Just thought this might be useful to some of the newer users, a list of what I see as the most commonly asked questions, and some misunderstood terms.
What is the difference between Nand, Haret and SD:
Nand; refers to the devices internal memory, which is NAND Flash memory, and is used to hold what is commonly called 'a ROM'. It is this memory which holds the Operating System, and can be 'Flashed' to change the data on it, once flashed it is persistent in memory, meaning that if you remove all power sources it will not lose this data, this is also known as 'Non-volatile Memory'. Nand Flash refers to a specific type of Flash memory, and gets it's name from the way the memory cells are constructed.
SD; Refers to the MicroSD cards we use in our devices, these are also Nand Flash but typically have slower transfer rates than the Nand Flash we have inside the device. typically used to store data, they can also be used to store the Android OS when used with Haret installs.
Haret; often confused with SD. It actually refers to Haret.exe, which is a program used to launch Linux systems from within another OS, such as Windows Mobile, think of it as a Virtual machine system, which allows users to run another OS. In our case, Haret refers to running Android within WM, it does not replace WM in Nand ROM, it does replace it in RAM however, but only until powered down, after that WM will boot from Nand next time the device is powered on.
What is my Panel Type?:
Panel; This refers to the actual LCD panel hardware, there are 3 types in use on Kaiser, and although Type2 seems most common, there are also Types 1 and 3. When running WM the panel type is autodetected and the correct settings are used for the display, however Android has no autodetect, so we must tell the OS which type we are using at boot, in Haret installs this is done with a line in Default.txt, in Nand it is set in the NBH we use to flash the kernel and other boot files needed to run Android. Display issues such as odd pixel colouration, streaks or lines on the display, white screen when exiting sleep, and other noticeable display issues can usually be cured by changing the panel type.
Other useful terms:
NBH; This is the file extension of a file intended for flashing to Nand, most commonly used to flash WM or Android, it can also be used to flash radio or splash screen.
Bootloader/tricolour screen; Both are the same, it refers to the screen display you get if you hold the camera button, and press power, on this screen are a few useful pieces of information, device type, (e.g KAIS130), SPL version, (e.g SPL-3.29.Hard), in the bottom white area it will say 'serial' or if connected to a PC, 'usb'. Remember to remove the SD card before entering Bootloader mode, as the bootloader also scans the SD for a file called KASIimg.nbh, and will run the updater utility if one is found.
HardSPL; This is a specially designed SPL that allows us to flash the Nand with an NBH file that was not signed by HTC, it also prevents itself from being overwritten, so that it is usually possible to reflash as long as we can get into Bootloader mode, this means we can, ( usually ), recover from a bad/corrupt flash.
Build and ROM; In WM terms, a ROM usually refers to a complete, ready to install, single file NBH, custom version of WM. However with Android we do not use the single file approach, and therefore we do not usually use the term ROM. Build is what we usually call a custom Android install. This is roughly equivalent to the WM 'cooked ROM', since each build is designed and built in a particular way, and may be any of the different android 'flavours'.
Flavours; Mostly used to describe the versions of android, these are, in historical order
1.1 - un-named, released feb 2009
1.5 - Cupcake, released april 2009
1.6 - Donut, released sept 2009
2.0/2.1 - Eclair, released as 2.0, oct 2009, and as 2.1, Jan 2010
2.2 - Froyo, released may 2010
3.0 - Gingerbread, scheduled release date, sep-dec 2010.
Odex'ed: As stock, android builds are odex'ed. Odexing involves generating an odex file for each app, which slightly lowers the memory used by the system, and may also speed up execution of apps, the downside is that it is difficult to modify odexed builds in order to tweak or theme them.
DeOdex'ed: a deodexed build is one in which the odex files are moved into the apk's, which slightly increases the memory used by /system, but allows modifications and tweaks to be used.
Deodex Vs Odex: Odex uses less space in /system, boots quicker, especially the initial boot after installation, however themeing is impossible, and various tweaks and modifications probably won't work. Deodexed uses more space in /system, has a slower initial boot, subsequent boots are much quicker, but may be a little slower than odexed, theming is a lot easier, as are modifications and tweaking of the build. ( most custom builds are deodexed due to the ease of theming and modifying ).
Bootsplash/Bootanimation:
The bootsplash is the static picture that appears as soon as you boot the device, usually is stays for 20 seconds or so before being replaced by the scrolling text showing Linux is booting.
The Bootanimation is the animated screen you see after Linux has booted, and usually loops until Android is loaded.
Sim Pin/SIM lock:
SIM Pin is often confused with the SIM lock, the SIM pin is the code you have to enter before using the phone when you start it up, this code is stored on the SIM card itself, and until recently caused a lot of problems, since Android could not decode it properly, this has been fixed in some flavours, Eclair and Froyo, but is still an issue in older flavours, such as Donut.
Sim lock also known as provider lock is a method used my phone service providers to ensure that you only use their service by locking the phone so that it only accepts that providers SIM cards, this lock code is stored on the phone, and may be unlocked by entering a code, or by bypassing it using unlocking software, once unlocked the phone will accept any other providers SIM card.
PUK the PUK is the Personal Unlock Code, and is a code that unblocks a SIM that has been blocked by too many unsuccessful attempts to enter the Sim Pin code, ( usually 3 attempts), this code must be entered to unblock the SIM card, usually the PUK is provided with the SIM Card, however if it is lost then some providers may give you the code, if the SIM has been registered by you.
Please feel free to add to this
Back to Windows Mobile:
If you need to reflash Windows Mobile, for whatever reason, these are my preferred methods:
I recommend using a Card Reader and MicroSD adaptor for working with SD cards, it makes life so much easier than relying on the kaiser to transfer and rename files, since most of us are used to handling files in Windows.
Method 1
1. Download a Stock shipped ROM, do not go crazy getting the latest custom 6.5 ROM, in my experience these often cause problems, if you want to go to Custom ROM's then flash stock first.
2. Extract the RUU_Signed.NBH file from the .exe, ( I use 7zip for this, but other archive utilities my work, winzip, winrar etc), rename the file to KAISimg.nbh and copy to the root of a freshly formatted SD card.
3. Insert the SD card in your Kaiser, pres and hold camera button while pressing power, ( you only need to press power briefly, but keep the camera button pressed until you see the tricoloured screen).
4. Once you get the tricolour screen, ( bootloader ), it should change to a grey screen with blue instructions, basically, press the power button and let it flash.
5. Once flashed, simply pull the battery/press reset and let it go through the first boot process.
Troubleshooting
Common problems with this method are that it will just not recognise the flash file, leaving you at the bootloader screen, this is usually caused by wrongly formatted sd cards, the card must be formatted FAT32. Other reasons are file name issues, make sure you have not accidentally mistyped the filename, or renamed it as kaisimg.nbh.nbh.
Method 2:
If Method 1 fails then the alternative method is USB flashing:
1. Disable Activesync, by unchecking the 'USB' option in Connection settings.
2. Remove the SD and SIM cards from the Kaiser.
3. Press Camera+Power to enter Bootloader.
4 Connect the usb cable, ensure that is says 'USB' at the bottom of the screen.
5. Flash the Stock ROM, usually by double clicking the downloaded stock ROM exe file, allow it to flash, and wait until it is finished before removing the USB Cable.
Troubleshooting
There are a few potential issues with this method also, if this method fails try another stock rom, the last shipped ROM from HTC was Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, this is a generic stock 6.1 rom and should be compatible with most if not all kaiser variants.
Useful Links:
ThoughtlessKyle's Why my Wifi doesn't Work Invaluable Information on recent WiFi Issues, A 'Must Read'......
LCD Panel Information
Tinboot thread ( the thread that launched Nand flashing on kaiser ).
SuperJMN's Android Issues roundup thread ( common problems, as yet unsolved )
Adding language support
Miscellaneous Notes.
Radio Version
Just as in Windows Mobile, Radio Version seems to play as vital a role on Android.
There are a number of problems that may be related to radio version, and just as in WM, the effects are sometimes surprising.
Audio: yes, just like WM the wrong radio version can cause audio issues, ranging from no audio, to more subtle issues such as call audio not working, even though all other audio events work fine.
Wifi: no surprise really, the radio stack controls wifi as well as the more common phone/network activities.
Data/Network: Obvious one, but there are a number of complicating factors here too, geographical location seems to affect radio version, for instance, in the USA, 1.71 radios may offer the best signal, and data rates, while in Europe, using 1.71 may cause a lot of 'No Signal' issues, where the phone seems to drop off the network, the solution is usually an older radio version, in the UK 1.65 seems the best choice for most users, I have also had reports of 1.65 being the best for South Africa, Asis, while Australia seems to do better on 1.70 or 1.71. This may be due to the technology in use in those countries.
GPS Maybe, not sure about this one, had at least one report that a radio downgrade from 1.71 to 1.65 seemed to help with GPS, as far as I am aware the GPS and the Radio stack are not related, but who knows for sure?
Great guide! I was thinking about making similar one myself, but couldn't find free time
I'll maybe try to add something this weekend
hello maybe a stupid question
what is the differents between odex and unodex
sorry for my bad english
kisses
Rose
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
CassandraN said:
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
Click to expand...
Click to collapse
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Thanks for the FAQ, it is extremely useful to noob or semi-noob like I am.
Thanks, that's why I decided to start it, and if one person finds it useful, it was worth it
say it with me class
Click to expand...
Click to collapse
This is just hilarious
BTW, I tried some of the reboot apps in the market, non of them seemed to work (on 2.1)
the original reboot menu that you get when you hold the power button did not work at all. it just hangs on the loading circle.
In Froyo however, things are a bit different. the reboot option shuts downs the device instead, I did not try any reboot app yet
Any ideas about this zenity?
zenity said:
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Click to expand...
Click to collapse
I usually battery pull (I lost my stylus and the cheap replacement won't fit in the reset hole ), but I still seem to have problems.
I think my problems are due to a rogue app eating all the CPU. My suspicions are Twitter or Swiftkey. The phone becomes so unresponsive that sometimes a hard reset is the only way to make it useable again. I'll try to avoid it in future if I possibly can.
Tried taskiller? Useful for watching your memory, and killing tasks if needed, osmonitor is also useful for, well monitoring the os
I have noticed that the system does get very unresponsive at times, and it usually means low memory, try an eclair build if you are using a CM6 based one, I usually get about 30+Mb free in normal conditions, and if things start to get too slow, well a tap on the taskiller widget sorts that out
@Duke911:
As far as I am aware there is no real reboot option, in any build, I think it's a kernel issue, or perhaps just not implemented correctly, the safest option is a power off, which performs a proper shutdown, I do know there have been a few issues with data corruption that may be associated with using reboot, or the reset button, since these may cause the system to shutdown to rapidly to sync any data that may be cached, it's similar to pulling an SD card out of the computer, there may be data left unwritten in cache, which is why there is a nice safe removal option
This is a cool wiki for Kaiser Android users! Thank you!
By OP request, I am making this thread a sticky and making some adjustments to the forum. Please PM me if you have any requests. Thanks.
Precious work, Zenity!!!
video call anyone?
Is there any chance of getting a build to support video calling?
Video calling will need working front camera driver at least, which is not supported yet, I do not know if anyone is actively working on this, however, at some time, someone will take up this challenge, just as they have with other things which did not work previously
Sent from my HTC Dream using Tapatalk
hello..
I just want to ask about polymod and cyanogenmod.
what is the function, are they different from eclair or froyo?
thanks ^^
CyanogenMod builds are all Modifications of base android releases, these are complete rebuilds of the system, and include many improvements over the original release.
Polymod is an Eclair Mod based on OpenEclair 1.3 and is modded in a different way to Cyanogen's methods and style.
Most Eclair and Froyo builds are ports and modifications of Cyanogen bases, ( in fact I don't think there are any Froyo builds that are not CM6 based).
For Donut things are different, most builds are modifications and ports of official releases, such as Myn's Warm Donut.
Related
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.
I'm having some lingering issues with my EVO even after running OTA updates. I am running a rooted stock ROM, currently software version 1.32.651.6 (I have not attempted the latest OTA update yet).
In particular are two problems - SD card issues have remained even after the OTA update. This was present even before rooting but after installing the first update (I went to a "full-service" store on opening day and they set it up themselves, assuming everyone would want it - luckily I could still get root). Issues include the Camera application reporting permissions problems randomly when trying to save pictures to the SD card, HTC's music application freaking out and coming to a near freeze trying to crawl the SD card during one of its troublesome spurts, and files disappearing from file explorers. So basically run of the mill, pre-first-OTA sd card problems. But occurring after the update and both before/after rooting.
Second is a problem with the camera itself. When first booting, HTC's included photo/video application will instantly crash after showing the camera icon on the black background. Google Goggles freezes for about 10 seconds then reports it was unable to connect to the camera. After the phone being on for about half an hour, these issues (seemingly) go away until the next reboot.
Last, and least frequent but still troubling, is a problem with the device powering on. At least twice I have been unable to get the device to turn on after powering it off, forcing a pull and replace of the battery to get it working again.
As far as I know, all of these issues could be either hardware or software. Even the power problem - my best guess is that the phone never powers off fully, but is instead locked inside of a deep sleep state and thus can not turn on until a battery pull forces the entire system off.
The questions being - first, are there any known solutions to the above problems? I have found many threads in particular regarding SD card issues, but none that seem to report these problems post-update. The others I have seen little to nothing about.
Second - if there are not known solutions, would it be prudent to return the phone as it may likely be a hardware problem?
Since it seems I'm forced to take the last update if I get a replacement, I may likely have problems getting a full root back. I'd like to avoid that if possible - having root works wonders for doing application development using non-native (unexposed) API's (Which - side note - since I'm developing for 2.1 at the moment, other than hacking for direct access to a Surface, does anyone know of a _fast_ way to do direct blits from native code? glTexImage2d is insanely slow).
Thanks all any help. Again, apologize if any of these are solved and gone problems, but I wasn't able to procure anything myself.
I'd go for the replacement, sounds like a defective unit..
Be sure that the folks here at xda will get root working regardless of OTA.
replace the unit, i'm very particular about my phones, if there is anything wrong with it I replace it.
I too have the SD card issue, I have updated, i have rooted, re-rooted, flashed new rom, different roms (fresh and sd) and it has always given me the sd card issue. Sometimes it wants to be a pain and not work at all, sometimes its good for at least a week or two. I am waiting for a little longer to make sure when I get a replacement its a newer version.
SD card permission errors --- POSSIBLE FIX
I hope/think/believe I fixed this error for those interested, I use my EVO for work and need it to work without a hitch....
Here goes (**Note i am a noob with smartphones with a dangerous amount of IT knowledge - disclaimer for those brave enough to browse around the root files and SD card files; I am not responsible for you bricking your phone, I am only trying to help those in need and putting in my 2 cents_)
Download and open the app ---> Root Explorer (or any other root explorer for that matter) from Android market.
Once Root Explorer is open (look up top/left it will say) Mounted as r/o (means read only) - press the white button to mount it as r/w (read & write)
Press and long hold on the SD card directory (folder) - you will get another window from which you must select the permissions option.
Under top option USER - check all marks -- READ WRITE AND EXECUTE & click OK.
VERY IMPORTANT - Click on the (white button) Mount as r/o to write protect your root files on your phone again.
I just applied this fix about 45 mins ago and seems to be working......updates to come if issues persist or re-surface. (**Note I could not see photos or play music and some apps were also giving me FCs (intermittently) due to permission or write errors to SD card; and now it seems to be working like nothing ever happened.)
What I have ::: stock ROM on EVO supersonic with recent HTC updates applied - standard 8Gig SD card provided with phone / had rooted but put back stock ROM for preference issues.
Hope this info helps some folks...very frustrating issue.
Cheers
SD card permission errors --- POSSIBLE FIX
ONE LAST SIDENOTE COMMENT -
I transfer data to my PC often (running Win 7 32bit_)
It is crucial that you right click on "safely remove hardware" icon on the lower right side (next to date and time) and WAIT until windows tells you
..."It is now safe to remove your hardware" --- I was just taking the plug out when done and it appears as if that could have started or compounded these issues with the SD card.
I too get the could not connect problems at times. And I have lost access to the SD card a few times. Some say its Fring that causes the problem. But after removing it I still have camera issues. I noticed that having the LED Light on while trying to open the camera will cause this problem.
I am running CM6 RC1 so this is to be expected from Release Candidates. Sit tight. It will get fixed.
Well after a full 24 hrs...no issues with the read write error on my EVO SD card, I think that when the phone is removed from PC incorrectly (i.e. pulling USB cable out in mode other than "Charge only" i.e. HTC sync, Disk Drive, Internet sharing - it causes it to "corrupt" the permissions on the SD card - It is still working like a champ and i am waiting impatiently for my EVO Froyo update ... feedback appreciated for those whom tried this fix and had it work....txs
@LF142
Hi there. So I followed all of your instructions above and downloaded Root Explorer. However, every time I change the permissions, they don't save. User, Group and Other is always switched off at root level. Do you think this may mean my SD card is corrupted?
I rooted it with BakedSnack.
I now want to un-root it as I miss taking shots, looking at my shots, listening to my tunes etc.
But I want to keep all my apps. All my texts and everything else. Whats the best way to go about this? I am also a bit of a n00b and I apologize if this is in the wrong forum, but when Froyo releases tomorrow (apparently) do I have to unroot to receive the update?
Thanks
Currently I'm running on Cyanogen mod6, and I had a few questions regarding Android/Kaiser interaction. As it sits, Android works great, minus a key problem: Whenever I make a phone call, the battery seems to drop drastically, and I get the "low battery" notice approximately 3 minutes into each phone call, even after the phone has been charged for an extended period of time. I've left Android at bare basics, virtually no apps, and still the same problem. Now I've searched and searched, and haven't really found a topic that relates to this particular issue (maybe searching under wrong keywords...?)
Also, I was thinking of flashing back to winmo (sadly, due to this very problem), and yet, I am unable to do that. I've put the appropriate files on the sd, and it seems to bypass the Kaisimg, etc files. Could it be that my android files were installed on the phone's memory and not my memory card's root memory? Hopefully that makes sense.
But if anyone can help point me in the right direction, this would be greatly appreciated.
It sounds like a failing battery. Can you flash it back to Windows Mobile to see if it behaves normally?
I'm very sorry you had that problem.
I've tried flashing it back. I'm still new to flashing ROMs, so please bare with me.
I've put the appropriate files on the root of the SD card, tried the power+camera+reset method, and got the error message of no image file. I even tried flashing everything to factory default, and still the same result...so unfortunately, I haven't been able to flash it back to WinMo either.
ysiphu said:
I've put the appropriate files on the root of the SD card, tried the power+camera+reset method, and got the error message of no image file. I even tried flashing everything to factory default, and still the same result...so unfortunately, I haven't been able to flash it back to WinMo either.
Click to expand...
Click to collapse
I prefer flashing via USB-chord, and found that fastest way to get WinMo back is to get some random ROM for Kaiser and boot phone with reset button while pressing camera (to get into bootloader) and then just normally flash using windows programs. Just be in bootloader when you launch KaiserRUU.
This also applies, if you do changes into kernel with hex editor (like modify keyboard settings and such). Fastest way to flash in my opinion.
And since phone is connected into computer whole flash process, it cannot shutdown afaik, but cannot guarantee it since I don't have dead battery.
it looks like it might be the battery. Flashed WinMo back on successfully, and still the same problem. Dammit.
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.
This was the kernel thread but it is so full of question that it was renamed to Question and answer!
before ask search in the forum.
Guide to install:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand (Flash the phone)
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret (Dual system windows/android)
If you have "install module error" please install the android update on sourceforge. Read more here:
http://forum.xda-developers.com/showthread.php?t=848921
Awesome job on this l1q1d, i finally got around to getting the git set up on my computer yesterday so in can modify and compile so i'll try and get coding when i have some free time Thanks for all your efforts.
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Here for testing...
Glad to see this thread started!! Thought dev for Kaiser had seen its end. I'm no coder but can help with testing.
Hey L1q1d, this isn't by any means vital but i find it annoying and don't know if any other kaiser users have found this. If i turn the phone on and don't unlock it before pressing the power button again (i.e. just to check the time), there is a relatively long delay before the screen turns off. If i unlock the phone and then press the power button it turns off instantly. I have attached the logcat from when the phone is turned on and then turned off, i have also indicated where it locks before turning off the screen. I'm looking into it but if you have any pointers or don't experience this with your device let me know please
-Arturo- said:
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Click to expand...
Click to collapse
Ok scratch that looks like the problem has been caused by having data on ext2 partition.
The kernel 2.6.32 runs way better than previous, but i have a persistent fail that knocks out the screen, at start i can see a message saying "msm_i2c.0: Bus still busy, status 2100m intf 100" and another more saying "msm_i2c.0: Error waiting for notbusy". ¿It is a common fail or it's only mine?
Hi
the problem is I do not belong here
I tried several variants android
the Caller ID does not work
basic configuration of network settings, but it is not good
if you want to set up an error message is incorrect sim, and it is no longer a network
something that is not a solution?
L1q1d, good work. Some of the changes you have made, such as nand, affect all of the related phone types. So, you might want to at least mention them on the vogue kernel thread. On the other hand, the keypad and battery code is not used by vogue. As you know, Polaris uses the same battery code as Kaiser.
I'm thinking two changes for battery code:
a) going back to max voltage and current instead of average, to work better with poor batteries. My old battery sometimes has deep dips in its reported voltage, causing a recalibration to 5% capacity when it really has more like 40%.
b) the recommended capacity calculations at high and low calibration points should be "recommended = battery_capacity - (new - old)" instead of "recommended -= (new - old)". As things are, the recommended value is pretty close on the first calibration, but any subsequent calibrations apply the same correction over and over again, making the recommended value go negative or insanely positive. Of course I cannot remember the names of the variables.
@L1q1d
This is a nice idea to make this thread for kaiser users.
Today I tried the latest kernel 4-10-2010 with fresh froyo 2.2.1 (nand installation). First the system works well. But after installing the ADW.Launcher from the market and after a reboot I got always chrashes from this launcher and I never had this before with any other kernel and the launcher version has not been changed. So maybe I have the same issues then Arturo. Then I tried the app task killer but it chrashes after starting it (same problem). I think these problems could be memory issues in the latest kernel version.
Keep going on your nice work for kaiser
l1q1d I have just got a framework exception and as usual 90% of apps don't work anymore. It occured using the latest kernel.
Also I still keep getting those launcher pro redraws It didn't happen while using the 2.6.25 kernel. Has the memory management been changed in the new kernel?
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
n2rjt said:
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yes I do. I ripped the compcache.sh file from latest dzo's fresh froyo build.(I remember reading Kalt Kaffe's post about getting compcache to work with the newest kernel a while ago so I assumed that it has been sorted out and we can enable compcache with new kernel) I'm on NAND at the moment with both system and data. I've tried system on nand and data on ext2 partition but the launcher redraws were killing me, every time I opened opera mini and then closed it the launcher was closed and I had to wait for it to load into memory again.
I'm back to system and data on nand at the moment with new kernel and it's much much better but still it happens from time to time. I've never experienced launcher redraws with the old kernel so I don't really now what;s wrong.
About the 4th partition....you mean swap, right?
When I was on nand +sd card I had 3 partitions 1) fat 32 then 2) ext2 about 30 mb(I don't know what for is the first ext2 partition but i remember that i couldn't install data to sd card with only one ext2 partition) and finally 3) second ext2 partition for data about 300mb. So by creating the third ext2 partition I would activate swap in compcache? I've never tried as I heard that it might used up the sd card faster. also I only have two sd cards 6gb(class 4) and 12 GB (class 2) so I think i would probably need class 6 for swap file?
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
n2rjt said:
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
Click to expand...
Click to collapse
Excellent N2rjt i think you just found the cause of my issues. I updated my system with the modules you have linked enabled compcache again and then i entered the "FREE" command and swap shows zero. So the compcache is not working this must be the reason for constant launcher redraws. Now what could be the cause of "broken" compcache?
Sent from my Full Android on Vogue using XDA App
lzo modules are now included in the kernel, you need only ramswap. probably compcache script have some problem with it.
Ok, guys I got a compcache.sh file from the latest dzo's froyo and compcache is finally enabled. I will be testing the device to see whether the issues are gone. Thanks for your help.
Bug: white screen, Android still alive
How I got a white screen:
AT&T Tilt-flavored Kaiser, latest kernel and dzo's Fresh Froyo, both built from current git code.
I was typing on the hardware keyboard, actually entering a message for xda-developers. I wanted to say "dmesg | grep ds2746", but couldn't find the "|" symbol. I remembered that the hardware keys for the soft keys (between R-T and between I-O) have some symbols mapped to them, so I was trying different Fn- and Symbol combinations of those keys.
Eventually I hit Fn-(Left soft key), and got a text screen with dmesg logs.
Okay, how to get back to a graphical screen? I tried a few keys that didn't take me back, then had a brilliant idea, hit the red hangup key.
That blanked the screen, but when I hit other keys to wake up, I had a white screen. Yet, adb logcat verifies that the phone is still running Android, and it is even responding to my touches, just I can't see anything except white.
Edit: can recover by using Fn- keypad right soft key.
Battery issues?
If anyone has battery issues, please open a terminal, and type this:
> dmesg | grep ds2746 > /sdcard/dmesg.log
and send the dmesg.log file.
Thanks!