Related
I was wondering if anyone knows why I my tablet won't root, does the paranoid android rom have a special root file, cause I tried with my regular root file and it says before I reboot that the root needs to be fix, why is that?
does anyone know how to solve this problem? pm me on [email protected]
alexjojo946 said:
does anyone know how to solve this problem? pm me on [email protected]
Click to expand...
Click to collapse
This room has a built-in superuser so yes, it's rooted. But since the superuser is built-in you won't see any superuser app. If you don't like it then you can disable it and use any superuser app, otherwise don't bother cuz it works anyway...
unclefab said:
This room has a built-in superuser so yes, it's rooted. But since the superuser is built-in you won't see any superuser app. If you don't like it then you can disable it and use any superuser app, otherwise don't bother cuz it works anyway...
Click to expand...
Click to collapse
yeah but i installed apps like titanium backup, no frills cpu, game boosters and I can't start them cause it says i need to check if my rom is rooted i tried to disable superuser in app manager and tried installing my own version, still nothing happens
alexjojo946 said:
yeah but i installed apps like titanium backup, no frills cpu, game boosters and I can't start them cause it says i need to check if my rom is rooted i tried to disable superuser in app manager and tried installing my own version, still nothing happens
Click to expand...
Click to collapse
First, install your own superuser, but don't disable the built-in one. Launch your superuser, let him update its binaries if needed, and let him get superuser permissions from the built-in superuser.
Here you go, now you can disable the built-in superuser and use your one.
I did it this way and it worked, so it should be the same for you.
But for now if your superusers are messed just flash again the rom, wipe dalvik and cache and start fresh.
Good luck!
unclefab said:
First, install your own superuser, but don't disable the built-in one. Launch your superuser, let him update its binaries if needed, and let him get superuser permissions from the built-in superuser.
Here you go, now you can disable the built-in superuser and use your one.
I did it this way and it worked, so it should be the same for you.
But for now if your superusers are messed just flash again the rom, wipe dalvik and cache and start fresh.
Good luck!
Click to expand...
Click to collapse
I just cleared everything and flashed again, i'm gonna try and do what u told me, hope this works
alexjojo946 said:
I just cleared everything and flashed again, i'm gonna try and do what u told me, hope this works
Click to expand...
Click to collapse
Its working, i updated the rom superuser and fixed system xbin su pathway, thanks for the help man ))
please give me a link too the rom... i want to flash that...
Sent from my GT-P6200 using Tapatalk HD
ali.cheeta said:
please give me a link too the rom... i want to flash that...
Sent from my GT-P6200 using Tapatalk HD
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2221328
its not that hard to find it...
Anyone have tried reducing DPI on our device? Any disadvantages of this operation? Like screwed up icons or something?
Sent from my HTC One SV powered by Saturn III.
Have you tried xposed & appsettings?
I've just noticed the thread about it (XDA App haven't shown it to me or may I missed it). Will do a try, I only hope I won't make a mistake anywhere.
Bazdir said:
I've just noticed the thread about it (XDA App haven't shown it to me or may I missed it). Will do a try, I only hope I won't make a mistake anywhere.
Click to expand...
Click to collapse
I use xposed an appsettings without any problem.
With the other solution (to change dpi in build.prop) you will have the problem that several apps seem to be incompatible and Play Store won't update these "incompatible" apps any longer.
Sylvia said:
I use xposed an appsettings without any problem.
With the other solution (to change dpi in build.prop) you will have the problem that several apps seem to be incompatible and Play Store won't update these "incompatible" apps any longer.
Click to expand...
Click to collapse
So... Setting 217 DPI will cause problems with updating apps such as jakdojade.pl or something like that? God damn it, I hoped, I would have a bit smaller interface like One S has.
And thanks for the feedback.
Bazdir said:
So... Setting 217 DPI will cause problems with updating apps such as jakdojade.pl or something like that? God damn it, I hoped, I would have a bit smaller interface like One S has.
And thanks for the feedback.
Click to expand...
Click to collapse
Personally, I had no update issues in reducing the dpi to 217 in build.prop
The only problem is that some apps will look glitchy (sense interface, torch), for them you'll need to set dpi back to 240, using something like appsettings for xposed framework
madpausa said:
Personally, I had no update issues in reducing the dpi to 217 in build.prop
The only problem is that some apps will look glitchy (sense interface, torch), for them you'll need to set dpi back to 240, using something like appsettings for xposed framework
Click to expand...
Click to collapse
Good. I've tried installing Xposed Framework to get Appsettings module, but then I've been spammed with illegal information. Do I have to install busybox? Or may I just forgot to set system rw in ES File Explorer... I just realised that might be the solution.
EDIT: Well... That haven't worked either. Only app_process have been patched. If I will push xposedbridge by myself, then it should work?
EDIT2: Okay, that haven't changed anything.. Any idea?
Sent from my HTC One SV powered by Saturn III.
Bazdir said:
Good. I've tried installing Xposed Framework to get Appsettings module, but then I've been spammed with illegal information. Do I have to install busybox? Or may I just forgot to set system rw in ES File Explorer... I just realised that might be the solution.
EDIT: Well... That haven't worked either. Only app_process have been patched. If I will push xposedbridge by myself, then it should work?
EDIT2: Okay, that haven't changed anything.. Any idea?
Sent from my HTC One SV powered by Saturn III.
Click to expand...
Click to collapse
Flash back stock boot.img with fastboot, install xposed, flash back the kernel/boot.img you used before.
old.splatterhand said:
Flash back stock boot.img with fastboot, install xposed, flash back the kernel/boot.img you used before.
Click to expand...
Click to collapse
I was wondering, if it wasn't caused by non-stock kernel. Then you picked up the idea here in this thread. And it worked. Thanks!
Bazdir said:
I was wondering, if it wasn't caused by non-stock kernel. Then you picked up the idea here in this thread. And it worked. Thanks!
Click to expand...
Click to collapse
I had the same problem
I'm bumping up this thread again, because I tried to take a DPI one step lower, so it means - 216 DPI. I have to tell, that the interface looks much better than it was on 217. The notification icons are sharper and all the icons and texts are sharper too. I really recommend to try it.
(I didn't want to make a new thread, so I posted it here.)
I find 216 still too large for my liking. I've been running 200 for a while without any issues. It's a good balance.
I am also using the multi-dpi version of google play so no probs there either.
The ONLY minor issue is that it cuts off the bottom of the 'Recent Apps' (the part showing the app name) which isn't a big deal for me at all as I can see what the app is anyway.
Hello,
I was previously on stock 5.0 with ElementalX kernel and SuperSU. I updated to 5.0.1 using TWRP, and everything is working good. I then tried to use BuildProp Editor to change lcd density like usual to 440 or 400, but when I hit apply, and reboot it is back at 480. I don't have computer to try adb route, but any ideas?
CptanPanic said:
Hello,
I was previously on stock 5.0 with ElementalX kernel and SuperSU. I updated to 5.0.1 using TWRP, and everything is working good. I then tried to use BuildProp Editor to change lcd density like usual to 440 or 400, but when I hit apply, and reboot it is back at 480. I don't have computer to try adb route, but any ideas?
Click to expand...
Click to collapse
Just open build.prop with a text editor or file browser/manager and edit the line lol
Lethargy said:
Just open build.prop with a text editor or file browser/manager and edit the line lol
Click to expand...
Click to collapse
Doh, yes this worked. Thanks.
Hi!
I'm rooted but whatever I set for DPI settings it doesn't seem to matter. I tried apps and directly editing the build.prop, no difference?
tbatliner said:
Hi!
I'm rooted but whatever I set for DPI settings it doesn't seem to matter. I tried apps and directly editing the build.prop, no difference?
Click to expand...
Click to collapse
add qemu.sf.lcd_density=320 or whatever dpi you want into the build.prop then restart
Thank you! ☺
As a few days frustration and zillion tries are behind me let me explain proper instalation of this sound engine. Just to notice that you DON'T need permissive kernel for that because I installed it on my stock German ROM and now works in French Orange ROM G935FXXU1APBF as well !
INSTALLATION PROCEDURE ON CLEAN STOCK ROM :
At first...
You need to DELETE not to freeze sound alive and adapt sound.
In build.prop find the lines or add them as follows ;
Ipa.decode=false
tunnel.decode=false
lpa.use-stagefright=false.
.
1.You need to root your SM-G935F device with newest SuperSU by ChainFire located here.So, download and flash TWRP recovery from here and flash SuperSU.Wipe dalvik,wipe cache, then Restart your device.
2.From Playstore download and install latest STERICSON BUSYBOX. Install busybox in default su/xbin and give root permission.Restart your device again.
3. Download from official page Viper4android version 2.4.0.1 from HERE
4. Using Root explorer copy Viper4Android in folder PRIV-APP and give it permission 0644 rw-r--r-- (see attached image)
5.Restart your device
6. Open V4A and install driver when it asks...don't exit app or DON'T TOUCH anything else, just Restart your device.
7. Open V4A and go to Settings - UI Setting - Expert Mode
8. In some occasions V4A will ask for new driver installation...Install again and restart device.
9. Use your V4A wisely !
IMPORTAINT NOTIFICATION !
If you previously messed up with V4A or rooting,I recommend fresh ROM installation from scratch.
If V4A constantly offers to install driver, it means you did not properly rooted your device !
VIPER4ANDROID IS NOT WORKING ON STOCK PLAYER !
That's all.If you didn't read post carefuly, there is no any support else, because it is not needed.
Followed your guide, didn't ask to install a new driver after step 8 and viper is not working any suggestions?
Bernard23 said:
Followed your guide, didn't ask to install a new driver after step 8 and viper is not working any suggestions?
Click to expand...
Click to collapse
In some cases it doesn't ask for another driver installation after entering expert mode.Did you try another player?
If you don't used it on clean rom then it could be anything.
I've not needed to do half of this.
riso123 said:
I've not needed to do half of this.
Click to expand...
Click to collapse
How come ?
BusyBox Location is Su/xbin or System/xbin ?
JazonX said:
BusyBox Location is Su/xbin or System/xbin ?
Click to expand...
Click to collapse
Did you read thread ? I mentioned above that busybox is in /su/xbin/
tin2404 said:
Did you read thread ? I mentioned above that busybox is in /su/xbin/
Click to expand...
Click to collapse
I read and hence the question, because usually since MM - Busybox is installed to System/xbin by default.
Nevermind, Gonna try that as well now. Thanks!
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
barbik said:
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
Click to expand...
Click to collapse
dude that's zip work flawlessly :good:
tin2404 said:
How come ?
Click to expand...
Click to collapse
Because I simply download the latest APK and install it as a normal app rather than copy across and setting permissions.
I then download and flash the ZIP from the below site:
http://androiding.how/how-to-fix-viper4android-selinux-policy-issues-on-lollipop/
After that I installed the driver, rebooted and all was good.
I was the first\one of the first, to flash v4a on our device.
I've already created a tutorial thread for this in the guide section. People might find it easier, no need to make adjustments to build.prop for example, it's automatic.
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
Beefheart said:
I've already created a tutorial thread for this in the guide section. People might find it easier, no need to make adjustments to build.prop for example, it's automatic.
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
Click to expand...
Click to collapse
Exactly what I was thinking...
Beefheart said:
I've already created a tutorial thread for this in the guide section. People might find it easier, no need to make adjustments to build.prop for example, it's automatic.
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
Click to expand...
Click to collapse
Amazing recommendation on the flat icons xposed module. Loving the custom status bar icons [emoji106]
Sent from my SM-G935W8 using Tapatalk
barbik said:
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
Click to expand...
Click to collapse
Thank you so much for this barbik!
I've literally spent the best part of a day trying to get this to work. Followed various guides posted here but only your link applied V4A system wide rather than just for GoneMAD.
If anyone else is having issues, uninstall the driver and the app, reboot into twrp and flash this zip instead.
Thanks again you saved me a few grey hairs!
SirBarnz said:
Thank you so much for this barbik!
I've literally spent the best part of a day trying to get this to work. Followed various guides posted here but only your link applied V4A system wide rather than just for GoneMAD.
If anyone else is having issues, uninstall the driver and the app, reboot into twrp and flash this zip instead.
Thanks again you saved me a few grey hairs!
Click to expand...
Click to collapse
I agree, that zip helped me as well after a few failed attempts Now it works perfectly and Spotify sound amazing!
barbik said:
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
Click to expand...
Click to collapse
Hi, flashed, works! Super! Thanks. One question: what is that clock??? app inside zip for? Is it necessary? That's strange surprise... It's located in system/app/com.cyanogenmod.lockclock-1, please explain. Thank you.
N4 powered by Echoe™
FRM300 said:
Hi, flashed, works! Super! Thanks. One question: what is that clock??? app inside zip for? Is it necessary? That's strange surprise... It's located in system/app/com.cyanogenmod.lockclock-1, please explain. Thank you.
N4 powered by Echoe™
Click to expand...
Click to collapse
+1
What's that Clock APK ?
JazonX said:
+1
What's that Clock APK ?
Click to expand...
Click to collapse
his is a clock widget ... they are not needed, they can be removed
Mine works perfectly fine with just freezing those two Samsung apps...
Sent from my SM-G935F using Tapatalk