Develop Bugs

(start menu?) Program menu keeps whiting out. help

Need some advice. My program menu on my xda keeps whiting out.
On an initial start (or after editing the program list) the program list (or start menu) displays fine.
On the 2nd click some icons start doubling up at the bottom and fill the screen.
The on the 3rd click it goes off the bottom of the screen and goes completely white!
What gives? I've editing the number of items, looking in the registry at start menu opetions, deleting programs, but nothing solves it.
Performance etc not hampered but its really annoying. It MIGHT have started after installing a c++ cube program launcher (not sure).
if anyone has ideas to fix it please let me know.
TIA Sean

Hey I just had that exact same issue earlier. I was editing my \Windows\start Menu\Programs folder and making some adjustments when i noticed it happening. I kinda narrowed it down to being something to do with HButton. I was fiddling with the Hbutton display options just after modifying the programs folder. After more fiddling with the HButton display (changing colour and position) and a soft reset, my Start menu started working fine again and I havent had any problems with it again so far.
Probably nothing at all to do with it but thats what seems to have fixed mine as i didnt touch anything else but HButton and it is now resolved.
hope this helps in some way
[EDIT] completely ignore what I just put above, its just happeed again. The only thing I have done this time is Activesync and install a game. Kinda thinking it has something to do with Activesync now.......

lol oh well i guess i'll have to put up with it for now then. half a mind to send it back to O2 but its a software bug, I'll get the problem on the next phone as well.

Try to see in Memory the program values.
In my experience when tou have few program memory, start and today redrow is very difficult.
It happened me some times ago when i tryed a rom with problems of memory allocation.
You can try another rom (today you have many chose )

bigix1 said:
You can try another rom (today you have many chose )
Click to expand...
Click to collapse
Well considering my phone is one a month old I dont think I'll be flashing the rom JUST yet.
And update: for some reason the start menu is back to normal behavior! Absolutely no idea why. Just when i was getting used to it as well.

Graphical Glitch

I am using Myns Android ROM withthe wifi update + 110 pixel density update, booting via SD card and every now and then I get a graphical glitch/system crash that shows as thin, black and white stripes on my screen.
Anyone know what might be the cause/how I can fix this?
If i chose to install to NAND, would it be more stable/faster? And can I simply flash it with a WM ROM to go back to "normal"?
Thanks!!

I cant say about the glitch, try changing the kernel maybe. But your second and third questions have been asked and answered so many times, its ridiculous. But since its your first post, I'll answer:
would it be more stable/faster?
Click to expand...
Click to collapse
Yes to both
can I simply flash it with a WM ROM to go back to "normal"?
Click to expand...
Click to collapse
Yes again. Also, Try using the search button in the forums, and read the stickys, go through some threads etc.

My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?

graphical glitches are usually caused by using the wrong panel type in default.txt when using haret, or the wrong NBH panel type when using Nand, to fix the first, edit default.txt, to fix the second flash another NBH with another panel type, (panel type is usually in the filename).
To remove a widget, press and hold on it, then move it to the bottom of the screen.

Apologies for being a totaly newbie, but what are the "panel types"? MY default.txt shows the correct resolution, but I cannot see anything about panels (I might just not be looking hard enough lol!)
I now have a problem when booting from the SD card that my resolution is "bigger" (icons are larger and overlap, menu items are larger too) But it was fine before i rebooted....
Any help for the GPRS issue?

mr_pablo said:
My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?
Click to expand...
Click to collapse
You can remove widgets by long pressing on them until the bottom tray becomes a bin/x or something similar, then drag them to it.
About the 3g problem, I had that a while back after installing a new build, what solved it for me was changing the kernel. I had flashed to nand so I simply got another nbh. For you it might be zimage. If you say you got that graphical glitch when the device went to sleep, then you should try changing your panel time. For a good smooth android experience, you will have to take some time, and flash many different nbhs/updates and change settings etc to get what works best for you.

I am trying out Myns Warm Donut again with the wifi update.
How can i change panel time?

Dunno if this helps but I managed to get GPRS/3G working on SuperEclair. I had to manually put in the APN and made sure the mcc mcn codes were right.
When i changed the codes the APN disapeared from the list but data connection established itself after a couple of minutes.
This is the link I used to get the right APN codes:
http://george.insideiphone.com/wp-content/uploads/2007/12/mcc-and-mnc-codes.pdf

For NBH files the panel type and resolution is in the filename: KAISIMG-PANEL1-320-ECLAIR.NBH : the filename shown is for Panel1 resolution 240x320.
To change panel type simply flash another NBH with panel2 or panel3, it will not affect your install, since the android nbh's don't format Nand, this is done by the installer
For Haret installs the panel type is changed in default.txt look for the line: board-htckaiser.panel_type and change the value to 1, 2 or 3.

Wow, that is great! I've searched for a solution for this problem a long time, but this is the first thing that works for my Kaizer 130.
Many thanks!

I had android running off the sd card most of the day yesterday, using the panel type of 1 worked well (did notice the odd glitch when coming out of sleep mode, but it didnt crash)
still not sure what the panel type does, can anyone explain? (curiosity really)
However, I tried to use the camera, and after switching to vide and back again to photo mode, android crashed.
I can suffer not using the camera, as its nothing amazing.
p.s. anyone know if you can remap the buttons? as the hang up button puts the phone into sleep mode, the wheel doesnt do much, and other buttons dont do much either.

Panel type refers to the LCD panel, there are 3 different types of panel fitted to the kaiser series, one manufactured by Sony, the other two by Topoly, functionally they are identical, however there are some differences in the electronic controllers fitted to each, which in winmo is detected automatically, however Android is unable to detect the differences and the correct type must be passed to the kernel at boot time, either by boot parameters in default.txt or hardcoded into the NBH. Due to the way electronics factories work, the panel type depends on which one was available at the lowest price, and shortest lead time, when it was required, hence the reason for the confusion, since some people still think that panel type is set for certain models of kaiser, which is inaccurate, since both my KAIS130's have different panels fitted.
Camera does not work in any Eclair build yet, it does in Donut builds, however it's still a little low quality even on the 3Mp Kais130, Video does not work on any android builds very well, if at all.
Remapping buttons can only be done by recompiling the kernel I think, however after a while the button layout becomes second nature, I actually get lost using winmo now, lol.

[Q] Disable physical keyboard

Hey guys,
Quick question here: Is it possible to disable the physical slide-out keyboard in either WM or android (specifically android) without having to take the thing apart?
I saw this thread:
http://forum.xda-developers.com/showthread.php?t=692022
But that didn't work for me. Has anyone else had luck with this solution? Is there any other way to disable or turn off the keyboard without physically unplugging it?

Why would you want to do that...? If you don't want to use it, then don't. The on-screen keyboard is pretty good, and you can get swype or whatever else you want... You never need to slide the kbd open.
So what's the point?

The keyboard is damaged. It sat in a puddle overnight, so now whenever I need to input text, the keyboard just outputs random characters. Constantly. Even when the physical keyboard is not engaged. I've been able to work around it in WM (its still VERY annoying), but as soon as I boot into android, it automatically goes to the browser and starts the random text thing again. I cant keep it on the home screen for more than half a second before it goes opens the browser again.
Whats even weirder is that I checked the water damage stickers on the phone and none of them have turned red.
I'm assuming some of the keys shorted out and are now always "on." So I just want to disable the physical keyboard and only use the soft keyboard.

Ouch. Well, if you have TEP just get the thing replaced - especially if it doesn't show any water damage.
With that said, I'd say the best option would be to physically disconnect the cable. I'm not aware of any software way to disable the kbd in Android... Curious, how do you do it in WinMo? I'll poke around to see if there is any way to do it in Android, not sure how it would be done. There may be a secret option that I'm not aware of, because it never comes up

The simplest option is probably to create a minimal microp key layout that only contains mappings for the three front panel keys handled by microp, and then perform surgery on your init script to replace the existing keymap entry for your rhod with your new minimal one. Nevertheless, init is embedded in your rootfs.img and isn't easily edited from a Windows computer. Thus you'd need to either copy init over to your sdcard with the terminal emulator inside of android, or install the Android SDK onto your computer so you can pull/push the file with adb. If you have a computer running Linux then there are more options.

Pop over to this thread: http://forum.xda-developers.com/showthread.php?t=828011&page=3 and maybe you'll get some ideas about how to create yourself a special keymap with nothing in!

Thanks for the info guys. I really no good at doing any deep editing, so a lot of those suggestions just went right over my head :-}
I know this is a big request, but if someone has the time and knowledge to create an empty key map for me and tell me how to apply it, that would be greatly appreciated. If not, no big deal. I just don't want to screw up my phone any more than it is, ya know?

Roots08 said:
I just don't want to screw up my phone any more than it is, ya know?
Click to expand...
Click to collapse
LOL you don't really seem to have much to lose at this point...!
Sounds like it may be more complex than originally thought. Unplugging that cable still seems to be your best bet... Otherwise you'll have to muck around with things everytime there's an update.

rootfs with bad kbd option
Roots08 said:
Thanks for the info guys. I really no good at doing any deep editing, so a lot of those suggestions just went right over my head :-}
I know this is a big request, but if someone has the time and knowledge to create an empty key map for me and tell me how to apply it, that would be greatly appreciated. If not, no big deal. I just don't want to screw up my phone any more than it is, ya know?
Click to expand...
Click to collapse
Download the rootfs found here. and follow these instructions:
1) Uncompress the file via the 7zip utility.
2) Rename it to: rootfs.img
3) Copy it over to the android boot folder (usually andboot) on your sd card.
4) Open up the file startup.txt found in the same folder with your favorite text editor.
5) Find the line that starts with set_cmdline and look for an entry on that line that begins with physkeyboard= and change its setting to: physkeyboard=rhod_badkbd
6) Restart your phone.
Since you're the one who has requested this, you're my designated tester. It should turn off all your keyboard keys. It should also leave the keys on your front panel working. Let me know how it works for you. If it works fine I'll submit this modification for inclusion into XDAndroid. If it doesn't, we'll have to tweak it further. You can thank Arrrghhh for talking me into doing this.

I have had this procedure work on several phones....
Take the battery out.
Submerse the entire phone in alcohol. The alcohol will displace the water in the phone. After a minute, take the phone out of the alcohol. The alcohol left in the phone will evaporate. After 24 hours, place the battery back in the phone.
Should work like new.

[Q] ts_calibration HTC Touch pro Xandroid

Hi everyone.
First time on a forum for years. This one is pretty daunting though. Not even sure if Im in the correct thread
Just recently got myself an HTC Touch Pro. Yeah! it's old but I guess its better that the Ericsson w350 I had.
I was not happy with the 6.1 Win Mobile OS on the HTC and I heard that Android can be loaded up instead. So I started doing some research.
To cut a long story short, I managed to load XDAndroid onto the microSD card. all is working fine except I messed up on the touch screen calibration. or at least it was not made clear to me that what I was indeed doing was a screen calibration.
After some reading on the wiki files, I removed the ts_calibration as instructed and rebooted the system. The graphic for the calibration test does not seem to display correctly. Hence the readon for the initial stuff-up so I simply had to guess where the pointer were using the win6.1 OS calibration(Don't ask - it involved a non-permanent marker). Even that does not seem to work.
It would seem that the co-ords where transposed after some fiddling around. Left was right, up was down etc. So I got to thinking to open that ts_calibration file and started playing around with the numbers. Even the screen functionality was reversed when the I slid the screen open. Navigation via the Keyboard is no hassle though. The touch button navigation seems to work fine except the selection key does not actually select anything, I have to use the enter key on the keyboard. Not sure if this is normal. So if anything, navigation involves the keyboard to be open thus the screen orientation is always landscape as opposed to portrait view which sucks! esp if I'm texting or making a call. What the work around for this is general?
So I thought of opening the ts file in a txt editor and I transposed the numbers. I seem to be getting somewhere as the up and down seem to be working correctly now but the left and right are not, center screen is still out though. I'm not sure what sets of number represent which co-ord. I know that the calibration requires 5 co-ords, but I dont know in which order they should be. Is middle, top-right, top-left, bottom left, bottom right?
It would be easier to just have the correct co-ords for this phone. instead of playing around with some random numbers. IOW would the ts file co-ords be the same for all HTC Touch Pros? if so where can I get the correct co-ord numbers for that file? then I wont have to use the calibration function. easier still, is there a free app that will do this from within the XDAndroid os?
The start up txt I chose was Raph100 for the root folder. This is correct for my phone according to the wiki help files. I've not updated the files and used them as is. Would the incremental updates fix this?

I'm having the same issue for my TP. After some discussion, I downloaded the ts file from the FRX07 fixed discussion and it's pretty darned close to accurate. MAYBE just a little off center to the lower left of icons.
Here's a utube vid that shows clearly the touch pattern for calibration.
http://www.youtube.com/watch?v=FB6MVFH4Jv4
Hope it helps.

Scroll direction after Update

HI,
i changed the scroll direction a while ago. Everything worked fine. After the Firmware update yesterday i noticed today that the scroll direction is again the original. So i thought i go again in the regestry and do the changes again. But they where still made. I changed it back to 0 and again to 1. I rebooted, removed the touch cover and connected it again. But nothing changed.
Someone and idea??

If you're using a Surface (in which case you really should have posted this in the Surface forum, not the RT forum) try the Trackpad Settings app (free, in the store). I personally am happy to use direct registry edits instead, but that stuff is all very unofficial. An app like Trackpad Settings, which comes from Microsoft, will be supported and should work fine.

normally i like the selfe made correction in the registry more, but i just testet the app you told me. The problem is, that the app did not find my touch cover. And it's deffently connected because i'm writing these words with it.
i hope you can help me.
sorry for the wrong topic. maybe a mod can move to surface.

Yeah, it does that sometimes. Try again. If it still doesn't work, try disconnecting and reconnecting the cover whiel the app is open. Also, right from the app's Marketplace description:
"If the app doesn't detect the keyboard, do the following:
1. Make sure you have the latest updates. <instructions>
2. From the Start screen, type Devices, tap Settings, then tap Devices And Printers. Then tap refresh three times. (Yes, it actually says this.)

tryed all this but nothing happens

After the latest update for the Touch pad app, it now wokrs.