Database Users

[Thinktank]Bringing Jellybean to the Play -- Alpha GSM/CDMA [8/22]

Xperia Play Users,
I am currently working on bringing CM10 to the Play, and I'm looking for input from anybody else who has ideas.
The Rules:
Post something constructive, no "Good Luck" "reserved" etc. this thread is for working through problems when building CM10
That said.
Update: I'll be posting errors here, so it'll be easy to keep track of.
First error I hit (& fixed? (compiler hasn't failed yet on this one)) deals with hardware/qcom/display/libcopybit where copybit_c2d.cpp fails to compile with a couple of errors related to "KGSL_USER_MEM_TYPE_ION" is not declared. (iirc)
I fixed this (I think) by replacing CM10's qcom/display with caf's qcom/display
Second error: (Erroring out right now)
In-line kernel building. I'm getting a (possible) GCC compiler false error where it says
Code:
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: In function 'wl_iw_set_pmksa':
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5335:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5338:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: At top level:
cc1: error: unrecognized command line option "-Wno-unitialised" [-Werror]
Possible fix: for now turn off in-line kernel building until either error is solved.
Error 3 -- Removed in-line kernel building, but forgot to set device/semc/zeusc/prebuilt/kernel to copy to out/target/product/zeusc/kernel ... whoops
Error 4 -- The way things are sent to logcat has been changed from ICS
Code:
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_string:device/semc/msm7x30-common/liblights/lights.c:87: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_int:device/semc/msm7x30-common/liblights/lights.c:66: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function set_light_backlight:device/semc/msm7x30-common/liblights/lights.c:131: error: undefined reference to 'LOGV'
Fixed by copying over liblights/ from jellybean version of msm7x30-common/
Error 5 -- Same error happens with msm7x30-common/libsensors/
Fixed the same way as error 4
Error 6 -- Last error I'm gonna talk about tonight:
I did (apparently) a half baked revert to using a prebuilt kernel & it just bit me in the butt. I'll fix it tomorrow & keep updating this.
Fixed it by using half of FXP's custombootimg.mk where it calls (PRODUCT_OUT)/kernel instead of (TARGET_PREBUILT_KERNEL)
Anybody else up for learning with me & briniging JB to the Play?
Pax
UPDATE: Pre-alpha release are available here: http://www.mediafire.com/?6ggud46a7c6cq
Latest kernel is here: http://forum.xda-developers.com/showpost.php?p=29498363&postcount=233
Remember, this is an alpha, a lot of stuff does not work. Please logcat any errors you find, otherwise (unless it's something like baseband unknown) I WILL IGNORE THEM
What Works:
CDMA Data
Calls
SMS
AUDIO!!
HW Video
GPS
What Doesn't Work:
Haven't tested to much, you guys tell me

I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app

sasukekun67 said:
I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app
Click to expand...
Click to collapse
Thank you, I think for JB CM wants to use -O2 when compiling so I'm not gonna touch that one (for now)
A Good place to start would be with Keiran's building ICS tutorial with some changes.
First off, I'm using Ubuntu 10.04 LTS, but Ubuntu 12.04 LTS *should* work (no guarantees)
To download the vendor tree (vendor/semc)
use this instead of what Keiran has (koush cleaned out a lot of the vendor trees out of his git, and mine is outdated)
Code:
git clone https://github.com/kali-/proprietary_vendor_semc.git -b ics semc
also, I'm using the ICS device tree (same as keiran) instead of JB because the JB tree's are not 100% functional right now.
Pretty much if you follow that (& I suggest instead of doing make -j# bacon do mka bacon) & run into any errors, i'll help with whatever suggestions I might have (or anybody else)
Note: If somebody needs help trying to build AOKP, I'll help, but I'm not as familiar with the source as I am with CM
Pax

Also, before I forget, here a how-to sync caf's (code aurora forums) repo (similar to cm/AOSP/etc)
https://www.codeaurora.org/xwiki/bin/QAEP/
The branch I synced was jb.
Pax
Sent from my R800x using Tapatalk 2

First build is complete, I'm need to make a nanadroid & flash a new kernel (I'm on keics/CNA right now so it'll be a little bit before I post results )
Pax

hi,
it won't boot on sony ericsson hdpi devices without msm.... changes (look at mini pro thread you will find a lot of usefull information about it)
you need to enable triple buffer in the kernel

Thanks Nickholtus, i'll look into it.
Status 6 error in the update-script (really? off the cm-10 building ?!?!) so i'm working on that now...

if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel

nickholtus said:
if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel
Click to expand...
Click to collapse
I'll probably base it off either FXP or Mjolnir's kernel (sorry Lupus)
[sritke]Do you have a link with a how-to add in triple buffer? [/strike] CAF!! - https://www.codeaurora.org/gitweb/q...it;h=50c3bc621e2cf0c3587b1827d931738d148c33d8
UPDATE: Nickholtus, it's not this easy, is it?!?! https://www.codeaurora.org/gitweb/q...;hpb=1125e58c5744e1ad833e30e5d2a74eb6dca1ca20
Also, if anybody wants to try to fix the update-script, i've attached it

no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
edit:
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix

nickholtus said:
no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
---------- Post added at 09:03 PM ---------- Previous post was at 08:58 PM ----------
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix
Click to expand...
Click to collapse
Here's the best diff (all 3) i've found for the commit
https://www.codeaurora.org/gitweb/q...ff;h=acffb1675f468a85f528e01707f3fa98f45b77f8

i am going ask kamarush and see what he thinks
he thinks it can probaply fix it

While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.

Sythedragon said:
While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.
Click to expand...
Click to collapse
hahaha, different type of scripts, but thanks for the idea
Pax
Also: Made the changes in the kernel I have on hand, fxp's from cm9/10 source. I've added in the correct stuff to cyanogen_zeus_defconfig & mach-msm/board-semc_zeus.c as soon as I'm done downloading Doom's ndk, i'll try & build it & see if it works
Pax

kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster

nickholtus said:
kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster
Click to expand...
Click to collapse
I was, then I got arrowed in the knee
Or i would be, but then my git clone downloads at ~200 kb/s

Nickholtus,
Here's a test kernel, the changes are in the zImage, the ramdisk is FXP's from well, it's a source build off code from yesterday.

thanks
going to try it now
still the same error
edit: i need to get adb working
doesn't find the device

Lemme look into it, i'll test it out shortly (trying to get my build of cm10 to install )
Pax
Edit: Nickholtus, could you post a link to your build, mine just doesn't want to work
Pax
Edit 2: I think it's because i'm coming from CNA to CM10, i'm gonna build cm9 then retry with that
Pax

i can't upload my build, the upload speed here is 15kbps atm

[Tool] ROM Porter

Tool Aces Present
Rom-Porter
Disclaimer​
Code:
title disclaimer
echo.
Echo you and you alone are choosing to use this tool. So i am not responsible if anything happens to you or your phone due to it.
Echo.
Click to expand...
Click to collapse
Pre-Requisites​1. notepad++
2. Better if you know the manual steps.
Click to expand...
Click to collapse
Steps​1. Download the zip and extract it.
2. Read the help and pre requisites first.
3. Run the rom-porter.bat file
4. Start porting and follow instructions.
Click to expand...
Click to collapse
Features​• Pause and resume Porting.
• Manufacturer ROM Port.
• Lewa and Joy OS Porting.
• Fully automated.
• Build.prop and init.d tweaks.
• Update feature.
• Readable Log File.
• Many Fail safe's.
Click to expand...
Click to collapse
Faq​q. It gives x error
a. Give which step it is(No.), what error it gives. and most importantly attach a log using 'Pull Log File' Option.
q. it says findstr not recognized as an internal or external command
a. just close the tool and restart it.
q. it says xcopy not recognized as an internal or external command
a. just close the tool and restart it.
q. How can i add my own build.prop and init.d tweaks
a. for build.prop, copy the tweak in a txt file, give it a name without space and copy it to essentialsbtweak
for init.d, copy the header "#!/system/bin/sh" and then the tweak, give it a name without space, remove the file extension and copy it to essentialsitweak
Q. I want x feature.
A. Just reply here what you want, if its possible by me, I'll add it asap
Click to expand...
Click to collapse
Credits​Rishab.Raj37 for his amazing guide on Porting rom
GalaxyUser for his excellent guide on porting manufacturer ROMS
blindndumb for his great guide on Porting Lewa and Joy OS
po8pimp for new awesome theme and exe packing
Abhinav2 For new coding and testing
PluginSz For testing the tool
Click to expand...
Click to collapse
If you like this tool press the thanks button, and consider giving this thread a five star Rating
Oh and if you upload the rom on xda, do give me credits.​
XDA:DevDB Information
Rom Porter, Tool/Utility for the Android General
Contributors
mnishamk
Version Information
Status: Stable
Current Stable Version: 3.6
Stable Release Date: 2013-07-24
Current Beta Version: 3.7
Beta Release Date: 2014-09-18
Created 2014-10-23
Last Updated 2014-10-23

Downloads and Changelogs
Download
Head Over to the download section
changelog
Code:
[19.12.14]
v3.9
-> Created self-extraction tool
-> Added Custom theme options
-> Changed bootup animation
-> Thanks to po8pimp
[06.12.14]
v3.8
->Fixed find and findstr error
->Changed the update tool routine.
[18.09.14]
v3.7
->Now can port Kitkat roms. Added kitkat filesystem changes
[24.7.13]
v3.6
->fixed bug in manufacturer rom port
[2.7.13]
v3.5
-> Automated Changing EOL character.
-> finally FULLY Automated.
[17.6.13]
v3.3
-> Added Lewa and Joy OS Porting.
-> Changed the way the sequence is executed.
-> Extended help menu.
-> Changed the logic in some cases.
[6.4.13]
v3.1
-> HTC network auto select fix
[27.5.13]
v2.9
-> small changes in coding
[26.5.13]
v2.8
-> Supports Manufacturer Roms (Testing phase)
-> Squashed a few Bugs
[20.5.13]
v2.7
-> Hopefully, Patched Find and Findstr error for good.
-> Fixed a logical Error
-> Updated Logs.
[17.5.13]
v2.6
->added Log Feature.
[16.5.13]
v2.5
-> added update option
[16.5.13]
v2.4
-> added option to copy zip to sd card.
[15.5.13]
v2.3
-> added Init.d tweaks
[15.5.13]
v2.2
-> added build.prop tweaks.
[14.5.13]
V2.1
-> Modified coding to make version selection automated. Thanks to abhinav2
v2.0
-> supports 32 bit too.
[13.5..13]
v1.9
-> first release

"1. Download the zip and extract it. ..."
SO, where is the zip ???

Good work
Cheers,
AJ

Abhinav2 said:
Lol u again forgot the dl link
Well anyways awesome work as always.....
Cheers,
AJ
Click to expand...
Click to collapse
No I didn't. I was updating the post.
Regards
N

mnishamk said:
No I didn't. I was updating the post.
Regards
N
Click to expand...
Click to collapse
Sorry opened this page a bit earlier.....though commented late so at that time the link wasn't up Just refreshed the page and saw the link
Keep it up anyways :good:
Cheers,
AJ

version 2.2 released
now you can add build.prop tweaks too.

Your kidding!! Great idea, a porting utility tool..Hats off to you and everyone involved with development..
XT912 CDMA Pac Man 4.2.2

1droidmod said:
Your kidding!! Great idea, a porting utility tool..Hats off to you and everyone involved with development..
XT912 CDMA Pac Man 4.2.2
Click to expand...
Click to collapse
The idea was alread there. And the tool too
We only made it a lil more automated.
Regards
N

hey guys ,can i port a cm10 touchwiz rom to a cm10 rom for LG P700 ? ..

I don't think it can be used, coz when they are from different manufacturers, they'll need heavy framework modding etc which the tool does not do.
So its better to port from the sam manufacturer and a similar specs device.
Regards
N

i understand ,that was the real fun in all this porting thing ,i realy wanted a touchwiz inspired rom ! thanks a lot !

The tool won't help you with it coz each one would be different. There's a guide arounf here for porting manufacturer roms, try that
Regards
N

v2.3 released. supports init.d tweaks

Thanks ,maybe someone wil develope an automatic porter like this one for diferent manufactor devices..until then i'm going to search the manual way to port id! Cheers
Sent from my LG-P700 using xda app-developers app

keemo.rom said:
Thanks ,maybe someone wil develope an automatic porter like this one for diferent manufactor devices..until then i'm going to search the manual way to port id! Cheers
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
I'll try it, :thumbup:but if its too hard, I may abandon it.
Regards
N

mnishamk said:
I'll try it, :thumbup:but if its too hard, I may abandon it.
Regards
N
Click to expand...
Click to collapse
Thats great news ,i hope you will have great succes!!
Sent from my LG-P700 using xda app-developers app

keemo.rom said:
Thanks ,maybe someone wil develope an automatic porter like this one for diferent manufactor devices..until then i'm going to search the manual way to port id! Cheers
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
An automatic "porter" for different devices roms is kinda impossible as this software would be able to practise magic lol. This means it would download the related kernel sources, edit them and insert correct code, including proprietary device files, configure the kernel and compile it (besides of that it must grab the toolchain and set the PATHs, etc, etc..). Then it would decompile the roms framework (of course including full automatic smali magic ) detecting the correct requirements and edit that stuff before it compiles and signs it with system sign keys.. And last but not least it has to compile board related drivers (for kernel and rom) and bake them into the project. When finished all processes it builds a full working flashable rom zip for your device - and if you are nice it will also download the right Gapps and copy all of it to your SDcard
Sorry for sounding like an a**hole Just joking a bit.
The point is that a software like that would do all the work for devs and we all wouldn't have to work that much.. It would be nice, but it's just too much code, too complex for a software to do this. Porting a rom to another device cannot be done with prebuilt files usually. You need to work with the source and that's a lot of work. Except the devices are using almost the same board, chipset and CPU.
Besides of that: This is a nice tool! Thanks for your work, this will be helpful for beginners to perform some first steps! :good:

im trying to port axiom for the hd to the m im using dhackers pere aosp as the base for the m. everything extracts fine then starts the porting process then at the end it says THE SYSTEM CANNOT FIND THE FILE SPECIFIED THE FILENAME, DIRECTORY NAME, OR VOLUME LABEL SYNTAX IS INCORRECT. that is after desktop\romporter\temp\platform.xml 2 files moved any ideas?

By the end you mean which step? The end of extraction?
Regards
N

Porting ROMs

How does one port ROMs to another phone? I'm looking to try and port Xylon to the Find 5.
Sent from my X909 using xda app-developers app

it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.

if you are building from source:
Find the 4.2.2 source code of the ROM you want to port
Get the manifest.
Add the CM10.1 device/kernel tree and proprietary libs in the .repo/local_manifest/roomservice.xml
sync all the repos
(do whatever the source might need you to set up: EG paranoid android, need you to setup your device properly in vendor/pa/* files)
compile. Fix any problems(maybe missing files, etc)
you could try a non-4.2.2-based ROM to port, but you'll run into more incompatibility issues to fix

mbh87 said:
it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.
Click to expand...
Click to collapse
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app

newbcake said:
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
No, build from source since it's available.

mbh87 said:
No, build from source since it's available.
Click to expand...
Click to collapse
You mean Oppo's source or AOSP from Google? I presume AOSP
Sent from my X909 using xda app-developers app

assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build

paperWastage said:
assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build
Click to expand...
Click to collapse
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]

newbcake said:
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]
Click to expand...
Click to collapse
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first

paperWastage said:
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first
Click to expand...
Click to collapse
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.

Well, I removed the HTC lines from manifest.xml (maybe not a good idea?) but anyway, it finished syncing after.

mbh87 said:
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.
Click to expand...
Click to collapse
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.

paperWastage said:
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.
Click to expand...
Click to collapse
Understood. I'm syncing up the Cm10 now. Thanks!
Is is best to do this all on Linux, Mac, or Windows?

It isn't possible to do it on windows so one of the other two.

mbh87 said:
It isn't possible to do it on windows so one of the other two.
Click to expand...
Click to collapse
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app

newbcake said:
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup

paperWastage said:
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup
Click to expand...
Click to collapse
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.

newbcake said:
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.
Click to expand...
Click to collapse
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file/line might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast/lunch & mka

paperWastage said:
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast & mka
Click to expand...
Click to collapse
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.

newbcake said:
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.
Click to expand...
Click to collapse
you could source the log for errors
or just run the compile script again and again.... the scheduler will continue building other packages, but it'll come to a point where it can't build anything else without that broken package.... and hence, the error in the log will be obvious(since everything else is already built, no logs from them)
it should be an error-free compile, but sometimes things could happen (a small tweak in package/A gives some problems when compiling with package/B)
I would say, most likely there's some build package incompatibility in your system.

[TOOL] Starting a new tool

I'm a beginner in AndroidModding, and the ways that I have found so far are boring (as well as my ability to describe my project).
Basically, I'm developing a visual tool to facilitate mods creation. I know there are already some, but I intend to make a better base for beginners as I don't make crap.
I'll leave out some screen shots and when I make the program more stable I'll upload a first test version.
I wish everyone who has any idea about what I can add in the project manifest and suggest the same. At the end I will give credit to all who help me improve things.
And also, if you guys think this is will be useless please tell me this too
[Change log]
14/10/13
Working features:
-Create and manage Devices and ROMs
--Auto framework change 90% complete
-Create multiple projects of same APK
-Import an APK via dialog box to avoid mistake at folder arrange
-Decompile, Build, Auto META-INF PATCH, Recompile and ZipAlign just at one click for each function.
-Shortcut to working folders
-Debug output
-Set zipalign compression option
Features i'm working on:
-Auto change framework for different devices
-Auto mod scripting
-Translation features
-Pull/Push files via ADB
Features that I already tought about:
-Multi-Framework capability: Switch between frameworks to mod apps of different Roms and devices without complication.
-Project creation: Create a new independent mod with just one click without losing your previous project.
-Auto patch: Select a Mod in a list, choose your preferences and watch while program do the hard work for you.
-Create a auto patch youself: If you are already experient and want automate your mods, you can create a list of actions to auto apply into an apk.
-Create a Zip file to install in recovery mod
-Default stuff to ApkTool like decompile, build, recompile, blabla
[add 06/10/13 18:30]
-Adb pull/push: send or get files from your phone by adb connection
-Smali code autopatch support
ps: I don't know speak english as well, so, sorry about any mistake

This is good and seems fun
will wait for a test release

Will it be Open Source ?
Then we could improve your work by submitting patches

Pixelvernichter said:
Will it be Open Source ?
Then we could improve your work by submitting patches
Click to expand...
Click to collapse
Its a good idea, I'll think aboit it
Sent from my GT-I9100 using xda app-developers app

Also, if you need an tester for your tool I have time and i would do it

That tool will be great for a nope like me thanks
Sent from my GT-I9100 using xda app-developers app

shfddi being
:good:
i'll help to test if u want to..

Live log would be good. To watch as phone boots into an inevitable bootloop when trying something new. Saves running log separately and lets you view as it happens. With filtering would be good. Adbmagic did something similar but you cant copy or search the log.
Sent from my GT-I9305 using Tapatalk 4

Solved!Does anyone know if a xml like instead when inner value is empty interferes something or just make file bigger? I mean to Android, because I know their same thing.
Also, who wants help me making me an logo? I was thinking about an android with Merlin's costume, but I don't have the skills to reproduce this
Goldieking said:
Live log would be good. To watch as phone boots into an inevitable bootloop when trying something new. Saves running log separately and lets you view as it happens. With filtering would be good. Adbmagic did something similar but you cant copy or search the log.
Sent from my GT-I9305 using Tapatalk 4
Click to expand...
Click to collapse
That's a good idea, i'll try implement that, thanks
Sent from my GT-I9100 using xda app-developers app

SkyaTura said:
Does anyone know if a xml like instead when inner value is empty interferes something or just make file bigger? I mean to Android, because I know their same thing.
Also, who wants help me making me an logo? I was thinking about an android with Merlin's costume, but I don't have the skills to reproduce this
That's a good idea, i'll try implement that, thanks
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Bump !
Logo in progress
( Android with Merlin Costum. lol xD )

New changes at thread!!!
I pretend to release a beta version this week yet
Pixelvernichter said:
Bump !
Logo in progress
( Android with Merlin Costum. lol xD )
Click to expand...
Click to collapse
Can we see a preview of our MerlinDroid?
(i would be annoying if i ask an icon version?)

Compiling i605

I can't get past this error
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/i605/omni_i605.mk]]: "device/samsung/l900/full_i605.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/i605/omni_i605.mk]]: "device/samsung/l900/full_i605.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_i605'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
real 0m0.122s
user 0m0.042s
sys 0m0.089s

apophis9283 said:
I can't get past this error
Click to expand...
Click to collapse
Do you have vendorsetup.sh in your /device/samsung/l900/ folder? If not, create it and put this in it:
Code:
add_lunch_combo omni_i605-userdebug
Do you have full_i605.mk in your device tree? Also, omni_i605.mk and i605.mk?

I had to put the i605 make file in the l900 folder. Doesnt make sense. After all that I got it to compile but no boot.
Sent from my SCH-I605 using Tapatalk 2

Also if l900 is important to build i605 then why doesnt it pull it when I brunch and pulls everything else?

apophis9283 said:
Also if l900 is important to build i605 then why doesnt it pull it when I brunch and pulls everything else?
Click to expand...
Click to collapse
Because nobody did a device bringup yet, so the compiler doesn't know that it needs some common stuff as well.
After examining the Omni repo: how can it pull i900 when the device tree does not exist in the Omni tree yet?
https://github.com/omnirom/

chasmodo said:
Because nobody did a device bringup yet, so the compiler doesn't know that it needs some common stuff as well.
After examining the Omni repo: how can it pull i900 when the device tree does not exist in the Omni tree yet?
https://github.com/omnirom/
Click to expand...
Click to collapse
Im looking at omniroms github. Android device samsung l900 is there and does have a kit kat tag. Its l900 not i900
l900 is Sprints note 2. i605 is Verizons Note 2. If having to put the i605 make file in the l900 folder is whats causing it not to boot, that means its compiling for l900 even though I want it to compile for i605. Something may be borked in build. No reason for i605 to depend on l900. Somethings just not right
Sent from my SCH-I605 using Tapatalk 2

apophis9283 said:
Its l900 not i900
Click to expand...
Click to collapse
Oh...sorry, I thought it was i900.
Anyway, you've got to create your l605 device tree and put all the l900-common references (if they exist) in it: take a look at n7100 or n7000 tree at Omni Github and you'll see what I'm talking about. There's no way for compiler to know what to do unless you tell it.

chasmodo said:
Oh...sorry, I thought it was i900.
Anyway, you've got to create your l605 device tree and put all the l900-common references in it: take a look at n7100 or n7000 tree at Omni Github and you'll see what I'm talking about. There's no way for compiler to know what to do unless you tell it.
Click to expand...
Click to collapse
My i605 folder looks identical to the way n7100 is setup. Its weird, It screams to have full_i605.mk put in the l900 device folder. It shoudlnt be doing this. Somethings borked.
All this over a typo. I found it. Compiling now without a l900 folder

In omni_i605.mk
Change
# Inherit device configuration
$(call inherit-product, device/samsung/l900/full_i605.mk)
change it to
# Inherit device configuration
$(call inherit-product, device/samsung/i605/full_i605.mk)

@apophis9283 I saw your post about No cell/data on the i605 nightly.. was that your build? SlimROM seems to have a working AOSP 4.4.2. Is there any chance that something from their project might help get OmniROM up and running on i605?
I would be willing to work on this, but have no experience or idea where to start.
Thanks.

travisn000 said:
@apophis9283 I saw your post about No cell/data on the i605 nightly.. was that your build? SlimROM seems to have a working AOSP 4.4.2. Is there any chance that something from their project might help get OmniROM up and running on i605?
I would be willing to work on this, but have no experience or idea where to start.
Thanks.
Click to expand...
Click to collapse
Data works on cm and aokp so far. I just havent looked any further into it yet. I got data on aokp by using cms device tree so i never isolated the actual problem. Omni requires an omni make file in the devices tree. So just need to pull in cms trees and make adjustments so omni will compile it
Sent from my SCH-I605 using Tapatalk 2

I quit messing with it. That roomservice file is annoying.
Sent from my SCH-I605 using Tapatalk 2

apophis9283 said:
I quit messing with it. That roomservice file is annoying.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
..does that mean pulling from the other projects won't work, or just won't work without ALOT of work? I don't know what the roomservice file is.. :?

I wanted to use a local manifest. Well when I tried to compile of course there were going to be errors but omnis response is to create the roomservice file. So its hard to tell what i may need to change around. The way aokp handles it is a million times better
Sent from my SCH-I605 using Tapatalk 2