just curious if theres a finished cm9 or cm10 mod for the htc one s or if they are all still working out the bugs right now. i tried looking some up but only found a couple that seem to still be a work in progress
Well since the ones you saw that there were still bugs in some..you are safe to assume that there's no completely working ROM. There are only little kinks, not major bugs like data not working or something.
invasion2 said:
Well since the ones you saw that there were still bugs in some..you are safe to assume that there's no completely working ROM. There are only little kinks, not major bugs like data not working or something.
Click to expand...
Click to collapse
ok cool good to know. well seeing how theres a couple of them still in development would there be one you would suggest over the other?
CM10 is producing official nightlies. I have been using it as my daily driver since the first day they started nightlies, and have very few (if any) issues. The occasional hiccup here and there, but nothing that stops me from using it as a daily driver. And I am on my phone constantly, mainly for work.
Here's the link to the download for official CM10: http://get.cm/?device=ville
Remember, because it's nightlies there is an updated version everyday. Sometimes big changes, more often than not little stuff.
Here's the changelog: http://changelog.bbqdroid.org/#ville/cm10/next
When downloading, be sure to use the NIGHTLIES and not EXPERIMENTAL (if you are looking for stability).
I also recommend using Fusion Kernel with this rom. Works wonders.
Here's the link to the kernel: http://forum.xda-developers.com/showthread.php?t=1837630
If I helped, hit thanks
tgtoys said:
CM10 is producing official nightlies. I have been using it as my daily driver since the first day they started nightlies, and have very few (if any) issues. The occasional hiccup here and there, but nothing that stops me from using it as a daily driver. And I am on my phone constantly, mainly for work.
Here's the link to the download for official CM10: http://get.cm/?device=ville
Remember, because it's nightlies there is an updated version everyday. Sometimes big changes, more often than not little stuff.
Here's the changelog: http://changelog.bbqdroid.org/#ville/cm10/next
When downloading, be sure to use the NIGHTLIES and not EXPERIMENTAL (if you are looking for stability).
I also recommend using Fusion Kernel with this rom. Works wonders.
Here's the link to the kernel: http://forum.xda-developers.com/showthread.php?t=1837630
If I helped, hit thanks
Click to expand...
Click to collapse
I agree with the above post. There is no reason not to use CM10 on the One S. I rocked it for a long time and it really is a pleasure to use. My only problem with CM10 is the camera doesn't perform as well as the stock camera. I tend to take a lot of pics and thus have gone back to a Sense-based ROM and now am just waiting for the moment HTC releases their Jelly Bean Sense update.
tgtoys said:
CM10 is producing official nightlies. I have been using it as my daily driver since the first day they started nightlies, and have very few (if any) issues. The occasional hiccup here and there, but nothing that stops me from using it as a daily driver. And I am on my phone constantly, mainly for work.
Here's the link to the download for official CM10: http://get.cm/?device=ville
Remember, because it's nightlies there is an updated version everyday. Sometimes big changes, more often than not little stuff.
Here's the changelog: http://changelog.bbqdroid.org/#ville/cm10/next
When downloading, be sure to use the NIGHTLIES and not EXPERIMENTAL (if you are looking for stability).
I also recommend using Fusion Kernel with this rom. Works wonders.
Here's the link to the kernel: http://forum.xda-developers.com/showthread.php?t=1837630
If I helped, hit thanks
Click to expand...
Click to collapse
so how long is it suppose to take to get past the cyanogen splash screen? because its taking a while. the screen image has a blue circle with electric current rotating inside with ahoneycomb background, with blue rectangles circling the inner circle and cyanogenmod typed in mid.
Logsdonj88 said:
so how long is it suppose to take to get past the cyanogen splash screen? because its taking a while. the screen image has a blue circle with electric current rotating inside with ahoneycomb background, with blue rectangles circling the inner circle and cyanogenmod typed in mid.
Click to expand...
Click to collapse
1st boot will take a couple minutes. It boots up quickly every time after. Are you using TWRP or CWM recovery?
tgtoys said:
1st boot will take a couple minutes. It boots up quickly every time after. Are you using TWRP or CWM recovery?
Click to expand...
Click to collapse
thinks its been stuck like this for 5 to 10 min. im using CWM recover.
i followed this guide if it helps http://forum.xda-developers.com/showthread.php?t=1583427
and used this link for the recovery file and downloaded the touch file http://www.clockworkmod.com/rommanager
Logsdonj88 said:
thinks its been stuck like this for 5 to 10 min. im using CWM recover.
i followed this guide if it helps http://forum.xda-developers.com/showthread.php?t=1583427
and used this link for the recovery file and downloaded the touch file http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
NVM i got it to work. i just went into recovery, wiped everything and re flashed cm10 again and it worked
ty guys for all the help i click thanks for all ya
Glad to hear you got it going. Enjoy
Oh,.and there is a new OTA feature on cm10, so you can update it pretty easily. It's under settings> about phone> cm updates.
Sent from my HTC One S using xda app-developers app
tgtoys said:
Glad to hear you got it going. Enjoy
Oh,.and there is a new OTA feature on cm10, so you can update it pretty easily. It's under settings> about phone> cm updates.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
ok so im still having one issue. the camera isnt working at all. is there a fix for this, or anyone else having the same issue?
Did you download the newest version? At the top of the list?
Sent from my HTC One S using xda app-developers app
tgtoys said:
Did you download the newest version? At the top of the list?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
no that one said experimental. i got the one below it that says nightly
Hmm my camera works fine..try wiping and reflashing.
Don't flash the fusion kernel, just the Rom.
Sent from my HTC One S using xda app-developers app
Related
Important!
It is strongly recommended that you flash clockwork recovery via NVFlash. If for some reason this or a future nightly build causes your phone to not boot up, you will not be able to boot into recovery unless you have it flashed via NVFlash.
NVFlash for Linux
NVFlash for Windows
To clear up some confusion, if you flashed your recovery via ROM Manager, you didn't actually flash a recovery. It is what we call a fakeflash, you should still probably flash with NVFlash.
Instructions
Download from http://download.cyanogenmod.com/?device=p999 and flash like you would any other ROM (via recovery or ROM Manager).
Be sure to backup before flashing, and of course a wipe is necessary when coming from stock.
Gapps are available from the usual places, however do not download the version that says it is for Tegra, even though this is a tegra device, as it will not flash.
Mod Edit:
Mikey1022 said:
Google Addon: http://goo-inside.me/google-apps/
Check the lastest package available on top
Click to expand...
Click to collapse
ChrisSoyars Edit:
After skimming some of the posts in this thread, here are some things that you can expect.
What to expect
- Everything working including Wifi, GPS, Audio, Camera, Front Facing Camera
- Screen off animation is not enabled, therefore it isn't broken.
- Occasional audio problems (as far as I know they have not been fixed). If audio does not play just reboot.
- Automagical brightness weridness, this is controlled by the kernel and not userspace, even having it working is very hacky.
Any reference to the first thread you need too look up, it's linked here:
http://forum.xda-developers.com/showthread.php?t=1058131
Changelog:
http://cm-nightlies.appspot.com/?device=p999
Thanks!!! Flashing
Is the server still down? The latest I see is 2011-5-25.
gamefreakgcb said:
Is the server still down? The latest I see is 2011-5-25.
Click to expand...
Click to collapse
I don't know whether it is still down or not, but yeah, that's still the latest build
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
brian6685 said:
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
Click to expand...
Click to collapse
Not on cm7 but Faux has made good progress with the help of debauchedsloth
So does this mean nightlies will resume soon?
edit, nvm oops
G2x with faux AOSP and faux orange kernel. [email protected] 5107 quadrant.
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
WHy a new thread? what is new?
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
How is your compile different from the gigglebread one from this morning?
jawknee530 said:
How is your compile different from the gigglebread one from this morning?
Click to expand...
Click to collapse
I dot think there's any really maybe one or two commits that got merged throughout the day. I just like compiling my own builds
Sent from my LG-P999 using XDA App
I see this thread kinda senseless as there isn't a newer nightly that was available before using the old thread. Although 2 pages seems more manageable then 300+ (which will happen eventually to this thread.)
Being a website developer I know these threads add up pretty quickly (hurray xda!)
I haven't flashed an actual CM rom in almost a week since the server crash. Hopefully the new thread is a sign that the server was repaired and new nightlies are on the way. Using the latest KANGS to get my fix, I know there is lots of progress. Running the latest KANG from today I think the rom is almost ready for a stable release after a few bugs get worked out.
I think the work you guys are doing is fantastic and much appriciated, although it may seem all we do is ***** half the time. Android wouldn't be the same without all of the developers leading the way. Big props. Hope all is well and I plan to continue to follow your work.
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
Just installed, cheers!
And thanks CM, I'm coming from #34 and just five minutes in its obvious there's been quite a bit of work done. Status Bar brightness slider is sweet.
i see a build 36 but it won't let me download? says its not found...
shniggies said:
i see a build 36 but it won't let me download? says its not found...
Click to expand...
Click to collapse
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
reisaru said:
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
Click to expand...
Click to collapse
ho ho... i must have checked riiiiiiight when it was uploading... because its downloading now
How did you find build 36 when 35 isn't out yet?
Sent from my LG-P999 using XDA App
UPDATE: After a few additional tweaks to the framework, this rom appears to be working for both green and red lens defy users. I've personally used it as my daily driver for several days this week, and found it to be stable and very usable. The one thing that does not work for me is the GPS, and quite honestly, I haven't had time to look in to it.
Here is a complete, working port of PARANOID ANDROID 1.97a for Defy. It is based on Galaxy S2 PARANOID 1.97 and Epsylon's CM10 1208. This is NOT a simple port using the port tool and includes the Framework changes necessary for the hardware.
I take no responsibility for any consequences from your decision to try this rom, and being based on alpha releases, I'm sure there are other problems, but I've personally used this rom for a prolonged period of time and the only problem I've had was with the GPS not locking.
Few things to note:
1. No offense to anyone, but this thread is not for complete noobs. While I will try to help when I can, I cannot promise any level of support. If you don't know how to flash via CWM, this is not for you.
2. This rom is based on the Froyo kernel and has been confirmed to work on MB525 with green as well as red lens. This is no guarantee that it will work on YOUR phone.
3. I intentionally used 1.97 as that version was very stable on my Galaxy Nexus - much moreso than 1.98 or 1.99
4. I've cleared the PARANOID defaults that most of the other PA roms come with. You can manually change the individual app settings under Paranoid Settings, or via the \system\etc\paranoid\properties.conf file which stores a record for every app including DPI and Layout.
5. After installing this rom, I "supercharged" it using a v6supercharger script (link below) and it did seem to help make the rom smoother and more responsive.
Special thanks to Epsylon3 and Quarx for their work on CM10 for the Defy, and Molesarecoming and D4rKn3sSyS for their work on PARANOID.
Thanks to brajesh.sharma87 for pointing out the bootloop "gottcha" of simply recompiling the framework (for specifics google "framework recompile bootloop" and read the first thread that comes up).
I strongly encourage any/all of you to contribute (make donations) to these developers.
DOWNLOAD ROM (double check MD5 before flashing - 96D409B4692319D9DA63FAA9CE1516A6)
Download latest gapps from here.
Here is the v6 supercharger script that I've been using and is confirmed to work with this rom.​
Make sure you're on Froyo kernel. Boot in to CWM recovery. Factory reset, wipe data/cache/dalvik. Install rom, followed by gapps. Wipe data/cache/dalvik again. Reboot (should take about 2-5 minutes). Install and configure the v6 script. Enjoy!
Looks pretty neat man! I might give it a shot soon. Any known bugs for now?
This is only PA rom which I manage to get work on my red lens defy without bootloop..
Cheer mate..:good:
now testing..
hm md5 matches, flashed it several times but it cant pass bootanimation :/
(edit: green lense defy)
here tooo stuck at endless bootanim...
o-liver said:
hm md5 matches, flashed it several times but it cant pass bootanimation :/
(edit: green lense defy)
Click to expand...
Click to collapse
meilbox said:
here tooo stuck at endless bootanim...
Click to expand...
Click to collapse
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
dew.man said:
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
Click to expand...
Click to collapse
bro if kernel was wrong they would have stuck at Moto logo not bootanim...
same with my builds too and the reason y i did not update my thread...
I made paranoid too but never boot... libandroid.runtime has errors as per logs...
and m in no mod to fix it for now...
Sent from my MB526 using xda premium
dew.man said:
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
Click to expand...
Click to collapse
did everything what i could, and my led does not flash in red...
nogoodusername said:
bro if kernel was wrong they would have stuck at Moto logo not bootanim...
Click to expand...
Click to collapse
good point.
nogoodusername said:
same with my builds too and the reason y i did not update my thread...
I made paranoid too but never boot... libandroid.runtime has errors as per logs...
and m in no mod to fix it for now...
Click to expand...
Click to collapse
Sorry, didn't even see your thread. Quite honestly, I've only been playing with PA for the last couple of weeks and have posted in rajesh.sharma87 thread as well as the rom porter thread, but nobody over there seems to want to read.
Have you looked at the logs from the devices that loop? Send me one if you have an example. I've tried lots of different combinations in conjunction with the framework-res mods before I got this to boot, but have not had any problems with this version. Interesting...
dew.man said:
good point.
Sorry, didn't even see your thread. Quite honestly, I've only been playing with PA for the last couple of weeks and have posted in rajesh.sharma87 thread as well as the rom porter thread, but nobody over there seems to want to read.
Have you looked at the logs from the devices that loop? Send me one if you have an example. I've tried lots of different combinations in conjunction with the framework-res mods before I got this to boot, but have not had any problems with this version. Interesting...
Click to expand...
Click to collapse
well paranoid jb(gb kernel) no boot for me at all...
havent tried urs m on gb kernel...
i dont have logs m on cm10
i m thinking of setting up git for paranoid... but my internet...:thumbdown:
Sent from my MB526 using xda premium
nogoodusername said:
well paranoid jb(gb kernel) no boot for me at all...
havent tried urs m on gb kernel...
i dont have logs m on cm10
i m thinking of setting up git for paranoid... but my internet...:thumbdown:
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL6 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
dew.man said:
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL7 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
Click to expand...
Click to collapse
How can you be on BL7 and still be able to switch to Froyo kernel?
niksy+ said:
How can you be on BL7 and still be able to switch to Froyo kernel?
Click to expand...
Click to collapse
My bad - it's BL6.
And for those that don't know, there was a leaked Froyo SBF with BL7 (see here).
dew.man said:
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL6 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
Click to expand...
Click to collapse
no the kernel has difference...
gb kernel has many missing libs!
Sent from my MB526 using xda premium
Hi dew.man, if u want to continue this, I will close my thread as u know there's no need of having multiple threads for the same work. The intention of the guide and the tool was to let everyone port and use and not polluting the developement thread by posting so many threads. I hope u get my point. If u really wish to take this up I am there with u and will provide u as much help as I can but at the same time we need to respect xda.
Opinion of other users are also welcome so that we can keep the developement thread clean. I've already closed 2 of my threads for the same reason. LewaOS and AOKP JB.
Sent from my MB525 using xda app-developers app
cant acquire logcat, its waiting for the device :/
o-liver said:
cant acquire logcat, its waiting for the device :/
Click to expand...
Click to collapse
dude goto bootmenu-boot-adb enable
press 2nd-init
and logcat...
Sent from my MB526 using xda premium
brajesh.sharma87 said:
Hi dew.man, if u want to continue this, I will close my thread as u know there's no need of having multiple threads for the same work. The intention of the guide and the tool was to let everyone port and use and not polluting the developement thread by posting so many threads. I hope u get my point. If u really wish to take this up I am there with u and will provide u as much help as I can but at the same time we need to respect xda.
Opinion of other users are also welcome so that we can keep the developement thread clean. I've already closed 2 of my threads for the same reason. LewaOS and AOKP JB.
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
First and foremost, thanks for all your help
Perhaps I was not clear enough, but I do not have the free time to take on any kind of support role. Please understand that my sole intention of this thread, was to provide/share a more recent version of PA/CM10 that I have been unable to obtain from anybody else. No offense intended, but I did ask you on several occasions to post a more recent version than the 1.95 you have in your (still existent) thread, and the only response I received was that you didn't have the bandwidth.
I also tried to work through/with kadevil's thread, but he pretty much ignored all the feedback he was getting about the tool not working for PA and JB.
Again, I was looking for a more recent version of PA (1.97+) with a more recent CM10 (8/06+) and was unable to find a working version. I built one that works for me, and wanted to share with anybody else that may be in a similar position...
Well guys i feel that the thread should be merged to brajesh's thread... since his thread has more organized 1st post...
no offence to op but thats wat i felt when i saw it...
peace
-hackergnome
Sent from my MB526 using xda premium
nogoodusername said:
Well guys i feel that the thread should be merged to brajesh's thread... since his thread has more organized 1st post...
no offence to op but thats wat i felt when i saw it...
peace
-hackergnome
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I'm perfectly fine with that as long as the op/title gets updated with the new version number
I'm getting frustrated with the daily random reboots of my G2x running stock gingerbread. Does CM 7.2 resolve this? I've been holding off waiting for the official ICS to release so I can install CM10 but I'm getting impatient... Also, do I have to reinstall all my apps, and is my data erased?
Thanks!
I don't think random reboots will ever be solved 100% for this phone. However comparing stock 7.2CM vs other Roms I've used for the G2X, it has been the most reliable and stable for me. The phone still crashes or reboots once every 2-3 days for me usually, when I'm running cpu/gpu intensive apps but almost never when its idle.
helloha1 said:
Also, do I have to reinstall all my apps, and is my data erased?
Thanks!
Click to expand...
Click to collapse
Invest in Titanium Backup and the Pro Key. I can't even put into words how worth it it is
Sent from my LG-P999 using xda premium
Im on cm 7.2 and have been for quite some time and since i flashed trinity kernel i have yet to experience one reboot.
Sent from my LG-P999 using xda app-developers app
Did you try it?
TMOfo said:
Did you try it?
Click to expand...
Click to collapse
No, I haven't yet. I think that i will sometime this weekend. Are there any good guides that I can follow? The one that is stickied says that it is outdated. I am running the latest baseband and software.
Just installed cm 7.2 with faux kernel 52... we'll see how this goes :laugh:
Hello, yesterday I was on my phone when it suddenly just seemed to shut off. I have cm10, and want to get rid of it and go back to stock. can i go back to the stock ics rom instead of gingerbread, and be able to do it on cm10 at the time? i can restore to the time i had my phone just rooted and stock ics. i just dont want to go through the trouble of going back to gingerbread stock rom and then updating to ics stock rom through kies. thanks in advance.
side question: is it normal for my phone to randomly shut off on cm10? from what i hear, its the screen of death. it happened to me 2 days after i flashed cm10 and then happened yesterday. (i flashed cm10 last month). if it occurs this often im going back to stock. im fine with the t mobile apps as long as no random reboots occur.
Just restore a backup it will work fine
Sent from my SGH-T769 using Tapatalk 4
so stock ics rom rooted will have no problems right? no random shut-offs? i want to stay out of this risky business.
exo114 said:
so stock ics rom rooted will have no problems right? no random shut-offs? i want to stay out of this risky business.
Click to expand...
Click to collapse
Have you tried the latest cm10 nightly ? The screen of death has not been present in ages.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
flyers00 said:
Have you tried the latest cm10 nightly ? The screen of death has not been present in ages.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
Sorry to hear but the nightlies are very stable and with use of one of the custom kernels (lz or blue lightning) the phone is stable. If you decide to go back to stock ROM good luck with everything
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
exo114 said:
Hello, yesterday I was on my phone when it suddenly just seemed to shut off. I have cm10, and want to get rid of it and go back to stock. can i go back to the stock ics rom instead of gingerbread, and be able to do it on cm10 at the time? i can restore to the time i had my phone just rooted and stock ics. i just dont want to go through the trouble of going back to gingerbread stock rom and then updating to ics stock rom through kies. thanks in advance.
side question: is it normal for my phone to randomly shut off on cm10? from what i hear, its the screen of death. it happened to me 2 days after i flashed cm10 and then happened yesterday. (i flashed cm10 last month). if it occurs this often im going back to stock. im fine with the t mobile apps as long as no random reboots occur.
Click to expand...
Click to collapse
I too have been experiencing what appears to be the SOD. The bottom "soft buttons" light up and the phone is dead. I have to perform a forced reboot to get it working. I am running CM 10-20130804 but it was happening on nightly builds before this version as well. It happens every few days for me. I keep hoping the next build will make it go away but it always comes back. I even posted the issue in the CM 10 thread but no one had any ideas other than a complete wipe and reinstall and i would rather not do that for CM10. I am waiting for the 10.2.....
mine shut off less frequently than yours. my question is: can i download stock ics rom from sammobile and use that through odin? i dont want to use stock gingerbread rom and then update through kies.
exo114 said:
mine shut off less frequently than yours. my question is: can i download stock ics rom from sammobile and use that through odin? i dont want to use stock gingerbread rom and then update through kies.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1591601
The last post addresses your question...
Sent from atop a BeanStalk
exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
Nightlies are very stable. The listed "stable" has many issues and would pose more of a threat than the nightlies. Try them out sometime . If something happens (which I highly doubt something will) we will be here to help and guide you
xWolf13 said:
Nightlies are very stable. The listed "stable" has many issues and would pose more of a threat than the nightlies. Try them out sometime . If something happens (which I highly doubt something will) we will be here to help and guide you
Click to expand...
Click to collapse
I said the same thing as you last night. With the nightlies and one of the custom kernels ,its a great combo
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
flyers00 said:
I said the same thing as you last night. With the nightlies and one of the custom kernels ,its a great combo
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I agree too. The stable is from 11/13/12, almost a year old, lulz. The nightlies are super stable and very customizable.
Romman0 said:
I agree too. The stable is from 11/13/12, almost a year old, lulz. The nightlies are super stable and very customizable.
Click to expand...
Click to collapse
Truly amazing its almost a year. The cm10.2 ROM and variations are pretty stable for alpha builds. Once the camera is fixed we should be good to go.
I remember being the guinea pig testing a fully functioning rooted ROM stock and cm7. Come a long way lol
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
in the end i just went back to stock ics rom. no need to worry about random shut-offs (used to happen on stock rom rooted, with "shell has been granted superuser permissions"). can i delete the clockworkmod folder and root stuff? i take it i cant go into cwm recovery without root.
bump. final question is what do i need to delete to leave no traces of being rooted before? is it safe to delete the clockworkmod folder in my phone files?
exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
boulos said:
I too have been experiencing what appears to be the SOD. The bottom "soft buttons" light up and the phone is dead. I have to perform a forced reboot to get it working. I am running CM 10-20130804 but it was happening on nightly builds before this version as well. It happens every few days for me. I keep hoping the next build will make it go away but it always comes back. I even posted the issue in the CM 10 thread but no one had any ideas other than a complete wipe and reinstall and i would rather not do that for CM10. I am waiting for the 10.2.....
Click to expand...
Click to collapse
The quote-unquote "Stable" build was not stable at all. It was captured before it was supposed to. Something like 2 or 3 nightly builds after that they incorporated the SOD fix into the kernel.
The latest nightly for CM10 is 100% stable as far as SOD, reboots, crashes, etc. I didn't ever have any problems with it up until I flashed beanstalk. I encourage you to give the latest nightly a chance before you go back to 4.0.4, but it's ultimately your choice
Agreed with above
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
mefistofel666 said:
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
Click to expand...
Click to collapse
nope those 3 build threads are it
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
SSPENCER10 is working very well for me. Everything he is putting out is stable and appears to be having fewer issues than KitKang. It is even working just as well with ART as it was with Dalvik. The 11-23 build also has the new CM11 boot animation.
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
You realize they are all based on exactly the same code right?
And you realize that if one makes 'progress' they all make 'progress' because they use the same code right?
[ROM][4.3.1][Official][OSE Rom][d2vzw]
I'm using this one and so far so good.
It has nightlies that have 4.4
I'd recommend KitKang. It's been extremely stable and has really good battery life. ART works very well.
Sent from my SCH-I535 using Tapatalk
KitKang!!
Second that!!
Sent from my SCH-I535 using xda app-developers app
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
Summary: I don't think KitKang is recognizing my SIM card, and is causing "Phone" to crash every second or two.
Hey guys, I tried flashing the latest KitKang ROM last night, but ran into a big issue. I wiped system, cache, dalvik cache, etc. I then reflashed the MF1 firmware (it was already flashed, but for some reason I always feel better re-flashing it every time.) Then I flashed the latest KitKang D2VZW nightly linked above, and flashed the GApps mentioned in that thread too. However, upon rebooting, every second or so it would say "phone has forced closed" (or something along those lines. Also, there was no signal. I got through the setup process after a VERY long time of pressing "okay" to that error and setting up my CM and Google accounts with one key in between each error. I thought I would be able to go into Mobile Networks and change the settings, which fixed certain early issues with CM10.1 or 10.2, but to no avail. I then tried reflashing (after wiping clean) CM10.2 again to get certain files for the phone to work, then flashing CM11 over that, and it seemed to work up until it freezes after getting to the home screen. Any thoughts on what the issue may be and/or how to fix it?
Thanks!
Sent from my SCH-I535 using xda app-developers app