Related
What happened to the nightlies? Cyanogenmod and Rom manager both list the last one at 8/31? So nobody has really put together a new nightly in over a week?
***EDIT***
-In fact I just looked and every model phone on cyanogenmod.com has their nightlies suddenly stop on 8/31. Whats going on?
Maybe a major update will come out. Be patient if you don't want flames thrown at you.
Sent from my LG-P999 using XDA Premium App
Kernel.org got hacked, so servers with Android sources were taken down. Learn to use search, there are 100 posts about this on XDA.
So got cm seven latest build running great. But two questions I haven't seen answer to at all is Bluetooth crackling over headset so can't use with my trucks system I.e. illegal texting/calling and also might seem stupid but couldn't find Samsung mediahub. Came from infused 2.2.3 to cm hoping since was more popular might have working hub so I can still watch movies I bought when phone was stock lol
Sent from my SGH-I997 using XDA App
flastae24 said:
So got cm seven latest build running great. But two questions I haven't seen answer to at all is Bluetooth crackling over headset so can't use with my trucks system I.e. illegal texting/calling and also might seem stupid but couldn't find Samsung mediahub. Came from infused 2.2.3 to cm hoping since was more popular might have working hub so I can still watch movies I bought when phone was stock lol
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Bluetooth will never work on CM7. Also CM7 is AOSP-based, and it doesn't contain anything from the Samsung ROMS.
Its pretty much closest you can get to pure Google with no crap from Samsung or ATT.
Sent from my SGH-I997 using xda premium
flastae24 said:
So got cm seven latest build running great. But two questions I haven't seen answer to at all is Bluetooth crackling over headset so can't use with my trucks system I.e. illegal texting/calling and also might seem stupid but couldn't find Samsung mediahub. Came from infused 2.2.3 to cm hoping since was more popular might have working hub so I can still watch movies I bought when phone was stock lol
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
I had found a thread on another forum talking about a fix for this bluetooth issue with CM7 i haven't had a chance to try it myself but maybe you can test it out and let me know
http://forum.cyanogenmod.com/topic/21449-bluetooth-pairing-but-not-connecting/
it's the post by Regular Guy and people say that it worked for them so try it out and let me know
irdanoob said:
I had found a thread on another forum talking about a fix for this bluetooth issue with CM7 i haven't had a chance to try it myself but maybe you can test it out and let me know
http://forum.cyanogenmod.com/topic/21449-bluetooth-pairing-but-not-connecting/
it's the post by Regular Guy and people say that it worked for them so try it out and let me know
Click to expand...
Click to collapse
That will not work for the Infuse with CM7.
Spend a bit more time reading the forum (THIS one, not other ones) and you will learn the issue is specific to this phone, and no fix is coming anytime soon.
Well everyone, since my KANG thread in the development section has become a discussion thread since official CM nightlies started again, I've decided to redirect the discussion to here. I'm going to ask the thread in the development section to be closed, so it can stop taking up space there...instead we'll take up space here! Lol. But anyways I want this to basically be a continuation of the old thread...you can talk about your G2X questions, comments, problems, etc. here. This will be especially geared toward CM-related problems, but all G2X-related topics are welcome here I hope that everyone will continue to help each other out, and of course I'll monitor the thread to help as much as I can and research things if necessary. Enjoy!
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Kalm_Traveler said:
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Click to expand...
Click to collapse
Ya I couldn't stand that answer my phone wait for it to ring after I select answer was surely a big annoying thing that and wifi calling issues but other then that VERY usable can't wait for newer builds and development on 4.0.3..
I'm on his GB CM7 build and love it great great battery life only at 90% with descent use today.
Sent from my LG-P999 using xda premium
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
j.d.r said:
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
Click to expand...
Click to collapse
As it is always said, it is best to do a full wipe. You never know what issues may stick behind or get caused by not doing a full wipe, but give it a shot and report back and hopefully you don't have issues.
Sent from my LG-P999 using xda premium
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
I believe Hellfire sandwich is the most updated and closest to everything working build. But there's lots coming down the pipeline thanks to our AMAZING DEVS!!!
Sent from my LG-P999 using xda premium
What's the best source for finding out the status of official Cyanogen 9 work on the G2X? I am not interested in kangs or spin-offs.
joeyxl said:
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I haven't tried any of the other ICS roms, but been using HFS since the initial release. Obviously it's not perfect, but I've been running it everyday and don't have any major complaints
CM Nightly 226/Unnamed & Kernels
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
I've used Faux123's UV/OC kernels, but seem to have lost my copy of his v0.4.3 (long term CM7.1.0.1 support). So, the newest v0.4.8 and T15 or ELF Trinity's won't work with mine. I know chip's vary, but mine seems to not like even the ELF Trinity kernel (which has worked for a few peeps running CM7.1.0.1).
Anyway, the breakdown of my ramblings are:
1. Anyone try CM Nightly 226/Unnamed?
2. Anyone happen to have a copy of Faux123's v0.4.3 kernel (CM Battery Version, not the DS driver) lying around? Or a compatible Trinity (preferred, actually)?
Eh, I know #2 is more wishful thinking. I'm mostly interested in anyone's experience with Nightly 226/Unnamed.
Ah, good to be back on XDA and CM, at that. I rolled on MIUI for way too long. Nice GUI & the customization was awesome, but man is that sucker a memory hog! Not to mention the random reboots and screen freezes... I should have never left my good ol' CM. Hindsight and all...
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
long story short, i have a wiped g2x. power button is a ***** to turn on to the point that my finger tips are sore from trying to get it to boot into recovery since last night. i can only seem to get 2 different screens trying to do this:
a) the lg boot animation which promtly freezes as the phone has been wiped & i probably haven't held the volume down button
b) the s/w screen used for flashing a recovery, etc
the phone is not mine but trying to help someone out. is there a timing to releasing the buttons? seems that when it goes to the s/w screen, lg appears for only about a second and then straight to that one. any help would be appreciated.
edit: posted it here only because i'd been following the old thread which led me to this one. i was trying to update to the latest while this happened. i started a similar thread in q&a so if it doesn't belong i''ll remove it, thanks
I've been in a loop like this before. Make sure you have done a battery pull. I think the key is not to hold the volume down button so long, and then be patient for recovery to load, it takes longer than expected in this situation.
Good luck.
Nightly #225
my_former_self said:
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
Click to expand...
Click to collapse
Ah, you want to talk to me! I just went from CM7.1.0.1 Stable to #225. More stable, much faster than CM7 Stable, #225 really should be CM7.2 Stable.
#226 seems to have a bug with the lockscreen PIN. Go get #225 and don't look back.
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
dmwOtis said:
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
Click to expand...
Click to collapse
Lots have stated the same thing doesn't work for most some say it did. Worth a try if you haven't yet, no go for me
Sent from my LG-P999 using xda premium
Where is this getril app?
Sent from my LG-P999 using XDA
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I agree, this is by far the most annoying bug and the only "show stopper" I can think of on CM7. I do not think it's a 'phone-by-phone' thing, because if I flash to stock or Weapon G2X, my mic volume is fine. It's only on CM/CM-based ROMs, such as MIUI. I can't count the number of times where people have told me to "speak up" until I'm practically yelling into my phone. I think there's a bug with noise cancellation that causes it to be quieter than it should be.
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
imoumni said:
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
GetRIL went the other way for my phone (Wind Canada P999), recommending v11h. Any notes re: the different builds?
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