Database Info

Is this the ultimate BUG?

I just found the ultimate bug and I believe this bug is responsible for G-Alarm and pTravelalarm not working. These alarm programs set the system volume to a predefined value, no matter where it was before (off, for example).
Why the heck does the PHONE RINGER volume influence the SYSTEM volume?
Check out the video:
here
http://www.youtube.com/watch?v=aBZAkJwDHT0
Can this be fixed in Windows? Reg-Hack?

Anyone here with a AT&T Fuze that can test this please? Is my hardware defective? I'm still within the 30 days to return that sucker if it is.
Thanxxx

Wow, strange!!
I already saw your post in the G-Alarm thread yesterday.
Just tested it with my Touch Pro running ROMeOS 1.51, and I do not have this bug.

johanromijn said:
Wow, strange!!
I already saw your post in the G-Alarm thread yesterday.
Just tested it with my Touch Pro running ROMeOS 1.51, and I do not have this bug.
Click to expand...
Click to collapse
I suspect it is related to the latest AT&T stock rom. I hope someone with a brand new AT&T version can test this. If it's just a rom problem, then I can probably flash mine but I don't want to try that right now and lose warranty if I'm not sure...
here's my latest video that shows directly how crucial this bug is to any alarm program:
http://www.youtube.com/watch?v=lKIqwyk9g9I
Cheers
Stefan

Again, it's myself who figured it out. After hours of trying and 3 hard resets (thanks to SpriteBackup I didn't have to install everything over again!)
Here is the result and the culprit is identified!
http://www.youtube.com/watch?v=M_6-i976_xE
Anyone else here with the AT&T Fuze that has the same problem? Is there a fixed version of ozim available?

electron73 said:
Again, it's myself who figured it out. After hours of trying and 3 hard resets (thanks to SpriteBackup I didn't have to install everything over again!)
Here is the result and the culprit is identified!
http://www.youtube.com/watch?v=M_6-i976_xE
Anyone else here with the AT&T Fuze that has the same problem? Is there a fixed version of ozim available?
Click to expand...
Click to collapse
Interesting, but can you please post your solution in text form as well so that every single person who reads this thread from now until the end of time does not have to go watch a Youtube video ?

DrunkenOstrich said:
Interesting, but can you please post your solution in text form as well so that every single person who reads this thread from now until the end of time does not have to go watch a Youtube video ?
Click to expand...
Click to collapse
Yeah sure, no problem. I just thought a picture says more than 1000 words and a video says even more. But here in plain English:
Starting up the OZ IM Messenger Client on the AT&T Fuze (or worse, having it autostart with the system) completely screws up the system volume settings. Suddenly the RINGER volume slider also influences the SYSTEM volume. Say you turn your ringer volume all the way down but you still want to listen to mp3's in Windows Media... nada. If you set your phone to silent or vibrate and have a nice alarm program like G-Alarm installed, the alarm will go off but no sound out of the speaker!
After closing down OZ IM you still have to soft-reboot to get your system sounds back.

DrunkenOstrich said:
Interesting, but can you please post your solution in text form as well so that every single person who reads this thread from now until the end of time does not have to go watch a Youtube video ?
Click to expand...
Click to collapse
Seconded. Technical stuff lends itself to words better.

dr g said:
Seconded. Technical stuff lends itself to words better.
Click to expand...
Click to collapse
Is there a newer version of the OZ IM available that doesn't f*** up the system volume? That company's website doesn't even allow you to contact anyone, let alone check for updates or get support

Here's the newest development in this case.
Tried a different OZ IM (verizon version) last night and the sound bug was GONE. BUT I got errors connecting. Found out that there is a config file with verizon gateway in it, replaced it with the AT&T one. Still an error. Different one though (404). Re-installed the original AT&T version. Sound bug back immediately
Just overwrote the .exe file with the one from Verizon: Sound bug gone but again connection error 404...
WTF?
Anyone have a different AT&T version besides the obviously screwed up 2.0.84 M ?

long phone lag when trying to answer a call HTC Touch Pro

Does anyone know of a fix for the long lag in answering calls for the HTC Touch Pro? If you can help please write back in the simplest terms! I am just learning how to use the phone and finally learned how to download and install cab files.
Thanks!

Kermy33 said:
Does anyone know of a fix for the long lag in answering calls for the HTC Touch Pro? If you can help please write back in the simplest terms! I am just learning how to use the phone and finally learned how to download and install cab files.
Thanks!
Click to expand...
Click to collapse
What have you installed (to cause this problem)?

Do a search for "diamond tweak". There is an option to shorten the delay when an incoming calls rings. Perhaps that will help.

if you have S2U2 installed, you could try uninstalling or disabling that. You could also switch from the Diamond dialpad to the regular WinMo dial pad (the screen you see when go to the dialer). You can make this change using the Advanced Config Tool (i'm pretty sure, if not, then try Diamond Tweak).
There's also the initial delay value in the registry as mentioned in the last post.
These should all help, some more than others though.

there actually is an issue with Diamond tweak and advanced config...
if you use them to set your data disconnect time if re writes a registry value that makes your phone fritz when trying to answer calls.in reg editor go to HKLM/comm/connmgr/planner.
Look for a entry of suspendresume. change that to #777. shold cure your issue. while you are there if you want to help out your battery change the Cachetime value to 60. that will kill your data afret 60 seconds of no use.

weird.....suspendresume on mine shows ~GPRS! as a value??
schollianmj said:
in reg editor go to HKLM/comm/connmgr/planner.
Look for a entry of suspendresume. change that to #777. shold cure your issue. while you are there if you want to help out your battery change the Cachetime value to 60. that will kill your data afret 60 seconds of no use.
Click to expand...
Click to collapse

thanks for the suggestions and how do I fix the hang up lag?
The slow delay in answering calls was a problem right out of the box. When I installed the slide to answer function the phones responsiveness greatly improved. There is also a huge lag from the time I end a call to the time I can go back to my home screen. Any suggestions for fixing that lag?

Kermy33 said:
The slow delay in answering calls was a problem right out of the box. When I installed the slide to answer function the phones responsiveness greatly improved. There is also a huge lag from the time I end a call to the time I can go back to my home screen. Any suggestions for fixing that lag?
Click to expand...
Click to collapse
no idea, but i have the same thing

No luck with the tweak mentioned in post #5. However, after I replaced the HD CallerID with the default WM one (which is not that bad!) the phone responds rapidly :
1) Zero lag between first caller's ring and screen respond.
2) Almost zero lag between first caller's ring and bluetooth handset ring.
3) Less than 0.5 ring before the device starts ringing.
Only a minor problem : The bluetooth icon does not show any more on the taskbar although the BT connections works fine !

Ok, where do you change to the default caller ID? I tried the registry edit and changing to the default dialer skin and had the same problem. This is so frustrating! About 50% of the time when it rings I hit the answer button and nothing happens. It even takes about 10 seconds before the screen changes from the home screen to the phone screen when it starts ringing.

How big a file for the ringtone are you using? The bigger the file, IMHO, the longer it'd take for the phone to load it...

Delete your call history and the lag after hanging up should disappear.

Htc Diamond Regedit
Hello,
I have a problem with my HTC.
I used PHM Regsitry. I found the Suspendresume key, and it wrote GPRS!
I clicked the key, and because I did not know who to change the value, I just wrote #777.
Now when I try to go there and change what I did, when I click Settings in regedit, it is emty or the program crackes.
Please help.

Paches and fixes
Goto HTC's website. There is a patch to resolve the issue for the delay in sound when answering calls.
Regarding the delay after the phone cal has been discontinued use "Advanced_Configuration_Tool_v3.3" (search this site). There is a setting that you can change to resolve it (default is 3000ms[3sec])

Shawn Botha said:
...
Regarding the delay after the phone cal has been discontinued use "Advanced_Configuration_Tool_v3.3" (search this site). There is a setting that you can change to resolve it (default is 3000ms[3sec])
Click to expand...
Click to collapse
This hangup delay is one of the first settings I changed when I got the phone. Almost everytime I scroll through contacts phonebooks, the phone would accidentally dial, so I press end end end repeatedly, but by the time it hangs up, the other party already had my caller id, and would call back asking why I called.
Why is this 3 sec delay built-in? There must be a reasoning behind it.
And while we're on the delay issue, why did they set the camera up with a 3-5 second delay to shoot? Is it for the autofocus? I got rid of the reg setting, now the camera is faster, and no autofocus issues... so why were these delays there to begin with?

atlaswing said:
Why is this 3 sec delay built-in? There must be a reasoning behind it.
And while we're on the delay issue, why did they set the camera up with a 3-5 second delay to shoot? Is it for the autofocus? I got rid of the reg setting, now the camera is faster, and no autofocus issues... so why were these delays there to begin with?
Click to expand...
Click to collapse
How did you changed the shooting delay in camera settings? What registry edit did you made?

joao pinto said:
How did you changed the shooting delay in camera settings? What registry edit did you made?
Click to expand...
Click to collapse
its in Schaps Advanced config 3.3 under Camera. But i digress...
it still begs the question, from an engineering standpoint, why did they set up these delays and lags?

bobok13 said:
Hello,
I have a problem with my HTC.
I used PHM Regsitry. I found the Suspendresume key, and it wrote GPRS!
I clicked the key, and because I did not know who to change the value, I just wrote #777.
Now when I try to go there and change what I did, when I click Settings in regedit, it is emty or the program crackes.
Please help.
Click to expand...
Click to collapse
I don't know if you resolved your issue.
You just have to erase "~GPRS!" and type in "#777"
No quotes of course.
I use Dotfred Task Manager 3.1

Same problem
I recently got this problem with the answer lag, I was using the same rom, same applications, same everything for the past few weeks. I am not entirely sure what caused the problem.
What would happen is when I get a call and I hit the answer key, the phone stops ringing and vibrating but it would still be flashing and has the phone number shown, I also have the slider installed and when I slide it, the same problem comes up!
In my reg editor, I do not have HKLM!
Any advise would be appreciated, this is getting annoying for both sides of the call.
Thank You
UPDATE
I actually may have found the solution, I removed the wireless manager shortcut when holding the answer button, and so far it's been working very quickly.
Go to settings -> Buttons and switch "button 1" from w/e u had to "<none>" I didn't even restart my phone...
2nd Update
Nope, just got an international call and it's holding it up... maybe it has to do with caller ID ?

HKLM is HKey_Local_Machine

[Q] How to set in-call volume to max and stay there

Here is the thing, I just can't come around to permanently set my in-call volume to stay in maximum setting. Everytime someone calls, I have to crank side volume buttons to the max. However, I have to repeat this for every call as it automatically sets itself somewhere in the middle. Boy, this is annoying.
I have WM 6.5 HTC MEGA (TOUCH 2)

This was registry edit for the same issue on a different device though.
HKEY_CURRENT_USER/CONTROLPANEL/SOUNDCATAGORIES/INCALL = INITVOL - WAS 2, CHANGED IT TO 4.
Check registry to see if it exists and give it a try. Soft reset is required after edit.
good day.

chopper the dog said:
This was registry edit for the same issue on a different device though.
HKEY_CURRENT_USER/CONTROLPANEL/SOUNDCATAGORIES/INCALL = INITVOL - WAS 2, CHANGED IT TO 4.
Check registry to see if it exists and give it a try. Soft reset is required after edit.
good day.
Click to expand...
Click to collapse
nothing happen..if anyone knows how to solve this problem please help

Has anyone tested the OTA way of upgrading vs the manual way of upgrading to 2.3.5?

not to discredit anyone who has said OTA vs. manual makes no difference (especially respected developers, which I am a developer myself looking forward to getting started on Android soon after I get settled at my new job learning Microsoft stuff), but I wanted to see what would happen if I let update happen via OTA instead of the manual method. the real reason is due to the varying of results people are reporting (especially the biggest change people said they noticed that I was looking forward to, which was speakerphone volume). so far, the only thing I've really noticed was improved 3G (which could be a placebo fix they put in similar to Apple's "better signal" display, but i was actually still connecting to 3G on my way home from work in places I normally don't......a co-worker/friend of mine reported the same results).
so far, after moving BACK to GRJ22:
- my WIFI has actually been the same on GRJ22 again (thought I was getting better WIFI here at work post the update)
-tethering works (kind of a duh since it was confirmed by Sprint that it breaks with the update)
-speaker volume is the same (way too weak for my tastes)
-no 4G widget (would have been nice but wasn't upset when I found it wasn't added in GRJ90)
-3G SEEMS slower (haven't done speed tests)
it's getting too hard for me to just stay on GRJ22 though, so I will probably just manually update and wait to test this again after the 3 weeks are up if I notice bugs or something, so I'd REALLY appreciate it if anyone could do provide actual like measured and tested results from letting the OTA happen instead of manually upgrading....

jrdatrackstar said:
not to discredit anyone who has said OTA vs. manual makes no difference (especially respected developers, which I am a developer myself looking forward to getting started on Android soon after I get settled at my new job learning Microsoft stuff), but I wanted to see what would happen if I let update happen via OTA instead of the manual method. the real reason is due to the varying of results people are reporting (especially the biggest change people said they noticed that I was looking forward to, which was speakerphone volume). so far, the only thing I've really noticed was improved 3G (which could be a placebo fix they put in similar to Apple's "better signal" display, but i was actually still connecting to 3G on my way home from work in places I normally don't......a co-worker/friend of mine reported the same results).
so far, after moving BACK to GRJ22:
- my WIFI has actually been the same on GRJ22 again (thought I was getting better WIFI here at work post the update)
-tethering works (kind of a duh since it was confirmed by Sprint that it breaks with the update)
-speaker volume is the same (way too weak for my tastes)
-no 4G widget (would have been nice but wasn't upset when I found it wasn't added in GRJ90)
-3G SEEMS slower (haven't done speed tests)
it's getting too hard for me to just stay on GRJ22 though, so I will probably just manually update and wait to test this again after the 3 weeks are up if I notice bugs or something, so I'd REALLY appreciate it if anyone could do provide actual like measured and tested results from letting the OTA happen instead of manually upgrading....
Click to expand...
Click to collapse
It makes no difference how you acquire and apply it....you literally get the exact same package you would manually download. Someone just went into the logcat and grabbed the URL so everyone else doesn't have to wait for their IMEI/ESN to be flagged for the update.
There are some commits in the git repo that show a 1 db volume raise for call rx in speakerphone and a gain adjustment, but those are from 3/28 - unsure if they were merged for the previous OTA or not.
http://android.git.kernel.org/?p=ke...it;h=07f1a225e4cc598be5761104a73c92fcb7ec26a7
http://android.git.kernel.org/?p=ke...it;h=7298b54d8c7fa73722a8a34ba86af09b60d8c416
2.3.5 does show new Broadcom firmwares added for bcm4329.
http://android.git.kernel.org/?p=platform/system/wlan/broadcom.git;a=summary

krohnjw said:
It makes no difference how you acquire and apply it....you literally get the exact same package you would manually download. Someone just went into the logcat and grabbed the URL so everyone else doesn't have to wait for their IMEI/ESN to be flagged for the update.
There are some commits in the git repo that show a 1 db volume raise for call rx in speakerphone and a gain adjustment, but those are from 3/28 - unsure if they were merged for the previous OTA or not.
http://android.git.kernel.org/?p=ke...it;h=07f1a225e4cc598be5761104a73c92fcb7ec26a7
http://android.git.kernel.org/?p=ke...it;h=7298b54d8c7fa73722a8a34ba86af09b60d8c416
2.3.5 does show new Broadcom firmwares added for bcm4329.
http://android.git.kernel.org/?p=platform/system/wlan/broadcom.git;a=summary
Click to expand...
Click to collapse
i actually saw that android.git.kernel page before the update dropped (in reference to the speakerphone volume) so that is what kept me believing that speakerphone volume should be raised in this update. the lack of the 4G widget that was STILL in the 7/25/2011 changelog notes makes me think that it's possible that speakerphone fix was NOT added in this release either
but again....it's conflicting because people have been reporting a noticeable increase in volume. what i saw everyone mentioning was that they noticed a difference in OVERALL speakerphone volume (music, alarm, calls, etc..), whereas that git file says that it was increased in the CALL volume (which I am not noticing a difference for EITHER scenarios)....

jrdatrackstar said:
i actually saw that android.git.kernel page before the update dropped (in reference to the speakerphone volume) so that is what kept me believing that speakerphone volume should be raised in this update. the lack of the 4G widget that was STILL in the 7/25/2011 changelog notes makes me think that it's possible that speakerphone fix was NOT added in this release either
but again....it's conflicting because people have been reporting a noticeable increase in volume.....
Click to expand...
Click to collapse
I'd suspect the volume changes were added if it's in the release notes. 1db isn't a huge change though and it's only on received volume for calls - so things like playing music should be unaffected.
You'll see in the commit details that it's only for voice calls, with a new table being introduced specifically for CDMA calls: cdma_voicecall_gain_table
The Gain adjustment however applies to standard playback: cdma_playback_gain_table

krohnjw said:
I'd suspect the volume changes were added if it's in the release notes. 1db isn't a huge change though and it's only on received volume for calls - so things like playing music should be unaffected.
You'll see in the commit details that it's only for voice calls, with a new table being introduced specifically for CDMA calls: cdma_voicecall_gain_table
The Gain adjustment however applies to standard playback: cdma_playback_gain_table
Click to expand...
Click to collapse
yea, i figured music shouldn't be affected. I'm confused about the Gain table your statement though (because of how you said "however"), as in:
you said things like music should be unaffected. what does the the "gain adjustment" refer to? thanks again for answering so promptly....

jrdatrackstar said:
yea, i figured music shouldn't be affected. I'm confused about the Gain table your statement though (because of how you said "however"), as in:
you said things like music should be unaffected. what does the the "gain adjustment" refer to? thanks again for answering so promptly....
Click to expand...
Click to collapse
The 1db increase was to the table that is used for call volume.
The gain adjustment was made to the table used for standard playback. Gain (input level) is adjusted prior to amplification. From the commit notes it looks like the volume level (output level) itself was raised in the device so the gain was lowered to maintain a similar volume level. Otherwise you would have ended up with a potentially significantly higher output level.
The volume is raised at the latest version's device.
So, the codec gain is lowered to satisfy a certain volume.
Click to expand...
Click to collapse
So in theory this should yield little change if the commit notes are to be believed.

Can someone help me change the amount of volume steps on a mediatek based device?

I have Infinix zero 8 (android 10) and im trying to change the ammount of volume steps it has to no luck. It only has 15 steps system wide. Not the slider but the system itself only supports 15 volume steps unlike samsung phones for example with 100 steps in the system itself and 15 in the slider by default. Meaning that when using some app that would allow the volume to be changed with the increments of 1/100, samusung internet for example, then the volume would only change with the increments of 7/100 not 1/100 as it should. It might sound confusing, cause it is. Ive also tried changing the ammount of volume steps using https://forum.xda-developers.com/t/module-volume-steps-increase-for-magisk-v10.3554996/ and also gravitybox. They dont work as intended. They do add more steps to the volume slider itself, but dont fix that system wide issue of only having 15 volume steps. When volume steps are increased to 30 for example then the volume slider works the same as before from the steps 1-15 and then going past that it loops back to 0 and goes up from there. Meaning that steps 1-15 and 16-30 are exactly the same. No actual increase in volume steps. Been having that problem since 2018, never found a solution for it. Any help is welcome.

Hi! Have you found a solution to this?
Or does anyone know a solution? I'm looking for a non-root solution, excluding Precise Volume (which works, but's buggy).
Thanks!

ben dah knee said:
Hi! Have you found a solution to this?
Or does anyone know a solution? I'm looking for a non-root solution, excluding Precise Volume (which works, but's buggy).
Thanks!
Click to expand...
Click to collapse
use gsi and add ro.config.media_vol_steps=100 into build.prop

Thank you!
I forgot to mention that I'm also not looking to flash, but I'll keep your solution in mind.

ben dah knee said:
Thank you!
I forgot to mention that I'm also not looking to flash, but I'll keep your solution in mind.
Click to expand...
Click to collapse
see if it works in stock rom then