kcv_earner said:

I have XT2052-1 with build number QPGS30.82-105-4.

I tried this twrp from Dec.31, 2020:

https://twrp.me/motorola/motorolamotoe2020.html

I took these steps:

#adb reboot bootloader
#fastboot flash boot twrp-3.5.0_10-0-ginna.img
#fastboot boot twrp-3.5.0_10-0-ginna.img

but twrp seemed to have no screen response after loading.

Click to expand...

This means your touch screen panel is not supported. Even if you have the same phone, some Moto E 2020s have a Focaltech panel, and the current maintainers for this device have not posted a fixed TWRP image on twrp.me which supports that panel. Do you have Telegram? If so, join the https://t.me/motoe7 group and have a chat with the current maintainers of the device. They have a OrangeFox recovery image which supports the Focaltech panel.

Boot into FTM mode, then using ADB commands type adb reboot edl. From EDL mode you can flash and dump partitions, but you will need a firehose for that, maybe you can borrow it from another ZTE device. Would be really cool building TWRP and a custom ROM for it, but without a touchscreen it's quite hard. Cymbal T would be easier.

If gallery doesn't find them, using a file manager, navigate to your /sdcard folder and locate the Pictures folder. The location path would be /sdcard/Pictures. If you use adb you can pull them to your computer with the command

I just received and opened the box of my new Ultra. I put it on my wireless charger and was pleased to see it start charging. If it will do as well with the case I purchased I'll be a happy man. I'll let it fully charge before messing with it. I might even wait for tomorrow to set it up. I'll have all day to play with it without any given time frame and have a full charge on both phones.

Milo Williamson said:

Try looking through google photos buddy, it would of been some kind of bug on an app. Sorry to hear about that, we will work and help you out every step of the way.

Click to expand...

It would stink if it was a bug in the app because I am using the Samsung ones that came with the phone & tablet.

I have a way that I've tested to unlock the bootloader on this device. Also, I have a custom recovery I compiled that works for this phone. I still have to get the recovery to survive a reboot, but I will write a tutorial as soon as I get it to survive reboot.

Try this thread: https://android.stackexchange.com/q...ct-my-contacts-from-a-backup-image-of-android

The information posted years ago might still be relevant for someone. Your post might be helpful as well. I didn't remove it. I did want to advise and inform you that the tread is quite dated being as you are new to the site.

@Eldritch1969 Thanks! that did it!!!! (had to disable wifi calling)

edit: actually just popped up again. dang!

what phone do you have? that first screenshot, where is that list from? im guessing that the app is not listed in the apps list in the phone settings? did you look for system apps as well?

I have XT2052-1 with build number QPGS30.82-105-4.

I tried this twrp from Dec.31, 2020:

https://twrp.me/motorola/motorolamotoe2020.html

I took these steps:

#adb reboot bootloader
#fastboot flash boot twrp-3.5.0_10-0-ginna.img
#fastboot boot twrp-3.5.0_10-0-ginna.img

but twrp seemed to have no screen response after loading.

any thoughts about a recovery image?

Mine gets worse in the winter when my hands get dry due to the weather. I use my face unlock most of the time now.

Thanks again. The only app could be Whatsapp which I use all the time. Two days ago I rebuilt the entire phone from scratch. App by app.
As of now, the phone is much faster, I got rid of some annoying adds and the mic is working fine. May be I solved the problem.

you can also try this app
https://play.google.com/store/apps/details?id=com.meh.DarkWallpapersHD

Greetings all,

I am working on an AccessibilityService that takes input from game controllers (PS5 controller, Xbox Controller, etc.), I am using OnKeyEvent() for handling button presses and releases ,however I am having a lot of trouble figuring out how to receive input from the Joysticks.

Generally I would use OnGenericMotionEvent() to handle MotionEvents from the joysticks, but since this is an AccessibilityService and not an Activity, it doesn't seem to have that method.

The MotionEvents I want to handle are as follows: AXIS_X, AXIS_Y, AXIS_Y, AXIS_RZ, AXIS_RY, AXIS_RX, AXIS_HAT_X, AXIS_HAT_Y, AXIS_LTRIGGER, AXIS_RTRIGGER, AXIS_BRAKE, AXIS_GAS

Does anyone here know how I could handle MotionEvents from an AccessibilityService? I've looked at the official docs and codelabs a lot but this has me stumped.

Regards,
0xB01b

Same is happening with my tab. It doesn't support OTG anymore, neither it detect any cable. I made a factory reset but still the problem persists.

Thank you puppykickr.

I managed to fix it but in a different way. I'm not sure how I got there but I went into Google Play settings and found 'My Devices' which showed that the device I was looking to fix was unticked. It seemed to me that it was worth ticking that box and then I found that it worked!

So I haven't tried your fix, which may well have fixed it anyway so thanks for the suggestion.

I do not believe of it, unless you mean through google play, then yeah leave them a review