yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] zusatzmetall:
1. Hi, if you have the white USB port is defective, you have bad cards with the USB burning tool. If the white connector is in place try the USB burning tool method. Or try the Burn card method. Post #4

2. Try an OTA update, there is a new update from 12.05.2018 Update

I can only speak for myself and my experience, I recommend the Nonchers firmware, I have modified this extra for the X96 mini BOX.

But if you would like to have an ATV version you can also try the modified version of N'ayam Amarsh'e.

ATV Xperience
[Android Stick & Console AMLogic based Computers] manusiabodoh:
Hey Mate, thanks for responding.

I am newbie in this android box and the tweaking stuff.

1. Hi, if you have the white USB port is defective, you have bad cards with the USB burning tool. If the white connector is in place try the USB burning tool method. Or try the Burn card method. -> Yes the USB port which is not working has white color. So I used the other port (black color) to plug in wireless remote for mouse+keyboard. So are you suggesting, due to the white port does not work, therefore I have to use burn card method if I want to update the firmware? Do I just copy the img file to SD card root directory or I have to use burn card maker?

Try an OTA update, there is a new update from 12.05.2018 Update -> Is this the right firmware for my X96 mini? If it so, I can use this firmware and use burn card method to update the firmware? What is OTA update? is this another method to upgrade the firmware? If it is so, can I use the OTAUpgrade app you posted on first page? https://yadi.sk/d/au4NFTBa3UCoQC

Sorry for asking and bothering you with these quoestions.

Looking forward for your reply.

Thank you.
[Android Stick & Console AMLogic based Computers] nickzeptepi:
Move the box to find the best WiFi signal. There's no aeriel and it could be in a weak WiFi wave pattern
[Android Stick & Console AMLogic based Computers] manusiabodoh:
I placed my box only a few meters from wifi router without anything blocking the signal. so i believe this is not the cause of the problem
[Android Stick & Console AMLogic based Computers] nickzeptepi:
Perhaps I didn't explain sufficiently, move it around from its current location, even if it's 20-50cm left or right. Then retest the speed.

The aeriel is crap, it's current location might be in a down wave pattern where it needs to be in the up wave.

Just try different locations retest & use the best spot
[Android Stick & Console AMLogic based Computers] mrsoje:
X96 mini has crap WiFi , so I use wired connection.

With Tanix firmware WiFi is much better but I stick with wire ...
[Android Stick & Console AMLogic based Computers] manusiabodoh:
Did try your recommendation and it didnt work

I think its either the firmware or the hardware... I paid peanut I got peanut :o
[Android Stick & Console AMLogic based Computers] manusiabodoh:
Mate, can you please help me. I did try and follow your instruction on how to upgrade my x96 mini.

I did this:

1. Download Norcher firmware and burn it into SD card.

2. Insert SD card into X96 mini and use toothpick to hold the button inside AV hole then i plug the electricity. On the screen it says updating and immediately i pulled off the toothpick. This when disaster started to happen, tv screen went blank and my box did nothing.

Now when i plug it to electricity there is only red light going and nothing happen. normally the light become blue and it start to boot up the tv box.

Can you or anyone here, please tell and show me how to recover my x96 mini.

Thank you very much.
[Android Stick & Console AMLogic based Computers] zusatzmetall:
Hello manusiabodoh,

I only have one box and it works great, otherwise I would try some things on my box to help you.

My box is set up so well that I do not want to adjust anything further.

There are certainly some things you can try.

1. Download from the page https://pan.baidu.com/s/1nuZwjLB PW: fiqn the folder down pack the three files on sd card. remove the power cable, insert the toothpick into the av and hold it, then plug the power cable in again, release the toothpick after about 10 seconds) It should start the recovery. From there you can install the first official update.

1.1 Start the recovery (remove the power cable, insert the toothpick into the av and hold it, then plug the power cable in again, release the toothpick after about 10 seconds) It should start the recovery. From there, put the box back.

2. You can after the reset of the box again try to flash the box via USB (maybe there is only a BUG)

3. You can, for example, put the TWRP.zip and a custom rom (example ATV Experience) on sd,

start the recovery (remove the power cable, insert the toothpick into the av and hold it, then plug the power cable in again, after approx. 10sec of releasing the toothpick) It should start the recovery.

install the TWRP.zip and then flash the rom.

4. You can, for example, put the TWRP.zip and a custom rom (example: ATV Experience) on sd,

start the recovery (remove the power cable, insert the toothpick into the av and hold it, then plug the power cable in again, after approx. 10sec of releasing the toothpick) It should start the recovery.

5. You can do a backup (for example, from https://4pda.ru/forum/index.php?showtopic=848620&st=9900) or the nonchers MOD 2 (https://drive.google.com/drive/folders/1SUn5D07SMa6mnbTIOnUaKmm6KPCVZ9hy ) or any backup

put on the card and then you can grab the TWRP.zip and the backup on sd

start the recovery (remove the power cable, insert the toothpick into the av and hold it,then plug the power cable in again, after approx. 10sec of releasing the toothpick) It should start the recovery.

install the TWRP.zip from TWRP to restore the backup.

6. You can open your box and look at the USB port to see if the contacts are soldered correctly, if necessary after soldering.

7. Send in the box for repair.

8. The box to send someone looking for you and install a firmware.

If I had a second BOX to test I could perhaps offer you more help. But I hope that this information will help you further.

Thanks to google translator
[Android Stick & Console AMLogic based Computers] manusiabodoh:
Thanks for replying.

Suggestion No 1 to hold the reset button for 10sec, i just did and it didnt work ?

I think the only way to fix my box is to flash the current firmware and inject with the fresh rom into the box using usb cable and PC.

Any idea and suggestion on how to this ?

Thank you.

---------- Post added at 09:14 AM ---------- Previous post was at 09:13 AM ----------

Thanks for replying.

Suggestion No 1 to hold the reset button for 10sec, i just did and it didnt work

I think the only way to fix my box is to flash the current firmware and inject with the fresh rom into the box using usb cable and PC.

Any idea and suggestion on how to do this ?

Thank you.
[Android Stick & Console AMLogic based Computers] zusatzmetall:
1. Download from the page https://pan.baidu.com/s/1nuZwjLB PW: fiqn the folder down pack the three files on sd card. remove the power cable, insert the toothpick into the av and hold it, then plug the power cable in again, release the toothpick after about 10 seconds) It should start the recovery. From there you can install the first official update.

For USB Burning tools you need the correct driver.... Have you installed the world cup driver on PC?
[Android Stick & Console AMLogic based Computers] manusiabodoh:
I dont know how to download those 3 files. The website is in chinese. And when i try to click download button (i assume its download button) it always download file baidunetdisk.exe (update, i just downloaded img & aml file, e but the zip file cant be downloaded)

About those 3 files, do i just copy and paste them into formatted sd card? or do i need to burn the recovery.img file?

For USB Burning tools you need the correct driver.... Have you installed the world cup driver on PC? -> not yet, cause i am still trying to do your recommendation to use that file from baidu and i dont have usb cable yet to connect pc to box

Thanks
[Android Stick & Console AMLogic based Computers] jellywobbles:
Can anyone post a current working link for a version of TWRP that is known to work with the X96 Mini 2Gb/16Gb?

Thanks

---------- Post added at 03:28 PM ---------- Previous post was at 03:28 PM ----------

Can anyone post a current working link for a version of TWRP that is known to work with the X96 Mini 2Gb/16Gb?

Thanks
[Android Stick & Console AMLogic based Computers] zusatzmetall:
See @ Post #2 there is is a working TWRP Link
[Android Stick & Console AMLogic based Computers] jellywobbles:
Thanks for that - was really looking for a version that can run off an SD card, as I don't want to flash TWRP to the X96.
[Android Stick & Console AMLogic based Computers] survar:
Are you using X96 mini Firmware on X96 mini hardware of some other device? Also does Tata Sky play video for you? I have got this started on my X96 Mini but for some reason, I only see the black screen and the video does not play. Appreciate if you can shed some light.
[Android Stick & Console AMLogic based Computers] DanielRiveros:
I installed the new version for May 2018 but the same thing keeps happening to me!

I can not make my x96 mini work! It stays frozen after 1min 30 seconds of starting. The main screen of apps remains and nothing, it does not work. I turn off, turn on, and go back the same. See the attachment, it remains on that screen without responding.
[Android Stick & Console AMLogic based Computers] PTHugo:
Go to recovery and delete all user data and cache then reboot it will take a while to boot back but hopefully will be like new
[Google Pixel 2 XL Questions & Answers] grigi93:
hey guys, maybe someone can help with my pixel 2 XL 64 GB in Germany

Since I upgraded to 8.1 my ambient screen doesn't work properly, black screen on calls and so on. I'm pretty sure it's some change with the proximity sensor. i used some apps to test the sensor and when I clean my screen really hard everything works fine (shows "far" in the test app) but when i just wave without touching the screen, it goes to "near" and doesn't recover until i wipe the screen again ( wtf?). I can't really use the phone like this. I am in contact with Google support but they give the generic suggestions like restart the phone etc.

Everything worked fine under 8.0. i actually went ahead and flashed 8.0 back on and it works properly. it seems like they increased the sensors aggressiveness in 8.1.

For most people the problem gets resolved by taking off the screen protector but I don't have one applied. neither are there any scratches on the display. Maybe my sensor is flawed in some way :/

I also tried the turning on /off adaptive brightness trick, to which there is a thread somewhere.

maybe you guys can share your experiences or fixes,

Thanks and Liebe Grüße from Germany !
[Google Pixel 2 XL Questions & Answers] CyberpodS2:
I myself had some odd behaviors after updating by using the factory image with the -w removed from the flash-all.bat and ended up starting from scratch due to my cat. (Long story) but anyway, I think you will find a few other folks had bad results of some sort or other after updating. Personally, I would back up everything with TiBu and a good nandroid. ( kill any pin or fingerprint stuff first). Get anything off the internal storage you don't want to lose also.

Worst case you have a few hours of putting it back together and best case you flash from scratch and restore your data partition in TWRP.

If you factor in the time screwing around trying to "fix" it, you might be better off starting over. :) Unless you did actually install 8.1 from scratch them forget all this. Lol
[Google Pixel 2 XL Questions & Answers] Badger50:
I did enjoy your cat story a while back! Dang varmints! :cool:
[Google Pixel 2 XL Questions & Answers] .paul:
FWIW - I received the OTA update on my phone (unlocked version) and the proximity sensor seems to be screwed up. I having the same issues you've described. I've also got the mooshi ion glass screen protector on my phone.
[Google Pixel 2 XL Questions & Answers] grigi93:
thank you! i already did a fresh factory flash of the 8.1 firmware from the Google devs website. Didn't solve the problem though:rolleyes: It works fine on 8.0 so I don't get it.

It's really strange that only a bunch of people experience this problem. I kinda hoped for a functioning phone , at least for 1000 bucks.

I'm considering to get a replacement if nobody finds a fix to this.
[Google Pixel 2 XL Questions & Answers] Voicebox:
Not sure if it'll help, but I installed "Sensors test" by Ettore Zaffaroni. Mine works just fine on 8.1 stock unrooted. The version is the OTA update to DP2.

In the Proximity test, at the bottom of that is says:

Vendor: AMS TAOS

Version: 2

Max Range: 5 cm

Resolution: 1 cm

Current: 01. ma

Maybe check and see if it is the same vendor and version. And if the other numbers match. I measured it activating between 1 1/2 inches and 2 inches, pretty much only directly in front of the sensor. I have a screen protector but with a hole cut out over the sensor.
[Google Pixel 2 XL Questions & Answers] evo5ive:
Same issue here, no screen protector installed. Tried a factory reset without luck, tried safe mode without luck. Only started since 8.1 update.
[Google Pixel 2 XL Questions & Answers] ogarlen:
Since the 8.1 OTA, I'm having an issue where the Always on Display doesn't always stay on and when the screen goes black, I can't use double-tap to wake it back up. I have to use the power button to turn the screen back on. I wonder if it's related to the proximity issue, because it's almost as if the screen thinks you have the phone up to your ear...?
[Google Pixel 2 XL Questions & Answers] dberthia:
Same issue here. Downloaded Sensors test, and Proximity shows as "NEAR", I've got a screen protector covering the sensor.
[Google Pixel 2 XL Questions & Answers] HikerVancouver:
I have the same issue. Pixel 2 xl, after upgrading to 8.1, proximity sensor says near when screen protector is on. I think that most likely something is messed up with the update.
[Google Pixel 2 XL Questions & Answers] ogarlen:
Wanted to add that I have a screen protector, however had the same one on 8.0 and had no issues. Also that neither DT2W or raise to wake works when the screen goes black, only pressing the power button. The issue seems intermittent. Always On Display seems to be working about half the time, whether I allow the screen to automatically shut off after a minute or if I press the power button to shut the screen off.
[Google Pixel 2 XL Questions & Answers] grigi93:
yes i did the test with the app sensor test and it shows "near". I downgraded to 8.0 and it works fine.

For all of you guys with screen protectors:

try removing it, it solved the problem for some people but not for me (i didn't have one on the first place)

or try downgrading if you know how to.

I went to my carrier today and they told me they got an email from Google about the 8.1 update is kinda messed up, so i should wait for the next patch. Idk what's going on, but i hope Google is aware of this.

thanks for the replies though!
[Google Pixel 2 XL Questions & Answers] Loujamon:
I'm also having similar problems with my phone with the sensor. Also with the gesture features not working such as, double tap and flip for camera.

Ambient display not functioning is properly the most annoying, along with black screens after phone calls.
[Google Pixel 2 XL Questions & Answers] HikerVancouver:
I did notify google of this issue. It would be good if all of you spend few minutes to do the same. That will let them know it is not an isolated incident.
[Google Pixel 2 XL Questions & Answers] dberthia:
Removing my screen protector immediately solved the problem for me. Just ordered another one that won't cover the proximity sensor.
[Google Pixel 2 XL Questions & Answers] dpw2atox:
I don't have a screen protector and I have the same issue with my proximity sensor. Anyone figure out a fix?
[Google Pixel 2 XL Questions & Answers] grigi93:
No fix that I'm aware of,

but there are many more people with similar issues.
[Google Pixel 2 XL Questions & Answers] Dc52ltr:
Same here, had a full glass screen protector on my 2xl (on Oreo 8.0)and I cracked it when carrying a pair on ladders, phone was in my pocket at the time. So I ordered the same screen protector again... Once again it worked fine but as soon as the update to 8.1 was installed I was getting a black screen whilst receiving a call and had to wait for the caller to hang up before my phone returned to normal. As soon as I removed the screen protector the phone was fine. I've checked this 3 times and the same thing happens. Google have done something to the proximity sensor in the last update, no question.
[Google Pixel 2 XL Questions & Answers] Enc0der:
Same issue here, no screen protector installed. Screen goes black every time I try to use the phone while on a call.
[Google Pixel 2 XL Questions & Answers] ElementalWindX:
Funny how my phone worked perfectly with my screen protector before this 8.1 update for the two months the phone as been out. Now I can't hang up phone calls or turn the screen on during phone calls. -_- Hope they fix it soon.
[Google Pixel 2 XL Questions & Answers] EMcTx:
My screen is also black when my phone rings. I did find that if I unlock via fingerprint, the screen comes on. I think it might be the phone app, because the screen comes on when someone calls me through Hangouts.
[Google Pixel 2 XL Questions & Answers] jblack41510:
Mine works just fine. 8.1 rooted with magisk. I have the amfilm glass with the hole cut. I didn't take an OTA update, I flashed the image when it was released.

I downloaded the "sensors test" app just to compare and all my stats and information is the same.
[Google Pixel 2 XL Questions & Answers] mlevin:
I'm experiencing exactly the same thing. I have a clear case (Spigen Liquid Crystal) and everything was fine under 8.0. Now with 8.1 it is intermittently going black. I took off the case and so far the screen has remained on.

Definitely seems like they changed the sensitivity of the proximity sensor.

I was about ready to flash back to 8.0 when I saw this thread.
[Google Pixel 2 XL Questions & Answers] DatGuy_Shawnaaaay:
Not alone

Yes. I've also encountered this problem. The Google forum seems useless. I've tried almost every possible solution I could think of:

•Taking screen protector off

•wiping the sensor with a microfiber cloth

•downgrading the ambient display app

•clearing cache for stock phone app, ambient display app, any app that seemed to relate to the sensor or calling

•toggling auto brightness

•Safe mode/ phone restart

You guys can feel free to try the same methods. I haven't tried resetting the phone because I don't think it will do anything and there has been many posts that seem to support my thoughts. There are 2 options now. Get a couple of people to rant out our frustration on the Google forum and wait for an update in January or exchange our devices.
[Google Pixel 2 XL Questions & Answers] biggiestuff:
8.1 update definitely did something with the way the proximity sensor is working. Incoming calls will cause the screen to stay lit even if the proximity sensor is covered (IE in pocket). This is causing accidental presses on the screen when I'm taking a call via a BT headset or my watch. While on the call i opened up the sensor test app and it can detect FAR or NEAR. I tried safe mode and I tried uninstalling updates to the phone app with no success.

I wanted to add that proxmity sensor works fine during incoming calls when BT headset is NOT connected. Seems like they added a feature that they didn't think through properly. Surprise surprise?
[Google Pixel 2 XL Questions & Answers] AndrasLOHF:
I'm finding my phone registering touches in my pockets much more than usual lately.
[Google Pixel 2 XL Questions & Answers] EMcTx:
After toggling adaptive brightness on and off, toggling ambient display on and off, clearing the cache of the ambient display and phone, and rebooting, my phone now comes on during an incoming call. I do have an anfilm screen protector and a case on my phone.
[Google Pixel 2 XL Questions & Answers] stgilbert:
I had the same problem. Flashed to 8.1 using the OTA from computer using adb. When it was done I noticed that the phone said completed successfully but on the terminal window it showed that it failed at 94%. When the phone booted everything looked OK but when I got a phone call the screen went black and I could not end the call. Had to wait for the other person to end it. Tried flashing the full factory image that said successful on both phone and computer but the issue was still there. I then flashed back to 8.0 but the issue remained. I wonder if there is a problem with one of the firmware updates they are doing. I did the same process on my wife's phone and after the OTA update it worked just fine. I called google told them what I did and they sent a new phone to me the next day. I updated that one to 8.1 and no issues.

Steve
[Google Pixel 2 XL Questions & Answers] v12xke:
Reporting anything to Google customer support is useless and a waste of time. This bug/issue has been reported on the official Google Issue Tracker. People who are affected should DROP BY the tracker and "star" the issue so the Google devs know how many devices are affected and under what conditions. The more stars an issue gets, the more attention it will get. You can also post your experiences, observations, tests, etc. for the benefit of the group. For example, your results from the proximity sensor testing app . This will help both Google and you as an end user... and get the problem solved more quickly.
[Google Pixel 2 XL Questions & Answers] mlevin:
Agreed. I never bother to go through customer support. I just open a bug on the issue tracker.

This one seems to be getting the most responses: https://issuetracker.google.com/issues/70819065
[Google Pixel 2 XL Questions & Answers] Yohanedirisinghe:
I'm having the same issue after updating to the 8.1 if some one found a solution please post here :(
[Google Pixel 2 XL Questions & Answers] mlevin:
The only solution (until they fix it in an update) is to remove your case. When I did that, the problem disappeared completely. If you don't have a case, the only thing I can think of is to make sure that the area around the proximity sensor is clean and unobstructed.
[Google Pixel 2 XL Questions & Answers] grigi93:
there is a work around to the phone call problem:

you can use the power button to end phone calls

just toggle the option under Accessibility.

doesn't solve the problem but is easier than rebooting the phone everytime.

btw on my phone the problem doesn't disappear when I take of my case, no screen protector installed.
[Google Pixel 2 XL Questions & Answers] dpw2atox:
I spoke with Google support about this and they after just sending me a new phone, we'll see if the new one works properly on 8.1 or not.
[Google Pixel 2 XL Questions & Answers] mlevin:
Can anyone who has a case actually sold by Google (one from https://store.google.com/category/pixel_2_accessories) comment on whether this problem occurs with the case?

I'm curious if Google even tested this with the cases they sell themselves, which presumably have Google's blessing in terms of compatibility and fit.

My Spigen liquid crystal case (https://www.spigen.com/collections/google-pixel-2/products/google-pixel-2-xl-case-liquid-crystal) causes the problem. I just ordered one of Google's fabric cases (https://store.google.com/product/pixel_2_case_fabric) to see if that works better.
[Google Pixel 2 XL Questions & Answers] dpw2atox:
As an update, the new P2XL works fine with the proximity sensor so if anyone has an issue with theirs that isn't resolved by cleaning or removing a case you might need to RMA the phone.