• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [BETA]Cyanogen!! Landed!!! :) Go get it![Updated 7/12/2011]

Kevmueller said:
...If I could ever figure out how to add a picture (not the small attachment) to my post I would put a couple up for you all to see. I am very happy with the video and picture quality.
Click to expand...

I use tinypic.com Just follow the steps to upload the pic then it gives you paste-able links for forum posting. :)
 
I am on SSX 2.0 now and I was wondering if I could just flash the nightly for CM7 or would I have to go back and start from scratch?
 
binary visions said:
People with battery problems, are you taking steps to find out what is actually draining the battery?

I mean, I see battery complaints left and right, but virtually nothing like, "I have battery problems... and this is what Battery manager shows/tells me."

I mean, damn, we have a really sweet battery manager. It shows % of battery drained by app, and has this stellar little chart that shows discharge rate, when the phone was awake, when Wifi was on, etc. Virtually every time I have a weird battery discharge - CM7 or not - I can go into the battery manager and immediately pinpoint the problem. A runaway app, or seeing that I lost signal and it correlated with a precipitous drop in the graph, or whatever.
Click to expand...

+1000

there are even more steps to take after this...

apps like Watchdog can alert you if apps are using a lot of CPU at a given time...and there are times (mostly back in the Froyo days) where i had particular apps that would be CONSTANTLY causing watchdog to fire off alerts...

apps like Android System Info can give you real time looks at how much CPU and memory an app or service is using and you can see if its hogging CPU...

Unfortunately one thing that Google dumped from Gingerbread is the "Battery History" menu...IMO this was one of the most useful tools for tracking down battery drainers...because instead of just "Android System" or "Android OS" it would give you specific process id's that are used there...then you could use an app like Android System Info to track down which one is running too much and try to figure out solutions...

binary visions said:
My old phone could only handle 1.1 GHz, no matter how I set the voltages (within reason, I didn't try cranking it up). Always got reboots if I went above 1.1.

My refurb overclocks like a madman. It was totally stable at 1.45 GHz, I was tempted to try higher but never experimented much.
Click to expand...

:mad: my phone is lik your old phone...i can get up to 1.175ghz...its somewhat stable...but if i play a lot of games it will eventually reboot...anything above that and the phone instantly locks up and becomes nearly unresponsive...

though i will say...a friend of mine has had a D2 since it was released...i finally was able to convince him to let me root it about a month ago...he cranked his D2 up to 1.4 and we played around with it..trying to find a sweet spot and on stock .596GB compared to his stock Froyo my phone at 1.15 (where i normally run) just plain outperformed his phone in every way...it was so much smoother and benchmarked (Quadrant, SmartBench, Linpack) much higher than his phone...

he got so upset that he went out and bought a DX 2 weeks later lol...i installed GB on it for him...we went through the same process and my phone benchmarks just about the same at 1.15 that his does at 1.2-1.3 lol

Paznos said:
The battery manager isn't very descriptive it just says that the Android OS is taking most of the battery 37% with the Use details showing CPU total 1h 1m 12s.

There's no way I can immediately tell what's sucking up all the battery it's not showing any time without signal no apps that are draining the battery, I'm getting half the battery life I would get in the same circumstances.
Click to expand...

well Android OS sucking 37% is quite a lot...and if its using the CPU for 1h+ im surprised that the usage percentage isn't higher than that...thats a lot of CPU usage...
 
Flashed CM7 on my second DX just for giggles. Wow, it's speedy. Once we have a reliably working camera I could see this being a daily driver.

No sure how acurate the Quadrant scores are on this ROM but I got 2150 before OC'ing and 2750 after going to 1.35 LV.
 
Well I'm back to CyanogenMod again... was on SSX then back on Liberty GB... I just can't get enough of Cyanogen... my only complaint is the battery life. I can get a good 4 or 5 hours longer on Liberty... oh well, it is amazing and I can just keep a charger with me.
 
Gonna give my setup a few days to get adjusted and then hope the battery life is good. The camera/camcorder fix on the rootzwiki page for CM4DX works perfectly and I'm running imoseyon tweaks now too.
 
As I understand, there's a video piece or something skipped, so it comes in faster than reality. Someone correct me if I'm wrong.
 
On Nightly #21 now... jumped from Nightly #10, flashed nightly + gapps + wiped Dalvik. Had a brief scare when it wouldn't boot past the Moto logo, pulled battery, then it got halfway through the Cyanogen boot process and restarted. Then it started okay and worked.

Figures the one time I flash something without making a backup first, it's going to hiccup.

Then flashed the camcorder/camera/video fix from RootzWiki. Tested camcorder, and that works - nice!

Built-in screenshots are great. Kinda wish it was a key combo instead of the system menu but no big deal. No problems yet but it's only been a couple hours so I'll reserve full judgement.
 
binary visions said:
On Nightly #21 now... jumped from Nightly #10, flashed nightly + gapps + wiped Dalvik. Had a brief scare when it wouldn't boot past the Moto logo, pulled battery, then it got halfway through the Cyanogen boot process and restarted. Then it started okay and worked.

Figures the one time I flash something without making a backup first, it's going to hiccup.

Then flashed the camcorder/camera/video fix from RootzWiki. Tested camcorder, and that works - nice!

Built-in screenshots are great. Kinda wish it was a key combo instead of the system menu but no big deal. No problems yet but it's only been a couple hours so I'll reserve full judgement.
Click to expand...

Got a link for the camcorder fix?
 
Also keep in mind the camcorder fix only records 480p, it doesn't do high def yet.
 
Always wondered. I'm still sitting on Nightly #7 or somin but when wiping dalvik to update to a latest build, does it matter if it's performed before or after the flash?
 
foo said:
Always wondered. I'm still sitting on Nightly #7 or somin but when wiping dalvik to update to a latest build, does it matter if it's performed before or after the flash?
Click to expand...

No, it should just be done before you boot for the first time - that is, do it in the same Clockwork Recovery session that you flash the build.
 
You must log in or register to reply here.
Back
Top Bottom