Related
So i've been doing some research about cyanogen mod 9 for my HTC desire and have read all the people's comments about how good it is but an still not convinced. I mean that i've heared that cyanogenmod 9 does not make your camera work. Thats a major set back isn't it? Also there are some other serious probs e.g WiFi, Google play apps e.t.c. So is cyanogenmod 9 worth all these troubles? Whats the up side?
The main benefit, is it gives people like me who own devices (samsung infuse) that dont get official ICS updates. It runs great on my device, and i prefer it to any other rom ive tried, but i use my sixaxis controller with my phone, and due to bluetooth not working im using CM7 til that issue is resolved. but in all honesty CM9 is the best custom Rom available for my device at least it you dont need bluetooth. it runs great and my battery life is great.
what about andriod apps. do apps run on such a firmware.
(espicially games)??
They certainly do! It's just like a normal ICS device - there's the Play Market and you can install any app suited for ICS
BTW, CM9 rocks, AOKP even more!
I Cyanogen 9 with my HTC ONE X. I also have problems with the Bluetooth works partially. After each ROM is different. Much like me, flash your phone to find THE right ROM.
Cyanogenmod 9 is brilliant if it's stable build. From your description they're still working on it,so I'd urge you be patient and try cyanogenmod 7 instead.
Or,check out MIUI4 rom if you're still interested in ICS
Sent from my U8150 using XDA
The matureness of CM9 depends also on the device you own, and the available or unavailable drivers - in your case it seems there are problems with the cam.
I suggest to get CM7.2 instead, till those problems are fixed on your device.
CM9 will always run as It provides you the best latest features from google.
Only "problem" I've experienced on CM9 on my Epic 4g is that Dead Space is no longer recognized as an authorized device. Other than that, I enjoy using it over GB. It feels like the interface makes "more sense," but of course that's just a personal preference.
I not a huge fan of CM9 ...as i ahev flashed in S2 couple of times ...but still the force close issue persist with the nightly builds(ICS)...!!
I can't wait for a stable build for the GS3! (yet I have to )
DeltaBlast said:
I can't wait for a stable build for the GS3! (yet I have to )
Click to expand...
Click to collapse
lets wait and see if they rocks or not
cm9
Using experimental cm9 build on Atrix. It's worth it, but it comes with sacrifices.
My phone is much much faster, smoother, and prettier. But at the cost of stability with the camcorder, and some obscure cm7 features.
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yeah Factory reset is recommended. And its Working great. I must ask you to consider updating to 4.2, 10.1 nightly build. Its literally flawless...
Sent from my SGH-I897
cm10.1 really cool. Waiting for slim android 4.2
Several days ago I did the upgrade to 10.1 from 10 without the factory reset - no problems, but wipe the caches). You need to clear the clock data first and do the upgrade from the boot screen (not the update screen in about phone). Do a backup just in case you have problems.
for further info go to :donandroid.com/how-to-update-cm10-to-cm10-1-with-cwm-recovery-581
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
+1
Sent From the Land of Defrag
if you do Erase SD Card, does it erase internal storage instead?
I tried the stable version of CM10, and it seemed to work great except for one thing. I could connect to my employer's Exchange server at all. I tried all kinds of things and it just couldn't connect. I took it to the IT guys and they fiddled with it for a while and couldn't get it to work either. A little quality time with Google told me that JB has a bug that sometimes makes it impossible to connect to corporate exchange accounts. I ended up switching to CM9. Do you know whether CM10.1 fixes that? If so I think I'll give it a try.
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
Slim 4.2.1 has been available in beta for a week or two now... I've not encountered any problems with beta 2 so far.
http://forum.xda-developers.com/showthread.php?t=2060386
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
thank quá hay :
theoctagon said:
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
Click to expand...
Click to collapse
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
laughingT said:
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
Click to expand...
Click to collapse
So for a stable fast ROM, you would suggest CM 10.0 over AOCP or some of the other 4.1.2 "final" version ROMs like SlimBean?
depends on your personal preference I suppose. you need to get to CM9 at least, preferably 10.0, to flash slim bean, right? So, if it runs well on 10.0, then you could go slim bean
you wrote that you just want the basics, nothing fancy. so, yes, CM10.
Sent from my SGH-I897
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yes, I did. And I didn't really have any problems with Semaphore, it just seemed a little laggy.
RichMD said:
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
Click to expand...
Click to collapse
I would highly recommend Sephhi's [ROM][4.2.1]Captivating (Xperia Themed)
It is CM10 based and is stripped down to run smooth.
http://forum.xda-developers.com/showthread.php?t=2057574
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
BELbX said:
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
Click to expand...
Click to collapse
Try hellybean 4.2. Hellybean came a long way from when i used it a while back! It's a much smaller and light weight package as compared to the xperia one. Barely any issues. Boot times and first boot are quick. Over clocking is fun again too. I thought it was oc'd at first for being smooth. It's so smooth and stable. One or two things, but nothing compared to others. I like the xperia one but it's heavier with more to be worked. It's running better then aokp 4.1 with semaphore.
Sent from my SGH-I897 using xda app-developers app
3g Problem
I just flashed 4.2.1 AoCP 5 and lost my 3G. Anyone know what's up?
I live and work in an area that has poor signal for Verizon. I almost immediately flashed to CM 10 after I got the Verizon Galaxy S3 because I was running CM 10 on my previous Sprint Galaxy S3 without issue. I have been updating the radio and RPM with each leak (currently running K3) and things got a little better but I constantly dropped calls. I had to flash back to stock because I flashed to CM 10.1 and my radio got messed up. I ran the newest stock rom for the last week and noticed a huge difference. I still had low signal but my data dropped less frequently and I could actually make phone calls in areas I couldn't before.
I rooted, and flashed to CM 10.1 and noticed right away the signal is not where it should be. I can't make phone calls inside of buildings with low signal at all, where with stock I could without issue. I love CyanogenMod but I don't think I can deal with the poor signal.
Any ideas on what could be causing this problem and maybe a possible resolution?
fowen said:
I live and work in an area that has poor signal for Verizon. I almost immediately flashed to CM 10 after I got the Verizon Galaxy S3 because I was running CM 10 on my previous Sprint Galaxy S3 without issue. I have been updating the radio and RPM with each leak (currently running K3) and things got a little better but I constantly dropped calls. I had to flash back to stock because I flashed to CM 10.1 and my radio got messed up. I ran the newest stock rom for the last week and noticed a huge difference. I still had low signal but my data dropped less frequently and I could actually make phone calls in areas I couldn't before.
I rooted, and flashed to CM 10.1 and noticed right away the signal is not where it should be. I can't make phone calls inside of buildings with low signal at all, where with stock I could without issue. I love CyanogenMod but I don't think I can deal with the poor signal.
Any ideas on what could be causing this problem and maybe a possible resolution?
Click to expand...
Click to collapse
Depends on where ya live, your mileage may vary. I get within 1-2 -dBm between the two.
Technically since we don't have the source code the reason CM10 has data is by a work around.
There really is nothing you can do. It is what it is. I've run devices with CM that have provided better signal, and usually were on sprint lol and then run them where they provide the same or slightly worse quality.
Happens.
Sent from my SCH-I535 using xda app-developers app
This does not ha e anything to do with cm 10. This this to do with the the phone radio. This is the reason why I switched to the DNA now I have Full bars everywhere I go. On my s3 I used to drop calls all the time.
Sent from my HTC DROID DNA.
Itzvik said:
This does not ha e anything to do with cm 10. This this to do with the the phone radio. This is the reason why I switched to the DNA now I have Full bars everywhere I go. On my s3 I used to drop calls all the time.
Sent from my HTC DROID DNA.
Click to expand...
Click to collapse
Your wrong...read OP post and you realize your wrong.
You have your DNA now leave and stop trolling.
Sent from my SCH-I535 using xda app-developers app
Ok I really hope I'm not beating the dead horse here but I have a similar problem on my verizon Galaxy s3 and I was hoping there might be a fix
My understanding is that the CM developers dont have the GS3 source for something (the RIL?) so they have to use a different RIL? I'm probably totally butchering that, because I dont understand the words I'm using, but from what I've gathered the signal is what it is on CM, and will not improve beyond where it is.
It is certainly usable for me, but there are many times my wife has 4g and I have 3g, or she has a 3g signal and I have nothing at all (she has a stock vzw gs3).
Restola said:
My understanding is that the CM developers dont have the GS3 source for something (the RIL?) so they have to use a different RIL? I'm probably totally butchering that, because I dont understand the words I'm using, but from what I've gathered the signal is what it is on CM, and will not improve beyond where it is.
It is certainly usable for me, but there are many times my wife has 4g and I have 3g, or she has a 3g signal and I have nothing at all (she has a stock vzw gs3).
Click to expand...
Click to collapse
I think you're correct on the RIL part.
I had the same issue on 10.1. I switched to an older radio, and though it is not perfect, it did give me better reception and the switch from 3g to 4g is faster. My radio is VRLHE
Why not try a rom like beans. It is a touch wiz rom that looks like aosp and had a lot of aosp features. That way the radios will work fine you will still have aosp stuff and all the goodness of being rooted.
Sent from my SCH-I535 using xda premium
Let's not get confused here. Tw rom's like beans are themed to look slightly aosp, but are far from it. Aosp has so many customization options that tw cannot come close to. (I'm an aosp guy, if you can't tell). That being said, signal strength will always be an issue on aosp based roms due to the Samsung ril only being licensed to samsung, hence only working on tw rom's. The official ril code will almost never be released as its how qualcom makes its money. Currently aosp rom's use a work around home brewed ril that is very effective, but not quite what stock rom will offer. So if your signal is poor where you are, aosp may not be the best choice for you, but for most the signal is just as good as tw, and imo the only way to run android.
Sent from my Nexus 7 using Tapatalk HD
I'm not confused, that's why I said looks like (aka themed like). Also I said some aosp features like MMS, camera/gallery, lock screen to name a few. Its no where near the same but if they are having issues which I read a few people do have with signal and losing data its a nice alternative and has SOME similar features.
Sent from my SCH-I535 using xda premium
I just upgraded from a Samsung Galaxy Nexus to a Samsung Galaxy S3, and just curious why everyone is still making/releasing 4.1.2 based ROMs when 4.2.2 has been available for so long?
Having come from running 4.2.2 on my Nexus, I was used to it, so the first think I did was unlock, root and get AOKP 4.2.2 on here. It runs flawlessly and everything works, so just hoping to get some insight on why all the ROMs in the dev section are old.
Thank you
Because many of the roms in development are based off Samsung's touchwiz software, which itself is based on 4.1.2 still. For 4.2.2 roms based off AOSP, most of them can be found in original development.
Basically the difference in versions is due to
Touchwiz: Google -> Samsung -> verizon -> devs
AOSP: Google -> devs
And aosp roms camcorder has extremely low volume recording so having kids I unfortunately cant use aosp even though I really want to.
crobs808 said:
Having come from running 4.2.2 on my Nexus, I was used to it, so the first think I did was unlock, root and get AOKP 4.2.2 on here. It runs flawlessly and everything works
Click to expand...
Click to collapse
Not quite everything works on an AOSP 4.2.x ROM. The radio interface layer (RIL) software for the GS3 has not been released by Samsung, the radio software used for all AOSP ROMs is reverse-engineered and is not quite as good as the original Samsung software. Your signal strength will not be quite as good using AOSP, though you may or may not notice a difference depending on coverage where you live.
More importantly, the GS3's world phone capabilities are not fully working with the AOSP RIL, I believe you can put a GSM SIM in the phone and make calls/texts, but not get data service. So if you travel internationally and want to use a local SIM to get data, you'll want to stick with a ROM based on the latest Samsung software, which unfortunately is still based on 4.1.2.
I'm happy to hear if either of those things have changed recently, it's been a little while since I looked into it. The only reason I don't use AOSP ROMs right now is because of the RIL issue, I need my phone to work as a phone first and foremost and that means going with something based on stock Samsung software. Of course, if neither of those things bother you, use what you like.
Hmm, weird. I have no call issues, and am getting 20MB/10MB on 4G LTE for data speeds, same as I did on my Nexus running AOKP build 6 (Android 4.2.2). Even the number of bars is the same, and more bars near my office than before with my Nexus (may be due to better radio hardware though). Also, I tested audio on video recording, and hear no difference in the videos I took on my Nexus. I also have kids, and the test I did was whispering to full talking from 5ft away - hear everything.
Weird. Guess I'll just keep using it since it's working for me.
crobs808 said:
Hmm, weird. I have no call issues, and am getting 20MB/10MB on 4G LTE for data speeds, same as I did on my Nexus running AOKP build 6 (Android 4.2.2). Even the number of bars is the same, and more bars near my office than before with my Nexus (may be due to better radio hardware though). Also, I tested audio on video recording, and hear no difference in the videos I took on my Nexus. I also have kids, and the test I did was whispering to full talking from 5ft away - hear everything.
Weird. Guess I'll just keep using it since it's working for me.
Click to expand...
Click to collapse
Different strokes for different folks. Personally I like many of the features of Touchwiz (The samsung camera app among others) but hate the way it looks so I use beans 4.1.2 builds. I was on AOSP 4.2.2 for a while but had isseus with the gps not tracking my runs properly and the low recording volume really got to me.
I've found that most AOSP builds leave me wanting. AOKP has never disappointed me; across devices.
If you had good reception with the Nexus...well, that speaks volumes. You're not anywhere near a fringe area. If you have great 4g, the Nexus worked great and AOSP roms on GS3 work great.
Where I live, there are a bunch of fringe areas and a lot of handshaking between 4g and 3g. The Nexus....I had to return it immediately. TERRIBLE reception. The GS3 with AOSP was a little better...but not much. When I'm sitting beside my wife with a rooted GS3 running Cleanrom, and I'm running CM10.1 and I have no signal and she has 4g...well, it gets frustrating. lol.
But I'm glad it's working for you...wish I could run 4.2.2...stupid RIL.
For those having GPS problems, have you done this?: http://forum.xda-developers.com/showthread.php?t=2201668
I much prefer the pure Google experience. when I had an HTC I hated Sense. When I had a Motorola I hated Motoblur. I didn't see any reason to learn to like TouchWiz
Also, I think I am blessed with my geographical area. I can travel 45 minutes from one side of my home city to the other and still have 4-5 bars on LTE.
Been running cm 10.2.1 for a bit now its works but has several issues, and was wondering if the Stock Rom 4.1.2 capable or running GSM? i know once flashing it back ill need to unlock the radio, but is it capable, CM is nice but too many little issues to make it practical on the photon q
so is it possible, if so how?
or is it not possible, why?
Why aren't you running a newer ROM, e.g. CM11? It's under the device name of "moto_msm8960".
Sent from Google Nexus 4 @ CM11
havent been running a newer rom because i hadnt gotten around to updating the recovery for flashing CM 11 since the photon q is no longer supported offfically by any of the updates and there arent currently any stable releases of CM 11 only nightly builds
Most of the Issues im dealing wirh are annoying and id rather not repeat them if i didnt haveto, many folks are still complaining about the broken data hand shaking issues for 3g data
Morecrabs said:
havent been running a newer rom because i hadnt gotten around to updating the recovery for flashing CM 11 since the photon q is no longer supported offfically by any of the updates and there arent currently any stable releases of CM 11 only nightly builds
Most of the Issues im dealing wirh are annoying and id rather not repeat them if i didnt haveto, many folks are still complaining about the broken data hand shaking issues for 3g data
Click to expand...
Click to collapse
Man, the only time to crank out a stable build is when the next Android version is out... Don't expect stable releases in the middle of something. Nightlies have always been stable for me. And isn't updating the recovery a simple one-time thing?
Sent from Google Nexus 4 @ CM11
Morecrabs said:
havent been running a newer rom because i hadnt gotten around to updating the recovery for flashing CM 11 since the photon q is no longer supported offfically by any of the updates and there arent currently any stable releases of CM 11 only nightly builds
Most of the Issues im dealing wirh are annoying and id rather not repeat them if i didnt haveto, many folks are still complaining about the broken data hand shaking issues for 3g data
Click to expand...
Click to collapse
Photon Q is officially supported by CyanogenMod (I'm maintainer).
http://wiki.cyanogenmod.org/w/Moto_msm8960_Info
I recommended to use OpenRecovery 2.09, download link can be found here: http://forum.xda-developers.com/showpost.php?p=48551561&postcount=75
CM11 is what I run on my phone and I'm not aware of any issues worth mentioning.
I have no idea what you mean by
broken data hand shaking issues for 3g data
Click to expand...
Click to collapse
. If people complain but don't post
Code:
adb logcat -b radio
, there's no way to help them. My data work fine.
(Issues reported by CDMA users are something else, outside of my scope as I'm in GSM land, but CDMA fixes are still in progress in the generic CM code).
When I search https://jira.cyanogenmod.org for xt897, I see only three bug reports.
There's not much moto_msm8960 specific progress happening right now as we mostly wait for the release of 3.4 kernel source by Motorola (it would be waste of time to backport more 3.4 code to our current 3.0 kernel as 3.0 will become obsolete hopefully soon).
Anyway, back to your original question: you can use the stock 4.1.2 firmware on SIM modded Q just fine.
on version 10.2.1 I had issues with 3G data, I had data when the Phone was connected with H+ but the Moment it switched to 3G i lost Connectivity, after a small amount of Google searching I found other folks had this issue as well except the Photon Q community had Not reported this issue explicitly, the Loss of 3G isnt something most would notice since the Coverage has been improving Signifcantly but for me in my area its fairly apparent because its more Rural, so we have some holes in the At&ts 4g coverage
I installed the Latest 2.7 Twrp and flashed CM11 Nightly lastest, working ok, but the Install of Gapps Keeps failing, this phone being my daily driver i want it to be as seamless as possible
Flashed latest Nightly and 3-22_gapps_Standard_4.4.2_Signed.zip
its failing on the gapps install
the 3G issues on the Nightly seem eliminated as i Havent Noticed the Coverage Loss as of yet, but was hoping to Get Ingress Running which made the Loss of Connectivity very apparent Go resistance!
thank U for the reply guys, I really do appreciate your works and didn't mean to come off as a whiner, just need it to work seamlessly since its a daily driver and this roms are experimental and Im no expert, I really do enjoy the Features Implemented and the Debloating especally but simply wondered if the stock would be able to provide me a more stable environment until till more kinks got worked out
Morecrabs said:
on version 10.2.1 I had issues with 3G data, I had data when the Phone was connected with H+ but the Moment it switched to 3G i lost Connectivity, after a small amount of Google searching I found other folks had this issue as well except the Photon Q community had Not reported this issue explicitly, the Loss of 3G isnt something most would notice since the Coverage has been improving Signifcantly but for me in my area its fairly apparent because its more Rural, so we have some holes in the At&ts 4g coverage
I installed the Latest 2.7 Twrp and flashed CM11 Nightly lastest, working ok, but the Install of Gapps Keeps failing, this phone being my daily driver i want it to be as seamless as possible
Flashed latest Nightly and 3-22_gapps_Standard_4.4.2_Signed.zip
its failing on the gapps install
the 3G issues on the Nightly seem eliminated as i Havent Noticed the Coverage Loss as of yet, but was hoping to Get Ingress Running which made the Loss of Connectivity very apparent Go resistance!
thank U for the reply guys, I really do appreciate your works and didn't mean to come off as a whiner, just need it to work seamlessly since its a daily driver and this roms are experimental and Im no expert, I really do enjoy the Features Implemented and the Debloating especally but simply wondered if the stock would be able to provide me a more stable environment until till more kinks got worked out
Click to expand...
Click to collapse
I am based in Australia where 3G 850mhz GSM band is used on a sim modded phone. I am running ICS. did you manage to get gapps installed?