Related
Hello everyone,
While i'm sure this must be a hard decision for most people, I am currently trying to decide which Rom to go with myself. I see there are about 5 different roms based on Froyo (2.2) and while i've tried reading pages and pages from each Rom post i've found out that what work in one may not work in the other.
So with that said how do you pick a rom that offers everything (if there's even one out yet?)
If i'm not mistaken Fresh has 4G issues and Tether doesnt work (not that tether is an issue but it'll be nice to have)
OMJ has music steaming issues, has working tether but camera is set to 3MP
I also see that most roms remove the Sprint apps (which i'm cool with except for the Navigator).. is there a way to get the Navigator back?
Decisions, Decisions.... Decisions....
The WiFi Tether issue isn't an issue with the rom. It's still a work in progress for full 2.2 support and it's possible to get it running if you flash a different kernel. Unfortunately that kernel has the adverse side effect of making the camera 3MP. Keep checking the wifi tether google code page to see when they release a fully working version for 2.2.
fresh has never had 4g issues.
4g confirmed working on all froyo betas and releases.
I can only comment on fresh bc that's the one I've used. I have no issues with 4g and tethering works great with netarchys 3.7.6c kernel although the back camera drops to 3mp which I'm fine with..also, fresh takes out the Sprint and some HTC apps but leaves them in a folder on your SD card in case you want to install any like navigation.
I'm sure you can adjust any of the roms to your liking, just play with them
Sent from my PC36100 using XDA App
I like Fresh's rom for HTC Sense. I am currently still running the CM6 nightlies tho. No 4G in my area so not a big deal for me.
WillJV said:
Hello everyone,
While i'm sure this must be a hard decision for most people, I am currently trying to decide which Rom to go with myself. I see there are about 5 different roms based on Froyo (2.2) and while i've tried reading pages and pages from each Rom post i've found out that what work in one may not work in the other.
So with that said how do you pick a rom that offers everything (if there's even one out yet?)
If i'm not mistaken Fresh has 4G issues and Tether doesnt work (not that tether is an issue but it'll be nice to have)
OMJ has music steaming issues, has working tether but camera is set to 3MP
I also see that most roms remove the Sprint apps (which i'm cool with except for the Navigator).. is there a way to get the Navigator back?
Decisions, Decisions.... Decisions....
Click to expand...
Click to collapse
This thread really belongs in the Q&A, as it has nothing to do with development.
However...
My best advice would be read through the threads for the respective roms, then try them out. Trying them out will give you the best information as far as what that rom has and what it doesn't have. but keep in mind, these roms aren't really made for you, they are just provided so you can use them if you want. They are ultimately made for the developers, and have their personal preferences built in.
If you want the sprint apps, I would suggest flashing fresh at least once. Although I'm not sure if he does it anymore, he use to put all the removed apps into /sdcard/fresh-removed-apks and you could reinstall them from there, on any rom.
It's all about one's personal choice when it comes to custom roms. They are all made possible and available by the wonderful devs. so you can flash as many of the roms you like. Once you see one that works good for you then go with it, that's what it all comes down to.
Nibert, Thanks i'll keep checking the post you mentioned.
Fazzmanic, not that i know for a fact that FRESH has issues with 4G. The only reason i said that is because there are at least 2 post in the ROM's thread from users who reported 4G not working... that's all.
ervman1, Does Fresh have that kernel you mentioned or you have to install that kernel after flashing the rom with Fresh?
bdelbenes, I like the HTC Sense myself. I've tried Open Home and Launcher Pro and they're cool yet I guess i used Sense at the beginning of me getting the phone so i got used to it.
Dougie2187, sorry for posting it on the wrong section but thanks to the Moderator who moved it to the correct forum. I have yet to flash my rom so i'm still on the factory 2.1 rom (rooted)... I guess i will do like most of you do and try one by one (well at least a few) till i find one that i like. I just wanted to make one choice and go with that instead of flashing my phone everyday LOL
WillJV said:
Nibert, Thanks i'll keep checking the post you mentioned.
Fazzmanic, not that i know for a fact that FRESH has issues with 4G. The only reason i said that is because there are at least 2 post in the ROM's thread from users who reported 4G not working... that's all.
ervman1, Does Fresh have that kernel you mentioned or you have to install that kernel after flashing the rom with Fresh?
bdelbenes, I like the HTC Sense myself. I've tried Open Home and Launcher Pro and they're cool yet I guess i used Sense at the beginning of me getting the phone so i got used to it.
Dougie2187, sorry for posting it on the wrong section but thanks to the Moderator who moved it to the correct forum. I have yet to flash my rom so i'm still on the factory 2.1 rom (rooted)... I guess i will do like most of you do and try one by one (well at least a few) till i find one that i like. I just wanted to make one choice and go with that instead of flashing my phone everyday LOL
Click to expand...
Click to collapse
Nandroid backups help make this process a lot easier. Fresh was my rom of choice for a while, Bugless Beast is really good as well but isn't up to date. Damage Control is really good too. But I've been using Cyanogen because it's AOSP.
It all ends up being personal preference, but those are some I would try out. Basically, flash one, set it up 100% and back it up. Then use it for a day or so, and try another one. And continue this until you find one you like.
on fresh 0.53 and 1.01 i had a 4g reconnection issue that i couldn't seem to shake even after doing the posted fix. it all seems to be sorted out with 3.whatever. avalaunch is another rom i can confirm that all the relevent bits work on.
froyo roms in general have taken a giant step forward since the OTA. i'd recommend downloading titanium backup and getting yourself the donated version then just try out whatever looks interesting. titanium makes the process a lot less painful since you can restore all your apps with their data in a batch process.
Hi,
Im nog allowed to post this link in the development section, so im sorry if its wrong here. Can anyone tell me the differences between the CM7 rom and the oxygen rom? What are the pro's and con's of each rom? Tried a lot of google searches, but couldnt find it.
Patrick
still_the_same said:
Hi,
Im nog allowed to post this link in the development section, so im sorry if its wrong here. Can anyone tell me the differences between the CM7 rom and the oxygen rom? What are the pro's and con's of each rom? Tried a lot of google searches, but couldnt find it.
Patrick
Click to expand...
Click to collapse
Depends if you want a technical explanation or simple?
As simple as it gets.. Nothing!
They are both GREAT Rom's by GREAT developers. However, they are also BOTH in "pre-stable" release status. This doesnt mean they arent stable, actually they are both insanely stable. It just means neither is a "Final Product"
Both share most of the same basic features and neither really has a downside or drawbacks.. it's all personal preference. I LOVED Oxygen when I was running it, but for me, the new features/tweaks/bugfixes of the CM7 nightlies just drew me in
Both have their own HBOOT, both support A2SD (though Cm7 is a seperate flashable zip) and both have a pretty stable following as far as theme support..
It really just comes down to you.. read through the threads/changelogs and see if one draws your attention more than the other.. remember, once you are rooted, it only takes a minute or two to flash a new ROM.. if you dont like the one you choose, try the other.
I find that CM7 actually works. I can't get Oxygen to install at all. The download messes up so the md5 is a mismatch and as such, when installed it doesn't. Just returns a bad request. But as mikeandjaimie said, there are very little differences. To be honest, you can't get someone to tell you what is better or not. It is down to you. Your own preference. Try them both out for a little bit and see which you like.
I've tried both over the last week (tried GingerVillain too) and I prefer Oxygen out of the 2 you mentioned. it's very basic, but I really like it. only had a problem with the Launcher Pro calendar widget, but everything else works fine. On CM I had some bad battery drain, but other people like it.
I actually managed to get Oxygen to work today and I am testing it a bit. Obviously there are still going to be bugs around but it's pretty stable. Oxygen is minimal. It uses the default Android launcher whereas CM7 uses ADWLauncher. I can't really tell the difference between them both really. Like I said above it is down to preference. There are no real differences at all.
mikeandjaimie said:
Both share most of the same basic features and neither really has a downside or drawbacks.. it's all personal preference. I LOVED Oxygen when I was running it, but for me, the new features/tweaks/bugfixes of the CM7 nightlies just drew me in
Click to expand...
Click to collapse
What features do you prefer in CM7 as opposed to oxygen?
...just interested
Well I haven't used oxygen in a bit, but they hadn't added any of the CM specific tweaks and features yet.. mostly stuff like gestures, etc.
Sent from my HTC Desire using XDA App
CM patches are used for pretty much everything in Oxygen, so most features are alike. I like both, but prefer bleeding edge so CM nightlies FTW
Sent from a piece of ginger bread... Now with a little cyan tint
I have never used oxygen roms but its my first time to cyanogenmod 7 roms ever and I can say I am more then happy, I am have been using the first build nightly for well over a week now and its been absolutely fine, the only thing that does not work is video recording which but everyone is pre-warned about that until the nexus one files get dropped in.
Just flashed to 24th Feb nightly and still no hiccups, not getting the battery drain issues like people are posting, but there is no noticeable decrease or increase for me compared to the previous O2 branded froyo build.
what about ginger villain?
Haven't used CM7, but if you want a fast and lightweight ROM with excellent battery life (see the battery saving mods) then you cannot go wrong with Oxygen
Moreover,tt looks like now that the nexus one OTA has been extracted we will see a stable version of Oxygen very soon, so the problems with the Camcorder on RC7 (the dev didn't want any hacks in the ROM since he wanted it to be as stable as possible) will be ironed out!
Do both these have Bluetooth gamepad support
Sent from my HTC Desire using XDA App
would love to see some posts with info about what made someone to move from one mod to another
(just a bump)
I loved Oxygen, loved it. Very fast and minimal allowing me to add to it the way I see fit, the way it should be really. Problem was I was one of the few that experienced bootloops constantly. On average once a day. Sometimes it would go into a boot loop at idle, and I wouldn't notice for over an hour, and by the time I got it back on, the screen being on and displaying the boot animation had drained some serious battery.
So I tried Ginger Villian, I had the same issue with bootloops, so I tried redux. I was quite happy with it, except it didn't work as a phone. It dropped calls every few minutes to multiple numbers, and it refused to send or recieve mms (Yes I checked the APNs). That's when I decided to try CM7, and found that it just works for me where the others didn't. Yes it's a little more heavily featured than I would like, yes it can be a bit laggy and slow every now and then, but it's the stability and reliability that keeps me here for the moment.
I wasn't S-Off when running Oxygen though, so I will delete the ext partition on my SD card and reinstall Oxygen with the oxygen hboot to see if maybe it makes a difference. Something must, there's a lot of people out there claiming to have never had a boot loop, though I would miss the T-Mobile theme enginge that CM7 ships with.
Probably more than you wanted to hear, but that's basically what made me jump from Oxygen to CM.
i really love a stable rom. that's why i prefer cyanogen and used cm6 for a long time. but i also want the latest android version. that's why i use oxygen at the moment until cm7 becomes "FINAL".
the most important thing about cm is that they do not modify the rom all the time. they create a rom, they test it as beta/rc (ONLY for bugfixing - no new (maybe buggy) features all the time) and one day you get a final rom which is no longer changed and STABLE.
I used CM6.1 for quite some time, I love AOSP ROMs, Ultralinx persuaded me to try Oxygen RC2 and I changed HBOOT to go with it. I love the minimalist, hack free aspect of the ROM. And because Oxygen 2.0.1 is so stable and lightweight, and that I can't be bothered to change HBOOT again I think I am going to stick with Oxygen until I am due to upgrade phones.
I used Oxygen since I first rooted, it was a froyo rom, but I used it all the way up to the most recent version. Today I tried cyanogenmod, just to see what differences (if any) there were.
So far, I've noticed the for a2sd+ on cm, you need to flash an additional script. But the main benefit of cm is that I can, for the first time since rooting, send mms again. I could receive them on oxygen no problem, but couldn't for the life send them. Definite benefit for me there.
hidinginthebush said:
I used Oxygen since I first rooted, it was a froyo rom, but I used it all the way up to the most recent version. Today I tried cyanogenmod, just to see what differences (if any) there were.
So far, I've noticed the for a2sd+ on cm, you need to flash an additional script. But the main benefit of cm is that I can, for the first time since rooting, send mms again. I could receive them on oxygen no problem, but couldn't for the life send them. Definite benefit for me there.
Click to expand...
Click to collapse
Sorry of topic now but:
What do you mean by flashing a script for the app2sd? I only have a app called S2E, and an ext3 partition. And that app does the job, just by restarting my phone the apps moves to the ext3. But I do realize that my internalmemory goes down when I have a lot of apps. Like now i got 96 mb free. Am I doin it right?
Thanks
xziaz said:
Sorry of topic now but:
What do you mean by flashing a script for the app2sd? I only have a app called S2E, and an ext3 partition. And that app does the job, just by restarting my phone the apps moves to the ext3. But I do realize that my internalmemory goes down when I have a lot of apps. Like now i got 96 mb free. Am I doin it right?
Thanks
Click to expand...
Click to collapse
Less than a minute of searching:
http://forum.xda-developers.com/showpost.php?p=10675412&postcount=2
xziaz said:
Sorry of topic now but:
What do you mean by flashing a script for the app2sd? I only have a app called S2E, and an ext3 partition. And that app does the job, just by restarting my phone the apps moves to the ext3. But I do realize that my internalmemory goes down when I have a lot of apps. Like now i got 96 mb free. Am I doin it right?
Thanks
Click to expand...
Click to collapse
If you haven't moved your dalvik cache to SD then your internal memory will decrease. Dalvik takes up so much storage space.
CM7.0.2.1....... sucks battery and app. Problems after update.... ??
Crans said:
CM7.0.2.1....... sucks battery and app. Problems after update.... ??
Click to expand...
Click to collapse
naw... running smooth as ever for me. maybe something went wrong with your install
Have you tried a different kernel? Make sure your screen brightness isn't up all the way also, big battery killer.
CM7 nightly
I dont think this belongs in development. try Q/A they might be able to help you out.
I am also having issues mainly with you tube all the videos are jittery as hell and tried a different rom and issue was gone.
Sent from my ADR6300 using XDA App
The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
You could check the threads for CM7 and see if it its a "development issue"...searching works from time to time
CM7 nightly
Just don't know why 7.0.2 to 7.0.2.1 would be so drastic.... understand nightlys but not stable
Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Opening a new thread about a ROM rather than posting in that ROM's thread, running it in a non standard configuration, AND having an attitude when someone points out a Q doesn't belong in dev? Yeah, I see no problem at all. /sarcasm
You guys are getting sarcasm and straight forward confused thanks for any input that actually pertained to my question... to others.... think before you speak or ask ... done... Please close this thread ASAP
Crans said:
The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one
Click to expand...
Click to collapse
um, the only thing they fixed from .2 to .2.1 was the camera.
To many people here post issues that aren't from a clean wipe.
No issues, move along.
Thank you for your reply..... as stated before...done
Remove this Thread
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.
morrisdan said:
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.
Click to expand...
Click to collapse
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
masully1984 said:
Have you tried a different kernel?
Click to expand...
Click to collapse
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).
I love using CM7 ... bugs or not please save your ignorance.morrisdan
Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Just because someone posts something in Q&A doesn't mean they aren't rooted. Your attitude sucks man. My personal opinion would be to reflash and wipe I have been running the latest stable release for as long as its been out and been updating to the latest version asap and have had zero problems other than those cause by user error. Perhaps you did something. Gotta release 9/10 problems are user generated.
skyblaster said:
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).
Click to expand...
Click to collapse
Dude you should always try different kernals with roms. You must be new. It is stable I've had zero problems. As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.
cstrife999 said:
Dude you should always try different kernals with roms. You must be new.
Click to expand...
Click to collapse
Don't let my post count fool you. I've been around since the beginning with the G1. Final, Stable, these words suggest newbie usage. Final builds should come with a final kernel. Unless you're a dev, tester, or need something specific for a certain application then you shouldn't need to kernel hack.
cstrife999 said:
As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.
Click to expand...
Click to collapse
I understand how memory wipes work, so I don't believe the multiple wipe requirement. However, if it is an issue with ClockworkMod 3.x then I do apologize for any nay say here against CM. However, that doesn't really explain why 7.0.2 and 7.0.2.1 came out so soon after 7.0.0, and I wasn't the only one with video troubles in 7.0.0.
/deleted
10char
So strangely at 11:45pm last night my phone went absolutely nutty... Can't figure it out but all of my apps keep crashing. Gmail, Maps, etc.
I haven't updated CM7 since it came out months ago so I need a bit of help upgrading all of what needs to be done... I figure this is a good reason to bring things up to speed.
Ideally I'd like to get 7.1 on here. I also can't remember all of what I need to download to do this process. Not as brilliant as the rest of you!
Can anyone give me (or point me in the direction of) some step by step instructions of what I need to do? Real layman's terms...
Currently:
Android 2.3.3
Model number ADR6300
Kernel 2.6.37.6-incredikernel-gb-04192011+
CyanogenMod 7.0.0-Inc
Build Number GRI40
Help me get this puppy up and running!
Thanks all and Happy New Year!!!
Go to cyanogenmod.com and click on devices. Scroll down until you see the HTC Droid Incredible and click on it. Click on the wiki link. Everything you need to know will be there. Use the via clockworkmod recovery method.
Get 7.1 stable, the gapps for it, incredikernel ext4 and the adrenaline shot. That's should be good.
-My life is a shooting range, people never change-
I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then constant FC's and freezes). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to reinstall again.
Some folks have said that the problem never goes away after a fresh install... I don't know about that. My phone screwed up, I searched and found many others with the problem, tried a quick fix, then abandoned CM 7.x stable immediately.
iowabeakster said:
I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then is completely fubar'd). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to start over again.
Click to expand...
Click to collapse
Hmmm interesting. Out of all the roms I have tried for the droid Incredible, CM7 has by far been the most stable. Never had any trouble with it and I have, at times, used it for months before trying a different rom.
Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.
CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.
Thanks for this tidbit... I haven't had the issue, nor do i plan on getting it.. I'm pretty adamant about keeping a certain percentage of free space on all partitions, so hopefully everything runs smooth.
Thanks again for the heads up.
tiny4579 said:
CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
iowabeakster said:
Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.
Click to expand...
Click to collapse
Don't let this Guy talk you out of cm7. I've been running the same kang for almost a month. And I ran the stable from October 9th til December 19th. It was always my fallback. I've never had issues, and as big as the nightlies/stable threads are. Why would you let one sway you?
-My life is a shooting range, people never change-
Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.
Your sarcasm is too advanced, my friend... ;] lol
iowabeakster said:
Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Use Pons 7.2 kang. I've been since he started and all is well. I was running the nightlies before that and have never had any issues.
Ahhhhhhh
Sent from my HTC Incredible S
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Reserved
Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky
I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1
Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app
I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2
This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.
adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app
Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do
Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.