yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 General] CLARiiON:
This trick applies for all Samsung phones. Wait for 3/4 months and let prices stabilize.

Andrei F from Anandtech also mentioned this in another forum about the Exynos:

Positive signs for batterylife.

---------- Post added at 12:16 AM ---------- Previous post was at 12:12 AM ----------

This should be a thing of the past, you got auto-upload options from Google, Microsoft with tons of storage. Just use them ;)
[Galaxy S6 General] se1000:
yeah. I'm really curious to see what the SOT is on this thing, we might be very pleasantly surprised.
[Galaxy S6 General] tyvar1:
I can understand your concerns, but for me I always full wipe when flashing roms to get the most stable start. So for me this will not be any problems. :)
[Galaxy S6 General] CLARiiON:
I am sure it won't be as good as Z3, but won't be bad either. This is what Samsung mentioned in keynote.

Normally Samsung delivers what they claim in batterylife. Last year they claimed 10h in the event.

And Anandtech found that those claims were correct.

^^ This has results for both 'normal' S5, as well as LTE-A S5 with QHD display. I am positive that this year to battery claims won't be very far from truth.
[Galaxy S6 General] istperson:
And I surely won't. I'm running cm12 on my Note 3 and I'm more than content with that. Actually I'm more interested in porting cm to an x64 Atom phone than admire the glass back and the trillion ppi display.
[Galaxy S6 General] brucipher:
I don't get this comment. I use a Nexus 5, have no sd card, and perform factory resets all the time and do not lose all my personal stuff....
[Galaxy S6 General] the_rooter:
Doesnt anyone else see that the casings of both phones look like the iphone 6+. Its just a copycat. I am sorry this is one of the reasons I am staying away.
[Galaxy S6 General] abbaskip:
My concern isn't so much the processor eating the battery, but that QHD screen. The screen is always such a big battery eater, so whilst the processor being more efficient is great, QHD is a concern - and I'm not sure you need any more than Full HD on a mobile device.

I'd have preferred a Full HD Super Amoled+ (i.e. non pentile) display.

Has anyone yet been able to find official word on MHL?
[Galaxy S6 General] tft:
https://www.youtube.com/watch?v=jUfvZs01ePI

.. a feature tooted by samsung.. so yeah.. now samsung users will be wall huggers along with iSheeps..
[Galaxy S6 General] geoff5093:
This doesn't make any sense. Internal storage is a separate partition, as far as custom recovery goes it's no easier or harder to wipe internal storage as it is external storage. It's a simple checkbox when performing a wipe. I have a G3 and store everything internally, I do full wipes all the time and you just simply exclude internal storage when wiping.
[Galaxy S6 General] Szadzik:
Hardly. If you think the only reason people use Android over iPhone is SD Card slot and removable battery, you are very wrong. The differences between the two OSes go much deeper than that and looking at how iOS 8 and up works on iPhones in my corporate environemnt, Apple has even lost the software polishing war as well, not only the war on getting you more control over the phone and all the customization you can do.

Do you think I ever had an extra battery for my S3-S4-S5? Nope. Everyone reasonable will use an external battery pack as it does not require replacing when changing devies and charges all other devices as well.
[Galaxy S6 General] da.trute:
I did add the caveat that I was a musician.
[Galaxy S6 General] Annunneo:
As I type this my battery is at 4% and I'm miles away from home, what do you think I'll do? Pull this extra battery from my pocket and pop it into my s4. Samsung lost their fricking minds with the s6, blasted buffoons.
[Galaxy S6 General] Szadzik:
Ever heard of car chargers or battery packs? Do you live in a cave?
[Galaxy S6 General] Annunneo:
I don't care for chunky clunky battery packs and do you think you'll be in a car always, nothing beats the simplicity and practicality of a removable battery.
[Galaxy S6 General] Szadzik:
Do not buy a phone with nonremovable battery, then. No one is trying to make you buy one.
[Galaxy S6 General] Annunneo:
So I have a question. If or when roms are made will your storage choice come into play? Like will certain roms only work for 32gb,64gb etc, or will they be universal?
[Galaxy S6 General] JoeFCaputo113:
No sir, storage capacity doesn't matter, they will still be the same phone/software/hardware.

Now my question is will S6 and S6 Edge ROMs/Kernels/Mods be compatible with each other?!
[Xperia Z3 Q&A, Help & Troubleshooting] rafhagunz:
AWAITING !!!!!!!!! :D :D

http://www.phonearena.com/news/Sony...rmware-approved-by-the-Wi-Fi-Alliance_id66147
[Xperia Z3 Q&A, Help & Troubleshooting] abhinav.tella:
I suppose they may be able to keep their Feb promise.
[Xperia Z3 Q&A, Help & Troubleshooting] rafhagunz:
i believe it!
[Xperia Z3 Q&A, Help & Troubleshooting] woozydevotee:
I would advice everyone to wait for the initial reviews before jumping on the Lollipop bandwagon, as Lollipops performance has been a mixed bag upill now, there have been some improvements with the 5.1, however I hope Sony does its homework well before pushing the update.
[Desire 816 Q&A, Help & Troubleshooting] rameramwe:
i've been having touch problems ... the phone just goes crazy and presses random stuff very fast and then calms down and after a minute goes crazy again and i have to press the buttons like three times for them to respond .

and i can't press the u letter on the keyboard unless i rotate the device .

i am rooted and unlocked so i did a full wipe (dalvik system cache data ) then downloaded a fresh nandroid backup and restored it from here : http://xdaforums.com/desire-816/general/fresh-htc-desire-816-a5dug-dual-sim-t3030958

now the u letter problem is solved after i did this but the random pressing and lag is still there .

this wasn't my first restore i tried cm12 and like 4 other backups .

now i'm starting to consider that my digitizer is broken .... is it ??????

my phone info :

Device Online Reading Info

Model : HTC Desire 816 dual sim

Version : 4.4.2

Build : 372006.1

Imei : *******66119732

Platform : msm8226

Checking Root Wait : False

Device Online Reading Info

MODEL : HTC DESIRE 816 DUAL SIM

NAME : HTC_A5DUG

HBOOT : 3.19.0.0000

SERIAL : FA4BDWW05151

CID : HTC__J15

MID : 0P9C70000

BUILD : 1.56.401.1

ANDROID : 4.4.2

IMEI : *******66119732

Checking Root Wait : False
[Desire 816 Q&A, Help & Troubleshooting] seekfind:
have you ever tried to update to the latest stock ROM (1.58.401)? it is known to fix touch issues among other things. it's an official OTA
[Desire 816 Q&A, Help & Troubleshooting] rameramwe:
Thanks a lot for the reply sir .

i will try it and tell you if it works .

i tried it before but when it tries to update the recovery opens up soi locked the bootloader but the recovery still tries to open ... meaning the ota isn't updating it's going to the recovery (cwm) instead ... you know why ????
[Desire 816 Q&A, Help & Troubleshooting] seekfind:
yup, you need to flash the stock recovery before locking the bootloader, also you need to unroot using SuperSU's unroot option
[Moto G Q&A, Help & Troubleshooting] MotoG4Me:
I've been reading forums on here all day and nothing seems to match my problem down to the letter.

Here is my problem, I thought this morning it would be fun to upgrade my Moto G, was rooted on Kit Kat (perfectly fine -_-) to Lollipop. I followed a tutorial with great feedback and thought what could go wrong? Turns out everything could go wrong and after following every step perfect, my phone was bricked. It just displayed the Warning: Bootloader Unlocked screen and does nothing else.

I'm able to get in to recovery, have all the ADB tools installed, tried every tutorial, non-stop, the entire day and nothing is working.

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img_sparsechunk.0

mfastboot flash system system.img_sparsechunk.1

mfastboot flash system system.img_sparsechunk.2

mfastboot flash modem NON-HLOS.bin

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash fsg fsg.mbn

mfastboot erase cache

mfastboot erase userdata

mfastboot reboot

When I type almost any of these commands I'm met with this: "error: cannot load 'gpt.bin': No error" not just for gpt.bin though, for anything? :rolleyes: Althought these commands worked fine when bricking my phone :rolleyes:

My phone is a single sim XT1032 Moto G. Can someone please help? I just want my phone fixed. I don't care if I never have to have Lollipop on it, it was fine the way it was and wish I'd just left it that way.
[Moto G Q&A, Help & Troubleshooting] audit13:
What lollipop ROM are you trying to flash? The gpe ROM uses a slightly different file format than a retail lollipop ROM.
[XDA Assist] jasondutch:
Hello,

Can anyone give me a download link for v6.0.5.0 version of clockworkmod recovery? (s3)

Because i want to install android 5.0.2 on my sister her S3
[XDA Assist] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. Exactly which version of the S3 are we talking about?
[XDA Assist] Anoop C:
Can you anyone help me with a new custom rom for my Iball 3G 7803Q-900 :)
[Xposed General] padhu1989:
Everyone ecxited about xposed framework released for lollipop.. But there are many facing problems installing framework because of SELinux set to enforce by default.

You can check you Selinux status in settings - About phone

You can set the SELinux to Permissive temporarily by running the bellow two commands in Terminal emulator

su

setenforce 0

But it SElinux will change to default once you hard reboot your phone.. In order to keep it in permissive, you need to soft reboot always whenever reboot needed and it's quite annoying..

So I found a workaround to Set the SELinux to permissive on boot itself.

For this you need to have init.d support.. If you don't have just install it via universal init.d tool available in xda.. (just do a search, u will get it) install universal init.d and activate init.d..

Then go to /etc/init.d directory, create a file and rename it as "08setperm" (without quotes) and add the below lines in the file and save it..

#!/system/sh

setenforce 0

And give full permission (rwxrwxrwx) .. Use root Explorer to edit and give permissions..

Now hard reboot your phone and you can see SELinux is set to "permissive" on boot itself..

Now install Xposed framework by following the steps mentioned in the official xposed thread..

This method is tested in moto G and working fine for me... I'm not responsible for anything if happened with your mobile after trying this..

Ps: if you flash any new nightly or new rom, you need to add the file in to init.d directory again..

I posted this using my mobile. So pardon me if any formatting issues..

Hit thanks if i helped you..
[Xposed General] ldeveraux:
Very obviously, can't set permissive on Galaxy S5. Hopefully soon though.
[Xposed General] LGtMgG2t:
Thanks, I was looking for the enforce command to make a script. It worked perfectly for me on an S4.
[Xposed General] padhu1989:
Press thanks button dude instead of saying it..
[Xposed General] Zwulf:
Doesn't work on Z3 Compact (D5803) CM12 nightly.
[Xposed General] Scriptkiddie7:
Nexus 6

"Alright So i have everything down according to your installation guide, When i want to set the file "08setperm" is when root browser tells me that the operation failed even though it has SU Granted."

Okay so I did some tinkering, Got it to work Reboot but after the 2nd Reboot it Boot-looped, On my Nexus But it can work .
[Xposed General] padhu1989:
Upgrade your root Explorer or super Su and try
[Xposed General] aalupatti:
Using the commands below should get permissive even after reboot

per http://xdaforums.com/showpost.php?p=58887725&postcount=230

su

mount -o remount,rw /system

mkdir /system/su.d

echo "#!/system/bin/sh" > /system/su.d/permissive.sh

echo "echo 0 > /sys/fs/selinux/enforce" >> /system/su.d/permissive.sh

chmod 755 > /system/su.d/permissive.sh
[Xposed General] mattdm:
Which part didn't work? As far as I can tell, we don't have init.d support on the Z3 Compact yet. Was it the Universal init.d Tool that didn't work for you?
[Xposed General] was12:
CM has init.d support buddy.
[Xposed General] Zwulf:
Doesn't work this way. You should have read following posts.

Solution:

Works!

Finally got a permissive system on reboot.

Edit: Doesn't help to get XPosed working on my Z3C though. :(
[Xposed General] C2fifield:
Another z3c here on the latest nightly, none of these methods even give me permissive status on boot...

EDIT: I lied I just had to install SuperSu
[Xposed General] JSIN3L33T:
This method worked for me also thank you sir :good:;):cowboy:
[Xposed General] DualJoe:
Just dd the kernel partition and hex-edit the kernel command line (androidboot.selinux=permissive).
[Xposed General] manu44:
So i am using Xperia Z2 with CM12.

Now, the issue with this particular CM12 is that, in case if we do a soft reboot then xposed starts working but networks vanishes. The Network comes back upon a normal restart but with soft reboot the issue comes back.

I have used these steps to

su

mount -o remount,rw /system

mkdir /system/su.d

echo "#!/system/bin/sh" > /system/su.d/permissive.sh

echo "setenforce 0" > /system/su.d/permissive.sh

echo "0" > /sys/fs/selinux/enforce

chmod 755 /system/su.d/permissive.sh

Make permissive survive a normal reboot but it doesnt work till i do a soft reboot. any help?
[Xposed General] themightydeity:
Exact same issue for me

I have same phone with CM12, when I soft reboot

1st soft reboot: no network

2nd soft reboot: screen goes black after unlocking the device

in last 2 days of multiple soft reboots, i got one soft reboot where xposed and network everything worked.
[Xposed General] Vij4k:
Ok, so..

I want script who started on boot(set permissive), because i do not have soft reboot after every normal reboot to working Xposed. How to do it? I have CM12 Nightly on Xperia Z1.

If i wrote in terminal this script:

It's work on every boot phone or once?
[Xposed General] Alexey71:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh

Work cm12. No need soft reboot:good::good:
[Xposed General] Vij4k:
@UP:

Only wrote this in Terminal and all is it?
[Xposed General] Alexey71:
SuperSu + android terminal or adb shell
[Xposed General] EzioStrong:
Hi.

M SELinux Status is Disable and i wanna active it, How can i do that ??

*I'm running CM12.1 On SM-G7102

Thanks
[Xposed General] celoxocis:
what is the advantage in setting the selinux to permissive mode on boot?

would that allow me to install apps placed into "priv-apps" on stock to be installed?

because I'm trying that and on reboot they are simply being ignored. would selinux on boot let me install those apps?
[Xposed General] preetfzr:
Now i am able to fix this driver installaition problem. Thanks [MENTION=4707513]padhu1989[/MENTION]
[Xposed General] Androdiver:
Thanks bro its work for me
[Xposed General] krasCGQ:
The developer might disable SELinux if policies aren't perfect yet. Enabling SELinux at this condition would cause issues...
[Xposed General] Yamaha169:
failed odin flash after hexedit

I got the hex edit down, the saving the file, the md5 check passed..... but I still cant flash .... wtf.... grr

---------- Post added at 02:18 AM ---------- Previous post was at 02:16 AM ----------

[/COLOR]

ive added init.d support to my device and tried to boot permissive with a selinux script... but I found I need to change the selinux permissive inside the kernel... which I can't do due to locked bootloader...

So for now till I can sell this Jimmy Crack corn phone... and get me the international G928C...

Those of you looking for reboot options for devices with selinux enforced and supersu stopping boot...

INSIDE ADB terminal (If your lost here, look up adb)

COMMANDS:

ADB root

ADB shell

Setenforce 0

Exit

The frozen att logo should go away and allow boot while being rooted...

Looking for experienced kernel editor that can create a stock modified kernel with selinux permissive and adb root access...
[Xposed General] hereandthere:
I have some scripts in init.d folder already. Each of them start the line with

#!/system/bin/sh

Instead of

#!/system/sh

I checked that the first file is exist but the other is not. So I use the first.

And for permission I set it up as 755 as other files' permission not 777.

It works also just fine after reboot.

Thanks for the tutorial.
[Xposed General] mobidea:
I use Tasker shell command on boot. It works great

Wysłane z mojego m8 przy użyciu Tapatalka
[Xposed General] thegameksk:
Can this be used on a rooted T-mobile Galaxy S 7?
[Xposed General] boroboy69r:
Not working on HTC m9 cm13.
[Xposed General] AnonVendetta:
Can someone possibly help me out with editing my boot.img? I'm running unofficial CM13 on Galaxy Tab 10.1 (GT-N8013). I don't want to use a script, I would rather have Selinux permanently set to permissive. My reason being, I don't like using the systemless versions of SuperSU/Xposed, I like to install them directly into /system. But if I flash System Mode SuperSU my device won't boot. I tried following the hex editing instructions, the modded img flashes successfully in TWRP, device still boots, but Selinux is always enforcing.

Thanks!
[Xposed General] krasCGQ:
You need some knowledge on git and compiling. If I become you, I would instead use an init.d script.
[Xposed General] Hyoretsu:
I did this and whenever I boot my device, SELinux is set to Enforcing. Already tried SELinuxModeChanger
[Xposed General] krasCGQ:
Are you using a Samsung device?
[Xposed General] ldeveraux:
I am, same problem. I assumed stock Samsung kernels can't be set permissive?
[Xposed General] krasCGQ:
Samsung stock kernels are compiled with SELinux is forced enforcing and couldn't be set permissive nor be disabled.

If you're brave enough, you could compile a kernel with disabled flag...
[Xposed General] ldeveraux:
I've flashed many kernels (I'm on PB1 semi-stock) but the kernel never sticks for some reason. I don't know how to fix it...:confused:
[Xposed General] krasCGQ:
Your device?
[Xposed General] ldeveraux:
Sorry, forgot what forum I was in :) Verizon S5.
[Xposed General] downslayer:
If you have macrodroid and the secure settings plugin, you can also set enforcing by using the 2 commands in OP in a run command (in Actions in secure settings). I set it with the trigger "device boot".

In case you don't want to scroll up to the OP, it's

su

setenforce 0
[Xposed General] thodibhen:
Just curious, why not? Systemless mods are the best thing to happen to Android for a long long time.... Much cleaner method & keeps your /system partition "vanilla"

I have root, xposed, android pay, OTAs, SELinux enforcing, etc. all working without any issues, all thanks to systemless mods

:confused:
[Xposed General] AnonVendetta:
[MENTION=7090699]thodibhen[/MENTION]: Because I am used to the old way of doing things, is why. I prefer to be permanently rooted/Xposed.I dont care about Android Pay, Pokemon Go, etc. I also have some rooted apps that dont work in systemless mode (they say I'm not rooted). I have other apps that dont work right if Selinux is enforcing. Setting to permissive in kernel is best (instead of with a script/app), since it's set it and forget it, and permanent (unless you flash a new kernel). Google took a concept originally developef by NSA and adopted it for Android. Not exactly the best people to be modelling security after.
[Xposed General] thodibhen:
To each their own! Best part about Android.

However, it would just suck if more devs started utilizing Safetynet in their apps, since it's one very easily accessible API..... I must be lucky, haven't ran into any apps that cry about SELinux; since security patches for Android leave much much to be desired, and probably(definitely) won't be improved anytime(or ever) in the future, I just see SELinux as an extra security barrier, even if it's not 100% perfect(nothing is).

I hear ya though, i'm also not a fan of change....waited until Magisk v6 before making the jump.

Happy hacking :D
[Xposed General] xXCoolGuYXx:
Is there a way to change selinux on idol 3 on android mm 6.0.1
[Xposed General] xXCoolGuYXx:
I get this when I us the app and I have root
[Xposed General] DaweisCZ:
Thanks a LOT working for me as well
[Xposed General] XDM inc:
I get the same thing
[Xposed General] xXCoolGuYXx:
I fixed it and how I fix it is that I flash cm13 then enabled root and then flash root and it work I'm on android 6.0.1
[Xposed General] XDM inc:
any way to not flash cm? i love stock miui weekly. what i have to do for now is keep opening terminal and running the command every launch.
[Xposed General] xXCoolGuYXx:
Which device ?
[Xposed General] XDM inc:
Xiaomi Redmi 3s unlocked bootloader and rooted

Android 6.0.1
[Xposed General] xXCoolGuYXx:
http://en.miui.com/thread-298586-1-1.html

http://www.rootupdate.com/2016/08/root-xiaomi-redmi-3s-prime-without-computer.html?m=1

Then just open SuperSU and let it install the brain and then don't let it reboot for you, when it asked to reboot close the app then you reboot yourself then boot back up then open play store and update the SuperSU app, then install the brain and do the same and it should work .
[Xposed General] Sanfin99:
For setting up Selinux to Permissive mode automatically after boot for non rooted phones and phones with no init.d support, there is an app called "init.d script support" in play store, which can execute any .sh script and from any folder in sd card.

I am using to set my Selinux change and works awesome, check out guys.
[Xposed General] XDM inc:
But I'm using systemless root so isn't the command

#!/system/bin/sh

Deprecated?

Doesn't work for me, I don't even have that folder

edit: i have installed a system version of superuser and changed #!/system/bin/sh to #!/system/xbin/sh (where theirs a su file in there) adn still dosent work.

the ini.d seems to be working because in the data partition theirs a selinux.log but its still enforcing.
[Xposed General] XDM inc:
also every check seems to work and init.d is working but it seems that it can do everything but change the selinux status. in my data partition i can see the test .log and the selinux.log but it doesn't actually change the status. i still have to use the app to change the status.
[Xposed General] lebaud07:
If you are using the Magisk version of SU (phh SuperUser), create the "permissive.sh" file in /magisk/phh/su.d/
[Xposed General] MBAHPOMADE:
i found the solution for goodix fingerprint in the miui rom can't add the fingerprint, it because the selinux problems, the default of this kernel is set to enforcing, you should set to permissive to fix that,

try to open the terminal emulator and type :

> su

> setenforce 0

and after that go to fingerprint options, and try to add fingerprint, and voila!

to developers : please make the installer of kernel to make the selinux permissions to permissive, ???
[Xposed General] SuperlativeB:
what do you mean Add the lines? do you mean in the name section of the file ?

Never mind I figure it out .
[Xposed General] aviatorhh:
BTW, any news on the camera issue?

Anyone interested in nightly LOS 14.1 himaul builds? I am doing some successful but still no camera working :-/
[Xposed General] SafiXS:
Dafuq, xposed and camera ?

Wrong section dude haha

Gesendet von meinem HTC One M9 mit Tapatalk
[Xposed General] *sigh*:
no work

samsung galaxy note 5 (sm-n920i)

Tried putting the script in and nothing happends when i hard reboot

In my settings it says

Se for androod status

Enforcing

SEPF_SECMOBILE_6.0.1_0029

Wed Dec 07 17:04:32 2016

Also in my init.d folder has 08setperm file already

#set correct permissions to /system/etc/init.d folder

mount -o remount,rw -t auto /system

chmod -R 777 /system/etc/init.d

mount -o remount,ro -t auto /system

I need help asap