Hey everyone,
As the title suggests, of those who have tried out Linux Deploy (for those of you who don't know what this, Its an app that automates setting up of chroot Linux and provides a few different "graphics subsystems" vnc, xserver and framebuffer) have you managed to get framebuffer working?
Seems like its largely trial and error as to getting the correct settings, I was unable to get this working using CAF Cyanogenmod. Maybe its dependent on kernel configuration, i was unable to find any reports of this working on the nexus 5.
Are you still doing anything with this? Currently working to try to get a Fedora install on my phone.
Related
Hey everyone,
I've been trying to connect my wiimote in debian. Im new to linux, im kinda putting all the pieces together as i go. wminput and all its corresponding packages seemed to install just fine with 'apt-get install wminput'.
But when I run wminput I get the error "unable to open uinput"
so googled, and managed to find uinput.ko and some general instructions on installing it.
I loaded it into /lib/modules/2.6.29.6-cm41/ and ran 'insmod uinput.ko' and i get the error 'Invalid module format' which im assuming is because it was compiled for an x86 system. modprobe displays a similar error.
I also dont understand the "cm41" in the path /lib/modules/2.6.29.6-cm41/, is that short for CyanogenMod, am I placing this module in my android Filesystem?
Are there any linux guru's around that could compile uinput.c for the g1 debian build? Or simply tell me that im way off track and there are bigger problems involved with getting this to work.
Also, if wminput did function. Does anyone know if it would send button presses to android while running in the background?
uinput.c
http://abstrakraft.org/cwiid/browser/trunk/wminput/uinput.c?format=txt
wminput
http://packages.debian.org/lenny/wminput
wmgui which i believe uses the same library as wminput has been made to work through ssh
http://www.lukedupin.com/projects/show?project=g1_wii -
There is also WMD for connecting to wiimotes but it requires uinput as well (i think).
http://www.circuitdb.com/articles/7/3 -
Ive been reading http://www.saurik.com/id/10 and it seems that this modules really needs to be installed to Android? And then I will be able to access this module from debian which is running on top on android? Can anyone confirm that?
I extracted the config file from my phone at /proc/config.gz and it has the line # CONFIG_INPUT_UINPUT is not set. some googling brings me here http://lxr.linux.no/#linux+v2.6.31/drivers/input/misc/Kconfig
206 config INPUT_UINPUT
207 tristate "User level driver support"
208 help
209 Say Y here if you want to support user level drivers for input
210 subsystem accessible under char device 10:223 - /dev/input/uinput.
211
212 To compile this driver as a module, choose M here: the
213 module will be called uinput.
This all leads me to believe that this module will work on the G1. Will Any Devs PLEASE compile this for me. If you think it would work properly that is.
I just dont have the skills to compile it myself yet. Ive been reading alot on how to compile the kernel and kernel modules for the G1, I setup Ubuntu, and setup my environment and installed the android source code. I was working off this link http://andblogs.net/2008/12/compiling-your-own-g1-kernel-modules/ but i dont understand how i get the kernel source . I have sooo much reading todo before I get all this. Any recommended links?
Hi,
After having had a gazillion of frustrations while attempting to add Ubuntu 12.04 to my PC, I had enough of the endless chain of problems to reach the point of installing the requirements for ADT.
So I thought I might be able to go with a virtual machine. I have my environment (Ubuntu 12.04, ADT and its requirements) installed and working on Oracle VM (with extensions installed).
Whatever I try with the USB settings, I'm unable to get either my Nexus 7 or my Asus TF300T to work on the VM.
I tried adding a USB filter with the correct IDs, but that didn't add either device to my VM.
I ran out of ideas to try. I really want to learn more about developing for Android, but it seems I can't get the devices to work.
Rhian said:
Hi,
After having had a gazillion of frustrations while attempting to add Ubuntu 12.04 to my PC, I had enough of the endless chain of problems to reach the point of installing the requirements for ADT.
So I thought I might be able to go with a virtual machine. I have my environment (Ubuntu 12.04, ADT and its requirements) installed and working on Oracle VM (with extensions installed).
Whatever I try with the USB settings, I'm unable to get either my Nexus 7 or my Asus TF300T to work on the VM.
I tried adding a USB filter with the correct IDs, but that didn't add either device to my VM.
I ran out of ideas to try. I really want to learn more about developing for Android, but it seems I can't get the devices to work.
Click to expand...
Click to collapse
Well i had this problem before search on google how to add adb device to vm and you will find a guide frogot wich site i will do sone search and report back
Sent from my GT-I9500 using xda premium
S.a.M.e.R_d said:
how to add adb device to vm and you will find a guide
Click to expand...
Click to collapse
Thanks, with some trial and error I got it working.
In short:
On the host run adb devices to start the deamon, it listens on port 5037, so with FreeSSHd on my windows host I could enable an ssh connection from my VM client using:
autossh -M5037 -N -f -R 5037:localhost:5037 10.0.2.2
Then my adb devices lists my hosted device.
On to the next challenges...
hello,
i've got motorola xoom MZ604 (wifi-only), and following this link from kali linux, and also this one, i've managed to install kali linux natively on my xoom.
it is booting, i can login, i can connect to internet via wpa_supplicant and other methods, but i have one big issue - i can't get the Xserver to run.
looking it up - it is related to the fb* issue on the nvidia tegra here.
but when i try to recompile the kernel with the fix on that link, the compilation fails everytime.
is there a way to apply this patch to my already installed kali?
or rather - any other way to solve this?
thanks,
Ilan
ilanp13 said:
hello,
i've got motorola xoom MZ604 (wifi-only), and following this link from kali linux, and also this one, i've managed to install kali linux natively on my xoom.
it is booting, i can login, i can connect to internet via wpa_supplicant and other methods, but i have one big issue - i can't get the Xserver to run.
looking it up - it is related to the fb* issue on the nvidia tegra here.
but when i try to recompile the kernel with the fix on that link, the compilation fails everytime.
is there a way to apply this patch to my already installed kali?
or rather - any other way to solve this?
thanks,
Ilan
Click to expand...
Click to collapse
i just planning up install
ilanp13 said:
hello,
i've got motorola xoom MZ604 (wifi-only), and following this link from kali linux, and also this one, i've managed to install kali linux natively on my xoom.
it is booting, i can login, i can connect to internet via wpa_supplicant and other methods, but i have one big issue - i can't get the Xserver to run.
looking it up - it is related to the fb* issue on the nvidia tegra here.
but when i try to recompile the kernel with the fix on that link, the compilation fails everytime.
is there a way to apply this patch to my already installed kali?
or rather - any other way to solve this?
thanks,
Ilan
Click to expand...
Click to collapse
Generally, it's bad practice to patch a compiled kernel. Occasionally I'll run into issues like this and I have to start over in a new source folder and try to recompile from scratch. If it succeeds, you know something was changed in your source other than your patch that borked it. If it fails, it sounds like the patch may not work.
Hi guys, I'm trying to install kali linux on a galaxy lite from metropcs. I was using linux deploy and have gotten root. I looked for the issue online and got all the same leads but not for my device.
The typical issue is usually a fail at checking mount points. I uploaded a screenshot and was wondering what some thoughts were.
Trying to build my own AOSP ROM and I keep getting stuck on emulator unable to find the kernel version, though the file is there.
I am using Hyper-V VM with Ubuntu V20 installed and the VHD is exactly that, a .vhd file extension for the virtual hard drive.
I just can not seem to resolve the problem on the missing kernel, also have supplied a pic showing exactly what it says after the build is finished and then I try and run emulator.
Any help or info, links on the matter would be much appreciated and thank you for taking the time to help out.
I have also noticed I can not use "emulator -list-avds" nothing happens. Just exits and terminal is ready for user input again.
So far I did a repo sync again and then a m -checkbuild and just waiting for it to finish to try emulator again
Update: Decided to start from scratch
Changes that I have made.
Using Ubuntu 18.04 for O.S
Switched from M.S Hyper-V to Oracle Virtual-Box (V.B has more features then Hyper-V and is better in performance because of it.).
Virtual HDD is set to .VHD but is on Sata and not IDE now (Virtual-Box only allows it).
Made the VHD a fixed drive instead of dynamic for better performance (Max size of 512GB)
Dedicated 32GB of ram to VM.
Allowed up to 6 cores on a 12 core processor.
might experiment getting Oracle JDK installed instead of using openjdk, due to having issues with it.
UPDATE_1
Fresh build on 18.04 same issues as old build. emulator, avd and android. all not working.
I might have missed a package to download or something or maybe java still is not working. Using openjdk 11 at the moment. I am running out of ideas as to why i can not get it working.
Update_2
Looks like the reason emulator is not working is due to me not installing SDK, I am not using the IDE so I think I need the command-line & Platform tools installed. got to work out how to install it now.
UPDATE_3
SDK from what I know is installed. Now I am getting an output file is missing, but build completed with no issues. Please help, new image also supplied.