Hermes / 8525 - Bug with the button repeat rate setting - 8525, TyTN, MDA Vario II, JasJam General

Hi All,
Scrolling does not work as expected. In my HTC Hermes – Cingular 8525 there is a bug with the button repeat rate setting.
I have tried various settings using the – Settings – Buttons – Up/Down Control – Repeat Rate, and still have a problem with the behavior.
For example, hold down the 5-way button to scroll through contacts for a few seconds and the highlight of contacts continues to repeat long after I let up on the 5-way hardware button.
On my HTC Wizard / Cingular 8125, I can set the repeat rate to the maximum setting and the scrolling stops immediately when I let up on the button. This is the expected behavior.
The 8525 continues to scroll and scroll and scroll. This is a bug.
Anyone else experience this?
Any thoughts on a fix through a registry hack?
Thanks in advance.
++md++

No, can't say I'm experiencing that problem. Or any problem for that matter. My Cingular 8525 is still going strong. I hope you get this fixed.

same problem with my Oz trion. Very annoying.

I had the same problem with my Cingular 8525...even returned it for a new one. The problem didn't exist in the store (tested it), but started after I changed the settings to my tastes. Try going to Today/Settings/Sounds & Notifications/Hardware buttons. Make sure the box is NOT checked. No button sounds, but your phone should speed up. It worked for me. Now I'm a poster not a lurker!!

I had the same issue with my T-mobile Vario II. Sound disabling has solved it for me, too. For non-experts this might be very odd that the solution to a navigation issue is to be found at a sound function. Happy we are that some people take the struggle to find such unexpected solutions. Thank you, Bookworm!

I had this exact same problem with my 8525. I would scroll thru my contacts and be like "God this scroll wheel is slow..... stop!! damnit, quit going after I stop turning the wheel!" I set the repeat rate to the fastest and took the sound off the the hardware buttons and now it works like a charm. PERFECT!!

Related

Exec Backlight bug - anyone found a fix???

I have a bug in my Exec:
whenever I start using my Exec, my backlight setting (within Settings/system/backlight/"turn off backlight if device is not used for...") REVERTS back to 10 seconds,
although I keep on changing the setting to either 30 seconds or a minute.
- I think i read before that someone else had encountered this bug in the past.
--Does anyone else have this?
--Does anyone know of a solution to fix this problem?
i'll appreciate any help ! ...this bug is really bugging me :wink:
nobody has any input :?: :?:
Are you running PocketZenPhone, or any other brand of profiling software? They might interfere with the behaviour of this setting.
mine acts normaly !!
SiliconeS:
No - I am not using PocketZenPhone.
Although I am still (not for long though!) using the o2 Active [i.e., the o2 Personal setting] which MIGHT have some profiling s/w - I am not too sure....
I am about to disable it within the next few days in any case - I hope that would solve the issue.
:arrow: Please write if you have any other insight considering the info I just provided.
First, a question: the maximum backlight time is usually 10 sec (in the Jasjar, at least). Did you change it using a registry tweak ?
I believe it is the keyboard backlighting that has the 10 second maximum. It seems the screen backlighting maximum for battery is 5 minutes through the settings.
I haven't had this problem at all by the way.
Tekflow:
I have the O2 xda Exec - so I am not too sure as to the settings in JasJar - as I haven't tried the i-Mate Rom yet;
I think Shivafool is right - I strongly doubt that the JasJar has a 10 second backlight limit - and the keyboard light is quite limited in time ...
In the Exec at least you can change it by going to: Settings/system/backlight/"turn off backlight if device is not used for..." (as mentioned above...) I am sure it is located in a similar place on the JasJar.
As to my own problem - I used SiliconS advise and looked for any profiling s/w within the Exec. I strongly suspect that indeed it was the O2 Active s/w, which has some profile settings, and which constantly over-rode the regular setting.
I am not entirely sure yet, but after I will change the o2 personal settings to Corporate (which would also disable the o2 Active s/w) - within a few days - I will know for sure.
I will post here if the problem will not be solved by that.
Thanx for all the help everyone !
Oooops, sorry, I thought you were talking about the keyboard backlight.
On a slightly different topic, my Backlight button on the front between the two speakers doesn't appear to work.
ashleyhall said:
On a slightly different topic, my Backlight button on the front between the two speakers doesn't appear to work.
Click to expand...
Click to collapse
It probably does work, but the problem is that it is an almost useless button. If you have your timers configured such that the backlight times out and goes off before the device times out and turns off, then during the time that the backlight is off and the device is still on you can press the backlight button to turn the backlight back on. AFAIK that's the only function for that button.
Brett

How long does it take to your tytn to wake up?

Hello
My tytn require a quite large amount of time to wake up and I was wondering if I was the only one in this case.
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.
The virtual keyboard used for inputing the code is also getting on my nerv; most of the time it start with the landscape layout (without any reason) and it take 2 sec to adjust to the portrait layout; during that time it is hard for me to input my code correctly because the size of the key is changing.
So, 2-4 seconds for waking up plus 2 seconds for keyboard adjustement is in my opinion quite slow. Am I the only one experiencing this? Are there fixes out there?
I also have some trouble with notification; it wake the device up! If the device is not password protected (only after 15 minutes on my phone) it start most of the time PIE (because of the hardware button). All this lead so to my second question: Is there a way not to wake up the device (at least the input) in order to avoid unwanted press on the hardwares buttons.
Thank you in advance !
fun_key said:
Is there a way not to wake up the device (at least the input) in order to avoid unwanted press on the hardwares buttons.
Click to expand...
Click to collapse
Settings -> System -> Key Lock -> When device is off: "Lock all buttons except Power button"
Thanks for your fast answer, i ll give a try!
Concerning the screen orientation issue I found out that it is related to the HTC case magnet.
EDIT:
In fact it was already configured like this; the device is not waked up by the hardware buttons, but by the notifications.
if you use the key lock you can avoid unwanted key presses. As for wake up times. I don't think anyone who has this device wants to admit that it takes to long cause they paid sooo much for it. However, I will admit that it does take a long time to wake up. I am comfortable saying this because its much like a turbo car, at first its not as fast as most naturally aspirated cars (turbo lag), then it blows their doors off. So it takes a couple seconds to wake up, then its faster then most other devices.
Later, Lew
Agreed. Coming from standby I get two rings of the "Old Phone" ringtone before it goes to voice mail.
I am hoping that new firmware will resolve this issue - my wizard was certainly more responsive when i presses the poer button to bring it out of standby. This is furthur delayed by the fact that i keep scabbling around the top of the device for the power button insted of the side!
pof said:
Settings -> System -> Key Lock -> When device is off: "Lock all buttons except Power button"
Click to expand...
Click to collapse
This doesn't help with the particular problem. What I think fun_key is trying to say is that whenever he gets a notification (for example when he gets a new sms message or a notification for a meeting) the phone will come out of sleep mode, so the key lock setting for "when device is off" won't be in effect. Instead the device will be powered up and accepting all keypresses, like the IE / Messaging- buttons, not to mention any presses on the screen.
I too find this annoying, and wish there was a way to make the phone go back to sleep after showing me a notification, instead of waiting for the default sleep time to go by. There are programs out there that have this functionality (for example MortSaver) though, so my advice would be to use those.
- Pud.0
thank for the mortsaver ip; i ll give a try!
Have exactly the same problems as fun_key (power button, keyboard in landscape, etc), and I suspect most of other people do. The wizard was definitely more responsive.
fun_key said:
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.QUOTE]
I've found a solution to the problem regarding the length of time before a call is missed (this is probably known by most people, I only found it after tinkering with the settings):
Start>Settings>Phone>Services(Tab). Choose Call Forwarding in the list, then click Get Settings. Change the 'Forward After' setting to a higher number. I changed mine to 25 seconds. Problem solved for me!
Click to expand...
Click to collapse
g00nerz said:
fun_key said:
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.QUOTE]
I've found a solution to the problem regarding the length of time before a call is missed (this is probably known by most people, I only found it after tinkering with the settings):
Start>Settings>Phone>Services(Tab). Choose Call Forwarding in the list, then click Get Settings. Change the 'Forward After' setting to a higher number. I changed mine to 25 seconds. Problem solved for me!
Click to expand...
Click to collapse
Glad your problem is solved. Perhaps others may find the following of note as well as your solution above:
http://forum.xda-developers.com/archive/index.php/t-258109.html
Mike
Click to expand...
Click to collapse
Hi team
I have the same issue, every time i turn my hermes on after its been off for more than say 30seconds it starts in landscape mode then switches to portraite mode, its driving me mad, at least i now know i am not the only person. maybe this will be fixed in the next rom update, fingers crossed aye
UPDATE: i also found this thread
http://forum.xda-developers.com/showthread.php?t=286552&highlight=standby+landscape
does anyone have any thoughts on his comments?
I actually think that the reply in the thread i posted above is correct,
My Hermes is an IMATE JASJAM (same thing of course) and i use the original belt holder that came with it, it has two (2) magnets in it to keep the cover shut, when ever i get a msg and i pull it out of the case (turns on automatically to show me the msg) its always comes out in landscape mode.
I turned my phone on and passed the cover with magnet side down over the phone and sure enough as i did that the screen changed from portrait to landscape mode, thus confirming its the magnet that causes it and not a defect with the phone.

buttons problem in P3600

Hi All,
I have a strange problem, tried to search the forum,
without success...
Sometimes the OK button doesn't response (both OK buttons...),
only clicking OK on the screen works.
another issue - sometimes when clicking the action button nothing happens, or even worse - it acts like a long press even when I press it really shortly...
Any one else had such problems?
Is it (as I guess) a hardware problem?
I have the same problem and I dont think its the hardware cause the button is not presented in "buttonmapping" in the controlpanel. This has worked before. Please respond if you solve the problem.
Mine does it on occasion. Pretty sure it's software and It seems to happen with the same apps each time. Make note of what apps you have running when it happens.
Just started doing it again but I realized that I have never had a prob with the OK or Start Menu buttons but rather the softkeys. In Today Agenda, the left key (edit) stopped working and then a few minutes later the right key (menu) stopped working. I closed all apps and the problem persisted with every appointment I opened. Soft reset fixed it.
I should also add that I am not using the latest version of Today Agenda because I have not figured out how to make it look like the version I am used to.
Might be related: a lot of games I have tried don't seem to support the softbuttons, phone buttons, or really much else besides the directional pad and center select button.

Cingular 8525 Scroll Wheel Mystery

Hi all,
Long time lurker, first time poster. I have enjoyed my 8125 and when I upgraded to the 8525, I ritualistically came here for all the answers. However, there is one issue that I have experienced that is not echoed by anyone else.
I have ROM version 1.34.502.1 and have the following apps installed:
Eten Dialer
Phonealarm
PQzII
TomTom 6 Navigator
TCPMP
Google Maps
Live Search
The problem is that when I freshly boot the phone and place a call, I can manipulate the in-call volume via the scroll wheel. Up, down, no problem. However, when I exit out of the dialer screen and return to it a few hour later, I find that I can no longer turn the in-call volume down via the scroll wheel--only up works.
If anyone can shed some light on this matter, I sure would appreciate it.
Thank you!
Anyone have any insights into this matter?
Fringo said:
Anyone have any insights into this matter?
Click to expand...
Click to collapse
Not much help, but just an observation. The behaviour shown by your scroll volume is certainly not normal. I tested this out on mine. What I did notice was that there is some lag in the response of the scroll volume - so long in fact that it can appear to be non-responsive. It seems the device "remembers" the number of clicks up and keeps trying to raise the volume even though its at maximum. So even if I then scroll down it can take a few seconds for it to complete trying to raise the volume before it begins trying to respond to my down scroll. In fact this behaviour can make it appear as if when scrolling down it actually is raising the volume - but I think this is only due to laggy behaviour in my case?
Mike
I found that the E-Ten dialer disabled my scroll wheel short-cut to call history and quick dial. When I removed it these functions came back. Shame, I like the big buttons.
Mike
Thank you guys for your responses. It wasn't a huge annoyance for me. I just don't like it when functionality just evaporates away from my phone inexplicably. Hopefully, it can be resolved somehow? I will look for further responses.
Thank you all in advance.
It's the PQzII that disable the in-call volume adjustment. But my version is: "down" -> turn in-call volume down, "up" -> switch to today.
http://forum.xda-developers.com/showthread.php?t=300248
PQz version up
Hi all,
I uploaded new PQzII.exe for Hermes.
http://www.nicque.com/pqz/PQzII.htm
2007-04-21 0.0.7-4 [Bug fix] PQzII_20070421_0007-4_Hermes.zip
*) Jog wheel (Volume Down) bug fix while calling.
Please try it and let me know if you find any trouble.
cheers,
tom
*)Edit
if you use "0x76" as any function. It has been changed to "0xAA".
There are some Hermes devices as like DoCoMo hTcZ/Softbank X01HT have "MOJI" button.
The button outputs "0x76" but it could be a cause of Jog wheel problem while calling.
as for me, I used 0x76 key code for IME on/off. and changed to "0xAA".
if you don't use 0x76 you don't need to care about this.
cheers,
tom

Power management problems/disillusions

I have my P3600 since Saturday and I updated it with the latest ROM which included the GPS.
Now I’m having problems with the power settings and functionality. I search all the threads for solutions but no similar problems are described so I post a new thread.
Problem 1:
The power settings are: backlight off after 30 sec. power off after 1 min. (on battery power). After 30 sec. the backlight dims to the lowest setting but the device does not switch off after 1 min (or any time for that matter). This is a huge drain on the battery! I can switch off the device with the power button but once it turns on again (e.g. while receiving an SMS or email) it stays on with the dimmed backlight.
Problem 2:
Using a Bluetooth headset and the media player the player pauses when switched of with the power button. This means just listening to music for around an hour and the battery is completely flat. My previous device was a S200 and that worked fine (could be switched off with the power button).
My guess is that both problems may have simple solutions so I’m asking you all to help me with this.
Thanks in advance,
Stefan
niobium said:
I have my P3600 since Saturday and I updated it with the latest ROM which included the GPS.
Now I’m having problems with the power settings and functionality. I search all the threads for solutions but no similar problems are described so I post a new thread.
Problem 2:
Using a Bluetooth headset and the media player the player pauses when switched of with the power button. This means just listening to music for around an hour and the battery is completely flat. My previous device was a S200 and that worked fine (could be switched off with the power button).
Click to expand...
Click to collapse
Well for problem 2 you haven't searched enough! Anyway you should not use the power button; go to the Windows Media player settings and map the "Toggle screen" function to a hardware button. Then toggle the screen off when you play music.
Regarding your other problem: what software have you installed? Have you got this problem on a freshly upgraded phone?
The solution you propose for problem 2 probably works for other devices but not for the Trinity. You can only assign buttons up, down, left, right and enter and they are needed within the player for obvious functions.
Problem 1 after fresh ROM update but right after that I installed TomTom 6.
I might try a new ROM update and check but rather as last resort...
niobium said:
The solution you propose for problem 2 probably works for other devices but not for the Trinity. You can only assign buttons up, down, left, right and enter and they are needed within the player for obvious functions.
Click to expand...
Click to collapse
It works for the Trinity too. You can also assign other functions to buttons if you keep them pressed. Toggle screen is assigned to "Hold Down" in my case. So if I press down once I decrease the volume, if I keep pressed I toggle the screen.
As to your first problem; i'm having the same problem too...
To narrow it down a bit; my device turns off (to standby) just like it should when i just briefly check the time or something and then put it away with the todayscreen on (so with no aplications running except some today-plugins ofcourse). However; it DOESN'T go back to sleep when the system has given any sort of notification, like a missed call or a received text-message or reminder for a calendar-item.
So my best guess is that it has something to do with the databases notification que (where WM2003/CE 4 had the problem of overflowing this notification que).
It's really anonying the hell out of me too, cause it really drains the battery fast if you don't discover it soon enough...
As for problem 2; map the screen-toggle to pressing the silver 'enter'button.....that workd great for me. By the way; i'm tinking about getting the new wired media remote control HTC is releasing shortly (check this link). I wonder if these buttons will be mappable.....
Edit: just as i posted this, i received a text message and this time it nicely turned back to standby (ie turned of) state when i didn't check it right away. I did however soft-reset last night before going to sleep. So i really do think it must be in the notification que somewhere, as PocketPlus will still clear that everytime i soft reset. Anyone having the same problem exactly as described ?
Well I found my phone again on after I received an SMS and this made me decide to completely reinstall the original ROM (including the GPS).
Step by step I installed all the applications (and tested the device in between: I started some programs and got some notification).
So far the result is that it all works fine now.
The difference might be the different ROM (from smartmobility.nl in stead of europe.htc.com although the version is exactly the same).
For problem 2: I unmapped the button 1 (was speed dial and moved that one to press&hold). In media player I mapped the button to ‘toggle screen’. I still like the S200 for this better because it only kept the media player & Bluetooth alive so that’s the best for preserving the battery…
niobium said:
For problem 2: I unmapped the button 1 (was speed dial and moved that one to press&hold). In media player I mapped the button to ‘toggle screen’. I still like the S200 for this better because it only kept the media player & Bluetooth alive so that’s the best for preserving the battery…
Click to expand...
Click to collapse
Hmmmm....i do the screen-toggle everytime i use it as a musicplayer, and i get considerable good batterylife....
However, i'm not using the BT headset anymore cause the volume was too dim...i'm using the 3,5mm adapterplug now. But batterylife with bluetooth was about the same when i used it.
After all the work yesterday, this morning the problem with not going to standby occured again!
But now I know more. It happened only after I added some sites to my RSS feedreader.
I use pRSSreader from David Andrs (http://pda.jasnapaka.com/prssr/)
Using the 'update settings' with 'automatically connect' the program tries to create a notification on the today screen if new messages arive.
This notification process is the problem. If I switch it of and soft-reset, the device works fine again.
I will mention this problem to David Andrs...
I hope this will help you as well.

Categories

Resources