Please can a mood Luck thread till further notice.
Thank you
LaputaCake said:
Hello who wants to help me build cm10.1 and cm10 for you guys as ive found one for £45 need a device tree and testers
Click to expand...
Click to collapse
I can help you testing your builds
HTC Desire X || Android 4.1.2 || mySENSEdx5 RC3.0
I will help testing too if I have time
I will help to with the testing.
LaputaCake said:
Hello who wants to help me build cm10.1 and cm10 for you guys as ive found one for £45 need a device tree and testers
Click to expand...
Click to collapse
You can find everything here : http://forum.xda-developers.com/showthread.php?t=2437255 .
Good luck.
Yeah. I can hlep with testing as well; when you provide your sources, I can assist in building too, when I have some time left (now there is hardly any, but it will be a bit better after christmas, I hope)
trying to repo sync and getting this even using protou project init:
repo init -u git://github.com/ProtouProject/android.git -b cm-10.1
but get this:
Code:
fatal: '../CyanogenMod/android_abi_cpp.git' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
error: Cannot fetch CyanogenMod/android_abi_cpp
I think this one is source for cm 10.2 only, if I'm not mistaken. For cm 10.1 or 10, there are only sources by atis112 (please correct me if I'm wrong).
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
I think this one is source for cm 10.2 only, if I'm not mistaken. For cm 10.1 or 10, there are only sources by atis112 (please correct me if I'm wrong).
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its alright i fixed by rebuilding envireoemtndfvbisduvbsdnzvh. just repo syncing now
LaputaCake said:
Its alright i fixed by rebuilding envireoemtndfvbisduvbsdnzvh. just repo syncing now
Click to expand...
Click to collapse
Ill be using this device tree
https://github.com/ProtouProject/android_device_htc_protou/tree/cm-10.1
Yeah,that is the device tree we are using.
Not sure how did you get to Protou Project github,we only use common from there.
Everything else is on Protoype-U github.
EDIT : Also if you need help with compiling tell me,i can setup a virtual ubuntu and do some work.
I can't dual boot it now because i need a whole partition for my school project.
nightwalkerkg said:
Yeah,that is the device tree we are using.
Not sure how did you get to Protou Project github,we only use common from there.
Everything else is on Protoype-U github.
EDIT : Also if you need help with compiling tell me,i can setup a virtual ubuntu and do some work.
I can't dual boot it now because i need a whole partition for my school project.
Click to expand...
Click to collapse
Does anyone have sim unlocking method working (Not paid)
Also how bigga hard drive do you have as ive only got 78.1g for ubuntu and 69.97gigs for windows
That should do for building cm if you're not building for more devices.
Sent from my HTC Desire X using XDA Premium 4 mobile app
I can help with compiling as well . Got about 200GB free disk space on Ubuntu lying around , waiting to be useful xD
Will setup & sync everything tomorrow though , right now I'm a little busy .
I can also help with testing , logcatting etc .
LaputaCake said:
Does anyone have sim unlocking method working (Not paid)
Also how bigga hard drive do you have as ive only got 78.1g for ubuntu and 69.97gigs for windows
Click to expand...
Click to collapse
Tried DesireC method... Not working, I was looking at it the other day and couldn't really find anything useful. Happy to see you Hear on The Dx subforum
dansou901 said:
That should do for building cm if you're not building for more devices.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im building cm10.2 for my phone aswell better cut down on windows but i got nice 500gb external hdd
And due to S-ON there is no free sim unlocking method for now. But there are several paid methods which should work.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
And due to S-ON there is no free sim unlocking method for now. But there are several paid methods which should work.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ill have to get unlocked or vodafone
LaputaCake said:
ill have to get unlocked or vodafone
Click to expand...
Click to collapse
anyone know anywhere to get one?
Is it really important to get the phone unlocked ?
You can just get a new sim card and run it,if you don't wont this phone to be your primary phone that is.
Related
Is there a good tutorial on how to compile CM10 (or any CM) for an unsupported device? In particular, I have a MIONE_PLUS phone manufactured by XiaoMi, which is not officially supported by CM. I'd like to experiment with creating a CM10 port to my device.
I've synced the CM10 repo, but I'm confused about what the next step should be. In terms of proprietary binary files / configuration files, how do I know what files are necessary? And how do I compile CM10 with an existing Linux kernel grabbed from my stock ROM?
Any advice is appreciated. Thanks!
first you need to get the propietary files for MI-one (wish i dubt that miui give it to the comunity).
blackwing182 said:
first you need to get the propietary files for MI-one (wish i dubt that miui give it to the comunity).
Click to expand...
Click to collapse
Will a general target, say, mini_armv7a, work?
Dominator008 said:
Will a general target, say, mini_armv7a, work?
Click to expand...
Click to collapse
As long as you find a phone from the same board type should be pretty easy getting boot.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
As long as you find a phone from the same board type should be pretty easy getting boot.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
MI-ONE is msm8660 so he can look to similar boards like HTC sensation , Samsung galaxy s2 T989 ( Hercules) , ATT samsung Skyrocket as an example
Hi guys,
I went to check for the HTC DX source code on htcdev.com, and saw there were around 31 sources, but they're are all CRC's...
Could anyone please explain to me, what is a CRC? I tried googling it, but it didn't really help.
Sent from my HTC Desire X using xda premium
kernel source
Lloir said:
kernel source
Click to expand...
Click to collapse
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
infernal77 said:
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
Click to expand...
Click to collapse
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Yasir Javed Ansari said:
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks, Yasir, I know lli0r made a device and vendor tree, but he said the vendor tree might be incomplete. He tried to make us a CM9 but hasn't got the device itself. I also read you can extract the files from a running device, but for that you need extract-files.sh or proprietary-files.sh, which isn't in there. I'm sure I can google and find one of those files from another device and try to run them on mine, but they're probably device-specific as well. And there isn't one of those files in lli0r's github. I checked that I'm sorry, I am ompletely new to Android, let alone building roms, but I love to just experiment a bit
Btw, when are you getting your Desire X ?
This is the discussion thread for the development of cm10.1 and cm10.2 and cwm6. Please dont ask how to root and etas for cm. This is only to discuss issues with cm and cwm6. Currently we have got issues with current cwm recovery so we need to work on that first. Problem is that @prbluebottle (the one who helped me getting a proper device tree) says he did compile and flash cm10.2(yes you see right) but sadly it didnt get to boot or to recovery mode. So first we need to work on proper cwm recovery. I'll keep u posted about progress when it happens.
UPDATE[27/12/2013]: We got a working CWM 6.0.2.8 thanks to @Doc_cheilvenerdi.org please guys contiune the furture discussion here. Now we have to work on CM10.1 @mackief dude if have repo synced cm10.1 please compile for us. I can test it if u want.
Ironman38102 said:
This is the discussion thread for the development of cm10.1 and cm10.2 and cwm6. Please dont ask how to root and etas for cm. This is only to discuss issues with cm and cwm6. Currently we have got issues with current cwm recovery so we need to work on that first. Problem is that @prbluebottle (the one who helped me getting a proper device tree) says he did compile and flash cm10.2(yes you see right) but sadly it didnt get to boot or to recovery mode. So first we need to work on proper cwm recovery. I'll keep u posted about progress when it happens.
Click to expand...
Click to collapse
How did you make cwm? Did you use the cwm builder? Do you have source if so where.
We didnt use cwm online builder. We ported it from another device using android kernel kitchen
Sent from my GT-S5282 using Tapatalk now Free
Ironman38102 said:
We didnt use cwm online builder. We ported it from another device using android kernel kitchen
Sent from my GT-S5282 using Tapatalk now Free
Click to expand...
Click to collapse
That's not good send me a boot.IMG and recovery.IMG . Also cat proc/partitions so I can set the correct partition sizes .
@ironman, better if you could upload here the cwm for S5282. So e ery user could use it.
Working CWM
Hnk1 managed to have a working CWM here: http://forum.xda-developers.com/showthread.php?p=46281146
Well me and my friends tried to compile unfortunately the device tree is incomplete but I found out what files are missing and Ill push to github today
Sent from my GT-S5282 using xda app-developers app
There is a seperate discussion made for cwm booting issues. Link is below If anyone can help u can pm op in the thread.
http://forum.xda-developers.com/showthread.php?p=46351688
Sent from my GT-S5282 using xda app-developers app
Just pushed missing device tree files to Github. @prbluebottle try compiling again and notfiy me for any issues
Ironman38102 said:
Just pushed missing device tree files to Github. @prbluebottle try compiling again and notfiy me for any issues
Click to expand...
Click to collapse
Hey bro is it possible to add app2sd support in CM10.1 ??
Not sure how do I do that
Sent from my GT-S5282 using Tapatalk now Free
Ironman38102 said:
Not sure how do I do that
Sent from my GT-S5282 using Tapatalk now Free
Click to expand...
Click to collapse
Modifying the vold.conf, vold.fstab and init.rc and related init files will do i think i am also not sure..
Chirtagh said:
Modifying the vold.conf, vold.fstab and init.rc and related init files will do i think i am also not sure..
Click to expand...
Click to collapse
I have no knowledge of editing linux scripts. I think @prbluebottle knows how to edit linux script. Although we need cm right now. We will do that later when we get a stable and bugless cm
Sent from my GT-S5282 using Tapatalk now Free
Ironman38102 said:
I have no knowledge of editing linux scripts. I think @prbluebottle knows how to edit linux script. Although we need cm right now. We will do that later when we get a stable and bugless cm
Sent from my GT-S5282 using Tapatalk now Free
Click to expand...
Click to collapse
Yeah can wait for that, CWM first priority and CM and so on...
So prbluebottle said that CWM 6 Booted, When it would be avail..?
No it didnt boot. Currently they are some issues that is preventing to boot cwm and cm10.1.
Sent from my GT-S5282 using Tapatalk now Free
Ironman38102 said:
No it didnt boot. Currently they are some issues that is preventing to boot cwm and cm10.1.
Sent from my GT-S5282 using Tapatalk now Free
Click to expand...
Click to collapse
Well bro i'm not good in CWM and CM so Will wait for you people to get over with that issues..
And that app2sd support i'll work on it.. :good:
Pushed proper extract-files.sh and setup-makefiles.sh to github @prbluebottle I hope its okay now. Please try to compile again and notify for any issues
till date cm is not for dual sim if it is ported only single sim will but hope for future cm developers develop for dual sim.
Press thanx if helpes
its totally free
sanchit0403 said:
till date cm is not for dual sim if it is ported only single sim will but hope for future cm developers develop for dual sim.
Press thanx if helpes
its totally free
Click to expand...
Click to collapse
We can do that later actullay. We need a stable cm
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Ironman38102 said:
About Working CWM
Click to expand...
Click to collapse
I have working CWM recovery and rooting guide. I guess after that, you only need to work on your ROM. Do not worry about smaller problems. I might lent a hand if time permits! I got Star online and I just wanted to do some experiments as it is a cheap device!
http://forum.xda-developers.com/showthread.php?t=2474165
Hello everyone!
I present to you a paranoid android 3.99 port for our Xperia SP
Changelog:
V2: Device no longer hard reboots on bootanimation
V1: initial release
BUGS:
V2: Device doesn't boot (stuck on bootanimation and ADB offline)
V1: Device doesn't boot (hard reboot after 10 seconds of showing splash screen)
Download: PA_HUASHAN_V2
Now as you can see this ROM port is not booting but at least it doesn't do a hard reboot anymore! Currently I have no ADB access as it is listed as offline when doing: ADB devices of course I can't figure out the problem myself so I'm asking you guys for help. Since there is no logcat I know that it might be nasty to determine the problem and where the phone stops booting. I hope you guys can help me get this ROM to boot so we will finally have a working PA rom
thanks to: @-NickHalden- for his nice guide on how to port ROM's
@FXP for the base rom (cm10.2)
and the paranoid android team for the ROM that was ported (pa 3.99 from nexus 4)
Why don't you simply build from source?
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
I'm trying that as well but i'm having some issues getting these files working
<device>.adds
<device>.removes
pa_<device>.conf
pa_<device>.mk
If I could easily get/make these files a source build would already be here
Do you have a idea on how to create these files? or where I can get them?
for example for the .adds file I need something like this (this comes from nexus 4)
https://github.com/ParanoidAndroid/android_vendor_pa/blob/jb43/manifests/mako.adds
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
kamarush said:
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
Click to expand...
Click to collapse
OK this is the .adds file I just made can you take a look at it?
huashan.adds
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
A long ago, i dont have see you on xda....
now you've back....great master
OK guys PA is currently building from source! now let's prepare to wait a long time xD
noahvt said:
OK this is the .adds file I just made can you take a look at it?
huashan.adds
Click to expand...
Click to collapse
This file will be almost the same as the cm dependencies. So this isn't good.
Levered said:
A long ago, i dont have see you on xda....
now you've back....great master
Click to expand...
Click to collapse
Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung
noahvt said:
OK guys PA is currently building from source! now let's prepare to wait a long time xD
Click to expand...
Click to collapse
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
I'm a huge fan of PA, I hope this one for our SP will progress nicely. Keep up the good work devs. Currently on CM coz stock is too laggy on my one.
Tapatalked from my Xperia P
noahvt said:
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
Click to expand...
Click to collapse
Just need to update/add pa_huashan to the pa vendor makefiles.
@kamarush
Remember you in developing the Xperia line 2011. Glad to see it with our Xperia SP. Some project in mind?
[QOUTE]Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung [/QUOTE]
Great, i really want rom by you. i hope you can make it soon..:good:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
noahvt said:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
Click to expand...
Click to collapse
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
MrSteve555 said:
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
Click to expand...
Click to collapse
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
noahvt said:
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
MrSteve555 said:
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
Click to expand...
Click to collapse
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
noahvt said:
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
MrSteve555 said:
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
Click to expand...
Click to collapse
Unfortunately it probably will have the freeze bug as it's based on the vendor blobs that bagyusz uses
Sent from my C5303 using XDA Free mobile app
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.