yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] stumps:
Hi kallt_kaffe,

can you think of any reason why the latest kernel (23-06-2010) causes kaiser panel to go totally white after bringing the device from sleep? ... boot process is Ok and everything's fine until the device switches off the screen. I tried several values for the "pm.sleep_mode" in my startup.txt but with no success. Last 6 months I haven't had any such issues ...

P.S.: Currently running off ext2 parititioned SD card + haret.exe + pm.sleep_mode=1 + rogue tools overclock to 526MHz + 120 dpi
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Try different panel settings in your default.txt/startup.txt
[Tilt, TyTN II, MDA Vario III Android Development] stumps:
many 10x kallt_kaffe!

just for other user's reference: I changed "board-htckaiser.panel_type" from 0 to 3 and now graphics quality is perfect as it was before. There's only a short white screen when bringing the device from sleep (not an issue at all though never had this before with board-htckaiser.panel_type=0).
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Actually there is no such thing as panel 0, that value is used for autodetection in the Vogue and we don't have autodetection on the Kaiser so 0 should never be used.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
My Kaiser's bluetooth doesn't seem to be turning on with the latest kernel, is it just mine??
[Tilt, TyTN II, MDA Vario III Android Development] Woodham:
Odd behaviour with this latest kernel. The I.E key doesn't seem to do anything (usually the "home" key ) and when my kaiser wakes up it doesn't show the slide to unlock screen any more.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Are you sure you didn't accidently flash a Vogue NBH? Or changed it to Polaris or Vogue with the NBH Editor? I'm using this kernel and I have no such problems. Have you tried just restarting the phone?
[Tilt, TyTN II, MDA Vario III Android Development] Woodham:
Double checked settings (set them in editor and checked them in hex), reflashed and reset, same stuff. Panel type 3, kaiser, 320, not oc'd, myns warm eclair.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
You could try using a hexeditor on the original Kaiser NBH to be absolutely sure that it is not the NBH Editor that sets up the wrong MTYPE. I'm using the Kaiser NBH as it is since I compile it directly with my own settings so I do not use the editor.

There is of course also a possibility that something has gone bad in your Android install. If you are on NAND you could do a SD card install without destroying your NAND install just to see if it makes a difference.

In fact, just clearing the dalvik cache may help.
[Tilt, TyTN II, MDA Vario III Android Development] Woodham:
=(, think it must be my android install went cuckoo after flashing. Tried reverting to 22nd's one but didn't help, tried clearing dalvik cache didn't help. I'll just reinstall I guess.
[Tilt, TyTN II, MDA Vario III Android Development] dadevil666:
Hi, i have a problem the couple of the last releases i have this problem whenever the phone goes to sleep after that i can't see the screen its just all white previous versions work btw im using zImage :)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
http://xdaforums.com/showpost.php?p=6911677&postcount=217
[Tilt, TyTN II, MDA Vario III Android Development] loserskater:
This has happened to me a couple of times. I think something gets tweaked the wrong way in the system. It might be an app. The only real solution I've found is to reinstall and clear data.
[Tilt, TyTN II, MDA Vario III Android Development] mmec2:
I've noticed some strange behaviour:

my kaiser now turns itself on if I try to charge it turned off - the orange light comes on for a while as usual then turns off, and after about a minute the home screen appears with a notification sound

It seems that it turns itself on as soon as it is plugged in, but only turns on the screen when it finishes booting
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
That is now normal behaviour, due to recent kernel changes to the way charging while powered off is handled, previously it would power on the led, and stop charging when the led turned off, this change allows the phone to charge more or less normally.
[Tilt, TyTN II, MDA Vario III Android Development] loserskater:
Is there any way you (or anybody) can make a kernel with commit 8e6f6a0bf80001249a810fba12e4cb7dbddae1b0

removed? I think it's causing problems on my kaiser... But I want to test to make sure. Ever since that commit, or maybe the one directly before it, I get THIS on boot.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Interesting, had a few issues with sleep recently and wondered if it was the recent RLS6 eclair release, but since I also upgraded kernel at the same time that may explain it, can't compile another, but I will try an older kernel to check anyway.
[Tilt, TyTN II, MDA Vario III Android Development] artex92:
@Zenity- I saw sleep issues too. It's kernel problem (I've updated it today and Kaisy get dizzy ^^")
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
At the moment the kernels in this thread are newer than the official ones because a Kaiser specific BT headset problem was fixed on the 29th but new official kernels has not yet been compiled. So get the ones from the first post if you need BT phonecalls to work and you don't wait for new official NBH's.
[Tilt, TyTN II, MDA Vario III Android Development] sda2:
Hi KK! First thanks for your work!

I have some issues with the newest versions of your NBHs.

My Kaiser turns off randomly with ANY build I use and the boot sometimes gets stuck after the first splash logo.

Do you have any idea how i could fix it?

Thanks in advance!
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Does the official NBH's from dzo have the same problem?
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Just a shameless 'bump' to move this thread to page one..

I just happen to think it needs to be there, ( or sticky ... hint hint ) :D
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
I agree, GPS is one of the more stable things in the android kernel i think, but at the same time it would be great if we could just polish it off by getting a quickGPS type system going which got satellite data from the web to help it get a fix. That would then be case closed on GPS for kaiser android!!!
[Tilt, TyTN II, MDA Vario III Android Development] ch604:
i seem to be having trouble getting a gps lock with this kernel... i can open up gps test and see plenty of sattelites, along with fair signals, but none of the bars ever change away from grey. theres also no way for me to see my location in google maps. is there something that i'm forgetting to do? please advise!

running myn's warm donut rls5 with most recent kernel from front page, flashed this morning. i was using myo's kernels, but with the same result. :confused:
[Tilt, TyTN II, MDA Vario III Android Development] GuySparkz:
which android kernel are people using? what is the significant difference of each? im using "kaisimg-panel2-320-tilt-froyo-26-07-10.nbh" is this recommended?

i had problems with the battery not charging properly and staying at 15% and then randomly freezing and restarting. ANY FIX???

im still using hardSPL 3.29 i cant get 3.34 to install properly...
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Ok, without information there can be no answers, you have not given sufficient data with which to make a diagnosis, however there are many threads on battery issues, please feel free to read a few of them.
[Tilt, TyTN II, MDA Vario III Android Development] noonas:
Hi there!

I have downloaded the Kaiser nbh file and edited it in atools (1.3.0) , setting the keyboard to Nordic (using Froyo kernel), does not help, how do I get the nordic keyboard mapp installed??
[Tilt, TyTN II, MDA Vario III Android Development] faraon7:
SD cart apps

That is the best kernel for me. I have amazing battery life with this kernel, only problem is that APP2SD not work. I try with link2sd and other without sucsess.

I get error message "Failed to move application".

1. Camera works

2. Gps work

3. WiFi work (with update)

4 everything is perfect exept app2sd. For me is the big problem for unfortunaltely.

If somebody have a solution. Please share:p
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Try the attached NBH and let me know if it works. I haven't got time to try it myself so I don't want to added to the first post until it has been tested.
[Tilt, TyTN II, MDA Vario III Android Development] voyteckst:
Thanks, I will try it later.
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
Same effect : no boot at all...

I think now it's the DZO's version of kernel who doesn't work for us !

Now we have to wait the DZO holyday's return...

Cheers :)
[Tilt, TyTN II, MDA Vario III Android Development] cXhristian:
Hi! Thank you so much for this!

I am Norwegian so this is perfect for me. Or well.. almost perfect.

I have some problems, so if you could make me a little custom kernel I would be really happy.

The keyboard mapping is perfect except for

Up arrow: Å (Does nothing right now)

Left arrow: Æ (; now)

Down arrow: Ø (Does nothing right now)

So if you could change those or tell me a way to change those it would be really nice of you. ;)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Sorry, can't fix that, just as I cannot fix ÄÅ. This is as good as it get. Hold down A for Å and Æ and hold down O for Ø. Trust me, I've tried... I'm sure it is not impossible but it would require a lot more changes in the kernel code than just a remapped keymap array.
[Tilt, TyTN II, MDA Vario III Android Development] cXhristian:
Ah, okey.

This is still very useful for me, I guess Ill just have to get used to pressing A and O. :)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New NBH and zImage for Kaiser in first post. Fixes the phone freezing when starting up GPS applications. This ONLY fix the freeze you sometimes get when a software enables or disables the GPS. It can still freeze while using the GPS, at least it does that for me.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New version that is up to date with the latest code from DZO.

I've also modified parts of the Kaiser GPS code and the NMEA parser and I'm experience a lot less GPS freezes than before. It's not 100% stable but at least for me it's a noticable improvement.
[Tilt, TyTN II, MDA Vario III Android Development] robuser007:
There are new improvements today.
[Tilt, TyTN II, MDA Vario III Android Development] xPreSiDenT:
Hi! thanks for the great work! Can you post an nbh with the regular english(non tilt) keyboard for donut? I'd really love to have a more stable GPS, and I dont know anything about hex editing. I'll try and learn on the weekend but If you can make one before then I'll be really thankful.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Just try i.Hex. It's not hard at all. Scroll down until you see the parameters in the rightmost column.

Click on the character you want to change and change it. Save when you are finished.

Change hw3d.version to 0 (for donut) and change attilt to 0 to get the correct keymap. You also may need to change the panel to whatever you usually use.

You do not need to understand hexadecimal to do it as you can edit in the ASCII column.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
'

Here's a screen shot on i.Hex and the parameters you (may) need to change.
[Tilt, TyTN II, MDA Vario III Android Development] xPreSiDenT:
Great! thanks a lot for the explanation. Will try this out as soon as I find some time. BTW what kernel is this based on? I tried the latest eclair kernels with donut, and everything was pretty good, apart from the gprs not working so I reverted to the donut kernels. Could I apply the GPS code to the donut nbhs if the need arises? It must be a copy paste job in the hex editor right or would it be more complicated?
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
The ONLY difference between donut and eclair NBH's are the hw3d.version parameter. Change it to 0 and it IS a donut NBH.

This is based on the latest code from DZO except it lacks the latest code where he added something that was supposed to help against resets when trying to use the camera. However it didn't seem to solve the issue so I haven't bothered to update it.

You cannot add my experimental GPS code to another NBH, changing parameters is one thing. Change code is a whole different matter.

I have not tried my GPS code on donut yet but it should work just the same. It will still freeze sometimes but it's more like 1-2 freezes/day instead of 3-4 freezes/hour.
[Tilt, TyTN II, MDA Vario III Android Development] Dark-Side:
I tested your new nbh on my kais130. GPS no more freezing on it. Good work ! Thanks

Rom: Incubus26Jc's Super Éclair 2.1-Update1 - [RLS 1]

NBH mods for 240x320,Panel 2, azerty, éclair hw3d, system@128Mo, Data@86Mo, no overclock

Wifi update for kaiser
[Tilt, TyTN II, MDA Vario III Android Development] robuser007:
I have a freez while using gps.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
As I said before it will still freeze but not as often as before. Every time the code reads NMEA data from the GPS a kernel panic can occur. I don't know why and I haven't managed to stop it. Basicly what I have done is that I've changed the code to read NMEA data less often but more data at each time. There is now a 0.5 second delay to a loop that before was continously trying to read data. This makes it freeze less often but the real problem is not solved and I think I propably need DZO's help and knowledge to solve it.

I'm currently doing some more "fine tuning" to the NMEA parsing and I've been logging NMEA sentences today and there seems to always be 2 seconds or more between position updates so I can propably increase the delays between to about 1.5 seconds and reduce the freezes even further.
[Tilt, TyTN II, MDA Vario III Android Development] jfg69:
Ive changed .nbh's so many times in the last few days, I'm not sure which is which.. how can I determine who's I'm running?.. I know where to look for the kernel info, just no idea how to tell whats what.. :confused:
[Tilt, TyTN II, MDA Vario III Android Development] robuser007:
Good luck with this.

I use the GPS function every week, that's why I stay with windows mobile 2-3 days a week. Maybe I can use an external GPS receiver (mouse) with bluetooth (but don't know if this is possible with any program under android)?
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I can attach to my bluetooth GPS but that's about it. I don't think Android itself supports using a bluetooth GPS.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Try this version: http://xdaforums.com/showpost.php?p=6335631&postcount=253
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New version posted. The bugs in the Kaiser GPS code that caused slow updates and kernel panics has been found and fixed + some more non-critical fixes. This time it works! :)
[Tilt, TyTN II, MDA Vario III Android Development] voyteckst:
Thanks for this kernel - I'm testing it. But in some of previous posts You wrote that there should be more space in system nand partition. Actually I have reinstalled my system and there is still the same:

/dev/block/mtdblock2 102.8M 89.1M 13.6M 87% /system
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
That was just about correcting my NBH's to use the same partition sizes as the official ones from DZO. Unless your previous installation was made with my first custom kernel there will be no difference.
[Tilt, TyTN II, MDA Vario III Android Development] voyteckst:
My installation was made before this correction. But then I use newest one (after correction) and reinstalled system (data was untouched on sdcard).
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Well, the partition corrections were made in one of the first versions so likely you installed with a version that had those changes allready. 102Mb is the correct size for the system partition.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
At least for me the latest DZO code (2010-04-29) broke audio so I reverted that code and compiled a new kernel (updated in first post) based on the 2010-04-26 code.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New version in first post. More fixes to the satellite information parsing. All detected satellites should now appear in GPS Test (and other GPS software that shows satellite data.)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New version in first post. No need to update if you use the kernel from May 1st. Also updated the Polaris NBH as I do not know what GPS code it uses (Vogue or Kaiser?)
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
I posted a question about adding the 'nostart' parameter in the nbh to stop data from starting in this thread http://xdaforums.com/showpost.php?p=6385506&postcount=22

I would hate to have to startup even MORE versions of nbh's so would it be possible to add this in? you could always leave it set to ppp.nostart=0 and we and change it to 1 with hexedit for those of us that need data off.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
No problem. I'll add it.
[Tilt, TyTN II, MDA Vario III Android Development] anothertmobilemda:
*job well done*

hexeditor is installed...though it appears it only views.

i dont know how to modify the nbh with it.

nice suggestions... but i need more instructions on actual details

like what key deletes a character

how to modify key\data values

but
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Try the attached NBH and let me know if it worked. Don't forget to hexedit it before flashing.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
See this post for a screenshot. Just click in the values you want to change and write the new one. Save when finished.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
What GPS software are you guys using? I'm using iGO and it's very slow, like an action could take 5 seconds for something to happen. Sometimes, It'll just stall for 10-20 minutes.

Is iGO for Android Kaiser friendly, or I'm doing something wrong? BTW, my screen resolution is 320X480 and DPI is 181. Don't know if that has anything to do with it?
[Tilt, TyTN II, MDA Vario III Android Development] robuser007:
I don't like sygic (it says N385 and not the streetname), but it should work better I heard.

Try to clean some ram (taskiller?)? and let us know.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
I already have taskiller, but only 35 MB of ram free. Would be 38 but voice keeps running.

I'll try out sygic.
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
Super!!!

thanks a lot. I am sure it will work.

to be honest I don't really understand why that option has been left out of most nbh's

I will try it ASAP, and let you know. ( I was in a mood and flashed back to winmo)
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
I reinstalled iGO and it's still slow. Lowered my settings from 320X480 DPI @ 181, to 320X428 DPI@144. The system is overall faster, but iGO is still slow, and lowering the resolution made some parts of the iGO screen get cut out.

I'll try that other GPS software now.
[Tilt, TyTN II, MDA Vario III Android Development] tarekk9:
HTC TyTNII

hi

i have HTC TytnII and i install it in my mobile

Is this suitable to my mobile? or help me to fine the good one for my

thanks
[Tilt, TyTN II, MDA Vario III Android Development] dannyliemburg:
My polaris got stuck at the smart mobility screen due the polaris panel type.

Installed i.Hex and searched for panel.

After panel it says panel 3 but it should be panel 1 for me.

changed the 3 to a 1 and flashed again but it still gets stuck at the same screen.

any suggestions?

(I normally don't change the nbh file but this one seems a lot better than the older ones which do work. So it's possible that I am just doing the wrong thing!)

Thanks in advance!

*Edit:

Does anyone who has a polaris with panel type 1 run Incubus26J's super eclair?

If anyone does, which nbh is recommended then?

(I know this is kinda off-topic but at polaris android development section there is also a thread about this nbh and super eclair!)
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
thanks you so much...

this worked great.

I flashed this and installed polymod2.1d

only problem now is that somehow from 2.1g with wifi/BT patches to 2.1d

it went from working BTaudio to nonworking BTaudio.

I will try that supereclair next to see if that is any better.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
New versions in first post based on 2010-05-07 code. Nothing new for Kaiser users but important fixes for Polaris users.
[Tilt, TyTN II, MDA Vario III Android Development] robuser007:
edit: I know already the answer.
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
Does having the data.img on the SD card prevent the mounting of my SD card in a computer?

I've got my Windows 7 X64 machine to see the SD card, but it claims that there's isn't anything in there. Claims it's a removable disk and that I need to insert a disk.

I really have no idea what's causing it.
[Tilt, TyTN II, MDA Vario III Android Development] robuser007:
I've flashed the 03-05-2010 from here:

http://xdaforums.com/showthread.php?t=663125

Does this one contain are your gps fixes ? This one (link) has hardware acceleration on for eclair ?
[Tilt, TyTN II, MDA Vario III Android Development] jfg69:
Any chance you may be able to do a 480 with the fixes for the Tilt? I started to use your .nbh a few weeks ago, but I wanted to see how 480 looked. I like 480 at around 170-175, So I'd like to stick with that to stay consistent.

I was able to get a GPS lock, but it took like what seemed forever, so hopefully I can improve on that, since I cant seem to use anything that calls for GPS without having 10-15 mins wait time.

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] Dukenukemx:
A 480? You mean 320X480? I've tried 320X480, and it's murder on the performance.

I use 1.70.18.02 and get a GPS lock within 20 seconds of starting the app.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Yes it has because my fixes are now part of the official source branch. However you can easily enable/disable HW accelleration with a hex editor. And by the way, the one I posted also has it enabled.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
First of all, the screen resolution can be changed with a HEX editor. I won't compile a zillion of versions. You can change your parameters easily with a hexeditor. It really is easy, trust me.

About GPS fix time it always takes a long time for the first fix as we do not have a QuickGPS application for Android like in WinMo. The QuickGPS "primes" the GPS with the satellite almanac (at least that is what I think it does). As long as you do not powercycle the GPS it should pick up fix quite fast after the first fix.
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
I have been playing with compiling the kernel and making my own nbh.

could you post your .config for building the zImage so I have something to compare with.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
There is nothing special about my .config. I've used "make vogue_defconfig" to create it.
[Tilt, TyTN II, MDA Vario III Android Development] mnjm9b:
Thats what I am using too.

you don't make any changes?

just keep the default settings?