Related
I have been following the Threads since I got my G1 for about 3 weeks now. Two days after receiving it I got the OTA update from T-Mobile before I knew it I was on RC30. After DREAMIMG.nbh and very careful reading I was able to downgrade to RC29, Root - Telnetd, and install RC30 Mod JFv1.2 then JFv1.3. Finally I installed Bootloader and got the skateboarding androids.
After a couple days of reading, I took the plunge. Let me be the first to say that as a Windows XP user, alot of this information is very confusing as I am used to a Dos type system, and all of these commands made it seem a bit more confusing than it really is.
Now that I have root and bootloader I would like to start to change the boot screen and try my hand at some Linux based stuff?
Being that I use Windows XP, it is my understanding that I can run Linux using Slax? I am very computer literate, but haven't tried my hand at programming since the days of Dos and Paschal. Are their any online tutorials that somone would recommend as a starter or is the Android Software so different that it may be better to start from scratch?
Willing to learn any pointers would be appreciated.
I may be misunderstanding you but if your looking to make any modifications to the operating system itself (which is definitely needed), I would suggest having a look at the Android source code at http://android.git.kernel.org. The back-end of the platform (kernel, etc) is all written in C. The userland stuff is written in Google's implementation of Java called Dalvik. Now that you have the dev bootloader, all you really have to do is clone the official android repository, make your changes, build and flash to the device using fastboot.
Thanx Datruesurfer
After all the reading it seemed alot of work was being done in Linux but I don't know anything about that so, I could be completely off base.
At your suggestion I looked at android.git.kernal and it seems they do a good job at explaining some things, but it still makes many references to Linux and Unix.
Would programming of Git be done in linux. I see that Git is gotten using .tar files which is Linux compressed files? So is it best to try to do programming using slax or ubuntu?
Also, are things like the boot screen modified using Linux based .png or can that be done in Windows?
Let me say sorry in advanced, as I am doing this for the first time, please say stop if I am being too n00bish.
Also...I noticed ....
that the commands given in the Git User's Manual look very familiar like the commands that were given while I was reverting my RC30 back to RC29 using the Pterminal/Telnet. Can this programming with Git be done off of the G1 Phone itself?
You're in over your head dude. If you haven't programmed in these object oriented based programming methods and you know nothing of linux, then recompiling the android source like the above poster suggested is too much.
I don't mean to dissapoint or negatively comment, but really save yourself the trouble.
If you really want to though, figure out the basics of C and java programming and start reading the source.
Brutal-Force said:
After all the reading it seemed alot of work was being done in Linux but I don't know anything about that so, I could be completely off base.
At your suggestion I looked at android.git.kernal and it seems they do a good job at explaining some things, but it still makes many references to Linux and Unix.
Would programming of Git be done in linux. I see that Git is gotten using .tar files which is Linux compressed files? So is it best to try to do programming using slax or ubuntu?
Also, are things like the boot screen modified using Linux based .png or can that be done in Windows?
Let me say sorry in advanced, as I am doing this for the first time, please say stop if I am being too n00bish.
Click to expand...
Click to collapse
A Few things...
1. Android and Git are two completely different products. Git is the revision control system used by Android. Whenever one of the developers at Google makes a change to the source code they will upload it to the repository. Then people can go revision by revision to see where modifications have been made and suggest their own if they wish.
2. The part where a Linux box would be handy is actually downloading all of the files in the repository and compiling your own build. As dirr said, you probably should hold off on this until you have a better understanding of the platform itself.
3 As far as the boot image goes, the bootloader will only accept files that have been formatted specifically for it. Once you have the image formatted, you can flash it in the SPL via fastboot (the screen with the skating androids) I believe this can all be done via windows now.
4. I think I better understand where your coming from as far as modification. You should look at http://code.google.com/android to learn about how to code in Dalvik, as that will help you out much more then learning C. Once you have a good understanding of that, you can try to build from source
Hope that helps...
Thanx for the advice.
After reading about the above suggestions, it does seem that to do something simple would only be simple for someone who has all the background programming information of different platforms. This is probably why most tutorials/procedures are written so vaguely here. I appreciate the input and I will hold off and just read up on things other "more experienced" people write about here. I have a basic understanding of what is happening, but the "language" is so complex. Maybe in baby steps I will learn, since it appears that on this forum "Android" is fairly new. And while I am watching what is happening here, I will get java for dummies or bone up on Dalvik and start reading and practicing. Thanx for the help guys, and thans JF, Koush and all the other senior members for the RC30 Mod. At least I have the skateboarding Androis
I was wondering if there are any software that can open this file? Anyone knows? I was trying to open with ISOMagic but it can't.
It uses the yaffs2 filesystem so you might need to keep that in mind... Windows doesnt natively support it so you probably need to install something to add compatibility (but i havent found anything yet)
use the search button:
http://forum.xda-developers.com/showthread.php?t=443994
Sorry but i'm not a Linux user.......windows only
namsir said:
Sorry but i'm not a Linux user.......windows only
Click to expand...
Click to collapse
virtual linux machine and a lot of reading.... what do you want to do to the boot image? if you are not certain of the changes you are making you will break your phone
I would like to add the boot config xml file to the JF ADP 1.5 and try to make it start up with any gif images and mp3 boot sounds. I've seen haykuro's ADP builds and i would like to invent new boot structions to JF ADP 1.5 build , just hope so......i don't really care about breaking the phone
namsir said:
Sorry but i'm not a Linux user.......windows only
Click to expand...
Click to collapse
Like korndub said, running Linux in a virtual machine is a good option for doing some quick tweaking. I suggest VMware player combined with a premade Ubuntu appliance.
Hello everyone! My name is geeksunny and I am fairly new to the community. Been a lurker for a quite a while now but I finally have something to share!
BarebonesAndroid
What it is
What I have here is a Bash script to automate backing up your /system/app directory and then steps through a list of packages offering to remove them from your device. It runs on your Linux PC and uses ADB to interface with your device.
I wrote this for myself to automate the process of trimming my system down after I flash a new ROM. I recently bought a Nook Color and have been flashing CyanogenMod 7 nightlys to it pretty frequently. I also use a Motorola Droid phone and this comes in handy for the same reason on that device as well.
Seeing as how this was written with CyanogenMod 7 in mind, I am not sure how well it will work with other ROMs. I think it would work as it uses generic uninstall commands. It is based off of the packages that come in CM7 so those packages are the only ones considered by this script.
Note: I'm pretty rusty with my Bash scripting and kinda threw this together in my spare time. It may not be the prettiest script in the world but it gets the job done!
Requirements
To use this script you must...
- Be running a Linux/Unix based OS. (I use Ubuntu for my SDK machine. I don't have a Mac and do not know for sure if this will run on OSX.)
- Have ADB set up correctly and talking with your device.
- Have read/write access to your device's /system folder. (Be rooted.)
How to use it
Unzip and run ./BarebonesAndroid.sh in your terminal.
if ./BarebonesAndroid.sh is not executable, run this command:
Code:
chmod 775 BarebonesAndroid.sh
- It will first ask you to confirm that the device is connected and recognized by ADB.
- It will then ask if you want to back up your /system/app directory before removing any packages. If yes, you can specify a directory for the script to back them up to. It will default to ./apkBackup
- After this it will begin ask you one-by-one if you want to remove a given package. Enter Y or N for each package.
- When the script is finish it will reboot your device.
Future plans
I originally wrote this for myself but thought this could be useful to others out there. Right now the requirements aren't all that accessable to the average user (Linux OS with ADB set up). If there is a demand for it, I may write a Windows batch script version, or maybe convert it into a cross-platform command-line application. Let me know what you think of this idea!
I do have a book on Android development and my eventual goal is to turn this in to a native app!
Regarding the script...
- Add support for multiple devices. Right now it asks that you only have one device connected at a time. This is because I haven't had experience with multiple devices hooked up at once. I plan to fix that in the future.
- Add more error checking and failproofing.
- Streamline the experience. Make things a little more graceful than going through a set list one-by-one.
- Sort the apps. Perhaps add categories.
- Check installed packages and only offer to remove them if they are installed.
Thats it! Thanks for looking!
Thanks dude, good work!
https://github.com/JackpotClavin/Android-Blob-Utility
The purpose of this program is to help AOSP-based ROM developers quickly and easily find out which proprietary blobs need to be copied into the ROM's build, or built using source. How the program works is you do a /system dump into a folder on a Linux computer. Then you make the program using the 'make' command; then you can run it.
First off, the program will ask you what the sdk version of the /system dump you pulled happens to be. For example, if your /system dump is Android 4.3, and intend port a 4.3-based ROM, then enter 18 and press enter.
When it prompts you for location of the /system dump you pulled, if the location of the build.prop of the /system dump is under:
Code:
/home/user/backup/dump/system/build.prop
then just use:
Code:
/home/user/backup/dump/system
The program will now ask you for your device's manufacturer's name, and the device's name. For my Verizon LG G2, I entered "lge" and "vs980" respectively.
The utility then will ask you how many files you wish to run through the program. In the case of my LG G2, the KitKat build requires two main proprietary camera-related libraries to run (/system/bin/mm-qcamera-daemon and
/system/lib/hw/camera.msm8974.so).
So I typed in 2 and pressed enter (because I'm running two proprietary files through the program)
Then simply typed in:
Code:
/home/user/backup/dump/system/bin/mm-qcamera-daemon
and pressed enter and it printed out *every* file needed to get /system/bin/mm-qcamera-daemon running (the file might be proprietary, or it can be built from source).
Then it asked for the final proprietary file, so I simply typed in:
Code:
/home/user/backup/dump/system/lib/hw/camera.msm8974.so
and pressed enter and it printed out *every* file needed to get /system/lib/hw/camera.msm8974.so running (the file might be proprietary, or it can be built from source).
An example usage of this program can be found here: https://raw.githubusercontent.com/JackpotClavin/Android-Blob-Utility/master/Example_Usage.txt
That's 106 proprietary blobs done in a flash!
The beauty of this program is that it's recursive, so if proprietary file 'A' needs proprietary file 'B' to run, but proprietary file 'B' needs proprietary file 'C' to run, which in turn needs 'D' to run, then simply entering proprietary file A to run will print out all A, B, C, and D nicely formatted so that you can simply copy the output and place it in a file under vendor/manufacturer/codename/codename-vendor-blobs.mk file in your AOSP build source tree's root.
Another great thing about this program is that it doesn't just catch the libraries needed to satisfy the linker, but rather, it will also print out those libraries that are called within the actual code of the library itself, like:
Code:
dlopen("libfoo.so", RTLD_NOW);
libfoo.so is not marked as a shared library, so the linker won't complain that libfoo.so is missing, and there might be no sign that libfoo.so missing and needed, but when it's time for the daemon or library to run, it won't show any sign that something is wrong, until you see that it doesn't work. This program will catch and display that libfoo.so is needed.
So basically:
1. Extract /system dump image
2. Tell program the SDK version of your /system dump
3. Tell program the location of your /system dump
4. Tell the program your device's manufacturer's name
5. Tell the program your device's codename
6. Tell program how many files you wish to run through the utility
7. Tell program the location of the file(s) you wish to run through the program.
8. Copy the output of the utility to a text file under vendor/manufacturer/codename/codename-vendor-blobs.mk
reserve
Hi,
I'm a noob and don't worry about my silly question.
I'm trying to build my first cm-rom and tested your tool. Thanks a lot for your work, it worked for me.
I'm a little bit curios about your point 5. Where can I find all the files I need for my own source-tree/device?
It would be nice if you can give me a hint.
Thanks a lot and greetings from germany
Greetings from the US
Do you mean the device folder the ROM? You can look at similar devices to your device and see what they did and make the changes to build Android.
This is the device folder for the Nexus 5 -> https://android.googlesource.com/device/lge/hammerhead
This tool is under-recognized. I think it's a really great way to find which blobs are dependencies!
Codename13 said:
This tool is under-recognized. I think it's a really great way to find which blobs are dependencies!
Click to expand...
Click to collapse
Thanks! Are you developing a ROM? Let me know if it helps!
Sent from my LG-VS980 using XDA Free mobile app
Could this be updated to Lolipop?
2GigayteSD said:
Could this be updated to Lolipop?
Click to expand...
Click to collapse
What do you mean? I added support for SDK version 20 if that's what you're asking.
Sent from my LG-VS980 using XDA Free mobile app
Does that mean I can port AOSP to any device just by getting all the necessary blobs? I'm not sure but I'm trying to port Lollipop to my device but I don't really have a clue how to do it/what's needed to do it. Will this be useful for me? Thanks.
cikoleko said:
Does that mean I can port AOSP to any device just by getting all the necessary blobs? I'm not sure but I'm trying to port Lollipop to my device but I don't really have a clue how to do it/what's needed to do it. Will this be useful for me? Thanks.
Click to expand...
Click to collapse
It helps with making ROMs for devices that don't have support (either the model is brand new or the device never gained AOSP ROM support for whatever reason)
Basically, in the early stages of porting ROMs, certain things won't work (graphics, camera, radio) and this is mostly due to not having the correct proprietary files needed for the OS to interact with the hardware. The proprietary files have dependencies (they rely on other libraries, which in turn may rely on other libraries, and so on and so forth until all proprietary libraries are satisfied).
In the case of my LG G2, there were a total of 92 proprietary files that needed to be pushed to the device in order to get just camera working. Instead of pushing one library at a time and getting a logcat or strace dump of what the daemons are calling or depend on, I wrote this program to recursively search for all proprietary libraries needed to satisfy a proprietary library (or in the case of the camera for my G2, there were two proprietary libraries needed that required those said 90 other proprietary blobs).
So rather than pushing libraries, (then gathering logs and stracing) and hoping that the one you just pushed is the one that will get your camera, radio, etc to work, you run your known proprietary daemons or libraries through this program and it will print out the necessary libraries to get it working, in a fraction of a second
Can you go through the actual "porting" process because from what I understand you have done it? If I'm correct to port a ROM you need to have working ROM from other device? If yes, does that device have to be same manufacturer? Lets say I do have working AOSPA kitkat for my device so I need to get AOSPA lollipop and exchange the certain files and then I'll able to run it? Once again if it's like that then I use your tool and get necessary blobs? I don't have a clue about this stuff, I only build ROMs but now time has come that my device is unsupported so can you give me some tips, thanks.
This is interesting. Going to have to try this out tomorrow.
cikoleko said:
Can you go through the actual "porting" process because from what I understand you have done it? If I'm correct to port a ROM you need to have working ROM from other device? If yes, does that device have to be same manufacturer? Lets say I do have working AOSPA kitkat for my device so I need to get AOSPA lollipop and exchange the certain files and then I'll able to run it? Once again if it's like that then I use your tool and get necessary blobs? I don't have a clue about this stuff, I only build ROMs but now time has come that my device is unsupported so can you give me some tips, thanks.
Click to expand...
Click to collapse
If you don't have a clue then dont do it, please! Work your way up. First step in this hypothetical is to wait for aospa 5.0
Thanks a lot for this tool
just one thing.. i cant get the blobs for my wireless (wl12xx)
Rest all done
andynoob said:
Thanks a lot for this tool
just one thing.. i cant get the blobs for my wireless (wl12xx)
Rest all done
Click to expand...
Click to collapse
Is it possible that each wl12xx library only relies on AOSP libraries (has no dependencies?)
See if they can be built from source!
Sent from my LG-VS980 using XDA Free mobile app
JackpotClavin said:
Is it possible that each wl12xx library only relies on AOSP libraries (has no dependencies?)
See if they can be built from source!
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Manufacturer hasnt provided the source code(Kernel) . Anyways thanks a lot for this tool :good: :good:
how to use it?
by reading the detailed instructions?
Sent from my LG-VS980 using XDA Free mobile app
JackpotClavin said:
by reading the detailed instructions?
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
should we adb pull /system first?
*edit
I did it! but where is the directory out?
J,
You are a life saver ! Subscribed. Will add link of thread to my signature. Will dance happily for some hours! :good:
Will seek therapy. :silly:
m
Hi. Has anyone had success with running Linux Deploy in Framebuffer mode on the P900?
Closest I have gotten is with a VT enabled (but WIP) kernel for CM11. I saw the debian desktop flicker on for a second and then all goes black!
Other than that, all my attempts have resulted in a black screen, no backlight.
Ideally, I think I want Linux (deb, ubuntu, something) running on this tablet. I think because of its screen size and powerful spec it would make a very decent laptop replacement, but I feel that the android OS is not designed for this task.
EDIT: I now have debian running using framebuffer on the p900!
notspike said:
I now have debian running using framebuffer on the p900!
Click to expand...
Click to collapse
Is there anyway you would share this in the developer thread, or is it still to early?
I would love to be able to use this option under the MultiROM. If it works on the P-900, it should be possible to have it work under the T-900 as well.
arcadia2uk said:
Is there anyway you would share this in the developer thread, or is it still to early?
I would love to be able to use this option under the MultiROM. If it works on the P-900, it should be possible to have it work under the T-900 as well.
Click to expand...
Click to collapse
Hi acardia, since this message I've gotten P900 to run ubuntu and debian. Unfortuantely there is difficulty with making the touchscreen function correctly - I have the digitizer and spen working though.
I'd like to know what is the utility of using the framebuffer. I use VNC and it's very fluid and functional
What are settings you used to use frambuffer in linux deploy ?
should I use the VT kernel ?
Do you get to use the camera (with VLC for example)?
spen working in framebuffer, USB keyboard working
touchscreen detected, but calibration not complete yet
Hi evereybody!
I have a SM-P905, rooted.
I try to install linux on my device and i got this message (view photo)
After i search on google about my problem, think i haven an incompatible kernel..
Can u help me please? Thx
wikkiz2 said:
Hi evereybody!
I have a SM-P905, rooted.
I try to install linux on my device and i got this message (view photo)
After i search on google about my problem, think i haven an incompatible kernel..
Can u help me please? Thx
Click to expand...
Click to collapse
If I'm right, there is no Kernels with loop device enabled for P905 at the moment.
Can i change the kernel? Or there is no point?
Thx
wikkiz2 said:
Can i change the kernel? Or there is no point?
Thx
Click to expand...
Click to collapse
If you take a look in the development section there is bonuzzz's P-900 kernel that comes with vtfb as one flavor, and there are also a few P-905 kernels. All of these kernels have github repositories, so I'm sure you could cook something up, if you're well versed enough in this domain.
wikkiz2 said:
Can i change the kernel? Or there is no point?
Thx
Click to expand...
Click to collapse
There is a discussion going on about the kernel compilation in the General Forum
notspike said:
Hi. Has anyone had success with running Linux Deploy in Framebuffer mode on the P900?
Closest I have gotten is with a VT enabled (but WIP) kernel for CM11. I saw the debian desktop flicker on for a second and then all goes black!
Other than that, all my attempts have resulted in a black screen, no backlight.
Ideally, I think I want Linux (deb, ubuntu, something) running on this tablet. I think because of its screen size and powerful spec it would make a very decent laptop replacement, but I feel that the android OS is not designed for this task.
EDIT: I now have debian running using framebuffer on the p900!
Click to expand...
Click to collapse
Hello, could you please describe what you had to do in order to get this working? I am trying to do exactly the same without much success. I have rooted my P-901 with the CF AutoRoot, and I have compiled and flashed a non-enforcing kernel using the instructions found at Graeme Hill's Dev Blog (sorry I can't post links yet) -- currently I am able to use Linux Deploy to have a distribution of Arch Linux running using LXDE, but I have to use VNC. I've tried fiddling around with the framebuffer settings in the configuration but it doesn't seem to work... I would love to get this feature working, as my understanding is that it is faster and better than using VNC!
Many thanks in advance!
hi I am currently away for the weekend but I will post some instructions when I'm back. do you know what issue you had when you attempted Framebuffer mode? I've given up on Linux on my tablet for the time being, I got it working but at the end of the day it's not optimised for the hardware so the user experience isn't worth it. too much tinkering and messing about, so I'm back to cm11
wikkiz2 said:
Can i change the kernel? Or there is no point?
Thx
Click to expand...
Click to collapse
The following link was posted by jdparden in the cm11 tread, I think all you need is found in the write-up <My setup with Ubuntu and a custom permissive Kernel: [ Galaxy Note Pro 12.2 ]>, including the link to a kernel.
Good Luck
indotoonster said:
Hello, could you please describe what you had to do in order to get this working? I am trying to do exactly the same without much success. I have rooted my P-901 with the CF AutoRoot, and I have compiled and flashed a non-enforcing kernel using the instructions found at Graeme Hill's Dev Blog (sorry I can't post links yet) -- currently I am able to use Linux Deploy to have a distribution of Arch Linux running using LXDE, but I have to use VNC. I've tried fiddling around with the framebuffer settings in the configuration but it doesn't seem to work... I would love to get this feature working, as my understanding is that it is faster and better than using VNC!
Many thanks in advance!
Click to expand...
Click to collapse
Hi, I used CM11 with the VT/FB enabled kernel.
Linux Deploy settings:
Output: Framebuffer
Additional: disabled VNC server, enabled X server
GUI settings: input as event2, you can check your device list to see what event your S-PEN is, touchscreen does not work properly - so use S-PEN!
use the latest Ubuntu distro
notspike said:
Hi, I used CM11 with the VT/FB enabled kernel.
Linux Deploy settings:
Output: Framebuffer
Additional: disabled VNC server, enabled X server
GUI settings: input as event2, you can check your device list to see what event your S-PEN is, touchscreen does not work properly - so use S-PEN!
use the latest Ubuntu distro
Click to expand...
Click to collapse
Hello notspike, thank you very much, I will try this out again over the weekend!
I can't remember exactly what didn't work last time, just that I remember it was working with VNC, and when I tried reconfiguring it to framebuffer and relaunching it just gave me a blank screen. However, I was doing this on the stock ROM (after rooting with Autoroot and installing a permissive-enabled kernel that I compiled myself as per the instructions on Graeme Hill's blog).
I haven't previously considered using CM11, but if this is what is necessary to get Linux working properly with framebuffer mode, I will bite the bullet and try it out!
indotoonster said:
Hello notspike, thank you very much, I will try this out again over the weekend!
I can't remember exactly what didn't work last time, just that I remember it was working with VNC, and when I tried reconfiguring it to framebuffer and relaunching it just gave me a blank screen. However, I was doing this on the stock ROM (after rooting with Autoroot and installing a permissive-enabled kernel that I compiled myself as per the instructions on Graeme Hill's blog).
I haven't previously considered using CM11, but if this is what is necessary to get Linux working properly with framebuffer mode, I will bite the bullet and try it out!
Click to expand...
Click to collapse
Hey I just noticed a mistake on my part, event8 is S-PEN, event2 is touchscreen, so you want to use event8. Also, if you have any peripherals plugged in at boot (i.e. OTG keyboard) it shifts around your event numbers, so event10 may be your s-pen, make sure you have nothing plugged in at boot and definitely check the device list for what event it is! Good luck
notspike said:
Hi, I used CM11 with the VT/FB enabled kernel.
Click to expand...
Click to collapse
So it seems that to get Linux Deploy working with Framebuffer one must first use a "VT/FB enabled kernel". Unfortunately I am using a P901, and all the custom kernels on these boards seem to be for P900 or P905 only.
I have successfully compiled a P901 kernel before to enable permissive mode using the instructions found at graemehill.ca/compiling-permissive-android-kernel. Does anyone know if creating a "VT/FB enabled kernel" is as simple as just setting the appropriate flags in the makefile and then recompiling the kernel? If so, could someone please point me in the direction of what flags I should set?
Many thanks in advance.
indotoonster said:
So it seems that to get Linux Deploy working with Framebuffer one must first use a "VT/FB enabled kernel". Unfortunately I am using a P901, and all the custom kernels on these boards seem to be for P900 or P905 only.
I have successfully compiled a P901 kernel before to enable permissive mode using the instructions found at graemehill.ca/compiling-permissive-android-kernel. Does anyone know if creating a "VT/FB enabled kernel" is as simple as just setting the appropriate flags in the makefile and then recompiling the kernel? If so, could someone please point me in the direction of what flags I should set?
Many thanks in advance.
Click to expand...
Click to collapse
There is no need for a vtfb enabled kernel. Instead you can use an on/off toggle called SELinux Mode Changer. Linux was successfully deployed by chhaggerty through this feature using Linux Deploy. Additionally, the toggle can be used for all/most kernels, but might run into issues if Knox is not completely removed. You can also achieve this by using a terminal emulator using the command
Code:
su
/system/bin/getenforce
You can also try disable it in build.prop where you set: ro.build.selinux=0,
or build it into a script for init.d
Wanam Xposed might also have the feature built in.
arcadia2uk said:
There is no need for a vtfb enabled kernel. Instead you can use an on/off toggle called SELinux Mode Changer. Linux was successfully deployed by chhaggerty through this feature using Linux Deploy. Additionally, the toggle can be used for all/most kernels, but might run into issues if Knox is not completely removed. You can also achieve this by using a terminal emulator using the command
Code:
su
/system/bin/getenforce
You can also try disable it in build.prop where you set: ro.build.selinux=0,
or build it into a script for init.d
Wanam Xposed might also have the feature built in.
Click to expand...
Click to collapse
Hi arcadia2uk, thanks for the information regarding the ability to enable permissive mode without requiring a recompiled kernel, that's useful. However, my query regarding the VT/FB enabled kernel is unrelated to the enforcing/permissive issue.
The reason I am asking is because I want to try using Linux in framebuffer mode (VNC seems a bit laggy for me), and from what I've read, I need the VT/FB enabled kernel. Unfortunately, none seem to exist for the P901 on these boards, so I'd like to try to compile one myself.
indotoonster said:
Hi arcadia2uk, thanks for the information regarding the ability to enable permissive mode without requiring a recompiled kernel, that's useful. However, my query regarding the VT/FB enabled kernel is unrelated to the enforcing/permissive issue.
The reason I am asking is because I want to try using Linux in framebuffer mode (VNC seems a bit laggy for me), and from what I've read, I need the VT/FB enabled kernel. Unfortunately, none seem to exist for the P901 on these boards, so I'd like to try to compile one myself.
Click to expand...
Click to collapse
I believe the toggle work just as well with framebuffer. Anyhow, you can try using the P-900 kernel the only thing that differentiates the two is the LTE support, and do you really need that with Linux?