Related
According to the thread on the Official Sony Support Community by Lemon and updated by me, Here a thread trying to list all troubles on the 4.2.2 Official Update.
If you're using a custom ROM do not list your problem here because that can be specifically a problem on your ROM.
Gracenote Update
I had approxamitely 3200 songs in my library. I attempted to update the artwork and music info using the integrated 'Download music info' option (powered by Gracenote). This repeatedly fails and crashes, and somehow managed to wipe approximitely 40 artists from my library of 150 artists. I now only have 108 artists, and have lost a lot of music, which I had paid for or ripped from CDs. I now have to do rip these all over again, and I've also wasted a considerable amount of money on MP3s which have now been wiped by shoddy software!!! I just tried to update some more files, just this moment, and while it managed to update beyond 82/800 tracks, it then failed and gave me a 'Network Error' and advised that 2 tracks had been updated - despite that it had already attempted to update more than 82 tracks!!! It's massively buggy. Not going to use it anymore in fear that it wipes more of my library.
Walkman App
Sometimes shows '-1' artists in library. When tapping into the Artist list and coming back out again, this updates and shows the correct number of artists. Why would it EVER show that I have '-1' artists in my library?!?
Android Become Slow
I've had it after the update, if you feel that your android is very slow since the update, just go to the settings, select applications and "desactivate" some useless app that eats memory, be carefull what you're desactivating, you don't need to be rooted for doing that, that helped in my case.
Earpods/Headphones Compatibility
My previous handset was the 2011 'flagship' Xperia Arc. The stock headphones which came with this handset are of a much better build quality (and tangle a lot less easily) than the stock headphones which came with the Xperia Z. However, upon connecting the Xperia Arc headphones to the Xperia Z, I get a message saying 'Headset not supported. Use another headset or visit the Sony Mobile support site for more information'.
Many earpods/headphone seems to not be supported anymore under this update, Sony needs to fix that quickly that's really annoying.
XDA Threads : http://forum.xda-developers.com/showthread.php?t=2340877
http://forum.xda-developers.com/showthread.php?t=2355500
MBS-100
Everytime I connect over Bluetooth to my MBS-100 (first generation) my WiFi crashes after about 4 minutes. Every time. This does NOT happen with my MBS-200. Seems Sony haven't put enough effort in testing support for their older devices/products, this is clearly also the case above with the stock Xperia Arc headphones.
SD Card bug surfacing
The Sony Xperia Z is suffering from a persistent hardware failure, which is inserted SD cards unusable. Most of time we need to reformat/restore it and in worst cases the SDCard is dead and you need to buy a new one.
I have this as well that asks me many times to check and verify my SDCARD when i use the MSC connection, if i don't do it i can't copy files on it.
XDA thread : http://forum.xda-developers.com/showthread.php?t=2352245
Photo Album uploading with Facebook for Xperia
Tried uploading 31 pictures using the integrated share to Facebook for Xperia feature last night, on a FAST connection (Download Speed: 44.9MBPS / Upload Speed: 7.4MBPS) - 1 picture uploaded, service failed. Tried again, 2 pictures uploaded, service failed. Tried again, notification said 'Uploading pictures for about 18 minutes, before timing out and failing without uploading any pictures. Any pictures that did upload, did not upload in order either. After repeatedly attempting this about 30/40 times, I managed to upload about 17 of the 31 pictures, and had to connect by USB in order to do the rest. Seems like this feature was slapped on without any REAL testing by Sony.
Lockscreen Bypass
It is possible to bypass the lockscreen by typing '*#*#7378423#*#*' and doing an NFC test in the Service Tests menu (http://www.youtube.com/watch?v=LLq1gxIt5YQ) - this renders the handset COMPLETELY UNSECURE.
XDA Thread http://forum.xda-developers.com/showthread.php?t=2206033
Socialife
Never updates automatically. Sometimes updates manually. Sometimes doesn't. Just tested manually refreshing this moment, today being March 26th, and nothing is showing beyond the afternoon of March 25th.
Stamina Mode / Battery Life
When first experiencing issues with my handset, a Repair was advised by support staff on the forum here, and official Sony Customer Support Staff. Following this repair, by battery life at 100% showed 4 DAYS AND 12 HOURS. A week later, on 100%, my battery life dropped to 2 DAYS AND 8 HOURS. Another week later, on 100%, my battery life is now showing 1 DAY AND 1 HOUR. All of these figures are with Stamina mode turned on. I haven't added anything to the handset to affect performance, it's simply degrading of it's own accord. Which makes me wonder why the support staff repeatedly assure us on these forums that 'the battery life will improve after a few charging cycles' - this is not the case, and there is CLEARLY a Power Management issue, which needs to be resolved.
LED Notification
Fortunately, I am not experiencing the LED issue that others have been. But it should be listed as others have been experiencing it.
Sleep of Death
Fortunately, I am not experiencing this issue. But it should be listed as others have been experiencing it, special mention for people who hard-bricked their phone, do not include that problem.
WiFi Signal Issues
Fortunately again, I am not experiencing any major WiFi issues. However, when uploading photos using Facebook for Xperia last night, it knocked off my WiFi twice for no reason. And I've also documented my WiFi issues in combination with Bluetooth to MBS-100 above.
Accessories
The 2011 flagship Xperia Arc came with quality headphones, a charger, and a mini-HDMI to HDMI cable for outputting to HDTVs. The 2013 flagship Xperia Z came with cheaper headphones, a charger and NO cable for outputting to my HDTV. I expected this to be included in the package, given the lofty pricetag, but now I realise I must go and buy an 'MHL Cable' - something I didn't even know existed until after I purchased the device. Thank you for not including this cable Sony.
If anyone has any further legitimate bugs/issues to add to the list above, let me know and I'll keep the OP updated.
If you know a fix i'll add a green comment.
Severity color :
Low
Medium
Critical
Fixed
Hi.
I'm on .423 and I don't seem to have the lockscreen bug.
In fact, I cannot dial any MMI codes using the emergency dialer.
On a side note, why is this tagged as [HELP THREAD]? There's already the help thread that I've started under stickies in the Q&A Section.
kgs1992 said:
Hi.
I'm on .423 and I don't seem to have the lockscreen bug.
In fact, I cannot dial any MMI codes using the emergency dialer.
On a side note, why is this tagged as [HELP THREAD]? There's already the help thread that I've started under stickies in the Q&A Section.
Click to expand...
Click to collapse
You're lucky, anyway that's interesting, what kind of ROM do you use?
For the thread i've edited with [BUGS LIST] it was just for being easily found for people, if you have a better idea for my thread i'm open to any suggestions.
QualQuek said:
You're lucky, anyway that's interesting, what kind of ROM do you use?
For the thread i've edited with [BUGS LIST] it was just for being easily found for people, if you have a better idea for my thread i'm open to any suggestions.
Click to expand...
Click to collapse
Stock ROM for C6603 from here.
[BUGS LIST] seems appropriate enough?
EDIT: There's also this SD Card bug surfacing. I have this problem too.
A bit short on patience right now, so haven't tried fixing it yet. You could add this to the list.
Thanks a lot, SDCard bug surfacing added to the list with critical severity.
musick oluarb
I'm Lemon, and these bugs have nothing to do with 4.2.2
I posted this in March, about 10 day's after the handset was launched, listing all the issues I found in the original 4.1 firmware, it's been updated a few times since.
With 4.2.2 I've only noticed a weird support issue where the software completely wiped me sd card of its own accord. I've lost ****loads of stuff as a result. It's only happened once though.
Still noticing the Walkman skipping during playback...
Some Home screen stuttering, nothing out of the ordinary for Sony.
Otherwise, 4.2.2 is much improved.
how are the lack of accessories, notably a mhl cable part of the bugs/issues with 4.2.2 ?
I don't know how to describe it wxactly but since the update (2 days ago), my phone has became super slow.
On 4.1 it was great never experienced any lag.. but now it feels like I'm holding my tired old phone again..
It goes from opening apps, through unsmoothly scrolling and floating around, to the lockscreen it self which can take about 3-8 seconds to show up image from black after pressinv power button to wake him up..
Also for unlocking, sliding up to move from lock screen to home screen can be laggy, stucky, and takes time...
Furthermore, WiFi signal (or atleast the icon showing) is poor and barely reaching my router when I'm 3 meters away..
As for not getting anything exciting from the update, or any changes, cool features from stock 4.2 (hmm som1 said notification toggles?) , I'm pretty disappointed, I would return back if that possible
Sent from my C6603 using xda premium
mcjordan92 said:
I don't know how to describe it wxactly but since the update (2 days ago), my phone has became super slow.
On 4.1 it was great never experienced any lag.. but now it feels like I'm holding my tired old phone again..
It goes from opening apps, through unsmoothly scrolling and floating around, to the lockscreen it self which can take about 3-8 seconds to show up image from black after pressinv power button to wake him up..
Also for unlocking, sliding up to move from lock screen to home screen can be laggy, stucky, and takes time...
Furthermore, WiFi signal (or atleast the icon showing) is poor and barely reaching my router when I'm 3 meters away..
As for not getting anything exciting from the update, or any changes, cool features from stock 4.2 (hmm som1 said notification toggles?) , I'm pretty disappointed, I would return back if that possible
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Yep i've seen many people complaigning about that too, btw you can disable some useless app on settings => applications, select one and choose "desactivate" that's helepd so much for me.
what in the world.. and .423 just came to my phone updates and it's now stuck in the notification bar but seeing all these makes me doesn't want to update it anymore ._.
From last night i am facing a problem where when I connect my headset (samsung) to my xperia z1 it displays the error *Headset not supported. Use another headset or visit the Sony Mobile support site for more information.*
I used to use this headset everyday but unfortunately it had stopped working.
Further, if i use any other headset, it displays the same message.
I have not updated my phone nor have i installed any mod or app.
Can anyone tell me the fix please?
Thank you!!
Dear all,
it is my first try to run cyanogenmod (10.1 Rel 7) on my SGS+. But when using it, I immediately found plenty of issues:
- Navigation is only partially working. After a while the maps starts jumping around and dark semi transparent overlay sections appear so that one cannot see the full map. In the forum I found the hint to deactivate Dithering. Done. Only little improvement.
- Alarm clock is not working when the phone is turned off.
- Screen goes off after dialing a number (workaround: lift phone to the ear and lower it back down -> screen is on again).
- No FM radio app (in comparison to the stock rom).
- Skype video is still upside down (as with stock rom).
My colleagues were very enthusiastic about cyanogen mod. In contrast, I haven't really detected the advantages. Are the developpers still working on the issues? Is there anything I can do to support you guys?
To answer your queries:
-Navigation- use the bug reporting method on the CM10.1 forums and submit it as a bug report either in the S CM10.1 thread or on JIRA. More details are given in the CM10.1 thread OP.
-This feature doesn't work even on stock. Its not a bug, and its not just CM10.1. MIUI allows this apparently however.
-This is normal, not a bug either. When you call someone the screen goes off because you're going to lift it to your ear anyway. The 'workaround' is actually the proximity sensor, and a similar thing happens on stock roms. The only solution to this is to press a button when the screen initially turns off.
-FM Radio isn't included in CM builds by default, as the API needed for it needs some intense changes made to it. There's Spirit FM if you want to run the risk. Check out the thread for more information.
-Skype on CM10.x is a known issue
Try CM10.2 and see if that helps the first issue, if not, report it using the methods in the CM threads. Otherwise everything else is as normal/known.
Sent from my GT-P7510 using Tapatalk HD
Irrespective of a few bugs there are definitely a number of advantages to using CM.
Have you noticed how smooth CM10.1 is? For me it's smoother than stock. Definitely a plus.
The pre-installed applications are more polished/work better and you actually have control over them. Don't like one? You can remove it. Unlike stock where you are stuck with a lot of junk (unless you have rooted your phone).
Bugfixes! We're no longer stuck with a 2 year old version of an OS for which we don't receive any bugfixes.
Customizability. CM gives you a lot more features to have your phone just the way you want it.
Overclocking and undervolting.
Not everyone had this problem, but my phone took > 5 minutes to get a GPS fix on stock. It takes < 10 seconds on CM.
And that's just what I came up with in a few minutes. Yes, there will be a few bugs and features which you think are weird (like the screen turning off when you make a call) but you'll find that on any piece of software. If you personally feel CM is a downgrade then it's your right to think so and go back to stock ROM. That doesn't mean the average xda-user is going to agree with you though.
(I think there are also a few ROMs based on the stock 2.3.6 versions, but since I've never used them I wouldn't know which ones are worth trying.)
Hi,
I have a Z3 Compact running pre-rooted Android 5.1.1 Lollipop. I got a notification about software update that i can't dismiss. i don't know if i should upgrade or not so force stopped the software update app.
What is your opinion about Marshmallow?
Are there any bugs?
Are there new features added and some features removed?
Is it worth upgrading to Mashmallow or should i keep Lollipop?
sorry i can't upgrade without user reviews
You can dismiss the update notification if you want (disable it).
MM has officially been out for only a few weeks and consequently is still full of bugs and problems.
The threads are full of the cries for help from the MM rom jumpers, oh the pain of being an early adopter.
Give it another month, by then it'll fixed.
Didgesteve said:
You can dismiss the update notification if you want (disable it).
MM has officially been out for only a few weeks and consequently is still full of bugs and problems.
The threads are full of the cries for help from the MM rom jumpers, oh the pain of being an early adopter.
Give it another month, by then it'll fixed.
Click to expand...
Click to collapse
How do you disable the notification? For which app do I have to do that?
Dont update to Mm.. There is some feature that missed..like battery stamina/ultra stamina..and also the battery drain fast..
Im a z3 compact Mm user
+1 for don't do it (now)
For me I will stay for not specified time at LP (mainly because of custom kernel).
Didgesteve said:
You can dismiss the update notification if you want (disable it).
MM has officially been out for only a few weeks and consequently is still full of bugs and problems.
The threads are full of the cries for help from the MM rom jumpers, oh the pain of being an early adopter.
Give it another month, by then it'll fixed.
Click to expand...
Click to collapse
Thanks. Is it safe to disable software update app?
i don't want unexpected bugs happen or boot loop
evildog1 said:
Thanks. Is it safe to disable software update app?
i don't want unexpected bugs happen or boot loop
Click to expand...
Click to collapse
The next time you see a notification, hold your finger on the notification and the bar will turn black and you will see an information 'i' on the right side, press this.
This will bring up the notification option.
Alternatively, go to settings\apps\scroll to the right until >all apps > 'update centre'
Then - force stop, untick notifications, clear cache/data
You won't get any more notifications about MM and no this won't harm or damage your phone in any way. Your phone will work fine on 5.1 for years and years, it doesn't need MM
Didgesteve said:
The next time you see a notification, hold your finger on the notification and the bar will turn black and you will see an information 'i' on the right side, press this.
This will bring up the notification option.
Alternatively, go to settings\apps\scroll to the right until >all apps > 'update centre'
Then - force stop, untick notifications, clear cache/data
You won't get any more notifications about MM and no this won't harm or damage your phone in any way. Your phone will work fine on 5.1 for years and years, it doesn't need MM
Click to expand...
Click to collapse
Ok i just uninstall updates, force stop, and clear data, but i could not disable the notification.
evildog1 said:
Ok i just uninstall updates, force stop, and clear data, but i could not disable the notification.
Click to expand...
Click to collapse
If you have root, then go to the market and install ES Explorer
Open it, go to menu, look at the bottom 'tools'.
tick 'root explorer'
Go back to the top of the menu and find "home/device/system/app"
Look for "com.sonyericsson.updatecenter.apk"
Make a copy and save it somewhere, like Downloads.
Then delete the original in system/app.
If there is a problem you can always put the copy back in the folder, otherwise you will never get another update message again:good:
Didgesteve said:
If you have root, then go to the market and install ES Explorer
Open it, go to menu, look at the bottom 'tools'.
tick 'root explorer'
Go back to the top of the menu and find "home/device/system/app"
Look for "com.sonyericsson.updatecenter.apk"
Make a copy and save it somewhere, like Downloads.
Then delete the original in system/app.
If there is a problem you can always put the copy back in the folder, otherwise you will never get another update message again:good:
Click to expand...
Click to collapse
Thanks. I just froze it using Titanium Backup
and i'm using X-plore with dual pane
Just like when Sony released 5.0 Lollipop, it was full of bugs and the battery life sucked. It wasn't until 5.1 came out that we finally got a usable ROM. Expect more of the same with MM. Wait until 6.1 is released before upgrading. Especially those who are not rooted. There's no fixes and no turning back for those users.
Sent from the only flagship device that can fit in my hand... Sony Experia Z3 Compact
Sorry to bring back an old thread but I just bought this phone secondhand and its on 5.1 and have received the update notification. Have the bugs that are in the above comments been fixed in 6.1 or is it still not worth upgrading to Marshmallow?
warzinak said:
Sorry to bring back an old thread but I just bought this phone secondhand and its on 5.1 and have received the update notification. Have the bugs that are in the above comments been fixed in 6.1 or is it still not worth upgrading to Marshmallow?
Click to expand...
Click to collapse
For me, the most horrible is the delay when opening apps:
Lag manifests on this way: in response to launching app (Dialer let say) "window"/app pops up immediately but is is empty/white and only after a sec/two content shows up (for Dialer recent call list, favourites/frequent contacts, search). Minimizing app and immediately opening again is ok (it is in cache, background, memory), instant content shows up. But if I launch another app after minimizing dialer and then start dialer again - lag in Dialer is there. As if somehow Dialer is killed in background and need to relaunch again from the start (even full relaunch should not take that long anyway). Same as killing it in recent activities. All other stock apps behave this way. It is really annoying to see such a powerfull phone lags in this basic stock apps, as this doesn't happen on previous android versions (4.4.4, 5.0.2 or 5.1.1).
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Fictional Reality said:
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Click to expand...
Click to collapse
Indeed, I bought an iPad mini, downgraded z3c to KK and life is good.
I use my phone now for what phones are meant to - calling, occasional e-mail, messaging, weather, etc. Battery life is 4..5 days. The car bluetooth shows addressbook again (did not work with LP, MM).
I use power toggles as lock screen widget for bluetooth, wifi, hotspot switch. Lock screen does not require additional swipe. All other things, in reality, work as they work with LP, MM.
For heavy use larger screen is recommended anyway - for the health of your eyes first of all.
Fictional Reality said:
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Click to expand...
Click to collapse
bookworth said:
Indeed, I bought an iPad mini, downgraded z3c to KK and life is good.
I use my phone now for what phones are meant to - calling, occasional e-mail, messaging, weather, etc. Battery life is 4..5 days. The car bluetooth shows addressbook again (did not work with LP, MM).
I use power toggles as lock screen widget for bluetooth, wifi, hotspot switch. Lock screen does not require additional swipe. All other things, in reality, work as they work with LP, MM.
For heavy use larger screen is recommended anyway - for the health of your eyes first of all.
Click to expand...
Click to collapse
Really? What problems did LP & MM bring to the z3c? If it is just better battery then I think I will stay with LP...(unless its twice as good on KK). The camera quality is important for me, are any of them better/worse than others?
Do I just use a 23.0.1.A.5.77 FTF file from here and flash it using Flashtool as the instructions here? I have not rooted or unlocked bootloader, all stock.
warzinak said:
Really? What problems did LP & MM bring to the z3c? If it is just better battery then I think I will stay with LP...(unless its twice as good on KK). The camera quality is important for me, are any of them better/worse than others?
Do I just use a 23.0.1.A.5.77 FTF file from here and flash it using Flashtool as the instructions here? I have not rooted or unlocked bootloader, all stock.
Click to expand...
Click to collapse
There is nothing wrong in MM.
Except for some people who do not use phone 12x7.
Since the concept ROM I was wondering why the battery gets empty even if I do nothing with it. The answer was Doze of course. Yes, I tried several ways for activating aggressive doze, but was not satisfied with these.
Then I decided to go retro and KitKat is all I really need, with its working STAMINA.
For camera I use Sony A6000 and you really can not compare real camera with phone.
If you use your phone heavily, please do not downgrade.
If you have smartwatch, please do not downgrade.
If you feel unsure about flashing, please do not downgrade.
If the warranty is dickbutt in your country - please do not downgrade.
If you still decide to downgrade, then yes, your instructions are correct.
NB! The flash will take long time. Be pacient. It seems to be stuck but it just stays in one place for 5..10 minutes and then everything is ok. I have not measured the exact time, but I was horrified at first flash - it really seemed stuck. Perhaps it is just with my phone.
Scared of MM, really?
Firstly its been out quite some time now, especially if you consider N has just been released to the Nexus range.
Stamina mode and Doze are fantastic, I get 2 days+ with my compact and it's on 24/7.
I also have audited my startup items and background apps to reduce load on then phone which pays dividends.
The initial MM upgrade didn't include Stamina but Sony have since released an update bringing it to the masses.
Your call in the end but don't let scaremongerers cloud your judgement, do some reading, reviews from good sources and make your own minds up.
I did and only issue I had, which I know probably isn't just down to MM, was the emergency dialling issue on lockscreen.
3rd party app cured that for me so now the phone doesn't sit in my pocket making random noises and dialling whoever it pleases anymore!
Fictional Reality said:
It would actually benefit you to DOWNGRADE to Kitkat...LP & MM are horrible on the Z3c
Click to expand...
Click to collapse
LP running fine for me. I only have 1 bug is video playback freezing while buffering.
asmetoma said:
Stamina mode and Doze are fantastic, I get 2 days+ with my compact and it's on 24/7.
Click to expand...
Click to collapse
I've got 4...5 days with KitKat, phone is also on 24/7 (but of course, I do not USE it 24/7). No root.
It's not about scare - the phone is too cheap to be scared, besides there are many new phones to choose from with really good batteries.
However, I do not feel that I should change the phone and I like when I do not have to charge it often.
---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------
Perhaps one should take into consideration that the workload of the phones has been increased a lot during last few years. Specially if you have smart devices etc.
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
SpGG said:
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
Click to expand...
Click to collapse
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
optimumpro said:
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
Click to expand...
Click to collapse
I didn't change anything. Same thing when I went for a new nightly of cm12.1 I did nothing out of the ordinary. Since I did not have new problems since the above mentioned, I didn't delve any further. Today I had another, interesting issue. No one was able to call the phone and I wasn't able to call out, even though the network showed up as fine with full bars. This lasted for several hours. I went into flight mode and back out of flight mode and the issue was fixed. Several SMS arrived about calls missed. And again, I have no idea if this was caused by the hardware, an issue with the software or even the network.
And that is the frustrating thing: How can I find out who the culprit is? Are there good system crash diagnostic tools? Because so far I haven't seen anything.
Since upgrading my Samsung S10e OTA, the Home and Recent App buttons disappear, and also I can't swipe the Notification pane down. The only fix seems to be a restart. The problem happens reliably after charging for a while, and occasionally during normal use as well.
I have tried wiping the cache and pretty much every other setting I can think of. Any idea how to fix this so that I at least don't have to reboot!?
any ideas anyone?
I am wondering if your launcher/home app is crashing? I think that even if you use a third-party launcher (eg, I use Nova) these buttons are still handled by Samsung's launcher/home app? If that is sleeping or crashing, it may be why these are disappearing? That would be my only guess at the moment.
On older phones, when this kind of thing happened, I would put a launcher icon on the screen, so I could relaunch it. But I don't see an icon available for the OneUIHome app on my phone... but if you can find some way to get that it may allow you to restart it, and test this theory?
schwinn8 said:
I am wondering if your launcher/home app is crashing? I think that even if you use a third-party launcher (eg, I use Nova) these buttons are still handled by Samsung's launcher/home app? If that is sleeping or crashing, it may be why these are disappearing? That would be my only guess at the moment.
On older phones, when this kind of thing happened, I would put a launcher icon on the screen, so I could relaunch it. But I don't see an icon available for the OneUIHome app on my phone... but if you can find some way to get that it may allow you to restart it, and test this theory?
Click to expand...
Click to collapse
I am not using a 3rd party launcher. However I have tried using Nova (free) and it seems to have the same problem.
I have also installed Assistive Touch that puts a little floating button on the top that acts as home/last used/notification panel. Only the Home function works however so I still can't access the notification panel.
I really don't want to do a factory reset! Maybe the next update will fix it but this phone is quite old now so I don't know how many updates are yet to come....
Sorry, I don't have any other ideas. I have heard of people having issues with A12 in general, but not this one particularly. That said, if you do a FDR then you may consider going back to A11 and seeing if that resolves it. The FDR might do it as well, but you can't go back to A11 from A12, so you could do that and see how it fares... then do the A12 update (without FDR) and see if it comes back - in which case you'd know it's something to do with A12 on your phone...?
Sorry I don't have better ideas!
Thanks - do you know if there are any large updates in the pipeline after the update to A12? I ask since I had this problem when I first bought the phone and I think it went with the next large update. Back then (2 years ago or more) I could fix the problem without restarting by clearing the cache in Android settings which somehow got the buttons & notification pane back. Unfort there isn't an option to clear the cache in A12 (I have tried doing it in recovery which made no difference).
That's weird... I don't believe we can expect A13... so the only thing I'd expect is continued security updates...
I have avoided A12 because of the many issues I read about on the forums and elsewhere. I have no issues with the phone today, so I figure why bother, you know?
I've actually never encountered this behaviour, strange. Mine have a bright line on the bottom part of the screen and sometimes it shines more then other. But that's purely hw issue not software.
Regarding updates, Samsung is updating now with May 22 security patches, I heard they moved us to 3months cycle of updates, but seems they still comes out monthly. That's cool!
kayuz said:
I've actually never encountered this behaviour, strange. Mine have a bright line on the bottom part of the screen and sometimes it shines more then other. But that's purely hw issue not software.
Regarding updates, Samsung is updating now with May 22 security patches, I heard they moved us to 3months cycle of updates, but seems they still comes out monthly. That's cool!
Click to expand...
Click to collapse
There are one or quite old posts about the same problem, and the suggested fix is to enter the following in ADB
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
But on my S10e there is no SetupWizardTestActivity option available when I go into ADB.
Any idea?
drb01 said:
There are one or quite old posts about the same problem, and the suggested fix is to enter the following in ADB
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
But on my S10e there is no SetupWizardTestActivity option available when I go into ADB.
Any idea?
Click to expand...
Click to collapse
Any ideas anyone? The problem seems if anything worse since the last OTA update from Samsung !
Have you tried a different launcher app? Is the OneUI app being killed by something? I would think it should be eliminated from battery optimization in the stock ROM by default, but make sure it is. Beyond that, if you're using any battery-saving apps that could be killing it?
schwinn8 said:
Have you tried a different launcher app? Is the OneUI app being killed by something? I would think it should be eliminated from battery optimization in the stock ROM by default, but make sure it is. Beyond that, if you're using any battery-saving apps that could be killing it?
Click to expand...
Click to collapse
The OneUI Home app was "Optmised". I changed it to Unrestricted which made no difference.
In a previous version of Android when I had this same problem I could just clear the app cache in Settings and the buttons would reappear. There doesn't seem to be a way to do this in Android 12. I have tried wiping cache in recovery which made no difference.
Do you have other battery optimization apps installed? Greenify, etc? These may be killing it as well.
You can still wipe cache in Android 12: https://mobileinternist.com/clear-cache-android
If you had a workaround in A11, I might suggest going back to that - you should be able to (for a while, at least... once the BL changes you won't be able to).
schwinn8 said:
Do you have other battery optimization apps installed? Greenify, etc? These may be killing it as well.
You can still wipe cache in Android 12: https://mobileinternist.com/clear-cache-android
If you had a workaround in A11, I might suggest going back to that - you should be able to (for a while, at least... once the BL changes you won't be able to).
Click to expand...
Click to collapse
V happy to go back to a11, but Is there a way to go back to a11 without doing a factory reset?
And excuse my ignorance but what is BL?
No, you can't go backwards without resetting.
BL = Bootloader. Samsung has been updating this and if you're on a later version, you cannot backtrack it (at least not on a Snapdragon phone). I realize now that I'm not sure which phone you have, so if you're on Exynos then the situation could be different.
As long as the A11 you're flashing has the same BL version as the one you have now, you can flash backwards that way. 5th digit from the end of the version number (eg G970U1UEU6IVD2) tells you the BL version. You'll need to get an A11 with the same version there, and it should be doable.
What's your full version number?
schwinn8 said:
No, you can't go backwards without resetting.
BL = Bootloader. Samsung has been updating this and if you're on a later version, you cannot backtrack it (at least not on a Snapdragon phone). I realize now that I'm not sure which phone you have, so if you're on Exynos then the situation could be different.
As long as the A11 you're flashing has the same BL version as the one you have now, you can flash backwards that way. 5th digit from the end of the version number (eg G970U1UEU6IVD2) tells you the BL version. You'll need to get an A11 with the same version there, and it should be doable.
What's your full version number?
Click to expand...
Click to collapse
The full build version is SP1A.210812.016.G970FXXUFHVE1.
If there is a way to go back to a11 without doing a reset I'd love to know! Or of course just any way to fix this problem ..
Sorry, I should have chased this down first - you have an Exynos phone, so you may have other options. You'll need to re-post and say you have an Exynos phone, and ask people about this again... maybe others who are more familiar with Exynos can chime in. Sorry for wasting your time with my Snapdragon-related info.
In the future, it's important to mention you have an Exynos phone... or say you have a G970F... the "F" means the same thing.