Develop Bugs

Is 14.3.A.0.757 as bug-free and stable as .114?

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

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

Touchwiz and battery problems

Hi,
I bought Tab S 8.4 recently (3 weeks ago).
I face two issues and I appreciate your help..
1- Toucwiz: it happens frequently after I restart my tablet to find the error message (Unfortunately, Touchwiz stopped working). When I press OK, the screen blanks and starts working fine. I tried resetting the tablet to factory settings, clearing cache, clearing Touchwiz application setting.
The problem goes for some time and comes back. it doesn't really impact the tablet function but it is a kind of irritating.
2- Battery drains: I used to have ipad mini, the battery life was about 5 to 6 days.
For the Tab S, it is maximum three days. taking into consideration that I am using the tablet for emails, browsing, and rarely lite games.
Please, let me know if you face these problems and if you know the fix.
Thanks,

a_k_gano said:
Hi,
I bought Tab S 8.4 recently (3 weeks ago).
I face two issues and I appreciate your help..
1- Toucwiz: it happens frequently after I restart my tablet to find the error message (Unfortunately, Touchwiz stopped working). When I press OK, the screen blanks and starts working fine. I tried resetting the tablet to factory settings, clearing cache, clearing Touchwiz application setting.
The problem goes for some time and comes back. it doesn't really impact the tablet function but it is a kind of irritating.
2- Battery drains: I used to have ipad mini, the battery life was about 5 to 6 days.
For the Tab S, it is maximum three days. taking into consideration that I am using the tablet for emails, browsing, and rarely lite games.
Please, let me know if you face these problems and if you know the fix.
Thanks,
Click to expand...
Click to collapse
1. Re-flash your device firmware with Odin. Many guides about on its use. Check sammobile.com or samsung-updates.com
2. The browsing time has been shown to be less than SOME other tablets but media play exceeding most others (including mini) of the same form factor. Don't know what users expect for such a thin device device with a very high resolution. There are far more pixels to push
There is also power saving mode and ultra power saving mode. You could also use auto brightness with lower setting.

As your coming from an Apple device here are some info on best battery saving practices for Android :
7 Quick Tips To Extend Battery Life on Android 4.4 Kitkat
http://www.idroidspace.com/best-tips-to-extend-battery-life-on-android-4-4-kitkat-devices/
Specifically for Tab S:
- (I don't use this one as to me it reduces the value of my tablet) : "Select adaptive display off and use basic color better battery life but sacrifice some color". This suggestion came at the beginning of August before at least one update which may have negated it's value.
- Settings:
- Increase the time between services being synced (GMail, Calender... Etc)
- Turn off syncing for any service you don't use
- Turn off Bluetooth if your not using it
- Turn off WiFi scanning once you have added your WiFi access point(s)
- uncheck WiFi remaining alive when tablet is asleep (sorry forgot the specific setting name)
- Anything you can tolerate that reduces screen brightness.
- Turn off auto brightness and control it manually
- Reduce the auto brightness value assuming you still want auto brightness
If that is still not enough then you can install a battery app which tracks "wakelocks" (apps that keep your app awake even when it is not being used). After analyzing that info you can uninstall the worst offenders. Sometimes the worst ones are part of the system or an essential app so you must put up with the drain. See this XDA post for a good battery analysing app which is free for XDA members.
http://forum.xda-developers.com/showpost.php?p=15869886&postcount=2
Likely the 1st link to the 7 tips article will give your the best bang for the buck.
Good luck
Sent from my Nexus 10 using XDA Premium HD app

The weird thing is that the Touchwiz error appears only at the restart. Then the tablet continues working fine.
it is less probable to happen when I restart the tablet after it is shut down, and more probable to happen when I restart it by command.
It is not stopping me from using the tablet, but it is some how irritating.

a_k_gano said:
The weird thing is that the Touchwiz error appears only at the restart. Then the tablet continues working fine.
it is less probable to happen when I restart the tablet after it is shut down, and more probable to happen when I restart it by command.
It is not stopping me from using the tablet, but it is some how irritating.
Click to expand...
Click to collapse
So you didn't bother to re-flash ?

UpInTheAir said:
So you didn't bother to re-flash ?
Click to expand...
Click to collapse
Not exactly, ... I downloaded the SW and planning to do it... was just asking if it really deserves?
one silly question... can it be a HW issue?
Thanks,

a_k_gano said:
Not exactly, ... I downloaded the SW and planning to do it... was just asking if it really deserves?
one silly question... can it be a HW issue?
Thanks,
Click to expand...
Click to collapse
Not a silly question.
A lot will be cleared up if you go ahead. You're data should be OK, but always recommend to save it off device.

UpInTheAir said:
Not a silly question.
A lot will be cleared up if you go ahead. You're data should be OK, but always recommend to save it off device.
Click to expand...
Click to collapse
I reflashed the SW.
so far so good.. will keep you updated.
Thanks,

a_k_gano said:
I reflashed the SW.
so far so good.. will keep you updated.
Thanks,
Click to expand...
Click to collapse
Problem appeared again... looks like it is related to some application.
I tried the safe mode and it works fine every time I restart the tablet in safe mode.
I downloaded Nova advanced launcher and it works fine so far...

a_k_gano said:
Problem appeared again... looks like it is related to some application.
I tried the safe mode and it works fine every time I restart the tablet in safe mode.
I downloaded Nova advanced launcher and it works fine so far...
Click to expand...
Click to collapse
You just need to remember what you did between then and now and narrow down the cause. ....

UpInTheAir said:
You just need to remember what you did between then and now and narrow down the cause. ....
Click to expand...
Click to collapse
I found the trigger ... Or I think I did
I cleared the Touchwiz data and cache .. so it went to the default configuration. I then started adding my widgets and shortcuts one by one.
I figured out that the Touchwiz fault happens when I add a short cut of an application installed on the microSD card.
I moved all the applications from the microSD to the internal memory and now Touchwiz works fine.
Now going to the microSD. The microSD I have is Transcend cat 10. It should be quite fast, and it is actually fast (R/W). However, I recall some posts regarding Transcend in-compatibility with new Samsung devices.
I have Galaxy S5 as well... same Transcend type and works fine.... BUT ... There is a Samsung application called User's digest for Samsung (or you can find it in the name of Vitamin's for Samsung).. It has a feature to place some tests to the handset. Both Galaxy S5 and Galaxy Tab S show the microSD card test result as "Disconnected"! ... I didn't care that much on the S5 as it didn't cause any problem, but now I started to care after what happened with the Tab S.
I ordered Samsung 32GB cat 10 microSD... should arrive in a week... will let you know about my experience.

It's confirmed now the touchwiz problem while starting the tablet is triggered by microsd.
The transcend I was using was fake. I am using an original one now and I can sense the enhancement in the read speed, as well as no touchwiz problem anymore.
Thanks,

How do I reboot in safe mode in galaxy tab s t705?
Thanks

Screen sometimes slow to turn on, occasionally freezes when attempting to unlock.

I've only noticed this since running the August security updated and its happened across three ROMs so far (Screwed, Pure Nexus, LOS (No gapps)). Sometimes the screen takes for ever to power up. Once it is up the lock screens responsiveness varies greatly. Not always in the same instance as the screen issue but when unlocking the device it will momentarily freeze. Sometimes locking itself again..
Curious if anyone has seen anything similar.

How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.

jhs39 said:
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
Click to expand...
Click to collapse
I'm restoring from tibu.

pcriz said:
I'm restoring from tibu.
Click to expand...
Click to collapse
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.

jhs39 said:
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
Click to expand...
Click to collapse
It's happened without any apps installed as well. I haven't tried safe mode yet no

are you using immersive mode?

diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.

pcriz said:
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
Click to expand...
Click to collapse
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug

diabl0w said:
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
Click to expand...
Click to collapse
Yeah that would make sense if you are seeing the same thing. I may jump back to a known good build and see what happens

I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.

pTeronaut said:
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
Click to expand...
Click to collapse
Thank you, I'll try that!

diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?

p1r473 said:
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
Click to expand...
Click to collapse
Check this thread. ?
https://forum.xda-developers.com/pi...e-problems-t3666479/post73629247#post73629247

My Xiaomi Mi 10T Lite goes black after using for while after Android 11 update, is this fixable or a bug that I should report?

I got a Xiaomi Mi 10T Lite and it's running on Android 11 since some weeks.
But after it updated to Android 11, it sometimes goes black when I'm using it for a while and I've to unlock it all the time.
It goes black and then returns to the lock screen.
Does anybody else also have this problem and is this a bug that I should report?
I've also a logcat, I think that it will be useful.
Logcat link: https://drive.google.com/file/d/16aGo7nzgde6bN9NMU-yavc9IZNT_FPU6/view?usp=drivesdk

Googole said:
I got a Xiaomi Mi 10T Lite and it's running on Android 11 since some weeks.
But after it updated to Android 11, it sometimes locks itself when I'm using it and In have to unlock it all the time.
It goes black and then returns to the lock screen.
Does anybody else also have this problem and is this a bug that I should report?
Click to expand...
Click to collapse
Sounds like you have something running that is causing a soft reboot of your phone
I've been using android 11 on this device for a while and not had any such issues

Mine is going back to Xiaomi today, mine keeps going into a boot loop and lasts for 3 hours or so sometimes before it sorts its self out, if I reboot it it just carry's on into boot loop, it often starts this when it is charging, at the moment the phone is unusable, so it is going back for them to check out.

TheFixItMan said:
Sounds like you have something running that is causing a soft reboot of your phone
I've been using android 11 on this device for a while and not had any such issues
Click to expand...
Click to collapse
I really don't know what causes it.

Googole said:
I really don't know what causes it.
Click to expand...
Click to collapse
Is this problem fixable?

Googole said:
Is this problem fixable?
Click to expand...
Click to collapse
Quick fix would be to factory reset your phone
Long fix would be to do an Adb logcat and record the exact moment your device soft reboots and see what it is but even then it maybe hard to work out what is causing it

TheFixItMan said:
Quick fix would be to factory reset your phone
Long fix would be to do an Adb logcat and record the exact moment your device soft reboots and see what it is but even then it maybe hard to work out what is causing it
Click to expand...
Click to collapse
I have done several factory resets, it did not improve my phone and the ADB logcat is not something I know about so I have now sent it back, I love the phone but I can't deal with the continued frustration it causes me, I am happy if they fix the issue and send it back to me, if not I would probably purchase another one.
My wife also has this phone (I purchased 2 at the same time) she does not have any issue with hers and we have pretty mush the same Apps and everything on the phones, I have even used her charger to see if that's causing some of the issue..
I will keep you all informed of the out come.

I've readed on Reddit that people experience crashes on their Xiaomi all the time.
So I've updated Webview and I'll let you know if the problem is solved.

Googole said:
I've readed on Reddit that people experience crashes on their Xiaomi all the time.
So I've updated Webview and I'll let you know if the problem is solved.
Click to expand...
Click to collapse
There was a bug yesterday that caused Google apps (and others that use Web view) to force close due to a bug in webview. This only effected a specific version of webview and was fixed in a few hours. I didn't notice any such issues on my device but I was using latest beta version.
As long as your webview and chrome is up to date your apps will function correctly (in regards to webview)

I tried that, but that didn't resolve the issue.
I have also done a factory reset but the bug still appears.
I know for sure that there is nothing wrong with my phone, so it must be a MIUI side issue and I'll report that bug to them.
So that means the topic is closed.
Thank you for your help!

Googole said:
I tried that, but that didn't resolve the issue.
I have also done a factory reset but the bug still appears.
I know for sure that there is nothing wrong with my phone, so it must be a MIUI side issue and I'll report that bug to them.
So that means the topic is closed.
Thank you for your help!
Click to expand...
Click to collapse
If you have done a factory reset and the problem still exists & you haven't installed any other app which could cause a soft reboot without any logs you will never know why it's doing it.
You could also have a hardware fault
It's very unlikely related to MIUI otherwise everyone (or a very high % of users) would also have the same issue and they are not. It's related to your device.
There's only two main bugs with MIUI android 11 on this device
1 - 3rd party launchers gestures & an icon of the app you're using appearing in the top left of screen when closing an app which has a work around of launching the system launcher then switching to 3rd party launcher.
2 - notification layout is incorrect with text too far aligned to the left. This doesn't effect functionality but looks wrong & could slightly crop off the far left of text.

I've done some research, asked the same question at more forums and tried some things and I'm convinced that this is a bug because of these reasons:
- My phone worked perfectly fine on Android 10
- I don't think there is a app that causes this bug because they worked perfectly fine on Android 10.
- There is no chance that there is anything wrong with my device because I'm really careful with it and I didn't done dangerous things for my phone
I'll report it to Xiaomi through Services and Feedback

Ok, if you read my message #7 above I explain about my phone going into reboot and boot looping etc, I have sent it back to Xiaomi on Tuesday, and this morning I have tracked the repair, They Say:
1. Fault category: Electrical - Other
2. Awaiting Component
So my phone obviously has a HARDWARE fault. I am pleased with the speed Xiaomi are dealing with this - so far.

See the OP

Googole said:
See the OP
Click to expand...
Click to collapse
Your logcat is not accessible to the public via that link and I hope the logcat was recorded at the exact time the issue happened

TheFixItMan said:
Your logcat is not accessible to the public via that link and I hope the logcat was recorded at the exact time the issue happened
Click to expand...
Click to collapse
I've changed the settings now, it should be accessible for everyone.
It wasn't recorded at the exact
moment the issue has happened but I really hope it could be useful because it recorded the crashed that happened earlier this day.

Googole said:
I've changed the settings now, it should be accessible for everyone.
It wasn't recorded at the exact
moment the issue has happened but I really hope it could be useful because it recorded the crashed that happened earlier this day.
Click to expand...
Click to collapse
Do you have a messaging widget on your home screen?
Can you remove all widgets from your home screen and then see if your phone continues to restart.
Looks like something is happening when you receive a message and the widget is failing to update
If it's a 3rd party app or launcher with the widget uninstall it

I don't have a widget, I use the default launcher because I can't use Smart Launcher 5 (which I used on Android 10) with gestures.
I use the default time and weather widget from Xiaomi which is linked to the default Weather and Clock app.
I've removed all my widgets from the home screen, I'll let you know if that works.

Googole said:
I don't have a widget, I use the default launcher because I can't use Smart Launcher 5 (which I used on Android 10) with gestures.
I use the default time and weather widget from Xiaomi which is linked to the default Weather and Clock app.
Click to expand...
Click to collapse
That is really the only error in your logcat (it also doesn't seem a complete logcat and only a part of one)
As mentioned the logcat needs to be recording at the exact moment the restart happens.
Other things you can try is clearing data of the following
Google services framework
Google
Google play services

TheFixItMan said:
That is really the only error in your logcat (it also doesn't seem a complete logcat and only a part of one)
As mentioned the logcat needs to be recording at the exact moment the restart happens.
Other things you can try is clearing data of the following
Google services framework
Google
Google play services
Click to expand...
Click to collapse
I guess I'll try to install Smart Launcher then, and then I'll try the things you advised me.
If the problem is still there, I'll make a new logcat.