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..
Related
Hello! Long time lurker, first time poster. I finally got around to making an account.
So, I'm having an issue when applying Da_G's overclocking kernels (Here).
The issue proliferates when I go into CWM and apply the AT&T .42 kernel and the 1.83ghz overclock script from the recovery menu. Basically, after cleaning the cache and the dalvik cache, I apply the .zips of the .42 kernel and the script, and reboot, and then I get a restart cycle that ends after the Samsung screen. I went ahead and did a full wipe of the phone, restored via ODIN to stock, and then tried flashing it again and this time I got to an "Android" logo followed by the same power cycling (this time with the camera LED flashing).
The strangest thing is that before I took my first Skyrocket back for dead pixels, I had gotten it running just fine before. But the last two I've had won't do it and get stuck in the aforementioned restart cycle.
I decided that it really wasn't worth the risk of bricking my phone (since I just got out of my 30 day warranty and had to take the phone back twice for dead pixels and the phone not turning on one day), and I guess in the end I'm just curious as to why I was having this issue. I guess if it's something stupid I'm doing, I'd go ahead and do it (especially since I have plans for that performance boost).
Anyways. Feedback appreciated.
The 1.83 isn't very stable that's what's causing the problems. Go one step down on the script
Alright, I'll try it right now. Maybe it was a fluke that it worked the first time.
EDIT: It booted up, but, then it shuts off when I open CPUTuner, but, they're talking about that in the official thread. Thanks!
1.83 is not stable and 1.78 and 1.72 are most stable with oc.
Sent from my SAMSUNG-SGH-I727 using xda premium
After running it for a few hours, now I'm getting Sleep of Deaths. I really want to speculate that it's the .42 version that I'm running, but, I haven't tinkering with it enough. I think I'll try downgrading to .3 to see if that fixes the issues, as that's what people seem to be saying is the most stable, and it's the one I ran before.
And if that doesn't work, eh, I'll flash back to stock kernel. Thanks guys.
Edit: Yeah, still getting SOD, flashing stock.
Did you try deleting your modules folder?
I had the same problem, 'cept I cranked it to 1.89ghz. I just flashed the stock att kernel and everything worked fine
Sent from my SAMSUNG-SGH-I727 using xda premium
Hi
What is the best custom Rom with HC ? I want to remove ICS till it gets better.
I tried searching but id prefer advice before i start experimenting around, plz help
Thanx
I'm also looking for a Nvflash back to HC just before ver ICS came out .....anybody have it please.
Sent from my Transformer TF101
JohnM109R said:
I'm also looking for a Nvflash back to HC just before ver ICS came out .....anybody have it please.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Guys - even if it's an older version of Hneycomb in NVFlash format, it will still help...
Here is what I'd recommend (as it worked perfectly for me) - it 10 easy steps!
1. Download this stock Honeycomb image in NVFlash format. It's not the latest version of Honeycomb, but it really doesn't matter, becuase once you install and root it, you are just going to install CWM recovery and install a custom Honeycom ROM over top of it anyway (which IS based on the latest version of Honeycomb):
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
2. Download rootkit for above version of Honeycomb:
http://www.4shared.com/rar/-IYDraGZ/Brkroottoolkitv71.html?
3. Download CWM Recovery.
4. NVFlash the image downloaded in step 1.
5. Boot Honeycomb (skip all configurations!) and then root it using the rootkit downloaded in step 2.
6. After Honeycomb is rooted, install CWM Recovery downloaded in step 3.
7. Download Revolver 3.11 and 3.11.1 patch
8. Install Revolver 3.11 via CWM.
9. Install Revolver 3.11.1 patch via CWM.
10. Enjoy Honeycomb stability again!
Or something close to that....
EDIT: Added links to NVFlash'able ROM and root kit.
The problem with HC revolver was that it took to long to boot up. Prime ROM did not have the same problem.
sdfghi said:
The problem with HC revolver was that it took to long to boot up. Prime ROM did not have the same problem.
Click to expand...
Click to collapse
Why is the boot-time such a big deal? I never reboot my device (at least now that I'm not on ICS anymore!), so the boot-time is almost meaningless...
I guess if you turn your device off every time you use it, that would be a pain.
Probably the reason that Revolver takes longer is becuase of what it's doing at boot-time (optimatizations, etc)...
Sent from my Transformer TF101 using Tapatalk
If you are willing to root and flash custom roms, first try a custom ICS rom in combination with a custom kernel instead of going back to honeycomb.
A lot of people got good results by using guevor's latest kernel.
Yeah that's what I'm trying to decide cause I need my pad daily use with not to much reboota and sods
Sent from my HTC HD2 using xda premium
I have already rooted my TF and made ready for a custom rom, but it seems that there is a fix available
[Kernel] ICS test (OC, UV) (test13) V9.2.2.3
Between HC and ICS, I thing ICS is far better (except for the stability issues), so I will give this a shot first before downgrading to HC.
As per my question on this thread HC Revolver sounds as a choice to many XDA members, so plan B should be this one.
some issues
Is revolver more stable now? I could never get the vga adapter to work. or it simply not freezing. This was last november.
If you're willing to go through the trouble to downgrade, you may as well just flash guevors test kernel or the TastyMehIcs kernel (in my sig) to fix the ics problems. I've had no problems on ARHD/Megatron with tastymeh 1.0 at all.
Edit: just looked at my uptime (I don't ever turn off really) 232 hours since last turnoff. That's stable enough for me!
I wanna know what good HC ROMs are out there too.
SoD doesn't happen to me at all, but I'm sick of the graphical glitches that are present throughout the ICS ROMs. People say it's only when you press recents - not true for me. I get it pressing recents, browsing youtube, in the nvidia apps, playing games, sometimes at the home screen, settings menu, etc.
It's very brief, but at the frequency it occurs, it's annoying. I want to know if it's present in HC as well. When I was on HC I never noticed it, but my device was on HC for maybe a total of two hours, so idk. The screen rotation thing is kinda annoying to. You turn the device, screen goes black for like a second, then it does the rotation animation. Things like that bother me cause it's not like that on my phone, even when I run ICS on that and it's not even receiving an ICS update.
I2IEAILiiTY said:
I wanna know what good HC ROMs are out there too.
SoD doesn't happen to me at all, but I'm sick of the graphical glitches that are present throughout the ICS ROMs. People say it's only when you press recents - not true for me. I get it pressing recents, browsing youtube, in the nvidia apps, playing games, sometimes at the home screen, settings menu, etc.
It's very brief, but at the frequency it occurs, it's annoying. I want to know if it's present in HC as well. When I was on HC I never noticed it, but my device was on HC for maybe a total of two hours, so idk. The screen rotation thing is kinda annoying to. You turn the device, screen goes black for like a second, then it does the rotation animation. Things like that bother me cause it's not like that on my phone, even when I run ICS on that and it's not even receiving an ICS update.
Click to expand...
Click to collapse
Be patient - we're beta testing a beta release now (.24) and it seems that the graphical glitches are fixed (I KNOW the recent-apps "diagonal tearing" is fixed at least) - I've never noticed any other glitches, to be honest...
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
Guys - even if it's an older version of Hneycomb in NVFlash format, it will still help...
Here is what I'd recommend (as it worked perfectly for me) - it 10 easy steps!
1. Download this stock Honeycomb image in NVFlash format. It's not the latest version of Honeycomb, but it really doesn't matter, becuase once you install and root it, you are just going to install CWM recovery and install a custom Honeycom ROM over top of it anyway (which IS based on the latest version of Honeycomb):
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
2. Download rootkit for above version of Honeycomb:
http://www.4shared.com/rar/-IYDraGZ/Brkroottoolkitv71.html?
3. Download CWM Recovery.
4. NVFlash the image downloaded in step 1.
5. Boot Honeycomb (skip all configurations!) and then root it using the rootkit downloaded in step 2.
6. After Honeycomb is rooted, install CWM Recovery downloaded in step 3.
7. Download Revolver 3.11 and 3.11.1 patch
8. Install Revolver 3.11 via CWM.
9. Install Revolver 3.11.1 patch via CWM.
10. Enjoy Honeycomb stability again!
Or something close to that....
EDIT: Added links to NVFlash'able ROM and root kit.
Click to expand...
Click to collapse
I wouldn't trust a rootkit , especially one hosted on 4shared. Just saying. A link to the original post would be nice.
---------- Post added at 02:50 AM ---------- Previous post was at 02:48 AM ----------
jtrosky said:
Be patient - we're beta testing a beta release now (.24) and it seems that the graphical glitches are fixed (I KNOW the recent-apps "diagonal tearing" is fixed at least) - I've never noticed any other glitches, to be honest...
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I haven't noticed these issues on the ROMs I've tried. And revolver is by far the best HC based ROM.
Jamesyboy said:
I wouldn't trust a rootkit , especially one hosted on 4shared. Just saying. A link to the original post would be nice.
Click to expand...
Click to collapse
Actually, that 4shared link is the link from the original post - I just copied the link here... I've personally used it and it's fine...
Sent from my Transformer TF101 using Tapatalk 2
I2IEAILiiTY said:
I wanna know what good HC ROMs are out there too.
SoD doesn't happen to me at all, but I'm sick of the graphical glitches that are present throughout the ICS ROMs. People say it's only when you press recents - not true for me. I get it pressing recents, browsing youtube, in the nvidia apps, playing games, sometimes at the home screen, settings menu, etc.
It's very brief, but at the frequency it occurs, it's annoying. I want to know if it's present in HC as well. When I was on HC I never noticed it, but my device was on HC for maybe a total of two hours, so idk. The screen rotation thing is kinda annoying to. You turn the device, screen goes black for like a second, then it does the rotation animation. Things like that bother me cause it's not like that on my phone, even when I run ICS on that and it's not even receiving an ICS update.
Click to expand...
Click to collapse
Turns out a lot of my issues were eliminated by flashing revolver and the androidhd builds,.probably cause they're essentially the stock ICS build.
Sent from my Transformer TF101 using Tapatalk 2
Thanks for guide.
I just found out I have a b50, and tried NVFLASH of ICS... worked for maybe 2-3 hrs, thought there was hope... and now it just froze playing music.
If this thing cannot even play music without glitching, whats the point really at all?
If this HC downgrade (and stay there) doesn't work, I'm selling this ASAP.
Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium
galamdring said:
Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'm thinking that there must be something off in the bootloader. I'm hesitant to go playing with it since that is a quick road to bricking. I might dissect the boot.img that is included in the cm10 zip. I'm thinking there is a missing module, or something similar.
Any input would be appreciated.
New update. I was able to get back to CM10. I had forgotten to wipe data. Thats what I get for flashing when half asleep.
Still trying to understand what happened to stop my cardock from working. Charging in the dock works fine, but it doesn't start car dock mode, or push audio through the usb. I'd really like to get that working again.
Hello everyone, I am having a problem with my tf101 running cyanogen mod 10 (4.1.2). When I leave it inactive for about 30min it will just randomly shutdown. I have had cyanogen 10 on the tablet for about 2 days before this started happening and it was running perfect then. If anyone has an answer for this problem it would be appreciated.
Switch to the teameos ROM. It's much more stable.
Sent from my Galaxy Nexus using Tapatalk 2
AnthraX- said:
Hello everyone, I am having a problem with my tf101 running cyanogen mod 10 (4.1.2). When I leave it inactive for about 30min it will just randomly shutdown. I have had cyanogen 10 on the tablet for about 2 days before this started happening and it was running perfect then. If anyone has an answer for this problem it would be appreciated.
Click to expand...
Click to collapse
I have noticed this on my tab too. usually when i turn it back on the battery is at 49-50% each time. Maybe it's a setting? Or maybe it's just some weird malfunction.
AnthraX- said:
Hello everyone, I am having a problem with my tf101 running cyanogen mod 10 (4.1.2). When I leave it inactive for about 30min it will just randomly shutdown. I have had cyanogen 10 on the tablet for about 2 days before this started happening and it was running perfect then. If anyone has an answer for this problem it would be appreciated.
Click to expand...
Click to collapse
Try going to the development page and download the newest nightly. Make sure there is not another zip inside the zip you download. You will get SN error if you do. Put it on the root of an sdcard (microsd), place it into the transformer, and boot up clockwork mod and select "install update.zip" or whatever it is. Hope this helps! It worked for me. You should not have to a factory restore. Only do that if it will not boot up. BEFORE YPU DO ANYTHING MAKE A BACKUP IN CWM! Restore if needed. Also clear cache and dalvik cache.
Good luck,
Jake
I've found that most roms since ICS have this problem. I think its the SoD (sleep of death issue).
I'm currently running Rayman's CM10 V6 which I haven't updated for a while and that still has the issue.
You can fix it by using "wakelock" from the store, but you will loose some battery life overall as it keeps the CPU active.
I need to spend some time updating my stuff, but apart from SoD the rom I'm using works great..
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