yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Yep... I've got some experimental code though for the GPS that I am working on but the config is not changed. However for compiling NBH's I have changed tinboot.S as it is not up-to-date.

Check my NBH's or DZO's NBH's with a hexeditor and look for the kernel parameters and update your tinboot.S.
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
yeah, I already did that.

having issues with missing clk parameters or something like that during zImage compile...

still looking into that.

although I successfully built an NBH using the zImage 29-04-10 from DZO

(I forgot to add the hw3d in tinboot... but it doesn't seem to make much difference)
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
There's a consistent problem I've been having with the GPS, and it's with iGo. The GPS locks up shortly after starting iGO. Though, it won't lock up when I use Nav. When I force close iGO, the GPS icon is still visible and starting up Nav will freeze as well. Only restarting the phone will unfreeze the GPS device.

Has anyone experienced this with iGO?
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Yes, I've had this issue with c:geo (a geocaching software) which when moving through different parts of the program switches the GPS off and on quickly. I've made changes to the code and I haven't had the issue since. But it's still to early to be sure I really fixed the problem. I'll post

I've attached an experimental version. It has some other experimental changes. It should work fine though.

Please let me know if it helped with the problem you have with iGO. At least for me it's sort of random when it happens so it's hard to know if it's fixed or not.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Thanks kallt_kaffe I gave it a try. I gave it two attempts.

First, when I tried it I was entering in the address and someone called me. At that point all I saw was a black screen.

Restarted phone and tried again, this time nobody called me and before I could enter the street name, it froze.

The problem looks like the GPS hogs a lot of attention away from the CPU. Like an infinite loop that gets worse. Even when I force close iGO, it's like the phone is still running really slow.

BTW, if anyone knows how to convert iGO to fit a 240X320 screen please explain how. I know there's a way, but nobody ever explained it. Running 320X480 really slows down my Kaiser.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I got the problem once yesterday myself but I have some other ideas that will try.

What happens if you just change LCD density to 106 or 100 (in 240x320 res)?
[Tilt, TyTN II, MDA Vario III Android Development] jfg69:
I wasnt having too many performance issues with the 480, just the GPS issue really. Either way, it all looks small to me as I'm blind as a bat when it comes to small stuff! A 20" screen would be nice for me.. :)

Maybe I'll try your radio too..
[Tilt, TyTN II, MDA Vario III Android Development] DoraMia:
Does anyone else have odd green pixels appearing? This is my first experience with Android, and I have fallen in love, but the graphics seem to be edged with neon green dots. I'm using this build (downloaded two hours ago) and the instructions in the sticky-ed thread.
[Tilt, TyTN II, MDA Vario III Android Development] jfg69:
Try a different panel. That worked for me in the past.
[Tilt, TyTN II, MDA Vario III Android Development] DoraMia:
Brilliant. USA ATT stamped kaiser, Panel 2 worked fine.

I might be in love.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Try the attached version. I've added a 0.5 second delay before enabling the GPS in case it is quick disable/enable of the GPS that causes the trouble.

EDIT: This didn't help me. I still got the "issue" today when running c:geo.
[Tilt, TyTN II, MDA Vario III Android Development] jfg69:
Back to running your latest, seems pretty good. I was able to get GPS lock after installing GPS Test, for some reason maps wasnt grabbing it. After that, Maps and Waze were both fine. I'll play more today. (Running with WarmDonut, a beta for Kaiser)

Only thing I did different than most was to hexedit battery back to 1350 from 2700, not sure what that does or doesn't do, but since that's my battery capacity, it should give me a correct reading I would think, yes?..
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
I haven't had the chance to test out your new rom today, but I was wondering if you could answer some questions about the kernel.

Does DZO still work on the kaiser kernel? Is the graphics driver based on the G1's? Is there any code for ext3 or ext4 support?
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Well, I finally got iGo working again (thanks to pasks), and this time at 240X320.

When I first ran, it would never get the GPS connected. So, much like Windows Mobile, I ran GPS Test first and then ran iGo. It didn't freeze, and when I shut off the application, so did the GPS.

The only problem is that iGo runs slow, but that's not kernal related. In fact, might be "Incubus26Jc's Super Eclair Lite 2.1 [RLS 5]". When I ran "mssmison CyanogenMod 5.07 test 3" iGo ran very fast, even at 320X480. Haven't had the chance to try "Incubus26Jc's Super Hero 2.1 [RLS1]" with iGo, for all I know it runs just as fast or faster then CyanogenMod 5.07 test 3.

I might try reinstalling CyanogenMod 5.07 test 3 or Myn’s Warm Donut. See if there's a difference with GPS stability.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Just tried iGO with kallt_kaffe's most recent kernel on Myn’s Warm Donut, and it's fast. No freezes, no slow downs, no problems. Something is wrong with Incubus26Jc's Super Eclair Lite 2.1 [RLS 5] to cause such a massive slow down in iGO.

Otherwise, latest kernel works far better for me.
[Tilt, TyTN II, MDA Vario III Android Development] muscles:
I am running the following:

Device: AT&T HTC Kaiser Tilt - currently on SD but want to run NAND once I get everything I need working.

Radio: 1.71.09.01

Rom: Myn's Warm Donut (RLS 5)

I use the GPS for an app called SportyPal to track my running. I also want to use the Google Maps Navigation feature. The app will get a GPS lock and work for a few minutes. However, shortly after it either loses the GPS or locks the phone up.

I posted this in the Warm Donut Kaiser thread and was directed here. I have read everything on this thread, but it is still not sinking in. I have downloaded the custom_kernal.zip and i.Hex. Since I am running HARET, I tried to edit the zImage file, but cannot find the lines needing to be changed. Can someone help me out?

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
you only need to hexedit if you are changing values in the nbh for flashing to nand.

for haret, all the parameters are in the default.txt

you don't edit the zImage.
[Tilt, TyTN II, MDA Vario III Android Development] muscles:
Got it... Much thanks!!!
[Tilt, TyTN II, MDA Vario III Android Development] muscles:
All I have to do is replace the current zImage file?
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Yes, that's all you need to do.
[Tilt, TyTN II, MDA Vario III Android Development] czar_au:
Is there a way to tell without re-installing which kernel I have installed on the phone. I am sure I have already installed this, but I still get GPS lockups. About Phone -> Kernel Version says "2.6.25-hiapk www.HiAPK.com #144"
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Today, with this kernel, I gave the GPS a good test drive. I used iGO, and after about 10 minutes driving down the road it froze up the GPS and the application. After shutting down my phone I had to yank the batter, otherwise starting the phone again would not allow me to use the GPS. Second time it lasted for 30 minutes and I made it to my destination. On the way back home it locked up within 3 minutes of turning it on.

It does still freeze. Just not as soon as I start iGO.
[Tilt, TyTN II, MDA Vario III Android Development] jfg69:
Have you tried this with a different app than iGo? I have been using Waze, open source map app. I havent had a chance to use it this week since I loaded this nbh. I will try it over the w/e.
[Tilt, TyTN II, MDA Vario III Android Development] muscles:
I just got back from a run and tried to use the GPS with SportyPal. It locked almost immediately.
[Tilt, TyTN II, MDA Vario III Android Development] highcoder:
I use Navigon Mobile Navigator 2.5.1 an have the same problem that Dukenukemx have.

It works fine (better than in WiMo) for about 20-30 minutes. Then GPS signal got lost but the symbol in the statusbar is still alive (not blinking). If you want to turn off GPS nothing happens. It seems that the whole GPS thing freezes. If you want to exit Navigon an error occours. Only a full shutdown solve this problem. ...for the next 30 minutes... :-)
[Tilt, TyTN II, MDA Vario III Android Development] czar_au:
Glad I'm not the only one. Google Nav, Co-Pilot, iGo all lock up :-(
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Post new version in first post. Kaiser Camera is now working in Donut builds again. However only for NAND users, but it is possible that replacing the initrd.gz (make a backup first) in \andboot with this one: http://androidhtc.git.sourceforge.n...dcd6ec6105d9fc7ec325b89398c89b2b94afe;hb=HEAD may make it work also for HaRET users (not tested)
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Before kallt_kaffe's new kernel in the post above (which I haven't tried), I got different results today driving the same destination. Today I drove to the same destination as in my previous post, but iGO never froze. Both there and back it didn't freeze.

The difference is that today was a clear day, with no clouds. Before, it was a cloudy day, and I had a hard time getting a signal with my GPS. Enough that I had GPS Test on the whole time, hoping that it would connect while I drove.

I'm thinking that when the GPS signal is low, it could freeze the GPS, but with a good signal it won't. Just an observation.

**EDIT**

BTW, tried the new kernel and exiting camera locks up the phone. Using Myn's Donut.

Also, the version of iGO that I use is iGOMyWay 8.4.2.124036.

**EDIT**

Tried out kallt_kaffe's new kernel and so far it's fast! Haven't tried GPS or anything, but a lot of things are running faster. The menu from the kernel is slower, but everything gets stuff done quicker. Fix Permissions is faster as well as anything file transfer related. This includes installing things from the market.
[Tilt, TyTN II, MDA Vario III Android Development] aqtrans:
With the newest kernel, I can't use the Recovery Mode option in the installer menu. According to the messages, the USB keeps getting reset, so it goes Offline>Online, Online>Offline over and over.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Was using GPS today with the new kernel and it froze. Clear sky and everything. Guess it's not based on signal quality.
[Tilt, TyTN II, MDA Vario III Android Development] highcoder:
The same here. Freeze after 5 minutes... :-/
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
For me it was 30 minutes. It's random when it happens. Though, I know getting a phone call while the GPS is on will totally freeze the phone when I hang up. :p
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Does it really freeze the phone or is it just the GPS application that stops responding? Try pressing the "home" button once (Internet explorer button). Wait a while and see if it returns to the launcher. The GPS icon can be either off, on or flashing but the symptoms are the same. Every GPS application that is started "hangs" but the phone does not freeze completely.

That is what I get sometimes and I'm not sure what is causing it but I will try to find out.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Oh, and if you are really sure that the phone is has frozen completely, after reboot check /proc/last_kmsg (you can copy it to the sdcard with "cp proc/last_kmsg /sdcard/last_kmsg.txt")and post the last part of it. There should be some sort of kernel panic in the end of it.

And if it is just an application hang, press home button, open a terminal and type something like "cat /proc/kmsg > /sdcard/kmsg.txt". You'll have to ctrl+c this command after a while. (middle button("ball") + c). Search for the last part where you see any life signs from the GPS (NMEA read ...) and post something like 25 lines before and 25 lines after the last GPS life sign.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Thanks, I'll remember to do that next time.

I've mashed the home button and waited for 10 minutes. Just a black screen on my phone. Could be an iGO issues itself. Don't see many people using it, but kinda have too since I don't have a data connection.

Also, would you happen to know why actions are delayed on Android? What causes it?
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New version in first post based on new code from DZO. It's camera improvements so unless you are running a Donut build there is no need to upgrade.

I've also done some changes to the GPS logging so that it would be easier to follow when libgps tries to turn off and on the GPS. This is for troubleshooting a problem that sometimes occur where the GPS access seems to become blocked leaving any software accessing the GPS in a hanged state. I'm not sure what is causing it and I'm not convinced that the problem lies in the kernel.
[Tilt, TyTN II, MDA Vario III Android Development] xPreSiDenT:
Thanks for the great work man... but this release and the last one gave me some problems. The touch screen alignment became a bit erratic. a simple tap causes scrolling and its hard to select things. Going back to the release before that. Hope you can find out the reason for this...
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Nice work. I must have flashed like 10 times this week with Android roms, and Myn's Donut works the best for me. So this will help greatly.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I have the same problems. DZO have done things to the touchscreen code in order to increase the sensitivity but it seems he overdone it a bit. I've asked in the kernel development thread how we could tune this down a bit but I have not yet recieved an answer.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
It does seem a bit inaccurate. I have a difficult time pulling down the status info bar from the top of the screen.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
If you are using the pen it usually works fine for me but if you try to use the finger things like that is close to impossible. It seems to me that there should be some sort of time before a "tap" is treated as a "slide" but that time seems to be extremely low or non existant.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
My finger does make it impossible, plus some taps are off. I'm sure I tapped the right spot, but it thinks I hit some other spot.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Try the attached version. Seems to have fixed the touchscreen problem. I've also done some changes to the GPS code that might improve stability so please let me know if anything got better (or worse).

EDIT: Oh, and I also filtered out the untracked sats so that they are not displayed in, for example "GPS Test". Untracked sats are those with signal level "00" which means the GPS know they should be in view but can't see them. If you really want them back add the board-kaiser-gps.show_untracked=1 to your kernel parameters.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I have no idea where to look for cell-tower location really. A-GPS is not the same thing. A-GPS can speed up time-to-first-fix and provide correction data to the GPS if understand it correctly. I have identified how the rpc-commands change when you enable A-GPS in WinMo but I doubt it would work even if I sent a valid A-GPS IP and port to it. Somehow it needs to communicate with TCP/IP so I suppose there must be some interaction with the operating system for it to work. I doubt it is worth the gain.

My main goal is to make the GPS 100% stable, there is still room for improvement. My second goal is to find a way to disable the static navigation. From what I've seen dumping rpc commands in WinMo it isn't even possible to get rid of it completely in WinMo but I can believe that someone designed a chip that is hardcoded to behave like this chip does.

If you don't know what static navigation means. Fire up GPS Test. Get a fix (a GPS fix). Walk under a clear sky and use the speed and bearing page in GPS Test. As long as you keep moving speed and bearing updates every second. Stop, stand still for 30 seconds or more. Start walking again. It will take 10-15 meters before speed and bearing starts updating again. That's "car mode" or "static navigation". Good for car navigation, useless for everything else.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Using the latest kernel, I had no problems today using the GPS. No problems with anything really. Even got a phone call with the GPS on and nothing froze up.

Strangely, the phone is working extremely fast. Everything is responsive and running fast. With some settings tweaked, my battery life is normal as well.
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
Thanks...that touchscreen problem was getting to be a bit annoying.

glad your still including the nostart param too...(lifesaver)

I am getting same results.... zippy... :)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New version in first post.

- Includes the touchscreen fix

- GPS accuracy is now using a simple HEPE (Horizontal Estimated Position Error) instead of showing the PDOP.

- GPS should no longer incorrectly tell Android that the fix is lost when it is not.

- No longer showing untracked sats, can be enabled with kernel parameter if you really want to see them. (board-kaiser-gps.show_untracked=1 turns them back on)

- Compatible with loserskaters NBH Editor.
[Tilt, TyTN II, MDA Vario III Android Development] mt1976:
Thanks kallt_kaffe for the new Kernel, all is working well including the touchscreen and GPS :D
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Gonna test this today.
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
TH for Polaris users

Thanks to make a NBH also for Polaris. I will try this now...

Cheers.:)
[Tilt, TyTN II, MDA Vario III Android Development] Millence:
Testing new kernels for more than 24 hours now. Everything works a little faster and a little smoother. Touch screen work great! No time for real test of GPS but I will test it today.

And there is one 'side effect'. With this kernel my phone is working on 550Mhz stable! last time I tested, with DZO's 08.04 nbh I think, everything above 500Mhz freezes the phone. Now is running stable on 550Mhz more then 24H!

Same phone, same build different kernel!

These new kernels have something to do with overclocking?
[Tilt, TyTN II, MDA Vario III Android Development] deezy7:
Hi kallt_kaffe et al,

Okay, I have a total nooby noob request here. I think you and the rest of the developers are doing some truly awesome work here! But I need some help with getting these fixes (gps, battery, and touchscreen) onto my kaiser! I have the Tytn II version (non-Tilt), and I am totally perplexed as to how to get your nbh flashed onto it. I mean, I know how to do it, but what I'm having troubles with is transforming your tilt-nbh into a kaiser-nbh.

I'm sitting here with two i.Hex windows open, one with dzo's panel2-kaiser.nbh from 19-05-10, and one is your new one. I can see the differences straight away, but how do I add your battery fix text into dzo's nbh? OR, would it kindly be possible to make a kaiser version? :D I fear screwing up the hex and messing up my phone :(

Any help would be greatly appreciated! Thanks!

[EDIT] kallt_kaffe + loserskater = AWESOME! That was SO EASY. Thanks guys!!! :)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Tilt, Tytn II (like mine) and all the other variants are all Kaisers. DZO's non-tilt NBH means that the tilt parameter is 0, Tilt users have it set to 1, I have it set ti 2 (nordic keyboard). A more proper name for the tilt parameter would be "keymap" but and that's all it controls. It controls wether you have a tilt or a non-tilt keymap. It has now been extended to support more keymaps but for compability reasons the "tilt" parameter name has been kept.

Short answer, use a hex-editor and change the tilt parameter to 0 and the panel type to 2 and you are good to go.
[Tilt, TyTN II, MDA Vario III Android Development] deezy7:
Ooooh I see I see...I could have just done that!!! lol See, what I really needed your nbh for was that battery parameter, which DZO's nbh does not have, or at least, the version I downloaded from May 19 did not have. When I was comparing it to your nbh, I couldn't figure out how to actually ADD that parameter!!

But that problem has now been SOLVED with loserskater's nifty little NBH Editor :D :D :D After running your nbh through it, I now have the parameter for the panel set to 2 already, and the keymap to a non-tilt, AND your parameter for the battery already added, and I changed it to 2000. Just flashed, so I'm gonna see if my battery indicator is more accurate now, and hopefully I see the gps and touchscreen improvements too!

Thanks again kalt!
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
That is a pretty massive overclock. My question is, how's the battery life at that clock speed? Can I set certain applications to run at 500+ Mhz, but back down to 400Mhz for saving battery power?
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
I'd just like to say thank you for the work you do on this thread Kallt_kaffe, it's really handy and much appreciated :)
[Tilt, TyTN II, MDA Vario III Android Development] Badgerfan:
Having some issues with the latest nbh. I've tried changing the panel to panel 3 using Loser's NBH editor and iHex, but am still getting a white screen at boot. I used kallt_kaffe's NBH from 27th and edited the panel and it worked fine, so not sure what's going wrong this time...Now using dzo's NBH from 28th.

P.S. Kallt_kaffe & DZO - you're both awesome.
[Tilt, TyTN II, MDA Vario III Android Development] aruna1975:
fixed touch screen issue on my Tilt

kallt_kaffe,

Thanks, after updating .nbh it fixed by touch screen issues.

Thanks again
[Tilt, TyTN II, MDA Vario III Android Development] jfg69:
Weird problem.. edited the latest nbh using the editor. Flashed it and all was good, except that I had to redo my Gmail settings and I lost all my call logs etc, no biggie..

Been using it most of the day. Made calls, used camera, texted. All ok. A few minutes ago, I tried the videocam, which didnt work. Pic came up etc, but no recording, which I expected.

Switched back to camera and was trying to get a pic of my dog as he was playing.. screen went black (after waiting about 20-30 sec's for a good pose,) phone rebooted, and now keeps booting into a loop. It runs the first screen, then all the linux commands scroll by and then the Android screen comes up while waiting for the OS to load.. and it crashes and goes back to the first start up screen again, continuously.

I pulled the battery and restarted, same thing..

Gonna reflash the NBH and see what happens.. Meanwhile, any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I don't think it's kernel related. Are you running a tattoo build. I sometimes lost my settings and even got filesystem corruption with the tattoo build. My feeling was that it powered off to fast compared to other builds. Might be some write cache thing that isn't flushed when powered off that causes loss of settings and file system corruption.

You propably need to reinstall Android.