First I would like to thank Team EOS for there amazing effort in the development of Stable Release 2.0 for the Xoom wifi.. Really nice work.
Have been lurking and learning for a while, now armed with enough knowledge to be dangerous... I step into the breach.
Xoom 604 running Team EOS 2.0.
My question: Is it possable to change the USB mount point from /media/usb to /mnt/usb. I have tried editing the /etc/vold.fstab with no success, am I missing a step?
Best, Eddie
USB mount location
I'm still working on this, is there the possibility of using a different usb.apk or must one be compiled from source to change the mount location?
Not opposed to trying but would rather have a little guidance
Thanks, E
Further Info - Could use some help
So all the research indicates this is kernel configuration. Does anyone know if there is a kernel patch or can direct me to a specific forum with the information to compile a patch.
Any help on this would be greatly appreciated..
Best, Eddie
Related
Hi all, i'm new to this forum so i will first give an introduction of my Android experience.
I have been developing apps and android for the ADP1 (g1) phone, these are mainly for gaining access to telephony data and displaying it for Telecom engineers. I would like to port this code into the Magic/Sapphire, though (please correct me if i am wrong) there is no support for building the android code for a magic and it appears you cannot flash system.img onto the magic.
I have been looking at the ROM's that are about and was wondering how you managed to make them?
If there is already a thread for this can someone point me in the right direction as i have been unable to find it, otherwise can someone post a guide on how to approach this. Thanks.
Liam
First post in the Dev section but this seemed to be the place to talk about kernel compilation and module development.
I have twice now, and am working on my third kernel compilation for the purposes of custom module building for the TF700 and the TF201.
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all. Is this normal for kernel compilations? I would have thought that it would be fully compilable out of the box ( so to speak). Is it ASUS or just android/Linux in general that works out this way?
Is there a better way to do it? Should I use some generic source with the same version numbers? The current source is just not working at all. I am using an Ubuntu distro. Have the cross compile tools etc... but it just fails. I have already resolved two missing definition references and it just keeps on failing in new places
Hopefully this question doesn't offend developers. I have moved from WinPhone to here and want to better my understanding of how this should all work but need to start with some basics before I can make a meaningful contribution.
Thanks.
P.S... I looked and didn't find a "Compiling android kernels for dummies" book
hx4700 Killer said:
I looked and didn't find a "Compiling android kernels for dummies" book
Click to expand...
Click to collapse
"Dummies" doesn't write a book on kernel dev. Too wrapped up in telling people how to download iTunes.....
Use your "Google". And when you find it, Google XDA University.
There, you will find steps for setting a build environment and kernel and cross arm.
Understand, all kernels are different, but a good place to start. Plus, you learn how to use Google. An added bonus.
Oh... and... as an extra bonus, I will move this to Q & A, as this post has no development work attached. :silly:
MD
My question wasn't HOW to cross compile. I have done it.
My question is WHY are there so many errors that need correcting when compiling the ASUS downloadable kernels and if this is typical of the source from any device or just ASUS?
hx4700 Killer said:
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all.
Click to expand...
Click to collapse
I had to fix exactly one pair of quotes vs. angle brackets somewhere in the RIL - get the patch pack from my kernel and apply the ril include fix. Then it should compile. If not, you are doing something wrong.
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
alexcass4 said:
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
Click to expand...
Click to collapse
Step 1: Get a suitable ARM toolchain. I can't help you here with Ubuntu because I'm using Gentoo and their crossdev tool (http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1).
Step 2: Cross-compiling the kernel works just as for native kernels (make menuconfig, make), but you have to pass parameters to each make, e.g. make ARCH="arm" CROSS_COMPILE="arm-gentoo-linux-gnueabi-" (or whatever your toolchain is called)
Step 3: For the TF700-specific blob stuff I have written a detailed tutorial here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
Hi everyone,
I've been working on CM for the PadFone Infinity (pretty good device, only lacking a good community) for some time, and I've started to have some results now.
I've basically been using Asus' kernel sources and a custom-made device tree. I then tried to build CM and corrected every error I encountered to try to compile ROM successfully. I eventually succeded in compiling it, but it's now that I need help the most.
Why? Because I have no kernel development knowledge at all, and I really don't want this project to die.
So, let's list what does work and what doesn't:
-Recovery compiles and works just fine. I can backup, restore, flash roms, wipe, and everything that is needed.
-ROM and kernel compile without errors too.
-ROM does NOT boot at all. Getting past the Asus logo, the screen just switches off, and phone totally looks like it's shutdown. No backlight, keys are not backlighted either.
So here is what is needed to compile ROM:
-Device Tree
-Kernel sources (modified to compile without errors)
-PadFone Infinity stock ROM (if needed. Also, there are device blobs in it, so it might be useful)
-Asus untouched kernel sources
I do have the device, so if you need anything about it (hardware info, for example), feel free to ask. I'd love to help, even though I've already made some work, I've come to a point where my knowledge will be far from enough...
Thanks everyone for reading, and maybe for helping if you are interested in this project.
Contact Faux, maybe he will be interested in maintaining a Kernel base for this device.
Bumping.
If a xda recognized developer is willing to develop for this device, I'll have one sent to him.
I really want to have CM and some dev community on this device. I started a bounty to be able to have a device sent to a dev, it seems that many people also want development on it.
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
mva.name said:
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
Click to expand...
Click to collapse
cm always need alot of work and if you don't have the device it's very difficult to have a stable build .
messi2050 said:
if you don't have the device it's very difficult to have a stable build .
Click to expand...
Click to collapse
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
mva.name said:
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
Click to expand...
Click to collapse
Yeah but that was from 2013 look to the post date , i can do it if the offer is still there but i doubt that
Hi there, I'm SDR (software Defined Radio) amateur, and I'm looking to connect a USB rtl-sdr Dongle to my GT-i9003, I did a search around our forum zone and I see just a "few old" stuff about OTG and our device, some one knows if we can use it with 3.0.101 kernel? so are the modules runing?, someone did a test?.
I'm thinking build a custom kernel for that with this extra modules but I'm not a programer and I dont know fix kernel/modules issues, maybe some advanced developer knows about that or can try?.
Without more, Bye and thanks in anyway.
Best regards:fingers-crossed:.
I'm not running CM11, but with my Dhiru's 10.1 (3.0.8 kernel) I Tried to connect an USB keyboard, but no results.
crDroid(http://forum.xda-developers.com/showthread.php?t=2544686) said it support otg
but i havn't try it
Hi All,
I've been reading these forums for sometime now. Until now I've only been here as a user of roms not as a developer.
However, on my current project I had the requirement to get an android distribution running on a beaglebone black embedded board. As there are a lot of experienced rom developers here I would like to ask my question here.
Currently I'm successfully booting the kernel. It also seems to get to the actual homescreen. However, it seems that I'm currently in a bootloop a when I reach the homescreen. I get thrown back to the boot animation.
My guess is that there is some kind of memory issue here. More specifically the vmalloc part.
I get the following error in the dmesg when the homescreen crashes:
binder: 1804: binder_alloc_buf failed to map pages in userspace, no vma
Can anyone confirm that this is good explanation and tell me how I should adres this issue? Or maybe provide me with some other tips?
I tried to increase the vmalloc size but I'm not really able to do so. if I enter the vmalloc=512M command on the uboot it doesn't really change the size...
Thanks
Hi there,
You must read some guides and tutorials for that. Starting from:
1. This guide about how to port different ROMs to your device.
2. This guide about how to port AOSP ROMs to your device.
3. This guide about how to port a ROM to your device.
4. This guide about how to create a new ROM for your device.
5. This guide for ROM development beginners.
6. This guide in xda university for building your own android rom.
7. This guide in xda university for porting an aosp rom from source.
There are also instructions on the cyanogen mod wiki site about it.
A good place to ask if you have questions about it or need help, is Chef Central - Android. Many devs are watching this forum and can help quickly.
Good luck