Database Info

[Q] TF700T keeps rebooting

All,
After having used this device for more than one year (just beyond the warranty expiration), we have found two issues:
The power button does not work properly - we seem to have to press harder, and in some cases, it seems to get stuck.
The machine keeps rebooting - this just started happening and occurs most often when using MyLibrary - the major use of the machine. Note that most items are library loans, i.e., have DRM.
Some more information regarding the crashing:
I tried to clear the cache, but all that shows up under the memory size is 'calculating' and the clear cache button is disabled. Simply looking at this information, not even trying to change anything, crashes the machine (and several times, I had to hard reset it to get it goign again)..
I have tried a cold boot, but that did not help.
The only thing I can think to try at this time is:
Factory reset
Start using a different read app - strongly considering Cool Reader
Is there anything else I can try before nuking the machine and starting over?
SPECS: 32 GB, Android V4.2.1, rooted - stock ROM

groston said:
All,
After having used this device for more than one year (just beyond the warranty expiration), we have found two issues:
The power button does not work properly - we seem to have to press harder, and in some cases, it seems to get stuck.
The machine keeps rebooting - this just started happening and occurs most often when using MyLibrary - the major use of the machine. Note that most items are library loans, i.e., have DRM.
Some more information regarding the crashing:
I tried to clear the cache, but all that shows up under the memory size is 'calculating' and the clear cache button is disabled. Simply looking at this information, not even trying to change anything, crashes the machine (and several times, I had to hard reset it to get it goign again)..
I have tried a cold boot, but that did not help.
The only thing I can think to try at this time is:
Factory reset
Start using a different read app - strongly considering Cool Reader
Is there anything else I can try before nuking the machine and starting over?
SPECS: 32 GB, Android V4.2.1, rooted - stock ROM
Click to expand...
Click to collapse
If you are rooted, try Lagfix from the Playstore. Google built the fstrim functionality into 4.3 - this does the same thing.
Let the app run a lot longer than it indicates it needs - I would run it overnight.
Any Android device gets clogged up over time. After a year of use a factory reset would not be a bad idea either.
Since you are out of warranty, consider unlocking and running a custom ROM - you won't believe the difference.... It's like getting a new tablet for free

[Q] Nexus 5 has repeated force closes on newly installed stock firmware

Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.

slixzen said:
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
Click to expand...
Click to collapse
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.

_MetalHead_ said:
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
Click to expand...
Click to collapse
I know this is a very late response.
The initial way that I installed the stock firmware was using fastboot, and installing each .img file separately.
I just re-flashed the factory image again (except for the recovery image), and am waiting for the phone to boot up (it seems like it takes ages for the phone to actually go from fresh install to fully booted), it has been over a 5 minutes now.
But once that is done, I will see what happens. Is there a way to check for bad hardware (I am specifically thinking flash storage)? Maybe that is causing the problem?

Sleep of Death befalls my SGN 12.2

Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?

To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.

ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).

Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.

Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.

Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?

Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.

Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.

[BUG][6.0.1 Stock]Home Button Ignored and Other Perfidious Symptoms

This mean bug hit us twice, so that it might be helpful do document it in order to help other persons with the same problems.
Symptoms:
Home button does no longer work.
Notifications and notification pulldown menu do not work (as consequence, data transfer via USB cable is impossible).
Quick settings do not work.
Factory reset does not work.
Developer mode cannot be enabled (as a consequence, no adb connection possible).
Automatic orientation disabled after every reboot.
Mobile data enabled (!) after every reboot (very funny if you pay 0,23 EUR per megabyte and do not notice...)
When changing volume using the physical keys, the device sometimes reboots.
This list is not necessarily complete, as there might be more symptoms.
According to various investigations (see links below) the system thinks that the Setup Wizard is still running. This bug presumably was introduced with some Android version (Oct 2015), came to the Moto G, and when the bug was removed, the Moto G did not get the corrected OS version.
When does the problem appear?
There are strong indications that the problem always occurs whenever the device runs out of (flash) memory. Note that our device did not have an SD when the problem appeared.
How can one heal the device?
There have been some recommendations how to repair the phone (see links below):
Change user
Run the SetupWizardTestActivity via adb
Run some additional command (see below) via adb.
Run the SetupWizardTestActivity via Nova Launcher.
Factory reset via Recovery.
What did really help?
In fact all methods 1 .. 4 failed, because no adb connection could be established (see Topic 5. of the symptoms), and the Setup Wizard got to an endless loop when I started it via Nova Launcher. So finally I used the Recovery system to reset the device.
If anybody ran into the same trap or has a better solution, please tell!
See also:
http://forum.xda-developers.com/2015-moto-g/help/moto-g3-properly-t3449495
http://forum.xda-developers.com/2015-moto-g/help/status-notification-bar-pull-t3435441
http://forums.androidcentral.com/an...me-button-not-working-many-more-problems.html
http://forums.androidcentral.com/mo...sing-huge-problems-moto-x-2nd-gen-2014-a.html
http://infomash.net/home-button-not-working-after-updating-to-android-marshmallow/
How to reset the Moto G

Reflash stock image via fastboot... if it continues to fail and you followed all instructions EXACTLY, your handset is defective, get it repaired or replace it.
The "setup wizard" bug is a known, but extremely rare, issue... but the symptoms are not the same as what you are experiencing. Home/Back/Recent buttons do not work -AND- the notification pull down do not work, in every case reported simply re-running setup wizard corrects the issue.

symptoms same , root reason may differ
Tenebrous sound thy words, and partially enigmatic is their meaning.
In fact:
- I forgot to mention the non-working notification pulldown menu, so I added this in post #1.
- Thus the noticed symptoms exactly match those described in the links I provided.
- However, the root reason might subtly differ, and, additionally, all proposed therapies except factory reset failed in our case.
- It might help to re-flash the stock or flash an alternative image to cure the device, but it was not necessary in our case, so it's not really a better solution.
I found this Lenovo Moto G3 forum dealing with the same problem:
https://forums.lenovo.com/t5/MOTO-G...cations-and-lock-screen-not-work/td-p/3255406
Post #9 mentions "my storage was running out".
Here is another one, for a slightly different device:
https://forums.lenovo.com/t5/MOTO-X...on-notifications-lock-screen-not/td-p/3354948

hey to chime in, I've got the same situatrion as of a few days ago on my Motorola Droid Maxx 2. WISH I could find a root exploit for this damned thing. I hate dealing with issues on it. Who has time for this garbage? I plan to do a factory reset (or try while expecting a failure as noted in original post here.)
Thanks for documenting your issue Ahkah as it at least has helped me feel OK about myself here. Excellent choice of wording. To the other poster, why do you speak so authoritatively to say that if _____, phone is defective? That's annoying and not true unless somehow here at android-is-still-interesting.com "defective phone" means "I dont know what happened."
What I have in common to your described condition:
- ran "low" on storage according to pop up.
- used some feature offering to "clean" hard disk or whatever. This may have been in FX file browser or else a native android feature or else a motorola app feature. Unfortunately dont recall. One of the few options it gave was to clear cache of all apps. Seemed risky to me but I hit it any way. This may have been the root cause.
- notification pull down reads only "no notifications."
- circle and square softkeys do nothing but give the visual feedback or sometimes vibration feedback that acknowledges the button press.
- pulling down from top of screen while bnotification area is already pulled down does nothing whereas normally it would open quick actions.
- searching /system for "wizard" comes back with a lot of results for apks, all of which do nothing, throw error, or install more of themselves.
- clicking developer options tells me that dev options are not available for this user. As far as I can tell there are no other users on my phone.
- clicking build number or whichever item in about phone multiple times to enable dev options does nothing.
- volume buttons to act funky and while fiddling with the phone that was one of the few things i was doing. simultaneously the phone was repeatedly rebooting. maybe correlated but i dont know i was messing with everything i knew to try.
Additional observations:
- phone takes a long time to boot up on some power off/ power ons.
- phone largely works if i could somehow ignore all the above.
- phone sometimes reboots mid-boot animation
- all above is observed after freeing up 3 gb on internal memory and i've had multiple gb free on sd card throughout issue.
I hate you motorola. I hate you google. I hate you verizon. I hate you CIA and NSA. I hate you United States. I hate you capitalism. I hate you imperialism. I hate you western world. I hate you ideology. I hate you technology. I DONT EVEN WANT A PHONE and this is how i get to spend an hour today.

Laggy Pixel - almost impossible to make/receive phone calls

Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
Ive updated to latest ota on pixel 1 and had no problems so far. You could check the dialer app is set as default dialer and all permissions are granted and maybe clear the apps storage/cache, force stop it and re open it and see if that solves anything? Could also check background apps and running services in developing options to see if an app is banging out the memory causing it to lag?
Sent from my Pixel using XDA Labs

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
if you already did factory reset then it must be a sign of motherboard is dying soon or bad nand chip. motherboard failing on pixel is very common but it happens to less than 1% of people. there are plent of threads on reddit/xda on this.

What's the status of your Pixel? Is the bootloader unlocked? Rooted? Did you have any such problems on the December udpate?

As mentioned - I did factory reset as I thought it may help cure the problems, but it didn't.
I have never unlocked bootloder and phone is not rooted. All standard here.
I have the latest update installed and same problems persist ;/
I'll try another factory reset today.