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
Related
I'm getting mad trying to debug these random reboots. I'm getting a lot of them while the device is sleeping, without any advice. Sometimes it even halts and gets to a black screen, and I've to remove the battery to restart it, because just pushing the power button won't do anything.
Here's the last_kmsg:
http://pastebin.com/m79ba1a6f
May anybody please help me addressing them? I've already tried all the standard things, like wipe dalvik cache, fix_permissions, wipe and reinstall and so on. Of course I'm ready to provide any additional info, if needed.
Thanks and keep up the great work!
BUG: scheduling while atomic: suspend/7/0xc00b67f9
I think this is the main problem with this crash. Any clue?
try
I suggest trying to remove widgets before then reboot and wipe dalvik cache.. I was having similar problems when I did this it worked fine.. Dont really expect anyone to help you here, they get pissed when people ask simple questions.
Okay, I'm gonna try this. Thank you very much!
im using that rom at the moment, have been using cyan for ages but i can no longer use it, its so damn laggy get blank screens between different apps ,reboots its so unusable
Today I tried a full format and reinstall. Started from scratch, and installed on top of the default 1.5 rom, and it seems to work much better. I still have some rare RR issues during normal app usage, but at least it does not reboots itself randomly without being used.
Trying to clear dalvik cache didn't help, the phone still was unusable, so I decided to format the SD without ext partition.
I'll try it out for some days, if I still will see many reboots I think I'll try out the RA rom, I've read it's much more stable.
Just why exactly didn't you flash 1.6 android first like it's advised?
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
http://forum.xda-developers.com/transformer-tf700
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?
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.
My phone died last Wednesday and has continuously proceeded to boot loop ever since. Not sure if this is due to mother board issues, a recent update, lack of space on device, or malfunctioning apps?
I don't think its a motherboard issue though. I was pretty much at capacity 29gb usable of 32gb. I recently downloaded instagram and every time I used it the the system UI send a warning message and proceeded to crash every time, but the phone never boot-looped? I had recently updated to 8.1.0 and after looking at the android loading screen over 1000x now, I can tell that the animation is a little different from before.
The bootloop that I am experiencing isn't a load then restart loop it's just an endless load. With the the google 'G' and an endless loading bar beneath swaying side to side for hours on end.
Unfortunately I haven't backed up my phone in more than 5 months. I was wondering if there was anything I can do to get my data back (i.e. media, numbers, texts etc.) or potentially get my phone working again with the data intact?
I can boot into recovery mode perfectly. In the past google had a "clear system cache feature" on V7.1 I think? but that was phased out with more recent updates leaving me with the option of only factory resetting the phone. My phone is not rooted. I was wondering if there was anything I could do in the recovery screen that could mimic the clear system cache feature? Like writing some sort of command line or something? Or anything else that I could do to get my data back and my phone working again?
What are my options?
buttface12 said:
My phone died last Wednesday and has continuously proceeded to boot loop ever since. Not sure if this is due to mother board issues, a recent update, lack of space on device, or malfunctioning apps?
I don't think its a motherboard issue though. I was pretty much at capacity 29gb usable of 32gb. I recently downloaded instagram and every time I used it the the system UI send a warning message and proceeded to crash every time, but the phone never boot-looped? I had recently updated to 8.1.0 and after looking at the android loading screen over 1000x now, I can tell that the animation is a little different from before.
The bootloop that I am experiencing isn't a load then restart loop it's just an endless load. With the the google 'G' and an endless loading bar beneath swaying side to side for hours on end.
Unfortunately I haven't backed up my phone in more than 5 months. I was wondering if there was anything I can do to get my data back (i.e. media, numbers, texts etc.) or potentially get my phone working again with the data intact?
I can boot into recovery mode perfectly. In the past google had a "clear system cache feature" on V7.1 I think? but that was phased out with more recent updates leaving me with the option of only factory resetting the phone. My phone is not rooted. I was wondering if there was anything I could do in the recovery screen that could mimic the clear system cache feature? Like writing some sort of command line or something? Or anything else that I could do to get my data back and my phone working again?
What are my options?
Click to expand...
Click to collapse
I think you can clear cache in fastboot. Not sure why you would continue to use an app that is crashing system.
lafester said:
I think you can clear cache in fastboot. Not sure why you would continue to use an app that is crashing system.
Click to expand...
Click to collapse
That feature was taken out of the boot-loader by google in the past few updates. I'm currently on 8.1.0.
I was wondering if there was an alternative method that I could take in fast boot/recovery mode that could possibly give me the same cache clearing result? Possibly some sort of adb method or something? Also unfortunately my boot loader is locked. So If I can't clear the cache, I was wondering what my current options are as far as backing up the device before I inevitably have to do a factory reset are?