Related
So, this thread is not about when the Thunderbolt will get Cyanogenmod support, because I can search and find that.
This thread is about how "official" CM support works. When I go to the Cyanogenmod site, I see a list of officially supported devices, which if I guess, are made, maintained and released by their team? I've been following along Android forums for almost a year now and see a lot of phone users trying to give their respective phones a CM port or CM rom to use. I presume these are "unofficial" and are being put together "aftermarket" by outside developers.
How and will the Thunderbolt get adopted by the Cyanogemod team and be one of those official phones listed on their site?
I'd take the root plunge for a rom like CM, which seems to be heavily updated and maintened and has the updater which would make updates for me very easy.
The thunderbolt will eventually.. I believe the reason it's not "supported' right now is because it's still in alpha. They don't state official support until they have a solid build.
My location is in montevideo urugauy according to CM7 lol.. On the map it shows me my location but somehow it thinks im in uruguay.. Any fix for this?
marc314 said:
My location is in montevideo urugauy according to CM7 lol.. On the map it shows me my location but somehow it thinks im in uruguay.. Any fix for this?
Click to expand...
Click to collapse
Clearly you must move to Uruguay.
Sent from my ThunderBolt using Tapatalk
At this point CM7 support is mostly anecdotal experiences by users to assist other users.
necosino said:
Clearly you must move to Uruguay.
Sent from my ThunderBolt using Tapatalk
Click to expand...
Click to collapse
Mine had me in Paris somewhere. Get GPS Status from the market. From the app hit menu, tools, manage a-gps state. Hit reset. Then go through those again but hit download data this time. After that and a refresh, it should all be well.
Sent from my ADR6400L using XDA Premium App
obeygiant said:
Mine had me in Paris somewhere. Get GPS Status from the market. From the app hit menu, tools, manage a-gps state. Hit reset. Then go through those again but hit download data this time. After that and a refresh, it should all be well.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thanks man.. Let me try this out..
macewank said:
The thunderbolt will eventually.. I believe the reason it's not "supported' right now is because it's still in alpha. They don't state official support until they have a solid build.
Click to expand...
Click to collapse
Where is it even listed in alpha?
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Thunderbolt
All I see are messages in the Wiki that the Thunderbolt is not yet supported. I am not talking about the port(s) that are here in XDA... I'm referring to a release by the CM team.
I am not rooted, and haven't played around with Rom Manager, but is an alpha "official" version of CM listed in there for the Thunderbolt?
Bwangster12 said:
Where is it even listed in alpha?
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Thunderbolt
All I see are messages in the Wiki that the Thunderbolt is not yet supported. I am not talking about the port(s) that are here in XDA... I'm referring to a release by the CM team.
I am not rooted, and haven't played around with Rom Manager, but is an alpha "official" version of CM listed in there for the Thunderbolt?
Click to expand...
Click to collapse
slayher is part of the CM team and the thunderbolt CM7 he's building is the "official" version. it's not listed under the officially supported devices because the code isn't anywhere near stable enough to be considered a daily driver. it's buggy, things don't work like they should. it's not release quality software yet.
all CM builds are technically ports. the base CM code doesn't just magically work on all phones by itself. there are specific people assigned as vendor maintainers that are generally responsible for making sure that CM works on their individually assigned device. see http://wiki.cyanogenmod.com/index.php?title=Community_Members for a list.
edit: i'm sure I did a poor job of explaining it and there's way more to it than what I described, but that's the gist. hope it makes sense
The CM7 alpha for the Thunderbolt is awesome. I have yet to find anything that it does not do well... except wireless tether..
4g, wifi for some people, battery life, soft buttons lighting up, call volume, getting settings to stick.
Just some of the bugs still plagueing CM7 for the thunderbolt.
Sent from my ThunderBolt using XDA App
It seems to be coming along nicely from my end user perspective. I'm running the pre-alpha pre-release on my TB from http://forum.xda-developers.com/showthread.php?t=1049542
I've been using it as a daily driver because of its Netflix support. One of the users in that thread posted a kernel and wifi fix which seem to greatly improve wifi and data connectivity, at least for me. I can deal with some minor bugs and annoyances. I'm just happy to have Netflix.
So once it becomes more stable, is considered a daily driver and presumably added to their support page....it will show up in rim manager and have the cyanogenmod updater support?
Right now for updates, you havta just keeping flashing the time from ur flash card right?
Bwangster12 said:
So once it becomes more stable, is considered a daily driver and presumably added to their support page....it will show up in rim manager and have the cyanogenmod updater support?
Right now for updates, you havta just keeping flashing the time from ur flash card right?
Click to expand...
Click to collapse
yep! i don't suspect it will be too much longer before we've got official support. exciting times
It's the only LTE phone. That's why it will take a while to get all bugs cleaned to be in the supported list.
Sent from my thunderbolt
Thats fine... didn't mean this to sound like a pushy thread. I thought the description given in this thread was fantastic, thanks. I was unclear as to what exactly happens when CM releases a rom.
I haven't rooted yet, but am sort of waiting for CM. From what I've read, it seems to be one of the most stable and maintained roms available and one of my main concerns is "quality" and maintaince/updates. Some of the roms available now sound good, but I don't wanna deal with having to be flashing left and right when new updates get released by Verizon.
My assumption with CM is that I can put install it with Rom manager and worry about updates using their Updater, right? Any GPS issues, battery concerns, whatever would be dealt with by CM?
I haven't seen or heard about when the OTA ICS updates will resume. Maybe I'm not looking in just the right places, but all of my searches (web & xda) don't have any new information.
Has anybody heard about when the updates will resume? I have the i9020a, but I guess I'm asking more generally.
Sent from my Nexus S (i9020a) using xda premium
What makes you think ICS OTA was stopped ?
I went back to GB for a day 3 weeks ago and the notifiaction to update to ICS keeps coming and annoying me ... One of the causes I revert back to ICS was the annoying update notification...
PS:My phone is I9020T BTW
Just haven't received any notification to update, and all the news I could find said it had been paused a few weeks ago but there was nothing new or recent saying that the pause was done with. At least that I could find.
That's because you have i9020T.
Google haven't release ICS update for I9020A yet.
kerry_xu_cs said:
That's because you have i9020T.
Google haven't release ICS update for I9020A yet.
Click to expand...
Click to collapse
If that's the case, I feel better about the lack of an update. So then it's a waiting game at this point.
Thanks.
i'm on i9023 and even i havent got it.. there hasnt been any news since they stopped the ota.. even am wondering if we'll ever see a official update..
i heard some rumor that Google has stop OTA temporarily due some bug ???
I heard it was because of battery issues. True or not don't know, but im guessing there's probably more to it than that. Been waiting along time for it tho.
Nexus s 4g completely stock. 2-5 fC's a day. Lets get this show on the road.
Well...
didmywillybiteya said:
I heard it was because of battery issues. True or not don't know, but im guessing there's probably more to it than that. Been waiting along time for it tho.
Nexus s 4g
Click to expand...
Click to collapse
I've been continuing to look around online to see what I could find, and I've stumbled across a seemingly useful thread on the Google Mobile Help Forum. I haven't made 8-10 posts on XDA yet, so I cannot provide an outside link here. I'm sure I could PM it to anybody who asks.
To sum up what I've found, it looks like they're still collecting data about the issues that users are having with the ICS update on the Nexus S. A Google employee provided links on where to report specific issues, which would include the battery issue that you had mentioned.
However, it still doesn't quell any concern about when they're going to have those issues corrected, or how much progress they have made so far.
Why wait ?
Don't wait for the OTA, root your phone and install any one of the amazing choice of developer ICS ROM's to your phone
I chose the ICS version by Peter Alfonso http://download.peteralfonso.com/crespo/rom
(in tandem with Eugene's Speedy Kernel) http://forum.xda-developers.com/showthread.php?t=1401455
and it's brilliant !
Haven't had one FC in three weeks of use and battery life is astounding
Go for it, it's easy to install and if you don't like you can simply revert back to your current ROM (so long as you used ROM Manager and made a backup of course)
Root is the way to go.
ICS is having battery problems. Go with a custom as mentioned above. I went with the [ROM][25-01-12][AOSP][4.0.3] Codename Android 1.2.0|Fully Open Source and its amazing!
Sent from:
Ice Cream Sandwich 4.0.3
I9023a
AOSP Codename Android 1.2.0
Or just compile it yourself. The code is there.
Sent from my Nexus S using Tapatalk
Best ICS ROM
I have been using Crossbones after testing out another well known rom. Crossbones seems to have the magic. The developer is very concerned with stability and only adds features if it works well. No random crashes and few bugs. But he rightly labels his current build a beta which I respect. Others are labeling their betas, stable builds. If you are looking for a good rom with lots of potential check this one out. Oh and BTW great battery life.
Thank you all for your suggestions.
I used to flash ROMs on my Captivate, and kept my Nexus S as a Google OTA phone. Though, considering this whole ICS mess, I'm considering going the way of the custom ROM on this device too.
I might give it another week or two, and see if anything happens by the start of February.
anonchalantsigh said:
Thank you all for your suggestions.
I used to flash ROMs on my Captivate, and kept my Nexus S as a Google OTA phone. Though, considering this whole ICS mess, I'm considering going the way of the custom ROM on this device too.
I might give it another week or two, and see if anything happens by the start of February.
Click to expand...
Click to collapse
If you have a linux machine compile it yourself, or pick one of many custom ROM's out in the development section or get mine from my signature, the lightest ICS Rom out there. No battery issues for me, lasts 2 days on medium usage.
Hmm i saw that Google stopped the update on some regions including mine -_- to gather feedback ...
Good ICS ROM
Checkout this ROM, it comes with the kernel in that integrated package.
http://forum.xda-developers.com/showthread.php?t=1425344
Don't wait for the OTA update, just flash this awesome ROM and chose the KERNEL that fit your needs !!!
Google it's way behind on ICS
my setup at the moment
CODENAME ANDROID 1.2 | Matrix v15 cfs
I have rooted and tried a couple ice roms but found them not much better. It was at the end of November tho, went back to stock hoping for the ota. I do know that there are some awesome builds out but I don't wanna wipe again just yet but I'm getting close.
I keep getting the update notification on my nexus S, I'm trying to figure out if this ICS upgrade that my phone keeps telling me about is the same with bugs etc or a fixed one...anyone know?
Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
slacka-vt said:
Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
Click to expand...
Click to collapse
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
nadiros said:
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
Click to expand...
Click to collapse
I'm glad to see I wasn't the only one bugged by the 3G signal showing in the status bar on Wingray. It wasn't a huge deal, but one of those little things you always notice once you see it the first time. There were a few other things, but overall it's a nice build.
I also use AOKP on my Nexus S as a daily driver and I'm very happy with it. No big issues to call out. Once the wingray builds progress a bit more and those few little bugs are worked out, I'll most likely switch to it as my main rom.
Build 25 - 3G icon bars still there.... feels superficial however I didn't test much further . I will continue to periodically check in on them... but like I said - for this aspect to be overlooked then they're not paying attention to wingray for some reason
I am used the Kang rom for a while primarily because it has volume button wake built in. But after a while that tweak just stopped working so now I'm back on Bugless Beast for Xoom.. There's still plenty room for improvement for the Kang rom so I'll try it again at a later stage.
I've built from source and removed the 3G radio icon. It's something I'm sure they'll get to. I noticed someone posted a bug report on that to them already. I posted what they need to do to get rid of it. I might post my build but only after getting permission to do so from them. Run's great with my oc kernel.
Well from what I see they (Team Kang) have discontinued their Wingray builds. Rootz wiki has a pitiful thread that has dwindled and I see only a Stingray release for Xoom as far as the latest build 30.
WTF !
Anyone know whats up?
Great so far but one question to those using it.
Allow apps to write to SD card is in the feature list.
How do I access this? Using various apps I can only write to media memory. Even if I change the path to /mnt/external1/. It just creates that folder within the internal memory.
Any help would be appreciated.
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 was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!
brob925 said:
I was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!
Click to expand...
Click to collapse
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app
ethantarheels123 said:
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?
brob925 said:
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?
Click to expand...
Click to collapse
The night lies have been down because some changes were made to the code upstream that causes the Evita build to fail. They're working on the kernel fixes to get the night lies to compile again but apparently its very involved.
Sent from my One X using Tapatalk 2
There was an experimental one posted today
my wifi doesn't crap out on the experimental nightly which was my only issue with 10/12
One should always read at min the last 10 pages of a thread of a Rom you might flash, an really it's expected of anyone.
WR
Sent from my HTC One X
Just a heads up dont know if anyone else is having this problem.
I rooted my 2.2 with the new 2.2 root instructions and downloaded the latest (10/25:experimental[cm-10-20121025-EXPERIMENTAL-evita.zip ]) cm10 build, everything works great, even wifi, except MOBILE data. I'm on straight talk, and man im getting slow speeds, nothing changed to APN, i think its a radio problem. anyone got any suggestions? I attached the radio link, which radio should i flash?
http://forum.xda-developers.com/showthread.php?t=1694012&page=99