I'm probably going to get flamed for this, but I've searched high and low and still cannot find a solution.
I'm getting pi**ed off that the Diamond seems to take almost 3/4 rings from a landline before it even makes a peep. The weird thing is, as soon as the landline starts the ringing sound, the diamond lights flashes immediately.
It's almost like the software can't keep up with the hardware. At the moment, I'm missing every single call as the answerphone kicks in before I even know I'm receiving a call.
Any clues/ideas/fixes.
Again sorry if I'm repeating a thread, but I couldn't find the answer anywhere.
here are several threads about this....
I did a search for 'ring'
http://forum.xda-developers.com/showthread.php?t=417359&highlight=ring
http://forum.xda-developers.com/showthread.php?t=403915&highlight=ring
http://forum.xda-developers.com/showthread.php?t=416100&highlight=ring
http://forum.xda-developers.com/showthread.php?t=400590&highlight=ring
alanplum said:
I'm probably going to get flamed for this, but I've searched high and low and still cannot find a solution.
I'm getting pi**ed off that the Diamond seems to take almost 3/4 rings from a landline before it even makes a peep. The weird thing is, as soon as the landline starts the ringing sound, the diamond lights flashes immediately.
It's almost like the software can't keep up with the hardware. At the moment, I'm missing every single call as the answerphone kicks in before I even know I'm receiving a call.
Any clues/ideas/fixes.
Again sorry if I'm repeating a thread, but I couldn't find the answer anywhere.
Click to expand...
Click to collapse
Was the same on my Trinity device and someone elses Wizard device. A feature of WM perhaps
there is a cab
fixs it..welll sort off
use the search and you will find
i have it on my diamond and its alot beter now
1. seems to me impossible that you, after soooooo much searching didn't find a thread to join instead starting a new one.
2. to my best knowledge (and i read and i really searched) there is no solution to this problem except the usual change the ring tones to mp3/change the rings to wav and a few very dubious cab files that (as a later everybody is complaining) had no effect. there is also one tweak in the Diamond Tweak program that also has no result (at least on my diamond).
3. just to add a slap to the insult, even the BT in my car start ringing before the diamond! i hear the BT device ringing and looking at my diamond i can see that he is still in the "mute but blinking" phase. most of the calls i pick and answer before my diamond's first ring.
4. now going to report this thread and ask some mod to glue it to an existing one. next time search and if not satisfied with the findings just post on an existing thread...
meanwhile you got more help than you deserve.
So friendly......
Fixed it now due to this thread. Disabled phone skin and changed mp3 to wav.
No issues now.
alanplum said:
So friendly......
Fixed it now due to this thread. Disabled phone skin and changed mp3 to wav.
No issues now.
Click to expand...
Click to collapse
just to stay on the "friendly" side: disabling the phone skin also gives you 10mb of more memory like in this post:
http://forum.xda-developers.com/showpost.php?p=2501745&postcount=27
or this one:
http://forum.xda-developers.com/showpost.php?p=2486722&postcount=1003
and pay attention at others have to say:
http://forum.xda-developers.com/showpost.php?p=2486738&postcount=1004 so maybe i am wrong.....
why i didn't recommend it to you? because is not so simple. it also disable a few other things. what things? i'll let you find out alone (this time).
I've flashed my 8925 twice and hard reset it once, I've tried with and without having allowed the ATT customizations, and still there's a bunch of stupid little crap that is driving me nuts. Please note: these bugs are with no additional software installed.
Can't keep the backlight from timing out. I've always disliked the default of having the screen auto dim: if the screen is on I'm probably *looking* at it, otherwise I'd have turned it off... I've tried everything, setting no backlight time out, leaving it checked but matched to the screen shutoff, it shows the right thing in the control panel and stays on after I leave that screen, but usually within minutes or especially after I've used the phone it'll start dimming at 10 seconds again--even though turn off backlight is still unchecked in the backlight control panel.
Missed calls / call log badly broken: I'll get the missed call notification but when I try to see the caller it shows the log as empty, and when I go into the log manually from the phone app it also shows empty--doesn't even have my outgoing calls.
Voicemail notification got stuck on. I can probably call ATT and have them fix this on their end in minutes but it's bloody annoying that my phone's been notifying me of a long deleted voicemail message for days.
Anybody else having any of these problems?
Anybody know a fix for any of them?
I've already tried advanced_configuration, no great help there.
What's the latest/best cooked ROM? I like that the official has stuff like Voice Command and Sprite Backup, would like to keep them...
I haven't noticed any of those problems. I have however had problems with the phone being really sluggish at times. Still testing with no apps installed. I don't have the backlight problem. I have just used the settings in Kaiser Tweak and everything is working. Not sure that I will keep using it though. I will probably go back to Hyperdragon's newest ROM's. Those always seem to work really well for me.
No issues with the official AT&T ROM either.
wmg76 said:
I have however had problems with the phone being really sluggish at times.
Click to expand...
Click to collapse
Are you using the right SPL?
I did not try the rom. But I heard cleartype w/ landscape problem still exist w/ this rom (like the official HTC 6.1 rom). It could be fix by replacing the ddi.dll but will probably break Opera mini 9.5.
Problems??? Pull up a chair! First I installed the ROM and none of my would work. I couldn't connect to the internet. I downloaded the ROM again and reflashed it. This time icons started disappearing on my phone. I did a soft reset. Nothing. Did a hard reset. Nothing. I reflashed. Loaded my apps, they actually worked. I set up my email, and I could connect to the internet. Great! Finally! One hour later, I got a phone call, but my phone didn't ring. Huh?Anyway, answered it, when the other party spoken it came out the speakerphone. I checked my device and there was no sound: ringtones,music games,alarms. Soft reset...Startup sound played..loaded up and no sound. Call ATT for a help, they decided to send me a replacement. Bad device, I guess. So I redownloaded the ROM and tried a different phone( i know, i know), can't get email to work, can't get MMetrics work. I quit!I will be going to custom ROM! I have a lot of reading to do.
Been using the new AT&T Rom since it was released and not having any issues. The only minor problem I have is that I'm seeing some compatibility issues with the version of S2U2 that I am using. Otherwise, good to go.
I don't get how people are having problems with this. Everything works flawlessly with me.
Except threaded messaging sucks, but with Kaiser Tweak, I turned it off.
I have had only 3 major issues with this rom.
1: Camera works, but doesn't show anything on the screen. I have a black screen, press the capture button, and I get a picture, but I can't tell what I am looking at until I take the picture. Working on this issue now. [Update] I just installed HTC Camera v5.04 b29195.00 http://rapidshare.com/files/99227062/HTC_Camera_v5.04_b29195.00__PPC_.CAB . Works Perfect now!
2. Battery life was HORRID! After 10 minutes I was down to 90%, while it sat on the desk, screen off, nothing running. After switching from 1.65.21.18 to 1.65.21.14, life was peachy. 8 hours with normal usage and only down to 80%.
3. Blue Tooth drops erratically. I connected my bt headset to the phone, made a call, after 10 or 15 minutes, it dropped the headset. BT stayed turn on, but headset couldn't be found. Turned off headset, turned back on, magically found. Haven't figured out what is causing this, but am researching that as well. OK, So I got on HTC's website to see if there was an update. There is no update for BT for the Tilt WM6.1. However, there is a fix for TYTN II WM6.0. http://www.htc.com/europe/SupportDownload.aspx?p_id=13&cat=0&dl_id=60. I decided to try this fix, installed thinking I would get the whole "this program was built for a previous version" garbage, but I didn't get that. Anyway, I am going to try this tomorrow when I make my calls. I will update if I notice it fixes my issues.
Otherwise, it's fast, good signal, good sound quality, etc. Overall I am pretty happy. Will be happier when I finally get the BT to stop dropping, as I travel a lot and it's illegal to talk on the phone w/o a hands free on any military installation.... Sorry if I didn't answer any problems others are having on this actual forum, but maybe someone else will be having the same issue and see my posts for my fixes. Thanks!
zip, zero, nada.......UI is faster, apps are faster, threaded SMS is really nice to have, MSVC works as advertised with my JB2.
Different Alarm Sounds!!
I have a small WAV file that I use as an alarm sound but now can't get the sound listing in the alarm setup. I use to put it in application data/sounds. It now doesn't show up if I put it there or anywhere else (/windows, /my documents/my ringtones). Anyone else have this problem?
eltrebor said:
I have a small WAV file that I use as an alarm sound but now can't get the sound listing in the alarm setup. I use to put it in application data/sounds. It now doesn't show up if I put it there or anywhere else (/windows, /my documents/my ringtones). Anyone else have this problem?
Click to expand...
Click to collapse
All my WAV and MIDI files in the root of Windows show up fine. How small is the file? 600kb is the size limit for sounds on AT&T ROMs unless you modify the registry key that restricts it. 600k may be large for an mp3 file, but that's only mere seconds of a WAV file.
I upgraded as soon as it was available and am seriously considering going back to the old WM6.0 ROM, which worked well. I have had several lockups and had to soft-reset. I have also had problems with calls. Once, it rang and shoed me the call, but wouldn't let me pick it up. Other times I have had echos. GPS lock time is also much longer. Oh, yes, the equalizer in TCPMP creates terrible distortion. It worked great in 6.0. And I am using the recompiled version.
It is great to get results of satisfaction with the new ROM, but I personally would like to know, for those who have been having problems and those, answers to some questions:
1 Which SPL
2 Which radio
3 Activesync or POP for email
4 Bloatware installed or not
5 PIE or other browser
I am sure that there are others, but those are what come to mind for the moment.
No Problems Here
FWIW, I think my Tilt is running much better with the new ROM. I've only had it (the new ROM) for a couple of days, but TT7 and Google Maps seem to run faster, and It seems to detect WIFI networks MUCH faster than with the old ROM. I'm a happy camper, at least for now.
I've noticed that its been alot slower and I don't like having a button devoted to the ringtone volume. The other HTC Tab I was using that was supposed to be an official use had Music allowing me to access Windows Media very easily now I can't. I also noticed my dialing pad is different and not the same as it was. I also don't like the threaded SMS on Windows Mobile it doesn't suit it. It makes it look very confusing and also I've noticed it has problems moving the screen upwards so that I can see what is being written in the space. Another thing I notice is randomly the HTC Home screen cuts itself off cutting off portions of the tab information. Its something to get used to but I don't see it happening cause I can't figure out what happened to some items on the phone like my GPS doesn't work, I am experiencing worse internet problems than before, Wifi dies frequently, and the dialer doesn't seem to work like it used to. Its a disappointment.
NotATreoFan said:
All my WAV and MIDI files in the root of Windows show up fine. How small is the file? 600kb is the size limit for sounds on AT&T ROMs unless you modify the registry key that restricts it. 600k may be large for an mp3 file, but that's only mere seconds of a WAV file.
Click to expand...
Click to collapse
Which key? I have been hunting... and no luck so far.
Backlight timeout linked to lock??
When I re-downloaded the software and re-flashed a *third* time things seemed to work better. The only thing I did differently was skip the 'setup a password' that last time I flashed.
The phone worked pretty well all weekend, and then this morning I finally put in owner info and set a pin password.
And I just noticed the backlight has started dimming after 10 seconds (or less) again. Restart didn't correct it, nor did changing the setting in advanced config so the screen doesn't dim for unlock screen.
For now I turned off lock and went into the backlight tab and it's stopped doing it. BLOODY ANNOYING. I've seen mention of the backlight timeout bug in other forums too...
Even while the phone was working well over the weekend I noticed that fairly often the first attempt to bring it out of standby flashes the screen on then it goes back off, comes on and stays on when I press power the second time.
I ran into the idiotic bug where text is white on white when in landscape mode, know I saw something about that being a cleartype bug or something and there being a fix, but why the hell would it be released like that?
Also, I can NOT get the 'message sent' notification to disable... does 'advanced config' not actually work?
Buggy is an understatement!
Having been unable to bear/ignore the bugs I reverted back to 6.0
Here's what I along with you guys have issues with.
1)Ringtones revert back to it's default tone whenever I open: Settings>Phone
2) Back-light reverts back to 10 seconds at random and often.
3) Google maps will not display letters when searching for places, but it'll invisibly type
4) Typical freezes on pages and things of that nature
5) Bloatware..
SeekerJBP said:
Which key? I have been hunting... and no luck so far.
Click to expand...
Click to collapse
I'll help you out here
Go into HKEY_CurrentUser --> ControlPanel --> Sounds --> FileSizeLimit ( it's a DWORD value)
Just delete the DWORD value, and bam, enjoy .
EDIT : wow, just realized this is my first post. I've been browsing the site since the Tilt came out, but I guess I've never found it necessary to post. haha!
TheCritic said:
Can't keep the backlight from timing out. I've always disliked the default of having the screen auto dim: if the screen is on I'm probably *looking* at it, otherwise I'd have turned it off... I've tried everything, setting no backlight time out, leaving it checked but matched to the screen shutoff, it shows the right thing in the control panel and stays on after I leave that screen, but usually within minutes or especially after I've used the phone it'll start dimming at 10 seconds again--even though turn off backlight is still unchecked in the backlight control panel.
Click to expand...
Click to collapse
I have the exact same problem with my 8925. My work buddy across the hall does not have this problem with his 8925. Running WM6.0 my screen has ALWAYS dimmed at boot, as well as after a call ended; his has never done so. Now, after we've both upgraded to WM6.1, I have all my same problems, as well as the additional 10 second auto dimming that I did not encounter with WM6.0, he still has none.
No matter what settings I change, no matter if connected to power, USB, or none, my screen dims after 10 seconds. I can get it to temporarily revert back to the setting of my choice, by going into the settings and then back out, but if I manually dim the phone, get a call, or pretty much anything, it defaults back to the automatic 10 second dimming. I'm so pissed off about this. S2U2 also automatically kicks in on every screen dim, so I can't use it while the dim prob is going on. Certainly someone within this HUGE base of geniuses has a definitive answer for this.
Lots of little bugs in this release.
Google maps doesn't like it.
Can't get TCPMP to work.
Gets sluggish.
MSVC doesn't notify.
Other things I can't think of now.
Pretty irritating to say the least.
Ok... I have set my backlight to 1 minute time out NUMEROUS times, but it keeps resetting itself back to 10 seconds after some time (i'm not sure how long). This is driving me crazy! Especially when I'm trying to read something. What can I do? ANY help is beyond appreciated!
p.s. It began after I installed the new windows 6.1 update.
I am having the same problem and it is also driving me crazy!!
Someone please help!
Thanks
Me to
..just yesterday the phone kept trying to dim at 10 seconds but S2u2 wouldn't allow it so it would come back on..and it kept doing that crap every 10 seconds!!! I can't stop that setting from reverting back to 10 seconds!!!
Seeeeee? Somebody has to be able to figure this out.
same issue
i got the same problem too. i got the oem rom with wm6.1 on it. i installed s2u and manila 2d and pocket tool man. tried all the settings i could find from those programs. but the backlight keeps resetting back to 10sec after a while
any help would be good!
Possible Fix when Backlight Patch doesn't work
Like many others, I have applied the Backlight patch and experienced NO improvement after the Tilt is turned off and on.
I have loaded PHM's RegEdit and had a look at other registry settings and found a solution that works on my Tilt.
Under HKEY_CURRENT_USER / ControlPanel / Backlight you will find a key called "LockLevel", my value for this key was initially 1. I changed it to 0, and since then, whatever setting I use for the backlight timeout stays put even after numerous power cycles and days of use.
Would someone else who is familiar and comfortable with RegEdit try this and confirm this so we can verify it is not just isolated on my Tilt?
dazimmermann said:
Like many others, I have applied the Backlight patch and experienced NO improvement after the Tilt is turned off and on.
I have loaded PHM's RegEdit and had a look at other registry settings and found a solution that works on my Tilt.
Under HKEY_CURRENT_USER / ControlPanel / Backlight you will find a key called "LockLevel", my value for this key was initially 1. I changed it to 0, and since then, whatever setting I use for the backlight timeout stays put even after numerous power cycles and days of use.
Would someone else who is familiar and comfortable with RegEdit try this and confirm this so we can verify it is not just isolated on my Tilt?
Click to expand...
Click to collapse
I am using the same PHM's , and my value is set at "0" already....
yes, Mine is also set at 0.
I cant believe that HTC would release a patch that doesnt work!
Anyone else had luck?
Setting it from 0 to 1
"Un-dims" your backlight. Setting it from 1 to 0 makes it bright thats all I could figure out
It's a known problem with the 6.1 ROMS, although not everyone experiences it. Even the stock AT&T ROM had it. An official fix for it was released not long ago. It's available for download here: http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=1&dl_id=269
It doesn't wipe your phone, so it's safe to do without having to set everything back up.
backlight works, but scroll wheel does not
jcreemer said:
It's a known problem with the 6.1 ROMS, although not everyone experiences it. Even the stock AT&T ROM had it. An official fix for it was released not long ago. It's available for download here: http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=1&dl_id=269
It doesn't wipe your phone, so it's safe to do without having to set everything back up.
Click to expand...
Click to collapse
This worked fine and fixed the backlight issue on my stock AT&T Tilt ROM, but it seems to have screwed up my scroll wheel function. Now my scroll wheel only turns up/down the phone volume. I can't seem to get it to do anything else in any other program.
bumblefreak said:
This worked fine and fixed the backlight issue on my stock AT&T Tilt ROM, but it seems to have screwed up my scroll wheel function. Now my scroll wheel only turns up/down the phone volume. I can't seem to get it to do anything else in any other program.
Click to expand...
Click to collapse
I haven't experienced that problem. What ROM are you using?
Finally!
Click Here for the .cab that fixed my unit. I got it off the ATT forum.
NOTE to all... Even this fix did not solve my problem until I checked the boxes to time the backlight. I like the backlight feature on all the time. If I don't want to see the screen, I turn it off.
I Had The Same Problem Too, But Then I Realized That Whenever I Disabled The Password Option In Settings It Went Back To Normal And Stayed At Whatever Timing I Set It To. The Only Thing About It Is That I Cant Use The Password Option In Settings. Unless I Was To Disable It Everytime I Used The Phone For More Than A Few Minutes At A Time...
I Have The At And T Tilt With The Shipped Wm6.1 Rom.
this will help
with your backlight problem
It helped me and then-some
I've tried all suggestions (except registry edits) and nothing works for mine! I like to keep my display on for GPS functions, but mine dims whether it's on battery or external power. The link for the cab in the AT&T forum no longer works, so I don't know whether that was similar to the HTC fix (which also doesn't work for me).
Since I have yet to try this, what program should I use to edit my registry? I've never done it, so I don't know what I need to do it. I also noticed someone posted these registry changes in the AT&T forum:
- change HKCU\ControlPanel\Backlight\ACTimeoutTemp value to your desired AC timeout in seconds. I set mine to 120 (2 min).
- change HKCU\ControlPanel\Backlight\BatteryTimeoutTemp value to your desired Battery timeout in seconds. I set mine to 60 (1 min).
- change HKCU\ControlPanel\Backlight\Locklevel\Locklevel to 0xFFFFFFFFF (this may also be just FFFFFFFF is your reg editor allows direct hex entries).
Note: With this change, if you wish to change your dimming timeout, you'll have to go back into the registry and update the settings.
Does this look like it would work? This is driving me absolutely nuts and I am this close to reverting to 6.0, even though my device was shipped with 6.1.
Thanks for the help, everyone.
EDIT: Since my search for this answer brought up too many different variables, I'd wanted to pose the question here, as it pertains to this issue... Will upgrading to a 6.5 ROM solve this backlight issue more simply?
Hi folks,
thought i write down my problem since i've been trying for quite a few months now to get rid of this problem:
First of all i need to tell that i am using dutty's v4 rom. I did not have the problem at all with some other roms, but i'd like to keep on using Dutty v4 since it is very fast, non-laggy with manila3D, and rock-stable.
So here is the deal:
After setting up my VoIP account, tweaking WLAN to keep attached to the AccessPoint even when the Diamond goes into sleep - I managed to make a VoIP test call to my provider via WLAN.
Everything works just fine - until the device falls into sleep after a couple of seconds.
Annoying thing is that it perfectly works with normal GSM calls even when it goes to sleep, but not with VoIP calls.
Not that i needed the display to work during the call - but audio as well as recorded audio - which gets lost as soon as the Diamond falls into sleep. I have to reactivate the display to hear/speak with the other person. So after i've done that it takes a random time until it falls asleep again. This takes about 2-10 seconds.
I've tried everything - DiamondTweak, Advanced Config, nosleep!!.cab, registry tweaks - nothing works. After i had that problem the first time with Dutty's rom v3.4, i also wrote him while ago. He fixed this issue in v3.7. Somebody got an idea what he did?
Now that v4 is out, the problem sometimes persists. It worked fine just after flashing the rom, then it suddenly stopped working after 3 Weeks. Now i made a hard reset, first thing afterwards i did: install all the voip stuff needed and it didn't work from the beginning.
It seems to be a problem affecting certain types of roms and their configuration, but i couldn't find out by now what's the exact matter. Even if the screen would turn off, but audio keeps on just to talk to each other (if i remember right, the Diamond is a phone too? this would be awesome!
After spending days with searching for it, the ultimate solution hasn't been posted on this forum so far. So if someone knows what to do about this, even if it means to recook a rom - please tell me!
Please read what i already tried before giving answers, and thanks in advance for any real help!