Develop Bugs

Sensors issue (acc., pros., gyro., lux). Android 5.0.1

My devices setting: stock OS, stock kernel, latest twrp and chainfire rooted. Nothing else. I updated from Android 4.4.4 straight to 5.0.1 (5.0 skipped) with fastboot clean flash, data, cache wipe.
So, the story went like this. I read a book on Google Play Books in landscape, then I put my device into sleep mode by closing the magnet cover. I closed it in landscape mode and left it in landscape.
Later, when I wanted to use my device again and I opened the cover to wake my device, the display was stuck in landscape. I didn't lock the autorotation.
I downloaded the app "Sensor Kinetics-Innoventions" to make tests of my device's sensors, pretty every kind of sensors. Here are the results, I attach some screenshots showing that the sensors cannot be detected at all (no numbers indication changing around. If you don't understand what I mean, try out the app yourself).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See, even the lux sensor doesn't work. Now my screen brightness doesn't adjust to the surroundings even when "adaptive brightness" is switched on my device.
FYI, I did a clean update from KitKat 4.4.4 to 5.0.1 skipping 5.0 using fastboot and official from factory image extracted system.img, boot.img, etc., wiped data and this kind of bug is what I encounter.
Normally, when the sensors are working, the app would show something like this (after reboot it fixed the issue, but only for a short time and I quickly made a screenshot):
The thing is, now, even a reboot won't fix the sensors issue. I am not in a mood to do all this flashing and setting up again, don't have that f*cking time. [emoji36]

Finally, I found a solution and temporary fix. The bug is actually caused by Google Now (I don't know which version though, maybe the lastest). I went to the Google Now "Ok Google voice recognition on every screen" and disabled it, rebootet and voila all sensors are working again. It has something to do with Google Nows constant voice recognition-ish thing. So this fix worked for me. Anyone wanted to know, here it is. Cheers and peace.

Nice to know

impressive!!! worked for me as well !

LG G4 (H815) - Missing (Stock) Recovery-Mode/Hardreset-Mode?

Hello XDA-Community!
After roundabout 8 Weeks of using my LG G4 (last year), it was demaged and restarted all over without a reason - so I contakted my provider for a repair - it was sended to w-support(.com) - it returned but wasn't repaired. Only thing that changed was, that I had Android v5.1 against v5.1.1 before the *repair* and the continuesly restarts were still happening. I tired to enter the Recovery-Mode by button-combination, but this wasn't possible... same for the Hardreset... so I was forced to enter the Hardreset by the running OS - this worked.
(After it was sended directly to LG-Support, it came back and worked again as it should, without 300 restarts a day... some memory-unit was demaged on the bord... however it fine now... BUT...)
Now ... I want to get back this STOCK-RECOVERY-MODE because I want to root this phone now! - last week I was able, after the contakt to LG-Support, to get the Android Update by OTA - for some reason, there are still devices which aren't able to get this update (even by PC-Software), because of something coupled with the IMEI (because the support asked for my IMEI and after only 1 day, I saw the update-info on my screen[?]!). Still strange sh**, but okay however, finally I got the update, but now I am struggled by the problem of the missing Recovery-Mode... what the Hell may I am able to do, to get things running??
I tried the "fastboot" or "LG-Method", by ADB-Connection to the PC, to unlock the Bootloader, but cmd isn't able to find my device, that's the first problem, why I am unable to unlock my bootloader directly, by the LG-Method (let's say LG-Method, because of the steps you have to make on the LG-Website, okay).
So all methods, based on the official Bootloader-UNLOCk are out for me... so what is left or do I have to recover the Recovery-Mode - and if I have to, then please tell me how!^^
By the way - after W-Support repaired my older LG G2 - there's also no Recovery-Mode anymore and also the Hardreset is bombed away, but device runs nicely! - There, I was able to get rootaccess back, by nvflash!
I hope, that I can get help here... this turns me scary as crazy!^^
SW-Update-Mode is availlable by Volume Down, without the battery - coupled to the PC... but the other method, by Volume Up and Power On-Button isn't availlable (?!)... so strange... what they had done to my phone?! - This wasn't meaned by the task to "REPAIR" the phone...
Some (mostly) needed information:
Android v6.0
Baseband-Version: MPSS.BO.2.5.c3-00101-M8992FAAAAnAZM-1.31581.1
Kernel-Version: 3.10.84
Build-Number: MRA58K
Software-Version: V20d-EUR-XX
I'm looking forward to your replies!
With friendly special thanks,
Reaper
>>>EDITED!<<<
Hello again Ladies and Gents,
As far as I am now, I was finally able to find my device below "adb devices", but now I got the thread with the PRE-Rooted System.img:
Link1: Click me!
and
Link2: Click me!
> question is now: "Is this compatible with my device?" - Because, I read "Problem may be because of latest OTA..." - this means the Android vX.X.X -> But which one they got to get the problem as same for the Method itselfs, isn't named in which ANDROID VERSION(S) - this Method is working or NOT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Happy about any responses to me! - As you can see, but only if I do understand this method the right, it might be a method without the unlock of the bootloader, right?
With friendly greeting again,
Reaper

[VZW VS986] Apps disappearing after rebooting

Phone details:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LG G4 Verizon Wireless VS986
Stock everything, unrooted, and up-to-date as of post
Android Version: 6.0
Security Patch Level: 2016-03-01
Kernel: 3.10.84-g4790274
Build: MRA58K
Software version: VS98625A
Device encryption enabled, but not on the SD card.
All apps are installed on the device. The SD card only contains music, podcasts, and pictures.
Issue: Starting this week some times when I reboot there are missing apps when the phone powers back up. I havent noticed this after every reboot, but maybe i...just havent noticed.
A few days ago I rebooted my phone to see it "Optimizing apps" after entering my encryption password as if I had cleared dalvik cache or performed an OS or kernel upgrade or something. After completion the phone started up as normal but probably a dozen apps were missing. Most notably Hangouts, my calendar app, and Google Now... I rebooted again 2 nights ago and Pocket Casts, my budgeting app, and Light Flow, amongst others, were missing. I rebooted again this morning and my fking launcher was missing (Nova). WHAT THE HELL IS GOING ON WITH MY PHONE?
Even stranger is when I reinstall an app I barely need to change any settings; the data must still be on the phone because almost all my settings and profiles are immediately present. When i re-installed my budgeting up I was still signed in and synced (cloud subscription service). When i reinstalled Nova my desktops were exactly how they were minutes earlier before the reboot. After re-installing Hangouts I was still signed into the appropriate google accounts and not signed into the one I don't use for Hangouts. When I re-installed Google Now I wasn't even presented with the setup wizard and tutorial and all the cards I'd expect were there and accurate.
Since the VZW G4 is not easily rooted or bootloader unlocked not only have I been stuck with whatever Verizon and LG deemed worthy of me using (read: NOT using) in addition to already being on my second phone due to the boot loop hardware issue., but now i've got this to deal with? This phone was supposed to be awesome, but if not for the removable battery and sd slot I'd have moved on months ago.
I'm gonna FDR this evening or tomorrow evening if I can't find a real solution. Has anyone seen anything like this before???

bump

Personally I hadn't heard that before, but a quick (Google) search indicates it's happening with various phones. My first thought was check for virus..

Performed a FDR this week and the issue has been resolved. Super weird.

Phone Bricked or Infected - weird artifacts and bootloop (S4 i9505)

MY PROBLEM IS INSANELY RARE AND (propably) HARD TO FIX
Hello!
I've had i9505 for over 4 years now, I had many problems with root, custom rom etc but I always find ways to fix them - not this time!
Since yesterday, I can't boot to the system. It started when I was just in my ES file explorer and suddenly some weird artifacts popped up and I couldn't see anything (its not a physical screen problem!) then my phone turned off itself so now, I'm trying this:
Hikd power button --> *short vibration* --> Samsung S4 logo pops up --> black screen --> again vibration --> ... and again and again. It just loops here.
So I left it for a night hoping that when I wake up it will be finally working again but no, NOW it was stuck on 'SAMSUNG' logo (the one with a blue background). So I pulled out the battery and the phone started restarting again (boot loop).
But there is something new about this situation. Every 2 or 3 restarts there are ARTIFACTS on the screen. For now, I've experienced 3 different ones and I managed to catch one of them with camera (see image below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is another one with a blue code in really small size, couldn't catch it fast enough tho.
This is what I have been doing with my phone before all this crap happened:
1. I installed 'Udemy' app from Google Play
2. I installed Modded Google Play via Lucky Patcher
3. I updated Lucky patcher
4. I edited build.prop to make my phone visible as s7, but then i changed it back
I think these artifacts may be caused a virus or just broken system files - I don't know :/
And pretty much that's it. I really want to know what possibly could cause this issue.
Please, everyone, I've always found ways to fix problems without flashing phone, so I believe I can now.
I have access to download mode and TWRP recovery.
But one more thing about TWRP - when I try to copy a file or wipe cache, error message pops up "E: Unable to mount storage". Is it possible, that for the first time ever my phone actually got infected?
If I catch any new artifacts, I will show them here.
I would be grateful for any help at this point, thanks
LOGCAT FILE:
https://pastebin.com/sPDJ0QQP
TWRP RECOVERY FILE:
https://pastebin.com/2Y0Fmew5
//Edit I'm not sure if the images are visible although the links are okay

[QST] - N976B - S-Pen stopped working after rolling back to stock

Hi there,
I have an issue with my S-Pen. it suddenly have stopped working with my device.
I own a N976B Note.
I guess it is an issue with the firmware, because the stylus is recognized on my other devices and the other styluses are not recognized on my note.
To help you understand the history i want to sum up some steps.
1. my phone had a t-obile branding, witch i wanted to remove, so i flashed another csc rom to get rid of that. (back in 2020)
2. After some annoyance by advertisement and the wish to get root and a custom rom, i installed Dr.Ketan Rom and was pretty satisfied, but the hassle with manual updates was a draw back, so i decided to roll back to complete stock to get OTA.
3. After some huslte and some rookie mistakes by trying to install a n975 stock rom on my device, i figured it out and flashed the matching rom. but now the stylus or the digitizer seems to be corrupted. the firmware version is not recognized by the phone. see the screenshot below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After some attempts to get it running again, i installed the very stock rom for my phone several times. (N976BXXS7FUI1)
I even checked "re-partition" and flashed with the matching pitfile in odin.
But there still no luck.
do you guys have some tips?
big thanks in advance!
greeting

Play with it. Spen's can be ornery as mules, once you get it going you're good.
They don't like being neglected for months.
My stock one was neglected. Took a couple days of playing with and then boom it stated charging like nothing ever happened.
Until it shows it's taking a charge it will do nothing. It will play dead.
Try clearing the system cache, reset network, pray to the pagan gods, play with it more... in and out, etc. Try enabling multiple spens, try disabling same... don't cross your spens, use the one for the 10+
Guess it just needs a good fk to get it going
I have 2 10+'s, both stock* and both run very well. Loading custom roms isn't needed, can kill desirable features and makes troubleshooting** much more difficult. That said if you're back on a stock rom the spen and associated hardware/firmware/software are likely good... it's just showing you who's boss. Play with it at least once a day, it will likely perk up in a week and stop it's wallflower act.
*with a package disabler and heavily optimized. I never update if it's running fast and stable; many apps are still running on their factory load as well. One 10+ is running on Pie, one on Q.
**Do Not enable power management. Make sure you didn't disable a needed parent/dependency apk! Do not ever, ever load Android 11 or higher, the kiss of death. Of course I could be mistaken, but probably not...