yashsingh1/xdaforums huggingface dataset:
[Remix OS for PC] HypoTurtle:
Adding/Increasing the size of app_process* will break it; that's why I made it /su/xpo/* instead of /system/* no added bytes == binary runs properly. To alter it to /su/xposed/* you would need to recompile from source [or possibly some sort of dissasemble/reassemble of the code]
[Remix OS for PC] youling257:
oh，/su/xpo，/xposed, /system, 7 characters，so , /su/xpo/lib、/xposed/lib、/system/lib……… ，the same number of characters
[Remix OS for PC] HypoTurtle:
Exactly, I made the same mistake you did last week when trying to make this. i.e. I forgot how elfs work (pointers etc. to specific pieces of code); [I also tried stealing space from the dalvik.so parts (as they aren't needed when using art afaik) but that still stalled] Once I noticed what I was doing I realised I could just use a /su/xpo folder; I was going to move everything to that folder from /su/xposed but figured having both wouldn't do any harm (to move them you just need to modify 000xposed a bit - it didn't/doesn't need altered for /su/xpo)

You can delete the duplicates in /su/xposed/* that are in /su/xpo/*; I had tried symlinking to xpo but that didn't seem to work (only tried once though).
[Remix OS for PC] youling257:
I try /su/xpo links to /su/xposed/system，can active xposed；

or，/su/xposed/system links to /su/xpo，and /su/xpo/lib、lib64、framework、bin、xposed.prop，may also can active，I don't try now.
[Remix OS for PC] Maromi:
since 3.0 power management is fixed. systems will idle now. my cpu runs 10 degress cooler now and will idle at the correct freq now.

actually disabling turbo_boost in intel_pstates is more of a battery saver in android but at the expense of running just as hot or hotter than with turbo. then there is the whole performance issue of if it takes longer to do something you are not really saving battery.

not ideal for all(skylake overclockers) but if you want the kernel supports using initrd=/intel-ucode.img to update cpu microcode for those who aren't receiving firmware updates anymore.
[Remix OS for PC] HypoTurtle:
I'm running a fanless CoreM with an aluminium backplate[/heatsink]. And disabling turbo_boost definitely helps with heat; [boost would be to 2GHz from 800MHz], haven't noticed any real slowdowns, but I guess for devices that default to 300-500MHz with turbo_boost off it could be an issue.

Haven't heard of the ucode thing. Would I need to be running Ubuntu/Linux to do that? So that the grub has a intel-ucode.img to use...

[MENTION=5550662]youling257[/MENTION] it would be actual files in /su/xposed/system/ and the 'new' files (those that aren't present in /system) except *_xposed symlinked to /su/xpo/.
[Remix OS for PC] Maromi:
this is not for everyone. you probably don't need it anyway. i use it because my firmware has not been updated by the oem since the majority of errata fixes were implemented. the oem doesn't have too for windows 10 machines because M$ updates it(sucks to be a skylake overclocker). other OS have it too ubuntu gives an option, fedora automatically.

shows how to make entries

https://wiki.archlinux.org/index.php/microcode

how to make

http://www.linuxfromscratch.org/blfs/view/svn/postlfs/firmware.html
[Remix OS for PC] yshalsager:
Amanzing work, working perfectly on lastest update Version 3.0.104
[Remix OS for PC] Divinitous:
Interesting, care to offer a step-by-step for us users who are limited on click roots and basic stuff.

I've replaced the ramdisk.img by opening the Remix partition through Windows 10.

With a file explorer in Remix i placed su.img in the /data directory

I installed Material Xposed but cannot seem to install the framework.

I seem to be missing an important step.
[Remix OS for PC] HypoTurtle:
That's all that's needed. Check with:

su -v

and

df

In terminal/termux, just to check everything is mounted correctly.
[Remix OS for PC] Divinitous:
Sorry for my ignorance but i'm still lost. I've typed the command and this the response.

s4.postimg .org/ye9azsi4d/Screenshot_20160814_173740.png

Had to put space before .org. My post count is too low to post links
[Remix OS for PC] HypoTurtle:
One of those .imgs is missing or broken.

ls /

and

ls -la /data

to see what's going on

It could be that the su.img is corrupt;

e2fsck -f /data/su.img might help
[Remix OS for PC] kissofkiss:
anybody can make a video step by step ? i am newbie i do not understand tut from HypoTurtle
[Remix OS for PC] wizmart:
hi Hypo, i managed to get xposed 32b installed on ext4 remix 403 not using systemless, it shows on xposed installer but not active, so i tried the symlink option but on reboot no success, it keeps looping. same problem trying systemless32 from your folder no boot. any idea perhaps?
[Remix OS for PC] HypoTurtle:
Probably a permissions issue: Try the instuctions here: http://xdaforums.com/showpost.php?p=68080472&postcount=88 with the system folder from a 32bit(x86) xposed. Or just use the xposed.zip from here: https://groups.google.com/forum/m/#!topic/android-x86/CZ5SXb8PF80
[Remix OS for PC] Divinitous:
Sweet jebus. I'm in business.

I opened the install iso and replaced the ramdisk.img file with the one supplied. I reinstalled the OS. Then with the use of rootexplorer i copied the file to the /data/ directory.
[Remix OS for PC] wizmart:
Thanks, i keep trying, i'll let you know the result
[Remix OS for PC] hellokittyr:
please give a more detail instruction... remix is running so fast on my i7 laptop.
[Remix OS for PC] WilderSu:
Hoooooly efs!, It works! (latest, 64 bit)
[Remix OS for PC] Cyborg Ninja:
Working flawless in latest 104, 64bit
[Remix OS for PC] torsi:
Great TY Hypo!

Worked just fine on 64-bit Latest Remix OS 3.0.201 (VirtualBox VM)
[Remix OS for PC] Whitest:
I don't understand why it's not working for me - I'm on latest Remix OS 3.0.201 64bit as well & as soon as I replace ramdisk.img & place su.img in /data/ while booted into Debian, on next reboot Remix loops at boot logo... or maybe I'm just too impatient and first boot takes a lot longer? I also checked permissions to be the same as all other files in corresponding folders...

Please give me a hint if you have any idea what could be wrong - I'd really like to use systemless root & Xposed with Remix.
[Remix OS for PC] Aguys:
Thats strange, are you using 32bit or 64bit? Coz its only for 64bit
[Remix OS for PC] ranaxda200:
Mine is 32bit and I'm xposed lol. It's running fine
[Remix OS for PC] HypoTurtle:
Just noticed there's two su.imgs there for 32bit - only one of those will work [I shrinked the su.imgs before upload and the first one I posted won't mount/resize correctly] and I'm not sure which is which; let me know which one works so I can remove the other.

Can anyone upload a copy of the 201 ramdisk.img I haven't got that yet.

Alternatively [someone on 64bit systemless] copy the ramdisk.img to /data/tmp and running:

su
cd /data/tmp
systSU

then using/uploading the ramdisk_su.img
[Remix OS for PC] Aguys:
There are two su.imgs, as said Hypoturtle...

Maybe he downloaded wrong su.img or corrupted su.img
[Remix OS for PC] ranaxda200:
Yeah I saw that, though I'm now out of pc but I choose randomly the first one. And it surprisingly works good
[Remix OS for PC] wizmart:
working now after trying with an sfs system finaly. no luck with system on folder

thanks Hypo
[Remix OS for PC] Whitest:
Didn't mention that important info: I'm on 64 bit & had only only tried booting with REMOUNT_RW=1 until now, will test later with normal boot. Thank you wizmart for pointing out your discovery :D I can also upload 201ramdisk later if nobody's faster.
[Remix OS for PC] Aguys:
[MENTION=4056517]HypoTurtle[/MENTION] could you check into this?:D
[Remix OS for PC] HypoTurtle:
The type of system doesn't matter for systemless; [MENTION=1675526]wizmart[/MENTION] was referring to normal system install of xposed [on 32bit I presume] - I'll check the 32bit system install when I get the chance.

In your case it's probably some of the left-over scripts at /su/su.d - I'll post a cleaned version with 201 - so if you can ALT&F1 while it's stuck at the logo; delete the other files in /su/su.d except 00xposed and 00daemonsu; and run logcat to see if it is a bootloop or if it's just rebuilding dalvik-cache [might as well also rm -rf /data/dalvik-cache/* to make sure the xposed dalvik-cache is built]

64bit ramdisk from 201 attached; will also update the gdrive version
[Remix OS for PC] Whitest:
For some reason ALT+F1 when stuck at the logo doesn't work for me, is there an option that has to be enabled/activated to be able to access that terminal?

EDIT : was able to get to terminal booting in debug mode, trying to work on this now

New 201 ramdisk_su.img renamed to ramdisk.img & placed in / doesn't work either ;(
[Remix OS for PC] HypoTurtle:
Strange...

Stock ramdisk.img still works?

There really shouldn't be a stall switching between the two, a logcat will confirm what's happening.

There's a ALT&F1 toggle at the top of Settings ==> Experimental Features.

In debug mode su.img isn't mounted yet I believe; so you'll need to mount that first [ mkdir /su; busybox mount -t ext4 /data/su.img /su ]
[Remix OS for PC] HypoTurtle:
I see you're on a mac of some sort.

What I've identified as the error is this:

<6>[ 28.317520] traps: main[2271] trap invalid opcode ip:f6c2ff9e sp:ffdf6b50 error:0 in libart.so[f6a00000+74b000]
<6>[ 28.528244] traps: main[1923] trap invalid opcode ip:7fbf788d950b sp:7ffecf067970 error:0 in libart.so[7fbf78687000+71e000]

hopefully you know about opcodes and can find a way around it; my knowledge is limited and would require some googling.

Edit. try adding microcode.blacklist=yes to the command line.

And chmod 000 /su/su.d/00xposed to turn xposed off - which should boot
[Remix OS for PC] danerrickcuba@gmail.com:
edit
[Remix OS for PC] Whitest:
changing the permissions of 000xposed worked immediately, I'm writing this booted into Remix OS with your ramdisk and su.img, although Xposed is obviously turned off - so it seems my old Macbook does not want to cooperate with Xposed...

Did you mean I should add microcode.blacklist=yes to grub boot parameters? or in another command line?
[Remix OS for PC] wizmart:
Yes i was talking about 32bit install on ntfs which succeeded on first try with sfs system without REMOUNT_RW, obviously we have to be read-only for systemless, xposedless.

before that i was trying on an ext4 usb full rw install system on folder and i could only get xposed (solar32) to show up but not active and i mean a normal installation no systemless (which didnt work me)

it seems the read-only condition first must be there to be able to install or has anyone managed to get it running on system folder ext4 32b ?
[Remix OS for PC] HypoTurtle:
To grub [on the linux line]; bit of a longshot though.

Can you check the logcat of the booting system to see if the opcode error is still there.
[Remix OS for PC] Whitest:
microcode.blacklist=yes did not have eny effect :(

in logcat after booting system with 'chmod 000 000xposed' opcode error is gone. :p so you were right about guessing that it was the cause of the bootloop. But even after googling for a while I can not understand what this opcode error means nor how to resolve it...

screenshot: [IMG="Screenshot RemixOS 'chmod 000 000xposed'"]https://s3.postimg.org/u0nj5qqcj/Screenshot_20160821_160440.png[/IMG]
[Remix OS for PC] HypoTurtle:
Can you post the output of lsmod.

Also there's a xml for blacklisting modules in /system/etc; try copying that to /su/vendor/etc/ and add microcode to it

Previously all I'd known about opcodes was that they were caused by hardware abd needed to be addressed to get OSX running on non-Mac hardware; not sure what else can or should be done about this opcode caused by a lib.
[Remix OS for PC] Whitest:
I'll try that xml method now. Thank you very much for taking the time to help me with this! :highfive:

EDIT: tried copying the modules.blacklist to su/vendor/etc/ and added 'blacklist microcode' using the same format as the original file - no luck.

Attempt results: microcode still enabled and the opcode error still present. extracts from new dmesg:

<6>[ 1.560644] microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa07
<6>[ 1.560655] microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa07
<6>[ 1.560690] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[...]
<6>[ 28.162793] traps: main[2469] trap invalid opcode ip:f6c17f9e sp:ffb25380 error:0 in libart.so[f69e8000+74b000]
<6>[ 28.358324] traps: main[2109] trap invalid opcode ip:7f180cc5950b sp:7ffd18e00e50 error:0 in libart.so[7f180ca07000+71e000]

lsmod output:

root@remix_x86_64:/ # lsmod
Module Size Used by
binfmt_misc 9139 1
wl 6423592 0
joydev 8960 1
applesmc 11656 0
input_polldev 5455 1 applesmc
acpi_cpufreq 10937 1
cfg80211 476703 1 wl
mac_hid 3836 0
btusb 31713 0
btrtl 4762 1 btusb
btbcm 7000 1 btusb
btintel 8387 1 btusb
bluetooth 441249 5 btusb,btrtl,btbcm,btintel
appletouch 9442 0
pcspkr 2158 0
efivars 7534 0
nouveau 1333267 8
mxm_wmi 2141 1 nouveau
wmi 8792 2 nouveau,mxm_wmi
snd_hda_codec_realtek 68154 1
ttm 76365 1 nouveau
snd_hda_codec_generic 53782 1 snd_hda_codec_realtek
drm_kms_helper 108236 1 nouveau
drm 311145 11 nouveau,ttm,drm_kms_helper
fb_sys_fops 1759 1 drm_kms_helper
sysfillrect 3485 1 drm_kms_helper
syscopyarea 3185 1 drm_kms_helper
sysimgblt 2562 1 drm_kms_helper
i2c_algo_bit 5413 1 nouveau
shpchp 23543 0
forcedeth 51245 0
snd_hda_intel 28217 0
snd_hda_codec 105357 3 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 53852 4 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec
snd_hwdep 5777 1 snd_hda_codec
snd_pcm 87200 3 snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer 20636 1 snd_pcm
snd 65310 6 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6619 1 snd
i2c_nforce2 6194 0
hid_appleir 2965 0
hid_apple 6169 0
coretemp 6212 0
hwmon 4420 3 applesmc,nouveau,coretemp
apple_bl 4727 0
sbs 7893 0
sbshc 4466 1 sbs
[Remix OS for PC] asuduakali:
hai [MENTION=4056517]HypoTurtle[/MENTION], can you create systemless Xposed with SuperSU in it? because stock Superuser still not work enough, some apps still need SuperSU Privileged to abe working, like Titanium Backup Apps
[Remix OS for PC] HypoTurtle:
It already has SuperSU; systemless xposed is dependant on systemless-root from superSU v2.76+
[Remix OS for PC] danerrickcuba@gmail.com:
here is what u need, post#99:

http://xdaforums.com/showthread.php?p=68101191

its generally a good idea to briefly go through forums/threads b4 posting a request!

<<<New World Order (NWO)>>>
[Remix OS for PC] asuduakali:
how to activate it? i use 3.0.201 version either x86 or x86_64 still use superuser to gain root access,must i need to install SuperSU manually to activate it? :confused:

thanks to answer my Questions
[Remix OS for PC] HypoTurtle:
Well the su binary included is superSU-v2.76+ and the location where it's stored is r/w able. If you use superuser apk it'll likely install/replace with it's own binary; so you should install SuperSU apk [an su manager] instead.

Check the su version with su -v
[Remix OS for PC] asuduakali:
i got it, thank you for answer my questions, now i clearly understand it :D
[Remix OS for PC] ians325:
Hopefully someone will release a version with Xposed and Su preinstalled soon
[Remix OS for PC] apersaud500:
Hi,

I keep getting this error, when installing remix os:

windir=C:\Windows

systemDrive:C:\

powershell.exe

this is WV_VISTA

Couldn't find uninstall program. E:\RemixOS\UninstallRemixOS.exe

checkefi

checkefi result:16000

remove: BCD failed. (16011)

checkSecureBoot result:16003

checkbitlocker E:\ result:1

data image:E:\RemixOS\data.img

installation,open_app,

installation,create_data_image,NTFS 8GB

installation,install_hdd,Remix_OS_for_PC_Android_M_64bit_B2016081502.iso

checkefi

checkefi result:16000

x86_64

arch=1

srcBaseDir E:\/RemixOS/efi/RemixOS/

targetBaseDir Z:/efi/RemixOS/

installFailed: 1

cd6 :no_device

cd7 :no_device

installation,install_hdd_efi_not_support,failed

installation,install_by_tool,hdd

messagebox,installation_failed,OK
[Remix OS for PC] HypoTurtle:
Yea; not seeing anything there of note.

I guess it could be due to a badly compiled lib; you might have better luck with the x86 version as that xposed is more officially supported.
[Remix OS for PC] Whitest:
Alright I'll try out with x86 remix and report my results here
[Remix OS for PC] phamtieugiao:
Hi guys, I flashed xposed-v85-sdk22-x86_64-MIUI-edition-by-SolarWarez-20160610.zip on my Mi Pad 2 running Remix OS 2.0 (Android 5.1.1). I got bootloop after flashing, any idea why?
[Remix OS for PC] asuduakali:
current ramdisk were work great on 3.0.201 :good::good: but it not working on 3.0.202 can you fix it [MENTION=4056517]HypoTurtle[/MENTION]? :o
[Remix OS for PC] HypoTurtle:
I'll upload later...

If you're on 64bit I've already included to tools to automate it [hopefully].

Follow this

Edit. 32bit uploaded is based on 202; 64bit is based on 201 [I think] but has been working fine for me on 202
[Remix OS for PC] asuduakali:
wow!!! that's great news, i'll be try it right now :good::good::good:

edit:

can't run systSU command dude, it says "sush: systSU: not found"
[Remix OS for PC] asuduakali:
still no luck [MENTION=4056517]HypoTurtle[/MENTION]

seemy previous post for detail

can you teach me how to create it manually?
[Remix OS for PC] HypoTurtle:
Sorry didn't see the edit.

You've switched to stock ramdisk right... as the modified one isn't working for you on 202/203?

In that case we need to mount the su.img

su
mount -o rw,remount /
mkdir /su
busybox mount -t ext4 /data/su.img /su
PATH=$PATH:/su/xbin_bind
cd /data/tmp
systSU

Let me know how that goes... [the ramdisk for 201 should be working fine with 202; so don't know if there is another issue here]

Edit. [MENTION=7387223]asuduakali[/MENTION] if systSU is still not there add the two files in the attachment to /su/xbin_bind with 755 permissions
[Remix OS for PC] asuduakali:
so i must update it to 202 and then do command after update? or i must run command from 201 x64 systemless?
[Remix OS for PC] HypoTurtle:
Version doesn't matter - but if you aren't using the modified ramdisk.img; you will need to mount the su.img manually as that is where the systSU binary is.

i.e. update to 202 = stock ramdisk = need to mount su.img manually [with those commands]

201 x64 systemless = modified ramdisk = su.img automatically mounted already
[Remix OS for PC] asuduakali:
ok, i'll try it right now :D
[Remix OS for PC] modaifallah:
I have 32 bit 3.0.203, what are the instructions?
[Remix OS for PC] asuduakali:
at last it works and run perfectly, great job dude :highfive: problem are with sukernel and systSU module that deleted before

use my modification ramdisk, i modified it using [MENTION=4056517]HypoTurtle[/MENTION] tutorials :D this one
[Remix OS for PC] HypoTurtle:
I'll add that to gdrive if that's okay. I'll make it clear which version it's from.

Realised that those mightn't be there like I thought when I downloaded the zips posted by whoever posted that xposed installation video - and credited them to 4pda [they are my images repackaged - without even bothering to 'clean' them].

To be accurate sukernel is from chainfire [ I could have written something similar in bash rather than the C++ he used - but as it's there already... ] and systSU is a simplification of the systemless-SuperSU install script

[MENTION=5754220]modaifallah[/MENTION] the 32bit ramdisk here is already based on 203
[Remix OS for PC] modaifallah:
So I replace the ramdisk and it's now working?
[Nexus 5 Q&A, Help & Troubleshooting] garikfox:
Hello everyone I just got my Nexus 5 this past Wednesday and while i was typing a text message with google messenger out of the blue it vibrated for 1 second, I turned off all alerts and no other notifications were seen. Anyone know why it did this ?

I'm on 6.0.1 BTW
[Nexus 5 Q&A, Help & Troubleshooting] funnel71:
Mine has done that too. It occurred while I was viewing email and I thought perhaps it was an ad vibrating my phone. I'm also getting about 50% of my calls while the rest are sent to voicemail with no explanation. I'm contemplating going back to lollipop
[Nexus 5 Q&A, Help & Troubleshooting] siddhu007:
Same here

My nexus 5 started to vibrate while i was texting.The vibration was continuous.I was really scared so thought of rebooting now its good and no more random vibrations :D
[Nexus 5 Q&A, Help & Troubleshooting] Cyber755:
Flash new ROM

Which ROM are you using?

Maybe this is a bug which is ROM related.

Just flash a newer version of your Rom.
[Nexus 5 Q&A, Help & Troubleshooting] humzaahmed155:
It's weird alright. On my old Nexus 5 it vibrated like crazy every time I shook the device ?
[Nexus 5 Q&A, Help & Troubleshooting] garikfox:
I turned off vibration on keypress for the Google keyboard, I doubt that was it but you never know we will see :)
[Xperia Z2 Q&A, Help & Troubleshooting] squeezer72:
After installing a new Display, the Device doesn't Charge anymore. It shows charging symbol for a second, then turns off and then starts looping. You can see it in this video:

www.youtube.com/watch?v=7n7CNDWQ1No

Is it possible, that the battery is exhausted?

Anyone with the same Problem and any idea, how to solve it?
[Xperia Z2 Q&A, Help & Troubleshooting] iArvee:
Yeah, could be. I repaired my Z2 after water got inside. After a few weeks, phone kept shutting off randomly. I had to plug it in so it would turn on. I replaced it with a new battery and everything was back to normal. :D
[Xperia Z2 Q&A, Help & Troubleshooting] squeezer72:
Got it running again?.

This worked for me:

1. Open the device carefully

2. Disconnect the battery from motherboard

3. While battery is disconnected from motherboard, push Powerbutton several times (did it 3 or 4 times)

4. Connect the battery carefully

5. Close the device and put charger on

The device should start charging normally.
[Note Edge Q&A, Help & Troubleshooting] darg:
Hi hoping for a bit of help. Flashed stock 5.1.1 on my 915fy last night, flasked the correct custom recovery and then slashed mickeys custom kernel after wiping the cache. Since then my wifi wont automatically connect to my home wifi but works perfectly when connected manually each time which is a pain. Anybody help fix the problem, thanks in advance?

***Should add that i have to input the wifi password every time when connecting manually
[Note Edge Q&A, Help & Troubleshooting] husko:
I have the same problem.. dont know how to fix it
[Note Edge Q&A, Help & Troubleshooting] darg:
Researched this and found an answer. Had to change a ro.secure file fro "true" to "false"
[Honor 7 Q&A, Help & Troubleshooting] netegitmen:
PLK-L01 C432B130 to update B130 to B140 update fail and PLK-L01 C432B300 problem. Help me. no update, no downgrade.

dload and fastboot fail.
[P3300, MDA Compact III General] Rich G:
Hi Guys,

This has been mentioned before, but I thought i should re-raise it, as far as I'm aware there has been no fix suggested yet.

Wi-fi turns off when you put your device on standby - is there any way to always keep wifi on, unless of course you turn it off manually with the connection manager.

Looking forward to any suggestions or workarounds.

Many thanks & kindest regards,

Rich.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Haroon786:
Hello guys,

I have the GT-I9195 running build 13.0-20160124 (latest). I've searched around for ages looking for a fix or correct version of SuperSU beta to install but to no avail. It just stays on the CM boot screen forever. I've tried versions 2.49, 2.51 and 2.64. Is there a version which works on the S4 mini?

Also, I know there is an inbuilt root manager for CM13 but many apps still do not work when granted access through it. :(
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] S3miniFin:
Here is working version for recovery installation: https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip

http://xdaforums.com/showthread.php?t=1538053
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Haroon786:
Thank you, will try it when I get home :)
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] strumcat:
Sorry to resurrect an old thread, but I just wanted to mention that this also works for cm13 on the LG Optimus L90 LG-D415. Big thanks.