THIS IS FOR THE 3.XX GPS ROMS ONLY.
SEE UPDATE BELOW
This will not work with the older 2.XX ROMs, the files are different between the ROMs and using the wrong one may make your phone SILENT.
This file is designed to increase the volume of the phone. It increases the ear piece speaker, speakerphone speaker, and headphone/handsfree speaker levels.
The ear piece and speakerphone speakers start at the factory Sprint level for low, but get louder in greater steps. The loudest was near the edge of distortion when I called my voicemail.
The headphone/handsfree level has been increased by about 15%, no where near as much as the first 2, but its headphones, so I'm not jacking it up that much.
To install....
1. Download audiopara.csv.txt
2. Rename to audiopara.csv (meaning you get rid of the .txt part)
3. Backup audiopara.csv from your Windows directory of your phone.
4. Copy into the Windows directory of your phone, overwriting the original.
5. Soft reset. Yes you need to soft reset.
Disclaimer : I am not responsible if you break your phone or go deaf. This is not a hard thing to do, read the directions twice. Also be careful when using initially as the volume is louder than it was when you got the phone.
Anyone may feel free to use this file in a custom ROM or whatever, jsut put my name in there, if you would.
Thanks to mswlogo for figuring out how to do this in the older ROMs.
Glad I could finally give back to the community that has helped me out so much. Enjoy.
FILE: http://www.scrufdog.com/AudioPara.csv.txt Right Click, Save Target As...
If someone wants to do a mirror thing go for it.
UPDATED
UPDATE: NOW WITH CAB FILE
I've also added the original since people arent backing up.
Here's the new and improved way to install. This zip file has my original .csv file in it AND now comes with a .cab file for easy install, without overwriting and copying and such.
Instructions are the same for the csv file.
Instructions for the cab are fairly simple.
1. Copy cab to phone.
2. Run cab, install to Device.
3. When done, soft reset.
4. Enjoy loudness.
Enjoy.
Let me know if there are problems.
in case anyone was trying to download this early yesterday and such and got a broken link, the server its on has been back up. Dont know what happened, but all is good now.
Thanks.
Hey bro thanks for this new audiopara file. I can finally use the speakerphone with out having to be ashamed of the low volume. .Thanks
What are the downsides of this? there has to be something if they made it that low right? Or not...
1999TL said:
What are the downsides of this? there has to be something if they made it that low right? Or not...
Click to expand...
Click to collapse
the only downside i can think of would be that your speaker will only last 5 years instead of 6, and thats only if you run the things at full blast ALLLLLL day long, and even then, I stopped at what my phone was playing distorted, and distortion is what kills speakers, not just loudness.
This file has been modded and used in the past, and no problems ever arose. It's the first thing I do when I reflash a ROM.
that was easy. I do notice a difference too on this rom. ON the past roms, I diddn't notice much of a difference.
Great Job!
I didn't have the old hack (moderate-fix-low-volume-issues-audiopara.csv_coarse_ear_extended_speaker.txt) installed very long before the 3.16 update came out, but with this new one, it seems louder. With the old hack, I still had to put the volume at max and strain slightly to hear. With this one, I have the volume at the notch below max and is plenty loud. In fact, I can hold the phone away from my ear and still hear fine. Nice work!
Thanks!
Cuddo's man, I did the rom upgrade and had no sound at all. I was running the previous coarse tweaked audiopara and it sure didn't work with the new Rom. I wonder what else does not work. Now if I can just get rid of the one unresolved item under activesync notes I'd be happy.....
check first post for update. You can now install with a cab file to make things easier.
What exactly does this do when compared with No2chem's nueAudio application?
http://www.weienterprises.com/nue/nueaudio.html
lets see...
1. Its one less icon floating around (no big deal for most people I suppose).
2. I've been told its louder than no2chem's loudest setting.
3. no2chem's kets you adjust parts of the file that dont actually do anything, and I found that one of them will crash your phone if you even try to adjust it, WinCE_Sys I think it was.
He does good work. I made this one awhile ago and most that use it like that it is apparently the loudest one out there (while keeping the same low volume setting), and that its a one time thing, with no program to mess with.
anyone here use this on a Verizon phone? If so what ROM are you using. I've been helping someone with a Verizon phone that installed this and lost all sound.
Thanks Scruffdog, I'll OEM the CAB to give people the option of this file or the unmodified audiopara in my kitchen. nueAudio is already a choice but if the settings are just right, how often would one need No2Chem's app?
and here it is:
cool. Thanks.
I removed your audiopara, as with DCD's, it broke the profile in SPB PhoneSuite and caused the odd lock-up. I'm guessing that it's only for WM 6.1 and not the 6.0 build such as the SPrint release.
Thanks...
Works on my VZX6800 with SPB suite installed on the newest DCD rom...
its almost too loud if anything.. For normal listening I have it on the lowest...
Speak Up I Cant Hear You!
Awesome job. finally I got some VOLUME!
Keystone said:
I removed your audiopara, as with DCD's, it broke the profile in SPB PhoneSuite and caused the odd lock-up. I'm guessing that it's only for WM 6.1 and not the 6.0 build such as the SPrint release.
Click to expand...
Click to collapse
that sucks, I was under the impression that it was 'per radio' not 'per OS'.
Send me one for WM6.0 and I'll take a look at it and compare the 2.
Keystone said:
I removed your audiopara, as with DCD's, it broke the profile in SPB PhoneSuite and caused the odd lock-up. I'm guessing that it's only for WM 6.1 and not the 6.0 build such as the SPrint release.
Click to expand...
Click to collapse
I downloaded your kitchen and took out the WM6.0 audiopara.csv. It's the exact same thing as mine, except for the volume bumps I did. All the rest of the settings a the same.
Can you describe the problem you were having a little more maybe? Did my file make things louder before the lock-up, or could you even get far enough to tell?
Related
Hi!
My phone doesn't ring anymore, it won't even vibrate!
It all started when I set PocketMusic as the default player for WMA files. This made the phone stop ringing, and when I checked in settings the ringtone was set to WindowsDefault instead of my usual OldPhone. I tried resetting the ringtone to OldPhone, but when I clicked ok it was automatically reset to WindowsDefault again. This happened for all of the WMA ringtones. They also did not play when you tested them in settings. I removed the association from PocketMusic, which made the ringtones play from the settings screen. But they still don't work when there´s an incoming call. The thing is just quiet.
If anyone has any kind of idea, please help me. The phone is on 4.00.11, I've tried soft resetting but that didn't help. There's probably a registry setting that's messed up, but which one?
Thanx!
/b
Possibly Similar
This sounds slightly similar to a problem I had with Pocket PC 2002 - look for a post named "Cursed by BellDitty". It was a registry key that wasn't written correctly.
Well did ya think to just hard reboot the phone? That will put everything back to original specs.
Just back up any data you need and turn the thing off and back on.
Re: Possibly Similar
dadarkmcse said:
This sounds slightly similar to a problem I had with Pocket PC 2002 - look for a post named "Cursed by BellDitty". It was a registry key that wasn't written correctly.
Click to expand...
Click to collapse
Yeah, I read that thread and fooled around a bit with the reg keys in ringtone0. Didn't help though. The strange thing is that ringpreview is working just fine, but ring is not. Could you post a copy of the keys and values in ring, ringpreview and ringtone0 so I can see what a healthy device should look like?
Thanx!
/b
chocodough said:
Well did ya think to just hard reboot the phone? That will put everything back to original specs.
Just back up any data you need and turn the thing off and back on.
Click to expand...
Click to collapse
I'd prefer to find out what's causing the problem and fix it. If I haven't solved it before the weekend I'll probably do a hard reboot. Don't like all of my installed progs dissappearing though, so I'll probably end up cooking myself a new rom as well to fit my most used applications into rom.
Cheers
/b
RegDump
Here is a reg. dump of my XDA when it ran 2002, I checked the registry of 2003 and it looks the same:
[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]
"Sound"="DefaultRing .wav"
"Script"="apw3r"
"SavedSound"="DefaultRing .wav"
"Category"="Ring"
Hope that helps.
Thanks everyone for your support.
I finally decided to go for the hard-reset, nothing else seemed to help.
/b
i had this same porblem after installing pocketmusic 1.3 bundeld.
It played the mp3 when clicked on them.
O2 plus played them tru pocketmusic, still it didn't work.
When tested at settigns/phone/ play it didn't work.
I removed the assoisition in pocket music(for mp3.wmv) now it works.
CJ
Yes, Betaplayer did the same, as well as an older version of Conduits' Music player.
You must just make sure that these files do not have the default association for wma or wav, they do not play nicely with the Phone Edition somehow.
(But Betaplayer is still the bestest video player for the Pocket PC!!)
THANKYOU THANKYOU!
Have been tearing my hair out over this one and dredding a hard reset.
Hi guys. Been away for a while and now actually bought an xda 2. I have a few problems and hopefully someone can help.
My xda came with rom 1.72.181 with blackberry. Not being bothered about blackberry I downloaded (after a full backup) and installed 1.72.187. I didn't realise that a full restore from my backup would put the software back to 1.72.181, so had to hard reset and reinstall everything again. Both are backed up now so I can swap as and when I feel like it between 181 and 187. Both have a full setup of all my software, but I thought a restore would only put the software back, not the os and rom also, (like with my xda1). Anyone know how to reinstall software without overwriting the rom software version?
Next problem. What is the latest rom available on here (links please if known), and will updating it mean yet another full reinstall of all software.
Also, I have an occasional (too often though) problem where the touch screen stops working and the only way to get it back is to reboot. Anyone know what might be causing this. I can use the buttons and turn it on and off, but the touchscreen does nothing until I reboot. It happens with both roms, but I don't think its hardware related as the soft reset makes everything fine again.
I have removed just about everything from startup including ia caller id and all flashman stuff. I'm not even using it as a phone much because I mainly wanted it as a pda, but I have a payg sim in it for cross network calls (saves on my o2 bill). So mostly, the phone is turned off.
Any help you clever people can give would be much appreciated, (no suggestions involving hammers please). Oh yes, its about 3 weeks old as of this post date so not worn out yet. Lastly, there's no passwords set or any security setting that could be causing it as everything is on default.
Please help a desperate man.
TIA
:?
Your touch screen should work out of the box. If it's not working out of the box, then you may have a hardware conflict issue.
I don't know what do you use for backup, but a full restore usually restores the registry and filesystem.
For a different version ROM, the usual advice is to install your software from scratch again.
If you are handy with the registry, what you can do is:
(a) export the registry of your own ROM, cut & paste the portion that contains the registry settings for your installed software, usually under HKLM\SOFTWARE\...
(b) use your ActiveSync to reinstall the software again in your new ROM
(c) import the HKLM\SOFTWARE\.. registry that you have saved earlier.
If you are handy with OSP WinCAB Mgr, you can create a CAB file for this and makes your restoration easlier.
Have you fitted a scree protector to the phone, this can sometimes cause problems with the touch screen if the protector is too close to or tucked under the edge of the cover, this can be intermittent also.
Re: Help Please
Thanks for the interest.
I have done a full reinstall with both rom versions, so that problem is gone. Just wondered if there was any way to put the software back after a rom upgrade without a full reinstall of everything.
As for the screen problem. Like I said, I don't think it's hardware related as it s all fine after a soft reset. Hardware would usually mean that it still won't work after rebooting. It's like whatever software controlling the touch feature throws a wobbler and locks me out, but the buttons all work as normal when it happens. I'll list the software thats installed and if you're aware of any known conflicts, please tell me in a reply.
Calligrapher, Phatpad, Launcher (today plugin), Tascal regedit, Frequency tuner, SPB Fullscreen keyboard, Pocket Mechanic (1.49), and Tomtom 3.
Any ideas to help this very confused man.
More help please.
I have removed calligrapher and it seems to have stopped locking up. Problem now is what do I do about it.
Anyone know how to cure this. The program is no good if it has problems with 2003, (and I have tried both drivers, default and calligrapher) without success. Now I'm stuck.
Any suggestions.
A very frustrated man.
Calligrapher 7.4, For you're information
I have removed calligrapher 7.4 and installed version 7.2. Guess what, no freezes. I informed phatware support of this and the response was what else do I have installed. They don't seem to accept that the latest version is the cause of the problem. It must be something else. Probably a today plugin????.
I then installed version 7.3. No lockups. Put 7.4 back in, back to square 1 with the locking up. It seems that anything before 7.4 is ok. I have told phatware support of this, but they still don't accept that 7.4 is the problem, instead putting the blame on anything else but version 7.4.
OK, here's my question. Am I losing it, or would it be safe to assume that (seeing as the others work) calligrapher 7.4 has a problem. A simple deduction watson, given the overwhelming evidence. Remember that I also have an xda1 and its the same story on that too.
Sorry phatware, but I'm gonna stay with my other stuff and look at the alternative's to calligrapher until I can try another (later) version that works with my machines.
One sale lost I think. Anyone else having similar problems.
Just got an HD2, and after looking for a good task manager found this awesome app TaskFacade 4. Unfortunately the dev appears to have stopped development for it, and the HD2 is just too fast for the app. I was bored, so I decompiled it (it's .net so that's easy) and made some minor fixes.
Anyway, here's what I fixed:
4.02 fixed by aussiebum (thanks aussiebum! ):
1. Fixed names of shortcuts.
2. Changed default destination directory to install on a storage card when selected.
4.02 changelist:
1. Fixed a memory leak that occurred when an app was started and closed outside of Task Facade.
2. Cleaned up Layout config page.
3. Cleaned up config file loading to minimize potential errors due to old and incompatible config files.
4.01 changelist:
1. Increased maximum number of frames for zoom-unzoom animation.
2. Added an optional sleep between frames to smooth out animation and reduce amount of resources used by the app.
3. Fixed a minor race condition which sometimes caused an updated icon to flash through just reactivated app.
Attaching latest version. Works perfectly on my HD2. Check it out.
Attaching screenshots.
YouTube video demo: http://www.youtube.com/watch?v=bFZHZb5cX9A
_
... Thanks!
Possible to get some screens.
I usually feel that task managers drain the battery a bit. How about this one?
Added screenshots. I just got this phone, so it's hard for me to judge its impact on the battery life. I will do some experiments.
Excellent try!!!
I used to use TaskFacade on my HD, but I always got the problem of gwes.exe growing larger and larger when usin TF, so I had to unistall it.
Can you manage to correct this problem?
Mr. spacepants, why don't you fix even "klaxon" , as the source is free, because gives problems with HD2.. to dismiss/snooze an alarm needs to unlock the phone first
have original taskfacade 4 on my hd2 it works fine except for the reasons you gave for making the new one.
tried it last night and it came up with something like the settings wouldnt load. i sot reset hoping thats all it needed but it still didnt work.
then my phone started having the led blink non stop.
so i uninstalled and put the original back on.
soft reset many times and tried tweaks to get the light off and eventually it stopped.
overall the program didnt work and no idea if led was unrelated
jolas said:
Excellent try!!!
I used to use TaskFacade on my HD, but I always got the problem of gwes.exe growing larger and larger when usin TF, so I had to unistall it.
Can you manage to correct this problem?
Click to expand...
Click to collapse
spacepants,
Your modification causes me the same problem.
Is it possible to make TaskFacade run as a service?
jolas said:
Excellent try!!!
I used to use TaskFacade on my HD, but I always got the problem of gwes.exe growing larger and larger when usin TF, so I had to unistall it.
Can you manage to correct this problem?
Click to expand...
Click to collapse
I just tried it today. After about 20 hours of running, with many task switches gwes.exe grew from 4.73 MB to 4.85 MB. And I am not sure if this was because of the TaskFacade - I didn't see any connection between its growth and app usage.
I am pretty sure I didn't fix this. Did you use version 4 when you saw this behavior? I guess it could also be thanks to a fix made in WinMo 6.5.
jolas said:
spacepants,
Your modification causes me the same problem.
Is it possible to make TaskFacade run as a service?
Click to expand...
Click to collapse
Huh, strange. I am not seeing this. Do you have any repro steps? Also what are you running it on - which WM version?
lbhocky19 said:
have original taskfacade 4 on my hd2 it works fine except for the reasons you gave for making the new one.
tried it last night and it came up with something like the settings wouldnt load. i sot reset hoping thats all it needed but it still didnt work.
then my phone started having the led blink non stop.
so i uninstalled and put the original back on.
soft reset many times and tried tweaks to get the light off and eventually it stopped.
overall the program didnt work and no idea if led was unrelated
Click to expand...
Click to collapse
Crap, sorry for all the trouble. I don't see how the app could have made the LED blink - it has no code that would call that API. Are you sure it's related to TaskFacade?
I am fixing the dependence of the app on the config file. It sounds like the installer didn't work for you for some reason, since it should have replaced everything.
Thanks for giving it a shot.
spacepants said:
Huh, strange. I am not seeing this. Do you have any repro steps? Also what are you running it on - which WM version?
Click to expand...
Click to collapse
Now, I'm on WM6.5.5 (23542 build), with sense 2.5.20121225.0.
Let's say that gwes.exe is consuming 38MB before I use TaskFacade.
Right after I run TF, it raises to about 42,7MB and it keeps raising when I use new programs. There is a point above that, I loose HTC menus and standard WM menus are displaying instead.
After a few time gwes.exe stabilizes it size to about 44-45MB.
I don't know if there use some kind os issues when using TF in Touch HD, because it has the same effect with different ROMs I tested.
jolas said:
Now, I'm on WM6.5.5 (23542 build), with sense 2.5.20121225.0.
Let's say that gwes.exe is consuming 38MB before I use TaskFacade.
Right after I run TF, it raises to about 42,7MB and it keeps raising when I use new programs. There is a point above that, I loose HTC menus and standard WM menus are displaying instead.
After a few time gwes.exe stabilizes it size to about 44-45MB.
I don't know if there use some kind os issues when using TF in Touch HD, because it has the same effect with different ROMs I tested.
Click to expand...
Click to collapse
I think I may have found the problem, but without a way to repro the bug I can't be sure I fixed it. Looks like gwes.exe can in some cases cache images that are in use, and if you do not explicitly dispose of them, the cache keeps growing.
I am not sure why I am not seeing this on my HD2. I have a Kaiser and a Touch Pro 2 lying around here - I will see if I can get a repro with them tomorrow, and test the potential fix.
Weird that your gwes.exe at the beginning is already 38 MB - I haven't seen mine go above 6 MB. It sounds like some other program on your phone may already have a problem.
spacepants said:
Weird that your gwes.exe at the beginning is already 38 MB - I haven't seen mine go above 6 MB. It sounds like some other program on your phone may already have a problem.
Click to expand...
Click to collapse
It depends on which app you use to determine it: sktools separates process and heap (so the measure is lower) while, for example, memmaid keeps it together (and thus the measure is higher).
Anyway, to give an example, with Manila and iPhoneToday my gwes at startup is 13.6 mb with sktools and 42mb with memmaid
btw, i too (blackstone) have problems with TF as jolas: after a short while i lose manila menus AND TF, also if in foreground, is not visible (it's there, since if i blind click somewhere i go to a different task, but i cannot see anything)
spacepants said:
I think I may have found the problem, but without a way to repro the bug I can't be sure I fixed it. Looks like gwes.exe can in some cases cache images that are in use, and if you do not explicitly dispose of them, the cache keeps growing.
I am not sure why I am not seeing this on my HD2. I have a Kaiser and a Touch Pro 2 lying around here - I will see if I can get a repro with them tomorrow, and test the potential fix.
Weird that your gwes.exe at the beginning is already 38 MB - I haven't seen mine go above 6 MB. It sounds like some other program on your phone may already have a problem.
Click to expand...
Click to collapse
Sorry, I was not very clear. When I said that my gwes.exe is 38MB, I mean at a random point (after a few hours of use), not after a soft reset.
As for the gwes.exe and caching images, I believe that you are right...
I hope you to find a solution, to make possible for me to use TF.
Thanks for your effords!!!
bbonzz said:
It depends on which app you use to determine it: sktools separates process and heap (so the measure is lower) while, for example, memmaid keeps it together (and thus the measure is higher).
Anyway, to give an example, with Manila and iPhoneToday my gwes at startup is 13.6 mb with sktools and 42mb with memmaid
Click to expand...
Click to collapse
You are right! For my measure I use memmaid, after a soft reset gwes.exe is about 21MB...
bbonzz said:
btw, i too (blackstone) have problems with TF as jolas: after a short while i lose manila menus AND TF, also if in foreground, is not visible (it's there, since if i blind click somewhere i go to a different task, but i cannot see anything)
Click to expand...
Click to collapse
Yes, this is exactly the problem I have, too.
Are there other HD users who face the same problem with TF, or we are the only 'lucky'?
yeah i have no idea how it would have done anything to the led but it definetly happened right after installing ?
il give the next cab a shot though and see if it installs properly
jolas said:
You are right! For my measure I use memmaid, after a soft reset gwes.exe is about 21MB...
Yes, this is exactly the problem I have, too.
Are there other HD users who face the same problem with TF, or we are the only 'lucky'?
Click to expand...
Click to collapse
Strange, I still can't repro this. Tried it on a couple of Energy ROMs on my Touch Pro 2 (one based on 21898, the other on 23554) - nothing. At best I get a 50k growth in gwes.exe every time a program starts and closes. I am using Task Manager 3.1 for measurements BTW, but memmaid concurs.
OK, if this doesn't repro on my Kaiser I am going to write a quick test program and try running through the normal operations of the app several thousand times to see if that has any effect.
Could you confirm that the steps you are using to get into this state? Are they the following?
1. Start an app.
2. Minimize the app.
3. Open TaskFacade.
4. Switch to the app.
5. Close the app from TaskFacade.
6. Go to step 1.
Thanks again for trying this out, BTW.
spacepants said:
Strange, I still can't repro this. Tried it on a couple of Energy ROMs on my Touch Pro 2 (one based on 21898, the other on 23554) - nothing. At best I get a 50k growth in gwes.exe every time a program starts and closes. I am using Task Manager 3.1 for measurements BTW, but memmaid concurs.
OK, if this doesn't repro on my Kaiser I am going to write a quick test program and try running through the normal operations of the app several thousand times to see if that has any effect.
Could you confirm that the steps you are using to get into this state? Are they the following?
1. Start an app.
2. Minimize the app.
3. Open TaskFacade.
4. Switch to the app.
5. Close the app from TaskFacade.
6. Go to step 1.
Thanks again for trying this out, BTW.
Click to expand...
Click to collapse
I want to thank you for keep searching about the problem I face.
The steps I usually do are:
1. Start an app.
2. Minimize the app.
3. Open TaskFacade (I have assign it to a hardware key via AEButton Plus)
4. Switch to the app.
5. Close the app.
6. Go to step 1.
I am grateful for your work!
If you want, I could try your test versions to resolve the problem I face.
Thank you!
What button are you assigning taskfacade to and what app are you using to do it? I tried aebuttons and it fails to map the volume up and down on the T-Mobile US version of HD2...not sure about other keys.
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.
I've been happily running the GEEWIZ 2.6 ROM alternately with GEEWIZ kernel and KGB kernel. No problems at all except for the Stereo Bluetooth connection to my car.
The phone works great on newer versions of my car 2009 Acura TSX and other phones work fine on my car.
Well I (via Google) finally narrowed the problem down. There is a bug in the native android 2.2 and 2.3 code that Samsung pushes right through. HTC for example fixed the code in their phones.
Google this: "Issue 9888oor A2DP sound quality". I added the word Acura as well.
Cyanogenmod 7.2 RC1 does not have this bug and the phone sounds fine on my car. Would it be possible to extract or port the A2DP code from Cyanogenmod 7 and place it into GEEWIZ or other more stock ROM's?
The reason I want to stay more stock is that I can't get SMS delivery confirmation to work in Cyanogenmod 7 or 9 or Gummy 1.0 and SMS confirmation works well in GEEWIZ 2.6.
I have tried GO and HandCent SMS clients in addition to stock and have checked all combination's of receive and sent notifications and delivery requests and reports. None work. Texts get through fine just no confirmation. Verizon to Verizon should work.
I don't have enough posts to post in the Dev/GEEWIZ thread. Can someone help or cross post please? I've read until I'm blue in the face on both of these issues. ;-)
BTW, I have 2 fascinates and both act exactly the same.
Thanks!
Zong00 said:
I've been happily running the GEEWIZ 2.6 ROM alternately with GEEWIZ kernel and KGB kernel. No problems at all except for the Stereo Bluetooth connection to my car.
The phone works great on newer versions of my car 2009 Acura TSX and other phones work fine on my car.
Well I (via Google) finally narrowed the problem down. There is a bug in the native android 2.2 and 2.3 code that Samsung pushes right through. HTC for example fixed the code in their phones.
Google this: "Issue 9888oor A2DP sound quality". I added the word Acura as well.
Cyanogenmod 7.2 RC1 does not have this bug and the phone sounds fine on my car. Would it be possible to extract or port the A2DP code from Cyanogenmod 7 and place it into GEEWIZ or other more stock ROM's?
The reason I want to stay more stock is that I can't get SMS delivery confirmation to work in Cyanogenmod 7 or 9 or Gummy 1.0 and SMS confirmation works well in GEEWIZ 2.6.
I have tried GO and HandCent SMS clients in addition to stock and have checked all combination's of receive and sent notifications and delivery requests and reports. None work. Texts get through fine just no confirmation. Verizon to Verizon should work.
I don't have enough posts to post in the Dev/GEEWIZ thread. Can someone help or cross post please? I've read until I'm blue in the face on both of these issues. ;-)
BTW, I have 2 fascinates and both act exactly the same.
Thanks!
Click to expand...
Click to collapse
No problem, I'll have a look at it for you and see if I can fix that in GeeWiz for the final release. Thanks for PMing me, by the way, I was about to post GW 2.8, but I would like to be able to include this too!
thanks
I would be happy to test any change. I'm getting used to flashing every night now. ;-)
Well, I ported over what I *thought* was everything they did in CM 7.2 and all that I managed to do was destroy the ability to pair with a device so far
I dug out my old BT audio receiver and I can certainly hear that it sounds like garbage by default. Well, it wasn't THAT bad but I do see, er hear, what you are talking about.
My concern is that my receiver is old and crappy (it is), and I may never be able to actually hear any difference. That said, I will keep trying for a while, if I can at least pair with the receiver after changing something I will pass it along to you and see if it does something useful for ya!
From what I understand the Fascinate with stock software works on older Bluetooth devices OK. I don't know that for sure because I don't have an older bluetooth device. On my car, the stock Fascinate does not have any fidelity, it produces sound via bluetooth like an AM radio with clicking sounds. When updated to Cyanogenmod 7.2, the sound is very FM like with no clicking sounds.
I appreciate the effort!
thanks,
OK, I finally got back to this. I was replacing too many modules, I toned it down a bit to just replace the bluez audio module and the a2dp module. I can absolutely hear a difference now!
It's still Bluetooth, aka not perfect, but I can crank the volume on the Fascinate up much louder before it "splats" (that's a very technical audio term) and overall it just sounds much much better.
I've attached a test version of an update-zip you can try. Should work with Clockwork Mod and/or my GeeWiz Recovery, but I've only tested with the latter of course . I will be making a more official version for GeeWiz 2.8 (I may go ahead and release a 2.8.1 with this, it's a pretty big fix -- who cares if I said there would be no more updates, right? LOL)
THANK YOU for pointing this out to me!! Let me know what you think!
Not yet
No joy -
First I tried loading the patch over fullwipe GEEWIZ 2.8 and KGB 12/31.
Next I tried loading the GEEWIZ kernel over the KGB kernel.
And finally I tried loading the full 2.8.1 system file.
The sound is still not nearly as clear as Cyanogen 7.2 RC1.
I'm sure if the new build is somewhere in the middle or not. Seems like the full fidelity is present now but the clicking sound is still present.
Cyanogen BT is as clear as a direct audio connection. At least to my old ears.
I'll revert back to 2.8 and try the audio test again.
Do you think a full wipe would help - can't imagine why.
Zong00 said:
No joy -
First I tried loading the patch over fullwipe GEEWIZ 2.8 and KGB 12/31.
Next I tried loading the GEEWIZ kernel over the KGB kernel.
And finally I tried loading the full 2.8.1 system file.
The sound is still not nearly as clear as Cyanogen 7.2 RC1.
I'm sure if the new build is somewhere in the middle or not. Seems like the full fidelity is present now but the clicking sound is still present.
Cyanogen BT is as clear as a direct audio connection. At least to my old ears.
I'll revert back to 2.8 and try the audio test again.
Do you think a full wipe would help - can't imagine why.
Click to expand...
Click to collapse
Full wipe probably wouldn't do anything for ya, no. When you say clicking, is it fairly often, or more like once per song? I get what sounds more like a skip (to me) about once per song, I didn't think it was the same complaint, but perhaps it is? If so, at least I can duplicate it, so that's good.
I'm not sure if much more can be done, the only remaining difference is the audio.conf (trivial changes) and the libbluetooth C library itself, and replacing the latter causes the Fascinate to not be able to pair. I think source would be required to properly replace that module (CyanogenMod has that particular luxury). It could be in the Java code, though. If that's the case it can still be fixed.
I'll poke around some more and see if I can do anything else for ya. I was jamming all night over bluetooth last night, honestly I didn't even know the device could do that a few days ago - LOL.
djp952 said:
Full wipe probably wouldn't do anything for ya, no. When you say clicking, is it fairly often, or more like once per song? I get what sounds more like a skip (to me) about once per song, I didn't think it was the same complaint, but perhaps it is? If so, at least I can duplicate it, so that's good.
I'm not sure if much more can be done, the only remaining difference is the audio.conf (trivial changes) and the libbluetooth C library itself, and replacing the latter causes the Fascinate to not be able to pair. I think source would be required to properly replace that module (CyanogenMod has that particular luxury). It could be in the Java code, though. If that's the case it can still be fixed.
I'll poke around some more and see if I can do anything else for ya. I was jamming all night over Bluetooth last night, honestly I didn't even know the device could do that a few days ago - LOL.
Click to expand...
Click to collapse
The clicking sound in my car occurs several times a second and its really obvious. Acura blamed the phone (Samsung) saying just that the phone wasn't compatible but I wasn't convinced until I found the Android bug ID.
I really appreciate the effort and it sounds like you fixed a problem just not my problem. ;-)
I'm considering a Galaxy III this summer but Samsung has left a bad taste in my mouth.
Let me know if you come up with anything else to try.
thanks!
Well, I spent some more time on this, and found that Samsung actually does include the BT code with their public distribution. So ... I spent some time merging that with the Cyanogenmod code that's currently available on github, and gave it a try. Short version: fail. Sounds like crap again and still skips intermittently for me. I can't replicate your more frequent skip, I'm afraid, but this was certainly a step backwards regardless.
Next I tried replacing all the modules my custom build generated with the ones from CyanogenMod 7.2 RC1. Even bigger fail, no bluetooth at all.
Using custom build with the BLUEZ modules from CyanogenMod restored the sound quality but it still skipped. Basically back where I started, so fail. I don't see the code edits they made that improve the fidelity so much, maybe they haven't committed them yet?
Last try was to set Master=true in the system/etc/bluetooth/audio.conf file on top of everything else. Still skips, but maybe a little less often? Still chalking it up as a fail.
So I think I'm not going to be able to fix this for you. There's a chance that what they did in CM 7.2 RC1 is just not posted yet and I can still make a custom set of binaries that will work, but I'm not very optimistic about it. I think what I did in GW 2.8.1 is pretty much as good as I can get it. Sorry
I did the best I could. For what it's worth, BT audio on my Fascinate is light years better than it is on my Galaxy Nexus at the moment. Not much consolation for you, but it's something I guess. The fact that I was able to generate a set of working BT binaries from source is also a good thing, even if they didn't solve anything since that means if I even stumble upon the fix it's something I can build myself!
You're welcome to try my final attempt, I've attached the .zip to this post. This is a custom BT module build with the BLUEZ modules with the ones from CM 7.2 RC1 and the master=true setting in audio.conf. I really don't think it will solve anything for you, but the only way to be sure is to try, right?