Android boot error "micropklt_lcd_ctrl: This function should no longer be used" - Touch Pro2, Tilt 2 Android Development

Android boot error "micropklt_lcd_ctrl: This function should no longer be used"
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
Reformatted SD and restarted from scratch.
Tried Android versions:
Project Android 030810.cab
Project Android 033110.cab
[MJG]Rhod.Eclair.Rebuild033110.3.rar
plus various older ones (with different base name, xAndroid or something like that?) already deleted.
Tried to disable 3D Hardware during boot.
Another suggested workaround to use specific files from older releases; these I could no longer find on the net.
To sum attempts up:
Tried different (?) Android releases (xAndroid, Project Android) - fail
Tried small SD card (1 GB) - fail
Tried SanDisk instead of Kingston SD card - pending
Tried to reformat SD card (with SD card formatter) - fail
Tried to disable 3D Hardware - fail
Tried WinMo ROM labeled as created for Android (Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan) - fail
Tried to insert SIM card (was missing) - fail
Tried to update HardSSL (Rhodium-HardSPL_V2_00R3.exe) - fail
Information:
(forum prevented me from adding links to external information)
This forum, other members with same problem
Looking for: suggestions what else to try.

ItsReallyMe said:
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
.
Click to expand...
Click to collapse
I have an AT&T Tilt2, stock rom, 8GB SanDisk. I see a very similar message when booting xdandroid, but mine continues to boot through, my boot sequence snippet runs like this:
Code:
[ 26.309173] Adding 102392k swap on /dev/block/ramzswap0.
Priority:-1 extents:1 across: 102392k
[ 26.484039]Something used micropklt_lcd_ctrl: This function should no longer be used
USING EXPERIMENTAL TILT2 LAYOUT
op: cannot stat '/init.etc/keymaps/tilt2_navi_pad.kl': No such file or directory
Touchscreen device directory is /sys/class/input/input2
Then continues to the screen calibration. I know I'm not helping directly, but perhaps can help lead others to clues ?

i already started a topic for this exact error....
http://forum.xda-developers.com/showthread.php?t=632128
So far no one has come up with a solution...

Oh, sorry, I searched the forum a few times, but mus have forgotten that thread, otherwise I would've posted there as well...
From what I can read there, maybe I should try a SanDisk instead of Kingston SD? Or is it SD vs. SDHC? Anyway, I just ordered a 2 GB SanDisk from Amazon (smallest one I could get ) and will try this next...

I managed to solve it by reflashing the newest HardSPL. (In my case I had a corrupt microp firmware, casuing all kind of problems in WM as well).
It might not solve the problem for you, but it can't hurt either

My SanDisk SD has not yet arrived, but I tried to insert a SIM card (phone currently has none, since I' using another one while testing) - no changes.
Thanks for the HardSPL hint - tried as well. No Luck, but at least another topic to add to the "things I tried" list

Okay.. So, i tried HardSPL.
Task 29
Reloaded my Rom
Hard Reset
Formatted Memory Stick
Followed ALL instructions!
Nothing happened.
I then went back and tried an old version of android from this thread
I used the 12/20 2.01 version.
AAAANNND..... it loaded right away....
WHY does this old version work, and the new ones wont?
what is different?

Update: my SanDisk SD card arrived, so I loaded [MJG]Rhod.2.1Sense.042310.rar, extracted it to the card, and started it. Same problem. This means it does not seem like a Kingston SD card problem.
So... I tested, and can confirm that the old build you linked solved the problem for me as well!

I have searched this ENTIRE FORUM and read EVERY SINGLE GOD FORSAKEN post about this error. I am at my whits end!
Someone said they got it to work with a more current package and an old rootfs.img
I didnt try the same two builds they did, i tried the sense ui one and the old rootfs. from the build i said works. it did not work.
so i figured i would compare the two rootfs.img to see what the difference is.
however, i cannot open the contents in windows (from what i understand)
so i install UBUNTU on my computer.
I cant for the life of me figure out how to mount the damn image!
PLEASE SOMEONE ELSE! please look this up. i am frustrated beyond words.
if you can give me a way to compare these files in windows, i will be glad to do it.
I just cant stand windows mobile crashing all the mother f-ing time and i REALLY REALLY REALLY want to use android. Im sorry for being so frustrated. i have spent literally HOURS on this...

Anyone, anything?

Mount rootfs.img
eternalcold said:
Anyone, anything?
Click to expand...
Click to collapse
You can mount image in terminal like this:
first create dir with:
mkdir /mnt/rootfs
then mount the image:
mount rootfs.img /mnt/rootfs/ -o loop
then change dir to /mnt/rootfs and you have the android FS.
i will also compare old and new rootfs so maybe we will found something!
BR

I still have this problem.

I tried what you said, but i keep getting errors. I cant seem to get it to work. I will again look through all the threads again, as well as the different websites i found from google. i will link them tomorrow when i get a chance. If anyone else has found anything, please let me know.

The latest kernel has the following commit message
"rewritten micropklt_lcd_ctrl calls to micropklt_set_misc_states calls"
So this might fix it for you guys?
It seems to have some other problems with sleep etc, but if it boots it is something

I see, thanks for looking, however, i still cant figure out how to mount and change things in ubuntu (sorry, i know i am a newb) would you be able to repackage it with the line changed to the old one? and upload it? i will check it out to see if it works.

It's alive!!
Download latest Android build with latest kernel from hxxp://glemsom.anapnea.net/android/htc-msm-android/ and replace zImage and modules and thats it.
i didn't test it full, but it starts!
Thanks to Star-Lite for info!!!
BR

Ah yes it works! Beautiful beautiful!

Don't thank me, thank CaptNoord for fixing this in the kernel
I'm sure he has a donate button somewhere

I will donate as soon as the bills are past this month (a couple more days)
Out of plain curiousity, is there a reason why this error only happened on some devices and not others? Could it be from a hardware difference between maybe different revisions of the device?

use the right starup.txt file

Related

Sprint update - SD card problems

well I updated to the new rom without a problem I backed everything up on my 8gig card and removed it prior to installing the new rom, now that I put the mem card back in the phone for some reason it shows up as empty? what is going on here?
*update* I just checked in settings to see if any space is being used on the mem card and it shows the space as used but nothing is physically visible on the card
if it turns out that I lose everything on the SD card this was he worst thing I have ever done, might as well throw the phone in the toilet and call it a day all contacts gone! all photos, 500+ songs and spreadsheets. Although it does show the space as used on the card (hope that is a good sign!)
someone please help
Try this. It's a demo version but it may save your data.
guitardoc64 said:
Try this. It's a demo version but it may save your data.
Click to expand...
Click to collapse
Thanks! I will give it a try
I'm having the same problem. For me each time I experience this, I just remove the card then reinsert it. It usually recognize the card after that. Just a hassle to have to do it each time it happens though. I've been searching other post to see if I can find a solution, but nothing yet. When I do find something, I'll post the solution for you.
motorcitymadman said:
I'm having the same problem. For me each time I experience this, I just remove the card then reinsert it. It usually recognize the card after that. Just a hassle to have to do it each time it happens though. I've been searching other post to see if I can find a solution, but nothing yet. When I do find something, I'll post the solution for you.
Click to expand...
Click to collapse
Thanks I recommend staying away from the program guitardoc64 posted, I took about 4+ hours for it to scan and find my data then when you go to save it you have to buy it first and the price is rediculous $69.00
"Data Doctor recovery memory card"
My bad!!!
Sorry about that! I posted the wrong program! In my search to find recovery tools I had downloaded about 10-15 different ones and well...got in a hurry to help, and can't apologise enough. I can fix my mistake at least, with the PCI file recovery program.
This one is freeware, works very fast (tested by recovering files my Touch screwed up) and I really wish I'd posted it instead.
Damn, tried uploading and it didn't work. Here's the link.
http://www.pcinspector.de/Sites/file_recovery/download.htm?language=1
guitardoc64 said:
Sorry about that! I posted the wrong program! In my search to find recovery tools I had downloaded about 10-15 different ones and well...got in a hurry to help, and can't apologise enough. I can fix my mistake at least, with the PCI file recovery program.
This one is freeware, works very fast (tested by recovering files my Touch screwed up) and I really wish I'd posted it instead.
Damn, tried uploading and it didn't work. Here's the link.
http://www.pcinspector.de/Sites/file_recovery/download.htm?language=1
Click to expand...
Click to collapse
No problem you were just trying to help and I appreciate that! Luckily I was able to retrieve most of my files minus a few programs and songs
These problems are on the new ROM?
somehow the files on my SD card were corrupted when I put the card back in, so I'm not sure if I can attribute it to the rom
It may not be the rom... over at PPCGEEKS they've been talking about the microsd cards getting corrupted for what seems like various issues. I ran into the same problem awhile back and I can't remember where I spotted it but, it mentioned reformatting the microsd in FAT as opposed to FAT32. I did that and I have not had any problems since.
http://forum.ppcgeeks.com/showthread.php?t=12148&highlight=microsd+card+corruption
ja8t
Its' not format specific. I have had the problem with the card formatted both ways. The Artemis SD .cab improved things but I still get problems, so far a soft-reset has been fixing things. I'm looking at the Diamond coming out in Sep on Sprint as a replacement. Don't get me wrong, The touch is 99% of what I expected it to be but the SD issue is a big disappointment. I never had issues with my Apache other than it's clunky size and the fact that it looked like a BBC sci-fi prop.

[How-To] properly install Android

It is not quite self-explaining how to install Android on our Windows Mobile devices. Therefore I took some time and wrote down all the steps for people who are new to "Android".
More testers -> more experience -> more knowledge -> faster/better development.
I hope this way the forum is kept clean(er) from all kinds of questioned that have already been answered many times.
ReadMe Includes:
- Partitioning
- Device preparations
- Boot loader
- Install steps
- Fixes
- Links
- more...
If you are a developer (you create your own package) feel free to use my ReadMe for your packages (update regularly though).
to download the ReadMe click the [Android Repository] button in my signature.
It goes to a rapidshare page with 3 files, and when I click on the filename Android_README.TXT
or start download, I get the error
The file could not be found. Please check the download link.
ok thanks. i fixed it (rs bug when renaming files ^^)
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
ATHiEST said:
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
Click to expand...
Click to collapse
normally just calculate how i wrote in the readme:
whole space -768 (3* 256) and then the other 3 x 256
but in ur case i would make the swap smaller (i think its not even used at all) and the fat32 bigger; for instance:
fat32 - 384 MB
ext2 - 256 MB
ext2 - 256 MB
swap - 128 MB (rest)
To be honest the bit I find most confusing is all the different versions!
i didnt create any partitions on my card, and android works as good as it does on any, mind you i have not updated the files fo0r a month so alot might have changed
ReadMe updated!
updated a bit...
Geeba said:
To be honest the bit I find most confusing is all the different versions!
Click to expand...
Click to collapse
i agree...
i've been looking these posts here for a couple of days now and i still don't know how to do it....
especially the DualBoot thing...
is it possible to make a little bigger how-to manual?
or at least explain the versioning and the needed thing a little more?
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
N!ghty said:
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
Click to expand...
Click to collapse
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
qtype said:
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
Click to expand...
Click to collapse
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
N!ghty said:
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
Click to expand...
Click to collapse
ok... thanks for the help... you helped me a lot just with the claryfication of the versions that need partitioning and the ones that don't...
i didn't know that...
good luck with studying!!!!
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
qtype said:
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
Click to expand...
Click to collapse
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
N!ghty said:
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
Click to expand...
Click to collapse
yep, I downloaded it but I didn't know that i have to rename it...
It did the trick... booting up Android
thanks for all of your help...
updated the readme, not includes DualBoot howto and some other changes...
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
qtype said:
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
Click to expand...
Click to collapse
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
N!ghty said:
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
Click to expand...
Click to collapse
sorry about that...I realized it later that I should ask in another thread that question...
I managed to figure it out... I just needed to manually configure my APN settings...

I'm ready to throw it out the window

Hi all.
I've been lurking on the Kaiser forum for some time and have found a wealth of very useful info... Except when it comes to running Android via HaRET.
Yes, I know there have been a million questions. Yes, I have seen many of them inserted into what should be straight developer/bug threads. Even so, the "answer" to my issue doesn't work.
From "How to run Polymod’s AWESOME 2.1 Eclare Build and Updates":
Section 2 - Errors and FAQ's
===============================
#1 Failed to reach system.img on SD Card
If you see the error message below:
“Failed to reach system.img on SD Card” then you did not hold the button down correctly. You are seeing this because you missed, disabled or bypassed the install menu.
Click to expand...
Click to collapse
NOT TRUE. I have booted more than 20 times pressing/holding the center button at different times and with different intensities. No matter what I do, I get this blasted error message. Any solution other than the stock one listed above would be cause for hero-worship.
This error can have a number of causes, namely the file system, is the SD card formatted FAT32, ( some cards come formatted FAT16 as standard), or having the SD card set up incorrectly, for haret you need to have all files in the andboot folder.
Provided haret starts correctly, which it is since you cannot reach the post-install stage unless it is booting the kernel, then the only part of the procedure that can go wrong is the installer.
The only things I can think of that would cause the installer not to start is either the card itself, or problems with the andboot folder and/or the files inside.
The only advice I can give at the moment is to calmly start haret, watch the scrolling text until you get the pause, and the 'press d-pad to start installer' text.
At that point if you press the d-pad centre button, and hold it you will see '^@' on the screen, if you do not see the '^@' or see anything else then the installer cannot start, it will only respond to the correct key.
If you see anything else it is possible you have incorrectly set an option in default.txt file.
If all this still fails, then report back with anything you find, I may have some other ideas based on what you find out
+1 on zenitys answer and in addition you are using the correct basefiles to run haret?
Try using the screen as a giant keypad and pressing and holding the center of the screen.
EDIT: Scratch that... It only works as a keypad once the menu is up. Sorry.
that works?
Seriously?
I mean really?
No it bloody does not, ( lol, can't believe i actually tried it ).....
i had this problem and pulled my hair out, eventually i downloaded a different haret basefile and copied to my SD and bam it worked, sorry but i'm i soon after went to nand and erased the haret files so i don't have them anymore.
zenity: Yes, it is FAT32 and yes all files are in andboot. I do see a '^@' when I press the center button if I press it when prompted. If I press and hold as soon as I see Tux, I don't get that character pair. I see a different string of characters if I press one of the other buttons instead. I haven't modified the default.txt file in any way other than to re-name it from default-kaiser.txt.
I am using the files from a haretinstall.zip that I got directly from sourceforge Android HTC project (sourceforge.net/projects/androidhtc/files/... not allowed to post links <_<). The files were under the date 02-13-2010. I have since grabbed two other more current versions of haretinstall.zip and will try them after I post this. I am also using the most current androidinstall.tar and androidupdate.tar from sourceforge, though I have also tried Polyrithmic Eclair 2.1g's androidinstall.tgz.
Thanks all for the replies and I'll try those other haretinstall.zip's while waiting for any other replies.
maybe try a different sd card?
I couldn't get any nbh's to be read off of my 2gb patriot, but when i put in my 16gb sandisk the nbh's worked.
I know this is only marginally related lol, but it's worth a shot?
mr_fosi said:
zenity: Yes, it is FAT32 and yes all files are in andboot. I do see a '^@' when I press the center button if I press it when prompted. If I press and hold as soon as I see Tux, I don't get that character pair. I see a different string of characters if I press one of the other buttons instead. I haven't modified the default.txt file in any way other than to re-name it from default-kaiser.txt.
I am using the files from a haretinstall.zip that I got directly from sourceforge Android HTC project (sourceforge.net/projects/androidhtc/files/... not allowed to post links <_<). The files were under the date 02-13-2010. I have since grabbed two other more current versions of haretinstall.zip and will try them after I post this. I am also using the most current androidinstall.tar and androidupdate.tar from sourceforge, though I have also tried Polyrithmic Eclair 2.1g's androidinstall.tgz.
Thanks all for the replies and I'll try those other haretinstall.zip's while waiting for any other replies.
Click to expand...
Click to collapse
I do remember trying the 2/13 first and that is the one that holding the button did absolutely nothing, it was either 2/14 or 2/20 (those are in my browsing history) that did work for me. It was a "ta dah" moment when the install menu popped up.
deezy7 said:
maybe try a different sd card?
I couldn't get any nbh's to be read off of my 2gb patriot, but when i put in my 16gb sandisk the nbh's worked.
I know this is only marginally related lol, but it's worth a shot?
Click to expand...
Click to collapse
I doubt it, cause its reading the kernel if he is getting the error message. The error message about system.img is because an install hasn't been performed to create a system.img or data.img file on the sdcard.
Actually it's very related, android seems unusually sensitive to SD card issues that winmo simply ignores.
If you have another SD card available then try that, if not then all I can suggest at the moment is reformatting a couple of times, that worked for one of my 2Gb cards that simply would not recognise my NBH files no matter what I did.
An alternative might be to grab kalt_kaffe's zimage from here : http://forum.xda-developers.com/showthread.php?t=660158
this seems to be the best zImage for eclair at the moment. Just download it, put it in andboot with the rest of the haret files, make sure it's named correctly, ( it'll probably need you to delete the zImage file already there anyway, or overwrite if you use a card reader and windows).
Since you are getting the ^@ then the kernel is running properly, that actually only leaves the SD card, the reason you get the other character pair if you press to early is that with some zImages the keyboard may not be set up early enough, which is why I always wait for the pause, never failed me yet.
Maybe... Maybe...
Thanks again all.
It may well be the SD card but a more current set of HaRET basefiles did finally fix the center button issue. I have been able to get android installed but little else. I have a blank screen (with clock, battery and wifi in the top bar) but nothing else.
I'm going to blame this issue particular tar files I used and I will go back and try the Eclaire by Polyrithmic or the one by kallt_kaffe you linked. I didn't really want the Andriod HTC tar files but was using them in an attempt to minimize the variables causing my initial button issue.
If you are going to use polymod may I suggest the 2.1D download linked in my sig, it's only the install.tar, but is pretty stable, and is in fact what I use for my everyday android on my main kaiser.
Since you have a working set of haret files, simply replace the zImage with kalt_kaffe's zImage, replace the installer with poly's 2.1D and you should hopefully be good to go
I tried 2.1d and it locked during the post-install setup. I also tried kalt_kaffe's zImage with both 2.1g and it broke my wifi.
As such, I am back to using 2.1g with the kernel that was originally bundled with it... Even bluetooth seems to work. I can see my lappy but I haven't tried pairing yet. No microphone though as far as I can tell. It'll be awesome once the ethereal developers find a way to make the camera work.
At least now I have something new to play with. I'm eying Warm Donut b/c I like the look but I don't know if I want to undo the working install I have. Never know till you try, right?
I guess this is probably already well-known but my kaiser's camera works under Warm Donut. The pics aren't all that great but it does take them.
If anyone else stops by... I'm having audio problems. I'd had audio problems with all the different Android releases I've tried so far. The main problem is that there is no audio. No alerts, rings or media.
Any suggestions?
mr_fosi said:
If anyone else stops by... I'm having audio problems. I'd had audio problems with all the different Android releases I've tried so far. The main problem is that there is no audio. No alerts, rings or media.
Any suggestions?
Click to expand...
Click to collapse
The way I understand it, that can be affected by your radio firmware... The radio firmware I use without any problems for android is in my sig.
Please post which one you are using, too!
Good call! I hadn't considered my radio version though I have seen numerous posts suggesting that users upgrade... Or at least swap theirs out.
WM6 indicates that my radio version is 1.27.14.09.
Radio 1.27.14.09
Protocol 22.45.88.07h
ROM 1.62.00.00
I'll do a little reading and see if I can't figure out how to swap a new radio (probably the one you're using) in.
Ok that's one old radio, go here : http://forum.xda-developers.com/showthread.php?t=393182, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio.
I got the radio nbh and now I am working out how to use nand. Most everything I see is geared toward wiping windows to replace it with android. I don't want to do that yet so I'm trying to parse now to flash this nbh without jacking up my device or the windows that is currently on it.

[Q] How to boot from Android first

Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.

Unable to use SD Card

I started a thread elsewhere and have been advised to put it here for a speedy resolution...
http://forum.xda-developers.com/showthread.php?p=9785290#post9785290
In essence, I have an HTC TP2 running WM 6.5 Pro supplied by Vodafone here in the UK. I have an 8Gb SD card (unknown manufacturer) formatted to FAT32. On the card I store all my WM apps, plus all my folders with files, docs, pictures, video, etc.
On the card I installed Ubuntu and XDAndroid via the 2.2 Froyo.112210 cab
The Ubuntu worked fine, The XDANDROID looked great and on the face of it worked fine too, until I tried to set the ringtone. I realised I was missing calls and notifications because it was on Silent, and I could not change it. I tried to open my music and videos, but the apps said i had no SD card. I checked memory in Settings and it stated that the SD card was mounted, but gave no size info and would not let me Unmount it. I then tried to search media on the card and had no joy. In essence it did not seem to recognise the card.
I then bought another SD card, this time a Kingston 16Gb already formatted to FAT32, added all the files and docs, it too would not work. I have since been round and round the loop of deleting both SD cards, reformatting to FAT32 using both my default Ubuntu app on my Laptop, gParted via my Laptop and the phone. None work.
I now am still on WM 6.5 because I can not use the phone.
I have searched Google and the Forum, and other than formatting to FAT32 I have seen nothing that can help, but that may just be my searching skills.
It has been suggested that some makes of card do not work also.
Other things that I have found a problem:
The keyboard does not light up when I use it, which is impossible poorly lit rooms, etc
Can't find a way of viewing folders, I'm sure there will be more once I get it going...
Any help, please!!!!!
Format with the HP tool. Full format.
Keyboard backlight doesn't work in Linux/Android yet. We're working on it...
Can't find a way of viewing folders...? Astro, OI File Manager...? There's a ton.
My experience is SD Card cannot be used if you installed xdaandroid with CAB version. I tried for the whole night, formatted my card with many different tools - without luck.
At last, I downloaded the zip one, and finally, it works!
Hope it also works with your
hadobac said:
My experience is SD Card cannot be used if you installed xdaandroid with CAB version. I tried for the whole night, formatted my card with many different tools - without luck.
At last, I downloaded the zip one, and finally, it works!
Hope it also works with your
Click to expand...
Click to collapse
Thanks for the tip. I'll try that. It makes more sense. I can't believe taht formatting using different tools can work as a FAT 32 is a FAT 32.... if not then what is it.
Can you tell me. Did you download to laptop, extract and then just copy the files on to your TP2 SD card....?
jonners59 said:
Can you tell me. Did you download to laptop, extract and then just copy the files on to your TP2 SD card....?
Click to expand...
Click to collapse
Either way, download extract & copy or just download & extract straight to your SD.
I don't think anyone should ever use the CAB install. The only benefit you get is a shortcut, which can easily be created manually.
The FIX
hadobac said:
My experience is SD Card cannot be used if you installed xdaandroid with CAB version. I tried for the whole night, formatted my card with many different tools - without luck.
At last, I downloaded the RAR one, and finally, it works!
Hope it also works with your
Click to expand...
Click to collapse
BRILLIANT - WELL DONE... Yes, this is the answer. Not reformatting. God knows how many times I tried and the number of different tools and processes of formatting. None worked.
This worked first go.
I am now just going through the device to fine tune and no doubt will find any glitches or queries.
So, short cut for all readers.
DO NOT USE THE CAB, Use the compresses RAR file.
http://reefermattness.scepterr.info/XDAndroid2.2Froyo.112210.rar
Save on the desktop of your Laptop/PC.
Connect device to the Laptop/PC
Extract to the root of the SD Card
Take out the Programs folder from the extracted folder on the SD Card and put in the Root of the SD Card - this may clash with the WM Programs folder, but I use Ubuntu so it allowed me to merge the two nicely.
Then off you go, boot up....
jonners59
I'm happy to hear that you had your problem solved.
AFAIK this bug just happenned with the latest version - the Froyo FRX03. I'm using Ubuntu as well, and the after I bought my new Memory stick, I formatted it with the Ubuntu Disk Utility, and the Cab - the Eclair - worked very well...
But like arrrghhh have said, yea people shouldn't use the CAB install. You gotta spend time installing it (and it usually takes quite long), and just to have its shortcut...
hadobac said:
jonners59
I'm happy to hear that you had your problem solved.
AFAIK this bug just happenned with the latest version - the Froyo FRX03. I'm using Ubuntu as well, and the after I bought my new Memory stick, I formatted it with the Ubuntu Disk Utility, and the Cab - the Eclair - worked very well...
But like arrrghhh have said, yea people shouldn't use the CAB install. You gotta spend time installing it (and it usually takes quite long), and just to have its shortcut...
Click to expand...
Click to collapse
Maybe, all I know is that I had trouble getting any releases to work, and spent ages searching for fixes, which is where I first encountered other's issues with the same problem. All suggested a reformat. And the only fix that worked was the zip Maybe if I had used the zip before I would not have had all this trouble.
Now that it works, I need to look at all the other little issues.
Light on all the time
fast use of the battery
Seems to lock up sometimes requiring soft restart
No Blue tooth
No camera
and I can't see my music or pictures, though i can see all those for the various apps!
jonners59 said:
Maybe, all I know is that I had trouble getting any releases to work, and spent ages searching for fixes, which is where I first encountered other's issues with the same problem. All suggested a reformat. And the only fix that worked was the zip Maybe if I had used the zip before I would not have had all this trouble.
Now that it works, I need to look at all the other little issues.
Light on all the time
fast use of the battery
Seems to lock up sometimes requiring soft restart
No Blue tooth
No camera
and I can't see my music or pictures, though i can see all those for the various apps!
Click to expand...
Click to collapse
You really need to at least read the FAQ dude, c'mon these are BASIC questions/problems.
I did tell you to reformat, I didn't think the cab was the issue honestly - I don't ever use the cab, as I think it's quite unnecessary... But others use it just fine AFAIK.
this worked for me...thanks
i installed the cab first and i also had this same problem with the sd card. i tried the zip file and that didn't work either. Then i used the hp tool that is mentioned in post #2 to format the sd and then tried the zip file again and BINGO. So i think a combination of formatting the sd and using the zip file works best. thanks alot guys for all the help. it sucked not having any sound
madhopps said:
i installed the cab first and i also had this same problem with the sd card. i tried the zip file and that didn't work either. Then i used the hp tool that is mentioned in post #2 to format the sd and then tried the zip file again and BINGO. So i think a combination of formatting the sd and using the zip file works best. thanks alot guys for all the help. it sucked not having any sound
Click to expand...
Click to collapse
Could be, but also suggested are gParted, which is a good format tool. The HP is for Windows machines. I use Ubuntu which is Linux, just like Android, so when I installed, it did so within WINE, which is Windows tool for running their apps on Linux. It's not perfect and in this case it could not find the USB ports. No worries though as I think the zip method was the ultimate solution for my senario
arrrghhh said:
You really need to at least read the FAQ dude, c'mon these are BASIC questions/problems.
I did tell you to reformat, I didn't think the cab was the issue honestly - I don't ever use the cab, as I think it's quite unnecessary... But others use it just fine AFAIK.
Click to expand...
Click to collapse
A little unkind arrrrghhh... The issues I raised in this reply were immediately after having managed to get the device working. And yes, I know some are in FAQ, though no solutions to most and many are not.
The power issue and the no ringtones options are not. The power has meant that I can not use Android and have gone back to WM for now. I used 2 batteries yesterday and ran out of charged batteries by 6PM! It should last over 24hrs per battery.
jonners59 said:
A little unkind arrrrghhh... The issues I raised in this reply were immediately after having managed to get the device working. And yes, I know some are in FAQ, though no solutions to most and many are not.
The power issue and the no ringtones options are not. The power has meant that I can not use Android and have gone back to WM for now. I used 2 batteries yesterday and ran out of charged batteries by 6PM! It should last over 24hrs per battery.
Click to expand...
Click to collapse
Well I'm glad you have such strong opinions about how this project should be. Keep making demands, it's very helpful...
Anyhoo, this project is for TESTING PURPOSES, it's not ready for prime-time yet. Have fun with it, but don't think it's meant to replace WinMo.
Also, all of your questions have been answered before - maybe they're not all in the FAQ, but most are. However, every single question you've asked has been asked before - use search!
arrrghhh said:
Well I'm glad you have such strong opinions about how this project should be. Keep making demands, it's very helpful...
Anyhoo, this project is for TESTING PURPOSES, it's not ready for prime-time yet. Have fun with it, but don't think it's meant to replace WinMo.
Also, all of your questions have been answered before - maybe they're not all in the FAQ, but most are. However, every single question you've asked has been asked before - use search!
Click to expand...
Click to collapse
Oh, yes, sorry, I am a bit forceful.
Actually, the device in Android has completely died. I have a blank black screen. Sad moment. I like the look, the feel and the way this project works, but it has a long way to go before it is a serious contender, sadly.
UPDATE: I plugged it in to my Laptop to effectively start over, and suddenly the PIN window appeared... We are back on. The ways and wonders of SW.
sd card
my girlfriend and i both have the same phone. I have a PNY 16GB sd card in my phone and she has a SanDisk 8Gb. I dont have the problem with android not reading my sd card and i used the cab file, but android wont read her sd card. did everything the same on both phones, so i am kinda thinking it is the maker of the sd cards.
edlokien said:
my girlfriend and i both have the same phone. I have a PNY 16GB sd card in my phone and she has a SanDisk 8Gb. I dont have the problem with android not reading my sd card and i used the cab file, but android wont read her sd card. did everything the same on both phones, so i am kinda thinking it is the maker of the sd cards.
Click to expand...
Click to collapse
I have heard this before, which is why I mention my card type in the thread
phone works fine, winmob works fine, if i use 4gb sdcard, android works, BUT
it android does not recognise sdcard(inside android),
if i use a 2gb sd card, inside android, the sd card is recognized.
When i use the 4gb is says sdcard not available,
format of both sd cards is the same, software is the same, android is the same.
for last: ANdroid is with both sd cards working, only inside android there is difference with both cards.
My experience and from what I have seen in my threads and searching is:
1. The SD card itself may make a difference. I have had and seen comments that some makes of card do not work or work as well as others.
2. The card should be formatted externally, i.e. gparted, HP's device or whatever to FAT32
3. The installation of Android should be done by downloading the zip to your PC/Laptop and then copying to the root of your SD card, then it tends to stand more chance of working.
I can second guess someone will contradict me, but I spent 4 months trying to get it working, including working with a developer... And following some advise this is what I found was the only way to make it work.
Give it a bash, but it is what ever works for you.
PS this is only a project so whilst the OS is absolutely fantastic it does have some things that do not work or work well. Good luck

Categories

Resources