Hello,
is there a Firefox OS image for the LG Optimus L9 P760 ?
git clone git://github.com/mozilla-b2g/B2G.git
./config
Valid devices to configure are:
- galaxy-s2
- galaxy-nexus
- nexus-4
- nexus-4-kk
- nexus-5
- nexus-s
- nexus-s-4g
- flo (Nexus 7 2013)
- otoro
- unagi
- inari
- keon
- peak
- leo
- hamachi
- helix
- wasabi
- fugu
- tarako
- tara
- dolphin
- pandaboard
- vixen
- flatfish
- flame
- emulator
- emulator-jb
- emulator-kk
- emulator-x86
- emulator-x86-jb
- emulator-x86-kk
Is there a compatible model in the list ?
Thanks
ds2k5 said:
Hello,
is there a Firefox OS image for the LG Optimus L9 P760 ?
git clone git://github.com/mozilla-b2g/B2G.git
./config
Valid devices to configure are:
- galaxy-s2
- galaxy-nexus
- nexus-4
- nexus-4-kk
- nexus-5
- nexus-s
- nexus-s-4g
- flo (Nexus 7 2013)
- otoro
- unagi
- inari
- keon
- peak
- leo
- hamachi
- helix
- wasabi
- fugu
- tarako
- tara
- dolphin
- pandaboard
- vixen
- flatfish
- flame
- emulator
- emulator-jb
- emulator-kk
- emulator-x86
- emulator-x86-jb
- emulator-x86-kk
Is there a compatible model in the list ?
Thanks
Click to expand...
Click to collapse
No, ROMs are device specific. You have to port it and add it to the list. I could attempt a port of this, I ported Firefox os to kindle fire HD, its hardware is very similar, and as long as there's a cm device tree that is ICS based or higher I should be able to attempt a build. I only haven't tried yet since my bootloader is yet to be unlocked, but I could attempt a build this weekend if you want, I just need a cm device tree.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
No, ROMs are device specific. You have to port it and add it to the list. I could attempt a port of this, I ported Firefox os to kindle fire HD, its hardware is very similar, and as long as there's a cm device tree that is ICS based or higher I should be able to attempt a build. I only haven't tried yet since my bootloader is yet to be unlocked, but I could attempt a build this weekend if you want, I just need a cm device tree.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Many thanks.
The Problem is, i get the LG in a few days.
If i have it, i try to give you the cm tree.
There is a guy that build a cm 11 rom for the LG.
http://artas182x.tk/?page_id=287
thanks
OK cool, can't wait to see how this works, its funny you mention it after the fact because a few months ago running Firefox is would have been a complete pain because sgx GPU's were having issues, I was around at the time they fixed it working on kfhd builds. Can't wait to attempt a build on this and see how it goes. Only downside is I can't personally test out the ROM. That being said i can already think of a few issues that might present themselves since the hardware is similar but only time will tell...
Sent from my Amazon Tate using Tapatalk
stunts513 said:
OK cool, can't wait to see how this works, its funny you mention it after the fact because a few months ago running Firefox is would have been a complete pain because sgx GPU's were having issues, I was around at the time they fixed it working on kfhd builds. Can't wait to attempt a build on this and see how it goes. Only downside is I can't personally test out the ROM. That being said i can already think of a few issues that might present themselves since the hardware is similar but only time will tell...
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Hi,
sorry my english is poor, do you have now any information that you need to build a FireFox OS Image (for LG P760)?
Or do you need anything else ?
thanks
I still need to find the device tree, but I'm going to bed I have to get up for work tomorrow and its late. I'll look into it this weekend.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I still need to find the device tree, but I'm going to bed I have to get up for work tomorrow and its late. I'll look into it this weekend.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
>I still need to find the device tree,
can i find this in the ROM Package ?
or how to get the "device tree" ?
thanks
stunts513 said:
I still need to find the device tree, but I'm going to bed I have to get up for work tomorrow and its late. I'll look into it this weekend.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
may be the GIT Repo can help you
https://github.com/artas182x
https://github.com/artas182x/lge-kernel-omap4
https://github.com/artas182x/proprietary_vendor_lge/tree/cm-10.1/p760
https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-11.0/p760
Thanks, I was hoping for a cm 10.2 dev tree but I can work with cm 11, their 4.3 builds were more stable than my current 4.4 builds on kfhd, though my 4.4 builds have a ton more bugs fixed from upstream. Thanks for that I will take a look at it this weekend.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Thanks, I was hoping for a cm 10.2 dev tree but I can work with cm 11, their 4.3 builds were more stable than my current 4.4 builds on kfhd, though my 4.4 builds have a ton more bugs fixed from upstream. Thanks for that I will take a look at it this weekend.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
here is the CM 10.2 device tree (i hope so)
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2-cwm
thanks
ds2k5 said:
here is the CM 10.2 device tree (i hope so)
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2-cwm
thanks
Click to expand...
Click to collapse
ok thanks, thats a good part of it i think, i will have to see about putting together a manifest using that repo plus maybe a few others, last time i did this it was with a device that wasnt official at the time so i had a manifest generated for the process already that made my life easier, so i will have to do some research this time to figure out what repos i need, i can guess that one and definately the proprietary blobs. Will try to get this done sometime soon, ran out of time this weekend because i was also doing something on my domain controller to update some deployment images and the freaking power inverter for the lcd screen died...
a small update before i head to work, i managed to get it to start the compilation process now, so now comes the tedious debugging process, already hit one error about selinux attribs that needs to be set correctly so there arent duplicates, those are easy enough to fix, just thought you might want an update.
if anybody is still curious how this is going, i'm tryin got fix an issue involving the kernel not compiling, finally decided to go with using a prebuilt but iunfortunately having a hard time figuring out why defining TARGET_PREBUILT_KERNEL isnt working...
Found the Firefox OS trining manual (sort of)
stunts513 said:
if anybody is still curious how this is going, i'm tryin got fix an issue involving the kernel not compiling, finally decided to go with using a prebuilt but iunfortunately having a hard time figuring out why defining TARGET_PREBUILT_KERNEL isnt working...
Click to expand...
Click to collapse
Nt really my field of expertise, but I read the post and found something I thought might be helpful. This was a link posted by (Duckbill, I think):
http://csmg.lgmobile.com:9002/gdmsp...1&ret=1&curPage=2&searchtype=&keyword=&arg01=
It is a link to the LG South Korea portal of some kind entitled: 2013-11-04 FireFox OS Training Material. It is presented as a .zip file but when extracted with 7z, it only produces this:
[autorun]
open=LGMain.exe
icon=LGMain.exe,0
The file is larger than 5MB so I'm sure this is simply more LG encryption, although I don't really understand the implications of the instructions. On the remote chance that this is helpful, let me know how it helped.
I got a successful build, not sure if it will work but it built successfully. If you wanna test it post back and i''ll post the link soon, still have to upload it.
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THIS SOFTWARE OR SOMETHING ELSE SUDDENLY FRIES YOUR DEVICE. ***
ok this is just a alpha build so no guarentees it will even boot and since i have the p769 with a locked bootloader i can't really test the build. Again this is for the p760 and i would like to mention if it doesnt work i wouldn tbe surprised if you get stuck at the bootloader logo while the os is actually trying to boot, if this happens i blame the hwc module, so if it does happen i believe you should have superuser access at a adb shell and you can simply run
Code:
adb shell mount -o rw,remount /system
adb shell rm /system/vendor/lib/hw/hwcomposer.p760.so
adb shell rm /system/vendor/lib/hw/hwcomposer.omap4.so
adb reboot
that might fix a not booting issue. This is a barebones build, until i know i have a build that can sucessfully build i dont bother tsing bluetooth and rild and such. I can say that since i didnt make the modifications i did last time that i'm assuming bluetooth is probably not enabled right now.
anyways i will make this a thread in the dev section when its out of testing. Here's a link to the first alpha build if you are willing to try it: http://d-h.st/5Kq
anybody going to test this? I let it sit for a few days but i was hoping to have some testers by now. Can't really debug it myself without having a actual device thats unlockable. Theoretically i might be able to run this with a 2nd init exploit, never tried setting one up on a b2g os though.
stunts513 said:
anybody going to test this? I let it sit for a few days but i was hoping to have some testers by now. Can't really debug it myself without having a actual device thats unlockable. Theoretically i might be able to run this with a 2nd init exploit, never tried setting one up on a b2g os though.
Click to expand...
Click to collapse
I can try to test it
please let me know where to download the image(s)
In the post before last. Thanks BTW.
stunts513 said:
In the post before last. Thanks BTW.
Click to expand...
Click to collapse
I have the CWM v6.0.4.5 from artas182x, and the CyanogenMod 11 from artas182x on my P760
if i do "install zip" -> "choose zip from /external_sd" -> full_p760-ota-eng.stunts513-signed.zip
assert failed: getprop("ro.product.device") == "p760" || getprop("ro.build.product") == "p760"
E:Error in /external_d/full_p760-ota-eng.stunts513-signed.zip
(Status 7)
Installation aborted.
Related
CYANOGENMOD 10.2 [UNOFFICIAL BUILDS]
Code:
BUGS:
no 1080p recording
cant use UMS (if you want to transfer something to your mobile connect with PTP and manually move it on your phone)
probably more
Code:
DOWNLOADS:
ROM
[URL="http://www.androidfilehost.com/?fid=23212708291682444"]DOWNLOAD ROM[/URL]
GAPPS
[URL="http://www.androidfilehost.com/?fid=23212708291681346"]gapps-jb-20130813-signed[/URL]
Code:
INSTALLATION INSTRUCTION:
Full wipe
manual format /system
Flash ROM
Flash Gapps
Reboot
Code:
BIG THANKS TO:
the CyanogenMod team
[URL="http://forum.xda-developers.com/member.php?u=3430186"]Mateo1111[/URL]: cause i really like your roms
[URL="http://forum.xda-developers.com/member.php?u=360947"]AntonX[/URL]: got some tweaks from him
change log
Code:
[CENTER]
CHANGELOG:
28/11
cm source
build is up and running
25/11
Updated cm source
Fixed settings for l9 - it works now
Fixed emulated storage - its disabled now
got some problems with connecting phone with UMS
though could be the school computer.
Going to test later today @ home
[/CENTER]
sweet nice to see new developer out there for p760 - wish you all the best and good luck in development
ulaon said:
sweet nice to see new developer out there for p760 - wish you all the best and good luck in development
Click to expand...
Click to collapse
Thanks ill do my best to learn
i stop developing this rom since mateo has a fully functional cm10.2 and its unuseful to have same roms this does not mean i stop developing this was more an experiment for myself
Fl3kzZ said:
i stop developing this rom since mateo has a fully functional cm10.2 and its unuseful to have same roms this does not mean i stop developing this was more an experiment for myself
Click to expand...
Click to collapse
"Nice, long career" ...but thank you! :good:
i wont stop but what i mean is there is already a stable 10.2 rom with frequent updates so whats the point to create another one?
JulianJenner said:
"Nice, long career" ...but thank you! :good:
Click to expand...
Click to collapse
Fl3kzZ said:
i wont stop but what i mean is there is already a stable 10.2 rom with frequent updates so whats the point to create another one?
Click to expand...
Click to collapse
He just quite developing it. You should keep it updated, as long as cm10.2 code still changes. Also you can probably still tweak the kernel some more, or add some cool cuatom features
And I dont know, how much you know about kernel development, but there is a thread about a "booting 3.4 kernel" in the galaxy nexus forum. This one also contains a lot of degfconfig settings, which might also work on our board (4430 and 4460 chipsets AFAIK). If you could check which enhancements we can use, so we can use them for 4.4 in the future. They might solve those graphical glitches.
Sent from my SM-T210 using xda app-developers app
N00BY0815 said:
He just quite developing it. You should keep it updated, as long as cm10.2 code still changes. Also you can probably still tweak the kernel some more, or add some cool cuatom features
And I dont know, how much you know about kernel development, but there is a thread about a "booting 3.4 kernel" in the galaxy nexus forum. This one also contains a lot of degfconfig settings, which might also work on our board (4430 and 4460 chipsets AFAIK). If you could check which enhancements we can use, so we can use them for 4.4 in the future. They might solve those graphical glitches.
Sent from my SM-T210 using xda app-developers app
Click to expand...
Click to collapse
alright i will get back to it but i had some probs with pc :/ my hdd crashed so i had to reinstall everything and for some reason i couldnt dual boot ubuntu and win 7 but got a working backtrack 5 distro so after weekend ill set things up
Sent from my LG-P760
got some trouble with dual booting ubuntu and windows but maybe found a way
so expect some builds soon
The reason I post my ROM here is because I'm soon starting with a new rom, broodROM KitKat which will also be available for the Note 3, So I figured why not test it on my current AOSP ROM (to see if there is any trouble on compiling, but no!). This AOSP is based on the real Google AOSP, no real further modifications (only thing is that it includes DeviceSettings from the S4 currently), and AppOps is exposed. that's all.
It includes the stock CM11 kernel (which is kinda crappy). but I don't have the device so cannot make decent kernel myself without testing. Also the ROM is 100% untested. but it compiled without any error with my sources (www.github.com/AOSP-S4-KK) so I think it's alright.
Working List
- You tell me I have no idea :silly:
Download Alpha 1
www.broodplank.net/files/AOSP-442-N9005-Alpha-1.zip
on alpha 01 you need to flash a custom kernel
SEND ME LOGCAT! BECAUSE CURRENTLY IT SEEM TO BOOTLOOP
The device name is listed as hlte in settings / build.prop, don't worry this is actually hltexx
Download Gapps Lite + SuperSU (yes it's not rooted by default, I recommend installing this package)
http://broodplank.net/files/gapps-4.4.2-lite-with-supersu-1.86.zip
Sources
- https://github.com/aosp-s4-kk
Download:
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u git://github.com/AOSP-S4-KK/platform_manifest -b kk-4.4
repo sync
Building:
Code:
. build/envsetup.sh
lunch
make otapackage
reserved1
Sweet man!! Thanks always looking for something new to flash lol downloading now
Sent from my iPad using Tapatalk
Downloading!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thankyou OP
anybody that has tried this, can you let me know if the temp/humidity sensors are still working after a few hours? as with other cm roms they stop working for me
Awesome Broodplank! Just switched from the Galaxy S Plus to the Note 3, always enjoyed your roms on there. Will try out this one! Keep up the good work
Sent from my SM-N9005 using xda app-developers app
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
radicalisto said:
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
Click to expand...
Click to collapse
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
broodplank1337 said:
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
Click to expand...
Click to collapse
OK - will try again now and let you know :good:
and new bootloader ?
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
radicalisto said:
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
Click to expand...
Click to collapse
ok good, could you open up adb shell, and send me the logcat, since I have no idea what actually could be the cause atm.
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
radicalisto said:
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
Click to expand...
Click to collapse
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
broodplank1337 said:
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
Click to expand...
Click to collapse
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
radicalisto said:
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
Click to expand...
Click to collapse
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
gianton said:
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
Click to expand...
Click to collapse
Ah I dropped the herp a derp then hahah, Nah reason I thought that was because of the CM kernel used to boot it up. Thanks for correcting :good:
---------- Post added at 08:56 AM ---------- Previous post was at 08:55 AM ----------
@gianton it'll boot into splash screen with temasek's kernel, if you wanna try and grab an ADB Logcat? - I'm having issues getting one :crying:
Sorry for not providing a good kernel, the thing is I cannot compile it decently with the ROM. it says I have to add module support and recontinue, thing is, the note 3 does not use it. but my build forces it.. Anyone have experience on CM with compiling the kernel? (the kernel is from CM after all)
You could try temasek or Yank555 or wootever for help with kernels as they're pretty decent at them - civato knows his stuff also, however I believe he has only worked with Stock samsung kernels and not CM stuff.
Still cannot get ADB logcat, phone won't recognise in PC
Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.
ALL WORK HAS MOVED TO THE 3.4 BRINGUP. YES, THAT MEANS 3.4 IS BOOTING AND WIP AND THIS KERNEL IS NOW DEPRECATED! CLICK HERE TO VIEW 3.4 PROGRESS
Check latest posts for updates
As you may be aware, we've been trying unsuccessfully to boot Nvidia's 3.4 kernel for tegra 3 on grouper.
Progress has pretty much halted, as this project needs to be finished before we have any hope of 3.4 ever working.
SAUCES
-
WE ALSO HAVE A GITHUB ORGANIZATION
What is this?
An attempt to get Google's ludicrously outdated grouper 3.1 kernel up-to-date with Nvidia's 3.1 kernel.
Why?
1) It'll be, put simply, "better" than Google's out-of-date kernel (...potentially)
2) This *must* be completed before work on 3.4 goes ahead
3) Hopefully other kernels, such as franco's, could be merged with this
How?
I did a "git rev-list" of Nvidia's branch, then Google's branch, all the way back to the point where Google added grouper support (Around March 2012), then diffed the result. I've attached the files in this post: The commits in the diff which have a + next to them are Nvidia's commits, as these are not present in Google's log. I simply need to cherry-pick all 1,699 of these, and make sure to manually update the grouper board files exactly as Nvidia's dev. boards are updated (because of course grouper itself is not updated at all in Nvidia's source). Then I need to fix all the compilation errors. If I get through around 50 - 80 commits a day, and fix the compilation errors the next day, I should be finished in 2 months max. Then serious 3.4 work can begin.
Should I use it?
From a user's perspective, in all honesty, no. This is a) a WIP and b) a means to another end (3.4). Other offerings such as franco's kernel are so far more improved than Google's anyway that this will not be necessarily "better" than those simply due to a load of updates from Nvidia. What *will* make this useful is if the final product is merged, as I said, into existing kernels, thus improving those. That said, I'll never upload a new version before having tested it myself, so you can be in the very least assured that it'll boot and run.
HOWEVER it would be extremely useful if you could run this simply for testing purposes. All my trust is placed in Nvidia's commits and my own ability to fix conflicts and compilation errors. Things may go wrong and your help would be massively appreciated.
Shutupandletmeflash!!!
I'll post updates regularly as possible here. I've used agnostic as it's fantastic. The naming scheme is: Alpha whilst I'm still cherry-picking, Beta once that's done and we're testing to fix bugs, then RC once its in a stable, releasable state (there'll probably only be 1 RC, then no more work); The numbering is x.y where x indicates major release (0 is Alpha, 1 will be Beta) and y will be increment by 1 on every single release.
Credits
@sgt. meow
Nvidia
Google
Asus
@legolas93 for F2FS
@frantisek.nesveda for agnostic-kernel
Anyone else I've forgotten (sorry, it's a while since I opened the 3.4 discussion thread)
XDA:DevDB Information
linux-tegra-nv-3.1-grouper, Kernel for the Nexus 7
Contributors
HTCDreamOn, Ziyan, n1kolaa, sgt. meow
Source Code: https://github.com/Ziyann/android_kernel_asus_grouper
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2015-06-07
FAQ
Q: Why is TricksterMod/ CPUSpy/etc. Not showing 1300MHz?
A: read this post.
GREAT! :good:
Its great to see people giving attention to an old device.
I will look forward to it.
What you forgot me
You know moral support!!
Lol J/K
Good thing you put it in original development
That will help.
So keep up the... Hmm dont know how to express it....
Your doing an beyond awesome job!
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I'm sure we will get Android 5 one way or another
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/10/15/being-the-will-of-our-lord-duarte-the-nexus-7-2012-will-receive-the-holy-blessing-of-android-5-0-official/
frantisek.nesveda said:
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/1...ve-the-holy-blessing-of-android-5-0-official/
Click to expand...
Click to collapse
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I expect the kernel will be updated as it was for 4.4 from 4.3. I'm still carrying on with this, however, as of course the new kernel will still be 3.1.10. Then I can apply those updates on top of this.
P.S Did some more cherry-picking today. Mostly smooth, very few conflicts so far.
HTCDreamOn said:
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
Click to expand...
Click to collapse
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
Same here
the kernel should work with CM
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now Android browser is a pain with attachments, 0.1 will be tomorrow.
HTCDreamOn said:
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now.
Click to expand...
Click to collapse
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
USBhost said:
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
Click to expand...
Click to collapse
0.1 uploaded. Glad it works.
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Interactive has never ran good on my tablet no matter what kernal.
Sent from my Nexus 7 using Tapatalk 2
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Thanks for pointing this out, I hadn't noticed this before but it's happening to me as well. I seem to remember a commit affecting cpufreq scaling somewhere so this could be it, but it should be easy to fix. I might stock up these smaller problems and fix them right at the end to reduce conflicts, but if its simple enough I'll fix it soonish.
In other news, Alpha 0.2 has been uploaded (first post as usual) mostly just more commits picked, but we're starting to get to the good stuff: changes to tegra3 drivers etc. And some things I can use to update grouper board files :good:
Alpha 0.2 works well here.
Snappy for a stock kernel.
Only things to report:
Max freq is 1200 with all governors.
To turn the tablet on after sleep I have to press the button a lot.
Keep up the good work!!!
Agreed with alpha 2 running smooth same as above with frequency at 1200 keep up the good work looking forward to future updates
I just installed Alpha 2 on LiquidSmooth 3.2. After the first boot, I got multiple force closes on "com.android.acore" but after a reboot everything seems to work just fine. I will use it for the next days and report any bugs I encounter.
I just tried the alpha 2 on my tilapia running a clean install of CyanogenMod 2014-10-23. On the first boot everything is fine, but after a reboot I get SystemUI FC's everytime I unlock the device and it relocks again.
When I install M-kernel a69 or alpha 1 of this kernel, everything seems to be fine. I am using Data-F2FS, if it matters somehow.
I can post a logcat or kmesg tomorrow, right now I screwed up my hackintosh bad and it doesn't even boot, so I don't have a way to access adb.
The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918