Hi, I am trying to incorporate a boot animation from one ROM from source and use the repo to apply it to another ROM from source. I am working on creating a ROM from source that is tweaked out. Is there an easy way to do this?
Rondeau79 said:
Hi, I am trying to incorporate a boot animation from one ROM from source and use the repo to apply it to another ROM from source. I am working on creating a ROM from source that is tweaked out. Is there an easy way to do this?
Click to expand...
Click to collapse
Copy in system/media and permission 644.Reboot.
Cypresshill555 said:
Copy in system/media and permission 644.Reboot.
Click to expand...
Click to collapse
Not quite what I want to do. I need to take a bootanimation from a GitHub source. Then replacing that to my local repos.
Related
anyone know if it's feasible to build the cm10.1 kernel without syncing the entire source?
I've tried googling it numerous times but nothing came up pertaining to it. i did however find how to build the cm9 kernel without syncing the entire source, bit couldn't get it to build...
thanks if anyone can help me five my way
ztotherad said:
anyone know if it's feasible to build the cm10.1 kernel without syncing the entire source?
I've tried googling it numerous times but nothing came up pertaining to it. i did however find how to build the cm9 kernel without syncing the entire source, bit couldn't get it to build...
thanks if anyone can help me five my way
Click to expand...
Click to collapse
See the Aries kernel tree on my github. Its a slightly modified version of the cyanogenmod tree, and includes a build script and initramfs so syncing the entire source tree isn't necessary to build from it.
jt1134 said:
See the Aries kernel tree on my github. Its a slightly modified version of the cyanogenmod tree, and includes a build script and initramfs so syncing the entire source tree isn't necessary to build from it.
Click to expand...
Click to collapse
thanks. i was honestly waiting for you to come in here and tell me it won't work without syncing it all, lol. I'll check it out though. thanks again! you effin' rock!
ztotherad said:
thanks. i was honestly waiting for you to come in here and tell me it won't work without syncing it all, lol. I'll check it out though. thanks again! you effin' rock!
Click to expand...
Click to collapse
NP. Iirc, I originally added the scripts after you asked me about it a few months back
All you should have to do is clone the repo, and then run the build.sh script that's included. It will download the right toolchain for you, build the initramfs archives and then compile the kernel.
I also set it up to create a flashable zip with the new kernel and modules, so the build script should handle all the essential steps automatically.
jt1134 said:
NP. Iirc, I originally added the scripts after you asked me about it a few months back
All you should have to do is clone the repo, and then run the build.sh script that's included. It will download the right toolchain for you, build the initramfs archives and then compile the kernel.
I also set it up to create a flashable zip with the new kernel and modules, so the build script should handle all the essential steps automatically.
Click to expand...
Click to collapse
haha yeah, cause a few months back you said i had to sync the whole source.
it sounds like you've been working your ass off. lol
but that's definitely awesome. it makes it easier on us all.
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 !
I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
SaiyanGoku said:
I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
adfurgerson said:
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
Click to expand...
Click to collapse
I'd suggest using the kernel you want since the beggining. Just Open up both files using winrar and delete boot.img from the GEE DU and replace it with the boot.img from the GEEB build that you like much.
Click to expand...
Click to collapse
so, does replacing the boot.img will do the job?
SaiyanGoku said:
so, does replacing the boot.img will do the job?
Click to expand...
Click to collapse
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
adfurgerson said:
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
Click to expand...
Click to collapse
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
jimbo77 said:
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
Click to expand...
Click to collapse
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
As stated earlier in the thread, No.
If you want to have HDR photos, you need to use a rom that's built on Mako/GEEB sources (like Vanir or PA or Carbon or Beanstalk or DU or 90% of the other roms on this forum.
CAF-based roms, including CM and Mokee use a completely different set of source code, so No, You Can Not add HDR to CM11 kernel.
If you want to learn about device development, sure, it might be possible. But just trying to Winzip Wizard everything into place is not going to accomplish Anything that you want it to.
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
jimbo77 said:
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
Click to expand...
Click to collapse
i learned C and C++ when i was in school. and about kernel coding, nothing yet.
i think i'm better using CM11 directly if ever wanted to switch from PA instead of nuking my phone experimenting on non-compatible kernels.
(i don't use HDR that often as post processing takes time and there isn't that much of a difference in image quality)
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 there im trying to compiling aosp
now as you know aosp doesnt compile kernel at the same time,, so i added the automated kernel building from cyanogenmod but on when starting the build it comes up with this
Makefile:121: *** output directory "out/target/product/****/obj/KERNEL_OBJ" does not exist. Stop.
winxuser said:
hi there im trying to compiling aosp
now as you know aosp doesnt compile kernel at the same time,, so i added the automated kernel building from cyanogenmod but on when starting the build it comes up with this
Makefile:121: *** output directory "out/target/product/****/obj/KERNEL_OBJ" does not exist. Stop.
Click to expand...
Click to collapse
Manually create out/target/product/****/obj/KERNEL_OBJ folder.
Just leave it empty. Then recompile. I tried it and it works.
henry0504 said:
Manually create out/target/product/****/obj/KERNEL_OBJ folder.
Just leave it empty. Then recompile. I tried it and it works.
Click to expand...
Click to collapse
It creates the folder but it cant cd into it to add the sources
Sent from my LG-D855 using XDA Free mobile app
You can put the prebuilt kernel under obj/KERNEL_OBJ/arch/arm/boot/zImage. Then recompile
henry0504 said:
You can put the prebuilt kernel under obj/KERNEL_OBJ/arch/arm/boot/zImage. Then recompile
Click to expand...
Click to collapse
Yeah but i dont want to use a prebuilt. I want it to comlile at the same time as the rom... Added the inline kernel building file but it doesnt work for some reason
Sent from my LG-D855 using XDA Free mobile app