Database Info

Let's all try to fix the charging issue..

... since this problem is bugging us with aku3.x and crossbow roms.
Especially with the crossbow rom, this seems to be the only problem. The other issues are already fixed, or are easy to get fixed (since they have already been fixed in earlier roms).
In addition to this, I think that if we work together we have greater chances of solving this frustrating issue.
So this is what I have tried (with no success):
1) replace the battdrv.dll with one from a prophet
I get the common result where the device will charge only when you softreset with the cable inserted. You also get a square in the "Model No" in device information (Module address conflict?) Someone solved the square issue in an aku 3.x rom. I would like to know how it was fixed.
2) replace the battdrv.dll with one from an HTC artemis
No charging/status indication. Model No is reported as "WIZA200"
3) I unloaded camera and keyboard driver to see if there are any conflicts with them - no difference

andrew_sh said:
... since this problem is bugging us with aku3.x and crossbow roms.
Click to expand...
Click to collapse
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus

ikarus said:
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus
Click to expand...
Click to collapse
Thanks for the info.
I just tried it.
Result:
I get the square in the device info.
No charging/no battery status.
Strange isn't it? I wonder why the model no gets f**d up.

To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...

MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
I tried replacing this file. The result is that activesync stops working completely.

MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus

ikarus said:
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus
Click to expand...
Click to collapse
ahh, thats a handy tool, thanks for the tip !

attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus

ikarus said:
attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus
Click to expand...
Click to collapse
Thanks ikarus, i'll try tomorrow.
So have you tried this? Did you find out what was causing the problem?

andrew_sh said:
So have you tried this?
Click to expand...
Click to collapse
MusicMike tested it, but it needs more testing hehe
andrew_sh said:
Did you find out what was causing the problem?
Click to expand...
Click to collapse
not yet... in part yes, but i don't want to write explanations which could turn out to be wrong...

I'm back, testing it now

Jesterz said:
I'm back, testing it now
Click to expand...
Click to collapse
Welcome back! hehe damn it's been a long time

HELP
okay i have the japnease wm6 rc7 both files its all in jap appantly the battrey issue is fixed and all the other problems can someone help me to convert the language into english and then i can test on my prophet we may have a fully working wm6 rom here guys please need help for final stages.

WM6 100% working on prophet
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly i need a hero to covert the language into english please can someone help

c3l5o said:
so I was just wondering what does the app change in my phone to make it work... I didn't eve have to soft reset it once...
Click to expand...
Click to collapse
jutley said:
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly...
Click to expand...
Click to collapse
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus

anyone sucess pls post...
i'll try tomorrow

ikarus said:
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus
Click to expand...
Click to collapse
Ok thanks ikarus! Really is a smart and slight solution
guitarz said:
anyone sucess pls post...
i'll try tomorrow
Click to expand...
Click to collapse
It IS working indeed

This fix tested and working on Qtek S200! Its one of the 2,2 clean roms from a few months ago. The battery problem has been my biggest annoyance! Thanks!

I also tried XDADev_BatFix on my 818Pro with AKU3.3-Jester-b1 ROM.
Looks like it really solve the battery charge problem.
Thanks ikarus!

Worked
It Worked on I-mate JamIn, Thanks.
some times the device do not wake up after it sleeps

WIFI on Myn's Warm Donut RLS 5

Is this possible at the moment? I have it running smoothly right now (on POLA100) with no WIFI and don't want to try all the updates and risk putting myself back to step 1.
Also, downloaded an app from marketplace. download completed but it didn't install. Is this normal?
Thanks for everyone's hard work!
Dave

newquaydave said:
Is this possible at the moment? I have it running smoothly right now (on POLA100) with no WIFI and don't want to try all the updates and risk putting myself back to step 1.
Also, downloaded an app from marketplace. download completed but it didn't install. Is this normal?
Thanks for everyone's hard work!
Dave
Click to expand...
Click to collapse
for working wifi and bt look to this site post 175
http://forum.xda-developers.com/showthread.php?t=651856&page=18
thanks to SuperJMN

Still no luck
Thanks but still getting the message "unable to start WIFI" when I click on the checkbox in the Wi Fi settings.
If I can get this working then there's no going back to win mobile!!
Dave

Hi,
Try again by following the method actually given by SuperJMN : it works
Sure it works very well...
Cheers.
newquaydave said:
Thanks but still getting the message "unable to start WIFI" when I click on the checkbox in the Wi Fi settings.
If I can get this working then there's no going back to win mobile!!
Dave
Click to expand...
Click to collapse

newquaydave said:
Thanks but still getting the message "unable to start WIFI" when I click on the checkbox in the Wi Fi settings.
If I can get this working then there's no going back to win mobile!!
Dave
Click to expand...
Click to collapse
manu33xtro said:
Hi,
Try again by following the method actually given by SuperJMN : it works
Sure it works very well...
Cheers.
Click to expand...
Click to collapse
It's all I can do! If only I had the way to fix all the problems for both NAND and HaRET method, I would share it for you all, my friends.

rls 5
Managed to do the necessary partitioning of my hdsc card
7Gb FAT32 primary
256Mb Ext2 primary
256Mb ext2 primary
Installed it fine and wifi working but was running really slowly and processes kept hanging.
So I've gone back to my original RLS 5 without wifi and its working really quickly. Just going to hang on now for a new androidupdate file.
Thanks for all your help
Dave

I got WIFI working on Myn's Warm Donut RLS 5. I used this nbh: http://sourceforge.net/projects/and...polariseclair/POLAIMG-PANEL1-320.NBH/download
And this fix http://forum.xda-developers.com/showpost.php?p=6086521&postcount=100
Cheers!

to trouble2000 - wifi and the fix
trouble2000 said:
I got WIFI working on Myn's Warm Donut RLS 5. I used this nbh: http://sourceforge.net/projects/and...polariseclair/POLAIMG-PANEL1-320.NBH/download
And this fix http://forum.xda-developers.com/showpost.php?p=6086521&postcount=100
Cheers!
Click to expand...
Click to collapse
if you have got this fix working for you, that means your phone is pola100. this fix does not work on pola200. i have tried it 6 times and after rebooting it shows the MYNS ANDRDOID screen and then a black screen after that.
regards
o2-lover

I have android running using Haret in WM so I don't think I can use thie nbh provided by trouble2000, can I?
If I can, how do I do it? I'm still pretty new to this!
Dave

Yes, my phone is pola100.

I've now got it fixed.
Once I replaced zImage with Paipo compiled zImage and then did the update it worked fine, keeping all my settings and programs etc although I did need to choose my network again, BT Cellnet!!
DAve

newquaydave said:
I've now got it fixed.
Once I replaced zImage with Paipo compiled zImage and then did the update it worked fine, keeping all my settings and programs etc although I did need to choose my network again, BT Cellnet!!
DAve
Click to expand...
Click to collapse
Wifi it's working for NAND too! take a look at the Polaris Android Kernel thread

o2-lover said:
if you have got this fix working for you, that means your phone is pola100. this fix does not work on pola200. i have tried it 6 times and after rebooting it shows the MYNS ANDRDOID screen and then a black screen after that.
regards
o2-lover
Click to expand...
Click to collapse
When it show the black screen, reboot. If you have haret, start android again.

newquaydave said:
Managed to do the necessary partitioning of my hdsc card
7Gb FAT32 primary
256Mb Ext2 primary
256Mb ext2 primary
Installed it fine and wifi working but was running really slowly and processes kept hanging.
So I've gone back to my original RLS 5 without wifi and its working really quickly. Just going to hang on now for a new androidupdate file.
Thanks for all your help
Dave
Click to expand...
Click to collapse
i am having problem to partition sdcard 8gb. use paragon/gparted unsuccessfully. how do you do it??

to thebullet - in case of black screen after android
thebulletfromhell said:
When it show the black screen, reboot. If you have haret, start android again.
Click to expand...
Click to collapse
dear bullet
once the blackscreen comes, it means that your phone is not working any more.
so cannot go to haret.
the only thing can be done then is to re-install the whole system. i didnt mind because i had backed up everything and syncing contacts through google is not a problem any more.
regards
o2-lover

Screen does not respond while using Android

I have tried both Incubus26jc's Super Froyo (RLS8) and VaniljEclair RLS7c . I manage to install them in sd card (I want to use them via haret.exe) but when I reach the welcome screen where I have to touch the android to continue, the screen does not respond ( D-pad and center button work). Could someone help me? I decided to open a new thread because of what I have searched, I found only one member with a similar (but not the same) problem
The installation method I follow is this (mostly copied from a SuperJMN's post):
1º Run HaRET
2º From the installer, select Install System
3º Choose install update (if any)
4º Choose to fix permissions (if there had been an update)
5º Reset (don't select "Quit", just reset, this is to avoid problems)
6º Wait for Windows Mobile to start and run HaRET again.

Although I am flashing to nand and you are using haret/zimage, we may have the same problem with the unified touch screen driver that DZO implemented around 16 June. Is there is a way to use the kernel .nbh and system .tar with haret, rather than zimage? If so, you might try using an older kernel from before 16 June ... or perhaps an older zimage.

I have similar problem, if not the exactly the same. Using an older kernel seems to be a workaround of this problem. hxxp://forum.xda-developers.com/showpost.php?p=7041656&postcount=21 (You need to fix the hxxp as appropriate as I am not allowed to link URL yet)

i have the similar problem too, havent fixed it :/

I tried zImage-12-06-10 (the last one before the 16th of June) and installation procedure did not even start. But zImage-29-04-10 worked for me. However, Froyo is not that fast. If I change any files (zImage or something else) is it possible to have a speed improvement?

Same problems.
All Android realeases work on my pola100 only with zImage 29.04.10.
No work with other kernel.
I suggest to developers to analyse 29.04.10 and try to understand WHY this works and others no.
Regards.

regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
also check this for solution from k_k
HTH

mensa07 said:
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
Click to expand...
Click to collapse
Those are the changes after which my touchscreen stopped working.
mensa07 said:
also check this for solution from k_k
Click to expand...
Click to collapse
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!

tmcfarland said:
Those are the changes after which my touchscreen stopped working.
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
Click to expand...
Click to collapse
you can use terminal or adb to change the value

files for a fast android version
Could someone with a fast and stable version of eclair or froyo please tell us what files did he/she used to make that happen because I installed incubus froyo build and it is a bit slow? I am talking about installing it in my sd card and run it using haret.exe

Simple how-to run android from windows

TO ALL PEOPLE:
PLEASE STOP POSTING IN THIS TOPIC ABOUT "THIS PART DOESN'T WORK ECC ECC" WRITE IN THE TOPIC OF THE RELEASE (KERNEL OR SYSTEM), PLEASE LOOK IN THIS THREAD FOR WORKING SETUPS AND TRICKS, AND SEARCH ON THE FORUM BEFORE POSTING!
I start with thread with a information for all users:
Haret system sucks so if you want a full working android system left windows behind you and move to the new android world flash on nand.
With this how-to you will not erase any part of your system but you do at your own risk.
Main problem: screen
For polaris there are 3 type of screen. Usually pola100 (the old one) use panel 1, and pola 200 (09 edition) has panel 3 but ... not always works...
The best mode to test is try to install and after double reboot you have black screen change panel type.
What you need:
phone
sd card (1 Gb or more) 500 mb free
time
Update guide: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret

reserved by me

Do we have to delete/remove the install-seq.sh after installation?
Are both files (system & data) cleared with the installation script?
Thanks for the help.

install-seq.sh disable automatically after correct install.
This how-to is fir first install on disk on images so it format both data an system.
If you want to make only un update use bsg select partion and select update.

partition
I believe you should make this sticky

Don't post without reading!!!!
This method doesn't use sd partition, it create two imagedisk on sd!

working android
l1q1d said:
Don't post without reading!!!!
This method doesn't use sd partition, it create two imagedisk on sd!
Click to expand...
Click to collapse
hi there,
i made all you told here, booting..after more minutes...the logo appears...but when i press the android logo from the screen.. the touch screen dosent work..i can not start..only with buttons..and after pressing buttons..get over wizard..the phone need SIM PIN..but i can not typed.
please help
i changed BORAD PANEL in 1,2,3 and in 2,3 is black screen.
please help me

You have to disable pin code before installing.
For the screen problem look in kernel thread...

waiting for not busy
What about "waiting for not busy" - im2c error ?
The only Zimage working for my pola100 it's an old 29-04-10 Version !
I am very disperate!
Bye !

touch screen dosent work
foxct2005 said:
What about "waiting for not busy" - im2c error ?
The only Zimage working for my pola100 it's an old 29-04-10 Version !
I am very disperate!
Bye !
Click to expand...
Click to collapse
Dear All,
i tried and deactivate the PIN of sim card..read all posts from previous thread that you gave me..but nothing..
all ok..
bootin..starting..apears the logo and final...
before i need to press the screen, appears a message ''Android system stop responding..and a button FINISH"...after pressing finish, i need to press the middle of the screen on the android logo and nothing, only 2 buttons Emergency Call and Choose Language. to can press these 2 buttons, i use the buttons and i can press them..but touch screen do not working.
please all of you..the masters of this softwares..give me a solution.
thx

Try to reinstall the system...
(rename /andboot/install-seq-disabled.sh to /andboot/install-seq.sh and boot)

touch screen problem
l1q1d said:
Try to reinstall the system...
(rename /andboot/install-seq-disabled.sh to /andboot/install-seq.sh and boot)
Click to expand...
Click to collapse
hi there..
i solved the problem..i took an older Z image..and working fine
the problem is that more applications like camera..media player screen adjust don't work..
they try to run..(i mean ..in camera..i can see..but appears a messages with stop working..sorry). i don't know why..
nothing work well
and what about the contacts..how can i get them from my Sim card?
i don't know..
if you can help me will be great.
thx allot for yours assistance.
best regards.

The information from sim card are very limitated (neither pin code works) so if you want to export contact sync before starting with google and configur your google account on android.
old zimage are full of bugs and all developers install android on nand so starting android from haret has many unfixed bugs.

I've been playing around with the haret install for a week or so now, and I've found that, for me at least, it makes a huge difference which initrd.gz file I use.
The one dated 22-05-10 doesn't let me install any zImages newer than 29-04-10. After trying all sorts of combinations of base files with different dates (haret, zImage) and additions to the default.txt, changing the initrd.gz file to the one dated 20-02-10 fixed most of my problems and lets me install the most recent zImage files without a glitch.
No clue why, just that it works.
I'm running a Pola100 with the original WM6.0 ROM still on it, and radio version 1.58.25.14. Yeah, I need to upgrade to at least the official WM6.1 ROM and probably something better. But I'm a newbie at this, so I need to work up some courage first ;-)

hello,
I tried to install android on sd following your instructions, everything seems to go well until the screen where it says:
"Welcome to htc vogue Frøya
touch the android to begin "
I'll try, but the touch does not work, I tried using the d-pad, which does work, but I can only select the language and the emergency call.
zImage as I used: zImage-Frøya-15-07-10
androidinstall.tar as I used: Incubus26Jc's Super Frøya RLS11 Themed
please help me because I would switch to Android!
thanks

Try with latest kernel version on kernel (i release it yesterday)

l1q1d said:
Try with latest kernel versin on kernel (i release it yesterday)
Click to expand...
Click to collapse
where can I find it?
thanks

I tried it unsuccessfully. Boot starts regulary, always ending on repeating error, looping forever.
I can read something like:
==============
ERROR no local apt for prog ... replying anyway
...
Setting function 4 for gpio ... that I don't own
==============
Is it related to which system file ? Loader? Kernel ? Or what ?
Thanks

What did you use for your installation?

I used the files mentioned at the very beginning of this post.
Regarding zimage: zimage-24-05-10

A fix for POLA100, Haret and waiting for notbusy error

I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
It also seems that this error is caused by the double vibration at the beginning of boot process and was solved once by paipo (see this post) by commenting out the vibration part and rebuilding. But those kernel is outdated and misses some latest features and fixes.
So I did the same as paipo but with the latest kernel from the git repository (as of 19.07.2010, revision d5d0a56fae6df779443a82e2d90b7ec8097cb332). zImage is attached to this post. I'll try to update the kernel from time to time.
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post

Disabling the vibration and rebuilding the kernel yourself
So how do you do this?
First of all, follow the steps 1 to 4 of Building kernel For Vogue, Kaiser, and Polaris part from this guide to prepare your building environment.
Now you need to open the arch/arm/mach-msm/board-htcpolaris.c file in your favourite text editor.
Search for vibrate word (it was line 1019). You'll see something like this:
Code:
// vibrate
for (i=0; i<2; i++) {
while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
mdelay(75);
}
Remove this part or replace with the following:
Code:
// vibrate
// for (i=0; i<2; i++) {
// while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
// mdelay(150);
// while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
// mdelay(75);
// }
As you can see, all lines now start with two slashes.
Now follow step 5 from the guide, mentioned above. You'll see a menu.
Go to System Type and select Android Optimization accroding to your needs. Then select Exit, than again Exit, then Yes.
Now follow step 6 from the guide. This will take some time. At the end you should see:
Code:
Kernel: arch/arm/boot/zImage is ready
Copy zImage from arch/arm/boot folder to \Storage Card\andboot folder on your device and use it

I update this option in the kernel.
Now double vibration is disable by default.

You are great !!!
leppa said:
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
...
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Click to expand...
Click to collapse
YOU ARE GREAT !!!
THANKS A LOT A LOT A LOT !!!
THIS EVENING I WILL TRY SURELY !!!!!!!
Only a question: Optimized for Eclair is equal to Optimize to FROYO ?
Can I use your zImage to Froyo RLS 11 ?
Thanks in advance.
Bye

This flag now do nothing, so it's indifferent

GGGGGGGGGGGGGGRRRRRRRRRRRRRRRRRREEEEEEEEEEEEEEEEEAAAAAAAAATTTTTTT !!!!!!
I Have Just tested zImage in attached files.
Froyo seems better reactive, more smooth and rock stable.
Thanks a lot ...
When Video Playback will be solved... I will flash immediately Froyo to give a new life to my Cruise!!!
Thanks thanks thanks!

@foxct2005 : you can flash it month ago!
All these problems are only for haret!

l1q1d said:
I update this option in the kernel.
Now double vibration is disable by default.
Click to expand...
Click to collapse
This change isn't yet in the git repository, is it?
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
The attached kernel images work as they did before - with double vibration on boot and "waiting for notbusy" error. To disable the double vibration (and get rid of the error) add board-htcpolaris.no_boot_vibration=1 to default.txt so this line:
Code:
set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
will look like this:
Code:
set cmdline "board-htcpolaris.panel_type=1 [COLOR="Red"]board-htcpolaris.no_boot_vibration=1[/COLOR] ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
Adding this parameter is mandatory if you suffer from "waiting for notbusy" error.

big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!

leppa said:
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
Click to expand...
Click to collapse
Good idea!
I have long think why developers not added it to the cmdline.

Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..

DmK75 said:
Good idea!
I have long think why developers not added it to the cmdline.
Click to expand...
Click to collapse
I think, they have much more other, more serious, things to do
michasch said:
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
Click to expand...
Click to collapse
nikiiv said:
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
Click to expand...
Click to collapse
You're welcome
If this patch gets upstream, we will not need to rebuild the kernel every time a new build comes out. I already posted it in the Polaris Android Linux Kernel Development Project thread.

thanks leppa,
i tried the froyo one, but for me doesn't work. last days i used the last dzo one, it worked for 2 or 3 days, and now doesn't work again. the only zimage that works is the 29-04 one, but my battery doesn't like it so much

loscassapalle said:
thanks leppa,
i tried the froyo one, but for me doesn't work.
Click to expand...
Click to collapse
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.

leppa said:
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
Click to expand...
Click to collapse
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.

loscassapalle said:
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
Click to expand...
Click to collapse
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).

leppa said:
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
Click to expand...
Click to collapse
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
the animation problem is strange. the zimage of 29-4 works, the animation ends in a few seconds, but the battery life is very short. the last dzo zimage worked for a couple of days, then i had the same problem after a softreset...and this one is the same...
EDIT: now it works... lol

loscassapalle said:
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
Click to expand...
Click to collapse
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
loscassapalle said:
EDIT: now it works... lol
Click to expand...
Click to collapse
So, it started working?

leppa said:
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
So, it started working?
Click to expand...
Click to collapse
i don't know how to edit the zimage...but now it works...i didn't change anything...

loscassapalle said:
i don't know how to edit the zimage...
Click to expand...
Click to collapse
You don't need to. I was talking about editing default.txt as I described in post 8.