What's The Best Way To Revert To 4.3 & Block OTA? - Nexus 4 Q&A, Help & Troubleshooting

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.

Related

Wondering if the leaked ROM is really final...

Hi all,
it has been now nearly two weeks since the rom update leaked, and still so sign of an official update on htc website.
I'm wondering if this was really the final rom version, if so i don't know why htc would wait another two weeks after the leak.
I heard that somebody got that rom from an ftp server which is used by htc to upload data before it gets released. In this case two weeks seems also way too long for a deployment.
Are there any signs of the official release? I'm curious to see whether there are any last minute changes done.
well it could do with both orange and tmobile (in the uk) need to add there custom rubbish to there phones?
I read about major improvements in speed.
BUT - I also read about weather DB issues, WiFi issues, a.o problems.
So, I am definitely going to stay put, until an official release.
I am not going to waste time on reinstalling software etc, by flashing something "maybe-this-is-a-rom-very-close-to-the-final-one"!
yeah of course the carrier updates will take more time, but im talking about the htc update for unbranded devices.
since i made the ruu update i can confirm speed updates (but not huge difference), and i can confirm that more often the browser seems to have issues when going online via wlan. connection is there, signal is there, but the browser cant open pages.
and my device actually freezed two times, i couldnt make softreset and had to take the battery out. annoying.
but overall im satisfied with the performance optimization, still i will make another update as soon as the official rom is out..
and another minor thing: updating weather information manually will result in three updates. the app will update the weather data three times in a row, even though you only pressed update once,
I've had none of those problems, just checked the weather and it seems to update just once. I did have to pull the battery a couple of times BEFORE installing this new ROM when my phone totally locked though.
two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.
rom t-mobile
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol
rhedgehog said:
two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.
Click to expand...
Click to collapse
yeah two weeks was maybe too much. I was hoping this is not final since i have some new issues since i made the ruu update:
- peep widget updates only every 30th try. I'm trying to update the tweets and it doesn't work for about 20 times, and then somehow it works after many more tries. When i open peep app i get an error message that the service is not reachable.
- wifi has problems. many times it seems the connection is dead, when technically everything is ok.
- freezes (but i installed about 40 apps, maybe this was too much...)
- keyboard has sometimes lags. i never had ANY lags inputting text before the update.
- more force closes by 3rd party apps.
- touchflo force closes seem to occur more often also (but i had them before too so this might be the same).
- freezes when the device is in sleep mode. I was at a meeting, not doin anything with the device. Then i wanted to check the time and the display didn't power on. So the device freezed during some background process by android or any 3rd party app. I never had this problem before the update.
the good:
- yes its faster (homescreens)
- even the contacts list has LESS stutter, but stutter is still there. IPHONE 3gs is way ahead in this regard. i don't know why other lists on android are completely fluid while the contacts app list is not fluid.
- battery seems to last longer
overall the first impression was VERY good, but is somehow stained by the problems that surface after some usage time...i'm not 100% sure if the speed update was worth it...waiting for android 1.6 update, maybe this sorts some stuff out..
I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave
locutus-of-borg said:
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol
Click to expand...
Click to collapse
the RUU update won't work on a branded device. You need root to install the new rom in this case.
foxmeister said:
I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave
Click to expand...
Click to collapse
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...
Shahpur.Azizpour said:
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...
Click to expand...
Click to collapse
Well, Menu->Security->Factory Data Reset should do the job. To be honest though, I'd be more inclined to trust the "standard" Android way of updating your ROM than the HTC RUU process, because, as far as I'm aware, this'll be their first RUU for an Android device.
Regards,
Dave
Interestingly, the second poster here, http://forum.xda-developers.com/showthread.php?t=557628 , indicates that they had a problem with the factory data reset, but a recovery image wipe fixed it. I wonder if this related to your issues?
Even if you don't want to flash the modified recovery image permanently to your phone, you could boot it using fast boot and then wipe.
Regards,
Dave
how does it work? how can i restore a revocery image? isn't this an issue with the latest RUU update, that flashing recovery rom is not possible anymore or am i mixing things up here?
Steps 1 to 5 in this link, http://forum.xda-developers.com/showpost.php?p=4257045 , tell you what you need to do to boot the modified recovery image. Note that this doesn't flash anything to your phone - it just boots off the image you've supplied. You can permanently flash the recovery image later if you wish, but since you took the RUU root, I guess you don't want to put anything "unofficial" on your phone.
I've no idea if you having RUU'd already will prevent this, and I'm not going to RUU my phone to find out, but I doubt you would be stopped booting using fastboot.
Regards,
Dave
okay, thanks for the info!
Modaco wrote on a thread that doing the RUU update will make it nearly impossible to flash a modified recovery image.
I'm going to work with my current setup for some more days. If i see the mentioned problem reoccuring more often, i will proceed with the steps in your post.
or maybe we will see some changes (if not to the rom itself maybe at least the RUU will get an update) with the official rom update.
bye
shahpur
Just searched and you are right, you can't boot the recovery image if you have the new HBOOT from the RUU. However, the situation is not irreversible!
http://android.modaco.com/content/htc-hero-hero-modaco-com/292396/if-you-flashed-the-2-73-ruu-and-got-the-new-hboot/
Regards,
Dave
got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.
sorry, was busy working, but it seems you;ve got the answers...
i;ve not had any problems that you have had either with those apps. mine is so much better it's ridiculous. but then i wiped first and again afterwards just to make sure.
Lars8000 said:
got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.
Click to expand...
Click to collapse
Wow cant wait for tht, but 2bh I wud like T-mob to release their update as well at the same time as I am getting the G2 Touch on friday.

[Q] CAN I tether my GS4 L720 MDC? Seems NOT!

I am hoping someone here will have mercy on me with my newb dilemma and give it the time for an answer.
I am a recent Galaxy S4 user- only 3 days ago (after 6+ years of jailbreaking every iPhone they've made.) So I am admittedly a bit new to all of this...
My S4 is a on a Sprint carrier, L720...MDC
Day 1: I rooted it, successfully (using Odin and CF-Auto-Root-jfltespr-jfltespr-sphl720.tar)
Later that day I flashed it with TWRP with a Wifi-tether workaround I got from downloadandroidrom.com. Everything I used was quite specifically for my model phone, carrier, modexed, etc... Still, after flashing I ended up in a start-up loop. (would hang at the startup Samsung logo)
Day 2: Things became difficult at this point since I had no more internet access. I needed to go research this at a friends and downloaded the STOCK rom in order to recover. After flashing the Rom I was back in biz! Yay!
...Or so I thought- Seems NOW I have no option in my settings panel for Wifi tether "Hotspot" AT ALL. It is no longer there! How can this be? I have tried flashing to stock and re-rooting, etc a bunch of different things but I cannot get it back. It WAS there because I tried it day one, before rooting, just to see what it would do. It clearly had "Hotspot" with a toggle between the WiFi and Bluetooth toggles.
I tried every app I could find (FoxFi, Easy Tether, etc...) but the phone warns me that "Hotspot not supported"
Day 3: I asked around and browsed all the developer sites for info but could find no answers.
At the end of the day I tried CWM's "Tether" app. THIS WORKED!
So my questions:
ARE there any ROMs I can flash this particular phone with? I can't seem to find ANY that specifically mention my firmware etc... (except the stock)
IS that even important? Can I flash it with Wicked, for instance?
What would YOU try in order to gain a hotspot? (untethered)
Thanks for ANY help or advice you can offer!
Yes you can tether.
Yes you can tether with MDC.
Yes you can tether with just a rooted stock ROM.
Yes there are ROMs that have tethering built in.
First thing you might want to do is spend some time going through the stickies and how-tos. They are very helpful.
Then maybe getting your phone to the latest firmware - MF9 (there are a few stickies and posts about that).
I use crawrj's hotspot mod on my phone (MF9) without issue.
Maybe just try a rooted stock MF9 and then add the hotspot and then go from there.
On the stock ROM, the wifi tether hotspot option will show up only after you allow sprint customization to run. If you installed the stock ROM, and skipped the sprint customization, the wifi tether option won't show up.
Once you get the wifi tether option, you can go to http://forum.xda-developers.com/showthread.php?t=2256950 to download the appropriate version (MDC/MDL/MF9 - odexed/deodexed) to flash in custom recovery - that will give you the hotspot mod.
If you want to go to stock MF9 (latest version for the Sprint S4), go to http://forum.xda-developers.com/showthread.php?t=2277480
Thanks!
jj14 said:
On the stock ROM, the wifi tether hotspot option will show up only after you allow sprint customization to run. If you installed the stock ROM, and skipped the sprint customization, the wifi tether option won't show up.]
Click to expand...
Click to collapse
I may be asking this prematurely since I am going to read up more on this per your advice, but I am curious about how I was supposed to "allow the customization to run."
I used the Odin installer and it just went through a loading process, more-or-less on it's own. I have reloaded the stock ROM a few times now and I saw no prompts for anything, though I had the Auto-restart option checked so it just restarted and I went from there. Should I not have had the auto restart on? At what point do I allow this customization?
TIA
PS. I was thinking a bit more about it and are you possibly talking about the "updating" to applications that occurs at first startup? 160-something updates as I recall in a blue modal dialog... This happens even after just TWRKing the hotspot zip though, so I am not sure it could be that- but if so, I have never interrupted that. I would be afraid to!
I'm having the same issue as OP, and like him, I don't exactly understand what everyone is saying by the "Sprint customization".. I've flashed multiple times but I never get any prompt from Sprint or anything, just the standard setup for my Google account.
I've tried searching all over about this, but there doesn't seem to be that much on this unfortunately...
PS. I was thinking a bit more about it and are you possibly talking about the "updating" to applications that occurs at first startup? 160-something updates as I recall in a blue modal dialog... This happens even after just TWRKing the hotspot zip though, so I am not sure it could be that- but if so, I have never interrupted that. I would be afraid to!
Click to expand...
Click to collapse
Correct a mundo on that. DONT stop that.
I have no idea what the 'sprint custmization' thingy he's talking about. May just the 'updating applications' but I don't know.
If you clear the dalvik cache, which the updater script for the hotspot mod does, or do it manually, you will always see that 'updating applications...' that is the system building the dalvik.
leaderbuilder said:
Correct a mundo on that. DONT stop that.
I have no idea what the 'sprint custmization' thingy he's talking about. May just the 'updating applications' but I don't know.
If you clear the dalvik cache, which the updater script for the hotspot mod does, or do it manually, you will always see that 'updating applications...' that is the system building the dalvik.
Click to expand...
Click to collapse
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
From the few people who've had this same issue, it's what jj14 said about needing to let Sprint run their "customization", but I'm never being prompted by Sprint to let anything install on my phone after various resets, so I'm quite lost...
Such a frustrating roadblock, got the mod and everything, just literally can't "turn it on". Because, well... The button. Isn't there. :/
None of the standard apps i used on the GN2 work either.
chosenhobo said:
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
From the few people who've had this same issue, it's what jj14 said about needing to let Sprint run their "customization", but I'm never being prompted by Sprint to let anything install on my phone after various resets, so I'm quite lost...
Such a frustrating roadblock, got the mod and everything, just literally can't "turn it on". Because, well... The button. Isn't there. :/
None of the standard apps i used on the GN2 work either.
Click to expand...
Click to collapse
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
Click to expand...
Click to collapse
Much of that issue discussed in crawj's thread and in a few others.
Though I don't have hotspot in my dropdown/menu/status bar I DO have it in the System Settings>Connections>Hotspot.
All I have to do is turn it on and it works (and of course I can then adjust any settings.).
I did try some of the things suggested (like adjusting stuff in the dbase(s) tables) in the follow-up posts to get it to show in the drop down, but never got that. Again just a VERY minor thing for me. As long as I can actually USE the tether/hotspot I'm good.
pic
All right sport, don't know what else to tell. Have fun with that.
Sent from my SPH-L720 using XDA Premium 4 mobile app
octojofo said:
I may be asking this prematurely since I am going to read up more on this per your advice, but I am curious about how I was supposed to "allow the customization to run."
I used the Odin installer and it just went through a loading process, more-or-less on it's own. I have reloaded the stock ROM a few times now and I saw no prompts for anything, though I had the Auto-restart option checked so it just restarted and I went from there. Should I not have had the auto restart on? At what point do I allow this customization?
TIA
PS. I was thinking a bit more about it and are you possibly talking about the "updating" to applications that occurs at first startup? 160-something updates as I recall in a blue modal dialog... This happens even after just TWRKing the hotspot zip though, so I am not sure it could be that- but if so, I have never interrupted that. I would be afraid to!
Click to expand...
Click to collapse
Sorry about the delay in responding - was out of town.
When you flash the stock ROM, after the reboot, the phone does one update from Sprint. I'm told that this is the one that loads Sprint's bloat (sprint zone, sprint ID etc), along with the activation, and it is during this update, that the hotspot feature is made available on the phone.
(and I'm not referring to the Updating applications" message - that is just the android OS rebuilding the cache.
On a related note, I found this link - http://forum.xda-developers.com/showthread.php?p=44779759 - you can try this out to see if this helps.
chosenhobo said:
Our issue isn't getting crawrj's mod to work, it's that there is literally no "Hotspot" button in our settings menu. I'm using Sac's custom ROM right now and the selection is missing for me as well. I had it for my old MF9 stock version, so I have no idea where it went...
Click to expand...
Click to collapse
I'm pretty sure that Sprint's customization process doesn't run on most custom ROMs - the hotspot feature should be built into the custom ROM directly - if it is missing, you may want to reach out the developer and ask for suggestions/workarounds.

!!!Stop SAMSUNG GALAXY S3 FREEZING Problems!!!

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.

[Q] Sprint S5 huge battery drain after rooting

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!

Nexus 6P Latest 'O' update Killed messaging & Texting - help

Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
but the last 3 days since...
Phone calls Go right to my voicemail box they dont even ring on my phone....
And my [defualt]texting app constantly shows a little cloud crossed out saying no service
Anywheres I had 4gLTE Is now 3g ONLY and i can only do things on the internet thats it, but its slow as a dog.
Airplane mode on-off doesn't work I dialed that *#*# .. (insertnumbers) #*#* for testing and
switching how my phone recieves signal didn't work,
Factory reset from inside my settings + Hard reset from recovery made 0 difference.
Ill recieve all my texts but cant reply to them by rebooting my phone they all come in at once when my phone turns on but them my message app stops working again
-----------
Called my provider (TOTAL WIRELESS,) They said everything fine on thier end nothing they can do. So I called Huawai, and Verizon... got no where.
So im thinking... Its the update patch, or i need a new sim card.. So where / how Do I get the Nexus 6p's STOCK ROM So I can reinstall and how do i do that?
Should i try that? wait for another patch? or request a new sim.... Because as of right now my phones a brick and i use it for work.
Fluttershy_plays said:
Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
my phones a brick and i use it for work.
Click to expand...
Click to collapse
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Could you help me find that? not sure 100% on navigation of this website but ill try.
Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
--EDIT--
Fixed by going back to stock and starting over.
Fluttershy_plays said:
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
Click to expand...
Click to collapse
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Exodusche said:
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Click to expand...
Click to collapse
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Fluttershy_plays said:
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Click to expand...
Click to collapse
I'm sure there's a way to root with app but just as easy to flash TWRP and install Magisk. Which has nice easy feature of hiding root and passing safety net. That way you get a certified playstore and still use android pay to name a few. If your interested let me know I can explain the process after flashing Magisk.

Categories

Resources