Hi Guys,
I have a Teclast x80 Pro, and I want to update windows on it, but I might need to reinstall android as well.
The one thing I love about this is the boot option - you start the tablet, it counts down from 10 and allows you to choose an OS - Android, or Windows before booting.
If I inadvertently wipe this, how can I restore it? or can I create a new boot screen like this?
Being a tablet it needs to be touch screen responsive, as I dont want to have to plug in a hub and mouse everytime I want to swap to Android.
touch screen
Being a tablet it needs to be touch screen responsive, as I dont want to have to plug in a hub and mouse everytime I want to swap to Android.
Related
Good evening everyone,
I tried several Android Roms (2.3.7, 4.x) in the last days and I always had problems with "phantom presses" on the touchscreen. Every 5 seconds (even if I don't touch the phone) there is one of these phantom presses in the middle of the screen... makes Android unusable.
So I installed the original Windows Mobile 6.5 rom again - the device works without any problems. So I think its not a hardware problem.
I even installed Windows Phone 7 on my HD2 and had the same problems as with Android (phantom presses in the middle of the screen).
Strange thing is: When I choose another driver in Windows Phone 7 (CotullaTouch.dll instead of kmdtouch.dll), I don't have any of these annoying phantom presses.
My question is: Is there a way to select another driver for the touchscreen in android too? Or does anyone have another hint for me how to fix this in Android?
I would appreciate your help, thanks in advance.
sschneiderotr said:
Good evening everyone,
I tried several Android Roms (2.3.7, 4.x) in the last days and I always had problems with "phantom presses" on the touchscreen. Every 5 seconds (even if I don't touch the phone) there is one of these phantom presses in the middle of the screen... makes Android unusable.
So I installed the original Windows Mobile 6.5 rom again - the device works without any problems. So I think its not a hardware problem.
I even installed Windows Phone 7 on my HD2 and had the same problems as with Android (phantom presses in the middle of the screen).
Strange thing is: When I choose another driver in Windows Phone 7 (CotullaTouch.dll instead of kmdtouch.dll), I don't have any of these annoying phantom presses.
My question is: Is there a way to select another driver for the touchscreen in android too? Or does anyone have another hint for me how to fix this in Android?
I would appreciate your help, thanks in advance.
Click to expand...
Click to collapse
How are you confirming something is touching the screen? I would suggest using Dev Tools, Pointer Location, and seeing if it says there is a touch on the screen. Most touchscreen errors are caused by the "End key" pressing down on the digitizer ribbons making the device register a touch. Before i remapped my buttons, when i would push the end key sometimes it would drag down my notification bar.
How are you confirming something is touching the screen? I would suggest using Dev Tools, Pointer Location, and seeing if it says there is a touch on the screen.
Click to expand...
Click to collapse
Hi, yes I know the "End key" issue. But when the phone lies on a table and I don't touch it (and I didn't press any of the keys under the screen before), my phone starts the applikation in the middle of the screen. I also started a paint-app once to check the touchscreen and unfortunately my phone draw something in the middle of the screen for me.
Like I said I don't have this problem with the original Windows Mobile 6.5 and I also don't have it with the "old" touchscreen-driver in Windows Phone 7. So I think it's definitely caused by the touchscreen-driver. Is there a way to make the touchscreen-driver less sensitive?
sschneiderotr said:
Hi, yes I know the "End key" issue. But when the phone lies on a table and I don't touch it (and I didn't press any of the keys under the screen before), my phone starts the applikation in the middle of the screen. I also started a paint-app once to check the touchscreen and unfortunately my phone draw something in the middle of the screen for me.
Like I said I don't have this problem with the original Windows Mobile 6.5 and I also don't have it with the "old" touchscreen-driver in Windows Phone 7. So I think it's definitely caused by the touchscreen-driver. Is there a way to make the touchscreen-driver less sensitive?
Click to expand...
Click to collapse
But youre the only person experiencing this issue. (As far as ive seen) so its gotta be something youre doing. The only way i see it being a driver issue is if your phone is like ancient compared to others and you somehow got an older graphics processor then the majority of devices out there.. Have you tried an android version booted from your memory card? Also try different kernels. Its a little hard to diagnose something like this without seeing the actual sympoms. so bear with me xP
I restored my Advent vega note 7 using super tool 2.3 and i get no feedback from the screen, stylus doesnt work neither does my touch gestures, any reason why? Happens when i reboot the device from complete shutdown and occasionally i get lucky where everything works. PLEASE HELP.
Did notice when it powers up it boots twice flashing the Advent vega banner with nvidia animation. and after it boots (touch inop) I can put it to sleep twice and if I press the power button the third time it reboots.
Had a similar issue myself. Doing a soft reset via the backup and reset option in settings cured the issue, also make sure you are booting the tablet with the stylus in, only take it out once the tablet has booted. I've had strange behaviour if I boot with the stylus out.
Hi,
I broke my LCD display a couple of months ago still, I managed to use the phone with the epaper display and eventually reinstall it without clearly writing down the exact procedure (with Lolipop)
Today, as my Marshmallow update freezed, I had to wipe all, thinking well I could easily find the steps to start the phone again.
The only problem remains that Setup Wizard wants us to use the LCD display, and I can't.
The last time I managed to use screen mirroring on Windows, with androidscreencast-0_3_1.jnlp, which is dicontinued.
To that extend, I allowed USB debugging (three lines to add) on system/build.prop and default.prop and copied a file from my computer (adbkeys.pub) to a certain folder in the device, to allow my PC to operate on the cellphone
But that last step doesn't work anymore.
I can see a dialog briefly popping up on the yotaphone, prompting me to allow the computer for debugging, but I can't click.
Droid Explorer tells me that this yotaphone is not allowed in $Vendor (or so on, I can't remember well).
So I managed to authorize the screen mirroring before, to start the phone, but I can't right now, although I found a new app, androidscreencast-0.0.10s-executable.jar.
I would have to copy adbkeys.pub to data/misc/adb/adb_keys, but as of today, that directory doesn't exist.
Can somebody please help me with that?
Thanks,
Hi,
I solved a similar situation by plugging a mouse to the phone using a usb to micro USB adapter (also called USB OTG adapter).
wicoz said:
Hi,
I solved a similar situation by plugging a mouse to the phone using a usb to micro USB adapter (also called USB OTG adapter).
Click to expand...
Click to collapse
Thank you for answering. And what do it do to plug a mouse?
I've made it : the phone starts again.
If anyone is interested, I'll tell the trick for a broken front screen like mine.
Now I'm looking forward to make an image backup of it as it is very fresh if it can save me or others !
And I need advices for that?
Hi!!!
I have the sale problem
How did you bypass the wizzard???
hi. how do you bypass setup wizard? i had mine reset due to stuck. before im using only back screen. please help!
My front screen also stopped working all of a sudden without me doing anything. I was able to use the eInk so I did a factory reset. Now however I'm stuck since I can't boot the phone without a working front screen. I was wondering if a software issue stops the front screen from working and if there is a way to check/fix it.
Hi everyone. I have an essential PH-1, dropped it and cracked the screen in a couple of places. It still worked normally, but I ordered a screen replacement from amazon. I was able to remove the screen easily enough because I wasn't trying to save it. I connected the new screen before permanently afixing it just to make sure it worked. So, the screen looks perfect and everything looks like new, but the screen doesn't register any touch response at all.
I am able to use the phone with a USB C keyboard and mouse, I'm writing this post on my phone with the keyboard and mouse. Its got the latest software and updates, and aside from the touch screen not feeling any touches, everything is normal. Does anyone know what might be the problem? I've unlocked the bootloader in preperation for installing TWRP, but the process didn't work for some reason. I'm still reading up on that. Could this be a software issue? I hope it's not a problem with the new screen. Ideas and thoughts are much appreciated.
I've tried everything I think, though very cumbersome I was able to unlock the bootloader, install TWRP and root, and installed the stock image - but still no joy. I then installed Lineage OS but there was still no touch response. I did a wipe first through ADB, before 8 installed the stock image, didn't make a difference. At this point I think it must be a defective screen unless anyone has any ideas I may not thought of? All of this done with a USB keyboard and mouse - switching back and forth disconnecting and reconnecting the phone to the PC to use ADB.
Hello all together,
I have here the Samsung SM-J530F/DS of my father.
After the smartphone was dropped, the display no longer shows anything.
Is there any way to backup the data?
There is no screen lock set up, it would just ask for a pin when restarting (I have the pin).
There are no cloud backups and there is no SD card inserted.
If you can get it to connect to the PC.
If it boots and the touch screen still works, it's in the right usb mode and you can hit the connect popup. That's a lot of if's... if the mobo is undamaged you can try replacing the display.
Had he used a SD card as a data drive for critical data and a good case things be a lot easier.
Yeah, a non-dev user probably didn't have ADB enabled. That makes life more difficult.
If you do get ADB working you can use a screen grabber/poker desktop application.
My AdbGrab.exe (in the sig) will let you grab the screen and mouse click things.
It's slow, but the advantage is that it works on stock, unrooted devices without installing anything.