Database Users

Howto: Solving notification issues. [ROOT]

After having a great deal of stress regarding the notification issues, I have come up with a solution.
Please note:
1. I have no idea why my solution works on only this one version of the firmware, but I can only reproduce it on build number NXT-AL10C00B129SP02 (The second-to-newest Chinese firmware). I cannot reproduce the solution on other versions and have not yet gotten notifications working on them, so please make sure you have the same version of everything as I do to make it go smoothly. I have only tried and failed on the latest Chinese and the latest international firmware, so perhaps an older version of that will have good results.
2. I can't guarantee this will work for everyone. Everyone has a different combination of software and settings, etc. What works for me very well may not work for you, and vice versa.
That being said, here is what I did, and how you can test and make sure it's working right for you.
Step One: Set up the OS.
Get NXT-AL10C00B129SP02 (available from the development section of this forum). You can unpack it and flash it with flashboot. The unpacking tool is as follows:
http://fs1.d-h.st/download/00173/wwfQ/HuaweiUpdateExtractor_0.9.9.3.zip
This tutorial won't cover flashboot usage. Please figure it out with google and feel free to ask if you need additional help.
You will then need to get TWRP installed. Please refer to root thread.
Getting into TWRP, please first format your /data partition, then flash the following in order. (maybe different versions will work, but these are what I used, and they worked for me, so maybe better safe than sorry.)
---
decrypt boot B129SP02.zip (can be found in this forum)
BETA-SuperSU-v2.66-2016013015024.zip
open_gapps-arm64-6.0-micro-20160108.zip
---
Then, clear cache and dalvik cache, boot the device up, and set it up.
Get into developer options and turn on ADB debugging. We will use adb to check that everything is working properly. Also, configure an email account with gmail. We'll use gmail to test as well.
Step Two: Doze Settings
Download and install Doze Settings Editor, available from the following:
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
Open SuperSU, then open Doze Settings Editor. SuperSU will ask for root permission, please grant it.
Go into Doze Setting Editor. To keep it easier, go to preferences and change display from milliseconds to seconds.
Set the following, from the top down.
30, 0, 0, 20.0, 0, 0, 12, 12, 2.0, 60, 600, 2.0, 3600, 300, 60, 20
(Easier way to do this is to load tuhinxp04's profile and just change idle timeout and max idle timeout to 60 sec and 600 sec respectively)
Step Three: Test
Now, we will test! Make sure you have adb on your computer, plug your phone into your computer, and run the following commands:
adb shell
dumpsys battery unplug
(turn off the screen of your phone)
dumpsys deviceidle step
(repeat this command until the state is IDLE.)
Now, check the status with this command:
dumpsys deviceidle
Things to look at from the output of this command are:
mState
mNextAlarmTime
Basically, mNextAlarmTime will count down to zero. When it reaches zero, mState will go from IDLE to IDLE_PENDING (and that's when you'll get your notifications). The settings we put in Doze Settings Editor make it so that the countdown starts at one minute, then increases twofold each time until it hits ten minutes. So the longest you'll wait to receive an email notification would be 9 min, 59 seconds.
If everything went well, the device will go from IDLE to IDLE_PENDING after the countdown. Send a test email and watch it arrive.
That's it! If this works, you'll get your notifications. You can adjust the numbers in Doze Settings Editor to match your personal preference.
Now here's the odd thing. With the latest Chinese firmware and international firmware, it does not go into IDLE_PENDING after the countdown. Instead, the countdown goes from +1sec to 0sec to -1sec and counts up, when debugging with ADB. I have no idea how to fix this, but if anyone with other firmware wants to try this solution and see what happens, hopefully we can fix notifications for all software versions. For now I'll stick with NXT-AL10C00B129SP02
UPDATE: I have somehow gotten AL10C00B129SP02 to behave the same as the newer version. I will look further into this as best I can and figure this out. So please hang on a little longer

Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!

Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I tried this on my L29 running B162. It seems to have made no difference at all. Notifications are still significantly delayed, especially for email.
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I think this is a Huawei EMUI thing. If you look back at older phones on older versions of Android (P8, Mate 7, etc) they all had this issue (and still do). People try to blame doze, but this issue existed long before Marshmallow was around.
I have the European L29 model and I see this issue. Don't let anyone try to tell you that model doesn't suffer from it. It's real.

Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102

[FIX] Touchscreen freeze / dead zone(s) after MHC19J

..........
TLDR - Permanent Fix is in the 2nd post
..........
Update: [2016.11.28]
I created a NEW permanent fix that will work on all versions, MM 6.0.1, N 7.0, N 7.1.1. Does NOT require root/supersu, does NOT require running beta 7.1.1.
See 2nd post
Thanks to user Trevonn for uploading npf26f touchscreen firmware.
Click to expand...
Click to collapse
Update: [2016.11.23]
http://forum.xda-developers.com/nex...dead-zones-t3361123/post69748579#post69748579
https://code.google.com/p/android/issues/detail?id=205223#c146
According to user Trevonn and users on the google bug report thread, the previously mentioned fix appears to have made it into the beta release channel, Android 7.1.1 DP2
Click to expand...
Click to collapse
Update: [2016.10.14]
https://code.google.com/p/android/issues/detail?id=205223#c120
Project Member #120 [email protected]
Hi,
The development team has fixed the issue that you have reported and it will be available in a future build
Thanks
Status: FutureRelease
Click to expand...
Click to collapse
Update: [2016.10.12]
https://code.google.com/p/android/issues/detail?id=205223#c119
Project Member #119 [email protected]
Update : we are working on the fix and will update more on this when we will fix this issue
Click to expand...
Click to collapse
Update: [2016.10.05]
https://code.google.com/p/android/issues/detail?id=205223#c112
Project Member #112 [email protected]
We are still working on the issue, we will update on this once we have any updates
Click to expand...
Click to collapse
Update: [2016.09.26]
Google finally looking into the problem and changed priority from small to high.
https://code.google.com/p/android/issues/detail?id=205223#c96
Project Member #96 [email protected]
update: This issue was tough to reproduce, we have got all the information from the external thread and we are making progress on it, thanks for the inputs. we will keep you posted more on this issue as it becomes available
Cc: [email protected]
Labels: -Priority-Small Priority-High
Click to expand...
Click to collapse
Update: [2016.09.03]
Due to security changes in Android N (Nougat) 7.0 you now need to have SuperSU installed for this fix to work.
Android M (Marshmallow) 6.x.x users do not need to have SuperSU installed, though it would be preferable.
Update: [2016.07.23]
Video demonstration of issue (thanks Troy Spicer):
https://www.youtube.com/watch?v=sfoAVnFFZrg
Update: [2016.06.21]
Google finally assigned the bug to development for further investigation.
If someone at Google is reading this thread, the super quick way to mitigate the problem is to simply package the older synaptics touchscreen firmware released with mmb29k-mmb29v and update the version # so it will overwrite existing firmware.
You can figure out what is wrong with the touchscreen firmware at a later date.
The downside of rolling back, ie having a touchscreen that doesn't behave ONLY while charging for some people where the end-user can obtain a new charger and workaround the problem, if they even use the phone while charging, is IMO better than having a touchscreen that is unusable for some people ALL the time with no simple workaround for the average user other than RMA.
https://code.google.com/p/android/issues/detail?id=205223#c54
Project Member #54 [email protected]
Hi,
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks
Status: Assigned
Labels: Defect-29526586
Click to expand...
Click to collapse
Background:
There is a well documented problem for some charger/device/voltage combos where the touchscreen will become unresponsive when connected to the stock charger. Ultimately the problem is with the charger design but it appears Google made some attempt to mitigate the problem with software in the MHC19J release.
See this thread for the power adapter touchscreen not responsive details
https://productforums.google.com/forum/#!msg/nexus/-rSxrBUMKr0/ao-N4Y6nAgAJ
Unfortunately in doing so it seems they may have put out a Synaptics touchscreen firmware that introduced a brand new problem for folks who've never had any touchscreen problems before, affecting them during *normal* usage rather than the more isolated case of only during charging.
Basically the symptoms are you start getting freezes / dead zones when you leave your device untouched for a couple of seconds. You can cycle the screen on/off to reset the touchscreen but the problem eventually comes back again after a few seconds. It even occurs upon startup when you need to enter your lock code or pattern, making it difficult to get into your device. For most people it will be on the right side of the screen and happen after about 6 seconds of inactivity. Swiping from left to right will sometimes restore responsiveness for a few more seconds.
My theory is Google put out a new Synaptics touchscreen firmware that adjusted the sensitivity of the touchscreen to compensate for the "noise" being generated by the bad power adapters. The change may have been too aggressive as it seems to have had a side effect of being too insensitive for some folks' touchscreen variations resulting in freezes / dead zones.
See these threads for the touchscreen freezes / dead zones after MHC19J details
http://forum.xda-developers.com/nexus-5x/help/touchscreen-freeze-t3335521
https://code.google.com/p/android/issues/detail?id=205223
https://www.reddit.com/r/nexus5x/comments/4anxs3/nexus_5x_not_responding_to_touches_occasionally/
So normally you'd just flash an older factory image and everything would be back to normal. Unfortunately for touchscreen firmware, flashing older factory images will have no effect. Once you have the new touchscreen firmware it will stay in place until a newer one comes out. Thus you can't actually get back to "true" factory by flashing the MDA89E factory image.
There is a way you can force a touchscreen firmware flash. This will be described in the next post.

NEW permanent fix (thanks trevonn for uploading the npf26f firmware)
As of 11/22/16 Google has finally released a fix for the touchscreen, but only on the beta channel.
Either install Android 7.1.1 DP2 NPF26F (or newer)
or
run the following update-touch-npf26f.zip in TWRP.
DOES require unlocked bootloader
does NOT require you to run beta 7.1.1
does NOT require root/supersu
makes NO modifications to your system nor vendor partitions
you will still be completely stock once the update is done, touchscreen firmware is uploaded to the screen's internal processor
IS persistent, you can install any ROM, custom, stock, doesn't matter, fix will remain​=======================
OLD instructions
To make it easier for people to try this fix, I created an update.zip that can be run from TWRP. This will roll back your Synaptics touchscreen firmware to the one that was included with MMB29K - MMB29V and thus fix the problem described above.
The old manual method is still available in the post below.
Update: On Android N (Nougat) 7.0 in addition to bootloader being unlocked you MUST install SuperSU 2.77 or newer PRIOR to running update-touch-vendor.zip There was a security change in 7.0 that causes data written to /vendor to rollback to original. Changes are physically there but get treated as data corruption and "fixed" automaticaly by reed solomon forward error correction. This auto-correct "feature" is disabled if dm-verity is disabled (installing SuperSU would take care of this for you)
You DO need to unlock your bootloader but you do NOT need to be root, however if you choose the 2nd option (update-touch-vendor) it would be best if you were root or you'll see the RED Android corrupt message.
The reason that happens with the 2nd option (update-touch-vendor) is to allow you to run the older touchscreen firmware with a ROM MHC19J (or newer) the /vendor partition needs to be modified to include the older touchscreen firmware (otherwise upon first boot, your rolled back touch screen firmware will get overwritten with the newer touchscreen firmware in /vendor/firmware). Because of how the Merkel-hashtree verification works, if you touch anything in /vendor (or /system), even just changing the date on a file or mounting r/w, it will complain about corruption. If you are running root, it will disable the dm-verity checks for /vendor (and /system), and you will just see the standard ORANGE bootloader unlocked warning.
This was ONLY tested with TWRP 3.0.2-0 for Marshmallow and TWRP 3.0.2-2 for Nougat and with stock ROMs, though it should work with most if not all ROMs.
I ONLY tested it with TWRP flashed onto the recovery partition (ie did not test temporarily loading twrp using "fastboot boot twrp.img")
There are two files available:
update-touch.zip - install this file using TWRP if you just want to rollback the touchscreen firmware.
This REQUIRES you first flash a release OLDER than MHC19J, for example MMB29V and
Do NOT upgrade to MHC19J (or newer) until Google fixes the problem
update-touch-vendor.zip - install this file using TWRP if you would like to rollback your touchscreen firmware
AND keep your existing MHC19J (or newer) Android system release
I also suggest you DISABLE your lockscreen PIN/Pattern before doing any installing of update-touch-vendor.
It is generally good practice to do this whenever you start modifying partitions that are being verified, otherwise parts of Android can get confused and think your phone is stolen and someone is trying to break in, thus attempt to lock you out.

This is the sysfs path for the touchscreen interface
/sys/bus/i2c/drivers/synaptics_rmi4_i2c/2-0020
Code:
[email protected]:/sys/bus/i2c/drivers/synaptics_rmi4_i2c/2-0020 # ls -l
-rw-rw-r-- root root 4096 2016-04-18 00:30 0dbutton
-r--r--r-- root root 4096 2016-04-18 00:30 blconfigblockcount
-r--r--r-- root root 4096 2016-04-18 00:30 blocksize
-r--r--r-- root root 4096 2016-04-18 00:30 buildid
--w--w---- root root 4096 2016-04-18 00:30 check_fw
-r--r--r-- root root 4096 2016-04-18 00:30 config_id
--w--w---- root root 4096 2016-04-18 00:30 configarea
-r--r--r-- root root 4096 2016-04-18 00:30 configblockcount
-rw-rw-r-- root root 0 2016-04-18 00:30 data
-r--r--r-- root root 4096 2016-04-18 00:30 dispconfigblockcount
lrwxrwxrwx root root 2016-04-18 00:30 driver -> ../../../../../bus/i2c/drivers/synaptics_rmi4_i2c
-r--r--r-- root root 4096 2016-04-18 00:30 flashprog
-rw-rw-r-- root root 4096 2016-04-18 00:30 flipx
-rw-rw-r-- root root 4096 2016-04-18 00:30 flipy
--w--w---- root root 4096 2016-04-18 00:30 force_update_fw
-rw-rw-r-- root root 4096 2016-04-18 00:30 full_pm_cycle
-rw-rw-r-- root root 4096 2016-04-18 00:30 fw_name
-r--r--r-- root root 4096 2016-04-18 00:30 fwblockcount
--w--w---- root root 4096 2016-04-18 00:30 imagesize
drwxr-xr-x root root 2016-04-18 00:30 input
-r--r--r-- root root 4096 2016-04-18 00:30 modalias
-r--r--r-- root root 4096 2016-04-18 00:30 name
-r--r--r-- root root 4096 2016-04-18 00:30 package_id
-r--r--r-- root root 4096 2016-04-18 00:30 permconfigblockcount
drwxr-xr-x root root 2016-04-18 00:30 power
-r--r--r-- root root 4096 2016-04-18 00:30 productinfo
--w--w---- root root 4096 2016-04-18 00:30 readconfig
-rw-r--r-- root root 4096 2016-04-18 00:30 reg_control
--w--w---- root root 4096 2016-04-18 00:30 reset
lrwxrwxrwx root root 2016-04-18 00:30 subsystem -> ../../../../../bus/i2c
-rw-r--r-- root root 4096 2016-04-18 00:30 uevent
--w--w---- root root 4096 2016-04-18 00:30 update_fw
--w--w---- root root 4096 2016-04-18 00:30 writeconfig
--w--w---- root root 4096 2016-04-18 00:30 writelockdown
Between using "update_fw" and "force_update_fw" you can force a firmware rollback.
So if someone who is affected by this bug would like to try and fix it, flash the factory image
for something EARLIER than MHC19J, let's say MMB29V.
Caveats
whenever you flash firmware you can seriously damage your device
this is slightly more dangerous than ROM flashes because if something goes wrong
your touchscreen might stop working, making it hard to interact with your device
firmware can NOT update when your screen is off / device is sleeping
make sure your device isn't suspended/sleeping, ie you can see your home screen
disable or lengthen your screen timeout so the touchscreen doesn't get turned off during the flash process
the "force_update_fw" command WILL take a 1 or 2 minutes
Do NOT interrupt the process or you can have a non-functioning touchscreen
Then you can try in an "adb shell" [need to be rooted]
Code:
su
cd /sys/bus/i2c/drivers/synaptics_rmi4_i2c/2-0020
cat buildid
echo 1 > force_update_fw
cat buildid
dmesg | grep rmi4_i2c > /sdcard/fwlog.txt
Theoretically your buildid before and after the flash should be different. If you check the log file
you can be sure whether the touchscreen firmware was written or not.
Restart your device and see if the touchscreen is back to normal.
If it is back to normal, then be happy and do NOT take any updates MHC19J or newer or you
will get the questionable touchscreen firmware again.
I've attached the mmb29k-mmb29v synaptics_fw.bin [MD5: a35f302acf40e28b4330ce9912c9bf0a]
If you want to use the latest ROM release and don't mind being rooted
FIX your touchscreen as described above
disable any lockscreen/pattern/PIN
manually flash the latest factory image (wiping user partition not necessary, but won't hurt)
*PRIOR* to rebooting, flash TWRP recovery
boot to TWRP recovery
the following steps WILL modify your vendor partition, as long as you are rooted you won't really
see any difference, but if you put stock boot.img back, it will complain about corrupted software
mount /vendor partition r/w
replace /vendor/firmware/synaptics_fw.bin with the attached one
unmount /vendor
flash SuperSU
reboot
reenable lockscreen/pattern/PIN
it is important to do this *PRIOR* to first system/rom boot after flashing the new factory image
or you will be stuck with the new (bad) touchscreen firmware again

In case anyone is curious there have been 3 touchscreen firmware updates since original release. These cannot be rolled back using factory images. Once you install these Android releases, for better or for worse, you get the associated touchscreen firmware.
So for example, once you get the mhc19j (or newer) update, you are stuck with the mhc19j touchscreen firmware even if you flash mda89e factory images to try and get back to stock. Factory Reset will NOT roll back the touchscreen firmware either.
This is the likely reason some people on this thread are experiencing very annoying touchscreen behavior seemingly appearing overnight when your phones picked up the mhc19j update. I am guessing they adjusted the touchscreen firmware to try and compensate for the "noise" from the defective chargers and were too aggressive, ending up causing issues for people who aren't even plugged in and have never had touchscreen issues.
mhc19q did not include any new touchscreen firmware so upgrading to that will have no effect.
If I didn't list a release it just means it is using the same firmware as the most recent listed predecessor.
mda89e
original synaptics touchscreen
mdb08i
updated synaptics touchscreen
updated qualcomm wireless lan
updated DRM
mmb29k
updated synaptics touchscreen
updated fingerprint
updated sensors
updated qualcomm wireless lan
updated qualcomm video
updated modem
mhc19j
updated synaptics touchscreen
updated sensors
updated bluetooth
updated modem
updated DRM
mtc20k
synaptics touchscreen firmware unchanged since mhc19j
other firmware unchanged since mhc19j
nrd90m (as compared to mtc20f)
synaptics touchscreen firmware unchanged since mhc19j
updated adreno
updated qualcomm wireless lan
updated bluetooth
updated fingerprint
updated DRM
n5d91l
synaptics touchscreen firmware unchanged since mhc19j
other firmware unchanged since nrd90m

Ok, this is now confirmed to FIX the issue.
No longer necessary to throw your 5x against the wall, curse Google, and/or schedule an RMA.
http://forum.xda-developers.com/showpost.php?p=66436391&postcount=28
unicorns-fart-rainbows said:
I downloaded the MMB29V image and followed sfhub's instructions to reflash the synaptics_rmi4_i2c firmware . Happy to report that the issue is fixed, screen works well .
Also, I'm not sure if it was mentioned elsewhere in this thread. The unresponsive screen primarily effects the right side. It occurs after 6 seconds of screen inactivity. It took me a while to figure out that swiping from the left to the to the right side restored screen responsiveness. Still super annoying, but way less frustrating than randomly clicking around until it magically works again, or spamming the power button.
Click to expand...
Click to collapse

My Touchscreen is kinda unresponsive compared to my Nexus 6p or Nexus 5.
I flashed the newest factory image right after I received it a few days ago and I'm wondering if the low sensivity could be caused by the touchscreen firmware.

If it is low sensitivy during chagring, that is the fault of the charger generating too much noise.
If it is low sensiting during normal usage, possibly it is the touchscreen firmware, but folks on that have been hit by this problem have very specific symptoms. The right side of their screen becomes unresponsive after around 6 seconds of inactivity. They can get it to respond again by swiping left to right or by cycling the screen using the power button.

My Touchscreen is unresponsive all the time, not just on a specific side or something.

This might help or might not. Your symptoms don't match but there are always variances in the manufacturing of touchscreens. I'd say it is worth a try.
Do you have a screen protector? Sometimes those can change the figures enough to confuse the touchscreen. I noticed my friend was using my phone and it was very hard to tap then I tried it and all the taps went through. That person told me they have problems on lots of phones and can't use screen protectors which I assume means the conductivity of their fingers is different than most people.
Also does it make a difference when the device is plugged in. I don't mean is it necessarily better when plugged in, just is it different, worse or better.

I used a glass protector and had to remove it cause it even lowered the sensivity even more.
So I'm without a protector at the moment.

I am PIE user and this touchscreen problem was making me mad. I just used update-touch-vendor.zip and everything is fine again! Thanks!
Install script said in TWRP "md5 check for dest touchscreen firmware failed" but before that I could not see errors and problem is solved so it seems to work.

makux said:
I am PIE user and this touchscreen problem was making me mad. I just used update-touch-vendor.zip and everything is fine again! Thanks!
Install script said in TWRP "md5 check for dest touchscreen firmware failed" but before that I could not see errors and problem is solved so it seems to work.
Click to expand...
Click to collapse
Glad it fixed your problem.
The install script you used will flash the firmware first, then it will copy the same firmware just flashed into the vendor firmware directory so the "bad" firmware doesn't get reloaded.
It checks the md5 checksum before flashing (and aborts if there is a problem) so your flash went fine (as evidence by your problem being fixed)
When the install goes to copy the firmware to vendor, it also checks the checksum after it copies to /vendor/firmware/synaptics_fw.bin (when the script is running it is slightly different mount point, but that is the directory when your system is booted)
That is the error you are seeing. It could be some permission problem or could be a bad copy. Not sure.
If you want to do some testing in a rooted adb shell
su
cd /vendor/firmware
ls -l synaptics_fw.*
md5sum synaptics_fw.*
You should see a listing for synaptics_fw.bin and synaptics_fw.bak The latter is the backup of your old firmware (prior to copy) in your /vendor/firmware partition.
File size for synaptics_fw.bin should be 96,000
md5sum for synaptics_fw.bin should be f7fbe71fd16807fc4b198e21ea4be6ff
If it isn't post the size and md5sum and I will try and figure out what firmware you have or if the copying got corrupted.
BTW by PIE user are you using some extended desktop where the Android controls slide out when needed? I can see one edge of the screen not being responsive being very annoying for that feature. It is possible the partition / mounts are slightly different for custom ROMs and/or different versions of TWRP (and that could be causing some problem with the copying). I only tested the install script on stock systems running TWRP 3.0.2-0.

TWRP version is the same.
But that not stock ROM or something might be the case.
I use Tesla rom 20160423-2024 + PIE from xposed/gravitybox (left and right side only) and problem was only at the right side. I have also disabled navbar.
After flashing zip I have have had zero problems.
And this is what I see now (no bak file) :
[email protected]:/vendor/firmware # ls -l syna*
-rw-rw-rw- root root 96000 2016-04-29 09:06 synaptics_fw.bin
[email protected]:/vendor/firmware # md5sum syna*
f7fbe71fd16807fc4b198e21ea4be6ff synaptics_fw.bin
[email protected]:/vendor/firmware #
But I also tested writing this with original charger and writing was almost impossible to do because of slowliness and touch problems. I removed the cable and all is ok again.
So definitely firmware is now changed, I do not remember that charger problem has happened before.
Anyway, this way is much better.

makux said:
[email protected]:/vendor/firmware # ls -l syna*
-rw-rw-rw- root root 96000 2016-04-29 09:06 synaptics_fw.bin
[email protected]:/vendor/firmware # md5sum syna*
f7fbe71fd16807fc4b198e21ea4be6ff synaptics_fw.bin
[email protected]:/vendor/firmware #
Click to expand...
Click to collapse
I had a mistake in the file size listed in the previous post, which I corrected. You have the correct file, the correct file size, and the correct md5 in your /vendor/firmware directory. I am not sure why the install script complained about md5 check earlier.
makux said:
But I also tested writing this with original charger and writing was almost impossible to do because of slowliness and touch problems. I removed the cable and all is ok again.
So definitely firmware is now changed, I do not remember that charger problem has happened before.
Click to expand...
Click to collapse
The touch problems with charger is because the early manufacture dates came with a defective charger which produced too much noise. They fixed the problem in newer chargers and they also tried to address the problem by adjusting touchscreen firmware sensitivity. However for *some* touchscreens, the "fix" led to the unresponsive right side of screen.
So previously you would have had probably less touch problems with charger connected, but right side of screen unresponsive after 6 seconds. The older touchscreen firmware (which you just flashed) would give you normal touchscreen, but you would be exposed to full effects of defective noisy charger when charging cable connected.
Since the latter case is much more usable, my suggestion is to use a different charger or get your charger replaced with the fixed one.

Just a question, please: where are the new touchscreen and other components firmware included? Are they inside vendor.img? Thanks!

gpvecchi said:
Just a question, please: where are the new touchscreen and other components firmware included? Are they inside vendor.img? Thanks!
Click to expand...
Click to collapse
the touchscreen firmware is initially located in vendor.img mounted at /vendor but after first boot the touchscreen firmware (if newer than existing) is uploaded into touchscreen private area so even if you replaced vendor.img it won't make a difference unless vendor.img includes newer touchscreen firnware. The private version of touchscreen firnware is what is run, not the one in vendor.img (at least not directly)

hi brother thank you for the great effort recently the device get an update MTC19T
i feel better touch screen response although it is not perfect but it's definitely better
so can you check if we have new touch screen update in this package.
and i feel charging is a little bit slower
r u recommending flash the old vendor or stay in the latest version?

MORADESSA said:
hi brother thank you for the great effort recently the device get an update MTC19T
i feel better touch screen response although it is not perfect but it's definitely better
so can you check if we have new touch screen update in this package.
and i feel charging is a little bit slower
r u recommending flash the old vendor or stay in the latest version?
Click to expand...
Click to collapse
I was traveling so only got a chance to take a quick look but I recall the touchscreen firmware did not change in the latest MTC19T release so it should be the same as the one in MHC19J (and MHC19Q)
If your touchscreen has always been flaky then it might not have to do with the firmware. If it was fine the whole time and suddenly started acting funny after MHC19J/MHC19Q/MTC19T then it is worth your time to try older touchscreen firmware.
Otherwise, you could try, but the chances of resolving your issues are lower.

MORADESSA said:
hi brother thank you for the great effort recently the device get an update MTC19T
i feel better touch screen response although it is not perfect but it's definitely better
so can you check if we have new touch screen update in this package.
Click to expand...
Click to collapse
Sorry I didn't get back to you sooner, but I did confirm what I mentioned in the previous message.
MTC19T synaptics touchscreen firmware has the same MD5 hash as MHC19J (and MHC19Q) so the firmware files are exactly the same.

sfhub said:
Sorry I didn't get back to you sooner, but I did confirm what I mentioned in the previous message.
MTC19T synaptics touchscreen firmware has the same MD5 hash as MHC19J (and MHC19Q) so the firmware files are exactly the same.
Click to expand...
Click to collapse
MTC19V synaptics touchscreen firmware also has the same MD5 hash as MHC19J (and MHC19Q) so if you have this touchscreen issue the newer software release likely won't fix it.

H901 T-Mobile Nougat v30c Full flashable upgrade

H901 T-Mobile Nougat v30c TWRP flashable upgrade.zip [The original v30c KDZ was released on 2017-10-04]
With some assistance and alot of patience from @runningnak3d I've managed to extract and package the H901 v30c KDZ into a flashable zip that will not overwrite the recovery. This is an unmodified factory rom that already comes with gapps. Later I may look at producing a version with some changes although alot of what a user might want can now be done through magisk such as debloating or adding app x to the Rom. Adding xposed adds even more options.
This is for the H901. Make SURE you have an ACTUAL H901, and not one of the half / half H901 / F600 phones.
I personally tested this by upgrading from the v30b nougat released by @runningnak3d. It may or may not work for marshmallow users. If you are on marshmallow you should take a full device backup using a script like these: https://forum.xda-developers.com/showpost.php?p=75155430&postcount=39
That post is for windows users but I posted some linux scripts I used right after that one. If you are on marshmallow and you flash this then try to go back to marshmallow without restoring a full device backup (NOT a TWRP Backup) you are going to be spending alot of time in the "how do I unbrick my phone" thread that's in Q&A. I believe a method has been found but why not just save yourself the hassle and make a backup? 30b users, a full image backup wouldn't hurt you either although you also have the option to flash the 30b update + full nougat zip to put you back at where you were.
When you flash this, all the carrier bloat / LG bloat / crap / garbage, will come back. You will also lose root until you flash the su method of your choice. That is the point of this, you WON'T lose TWRP, so you can still root...
Download v30c_upgrade.zip here: https://www.androidfilehost.com/?fid=673956719939821713
md5sum: b2abb8b3ccd0576c9c47768e26b64a85
On a bright note I've personally tested Magisk v15.3 (the latest version at the time of this post) with this rom and it works fine. Magisk also has many very nice addon modules which add some interesting features.
The official magisk thread is here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A partial list of modules can be found here: https://forum.xda-developers.com/apps/magisk/collection-magisk-modules-v2-t3575758
A full list can be found in "magisk manager" which will be installed if you flash the magisk zip.
I'll throw out a few things that may grab your attention....dolby atmos.....viper4android.....google camera.......the ability to debloat the rom systemlessly...make apps system apps easily..change the dpi...all without actually changing the system partition. Oh yeah..xposed can be installed via magisk and works fine although you will have to disable it and reboot if you want to be able to use android pay or pokemon go as the device fails "safetynet" when xposed is enabled.
Any questions, don't hesitate to ask. (and yes I shamelessly swiped alot of this post from @runningnak3d's full nougat post)
By the way... @kawaii.beans was nice enough to make a magisk compatible boot animation zip..uninstalling the module puts you back to the factory boot animation. It's taken from this thread: https://forum.xda-developers.com/tmobile-lg-v10/themes-apps/theme-feb-8-2016-t3311282
and is available here: https://forum.xda-developers.com/showpost.php?p=75412717&postcount=98
You can easily use this same zip to add custom ringtones, sounds, boot animations etc. Basically ANY file in the system folder can be added or replaced. Uninstalling the module removes all of it. Changes can be made to the build.prop the same way. I highly suggest you install the command line magisk manager you can run while in twrp that will allow you to uninstall modules you've implemented that might be preventing you from booting up.
Pic 1 = software screen showing H90130c software revision.
Pic 2-5 are magisk modules I personally have enabled. You might find them of interest.
Debloating:
The apps below I personally used the debloat feature to "uninstall". The nice thing about doing this through magisk is if they do cause you problems you can easily re-run debloat and add them back since this is all done systemlessly(the actual system partition is never really touched). Choices made will also re-apply through rom upgrades.
(Update 02/14/2018) The most recent version of the magisk debloat module allows the config to be both imported and exported. I've attached a copy of an importable list at the bottom of the post. This file needs to be in /cache/ under the same name to be importable.
Code:
1 - Drive
2 - Google Drive Promotion
3 - DRM Service
4 - Android Easter Egg
5 - Docs
6 - Sheets
7 - Slides
8 - GNSS Air Test
9 - gnsslogcat
10 - LG GNSS 2.1
11 - GnssTest 1.2
12 - HTML Viewer
13 - Hangouts
14 - Hidden Menu
15 - LG Account
16 - LGAirDrive
17 - LG Backup Launcher
18 - LGDrm
19 - FOTA Update
20 - Audio share
21 - LGSmartcardService
22 - Smart cleaning
23 - LGWernickeManager
24 - LatinIME
25 - PacProcessor
26 - Print Spooler
27 - SmartShareProvider
28 - Visual Voicemail
29 - Upsell
30 - Wfd Service
31 - atfwd
32 - ELTest
33 - Facebook
34 - Facebook App Manager
35 - ServiceMenu
36 - TalkBack
37 - com.tmobile.pr.adapt
38 - BackupRestoreConfirmation
39 - LG Health Agent
40 - Cloud
41 - Battery drain info
42 - GCUV
43 - Game battery saver
44 - Market Feedback Agent
45 - IceContacts
46 - InCalAgent
47 - LG AirDrive
48 - Clock
49 - App Updates
50 - LG Mobile Switch
51 - Calendar
52 - Smart Notice
53 - Contacts
54 - LG Keyboard
55 - EasyHome
56 - Email
57 - Exchange
58 - File Manager
59 - FormManager
60 - Answer me
61 - Home(UX 4.0)
62 - LGInstallService
63 - LDB
64 - LGMapUI
65 - Music
66 - Music
67 - LG P2p Service
68 - LG Bridge Service
69 - LGPartnerBookmarksProvider
70 - EULA
71 - About Second screen
72 - SnapPage
73 - Tasks storage
74 - Update Center
75 - Voice care
76 - Voice Command
77 - LG VoiceCommand SpeechPack
78 - Voice Recorder
79 - LG WFDS Services
80 - Mobile HotSpot
81 - LIA Informant
82 - LIA S4URecommender
83 - LG Connectivity Service
84 - Lookout
85 - Mobile Hotspot
86 - My Places Engine
87 - My Place
88 - T-Mobile Name ID
89 - RCSProvider
90 - SmartSetting
91 - T-Mobile
92 - Device Unlock
93 - Tags
94 - Terms of Use for LG apps
95 - LG VPN
96 - T-Mobile TV
97 - Facebook App Installer
98 - qcrilmsgtunnel
Feel free to suggest removal of additional bloatware that you've personally tested.

Reserved

Reserved #2

This one too....

famewolf said:
H901 T-Mobile Nougat v30c TWRP flashable upgrade.zip [The original v30c KDZ was released on 2017-10-04].
Click to expand...
Click to collapse
:good:
Nice job, Kemo sahbee!
Keep up the good work!
Sent from my LG-H901 using XDA Labs

NYLimited said:
:good:
Nice job, Kemo sahbee!
Keep up the good work!
Sent from my LG-H901 using XDA Labs
Click to expand...
Click to collapse
Great job.
At the moment working without failures.
Thank you very much.
Enviado desde mi LG-H901 mediante Tapatalk

Tested 24 hours and everything perfect.
Except Adaway I can not download the host files.
Any solution?

epicuros said:
Tested 24 hours and everything perfect.
Except Adaway I can not download the host files.
Any solution?
Click to expand...
Click to collapse
It's a factory rom with 0 changes. I'm using adaway from f-droid.org with no issues including downloading of host files. Check your settings and see if you have them set to only download on wifi etc.
If you are using magisk for root you do realize you have to enable the systemless hosts option in magisk?

I have a tmo h901 with a vs990 motherboard. In the other nougat thread other people with vs990 boards in their h901 claimed they bricked with the nougat updates. I did update from lp to mm with @Eliminater74's flashable full updates (his actually TWRP flashed all partitions from the kdz except recovery, currently on 20l) before I found out tmo was given hybrid stock from lg. So I wonder if anyone is still around with one of these "factory hybrids" that is willing to be a guinea pig?
Sent from my Moto Z (2) using XDA Labs

skywalker-live said:
I have a tmo h901 with a vs990 motherboard. In the other nougat thread other people with vs990 boards in their h901 claimed they bricked with the nougat updates. I did update from lp to mm with @Eliminater74's flashable full updates (his actually TWRP flashed all partitions from the kdz except recovery, currently on 20l) before I found out tmo was given hybrid stock from lg. So I wonder if anyone is still around with one of these "factory hybrids" that is willing to be a guinea pig?
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
I don't think anyone should risk bricking their phone to be a guinea pig for you. If you make a full device backup and keep twrp you should be able to do a full device restore (all partitions not just the ones twrp does or the ones in the zip because while booted up under nougat it updates more partitions) and be back where you started.

epicuros said:
Tested 24 hours and everything perfect.
Except Adaway I can not download the host files.
Any solution?
Click to expand...
Click to collapse
Firewall? Were you running SuperSU systemless?
Try uninstalling and reinstalling adaway and see what happens...
Sent from my LG-H901 using XDA Labs

NYLimited said:
Firewall? Were you running SuperSU systemless?
Try uninstalling and reinstalling adaway and see what happens...
Sent from my LG-H901 using XDA Labs
Click to expand...
Click to collapse
OKAY. Yes now.
After long desists Adaway and reinstall works properly. :good:
At the moment all ok with the Rom.:bueno:

I can't get Arise Sound Systems to install. It flashes but the Arise system and features do not appear on the phone. SU is flashed on the rom so it is rooted.

alotmoore said:
I can't get Arise Sound Systems to install. It flashes but the Arise system and features do not appear on the phone. SU is flashed on the rom so it is rooted.
Click to expand...
Click to collapse
I know nothing about Arise. If you are using systemless root whether it's magisk or supersu the sound package you flash has to have support for THAT method of systemless root ie if you are using magisk you install the magisk sound modules available inside the app. If I had to guess I'd day if it's not showing up then it's not getting flashed. I stopped using supersu when chainfire sold it to a company that may be nothing but a chinese shell corporation. You might try Arise sound threads. I had no issues with dolby atmos and viper4android in my limited testing of them (via magisk modules).
https://www.reddit.com/r/Android/comments/54xdmp/ccmt_who_exactly_are_the_owners_of_supersu/
Standard disclaimer: Again, it's a factory rom with 0 changes. I extracted the kdz to the individual partition image files then put all those img files minus the recovery one into a zip with instructions to flash to the appropriate partition.

Flashing LG V10 h90a to h901 T-Mobile
Hello friends, I'm new here and I need help with something if possible.
I have a lg v10 h900a att, and I want to know if I can flash my lg v10 to the h901 version of T-Mobile.
preferably with android 7 (nougat)

andrioris19 said:
Hello friends, I'm new here and I need help with something if possible.
I have a lg v10 h900a att, and I want to know if I can flash my lg v10 to the h901 version of T-Mobile.
preferably with android 7 (nougat)
Click to expand...
Click to collapse
The AT&T V10(H900) is a totally different model than the T-mobile V10(H901) and nothing is compatible between them rom wise. You'll have to check in the AT&T v10 section. I would not rush anything because for the t-mobile v10 it's a known fact that nougat has NO root method/twrp unless you can root it while it's on marshmallow or lollipop.

Thanks for doing this. Testing it out right now.

@famewolf, what app do you use in place of Contacts?

prabs99 said:
@famewolf, what app do you use in place of Contacts?
Click to expand...
Click to collapse
I use truecaller for callerid, dialer, contacts and sms however you could always use something like "simple contacts" from f-droid.org (they have a whole line of apps called simple x..simple calendar, simple contacts etc....)
You also always have the option of going into debloat and restoring the app if you are importing my list and want to keep some I removed.
and for others wondering:
I use aacalendar (google play) for my calendar app.
I use the magisk youtube with no ads.

Will try it. Just got it installed. Any word on the battery life? My battery life on v30b was like 5 hours.
famewolf said:
I use truecaller for callerid, dialer, contacts and sms however you could always use something like "simple contacts" from f-droid.org (they have a whole line of apps called simple x..simple calendar, simple contacts etc....)
You also always have the option of going into debloat and restoring the app if you are importing my list and want to keep some I removed.
Click to expand...
Click to collapse

OlympicsReminder service has started!

Hello,
I've just installed Jan 2020 update (~100mb) over stock ROM and upon restarting I noticed the following text flashing briefly on screen:
Code:
OlympicsReminder service has started!
I don't recall having seen this before.
Does anyone has any information about this "OlympicsReminder service"?

I found this site here.
Maybe some new kind of broadcast system used by xiaomi
https://blog.csdn.net/zeng622peng/article/details/6129102
EDIT:
I found this repo
https://github.com/yuanyukun/IIE/bl.../java/com/horem/parachute/main/BootClass.java
----
According to the AndroidManifest File here
https://github.com/yuanyukun/IIE/blob/master/app1/src/main/AndroidManifest.xml
Some services by baido are used.
---
https://github.com/yuanyukun/IIE/tree/master/app1/src/main/java/com/horem/parachute/task
Here PayResult and TaskPayActivity the code look like its somehow about alipay or so
---
Im not pretty good at reading source of android apps. So dont think about my research to be 100% correct

Android 11- OneUI 3.0 (Beta 1,2 & 3) - Manual Update/SideLoad (N986U & N986U1) - [Guide]

********** ANNOUNCEMENT - Beta Enrollment without Banner (OPEN NOW - Nov 16,17) - Read More Here​
INTRODUCTION - Hello all. Now Samsung wants us to go to Members app and keep looking for banner to sign up for Android 11, One UI 3 Beta . It went live October 27th, 10:20 PM EST, As fate would have it, i went to sleep early, i missed it and the banner refused to show up for me in the morning. Download was only showing up for people with unlocked variants on ATID firmware.
DISCLAIMER / NOTICE - Flashing is always risky. I am not responsible for anything that may happen to your device including but not limited to it turning against you, making you its slave and sucking you into the Matrix.
This post is a collection of wisdom, research and hard work of many people over many years across many forums and not just XDA. I will try to credit and link to their original posts.
TIP -Keep in Notice -This SHALL NOT Factory Reset Your Device or Format Data, it is still a good idea to Take Back Up - Just a Suggestion - Always have a latest Back Up
******** UPDATE - It seems ATT devices are getting wiped now if its CSC or the Sim remains to be tested.
i don't have ATT hence cant verify but in case you have an Unlocked device (N986U1) with ATT sim, then, removing sim and Changing the CSC to XAA/XAA/XAA before sideloading Beta is advisable.​
PROBLEM STATEMENT - Missed the One UI 3.0, Android 11, Beta Sign up Banner in Members app or got the banner but didn't get the download and I really want it NOW.
Not sure if you want it now? - Find the BETA CHANGELOG HERE
GRAB YOURSELF A COFFEE / DRINK, because depending on where you at and how fast you/your internet speeds/your Machine is this may take anywhere between 7 to 45 Mins​SOLUTION -
1. Pre-Requisites - Make sure Following Conditions are met before you start
You need a PC/Laptop along with your phone and USB Cable.
You need ADB installed, you can use ADB on Linux too - NOTE If your ADB Tools are not working, download my ADB Folder called platform-tools. Then extract it somewhere easy to remember/ find, like desktop
Remember the Location of the folder where you have ADB installed / Location of platform-tools- This is the location containing adb.exe file.
You may or may not need ADB/USB Drivers if any errors in ADB please Download Drivers from here and Install on your PC.
This following one step is relevant Only for flashing Beta 1
Use Odin to Flash Unlocked (SM-N986U1) ATID Firmware if you are not on that. Refer this thread to get your Firmware.
For changing Firmware from N986U to N986U1 and / or GUIDE TO FLASHING USING ODIN Refer This thread
______________________________________________________________________________________________________________________________________________________________
2. Now Download the relevant Beta File that you intend to flash - note that to Sideload Beta 2 you need to be on Beta 1 first. Mandotory Sequence = Beta 1>>Beta 2>>Beta 3 There is no skipping versions possible here.
BETA 1 (ZTGJ) Get the Beta1.zip file from here Thanks to @thatotherguy.. for the original zip.
BETA 2 (ZTK1) Get the Beta2.zip file from here
BETA 3 (ZTK9) Get the Beta3.zip file from here
______________________________________________________________________________________________________________________________________________________________
*************** Apply Update from SD card failed for me (Feel free to try that ) but here we will be using ADB Sideload Feature in Stock Recovery*************​
HOW TO - Using ADB Sideload - Windows -The Process is Similar for Linux too
1. Copy the downloaded zip file to the ADB Folder (From Pre-Requisite step). ADB Folder is the folder containing ADB.exe it might be named differently for you (The one i have posted is called platform-tools)
2. Open Command Prompt Window as Admin.
3. Type in
Code:
cd Copy-paste the location of your ADB folder here
4. Connect the phone to the PC using USB Cable and Unlock it. Go to Developer Options and Switch on USB Debugging.
To turn on developer options go to Settings>>About Phone>>Software Information>> Then tap the build number 7 times - Developer options will appear at the bottom of Settings Menu
5. On your PC Type in Command Prompt
Code:
adb devices
6. Give Permission that appears on your phone and PC - I check the box Always Allow, you should do the same.
7. Now type the following and the phone will reboot to recovery.
Code:
adb reboot recovery
8. Once you see recovery on your phone Use Volume Keys to scroll down to Apply Update from ADB and press Power Button.
9. Now on your PC, Type the following in Command Prompt; this is just to be sure, it should show the device name with Sideload next to it.
Code:
adb devices
10. Type
Code:
adb sideload Beta1.zip
For Beta 2 use adb sideload beta2.zip Similarly For Beta 3 use adb sideload beta3.zip. Use whatever you have named the zip file. Most people use update.zip. The commands here are for the attached files in this post and their naming convention.
11. Wait for it to finish and Done
2nd (Second) BETA Is Out- How To Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling​
Second Beta should be flashed After Beta 1. Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 1st Beta. Download the 2nd Beta (ZTK1) Zip File to flash Here Thanks to @hayabusa1300cc for the FOTA Link.
3rd (Third) BETA Is Out- Nov 16, 2020 Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling​
Third Beta should be flashed After Beta 1>>Beta 2. Third Beta (ZTK9) can not be flashed unless you have Second Beta (ZTK1). Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 2nd Beta. Download the 3rd Beta (ZTK9) Zip File to flash Here
OPTIONAL THINGS TO DO POST UPDATE ​
If you want to enable RCS (In the Native SMS app) and Native Video calling (This feature is on Tmobile) have a look at this thread.
Check out this Guide Service Mode and CSC Guide/Enable LTE/5G Bands and Services/5G Low Band on U1 by @mellojosh
TROUBLESHOOTING​Some people might run into "cant read update.zip" error for that we need to make ADB Large address aware. Follow the Steps Here I use the Advanced mode as it shows the true false flags. - This wont happen if you use the ADB Tools provided by me above under the Pre-requisites section.
************** FOR FUTURE BETA OTA Questions / Bugs - Observations and some more info - Go Here ********Please dont ask questions without reading.
QUESTIONS, HELP & SUPPORT ?? - See if I am Online here on this Live Chat​
If it helped HIT THAT THANKS BUTTON, what are you waiting for ? Cheers !!

Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)

I get "adb: failed to read command: No error"

ekerbuddyeker said:
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
Click to expand...
Click to collapse
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.

d_ganggreen said:
I get "adb: failed to read command: No error"
Click to expand...
Click to collapse
Use a different USB Cable. A good quality one preferably. Also try changing USB port.

Can i install this on sm n 9860 version and does google pay and samsung pay beta work?

warriorvibhu said:
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Click to expand...
Click to collapse
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.

d_ganggreen said:
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
Click to expand...
Click to collapse
Are you on ATID Firmware?

warriorvibhu said:
Are you on ATID Firmware?
Click to expand...
Click to collapse
I am, I odin flashed it a few weeks ago.

1gorelo said:
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
Click to expand...
Click to collapse
Too early in the morning to go out and test that. This is Beta and i have already encountered some bugs. So you have to be up for that.
Good Lock wont work, gesture navigation is buggy, you can not even apply wallpapers from the Galaxy Themes app.
Wallpaper Service on the other hand is greatly improved. Fingerprint sensor is much faster.

d_ganggreen said:
I am, I odin flashed it a few weeks ago.
Click to expand...
Click to collapse
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.

warriorvibhu said:
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
Click to expand...
Click to collapse
Thank you! Whatever it was, that worked. I am able to get it running with your tools. I am running it now.

CHANGELOG - Android 11_OneUI 3 Beta
************ Notice: This changelog is compiled from various different resources online, verification of these features rests with the users **********
Code:
[COLOR="SeaGreen"][CENTER]BETA CHANGELOG[/CENTER][/COLOR]
[B]Home screen[/B]
– Touch and hold an app to add an associated widget
– Turn the screen off by double-tapping on an empty are of the Home screen. You can turn this on in Settings > Advanced features > Motion and gestures.
Lock screen
– Dynamic Lock screen now has more categories, and you can select more than one.
– Lock screen widgets are improved.
[B]Contacts, Phone and Call Background[/B]
– Added the ability to edit multiple linked contacts at one time.
– Added an option to help you quickly delete duplicate contacts.
– Enhanced the search experience.
– Extended the storage period of the Trash bin from 15 to 30 days.
– Added the ability to customize the call screen with your own pictures and videos.
[B]Messages[/B]
– Created a Trash bin to store recently deleted messages.
– Call & Text on other devices
– Added the ability to turn Call & text on other devices on or off with Bixby Routines.
[B]Calendar[/B]
– Events with the same start time are now shown together in month and agenda view.
– Reorganized options for adding and editing events.
– Improved layout for full screen alerts.
[B]Reminder[/B]
– Improved layout for full screen alerts
[B]Camera[/B]
– Improved auto-focus and auto exposure functionality and usability.
– Improved stabilization when taking pictures of the moon at high zoom levels.
[B]Photo editor[/B]
– Added the ability to revert edited pictures back to their original versions.
[B]Bixby Routine[/B]
– Grouped preset routines help you get started quickly and learn how to build your own routines easily.
– You can now see what actions are reversed when a routine ends.
– New conditions have been added, such as a specific start time, the disconnection of a Bluetooth device or Wi-Fi network, a call from a specific number, and more.
– New actions have been added, including talking to Bixby and accessibility actions.
– You can add a customized icon for each routine and add routines to the Lock screen for quick access.
[B]Digital wellbeing and Parental controls[/B]
– Added trends to your weekly report. You can see how your usage has changed since the previous week and check your usage time for each feature.
– Added phone usage time while driving to the weekly report.
– Added a lock screen widget so you can check your screen time without unlocking your phone.
– Added separate profiles for personal and work modes so you can track your screen time separately.
[B]Internet[/B]
– Added ability to block websites from redirecting you when you tap the Back button.
– Added warnings and blocking options for websites that shot too many pop-ups or notifications.
– Rearranged menus to make things easier to find.
– Added several new add-ons, including one that translates websites.
– Added option hide the status bar for a more immersive browsing experience.
– Increased maximum number of open tabs to 99.
– Added ability to lock and reorder tabs.
– Improved design for tab bar which is now supported on all devices.
– Ended support for Samsung Internet edge panel.
[B]Quick panel[/B]
– See your conversations and media more conveniently in their own sections when you swipe down from the top of the screen.
[B]AOD[/B]
– Always On Display widgets are improved.
[B]Accessibility[/B]
– Get quick access to the most important accessibility settings during device setup.
– Get recommended accessibility features based on what you use.
– Set the Accessibility shortcut more easily in settings.
– Sound detectors now work with your SmartThings devices such as TVs and lights to give you more visible alerts when the doorbell rings or a baby is crying.
[B]Samsung Keyboard[/B]
– You can find the keyboard in settings more easily under General management in Settings, and the settings have been reorganized to put the most important ones first.
Samsung DeX
– You can now connect to supported TVs wirelessly.
– New touchpad multi-gestures let you change screen zoom and font size more easily.
Feel free to add anything else that you observe.

warriorvibhu said:
Wohooo Fingers Crossed. Did it finish ?
Click to expand...
Click to collapse
Yes it did, running 3.0 beta now!

warriorvibhu said:
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
Click to expand...
Click to collapse
I'm on n9860 which is a snapdragon. I'm not sure if it's the same. Anyone want to try?

My US unlocked stuck at 16% when sideloading? Is it normal?

jianansong said:
My US unlocked stuck at 16% when sideloading? Is it normal?
Click to expand...
Click to collapse
Since how long ?
Which step are you at?

warriorvibhu said:
Since how long ?
Which step are you at? (See Pics)
Click to expand...
Click to collapse
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.

jianansong said:
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
Click to expand...
Click to collapse
Yes thats too long Cancel and restart, It took me 97.5 seconds to verify the package.
Your ADB is fine dont change that. For firmware you can try using the second link from google drive. do you meet the criteria Unlocked and on ATID ?

warriorvibhu said:
Yes thats too long. do you meet the criteria Unlocked and on ATID ?
Click to expand...
Click to collapse
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------
jianansong said:
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
Click to expand...
Click to collapse
At the command line, I clicked "control + C" and surprisingly the progress number starts moving again, and now I am at 53% and it's still going...