I deleted live wallpaper picker by mistake,now unable to set live wallpaper...tried to install live wallpaper picker apk bt it doesn't install...is there any option rather to flash rom again
You can try to extract it from the roms zip, but dirty flashing the rom is not a problem at all or why you don't want it?
I thought that it might delete all my configuration I did in my RR rom.
Dirty flashing will not wipe your configuration. Backup with twrp and then flash the rom again.
Did it...everything working now ?...Thanks Alot for help
After restart I again need to set my live wallpaper....I am on RR 8.1 any solution????
Is there any solution of ghost touch? Only Automatic brightness but sometimes it starts again ghost touching. I have moto g4
Use kernel auditor app and set rgb to 150,140,150. Search the fourums you will get more answers
There's no real solution only the workaround you already mentioned. Service center is the only possible "solution".
Ask in rr thread jleeblanch will look into it, check oreo or nougat
He means ghost touch, not ghost screen, where lowering rgb values prevents the screen from that ghost(burn in) effects.
Oh, ok now i understood that due to screen burn, his display has been permanently damaged.
I tried stock system update while having twrp which caused my phone to boot to recovery everytime so I used twrp to boot in bootloader and then start the phone which works fine then I changed my rom to a different one but I still have the same problem, everytime I boot it goes into the recovery and then I need to use the bootloader, I have the 64bit twrp btw, thanks.
Yes ghost touch. It starts annoying when brightness is over than half, without automatic brightness. But with automatic it starts also sometimes touching itself daylight under the sun example. Thanks for replies
Facing ghost touch issue and tried so many methods as shown in xda and YouTube but no result.
Running stock OS and problem occurs during charging,high brightness.
Also read some threads that some custom rom fixes that ghost and in some still its there
So I request you to suggest a custom rom which fixes ghost touch issue.:crying:
Thank you
Running stock OS and problem occurs during charging,high brightness.
Also read some threads that some custom rom fixes that ghost and in some still its there
So I request you to suggest a custom rom which fixes ghost touch issue.:crying:
Thank you
Why you explaining it wrong again mate? I explained you here https://forum.xda-developers.com/mo...-question-noob-friendly-t3526598/post76486385 already, that ghost touch can't be fixed when lowering rgb values.
Again: Ghost touch isn't the same as ghost screenkm(which can be workaround with lowering rgb values).
Ghost touch thread for reading ahead https://forum.xda-developers.com/moto-g4-plus/help/ghost-touch-issue-t3692798/page3
Last edited:
Has anyone ever had any luck fixing the speaker issue without sending the device in to be repaired?
Basically the speaker just died one day, it appears to be common but I still don't know if it's a hardware or software issue.
Basically the speaker just died one day, it appears to be common but I still don't know if it's a hardware or software issue.
If it's a hardware issue or inherent physical vulnerability there probably is not much that could be done about with software (although perhaps there could be ways of decreasing the probability the problem occurring by using a case).
I've not seen reports of this in Athene threads here (not that there aren't any) so could you elaborate about why you think it's common, or even better cite the sources that indicate such?
Hey, thank you for replying.
I could be wrong but it seems fairly common due to it returning a decent number of results on Google, mostly to this forum. There's lots of threads reporting similar issues but not a lot of discussion. Nobody seems to have a solution past taking it to a repair centre, but it just feels like such a strange issue.
If I try to play something on Google Play Music, the track just won't start. Youtube gives an error message saying playback failed. Media just doesn't attempt to play at all. Plugging headphones in doesn't work either, they're just not detected.
Up until a couple of days ago, I could still hear sound when booting up the phone but that's stopped now. I saw a couple of people say that they opened up the phone and found that the connector for the speaker was loose and was a fairly simple fix, but I don't really want to open up the phone unless I really have to.