Related
Please for any Dev's who want to take a time for this phone, disable the Fast Dormancy in default or make a setting for enable and disable it...
because, this is the battery drainer based on those
http://forum.xda-developers.com/showpost.php?p=42647534&postcount=17091
http://forum.xda-developers.com/showpost.php?p=42648484&postcount=17094
read from BatteryBetterStats
or there's have any another solution for this, please write here.
I have the same problem
And then my Xperia L rarely goes into deep sleep mode. I have mine rooted, so if there is anything I can try I, please let me know.
pjssilva said:
And then my Xperia L rarely goes into deep sleep mode. I have mine rooted, so if there is anything I can try I, please let me know.
Click to expand...
Click to collapse
I try to add ro.ril.fast.dormancy.rule=0 in build.prop but it's nothing changes, it just works in sgs2..
and another method use fast dormancy toggle in playstore, but can't use it for compatibility issue..
maybe some dev's here want to help for it,,because all of system now is stable,just this issue is very frustating me..and another people too cause of battery drainer..
I just noticed this link - would you guys try it?
http://www.androidnz.net/2012/06/at-your-own-risk-how-to-disable-fast.html
pradeepvizz said:
I just noticed this link - would you guys try it?
http://www.androidnz.net/2012/06/at-your-own-risk-how-to-disable-fast.html
Click to expand...
Click to collapse
I tried the app but it says that "your device is not supported".
I may try later to reproduce the tutorial, but it is quite long and evolved and it may be very device specific. So I am not sure I can follow it successfully.
This is a major bug in my point of view. We should be loud about it so that Sony step in and try to fix it.
---------- Post added at 08:03 AM ---------- Previous post was at 07:55 AM ----------
A suggestion:
If you want to check whether your device has this bug try "Wakelock Detector" from Play Store (its a free app). After installing the app go into settings and select "Advanced mode". If you device is affected it should show "Device (or something like this, my app is in Portuguese so I am tying to translate back into English)" in th top spots (in my case it is in the top by a large margin). Clicking in this entries to show the details you'll see that "Data dormancy" is the major reason.
Also note that your device should stay most of the time Awake instead of being in Deep Sleep mode.
Finally, this problem only affects devices if you operator network does not support data dormancy. This seems case of the Vivo network in Barzil, at least where I live. If your operator supports data dormancy it is then a good thing, as it helps to save battery.
pradeepvizz said:
I just noticed this link - would you guys try it?
http://www.androidnz.net/2012/06/at-your-own-risk-how-to-disable-fast.html
Click to expand...
Click to collapse
but there is link you mentioned is success with modify the CSC file..
so, how to modify our CSC file ?
karkand said:
but there is link you mentioned is success with modify the CSC file..
so, how to modify our CSC file ?
Click to expand...
Click to collapse
There is a long tutorial there on how to manually modify the fast dormancy parameters. But you will need to unlock your bootloader first because you need to write to /system. Mine is not unlocked yet, I still creating courage to do it. I'll probably do it to better investigate this bug.
pjssilva said:
There is a long tutorial there on how to manually modify the fast dormancy parameters. But you will need to unlock your bootloader first because you need to write to /system. Mine is not unlocked yet, I still creating courage to do it. I'll probably do it to better investigate this bug.
Click to expand...
Click to collapse
just unlock ? I can do that now...yesterday I have unlock it and relock it again for back to stock from custom kernel..
but,where the tutorial,,I searching there just for Samsung devices
EDIT :
this is it http://forum.xda-developers.com/showthread.php?p=35689455 ?
I have trying this but,not found for 'fastdormancy' field in there
karkand said:
just unlock ? I can do that now...yesterday I have unlock it and relock it again for back to stock from custom kernel..
but,where the tutorial,,I searching there just for Samsung devices
EDIT :
this is it http://forum.xda-developers.com/showthread.php?p=35689455 ?
I have trying this but,not found for 'fastdormancy' field in there
Click to expand...
Click to collapse
Yes, I meant something along those lines, I believe that that post is the origin of the idea described in the Samsung section.
By doing some more research I came across to this post http://forum.xda-developers.com/showpost.php?p=40606899&postcount=38 that suggest to use
ro.semc.enable.fast_dormancy=false
in build.prop. It is for Xperia T, but at least it is a Sony device.
Can you try as your bootloader is already unlocked?
pjssilva said:
Yes, I meant something along those lines, I believe that that post is the origin of the idea described in the Samsung section.
By doing some more research I came across to this post http://forum.xda-developers.com/showpost.php?p=40606899&postcount=38 that suggest to use
ro.semc.enable.fast_dormancy=false
in build.prop. It is for Xperia T, but at least it is a Sony device.
Can you try as your bootloader is already unlocked?
Click to expand...
Click to collapse
Ok, I will give a try.
EDIT: it is not working
Solved for me
karkand said:
Ok, I will give a try.
EDIT: it is not working
Click to expand...
Click to collapse
Weird. It did work for me. I changed the configuration using Build Prop Editor , rebooted and it is working right now. No "Data Dormancy" wakes anymore. Try using this app. Note that it did work even in a locked bootloader (I haven't unlocked mine).
Obs: I tried before from the command line using setprop and it didn't work, so success may depend on how you try to edit the option.
pjssilva said:
Weird. It did work for me. I changed the configuration using Build Prop Editor , rebooted and it is working right now. No "Data Dormancy" wakes anymore. Try using this app. Note that it did work even in a locked bootloader (I haven't unlocked mine).
Obs: I tried before from the command line using setprop and it didn't work, so success may depend on how you try to edit the option.
Click to expand...
Click to collapse
oh yes, my Data Dormancy is completely gone after several restarts...
thanks mate...
but my phone keep wake up because something...you can see my post in bbs thread..
EDIT1:
But I will do some researchs for this one in many condition..
EDIT2:
@pjssilva Fail when in locked bootloader using that tool...after reboot, that property is gone...
how you apply that? please..
EDIT3:
sorry, I forgot to install busybox after rooting
now, it's edited successfully even after reboot, now I will test it
EDIT3:
sorry, I forgot to install busybox after rooting
now, it's edited successfully even after reboot, now I will test it [/QUOTE]
Great you solved the issue.
It feels great to have the phone eating only 1.5-2% of the battery an hour after this change (from 6% before).
Thank your for the tutorial too. I will help other people.
pjssilva said:
Great you solved the issue.
It feels great to have the phone eating only 1.5-2% of the battery an hour after this change (from 6% before).
Thank your for the tutorial too. I will help other people.
Click to expand...
Click to collapse
yeah after more information about Build Prop Editor,,,it need busybox installed..I use framaroot to rooting..
very great if you look for GSF and MAPS in BBS thread...I got 0.7%/hr
Yeah your welcome, I put your name in there
karkand said:
Ok, I will give a try.
EDIT: it is not working
Click to expand...
Click to collapse
Didn't worked for me also. After restart there is data dormancy wakeup again.
Xperia M2, 4.3 rooted.
I don't know if i missed something, installed build prop editor, make the changes and restarted.
The thread asks for busybox installed, i don't have busybox and i don't know if its important.
EDIT: After installed busybox, the above stayed on reboot ok.
Because fast dormancy wakelock apperared after ~12 hours after a reboot, i will wait some hours to check if it appeares again. Thank you.
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
jimbub said:
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
Click to expand...
Click to collapse
I always selected yes, jsut in case. But I made the jump to official TWRP and no longer get that nag. Maybe check that out. To me its better, esp since its 100% working now.
jimbub said:
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
Click to expand...
Click to collapse
I've been getting the same issue since rooting. Root seems to work just fine regardless (can write to /system and everything.)
From what I can tell, it's an issue with the permissions on the su binary. The permissions are rwx-r-x-r-x where as they should be rws-r-x-r-x (setuid bit set.) The easiest way to check this on your device is through the rootchecker app. You can try and manually change the permissions but they don't stick, and I haven't found anybody else with the problem or a solution.
I used to get this on twrp on my s4 and with cwm on this device as well. Always selected no and everything was fine.
Sent from my HTC6525LVW using Tapatalk
Um, you know...If it is enabled, it will limited some operation.So I want to disabled it? But how to do that?
This should help make the process easier. You'll need root. Download the apk from the provided link and you're good to go. :good:
https://f-droid.org/repository/browse/?fdfilter=selinux&fdid=com.mrbimc.selinux
I thought this was the standard way we've been doing it for months, I know I have.
@Jorge_007 ,yeah, I know this. But you know, I think it is a troublesome operation, because every time I restarted my phone I have to open this app and click that button, I think can use a script to solve it, but I don not know. because I can not find the right scrpit to do this. So, can you help me?
00various said:
@Jorge_007 ,yeah, I know this. But you know, I think it is a troublesome operation, because every time I restarted my phone I have to open this app and click that button, I think can use a script to solve it, but I don not know. because I can not find the right scrpit to do this. So, can you help me?
Click to expand...
Click to collapse
Strange, I've never had to start mine since I installed it.
00various said:
@Jorge_007 ,yeah, I know this. But you know, I think it is a troublesome operation, because every time I restarted my phone I have to open this app and click that button, I think can use a script to solve it, but I don not know. because I can not find the right scrpit to do this. So, can you help me?
Click to expand...
Click to collapse
Try this script I found on XDA and see if it sets it to Permissive after boot. If it doesn't work all you need to do is delete it. You'll need Init.d support. There's app on the playstore that emulate Init.d. Remember to install busybox first.
http://forum.xda-developers.com/verizon-galaxy-note-3/development/script-permissive-selinux-stock-kernels-t2854363
@eemgee ,I mean I have to reboot my phone sometimes.
@Jorge_007 ,thank you so much!
@Jorge_007 ,unfortunately, it does not work.
00various said:
@Jorge_007 ,unfortunately, it does not work.
Click to expand...
Click to collapse
Well that's a bummer! Are you on the stock ROM or Custom ROM? For the custom ROM I know there are kernels here that are permissible by default. I'm not sure about the stock ROM. Have you looked into doing a soft reboot and see if the selinux policy sticks to what you want?
Here's an app that does soft reboot. https://play.google.com/store/apps/details?id=simple.reboot.com&hl=en
Maybe that'll work. Doesn't hurt try right?
@Jorge_007 I used a stock ROM now.But I don not want to change kernel. Do you have other ways?
00various said:
@Jorge_007 I used a stock ROM now.But I don not want to change kernel. Do you have other ways?
Click to expand...
Click to collapse
I'm not sure why you're having issues. I just installed the selinuxmodechanger app I mentioned earlier and it changes it to permissive after boot.... All I did was check the box show notification. What exactly are you doing that needs selinux to be permissive. Anyways, that's the end of the line for me. I don't know of any other ways to do it. Sorry.
Jorge_007 said:
I'm not sure why you're having issues. I just installed the selinuxmodechanger app I mentioned earlier and it changes it to permissive after boot.... All I did was check the box show notification. What exactly are you doing that needs selinux to be permissive. Anyways, that's the end of the line for me. I don't know of any other ways to do it. Sorry.
Click to expand...
Click to collapse
Sorry.I am really sorry.Sometimes I think I am a trouble maker.Maybe my question is too much. But thank you so much for your reply.Really, I install v4a but it did not work,then I want to disabled SeLiunx.But now I think maybe I don not need it cause the audio effect of my phone is not bad.Thank you again!!!:victory:Happy everyday!!
00various said:
Sorry.I am really sorry.Sometimes I think I am a trouble maker.Maybe my question is too much. But thank you so much for your reply.Really, I install v4a but it did not work,then I want to disabled SeLiunx.But now I think maybe I don not need it cause the audio effect of my phone is not bad.Thank you again!!!:victory:Happy everyday!!
Click to expand...
Click to collapse
No problem. And Viper4Android doesn't work well on lollipop stock ROM. I've already tried it before. When it does work it only worked for Google Play Music and nothing else. You're suppose to disable Nuplayer in the developer settings for V4A to work at all on lollipop. It worked best on Kitkat for stock ROMs.
I have been trying to root this model mentioned in the title for the past 4 days, nothing works. Anybody who has any ideas feel free to comment.
i am working on this model too, but nothing works at the moment, did u try rom change?
Yeah, I tried that, but anything I attempt to flash ends with a secure check fail in Odin.
https://forum.xda-developers.com/showthread.php?t=3555352
Sent from my Nexus 6P using Tapatalk
Still Stuck on Check Fail in Odin
hydroman202 said:
Yeah, I tried that, but anything I attempt to flash ends with a secure check fail in Odin.
Click to expand...
Click to collapse
So I have followed Hydromans rooting instructions closely, but no matter what, I am failing in Odin. Even tried to flash fresh firmware in case I missed a setting somewhere, but Im stumped. Dev Options on, both boxes ticked, downloaded boot.tar from Hydromans link, Odin 12.3. Samsung drivers are up to date as well. Ive even used debloater to block Knox packages first, but fail, fail, fail. How did you overcome this in order to set SELinux to permissive??
PapaV123 said:
So I have followed Hydromans rooting instructions closely, but no matter what, I am failing in Odin. Even tried to flash fresh firmware in case I missed a setting somewhere, but Im stumped. Dev Options on, both boxes ticked, downloaded boot.tar from Hydromans link, Odin 12.3. Samsung drivers are up to date as well. Ive even used debloater to block Knox packages first, but fail, fail, fail. How did you overcome this in order to set SELinux to permissive??
Click to expand...
Click to collapse
I believe that model has the Exynos cpu, you can download cpu-z from the market to check. If so, you can follow the directions in this link to add twrp recovery and root while doing so.
https://forum.xda-developers.com/an...overy-official-twrp-on5ltetmo-galaxy-t3422730
Thank u but....
Thank u but mine is the sms550tl tracphone model, can't install twrp without bricking it. I realized I have a new FW released since march, and it seems there isn't a recent boot.tar to use. Thanks for the help
ScSoluciones said:
i am working on this model too, but nothing works at the moment, did u try rom change?
Click to expand...
Click to collapse
Have you found a one click root solution for this device? Samsung Galaxy on5 Android version 6.0.1 SM-G550T1
Sent from my SM-G550T1 using XDA Labs
Skrappy187 said:
Have you found a one click root solution for this device? Samsung Galaxy on5 Android version 6.0.1 SM-G550T1
Sent from my SM-G550T1 using XDA Labs
Click to expand...
Click to collapse
I'm looking for this as well. SELinux is permissive, but KingRoot just refuses to work. Did I trip KNOX for nothing?
All,
i am new to the site and this was my first attempt to root my trusty s4 to try a custom rom. i followed a guide on the site using odin, recovery-clockwork-6.0.3.2-jfltetmo.tar and root_m919UVUAMDL.zip
everything seemed to be going well, but when i tried to reboot i got the error "Kernel is not SEandroid Enforcing, Set Warranty bit kernel"
Im not sure what to do.
i have read one post where someone suggests to load the new rom. I can load a file onto the sd card via sdcard reader.
Thanks for your time.
abadillo said:
All,
i am new to the site and this was my first attempt to root my trusty s4 to try a custom rom. i followed a guide on the site using odin, recovery-clockwork-6.0.3.2-jfltetmo.tar and root_m919UVUAMDL.zip
everything seemed to be going well, but when i tried to reboot i got the error "Kernel is not SEandroid Enforcing, Set Warranty bit kernel"
Im not sure what to do.
i have read one post where someone suggests to load the new rom. I can load a file onto the sd card via sdcard reader.
Thanks for your time.
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/showthread.php?t=3656502
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Try this
https://forum.xda-developers.com/showthread.php?t=3656502
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Droidriven,
Thanks for your time and help. can you give me your opinion on below.
so before i saw your reply i tried loading optimized-lineageOS-13.0-20170211-stable. This took and the phone is booting and seems to be working well.
i do still see the "set warranty bit: kernel" in the upper left, but the phone is booting fine now.
should i still run the proposed solution you gave?
Could this be an issue should i want to try another ROM?
abadillo said:
Droidriven,
Thanks for your time and help. can you give me your opinion on below.
so before i saw your reply i tried loading optimized-lineageOS-13.0-20170211-stable. This took and the phone is booting and seems to be working well.
i do still see the "set warranty bit: kernel" in the upper left, but the phone is booting fine now.
should i still run the proposed solution you gave?
Could this be an issue should i want to try another ROM?
Click to expand...
Click to collapse
No, it's not an issue, it's normal, Google makes android with SELINUX "enforcing" as default. We have to use this app to set it to "permissive".
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE