[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release

[dadaR6]

Originally Posted by jerryyyyy

Settings do not work for me. If the "Power Control" widget (whatever that is?), works through the same settings, likely not to work either. Seems like, if I want BT to work I have to go through the steps outlines in XDA... a bit too much work...

Cheers

In my case, I had to boot WinMo with BT OFF, then do NOT turn it on in WinMo, leave it OFF, then launch Haret. After that I am able to toggle BT ON/OFF in Android otherwise it would just fail to enable.

Hope it helps.

[arrrghhh]

Originally Posted by dadaR6

In my case, I had to boot WinMo with BT OFF, then do NOT turn it on in WinMo, leave it OFF, then launch Haret. After that I am able to toggle BT ON/OFF in Android otherwise it would just fail to enable.

Hope it helps.

I thought it just messed up sleep? If this is true I'll add it to the first post... such oddities all because of WinMo!

[dadaR6]

Originally Posted by arrrghhh

I thought it just messed up sleep? If this is true I'll add it to the first post... such oddities all because of WinMo!

Well, honestly I dont remember which one was it, but in one case I was getting no sleep or cannot start BT if BT was ON at some point in WinMo. I tried it so many times, that I forgot which one was causing what. lol. Now BT is always OFF in WinMo from beginning to end and I dont have any issues anymore (with BT at least...).

I am getting the same oddity as others regarding the service signal: receive a call then I hang up, then the no service icon appears but I can still receive calls!, I just cannot place any until I switch to Airplane Mode.

[dadaR6]

Originally Posted by dadaR6

Well, honestly I dont remember which one was it, but in one case I was getting no sleep or cannot start BT if BT was ON at some point in WinMo. I tried it so many times, that I forgot which one was causing what. lol. Now BT is always OFF in WinMo from beginning to end and I dont have any issues anymore (with BT at least...).

I am getting the same oddity as others regarding the service signal: receive a call then I hang up, then the no service icon appears but I can still receive calls!, I just cannot place any until I switch to Airplane Mode.

I tried again to confirm the behavior:
- If BT was ON when starting Haret, BT will not start in Android and it will not let the phone enter deep sleeps.
- If BT was OFF when starting Haret but was ON at some point after the boot in WinMo, then in Android, BT will not start, but the phone will enter deep sleeps. Once you try to start BT, phone will not sleep anymore.
- If BT was OFF from beginning to end in WinMo, then in Android, BT will start and phone will enter deeps sleeps with BT ON or OFF.

[cutecool]

hey i didnt understand if i want to put Android n run it from a particular folder so where should i add tat command line in start up

for eg.. in my SD card i make a folder ANDROID

so will my startup look like this..

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=Android lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=1 pm.sleep_mode=1 physkeyboard=rhod400"
boot

[arrrghhh]

Originally Posted by dadaR6

I tried again to confirm the behavior:
- If BT was ON when starting Haret, BT will not start in Android and it will not let the phone enter deep sleeps.
- If BT was OFF when starting Haret but was ON at some point after the boot in WinMo, then in Android, BT will not start, but the phone will enter deep sleeps. Once you try to start BT, phone will not sleep anymore.
- If BT was OFF from beginning to end in WinMo, then in Android, BT will start and phone will enter deeps sleeps with BT ON or OFF.

Thanks! I'll add this to the caveat list.

Originally Posted by cutecool

hey i didnt understand if i want to put Android n run it from a particular folder so where should i add tat command line in start up

for eg.. in my SD card i make a folder ANDROID

so will my startup look like this..

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=Android lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=1 pm.sleep_mode=1 physkeyboard=rhod400"
boot

You have it correct, but if the folder name is in all caps - ANDROID, then rel_path=ANDROID. Linux is CaSe sensitive!

[jerryyyyy]

Originally Posted by dadaR6

In my case, I had to boot WinMo with BT OFF, then do NOT turn it on in WinMo, leave it OFF, then launch Haret. After that I am able to toggle BT ON/OFF in Android otherwise it would just fail to enable.

Hope it helps.

This was the key!

I was able to pair my TP2 with my Motorola S9 headset and also with my car BT!