Related
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.
My screen rotation has stopped. It remains on portrait.
I'm guessing I need to exchange the phone.
Any other thoughts or suggestions?
Oh, I'm on the Froyo Beta 2.8.1 of Design Gears'. Been on it for a few days, so I doubt that has anything to do with it.
i hope you have tried pulling down the notifications, and enable auto rotation, or checked it out in the settings....! ! !
neo_31591 said:
i hope you have tried pulling down the notifications, and enable auto rotation, or checked it out in the settings....! ! !
Click to expand...
Click to collapse
Thanks for the suggestiong, but yes, of course Including power off, pull battery reboot; look in several other programs that may fiddle wiht it.
Later, I did one-click back to orig ROM, and it still did it. Went to a 4 hour meeting and after that it works
What I'm afraid will happen now is it will work until my 30 days are up and quit again.
youre lucky that you were able to flash back! my phone did the same thing only when it was stuck in portrait mode I lost all ability to interface via usb... so I was stuck until android magicaly fixed itself today. My phone was stuck like that for 4 days.
Well, I'm back to no rotation, and Screeble is showing as Phone Idle.
I am beginning to think that the sensors on the phone are going out.
ewingr said:
Well, I'm back to no rotation, and Screeble is showing as Phone Idle.
I am beginning to think that the sensors on the phone are going out.
Click to expand...
Click to collapse
I went through the same thing with Assonance. Fixed by installing launcher pro, then recalibrate in display settings, then uninstall launcher pro. I used launcher pro because it has its own screen rotate setting that reset the phones. Give it a try.
Pretty much immediately after posting, I decided to reload my ROM. That fixed it. This happened immediately after doing some software upgrades from the market. Apparently software can screw it up. Or a botched upgrade.
Well, my rotation is broken once again. This is becoming a bit frustrating.
There were 6 apps that updated last night. I'm not sure why/how an app could break rotation. I can toggle it on and off, but the sensor is not working.
I guess I will once again restore to stock, rflash, etc, and see if it comes back. If its the hardware, I wish it would just quite once and for all, and I'd hvae the phone replaced.
This is gonna help so much but that sux
Sent from my GT-I9000 using XDA App
Since last night, my screen stopped timing out. I've been playing around with trying to get wallpaper to look right, and have installed Wallpaper Set & Save (didn't make it look right) and WallpaperCASA (can't figure out how to use custom wallpaper). Not sure if installing them is related, but a few hours after, my screen no longer times out. Eating battery charge. I can't find a setting in either one of them that has anything to do with this. And the screen was timing out fine immediately after installing them.
Timeout settings are set to 2 minutes. Does anyone know of another setting that controls this?
loribuono said:
Since last night, my screen stopped timing out. I've been playing around with trying to get wallpaper to look right, and have installed Wallpaper Set & Save (didn't make it look right) and WallpaperCASA (can't figure out how to use custom wallpaper). Not sure if installing them is related, but a few hours after, my screen no longer times out. Eating battery charge. I can't find a setting in either one of them that has anything to do with this. And the screen was timing out fine immediately after installing them.
Timeout settings are set to 2 minutes. Does anyone know of another setting that controls this?
Click to expand...
Click to collapse
Just ran into this myself....anyone, anyone?
I wasnt messing with wallpapers just screen timeout stopped working.
Got the same issue (no screen timeout) but with some odd thing. When I try to setup the screen timeout choosing "screen" on setup menu... I´ve got an error... the setup process ends unexpectly. I´m using N114, lastest OC Kernel from Dalingrin.
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
lean7 said:
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
Click to expand...
Click to collapse
this work with zeus?
Yep, I've 6.31n and work good.
lean7 said:
Yep, I've 6.31n and work good.
Click to expand...
Click to collapse
doesn't work. just blink once, then off.. what's wrong?
---------------
maybe doesn't work with 6.31o..
Used it once, in february...its not this good
But does the job
Sent from my LG-P970 using Tapatalk
This app is known here. There already was a discussion with it.
From the app in Google play:
"We are aware of the issues with Optimus Black since the 2.3.4-update"
ciplukzz said:
doesn't work. just blink once, then off.. what's wrong?
---------------
maybe doesn't work with 6.31o..
Click to expand...
Click to collapse
You were right! It's not working now :S
Thankyou for sharing this app!
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out:
http://www.mediafire.com/?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
If you want the source my build directory is hosted here: http://www.mediafire.com/?hmx5wpbwx00c47l
brownowski said:
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out (sorry for the format, can't post links yet - please remove the spaces):
Code:
www . mediafire . com / ?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
Click to expand...
Click to collapse
Good aproach! Take into account that is normal that the kernel switch off leds on battery... think in the leds allways on... I have had some kernel-related atempts to correct this... but atm no luck.
Regards!
When the screen is off and the device is on battery it is doing some sort of polling every few seconds to check and reset the LEDs rather than just a trigger when the screen turns off and that is what makes the app not work.
I tried a few different ways to reset the LEDs but the only way that would work is to force them off by writing a 0 into led_onoff followed immediately by a 1 into led_onoff. It wasn't enough to just echo 1 > led_onoff, I had to do a 0 first. However, with power connected, just the echo 1 > led_onoff was all I needed.
As far as I could tell, the led_onoff seems to only part of the 970 device code. I'm guessing that the other devices don't have an issue because they don't have to activate the LEDs in that way.
One other thing I tried was removing all write privileges to those files after turning on the LEDs to see if the system was writing a value into them to turn them off. They were still turned off so I kind of figured it's something in the kernel itself manually resetting things.
this should be good if work in customs ROM...to notify us for new message and etc
have a problem
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
lean7 said:
You were right! It's not working now :S
Click to expand...
Click to collapse
anguszhou said:
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
Click to expand...
Click to collapse
read the first page pls. it isnt working with 2.3.4 we know that.
anguszhou said:
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
Click to expand...
Click to collapse
Did you try the one I posted in post 9? http://forum.xda-developers.com/showpost.php?p=28571222&postcount=9
It sort of works in blink mode (best with repeating non-fading pulse with a lit time of 2000ms).
I'm using it in Zeus v6.35 at the moment.
lean7 said:
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
Click to expand...
Click to collapse
My only wish is that it was all 4 lights instead of just search, but who cares, in a month Ill probably prefer just search and be happy
Thanks for this find, I was desperate for it
brownowski said:
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out:
http://www.mediafire.com/?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
Click to expand...
Click to collapse
Still not working on 2.3.4
working on ics?
New version of LG Notifications
jn83 said:
Still not working on 2.3.4
Click to expand...
Click to collapse
Hi, please test the attached APK. For now I have worked exclusively on the mode "repeat fading pulse". Please unintall the application if you have it already installed.
I used it for 2 days now and it seems to work for me, so report bugs, but only for the mode repeat fading pulse if have problems. I will try to fix also the other modes, when I have time.
PS: of course all credits go to the original creator of Lg Notification application. I only try to fix this to work on Lg Optimus Black on Gingerbread.
Dan
danfizesan said:
Hi, please test the attached APK. For now I have worked exclusively on the mode "repeat fading pulse". Please unintall the application if you have it already installed.
I used it for 2 days now and it seems to work for me, so report bugs, but only for the mode repeat fading pulse if have problems. I will try to fix also the other modes, when I have time.
PS:
Dan
Click to expand...
Click to collapse
There is a problem with repeat fading pulse. It eats too much battery. Constant light it is much battery friendly.
Google Play Music is really screwy. It works for the most part but sometimes when opening up a new interface like clicking on an album or artist it crashes my phone. The phone will freeze and it wont recognize any touch input. Turning the screen off and back on will just bring up the frozen page, it doesn't even bring up the lock screen. I have to either pull the battery or if i let it sit for a few minutes it automatically reboots. It continues to play music while frozen though. I uninstalled the app and got rid off my xposed mods that interacted with the app and then reinstalled it. I still have the same problem though. Sometimes it happens every few hours but I have had it happen every few minutes sometimes. I'm using the newest version of the Xtreme ROM but no one else seems to have this issue.
t3chfr3ak said:
Google Play Music is really screwy. It works for the most part but sometimes when opening up a new interface like clicking on an album or artist it crashes my phone. The phone will freeze and it wont recognize any touch input. Turning the screen off and back on will just bring up the frozen page, it doesn't even bring up the lock screen. I have to either pull the battery or if i let it sit for a few minutes it automatically reboots. It continues to play music while frozen though. I uninstalled the app and got rid off my xposed mods that interacted with the app and then reinstalled it. I still have the same problem though. Sometimes it happens every few hours but I have had it happen every few minutes sometimes. I'm using the newest version of the Xtreme ROM but no one else seems to have this issue.
Click to expand...
Click to collapse
maybe do a KDZ installation and it might fix it. if it continues its something else.