Related
I randomly realized my G4 wasn't rotating the screen anymore and I have since tried everything - factory resetting, calibrating the sensor (doesn't work) and even the banging phone on table method, none are successful.
This may indicate that it is a hardware issue but if I hold the phone landscape and open the camera the buttons do rotate, but if I rotate whilst already inside the app nothing changes so I'm not exactly sure what is going on. When I use the app CPU-Z to track the accelerometer value it stays static until I turn the screen off and move the phone a bit, when I turn it on the value changes again but stays still.
Any idea what the cause is??
does booting into safe mode make any difference (i know you said factory reset, but I'm curious).
Also, probably won't, but is there any difference whilst the phone is charging?
Throwing this out there. Did you debloat? On the Samsung models, if you uninstall the Hub app, rotation gets broken for some weird reason. I don't know what that would be on the G4, but maybe? Just a random guess.
lawrence750 said:
does booting into safe mode make any difference (i know you said factory reset, but I'm curious).
Also, probably won't, but is there any difference whilst the phone is charging?
Click to expand...
Click to collapse
I'll try booting into safe mode, and there's no difference while charging.
pre4speed said:
Throwing this out there. Did you debloat? On the Samsung models, if you uninstall the Hub app, rotation gets broken for some weird reason. I don't know what that would be on the G4, but maybe? Just a random guess.
Click to expand...
Click to collapse
I believe I did remove a few apps but since I factory reset and flashed a fresh image I believe they should be restored?
wilfred888 said:
I'll try booting into safe mode, and there's no difference while charging.
I believe I did remove a few apps but since I factory reset and flashed a fresh image I believe they should be restored?
Click to expand...
Click to collapse
Not necessarily. I know a factory reset doesn't restore any previously removed apps, and flashing factory a fresh image depends on how it's flashed I've discovered. Only a CSC restores the phone to factory specs, while other methods didn't for me.
pre4speed said:
Not necessarily. I know a factory reset doesn't restore any previously removed apps, and flashing factory a fresh image depends on how it's flashed I've discovered. Only a CSC restores the phone to factory specs, while other methods didn't for me.
Click to expand...
Click to collapse
Safe mode didn't help, and I actually don't know which ones I removed but they looked pretty normal, how do I check or compare vs stock?
wilfred888 said:
Safe mode didn't help, and I actually don't know which ones I removed but they looked pretty normal, how do I check or compare vs stock?
Click to expand...
Click to collapse
I think I recall seeing a debloat list somewhere. See if you can find it and compare what you've got. I'm not saying this is the problem, but it could be.
pre4speed said:
I think I recall seeing a debloat list somewhere. See if you can find it and compare what you've got. I'm not saying this is the problem, but it could be.
Click to expand...
Click to collapse
Yeah I found a few lists but they only have apps that are safe to remove and don't warn or mention possible ones that cause problems which I may have already removed
wilfred888 said:
I randomly realized my G4 wasn't rotating the screen anymore and I have since tried everything - factory resetting, calibrating the sensor (doesn't work) and even the banging phone on table method, none are successful.
This may indicate that it is a hardware issue but if I hold the phone landscape and open the camera the buttons do rotate, but if I rotate whilst already inside the app nothing changes so I'm not exactly sure what is going on. When I use the app CPU-Z to track the accelerometer value it stays static until I turn the screen off and move the phone a bit, when I turn it on the value changes again but stays still.
Any idea what the cause is??
Click to expand...
Click to collapse
I had the exact problem a few weeks ago, thought my hardware was already flaking. Don't remember what I did to get it working, but it wasn't overly complex.. Rebooting didn't help, I think I pulled the battery, waited a bit, and then rebooted and then went to calibration from there.
Do you happen to have xposed installed by the way?
Sent from my LG-H812 using XDA Free mobile app
strikelight said:
I had the exact problem a few weeks ago, thought my hardware was already flaking. Don't remember what I did to get it working, but it wasn't overly complex.. Rebooting didn't help, I think I pulled the battery, waited a bit, and then rebooted and then went to calibration from there.
Do you happen to have xposed installed by the way?
Sent from my LG-H812 using XDA Free mobile app
Click to expand...
Click to collapse
Hey thanks for your reply, I am trying now the battery pulling method, did you then calibrate through the sensor in display settings?
And yeah I do, hmm not sure if it stopped working after that actually.. but I remember after I flashed a fresh .kdz even without xposed it still doesn't work.
wilfred888 said:
Hey thanks for your reply, I am trying now the battery pulling method, did you then calibrate through the sensor in display settings?
And yeah I do, hmm not sure if it stopped working after that actually.. but I remember after I flashed a fresh .kdz even without xposed it still doesn't work.
Click to expand...
Click to collapse
Yea would have been the calibration from the regular settings.
As for xposed, flashing a kdz will keep user data and settings.. It might have been gravitybox causing the issue for me, which if you uninstall that, reboot and reinstall it, might help. Same goes for any other modules you had enabled.
Sent from my LG-H812 using XDA Free mobile app
strikelight said:
Yea would have been the calibration from the regular settings.
As for xposed, flashing a kdz will keep user data and settings.. It might have been gravitybox causing the issue for me, which if you uninstall that, reboot and reinstall it, might help. Same goes for any other modules you had enabled.
Sent from my LG-H812 using XDA Free mobile app
Click to expand...
Click to collapse
Oh yeah it did but I factory reset as well so... I never installed gravitybox since I heard there were some problems with it but I'll see if there are any modules causing issues.
Silly question: Have you tried clicking the rotation icon in the pull-down notifications bar?
alamo76 said:
Silly question: Have you tried clicking the rotation icon in the pull-down notifications bar?
Click to expand...
Click to collapse
Yeah I have I don't even know there are signs that point towards it being a hardware or a software issue tbh.
Problem happened to me too. Started yesterday, sometimes worked, sometimes stuck on portrait.
Shutting down and pulling the battery for a few seconds seems to do the trick. It works properly now..
Have you been used apps which could calibrate the accelerometer before?
etc. some games that needs to be controlled by rotating the phone on its axis..
onotor said:
Have you been used apps which could calibrate the accelerometer before?
etc. some games that needs to be controlled by rotating the phone on its axis..
Click to expand...
Click to collapse
Me? Not that I know. Some new apps yes, but still proper screen rotation.
This problem happened on my g4 today...
Stock ROM?
LG 4 not rotating??
quick fix which worked for me was just take the battery out, wait 30 seconds, put back in switch on and problem solved...
hope this helps guys.... regards Steve
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
broky said:
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
Click to expand...
Click to collapse
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
levone1 said:
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
Click to expand...
Click to collapse
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
broky said:
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
Click to expand...
Click to collapse
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
levone1 said:
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
Click to expand...
Click to collapse
thanks mate i m working on it and i ll repopt back if i solve it and how or need more help
SOLVED:after a lot of testing found out that my problem was xposed framework v74-sdk22.
from the moment i installed xposeeed v75-sdk22 everything works as it should,not a single reboot and phone is rebooting faster also and no lag as i used to have before,fingers crossed it won t show up again:good:
Good evening, just lately I have encountered a bug when trying to install APK's. When I go to install via Package Installer it will open up the screen and when I go to press next it doesn't do anything, I have tried rotating the screen and pressing Next and it just doesn't work whatsoever...
I powered off my device and powered back on and this seemed like it fixed the problem.
Is/has anyone else encountered this? I've also noticed ometimes when typing on the keyboard the sound goes tinny for 5 seconds or so and go back to normal, it's been like this since unboxing too.
I haven't had this issue exactly, but when I install a new app and it asks for permission to access my location/storage/etc.. I can't press Allow.. I can press Deny though no problem at all. Right now I'm manually going into apps/permissions and granting all my apps whatever I think it needs.. Just a pain to do it that way though!
I had this issue the other night. It seems an invisible overlay gets stuck sometimes. Not sure what app or why, but clearing all the recent apps fixed it for me. Try that if it happens again instead of waiting for the phone to restart.
Sent from my G3223
Also had this problem two days ago and restarting seemed to fix it. I was disabling some of the stock apps at the time so I wondered if that had something to do with it but I don't know, don't think I re-enabled any of the apps or anything before or after the reboot and so far it's been working since.
mikeandjaimie said:
I haven't had this issue exactly, but when I install a new app and it asks for permission to access my location/storage/etc.. I can't press Allow.. I can press Deny though no problem at all. Right now I'm manually going into apps/permissions and granting all my apps whatever I think it needs.. Just a pain to do it that way though!
Click to expand...
Click to collapse
Thanks for your feedback and I have also had that problem too. Of course yes we can go into app settings and enable and like you stated it's a pain haha. I know this isn't the place to point these problems out and get them fixed but it's nice to know I'm not the only one ??
redincali said:
I had this issue the other night. It seems an invisible overlay gets stuck sometimes. Not sure what app or why, but clearing all the recent apps fixed it for me. Try that if it happens again instead of waiting for the phone to restart.
Click to expand...
Click to collapse
Yes dude, that's correct and thanks for that valuable information I do clean my cache regularly and can't say I've come across the problem for a while, so thanks again.
exonym said:
Also had this problem two days ago and restarting seemed to fix it. I was disabling some of the stock apps at the time so I wondered if that had something to do with it but I don't know, don't think I re-enabled any of the apps or anything before or after the reboot and so far it's been working since.
Click to expand...
Click to collapse
I'd like to mention I have disabled and uninstalled quite a lot too, but I can't say if this adds to the problem. It'd just be really nice to hopefully get the new build of software that was recently announced on Xperia Blog but I can't say if this will fix the problems etc. I don't know? ??
Sent from my Sony Xperia XA1 Ultra using XDA Labs
LevsOG said:
Good evening, just lately I have encountered a bug when trying to install APK's. When I go to install via Package Installer it will open up the screen and when I go to press next it doesn't do anything, I have tried rotating the screen and pressing Next and it just doesn't work whatsoever...
I powered off my device and powered back on and this seemed like it fixed the problem.
Is/has anyone else encountered this? I've also noticed ometimes when typing on the keyboard the sound goes tinny for 5 seconds or so and go back to normal, it's been like this since unboxing too.
Click to expand...
Click to collapse
I've experienced this issue as well and the culprit seemed to be an overlay permission from another app. As I'm sure everyone knows, this phone's screen is very bright even at it's lowest setting. I like to read at night and the light bothers my wife so I started using an app called Nightowl that further dims the screen. Nightowl produces a overlay that dims the entire screen. If i happen to be running nightowl and try to install the app, I can't tap install. Once I turn off the app I'm able to install like normal. Hope that helps lead you in the right direction as restarting the phone every time a problem presents itself is kind of a bummer.
Sorry if this is posted somewhere, I did search quite a bit. Anyway, my wife's z2 force WiFi Keeps turning off by itself. I set it to always stay on even, still does it. Rebooted, still there. This is a big problem because we ran through all of our data (Verizon) because we didn't know for a while. Anyone else experiencing this? Any fix? Please and thanks!
gettinwicked said:
Sorry if this is posted somewhere, I did search quite a bit. Anyway, my wife's z2 force WiFi Keeps turning off by itself. I set it to always stay on even, still does it. Rebooted, still there. This is a big problem because we ran through all of our data (Verizon) because we didn't know for a while. Anyone else experiencing this? Any fix? Please and thanks!
Click to expand...
Click to collapse
Disconnecting or turning off?
enetec said:
Disconnecting or turning off?
Click to expand...
Click to collapse
Turning off. If she turns it on while using it, it seems to stay on, but then it'll turn off and stay off until she hits the WiFi button.
gettinwicked said:
Turning off. If she turns it on while using it, it seems to stay on, but then it'll turn off and stay off until she hits the WiFi button.
Click to expand...
Click to collapse
Have you rooted your phone? Have you installed some power saving apps?
enetec said:
Have you rooted your phone? Have you installed some power saving apps?
Click to expand...
Click to collapse
None of the above. It's stock, with a few apps she likes such as Facebook and Pinterest. Nothing that would do that.
Pure speculation, as I don't own the Verizon model, take it for what it's worth...
It sounds like Verizon software is handling this. Having previously owned both ATT and Verizon devices, I know how they love slapping their seemingly helpful "data manager" apps into the stock system apps. Usually these apps can--and often will--by default handle wireless hand-off settings.
This is where I would look first. If your not rooted, I'm not sure what your options are to block this type of app, especially if it was installed as "system", but you might get lucky, and be able to freeze it or at least deny it permissions.
Again, all speculation. I'd be really interested to know if I'm close though.
Edit: You also might look into your build.prop settings. I haven't manually poked into these since honeycomb, so I won't be much help here, but I'm sure someone here can point you at the right variables inside build.prop to see if there's an "oopsie". Again, just a thought.
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
zebinadams said:
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
Click to expand...
Click to collapse
What android version are you running? Do you have many apps installed? Have you tried restoring back to factory defaults?
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
zebinadams said:
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
Click to expand...
Click to collapse
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Ok, I'll try that when I get a chance. we'll see if it works.
marcost22 said:
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Click to expand...
Click to collapse
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
zebinadams said:
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
Click to expand...
Click to collapse
This is gonna sound weird, but have you changed your screen at all?
marcost22 said:
This is gonna sound weird, but have you changed your screen at all?
Click to expand...
Click to collapse
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
zebinadams said:
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
Click to expand...
Click to collapse
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
marcost22 said:
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
Click to expand...
Click to collapse
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
zebinadams said:
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
Click to expand...
Click to collapse
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
marcost22 said:
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
Click to expand...
Click to collapse
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
zebinadams said:
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
Click to expand...
Click to collapse
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
marcost22 said:
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
Click to expand...
Click to collapse
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
zebinadams said:
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
View attachment 5544389
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
Click to expand...
Click to collapse
Yeah, to me it still looks significantly brighter around the clock
marcost22 said:
Yeah, to me it still looks significantly brighter around the clock
Click to expand...
Click to collapse
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
zebinadams said:
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
Click to expand...
Click to collapse
[REFERENCE] How to compile an Android kernel
Introduction Hello everyone, I will be going over how to compile a kernel from beginning to end! Prerequisites: A Linux environment (preferably 64-bit) Knowledge of how to navigate the command line Common sense A learning spirit, there will be...
forum.xda-developers.com
Is a great guide, you'd need to follow the clang guide tho, as our kernel IS clang-compiled, and i recommend repacking the boot.img
You'd need to change this line
kernel_motorola_msm8953/msm8953-albus.dtsi at 7befedacd91b84ed737b691671c088c89e394f66 ยท AICP/kernel_motorola_msm8953
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
In your source to be
qpnp,qpnp-labibb-mode = "lcd";
If i'm right, after doing that and flashing it the issue will be fixed. Otherwise when you try to turn on the display it will cause a kernel panic
You would need to reflash this boot.img after every update, and redownload sources everytime i do something to kernel.