Related
I haven't fully tested this issue yet mainly because I've only had the phone for a few days... I wanted to check if anyone else had this problem.
Under Settings -> Sound & Display -> Notification Flash
I have all the options ticked.
In theory, whenever I have a missed call or a SMS or email etc, I should be able to tell that I need to check my phone be a little blinking light in the top right corner off the screen. I just came back to my phone and this LED wasn't blinking but when I turned on the phone, there was a missed call and a SMS.
Other times, it seemed to work fine.
Anyone else noticed this problem?
it only flashes for 5 mins and then stops. There is no way to change this without additional apps.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Oh... How disappointing. Pretty useless imo. Thanks for the info. I wonder if they will fix it. My previous phone, Touch Diamond, had something similar but it never stopped flashing until you looked at your missed calls.
Now that explains things. I tend to look for the led after I've not used the phone for a while. In my pocket or elsewhere. Quite a few times I've seen no flashing but have a notification in the top left. I thought it was another one of those little 'features' we keep finding.
Yeh i discovered this awhile back and it's annoying as hell, i just use a app called Missed Reminder which can be configured to allowed it to keep flashing indefinitely
I was just going to make a post about this. I thought the LED notification wasn't working at all on my Desire, since I've never seen it, but perhaps it had just stopped before I had the chance to catch it, then
ardsar said:
it only flashes for 5 mins and then stops. There is no way to change this without additional apps.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What apps are you referring to? It would be nice to be able to have the LED flash longer.
I'm guessing this is to save battery time, I don't know how much power a small LED uses but it surely can't help with the already abysmal battery life
I first thought the LED was located behind the optical trackpad, because the trackball on my Hero could light up. I think the LED-notification is pretty dumb since it's almost invisible when it lights up. The lighting trackball was much much better
This is a known issue. I thought that did not happen in Android, but I guess I was wrong.
If the phone work in Windows Mobile, there are a registry key to let assign values to the options, so they are usable.
Here: http://forum.xda-developers.com/showthread.php?p=4846399#post4846399
In Android, I have no clue... maybe my info help in any way.
PMoto
It would be nice to be able to change the flash time from the default 5 minutes, or atleast an option for no time limit.
I know it's to help save battery life, but I'm willing to say that the light flashing will use less battery then the back light coming on everytime I'm away from my phone for more then 5 minutes, from me checking to see if I have new messages, email, or missed phone calls.
Same issue with my recently purchased A40.
No blinking at all despite screen flash notification selected.
Hope someone can help
Hello,
I recently bought an Incredible for my girlfriend on craigslist. It was only 2 months old (in great condition to boot). Either way after flashing CM7.0 I noticed that the automatic backlight setting did not work. I just set it to around 25% and figured I would figure it out later. After 7.0.2.1 came out I flashed that and no change. I then decided to figure it out. It seems that after waking the sensor doesn't work unless really flooded with direct bright light (such as the flash light from my incredible). After that it works mostly as intended.
Here is how I tested it. I lock the phone when in the custom light levels screen. When unlocking the Sensor (filtered / raw) is at 10/10 and will not change no matter what I do until I hit it directly with a bright light. I believe that it will also change eventually letting it just sit. Most of my tests involved using bright light sources. After that the sensor works just fine and changes almost instantly when I cover it with my hand and then move it into regular room light. Is this a known issue? I checked the bug tracker briefly but did not see anything. I have had two others test. One had fine light sensor response the other had the same issue as me.
Anyone have any idea?
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
k_nivesout said:
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It does work but the sensor doesn't respond in a timely fashion.
Have you tried changing the sample interval?
Sent from my ADR6300 using XDA App
What settings are you using? I.E. do you have filtering enabled? What is your window length? Sample interval? Etc.
I've never seen anyone discuss this as a CM7 bug. Based on the way you are describing it, it sounds like you might just need to tweak your settings.
For example, if your window length is very long and sample interval slow, that might be why your readings are taking so long to update. As for why the reading changes as soon as you hit it with a bright light, you could be tripping the reset threshold.
Just in case you haven't checked it out already:
Numerical explanation of the CM7 automatic backlight settings
I will check when she gets off work. All I did was flash cm7. I didn't mess with light sensor settings.
Ok... I have checked it... Not good. Sample intervals were set to 1s. Even still they were not enabled. Messing with the settings didn't yield any results either. It was still sluggish until hitting it with bright light...
I would search, there are multiple threads around where people have posted their settings, I would try those then tweak it to your liking. Also check out byrong's thread, the man knows his stuff.
Sent from my ADR6300 using XDA App
The automatic brightness sucks on stock as well. Just turn it off. You can't see the screen in bright sunlight no matter what the setting is, and you can see it just fine at 64/255 inside. All the automatic brightness does is give you a headache.
On most Android phones in the Development section you can set the screen to stay on when charging, but that's missing on this one. Any idea where it went, or how I can approximate the same function?
Trying to figure this one out too. "Screen On" in the market allows you to set this as an option, however I seemed to get the loss of signal problem much more frequently when I use this app. I haven't tested extensively so I could be wrong, but I hope this gets added through a custom ROM soon. Listening to Spotify at work is annoying when I have to wake up my phone and unlock each time I want to change tracks.
it was taken off of the galaxy I and II familys because super amoled screens suffer from burn in super easy
urinsane said:
Trying to figure this one out too. "Screen On" in the market allows you to set this as an option, however I seemed to get the loss of signal problem much more frequently when I use this app. I haven't tested extensively so I could be wrong, but I hope this gets added through a custom ROM soon. Listening to Spotify at work is annoying when I have to wake up my phone and unlock each time I want to change tracks.
Click to expand...
Click to collapse
I installed ScreenTimeoutSwitch and I'm pretty happy with it. The most it will do is 240 minutes of on-time, but that's not bad.
Success100 said:
it was taken off of the galaxy I and II familys because super amoled screens suffer from burn in super easy
Click to expand...
Click to collapse
Galaxy S 1 had it, since I'm coming from an Epic and used to having the feature. Hadn't heard about there being an issue before. That's a problem on car rides, when the point is not to have to reach over and turn on the screen. Also, as far as I'm aware their desk docks and car docks override this and keep it on, so that doesn't jive...
I have been using tasker to set this. Just made a profile that set the screen timeout to the highest when plugged in and then back to 30sec when not plugged in.
Success100 said:
it was taken off of the galaxy I and II familys because super amoled screens suffer from burn in super easy
Click to expand...
Click to collapse
+1 QFT
Do not set your screen to stay on unless you want to be annoyed by ghosting in about a month. I suggest you use the 15second screen timer and avoid displaying static images.
My OG Epic had some visible burn-in due to my music player staying dimly lit while driving. I could see the player controls in yellow on any white screen displayed.
walord said:
+1 QFT
Do not set your screen to stay on unless you want to be annoyed by ghosting in about a month. I suggest you use the 15second screen timer and avoid displaying static images.
My OG Epic had some visible burn-in due to my music player staying dimly lit while driving. I could see the player controls in yellow on any white screen displayed.
Click to expand...
Click to collapse
Odd, my OG Epic has no such problem. And a 15-second screen timer makes the phone next to useless. I find anything under a minute incredibly frustrating to use.
Sorry, these descriptions sound like an unusable device. 15 second timeout, and avoid displaying static images? Sounds excessively fragile. Also doesn't jive with anything I've heard about the device or my own experience with the previous one. I feel like people are being overly-cautious here. As well, if this is true, where's the public outcry? Those limitations are unreasonable and should have prevented this from being a popular technology.
TurboFool said:
Odd, my OG Epic has no such problem. And a 15-second screen timer makes the phone next to useless. I find anything under a minute incredibly frustrating to use.
Sorry, these descriptions sound like an unusable device. 15 second timeout, and avoid displaying static images? Sounds excessively fragile. Also doesn't jive with anything I've heard about the device or my own experience with the previous one. I feel like people are being overly-cautious here. As well, if this is true, where's the public outcry? Those limitations are unreasonable and should have prevented this from being a popular technology.
Click to expand...
Click to collapse
well, alot of the galaxy phones had it disabled. For example, I had the Samsung Galaxy S 4G from Tmobile and it did not have this option with the most recent software update.
Screen burn in is an issue on any amoled display. its not that bad, but if you do get it, it shows up on gray and blue images.
Thats the reason its been disabled on alot of them to prevent burn-in.
Now, if you choose to use a hack or app to keep it on just keep in mind that static images on full brightness after about a few minutes will cause ghosting from screen burn in
Success100 said:
well, alot of the galaxy phones had it disabled. For example, I had the Samsung Galaxy S 4G from Tmobile and it did not have this option with the most recent software update.
Screen burn in is an issue on any amoled display. its not that bad, but if you do get it, it shows up on gray and blue images.
Thats the reason its been disabled on alot of them to prevent burn-in.
Now, if you choose to use a hack or app to keep it on just keep in mind that static images on full brightness after about a few minutes will cause ghosting from screen burn in
Click to expand...
Click to collapse
Interesting. Well, I will keep that in mind. I've been doing it for a while now with this one with no problem, and obviously when I'm driving the navigation stays on the whole time. Still, it hasn't been very long. I figure if I have issues by the time we're closing in on a year I can always get a warranty replacement to hold me for the next eight months.
I mainly want screen on while I'm driving to reduce distractions/interactions when changing music tracks. I have the car home app and if I use car home when plugged in, the screen will never turn off.
Sent from my SPH-D710 using xda premium
Gilbot said:
I mainly want screen on while I'm driving to reduce distractions/interactions when changing music tracks. I have the car home app and if I use car home when plugged in, the screen will never turn off.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That's exactly how I got the burn in, using pandora and other music apps while driving allowed the controls to burn into the screen.
Now I have a bluetooth enabled car stereo and I can control pandora and my music player through it so the screen can just stay off.
The burn in issue is due to the fact that the blue led will start dimming before the other two. When that happens, the areas where the blues start dying get discolored since the blue subpixels aren't at 100%. I'm not sure if this was resolved with SAMOLED+, but it's probably still an issue. Again, as long as you don't leave a static image that drives the blue high, it won't be an issue.
Does burn in occur when the screen brightness is %100? Or will it also happen when the brightness its turned all the way down?
I’m usually the first to hit the Update button on anything I own, but after reading about all the bugs that Sony introduced with the firmware updates following .114, I chose not to update mine. I’ve been stuck with a permanent notification in my Notification Shade informing me of the update ever since but that is a small price to pay for a relatively bug-free phone.
Now that .757 is released, is it safe to take the plunge? I am in no particular hurry because I cannot think on anything in KitKat that I particularly want and I know that Sony hasn’t fixed my major issues with the phone anyway. I know the camera isn’t any better in low light, the proximity sensor lag remains and the fast dormancy “feature” that drains up to 40% of the phone’s battery every day is still there.
But if it is as stable as .114, I’d like to be on the latest and greatest again. Your opinion is welcome. Thank you.
Android 4.4 has a general bug with the sound (google problem) but apart from that I can't find anything wrong. Battery seems great. In fact I like it better than the 4.3 rom.
Sent from my D5503 using XDA Free mobile app
I did not get any bug yet.. But if u r not rooted then dont upgrade.. Else it will reduce functionality of ur sd card
Sent from my Xperia Z1 Compact (D5503)
coolkoushik07 said:
I did not get any bug yet.. But if u r not rooted then dont upgrade.. Else it will reduce functionality of ur sd card
Sent from my Xperia Z1 Compact (D5503)
Click to expand...
Click to collapse
Oh yes, I was nothing but shocked when I installed KK - I'm mean is this an open source droid or a locked down fruit phone?
Not to forget to mention that email+exchange permissions is changed (for my company mail which uses ms exchange servers).
PIN requirement is not enough on KK, only password with atleast 4 letters, 2 numbers and 3 signs
Takes a week to unlock your phone unless you root and install an old hacked version of email+exchange.apk+the risk of getting sacked (if they would find out).
Only thing I miss from KK is the Stamina icon but the GEL Xperia Xposed dev is looking into porting it :good:
coolkoushik07 said:
Else it will reduce functionality of ur sd card
Click to expand...
Click to collapse
What does this mean?
Sent from my D5503 using Tapatalk
rkelsen said:
What does this mean?
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
Other apps cant perform operations in sd card in kitkat without root..
Sent from my Xperia Z1 Compact (D5503)
Thanks for the responses, guys. Are there any new features in KitKat, from either Google or Sony, worth updating for?
Google camera.
Sent from my Nexus 7 using Tapatalk
[SIC] said:
Takes a week to unlock your phone unless you root and install an old hacked version of email+exchange.apk+the risk of getting sacked (if they would find out).
Click to expand...
Click to collapse
There is an Xposed mod: http://repo.xposed.info/module/org.flacid.exchangebypass
i've been in kk using RomAur 3.0 and performs great. No bugs, wifi is more stable (but wiht the same cuts and problems of stock 757 rom) than 114.
Sent from my D5503 using Tapatalk
I considered rooting it but the process seems to be far too convoluted for me to attempt. I'm happy with stock.
Sent from my D5503 using Tapatalk
juried said:
Google camera.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Why do you think it is better than Sony’s Camera app? It does not remove the low light issue (where the camera bumps up the ISO much more than it strictly needs to and makes the photos a grainy, unusable mess) and it does not have a manual mode, so you can tackle it yourself. While I like the sparse interface, I have to stick with Sony’s app, because this phone’s camera is useless without manual mode in low light.
Also, on an unrelated note, can any one of you help me get the Personalised Recognition feature back in Google Now? I used to have it in the settings menu but don’t anymore. It disappeared while I was on .114 and I was hoping that updating to .757 would bring it back, but it hasn’t. Do you guys have it?
Sorry to keep bumping my own thread, but this message is just to help out other users who are thinking of installing this update. My recommendation is: go for it!
I had a long list of annoyances with this phone, but I updated to .757 yesterday and it has fixed almost all the issues I had on .114. The major issues that have been addressed:
The Fast Dormancy bug seems to be gone. That Android process that was eating up 40% of my battery life every day no longer shows up on the battery usage screen.
The proximity sensor delay is gone. You bring the phone away from your ear and the display turns on instantly. Magic!
So far, I have no experienced the keyboard skipping issue, so I hope that is taken care of as well.
The only major issue that remains is that the camera is still terrible in low light, thanks to the software that bumps up the ISO needlessly to insane levels. But I can live with that.
I no longer regret buying this thing.
aryayush said:
Sorry to keep bumping my own thread, but this message is just to help out other users who are thinking of installing this update. My recommendation is: go for it!
I had a long list of annoyances with this phone, but I updated to .757 yesterday and it has fixed almost all the issues I had on .114. The major issues that have been addressed:
The Fast Dormancy bug seems to be gone. That Android process that was eating up 40% of my battery life every day no longer shows up on the battery usage screen.
The proximity sensor delay is gone. You bring the phone away from your ear and the display turns on instantly. Magic!
So far, I have no experienced the keyboard skipping issue, so I hope that is taken care of as well.
The only major issue that remains is that the camera is still terrible in low light, thanks to the software that bumps up the ISO needlessly to insane levels. But I can live with that.
I no longer regret buying this thing.
Click to expand...
Click to collapse
I know it's not really a solution, but keep your cam in manual mode and alter the ISO manually. Every phone I've ever used with a camera (iPhones are particularly bad offenders) ALWAYS overcompensate on the ISO in every single environment other than outside on a bright day.
You'll get spectacular improvements if you just get into the habit of entering manual mode, and altering the ISO to the lowest you can get away with (while keeping all the other options on auto) each time you're taking a photo. As far as Im concerned it's far better that way and produces better results than either superior auto or the iPhone's one-button-capture simplicity.
Thanks. I already do that but the default camera app does not make it easy to change the ISO. It takes at least five taps from within the main camera interface to change the ISO and come back. Often, by the time you are done experimenting with the ISO settings, the subject has moved on. Or you end up with a reasonably well lit but blurry shot because the camera UI makes no attempt to inform you of the shutter speed when you take the shot. I have no found any camera apps on the Play Store that make up for these deficiencies either.
aryayush said:
Thanks. I already do that but the default camera app does not make it easy to change the ISO. It takes at least five taps from within the main camera interface to change the ISO and come back. Often, by the time you are done experimenting with the ISO settings, the subject has moved on. Or you end up with a reasonably well lit but blurry shot because the camera UI makes no attempt to inform you of the shutter speed when you take the shot. I have no found any camera apps on the Play Store that make up for these deficiencies either.
Click to expand...
Click to collapse
Yeah fair enough. Good point.
i have a screen issue. same as a problem the video has been upload to youtube. 10 fingers touch the screen not stable.. also issue is when i draw/sketch on the screen. but only happen some times. on a day happen 10 times or more.
i did flash many kind of custom rom.. but the issue still exist.
shaldi said:
i have a screen issue. same as a problem the video has been upload to youtube. 10 fingers touch the screen not stable.. also issue is when i draw/sketch on the screen. but only happen some times. on a day happen 10 times or more.
i did flash many kind of custom rom.. but the issue still exist.
Click to expand...
Click to collapse
What kind of screen issue do u have??
Sent from my Xperia Z1 Compact (D5503)
Good thing for me that went from .114 directly to .757 (i am rooted also)
Camera app have now a 15Meg option
Transparency
Bad things
Conversations.apk (the SMS/MMS app from Sony) is full of bugs. And when I mean full, I really mean it.
Sometimes messages that i already read in the conversations, disappears. All I would see is the blue bubble showing that there's a message, but without the text of the messages. So far this seems to only affect SMS, not MMS.
The color of the bubble when you type, let say blue, and the color of the bubble of the other person talking to you, let say faded blue, often get switch, so reading a conversation might become difficult.
To get the difficulty level higher in following your conversation, sometimes even the side of the screen your bubble is supposed to be attached switch. I mean here, that when you type, your message is next to right side, and your friends reply is next to left side. But now, sometimes you switch side all of a sudden, or worst, sometimes you're on the same side then your interlocutor. Reading SMS with the conversation.apk is totally hardcore now.
Another thing that really piss be off, but I do not know if this is from 757 or if it was already in 114, since I did not use this app in 114, it is the Email software. The Email software stacks/bundles all the messages with the same subjet title when someone reply or transfer your email. (like Gmail does in a browser by default). I really hate this functionality, I prefer to just scroll down to see the previous message if I need to. Unfortunately for me, there's no option in the app to unstack/ungroup emails messages.
Another problem I have with the Email app, this is a bug, because it wasn't doing this in previous build, it is that the Small yellow icon on the icon that tells you that there's 1,2,3 what ever number unread messages, and also the Mail icon in the notification bar, does not go away upon opening the email message. You need to actually press the back button to exit the new messages for it to be marked as read, so that the icon and the notification bar adjust. So if you open an email messages, press the home button to do whatever else, then look back at your notification bar or email icon, you'll think you got new email message, but in fact, it's the same one that is still marked as unread, even if you did open it and read it...
Email and SMS/MMS apps are what I use the most on my phone, I've been using them since I got my first Xperia X10 Mini Pro that was running 1.6, but I've never had that much trouble, they have so many annoying bugs right now. The only problem I've had was the notification LED bug on my Xperia Mini Pro running ICS.
Another thing that I hate, but this is not from 757, but from JellyBean. I come from ICS, and what I hate the most, is the damn white background of all apps. It use more battery and it hurts my eyes in low light room even with minimum brightness. I just wish a stable CyanogenMod with black background pops like in ICS so that I can install it. I've seen some topic about it over here, but they only explain how to uncompile and recompile, too much complicated, I'd rather simply have a package I could simply install with CWM.
EDIT: Oh yeah, I forgot to mention another bug. Somehow the auto-rotate of the screen stopped working twice in the last 2 weeks. Each time I need to go in the accessibility options and uncheck/recheck the auto-rotate option to fix this. (grrr need to wait 5 minutes to be able to edit my msg #xdaforumantispam)
This phone has an LED-backlit LCD display. It does not affect the phone's battery life whether the screen is white or black. Not enough to make a practical difference, in any case.
Sent from my D5503 using Tapatalk
Have any other Z5 premium users noticed that sometimes when you wake up the screen it looks super washed out almost LG G3 esque for a second or 2 then it goes back to looking normal?
Just wondering if there's an explanation, it's a common thing or i have a faulty handset.
Thanks
Darkwun said:
Have any other Z5 premium users noticed that sometimes when you wake up the screen it looks super washed out almost LG G3 esque for a second or 2 then it goes back to looking normal?
Just wondering if there's an explanation, it's a common thing or i have a faulty handset.
Thanks
Click to expand...
Click to collapse
Don't think it's faulty. Very noticable to me on very dark screens. If you turn off Adaptive Brightness in settings this doesn't happen. It's just trying to adjust the screen to a proper brightness.
I have had the same issue.
Normally if I wake the phone up directly into an app that had a dark background i can easily see this. I find that pressing the recent apps key, selecting another app and then going back into the washed out app helps to remedy the problem if it does not sort itself out.
This happens for me as well. Note this also happened on my z3. Im not all that worried about it. The washed out display is usually sorted within a few seconds. If it bothers you that much, turning off adaptive brightness get rid of the issue as mentioned earlier.
I've taken to using Lux Auto, it resolved the issue.
They talked about it on the Sony forums, there's a bug in the adaptive brightness and Sony said that they are fixing it for the 6.0 update
Sent from my E6853 using Tapatalk
Always notice it when I leave my keyboard open and lock screen. When I unlock it later the keyboard looks all washed out then fades back to normal. Never bothered me though on this or previous Sony phones
Sent from my E6853 using Tapatalk
Cheers for the answers guess i'll wait for this 6.0 update to drop to see if it fixes it
Darkwun said:
Cheers for the answers guess i'll wait for this 6.0 update to drop to see if it fixes it
Click to expand...
Click to collapse
Good Luck
We're on 7.0 and it is still not working. My screen becomes the dimmest in sunlight or bright days, that's exactly when I need it the brightest and it becomes dim - Sonny ? or Funny !
I am tired of this phone.
May 5th.
So when I am tired I am trying the most crazy things....
Installed LUX Auto Brightness - 48 hours and not a single problem.
https://play.google.com/store/apps/details?id=com.vito.lux
I organized the application a bit, Min brightness 40% , Max - 100% , link your 0 lux ambient to 60% brightness and use other good stuff.
This application controls the Z5 Brightness so that it gives me what need.
Of course my Z5 adaptive brightness is OFF.
I can not explain how this does it, even me being an EE, but still Job is done.
This was very frustrating so you can understand my excitement.