Database Users

backlight, incoming call delay, and alarm bug

Cingular 8125
I have 3 issues...
1. The backlight seems to shut itself off every once in a while. I'll try to wake the phone from sleep mode only to notice there is no light, so I have to move the phone near a light source to see the dimmed screen and work my way to the backlight setting and increase it back to normal.
This happened once while I was driving
Is there a cure for this problem?
Also, I noticed spb pocket plus's backlight slider on my today screen does not work, nor do the shortcut commands it has for backlight up/down/loop etc.
2. When I was testing a new ringtone, I called my phone from another phone. I noticed it does not receive the call on the first ring. It receives it on the 2nd ring. I can hang up during or right after the first ring and not have it come up on my phone. Is this normal?
3. Alarm bug. This %$#@ lead me to hard-reset my phone 3 times already. When my phone is in sleep mode and an alarm triggers, sometimes the phone won't wake, but keeps playing the alarm. I wake the phone manually only to notice there is no alarm notification, but a flashing orange light and constant alarm sound and vibration. A soft-reset seemed to make the problem worse. Finally, I found a program called memMaid which lets me delete notifications and duplicate notifications etc. Is this the best method to cure this problem?
Thanks in advance.

With the backlight, do you have it on charge at the time of it messing up?
i've had this issue but only when the phone was on charge.
if i unplugged the phone, backlight came back and then i simply plugged it back in
other than that, no cure that i've found. what software version are you using?
for the alarm, not seen that, i have noticed that recently i've had the alarm apparently going off (but it hasnt!) and then almost 2 hours later, i have a msg saying "alarm" with the dismiss button and the time of when it was supposed to go off. very odd. luckily i have a nokia 6230i that i use as my alarm clock.
and for the calls... i have the same problem but only when i copy over my SMS back onto the device. after hard reset its fine, but as soon as my msgs go back, i think the phone mem gets slower. (i have 1600 sms now on the phone with about 300 contacts with pictures)
I have the same issue with sms where the phone will light up, 5 seconds after it recieves the sms... so i'm guessing thats the same as the phone side, it lights up on my end, 3-5 secs later it rings (which is eqiv to one ring on their side so it hangs up after 2 more rings).
very strange issues though, i hope softwre updates fix it because it is annoying me now!
also have an issue with my camera where if you dont X out of it, then dont expect it to load again unless you reset the phone. it just shows the "egg timer" and thats it. useless camera software but great pda/phone. again luckily i have a camera always with me anyway.

Only thing i have experience with this is for 1).
I still get that backlight problem.
It started happening when i installed PocketZenPhone beta.
After every soft reset, if i let the phone go into standby or the let the backlight time out, the backlight setting will go all the way to the lowest.
I don't know how to fix this bug, only thing i've done to sort with it is have a Today Screen launcher set up so that i have an icon that leads directly to the backlight setting, so whenever it dims on me, i'm 2 thumb pushes away.

Actually, this is the first time i saw this, when i installed zen on mine too!
It was then i realised that if you unplugged the power supply then replug it in, it fixed it
in the end, i got fed up of zen's stability or the lack off so i removed it, hard reset etc
it still happens but very rarely, and when it does, its just because i've turned it off and on while it was on the power supply

i have the same freaking problem with backlight. not sure what the deal is but very very annoying. is there a fix to this problem??

i have the same freaking problem with backlight. not sure what the deal is but very very annoying. is there a fix to this problem??

Mine had the occasional "backlight set to off" (i.e. pushing the 5-way would NOT turn it back on - had to use Control Panel applet) problem too. I never used Pocket Zen Phone on this phone (have on others in the past) but did use both SPB pocket plus and Phone Alarm.
I think the problem is somehow related to apps that try to control the backlight. As you've noted, SPB's backlight applets don't do anything, I think that PZP and Phone Alarm, as part of their attempts to control the backlight in their profiles mess it up somehow.
What i did was limit my profiles in PA to only two, and make sure both of them were set exactly the same way as far as controlling the backlight:
o Both profiles have backlight set to 50% all the time
o Both profiles set to power off the backlight at 3 minutes on both AC and battery
o Both profiles set to suspend the device at 2 mins on battery (so never getting to the "backlight only power-off" setting above).
o Having the backlight go dark on AC is new for me, but it keeps it consistent with the battery setting, but it's no biggie and if it ain't broke...plus if I touch any button it comes back on
I also removed SPB pocket plus and found some freebie utilities that do what I wanted from SPB.
So I'm not positive it's related, but doing these three things and i haven't had the light go dark since. Every once in a while after a reboot the light does go dark, but hitting any button or the 5-way brings it back so it's not the same "setting has been set to no backlight at all" problem I was having, and only seems to occur soon after a reboot, and then not again.
-JMS

i fixed my problem by flashing rom over with 2.17 US version.

Power settings resetting

Currently running May 1st Energy ROM, having an issue where regardless what settings I put for battery light settings (2 minute timeout) it always goes back to 10 seconds...any ideas?
Another issue is the problem with the stock lock screen...I want to completely disable it (both slider and soft key screen locks). I was using S2U2 But it causes double slide screen locks...

[Q] Screen won't turn on after a call ends

Hey,
I have a weird issue with the proximity sensor.
When I answer a call, the screen turns off as usual, however, every now and then the screen won't turn on after the call ends. The phone is still responsive however, and pressing the power button simply gives the lock sound.
I'm using CyanogenMod 6.1 Nightly 85 but I'm fairly certain it's happened before on other roms as well.
Any ideas?

That Problem I've sometimes too! Dont know to fix it...

[Q] CM7 Nightly #71 - Input buttons not glowing

I have flashed CM7 Nightly #71. Post flash the Input buttons on the phone stopped glowing. Reboot does not help. Even boot time the input buttons are not initialised.
Any solution ?
Edit : Well played with Display setting -- With Screen brightness set to auto mode, input buttons behave normally, but take a while to glow once you unlock the screen. Well I am using brighness widget button in the power widget to change the brightness.
Edit : Well after playing multiple time now it behave normally across all brightness settings in the widget. I shall trying reboot and check if it initialises during boot time and post reboot behavior.
Edit : Input button don't initialise during boot. 25-30% brightness setting when changed to Auto brightness, Input buttons started glowing normally.
Is this a bug or input button are supposed to behave in this fashion ?

http://review.cyanogenmod.com/#change,5239
That commit messed it all up.

It remains lit for me all the time - but, your comment on the commit explains it all.

I am on #83 with new kernal flashed. Input button issue still remains. It does not come on for some settings while toggling battery settings in power widget notification.
I have installed miui camera from kevin2516. Sometimes camera sound goes after clicking few times. Along with camera sound, all sounds of the phone go off even calls. Only reboot resolves this?
Any solutions please?

The Sound Off issue is a known bug. It was *probably* solved in CM7 Stable versions, not sure though.

Move from #71 to #83 feel voice clarity during the call is reduced inspite of 4 bar full signal indication.

Feedback ---- #83 with new kernel, miui camera error with complete sound off couple if times

Dt2W Casuing On Call Vibrations - CM13 Based Rom's

There is an issue I have been facing with all CM13 based roms for the OP2. If Dt2W is active it causes sudden vibrations when am on call. To troubleshoot the issue I did the following.
1. Wipe everything except sd card.
2. Flash Rom (Any with CM13 base)
3. Flash Gapps (Tried Open Full and TBO)
4. After first boot set up everything and let the phone settee
5. Make a few calls.
My Observations.
1. The vibrations are not intermittent i.e. they don't happen on every call just few of them.
2. It mainly happens when I am moving and talking eg when I am calling someone and walking. If my hand is still it mostly doesn't happen.
3. NO apps or specific Setup is causing this since I tried to reproduce the issue without any apps or setting changes (just ROM and Gapps)
4. Back in April '16 at some point Dt2W was broken on CM 13 roms the issue seems to have started right after that(I may be mistaken though)
I have spent a lot of time on the custom rom forums but no one seems to mention this as a bug. The reply mostly I got was disable Dt2W and that is really not a solution. It makes me wonder if am the only one facing the issue.
Can anyone who is NOT facing the bug post steps they followed to setup their rom may be I can try and trouble shoot further.
Thanks

AshDroidG said:
There is an issue I have been facing with all CM13 based roms for the OP2. If Dt2W is active it causes sudden vibrations when am on call. To troubleshoot the issue I did the following.
1. Wipe everything except sd card.
2. Flash Rom (Any with CM13 base)
3. Flash Gapps (Tried Open Full and TBO)
4. After first boot set up everything and let the phone settee
5. Make a few calls.
My Observations.
1. The vibrations are not intermittent i.e. they don't happen on every call just few of them.
2. It mainly happens when I am moving and talking eg when I am calling someone and walking. If my hand is still it mostly doesn't happen.
3. NO apps or specific Setup is causing this since I tried to reproduce the issue without any apps or setting changes (just ROM and Gapps)
4. Back in April '16 at some point Dt2W was broken on CM 13 roms the issue seems to have started right after that(I may be mistaken though)
I have spent a lot of time on the custom rom forums but no one seems to mention this as a bug. The reply mostly I got was disable Dt2W and that is really not a solution. It makes me wonder if am the only one facing the issue.
Can anyone who is NOT facing the bug post steps they followed to setup their rom may be I can try and trouble shoot further.
Thanks
Click to expand...
Click to collapse
Just a shot in the dark , did u try enabling prevent accidental wake-up ? Could be possible that when you are on a call you end up tapping the screen to trigger the vibration (Double tap).
When the prevent accidental wake-up is enabled this wont happen.
Hope it helps.

mdaamir1989 said:
Just a shot in the dark , did u try enabling prevent accidental wake-up ? Could be possible that when you are on a call you end up tapping the screen to trigger the vibration (Double tap).
When the prevent accidental wake-up is enabled this wont happen.
Hope it helps.
Click to expand...
Click to collapse
Yup tried that too but still bug persist.
I did flash an AOSP and CAF based rom (Exodus) to test it and found that it does not have the bug (Have to mention that they have disabled vibrations for dt2w meaning when it is active and used to wake the screen there is no vibration) . I think my hunch of something being wrong with CM13 base is correct.
Are you using CM13?
Thnx for replying

AshDroidG said:
Yup tried that too but still bug persist.
I did flash an AOSP and CAF based rom (Exodus) to test it and found that it does not have the bug (Have to mention that they have disabled vibrations for dt2w meaning when it is active and used to wake the screen there is no vibration) . I think my hunch of something being wrong with CM13 base is correct.
Are you using CM13?
Thnx for replying
Click to expand...
Click to collapse
I was , but i am on Exodus now. Maybe the next time i flash CM13 i will try to reproduce the problem.
Sent from my ONE A2003 using XDA-Developers mobile app

mdaamir1989 said:
I was , but i am on Exodus now. Maybe the next time i flash CM13 i will try to reproduce the problem.
Click to expand...
Click to collapse
Sure:good: thank you for your time.

Update
So I went back and flashed OOS to check why these vibrations don't happen on OOS. Turns out this has nothing got to do withe Dt2W or dialer as such. This behavior happens because the Prevent Accidental Wake up disables the Screen Wake up but allows Dt2W inputs. This is what I found
On OOS.
a. Double tap screen normally and you will feel haptic feedback and screen will turn on.
b. Cover the proximity sensor and double tap, the screen will remain off and there will be NO haptic feedback. Which is how prevent accidental wakeup should actually work.
On CM13 Based Roms.
a. Cover the proximity sensor and double tap the screen the screen remain OFF but the phone register's the double tap to wake gesture. Ideally prevent accidental wakeup should not allow the gesture input as well.
This behavior is may be because prevent accidental wake has not been integrated the properly. I say this because when the phone rings and you cover the proximity sensor (Prevent Accidental Wakeup Active) the screen goes off, this is not the correct behavior. The Prevent accidental wake up option should actually ignore proximity sensor when there is a phone call.
As of now I am on RR 5.7.1 and have disabled Vibrate on touch (Meaning even if the gesture happens the phone wont vibrate) I find this a better workaround rather than disabling Dt2W. Disabling Vibrate on touch means no vibrations for button press and long press and stuff like that which is ok with me (this option could also be the reason why some user say they have not felt any vibrations when making calls.)

AshDroidG said:
So I went back and flashed OOS to check why these vibrations don't happen on OOS. Turns out this has nothing got to do withe Dt2W or dialer as such. This behavior happens because the Prevent Accidental Wake up disables the Screen Wake up but allows Dt2W inputs. This is what I found
On OOS.
a. Double tap screen normally and you will feel haptic feedback and screen will turn on.
b. Cover the proximity sensor and double tap, the screen will remain off and there will be NO haptic feedback. Which is how prevent accidental wakeup should actually work.
On CM13 Based Roms.
a. Cover the proximity sensor and double tap the screen the screen remain OFF but the phone register's the double tap to wake gesture. Ideally prevent accidental wakeup should not allow the gesture input as well.
This behavior is may be because prevent accidental wake has not been integrated the properly. I say this because when the phone rings and you cover the proximity sensor (Prevent Accidental Wakeup Active) the screen goes off, this is not the correct behavior. The Prevent accidental wake up option should actually ignore proximity sensor when there is a phone call.
As of now I am on RR 5.7.1 and have disabled Vibrate on touch (Meaning even if the gesture happens the phone wont vibrate) I find this a better workaround rather than disabling Dt2W. Disabling Vibrate on touch means no vibrations for button press and long press and stuff like that which is ok with me (this option could also be the reason why some user say they have not felt any vibrations when making calls.)
Click to expand...
Click to collapse
Actually I face similar issue on cm based Roms , this issue is from day one . Also on OOS , sometimes screen is being pressed and notification bar slides down and buttons are being pressed while on call. Disabling dt2w solves temporarily.

kunalshah912 said:
Actually I face similar issue on cm based Roms , this issue is from day one . Also on OOS , sometimes screen is being pressed and notification bar slides down and buttons are being pressed while on call. Disabling dt2w solves temporarily.
Click to expand...
Click to collapse
Its a problem with CM13 base. So any rom using CM 13 will have this behavior. I believe the people who say they don't face this behavior have disabled vibrate on touch like I have now. I never had an issue with OOS though.
Can you let me know does your screen goes off when ringing on CM 13 (when you cover the proximity sensor with prevent accidental wake enabled)

AshDroidG said:
Its a problem with CM13 base. So any rom using CM 13 will have this behavior. I believe the people who say they don't face this behavior have disabled vibrate on touch like I have now. I never had an issue with OOS though.
Can you let me know does your screen goes off when ringing on CM 13 (when you cover the proximity sensor with prevent accidental wake enabled)
Click to expand...
Click to collapse
i am on OOS , flashing cm13 soon , will let u know.