Long time lurker first time poster... so don't beat me up too bad.
I'm looking at jumping into the CM7 world and am looking for some input.
I've used multiple versions of Skyraider up to 3.5 and loved them until they began getting a bit laggy (tried multiple kernels). I'm now using myn's warm 2.2 and ziggy's kernel with great success. Phone operates VERY smooth and all features work (not even sure why I want to try something new... guess I'm bored?).
Long story short, my phone is a daily driver and needs good battery life and all features to work (BT, camera, data, WiFi, etc...). I don;t mind flashing a few ROM's but it gets quite time consuing setting up the desktop screens, apps, calendars, etc...
I see that some builds break things, some fix things and it's hard to know which build does what. Many folks feel CM7 is the greatest thing since the Atari 2600; so here's my question:
What build are you using?
Does the phone scroll and transition smoothly?
All features working?
Getting FC's?
And yes... I have done quite a bit of reading on the CM7 nightly thread and others as well. People have a tendancy to post issues, not sucesses so it's difficult to find a good stable GB ROM.
Im on the latest release #37 I believe Using slayhers .37 kernal.
Love it. Altho, ever since I installed .37 kernal I've had my phone randomly reboot between 7:30 am - 9:00 am
I have yet to find out why... and it's only durring those hours too
I'm loving this ROM. Every time i go back to a sense, rom, i end up flashing cm6/7 back.
There are good things about cm6 and cm7... cm6 has a better camera app, probably more stable, but cm7 brings all the little things together, like multitouch keyboard + maps, it's snappy, the txting lag has been much improved. I think they are going to drop RC1 tonite..
I'm using build #33 with Chad's.37 kernel and everything's been running perfectly for the past few days. I don't think I've had a single FC or reboot. Battery life has also been very good, been using it pretty heavily all day and I'm down to 50%.
Just flashed 38, Have also used pretty much all the 20's 31 and 32. .37 Slayher Homebrewed #14
No reboots. I would say I could count the FCs on one hand easily and honestly don't blame the build I blame the app.
I used a number of roms before. Most of them from Rom manager. Now I am strictly a CM guy. Love these builds. I don't use Rom manager anymore either, just manually flash.
Personally, I'm someone who generally avoids experimental roms that still have incomplete functionality. Like you, my phone is a daily driver and I need to be able to rely on it. But CM7 was getting such rave reviews, I started to read up on it. It seemed that by the time I was hopping onto the bandwagon (nightly build 27 or so), everything was functional, there were just some things to be polished here and there.
It would be an understatement to say that I've been pleased.
To answer your questions specifically:
What build are you using? - Just flashed to #38, but have used a number of the builds
Does the phone scroll and transition smoothly? - Yes. For whatever its worth, I use LauncherPro Plus rather than ADW (which is what CM7 comes with)
All features working? - Yes. At least everything that I use.
Getting FC's? - Nothing that can't be traced back to another issue besides CM7
Don't get me wrong, I've had some tiny issues here and there, and some weird interactions, but nothing critical, and nothing that has stopped me from using this as my only rom.
I still keep old nandroids of the last two roms I used before CM7, but unless something drastic changes, they will just collect dust.
I've been using CM7 as a daily driver since like build 11, I haven't had any problems at all and its nice seeing new things added with each build
My dinc runs CM7 with the modified slayher .37 kernel. I runs super fast, but I haven't really noticed a significant increase in battery life. It used to crash, but since I set the wifi sleep policy to never, I have not had any problems.
build#38 ran awesome. no force closes and great battery life 20 hours or more. id say give it a try.
Just flashed RC1. Going great so far with only a few FC's that were solved with a simple reinstall.
Sent from my ADR6300 using XDA App
Did RC1, shaky, but amazing. Running 39 and it is better, has a lot of fixes that RC1 was plagued with. Like the rotary lock in the call screen.
I've been following CM7 development since Crackflashers. The rom has come a long way. Many people had problems with the first RC1 release because a mistake was made and those who did a clean wipe were locked out of the system. -Guess that should serve as a lesson to always nandroid first-
My advice is to continue flashing nightlies. As previously mentioned, the code will continue to improve and you will receive the latest fixes and features. Save yourself the trouble and clear cache and Dalvik before every flash. No need to wipe data.
Does anybody happen to know if there is a .37 version of the invisiblek kernel that includes the wifi sleep policy fix?
Its been working fine for me. The only problem I am having is that trackball wake doesn't function. I've made sure its selected int he CM settings, but I can press the trackball until kingdom come and it won't do anything. Looking at the dev. thread, I'm either the only one experiencing it, or the only one who cares.
SD card not mounting
flashed CM7 yesterday, really like how it runs. problem is my SD card won't load on the phone! I tried two different cards but no luck. recovery won't mount them either so I can't restore a nandroid backup. help!
also when I reboot most of the time, it'll show the htc incredible screen then go black and vibrate 5 times.
I'm running CM7 nightly #2 with the 2.6.37 incredikernel and it's great. Everything is very smooth and I can't seem to find anything that refuses to work. I had fc's when I first flashed the rom but fixing permissions in rom manager did the trick, since then I've had no problems.
I flashed CM7 as soon as they posted RC1 to ROM manager. I was skeptical at first and had a bunch of FC issues until I ran fix permissions (AFTER you install all apps). Haven't had issues since and my battery is lasting longer than ever, even without Juice Defender. Performs great. Can't wait until they get to adding more features like 6.1 had.
Sent from HTC Incredible [CyanogenMod 7 RC1]
Is it just me, or did Cyanogenmod lose some customization options from CM6.1 to CM7?
I dont see many editing options under CyanogenMod Settings and miss the ones from CM6.1
I'm on Build #41 and I can say a few things:
1) Battery life sucks on the Incredible no matter what. So just accept that. That being said, with Incredikernel .37 and CM7 Build 41, my battery life is "acceptable" compared to completely unacceptable with any other kernel or Sense Rom combination.
2) Random reboots. I don't know if it's just my phone, but even after trying three different .37 kernels, fixing permissions and re-flashing, my phone will go through "reboot anxiety attacks" where it reboots once every 10-12 minutes and then it will be fine for a whole day. It's not at specific times either.
3) Honeybread Theme - Get it. That's all.
4) Turn off wifi sleep completely. It seemed to curb some battery issues I was having.
Thanks All...
I went ahead and took the plunge and I don't regret it
I had some issues with RC1 and had to go to nightly #38. Everything has been solid with the exception of 2 random reboots (in the last 3 days). Not sure why but this isn't a show stopper.
I'll likley wait a while before flashing another nightly build.
So far so good. Batter life is ok... I know the Inc isn't the best for battery life but I got a bit better with Myn's ROM.
My quadrant numbers have improved (I know... relatively meaningless) and the UI is quite smooth.
Thanks to the development team... You've done a great job !!!
Related
Is the general consensus that Sense roms are general more stable and complete than AOSP roms?
I have tried a few of both, and it seems that every AOSP rom is incomplete.
By incomplete I mean it always seems to:
Reboot for no reason
Not mount the phones internal storage, nor mount the internal storage when connect to the computer (thus assigning it a drive letter)
Random app forcecloses
Now I know you can have problems like this on Sense roms too.
I would like to stay on a AOSP rom, since the ones i have liked have great built in tweaking menus/apps.
Are there any AOSP that dont fall into the above criteria of reboot (especially when using wifi), mounting internal storage on and off the computer (i keep my mp3's and movies on there!), and minor forcecloses?
I have yet to find a single AOSP rom that works like it needs to. So far, for stability sake, stick with a sense rom.
I am in the same boat as you BTW, I have been testing each AOSP (havent been many) hoping, but so far I am still stuck with Sense- which I absolutely cannot stand.
I hear ya
Thanks for the reply. I look forward to an AOSP build too that fits all my needs. I am tired of sense also, and even when I get on a Sense rom, i load up LauncherPro immediately and pretty much dont use much of the sense stuff.
I really liked the Ruby and Shadowrom, but i had freezes, reboots, and not internel storage mounting of course. I tried different kernels, tweaking, wiping, praying, beer drinking, and even subjected myself to watching a chick flick with my Fiancée, and still no luck (at least with the roms).
I keep a sharp eye out on the Development forums daily, hoping to pounce on the next AOSP rom that does everything (tethering, storage mounting, wifi without reboots, to name a few) that roms like Skyraider and Virtuous (sorry if i didnt name someones), and still has that great AOSP rom ability to configure and tweak to my hearts end.
dccoh said:
Is the general consensus that Sense roms are general more stable and complete than AOSP roms?
I have tried a few of both, and it seems that every AOSP rom is incomplete.
By incomplete I mean it always seems to:
Reboot for no reason
Not mount the phones internal storage, nor mount the internal storage when connect to the computer (thus assigning it a drive letter)
Random app forcecloses
Now I know you can have problems like this on Sense roms too.
I would like to stay on a AOSP rom, since the ones i have liked have great built in tweaking menus/apps.
Are there any AOSP that dont fall into the above criteria of reboot (especially when using wifi), mounting internal storage on and off the computer (i keep my mp3's and movies on there!), and minor forcecloses?
Click to expand...
Click to collapse
From my experience CM6 has none of those issues
Internal memory mounts it just doesnt display it in settings
And when I connect it to my computer I get both internal and external storages on my computer so I can access them both
I haven't had a random reboot untill I flash a custom kernal or if I overclock the original so I suggest don't overclock
But I still have the stupid email fc at startup but that's it
Sent from my ADR6300 using XDA App
Which build?
Really? May I ask which build or nightly build you are using? And which kernel with CM was giving you fc's? Thanks alot for the info too.
dccoh said:
Really? May I ask which build or nightly build you are using? And which kernel with CM was giving you fc's? Thanks alot for the info too.
Click to expand...
Click to collapse
I've been using all the nightlies from the 19th on up in order
I use the standard kernel that comes with each build
Every one so far gives me the email fc
Sent from my ADR6300 using XDA App
I currently run CM 6.0.2 with King's aosp kernel.
Internal storage is available when plugged into PC, doesn't show up (as has been stated.)
Rarely used Wifi anyway because I've got an unlimited data package, and can do my high-speed downloading on my laptop. Haven't even tried to use it since I've flashed, actually.
Had one random reboot when I setCPU to 1190mhz, oops. I remember my battery being excessively hot, as well. Since I generally run it at 768mhz, that doesn't bother me.
But why underclock my Incredible? Well, if I plan on doing something processor intensive, I'll crank it back up. If I use it for standard web browsing, video playback, etc, can barely tell the difference, and I unplug at 7:30am at 100% and get home from work at 5:30 at 70% on stock battery.
And honestly, the first ROM I flashed was CM6 RC3, and I swore to myself I'd never use it again, because it wasn't Sense.
You'll find the AOSP you like, it'll just take a few flashes. Besides, the developers aren't very possessive of their awesome accomplishments, that's why we get to use them.
For stability, Sense always wins...
But performance, which i personally care more about, AOSP roms are much better.
I'm running CM6 6.0.2 w/ King's Kernel, and all has been good. Just the battery life isn't so great, and bluetooth is kinda gimped. Aside from that, everything works, and i get no more random reboots.
I just wanted to revisit this topic because I typed in AOSP vs. Sense in google, and this was a result. Cyanogen Mod 6.1 final is damn near bullet proof and with the right research/widgets/kernel/etc can stomp just about anything.
Cyanogenmod should deliver great battery life as well as performance. Either 6 or 7 would produce great results
I'm on CM7 now and it's running GREAT.... no FCs or anything
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.
Anyone else get a random black screen of death with CM7? To clarify, when you open an app, the screen will just black out except for the notification bar. Sometimes you have to force stop the app and re-launch it. This happened once and I couldn't even get into Settings | Applications to force stop it, as that was "BSOD" also. I had to reboot. There's no specific app that it happens with, either.
Also happens regardless of the kernel I'm using. HW0003.
It drove me nuts for the last time today and I rolled back to completely stock Sense 2.2 ROM. I already miss CM7
Is this something fixable? I really don't want to use Sense UI until they release the official Sense/2.3 update (I have the 100% brightness problem with the leaks). I can't imagine the CM brains would overlook a problem like this.
I would just recommend a complete wipe...wipe again..and again..and oh yeah, wipe dalvik a few times too. Then try to reflash CM7 and see what that does for you. And try using the stock kern for a while, then switch and see if the issue replicates.
My 2 Cents,
Tee Jay
teejaymarx said:
I would just recommend a complete wipe...wipe again..and again..and oh yeah, wipe dalvik a few times too. Then try to reflash CM7 and see what that does for you. And try using the stock kern for a while, then switch and see if the issue replicates.
My 2 Cents,
Tee Jay
Click to expand...
Click to collapse
Thanks, but "been there, done that"
I haven't seen the issue you speak of, which kernel? Which cm7?
NewZJ said:
I haven't seen the issue you speak of, which kernel? Which cm7?
Click to expand...
Click to collapse
CM7 Final (7.0). Kernel that it comes with. Happened when I was using Savaged-Zen kernels also.
EDIT: Used to happen with the nightly's and RC's, too.
Been running CM7 since before RC1 release and currently on CM7.0.2.1 with Timat kernel and never had a bsod
Try flashing a different aosp rom.. There are several that are actually off cyn7. I like kings gb myself couple of different builds there.. Did you try fixing permissions? download the rom from web again. And then reflash.. I had a similar problem on destroyer rom think I got a bad link or computer corrupted the download.
Kings GB Destroyed EVO
It could be a lot simpler; make sure your programs are compatible with Gingerbread
Despite having compatibility mode, I still get issues with certain apps.
Yes, this is happening to me, mostly with Messages and Maps. I am using Tiamat, CM7 final
Try this rom, it is based off CM7 but is WAY more stable
http://forum.xda-developers.com/showthread.php?t=1000676
for my phone anyway, cm7 is buggy and gives me bsod and random reboots. sucks because i am a die-hard CM fan
I used to get this issue alot when using an older build and savage zen. I know exactly what you're talking about. Flashing the #57 and switching to tiamat 3.3.8 fixed the blackscreens for me.
Sent from my PC36100
Rather bump my old thread than start a new one. These problems still happen using the latest "stable" build and the kernel that it comes with. I thought it was the launcher at first, but it happens with LP or ADW.
This is massively frustrating.
I've wiped and reflashed so many times I'm going to puke. I've even used Caulkin's wipe .zip script.
EDIT: Add these to the list of issues:
1. Sometimes when you are typing a URL or something into the browser address bar, the letters don't show up as you type
2. Sometimes when you hit the numbers button on the default keyboard, nothing happens, so you're "typing blind"
The Black Screen of Death happens to lots and lots of various programs, not just ones that "aren't compatible" -- like Gmail, messaging, Market, it's also prevented me from going to Settings | Applications to kill apps off, too...
Use this script and Godmode kernel. Its ridiculous how amazing this is
http://forum.xda-developers.com/showthread.php?t=1093687
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
I've got the same issues.
Chase
EVO 4G
CM7.0.0
When it was happening to me last night, I had to yank the battery to get into recovery from boot because **** wasn't working. I did a full wipe and restored my stock backup.
I'd say that I'll miss CM7, but I won't miss the massively frustrating problems. I'll patiently await tomorrow's update.
Soooo, I've spent almost all of brief 8 months of rooted joy bouncing around Sense-based ROMs. I jumped on CM7 after last playing with early releases of CM6. The issue: Awesome Drop doesn't work with CM 7. (I love this app for being able to drag and drop things from any computer to my phone sans cables.) At first I thought I'd corrupted something on my end, so I went back to Lou's Senseless Revolution (Sense-based) and Awesome worked without issue. I then wiped and flashed to CM 7.0.0...Awesome was DOA. I then tried wiping and flashing to CM 7.0.3...Awesome is still DOA. I even tried the latest nightly (83) to no avail. I love this app and I'm quite frustrated that it won't play nice with CM7. Two questions:
1) Due diligence: is anyone who is currently running CM7 able to use Awesome Drop?
2) Does anyone know what might be causing this issue?
I'd sincerely appreciate any input!
I just got done using it on CM 7.0.3, it worked perfectly. I'm not sure what could be causing the issue I have GoLauncher installed as my home and not ADW. Not too sure if that has any affect.
Thanks for the reply. I'll be honest...I'm not prone to profanity, but I'm getting close. I've restored my old Sense-based ROM four times today...Awesome Drop works fine. I then upgrade to CM from there. Any CM 7 build I choose...Awesome is subsequently DOA. When it worked for you, did you use it over WiFi or 3G? (I'm using 3G.) EVERY TIME, I get to the 'waiting for drop' point, drop a file in my browser window........and then nothing. My Inc remains at the 'waiting for drop' screen. Men more magnanimous than I would probably just move on....but I've become obsessed with making this work. I've tried 7.0.0, 7.0.3 and nightly 83 with the stock kernels. I've tried 7.0.0 and 7.0.3 with Chad's last few kernels. Nothing. For the life of me, I can't understand why the app won't cooperate with CM 7 when it works on my phone with a Sense ROM. I wipe everything before every flash, so I don't think there could be any remnants from the Sense side of things. Any ideas? Anyone else? Am I the only member of this special level of hell where one of your favorite apps won't run?
PS - In all cases, I've tried it ADW and with LPP.
Is it possibly just not working on gingerbread?
Edit: Didn't read, I'm sorry.
Sent from my ADR6300 using XDA App
I was using 3G, it wouldn't let me drop a whole folder though just files individually. Not sure what could be going wrong for you, honestly I was too impressed with the app. Drop box is much better.
Sent from my ADR6300 using XDA App
Okay, thanks for the efforts. I'm not sure what is tweaked on my end. None of my efforts have worked. Dropbox IS great (I use it, too). However, I use several computers; many of them are community machines. Thus, remaining logged in to Dropbox is less appealing/secure for me than quickly launching a browser with Awesome Drop and completing a file transfer. I guess my usage scenario is somewhat unique. Thanks again, though!
Hi all,
I'm a new Nexus user and I was just wondering what is currently the best ROM and Kernal people are using. I put Android Revolution HD on my Nexus a few days ago and it's running great. I keep hearing people talk about Cyanogen or the Franco kernal though.
Are the performance improvements that much better, or should I stick to Revolution? I don't require a lot of personalization in terms of how things look. I'm quite happy with the stock look of the phone. I just want all the "behind the scenes" improvements like better battery life and loading times. What's the best setup in your experiences?
Thanks!
I've played around with several of the roms and kernels, with mixed results. It seemed like some roms and kernels would get me crazy performance, but really crappy stability.
The setup I'm running now is a cleanly wiped install of GummyNex 0.8.1 found here, or more directly here OnDemand governor is giving me respectable battery life. When I'm running short, I'll switch to Conservative. I've been meaning to set something up in Tasker or Setting Profiles to do it for me.
And Google apps found here, also more directly here
The kernel I run is Trinity, found here
If you haven't done so already, I found awesome performance improvements by opening the egl,cfg file in /system/lib/egl/, and deleting the first line- usually "0 0 android". Then going back into the egl folder and deleting both the .bak file some editors create, and the "libGLES_android.so" file. This is an ICS tweak that alleges to eliminate CPU rendering. I know there's an option in developer tools to "force GPU rendering", but apparently that doesn't quite cut it.
Anyway, that's my 2 cents, and it's blazing fast and stable. Averaging around 3800 in Quadrant.
Thanks! Revolution HD already does GPU rendering so I'm not to worried about that. I guess I'll just stick with that since it's basically stock with a few performance tweaks. I'm not big on instability :/.
The Trinity kernel looks interesting though... Is the overclock safe though? And does it drain a lot of extra battery?
Luuthian said:
Thanks! Revolution HD already does GPU rendering so I'm not to worried about that. I guess I'll just stick with that since it's basically stock with a few performance tweaks. I'm not big on instability :/.
The Trinity kernel looks interesting though... Is the overclock safe though? And does it drain a lot of extra battery?
Click to expand...
Click to collapse
Revolution HD is based on 4.0.2 so many kernels will not work because they are based on 4.0.3 and 4.0.4. I highly recommend you use a rom that is based on 4.0.3 AOSP (Such as GummyNex or AOKP). 4.0.3 has better stability/battery/performance tweaks anyway. If you want a better selection of Trinity's kernels go here. TNP1344-ANY-384-aelp (dated Feb 27th) is really nice. If it gives you bootloops up the voltages by 50 or 100.
aokp.27 + glados.v.1.18 OR leankernel.v.2.4.0 (both are stable as a rock)
Alright, I'll try Open Kang I guess. I'm so new to this... Sorry for all the questions :/.
It seems like a hassle to reinstall all your apps often so that you can switch to a new ROM . Does this need to be done every time the device changes its firmware version?
Luuthian said:
Alright, I'll try Open Kang I guess. I'm so new to this... Sorry for all the questions :/.
It seems like a hassle to reinstall all your apps often so that you can switch to a new ROM . Does this need to be done every time the device changes its firmware version?
Click to expand...
Click to collapse
Well... you can always backup your apps with Titanium Backup, and save all your preferences (such as Nova Launcher, Minimalistic Text, etc.) and then reload that. And usually if you stick one one Rom and then an update comes from that rom, you don't have to wipe data (just cache & dalvik cache). But if you're switching Roms, then yes, you have to reinstall all your apps.
Luuthian said:
Alright, I'll try Open Kang I guess. I'm so new to this... Sorry for all the questions :/.
It seems like a hassle to reinstall all your apps often so that you can switch to a new ROM . Does this need to be done every time the device changes its firmware version?
Click to expand...
Click to collapse
with titanium pro its a matter of minutes, saves your app-data also, so you don't loose your highscores. but as was mentioned before, updates go through without factory-reset most of the time once you're settled.
btw, aokp is perfectly stable.
I'm running gummy with the latest lean kernel and love it. Battery life is great and performance is top notch. Big fan of team gummy. I get a solid full days use regularly. usually around 20% when I plug it in after 16 hours of use and I use it fairly regularly, wifi, 4g, txt, web, etc.
Sent from my Galaxy Nexus using Tapatalk