Related
First off, I just want to say I don't mean to step on anyone's toes. Thanks for all the work so far from digitalhigh, bracketslash, santod040 and everyone who has posted information about or commits to the CM12 build tree. This is not my code, all I have done is disable enough stuff to get it to build and boot. A LOT OF STUFF IS BROKEN. This is intended for developers only right now. I will try to update the builds as I can but please don't expect true nightly builds.
DISCLAIMER: I am in no way responsible for malfunctioning or bricked devices if you run this software. If you do not agree to these terms, DO NOT DOWNLOAD. Again, this is seriously broken right now.
What doesn't work:
-Almost everything
What works:
-Wifi
-Touchscreen
-Sound
Changelog:
Merged (compare to build date)
Open (not in build yet)
Installation notes:
As I have yet to find a way to easily disable NFC for the builds, you will have to remove the /system/app/Nfc to stop those force closes. I just went to TWRP, mounted system, then ran "rm -rf /system/app/Nfc" to disable NFC for now.
Downloads:
2014-11-17: Download (Android File Host)
Edit: Please see bracketslash's thread for future downloads: http://forum.xda-developers.com/ver...ment/cm12-unofficial-unstable-builds-t2941198
bring it on bro
This saved me some time. Guess I'll see what I can do.
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
That was fast!
krazie1 said:
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
Click to expand...
Click to collapse
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Ive been patiently waiting for cm12 on this beast
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
jake.99x3 said:
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
Click to expand...
Click to collapse
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
djh816 said:
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
Click to expand...
Click to collapse
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
jake.99x3 said:
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
Click to expand...
Click to collapse
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
xdadevelopers-user said:
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
Click to expand...
Click to collapse
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
djh816 said:
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
Click to expand...
Click to collapse
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
macs18max said:
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
Click to expand...
Click to collapse
I started with clean ubuntu 14.04 lts x64 and added the packages from bracketslash's thread here. Then I just installed openjdk-7-jdk and openjdk-7-jre after that.
djh816 said:
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
Click to expand...
Click to collapse
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
djh816 said:
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Click to expand...
Click to collapse
You don't need to do all of that.
There's one commit and everything works just fine.... nothing's broken.
http://review.cyanogenmod.org/#/c/76760
...and you may just want to thank invisiblek in your original post. He's the only one that did all of the work to bring up the device.
Gunman84 said:
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
Click to expand...
Click to collapse
calling @santod040 for some cm love for m8vzw
munchy_cool said:
calling @santod040 for some cm love for m8vzw
Click to expand...
Click to collapse
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
ajrty33 said:
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
Click to expand...
Click to collapse
Welcome to XDA ..
Lollipop Red M8
Do not post "Thank you" type responses.[SIZE=+3]ALL ROMS EVER (Intro to be added)[/SIZE]
[SIZE=+2][INDEX][/SIZE]
[SIZE=+2]Helpful Information[/SIZE][SIZE=+1]Welcome, this thread has been created to encompass everything you may need for your android device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, or create your own thread in the Q&A forum. Do not use this as a general help thread.
Since most ROMs are MM now I will split ROMs in this thread into 2 sections, MM and EOL.
This thread probably isn't going to help anyone. If it does help you, however, please tell me the usage in a post!
Please tell me if I made any mistakes in the categorization, and add on new ROMs as they come out/those which I forgotten to add.
Lastly, Stock-Based ROMs will not be added unless it is being ported to other devices eg. Xperia ROM ported to XOSP to other devices[/SIZE]Click on a Link below for More Info
MM ROMs
Toolchains
EOL ROMs
Kernels
Useful links any general index should have
http://forum.xda-developers.com/showpost.php?p=65849943&postcount=34
*Forum Rules | New Users Guide | XDA Tour | Report PostsPlease look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP
MM ROMs
*Mainly* CM-Based:
CyanogenMod
Temasek's CM
PAC ROM (And their cute but old website copyrighted 2014)
AICP
BeanStalk ROM
BlissPop ROM
AOKP
Resurrection Remix
XOSP
crDroid
CyanPop
OctOS
Marsh
MoKee
LiquidSmooth (+Slim base)
FlexOS (This is relatively obsolete as compared to Team Flex's AOSP-based Flayr OS)
OwnRom
TeslaOS (Not to be confused with Tesla by GZR)
*Mainly* AOSP/CAF-Based:
Dirty Unicorns (And CAF)
Pure Nexus
Cyanide L MM (Apparently it isn't Cyanide M) (Un-merged with Fusion from VrToxin)
OmniROM
Tesla by GZR
Slim
YAOSP
SlimYAOSP (Repo Init THIS first)
Nameless ROM
Broken ROM
Chroma ROM
MoKee
UberMallow (Previously OptiPop)
CandySix
FlayrOS
Exodus ROM (Quite confused as to which manifest to link to)
Validus by GZR
TipsyOS
OrionOS
Screw'D AOSP
AOSiP
ZephyrOS
BenzoRom
Beltz Rom (AOSP with DUI)
Cardinal AOSP
Citrus CAF
Evervolv
CopperHead OS
Toxic OS
All Purenexus and Slim mods from the guys at http://forum.xda-developers.com/slimroms/general/rom-builders-collective-t2861778
Toolchains
Guide for using below TC
UberTC (And Github) (For Pre-Built TC refer to BitBucket)
Linaro
SaberMod (Pre-Built TC at their website)
Hyper Toolchains
DragonTC
Christopher83's custom TC builds
Archi's Toolchains (Change the branches to change TC)
EOL stuff
VrToxin (Apparently some internal strife)
Fusion (Merged with Cyanide to VrToxin, then VrToxin died)
Archidroid/Archikernel (Should be getting a revive soon since Archi got an OP2)
Perseus Kernel (IDK why it died, too long ago)
Minimal OS (IDK why it died. Wanted to build this in particular because LP Minimal is awesome but suddenly github activity stopped)
Paranoid Android (RIP will miss you guys. They got "bought over" by OnePlus to dev OxygenOS)
F-AOSP (IDK why it died.)
Yank Kernel (I think he just gave up or something)
[*]80% of Dirty Unicorn (Went over to some Russian company) (Hi Mazda/Alex Cruz)
Euphoria OS
RadonX
Nexus Experience
Custom Kernels
AK Kernel
Lightning Kernel
Agni kernel
Arter97's Kernels
Boeffla Kernel
Franco Kernel
ElementalX
Phasma Kernel
Kylo Kernel (Same as above...???)
Some random modded kernels mostly in Nexus forums I didn't bother to add
RIP people.
A filler and awareness post.
See you in heaven. I know you are in a better place now.
TonyStark
FlashVetrin
Please add on. So far I only know of those two ^^
Garbage Link Collector
Another Link Collector (But not structured so Garbagely)
A ROM Building Guide for you to build ANY ROM on this list
XDA New User Guide
How to shake off "n00b" status
How to get Moderator's attention (Don't waste their time unnecessarily though )
Requests to Mods (All users welcome)
Logcat (MEOW)
Commonly used acronyms on XDA
How to become RC/RT
Signature Code Sharing
Archi's Optimisations (And for MM)
Index Project
Ask Away Project
Anti-Piracy/ContentGuard
NEED-TO-READ 1
NEED-TO-READ 2
Special thanks to:
@Trafalgar Square
@sd_shadow
@kuzibri
@zelendel
And everyone else at the Index Thread!!
Temporary to-do:
CarbonROM
others?
limjh16 said:
Last one
Click to expand...
Click to collapse
I would add descriptions and differences between rom types
https://en.wikipedia.org/wiki/List_of_custom_Android_firmware
http://android.wikia.com/wiki/Category:Custom_ROMs
http://lifehacker.com/5915093/five-best-android-roms
Sent from my KFFOWI using XDA Labs
limjh16;65315332
said:
CM
AOSP
Others
Kernels
Dead ROM/Kernels
Useful links any general index should have
[/INDENT][/INDENT]
*Forum Rules | New Users Guide | XDA Tour | Report PostsPlease look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP
Click to expand...
Click to collapse
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri
Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill
kuzibri said:
Hi,
sofar, so good. Would it be an idea to also add an item which devices are supported and which not? I would remove the item "Dead ROM/Kernels", they are of no use for your thread and may cause confusion.
kindest regards,kuzibri
Click to expand...
Click to collapse
That item is meant for stuff like AOKP where its dead, but for those who want kitkat then they can refer.
sd_shadow said:
Here is a big list of porting and compiling rom guides
[Guides][Updated] All Guides @ One Place By Hpsgill by Hpsgill
Click to expand...
Click to collapse
Will have a look and add to useful links section.
This thread is gonna take really long to get updated I am very busy with school haha...
limjh16 said:
This thread is gonna take really long to get updated I am very busy with school haha...
Click to expand...
Click to collapse
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri
kuzibri said:
Why did you choose to start such a thread, which is very time consuming, when you are so busy with school? If I were you, I would restrict your available time to make an index thread of your own devices (i9305 or SGS3-LTE). I can understand your wish of creating the thread that's in your mind, but you do need/have the time to create and maintain it, which is IMHO almost impossible when you are also at school. If you still want to create this ALL ROM EVER thread, ask help from other members to help you, cause you cannot do it on your own. Nevertheless, if you still want to continue with this ALL ROM Ever thread, I'm willing to help you where ever I can. :good:
kindest regards, kuzibri
Click to expand...
Click to collapse
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.
To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.
zelendel said:
To be honest most won't bother as not all roms are available for all devices.
Also don't put any fair in what someone else thinks of a rom. Their opinion almost never really matters.
Click to expand...
Click to collapse
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.
limjh16 said:
Hmm true... But I created mostly for me cuz I was just going around xda finding a ROM to build so I thought this thread would help.
Click to expand...
Click to collapse
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM
zelendel said:
No sure where it would help but ok. Going around building roms from other groups will not last long. More and more teams are closing their source and not letting others use it.
So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM
Click to expand...
Click to collapse
Well I just started learning how to build so idk how to start off my own ROM project... But I am interested...... Teach me please...?
limjh16 said:
I didn't expect my first term of school to be so hectic, I created this before my term started. It's alright, I'll just leave this here. Not like anyone except you and sd_shadow comes here... but I'll try to update once a week.
Click to expand...
Click to collapse
Hi,
it's no problem that it will take longer that you thought initially. I agree with @zelendel regarding this: "So if your worried about building then I would start my own project and start from scratch with it. Aosp not CM" Cyogen Mod is a world on it's own and accepted as a fully functional OS. Regarding the fact that only sd_shadow and I, besides zelendel now, only visit your thread, is logical because it's a WIP.
kindest regards, kuzibri
As probably most of you know, @temasek has "left the building". Since I'm currently support his ROM for some devices, I decided to "fork" all temasek repos on github and continue his work.
If anyone want to keep temasek ROMs updated, you can use my repositories to continue build updated ROMs.
Here is all you need -> https://github.com/FSadino/android
Feel free to use my repos, you don't need to ask any permission for that, just give proper credits on your threads.
Let's keep this developer "awake" on XDA
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is either 3.18.66 (OxygenOS) or 3.18.71 (LineageOS and most likely all other custom ROMs) and the current version upstream is 3.18.124 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op3
There are three branches: one for OxygenOS stable, one for OxygenOS beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
hmm this helps a lot bro. Thanks for opening this thread. So, here comes my first question - how can we make a kernal compatible with most of the Oreo roms which we have at present like nos, Z, Pixel, Aosip or omni or others as they all use different.
mady51 said:
hmm this helps a lot bro. Thanks for opening this thread. So, here comes my first question - how can we make a kernal compatible with most of the Oreo roms which we have at present like nos, Z, Pixel, Aosip or omni or others as they all use different.
Click to expand...
Click to collapse
Well that's not exactly a topic for this thread but it depends on what makes them different. Some things can co-exist, others can't. I know that's a generic response but I don't really have anything more descriptive I can give.
3.18.93 has been merged in.
3.18.94 has been merged in (conflict notes).
3.18.95 has been merged in.
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
v3.18.96
https://github.com/nvertigo/android_kernel_oneplus_msm8996/tree/linux-stable/merge-15.1
This is current lineageos/lineage-15.1 merged with https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tag/?h=v3.18.96.
3.18.96 has been merged in.
nathanchance said:
3.18.96 has been merged in.
Click to expand...
Click to collapse
Sir! it's a flashable kernel for 1+3T?
acultr said:
Sir! it's a flashable kernel for 1+3T?
Click to expand...
Click to collapse
Umm.. no. Might wanna read a bit more before asking. It's just the kernel sources.
acultr said:
Sir! it's a flashable kernel for 1+3T?
Click to expand...
Click to collapse
No, it's for peoples who want build upstreamed kernel, like sources to build.
3.18.97 has been merged in.
3.18.98 has been merged in.
My apologies to the custom ROM users for breaking MTP and adb many thanks to @martinusbe and @nvertigo67 for reporting the issue to me and helping me fix it! The change has been pushed, please pull to update!
https://github.com/android-linux-stable/op3/commit/180f737979e7f81b7e650fbff11dcc437d358142
nathanchance said:
My apologies to the custom ROM users for breaking MTP and adb many thanks to @martinusbe and @nvertigo67 for reporting the issue to me and helping me fix it! The change has been pushed, please pull to update!
https://github.com/android-linux-stable/op3/commit/180f737979e7f81b7e650fbff11dcc437d358142
Click to expand...
Click to collapse
No reason to apologies. Thanx to you and @martinusbe for fixing this. Without you I would still search in ffs commits...
nathanchance said:
My apologies to the custom ROM users for breaking MTP and adb many thanks to @martinusbe and @nvertigo67 for reporting the issue to me and helping me fix it! The change has been pushed, please pull to update!
https://github.com/android-linux-stable/op3/commit/180f737979e7f81b7e650fbff11dcc437d358142
Click to expand...
Click to collapse
Yay its fixed. I'm sure people against upstreaming will use this as an argument to say upstreaming is bad. I'm not a dev so I really have no idea what's right. In my book, higher version = good lol xD
knpk13 said:
Yay its fixed. I'm sure people against upstreaming will use this as an argument to say upstreaming is bad. I'm not a dev so I really have no idea what's right. In my book, higher version = good lol xD
Click to expand...
Click to collapse
Well it wasn't stable that broke this, it was a CAF merge I still should have dug deeper into the conflict, I definitely rushed it. I don't do that with the stable merges.
3.18.99 has been merged in.
3.18.100 has been merged in.
Hello Folks,
I am searching Testers for DIOS 12.1 My new upcoming Xperia exclusive OS.
Things that don't work actually on Sagami Boards due to the Xperia Software Binaries:
-Mobile Data
-Wifi
-NFC
-Battery Status (No Infos)
Make sure You know what You do. Flash the OEM Software binaries to use this AOSP/SODP based ROM. Flash all Images included in My ZIPs. OTAs can be applied over ADB and Recovery after You have flashed My Kernels/Recoveries. Feel free to ask Me out if You have Questions and consider Joining Me on Social Media or Discord to stay up-to-date.
Sign in - Google Accounts
Device Trees & Kernel: https://github.com/sonyxperiadev/local_manifests
Hi OP, since you are the original developer for this ROM, I changed the tag from General to Development.
Also, because you are posting this ROM yourself, could you please also post a link to kernel source repo? As on XDA we need to comply with GPL v2 which requires kernel source to be open source.
Thank you very much.
jerryhou85 said:
Hi OP, since you are the original developer for this ROM, I changed the tag from General to Development.
Also, because you are posting this ROM yourself, could you please also post a link to kernel source repo? As on XDA we need to comply with GPL v2 which requires kernel source to be open source.
Thank you very much.
Click to expand...
Click to collapse
Thanks for the Help! Since i am using the SODP Device Trees are we going with Pre-Compiled Kernels from the SODP for now.
Source will be added to the first Post! https://github.com/sonyxperiadev/local_manifests