Just popping in to say hello. I'm brand new to Android, but I've been building linux kernels and hacking on various projects since i586 days (P5-90! Booyah.)
I got my toes wet merging 3.0.69 into Garwynn's community kernel and figuring out how to build a Perseus package that didn't break STweaks.
I am currently trying to get a kernel to compile with netfilter and RNDIS. My issue is this: drivers/usb/gadget/gadget_gbhc looks like a murder scene. It looks like a major project to clean it up to the point that it would would work.
Fixing it also may be a waste of time, as the android mainlining project's target completion date is coming right up.
On the other hand, as of this morning they hadn't mainlined RNDIS yet, and the clock is ticking for Android 5- so who knows if this will even be working for Android 5 (or whether Android 5 will be Linux 3.9, though rumors say yes).
Has anyone already fought with this and got it working? I am torn between not wanting to walk away from a challenge, and knowing that it's a waste of (lots of) time.
Related
New to Android. But long time user of Linux/RH/Fedora. Are there “distro's” on Android? Can users easily add/remove software with a RPM type management system? In Linux if you don't like TnT you would just uninstall it. Viewsonic g tablet seems to be ok if you manually change a few things. I'm assuming that this is generally a temporary problem due to Viewsonic being behind in their updates. But what I would like to know is there going to be any long term “distro” type leadership going forward? When the new Android Tablet OS is released will it work with most hardware (Viewsonic) like a Linux distro or are we depended on Viewsonic. If Viewsonic let us down can we divorce them and go directly to Android or someone else for automatic updates? Thinking about buying. Can wait for Flash update hopefully in December. Don't see screen as a problem, basically the same as most laptops/netbooks. Can add market manually till it become official with new OS.
.
Sears - Save $5 off $50 with code SEARS5OFF50 at cart
Android is not like normal distros.
Being primarily an OS aimed at mobile devices (IE phones) with limited memory and proprietary layouts and internal set-ups, all drivers can not be provided in one overall install. Confliction between drivers would be an issue as well. Also look at many phones (like the nexus one) the Firmware controlling the cellular radio also controls the camera and encoding of videos and images. There is some common ground, but one ROM will not work on all devices without tweaking for the perticular device. CyanogenMOD ROM is a good example, it works on many devices but you must install the proper version for the device you have.
Also remember that we do not have Root on these devices out of the box, 99% of the time we must find an exploit to gain full access to the device. The Nexus one and the G tablet are the only devices I know of off hand without locked down bootloaders. Cellular carriers want the devices looked down so the users can not use the device in ways that the carriers do not want. (like free tethering)
We are dependant on the manufacturer often times to release source code for the device so Devs can rip out the proper drivers and framework for the device. Often times drivers cross over between android versions making updating easier for the ROM devs.
If you want a device that you can truly tinker with, stick to devices that Google has as Developer models. The old G1 the Nexus One and the upcoming Nexus S. Maybe they will release a Dev tablet as well.
The N900 is more open in that regard as far as being like a true Linux, though the future of that branch seems uncertain. It will defiantly be more niche.
Thanks for the reply. I guess I was thinking Android was Linux lite. Not sure where I stand on a tablet now. Think I want a Linux pc in a tablet form. Fedora on a tablet would be fine for me. Like you say tablets with MeeGo (Intel/Nokia/Linux Foundation) may or may not appear any time soon. Have to wait and see what happens.
tktim said:
Thanks for the reply. I guess I was thinking Android was Linux lite. Not sure where I stand on a tablet now. Think I want a Linux pc in a tablet form. Fedora on a tablet would be fine for me. Like you say tablets with MeeGo (Intel/Nokia/Linux Foundation) may or may not appear any time soon. Have to wait and see what happens.
Click to expand...
Click to collapse
Android is running on top of Linux, and given programs compiled for ARM you can install about anything, but there's no X... Framebuffer stuff could potentially work..
But no, if you're looking for a typical Linux desktop environment, this isn't the place to look. Although some of the dual boot Windows/Android tablets makes me wonder how difficult it would be to get it Linux/Android.
Thanks for the additional information.
Kernel development isn't my strong suite.
But I'm very interested in some opinions on what exactly it would take to get MeeGo running on the G-Tablet.
http://tapntap.http.internapcdn.net/tapntap/viewsonic/gTablet-TapUI-1.1-Kernel-Patch.zip
Would that kernel patch be of any use?
Lets assemble a team to do it, i will be on it but i probably dont know enough to lead it or anything. You might send an email to the meego team asking about what all the kernel needs to support in order to get this thing running.
Martin is working on Advent Vega for Meego and I think we can just follow the step for G tablet.
Here is the progress:
xxxx://wiki.meego.com/ARM/TEGRA2
xxxx://wiki.meego.com/ARM/TEGRA2/Notes
I can't post the URL until I got 8 postings, so just replace xxxx = http
NS_nix
Nice. Looks like it's still got a long ways to come, but glad someone's already working on it! I'll keep my eye on that page.
I think we do is enumerate the components of G-tablet using the kernel source info.
1. Touch screen is using eGalax. +CONFIG_TOUCHSCREEN_USB_EGALAX=y
2. bcm4329 wlan for Wireless 8011n
XXXX://forum.xda-developers.com/showthread.php?t=892308
3.
And use this info to patch the meego kernel for G-tablet or the other way around, find a tegra kernel with g-tablet patch that can run meego.
First let me introduce myself. The name is Darcy and I have been casually using linux and other *nix OS for about a decade. I am in school working on a programing degree ATM, and am a pretty quick study. Anyways, I without much research bought my wife a generic 7" tablet running android 1.6. I know what processor it has and Im hoping that leads me to a place to start. Ok so the device is a "Kasser Net'sGo" we didnt realize that its just a china pad with another companys name on it when we ordered it. So most of the apps dont run correctly, and in general the device sucks(on a software level the HW is fine although generic).
Anyways it apears that i can get into recovery mode to flash if i had no other choices. But since there are no official roms im hoping to find a build thats based on the same CPU or similar hardware to find a starting point. Its running the Marvell Aspen 800mhz chip and standard ddr2. Sadly thats all we have been able to find out about this device.
I have compiled custom builds for linux before, and i have now purchased a Gtab so i have a less garbage device to test some things on(i have allready flashed 2 different roms and fooled with a bunch of the settings). But we would realy like to do something with this other tablet. So if anyone can point me in the direction of some info on how to do android builds or a repository of chipset drivers and such that might help me that would be greatly appreciated.
Ok i am desperate guys!!!!!!!!!!!! Ive been away from the android scene for a little while becuase Ive recently gotten into micro controllers specifically the parallax propeller. Anyways some guys recently got GCC working with the propeller, and have released the toolchain open source obviously! Well there has been alot of effort and research on my part in being able to use an android phone to program the propeller and arduino acually via bluetooth!
The only thing thats missing at this point is a loader program and optionaly the new propeller gcc toolchain compiled for arm! Well I had inteded on porting it! I had done alot of kernel hacking a few months ago on the ndk7. I downloaded ndk 8 and i have searched hi and low through the docs and the directorys it seems there is no arm-eabi binarys anymore? I cant even find ndk7 anymore. The documentation with the ndk is just confusing im thinking i need to build a stand alone compiler... i have no idea....
Could anyone please help me get the arm tool chain without neon extensions set up? Im thinking I have to compile it with this new ndk, ive spent 2 hours trying to figure this out and the truth is I have porting to do not fusing with all this junk google changed on me in 6 months. All I want is an android compatible cross compiler working
Just curious of anyone has attempted to run vxWorks using some generic opengl library on a phone yet?
I know Wind River helped with some of the initial porting of Android in the early stages, so I am hoping it wouldn't be that big of a transition to port over some android libraries to vxWorks... :fingers-crossed:
I know this will never be practical for real usage, but this is more like a side project for me.