Proximity sensor causing problems to Knock Code, perhaps software issue? - G2 Q&A, Help & Troubleshooting

Two months ago I updated the firmware of my LG G2 D802 to Android 5.0.2 via the LG PC suite. After the installation I made a factory data reset to have a "clean" firmware.
Software info.
Kernel version: 3.4.0
Build number: LRX22G
Software version: V30b-EUR-XX
Currently this is the latest stock firmware.
I use the Knock Code as lock screen. The proximity sensor is causing a problem to the Knock Code after the update to Android 5.0.2.
It makes the smartphone believe that there have been 5 attempts to enter the code even if the screen hasn't been touched.
I've uploaded a video about the issue on YouTube.
Please search for "LG G2 D802 proximity sensor problem with Knock Code " because, as a new user, I'm not allowed to insert links.
It usually happens that the Knock Code recovery procedure is activated when I put the smartphone into my pockets.
The proximity sensor is working fine while phoning. I wonder if this could be a bug of the new firmware.
I installed the app Terminal Emulator. Is there a command to log the system related messages, something like the Linux terminal command tail -f /var/log/messages ?
In this way I could post the log and maybe a skilled user could help me to understand if it is a software or hardware problem.
Thanks for any help!
Bye!

Related

Knock Code only working when display on (after TWRP Recovery flash via Autorec)

Hi,
I wonder how to proceed on my problem, as the Knock Code doesn't work when the display is off. Instead, I have to Double-Tap (Knock On) first, then enter the Knock Code, as the display is turned on showing the usual Knock Code screen. I'd like to get Knock Code working as it was in out-of-box state, i.e. in display-off-state.
Right after unpacking the G2, I rooted via ioroot25 (4.4.2 Stock-ROM, Software-Version: D80220d-EUR-XX).
After installing/configuring all apps, I flashed TWRP Recovery via AutoRec.apk to be able to Nandroid Backup everything. Flash process was successful, but I noticed that Knock-On/Code wasn't working anymore.
Solution: Enter 3845#*802# in Dialer -> Settings -> Tap on Update Touch Firmware.
Result: Knock-On works, Knock-Code only after Knocking On, i.e. when the display is on and the Knock Code screen appears.
Question: Does anybody know, if this solves my problem?:
You can simply flash this kernel that support knock code, after you got TWRP with autorec.
http://www.androidfilehost.com/?w=files&flid=14195
Click to expand...
Click to collapse
I have no clue concerning the compatibility of the above mentioned kernel with my G2's state (4.4.2, rooted, AutoRec TWRP flash). How can I flash it and will it eventually bring Knock Code on turned-off display back?
Appreciate your help!

G2 D802 touch screen weirdness and baseband issues

Hi all,
A quick peek of touchscreen issues attached:
http://youtu.be/Hhuiv1SdsDQ
I enabled show touch options in usb debugging and took this video. Every touch on the screen is registering atleast two and mostly three touches as you can see in the vid. Any way to resolve it? I have tried to downgrade OS to 4.2 using LG Flash tool, and that doesn't work.
How do I fix this? Is it a hardware issue?
Baseband problem:
When I downgrade the phone to a D802 v10B or 10A, I lose baseband. Currently has India KitKat D802T20A_00.KDZ installed and baseband is present. Even downgrading to D802T10A_00.kdz loses baseband. Any thoughts why this is happening?
Try to go to hiddenmenu by dialing the number and then find update touch or something like that and or check your screen for dirt and clean it
fix found ?
I ran an update on my g2 from lg, and ended up with the same issue. Have you found a fix?
Same issue on my G2 (see my thread) but yesterday I gave up and send it to LG to fix it.
I tried nearly everyting I guess but nothing did help. Also the way into the hidden menu was without any result.
So I wish you good luck.
Me too!
I have the same issue. (VS980) It's impossible to use the phone while this is happening.
Now that I think about it, I didn't have any issues with this until after I installed the latest OTA
Anyone have any ideas to fix this??
Update
Finding out stock firmware and calling lg tech in the morning. Will update if I make any progress.
Reinstalled "out of the box" original rom ver. VS980-24A (.kdz) using LG Flash Tool. Problem gone - worked fine for several hours. Phone asked to install Verizon update VS980-26A, problem has returned. Called tech support, they couldn't understand the issue and decided my device was broken. They are sending me a replacement under LG warranty.
I used this for returning to "out of the box":
http://forum.xda-developers.com/showthread.php?t=2432476

Lg G2 D801 call sensor problem

I lollipop android update, Then I noticed that the phone proximity sensor work
In no way does not work now
1- I've tested the hidden menu : proximity sensor fail
2- LG FLASH TOOL I reinstall 4.4.2 android KitKat : results the same
does not work
What else can I do ?
Up: SOLUTÄ°ON
the phone was sold :/

Samsung J500F misterious lock screen bug

Model: Samsung J500F
Baseband: J500FXXU1BPF2 (Portugal)
Greetings to everyone.
My samsung j5 has a bug with the lock screen, which seems never ocurred with someone else.
It started when after i updated to Android Marshmallow after OTA updates and then i made a factory reset. After that i tried to put a Pin in lockscreen and after the pin was confirmed i locked the phone. When after a while i hit the button to turn the screen on it didnt asked the pin. In fact when i tried to change the pin in security settings it asked me a pin which wasn't the same that i put before.
To trying to solve this i though of doing a new factory reset, so i had to go to mysamsung.com to unlock the phone via remote controls and then i succefully reseted the phone.
The problem is that in the middle i forgot that and tried to do root but something went bad and i did lost the warranty but root didn't work. So a days after I tried to put a pass code and again the same error, this time asking for a password that didn't match mine.
I did some troubleshot:
-after Putting another pin the phone sends me to the previous page (security page) and instead of "pin" method to unlock screen it says "swip finger"
-it happens with passcode and pattern code too but when pattern code is choosed if i go to change it it firstly shows a pattern change screens but in a sec it dissapear being possible to put a new one and have the same bug
-I downloaded and installed a stock rom to my baseband and model (android 6.0 but my phone came with 5.1) and the error still exist.
-samsung support said to use smart switch initialization service but it says that my device doesn't support.
Notes: I didn't want to install a custom rom cause i like the samsung style.
Like i said: warranty is now voided (knox 0x1 (2)).
Any help would be apreciated.
Ps: I will provide screenshots and more info if needed.
Solved
Joylopes25 said:
Model: Samsung J500F
Baseband: J500FXXU1BPF2 (Portugal)
Greetings to everyone.
My samsung j5 has a bug with the lock screen, which seems never ocurred with someone else.
It started when after i updated to Android Marshmallow after OTA updates and then i made a factory reset. After that i tried to put a Pin in lockscreen and after the pin was confirmed i locked the phone. When after a while i hit the button to turn the screen on it didnt asked the pin. In fact when i tried to change the pin in security settings it asked me a pin which wasn't the same that i put before.
To trying to solve this i though of doing a new factory reset, so i had to go to mysamsung.com to unlock the phone via remote controls and then i succefully reseted the phone.
The problem is that in the middle i forgot that and tried to do root but something went bad and i did lost the warranty but root didn't work. So a days after I tried to put a pass code and again the same error, this time asking for a password that didn't match mine.
I did some troubleshot:
-after Putting another pin the phone sends me to the previous page (security page) and instead of "pin" method to unlock screen it says "swip finger"
-it happens with passcode and pattern code too but when pattern code is choosed if i go to change it it firstly shows a pattern change screens but in a sec it dissapear being possible to put a new one and have the same bug
-I downloaded and installed a stock rom to my baseband and model (android 6.0 but my phone came with 5.1) and the error still exist.
-samsung support said to use smart switch initialization service but it says that my device doesn't support.
Notes: I didn't want to install a custom rom cause i like the samsung style.
Like i said: warranty is now voided (knox 0x1 (2)).
Any help would be apreciated.
Ps: I will provide screenshots and more info if needed.
Click to expand...
Click to collapse
Hey everyone.
Turns out that after almost two months Samsung relased an updated that fixed this error.
Joylopes25 said:
Hey everyone.
Turns out that after almost two months Samsung relased an updated that fixed this error.
Click to expand...
Click to collapse
With installing the new update your phone baseband is still J500FXXU1BPF2 or something else?
saeid.1980 said:
With installing the new update your phone baseband is still J500FXXU1BPF2 or something else?
Click to expand...
Click to collapse
Actually with this new update the baseband still the same but when I updated the Android 5.1 to 6.0 the baseband changed.

Need help downgrading stock Oreo to MM or Nougat (with locked bootloader)

Edit: I worked out my issues, I'll leave this here in case others have similar trouble:
I needed to manually add in the RAW F53XX files from the github (https://github.com/Androxyde/devices/tree/master/F53XX), this allowed Flashtool to correctly detect the type of phone and apply the fsc. I was then able to flash my desired firmware, I chose the 6.0.1 release for Journalists to begin with as a test. This confirmed my suspicion that it was a software update issue causing the proximity sensor to malfunction (stuck on) and also fixed up the FACTORY STARTUP SERVICE-POWER OFF bug and the Warrantytimeservice permanent notification. I can now look at updating to later versions of Android and find the latest version before I have issues again.
---
tl;dr - I need a guide that actually works on downgrading the F5321 to a specific stock Android version with a locked bootloader.
I recently received a new, old stock version of the X Compact (F5321) that appears to be a HK variant as it started up with the Chinese language selected.
It was initially stock Android 6.0.1 with no apparent problems. After OTA updating all the way through to 7.1.x and onward to the latest 8.0, I now receive the "FACTORY STARTUP SERVICE" problem. Even if I'm quick enough to disable the service for the service flag, the proximity sensor does not work as well after updating, making phone calls impossible. I believe the issue is all related to software, not hardware. I want to downgrade to 6.x and go from there before I have to send it back for another replacement.
I'm having trouble with getting Flashtool to correctly detect and identify the firmware files that I want to flash. I want a completely stock version of Android, so keeping the bootloader locked is fine for me.
After downloading the firmware that I want to try, XperiFirm will close and Flashtool will successfully build the FTF. After clicking the lightning bolt > flashmode > the firmware list is blank.
I'm using Flashtool 0.9.26 (I have tried older versions as well with the same problems) with driver signature enforcement disabled and correct drivers installed to detect the phone.
The last time I used Flashtool was to flash my older Z5 Compact, I didn't have any issues then and it was all done within 10 minutes. I've already spent more than 5 hours on this phone and would appreciate any help.
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
pseudonym58 said:
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
Click to expand...
Click to collapse
The "FACTORY STARTUP SERVICE" and to a lesser extent, "Warrantytimeservice" problems surface only in the later version of Android. The only way I could remove them was by staying on 6.0.x only. Anything higher, and the problems show up again. It seems to be a byproduct of upgrading the HK variant that wasn't designed to actually be software upgraded - you won't be able to have the US 8.x firmware on the phone.
Sorry to say, but you'll be stuck on 6.0.x if you want a usable phone. I should mention that I was never able to maintain a newer firmware on that particular phone.
I've since sent the Compact X back (it was meant to be a gift) and replaced it with a Samsung A20.
h
I'm using SO-O2J and a sim card not docomo. Use the "Repair" in Xperia Companion and it auto flash Android 7.0
..
PioneerSeeker said:
Try different region's roms on www.xperiablog.net and I hope you'll be successful to find nougat or oreo at last for your phone.
Remember xperia devices do not need to unlock bootloader for downgrade...
Click to expand...
Click to collapse
Thanks; I was able to obtain an X Compact originally for the UK market, and was able to successfully flash the US Oreo firmware. All seems to be in order.

Categories

Resources