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 decided to make a thread for kaos that gives a more complete set of incomplete/broken things so he doesn't half to. I will try to keep this up to date as possible and if you see something that has been fixed that i have listed as broken please post and I will correct it. I will try to do as many detailed things as possible for now and as things are fixed I will remove them and if a fix is required to be applied manually will try to include it also. Keep in mind this is an unofficial thread and I am not responsible for anything you do to your phone. Now to the list (PS if this is an inappropriate posting area feel free to move it)
Data: FIXED entirely update to latest build
Wifi: FIXED update to latest build.
Bluetooth: Somewhat working, will pair but won't connect.
Browser: UPDATE: fixed, still crashes on flash and javascript some though according to people in irc.
USB notification: no usb mount notification not sure if USB mass storage will work or not but adb still works so a work around is using the commands adb push and adb pull (google on how to use these commands if you dont know already)
Vibrate notifications: vibrate works on the stock messaging app fine but I can't get it working on go sms. Workaround would be just use the stock notifications.
Quadrant: quadrant doesnt work for me gets stuck at database writes, not a big deal no known fix though
Sensors: FIXED update to latest build
Headphone jack: Headphone jack is now fixed somewhat. Still buggy to a degree some headphones won't work (it seems to only work for headphones that have a mic built in for me but it could be just hit and miss with all headphones).
Haptic feedback: haptic feedback in general doesn't work. No known fix
Camera: Currently not working. No known fix.
Cyanogen Settings has some things that make the phone freeze, DO NOT ENABLE JIT its not working yet.
Recovery: Currently broken for me and some other people. Not sure if its working for others (kaos's works and has been apparently.) JT said it shouldn't be a hard fix for him in the future (likely next release?) Use odin to get back to stock and restore your backup from before you had CM installed if you made one if you want. (report any problems in thread please) UPDATE: Greyone and Kaos informed me that recovery works if you go to recovery mode and select advanced > reboot recovery (thanks!)
Wireless tethering:Works if you use the Wireless tether app! fix found by ae55. Might work with other wireless tether applications but it WILL NOT work with the wireless tether in the settings menu.
USB tethering: Not working for me (try it and post if it works for you, its in settings, wireless and networks) more than likely a 3rd party app like easy tether would fix this as long as your 3g is working
MMS: MMS also does not currently work. A workaround is to simply get the message sent to your email for receiving but it seems that the sending of gmail messages isnt working atm i just did a test message to my number and it is sitting in my outbox. Been there for a good bit so its more than likely not sending it. A 3rd party application could fix this possibly? Update: Message finally went through it took a solid 15-20min though so I wouldn't rely on it myself. Again, 3rd party app would prob be your best bet around this. IT DOES NOTIFY YOU IF YOU RECEIVE AN MMS JUST WONT DOWNLOAD IT!
ADW launcher app drawer: not really a bug just many users have looked for this and cant find it, its pretty simple to fix just longpress on the homescreen and tap custom shortcuts then the adw launcher things then app drawer. Hope this clears some things up.
YOUTUBE: seems as though the youtube application isnt playing videos, I dont have good enough service to test it but I will take everyone in the threads word for it. Other video playback apps seem to be having trouble too.
Pandora: Currently my pandora isnt working, could just be me but i think its a problem with the 3g still.
Thats all that I can find for now that isn't working but its likely I missed something, I more than stress to keep in mind Kaosinate is still a VERY alpha build. Its about a 50-50 split between things working and things not working for now but it is coming along thanks to Kaos' work on it and I invite everyone to follow him on twitter and join IRC for the MOST up to date information about this ROM.
Edit: Nevermind. Haven't checked his tweets (well, his reply tweets). Good write up.
bendbowden said:
From Kaos' thread:
Click to expand...
Click to collapse
Kaos permitted and favored this thread on his twitter. (check it)
wirless tether worked for me on v1
Sound hound doesn't work lol. Can't recognize any song that it could before.. Not a hardware issue but still
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Cannot delete files using root explorer
rm: no such tool
so far i love this rom. here are the few things i have noticed so far, some are probably known already
-unable to setup an exchange 2010 account. I fixed it by loading a new e-mail.apk i found in CM forums.
-Unable to watch videos. sling, vevo, movie trailers.
-Some funky thing happened when i powered the phone off. had to pull battery.
minor things i know, but i wanted to point them out.
I get no service from verizon at all. Roaming symbol then no service. Dunno why. Will try flashing again later when I have easy access to odin
Sent from my sch-i500 using dj05 w/ stupidfast kernel
my slingplayer works.. i get a "There was a problem while playing" error for youtube.
daavy said:
my slingplayer works.. i get a "There was a problem while playing" error for youtube.
Click to expand...
Click to collapse
Same here, YouTube does not work. No big deal.
I just want my GPS
aes55 said:
wirless tether worked for me on v1
Click to expand...
Click to collapse
]\
I would love to know how this is possible when the wifi drivers wont even load... post up some pics or something.
EDIT: Kaos has informed us that the drivers do load its the wifi scanner files that arent working yet.
BartJJ said:
]\
I would love to know how this is possible when the wifi drivers wont even load... post up some pics or something.
Click to expand...
Click to collapse
here you go
EDIT: This is with the stand alone "wireless tether" app
aes55 said:
here you go
Click to expand...
Click to collapse
Interesting I'll update the thread to include such information
2296 in quadrant...
To fix the rm: no such tool prompt;
Threax said:
Thanks this works perfectly. You can even do it in root explorer by navigating to /system/bin/rm and choosing rename from the long press menu and renaming it rm.old. Don't forget to mount rw at the top.
Click to expand...
Click to collapse
Sling started working after reboot but I found a few others.
Pandora and Sirius wont stream
Speakerphone no workie
Sent from my SCH-I500 using XDA App
The latest Swype beta works wonderfully in Kaosinate v2.
There is an extra step you have to perform to get it working.
Download and install the swype installer from your beta.swype.com page. Install swype. It will force close when trying to configure swype after the install or generate a license.
Delete the libSwype.co from system/lib/. Then reinstall swype and voila! You will have a fully working, fully up to date, swype keyboard.
--I'll post this in the kaosinate thread too to make sure everyone knows it works. I was dying w/o it.
Edit: just realized someone already posted this in the kaosinate thread so i'll just leave it at this post.
Anyone else still getting the skipping in audio with this? Damn annoying..
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Audio only skips when you change the volume or something of that sort for me, not a real big deal.
Does it a ton during playback for me
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Neuman.Tim said:
Anyone else still getting the skipping in audio with this? Damn annoying..
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Click to expand...
Click to collapse
My notification sounds do this if the screen is off. Play briefly then stop, soon as I wake the phone it continues to play
Gingerbread Notification Icons(MetaMorph including Market, Gmail, and TWiz Email notifications.)
PLEASE READ:
This is just a little MetaMorph I threw together to change the notification icons of your favorite Vibrant ROM to the AOSP Gingerbread style icons. I pulled the icons from the Galaxy S and the leaked Gingerbread I9000 ROM. This is currently a BETA release to iron out any problems, and to take suggestions for more icons I may have missed, or icons from other apps I may have forgot about. Feedback is highly appreciated. This should work on all 2.1 through 2.2.1 ROMs, but I've currently only tested it on my current driver, that's where you come in!
NOTE: This may also work on other Galaxy S devices, but please, if you're going to test it, MAKE A NANDROID BACKUP!!! Or at least know how to restore your current framework.)
Disclaimer:
I do my best to thoroughly test and make sure my themes and updates as universal as possible. That being said, not every flash is perfect. Issues with my themes/updates in the past have been rare, and easily recoverable, but that may not always be the case. Just as with any other updates you apply to your device, you're taking a small risk; That risk can grow when negative factors are added, e.g. human error/misjudgment, bad downloads, bad flashes, etc. I make these updates in my spare time, and offer them to anyone interested, however I am not responsible for damaged software, hardware, or any lives that brutally fall apart after flashing my updates. Please make sure you fully understand what you're doing, and the steps to reverse it if necessary, before applying these updates. XDA is a valuable source of information, simple searching/reading threads will often help you find a solution.
Instructions:
MAKE A NANDROID BACKUP if you don't know how to restore your framework if anything goes wrong.
If you don't already have it, install the MetaMorph app by Stericson from the Market.
Download the attached .zip, and place it somewhere you'll remember on your sdcard.
Make sure USB storage is unmounted, and for best results, activate Flight Mode.
Run the MetaMorph app, Start Checks, and Unzip/Extract the .zip you previously placed on your sdcard.
Close the description. You can now install the different sub themes individually if you so chose (it's scrollable) , or you can select Apply all!
If you chose apply all and didn't encounter a forced reboot, it will prompt you to reboot, do so. Otherwise try again if it was unsuccessful, and reboot when it's done.
Deactivate Flight Mode and enjoy!
NOTE: You will have to reapply the sub themes for Market and Gmail every time they update.
Change Log:
BETA 0.1
Market
Gmail
TWiz Email
Alarm Clock
Call Muted
Car Mode
GTalk
Disk Full
Error/Warning
Missed Call (I9000)
More (Off-screen Notifications)
SD Card Notifications
Sync
Voice Mail
WiFi In Range (I9000)
Debug
Bluetooth
USB Connected
GPS
No SIM
In Call (I9000)
Call Forward (I9000)
Call On Hold (I9000)
Vibrate
System Secure
Speakerphone (I9000)
Throttled
Couple more, probably unused.
THANKS JDAN! I've only tested Gmail and Market notifications, but its working great!
The Market icons seem to have reverted back somehow. Ill try to apply it again and see how long it lasts.
Your Market probably just auto updated. Every time Market and Gmail are updated they will "revert" back to the standard notification icons.
Sent from my SGH-T959 using Tapatalk
nicely done, gonna try this out in a few
Hmmm didn't work. I'll mess with it some more.
Sent from my SGH-T959 using Tapatalk
birgertime said:
Hmmm didn't work. I'll mess with it some more.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Metamorph is rarely successful for me on the first attempt when modifying framework-res. It usually takes me at least two attempts, sometimes with it force rebooting on me. Did Gmail, Email, and Market work for you at least?
On a side note, I might hit you up on Gtalk later with a couple questions.
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
1) Is honeycomb available for use, or are the available honeycombs not complete versions?
2) The important question: sometimes I mistakenly press the "+" volume button, and if it is the last tick or the one before it, the sound becomes extremely high that I'm afraid if this happened a lot my hearing will be really damaged. So, is there a way to re "tune" how much the volume goes up, or to limit the sound to some limit?
3) What should I do to get android apps to work on my NC? If I have to root it, what method should I follow?
4) Should I update from 1.01 to 1.1?
wajed said:
1) Is honeycomb available for use, or are the available honeycombs not complete versions?
2) The important question: sometimes I mistakenly press the "+" volume button, and if it is the last tick or the one before it, the sound becomes extremely high that I'm afraid if this happened a lot my hearing will be really damaged. So, is there a way to re "tune" how much the volume goes up, or to limit the sound to some limit?
3) What should I do to get android apps to work on my NC? If I have to root it, what method should I follow?
4) Should I update from 1.01 to 1.1?
Click to expand...
Click to collapse
You will need to root to use apps. I use CM7 from emmc everything works great for me and if you need or want to go back to stock there are easy ways to do that. Just make sure you read install directions and follow them exactly.
wajed said:
1) Is honeycomb available for use, or are the available honeycombs not complete versions?
2) The important question: sometimes I mistakenly press the "+" volume button, and if it is the last tick or the one before it, the sound becomes extremely high that I'm afraid if this happened a lot my hearing will be really damaged. So, is there a way to re "tune" how much the volume goes up, or to limit the sound to some limit?
3) What should I do to get android apps to work on my NC? If I have to root it, what method should I follow?
4) Should I update from 1.01 to 1.1?
Click to expand...
Click to collapse
1: Honeycomb is not ASOP from Google yet. The version currently running on the nook was ported from the emulator. It seems to work ok from what people are saying but its not full honeycomb.
2: not that i am aware of. I personally remapped those buttons to menu and back, and you could do the same and use an application to control volume.
3: You will need to root your device to unlock the full power.
4: this really depends on what you want to do. 1.1 adds a few bug fixes and the ability to use pinch to zoom in the stock webbrowser on the nook. If you root this using autonooter, you will get to keep the nook app that everyone seems to like, but you will be on eclair, which means no flash. You could wipe the device completely and install Nookie froyo (android 2.2) CM7 (android 2.3) or the honeycomb build mentioned above (android 3.0) Personally i really like what they have done with cm7 and they are constantly updating it. but really its your call. read the other forums on the exact steps to do any of this, its all well documented there.
wajed said:
1) snip sometimes I mistakenly press the "+" volume button, and if it is the last tick or the one before it, the sound becomes extremely high that I'm afraid if this happened a lot my hearing will be really damaged. So, is there a way to re "tune" how much the volume goes up, or to limit the sound to some limit?
snip
Click to expand...
Click to collapse
I wish I had this problem! Are you using extremely efficient headphones? I can't get my NC to output audio at any level I would call loud!
My current solution is an external powered speaker & "Mymusicon" with the sub knob turned all the way up.
Cheers,
kev
bugeyed1 said:
I wish I had this problem! Are you using extremely efficient headphones? I can't get my NC to output audio at any level I would call loud!
My current solution is an external powered speaker & "Mymusicon" with the sub knob turned all the way up.
Cheers,
kev
Click to expand...
Click to collapse
use the overclocked kernel for a very nice volume increase (even if you don't overclock.)
Also the DSP manager app has a bass boost and EQ that can crank out volume if need be.
@Rick_V
@john10101
@chisleu
Thank you
@bugeyed1
I have hearing loss in both ears (one more than the other,) and tho, as you can see, it is really too loud for me at the first tick or the one before it. They are called Brainwavz M1, I got them for 30-40 dollars.