yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro Guides, News, & Discussion] trion:
No it doesn't use bleutooth, only nfc, you take it of sound is gone. here is a video of it https://www.youtube.com/watch?v=JhucQbcVv7s

I find it strange that NFC still works with it when turned off. But at least no ghost touches then. :D

Edit: nevermind I allways thought it uses NFC, but it seems to read the magnetic field of the phone speaker.
[OnePlus 7 Pro Guides, News, & Discussion] tremendouz:
My device is the 12GB version. Build date 09/05

I'm neither able to reproduce that sh*t on OOS 9.5.1, nor on Android Q Beta. I only get that green blinking dot in CPU-Z on those, which some named a proximity sensor.

In OOS 9.5.5 the green dot went away in CPU-Z. If NFC enabled I got ghost touches only in CPU-Z, if NFC disabled I haven't had a single random touch till now.
[OnePlus 7 Pro Guides, News, & Discussion] BoboBrazil:
This is definitely a hardware issue since not all units are affected. Probably poor NFC shielding. OnePlus will never admit there was faulty hardware that came out of their factory though. I returned mine and might order again down the road once issues are resolved.
[OnePlus 7 Pro Guides, News, & Discussion] baiosss:
Same with mine. 8/256GB version, and build date 10/05. With OOS 9.5.1 only blinking sensor. After 9.5.5 I have ghost touches only with nfc enabled.

Στάλθηκε από το GM1913 μου χρησιμοποιώντας Tapatalk
[OnePlus 7 Pro Guides, News, & Discussion] tremendouz:
Although I don't wanna believe this, it might sadly be the truth.

I'm thinking of going the same way.
[OnePlus 7 Pro Guides, News, & Discussion] tWoBrO:
Apparently it didn't happen with anyone in version 9.5.1.

But if this isn't fixed in the next update, I guess we have our answer.
[OnePlus 7 Pro Guides, News, & Discussion] BoboBrazil:
I've seen reports of it happening to people on 9.5.1 as well. If this was a software issue it would affect everyone the same and should be able to be reproduced by anyone in the same firmware.
[OnePlus 7 Pro Guides, News, & Discussion] larsdennert:
It could just be a hardware burn in issue where it shows up after a while. That would explain why people think it is related to an earlier rom. Mine didn't start until 9.5.6 but not right after installing it. So I'm doubtful that it is rom related. Had to turn off NFC but I use it rarely.

They might be able to filter the effect by editing the surface flinger to ignore motions that are not possible for a human finger. Or maybe disable touch when the NFC chip is transmitting though the coil might always be active to power a tag.
[OnePlus 7 Pro Guides, News, & Discussion] frosty5689:
There was a thread on OnePlus forum that was removed saying the ghost touch issue within CPUZ with NFC turned on would be fixed in the next update.
[OnePlus 7 Pro Guides, News, & Discussion] baiosss:
Try this and tell us.

https://forums.oneplus.com/threads/how-i-temporarily-fixed-the-ghost-touch-issue.1043755/

Στάλθηκε από το GM1913 μου χρησιμοποιώντας Tapatalk
[OnePlus 7 Pro Guides, News, & Discussion] s3axel:
Had this issue on my brand new OP7 Pro, too...

It wasn't there from the start but came up at some time during setting everything up. Interesting enough a clear of cache and dalvik in TWRP got rid of it, so far without reappearing...

So I also rather think it's a software issue.

BTW, when I had those ghost touches no setting (NFC, BT, Wifi, Flight mode) did influence it, it was also not related to the launcher (I tried stock and Nova)

Gesendet von meinem GM1913 mit Tapatalk
[OnePlus 7 Pro Guides, News, & Discussion] Nekromantik:
Something people dont understand is if its hardware then you would see this issue on multiple different apps.

I just installed nfc reader which activates nfc chip and no ghost touches.

If the nfc chip had bad shielding then any app that activates the NFC chip would cause the ghost touches.

I do think its software issue.
[OnePlus 7 Pro Guides, News, & Discussion] larsdennert:
Maybe it's this lol.

https://www.zdnet.com/article/new-attack-creates-ghost-taps-on-modern-android-smartphones/
[OnePlus 7 Pro Guides, News, & Discussion] liam_davenport:
Had my unit 3 days ran it fine for 2 days no issue soon as I took 9.5.5 EU OTA a few hours after I got a random reboot suddenly the ghost touch appeared.
[OnePlus 7 Pro Guides, News, & Discussion] marcinsu:
I have ghost touches in firefox and when I'm writing this message in Tapatalk, very bad...

https://youtu.be/j0WJvW5bkYg

Wysłane z mojego GM1913 przy użyciu Tapatalka
[OnePlus 7 Pro Guides, News, & Discussion] Nekromantik:
when browsing a site? or scrolling in firefox?

i get no ghost touches in firefox

only cpuz
[OnePlus 7 Pro Guides, News, & Discussion] marcinsu:
When browsing this site: https://forums.oneplus.com/threads/how-i-temporarily-fixed-the-ghost-touch-issue.1043755/

Wysłane z mojego GM1913 przy użyciu Tapatalka
[OnePlus 7 Pro Guides, News, & Discussion] paatha13:
I don't know guys but probably I'm not gonna keep the phone if had any kind issue anywhere even cpuz only.

And will re order after a month hoping newer batch unit things get resolved ASAP.

Those issue is Total unacceptable to me and Oneplus has no excuse.
[OnePlus 7 Pro Guides, News, & Discussion] tremendouz:
I don't really care anymore for now.

That's just to much money for having a device that nobody knows if it has software or hardware issue. But for sure is, that when we receive the information at some day, it'll be to late to apply RMA. Therefore I just applied RMA.
[OnePlus 7 Pro Guides, News, & Discussion] MisiekDP:
I copied post from OnePlus forum. I think that this is important information.

----------------------------------------------------------

PREVIOUS POST:

----------------------------------------------------------

I've turned NFC off and voila the issue is gone. But in no way is that a solution or even a workaround that's sustainable. The way I see it is:

1) it's a hardware problem and OnePlus starts a whole Repair program for affected devices.

2) it's a hardware problem but instead of OnePlus doing a repair program, they find a way to mitigate it in software (something like reducing NFC power levels or decreasing touch screen sensitivity). not ideal but more cost effective for OnePlus.

3) Just a standard software issue.

I'm airing on the side of 1) unfortunately though, because turning off NFC doesn't mean it's a software issue, it just means it's NFC related. Plus if this was software I get the feeling the ghost touches would happen all over the screen, not just near the top.

PS. Has anyone confirmed where the NFC antennas are in the OP7 pro? My bet it's right where the ghost touches are occuring.​

----------------------------------------------------------

REPLY:

----------------------------------------------------------

The NFC coil is not where the touches are occuring. If you draw a line down from the popup camera, and then across from the centre of the main camera, the point where they intersect is where the NFC coil is. About 1/3rd down the screen and 1/3rd from the right.

I'm a developer and I've had a look through kernel logs coming out of my phone as the touches are occuring. What you see are memory errors whenever ghost touches occur, and none when ghost touches aren't occuring - that can't be a coincidence. We also know that there is a memory leak within the touchscreen driver on a function called get_touch_points(). My current best theory is that the driver has a memory management issue, resulting in random blocks of memory being returned instead of proper data about touch locations. I think NFC probably causes the issue since it'll be using the same kernel memory space and will probably have quite a lot of kernel memory, meaning it's more likely to trigger these memory issues within the touchscreen driver.

We also know the issue isn't present on 9.5.1 on the Pro, which is using the April 23rd kernel build. The Pro 5G does have ghost touches on 9.5.1, but since the android security patch for that is more recent, it's very likely the kernel build is also more recent. The kernel build would largely be independent of the OOS version so there being a driver issue makes sense at this point.

That's my view on the issue. Hopefully that gives you confidence.

Edit: Typo

Also I should probably mention if it's not already obvious that this is my personal opinion of what's happening given the knowledge I have. I don't have any inside information from OnePlus or anything like that, so it is possible I'm completely wrong. I'm working off information from here and on the open source repository for the 7 series kernel that's on GitHub.
[OnePlus 7 Pro Guides, News, & Discussion] Aniket_IITM:
It's software issue

View attachment 4770705
[OnePlus 7 Pro Guides, News, & Discussion] Nekromantik:
upcoming weeks is vague.

could be 1 week or 1 month!

Plus I am worried it will take longer coming to 5g model
[OnePlus 7 Pro Guides, News, & Discussion] BoboBrazil:
This is gonna be like the OnePlus One touchscreen issues all over again
[OnePlus 7 Pro Guides, News, & Discussion] greystealth:
The internet is making this a bigger issue than what it is. It happens rarely and goes away completely if you turn off NFC. There's no reason to have NFC on all the time anyways unless you're using Google Pay all day for some odd reason. OnePlus is aware and investigating. I'm sure it'll be addressed in an update.
[OnePlus 7 Pro Guides, News, & Discussion] worldsoutro:
The fix OnePlus will put out is to buy the OnePlus 7t pro ?
[OnePlus 7 Pro Guides, News, & Discussion] parsa5:
Im sorry, but it does not happen rarely for me. I had turned on my NFC to use google pay and forgot to turn it off. I started noticing the ghost touches everywhere throughout the use of the phone the next day. Thats when I remembered that NFC was still on. They really need to solve this issue with this next OTA.
[OnePlus 7 Pro Guides, News, & Discussion] midasziom:
Newest Oxygen OS 9.5.7 and no ghost touches!

Already confirmed on OP forums.
[OnePlus 7 Pro Guides, News, & Discussion] hvihavai:
Yes, after quick testing, this seems to be fixed... :)
[OnePlus 7 Pro Guides, News, & Discussion] Jonathan.Parker2005:
Yeppers. I can confirm after an update to 9.5.7 I've had zero ghost touches.
[OnePlus 7 Pro Guides, News, & Discussion] baiosss:
What about «thank you for your feedback» random pop-up messages?

Στάλθηκε από το GM1913 μου χρησιμοποιώντας Tapatalk
[MeMO Pad 7 Q&A, Help & Troubleshooting] celphtitled885:
i have a lifesheild tablet i got from the security company for free problem is evvverything is locked down i cant get in to recover nothing its just a monitor at this point .......ive seen some old threads that someone had a password to unlock safelock and allowed them to turn on certain features does anyone have i guess the updated password to bypass safelock? i can tap the screen a few times and it requests a password to do anything
[MeMO Pad 7 Q&A, Help & Troubleshooting] jerrysmatrix:
Try 2021 or pick up on this thread here: https://xdaforums.com/showpost.php?p=79595840&postcount=13
[OnePlus 7 Pro Guides, News, & Discussion] SAO:
I've been searching all around, called my Carrier support, opened a Bug report on OnePlus for this issue posted around the forum, no one was able to help.

I even have a thread (where i will link this one) asking people with whom it worked and didn't work... and now i found the solution. I just tested on my 7pro, and it worked!

Follow this link and the article, and report back to see if it works!

How to enable VoLTE and WifiCalling on OnePlus 7pro

I'll be happy to know if i helped some people!

EDIT : sorry, if this was discussed and a solution already found. I normally really search for answers, but i guess i missed that one. Thanks and credit goes to [MENTION=697919]dalle3[/MENTION] to have posted it first in this thread. I guess i hovered over that thread without seeing it as it wasn't a "solution" as per say. This is the original thread : Original thread
[OnePlus 7 Pro Guides, News, & Discussion] dalle3:
You have searched but obviously didn't read what i have posted here few days ago about volte switches 4 op7

Nice to see someone made article from that

cheers
[OnePlus 7 Pro Guides, News, & Discussion] SAO:
Damn man, i'm sorry if i missed it. I don't like to double post.. let me try to find it.
[OnePlus 7 Pro Guides, News, & Discussion] dalle3:
Hi, sorry for late response, I'm still at work

No problem at all have just shared way to make it work

but i didn't start that thread , it will be better and easier to find if mod or someone who started thead change name or add solution founded .

Cheers
[OnePlus 7 Pro Guides, News, & Discussion] Fostil:
You can enable switches for volte, but they dont do a thing if your operator didnt certified op7...
[OnePlus 7 Pro Guides, News, & Discussion] dalle3:
I don't think here in Austria 3 provider and A1 are certified oneplus phones but these phones work well with ims profiles from other countries like OnePlus 6t for 3 (three at)

Have used profile from 3 uk telefonica , and for A1 network here profile from German telekom and from India booth worked volte and wifi calling ,

done with qpst

Without any problem no such need for certification

Cheers
[OnePlus 7 Pro Guides, News, & Discussion] mcn1970:
works perfectly for Orange Romania. thankx
[OnePlus 7 Pro Guides, News, & Discussion] mazdamiata210:
AT&T and there is no option to enable it in this menu
[OnePlus 7 Pro Guides, News, & Discussion] Osksnake:
How do you turn off system log after this?
[OnePlus 7 Pro Guides, News, & Discussion] mikey_sk:
i got the Chinese version of the phone (12gb ram version for a great price from wonda). Flashed international oxygen OS and my wifi calling and 4g calling/volte work with Three UK. didnt need to do any of the above.
[OnePlus 7 Pro Guides, News, & Discussion] Tex_usa:
I'm having that very problem. The switch is there but it always reverts back to H+ when calling.
[Galaxy Note 4 Android Development (Snapdragon)] PasSlert:
Hello,

First of all, thank you for you continuous work and courage to keep our devices up to date, by you I mean the whole awesome team !

Updated of TWRP 3.3.1-0 was successfully done within TWRP 3.3.0-0 - flash image - recovery.

Update of Bootloader_Modem file was a bit longer :

- with the provided Odin3 v3.13.1 - the ID:COM was going crazy connecting/disconnected no matter what USB port (2.0 and 3.0) I was using and I was using OEM cable.

<ID:0/005> Added!!

<ID:0/005> Removed!!

<ID:0/005> Added!!

<ID:0/005> Removed!!

...

Updating Samsung Mobile Phone Driver didn't help (but just in case, link = https://xdaforums.com/showpost.php?p=78823944&postcount=623 )

Even after a restart of Windows 10 OS.

Luckily I had kept a zip of Odin3_v3.10.7 close by me (this was the version I used for my previous BL/CP update) and using this version was fine, my n910f is correctly on DRI2_DQL1.

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1100)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> aboot.mbn

<ID:0/005> NAND Write Start!!

<ID:0/005> modem.bin

<ID:0/005> NON-HLOS.bin

<ID:0/005> rpm.mbn

<ID:0/005> sbl1.mbn

<ID:0/005> sdi.mbn

<ID:0/005> tz.mbn

<ID:0/005> RQT_CLOSE !!

<ID:0/005> RES OK !!

<ID:0/005> Removed!!

<ID:0/005> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

I'll report if anything good or bad is noticed within the next few days.

Thank you again,
[Galaxy Note 4 Android Development (Snapdragon)] Apex Predator:
Updated to 3.3.1-0 and for some reason it refuses to remember the correct date and time. Every time I boot in it defaults to something like 1971-01-20 with a completely wrong time for my time zone. Some other basic setting like reversed navbar would not stick every time.

Reverted to 3.2.3-0 and everything's back to normal. Any ideas? I though maybe my phone was somehow causing it but once I reverted the problem disappeared.
[Galaxy Note 4 Android Development (Snapdragon)] mangojack01:
[MENTION=6005084]ripee[/MENTION]

Has the issue been resolved yet ?

It only happens to me when I do a full complete wipe for a clean flash.

It doesn't seem to affect a roms integrity when restoring a backup.

Once a rom has been run for a length of time the TWRP clock updates ok.

All these backups are less than 3 days old.

All are the latest builds of each respective rom.

The oldest backup is Xenon
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
The easiest way to resolve this is to wipe your phone, flash stock, then start again with twrp and your rom. TWRP gets its time and date from the system clock, which is set by the rom, which is set by your mobile company.

I had the same thing happen on my wifi-only tablet, and reflashing stock is the only thing that worked. No idea why this happened in the first place, perhaps some twrp or rom update went screwy, and some file or folder permission isn't allowing it to be set properly.
[Galaxy Note 4 Android Development (Snapdragon)] kevintm78:
I'm still using 3.2.3 so this might be irrelevant info, or just wrong info, but it looks like that .twrps file on the internal sdcard is where the settings are stored. I had never updated my time in twrp so it had been on mountain time (-7) and the file at /storage/emulated/0/TWRP/.twrps reflected that but I just changed to it to my correct time, eastern standard (-5) (it's still daylight savings so its EDT instead EST for the moment). Now that hidden file has been updated with EST and EDT references.

I guess if you're formatting the internal sdcard there's no way to protect it, but perhaps users could copy it and then replace it after a full wipe assuming TWRP is not being updated. If updating TWRP it might just be safer to redo the settings or, like I apparently have, just not pay it any attention. :p

Since there's a variety of file explorer apps out there I thought I would add that some file managers may use the symlink path of /sdcard/TWRP/.twrps or mnt/sdcard/TWRP/.twrps but for those that are curious the actual path is /storage/emulated/0/TWRP/.twrps

[IMG="png-pong"]https://xdaforums.com/attachment.php?attachmentid=4964947&stc=1&d=1583426980[/IMG]
[Galaxy Note 4 Android Development (Snapdragon)] mangojack01:
I agree, it's more of an annoyance than anything else, especially to a grumpy, slightly aspie, 69yo pedant.

I run trwp v 3.3.1

I've tried cut n paste .twrp after formating internal sd many times in many ways via twrp file manager.

eg, wipe everything internal, reboot recovery, setup recovery, replace/ overwrite or edit new .twrp file, reboot recovery, but without success.

cest la vie

Thanks for your feedback, I'm sure others also may find it enlightening.
[Galaxy Note 4 Android Development (Snapdragon)] zfk110:
Hi, Ripee

I got two 910V I bought it off one has bad efs partition and one has bad speaker/mic I was thinking to copy bad speaker/mic efs partition to another one, but copying over efs partition didn't do anything. I thought it will copy over IMEI stuff to this second phone?
[Galaxy Note 4 Android Development (Snapdragon)] tripLr:
You have an interesting challenge. .

Have you tried a restore sd card ?

Check the emmc brickbug if you can.

I believe the hack to get root for the Verizon note 4 writes to the efs partition to clone it into a developer edition. Which every with a hacked Verizon phone like mine has the exact same IMEI 1000000000000 or something like that
[Galaxy Note 4 Android Development (Snapdragon)] louisJJ:
Hi

how to flash N910FXXU1DRI2_N910FXXU1DQL1.tar (bootloader_modem.tar) with Heimdall ? I understand I have to untar and flash files separately, but there are not only two files in this .tar, there are 7 files !

Can you guide me please ?

Thanks
[Galaxy Note 4 Android Development (Snapdragon)] dsat53:
Incase you haven't solved it yet.

This worked for me on manjaro-linux with heimdall installed as well as on debian-sid with heimdall-flash.

As root:

heimdall detect

To make sure your device is detected

heimdall flash --APNHLOS /tmp/e/NON-HLOS.bin --ABOOT /tmp/e/aboot.mbn --MODEM /tmp/e/modem.bin --RPM /tmp/e/rpm.mbn --SBL1 /tmp/e/sbl1.mbn --DBI /tmp/e/sdi.mbn --TZ /tmp/e/tz.mbn --no-reboot

Where for example /tmp/e/ is your path to files to flash.

When process finished successfully pull battery and reboot to recovery.
[Galaxy Note 4 Android Development (Snapdragon)] louisJJ:
Thanks a lot! :)
[Galaxy Note 4 Android Development (Snapdragon)] louisJJ:
Hi,

I am having troubles with the modem that is listed in this thread...N910FXXU1DQL1....I have poor reception.

Can someone point me to a full list of modems I can test ? I am installing LineageOS 16 from this tuto.

Thanks
[Galaxy Note 4 Android Development (Snapdragon)] FlipPhone:
Just adding this here in case anyone else is looking for it

N910FXXU1DRI2_N910FXXU1DRI1.tar.md5
[Galaxy Note 4 Android Development (Snapdragon)] v00d007:
Caution: backups made with older versions than v3.4.0 seem to be not compatible. I wanted to restore a backup I made with v3.2.1 with v3.4.0 but the system couldn't boot. Verified this two times. Had to go back to v3.21 to perform a successful restore.
[Galaxy Note 4 Android Development (Snapdragon)] Youms:
It's better using TWRP 3.3.1 for all flashing operations.
[Galaxy Note 4 Android Development (Snapdragon)] Qistina Ardy:
I think we have the same odin
[Galaxy Note 4 Android Development (Snapdragon)] bmwdroid:
Odin doesn't have to be installed.

Just to doubleclick any of the different .exe starts the appropriate version.
[Galaxy Note 4 Android Development (Snapdragon)] Qistina Ardy:
Will the bootloader+ moderm work on ressurection remix pie rom and fix the can't read sim card issue?
[Galaxy Note 4 Android Development (Snapdragon)] CokelPX:
Samsung galaxy not 4

SM-N910S korea (treltest)

Can enyone tell me

Where i get

Ty
[Galaxy Note 4 Android Development (Snapdragon)] bmwdroid:
Better clarify what you want to get?

Bootloader, modem, TWRP?

As I found out yours has Exynos CPU.

Didn't you know?

Here is a Snapdragon sub thread.

Better look here or here.
[Galaxy Note 4 Android Development (Snapdragon)] crispaul12:
I have a Samsung Galaxy Note 4 (SM-N910F; trltevzw; Bootloader:N910VVRU2BOG5; PDA:N910FXXU1DQJ1) on which I would like to install the TWRP recovery; I tried with Odin, but it is not possible (Fail-Auth) probably because my bootloader is locked.

How can I bypass the bootloader lock problem?

Thanks
[Galaxy Note 4 Android Development (Snapdragon)] bmwdroid:
Acc to TWRP site

<International & Americas (SM-N910F/trltexx, SM-N910G/trltedt, SM-N910P/trltespr, SM-N910R4/trlteusc, SM-N910T/trltetmo, SM-N910V/trltevzw, SM-N910W8/trltecan)>

So if it says trltevzw it should be N910V.

I assume Verizon.

There's a special thread afaik for this cause of its specific problems.

Perhaps it works to autoroot first 🤷‍♂️ but I don't know.
[Galaxy Note 4 Android Development (Snapdragon)] crispaul12:
Thanks

May you please point me to the special thread?
[Galaxy Note 4 Android Development (Snapdragon)] bmwdroid:
Gotta search here: https://xdaforums.com/c/verizon-samsung-galaxy-note-4.3674/

Doing more searching for you I'm to lazy.

N910V plus TWRP, root, ROM one after another should give the results you need.
[Galaxy Note 4 Android Development (Snapdragon)] crispaul12:
thanks
[Galaxy Note 4 Android Development (Snapdragon)] Unidave199:
Hya Gang... I have the SM-910P with the Q15 variant which is the last one Sprint put out over the air. Is there an advantage to updating to the last Bootloader/Modem (PK1)?
[Galaxy Note 4 Android Development (Snapdragon)] pointbob:
odin does not connect in download mode - i have 910v

however if i connect my phone via safe mode then it does connect with odin but then fails to update twrp. i tried update it in twrp but file N910VVRU2CQL1_N910VVRU2CQL1.tar was not recognized as an image (since the dl here is a tar)...help (currently on a older 3.0 vers of twrp...worried it might fail update lineage )...also im on stock rom

sort of a bummer because i must have had odin workign at 1 point on my windows 10 machine....since i rooted the phone last year....