Hey everyone,
I have been reading and learning a ton from the XDA threads over the past couple weeks so first off, Thank You! for all the useful info on here.
After doing some research I just rooted my Sprint S5 so I could tether free and use an international SIM when travelling. After rooting successfully, I tried several different tether methods; TreVe mod, Xtether, Fox Fi and finally Fabios WiFi Tether Router.
Fabio's tether is working sometimes but the result of all this work is that my battery is draining super quick, like 4 - 6 hrs. Also, my usual smooth performance is gone. Switching screens is choppy, using widgets is slow, internet is hampered.
I'm wondering if I rooted incorrectly or if remnants of tether programs are floating around in the background... I tried Dalvik wipe and ROM cleaner
Biggest problem... I didn't know about making a recovery file when I rooted... Yes, I'm a first timer :silly:
So my questions are as follows:
-How can I fix the battery drain?
-How can I restore performance
-Can I still use CWM or TWRP after rooting or is it too late?
I'm doing 27 hrs of travel in a couple days and have 2 kids so any help would be greatly appreciated!!
Thanks
First, Did you keep location/GPS off? Coz, it sucks battery a lot..
Obviously you can use CWM/TWRP now.. Basically it's recommend to flash it after root..
Finally, if you're not happy with a rooted device, you can always go back to stock device by flashing with a stock firmware..
Masum56k said:
First, Did you keep location/GPS off? Coz, it sucks battery a lot..
Obviously you can use CWM/TWRP now.. Basically it's recommend to flash it after root..
Finally, if you're not happy with a rooted device, you can always go back to stock device by flashing with a stock firmware..
Click to expand...
Click to collapse
First off, Thanks Masum for your help!
Battery drain:
I was using GPS/Location the same amount before rooting and the battery was lasting around 12 hours; I have about 6 hours of battery life now with minimal use. Could using GPS after rooting make a difference? It seems like everything is slowing down and my battery analysis says that Connections Optimizer is draining 42% and Android System is draining 31%. Is that unusual?
CWM/TWRP:
My understanding so far with the CWM/TWRP is that you should make a recovery when the phone is running healthy so you can go back to that if your phone gets messed up (like mine is now). Possibly I don't understand Recovery correctly. Please clarify.
Also, when trying to install TWRP from the installer app, it asks for the Device Name and then leaves a message saying that I will probably brick my phone if I enter the wrong one. I cant find my device name anywhere (Sprint S5). How do I find it?
Flash to stock firmware:
I was hoping to avoid this if possible as all the tutorials seems to be pretty complicated (for intermediate and pro's) and I'm a little worried i'm going to brick my phone ;0) But if this is my only option i have a couple questions:
In order to flash with a stock firmware, do I need to have a recovery file in place? If not, could you point me in the right direction for instructions for noobies on flashing to stock firmware for Sprint S5 please.
Once again, thanks for your help!
Related
I just updated to 4.4 yesterday, now battery life is horrible and tethering is broken. This is the weakest update I've seen since I moved to Android with the N1 launch. Other than the boot animation and a slight boost in wifi speeds I'm really not seeing any redeemable qualities in Kit Kat. I want to go back to 4.3 and block the OTA. What's the best way to do it? Is there any way to stay really close to stock rooted and do that? I'd prefer not to use any highly customized and buggy ROMs but if I have no choice I'll do what I have to.
Any suggestions?
GorillaPimp said:
I just updated to 4.4 yesterday, now battery life is horrible and tethering is broken. This is the weakest update I've seen since I moved to Android with the N1 launch. Other than the boot animation and a slight boost in wifi speeds I'm really not seeing any redeemable qualities in Kit Kat. I want to go back to 4.3 and block the OTA. What's the best way to do it? Is there any way to stay really close to stock rooted and do that? I'd prefer not to use any highly customized and buggy ROMs but if I have no choice I'll do what I have to.
Any suggestions?
Click to expand...
Click to collapse
I'm no expert but surly this would be a case of using something like Wugtool kit and revert to stock, then simply unlock the bootloader and flash a custom recovery this will block the update.
slugger09 said:
I'm no expert but surly this would be a case of using something like Wugtool kit and revert to stock, then simply unlock the bootloader and flash a custom recovery this will block the update.
Click to expand...
Click to collapse
I was already rooted and had a custom recovery on stock 4.3 but read that OTA would still be applied unless a custom kernel was installed or other major differences. I also couldn't tell whether the OTA will just fail and not be applied or if the error encountered would fubar my phone.
GorillaPimp said:
I was already rooted and had a custom recovery on stock 4.3 but read that OTA would still be applied unless a custom kernel was installed or other major differences. I also couldn't tell whether the OTA will just fail and not be applied or if the error encountered would fubar my phone.
Click to expand...
Click to collapse
as long u have custom recovery, the ota will still popup but no install, if i remember to block ota popup u need custom kernel
edit: the error on ota install would háppen b4 the ota would do anyting to the phone.
you do know that you can not judge battery life from one or two of the first battery cycles with a rom, right? first boot is when the device does most of its syncing, and you will get the worst battery life. not until the 3rd or 4th battery cycle will you actually see what the battery life is really like. and tethering isnt broken, the default tethering option works fine. third part tethering apps could be broken in 4.4, until they fix things.
opssemnik said:
as long u have custom recovery, the ota will still popup but no install, if i remember to block ota popup u need custom kernel
edit: the error on ota install would háppen b4 the ota would do anyting to the phone.
Click to expand...
Click to collapse
Thanks! What I needed to know.
simms22 said:
you do know that you can not judge battery life from one or two of the first battery cycles with a rom, right? first boot is when the device does most of its syncing, and you will get the worst battery life. not until the 3rd or 4th battery cycle will you actually see what the battery life is really like. and tethering isnt broken, the default tethering option works fine. third part tethering apps could be broken in 4.4, until they fix things.
Click to expand...
Click to collapse
I'll give it a few days on the battery unless it's out of control. My biggest concern was that it was charging at a slower rate. For the first 8 hours it couldn't do more than maintain current charge level while charging with my MBP. It seems to have overcome that now. I checked usage and couldn't see any heavy syncing.
Many thanks on the tethering. I was using stock tethering but couldn't get any traffic to get to the phone or past it but DHCP was working. After reading your comments I tried again, this time with another Android device and it worked. I want to say I had a similar problem before tethering a Win8 system so I will investigate that more.
Thanks again for all the replies. Really appreciate it.
Update
I thought I was OK with KitKat until I saw the stock email app had been updated to look just like the awful Gmail app. K9 won't work with my exchange accounts so after failing to get the earlier stock email (4.1) to work in KitKat I went back to 4.3. After a week I got nagged by OTA alerts. For others in search of a fix for BLOCKING OTA UPDATES ON THE NEXUS 4, I BLOCKED OTA UPDATES by following this great thread http://forum.xda-developers.com/showthread.php?t=1998378
I installed FOTAKILL, changed permissions, wiped the caches in recovery and renamed the otacerts.zip in /system/etc/security/ (using ES with root and mounting system with RW - plenty of other ways to do this) and no more hard update notification that you can't swipe away. There's a service manager you can try out also but reviews seemed spotty - read the linked thread for more info. Best of all I can use my phone and not be forced to use $h!tShat and I don't have to spend hours researching ROMs and kernel combinations and their respective bugs. Hope this info helps someone else. I couldn't get any hits searching for fixing the OTA problem with the N4 but the Nexus7 instructions have carried over to the N4 pretty well.
Hi everyone
I have an international version of Note 3. The problem I'm facing is, after rooting my phone and installing Lidroid Custom ROM, the battery on my phone started draining badly. To get rid of the problem I reinstalled Stock ROM on it and also unrooted the phone. But the problem is still there.
Even without using the phone, the percentage drainage is about 1% every 10-15mns. Have removed all third party application from the phone, but to no avail.
Can something be done about this? I'm at wits end and need a solution badly. Please respond ASAP.
Thanks in advance.
anirmj said:
Hi everyone
I have an international version of Note 3. The problem I'm facing is, after rooting my phone and installing Lidroid Custom ROM, the battery on my phone started draining badly. To get rid of the problem I reinstalled Stock ROM on it and also unrooted the phone. But the problem is still there.
Even without using the phone, the percentage drainage is about 1% every 10-15mns. Have removed all third party application from the phone, but to no avail.
Can something be done about this? I'm at wits end and need a solution badly. Please respond ASAP.
Thanks in advance.
Click to expand...
Click to collapse
Get wakelock detector from Google play see if it's a app draining the battery
Get into recovery mode and clean your cache, whatever bad bug went on with the custom ROM flash is still there. Once you clear it you should be OK.
Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:
Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...
what?
i havent got this
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?
Read the freezing thread sticky .
Delete this non working fix as well .
JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?
Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.
Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.
To preface the current issue with my phone, I guess I should probably give some history of what I've done to it. I got my S4 around November last year, where I kept TouchWiz for about a good 3 months. At the end of those 3 months, I downloaded and installed CM KitKat using their easy installer and it worked! However, when Lollipop came around, I got a little impatient and decided to get CM12 using Antares version. Initially, I noticed there were a few bugs/glitches, but ignored them for the time being. As time went on, it became increasingly aggravating and so a few dayus ago I tried to switch back to stock TouchWiz. When I was setting up the phone, I noticed that the wi-fi would just not turn it. It would stay at "turning on" for a very long time with no sucess. Thus, I decided to switch back to Antares version of CM, but now there were a few issues: service was VERY spotty and the piece de resistance: no sound at ALL, and youtube would never play videos. I searched around and saw that using the Sound Recorder would give me an error: "Internal Application Error. Microphone may be in use." Now I'm not the most techy person around and probably should not have been messing around with my phone, but now all I want is a properly working phone, doesn't matter if its kitkat or lollipop. Your help is greatly appreciated. (If you need to know more info, go ahead and ask, because I'm very new to all this) Thanks!
If you want the stock ROM back, flash it twice using Odin. General consensus here is that you need to flash the modem twice in order for WiFi and cellular radios to work properly. Flashing the ROM twice will do that without having to track down just the modem file and trying to flash that.
Strephon Alkhalikoi said:
If you want the stock ROM back, flash it twice using Odin. General consensus here is that you need to flash the modem twice in order for WiFi and cellular radios to work properly. Flashing the ROM twice will do that without having to track down just the modem file and trying to flash that.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be working :/ When setting up my S4, it's still stuck at turning on the wifi
I switched back to Antares CM, and everything works fine except for sound/microphone (to my knowledge). Would there be any way to fix this?
I have asked in the specific threads, but I'm getting ignored.
I have tried the HTLE version, but my phone won't take that version. It shows error, that is not for my phone.
Any help would be appreciated.
Thank you in advance,
Tibor
tibimakai said:
I have asked in the specific threads, but I'm getting ignored.
I have tried the HTLE version, but my phone won't take that version. It shows error, that is not for my phone.
Any help would be appreciated.
Thank you in advance,
Tibor
Click to expand...
Click to collapse
Just go to the regular Note 3 development section and grab the AryaMod Port S7Edge Port, and it works on the T-Mobile N900T as well. Most of the ROM's over there will work on this phone.
Or this https://forum.xda-developers.com/galaxy-note-3/development/rom-t3565746
tibimakai said:
I have asked in the specific threads, but I'm getting ignored.
I have tried the HTLE version, but my phone won't take that version. It shows error, that is not for my phone.
Any help would be appreciated.
Thank you in advance,
Tibor
Click to expand...
Click to collapse
Why don't you ask/look in the T Mobile forum ???
I haven't found any that allow for proper GPS locking. You can get location, but the satellites won't stay locked. Aside from that, I haven't been unable to install any of the Nougat or Note7 ports on my T-Mobile phone. Some aren't 100% stable though, and that goes for almost any device.
It's fun to play with them, I guess, but so far the only safe daily driver is the stock ROM, if you want full stability, battery life, GPS, 100% functional. Personally I can't wonder if my alarm will go off, or if the battery will randomly drain, and shoddy GPS is an issue since I'm not currently using a standalone GPS device. I don't know about you, but the possibility of my phone crashing or rebooting during a call, while navigating, or while relying on the alarm is just not worth the eye candy that you can get just by rooting and installing aftermarket tweaks.
I've run two of the Cyanogenmod 14.1 based roms, maybe more, and they all had those issues. Same thing with the Phronesis ROMs. All are unreliable for every day use.
So, in short, I don't there is a best Nougat ROM, because I can't see using any of them aside from dual booting into them here and there, out of boredom, and to check if things have improved.
Thanks for that. I was afraid of this, that they are not reliable. I guess, I will just have to wait, for the Note8 then.
Guys, if your problem is that your phone is seeing satellites but never actually locks, there's a fix for that. Grab the gps.conf from this thread: https://forum.xda-developers.com/ga...-devs-fix-gps-users-ntp-to-localhost-t3531891
Move that gps.conf to /system/etc/ through whichever means you prefer (recovery, root file manager, whatever), set it to 0644 permissions (rw-r--r--), reboot and you should never have trouble getting a GPS lock again (until you flash another rom, then just do it again). Long story short, there's a stupid bug with most ROMs out there that they're trying to sync to the GPS satellites using data from a server over the internet instead of the (very accurate) internal clock, and since there's a delay over the internet it can't sync and never locks. That gps.conf fixes that issue.
I have ended up, installing this update and it seems like it's working great, except when I reboot it, it's going in reboot loop. The only way I can boot it up, if I remove the battery for a while.
I did not try gps, yet.
I'm using RR rom 7.1.1. It works great
Do you have, US T-Mobile phone? If yes, than from where did you get that rom?