http://www.cyanogenmod.com/blog/cyanogenmod-10-m1
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
http://get.cm/?device=&type=nightly
Downloading now.
GS3
This is interesting, will try. I do wonder if this differs much from other available builds we have except now it will be frozen for a month. Presumably those cleanups have already appeared in other builds? Maybe someone more knowledgeable about how that works can say. I do think it's a good idea.
Sent from my SCH-I535 using Tapatalk 2
Hmm. Interesting and I think it's a great idea but looking at the builds the experimental M1 and the latest nightly look to be the same size. Maybe it's supposed to be this way?
Sent from my SCH-I535 using Tapatalk 2
niv3d said:
Hmm. Interesting and I think it's a great idea but looking at the builds the experimental M1 and the latest nightly look to be the same size. Maybe it's supposed to be this way?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, maybe they tweaked a few things and said that's that.
GS3
blestsol said:
Yeah, maybe they tweaked a few things and said that's that.
GS3
Click to expand...
Click to collapse
PLEASE DELETE
Well unfortunately I can't run AOSP as a stable DD until the RIL is fixed :/ I know it's being worked on. But I'm constantly in a 3/4G area
EDIT: I am so incredibly sorry that this post got under someone's skin and "cluttered" a thread.
Sent from my SCH-I535 using Tapatalk 2
thanks for the linkage, updated OP in Official Cm thread although I feel someone should branch off a M1 discussion thread as it will very greatly from the Official Nightly and the UnOfficial Nightly builds.
http://forum.xda-developers.com/showthread.php?t=1840414
If someone cares to maintain the M1 thread and starts it let me know and I will link to it from the Nightly thread
niv3d said:
Well unfortunately I can't run AOSP as a stable DD until the RIL is fixed :/ I know it's being worked on. But I'm constantly in a 3/4G area
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
We dont need to hear you whine about how your area sucks. Please refrain from cluttering threads, all I ask.
tonu42 said:
We dont need to hear you whine about how your area sucks. Please refrain from cluttering threads, all I ask.
Click to expand...
Click to collapse
Can you refrain from tossing napalm at the dude? Peaceful little discussion thread.
GS3
tonu42 said:
We dont need to hear you whine about how your area sucks. Please refrain from cluttering threads, all I ask.
Click to expand...
Click to collapse
EDIT: Never mind I have better things to do with my time
Sent from my SCH-I535 using Tapatalk 2
Anyone know how to get the volume of either the monthly or nightly releases to work?
I don't mean the regular volume, I mean when recording video the volume is almost non-existent. It's very frustrating and I can't seem to find a fix, every AOSP ROM I've tried here is the same story as far as that.
I can record fine on a TW ROM so I know it's not a hardware problem.
Anyone else try the m1 yet? Any other issues besides data and volume while video recording? I've been waiting for a release candidate but it looks like this is the closest thing for a while so I wanna flash but still nervous cause I'm a noob ):
exoteric said:
Anyone else try the m1 yet? Any other issues besides data and volume while video recording? I've been waiting for a release candidate but it looks like this is the closest thing for a while so I wanna flash but still nervous cause I'm a noob ):
Click to expand...
Click to collapse
havent had data issues myself, volume while recording? i guess audio is kinda quiet while playing back videos, but i dont use it so im stocked that the "take image while recording" feature works
niv3d said:
PLEASE DELETE
Well unfortunately I can't run AOSP as a stable DD until the RIL is fixed :/ I know it's being worked on. But I'm constantly in a 3/4G area
EDIT: I am so incredibly sorry that this post got under someone's skin and "cluttered" a thread.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for talking about the 3g issue, I appreciate the roms everyone is making and modding but I think they need to tone down the mods that are trivial and concentrate on more major bugs. So ya I'd prefer fixing dropping 3g every 5 minutes to fixing a blue tooth bug that only happens when the third moon of Jupiter lines up with Plutos dark side of the planet during a tornado. Can't wait to try this rom
Sent from my Galaxy S III
M series build fixed the speakerphone echoing problem for me
CM10 M1
Flashed CM10 M1 3 days ago, came from Synergy 1.7 ICS ROM and have the latest radio VRLG1. Did a clean wipe and restored Apps w/Data using Titanium Backup.
All seems to working fantastic, great speed and smoothness to this ROM, battery life seem as good as stock or Synergy. Haven't noticed any data issues, volume on phone calls is good.
Minor issues, after flashing had to reboot twice to get past data activiation, and Trebuchet seem to have a little problem and kept closing. Load Nova as my launcher (it was my launcher on Synergy) and have had no issues since.
Yea I mentioned in official release thread my impressions but in case anyone is following this..I've had excellent experience. No real errors to speak of. It's a true stable build for me. Love it.
Related
If anyone has questions or concerns regarding the CyanogenMod 10 please ask here and stay away from the development section for these posts, as it has over 3000 posts.
To start off please read the CM10 faq on the first Page of the CM10 thread before asking any questions here or in the official thread. Thanks
Sent from my HTC One X(L/AT&T)
So, does (or will) the camera app in CM10 have the same burst mode that the Sense camera has? Can you take AS MANY photos AS QUICKLY? Will those photos be similar quality? Will we be able to pull stills from previously recorded video? Or take Hi Res stills while shooting HD video?
I read the last 15 pages of the development thread and didn't see any of this being discussed.
Thanks a bunch!
Billy
Sent from my Nexus 7 using Tapatalk 2
Burst mode is a sense cam feature only, because there is no sense in cm those features will not be there. Your best bet is if you want sense cam but asop feel go with clean rom or tn rom, they can desense the launcher but keep the apps but you will be on ics. But i will say the cm cam is alot faster then it used to be and is still a good camera.
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
PaKMaN787 said:
To start off if you want the video camera and/or audio fixes, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
yungskeeme said:
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Click to expand...
Click to collapse
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
PaKMaN787 said:
To start off if you want the video camera and/or. music workarounds, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
PaKMaN787 said:
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
Definetly hit or miss. Heard it was fixed in the 8/28 but no music so I guess I'll stay on 8/22 and deal with it. Heard someone say they flashed AOKP ICS rom and reflashed CM10 and it was fixed.
bstephens2u said:
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'll do a little poking around and see if I can get this working (I probably won't) and I'll let you know if I do!
tropazr said:
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
Click to expand...
Click to collapse
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Is wake locks an issue with cm10 so far or just a few users isolated type instance? I was getting massive wake lock for alarmmanager that I do not get on CleanRom.
anyone else getting bad battery life with this ROM? currently running the 8/29 nightly.
Right now im at 33% battery with 11h on the battery but only 1h45min screen time. I also have GPS on and brightness around 1/2..which could possibly be the problem.
JeepFreak said:
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
toptalent said:
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Click to expand...
Click to collapse
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
h8rift said:
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
Click to expand...
Click to collapse
Wooooooooooot!! And would it just be TeamDouche in general that deserves the donation? Or was somebody specific working on this?
Thanks H8!
Billy
Sent from my Nexus 7 using Tapatalk 2
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
Click to expand...
Click to collapse
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
toptalent said:
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
Click to expand...
Click to collapse
I'm not entirely sure if something is being worked on but I think you should flash CR4.0 as it is definitely working and is 4.0.3 base which is what h8rift said to flash.
Sent from my HTC One X(L/AT&T)
May I ask what is the right procedure to flash CM10? In the zip there is a boot.img. Do we need to manually extract and flash it with fastboot?
I ask this because some people (including me) can't make LTE to work in CM9/10. Some say by flashing CleanROM 4.0, full reset then flash CM10, LTE will be the default. This trick does not work for me. What is the mechanism of this trick? What stays after full reset? All I can think is the boot image. But even manually flashing CleanROM's boot.img then flash CM10 does not work for me. Changing build.prop (ro.ril.def.preferred.network and ro.telephony.default_network as suggested at code.google.com/p/cyanogenmod/issues/detail?id=1623 , sorry can't link external) of course does not work either.
I know #*#*info*#*# can change the preferred network type, but it does not stick after reboot, which renders this approach useless.
Thanks.
Seems my hard work has finally paid off!
https://plus.google.com/+CyanogenMod/posts/TKJdwcptRRv
I'll update my thread accordingly once the nightlies begin. Since it'll be a couple of days before the nightlies actually begin, I'll run another build in the mean time. Partly because I want to make sure the CM repo will produce good builds
Yay!
Bugs that still exist: touchkey w/ BLN that they're using is just an interim driver... I need to finish porting that. Also, the random WIFI MAC bug. Ugh.
Oh! And there's a work around for users of the official CWM in ROM Manager. Until once the new builds kick in, you should be able to install them through the official CWM, which will allow CWM to update and correct their problem. This is some serious catch 22 stuff. But it'll get worked out.
Otherwise, you people should be able to start enjoying some nightly CM goodness.
I can then go on to finish the I577 port and get them on their way as well...
dr4stic said:
Seems my hard work has finally paid off!
https://plus.google.com/+CyanogenMod/posts/TKJdwcptRRv
I'll update my thread accordingly once the nightlies begin. Since it'll be a couple of days before the nightlies actually begin, I'll run another build in the mean time. Partly because I want to make sure the CM repo will produce good builds
Yay!
Bugs that still exist: touchkey w/ BLN that they're using is just an interim driver... I need to finish porting that. Also, the random WIFI MAC bug. Ugh.
Oh! And there's a work around for users of the official CWM in ROM Manager. Until once the new builds kick in, you should be able to install them through the official CWM, which will allow CWM to update and correct their problem. This is some serious catch 22 stuff. But it'll get worked out.
Otherwise, you people should be able to start enjoying some nightly CM goodness.
I can then go on to finish the I577 port and get them on their way as well...
Click to expand...
Click to collapse
Great news ,job well done.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Congratulations guys !
First, you got ICS update from T-Mobile.
Now, official CM10 is going to be available for your device.
:good:
Congrats! This is awesome news for both Blaze and Exhilarate owners. Thanks to everyone involved for all the work put into getting us this far this fast. I'm really starting to feel good about picking this phone over the S2.
Well done. Thank you for your support.
Sent from my SGH-T769 using xda app-developers app
namaui said:
Congrats! This is awesome news for both Blaze and Exhilarate owners. Thanks to everyone involved for all the work put into getting us this far this fast. I'm really starting to feel good about picking this phone over the S2.
Click to expand...
Click to collapse
Ditto
Sent from my CM10 powered Galaxy S Blaze 4G
AWESOME NEWS! Thanks so much for all of your hard work!
Yea thanks a bunch! Funny how I have JB and my friend on his g3 has ICS I love my phone again
dispozable said:
Yea thanks a bunch! Funny how I have JB and my friend on his g3 has ICS I love my phone again
Click to expand...
Click to collapse
Next stop: key lime pie
Sent from my CM10 powered Galaxy S Blaze 4G
dispozable said:
Yea thanks a bunch! Funny how I have JB and my friend on his g3 has ICS I love my phone again
Click to expand...
Click to collapse
Hell yeah! In a couple of weeks we went from doubting whether we'd ever see ICS on our phones to official CM10 support.
Seems I've lucked out with the purchase of my last two phones thanks to the awesomeness of the folks here on XDA. A couple years ago the HD2 was the most powerful subsidized phone available from T-Mobile (Nexus One was probably the best phone but couldn't afford to buy it in full). I reluctantly bought the HD2 but wanted Android OS so bad. About a month later devs ported a stable rom over via SD card and then made it NAND flash-able.
A couple months ago I was due for an upgrade again. I had to buy two phones (my wife's MyTouch 3G just wasn't cutting it for her) so I was again on a limited budget. When I looked at the specs I chose the Blaze since it seemed like the most powerful phone for the money. I was again bummed because it was running an older OS version than my two year old WinMo phone but now here we are!
:good::victory:
Could someone explain to a newbie, like myself, how official CM is different than unoffical.
Does it mean that offical CM fixes are automatically generated for Blaze every night? Is there a different place to grab these updates, than here in the Blaze Development forum.
ltcmdrworf said:
Could someone explain to a newbie, like myself, how official CM is different than unoffical.
Does it mean that offical CM fixes are automatically generated for Blaze every night? Is there a different place to grab these updates, than here in the Blaze Development forum.
Click to expand...
Click to collapse
Yeah, CM official will be generated on their servers (which are some serious kit) vs. the 4.5 hours builds required of my home machine.
The nightlies (in theory) should begin tonight, I'll update the main thread once it's all officially there.
I've been working closely with the devs in CM to get all this committed, therefore the next nightly should be just like my 10/09 build + my BLN fix + changes within CM from 10/09-10/12 (which in theory will be the first nightly). And then every nightly after that will get the CM updates moving forward.
With CM10 being official, it might not be too far of a jump to also add official CM9 builds. The device definition is mostly the same, just a matter of different binary blobs for the video. I'll have to talk to the guys about that.
The majority of the work I did was in porting the kernel changes into the main kernel repo. This is also going to benefit the CM9 build as erikmm asked for a copy of my patches. It means he'll get my WiFi random MAC bug (until I fix it), but other stuff should work... better?
Either way... a day to celebrate
dr4stic said:
Either way... a day to celebrate
Click to expand...
Click to collapse
Yup, ok I get it now. Excellent job, that is a huge deal.
I haven't seen Erik around.. I mean i guess I know why.. but i wonder if he knows....
unicorndust98 said:
I haven't seen Erik around.. I mean i guess I know why.. but i wonder if he knows....
Click to expand...
Click to collapse
I shot Erik a message earlier to let him know. Amazing what's happened in a week's time. Great news
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Quick question... I know they're "Nightlies" but when can we possibly expect the first one to drop? (Oh my, I broke the no skiing for eta's rule xD) I was curious if they gave you a rough idea.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
I'm hoping to get an "M" release.
Just want to say thank you man. Never thought it little device would get this much attention.
Sent from my blaze using cm10
Acerbus91 said:
Quick question... I know they're "Nightlies" but when can we possibly expect the first one to drop? (Oh my, I broke the no skiing for eta's rule xD) I was curious if they gave you a rough idea.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Well, just in case you didn't check this morning.... it's up So, ETA... yeah... this morning
chjema said:
I'm hoping to get an "M" release.
Just want to say thank you man. Never thought it little device would get this much attention.
Sent from my blaze using cm10
Click to expand...
Click to collapse
We'll get an M in a Month, the M3 (hopefully about the same time I place my order for an M3 ). They specifically held the kernel patches back so they could roll out the M release first. And they did this understandably. The patches I did could have seriously affected a few other builds (T989, I727, I717), etc... So they waited till after the monthly to add the kernel patches and add us to the device tree. CM had been in a soft freeze mostly for the last week.
Acerbus91 said:
Quick question... I know they're "Nightlies" but when can we possibly expect the first one to drop? (Oh my, I broke the no skiing for eta's rule xD) I was curious if they gave you a rough idea.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I got an update notification this morning for a 10/12 build. Go to settings-about phone-cyanogenmod updates. Download the update there. It will reboot and install automatically.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Just installed. I'll keep an eye open for anything different.
Sent from my SAMSUNG-SGH-T769 using xda premium
I just flashed the latest version of cm10.1 and now i have an R over my signal bar. Can someone tell me how to fix this? This happened once before when i flashed the 12182012 cm10.1 and it took me forever to fix.
Try this: http://forum.xda-developers.com/showthread.php?t=2066275. Try what's in the last post before following the instructions in the OP.
gocool767 said:
I just flashed the latest version of cm10.1 and now i have an R over my signal bar. Can someone tell me how to fix this? This happened once before when i flashed the 12182012 cm10.1 and it took me forever to fix.
Click to expand...
Click to collapse
BigErnM said:
Try this: http://forum.xda-developers.com/showthread.php?t=2066275. Try what's in the last post before following the instructions in the OP.
Click to expand...
Click to collapse
Yea we are in the hundreds of new posts on this one. Would help if some would read before they flash.
Agreed, it's getting ridiculous!
People know this.... 4.2 rom's have data problems. Practically every rom thread discusses this in a high level of detail. There are fixes if you read. Not gonna hand out this answer, as it's been said over and over in the forums. It's a source issue, even nexus devices are experiencing this issue.
Next, 4.2 will completely change your storage arrangement on your device. Legacy/and 0 folders will become dominant due to the multiuser features. Read, and learn what this will do, and how to recover from it if you downgrade back to 4.1. The op's all warn of these issues! :screwy:
Sent from my Nexus 7 using xda premium
annoyingduck said:
Agreed, it's getting ridiculous!
People know this.... 4.2 rom's have data problems. Practically every rom thread discusses this in a high level of detail. There are fixes if you read. Not gonna hand out this answer, as it's been said over and over in the forums. It's a source issue, even nexus devices are experiencing this issue.
Next, 4.2 will completely change your storage arrangement on your device. Legacy/and 0 folders will become dominant due to the multiuser features. Read, and learn what this will do, and how to recover from it if you downgrade back to 4.1. The op's all warn of these issues! :screwy:
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Damn Duck. Even the devices released with 4.2 have problems. How they think gonna be stable on unsupported devices. I have $600 device. I want everything it came with to go faster but not willing to have cutting edge broke ****.
Dog, it took me all of 2 min of reading to know to stay away from 4.2 on our s3 at this time. I agree, the hit or miss on data is to risky, especially when I'm a year and a half from an upgrade!
I'm running stock rooted pure Google 4.2.1 on my Nexus 7, and it is still a WIP. For custom roms, the multiuser partitioning for source/cm based roms is causing headaches. So much is different than 4.1. Simple theme engine themes are borking the devices, as the legacy folder doesn't know where to apply it. Brand new nexus and s**t is broken, how the hell is our s3 gonna be any better running this android version at this time! Hell, cm10 based roms are still lacking full Samsung source coding....
Sent from my Nexus 7 using xda premium
annoyingduck said:
Dog, it took me all of 2 min of reading to know to stay away from 4.2 on our s3 at this time. I agree, the hit or miss on data is to risky, especially when I'm a year and a half from an upgrade!
I'm running stock rooted pure Google 4.2.1 on my Nexus 7, and it is still a WIP. For custom roms, the multiuser partitioning for source/cm based roms is causing headaches. So much is different than 4.1. Simple theme engine themes are borking the devices, as the legacy folder doesn't know where to apply it. Brand new nexus and s**t is broken, how the hell is our s3 gonna be any better running this android version at this time! Hell, cm10 based roms are still lacking full Samsung source coding....
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Glad to see you duck. Haven't heard from you for a while. Hey man. I'm rockin stock deodexed,kerneled, tweaked, themed 4.1.1 with all the 4.1.1-4.2 inverted apps available. **** stable. Everything works. And no hiccups. I'm good to go. Running 1.72/384 with Quad of 6500. If they didn't see my right handed app button wouldn't know I was running TW. Fast and smooth enough for me and I can call home if I need to.
You too, been on eclipse aosp for the longest time. All decked out. Running a mix of Gunthermic's dh inverts, b-boys, and justins. Will be rocking some synergy once I finish up some beta theme testing
Hi, I have a wind mobile lg-p999dw (T-Mobile G2x)
I wanted to know that since official updates never came out for the g2x cyanogenmod and other roms were created.
Since it was an abandoned phone, developers put this phone in their priority list.
CM7 was very successful and it went all the way to a fully stable version of CM 7.2.
Ever since CM9 came out these teams lost hope.
Cyanogenmod, Eaglesblood, Hellfire, Paranoid Android, ...
When jellybean came out CM 9 for the G2x was abandoned at an early stage and development of CM 10 started.
My question is why, WHY WHY WHY hasn't a perfectly stable version of a jellybean rom for g2x not come out that is perfectly as stable like CM 7.2 while other phones like htc one x and samsung galaxy s iii that already get official updates and get the stable version of the rom?
Different reasons for different ROMs.
For some older ones there wasn't HWA, but a hacked together version that still wasn't perfect and things like the camera had issues.
For newer ones the only major problem seems to be that the radio just isn't working.
It came down to LG not releasing drivers/code. People could hack together some things, but that could only get us so far. LG did a lot of weird things with their code, I believe.
At least, in my lurking and search, that's how I understand it. I'd love to see a fully working jellybean rom for the G2x since my girlfriend got it from me as a hand me down.
Take a look through adampk's CM10.1 thread in the development section and it's User Thread here in the general section. You'll get a good view at what's not working and what everyone has tried. Maybe you can even help out.
Shamoy said:
Hi, I have a wind mobile lg-p999dw (T-Mobile G2x)
I wanted to know that since official updates never came out for the g2x cyanogenmod and other roms were created.
Since it was an abandoned phone, developers put this phone in their priority list.
CM7 was very successful and it went all the way to a fully stable version of CM 7.2.
Ever since CM9 came out these teams lost hope.
Cyanogenmod, Eaglesblood, Hellfire, Paranoid Android, ...
When jellybean came out CM 9 for the G2x was abandoned at an early stage and development of CM 10 started.
My question is why, WHY WHY WHY hasn't a perfectly stable version of a jellybean rom for g2x not come out that is perfectly as stable like CM 7.2 while other phones like htc one x and samsung galaxy s iii that already get official updates and get the stable version of the rom?
Click to expand...
Click to collapse
You have to understand that most of CM9 and CM10 builds right now are based on a deprecated kernel and a modified android framework, known as "hackfest", which lacks many functions needed in the newer OSes. If you try Adampk's build 6 with, optionally, my kernel, you will see that it is really stable and works well, but not the radio. This is being worked on actively.
Most of the teams you specified simply switched to a newer model, not because of a compatibility issue. Cyanogen left us because our phone maintainer, RC, couldn't fix the radio. If he did release it anyways he would've received a lot of complains, which he didn't want.
Why why why... Wah wah wah..
Sent from my LG-P999 using xda app-developers app
Mazout360 said:
You have to understand that most of CM9 and CM10 builds right now are based on a deprecated kernel and a modified android framework, known as "hackfest", which lacks many functions needed in the newer OSes. If you try Adampk's build 6 with, optionally, my kernel, you will see that it is really stable and works well, but not the radio. This is being worked on actively.
Most of the teams you specified simply switched to a newer model, not because of a compatibility issue. Cyanogen left us because our phone maintainer, RC, couldn't fix the radio. If he did release it anyways he would've received a lot of complains, which he didn't want.
Click to expand...
Click to collapse
Thanks for someone whose actively working on it and replying. Glad to have someone with the knowledge xP
Sent from my Nexus 4 using xda premium
How do I install google apps with CyanogenMod 10
Which Gapps do you recommend for the TMobile LG G2X P999?
Currently running:
gapps-jb-20120726-signed
cm-9.9.9-JB-p999-2(OS)
Issue I am having is major feedback when making a any calls on...
Mordephi said:
Which Gapps do you recommend for the TMobile LG G2X P999?
Currently running:
gapps-jb-20120726-signed
cm-9.9.9-JB-p999-2(OS)
Issue I am having is major feedback when making a any calls on...
Click to expand...
Click to collapse
Do a search for baseband.zip, or look in these topics, there should be links in them.
Sent from my LG-P999 using xda app-developers app
redmonke255 said:
Do a search for baseband.zip, or look in these topics, there should be links in them.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
WOW that worked great! Thank you very much. Do you know if there is a solutions for the bluetooth not connecting or no audio on bluetooth?
Downgrading your baseband to 2.3.3 is only known way to get working audio for Bluetooth calling at the moment
Sent from my LG-P999 using xda premium
Pain-N-Panic said:
Downgrading your baseband to 2.3.3 is only known way to get working audio for Bluetooth calling at the moment
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Or stock 2.3.4/based ROMs. It's not too bad you know : angel:
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
mansa_noob said:
Or stock 2.3.4/based ROMs. It's not too bad you know : angel:
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
Click to expand...
Click to collapse
LOL yeah I guess you could do that too. I'm just way too much of a tweaker/modder/flashcrazy to keep a stock phone!
Pain-N-Panic said:
LOL yeah I guess you could do that too. I'm just way too much of a tweaker/modder/flashcrazy to keep a stock phone!
Click to expand...
Click to collapse
Lol my wife won't let me mess with her nexus 4 but it drives me nuts that she can't change her battery icon to percentage and change lockscreen background and...omg I could go all day.
TwitchyEye said:
Lol my wife won't let me mess with her nexus 4 but it drives me nuts that she can't change her battery icon to percentage and change lockscreen background and...omg I could go all day.
Click to expand...
Click to collapse
Based on experience, it is generally not a good idea to mess with your wife's phone . LOL.
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
mansa_noob said:
Based on experience, it is generally not a good idea to mess with your wife's phone . LOL.
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
Click to expand...
Click to collapse
Lol so true! I'm just glad she's done with this one. The first day she got her new phone she goes how do you pull the battery? I go you won't need to. She goes
If only they had a head exploding emoji
In the past few days, I've seen that a lot of devices have started to get Lollipop ROMs, such as the 1+1, Xperia Z3, Galaxy SIII Mini, and even the SII. I am wondering, is there any developer currently working on Lollipop for the d2vzw/d2lte? If not, does anybody have any idea how to compile Lollipop for the SIII?
Been lurking around as well. Noticed that the i9300 and the i747 models (no longer unified) both have Alpha Lollipop roms in production. Currently on Moto X (First Gen) but would love to dust off the old GS3 to get an early taste of 5.0. Been looking into porting but it's well over my head, plus I don't want to be the guy who bricks his backup by trying to port an early rom build. Would love to see a thread pop up tho about a release
ThaSik1 said:
Been lurking around as well. Noticed that the i9300 and the i747 models (no longer unified) both have Alpha Lollipop roms in production. Currently on Moto X (First Gen) but would love to dust off the old GS3 to get an early taste of 5.0. Been looking into porting but it's well over my head, plus I don't want to be the guy who bricks his backup by trying to port an early rom build. Would love to see a thread pop up tho about a release
Click to expand...
Click to collapse
Carbon Rom is moving in that direction, but it will take some time to see a build I'm sure. They don't tend to release unpolished roms.. Especially on a new version of Android
Sent from my SCH-I535 using XDA Free mobile app
Deliquified said:
Carbon Rom is moving in that direction, but it will take some time to see a build I'm sure. They don't tend to release unpolished roms.. Especially on a new version of Android
Click to expand...
Click to collapse
Makes sense. Haven't been around the scene in a while (my Moto X is locked down tight) so I thought I'd take a peek and see if you guys were getting any Lollipop love just yet lol Thanks for the response and I look forward to what the devs push out soon!
Welp, did a bit of digging and got the rom working on my GS3 but unfortunately I have no signal (voice) but LTE is working. At this point I imagine it's a kernel issue unless someone knows otherwise. gonna do a bit more digging tonight to see if I can't fix the problem.
ThaSik1 said:
Welp, did a bit of digging and got the rom working on my GS3 but unfortunately I have no signal (voice) but LTE is working. At this point I imagine it's a kernel issue unless someone knows otherwise. gonna do a bit more digging tonight to see if I can't fix the problem.
Click to expand...
Click to collapse
Any update on the build? The d2att/ATT SIII has a working build already. http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Would it be possible to compile this for the VZW SIII?
glman1 said:
Any update on the build? The d2att/ATT SIII has a working build already. http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Would it be possible to compile this for the VZW SIII?
Click to expand...
Click to collapse
i wonder if it would be safe to flash that. are all d2lte phones the same
kidhudi said:
i wonder if it would be safe to flash that. are all d2lte phones the same
Click to expand...
Click to collapse
It's not safe. DO NOT flash an AT&T ROM on the Verizon variant.
kidhudi said:
i wonder if it would be safe to flash that. are all d2lte phones the same
Click to expand...
Click to collapse
Absolutely not. Only if it specifically states d2lte. This one says d2att which can and will brick your device
From my CM11 S3
I am really excited for a lolipop ROM. Do you guys know of any developers working on one for the VZW GS3?
johnston9234 said:
I am really excited for a lolipop ROM. Do you guys know of any developers working on one for the VZW GS3?
Click to expand...
Click to collapse
One of them may be updated, I'm not aware of any but I'm not always in the development forums anymore
From my CM11 S3
As the others have stated, I wouldn't recommend flashing the At&t variant even though we share similar hardware (basically the same). Since the GS3 is my backup, I tweaked their rom and it booted for me, but like I said, there is no voice/sms working even tho LTE does activate oddly. I went to the IRC to see what I needed to look into but the devs there confirmed that they are indeed working on a rom for you guys already and I know they have made better progress than me. Wasn't looking to duplicate efforts, so I said I'd just stop and wait like everyone else cuz it'll be so much safer in the end. Sorry if I got anyone hyped but legit builds are in the works by expert devs, so no worries!
Edit: What I tell ya http://forum.xda-developers.com/showpost.php?p=57012966&postcount=1502
Theres a VZW Lollipop ROM from Mastamoon that works pretty well. Its under his CM11.X thread though, a link on that thread is a page back or so.
Camera doesn't work, but you can download open camera from the market which works.
Edit:
Didn't realize @TheSiK1 already linked it.
MastaMoon said hes not really gonna work on it much though...
Are there other devs you talked to that are working in it or just MastaMoon?
Sent from my SCH-I535 using XDA Free mobile app
XdrummerXboy said:
Theres a VZW Lollipop ROM from Mastamoon that works pretty well. Its under his CM11.X thread though, a link on that thread is a page back or so.
Camera doesn't work, but you can download open camera from the market which works.
Edit:
Didn't realize @TheSiK1 already linked it.
MastaMoon said hes not really find work on it much though...
Are there other devs you talked to that are working in it or just MastaMoon?
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
CM12 official will be here soon enough. After reading a bunch of comments it's quite buggy. Personally I'm going to wait to flash it
From my CM11 S3
I'm using right now and considering, I found the first 4.4.4 ROMs much bugger than this one. Using it as a daily driver. Home button only works after screen is unlocked. Can't wake phone using home button.
sjpritch25 said:
I'm using right now and considering, I found the first 4.4.4 ROMs much bugger than this one. Using it as a daily driver. Home button only works after screen is unlocked. Can't wake phone using home button.
Click to expand...
Click to collapse
If its buggier than CM11 how come the home button doesn't work properly? Sounds like a bug to me, this is a good reason why a lot of people don't test things out until the bugs are worked out
From my CM11 S3
ShapesBlue said:
If its buggier than CM11 how come the home button doesn't work properly? Sounds like a bug to me, this is a good reason why a lot of people don't test things out until the bugs are worked out
From my CM11 S3
Click to expand...
Click to collapse
There's no question its not perfect.
I don't mind being a bit of a guinea pig as long as it doesn't brick my phone!
I'm just surprised its not more buggy than it is this early on!
Sent from my SCH-I535 using XDA Free mobile app
XdrummerXboy said:
There's no question its not perfect.
I don't mind being a bit of a guinea pig as long as it doesn't brick my phone!
I'm just surprised its not more buggy than it is this early on!
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
True, but I'm not one to always jump on a rom right away. Plus CM from cyanogen mod will be out soon enough anyways
From my CM11 S3
ShapesBlue said:
True, but I'm not one to always jump on a rom right away. Plus CM from cyanogen mod will be out soon enough anyways
From my CM11 S3
Click to expand...
Click to collapse
The build, at least for me, has been pretty great so far. The home button does in fact work, you just can't wake the phone with the home button. But I understand that people need something very stable to use, but I'm OK with a few bugs.