Today I build PureKAT v3 to my s5300 and for now it looks good except two little things. At the pin code screen, I can't see the numbers I entered. Fortunately it accepts the code. The other thing; sometimes when I reboot the phone it freezes. I know it's not that important but if there's a solution I'd like to learn
Related
I've recently left my i9100 for an i9305 and decided to start by flashing the equivalent to my favourite ROM from my S2, namely SlimSaber (SlimKat unoffical build with Saber Mod) from here (build 8.0). Unfortunately I didn't test it much before installing the custom ROM as I wanted to go strait back to the KitKat experience I am used to, so I'm not sure if the problem was there before.
Anyway it seems to be a common problem with smartphones - the proximity sensor doesn't work! It's really annoying because whenever I make a call the display turns off and i can't use the dialer or anything else. On my Sensor Box app it consistently reads as distance 0.0cm. Now obviously knowing that it's a common problem I'm not just burdening you guys with it without having a good dig myself.
Here's what I've tried:
* Various proximity sensor fix/calibration apps.
* Manually calibrating the proximity sensor from the terminal as outlined in Method 1 here.
* Various USSD/MMI code solutions all come to an abrupt dead end because of my other bug.
* Disabling "Turn off screen during calls" from the dialer's settings - the option doesn't seem to exist on my SlimKat dialer and i hate other dialers
* Disabling proximity and light sensor using Hardware Disabler app, worked but has awful side effects crippling other sensors!
* Blowing compressed air down the headphone jack
* Disassembling the phone and directing the sensor away from glass so it has nothing at all in front of it at all. Still registering 0.0cm.
* Swapping sensor and front camera from an i9300 which I understand is the same.
* A few different Kernels.
I have no screen protector, phone case, or crack in front of the sensor. I should however point out that i did a screen+frame swap from an i9300 which required some frame modifications, but i can't see how this would affect it... Unless perhaps it could be a grounding issue with some metal i exposed on the frame?
Any more ideas?
Okay so I wanted feedback regarding this whether someone else is experiencing this or not.
I have gradually observed during the last few days that a lot of my touches to click have gone unresponsive in Nougat. Initially it was something that I hadnt quite noticed but slowly the trend became obvious. Now dont get me wrong, this would happen a few times here and there with lollipop and MM as well, but the rate is far higher now on Nougat. Especially when typing on the keyboard this means mis-spelled words, missed letters, and accuracy is far worse now.
Has anyone else observed this or is it just me?
Just got my xcover 4 with nougat installed i have the same issue.
The sensitivity is low and i need to press a bit higher finger force to respond.
Even with sensitivity (glove mode) set to on things get worse.
I'm seeing the same thing. What is strange is that I'll see the button highlight/depress, but no action occurs. This is on multiple apps.
On what device/OS?
Sprint Note 5 on Nougat
Did you try gloves mode? Does it work?
the same for me on 920cd and the same iusse using S pen
I contacted samsung Greece about the existing problem.
I reported the problems me and you guys have and the tech support told me that your problems exist because you did not factory reset the devices before upgrading to nougat.
Anyone tried to contact samsung about the problem?
They dont know anything about it.
facing same issue screen lagging in note 5 sm-n920s also tried custom rom but still lagging in typing and scrolling on facebook
I have the same problem on my xcover 4 here!!
When I run the the touch screen test, touch screen responds well, but when I want to write a message or to scroll the home screen Its very annoying. It looks like software problem.
please help
Hi guys.
I have 2nd piece of Xcover 4 SM-G390F (first was change by seller for new one) and had the same problem. First 2-3 days all work perfect.. I have installed my applications, work perfect for two days, but after this... --After wake, display react only in centre area, 1 centimeter from display border no reaction or react on xxx touch. After few seconds (20-30) display react on full range, but with lags... So... I go for support to Samsung official at CZE.
Support tells me, that they don't know about this problem, that I'm 1st who has this problem... And some other bull... about unofficial sell and any other. So I post them IMEI and they let me know, if my distribution is official or not, and we'll see what next. They recomend me to go to service center, where somebody looks on my SM. So I see tomorrow.
ROM - official Android 7 Nougat from start using (not updated from other version)
Deleting apps - no effect
Safe mode - no effect
Factory reset - no effect
Apps to calibrate screen - no effect
Hi,
Using the Red Magic 3 is quite nice, but one of the major problems to me is the FingerPrint scanner.
It happens really often that I have to "press" the FP scanner several times before it lets me in
But on the other had, Face unlcok works superbly here !
It recognizes my face everytime, even in rather dark environment.
And unlocking is then super fast...
Guess I'll use that more often than the FP scanner
You guys also have that "problem" with the P scanner ?
No its working perfect for me, much better then the fp sensor of the xiaomi mi mix 2 (my prev phone). Meaby try to set it up again?
I had the same problem, then it went away, then it came back.
Saw some people complaining here as well on github.
Funny thing for me, seem to be related to having activated multiple users in this device and for some reason the finger print only works (normally) on this second account. Deleting that saving account did not solve the issue as the sensor continues completely irresponsive in my main account (so it's clearly just a software issue). If I recreate a second account it will work there, but still not in my main account.
Do you have more than one user registered for that device? I use the other users mainly to have alt accounts for different games
I'm in touch with their (slow) support and the last message I got was:
We will feedback this case to our R&D .Pls provide the order number and Build number of the phone.If you can, please also provide a video file of this process,thanks.
In my case it's clearly just a software issue, so it should be fixed in future builds (hopefully).
Perhaps a factory reset would help, but I don't want to test that option as I'm lazy to set up everything up again.
Hi,
Same thing here.
The FP scanner is not on par with some of the RM3 sibblings like the Mate 20x or the mi mix 3.
I think the scanner is too small to recognize your fingerprint decently.
But if I compare Face unlock on this device to face unlock on the afroementioned devices, it's a totally different story !!!
It is amazingly fast and reliable, even in low light conditions...
So I am almost always using that one.
Regards.
No problems here with the FP scanner.
I'm on Global ROM,bootloader is still locked,no root and only my account registered to the phone,but I've setup 4 fingerprints,and all of them work quite good....
Currently using PixelExperience Plus ROM. Was using HavocOS before this. There were similar issues in both the roms.. The proximity sensor just won't work during calls. Phone needs a restart to fix this.. goes back to problematic in a short while..
The autobrightness sensor issue is less frustrating.. waking up the device the brightness gets stuck at about 50%. The slider does nothing.. locking the screen and waking up again solves it. Minor issue..
But.. does anyone have a fix?
Same problem here with latest oficial rom. Randomly screen goes black in a call although the phone is on a table.
Same problem here
Why do Xiaomi seem to have such a problem with proximity sensors?
The one on my Note 7 doesn't work properly and a google search reveals complaints about sensors on many models.
It's not as if they are rocket science any more.
Could this also be the reason when I receive a call the phone screen on some occasions didn't even light up and I have to double tap to see who's calling. I really hope it's something they can fix.
Did anyone get a fix? I still have this goddamn problem! Even with the latest evolution x rom or pixel experience rom (tried the latest version released like days back for both roms). This problem started right after I unlocked my bootloader and flashed a custom ROM and the problem is present in EVERY custom rom that I've tried. Please help me out with a fix as this is really annoying and the phone is practically useless. As soon as I make a call or get a call my display simply shuts down and doesn't switch on until 30 secs after the call ends. So my display is basically off for easy 2-3 minutes. Can't use my phone then. This sucks when I've dialled a wrong number or want to cut the call myself because I can't do any of that!
I compiled and installed AOSP (Android Pie) from Sonys Open Devices page and it's running pretty well except for the following:
-) "Secure Startup" Option is broken - It kinda works but when you type in an incorrect PIN code the phone tells me that the code I entered was correct but that my data is corrupt and that I need to reset my phone. After a few restart attempts it then proceeds to work. Anyhow not working well and one little wrong click and the phone does a factory reset.
-) Fingerprint sensor - Works 90% of the time however if you "provoke" the phone by using a non-registered fingerprint a couple of times, turning the phone off and on, etc... Cannot say exactly what causes it - The phone reboots. Now this is not so bad, except that natural phone usage causes this once or twice a day - Random reboots through the fingerprint sensor. If I have no fingerprint registered the phone never reboots and all is good. So something is amiss here.
-) Bluetooth tends to fail somehow - It works and then after some random time people cannot understand me when I'm talking to them on the phone via my bluetooth headset
I've tested this with older pre-compiled version of AOSP Pie and the issues are the same. The issues are also present for the F8131 an F8132 model of this phone.
I'm really trying hard to fall in love with my Xperia X Performance but it's quite a struggle. The stock ROM does not allow RAW capture, hence I cannot install any version of GCAM that works. The Sony camera app produces mediocre pictures. Also the torch is very dim. Two things that really annoy me.
AOSP seems promising except for the issues listed above. Did anyone experience the same issues and possibly find a fix? If yes, please share. That would be awesome.
Thanks!