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

Status
Not open for further replies.
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Without getting into a huge explination about overclocking suffice to say that not all chips are created equal. When a chip maker produces a CPU they will test a lot of them and if they consistantly get no errors with a given speed they will mark the processor for that speed. However that doesn't mean you can't dial it up to 11 and get a little more out of your chip some chips will run at far faster speeds than they are speced out, for others not so much, but all of them will run at the advertised speed (600mhz) in our case. The other limiting factor is the rest of the hardware, your CPU may be running at a faster clock cycle but that doesnt mean everything else is. Your memory for instance might not like running with the clock multiplier that matches up with your CPU (AKA stumbling all over itself). Just because one machine can be cranked up to a super fast speed doesnt mean the same model running the same OS will have the same level of tolerance.
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Works great! Thanks joban I'm about to donate! For those with the lock screen lag bug, it seems to go away if you use a live wallpaper, weird... but a fix I can definitely live with
 
  • Like
Reactions: PharmNerd
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

AAAARGH!! I've been hit with the com.android.phone error!

Anyone have a link to the fix (besides factory reset)? The link on the sticky page is dead.

well im using the sonygenmod 1.2 which doesnt have that error because that made me mad too! the link to it is on the front page!
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

wlfpck been added to the donator list! thanks man! :)
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

New update ROCKS!!! Joban is the MAN!!!
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

AAAARGH!! I've been hit with the com.android.phone error!

Anyone have a link to the fix (besides factory reset)? The link on the sticky page is dead.

Found something online to work my way out of this.. phew...

- Put phone in Airplane Mode to stop the FCs; then turn JUST Wifi back on
- Buy SQLite Editor from Android Market
- Open the app
- Browse to Settings Storage (com.android.providers.settings)
- Tap on settings.db
- Tap on "secure", then scroll down and delete "preferred_network_mode"
- Turn off airplane mode (you'll probably get the error one more time, but it'll go away after you dismiss it).
- Open Android Market app on phone and return SQLite Editor before the 15min deadline runs out :p

Also... a word to the wise: do NOT enable "Screen-on animation"!! Instead of an animation, you'll be stuck with a black screen. I did this, and had to do a battery pull to bypass the failed animation and turn off that setting. Coincidentally, after the battery pull, this is when I also ran into the com.android.phone errors.
 
Last edited:
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Coincidentally, after the battery pull, this is when I also ran into the com.android.phone errors.

Im wondering if there is a database corruption that happens, I kept getting it every time my phone links up to my google account till then it runs fine but once it links you start getting the com.android.phone error. I have not seen any issues using the 2.03 kernel with MMatts Cyangen ROM aside from the lack of gyro and the wifi reconnect being a little stupid. I am going to try the new kernel in a few mins, havent had time till now.

On a side not the battery issues were fixed by doing the following and apparently should be done anytime you ReROM you phone.

1 Charge the phone to 100%
2 boot to CWM and delete the battery stats
3 let the batter drain completely

thats it apparently there are issues with the different ROMs reading the stats all weird and the discharge and recalibration fixes it.
 
  • Like
Reactions: PharmNerd
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Im wondering if there is a database corruption that happens, I kept getting it every time my phone links up to my google account till then it runs fine but once it links you start getting the com.android.phone error. I have not seen any issues using the 2.03 kernel with MMatts Cyangen ROM aside from the lack of gyro and the wifi reconnect being a little stupid. I am going to try the new kernel in a few mins, havent had time till now.

On a side not the battery issues were fixed by doing the following and apparently should be done anytime you ReROM you phone.

1 Charge the phone to 100%
2 boot to CWM and delete the battery stats
3 let the batter drain completely

thats it apparently there are issues with the different ROMs reading the stats all weird and the discharge and recalibration fixes it.

Interesting, I've never done this/doubt i will, cause i get at least a good 19.5 hrs out of my phone, with a few 20-30 mins calls.
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Mine was getting about 5 hours a charge after I flashed to a new ROM now Im getting around 20 some hours with normal usage.
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Installed on a Thrive successfully, with the exception of bluetooth not working. It is able to find and pair with a device, but the status remains "paired but not connected."
Everything else works, so thanks for bringing custom roms to this phone! :D
 
  • Like
Reactions: joban
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

I could never get the bluetooth working till I went to Cyangen MMatts rom but I have been running it with the 2.08 kernel and it is working fine.
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Installed on a Thrive successfully, with the exception of bluetooth not working. It is able to find and pair with a device, but the status remains "paired but not connected."
Everything else works, so thanks for bringing custom roms to this phone! :D

I had THE EXACT SAME PROBLEM. I fixed it though.


I have an cheap Emerson bluetooth headset that would pair with my device, but not connect. After it was paired, I held the talk/hangup button on the bluetooth and the phone asked me if I wanted to connect with the bluetooth device. I clicked yes, and VOILA!. It works. :)


Here's a screenshot of me making a call. Remember the blue background means that ts connected to my bluetooth.

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

thats great guys! im also getting some amazing battery life as well! i remember on stock it from from 100% to 0% in just like 5-6 hours if im using the phone or not! and now its like 19+ hours! loving it! and for the bluetooth i quiet dont know cuz i dont use bluetooth myself, but let me know if the issue is not solved.
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Its ok Joban. I can assure you that the bluetooth works. I've been talking to people on it in my car all week.
 
  • Like
Reactions: joban
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

and sabrelime thanks for the donation! :) ur name is added to the list now!
 
Re: Joban's Kernel 2.08 (Overclock, CM7 2.3.7 etc..) **Gyro Fixed

Since I don't really use transport functions over Bluetooth, I figured I'd be fine. We'll see when I try syncing up the Miccus BluBridge in my car, and the Belkin Receiver in my office.

Bluetooth seems to work more-or-less like it did on stock. No problems whatsoever.

One thing CM7 does that stock never did is automatically connect (sometimes) to my always-on Belkin receiver when I enable Bluetooth. On stock, I always had to go into BT settings and manually connect.

Noticed this morning that I was down to about 60% battery about 3hrs after unplugging. On stock I was always able to get up at 5:30am, use my phone all day, and have about 20% leftover when I went to bed at 10:30pm -- so CM7 was worse than stock at first.

Did donavan's battery setting reset a few hours ago -- we'll see tomorrow how that helps. Right now I'm TRYING to drain the battery, so that fact that I'm down to 30% after 3.5hrs doesn't mean much. :)

screenshot-1319836459441.png
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
956,898
Messages
6,970,502
Members
3,163,642
Latest member
958ryan