I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive been using several 4.3 roms without one issue. Dirty Unicorn and Carbon have been prefect so far. Using latest twrp, full wipe and stock kernels.
Noremacam said:
I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
Click to expand...
Click to collapse
What revision is your phone? Rev4? Rev5? My phone is a Rev0 and I'm not having any problems with running AOSP based ROMs.
I did too. I'm not sure WTF was going on, but ASOP/CM would be great for about a month, and then it'd start random rebooting. After it'd start random rebooting, the way to stop it would be to ODIN back to stock, and start over. Clean installs, nandroid restores, full formats.. None of it worked.
So here I stay on a crappy 4.1.2 TW ROM.. itching to return, but not really seeing enough improvements to warrant another go.
How are you restoring apps and data? I had problems after restoring via titanium backup, but when I restored selectively (just apps and data I really needed) with helium it's running fine.
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Noremacam said:
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Click to expand...
Click to collapse
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Check in terminal emulator.
Su (enter)
cat /proc/cpuinfo (enter)
This will give you the revision number and a lot more about your phone.
I have "rev 4" on my brown GS3 and have been running CM10.1.3. The only time my phone crashes/reboots is when I attempt to use the front facing camera with a third party camera app.
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Noremacam said:
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Click to expand...
Click to collapse
Download aLogCat from the play store and start the app. Then trigger the crash
Sent from my SCH-I535 using Tapatalk
What do you do if you can't cause it to crash? Mine are always totally random. It'll crash during a call, it'll crash while web browsing, it'll crash while locked in my pocket.. The only time it won't crash is when you want it to!
Do you just end up with a giant log file then or what?
Related
Hey I just wanted to know peoples opinions on what is the best CM10 Rom so far. Especially considering the things that dont work like MMS or tethering or Netflix (I dont think any work with it though)
I like it. It's clean and boost free.
Sent from my SCH-I535 using xda premium
Just loaded everything looks good except camera or gallery doesn't work. Am I missing something?
AndroidGraphix said:
I like it. It's clean and boost free.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which CM10 rom are you running? Invis? The official CM?
llama555 said:
Which CM10 rom are you running? Invis? The official CM?
Click to expand...
Click to collapse
Official CM10 nightly
mms aint working yet but should in next official nightly. which should be in a few hours... other than that, official definitely had the most stable release!
NFC also isn't working but hopefully it gets fixed soon including MMS.
You'll probably just want to roll with the officials. Most everything you want has already been or is soon to be merged.
Anyone get WiFi tether to work? It worked for me on CM9
Just a question. Does CM10 have the long press volume feature to skip tracks while the phone is asleep? Love this about synergy
Sent from my SCH-I535 using xda app-developers app
What happened to the official thread in the original development sub forum? :what:
Sent from my SCH-I535 using xda premium
llama555 said:
Hey I just wanted to know peoples opinions on what is the best CM10 Rom so far. Especially considering the things that dont work like MMS or tethering or Netflix (I dont think any work with it though)
Click to expand...
Click to collapse
i have used about a day and here are my thought
unlocked bootloader
i have cleaned cache format factory reset before install
after boot i have loaded my app with data not bloatware with toolbox pro
using go launcher no live wall paper and juice defender
rest of app are... well just application and few games.
and here is real pro and cons
Pro
Fast, it does the job, google and now other jb features are works perfectly
unlock bootloader can be easily done thanks you adam.
boot time is faster than what i used to use AOKP milestone 6.1
Con
UNSTABLE, within half a day rebooted like 3~4 times while i was doing something
who know how many times it rebooted while i wasnt looking.. it seems more because from battery status
there are few blank spots. i have no idea what is wrong kernel perhaps?
i am not sure i thought CM is made from AOSP so i thought it should be pretty stable but i guess not.
also i have car blue tooth device with handset free (GROM) it wont connect and my logitech one works perfectly
DATA also not stable it think for battery it tries to turn it off (i think it's from juice defender) but takes about 10~15 seconds before i get the data
if you dont have problem with rebooting at random times, some glitches and no softkey (it's nightly so i cant really say it's bad rom)
this is the ROM.. it's faster than any rom i have tried.. what do you guys think??
maybe i should have tried longer but for me it was too unstable.
does cm10 have any critical bugs??
So, I was curious about a couple things.
First, how do nightlies work? Do you have to go and download a new file every single night and flash it? Or is there something working with the ROM that will flash a new version for you as it comes?
Second, I was curious as to when you guys think that CM10 for the SGSIII will be stable to the point where all major things, data, keys, gallery, camera, MMS, bluetooth, etc, are working reliably? I'm incredibly pleased with the stock experience, but there's always something to be gained from custom ROM's and I'm looking forward to being able to use CM10 I just don't want to miss a big part of my phone.
Not meaning to hijack the thread or anything! I'll throw in my two cents too by saying that I'd recommend the official CM10 based on the fact that MMS seemingly works currently and I'm unsure of how it's doing on the unofficial ROM.
syungyou said:
i have used about a day and here are my thought
unlocked bootloader
i have cleaned cache format factory reset before install
after boot i have loaded my app with data not bloatware with toolbox pro
using go launcher no live wall paper and juice defender
rest of app are... well just application and few games.
and here is real pro and cons
Pro
Fast, it does the job, google and now other jb features are works perfectly
unlock bootloader can be easily done thanks you adam.
boot time is faster than what i used to use AOKP milestone 6.1
Con
UNSTABLE, within half a day rebooted like 3~4 times while i was doing something
who know how many times it rebooted while i wasnt looking.. it seems more because from battery status
there are few blank spots. i have no idea what is wrong kernel perhaps?
i am not sure i thought CM is made from AOSP so i thought it should be pretty stable but i guess not.
also i have car blue tooth device with handset free (GROM) it wont connect and my logitech one works perfectly
DATA also not stable it think for battery it tries to turn it off (i think it's from juice defender) but takes about 10~15 seconds before i get the data
if you dont have problem with rebooting at random times, some glitches and no softkey (it's nightly so i cant really say it's bad rom)
this is the ROM.. it's faster than any rom i have tried.. what do you guys think??
maybe i should have tried longer but for me it was too unstable.
Click to expand...
Click to collapse
Ummmm.......I dont have any of those issues....I recommend full wipe and retry...with newest official from get.cm
Fallen224 said:
So, I was curious about a couple things.
First, how do nightlies work? Do you have to go and download a new file every single night and flash it? Or is there something working with the ROM that will flash a new version for you as it comes?
Second, I was curious as to when you guys think that CM10 for the SGSIII will be stable to the point where all major things, data, keys, gallery, camera, MMS, bluetooth, etc, are working reliably? I'm incredibly pleased with the stock experience, but there's always something to be gained from custom ROM's and I'm looking forward to being able to use CM10 I just don't want to miss a big part of my phone.
Not meaning to hijack the thread or anything! I'll throw in my two cents too by saying that I'd recommend the official CM10 based on the fact that MMS seemingly works currently and I'm unsure of how it's doing on the unofficial ROM.
Click to expand...
Click to collapse
Again, its fully stable. In your "second" part, literally every single thing you listed is fully working and stable. Except soft keys which were actually disabled because they have the same purpose as hard keys and just take up valuable real estate. Yes, nightlies are every night but you can dirty flash if you're lazy. You only really need to flash once a major fix or update has been merged. Just follow the changelogs.
And for you, based on what you reported as not-working, I'd also say you got a bad flash or something. Mine runs almost identical to what stock JB ran on my GNexus. Only better with mods
Sent from my Galaxy S3 using Tapatalk 2
Regarding Twistedumbrella 4.04 Rom found here:
I've never donated to a developer (shame on me) but I just did for this one. I really want to keep my Thunderbolt going cause I'm off contract and have an unlimited data plan. Like some are reporting, the most recent builds of this ROM gave me a boot loop and I can't run them, but anyone considering trying this rom I encourage you to try the 12/06 edition at the link below. This 12/06 installed for me and ran just fine, and I am SO pleased at the increased speed AND battery life that I perceive I am getting. This ROM is not loaded with the HTC sense overhead, and things seem much snappier all around. I was about to ditch my Thunderbolt because things had slowed to molasses using the original BAMF 4.04 rom, but this one is working great!
Here's the link (copied from the thread linked above)
THANK YOU TWISTEDUMBRELLA
I too would like to join in and say thanks to twisted. His rom is the only thing that is keeping me on the Tbolt. I am one of the few with a model that gets bootloops from the newer versions but 12/06 works great for me.
I'm grateful too...
Ionace7 said:
I too would like to join in and say thanks to twisted. His rom is the only thing that is keeping me on the Tbolt. I am one of the few with a model that gets bootloops from the newer versions but 12/06 works great for me.
Click to expand...
Click to collapse
I too am grateful for the twisted ROM. I also have the boot loops on versions younger than 12/06. I also have the serial number ending in "A". However, my Bolt is working quite well with the 12/06 ROM!
Thanks Twisted!
bbshopper said:
I too am grateful for the twisted ROM. I also have the boot loops on versions younger than 12/06. I also have the serial number ending in "A". However, my Bolt is working quite well with the 12/06 ROM!
Thanks Twisted!
Click to expand...
Click to collapse
What 4ext recovery version are you using? I'm using rc8 and all his builds boot fine. Hall is using rc5 and doesn't get them either. I'm just curious if the rc9 version of the recovery has a bug that is causing the boot loops.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
What 4ext recovery version are you using? I'm using rc8 and all his builds boot fine. Hall is using rc5 and doesn't get them either. I'm just curious if the rc9 version of the recovery has a bug that is causing the boot loops.
Click to expand...
Click to collapse
As mentioned in the Dev section thread, the bootloops coincide with a certain version of hardware of the Tbolt. Specifically, those with a TBolt with a model number ending with an "A" are affected by the bootloops. It doesn't have anything to do with the recovery software.
Bingo. I pulled my battery to check the serial number and yes indeed, mine ends "A." But like is also mentioned above, my 12/06 rom is running VERY well, so I'm completely happy where I am.
But thanks for pointing this out -- that saves me a lot of time from being tempted to play with the recovery software or partitions or anything else.
Ionace7 said:
As mentioned in the Dev section thread, the bootloops coincide with a certain version of hardware of the Tbolt. Specifically, those with a TBolt with a model number ending with an "A" are affected by the bootloops. It doesn't have anything to do with the recovery software.
Click to expand...
Click to collapse
Ionace7 said:
As mentioned in the Dev section thread, the bootloops coincide with a certain version of hardware of the Tbolt. Specifically, those with a TBolt with a model number ending with an "A" are affected by the bootloops. It doesn't have anything to do with the recovery software.
Click to expand...
Click to collapse
That still doesn't take away from the fact that the recovery could be causing the problem. It's possible that whatever is different with the hardware could have an affect on the recovery as well.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
That still doesn't take away from the fact that the recovery could be causing the problem. It's possible that whatever is different with the hardware could have an affect on the recovery as well.
Click to expand...
Click to collapse
Good point, nonetheless it seems there may be a work around of restoring just the boot data from a earlier (12/06) version of the rom will make the newer ones work while sacrificing the camera (it stops working).
Update: (don't want to keep adding off-topic posts) The work around worked for me without any problems (camera worked) when going from 12/06 to 12/19. Also the new 12/28 update doesn't bootloop for me.
But for a majority of tbolt usrs if u got a p/n ending with an "A", "B" and you experience any issues i.e. bootloops I caution you to stay away from ics for now until something stable comes out if it ever will. Lol!
For those with p/n "C", "XC" etc happy flashing. Seems these experience random reboots at some point but do not have major issues as the ones above.
Just thot I'd put this out there for those going thro bootloops and its driving them nuts!
Sent from my ADR6400L using Tapatalk 2
I cannot believe anyone actually used the BAMF ICS rom for more than 5 mins. that rom is full of so much wack. Never had any bootloops with any of Twisted builds and ive tried pretty much all of them since day one. TWRP...
a bit of info on this particular bootloop for those not following the thread:
-flashing a previous working boot partition from recovery seems to get you past the loop (e.g. flash new rom, restore boot from 12/06 backup)
-alternatively, the 12/28 version on page 28 of the thread works with no loop on my particular hardware. i think twisted is still working on a final build though, which could potentially return to bootlooping if he hasn't isolated the problem.
viceversa said:
I cannot believe anyone actually used the BAMF ICS rom for more than 5 mins. that rom is full of so much wack. Never had any bootloops with any of Twisted builds and ive tried pretty much all of them since day one. TWRP...
Click to expand...
Click to collapse
HA! I deserved that, vice versa. I know enough to be dangerous to myself most of the time but that's about it. The BAMF rom looked so much prettier I stayed with it but it ended up a nightmare, as you suggest. I'm now almost on my 24th hour of the 12/06 rom and no spontaneous resets at all, MUCH better batter life, MUCH snappier in general, and I am MUCH happier with my thunderbolt! Presumably there's things that need to be improved past 12/06, but I'm not so much of a power user (obviously) even to have found them.
freecicero said:
HA! I deserved that, vice versa. I know enough to be dangerous to myself most of the time but that's about it. The BAMF rom looked so much prettier I stayed with it but it ended up a nightmare, as you suggest. I'm now almost on my 24th hour of the 12/06 rom and no spontaneous resets at all, MUCH better batter life, MUCH snappier in general, and I am MUCH happier with my thunderbolt! Presumably there's things that need to be improved past 12/06, but I'm not so much of a power user (obviously) even to have found them.
Click to expand...
Click to collapse
If you liked the bamf leak then try NuSense out. It is a fantastic rom that uses parts from it and a desire hd rom. For a snappier version that is more stable than the aosp rom try unsense.
Sent from my ADR6400L using Tapatalk 2
I've never had boot loops with any of twisted's releases. I did however had the occasional random reboot. I'd go to answer a phone call and this sucker would just reboot on me for no reason.
Sent from my ADR6400L using Tapatalk 2
rafaelvelasquez2 said:
I've never had boot loops with any of twisted's releases. I did however had the occasional random reboot. I'd go to answer a phone call and this sucker would just reboot on me for no reason.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
The only time I heard of that was when people used the leaked radios or the combination radio made from the leak and .19 radio.
Sent from my ADR6400L using Tapatalk 2
Hey guys I have run into a problem I would appreciate any comments on -- I've been all over the internet reading about the failure of Google Maps/Navigation to read street names in Andriod 404 without finding anything that helps me. I already had Ivona voice installed, and I even installed SVOX to see if that what help, but the app refuses to use anything but the standard voice, and it never gives street names, just "turn right, turn left" etc.
I've done all the clear data and cache suggestions and that isn't helping.
Does anyone know if a fix was developed that I can apply using this 12/6 ROM? other than that this rom is working great for me, and I suspect the problem isn't in the rom itself. I'd even gladly download an older version of the MAP apk if I could find it - I don't use the advanced MAP features at all.
Thanks for any suggestions.
freecicero said:
Hey guys I have run into a problem I would appreciate any comments on -- I've been all over the internet reading about the failure of Google Maps/Navigation to read street names in Andriod 404 without finding anything that helps me. I already had Ivona voice installed, and I even installed SVOX to see if that what help, but the app refuses to use anything but the standard voice, and it never gives street names, just "turn right, turn left" etc.
I've done all the clear data and cache suggestions and that isn't helping.
Does anyone know if a fix was developed that I can apply using this 12/6 ROM? other than that this rom is working great for me, and I suspect the problem isn't in the rom itself. I'd even gladly download an older version of the MAP apk if I could find it - I don't use the advanced MAP features at all.
Thanks for any suggestions.
Click to expand...
Click to collapse
Wrong forum my friend
Sent from my ADR6400L
Wifi Working at all?
Has anyone gotten any of the WiFi apps to work on this? Barnacle works on Ad-hoc, but I can't seem to get even the Wifi Tether app to work. Thanks guys.
pdub517 said:
Has anyone gotten any of the WiFi apps to work on this? Barnacle works on Ad-hoc, but I can't seem to get even the Wifi Tether app to work. Thanks guys.
Click to expand...
Click to collapse
Wireless tether has to be setup using the Google nexus one profile. Routing fix checked and wake lock checked.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The only time I heard of that was when people used the leaked radios or the combination radio made from the leak and .19 radio.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Really, I been only getting the random reboots, however I am on the leaked ICS radio.
Maybe I should switch back to the stock .19 radio.... Unless the new HTC ICS radio comes out soon with this update.
Does anyone know where the radio forum went too?
I've tried several 4.2.2 ROMs (LiquidSmooth, CM, SlimBean, Carbon).... each time with full wipes.
With each one, I have an issue where the screen will start acting up, basically covered in black/white lines (and glitching on and off).
Anyone else have this issue? Something wrong with my phone?
I'm going to try SlimBean 4.2.1 next, to see if it is a 4.2.2 issue.
kurruptor said:
I've tried several 4.2.2 ROMs (LiquidSmooth, CM, SlimBean, Carbon).... each time with full wipes.
With each one, I have an issue where the screen will start acting up, basically covered in black/white lines (and glitching on and off).
Anyone else have this issue? Something wrong with my phone?
I'm going to try SlimBean 4.2.1 next, to see if it is a 4.2.2 issue.
Click to expand...
Click to collapse
I jusut had same rpblem with 4.1.2 but cant seem to even get into odin. Phone is just lcked
★☞ [Rom][4.1.2] Jelly 'Beans' - Build 14 [04/04/13][Fully Customizable][VRBMB1] ☜★
http://forum.xda-developers.com/showpost.php?p=39924705&postcount=8081
could it b kernel?
fallentimm said:
I jusut had same rpblem with 4.1.2 but cant seem to even get into odin. Phone is just lcked
★☞ [Rom][4.1.2] Jelly 'Beans' - Build 14 [04/04/13][Fully Customizable][VRBMB1] ☜★
http://forum.xda-developers.com/showpost.php?p=39924705&postcount=8081
could it b kernel?
Click to expand...
Click to collapse
Mine doesn't lock up completely. I can actually still interact with apps (provided I know what to do without seeing the screen properly). It is sporadic as well, so if I reboot. It won't happen immediately... sometimes within minutes, sometimes within hours, sometimes not until the next day.
ive run four to five 4.2.2 roms and never had this happen.
Same results on Slimbean 4.2.1. Hmmm..
Getting similar results even on CleanROM. Completely different kernel.
Back to full stock I guess. Hopefully my phone didn't get messed up.
I had the issue and went back to clean room 5.6 and the problem disappeared
Disable hardware overlays in developer options... Used to be a problem with AOSP roms on this beautiful baby I'm using right now. That always fixed it... Be aware, doesn't always stick after reboot
Sent from my HTC Droid Incredible 2 using Tapatalk 2
Thanks faeh, that looks like the problem I have. Couldn't figure out what word to search for existing known issues. "Flickering" never came to mind.
No problem
Sent from my SCH-I535 using Tapatalk 2
So to start, my phone is rooted and the bootloader is unlocked. I should also have the latest modem flashed. The problem is that the screen will freeze upon some calls, not all of them, and prevents me from doing anything. I can still hear everything that's coming through but the screen itself is just unresponsive. At that point, I usually just pull the battery and reboot and make the call over again. It hasn't happened to me immediately after a battery pull yet.
This problem has occurred to me on multiple roms. I initially noticed it on LiquidSmooth's 3/16/13 stable build and so I re-flashed it making sure to do a clean install. It kept on happening so I kept switching roms and am now on Carbon Rom and it hadn't given me any problems until just now (been on Carbon for over a week). All of my rom installs are done with clean flashes so I really don't know what's going on at this point.
Any help would be absolutely fantastic!
it's a known issue on AOSP roms
Try using the latest Official CM10.1 nightly. Best to do reset, clean install. That issue has pretty much been squashed on the latest builds.
Sent using Tapatalk
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app
kupnooduls said:
I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I am currently using Paranoid Android which is based off cyanogenmod, and I get the same thing. Phone freezes mid call. I was having general freezing problems across the board until I installed PA, I kept thinking is was my launchers, etc, but I am bare bones right now and it still does it periodically, and have once had it do it directly after a battery pull.
When mine does it, the call drops.
Two things..
First, I have been having the same phone freeze issues as everyone else, tried different roms, the dummy file fix, all kinds of different things going through this forum. I wanted to do everything I could possibly do before posting about it.
I am using Paranoid Android. I noticed the cyanogenmod version listed in the phone info is [email protected]#1 Tues March 19
Is this just a PA version number or actually the kernel number? What if I was to flash the newest stable kernel to my PA?
ALSO
I noticed when my phone does its freeze up thing, the battery has been at 53-57%. It does not seem to do it any lower or higher battery percentage. Is it possible that its actually a problem with the battery or the battery percentage programming??? It just seemed odd that it always seemed to be around the same % when it happened.
Any thoughts????
I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.
Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app
Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.
had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.
I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.