yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] k23m:
OK and fast :)

Look...

<4>[ 3.586944] [ektf3k]:[elan] Get unknow packet {0xFF, 0x55, 0x55, 0x55}
<4>[ 3.796325] [ektf3k]:[elan] Get unknow packet {0xFF, 0x55, 0x55, 0x55}
<4>[ 4.005676] [ektf3k]:[elan] Get unknow packet {0xFF, 0x55, 0x55, 0x55}
<4>[ 4.215057] [ektf3k]:[elan] Get unknow packet {0xFF, 0x55, 0x55, 0x55}
<4>[ 4.424468] [ektf3k]:[elan] Get unknow packet {0xFF, 0x55, 0x55, 0x55}
<4>[ 4.633819] [ektf3k]:[elan] Get unknow packet {0xFF, 0x55, 0x55, 0x55}
<4>[ 4.843200] [ektf3k]:[elan] Get unknow packet {0xFF, 0x55, 0x55, 0x55}

ELAN is the touch controller chip on the replacement PCB and it is spamming constantly with these messages. It seems that you did not connect properly TPCON1 or TPCON2.
[Nexus 7 (2013) Q&A] Dewos:
I wish!!! Sadly I'm not the only one with this problem:

- http://xdaforums.com/nexus-7-2013/n...alibration-t2939991/post58440542#post58440542

- http://forums.androidcentral.com/go...te-screen-after-replacing-charging-board.html

- https://www.youtube.com/watch?v=jkaDHSS-Jtc

and so on. But there must be a way :(
[Nexus 7 (2013) Q&A] Dewos:
[MENTION=7182780]k23m[/MENTION] do you have /proc/ektf_dbg (mine is empty) and /devices/virtual/input/input0?
[Nexus 7 (2013) Q&A] k23m:
Yes ;)

Check it yourself: adb shell cat /proc/ektf_dbg

GG is totally silent about "Get unknow packet {0xFF, 0x55, 0x55, 0x55}" (verbatim phrase search) - you are the very first, congratulations :laugh:

When I have the time, I will pull apart my N7, disconnect TPCON1 and get the log.
[Nexus 7 (2013) Q&A] Dewos:
Yap, empty file :rolleyes:

Is a conspiracy......... GG protects the nexus brand :p

https://github.com/bigbiff/kernel_asus_tf700t/blob/master/drivers/input/touchscreen/ektf3k.c#L1023

Thanks!!! Anyway, after some more test, it seems to me that the touchscreen driver fails to boot (at booting time), hence the boostrap files are missing.

Something similar happened here on ASUS Transformer and they solved it with a custom firmware:

http://xdaforums.com/showthread.php?t=2091233

For example http://xdaforums.com/showpost.php?p=64395607&postcount=984
[Nexus 7 (2013) Q&A] k23m:
adb shell cat /proc/ektf_dbg outputs "Debug Level: Release Date: 2011/10/05"

github - "0xFF, 0x55, 0x55, 0x55" is not there

FW boots fine, note your log: <4>[ 2.549804] [ektf3k]:The firmware was version 0xA044 and id:0x3029
[Nexus 7 (2013) Q&A] Dewos:
[MENTION=7182780]k23m[/MENTION] any news on your side? :angel: You're my only hope :D
[Nexus 7 (2013) Q&A] k23m:
Not yet but why did you give up on the old PCB? The USB socket is trivially easy to repair.
[Nexus 7 (2013) Q&A] Dewos:
Mmmm.... well, here is the true story: some months ago the tablet dropped and the digitalizer broken up. So I ordered a new lcd+digitalizer on ebay and replaced the old one.

After the replace the screen was perfect but during the fix I heavily damaged the TPCON 1/2 port (was my first attempt :angel:) and the touchscreen has gone completly wild some time after that (ghost touch etc) forcing me to use it without the touchscreen but with an OTG Usb Mouse.

After months of OTG plug IN and plug OUT, the usb port said "goodbye cruel world" and so here we are: I ordered up a new sub board: OTG is ok but no touchscreen at all. So I'm clearly stuck here, hoping in a solution. :crying:
[Nexus 7 (2013) Q&A] k23m:
I see, the board is useless indeed but it still may help us in one last application. Please connect it to the main silver cable ONLY and if USB can still work a bit and grab a dmesg log. Don't disconnect the new board from TPCONs as we don't want to risk another damage. The objective is to see the log when there is a problem with TPCON. I'd do it on my N7 but not yet.
[Nexus 7 (2013) Q&A] Dewos:
Made it. No "Get unknow packet" gibberish in the old one, even with the ribbon cable disconnected.

P.s.

This is the same error on Asus Transformer: http://xdaforums.com/showthread.php?t=2091233&page=72

And probably related, the firmware for FLO: https://github.com/TheMuppets/proprietary_vendor_asus/tree/cm-12.1/flo/proprietary/vendor/firmware

Also http://xdaforums.com/showpost.php?p=40075700&postcount=191

But #touch_fw_update is an ASUS proprietary shell command, I don't think it works on the Nexus 7.

Ok here there are all the FW releases http://xdaforums.com/showthread.php?t=2800308.

As here: http://xdaforums.com/showpost.php?p=53635199&postcount=828

Maybe I can try to flash all of them, what do you think?
[Nexus 7 (2013) Q&A] k23m:
Excellent, thank you, TPCON had to be checked first, now we can focus on 'calibration'.

Can you confirm that both of your PCBs have the ELAN eKTH325BAWS chip? I am still searching for info on eKTH325BAWS and its programming registers but the closest I find is only this.

Yes, please do try the forced firmware update.
[Nexus 7 (2013) Q&A] Dewos:
Hi [MENTION=7182780]k23m[/MENTION], thanks for your time on this one :) Yes the chips are both eKTH325BAWS, same Revision (1.4) but different serial numbers.

By the way I made some progress:

I flashed all fw from here: http://xdaforums.com/showthread.php?t=2428133 with this results:

boot-ts03-lock.img No errors, some ghostly touches in specific areas only

boot-ts04-lock.img No errors, some ghostly touches in specific areas only

boot-ts05-lock.img No errors, some ghostly touches in specific areas only

boot-ts06-lock.img No errors, some ghostly touches in specific areas only

boot-ts07-lock.img No errors, some ghostly touches in specific areas only

boot-ts08-lock.img No errors, some ghostly touches in specific areas only

boot-ts09-lock.img No errors, some ghostly touches in specific areas only

boot-ts10-lock.img No errors, LESS ghostly touches touch in DIFFERENT areas only

boot-ts11-lock.img No errors, LESS ghostly touches in DIFFERENT areas only

boot-ts12-lock.img No errors, LESS ghostly touches in DIFFERENT areas only

boot-ts14-lock.img No errors, LESS ghostly touches in DIFFERENT areas only

boot-ts16-lock.img No errors, LESS ghostly touches in DIFFERENT areas only

boot-ts18-lock.img Get unknow packet error, no touch at all

boot-ts20-lock.img Get unknow packet error, no touch at all

boot-ts25-lock.img Get unknow packet error, no touch at all

boot-ts30-lock.img Get unknow packet error, no touch at all

Clearly something has changed between the FW builds in time, and after the Ts16 the new sub-board became unsupported (or probably it is from an older production bach).

Anyway, for older FW something works, so there is still hope probably, maybe we must find a way to trigger a re-calibration somehow.
[Nexus 7 (2013) Q&A] k23m:
Thanks to your logs we can now confirm without any doubt the FW-lock method used by OP of the firmware thread. Note my log:

[ektf3k]:[elan] __fw_packet_handler: firmware version: 0xa044
[ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029
[ektf3k]:The firmware was version 0xA044 and id:0x3029

Kernel's FW is 0xa044, ELAN's FW is 0xa044 - so no upgrade is needed.

Your ts16 log:

[ektf3k]:[elan] __fw_packet_handler: firmware version: 0xa063
[ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029
[ektf3k]:The firmware was version 0xA044 and id:0x3029

Kernel's FW is 0xa044, ELAN's FW is 0xa063 - no upgrade needed as far as the kernel is concerned but ELAN's firmware is much older than 0xa044 and only reports a fake, high version number.

:good:
[Nexus 7 (2013) Q&A] Dewos:
Ok so what now? Note that when I say "No errors, some ghostly touches" I mean it: ONLY 2, 3 points in the tablet are sensible. The tablet is completly not usable anyway. Any idea?
[Nexus 7 (2013) Q&A] k23m:
Now we search for eKTH325BAWS programming info. It is here, somewhere on this path...

www.emc.com.tw/twn/database/Sa2/Tp/An/eKT8150%20Application%20Design%20Note%201v1.pdf
www.emc.com.tw/twn/database/Data_Sheet/PE/ePH1200.pdf

...and on ASUS sites. :cyclops:
[Nexus 7 (2013) Q&A] Dewos:
I have a bad feeling about this :p
[Nexus 7 (2013) Q&A] k23m:
No worries, a few ideas to keep you busy... :D

- search for the next best, eg eKT81, eKT8122, eKT8123, eKT8150

- explore 'rough calibrate': echo ff > /proc/ektf_dbg

- use YAMTT for precise evaluation of your tests
​

Btw if you are still on ts16 please post for me the output of: adb shell head /sys/bus/i2c/drivers/elan-ktf3k/3-0010/*
[Nexus 7 (2013) Q&A] Axel85:
Does the elan-touchscreen.idc file entries relates to screen calibration? Is it possible to modify the amplitude of the touch this way?

For example, I can see perfect touch response in multitouch tester or yamtt in a specific point, but if I try to click on a small link in chrome in the same area it s more difficult and sometimes I have to try 2 times (chrome tabs X)
[Nexus 7 (2013) Q&A] k23m:
It appears to be an OS-level preset but if you modify it, you will lose OTA updates because it resides on the /system partition.
[Nexus 7 (2013) Q&A] Axel85:
Don't mind about ota updates... I m on cyanogenmod 13. Are there any info about those parameters?
[Nexus 7 (2013) Q&A] k23m:
# Size
touch.size.calibration = diameter
touch.size.scale = 6.3284
touch.size.bias = 39.9752

# Pressure
touch.pressure.calibration = amplitude
touch.pressure.scale = 0.0048

Touch Device Configuration​

Let us know how it goes.
[Nexus 7 (2013) Q&A] Axel85:
Changing the touch pressure scale parameter seems to not do anything to the system
[Nexus 7 (2013) Q&A] Axel85:
Tonight I had some spare time to try modding the file. I can say for sure that all the parameters I put in the file change absolutely nothing. I m on cm13 don t know in other ROM if it s the same
[Nexus 7 (2013) Q&A] tinOFbeer:
I know the topic is old, but maybe someone else will have this problem.

The solution is very simple, all you need is the Kernel with touchscreen force update patch.

I personally use a kernel named Glitch (Pure version) https://xdaforums.com/showthread.php?t=2449919

After flashing, the touch screen started working again.

After all you can write the original software, the touch will still work.

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Nexus 7 (2013) Q&A] k23m:
But these are the same force update patches as initially tried by the OP. They did not work. These various firmware versions may or may not help, but the only reliable solution is calibration which compensates for touch screen manufacturing and assembly tolerances. So far we have not found an alternative to....

Incidentally, once a force update patch is applied you don't need this kernel anymore.
[Nexus 7 (2013) Q&A] tinOFbeer:
I also tried all the patches, none of them helped. I tried this on two different chinese PCBs and two tablets (one 16GB with a replacement screen and the other 32GB with a factory screen) without success. Flashing the mentioned kernel has restored the touch, on both, and it works perfectly.

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Nexus 7 (2013) Q&A] mememel:
I launch TWRP recovery with my old USB Board, i launch the new Glitch kernel installation. I reboot everything.

I switch the USB board, and now touchscreen issue is over and everything works perfectly !!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Vivacity:
This is Old twrp . New recovery for a800i can be found here http://xdaforums.com/samsung-a-series/orig-development/recovery-twrp-3-0-1-0-galaxy-a800i-f-t3350856

Official release of TWRP recovery for the SM-A800I, Exynos5433

1. You will need to download and install Odin on your PC.

2. Once you have Odin installed, download the proper .tar file for your device from the download link below.

3. Power off your device. Turn on your device using the proper key combo to get into download mode and plug usb cable

4. Use the AP button to browse to and select the tar file that you downloaded

5. Uncheck Auto-reboot and flash

Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.

Download link: https://dl.twrp.me/a8hplte/

Source: https://github.com/TeamWin/android_device_samsung_a8hplte

Recovery made by androidlover.

Flash this at your own risk. Make sure that you have stock firmware downloaded from SAMMOBILE in case of problems. This will trip knox counter. Last, no one here is responsible of what you do with your device. This recovery is meant for only samsung A800I with exynos chipset. Note on some android it is required to enable OEM unlocking when flashing. Go into Settings -> Developer Options -> OEM unlocking
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] superstarrazik:
thanx going to try soon thanx brother
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Arifshaikh1996:
Hey brother did anyone have any Custom ROM for Galaxy A8 2015
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mumuni:
Am having the same question.

Any nougat custom rom for our phone.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] theheartbenvn:
I don't think there are any custom ROM for this phone, as i have been desperately searching for them.
[MDA III, XDA III, PDA2k, 9090 General] tatotato:
The board ID of the Telecom New Zealand Harrier (CDMA) is 0x4.

Just so everybody knows.

p.s. I tried to add it to the wiki, the page is locked.
[Mate 8 Q&A, Help & Troubleshooting] milili:
Hi everybody

So I have this major problem with my mate 8 which is when I go into Memory and storage settings it shows that I have more than 10GB of image in my phone and to be sure I deleted every single image in my phone but the problem still persists.

I had the NXT-L29C185B103 firmware and I thought that it was a bug and with a update it will be gone but after updating to NXT-L29C185B162 it still shows that I have ridiculous amount of images in my phone.

What should I do and what is the problem ?

View attachment 3680304

P.s. my phone is not rooted
[Mate 8 Q&A, Help & Troubleshooting] jbmc83:
hm try an app like es file explorer, it allows u to analyze all contents of your storage according to file size and type. that may give you a better overview on where the culprit lies...
[Mate 8 Q&A, Help & Troubleshooting] milili:
I used your advice and analyzed sd card with es file explorer

It seems that the total amount of used space and free is right but emui just reports my videos as images which is kind of weird

I guess I have to put it on account of some bug in android 6 and emui 4 collision

Hope this gets fixed as well as the notification issue and app crashes

Anyway

Thanx for the help

I appreciate it
[Samsung Galaxy S7 Edge Questions and Answers] VEAWA:
After a couple of hours on my pocket i noticed that there is a lot of dust under the glass just on the top of home button. No way to clean it. It´s sucks, phone which is supposedly IP68 water and dust resistant in two hours looks like my old note 4. Can´t take photos for now.

Any of you guys with black phone also noticed that? I can live with but it drive me crazy.

Cheers.
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
You sure it's under the glass and not just stuck to the top? It's strange that dust could get through. If so, I would contact the retailer and get it exchanged as it sounds like a defective handset.
[Samsung Galaxy S7 Edge Questions and Answers] timtom67:
I'm having the exact same problem...it is driving me crazy.

Do you also own the black version?
[Samsung Galaxy S7 Edge Questions and Answers] VEAWA:
Yes, black version.

I went to Samsung customer service. They told they dont see nothing strange (of course). They offered to send it to Samsung official service on Madrid (Spain) to check if there is some kind of physical damage and let them decide what to do.

So probably i will do that on monday. other 2 weeks without my phone.

Someone else with this problem? I just want know if its a problem or something normal.

Cheers.
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
Do you have any photos of it?
[Samsung Galaxy S7 Edge Questions and Answers] StreetkillnHD:
Any little defects phone company's like to brush off so it saves them money and time.
[Samsung Galaxy S7 Edge Questions and Answers] iz1pp0:
You meant something like this? I have it as well.
[Samsung Galaxy S7 Edge Questions and Answers] daLareid:
That sure looks annoying.
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
I noticed that on mine today, a quick scrape with my nail removed it
[Samsung Galaxy S7 Edge Questions and Answers] iz1pp0:
How can you put your nail inside this micro hole?
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
I suppose it wasn't actually under the glass. It was at the side of the home button.

The issue in the photo looks more like light from the screen to me.
[Samsung Galaxy S7 Edge Questions and Answers] timtom67:
From my personal experience and "investigation" I was able to remove most of the dust with a very thin sheet of paper and lots of patience. I put the paper between the glass and the frame and pushed the dust out. It took a long time though.

As for the investigation part it appears that the black coating doesn't extend all the way to the edge of the glass which means there's a very narrow part of the glass where the dust can get stuck and stay visible.

It's a near perfect phone with 2 very annoying downsides, fingerprints and dust getting stuck around the glass frame, at least with the black version.
[Samsung Galaxy S7 Edge Questions and Answers] Lostatsea23:
I have this same issue. Driving me crazy...
[Samsung Galaxy S7 Edge Questions and Answers] krico:
If these phones are supposed to be water resistant,have you tried to stick it under a tap to see if it washes out?
[Samsung Galaxy S7 Edge Questions and Answers] Lostatsea23:
No... wouldn't that ruin it cause it water resistant but I don't think under any pressure though..
[Samsung Galaxy S7 Edge Questions and Answers] Rckrz6:
I have that issue around the speaker grill mesh

https://goo.gl/photos/VUv6LyYvH5KQQ6iF8
[Samsung Galaxy S7 Edge Questions and Answers] guaneet:
I have dust as well around the ear piece grill and around my home button.
[Samsung Galaxy S7 Edge Questions and Answers] Rckrz6:
It's annoying as hell but I guess I live with it unless it makes it way to the camera or the proximity sensor
[Samsung Galaxy S7 Edge Questions and Answers] xile6:
Sounds like a defect.

Dust under the screen means that your phone is not water proof.

Id go back to the store and get another one.

I had this with a gaminng system. Took it back and got another one.
[Samsung Galaxy S7 Edge Questions and Answers] Rckrz6:
It does not mean it's not water proof it just means it's not sealed around the edge, it's sealed further in as there's a small crevice
[MX Player] tech_heart1:
For Android MX Player is quite awesome but for windows phone the app still needs updates but now recently they added subtitles support for windows phone but there is not mentioned anywhere how to make the subtitles play during the video plays! So,thats my question if you guys know any link or anything that would really help then plz reply to the thread! :)
[Samsung Galaxy S7 Edge Questions and Answers] toofimoofi:
I cant find any ftp server apps that allow ext sd writing on my S7Edge. Any tips?

Ps: found one. Solid Explorer with ftp server plugin. Pretty neat :)
[Samsung Galaxy S7 Edge Questions and Answers] masiegel:
I am using Total Commander with FTP-Plugin. As far as I know, writing to exSD is only possible under Android 6.x when rooted.
[Samsung Galaxy S7 Edge Questions and Answers] toofimoofi:
I am rooted :)
[Samsung Galaxy S7 Edge Questions and Answers] masiegel:
How did you got root? As far as I know root isn't available yet. Has the KNOX count changed? Thanks in advance
[Samsung Galaxy S7 Edge Questions and Answers] toofimoofi:
Knox gets tripped yes.

Install twrp from this forum. Format data or else u cant access internal sd from you twrp.

Then flash superuser beta that i uploaded here for you:

http://www.filehosting.org/file/details/552120/BETA-SuperSU-v2.68-20160228150503.zip

Voila. Root and everything works like a charm.
[Samsung Galaxy S7 Edge Questions and Answers] Brava27:
I can't seem to get it changing...

Thanks
[Samsung Galaxy S7 Edge Questions and Answers] dannejanne:
Third party fonts does not work unfortunately. Let's hope it gets fixed in an update. For now you have to install fonts from the Galaxy Apps app.
[XDA Assist] :
I launch RUU to update my htc but when it gets to rebooting bootloader the phone just boots normally and the update utility gets stuck at Waiting for boootloader.

I try the command line fastboot oem rebootRUU it does the same (the phone boots normally, and gets stuck at the first HTC white screen). WHY??
[XDA Assist] NOSTALGIA:
Hi

Thank you for using XDA Assist

You can create an account and find the HTC phone you have on this list and you can ask Q&A sections for help regarding your problem here

http://xdaforums.com/htc
[Google Chromecast] twister2000:
Hello,

I've got a problem with my setup.

I connected Chromecast through the HDMI to VGA adaptop (with audio output) - the setup worked fine straight after connecting power to the Chromecast.

Everything was fine for a day or so and then I turn on the TV and the screen was black.

I checked the connections etc but no joy - I tested all components separately and everything works as expected.

I think the issue might be related to the recent Chromecast update... is that possible?

Does anyone else has a similar problem? What I could check/do to sort it out?

Thanks!
[Google Chromecast] xelemorf:
Hi,

Not sure if this can help, but I had a similar (blank screen) issue when the chromecast device was starting up with my monitor turned off (connected with a hdmi/analog audio splitter - for audio transmit only). After turning the monitor on and restarting the chromecast everything seems to be fine, guessing chromecast would initialize the display at boot time only.
[General Questions and Answers] joey_xda:
Is there any way to make my Bluetooth connection undetectable ? I have a non-rooted ZTE Zmax2 on lollipop. In the Bluetooth settings, there is no option to turn off discover mode. If I use my other phone to search, my phone always comes up. I use a Bluetooth headset so turning off Bluetooth completely is not an option.

Thanks
[Onetouch Idol 3 Q&A, Help & Troubleshooting] capitanazo:
first of all sorry for my english but i couldn't find help in spanish so here it goes.

about a week ago i installed AICP on my alcatel 4.7" and everything was great until two days ago when my phone lost signal over night. at first i thought it a carrier problem, buta day pass and still no signal. i switched sim cards, tried to manually search for networks but still nothing. reflashed AICP+gapps and nothing happened. the same with CM12. sometimes tha phone gain signal an data but i couldnt make call or connect.

so here i am not knowing if i should go back to stock o what to do. i need help so i dont loose a great phone.

saludos
[Samsung Galaxy S7 Edge Questions and Answers] Pilz:
I was updating some apps from the playstore and decided to check my voice mail by holding the 1 key in the dialer, but then my phone rebooted. Now, it won't boot past the TMO screen no matter what I do. I've tried wiping cache in recovery, and everything but a factory reset because I have a pin/fingerprint set up. I've heard that it will lock you out of your phone for 3 days if you factory reset from MM for security reasons, hence why I haven't done it. I can't find the firmware to sideload for the T-Mobile variant, can someone shed some light on this issue? It's rather annoying to have it softbrick for no reason, and not have the firmware to fix it. If someone has the firmware that would be great, or if they know how to fix it.
[Samsung Galaxy S7 Edge Questions and Answers] t12icky0:
you can bypass FRP(the lock after reset). ive done this with about 5 s6 edges. I just bypassed one last night. i would assume it prolly works with the s7 edge also.

https://www.youtube.com/watch?v=ogMtWt7Znxw
[Samsung Galaxy S7 Edge Questions and Answers] Pilz:
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
[Samsung Galaxy S7 Edge Questions and Answers] t12icky0:
Good luck