Up until this morning after work, I had been using Synergy. On practically a daily basis, my phone would shut off randomly in the middle of use. Sometimes, I wouldn't even be using my phone. I had noticed my battery draining much quicker and Display would have the biggest impact. I could shut my screen off, check my phone ten minutes later and the battery will have drained another 5 to 10 percent.
This morning, I flashed MikG after reading it's one of the more stable Gingerbread ROMs that implements things I like about Sense 3.0. I went out to lunch and my phone randomly shut off when it said I had 84% capacity left on my battery. Every time this happens, I have to go into recovery and with cache and dalvik cache or I get random force closes. When I finally get back into the ROM, it shows 0% battery. At this point, I hook my phone up to a charger, wipe cache and dalvik cache and reboot my phone. When it got back into the ROM on the charger, it registered 87% capacity.
I'm not sure what could be causing these random shutdowns. I'm using radio 2.15.00.05.02, PRI 1.77_003, NV 1.90_003.
Random shutoffs
Your problems your describing are pretty broad and could be a result of many factors. Could be a kernel issue, not wiping phone properly, or a corrupt download of the rom. Plus your radio is way out of date, will effect you internet speed. I was on synergy and I know there was a lot of complaints on bad downloads. I would recommend starting over on a clean slate to isolate the problem.
1. restore nandroid
2. Install Amon Ra 2.3 recovery (if you dont have)
3. Update radios/wimax/etc.
4. Copy SD card to hardrive on computer
5. wipe phone in recovery minimum 3 times
6. Partion SD card 0/2048/ext 3
7. Flash synergy RSL1 zip in recovery (non God-mode recommended)
8. Flash Dark Tremors A2SD in recovery
9. Reboot phone let settle
10. Boot into recovery
11. Flash kernel (lithids freedom v.0.9) or new custom kernel out called sol
12. Calibrate battery
Do these steps and you won't have any problems
chessmyantidrug said:
Up until this morning after work, I had been using Synergy. On practically a daily basis, my phone would shut off randomly in the middle of use. Sometimes, I wouldn't even be using my phone. I had noticed my battery draining much quicker and Display would have the biggest impact. I could shut my screen off, check my phone ten minutes later and the battery will have drained another 5 to 10 percent.
This morning, I flashed MikG after reading it's one of the more stable Gingerbread ROMs that implements things I like about Sense 3.0. I went out to lunch and my phone randomly shut off when it said I had 84% capacity left on my battery. Every time this happens, I have to go into recovery and with cache and dalvik cache or I get random force closes. When I finally get back into the ROM, it shows 0% battery. At this point, I hook my phone up to a charger, wipe cache and dalvik cache and reboot my phone. When it got back into the ROM on the charger, it registered 87% capacity.
I'm not sure what could be causing these random shutdowns. I'm using radio 2.15.00.05.02, PRI 1.77_003, NV 1.90_003.
Click to expand...
Click to collapse
Sorry to hear you are having these issues but a fellow board member tried to help you and I understand you may be busy but a quick thanks I will check that out would of been nice.... Also there is a thread dedicated to your issue with quite a few post. Look here and I hope it helps you as well as what was advised above.
Not trying to be a @ss but people get mad when no-one answers them and this is something that with a lil searching you would of seen there were plenty of threads about and possible solutions. Good luck and I hope your issue gets resolved
I work nights and I haven't checked this thread since before I left for work at 6 last night.
Whenever I perform wipes, I wipe cache and dalvik a minimum of three times. Whenever I flash a new ROM, I wipe data a minimum of three times. I'll update my radio and see if I'm still having problems.
playya said:
Look here and I hope it helps you as well as what was advised above.
Click to expand...
Click to collapse
My phone doesn't randomly reboot, it randomly shuts off. It doesn't restart, it just shuts off.
You have a battery issue and for $15 on ebay you can fix it.
Sent from my PC36100 using XDA App
I bought one of those GaliliO batteries off eBay. This is my first day using it, but I'm already liking the results.
Related
I've tried several different ROMs (AvaV10, Cyanogen, Fresh, NonSense), along with different kernels (pretty-much any that I could find), and I simply can not get my phone to sleep. It's always at 100%, no matter what I do.
In Spare Parts I'm getting:
Other Usage - Total in all time:
Running 100.0%
(everything else under 10%)
Partial wake usage - Total in all time:
Android System ~35%
UID 10027 ~20%
(everything else under 10%)
Network Usage - Total in all time:
0 - 100%
Dialer ~40%
Android System ~50%
(everything else under 20%)
So now my question is, what is the "0" that shows up at 100% in my network usage? No matter what I change, I can't seem to get rid of that "0".
I'm on:
HBoot 2.10.0001
Radio 2.15.00.11.19 (I've tried 09.01 also)
Newest WiMax, PRI, and NV.
AmonRa Recovery v1.8.0
Multiple wipes on everything, nothing works.
The problem started about a week ago, and I simply can't figure it out. I've changed everything I could think of. I was originally on Radio 09.01, and I updated, but this was after the problem started. I also updated my HBoot from 0.97 after the problem started. Nothing seems to be working.
Note: I've also tried airplane mode, this does not help.
Solved using Calkulin's wipe method
I'm getting pretty good results from my setup.
1. Myn's Warm rom rls4
2. New kernel- I just downloaded last night but the battery stayed on 100% for quite a while. Here's the link- http://forum.xda-developers.com/showthread.php?t=876590&highlight=calkulin's
3.Riptide9's ColorNclear theme with several of the addons, speedo batt, blue dialer, launcher pro (the update for warm2.2 themed).
I myself have tried probably every rom out there that has working 4g, I dont see owning an evo and not having 4g, and found this one to be the best. You do have to do an update to the wireless tether, can be done through the app itself. Hit me up if you need assistance. If it is the batt life you're primarily concerned with, this kernel is supposed to be awesome. Check it out, mine is overclocked to 1152000 and it still stayed at 100% for a good amount of time after being taken off charge. If you try it and like it let me know. I like to know that I was able to help someone.
Try removing your SD card and see if it still has that issue.
I suppose I should have mentioned why I need a fix so badly...
I'm only getting ~4 hours of battery life. I go into work at 6:30am and when I leave for lunch at 11:30, my phone is dead (with absolutely no use).
I need to figure out what this "0" is in "Network usage" because that's what is keeping my phone awake 100% of the time. Like I said though, even Airplane mode doesn't fix it (I don't see why something is using my network in airplane mode).
I tried removing the SD-card, that didn't help.
I've already tried the kernel that you linked to, that didn't make a difference... Same issue, my battery just drops.
If I'm doing something, I can literally just watch it drop in front of my eyes. If I'm using the phone (browsing the web, checking email, etc...) it drops one percent about every 20-25 seconds (I get something like 40-45 minutes if I'm using the phone before it dies).
maybe you have a faulty batt. I dont know.
Have you tried completely starting from square one?
titanium backup, then wipe everything, wipe again, and flash the stock rooted rom (or maybe even the OTA and re-root later).
After flashing, reboot your phone but dont restore your backup yet. See what happens, then slowly restore apks and files, etc, one at a time and see how the battery acts.
I don't know what the "0" means, sorry. But maybe this will help you figure out what is causing the problem.
Harfainx said:
I've tried several different ROMs (AvaV10, Cyanogen, Fresh, NonSense), along with different kernels (pretty-much any that I could find), and I simply can not get my phone to sleep. It's always at 100%, no matter what I do.
In Spare Parts I'm getting:
Other Usage - Total in all time:
Running 100.0%
(everything else under 10%)
Partial wake usage - Total in all time:
Android System ~35%
UID 10027 ~20%
(everything else under 10%)
Network Usage - Total in all time:
0 - 100%
Dialer ~40%
Android System ~50%
(everything else under 20%)
So now my question is, what is the "0" that shows up at 100% in my network usage? No matter what I change, I can't seem to get rid of that "0".
I'm on:
HBoot 2.10.0001
Radio 2.15.00.11.19 (I've tried 09.01 also)
Newest WiMax, PRI, and NV.
AmonRa Recovery v1.8.0
Multiple wipes on everything, nothing works.
The problem started about a week ago, and I simply can't figure it out. I've changed everything I could think of. I was originally on Radio 09.01, and I updated, but this was after the problem started. I also updated my HBoot from 0.97 after the problem started. Nothing seems to be working.
Note: I've also tried airplane mode, this does not help.
Click to expand...
Click to collapse
You need to do caulks format all as it will wipe everything that the recovery misses. Hope that helps
Sent from my PC36100 using XDA App
Excellent, I got it working!
Performing Calk's wipe, and doing a fresh install seems to have it working again. I was thrilled to see that I wasn't at 100% after setting my phone down for 20 minutes to let it sleep.
I've been installing apps one by one hoping that something doesn't break it again.
I still have no idea what was causing the problem, but it's fixed now. Thank you for the help everyone, especially Craigbailey for the advice and Calkulin for the fix.
So I'm having this exact same problem (100% time running), but Calkulin's format all did not work for me. I ran it, flashed a brand new ROM, and I was still at 100% run time. I did nothing other than sign in to google, and download spare parts to check my run time.
Any other suggestions?
First remove the battery let it sit for 5 minutes outside of the phone... At the same time remove the sd card and put it back in... Then after waiting 5 minutes put the battery back in. Then do the format and all should be good... I too had this problem with original senseui rom that was rooted and solved this problem through sprint and thats what they told me to do and it worked... Oh and also try setcpu and a screen off profile with the right kernels should extend your evo battery to 30 hours or more depending on phone usage! I have cm7 nightly with savage zen bfs kernel and with setcpu I'm getting 30 hours on a regular batstat says 37 hours has been my max awake time... So doing pretty good with that give it a try and with cyanogen you should try performance tweaks to underclock your rom.
After finally flashing my phone with EVIo Cailukin's Rom I have endured some problems and I've search for them and coudln't find anything. I rooted my phone with the latest UnrEVOked program. Noticed this morning my phone was running 100%...
upon other problems, my phone internet speed is lagging. and my battery is really hot!
Pneuma1985 said:
First remove the battery let it sit for 5 minutes outside of the phone... At the same time remove the sd card and put it back in... Then after waiting 5 minutes put the battery back in. Then do the format and all should be good... I too had this problem with original senseui rom that was rooted and solved this problem through sprint and thats what they told me to do and it worked... Oh and also try setcpu and a screen off profile with the right kernels should extend your evo battery to 30 hours or more depending on phone usage! I have cm7 nightly with savage zen bfs kernel and with setcpu I'm getting 30 hours on a regular batstat says 37 hours has been my max awake time... So doing pretty good with that give it a try and with cyanogen you should try performance tweaks to underclock your rom.
Click to expand...
Click to collapse
I tried the removing the battery thing, and I'm still getting 100% run time, with a nandroid restored rom, and 2 different newly installed roms. I am so confused now. Anyone have any suggestions?
UPDATE: Looks like my phone is not at 100% run time anymore. All I did was redo Calkulin's format_all, flash a new ROM, and then reflash the new radios and PRI, and now my phone is not 100% running anymore.
Yay!
Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference
bump. should I post somewhere else?
Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!
I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App
I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies
Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
louballs said:
Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
Click to expand...
Click to collapse
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
HTCDreamOn said:
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
Click to expand...
Click to collapse
Thanks for the tip. I had already deleted the battery stats bin file from the system and rebooted and received the same results (assume thats what your fix does). I've also reinstalled the rom and had no issues. Ive done searches and found that SEVERAL other people with the G2 had this issue. Kind of surprised it hasnt yet been addressed on this forum. Back in 2011 Tmobile was asking for people to volunteer some info in order to fix it. Apparently nothing was ever done and when i call in (several times), no one seems to know what im talking about even when i point them in the direction of their own forums. I'm really at a loss and don't feel like paying out the a$$ for a new phone when I know this is not something I did.
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Different roms use a different amount of power...
Sent from my GT-P3100 using xda app-developers app
xSTUDDSx said:
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Click to expand...
Click to collapse
I'm not 100% sure but it is possible the bricking messed with the battery. LGNPSTing back to stock could have affected it, anytime you flash a new rom it takes a couple of days to "settle in" but you said last weekend so it should be settled by now.
But from your info, it may be the way you are charging it. There is a common misconception that every so often you are supposed to let your battery drain fully and then charge to 100%. This is only true for nickel based batteries, ours is lithium so this is in fact quite detrimental. Lithium batteries are built to be charged often and you should never let it dip too far into the red. Doing so decreases the life and performance of your battery significantly. 5% is as low as I'll let my battery dip before charging and even that is pushing it imo. There is an app in the play store called battery calibration that actually tells you to do this, but like I said, it's only useful for nickel based rechargeable batteries. Also this same app's function is deleting the batterystats.bin file in order to "recalibrate" the battery. This is also completely false as that file has nothing to do with how well your battery performs.
I wouldn't turn the phone off to charge, just charge it while it's still on so the screen actually shuts off. Checking your wakelocks and using greenify on power hungry apps will go a long way. I also turn my capacitive buttons off because I don't need to see them to know left, right, center and what they do. And if I'm not using it, it is always off, sync, gps, brightness when inside, etc. But as I said, it may have been the way you were charging it, it might not affect the battery for months, then all of a sudden your battery doesn't perform as well because it's dying due to improper charging techniques. And when you LGNPSTed back to stock, your system tries to start fresh which is why it may have happened immediately afterwards.
I hope some of this helps you - if using greenify doesnt show improvement you may want to buy a bigger capacity battery and start fresh. Installing the new battery is tricky however, there are youtube videos on how to do it, but it may not be for everyone.
Good luck and I'm sorry if I assumed too much or misread your info!
EDIT: You may also want to try flashing a different stock kernel(I use Viper1.1, my signature has a link to the thread) and using trickstermod to undervolt the cpu. The improvement is minimal but every little bit helps. On average I get a full 24 hours in between charges and usually charge once it hits 10-15%. And it only takes about 60-120 minutes to fully charge.
However the lgog is also very fickle, what works for one may not work on another, even if it's the exact same model. Many people have reported the same security bootloop soft brick after deleting google apps for instance, but I deleted(not frozen or disabled) google apps just fine. The only ones I have on my phone are play store and google search and I'm still on stock zvc.
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
And based off what your saying would you not recommend doing LGNPOST again?
xSTUDDSx said:
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
Click to expand...
Click to collapse
Ok well it seems like you follow good battery techniques. Maybe try LGNPSTing back to a full stock zvc(or zvb and then updating to zvc) and charge it to 100%(let it sit at 100% while still charging for 15 mintues or so) before rerooting and unlocking. I would probably also copy your internal to your pc and wipe everything in recovery before doing LGNPST just to make sure it is a completely clean slate. I added an edit in my post above as well.
I had a strange issue a few weeks back where I tried overclocking my cpu with AK kernel - my battery was at 99%. My phone shut off and wouldn't come back on, just had a red blinking light. I later found out it was an issue with AK. I charged it for a few minutes and luckily was able to get into TWRP. The strange part was that when I did get into TWRP my battery read 0%, I did a full wipe and restored my backup, then my battery read 99% in TWRP. It's a different issue from yours but makes me think that it's possible that your softbrick and LGNPSTing affected it somehow.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
xSTUDDSx said:
And based off what your saying would you not recommend doing LGNPOST again?
Click to expand...
Click to collapse
I honestly have not had or heard of any issues with LGNPST and battery performance. Anytime Ive had to use LGNPST with a full stock .bin, it essentially set my phone back to factory condition, battery performance included. However since this all happened when you did this, maybe try flashing another rom first, even a stock based one and leave LGNPST as a last resort. Just make sure you read the instructions for whatever rom you decide to test and always do a full wipe(data, cache, dalvik and system) before flashing.
EDIT: Sorry if it seems like I gave you conflicting info, if it was me I would probably be weary of using LGNPST again, personally. But if I tried flashing other things, different recoveries, roms and still had the same issue, maybe it was just a slightly messed up LGNPST flash and would try it again as a last resort.
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
xSTUDDSx said:
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
Click to expand...
Click to collapse
After holding volume up + power, you then will hit volume down twice and power again. Once in TWRP it is very easy, there is an install button, wipe button, etc. Hit the backup button, pick all available options and then do a backup and reboot into your OS. From there, download a rom(optimus DE is a great stock rom) to your internal and you will probably need gapps as well(depends on rom but almost all of them need gapps or you wont even have the play store - just read the install instructions of the rom). Go back into recovery, This is under the advanced wipe button in the wipe menu - wipe everything except internal storage(if you wipe internal you will lose your backup, pictures, music, etc) and then go to install, pick the rom.zip and flash that, then pick the gapps zip and flash that as well.
Also keep in mind that if you flash an AOSP or CM based rom, the file system will be different. Our internal storage is /data/media but for AOSP based it is /data/media/0. So say for instance you make a backup in TWRP of your stock then flash an AOSP rom, it will look as if your internal is gone as well as your backup. You will just have to use a root file explorer to copy the /data/media/TWRP folder to /data/media/0/TWRP and then you will be able to restore your backup from TWRP.
If you are just going to try LGNPST again then when you get into TWRP pick everything including internal and turn the phone off and put the phone into dl mode(you know what you are doing from there).
One final note, if you are using current FreeGee to unlock then you are most likely using the updated TWRP. Some people have had SEVERE issues with it, for others it works just fine. You need it to install any rom based on Android 4.4 but I personally use TWRP 2.5.0.0 which will flash stock to Android 4.3 roms just fine and it is rock solid stable. So unless you are planning on installing a kit kat rom, I would first download the TWRP 2.5.0.0 zip found here to your internal, go into twrp, pick the install button, find the .zip file and install that, then go to reboot in TWRP's main menu and choose recovery instead of system. TWRP should now read 2.5.0.0.
Sorry for the books I'm writing here but I think it's always best to be thorough!! And I haven't slept in about 30 hours so I am a bit scatter brained.
I have been using fulmics for a long time now. I live somewhere where the temperature is always something around 17-25 degrees on summer and never had an overheating problem. Now, I'm on holiday somewhere hotter (canary islands) and the 30-ish temperatures are causing my phone to reboot if i take a couple of pictures or if I open apps like pokemon go. I think this has something g to do with heat because back at the hotel, I don't have these issues at all. Even when i perform the same tasks at night, the phone does not reboot.
Now, I can't remember if I chose the stock or the the thermal throttle values upon installation but I'd like to ask, which would be the best option to avoid this issue and also, any other advice you could give in order to mitigate this issue. I asked on the fulmics thread over at xda but the mods locked it because some asshole didn't stop asking the dev for Etas. Screw that guy.
Any help would be welcome! Thanks!
Hi, there will probably be an update to fulmics 6.0 which should solve overheating problems. I'd recommend for you to move to Cloudy G3 2.5 or XenonHD with aCC kernel just for now.
I also have problems with heating. When the phone is at direct sunlight for some time it become irresponsible. I mean it don't reboot but message pop up "system ui stopped ....." and screen lock. I wonder if fulmics ROM is the reason for that. As far as I remember upon installation I choose stock settings, kernel.
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
My G2 acted like this when the battery died. Its a sure sign
GFXi0N said:
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
Click to expand...
Click to collapse