The project is pretty much dead as it was a more or less a proof-of-concept, and our touchscreen drivers aren't built into the kernel, and I can't get past the device encryption screen, but I've got a Moto X stock image "booting" on my Razr M I'll upload it sometime today or tomorrow in the form of a TWRP backup in case anybody wants to tinker around with it and try to get this thing booting 100%
Hopefully if I get some free time, I can tinker around with it and maybe rebuild the boot.img and remove the encryption flag in the fstab, and see if there's something I missed regarding the touch screen. The Razr HD guys might have a better shot at as their touchscreen isn't like ours, and could potentially work.
It appears as if this 3.4 kernel on the X might make it into our 4.2 ROM (whenever that will come out), and that's why Motorola's taking a long time to get from 4.1 to 4.2
[email protected]:/ # cat /proc/version
Linux version 3.4.42-xline-gfd1a699-00157-gfb2f8fc ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jul 18 20:25:42 CDT 2013
Here's some images I've got of the goods: http://imgur.com/a/MfIRQ
Update: the touch issue is due to an invalid devtree, which is proprietary. Once kernel source drops, I might be able to manually override the kernel source to not detect the touchscreen via the devtree, but rather, hardcode it to use our touchscreen
Update 2: Boots! http://imgur.com/j9dMtR7
Still no touchscreen and probably won't happen anytime soon now we wait for kernel source
Source should be out soon ... then CM will get it
And there are some annoyances anyway, such as checking SHA1 checksum for modules.
As for the ROM, use devtree from RAZR M! You'll also need to update a few XMLs in the framework.
Skrilax_CZ said:
Source should be out soon ... then CM will get it
And there are some annoyances anyway, such as checking SHA1 checksum for modules.
As for the ROM, use devtree from RAZR M! You'll also need to update a few XMLs in the framework.
Click to expand...
Click to collapse
I never changed the devtree so it's still the Razr M's one. I got an error in the dmesg saying invalid header in the devtree or something like that. Do you think we will need a new devtree for this 3.4 kernel?
Here's a dmesg output: http://pastebin.com/dpHwBddu
That line 34 is where I feel that the current 3.0.31 devtree for the Razr M might be incompatible with the 3.4 kernel
Sent from my XT907 using xda app-developers app
Ah I see. So we'll have to use our own devtree. Not a real problem, but it's easier to wait for the source and adapt our platform.
@JackpotClavin: Kernel source is out: http://sourceforge.net/projects/ultra.motorola/files/XT1080-XT1030/
btw. did you extract the defconfig from the kernel?
Skrilax_CZ said:
@JackpotClavin: Kernel source is out: http://sourceforge.net/projects/ultra.motorola/files/XT1080-XT1030/
btw. did you extract the defconfig from the kernel?
Click to expand...
Click to collapse
http://pastebin.com/kWqaWyB1
I literally just checked the opensource website like a half hour ago and it wasn't up then
That's from the Roger's sbf on your sbf website (thanks for that btw!)
Making progress on the device tree. I've got it to load up so far (it wasn't recognizing it before)
Hmm, the command to decompile devtree is "dtc -I dtb -O dts devtree.dtb > devtree.dts." right? It somewhat kicks me on bad magic when I extract devtree from the FXZ and also cut the first x bytes (so the magic is first).
I've never decompiled a devtree before. Is the one you're trying to decompile for the Moto X or the Razr M?
Originally, the devtree wasn't being read at all by the processor, then the only change I made to the kernel was for endianess format for compatability for the older devtrees (like the one the Razr M still has from the 3.0.31 kernel). Perhaps once the 4.2 upgrade comes around, they will update the devtree to be compatible with the 3.4 kernel, which will probably use big endian format like the Moto X does.
https://github.com/epinter/android_...mmit/8033dcc5ed05cb5ab52539acfd0cbee65a518863 (cherry-pick)
https://github.com/epinter/android_...mmit/c6dfc183e9ad497384ce5d99f088255a572c9193 (cherry-pick)
https://github.com/epinter/android_...n/blob/cm-10.1/arch/arm/mach-msm/Kconfig#L687 (add line #687)
It will get the 3.4 kernel to recognize a 3.0 kernel devtree
It's for Photon Q (same series as Razr HD / M etc.) and I think not all the phones from the Razr HD / Razr M / Photon Q / Atrix HD will get a 4.2 upgrade (somewhat looks to me that only Razr HD will get it). Besides we're not waiting just for that, are we
Skrilax_CZ said:
It's for Photon Q (same series as Razr HD / M etc.) and I think not all the phones from the Razr HD / Razr M / Photon Q / Atrix HD will get a 4.2 upgrade (somewhat looks to me that only Razr HD will get it). Besides we're not waiting just for that, are we
Click to expand...
Click to collapse
I think you know more than you are letting go
BTW do you think the sources for the x will help you guys with the work for the 3.4.y kernel and the other moto q com phones in CM?
It appears as if the devtree is written in a different structure from what the 3.0 kernel used which is making it annoying to direct the kernel to certain branches of the devtree. Things like parsing the devtree for the tdat filename which is needed for our touch interface is mapped out differently from 3.0 and I'm trying to put them together to work with the 3.0 devtree until we get one that's actually meant for the 3.4 kernel
Sent from my XT907 using xda app-developers app
@Skrilax_CZ Did you happen to see the devtree source files in the MotoX kernel source?
In arch/arm/boot/dts there's the source to make device trees.
make -j1 CROSS_COMPILE=arm-eabi- ARCH=arm msm8960ab-sasquatch-p2.dtb yields a .dtb file in arch/arm/boot that's supposed to be a devtree, but when I flash it on my device, the devtree still isn't recognized and there's no filesystem generated at /proc/device-tree. Do you think there might have to be an offset or something?
In devtree partitions, there are 5 interger values at the beginnig and the devtree is in little endian, instead of big endian.
How is this going guys?
Sent from my SCH-I535 using Tapatalk 4
Is there anything that we amateurs can help out with?
Sent from my XT907 using XDA Premium 4 mobile app
I'm definitely interested in this project. Touchless control, active display (!!!), assist, trusted devices, and motorola connect!
There isn't really anything we can do until the devtree is sorted out. I think we will have to wait until there's an official build with a 3.4 kernel and 4.2 from Motorola. I'm sure it isn't too far away
Sent from my XT907 using xda app-developers app
JackpotClavin said:
There isn't really anything we can do until the devtree is sorted out. I think we will have to wait until there's an official build with a 3.4 kernel and 4.2 from Motorola. I'm sure it isn't too far away
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Since the touchscreen isn't currently working, you should use an OTG cable w/a mouse so you can navigate throughout the phone and see just how much of the rom actually works
I'll give it a try... Any new news on this project? I went to a vzw suite and their X is running 4.2.2...
Sent from my XT907 using XDA Premium 4 mobile app
Related
This method should work for Android 2.2 releases. This only works for 1.2.6 and 1.5.7. It does not work with 1.8.3, and so will almost surely not work for Android 2.3 releases. They have said the week of July 8th they will release the 1.8.3 source. As an alternative, I have figured out how to load a sbf from Latin America that is also Android 2.2.2, and we have it's kernel source. I have tested compiling a custom kernel for it, and it works. I advise only people interested in playing with custom kernels use this method.
Install Ubuntu Maverick with the gnueabi.
Packages:
binutils-arm-linux-gnueabi
cpp-4.4-arm-linux-gnueabi
cpp-4.5-arm-linux-gnueabi
g++-4.4-arm-linux-gnueabi
gcc-4.4-arm-linux-gnueabi
gcc-4.4-arm-linux-gnueabi-base
gcc-4.5-arm-linux-gnueabi
gcc-4.5-arm-linux-gnueabi-base
gcc-arm-linux-gnueabi
Argentina SBF
Run sbf_flash -x against it to break it into CG files. You only need CG56(boot), CG57(system), and CG58(webtop). You might be able to stick with the 1.8.3 AT&T webtop, I haven't tested.
Use fastboot to write them to the phone. It has to be moto-fastboot.
fastboot flash system CG57.img
fastboot flash webtop CG58.img
Use split_bootimg.pl to split CG56 into the kernel and ramdisk files.
Once you have compiled your own kernel
fastboot flash:raw boot zImage CG56.img-ramdisk.gz
Compiling a custom kernel
Download /proc/config.gz from a phone running the release you want to compile a kernel for
mkdir ~/atrix-kernel
cd ~/atrix-kernel
tar zxf ~/kernel.tgz
cp -a ~/config.gz .
gunzip config.gz
cp -a config .config
Edit .config if you want
export ARCH=arm
export CROSS_COMPILE=arm-linux-gnueabi-
make oldconfig
make zImage
make modules
The resulting zImage is arch/arm/boot/zImage.
Use an existing ramdisk. Modify it if you want.
On phone:
dd if=/dev/block/mmcblk0p11 of=/tmp/boot.img
On computer, as root:
mkdir /mnt/boot
mount ~/boot.img /mnt/boot -o loop,ro
Use split_bootimg.pl to pull the ramdisk.gz out of boot.img
Read more at http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
If it mounts, you have the boot image. I can't guarntee it is mmcblk0p11 in all cases. It should also be 8mb.
fastboot flash:raw boot zImage ramdisk.gz
or
fastboot flash boot boot.img
If you want to change kernel command line arguments use mkbootimg. Run dmesg | less on your phone to copy YOUR kernel arguments.
Example:
mkbootimg --kernel zImage --ramdisk ramdisk.gz --cmdline "[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo androidboot.serialno=AGGB2I1532" -o boot.img
moto-fastboot
http://forum.xda-developers.com/showthread.php?t=1138092
fastboot 64-bit
http://forum.xda-developers.com/attachment.php?attachmentid=634867&d=1308871353
fastboot 32-bit
http://forum.xda-developers.com/attachment.php?attachmentid=635031&d=1308879588
mkbootimg 32-bit, should work for 64-bit if you have the libraries:
http://proton.cygnusx-1.org/~edgan/mkbootimg
split_bootimg.pl
http://code.lardcave.net/entries/2010/11/24/164025/split_bootimg.pl
http://zen-droid.googlecode.com/files/split_bootimg.pl
sbf_flash
http://blog.opticaldelusion.org/2010/05/sbfflash.html
1.2.6 AT&T kernel.tgz
http://sourceforge.net/projects/atrix.motorola/files/Atrix ATT/OLYFR_U4_1.2.6/kernel.tgz/download
0.50.0 Personal Argentina kernel.tgz
http://sourceforge.net/projects/atrix.motorola/files/Atrix LATAM/OLYLA_U4_0.50.0/kernel.tgz/download
Excellent work Edgan!
i've been fumbling around for a while now getting things set up, i wish i would have known this before.
thanks for the post/instructions!
this is what moto says about it:
https://sourceforge.net/projects/atrix.motorola/files/Atrix ATT/OLYFR_U4_1.2.6/
1. Create a workspace containing vanilla 'android-2.2.1_r1' release from Google.
2. Overlay Motorola-provided published repos on top of original Google versions.
3. Build user space components (see end of this document for the list of supported targets):
cd <workspace>
. build/envsetup.sh
lunch generic-user
make TARGET_BOARD_PLATFORM=tegra TARGET_ARCH_VARIANT=armv7-a \ arch_variant_cflags="-march=armv7-a -mtune=cortex-a9 -mfloat-abi=softfp -mfpu=vfpv3-d16" \ BOARD_HAVE_BLUETOOTH=true BOARD_HAVE_BLUETOOTH_BCM=true \ BOARD_GPS_LIBRARIES= WPA_SUPPLICANT_VERSION=VER_0_6_X <list-of-targets>
4. Building kernel and kernel modules.
cd <workspace>/kernel
export ARCH=arm
export CROSS_COMPILE="arm-eabi-"
make tegra_olympus_android_defconfig
make FACTORY_BUILD=false BUILD_ID=OLYFR_U4_1.2.6
cd <workspace>/vendor/bcm/wlan/osrc/open-src/src/dhd/linux
make ANDROID_BUILD_TOP=<workspace> BUILD_ID=OLYFR_U4_1.2.6
Appendix A: list of supported targets
out/target/product/generic/system/bin/bluetoothd
out/target/product/generic/system/bin/brcm_patchram_plus
out/target/product/generic/system/bin/busybox
out/target/product/generic/system/bin/dnsmasq
out/target/product/generic/system/bin/dumpe2fs
out/target/product/generic/system/bin/dund
out/target/product/generic/system/bin/e2fsck
out/target/product/generic/system/bin/hciattach
out/target/product/generic/system/bin/iptables
out/target/product/generic/system/bin/iwconfig
out/target/product/generic/system/bin/iwevent
out/target/product/generic/system/bin/iwgetid
out/target/product/generic/system/bin/iwlist
out/target/product/generic/system/bin/iwpriv
out/target/product/generic/system/bin/iwspy
out/target/product/generic/system/bin/mke2fs
out/target/product/generic/system/bin/pand
out/target/product/generic/system/bin/resize2fs
out/target/product/generic/system/bin/sdptool
out/target/product/generic/system/bin/tc
out/target/product/generic/system/bin/tune2fs
out/target/product/generic/system/framework/jcifs-krb5-1.3.12.jar
out/target/product/generic/system/lib/bluez-plugin/audio.so
out/target/product/generic/system/lib/bluez-plugin/input.so
out/target/product/generic/system/lib/liba2dp.so
out/target/product/generic/system/lib/libbluetoothd.so
out/target/product/generic/system/lib/libbluetooth.so
out/target/product/generic/system/lib/libext2_blkid.so
out/target/product/generic/system/lib/libext2_com_err.so
out/target/product/generic/system/lib/libext2_e2p.so
out/target/product/generic/system/lib/libext2fs.so
out/target/product/generic/system/lib/libext2_profile.so
out/target/product/generic/system/lib/libext2_uuid.so
out/target/product/generic/system/lib/libiprouteutil.so
out/target/product/generic/system/lib/libnetlink.so
out/target/product/generic/system/lib/libwbxmlparser.so
out/target/product/generic/system/xbin/avinfo
out/target/product/generic/system/xbin/hciconfig
out/target/product/generic/system/xbin/hcitool
out/target/product/generic/system/xbin/l2ping
i had problems compiling, but i hope tonight my luck is better. vanilla compiled fine, but not after i added the Atrix stuff to it.
i took everything and untar'd it in my working directory and created any directory structures that didn't exist, but i was a little uncertain as to what to do with a handful of them, like the kernel.tgz. you supposed to created that directory then untar it?
Should be stickified. This will be a useful resource for prospective rom builders.
Sent from my MB860 using XDA App
This is awesome! Thank you. I have been playing around with a build environment for a day or two. When I try the "make tegra_olympus_android_defconfig " it spits out an error at me...prolly missing something.
Sorry, I don't really know all that much about this, but could we use this to compile CM6? It wouldn't be ideal, but would be better than stock until someone who knows what they're doing makes a CM7 build.
Sent from my MB860 using XDA App
lunder said:
Sorry, I don't really know all that much about this, but could we use this to compile CM6? It wouldn't be ideal, but would be better than stock until someone who knows what they're doing makes a CM7 build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
kholk said earlier he got CM7 and will release when he is home.
anyways
I got my kernel build, now how do i use it to create a custom rom, could someone point me towards the info, or atlest give me som sort of hint!
samcripp said:
kholk said earlier he got CM7 and will release when he is home.
Click to expand...
Click to collapse
Some point me in the direction of where this was stated... been away from the computer since Friday... thanks
Swiftks said:
Some point me in the direction of where this was stated... been away from the computer since Friday... thanks
Click to expand...
Click to collapse
he said this on irc
samcripp said:
he said this on irc
Click to expand...
Click to collapse
did he say he had it or he was working it... to my understanding, porting CM7 is a long task. dont get me wrong, kholk is phenomenal but its hard to belive development has started, and its released soon. would be nice though, maybe hes been working hardcore on it and the port is going smoothly
Regardless, either way it's good news. I also hear that the official CM7 dev team is getting or has already gotten a Atrix too. Hope that maybe some time in the not to distant future we can get an "official" CM7 rom, built specifically around the Atrix & its hardware.
Sent from my MB860 using XDA Premium App
Swiftks said:
Regardless, either way it's good news. I also hear that the official CM7 dev team is getting or has already gotten a Atrix too. Hope that maybe some time in the not to distant future we can get an "official" CM7 rom, built specifically around the Atrix & its hardware.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
agreed bud, couldent have said it any better
how many of you could compile an oc kernel? maybe thermal throttling disabled
anybody already working on it?
Swiftks said:
Regardless, either way it's good news. I also hear that the official CM7 dev team is getting or has already gotten a Atrix too. Hope that maybe some time in the not to distant future we can get an "official" CM7 rom, built specifically around the Atrix & its hardware.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Kholk has a engineering device and not a retail ATT model.
It is completely realistic that he could have a CM7 build that he was developing the whole time on his device but waiting for the bootloader to get unlocked to release it.
We just have to wait and see what goodies kholk desides to release.
Edit: sorry this is all way off topic and I should not have added additional comments based on off-topic items.
we will be getting a 4.1.83 source release around the 7 or 8th of july.
Watch out my thread at moto's open source forum:
http://sourceforge.net/motorola/atrix/discussion/general_comments/thread/c63fc4c9/
franciscojavierleon said:
we will be getting a 4.1.83 source release around the 7 or 8th of july.
Watch out my thread at moto's open source forum:
http://sourceforge.net/motorola/atrix/discussion/general_comments/thread/c63fc4c9/
Click to expand...
Click to collapse
That is great news. We are dying on irc without those
Sent from my MB860 using XDA Premium App
That is great news That the 4.1.83 kernel source is coming out in a week or so. Since it has not released yet, we won't be getting a 2.3.4 kernel for a bit I don't think. I am a bit new to this kind of stuff.
If you have an AOSP system.img and ram disk, do you just package the ram disk with the kernel into a boot.img and run it (and maybe pray )? I don't believe its as simple as that but that is why I ask
What channel are you guys hanging out on re: IRC? I would love to chip in on the kernel dev/community rolls as I have a lot of relevant experience.
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.
Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse
Woohoo! Look forward to trying this!
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Great work, thanks! I'm glad that there is work going on!
Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium
Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!
Wow!! Keep up the good work!!!
can't wait, great work!
Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia
obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.
this isnt for the K1 is it
It's for tpt only
When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?
TPT= ThinkPad Tablet
Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.
Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.
mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.
I have put this project on hold for now. I flashed latest Austrian ICS build to my device and continue using it as my Kindle reader on my travels. IF somone manages to fix the two issues with kernel, send me a message and I'll continue working with the repository. But for now I'm not thinking nor touching the subject before Easter. Thank you for participating for now
I've started porting Ubuntu-touch dev-preview to the Galaxy Tab 7.7 (3g). If you do not understand it already, you flash this at your own risk. There is now also a Ubuntu-touch specific device page here: https://wiki.ubuntu.com/Touch/Devices/p6800. I'll try to keep this thread and the Ubuntu devices page as close to each other as possible.
Big thanks to Daniel_hk for helping with boot.img Now It can be booted, but the screen is still black
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
Code:
[email protected]:/# uname -a
Linux localhost 3.0.15-CM-g1dc3074 #2 SMP PREEMPT Wed Mar 13 00:43:37 EET 2013 armv7l armv7l armv7l GNU/Linux
Repositories:
Latest release tagged with: "v0.3", not tested!
https://github.com/dun1982/android_device_samsung_p6800
https://github.com/dun1982/android_kernel_samsung_p6800
Download
cm-10.1-20130312-UNOFFICIAL-p6800.zip
Daily Ubuntu image: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
Installation
Install CWM 6.0.2.8
Wipe data/factory reset
Wipe cache partition
Flash cm-10.1-20130312-UNOFFICIAL-p6800.zip to device
Flash quantal-preinstalled-phablet-armhf.zip to device
Reboot
Starting to use
Then it gets interesting (Black sreen for now now Run the following commands in your desktop system:
Code:
adb root
adb shell
ubuntu_chroot shell
You should have now root access inside your tabled. Continue with this wiki next
What works
Ubuntu-touch dev-preview is flashable.
It boots!
Known Issues
Kernel is based to the CyanogenMod/android_kernel_samsung_smdk4210, but it is a mess. So forked it, took code here and there (mostly from locerra's JB build).
Kernel is based 3.0.15 and no newer one available (yet).
Most of the drivers in kernel had to be turned off, because build was not succeeding...
bluetooth: Doesn't work
audio: Dock audio doesn't work.
hwcomposer: HDMI dongle doesn't work.
wifi: Doesn't work.
camera: Doesn't work.
.. and lot of kernel level bugs for sure.
Displaydrivers are not working (yet).
Release notes
Version 0.2 (13.03.2013) - Now it boots, see release notes
Version 0.1 (07.03.2013) - Intial release, nothing works
Credits
BIG THANKS to daniel_hk for solving the boot.img problem for me.
Anyone who has worked previously with the device/kernel source.
locerra (for getting CM10.1 to flashable state).
wowww!!! thank you !test now:victory::victory:
Placeholder for future.
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Not 6810 versión?
AUs
el_campi said:
Not 6810 versión?
AUs
Click to expand...
Click to collapse
I cannot test it for anything else. The kernel sources are from CM10.1 that was in use from locerra, so in theory it should work with i815 and with p6810 as well. But I cannot give you any guarantees...
And also before I get this build to even start with my device, I do not think that sharing image would help anyone. But if you are a developer, I would like to talk with you on issues that I might have missed or done wrong. So contact me
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
any update?
Sent from my GT-P6800 using xda premium
Not much. The generated image is missing /data/ubuntu completely and that is the reason why the image does not boot. I got also flu and fewer, so I have had not that much time after the weekend to look on the issues on that.
I'm also waiting if I get any answers from Ubuntu touch emailing list regarding the problem and where to look for answers, but my quess is that it has something to do with the devices fstab file...
Good news everyone!
Just got a very good answer the problem I had with the /data/ubuntu-folder missing from the image. There was no image provided for the actual Ubuntu at all by the build-process...
When I get home from work, I'll try to find time to look into the build process if I can include the actual Ubuntu image to the ready made image and then release it after I get my device to boot. But it seems that I got the right nudge forward for this now :highfive:
Hmpf, still not booting. Now the /data/ubuntu logs are unmodified, which would point towards kernel or fstab-issue (ie. /data/ubuntu is never used...).
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Good job :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my GT-p6800 using xda premium
Doh... still not working... Any ideas anyone?
Ok, new version build from different repositories (thx, danile_hk for tip).
I'll test the new image this evening when I get back to home, and I have my fingers crossed that I can get the device to boot up and even display something useful. After that I can start looking for ubuntu developemnt
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
dun1982 said:
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
Click to expand...
Click to collapse
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
It seems that I hit the wall (again) with the mentioned big issues.
For now, I keep some sabbatical from Ubuntu Touch things (ie. I flashed ICS Austria to my device) and use it as my Kindle reader again.
If by miracle I get more info regarding how to get the Kernel working with Ubuntu Touch, then by allmeans I continue working with this project. So far it just seems that making a working image, is out of my hands currently.
At least you had a go. Thanks for your efforts, and hope you might have another crack at it later on.
I'm feeling a little bit that way right now too, and put my ICS kernel on the back burner. I think I'm trying to multitask a little too much at times....
Yep, a break is what you need, maybe some clarity will come after you've had a chance to recharge.
Sent from my GT-I9300 using xda premium
It's very nice to see you took up the big responsibility to make this superb device to be usable again! it has great specs, really. KUDOS bro!!
Any update on this development?
ZhenMing said:
Any update on this development?
Click to expand...
Click to collapse
Not much, I have had no interest to spend time with this topic because I have been very busy IRL. After I get my new house renovated fully and get my job tasks done, I wont be spending much time with this project. Feel free to use any sources provided in this thread to further advance the subject.
But this wont go forward that much, if the GT-P6800 wont get official CM10.1 update...
It works?
I am trying to compile android 2.3 v20s kernel and it is giving me 18 mismatch section ...I sorted out first three.....but I am not expecting the other 15.....has any one faced this.......I have use arm-eabi -4.4.3 and 4.4.0 and also 4.6 ...but no change.....
I know there are dev's who has successfully compiled it.....can any one tell me whether they saw so many mismatches ....because it is original source from lg......
I did not face these many mismatch or i think there were none during 4.0.4 compile.....
I know they can be fixed by putting of adding/removing __init etc but i am not expecting them
I have attached the build log ...
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Duarte777 said:
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Click to expand...
Click to collapse
They are just warnings....The build is complete
...But i think section mismatches are bad...and these are too many....
Sent from my LG-P970 using xda app-developers app
Duarte777 said:
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Click to expand...
Click to collapse
Also the lines where mismatch is coming ...the code is same in 4.0.4 but they don't give warnings ...I used 4.6 for 2.3 also but same ....
Are there any compiler flags to be set in makefile which can take care of these.....
Sent from my LG-P970 using xda app-developers app
Can any more dev's put some light on this....
Sent from my LG-P970 using xda app-developers app
I downloaded arm-linux-androideabi-4.6 from https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/
and then only got one warning which I fixed and no warnings now.....
but if i use arm-eabi-4.6 https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
or any arm-eabi- version then i get 14 mismatch ,,,,,,
AFAIK arm-eabi- is used to build kernels and androideabi is used to build android layer.......but the later also builds kernel and i don't get any warnings now.......
Also found one reference where arm-linux-androideab- is used to build nexus S kernel.....
http://glandium.org/blog/?p=2214
So is it safe to use kernel built by arm-linux-androideab-
I see there is no response .But that is OK,as I have fixed all the section mismatches .The issue was in LG's code..and now compiled with arm-eabi-4.6 with zero section mismatch errors....I will try the kernel after applying rmcc patch ..maybe this weekend.
got the kernel booting
see below post for info
http://forum.xda-developers.com/showpost.php?p=52409264&postcount=13
https://github.com/rajeshmk2011/lg_p970_gingerbreadkernel.git
4.9 was released and Nexus 5 it's support by mainline kernel
http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.9-ARM-Pull
Interesting. This might bring development back to the phone. Also 4.8 and 4.9 have some amazing features and speed improvements.
Will any dev merge and update our kernel? will this function with our android latest version?
santi1993 said:
Will any dev merge and update our kernel? will this function with our android latest version?
Click to expand...
Click to collapse
No, it's probably not even functional in many aspects, there will be a lot of patching/fixing needed to get it to work.
There is already been discussed about his.
Yes, it's impossible use 4.9 without patch related to panel, exc exc
So what does exactly the "Nexus 5 support" on this kernel mean if you can't run Android on it without patching? Would it potentially help running Linux distros on our devices or?
TheReduxPL said:
So what does exactly the "Nexus 5 support" on this kernel mean if you can't run Android on it without patching? Would it potentially help running Linux distros on our devices or?
Click to expand...
Click to collapse
There is support for the kernel, so yes, you could now run Arch, Debian, OpenWRT, or DD-WRT much more easily.
Android utilizes old libraries that are not compatible with new kernels (that's at least my understanding of the matter), so you would need to patch it to run a newer kernel, and that could only get you so far.
The newest kernel version that anyone had managed to boot Android with is the latest 4.4.x LTS release.
I wonder if someone could backport the necessary changes from 4.9 to the latest 4.4.x release though, that would already be something.
Thank you! I really like the concept of running *WRT on Nexus - I wonder how would functionality like network booting work like...
Could the mainline kernel also be used for other non-Android OSs like Ubuntu (Touch) or Sailfish OS?
TheReduxPL said:
Thank you! I really like the concept of running *WRT on Nexus - I wonder how would functionality like network booting work like...
Could the mainline kernel also be used for other non-Android OSs like Ubuntu (Touch) or Sailfish OS?
Click to expand...
Click to collapse
I don't think so, as they rely on Android bits to work with the bootloader and recovery.
But perhaps there is a chance with the new OS that KDE are cooking, which is supposed to be completely independent of Android.
The 4.10 kernel brings in mainline support for the Nexus 6P and the Nexus 5X.
I wish that mainline support would arrive for the Nexus 4.
moriel5 said:
The newest kernel version that anyone had managed to boot Android with is the latest 4.4.x LTS release.
Click to expand...
Click to collapse
Update: Apparently Android 6.0.x and up can now utilize kernel 4.9.x.
As there is a build of Android 7.1.x for the x86 platform (I have no idea whether it is an official build of Android-x86, nor do I know the precise Android version, though) with a 4.9.x kernel (again, I have no idea precisely which version).
My source is a newly thread opened in the Remix OS forum, in which the OP asks for the possibility of updating the kernel in Remix OS, and mentions that he/she managed to boot it (only in debug mode, though) with the aforementioned kernel.
The source: https://forum.xda-developers.com/remix/remix-os/remix-3-0-207-kernel-t3546057
anyone managed to boot a hh from any kind of 4.9 compilation?
Sent from my Nexus 5 CAF using Tapatalk
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
santi1993 said:
anyone managed to boot a hh from any kind of 4.9 compilation?
Click to expand...
Click to collapse
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
Linux version 4.9.27 ([email protected])
Wow, you are one of the coolest users on there! i doubt anyone could boot it up!
You rock! hope we can get a public release to test it out!
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
Hey that's amazing. I've been working on this too. So where exactly did you enter the command line parameter for console? Can you list out that command?
Sent from my Nexus 5 using XDA Labs
santi1993 said:
Linux version 4.9.27 ([email protected])
Wow, you are one of the coolest users on there! i doubt anyone could boot it up!
You rock! hope we can get a public release to test it out!
Click to expand...
Click to collapse
Thanks for appreciation, but what do you expect from "public release"?
As many other already posted here, this kernel is far away from the 3.4 Images for daily use.
So this is just for fun of course :angel:
Icyphox said:
Hey that's amazing. I've been working on this too. So where exactly did you enter the command line parameter for console? Can you list out that command?
Sent from my Nexus 5 using XDA Labs
Click to expand...
Click to collapse
Have a look at the tool abootimg.
You could use a bootimg.cfg fle and change the cmdline for your boot image individually.
E.g.:
Code:
bootsize = 0xe48800
pagesize = 0x800
kerneladdr = 0x8000
ramdiskaddr = 0x2900000
secondaddr = 0xf00000
tagsaddr = 0x2700000
name =
cmdline = console=ttyMSM0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 androidboot.selinux=permissive
The other parameters are fixed values for hammerhead... and the bootsize value depends on the size needed for your image.
In this case it's just the default value used for TWRP.
Then use the tool like this:
abootimg --create hammerhead-kernel4.img -f bootimg.cfg -k zImage-dtb -r initrd.img
Best regards,
scholbert
scholbert said:
Thanks for appreciation, but what do you expect from "public release"?
As many other already posted here, this kernel is far away from the 3.4 Images for daily use.
So this is just for fun of course :angel:
Have a look at the tool abootimg.
You could use a bootimg.cfg fle and change the cmdline for your boot image individually.
E.g.:
The other parameters are fixed values for hammerhead... and the bootsize value depends on the size needed for your image.
In this case it's just the default value used for TWRP.
Then use the tool like this:
abootimg --create hammerhead-kernel4.img -f bootimg.cfg -k zImage-dtb -r initrd.img
Best regards,
scholbert
Click to expand...
Click to collapse
Wonderful! The heads-up I needed was the bootimg.cfg. Thanks a bunch. Also, is your ROM usable with this kernel?
Sent from my Nexus 5 using XDA Labs
Icyphox said:
Wonderful! The heads-up I needed was the bootimg.cfg. Thanks a bunch. Also, is your ROM usable with this kernel?
Sent from my Nexus 5 using XDA Labs
Click to expand...
Click to collapse
No far away from any use together with a ROM or even anything the TWRP image uses inside.
No graphics... no usb...
This is just a proof of concept, playing around with the dts files and kernel. Nothing more.
If someone would create a console based ramdisk with some tools included, you may dig a little deeper into the soc or check which parts are responsive or not.
Cheers,
scholbert
It has been quite some time.
Does anyone think that using PostMarketOS's kernel as a stepping stone may help get at least kernel 4.4 to a daily-driver ready status?
Update: Perhaps it would also be a good idea to use the Nexus 7 (2013)'s sources to try porting the newer kernel there to the Nexus 4 (as they share the same SOC).
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
From the logs, it looks like the reason the boot stops is because of init.rc errors. I might be able to help with that, but my nexus 5's battery is toast.