Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed**

[joban]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

After applying your fix, go to Settings ->Wireless & Networks ->Mobile networks, and try to enable "Use only 2G networks".

First off.. did that work? I'd really like to be able to force 2G like I could on stock Froyo.

Second, do the errors come back now after a reboot? I can dependably make them appear by attempting to change that setting.

I had to make a permanent purchase of SQLite Editor after trying to enable 2G. Here's the fix for the errors, in case anyone gets stuck in the loop of FCs.

yea 2g blacked out after i tried to click it, so i dont think it worked.

 

[buzzman]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

can use this rom and someone can tell me if the bluetooth works( send/receive file?
[UNOFFICIAL][ROM][stable:6.5.8,testing:6.6.1] CyanogenMod 7.1.0 (Android 2.3.7) - xda-developers

Flashed this yesterday- can pair bluetooth headset, but it won't connect. Maybe this is asso.with sending files one way but not the other?

 

[Inspector-Archundia]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

which rom ur running? and did it happen to all the roms u tried? how about 2.3.7?

I'm running mmatt v1.2... i havent tried any other rom, maybe i will try gingercrust v1.3, but i read i have to install a froyo based rom before installing gingercrust :S and i can't go from mmatt's rom to that one directly

 

[buzzman]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

I went from sonygen to gingerCrust and did not have a problem flashing. I did wipe everything I possibly could-Then went from gingercrust to CM7, again, wiped it all. Still don't have a working bluetooth headset.
They pair, but don't connect. I know it's not the headset. It connects with the 2.2.2 and runs vlingo.

 

[joban]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

alright guys i thought i fixed the com.android.phone error but after like 3 reboots I got it! So still working on it!

 

[CrackerTeg]

How are you getting that error? I haven't gotten that since the first kernel.

 

[buzzman]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

I got it on gingerCruzt before moving on to CM7. I also got it on the sonygen a bunch of times.

 

[LifesGoodPhoenix]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

now thats odd. i only got it on 2.3.7, call log error(evenstream) on sonygen, very eratic,.... nothing so far on 2.3.5

 

[CrackerTeg]

That's weird. Like I said, I only got it a handful of times on 2.3.7 and it was the first kernel.

 

[LifesGoodPhoenix]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

The only thing that's been consecutive with all roms I've tried is the black screen fumble while in call.

 

[CrackerTeg]

Yeah. I'd definitely have to agree with that one.

 

[PharmNerd]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

How are you getting that error? I haven't gotten that since the first kernel.

The com.android.phone error seems to be due to one of many triggers that end up improperly populating the "preferred_network_mode" value in the CM7 settings database.

Trying to disable 3G, trying to turn cellular data on/off, viewing or attempting to change various network settings, etc... If you try one of these things, for whatever reason, some ROMs insist on setting "preferred_network_mode" so the phone is in "Global" (CDMA?) mode. Manual attempts to set it as anything but "Global" are ignored.

 

[pietromoon]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

What generated that benchmarking graphic on the original post?

 

[buzzman]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

The com.android.phone error seems to be due to one of many triggers that end up improperly populating the "preferred_network_mode" value in the CM7 settings database.

Trying to disable 3G, trying to turn cellular data on/off, viewing or attempting to change various network settings, etc... If you try one of these things, for whatever reason, some ROMs insist on setting "preferred_network_mode" so the phone is in "Global" (CDMA?) mode. Manual attempts to set it as anything but "Global" are ignored.

I have cm7 running and have put in my att sim since it seems pretty stable. I have tried to force 2g(thought it was working in this rom) but it is a quick flash, then grayed out. But I have not gotton the com.android.phone error at all in this rom. I also shut off cellular data without any problems and it does not trigger the error.

Interesting- With my PAYG t-mo chip in, it runs edge without error. ATT 3g does not work on T-mo sims- all you get is edge speeds
****************************************************************************************************************************

How weird is this. Just turned on phone with t-mo chip in it and I now have the constant error on my screen. Can't get rid of it. Didn't have one for 2 days. Now it won't go away. Definitely time to switch out. I will put on the last one to try- the cyanogenMatt rom.

 

[LifesGoodPhoenix]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

What generated that benchmarking graphic on the original post?

CM7.1 2.3.7 with original kernal

 

[PharmNerd]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

I have cm7 running and have put in my att sim since it seems pretty stable. I have tried to force 2g(thought it was working in this rom) but it is a quick flash, then grayed out. But I have not gotton the com.android.phone error at all in this rom. I also shut off cellular data without any problems and it does not trigger the error.

Interesting- With my PAYG t-mo chip in, it runs edge without error. ATT 3g does not work on T-mo sims- all you get is edge speeds.

The phone generally works fine after you change those values...

...until you reboot it. At least for AT&T. Maybe it works just fine with T-mo.. (?)

 

[cvm]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

it is unlocked

 

[buzzman]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Joban, i have a bug i think is caused by the kernel... when the phone is locked and i press any key it gets stuck in a black screen unless i use a live wallpaper (i can get out by touching on the screen). But that is not that bad, the most anoying bug is when i receive a call, the phone also gets stuck in the black screen and i have to guess where sliding bar is to pick up the call, and i can't see who is calling. This last bug happens regardless if im using a live wallpaper or not. thank you...

On this same rom I had all this happen to me tonite. Phone rang twice, couldn't answer cause it was a black screen- unresponsive. Then later, It was stuck on the black screen. I couldn't shut it off or get a home screen. It had to wake itself up. And I have a live wallpaper running. It might be time to move on to the next trial. This, along with not being able to connect my bluetooth headset might push me onward to cyanogenMMattv1. Haven't tried that one yet.

 

[joban]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

yea guys seems like we have too many bugs! i was working on a new kernel with all these things in mind but the phone wouldnt go past the boot animation screen n crashed, so need more work! well be on it over the 3 day weekend! if i get this fixed i want donations from all u

 

[donavan]

Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Joban... Is this new kernel going to be for designed for 2.3.7 or for the older 2.3.5 thats seems to be more stable with your past kernel releases? Just wondering if Im looking at reinstalling a different ROM or just updating the kernel?