Develop Bugs

applytheme - Tool for universal themes.

I'm working on a tool I'm calling "applytheme". Basically you create a theme.zip, stick it in an archive with the included applytheme binary and update-script, sign it, and it will update the files on any of the Dream firmwares with the ones you've provided.
There are some limitations currently:
It can't yet determine space required before-hand, so you may run out of space in the middle. If you do, you can just restore the original theme with the restoration update.zip.
It can't add files - only replace existing ones.
The original files are stored in /data/original_theme.zip, which will eat your /data space, but only the replaced files are stored.
This version is a test release and may or may not have bugs. Be sure to back up your phone before trying it.
Please consult the example for figuring out what to put in the theme.zip, but it's basically full-path-to-filename-you-want-to-update/full-path-to-file-you-want-to-replace
So if you wanted to replace "assets/images/android_320x480.png" (the boot screen) in "/system/framework/framework-res.apk", you would have a file in your theme.zip called "system/framework/framework-res.apk/assets/images/android_320x480.png".
Case matters - please use the correct case (which is usually all lowercase).
Example theme (replaces boot animation only, with a cupcakedroid):
applytheme-200902090018-example.zip
Restoration update.zip (restores from /data/original_theme.zip then deletes original_theme.zip):
theme_restore-200902090018.zip
Source code (for developers or other curious people):
applytheme-200902090018.tar.gz
EDIT: 200902082117 fixes a couple of stupid bugs in 200902081755 :/
EDIT: 200902082316 removed extraneous/incorrect free space check; noticed that the update script stuff is significantly more stupid than I'd thought - update scripts should work now.
EDIT: 200902090018 close files so space can be reclaimed during patching
Reporting problems
If one of the applytheme updates fails, while still in the recovery mode please do the following:
Press ALT+X to get to the console
Press <enter> to get to the prompt
Type cp /cache/recovery/log /sdcard/recovery.txt
Type df >> /sdcard/recovery.txt
Type reboot to reboot.
Send the recovery.txt from the SD card to zinx <AT> users.sourceforge.net with the subject "applytheme error log"
If I don't have the log (or at least the error message from the log), I can't know why it's failing, and can't do anything to fix it.

I am looking at your post but don't see the benefits of doing it like this. you would still need to do this every time you add a theme or just a image and you still need to sign it or am I just not seeing the benefits of using it

kron2 said:
I am looking at your post but don't see the benefits of doing it like this. you would still need to do this every time you add a theme or just a image and you still need to sign it or am I just not seeing the benefits of using it
Click to expand...
Click to collapse
Current themes replace the whole system.
If you change as single file in /system/app/Browser.apk (say, an icon), you have to replace the whole file.
You don't have to do that with applytheme, so you can replace the icon no matter what firmware is being run.

This would be great themes wont need to be converted any more.

manup456 said:
This would be great themes wont need to be converted any more.
Click to expand...
Click to collapse
Indeed, for example:
More Vintage Less War via applytheme (theme by manup456 )
EDIT: Oh, I should note I tested this one with RC33. Didn't bother to time the progress meter though, so just wait until it tells you to reboot with home+back.

This looks like an amazing tool! I'm surprised more people haven't checked this out.
Let me get a few things straight before I give it a shot.
Let's say I was updating some basic images in the framework-res.apk. All I need to do is:
~Download your applytheme-example.zip
~Open up the theme.zip (remove current folders inside)
~Create the folders system\framework\framework-res.apk\res\drawable\
~Add the icons I've changed, with the exact original names
~rename applytheme-example.zip to update.zip
~load onto SD card and load onto phone as usual
~success?
I don't quite understand the backup system...
When you load the update onto the phone, it backs up the images you're replacing and puts them into a \data\original_theme.zip?
Then, if for some reason you want to revert to the original theme, you simply run the theme.restore.zip on the phone and it grabs all the \data\original_theme.zip images and places them in their original location?
Also, if the theme you're installing is a few megs, then the \data\original_theme.zip will get rather large, no? Will this cause any issues?
Thanks!

The steps are a bit more like this:
Download applytheme-example.zip
create system/framework/framework-res.apk/res/drawable/
add the files you've changed
create a theme.zip with the files above - MAKE SURE IT HAS THE PATH, STARTING WITH system/
replace the theme/theme.zip in applytheme-example.zip with your new theme.zip
sign the applytheme-example.zip with the replaced theme/theme.zip
put it on the SD card as /sdcard/update.zip and update as normal
success! (unless there was a problem during patching, then it may be partially applied and you can use theme_restore.zip to fix it)
MOONSSPOON said:
When you load the update onto the phone, it backs up the images you're replacing and puts them into a \data\original_theme.zip?
Then, if for some reason you want to revert to the original theme, you simply run the theme.restore.zip on the phone and it grabs all the \data\original_theme.zip images and places them in their original location?
Click to expand...
Click to collapse
Yep.
MOONSSPOON said:
Also, if the theme you're installing is a few megs, then the \data\original_theme.zip will get rather large, no? Will this cause any issues?
Click to expand...
Click to collapse
It can get large, yes, but keep in mind that it's only the original files that have changed that get put in it. Most themes right now are much larger .zips than they actually are, because they include much more than what was changed. If it gets too large to fit, the update will just fail part-way, and you can restore using the theme_restore.zip.
You can also delete it if you don't want to restore.
If you have any better ideas for any of this, I'm definitely open to suggestion - It's not anywhere near finalized yet

Great work. Definitely a step in the right direction for generalizing themes and allowing them to work with any build without modification.
Some thoughts for the next steps... Perhaps do a once-over of the files in theme.zip and compare their sizes with the existing files? This would just about double the time it takes to install, but should catch any out-of-space issues before any replacements had been made. Alternatively, perhaps there's a way to detect failures and automatically revert and display an error?

MasterBunnyFu said:
Great work. Definitely a step in the right direction for generalizing themes and allowing them to work with any build without modification.
Some thoughts for the next steps... Perhaps do a once-over of the files in theme.zip and compare their sizes with the existing files? This would just about double the time it takes to install, but should catch any out-of-space issues before any replacements had been made. Alternatively, perhaps there's a way to detect failures and automatically revert and display an error?
Click to expand...
Click to collapse
Automatic reversion can be done.
The update stuff is too stupid to let me display an error (Seriously. There's no way to display a message to the user. All I get is the unchangeable 'Failed on line 3'.) - an error is kept in /cache/recovery/log though.
Checking the file sizes would indeed take twice as long - everything is compressed, so I'd basically be creating every file touched, but discarding the output, then creating it all again. It already takes quite some time, and it should normally have enough space free, so I would prefer to go the automatic reversion route if people don't want to have to use the theme_restore.zip after a partial update.

So I tried throwing in your more vintage theme, but I get the error failed on line 4.
I feel like a leecher posting this message, but explain to me how it's done.

APrinceAmongMen said:
So I tried throwing in your more vintage theme, but I get the error failed on line 4.
I feel like a leecher posting this message, but explain to me how it's done.
Click to expand...
Click to collapse
Should just be putting in it; can you post the /cache/recovery/log from after it fails? May need to copy it somewhere before rebooting.
I expect it's due to lack of space, but it was ok here :x

In an effort to make it a bit easier initially, I've written "toapplytheme". It takes a theme update, the update it was based on, and outputs an applytheme compatible theme.zip - You still have to put in in theme/theme.zip in the applytheme update zip and re-sign it, though.
If you use something other than the update it was based on, you're going to end up with a lot of extra and/or missing files, so don't do it.
Ex:
Code:
toat MyExcellentTheme.zip JFv1.41_RC33_light2.zip theme.zip
toat-200902091613.zip

Worked for me
I have an ADP1 w/the latest JFv1.43h, I extracted Rusty Metal (from the RC33 version, using you tool). Put it there on the example, signed it all and voila...
The only thing I noticed is that the background did not get changed, but that is a minimal issue (and easily fixed).
Great job Zinx, I don't understand why all theme designers don't use this tool.
A matter of time I hope?

DanOtero said:
I have an ADP1 w/the latest JFv1.43h, I extracted Rusty Metal (from the RC33 version, using you tool). Put it there on the example, signed it all and voila...
The only thing I noticed is that the background did not get changed, but that is a minimal issue (and easily fixed).
Click to expand...
Click to collapse
I just applied Rusty Metal to my G1 using the standard way (not this tool) and the background doesn't install with it anyways, so it's not a problem with this tool, but the theme itself simply doesn't include it.

[Q] Latest xdandroid for touch pro 2 how-to

This is my first for anything like this. I have a Sprint HTC Touch Pro 2, and want to put the latest version of XDANDROID on it. But, have no clue which version or where to start. I would like to eventually get in to building on my own. Could someone please help get me started?

TheCasper said:
This is my first for anything like this. I have a Sprint HTC Touch Pro 2, and want to put the latest version of XDANDROID on it. But, have no clue which version or where to start. I would like to eventually get in to building on my own. Could someone please help get me started?
Click to expand...
Click to collapse
to get started, it really doesn't get any simpler than downloading the latest FRX03 from here:
http://sites.google.com/site/androidport/downloads
(i'd recommend the RAR version, so you can unzip it into your SD card faster)
after that, just use WM's file explorer navigate to andboot and run haret.exe and you're "done"
----
(optional) with a little bit of more effort, go into the top sticky of this forum, and update to the latest Kernel (1253). the current Kernel in FRX03 from Dec 20 is (i believe) 1232.

It's sort of that easy, but I had this same question before I did it too. It would have been nice if the FAQ said this explicitly.
If you download the rar archive, it will extract out in its own subdirectory, e.g.
XDAndroid2.2Froyo.XXxxXX/andboot/...
The first thing I do is move the andboot subdirectory to the root of the SD card.
The next thing is to edit the andboot/startup.txt file to match your phone. I guess you can use the XDAndroidStartup utility to take care of this instead, but the first time I tried that it failed because of that silly runtime dependency.
If you want to use the startup utility, and it gives you an error and refuses to run, you need to install the updated net framework like it talks about on this page:
http://sites.google.com/site/androidport/startup-utility

Thanks guy I will give it a try and post if I have questions. I love the design/setup of my TP2 but I hate the windows OS.

Need more help My phone is getting stuck and the XDANDROID start up image/video thing

TheCasper said:
Need more help My phone is getting stuck and the XDANDROID start up image/video thing
Click to expand...
Click to collapse
Just let it do its thing, boots can take 5-10 min!

Kind of got it working, but have no idea how to use it fun stuff.

quick question, do I always have to have the sim card out when running ANDROID?

TheCasper said:
quick question, do I always have to have the sim card out when running ANDROID?
Click to expand...
Click to collapse
If your phone is in GSM mode, you'll want it in. Check your startup.txt, you'll need force_cdma=0 in there.
If you're on CDMA, I believe you do have to have the SIM removed, yes. Also, the above command should have a 1 instead of 0.
^^ I'm not positive about that piece, but I do know that Android on our phones will only recognize one or the other - GSM or CDMA. Maybe we'll get it to recognize both one day, I saw an entry for it in the RIL...

I do know that I have CDMA. Plus how do update the kernel, where do I put it?

TheCasper said:
I do know that I have CDMA. Plus how do update the kernel, where do I put it?
Click to expand...
Click to collapse
You simply replace your existing kernel and modules.
So delete the existing zImage/modules-xxxx.tar.gz, and put in the new zImage/modules-xxx.tar.gz. Don't rename the modules file, but be sure the zImage file is named just that - zImage.
The files go where you run haret.exe from - typically the root of the SD, or in /andboot.

UH-OH, not sure what happened. I reformated my SD card to do a new run since I found what I wanted. Now it seems like I can do everything but make calls in WM6.5. What do I do

TheCasper said:
UH-OH, not sure what happened. I reformated my SD card to do a new run since I found what I wanted. Now it seems like I can do everything but make calls in WM6.5. What do I do
Click to expand...
Click to collapse
Android should have no effect on WinMo (assuming you're using haret/install on your SD). Plus, this really isn't a place to get help with WinMo.
Do the usual - soft reset, hard reset, reflash of stock ROM.

arrrghhh said:
Android should have no effect on WinMo (assuming you're using haret/install on your SD). Plus, this really isn't a place to get help with WinMo.
Do the usual - soft reset, hard reset, reflash of stock ROM.
Click to expand...
Click to collapse
I know, I'm trying to put android on it and I am using haret from the SD card. I'm just not sure if this is will effect android or is a common problem. Thanks though, I have been going through those things while i wait.

Installing Android without SD, to test NAND?

Is it possible to install Android on Kaiser without SD? Has anyone investigated bundling the /system partition with tinboot so the whole thing is installed with a single KAISIMG?
I ask because I have one Kaiser whose SD reader is broken. If I could install more than a kernel, I could try risky changes to fix the NAND driver. If I brick the phone or kill its flash, it's no big loss.

No, you can't do it now, maybe i can suggest you to look after a method do dump the nand after install and use it as kaiser image

Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?

PoXFreak said:
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
Click to expand...
Click to collapse
I don't think thats l1q1d idea... perhaps a complete nand dump, and reflash it to another kaiser.
The kernel and partitions must be configures before the dump...

I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.

This is possible, in fact there was a time where an empty img file was being incorporated into the NBH where on a windows NBH the system files would normally be copied. A windows NBH consists of a number of parts, I can't remember what they are all called right now, but they can all be merged using NBHmerge. I can't give you specific instructions but there's no reason why it can't be done, not sure it'll be much fun though!

n2rjt said:
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
Click to expand...
Click to collapse
pre-beta that you're testing on HTC What ??

daedric said:
pre-beta that you're testing on HTC What ??
Click to expand...
Click to collapse
HTC Wizard. I have two of them, which I have named Radagast and Gandalf. It's my all-time favorite smartphone, although it is obviously even more obsolete than the Kaiser. I use one of them as my primary phone whenever Android is giving me fits. Right now I'm testing H3r7 beta 2 preview where the cook has adeptly squeezed WM6.5 into a tiny, fast, stable package.

If I knew that I wouldn't have given my Wizard away...
I thought Ham3r was finished when he hit 6.1 but I stand corrected...pfft.

help androidinstall.tgz
please share for me : file androidinstall.tgz 2.1 or 2.2 but must run wifi and 3G.
Send for me by: [email protected] thanks i come from VietNam

I think with the proper memory map Android could be installed via FrankenKaiser or something of that sort. Something that addresses the NAND directly through OEMSBL, bypassing the need for a HardSPL. Of course the phone would have to be CID unlocked to do this, but I think it's possible to install via CustomRUU if the mapping was done beforehand.
I have read somewhere that NAND marked as bad in the map still gets "written" to, meaning whatever is supposed to go there is put there and never read. Once unmarked the written info comes back, but that requires a full format anyway.
I say very possible...

I have stopped trying to do this, but wanted to record my latest thoughts in case someone reads this in the future.
I think the best way to install Android on a Kaiser that can't read its sdcard is to edit the initrd then use recovery mode:
* install adbd so it gets started in recovery mode
* allow the menu when sdcard is not installed
* change scripts to look for /data/andboot
* change recovery mode to mount /data partition to usb
Then, of course, you boot the kernel, use the menu, enter recovery mode, transfer androidinstall.tgz and androidupdate.tgz to /data/andboot, then install system, install updates, clear data, and run. If something doesn't work, adb shell or adb push can help.
I think it's too much work to be worth it on this old phone.

[Q] Question about build sizes

Hi All...
Maybe a dumb question but I need an answer.
I was looking through the rest of the builds on kingshui's sourceforge site and something caught me off-guard.
Apparently he has some /system builds exceeding 100mb (the one I downloaded was 103mb, 98mb in a tarball).
I know with standard kernels we can slide the partition marker to the right and gain some /system space, but I'm currently using Scoot's cache kernel: No partition changing allowed (I guess), but the kernel is so smooth and fluid with my kingshui build.
I guess my question would be this...
Can I remove apps from the app folder to shrink this build to the 100mb limit, or will this cause issues in the build itself?
Edit; it appears to be CGM 5.0.8 RLS11, which is Android 2.1 -update1
DURRR!

Still... it's better to answer for future generations.
The androidinstall.tar has at least on folder in it, named System.
It might have another folder in it, named Data.
It might even have other folders, ignore them for now.
Inside both system, there might be alot of folders (expecially in system), but one of them is called "App". Now, all the apps will be there, along with perhaps a .odex file for everyone.
You can move certains apps from /system/app to /data/app. (if /data does not exists, create /data and app inside it.) You can also remove things from /system/app, if you're not going to use them. Like, CMwallpapers.apk.
PoXFreak said:
Hi All...
Maybe a dumb question but I need an answer.
I was looking through the rest of the builds on kingshui's sourceforge site and something caught me off-guard.
Apparently he has some /system builds exceeding 100mb (the one I downloaded was 103mb, 98mb in a tarball).
I know with standard kernels we can slide the partition marker to the right and gain some /system space, but I'm currently using Scoot's cache kernel: No partition changing allowed (I guess), but the kernel is so smooth and fluid with my kingshui build.
I guess my question would be this...
Can I remove apps from the app folder to shrink this build to the 100mb limit, or will this cause issues in the build itself?
Edit; it appears to be CGM 5.0.8 RLS11, which is Android 2.1 -update1
DURRR!
Click to expand...
Click to collapse

Hey, I learn something new everyday!
I assume this would mean that if I needed to move apps from /system to /data, I would copy the files I wanted from /system/app and make a new folder for /data and put the apps in /data/app, along with the odex files if needed?
I did not know it was that easy. I always had a fear of ruining a build due o mis-matched apps being installed.

PoXFreak said:
Hey, I learn something new everyday!
I assume this would mean that if I needed to move apps from /system to /data, I would copy the files I wanted from /system/app and make a new folder for /data and put the apps in /data/app, along with the odex files if needed?
I did not know it was that easy. I always had a fear of ruining a build due o mis-matched apps being installed.
Click to expand...
Click to collapse
Be advised!!! Not every single package SHOULD/CAN be moved to DATA.
Examples:
Vending.apk -- Market... shouldn't.
Google*.apk -- Can't/Shouldn't
LatinIME.apk - I belive CAN'T.
Also... you never bumped into a release with the data folder already present ?
It's usually made so that you can remove apps by uninstalling them (Default launcher for example, in case you replaced it).
Also... why didn't you experiment ??

Sorry for the late reply, I got hung up in trying to memory map the HTC Raphael...
Anyway, I tend to think of it as "sacrelige" (sp) to mess with what others have already worked hard to build.
I will however take the "system_froyo_us_odex" package and modify it by changing the bootanimation.zip or wallpapers.apk to what I like. I have a CM theme pack (5.0.8 I believe), but I haven't gotten around to messing with it. It does however have a couple of certificates along with it, one being "manifest.cert", whic I really don't want to play with.
My Ubuntu machine doesn't like me since the latest kernel update to 11.04 and working on it has become a bear.
Que sera sera, another laptop needed...

PoXFreak said:
Sorry for the late reply, I got hung up in trying to memory map the HTC Raphael...
Anyway, I tend to think of it as "sacrelige" (sp) to mess with what others have already worked hard to build.
I will however take the "system_froyo_us_odex" package and modify it by changing the bootanimation.zip or wallpapers.apk to what I like. I have a CM theme pack (5.0.8 I believe), but I haven't gotten around to messing with it. It does however have a couple of certificates along with it, one being "manifest.cert", whic I really don't want to play with.
My Ubuntu machine doesn't like me since the latest kernel update to 11.04 and working on it has become a bear.
Que sera sera, another laptop needed...
Click to expand...
Click to collapse
It would be sacrilegio if you would dessecate a rom, and publish it as your own without credits. But for out own use, tweak away Just remember not to come asking on it's respective thread if the errors happening might be introduced with your tampering.
As for themes, it's not really my topic
About ubuntu... what machine are we talking about ?

An old Toshiba with an intel proc and realtek audio. I think it has to do with the touchpad (alps) because the system will freeze until I touch it.
As far as that CGM build, I can't use it becaus I'm set up for Froyo and that build is 2.1 update 1.

"Fixed" build.prop file for Kaiser (Attached tarball)

!ALWAYS make a databackup.img on your device BEFORE making any changes!
Hi all!
For the past 3 weeks I have been making small changes to the build prop file inside the Android /system folder.
These changes incorporate not only a increase in speed but also stability.
What I would like to see happen is one of 2 things, or both if possible.
1. Incorporate this build.prop file into the various "System_Froyo" builds available, forcing these changes on initial install, or
2. Vogue/Polaris developers browse the file for contradicting information (things that won't work on a Vogue/Polaris) and make appropriate changes.
Improvements include:
ro.ril.disable.power.collapse (prevents sleep of death),
various dalvik vm improvements,
force hardware acceleration and performance tuning,
various telephony enhancements including ring delay time and data speeds.
After making these changes, the phone rings immediately, the UI is much smoother (GUI uses video processor primarily), and data jumped from 1.3Mb/sec to over 3.2Mb/sec, making web pages load faster. (EDIT: The 3.2Mb/sec is the top of the scale, I actually averaged 2.2Mb/sec with average pings between 300-500 across 3 different radio roms).
VOGUE/POLARIS OWNERS!
Please test this file and report findings here.
IF you find you need to remove any lines, please do so before copying the file into /system. This file works well on the AT&T networks (Cingular), but may not have much effect on other networks.
If you have trouble after installing this file, please post your bootlog file.
PoX

So may I know what rom support this?

This has only been tested on a "clean" Froyo build, so I cannot make any assumptions as to if it will work in Gingerbread/Eclair/Donut/etc.
If everyone follows the install guide on the front page, I would assume that it would work worldwide, as long as it's Froyo.
In the future I could try it out on Gingerbread and other builds, but I make no promises as development has all but ended for Android on MSM72**.

I can test this. Perhaps, kaiser on Android could be good for daily use?...
Thanks for sharing

PoXFreak said:
Hi all!
For the past 2 weeks I have been making small changes to the build prop file inside the Android /system folder.
These changes incorporate not only a increase in speed but also stability.
What I would like to see happen is one of 2 things, or both if possible.
1. Incorporate this build.prop file into the various "System_Froyo" builds available, forcing these changes on initial install, or
2. Vogue/Polaris developers browse the file for contradicting information (things that won't work on a Vogue/Polaris) and make appropriate changes.
Improvements include:
ro.ril.disable.power.collapse (prevents sleep of death),
various dalvik vm improvements,
force hardware acceleration and performance tuning,
various telephony enhancements including ring delay time and data speeds.
After making these changes, the phone rings immediately, the UI is much smoother (GUI uses video processor primarily), and data jumped from 1.3Mb/sec to over 3.2Mb/sec, making web pages load faster.
If there is interest in this, please respond to this post. If there is enough interest I will attach it to this post as a .tar file.
Click to expand...
Click to collapse
PoXFreak said:
This has only been tested on a "clean" Froyo build, so I cannot make any assumptions as to if it will work in Gingerbread/Eclair/Donut/etc.
If everyone follows the install guide on the front page, I would assume that it would work worldwide, as long as it's Froyo.
In the future I could try it out on Gingerbread and other builds, but I make no promises as development has all but ended for Android on MSM72k.
Click to expand...
Click to collapse
I'm interested in your new build.prop tar, but I do not understand the thing about the install guide, you mentioned in you second post.
My Kaiser is running CM7 RC3 on haret, so maybe I can do some testing on gingerbread, with you.
Your trials, about tweaking the app download possibility, sound very interesting too, as I read about a tweaked build.prop for a tab that simulates to be a samsung tab in combination with an older version of the app market.
Feel free to PM, although I'm quite a newby to android.

I can build with Fresh Froyo and try it, but not until April sorry.
I am currently traveling and away from a development system.
I have been slowly trying to get a reliable app2sd capability working.
I'd suggest searching old posts for power collapse to see if dzo or others long ago tried this.
It sounds promising.

muckelmaus said:
I'm interested in your new build.prop tar, but I do not understand the thing about the install guide, you mentioned in you second post.
My Kaiser is running CM7 RC3 on haret, so maybe I can do some testing on gingerbread, with you.
Your trials, about tweaking the app download possibility, sound very interesting too, as I read about a tweaked build.prop for a tab that simulates to be a samsung tab in combination with an older version of the app market.
Feel free to PM, although I'm quite a newby to android.
Click to expand...
Click to collapse
The "install guide" I'm referring to is here...
How to replace Windows Mobile with Android (Guide)
There would be a change to the original build.prop file which exists inside the /system folder and would be installed when Android is installed on the Kaiser.
Mind you, I live in a busy city with LOTS of cell towers and, since 3g works on the principle of multi-tower usage, YMMV. If you live way out in the country with maybe 2-3 towers nearby, this may not help you.
Also, this has been tested on a NAND-installed OS, not a HaRet install. I cannot verify or guarantee this will work with a HaReT install as I have no way to test it and I think of HaReT as the "slow cousin" to a NAND install.
On a side note: My Kaiser has not had one sleep of death, hard-lock, white screen or even an FC for 9 days now. Apps running out of memory can be a slight problem but they will just close on their own as opposed to FC-ing. at worst I've had one hot reboot called by the system, and the FCs' are few, even with heavy Facebook and Maps use.
n2, if this works on all Kaisers, is there a way to push it to SF and either add it as a mod or rebuild the "system_froyo" install files and incorporate it within?

I will try in early April. Until then please solicit Vogue and Polaris users to try it.
Sent from my Nexus One using XDA

I am interested and willing to try this out!

Where is your " "Fixed" build.prop file for Kaiser "?

Tarball added to OP, please test and report back. Any problems should be reported here along with the bootlog from your phone.

Hi guys!
Problem occured when moving file to root folder. To solve I tried root explorer and z4root both. CM7 + Krazy-Killa's Kernel on tilt 8925.
Please talk what to do with it!
thanks!

Rename original build.prop file to "build.prop.old" or something you will remember, without the quotes, then paste the new build.prop file into the /system folder... it should go right in with no errors, unless you try it without read/write abilities.
CM7 may already have some of these fixes installed in the existing build.prop file. To check, open this build.prop with a text editor and check the entries under "additional build properties".

n2rjt said:
I will try in early April. Until then please solicit Vogue and Polaris users to try it.
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Vogue/Polaris users solicited, although I'm not sure if this can be used on a CDMA network. Last count shows about 15-20% of the "other" phones were Vogues, the rest were Polaris users.
It would be nice to start getting good feedback since this would be my first actual "hard" mod (one that is installed with the system, not modded through some other installer/program).

PoXFreak said:
Rename original build.prop file to "build.prop.old" or something you will remember, without the quotes, then paste the new build.prop file into the /system folder... it should go right in with no errors, unless you try it without read/write abilities.
CM7 may already have some of these fixes installed in the existing build.prop file. To check, open this build.prop with a text editor and check the entries under "additional build properties".
Click to expand...
Click to collapse
Can't rename. And can't change file attributions read only to read/write.

ZLodei said:
Can't rename. And can't change file attributions read only to read/write.
Click to expand...
Click to collapse
You probably need to remount /system read/write. I just wish I could remember how. Been a long time since I put my vogue down.

If you can get terminal emulator up on that phone, I believe all you would have to do is type in "su" then "mount /system".
All Kaiser/Polaris/Vogue Android builds are rooted and usually have superuser installed. I will take a look into Scoot's CM7 and confirm this. I know there is an update to superuser that leaves the old binary unable to be updated.

PoXFreak said:
If you can get terminal emulator up on that phone, I believe all you would have to do is type in "su" then "mount /system".
All Kaiser/Polaris/Vogue Android builds are rooted and usually have superuser installed. I will take a look into Scoot's CM7 and confirm this. I know there is an update to superuser that leaves the old binary unable to be updated.
Click to expand...
Click to collapse
Hi! Thank you!
What does exactly I have to do in terminal emulator?

I would hope you have superuser capability, if you don't then use another build that does have them...
Anyway, this is all I could figure out to remount the /system as RW. Type the following below into terminal emulator...
mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
(Where "mtdblock2" has /system, "mtdblock3" has /data, and "mtdblock4" has /cache.)
Hope this helps...

Please correct me if i'm wrong.
I installed this new build.prop from the bootloader using androidupdate.tar.
Because i made a tar archive this way: system/build.prop
Isn't it the easiest method? No mounting and hacking in terminal emulator.
Anyway, do anybody know which ROM contains hungarian language? I gave my Kaiser to my father and it would be great if he could use it in hungarian.
I thought VaniljEclair 11 has it, and it is almost true. It has hungarian language but when i set it nothing happens. Everything is in english as before.
Thanks!
Edit:
You can download it from here:
http://mattempus.sohasenem.hu/pub/androidupdate.tar