Hey guys,
It is hard to explain the problem. The ROM is working perfect and fulfills all my needs. However every once in a while the tablet goes dead. completely dead without any aparent reason. Only way to get it back to life is to open it up, Unplug the battery and it boots up just fine. works for a while may be 15 days or 5 hours I never know.
On an average I have opend my tablet for more than 10 times in last 3 months. Other than that it works just fine.
Any idea, what's causing this problem?
I had the same type problem with these crashes. Mine would come back by opening the back and pressing the reset button. The problem was there with all the 4.1.x ROMs. I suspect it is the kernel.
I finally got annoyed enough to go back to my trusted Frankentab Froyo ROM.
Sent from my FrankenTAB using Tapatalk 2
jhermit said:
I had the same type problem with these crashes. Mine would come back by opening the back and pressing the reset button. The problem was there with all the 4.1.x ROMs. I suspect it is the kernel.
I finally got annoyed enough to go back to my trusted Frankentab Froyo ROM.
Sent from my FrankenTAB using Tapatalk 2
Click to expand...
Click to collapse
Doesn't matter which rom I run, even stock, I get the occasional shut down of the blue.
Though I must say outside of the lack of flash Smooth runs very nice and only seems to shut down when I'm playing Pocket Empires (which isn't coded that great to begin with and crashes on my EVO as well) or just letting it idle. It has happened to me 3 total times since the original install 3 weeks back but not once since flashing the 2 updates to 4.1.2 with boot.img and audio fix a few days back.
I love using the dock and pumping out NES and SNES roms, HBO GO or avi files to the tv. Some people say that HBO GO doesn't work on theirs, might work for me because I'm using Dizzy's IMEI hack (also worked on black jb w/ the IMEI hack). Meh, beats me.
Thanks for the replies guys. I have not updated the ROM in a while. Might look into it. The instructions for the update is kind of confusing.
Well, So I am not the only one. I have noticed my tablet goes dead specially when a media is playing and I hook up speaker system via 3.5mm audia jack. perhaps plugging in and out that jack messes up the voltage discharge? I too believe its a kernel problem Athough my level of experty is no were near to comment such
Over all, when the smoothBean works, I just love it. and opening the tablet disconnecting batter now take me less than 7 minutes , lol.
theteju said:
Thanks for the replies guys. I have not updated the ROM in a while. Might look into it. The instructions for the update is kind of confusing.
Well, So I am not the only one. I have noticed my tablet goes dead specially when a media is playing and I hook up speaker system via 3.5mm audia jack. perhaps plugging in and out that jack messes up the voltage discharge? I too believe its a kernel problem Athough my level of experty is no were near to comment such
Over all, when the smoothBean works, I just love it. and opening the tablet disconnecting batter now take me less than 7 minutes , lol.
Click to expand...
Click to collapse
I liked black jb pretty well, started there, and tried smooth. Liking smooth best.
I haven't crashed plugging in speakers because I run through the dock via hdmi.
I have however lost volume when I was using my headphones then unplugged them while avi file was playing (happened twice out of 30 or so many times, in mx player).
I'm using mx player w/ hardware decoding enabled, if I might ask what app are you running when it crashes?
And...
I've bounced around enough roms where I'm used to locking up at the 3 birds screen on initial install (and a press of the reset button fixes it 90% of the time), so I just broke out the dremmel and a tape measure, put in a hole small enough for a safety pin directly over my reset in the back and ground in DRH (while the panel was off, I'm crazy not stupid! lol, got tired of prying off the back).
---------- Post added at 10:30 PM ---------- Previous post was at 09:59 PM ----------
Trust me, the updates are cake, nothing to worry about.
I use DRH's clockwork 5.5.0.4. and 4.1.2 smooth inverted
Download to pc (boot.img, audio fix), transfer to microsdhc card.
boot into clockwork
first page select: install zip from sdcard
second page select: choose zip from external sdcard
run both, order shouldn't matter
reboot, done!
theteju said:
On an average I have opend my tablet for more than 10 times in last 3 months. Other than that it works just fine.
Any idea, what's causing this problem?
Click to expand...
Click to collapse
If you press the reset button instead of unplugging the battery, then on the next boot after the crash, the /proc/last_kmsg file should hold the messages from the kernel--if it was the kernel that crashed (most likely here).
Post the contents of /proc/last_kmsg after a crash.
Hi Rajeevvp,
Sure, I will do it on next crash. luckily, its been working good since last 4 days with crossed fingers lol.
Okey it happend again, Dec 30th 2012 at 3:00pm.
This time, I reset it instead of disconnecting the battery. There is no such file as /proc/last_kmsg !
The tablet rebooted just fine.
theteju said:
This time, I reset it instead of disconnecting the battery. There is no such file as /proc/last_kmsg !
Click to expand...
Click to collapse
Post the output of this command (type only the stuff in bold):
Code:
~# [B]zcat /proc/config.gz | fgrep RAM_CONSOLE[/B]
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
# CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
~#
You should see output like the above--esp. ANDROID_RAM_CONSOLE=y.
rajeevvp said:
Post the output of this command (type only the stuff in bold):
Code:
~# [B]zcat /proc/config.gz | fgrep RAM_CONSOLE[/B]
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
# CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
~#
You should see output like the above--esp. ANDROID_RAM_CONSOLE=y.
Click to expand...
Click to collapse
[email protected]:/ $ zcat /proc/config.gz | fgrep RAM_CONSOLE
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION=y
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_DATA_SIZE=128
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_ECC_SIZE=16
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_SYMBOL_SIZE=8
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_POLYNOMIAL=0x11d
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
[email protected]:/ $
theteju said:
[email protected]:/ $ zcat /proc/config.gz | fgrep RAM_CONSOLE
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION=y
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_DATA_SIZE=128
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_ECC_SIZE=16
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_SYMBOL_SIZE=8
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_POLYNOMIAL=0x11d
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
[email protected]:/ $
Click to expand...
Click to collapse
bump, been waiting for reply. I dont know what these output means,, is there something wrong?
If you are busy enjoying new year eve, than fine. i can wait more . By the way Happy new year guys !
Take care. Peace.
Just a little update. after last reset, I did update namely the bootimage update and sound update available on the ROM page. and the tablet is working fine since then. It has been three days without froze, yay..
Only problem I'm experiencing on Smooth is when I've had a headset plugged in and it gets pulled out while playing an audio or video file I lose audio until I reboot.
Doesn't bother me any, when it happens I know the nephew has been sneaking onto the Facebook account he "secretly" has that he's not allowed to have and was watching a video when he yanked out the headphones from the jack, closed the browser and slides the tablet under a piece of furniture then "forgets" where it is when he thinks I'm walking into the room.
Gotta love kids that think they're being sneaky and don't know how to clear history.
tobalaz said:
Only problem I'm experiencing on Smooth is when I've had a headset plugged in and it gets pulled out while playing an audio or video file I lose audio until I reboot.
Doesn't bother me any, when it happens I know the nephew has been sneaking onto the Facebook account he "secretly" has that he's not allowed to have and was watching a video when he yanked out the headphones from the jack, closed the browser and slides the tablet under a piece of furniture then "forgets" where it is when he thinks I'm walking into the room.
Gotta love kids that think they're being sneaky and don't know how to clear history.
Click to expand...
Click to collapse
Should not be discussed on this thread, but just to mention, Privacy feature is lacking on perfectly working ROM. for example, any one can just click gmail app and can access my emails if the tablet is unattended. It would be nice to have those app ask for password everytime we click it. Perhaps I do not make sense, unable to explain my quesiton.
Well, if you don't want people accessing your tablet, in settings, security, you change the lock screen from the default slide to unlock another setting like password, pin or pattern so it just doesn't open to anyone.
And if its just the mail app you want a password lock on (like on Outlook) then you might be able to find a client that will in market. Never looked into it, I get all my mail sent to my phone which has a strict "touch it and I'm pulling one of my swords off the wall and we'll see if you can do it again without hands" policy.
I'm not too concerned with my tablet, I like it a lot, but if someone messes it up I can flash a clean OS back on in 10 minutes. Letting people use it keeps them off of my gaming PC and my Skyrim game saves.
Sent from my sMoothTab using xda app-developers app
theteju said:
[email protected]:/ $ zcat /proc/config.gz | fgrep RAM_CONSOLE
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION=y
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_DATA_SIZE=128
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_ECC_SIZE=16
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_SYMBOL_SIZE=8
CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION_POLYNOMIAL=0x11d
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
[email protected]:/ $
Click to expand...
Click to collapse
OK, so we've eliminated the obvious. RAM console support is built into this kernel. Next, we do some tests:
Baseline tests:
1. Reboot the tablet, then run a dmesg command like this:
Code:
$ [B]dmesg >/mnt/sdcard/dmesg1.txt[/B]
2. Reboot the tablet again and run a second dmesg command changing the output filename to dmesg2.txt. Check if /proc/last_kmsg exists. If it does, then copy it to /mnt/sdcard.
Reset switch tests:
3. Reboot tablet. Run a 3rd dmesg command with output in dmesg3.txt.
4. Reboot the tablet by pressing the reset switch. After the tablet boots, run a 4th dmesg command with output in dmesg4.txt. Check if /proc/last_kmsg exists. If it does, then copy it to /mnt/sdcard as a different filename.
Post all 6 files here.
Hi Rajeevvp,
Thank you for your reply. Reason I have not replied is because, after the running two update files my Gtab is running fine now. It has been more than 7 days now without any hiccup. Most importantly the ROM's developer himself comment in some post that the audio update has more than just audio and I do not know what it is but it certainly solved the problem for now.
But your reply certainly will help to troubleshoot down the road. So thanks again.
Peace.
theteju said:
Most importantly the ROM's developer himself comment in some post that the audio update has more than just audio and I do not know what it is but it certainly solved the problem for now.
Click to expand...
Click to collapse
Most likely the problem has gone underground rather than been fixed by those updates--but, no matter: enjoy your tablet.
theteju said:
Okey it happend again, Dec 30th 2012 at 3:00pm.
This time, I reset it instead of disconnecting the battery. There is no such file as /proc/last_kmsg !
The tablet rebooted just fine.
Click to expand...
Click to collapse
Here is what many of us have done for needing to reset. Take the back off the tablet, take some measurements, drill a hole thru the plastic above the reset button. This way you can put a paperclip in the back and reset without wearing out the little tabs that hold the back on. They do break sometimes no matter how careful you are. They just are not made for repetitve opening of the back. Also it saves wear breaking the batter cable. HTH
If you are flashing ROMs the reset hole in the back is a requirement.
Sent from my Malata SMBA1002 using Tapatalk HD
Related
I don't know why no one else has done this yet since it's a problem that affects every nexus one music lover that has a car dock. This file will fix it so that the volume level remains at max when the phone is inserted into the car dock.
I commented out the code that Google added in Froyo that cuts the volume level by -10dB when the headphone output is used at the same time as bluetooth (car dock).
This library was compiled using the Cyanogen 6.0 source, so I can't guarantee that it will work with any of the nightly releases of CM6. I have only tested it with the finial release of CM 6.0.
Requirements:
* Android SDK
* Nexus One
1. Download the libaudiopolicy.so file from http://www.mediafire.com/?nocgpiypp10jcpt and place it in the <path to sdk>/tools/ folder.
2. Open a comand prompt/console and navigate to the <path to sdk>/tools/ folder.
3. Type in the following:
adb push libaudiopolicy.so /sdcard/libaudiopolicy-new.so (copy fixed library to sdcard)
adb shell (login to the shell of your phone)
su (enable super user mode)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (Remount /system to allow writing)
cp /system/lib/libaudiopolicy.so /sdcard/libaudiopolicy-bak.so (backup old library file)
cp /sdcard/libaudiopolicy-new.so /system/lib/libaudiopolicy.so (replace current library with fix one)
chmod 644 /system/lib/libaudiopolicy.so (set the correct permissions on the new file)
exit (exit superuser mode)
exit (exit shell)
4. Restart the phone.
Recovery:
If for some reason your phone doesn't make it past the first animated X graphic, don't worry it's not bricked. You need to restore back to using the old library by doing the following. I'm going by memory on this so I might be a little off on the details.
1. Pull the battery to power off the phone.
2. Boot into recovery. (If I remember right, hold the trackball and press power.)
3. Enter the shell (it's somewhere in the menu)
4. Type in the following:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
mount /sdcard
cp /sdcard/libaudiopolicy-bak.so /system/lib/libaudiopolicy.so
chmod 644 /system/lib/libaudiopolicy.so
exit
5 . Reboot the phone.
For those of you wonder what I did, here is a rough description:
1. I grabbed the source for Cyanogenmod 6.0.
2. Commented out lines in hardware/msm7k/libaudio-qsd8k/AudioPolicyManager.cpp.
3. Compiled the module by doing a "make modules libaudiopolicy".
New version compiled from the Nov 23rd source. Should work on CM 6 nightlies from Nov 13th forward.
http://www.mediafire.com/?cfht17py4hvat42
is it always going to be at max or can we adjust it?
Instead of commenting out the lines, would it work if you simply changed "-10dB" to "-0dB"?
Going to look for replies of people trying this. I haven't rooted yet, but if this works, I will.
I haven't had time to look too far into it, but it looks like the volume gets reset to max and it's reduced under certain conditions. All I did was remove the -10dB cut for the specific condition that happens when playing music from the headphone output in the car dock.
There must be a good reason why Google is overriding the existing media volume level. Changing it so that the volume controls function would probably break bluetooth headset compatibility. I was thinking about adding a drop down list in the car dock settings to allow different volume reductions, but that requires modifying a lot of files which would break compatibility with CM6 and it's spawn. Then I would have to start rolling my own rom. Right now I'm focused on leaving town and going where there is no cel reception. I posted this to help those that had switched back to 2.1 just to use the car dock with their car audio.
The actually value used is 0.316 for -10db. In a previous version of the file they were using a value of 0.400 for -8db. I didn't have time to figure out what scale these values relate to in order to find a 0dB.
piaxVirus said:
I haven't had time to look too far into it, but it looks like the volume gets reset to max and it's reduced under certain conditions. All I did was remove the -10dB cut for the specific condition that happens when playing music from the headphone output in the car dock.
There must be a good reason why Google is overriding the existing media volume level. Changing it so that the volume controls function would probably break bluetooth headset compatibility. I was thinking about adding a drop down list in the car dock settings to allow different volume reductions, but that requires modifying a lot of files which would break compatibility with CM6 and it's spawn. Then I would have to start rolling my own rom. Right now I'm focused on leaving town and going where there is no cel reception. I posted this to help those that had switched back to 2.1 just to use the car dock with their car audio.
Click to expand...
Click to collapse
I've actually bought the BluBridge just so I can use the Car Dock with audio. Going back to 2.1 is unacceptable for me.
What do you mean by breaking volume control functions? The volume controls on my Car Dock have never worked for me. What situation are they supposed to work?
Since i only keep my volume at max when playing through the car dock, I never bothered trying to use my car dock volume controls with 2.1. I think using software to change the media volume still worked in 2.1, but that changed with 2.2. I suspect google had planned on having working car dock volume buttons (why else would you add them), but ran into issues keeping things compatible with other car docks, bt car stereos, and bt headsets.
Sent from my Nexus One using XDA App
Fantastic.
I've loaded on a Stock FRF91 and reboot was successful. When I get off of work at 5PM, i'll be able to test the functionality.
ibegary said:
Fantastic.
I've loaded on a Stock FRF91 and reboot was successful. When I get off of work at 5PM, i'll be able to test the functionality.
Click to expand...
Click to collapse
How did you modify system files w/o root?
I just rooted my phone and flashed CM6RC2 and made it to Home. Going to test after work ends as well.
Seems to work fine on my way home from work. Thanks man.
Sent from my Nexus One using XDA App
Works fine on the Evo running Fresh Rom 3.3.0.1 as well just btw thanks!
Finally someone fixed this! Glad I'm not the only one who noticed. Maybe now I wont have to pit a piece of paper on the second pin so it wont activate carmode. Is there a flashable version on the roadmap? Hate to redo all that abd everytime I update.
Just curious... Anyone know if this has been rolled into the CM6 nightlies already? If not, I wanna go ahead and use this since I use my car dock a lot, but if it's already in the latest CM6 nightlies, I don't wanna potentially overwrite newer code from TeamDouche
What do ya know, the Evo uses the same Qualcomm msm7k chip. This fix could also work for any other phones using that chip.
I just checked and it looks like there were changes committed for AudioPolicyManager.cpp on Aug 5 and 16th, so I will need to look at compiling a new version for those of you on nighties.
github.com/CyanogenMod/android_hardware_msm7k/commits/froyo/libaudio-qsd8k/AudioPolicyManager.cpp
I won't have time to work on this in the next few days, but some time next week I will be able to. At the same time I'll look at getting this added to CM.
piaxVirus said:
The actually value used is 0.316 for -10db. In a previous version of the file they were using a value of 0.400 for -8db. I didn't have time to figure out what scale these values relate to in order to find a 0dB.
Click to expand...
Click to collapse
How about 1.0?
The attenuation is 20*log(1/scaling) dB. So e.g. scaling==0.400 gives 20*log(2.5), which is approx 8 dB. scaling==1.0 gives 20*log(1) == 0 db attenuation.
Why they're attenuating the volume in this case, I don't know, since I haven't looked into it in any detail. With A2DP you'll usually want to send it the audio data at 0 dB and let the accessory handle the volume control itself. Though when audio effects enter the picture (equalizers, for example) you're pretty much forced to leave a few dB of headroom for the effects.
piaxVirus said:
What do ya know, the Evo uses the same Qualcomm msm7k chip. This fix could also work for any other phones using that chip.
I just checked and it looks like there were changes committed for AudioPolicyManager.cpp on Aug 5 and 16th, so I will need to look at compiling a new version for those of you on nighties.
github.com/CyanogenMod/android_hardware_msm7k/commits/froyo/libaudio-qsd8k/AudioPolicyManager.cpp
I won't have time to work on this in the next few days, but some time next week I will be able to. At the same time I'll look at getting this added to CM.
Click to expand...
Click to collapse
Awesome! That'd be great, thanks!
Waiting for this to be implemented into CM6.0
Saphroxx said:
Waiting for this to be implemented into CM6.0
Click to expand...
Click to collapse
Yeah. But we'll still have the same busted car home with the retarded 'exit' button and the new media framework... Grrrrrr.
Sent from my Nexus One using XDA App
ianken said:
Yeah. But we'll still have the same busted car home with the retarded 'exit' button and the new media framework... Grrrrrr.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What's wrong with the 'exit'? thats my most use button.
New Car Home App
ianken said:
Yeah. But we'll still have the same busted car home with the retarded 'exit' button and the new media framework... Grrrrrr.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah... I know it doesn't fix all of that but the new car home app is definitely an improvement over the stock one. You can finally add shortcuts to third party apps (and I suppose you could remove the Exit button if you really wanted to ) as well as set the car home to launch when the phone is connected to any bluetooth device (although I don't think you can tell it to not launch the car home app when inserted into the car dock :\). Check it out if you haven't already. It's supposed to be available in the market, but I wasn't able to find it when I tried Friday (apparently it was improperly signed). If you can't find it there, I put a copy up on MediaFire though.
CarHomeGoogle-2.2.1.apk: http://www.mediafire.com/?31b3q1f5xibbg0j
MD5: 83f6d27105abd4da8bb0721d118fa8fa
Cheers.
Hi,
before you chop my head off, please listen
I did a lot of (google and xda) searching and i indeed found some useless discussions in Q&A section a.k.a. "what is that" "can i delete that" yada yada yada... . I know what it is, but i wanna disable it. And in Q&A obviously not that many capable ppl/cooks take a look. Thats the reason why i post here...
As this is not rom-related (happens with(out) sense roms on 2.2 and 2.3), i wonder if it's some default kernel routine, which can be altered. Or maybe just some textual setting in a config file?
As this is kinda annoying, if you use the dhd in a silicon case, where the two buttons are hit very often simultaniously, a solution would be great.
Any ideas?
thx in advance
angelus
what are you talking about? what do you mean happens when pressing vol up + vol down? on my phone nothing happens.
hi,
http://forum.xda-developers.com/showthread.php?t=863885&highlight=bugreport
http://forum.xda-developers.com/showthread.php?t=982694&highlight=bugreport
http://forum.xda-developers.com/showthread.php?t=949570&highlight=bugreport
hitting both buttons the same time, it vibrates, takes some time to generate a 2-4mb bugreport on /sdcard/bugreports , vibrates 2 times again when its finished.
meanwhile the dhd is completly laggy and not to be used, which is annoying when you get it out of your pocket just to type a text or answer a call
also happens if screen is off. i am currently on cm7 nightly #36
greetz
i didn't checked if it creates a bug report but i never had my phone laggy when i pressed that two. just tested it. it even does not vibrate.
never had it on stock neither on my current leedroid 2.2.2 or any prvious leddroid rom.
a user said:
i didn't checked if it creates a bug report but i never had my phone laggy when i pressed that two. just tested it. it even does not vibrate.
never had it on stock neither on my current leedroid 2.2.2 or any prvious leddroid rom.
Click to expand...
Click to collapse
Pressing the two buttons (vol +/-) creates a bug report on Mighty Nutella (CM7).. never noticed this though
Disable debugging mode
Still doing bugreports if usb debug is disabled... already tried that.
If you disable it your phone will probably get laggy due to the buggy init process
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
Flussen said:
If you disable it your phone will probably get laggy due to the buggy init process
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
Click to expand...
Click to collapse
i don't know of cm7 but in the latest stock and also in several custom roms this has been already fixed for long time.
but on custom roms you may hit a different problem without usb debugging: it can happen that you get bootloops after rebooting without usb debugging on.
unfortunately this is going exactly the q&a direction, where i didnt wanna go. check the links in #3, there is everything mentioned you posted so far.
maybe a developer/cook can take a look at it or has an opinion.
thx.
Would be nice to know if this can be disabled. I have the same problem with the gel case putting pressure on both buttons when I pull it out of my pocket. Even worse is when its got both volume buttons pressed and I press Power to wake the screen. Instant reboot.
I know this is by design, but like the OP, I would also like to know if it can be disabled.
hmm, funny... after some more trys i managed to get the same behaviour
but it doesn't happen allways. in my case it is quite difficult to reproduce it, but possible.
Let me just point the OP to Chef Central for this. Obviously this is a Chef/dev question, and it's likely occurring on multiple devices.
Thread will be moved there.
so thats why it always vibrates by itself!
somebody please find a way to disable this! All those bugreports had 1gb of space used!!! obviously deleted now but before I was wondering why i had such a small amount of space..
Yep i can confirm that as well, CM7 latest nightly, it's annoying because you are listening to music it's a in a phone sock, you go to press a button to turn it up, you press both by accident, **** hits the fan.
I have also just come across this issue when my favourite Huawei u8150 custom rom was updated to Kernel v2.2.2 ported from a Huawei u8180.
I have worked out a quick and dirty fix and so far is works without any issues. Check my post below for full details.
http://forum.xda-developers.com/showpost.php?p=15429103&postcount=242
Somewhere, in your BOOT.IMG, there's an ".rc" file with these rows:
Code:
# bugreport is triggered by the KEY_VOLUMEUP and KEY_VOLUMEDOWN keycodes or triggered by projectmenu
service bugreport /system/bin/dumpstate -d -v -o /sdcard/bugreports/bugreport
user root
disabled
oneshot
keycodes 115 114
I simply deleted the last one and bugreport is not annoying LEANdroid's users anymore!
ps. I also modified the description row in this way:
Code:
# bugreport is triggered by projectmenu
hey everyone I'm having a weird problem with my TP. The speakers on this thing work well for a while but, at random times the sounds and music I play comes out with static. If I reset the tab it goes away or sometimes if I even plug my head phones in and out it goes back to normal but not often. I've even done a tablet reset and ran webOS and it still happens from time to time. I've contacted HP and they just keep telling me its software related so I'm stuck. I'm running the latest version of webOS now. Its not rooted or anything either but I'm considering turning on developer mode to see if it will work but I don't know. Any ideas/suggestions. Thanks guys I appreciate you looking into the matter for me.
Do you mean the sound become distorted? Like muffled? Its happening to me also when the screen turns off. But if I turn on screen, its gets good. Also it happens only if its on highest volume?
sent from cm7ed touchpad
I've had both problems listed above. Booting into WebOS then back to Alpha 3 solved it temporarily. I imagine with CM9 ICS being the major focus now, we will have to live with it for now.
I have noticed that when I am on Pandora with classical it does not pop; only my 80's Techno pop makes the speakers squeal. Maybe the TP is making a comment on my music?
franky619 said:
hey everyone I'm having a weird problem with my TP. The speakers on this thing work well for a while but, at random times the sounds and music I play comes out with static. If I reset the tab it goes away or sometimes if I even plug my head phones in and out it goes back to normal but not often. I've even done a tablet reset and ran webOS and it still happens from time to time. I've contacted HP and they just keep telling me its software related so I'm stuck. I'm running the latest version of webOS now. Its not rooted or anything either but I'm considering turning on developer mode to see if it will work but I don't know. Any ideas/suggestions. Thanks guys I appreciate you looking into the matter for me.
Click to expand...
Click to collapse
Install prepare and install sound app that restarts the sound drivers, gets rid of the static temporarily. It is software related since the 3.0.4 update.
benfikaman said:
Install prepare and install sound app that restarts the sound drivers, gets rid of the static temporarily. It is software related since the 3.0.4 update.
Click to expand...
Click to collapse
Yes I meant distorted and it also happens when I use either Pandora or play videos on YouTube. Where can I find that benfikaman?
This app is called PulseAudio Restarter (covered here)
You could also do it manually with xterm :
Code:
pulseaudio --kill
I don't remember if you have to type pulseaudio --start after, but anyway the app does it so you won't need these commands.
I guess then I am going to have to unlock my tab and install preware to get that app first. Thanks guys I'll post my results soon. Oh if I run preware will that void the tablets warranty or something? I'm sure ppl have asked this before but I'm not sure how this works. Thanks guys!
franky619 said:
Oh if I run preware will that void the tablets warranty or something?
Click to expand...
Click to collapse
Preware is featured in the official HP catalog, and I've haven't seen any warning about warranty on the webOsInternals Preware page.
If you really need to use your warranty, you'll be able to restore your TP at its original state with webOsDoctor.
You'll see, it's easy to install preware
EDIT : some more infos here, didn't found official link about it.
preware and patches won't void the warrenty. An overclocked kernal could, if applicable
Click to expand...
Click to collapse
benfikaman said:
Install prepare and install sound app that restarts the sound drivers, gets rid of the static temporarily. It is software related since the 3.0.4 update.
Click to expand...
Click to collapse
I ran into the same issue this morning with a bad static sound. I ran the pulseaudio restarter app and that did not fix the issue. I also have had times when no audio at all and the pulseaudio app fixed that. A full reboot fixes the static issues but I agree that it is annoying. I haven't moved into Android yet and I'm running an up to date Touchpad.
So far so good for me. Im hoping it works. I have another question-if any of you guys are in yahoo fantasy leagues or have done it before than you may know what I am talking about. With the touchpad I can't use websites like yahoo fantasy or pizza hut. The browser keeps refreshing itself or like in yahoo's case, each time I click on a little note thats supposed to open as a small window on the site it wont do that either. Is there anything that can fix this?
I tried to run same music apps in webos and they were fine. I have sound problem only in android and only when screen is off. Should I try that pulseaudio app?
It won't help, the screen off sound issue is a CM issue, on the android side, this webOS app can't do anything about it. And I doubt that's the same problem, restarting pulseaudio by adb or console in android won't fix it.
hey guys so here's what's up....the speakers worked fine for a few days after running pulse audio but now its back to the same thing. Any other suggestions? Thanks guys!
So have Asus really screwed this up. I could do with your help by testing this.
While docked, pick up a widget that's resizable.
Move it around the screen and then let go so you can resize it.
Don't resize it but let the tablet go to sleep.
As usual though, my video will paint better words.
vgjfelix said:
So have Asus really screwed this up. I could do with your help by testing this.
While docked, pick up a widget that's resizable.
Move it around the screen and then let go so you can resize it.
Don't resize it but let the tablet go to sleep.
As usual though, my video will paint better words.
Click to expand...
Click to collapse
do you have an sd card in the dock?
Wasn't able to reproduce this no matter how i tried :/
whycali said:
do you have an sd card in the dock?
Click to expand...
Click to collapse
I do yes. Is this the sleep of death thing I read about but never experienced until now by chance?
vgjfelix said:
I do yes. Is this the sleep of death thing I read about but never experienced until now by chance?
Click to expand...
Click to collapse
maybe. try it without sd!
Tapatalked!
vgjfelix said:
So have Asus really screwed this up. I could do with your help by testing this.
While docked, pick up a widget that's resizable.
Move it around the screen and then let go so you can resize it.
Don't resize it but let the tablet go to sleep.
As usual though, my video will paint better words.
Click to expand...
Click to collapse
Like honestly???
Sent from my SAMSUNG-SGH-I727 using xda premium
I tried 5 times, with SD card in the dock and without. I cant replicate the bug.
I must add, I did a factory reset loaded Asus stock .28, root, ota via the dlpkgfile so my setup is a fresh install so to speak.
I'm rooted JB stock and locked.
if that makes a diffrence
Hey folks,
I just found a real issue. Instead of opening a new thread, I think it fits quite well here.
So here is the thing:
I connected a old and small microsoft USB mouse (USB ID 045e:00a4 Microsoft Corp.) to the dock to use it together with splashtop. Now if I just wait until the tablet goes to sleep it will suddenly reboot. This is - at least for me - easy to reproduce.
tobi01001 said:
Hey folks,
I just found a real issue. Instead of opening a new thread, I think it fits quite well here.
So here is the thing:
I connected a old and small microsoft USB mouse (USB ID 045e:00a4 Microsoft Corp.) to the dock to use it together with splashtop. Now if I just wait until the tablet goes to sleep it will suddenly reboot. This is - at least for me - easy to reproduce.
Click to expand...
Click to collapse
At last, someone else who has replicated it. And I share your mouse reboot in this video:
Okay, I've now got this issue. Had it reboot several times unintentionally and that was while doing work
Just leave any USB device plugged in. Leave it till it goes to sleep... Restarts. What a crazy bug?! I was just viewing some PDF's, and then left my tablet for a minute, next thing you know, it's restarted itself.
vgjfelix said:
At last, someone else who has replicated it. And I share your mouse reboot in this video:
Click to expand...
Click to collapse
vgjfelix, I got the same thing with the mouse too. Also can you test to see if your BACKSPACE key works? After the update, with the stock browser, the backspace key doesn't work when you do a web search like in yahoo.com or google.com
Thanks
This is a nasty jelly bean bug, but hopefully because of your well documented video, Asus can get it fixed on the next update.
Sent from my Galaxy Nexus using xda premium
my TP just restarts whenever i play games. that's just great
Well I am begining to feel left out. I cannot get my prime to force close. I have even tried having the weather widget in its move box and an sd card in the slot as well as a usb mouse plugged in and it just goes to sleep just as it should and a nudge on the mouse a bit later and it wakes up just as it should. This prime has never forced closed since JB. Stock machine. Happy with it.
I've had this issue but without resizing widgets or anything.. I just let the tablet alone for a bit... it goes to sleep then either reboots by itself or just shuts down.. and then I have to long press the power button to turn it on again (it takes much longer to turn on after this happens)
Yep, me too. Thought it was a game or something, but it just randomly reboots just after going to sleep. Tried wiping and factory reset. No joy.
Anyone any ideas?
Thanks
YellowShed
Thanks to all who posted in this thread (clicked a few key 'Thanks' buttons). I was going crazy with the reboots 5-10x a day after JB update.
Saw USB/SD comments so I removed my SD card and my usb thumbdrive from the dock late last week and it's been up and stable for about 5 days with no reboots.
My reboots seemed to coincide with either dimming to sleep or waking up (music playback when closed was the clue that some were apparently on wake)
As the title states. Those using the newest roms do your phones ring as should? Been using and always going back to Baked 6 because every newer rom I try the phone frequently does not ring. To name a few, I tried Hellybean, Slim, Carbon, Baked 8. I have tried every solution that I can find in these forums. I depend on my phone for work so it has to be reliable. Does it not bother others that the phone does not ring as should or does yours work?
I'm on Helly Bean and it rings every time... although I don't get phone calls very often at all, so maybe if I did it would miss a few. This is a common issue unfortunately and I've yet to hear of an easy solution.
Not Ringing Either
My phone doesn't ring either. Hasn't through out the whole time I've been using HellyBean. I've been searching the forums and thus far haven't found a fix. If anybody has the fix thread can you post it here, thank you. Looks like I'll have to look into another rom as suggested in the start post.
it;s probably a ROM that doesn;t get any attention but i have been using JellyBro and the ringing and notifications work fine.
Look here for a fix
http://forum.xda-developers.com/showthread.php?p=42185823
louiehummv said:
Ugh, not again. Well... for what its worth, I found a way to stop losing em.
First, a little background... I discovered that the "media store" app will index ur phone's media after every reboot (as expected), but hangs before committing its findings from the temporary "wal" file to the "internal.db" database (where all ur media locations are stored). Then, when attempting to access the database while configuring ur ringtones/sounds, the media store app craps out and drops it findings altogether. Basically, the wal file disappears and the database file size decreases. So, all we have to do is force the wall file to commit before the media store drops it. Afterwards, the media store app doesn't appear to have a problem maintaining the database... even after rebooting. Definitely a bug with the app; see for urself by observing internal.db in /data/data/com.android.providers.media/databases.
Now, the workaround (ull hafta reassign all ur ringtones/sounds after this... not like they worked anyway)...
1 - Delete the contents of the folder /data/data/com.android.providers.media/databases.
2 - Reboot and wait ~5 min after startup to let the media store reindex all ur media. DO NOT configure any app's ringtones/sounds just yet.
3 - In terminal, enter the following commands. You should see "x | y | z" after the checkpoint command... where x is 0 (database is ok), y is the number of modified pages, and z is the number of pages successfully committed to the database. y and z should be equal and much greater than 0. If the result is not as described, the database is probably screwed up and u were too late. Go back to step 1 and repeat.
$ su
# cd /data/data/com.android.providers.media/databases
# sqlite3 internal.db
> pragma wal_checkpoint(FULL);
> .exit
# exit
$ exit
4 - Trust the workaround and start configuring ur ringtones/sounds now... or reboot again and ensure the media store database stays fixed. I recommend the latter.
5 - 3 sir!
Sent from my SCH-I535 using my wit and brilliance
Click to expand...
Click to collapse
hhp_211 said:
Look here for a fix
Click to expand...
Click to collapse
Can't find "/data/data/com.android.providers.media/databases"
Edit: Found
Hello,
I also suffered this issue, i think the rom you flashed was to blame.
This issue has been long discussed in our Chinese fascinate forum.
I strongly recommend you flash the lastest cm10.
自由自我
hhp_211 said:
Look here for a fix
http://forum.xda-developers.com/showthread.php?p=42185823
Click to expand...
Click to collapse
Tried the workaround. Ringtones lasted longer, but stopped after a couple hours. Tried on latest Helly. Curious which roms it's working for others on.
dukeoid said:
Tried the workaround. Ringtones lasted longer, but stopped after a couple hours. Tried on latest Helly. Curious which roms it's working for others on.
Click to expand...
Click to collapse
well i'm currently on Slim 04/09 build -
previous Slim 3/17;; ParanoidAndroid March Builds;; Baked Bean, 6/7/8;;; HellyBean;;; AOKP PUB;;;
that gets me back all the way to the beginning of the year
I have had working ringtones on ALL of these as my daily use phone...
on my test phone I cant test ringtones cause [ its not activated] but notification tones for things like hangouts, twitter, gmail, etc have ALL worked without fail on every build I've loaded,,, [ which is virtually ""ALL"" the others at one point or another]
but kind of like that work around is saying I always wait after a clean/data wipe about 10 minutes [before setting ringtones] while figuring out my other settings, adding apps and what not, usually give at least 1 more reboot and wait again another 10 minutes then set ringtones,,, but I also have my 2 personal use ones [ringtone = pyxis ,,&,, Notification = cyanping] stored in a file on my sd card [a couple ROMs have not had these and I don't really care to use anything else right now] and always making sure to choose media player/server as the default app if I've wiped media storage settings data,,, [that way I can add them back into the appropriate folders if needed]
I did have this issue way back about August/September of last year running on AOKP builds, but I remember odin to stock, then THS 1/2 build then flashing to an older glitched build before the original partition changes or the later partition changes, and probably flashing new aokp,,, wiping data, etc and I got mine fixed...butt... it could have gone back to me waiting out those initial scanning times plus reboots ~ before ~ setting ringtones/data,,,
then again,,, some peoples fascinates have just given them major issues with this and they have rarely seemed to fix the problem,,, so it could be hardware tolerances and those are just really off on some setting somewhere...???
Good Luck
I really dont feel it is a ROM issue...maybe an Android issue, like the voicemail notification prompt problems [because we dont have LTE and that is coded into jb software now, so the fascinate freaks out when it cant find lte settings...]
.
---------- Post added at 05:48 PM ---------- Previous post was at 05:38 PM ----------
you could try ,,, now that it borked on you,,, clearing out the android.providers.media / data , boot into recovery, wipe dalvik and cache partition, and reboot then wait out the time, reboot and again wait out time,,, then set ringtones,,, and try...don't know what else to say...
Thanks for the suggestions. Will try them.