yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] kh.farooq.92:
With Android 7.1.1 i noticed some issues (I was talking about it with defcomk):

- Reading / Writing speed (tested many times with a1 sd bench) dropped: with Android 6 --> R 220 / W 87; now with Android 7.1.1 --> R 175 - W 87

- Google photo can't able to see 60fps videos smoothly (with vlc they look as perfect as always, but i want to see my personal video and photos with only one app...with MM Google photo was working great for 60fps videos)

- Battery finish earlier

- one of the reason to update from android 6 to android 7 was the multitasking mode, which has been removed from 7.1.1

Anyone notice same issues? Do you suggest me to wait for some update or to go back to Android 6? Thanks
[Nexus 6P Q&A, Help & Troubleshooting] GKti22:
Not at all it has been quite the opposite from my experience, also the multitasking is still present, have you clean flashed the latest factory image?
[Nexus 6P Q&A, Help & Troubleshooting] kh.farooq.92:
Yes i've made factory reset and canceled data and everything. After that I've made the 7.1.1 update that my Nexus notificated me. I'm happy that your experience is opposite of mine, but you cannot say that 7.1.1 support multitasking...I've read for confirm in other forums that they have removed that feature...when you go to other, after long press on the icon on notification bar to activate the "hidden settings" there's no more the multitasking feature! Thought now I go back to MM and magically I tested again my reading writing speed... Reading increase to 223mb

and writing increase to 96mb

I also see people who have on Nexus 6p 122mb writing speed, how's that possible?
[Nexus 6P Q&A, Help & Troubleshooting] blitzkriegger:
If you are talking about the multi-window feature it is still present in Android 7.1.1. When you have an open app (which allow multi-window) you just have to long press the recents button so you can choose which app to display on the lower half of the screen. The system tuner setting related to the feature has been removed but rightfully so as it is already set by default.
[Nexus 6P Q&A, Help & Troubleshooting] kh.farooq.92:
Ok thanks!btw i'm not still understand why i have a better Reading writing Speed on MM instead Android N...
[Nexus 6P Q&A, Help & Troubleshooting] boxguy1:
Use ex kernel it speeds read/write speed
[Nexus 6P Q&A, Help & Troubleshooting] kh.farooq.92:
Thanks
[Nexus 6P Q&A, Help & Troubleshooting] countersteer:
Personally, I would stay on 7.1.1. Google is quick to address feedback in their monthly updates and you are currently up to date with security patches.
[Android General] Rendering:
I am a Linux power user, so I am used to deal with Linux / Unix partitions, BUT Android partitioning scheme has always been a huge WTF to me, even if I resized partition of many Android phones with the lovely XDA guides.

Okay, let's start with what is easy to understand. Here you can read a good explanation of Android partitions

/boot

/system

/recovery

/data

/cache

/misc

Let's take as examply my Samsung Galaxy S5: it is selled in two versions 16 GB and 32 GB internal storage. Mine is 16 GB

I installed CyanogenMOD 13 on it, I installed a 128 GB micro SD card and I formatted it as internal storage (Andoird >= 6 feature).

Android >= 6 internal storage has been projected to expand the applications memory too

So I expected the phone to see the 128 GB micro SD card as the only memory storage. But it is not actually.

At the following URL https://s27.postimg.org/rmc4muymr/Android.jpg you can see the phone using two different storages:

Internal memory 11,59 GB

SD Sand Disk card 119 GB

I cannot understand why Android is still using the internal memory of the phone, even if it is actually using the SD card too (as I can see checking the size of /Android folder on the SD card).

Could you please help me understanding "the magic" behind Android storage paradigm?

Thank you
[Android General] Rendering:
up
[Android General] sandix:
With that feature, apps that can be installed on "External" storage, will be installed there by default, same with pictures and videos, you now have the option to move apps AND its data (Unlike before in 5.x)

The phone will treat the SD card as internal storage (Only because of the way the SD is formatted) however, being that SD Cards are slow in design, Android will not classify it as "Actual" internal storage.

I hope this information helps you out!
[Amazon Fire Phone] :
Nothing here anymore.
[Amazon Fire Phone] mifl:
After giving a first look at his work, there are some things I do not understand:

There is no complete history of your work, so it is very difficult to collaborate in this.

You use as version 4.6.1 kernel, the last being released 4.6.6

It uses a toolchain linaro-4.9-arm-linux-gnueabihf, when the original kernel should be compiled with arm-eabi-4.7.

MIFL.
[ONE Q&A, Help & Troubleshooting] szaf:
Had the same problem with H20. Flash recovery via fastboot
[ONE Q&A, Help & Troubleshooting] Zurga Evan:
ok bro pb solved from oneplus forum

thanks in advance for your reply :)
[OnePlus 3 Questions & Answers] JazzieBoi:
I have problems on my internal sdcard where I cant write to some folders, they are read only. No idea how this happened... Here is the permissions fixer I was going to flash: http://xdaforums.com/attachment.php?attachmentid=3761904&d=1464187934

I just wanted to make sure its okay to flash so that I don't turn my op3 into a paper weight, thanks :)
[Samsung Galaxy S7 Edge Questions and Answers] daniel81uk:
Like in title. S7 EDGE is not saving/breaking video files when recording app is set to save on SD card. After recording file thumbnail is just a black square with 0Kb size. It works fine for photos and when saving to internal memory. Memory card is not an issue here as 5 or 6 different gives same results.

This is not my device. One of my friends called me earlier today and asked for help since I work with phones but this is first time I heard about this issue.
[X Style (Pure) Q&A, Help & Troubleshooting] hometech99:
If go to stock and relock bootloader for OTA, what is procedure to unlock again? Do you go back to the Moto site for a new code, or will they expect you to have the original unlock code (thus you could be outta luck if you bought the phone used , with an unlocked bootloader.)
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
The procedure is the same as when you first unlocked, although if you have the original unlock code you can skip getting a new one from Moto's site (it's the same code anyway), same rules apply, it will wipe everything and you must have OEM Unlocking in Developer options enabled as when the bootloader is relocked this option is turned off and must be turned on again manually.

Be aware you do

NOT

have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc).
[X Style (Pure) Q&A, Help & Troubleshooting] hometech99:
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."

Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
[X Style (Pure) Q&A, Help & Troubleshooting] southlandrunner:
Here ya go..

http://xdaforums.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Just look in my sig... if you read there are links to firmware, and instructions to lock and flash, or just flash the factory image. I would recommend flashing the complete system image though, not just the pieces.
[X Style (Pure) Q&A, Help & Troubleshooting] hometech99:
..but your flashboot instructions show the pieces. Did you modify the process, and get the whole system image?

Thanks!:)
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
No, I meant each piece of the full image, don't skip any parts.
[Redmi Note 2 General] gnazio:
A moderator of the official forum has opened a thread to collect data to help developers analyze and (let's hope) fix problems related to battery duration.

Please collect your data and sent them, this could be a unique and the last opportunity...

Here's the thread:

http://en.miui.com/thread-429741-1-1.html
[Tilt, TyTN II, MDA Vario III General] aksd:
I read in the spec sheet(I'm sure many of the members must be aware of this already) that the QUalcomm processor supports USB On the Go, and since Windows Mobile 6.0 has the necessary drivers built in if a suitable cable is used as this maybe http://www.cableclub.com/female-mini-male-adapter-p-1871.html, we can have a USB host device? I did a search and in a post, which I cant find again a member said USB OTG was working on a friends Kaiser. Any other members tried it out yet?

Regards,

Akshay
[Sony Xperia XZ Questions & Answers] jmwtac:
Hi, I have fixed my phone thanks to other users, When Xperia Manager repaired phone, It installed Android 7.0, Everthing works fine except for the Stock Camera application which says it is being used by another application. If I insall another camer application it works fine and snapchat etc. Any ideas of way to fix, I have tried xperia manager again to repair and still the same. Anynone else having this issue ??

Its ok seen how to solve it with unlocking bootloader again.

Thanks
[Sony Xperia XZ Questions & Answers] Linux4ever85:
Did you try rebooting your phone?
[Sony Xperia XZ Questions & Answers] chawlasrijan:
Please check the other threads before posting, this issue has been solved already.

You need to Unlock your bootloader again on N using Sony's official guide.
[Xiaomi Redmi Note 4 Questions & Answers] gaosphappy:
Hi all.. I have just today received my note 4 global edition and turned it on and love it... However when setting up it asks to choose your locale but there is no united kingdom option..

Question is what am I missing and what have other uk users picked. I chose Poland purely because of my Samsung s2 days.

Any help advise etc great fully received. :good:
[Xiaomi Redmi Note 4 Questions & Answers] gsmyth:
I think I chose Spain, but it doesnt seem to make a difference in actual usage terms (anywhere in the OS), as you set the language to english anyway.
[Xiaomi Redmi Note 4 Questions & Answers] sudd1976:
Hi,

I'm also in the UK and it doesn't matter what location you choose, you can set time and date and also the wether app has all UK cities.
[Greenify] craigevil:
Newest stable version works but doesn't ask for root privilege. Rooted using Chainfire's supersu.
[Greenify] ghst7:
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now

Best of luck
[Greenify] olliebean:
Which settings require root? I've toggled all the settings and none of them made it ask for root.
[Greenify] ghst7:
For me it asked for root when I changed settings under "wake up tracking and cut off".

If nothing happens to you reboot your phone and try again, you could also check to see if there is any denied requests of greenery in super su app and manually grant it.
[Greenify] craigevil:
Oh it works just fine. It's just not showing up in Supersu as having root access.
[Greenify] ratchetrizzo:
I have the same problem.

After I updated from the market today I can't get greenify to properly request root access.

When I run it I tell it I'll rooted, see it saying it's requesting root access but supersu doesn't prompt then says it can't get root. Same results with rebooting.

In supersu there are no request prompts from greenify. I deleted the greenify access to see if that would get it to reprompt but it still says can't get root and supersu shows no requests in logs.

Other apps still work fine in supersu.

Edit --

Interesting, I disabled the module in xposed and when it prompts for root supersu pops right up. So I gave it access that way but logs show that once the module is reenabled it never asks for root.

Weird
[Greenify] rockah:
Can't get root privilege

I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.

What i did so far:

Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.

Reboot

Never it shows up in SU or get root request permission popup.

On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
[Greenify] newkydawg:
Got mine to work by deselecting Greenify module in Xposed and rebooting. Started Greenify app and it said to either to activate the Xposed module or select non-root mode. I clicked on Greenify settings and tried to change Xposed settings and a popup window asked if I wanted to activate Xposed module. I selected yes, Xposed started, I selected Greenify module and rebooted. During the bootup process, Greenify asked for root permissions.
[Greenify] olliebean:
A similar process worked for me: deactivated the Xposed module, rebooted, started the Greenify app, then I went into the Greenify settings and turned on the enhanced wake up tracker, which caused Greenify to request root. Granted permission, then reactivated the Xposed module and rebooted again. Checked in SuperSU that Greenify had permissions, then I just had to re-enable the Xposed based features in the Greenify settings.

Having done that, however, I see from the SuperSU logs that Greenify isn't actually requesting any root permissions since I re-enabled the Xposed module. I suspect the new version is using Xposed for all its root access and no longer needs root permissions for the app in Boost (Xposed) mode.
[Greenify] dreinulldrei:
Lots of guessing here.

I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
[Greenify] DB126:
Read prior posts for further guidance. Seems others have got it to work. I had zero/nada/no problems on latest betas w/Xposed and SuperSU 2.76. YMMV.
[Greenify] dreinulldrei:
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
[Greenify] DB126:
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).

BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
[Greenify] divineBliss:
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.

Wonder if I should drop back to v2.76 and how to even do that without losing root?

---------- Post added at 03:55 PM ---------- Previous post was at 03:43 PM ----------

This page has a link to the SuperSU v2.76 zip on ChainFire's site, which can be flashed with TWRP, etc depending on your phone.

https://www.progeeksblog.com/download-supersu-for-android/

I have not tried to flash it myself.
[Greenify] DB126:
If life is good don't change anything! I'm not out to skewer SuperSU v2.78; the problems I and a few others experienced are likely outliers with various contributing factors. That said, SuperSU 2.76 has been rock solid on my devices as have most of ChainFire's previous releases. Sticking with what works for now.
[Greenify] craigevil:
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
[Greenify] divineBliss:
If you moved Greenify apk to

"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
[Greenify] DB126:
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
[Greenify] divineBliss:
I don't think you can do anything to the SuperSU configuration to make it so apps in priv-app have to ask for SU permission. I have other apps in there and have never seen them ask and they are not in SuperSU log either.

I moved my Greenify apk into priv-app because it wasn't clear to me that there was nothing to gain by doing that as I already had Xposed installed and working. Have since moved it back to original folder in /data/app/.
[Greenify] pure.by:
- Android 6.0.1

- SuperSU 2.78 (systemless root)

- Xposed

- latest Greenify Beta from PlayStore (in Root+Boost mode)

- NOT installed as system app or anything.

Same problem here -- Greenify never asks for root, is not listed in SuperSU logs. Greenify initially had root access iirc, but one of the updates from PlayStore removed it.

Nevertheless Greenify seems to be working fine though.

EDIT: All other root apps on my phone (OnePlus 2, stock OxygenOS 3.1) don't have any issues with root access.
[Greenify] divineBliss:
I have the same versions you listed, but Greenify does ask for su and is in the SuperSU log. Interesting.
[Greenify] pure.by:
Interesting indeed.

I forgot to mention my root is systemless, and all other root apps don't have any root access issues whatsoever. OnePlus 2, stock OxygenOS 3.1.
[Greenify] DB126:
My experience is somewhat different. User apps explicitly moved into priv-app continue to prompt for SU permissions if not already defined. Obviously other items in that folder do not. Possibility under developer control or the apps I chose were not a representative sample. Topic quickly moving above my pay grade...

Yesterday I reflashed SuperSU as part of a rom refresh and deleted Greenify's permissions in SuperSU. Just noticed it did not ask for reauthorization but appears to be working fine in root+boost(Xposed) mode with various features enabled that previously demanded root. Greenify app remains in user space. Fascinating.
[Greenify] divineBliss:
I should clarify that the other non-system apps in my priv-app are helper components of battery monitoring apps that got installed by the battery apps after they asked me for permission to do that, so maybe that makes a difference? New ground for me too.

My phone root is not systemless, running CandySix ROM on Huawei Ascend Mate 2 :) . Xposed framework v86. Latest is v87.
[Greenify] adlx.xda:
Exactly what I did too... I guess there some bug in the Root checking method lol.
[Greenify] divineBliss:
Now since last night my Greenify is not showing up in SuperSU or asking for su permission based on no toast from SuperSU. Dunno what changed :confused: ? I didn't update Greenify or SuperSU or Xposed. Tried rebooting before posting and no change. Greenify seems to be working fine.

I am using Greenify 3.0 build 5 and feeling rather confused now :confused: :) .
[Greenify] DB126:
Mirrors what happened to me. Real head scratcher but not complaining as Greenify appears to be working fine. 3.0 build 5.
[Greenify] divineBliss:
Earlier today I went into SuperSU and changed Greenify setting to prompt for SU. Hours go by, I've gone into Greenify numerous times and zzz'd apps, no SuperSU toast occurred.

Few minutes ago I decided to Greenify "Bluetooth share" system app, and bam, SuperSU request for Greenify pops up and Greenify is in SuperSU log. Now I can't reproduce that again :confused: . Gremlins in here :lol: . Oasisfeng must be rofl. :) Where is he these days?

I did undo the "Bluetooth share" Greenify BTW, as I do want Bluetooth to work in my car :) .
[Greenify] DB126:
Tried to duplicate your findings w/BT share and several other system apps. No SuperSU prompt...but also no problem hibernating apps. At least as reported by Greenify. I have not tried to verify hibernation status. Boost (Xposed) mode.
[Greenify] jogibear:
Had the same issue and resolved it.

Here is what I did :

Restored previous version of Greenify using Titanium.

Rebooted.

Updated from Play store.

Once updated I opened the Greenify app directly from the play store (before rebooting).

It then prompted for root access and then I could grant it.

Continued with new setup screens.

Closed the app and then rebooted.

New version was then working with root.

It should be noted, however, that I use the donation features. When I toggled any of them it still asked me to purchase the donation pack even though it was previously purchased and installed. I had to uninstall and then re-install the donation pack and then all works fine.
[Greenify] divineBliss:
Will be interesting to see if you get any more SU requests or log entries in the SU app if you have those enabled.
[Greenify] divineBliss:
Newly released SuperSU version 2.79 on Play Store to add to the mix :) .

https://play.google.com/store/apps/details?id=eu.chainfire.supersu
[Greenify] guastucci:
Here too. Using CF or magisc root module. Both say that root access is not granted. What may I do?
[Greenify] 4ronie4:
Same problem with moto g 2013 CM 13, greenify never asks for root and says that device is not rooted.
[Greenify] divineBliss:
I had changed my SuperSU Greenify configuration to Prompt for Greenify and log full content.

Well, I looked at what Greenify did last time it was logged in SuperSU two days ago and it had to do with changing permissions and writing file

"/data/system/ifw/gib.xml"

which is related to Android Intent Firewalls - huh? Never heard of that before, so googled and found:

http://www.cis.syr.edu/~wedu/android/IntentFirewall/

I don't know what if anything that has to do with me Greenifying "Bluetooth share" which I wrote about before. :confused:

Can you guys check and see if you have said gib.xml file which has Greenify UID on my phone BTW :confused: .

No prompts or log entries for Greenify from SuperSU since this event two days ago and Greenify appears to be working fine as far as I can tell.
[Greenify] DB126:
- have that file

- no Greenify entries

- no SuperSU entries or log entries for Greenify

- that said Greenify 3.0 B5 continues to perform as expected in root/boost/Xposed mode
[Greenify] divineBliss:
Thanks! Is gib.xml file UID corresponding to Greenify on your device? GID is system in my case. What about file date? Mine is 12/14/2016.
[Greenify] DB126:
Sometimes screenshots are easier/quicker. :)
[Greenify] divineBliss:
True! :) Total Commander File Manager:
[Greenify] divineBliss:
Setting SuperSU to prompt for Greenify su, then setting gib.xml UID to system, then adding a new app to the Greenify hibernate list will result in a SuperSU toast for Greenify.

Do I get a cookie :lol: ? Greenify will then change the UID, update gib.xml, and be happy without prompting for su again. I'm guessing Greenify just started using Intent Firewall - or maybe a more efficient way of asking for su less often. What does all this mean? Dunno? BTW, anyone know where oasisfeng is? He's gone into stealth mode :lol: .
[Greenify] SyCoREAPER:
Mine is also failing to get root, this has never happened before. Everything else sees/obtains root perfectly fine.

Right as I posted this, maybe coincidence. While Greenify says obtaining root, I angrily tapped the white area in Greenify and suddenly the root prompt popped up
[Greenify] divineBliss:
Update: Each time I add a new application to the Greenify hibernate list, I do get a SuperSU root request for Greenify. Don't see a SuperSU request for Greenify otherwise. Greenify appears to be working fine.

This is with Android 6.0.1, Greenify v3.0b5, (root + Xposed) mode and apk in /data/app Greenify folder.