Hello
Has anyone had an issue with, the velvet touch not extending to the top of the phone?
I've turned on tracing via dev tools and I get a perfect line about 7mm from the top (essentially top bar +).
I've called LG but it is out of the warranty period. I thought I would flash an older Rom and hope that fixes it, then update as I go. But LG doesn't seem to make its ROMs available. And getting to fastboot screen is harder than Samsung.
Any ideas?
Quick Q&A
* Yes I removed the screen protector
* yes I've rebooted
* yes I've factory reset it
* yes I applied the recent update
* Yes I tried recalibration tools
* yes it is oem
* no it is not rooted
* no the screen is not cracked
* no it wasn't dropped
* it happened partially after the summer ('22) ota update. The issue was on halfway through the top bar.
* it dropped to the ~7mm mark after the fall update.
* no change on the last one.
* yes I've looked online to see if there was any other similar question
* yes I did tell my mother she wasn't lying to me about being special
Oh yeah
LM-900GUM
Related
JUST AN INFORMATION if u ppl are building CM 10.1 kernel and facing same issue >
adfad666 (RD) said -
I have been modifying the Sony kernel sources, and porting our 4.1 kernel to a 4.2 CAF branch to be used with CyanogenMod 10.1 and above. We will eventually receive Android 4.3 direct from Sony, and therefore suitable kernel sources, but if we can beat them to it, why not?
However our Xperia SP has a very temperamental screen, it really needs a perfect frame buffer or it will crap out on you with no apparent way back.
If you flash a kernel with a broken frame buffer (a kernel that does not send the correct signals to the display), you will see nothing on the screen, sometimes random vertical lines, then your device will get into a low level bootloop, (ADB will not be available) and even if you flash a working kernel from a factory image this will not recover the device. Basically, the screen gets stuck in a non-functional state, the device is able to detect this and immediately hard resets, so your device seems hard bricked.
Well... almost.
Fortunately, Sony build into their factory images a special lock that, on first boot, nothing can cause the device to shut down or reboot. Therefore to break this hard brick, you need to do a full wipe with flashtool.
On reboot the screen will still be broken, but it will do a full boot (you will eventually hear touch sounds when pressing the screen). You can now hit the power button to switch off the display, hit it again and your screen should, finally, come back to life.
* * * * * * * * * *
Why does this happen? My guess is that a specific set of commands must be used to control the display. Any deviation from that set and the screen gets stuck in a non-functional state, and the only way to recover is to eventually send the correct off/on sequence to it.
However this can only happen from a working rom, but due to the auto detect of the broken screen and hard reset (forcing the hardware to switch off without sending an off command to the screen), this can only happen after a full wipe to recreate the first boot sequence.
Therefore if you are experimenting with the kernel you need to be aware of this... 'feature' and that luckily there is a way to recover from it.
I have needed to recover my device three times now with this method and I haven't even owned it for a week yet. I have never seen such behaviour on any of the other devices I have worked on, so this is going to make kernel porting a tricky and tedious affair. The fact that the screen 'remembers' your bad kernel even after you flash a good one is pretty disturbing. (I even left my Xperia SP powered off for over an hour to see if the lack of power would reset the screen, but no change)
official thread > http://forum.xda-developers.com/showthread.php?t=2457353
is this happen to our mobile also ? because both mobile are released at same period
Thanks
the are relased in simillar time,but both have different screens,sp have hd and we have FWVGA screen,we have also different lcd density,so i think this will be only on sp not on L.
Well, we've booted cm10.1 to homescreen. I had already adjusted frame buffer ( same as we do in recovery ) and it works fine.
A quick comparison between msm_fb.c ( video driver) in our stock kernel sources and MSM8930 CAF sources will tell you that sony team uses special CCI drivers to control the LCD... For eg brightness etc.
Without them, I doubt screen will work functionally.
Thankfully, the stock kernel booted cm10.1 without any major changes ( except frame buffers fix ) .
Hi, I've seen a related post reg. Xposed framework for our phones, did however see the "need" of starting a new one here.
Anyone having Xposed installed and facing issues:
* serious lag
* random reboots (last week up to 5 per day, de-activating resluted in an immediate "reboot-stop")
* severe battery-drain (just having the screen active resulted in a visible decrease per minute....)
I had themeinstaller applied (love the CM10 thems) as well as advanced power (reboot) and sofkeys.
I did try desabling 1 at the time, nothing worked/helped until finally deactivating framework itself.
Current environment:
* stock
* unlocked B/L
* (rooted...)
* used the latest frameork downloaded form the site
I really love having it, and don't just now want to go to CM11 (waiting for a RC or similar).
txs for the feedback,
cheers.
Hi,
I have never had issues with MX Player, but right after Lollipop => Marshmallow (HTC Sense) upgrade it started to crash very often.
HW/SW: HTC One E8 / Android 6.0.1 ... Sense 7.0 ... Soft.no 3.07.401.1 (stock non-rooted)
* Crashes most often when starting to play a video, turning off screen, going to home screen etc., but is not necessarily limited to that
* Once it's playing and is not manipulated with, most often it will play to completition.
* None of this ever happened to me before the upgrade (and the one before that)
* Tried to reinstall the app, but it didn't help
* Restarting phone didn't help
* Was happening before setting a custom codec, with it as well, when switching back default didn't help
* I don't experience any issues with other apps
* Not running any security app, and I'd say no suspicious app
* Seems less prone to crash with SW decoder, but still does with all of them
* Seems to happens with all the videos.
* Not sure it's related, but sometimes when starting playing it really freezes the system and has to be force stopped ... but this is rather rare
Managed to capture some logcat, hope it will helpful + attached the debug report created by MX Player.
Thank you!
NoxArt said:
Hi,
I have never had issues with MX Player, but right after Lollipop => Marshmallow (HTC Sense) upgrade it started to crash very often.
HW/SW: HTC One E8 / Android 6.0.1 ... Sense 7.0 ... Soft.no 3.07.401.1 (stock non-rooted)
* Crashes most often when starting to play a video, turning off screen, going to home screen etc., but is not necessarily limited to that
* Once it's playing and is not manipulated with, most often it will play to completition.
* None of this ever happened to me before the upgrade (and the one before that)
* Tried to reinstall the app, but it didn't help
* Restarting phone didn't help
* Was happening before setting a custom codec, with it as well, when switching back default didn't help
* I don't experience any issues with other apps
* Not running any security app, and I'd say no suspicious app
* Seems less prone to crash with SW decoder, but still does with all of them
* Seems to happens with all the videos.
* Not sure it's related, but sometimes when starting playing it really freezes the system and has to be force stopped ... but this is rather rare
Managed to capture some logcat, hope it will helpful + attached the debug report created by MX Player.
Thank you!
Click to expand...
Click to collapse
Can you disable HW+ from decoder settings & try again? Marshmallow upgrade on many HTC device leads to crash when hardware acceleration is used.
Sent from my SM-G900H using Tapatalk
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Detailed installation instructions:
Install LineageOS on cheryl
Detailed upgrade instructions from previous version:
Upgrade LineageOS on cheryl
Download link:
LineageOS Downloads
Recommended Google Apps package:
MindTheGapps (choose ARM64 11.0 zip)
Changelog:
Changes for cheryl
Bug reports:
How to submit a bug report
LineageOS GitLab
Known bugs (won't fix):
- Can't switch FPS to 60 (can only switch between 90 and 120)
- Can't switch screen resolution (defaults to 2560x1440)
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Recommended 9.0 - P-MR2-RC001-RZR-N.7083 (automatically installed with the ROM)
I just wanted to post here that the newest update (April 17) seems to have fixed the not charging bug for me.
If I install this ROM and Gapps, will it pass security and I can use Gpay and wear OS with no issues? I don't want to use magisk or Xposed. Tia.
Just an FYI the May 15 update has started some random phone freak outs where it seems like I'm swiping everything at once/touching all over the place. Basically total screen freak out/ lock up. Usually fixes itself after turn off screen then turn screen back on. Did not have this issue in the may 8th version.
I've decided to install this Rom anyway. Magisk has passed CTS and I can use Gpay and various banking apps using Magisk hide. Phone is working well with good battery performance.
No bugs found so far.
initially my fingerprint sensor was working after installing then it stopped. i tried reset , re install everything.
how can it go again suddenly. second time. last time installing your rom fixed it . but not anymore after an update in your rom.
can you tell me how to fix it?
VERY occasionally my fingerprint stops working. Lock and unlocks fixes though.
I've installed the ROM yesterday and the only issue that I have is the wifi hotspot doesn't work. It shows that is open but none of my devices can see the network, I try to set manually the SSID but still doesn't work. Has anyone else the same problem?
Thanks for the ROM. It is buttery smooth and all apps are functioning well. However, I am still having an intermittent issue with the battery refuses to charge while it is on (with the message "...can't charge at the moment"). Restarting the phone will not resolve it. The only way to get the battery to charge it is to plug the charger while the phine is off. On some other ocassions, it charges ok while the phone is on - but this is very rare. Hoping for a resolution to this issue.
Looking to go from 17.1 to 18.1 soon.
Just checking, can I keep my data intact?
Also, I'm using adoptable SD storage on 17.1. Any precaution I should take before installing 18.1?
munsened said:
Just an FYI the May 15 update has started some random phone freak outs where it seems like I'm swiping everything at once/touching all over the place. Basically total screen freak out/ lock up. Usually fixes itself after turn off screen then turn screen back on. Did not have this issue in the may 8th version.
Click to expand...
Click to collapse
I have this same problem, pull down menu will come down halfway and screen will just go absolutely nuts. got to the point screen was completely frozen and couldnt use the phone at all. Replaced it with Pixel Experience and so far not seen one problem with it.
Still using this ROM with 0 problems as daily.
I can't get my Type-C to HDMI (and USB Type-A) dock working with this. Dock was working perfectly on Android 9. Would appreciate direction, but may try 17.1 to see if Android 10 has better success. Trying to use old Razer Phone 1 with monitor as shop google/youtube terminal.
Possibly issue with 120fps lock applying to external displays?
I also cannot use usb-c to 3.5mm adapter for headphones.
Idk if this is ROM related or if it's the unsupported adapter as it's not official Razer.
Randomginger said:
I also cannot use usb-c to 3.5mm adapter for headphones.
Idk if this is ROM related or if it's the unsupported adapter as it's not official Razer.
Click to expand...
Click to collapse
I'm still on LOS17.1 (2021.11.3) but also had the problem with the official Razer usb-c to 3.5mm adapter not work. I think it's LOS.
For those of you who installed this, did you notice any sound volume issues? I have noticed that the speaker volume is much lower on LineageOS than it was on stock 9.0. Is that just me?
.ezhik said:
For those of you who installed this, did you notice any sound volume issues? I have noticed that the speaker volume is much lower on LineageOS than it was on stock 9.0. Is that just me?
Click to expand...
Click to collapse
I disabled the AudioFX app that came with LOS. That greatly improved the sound quailty
brahma1 said:
I disabled the AudioFX app that came with LOS. That greatly improved the sound quailty
Click to expand...
Click to collapse
I went back to stock and noticed that the whole difference is due to Dolby Atmos pre-installed App. I wonder if someone was able to extract that APK?
Dolby has lots of closed source framework dependencies so we can't really make it work outside stock OS.
Thank you for the rom but I notice text messages can't send using LTE network only 3g. Does anybody have this issue? Thanks in advance
A while ago—and I didn't think I noticed it right away, so it's hard to say exactly when or if it was immediately after an Android update—my Pixel 4a's gyroscope and accelerometer stopped functioning. I installed the sensor logging app phyphox from F-Droid and it tells me my device doesn't appear to have a gyroscope or accelerometer, although other sensors like the light and proximity sensors work. I am running stock Android with the latest updates. The phone is otherwise functional, but the problems I've noticed are:
* AR/VR functionality doesn't work at all
* Location sensing is less accurate when stationary or at walking speeds
* I can't rotate the screen even with Auto Rotate enabled, except in apps like YouTube that enable manual rotation
* If I take photos or videos in landscape orientation I have to manually rotate them afterwards
I tried uninstalling some old apps and starting the phone in safe mode, but the problem of not being able to rotate the screen with Auto Rotate persisted. I then tried a factory reset; this didn't help either. Today I got the update from Android 11 to Android 12; the update went fine but I still have this problem on Android 12.
Has anyone solved this issue with the Pixel 4a? What should I try next?
Reflash to last working rom.
If that fails it likely a mobo failure.
Once I have a fast, stable OS that's fulfilling its mission I don't update. Updates aren't needed or even desirable most times* especially since Android R raised its ugly head.
Pie and Q are still the more desirable variants.
Since Q Android has been in a high G flat spin and all they do in response is mash the throttles into the full afterburner indents.
That won't get it... *splash*
Scoped storage splashed 2x
*if you the latest Android hype, yes; if you want the most functional and user friendly, no.
Choose wisely or your it's a lick on you.
lunasspecto said:
A while ago—and I didn't think I noticed it right away, so it's hard to say exactly when or if it was immediately after an Android update—my Pixel 4a's gyroscope and accelerometer stopped functioning. I installed the sensor logging app phyphox from F-Droid and it tells me my device doesn't appear to have a gyroscope or accelerometer, although other sensors like the light and proximity sensors work. I am running stock Android with the latest updates. The phone is otherwise functional, but the problems I've noticed are:
* AR/VR functionality doesn't work at all
* Location sensing is less accurate when stationary or at walking speeds
* I can't rotate the screen even with Auto Rotate enabled, except in apps like YouTube that enable manual rotation
* If I take photos or videos in landscape orientation I have to manually rotate them afterwards
I tried uninstalling some old apps and starting the phone in safe mode, but the problem of not being able to rotate the screen with Auto Rotate persisted. I then tried a factory reset; this didn't help either. Today I got the update from Android 11 to Android 12; the update went fine but I still have this problem on Android 12.
Has anyone solved this issue with the Pixel 4a? What should I try next?
Click to expand...
Click to collapse
I'm having the exact same problem..have you find any solution yet?
samrattt said:
I'm having the exact same problem..have you find any solution yet?
Click to expand...
Click to collapse
Nope. I haven't tried downgrading or flashing ROMs because I'm worried it will interfere with my employer's device policy that allows me to view my work email, calendar, etc on my phone, and also because I don't really have the time. So for now I'm just living with the issue.