yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] rambuster69:
Hi folks

even if the nifty little "similar threads" thingy came up with some matches, none of them deals with the issue on the HD2, and searching the threads didnt yield results either (unless i am asking the wrong questions that is...:-))

My problem: Flashing ROMs was a bit of a hassle but in the end i got a working android running on my HD2. But the issue is the the hardware keys seem to act up:

The call key (leftmost) seems to be the home key but also decreases the volume at the same time.

The home key is also the home key, but doesnt do anything to the volume.

The Windows Key SHOULD be the menu key, but brings me back home instead and increases the volume. In some apps (browser) it BRINGS up the menu, but also increases the volume.

The back key and the endcall key both work as expected (surprise)

This happend on the stock desire NAND i used before and on the ROM i use right now (cant remember the name, phone not here)

I already tried to get results with the keynrchecker provided with buttonremapper, but it comes back with several results per keypress (confusing).

right now i workaround with button savior, but i'd rather like to have the keys work as expected...

Does anyone have a clue as to whats going wrong?

Have a nice day

rambuster
[myTouch 4G Android Development] faux123:
reserved 2 just in case...
[myTouch 4G Android Development] Marine6680:
Think I may try this out.

Never used the Minmax governor before. What does it do?

I use SetCPU profiles for when the battery gets low, the smartass governor does not work well for that, and I have the screen off profile disabled now. The CPU probably does not use that much power to matter that I cant just use smartass all the time.

Gonna hit up the dev of setCPU to add multiple conditions for profiles. Like battery level and screen off in one profile.
[myTouch 4G Android Development] RavenWulf:
out-f*ing-standing, I was about to give up and switch from Gr8Gorilla's DHD port with tiger13's Gorilla Red theme to CM6 or to eVil D's DHD port just to get the 1.8GHz and Smartass governor. this works perfectly for me... Wi-Fi, Wi-Fi Hotspot and Wi-Fi calling work perfect first time every time. Thanks much :D

Edit : so far so good, is grabbing mobile data without issue, ALL of my wi-fi is working without issue, not getting boot loops or random reboots.

I must say very well played for your first kernel hack.
[myTouch 4G Android Development] Seifer48:
Flashing now, exactly what I was looking for! I'll be sure to let you know the results
[myTouch 4G Android Development] Onefast:
How should I set up setCpu? It doesn't need a screen off profile? Thanks! Working great so far w/ no issues!
[myTouch 4G Android Development] ckisgen:
I dug this up on the minmax governor...not sure of it's accuracy but sounds about right? lol

minmax governor - I have been investigating the behaviour of different governors (ondemand, conservative, interactive) very heavily during the last couple of weeks. It seems that they tend to jump frequencies a lot. This is why ninpo now releases his kernel with a very small frequency table (and requires him to provide different versions for each speed you want).

My idea was very simple, the 'minmax' governor will only jump between the min frequency and max frequency! It will select which frequency according to the current cpu load. This is great because you can set the min and max frequency easily with SetCPU.

This seems to also improve responsiveness and not to hinder the battery life. It is true that your phone will now spend most of its "working" time at the max frequency but this is great it gives you performance and from what I tested does not drain the battery too much. The heavy battery drainers are things like wifi, etc. and when the phone goes to sleep, its sleeping anyway.
[myTouch 4G Android Development] RavenWulf:
see, this is why I keep directing the guys over on Android Forums over here. I was getting ready to take a pic of my new Golden Bushy-nose Pleco to show my buddy, when I noticed the "camera bug" I log in to give faux the heads up about it and BAMM he has already discovered it and put out v0.2 with the fix. Man do I love our dedicated developers and hackers, y'all are the ****!!!
[myTouch 4G Android Development] ckisgen:
flashed this kernel over about an hour ago. I'm currently running Ice Glacier 1.1.6 and was missing the smartass kernel from eVil's DHD ROMs but wasn't ready to leave Ice yet. I really like this kernel so far. no issues, everything seems to work. it's snappy and I love that faux has already released v0.2 (same day as v0.1?)

I snagged a 61.4 linpack oc'ed to 1.8ghz with this kernel. That was with v0.1 For whatever reason it's a couple points lower on v0.2 but I don't really put a whole lot of stock into those benchmarks. Just kind of fun to toy around with.

Great job, Faux! Everyone remember to hit your thanks button!
[myTouch 4G Android Development] jmwils3:
seriously awesome job on the kernel, bro :) flashing the 0.2 now, and eagerly awaiting whatever you have in store for 0.3 that youre working on now. good luck!
[myTouch 4G Android Development] negreenfield:
For whatever reason I can't get this kernel to boot. I'm running Ice Glacier 1.1.6, I've installed grankin's kernel in the past with no issues, but this one gets stuck at the Ice Glacier "Android" screen after about 15 seconds and just sits forever. I go back, clear cache and dalvik again, install grankin with no issues. Very weird.
[myTouch 4G Android Development] epsix:
I'm also running Iced Glacier 1.1. 6

I have no problems what so ever when flashing faux kernel.
[myTouch 4G Android Development] jmwils3:
mine did that at first on on 0.1. Try flashing the kernel a second time (no wipe at all). For some reason, that worked for me. And it DOES take a while to boot on first install, so give it plenty of time.
[myTouch 4G Android Development] negreenfield:
Just installed without cache or dalvik wipe and booted fine. We'll see how it runs.
[myTouch 4G Android Development] jmwils3:
glad it worked :)
[myTouch 4G Android Development] negreenfield:
Thanks for the suggestion. Seems to run really well.
[myTouch 4G Android Development] jmwils3:
well dont forget the thanks button :) though faux deserves it more, he's the one who gave us this awesome kernel.
[myTouch 4G Android Development] bobsbbq:
What does the Feb 14th mean in the title?
[myTouch 4G Android Development] ckisgen:
bob, your wife is gonna cut your marbles off...
[myTouch 4G Android Development] Vinsane:
Not sure what's going on. Getting random reboots and not sure if my 3G/4G is working. I'm trying to post on XDA and it freezes and reboots.

I can't best my own score in quadrant though :p

@1808 I get freeze
[myTouch 4G Android Development] vw671:
Any chance of boosting the headphone jack?
[myTouch 4G Android Development] faux123:
Try the slightly newer v0.3.0 BFS-SLAB version and see if you can be stable @ 1.84... Battery vs Performance is a never ending struggle :(

I haven't heard anyone complained about headphone jack's volume yet... is it too low? (are you using T-mobile's headphones? sometimes cheap headphones have crappy magnets or parts that cause the volume to be low).
[myTouch 4G Android Development] tw39515:
Newest revised faux123-Kernel-v0.3.0-slab-b

Max: 1843

Min: 1843

performance gov.

eViL-4G-Z-v.0.7.0

just had a reboot at

Max: 1843

Min: 245

on demand gov.
[myTouch 4G Android Development] faux123:
Updated version 0.3.0 BFS-SLAB version with slightly better VDD levels... download and re-install the newer version....
[myTouch 4G Android Development] tw39515:
will do. thanks

just checked was running that version.
[myTouch 4G Android Development] Vinsane:
Running new version BFS SLAB

Max 1804

Min 245

Smartass Gov

It doesnt like Interactive at that level

Is anyone having 3G/4G issues?
[myTouch 4G Android Development] bighulk666:
0.3.0b BFS-SLQB + Stock Rom

Max 1704

Min 235

Quadrant Standard

Smartass: 2350 / 2304 (after reboot)

On Demand: 2563

Interactive: 2718

Performance: 2512
[myTouch 4G Android Development] jriv:
The new kernal works great fixed lag . Great job

Sent from a guy living in a van down by the river
[myTouch 4G Android Development] faux123:
Your chip maybe borderline unstable... Try the High Voltage (HV) version and see if you are still having trouble with your Cell connection. Not all chips are created equal...:(

As an aside, the Kernel have NO control over cell radios. The radio is run and controlled by a separate chip with its own firmware.
[myTouch 4G Android Development] Vinsane:
Is the v3 bfs slab HV version updated too?
[myTouch 4G Android Development] faux123:
The voltage level on the HV version has not been changed. If your chip is borderline, you should be able to give it a try to see if it is more stable.
[myTouch 4G Android Development] XxKOLOHExX:
I love this kernel :-) would love to see it on CM7
[myTouch 4G Android Development] faux123:
Thanks for the compliment... I am more of a hands on guy and I am currently using a Sense ROM right now, so I can test my own kernel as I add more features to it.

As far as CM7 is concern, I would like to develop for it, but I only have my own phone to test and I can't afford to switch back and forth between CM7 and Sense ROM (I only have my phone as the only contact to the rest of the world :o )

Maybe 1 day when I decide to move to CM7, then I may start looking into it...
[myTouch 4G Android Development] XxKOLOHExX:
Awesome, that's cool, keep up the awesome work and thanks again :-)
[myTouch 4G Android Development] epsix:
Latest kernel slow and give low benchmark scrore and cause my phone freeze..Back to v0.03b. Keep up the good work faux123:)
[myTouch 4G Android Development] DarkNytefire:
Hm. Can't tell if there are any real performance gains our if it's just placebo...but I can tell you my battery life is stellar :) highly appreciate this kernel! Sense for the win
[myTouch 4G Android Development] faux123:
Can you be more specific? Is SLQB slow or SLAB slow?
[myTouch 4G Android Development] faux123:
Are you using SLQB or SLAB? Thanks...
[myTouch 4G Android Development] ckisgen:
just pulled down 63.4 linpack on SLQB running iced 1.1.6 on performance gov

I've been running SLQB for about a day now mostly at 1.1ghz smartass with no noticeable lag or issues.

getting ready to flash newest SLAB and test her out...
[myTouch 4G Android Development] DarkNytefire:
Using SLQB
[myTouch 4G Android Development] Vanquiz:
Thanks faux for your great kernel. Just want to give my report, using Iced Glacier 1.1.6, it seems I'm having the lag the other way around compared with the others.

I jumped from 2.3 to the latest 3.0 SLAB (Not HV) and noticing a bad lag, even though quadrant scored pretty high, wiped cache and dalvik twice, fixed permission problem still persist.

Then flashed 3.0 SLQB (Not HV), runs smooth like a butter, so I'll test this out to see the battery performance compared to 2.3.
[myTouch 4G Android Development] jriv:
I must have a ****ty chipset cause on the slab and slqb my linpack is only 50

Sent from a guy living in a van down by the river
[myTouch 4G Android Development] ckisgen:
ya on INITIAL impression of driving the SLAB since early this morning is that the SLQB seems to run better than the SLAB on mine also. I'm on Iced 1.1.6 as well. I def get a bit higher linpack and quadrant scores on SLQB. but I seem to notice a REALLY small bit of lag on SLAB when exiting back to the homescreen. there was zero on SLQB that I could detect.

unless battery life ends up being noticeably superior on SLAB I think I'll be going back to SLQB.

*on a nice side note - I managed to get a 63.7 linpack on SLQB when I switched to interactive. feel free to check me out on linpack top devices..I'm currently #10 for all Glaciers :) :) (cmk/Raleigh)

also only 0.1 under the #10 score for ALL android devices (63.8)

thanks again Faux
[myTouch 4G Android Development] Crazydaddy:
Sweet kernels man! 2.3 has been running fine, gonna try out your newest mytouch swag..... :D

Rooted/OC'd/De-bloated
[myTouch 4G Android Development] Vinsane:
For some reason...my device didn't like SLQB...maybe since its stock rom
[myTouch 4G Android Development] Crazydaddy:
SLQB took on mine. And its sitting for a few hours on standby and still at 100% battery life...so far

Rooted/OC'd/De-bloated
[myTouch 4G Android Development] faux123:
When you experienced lag...

Make sure you wipe cache and dalvik... I am trying to figure out why it is lagging for some and fine for others. I don't want to end up supporting multiple divergent kernels if I can avoid it. If you experienced lag, please give as much details as possible such as ROM version, how was it lagging, if you have task killer running etc...

BTW, this is for everyone, DO NOT use any task killers, they do all harm and does nothing to improve your performance or battery life.
[myTouch 4G Android Development] Vinsane:
Everytime I change kernels I wipe cache and dalvik.

I've tried all versions SLAB, SLQB, and the first few originals.

I tried SLQB again and it lagged my phone like crazy.

SLAB v3 (no hv) has been the most stable for me in all aspects.

Stock rom...frozen apps..adw launcher...lots of widgets..no active task killer (only manual one from System Panel App)

Thanks for all your hard work Faux! These are great!
[myTouch 4G Android Development] Onefast:
I get a little bit of lag when ever I lock with the top button. Only when I use the new SLAB or SLQB. Any other kernal it locks instantaneously. I get like a 1 second delay... Stock rom, no bloat...no setcpu
[myTouch 4G Android Development] Risky:
I really want to try this kernal but I'm on Ice Glacier 1.1.5.1 because I'm getting better 4G speeds with this over 1.1.6. Anyone know if I can? If so, can I flash this kernal and just wipe cache and dalvic or do I have to do a full wipe which I'd rather not do.
[myTouch 4G Android Development] jriv:
U can just flash over top don't need to wipe anything

Sent from a guy living in a van down by the river
[myTouch 4G Android Development] ckisgen:
the guy who made the kernel strongly recommends wiping both caches. no need for data wipe.
[myTouch 4G Android Development] faux123:
Announcement:

My theory on why some of you are lagging is due to specific application caches... You see some of the app programmers also want to improve the performance on their apps, so they cache parts of their code to shorten the loading time... Unfortunately, the cache depends on the memory architecture of the kernel, so when the underlining kernel change the way memory is allocated, the previously cached components are now in conflict with the new kernel thus causing lag... But this is ONLY MY THEORY... To help me prove this, if you experienced lag, please download Cache Cleaner NG from here or search in market.

Once installed, open the program and make sure SD option is checked, then select clean now... Once it completes the cleaning of application caches, reboot the phone and see if the lag goes away... If not... post it here to help me isolate the issue...

Thanks for the participation...
[myTouch 4G Android Development] Vinsane:
Funny. I had that app already.

I cleared cache before flashing new kernels each time...and still had the lag with SLQB
[myTouch 4G Android Development] Marine6680:
ROM Manager allows you to flash the latest recovery by default now. I went to flash IG and this Kernel, but I noticed the orange text. So be aware of that if your rooting a new device.
[myTouch 4G Android Development] :
Using bfs 0.3 slqb works great low quadrant but makes up for real user experience
[myTouch 4G Android Development] Vinsane:
2 days in feedback using SLAB v3 non hv

Everything had been smooth until 2 hic-ups.

Last night...during heavy usage...lots of downloads..the phone lagged badly. To.the point where I had to reboot. After reboot, everything was fine again.

Same thing today...heavy morning use (being online and using various apps)..it lagged badly again. Tried to do a clean cache via app...no dice.

Needed a reboot.

Current settings are:

Max 1335

Min 245

Smartass gov

Stock rom..rooted..frozen apps..adw launcher..honeycomb live wallpaper...multiple widgets.
[myTouch 4G Android Development] faux123:
Thanks, this is VERY USEFUL information for me... It maybe related to the new I/O Scheduler I chose for this beta. The "No OP" I/O scheduler is extremely simple and supposedly recommended for FLASH type devices because it HAS NO advanced queuing or latency hiding techniques needed for FLASH type devices. Based on your report, it seemed with too much I/O accesses, the simple "No OP" I/O scheduler is overwhelmed...

With my Kernel, I have INCLUDED ALL 3 different types of I/O schedulers in the Kernel itself, so you can CHANGE the I/O scheduler on the fly with the following commands using terminal emulator to switch from "noop" to "deadline"

su

echo deadline > /sys/block/mmcblk0/queue/scheduler

(This will only persist per power up, so if you reboot/restart/shutdown, the next power-up will still default to "noop")

Please give it a shot and try to do some HEAVY multi-tasking as you did and see if the lag still persist... Thank you very much....

For everyone else who experienced lag:

The above was a very good example on how to report issues to help me trouble shoot problems :D
[myTouch 4G Android Development] Vinsane:
Should I be getting any kind of response prompt from terminal once I input that command line?

I'm only getting # again
[myTouch 4G Android Development] faux123:
no, unfortunately there no feedback from issuing these commands. Issuing these commands are completely safe, no harm will be done to the system if messed up...

I am @ work right now... When I get back tonight, I will release version 0.3.1 beta with "deadline" I/O scheduler set as default to see if lag still persists...

Geek talk below:

It seemed that Android is doing something I don't quite understanding when it comes to I/O handling... I am going to read up on this subject....

From most Linux Kernel literatures I've read, many have claimed that SSD/FLASH devices DO NOT have Disk Access/Mechanical latencies, so simple I/O scheduler should work better than all other types of I/O schedulers designed to minimize/hide the mechanical latencies of hard drives... Maybe the type of MMC/SD card controller / device driver is doing something different from my thinking....
[myTouch 4G Android Development] eliasadrian:
Using version 0.3.0b BFS SLQB for a couple days now, no issues or problems.

The first 5-15 minutes after flashing it was a bit laggy, I think it was cuz I got a replacement phone and this was the first kernel flash. I did it on Clockwork 2.5.1.2 and wiped both caches, flashed grankin's kernel first, got stuck at bootup, pulled battery, then flashed v.0.3.0b-BFS-SLQB, fixed permissions and it worked fine. I had been using Faux123's kernels on previous mytouch4g, they're great, thanks!

-Stock ROM, debloated, ADW Launcher, SetCPU for O/C 1209 max (about 45 on linpack, 1850 on Quadrant 1st and 2nd but 2100 3rd try)
[myTouch 4G Android Development] negreenfield:
Running version 0.3.0b BFS-SLQB.

So far so good. Runs smooth and fast. I've been having some issues with Bluetooth and my Kensington Liquidaux on some of your older versions, so then I went back to IG 1.1.6 with the kernel that it comes with and saw the same issues so I'm going to test some more probably tomorrow to see if it's an IG thing. If so I may try the stock ROM by itself for a few days, then add your kernel to that. I don't remember having any issues with the stock ROM and my Liquidaux but it's been a while since I've been on the stock ROM so maybe not. I also don't have any controlled setups I did so troubleshooting is difficult.

Anyway, I'll report back when I get more testing done but so far so good.
[myTouch 4G Android Development] faux123:
I did not update/change the bluetooth driver from HTC in my kernels...

HTC Bluetooth drivers have some known issues, one of them being NOT compatible with Wii-mote for use with emulators, and I am sure there are many others...

Problem, when updating the existing HTC bluetooth driver, is that any change to it MAY BREAK HTC Sense compatibility.... So in order to keep my kernels 100% Sense Compatible (including all the Sense flaws), some of these issues will be whatever they are until HTC upgrade their OWN SOURCE CODE first... :(
[myTouch 4G Android Development] negreenfield:
Thanks for that info. That should help my testing. My Liquidaux works well most of the time but obviously it's another variable itself so getting down to the bottom of the issues with so many variables may be impossible. It works 90% of the time (almost 100% for music, probably 75% for using with calling) and it all could just be the product itself. I also use a different car home app so I don't know what affect it has as well.

Anyway, I'm glad you're working hard on a kernel for Sense-based ROMs. I tried out CM7 and it was nice but still prefer Sense over anything else.
[myTouch 4G Android Development] faux123:
For everyone else who experienced lag (with either SLQB or SLAB versions):

With my Kernel, I have INCLUDED ALL 3 different types of I/O schedulers in the Kernel itself, so you can CHANGE the I/O scheduler on the fly with the following commands using terminal emulator to switch from "noop" to "deadline"

su

echo deadline > /sys/block/mmcblk0/queue/scheduler

cat /sys/block/*/queue/scheduler

you should see:

noop [deadline] cfq

if deadline is within the square brackets, you have successfully switched I/O scheduler from noop to deadline.

These commands are SAFE, won't brick your phone if messed up...

(This will only persist per power up, so if you reboot/restart/shutdown, the next power-up will still default to "noop")

Please give it a shot and try to do some HEAVY multi-tasking as you did and see if the lag still persist... Thank you very much....
[myTouch 4G Android Development] DarkNytefire:
Sorry if this is an extreme newb question but how do I swap between the governors? Or rather, is there anything I should be doing after flash to make sure that I'm going to get the absolute best battery life from this kernel?
[myTouch 4G Android Development] Vinsane:
Use SetCPU app to change the gov

Once you flash the new kernel...open up setcpu and it defaults to smartass...you can change it from there.
[myTouch 4G Android Development] DarkNytefire:
Highly appreciated.
[myTouch 4G Android Development] Marine6680:
Are the betas running pretty well?

Also, I have been getting an error message when wiping dalvik.

Can't mount /dev/block/mmcblk1p2

Been doing that for a while now.
[myTouch 4G Android Development] ckisgen:
I get same error...

however my SLQB kernel is running very smooth so far. I was still at 51% last night after over 20 hours off the charger. I would say I was JUST on the lighter side of medium usage (for me) ... 20 mins of phone calls, screen on 2 hours total..several texts and emails, etc.

was at 1.2ghz max / 245hz min / smartass gov (no profiles)
[myTouch 4G Android Development] faux123:
This means your SD card is not setup properly or the sd-ext partition (used for running apps from sd) is either corrupted or missing. The only way to fix it is to re-partition your SD card but doing so will erase all your data. Android can run apps from SD a couple of ways, so a bad sd-ext partition is not fatal just annoying.

For everyone:

How's the new updated beta going? Are there still lags or have they disappeared... please leave feedback... thanks
[myTouch 4G Android Development] Crazydaddy:
Just installed version 0.3.1b BFS-SLQB. I never really run mine at more than 1.5, I just like having something a bit faster if needed..... Seems nice and stable, battery life seems good too. Only thing I noticed is if you pull up the info tab on setcpu, it shows your kerner version but still at v0.3.0 instead of 3.1b.