yashsingh1/xdaforums huggingface dataset:
[Vivo Nex Questions & Answers] stylobic:
I'm in contact with vivo support on messenger, but after a couple of logs uploaded, they still have no clue of what's happening. I'll wait next update and if no improvement, i'll get a new phone.

Maybe you could help as well with some logs for them to check, search for VIVOGLOBAL on messenger
[Vivo Nex Questions & Answers] Twotems:
I don't use messenger but it's pretty obvious what the problem is. It's right there in the Changelog "reduced system power consumption in the locked standby screen". In this case they've managed to somehow break both wifi and data access for whitelisted apps while the phone is locked. First thing they should do is check the functionality of the whitelist and apps locked in recent.
[Vivo Nex Questions & Answers] stylobic:
I think the reduced consumption was introduced to fix the high consumption from the previous FW.

I noticed too a bettery drain and high temperature of the phone, they fixed it after 1 week if I remember well.
[Vivo Nex Questions & Answers] Twotems:
Yes. The upgrade to Android 10 screwed up battery consumption but they've broken something else with this update.
[Vivo Nex Questions & Answers] DrG0nz0:
Yup, had the same problem...now it doesnt heat up as much but still have the notification problem on WhatsApp and messenger, which is a pain in the ass....

Anyone found any additional config that corrects this?
[Vivo Nex Questions & Answers] Vijay45622:
Hello all, any update from Vivo support on notifications issue? Or any temporary fix to avoid this
[Vivo Nex Questions & Answers] siegie65:
I received an update to version 8.10.5 yesterday. Whatsapp notifications came today without delay during work. Battery consumption was 25% after 10 hours
[Vivo Nex Questions & Answers] chanlokhung:
Where do I get version 8.10.5? I am on PD1805F_EX_A_8.10.1. Cannot receive 8.10.5 OTA update, cannot find the latest rom in vivo support page.
[Vivo Nex Questions & Answers] sumitschirayil:
Even me I am also stuck with PD1805F_EX_A_8.10.1
[Vivo Nex Questions & Answers] siegie65:
Hello i have the Chinese version PD1805_A you have the International i think there is no update this Time
[Vivo Nex Questions & Answers] chanlokhung:
Do you know any workaround or ways for downgrading?

One of the possible workaround is to

download push notification fixer app, set the interval to be one minute, then add notification fixer app to whistlist, autostart, high battery consumption.

By doing that, I am able to at least get some notification within 15 minutes (although not instantly, but better than it was).

I was not aware of update interval. I would appreciate if you could share the experience on when to receive the next update.

---------- Post added at 11:20 PM ---------- Previous post was at 11:13 PM ----------

Thanks for your reply:D It'd be great if you could share how you install Gapps for the Chinese version. I'd go for the Chinese version for faster update and maintenance update.
[Vivo Nex Questions & Answers] vijikali007:
After reset working fine for me....sometime lag is there but can be useable
[Vivo Nex Questions & Answers] chanlokhung:
Thanks for the comment, I would appreciate if you could provide the following before I consider resetting my phone.

Are you on PD1805F_EX_A_8.10.1 and experienced notification before?

Does "sometime lag" means the application not running smoothly or notification lag?

:D
[Vivo Nex Questions & Answers] vijikali007:
Yes I am on same version and lag means yes as you said some time notification will be delayed....not like no notification

And all applications are running very smooth I don't have any issue on that
[Vivo Nex Questions & Answers] Twotems:
I tried Push Notification Fixer and it didn't help much. So I installed Network Keep Alive instead and that seems to help. However it can't be locked in recent apps but seems to still run in the background if whitelisted/autostart etc. There's no real solution to this until Vivo pushes another update to the international version.
[Vivo Nex Questions & Answers] chanlokhung:
After some more day of testing I have figured out Push Notifcation Fixer stopped working after being killed by the battery management. Whitelist does not seems to help. I will try PNF + Network Keep Alive together XD

I couldn't understand "seems to help but no real solution"? Do you mean the application is working or not working?

BTW, the phone was launched in Jun 2018 with 2 year of software support. What do you think on the probability of getting "Vivo pushes another update to the international version"?
[Vivo Nex Questions & Answers] Twotems:
Try Heartbeat Fixer for GCM too even though it does the same thing as PNF. I have all three enabled but Network Keep Alive is best. What I mean is that it still doesn't solve my Google Voice issue but works ok otherwise.

I'm optimistic because they just pushed an update to the Chinese version that solved these issues.
[Vivo Nex Questions & Answers] sumitschirayil:
I got a new update to my vivo NEX, update version: vivo rev 8.11.1

Will be testing it to find whether the notification issue got resolved with this new update.
[Vivo Nex Questions & Answers] chanlokhung:
Looking forward to your results although I haven't receive this OTA udpate. I know some of mates from India has received but they don't have the notification problem prior to the update.
[Vivo Nex Questions & Answers] ScoobyJ:
Same here and didn't fix it. The support stopped replying after got me like 7 messages to make them understand that teaching me how to charge the phone was ridiculous. They asked for some logs and then said that they don't have an ETA for the fix. After that they never replied again to my messages.

I won't buy anything from Vivo again in my whole life. Worst support ever.
[Vivo Nex Questions & Answers] saurabh2310:
It's been months now with this problem. I have finally decided to stop using this phone and gone back to my old device. It's so annoying that Vivo left a flagship phone bite the dust. I was skeptical to invest big bucks and Vivo has proven me right that never again should I trust such brands with a big investment. Though nex can still do all the heavy lifting but I am missing all my work and personal notifications. Definitely can't be used as a daily driver. I am eying the pixel 4a now.

A BIG thumbs down to Vivo from my end.

---------- Post added at 01:03 PM ---------- Previous post was at 12:59 PM ----------

For people who are looking at a temporary fix, this fetches all the pending notifications for me:

Make the data network to refresh, either by turning wifi off and on.

Or by switching airplane mode on and off.

It sucks
[Vivo Nex Questions & Answers] Pussybär:
Update vivo rev 8.12.0:

"Fixed the issue where WhatsApp occasionally cannot receive messages when the screen is off."

It works.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] bjoeg:
I need some troubleshoot tinkering

I have received a Note 10.1 (GT-N8020) from a friend who would appreciate if I could salvage pictures and documents that was on this tablet, and let us not debate his backup options.

Problem with the tablet is it wont boot properly.

It just hangs on the Samsung animation.

As first troubleshoot step my thought was to boot into Recovery and wipe cache and dalvik, just to get it booting. But I simply cannot boot into Recovery. I can only get to ODIN mode.

After several attempts giving up on Recovery, my plan was to flash a new Recovery onto tablet by using ODIN mode, however all attempts both with several different version of ODIN and different version of TWRP fails to be flashed.

<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 6 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

So here I am, feeling stuck.

Either I am thinking there is a defect with the NAND chip, why the tablet must have failed in first place, however I can also find some articles claiming some of Samsung's tablets does not have a Recovery mode/partition, is this true for this model?

I have not reflashed entire tablet, since I need access to whatever data there must be on the tablet.

I also found description on sammobile explaining how to re-install ROM while preserving apps and data, but they keep mentioning ROMs based on 5 files (AP, BL, CP, CSC, HOME_CSC), while I can only find ROMs based on single files (AP)

Link to article (see step 2)

https://www.sammobile.com/samsung/galaxy-note-101/firmware/GT-N8020/CNX/download/N8020XXUDOH1/55623/

Anyone know where I can download such ROM based on 5 files (Samsung official ROM)

Suggestions for any other methods I can try to get the data out of tablet?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] JJEgan:
Try Philz Recovery instead of TWRP .

Not sure if ADB will work for you .
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] bjoeg:
Philz Recovery tried to flash and fails too
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] JJEgan:
Recover data try ADB .
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] bjoeg:
IIRC would that not require USB debugging enabled (which I cannot since it will not boot) and the Android in a running state?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] bjoeg:
Thanks to the SamFirm tool I managed to find some ROMs configured with CSC_HOME. On first shot it failed to flash these ROMs too. But I will try some more tinkering
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] html6405:
I guess your eMMC is locked.

So the only possible solution would be to desolder it and read the data directly out of it.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] j_ds:
Whereas the OP gives a link to an "article" at sammobile, that page has since changed and no longer gives any useful instruction for re-flashing while preserving apps and data. However, I believe that the original "step 2" of that page referred to was : "2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data."
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] JJEgan:
Probably a bit late for the original poster from 2020 .

Could try flashing with No CSC .
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] j_ds:
Sure, there's a good chance that the original tablet has since become e-waste, however, there is also some chance that it's sitting in his friend's drawer in the slim hope of a resolution.

However, my clarification about "step 2" is for the benefit of other readers of this thread, since the OP will already know this information.

My own GT-N8020 tablet has the exact same problem. I was able to overcome the flashing difficulty by using the Prince Comsy patched version of Odin 3.12.3 (which disregards spurious USB communications errors that tend to occur).

However, re-flashing without the CSC portion of the firmware doesn't resolve the problem. I can't include the CSC portion as this will clear the data that I need to recover, and I haven't yet been able to find a HOME_CSC alternative.

Joe.
[Touch Diamond, MDA Compact IV General] mondilv:
Hello!

Anybody know why the wifi rate is about only 500 kbis/s?

Test made by Pocket speed test. (http://xdaforums.com/showthread.php?t=395165)

With/without AC power.

Phone radio - disabled/enabled.

All Power mode presets has tested.

Momentary speed rate not stable: 100-800 kbit/s

Notebook at the same point use 30-40 Mbit/s...

Is it only my problem or global?
[Moto G7 Play Guides, News, & Discussion] 00p513:
Edit 25/10/2020: OK its been a while guys, if you want to try a ROM I'd highly recommend following LineageOS's wiki for instructions. Then if u want to try other ROMs keep an eye out in these forums, ill have a build up every now and then. See ya around guys :)

==========================================================================================

Rather than having random comments in random parts of the forum here is a thread for everything 64 bit on G7 Play.

CURRENT STATUS

WE DID IT!!!! CHECK SyberHexen's ANDROIDFILEHOST FOR DOWNLOAD!

OLD POST ARCHIVED BELOW

And here is what is available so far:

A nice selection of ROMs for the other G7's, but they dont actually boot on the Play, although should do something in theory

postmarketOS is aarch64, but that is mobile linux, and no phone interface works (x.org doesnt work with the current drivers)

Here is what I've tried:

crDroid from ocean:

I got it to install by: repartitioning device using ocean gpt.bin

Then flashing stock rom from channel

Booting TWRP

Flashing ROM, with modified zip accepting channel

Doesnt boot

Also tried a flash using ocean firmware completely, doesn't boot, but got the logos and bootloader works lol

If anyone has any tips or progress drop it here, eta kids go away. Read the status above if you want the up-to-date answer
[Moto G7 Play Guides, News, & Discussion] mrsurge:
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everythi

---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------

You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everything else will work fine. I'm working on getting a new dev environment set up I'll give it a shot... This phone is reeeeealy under developed. Proly cause the g6 play is a way better phone and much cheaper to boot
[Moto G7 Play Guides, News, & Discussion] kD:
We have a 64-bit kernel and 64-bit Lineage OS testing builds but porting 64-bit vendor partition for it to flash in g7 play hasn't been achieved yet.
[Moto G7 Play Guides, News, & Discussion] mrsurge:
I think maybe you can just pick out driver binaries from 64 bit /vendor and use all the configs scripts and frameworks from the original vendor

Try backing up/vendor pieceing the drivers from another device of the same model but diff carrier and a combo as such would work. If not mistaken the. Vendor from the Verizon g6 play worked for sprint except data and wifi or radio in general didn't work.. that's a start right there

I think the modem is going to be the same architecture no matter what so you wouldn't have to worry to much about that
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
64bit Test

Okay so this sh*t probably totally won't boot up at all, but if someone is feeling brave, you can test this out.

1. From your active slot, with root access, you'll need to dd these images to the correct partitions. It's easiest to do this from the internal sdcard using termux. Use the following as a template. These commands assume you're installing it to slot b.

su
dd if=/sdcard/boot64.img of=/dev/block/by-name/boot_b
dd if=/sdcard/dtbo64.img of=/dev/block/by-name/dtbo_b
dd if=/sdcard/vendor64.img of=/dev/block/by-name/vendor_b
dd if=/sdcard/oem64.img of=/dev/block/by-name/oem_b

2. Reboot into fastboot, swap active slots, and wipe userdata + DDR. Then flash an arm64 AB GSI. I'd recommend trying Phh's AOSP Vanilla to maximize the chances of success.

To swap slots and wipe user data...

fastboot --set-active=_b
fastboot erase userdata
fastboot erase DDR

3. Reboot system, and tell me what happens.

**Do NOT attempt to use TWRP with this. You'll probably have to reflash stock firmware to the slot you tampered with to get everything back to normal afterwards.**

Link: 64bit Folder

This is not source built, and it's very much a hack job, so I'm really not expecting anything to work. I did get Ubuntu installed this morning, so I will attempt to build from source in the near future.
[Moto G7 Play Guides, News, & Discussion] 00p513:
Please don't use this if you don't know what a "brick" is or how to recover from one
[Moto G7 Play Guides, News, & Discussion] 00p513:
PS: it probably wont work cause vendor is twice the size xD
[Moto G7 Play Guides, News, & Discussion] PoochyX:
The G7 play is coming so far little by little it was like yesterday we never thought we would have twrp and magisk and now in fact we do on a GSI

([emoji88]Havoc GSI[emoji88])
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
You are correct. She's way too hefty. It's ~164mb too large. I tried resizing last night, but I can only shrink it to 433mb. I can probably remove the modem files and replace them with the ones from stock. I think it's where most of the extra weight is from. The 64bit libs are about 1.5x bigger, but I don't think that accounts for all of it. The Muppets have a tree for sdm632, so all I need to do is look at it, and delete everything in vendor that's not in there. It should help but I'm not sure if it'll be enough. I could repartition it, but I'm not a fan of resizing partitions because I'm very fearful of bricks.
[Moto G7 Play Guides, News, & Discussion] 00p513:
I can get a bit more space with an ocean gpt.bin btw. i suppose we could see how those files work i guess and make a bigger vendor?
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
Have you flashed the gpt.bin from ocean before? If so I'll definitely try using that with the slightly smaller vendor I made. I'm thinking most things from Ocean should work natively. The only difference is screen size by a few pixels, ram, and battery capacity. Otherwise they're essentially the same.
[Moto G7 Play Guides, News, & Discussion] 00p513:
yeah i use channel firmware extracted, then i use motoflash2sh to generate a bashscript from the flashfile. I then replace gpt .bin and remove it from the md5 checks at the beginning of the script. run the script and im repartitioned!
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
That's awesome! I'll try working with this.
[Moto G7 Play Guides, News, & Discussion] 00p513:
ill send a repartition kit later. just unzip and run the script
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
I already found it. So I'd just remove 61863ba7dac0c512d610ffa6406a50f8 and it'll flash correct?

md5sum --check <<EOF || exit 1
[B]61863ba7dac0c512d610ffa6406a50f8[/B] *gpt.bin
[Moto G7 Play Guides, News, & Discussion] 00p513:
that whole line needs deleting. That is just to stop it failing on md5 verification ,as it is a dfiferent file
[Moto G7 Play Guides, News, & Discussion] 00p513:
Did it work? Any update on the vendor image?
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
I haven't tried it yet. I got side tracked compiling twrp. I'm 3 errors away from success. Something about unknown compiler flags.
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
As an FYI, I'm out of a computer for the next several months, possibly up to a year. I'm going through a nasty divorce at the moment, and that's all I'm going to say about that. I'll get back into the game as soon as I can, but for now, you should not expect me to put out anything new for quite awhile. I can and will help people as much as possible during this time. But my ability to do so is going to be hindered without an PC.
[Moto G7 Play Guides, News, & Discussion] malac0da:
I'm sorry to hear that. My divorce lasts since two years.

However, that's not why I registered. I received a Moto G7 Play for app security testing just a few days ago and found this forum when trying to install GSI to the phone. Everything works fine, but I'm interested to upgrade the OS to 64bit. Therefore, I'd like to try out the work already present in this thread. Unfortunately, I have neither found the repartition kit nor gained enough information about gpt.bin file format yet in order to repartition the flash memory of the G7 Play.

I'd really appreciate if anybody could either post or send me the repartition kit or supply information about the partition table format, because I failed to google for that kind of information.

[edit] Ok, I found out how to change partition size to the size of ocean. I flashed the following images:

* Partition table from ocean

* Everything else except system_a from channel

* system_a from phh (binder64)

Everything worked just fine.

Then I proceeded to flash the files posted in this thread earlier. The vendor64.img fits into the new partition layout just fine. After flashing all 4 files, I proceeded to flash phh 64bit version. Then I rebooted, but the boot failed:

First, the device showed up some very long hexadecimal number (maybe some UUID?) on a black screen, where it had shown "bad key" before when everything went right.

Afterwards, it ran into fastboot:

So, I'm back on binder64 again.

Please, could you provide any help for fixing the images, or at least the information how you have built the 64bit images?
[Moto G7 Play Guides, News, & Discussion] 00p513:
Use SyberHexen's TWRP and Lineage from AFH in OP
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
This is epic. Is the repartition script also in SyberHexen's AFH files?
[Moto G7 Play Guides, News, & Discussion] transgirlphoebe:
Can someone run me through what needs done here? I assume boot twrp and flash rom and good2go at that point but id rather not brick this thing

UPDATE: flashed latest LineageOS from AFH,boots fine moto gestures good VoLTE good,fingerprint also works! anything else i might be missing?
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
So I'm guessing you didn't need to repartition? Sounds like the zip did it during the flashing process. It'd be nice to confirm that though.
[Moto G7 Play Guides, News, & Discussion] 00p513:
aha it fits in stock layout. ill upload the script later to my website
[Moto G7 Play Guides, News, & Discussion] transgirlphoebe:
Yeah i was running AOSP with MicroG with it being stock aside for the gsi. Stock partition layout works fine,though OpenGapps seems to have gplay services stopping when it setup wizard. Is adb enabled on first boot to potentially grab a logcat?

Stock 10 firm was what was used
[Moto G7 Play Guides, News, & Discussion] malac0da:
Thank you!

Unfortunately, I ran into a hard brick when I tried to install that. I'm fighting with qboot now. It says, it cannot open singleimage. However, I guess that's OT here.

[edit] Reverse engineering of qboot saved me. :D

[edit2] Performing the installation procedure on stock a9 (EU) bricks the device reproducible. when the installation finished, the device directly booted into Qualcomm QDL mode. I guess, it's either the a9 or the EU device. Okay, I'll try stock a10 next.

[edit3] same result with a10. maybe the RETEU version is not supported yet? I installed the latest build lineage-17.1-20200818-UNOFFICIAL-channel.zip
[Moto G7 Play Guides, News, & Discussion] 00p513:
how did you get out? just briicked mine and qboot gives me weird errors
[Moto G7 Play Guides, News, & Discussion] malac0da:
I used qboot with Linux, it didn't work with Windows for me. I didn't run the blank-flash.sh, but I executed this command (as root):

./qboot blank-flash singleimage.bin --debug 2

However, this didn't work every time. Whenever qboot failed, I had to restart the device into recovery mode (i.e. push power and vol- for 30 sec). The device stays in recovery mode if qboot fails, but it seemed that it went into some state where the communication with qboot isn't working anymore.

It took 2-3 tries with the command above until qboot worked.

Reversing qboot revealed to me that in some cases it failed to use singleimage.bin if this file is not explicitly provided. The other things were trial and error.
[Moto G7 Play Guides, News, & Discussion] 00p513:
is there an arm build for linux anywhere?
[Moto G7 Play Guides, News, & Discussion] malac0da:
I don't know. You may boot an x86/x64 Linux from an USB stick if you don't have Linux installed on your PC.
[Moto G7 Play Guides, News, & Discussion] 00p513:
i dont have a pc xD

i am writing this on a pi atm, and i could borrow by my dads pc for windows