[Q] Does latest Cyanogenmod nightly work for you? - Verizon Samsung Galaxy S III

I flashed a CM nightly several weeks ago and my phone went to h*ll. I had to go back to square one and re-root, unlock again, etc. to get the phone back to operational.
Can anyone tell me if they have the current CM working normally on their SIII these days? I tried to look at reviews through ROM manager but that doesn't seem to be working.
I know everyone's experience will be a little different. Just tossing this out to see if it generates a bunch of little replies with experience.
Thanks!
******* EDIT ***** I just found the long CM 10.1 thread... I'll try and find my answer in that. Sorry if this counts as a "duplicate post."

Related

Who had CM9 before going to ten?

Long story short.
When SGS3 first came out and there were CM9 Betas, I tried them out, no major issues until I lost my IMEI, Odined back to stock, Restored no big deal. Fast forward to two days ago. I tried a CM10 Nightly, in which I F'ed up bigtime, Leaving me in the middle of work, with an inaccessible internal SD. Luckily, I still had a CM-9 20120719 Unofficial and a gapps-ics 20120429 on my external. Flashed them both had CM9 again. First thing I did was get Rom Manager, DL the 09-01 Nightly and gapps 4.1. Dirtly flashed it right over ( I intended on ODIN'ing when I got back home anyway) Boots up....
STABLE AS EVER. IMHO just as stable as CM7 on my Droid X (incredibly stable), better yet, no major bugs that many people have been reporting. Only minor issue I noticed was music being paused via notifications and currently that isn't an issue, but I've been playing with settings and apps all day, not sure what fixed it.
The reason I pose this question, is because in the Dev forums (which I'm not allowed to post in...) there are many people who say this is stable and clean, and many other people complaining about everything under the sun. My theory is that because I had to flash CM10 over CM9 I am seeing stability and no issues. 2 Days of love
Has anyone else flashed 10 over 9, and running stable? Has anyone else done so and had major issues? Am I just a lucky SOB?
I already tried finding out the status of cm9 but apparently it's a ghost ROM and nobody gave me an answer. There isn't even a thread in the dev section for it. The only thing I could find was 1 post saying it was a stable release but no links or any other info. That's it. Everybody seems to be drooling over cutting edge bugged filled nightlies of cm10 to care.
Yeah, I ran AOKP M6.1 until things started rolling on Jelly Bean. Only issue I had was no MMS.
If you google search CM9 for SGS3 there is a ton of info for it.
" To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
so I can't post links. but look for Droid Life, there is an install guide on it/
there are also install vids on youtube.

Vibrant Similarities and Best ROM for first flash on S3 and

I had the Vibrant and flashed all kinds I'd ROMs with it. Moved to the iPhone 4s and then traded that for my new S3. It was a good choice. So now I'm planning to get started flashing on this phone.
Wanted to know what is the same and what is different from the Vibrant from previous Vibrant users.
What's the best place to start flashing? I'm looking for stability and speed. Preferably more stability than stock cause stock is a little buggy honestly.
Sent from my SCH-I535 using xda app-developers app
GoodVibrant-ions said:
I had the Vibrant and flashed all kinds I'd ROMs with it. Moved to the iPhone 4s and then traded that for my new S3. It was a good choice. So now I'm planning to get started flashing on this phone.
Wanted to know what is the same and what is different from the Vibrant from previous Vibrant users.
What's the best place to start flashing? I'm looking for stability and speed. Preferably more stability than stock cause stock is a little buggy honestly.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Please elaborate on what is buggy about stock?
My question was more about everything else I posted besides that statement but to answer the question, I am getting force closes on some apps and occasionally the home screen locks up. That's what I meant by buggy.
Sent from my SCH-I535 using xda app-developers app
there's a link in my signature that should help you id post it but im on my ipad using tapatalk right now.
In before the lock
Sent from my Galaxy SIII
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
And I was hoping someone could tell me what's stable and smooth right now. Stock has been touch and go for my device and I haven't done anything to it. I'm looking for a fast non-overclocked kernel matched with a stable daily driver ROM. Any help is appreciated, dickhead comments aren't. This place has turned all elitist. This is the General forums....thought I could get away with a few simple questions with answers based on experiences, after having read through all these threads.
Speaking of which NeverendingXin, I read a lot of that thread yesterday but it seemed to give descriptions of what AOSP vs AOKP vs CM10 vs MIUI. Which I learned a lot from and I appreciate. But I was looking for more advice on specific ROMs. Anyone that could say "This ROM with this kernel has worked for me and I like it's speed" or whatever would do.
You want to find out what's stable and smooth?
Man up and make a backup of your current rom and flash away trying different roms. You'll likely end up getting different responses from different people and it isn't likely you'll have their same experience. Just find out for yourself. The guide the person above directed to you to was made to prevent threads asking what rom is stable or to use.
Sent from my Galaxy SIII
GoodVibrant-ions said:
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
And I was hoping someone could tell me what's stable and smooth right now. Stock has been touch and go for my device and I haven't done anything to it. I'm looking for a fast non-overclocked kernel matched with a stable daily driver ROM. Any help is appreciated, dickhead comments aren't. This place has turned all elitist. This is the General forums....thought I could get away with a few simple questions with answers based on experiences, after having read through all these threads.
Speaking of which NeverendingXin, I read a lot of that thread yesterday but it seemed to give descriptions of what AOSP vs AOKP vs CM10 vs MIUI. Which I learned a lot from and I appreciate. But I was looking for more advice on specific ROMs. Anyone that could say "This ROM with this kernel has worked for me and I like it's speed" or whatever would do.
Click to expand...
Click to collapse
Well in that sense the best information I can give you is that for a touch wiz ics Rom I'd use synergy, I used that for a long time and it was always super stable and smooth for me. If your looking for aosp then I'd use either liquid smooth or slim bean I'm more familiar with liquid and it's really great, but I'm trying out slim bean and it's so far been good as well. I hope this helps
GoodVibrant-ions said:
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
Click to expand...
Click to collapse
I'm from the Fascinate but I've also worked on the Vibrant.
* You don't have to worry about bml/mtd here. Which means you can flash basically everything without having to odin.
* You do have to worry about the locked bootloader. CASUAL can unlock it. Droidstyle has a sticky thread here on xda to help you with this and many other processes.
* There are excellent stock and AOSP-based ROMS. AOSP-based ROMS aren't quite 100% (but close) on RIL issues though.
*On verizon, radios are typically flashed separately and only in certain circumstances (odin package) included with ROMS.
* You DO have to worry about the IMEI issue. There are numerous threads about backing up this information and a Sticky thread with a tool for recovering it.
* If you are looking for a custom kernel check out Leankernel which is linked to in the signature of the poster above me. note that it's an AOSP kernel. Find the touchwiz version in the same forum.
Something else to bote about unlocking the bootloader, if you are going to use EZ Unlock from the market DON'T!!!! Go to root wiki and download version 1.2. For some reason 1.3 & 1.4 are wonky. The older versions are on the same thread as 1.4.
My vote for a ROM is Paranoid Android, I had some bug issues on Liquid Smooth but on PA I have had none thus far. I would reccomend flashing Paranoid Android version 2.5 instead of 2.51, there seems to be an issue for some users with the latest commits in 2.51 from what I read earlier today.
I'm sure you know how to back up you IMEI but just in case use the terminal method and the synergy flash method.
Just trying to cover most bases, I didn't know what you knew and didn't know.
Sent by one of my many Anthromorphic Personifications
GoodVibrant-ions said:
My question was more about everything else I posted besides that statement but to answer the question, I am getting force closes on some apps and occasionally the home screen locks up. That's what I meant by buggy.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The reason I asked is because stock on the S3 is as stable as you are going to get. The most stable custom Roms are going to be the ones based of stock TW and you can get them with some added tweaks. They are no more stable then stock as stock is stable as a *****. If you are getting force closes and lockups there is probably an issue with what you have installed.
Any AOSP rom will still have bugs and will be the least stable out of all the options. No matter how many people say Liquid or AOKP or CM10 or PA or MIUI is running great, they run no where near as stable and perfect as any TW rom.
If you want stability, go with a TW rom. read the different threads, mostly the last couple of pages of each which are usually about the latest release and you will know what is good and what is not.
This is what I am running and it does not get any more stable then this but then again stock was stable as ***** as well...
http://forum.xda-developers.com/showthread.php?t=1904329
Thanks guys.... this is exactly what I was looking for. As far as backing up the IMEI, I've never had to do that. Not on the Vibrant or My HTC View....so I have some reading to do there. Any tips or links to threads on that would be appreciated.
And I did have to unlock the bootloader on the View, but it's not a process I know a lot about.... so reading to do there as well.
Thanks for the tips guys. Looks like I'm going back to do some more studying.
Sent from my SCH-I535 using xda app-developers app
A very very good post explaining how to flash recoveries, roms, and just about anything else you ever would need to know:
http://forum.xda-developers.com/showthread.php?t=1762709
IMEI Backup:
http://forum.xda-developers.com/showthread.php?t=1852255
EZ-Unlock for you bootloader, download version 1.2 it is towards the bottom of the first post:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Sent by one of my many Anthromorphic Personifications
Perfect. Thanks man. I'd seen the first two threads but not the ezunlocker thread. Should be all I need to figure out how to get started and which ROM to try.
Thanks for the help guys
Sent from my SCH-I535 using xda app-developers app
PaulG1488 said:
You want to find out what's stable and smooth?
Man up and make a backup of your current rom and flash away trying different roms. You'll likely end up getting different responses from different people and it isn't likely you'll have their same experience. Just find out for yourself. The guide the person above directed to you to was made to prevent threads asking what rom is stable or to use.
Sent from my Galaxy SIII
Click to expand...
Click to collapse
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
shangrila500 said:
Something else to bote about unlocking the bootloader, if you are going to use EZ Unlock from the market DON'T!!!! Go to root wiki and download version 1.2. For some reason 1.3 & 1.4 are wonky. The older versions are on the same thread as 1.4.
My vote for a ROM is Paranoid Android, I had some bug issues on Liquid Smooth but on PA I have had none thus far. I would reccomend flashing Paranoid Android version 2.5 instead of 2.51, there seems to be an issue for some users with the latest commits in 2.51 from what I read earlier today.
I'm sure you know how to back up you IMEI but just in case use the terminal method and the synergy flash method.
Just trying to cover most bases, I didn't know what you knew and didn't know.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
rampantandroid said:
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
Click to expand...
Click to collapse
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
shangrila500 said:
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Check the PA thread for the answer - go into PA settings, go to the app settings, find the settings app in there and hit reset. My guess is that it is a bug with the current version of the ROM.
GoodVibrant-ions said:
Perfect. Thanks man. I'd seen the first two threads but not the ezunlocker thread. Should be all I need to figure out how to get started and which ROM to try.
Thanks for the help guys
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
shangrila500 said:
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
rampantandroid said:
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
Click to expand...
Click to collapse
So what ROM did you end up using? Any that you'd recommend?
Please read forum rules before posting
Questions go in Q&A
Thread Moved
Thanks
FNM

CM 10.1 RC1 Instability

Yesterday decided to finally switch over from SeanZ's Sky-JB to the RC1 version of CM 10.1. After doing so, I've started having some serious stability issues with my phone where it will randomly freeze up and start a hard reboot, then freeze with a black screen until I manually hard reboot it.
I've checked the md5 and flashed twice, then I gave up and downloaded the latest of the PACman ROM (and have checked the md5 on it too), which is really nice but has been giving me the same issues.
Does anybody have any suggestions for me to try? I've been using these custom roms for about a year now, but I've never been really good at troubleshooting. If there are any logs that would help you guys out, let me know what and how to get them and I'll send them on over. Thanks for your help!
Do some searching. It's hard to miss your answer if you searched a little.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Found some basic info on reporting logs with Lumberjack and Bootlog Uptime. I'll keep searching and check back with logs when it crashes next.
I think what jd was saying is that, your issues are known and VERY well documented in the cm10.1 thread. The cm team is working to fix the issue. I understand that it is a long thread, but the least you can do, if you are going to flash a rom, is to read at least the last couple of pages of the thread to get an idea of the current issues occurring with others.
If you'd like something stable, there is a thread in the general section that has the last stable build of cm10.1 from 4/23. You could also try the slim build from prbassplayer
Sent from my Slimmed out Skyrocket
Thanks. I've been searching through the different threads and I find a lot of problems, but not as many as I would've though with the same thing that I have. Is there a channel or blog of some sort that I can follow that has CM's status updates on the situations? I've looked through the CM 10.1 Nightlies thread over in the Dev section, but I don't see much from the OP in way of updates.
Because the OP is busy trying to fix the problems. roger_n and carvsdriver have been doing the bulk of the organizing and feedback loop, while topprospect has been busy trying to fix it. Don't judge a book by it's cover, you gotta read...

S3 constantly crashing

Hello,
I bought a VZW Galaxy S3 at the end of May. I left Touch Whiz on it for about a week before I couldn't stand the look of it any more, It also started freezing and I would have to hold the power button down to reboot it. This would happen 2-3 times a day so I decided to go with a custom rom. I had rooted and installed custom roms on my Nexus 7 several times before so I felt comfortable doing it on my S3. I was able to root it and unlock the bootlader and I installd TWRP as my custom recovery. I flashed the AOKP rom and was using that for several weeks. Initially it worked great and crashed maybe once a day but I figured that was normal for a custom rom. After a few weeks it started to crash more and more. I finally ended up restoring the phone from an AOKP backup I had made the first day. That seemed to help a bit. After it started to get worse again I switched to SlimBean. This one was the worst. It worked good for a few days then crashed constantly. Finally, after getting extremely frustrated I flashed CM 10.1.2 I decided to go with one of the Milestones to be on the safe side. This was working great until now. It constantly freezes and crashes. Also, many of the apps crash. I am just wondering if this is an issue with how I unlocked and rooted it or if this is an issue with my phone? I have also noticed I have terrible reception with any rom even stock. What roms would you guys recommend as a very stable one? I know CM is supposed to be. Any help would be greatly appreciated. Sorry for the long post I wanted to make sure I included enough information.
Thanks.

CM11 new nightly (20150802)

I saw a new "nightly" has been pushed out for the Relay. Based on the changelog (fixing integer overflows and underflows), this looks like a fix for Stagefright.
I've updated from within the 20150607 nightly, and so far, everything looks good. My GPS and camera still work fine, and I didn't bother toggling any settings before updating.
At least I have ONE phone with a Stagefright fix. It's kind of ironic that it's the oldest of my Androids.
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
So I guess it's time to bite the bullet and do the double-twist-and-backflip GPS fix. Let me go over this for a moment, to get it straight.
I need a new CWM recovery, latest'n'greatest.
I need and old 10.1 or maybe 10.2 ROM image.
I need the old baseband firmware to go with the old ROM image.
Is this the full list?
There have been numerous links to all three of these, but I tried last week, and at least some of them have gone stale. Does anyone have a current and working set of links for them?
My wife's Relay is still at CM11M8, and really it's about time I got her properly flashed forward, especially now with Stagefright and Freak both fixed. We've locked out on Stagefright so far because we have voice-only through PureTalkUSA, only do data on wifi, and therefore don't do MMS.
GPS fix:
You need a CM10.1 build (Only ones ever produced were 'experimental'), the ICS stock baseband (modem) and the JB stock baseband. Recovery doesn't particularly matter, so long as you can flash images, but I still recommend the CWM that has been around for a while (I've tested it, it works fine even with upcoming Images)
Procedure:
Boot into recovery, run a full backup on your device.
flash ICS baseband
Flash CM10.1 Image
Factory Reset
Boot into system (Not sure if this is needed, but I always do.)
Once system boots up, shut system down.
Open phone, pull battery.
Wait ~30 seconds, replace battery.
Boot phone.
Once system boots up, (If you have a way to test it, GPS should work now). Reboot into recovery.
Flash JB baseband.
Restore your system backup.
Reboot into system. Your GPS should now work with your current system.
I posted a reply into a thread, there was an up to date link with just the modem... I can confirm that running on CM nightly (june something) I have no issues with GPS, wifi 2.4ghz band doesnt work with bluetooth enabled though
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
phred14 said:
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
Click to expand...
Click to collapse
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
dzl said:
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
Click to expand...
Click to collapse
I got my Relay about a year and a half ago for Christmas, mostly as a learning vehicle, but also for the convenience. The plan from the get-go was to put Cyanogenmod on it. For a while it was wifi-only, then a few months later my wife decided she wanted one, and I found the Family Flex Plan at PureTalkUSA that let us have two phones for the the cost of a Virgin Mobile and TracFone. (What we had before) It's also one of the few ways to get voice-only, and use wifi for data.
The Relay is getting a bit long in the tooth, and perhaps most discouraging "aging" side of it is the ramp-down here. However anything I get will be CM-ready from the get-go.
Flashed the latest CM11 nightly today. No major bugs so far with moderate use throughout the day. So much faster than my Xperia with the stock firmware, actually enjoying Android again.
Sent from my SGH-T699 using XDA Free mobile app
20150823
I had been running M8 since it came out until last weekend. Decided to do a complete wipe and try for the newest nightly to fix the Stagefright bug. Things went real smooth. GPS is working faster than ever.
Everything runs like a dream... except the adaptive light sensor. Adaptive brightness is not working at all. I've check the sensors and the Lux sensor is working fine. If I turn on adaptive brightness, and then adjust, the settings crash. Anyone else experiencing anything like this?
Yeah that is one thing that I have noticed as well, the auto brightness doesn't work. Can't say I've attempted to diagnose it at all though.
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
TPMJB said:
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
Click to expand...
Click to collapse
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
phred14 said:
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
Click to expand...
Click to collapse
I would like for updates to CM12, but we only have unofficial versions of CM12. I am a noob at compiling and I hear it is an arduous task to get it working.
Magamo said:
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
Click to expand...
Click to collapse
Some time between then and now (some time in September, I believe) the stagefright fixes were backported to the omni-4.4 branch. I have a build from this running on my relay right now and Zimperium gives it a clean bill of health.
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
kodimagnyl said:
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
Click to expand...
Click to collapse
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
i have a rooted stock rom, can i move to the latest cm11 nightly build?
phred14 said:
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
Click to expand...
Click to collapse
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
kodimagnyl said:
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
Click to expand...
Click to collapse
Can't reach the second link, but I've already got a copy of the current modem, the old one is what I've been missing. Things are starting to get busy, so I don't know how soon I'll be able to try it.
BTW, I've been told to do a "nandroid backup", then wipe and load the back-level stuff, do the GPS fix, then a "nandroid restore". I'm going to presume that the backup / restore doesn't handle the modem, and on my way back from back-level, I'll first have to use heimdall to reload the current modem?
Thanks

Categories

Resources