Related
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
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.
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
So now I am getting the below error while compiling Omni ROM:
hardware/qcom/media-caf/mm-video/vidc/venc/src/video_encoder_device.cpp:2450:17: error: 'struct venc_entropycfg' has no member named 'longentropysel'
Full Log:
http://hastebin.com/kudarekaqo.vhdl
Please help me in killing this last error
https://gerrit.omnirom.org/#/c/2940/
You need the equivalent of this patch for your kernel.
tilal6991 said:
https://gerrit.omnirom.org/#/c/2940/
You need the equivalent of this patch for your kernel.
Click to expand...
Click to collapse
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3
matrixzone said:
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3
Click to expand...
Click to collapse
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.
tilal6991 said:
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.
Click to expand...
Click to collapse
thanks man. How to see the code change from gerrit, checking the code change in github is very easy
Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.
chasmodo said:
Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.
Click to expand...
Click to collapse
In this particular case - look at the files changed by the commit and pull up the commit history for one of them - saves a lot of time.
Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.
We should have just fixed the remaining broken devices two weeks ago, oh well.
As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.
Entropy512 said:
Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.
We should have just fixed the remaining broken devices two weeks ago, oh well.
As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.
Click to expand...
Click to collapse
Also qcom devices that has "TARGET_QCOM_MEDIA_VARIANT := caf" in BoardConfig
I said that cause there are qcom devices that can work with no caf repos tbh..
An example would be Sony fusion3 devices.....
They worked on our android-4.4 branches perfectly fine prior to the qcom-4.4_2.7 merge
And fusion3 OmniROM/CyanogenMod Nightlies don't use any of the caf repos tbh . Though AOKP does
I keep getting this sync error:
Code:
Unexpected end of command stream
Fetching projects: 99% (415/419) fatal: Couldn't find remote ref refs/heads/android-4.4.2_r1
error: Cannot fetch android_frameworks_opt_mms
error: Cannot fetch TheMuppets/proprietary_vendor_htc
also, if i have a working cm official, what can i pull from it that would work with omni?
pandasa123 said:
I keep getting this sync error:
Code:
Unexpected end of command stream
Fetching projects: 99% (415/419) fatal: Couldn't find remote ref refs/heads/android-4.4.2_r1
error: Cannot fetch android_frameworks_opt_mms
error: Cannot fetch TheMuppets/proprietary_vendor_htc
also, if i have a working cm official, what can i pull from it that would work with omni?
Click to expand...
Click to collapse
The error is incomplete... I have no idea WHICH repo it's looking for that branch on since it's failing on multiple repos.
My guess would be a malformed omni.dependencies or a bad manifest in .repo/local_manifests/
I can tell you that syncing TheMuppets will result in broken builds 90% of the time.
What should I do for device props instead of muppets? And malformed omni.dependencies? That can affect it?
Sent from my One Xl using Tapatalk
pandasa123 said:
What should I do for device props instead of muppets?
Click to expand...
Click to collapse
https://github.com/DonkeyCoyote/
pandasa123 said:
And malformed omni.dependencies? That can affect it?
Click to expand...
Click to collapse
Yes, because what's in omni.dependencies gets synced as well. So if it tells repo to sync something that isn't there...
So omni is like building other ROMs? Just like building cm but change the cm parts to omni and adding twrp?
On the HTC one xl (Evita) and I really liked the multi window and thought we were overdue for an Omni build, so I wanted to try building it myself instead of waiting for one
Sent from my One Xl using Tapatalk
pandasa123 said:
So omni is like building other ROMs? Just like building cm but change the cm parts to omni and adding twrp?
On the HTC one xl (Evita) and I really liked the multi window and thought we were overdue for an Omni build, so I wanted to try building it myself instead of waiting for one
Sent from my One Xl using Tapatalk
Click to expand...
Click to collapse
In essence, yes. And I applaud you for being proactive and starting to compile for yourself.
PonsAsinorem said:
In essence, yes. And I applaud you for being proactive and starting to compile for yourself.
Click to expand...
Click to collapse
everything is syncing beautifully now...just one quick question...
for omni, should i add to the sync the CyanogenMod/android_device_htc_evita git repo with the build? i mean, with the build, the only thing that's really specified is the kernel and thats it, so there has to be more variety than just that, isn't there?
pandasa123 said:
everything is syncing beautifully now...just one quick question...
for omni, should i add to the sync the CyanogenMod/android_device_htc_evita git repo with the build? i mean, with the build, the only thing that's really specified is the kernel and thats it, so there has to be more variety than just that, isn't there?
Click to expand...
Click to collapse
Nope, not really. I'd try to sync only Omni's repos (and Google's), and leave other ROMs out of it. Assuming you're trying to build for the evita, and Omni doesn't have one for that, then you're best bet is to:
1. Fork (or create) a device tree
2. Make sure it's omnified
3. Add it to local_manifest
4. Once you have it up and running with minimal bugs, request to have Omni fork your device tree so it can be supported.
PonsAsinorem said:
Nope, not really. I'd try to sync only Omni's repos (and Google's), and leave other ROMs out of it. Assuming you're trying to build for the evita, and Omni doesn't have one for that, then you're best bet is to:
1. Fork (or create) a device tree
2. Make sure it's omnified
3. Add it to local_manifest
4. Once you have it up and running with minimal bugs, request to have Omni fork your device tree so it can be supported.
Click to expand...
Click to collapse
Omnified? This always confuses me. How do users have twrp if they have cwm installed? Will it overwrite?
And for the Evita tree, its basically me downloading cm tree locally and changing it to comply with omni? And then uploading it to my git so it can be added to local_manifest with that?
Sent from my One X using Tapatalk
pandasa123 said:
How do users have twrp if they have cwm installed?
Click to expand...
Click to collapse
They don't. It's either one or the other.
pandasa123 said:
Will it overwrite?
Click to expand...
Click to collapse
If you install it, yes. You don't have to, but it's recommended.
pandasa123 said:
And for the Evita tree, its basically me downloading cm tree locally and changing it to comply with omni? And then uploading it to my git so it can be added to local_manifest with that?
Click to expand...
Click to collapse
More or less. If you haven't seen this yet:
Porting Omni To Your Device
everything is synced and i followed the guide about the .mk files and vendorsetup.sh
at the beginning of the build, it showed these issues and i was wondering what they meant
Code:
build/core/product_config.mk:241: *** No matches for product "omni_evita". Stop.
WARNING: Trying to fetch a device that's already there
EDIT: the build died:
Code:
build/core/product_config.mk:241: *** No matches for product "omni_evita". Stop.
** Don't have a product spec for: 'omni_evita'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'