- May 7, 2002
- 10,376
- 762
- 126
I know this is a common problem with this device, and the only fix seems to be to enter the special recovery menu, and then clear the cache partition.
It seems absurd that google hasn't come up with a fix yet.
This is with Kit Kat.
Has anyone with one of these things tried one of the alternative OSs that are out there to see if this is fixed in any of them?
I wonder if the 2nd gen one has this issue still?
Other than that, this is still a pretty nice device.
It seems absurd that google hasn't come up with a fix yet.
This is with Kit Kat.
Has anyone with one of these things tried one of the alternative OSs that are out there to see if this is fixed in any of them?
I wonder if the 2nd gen one has this issue still?
Other than that, this is still a pretty nice device.