Related
Hello there,while working on OMFGB and CM6,I decided to take ICS CAF sources and build them since andy is working at AOSP,arjen is working at CM9 and now I'm working at CAF. I opened this since I can handle various projects at a time,infact I'm developing for other stuff also.
Current status: Fixing build errors
All d best little genius..
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Good luck bro!
OT: Mind I ask u why u changed ur name?
Sent from my LG-P500 using xda premium
andy572 said:
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Click to expand...
Click to collapse
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
mentalityx said:
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
Click to expand...
Click to collapse
You're right. But now i've already created them,so for the next time.
Bytecode said:
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Click to expand...
Click to collapse
dont know, the hw specs are the same - at least the same cpu/gpu and memory.
maybe only another camera^^
Building now
sooo... any news here?
Bytecode said:
Building now
Click to expand...
Click to collapse
Ha ha little bytecode is going again
Enjoy your build procedure well be waiting
Sent from my LG-P500 using xda premium
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
edit the Android.mk and remove that lib, its proprietary **** only
SWEATTAIMI said:
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
_Arjen_ said:
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
Click to expand...
Click to collapse
I'm getting really,really confused here
Adding vendor and device folder from andy gives me libskia ****,adding all from andy gives me framework ****,I don't know what to do here
Lemme basically explain: What files are needed for building/booting CAF ICS succesfully? Don't post stuff necessary for fixing bugs later
Thank you
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Bytecode said:
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
Click to expand...
Click to collapse
AOSP is not CAF, AOSP is not CM - each framework has its own code, it
has nothing to do with my changes, as you can see in my patches, its nothing
to make it "feel me like a phoenix"
To help you a bit:
some makefile variables cant be used in CAF, CM or AOSP and vice versa,
you have to look in relevant config variables ad what its used for,
than look in the source code if the name has changed or the variable
cant be used (or what ever).
_Arjen_ said:
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Click to expand...
Click to collapse
qcom repos are very needed to compile qcom related changes like audio/media.
This script is for if you are compiling android from source and want to convert one tree to another name. For instance, we have been using a modified mako tree so if you wanted to start compiling for the Optimus G you would download the mako tree and modify it to our device. That would normally mean you need to replace all instances of the word mako with geeb or whatever you want to call it. and also rename some files as well. this script does it all for you.
just put it in the device tree directory and run it and it will prompt you for the rest.
it will ask you about the current device name and the new device name. the current device name should be the name of the device you are switching from and the new device name should be whatever you want to rename it to. both should be just one word like mako or skyrocket or geeb or geeb_att_us (underscores are OK).
Download -------> name-changer.py
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the script requires python to run (it works in python 2.5....not sure about python3)
just run (in the device tree directory):
Code:
./name-changer.py
please let me know if you have any suggestions or bugs. thanks
So if I'm reading this correctly, you would be able to have the sources for say paranoid android, then you put this in there and it would edit the sources to work for our phone?
Or am I way over thinking this?
Sent from my Nexus 4 using Tapatalk 2
MrZim4 said:
So if I'm reading this correctly, you would be able to have the sources for say paranoid android, then you put this in there and it would edit the sources to work for our phone?
Or am I way over thinking this?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This is for the device source.... Not android source. Its for converting one tree to another phone. I just made it because I tend to do this manually all the time so I just wanted to automate the process.
Sent from my LG-E970 using xda app-developers app
I've started started to create a library which makes using xposed more easy and includes features you normally have to develop on your own.
I hope that much people will contribute to make this library bigger.
current featues:
- use a settings app to configure your injections and notify them about changes instantly
- add/remove entries in Settings application
Sourcecode:
https://github.com/M1cha/android_library_libxposed
My eye are blinking and I'm crying right now...
Thanks sir and best wishes to you
omg good luck sir
m11kkaa said:
I've started started to create a library which makes using xposed more easy and includes features you normally have to develop on your own.
I hope that much people will contribute to make this library bigger.
current featues:
- use a settings app to configure your injections and notify them about changes instantly
- add/remove entries in Settings application
Sourcecode:
https://github.com/M1cha/android_library_libxposed
Click to expand...
Click to collapse
Great work dude ! Count me in for any contribution.
Just cloned and ran through.... This is fantastical and awesome work! Thank you very much!
Sent from my SGH-I337 using Tapatalk
I just saw that XPosed provides a XSharedPreferences class which directly opens the prefs of another apps. I think that this is better than my solution. But still be can extend this lib with much more features.
m11kkaa said:
I just saw that XPosed provides a XSharedPreferences class which directly opens the prefs of another apps. I think that this is better than my solution. But still be can extend this lib with much more features.
Click to expand...
Click to collapse
I have been using the XSharedPrefs in a module I am doing, but I can't make it work Live, after changes I have to reboot.
I saw that some github xposed modules use the sendBroadcast to update the prefs on the fly, but I can't make it work.
mcbyte_it said:
I have been using the XSharedPrefs in a module I am doing, but I can't make it work Live, after changes I have to reboot.
I saw that some github xposed modules use the sendBroadcast to update the prefs on the fly, but I can't make it work.
Click to expand...
Click to collapse
Then my solution in this library isn't useless yeah
How to Install ?! :/
androidsupersu said:
How to Install ?! :/
Click to expand...
Click to collapse
Same as any other library:
- clone git repo
- import it to eclipse ("existing android project into workspace")
- add the project as dependency to your app
m11kkaa said:
Same as any other library:
- clone git repo
- import it to eclipse ("existing android project into workspace")
- add the project as dependency to your app
Click to expand...
Click to collapse
Can anyone do this for me ?! Im not a pro i'm not a realy developer:/ i can't do this :/
androidsupersu said:
Can anyone do this for me ?! Im not a pro i'm not a realy developer:/ i can't do this :/
Click to expand...
Click to collapse
If you're not a developer you are at the wrong place here.
This isn't any app you can install. It's a library for developers.
m11kkaa said:
If you're not a developer you are at the wrong place here.
This isn't any app you can install. It's a library for developers.
Click to expand...
Click to collapse
Where's the source? I see only a compiled java jar.
AdamOutler said:
Where's the source? I see only a compiled java jar.
Click to expand...
Click to collapse
What do you mean? the source is on github:
https://github.com/M1cha/android_library_libxposed
The "XposedBridgeApi.jar" is just the XposedApi, this library is based on top of this.
The source of this library itself is in the src folder
m11kkaa said:
What do you mean? the source is on github:
https://github.com/M1cha/android_library_libxposed
The "XposedBridgeApi.jar" is just the XposedApi, this library is based on top of this.
The source of this library itself is in the src folder
Click to expand...
Click to collapse
Oh, sorry.. Im not used to the mobile interface on github. I thought SRC was the title. I use desktop generally. Threw me off, sorry.
AdamOutler said:
Oh, sorry.. Im not used to the mobile interface on github. I thought SRC was the title. I use desktop generally. Threw me off, sorry.
Click to expand...
Click to collapse
no problem. github mobile isn't that good
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,
Some of you all (who are reading this thread) might have seen me somewhere on subforums (either this subforum and/or other devices' subforum). I was previously maintained kernels for some devices (which I discontinued them later due to limited free time and I was no longer have them under my control).
Why I make this public?
I want to collect as many information as possible regarding building arm64 kernels (which I never do it before today), not limited to a developer, but as many as possible (if can)
I want to make my comeback on development by making an attempt to build a custom kernel for Redmi 3. So, I have these prepared:
Configured my netbook as building machine with LXLE.
Downloaded the required kernel source (I'm building for CM-14.1 based ROMs)
Grabbed UBERTC 4.9.4 aarch64
To make things easier without need to edit Makefile everytime I change toolchain, I created a script:
Code:
#!/bin/bash
# Placeholder - my system puts warnings everywhere about locale
export LC_ALL=en_US.UTF-8
# Environment variables
export ARCH=arm64
export CROSS_COMPILE=../../toolchains/aarch64-linux-android-4.9-kernel/bin/aarch64-linux-android-
# Actual command
make -s distclean
make -s cyanogenmod_ido_defconfig
make -s -j4
No problems during compilation process. All forbidden warnings triggered could be bypassed safely. Then, I tested my own build by creating a flashable zip. The process did flawlessly. However, it stucks forever on Mi logo.
Oh ya, I use -O3 optimizations on compilation.
Is there something I should do regarding the unbootable kernel?
I don't want to test every single toolchain out there due to my limited internet quota and my expectations on the same result.
Or... maybe suggestions?
Any help, suggestions, and comments are greatly appreciated. Thank you!
Regards.
Bump.
Seems like nothing noticed this thread. Should I mention every kernel developers here? I'm out of nowhere.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Bump.
Seems like nothing noticed this thread. Should I mention every kernel developers here? I'm out of nowhere.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Hey,
well, your way of doing it looks good. Do you get a last_kmsg probably? Also did you use the correct ramdisk, etc?
Excuse me sir, i want ask for help for my battery issue. Why my battery drop to 98% after unplug just a few second?_ I am on mokee and RR rom before and now i already flash it to MIUI but still got like that. Please help me if any solution for that ? sorry for my bad english
BlueFlame4 said:
Hey,
well, your way of doing it looks good. Do you get a last_kmsg probably? Also did you use the correct ramdisk, etc?
Click to expand...
Click to collapse
Nope. It stuck all way at Mi logo. No sign of life at all. Tested on official CM-14.1 and MoKee 7.1.1.
I use the modified AnyKernel2 template (removed Busybox requirement and points to Image.gz instead).
I also tried to download other kernel and use the zip as the base and the output is same.
Sent from my ASUS_Z00A using XDA Labs
ghal17 said:
Excuse me sir, i want ask for help for my battery issue. Why my battery drop to 98% after unplug just a few second?_ I am on mokee and RR rom before and now i already flash it to MIUI but still got like that. Please help me if any solution for that ? sorry for my bad english
Click to expand...
Click to collapse
Hi,
It's better to stay on topic.
You may create your own separate thread so people could assist you better and won't mix up with this one.
Regards.
Sent from my ASUS_Z00A using XDA Labs
So you get a last_kmsg?
Problem solved.
The culprit is the missing DTB!
When I look into the source once again, there's something missing: DTB file.
The file doesn't exist on arch/arm64/boot/dts, but instead on arch/arm/boot/dts. So, I created a link:
Code:
$ ln -s ../../../arm/boot/dts/msm8939-qrd-wt88509_64.dtb ./arch/arm64/boot/dts/msm8939-qrd-wt88509_64.dtb
Then I enabled CONFIG_BUILD_ARM64_APPENDED_DTB and re-compile kernel (using Google's GCC). Re-test it again (but with a boot.img extracted from MoKee zip unpacked with AIK and finally it booted!
Thank you very much, anyway.
Thread marked as Solved for now.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Problem solved.
The culprit is the missing DTB!
When I look into the source once again, there's something missing: DTB file.
The file doesn't exist on arch/arm64/boot/dts, but instead on arch/arm/boot/dts. So, I created a link:
Code:
$ ln -s ../../../arm/boot/dts/msm8939-qrd-wt88509_64.dtb ./arch/arm64/boot/dts/msm8939-qrd-wt88509_64.dtb
Then I enabled CONFIG_BUILD_ARM64_APPENDED_DTB and re-compile kernel (using Google's GCC). Re-test it again (but with a boot.img extracted from MoKee zip unpacked with AIK and finally it booted!
Thank you very much, anyway.
Thread marked as Solved for now.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Hey what did you change from original kernel? New features like hotplug? Is it easy to compile an booting kernel?
Sent from my Redmi 3 using XDA-Developers mobile app
rikusuicide said:
Hey what did you change from original kernel? New features like hotplug? Is it easy to compile an booting kernel?
Click to expand...
Click to collapse
For now, kernel patching.
Unless you have ever compiled one.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
For now, kernel patching.
Unless you have ever compiled one.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Will you release an costume kernel? CM 13, CM 14.1 or miui 8? Ya need testers?
Sent from my Redmi 3 using XDA-Developers mobile app
rikusuicide said:
Will you release an costume kernel? CM 13, CM 14.1 or miui 8? Ya need testers?
Click to expand...
Click to collapse
Maybe next year, as things go unpredictable.
EDIT: MIUI won't be supported due to lack of resources required.
I'll ask moderators to close this thread to prevent other type of nonsense discussions.
Sent from my ASUS_Z00A using XDA Labs
Thread closed at OPs request