Related
This is the Development and Downloads Thread for the ION Build of Android for our Kaisers.
Any Non Development Questions will be Ignored in this Thread
Only Development related content will be posted here.
All non development related questions need to be directed to this thread: Questions and Troubleshooting
First Thanks to Vilord for the work, and thanks to whoever he thanked (Martin, Okibi, etc etc)
Working:
Data Connection
Google Services
Call Waiting
GPU Graphics Acceleration
Work In Progress: (not by me)
Camera
GPS
WIFI
Instructions: (adapted from Vilord's vogue post)
For some people ROM and Radio make a difference in whether or not certain aspects of the phone work. I am using Shifu's 6.1 V08 WWE Naked ROM with Radio 1.65.24.36
Before I boot haret, while still in WinMo, I always complete 1 call, so I call my voice mail, then once it connects I hang up. I'm not sure if completing a call like this actually helps, but I do it anyway. If you are not able to make calls, try this step.
Step 1: Download the files:
-Download ExtractToRootOfSDCard.zip below and extract *everything* to the root of your SD card
-Download system-ion.img from below, rename it to system.img and put it in the root of your SD card
-Download zImage from below and put it in the root of your SD card
-Download the newest initrd.gz file, extract it to your SDCard and overwrite the initrd.gz file that was in the ExtractToRootOfSDCard.zip
Step 2: Run it!
-Run Haret, and it should boot into android.
Reports have shown that starting over with the fresh data file (data.gz) instead of using your existing data.img produces better results.
Be aware of the fact that it will take a long time to extract the data.img file from the data.gz archive during your first boot. It took about 5 minutes for me.
At first your orientation may not return to portrait mode after closing the keyboard, if this happens fix it by:
Going to Settings > Sound & Display > Under Display Settings UNCHECK "Orientation"
Download the system-ion.img file (then rename it to system.img put it in the root of your SD card)
Download the kernel aka zImage (then put it in the root of your SD card)
Download the latest initrd.gz file from Vilord's google code page
reserved for updates
reserved for updates
Thanks for the thread, I'll update this post later with my ION system.img that has the original key layout along with bash and busybox tools added. Other than that, it's the current one you posted.
For anyone new to developing Android, here's what to do (thanks to everyone for these scripts):
system.img
Code:
mkdir stock-system && mkdir temp
sudo mount -o loop system.img stock-system
genext2fs -d stock-system -b 300000 -a system.ext2
sudo mount -o loop system.ext2 temp/
[B]---Make Changes---[/B]
sudo mkfs.cramfs temp/ system.1.5.img
I've attached genext2fs as well (thanks dzo)
initrd.gz
Extract--
Code:
gunzip initrd.gz && cpio -i < initrd.cpio
Compress-- (within directory)
Code:
find ./ | cpio -H newc -o | gzip > ../myinitrd.gz
data.gz
Is simply a gzipped ext2 img file.
We've been putting busybox and bash into the initrd... since it doesn't take up much space it allows more customization of the initrd environment...
Could you let me know what of my vogue stuff doesn't work on kaiser and what you need to change to make it work? It may be easy to adapt the vogue stuff to be compatible with both.
Installed ok. With a couple notes:
During first boot, got stuck at the terminal screen with nothing happening after the Data.img was extracted.
Rebooted, booted fine.
Noticed that 320x480 looks retarded as a screen resolution for Kaiser
Reset resolution to 336x448 and rebooted.
Crashed in terminal with Oops #11 (seriously, thats what it said)
Reset resolution to 320x428 looks fine. I'll probably try a few higher resolutions to get more screen real-estate.
Also, I was initially not able to install items from the Market. They download fine, but when the 'install' starts, it throws an error. This may have to do with attempting to download two things at one time. I later retried the download and both items installed fine.
In initrd.gz/init file:
When it boots, it complains of "no telephony database. Will check for Android apn on next boot:"
Code:
SQLITE3="/bin/sqlite3"
[B]DB="/data/data/com.android.providers.telephony/databases/telephony.db"[/B]
if [ -e $DB ] ; then
if [ "`$SQLITE3 $DB 'SELECT numeric FROM carriers;' | grep 310995`" != "310995" ] ; then
echo Creating android apn
"$SQLITE3" "$DB" "INSERT INTO carriers VALUES(NULL, 'Android' , '310995' , '310' , '995' , 'internet' , '*' , '*' , '*' , NULL, NULL, NULL, NULL, 'null' , 'default' , 1);"
fi
else
[B] echo No telephony database. Will check for android apn on next reboot[/B]
fi
After that it says "chmod: 1000 no such file or directory."
Code:
if [ -d /data/app ] ; then
if [ -d /sdcard/AndroidApps ] ; then
echo Copying Applications
cp /sdcard/AndroidApps/* /data/app
[B] chown 1000 1000 /data/app/*[/B]
fi
fi
Example of Questions being asked in wrong thread
enatefox said:
...all the other stuff you said, then...
How can I debug bootup?
Click to expand...
Click to collapse
Please refer questions like this to the "Questions and Troubleshooting Thread"
enatefox said:
In initrd.gz/init file:
When it boots, it complains of "no telephony database. Will check for Android apn on next boot:"
Code:
SQLITE3="/bin/sqlite3"
[B]DB="/data/data/com.android.providers.telephony/databases/telephony.db"[/B]
if [ -e $DB ] ; then
if [ "`$SQLITE3 $DB 'SELECT numeric FROM carriers;' | grep 310995`" != "310995" ] ; then
echo Creating android apn
"$SQLITE3" "$DB" "INSERT INTO carriers VALUES(NULL, 'Android' , '310995' , '310' , '995' , 'internet' , '*' , '*' , '*' , NULL, NULL, NULL, NULL, 'null' , 'default' , 1);"
fi
else
[B] echo No telephony database. Will check for android apn on next reboot[/B]
fi
After that it says "chmod: 1000 no such file or directory."
Code:
if [ -d /data/app ] ; then
if [ -d /sdcard/AndroidApps ] ; then
echo Copying Applications
cp /sdcard/AndroidApps/* /data/app
[B] chown 1000 1000 /data/app/*[/B]
fi
fi
Click to expand...
Click to collapse
The chown line has been fixed and will be uploaded soon.
The no telephony database line should go away after first bootup. Does it not?
MBurris: the setupmodem.sh script you have must be an older version as I had already removed the lines you mentioned. Anything else?
now I understand, you want the stuff added back *in*
It is done, added to ppp-on-dialer where it belongs.
Also completely fixed the data.gz stuff by eliminating data.gz. Now the initrd will create a new data.img if there isn't one there.
support for data.img backups from bootup as well, just create a /sdcard/backup folder
@Vilord: Have you added the new stuff into your latest initrd.gz (on google download)?
Edit: After I used the latest files from google download all the files on my SD card are totally gone :s. I booted Android Original ION hero build, and back in Windows all files are gone on my SD card :s
Hi there, dunno if this belongs to the ION question and answer thread, but could anyone be able to make one of the roms with this:
http://android-unleashed.com/2009/06/htc-hero-theme-1-2-for-the-android-g1.html
Cause i think this theme would be very cool on this ion builds..
Still having issues with the phone not waking up.
Using pm.sleepmode=1, otherwise, as you know, the battery life lasts about 2 hours.
KAIS110
radem205 said:
@Vilord: Have you added the new stuff into your latest initrd.gz (on google download)?
Edit: After I used the latest files from google download all the files on my SD card are totally gone :s. I booted Android Original ION hero build, and back in Windows all files are gone on my SD card :s
Click to expand...
Click to collapse
I think this is due to corruption on the SD card, coupled with the creation of a large file (data.img). I'll post an updated initrd in an hour that has filesystem checking on the SD card before it tries to do anything else, that should avoid wiping out people's stuff.
EDIT: sorry, hit go advanced and post by accident and double posted
JeckyllHavok said:
Hi there, dunno if this belongs to the ION question and answer thread, but could anyone be able to make one of the roms with this:
http://android-unleashed.com/2009/06/htc-hero-theme-1-2-for-the-android-g1.html
Cause i think this theme would be very cool on this ion builds..
Click to expand...
Click to collapse
I'm with you. 3 threads and no real response at getting themes. I tried it myself by manually overwriting the apps, data files and framework as the update would but it hangs at boot or crashes mercilessly once the desktop appears beyond nonfunctional.
mburris, that's what prompted me to post the question about how to debug bootup. This is every bit a development issue. Those are signed apps that override the ION ones and they should "just work" so what's wrong and who's at fault . Plus it's hard for us to really troubleshoot users' issues with modems and startup without something better than dmesg. Then users can attach a log to their posts for us to look at.
Posted to the vogue people:
Okay the initrd.gz on google code has been updated yet again.
This time is a major update with repaired bell SMS (thank you Martin), new libgps (thank you Steven), and statically linked filesystem checks (that was me).
On my phone, it took about a minute to create a new data.img (*don't use data.gz!!!*)
You'll want to use martin's new zImage from here
MBurris, does it just work now, or is there still some tweaking for kaiser?
---
For themeing, it is *very* difficult to theme an ion build. Much easier to theme the opensource builds, but they aren't as fast.
For themeing, it is *very* difficult to theme an ion build. Much easier to theme the opensource builds, but they aren't as fast.
Click to expand...
Click to collapse
How difficult are we talking? Mssmision had two ION builds with Hero. What's involved?
Latest initrd and zImage:
336x448 resolution works again! SOOO much nicer than the non-4:3 included with the install package you posted...
Noticed the Blue LED blinks now... Something good coming?
Data, Market, Txt, calls, call-waiting, all work.
GoogleTalk works again,
runs SOOOO fast....
This thread puts all the necessary steps together for sucessfully run the Android-release from THIS thread on the X1. Since many seem to have problems with that this may become handy
So lets get started!
What you need:
- latest XPEROID-release, fatsal-xperoid-20100221.7z, get it here
- 7zip to extract it, get it here
- sd-card, using fat32-filesystem with 500MB free space
What you need to do with it:
1. Extract fatsal-xperoid-20100221.7z on your computer. This will give you the following files:
- calibration, wlan-firmware
- haret.exe, runs the linux-kernel and android
- initrd.gz, initial ramdisk, needed for linux to boot (phase one)
- modules-2.6.27-00888-g339bdfc-dirty.tar.gz, linux- and android-driver for wlan
- rootfs.img, contains files needed for linux to continue boot (phase two)
- STARTUP.TXT, contains the parameter for haret.exe and boot-options for linux-kernel
- system.sqsh, contains all android system files
- zImage, contains the linux-kernel
- conf/*.user.conf, configuration files for android
- AndroidApps/*.apk, applications for android, installed during boot
2. Delete all the *.apk-files from the AndroidApps-directory. They are not needed for running android. You should keep the directory, just delete all files in it.
3. Download some essential android apps here, you will get essential_apps.zip. Extract it and put the apk-files into the AndroidApps/ folder.
4. go to conf/ and delete eclair.user.conf, then rename eclair.user.conf~ to eclair.user.conf. That will disable the swapfile.
5. open startup.txt and remove the mem-option mem=102M. This was suggested by hotlein here. That will increase the memory from 102m to 182M and improve android speed alot.
6. Copy all files and directories to the root of your sd-card. Do not create any directory, just copy them to the blank sd-card.
7. Put the sd-card in your phone if not already done. On the X1 open the sd-card and run haret.exe. You will get alot text running across the screen. During the boot-process, one file is created.
- data.img (256M). This file contains all the files normaly stored on the android-phone. Your settings, Applications, media, etc. You can always delete this file to reset android. It will be recreated.
First boot takes a while to complete, so be patient. Finally you should get the android welcome screen. Follow the on-screen-instructions and you are done!
Changing some settings
- IMPORTANT: Disable GPS in settings -> location & security -> Use GPS satellites, because it will hang the device!
- Turn off locks screen when holding red call button. Spare parts -> End button behaviour -> Nothing. That will simplify the shutdown procedure. Credits go to Reversedhex: Post
Now let's stop android
1. Press and hold the end-call-key. The phone starts to vibrate like crazy, ignore that.
2. After a few seconds a menu pops up. Dont release the button yet, keep holding it! If you changed end button behaviour, you can release it now.
3. Press down on the digi-pad. You may press it three times to go to the shutdown-option.
4. Now you can release the end-call-key. If you do not hold it, you will end up in the android lock screen.
5. Select shutdown option and confirm. Then android shuts down.
If you try another kernel-image (that is replacing zImage), the system may lock up during shutdown. Then you have to soft-reset your phone. But you should always try to shut android down.
Now you can update the linux-kernel:
1. Download the kernel-image, get the latest here. That gives you zImage_kovsky_20100325.zip.
2. Extract zImage_kovsky_20100325.zip to get zImage. This is the linux kernel.
3. Copy zImage to the root of your sd-card. You should always back up your existing zImage so you can go back.
4. Download wlan-modules, as they must match the kernel-image, get them from here. That gives you wlan-modules_20100325.zip.
5. Extract wlan-modules_20100325.zip to get modules-2.6.27-01006-ga30aafa-dirty.tar.gz. This archive contains the wlan modules. Do not extract this. Simply put this on the root of your sd-card. On android startup this file will be extracted on the modules copied for you.
As suggestet by angusmcb (post), i used for the latest kernel the latest cross-compiler.
Latest kernel from xdadev-repos with backlight control and correct battery readout, get it here. The archive also contains matching wlan-modules.
Troubleshooting
Q. Android will not boot
A1. check if all needed files are present
A2. check if you have enough free space on card. Android creates two big files during first boot, so you will need at least 384M free space.
A3. you can try to delete data.img and swapfile to reset android. This helps if you messed up settings in android.
Q. Wlan wont start
A1. check if file calibration on sd-card-root
A2. check if file modules-*.tar.gz matches kernel-image
A3. you may try to enable wlan in windows mobile before running haret.exe
Q. How to stop android from using data connection
A. go to settings -> wireless & networks -> mobile networks -> access point names and delete all apn-settings
Q. Android-screen is upside-down
A. Slide out keyboard -> android switches to landscape. Then slide keyboard in -> android switches to correct portrait.
Q. I have no ringtones
A1. Put the ringtones in the MEDIA\AUDIO\ringtones folder (post, post for folder structure)
A2. Take a look at this post. Some characters make the android media scanner crash.
Q. I can not enter pipe-symbol. Where to find keymaping
A1. Press function key, followed by shift key, followed by commer key (right hand side of space bar) (linuxtux post)
A2. For keymapping in general take a look here. That is the default android keymapping.
Q. I want live wallpapers
A. Here you go. But be prepared for performance loss.
Q. I can not send SMS
A. Check this post by jimipoh. It might help.
Done for today
reserved for future updates
also reserved for future updates
and this, too
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
What the F?
♥♥♥
Good luck~♥
Muo said:
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
Click to expand...
Click to collapse
This thread is mainly about how to get android working. I am trying to speed android up by partitioning the sdcard as fatsal mentioned. If it works there will be a HOWTO for that, too.
Until then i will continue to work the linux-kernel for X1-android until it is done (or i loose my X1, too )
This is pretty consize. I hope it sums up all the main points of fatsal thread on android
With zImage_kovsky_20100313.zip system always lock up during shutdown
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
No no no! Your doing it wrong!! D:<
gbajzelj said:
i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
Unfortunately, due to certain hardware limitations of the X2, boot time of the X1 kernel on the X2 can take a little longer. About 1.2 seconds after the sun explodes and extinguishes all life on Earth 4 billion years in the future, is a good estimate.
Sorry
vdelf, will you be committing regularly to gitorious? Or do you have a scratch repo for messing around with?
vdelf said:
also reserved for future updates
Click to expand...
Click to collapse
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
i had the bin/sh error too , first time.
when simply retrying -> it booted up to the "exploding X".
however, that screen froze on me.
i seem to get more progress though than with the material from the original threads.
the material from this topic has gotten me further than ever before. as i speak i'm booting a fresh one with the new kernel (from the start). it's upside down, but i hope this one works 'out of the box'.
persistence is paramount, as time passes the chance on reaching satisfaction approaches 1. how this satisfaction is achieved is up to you; may it be through running XPEROID, purchasing an android phone or simply giving up.
I managed to get it back to the "exploding X" screen (using the first file, not the kernel update).
It seems to be stuck in the X screen though, it's looping (and stalling a little) for 20 minutes now. Last time I soft-resetted the phone after about 10 minutes of X-screen, and it mangled my sd card (meaning I had start from scratch). There is no text (or error message for that matter), so I don't know what is going on.
Is anyone familiar with this?
EDIT:
I paused my attempts for now. Same result over and over. I'm not able to find anything on this in the original thread (or possibly when I read every single post I might find something), search reveals nothing to me.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
You have to use a version of haret that supports your phone. As X1 and X2 have not identical hardware (or do they?) someone has to code X2-support to haret. Until then it will not work.
In startup.txt there is this line
Code:
set mtype 2006
This is for kovsky X1. For X2 there has to be a different value, but dont ask me about that
dawen said:
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
Click to expand...
Click to collapse
It seems that your sd-card has no partition. If you use linux, you can check this very easy. On windows, you can try to reformat the card.
You can also try another card.
Woudnt it be possbile/smarter to put the android on your xperia's internal memory (when you have 300+mb free?) or woudnt there be any diffrence in speed?
can you install apps from the market
or do you have to manually do it (pasting the apk to the sd)
?
Well like the title states, I would like to see the kernel messages instead of a boot animation. Just for the geeky look of course ^__^
So is there a way of doing that?
I'm using a German Vodafone Magic 32B, running Cyanogenmod 5.0.8.
I think you can't put the boot in verbose mode, you could do an animated sequence with PNG files to emulate the verbose mode but it won't be the real boot messages of course, just images
Yeah I'm using a boot animation that imitates the BIOS POST-screen on a PC, it's nice but the verbose mode is much cooler
The boot animation I'm using:
http://forum.xda-developers.com/showthread.php?t=648555
What I'm after:
http://www.youtube.com/watch?v=HQKfeDnMVQ8 (about 2 minutes into the video)
If there was a simple setting in a configuration file, it would be awesome, if it required modifing the boot loader, it would suck
From what I understand, you need to change the init.rc file in \
setprop ro.kernel.android.bootanim 0
setprop debug.sf.nobootanimation 1
or simply change export ANDROID_BOOTLOGO 1 to export ANDROID_BOOTLOGO 0 also in init.rc
However, all changes to init.rc are gone after restarting the phone....
Any ideas?
Hm, it seems like the init.rc we see in our rootfs is part of a ramdisk. A ramdisk created from an image in our boot image, i guess a modification of the boot image would help the cause, but that's way too much trouble
quazar666 said:
From what I understand, you need to change the init.rc file in \
setprop ro.kernel.android.bootanim 0
setprop debug.sf.nobootanimation 1
or simply change export ANDROID_BOOTLOGO 1 to export ANDROID_BOOTLOGO 0 also in init.rc
However, all changes to init.rc are gone after restarting the phone....
Any ideas?
Click to expand...
Click to collapse
I modified the boot.img with the first changes but it just broke it. Apparently the setprop method won't work. I'll try the export suggestion sometime in the next couple days and report back.
Awesome, thanks for trying
No problem. If I get it working I'll post a tutorial on how to rebuild the boot.img to do this. I'll also post a premade boot.img for the latest CM release candidate.
Any news ?
nattiii said:
Well like the title states, I would like to see the kernel messages instead of a boot animation. Just for the geeky look of course ^__^
So is there a way of doing that?
I'm using a German Vodafone Magic 32B, running Cyanogenmod 5.0.8.
Click to expand...
Click to collapse
What you want is this http://www.youtube.com/watch?v=7u6qNzsgbxY
As you indicated yourself.......they are messages from the kernel. You would need a kernel that's verbose instead of having a logo.rle. Kernels have specific headers & hashes so its really hard to just 'add' or 'remove' stuff inside. You would need to compile a special kernel to achieve this. I'm pretty sure the permissions & logo.rle are in the initrd which is 1/2 of the Boot.img alongside the zImage. Hope that helps
Any updates on this? This would be killer!
92drls said:
Any updates on this? This would be killer!
Click to expand...
Click to collapse
Try chainfire's "live dmesg" and " live logcat" boot animations, should be available on the market
Sent from my HTC Desire using XDA App
I just tried the live dmesg. That's absolutly brilliant! Thanks for the tip!
Sent from my XT894 using xda app-developers app
Hi,
I'm new to this site and XDandroid Rom so I will try to provide as much information as possible to assist you in helping me. I have recently installed the "XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACK AGE" on my Raph800 Touch Pro.
The problem that I have noticed is that well, mostly this problem has been occuring while on battery power, but after the phone goes unattended for about 40 seconds it goes into a sleep/hibernate state that I cannot get out of without doing a battery pull.
My code in the "startup.txt" file is:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2039
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 rel_path=andboot pm.sleep_mode=1 force_cdma=1"
boot
Also there is still currently no way to have WEP wifi network work on this build correct?
Any help will be appreciated.
Thank you
DA01 said:
Hi,
I'm new to this site and XDandroid Rom so I will try to provide as much information as possible to assist you in helping me. I have recently installed the "XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACK AGE" on my Raph800 Touch Pro.
The problem that I have noticed is that well, mostly this problem has been occuring while on battery power, but after the phone goes unattended for about 40 seconds it goes into a sleep/hibernate state that I cannot get out of without doing a battery pull.
My code in the "startup.txt" file is:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2039
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 rel_path=andboot pm.sleep_mode=1 force_cdma=1"
boot
this seem to be a problem we are yet to get a solution to,i run xdandroid 2.2 froyo on the htc fuze.when the phone sleeps for more than 5min it won't wake except by soft reset or removing the battery and restart the phone into winmo.. any solution to this as yet ?
Click to expand...
Click to collapse
Hi,
I installed the above build on my Sony Ericsson X1,
Im getting really poor performance, after quite a while of trying I managed to install Android System Monitor, I notice my processor is running at 57.6Khz 100.2% of the time!
I read that this build is pretty quick...
within the frequency stats it shows:
-122.88Mhz 0.0% (0)
-245.76Mhz 0.0% (0)
-320.0Mhz 0.0% (0)
-480.0Mhz 0.0% (0)
-57.6Mhz 0.0% (100.02%)
I think this could be my problem....
in my startup.txt file I have the following:
set ramsize 0x8000000
set ramaddr 0x10000000
set mtype 2006
set INITRD_OFFSET 0x608000
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=npkboot fbcon=rotate:2 ro.sf.hwrotation=180 lcd.density=240 msmvkeyb_toggle=off msmts_calib=0x0366.0x04b.0x0c8.0x038e clock-wince.grp=0xa92 acpuclock.oc_freq_khz=650000 pmem.extra=1 no_console_suspend physkeyboard=kovsq msmsdcc_1bit msmsdcc_fmax=14000000 hw3d.force=1 acpuclock.force_turbo=1"
boot
Someone please help!
this is the exact thread i followed:
http://forum.xda-developers.com/showthread.php?t=1156421
Making sure I have created the partitions correctly.
the only thing I did change was the order in which the partitions, otherwise I couldnt access the fat32 partition to copy the files.
I did try the Turbo kernel which didnt make any difference.
I have tested the card and its fine, i have used this for other builds on a Touch pro 2 and it worked fine.
This was ran the same before I installed the gapps.zip using clockwork mod.
I managed to get it to boot up really quick once, it really was flying! then it rebooted..
since then it doesnt even boot, im trying to step the CPU down as much as possible. on the thread it recommends 614000khz but I have gone down less that 600 and its still crashing and re-booting.
I might leave it a while incase its a heat issue, and let the cpu cool...
Any help would be greatly appriciated!
thanks in advance.
acpuclock.oc_freq_khz=650000
you can make it small.576000-624000 is enough,and I didn't install gapps.
but my keyboard sometimes can't work, what about yours
Honeycomb Froyo V3
Had the same problem, massive heat problems and poor battery life with this build, now using NAND CM7 Gingerbread, much better, much more stable