Related
when I do: "make otapackage" i have this error after some minutes
make: *** Nessuna regola per generare l'obiettivo "vendor/lge/thunderg/proprietary/lib/libril.so", necessario per "out/target/product/thunderg/system/lib/libril.so". Arresto.
Click to expand...
Click to collapse
How I can resolve it?
I've read Noejn HowTo.
you have to copy the libril.so to your target - the lib gets linked with some other libs so the lib is needed on this place before other libs can be compiled.
I've copied libril.so in out/target/product/thunderg/system/lib... Now i try again with "make otapackage"
For future, kindly set LC_MESSAGES=C in your environment for compiling. Getting compile error output in random languages is rather annoying if you need help.
dr.notor said:
For future, kindly set LC_MESSAGES=C in your environment for compiling. Getting compile error output in random languages is rather annoying if you need help.
Click to expand...
Click to collapse
/offtopic/
you back again doktornotor?
Sent from my LG-P500
Thank you! I've compiled fine CM7 and it works! But... How I can compile "Launcher2" from CM/Android sources?
EDIT: mmm package/apps/Launcher2
0x0v3rfl0w said:
Thank you! I've compiled fine CM7 and it works! But... How I can compile "Launcher2" from CM/Android sources?
EDIT: mmm package/apps/Launcher2
Click to expand...
Click to collapse
so a new cm7 is coming from u?
mathew3184 said:
so a new cm7 is coming from u?
Click to expand...
Click to collapse
I don't know... Maybe I'll create it only for me... i don't know...
I would like to start building this rom (with kernel), because I did not like how it was stopped by Maclaw, but I need people to help me because I have a netbook and the construction of the rom could be very slow.
Any volunteers?
UP
i can help, did u downloaded the source?
Messi10 said:
i can help, did u downloaded the source?
Click to expand...
Click to collapse
Yes now I just have to fill the rom
Fedefriffo said:
Yes now I just have to fill the rom
Click to expand...
Click to collapse
if u have ant error in building post it here and i will try to help
Can I use Squadzone source for the kernel? I know that support the swap partition ...
Ok I finished the repo sync following this guide: http://source.android.com/source/downloading.html , now how do I build for arm-v6? (noob question)
Fedefriffo said:
Can I use Squadzone source for the kernel? I know that support the swap partition ...
Ok I finished the repo sync following this guide: http://source.android.com/source/downloading.html , now how do I build for arm-v6? (noob question)
Click to expand...
Click to collapse
see this guide
Messi10 said:
see this guide
Click to expand...
Click to collapse
Thanks, it was what I wanted
Ok so now I have a problem with the guide, I followed everything but when he says: replace CM9 folder tree with this, do you mean?
Fedefriffo said:
Ok so now I have a problem with the guide, I followed everything but when he says: replace CM9 folder tree with this, do you mean?
Click to expand...
Click to collapse
do this in terminal
cd android/system
git clone git://github.com/Squadzone/GalaxyMini_cm9_config
Click to expand...
Click to collapse
Messi10 said:
do this in terminal
Click to expand...
Click to collapse
Already done, but when I put the command. build / envsetup.sh && brunch tass says it can not find the device
Fedefriffo said:
Already done, but when I put the command. build / envsetup.sh && brunch tass says it can not find the device
Click to expand...
Click to collapse
try repo sync again
Messi10 said:
try repo sync again
Click to expand...
Click to collapse
Ok now I try to build, likely tomorrow afternoon news
One question, can I use the 3.0 kernel source taken by galaxy nexus?
Fedefriffo said:
Ok now I try to build, likely tomorrow afternoon news
One question, can I use the 3.0 kernel source galaxy taken by nexus?
Click to expand...
Click to collapse
i don't think so
there is no "brunch" in aosp;
do:
Code:
. build/envsetup.sh && lunch full_tass-userdebug
Code:
make -j[B]x[/B]
o r
Code:
make -j[B]x[/B] otapackage
where x is jobs, I have 4 cores and 4 threads so I use make -j8
TheWhisp said:
there is no "brunch" in aosp;
do:
Code:
. build/envsetup.sh && lunch full_tass-userdebug
Code:
make -j[B]x[/B]
o r
Code:
make -j[B]x[/B] otapackage
where x is jobs, I have 4 cores and 4 threads so I use make -j8
Click to expand...
Click to collapse
I have this error: federico @ Balamb-DOTS: ~ / $ AOSP_GALAXY_MINI. build / && envsetup.sh lunch full_tass-userdebug
Including device / asus / grouper / vendorsetup.sh
Including device/generic/armv7-a-neon/vendorsetup.sh
Including device/generic/armv7-a/vendorsetup.sh
Including device / bike / wingray / vendorsetup.sh
Including device/samsung/crespo4g/vendorsetup.sh
Including device / samsung / kinky / vendorsetup.sh
Including device / samsung / maguro / vendorsetup.sh
Including device / samsung / bull / vendorsetup.sh
Including device / you / panda / vendorsetup.sh
Including sdk / bash_completion / adb.bash
build / core / product_config.mk: 205: *** No product matches for "full_tass". Arrest.
Product ** Do not have a spec for: 'full_tass'
** Do you have the right repo manifest?
federico @ Balamb-DOTS: ~ / $ AOSP_GALAXY_MINI
you need file full_tass.mk in device/samsung/tass. Check github/MaclawStudios
TheWhisp said:
you need file full_tass.mk in device/samsung/tass. Check github/MaclawStudios
Click to expand...
Click to collapse
I've found full_gio.mk not full_tass.mk
Fedefriffo said:
I've found full_gio.mk not full_tass.mk
Click to expand...
Click to collapse
Just take this (attachment)
Thanks now i build...
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
sarkar1990 said:
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
Click to expand...
Click to collapse
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
nil1511 said:
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
Click to expand...
Click to collapse
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
Awesome. You can either upload them link me the git if its there
sarkar1990 said:
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
Click to expand...
Click to collapse
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
nil1511 said:
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
Click to expand...
Click to collapse
If you want to learn. It would be best to clone the Doomlord git and then read the files and scripts that are present there. This will give you the knowledge you may need to proceed further.
the git for our processor msm8960t is already present on github. Also download the kernel sources and drivers provided by Sony themselves from their developerworld page
sarkar1990 said:
the git for our processor msm8960t is already present on github.
Click to expand...
Click to collapse
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
eeehaw said:
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
Click to expand...
Click to collapse
Here is the link
https://github.com/DooMLoRD/android_kernel_sony_msm8960t.git
eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
sarkar1990 said:
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
Click to expand...
Click to collapse
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
eeehaw said:
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
Click to expand...
Click to collapse
Can you push your device file on github
nil1511 said:
Can you push your device file on github
Click to expand...
Click to collapse
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
eeehaw said:
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
Click to expand...
Click to collapse
Man, I keep running into the error! Ahh.. I think we need a better device tree.
sarkar1990 said:
Man, I keep running into the error! Ahh.. I think we need a better device tree.
Click to expand...
Click to collapse
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
CallMeVentus said:
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
eeehaw said:
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
Click to expand...
Click to collapse
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
CallMeVentus said:
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
eeehaw said:
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
Click to expand...
Click to collapse
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
CallMeVentus said:
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
No. I knew there were changes but I never knew what they were ? I asked a few people in a few threads but was not able to decipher.
Do you have any idea what sort of changes are required. ?
Before this is flagged as duplicate thread. Or a simple link to the source code of raymanfx source code. Or even the s6 edge plus port.
If I compile just using source code. It doesn't boot, I've tried all I have that I'm limited at.. some driver error Possibly narrowed it down to it being the defconfig.
Need the missing elf file and a working defconfig. (I am trying to fix some bugs until a more suited release is made..
Thank you
@RaymanFX @Ducter
And anyone else with knowledge
LiL_Assassin said:
Before this is flagged as duplicate thread. Or a simple link to the source code of raymanfx source code. Or even the s6 edge plus port.
If I compile just using source code. It doesn't boot, I've tried all I have that I'm limited at.. some driver error Possibly narrowed it down to it being the defconfig.
Need the missing elf file and a working defconfig. (I am trying to fix some bugs until a more suited release is made..
Thank you
@RaymanFX @Ducter
And anyone else with knowledge
Click to expand...
Click to collapse
Have you tried removing the 'OMX' folders from the system lib / lib64 folder? After you compiled the build.
Battlehero said:
Have you tried removing the 'OMX' folders from the system lib / lib64 folder? After you compiled the build.
Click to expand...
Click to collapse
Sorry man my apologies. I am trying the kernel side of things not the actual rom
LiL_Assassin said:
Sorry man my apologies. I am trying the kernel side of things not the actual rom
Click to expand...
Click to collapse
What device variant do you have?
Battlehero said:
What device variant do you have?
Click to expand...
Click to collapse
My friend has c and I have I
LiL_Assassin said:
My friend has c and I have I
Click to expand...
Click to collapse
Upload the build and I'll have a gander.
Battlehero said:
Upload the build and I'll have a gander.
Click to expand...
Click to collapse
I sent you a pm.
Battlehero said:
Upload the build and I'll have a gander.
Click to expand...
Click to collapse
Though if the pm or this doesn't suit you. Here's an upload for you man. We could be doing things wrong.. But we would love the insight. (We think this is the furthest we have managed)
https://www.dropbox.com/sh/oaenmo464fxoycz/AAD1uk-18MaNp0fQVyyjTvPAa?dl=0
Since OnePlus 8 got LineageOS, I figure it's time for us to do the same. But first we should do some kernel compilation.
I've compiled the kernel successfully but it is NOT booting, this is for people who know more than me for these newer chipset which they can get the kernel message.
Here's the official kernel source i forked: https://github.com/TipzTeam/android_kernel_xiaomi_sm8250
Here's a link to the compiles of the kernel:
https://androidfilehost.com/?w=files&flid=314140
Good luck!
who has tried ?? what are the differences from official kernel??
aleksgiab said:
who has tried ?? what are the differences from official kernel??
Click to expand...
Click to collapse
I tried, here's what I found:
1. Doesn't boot
Here's the differences:
1. Booting
2. Dts
3. Drivers?
it's still in the early stages so i won't experiment because i'll take it brick I'll wait to try other users to have a good time too
aleksgiab said:
it's still in the early stages so i won't experiment because i'll take it brick I'll wait to try other users to have a good time too
Click to expand...
Click to collapse
I tried on my own and doesn't boot but I don't know how to get kmsg
TipzTeam said:
I tried on my own and doesn't boot but I don't know how to get kmsg
Click to expand...
Click to collapse
then don't experiment ... so as not to spoil it
aleksgiab said:
then don't experiment ... so as not to spoil it
Click to expand...
Click to collapse
You don't understand. I am trying to get people who know more than me with these new chipsets which they can pull boot logs.
What VM or software are you using to compile kernel?
Link?
badaas said:
What VM or software are you using to compile kernel?
Link?
Click to expand...
Click to collapse
I use Ubuntu 18.04 on a real computer.
is it possible to make a gsi without compiling the kernel?
404
TipzTeam said:
I use Ubuntu 18.04 on a real computer.
Click to expand...
Click to collapse
I've just compiled the kernel for the LMI (POCO F2 Pro) and it's 13.3mb image.gz-dtb file.
I have the same issue it doesn't boot, complied without errors.
I first did the compressed image, it's 13.3mb, next I did the uncompressed image and it's 37mb