yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] Drunkpilot:
As far as the kernel and the usb issue, there were some people that were having those problems, so Jaybob made a 2nd .35 kernel that disables the headset capabilities to try and fix that issue. Here is the thread: http://xdaforums.com/showthread.php?t=1110418. This way you can still stay with the .35.

I'm wondering if running the min. CPU at 521 will help to overheat your battery and cause reboots. I wish I knew more about governors and schedulers find the optimum. I know that on s0be's .35 kernel there were limited choices (which I would expect as it is/was still in its infancy really). I haven't run Deca's battery tweak in a while (which is a tweak of Collins tweak) so I haven't looked at the different options available and tested different ones to see the results on gps, etc. When I ran Jaybob's CM 6.2 that has Deca's #589 kernel cooked into it, it's default scheduler was deadline (I think that's what it was called), but in s0be's .35 (as I can speak to JB's version) there was no deadline- there was noop and bfq. Like I said, I know very little about the ins and outs to see if this even has a chance of mattering.

I love the smoothness of this rom. Good times for the Hero.
[Hero CDMA Android Development] windtrader:
Can't some of the cpu setting apps control specific apps if that makes sense? For example, if a map app runs the cpu min can be set up higher?
[Hero CDMA Android Development] hakujin:
Thx, but think I"ll defer to the 1st .35 as I like headset periodically, and the USB problem is mild; doesn't always present itself and is moot for me under regular use as I can utilize Samba Filesharing when needed.

Isn't this Jaybob ROM built of the same CyanogenMod Herocmod? Wonder why if this is the case, that the problem is here but not there.

As far as schedulers, I've always been under the impression that interactive was best governor so I have stuck to it. NOOP scheduler is the simplest I/O scheduler for the Linux kernel and is the least demanding to SD, afaick, though not sure what is run be default according to this kernel.

Anyway, the min CPU seems to have very little impact on my batt life or heat of phone so I'm actually quite surprised there.

I'm going to dry run Navigon as well now that is in order and will let anyone know if I have any issues on my Heroc.

If you or anyone should happen to see an updated kernel, say .36, that remedies both USB, Headset, and Camera, let a user know! To that end, how about CM's v2.3.4 default kernel (this leads back to my orig. question)?

:)
[Hero CDMA Android Development] ehiggins:
my navigation works flawlessly on froyo 352-652 on demand draws fine. I think its more of a cyanogen thing than a cpu thing. I actually only miss theme chooser
[Hero CDMA Android Development] bravo1565:
What difference did you see on the rom?
[Hero CDMA Android Development] 24601:
Using v6 - option 3, with v8 tweaks. The overall responsiveness is quicker and less laggy; apps open quicker, screen scrolls smoother, etc. No need for memory management apps. The incoming call screen delay is gone. Wifi tether seems to hold better (may be placebo).
[Hero CDMA Android Development] ch1naski:
What v8 tweaks? In the options menu, the first one?

nandroids are for

sissies
[Hero CDMA Android Development] genuser:
So I still believe that the CPU governors on GB don't perform as well on the Hero and that is at the root of the gps issues. That is why bumping up the min CPU speed makes a big difference. Similarly, you have to bump up min for Pandora to work. I have watched the CPU speed in the Setcpu info screen while naving (not recommended :eek:). When things start to lock up, the CPU speed is stuck at the min. To me, this means the governor isn't responding to the demand. You can duplicate the symptoms with Pandora, which has always been known to lock up the phone with low min CPU speed. Most of my gps issues come with an increase demand for CPU. Times such as loss of signal, recalculating route, etc. I think the increased demand overwhelms the little Hero processor and it goes deer in the headlights ;). My 2 cents.
[Hero CDMA Android Development] GeezyAF:
There's "V8" scripts in the original thread.

Basically a little taste of what his next script will have.

I'm running those as well.
[Hero CDMA Android Development] windtrader:
Here is the update on my testing. I want to go back to froyo! What I am seeing consistently now is that the GPS signal gets dropped for short periods of time and the software gets confused and lost. For example, in Google Nav, things start out fine for a minute (reboot first), screen scrolls, lady talks. Then it will slow down or freeze. Then I can hear all the navigation voices and it is still tracking for a bit but the moving map has frozen.

In Navigon, it will get GPS signal lost and once in awhile it will reacquire the GPS. Either way the phone is able to stay alive and if I go back to Home and start GPS Status, it will acquire fix.

As to exactly the cause, I have given up. These devices are extremely complex hardware and software design and the true root cause could be in thousands of places. I still believe that something was redesigned in GB that assumed higher minimum hardware/software specification and we are running below that and all the Android QA did not fully test the level of our devices. I don't even know if you run an unrooted phone if you can download GB.

I gave up and tried to roll back to a froyo config but ran into various sorts of problems, mostly not finding the right ROM and basic GAPPS to get going. Also forgot if CWM had to be backlevel as well. But that is my goal at least to satisfy my curiosity if going back to an earlier ROM resolves the issue and to reevaluate what I give up by staying there.

btw - I do get very strong GPS lock so I don't think signal is the issue but it is possible that it might lose it for brief moments as it is a car.
[Hero CDMA Android Development] ehiggins:
http://xdaforums.com/showpost.php?p=8135299&postcount=1

gapps and 2.2.1 are in that thread. I went back last week using that rom and that gapps. Everything was great and today my nexus s 4g came so I wish you the best of luck
[Hero CDMA Android Development] windtrader:
That is SO damn funny. I am ready to do the same thing. It seems that phone can be had for free or near free and all this GPS funky crap becomes a distant memory very fast. :-)
[Hero CDMA Android Development] bravo1565:
@24601

Option 3? Tried but all I see is scrolling speed and at the end choose 1-17
[Hero CDMA Android Development] ch1naski:
Out would be option 3. Choose a slow scrolling speed and you should see all the options.

nandroids are for

sissies
[Hero CDMA Android Development] st3v3_r:
My GPS is rock solid when using the Evervolv ROM ( http://xdaforums.com/showthread.php?t=1089589 ). Every other GB ROM I have tried, I get the GPS "freeze" issues. Don't know what's different in Evervolv than the other ROMs, but it works.
[Hero CDMA Android Development] 24601:
The first screen is for you to enter a scrolling speed number, 0-3. After that the script will scroll through your options, 1-17. But we should be having this discussion in the Supercharger thread. Let's not hijack JB's thread. Head over and i'll help you through it.
[Hero CDMA Android Development] hakujin:
Holy bejebus, Camera is sh1te on KERN .35, wtf... Camera 360 Ult., Camera FX Pro, HDR Camera, 'Camera', you name it!

Going back to .29. Can't take a picture.
[Hero CDMA Android Development] waqasr:
Why don't you try MiUi camera before you give up!

It was working for me. I only went back to .29 kernel because

.35 kernel was not recognizing my usb handsfree!!
[Hero CDMA Android Development] Robbie_G:
I'm not having any GPS or camera issues with this ROM. Is this just a problem for some phones?
[Hero CDMA Android Development] Drunkpilot:
It usually takes a reboot and it is fixed...for a while. The .35 kernel has intermittent camera issues. I have used all of the cameras and they all have crashed at some point. .35 is a work in progress. Check out the .35 kernel thread to find out more. The .29 kernel in the OP works just fine though.
[Hero CDMA Android Development] JeffW8:
Just some phones... And even then, I think some have there settings messed up.

(Posted while sitting on the train or on the... well, you know.)
[Hero CDMA Android Development] genuser:
I'm all eyes, show me the magic settings! My phone is now freezing on GNav with ASOP'S Froyo rom. :-(
[Hero CDMA Android Development] Robbie_G:
Maybe it's a hardware problem
[Hero CDMA Android Development] jamega2f:
After flashing the recent update my USB unmount works no more need to take my SD card out anymore

HUNGRY HERO EATING GINGERBREAD COOKIES
[Hero CDMA Android Development] JeffW8:
Apologies for the late reply. I saw your question soon after you wrote it, but it's a loaded question - lots to put down. I had posted this a week or so ago, but I'll try and be more clear and thorough. When I wrote it last time, I wasn't sure if my results from a ten-minute car ride were enough to indicate success - even though that's the longest Google Nav went without freezing on me. Now, I have gone at least 45 minutes with no signs of trouble.

Here's my Hero:

* jaybob's July 24th build

* jaybob's default kernel - .35, not .29

* CWMod 3.0.2.4

* Firerat's 1.5.6 mod at 110 18

* CPU is OnDemand, 691/691 (no battery drain either)

* Compache is 18%

* No JIT

* No surface dithering

* No purging of assets

* No locking home in memory

* No locking the messaging app in memory

* VM heap size is 48

* And I'm using ADW.Launcher EX, although that might not matter

FINALLY - Google Maps 5.5

I think a heap size of 32 should be fine. I tried upping the cpu to 768 and GNav definitely freezes. I guess I've known for a while that my phone can't handle 768, but I was always in denial.

Also, I don't use headsets, bluetooth or not. I also can't remember the last time I connected my phone to my PC via USB since I just use dropbox. As for camera, stock doesn't work, but I've been fine with Camera360.

If I've left anything off, let me know. I'm finally happy with my phone again.
[Hero CDMA Android Development] genuser:
Thanks JeffW8!

Unfortunately my phone didn't run well with the .35 kernel. Not nav, just basic use and it would reboot.

Other settings I agree with. My phone does run better with JIT enabled. I will probably give the new JB a try soon and give your exact settings a go.

I sense a 3VO in the near future! But the Heros will be around for handmedowns for a while.
[Hero CDMA Android Development] JeffW8:
You're welcome! I agree that it may be time for that new phone. I'm curious which is better... The 3vo or the soon-to-arrive Photon. I love the idea of the Nexus S, but can't stomach a single core phone. I would love for the phone to last 2 whole years.

(Posted while sitting on the train or on the... well, you know.)
[Hero CDMA Android Development] chalan30:
going back to .29 is what ive had to do numerous time over several .35 builds to get the camera to work. Its documented in the .35 github. but while .35 feels smoother, as far as every day usefulness .29 is plenty. FYI add this V6 Supercharger etc. and it feels even more snappy!
[Hero CDMA Android Development] waqasr:
I did apply the V6 SuperCharge script and I do feel the phone is more

snappy now but I wanted to ask once i upload the rom will i need to run

this script each time?

Also there are 2 more scripts mentioned in the original post

1.3GTurbocharger

2.98KickAssKernel

Should i also install those?
[Hero CDMA Android Development] Drunkpilot:
I'm giving them a whirl and they feel pretty nice. I've enabled jit as well and the tv animations still are working which is something I have noticed always stops it working. Also, switching the animations to fast in spare parts instead of normal speed. I'm actually doing all animations instead of some and its not frustrating me; I've been a " some" person since cm 6.2 redglass.

My quadrant scores are averaging over 400 now and that's with firerat's. I'm liking the tweaks along with JBGB.

Flashing IS a gateway drug!
[Hero CDMA Android Development] 24601:
You definitely should install the 2 v8 scripts - 3gturbocharger and 98kickasskernel. If you change roms you will need to run the scripts again.
[Hero CDMA Android Development] waqasr:
Thanks a lot for answering my question, I did that and MY GOD my phone is like 10 times more snapper then before!! The only thing is when I run the V6 SuperCharger script I dont understand the numbers it keeps asking me. Do you know what they mean and what numbers I need to select? I think I found this on

another post

"Firstly, choose the Scrolling text Speed, from 1 to 3

Touch the screen and tap the number 6, Balanced 3, the best choice for GT540, and hit ENTER .... The script will work .... after finished, touch the screen again and tap the number 16, to exit, and press the HOME button."

But some times it prompts me more then 4 times. I hope I didnt confuse you with my question since ENglish is not my first language. If I did let me know I will try to rephrase my question.

Thanks in advance!! :)
[Hero CDMA Android Development] chalan30:
I also installed the 3G and 98 scripts but didnt notice a whole lot of difference. I think the scripts get added to the ROM's build.prop file so as long as you dont wipe system it should still run, although Im not sure if you still need script manager installed?
[Hero CDMA Android Development] 24601:
The first set of numbers, 0-3, is asking you to establish the speed by which script manager will scroll the text on the screen while you apply the tweak. 0 is fastest. Type a number from 0 to 3 and hit enter on your screen keyboard. After that, the menu will scroll by, that is the second set of numbers, 1-17. You need to pick a setting you think will work best. For other Hero users running JB's rom, setting 6 or 7 seems to work best. YMMV. Try setting 6, then hit enter on your screen keyboard. Watch script manager implement the tweak. Wait for it to end. If it is the first time running the script, reboot either manually, or by typing 16 into the menu and hitting enter.
[Hero CDMA Android Development] waqasr:
Thanks a lot for taking time out and explaining the whole thing.

The thing is that I am still fairly new to all this so that why I always

have a lot of questions but I get it now =)

God bless
[Hero CDMA Android Development] genuser:
Photon is a pretty nice looking phone too. Very similar specs...

I don't know much about Blur, but have really thought highly of SenseUI and really only ran away from it on the Hero due to memory and CPU speed. Those won't be an issue in year 1 of a dual core device.

8MPixels on the Photon v.s. 5MPixels on the 3VO. I have never thought a phone camera was important until recently. It's really convenient and a good enough phone camera will never replace my DSLR, but it could replace my point and shoot for the times I don't want to carry another hunk of electronics.

Other major difference is unlocked boot loaders. 3VO is now unlocked. Motorola isn't very cooperative on this front and I don't know how long that will take.

I agree the Nexus S is a really sharp looking phone. The one lesson I learned buying the Hero was to always buy the most hardware that is available. Smart phones are right now where PC's were when Windows was just coming out. The size and demands of the OS and apps fast out grow the hardware. 15 years ago it was tough to get a PC to last a couple years unless you didn't upgrade your OS and apps. This is the same case with smart phones now. So buy as much hardware as you can!
[Hero CDMA Android Development] JeffW8:
I had to push the "Thanks" button for your post. Those were some great thoughts. I think you helped me with my indecision ;-)
[Hero CDMA Android Development] hakujin:
Mostly anecdotal, imo. CWMOD, Firerat, version of GM (I tried 4-6 versions) - moot. I have surface dithering, purging of assets and JIT on, and no problem w/ Navi right now. This tells me that none of those variables are directly to blame. I also use interactive in lieu of on demand. So this somewhat rules out governor being to blame. I think there's def. something to min/max clock frequency, which is amusing because this wasn't always a problem for me. Pretty suremy heap is the same as yours. Also def. something to sampling rate. Lastly def. something to the kernel to as .35 works whereas the identical settings in .29 do not.

In the end this is all mitigating a systemic bug. I think someone once laboriously explained it as bottom line: a memory allocation problem. The variables at play quell it to an extent but bottom line, I think it's a bug in code.

BTW, Camera 360 Prem is a great app (think orig. camera 360 went by wayside) in an of itself, but it has no effect for me toward resolving the camera problem. I've wiped date/cache on camera app, rebooted into recovery and wiped davlik + cache. Camera, 360, Zoom FX, & HDR camera refuse to save a shot, they just freeze. If I go back to .29, the problem vanishes, but then the gps beast.

Concerning now to hear of the problem carrying back to Froyo. I suggest wiipng 6+ times like a greasy stool. :eek:

As for me, I'm gonna try that v6 supercharger and drop akmo like its hot, like task killer many moons ago that preceded it. wonder if ANYONE Is running .29 w/ REALLY working GPS/Gmaps w/ zero issue.
[Hero CDMA Android Development] genuser:
I agree with your conclusion but wonder on one point... "who" is responsible for ramping up the CPU speed when demand hits the processor? Raising min cpu does help, so there is a clue here. I just assumed it was the governers since they at least set up the rules for how aggressively it ramps up and down. I know for a fact that I can get my phone stuck at min CPU and it won't come off the bottom.

I also highly suspect that the increasing demands on memory have to be pushing a phone like the Hero.

Could also just be the abuse. I have been overclocking my phone for almost a year. Dropped it many times. It's been a real trooper, but it's been a tough life. :eek:

Let me know how the v6 deal goes. I read on it last night and it's intriguing. If the issue is memory management, there's a chance that could clean things up. I installed ATK on the Froyo ROM to see if that helps. Not enough time yet to draw conclusions. Unlike GB, it takes Froyo well over an hour of Nav'ing to fail on my phone. That's quite useable.
[Hero CDMA Android Development] JeffW8:
Gingerbread is working for me with only one issue at all, and that is that the stock camera fails. With Camera360, my phone is perfect - no issues, nothing to complain about. Sure, I'm a couple of versions behind on Google Maps, but I haven't noticed. If you are still having problems, then there is a good chance that more of those settings make a difference than you think. You're probably right that it's a memory issue, but most of those settings deal with memory one way or another. I posted those settings and Google Maps version because I believe that if someone were to use them, they'd have more success. I'll grant that CWMOD and firerat's might not mean anything, but I posted everything about my phone anyway.

No one has actually disproved my theory that purging assets is bad, either ;)

And I don't remember who posted the tip about setting fast animations in Spare Parts, but that actually helped the perceived speed as well.

(Posted while sitting on the train or on the... well, you know.)
[Hero CDMA Android Development] hakujin:
tht sux that the problems carried back over to froyo :(. i don't remember any issues at any length of time, but now i'm 2nd guessing myself and thinking there is no other options (in terms of roms) at this point.
[Hero CDMA Android Development] hakujin:
Re: Governors,

Interactive, if it's properly implemented on this kernel (no reason it wouldn't be right?) reacts faster to CPU requests than ondemand, so if anything it should increase overall performance.

However, if we're running same min/max clock, isn't this moot anyway?

I do feel (as many of you) that setting the minimum too low is a contributing factor to what is conking out gmaps. The sad thing is there was no doubt MIN clocked much lower on Fresh early last year (plus bloated SENSE) and i went on a many hour trip and was able to multi task on my phone w/ no problems. My natural reaction would be, 'oh, Gmaps is far more bloated now, shame on google, or the advancement of tech (take your pic), 'cept... I regressed to early 4.x and while there was a definite boost to snappiness (esp. pre latitude), but gps would STILL drop in a matter of minutes, like clockwork.

Maybe... I could implement these new doable settings you posted above w/ older maps and best of both worlds (snappy and no gps fix loss), 'cept I'm left wondering to what end since I"m content w/ gmaps now. Think bothering me now is the camera, so I've decided to change a few more settings in likeness to aforementioned, w/ a 25k sample rate and see where this takes me. I am perplexed at high heap being beneficial though... would think lower size would be kinder to memory allocation on a device w/ very little memory (such as our Heros).

Anyway, looking forward to v6 and dispensing w/ AKMO but don't have time to test that today.

Incidentally, (and totally OT), Gallery has to be thee most BLOATED, PoS, app I've ever beared witness too. I just installed a class 6 (w/ class 10 performance) micro SD card in my hero and it was so painfully slow the other day. QuickPic remedies that, but w/ a nasty over sharpening affect on my pics that I can't stand. I also think this sharpening carries over when i upload pics to fb.

Edit: BTW, Camera 360 Ult. and Camera are both working for me again w/ a min max 652. Also running zeam launcher again (10th try, haha!) over my belowed LP. It always has felt snappier but missing features that I liked from LP; some (like 5 column drawer) have been added which is cool.

DoubleEdit: Interesting that I can finally run JIT seemingly stable now. This wasn't always the case. However, I'm thinking that my phone has really been on light duty as of late, as the majority of my apps are still on TB standby so time will tell with this!
[Hero CDMA Android Development] windtrader:
I came across something that got me thinking about source of GPS issue. I saw one of these either autokillers or cpu setting things and I thought I saw GPS as something that could be watched and tweaked. Of course the CPU and GPS are different so it could easily make sense that there are internal GPS settings that control a variety of parameters and maybe one of those in the CM7 releases is conflicting with other system settings. Just a thought.

I am trialing Evolver now and installed SetCPU to manage min cpu. I have it set at 480/691 and a profile to dial it down to 264/691 when screen is off. There used to be a lag on incoming calls when min cpu was set too low. will see if gps is stable and battery life does not suffer too much but i doubt it will be any noticeable difference as we all know gps and display gobble battery.
[Hero CDMA Android Development] genuser:
OBTW, which GAPPs are you running?
[Hero CDMA Android Development] JeffW8:
GB 03-25. I've heard about the newer versions, but I've never given them much thought.
[Hero CDMA Android Development] JeffW8:
Yeah, I feel the same about governors - never knew which ones would be the best, but since I found that running min and max at the same level doesn't hurt battery much, you're probably right.

My heap size is indeed back down to 32, and the phone does seem to run better that way. I just posted the higher number as that's what I had going at the time of the test.

What do you mean by "sample rate"? Are you using a different rom than jaybob's gb?

And let me know what you think about v6 - sounds like a lot of people like it, but I'm not sure I want to spend the time yet.

On your Edit: Tried dropping to 652, but no luck for me. Stock camera is just not working for me. It worked going to .29, but then GNav had trouble again - and I much prefer GNav.