yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9+ Guides, News, & Discussion] gibbo82:
Any advise for standby drain? Thats where i seem to be suffering! Even greenify doesn’t help!?
[Samsung Galaxy S9+ Guides, News, & Discussion] TechOut:
Are you inside a building during most of the standby time? Or anywhere that would cause a weak signal? I found inside large building or places where cell reception is low causes a lot of battery drain during standby
[Samsung Galaxy S9+ Guides, News, & Discussion] Swordchan:
No just no. Feels like i disabled every app there is. 4 hours sot. Maximum 24 hours total time. Draining 10% minimum during sleep if left unplugged for (7 hours) i put every app in sleep. Cant find samsung ar etc in (always sleeping apps tho) i set everything except for messenger. Snap.waze. bbs and spotify in always sleep. Still not sure it will work. Aod on. Auto brightness on.. maybe i shouldn't complain. But when people get 7 hours sot i feel like i need to complain. I had bad battery time with my s7 aswell.
[Samsung Galaxy S9+ Guides, News, & Discussion] spaladugu:
I understand why you would be skeptical. i will try to get a screenshot the next time i have a chance.

Another thing I did notice is screen brightness is one of the biggest battery killers on the phone. Maybe try power saving mode but only use the -10% brightness option that should help a little bit or manage your brightness manually. Hope that helps
[Samsung Galaxy S9+ Guides, News, & Discussion] kingdave82:
I'm pretty disappointed with the battery life on my S9+ to be honest. Today for example, with minimal usage, after unplugging at about 9:30 am I was down to 35% by noon.

I've recharged it and now left it sitting - it is consuming power at a rate of 1% per 10 minutes, just sitting on the table without me using it. I'm at home, with a strong 4G signal, WiFi router is in the same room, and Bluetooth is disabled.

I moved from an LG G6 to this phone because I was tired of the LG hanging and stumbling to do basic things, but at least the battery lasted a little longer - I could sit it on the table and I'd only lose a couple of percent over the course of a few hours.
[Samsung Galaxy S9+ Guides, News, & Discussion] Bxrider117:
I followed these steps yesterday. I took my phone off the charger about 11pm yesterday. Here is my battery info since that time
[Samsung Galaxy S9+ Guides, News, & Discussion] Robalboa:
Ill tell you one way that brought my battery life to Awesomeness. lol Sounds like nothing But i deleted/Disabled FACEBOOK APP and right now im on

1 DAY 12hrs and 27 mins

WITH 52% battery left

Before I removed facebook it was about 30 hours or so.
[Samsung Galaxy S9+ Guides, News, & Discussion] skivnit:
This is a lot of bs, why would you buy a 900usd device to cripple it?I only disabled AOD AMD Facebook cause I never used those in any previous phone and my battery life is great. I'm always using wqhd+, no powrrsaving etc...
[Samsung Galaxy S9+ Guides, News, & Discussion] blackout720:
the battery of a phone degrades over time. in a year or two you might find yourself needing to save a little battery here and there. My s7 is already feeling like a slug with 2 hours of battery.
[Samsung Galaxy S9+ Guides, News, & Discussion] harshang2007:
I found one major default setting which affects battery like huge. Under developer options, 'Keep mobile data turned on' is ON!!

This makes your mobile data to be on always no Matter you or on WiFi or not
[Samsung Galaxy S9+ Guides, News, & Discussion] zathus:
So your saying it should be on?
[Samsung Galaxy S9+ Guides, News, & Discussion] harshang2007:
That setting should be off by default
[Samsung Galaxy S9+ Guides, News, & Discussion] Robalboa:
Im not sure what settings you have. I am still on the same charge that i was on when i posted here yesterday. im now at 14% 2 Days ,11 hrs, 33 minutes

The only thing i did was disable Facebook, Disable or delete any apps i dont use at all . I dont allow any app to turn on wifi scanning , I turned off Notifications on any app i dont want them (long list to scroll through)

and i dont have any power save nothing. I will confirm you dont want "Keep Mobile data on" in dev options. (toggle it off)

Because.... one quick way to drain your battery is to be in a bad cell location.

If you are in a concrete building (roof too) youll see your battery drain trying to get a PRIORITY 1 cell connection.

a bad cell signal will eat battery like Pac Man. inside of steal roofed structures also will cause the phone to keep looking for a better cell connection and drain away

But im totally happy with the battery life. My S7 edge did the same thing 2 to 3 days normal use.

I thing i always do first when i get a new phone is let the battery drain down to about 10 percent or a little less then Charge it full (NOT Quick Charge)

slowly. I do use a quick charge stand but the first time i slow fill it.

Thats all Ive got. good luck brothers
[Samsung Galaxy S9+ Guides, News, & Discussion] WorldIRC:
Would disabling this disable VoLTE when one is at home on WiFi?
[Samsung Galaxy S9+ Guides, News, & Discussion] lowspeed:
^^^ THIS

Made a huge difference on my phone.
[Samsung Galaxy S9+ Guides, News, & Discussion] WorldIRC:
I was able to confirm VoLTE still works even with the Mobile Data Always On setting disabled when on WiFI @ home. When on the call, the data flows, even when on WiFi, but as soon as I end the call and remain on WiFi, the Tx Pwr drops to nil.
[Samsung Galaxy S9+ Guides, News, & Discussion] bartio1975:
Instead of saying things like normal usage it would be helpful if you post your battery usage including Screen on Time. Because one person's normal usage can be another's light usage on so on. Thanks!
[Tilt, TyTN II, MDA Vario III Themes and Apps] Audio:
I've done my searches (yes more than one, using several key words :D) before I get flamed.

Didn't quite know where to start this thread, but it seems software related, so will post here (plus, this forum looks a bit empty :))

Onto the issue, i'd like to be able to change the scrollbar graphics on the today screen (see picture below), reason being I have a lot of appointments and stuff so it's almost always there, but it contrasts with the slick look of Dutty's WM6.1. I've noticed Confused Stu's "Mobile Vista" ROM (which is pictured below, great work stu :)) has changed the scrollbar graphics, so I'd like to do my own. Any help would be appreciated.

Thanks
[Tilt, TyTN II, MDA Vario III Themes and Apps] MACkjam:
What you see in that image is the TodayAgenda plugin which I also use.

Here is the cab for you.

Enjoy.
[Tilt, TyTN II, MDA Vario III Themes and Apps] Audio:
Thanks MACKjam, looks interesting.

However, I was hoping to be able to create my own graphics for the scrollbar, in flash/PS/whatever. I'd love for it to be as easy as finding some .jpg/.bmp's and modifying them, but I know it won't be that easy :(
[Tilt, TyTN II, MDA Vario III Themes and Apps] Mr. Zach:
i ran across this thread and started using that plugin and i think it's great, my only issue is i still get the default today screen scroll bar, so i have 2 including the one in the today plugin. how do i disable the default scroll bar? i've been searching and diggin through registry and i just don't see that option.
[Tilt, TyTN II, MDA Vario III Themes and Apps] DaveShaw:
Not sure you can, Fix the Height of TodayAgenda in the Layout tab so that I doesn't create scroll bars.

Ta,

Dave
[Tilt, TyTN II, MDA Vario III Themes and Apps] Mr. Zach:
very good thanks. that was driving me nuts.
[Tilt, TyTN II, MDA Vario III Themes and Apps] matmaneyre:
Way to hijack someone elses thread!
[Tilt, TyTN II, MDA Vario III Themes and Apps] Audio:
Yeah thanks for that :mad:

O/J. but back on topic :D
[Tilt, TyTN II, MDA Vario III Themes and Apps] greeek:
Actually - That IS a good plugin!

Thanks! :)
[Samsung Galaxy S9+ Questions & Answers] kenfb1:
Hi,

Quick question:

Getting a S9 Plus either way but:

I'd like to get the Unlocked version with the Exynos 9810 chip.

Will I have any issues with bands etc. on T Mobile????

What exactly won't work with US carriers??

Also model numbers if you have them.

Thanks for any insight,

Ken
[Samsung Galaxy S9+ Questions & Answers] i7vSa7vi7y:
Also looking for this information.
[Samsung Galaxy S9+ Questions & Answers] RossTeagan:
As I saw on other threads there will be no issues for the Unlocked to work with T-Mobile.
[Samsung Galaxy S9+ Questions & Answers] kenfb1:
Ok,

Here's the model number;

S9+G965F

Unlocked with the Exynos CPU.
[Samsung Galaxy S9+ Questions & Answers] RossTeagan:
Isn't the F version the European one?
[Samsung Galaxy S9+ Questions & Answers] kenfb1:
Yes it is. Looking to buy from Clove UK.
[MX Player] Avalon:
Hello,

On the 4th of may 2017 I have already purchased Mx player pro, but now when I visit the Mx player pro page in the app store the price is listed again! I tapped on it in the hope that it would install normally but instead I'm charged 26 PLN (around $5.50). In other words I paid twice!

In my purchase order on google play list it shows "canceled", but the money is still deducted from my bank account. Top top it off if I click on 26.00PLN/Install in Google play it says "error you already own this item" even though it's not installed on any of my devices.

Tl;Dr I paid a second time for this app and I can't even install it anymore and money is already deducted from my bank account.
[MX Player] Thirumalai.K:
Hi,

if it's showing as cancelled, the money will be automatically refunded within the timeline defined by the Google.

Probably it's an issue with Google Services. If your old purchase is still valid, just remove the google account it from the device & add it again after the restart. It won't ask you to purchase again.
[Moto Z Play Guides, News, & Discussion] lanyao1920:
Warning: This is dangerous! Even if you do everything according to the following description, your phone may end up damaged! There are no warranties!!

As we know we could change the single sim z play to dual sim by mod the "persist.radio.multisim.config" in TWRP, like showing below:

https://xdaforums.com/moto-z-play/how-to/guide-to-enable-dualsim-singlesim-t3570601

However it will not be functional after you re-flash the firmware.

So inspired by the moto z dual sim mod thread of [MENTION=962402]benzinerwin[/MENTION]:

https://xdaforums.com/moto-z/how-to/guide-dual-sim-mod-signle-sim-moto-z-t3606528

I fingered out the same way on moto z play:

1, Pull the partition controls the "dualsim: false / true" flag:

adb shell "dd if=/dev/block/mmcblk0p50 of=/tmp/mmcblk0p50.bin"
adb pull /tmp/mmcblk0p50.bin

2, Use a hex editor to change "6661 6C73 6500" to "7472 7565 0000":

3, Write the partition back:

adb push mmcblk0p50_edit.bin /tmp/mmcblk0p50_edit.bin
adb shell "dd if=/tmp/mmcblk0p50_edit.bin of=/dev/block/mmcblk0p50"
adb reboot bootloader

4, Erase the partitions modemst1, modemst2 and cache, reboot again.

fastboot oem hw
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot

After all above steps you can relock the bootloader, go back to stock again, this mod is compatible with future moto OTAs, and it will stay no matter which firmware you have.

Enjoy!
[Moto Z Play Guides, News, & Discussion] valderaC:
Do you need to be root?

---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------

I'm on Android Oreo Soak, do you think it would work?
[Moto Z Play Guides, News, & Discussion] lanyao1920:
No need to root, but you need to unlock the bootloader, use TWRP to dump the partition, modify it, write it back.

Then you can relock the bootloader.

Yes I was on 8.0 soka also, it works.

Basically you're changing something out of the rom.
[Moto Z Play Guides, News, & Discussion] TheGuyNL:
Just did this on my Moto Z Play, works great on Android Oreo!
[Moto Z Play Guides, News, & Discussion] kalevilladiego@gmail.com:
tutorial

I would like to know where I find a guide or video guide to perform the procedure without making mistakes, because I would like to leave my motorola z play dual sim

me gustaría saber donde encuentro una guía o vídeo guía para realizar el procedimiento sin cometer errores, porque me gustaria dejar mi motorola z play dual sim
[Moto Z Play Guides, News, & Discussion] ralphodog:
Anything to back up to make this safe and avoid chance of wiping out IMEI like the other thread?
[Moto Z Play Guides, News, & Discussion] tag68:
What are you talking about? Why do you refer to another thread without linking it? Which wipe imei?

It just works fine. That's my experience. Did the mod, got two sim displayed.
[Moto Z Play Guides, News, & Discussion] derBorg:
Hi, [MENTION=962402]benzinerwin[/MENTION] mentioned to backup the stock recovery partition in order to be able to flash the stock recovery after the modification.

I managed to unlock the bootloader and boot (not flash) into TWRP. However, the recovery partition is not among the partitions TWRP offers for backup.

Can anyone help?
[Moto Z Play Guides, News, & Discussion] ilovemeow:
will it restore everything after flash original firmware?
[Moto Z Play Guides, News, & Discussion] danton47:
Thanks, this worked like a charm!

I didn't flash TWRP, just booted it from ram and then followed the guide

fastboot boot twrp-3.2.2-0-addison.img

Slightly off-topic, but could someone point me to a guide to re-lock the bootloader? I couldn't find anything that wouldn't require re-flashing a ton of images. I'm completely stock on Oreo, with this dual-sim mod being the only modification.
[Moto Z Play Guides, News, & Discussion] tag68:
For relock you need signed images. Procedure is, you say "start relock", then flash all important partitions with images signed by Lenotorola, then say "end relock". If signature is fine, relock will succeed.

This means you need signed images you want to flash for relock. It's a bad idea to downgrade, especially Moto devices which like to hard brick on OTA after downgrade, so you would need signed Oreo files for relock.

The Dual-SIM mod should be fine and compatible with relock, but that is just a guess by me.

Why do you want to relock? Afterwards you won't be able to start twrp and do Nandroid backup or restore, you are aware of this feature loss?
[Moto Z Play Guides, News, & Discussion] danton47:
The only reason to relock would be to make some security-sensitive software like Google Pay happy. I'm using some corporate software which I thought might refuse to work on a device with an unlocked bootloader. Fortunately, this turned out not to be the case, so I'm good for now. Still, this may change with a future upgrade, so I'm a bit undecided. Maybe I should go through the pain of re-flashing/re-locking while signed images are still available for the OS version I'm currently running.

Anyway, thanks a lot for your detailed response, much appreciated!
[Moto Z Play Guides, News, & Discussion] tag68:
You also may use Magisk and Magisk Hide which hides the unlocked state of your phone and usually makes SafetyNet (Pokemon Go, Google Pay etc.) happy. Your phone then is rooted, but if you never give any app the approval to make use of that power, it shouldn't do any harm.
[Moto Z Play Guides, News, & Discussion] derBorg:
Hi, I tried to do the mod the way danton47 did it, which means by only booting twrp instead of flashing it. However, I did not manage to pull the mmcblk0p50.bin file. This is what I did so far:

Starting point:

- the phone runs on Stock-Android 8.0.0, Build number OPNS27.76-12-22-3;

- The Stock recovery was still in place

- the phone was NOT rooted

- the bootloader was locked

What I did then was:

- installation of adb, fastboot and the USB drivers on my computer (I am operating on Windows 7)

- enabling of the "developer options", "USB debugging" and "OEM unlocking" in the stock OS settings of the phone

- unlocking of the bootloader using adb and fastboot and getting the unlock key from the motorola website

-> Having done all this I assume that my adb and fastboot setup is complete and fully functional - otherwise I wouldn't have come so far. Please let me know if I am wrong with that.

- Download of twrp

- copy of the twrp bin file into the same directory in which the adb and fastboot exe files are

- reboot of the phone into bootloader

- boot of twrp from ram

Here the problems started. Initially I tried to use TWRP to backup the (Stock-) recovery partition so that I can then flash twrp, execute the dual-sim modification and then go back to stock-recovery (for the same reason as danton47: the only modification I want ot do to this phone is to enable the dual sim feature).

However, twrp does not offer the recovery partition for backup. I made quite some reasearch for that issue but did not find any solution.

Therefore I was very happy to see that danton47 managed to unlock the dual-sim functionality without flashing twrp. As I understood it this means that the modification can be executed without changing anything else than the affected bin file. So I booted into twrp (same version as danton47 used) again:

fastboot boot twrp-3.2.2-0-addison.img

However,

adb devices

does not show me any device! I also tried to enable the "adb sideleoad" in twrp, hoping that this would allow adb to access the phone while TWRP is running (just tell me if this is completely useless at this point). No success neither.

When activating the adb sideload, I get the options "Wipe Dalvik Cache" and "Wipe Cache". I didn't use these options as I don't know what would be wiped.

Can anyone help me with either

- getting twrp to backup my stock recovery so that I can try again by flashing twrp

or

- enabling adb to access the phone whil twrp is booted from ram?

Thanks in advance!
[Moto Z Play Guides, News, & Discussion] tag68:
For adb you do not start twrp. Just enter fastboot mode.
[Moto Z Play Guides, News, & Discussion] derBorg:
Thanks for the quick response!

However, I don't get ahead with it. What I read so far is that adb is not used in fastboot mode (which is the same as the bootloader, right?), but when android (or eventually twrp) is running. Please correct me if I'm wrong. At least it didn't work when I tried right now. When the phone is in fastboot mode <adb devices> does not show any device, while <fastboot devices> does.

Here the code I entered with the output I got (serial number edited), starting with android booted, the usb connection established and usb debugging enabled:

adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ZY12345678 device

adb reboot bootloader

adb devices
List of devices attached

fastboot devices
ZY12345678 fastboot

adb devices
List of devices attached
[Moto Z Play Guides, News, & Discussion] derBorg:
Allright, I got it done. Now I want to close my issue on this thread and share my experience.

I could solve the problem that adb did not work in TWRP by hints I found in this thread:

https://xdaforums.com/galaxy-nexus/help/adb-twrp-recovery-t1968989

Apparently it was some sort of driver issue (on Windows 7). When the stock Android was booted, the adb driver worked perfectly and in the device manager I got an entry "Android device/Motorola ADB Interface". After rebooting into bootloader and booting (without flashing) into TWRP using the command:

fastboot boot twrp-3.2.2-0-addison.img

The phone did not show up at the same place in the device manager any more. Instead, it appeared as "Andere Geräte/ADB Interface", which translates to something like "Further devices/ADB Interface" (I don't know for sure the exact english wording MS uses at this place). Moreover, "ADB Interface" could not be installed properly. This was the reason, why ADB did not work with TWRP booted.

To solve this issue, I pushed Windows to find a driver for the ADB interface. It also found one but not quite the correct one. It found a driver from Samsung and the phone with TWPR booted appeared as "SAMSUNG Android Phone/Android Composite ADB Interface". With this driver installed and TWRP booted "adb devices" finally found my phone. However, I wasn't really comfortable using a not completely adequate driver for modifying my phone, so I uninstalled the driver again an tried to find the corresponding motorola driver. Unfortunately, the only one I found was the driver I already had installed and which allowed me to run adb on Android, but failed on TWRP. Finally, I let windows install the Samsung driver again and (after making a final backup of my contacts and data) executed the dualsim modification described above, which finally was the easiest part of all.

Thanks again to lanyao1920 and benzinerwin for posting how to do the modification and thanks to danton47 to point out that it is not required to flash TWRP for this purpose!
[Moto Z Play Guides, News, & Discussion] dandrumheller:
I finally got around to doing this mod. Started last night, and was struggling with things not going quite as described. Couldn't get adb push/pull to behave, screwed around with chmod'ing the files, and some other random crap. Was able to get the mmcblk0p50.bin out and hex edited, but every time I tried dd'ing it back to dev/block/ it wouldn't write correctly. mmcblk0p50 was nearly blank when I looked at it in Xplore's hex viewer. Phone seemed to be functioning fine in this condition, however, albeit with only one sim.

It might have been the couple of imperial stouts I was having, but when I woke up this morning I tried again. And everything worked exactly as described with no issues.

What was I doing wrong? I'll tell you - I was trying to do the ADB commands with the device fully running last night, rather than in recovery.

There is a brief mention in post 2 that apparently didn't click with me last night (maybe cause beer?) that you need to be in recovery. I might have caught this a few years ago when I was messing around more, but I haven't done much of this stuff for a while. I'd like to recommend to OP to add a comment in the OP to make sure others are aware all the adb commands must be done from recovery. Or maybe not needed since I'm the only one who seems to have had issues. :)

My experience so far: I am US user, using a carrier unlocked device on August 2018 security patch of RETUS stock software. I'm bootloader unlocked, and rooted. I happen to already have a dual-sim tray for my device sold as single sim - I ordered it a couple years ago for travelling abroad, just to have a non-usable place to stash my US sim safely while I was using a local prepaid one on my trip. I have so far tested only my postpaid ATT sim. It appears to be working for both data and calling in both sim slot 1 and sim slot 2, even though slot 2, as advertised, indicates IMEI of 0. My only testing so far, however, has been on my ATT microcell, so I'm not sure if that makes a difference or not. I was actually not expecting the device to connect to the microcell using slot 2, as all devices have to be manually registered to it using IMEI. I'll post back with any further info, as I've seen very limited info anywhere about what actually works and what doesn't in the US in this type of situation. I expect to be able to test a verizon sim and a freedompop sim shortly.

Big thanks to the OP for finding this solution!
[Moto Z Play Guides, News, & Discussion] tag68:
For me it worked fine on first try, except that Dual SIM is not working as expected:

- If you activate "always use SIM1 for phone" - it still asks which SIM to use when calling someone

- If you click when calling "remember decision for this contact" when clicking SIM1, you STILL get asked which SIM to use on next call

- If you are using Android Auto and making a call, it displays the question which SIM to use on the phone display

I'm using Android 8.0.0 patch dated August 2018. Is there some possibility to correct the behavior?
[Moto Z Play Guides, News, & Discussion] dandrumheller:
It appears that I am seeing the same behaviors so far. Not a huge deal in my use case, but I can see how that would be irritating in many use cases.

Complete wild guess here: firmware from an originally dual sim device might fix this? No idea if this would really work, or present other issues...