Related
Hello, I found a driver online that I want to add to my Android phone. It is a DisplayLink device driver.
magoroku15/DisplayLink-driver-for-android (from github)
The part I am confused about is how to go about adding the driver to my phone. Do I need to download the Android source code, add the driver to that, and then build the whole thing? Or is it possible to just load the driver as a module?
I've searched Google but haven't found anything definitive. I'm not even sure if I'm using the right terms here, as I haven't ever played around with adding drivers to anything before.
Any help would be greatly appreciated!
yes. i would also like to know how this is done.. please share. thanks
me 3! tell usssss
you would need a dev environment setup to cross compile for that device (your phone) then compile the source as a module and load it from a command line. (insmod <module>). if you get a new line in the terminal without error, its loaded.
thanks! ill try this later..
nenn said:
you would need a dev environment setup to cross compile for that device (your phone) then compile the source as a module and load it from a command line. (insmod <module>). if you get a new line in the terminal without error, its loaded.
Click to expand...
Click to collapse
What if you don't (or don't want to) have root access on the phone?
well this guy in his thread is loading a lot of drivers *.ko i thing?
helpful?
*edit* forgot the link
http://sven.killig.de/android/N1/2.2/usb_host/
Any answers?
I'm looking for the same thing: I want to install a new driver on Android devices, but I can't Root the devices - I need to add the driver(s) to stock Android installations.
Just curious.. why do so many ppl seem to add driver to their system? :/
My task is similar to noted earlier.
I want to make "virtual driver". In other words, the device doesn't have specific hardware and I need to emulate it programmately.
Any hints and links would be useful.
Thanks.
jkoshi said:
What if you don't (or don't want to) have root access on the phone?
Click to expand...
Click to collapse
I think you would need root access on your device in order to load your kernel module: 'insmod your_module.ko' or whatever.
- jc
Hey i was looking to do this exact thing so i could connect a mimo monitor to my phone any progress or step by step instructions
Subscribed
you need to have right kernel module compiled on the same kernel version that you android is running on.
it is a may be not only *.ko file, but it may need also another firmware files.
if it is only one file, you are lucky, you need just that ko file with right kernel version and put to vendor directory with modules.
and if not automaticaly loaded, you must call insmod command from rc file on device boot or manually from terminal.
better solution is to compile kernel yourself with driver inside it.
for details see 'linux kernel modules'.
Note: for sure you need root access to such as system modify operations...
And here : https://hex.ro/wp/blog/compile-an-android-kernel-module-outside-the-kernel-source-tree/
Hi everyone
I just got myself a transformer and really love it
i am running it with the latest revolver rom
Today I tried to map a network drive and everything was fine until I have a few video and music files with chinese file names. I am using cifs manager and es explorer. All the chinese characters show up as question marks "?" and it seems the system cannot understand the name (I cannot play the files nor renaming them on my tablet)
I tried googling a bit but failed to find a solution. Can anyone shed some light on this issue?
Thanks very much in advance
p,s, found this link and tried adding "iocchaset=utf8" into the option line in cifsmanager but sadly it does not work
I believe you'll need a kernel a with utf-8 support and load it via the settings in CIFSmanager.
dy57 said:
I believe you'll need a kernel a with utf-8 support and load it via the settings in CIFSmanager.
Click to expand...
Click to collapse
thanks for your reply
may I ask how I can check which kernel supports utf-8?
and what do u mean by load it via the settings in CIFSmanager?
Sorry if my question sounds noob
i am really new to this world lol
121212121212121212
I was hoping some post this here.
I wanted to know have you checked on stock kernel does it supports touchscreen work.
if not can anyone test and suggest which all kernels are supporting it and not.
anantshri said:
I was hoping some post this here.
I wanted to know have you checked on stock kernel does it supports touchscreen work.
if not can anyone test and suggest which all kernels are supporting it and not.
Click to expand...
Click to collapse
I got Aroma installer in X10S v8.2 addon zip (for unlock bootlaoader) and had no problem on stock or custom kernel.
However I never tried on fxp kernel.
For info there's a menu in aroma installer to config the touchscreen, values must be written in the config file (aroma config).
The only restriction for now is that Aroma installer is using Edify script so may cause problem on locked bootloader ... doesn't copy files or else ...
@Feravolt
Thanks for this thread !!!
About the script for locked bootloader did you have time to look at it ?
It would be very nice to include it directly in kernel .. maybe it could solve the problem with lock bootloader ?
Hi OP
Below is the latest Aroma File Manager's newest features :
- Terminal Emulator.
- Set Permissions.
- Auto screen calib.
Bugs :
- File copy, paste and move function from Internal Memory into SD Card (and vice versa).
- Scrolling Touch for X10, have to use volume buttons.
Any chance for X10 to have this recovery tool to be integrated in Kernel (for GB, ICS and JB) ?
Just incase if no backup file, PC/Laptop arround to repaire bootloop or bricked phone, easily .
Thanks in advance
Regards
Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS.
Install the latest version of SuperSU. Sign in to Play Store using your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images
Oooh... now I can test this to see if it fixes my G+ compatibility issue
The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you
meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.
irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211
#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.
This will work on a Nexus 9 or it only works in pc's?
when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy
Waiting for rooted system.img for Phoenix OS 2.1.0
SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy
MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?
Guys, when to expect a rooted image for V 2.1.0 x86
thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?
Coconut Kernel for LineageOS 15.1 - With Nethunter Support
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is only for Lineage-OS 15.1 or ROMs based on it
Since I did not find a kernel for LOS Oreo with USB Wifi drivers, compiled one.
This kernel has been built from the LOS 15.1 source on git with changes adapted for standalone compiling. So i don't know if any ROM feature is broken though i believe stock features should work.
Yes, it supports monitor mode and packet injection.
Drivedroid is also supported by default in the kernel.
How to use USB Wifi Adapters?
Download from attachment and flash the kernel in twrp
Reboot (First boot will be a bit slow)
Plugin the adapter
MAKE SURE THAT USB OTG IS ENABLED IN SETTINGS FOR ANY OTHER LINEAGEOS BASED ROM
Test by issuing the command ifconfig wlan1 up
It's also important to be on latest 5.0.8 firmware (not rom) for this to work.
Troubleshooting
If the above steps don't work for you,
1. Clean install latest oxygen os 5.0.8 from stock recovery by side loading ( this will install latest firmware which is required)
2. Do system, dalvik, cache, data wipe(firmware will be still there)
3. Flash any lineage15.1 based rom or LOS itself and gapps
4. Flash and enable root
5. Flash coconut kernel
6. Install and open terminal and type ifconfig wlan1 up as root to test after plugging in usb card
This is the failsafe method
You can use the usb adapters in any chroot environment(eg LinuxDeploy) - not just nethunter.
To mods - i created a separated thread for people to not flash incorrect zip. if its against the rules, i can merge it.
Source
https://github.com/LineageOS/android_kernel_oneplus_msm8996
Been looking for this for ages, gonna test now
Hey can you add the driver for the Atheros AR9271 Chipset?
hairyfred said:
Hey can you add the driver for the Atheros AR9271 Chipset?
Click to expand...
Click to collapse
It's added and tested working. Does it not work for you?
fredrickz said:
It's added and tested working. Does it not work for you?
Click to expand...
Click to collapse
None of the drivers seem to work, in about phone it says I'm using your kernel so I'm a bit confused
I tried manually moving the file from system/etc/firmware to system/lib/modules and to modprobe it but that doesn't work there either
it's probs a simple mistake I've made, I'm on omni rom 8.1
hairyfred said:
Hey can you add the driver for the Atheros AR9271 Chipset?
Click to expand...
Click to collapse
hairyfred said:
None of the drivers seem to work, in about phone it says I'm using your kernel so I'm a bit confused
I tried manually moving the file from system/etc/firmware to system/lib/modules and to modprobe it but that doesn't work there either
it's probs a simple mistake I've made, I'm on omni rom 8.1
Click to expand...
Click to collapse
I personally tested it on Lineage OS 15.1
I don't know about omnirom. My kernel has nothing to do with the folder /system/etc/firmware
See the screenshot.
There is no need to load the module as all drivers are built-in.
Post me an output of dmesg | grep htc
Reboot the phone, plugin your WiFi card, open terminal, type su, then type dmesg | grep htc
Also check if otg support is enabled in omnirom. Just plugin a USB flash drive on to the otg cable/adapter and see if the drive shows up. If yes, then otg is enabled, else you need to enable that.
I think otg maybe disabled by default in omnirom. Search otg in settings
fredrickz said:
I personally tested it on Lineage OS 15.1
I don't know about omnirom. My kernel has nothing to do with the folder /system/etc/firmware
See the screenshot.
There is no need to load the module as all drivers are built-in.
Post me an output of dmesg | grep htc
Reboot the phone, plugin your WiFi card, open terminal, type su, then type dmesg | grep htc
Also check if otg support is enabled in omnirom. Just plugin a USB flash drive on to the otg cable/adapter and see if the drive shows up. If yes, then otg is enabled, else you need to enable that.
Click to expand...
Click to collapse
I type it, no output, kernel might be incompatible with my rom :/ even though its lineage based
hairyfred said:
I type it, no output, kernel might be incompatible with my rom :/ even though its lineage based
Click to expand...
Click to collapse
Chk the otg settings. Plugin a flash drive and see if it gets detected also type otg in settings and see if theres an option to enable it.
If you enable otg, you should remove and insert the card and test
fredrickz said:
Chk the otg settings. Plugin a flash drive and see if it gets detected also type otg in settings and see if theres an option to enable it.
If you enable otg, you should remove and insert the card and test
Click to expand...
Click to collapse
OTG is detected , it can use usbs etc
Send me a link of the omnirom u use
fredrickz said:
Send me a link of the omnirom u use
Click to expand...
Click to collapse
http://dl.omnirom.org/oneplus3/ latest one
hairyfred said:
http://dl.omnirom.org/oneplus3/ latest one
Click to expand...
Click to collapse
Just downloaded and installed that.
Flashed the ROM after wiping data, system, cache
Flashed supersu
Didn't flash gapps as I was just testing.
Flashed my kernel
Rebooted
Downloaded termux
Typed su
Plugged in USB ath9271 tplink wn722n
Typed ifconfig wlan1 up
And it worked
Possible problems for you
You need to install the latest firmware and modem for OxygenOs 5.0.8 .the latest you can get
For that you can either flash full oxygen OS ROM from op3 recovery by side loading
OR
you could download and flash only the firmware and.modem collection.
I recommend you flash stock oxygen is 5.0.8 official from their website.
Then wipe system data cache and then flash omni ROM latest and gapps and SuperSU whatever
Then reboot and complete initial setup
Then reboot and flashy my kernel.
It will work.
Firmware and modem only for OnePlus 3 OOS 5.0.8 Latest
https://androidfilehost.com/?fid=11410963190603878417
Xda thread
https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
fredrickz said:
Firmware and modem only for OnePlus 3 OOS 5.0.8 Latest
https://androidfilehost.com/?fid=11410963190603878417
Xda thread
https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Click to expand...
Click to collapse
HAVOC 2.2 is AOSP base, should i try on that? If No please add support for it, its a Highly customizable Rom an Top Liked, I want to test your kernel
Hayatzada said:
HAVOC 2.2 is AOSP base, should i try on that? If No please add support for it, its a Highly customizable Rom an Top Liked, I want to test your kernel
Click to expand...
Click to collapse
The kernel should work on that ROM but for all the specific features of that rom, i should build the kernel from the customized version of their source. If their source is updated with all rom features, and it's available in git, maybe i can try.
You can ask the rom devs regarding updated kernel source for their rom and if you find one let me know. I'll look into it.
fredrickz said:
The kernel should work on that ROM but for all the specific features of that rom, i should build the kernel from the customized version of their source. If their source is updated with all rom features, and it's available in git, maybe i can try.
You can ask the rom devs regarding updated kernel source for their rom and if you find one let me know. I'll look into it.
Click to expand...
Click to collapse
i installed magisk module Nethunter but can't see Nethunter Icon on Havoc 2.2. any idia what the problem would be?
Hayatzada said:
i installed magisk module Nethunter but can't see Nethunter Icon on Havoc 2.2. any idia what the problem would be?
Click to expand...
Click to collapse
I've compiled a kernel with USB WiFi drivers supporting monitor mode and packet injection for havoc 2.2 pie. You can try that too. I'll try to post it in a cpl of days. Im just testing the kernel for any stability issues. As if now its working fine and USB adapters are also working good.
I personally have used nethunter only by installing the nethuter apk or by flashing the zip file for the ROM version. If magisk module is giving problems, you can do any of the following
1. Download nethunter apk by searching online
2. Download armhf or arm64 full ROM zip from nethunter nightly website(both works on OP3)
3. Extract Kali image from the zip and place in root of internal storage.
4. Open nethunter app and install from sdcard
5. Install additional tools if required
OR
Simply omit nethunter and use another chroot app like Linux Deploy.
You can install and use all tools in Linux deploy the same way as net hunter like airgeddon, metasploit, Beef, airmon-ng, wifite, reaver etc
I think a new version of net hunter is on its way too..
fredrickz said:
I've compiled a kernel with USB WiFi drivers supporting monitor mode and packet injection for havoc 2.2 pie. You can try that too. I'll try to post it in a cpl of days. Im just testing the kernel for any stability issues. As if now its working fine and USB adapters are also working good.
I personally have used nethunter only by installing the nethuter apk or by flashing the zip file for the ROM version. If magisk module is giving problems, you can do any of the following
1. Download nethunter apk by searching online
2. Download armhf or arm64 full ROM zip from nethunter nightly website(both works on OP3)
3. Extract Kali image from the zip and place in root of internal storage.
4. Open nethunter app and install from sdcard
5. Install additional tools if required
OR
Simply omit nethunter and use another chroot app like Linux Deploy.
You can install and use all tools in Linux deploy the same way as net hunter like airgeddon, metasploit, Beef, airmon-ng, wifite, reaver etc
I think a new version of net hunter is on its way too..
Click to expand...
Click to collapse
Thanks a lot for your reply, installed nethunter apk and placed in root of internal storage after renaming but not detected by chroot(have successfully done it before in Nougat), i personally dislike Linux deploy method so waiting for resolving, i think its a Pie issue. By the way thanks again.
Hayatzada said:
Thanks a lot for your reply, installed nethunter apk and placed in root of internal storage after renaming but not detected by chroot(have successfully done it before in Nougat), i personally dislike Linux deploy method so waiting for resolving, i think its a Pie issue. By the way thanks again.
Click to expand...
Click to collapse
Try the download option in nethunter app. Renaming to correct file should get it detected in nethunter app
Regarding linuxdeploy, you can change the default repository to any other mirror and get blazing fast speed. Try the following
Install to a file or directory selecting kali-rolling
Use http://kali.download/kali as source instead of default http://http.kali.org/kali
Then select other configurations and install it
What was the filename you renamed the kali archive to?
fredrickz said:
Try the download option in nethunter app. Renaming to correct file should get it detected in nethunter app
Regarding linuxdeploy, you can change the default repository to any other mirror and get blazing fast speed. Try the following
Install to a file or directory selecting kali-rolling
Use http://kali.download/kali as source instead of default http://http.kali.org/kali
Then select other configurations and install it
What was the filename you renamed the kali archive to?
Click to expand...
Click to collapse
i successfully installed kali but nethunter terminal crashes when ever i open it.