Since I got the Fire about 1.5 months ago, music apps have never worked flawlessly on this tablet. The system will randomly freeze, music will loop the past half second for about 20 seconds and reboot. It has occurred on stock, CM, and Slim roms so it is not specific to Amazon's terrible FireOS. What I have learned is that the tablet will never crash if the screen is on, only when the screen is off. It seems to happen only after a period of time (variable between 2 minutes to 30 minutes) of the screen being off. It also seems related to battery usage since I also never noticed crashing when the tablet is plugged in. I have been able to increase the time between crashes significantly in the past by installing the music player as a system app so it could also be a problem with cache/permissions. I have tried full wipes so I don't think its an issue with dirty flashing. Anyone else encountering this issue?
Can anyone direct me to a guide on troubleshooting a kernel crash? (Logging it) I assume that's what is going on here. I tried looking for the /proc/last_kmsg but it doesn't exist.
Anyone? Tablet still constantly crashing despite trying various roms after factory reset and full wipe.
I played with the kernel adiutor to prevent low memory killing which fixed the problem, but now the tablet becomes unresponsive with chrome open. Seems like it only has enough memory to run one or two apps at a time (chrome being so intensive). For the cause of the crash, I believe it was related to Spotify being killed by android memory manager and somehow it crashed the kernel when trying to kill Spotify with the screen off.
Same issue here, I messed around with the kernel settings trying to find a solution. I believe the issue is caused by the hotplug governor turning off CPU cores while the screen is off with the music app, somehow this is causing the CPU to lock up. In Kernel Adiutor, go to CPU > CPU Governor Tunables and change 'is_cpu_hotplug_disable' from 0 to 1 and set it to apply on boot. So far this has worked for me.
Related
Hey all,
I am currently running my VZW Galaxy Tab with a stock 2.2 Froyo build that is rooted and running Boushh's KhasMek Kernel V5.
Ever since I installed that kernel, I have been experiencing constant force closes. It's really not any one app either, it is most of them. So far, I have put the freeze (via Titanium Backup) on all the apps that have FC'd a lot that I don't use. Maps was one of the biggest culprits. Facebook FCs a lot as well, and the only way to fix it is to go into app management and clear data. Similar issues with random games and such as well.
I have tried uninstalling and reinstalling multiple apps, and this helps for a time, but doesn't last too long. I have tried switching launchers, just in case it was somehow related, but it doesn't seem to be.
Basically, whenever I leave the tablet on idle for more than a few minutes, when I unlock it something hangs and I get an FC of a random app.
And a lot of times, it just does the single vibrate, followed by two quick ones, and nothing comes up as having FC. But, in the mean time, the tablet is unusable until it hits the second set of vibrations.
This is extremely annoying and is preventing usage of the tablet for periods of time. So, I am wondering, is anyone else experiencing this? If so, what have you done to fix it? At this point, I am inclined to just revert back to stock, though I would rather not.
Thanks for any insight.
As of now, I am constantly getting
com.google.process.gapps
force closing.
[Q]
Out of the blue my Bionic just started rebooting. 8-10 time per day, who knows how may time at night. I am using the stock ROM. I am looking for a stable ROM that I can use to fix the problem. I also have the problem of disapearing apps that I move to the ext card.
Feedback on possible cures will be welcomed.
I just experienced my first unexpected reboot. It was after plugging in my USB to my computer.
This seems like the sort of thing that would have a 50% chance of being related to your hardware, and a 50% chance of an unstable app screwing something up. The stock software is at least stable enough that it's not very likely to be the cause of your issues, and flashing another ROM (which will have the same kernel) won't help if it is a hardware issue.
A factory reset followed by staggered reinstallation of apps (one or two at a time, to see if one in particular might be causing issues) would be my first step for a problem as extreme as random reboots. The next step is through warranty channels. I might even do that first- I don't think I could put up with a phone that rebooted on me.
And the cure for disappearing apps is to not use media area for storage. The phone dedicates 4gb for apps, that should be more than enough until they patch a fix.
i may have to add that my phone was completely stable until i purchased and installed the extended battery then i started to experience reboots and a few locks here and there.
i did a few factory reset on the stock but the phone was still acting up with the new battery.
i then decided to root and run roms and to be frank no locks and or reboots running the same battery that seemed to be causing the problems based on that being the only change to my phone before the reboot and locks.
i am not saying that there is something there with the stock as there would be more reports on this but rooting and going back to stock is a single click now making it a fast process to trouble shoot the software.
i am experiencing a bad or short life with the extended so in my case it could have been the battery screwing up the reads on the software (guess) but the first 3 charge from full to dead just about 3 days after that same extended only last one day.
in general it seemed that my issue could have been a bad battery and wiping data and playing with roms may had help but in the end i will be calling verizon for a battery replacement as i doubt that in two weeks the battery charge for an extended could only last 1 day of medium use.
sorry long response and by no means i'm i encouraging to root and rom just speaking out of my experience.
Hi - first post here. After 4 Thunderbolts - Verizon sent me a Bionic. Much better however, after rooting with 43v3r and de-bloating with The Black Hat App - I'm having random reboots. Initially, the reboots were several times per day increasing in frequency to several times an hour. Y u c k - My Thunderbolt could do that too.
So in troubleshooting:
1 - I've reverted to stock build - no add'l apps: No reboots in 48 hours. So - I doubt it's hardware.
2- After reverting - I then rooted w/43v3R, then debloated - just using stock apps - no reboots in 24 hours. So, I really doubt it's debloating or rooting
3 - After adding a few apps - Stitcher, Enhanced email, SVOX w/voice, Beautiful Widgets (w/clock selected) - I get a reboot.
4 - Remove everything but stitcher. No reboots - 24 hours.
5 - Add Enhanced Email yesterday
Today, I had a reboot.
6 - So culprit 'looks' like Enhanced Email OR perhaps a switching problem between 3/4g (The Thunderbolt - Stitcher used to drop connection in this particular location so, there IS an issue w/3G-4G.
Questions:
1 - If it's not a 3g/4g issue; could it be related to where Enhanced email or Stitcher chooses to install itself?
2 - Is there a log somewhere where I could find 'boot' times and any issues relating to reboots? Like a 'minidump' in Windows...
thanks
I, too, have started having unexpected reboots. I can't pinpoint it exactly, but I have also recently isntalled Enhanced Email (trial version).
Reboot Logger
Hey Google is our friend - don't know why I didn't look before but I found this in Android Market.
"Reboot Logger" by Watanabe,Masayuki.
Just installed it - will report back after Thanksgiving (in the U.S. - Thursday)...
(I would post a link but I'm a noob here - and, now I know why I hate myself.)
Looks like promising -
Have yall installed any themes or different battery icons, or anything like that to yours? Mine is 43v3R rooted with the liberty romv2. I was changing a cpl of the icons and experienced a reboot just out of the blue. I got rid of the icons I changed and stayed with the icons that came with the liberty rom and have no issues at all. I do not have enhanced mail on mine.
most bionics will turn off and wont turn back on till you do a battery pull. Its a known issue, all you have to do is google it and it turns up. From what ive read putting the battery on performance mode and putting on detect in pocket will help. Personally it doesnt help, i had the issue with the stock battery so purchased a extended thinking it was the battery, but after doing research i found out it isnt. They say the new OTA should fix it
icons - reboot logger
Thanks - haven't changed any icons BUT I am using HTC Thunderbolt wallpaper. I had a Thunderbolt that had a reboot problem until the OTA before Gingerbread - Verizon offered me the Bionic when I called about my Thunderbolt issues (I had three replacements - all with the same issues).
I will try different wallpaper -
Reboot logger works well but doesn't offer a clue as to what is causing the reboots. Mine has rebooted 2-3 times per day since I installed Reboot Logger(RL).
3 times a day is tolerable but, I would like to get to the bottom of what's causing it.
What IS helpful with RL is that it does show that the reboots are not occuring in any obvious time sequence.
They may be related to push emails coming in from my Exchange server. Not sure - I'll post more as I learn more. Hopefully the upcoming OTA will fix - though my experience with HTC's OTAs does not give me a lot of hope.
Update - Last night, I uninstalled Stitcher - Stitcher frequently throws errors requiring a FORCE CLOSE. I also have kept Blueooth off.
No reboots in 24 hours -
Will reinstall Stitcher in the morning (I need it at the gym)...
Update tomorrow/Monday
Turned Bluetooth ON - no reboots in 36 hours so, It looks like Stitcher may be the culprit - I wonder if Stitcher has issue with the internal/external SD storage scheme.
As I noted previously, Stitcher reports 'force closes' frequently - especially when it's not even active (when I have not loaded it or used it).
(No sooner than I posted this - my phone rebooted. And again, and again will switch off BT - I'm in my office so, there's could be an issue with 3g/4g switching or other interference...)
Have you tried setting the phone to run strictly 3g? I have had no issues at all with mine jumping back and forth between 3g/4g.. I leave mine on 3g to keep it from trying to search for a 4g signal. I never turn bluetooth on, nor do I ever really use the compass. hmmmm... Can you tell me everything you have done to the phone. Apps you have installed, what ROM you using, if you have .886/.893 etc? I'm willing to see how close we are as for as how our phone's are setup and help as much as I can. I have not had a single issue with mine other then that one reboot after changing the battery icon.
After nearly two weeks of monitoring restarts - it appears that the problem is more related to where I am. At my home, restarts are rare and related to Stitcher.
At work in Beverly Hills, CA; restarts occur frequently. I assume it has something to do with 3g/4G switchover/crossover or interference.
I had lots of problems with the Thunderbolt dropping data connections in 90210. I could not use the hotspot. On the Bionic, the hotspot functions really well. I've used it up north near Fresno in 3G only land, here in BH and at home where I have decent 4G coverage.
When I remove Stitcher, the reboot problem disappears. Sometimes when I 'wake' the phone, there is a dialog apologizing for Stitcher having 'force closed' even if I haven't used it for days. Market reviews indicate anecdotally that Stitcher has a problem with force closes. This behavior must also be at the root of some of the reboots.
I've also set all programs not to update automatically - this may have reduced the reboots as well. On average, I'm getting 2-3 reboots per day. More than I would like but, tolerable.
I'm seeing lag on the phone under a specific set of conditions and wondered if anyone else was seeing this. If the phone has been asleep for more than about 20 minutes, after I wake the phone the first app that I launch, irrespective of what the app is, lags for about 2 seconds before opening. Any less than about 20 minutes sleep time and the problem doesn't appear.
After the initial lag opening the first app everything works fine until the phone has been asleep again for more than around 20 minutes. Then the same thing again..... the first app that I open lags for about 2 seconds before opening.
The problem was happening with the standard kernel, KKA. I've since rooted and flashed AbyssNote 2.3 but kept the standard rom and the problem is still there. Anyone have an clues what might be causing this?
Remember that when the CPU comes from a deep sleep it's running <50Mhz. So as soon as the phone wakes it needs to speed up again. That's it's only the first App. By then the cpu is running >800Mhz.
Sent from my GT-N7000 using XDA App
Two seconds for CPU waking up? It's 21th century.
GPSSerbia said:
Two seconds for CPU waking up? It's 21th century.
Click to expand...
Click to collapse
I totally agree but it's not the dreaded wake up lag that I'm referring to. I really thought Samsung would have dealt with that by now, but to their discredit they haven't either on the SGS2 or the Note.
People who justify the wake up lag by saying the phone has been in deep sleep are clutching at straws. HTC phones deep sleep and don't have wake up lag. This is a Samsung issue and it should have been dealt with by now on phones of the caliber of the SGS2 and the Note.
The lag I'm referring to is after the phone is awake and I launch the first app. There is a lag of about 2 seconds before the app launches, irrespective of what actual app it is the I'm launching.
After that, all is good until the next time I use the phone.
Tried to change microSD card, or trying to use phone without it? Seems like card problem.
I don't have this lag issue on my note. I use abyssnote kernel with interactive CPU governor.
Sent from my GT-N7000 using xda premium
GPSSerbia said:
Tried to change microSD card, or trying to use phone without it? Seems like card problem.
Click to expand...
Click to collapse
Thanks for the suggestion but the microSD card is not causing the problem. I removed the card and the problem still exists.
I get this lag too guys, sometimes longer than 2 seconds. Very annoying. Also you have to wait ages for the app list to appear when creating shortcuts for homescreen. This happens after the phone has been on for a while after a reset. Its fast from a fresh reboot. This does not happen on the S2.
General responsivness of the phone goes downwards as time and days pass. This does not happen with the S2. Have to reboot every two days pretty much to get the snappiness back as clearing memory via task manager does not solve this.
I'm Using Checkrom with Abyssnote Kernal. Happens with FM Kernal too, so I don't think its kernal related. Don't remember this happening on stock firmware.
I had a similar problem(but worse) sometimes when using the stock rom.
I've replaced the stock rom and been using CM10.1 on emmc.
Sometimes when playing games the touch screen may become unresponsive but the 3 standard buttons still would work.
(as well as the hardware buttons.)
When this happens I'm not able to click on any of the icons on the home screen. (none of the control buttons work in game, either.)
I wonder if this is a hardware problem, CM10 problem, or a problem with the coding of the game (dungeon hunter 4.)
The problem actually does not last. Nook HD+ recovers by itself after about 1 minute.
Else, I could also click on the power button to turn off display and turn it back on.
Once it's back on everything is working including the in-game controls.
Does anyone have a similar problem?
I doubt this could be a bug in the game (Dungeon Hunter 4). The game is very buggy but when I play it on Nexus 7, I never experienced any control button issues. (Though it does crash "a lot" and sometimes more often than on the Nook HD+)
I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help
ndttung8487 said:
I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help
Click to expand...
Click to collapse
Thanks. I appreciate your help. I had this problem again today and I noticed the available ram was indeed quite low at the time.
Although it seemed unresponsive, it seemed more like being extremely slow.
Somehow if I turn off the display and turn it backs on it gets a bit better.
I suspect dungeon hunter 4 has a memory leaking problem. (memory not released completely if reload an area many times.)
I tend to have this problem if I load a lot of data in the game several times.
Strangely this does not occur on Nexus 7 based on the latest patch.
I searched in xda and it seemed last year Nexus 7 also had the same problem especially when playing certain games.
So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Here is his topic: http://forum.xda-developers.com/showthread.php?t=2263553
ndttung8487 said:
So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Click to expand...
Click to collapse
Thanks. I deleted the game as it is very buggy, crashes often and with many in game bugs. I'm finally done with it.
If I encounter the same issue with other apps I'll definitely upload the log.
I had it on all roms
Hi,
No, you are not alone. The issue occurred on all roms I used so far.
Indeed it mostly shows up in games, though I think I noticed it in other apps too occasionally.
I usually use the power button, but I'll try clearing the memory in the future...
M.
Hello,
For the last 6 months or so, I've experienced many lag issues with my device. At the begging, I had a CM11 ROM installed on my phone, so I decided to revert back to the V20B official european firmware because I thought those lags were related to the ROM. But nothing changed, and as of today I still have responsiveness issues.
This lag issue appears from time to time, and makes my device basically unusable. It feels like the whole CPU is hogged by an application, or like I underclocked my device to 53mhz on purpose. During these lags, trying to wake up my device will take up to 5 seconds, and navigating the main screen will be nearly impossible. Also, my phone will get very hot which would imply that my CPU is indeed used by an application. Sometime the issue will disappear by itself after a few minutes, but I usually reboot the device which temporarily fixes the problem.
I have tried to disable LG MLT, and I think it helped but the lag still occasionally occurs.
I don't really use third party applications either.
I think these lags might be related to the Google Chrome browser, but it doesn't make any sense as it is an official app.
Anyway if any of you have an idea on how to fix the issue or how to find the application/service/whatever hogging the CPU I'd be grateful
Thanks !
I did experience such lags in CM11 after a few days of usage.But talking about stock, these freezes sound bit weird.You might want to check your installed apps.Download watchdog lite from play store and let it watch on agressive mode.Also check if your phone is hot when these freezes occur, might be the throttling kicking in.
I also experienced this kind of lags due to bad gapps I had installed back in the day, though stock ROM comes with gapps so it's not that.
Thanks for your reply,
I installed Watch dog lite and I'm now waiting for an alert. I hope it will give me the name of the culprit
If you are rooted which i assume you are. You can try app from playstore called "lagfix" (fstrim)
Sometimes really helps. Sometimes it doesn't