[Q] A few AOSP compile questions - LG Optimus 2x

I am trying to compile a clean AOSP ROM for my O2X, there is a few things I am having trouble with.
1. What is the significance of overriding the build prop with the following:
Code:
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=lge_star BUILD_ID=FRG83G BUILD_DISPLAY_ID=GRJ22 BUILD_FINGERPRINT=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys PRIVATE_BUILD_DESC="star-user 2.2.2 FRG83G 2ED2ADCFFC release-keys"
Clearly its used for something, else CM7 wouldn't be doing it.
2. When I try to boot the compiled system (using either CM or EternityProject kernel), it simply stops at the LG logo, no logcat, no dmsg, nothing and after a while it reboots. What could I be missing?
I am using the init.rc from the CM7 p990 source, do I need some extra modules for it to boot? (I have added busybox and bash)
Tips on how I could debug the issue would be appreciated (any additional logs?).

I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?

fallout0 said:
I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?
Click to expand...
Click to collapse
Yea I am trying to create a device tree that will make AOSP compile and run. Its compiling just fine and it uses bits from the CyanogenMod device tree. The problem is that it wont run, it gives me no logcat output at all.
Here is the p990.mk:
http://pastebin.com/SxUZZDau
The boardconfig and proprietaries are identical to CM7. (Merged star-common and p990 configs since I have no use for p999)

Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on

fallout0 said:
Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on
Click to expand...
Click to collapse
Same problem, no dmsg or logcat.
Im gonna start from scratch now

About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.

L10nH34Rt said:
About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.
Click to expand...
Click to collapse
That would make it rather useless

KernelCrap said:
Same problem, no dmsg or logcat.
Im gonna start from scratch now
Click to expand...
Click to collapse
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied

fallout0 said:
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied
Click to expand...
Click to collapse
Im gonna try to build using the 2.3.3 gingerbread-tegra source from nvidia
EDIT: Same problem, when running something i get "Segmentation fault". I am using the gingerbread-tegra source from nvidia :S
I have the following in BoardConfig.mk:
TARGET_HAVE_TEGRA_ERRATA_657451 := true
Busybox is working fine though :/

Shouldn't the source from nvidia allow me to execute the compiled binaries without giving segmentation fault?
The funny thing is that busybox is working, and I can access dmesg through busybox.

KernelCrap said:
That would make it rather useless
Click to expand...
Click to collapse
It wouldn't if you couldn't access the market now would it?

L10nH34Rt said:
It wouldn't if you couldn't access the market now would it?
Click to expand...
Click to collapse
I'd rather have it boot atm.
Still same problem even though I have moved to the gingerbread-tegra source

IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.

L10nH34Rt said:
IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.
Click to expand...
Click to collapse
For starters I don't care about camera or hdmi, I want a clean AOSP rom - CM is great, but it includes too many extra features for my taste.

Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.

Hi guys, where i can find sources from nvidia ? I only found the kernel git...
Thank's

fallout0 said:
Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.
Click to expand...
Click to collapse
I am sure and I am using the leaked libraries too. Anything else i can try?
Sent from my Optimus 2X using XDA App

If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work

fallout0 said:
If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work
Click to expand...
Click to collapse
Will try that once I get home later today

I commented it out the following places:
Code:
./bionic/libc/Android.mk:497: ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
./bionic/linker/Android.mk:46:ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
Still not booting, now the error is (from logcat):
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
But /system/bin/sh does exists, with the following permissions (also tried with chmod 777):
Code:
-rwxr-xr-x 1 root shell 82840 sh
If I do adb shell when in recovery and executes the binary files, they all seg fault (except for busybox) :/
Here is my BoardConfig.mk:
http://pastebin.com/ZsmJp0v1

Related

[DEV][BRAINSTORM] Fully-working CWM Recovery

While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Now, I have tried to fix these but recoveries are a new domain for me and at a first attempt I couldn't bring some of these to work. Compiling the latest version was easy and an important first step towards official; however, all others I couldn't do it and I don't think we should talk with koush before fixing all this.
Here are my short attempts:
- For USB mount I defined on the BoardConfig the path for UMS lun0 file. The path seems to be correct and there's no other file in /platform/ as I've found out by running a ls -R. I have no idea why it's not working.
- For ADB, I made sure the persist.adb.service is set to 1 and the init.rc is starting it. This being said, I don't know what's missing. Perhaps this is of interest?
- For EXT4 support I thought it was just a matter of adding alternative FS to recovery.fstab. Seems I was wrong though.
So, does anyone want to join in and help?
This is really new territory to me and I have a quite faint idea of what I'm doing.
A few guidelines:
- Read this to get an idea.
- You'll need CM sources (repo init... repo sync...)
- The CWM recovery source is in /bootable/recovery
- Here is my device source and a patch file for some changes on recovery src *
- Run build commands (. build/envsetup.sh, lunch full_p970-eng, make -j4 recoveryimage)
* If you don't change what I did on the recovery source you won't have a key to select.
Also, I have CWM 4.x at the moment on my OB but since it does the same as the already posted 3.x I don't deem necessary to share it; but if anyone wants, I'll upload it.
I'll join the party when I come from the mini-vacations, hope there'll be some progress meanwhile!
Great
i'll try to do some help,maybe little
If anyone wants you can request a pull from my source.
Also, here's a flashing CWM 4.x. I renamed it Nova recovery for the lulz.
http://www.multiupload.com/R7WGNYTL7G
Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
EXT4 Backup and Restore worked for me after editing the fstab file.
For the ADB and USB mount problem i have no Idea what is missing. Like you said, adb daemon should get started througt the initscript.
BTW. seems like the Progressbar isn´t working on the newer Versions of CWM
xantaro said:
EXT4 Backup and Restore worked for me after editing the fstab file.
Click to expand...
Click to collapse
Could you release a new version or tell us how to do it? Thanks
To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto
xantaro said:
Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
Click to expand...
Click to collapse
I thought the flag wasn't suffice. Thanks.
Rusty! said:
To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto
Click to expand...
Click to collapse
Nice tip, I'll try.
knzo said:
While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Click to expand...
Click to collapse
Hey,
I know this is an old thread but still if u have not resolved the problem with ADB and USB follow these instruction:
Before we start:
My mobile is Spice Mi-410 (Qualcomm made), also known as Cherrymobile magnum, Wellcomm, Motorola triumph in different countries. So may be these tweak will not work with your device. (But you can give it a try )
I hope you know how to unpack recovery.img of your device (or boot.img if your recovery ramdisk is stored in boot.img like Xperia Arc) if not then follow this guide to unpack recovery.img and extract recovery ramdisk into a folder.
Tweak
For ADB: Open init.rc file from recovery ramdisk/initram using any editor of your choice
Put this line at the end of "on init" section
Code:
write /sys/module/g_android/parameters/product_id ####
where #### should be replaced by your device's product id.
(if you dont know what it is then connect your mobile to PC and issue "lsusb" command in ubuntu terminal, you should see something like this
Bus 001 Device 027: ID 0489:c000 Foxconn / Hon Hai
Here c000 is my devices product id and Foxconn is my device's manufacturer)
Though /sys/module/g_android is not present in our device but this worked for me.
Please note that the device id is case sensitive, so write what you see on PC
For USB: For this add following line at the end of "on boot" section in init.rc file
Code:
echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
For your device first confirm the location of /sys/class/ ###### / ####/usb_mass_storage/enable
Since this location vary from device to device.
This should enable usb storage mounting from recovery.
Best of luck!!
One option for load rootfs image in native mode is necesary
enviado

[Q] Help!! wifi error after loading compiled franco kernel

Hi All,
This is my first thread on this forum. Please help in resolving an error that I am facing. I could compile and link successfully franco kernel after downloading the source from franco's github!!
The only problem I face is with wifi. It displays error in the wi-fi option!! This is some what similar to what we used to get in the initial version of gingerbread kernel what Franco had made earlier!! I get the same error even with the stock GB source code of LG or with paulo's kernel source!!! Strange!!!!
The wifi driver(bcm4325) seems to be same except for some tweaks to the original GB source(In the case of Franco's)!! In either case, I am getting the error. The only difference I see is that of the compiler option -Ofast(Optimization option) was used by Franco while since I updated to the latest version of gcc, I do not get the -Ofast option!! So it uses the -Os option instead!!
Error is(logcat):
D/WifiService( 1726): setWifiEnabledBlocking : Country code is COM
E/WifiService( 1726): Failed to load Wi-Fi driver.
Same compiling options were used to compile both zImage and modules?? What could be wrong here? I am not sure what could be wrong here!!! Can anybody help me on this??
Thanks in advace.
I get this on sense too
(but I replaced all that Android wifi stuff,so on Sense,its wierd )
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App
dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!
franciscofranco said:
I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App
Click to expand...
Click to collapse
Yup franco. I copied to modules and then signed it with command:
"java -classpath testsign.jar testsign port.zip signed-port.zip"
I really can't understand why this is getting failed as the same compile options were used for both zImage and wireless.ko!! Rest all works fine except the wifi error!!! The idea i think is as long as all the executables are of same signature, then it should work fine, right?? I am confused on what could be the problem!!!
dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
Today I will try with other compile options, either O1, O2.... etc.
Strange thing is that I face this problem with all other available kernels also!! Like for ex., original GB source from LG, paulo's kernel!! All of it!!
shashi_hv said:
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!
Click to expand...
Click to collapse
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.
dr.notor said:
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.
Click to expand...
Click to collapse
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!
shashi_hv said:
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!
Click to expand...
Click to collapse
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko
dr.notor said:
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko
Click to expand...
Click to collapse
I know that notor!!!
I copied the tun.ko and wireless.ko to the appropriate folder and built the zip file which i flashed!!
The problem is very weird. I see the file wireless.ko if I browse thro' file manager. Even when i press tab in busybox, wireless.ko gets auto populated or even the ls command lists it!!
It is much more weird that if I tried to do insmode ....../tun.ko, i get the error as 'exec format error' but a 'no such file' for the wireless.ko!! Though I flashed both these of these!!
You know, go wipe the files in /system/lib/modules and flash your kernel and modules from the SAME KERNEL you have compiled.
Also, it is insmod, not insmode and generally if you are posting something, copy and paste the exact output of a command instead of telling us stories about what the output says.
Yup thats what i was thinking too.. i would wipe and try copying it once again.
Definitely i would have shown you the screen shots.. but i am not in a position to grab those and paste it here, as i am in office right now.. but the point is i understand some of linux system and familiar wirh it!!
I tried to create and flash the zip the standard way thats available on net and it did not worked!! Thats the point!! So wanted to know am i missing anything!!
Sent from my LG Optimus One P500 using XDA Premium App
Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...
dr.notor said:
Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...
Click to expand...
Click to collapse
I tried this!!!
1. su
2. rm -f /system/lib/modules/wireless.ko
3. rm -f /system/lib/modules/tun.ko
Now the files were not there in the directory. Flashed the same zip file which I used earlier and found the wireless.ko and tun.ko in the same path!!! But still the problem prevails!!
Just to confirm once again that I indeed copied the compiled wireless.ko and tun.ko and built the zip file!! No problem in that!!!
Why do not you try to do insmod of any existing file in the modules path and report what error you get?? I think even you should get the same error even in your phone too!! I tried this command on an already existing libra.ko in the same path and got the same error!!!
for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...
andy572 said:
for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...
Click to expand...
Click to collapse
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.
dr.notor said:
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.
Click to expand...
Click to collapse
On a different note, can anybody tell me who will load the wireless.ko and tun.ko at boot time? I mean is there any kind of scripts like the init.rc or any other *.sh scripts under /system/etc?
I tried to see in the init.qcom.wifi.sh script, but its based on the property 'wlan.driver.status'!! I dont see this property under getprop command, but added one using setprop, but no success!!!
Suggestion: restore the stock init **** and leave it alone. There is absolutely no need to mess with that to get WiFi working on any ROM. Others, like tun.ko, you need to load manually via initscript or whatever. Go fix your kernel compile and it will just work.

looking for kernel compile help

I am attempting to compile a kernel for use on a Droid 1 and so far have had no luck. I want to do some experiments on the kernel and so need to be able to compile and reload the kernel. I've done this with no problem on my Viewsonic G-Tablet and Motorola Cliq, but so far can't get a custom kernel to load on any of the ROMs I've installed on the Droid. I've used an assortment of custom ROMs, both Froyo and Gingerbread, and either one is fine for what I am doing. I've pulled the ".config" file off these running ROMs and used it on a variety of kernel versions. In most cases, I can compile the kernel with no problem and create the "zImage" file, but after repackaging the kernel and loading, the Droid simply goes to the "M" logo and hangs.
If anyone has recompiled the kernel and loaded it on a Droid, I would appreciate any assistance you can give. I'm assuming that I'm just doing something stupid, but can't see what the issue is with this Droid.
Thanks in advance,
What exactly did you want to experiment with? I've attempted replacing the kernel many times, mostly to remove the Android initrd and point the kernel to my Debian filesystem on the microSD card.
In case you need something to compare to, this is how I did it.
I'm going to assume the following:
* Your Droid is in RZRecovery and connected to computer
* Your microSD card is mounted (USB storage)
* You have abootimg and git installed (assuming you use Debian or Ubuntu)
Code:
abootimg -u $boot.img_from_cm7_update.zip -k $new_zImage
adb push boot.img /tmp
adb shell flash_image boot /tmp/boot.img
OR
Code:
git clone git://github.com/koush/AnyKernel.git
cp $new_zImage AnyKernel/kernel/
cp $kernel_modules AnyKernel/system/lib/modules
cd AnyKernel && zip -r ../update.zip *
cd .. && cp update.zip $mounted_phone_SD
# then select update.zip from recovery
I don't recall whether I had any success doing this with CyanogenMod, but for Debian I found out that I needed to enable a bunch of kernel features (TTY, framebuffer console, bootloader init checking for the LCD, and CONFIG_CMDLINE_FORCE) to get the kernel to boot. I'm still looking for true multitouch support (more than two touch points), touchscreen calibration for Debian, a fix for broken thumb support on the OMAP3430 with the 2.6.32 kernel so Ubuntu doesn't panic loading init, and/or some easy way to get a newer (Linux 3.1+) kernel ported.
I can't tell you exactly why you're stuck on the Motorola logo - it's happened to me before, but trial and error eventually fixed it.
I would say the easiest thing to do is try a CyanogenMod nightly build and then figure out exactly what it is you want to accomplish. I know at least on the Milestone where the bootloader was locked, people got creative and wrote kernel modules that did what they wanted (overclock, 5-point multitouch, etc)... Sometimes I get lost dreaming. It's kind of depressing
Check on the Kernel Manager Pro App. There is a deprimed Kernel that I'm using on my OG Droid. You may be able to get with the DEV of the Kernel and get some help.

Linux ON droid not IN android question????

Ok, this goes out to any and all DEVs out there. We all know by now that we (some people not me) can run linux within android using the loop mounts, vnc viewer, etc... Now how about REPLACING android with a linux distro like debian or maybe even what these guys use http://openpandora.org/ ..... its linux based and has an arm CPU.. Any way I'm talking about flashing over android wiping the internal sorage and installing linux on it or even using the boot loader to flash over android???, of course this is getting rid of any 3g connection and phone usage. I understand that, I am talking about giving our RETIRED droid 1s a use. I wanna see my D1 run a linux distro in full hardware mode NO MORE ANDROID. now dont get me wrong I love android as much as the next guy, but why now flash something else to it???
Another link I found, this is for windows mobile but hey, similar idea.
http://wing-linux.sourceforge.net/trac/wiki/FAQ
P.S. I AM NOT A DEV JUST AN IDIOT WITH AN IDEA!! my ignorance is NOT bliss and I would love to know if this is even possible. I'm willing to help ANY WAY I CAN. lol
THANKS!!!
I don't think it's possible. Because of the locked bootloader we're forced to use Motorola's bug-ridden Kernel and as Android's Kernel is a heavily modified Linux Kernel it most likely won't run an ordinary Linux distro.
But I'm no expert either
Milestone is locked, Droid is not ...
Maybe this will help (if you don't know german, you can use Google Translate):
http://www.android-hilfe.de/anleitu...debian-chroot-mit-lxde-auf-dem-milestone.html
Thanks for the replies. Again the USA Droid 1 is nit locked or at least has been completely unlokcked. I've read a million "run debian on android" posts... I don't need to know German to see that the post above is the same thing. Like I said before I have NO INTEREST IN RUNNING LINUX ON ANDROID. I want TO REPLACE android completely with Linux to make a device like the openpandora handheld from my first link.
Any one up to the challenge????
Thanks again!
Really, no one??
I've been running Debian on my Droid booting from the SD card for a while, more recently trying Arch Linux after realizing that anything optimized for ARMv7, VFPv3, NEON, or Thumb-2 (I'm not sure which unfortunately) won't boot because of a page fault or something. Ubuntu, MeeGo, and Angstrom just kernel panic and don't give any useful information even at the highest debugging level. I'm back to using an ARMv5te Arch Linux build (http://archlinuxarm.org) although I could just as well use Debian. I really wish Ubuntu worked for multitouch.
Well, I got the touchscreen calibrated! I forgot that my screen rotation hack only rotated the framebuffer It's stuck in portrait for now. I decided to use mtev (MeeGo's multitouch X11 input driver) after being fed up with evdev's aversion to being rotated, but now that I'm back to the stock portrait rotation evdev should work fine.
If you want instructions, either PM me or wait until I post a full guide and/or my patched kernel tree. It's not super difficult, but it's a lot of command line use and compiling.
What works:
*CPU and SD card (obviously )
*Touchscreen (single touch/portrait only for now)
What needs work:
*Keyboard mapping is wrong, the number keys and symbols don't work. I need to figure out how Android handles Alt. I had to patch the GPIO keyboard driver because the keyboard worked in the console but not in X11, which expects EV_SYN.
*Sound is OSS only, but there is no mixer device, so aumix is useless and there's no volume control or sound output.
*I haven't tried the SGX driver, so I can't comment on hardware acceleration yet.
*Battery charging relies on battd, which is a proprietary Android binary from Motorola. It might run on Debian with "ls -s / /system" and the creation of the socket it expects (init.sholes.rc I believe), but I'm not getting my hopes up.
Untested:
*WiFi (needs firmware, but should work)
*Bluetooth
*Calls/data
*Sensors (although the accelerometer and compass seem to be recognized by evdev)
I'll upload my kernel, either as patches or on GitHub (or binaries if there's enough demand) once I get around to fixing the keyboard issue. Fingers crossed that I don't get carried away cleaning up the kernel, or worse yet, give up...
This is incredible news! I'm so glad to hear it. Of course you are running in hardware mode? Not through android? If so I'm super exited about this! I love arch Linux, I run it on all my computers and I understand it more than any other distro I've tried. I would love to give it a shot, though I'm not that great at compiling I think it will be worth it.
As I said before I am in no way a dev or even a Linux pro, but I can get by and if theres any way I can help this project become "complete" I'm willing to learn what ever is necessary to do so.
Also were u able to get an x server running? Possibly a DE? That would be crazy awesome.
Thanks a million, looking foreword to work with you and make this happen!
For anyone who's interested, I put together a quick package containing my kernel patches, configuration notes, and an automated kernel build script.
It's pretty self-explanatory aside from the installation of the root filesystem, which I leave up to your imagination
As I've probably repeated several times now, I've run Debian and Arch Linux natively on my Droid with my patched kernel (no chroot or VNC "hack"). With enough determination, it's possible to run practically anything on it - personally, I'm determined to get Ubuntu on it.
WOOT... insta-fail for me LOL you have it set up to work in specific directories? I thought i placed everything right but I guess not.. I got an error on the first line of output lol
Welcome to gTan64\'s lazy Droid kernel compiler\!
build.sh: line 5: [: missing `]'
build.sh: line 5: -z: command not found
build.sh: line 5: -z: command not found
Entering $WORK
Applying patches
build.sh: line 16: /*.patch: No such file or directory
mv: cannot stat `/arch/arm/boot/compressed': No such file or directory
cp: cannot stat `/compressed': No such file or directory
Setting up build
cp: cannot stat `/GNUmakefile': No such file or directory
cp: cannot stat `/sholes_config': No such file or directory
FIXME! No numeral or symbol input until someone finds a third-level
modifier key to use instead of AltGr for the keyboard.
cp $MISC/defkeymap.map $K_SRC/drivers/char
Building kernel!
make: *** No targets specified and no makefile found. Stop.
Kernel build done!
You have done something amazing, I'm just to stupid to figure it out my self. XD
I can understand why you would want ubuntu with all its pre-setup glory and support for nearly all hardware but dont you think its a little heavy for this hardware? lol I doubt you would try to use the Unity UI but I doubt that alone would even fit in ram LOL you could just use the ubuntu packages and drivers with debian maybe?
THANKS AGAIN!!!!
That's what happens when I don't test my own scripts
I was thinking too much about making it easy. Just try applying my patches to your tree manually.
Code:
cd kernel_src
patch -p1 <../patches/first.diff
patch -p1 <../patches/next.diff #and so on...
#Obviously, substitute the paths of the actual patches ;)
#Finally, copy sholes_config to .config and invoke 'make'.
It's actually much simpler than my script makes it, and you don't need my convoluted folder setup.
UM lol I cant find any patch files? are they in the ZIP? or do I have to obtain them elsewhere?
I can tell this is gonna be a hell of a project LOL
THANKS!!!
"Duh" moment - I used the .diff file extension instead of .patch
I'm such a scatterbrain... Remind me not to release anything before testing
EDIT: Strike that, reverse it. They're .patch files.
I AM BLIND lol I found them... BUT.. when I try to patch. terminal just seems to lock up... I press enter, the curser moves to the next line but it doesnt do anything. lol how long should 1 patch take?? its been about 10 minutes and I leave it be for now
EDIT:
LOL i forgot the "<" in the command OOPS but I'm not seeing any .config file or folder in the source to copy the sholes_config too. yes I have show hidden files on.. PS unfortatly usinf Fedora 15 gnome 2...... (on server so I can work on this anywhere through vnc )
THANKS
When I said "copy sholes_config to .config", that's literally what I meant. .config is the Linux kernel build configuration file, not a folder.
'cp /path/to/sholes_config .config' from your kernel tree should do it.
Oh, I forgot to mention that you need an ARM cross-compiler/toolchain. I use the gcc-arm-linux-gnueabi package in Ubuntu, but I don't know what the Arch equivalent is off the top of my head.
The "GNUmakefile" is just a convenience, it exports "ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-" before calling the actual makefile. If you don't have an ARM cross compiler in your path, it won't build at all. If you do, modify CROSS_COMPILE to point to it - on some systems it's called arm-unknown-linux-gnueabi, etc. etc.
Let me know if you get anywhere before it errors out.
OK I put the config file in the kernel_src but unfortainatly I'm using Fedora 15 XP I installed arm-gp2x-linux-gcc which is the fedora arm gcc I guess... lol so wha would I edit in the .config to make it point to arm-gp2x-linux-gcc. Its not my first attempt to compile an android kernel but I've never been succesfull LOLOL
thanks
I'm pretty sure that toolchain won't work - the GP2X was ARMv5 IIRC, so unless it's a newer build of GCC (4.3 or higher) and you're absolutely sure it supports the ARM EABI and the ability to generate ARMv7 instructions (which is unlikely if it's pre-4.1), I would recommend a newer toolchain.
CodeSourcery makes a pretty solid one: https://sourcery.mentor.com/sgpp/lite/arm/portal/release1803
If you end up using it, you can change the second line in GNUmakefile to "CROSS_COMPILE=arm-none-linux-gnueabi-". Don't worry about changing .config.
Well I DLed the linux/GNU installer and it gave me "arm-2011.03-41-arm-none-linux-gnueabi.bin" LOL
so I was thinking would it just be easier to just use my lappy with crunchbang (debian based) so I can follow ur instructions with deb / apt-get LOL fedora is a ***** and it dont have what I need... I cant find an arm v7 cross compiler for it
thanks
.bin files are the Linux equivalent of Windows EXE installers. Run it like this:
Code:
#cd /path/to/installer.bin
./installer.bin
#substitute the actual name, of course.
It needs root permissions if you want to install it to /usr/local (sudo ./installer.bin or su -c 'sh installer.bin'). You can also install it to /usr, but that will make it more tedious to uninstall later. If you decide to install it in your home folder - say ~/toolchain - you don't need root permissions, but you will need to add ~/toolchain/bin to your path:
Code:
export PATH=$PATH:$HOME/toolchain/bin
To be honest, I prefer Ubuntu to Fedora/OpenSUSE/$RPM_distro, so if you have access to a Debian or Ubuntu system, using that would make my life easier
Omg duh... the "non_Linux" part of the name true me off lol i'll start doing this on my laptop it's deb based crunchbang. I prefer anything over rpm distros too but it was a quick painless install on my server XP thanks ill try this when I get home
Sent from my DROIDX using XDA App

HP Touchpad running Ubuntu Touch

THIS THREAD IS NOW OUTDATED. Page 17 and on contains information for Ubuntu Touch Saucy port.
NEW THREAD ON THE WAY.
http://forum.xda-developers.com/showthread.php?t=2426924
What works. Wifi+ADB+Touch.
What doesn't work: Sound+Bluetooth. Bluetooth doesn't work yet in Ubuntu Touch, and Sound doesn't work with the Evervolv source. Camera.
Download these files.
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip Ubuntu Touch RootFS
Recovery Image.
http://gdurl.com/A0mz/download
Put on your SDCARD and install in ClockWorkMod. You know.. when you first turn on the tablet, moboot loads.. you should see a menu for clockwork recovery mod.
EDIT: Oh yeah.. First do a factory reset in recovery mod, THEN install the zip files... The factory reset formats the cm-cache and cm-data partitions.. There are 3 partitions. cm-cache cm-data cm-system. Factory reset formats cache and data.. When you install the first zip, it formats the system partition. Then after that install the RootFS.zip that you downloaded from ubuntu... It extracts the RootFS to the cm-data partition, that you formatted. So it should be clean.
Reboot.
Enjoy!
Oh yeah.. Onscreen Keyboard is not sized right. Seems to be an Ubuntu bug... If your fonts are wrong. .reboot.. check out /system/etc/init.d/90userinit for the stuff I added.
thanks to the usual guys. JCSullins, Evervolv, Tigeris and litz and ompx in ubuntu-touch on irc. The wifi fix was an idea I got while stuck in traffic. Can't believe it worked.
Oh yeah.. THANK YOU DR. MARBLE.
PS. I read somewhere you need at least 600MB of free space, AFTER you copy the files to the sdcard, for the extraction to go well...
nice
Awesome, can't wait to try this out!
How to install that on tp?
Way too cool!! tnx for all the hard work
tux-world said:
How to install that on tp?
Click to expand...
Click to collapse
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.
Crazy how the font turned out like that
Sent from my SAMSUNG-SGH-T989 using xda premium
Great news
SGA, thanks for your effort in bringing Ubuntu touch to Touchpad!
If you need help with testers, let me know
Vistaus said:
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.
Click to expand...
Click to collapse
is this CM?
tux-world said:
is this CM?
Click to expand...
Click to collapse
No. It's Ubuntu Touch, but from what I have heard on XDA Developer T.V. (check 'em out on YouTube) it is based on CyanogenMod.
Sent from my Xperia S ~XZXperience~Unlocked BL~Rooted~6.1.A.2.55~
I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app
What source did you use to compile? I tried to compile it and kept getting some weird error got frustrated and gave up.
blmvxer said:
I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I think that's how it will always be. The core zip is device specific and contains the CM base while the phablet zip is for all devices.
Off to 3.0.8
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Going to try a newer kernel to get wifi working. We need Fanotify in the kernel for the network manager to see the wireless. Has to do with proc mounted inside of a chroot and daemons having permission. Sad because once you run ubuntu_chroot shell to get in, you can run iwlist wlan0 scan...
Status Update Complete.
How to compile. Grab evervolv's device folder, but not his vendor folder.. grab hardware/qcom hardware/atheros and the compat-wireless from.. some folder.. forgot the name... I got these from evervolv's ubuntuphone branch for tenderloin.. (the kernel) and his build of android.
Those are the current sources.. May change.. Be sure to change ev.mk file to cm.mk, and change /vender/ev (inside of ev.mk) to /vendor/cm, ev.dependencies file to cm.dependencies....
JCSullins announced he will start work on JB. So that is cool. But.. 3.0.8 Kernel doesn't have working sound or bluetooth. Until someone figures that out with 3.0.8, Ubuntu-Touch and the Touchpad WILL NOT HAVE SOUND. (cough cough nag jcsullins cough cough).. That guy is the man to go to for that.
Backporting Fanotify is not easy. You run into having to change the msm code. (I ran into msm-watchdog.c) So much you might as well just go to 3.0.8.. I have an odd feeling that is someone were to backport it, sound would stop working....
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Backup you jellybean system folder to a tarball and then extract it somewhere.. Same with the Ubuntu Touch system folder.
(I was about to give up!)
cp -R -f /jellybean/lib/* /system/lib
cp -R -f /ubuntutouch/lib/* /system/lib
cp -R -f /jellybean/etc/firmware/* /system/etc/firmware (my adreno firmware was missing, so this will fix that)
reboot.. and it worked.. merged libraries.
Fonts are not bad all the time..... Going to try this with 3.0.8 tonight.. If someone is bored today, give it a shot. Let us know how it works.
To brunch tenderloin I have to manually create out/host/linux-x86/bin and stick mkimage in there.
go to vender/cm/vendersetup.sh and add add-lunch-combo cm-tenderloin-userdebug.. I think.
there is a mkimage in the ubuntu touch source.. I used that. /system/extras/mkimage.. it needs to be compiled gcc mkimage.c -o mkimage -lz
then copy it cp ./system/extras/mkimage/mkimage ./out/host/linux-x86/bin no idea if this is required.
there are 2 bzr branch commands that need to be run.. google that.. Should be in Ubuntu Porting guide, but it's not. ubuntuappmanager library and some other library.
edit: run this inside of the ubuntu touch source folder/ubuntu
"bzr branch lphablet-extras/libhybris hybris" stupid smiles. =)
"bzr branch lplatform-api platform-api"
http://forum.xda-developers.com/showthread.php?p=38745624
dont forget to run extract-files.sh and get-prebuild, etc.
source build/envsetup.sh
lunch (pick 14)
brunch tenderloin
I bring over ts_srv and that other ts program from jellybean to ubuntu and currently add commands to /system/etc/init.d/90userinit to get stuff running.. Lazy, I am.
Confused? That is my rough draft guide.
A dude by the name of tigeris, or something that started with tig.. he helped me a lot on ubuntu-phone on irc. So did another guy named.. omxy.. I think... I will find them. Gotta go,
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
My wife would really like someone to pick this work up.. She wants me to .. "come back to the family"....
Oh yeah.. Wifi does work.
To get wifi working..
do this.
ubuntu_chroot shell
mount -o proc proc /proc
network manager should now bomb.
this is for open security.
ifconfig wlan0 essid "your essid"
ifconfig wlan0 up
dhcpcd wlan0
dhcpcd taken from jellybean tar.gz from the bin folder.. So.. yeah.. but no network-manager without fanotify and some other daemons. be sure to take dhcpcd stuff from etc.
DONT RUN ubuntu_chroot all by itself.. It will crash.
ALSO you MUST unmount proc before shutting down or it will be stuck in mtab and you will have old stuff inside of the /proc folder, inside of chroot, or rather /data/ubuntu/proc..
Problems? Restore ubuntufs tarball in recovery.
I will release something sometime soon.. after testing 3.0.8.. but if you know how to do all this stuff, be my guest.
Why don't you create your own github and share with us?
I bet that there are a lot of devs who want to continue.
I am really interested but I kind of got lost when you said to get the files from Evervolv... Can you post links to be more specific please?
Thank you.
Its just githib.com/evervolv
Sent from my Touchpad using xda premium
Doing that tonight... By the end of tonight I will release something..
It will be 3 files.
The first will be the .zip file that has the actual /system folder
second is of course from ubuntu and is the rootfs.
Third will be a tarball you guys can extract once the tablet is booted that will just have touch and graphics working. You can use wifi if you run it from adb, and keep the tablet powered on.
I haven't even touched pixel ratio.
Oh.. a 4th file.. of the whole ubuntu touch folder.. cleaned and made proper.. Uploaded to google drive.. Or hell I guess I can look at github...
Gotta play mario with my little girl first.
jshafer817 said:
Gotta play mario with my little girl first.
Click to expand...
Click to collapse
LOL
Gotta always spend time with them :good:

Categories

Resources