Database Users

[Q] Camera problems.

Hello
I have been having some problems with the main camera on the A500. It has different tints to it. Sometimes the picture seems to be divided in 4 and all 4 squares have a different hue to them. Restoring to factory settings seem to take care of it for a while. Initially I thought it was "skype" that messed it up, but it is not.
I just restarted the tablet and the camera is giving me a yellow tint, with a clear horizontal stripe about 3/4 inch wide through the middle.
The tab has stock 3.2 on it.
I was wondering if anyone has experienced similar problems and if there was a solution to the problem.
Thank you

Well, I would think the problem seems to be some app/apps you have installed. Based on when you do a factory reset, it goes away.
I would just do another factory reset. Then verify it went away. Run it for a couple of days WITHOUT installing any apps. This will probably rule out a hardware issue.
Then install apps, 1 at a time. Use the camera, and look for issues.

Thanx. I will give that a try.

I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?

mobilebone said:
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
Click to expand...
Click to collapse
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.

Moscow Desire said:
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Click to expand...
Click to collapse
I thought it would be ok. But after restarting a few times, the camera colors are off. I'm going to root and install a custom 3.2 to make sure it is not the hardware.
Spasiba for all your help )

any news about this problems.
it seems that my iconia has the same problem- i never noticed it because i dont use the rear camera.
i sold it it today and the guy who bought has described something like what you folks are talking about
the strange thing is that i had done a clean boot before i sold it, and the buyer hasnt installed anything on it yet.
im waiting to hear back from him after he tries another clean boot.
anyone else have any ideas ?

I'm having the same problem. I don't use it much, but the camera was ok before. When I tried using it this weekend, it showed colored translucent squares on the sides. It is not a config problem, as there are no effects turned on. The front camera works 100%. I will post a sample when I get home.
If I change the "whites" config to Incandescent, it kind of solves the problem. Sometimes, the squares appear, but not for most the time.
I believe this is not a harware issue, unless that whites configuration is made with hardware (highly doubt it). I don't have Swift key, or Yahoo messenger, or any other apps that use the camera (other than Skype, but it was already installed when the camera worked).
Did anybody find a fix to this? It seems it is only a problem on stock 3.2.
Edit: not an exclusive 3.2 stock issue, it appears that custom roms have this problem as well.

I have the same issue after ICS ota upgrade...
Any ideas?

I haven't had the issue since the ICS upgrade. Only tested once or twice, but it is working properly.
What I did to partially fix it was changing the White Balance to "Incandescent".

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.

I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

Bluetooth audio "stutter" on wake/unlock?

Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.

codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app

Gizmoe said:
It's a problem at the source code. It's says it's been fixed on Developer N preview 3. So when N is released publicly it should be fixed. Or you can join the beta program. I have preview 3 running now and it's pretty solid. I don't use bluetooth audio though, so I can't say if it is indeed fixed. If you do try it be sure to enable OEM unlocking in Android dev settings just to be sure you can save your device should anything happen. Also check the list of supported apps so if any app you rely isn't supported you can decide from there.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Gotcha, that's what I was afraid of. Will checkout the N Preview, thanks!

codeman05 said:
Recently picked up the 6P (still stock on lastest FW) and have only one issue with it.
When I am steaming audio over bluetooth in my car (usually using Play Music), if I wakeup/unlock the device, the audio stutters/lags for a good 5-10 seconds before going back to normal. Once awake, dragging down the notifications menu can cause a similar effect though less pronounced. If I turn the screen back off, it goes back to normal instantly.
I don't have any other BT devices to test this on, but I've not had this issue with any other androids in my car. I also don't see any "lag" issues anywhere else. Before I unlock and root this thing, any ideas on how to fix it on the stock rom, or is a custom rom not likely to fix this either?
Appreciate it.
Click to expand...
Click to collapse
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?

Shocknoble said:
Hey! I just found this post. I have had the same issue on my 6P since receiving it in November. I was stock until just a few days ago, now just running 6.0.1 and xposed. The issue fixed itself right after I wiped and rooted, but is now back. This is odd because booting my phone into safe mode didn't fix the issue, so I'm thinking it's not caused by a specific app, although I'm yet to try it.
Since you mentioned you don't use other bluetooth devices, this problem ONLY exists for me in my car audio, a 2015 Chevy Cruze.
If you don't mind me asking, what car are you driving?
Click to expand...
Click to collapse
I have the exact same problem with my 2015 Chevy Volt nav / stereo system. I never noticed this issue until I updated to the Android N release a few days ago. It always happens when I turn on the screen. I rooted and went back to Android M, but the issue is still there. I'm guessing that's because my phone now has the latest baseband and radios instead of the older ones that did not have this Bluetooth problem. If you guys come up with a fix let me know. I'm thinking of flashing the Android M radios to see if that's the problem since I'm now running a custom Android M based ROM anyway. I tested the phone with my wife's 2016 Mazda CX5 and it has none of this screen on stuttering garbage.
UPDATE: I went ahead rooted, installed Pure Nexus ROM (6.0.1-20160821), installed ElementalX-N6P-1.21 kernel, flashed bootloader-angler-angler-03.54.img and radio-angler-angler-03.61.img from angler-mtc20f-factory-d62de11e.tgz, and after all that the issue is still there! What a complete waste of time. What I'm guessing might be the problem is I switched to Sprint on July 2016. Before that I was on T-Mobile and I never had this screen on stuttering issue. It seems there might be some type of interference here and it's possible it is a hardware design flaw since Google has not been able to fix the issue for quite some time. As of now I've switched to my LG G5 phone which has no Bluetooth issues with my Chevy Volt. If I don't find a fix soon I'll probably sell the Nexus 6P and wait for the newer Nexus devices.

FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).

macmanui said:
FWIW, I have the same issue with my 2014 Chevy Cruze and my HTC 10. Ran across this thread while hunting down a solution (unsuccessfully, this far).
Click to expand...
Click to collapse
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!

I have found a somewhat reliable fix - PLEASE tell me it works for you all as well.
Hopefully we are all familiar with the problem: A Nexus 6P ( Or whatever is the issue for you) is paired with my 2015 Chevy Cruze that I use to stream audio while commuting. The audio is more or less fine until the screen turns off/I lock the phone. Once I unlock the phone or a notification wakes the screen up, the audio stutters over my car speakers until I turn the screen back off, or 6-8 seconds has passed. This doesn't happen with any other device I own when paired to my car, and my phone doesn't have the same issue when paired with any other bluetooth receiver. I am on a rooted but otherwise stock 6P running 7.0.
I do not use my car for messages, only music/podcasts and phonecalls. I went into the bluetooth settings while driving ( I do not recommend you do this while your car is in motion) and noticed the stuttering was consistent the entire time I had the menu open. This prompted me to assume it must have something to do with the phone making other bluetooth actions while connected to my car, that my car didn't like.
I clicked on the gear for settings next to my car in the bluetooth paired devices list, which pops up the menu that lets you change the name of the device, and what it is used for. My options are: 'Phone Audio', 'Media Audio', 'Contact Sharing', and 'Message Access'. I denied message access to my car the last time it prompted me, but the last two on the list were still checked. I unchecked both of them, reset my phone, and crossed my fingers.
It works. It freaking works. It's not 100% and if I flip the screen on and off over and over again it'll still get a little wonky, but I no longer cringe when I have to unlock my car in the phone.
Will the rest of you give this a shot and let me know if you have similar luck? Best wishes!
Josh
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?
---------- Post added at 01:50 PM ---------- Previous post was at 01:50 PM ----------
mhajii210 said:
I figured out that if I uncheck Message Access for my Chevy Volt under my phone's Bluetooth settings, the screen on stuttering is fixed!! Everything works flawlessly with my wife's Mazda CX5 so it must be a Bluetooth compatibility issue. Check it out and see if that resolves your HTC 10 issue with your Chevy. Good luck!
Click to expand...
Click to collapse
You're totally right. I discovered this on my own right about the same time you did apparently and I wanted to make sure it lasted before I made a post here. You deserve all the credit, I'm just so happy it's fixed. Now, I am curious if it'll still stutter a bit if you turn your screen on and off really quickly a few times?

Seems that GM vehicles are a common denominator too! I have the stuttering with my 6P int my Holden Cruze. Didn't have the issue with my old Nexus 6 and don't have the issue with the 6P when making calls over BT. I haven't listened to as great deal of music from the 6P over BT except in the car so can't really compare there.
It's interesting to read a comment that it was going to be fixed in M preview 3 but even now in Marshmallow release the issue is still there.

Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.

Pica_Man said:
Hi, been suffering with a stutter in my Mercedes every 20mins with a 5X on 7.0. Again, seems a common problem with Mercs. I tried EVERYTHING to fix this for months, including full phone wipes and flashes.
I just fixed my issue entirely, not sure if it will work for you guys, but I believe it is an issue with the BT bandwidth that the car is able to cope with. I turned off Phone Book and SMS Message Access services and my issue is gone. I think the phone is maxing the bandwidth with A2DP and as soon as a sync is requested for phone book or message = the problem arises.
Click to expand...
Click to collapse
Interesting. It certainly does feel like a bandwidth issue. I have a Moto360 and has tried turning that off but hadn't thought of turning phone functions off. I don't really want to do that either but will try it to confirm.

I turned off phonebook and SMS but it made no difference to me at all.

I have noticed a Terrible shutter from my device when paired to a portable BT speaker. at times the only fix is to turn the speaker off then back on. it is horrid.

OP2 Screen rotation periodically stops working

Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!

OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.

utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.

k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13

Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.

Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.

Z3 compact user in 2019

Hello,
I am getting my z3 compact tomorrow. I would like some input from existing users about the phone:
1) which official rom will give me the best user experience, meaning best camera, snappiness, the least problems/bugs. I usualy prefer the rom that the phone was shipped with, so is there a reason to go to newer rom, meaning better battery life, bug fixes, better camera ?
2) as i know camera on this phone is horrible, what do i need to know to get at least mediocre performance out of it ? Do u suggest superior auto or manual ?
3) anything else i need to know ? I will mostly use it for calls, camera, occasionaly google maps and music, almost never for webpage browsing or videos, never for games

1) I use the official .291 ROM with MM
2) Use the Cyberian camera mod and Manual mode
3) There is the common touch screen issues and issues with 3.5jack

1) i have it at 6.0.1 right now. I would rather remain at stock since i dont wanna mess up camera keys and add more bugs.
2) do i have to root phone for this cyberian camera ? Could you quickly explain what gains i get with it over default camera ?
3) i didnt get touchscreen issues, didnt test 3.5 jack yet. The only problem i had so far was that when i wanted to take a photo and before taking it, i was moving phone very quickly and suddenly i got artifacts and screen tearing on screen. 1 thing to note is that phone was quite warm at the moment because i was bulk installing apps. After that i wasnt able to replicate the problem again. I hope it was momentary thing and that phone will work ok

Btw phone is updated to last rom and factory reset (actualy factory reset 2 times in a row). And there is a wierd thing. When i connect to my computer, i want to be able to access my pictures right away. But instead i have to click mtp mode on screen of mobile phone. I went to connectivity and basicly i have no option there to change default connectivity mode - the only thing there is option to automaticly install software when connected to pc. Is there a way to change things so that when i connect the phone to pc, i dont have to press anything and be able to access pictures right away

No one using this phone anymore ?

xperiafan8 said:
1) i have it at 6.0.1 right now. I would rather remain at stock since i dont wanna mess up camera keys and add more bugs.
2) do i have to root phone for this cyberian camera ? Could you quickly explain what gains i get with it over default camera ?
3) i didnt get touchscreen issues, didnt test 3.5 jack yet. The only problem i had so far was that when i wanted to take a photo and before taking it, i was moving phone very quickly and suddenly i got artifacts and screen tearing on screen. 1 thing to note is that phone was quite warm at the moment because i was bulk installing apps. After that i wasnt able to replicate the problem again. I hope it was momentary thing and that phone will work ok
Click to expand...
Click to collapse
i'm still sticking with z3c, but i'm a noob, probably not the best person to answer your question.
i have never tried official stock 6.0.1, i tried slimm 6.0.1 and existenz 6.0.1 but the battery life is disappointing.
at the moment i'm going back to official stock 5.1.1 with cyberian camera.
i think u need to root, (after root, CLEAR DATA "Camera","Camera Common" & "Video" and then flash cyberian camera via recovery)
i never had ur screen tearing issue.

Miui 7, Androplus Kernel v32' and living normally...

z3c my emergency mobile..existenz rom. is a pseudocustom that preserves all the functionality Z series, ant +, mirrorlink 1: 1, etc. mobile 10, comfortable, beautiful, well built, much better than the later z5c. I have had 2 z3c and 2 z5c and the z3c is much more device. I have had the bad luck to always have devices with the bootloader closed(prototype) and not be able to enjoy them 100%, but existenz is very good rom for daily use

xperiafan8 said:
Btw phone is updated to last rom and factory reset (actualy factory reset 2 times in a row). And there is a wierd thing. When i connect to my computer, i want to be able to access my pictures right away. But instead i have to click mtp mode on screen of mobile phone. I went to connectivity and basicly i have no option there to change default connectivity mode - the only thing there is option to automaticly install software when connected to pc. Is there a way to change things so that when i connect the phone to pc, i dont have to press anything and be able to access pictures right away
Click to expand...
Click to collapse
Don't worry about that, it's normal. It was one of the "great" and new features in android MM. Every device which runs stock, or nearly stock android MM will do the same when connected to a PC. So seriously, no worries, it's okay, you'll always need to select MTP.

Btw touch focus doesnt work in camera. I click on a spot but it does nothing. I would really love to have option to focus to my liking before taking a picture. And i dont want to use dedicated camera button

xperiafan8 said:
Btw touch focus doesnt work in camera.
Click to expand...
Click to collapse
You're in Manual Mode? There's no Touch Focus option in Superior Auto.

There are lots of used Z3 Compact ads for sale with the touch not working.

I'm using omnirom 8.1 and z3c.

The touchscreen-issue is very common on this phone indeed. I exchanged my touchscreen of my 3-year-old Z3C by myself and if you have some suiteable tools, a calm hand and a bit of time, the process is possible for an average-experienced user. There are lots of Youtube-Videos as well. My girlfriend had a Z3C as well and the touchscreen of this phone was broken too. Seems like planned obsolescence?

Carbon Rom Oreo. It's always been my go to rom when I cannot find a smooth and fluid rom, or when the rom doesn't support the device's specific features , such as the z3c's camera button. I've used the rom on the z3c for all of 2 days so far and I'm continually amazed at how the devs have managed to create such a polished experience.

hellomot0 said:
1) I use the official .291 ROM with MM
2) Use the Cyberian camera mod and Manual mode
3) There is the common touch screen issues and issues with 3.5jack
Click to expand...
Click to collapse
Have you tried gcam on Z3 compact?

Derickee Medvedev said:
Miui 7, Androplus Kernel v32' and living normally...
Click to expand...
Click to collapse
Is your phone D5803 or D5833? Mine is the second one and just can't boot if I install any custom ROM. I tried many but none worked

FlavioHuster said:
Is your phone D5803 or D5833? Mine is the second one and just can't boot if I install any custom ROM. I tried many but none worked
Click to expand...
Click to collapse
Use the flash tool for sony, and flash the D5803 Firmware, choose the version desired and flash

Derickee Medvedev said:
Use the flash tool for sony, and flash the D5803 Firmware, choose the version desired and flash
Click to expand...
Click to collapse
It didn't work :/ I'm almost giving up on this phone

xperiafan8 said:
No one using this phone anymore ?
Click to expand...
Click to collapse
Me until now still using this phone for PUBG mobile
xperiafan8 said:
Hello,
I am getting my z3 compact tomorrow. I would like some input from existing users about the phone:
1) which official rom will give me the best user experience, meaning best camera, snappiness, the least problems/bugs. I usualy prefer the rom that the phone was shipped with, so is there a reason to go to newer rom, meaning better battery life, bug fixes, better camera ?
2) as i know camera on this phone is horrible, what do i need to know to get at least mediocre performance out of it ? Do u suggest superior auto or manual ?
3) anything else i need to know ? I will mostly use it for calls, camera, occasionaly google maps and music, almost never for webpage browsing or videos, never for games
Click to expand...
Click to collapse
1. Stock Rom 6.0.1, Lollipop 5.1.1 is more smooth and not heating
2. Use cyberian mod, using manual mode had more good image than superior auto but you must set the manual settings first
---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------
beliC619 said:
Have you tried gcam on Z3 compact?
Click to expand...
Click to collapse
didnt work