Related
Obsolete
This workaround was only relevant some time ago while custom kernels did not yet have updated sources from Samsung to work on 4.0.4 ROMs. This is no longer the case so this info is completely irrelevant now.
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix for it.
Installation
Just take the CWM zip file and apply it on your ROM. It will leave a backup of the 2 files that will be replaced.
Removal
The Restore zip can be "installed" to remove the patched files and put back the original ones that were kept on your device.
Tested and working both for Camera preview and Video playback, on XWLPM.
Note: This is a temporary fix until the kernel devs have enough information to properly update their code, and when that happens this fix can be uninstalled.
Heyy Tungstwenty, another great fix by you!
Well done, it works great! Now also videoplayback works fine with siya on 4.0.4!
Now the only thing left not working on 4.0.4 with Siya is the bluetooth...
Thanks again!
he he he go 4.04 gooo!
Thanks man.
Hi @Tungstwenty
Time to go OUT of stock Kernel XWLPM and move to Siyha Kernel, thanks a lot my friend...
Cheers
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Thanks for the tips!
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
Click to expand...
Click to collapse
I actually had that happen to me when i was on Neat Rom. Don't know what caused it but I ended up switching roms.
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Click to expand...
Click to collapse
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Tungstwenty said:
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Click to expand...
Click to collapse
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
The Undertakerr said:
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
Click to expand...
Click to collapse
I don't think it's offtopic
This is indeed very strange, but here's a possible explanation:
The custom kernels (Siyah, Dorimanxx, ...) each have their own tweaks; they're not exactly the same. While they might share lots of common changes and improvements, they do have different things hence the word "custom".
There's a possibility that the sequence of events to make the camera work is contained not only on the binaries (the ones in the zip file I posted), but also on some cached data that was already picked up when you first ran the camera app, which invoked a service, which in turn invoked a library, etc. Later, when reopening the camera, now with the "fixed" binaries, there might still be bad data that a particular kernel is not expecting. Even if you came from Siyah when initially running the camera app, the original libraries might have cached strange data that the kernel will no longer recognize even after the binaries are now in line with the kernel. And another kernel might have code that is lenient enough to still work with it.
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
thanks a lot for the camera fix now I can use official 4.0.4 more often with my favourite kernel - Siyah
Tungstwenty said:
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix
Click to expand...
Click to collapse
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Click to expand...
Click to collapse
I have worked on this fix using XWLPM as a secondary ROM (I'm still on XWLPG) but this should work both for LPM and LQ5.
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Sent from my GT-I9100 using xda app-developers app
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
cdaarif said:
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Click to expand...
Click to collapse
This is just a fix for Camera + Video. I know bluetooth is also not working but as I posted before, I tried to fix it as well but don't think it's doable without changing the kernels. Kernel devs will have to find a way to fix it.
Working bluetooth on LPM with stock Kernel and camera with your hack.
marbutina said:
Working bluetooth on LPM with stock Kernel and camera with your hack.
Click to expand...
Click to collapse
If you're using stock kernel you can (should) uninstall my camera/video hack. It's only needed for custom kernels.
Thanks.
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
hardcore said:
Well whaddaya know...
K3-9:
- Bluetooth now works for 4.0.4 ROMS
Click to expand...
Click to collapse
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Krendelrus said:
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Click to expand...
Click to collapse
Thanks for the above info!
Best to repeat this message in the Siya thread, and/or send Gokhanmoral this info by PM. He might be able to use Hardcore's sources to fix bluetooth in Siya kernel...
Edit: I see you allready did that. Thanks again! Maybe soon we can have working bluetooth with a custom kernel, that would be great!
**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.1+v33.2 ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far).
**Where you can use it ?**
Tested so far on Omega v33.1, confirmed working on Omega v33.2 as well including some other XXELK4 stock/custom based ROMs
Not needed for Omega >=v33.3 or patched stock ROM XXELK4
**Just press THANKS if it worked**
Thanks to Omegas Team.
All you need to do to fix is flash a different kernel
Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Incorrect. Lots of people running 4.1.2 on various kernels and still facing the same problem. Myself included having tried 3 different kernels.
Sent from my GT-I9300 using xda app-developers app
Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Not helping. Already tried. This is nearly annoying like the hello hello bug. Not all got it and every phone needs a different fix.
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member
Chris_84 said:
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Click to expand...
Click to collapse
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
*sorry* I just flashed also another modem just prior to that fix, see 1st post...however when I flashed different modem before I was trying to fix GPS issue, it didn't help at all
shaarky said:
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
Click to expand...
Click to collapse
Don't know for sure but think maybe the video fix who install the old libs brake GPS again but I'm not sure. As I wrote in omega thread. After dirty flash it works perfect even with custom kernel and after installing the video fix it brake down again.
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member
It's working so far.
I haven't flashed fix video but installed siyah so sooner or later I'll need the video fix.
I'll let you know how it goes.
Sent from my GT-I9300 using xda app-developers app
shaarky said:
**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.x ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far). Tested so far on Omega v33.1 only, but should work on v33.2 as well including some other XXELK4 stock based ROMs
**Report and let others know if this helps or not and/or press THANKS**
Thanks to Omegas Team.
Click to expand...
Click to collapse
Tried all what you have said you had tried and also no luck - still having GPS problems.
Installed the fix.
Before installation, using Waze, I used to get a fix within 5 seconds, and then I used to lose the signal after 3-5 Mins. max.
After installation - got a fix same within ~5 secs, and I kept it on for about 10 mins and I had no signal loss.
I will try it further on my way home (about 20-30 min drive) and post results.
Thanks alot - hope this might just do it!
***EDIT***
Drove 20-25 mins home - all working fine.
Will do more testing tomorrow, but looks like this is the fix, for me anyhow.
Big thanks!
Work for me.
This fix work for me. Test during 40 min of navigation .I´m on Omega 33.1 with video fix and Kernel Perseus 26.1
Will test again on the end of the day.
is the "use wireless network" is turn on on your rom??
or turn off??
not working for me on omega 33.2 + stock kernel
liad1981 said:
is the "use wireless network" is turn on on your rom??
or turn off??
Click to expand...
Click to collapse
Is ON
Sent from my GT-I9300 using Tapatalk 2
Small report:
Today morning I use GPS (Waze and Be On Road) to navigate to my work (15km).
Lost signal every 3 - 5 minutes. Strange.
In my work I flash your fix.
Navigate (Be On Road) approximately 15km to customer and 15km to work. Working absolutely good.
Thank you.
I will test later much more and report again.
Update1: On the way home from work gps navigation (Be On Road) work like a charm. I am lucky
Update2: Today on way from home to work, working very well. Thank you. Now I vote for YES
Hi my friend. But suddenly your fix work here. Did another full wipe. Installed my usual stuff and got no fix. Then I thought I try again your zip and it works for now. Will test how long but really hope that's it.
Sent from my GT-I9300 using xda premium
i installed 33.2 with no wipe on 33.1 and i had the gps problem.
it found the first fix but after 2-3 minutes the fix isnt possible.
i did a first check with your fix and it seems to work now...tomorrow on my way to office i will give it a try
thx
How did I miss this! Going to flash and test on the way to work tomorrow...looks promising!
Sent from my GT-I9300 using Tapatalk 2
Not sure i tried this one, but just flashed it and will try in about 2 hours and will report back.
For me it's working now.. I'm on Omega 33.2 and latest Siyah
tapatalked via SGS3 on OMEGA and Motomoto00
Oke, just had my 25 minutes drive.
Flashed your zip before went on the road, double checked that Use wireless networks was enabled again, this afternoon i disabled it and gps worked again.
And from work to home, not one single drop off gps noticed using Sygic.
Also watched carefully to Sygics speed meter and it was corresponding with the speed i actually drove, not going from 30 to 100 i saw yesterday before gps broke down.
Looks your file did it for me.
Deleted
[Help & Temporarily fix]can't use wifi / usb / bluetooth tethering when data is on
hi
I have this problem for a long time but i found some new things about this problem that want to share it with everyone , so i decide to create a new thread , so you can share your ideas to fix it also i found a way to use it Temporarily
my device info:
lt18i , android 4.0.4 , build number 4.1.B.1.13
rooted , bootloader unlocked
installed UHDv4 ROM and UHDv4.8 MOD with LuPuSv16
who have this problem ?????
my problem is :
i want to use (wifi/usb/bluetooth) tethering , everything is good just after removing wifi modules from lupus menu ( just for a minute )
after a while i can't use wifi tethering when data is enabled
*****The only thing that I did not notice, it was option 3 , you will read it in the following*****
so i decide to use another kernel : so i should to flash a wifi module from CWM but after boot up i don't have any wifi but (usb/bluetooth) tethering works good
i also tried to remove lupus wifi modules before flashing new kernel
So I went back to LuPuS
***** i found a new feature i should do the following to make wifi hotspot works when data is enabled ******
i have 3 options:
1 = first enable data then enable wifi hotspot ***in other words*** enable wifi hotspot when data is enabled = works
2 = first enable wifi hotspot then enable data ***in other words*** enable data when wifi hotspot is enabled = this will make the problem
i should just do option 1 to make it work , if i do option 2 , the problem starts and i can't make it work with option 1
after that the problem starts :d i can't use it again to solv the problem , for example
but i found a new option for make it work
3 = enable data then reboot ***in other words*** reboot when data is enabled , without removing wifi modules
if i do option 3 , i can use option 1 again without problem
uuuhhhhhh so strange problem
i think my phone have problem with set the internet ip address for tethering
here is the logcat when i did option 2 and wifi hotspot don't work with option 1 :
View attachment 2013-08-18-09-39-35.txt
here is the logcats when i did option 3 and wifi hotspot work with option 1 :
View attachment 2013-08-18-09-42-50.txt
here is the logcat when i did option 2 and wifi hotspot don't work with option 1 :
View attachment 2013-08-18-09-44-04.txt
Never heard about this problem !
I have this problem at Legacy 4.2.2 and 4.3.
Sent from my Xperia Arc S using XDA Premium 4 mobile app
Prider555 said:
I have this problem at Legacy 4.2.2 and 4.3.
Sent from my Xperia Arc S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what about option 1 & 3 , can they help you ? do you think it is from "set the ip address ?
EAGLEBOOY said:
what about option 1 & 3 , can they help you ? do you think it is from "set the ip address ?
Click to expand...
Click to collapse
When I use option 1 & 3 then is all working fine. I dont really now what this mean "set the ip address". Im not a developer!
hi , please someone help
devs please say something , just what you know and ways that can help
please help , thanks
finaly the problem is fixed now
hi
finaly the problem is fixed now
you can't solv it by changing a rom or kernel , you should flash a FTF with flashtool to solv it
here is what i did :
i flashed LT18i_4.1.B.1.13_Vodafone DE.ftf with flashtool and it works now
after that i flashed LuPuS kernel and UHD ROM and UHD MOD
it is still works very good , now i can turn on wifi hotspot when data is enabled whithout any problem , everything is good now
i suggest you flash LT18i_4.1.B.1.13_Vodafone DE.ftf For increasing system and data memory for Arc user and latest BB
Hi I think I find how to fix it
You can flash a ftf via flashtool to fix it but this way will wipe all your data
we can flash a ftf but without flashing system, kernel, baseband and without wipe data
You can choose which one you want to flash
So select what you don't want and leave unselected which you want in flashtool
Sent from my LT18i using Tapatalk 2
hi EAGLEBOOY,
I have moved your thread from General section to Q&A, Help & Troubleshooting section. This maybe useful to others so if it is in Q&A it will be easier to find. Please use the correct sub-forums when posting.
--wedgess
Forum Moderator
Hi all, can someone help me pls?
When i install any not stock based rom (CM11, Mokee, Carbon) my e975 doesn't goin deepsleep.
Now i'm on Artmod 5.3 and deepsleep works.
I've tried to flash only rom and gapps, installed only better battery stats and the phone doesn't go on deep sleep to.
I've the suspendbackoff wakelock on kernel wakelock and com.google.android.gms on Allarms.
I don't understand where the problem is.
Tx for any help.
I've seen that i have a RILJ wakelock, it's a baseband related problem i think, what can i do for solve that?
https://docs.google.com/file/d/0B-2RJW9ppzwjdkFNOHA0OXZJUEU/edit?usp=docslist_api
paolinhos said:
https://docs.google.com/file/d/0B-2RJW9ppzwjdkFNOHA0OXZJUEU/edit?usp=docslist_api
Click to expand...
Click to collapse
It clearly shows that your phone is in deep sleep state 3 minutes out of 10 (that's your stats period). Is this taken on ArtMod ROM? RILJ wakelock is only 1 minute (12.7% of total stats period), so is that really a problem? Are you trying to improve your deep sleep on ArtMod, or solve the problem with non-stock custom ROMs?
kt-Froggy said:
It clearly shows that your phone is in deep sleep state 3 minutes out of 10 (that's your stats period). Is this taken on ArtMod ROM? RILJ wakelock is only 1 minute (12.7% of total stats period), so is that really a problem? Are you trying to improve your deep sleep on ArtMod, or solve the problem with non-stock custom ROMs?
Click to expand...
Click to collapse
no i'm on mokee caming from artmod, the 3 minutes that phone is in deepsleep are when i've switch on it in airplane mode, then i switch off airplane mode and it never goes in deepsleep mode.
if i switch on the phone withouth airplane mode it never goes on deep sleep.
This only succed on non stock roms.
Basically if i'm in non stock based rom my phone never go into deepsleep mode.
I've tried to flash a clean rom CM11 and only install better battery stats and i see however the phone never go in deep sleep, if i switch on the phone normal way and then i put it in aereo mode it doesn't go in deep sleep mode to.
Only way to mke it goes on deep sleep is to restart it on airplane mode.
Sorry i've bad english, i hope you understand me.
Ahh, OK. It's pretty clear now, thanks!
Sorry, I don't have much experience with non-stock ROMs, so I am afraid I wouldn't be able to help you much with this... Hopefully, someone can give you some ideas. One thing I can suggest is to look at some apps to force deep sleep mode. For example, DS Battery Saver. Might not be the best approach (better to resolve the underlying problem), but it did help me when I was trying to improve my battery life...
kt-Froggy said:
Ahh, OK. It's pretty clear now, thanks!
Sorry, I don't have much experience with non-stock ROMs, so I am afraid I wouldn't be able to help you much with this... Hopefully, someone can give you some ideas. One thing I can suggest is to look at some apps to force deep sleep mode. For example, DS Battery Saver. Might not be the best approach (better to resolve the underlying problem), but it did help me when I was trying to improve my battery life...
Click to expand...
Click to collapse
Already tried ds battery saver and du battery saver, no one help me...
i'm really afraid about this problem because before installing Artmod i've no problem with cyano based rom...
I don't think it's problem related to artmode however.
Pls can someone help me???
EDIT: I've installed the new Carbon Rom with jolla kernel and it seems to go on deep sleep..
I attach a quick better battery stats report if someone can help.
I've tried to install a 10c baseband before flash Mokee rom, not usefull..
Now i try to flash another kernel.
I don't understand why in based stock rom the phone goes in deepsleep and with CM11 based no.
I see on gee or geeb based cm11 rom deepsleep works
need help guys
my device battery drain when wifi on without install any apps and without using the phone
wifi traffics indicators always active and device always wake never go to sleep
but if i turn wifi off device sleep well and no battery drain
that happen with me with all lollipop roms
i hope someone help me here
MaZaGnGy said:
need help guys
my device battery drain when wifi on without install any apps and without using the phone
wifi traffics indicators always active and device always wake never go to sleep
but if i turn wifi off device sleep well and no battery drain
that happen with me with all lollipop roms
i hope someone help me here
Click to expand...
Click to collapse
Which rom & kernel are you on?Be little more details.Eventhough not insatlling apps or surfing web while wifi on,little bit of battery drain because of wifi on..Try dirrent kernel
crazykas said:
Which rom & kernel are you on?Be little more details.Eventhough not insatlling apps or surfing web while wifi on,little bit of battery drain because of wifi on..Try dirrent kernel
Click to expand...
Click to collapse
5
Android Revolution HD 41.0
ViperOneM8 4.3.0
SkyDragon v8
i flash all this roms full wipe and after 1st boot and finished the setup i reboot the device and as i say in the OP
im unlocked and s-on and always using the kernel come with the rom