Hello everybody,
I have finally completed version 1 of my device tree for our device.
You can find it at
https://github.com/alterbang/android_device_xiaomi_libra
If you have a working CM local source you can lunch && mka otapackage for the glory
A few details:
I forked from xiaomi-dev, xiaobai's testing repo
Copied include folder from https://github.com/CyanogenMod/android_device_xiaomi_cancro
Edited AndroidBoard.mk with an "#alterbang" section with dir creation and patched files copy
Edited BoardConfig.mk with TARGET_SPECIFIC_HEADER_PATH := $(LOCAL_PATH)/include
Added "#alterbang" section with missing files to proprietary-files.txt, and removed a couple files.
BONUS: i have added a script "extract-files-from-miui-zip" to extract files from a miui.zip file (like the roms over at xiaomi.eu) so you can extract them without having to flash miui to your phone
ANY COMMENT OR COLLABORATION IS WELCOME
It's the first time i work actively with CM, so have mercy on me
I created this project because i believe in collaboration and openness, so get your hands dirty!
Thank you!
alterbang
Build 20160129 DOWNLOAD LINK
https://mega.nz/#!wBVlUJ4D!E-TDy01wNqBuLQvbznNfOd6bfkpPvaAcSePWZdlDXbY
-works: everything
-bugs: wakeup is sometimes slow. if you know how to fix, please tell me
Wow, awesome work!!
I'm not a dev, but I build CM 12.1 for klimtlte and CM 13 for mako (before I got my shiny new Mi 4c ...).
Double thumbs-up for your work on the extract-files-from-miui-zip.sh. Have you thought about uploading the files to TheMuppets github? Would make it even easier to build, and aries and cancro are already there.
Also I like that you shared your findings and how you got it to work and what you used to get it to work, much appreciated!! This is the way to do it in my opinion!
I very much like the idea of running my own build on my phone, however I am not sure if I should put too much effort into 12.1 any more with all the nice CM13 roms getting better and better (Team Superluminals cm13 builds work great on my phone) ... I will keep an eye on your github, though, and might ask your for your local manifest in the future
Again, you did great work so far!
Oh, one mroe thing: Whats the state of SELinux with your build? Is it permissive? Or did you or xiobai have an enforcing SELinux working?
Thank you muff99!
As for your question: i saw SELinux permissive removed in the mk files, but i don't know if that's enough. I'll let you know!
For Marshmallow / CM13: the idea is to do the same thing also for that branch
Hey !
Somebody could explain me what are the differences of this version between the Xiaobi one ?
Ty
DFurax said:
Hey !
Somebody could explain me what are the differences of this version between the Xiaobi one ?
Ty
Click to expand...
Click to collapse
You can compile this to yourself, you can take part of the development with this tree.
Sent from my Mi-4c using Tapatalk
Here are non open source binaries :
https://github.com/AndropaX/proprietary_vendor_xiaomi_libra
Pull requests with updates (from dev version please) are welcome.
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Hi,
I'm new in building ROM, so i'm trying to build rom but it seems local_manifest.xml needed ?! Where i can found it?!
Thx in advance
I am trying to put together a cm 13 build, this is how my local manifest looks so far:
Code:
<manifest>
<remote name="ghub" fetch="git://github.com/"/>
<!-- <project name="thune-xiaobai/android_device_xiaomi_libra.git" path="device/xiaomi/libra" remote="ghub" revision="cm-13.0"/>-->
<project name="xiaomi-dev/android_device_xiaomi_libra.git" path="device/xiaomi/libra" remote="ghub" revision="cm-13.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="ghub" revision="cm-13.0"/>
<project name="AndropaX/proprietary_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="ghub" reviSion="master"/>
...
</manifest>
It seems like Xiaobai is not using his thune-xiaobai Github any more, but he is contributing to xiaomi-dev, so I chose that device tree as did @alterbang.
@dexxa05:
Thnx! You sure the dev roms are a good source? After this locked-bootloader news I am hesitant to use dev rom files ...
Got until this one:
Code:
make: *** No rule to make target `/home/freddi/android/system/out/target/product/libra/obj/KERNEL_OBJ/usr', needed by `/home/freddi/android/system/out/target/product/libra/dt.img'. Stop.
Seems like @alterbang ran into this here:
http://forum.xda-developers.com/mi-...12-1-mi-4c-t3226541/post64204905#post64204905
Which dependencies did you add to fix this?
Oh btw, I dont wanna hijack your cm 12.1 thread to talk about cm 13 ... should I open another thread?
UPDATE: Oh I just saw all the stuff that you did to your device tree in /include, have to work through that ... cancro already has cm13, looks like there is even a kernel source.
that is just a missing dir, search my repo and yes please open a new thread! so we can start together on cm13
Hi Guys,
Small issues i'm trying to build 12.1 but the system try to build 13.0
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=6.0.1
CM_VERSION=13.0-20160119-UNOFFICIAL-libra
TARGET_PRODUCT=cm_libra
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-4-amd64-x86_64-with-debian-7.9
HOST_BUILD_TYPE=release
BUILD_ID=MMB29T
OUT_DIR=/home/dexxa05/android/system/out
============================================
Do you know how to change that?!
Thx in advance
dexxa05 said:
Hi Guys,
Small issues i'm trying to build 12.1 but the system try to build 13.0
Do you know how to change that?!
Thx in advance
Click to expand...
Click to collapse
How did you init your repo? You have to do it like this, I guess:
repo init -u https://github.com/CyanogenMod/android.git -b cm-12.1
Also, check the "revision" attribute in your .repo/local_manifests/*.xml files, it should be "revision="cm-12.1" " for you
AndropaX said:
Here are non open source binaries :
https://github.com/AndropaX/proprietary_vendor_xiaomi_libra
Pull requests with updates (from dev version please) are welcome.
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Click to expand...
Click to collapse
Is that from the latest MIUI?
From china dev rom 6.1.11
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Ok, now updated to 16.1.14
Great job AndropaX
Where you got kernel sources for mi4c?
Nowhere, i'm still using a prebuilt kernel...
We're still waiting for Xiaomi to comply to GPL.
And unfortunately nothing seems to indicate that's happening soon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sup
Updated the first post with the flashable zip
Is it possible to have the snapdragon camera on cm12.1?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Paranoid Android 3+
Device: JFLTEATT
WARNING
Flash at your own risk! I am NOT responsible for bricks!
Keep the forum on topic please, no trash talking, trolling, or talking of other ROMS.
INSTRUCTIONS
Wipe device
Wipe Cache & Dalvik
Install ROM
Install Paranoid GApps Package http://goo.im/devs/paranoidandroid/roms/gapps
Reboot
DOWNLOAD LINK
(BUILDING - coming soon)
chaosclarity said:
Building as I type this! Once it's done, I'll post it up. Then, mods can move this over to the dev section.
Click to expand...
Click to collapse
Looking forward to it.. I like some of the touchwiz features hence still being on a touchwiz ROM but I used PA3+ on my note 2 and would love to give it a shot on this
Sent from my WICKED AT&T S4 i337
Sync is taking a bit.. probably won't get build done until morning at this rate.
excited
chaosclarity said:
Sync is taking a bit.. probably won't get build done until morning at this rate.
Click to expand...
Click to collapse
hey brother i am excited to see it i am using cyanogenmod and i like it but i like the idea of the options you put in it .... would halo be available for this
Yeah is halo an option for this? I know the source isn't released but could you port it over from another phone that has halos already. Thanks
Sent from my SGH-1337 using Tapatalk 4 Beta
Sweet. Been waiting for this.
Hit a snag.. any devs care to chime in on this one?
Code:
Building ParanoidAndroid v3.56
Looking for device files
Device tree found. Skipping step.
Setting up environment
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/jfltetmo/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
Lunching device
build/core/product_config.mk:209: *** No matches for product "pa_jfltetmo". Stop.
Device jfltetmo not found. Attempting to retrieve device repository from CyanogenMod Github ().
Found repository: android_device_samsung_jfltetmo
CyanogenMod/android_device_samsung_jfltetmo already exists
Syncing repository to retrieve project.
fatal: Couldn't find remote ref refs/heads/jellybean
fatal: Couldn't find remote ref refs/heads/jellybean
error: Cannot fetch CyanogenMod/android_device_samsung_jfltetmo
error: Exited sync due to fetch errors
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:209: *** No matches for product "pa_jfltetmo". Stop.
** Don't have a product spec for: 'pa_jfltetmo'
** Do you have the right repo manifest?
Starting compilation
build/envsetup.sh: line 1666: schedtool: command not found
Total time elapsed: 1 minutes (102.701881915 seconds)
Try make clean/clobber and try building again see if it gives the same output
It seems there's no device tree for the galaxy s4 official?
jetlitheone said:
It seems there's no device tree for the galaxy s4 official?
Click to expand...
Click to collapse
I had to clobber something up.. but you're right it's a bit sketchy at the moment.
I used a few device tree sources I found from the i9505 section on this forum - all are hosted on CyanogenMod's Github from his Tmobile build. It *should* work.. but at the moment it's a bit of a mess.
chaosclarity said:
I had to clobber something up.. but you're right it's a bit sketchy at the moment.
I used a few device tree sources I found from the i9505 section on this forum - all are hosted on CyanogenMod's Github from his Tmobile build. It *should* work.. but at the moment it's a bit of a mess.
Click to expand...
Click to collapse
Looks like CM has jflteatt up.. will go at it again tonight.
Resyncing currently.. hope it builds later! :laugh:
chaosclarity said:
Resyncing currently.. hope it builds later! :laugh:
Click to expand...
Click to collapse
How long will that take?
Maybe I'll help out if you want.
Do you need a fast PC for this?
I'm getting tired:
Code:
Building ParanoidAndroid v3.50
Looking for device files
Device tree found. Skipping step.
Setting up environment
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/jflteatt/vendorsetup.sh
including device/samsung/jfltetmo/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
Lunching device
Looking for dependencies
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=pa_jflteatt
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-17-generic-x86_64-with-Ubuntu-12.10-quantal
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=/home/kaschenberg/android/system/out
============================================
Starting compilation
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=pa_jflteatt
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-17-generic-x86_64-with-Ubuntu-12.10-quantal
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=/home/kaschenberg/android/system/out
============================================
build/core/binary.mk:11: *** external/bzip2: LOCAL_NDK_VERSION is now retired.. Stop.
WTF!?
Found the issue probably - no build tonight guys.
Resyncing again...
Finally, it's building. Goodnight!
cant wait no rush
By the way guys, there's no halos that's not open source yet.
What's the verdict Chaos? Been itching all day to try this out after seeing it reviewed on the S3 =3
Sent via the Bacon Powered GS4
Hey.
AOKP stands for Android Open Kang Project. It is a custom ROM distribution for several high-end Android devices.
We fork the source code of Android that Google puts out in the open with every major version release, and we then add the magical unicorn bytes (we add some of the coolest features that are both useful and make your ROM awesome).
AOKP is lightweight. Most OEMs provide a heavy UI layer over Android and have loads of bloatware (i.e. apps that not everyone use every day, but you cannot remove because they’re “baked in” by default). Since AOKP is built upon vanilla Android source, it has neither of the above. With AOKP, you can generally do a lot more with your device than what you could do with the original firmware that came installed on it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What Works :
Everything which is not in Not working section!
Not Working :
-camcorder
-Bluetooth
-data network
-and please tell mee
Downloads
ROM
GAPPS
Credits
[email protected]<Engine/> for AOKP pico device
[email protected] for cm 10.2
Great work,we'll be much happier if we could have a bug free ROM
Sent from my GT-S7500 using XDA Premium 4 mobile app
TechKang said:
Did you compile from source?
Maybe I compile CM10.2, AOKP, PACMAN 4.3, etc all from source would be much better / more stable?
Click to expand...
Click to collapse
It's a port.
OT: Tech did you make a kitkat rom worked ?
compiling
hey guys wat does compiling from source means??????
TechKang said:
Did you compile from source?
Maybe I compile CM10.2, AOKP, PACMAN 4.3, etc all from source would be much better / more stable?
Click to expand...
Click to collapse
Yeah, you said you succesfully booted kitkat.? When is the release date?
I leave my phone for 1 hour and when i open i lost 30% battery, my wifi turns off and can't connect now.
this is kitkat 4.4.2
yazidkucrit said:
this is kitkat 4.4.2
Click to expand...
Click to collapse
it's cool!
yazidkucrit said:
this is kitkat 4.4.2
Click to expand...
Click to collapse
Gj! when can you relase it?
i managed to do something similar but as i have wooden pc when i sync repo it blocks and i have to continously break it
when you release the kitkat
I am so excited
kitkat 4.4.2
WAITING UNFINISHED JOB...
EROR COMPILE
yazidkucrit said:
kitkat 4.4.2
WAITING UNFINISHED JOB...
EROR COMPILE
Click to expand...
Click to collapse
i'll try tomorrow with a different pc maybe i have luck
why it gives you error?
i read that this kind of errors happen because the system can't write some temporary files, maybe free some space and restart the compilation?
p.d. you are using the same 3.0 kernel as we have right? or compiling a new one?
yazidkucrit said:
kitkat 4.4.2
waiting unfinished job...
Eror compile
Click to expand...
Click to collapse
any progress with this issue
ShadowsDie said:
i'll try tomorrow with a different pc maybe i have luck
why it gives you error?
i read that this kind of errors happen because the system can't write some temporary files, maybe free some space and restart the compilation?
p.d. you are using the same 3.0 kernel as we have right? or compiling a new one?
Click to expand...
Click to collapse
use kernel 3.0.xx
not teste
my first build from source and not teste because mya ace plus is sould
yazidkucrit said:
my first build from source and not teste because mya ace plus is sould
Click to expand...
Click to collapse
What kernel deconfig did you use?
Sent from my GT-S7500 using xda app-developers app
trebon_defconfig
yazidkucrit said:
trebon_defconfig
Click to expand...
Click to collapse
i have one more question did you got this:
make: *** No rule to make target `/home/josip/cyanogenmod11/out/target/product/trebon/obj/KERNEL_OBJ/usr', needed by `/home/josip/cyanogenmod11/out/target/product/trebon/obj/STATIC_LIBRARIES/libminui_intermediates/events.o'. Stop.
make: *** Waiting for unfinished jobs.
do you know what it could be??
becausei wanted to compile a rom for educational reasons and to help galaxy ace plus forum
yazidkucrit said:
trebon_defconfig
Click to expand...
Click to collapse
from kernel 3.4.6.7?
Any progress?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Application for Github Tutorial
Introduction:
Hi,
This is an application developed for helping people with github who are especially new to it.
Features:
1.Basic section where all the basics of github is presented.
2.Intermediate section.
3.Advance section.
4.You can take test in the "Judge your learning section"
Note:
If you have any suggestions/queries then you can send me a mail ( [email protected] ).
And Press the back button to go to navigation menu after you open the app.
Download link:
Github tutorial with Ads
Github tutorial without Ads
Source
Credits:
@major190 for helping me with some app issues and motivation. good person
XDA:DevDB Information
Github Tutorial, App for all devices (see above for details)
Contributors
Vivek_Neel
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2014-12-16
Created 2014-12-16
Last Updated 2015-01-01
Awesome Brother
Love Your Work
And my bro just started with git
Awesome work bro!
Thanks
Awesome!
Sent from my BlakKat CM11 powered OnePlus One "BACON"
This is just what I needed.
And another of great work
Good job! It looks really good :good:
Finally. Simply awesome
Can any body upload the app to Attachments please
Thanks for the app
Upload kernel, vendor and device tree.
Nice im going to try this app. I normall see guide that tell the basic stuff. Those guides and in how easy it is to upload the device tree files to master on github. And they tell how to add ore remove some files I get that.!
I have a device tree in master that is cm9. I want to upload a nother device tree to cm 10.2 and 11 using the terminal.
Here is my github: https://github.com/Frank77GLD/android_device_YG_m805_892x
For now i used a option in github to copy the cm9 project files to the cm10.2 github tree. I did have to change most files in cm10.2
My cm11 device tree is still empty. What should be the right way to upload my cm11 project files to the cm11 device tree?
This year i made a github with kernel files. 1 with vendor files and a device tree. I did have the problem that files got uploaded in the wrong device tree. Vendor files went in the kernel tree and the kernel files wint in like the devie tree. How to logon to the right device tree ore log out ore use the right command in my terminal? Im a bit scared when i upload files that they will go in the wrong device tree. I hope you're app can help out.
Can any one please attach the app because i can't download it From play stre
Thanks for this! Just in time for my in-laws' Christmas party. Something to read and learn while everyone else has fun. This is something that I have looking for.
Just to let you know you guys. This app has been featured on xda headlines.
http://www.xda-developers.com/android/github-tutorial-app/
Thank you xda
[email protected] said:
Nice im going to try this app. I normall see guide that tell the basic stuff. Those guides and in how easy it is to upload the device tree files to master on github. And they tell how to add ore remove some files I get that.!
I have a device tree in master that is cm9. I want to upload a nother device tree to cm 10.2 and 11 using the terminal.
Here is my github: https://github.com/Frank77GLD/android_device_YG_m805_892x
For now i used a option in github to copy the cm9 project files to the cm10.2 github tree. I did have to change most files in cm10.2
My cm11 device tree is still empty. What should be the right way to upload my cm11 project files to the cm11 device tree?
This year i made a github with kernel files. 1 with vendor files and a device tree. I did have the problem that files got uploaded in the wrong device tree. Vendor files went in the kernel tree and the kernel files wint in like the devie tree. How to logon to the right device tree ore log out ore use the right command in my terminal? Im a bit scared when i upload files that they will go in the wrong device tree. I hope you're app can help out.
Click to expand...
Click to collapse
I will have a look on this
Awesome it can help so much
awesome!!
Thanks muchly for this bro you're simply awesome!
Great Contribution
Awesome work @Vivek_Neel
Keep up the Good work Mate :angel:
Very cool.
https://plus.google.com/+ParanoidAndroidCorner/posts/RbrCXacYqES
TL;DR ?? Here is the interesting part
We are also announcing that with the help of Sony and their Open Devices Project we will be able to support all 22 Xperia devices on the SonyXperiaDev GitHub Instance. This initial Sony release is for the Shinano family, but the Rhine, Yukon and Kitakami platforms are expected to follow shortly. This is really exciting news for us and it allows us to give you the Android experience we all love on a much wider range of devices.
Click to expand...
Click to collapse
Konstantinosj77 said:
https://plus.google.com/+ParanoidAndroidCorner/posts/RbrCXacYqES
TL;DR ?? Here is the interesting part
Click to expand...
Click to collapse
ok but where is their github tree...when searching, i cannot find anything on github for AOSPA nor Paranoid Android, only AOSParadox, which i guess is not the same
quake73 said:
ok but where is their github tree...when searching, i cannot find anything on github for AOSPA nor Paranoid Android, only AOSParadox, which i guess is not the same
Click to expand...
Click to collapse
Sources are not up yet,only the OP devices kernels and trees https://github.com/AOSPA
Also their manifest is broken,already tried
Konstantinosj77 said:
Sources are not up yet,olnly the OP devices kernels and trees https://github.com/AOSPA
Also their manifest is broken,already tried
Click to expand...
Click to collapse
i admit, this is a little off the subject but...any idea of how to build a caf rom? or any idea of how to make sense of the caf tree names? I tried to compile some 'frankenstein' roms, combinations of caf+aosp but without success...i mentioned aosparadox, there is some guy, TheQuiche that supposedly 'maintains' the device tree for eagle for aosparadox but he only appears once in every 2-3 months. Have you seen/tried to build? I have tried but failed miserably every time Is there any point in trying anything with caf? I've read that it is the purest source/kernel for qcom devices
and this for example: https://github.com/AOSP-CAF? any idea if it is worth trying? (i already tried but failed )
quake73 said:
i admit, this is a little off the subject but...any idea of how to build a caf rom? or any idea of how to make sense of the caf tree names? I tried to compile some 'frankenstein' roms, combinations of caf+aosp but without success...i mentioned aosparadox, there is some guy, TheQuiche that supposedly 'maintains' the device tree for eagle for aosparadox but he only appears once in every 2-3 months. Have you seen/tried to build? I have tried but failed miserably every time Is there any point in trying anything with caf? I've read that it is the purest source/kernel for qcom devices
and this for example: https://github.com/AOSP-CAF? any idea if it is worth trying? (i already tried but failed )
Click to expand...
Click to collapse
I just checked his sources...there is no point in trying,he uses the same sony sources as everybody. (1.2.2 kernel branch)
Konstantinosj77 said:
I just checked his sources...there is no point in trying,he uses the same sony sources as everybody. (1.2.2 kernel branch)
Click to expand...
Click to collapse
yeah, i actually managed to build but got only a blank screen on my phone....and yes, i noticed his kernel, from sonyxperiadev. Tried to blindly guess and used some of the caf kernels, some went well but, black screen again.
quake73 said:
yeah, i actually managed to build but got only a blank screen on my phone....and yes, i noticed his kernel, from sonyxperiadev. Tried to blindly guess and used some of the caf kernels, some went well but, black screen again.
Click to expand...
Click to collapse
Let's wait for AOSPA
Maybe is the begingin of the stable roms on the xperia m2!
Enviado desde mi Xperia M2 Aqua usando Tapatalk
Sources are up!
https://github.com/AOSPA for builders sync the marshmallow branch. Still needs some edits thought....
Working/not working: Same as every other MM rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Konstantinosj77 said:
https://github.com/AOSPA for builders sync the marshmallow branch. Still needs some edits thought....
Working/not working: Same as every other MM rom
Click to expand...
Click to collapse
I admit the defeat this time, you got me this time, I was trying to build this one, too.
quake73 said:
I admit the defeat this time, you got me this time, I was trying to build this one, too.
Click to expand...
Click to collapse
Hahaha well i won't upload the build cause it's a bit hacky...let's wait for the official one
Konstantinosj77 said:
https://github.com/AOSPA for builders sync the marshmallow branch. Still needs some edits thought....
Working/not working: Same as every other MM rom
Click to expand...
Click to collapse
Srsly I prefer a fully working Lollipop build than an unstable Marshmallow...
I will try to build and test this rom when i get home
I hope they could make something stable
Enviado desde mi Xperia M2 Aqua usando Tapatalk
quake73 said:
I admit the defeat this time, you got me this time, I was trying to build this one, too.
Click to expand...
Click to collapse
Can you upload that when your build is over ?
vinz156 said:
Can you upload that when your build is over ?
Click to expand...
Click to collapse
sure, you can find it here (pa_eagle-6.0.1-20160627.zip) but wait first, it is uploading now, should be there in less than an hour (my upload is slow).
https://1drv.ms/f/s!AgjGxeMsjY4Ky3eAIsZX5og3_rkf
quake73 said:
i admit, this is a little off the subject but...any idea of how to build a caf rom? or any idea of how to make sense of the caf tree names? I tried to compile some 'frankenstein' roms, combinations of caf+aosp but without success...i mentioned aosparadox, there is some guy, TheQuiche that supposedly 'maintains' the device tree for eagle for aosparadox but he only appears once in every 2-3 months. Have you seen/tried to build? I have tried but failed miserably every time Is there any point in trying anything with caf? I've read that it is the purest source/kernel for qcom devices
and this for example: https://github.com/AOSP-CAF? any idea if it is worth trying? (i already tried but failed )
Click to expand...
Click to collapse
Hi there!
We (the AOSParadox team) were indeed working on bringing CAF to eagle. A friend of mine owned the device and i found the stock ROM really bad and the available ROM options at the time (i don't know how it is today.) were lacking aswell so for a while we were working on it but then my friend dropped his device and it broke, thus we didn't work on it anymore.
PS: I'm TheQuiche
Hello everyone
user @santeri3700 built oc kernel for our samsung galaxy core plus
but I wanted him even more tweak cpu ... and it worked!
Present *DANiO* Kernel; which is overclocked to 1.7GHz!
Advantages:
Overclocked to 1.77GHz,
It has drivers ntfs and exFAT
It uses anykernel2; now it's more elegant
bugs:
Not yet discovered
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.youtube.com/watch?v=BEpb3kOtn8U
Correction of graphics; changed the logo when starting kernel
Automatic builder is on my github
If you still want to test it here is a link.
Updated "updater-script" in zip file "Modules for DANiO Kernel.zip" faulting installation via twrp or cwm
DOWNLOAD UPDATE FOR THIS FILE
Wifi still dont work
Edit
Now works
QGM said:
Wifi still dont work
Edit
Now works
Click to expand...
Click to collapse
you're welcome
PS: Do u using my kernel in this time?
No because i back to stock rom
Wysłane z mojego SM-G350 przy użyciu Tapatalka
Danielisko said:
you're welcome
PS: Do u using my kernel in this time?
Click to expand...
Click to collapse
QGM said:
No because i back to stock rom
Wysłane z mojego SM-G350 przy użyciu Tapatalka
Click to expand...
Click to collapse
@Danielisko
If you rebase your changes on top of the current Salmiakki Super V2 source, it should most probably work on Stock 4.2.2 and CM/Lineage 13 :good:
EDIT: You need to use the prepared AnyKernel 2 flashable ZIP from the Salmiakki Super thread and put your kernel in it, else it won't be compatible with all ROMs (because if you do it by boot.img, it overwrites the Ramdisk). Also, remember to put the kernel modules you have built into the appropriate folder, else WiFi and some other stuff won't work.
EDIT2: I saw that you have a seperate ZIP for the modules. Still, AnyKernel 2 is easier to use and privides more functionality (and it preserves the ramdisk)
EDIT3: Salmiakki Super V2 source is here:
http://www.github.com/SiniTurk/android_kernel_samsung_cs02/tree/salmiakki
EDIT4: Also, make sure you publish the source of your kernel somewhere and link it, because you are technically violating the License right now
@TimSchumi thx .... btw: You requested me to use a anykernel2 from @osm0sis user... now I request you to test this my kernel.
Greetings
Later I will give the source of the kernel
Danielisko said:
@TimSchumi thx .... btw: You requested me to use a anykernel2 from @osm0sis user... now I request you to test this my kernel.
Greetings
Later I will give the source of the kernel
Click to expand...
Click to collapse
This kernel bootloops on Lineage 13 (how did you add that bootimage btw?), didn't test Lineage 11 yet
i did it fast.... maybe it's bad 'anykernel.sh' file?
Code:
# AnyKernel2 Ramdisk Mod Script
# osm0sis @ xda-developers
## AnyKernel setup
# begin properties
properties() {
kernel.string=*DANiO* OC Kernel
do.devicecheck=1
do.modules=1
do.cleanup=1
do.cleanuponabort=1
device.name1=cs02
}
# end properties
# shell variables
block=/dev/block/mmcblk0p5;
is_slot_device=0;
## AnyKernel methods (DO NOT CHANGE)
# import patching functions/variables - see for reference
. /tmp/anykernel/tools/ak2-core.sh;
## AnyKernel install
dump_boot;
write_boot;
## end install
And what is the difference between 'base', 'cm-11.0'+ (and up)?
I'm trying to compile 'base' for all cm-* (? - Need confirmation)
PS: As I remember it is probably 'cm-11.0' version of kernel.
Danielisko said:
i did it fast.... maybe it's bad 'anykernel.sh' file?
And what is the difference between 'base', 'cm-11.0'+ (and up)?
I'm trying to compile 'base' for all cm-* (? - Need confirmation)
PS: As I remember it is probably 'cm-11.0' version of kernel.
Click to expand...
Click to collapse
Did you base it of the 'normal' version of AnyKernel or did you take the AnyKernel zip from the Salmiakki Super thread? Because the latter should work fine if you only switch out the zImage and the modules.
The kernel source should be the same over all branches (except for salmiakki ofc, which ships OC and the nethunter kernel, which ships OC and a USB HID driver)
I recommend you to take the 'salmaikki' branch and reapply your changes on top of it.
ok you can test my repo for building kernel....
It has a build procedure that clones a github repository (it just is not a fork), then downloads the 'danio_oc_kernel-prepared.tar.bz2' file, unpack it and merges it into the previously downloaded repo and builds the kernel. Such a philosophy!
EDIT: You maybe try this, when i compile a while ago from 'salmiakki' branch . @berkantkz , @santeri3700 and @Logiel - Will you test it?
Danielisko said:
ok you can test my repo for building kernel....
It has a build procedure that clones a github repository (it just is not a fork), then downloads the 'danio_oc_kernel-prepared.tar.bz2' file, unpack it and merges it into the previously downloaded repo and builds the kernel. Such a philosophy!
EDIT: You maybe try this, when i compile a while ago from 'salmiakki' branch . @berkantkz , @santeri3700 and @Logiel - Will you test it?
Click to expand...
Click to collapse
I actually couldn't quite understand what did you mean to. I haven't been following the thread for long time so I don't know the affair
berkantkz said:
I actually couldn't quite understand what did you mean to. I haven't been following the thread for long time so I don't know the affair
Click to expand...
Click to collapse
simply download, flash it and test if it's working and wi-fi
Danielisko said:
simply download, flash it and test if it's working and wi-fi
Click to expand...
Click to collapse
Well, I don't own your devices man I just helped to Santeri and Tim
Danielisko said:
ok you can test my repo for building kernel....
It has a build procedure that clones a github repository (it just is not a fork), then downloads the 'danio_oc_kernel-prepared.tar.bz2' file, unpack it and merges it into the previously downloaded repo and builds the kernel. Such a philosophy!
EDIT: You maybe try this, when i compile a while ago from 'salmiakki' branch . @berkantkz , @santeri3700 and @Logiel - Will you test it?
Click to expand...
Click to collapse
I'm currently preparing everything for vacation, I'll test it when I have some free time (I need to flash Lineage 11 anyways to confirm a bug)
TimSchumi said:
I'm currently preparing everything for vacation, I'll test it when I have some free time (I need to flash Lineage 11 anyways to confirm a bug)
Click to expand...
Click to collapse
and how?
Danielisko said:
and how?
Click to expand...
Click to collapse
Still did not boot.
TimSchumi said:
Still did not boot.
Click to expand...
Click to collapse
sorry for my late
according in "ak2-core.sh" file uses only gzip...
i added some decompressor for initrd (such as: xzcat, bzcat, etc....).
---
You can test it again.
Danielisko said:
sorry for my late
according in "ak2-core.sh" file uses only gzip...
i added some decompressor for initrd (such as: xzcat, bzcat, etc....).
---
You can test it again.
Click to expand...
Click to collapse
This ZIP doesn't even flash.
Everything was ok about the ZIP itself, the kernel was unbootable.
i see :/
the kernel bumped to the latest version and maybe its need rebuilding? btw travis-ci is building the kernel
the new content with kernel source and flashable zip will be here
and the logging is here