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.
i don't want shutter sound while taking pics
even in silent mode i can hear that sound
any other way to disable it
reducing volume to 0 works for me
another way would be by editing the registry.
kabumm said:
another way would be by editing the registry.
Click to expand...
Click to collapse
? What should I edit?
Find Windows\camerashutter_mirage.wav or shutter.wav and replace the empty .wav
That's the first thing I tried. Searching registry for these strings doesn't yield any results. The files themselves sit in \Windows, but I can't delete or replace them.
Which software did you use?
Why would you want to take pictures with no sutter sound? I remember some one asking this before and was told the shutter sound is to stop people taking picture of people with out them knowing. It made me laugh too but you never know.
I personally want to remove it because it sounds at the wrong time, messing up my pictures of people.
If it worked properly, I'd certainly leave it. Don't know about the others. You can't disable it on the iPhone IIRC, but nobody complains.
Try putting you finger over the speaker as it very easy to mute the sound like this and does not get in the way on the lense, just tried it for you and it kinda work. Its not the best fix but you never know it may help.
I only got my Mozart last week but turning the phone volume to "0" silences the camera...
Turning the volume all the way down works for me as well, but it's an awkward workaround - it doesn't work in the camera application itself, I have to do it beforehand, and it takes too much time.
There is a reg hack available for this.
http://forum.xda-developers.com/showthread.php?t=907971
Hi. I bought the Prime and Keybaord dock and love them! The only thing is that I am not a fan of the stock ICS browser and I am sure that I am not the only one. I wanted to know if there is a way to change the browser that is launched when pressing the internet/browser launch button (the one with a saturn-ish looking planet on it) on the keyboard dock because I haven't heard of anyone able to do it. I have tried disabling the stock browser but that makes the button unable to launch anything. I have my Prime rooted as well. I figured that I start a thread on this issue to see if anyone has been able to do it.
Don't think the browser question has ever been answere but I do think somewhere in these ATP or the OG TF forums, it has been said how to modify the key map files or something. That'd be a starting point, maybe.
Sent from my Transformer Prime TF201 using Tapatalk
What if we replaced the system app with opera? (or browser of choice)
Depends on how it's being launched. I.e. if it's dependant on the class name inside the APK, mv Opera Browser != good enough. Although replacing Browser with a stub that just forwards to another app is probably possible.
Sent from my Transformer Prime TF201 using Tapatalk
This has been brought up before (with the TF101), and there hasn't been any progress made that would enable this functionality.
In the keylayout file, it's key 150 that launches the EXPLORER keycode, but I can't find any documentation that shows what that launches by default (other than the default browser).
Edit: After some more digging, it appears that this functionality resides within the Asus Keyboard IME. Going to see if I can work around this.
Edit2: Success! I was able to take the deodexed Keyboard.apk (thanks Swiftks) and modify the smali to launch com.beansoft.browserplus (ICS Browser+) instead of the built-in ICS browser (com.android.browser). Happy happy joy joy!
Unfortunately this means that the edit would have to be done per-browser. I haven't tried this with Firefox, Chrome, Boat, or Opera, but will look into those tomorrow. For now, if anyone wants to test this (no guarantees, as usual with system app mods) I've attached it to this post. Make sure you backup your stock Keyboard.apk and Keyboard.odex first!
Quick how-to:
1) adb push Keyboard_ICS+.apk /mnt/sdcard/
2) adb to TFP, remount system read-write
3) cd /system/app, cp Keyboard.* /mnt/sdcard/backups (or where ever you want to keep your originals)
4) rm Keyboard.*
5) cp /mnt/sdcard/Keyboard_ICS+.apk ./Keyboard.apk
6) chmod 644 Keyboard.apk
7) reboot
When your TFP comes back up, you should be able to hit the browser button on the dock and it should launch ICS Browser+ (assuming you've got it installed already).
Props to appelflap for making a kick-ass browser, and to Swiftks for deodexing the system files.
EDIT: Attachment removed. Updated thread contains new APK.
Edit: Failed to read you were already going to do this for chrome tomorrow. Best of luck and I look forward to it.
agentdr8 said:
This has been brought up before (with the TF101), and there hasn't been any progress made that would enable this functionality.
In the keylayout file, it's key 150 that launches the EXPLORER keycode, but I can't find any documentation that shows what that launches by default (other than the default browser).
Edit: After some more digging, it appears that this functionality resides within the Asus Keyboard IME. Going to see if I can work around this.
Edit2: Success! I was able to take the deodexed Keyboard.apk (thanks Swiftks) and modify the smali to launch com.beansoft.browserplus (ICS Browser+) instead of the built-in ICS browser (com.android.browser). Happy happy joy joy!
Unfortunately this means that the edit would have to be done per-browser. I haven't tried this with Firefox, Chrome, Boat, or Opera, but will look into those tomorrow. For now, if anyone wants to test this (no guarantees, as usual with system app mods) I've attached it to this post. Make sure you backup your stock Keyboard.apk and Keyboard.odex first!
Quick how-to:
1) adb push Keyboard_ICS+.apk /mnt/sdcard/
2) adb to TFP, remount system read-write
3) cd /system/app, cp Keyboard.* /mnt/sdcard/backups (or where ever you want to keep your originals)
4) rm Keyboard.*
5) cp /mnt/sdcard/Keyboard_ICS+.apk ./Keyboard.apk
6) chmod 644 Keyboard.apk
7) reboot
When your TFP comes back up, you should be able to hit the browser button on the dock and it should launch ICS Browser+ (assuming you've got it installed already).
Props to appelflap for making a kick-ass browser, and to Swiftks for deodexing the system files.
Click to expand...
Click to collapse
Any chance you could hook one up to work with boat browser? I use it now that flash doesn't work in opera. It would be awesome to be able to use the keyboard launch key. Thanks!
Doesn't look like this can be modded to work with browsers that aren't based on the stock ICS browser. The activity for alternate browsers isn't explicitly defined in the AndroidManifest.xml for the Keyboard.apk, so it throws an exception when trying this mod for Chrome, Boat, etc.
So for now, the only way I can foresee overcoming this limitation (because the manifest can't be edited without being re-signed) would be to build a small helper app that extends com.android.browser much like ICS+ browser does, but instead of launching a standard browser view, use it to launch a browser picker or the default browser.
Maybe in my spare time I'll figure out how to do something like that.
agentdr8 said:
Doesn't look like this can be modded to work with browsers that aren't based on the stock ICS browser. The activity for alternate browsers isn't explicitly defined in the AndroidManifest.xml for the Keyboard.apk, so it throws an exception when trying this mod for Chrome, Boat, etc.
So for now, the only way I can foresee overcoming this limitation (because the manifest can't be edited without being re-signed) would be to build a small helper app that extends com.android.browser much like ICS+ browser does, but instead of launching a standard browser view, use it to launch a browser picker or the default browser.
Maybe in my spare time I'll figure out how to do something like that.
Click to expand...
Click to collapse
Hey, thanks for the help man. I look forward to seeing what you come up with!
agentdr8 said:
This has been brought up before (with the TF101), and there hasn't been any progress made that would enable this functionality.
In the keylayout file, it's key 150 that launches the EXPLORER keycode, but I can't find any documentation that shows what that launches by default (other than the default browser).
Edit: After some more digging, it appears that this functionality resides within the Asus Keyboard IME. Going to see if I can work around this.
Edit2: Success! I was able to take the deodexed Keyboard.apk (thanks Swiftks) and modify the smali to launch com.beansoft.browserplus (ICS Browser+) instead of the built-in ICS browser (com.android.browser). Happy happy joy joy!
Unfortunately this means that the edit would have to be done per-browser. I haven't tried this with Firefox, Chrome, Boat, or Opera, but will look into those tomorrow. For now, if anyone wants to test this (no guarantees, as usual with system app mods) I've attached it to this post. Make sure you backup your stock Keyboard.apk and Keyboard.odex first!
Quick how-to:
1) adb push Keyboard_ICS+.apk /mnt/sdcard/
2) adb to TFP, remount system read-write
3) cd /system/app, cp Keyboard.* /mnt/sdcard/backups (or where ever you want to keep your originals)
4) rm Keyboard.*
5) cp /mnt/sdcard/Keyboard_ICS+.apk ./Keyboard.apk
6) chmod 644 Keyboard.apk
7) reboot
When your TFP comes back up, you should be able to hit the browser button on the dock and it should launch ICS Browser+ (assuming you've got it installed already).
Props to appelflap for making a kick-ass browser, and to Swiftks for deodexing the system files.
Click to expand...
Click to collapse
Would I be able to do this via root explorer?
Ronde90 said:
Would I be able to do this via root explorer?
Click to expand...
Click to collapse
Would like to know this as well. Never had much luck with ADB.
hollywould said:
Would like to know this as well. Never had much luck with ADB.
Click to expand...
Click to collapse
I tried it with root explorer and had no luck. I'm going to try it with ADB explorer later today.
You can do it in a terminal emulator without adb, if you su to root and have the files on your device already.
If not rebooting after you should remember to remount /system back the way it was when done.
Sent from my Transformer Prime TF201 using Tapatalk
dont hate me on this.
i've googled 4 hours, read and tried numerous methods but cant find a working method.
previous suggested method for gingerbread does not work, such as
-making a build.prob file in \data\ did not work.
-use root explorer to go \system\media\audio\ui and delete all camera related ogg files
other suggestion includes using "ics camera", app, this sorta works, but i very much prefer to use the stock one.
another suggestion is to use paid app "tasker", to auto set silent mode when camera is running, works, but i hate having an uncessary background process constantly running. :-(
any really working known fix for this?
right now i am using litening rom 2.5 that is ics.
the shutter sound is off by default, the sound that remains is the focusing sound.
please please if anyone have any idea how to shut the camera sound, please share it with everyone here.
PS: ics, not gingerbread method.
seen in galaxy nexus forums, turning down the media volume will mute the camera completely.
but why this not work for s2...sad...
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