yashsingh1/xdaforums huggingface dataset:
[Mi 3 Q&A, Help & Troubleshooting] solazz:
Tried the ones from this thread?

http://xdaforums.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927/page5
[OnePlus 3 Questions & Answers] YourTheBest:
Hi,

What is the best automation app? Like automate? But more stable/fast?

Thanks
[OnePlus 3 Questions & Answers] Arstoien:
I have never had problems with Tasker. Plus, as far as I'm familiar with the alternatives, nothing gives you what Tasker offers in terms of features and flexibility.
[OnePlus 3 Questions & Answers] thebobmannh:
Yeah I always try out the alternatives and am sometimes excited about them, but always come back to Tasker.
[OnePlus 3 Questions & Answers] nikhil.agrawal:
Macdroid is another great app.
[Moto G4 Play Questions & Answers] bobbyphoenix:
Has anyone noticed when you launch an app, and the speaker starts, it makes a little click sound? Is this normal? Is it just the speaker turning on? I'm a bit paranoid now since I first thought the speaker was bad, but then compared it to my G3, and now really like it better, but I do notice the ever so slight "click/pop" right before sound starts to come through the speaker. It even kind of does it when the sound stops, and the speaker turns off, but it's much less turning off than when it starts.
[Moto G4 Play Questions & Answers] bobbyphoenix:
Nobody who viewed this thread has a G4 Play that can say yes or no? Can someone please check their phone before I return mine as defective. Just listen close to the speaker, and open an app that plays sound (IE: games), or open YouTube, and start a video. Does the speaker make a slight click sound right before any other sound? Like the speaker is turning on before playing the sound/music/audio? I would hate to return the phone, get a new one, and find out the new one does the same thing as it is normal for all G4 Play phones.
[Moto G4 Play Questions & Answers] bobbyphoenix:
Thanks to all who help test their own for me. Great community this is.
[Moto G4 Play Questions & Answers] PavelBronco:
Yes, mine does a faint click as well.
[Moto G4 Play Questions & Answers] bobbyphoenix:
Thanks for your input. Yeah, it's not really noticeable unless it's really quiet, or the phone is up close to my face. I have kind of bad OCD, and when I first heard it, it bothered me, but now I don't really notice at all. I guess it's just the way the speaker works.
[Moto G4 Play Questions & Answers] facuarmo:
It's normal, it needs to wake up the driver so it probably catches some noise from one of the electronic components related.
[Moto G4 Play Questions & Answers] mkollersms:
Said click can also be heard on Bluetooth. If I have my Moto Surround connected and no music playing, I'll hear a hiss every so often while browsing Twitter. Probably a software-side effect (like the aforementioned driver suspicion).
[Moto G4 Play Questions & Answers] cy56:
Nope.
[Galaxy Note 3 Q&A, Help & Troubleshooting] itscarollee:
My Note 4 has an "active apps" icon - can I get that feature for my Note 3?
[Galaxy Note 3 Q&A, Help & Troubleshooting] James_Watson:
But Note 3 does also have the "active apps" widget.

Do you mean that you want to change the icon of that widget for your Note 3?
[General Topics] refi64:
A few days ago, I flashed a zip onto my phone that set SELinux to permissive. However, there was a problem: it deleted logd, which is essential to adb logcat. Considering I'm an Android developer, that isn't a good thing! It took me a bit to figure out how to get it back, so I'm making this guide to share with you guys to help whatever poor soul has to fix this next.

Note that these steps were designed with Linux in mind, though they might be adaptable to Cygwin/OSX with some effort.

Also, make sure you delete any SELinux permissive scripts from init.d/su.d first!

Prerequisites

The OTA or custom rom zip that your device is currently running

adb

simg2img (available in the Ubuntu software repositories)

sdat2img (available here)

Instructions

Put your OTA/custom ROM zip file in a new folder and unzip it (this example is using the Pure Nexus ZIP):

mkdir restore_logd
cp pure_nexus_hammerhead-7.0-20161025-HOMEMADE.zip restore_logd
cd restore_logd
unzip pure_nexus_hammerhead-7.0-20161025-HOMEMADE.zip

Now, look for a file named either system.new.dat or system.img.

If you have system.img, then run:

simg2img system.img system.raw.img

If you have system.new.dat AND system.transfer.list, instead run:

sdat2img.py system.transfer.list system.new.dat system.raw.img

Either way, you should now have a file named system.raw.img. Next, mount it:

mkdir system_mnt
sudo mount -t ext4 -o loop system.raw.img system_mnt

This will mount the system image onto the system_mnt folder.

Plug in your device to your computer and make sure USB debugging is enabled, then run:

adb push system_mnt/bin/logd /sdcard/logd
adb shell

You should now be in a shell connected to your device. Inside, run:

su
mount -o rw,remount /system
cp /sdcard/logd /system/bin/logd
chmod 755 /system/bin/logd
exit

This will install the logd binary and close the shell.

This next part is very important! Making sure you closed the adb shell and are still inside the directory you created, run:

ls -Z system_mnt/bin/logd

If the output looks like this:

? system_mnt/bin/logd

then you have nothing else to do. Otherwise, it might look a bit like this:

u:object_r:logd_exec:s0 system_mnt/bin/logd

Copy part before the path; in this case, it's:

u:object_r:logd_exec:s0

Then, run:

adb shell su root chcon permission /system/bin/logd

replacing permission with the string you copied.

Now you can unplug and restart your device; logd should now be fully working!

Last but not least, run:

sudo fusermount -u system_mnt

to unmount the system image from your computer.

Enjoy! :o
[General Topics] seasonyuu:
Execute command failed while replacing permission

adb shell su root chcon permission /system/bin/logd
u:object_r:logd_exec:s0
/system/bin/sh: <stdin>[1]: u:object_r:logd_exec:s0: not found
[Blu Vivo 5] krodiak:
I see there are some people wondering how to get the marshmallow update from lollipop

I was on stock lollipop rooted and running xposed, everything was perfect, in order to get marshmallow update and root it I did this

Flashed stock rom using the repair rom found here in xda using sp flash tool www.sw-condor.com/smartphones/A55 slim.html

Once in stock, I updated OTA to marshmallow

Once in marshmallow I flashed only the recovery using the same scatter file from the repair rom and the custom twrp for blu vivo 5

Immediately after flashing twrp, booted recovery (power + vol+, once it vibrates al blu logo appears, release power)

Flashed (latest SuperSu)

Enjoy :)
[Blu Vivo 5] krodiak:
Screenshots

Screenshots attached.
[Blu Vivo 5] MikeRogers:
Thank you for this.

I have already updated to marshmallow but need to root it. The repair rom link isn't working, I need the scatter file to flash recovery. Got another link?

UPDATE - found an mt6573 scatter file, so that's not an issue, but I can not get SP Tools to flash, it basically sits there and does nothing, then I get an error "can not pass bootrom start command". Any chance of a detailed tutorial with pictures or video?

Thanks,
[Blu Vivo 5] mopo01:
Make sure you have the USB (?) Drivers
[Blu Vivo 5] krodiak:
USB Drivers

There's 2 possibilities:

The easy one:

If you have the proper drivers, power off the device, wait 10 seconds or so. Then click download in the sp flash tool and then connect the phone, the tricky part is that YOU NEED TO PUSH VOL+ OR VOL- in order to sp flash tool to recognize the phone and start flashing

The not so easy:

You don't have the proper drivers:

I had to install manually a driver, device manager->Select the first item (the name of your computer)-> Action -> Add legacy hardware

You need to download the drivers and then tell the device manager to look for drivers in the specific folder where you downloaded them, then it will find a device, I don't remember its name, follow this guide

Don't forget to hit thanks if I helped :) :highfive:
[Blu Vivo 5] MikeRogers:
Ok, got this working finally. As for the initial issue with SP flash not working, I'm not sure what it was. I have the drivers and everything, but I rebooted the computer/phone (then turned it off) and then it started working. I did also press the volume button when it was off, that may have helped as I didn't know to do that before.

Next, the scatter file I found on the internet somewhere else wasn't correct. I found the correct link to the recovery ROM (you may want to update it in your initial post): http://www.mediafire.com/download/p29wpz59wg9ob2b/BLU_V0050UU_V09_REPAIR.zip

Other than that your guide worked perfectly, thank you.
[Blu Vivo 5] krodiak:
Updated OP

Thanks, I updated the OP, it seems the I copied the shortened text instead of the full link, thanks for noticing that.
[Blu Vivo 5] krodiak:
xposed

Battery life is great on mine, I installed xposed and amplify to block some wakelocks, but even before that, I had a very decent battery life, I read somewhere that you need to let your phone to completeley discharge, not even having enough juice to try to boot when the power button is pressed.

Once is completely dead, charge your phone (keeping the phone off) until it is fully charged.
[Blu Vivo 5] Mechalikh:
give credit to Syed Ahmed Ali Shah for recovery please ...
[Blu Vivo 5] marko717:
I have android 6.0 official and i want root my blu vivo 5. Here root 5.1... How to root in 6.0.1?
[Blu Vivo 5] MikeRogers:
The OP explains exactly how to do this.
[Blu Vivo 5] marko717:
The instructions are same that original post? I have 6.0.1 now.
[Blu Vivo 5] MikeRogers:
You could probably try just doing steps 3 through 5. I'm no expert but I think it might work.
[Blu Vivo 5] marko717:
Im begginer and i wont to do a mistake. I want to know if this work with 6.0.1 or if this is pass 5.1 to 6.0.1
[Blu Vivo 5] MikeRogers:
The OP is for rooting Marshmallow so I would imagine it would be fine with 6.0.1 as that's still Marshmallow. You would only be flashing recovery (TWRP) if you don't have it already and then using that to flash SuperSU. Nothing very dangerous. Give it a try and let us know.
[Blu Vivo 5] marko717:
I think this is for lollypop and have an upgrade to marshmallow. It is not for root 6.0 directly. I would not want to use this .. kingoroot .. kingroot .. 360 .. none worked for me. I only have this method and never did a flash, recovery or a twrp
[Blu Vivo 5] MikeRogers:
Nope, read the OP. It's clearly flashing TWRP and SuperSU "AFTER" doing an OTA update to Marshmallow. I have personally done this to my Blu Vivo 5 running the initial Marshmallow update and it works fine.
[Blu Vivo 5] marko717:
I will do all steps then
[Blu Vivo 5] MikeRogers:
You will not need to do step 1 or step 2 since you already have Marshmallow.
[Blu Vivo 5] marko717:
Can you explain steps 3, 4 and 5? I do not understand. I do not understand what pc program to use or what to do
[Blu Vivo 5] marko717:
Somebody can explain me?
[Blu Vivo 5] krodiak:
we were all noobs at some point

Hello, I just read your posts, with all due respect, this is a helping community but you have to put some effort and do some research and kinda be self taught...

Were you able to fix your phone?

The OP is pretty much self explanatory, it has all the links and stuff you need to do what you want, I was not able to upgrade to marshmallow OTA because I had a rooted device, so what I did was to reflash it to lollipop, then update OTA to marshmallow and then root and install TWRP using marshmallow again.
[Blu Vivo 5] krodiak:
Read carefully
[Blu Vivo 5] Adi rahman:
I can't use the gguardian apl, it's always show permit to root first, but but my phone doesn't support to root, so how can i use gguardian apl? Thx
[Blu Vivo 5] zulkifli 02:
Gguarrdian whag
[Blu Vivo 5] zulkifli 02:
Root Android vivo1603

---------- Post added at 03:45 AM ---------- Previous post was at 03:32 AM ----------
[Blu Vivo 5] Pollem:
Root android vivio 1601
[Blu Vivo 5] ary setyawan:
How to root vivo v5s(1612)OS 7.0???
[Blu Vivo 5] Letrix:
Search on YouTube
[Blu Vivo 5] Deni187:
How to root Vivo y55 ??
[Blu Vivo 5] year hjesgjj:
How to root vivo y55l
[Blu Vivo 5] Arpan Kumar Halder:
How root vivo v5 plus plz
[Blu Vivo 5] Charlenecruz:
How to root plss the vivo v5 lite..
[Blu Vivo 5] juddvillanueva:
how to root vivo v5
[Blu Vivo 5] Letrix:
Google Is your friend
[Blu Vivo 5] nondm:
How to root vivoy53
[Blu Vivo 5] dayanggsexcy:
How to root vivo v5
[Blu Vivo 5] IHK Shawon:
thnx man worked like a charm

very very thnx mate u saved my life
[Sony Smartwatch 3] markgranto:
Cant for the life of me get google music to work on the SW3 (paired with a S7 Edge running stock marshmallow). Anyone had similar?

Downloaded 2 playlists to my phones internal memory as instructed online, one of my own uploaded music to the service, and one of music i hadnt uploaded (signed up for a google music trial to see if that was the reason).

Phone and watch are connected in the actual wear app fine etc. Set up properly in the google music app settings and can see the playlists both there ready to go to the watch from the 'manage wear downloads' section and my watch shows, opened up the app on the watch and then 'play on wear', eventually after maybe 15 seconds it shows all my available playlists and the 2 playlists id downloaded onto the phone are in orange, but nothing happens after that. No sync. Even though i set it to sync when it asked me when first opened the app on the watch. I can select and deselect playlists and an orange tick card pops up at the bottom of the screen, when i click that it just goes back to the watch main face. Left it to see if it starts but nothing.

Tried factory resetting the watch, uninstalling updates for play music on phone, updating again, clearing cache of the app, even clearing the cache on the phone, watch fully charged or on charge, same with phone, also tried 2 bluetooth headsets to see if it wasnt picking that up right.

Anyone think of anything ive missed (apart from factory resetting the phone)? cheers.
[Sony Smartwatch 3] mattnmag:
I'm not sure if this will help, but you might try unpairing the watch from the phone and then go into the Google Play Services settings and wipe the Wearable Storage data. Then factory reset the watch and wipe the data on the Android Wear companion app... reboot the phone and watch... and then pair the watch with the phone again.

That should give you a fresh start and hopefully help to get things synced up.
[Sony Smartwatch 3] markgranto:
Will give that a bash now, cheers
[Sony Smartwatch 3] markgranto:
unpaired the watch, went into play services and wiped the wear storage. Factory reset the watch and cleared the data in the wear app and uninstalled it. Rebooted both and set it all up again from scratch. Opened the app on the watch and turned on music sync. Initially said i needed to plug in power which i did, and then it showed the playlists, clicked on the ones i had been testing with and then the orange tick and it goes back to the watch face as before. Checked the settings in the play music app and all looks as it should. Still wont sync. :silly:
[Sony Smartwatch 3] markgranto:
Unpaired with S7 Edge, factory reset and setup with my LG G Pad, worked a treat, music sync'd without any issue.

Unpaired, reset etc and set back up fresh with the S7 Edge. Same issues. Arghhhhh!!!

Wonder if its something permissions related on the S7 thats doing it not allowing the transfer of files to the watch. Saying that tested with wear media app and that sync'd across music files fine. Anyone any ideas?
[Sony Smartwatch 3] markgranto:
Managed to get this sorted.

Was reading through this

https://productforums.google.com/forum/m/#!msg/android-wear/DGr1WPiy9Po/Sv6ThhXmDAAJ

And saw a comment about taking out the sd card, so did so and it worked immediately even though play music was saving to the internal storage. Very weird. But glad it's sorted.
[Sony Smartwatch 3] mattnmag:
Glad to hear that you got it fixed. I'm sure this will help someone else.
[Sony Smartwatch 3] markgranto:
There was music files on the sd card but not relating to Google play music, must have been trying to scan this possibly. Who knows. Anyway, yeah hopefully someone finds it useful.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.

New features in this update that I've noticed:

-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!

-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)

-The command center widget has been replaced with the Droid Turbo 2 version

Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho

Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8

Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:

OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ

OPTION 2: Flash this patch made by [MENTION=5747496]bhb27[/MENTION]: https://www.androidfilehost.com/?fid=745425885120696423

Wipe cache and dalvik/art cache after either of these options.

NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.

If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.

If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/

If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.
[Verizon Motorola Droid Turbo Android Development] s5610:
Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))

+ mirror
[Verizon Motorola Droid Turbo Android Development] ---UFO---:
I can confirm that it works on old bootloader.

I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.

PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?
[Verizon Motorola Droid Turbo Android Development] rickyblaze13:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
[Verizon Motorola Droid Turbo Android Development] Jacked Burton:
Thanks OP
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
When in doubt, always wipe.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
[Verizon Motorola Droid Turbo Android Development] s5610:
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )
[Verizon Motorola Droid Turbo Android Development] rickyblaze13:
It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
[Verizon Motorola Droid Turbo Android Development] Crowick:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.
[Verizon Motorola Droid Turbo Android Development] Crowick:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?

---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------

Google Drive link to the TWRP Flashable version in your OP hosted on Mega.

https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
[Verizon Motorola Droid Turbo Android Development] 3Dota:
thanks for gdrive mirror
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.
[Verizon Motorola Droid Turbo Android Development] s5610:
fastboot boot TWRP.img
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Nice! Good call.

https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
[Verizon Motorola Droid Turbo Android Development] The_Nothingman:
Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?
[Verizon Motorola Droid Turbo Android Development] rickyblaze13:
Just the first boot after flashing
[Verizon Motorola Droid Turbo Android Development] rampitec:
Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.
[Verizon Motorola Droid Turbo Android Development] xdaNull:
Perhaps this:

https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/

I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.
[Verizon Motorola Droid Turbo Android Development] checo79:
how long? i wait 20 minutes then reflashed backup..
[Verizon Motorola Droid Turbo Android Development] rampitec:
I had the same, waited 15 min for big "M" to disappear (or "bootloader unlocked warning" screen if you did not flash logo-fix)... Well, I did dirty flash, only cleared cache + dalvik. Then rebooted to TWRP again and wiped data. Big "M" passed in a minute. Then "Droid" screen passed in about 5-10 minutes. Now I have it back with MM and setup wizard. Try wiping data, you have backup, you have nothing to lose ;)

P.S. And now I have just restored /data from backup on top of alive MM... Going to to let it boot until morning, while I'm sleeping. If it does not, then no luck, will have to wipe data again, restore apps from Titanium/market and reconfigure. Really hate this step (reconfiguring), and would install custom for smooth updates if only I would not be so excited about Wi-Fi calling from abroad.
[Verizon Motorola Droid Turbo Android Development] checo79:
full wipe, now work, but clock applications still not work(i've tried 4-5 roms)
[Verizon Motorola Droid Turbo Android Development] gherman222:
Yes, it took a while on first boot. But it seems like I've lost root? How can I get it back? :confused:

---------- Post added at 12:24 PM ---------- Previous post was at 11:35 AM ----------

Fixed! Thanks to [MENTION=3250376]ChazzMatt[/MENTION] :)

INITIAL ROOT ON QUARK MOTOROLA MARSHMALLOW 6.0.1

This same version of Marshmallow was released back in July for sibling Quark Moto XT1225. We found out then newer versions of SuperSu don't work for initial root. You need this older version first. No need to re-invent the wheel. It's the same device, same software.

_______________

Go ahead and download SuperSU from the attached file at bottom of this post. It's an older version of SuperSu but works well on the Quark Motorola Marshmallow ROM. You can always update to newer version later.

BETA-SuperSU-v2.62-3-20151211162651

Attached to this bottom of this post or download from here:

https://download.chainfire.eu/751/SuperSU/

Flash this version initially. You can update to newer version later. (People had problems flashing the very newest SuperSu for initial root, but this version works good. Again, you can update to newer version later, after you gain root.)

_______

BONUS TIP - SuperSu Setting

After you reboot, go into SuperSu settings and UNcheck this box. Mount namespace separation.

Uncheck that. Disable that. Then, reboot.

If it's enabled it will conflict with Titanium Backup which you will use at some point, or should. And you will have no idea why Titanium Backup is saying you are out of space, when you are not -- but it's due to this setting in SuperSu!