I would like to build ROM for one plus one from AOSP (android 5.1.1)
Look like i need below three information from the device manufacturer and override it in local_manifest.xml
1. Device Tree'
2. Vendor
3. Kernel.
I am able to get Device tree and Kernel. I am not able to find Vendor binaries for one plus one.
anybody can help me to get this?
Below is the local_manifest.xml i have. But it is missing vendor information.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="https://github.com/"/>
<project path="device/oneplusone/one" name="CyanogenMod/android_device_oneplus_bacon" remote="github" revision="cm-12.0" />
<project path="kernel/oneplusone/one" name="CyanogenMod/android_kernel_oneplus_msm8974" remote="github" revision="cm-12.0" />
</manifest>
forget about it, oneplus one needs deep software modifications from qualcomm (maybe you know 'caf').
OldDroid said:
forget about it, oneplus one needs deep software modifications from qualcomm (maybe you know 'caf').
Click to expand...
Click to collapse
I dream about AOSP
But there must be way to do it. For example, Euphoria is AOSP based with device tree/kernel from CM. Also, i saw this . AOSP, but CM source.
Related
Hi,
I was working since a while on this :
android_kernel_mt6589
For releases (beta builds - maybe unstable/not working), see here
I'm trying to support other devices too. Please send me your mt6589 device name and his kernel source (stock source !!)
Actual features :
Built commit history (patches cherry-pick from AOSP inside mtk kernel)
Mtk generate&build scripts moved into kernel directory
Merging meditatek sources (some devices will benefit from others kernel changes)
Removed a lot of unusued debug
Cortex A7 Optimizations + NeonV2 + FPV4
Built with sabermod (4.8.3) arm-eabi 4.8
Can be used into Omnirom build process (kernel and modules)
Future releases :
Support for multiple devices
Mtk commits for kernel source (with comments or docs)
Improve mediatek source ?
Suggestions welcomed
Supported devices :
Faea F2S
Requested devices :
Oppo R819 - WIP
Wiko (MT6589 devices) - need check for GPL compliance (OTA and updates on kernel source)
Lenovo P780 - need check for GPL compliance (OTA and updates on kernel source)
ZTE V967S - need check for GPL compliance (OTA and updates on kernel source)
Acer Liquid E2
Requested devices but no stock sources :
Xolo Q800 - need GPL compliance
Micromax A116 - need GPL compliance
Info about compatibility :
Kernel should be compatible with MT6589/MT6589M/MT6589T because the OC is hardware dependent (it gets the values of the board to detect which generation it is)
What I won't do :
Support overclocking for MT6589/MT6589M to act like MT6589/MT6589T
XDA:DevDB Information
[KERNEL-3.4.67] Source for MT6589 / MT6589M / MT6589T, a Kernel for the Android General
Contributors
Dr-Shadow
Kernel Special Features: Full source for kernel with commit history
Version Information
Status: Stable
Stable Release Date: 2014-03-04
Created 2014-03-04
Last Updated 2014-04-13
Reserved
So I implemented a way to build easyly the kernel
All you need is repo, git and dependencies as described here : https://github.com/Dr-Shadow/android_kernel_mt6589_manifest
So if you want to build latest kernel from my git :
For Faea F2S : ramdisk from stock ROM - almost stock kernel should be "stable"
Code:
repo init -u https://github.com/Dr-Shadow/android_kernel_mt6589_manifest.git -b master
cd kernel
./build.sh
For Oppo R819 : ramdisk from stock colorOS stable (V1.0.0i 140120) - BETA
Code:
repo init -u https://github.com/Dr-Shadow/android_kernel_mt6589_manifest.git -b r819-release
cd kernel
./build.sh
Next branch (released) :
For Faea F2S : ramdisk from stock ROM - BETA real 3.4.67 (should be stable)
Code:
repo init -u https://github.com/Dr-Shadow/android_kernel_mt6589_manifest.git -b devel-upstream
cd kernel
./build.sh
I improved the build.sh like this, you don't need to worry about vars and others.
Reserved
Any help is welcomed for this kernel tree.
What you can actually do :
Check if you can compile actually suported devices
Do pull requests to add devices or drivers
Check changes between your original stock source of your device
Adapt configuration files (Remove drivers not added or not working, add missing var)
Create a build script with a var for TARGET_PRODUCT which would be able to check env, build kernel and modules to out/ (my build.sh is a example for e960 - Faea F2S)
Actually, I'm merging Oppo R819 sources and I saw there was differences on mediatek drivers (some things were added by Oppo)
For example, I got this diff :
https://docs.google.com/document/d/1OGQS_HWRG9LbSiBCwWilKIQ-Wo_Asbz49IREXeZFJEA/edit
So for merging I'm replacing VENDOR_EDIT by OPPO_R819 so when kernel is compiling it should be able to keep Oppo changes only for Oppo R819 (thank you preprocessor for your hard work).
Of course, I'm not merging debug stuff.
The other idea would be to create documents, to document a specific change between another mtk source like those changes :
https://docs.google.com/document/d/15Bexb9ytPsYbvwo871u0mifmh9NqDJd6Oo1rXZiDiCg/edit
The focus of doc would be to show if the changes would be interesting for system part (better app for photos for example)
Example of new var introduced by recent mtk source (MAIN_SENSOR_ROTATE_DEGREE_X see config files) :
https://github.com/Dr-Shadow/androi...hal/camera/camera/cfg_setting_imgsensor.h#L52
Ok this is for hal but it's still interesting to check changes and this is actually my focus.
Awesome
You finnaly got the time to released it
:good:
Kernel source code Acer E2 Duo v370:
http://global-download.acer.com/GDF...E2&Step3=V370&OS=ALL&LC=fr&BC=ACER&SC=EMEA_13
Extracted kernel:
https://www.mediafire.com/?anywf4e9d1mb755
That's what you want?
I'm starting with the kernels ...
Matx13 said:
Kernel source code Acer E2 Duo v370:
http://global-download.acer.com/GDF...E2&Step3=V370&OS=ALL&LC=fr&BC=ACER&SC=EMEA_13
Extracted kernel:
https://www.mediafire.com/?anywf4e9d1mb755
That's what you want? :good:
Click to expand...
Click to collapse
Thank you for your sources
I will reconsider working on this device if Acer updates the kernel source (I got a discussion for it with Acer - need some time to find a solution).
There is a working kernel by @kashifmin, please check his gitrepo : http://d-h.st/zdN
Device : Micromax A116
this kernel have few bugs.
eagledipesh said:
There is a working kernel by @kashifmin, please check his gitrepo : http://d-h.st/zdN
Device : Micromax A116
this kernel have few bugs.
Click to expand...
Click to collapse
Yes but this is not a stock source.
Dr-Shadow said:
Yes but this is not a stock source.
Click to expand...
Click to collapse
Great work sir. Check your pm for stock source links
I see that you cherry picked many commits but still can you provide a Changelog (With Major changes from Stock MTK Kernel and Features )
This will help me atleast for development of kernel for other MTK Chipsets
Btw Great work i always like development and i also bought a MTK Phone based on MT6572
I suppose these are from the THL W8:
https://github.com/C3C0/MT6589_kernel_source
Adding the iOcean X7 woukd be nice, but I think sources aren't available..
GuneetAtwal said:
I see that you cherry picked many commits but still can you provide a Changelog (With Major changes from Stock MTK Kernel and Features )
This will help me atleast for development of kernel for other MTK Chipsets
Btw Great work i always like development and i also bought a MTK Phone based on MT6572
Click to expand...
Click to collapse
I think you didn't understand what I have written ^^
I cleaned kernel of debug and added the commits MTK injected in kernel so it's like stock mtk kernel with few changes and fixes (android binder for example).
Dr-Shadow said:
I think you didn't understand what I have written ^^
I cleaned kernel of debug and added the commits MTK injected in kernel so it's like stock mtk kernel with few changes and fixes (android binder for example).
Click to expand...
Click to collapse
gotcha sorry for incovience created by first Page moreover have you tried Dynamic Fysnc Control by Faux123 that is nice and any way to update source with the mainstream updating source ?
GuneetAtwal said:
gotcha sorry for incovience created by first Page moreover have you tried Dynamic Fysnc Control by Faux123 that is nice and any way to update source with the mainstream updating source ?
Click to expand...
Click to collapse
Yeah I should be able to update with mainstream updating source and it should be easier than mtk stock kernel as I fixed a lot of whitespaces, useless comments and others (around 400 or more files).
Actually I'm porting oppo R819, it will introduce some new features which could be interesting
Device : Micromax Chd A116
Kernel Source stock link : Updating...
Kernel Source Modified (kashifmin) : ADDED
Dr-Shadow said:
Yeah I should be able to update with mainstream updating source and it should be easier than mtk stock kernel as I fixed a lot of whitespaces, useless comments and others (around 400 or more files).
Actually I'm porting oppo R819, it will introduce some new features which could be interesting
Click to expand...
Click to collapse
Hmm Now i got it thats why the source was very smooth as earlier in Novem. i tried to compile Oppo kernel source and it compiled with no probs but your source is very smooth with some(actually many) warning but no Errors with the default drivers but when i introduced other phone's config and drivers it gave errors in aee :/ but will fix that
Thanks for Awesome Work will try and help by adding commits after my exams
Hey
Alcatel One Touch Hero (OT-8020D) / TCL Hero N3 (Y910)
This is supposedly the sauces.
SourceForge link (this will start the download automatically, sorry about that. Is a huge tar! :/
Update : Add support for GSLx680 touchpanel driver for Faea F2S
I have the Elephone P8, any support for this phone?
Sent from my P8 using xda app-developers app
bmw2k1 said:
I have the Elephone P8, any support for this phone?
Sent from my P8 using xda app-developers app
Click to expand...
Click to collapse
Hi
When requesting, do it with your phone stock kernel sources please
If you don't own kernel sources for your device, there's nothing he can do.
Regards
Hello ,
I am new to android. I have brazillian Lollipop on my moto g xt1033.
I am trying to build cm12 and going through the cynogenMod wiki but stuck in one of instruction :
"Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly."
So if I want to build CM12 for my device do I need to flash CM12 first??
If so , then can some please guide me , from where can I download CM12 image for xt1033.
ankrat said:
Hello ,
I am new to android. I have brazillian Lollipop on my moto g xt1033.
I am trying to build cm12 and going through the cynogenMod wiki but stuck in one of instruction :
"Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly."
So if I want to build CM12 for my device do I need to flash CM12 first??
If so , then can some please guide me , from where can I download CM12 image for xt1033.
Click to expand...
Click to collapse
U won't need that part since we already have vendor files
Just cd to ur lollipop source code directory
Then
Code:
. build/envsetup.ah
Breakfast falcon
To start ur build
Code:
Brunch falcon
bharat_goku said:
U won't need that part since we already have vendor files
Just cd to ur lollipop source code directory
Then
Code:
. build/envsetup.ah
Breakfast falcon
To start ur build
Code:
Brunch falcon
Click to expand...
Click to collapse
thanks for the info.
Getting below erro :
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/motorola/falcon/cm.mk]]: "vendor/motorola/msm8226-common/msm8226-common-vendor.mk" does not exist. Stop.
ankrat said:
Getting below erro :
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/motorola/falcon/cm.mk]]: "vendor/motorola/msm8226-common/msm8226-common-vendor.mk" does not exist. Stop.
Click to expand...
Click to collapse
u probably forgot this in roomservices.xml
Code:
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-12.0" />
it should look something like this but instead of anerikg type cyanogenmod
https://github.com/anerikg/local_manifests/blob/master/cm12.xml
sync breakfast and brunch
good luck
Code:
Code:
/*
* Your already voided warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
This is restricted to the same bootloaders that CM is. If you don't want to upgrade your bootloader then you can remove the check, however, I'm not responsible for anything that may go wrong (not that I am otherwise...)
Reboot to recovery
Wipe data and cache
Install zip
If desired, install gapps now. If you want root, install SuperSU - for 6.0, make sure its systemless (ie use 2.67+)
Things to Take Note Of
Bugs are likely present! If you find any, please let me know - also includes as much info as possible and any relevant logs (see http://forum.xda-developers.com/showthread.php?t=2185929 on how to take them.)
Does not work on msim devices (unless they've been converted to GPe). I have also had reports that there was no data on CDMA variants
This build is very close to the official OmniRom source code. This means that there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Backup Backup Backup! I'm not responsible for you losing any data.
Big thanks should go to the Omni team as its their source code which is easy to work with and to the CM team for their device trees which were used as a base
To see a list of current issues and their status, please have a look at my GitHub Issue Status page.
Working on latest build
Wi-Fi
Bluetooth
SMS
Data network
GPS
ANT+
Screen-off charging
MotoGParts
Dual-Sim (Caveat: cellular data is automatically switched to SIM 2 after being disconnected from wifi or after restarting the phone.)
Partially working
FMRadio - volume control is not working
What doesn't work
CDMA variants have no data
Selinux is currently in permissive mode
Everything else is not tested!!!
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_motorola_falcon for the device tree
http://github.com/xc-racer99/android_device_motorola_msm8226-common for the common device tree
http://github.com/xc-racer99/android_kernel_motorola_msm8226 for the kernel
http://github.com/xc-racer99/proprietary_vendor_motorola for the prop blobs
Downloads!
Download 6.0 builds from https://www.androidfilehost.com/?w=files&flid=50471
Download 5.1 builds from https://www.androidfilehost.com/?w=files&flid=39570
The first two builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Gapps
Any gapps for the desired Android version should work. If you want a link here, use OpenGapps
SuperSu
SuperSu can be found at http://forum.xda-developers.com/apps/supersu
Changelog for 6.0 Builds
Changelog for 2016/02/22
Initial soft release of 6.0
Known bugs - hotspot, some wifi bands, FM radio, ???
Changelog for 2016/03/11
Updated Omni source
Fixed FM radio
Fixed some issues with wifi bands and hotspot
Changelog for 2016/03/18 Build
Updated Omni source code
Treat all XT1033 variants as if they were single SIM - hopefully fixes SMS issues (you will still need to flash a single-SIM radio I believe)
Changelog for 2016/04/09
Call audio volume has been increased
Updated Omni source code - includes April 2, 2016 security patch level
Changelog for 2016/04/21
MSIM variants now work (this is thanks to the Omni team and I did no work on it)
If you have a GPe device (or just an ext4 userdata), the props are now set correctly
Changelog for 2016-05-09
Updated Omni source - includes May 1, 2016 security patch
Changelog for 2016/05/26
Snapdragon Camera added
ANT+ added to airplane mode list
Changelog for 2016-06-08
FM radio volume control works again
June security patch level
Changelog for 2016/06/15
Snapdragon Camera problem resolved
Changelog for 2016-07-15
Security patch level of July 5, 2016
Changelog for 2016-08-03
Security patch level of August 5, 2016
Changelog for 5.1 Builds
Changelog for 2015/09/09 Build
Initial public release
Changelog for 2015/09/10 Build
Fixed audio routing issues, including in-call audio
Dual-Sim now enabled for right model - unknown if works
Added ANT+ support
Added global action menu - aka Sound, Airplane Mode and Users added to Power menu
SElinux to enforcing mode
Changelog for 2015/09/19 Build
Powered-off charging animation now works
MotoGParts have been added
This is adds vibration intensity and color calibration
Changelog for 2015/10/01 Build
Updated Omni source
Changelog for 2015/10/15 Build
Updated Omni source
Probably fixed CDMA data
Build Your Own!
For 6.0
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment but use the android-6.0 branch. Before doing a repo sync, create a file in local_manifests and put the follow in it:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="android_device_motorola_falcon" path="device/motorola/falcon" remote="omnirom" revision="android-6.0" />
<remove-project name="android_device_motorola_falcon" path="device/motorola/falcon" remote="omnirom" revision="android-6.0" />
<project name="xc-racer99/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="android-6.0" />
<project name="ant-wireless/Android_build" path="external/ant-wireless/build" remote="github" revision="master" />
<project name="ant-wireless/Android_antradio-library" path="external/ant-wireless/antradio-library" remote="github" revision="master" />
<project name="ant-wireless/Linux_ant-hal" path="external/ant-wireless/ant-hal" remote="github" revision="master" />
<project name="ant-wireless/Android_ANTHALService" path="external/ant-wireless/ANTHALService" remote="github" revision="master" />
<project name="ant-wireless/Android_ANTRadioService" path="external/ant-wireless/ANTRadioService" remote="github" revision="master" />
<project name="ant-wireless/Android_ANTPlusPluginsService" path="external/ant-wireless/Android_ANTPlusPluginsService" remote="github" revision="master" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-13.0" />
<project name="xc-racer99/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="android-6.0" />
<project name="xc-racer99/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="android-6.0" />
<project name="android_hardware_qcom_display-caf-msm8974" path="hardware/qcom/display-caf-msm8974" remote="omnirom" revision="android-6.0" />
<project name="android_hardware_qcom_media-caf-msm8974" path="hardware/qcom/media-caf-msm8974" remote="omnirom" revision="android-6.0" />
<project name="android_hardware_qcom_audio-caf-msm8974" path="hardware/qcom/audio-caf-msm8974" remote="omnirom" revision="android-6.0" />
<project name="android_device_qcom_caf-sepolicy" path="device/qcom/sepolicy" remote="omnirom" revision="android-6.0" />
<project name="android_frameworks_av" path="frameworks/av-caf" remote="omnirom" revision="android-6.0-caf" />
<project name="android_frameworks_native" path="frameworks/native-caf" remote="omnirom" revision="android-6.0-caf" />
<project name="android_hardware_ril" path="hardware/ril-caf" remote="omnirom" revision="android-6.0-caf" />
<project name="xc-racer99/android_system_qcom" path="system/qcom" remote="github" revision="android-6.0" />
<project name="vendor_qcom_opensource_display-frameworks" path="vendor/qcom/opensource/display-frameworks" remote="omnirom" revision="android-6.0" />
<project name="xc-racer99/android_external_connectivity" path="external/connectivity" remote="github" revision="android-6.0" />
<project name="xc-racer99/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="android-6.0" />
</manifest>
Run ./device/motorola/falcon/patches/apply_patches.sh to apply the necessary patches to the source code. Then run "source ./build/envsetup.sh" followed by "brunch falcon".
For 5.1
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment but use the android-5.1 branch. Before doing a repo sync, create a file in local_manifests and put the follow in it:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xc-racer99/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="android-5.1" />
<project name="android_hardware_qcom_display-caf-bfam" path="hardware/qcom/display-caf-bfam" remote="omnirom" revision="android-5.1" />
<project name="android_hardware_qcom_media-caf-bfam" path="hardware/qcom/media-caf-bfam" remote="omnirom" revision="android-5.1" />
<project name="android_hardware_qcom_audio-caf-bfam" path="hardware/qcom/audio-caf-bfam" remote="omnirom" revision="android-5.1" />
<project name="android_frameworks_av" path="frameworks/av-caf" remote="omnirom" revision="android-5.1-caf" />
<project name="android_hardware_qcom_fm" path="hardware/qcom/fm" remote="omnirom" revision="android-5.1" />
<project name="xc-racer99/android_system_qcom" path="system/qcom" remote="github" revision="android-5.1" />
<project name="xc-racer99/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="android-5.1" />
<project name="xc-racer99/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="android-5.1" />
<project name="xc-racer99/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="android-5.1" />
<project name="ant-wireless/Android_build" path="external/ant-wireless/build" remote="github" revision="master" />
<project name="ant-wireless/Android_antradio-library" path="external/ant-wireless/antradio-library" remote="github" revision="master" />
<project name="ant-wireless/Linux_ant-hal" path="external/ant-wireless/ant-hal" remote="github" revision="master" />
<project name="ant-wireless/Android_ANTHALService" path="external/ant-wireless/ANTHALService" remote="github" revision="master" />
<project name="ant-wireless/Android_ANTRadioService" path="external/ant-wireless/ANTRadioService" remote="github" revision="master" />
<project name="ant-wireless/Android_ANTPlusPluginsService" path="external/ant-wireless/Android_ANTPlusPluginsService" remote="github" revision="master" />
</manifest>
Next, apply the patch located at https://gist.github.com/xc-racer99/d1d5cff162ee4fa0239d Then, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch falcon"
download link?
Oh,thanks.downloading...
ysop said:
download link?
Click to expand...
Click to collapse
You got here too fast. Its up now! Still finishing off creating the thread.
great rom
Great.... I will test dual sim..... Thanking for keeping people hopes alive
Sent from my Moto G using XDA Free mobile app
In the old thread I tested your rom but the sim card want recognize is it the same with this one or its it corrected?
Envoyé de mon XT1039 en utilisant Tapatalk
Mchasard said:
In the old thread I tested your rom but the sim card want recognize is it the same with this one or its it corrected?
Envoyé de mon XT1039 en utilisant Tapatalk
Click to expand...
Click to collapse
Well, you didn't test my ROM, you tested TheCrazySkull's.... Though we are working together on it.
That one did not recognize the SIM, this one does. There were a couple of patches that weren't integrated on the build he posted.
xc-racer99 said:
Well, you didn't test my ROM, you tested TheCrazySkull's.... Though we are working together on it.
That one did not recognize the SIM, this one does. There were a couple of patches that weren't integrated on the build he posted.
Click to expand...
Click to collapse
next time please put android file host as file server. Google drive download sucks...lolzzz
sachoosaini said:
next time please put android file host as file server. Google drive download sucks...lolzzz
Click to expand...
Click to collapse
I'll consider it. I've never used it before though. I'll create an account and see how it works.
Edit: Have requested developer status on android file host so I can upload things. We'll see if they approve me or not!
May someone test the calls? Ill try this but i need the calls working
DeHuMaNiZeD said:
May someone test the calls? Ill try this but i need the calls working
Click to expand...
Click to collapse
Multisim variants wont have call nor data nor anything sim related (aka ril) working.
Im working on a fix so maybe it will be working in a feature update.
DeHuMaNiZeD said:
May someone test the calls? Ill try this but i need the calls working
Click to expand...
Click to collapse
Ok, I just tried a call. I had no audio! I think there must be some issue with the audio routing (still!).
On a better note, data did work.
sachoosaini said:
Great.... I will test dual sim..... Thanking for keeping people hopes alive
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Don't bother testing multi-sim on this first build. I enabled multi-sim for the xt1032, not for the xt1033...:crying:
So, xt1032 people, your phone didn't just magically gain an extra sim card slot
Too bad, if the calls worked i'd probably use it as a daily driver. Ill wait
DeHuMaNiZeD said:
Too bad, if the calls worked i'd probably use it as a daily driver. Ill wait
Click to expand...
Click to collapse
Well, I just fixed call audio so that excuse is gone. I've got a new build ready to go but I haven't heard back from android file host yet. I'll probably upload it later today. It will also bring in ANT+ support and will hopefully have selinux in enforcing mode. FM radio is still a no-go so far (not that I've tried to get it to work yet).
xc-racer99 said:
Well, I just fixed call audio so that excuse is gone. I've got a new build ready to go but I haven't heard back from android file host yet. I'll probably upload it later today. It will also bring in ANT+ support and will hopefully have selinux in enforcing mode. FM radio is still a no-go so far (not that I've tried to get it to work yet).
Click to expand...
Click to collapse
You are working seriously hard brother..
Nice to see working with the dedication for omni for so long....
Sent from my Moto G using XDA Free mobile app
xc-racer99 said:
Well, I just fixed call audio so that excuse is gone. I've got a new build ready to go but I haven't heard back from android file host yet. I'll probably upload it later today. It will also bring in ANT+ support and will hopefully have selinux in enforcing mode. FM radio is still a no-go so far (not that I've tried to get it to work yet).
Click to expand...
Click to collapse
Well, now it's stable for me. Will wait for link. Thanks for bring us omnirom bro.
Btw.. What is the most important bug now that you fixed ril, bluetooth and call audio?
I love this ROM, thanks for sharing this great work!
I have decided to stick with MIUI to source code becomes available to developers.
While I admire custom ROM development so far: there seem to be a lot of bugs an limitations that developers are all saying are the result of not having source code.
Does anyone have a probable date on the release of source code for the Poco X3 an X3 NFC?
Source code may help with GSI an F2FS development for our device for instance?
I Have Oreo Based Stock Rom And Its Relevant Device Tree. I Want To Build Latest Version Of Aosp Or LineageOs Then Why Do I Need To Port My Current Device Tree To Newer Android Version. As Far As I Knows Device Tree Is A Hardware Description And Should Not Change With Android Version Because The Hardware Information Is Constant. The Kernel Tree And Vendor Tree Remains Same And Dont Change With Newer Android Version Then Why Device Tree Changes With Newer Android Version.
For Example, The Device Tree Based On Oreo Will Not Work With Android 12 We Need To Port It First.But The Kernel Tree And Vendor Tree Which Was Working In Oreo Will Continue To Work Further Without Any Modification.
Priyanshu jangid said:
I Have Oreo Based Stock Rom And Its Relevant Device Tree. I Want To Build Latest Version Of Aosp Or LineageOs Then Why Do I Need To Port My Current Device Tree To Newer Android Version. As Far As I Knows Device Tree Is A Hardware Description And Should Not Change With Android Version Because The Hardware Information Is Constant. The Kernel Tree And Vendor Tree Remains Same And Dont Change With Newer Android Version Then Why Device Tree Changes With Newer Android Version.
For Example, The Device Tree Based On Oreo Will Not Work With Android 12 We Need To Port It First.But The Kernel Tree And Vendor Tree Which Was Working In Oreo Will Continue To Work Further Without Any Modification.
Click to expand...
Click to collapse
Sometimes the partition structure is changed from one version to the next, this changes the tree in order to compile the ROM with the correct partitioning structure.