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

**thrivin** · 10-27-2011, 12:20 PM

It seems like most of you guys have the Phoenix.

Has anyone had any success with the Thrive?

My last attempt at this resulted in a complete and full brick, so I am nervous about going forward without confirmation.

**joban** · 10-27-2011, 12:52 PM

yea thanks man!

and there are alot of guides posted here how to get CWM, so just look around man

**joban** · 10-27-2011, 12:56 PM

Always i would be adding a list of the people who donated because that really means to me. I did spend many countless hours on the kernel and shared it to everyone so they can enjoy their phone and not soo many about getting money in return, but it does give me the motivation to keep on working!

THANK YOU!

**joban** · 10-27-2011, 02:38 PM

Originally Posted by thrivin

It seems like most of you guys have the Phoenix.

Has anyone had any success with the Thrive?

My last attempt at this resulted in a complete and full brick, so I am nervous about going forward without confirmation.

First of all you cant really have a full brick with a flash zip! Second I think u didnt get the CWM recovery installed right and there is your problem.

**PharmNerd** · 10-27-2011, 05:54 PM

Originally Posted by thrivin

It seems like most of you guys have the Phoenix.

Has anyone had any success with the Thrive?

I just installed it on my Thrive. So far so good.

Using Cyanogenmod 7.1 from the first post in this thread. Flashed Gapps per the P500 forum sticky. Did not need to do anything special to get GPS working.

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.

**wlfpck** · 10-27-2011, 07:09 PM

Donated to you Joban

Haven't had a chance to try all this out. I will do so once I get time to do so. Keep up the great work.

Also....

I gave LG a call today. They had to transfer me up a couple tech levels but they are currently working on the gingerbread rom for our phone. Though at the rate they're going, we might have 4.0 ICS out and rolled onto our cells by the time they throw gingerbread out.

**PharmNerd** · 10-27-2011, 07:46 PM

Hey, Joban...

How did you manage to OC to 768MHz? I've tried a couple times, but end up with kernel panics after no more than a minute.

I've been trying to overclock by changing the setting at Settings --> CyanogenMod Settings --> Performance --> CPU settings --> Max CPU frequency.

**CrackerTeg** · 10-27-2011, 08:26 PM

I've been getting the same thing even at 690. Weirdest thing.

**PharmNerd** · 10-27-2011, 08:35 PM

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.

**sabrelime** · 10-27-2011, 08:53 PM

I've set mine at 748 for..... forever now, with no problems.

I have set it as high as 806, but after a couple of minutes, the phone crashes. I rolled it back to 748 because that was the best quadrant benchmark I was getting. Whenever I went past 748, the numbers started going back down. The only thing I can think of is that it starts tripping over itself when you push it past that.

**donavan** · 10-27-2011, 09:28 PM

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.

**kingv10** · 10-27-2011, 10:09 PM

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

**dybdahlD** · 10-27-2011, 10:28 PM

Originally Posted by CrackerTeg

I've been getting the same thing even at 690. Weirdest thing.

try using setcpu in the app market

**joban** · 10-27-2011, 11:46 PM

Originally Posted by PharmNerd

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!

**joban** · 10-28-2011, 12:51 AM

wlfpck been added to the donator list! thanks man!

**CrackerTeg** · 10-28-2011, 04:29 AM

Originally Posted by dybdahlD

try using setcpu in the app market

I did.

**jrmoore10** · 10-28-2011, 04:48 AM

New update ROCKS!!! Joban is the MAN!!!

**PharmNerd** · 10-28-2011, 08:40 AM

Originally Posted by PharmNerd

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

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.

**donavan** · 10-28-2011, 09:21 AM

Originally Posted by PharmNerd

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.

**vipe_202** · 10-28-2011, 10:09 AM

Originally Posted by donavan

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.

**donavan** · 10-28-2011, 10:26 AM

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.

**ACMobiusOne** · 10-28-2011, 02:39 PM

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!

**donavan** · 10-28-2011, 02:53 PM

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.

**sabrelime** · 10-28-2011, 03:15 PM

Originally Posted by ACMobiusOne

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!

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.

**joban** · 10-28-2011, 03:35 PM

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.