Database Info

Any way around not having to clear the "cache" on BOOT?

So I am running into the problem that my phone wont boot up if I turn my phone off, or it dies.
The only way around to getting it back on is getting CWM up and doing a "cache wipe".
The symptoms I am having when I try to turn it on is I do not get past the LG logo. The soft keys are lit and the screen back light comes on and off (black screen) with a 2-3 second intervals forever (have not went past 10min).
I am running xboards tweaked 2.3.3 with fauxes stock volt kernel, any more into?
Thanks guys.

No one? Really?..

Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.

Paul Nur said:
No one? Really?..
Click to expand...
Click to collapse
The only thing I can think of is maybe an issue with the custom kernel. Do you remember having the issue before you flashed Faux's kernel?

jboxer said:
Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.
Click to expand...
Click to collapse
.. and that. lol

jboxer said:
Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.
Click to expand...
Click to collapse
I installed fauxes OC (over clock), and its working fine now, I was having problems with SV (stock voltage), maybe that was the culprate?
P.S. After restarting my phone (I have been doing it every so often to test for stability) my home screen got reset to factory? I had all my apps and everything, it was just factory..??? Only happened once tho.
phburks said:
The only thing I can think of is maybe an issue with the custom kernel. Do you remember having the issue before you flashed Faux's kernel?
Click to expand...
Click to collapse
^^^^^^^^^^

Can't find stable Android 4.x ROM/ Kernel

Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.

Unrelashade said:
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Click to expand...
Click to collapse
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2

mattlowry said:
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own

demkantor said:
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
Click to expand...
Click to collapse
Thanks guys! Fastboot says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
Click to expand...
Click to collapse
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha

Unrelashade said:
Thanks guys! Fastboot says:
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Click to expand...
Click to collapse
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2

Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium

You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?

mattlowry said:
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
demkantor said:
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
WeekendsR2Short said:
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
Click to expand...
Click to collapse
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.44.1107
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
Jun 27 2011, 14:08:29
Click to expand...
Click to collapse
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha

If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Sent from my HTC MyTouch 4G Slide using xda premium

Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2

A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Sent from my myTouch_4G_Slide using xda app-developers app

Unrelashade said:
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
Click to expand...
Click to collapse
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.

WeekendsR2Short said:
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
Click to expand...
Click to collapse
Thanks for the info.
demkantor said:
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Click to expand...
Click to collapse
Ok, right now I'll not try flashing bootloader since everything seems to be normal.
What I did to get last_kmsg:
Code:
Open terminal app
Enter "su" to get root privileges
Enter "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" to save current log.
Close terminal app.
I attached the last_kmsg.txt. What do I do with it now? I don't have knowledge to understand it.
mattlowry said:
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
I can't remember using a ROM that never crashed, but I'll try a stock ROM if nothing else works. However an old kernel of scverhagens CM 9.1 seems to work flawlessly if battery is not about < 15%. The newest r10 kernel on the other hand always immediately crashes when the phone is not charging. When charging I haven't experienced a crash yet. That's strange and makes me suspect my battery is the problem.
mojoffdawal said:
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Click to expand...
Click to collapse
Thanks! I guess I'll try an Anker since I have seen so much users here using it.

virtuous rom works great! when i had mine, i was running 4.0.3 overclocked to 1.5ghz. super stable too! daily driver for sure.
Sent from my SGH-T999 using xda app-developers app

Thanks, but the problem is I'm pretty sure that something's wrong with my phone...
I'll try virtuous ROM and a new battery though.

hope it works
Sent from my SGH-T999 using Tapatalk 2

So, I'm reviving this thread, because I stopped writing only because my phone was broken. Now it's back and I'm facing this problem again.
I've tried a lot of the 4.x ROMs here from the forums, but all of them rebooted or shut down after 5 - 10 minutes after flashing. I also tried some without flashing gapps even, but still the same symptoms. Also tested it with my new battery, nothing changed. Even the scverhagen CM 9.1 ROM rebootet shortly after flashing that worked longer previously (guess that was just by chance)
Now I've tried the original image and it works! Ugh. So what can be wrong, any ideas?

I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app

bit1 said:
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
It happened with both stock and new battery (Anker).
Thanks, update to latest TWRP had been my next try, if it didn't work now. But it does! Yeaaah so happy Thanks to everyone again. Almost three hours uptime and not a single issue so far!
To conclude: What I did:
Revert completely back to stock with BlueIX6's stock image (except that phone was still s-off and sdcard not wiped).
Then followed instructions to unlock bootloader, flash CWM recovery and finally flashed ROM (see sticky thread). Works like a charm!
In hindsight maybe radio made my phone unstable... I think it's the only thing that's different from now.

[Q] Hardware issue?

Does anyone have a problem with random "pauses" while using apps? It's totally not noticeable for applications that aren't continually running animations (ie: kindle, text scrolling) but becomes evident when doing thins such as:
- recording video (the "pause" will cause the recording to stop randomly for both continuous and time lapse)
- playing games (will cause the game to go to the pause screen)
- tasker programming (I think this is affected because tasker will randomly close itself without a FC dialog, profiles and tasks seem okay)
I turned on debugging to see if it was a dirty screen or anything, but the touch coordinates don't change at all when the "pause" happens. Anyone have an idea how I can fix this? It is rather crippling to the N5.
I am rooted and I have seen this problem on all roms (and I believe I noticed it on stock too...)
I use a ballistic case, if anyone else has had problems with it...
Thanks in advance!
Using N5 on Carbon + Franco kernel

I guess no one's ever had this problem before? =[

Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar

Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
I've tried out a few roms (factory reseting and cache clearing between each one) to see if it was any one problem, but whether AOSP or CM based, I still have the problem =/
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!

Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Click to expand...
Click to collapse
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?

mistahseller said:
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
Click to expand...
Click to collapse
I used the Chainfire's autoroot (http://forum.xda-developers.com/showthread.php?t=2507211) on Windows.

mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm, I think it worked. I haven't tested it out for lengthy periods of time but I haven't noticed any pausing anymore! =]
I followed the unroot instructions to return to stock. Although I didn't relock the bootloader.
Then I booted up stock and it seemed like it works fine.
I reinstalled CWM recovery through adb (same as I did the first time) and proceeded to reflash
It seems like the problem is gone now on custom ROM as well. Interestingly enough, if I nandroid restore my old backup, I do get the problem again.
Is there something different between reflashing stock part and wiping from factory/data reset + system partition format + wipe cache + wipe davalik?
Thanks for your help guys! I was sure before that it was hardware since I had the problem on stock w/ root, but thankfully it's not a hardware problem! =]

Camera problem

Hi people I have been using my Nexus 5 for a month now. Loving it! Going stock with Elemental 26 kernel, dalvik
This happens quite random, not often but it is annoying. Camera stops working.. I start it up.. And it just.. Black.. Waiting until it says "camera stopped“ a restart does help, but I have Sometimes missed some shots because of this.
Anyone that have experienced this and have a permanent solution?
Sent from my Nexus 5 using xda app-developers app

UnLucky12 said:
Hi people I have been using my Nexus 5 for a month now. Loving it! Going stock with Elemental 26 kernel, dalvik
This happens quite random, not often but it is annoying. Camera stops working.. I start it up.. And it just.. Black.. Waiting until it says "camera stopped“ a restart does help, but I have Sometimes missed some shots because of this.
Anyone that have experienced this and have a permanent solution?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
To try in order - step by step if the previous didn't solve the problem:
1. Clear app data
2. Flash the stock kernel
3. Factory reset
4. Clean installation
5. RMA...
I had it on my previous device and it was a hardware bug so :fingers-crossed:

Primokorn said:
To try in order - step by step if the previous didn't solve the problem:
1. Clear app data
2. Flash the stock kernel
3. Factory reset
4. Clean installation
5. RMA...
I had it on my previous device and it was a hardware bug so :fingers-crossed:
Click to expand...
Click to collapse
Thanks! Clear app data haven't worked, so will try to flash the stock kernel when I get home. Will get back to this thread if the step doesn't work.
And.. RMA?

UnLucky12 said:
And.. RMA?
Click to expand...
Click to collapse
Send your phone back to Google for repairs.

I've had this issue once while on CM11. A restart fixed it, leading me to believe it's a ROM/Kernel bug, and also hasn't happened on the latest nightly. OP, try a different kernel version.

abtekk said:
I've had this issue once while on CM11. A restart fixed it, leading me to believe it's a ROM/Kernel bug, and also hasn't happened on the latest nightly. OP, try a different kernel version.
Click to expand...
Click to collapse
I am on stock, maybe it is kernel related.. I don't know. Don't want to blame the kernel just yet. But 26 is the latest. Waiting for an update, maybe try another kernel and see if that help, if the problem occurs again.

UnLucky12 said:
I am on stock, maybe it is kernel related.. I don't know. Don't want to blame the kernel just yet. But 26 is the latest. Waiting for an update, maybe try another kernel and see if that help, if the problem occurs again.
Click to expand...
Click to collapse
Flashable zips of stock kernel are available here. You can also fastboot flash the boot.img file from the factory images.

Phone won't stay off

Running stock Lollipop rom with Franco R68. Rooted with CFAR. Since I flashed latest TWRP this afternoon the phone won't shut down. Every time I turn it off it turns back on after a few seconds. Not a major problem but is this happening to anyone else?

pepdavies said:
Running stock Lollipop rom with Franco R68. Rooted with CFAR. Since I flashed latest TWRP this afternoon the phone won't shut down. Every time I turn it off it turns back on after a few seconds. Not a major problem but is this happening to anyone else?
Click to expand...
Click to collapse
i dont have this particular issue but i found 2 other threads stating this issue here and here

Haven't seen it yet but I had it on KitKat randomly. I don't have a clue how to fix it, reboot don't help.

Pretty sure this is an r68 issue, I'm sure franco will fix this soon!

pepdavies said:
Running stock Lollipop rom with Franco R68. Rooted with CFAR. Since I flashed latest TWRP this afternoon the phone won't shut down. Every time I turn it off it turns back on after a few seconds. Not a major problem but is this happening to anyone else?
Click to expand...
Click to collapse
not because of twrp.
the recovery and rom are in two different partitions. most likely its an app causing the issue.

nexus.freak said:
i dont have this particular issue but i found 2 other threads stating this issue here and here
Click to expand...
Click to collapse
Thanks but neither of those issues are the same as mine

It was Franco. All fixed now. Thanks

pepdavies said:
It was Franco. All fixed now. Thanks
Click to expand...
Click to collapse
Having the same problem too! May I know what the "fix" was? The only way I managed to get rid of it was to reflash r67.

jamentangent said:
Having the same problem too! May I know what the "fix" was? The only way I managed to get rid of it was to reflash r67.
Click to expand...
Click to collapse
Franco uploaded a fixed version of r68