Hi I have a Sony Xperia Z and it was rooted before I updated the software to 4.2.2 version. I wanted to root the 4.2.2 version too because i wanted to use light flow and make sure the leds all work properly with stamina mode. So I root my phone and copy super stamina.apk into the app folder and then when i next restart my phone, i keep getting the message, android updating apps. it then goes onto the home screen for about 5 seconds and reboots and does the same thing again, android updating apps, home screen for 5 seconds and reboot. any ideas whats going?
wasifraza said:
Hi I have a Sony Xperia Z and it was rooted before I updated the software to 4.2.2 version. I wanted to root the 4.2.2 version too because i wanted to use light flow and make sure the leds all work properly with stamina mode. So I root my phone and copy super stamina.apk into the app folder and then when i next restart my phone, i keep getting the message, android updating apps. it then goes onto the home screen for about 5 seconds and reboots and does the same thing again, android updating apps, home screen for 5 seconds and reboot. any ideas whats going?
Click to expand...
Click to collapse
Probably the wrong version of super stamina for your firmware, what Rom are you using? I would recommend removing super stamina, not sure why you need it, 4.2.2 is pretty good with battery life without stamina and obviously really good with the stock stamina mode
Related
I'm having a problem with WidgetLocker lock screen on mt rooted GT-I9070, cuz it takes time to start automatically after the boot and till then there's no lock on the screen. I was wondering if there is a way for making the app run in background while android boots by adding scripts or any other means. Tried making it a system app... it started up a bit faster but not enough... Please let me know if there's a solution.
GT-I9070
Android 4.1.2 (DDULP8)
Kernel- Cocore-E 8.6
Recovery- TWRP
Akash.Bhagat said:
I'm having a problem with WidgetLocker lock screen on mt rooted GT-I9070, cuz it takes time to start automatically after the boot and till then there's no lock on the screen. I was wondering if there is a way for making the app run in background while android boots by adding scripts or any other means. Tried making it a system app... it started up a bit faster but not enough... Please let me know if there's a solution.
GT-I9070
Android 4.1.2 (DDULP8)
Kernel- Cocore-E 8.6
Recovery- TWRP
Click to expand...
Click to collapse
I guess tasker can do that job
DaRkRhiNe said:
I guess tasker can do that job
Click to expand...
Click to collapse
I can't actually find a way how to do it with Tasker. What do I need to do?
Akash.Bhagat said:
I can't actually find a way how to do it with Tasker. What do I need to do?
Click to expand...
Click to collapse
Did not try to search auto start on Play store?
Try something like this: https://play.google.com/store/apps/details?id=com.autostart
I am not sure if it will work, but you can try...
Thanks
The app is already set to "Appear on boot" and it does start when the android boots, but almost after 2 minutes. That's quite slow since its the lockscreen. I want it to be visible when android starts, just like the stock android lockscreen appears when the device boots. For that i was wondering if it could be made to start at the same time when android boots so it'd be available instantly after boot. Just want to make the app load much faster after boot.
well, when you use tasker, that won't help as tasker itself needs to start, and that takes time
for me widgetlocker starts up right after booting, but i always wait a minute or 2 to let android boot before doing anything
Akash.Bhagat said:
I'm having a problem with WidgetLocker lock screen on mt rooted GT-I9070, cuz it takes time to start automatically after the boot and till then there's no lock on the screen. I was wondering if there is a way for making the app run in background while android boots by adding scripts or any other means. Tried making it a system app... it started up a bit faster but not enough... Please let me know if there's a solution.
GT-I9070
Android 4.1.2 (DDULP8)
Kernel- Cocore-E 8.6
Recovery- TWRP
Click to expand...
Click to collapse
Install Xposed Framework then install BootManager module.
Opss
Hi everyone!
I get my XZR 3 days before and upgraded it to Android 4.4.2. And cause of the problem with accu drain with Google Service I want to go back to Android 4.3.
Is this possible and what must I do to solve this?
Can I get root access after that?
Greetings Lemmi.
even if u go back to 4.3 google play services will still update to the same version and u will still get drain...
chewdaniel said:
even if u go back to 4.3 google play services will still update to the same version and u will still get drain...
Click to expand...
Click to collapse
That is not good.
Friend of mine have a xperia zr with Android 4.3 and his one stays the whole day with heavy using without problems. Thats the reason why a wanted to go back. But if it dont help I will stay where I am and wait for the update, that may fix the problem.
battery drain has gone when i do 6 steps in this topic http://forum.xda-developers.com/showthread.php?t=2774949
you can try this
now, my battery is very good, 5' onscreen wifi for 1% battery
I also use 4.3 and have no battery drain!
wihushae said:
I also use 4.3 and have no battery drain!
Click to expand...
Click to collapse
you may flash 4.3 ftf with wiped data and you will be back in 4.3 for good!!
On 4.4.2, you can still get rid of that battery drain by:
-go to settings>apps and clear Google play services data and Uninstall updates
-update again and get rid of the drain
I did it and it worked.
I rooted my HTC one. And now weird stuff is happeningt that has never happened before when I was unrooted. 1 , the battery seems to have a problem. It goes from 67%to 66%normally. I'll use an app like Facebooko r YouTube, and http be at 78% and more recently 100%. Weird. Also when I install an app from Google play or download the all file, it said successfullyi installed but it doesn't show up in the app drawer until I reboot, and if I click on it to open it , it tells me it has stopped. And when I have to update an app it takes forever. I mean I've been updating 6 apps forbtwp days now. And it hasn'tprogressedp passed the "installing" step. And my phone is always really warm. But not hot. Please help
Well, what i would do in your case is to reboot into TWRP or any other custom Recovery you have, and do a factory reset to the phone.
And if that wouldn't work i would flash the respective STOCK ROM for my phone.
it sounds drastic but i dont really know what else you can do.
Hi! I have a rooted Xperia z3 compact running android 5.1.1
I installed better battery stats and it asked me to install the compaion app. I did it, and then I rebooted the phone. But when I try to open it, I find it stuck like in this screenshot. I can't use the app neither if I unistall the whole program, it turns out to stuck again there. If I unistall the compaion app, the app crashes. What is happening?
Thanks!
Spoiler: screenshot
https://www.dropbox.com/s/urc0mnqup4w5c6j/Screenshot_2015-10-07-00-08-34.jpg?dl=0
It happened with me too. If you have purchased the app then make sure your phone is restarted after installing as a system app and after restart go to playstore and you will see update option go ahead and update and everything will be fine. It doesn't work if you have not purchased.
Sent from my ONE A2003 using Tapatalk
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk