Htc Universal

[ShiroiKuma]

Edit: It looks like the bluetooth module is powered up by default.  I've updated titchy-hardware-support to turn it off.  I've no idea whether it will make much difference, though.

So how do I bring bluetooth up now?

hciconfig gives me nothing, no change when insmoding the two bluetooth module files in /lib/modules

This should power it up again:

Code: [Select]

devmem2 0x10000104 halfword 0xC6A0

Doesn't seem to work. hciconfig still gives me nothing.

I've tried many ways now, even rebooted, can't get it up. hconfig empty, ifconfig hci0 up - hci0: ERROR while getting interface flags: No such device, what's wrong?

[Sam Liddicott]

I've noticed twice now that if I send a text to a non-usb'd suspended universal and do not acknowledge the text, that the battery depletion rate increases.

Test:

fully charge phone., apm shows 99%
suspend for 10 hours
apm shows battery about 90%

fully charge phone
suspend
send text (don't acknowledge)
wait for screen to go black
wait 10 hours
apm shows battery about 81%

I also get
1. backlight button mostly doesn't work after resume
2. sometimes mouse pointer doesn't work after resume
3. sometimes device crashes on reboot
4. sometimes after reboot to wm6.1 (ranju's latest rom) mouse pointer or keyboard don't work until reset.

Sam

[Sam Liddicott]

I also find that the keyboard is not sensitive enough, I generally don't seem to hold the key down for long enough to register, I guess I need to reduce the debounce settings.

Sam

[Sam Liddicott]

128MB upgrade

I'm just picking who to do my 128MB upgrade, does anybody here have the upgrade knows someone who can make a recommendation?
(I'm based in the UK)

Sam

[datathief]

I've noticed twice now that if I send a text to a non-usb'd suspended universal and do not acknowledge the text, that the battery depletion rate increases.

Test:

fully charge phone., apm shows 99%
suspend for 10 hours
apm shows battery about 90%

fully charge phone
suspend
send text (don't acknowledge)
wait for screen to go black
wait 10 hours
apm shows battery about 81%

I also get
1. backlight button mostly doesn't work after resume
2. sometimes mouse pointer doesn't work after resume
3. sometimes device crashes on reboot
4. sometimes after reboot to wm6.1 (ranju's latest rom) mouse pointer or keyboard don't work until reset.

Sam

Do you get messages in syslog like 'Proxy exited with status 1'?  That would mean some apmd scripts are not being run, which would cause some of those symptoms.

If so, try running:

Code: [Select]

/etc/apm/apmd-proxy resume suspend and see if you get any error messages that might indicate which apm script is failing.  If one script fails, the rest don't get run at all (which is a bug in apmd in my opinion).

[ShiroiKuma]

3. sometimes device crashes on reboot
4. sometimes after reboot to wm6.1 (ranju's latest rom) mouse pointer or keyboard don't work until reset.

Don't use reset. It always messes up. When you want to reset to Windows, use halt, then soft reset with the stylus.

[datathief]

Edit: It looks like the bluetooth module is powered up by default.  I've updated titchy-hardware-support to turn it off.  I've no idea whether it will make much difference, though.

So how do I bring bluetooth up now?

hciconfig gives me nothing, no change when insmoding the two bluetooth module files in /lib/modules

This should power it up again:

Code: [Select]

devmem2 0x10000104 halfword 0xC6A0

Doesn't seem to work. hciconfig still gives me nothing.

I've tried many ways now, even rebooted, can't get it up. hconfig empty, ifconfig hci0 up - hci0: ERROR while getting interface flags: No such device, what's wrong?

There's a bluetooth reset line (I'm getting my information from http://wiki.xda-developers.com/index.php?p...=UniversalASIC3 if you're wondering).  Try:

Code: [Select]

devmem2 0x10000104 halfword 0xC620 # bt power on, reset low
devmem2 0x10000104 halfword 0xC6A0 # bt power on, reset high
Edit: You don't need to do the above

Code: [Select]

echo ttyS1 swave >/etc/bluetooth/uart
/etc/init.d/bluetooth restart

[datathief]

(Whilst trying to get bluetooth to work, I rebooted.  Out of curiosity I've just checked my syslog, and as far as I can tell, the last time I rebooted was May 7.  With the amount of surfing, e-mailing, chatting and SSHing I do, I'm shocked.  I think it's the most reliable and most useful phone i've ever owned.  Still feel a bit silly talking into it, though.   )

[ShiroiKuma]

Edit: You don't need to do the above

Code: [Select]

echo ttyS1 swave >/etc/bluetooth/uart
/etc/init.d/bluetooth restart

This doesn't seem to be working for me, after restarting bluetooth I get:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']# /etc/init.d/bluetooth restart
Restarting bluetooth: hcid.[/div]
then hciconfig still gives empty output.

[datathief]

Edit: You don't need to do the above

Code: [Select]

echo ttyS1 swave >/etc/bluetooth/uart
/etc/init.d/bluetooth restart

This doesn't seem to be working for me, after restarting bluetooth I get:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']# /etc/init.d/bluetooth restart
Restarting bluetooth: hcid.[/div]
then hciconfig still gives empty output.

Does the following do anything?

Code: [Select]

hciattach /dev/ttyS1 swaveDoes the blue LED start flashing?

[ShiroiKuma]

The hciattach worked, the bluetooth device is up now and the led flashing, I'll experiment with it now. You said the above devmems are unnecessary. What's the best way to bring it down now, battery-wise?

[datathief]

What's the best way to bring it down now, battery-wise?

The driver seems to power it down properly.  Just use:

Code: [Select]

/etc/init.d/bluetooth stopOr if all else fails, kill the 'hciattach' process.

[Sam Liddicott]

I've noticed twice now that if I send a text to a non-usb'd suspended universal and do not acknowledge the text, that the battery depletion rate increases.

Test:

fully charge phone., apm shows 99%
suspend for 10 hours
apm shows battery about 90%

fully charge phone
suspend
send text (don't acknowledge)
wait for screen to go black
wait 10 hours
apm shows battery about 81%

I also get
1. backlight button mostly doesn't work after resume
2. sometimes mouse pointer doesn't work after resume
3. sometimes device crashes on reboot
4. sometimes after reboot to wm6.1 (ranju's latest rom) mouse pointer or keyboard don't work until reset.

Sam

Do you get messages in syslog like 'Proxy exited with status 1'?  That would mean some apmd scripts are not being run, which would cause some of those symptoms.

If so, try running:

Code: [Select]

/etc/apm/apmd-proxy resume suspend and see if you get any error messages that might indicate which apm script is failing.  If one script fails, the rest don't get run at all (which is a bug in apmd in my opinion).

It seems like it is nothing to do with sms or autosuspend, I'm just back to losing 2% an hour again instead of 1% an hour which I was getting after you fixed the bluetooth suspend.

Sam

[datathief]

It seems like it is nothing to do with sms or autosuspend, I'm just back to losing 2% an hour again instead of 1% an hour which I was getting after you fixed the bluetooth suspend.

Sam

It's difficult for me to test battery life  -  my phone is in use most of the day, and on charge overnight.  I'll try to find an opportunity.

In the meantime:

• Do you get good battery life on your first suspend after a reboot, and bad battery life on every subsequent suspend?  If so, the kernel must be doing something upon resume.
• When you're getting bad battery life, run:
  Code: [Select]
  devmem2 0x10000105 byteIf the result (the last number on the last line of output) is 0x86, bluetooth is powered down.  If the result is 0xC6, it's not, and that could be the culprit.
• Do you have the htcuniversal_acx and/or acx modules loaded?

[Sam Liddicott]

It seems like it is nothing to do with sms or autosuspend, I'm just back to losing 2% an hour again instead of 1% an hour which I was getting after you fixed the bluetooth suspend.

Sam

It's difficult for me to test battery life  -  my phone is in use most of the day, and on charge overnight.  I'll try to find an opportunity.

In the meantime:

• Do you get good battery life on your first suspend after a reboot, and bad battery life on every subsequent suspend?  If so, the kernel must be doing something upon resume.
• When you're getting bad battery life, run:
  Code: [Select]
  devmem2 0x10000105 byteIf the result (the last number on the last line of output) is 0x86, bluetooth is powered down.  If the result is 0xC6, it's not, and that could be the culprit.
• Do you have the htcuniversal_acx and/or acx modules loaded?

bluetooth is off according to that and no acx modules are loaded.

I'll do more experiments tonight, and still losing 2% per hour.

Sam