Apologies in advance for noobish questions...
I bought an unlocked Z5C (US version) at Best Buy a few weeks ago, and have been happy with the phone, even though the fingerprint sensor has been disabled for the US.
I had been hoping for the possibility that when 6.0 was released for the phone, because of the new framework having more fingerprint-related libraries baked in, that the sensor would be enabled. No such luck.
So, my question is, how easy/difficult would it be to somehow enable the fingerprint sensor on the US version of the Z5 Compact?
I've never really gotten too deep into rooting, building, etc., but I am a software developer, so I'd be comfortable with development tools, build environments, modules, etc., but I just don't know where to start with something so specific, having never done it for this platform before.
I'd have to think that there would be some way to do a custom build, either importing fingerprint libraries into a US build, or importing US radio libraries into an international build that has the sensor enabled, or some combination like that?
I'm really just looking for someone to hopefully point me in a direction to try to do this. If there's already a solution, even better, but I'm not holding my breath for that one.
Thanks in advance for any info!
-Mark
Im not positive but I thought both versions have different hardware. If so then the us would not have it?
mario24601 said:
Im not positive but I thought both versions have different hardware. If so then the us would not have it?
Click to expand...
Click to collapse
My understanding was that the hardware is still present in the US version, but it was disabled for legal reasons. Could be wrong though.
msamuels0 said:
Apologies in advance for noobish questions...
I bought an unlocked Z5C (US version) at Best Buy a few weeks ago, and have been happy with the phone, even though the fingerprint sensor has been disabled for the US.
I had been hoping for the possibility that when 6.0 was released for the phone, because of the new framework having more fingerprint-related libraries baked in, that the sensor would be enabled. No such luck.
So, my question is, how easy/difficult would it be to somehow enable the fingerprint sensor on the US version of the Z5 Compact?
I've never really gotten too deep into rooting, building, etc., but I am a software developer, so I'd be comfortable with development tools, build environments, modules, etc., but I just don't know where to start with something so specific, having never done it for this platform before.
I'd have to think that there would be some way to do a custom build, either importing fingerprint libraries into a US build, or importing US radio libraries into an international build that has the sensor enabled, or some combination like that?
I'm really just looking for someone to hopefully point me in a direction to try to do this. If there's already a solution, even better, but I'm not holding my breath for that one.
Thanks in advance for any info!
-Mark
Click to expand...
Click to collapse
try this method in this thread might be able to activate it if its software locked
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Pakman123 said:
try this method in this thread might be able to activate it if its software locked
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Click to expand...
Click to collapse
Exactly what I was looking for, thanks!
We'll see how it goes!
msamuels0 said:
Exactly what I was looking for, thanks!
We'll see how it goes!
Click to expand...
Click to collapse
no problem good luck
Let us know if it works, I am curious.
DAVe3283 said:
Let us know if it works, I am curious.
Click to expand...
Click to collapse
Quick update...
I finally got a chance to mess with this over the weekend. There is not yet a Custom UK E5823 release for MM, so I tried copying the files from another MM non-us release, and it didn't appear to work. However, I did go and revert back to Lollipop with the latest available UK release, and can at least confirm that the fingerprint hardware is indeed present, as the fingerprint manager then showed up, and the sensor worked. I went back to the latest E5803 Custom US Marshmallow, and will wait until MM is available for UK, and try to copy those files and rebuild again then.
Interesting... that is good to know. It seems that we could buy the US version to get the warranty, then just flash an international firmware to unlock all the functionality. And hopefully down the road, do the mash-up firmware for the best of both worlds!
I'm just surprised they disabled the sensor in the US, especially with the sensor still present in the phone!
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Fantastic work!
Sent from my SM-G850M using Tapatalk
msamuels0 said:
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Click to expand...
Click to collapse
Congrats!! Wat about cellular reception and call quality, any glitches?? (like echo troubles...)
AnandRajaguru said:
Congrats!! Wat about cellular reception and call quality, any glitches?? (like echo troubles...)
Click to expand...
Click to collapse
I don't have a US model but an international model, running on Nordic using att and have no issues other than signal bars displaying less signal than i have. I'll show no bars at the same db rating my other phone shows 2 bars. No big deal phone still works fine.
Woo! This makes my day!
runningwarrior08 said:
I don't have a US model but an international model, running on Nordic using att and have no issues other than signal bars displaying less signal than i have. I'll show no bars at the same db rating my other phone shows 2 bars. No big deal phone still works fine.
Click to expand...
Click to collapse
Yeah, I noticed the signal meter reading lower than it should on the Nordic firmware on US T-Mobile. Getting 20Mbps on 4G with no bars is fine with me.
Amazing news for US version owners
msamuels0 said:
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Click to expand...
Click to collapse
You don't have volte though right?
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
Sony phones have always reported lower signal than actually present. No idea why
Possible to revert back?
This is great news. Is it possible to revert back to make it report as the right model for warranty purposes?
Of corse, just flash back US firmaware and it'll be ok.
just flashed "customized uk" version and got my US z5c fingerprint reader up and running. wonder what, if any, issues might arise from running a firmware for a different model, e5823 vs. e5803.
this thing is nice, but man , it does get pretty hot in the back top center. yowza.
Related
.... will not be anything that is resolved here. It is a problem with the firmware for ICS.
I was talking to somebody at sprint today while I was there and showing them my device and asking if there will be any issues caused by having a virgin mobile ROM on the device. The lady explained to me that they are exactly the same, get the same reception, same update packages, and work on the same network, etc., etc.... All of this was known to me to some extent, but wanted to hear it from somebody at the company... and told me that the only problem they are having is with ICS in general is that there have been data/radio issues with the Galaxy Nexus line as well ever since it released on their network a few weeks ago.
Furthermore, she explained that this was a known bug/issue and that she knew for a fact that an update would be coming with a fix and that it was being worked on right now.
The reason I wanted to share this was because I have seen a lot of misinformation floating around about 1.) having a virgin mobile ROM on your device and 2.) virgin mobile ROM causing data issues - which is not the cause of the issue as I mentioned just now.
Just want you all to be aware of this in case you were thinking having this software and firmware on your device would cause any issues with your billing, your contract, etc. Simply put - it will not. Virgin mobile is owned by sprint, they run on the same towers, same network, and info of accounts is stored in the same place. You could literally walk into a sprint store to pay your bill for your virgin mobile account.
All is well. All is safe. An update will come to fix the data issues, keep your eyes peeled for it folks. We are not given source code for radios, etc., so unfortunately that needs to be fixed on the carrier/manufacturer end - and as I said, it will be fixed and they are working on it. Sit tight.
Hope this cleared up any misconception floating around.
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Oh man, you have no idea how much I was freaking out about the billing. Thanks man. (Y)
xHausx said:
So, you're don't really know how to fix it then? Forgive me for being a little confused, but you say there is a problem with the firmware and then say that there is nothing wrong with it?
Click to expand...
Click to collapse
yeah, i can see the confusion there....
re-worded, i would say it appeared to me that people thought there were data issues because of being on a virgin mobile ROM. The point I am trying to express is that the problem is the firmware, not because the ROM is for the virgin mobile 3D - if this same firmware was released for "official sprint RUU" where your banner said "sprint" they would still be having the same issues. Ex.: the lady at sprint said the galaxy nexus was having the same issue.
If that makes sense.
If not, not sure how else I can explain it.
It seemed people were crediting the problem to the fact that there device is attached to virgin mobile - this is not the case.
EDIT*** lol, nice ninja edit haus - you gotta be quicker than that roffle
xHausx said:
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Click to expand...
Click to collapse
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Punk9 said:
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Click to expand...
Click to collapse
after half a day of having flashing back they determined the problem to be gone??
......
the issues being caused by the firmware are not constant, and apparently are rather random from what I have read. a perfect example is my own device... no issues with new firmware until today (day 3) of having it, even tho many people reported issues after just a couple of hours.
I'll talk with chad and see what he is cooking up... I havent talked to him a whole lot this weekend.
sent from ICEvo
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
this is true... but again, what is your explanation of the galaxy nexus having the same issue, and the fact that a sprint rep was entirely aware of the issue and that is was being worked on and would come in an update?
and surprise, but any new technology is "beta" ..... whether it is an official release or not. it is the price you pay for cutting edge technology.
sent from ICEvo
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
raptoro07 said:
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
Click to expand...
Click to collapse
from what the lady explained to me, yes it is... intermittent data loss is a bug within the new firmware for ICS
my point here is that it has nothing to do with your ROM being intended for a virgin mobile 3D. it is because of a bug within the firmware for the radios.
as i said, sprint rep explained this to me, and seemed very confident in the way she explained it - confirming it as a known issue, and also knowing that it would be fixed soon because it was being worked on and said it would be serviced as a firmware update.
sent from ICEvo
You think a sprint tech in the store is an authority !!
For one thing, many may not care, you lose VPN capabilities. Which I need and want and has nothing to do with ICS. Flashed back to GingerBread an it's still gone.
You may also lose the ability to properly update the PRI when new ones come out with official ICS.
It is not just a banner issue.
I'm not in a roaming area to confirm roaming issues but I believe folks when they say they can no longer roam on th 3G. I never touched my default roaming settings and it always worked fine. You may be right that roaming is only ICS issue. But it smells like it's way more than that by folks reports. And quite believable given the phone half believes it's on Virgin Mobile.
It is the PRI which manages routing that is not correct. And different folks will get different issues depending on their location.
I don't think chad and friends would be working so hard to fix it if it was such minor issue and I trust them more than some sprint sales person.
Like was stated above. There are two kinds of people. Those with issues and those with no issues, YET !!
And please FIX the broken subject.
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
"issues" is a vague word. whats to say a person's issue is due to ICS, the radios, or anything else in particular?
The new radios made me gain 20 pounds. There's no information showing that the radios did or didn't cause this. Yet here we are proverbially attributing all these issues to one thing or the other, when in reality WE DO NOT KNOW what is causing these problems.
retnuh730 said:
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
Click to expand...
Click to collapse
People here are not stupid. Most do backups before they try something.
I restored a backup and lost capabilities I had.
I reflashed every every sprint RUU, Reflash Hboot 1.40, restored back up and things are not the same.
If you flashed that freeza patch your phone has it's feet in both Sprint and Virgin Mobile and it's not good.
Yes, we know we screwed up. And some of us would like it fixed before we get more surprises of what does not work correctly.
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
What is the "setprop" an ADB command? Do you have to use it. I edited the build.prop how you said reset the phone and nothing changed. I am roaming and cannot connect to data. My phone's data works fine when in a coverage area, but obviously not when roaming. I never did any kind of firmware update. Hope that helps.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
powduh09 said:
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
Click to expand...
Click to collapse
+1 this is a direct pull of the ruu for the upcoming vm evo 3d
Sent from my PG86100 using Tapatalk 2
to anyone that hasn't seen it already, if you flashed this firmware, chad is working on a fix over that this thread
http://forum.xda-developers.com/showthread.php?t=1638225&page=41
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
successfully implemented this. Hope this solves the no roaming issue. Thanks
Visionikz03 said:
successfully implemented this. Hope this solves the no roaming issue. Thanks
Click to expand...
Click to collapse
How were you able to do this? I'm trying to research a little on setprop.....but still not fully understanding it
Sent from my PG86100 using xda premium
So in the span of an hour I had rooted and unrooted my phone. Did this for a couple reasons really. First being this is my first android phone and I wanted to experience the process. Second being I wanted to try the sixaxis controller apk.
I live in Canada and imported a phone via amazon.com purchase. I believe I got the Taiwan model as right out of the box it was defaulted to a chinese character setting. During my unroot process, I flash the UK base into it. This happened because of two things. One being I wasn't 100% sure I had the Taiwan model or not when I was selecting the rom to flash back to. And two, I was following the video in the rooting section which included resetting my flash count to zero and changing my phone from KOR to BTU.
Since then I've run some tests. Cell service is looking good, data is working. Only thing I noticed that I lost in the process was the language keyboard(canada) was available in the chinese stock rom, but I have to use the US one for this stock.
Is there anything I should be aware of? Should I not get too attached to this stock rom and try my best to flash back into the original?
Is there anything I should be aware of?
Click to expand...
Click to collapse
Nope. Rom's are completely interchangeable within the boundaries if the i9300/i9300T hardware.
You can even go as far as cherry-picking the System from one ROM, the CSC from another, the modem from yet another...
(Only within compatibility, Axxx and Bxxx ROM's are not compatible, Bxxx being newer)
Great, good to know. Thanks.
actually just found something, I can no longer access the menu button from within the wifi settings screen. As a result I can't select frequency band, etc.
It's possible that some ROM's dont include that feature. If it's on auto you should be fine anyway since it _should_ prefer the 5Ghz band over 2.4.
AOSP Roms don't have it either, no issue here =)
Guys,
EU version started shipping with ROM Omate_TrueSmart_20140328.182336_V2.0 build
Are the sensors working? if so, can anyone upload the ROM for all the poor people with dead sensors.
NB. i tried every single ROM available in this forum and no luck.
Thanks
my watch is Omate 2100mhz 1/8GB from china with Chinese ROM
That's actually a great question.
Could anyone write some feedback for 2100 1/8 - what are your impressions, something is fixed (we all know what are TS problems, so are they fixed?
And really, what about sensors and BT?
Companion mod is working?
Sent from my C6903 using Tapatalk
Received mine on Friday, not had time to really play with it yet but I can confirm that BT and Companion are working. What sensor issues are there?
I have not even lurked on these threads so please feel free to ask questions and will answer as soon as I can.
chippyuk said:
Received mine on Friday, not had time to really play with it yet but I can confirm that BT and Companion are working. What sensor issues are there?
I have not even lurked on these threads so please feel free to ask questions and will answer as soon as I can.
Click to expand...
Click to collapse
What version is your ROM? try to download ocompass from the ostore if it is working than the sensors are working.
azizbouharb said:
What version is your ROM? try to download ocompass from the ostore if it is working than the sensors are working.
Click to expand...
Click to collapse
It is 20140328.182336_V2.0. Omate version is OUI 2.1. Kernel is 3.4.5
OCompass works fine and in Android Sensor Box, Accelerometer, Orientation Gyroscope and magnetic all work, Sound causes the app to FC.
chippyuk said:
It is 20140328.182336_V2.0. Omate version is OUI 2.1. Kernel is 3.4.5
OCompass works fine and in Android Sensor Box, Accelerometer, Orientation Gyroscope and magnetic all work, Sound causes the app to FC.
Click to expand...
Click to collapse
Great , i'll be looking forward to have the ROM, thanks
azizbouharb said:
Great , i'll be looking forward to have the ROM, thanks
Click to expand...
Click to collapse
I am away on business at the moment but will see if I can get some time to dump It and upload it for you very soon. Please let me know if you manage to get it in the mean time.
Thanks.
I just need to verify a few things before I upload it. If everybody will be patient, I will be able to prepatch it as well.
Also, just because it's newer doesn't mean anything. 0328 may have more issues than a merged firmware based on something older or based on something that doesn't even come from Omate. The 512/4 working sensors is a perfect example. That doesn't even use Omate's kernel but a kernel from a different brand.
chippyuk said:
I am away on business at the moment but will see if I can get some time to dump It and upload it for you very soon. Please let me know if you manage to get it in the mean time.
Thanks.
Click to expand...
Click to collapse
Thank you
azizbouharb said:
Thank you
Click to expand...
Click to collapse
Think it best we wait for Lokifish to do his magic, no point in me putting the base version up, doubt I would be able to until the weekend anyway. It will be worth the wait!
Full 20140328 firmware for those that need it.
And by need it I mean you messed up your device and need a way to get back to stock.
Lokifish Marz said:
Full 20140328 firmware for those that need it.
And by need it I mean you messed up your device and need a way to get back to stock.
Click to expand...
Click to collapse
Not that it matters but is this the one that ships with EU 1/8/2100 devices with OUI 2.1?
Hey crew.
So I've searched high and low for information about the 6.0.1 update for Z5 (Compact). I've seen news pertaining to a global rollout for the Z2 and Z3 series, and have read that there was a plan for it to be released to Z5 series soon (these articles were back in early April). However, anything relevant for the 6.0.1 update on Z5 series has been vague information. I haven't found anything on the forums relating to this topic.
I was curious to see if anyone knew anything more about the 6.0.1 update for the Z5 series, or had sources to link to?
-----
Also, I'm curious to know what everyone's experience on 6.0 has been so far for Z5 compact. I've seen a lot of mixed reviews, mostly negative based on bugs and issues relating to Wifi, External Storage, Google Play Services crashing, etc. Then I've seen other posts saying these things have been fixed, while others are still waiting for a fix. So it's been a lot of conflicting information, and I've remained on Lollipop (on AT&T in the US). So are there fixes for these issues, and is it worth it to upgrade to Marshmallow in the meantime?
I've not had any issues that I can think of. 6.0 has run fine, however since I rooted I have had issues.
Firstly I have Wi-Fi issues. This may not be due to root but my phone definitely isn't as good at retaining a good connection. This occurs when I'm at university walking about and the phone is connectecting and disconnecting from different routers. I don't get any Wi-Fi issues at home though.
Secondly, I'm victim of the "Fingerprint hardware is not available" issue that you can find in another post. Many consider it's an issue with the dose function since it affects some Nexus devices. Mine seems to break daily, but I've given up using it for the mean time. This is the main issue I have and want 6.0.1 to fix.
And finally I've have random slow downs and non responsiveness here and there, but nothing too serious. Sometimes all but the nav keys go unresponsive, so I have to lock and unlock. But this is hardly an issue, just an annoyance.
I've also looked around for 6.0.1 info and websites are all vague and unreliable. I like the phone but it's in a constant state of "this needs to be fixed" which I fear won't be for another few months. Sony are pushing their X range right now so I'm afraid that the Z5 is already being neglected. However I think their lack of update may mean they're trying to get it right this time round. All we can do is hope and be patient.
fisheyes1 said:
I've not had any issues that I can think of. 6.0 has run fine, however since I rooted I have had issues.
Firstly I have Wi-Fi issues. This may not be due to root but my phone definitely isn't as good at retaining a good connection. This occurs when I'm at university walking about and the phone is connectecting and disconnecting from different routers. I don't get any Wi-Fi issues at home though.
Click to expand...
Click to collapse
The wifi issue is a bug for all versions on this phone. It does not auto connect when the screen is off.
girthmaul said:
The wifi issue is a bug for all versions on this phone. It does not auto connect when the screen is off.
Click to expand...
Click to collapse
Something must have changed, though. I didn't have this issue with the original firmware, my phone stayed connected to wifi with screen off. This changed with the update to M. I'm noticing this very obviously, because I hear the GSM or LTE signal noise via my unshielded monitors, which is annoying as hell, when my phone is just lying on the desk.
Do you, or someone else, know, if Sony acknowledged this bug? Because if they're not going to fix it, this will be a reason for me to switch the phone.
6.0.1
I have read from reputed shafiq01(xda member) that the 6.0.1 update is on the way and it brings xperia x features to z5 and UI too and he had previously also been right so just be patient. Xda him and see for yourself.
http://en.yibada.com/articles/12497...w-xperia-z2-xperia-z3-xperia-z4-xperia-z5.htm
Just found this article. Why would the new version (32.1.A.1.163) have a smaller number than the current version (32.1.A.1.185)?
dave
bigdfmartin said:
Just found this article. Why would the new version (32.1.A.1.163) have a smaller number than the current version (32.1.A.1.185)?
Click to expand...
Click to collapse
32.1.A.1.163 is for the Z3+. It's the same that the Z5 also got at some point depending on your location/provider.
Don't trust those clickbait sites.
Amanansari said:
I have read from reputed shafiq01(xda member) that the 6.0.1 update is on the way and it brings xperia x features to z5 and UI too and he had previously also been right so just be patient. Xda him and see for yourself.
Click to expand...
Click to collapse
Really ? That Will be awesome
bigdfmartin said:
http://en.yibada.com/articles/12497...w-xperia-z2-xperia-z3-xperia-z4-xperia-z5.htm
Just found this article. Why would the new version (32.1.A.1.163) have a smaller number than the current version (32.1.A.1.185)?
dave
Click to expand...
Click to collapse
In case of the Z5 Compact, 32.1.A.1.163 was the first Marshmallow firmware released in early March. 32.1.A.1.185 rolled out a month or so later, apparently to fix bugs.
Personally, I haven't run into any issues with Wi-Fi or fingerprint reader in both Marshmallow firmwares. I'm happy with what I have, but 6.0.1 and a more up-to-date security patch wouldn't hurt
I use an ATT unlocked variant of s21 5G
1: It overheats excessively, you cant even game on it
2: When gaming, the touch sensitivity is very low despite turning on increased sensitivity in settings
Anyone know why or give a possible solution, my guess is because its still stuck on One Ui 3 and Android 11
habiodunz said:
I use an ATT unlocked variant of s21 5G
1: It overheats excessively, you cant even game on it
2: When gaming, the touch sensitivity is very low despite turning on increased sensitivity in settings
Anyone know why or give a possible solution, my guess is because its still stuck on One Ui 3 and Android 11
Click to expand...
Click to collapse
I can't say why with any certainty, but can say I would never want a carrier rom on my phone, I always switch to an 'open' version as it rids you of the carrier bloat and and restrictions etc they put in their roms.
Granted, that doesn't work for everyone as they are 'tied' to a specific carrier. So, if that's the case, I'd look for info about whatever that specific rom / carrier problems exist.
But, if you can go with any carrier you want, go with one like Mint Mobile, which allows volte, vowifi, and 'open' rom phones, like the S21. It's easy enough to find how to use Odin to flash an 'open' rom also.
One additional thing you would accomplish by doing the above; you'll discover if the issues you're experiencing are the fault of the current rom, or they are hardware related. Not sure how else you would test that hypothesis other than doing the exact above?
good luck
AsItLies said:
I can't say why with any certainty, but can say I would never want a carrier rom on my phone, I always switch to an 'open' version as it rids you of the carrier bloat and and restrictions etc they put in their roms.
Granted, that doesn't work for everyone as they are 'tied' to a specific carrier. So, if that's the case, I'd look for info about whatever that specific rom / carrier problems exist.
But, if you can go with any carrier you want, go with one like Mint Mobile, which allows volte, vowifi, and 'open' rom phones, like the S21. It's easy enough to find how to use Odin to flash an 'open' rom also.
One additional thing you would accomplish by doing the above; you'll discover if the issues you're experiencing are the fault of the current rom, or they are hardware related. Not sure how else you would test that hypothesis other than doing the exact above?
good luck
Click to expand...
Click to collapse
Thanks mate, started getting the files for a new ROM