Im just wondering.... is there going to be another cm9 release or is the alpha 6 version the last one? I've noticed that cm10 is getting updated, so have they moved on? I also tried checking the cm website and can't find the E4GT section. Ive been holding out on rooting and setting up cm9 for something past alpha stage but im getting tempted too much to load alpha 6 version.
Sent from my SPH-D710 using xda app-developers app
whitelight said:
Im just wondering.... is there going to be another cm9 release or is the alpha 6 version the last one? I've noticed that cm10 is getting updated, so have they moved on? I also tried checking the cm website and can't find the E4GT section. Ive been holding out on rooting and setting up cm9 for something past alpha stage but im getting tempted too much to load alpha 6 version.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
There have been many nightlies that blow alpha 6 away. Go to the CM9 thread in the original development section for details...
Edit. It is very stable now and well worth a daily driver. Hope this helps!
Sent from my SPH-D710 using Tapatalk 2
I'd say its past alpha status. Pretty much an RC release, just haven't been officially merged into CM yet which chris41g has been working on. Like the guy above me said, very stable and a good DD.
Sent from my Nexus 7 using Tapatalk 2
Thats music to my ears. Im going to look for it. Is it still using the, i believe, modified gb kernel or is it using a ics kernel? Being in stock ics (ff18), would it be a problem?
Sent from my SPH-D710 using xda app-developers app
whitelight said:
Thats music to my ears. Im going to look for it. Is it still using the, i believe, modified gb kernel or is it using a ics kernel? Being in stock ics (ff18), would it be a problem?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
CM9 never used a modified gingerbread kernel, we were flashing it with a gingerbread cwm repack to avoid the eMMC super brick bug.
Nightly 7-31 (which had no data due to a RIL change) was the last FF18 based kernel, initramfs was repacked with the startup scripts for AOSP etc. 7-17 Nightly was my favorite out of those.
Chris41G has had some source kernels out for awhile and starting with the 8/02 nightly they have been included. Early ones and the RC13 and older kernels had some problems with 4G and thanks to a ton of time Chris put into it the current ones shouldnt. Im runnin Chris's builds rather than the nightlies though.
So now there is no worries in the "super brick" thing?
Sent from my SPH-D710 using xda app-developers app
whitelight said:
So now there is no worries in the "super brick" thing?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The brick is triggered by a function being called with a particular switch but it only happens when the kernel or program has been compiled against a particular library. Thats a basic and slightly outdated view on the problem more info can be found here - http://forum.xda-developers.com/showthread.php?t=1644364
The Galaxy Note actually shipped with ICS and no work around and factory resetting was like playing russian roulette with the phone. The International is supposidly safe but based on the kernel source for FF18, our phone does not have a work around in place on FF18. The bug itself will never be fixed on our end. It requires flashing the eMMC firmware which can generally only be done by an eMMC partner.
Basically any time a partition is formatted without work arounds in place a bug in the eMMC controller could randomly corrupt storage at a very low level. These formats occur during Factory resets and when flashing a rom, etc.
Safe recoveries are worked around so that factory resetting and wiping partitions is safe. The danger still lies in scripts making the call, that as well has been worked around either blocking a certain call or replacing it. The final danger is zips, usually for roms with an unsafe Updater Binary. CM9 Alpha 5 for example does not have a safe updater binary, from what I know the stock roms don't either. There are recoveries setup to swap this element out to make flashing safe altogether. Can't tell you how common that is at this point I do not keep up.
Source kernels have more safeguards than just recovery repacked, but something is better than nothing as well.
RainMotorsports said:
The brick is triggered by a function being called with a particular switch but it only happens when the kernel or program has been compiled against a particular library. Thats a basic and slightly outdated view on the problem more info can be found here - http://forum.xda-developers.com/showthread.php?t=1644364
The Galaxy Note actually shipped with ICS and no work around and factory resetting was like playing russian roulette with the phone. The International is supposidly safe but based on the kernel source for FF18, our phone does not have a work around in place on FF18. The bug itself will never be fixed on our end. It requires flashing the eMMC firmware which can generally only be done by an eMMC partner.
Basically any time a partition is formatted without work arounds in place a bug in the eMMC controller could randomly corrupt storage at a very low level. These formats occur during Factory resets and when flashing a rom, etc.
Safe recoveries are worked around so that factory resetting and wiping partitions is safe. The danger still lies in scripts making the call, that as well has been worked around either blocking a certain call or replacing it. The final danger is zips, usually for roms with an unsafe Updater Binary. CM9 Alpha 5 for example does not have a safe updater binary, from what I know the stock roms don't either. There are recoveries setup to swap this element out to make flashing safe altogether. Can't tell you how common that is at this point I do not keep up.
Source kernels have more safeguards than just recovery repacked, but something is better than nothing as well.
Click to expand...
Click to collapse
Excellently said. Perfect!
Could you link my to Chris's latest/ most stable builds/kernels? Thanks
Sent from my SPH-D710 using Tapatalk 2
timmetal6669 said:
Excellently said. Perfect!
Click to expand...
Click to collapse
Thanks. I am sure anyone on my level with working memory and who has kept up can explain it a little better. Its been awhile for me. I know the mmc cap erase switch on the format call was the suspected culprit but in the end that didnt seem to matter it was then being looked at that the Android 4.0 kernel was compiled against a library for makeext4fs or something.
fabolousrmx said:
Could you link my to Chris's latest/ most stable builds/kernels? Thanks
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I also tried searching for his rom builds but i get other things. I googled but the closes i got to was a kernel and not sure if it was for E4GT.
Sent from my SPH-D710 using xda app-developers app
whitelight said:
I also tried searching for his rom builds but i get other things. I googled but the closes i got to was a kernel and not sure if it was for E4GT.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
www.chris41g.devphone.org
Sent from my SPH-D710 using Tapatalk 2
Related
Sent from my SPH-D710 using xda premium
nope it just sets at the screen when it should be playing. Boy does that suck.
Ditto. Sometimes sound plays; but muffled. Awesome Rom though, loving it otherwise.
Sent from my SPH-D710 using xda premium
Wow. Huge downgrade. No thanks.
works for me don't know why.
Sent from my SPH-D710 using Tapatalk
Twinsen72 said:
Wow. Huge downgrade. No thanks.
Click to expand...
Click to collapse
Huge downgrade for something that's in alpha stage to not be working perfectly?
Netflix upgraded to work with android 4.x back in december with the galaxy nexus release. Like other people who saying I think it's more to do with the actual rom than anything else. I'm sure with the next series releases these minor compatibility issues will be fixed.
Its netflix now but what else isn't working? There are programs other people use on a daily basis not seen at the moment with the current developers and testers using this beta style rom. We are not status quo. There's only a few people using calk's fb17 release at the moment...100 max I am willing to gamble.
The real question is what else isn't working? What other programs like netflix are not running correctly on this version of ice cream sandwich. Maybe there's an off chance that we can isolate the problems similar to what's going on with netflix and other programs and somehow cross check them together with other programs/APKs to find some related issue and tackle it from there.
Until then, like others, I'm gonna stay back on a regular android 3.x rom and work from here because I can't make it through my work night without netflix. It's too damn boring here at usps. 2 hours of work and 6 hours of downtime makes kevin a dull boy. here's hoping an even more stable release is put out so that we can have basic yet minor things like netflix back. Even though it may not seem that important to some other joe schmo across the internet at least a few of us actually desire something like netflix so I wouldn't judge too much.
Oh and by the way, I think this is working with my fb15 version last night so who knows maybe its just some issue isolated to the fb17 rom. I would check but I'm not at home. I really don't feel like temporarily breaking my phone for the evening. If someone wants to check to make sure you could try to flash the old fb15 release and see how netflix runs on that...or if it runs at all.
Sent from my SPH-D710 using XDA App
Netflix its working on mine.
Sent from my SPH-D710 using Tapatalk
Like every other release for any OS, software patchwork needs to be done. What is truly exciting about ICS is that Google is requiring manufacturers not to mess with the base of the OS. Which means developers update once and it should be compatible with all. Its exciting mainly because some cool devs for ios have been holding back due to android manufacturers messing around. Now they should easly convert to android.
Robbzilla said:
Netflix its working on mine.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Quick question, and I'm not sure if it matters or not but how did you go about flashing calks rom? I can think of 3 or 4 different ways I can go about getting everything installed with this fb17 rom. I'm trying to figure out the difference between what you did what I did and how I can possibly get this to work for my phone. last time I installed it on a freshly flashed cwm as well as the fb15 modem. Then I even reverted back to stock el29 modem and rom, then installed calks rooted and deodexed fb17 rom keeping the el29 modem (doubt it matters much which modem I had). just wanted see if you did nothing there for different...or...something
Edit: Dang speak and spell screwed up everything...lol
Sent from my SPH-D710 using XDA App
Wanted to get a discussion going over a much debated and discussed topic....flashing ICS roms with ICS kernels. I want to know the forums specific attempts so we can better understand user errors versus software errors versus hardware errors.
I bring this up as I went from el29 to fc07 a while back and have been on ICS since. I am now on FC22 courtesy of agat63, which I flashed over calks fc18 v2 from. Before that I went from stock rooted fc15 to calks. This was all done using either rogue recovery fc07 or rogue recovery fc22 and using calks format all zip or modified format all zip.
Does it seem this was all "lucky"? I have a feeling many of these brick issues are due to people trying to flash between an AOSP type rom to another and/or using ROM Manager to do so. So lets hear it . . .
Sent from my SPH-D710 using XDA
wow, finally an official thread to discuss this rare issue......
Burn
10char
Wow a troll in xda. No way....
http://troll.me/images/futurama-fry/not-sure-if-trolling-or-just-retarded.jpg
Sent from my SPH-D710 using XDA
The bricking is related to (I think) data partitioning in the ics cwm recovery. If you wipe anything, something is most likely going to go wrong.
Sent from my SPH-D710 using Tapatalk
Overstew said:
The bricking is related to (I think) data partitioning in the ics cwm recovery. If you wipe anything, something is most likely going to go wrong.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
That's what I'm trying to boil down to....I have done bith wipes and zip formats, yet no issues....some methods or ROMS are leading into this so I'm hoping the brickers out there can give some feedback on exactly what was flashed and on what ROM, along with some success stories to try to figure out the issue.
Sent from my SPH-D710 using XDA
I dont mind firing up the Pc to run Odin, it justifies the 500+ I spent on it 4 months ago.
phatmanxxl said:
I dont mind firing up the Pc to run Odin, it justifies the 500+ I spent on it 4 months ago.
Click to expand...
Click to collapse
Agree, love Odin. Just wanna stop the brick posts and hope we can formulate a solid practice on how to prevent it.
Sent from my SPH-D710 using XDA
dante32278 said:
Agree, love Odin. Just wanna stop the brick posts and hope we can formulate a solid practice on how to prevent it.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Someone said once the source is released the risks should be minimal.
Also true....but with all the leaks going around and flashaholics it'd be good to have some guidelines til then, other than speculation. "I believe in science."
Sent from my SPH-D710 using XDA
Overstew said:
The bricking is related to (I think) data partitioning in the ics cwm recovery. If you wipe anything, something is most likely going to go wrong.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
In addition,
CM9/AOSP/AOKP seem to increase brick chances.
CMW Touch espicially with ROM Manager is espicially dangerous and should not be touched.
zonlicht said:
In addition,
CM9/AOSP/AOKP seem to increase brick chances.
CMW Touch espicially with ROM Manager is espicially dangerous and should not be touched.
Click to expand...
Click to collapse
This is what I hear the most. Has anyone else had success with flashing stock ROMs via clockwork on a stock(ish) ICS ROM? By this I mean based off fc07/15/18/22 (calk/agat63/goodness) and not CM9/AOKP/etc...
Sent from my SPH-D710 using XDA
I'm dying to run CM9 on my CDMA gnex. How do these (nightlies) work?
Sent from my Galaxy Nexus using xda premium
They are unstable roms that are constantly being worked on. The current nightly is the progress they've made so far. I haven't tried cm9 specifically, but certain features most likely don't work/ aren't included yet. I recommend reading through the change logs so u have an idea of what's going on. Just back up whatever rom you're currently on and if u flash cm9 don't forget gapps.
Sent from my Galaxy Nexus using XDA
You will need to unlock and root your phone before installing the nightlies.
http://forum.xda-developers.com/showthread.php?t=1693892
Then I use ROM Manager to install the nightlies.
bwood20 said:
They are unstable roms that are constantly being worked on. The current nightly is the progress they've made so far. I haven't tried cm9 specifically, but certain features most likely don't work/ aren't included yet. I recommend reading through the change logs so u have an idea of what's going on. Just back up whatever rom you're currently on and if u flash cm9 don't forget gapps.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
While they are nightlies, they are not unstable. Everything should work, but there are missing features.
If installed is there an ota update pushed to my phone or like any other rom and wipe etc and flash updated rom?
Sent from my Galaxy Nexus using xda premium
fk.gregor said:
If installed is there an ota update pushed to my phone or like any other rom and wipe etc and flash updated rom?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No ota's, you have to flash each one yourself. However, you usually don't have to wipe unless a major change is incorporated.
Ok. Would it be worth flashing iyo?
Sent from my Galaxy Nexus using xda premium
The nightlies are far from unstable - I've been a CM desciple for a looooong time on many different devices. Everything works for me. No problems what-so-ever.
I realize it's not for everyone but I strongly recommend you give it a shot. Make a nandroid and flash away.
It's worth flashing. You can use ROM manager to download and flash updates, so it's no sweat to update when you want.
Fyi if you want to download and install nightlies through ROM manager, you have to buy it.
Swyped on my CM9 Galaxy Nexus
Herman76 said:
It's worth flashing. You can use ROM manager to download and flash updates, so it's no sweat to update when you want.
Fyi if you want to download and install nightlies through ROM manager, you have to buy it.
Swyped on my CM9 Galaxy Nexus
Click to expand...
Click to collapse
You shouldn't rely on rom manager though. Maybe for downloads but always install manually.
"Long is the way, and hard, that out of hell leads up to light."
Sweet. I'm pretty stoked to give this a shot!
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
You shouldn't rely on rom manager though. Maybe for downloads but always install manually.
"Long is the way, and hard, that out of hell leads up to light."
Click to expand...
Click to collapse
Why install manually?
tsaunders said:
Why install manually?
Click to expand...
Click to collapse
ROM Manager can screw installations up and usually if recovery throws an error you won't see it if you flash through ROM Manager.
"Long is the way, and hard, that out of hell leads up to light."
I agree to some extent, but if you are familiar with manually flashing, I don't see any problem with using ROM manager to flash.
I have been using it since my sgs days and never had any hiccups.
Swyped on my CM9 Galaxy Nexus
Herman76 said:
I agree to some extent, but if you are familiar with manually flashing, I don't see any problem with using ROM manager to flash.
I have been using it since my sgs days and never had any hiccups.
Swyped on my CM9 Galaxy Nexus
Click to expand...
Click to collapse
I believe you, most people have no problems but some do so I just try to tell people to do it manually.
"Long is the way, and hard, that out of hell leads up to light."
I will just echo what some others here have already said. In my experience, CM nightlies (7 and 9 on various devices) aren't unstable at all, perhaps missing some features at times, but far from unstable. Of course each device may have a different story, but I think it is definitely worth a shot.
What sort of features are missing?
Sent from my Galaxy Nexus using xda premium
fk.gregor said:
What sort of features are missing?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Comparing to stock, no features are missing and many have been added. Comparing to what is planned for the "stable" release of cm9 then, yes, features are missing.
Every now and then changes get made which will break some part of the phone, but they are mostly annoyances, it's extremely rare for a nightly to break core functionality of the device but it could happen.
Been using cm since version 6, always running nighties and none of them have ever broken my phone. Sometimes things have happened like breakages to video playback for example but they get fixed pretty quick. I've always been able to do stuff like making calls, SMS and email on every nightly over five phones.
Sent from my GNex
Alright so I flashed it and instantly loved the boot image. It's sick!
Sent from my Galaxy Nexus using xda premium
I'm pretty sure I flashed the latest gapps but they weren't on there...
Sent from my Galaxy Nexus using xda premium
Im getting my ET4G on the 14th, So I decide to do some research on it (which is what everyone should do anyways) and I stumble upon the ICS kernel, data wipe hard brick, and I wonder to myself, Why hasn't the option to wipe data been removed from ICS kernels(cwm)? it would save alot of ppl (albeit ppl who don't know how to research first) alot of time and potentially money, hell i mean no one can even wipe in ICS anyways right? so why even allow the option until a workaround is found?
holy monky! so simple, yet brilliant. im sure somebody is gonna come along and say....nevermind..... good call though!
Sent from my SPH-D710 using xda premium
probably right, but hey, my phones (most likely) not gonna get bricked.
its a sad day when someone destroys a phone they just got, especially doing something simple like wiping the data partition.
maybe even just a warning when you wipe that it could brick your phone on ICS, shouldn't be that hard, its already got a confirmation dialogue
zeruth said:
Im getting my ET4G on the 14th, So I decide to do some research on it (which is what everyone should do anyways) and I stumble upon the ICS kernel, data wipe hard brick, and I wonder to myself, Why hasn't the option to wipe data been removed from ICS kernels(cwm)? it would save alot of ppl (albeit ppl who don't know how to research first) alot of time and potentially money, hell i mean no one can even wipe in ICS anyways right? so why even allow the option until a workaround is found?
Click to expand...
Click to collapse
ICS kernel source hasn't been released for the epic touch yet. So there's no way to remove the command that's causing the bricks.
Sent from my Galaxy Nexus using XDA
It's been done already on some kernels and other work arounds have already been found, until source drops.
This thread goes into exceptional detail. The devs and some users have gone to tremendous lengths researching the specific cause. I believe samsung actually threw in a little help as well. http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SPH-D710 using Tapatalk 2
times_infinity said:
ICS kernel source hasn't been released for the epic touch yet. So there's no way to remove the command that's causing the bricks.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
May be true but you can work around it. Chris41g and Dees_Troy did so with TWRP recovery by working around the command so it isn't called when you wipe data and by having a safe GB update-binary used when flashing zips. Also isn't sbrissens kernel safe?
Sent from my SPH-D710 using Tapatalk
slick_rick said:
May be true but you can work around it. Chris41g and Dees_Troy did so with TWRP recovery by working around the command so it isn't called when you wipe data and by having a safe GB update-binary used when flashing zips. Also isn't sbrissens kernel safe?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
This is very true. The suppress_emmc_wipe feature implemented into ext4_utils along side the gb update-binary is a good alternative for now. Also, sbrissens kernel is safe, just not ready for prime time yet
Sent from my Galaxy Nexus using XDA
okay i finally found a link and was able to flash if anyone is interested...
from numerous attempts before; this is how i was able to flash
1 - Mobile odin el26cwm
2 - Factory Data/Reset
3 - Wipe Cache
4 - Wipe Davlik-cache (under advance)
5 - Format system (under mounts and storage)
6 - Install update-cm-7.2.0-RC6-epic4gtouch-KANG-signed.zip
7 - Install gapps-gb-20110828-signed.zip
8 - Reboot
Setup files needed:
ROM - http://minus.com/lidQKBHor76kG
GAPPS - http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
Original Thread and dedication - http://rootzwiki.com/topic/12440-ro...ha-6-1-15-2012-i-cant-believe-its-not-butter/
Sorry we don't have a fully stable cm7. Nor a current non stable build of cm7.
we dont have a fully stable anything really ? but without being a smartass cuss i didnt mean it haha, can u hand me a link or is it dead and gone ? i thought i found one but it didnt boot stuck at splashscreen
http://rootzwiki.com/topic/12440-ro...2-i-cant-believe-its-not-butter/page__st__710
That is the closest thing to CM7 that has been released publicly for this phone. I'm not sure about all the issues but I kno for a fact that 4G doesn't work with it. I think a this point you would probably be better off with CM9 or maybe even CM10.
I tried building CM7 for this phone and there was some issues that I didn't feel like it should be released. The ROM itself was smooth, but it was far from a daily driver.
As far as I know times_infinity has also built CM7 with the same issues I was experiencing. Using the kernel bubby hacked together was a nightmare. If it happens, we need a new kernel.
I will eventually get back around to working on it again.
Sent from my SPH-D710 using xda premium
Mattix724 said:
I tried building CM7 for this phone and there was some issues that I didn't feel like it should be released. The ROM itself was smooth, but it was far from a daily driver.
As far as I know times_infinity has also built CM7 with the same issues I was experiencing. Using the kernel bubby hacked together was a nightmare. If it happens, we need a new kernel.
I will eventually get back around to working on it again.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
yeah that rom wouldnt boot 8^(
Along the same lines, what happened to cm9? Why is the thread closed if nightlies are still happening according to the website?
Sent from my SPH-D710 using xda app-developers app
Lonbobby said:
Along the same lines, what happened to cm9? Why is the thread closed if nightlies are still happening according to the website?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Darchstars CM9 thread was closed because he is no longer working on our device. Check again in original development.
Sent from my Nexus 7 using Tapatalk 2
Chris and team epic have a beta 1 in original development. Nightlies are at goo.im/devs/shabbypenguin
Experimental builds done multiple times in a day sometimes are at goo.im/devs/chris41g/cm
sent from my BAD A$$ Epic touch
bump for updated op