Related
Well everyone, since my KANG thread in the development section has become a discussion thread since official CM nightlies started again, I've decided to redirect the discussion to here. I'm going to ask the thread in the development section to be closed, so it can stop taking up space there...instead we'll take up space here! Lol. But anyways I want this to basically be a continuation of the old thread...you can talk about your G2X questions, comments, problems, etc. here. This will be especially geared toward CM-related problems, but all G2X-related topics are welcome here I hope that everyone will continue to help each other out, and of course I'll monitor the thread to help as much as I can and research things if necessary. Enjoy!
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Kalm_Traveler said:
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Click to expand...
Click to collapse
Ya I couldn't stand that answer my phone wait for it to ring after I select answer was surely a big annoying thing that and wifi calling issues but other then that VERY usable can't wait for newer builds and development on 4.0.3..
I'm on his GB CM7 build and love it great great battery life only at 90% with descent use today.
Sent from my LG-P999 using xda premium
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
j.d.r said:
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
Click to expand...
Click to collapse
As it is always said, it is best to do a full wipe. You never know what issues may stick behind or get caused by not doing a full wipe, but give it a shot and report back and hopefully you don't have issues.
Sent from my LG-P999 using xda premium
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
I believe Hellfire sandwich is the most updated and closest to everything working build. But there's lots coming down the pipeline thanks to our AMAZING DEVS!!!
Sent from my LG-P999 using xda premium
What's the best source for finding out the status of official Cyanogen 9 work on the G2X? I am not interested in kangs or spin-offs.
joeyxl said:
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I haven't tried any of the other ICS roms, but been using HFS since the initial release. Obviously it's not perfect, but I've been running it everyday and don't have any major complaints
CM Nightly 226/Unnamed & Kernels
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
I've used Faux123's UV/OC kernels, but seem to have lost my copy of his v0.4.3 (long term CM7.1.0.1 support). So, the newest v0.4.8 and T15 or ELF Trinity's won't work with mine. I know chip's vary, but mine seems to not like even the ELF Trinity kernel (which has worked for a few peeps running CM7.1.0.1).
Anyway, the breakdown of my ramblings are:
1. Anyone try CM Nightly 226/Unnamed?
2. Anyone happen to have a copy of Faux123's v0.4.3 kernel (CM Battery Version, not the DS driver) lying around? Or a compatible Trinity (preferred, actually)?
Eh, I know #2 is more wishful thinking. I'm mostly interested in anyone's experience with Nightly 226/Unnamed.
Ah, good to be back on XDA and CM, at that. I rolled on MIUI for way too long. Nice GUI & the customization was awesome, but man is that sucker a memory hog! Not to mention the random reboots and screen freezes... I should have never left my good ol' CM. Hindsight and all...
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
long story short, i have a wiped g2x. power button is a ***** to turn on to the point that my finger tips are sore from trying to get it to boot into recovery since last night. i can only seem to get 2 different screens trying to do this:
a) the lg boot animation which promtly freezes as the phone has been wiped & i probably haven't held the volume down button
b) the s/w screen used for flashing a recovery, etc
the phone is not mine but trying to help someone out. is there a timing to releasing the buttons? seems that when it goes to the s/w screen, lg appears for only about a second and then straight to that one. any help would be appreciated.
edit: posted it here only because i'd been following the old thread which led me to this one. i was trying to update to the latest while this happened. i started a similar thread in q&a so if it doesn't belong i''ll remove it, thanks
I've been in a loop like this before. Make sure you have done a battery pull. I think the key is not to hold the volume down button so long, and then be patient for recovery to load, it takes longer than expected in this situation.
Good luck.
Nightly #225
my_former_self said:
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
Click to expand...
Click to collapse
Ah, you want to talk to me! I just went from CM7.1.0.1 Stable to #225. More stable, much faster than CM7 Stable, #225 really should be CM7.2 Stable.
#226 seems to have a bug with the lockscreen PIN. Go get #225 and don't look back.
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
dmwOtis said:
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
Click to expand...
Click to collapse
Lots have stated the same thing doesn't work for most some say it did. Worth a try if you haven't yet, no go for me
Sent from my LG-P999 using xda premium
Where is this getril app?
Sent from my LG-P999 using XDA
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I agree, this is by far the most annoying bug and the only "show stopper" I can think of on CM7. I do not think it's a 'phone-by-phone' thing, because if I flash to stock or Weapon G2X, my mic volume is fine. It's only on CM/CM-based ROMs, such as MIUI. I can't count the number of times where people have told me to "speak up" until I'm practically yelling into my phone. I think there's a bug with noise cancellation that causes it to be quieter than it should be.
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
imoumni said:
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
GetRIL went the other way for my phone (Wind Canada P999), recommending v11h. Any notes re: the different builds?
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.
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
I'm not sure if this is the right place for me to post it... On the Tab 2 forum there is an area for this in the development area, but I couldn't find it. Sorry in advance if this doesn't go here.
I just installed the nightly for the 20th of CM10.1 and I'm getting a lot of SystemUI force closes. Wondering if anyone else was having this issue or if it was just me?
I know... It is a nightly so I'm not fussed about it but if it is just me, I'll look into fixing it on my end but if others are having issues with that ROM then I"ll probably flash back to the 18th or something.
Thanks.
titanshadow said:
I'm not sure if this is the right place for me to post it... On the Tab 2 forum there is an area for this in the development area, but I couldn't find it. Sorry in advance if this doesn't go here.
I just installed the nightly for the 20th of CM10.1 and I'm getting a lot of SystemUI force closes. Wondering if anyone else was having this issue or if it was just me?
I know... It is a nightly so I'm not fussed about it but if it is just me, I'll look into fixing it on my end but if others are having issues with that ROM then I"ll probably flash back to the 18th or something.
Thanks.
Click to expand...
Click to collapse
There is another thread for cm10.1 issues and whatnot, its not a big deal to me, but I've seen people freak out! Haha
Anyways, lately there's been a lot of issues with the nightlies lately. The new CM (around march 18th) came with a new kernel version, from version 3.0ish or something to 3.43 ish?? Anyways, the new kernel fixed some issues, but also caused some new issues since its still fairly new from my understanding. I've had one system ui force close, and MANY freezes. Also, there for a while it would freeze during calls, but I haven't had one of those for a while now.
Sent from my SCH-I535 using xda app-developers app
XdrummerXboy said:
There is another thread for cm10.1 issues and whatnot, its not a big deal to me, but I've seen people freak out! Haha
Anyways, lately there's been a lot of issues with the nightlies lately. The new CM (around march 18th) came with a new kernel version, from version 3.0ish or something to 3.43 ish?? Anyways, the new kernel fixed some issues, but also caused some new issues since its still fairly new from my understanding. I've had one system ui force close, and MANY freezes. Also, there for a while it would freeze during calls, but I haven't had one of those for a while now.
Click to expand...
Click to collapse
Thanks for the information... Yeah, I actually had more freezing when I was stock then with the CM builds. Where might I find the other thread? I must be blind to not have seen it.
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????