Hello all!
At the request of Santod, here is a separate thread to discuss the SMS issue some of us are experiencing with his 5.0.1 GPE ROM.
The original ROM thread can be found here:
http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
For some of us, flashing this ROM makes sending SMS messages work intermittently. Some experience that only the first message successfully sends, then all subsequent messages fail. Personally, I've tried flashing v. 1.02 three times to no avail. My most recent attempt was after re-flashing updated firmware and radios.
Let's figure this out!
As an update, it would seem that disabling both cellular data (In Settings -> Data Usage) and setting the preferred network to 1x (In Settings -> Wireless & Networks -> More -> Cellular Networks) seems to stop SMS from failing.
I've attached screenshots of my current settings.
Perhaps this helps!!!
steveg545 said:
As an update, it would seem that disabling both cellular data (In Settings -> Data Usage) and setting the preferred network to 1x (In Settings -> Wireless & Networks -> More -> Cellular Networks) seems to stop SMS from failing.
I've attached screenshots of my current settings.
Perhaps this helps!!!
Click to expand...
Click to collapse
because that stops the phone from sending them all together?
synisterwolf said:
because that stops the phone from sending them all together?
Click to expand...
Click to collapse
1x allows me to send SMS and make calls. Just tested both.
steveg545 said:
1x allows me to send SMS and make calls. Just tested both.
Click to expand...
Click to collapse
good to know. i wonder why some are having the sms bug. I use textra and havent ran into the problem yet..
*knocks on wood*
steveg545 said:
As an update, it would seem that disabling both cellular data (In Settings -> Data Usage) and setting the preferred network to 1x (In Settings -> Wireless & Networks -> More -> Cellular Networks) seems to stop SMS from failing.
I've attached screenshots of my current settings.
Perhaps this helps!!!
Click to expand...
Click to collapse
Damn. I'm glad there's SOME way around it, but hopefully a more convenient and more permanent solution comes along soon. This is the only ROM on any phone that I've been 100% satisfied with. Well I mean, it was perfect until I started having the SMS issue.
OP.
Can you pull a log cat after you sent 2 messages before the work around. i wonder if i can see something that i can help with. lmk
synisterwolf said:
OP.
Can you pull a log cat after you sent 2 messages before the work around. i wonder if i can see something that i can help with. lmk
Click to expand...
Click to collapse
Sorry if the log is a bit of a mess (never pulled one before).
Two messages were sent on a fresh boot, one succeeded. One failed.
Let me know if I can be of any more help!
Setting to 1x and disabling data allows SMS for me too. So weird.
Sent from my HTC One using XDA Free mobile app
Headed home now. Will take a look at it.
Problem Flashing Stock recovery
I'm having the SMS problem. I tried the method of flashing stock recovery and then factory resetting. I flashed the stock recovery and it seemed to flash ok, but when I go into bootloader and select recovery, the screen goes blank and then after a bit, an image of the phone appears with an red triangle and exclamation point on it. So I can't get into recovery. I reflashed TWRP recovery and I can get into that fine, but when I flash stock recovery, it still doesn't work. The stock recovery I'm using is https://www.androidfilehost.com/?fid=23622183712472879
Any ideas?
greiland said:
I'm having the SMS problem. I tried the method of flashing stock recovery and then factory resetting. I flashed the stock recovery and it seemed to flash ok, but when I go into bootloader and select recovery, the screen goes blank and then after a bit, an image of the phone appears with an red triangle and exclamation point on it. So I can't get into recovery. I reflashed TWRP recovery and I can get into that fine, but when I flash stock recovery, it still doesn't work. The stock recovery I'm using is https://www.androidfilehost.com/?fid=23622183712472879
Any ideas?
Click to expand...
Click to collapse
You don't need to do anything else with the stock recovery. You have to have it in order to do the stock factory reset. After you do the factory reset go back to twrp and flash the ROM again.
Well add me to the list of people having this problem. Setting it to 1x network only also allows me to send texts temporarily until I turn it back on LTE. Has a reset with the stock recovery been working for many people or was it a new idea that you decided to try greiland? Has anybody else restored their text history with titanium backup? I did and am wondering if it is a problem. I went from a fresh flash from 4.4.3 stock with all of the OTA firmware so I'd be surprised if it is something that requires a factory reset.
Also what recovery did you guys use? I flashed it with 2.8.1.0 and I had to do it twice before it would let me boot.
BranC85 said:
Well add me to the list of people having this problem. Setting it to 1x network only also allows me to send texts temporarily until I turn it back on LTE. Has a reset with the stock recovery been working for many people or was it a new idea that you decided to try greiland? Has anybody else restored their text history with titanium backup? I did and am wondering if it is a problem. I went from a fresh flash from 4.4.3 stock with all of the OTA firmware so I'd be surprised if it is something that requires a factory reset.
Also what recovery did you guys use? I flashed it with 2.8.1.0 and I had to do it twice before it would let me boot.
Click to expand...
Click to collapse
Try again with 2712 and don't restore your messages.
disconnecktie said:
You don't need to do anything else with the stock recovery. You have to have it in order to do the stock factory reset. After you do the factory reset go back to twrp and flash the ROM again.
Click to expand...
Click to collapse
Stock recovery factory reset did not fix it for me.
---------- Post added at 11:26 AM ---------- Previous post was at 11:13 AM ----------
I'm doing the stock recovery reset based on Santod's advice (http://forum.xda-developers.com/showpost.php?p=55930057&postcount=1553). There's a lot of discussion about it towards the end of his Lollipop thread and his GPE 4.4.4 thread.
It just started happening to me within the last few days. Only thing I've done to my phone right before it started happening was I upgraded to Santod's GPE Lollipop V1.02 edition (dirty flash from 1.00) and installed the NuK3rn3l V2.00 kernel. The other thing I did was I restored an old Titanium backup of my SMS messages from a 4.4.4 backup. Maybe that hosed things up? But I've done full wipes, stock factory resets since that and it won't fix it. Only thing that fixes it is restoring my nandroid backup of the [ROM][4.4.4] NuSenseSIX-ART Edition that I had before upgrading to Lollipop.
This may have already been suggested but using an alternative texting app like Textra doesn't work. This is getting so freaking frustrating.
For me, coming from a fresh flash on mdmower's TWRP 2.7.1.2 and not restoring any messages (I don't use Titanium or any app backups) still presents the issue. App doesn't matter (I've tried stock messaging, Google Messenger, and Textra).
There is a logcat a few posts back that I pulled when the issue occurred as well.
Just an FYI from my experience thus far!
steveg545 said:
For me, coming from a fresh flash on mdmower's TWRP 2.7.1.2 and not restoring any messages (I don't use Titanium or any app backups) still presents the issue. App doesn't matter (I've tried stock messaging, Google Messenger, and Textra).
There is a logcat a few posts back that I pulled when the issue occurred as well.
Just an FYI from my experience thus far!
Click to expand...
Click to collapse
Have you tried the factory reset with the stock recovery too? I've thought about it but its a lot of work to do if it isn't doing the trick for anybody else here.
BranC85 said:
Have you tried the factory reset with the stock recovery too? I've thought about it but its a lot of work to do if it isn't doing the trick for anybody else here.
Click to expand...
Click to collapse
I'm in the same boat. If the stock recovery fix hasn't worked for others, I wonder if it's worth the work.
I think I'll give it a try as a last ditch effort if the logcat I uploaded doesn't yield any insight into the issue.
Not saying Tibu is or isn't the cause of the problem.
But my gut always tells me folks with this issue did just that.
Restored messages with tibu.
Are there residual side effects that continue to booger you up once that's been done, even after a full wipe?
I don't know, but restoring messages with Tibu is about the worst thing ever and has always, always, always created issues.
I won't even touch Tibu personally.
Haven't since a bad experience years ago, and never will again.
It causes more grief then it saves me.
That's my opinion on Tibu...
Related
Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
my3kgt said:
Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
Click to expand...
Click to collapse
General Network Error is when the system returns an error stating that you have no connectivity to send a message or an MMS (at least from my experience w/ it). I have this issue a lot with any messaging on my end because of shoddy reception. Which other ROMs besides Virtuous are you flashing that are giving this error? I know for a fact the CM7 has been having a LOT of issues with data connectivity. The last ones I remember hearing about with working data is #79 (or was it #80, I can't remember) and #85 and for a few people, #92.
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Have you tried a different radio?
Sent from my Incredible 2 using xda premium
my3kgt said:
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Click to expand...
Click to collapse
People on CM were complaining of the same exact issue. They'd get bars of reception but MMS was just broken. I was just stating that when I try to send a message thru verizon and not google voice, I often get the same error message you're getting, which means that the data is being prevented from going out. I probably should've clarified that a little better lol. When you installed Virtuous, did you do a wipe data/cache and a wipe dalvik cache?
Also, if you restore back to your Gingerbread 2.3.3 that's rooted and your MMS is working fine there, then I don't believe it could be your radio. A possibility would be the kernel, but I doubt that Virtuous would package a kernel that would crash the MMS function. And since it's any SMS/MMS app, that knocks out the possibility of it being application based. The only thing I can suggest, would be to test out another ROM. If you're looking for sense based roms, go for BAMF's (http://www.teambamf.net) or Newt's Incredible 2 HD (http://www.themikmik.com). If you're looking for an AOSP based rom, go for CM7 (found on ROM Manager or at http://www.cyanogenmod.com) or MIUI (ROM Manager again, or http://www.miuiandroid.com). If you want a hybrid, I would suggest Skyraider Zeus (http://www.teambamf.net) or Gingersense (it can be found in the development portion of XDA). Remember when you flash a rom for the very first time, I'm sure you know this already, but you need to backup your rom first and then wipe data/cache and wipe your dalvik cache. Not doing either wipe before installing a brand new rom for the first time can cause unforseen errors.
Ok I found the answer while actually looking for new radios, so thanks for the post! haha
For all you out there who might run into the same problem, this is the solution I found..
Instructions to fix MMS (by xelsewherex)
1.Go to the market and download apn backup and restore (Market Link APN B&R).
2.Create a folder on your sdcard named APNBackupRestore if it doesn't exist already.
3.Copy this file, ht tp://db.tt/9Ao5ErR, to APNBackupRestore folder (If you aren't doing this on desktop, hit menu now in xda and choose browser. File is an xml and your phone will not know what to do with it. Long press the link and use 'save link'). This is an XML doc, sorry but since I'm new I can't just post a link, just remove the spaces between ht and tp.
4.Run APN Backup Restore and press Delete Apns and then Restore from the downloaded file.
5.You should be good to go from there. MMS should now work and the softkey lights do as well.
Hey Everyone,
I am running the SGH-T989 with the latest Darkside (2.3) ROM and kernel. Though new to the forums I have been "trolling" here for years and rooting and moding every phone I have had since ... well I can't remember when.
Never had any serious troubles, but suddenly, about 2 days ago I stopped getting incoming calls. It acts as though the phone is off and all calls go straight to voice mail, this happens when I have full signal, and I can still make outgoing calls. I have done full wipes, charged fully, tried it plugged in, not plugged in, on WIFI calling, on cellular networks, different ROMs, and nothing seems to work.
Anyone have any suggestions?
check under settings --call--- call rejection---auto reject numbers---should be off or the ones you want rejected...may got switched to all calls
Thanks for the response Bobby. Unfortunately I checked that after posting and it is set to off.
However I retired again and I am receiving calls now over Wifi calling, just not over cellular networks.
This is herring frustrating and of course the missus blames me for routing and ROMing
Ok,actuakly I tried to type retried but you gotta love auto-correct.
Sent from my SGH-T989 using XDA App
What about call forwarding?
Just checked and Call forwarding is set to:
Always forward: Disabled
Forward when busy / unanswered / unreachable is all set to voicemail.
Could that be the culprit even if I show full signal and am able to make out going calls? Should I disable any of those?
A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.
myndsey said:
A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.
Click to expand...
Click to collapse
Yes if you restore system data that causes issues unless it's backed up and restored on the exact same rom.
Sent via Brain Drain
I am having the same exact problem on Jugs 5.0... very interesting. I did not do a Ti restore, but rather just upgraded from one iteration of Jugs (3.7) to the latest.
But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.
You beat me by seconds Poser. I tried Jugs 5.0 too and the problem still didn't go away.
Mystic_ said:
But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.
Click to expand...
Click to collapse
By fresh install did you go into recovery and:
1. wipe data/factory reset
2. wipe cache
3. wipe davlik
4. mnt /system and wipe
5. flash ROM
I only ask, because I am wondering if "ghosting" is leading to mine and your problem?
Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.
Mystic_ said:
Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.
Click to expand...
Click to collapse
No dice, same problem. Wonder if it is an /efs problem?
Don't know but it is odd. I can still make outgoing calls, get data and everything else.
I have the same exact symptoms...exactly. It also just began a couple of days ago. Have you restored to bone stock via ODIN (I can't, my usb port is shot)?
Get a new sim card. If factory reset doesn't do it and you think its not network related and you don't think you accidentally blacklisted all your friends its probably the sim card.
Sent from my HTC Vision using xda premium
Android_Monsters hit the nail on the head. I took it to a T-Mobile store, they replaced the sim and all is golden (except that my wife can now call me again )
And in case you are worried, my phone was still rooted / ROMed and the Tmobile rep working the store was simply stunned to see the custom boot screen. They didn't care in the slightest that the phone was rooted and ROMed. In fact he was upset because he couldn't do that because of company regulations.
Same here.... new Sim did the trick
Huh?
This happened to me b4 I called t-mobile and they fixed it without going anywhere.
Sent from my SGH-T989 using xda premium
For some reason, my phone randomly has lost the ability to make or receive phone calls. Any time i try to place a call, it simply says "call ended" before even attempting to dial. I have not made any major changes to the phone recently. This seems to have happened out of nowhere. Data and text messaging work just fine, but phone calls won't.
My phone is rooted and I have the leaked Touch Wiz Jelly Bean rom installed. Also using CWM recovery.
I have tried pulling the battery for 10 minutes, and I also wiped cache/dalvik then did a system reboot through recovery, to no avail. Is there anything else I can try? Would prefer not to have to do a full data wipe if possible. Unfortunately I can't even call Telus (my carrier) to ask them for advice, due to this problem.
Is your IMEI# intact? Maybe try a new SIM card? Go back to stock to see if that fixes it. (I know you said you'd prefer not to wipe.)
Just to rule out any ROM related issues you could always make a full backup from recovery, then full wipe and flash back to stock and see if the problem persists. This way although you did wipe you can revert back to you current setup in a matter of minutes like nothing ever happened, if the problem is not fixed by going back to stock.
saj222 said:
Is your IMEI# intact? Maybe try a new IMEI card? Go back to stock to see if that fixes it. (I know you said you'd prefer not to wipe.)
Click to expand...
Click to collapse
Yep IMEI is still there. Anyone have any other suggestions before I wipe and flash back to stock? I'll try a new SIM card if wiping and re-flashing doesn't work.
dntesinfrno said:
Just to rule out any ROM related issues you could always make a full backup from recovery, then full wipe and flash back to stock and see if the problem persists. This way although you did wipe you can revert back to you current setup in a matter of minutes like nothing ever happened, if the problem is not fixed by going back to stock.
Click to expand...
Click to collapse
This seems like a good idea, I think I'll have to go this route... thanks.
Okay so I did a full backup using CWM, then wiped everything. Attempted to re flash the stock rom but ran into an issue and decided to try a different rom instead just to try it out.
Dialler worked fine on the new rom, so that was great news. Then I attempted to sync my contacts and everything with my Gmail.... But nothing was there. Apparently I somehow lost all my contacts!
So, freaked out, I immediately reverted to my Cwm backup, which thankfully restored everything. Just for the hell of it I tried the dialler... And it worked! So.... Yeah I have no idea what exactly fixed my problem in the end, but I'm just happy its working.
Thanks for the suggestions everyone!
Sent from my SGH-I747M using xda app-developers app
Sounds like the dialer app was borked somehow, might want to look into those sync settings though. I had an issue one time where the contacts i added to my phone were saving to the phone and not as gmail contacts. To check you can just log into gmail in a broswer and look at your contacts, make sure they are all there. If not you can go to your contacts on your phone, press menu and export to a .csv file. This will move all contact info into this file and you contacts will be blank, at this point simply find where you saved the .csv and import the contacts which will give you the option to make them gmail contacts. Then all you need to do is go into gmail on the browser again and delete and/or merge the duplicates.
Okay so I left my phone as-is for the past couple weeks until earlier tonight. I made a backup with CWM, then I attempted to flash a couple new roms. Did a cache/dalvik/system format/factory reset before each rom installation, then made sure to format cache/dalvik and fix permissions after each installation attempt. The roms installed fine and everything was working, except I lost use of my dialler again! So I reverted to my backup, but the dialler problem has persisted, just like I described in the OP. The way I "fixed" it last time, was to restore my backup....but that isn't helping this time...
Anyone know what else I can try? IMEI still intact, getting mobile data, wifi, MMS, etc... just can't make or receive calls again.
I should also mention that I a while back, before I tried rooting/installing any custom ROMs, I made a backup of my EFS folder on my phone... should I attempt to restore this?
Dial
*#2263#
Check to make sure automatic it's selected.
I had a similar problem messing around with lte, and found the above fixed the issue.
Also on Telus.
Sent from my SGH-I747M using Tapatalk 2
Wow thanks so much! That totally fixed the problem. I seem to pick up lte signals less often now but at least I can use my phone!
Sent from my SGH-I747M using xda app-developers app
Yeah, the lye on my phone only picks up when I'm out of my house. Has to do with the signal from telus I believe
Sent from my SGH-I747M using Tapatalk 2
Help! My phone is freezing / locking up and rebooting several times a day now!
I successfully did the stock AT&T Jellybean update this week when it became available via Kies.
I had no issues with the initial upgrade…it seemed to go smooth.
After a day…or a few hours….I can’t remember…I did start noticing a few issues with Touch Wiz closing or freezing and some other apps misbehaving. I can’t even remember what exactly the issues were.
I was also having some other quirky issues with the phone on stock ICS before the JB update…so I have been meaning to do a factory reset and reinstall everything.
So with the phone being even more flakey with JB I went ahead and did a factory reset with my new JB setup.
After a few hours setting up the phone with all my apps, settings, etc I noticed two issues. Swiftkey would not remain selected as my default keyboard and AT&T Voicemail viewer would not retain any of my account settings after a reboot.
After some Googling I learned that this is a know issue with JB 4.1.1 for many apps…they don’t quite install properly and something happens during shutdown that causes the settings to be lost. The only work around seemed to be:
Root Phone
Install apps
Backup with Titanium or other backup program
Uninstall apps
Restore apps – then they somehow install properly and work
I did this…first time rooting the phone….and the root and work around worked perfectly first time.
But after continuing to install apps and tweak my phone the real problems have now begun.
The phone is completely freezing at random times…in any app or in the TW launcher. It seems to just sit there frozen until I hold down the power key long enough to force a reboot or take out the battery.
There are no force closes or other error messages and I have found no other pattern to the freezes.
So now the phone is almost totally useless. It may work for a few hours…or just a few minutes before locking up. Worse…I have no way to know this has happened if the phone is in my pocket.
I did another full factory reset using the Recovery Mode and reinstalled everything again and am having the same issues.
I fear the root somehow corrupted my phone or one of my apps is totally incompatible with JB but I have to many (~70) it will be very hard to tell which one.
The other issue I am having is the battery is draining in just 4-5 hours even with light use.
Coincidentally….4G LTE was just turned on in my area this week so that would be a factor in both the battery drain and maybe even the lockups. I have a Microcell at home…wondering if 4G LTE and my Microcell are not behaving.
There are just too many variables with a new ROM (JB), fresh rooting of the phone plus recovery app installed, plus 70+ apps, plus new 4G LTE, plus my Microcell.
I don’t know what to try next to get the phone stable or to get the battery use reasonable.
Please post any and all suggestions….
One thing I’d like to clear up or eliminate is the root issue…is there any way that is the cause of my phone’s current problems?
What a mess of a week! Instead of the total awesomeness of JB, 4G LTE, and the fresh experience of using a rooted phone...all happening for me in the same week...I get a total headache and useless phone. Sure hope I can dig my way out of this.
Thanks for reading my long post!
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
wujiku said:
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Thanks for the ideas....had not heard of the "Hard Factory reset *2767*3855#"....how is that different from a factory restet initiated from winthing Android or from the recovery program?
Also - is there any quick / easy way to know which of my apps are supposed to be compatible with JB?
Sure will be a pain to reconfigure everything again.
Should I be safe installing my apps via Titanium backup restores? (as long as I don't restore data)
Also - what about restoring my IMs and call logs from Kies? Is that safe?
Boomer6345 said:
Thanks for the ideas....had not heard of the "Hard Factory reset *2767*3855#"....how is that different from a factory restet initiated from winthing Android or from the recovery program?
Also - is there any quick / easy way to know which of my apps are supposed to be compatible with JB?
Sure will be a pain to reconfigure everything again.
Should I be safe installing my apps via Titanium backup restores? (as long as I don't restore data)
Also - what about restoring my IMs and call logs from Kies? Is that safe?
Click to expand...
Click to collapse
Do you happen to have juice defender? I had the same problem, and noticed it only happened when I was on battery. I uninstalled that and it stopped rebooting.
stbtigerr said:
Do you happen to have juice defender? I had the same problem, and noticed it only happened when I was on battery. I uninstalled that and it stopped rebooting.
Click to expand...
Click to collapse
Nope....juice defender...
And my phone doesn't really seem to be rebooting....just freezing up. I have to force it to reboot by holding down the power button for 10 seconds.
About to try a fresh factory ROM install (pre-rooted) and a hard factory reset.
Then I'll add my apps back very slowly to see....
What a pain in the you know what!
wujiku said:
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Well...I did all that...and no luck. Still freezing up.
I could not actually do the exact *2767*3855# reset...the phone would not respond to that command. So I used CWM to format the SDCard and also did a factory reset there.
Reinstalled my apps carefully and without data restore...boom....phone is locking up all the time again after maybe 12 hours of good operation.
Either this build of JB is not working on my phone or it somehow got fubar'ed during that first upgrade.
My plan now is to restore to factory ICS un-rooted....reset the flash counter if possible....and return the phone under warranty if possible.
Any recommendations for this?
Got replacement phone - still freezing up!
Boomer6345 said:
Well...I did all that...and no luck. Still freezing up.
I could not actually do the exact *2767*3855# reset...the phone would not respond to that command. So I used CWM to format the SDCard and also did a factory reset there.
Reinstalled my apps carefully and without data restore...boom....phone is locking up all the time again after maybe 12 hours of good operation.
Either this build of JB is not working on my phone or it somehow got fubar'ed during that first upgrade.
My plan now is to restore to factory ICS un-rooted....reset the flash counter if possible....and return the phone under warranty if possible.
Any recommendations for this?
Click to expand...
Click to collapse
HELP!!!! Please!!!!!
I did a warranty RMA and got a new (refurbed) phone from AT&T. I set it up with stock ICS and it seemed to work fine. I installed CWM without rooting via ODIN and did a Nandroid backup. I then used CWM to load TWRP recovery and did a backup with that.
Then I loaded the stock JB room with root. Tweaked the phone and app settings a little and things seemed to be fine for 1/2 a day. I reinstalled TWRP since the ROM flash replaced it with stock recovery. Things still seemed fine.
So...with JB rooted and seeming to work fine....I booted into Recovery (TWRP) and did a fresh Nandroid backup since the phone was finally all configured and working (apparently).
Well after rebooting from the backup...the phone is acting all crazy again. It seemed to crash my home WiFi network....had to reboot my router. Now the phone freezes or locks up any time I disable WiFi or change WiFi settings.
I am just cursed with the GS3!
Two separate phones with stock AT&T JB with root...one running CWM Touch and the new one running TWRP and both lock up or freeze all the time.
Should I give up and try custom ROMs? Give up on rooting?
I want TouchWiz for SBeam and some of the Samsung apps that I like better than stock...would rather just stay stock with Root.
What can I do to get this phone stabilized with root and JB???
Just did another test...
If I leave my house and walk a couple hundred yards away...as soon as the phone finally loses the WiFi signal and disconnects it locks up.
Seems like all my issues (with first phone maybe too) are tied to WiFi.
Is no one else having WiFi issues with JB? Could it be tied to rooting somehow? For instance...maybe the stock rooted ROM has different modem or WiFi drivers...or different kernel than the actual stock JB ROM I first used via Kies update?
Boomer6345 said:
Just did another test...
If I leave my house and walk a couple hundred yards away...as soon as the phone finally loses the WiFi signal and disconnects it locks up.
Seems like all my issues (with first phone maybe too) are tied to WiFi.
Is no one else having WiFi issues with JB? Could it be tied to rooting somehow? For instance...maybe the stock rooted ROM has different modem or WiFi drivers...or different kernel than the actual stock JB ROM I first used via Kies update?
Click to expand...
Click to collapse
I've got the KIES JB Update, & rooted. I am not experiencing any of the issues your having. It might be helpful if you could post a list of apps & widgets that you have installed, If you have frozen or removed stock files.
It sounds like you may be experiencing some app conflict issues.
MasterDecker said:
I've got the KIES JB Update, & rooted. I am not experiencing any of the issues your having. It might be helpful if you could post a list of apps & widgets that you have installed, If you have frozen or removed stock files.
It sounds like you may be experiencing some app conflict issues.
Click to expand...
Click to collapse
I have not frozen any apps or done anything I would consider advanced or risky....
I tried running with what I thought would be just "safe" apps....no luck. I've got most all of my apps installed and did a Titanium Backup so here is a dump of all the user apps backed up:
Code:
cgeo.geocaching-20121219-204517.tar.gz
com.amazon.kindle-20121219-204309.tar.gz
com.amazon.mp3-20121219-204326.tar.gz
com.amazon.mShop.android-20121219-204301.tar.gz
com.anddoes.launcher-20121219-205011.tar.gz
com.anddoes.launcher.pro-20121219-205016.tar.gz
com.android.chrome-20121219-204524.tar.gz
com.ap.advml-20121219-204732.tar.gz
com.apksoftware.compass-20121219-204539.tar.gz
com.ArtInGames.AirAttackHD-20121219-204225.tar.gz
com.asksven.betterbatterystats-20121219-204516.tar.gz
com.att.android.uverse-20121219-204944.tar.gz
com.att.mobile.android.vvm-20121219-204953.tar.gz
com.att.um.androidvmv-20121219-204448.tar.gz
com.aws.android-20121219-204954.tar.gz
com.careerbuilder.SugarDrone-20121219-204718.tar.gz
com.devuni.flashlight-20121219-204654.tar.gz
com.dominospizza-20121219-204542.tar.gz
com.duduapps.craigslistfree-20121219-204542.tar.gz
com.ea.tetrisfree_na-20121219-204932.tar.gz
com.ebay.mobile-20121219-204552.tar.gz
com.espn.score_center-20121219-204826.tar.gz
com.evernote-20121219-204602.tar.gz
com.facebook.katana-20121219-204621.tar.gz
com.gamestar.pianoperfect-20121219-204756.tar.gz
com.google.android.stardroid-20121219-204659.tar.gz
com.greatclips.android-20121219-204659.tar.gz
com.imangi.templerun-20121219-204915.tar.gz
com.imdb.mobile-20121219-204702.tar.gz
com.instagram.android-20121219-204708.tar.gz
com.jawbone.companion-20121219-204719.tar.gz
com.joeykrim.rootcheck-20121219-204826.tar.gz
com.july.cbssports.activity-20121219-204649.tar.gz
com.kb.Carrom3D-20121219-204804.tar.gz
com.keramidas.TitaniumBackupPro-20121219-205010.tar.gz
com.lastpass.lpandroid-20121219-204723.tar.gz
com.maxmpz.audioplayer-20121219-204808.tar.gz
com.maxmpz.audioplayer.unlock-20121219-204825.tar.gz
com.meijer.rx.android-20121219-204730.tar.gz
com.melodis.midomiMusicIdentifier.freemium-20121219-204849.tar.gz
com.metago.astro-20121219-204444.tar.gz
com.mxtech.videoplayer.ad-20121219-204733.tar.gz
com.netflix.mediaclient-20121219-204744.tar.gz
com.outfit7.talkingtom-20121219-204911.tar.gz
com.pandora.android-20121219-204752.tar.gz
com.photox.touchwhiz-20121219-204212.tar.gz
com.q2e.unitedfcu5017android.ufcu.uwnmobile-20121219-204953.tar.gz
com.rovio.angrybirds-20121219-204333.tar.gz
com.rovio.angrybirdsspace.ads-20121219-204352.tar.gz
com.rovio.angrybirdsstarwarshd.premium.iap-20121219-204414.tar.gz
com.rovio.BadPiggiesHD-20121219-204449.tar.gz
com.s0up.goomanager-20121219-205017.tar.gz
com.shazam.android-20121219-204827.tar.gz
com.shotzoom.golfshot-20121219-204655.tar.gz
com.skype.raider-20121219-204832.tar.gz
com.smugmug.android-20121219-204847.tar.gz
com.spotify.mobile.android.ui-20121219-204855.tar.gz
com.thewolverine.app-20121219-204944.tar.gz
com.touchtype.swiftkey-20121219-204859.tar.gz
com.trimble.allsportle-20121219-204258.tar.gz
com.vp.alarmClockPlusDock-20121219-204255.tar.gz
com.weather.Weather-20121219-204938.tar.gz
com.yelp.android-20121219-204959.tar.gz
com.yum.pizzahut-20121219-204759.tar.gz
de.heimlich.gut.solitaire.hd-20121219-204847.tar.gz
eu.chainfire.triangleaway-20121219-204224.tar.gz
jackpal.androidterm-20121219-204224.tar.gz
la.droid.qr-20121219-204813.tar.gz
net.androgames.level-20121219-204515.tar.gz
net.zedge.android-20121219-205008.tar.gz
nl.rogro.GScriptLite-20121219-204702.tar.gz
org.wikipedia-20121219-204958.tar.gz
Having the exact same problems as you. Please help. I'm also considering giving the phone back at Best Buy and having them give me a new one with ICS and leaving ICS on there. My steps are very simple. I had the stock ICS ROM from AT&T and I used Kies to upgrade to stock JB. That's it, nothing else, no rooting, nothing.
I am seeing exactly the same behavior, when wifi switches to 4G or even sometimes when bluetooth comes on, etc I will see the lockup and hang. Have to hold down power button to restart. But I don't think this is completely the issue, because even if I turn off wifi, bluetooth and only leave on 4G, then I still will see random reboots, but a lot lot less frequent. Also, I have always had 4G and I see the battery only lasting 4-6 hrs, so I think this is normal with 4G. I saw this even with ICS.
I have not done any factory reset or anything - I would assume if you use the Kies s/w to update and it leaves your files and apps on there, then it should just work. But I will try the factory reset once I backup my contacts, etc.
I'm a little shocked that people are having this problem with a newly released ROM.
abhansali said:
Having the exact same problems as you. Please help. I'm also considering giving the phone back at Best Buy and having them give me a new one with ICS and leaving ICS on there. My steps are very simple. I had the stock ICS ROM from AT&T and I used Kies to upgrade to stock JB. That's it, nothing else, no rooting, nothing.
I am seeing exactly the same behavior, when wifi switches to 4G or even sometimes when bluetooth comes on, etc I will see the lockup and hang. Have to hold down power button to restart. But I don't think this is completely the issue, because even if I turn off wifi, bluetooth and only leave on 4G, then I still will see random reboots, but a lot lot less frequent. Also, I have always had 4G and I see the battery only lasting 4-6 hrs, so I think this is normal with 4G. I saw this even with ICS.
I have not done any factory reset or anything - I would assume if you use the Kies s/w to update and it leaves your files and apps on there, then it should just work. But I will try the factory reset once I backup my contacts, etc.
I'm a little shocked that people are having this problem with a newly released ROM.
Click to expand...
Click to collapse
After several re-flashes to stock JB with root and still more freezing with WiFi, etc....I gave up and loaded a custom ROM this morning.
I'm running BlackJelly...and after about 8 hours it seems be be running great so far. It is TW JB-based...and having very few issues with it. Battery is poor but it takes a few days of charging and use I guess to get the battery / phone / ROM calibrated. AT&T Visual Voicemail is not working and the phone shows H instead of 4G LTE...but I'm sure I can fix those issues by searching through the hundreds of thread pages on that ROM is this forum.
Give it a try before you switch to ICS or trade in the phone. You can always flash back to stock un-rooted and use Triangle Away to reset flash counter.
Good luck!
Still stuck with crashing phone!
Boomer6345 said:
After several re-flashes to stock JB with root and still more freezing with WiFi, etc....I gave up and loaded a custom ROM this morning.
I'm running BlackJelly...and after about 8 hours it seems be be running great so far. It is TW JB-based...and having very few issues with it. Battery is poor but it takes a few days of charging and use I guess to get the battery / phone / ROM calibrated. AT&T Visual Voicemail is not working and the phone shows H instead of 4G LTE...but I'm sure I can fix those issues by searching through the hundreds of thread pages on that ROM is this forum.
Give it a try before you switch to ICS or trade in the phone. You can always flash back to stock un-rooted and use Triangle Away to reset flash counter.
Good luck!
Click to expand...
Click to collapse
Well...after over a week of trying it out....BlackJelly did not help me. Still had freezes / lock-ups.
I can't tell if the phone is re-booting itself or just re-launching the Launcher (I us Nova but tried stock and Apex too). The phone appears to re-boot on it's own but the up-time under status would not reset...making it seem like not a re-boot but a launcher reload or something. Pretty much same issues as with stock JB.
So I gave up and tried CM10.1 nightlies....and wow....crashing all the time now. Whereas stock JB and BlackJelly seemed to crash when I left my home or left any WiFi network or even just when I disabled WiFi while connected....CM10.1 crashes all the time while at home seemingly at random. I can get 5 hours of great use...then have it crash 5 times in an hour. Seems to crash a lot in the settings menus.
This is with my second (replacement) phone. I am just cursed!
How do I effectively use a LogCat app or something to find out what apps or services or whatever are crashing my phone? Help!
Read through this whole thread and no where did you ever mention clearing your cache. Clear your system cache/davlik cache and reboot.
cjranucci said:
Read through this whole thread and no where did you ever mention clearing your cache. Clear your system cache/davlik cache and reboot.
Click to expand...
Click to collapse
Sorry...should have mentioned that. I've cleared the system and davlik cache many times...before and after flashing. I've done full system wipes / resets, formatted my SD card...everything I can think of.
I either have a rouge app that I seem to install right away after clean flashes....or a rouge Wifi router in my house that messes up my phone even when I leave and use other networks...or a rouge ATT&T microcell that does the same....or a rogue LTE area in West Michigan....
Or a second bad phone sent from AT&T. But no form of JB seems to work for me no matter what. Guess I could run a clean install with no apps for several days...and then add in an app a day for the next 2+ months until I find the bad app...if that is even the case.
So bummed with this mess!
My phone freeze after rotation on landscape only with JB. all kind roms of JB stock, cyanogen,, aokp.
makamobile said:
My phone freeze after rotation on landscape only with JB. all kind roms of JB stock, cyanogen,, aokp.
Click to expand...
Click to collapse
Interesting....that might be what I was experiencing....but I never thought that was it....did not notice that cause/effect.
I gave up and went back to stock / rooted ICS / TW...version LH9. Loaded it yesterday and have had 24 hours of great use...no issues.
I miss JB and Google Now...but at least my phone works!
I'm not sure for stock JB but on other ROMs, you could try changing your governor and scheduler.
BWolf56 said:
I'm not sure for stock JB but on other ROMs, you could try changing your governor and scheduler.
Click to expand...
Click to collapse
When on CM10.1 I tried bumping the minimum CPU speed to 484 and 5xx (can't remember the actual numbers)....and the maximum CPU speed to to 14xx and 13xx (again, can't remember)....and this did not help.
Not sure if that is what you meant tho.
Anyway...I gave up and went back to rooted stock ICS (LH9) and the phone is working great. I've given up on JB for now. I will wait for a new major JB release from Samsung before I try again.
copy paste from gs3 verizon forum
Q: The phone keeps freezing when I go into landscape mode.
A: This has been covered many times in the thread, but to reiterate: If you are using the AOSP lockscreen you must disable "Ripple Effect" in Settings -> Lock Screen -> Lock Screen Options
Hi,
Yesterday I posted about why my Wifi and 3G didn't work after flashing CM11. With the help of of engine95 I got this to work (thanks!) but now I am running into another problem:
The GPS doesn't work. As far as I can tell the standard solution is to flash stock again and get a GPS fix, then go to back to CM. So I flashed ZVC_Stock_Root.zip again. This worked yesterday, but today it shows a message "cyanogenmod account has stopped" and reboots after a while. I have done a factory reset and wiped Dalvik cache but the message still appears.
Does anybody know how to fix this?
Delete system in recovery and re-flash ZVC stock zip to get rid of pop up message.
max12344 said:
Hi,
Yesterday I posted about why my Wifi and 3G didn't work after flashing CM11. With the help of of engine95 I got this to work (thanks!) but now I am running into another problem:
The GPS doesn't work. As far as I can tell the standard solution is to flash stock again and get a GPS fix, then go to back to CM. So I flashed ZVC_Stock_Root.zip again. This worked yesterday, but today it shows a message "cyanogenmod account has stopped" and reboots after a while. I have done a factory reset and wiped Dalvik cache but the message still appears.
Does anybody know how to fix this?
Click to expand...
Click to collapse
This ^^^^^^.
Also. when you flash to the stock ZVC, make sure everything is working and make a backup in TWRP/CWM. That way you can bounce back and forth when CM/AOSP Rom's have issue's that need to be fixed with stock. ie update profile prl, GPS.
engine95 said:
This ^^^^^^.
Also. when you flash to the stock ZVC, make sure everything is working and make a backup in TWRP/CWM. That way you can bounce back and forth when CM/AOSP Rom's have issue's that need to be fixed with stock. ie update profile prl, GPS.
Click to expand...
Click to collapse
Thanks a lot, everybody. Formatting system allowed me to boot up stock and get a GPS fix. I have backed up stock and can switch easily between CM and stock now.
It took a while but now I have a fully functioning Optimus G with CM11.