So, this happened to me for the first time last night...My phone had charged 100% and so I removed the charger..Idk for some reason the battery drained overnight in about 4 and a half hours..when I woke up and went to check some notifications, I also found out some very very serious ghosting, not instant ghosting, the long lasting one...I don't really remember much about last night (was high) but I'll post some screen shots.
Look near the CPU in the top center of the screen..there's a small whitish circle which is a Snap from CNN on snapchat..and its not going away..not visible on white surfaces though.
Oh and BTW I'm on Sultan's ROM on 5.1.1 latest update (was stable until November, now some FCs and random reboots and whatnot, will migrate to Oxygen OS 2.2.0 by PMehra) with AK kernel.
go to mashmallo instead
#sychrome# said:
go to mashmallo instead
Click to expand...
Click to collapse
I did try Sultan's Marsh..But too buggy for me..suggest me a good ROM (with support for custom kernels please )
Xno3 said:
I did try Sultan's Marsh..But too buggy for me..suggest me a good ROM (with support for custom kernels please )
Click to expand...
Click to collapse
i have very stable check for correct twrp version and firmware and no su
Xno3 said:
So, this happened to me for the first time last night...My phone had charged 100% and so I removed the charger..Idk for some reason the battery drained overnight in about 4 and a half hours..when I woke up and went to check some notifications, I also found out some very very serious ghosting, not instant ghosting, the long lasting one...I don't really remember much about last night (was high) but I'll post some screen shots.
Look near the CPU in the top center of the screen..there's a small whitish circle which is a Snap from CNN on snapchat..and its not going away..not visible on white surfaces though.
Oh and BTW I'm on Sultan's ROM on 5.1.1 latest update (was stable until November, now some FCs and random reboots and whatnot, will migrate to Oxygen OS 2.2.0 by PMehra) with AK kernel.
Click to expand...
Click to collapse
You do realize AK kernel despite using anykernel isn't in line with Sultans latest changes to the ROM & kernel? Either way your camera seemed to have held a wakelock and drained your battery
Sent from my A0001 using Tapatalk
Renosh said:
You do realize AK kernel despite using anykernel isn't in line with Sultans latest changes to the ROM & kernel? Either way your camera seemed to have held a wakelock and drained your battery
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
That's what I thought after seeing the qcamera process in battery stats. Thanks for the confirmation! going to flash Sultan's Latest Marsh...last time I flashed it, the DPI settings were causing reboots and also random freezes plus I like stability so I flashed back to 5.1.1...hope the Feb update has got rid of it.
Plus did you notice the ghosting image? It's gone now but I was really worried!
#sychrome# said:
i have very stable check for correct twrp version and firmware and no su
Click to expand...
Click to collapse
Yea I am going to flash 6.0.1 now using 2.8.6.0 TWRP. Hope it isn't as buggy now because IMHO Sultan's Roms are the best!
I have the same 4hr battery life on my OPO. upgraded to latest CM12 but wanna go back to old Android Kitkat CM11 if i can.
Xno3 said:
Yea I am going to flash 6.0.1 now using 2.8.6.0 TWRP. Hope it isn't as buggy now because IMHO Sultan's Roms are the best!
Click to expand...
Click to collapse
upgrade ur unofficial twrp to 3.0 unofficial it solved many problems with me
Xno3 said:
So, this happened to me for the first time last night...My phone had charged 100% and so I removed the charger..Idk for some reason the battery drained overnight in about 4 and a half hours..when I woke up and went to check some notifications, I also found out some very very serious ghosting, not instant ghosting, the long lasting one...I don't really remember much about last night (was high) but I'll post some screen shots.
Look near the CPU in the top center of the screen..there's a small whitish circle which is a Snap from CNN on snapchat..and its not going away..not visible on white surfaces though.
Oh and BTW I'm on Sultan's ROM on 5.1.1 latest update (was stable until November, now some FCs and random reboots and whatnot, will migrate to Oxygen OS 2.2.0 by PMehra) with AK kernel.
Click to expand...
Click to collapse
Think there may have been an issue with his latest builds. I have moved away from both of his roms and went to all stock cm-12.1-20151117-SNAPSHOT and had 5 days on a charge, with a 0.6% drain/hr. I also don't use my phone much during the week, wifi on and switched to 3g. Might want to install better battery stats (you can find here on xda) and/or wakelock detector (playstore) and see what actually is killing your battery. Or just revert to an earlier build where these issues weren't present.
#sychrome# said:
upgrade ur unofficial twrp to 3.0 unofficial it solved many problems with me
Click to expand...
Click to collapse
version of twrp makes no difference, I've been using 2.8.6.0 for over a year now with no issues at all.
kenboyles72 said:
Think there may have been an issue with his latest builds. I have moved away from both of his roms and went to all stock cm-12.1-20151117-SNAPSHOT and had 5 days on a charge, with a 0.6% drain/hr. I also don't use my phone much during the week, wifi on and switched to 3g. Might want to install better battery stats (you can find here on xda) and/or wakelock detector (playstore) and see what actually is killing your battery. Or just revert to an earlier build where these issues weren't present.
version of twrp makes no difference, I've been using 2.8.6.0 for over a year now with no issues at all.
Click to expand...
Click to collapse
but yesterday I lost everything still didn't achieve my goal and After flashing .u know ?
Sent from my A0001 using Tapatalk
#sychrome# said:
but yesterday I lost everything still didn't achieve my goal and After flashing .u know
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I hear ya, been there, done that. Lost some of my files, but most were already saved on pc. I do a backup of my sdcard once a week, just in case. A month or so ago, I did a clean update to a new build of Sultan's CM13 caf rom and I was caught in a bootloop. I tried everything to solve this and had no luck. I could however flash cm13 nighlies and RR rom no issues, but as soon as I flashed cm13 caf rom, went to bootloop. Finally fastboot flashed official cm11s factory image and started fresh. Since then I have had no problems. There were a lot of other people with this issue, so there was something in his rom that was jacked somewhere. I did go back to Sultan's cm13 rom for a bit, but didn't run as good as his earlier builds, so went to his cm12 rom. After the latest upstreams from CM, phone performance started to go down hill. So, I just said the hell with it and went to stock cm-12.1-20151117-SNAPSHOT and everything is stable and running like it should. May flash a dif kernel in a day or so, but right now, everything is running fine. Like I said, I got 5 days on a charge with minimal usage as I don't use phone during the week. I don't have time to use phone when working and to damn tired after work. Think I had around 2hr SOT.
kenboyles72 said:
I hear ya, been there, done that. Lost some of my files, but most were already saved on pc. I do a backup of my sdcard once a week, just in case. A month or so ago, I did a clean update to a new build of Sultan's CM13 caf rom and I was caught in a bootloop. I tried everything to solve this and had no luck. I could however flash cm13 nighlies and RR rom no issues, but as soon as I flashed cm13 caf rom, went to bootloop. Finally fastboot flashed official cm11s factory image and started fresh. Since then I have had no problems. There were a lot of other people with this issue, so there was something in his rom that was jacked somewhere. I did go back to Sultan's cm13 rom for a bit, but didn't run as good as his earlier builds, so went to his cm12 rom. After the latest upstreams from CM, phone performance started to go down hill. So, I just said the hell with it and went to stock cm-12.1-20151117-SNAPSHOT and everything is stable and running like it should. May flash a dif kernel in a day or so, but right now, everything is running fine. Like I said, I got 5 days on a charge with minimal usage as I don't use phone during the week. I don't have time to use phone when working and to damn tired after work. Think I had around 2hr SOT.
Click to expand...
Click to collapse
good luck and I am real sad for the potential of phone.it could serving u Right but it is torturing u.its funny that though 2 same things in nature yet so much diff[emoji3]
Sent from my A0001 using Tapatalk
Related
So I installed Team Eos4 nightly build 94 with kat kernel 80b and it is great so far with only a couple odd things. Has anyone trying this had their device turn off when it it should just be sleeping? Mine will shut off if the screen goes dark for more than just a few minutes. Thanks.
Edit: i messed up. I was on the stock kernel, not kk 80b. I must have flashed the kernel first before the rom. Idiot i am. Anywho, other than that i followed all protocol set up by the developers. Am using rogue recovery. Just flashed Kat kernel 80b now, so I'll see what happens. Thanks for the replies.
What recovery are you using?
Did you wipe the caches, system and do a factory reset in recovery before flashing?
OK, it is still happening. I'm running rogue xm recovery 1.5.0 which claims to be a cwm 5 based recovery.
Same issue. If the pad sleeps for more than minute or so-- haven't done an official time-it will basicly turn itself off. Need to long press the power button to turn back on and it goes through the regular boot process. I don't think this is some sort of deep sleep mode, but not really sure.
Sent from my Transformer TF101 using Tapatalk HD
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
Thank you for your help. I guess afterward it would be necessary to go through the whole process of wiping and flashing again?
Sent from my Transformer TF101 using Tapatalk HD
I would highly recommend it.
Update: interesting experiences yesterday with the rom. Was doing fine with me at work when there was no WiFi access, but once back home it would sometimes do its little sleeping trick. I decided to wipe and re flash the room and then the kernel, but it is still happening. Will try a full factory reset and flash again.
Sent from my Transformer TF101 using Tapatalk HD
I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???
Shesakillatwo said:
I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???
Click to expand...
Click to collapse
Been messing around with things.. This issue only happens when unplugged from charger. I installed wake lock to see if that would do anything. It seems to eliminate the problem but then you have battery drain. This reminds me of an issue that occured to some people after the ICS update.
Sent from my Transformer TF101 using Tapatalk HD
frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium
just lou said:
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD
wekurtz74 said:
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
I upgraded from B143 to 93 last night just before going to bed, left the tablet on all night, and again this morning had to do the long power button hold to get the tablet booted. A minor inconvenience when stacked up against the gains the ROM gives me. Guess we'll wait for the next version and see how that goes...............
---------- Post added at 09:31 AM ---------- Previous post was at 09:21 AM ----------
One other thing I noticed in the Dev Threads. If I understood correctly, some builds are appear to be done with "Linaro toolchain", and some not. I do not even know what "Linaro toolchain" is, but if some use this and some do not, could this possibly be a reason I have issues with some builds and not others. Sorry in advance if this is a stupid question???
Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.
wekurtz74 said:
Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.
Click to expand...
Click to collapse
As an FYI, I have downloaded and installed B145 and will let you know how it goes. To add to my input here, everytime I upgrade/flash:
1. I do a Cache wipe
2. I do a Dalvik Wipe
3. I flash the ROM
4. Flash the 80B Kernel
5. I flash the GAPPS
6. I again do both a Cache and a Dalvik Wipe
7. I reboot.........
I also have the TWRP Flash script/app installed.
So, I attached my dock last night for the first time since I rooted and moved to the 4.2 ROM to check out the Battery changes for the Dock. They worked well and the ROM continues to be awesome. On going to bed, I left the dock attached and all started up fine this morning. Since having the dock attached is adding another variable, I will disconnect it before going to bed tonight and provide an update tomrrow.
Short update. Left my unit on all night and responded perfectly this morning when I tried to wake it up. B145 with the v3 Battery patch seems to be working Great!!!!!
After Several days I can report that B145 with the v3 Battery patch seems to be working perfectly for me.
Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...
landous said:
Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...
Click to expand...
Click to collapse
try the 92 kernel also and preview 150.
scott
wn1ytw said:
try the 92 kernel also and preview 150.
scott
Click to expand...
Click to collapse
I am heading this way.. will let you know how it goes.. as I have had most of the problems described in this thread over the last few days..
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Update:
Tried Elemental X, the phone reboots randomly now... And also just googled problem with Nexus 5... it seems like 5.0 and 5.0.1 have TONS of random reboot issues...? Goddamn it Google...
Do any of you have a stable ROM (stock or custom) that doesn't have random reboot issues?
Elementalx
codenamezero said:
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Click to expand...
Click to collapse
i use franco kernel 70 with stock rooted 5.0.1 with no issues. but i don't see any differences between stock and franco. neither performance nor battery life.
This Nexus 5 is just getting worst... it random reboots now.
codenamezero said:
This Nexus 5 is just getting worst... it random reboots now.
Click to expand...
Click to collapse
Sorry to hear that. Could it possibly be a hardware issue since you say it's happening to you across all software? Corrupted storage media could cause random reboots such as that.
I'm not seeing any myself, though I do reboot the phone about once a week just as a precautionary measure with L's RAM management.
Was having this issue with Stock and Custom ROMS ended up going back to KITKAT and no problems. Hopefully they will have this fixed with 5.1 that will be released soon.
Stock one is allways the best choise. You must be aware, that the stock one is build by a lot of good developers and custom ones are made by individual enthusiasts. There is nothing wrong with that, but the pure logic here speaks by itself.
Used a lot of different roms
ordered my nexus on release day, used quite a few different roms and i've never had a random reboot.
Hi guys,
Yesterday I wanted to install Carbon Rom on my One Plus One. After the installation failed ones I noticed that I maybe should also flash the CM12.1_15.05.15_modem_firmware.zip. But also with this flashed first the installation of the Carbon Rom failed in TWRP. So I decided to go back to the newest CM12.1 Nightly.
For me, yesterday, nothing went wrong with CM. I flashed cm and the pa gapps. All ran and worked fine.
Today I noticed that my battery life is really bad. At least badder that before. I lost 40% of battery in 5 hours with not much use. Maybe is deep sleep broken or so.
And finnaly I also noticed that my phone got really hot. I attached an screenshot from Aida64.
Maybe that temperatures are normal ... I havn't just Aida64 on my phone before ... But for me that temperatures look very high.
So my final question is: How can I flash back the original modem software?
Can my bad battery be caused by the other modem software?
Hopefully someboddy can help me.
Okay So I had been using CM12.1 Nightly when this first happened. After switching on my phone, within two to three minutes my phone would hang up, freeze and reboot! It used to happen all the time.
After which i downlaoded stock Cyanogen OS and flashed it wiping every partition possible. After a almost 3 hrs of use this problem started occurring again even on stock rom!
Also the gestures stop working like only music and camera gestures work and not Flashlight even if it is turned on. I read on a few forums flashing modem helps but didnt quite work out! Please help me out soon. My phone is almost unusable right now!
dwaipayanray95 said:
Okay So I had been using CM12.1 Nightly when this first happened. After switching on my phone, within two to three minutes my phone would hang up, freeze and reboot! It used to happen all the time.
After which i downlaoded stock Cyanogen OS and flashed it wiping every partition possible. After a almost 3 hrs of use this problem started occurring again even on stock rom!
Also the gestures stop working like only music and camera gestures work and not Flashlight even if it is turned on. I read on a few forums flashing modem helps but didnt quite work out! Please help me out soon. My phone is almost unusable right now!
Click to expand...
Click to collapse
What method did you use to flash the stock Cyanogen OS? Recovery or fastboot?
I first flashed 17 Build number with Fastboot! Had no good....Changed kernels to AK and Boeffla and back to stock no good
Then I downloaded the entire Stock 23 build and flashed it...no good
Help me! Please
Only if I format everything it holds stable! I formatted everything and flashed build 23 again 2 hours ago! And rebooted now with AK kernel! Lets see....Any logs u want me to submit?
EDIT: Freeze and rebooted! Same thing happens with Boeffla kernel! Though I guess I am the only one facing this issue and its not a issue with the kernel! But still I'm fastbooting the stock kernel from 23 Build now!
dwaipayanray95 said:
I first flashed 17 Build number with Fastboot! Had no good....Changed kernels to AK and Boeffla and back to stock no good
Then I downloaded the entire Stock 23 build and flashed it...no good
Help me! Please
Only if I format everything it holds stable! I formatted everything and flashed build 23 again 2 hours ago! And rebooted now with AK kernel! Lets see....Any logs u want me to submit?
EDIT: Freeze and rebooted! Same thing happens with Boeffla kernel! Though I guess I am the only one facing this issue and its not a issue with the kernel! But still I'm fastbooting the stock kernel from 23 Build now!
Click to expand...
Click to collapse
Is this happening while completely stock, or with user apps installed?
Heisenberg said:
Is this happening while completely stock, or with user apps installed?
Click to expand...
Click to collapse
I had it now...on completely stock with ak and just whatsapp installed...
dwaipayanray95 said:
I had it now...on completely stock with ak and just whatsapp installed...
Click to expand...
Click to collapse
I flashed stock boot.img from 23 build and now installing apps....so far so good!
I made a post in Reddit, but I thought it might be good to check here as well.
Basically, I'm on Fulmics 6.5. I can get about 2 hours of SOT on a good day, but other days, I'm stuck with 1-1.5 SOT. I really don't understand, because I got this phone a month ago, and I'm using new batteries (found here). I hear some people say that Fulmics improved their SOT by 1.5 hours but... if that were true for me, that means I get 0 SOT without Fulmics?
As I said in my post, I will probably reflash Fulmics next week to see if that will fix anything, but does anyone have explanations? In the few GSam screen shots I grabbed, you can see that Android System grabs at least 25% of my battery. Also, my overnight drain is really bad, considering Marshmallow ROMs are supposed to have Doze...
tdk0117 said:
I made a post in Reddit, but I thought it might be good to check here as well.
Basically, I'm on Fulmics 6.5. I can get about 2 hours of SOT on a good day, but other days, I'm stuck with 1-1.5 SOT. I really don't understand, because I got this phone a month ago, and I'm using new batteries (found here). I hear some people say that Fulmics improved their SOT by 1.5 hours but... if that were true for me, that means I get 0 SOT without Fulmics?
As I said in my post, I will probably reflash Fulmics next week to see if that will fix anything, but does anyone have explanations? In the few GSam screen shots I grabbed, you can see that Android System grabs at least 25% of my battery. Also, my overnight drain is really bad, considering Marshmallow ROMs are supposed to have Doze...
Click to expand...
Click to collapse
only way to test for sure is use a stock rom or flash back to stock.
Sent from my iPhone using Tapatalk
hyelton said:
only way to test for sure is use a stock rom or flash back to stock.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Isn't Fulmics a stock ROM? Are there stock Marshmallow ROMs available for the D850?
I went from Marshmallow to KitKat using your LG UP method. Then I used TowelRoot, TWRP Manager, and then finally flashed Fulmics 6.5. Did I mess up a step, and that's why my battery drain is so bad?
tdk0117 said:
Isn't Fulmics a stock ROM? Are there stock Marshmallow ROMs available for the D850?
I went from Marshmallow to KitKat using your LG UP method. Then I used TowelRoot, TWRP Manager, and then finally flashed Fulmics 6.5. Did I mess up a step, and that's why my battery drain is so bad?
Click to expand...
Click to collapse
You must ota update from KitKat to get stock MM. When I say stock rom I mean pure stock. Filmics is not a stock rom as there's changes etc.
I would just stat to test out stock firmware first. As if it fixes the battery drain issue then it's the rom your running or application that's installed causing it. When it comes to battery drain unless it's a hardware issue or known issue it's always on the user side of things to find out.
Sent from my iPhone using Tapatalk
hyelton said:
You must ota update from KitKat to get stock MM. When I say stock rom I mean pure stock. Filmics is not a stock rom as there's changes etc.
I would just stat to test out stock firmware first. As if it fixes the battery drain issue then it's the rom your running or application that's installed causing it. When it comes to battery drain unless it's a hardware issue or known issue it's always on the user side of things to find out.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, but I don't think I can OTA to MM because I don't have an AT&T SIM card: I am using a Cricket SIM on my D850. So the only thing I can do is reflash Fulmic, or flash something else. But that's assuming it's a software issue.
tdk0117 said:
I see, but I don't think I can OTA to MM because I don't have an AT&T SIM card: I am using a Cricket SIM on my D850. So the only thing I can do is reflash Fulmic, or flash something else. But that's assuming it's a software issue.
Click to expand...
Click to collapse
Yeah you wouldn't be able to ota update. Your best bet is to wipe and reflash your rom. Whenever you flashed your rom you wiped correct?
Sent from my iPhone using Tapatalk
hyelton said:
Yeah you wouldn't be able to ota update. Your best bet is to wipe and reflash your rom. Whenever you flashed your rom you wiped correct?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yeah, here were my specific steps (that I can remember):
-LG UP to KitKat
-TowelRoot
-TWRP Manager to install TWRP
-Wipe ALL (checked very single box in Advanced Wipe)
-Flashed Fulmics
-Reboot
tdk0117 said:
Yeah, here were my specific steps (that I can remember):
-LG UP to KitKat
-TowelRoot
-TWRP Manager to install TWRP
-Wipe ALL (checked very single box in Advanced Wipe)
-Flashed Fulmics
-Reboot
Click to expand...
Click to collapse
Yeah next step is to reflash. But also rouge apps can cause battery drain as well. Along with having location services turned on.
Sent from my iPhone using Tapatalk
hyelton said:
Yeah next step is to reflash. But also rouge apps can cause battery drain as well. Along with having location services turned on.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So it shouldn't be a battery problem? I swapped out a different battery, and drain seems bad too. Unless I have two bad batteries....?
hyelton said:
Yeah next step is to reflash. But also rouge apps can cause battery drain as well. Along with having location services turned on.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So I did a reflash.... and the results aren't looking much better.
I would suggest seeing if you can get an OEM battery to try out. If you know anyone who has a g3 as a backup phone or a spare battery, give it a try. It could be the batteries you bought.
aybarrap1 said:
I would suggest seeing if you can get an OEM battery to try out. If you know anyone who has a g3 as a backup phone or a spare battery, give it a try. It could be the batteries you bought.
Click to expand...
Click to collapse
I'm going to try this one for a week, and then I'll switch to the OEM one I bought from LG. I doubt there will be a difference though, unless I got TWO faulty batteries?