[DEV] - CyanogenMod - 7.1.0 {2.3.7} - 400/500 Only

[[ACL]]

Haha, i step out this afternoon and come back to all these replies. The only issue that really worries me is the sound for now. I'll look into that and see why my build is different. I may have missed something which always happens when you try to debug. Also im surprised thats all considering this is the first round of many.

As for the LS and Prox. Well cm has a different way of dealing with all that. Actually i think you can even turn it off in the settings so i havent gone too deep into it. It would be hard to believe it's broken since it works on omgb which is almost pure aosp. I am however working on improving the LS a little more. The issue is that it takes a good amount of light to actually brighten the screen. No problem, we can adjust some values right? wrong because lets say you turn off the lights and you want to just browse something on the phone, the screen will blind you if we change the values too much.

So the key is to find a happy medium. Almost all kernel updates from me lately have some sort of LS adjustment. I'll know when to stop when everyone no longer complains about it .. lol

[vzihome]

FYI apn won't "show/save" after saving, hence no mms both cm7 and omgb

Also using any value on sdbooster for me = black screen of death(on sleep)...have to pull out battery(both cm7 and omgb). Staying with stock value 128 running like a champ(omgb)

Sent from my (ACL) OMGB using Tapatalk

[[ACL]]

Originally Posted by vzihome

FYI apn won't "show/save" after saving, hence no mms both cm7 and omgb

Also using any value on sdbooster for me = black screen of death(on sleep)...have to pull out battery(both cm7 and omgb). Staying with stock value 128 running like a champ(omgb)

Sent from my (ACL) OMGB using Tapatalk

lets get some logs going .. I dont know what sdbooster is but im interested to know.

adb into the phone. do a logcat and run thatever is crashing. See what the logcat says. If it kills adb, then just copy and past the last thing you see.

Do the same for kernel but this is tricky. Adb into the phone and type "cat /proc/kmsg" This will show you the dmesg as it runs. THen crash the phone again with the app and see whats the last thing.

Thanks dood.

[Boominsvx]

Well here's a dmesg, logcat and logcat radio I threw together after playing sound, crashing the market and crashing launcherpro. May be of use so here ya go. I've had plenty of failed unblanks with SCREEN_STATE: error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE, but no soft reboots or crashed system server yet... I dont think. Probably cause I dont have service on this phone now.

Also, I see this after LauncherPro crashes
E/ActivityManager( 1075): ANR in android.process.acore (com.fede.launcher/.Launcher)
E/ActivityManager( 1075): Reason: keyDispatchingTimedOut

and I noticed the hard keyboard d=pad keys are off, and FN key doesnt seem to work. Not sure if this is related to the same theoretical "keys".

[vzihome]

Originally Posted by [ACL]

lets get some logs going .. I dont know what sdbooster is but im interested to know.

adb into the phone. do a logcat and run thatever is crashing. See what the logcat says. If it kills adb, then just copy and past the last thing you see.

Do the same for kernel but this is tricky. Adb into the phone and type "cat /proc/kmsg" This will show you the dmesg as it runs. THen crash the phone again with the app and see whats the last thing.

Thanks dood.

At work will do later, sdbooster set read write speed of sdcard

Sent from my Touch Pro 2 using Tapatalk

[arrrghhh]

Originally Posted by [ACL]

lets get some logs going .. I dont know what sdbooster is but im interested to know.

adb into the phone. do a logcat and run thatever is crashing. See what the logcat says. If it kills adb, then just copy and past the last thing you see.

Do the same for kernel but this is tricky. Adb into the phone and type "cat /proc/kmsg" This will show you the dmesg as it runs. THen crash the phone again with the app and see whats the last thing.

Thanks dood.

Heh, I run SD Booster, but never messed with the values on NAND - it was pretty important when we were running off of the SD card, but now it doesn't seem so important. I guess if you move apps to the SD card it is important, as those apps will then be running off the SD (duh).

Edit - I'll check it out and post some logs if he doesn't. I'm not on CM, I jumped ship back to OMGB... Evidently it fails on both tho.

[vzihome]

Originally Posted by arrrghhh

Heh, I run SD Booster, but never messed with the values on NAND - it was pretty important when we were running off of the SD card, but now it doesn't seem so important. I guess if you move apps to the SD card it is important, as those apps will then be running off the SD (duh).

Edit - I'll check it out and post some logs if he doesn't. I'm not on CM, I jumped ship back to OMGB... Evidently it fails on both tho.

You might have to post them not able to at the moment.

On another note installing the minimal gapps (that i posted on omgb thread) on cm7 no fc's, no sluggishness,no fail to wake issues(turned off auto brightness) running upto par with omgb or maybe better, dont know might be a placebo effect. Only thing from keeping me running cm7 is for lack of sound on speakerphone, i do like the sound volume on ear speaker, really loud!

Sent from my (ACL) CM7.1 using Tapatalk

[baalho]

This is looking really good, I had problem booting into android on the latest OMGB, so i had given up.

so far been using for couple of hours.
-After market fix, no fc (change language to english(us))
-USB thetering works great (using PDAnet from market)

issues so far
-Used the custom shortcut trick to get to WifiHotspot (ap), but would not start.
-No sound at all during calls
-Sound only comes from external speaker, and the volume is very low


looks promising!

Great job

[vzihome]

Could the sound problem be an audiopara file? Can I just switch it with omgb and be good?

Sent from my Touch Pro 2 using Tapatalk

[x12CHRIS18x]

Is this build stable now?