Database Info

Volume turns screen on when in lock mode

Got a strange problem....
If I press up/down volume when the phone is supposed to be locked it turns the screen on. Obviously if my phone is in my pocket this is going to happen all the time and waste the battery etc.
Any ideas how I can prevent this from happenning?
cheers.

Thats a feature, not a bug
I know on MIUI-rom you can turn it off in settings, which rom are you using?!

I'm using Shadow Hawk v2.1
Looked everywhere for a setting, just can't find it.

I never tried that rom, but in the thread where to download shadow hawk you should have a look in the feature list
Code:
*Wake phone with volume keys (thanks to lowveld)

tangerine0072000 said:
Got a strange problem....
If I press up/down volume when the phone is supposed to be locked it turns the screen on. Obviously if my phone is in my pocket this is going to happen all the time and waste the battery etc.
Any ideas how I can prevent this from happenning?
cheers.
Click to expand...
Click to collapse
Hmmm...Maybe you can turn off this option from within RCMix tweaks, if you enabled it from there. I've never used that ROM, but i understand that it uses RCMix tweaks and it would do you good to find out if there is a volume wake setting in there. If there isn't, i have the fix for it, and i can give it to you if you're willing to try it. First let me know if you can find anything in the RCMix tweaks.
Cheers

thanks chaps, I had a look in RC tweaks initially before posting, but there is nothing in there that refferences the volume controls.

by the way, what was the fix ?

tangerine0072000 said:
by the way, what was the fix ?
Click to expand...
Click to collapse
Well, the solution is to replace android.policy.jar with the attached file.
This is located in system/framework
Use root explorer or es file explorer with root access, mount system as r/w and replace the said file in the above folder with the one below. Reboot. That's it...your volume buttons will just function as normal volume rocker, and will not wake the phone up anymore.
P.S. : While i don't expect any problem at all, i would highly recommend taking a nandroid backup, and also backing up your original android.policy.jar in case something goes wrong, or you want to revert back to volume rocker wake... Do post back if it works for you.
CLICK TO DOWNLOAD

thanks for the info, I got the download. I tried mounting through these apps, but can't find an option for it. Do I need to mount read/write via the ADB ?
Not done this procedure before.
thanks,

I managed to replace the file using 'root explorer'. Did a reboot, but still got the problem with the volume switching the screen on.

so in my infinate wisdom I thought I might as well put the orignal file back which I did and rebooted. Then the phone wouldn't boot, stuck on HTC logo.
Then I thought I would restore my nandroid back (which I made last night). Phone will only still boot to HTC screen. Doh !
Did this serveral times, formating, clearing cache, restoring backup, but still no joy.

You should read this thread!
edit:
another guide

think I have corrupted cache as I know get....
E:Can't open /cache/recovery/log comming alot when trying to do anything in recovery mode.

tangerine0072000 said:
think I have corrupted cache as I know get....
E:Can't open /cache/recovery/log comming alot when trying to do anything in recovery mode.
Click to expand...
Click to collapse
did you read the guides of my last post? they are may solving your problems!

really wiered.
when I do 'dmesg | grep mmc0' I just get the command prompt...
~ # dmesg | grep mmc0
dmesg | grep mmc0
~ #
I contined to perform 'mke2fs /dev/block/mmcblk0p27'
~ # mke2fs /dev/block/mmcblk0p27
mke2fs /dev/block/mmcblk0p27
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
76912 inodes, 307196 blocks
15359 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
38 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: done
Writing superblocks and filesystem accounting information:
done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override
~ #
then tried to install my rom which failed part way through.

I am now getting some response from ADB, no errors that I can see.
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 6.994781] mmc0: No card detect facilities available
<6>[ 6.995300] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.995544] mmc0: Platform slot type: MMC
<6>[ 6.995666] mmc0: 4 bit data mode disabled
<6>[ 6.995819] mmc0: 8 bit data mode enabled
<6>[ 6.996032] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.996154] mmc0: Slot eject status = 0
<6>[ 6.996398] mmc0: Power save feature enable = 1
<6>[ 6.996520] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2c8000
<6>[ 6.996765] mmc0: DM cmd busaddr 0x0c2c8000, cmdptr busaddr 0x0c2c8300
<6>[ 7.150024] mmc0: new high speed MMC card at address 0001
<6>[ 7.151672] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

[Q] eMMC Fried?

Ok I have searched through all the relevant eMMc fried posts however I have not found a similar post to this with the same cmd return so you help would be appreciated..
After the dmesg grep command this was what the cmd returned...
Code:
C:\android-tools\android-tools>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 7.922210] mmc0: No card detect facilities available
<6>[ 7.922760] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.923004] mmc0: Platform slot type: MMC
<6>[ 7.923126] mmc0: 4 bit data mode disabled
<6>[ 7.923339] mmc0: 8 bit data mode enabled
<6>[ 7.923492] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.923736] mmc0: Slot eject status = 0
<6>[ 7.923858] mmc0: Power save feature enable = 1
<6>[ 7.923980] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2d3000
<6>[ 7.924224] mmc0: DM cmd busaddr 0x0c2d3000, cmdptr busaddr 0x0c2d3300
<6>[ 8.077545] mmc0: new high speed MMC card at address 0001
<6>[ 8.079345] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
Is this a fried chip or some other issue?
I am still getting the usual fried error in the bootloader:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Currently running:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
Thanks for your help.

Your eMMC is fine.
Wipe your /cache from recovery. Use 4EXT

veejayjameson said:
Ok I have searched through all the relevant eMMc fried posts however I have not found a similar post to this with the same cmd return so you help would be appreciated..
After the dmesg grep command this was what the cmd returned...
Code:
C:\android-tools\android-tools>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 7.922210] mmc0: No card detect facilities available
<6>[ 7.922760] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.923004] mmc0: Platform slot type: MMC
<6>[ 7.923126] mmc0: 4 bit data mode disabled
<6>[ 7.923339] mmc0: 8 bit data mode enabled
<6>[ 7.923492] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.923736] mmc0: Slot eject status = 0
<6>[ 7.923858] mmc0: Power save feature enable = 1
<6>[ 7.923980] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2d3000
<6>[ 7.924224] mmc0: DM cmd busaddr 0x0c2d3000, cmdptr busaddr 0x0c2d3300
<6>[ 8.077545] mmc0: new high speed MMC card at address 0001
<6>[ 8.079345] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
Is this a fried chip or some other issue?
I am still getting the usual fried error in the bootloader:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Currently running:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
Thanks for your help.
Click to expand...
Click to collapse
Try wipe the whole phone and install a new rom xD

massi99 said:
Try wipe the whole phone and install a new rom xD
Click to expand...
Click to collapse
+1 Yup, that would be my advice too... it's just your cache partition that gone tits-up, and i think a format of the cache should solve it. But why not just be double sure and nuke all the bloody partitions and do a clean flash!

massi99 said:
Try wipe the whole phone and install a new rom xD
Click to expand...
Click to collapse
apk24 said:
+1 Yup, that would be my advice too... it's just your cache partition that gone tits-up, and i think a format of the cache should solve it. But why not just be double sure and nuke all the bloody partitions and do a clean flash!
Click to expand...
Click to collapse
Only one of the "all the bloody partitions" can give this error. Guess which one is it...
But nothing against the double sure, full wipe and clean install of new ROM should solve this for sure
I recommend to use 4EXT Recovery to convert all partitions to ext4 filesystem, then format/wipe all of them, then install a new ROM
But if he wants to keep the present ROM, just wiping cache is the solution...

amidabuddha said:
Only one of the "all the bloody partitions" can give this error. Guess which one is it...
But nothing against the double sure, full wipe and clean install of new ROM should solve this for sure
I recommend to use 4EXT Recovery to convert all partitions to ext4 filesystem, then format/wipe all of them, then install a new ROM
But if he wants to keep the present ROM, just wiping cache is the solution...
Click to expand...
Click to collapse
My favorite savior of bricked devices!
Wherever there's a potential brick, i find you there... maybe i'm vain, but it sure does make me feel secure knowing that there is someone like you around at the DS forum!

I have the same problem. I think my cache partition is corrupted. But after many try I can't format it. It take long time to format.
Also I cant flash 4ext or anything else via adb, fastboot or clockworkmod.
Can HTC service center solved this? Or they will just change the whole PCB?
Plz help me.
Sent from my HTC Legend using xda premium

enigmaamit said:
My favorite savior of bricked devices!
Wherever there's a potential brick, i find you there... maybe i'm vain, but it sure does make me feel secure knowing that there is someone like you around at the DS forum!
Click to expand...
Click to collapse
+1 to that !

Some how I've f***-up /data and /cache partitions [desperately needing help please]

Hello,
Will installing a new rom on my S-OFF Desire S, it has been a glitch and I've removed the battery to reboot the phone. Now I'm stuck at the "htc logo step".
After some investigation it appears that neither /cache nor /data are now mountable.
I've been think that my eMMc card (which belongs to the faulty serie (M4G2DE)) may have been fried. How ever It appears it is not the case since using adb shell to issue
Code:
# cat /proc/kmsg | grep mmc0
Code:
<3>[ 10.141387] mmc0: No card detect facilities available
<6>[ 10.142028] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 10.142150] mmc0: Platform slot type: MMC
<6>[ 10.142395] mmc0: 4 bit data mode disabled
<6>[ 10.142517] mmc0: 8 bit data mode enabled
<6>[ 10.142639] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 10.142883] mmc0: Slot eject status = 0
<6>[ 10.143005] mmc0: Power save feature enable = 1
<6>[ 10.143249] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0b8c8000
<6>[ 10.143371] mmc0: DM cmd busaddr 0x0b8c8000, cmdptr busaddr 0x0b8c8300
<6>[ 10.296691] mmc0: new high speed MMC card at address 0001
<6>[ 10.297943] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 34.849822] mmc0: Failed to get card ready i = 126959
<6>[ 34.850036] mmc0: reinit card
<4>[ 34.850128] mmc0: Starting deferred resume
<6>[ 36.891876] mmc0: Deferred resume failed
<3>[ 60.337951] mmc0: DMA channel flushed (0x80000004)
<6>[ 60.338317] mmc0: Controller has been reset
<6>[ 60.338562] mmc0: Worked around bug 1535304
<3>[ 60.339935] mmc0: DMA channel flushed (0x80000004)
<6>[ 60.340301] mmc0: Controller has been reset
<6>[ 60.340545] mmc0: Worked around bug 1535304
<6>[ 60.347320] mmc0: reinit card
I've tried to clean the file systems using e2fsck but also to make brand new fs using mke2fs and mkfs.ext2, these processes have be able to run, but the mount still fails :
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
Click to expand...
Click to collapse
I've been going through several thread here and there : http://forum.xda-developers.com/showthread.php?t=1305950 ; http://forum.xda-developers.com/showthread.php?t=1456036 ; http://forum.xda-developers.com/showthread.php?t=1854558
there is some tips inhere but no working solution, have you any suggestions ? Is there any way to "go back" to standard settings for theses two partitions ?
Thanks a lot !
François.

Can you boot to recovery? If so, have you tried formatting the partitions from there?
Sent from my Desire S using xda app-developers app

Can you boot to recovery? If so, have you tried formatting the partitions from there?
Click to expand...
Click to collapse
Yes I can boot to recovery, and I've tried formatting cache/data partitions, it was not successful.
Should I give it a try with ADB shell ?
Thanks for helping !
F.

[email protected] said:
Yes I can boot to recovery, and I've tried formatting cache/data partitions, it was not successful.
Should I give it a try with ADB shell ?
Thanks for helping !
F.
Click to expand...
Click to collapse
Try 4EXT Recovery if you are using different.
Another solution is to flash a RUU it will restore everything. But be carefully for the version, it has to be the same or higher of your current one
EDIT: looked at the first post and I am sorry to say this but your EMMC is corrupted.
Code:
<3>[ 34.849822] mmc0: Failed to get card ready i = 126959
<6>[ 34.850036] mmc0: reinit card
<4>[ 34.850128] mmc0: Starting deferred resume
<6>[ 36.891876] mmc0: Deferred resume failed
Read carefully through this thread there is a scanner that analyzes corrupted emmc card and it *may* (if you are lucky) to isolate the bad blocks and allows to use the device again with a bit shortened storage. No guarantees. The other way is a replacement of the chip - you can find one here

amidabuddha said:
EDIT: looked at the first post and I am sorry to say this but your EMMC is corrupted.
Click to expand...
Click to collapse
My should question should have been "is my eMMC corrupted", thanks for carefully reading my post.
I'll give a try to the software solution ASAP, thanks for pointing it out !

Read carefully through this thread there is a scanner that analyzes corrupted emmc card and it *may* (if you are lucky) to isolate the bad blocks and allows to use the device again with a bit shortened storage. No guarantees. The other way is a replacement of the chip - you can find one here
Click to expand...
Click to collapse
Scan have been able to go through the whole eMMC's partitions. I would like to believe that the eMMC is still some how usable, but it can't use them. Should I try to "shift" the partitions, to try to get ride of the old file system ?
Thanks again,
F.

[email protected] said:
Scan have been able to go through the whole eMMC's partitions. I would like to believe that the eMMC is still some how usable, but it can't use them. Should I try to "shift" the partitions, to try to get ride of the old file system ?
Thanks again,
F.
Click to expand...
Click to collapse
Sorry it didn't helped. Unfortunately I am not aware of any other method besides replacement to suggest
Sent from my HTC Desire S

There are a few threads were they use the sd card to load a rom with fried emc. I don't know anything more about it.
Sent from my Desire S using xda app-developers app

There are a few threads were they use the sd card to load a rom with fried emc. I don't know anything more about it.
Click to expand...
Click to collapse
Yeah this one for example http://forum.xda-developers.com/showthread.php?t=1756287
but I fail using the provided boot.img with fastboot
The other way is a replacement of the chip - you can find one here
Click to expand...
Click to collapse
Since the eMMC seems to be badly fried, I'm now considering physical replacement. So I've watched the following disassembly video : http://www.youtube.com/watch?v=W7sp3gN-vc0
It does not show the mother border without it's protections, so I am wondering what I'll have to do once the protection removed ? any soldering work ?
A last question about the site you've mentioned (parts4repair.com) is it reliable ?

[email protected] said:
Yeah this one for example http://forum.xda-developers.com/showthread.php?t=1756287
but I fail using the provided boot.img with fastboot
Since the eMMC seems to be badly fried, I'm now considering physical replacement. So I've watched the following disassembly video : http://www.youtube.com/watch?v=W7sp3gN-vc0
It does not show the mother border without it's protections, so I am wondering what I'll have to do once the protection removed ? any soldering work ?
A last question about the site you've mentioned (parts4repair.com) is it reliable ?
Click to expand...
Click to collapse
Luckily I have never ordered a chip for myself but this site was referenced from another users in the past. It is even shipped with a bootloader preinstalled so you just have to put it into the device.
As per the soldering process IMO is best to use a services of a skilled technician to do the job
Sent from my HTC Desire S

No WiFi - wlan0 device can't be found. "dhdsdio_probe_attach: si_attach failed!".

No WiFi - wlan0 device can't be found. "dhdsdio_probe_attach: si_attach failed!".
Hi all,
I have a UK Sensation XE that I've had for 18 months. My WiFi has not worked for many months, maybe a year. I am pretty sure the problem first started on GB, because I remember doing an OTA update to stock ICS and hoping it would fix the problem and it didn't.
I just started trying to seriously fix the problem a few days ago. Since then, I have researched on here and Google for hours and hours, and tried every suggestion I could find. I have done lots of diagnostics.
What I've discovered is that the WiFi driver does load, but it reports in dmesg that it can't find the device. Therefore it does not create wlan0. Therefore wpa_supplicant cannot load.
Everything else on the phone works OK - 2G/3G, Bluetooth, USB, etc. Just WiFi is broken.
I am wondering if maybe my WiFi hardware is bust. But then again, I do see the same symptoms on other posts - like this one and this one. The first of those two posts reported it worked for him when he went back to Stock 2.2, suggesting there was some software cause.
dmesg shows the following (I've edited a bit in the middle so to not make this message too long - full dmesg output is in attached txt) :
Code:
gannet_setup
gannet initialized OK
[WLAN] ## wifi_probe
[WLAN][WRN] wifi_set_power = 1
pyramid_wifi_power: 1
EXT4-fs (mmcblk0p22): re-mounted. Opts: user_xattr,barrier=0,data=ordered
[WLAN] wifi_set_carddetect = 1
pyramid_wifi_set_carddetect: 1
mmc2: Slot status change detected (0 -> 1)
[WLAN] Dongle Host Driver, version 5.90.125.120
mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
mmc2: new high speed SDIO card at address 0001
[WLAN] alloc static buf at cf9c0000!
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
EXT4-fs (mmcblk0p22): re-mounted. Opts: user_xattr,barrier=0,data=ordered
mmc2: CMD53: Data timeout
mmc2: SDCC PWR is ON
mmc2: SDCC clks are ON, MCLK rate=48000000
mmc2: SDCC irq is enabled
===== SDCC-CORE: Register Dumps @base=0xd08a6000 =====
.. cut a bunch of Reg= values ..
mmc2: PIO mode
mmc2: xfer_size=4, data_xfered=0, xfer_remain=4
mmc2: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
[COLOR="Red"][WLAN][WRN] dhdsdio_probe_attach: si_attach failed!
[WLAN][WRN] dhdsdio_probe: dhdsdio_probe_attach failed
[WLAN][WRN] dhd_module_init: wifi_fail_retry is true
[WLAN] ## wifi_remove
[WLAN][WRN] wifi_set_power = 0
pyramid_wifi_power: 0
[WLAN] wifi_set_carddetect = 0
pyramid_wifi_set_carddetect: 0
mmc2: Slot status change detected (1 -> 0)
mmc2: card 0001 removed
[WLAN] ## wifi_remove leave
[WLAN] module init fail, try again!
[/COLOR]pyramid_wifi_power: 1
pyramid_wifi_set_carddetect: 1
mmc2: Slot status change detected (0 -> 1)
[WLAN] Dongle Host Driver, version 5.90.125.120
I have attached a longer section of dmesg output, starting at boot and going a bit past the last reference to WLAN. The above dmesg snippet starts on line 760 of the attached dmesg txt file. I attached the fuller log in case the dmesg output shows some other error, not tagged WLAN, that I don't recognise as being a problem.
The bcmdhd.ko module is loaded OK:
Code:
# lsmod
tun 14813 0 - Live 0xbf091000
bcmdhd 483764 0 - Live 0xbf005000
kineto_gan 4230 0 - Live 0xbf000000
In logcat, there are various errors from wpa_supplicant and other, which all basically just indicate that it can't find wlan0. Here's a small sample:
Code:
E/wpa_supplicant( 5847): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 5847): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 5847): wlan0: Failed to initialize driver interface
This is confirmed from shell:
Code:
# ip link ls wlan0
ip: can't find device 'wlan0'
The problem started on stock, I think stock GB. I do not know of any trigger for it happening.
Around that time I was playing around with rooting for the first time, and I tried Revolution S-OFF which I recall changed my HBOOT from 1.19 to 1.17 or something. But that's as far as I got at the time, I just ran Revolution S-Off, I remember it changed my HBOOT version on phone startup, and then I never tried anything more with flashing/rooting.
I do not know if the Wifi problem started at the same time I tried that hboot change. I cannot remember exactly when the WiFi broke, I don't know if anything triggered it.
All I am pretty sure of is that the problem started on stock GB, and then it was not resolved when I OTA updated to stock ICS (the stock ICS upgrade then changed my hboot to 1.29).
So I know the problem existed on Stock ICS. I think it happened also on stock GB. Then this is what I have also tried recently, in the last week, since I first started flashing/rooting/customising my phone:
Full phone wipe - used 4Ext to do complete wipe of all partitions, before installing new ROMs
Tried with a) no SD card at all, b) two different SD cards, c) did a complete format of one SD card
Tried without sim-card, also tried WiFix to set country code - doubt this has anything to do with it though as there's not even a wlan0 device.
Stock 3.33 FW, and then XDA-Dev 3.32 FW and XDA-Dev 3.33 FW
Stock HTC ICS release as per OTA update
Android Revolution HD 7.1 ROM 4.0.3 ICS
Elegancia ROM 3.70 ROM 4.0.4 ICS
Stock, Faux, Sebastian and Bricked kernels
Originally HTCDev locked, and now unlocked
Originally S-On, and now S-Off (Hboot 1.27)
Flashing boot.img separately with fastboot flash boot boot.img
Flashing ROM with 4Ext SmartFlash (even though I had S-OFF) - and then turning it off again and re-flashing.
Deleting wpa_supplicant.conf (not that this should work as issue is before supplicant. I've put the conf back now.)
So right now my phone is:
HTCDev unlock
S-Off, HBoot 1.27 (I used Juopunutbear-off with the 'wire trick')
4Ext Flash Recovery
Elegancia Rom 3.70 with Bricked kernel
I have searched so much and tried so many things, so I would be super grateful for any help at all. Maybe it's just a HW fault, but I have seen other people with the same symptoms of dmesg reporting it can't find the device, and some of those people did have the issues caused by SW problems, so I am hoping there is still some chance it's resolvable.
Thanks in advance!

No thoughts from anyone?
Would be great to get any thoughts or feedback - even if it's just to say that the HW is broken.

I've been looking all over for a solution for this problem myself. WiFi 'died' with an OTA a while back, none of the suggestions found all over work.
WiFix (basically changing the region) doesn't apply, wlan0 doesn't even start properly.
You mentioned BT is working, but I can see devices, not connect to them, so for me BT is partially working.
What I tried so far:
Different FWs/RUUs, even going back to Gingerbread!
Different RIL - FW/Radio combos
Different ROMs on Universal 3.33 FW as well as FWs from RUUs
I even put a Z710e RUU on it to see if that might work.
Device:
Sensation XE Z715e, currently on: HBoot 1.27.1100, FW 3.33.401.153 Radio11.76C.3504.00U_11.29A.3504.18_M
Stock Rom lsmod:
Code:
bcm4329 225933 0 - Live 0xbf03c000
kineto_gan 4190 0 - Live 0xbf000000
CM10.1 lsmod:
Code:
bcmdhd 444356 0 - Live 0x00000000
I see the same errors as OP in my logcat and dmesg.
I'm starting to suspect the chip is fritzed and needs to be replaced (I can't heat it as suggested here: http://forum.xda-developers.com/showpost.php?p=38165494&postcount=66 )
My other Z715e is unaffected.

[Q] Random restarts

My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.

Moon2 said:
My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.
Click to expand...
Click to collapse
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?

DennisBold said:
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?
Click to expand...
Click to collapse
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)

I'm having the same problem with my sensation with alternative battery!!! Please help!!!

It just happened again and I've got another logcat, I'll try and do the dmesg now.
I've tried letting the phone sleep without wifi/3g, taking sd card out, formatting it.

Moon2 said:
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)
Click to expand...
Click to collapse
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?

DennisBold said:
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?
Click to expand...
Click to collapse
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.

Moon2 said:
Miui v4
Click to expand...
Click to collapse
Is your GPS enabled, and does this happen when your GPS is disabled?
Moon2 said:
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.
Click to expand...
Click to collapse
Never really looked at that, well, the only thing I can connect it with is GPS.

DennisBold said:
Is your GPS enabled, and does this happen when your GPS is disabled?
Click to expand...
Click to collapse
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.

Moon2 said:
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.
Click to expand...
Click to collapse
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?

DennisBold said:
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?
Click to expand...
Click to collapse
No, I've tried all of the roms with & without adding any apps.

Moon2 said:
No, I've tried all of the roms with & without adding any apps.
Click to expand...
Click to collapse
There's not exactly any errors other than this on dmesg.
Code:
<3>[ 475.735900] init: cannot execve('/system/bin/DxDrmServerIpc'): Permission denied
That isn't really a problem. Neither are these:
Code:
E/MobileDataStateTracker( 242): Error mapping networkType 23 to apnType.
Code:
D/MobileDataStateTracker( 242): internet: mMobileDataState=DISCONNECTED mTeardownRequested=false got [AnyDataCSC] : type=internet state=DISCONNECTED reason=dataDetached apn=null roaming=false unavailable=true NetworkType=0 NetworkTypeName=UNKNOWN entitleError=0 apnCarrier=null

I've just installed cm9 and run the logcat to just before it rebooted.

Moon2 said:
I've just installed cm9 and run the logcat to just before it rebooted.
Click to expand...
Click to collapse
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.

DennisBold said:
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.
Click to expand...
Click to collapse
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.

Moon2 said:
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.
Click to expand...
Click to collapse
Thanks.
Can you try:
Code:
adb shell
dmesg | grep mmc
And copy and paste the results?
You should see:
Code:
[email protected]:/ # dmesg | grep mmc
dmesg | grep mmc
[email protected]:/ #
---------- Post added at 08:04 PM ---------- Previous post was at 07:33 PM ----------
Could you run?
Code:
cat /sys/class/block/mmcblk0/device/name

Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M

Moon2 said:
Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M
Click to expand...
Click to collapse
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc

DennisBold said:
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc
Click to expand...
Click to collapse
Code:
dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: poweron_status=1 board_pyramid.disable_ua
rt3=0 diag.enabled=0 board_pyramid.debug_uart=0 userdata_sel=0 androidboot.emmc=
true androidboot.pagesize=2048 androidboot.baseband=10.14.9035.01_M androidboo
t.cid=11111111 androidboot.batt_poweron=good_battery androidboot.carrier=ALL and
roidboot.mid=PG5813000 androidboot.keycaps=qwerty androidboot.dq=FAIL androidboo
t.mode=normal androidboot.serialno=SH191V463715 androidboot.bootloader=1.17.1111
zygote_oneshot=off msm_watchdog.enable=1 console=ttyHSL0 androidboot.hardware=p
yramid no_console_suspend=1
<6>[ 0.335052] pyramid: pyramid_init_mmc
<6>[ 0.907806] Create /proc/emmc OK.
<3>[ 2.389921] mmc0: No card detect facilities available
<6>[ 2.390287] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18
<6>[ 2.390379] mmc0: Platform slot type: MMC
<6>[ 2.390562] mmc0: 8 bit data mode enabled
<6>[ 2.390654] mmc0: 4 bit data mode disabled
<6>[ 2.390745] mmc0: polling status mode disabled
<6>[ 2.390928] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.391020] mmc0: Slot eject status = 0
<6>[ 2.391203] mmc0: Power save feature enable = 1
<6>[ 2.391294] mmc0: DM non-cached buffer at ff007000, dma_addr 0x5751b000
<6>[ 2.391386] mmc0: DM cmd busaddr 0x5751b000, cmdptr busaddr 0x5751b300
<6>[ 2.391966] mmc1: Qualcomm MSM SDCC at 0x0000000012180000 irq 134,654 dma
20
<6>[ 2.392149] mmc1: Platform slot type: SD
<6>[ 2.392240] mmc1: 8 bit data mode disabled
<6>[ 2.392332] mmc1: 4 bit data mode enabled
<6>[ 2.392515] mmc1: polling status mode disabled
<6>[ 2.392607] mmc1: MMC clock 144000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.392790] mmc1: Slot eject status = 0
<6>[ 2.392881] mmc1: Power save feature enable = 1
<6>[ 2.392973] mmc1: DM non-cached buffer at ff008000, dma_addr 0x5751c000
<6>[ 2.393156] mmc1: DM cmd busaddr 0x5751c000, cmdptr busaddr 0x5751c300
<6>[ 2.393644] mmc2: Qualcomm MSM SDCC at 0x00000000121c0000 irq 133,0 dma 21
<6>[ 2.393736] mmc2: Platform slot type: N/A
<6>[ 2.393919] mmc2: 8 bit data mode disabled
<6>[ 2.394010] mmc2: 4 bit data mode enabled
<6>[ 2.394102] mmc2: polling status mode disabled
<6>[ 2.394285] mmc2: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.394377] mmc2: Slot eject status = 1
<6>[ 2.394468] mmc2: Power save feature enable = 1
<6>[ 2.394651] mmc2: DM non-cached buffer at ff009000, dma_addr 0x5751d000
<6>[ 2.394743] mmc2: DM cmd busaddr 0x5751d000, cmdptr busaddr 0x5751d300
<6>[ 2.513761] mmc0: new high speed MMC card at address 0001
<6>[ 2.526975] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
<6>[ 2.527555] mmcblk0: p1 p2 p3 p4 < p5 p6
<6>[ 2.568296] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly file
system
<6>[ 2.568662] EXT4-fs (mmcblk0p22): write access will be enabled during reco
very
<4>[ 2.666654] mmc1: high speed mode max_dtr = 50000000
<4>[ 2.667081] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 2.667264] mmc1: new high speed SD card at address 1234
<6>[ 2.667753] mmcblk1: mmc1:1234 SA02G 1.83 GiB
<6>[ 2.668149] mmcblk1: p1
<6>[ 2.697813] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.705625] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mod
e. Opts: (null)
<7>[ 3.291562] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22945
<7>[ 3.292050] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22946
<6>[ 3.292416] EXT4-fs (mmcblk0p23): 2 orphan inodes deleted
<6>[ 3.292691] EXT4-fs (mmcblk0p23): recovery complete
<6>[ 3.334836] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.389493] EXT4-fs (mmcblk0p24): recovery complete
<6>[ 3.397031] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.516964] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 3.521115] EXT4-fs (mmcblk0p27): mounted filesystem with writeback data m
ode. Opts: nodelalloc
<6>[ 20.862468] mmc2: Slot status change detected (0 -> 1)
<7>[ 20.915202] mmc2: queuing CIS tuple 0x91 length 3
<6>[ 20.915446] mmc2: new high speed SDIO card at address 0001
Code:
logcat | grep mmc
I've left it running for a few mins but nothings showing up.

Its still not showing anything, but I'm attaching a logcat on stock gb upto the point it restarted.