[CDMA HERO ROM] Gumbo ROM 1.5c

@psudeo
Glad it worked. Our Google overlords are pleased :)

@pewpewbangbang
I don't know if you noticed, but I didn't have too much to say about the issue. That won't change here. I'm not going to put myself on the spot and say it works or it doesn't. I got tired of everyone begging me to build a kernel with the patch in it, so I did and warned everyone that it was at your own risk. Overclocking is impossible to accurately measure because you have to use software that can/will be affected by the rest of the system.

Some swear it works. Some swear it doesn't. I swear there's no way to tell. If you need an app on your phone that says you're overclocked but still throttled by the bus speed and i/o bottleneck (as is popular now :) ) you can use the kernel you linked to to get up to 1001 bogomips, but I'm not suggesting anyone do it.
 
Again, I don't know. I haven't tried it -- I haven't needed to. There is an overclocking app that people used to use (some still do), that will allow you to try to go beyond even 688mhz, but again -- there's absolutely no point; our phones won't be able to handle it anyways. If I read correctly, someone had said that fasted out phones' cpu's could clock was about 700 something... I may be wrong, though.

To touch on this a bit more. Using conventional methods, like soldering a jumper across the CPU and changing the voltage the Hero's CPU can run @768 Mhz in theory.

You can OC a computer because the BIOS gives you access to the motherboard hardware and offers more than one clock speed multiplier. That's not present or accessible on a phone.
 
To touch on this a bit more. Using conventional methods, like soldering a jumper across the CPU and changing the voltage the Hero's CPU can run @768 Mhz in theory.

You can OC a computer because the BIOS gives you access to the motherboard hardware and offers more than one clock speed multiplier. That's not present or accessible on a phone.

That's exactly what I thought. I've OC'ed a computer before -- but figured unless someone actually took the phone part and did some "soldering", this wasn't very feasible, to not mention, I don't know how to solder... lol.:rolleyes:
 
Yea im pretty noob at phones compared to the computer. I overclock my systems so i know about that stuff but phones are different haha.

I actually want to get into programming for Android and all that stuff, something to learn and possibly do as a career in the future when i go to college and stuff. And this seems like a great place to start somewhat, atleast when i get the phone haha.

Yea, the apps like SetCPU and stuff don't work i don't believe, well they work, just not in overclocking the CPU past 528mhz which is stock.

I agree, it probably wont be needed once flashed to Gumbo 1.5c :) but you know, all that talk about the lag, especially when the phone first came out, and the fact that the hardware is from 2007 unlike the HTC Legend which will have hardware from 2009.

Anyways, yea it probably wont be needed in the end and i doubt i will even try to go past 528mhz. Was just wondering i guess and it was a possibility.

Also, the fastest phone CPU out there right now is Snapdragon, and it clocks at 1000mhz or 1ghz :D it's on the Nexus One and the HTC Supersonic as well as the HTC Desire. The Samsung Moment also has an 800mhz CPU so yea, there are phones out there with CPU's faster than 700mhz. The Droid can be clocked up to 800mhz stable and safe also, atleast from what i've read and from what i've seen on my friends droid which runs 24/7 at 800mhz, well not 24/7 but thats the max clock and the minimum is like 125mhz when the screen is off and stuff.

Thanks though guys. Hopefully i can get into programming apps and stuff since it seems really fun and i might want to go into that career field in the future. Also have something to write on my resume for college or something haha :)
 
Thanks though guys. Hopefully i can get into programming apps and stuff since it seems really fun and i might want to go into that career field in the future. Also have something to write on my resume for college or something haha :)
If programming is something you want to do -- then start NOW, don't tell yourself you'll do it later (not saying you are -- but that's what I did, and I hate myself for that). Practice whenever you can. To get started, there are TUNS of resources on the internet. If you're not familiar with Linux, I would highly advise you to become familiar -- it'll definitely help you with whatever technical area you want to go into.

Java is probably the best language for you to start with, especially if you want to develop for Android. Install Android's SDK (developer.android.com) and play around with it, you'll only be making yourself better off. Start early, practice often, and success will become inevitable.
 
haha im not 100% sure wat i want to do yet. Just mainly engineering/computers/electronics right now, programming is just a possibility.
 
Well, I just flashed BARE along with the SenseUI package.

All I can say is...

I LOVE YOU MAN!!! LOL :p :p

Seriously though, I had been toying with the idea of rooting and flashing this ROM for the longest time... and basically, I grew TIRED of that stock Sprint ROM lagging the **** out of the phone.

In the hour I've spent restoring my phone (contacts, apps, settings....etc etc), here's the noticeable improvements:

Speed: Startup is lightning fast (love that startup animation BTW ^^). The phone responds now. No more clicking then waiting... waiting... waiting... yeah, you get the idea.

Keyboard: Even with the haptic feedback enabled, it's still peppy. NO LAG! LOVE IT!! <3

Market: On the Stock ROM (unrooted), the Market would HORRIBLY lag if it was downloading or installing an app. Now? Not at all. I can breeeeeze through that market! :D


I'm going to play with this more, and I'll add more feedback as I use this more. So far so good! Great job gbhil!
 
Last edited:
Well, I just flashed BARE along with the SenseUI package.

All I can say is...

I LOVE YOU MAN!!! LOL :p :p

Seriously though, I had been toying with the idea of rooting and flashing this ROM for the longest time... and basically, I grew TIRED of that stock Sprint ROM lagging the **** out of the phone.

In the hour I've spent restoring my phone (contacts, apps, settings....etc etc), here's the noticeable improvements:

Speed: Startup is lightning fast (love that startup animation BTW ^^). The phone responds now. No more clicking then waiting... waiting... waiting... yeah, you get the idea.

Keyboard: Even with the tactile feedback enabled, it's still peppy. NO LAG! LOVE IT!! <3

Market: On the Stock ROM (unrooted), the Market would HORRIBLY lag if it was downloading or installing an app. Now? Not at all. I can breeeeeze through that market! :D


I'm going to play with this more, and I'll add more feedback as I use this more. So far so good! Great job gbhil!

Good to know, I'm installing Vista on my Macbook just to do this. I asked my gf if I could borrow her computer and she said... What for? As soon as I mentioned rooting my phone, her eyes rolled and said, hell no.
 
Well, I was a little confused this morning. My phone battery was at 100% last night.... and I when I woke up 5 hours later... it was dead. Any ideas what could've destroyed the battery in that short of a time period? :confused:
 
Well, I was a little confused this morning. My phone battery was at 100% last night.... and I when I woke up 5 hours later... it was dead. Any ideas what could've destroyed the battery in that short of a time period? :confused:

You have an app that has locked the phone awake. Biggest known culprits are Wavesecure and Youmail. Keep an eye on the awake time in settings, if it gets high or reads 100%, the spare parts app in the ROM can tell us which app it is.

Most times a reboot fixes it, unless its wave secure or youmail. If it keeps giving you trouble, I'll be happy to help you track it down.
 
You have an app that has locked the phone awake. Biggest known culprits are Wavesecure and Youmail. Keep an eye on the awake time in settings, if it gets high or reads 100%, the spare parts app in the ROM can tell us which app it is.

Most times a reboot fixes it, unless its wave secure or youmail. If it keeps giving you trouble, I'll be happy to help you track it down.

I took it off the charger at around noon and battery level is currently sitting at 87% at 3pm. Awake time is slowly dropping... sitting at 61%. So, I think it's okay now. :)
 
Not sure. I've never seen or heard of this. Got any links? I'd love to have a look and try to figure out why, and moreimportantly how to fix.

I just re-read my post and realize I left a very important detail out. It's on the lock screen.. where it shows any alarms you have set. I have mine set for 8am tomorrow and it shows 1266584400000.
 
Do you think live wallpapers and themes would lag the phone really bad?? Like even on your custom rom?

Live wallpapers won't run on 1.5. You'll have to load a hacked ROM (buggy, but usable) or wait for Sprint to get us an upgrade.

Themes however, will run just fine.

I took it off the charger at around noon and battery level is currently sitting at 87% at 3pm. Awake time is slowly dropping... sitting at 61%. So, I think it's okay now. :)

Good to hear. Like I said, if it happens again holler at me.

I just re-read my post and realize I left a very important detail out. It's on the lock screen.. where it shows any alarms you have set. I have mine set for 8am tomorrow and it shows 1266584400000.

Happens for me too.

Neat. I know it's not neat for you guys lol. I'll poke around and see if anyone has found and info about fixing that. Thanks for the heads up.
 
I've been running Bare for a while and enjoying it, but now I want Sense back. I downloaded the Sense package here, rebooted to recovery and flashed the zip. Rebooted, and got mass FCs and no signal. So I rebooted again and wiped, then rebooted. Same thing.

After typing that already on my phone, I realized I'm also using the custom memkiller settings for a non-Sense UI. That could cause the FCs, buy what about the no signal?
 
Neat. I know it's not neat for you guys lol. I'll poke around and see if anyone has found and info about fixing that. Thanks for the heads up.

In my quick Google searches, I've found a few bug reports and complaints from people using AOSP releases with the same problem. Each of the ones I've found have been a person reporting it, and zero responses. As far as I can see, it's an issue that no one cares about.
 
I've been running Bare for a while and enjoying it, but now I want Sense back. I downloaded the Sense package here, rebooted to recovery and flashed the zip. Rebooted, and got mass FCs and no signal. So I rebooted again and wiped, then rebooted. Same thing.

After typing that already on my phone, I realized I'm also using the custom memkiller settings for a non-Sense UI. That could cause the FCs, buy what about the no signal?

Try wiping dalvik cache from recovery. This is the first report I've heard of no-signal issues. All flashing the sense package is doing is pushing all the stripped out HTC apk's back where they belong, so I can't think of anything that would affect the radio.

In my quick Google searches, I've found a few bug reports and complaints from people using AOSP releases with the same problem. Each of the ones I've found have been a person reporting it, and zero responses. As far as I can see, it's an issue that no one cares about.
I've fired off an email to the big guns - Cyanogen and Paul O'Brien. Hopefully they have some ideas.
 
I did that. I just now RUU'd, re-rooted, and flashed again and I'm getting some FCs and no signal. Very odd.

When I open the phone app, android.process.acore FCs
 
Last edited:

Trending Posts

Forum statistics

Threads
957,011
Messages
6,971,034
Members
3,163,683
Latest member
philstephenrichards