Code:
#include <rbh_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked phones, ISIS invasions, ebola outbreaks,
* or any other major catastrophe encountered while running my kernel.
* You flashed this, you did this to yourself. You did this to us all.
* The world shall stone you to death for your crimes against humanity.
* If you want to blame someone, blame my twin, he's evil!
*
* BASIC ADB/FASTBOOT SKILLS REQUIRED
*/
FEATURES:
* Based on HTC M8 CM11 Kernel
* Built with latest Linaro Toolchain
(refer below for more details)
* Extra Governors
* Extra Schedulers
* Supports Exfat, F2FS, NTFS, CIFS etc.
* Native Gamepad support for 6th Gen Controllers (USB+BT)
* Butter smooth!
* Updated GPU Drivers
Linaro Toolchain info:
Code:
[email protected]:/media/rbheromax/4e3f6837-13f1-4e0e-b871-970c17fd13e7/Android/android_kernel_htc_msm8974$ ~/android/*hf*/bin/*gcc -v
Using built-in specs.
COLLECT_GCC=/home/rbheromax/android/gcc-linaro-4.9-2014.05-arm-linux-gnueabihf-x86_64-linux-gnu/bin/arm-linux-gnueabihf-gcc
COLLECT_LTO_WRAPPER=/media/rbheromax/4e3f6837-13f1-4e0e-b871-970c17fd13e7/Android/gcc-linaro-4.9-2014.05-arm-linux-gnueabihf-x86_64-linux-gnu/bin/../libexec/gcc/arm-linux-gnueabihf/4.9.1/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: '/home/buildslave/workspace/shared//snapshots/gcc.git~linaro-4.9-branch/configure' --with-bugurl=https://bugs.launchpad.net/gcc-linaro --with-mpc=/home/buildslave/workspace/BuildFarm/label/x86_64/target/arm-linux-gnueabihf/_build/builds/destdir/x86_64-unknown-linux-gnu --with-mpfr=/home/buildslave/workspace/BuildFarm/label/x86_64/target/arm-linux-gnueabihf/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gmp=/home/buildslave/workspace/BuildFarm/label/x86_64/target/arm-linux-gnueabihf/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gnu-as --with-gnu-ld --disable-libstdcxx-pch --disable-libmudflap --with-cloog=no --with-ppl=no --with-isl=no --disable-nls --enable-multiarch --disable-multilib --enable-c99 --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb --enable-languages=c,c++,fortran,lto --with-sysroot=/opt/linaro/sysroot-glibc.git-arm-linux-gnueabihf --disable-shared --enable-static --disable-bootstrap --with-build-sysroot=/home/buildslave/workspace/BuildFarm/label/x86_64/target/arm-linux-gnueabihf/_build/sysroots/arm-linux-gnueabihf --enable-lto --enable-linker-build-id --enable-long-long --enable-plugin --enable-shared=libgcc,libstdc++-v3,liblto_plugin --with-bugurl=https://bugs.launchpad.net/gcc-linaro --with-pkgversion='Linaro GCC 2014.05' --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=arm-linux-gnueabihf --prefix=/home/buildslave/workspace/BuildFarm/label/x86_64/target/arm-linux-gnueabihf/_build/builds/destdir/x86_64-unknown-linux-gnu
Thread model: posix
gcc version 4.9.1 20140422 (prerelease) (Linaro GCC 2014.05)
ToDO: Give me FEATURE REQUESTS!!!
It is OK to bug me about ETAs, otherwise I just might not even put anything out lol
Click to expand...
Click to collapse
Source: https://github.com/rbheromax/android_kernel_htc_msm8974
Reserved
Changelog:
V0:
Current bugs:
* FFC (Front Camera)
* Back Camera
* Likes to SOD (Sleep of Death) while on ART
* You tell me...
your putting in major work bro,i can see you taking this phone to some great places :good:
@rbheromax, Kali Man and I have been working on CM11 for a few weeks now, i originally started the rom development and he is helping with rom and kernel. We are very close to having a fully working Cm11 port, Then on to CM12
shinru2004 said:
@rbheromax, Kali Man and I have been working on CM11 for a few weeks now, i originally started the rom development and he is helping with rom and kernel. We are very close to having a fully working Cm11 port, Then on to CM12
Click to expand...
Click to collapse
hey for a part of the cm11 could there be a way to get rid of the emulated sd card like entirely?
or have the system use symbolic linking like it has on stock?
Is the download link down? I'd like to test this kernel please.
Muhff said:
Is the download link down? I'd like to test this kernel please.
Click to expand...
Click to collapse
what every happen to the cm11 kernel..... forgotin rom....
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
smiley45 said:
what every happen to the cm11 kernel..... forgot rom....
Click to expand...
Click to collapse
what is the best Linux to use to try and port cm11 and 12 form a5 to your phones. I was think BBQ Linux instead of Ubuntu 13.10 with Ubuntu 13.10 I failed so many times and they say BBQ have everything for android dev. please let me know and just a note I am still learning so a clean answer would be nice.........................
smiley45 said:
what every happen to the cm11 kernel..... forgotin rom....
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
what is the best Linux to use to try and port cm11 and 12 form a5 to your phones. I was think BBQ Linux instead of Ubuntu 13.10 with Ubuntu 13.10 I failed so many times and they say BBQ have everything for android dev. please let me know and just a note I am still learning so a clean answer would be nice.........................
Click to expand...
Click to collapse
We've still got kernels, we've got an Omni kernel and a CM kernel, we can build a kernel just fine, EVERYTHING ROM side starts to break into pieces.
To answer your question, I switch between Arch and Mint quite frequently and @rbheromax uses Ubuntu.
I've never heard of BBQ, but it appears to be a just a spin-off of Arch (which is generally not a beginner-friendly dirstro).
Also you'll have to download the sources for whatever you decide to dev for and there's no way that comes bundled with BBQ.
dip_spit said:
We've still got kernels, we've got an Omni kernel and a CM kernel, we can build a kernel just fine, EVERYTHING ROM side starts to break into pieces.
To answer your question, I switch between Arch and Mint quite frequently and @rbheromax uses Ubuntu.
I've never heard of BBQ, but it appears to be a just a spin-off of Arch (which is generally not a beginner-friendly dirstro).
Also you'll have to download the sources for whatever you decide to dev for and there's no way that comes bundled with BBQ.
Click to expand...
Click to collapse
http://www.google.com/url?sa=t&rct=...9Ygt6pjJHA_Ic9abQ&sig2=cibdhoVUjSQxZ3Uz2xaeEw
thanks for the advice. I was reading about the bb q Linux form here . I thought it might help me out. but I just going to stay with Ubuntu or I will try the new Ubuntu mate 15.04 and see where it goes..... thanks again.
smiley45 said:
what is the best Linux to use to try and port cm11 and 12 form a5 to your phones. I was think BBQ Linux instead of Ubuntu 13.10 with Ubuntu 13.10 I failed so many times and they say BBQ have everything for android dev. please let me know and just a note I am still learning so a clean answer would be nice.........................
Click to expand...
Click to collapse
I wasn't going to answer this question as I am not as advanced as the Devs for this phone, I'm more intermediate, but I love Ubuntu 14.10. It is very user friendly and I have been able to simply do Google searches and ask a couple of questions to do everything I want to do on it. Ubuntu is pretty much self-correcting. If you try to install something and you are missing a prerequisite, it lets you know, or if it doesn't work quite right a Google search will always answer your inquiry.
rbheromax said:
Reserved
Click to expand...
Click to collapse
Can you also please provide a CM11 build with the latest repo sync (and your awesome kernel included)? Thanks.
Download link by chance?
shinru2004 said:
@rbheromax, Kali Man and I have been working on CM11 for a few weeks now, i originally started the rom development and he is helping with rom and kernel. We are very close to having a fully working Cm11 port, Then on to CM12
Click to expand...
Click to collapse
I'm interested in compiling cm12.1 and helping to debug the build process, however, there are so many device trees and kernel repos that I don't know which ones to use. Could you point me towards the ones that you use and will be using for cm-12.1?
r3pwn said:
I'm interested in compiling cm12.1 and helping to debug the build process, however, there are so many device trees and kernel repos that I don't know which ones to use. Could you point me towards the ones that you use and will be using for cm-12.1?
Click to expand...
Click to collapse
shinru isnt in the dev scene anymore ,heres rbheromax's dev tree,he said its ready for cm12
https://github.com/rbheromax/android_device_htc_a11
pattyboi:) said:
shinru isnt in the dev scene anymore ,heres rbheromax's dev tree,he said its ready for cm12
https://github.com/rbheromax/android_device_htc_a11
Click to expand...
Click to collapse
Sweet, thanks. Which kernel branch should I use?
r3pwn said:
Sweet, thanks. Which kernel branch should I use?
Click to expand...
Click to collapse
He has a cm12 branch in his kernel source,that'd be ur best bet right now
pattyboi:) said:
He has a cm12 branch in his kernel source,that'd be ur best bet right now
Click to expand...
Click to collapse
I do? Hmmm guess I might as well keep working on it
pattyboi:) said:
He has a cm12 branch in his kernel source,that'd be ur best bet right now
Click to expand...
Click to collapse
rbheromax said:
I do? Hmmm guess I might as well keep working on it
Click to expand...
Click to collapse
I don't see one. All I see is 3.4.0-stable, 3.4.0-cm, 3.4.0-experimental, 3.4.0-nw, 3.4.0-stock, and 3.10.28-stable. I'm guessing you meant the 3.4.0-cm one, but the default branch is set to 3.4.0-stable.
EDIT: Yes, it is the 3.4.0-cm one.
r3pwn said:
I don't see one. All I see is 3.4.0-stable, 3.4.0-cm, 3.4.0-experimental, 3.4.0-nw, 3.4.0-stock, and 3.10.28-stable. I'm guessing you meant the 3.4.0-cm one, but the default branch is set to 3.4.0-stable.
Click to expand...
Click to collapse
It's the cm one my man,my bad thought it was labeled cm12
Related
[SIZE=+1]CM11 for LG L90 LG-D415[/SIZE]
Ok guys and gals... I must first state that this is not my original work. The CM11 base I'm building off of is all due to the hard work and efforts of @Quarx. His ROM is located here for devices other than the LG-D415.
This thread was created to assist @Quarx by not littering his thread with posts for LG-D415 devices. He doesn't own a D415, but I do :silly:
With that said...
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
[SIZE=+1]To use this ROM you MUST have an unlocked bootloader[/SIZE]
All specs with this ROM are the same as the specs with @Quarx ROM minus the fact that this ROM is built specifically for D415 devices
What's working
Bluetooth
Calls
Front camera
GPS
Mobile Data
Rear Camera
Superb battery life
WIFI
Most everything else
What's NOT working or working correctly
CM Updater ( Until I figure out how to implement my own )
Video recording ( front/rear camera. Works for some, not for others )
Video playback ( Works for some, not for others )
IR
LG Knock Code ( Double tap to wake )
Credits located in post #2
Changelog located in post #3
Download links are located in post #4
Source links are located in post #5
Installation
Boot to recovery ( Custom recovery required )
Wipe cache ( only required on first installation )
Wipe Dalvik cache ( only required on first installation )
Format /system and optionally /data ( Only necessary if coming from stock or a different ROM )
Install ROM
Install GApps
XDA:DevDB Information
CyanogenMod 11 for LG Optimus L90 ( LG-D415 ), ROM for the LG Optimus L90
Contributors
shinobisoft
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-10-15
Last Updated 2014-12-17
Credits and Thanks
Credits
@Quarx - For getting everything started for developing for the LG L90
@CyanogenMod - For CM11 obviously
@k2wl - For assisting with tips/hints/suggestions
@demonslayer12349 - For assisting with tips/hints/suggestions
@shoxxy - For Philz-Touch recovery for our devices. Also for helping "behind the scenes"
Very Special Thanks
@jran0880 - For his donation of $50.00
Changelogs
12/02/2014
No changes to note on my end. View CM's changelog for any changes/updates.
10/22/2014
Removed NFC again
Removed FM Radio again
There may be some OS changes thanks to the CM team. See their changelog for changes.
SELinux is still disabled in this build. Device doesn't seem to like it when it's enabled. LOL...
Something else to figure out
10/07/2014
Changed kernel configs and dtbs from W7_TMO_US to W7_OPEN_CIS. My first few builds were built using W7_OPEN_CIS. Seems to be fewer issues with those ROMs than my most recent.
Re-enabled NFC. I'm starting to think it does exist on the device.
Re-enabled FM. Strangley I can at least hear static now. So the hardware may actually be there.
Any other changes would be OS related and would be noted by CM in their changelog.
Enabled the "Quick Key", the button above volume keys, to wake the display.
10/04/2014
Removed most NFC related stuff. D415 doesn't have NFC
Removed FM Radio.apk. D415 doesn't have FM receiver
FIX - Correct camera drivers now load on device start up
FIX - Video playback drivers
Too many other changes over the last month to begin to try and remember. LOL
My last sync with CM may have had some fixes incorporated. About a week ago
09/10/2014 - There have been no real "changes" in any of my builds besides editing some config files and adding files to fully specify the device as a w7 device and not a w7ds device. The D415 is not a dual sim device which I believe was part of the conflict between @Quarx builds and the D415 devices. So with the 09/10 build as far as I have been able to determine, everything about the build now identifies the device as a w7 device.
Downloads
Newest build: 2014-12-02 Mirror: 2014-12-02
Previous builds:
2014-10-22 Mirror: 2014-10-22
2014-10-07 Mirror: 2014-10-07
2014-10-04
2014-09-10
2014-09-07
2014-09-04GApps: http://forum.xda-developers.com/showthread.php?t=2397942
Use the link above for PA-GApps for the moment. I will put together a GApps package eventually. LOL :silly:
Recoveries: ( flash with fastboot, an app like Flashify, or my LG L90 Utilities )
CWM 6.0.5.1 ( Swipe up/down to scroll. Swipe left to go back, Swipe right to select ) Factory Reset: DISABLED
Philz-Touch 6.57.5 ( Thanks to @shoxxy )
The TWRP 2.7.1.0 package attached to this post is flashable via recovery.
Sources
GitHub Sources
Device: https://github.com/shinobisoft/android_device_lge_w7
Kernel: https://github.com/shinobisoft/android_kernel_lge_msm8226
AV Frameworks: https://github.com/shinobisoft/android_frameworks_av
LG Proprietary blobs: https://github.com/shinobisoft/vendor_lge_proprietary
I must stress again that these works are based off of the works of @Quarx - [Rom][DEV][4.4.4] CyanogenMod 11 for LG L90
Awesome! Looking forward to continued development ...just curious anything fixed from the 9/4 build to the 9/7 build?
Sent from my LG-D415 using Tapatalk
slamdunksaliby said:
Awesome! Looking forward to continued development ...just curious anything fixed from the 9/4 build to the 9/7 build?
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Probably not. I've only been building with my fixes on top of @Quarx sources on GitHub. I'm still trying to get everything of mine over to GitHub at the moment. I unfortunately have a full time job so I don't have a ton of free time. The weekends are usually the only free time I have. I overslept today and decided to play hookey for the rest of the day. LOL. Imma bad bad boy LMAO.
When I get settled in to GitHub and have a chance to really check out the source code, I'll then see what I can do.
shinobisoft said:
Probably not. I've only been building with my fixes on top of @Quarx sources on GitHub. I'm still trying to get everything of mine over to GitHub at the moment. I unfortunately have a full time job so I don't have a ton of free time. The weekends are usually the only free time I have. I overslept today and decided to play hookey for the rest of the day. LOL. Imma bad bad boy LMAO.
When I get settled in to GitHub and have a chance to really check out the source code, I'll then see what I can do.
Click to expand...
Click to collapse
Haha no worries thanks so much
Sent from my LG-D415 using Tapatalk
Nice thing to see coming here tonight!!!! You're the best![emoji2] [emoji4] [emoji2]
Sent from my LG-D415 using Tapatalk
shinobisoft said:
Probably not. I've only been building with my fixes on top of @Quarx sources on GitHub. I'm still trying to get everything of mine over to GitHub at the moment. I unfortunately have a full time job so I don't have a ton of free time. The weekends are usually the only free time I have. I overslept today and decided to play hookey for the rest of the day. LOL. Imma bad bad boy LMAO.
When I get settled in to GitHub and have a chance to really check out the source code, I'll then see what I can do.
Click to expand...
Click to collapse
Hey bro well i found your repo i was wondering are you going to set it up to where their will be your own device tree kernel etc? I also have d415 and would like to use this as a base and see what i can do to help get some things working/test and share.
I have built from the most recent source via Quarx repo however it still has all the issues with wifi, gps, and camera some of which you have gotten to work, may I ask what you altered to get those working?
toxinburn said:
Hey bro well i found your repo i was wondering are you going to set it up to where their will be your own device tree kernel etc? I also have d415 and would like to use this as a base and see what i can do to help get some things working/test and share.
Click to expand...
Click to collapse
Eventually. Don't fork anything yet. I've gotta change a few things at github.
Sent from my LG-D415 using Tapatalk
shinobisoft said:
Eventually. Don't fork anything yet. I've gotta change a few things at github.
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
heheh of course i already did but no worries.
thanks! This is so much faster than stock ROM. Stock ROM used to redraw UI every time i stay in an app for a bit.
toxinburn said:
... may I ask what you altered to get those working?
Click to expand...
Click to collapse
Sure ,you can ask but I'll never tell. LOL. Just kidding.
It's actually kinda long winded tho and I'm not sure I can explain exactly what needs to be done. It will be easier for me to fix my GitHub and have you fork from it than to explain everything in enough detail to understand what needs to be done.
I'm just getting in from work. Hopefully I can have my GitHub repaired in the next couple hours
Just want to say thanks to you (for the D415 version) as well as Quarx for supporting this phone! I must say this L90, even with the stock ROM, was the best $50 I ever spent. I am still discovering features on this phone that I had no idea were even on here, such as NFC, infrared remote, and even the flashlight (yeah, I really thought this didn't have a camera flash until I launched the Torch app). But now to see this phone with CM11 just makes it that much better of a deal. Other than the front camera currently not working, which is fine for me since I never use it anyway, this ROM is absolutely fantastic and is twice as fast as the stock LG ROM.
Keep up the good development work! If you have any experimental ROMs, kernels, or any other mods, please let me know and I will be happy to test them. This is a great little phone for the price tag, and I'd love to see the development blossom for this thing.
Sent from my LG-D415 using XDA Free mobile app
1) Happy Birthday to me :silly:
2) I'm doing a test build now to see if I managed to fix what I broke last night. LOL
3) If #2 is successful, then I'll upload my kernel sources to GitHub for those who are interested. Then I'll also post a link in the OP to my GitHub for CM11.
Cross y'alls fingers and toes! No eyes please!!! LMAO...
shinobisoft said:
1) Happy Birthday to me :silly:
2) I'm doing a test build now to see if I managed to fix what I broke last night. LOL
3) If #2 is successful, then I'll upload my kernel sources to GitHub for those who are interested. Then I'll also post a link in the OP to my GitHub for CM11.
Cross y'alls fingers and toes! No eyes please!!! LMAO...
Click to expand...
Click to collapse
happy birthday !!!!have a great day!!!
shinobisoft said:
1) Happy Birthday to me :silly:
2) I'm doing a test build now to see if I managed to fix what I broke last night. LOL
3) If #2 is successful, then I'll upload my kernel sources to GitHub for those who are interested. Then I'll also post a link in the OP to my GitHub for CM11.
Cross y'alls fingers and toes! No eyes please!!! LMAO...
Click to expand...
Click to collapse
Sorry for OT
HAPPY B-DAY !!!! stay healthy
Ok. I got it to build. It flashes and boots just fine. But... I'm having one heck of a time pushing my kernel sources to GitHub.
The kernel sources are where most of the changes/additions I've made are. Without them the rest of the project is useless. LOL. I'm not sure if the issue is my wifi adapter or the wifi router I'm connected to but I keep getting kicked off during an upload. Sometimes I can get it to resume but never long enough got it to complete the upload. Grrrr...
All sources are now on GitHub. Source links are in post #3
EDIT::
New build up. See post #2
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.
Hey guys
In memory of a very dear friend who passed away yesterday, I am starting this thread and a new era for our x3.
CM has pushed their CM13 branches yesterday, which means it's time for a new project. This time, though, I will be all by myself.
Please do not expect any miracles soon, as the M sources still need to settle a bit before we can even hope for a halfway working build.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, which we will most likely merge happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let me/us know about it before you release it and give proper credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
Most likely everything
Working:
Most likely nothing
Now, the most important part:
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[DEV] [WIP] Unofficial CM13 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-10-06
Last Updated 2015-10-06
Reserved
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
I will pay you, just please make final ROM for 4X, with everything working as it shoud be! That would be awesome!
Wysłane z mojego LG-P880 przy użyciu Tapatalka
I will pay you too. I would like when I will be to have the final ROM fo 4x. Thanks
Make it working relibly and responsively, and I will pay you too. You deserve it!
I don't mind if it takes months to achieve it. Just make it at some point, and I'll be happy!
Can't wait !!!
ps. i'm sorry for your friend
laufersteppenwolf said:
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
Click to expand...
Click to collapse
I'm also waiting for complete bringup tried for daily driver... failed. If you need help just send me message on hangouts/mail
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
SHM said:
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
Click to expand...
Click to collapse
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Some days ago is builded a cm13 ZIP, but it doesnt even pass bootloader.
Here are my commits for device tree. I disabled most likely everthong what causes building errors like Audio and CameraWrapper.
Here are my commits https://github.com/lenzwagner/android_device_lge_p880/commits/cm-13.0
@laufersteppenwolf will be on IRC the next evenings. Hope you'll be there too.
---------- Post added at 07:45 PM ---------- Previous post was at 07:40 PM ----------
laufersteppenwolf said:
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Click to expand...
Click to collapse
They fixed it some days ago.
Look here:
1. http://review.cyanogenmod.org/114239
2. http://review.cyanogenmod.org/114277
3. http://review.cyanogenmod.org/112338
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
laufersteppenwolf said:
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
Click to expand...
Click to collapse
If you find time, i'm on IRC atm
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
edit: eh, those commits have already been merged so problem still persists.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
fritzcola said:
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
Click to expand...
Click to collapse
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
SHM said:
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
Click to expand...
Click to collapse
Weird cause i just compiled a build with no errors.
fritzcola said:
Weird cause i just compiled a build with no errors.
Click to expand...
Click to collapse
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
fritzcola said:
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
Click to expand...
Click to collapse
No sir I am not. For another device, forgive me if that caused any confusion. My initial post on here was with regards to ffmpeg. A hunt for an unofficial build on xda brought up a few links and so wanted to make contact with the dev(s) to see if they had the same problem and/or fix so I may compare and possibly adapt if applicable my previous outcome. As for my current issue I do not expect any answer or results from here since its completely off topic from this device. I merely shared it in response with no intention or expectations for a solution. . I did take a look at your repo and saw ffmpeg is obsolete so I removed it from my tree as well since it was most definitely causing my builds to break.
any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
Arjunfire said:
any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
Click to expand...
Click to collapse
you can make
I think he asked that because he cant do this. But I think it is only a matter of time until something will be released. At least I hope so.
I want it
Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:
rayzen6 said:
Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:
Click to expand...
Click to collapse
I think there will be no drivers for Spadragon 800/801...?
Athanatos81 said:
I think there will be no drivers for Spadragon 800/801...?
Click to expand...
Click to collapse
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .
I hope stil working on s5 sm g900f
Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...
rayzen6 said:
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .
Click to expand...
Click to collapse
Yup but i guess it can be done without vulkan api. As in nexus 4 port.
kardinal969 said:
Yup but i guess it can be done without vulkan api. As in nexus 4 port.
Click to expand...
Click to collapse
That's what I said brother
freibergisch said:
Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...
Click to expand...
Click to collapse
it is possible to update drivers for gpu if you have an unlocked bootloader and are on mm aosp rom
Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte
Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
chippinganimal said:
Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte
Click to expand...
Click to collapse
They should
Paoletti said:
Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
They should
Click to expand...
Click to collapse
Alright, got ubuntu installed (windows partition had a heart attack afterwards lmao) so now Ill do my best to follow that guide and see what happens i guess... Should build pretty fast since this machine has a i7 3770 and 16gb of ram and it seems the guide says 8gb of ram is fine.
Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?
chippinganimal said:
Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?
Click to expand...
Click to collapse
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up
Paoletti said:
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up
Click to expand...
Click to collapse
This is a git thing. Basically the branch name has changed. It's now in the staging branch so:
-b staging/cm-14.0
Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613
rayzen6 said:
Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613
Click to expand...
Click to collapse
We want to try that build, beta, alpha or wathever it is. We just want to try it, feel nougat in our hands, we want a download link for that build, even if it isn't stable, daily usable and public. We want that, we must have that.