I've been trying to get a working build over the past week or two for the GS4 and I wanted to clarify.
My UT repo is up to date, yet when using the lunch cm_jfltetmo-userdebug command tells me that it's PLATFORM_VERSION=4.2.1. Shouldn't this be 4.2.2 or have the sources just not been updated to 4.2.2 yet? If it's just that the phablet sources are still on version 4.2.1, is there any way I could at least update my local Ubuntu repo to match 4.2.2? For reference, my CM build tells me the correct version number...
lordcheeto03 said:
I've been trying to get a working build over the past week or two for the GS4 and I wanted to clarify.
My UT repo is up to date, yet when using the lunch cm_jfltetmo-userdebug command tells me that it's PLATFORM_VERSION=4.2.1. Shouldn't this be 4.2.2 or have the sources just not been updated to 4.2.2 yet? If it's just that the phablet sources are still on version 4.2.1, is there any way I could at least update my local Ubuntu repo to match 4.2.2? For reference, my CM build tells me the correct version number...
Click to expand...
Click to collapse
If you look at http://phablet.ubuntu.com/gitweb you will see branches named phablet-saucy, amorng others things (like working with flipped images only) it updates on top of cm-10.1.2 which is based out of 4.2.2
You can probably extra officially use it, but it still needs some testing and hasn't been announced.
Is there any way I can build for my device without the kernel and either inject the kernel after the build completes or make it a separate flashable unit?
Bump
lordcheeto03 said:
Is there any way I can build for my device without the kernel and either inject the kernel after the build completes or make it a separate flashable unit?
Click to expand...
Click to collapse
You can just put in the boot IMG in the zip after it builds, or you can put a prebuilt boot.IMG in the device repo.
Sent from my LG-LS970 using Tapatalk 4 Beta
Related
Is there a simple way I could port the lastest PAC ROM to the atrix i am aware that th3bill has a 4.1.2 version up, but i would perfer a 4.2.2 with the new kernel and Halo (From PA)
Anybody know a way to port, or can port it across the Atrix 4G ?
Good way: Await for new kernel and port
Another Way: follow this mini-guide made to an HTC Pyramid user. You can build from source. -> http://forum.xda-developers.com/showthread.php?t=2008344
Make sure you build a repo sync with repo init -u git://github.com/PAC-man/android.git -b <branch>
Then well, maybe it'll work. Other way to port is with rom porting tool; but its a non-guaranteed porting --> http://forum.xda-developers.com/showthread.php?t=2196491
jhonnyx said:
Good way: Await for new kernel and port
Another Way: follow this mini-guide made to an HTC Pyramid user. You can build from source. -> http://forum.xda-developers.com/showthread.php?t=2008344
Make sure you build a repo sync with repo init -u git://github.com/PAC-man/android.git -b <branch>
Then well, maybe it'll work. Other way to port is with rom porting tool; but its a non-guaranteed porting --> http://forum.xda-developers.com/showthread.php?t=2196491
Click to expand...
Click to collapse
Right thank you I will look into it, I was thinking more of a natve port but I guess all the work to being put on the kernel at the moment.
kingbobski said:
Right thank you I will look into it, I was thinking more of a natve port but I guess all the work to being put on the kernel at the moment.
Click to expand...
Click to collapse
I think you can try porting something from Infuse -> http://forum.xda-developers.com/showthread.php?t=2038579 but I think you cannot post if you manage to get it working.
I might try to get it booting, if possible; but I encourage you to wait for sources to the kernel to be available; then building PAC ROM from source.
I'll keep you updated if I get it booting at least (I hightly doubt I get it working)
jhonnyx said:
I think you can try porting something from Infuse -> http://forum.xda-developers.com/showthread.php?t=2038579 but I think you cannot post if you manage to get it working.
I might try to get it booting, if possible; but I encourage you to wait for sources to the kernel to be available; then building PAC ROM from source.
I'll keep you updated if I get it booting at least (I hightly doubt I get it working)
Click to expand...
Click to collapse
Right thanks alot I'm new to whole building the sources, I will figure it out eventually I just really want Halo so much on the Atrix but no ROM has it yet !
kingbobski said:
Right thanks alot I'm new to whole building the sources, I will figure it out eventually I just really want Halo so much on the Atrix but no ROM has it yet !
Click to expand...
Click to collapse
That makes us two
The closest PACROM we have is by th3bill but it's android 4.1.2 without the halo and i like the 4.2 Quick setting and lockscreen D: but i like the DPI setting in PA, so PACROM running at 4.2.2 with new kernel is ideal !
THREAD DEPRECATED! project moved here:
http://forum.xda-developers.com/goo...om-openpdroid-patched-cyanogenmod-11-t2817655
----------------------------
title is self explanatory. I'll share my builds in case others are interested.
please look for them here:
THREAD DEPRECATED!
EDIT:
information in the edit below is not longer current. please see:
http://forum.xda-developers.com/showpost.php?p=52664423&postcount=5
EDIT:
additional information as requested by moderator:
this is just a build of master branch cyanogenmod for hammerhead patched with the latest openpdroid patches as available on openpdroid's github (https://github.com/OpenPDroid/OpenPDroidPatches). not a single line of code was changed, as the source level patches still apply without errors.
it used to be the case that auto-patcher could smali-patch binary android builds. now auto-patcher has gone unmaintained and smali patches no longer apply on recent builds of cyanogenmod.
many people are not willing to build from source and are abandoning openpdroid. i will continue to use it on kit-kat at least. these are my builds and are shared here as a convenience for hammerhead users who do not want to build their own OS. no changes were introduced. source code is available on the respective project githubs.
NOTE: uploads are in progress, please check later.
new build (currently uploading to the dropbox link)
new build (currently uploading to the dropbox link)
this one cherry picks this:
http://review.cyanogenmod.org/#/c/62281/
to support 5x5 grid size in the home screen.
new build (currently uploading to the dropbox link)
CM11-M6 broke OpenPDroid patch compatibility. i forked OPD to restore compatibility, fix several bugs and clean up the code. sources here:
https://github.com/Lanchon/OpenPDroid-patches
cherry picks this (patchset 6) to support 5x5 grid size in the home screen:
http://review.cyanogenmod.org/#/c/62281/
Is it Art compatible ?
yuuzhantar said:
Is it Art compatible ?
Click to expand...
Click to collapse
Dude,
OP's built CM11 from source with the added OpenPDroid patches. The ROM that he's linked to us is just CM11 with OpenPDroid.
Your question should be: "Does CM11 allow you to select different runtimes?".
The answer to that question is: "Yes, this option is located under 'Developer Options'.".
If you next question is: "How do I access 'Developer Options'?", then look here: http://www.youtube.com/watch?v=XcFVRDZ5Z9Q.
LewisD94 said:
Dude,
OP's built CM11 from source with the added OpenPDroid patches. The ROM that he's linked to us is just CM11 with OpenPDroid.
Your question should be: "Does CM11 allow you to select different runtimes?".
The answer to that question is: "Yes, this option is located under 'Developer Options'.".
If you next question is: "How do I access 'Developer Options'?", then look here: http://www.youtube.com/watch?v=XcFVRDZ5Z9Q.
Click to expand...
Click to collapse
Dude,
last time we had informations about pdroid, it was "not compatible with art"
http://forum.xda-developers.com/showpost.php?p=47902311&postcount=3796
As we don't know if it's because of the smali patching process or anything else,
I asked to know if a rom build with openpdroid included in the source was Art compatible.
And if I ask about Art, likerly I know how to use it (it switched since 4.4 was released ... )
Anyway, I'm done with CM, I switched to Omni this week-end after my phone became unusable, corruption of system data
yuuzhantar said:
Dude,
last time we had informations about pdroid, it was "not compatible with art"
http://forum.xda-developers.com/showpost.php?p=47902311&postcount=3796
As we don't know if it's because of the smali patching process or anything else,
I asked to know if a rom build with openpdroid included in the source was Art compatible.
And if I ask about Art, likerly I know how to use it (it switched since 4.4 was released ... )
Anyway, I'm done with CM, I switched to Omni this week-end after my phone became unusable, corruption of system data
Click to expand...
Click to collapse
you should try making your own rom before you bad mouth another.
flex360 said:
you should try making your own rom before you bad mouth another.
Click to expand...
Click to collapse
What business is it of yours?
I just sayed that I stop using cm after it crashed
Great to have someone building CM11 with openpdroid! Can't thank you enough!!!
Just one question:
Which kernel works best with this CM11? Any bad experiences?
Gesendet von meinem Nexus 5 mit Tapatalk 2
new build!
EDIT: this build is now based on android 4.4.4. remember to UPDATE YOUR GAPPS, or else...
sorry for the delay. i took off to europe to try out something with someone i met last year... it was a good bet that didnt work
but im back!!!
this build includes the custom home screen grid size selection that was merged into master recently, and so the old cherry pick slash hack (http://review.cyanogenmod.org/#/c/62281/) is gone for good.
NOTE: the update WILL NOT import your home screens beyond the upper left 4x4 area. so if you were using the previous cherry pick to increase the grid size, make sure you reshuffle the icons and widgets to the upper left 4x4 subset of each screen. anything outside that area will be lost. after the update you can increase the grid again and reshuffle back to your liking.
yuuzhantar said:
Is it Art compatible ?
Click to expand...
Click to collapse
all OPD changes are at the java/dalvik level, which makes me suspect that this build is as ART compatible as standard CM. that said, i've never used ART.
schwarzlichtkind said:
Which kernel works best with this CM11? Any bad experiences?
Click to expand...
Click to collapse
any kernel that works well with CM standard should work as well with this build.
@Lanchon
Are you getting com.android.phone has stopped messages upon first boot? I have tried full wipe, flashing different kernels, different gapps packages, etc to no avail. I am installing as secondary ROM with MultiROM by the way. Your previous build (M6 I think) installs this way with no issues.
Thanks so much for keeping pdroid alive!
stone_ship said:
@Lanchon
Are you getting com.android.phone has stopped messages upon first boot? I have tried full wipe, flashing different kernels, different gapps packages, etc to no avail. I am installing as secondary ROM with MultiROM by the way. Your previous build (M6 I think) installs this way with no issues.
Thanks so much for keeping pdroid alive!
Click to expand...
Click to collapse
i havent done a clean install since i dont know when!! nor have i used multirom. im using BaNkS gapps minimal with some add-ons and i dont experience a hitch. note that you need 4.4.4 gapps for this rom. recommend you format the system partition (if it makes sense with multirom) before flashing rom and gapps. then wipe cache and dalvik.
new build uploaded!
i will also be building for the i9100; first build is uploading now...
THREAD DEPRECATED! project moved here:
http://forum.xda-developers.com/goo...om-openpdroid-patched-cyanogenmod-11-t2817655
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
been trying to download repo for cynogenmod but have failed with numerous attempt. it is a huge file. is it possible to download just the required files to make cwm recovery 11 ? for kitkat? if possible how ?
Regrettably, no. You will need to repo sync the entire source code
shoey63 said:
Regrettably, no. You will need to repo sync the entire source code
Click to expand...
Click to collapse
alrite,
Code:
:git fetch aosp --tags tag android-4.4.4_2 +refs/tags/android-4.4.4_r2:refs/tags/android-4.4.4_r2
getting error on this one, can i download it manually from ?
https://android.googlesource.com/platform/prebuilts/sdk/+refs
Before going through the pain of doing that, does your device have Cm11 device tree?
shoey63 said:
Before going through the pain of doing that, does your device have Cm11 device tree?
Click to expand...
Click to collapse
no. as per my knowledge . My device is Lg g3 f460 k (snapdragon 805 variant). on kitkat 4.4.2. i searched far and wide but nothing related to it.
I only have 2 options now,
sync cm 12 (not sure if i could build a recovery here that will work in kitkat)
download individual files and put it the respective folders.
It would be better to start with cm11, which is known to be compatible with your device, as you have kitkat. But Cm12 has, at least in the later revisions, his own Recovery, which only offers a part of the options.
Spartaner25 said:
It would be better to start with cm11, which is known to be compatible with your device, as you have kitkat. But Cm12 has, at least in the later revisions, his own Recovery, which only offers a part of the options.
Click to expand...
Click to collapse
okay got everything but there is sdk folder missing in prebuilts.. help me download it manually perhaps ? my version of android is 4.4.2
I have a repo with android cm-12.1 as branch.
Now i want to update this repo to new CM version 13.0 without downloading the whole repo again.
Is that possible?
Unfortunately, no. Too many differences in the code bases.
MJPollard said:
Unfortunately, no. Too many differences in the code bases.
Click to expand...
Click to collapse
Okay,what happens if init a new branch (cm-13.0) in the same repo directory.
Is it faster than new repo?
Sent from my Micromax bolt
A27 using XDA Free mobile app
svprm said:
Okay,what happens if init a new branch (cm-13.0) in the same repo directory.
Is it faster than new repo?
Click to expand...
Click to collapse
Even if you could do that (and I'm not sure you can), the new branch would probably have to sync every single package over again, so you aren't really saving any time (and would likely cause major headaches). I think you really would be better off creating a completely new repo.