Related
Now that the new update has been leaked we have new firmware with a new radio (.0320). Has anyone seen any differences between this one and .0312, the previous newest radio? Would it be worth it to flash the new firmware if I was running a custom rom (jelly bean paranoid android)?
I just realized this should probably be in q and a. Can this be moved?
Sent from my Incredible 2 using xda app-developers app
I heard doesn't seem to work with SOME roms
Sent from my Goonified Paranoid Jelly Droid Incredible 2
I tried the latest ota Rom (minus bloat) with the new firmware and it worked fine
Sent from my ADR6350 using xda app-developers app
new radio on cm10
I tried the .0320 radio on aeroevan's cm10 and it just hung on boot. I then did a restrore to the CWM backup I made before I installed it and my phone booted fine and says it still has the new radio. Wierd... Does CWM recovery not backup and restore the radio?
chuck864 said:
I tried the .0320 radio on aeroevan's cm10 and it just hung on boot. I then did a restrore to the CWM backup I made before I installed it and my phone booted fine and says it still has the new radio. Wierd... Does CWM recovery not backup and restore the radio?
Click to expand...
Click to collapse
No, it doesn't, it was probably because of the other firmware stuff. But cwm does not back up the radio
Sent from my ADR6350 using xda app-developers app
chuck864 said:
I tried the .0320 radio on aeroevan's cm10 and it just hung on boot. I then did a restrore to the CWM backup I made before I installed it and my phone booted fine and says it still has the new radio. Wierd... Does CWM recovery not backup and restore the radio?
Click to expand...
Click to collapse
More accurately said...your radio is not affected by flashing roms. Only if you flash something specifically at the radio level.
As for CM10 hanging on boot, it has been a little finicky. I get bootloops, but eventually it brings itself out of the bootloop. If it is truly hanging, try changing the order of flashing...I do rom-->kernel-->gapps. I used to do gapps before kernel, but this seems to bring consistently better results. Don't have any idea why that would be. Also, I think you have to have either the 12 or 13 kernel for CM10 at this point.
The first time u flashed back to cm10 did you forget to flash a kernel? That could cause it not to boot and your backup that worked would have the kernel included where your fresh install wouldn't. This could explain what happened.
Forgot to quote the post but this is in response to chuck
Sent from my ADR6350 using xda premium
New firmware caused bootloop issues for me even after I wiped system, data and cache. I described it a separate bthread in Q
And A. That said, I didn't have good description with the latest radio. Always had the best luck with 622, which is an old gingerbread radio.
Sent from my Incredible 2 using xda app-developers app
no issues with AOKP. I did have a few issues the cwm and i think i just need to reflash recovery. Otherwise, no issues so far.
adammwhiles said:
The first time u flashed back to cm10 did you forget to flash a kernel? That could cause it not to boot and your backup that worked would have the kernel included where your fresh install wouldn't. This could explain what happened.
Forgot to quote the post but this is in response to chuck
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Kernel should be included in Rom, always has been, unless this is different, I don't know been away for a while...
Sent from my ADR6350 using xda app-developers app
jeremytn86 said:
Kernel should be included in Rom, always has been, unless this is different, I don't know been away for a while...
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
Some lately have been different
Sent from my ADR6350 using xda premium
Running Nit's TSM UKB Evolution 2.0 now with the newly leaked ics firmware with the .0320 radio, mobile data signal is a bit stronger, by as much as 8 to 10 dBm and WiFi isn't dropping out (was seeing random "X" instead of the signal bar before) - haven't run into any FC issues yet. screen transitioned is still a bit laggy sometimes when changing home screen - battery life is on par with other similar roms.
jeremytn86 said:
Kernel should be included in Rom, always has been, unless this is different, I don't know been away for a while...
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
The CM10 roms need a kernel flash following rom install:
http://forum.xda-developers.com/showthread.php?t=1805773
Notice the "NOT optional" part.
Letitride said:
Running Nit's TSM UKB Evolution 2.0 now with the newly leaked ics firmware with the .0320 radio, mobile data signal is a bit stronger, by as much as 8 to 10 dBm and WiFi isn't dropping out (was seeing random "X" instead of the signal bar before) - haven't run into any FC issues yet. screen transitioned is still a bit laggy sometimes when changing home screen - battery life is on par with other similar roms.
Click to expand...
Click to collapse
Thanks Letitride. Ill give this a shot today.
adammwhiles said:
The first time u flashed back to cm10 did you forget to flash a kernel? That could cause it not to boot and your backup that worked would have the kernel included where your fresh install wouldn't. This could explain what happened.
Forgot to quote the post but this is in response to chuck
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
I didn't reflash the rom. I just did a restore from the backup I made right before I flashed the new radio. I have been running aeroevan's kernel
v.12 with Adreno drivers and cm10 7/30 build for 2 weeks now with no complants.(except for the FFC and video camera.)
If you read this post:
http://forum.xda-developers.com/showthread.php?t=1134451&page=51
You will see other people you have gotten it to work by clearing the cache after installing the .0320 radio so maybe the restore had the same effect. I didn't see any improvements as far as signal goes so I just reflashed the .0312 radio to avoid any problems. I may feel froggy this weekend and reinstall the .0320 radio this weekend and try the clear cache trick out. If so I will report back with the results.
Rushead said:
The CM10 roms need a kernel flash following rom install:
http://forum.xda-developers.com/showthread.php?t=1805773
Notice the "NOT optional" part.
Click to expand...
Click to collapse
No I didn't. Didn't really read op, didn't flash this, just saw his post, like I said was gone a while, had never seen rom without kernel, until now. ..
Sent from my Incredible 2 using xda app-developers app
I ended up installing the firmware then doing a full wipe before flashing my last ROM. So basically all I was left with was the new radio. Everything works so far.
Sent from my Incredible 2 using xda app-developers app
I tried just flashing the new radio .320 without the Rom and my aero 8/21 hung at boot. So I loaded the leaked ics Rom and I had the WiFi killing the data bug so I flashed tazz's and macros latest 8/28 build and my service is pretty solid. Ive seen better battery life and less service jumping with this radio. When and if aero updates his cm10 I'm going to try it out and see if things go the same for his Rom. I'm in love with the cm10 builds
Sent from my HTC Incredible 2 using xda app-developers app
After you flash radio on areo's cm10 just wipe cache will boot fine then.
Sent from my Incredible 2 using Tapatalk
so i thought id take it upon myself to download the latest aokp jb build 3 and flashed it over aokp m6 after i did a full wipe and it installed perfectly but i rebooted my phone to check something and when i did it bootlooped i panicked cause i couldn't restore a backup or get it running again i got REALLY LUCKY and for some reason i was able to get my backup to restore after countless times of trying so now I'm back on m6 i fear of going back to aokp jb until i know it's safe to go from aokp m6 to aokp jb i can't brick another phone has any had this problem or i was just unlucky or what
Sent from my Galaxy Nexus using xda app-developers app
Try to wipe all data and reflash the rom,(including cache+dalvik cache) because every time you flash a rom with a different version of Android this procedure should be done to avoid problems like this
Wipe/Factory Reset
Wipe everything/factory reset and reflash rom and gapps. This will fix your issues. Good Luck!!
I wiped everything the first time im sorta scared to go through it again to see if it will work cause when i flashed it ran perfectly but i noticed when i was trying to change my softkey icons rom control kept force closing for some reason so that's when i rebooted and then i got the boot loop
Sent from my Galaxy Nexus using xda app-developers app
dont complain about issues if you dirty flash roms.
if you have problems with a dirty flash, wipe and then reflash.
Zepius said:
dont complain about issues if you dirty flash roms.
if you have problems with a dirty flash, wipe and then reflash.
Click to expand...
Click to collapse
I flashed everything perfect i wiped everything before i flashed the Rom so i didnt dirty flash ive been flashing roms since the first droid so i know how to flash unfortunately flashing this build of aokp didn't go to well for me
Sent from my Galaxy Nexus using xda app-developers app
I'm confused you flashed over M6 and didn't dirty flash? AOKP always recommends a full wipe. I flashed Build 3 last night, clean without a single issue. As for bricking, it's a Nexus. Kinda hard.
Sent from my Nexus 7
masully84 said:
I'm confused you flashed over M6 and didn't dirty flash? AOKP always recommends a full wipe. I flashed Build 3 last night, clean without a single issue.
Sent from my Nexus 7
Click to expand...
Click to collapse
I didnt flash directly over m6 without wipeing everything first before flashing the new aokp jb b3 i think thats where people getting alil confused
Sent from my Galaxy Nexus using xda app-developers app
jave16 said:
so i thought id take it upon myself to download the latest aokp jb build 3 and flashed it over aokp m6 and it installed perfectly
Click to expand...
Click to collapse
you said you just flashed it over.
Zepius said:
you said you just flashed it over.
Click to expand...
Click to collapse
My mistake i was trying to say coming from m6 i flashed from that to aokp jb after i wiped everything first
Sent from my Galaxy Nexus using xda app-developers app
Factory reset
Wipe cache
Wipe dalvic cache
Format system
Flash build 3
Flash gapps
Fix permissions
Reboot
I have been looking all over and my eyes are about ready to have a critical meltdown.
I have a T-Mo T-989 (Hercules) and have been looking for a JB ROM all night and found some shady threads or ROMs that don't work. I dunno, maybe I've installed something wrong, little help here?
Generally the ones that will install get hung up during the initial boot, wtf? Have run across some that wouldn't even install and would abort.
I should say I am using CWM 5.0.2.6... I think, its been so long since I have done anything to this phone so I forget but I know its ither Odin or CWM (or are they both one in the same? x.x ) I've been using Darkside Evolution ICS ROM all this time and would be nice to move up to JB if there is a stable one out there
Have you tried vincom's cm build? http://forum.xda-developers.com/showthread.php?t=1886009 its very stable. Been using it for 9 days now without a single SOD or RR. To get the best results I recommend using TWRP. Just head over to the play store and download GooManager. Open, grant superuser, hit menu, then click on "install open recovery script". Go through the prompts and it will download and install TWRP. The method I use for flashing was: Darkside superwipe, ROM, gapps. (I did not use the super light gapps because the home button doesn't work when I do and it doesn't auto restore my apps)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
iburnhearts said:
Have you tried vincom's cm build? http://forum.xda-developers.com/showthread.php?t=1886009 its very stable. Been using it for 9 days now without a single SOD or RR. To get the best results I recommend using TWRP. Just head over to the play store and download GooManager. Open, grant superuser, hit menu, then click on "install open recovery script". Go through the prompts and it will download and install TWRP. The method I use for flashing was: Darkside superwipe, ROM, gapps. (I did not use the super light gapps because the home button doesn't work when I do and it doesn't auto restore my apps)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Hmm, well I got goo manager and its now stuck on the TWRP's boot screen and just reboots after so long of sitting there :/ and its already deleted the rom, so I guess I have to go through the CWM rooting proceeders again?
Well I have managed to get CWM5 back on it and got a working ROM for now but it seems when I do the method you imply it flukes and freezes at the TWRP boot screen. I followed ye the best way possible, maybe there is an alternative way?
I have tried installed Vincom's JB all versions and it comes back as error then aborts install or it installs but sits at initial boot for more than 25min and does nothing I've found that while the warning say give it 10min to boot is generally just a 'just in case' scenario since the T989's processors are considerably powerful.
I have tried to get the ROM onto the phone's internal memory and install from there like Vincom said but the computer won't read the phone for some reason >.<
i would say, to use twrp and download the latest cm10 Here.
i recommend twrp for stable flashing cause there's bugs in latest cwm...
PorscheHusky said:
Well I have managed to get CWM5 back on it and got a working ROM for now but it seems when I do the method you imply it flukes and freezes at the TWRP boot screen. I followed ye the best way possible, maybe there is an alternative way?
I have tried installed Vincom's JB all versions and it comes back as error then aborts install or it installs but sits at initial boot for more than 25min and does nothing I've found that while the warning say give it 10min to boot is generally just a 'just in case' scenario since the T989's processors are considerably powerful.
I have tried to get the ROM onto the phone's internal memory and install from there like Vincom said but the computer won't read the phone for some reason >.<
Click to expand...
Click to collapse
Flash this. Its a flashable TWRP 2.3.1.1 zip.
http://db.tt/gu2PDvZI
Restart recovery, your good!! You need the newer recoveries, like TWRP or CWM 6 to flash JB ROMs
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Flash this. Its a flashable TWRP 2.3.1.1 zip.
http://db.tt/gu2PDvZI
Restart recovery, your good!! You need the newer recoveries, like TWRP or CWM 6 to flash JB ROMs
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Not entirely true. Contrary to what everyone has been saying, and im not trolling just saying from personal experience - cwr 5.0.2.7 and dark side wipes have yet to give me problems I was on the majority if not all jb roms with no issues other than rr/sod which was before the kernel fix.
I'm a noob and expect that 90% of the people here kno more than I do but I wish someone could explain to me why the scripts and cwr 5027 are suddenly so bad.
::
Sent from my SGH-T989 using xda app-developers app
John imilitym
bzlik88 said:
Not entirely true. Contrary to what everyone has been saying, and im not trolling just saying from personal experience - cwr 5.0.2.7 and dark side wipes have yet to give me problems I was on the majority if not all jb roms with no issues other than rr/sod which was before the kernel fix.
I'm a noob and expect that 90% of the people here kno more than I do but I wish someone could explain to me why the scripts and cwr 5027 are suddenly so bad.
::
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
CWR 5027 isn't bad at all it's just that using darkside scripts with certain new recoveries has caused some people boot loops and also with the newer recoveries they aren't required since the built in wipe options work just fine.Personally I use the recovery here http://forum.xda-developers.com/showthread.php?t=1844637
and have had zero issues with it plus it has the darkside scripts built in
Galaxy S Bean ROM! 4.1.2 almost everything stable from Camera to Phone Calls
Sent from my SGH-T989 using xda app-developers app
arthurgreeeen said:
Galaxy S Bean ROM! 4.1.2 almost everything stable from Camera to Phone Calls
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
+1. You can't go wrong with that Rom! I been running it for over a week now with zero complaints
Sent from my SGH-T989 using xda app-developers app
With the v3 sbean I couldn't get my home button to work when I ask tmo twice he didn't respond to my question. I'm looking at slimbean next we'll see how that goes
Sent from my SGH-T989 using xda app-developers app
I would recommend trying either AOKP OFFICIAL Build 5 (not sure if by time you read this if theres a newer one) or a CM10 Nightly. I've tried tons of different JB roms from 4.1 to 4.1.2 and those work good. Decent battery life without changing too many settings (I'm afraid to change too many things because I've hard bricked my phone before but barely got it replaced under the 20 day full exchange warranty). No random reboots or force closes for me so far. Highly recommend trying them out, very simple to flash.
Been on the official aokp and its amazingly stable better then anything jb rom I tried on the s2 battery is excellent too
Sent from my SGH-T989 using xda app-developers app
duckied said:
Been on the official aokp and its amazingly stable better then anything jb rom I tried on the s2 battery is excellent too
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
And I haven't had anything go majorly wrong with cm10 since the nightlies went official. I'm on the 10/24 nightly right now.
Sent from my A100 using Tapatalk HD
Nice nice... I wanna test out CMX maybe I'll make a nand backup and check it out
Sent from my SGH-T989 using xda app-developers app
LoopDoGG79 said:
Flash this. Its a flashable TWRP 2.3.1.1 zip.
http://db.tt/gu2PDvZI
Restart recovery, your good!! You need the newer recoveries, like TWRP or CWM 6 to flash JB ROMs
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Actually... I have CMW6 now the touch one. Does that have something to do with it? The main issue I have with SBean and CM9's JB is eveyrone complains that they can't hear me, that I sound like a robot and the call is badly broken up or that I'm not speaking up like my mic isn't picking up on my voice very well.
Is this a ROM error or a kernel error? rather annoying frankly @[email protected]
Go to your phone app then settings and check noise suppression
Sent from my SGH-T989 using xda premium
duckied said:
Go to your phone app then settings and check noise suppression
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
This is a sure fix then? This would make me the happiest Porsche Husky on Earth if I could go back to Sbean
The customization features of it are to die for
Ooooo, wait a tic... I feel like such n00b now...
I kept downloading V1 thinking it was the newest one xD I think the V6 at the way bottom is the newest one. I'll try that for a few days then report back.
Edit: QUESTION - my screen is flickering (just installed SBEAN V6)... is that a bad install or did I have to fix permissions?
That pretty common in most JB rom but it usually goes away after few mins for me. You can go to settings and then developer options then disable hw overlay but you would need to do it on every boot because it won't stick after a reboot.
Btw you should check out official aokp-milestone-1 it not on here but Google aokp and download the one for our phone. Its pretty sick and stable.
Sent from my SGH-T989 using xda premium
Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?
Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.
The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.
mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)
mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.
mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA
Was it already rooted?
Sent from my SGH-T999 using xda premium
mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium
http://get.cm/?device=d2att
JB 4.3 CyanogenMod 10.2
Sent from my SAMSUNG-SGH-I747 using xda premium
oriveradel said:
http://get.cm/?device=d2att
JB 4.3 CyanogenMod 10.2
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Going to flash this weekend.
I found I had to flash a new gapps to get the play store working. I also had to uninstall and reinstall several apps that were force closing or not loading. But otherwise it seems to be as stable as 10.1.x for me.
I could not successfully flash back to any 10.1.x version (at least without doing a factory wipe) and I had actually flashed to 10.2 by accident (thinking it was a 10.1 nightly). So make sure to backup before you go ahead.
I'm also sad to see I'm still getting a runaway usb_otg process after disconnecting from a computer USB port requiring a reboot. Hopefully this will be fixed soon. The connected to USB notification also remains active sometimes after disconnecting.
tmagritte said:
I found I had to flash a new gapps to get the play store working. I also had to uninstall and reinstall several apps that were force closing or not loading. But otherwise it seems to be as stable as 10.1.x for me.
I could not successfully flash back to any 10.1.x version (at least without doing a factory wipe) and I had actually flashed to 10.2 by accident (thinking it was a 10.1 nightly). So make sure to backup before you go ahead.
I'm also sad to see I'm still getting a runaway usb_otg process after disconnecting from a computer USB port requiring a reboot. Hopefully this will be fixed soon. The connected to USB notification also remains active sometimes after disconnecting.
Click to expand...
Click to collapse
If you make clean flashing a religion you wouldn't run into any problems.... clean flashed every nightly and never experienced 98 percent of problems others have had.
Whats the main difference between 4.2 and 4.3?
---------- Post added at 11:21 PM ---------- Previous post was at 11:13 PM ----------
I mean is it worth going through it and dealing with the bugs if we have a 4.2 thats working great?
I flash this yesterday but keyboard dosnt work :/
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
woot! 4.3!
Yay for new versions...time for yet another full wipe and flash...
Anyone know yet how stable this is?
Installed the first Nightly from the 14th.
I had similar issues with GAPPS. Had to upgrade to most recent.
Overall, its a nice build. I am still having issues with phone reboots every so often. Only seems to happen when I am using GPS and BlueTooth
i.e. on my commute home. But the reboots are so fast, they may occur at other times when I don't have the phone up in my view.
Happy that I upgraded none the less.
Nice cant wait to try it out. I heard there are problems with the camera though.
Sent from my SGH-I747 using xda app-developers app
DexedrineXR said:
If you make clean flashing a religion you wouldn't run into any problems.... clean flashed every nightly and never experienced 98 percent of problems others have had.
Click to expand...
Click to collapse
you clean flash every nightly? what a huge pain in the ass. at most i clean flash once a month or so, anything more defeats the purpose of customizing your setup since you have to keep redoing everything.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
dLo GSR said:
you clean flash every nightly? what a huge pain in the ass. at most i clean flash once a month or so, anything more defeats the purpose of customizing your setup since you have to keep redoing everything.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
If you make a backup of your data partition, you can clean flash, restore your data partition, and be fully up and running in 10 minutes.
tokuzumi said:
If you make a backup of your data partition, you can clean flash, restore your data partition, and be fully up and running in 10 minutes.
Click to expand...
Click to collapse
Except that ain't really a clean flash. :silly:
polobunny said:
Except that ain't really a clean flash. :silly:
Click to expand...
Click to collapse
He's not talking about system data, he's probably talking about just your apps. I'd rather take an extra five minutes to make sure I have no problems than run into problems.