Related
These are UNOFFICIAL CM10.1 JellyBean Nightlies / Releases brought to you by Mustaavalkosta and TeamCodefire as a continuum to CM10 nightlies.
{
"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"
}
#include
/*
* Your 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.
*/
Click to expand...
Click to collapse
General:
Builds are generated automatically each day week (except "releases" which will be done once a month and after SR1 when required) with latest changes from CM, Andromadus and myself. Builds use some required Andromadus' repos for msm7x30 that can be found from github (link below) and local device repo for ace. Kernel is based on synergye's KangBang kernel with some changes to fulfill some dependencies on this rom. Local manifest used for the builds can be found here. If the builds stop coming at some point, it most likely means there are changes in upstream that broke the build. I'll attend to solving such situations when I have time. Latest 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus (for msm7x30 repos)
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
Juansheng
KangBangKreations (shipped kernel is based on this)
paulb_nl
thachtunganh (s2w)
PipelinerArd (for initial spark for this project)
synergye
TeamCodefire (for build server and hosting, priceless)
a user (for provided tweaks)
Flow-Wolf (for the video review, see Q&A)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
Andromadus
CyanogenMod
Mustaavalkosta
Changelogs:
BBQLog
CM Gerrit
CM Google+
Github (see above)
Fresh installation instructions:
20130313 and newer nightlies are not compatible with KangBang 3.x or older!
Download Nightlies / Releases [BasketBuild mirror]
Download gapps (goo.im/gapps)
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
Flash gapps-jb-xxxxxxxx-signed.zip
Reboot and enjoy.
Update installation instructions:
20130313 and newer nightlies are not compatible with KangBang 3.x or older!
Download Nightlies / Releases [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
No need to flash gapps as CM backuptool script should take care of them.
Reboot and enjoy.
InspireMod
http://downloads.codefi.re/mustaavalkosta/inspiremod
Contact:
My Google+
My twitter
#codefireX @ freenode
Donations:
codefi.re (use the donation button at the bottom of the page)
Mustaavalkosta
(codefi.re donations are used to cover the server costs, my donations will be used to increase my beard growth in a way or another)
Q&A:
Q: What's "M-Series"?
A:
CyanogenMod said:
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
Click to expand...
Click to collapse
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: HTC Dev unlock is pretty much useless when flashing roms from recovery. Until HTC One, it doesn't allow flashing boot partition from recovery which pretty much kills or cripples any custom rom if boot.img has been modified. You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: What does the ROM look like?
A: Video review by Flow-Wolf.
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM10.1 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm10
cd cm10/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
mkdir -p .repo/local_manifests
wget https://github.com/Mustaavalkosta/android/raw/cm-10.1/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: My device rebooted itself all the way to the white HTC bootsplash. What should I do?
A:
synergye said:
Regarding the reboots, it would be incredibly helpful if someone could get a last_kmsg after an unexpected reboot. To do so, go directly to recovery after the reboot (without booting into android) via the volume key and power button, then run adb pull /proc/last_kmsg on your computer and upload. I thought the issue was stemming from out of pmem errors like on vision which is why I increased pmem allocation again. Without any evidence, it's just guesswork though.
Click to expand...
Click to collapse
Flashable zip to copy /proc/last_ksmg to your sdcard, no adb needed: http://downloads.codefi.re/mustaavalkosta/last_kmsg.zip
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 10.1 Nightlies / Releases [SR3], ROM for the HTC Desire HD
Contributors
Mustaavalkosta
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: SR3
Stable Release Date: 2013-11-25
Created 2014-10-09
Last Updated 2014-10-09
First:good:
MMS - 1a perfekt
GPS- 1a perfekt (need 16sek. for 16 Sat.)
Baterry- 360 min. from 100% to 89% (GPS;Whatsapp,3 call/ 15 min.,and more....
I use HOLO L. and Juice Def. PERFEKT COMBI!!!!
THX for this ROM man!
Second :crying:
But tested! and wow.. great rom! Thank you Mustaavalkosta ! :good:
here comes another one!
Wow, owners of other devices are sure gonna be jealous. Such an old device getting so many stable 4.2 ROM! Respect to all developers.
Sent from my Desire HD using xda app-developers app
I love that so much developers release new, stable ROM for DHD. keep it up devs. Very cool.
Sent It From Outer Space.
any plans releasing aokp version :victory: ?
since IceCold i didnt have AOKP
ps: do you want to marry me
yener90 said:
any plans releasing aokp version :victory: ?
since IceCold i didnt have AOKP
Click to expand...
Click to collapse
Nope, as close to AOKP as you can get currently (feature-wise) is by using codefireX (afaik).
ps: do you want to marry me
Click to expand...
Click to collapse
Depends if you like beards?
yener90 said:
any plans releasing aokp version :victory: ?
since IceCold i didnt have AOKP
ps: do you want to marry me
Click to expand...
Click to collapse
blindndumb has paranoid android, cm10 and AOKP mixture ROM, commonly known as PACman ROM. It is based on RB's R30
Sent from my Desire HD using xda app-developers app
Mustaavalkosta said:
Nope, as close to AOKP as you can get currently (feature-wise) is by using codefireX (afaik).
Click to expand...
Click to collapse
Yes i know, but it has so much patches, that i get trouble with it.
SR1:
- clock issue -> i came really late to university, after this i use more often my wristwatch xD
- opera issue -> only browser i can use on android
had more troubles didnt remember
SR2 i realised same problems. not the clock issue but the other.
Now i am using CM10.1. really love the rom
AOKP has more features -> only reason i want to have this rom
Mustaavalkosta said:
Depends if you like beards?
Click to expand...
Click to collapse
hmm i got self one i didnt expected that yu would agree :laugh:
NiCk.JaY said:
blindndumb has paranoid android, cm10 and AOKP mixture ROM, commonly known as PACman ROM. It is based on RB's R30
Click to expand...
Click to collapse
i already tried it.
Its slow. i dont like lags. i need a phone which is fast. codefireX & CM10.1 are the fastest roms i ever had.
Sorry being offtopic.
Here goes the 4.2 again , hooraay ..
Sent from my iPhone powered iOS 6.0.1 by Apple™
Hey anyone can show me screenshots of this ROM plz............
sagar4all007 said:
Hey anyone can show me screenshots of this ROM plz............
Click to expand...
Click to collapse
Rom looks same as other 4.2 there is no need to post ss.
Sent from my Desire HD using xda app-developers app
KalZakath said:
Rom looks same as other 4.2 there is no need to post ss.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Maybe i'm wrong, but it's not true. - I don't know any other pure AOSP+CM rom 4.2 for Ace
The other builds i've tested have extra settings
KalZakath said:
Rom looks same as other 4.2 there is no need to post ss.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
True but it is hard to show diffrience by screenies. If someone want to see how does it looks should install it because 1st impession is - standard 4.2.
Sent from my Desire HD using xda app-developers app
thanks to all the developers that make me use this phone
Mustaavalkosta said:
These are UNOFFICIAL CM10.1 JellyBean Nightlies brought to you by Mustaavalkosta and TeamCodefire as continuum to CM10 nightlies.
General:
Builds are generated automatically each night with latest changes from CM, Andromadus, KangBang stable kernel and myself. Builds use some required Andromadus' device specific repositories (for Desire S) that can be found from github (link below) and local device repository for ace. Local manifest used for the builds can be found here. If the builds stop coming at some point, it most likely means there are changes in upstream that broke the build. I'll attend to solving such situations when I have time. Latest 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus (for device specific repos)
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
Juansheng
KangBangKreations
PipelinerArd (for initial spark for this project)
synergye
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
Andromadus
CyanogenMod
KangBangKreations (kb-stable)
Mustaavalkosta
Changelogs:
BBQLog
CM Google+
CM Gerrit
Github (see above)
Installation instructions:
Download ROM
Download gapps (goo.im/gapps)
Put them on SD card.
Reboot to recovery.
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
Flash gapps-jb-xxxxxxxx-signed.zip
Reboot and enjoy.
Donations:
codefi.re (preferred, use the donation button at the bottom of the page)
Mustaavalkosta
(codefi.re donations are used to cover the server costs)
Q&A:
Q: What's the difference between these builds and PipelinerArd's builds?
A: These builds are as close to CM source as possible without breaking either build or hardware support. PipelinerArd uses a big chunk of codefireX's repositories for various things. This doesn't mean his builds are bad, they are just not very close to CM source anymore. You can compare the manifests yourself and decide which one better suits your needs. My local manifest / PipelinerArd's manifest. And again, I'm not here to invalidate his work and I've no quarrel with him. I'm just mentioning this as someone is bound to ask about it.
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: I'm not here to fix any device specific bugs or problems. I only compiled the build manifest using repositories already available to everyone. I can only rearrange build manifest to fix feature X. If it still doesn't work, too bad. Hope that Desire S is having the same problem and Andromadus is going to fix it. Help yourself and help others.
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Something about something something something.
A: Ask the guy/gal next to you.
Click to expand...
Click to collapse
If you're gonna compare your rom to mine you could at least get the repo right git://github.com/PipelinerArd/android.fit -b cm-10.1
I've just flashed and configured this rom as my daily one.
Anyway it seems to works fine as the other 4.2.1 roms, but anyway i've found a not "green" camera on this one on the preview of the shot.
PipelinerArd said:
If you're gonna compare your rom to mine you could at least get the repo right git://github.com/PipelinerArd/android.fit -b cm-10.1
Click to expand...
Click to collapse
Ah, my bad. The new github layout is confusing. I only saw the popular repositories when I was looking for your manifest. I spend my time mostly with bitbucket these days. You didn't have a direct link to manifest (nor any repo links) anywhere in your ROM's first post (or at least I didn't and still can't see anything). :|
I'm sorry for any hard feelings caused by unintentionally stepping on toes. I fixed the incorrect Q&A section. At least flashmaniacs should be happy for daily doses. Hurray.
can anyone confirm it possible to auto focus by hold shutter icon and capture by releasing it?
I have commit a new pull request in github
github.com/omnirom/android_packages_apps_OmniGears/pull/3
here is my fork
github.com/codetin/android_packages_apps_OmniGears/tree/android-4.4
code_tin said:
I have commit a new pull request in github
github.com/omnirom/android_packages_apps_OmniGears/pull/3
here is my fork
github.com/codetin/android_packages_apps_OmniGears/tree/android-4.4
Click to expand...
Click to collapse
Please upload on Gerrit
{
"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"
}
* By flashing this, you automatically void your warranty!
* If your phone breaks, blows up or runs away from you, do not cry to us!
* Do not ask for ETAs!!
* Download the ROM and GApps
* Reboot to recovery
* Wipe data/factory reset
* Flash the ROM and then GApps
* Reboot your phone
* Enjoy
* PAC-ROM Download
* Open GApps Nano 5.1
* PAC-ROM Sharing Policy
* PAC-ROM Site
* PAC-ROM Forum
* PAC-ROM Gerrit
* PAC-ROM Changelog
* PAC-ROM JENKINS
* PAC-ROM Bug Reports/Feature Requests
* PAC-ROM Github
* PAC-ROM Stats
* PAC-ROM Google+
* PAC-ROM Facebook
* PAC-ROM Twitter
* Want to become a device Maintainer for PAC-ROM?
* PAC-ROM Central - Questions and Features broken down and seen by all PAC Devs on XDA
* PAC-ROM Team
* Cyanogen Team
* AOKP Team
* Paranoid Android
* SlimRoms
* RootBox
* Carbon ROM
* Vanir
* ChameleonOS
* Omnirom
* Paranoid SaberDroid
* Special thanks to all our Build Bot Providers (see Contributors list for all names)
* PAC Graphix Team - Graphics, logos and images (see Contributors list for all names)
* And of course, thank you for your love and support!
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
Status: Unofficial Release
NOTE: THIS IS ONE AND THE LAST ONE 5.1.1 (LMY49J) BUILD.
AFTER INSTALLATION:
GO TO SETTINGS - PAC SETTINGS - MISCELLANEOUS - PAC STATS
AND UNCHECK THIS BOX <ENABLE REPORTING>
OPTIONAL:open build.prop file (requires root) and change string "ro.build.display.id=cm_tate-userdebug 5.1.1 LMY49J..." to "ro.build.display.id=pac_tate-userdebug 5.1.1 LMY49J..." (watch screenshot #1)
Personal Modifications:
- Bootanimation is replaced with MM bootanimation
- Old fashioned Calendar replaced with Google Calendar
- Added missing OmniSwitch
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
alexander_32 said:
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
Click to expand...
Click to collapse
That's fine; no hard feelings. You can PM transi1 your build issues, and I think he'd be glad to help you out.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's fine; no hard feelings. You can PM transi1 your build issues, and I think he'd be glad to help you out.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I've contacted transi1 already. Something wrong with file_context.
But, like I said before, it should be a release source.
By the way, I've got a difference viewer software to figure out differences between cm12.1 and cm13 branches. This should help also.
alexander_32 said:
I've contacted transi1 already. Something wrong with file_context.
But, like I said before, it should be a release source.
By the way, I've got a difference viewer software to figure out differences between cm12.1 and cm13 branches. This should help also.
Click to expand...
Click to collapse
I have the same issues when building for jem. If you don't mind PMing your build errors (preferably the whole build output if you have it), I can try to patch file_contexts until transi fixes the file to resolve the build errors. Also, you may later get an issue with make_recovery_patch; if you do, let me know and I'll tell you how to fix it. transi's been quite helpful when I started building my custom CM ROM for jem; I tried contacting him about the latest issue with file_contexts, but he hasn't responded yet.
Sent from my Amazon Jem using XDA Labs
Sorry to hijack the thread a bit, but I also receives the errors you mentioned. Transi has provided me a file_contexts file of his own, but the build errors out. There may have been more edits transi has done to his source that he has not mentioned or put on Git.
On the other hand, we're not mad at you . Were all on good terms.
xWolf13 said:
Sorry to hijack the thread a bit, but I also receives the errors you mentioned. Transi has provided me a file_contexts file of his own, but the build errors out. There may have been more edits transi has done to his source that he has not mentioned or put on Git.
On the other hand, we're not mad at you . Were all on good terms.
Click to expand...
Click to collapse
Yep, I guess that Git is not up to date.
Thank you xWolf13.
alexander_32 said:
@monster1612 , @jhnsmith08 , @xWolf13
Guys, I'm so sorry about pac 6.0. Hope you are not really mad at me and this post will cheer you up a little bit.
I had to reinstall Ubuntu, Windows + a lot of distractions and annoying stuff. It was a real mess.
Clearly, it was not a good idea to compile pac 6.0 now (pac 6.0 status: alpha 1). Plus I've got errors that are not easy to solve.
But I'll bring pac 6.0 for tate later (release version).
Hope you guys are not really mad at me.
Click to expand...
Click to collapse
I can't imagine anyone getting mad at you for attempting to give them something for free!! Thank you for your time and hard work. I am trying out this ROM today. Lollipop is okay by me AND it's at least up to date as of April which is nice too! :good:
vasolini said:
I can't imagine anyone getting mad at you for attempting to give them something for free!! Thank you for your time and hard work. I am trying out this ROM today. Lollipop is okay by me AND it's at least up to date as of April which is nice too! :good:
Click to expand...
Click to collapse
You're welcome. I'm gonna to bring AOSP MM ROMs for tate this summer. I've noticed that full_tate-userdebug command is related to AOSP compiling, but will it work with Marshmallow? That is the question. And I'll bring release version of PAC MM (Alpha 1 at the moment) later.
Don't forget to go to PAC Settings-MISCELLANEOUS-PAC Stats and uncheck Enable reporting box. That box causes Settings error when you turn on WIFI. Also, I recommend you to delete useless system apps, like: phone, mms, browser etc. You can do it before flashing, by the way. Thanks for your interest.
alexander_32 said:
You're welcome. I'm gonna to bring AOSP MM ROMs for tate this summer. I've noticed that full_tate-userdebug command is related to AOSP compiling, but will it work with Marshmallow? That is the question. And I'll bring release version of PAC MM (Alpha 1 at the moment) later.
Don't forget to go to PAC Settings-MISCELLANEOUS-PAC Stats and uncheck Enable reporting box. That box causes Settings error when you turn on WIFI. Also, I recommend you to delete useless system apps, like: phone, mms, browser etc. You can do it before flashing, by the way. Thanks for your interest.
Click to expand...
Click to collapse
I suppose building with that recipe (full_tate_userdebug) might not matter all that much. I'm going to try compiling vanilla CM with that option (its jem equivalent, anyway) tonight and seeing if it works. brunch jem worked without a hitch for me, so I would suppose that one could use that same command for tate and not have any errors. When you say AOSP, do you mean actual AOSP (no CM or other derivatives)? If you try full_tate_userdebug on a CM build tree, it would most likely compile CM or whatever's in the tree.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
I suppose building with that recipe (full_tate_userdebug) might not matter all that much. I'm going to try compiling vanilla CM with that option (its jem equivalent, anyway) tonight and seeing if it works. brunch jem worked without a hitch for me, so I would suppose that one could use that same command for tate and not have any errors. When you say AOSP, do you mean actual AOSP (no CM or other derivatives)? If you try full_tate_userdebug on a CM build tree, it would most likely compile CM or whatever's in the tree.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I'm gonna download AOSP and see what happens (with full_tate-userdebug command). I've seen on github Hashcode's file about compiling android 4.3 AOSP for tate. There was a line about full_tate-userdebug. We'll see. I'm gonna start in June.
You mean there is no full_jem-userdebug command or what? You can try of course to compile vanilla CM with full_tate-userdebug option, but I guess it's correct to use cm_jem-userdebug command.
alexander_32 said:
I'm gonna download AOSP and see what happens (with full_tate-userdebug command). I've seen on github Hashcode's file about compiling android 4.3 AOSP for tate. There was a line about full_tate-userdebug. We'll see. I'll gonna start in June.
You mean there is no full_jem-userdebug command or what? You can try of course to compile vanilla CM with full_tate-userdebug option, but I guess it's correct to use cm_jem-userdebug command.
Click to expand...
Click to collapse
I'm pretty sure there is a full_jem_userdebug option; it would just build whatever source is present in the build trees. The cm_jem_userdebug command is a built-in parameter for officially supported CM devices, and thus it would make sense for the option to not exist when building straight AOSP; full_jem_userdebug and full_tate_userdebug are commands provided by the local manifest file. As long as you make sure to add in the local manifest file like normal and resolve the build issues beforehand (like the multiple same specs for the file_contexts file), you shouldn't have too much trouble building AOSP from source. Just note that some of the conventional build steps you'd have when building CM differ when building AOSP.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
I'm pretty sure there is a full_jem_userdebug option; it would just build whatever source is present in the build trees. The cm_jem_userdebug command is a built-in parameter for officially supported CM devices, and thus it would make sense for the option to not exist when building straight AOSP; full_jem_userdebug and full_tate_userdebug are commands provided by the local manifest file. As long as you make sure to add in the local manifest file like normal and resolve the build issues beforehand (like the multiple same specs for the file_contexts file), you shouldn't have too much trouble building AOSP from source. Just note that some of the conventional build steps you'd have when building CM differ when building AOSP.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Alright, we'll see what happens.
Just wanted to say thanks for posting this...
It's a very solid rom.
I get one error on reboots, ("settings has stopped"), but other than that very minor glitch it's a very usable rom.
mikeataol said:
Just wanted to say thanks for posting this...
It's a very solid rom.
I get one error on reboots, ("settings has stopped"), but other than that very minor glitch it's a very usable rom.
Click to expand...
Click to collapse
Go to settings - pac settings - miscellaneous - pac stats and uncheck this box <enable reporting>
It will solve "settings has stopped".
Thanks.
alexander_32 said:
Go to settings - pac settings - miscellaneous - pac stats and uncheck this box <enable reporting>
It will solve "settings has stopped".
Thanks.
Click to expand...
Click to collapse
Fixed it as you expected it would, Thanks!
mikeataol said:
Fixed it as you expected it would, Thanks!
Click to expand...
Click to collapse
No problem
That is the last one Lollipop release (LMY49J), by the way. Forgot to add it before.
Hello to all. I hope someone can help me.
Background: I am a relatively experienced programmer. I have been programming with C/C++ (and other) in Linux for the last 6 years or so. However I have never dived in Linux Kernel development yet. So I would appreciate some help from anyone that can help me.
Goal: My goal is to learn more about Linux Kernel development. I want to start from my beloved G2, which is approaching its usage EOL. The device is fine, but I am planning on investing on a new one, so I will be able to squeeze it as much as I want.
I want to create a clean kernel for AOSP (CAF) based versions of Android. My vision is to start with a clean CAF base (without CM patches, etc) and bring it up-to-date till Linux 3.4.113 and manage it to boot. Then start backporting code, enhancements, etc. and making tests.
I searched in CAF repositories and I found them to be a mess. Can someone who is experienced with how things work point to the latest clean CAF source for msm8974?
I also want to hear anyone's thoughts on the attempt. Thanks ahead and regards.
Maybe @GalaticStryder, you can give me some guidelines. Deeply appreciated.
errikosd said:
Hello to all. I hope someone can help me.
Background: I am a relatively experienced programmer. I have been programming with C/C++ (and other) in Linux for the last 6 years or so. However I have never dived in Linux Kernel development yet. So I would appreciate some help from anyone that can help me.
Goal: My goal is to learn more about Linux Kernel development. I want to start from my beloved G2, which is approaching its usage EOL. The device is fine, but I am planning on investing on a new one, so I will be able to squeeze it as much as I want.
I want to create a clean kernel for AOSP (CAF) based versions of Android. My vision is to start with a clean CAF base (without CM patches, etc) and bring it up-to-date till Linux 3.4.113 and manage it to boot. Then start backporting code, enhancements, etc. and making tests.
I searched in CAF repositories and I found them to be a mess. Can someone who is experienced with how things work point to the latest clean CAF source for msm8974?
I also want to hear anyone's thoughts on the attempt. Thanks ahead and regards.
Click to expand...
Click to collapse
I think the pure branch in GalaticStryder's Github is pure caf kernel, I don't think he added anything.
shaneel1491 said:
I think the pure branch in GalaticStryder's Github is pure caf kernel, I don't think he added anything.
Click to expand...
Click to collapse
Unfortunately, I think that that branch does not exist anymore. Except if it is now called "marshmallow-caf".
errikosd said:
Unfortunately, I think that that branch does not exist anymore. Except if it is now called "marshmallow-caf".
Click to expand...
Click to collapse
It could be, not sure though.. I did download the source when he had it, I can zip and upload if you need?
Edit: nevermind, I forked his source a while back. Here https://github.com/shack-32/kernel_lge_msm8974/tree/pure
Also when I built it, as well as when he built, the mpdecision seems to be busted on boot, so the cores won't hotplug, you can enable it by looking in /sys directory and echo '1' for the mpdecision file.
shaneel1491 said:
It could be, not sure though.. I did download the source when he had it, I can zip and upload if you need?
Edit: nevermind, I forked his source a while back. Here https://github.com/shack-32/kernel_lge_msm8974/tree/pure
Also when I built it, as well as when he built, the mpdecision seems to be busted on boot, so the cores won't hotplug, you can enable it by looking in /sys directory and echo '1' for the mpdecision file.
Click to expand...
Click to collapse
Thanks a lot! I believe this would be a good start.
I will try and pair it with anykernel packager and enable mpdecision on boot.
errikosd said:
Thanks a lot! I believe this would be a good start.
I will try and pair it with anykernel packager and enable mpdecision on boot.
Click to expand...
Click to collapse
Cool, good luck with it!
Well, I'd first need to explain some other stuff first before you get started
The CAF release for MSM8974 Kernel is oddly one of the no longer maintained ones: LA.BF.1.1.1.x.
To initialize a brand new clean Kernel you'd need to pull the CAF source code and copy the plain LGE Kernel code from the latest release they pushed which is if I'm not mistaken D80230F, then diff it to see what has got replaced and get it back, adapting the code manually on top of the recently merged LGE source code.
This would basically be the first step, then you'd head over to compilation fixes, create the scripts and the tools to bump the image and flash it to see if it boots.
To support more devices you'd need to merge the other variants as well from LGE source code and then do the same as before...
This doesn't make sense since you'd be getting an old Kernel from CAF and yet an older one from LGE. The little updates made on top of the first CyanogenMod 12.1 (CAF Kernel) were very basic and were caught already either by CM itself on their Kernel tree or mine.
Then you'd go forward to merging the kernel-common updates for 3.4.y coming from Google source code and then head over to update the base Linux Kernel version, fix compilation and such...
Since all this is done already, all you'd need is forking the Kernel at 3.4.110 and cherry-pick the selected changes you'd like up to 3.4.113 and compile using my scripts and all that...
The HEAD for that is c8bd789d12f8299db2e5a319abeb4a95df9078b6 and you're set to freely modify it the way you think should be done...
This is the lazy way of course but a great start...
GalaticStryder said:
Well, I'd first need to explain some other stuff first before you get started
The CAF release for MSM8974 Kernel is oddly one of the no longer maintained ones: LA.BF.1.1.1.x.
To initialize a brand new clean Kernel you'd need to pull the CAF source code and copy the plain LGE Kernel code from the latest release they pushed which is if I'm not mistaken D80230F, then diff it to see what has got replaced and get it back, adapting the code manually on top of the recently merged LGE source code.
This would basically be the first step, then you'd head over to compilation fixes, create the scripts and the tools to bump the image and flash it to see if it boots.
To support more devices you'd need to merge the other variants as well from LGE source code and then do the same as before...
This doesn't make sense since you'd be getting an old Kernel from CAF and yet an older one from LGE. The little updates made on top of the first CyanogenMod 12.1 (CAF Kernel) were very basic and were caught already either by CM itself on their Kernel tree or mine.
Then you'd go forward to merging the kernel-common updates for 3.4.y coming from Google source code and then head over to update the base Linux Kernel version, fix compilation and such...
Since all this is done already, all you'd need is forking the Kernel at 3.4.110 and cherry-pick the selected changes you'd like up to 3.4.113 and compile using my scripts and all that...
The HEAD for that is c8bd789d12f8299db2e5a319abeb4a95df9078b6 and you're set to freely modify it the way you think should be done...
This is the lazy way of course but a great start...
Click to expand...
Click to collapse
So that HEAD has to be the cleanest "working" snapshot I can get, right?
Thanks a lot for outlining the procedure and giving me the boost I needed. It will be definitely easier to get started now.
errikosd said:
So that HEAD has to be the cleanest "working" snapshot I can get, right?
Thanks a lot for outlining the procedure and giving me the boost I needed. It will be definitely easier to get started now.
Click to expand...
Click to collapse
Yes, it's pretty clean. Make sure you clean anykernel too.
There's a lot of work for developing kernels! I would like to learn how to do step by step, but i think i have a lot of things that i must learn before starting developing a kernel... As languages i'm learning C, but i don't know other...
matteo0026 said:
There's a lot of work for developing kernels! I would like to learn how to do step by step, but i think i have a lot of things that i must learn before starting developing a kernel... As languages i'm learning C, but i don't know other...
Click to expand...
Click to collapse
Building a kernel is not too hard, adding stuff is a bit tougher. You should start but simply downloading the source of a kernel already found on GitHub. There are various guides on xda that teach you how to build. Once you are comfortable with building you can go on to adding governors and many other tweaks, that's where commits come into play as it makes everything easier to add stuff.
This is a simple tutorial, try look for some more as well http://forum.xda-developers.com/showthread.php?t=2152819
shaneel1491 said:
Building a kernel is not too hard, adding stuff is a bit tougher. You should start but simply downloading the source of a kernel already found on GitHub. There are various guides on xda that teach you how to build. Once you are comfortable with building you can go on to adding governors and many other tweaks, that's where commits come into play as it makes everything easier to add stuff.
This is a simple tutorial, try look for some more as well http://forum.xda-developers.com/showthread.php?t=2152819
Click to expand...
Click to collapse
I'm yet blocked on one step of guide... i can't find only one file g2_blablabla.deconfig...
matteo0026 said:
I'm yet blocked on one step of guide... i can't find only one file g2_blablabla.deconfig...
Click to expand...
Click to collapse
It's not actually named blablabla, the defconfig directory is basically the insturctions to build for all the different devices, so it should be g2_d802.defconfig or something along those lines for D802, as long as it has your device name, for example when Dorimanx builds, his file would be (https://github.com/dorimanx/Dorimanx-LG-G2-D802-Kernel/tree/LG-STOCK-KK/arch/arm/configs) -> dorimanx_d802_defconfig
The defconfig file is found in /arch/arm/configs directory
shaneel1491 said:
It's not actually named blablabla, the defconfig directory is basically the insturctions to build for all the different devices, so it should be g2_d802.defconfig or something along those lines for D802, as long as it has your device name, for example when Dorimanx builds, his file would be (https://github.com/dorimanx/Dorimanx-LG-G2-D802-Kernel/tree/LG-STOCK-KK/arch/arm/configs) -> dorimanx_d802_defconfig
The defconfig file is found in /arch/arm/configs directory
Click to expand...
Click to collapse
Ok, then there isn't nothing of d802_something_deconfig
See this too
{
"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"
}
matteo0026 said:
Ok, then there isn't nothing of d802_something_deconfig
See this tooView attachment 3929508
Click to expand...
Click to collapse
Which repo did you download source from. You can use the d802 config one from my forked version of galatic's pure branch
https://github.com/shack-32/kernel_lge_msm8974/tree/pure/arch/arm/configs
Dori's config is named: dorimanx_d802_defconfig
shaneel1491 said:
Which repo did you download source from. You can use the d802 config one from my forked version of galatic's pure branch
https://github.com/shack-32/kernel_lge_msm8974/tree/pure/arch/arm/configs
Dori's config is named: dorimanx_d802_defconfig
Click to expand...
Click to collapse
Ok, maybe the problem is that i took full stock sources kernel from opensource.lge.com ... Then now i try to do the same thing with lambda sources...?
matteo0026 said:
Ok, maybe the problem is that i took full stock sources kernel from opensource.lge.com ... Then now i try to do the same thing with lambda sources...
Click to expand...
Click to collapse
Hmmm, as far as I know you might run into problems building LG provided ROM for an AOSP/CM rom, so if you follow the same process with caf kernel it should work.
shaneel1491 said:
Hmmm, as far as I know you might run into problems building LG provided ROM for an AOSP/CM rom, so if you follow the same process with caf kernel it should work.
Click to expand...
Click to collapse
Ok then must i take a CAF kernel? Can i take lambda kernel?
matteo0026 said:
Ok then must i take a CAF kernel? Can i take lambda kernel?
Click to expand...
Click to collapse
Either, lambda is a modified caf version
{
"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"
}
team bliss is pleased to present to you
bliss rom based on Android 9 Pie
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Notice
The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible.We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.Please do not ask for ETA'sWe will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts
AIO Thread
Bliss Sourcehttps://github.com/BlissRoms
BlissRoms Devices Sourcehttps://github.com/BlissRoms-Devices
BlissRoms Kernel Sourcehttps://github.com/BlissRoms-Kernels
BlissRoms Vendor Sourcehttps://github.com/BlissRoms-Vendor
We suggest using OpenGapps, but if your device maintainer mentions otherwise, please go with that suggestion. Open Gapps Project
WARNING: If you dirty flash BlissRoms you must install the same Gapps you flashed, or a newer version, BEFORE rebooting. Rebooting will corrupt the system into an unrecoverable state. For best results, use Opengapps, use the SAME variant download and make sure to flash the same date/newer version.
For example, if you flashed Opengapps micro 20190307, then after flashing a new BlissRoms zip you must flash the same micro 20190307 zip again, OR a micro variant with a date that is newer than 20190307 (e.g. 20190506).
Bliss Device DownloadsBullhead BuildsAlternate download mirror (archive)
Team Bliss is not responsible in any way for anything that happens to your device in the process of installingPlease familiarize yourself with flashing and custom rom use before attempting to flash the rom. Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Make sure you are rootedMake sure you have a custom recovery installed(TWRP is the preferred recovery)Download the latest Bliss Rom & the latest GApps packageBoot into recoveryBackup your current ROMPerform a FULL factory wipe and wipe/system and dalvik cache as a precautionFlash Bliss RomFlash Google Apps packageFlash Root of your choice(Unless OP states otherwise)First boot may take up to 10 minutes. This is due to Gapps and root optimization.
[*] Issue with fc when accessing battery manager in settings[*] Possible issue with android system failing on certain firmware/variants
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
Download the Catlog app from the Play Store.There is also a donate version which you can purchase to show appreciation.After downloading the Catlog app, go to the app settings, and change the log level to Debug.Clear all previous logs and take the exact steps to produce the error you are receiving.As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.Copy and paste the entire log either to Hastebin or PastebinSave the log, and copy and paste the link into the forum with a brief description of the error.
@Jackeagle @electrikjesus @rfwaterspf1 @Makaveli_da_dev @ElfinJNoty @BitOBSessiOn @customworx@nilac @sixohtew @aclegg2011 @Roger.T @T.M.Wrath @kanttii @rev3nt3ch @techfreak243 @SuperDroidBond @USA_RedDragon @bcrichster@deadmanxXD @krittin98 @BlackScorpion @techexhibeo @droidbot @siphonay @pacer456 @nitin1438 @theGeekyLad @kunalshah912 @regalstreak @lordarcadiusA huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!We really appreciate all your knowledge & hard work!
Thanks to @milouk for allowing me to use his kernel with my builds.
Team Bliss aims to develop and maintain various OS & software projects for educational and the Android community building purposes. Team membership consist of and provides:training, development opportunities, design opportunities, build servers, download servers, design & development software,as well as professionals and mentors in all fields revolving around Android development.If someone wants to donate, please do so via this PayPal link:
PayPal LinkWE ARE A U.S. FEDERAL NON-PROFIT ORGANIZATION (501c3)
We receive a small donation each time you make a purchase with “Amazon Smile”:https://smile.amazon.com/ch/82-3580195
Very Important InformationTeam Bliss will allow some minor off-topic comments in our development threads. Please post in the general forums for off-topic comments and/or questions. Overall, please keep comments relevant to development, as this better helps you and our teamwhen trying to determine problems that users are having. We appreciate all levels of knowledge in our threads, and therefore we ask that the seasoned members be helpful to those with less knowledge. Most importantly, do NOT troll those with less knowledge than yourself.Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts. We thank you for adhering to our thread rules.
Websitehttps://blissroms.com
Telegram Communitieshttps://t.me/Team_Bliss_Communityhttps://t.me/blissx86[/CENTER]
https://t.me/Team_Bliss_Build_Supporthttps://t.me/Project_Xtremis
Official Platform Linkshttps://www.facebook.comBlissFamilyOfROMshttps://plus.google.com/communities/118265887490106132524https://twitter.com/Bliss_ROMshttps://www.instagram.com/blissroms
Thank you for using Bliss! And as always: #StayBlissful
XDA:DevDB Information
BlissRoms, ROM for the LG Nexus 5X
Contributors
jackeagle, ideaman924
Source Code: https://github.com/BlissRoms
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Pie
Version Information
Status: Stable
Current Stable Version: 11.9
Stable Release Date: 2019-07-06
Created 2018-11-26
Last Updated 2019-07-31
Notes and Credits
Notes
- Have any bugs ? Kindly post elaborated bug report with logs! Logs are important to debug anything!
- Clean flash (Always! This will save your future valuable time)
Credits
- Huge Thanks to aoscp dev Sirhc95
== Changelog ==
Dec 6th , 2018
Code:
====================
12-06-2018
====================
* device/lge/bullhead/
52dc046 Merge https://github.com/CypherOS/device_lge_bullhead into HEAD
====================
12-05-2018
====================
* build/make/
355fcca2e Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform/build into HEAD
* manifest/
9864d3b Merge branch 'android-9.0.0_r21' of https://android.googlesource.com/platform/manifest into default
* system/vold/
28b6192 Revert "Do not unmount /mnt/product/* when vold starts"
====================
12-04-2018
====================
* art/
1eb5787020 add .gitreview
* bionic/
492863b68 Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform//bionic into HEAD
* build/make/
e4c3d0138 core: Disable vendor restrictions
* frameworks/base/
79c9233d627 Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform//frameworks/base into HEAD
* frameworks/native/
1ceaa3f92 Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform//frameworks/native into HEAD
* kernel/lge/bullhead/
1aad5383bff Merge https://github.com/CypherOS/kernel_lge_bullhead into HEAD
* manifest/
628bd23 Manifest for Android 9.0.0 Release 21
8e0e67b Manifest for Android 9.0.0 Release 19
* packages/services/Telecomm/
099b39a1 Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform//packages/services/Telecomm into HEAD
* system/bt/
e8bcf6f68 Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform//system/bt into HEAD
* system/core/
267642e96 LockscreenCharging: squashed (2/3)
e64d23e27 Revert "debuggerd: Resolve tombstoned missing O_CREAT mode"
d780cc637 adb: Add wait-for-online command
d77afa85e debuggerd: add Bliss version to tombstones
e872d56a6 adb: host: Provide better sideload status
0040bcd72 sdcard: Allow building as a static library
a4fc98bcc libsysutils: Allow building static library
15c8f6757 debuggerd: Resolve tombstoned missing O_CREAT mode
1a558ef80 bsdgrep: for -r, use the working directory if none specified
28458cfa3 camera: Add L-compatible camera feature enums
5daf2890f init: Don't run update_sys_usb_config if /data isn't mounted
9a5b9458a rootdir: init.rc: Fix for "add_tid_to_cgroup failed to write" warnings
47372e070 Handle UFS card
f956b47da healthd: allow custom charger images
a32c6980f healthd: Reinitialize mChargerNames for every battery update
9f559c6ea healthd: cover devices that have voltage_max file with value of 0
f973d9f41 utils: Threads: Handle empty thread names
559d53618 healthd: Add support for HVDCP_3 chargers
9054a78b7 healthd: Add DASH charger type
3baebc227 init: always allow local.prop overrides
fff120825 fs_mgr: Add fs_mgr_get_entry_for_mount_point_after to header
55057582e adb: Look for executables in alternate places
568b86889 Camera: Add feature extensions
84471b02c logcat: Map '-C' to 'logcat -v color'
788dedb86 mkbootimg: add 32K 64K and 128K pagesizes
db1235f2c mkbootimg: add support for --dt
a451d11b0 init: don't skip starting a service with no domain if permissive
72619f9fa init: Add vendor-specific initialization hooks.
47c438fe2 Disable flashing of stock recovery correctly
589ca3533 Set permissions on /system/addon.d/ and files within.
014d25101 Set /system/etc/init.d/* permissions
c4761807c Add .gitreview
9460b94fb Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform/system/core into HEAD
* system/vold/
aca378d Merge tag 'android-9.0.0_r21' of https://android.googlesource.com/platform//system/vold into HEAD
* vendor/bliss/
56e8bd6e update list of Official devices
====================
12-03-2018
====================
* build/make/
a6ce51269 [treble builds] remove external/exfat from treble manifest
f2e28787c [x86 builds] remove external/exfat from x86 manifest
d56f4ce5c Move changelog generator to build
a01d852f4 Revert "[x86 builds] Switch to old foss sources"
55d84b4a0 [x86 builds] Switch to old foss sources
7b8c9d002 [x86 builds] Add Go-Gapps
ce1a1ba65 [x86 builds] Let's fix the proprietary method some more
185b30e53 [x86 builds] Add proprietary method
e806ae5af [x86 builds] drm_framebuffer tests 1/2
758b5edda build: Automatically replace old-style kernel header includes with new header lib
9bde9947f [treble builds] Fix derp in treble-build scripts
1f743a6d3 [treble builds] rework things a bit more
aecb3e178 [treble builds] Rework patching system
56f8e0a21 [treble builds] Add -p (patch) flag
291656e64 Drop deprecated stuff/move stuff to vendor/device
2ed30eaf8 Merge tag 'android-9.0.0_r16' of https://android.googlesource.com/platform/build into HEAD
====================
12-02-2018
====================
* frameworks/av/
016a03a13 Merge changes from topic "updates" into p9.0
* manifest/
3033edd track json-c
Thanks developers for this rom. Will try it soon.?
Deleted.
Bliss was my favourite ROM when I had my N5, I hope it's going to be as good for the N5X !
Volte working?
rahuldude0504 said:
Volte working?
Click to expand...
Click to collapse
Never
Sent from my LG Nexus 5X using XDA Labs
Has anyone already installed this firmware? It's just that NFC does not work for me, I wanted to find out if this is a common bug or just my.
kaso911 said:
Never
Click to expand...
Click to collapse
Volte is working fine on DU 13 for bullhead.
francos21 said:
Volte is working fine on DU 13 for bullhead.
Click to expand...
Click to collapse
Give link to download
erfan khan said:
Give link to download
Click to expand...
Click to collapse
First I can't give it until official DU release.
Secondly it's not the right place to speak about DU here it's not fair for the dev. I was simply implying that it was not "Never".
rahuldude0504 said:
Volte working?
Click to expand...
Click to collapse
VoLTE isn't limited to the ROM; your carrier also has to support the VoLTE standard used in your device. If there is a mismatch, or your carrier uses a different protocol, then VoLTE will break. We've included the minimum required for VoLTE to function, but we cannot guarantee it will work in all regions under all conditions.
Should you feel your carrier definitely supports the VoLTE standard used on your 5X, please file a bug report with a logcat included. Thank you!
How is batterylife? I had the pixelexperience rom (batterylife was not great)
After that i installed the AOSCP rom. With good batterylife.
francos21 said:
Volte is working fine on DU 13 for bullhead.
Click to expand...
Click to collapse
Where I find DU 13 for bullhead? ?
Sent from my bullhead using XDA Labs
panamera2011 said:
Where I find DU 13 for bullhead? ?
Click to expand...
Click to collapse
Read 3 post above yours
Has anyone tried this ROM? Is it good as a daily driver? Does root work?
ideaman924 said:
VoLTE isn't limited to the ROM; your carrier also has to support the VoLTE standard used in your device. If there is a mismatch, or your carrier uses a different protocol, then VoLTE will break. We've included the minimum required for VoLTE to function, but we cannot guarantee it will work in all regions under all conditions.
Should you feel your carrier definitely supports the VoLTE standard used on your 5X, please file a bug report with a logcat included. Thank you!
Click to expand...
Click to collapse
Thank you for the reply...
I'll try if it is working or not, if not I'll just report a bug and will send logcat?
laserswift said:
Is selinux enforcing? I can't find that information when I go to about phone.
Click to expand...
Click to collapse
Nope, it's permissive. You can check in terminal: su -c getenforce
works very well so far, didn't notice any problems myself