yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] trilu:
Hi all,

i think i have fixed the ugly bluetooth battery drain bug.

It works for me since yesterday evening. Battery drain is between 2ma and 5ma with GSM and BT enabled. Also the headset in my car works very well.

Base for my work was tytungs kernel git - i think it was v8, but not sure...

In this post you will find a patch file, the compiled kernel and the source files i have modified. I'm a absolutly beginner with compiling linux, so i am not sure that the patch file will work, diff has a realy big manual :p

http://gitorious.org/~tytung/linux-on-wince-htc/tytungs-hastarins-linux_on_wince_htc

Also i am not sure how this kernel will work with Sense roms, because Sense use btld which has the power saving features in the binary and not in the kernel.

Last but not least i will thank Charansingh for the work he has done on the BT problem and tytung for his kernel base.

If you like to test the kernel, please take also my modules, because i get with the precompiled files from tytung a version magic error.

Your feedback is highly appreciated.

Best regards

trilu

In this Post you will find the zip file for updating magldr

http://xdaforums.com/showpost.php?p=12374073&postcount=7

Here you find the zip file for updating clk

http://xdaforums.com/showpost.php?p=12378215&postcount=34

Just found another point to save 3 to 5ma more

I installed Typhoons CM7 Image and was wondering why me drain in standby was 7 to 10ma with BT enabled.

Yesterday with Charansingh's nightly it was arround 3 to 5ma.

The solution is to set the low power flag on brcm_patchram_plus in init.rc

service hciattach /system/bin/brcm_patchram_plus --enable_lpm --enable_hci \

--baudrate 3000000 --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0

Also seen that in a lot of images hciattach service is set in init.rc and init.htcleo.rc

In my experience the hciattach service should start only in init.rc, before bluetoothd service.
[HD2 Android NAND Development] arifqur:
Wow!

Thank God for this.

Finally and hopefully this matter is solved.

Which Rom have you tested this kernel with?

Can I use the latest Tween's Rom?
[HD2 Android NAND Development] silverbluem:
ohohohohohoooooho!!!1

super man!! many many thanks

will try it now! :)
[HD2 Android NAND Development] seadersn:
pls report :)
[HD2 Android NAND Development] trilu:
I've tested with Charansingh CM7 nightly - but it should work with every rom which uses tytungs kernel v8 and is Gingerbread.

As mentioned, feedback for Froyo and Sense is welcome...
[HD2 Android NAND Development] mponte:
can anybody build a boot.img to flash via cwm?
[HD2 Android NAND Development] seadersn:
here you are :) magldr version; for cLK use fastboot flash:raw command. (you'll need your own initrd.gz or the one delivered with build).
[HD2 Android NAND Development] mponte:
i got cLK in Typhoon 2.8.0.

kernel is on a boot.img file to flash. can i only flash this file with cwm as is?

as i see the updater-script only updates the zImage file and modules

P.S.

what's about this?

package_extract_dir("boot", "/boot");

there is no boot folder, only zImage file
[HD2 Android NAND Development] seadersn:
cLK version doesn't exist for now. i will make one, but this will take roundabout 4-6 hours, as i have to sleep a little bit now (only two hours the last 24h).
[HD2 Android NAND Development] silverbluem:
Works like a charm!! On hyperdroid cm7

thanks!!
[HD2 Android NAND Development] trilu:
how can i build a boot.img file for clk?
[HD2 Android NAND Development] Sunmj:
so great news...thanks a lot

i'll try it just now
[HD2 Android NAND Development] dubie76:
Anyone try this on a sense rom yet? I'm running boy ppc rom has 60ma bt drain in stand by! !
[HD2 Android NAND Development] tytung:
Hi trilu,

Great job.

Thank you.

Regarding diff command:

cd tytungs-hastarins-linux_on_wince_htc
git diff > ../bt.diff
{or}
git format-patch -o ../patches origin
[HD2 Android NAND Development] tytung:
Create a folder including unyaffs, mkyaffs2image, unpack.sh, pack.sh, and boot.img (Get boot.img from cLK thread).

1. unpack.sh

if [ -f boot.img ]; then
rm -rf boot
mkdir boot
cd boot
../unyaffs ../boot.img

cd ..
rm -rf initrd
mkdir initrd
cd initrd
gzip -dc ../boot/initrd.gz | cpio -i
else
echo cannot find boot.img
fi

2. replace boot/zImage

3. pack.sh

cd initrd
find . | cpio -o -H newc | gzip -9 > ../boot/initrd.gz
cd ..
mkyaffs2image boot/ boot.img

Then you will get a modified boot.img.
[HD2 Android NAND Development] fa2k:
5-7mA with WLAN, BT and GPS on MIUI 1.3.18 (Froyo 2.2.1)

Thank a lot
[HD2 Android NAND Development] mponte:
trilu, can you make now a boot.img to test typhoon build?
[HD2 Android NAND Development] charnsingh_online:
If ur on clk and fastboot commands work i think u should be able to fastboot flash zimage zimage to update the kernel
[HD2 Android NAND Development] Evil_enc:
is the hd2 now officially supported? cant see any news.. all devices have working RC2. what about official cyanogenmod for hd2 leo? cant see anything on their website
[HD2 Android NAND Development] cobhc:
We'll never get official CM7 for the HD2 as the HD2 is not a native Android device, and there is licensing issues because of that.
[HD2 Android NAND Development] justj:
hyperdroid v10 rom / tytung r7 kernel

BT on standby from 70ma before patch to 10ma after patch.

Big improvement ! Genius!

Edit :

as it seems there's a speed trade off with this patch. Everything seems to be lagging a bit. Will try some other kernels and see if it is still cause the speed decrease.

Edit: am flash back to the old kernel. I don't know why this patch makes my phone lagging so much. Shame.
[HD2 Android NAND Development] tyrone1:
How do I install this with clockwork recovery ? Just install update.zip? Or choose install zip from sdcard? Thanks for your help.
[HD2 Android NAND Development] indrema:
you can do both

a: rename the file to update.zip & place it in the root of your sdcard

b: place it anywhere of your sdcard(i have subfolder called "zips" besides the regular "backup" under "clockworkmod" folder), choose install zip from sdcard & look for the file

i don't know if it is necessary but also made "Fix permisions" after install
[HD2 Android NAND Development] krot84:
I don't really get it. Should i install both the kernel and the patch for my rom or only the patch ?
[HD2 Android NAND Development] arifqur:
Tried it with Tween's Typhoon2.8.1 and CrawlingCity's3.1

I get standby of 13 to 17mA on both.

Previously I used to get around 70mA.

Great Job man.

You da Man
[HD2 Android NAND Development] D4rk50ul:
Testing on a test build of HyperDroidGBX with Tytung R8.1 kernel. So far 10-14ma drain in standby with Wifi, BT, GPS, 3G on. Standby was 2-5 with Wifi/BT off before patch.

Excellent.
[HD2 Android NAND Development] tyrone1:
Testing on hyperDroid gbx 10
[HD2 Android NAND Development] trilu:
Here it is - boot.img for clk with the initrd of typhoons latest CM image.

Please note, you must change also the files in /system/lib/modules, otherwise you get no wlan, etc. connection.
[HD2 Android NAND Development] dsreid:
HTC HD2, which file do i update with for CWR? just the patch file? i am running kernel tytung r7, update CM7 base 29,
[HD2 Android NAND Development] DaNnY549:
Thank You!! I WILL TEST IT!!
[HD2 Android NAND Development] trilu:
here is a update file for cwr

http://xdaforums.com/showpost.php?p=12374073&postcount=7

but this file will only work with magldr...
[HD2 Android NAND Development] clio94:
kernel works perfect also in american android sd rom :) thank you
[HD2 Android NAND Development] trilu:
Just found another point to save 3 to 5ma more :D

I installed Typhoons CM7 Image and was wondering why me drain in standby was 7 to 10ma with BT enabled.

Yesterday with Charansingh's nightly it was arround 3 to 5ma.

The solution is to set the low power flag on brcm_patchram_plus in init.rc

service hciattach /system/bin/brcm_patchram_plus --enable_lpm --enable_hci \

--baudrate 3000000 --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0

Also seen that in a lot of images hciattach service is set in init.rc and init.htcleo.rc

In my experience the hciattach service should start only in init.rc, before bluetoothd service.
[HD2 Android NAND Development] mponte:
Here you can take a cLK CWM update zip file with bootloader and modules all together.

I installed from this file, so it works.

Now I'm making a draining test with differents GPS/BT/Data Configuration.
[HD2 Android NAND Development] TheWizzard2203:
But after aplying this patch, the overclock functionality has gone and the highest speed is the default speed of 998mhz.
[HD2 Android NAND Development] 暗黑王:
good job man.

try the patch now.
[HD2 Android NAND Development] trilu:
Thats possible - its only a test kernel for me to fix the bluetooth problem. I am pretty sure that we see in the next hours/days some update on the kernels of rafpigna, tytung and the others :D
[HD2 Android NAND Development] felipemadox:
Pair Issue

After install this kernel, i cannot pair with my ad2p nokia bh-503 bluetooth headphone.
[HD2 Android NAND Development] trilu:
can you provide a logcat file?
[HD2 Android NAND Development] Mr.Observer:
My DOUUUUUG! <-- hadn't said that in a long while. thank you much :)
[HD2 Android NAND Development] pkoper:
Remove old pairing and pair again... helped me.
[HD2 Android NAND Development] buttami:
kernel works with MCCM GB V2.2 Gingerbread sd rom

good job

tnx
[HD2 Android NAND Development] chivychao:
thank you for your awesome work so much!
[HD2 Android NAND Development] mponte:
Testing results in Typhoon v2.8.0 with BT patch applied:

Wifi off | BT off | GPS off | Data off 5-7-5 mA

Wifi off | BT on | GPS off | Data off 10-11-10 mA

Wifi on | BT on | GPS off | Data off 13-19-13 mA

Wifi on | BT on | GPS off | Data on 18-13-12 mA

Wifi on | BT on | GPS on | Data on 13-13-18 mA

all results in standby. No BT device connected.

Tests for 6mins each option, with 2mins history rate interval (3 times), using Battery Monitor Widget. 2 mins interval between each other (after unlock screen and read results).
[HD2 Android NAND Development] karendar:
Whenever I try and unyaffs, I get "broken image file". Any idea why? Tried it on multiple boot.img in ubuntu, windows, etc.
[HD2 Android NAND Development] trilu:
with editing init.rc and enabling the --enable_lpm i get 3 to 5ma with Data on, BT on, Wifi and GPS off
[HD2 Android NAND Development] tytung:
Yes, --enable_lpm is necessary because lpm stands for low power mode.
[HD2 Android NAND Development] seadersn:
trilu, can you create a new patch file with the commands tytung provided, pls...? :)
[HD2 Android NAND Development] felipemadox:
Doesnt work.

They just back to work when i put back tytungr7
[HD2 Android NAND Development] tytung:
It works with my boot.img.
[HD2 Android NAND Development] FerretAD:
Working here - Thank-you very much, been waiting for this one :)

Will report average current tomorrow.
[HD2 Android NAND Development] pycomputing:
excelent thanks for all
[HD2 Android NAND Development] czacha234:
Hi,

I cant connect my BT headset to phone. It says is paired but not connected, when try to connect manually, its connecting and nothing happens. Dont know how to provide a logcat, sorry. Also tried unpair and pair it again, nothing. After applied this patch I get 9-15mA in standby, which is better result then before. Great work :D
[HD2 Android NAND Development] tytung:
His code has some unnecessary old code which is commented.

I have manually patch it with my git repository.
[HD2 Android NAND Development] tytung:
I have added some possible missing code from board-mahimahi.c and is compiling a new kernel.
[HD2 Android NAND Development] seadersn:
alright, thanks. :)
[HD2 Android NAND Development] buttami:
+1 some here
[HD2 Android NAND Development] trilu:
if you want or need i can upload you the whole kerneltree....

i've used as base the board_bravo files.

for all who having problems with pairing - without a logcat dump it is like reading a crystall ball.

you get a logcat dump in this way:

adb logcat > logcat.txt

and after 1 or 2 seconds press crtl + c
[HD2 Android NAND Development] waichai:
Iam using miui 1.3.18, patch this: http://xdaforums.com/showpost.php?p=12374073&postcount=7

Iam getting 9mA with BT on in standby even my BT headset is connected and on.

If your device won't see new bt device, try turn off and on in BT setting.
[HD2 Android NAND Development] tytung:
kernel_tytung_r8.2_beta_update.zip

http://www.multiupload.com/FEQVJQBYZR

Based on Trilu's patch

Removed some debug and unnecessary code, and added some possible missing code
[HD2 Android NAND Development] trilu:
you are realy fast :p

can you send me your changes - i mean the missing peaces?
[HD2 Android NAND Development] buttami:
D/AK8973 ( 184): Compass Start

D/dalvikvm( 2198): GC_CONCURRENT freed 397K, 55% free 2585K/5639K, external 0K/0K, paused 4ms+6ms

D/SettingsAppWidgetProvider( 2198): Widget is from a previous version... Let's update

D/SettingsAppWidgetProvider( 2198): No instances yet... Wait for at least one instance to exist before adding global settings

E/CachedBluetoothDevice( 2198): updating profiles for Motorola H700

V/CachedBluetoothDevice( 2198): Class: 200404

V/CachedBluetoothDevice( 2198): UUID:

V/CachedBluetoothDevice( 2198): 00001108-0000-1000-8000-00805f9b34fb

V/CachedBluetoothDevice( 2198): 0000111e-0000-1000-8000-00805f9b34fb

D/skia ( 311): purging 197K from font cache [24 entries]

I/ActivityManager( 230): Start proc com.google.android.apps.gesturesearch for broadcast com.google.android.apps.gesturesearch/.search.BatteryReceiver: pid=2208 uid=10098 gids={3003}

I/ActivityThread( 2208): Pub com.google.android.apps.gesturesearch.index: com.google.android.apps.gesturesearch.data.IndexProvider

I/ActivityThread( 2208): Pub com.google.android.apps.gesturesearch.history: com.google.android.apps.gesturesearch.data.QueryHistoryProvider

D/WifiService( 230): ACTION_SCREEN_ON

D/skia ( 311): purging 196K from font cache [25 entries]

D/WifiService( 230): ACTION_BATTERY_CHANGED pluggedType: 2

E/lights ( 230): ***: value=20 (Mode=1)

D/dalvikvm( 2162): GC_EXPLICIT freed 161K, 54% free 2505K/5379K, external 0K/0K, paused 27ms

E/lights ( 230): ***: value=55 (Mode=1)

E/lights ( 230): ***: manual set BL value=0 (Mode=1)

I/power ( 230): *** set_screen_state 0

D/WifiService( 230): ACTION_SCREEN_OFF

D/WifiService( 230): setting ACTION_DEVICE_IDLE timer for 900000ms

I/Process ( 230): Sending signal. PID: 2208 SIG: 9

I/Process ( 230): Sending signal. PID: 2184 SIG: 9

I/Process ( 230): Sending signal. PID: 2162 SIG: 9

I/Process ( 230): Sending signal. PID: 2198 SIG: 9

I/Process ( 230): Sending signal. PID: 2170 SIG: 9

W/ActivityManager( 230): Scheduling restart of crashed service com.android.bluetooth/.pbap.BluetoothPbapService in 5000ms

D/AK8973 ( 184): Compass CLOSE

D/SurfaceFlinger( 230): About to give-up screen, flinger = 0x93948

can this help you?
[HD2 Android NAND Development] mponte:
Applied this option ( --enable_lpm in init.rc) and the results are:

Wifi off | BT on | GPS off | Data off 9-10-9 mA

Wifi off | BT on | GPS off | Data on 10-9-9 mA

Wifi on | BT on | GPS off | Data on 14-14-15 mA
[HD2 Android NAND Development] tytung:
I think you don't need to upload the whole kernel tree.

Diff or Patch format files are more convenient than the whole kernel tree.

I also jumped into the Bluetooth battery drain issue several days ago.

My reference base is Nexus One.

Anyway, I have modified something and uploaded a r8.2 beta kernel.

Waiting for other users' testings in terms of the pair problem.
[HD2 Android NAND Development] almanbrother:
Can someone please tell me exactly how to do this?

Thanks in advance!
[HD2 Android NAND Development] tytung:
In board-htcleo.c

+
+static uint32_t bt_gpio_table_rev_CX[] = {
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_UART1_RTS, 2, GPIO_OUTPUT,
+	GPIO_PULL_UP, GPIO_8MA),
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_UART1_CTS, 2, GPIO_INPUT,
+	GPIO_PULL_UP, GPIO_8MA),
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_UART1_RX, 2, GPIO_INPUT,
+	GPIO_PULL_UP, GPIO_8MA),
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_UART1_TX, 2, GPIO_OUTPUT,
+	GPIO_PULL_UP, GPIO_8MA),
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_RESET_N, 0, GPIO_OUTPUT,
+	GPIO_PULL_DOWN, GPIO_4MA),
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_SHUTDOWN_N, 0, GPIO_OUTPUT,
+	GPIO_PULL_DOWN, GPIO_4MA),
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_CHIP_WAKE, 0, GPIO_OUTPUT,
+	GPIO_PULL_DOWN, GPIO_4MA),
+	PCOM_GPIO_CFG(HTCLEO_GPIO_BT_HOST_WAKE, 0, GPIO_INPUT,
+	GPIO_PULL_DOWN, GPIO_4MA),
+};

add the following lines in board-htcleo-rfkill.c

gpio_free(HTCLEO_GPIO_BT_SHUTDOWN_N);

gpio_free(HTCLEO_GPIO_BT_RESET_N);

static int htcleo_rfkill_remove(struct platform_device *dev)
{
rfkill_unregister(bt_rfk);
rfkill_destroy(bt_rfk);
gpio_free(HTCLEO_GPIO_BT_SHUTDOWN_N);
gpio_free(HTCLEO_GPIO_BT_RESET_N);

return 0;
}
[HD2 Android NAND Development] DuperMan:
Is the 8.2 beta for magldr or cLK?

EDIT

I'm on cLK 1.3.3 atm
[HD2 Android NAND Development] trilu:
did your kernel work for you?

i think the pairing problem comes from caching of the connection data in

/data/misc/bluetoothd

Maybe its worth to delete the content of the folder by typing

apt shell rm -r /data/misc/bluetoothd/*

and do an reboot?
[HD2 Android NAND Development] felipemadox:
Still not working.

I have deleted the old pair, install the new kernel and when i press on to pair i got

Nokia BH-503

Pairing...

And it stock on that.

Its weird, once with tytung they always pair.
[HD2 Android NAND Development] czacha234:
Thanks man, downloading now and will flash right away. I will let know after test. :D

EDIT:

After flashing new kernel, still the same. It does want to pair, once it pairied didnt want to connect to bt headset. But I had battery drain at 9mA without connected anything, according to current widget. Hopefuly ypu will be able to fix that. Thanks for your effort guys. :D
[HD2 Android NAND Development] seadersn:
you can easily find out yourself: open the zip, and if

boot folder = magldr

boot.img = cLK

:)
[HD2 Android NAND Development] DuperMan:
Thanks

I'll wait for a cLK version to help testing, hopefully before it's out of beta ;)
[HD2 Android NAND Development] trilu:
the bt_gpio_table_rev_CX[] is not needed, because its nearly the same as bt_gpio_table_rev and will in board_bravo only used if cdma version is detected.

if (is_cdma_version(system_rev)) {

bcm_bt_lpm_pdata.gpio_wake = BRAVO_CDMA_GPIO_BT_WAKE;

bravo_flashlight_data.torch = BRAVO_CDMA_GPIO_FLASHLIGHT_TORCH;

config_gpio_table(bt_gpio_table_rev_CX, ARRAY_SIZE(bt_gpio_table_rev_CX));

} else {

config_gpio_table(bt_gpio_table, ARRAY_SIZE(bt_gpio_table));

}

that is the only reference for this table...
[HD2 Android NAND Development] :
Sorry mods but:

thank you very much <3
[HD2 Android NAND Development] felipemadox:
Doesnt work.
[HD2 Android NAND Development] mponte:
Question (Post #65)

about post #45

in reference to post #33

This post is #76. You must read a little bit more.
[HD2 Android NAND Development] tytung:
Yes, my modified kernel still works.

I deleted my previous Bluetooth devices from Bluetooth settings and paired it again.

Edit:

The pic is so small after uploading it here. Just ignore it. :)
[HD2 Android NAND Development] felipemadox:
Weird.

Here just works with r7.
[HD2 Android NAND Development] justj:
Just installed the new beta kernel from tytung and it rocks!!

Works perfectly with Pongster's Hyperdroid v10.

BT on standby 9ma!!!!!!!!!!and no previous mentioned performance issue eiither.

RESPECT!!!!!!!!!!!
[HD2 Android NAND Development] almanbrother:
WOW!!! you invest more time in searching those posts and multiquote them then simply answering my question.

It's in mine opinion so useless to react that way. If it has been asked thousend times before then you would have a point, but now....

And by the way post #45???

Actualy my question isn't answered so far from post #1-80
[HD2 Android NAND Development] mponte:
Reboot twice. After 30mins in standby:

Wifi on | BT on | GPS off | Data on 9-13 mA

These were my default switches in WinMo for 24h/7d. I think an average of 11mA is good enough. Don't you?
[HD2 Android NAND Development] smakazmi:
This is a significant achievement. Thanks and Congratulations! :D
[HD2 Android NAND Development] Yom:
Cannot pair my Sony stereo headset...

With Tytung's 8.2 beta kernel, the phone just says "pairing... " and never does...

I am running HyperDroid CM7 1.0.3.

EDIT: It is not even seeing the headset when scanning...
[HD2 Android NAND Development] felipemadox:
Same thing with Nokia bh-503
[HD2 Android NAND Development] buttami:
Same thing with motorola h700
[HD2 Android NAND Development] waichai:
try turn on and off in BT Setting. it happen to me in first try.
[HD2 Android NAND Development] Rubanzip:
this fix is not working in coredroid 1.4 version
[HD2 Android NAND Development] Yom:
Did so, more than once, no cigar...
[HD2 Android NAND Development] pkoper:
It kind of hangs sometimes....

If stuck in "pairing..... " just try switching visibility off and back on during the process. Works for me if pairing doesn't work. Strange thing is, that it does not always happen. 5 out of ten times i need to toggle visibility during pairing in order to get a pair.
[HD2 Android NAND Development] seavers11:
Want to pair my bluetooth watch mbw150, but it shows "pairing" and nothing happen... with V8.1 everything works great :o
[HD2 Android NAND Development] trilu:
now i am inquiring ;)
[HD2 Android NAND Development] pkoper:
Have you set device visibility ON?
[HD2 Android NAND Development] trilu:
i had this effect also one time, but now its gone.

the problem is, that the bt chip is most time in deep sleep and every time when the ttyHS0 device send some bytes to the bt chip, the chip must wake up and it can be happen that the first bit is choked...

by scanning for devices, the chip can't sleep, because he is working...
[HD2 Android NAND Development] pkoper:
Ok, that would explain a few things.

While my headset was paired and connected I tried making a call via headset redial. It did not work so pressed the button several times. About a minute later my phone rang the number several times in a row.
[HD2 Android NAND Development] trilu:
was that with my kernel or tytungs one?

if it was with the new one from tytung, can you test it also with mine?

to go deeper in development, or testing i must reproduce the failure - that is the only possibility to do some debugging...

just a question - i have an european version of hd2, does all the people who have problems with pairing the US version?

maybe there are some differences in gpio to the chip....
[HD2 Android NAND Development] epos85:
Hi. I'm using GBX v10.. I have applied the patch and it works:) 9mA :D

But there are some problems... There is no line in 'init.rc' that says..

service hciattach /system/bin/brcm_patchram_plus --enable_lpm --enable_hci \

--baudrate 3000000 --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0

And when I'm trying to write the line above 'bluetoothd', its gone after I have rebooted.. I have saved the file "yes" as "root", but nothing works :-(

And a another thing..

'init.htcleo.rc' has that line, but I can't add ''--enable_lpm'' cause the flag is gone after rebooting the device :-(

What program should I use to edit the files with?

And should the line be in 'init.rc', 'init.htcleo.rc' or both?
[HD2 Android NAND Development] pkoper:
With Tytungs 8.2 beta....

I will try with yours.

PS. Euro HD2
[HD2 Android NAND Development] sjappie:
This one works great on a Hyperdroid rom!
[HD2 Android NAND Development] trilu:
init.rc is a startup script inside the initrd.gz. initrd.gz will decompressed by the kernel and holds the main file system. you cant edit the content of initrd.gz without decompress. best idea is to wait until the rom developers have adapt the patch...
[HD2 Android NAND Development] epos85:
Could you tell me how to, please:-)
[HD2 Android NAND Development] pkoper:
Ok... same behaviour with your kernel.

Sometimes BT seems non responsive. So if press redial 5 times on the BT headset and then switch the phones BT visibility on/off a few times, then the phone will redial 5 times in a row.

If I wait long enough, the phone will eventually redial itself. Maximum delay was about 15 to 20 seconds.

Hope this helps.