Hello everyone!
I finally got a build environment working. Originally this started out with wanting to have CAF CM for my phone and to start building myself because I've heard that CAF can allegedly be better than pure AOSP (although granted the effect may be purely homeopathic, but while I'm at carving my own customisations, may as well take something extravagant), so I started these builds as practice for future projects and am sharing the results with you. The main goal is to stick as close to the original builds as possible, but introduce minor tweaks and changes that may improve the user experience indirectly from various sources (while hopefully maintaining the ability to flash back and forth between my builds and official. No guarentees)
I will aim for a monthly build cycle (or when I feel like building) rather than building nightlies, since I don't have a build bot nor the time to do builds that frequently.
Expect to see builds in a two-weeks interval at the very least, monthly at the very most. I'll keep these builds up as long as I see any usefulness in having this particular constellation since I've started it pretty much only because I wanted to fill in a gap and to also have the freedom of even more control over my phone.
Disclaimer:
I DO NOT GUARENTEE A CONTINUOUS BUILD CYCLE. YOU MAY HAVE TO FLASH BACK TO CM OFFICIAL IN ORDER TO GET UPDATES IF I HAVE TO RETIRE THESE BUILDS. I CANNOT ASSIST YOU WITH BUGS OR CRASHES AS I HAVEN'T CODED ANYTHING IN THIS BUILD. THIS IS SIMPLY A SHARE. THESE BUILDS ARE PROVIDED AS-IS WITHOUT ANY GUARANTEE THAT THEY WORK. THEY ARE TESTED AND USED AS DAILY DRIVERS, HOWEVER I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE IN ANY MANNER. WHAT YOU DO WITH YOUR PHONE IS YOUR THING. IF YOU B*LLOCK IT UP THEN THAT'S YOUR PROBLEM.
CM14 Info:
Even against my predictions, there is even a CAF version again, so I'm sticking to that like on CM13. The edits made to the ROM will be the same as the CM13 CAF version. As of 23/11 I've become inspired to experiment with a few cherry-picks of features I find useful or have been requested. What you get in the package is:
Minimal cherry-picks without a bloat of features that noone uses cluttering up the settings (list coming up once the experiments are done, current version is still pure CM14.1, scroll down to the more recent pages of the thread to see what I'm planning)
Mods under the hood preinstalled that came to be included through my laziness while updating my phone, for now just SELinux V4A support and stereo audio output (suggestions welcome)
A better kernel than CM stock if I happen to stumble over one. This one is more a "could be".
An actual OTA mechanism through a modded CMUpdater if enough people end up using the ROM and start donating to me (I can't afford a server).
The petty cosmetic change that is having it say "Nexus 5" in the "About Phone" section instead of "Nexus 5 CAF". Was just a finger exercise in the beginning of my work.
Some more Info:
I am not an actual developer yet and just getting familiar with building from source, over cherrypicking to eventually creating my own ROM from scratch. Therefore I cannot squash any bugs yet, even though I would love to. Yes, I'm a noob. If a bug disappears then that's purely because the guys whose open source code I'm using fixed it brilliantly. I do not take any credit for fixed bugs since I know as much about programming Android as a politician knows about keeping their promises: I know it could be possible, but it's not happening (yet).
Please do not clutter this thread with any bugreports. That don't seem related to my changes (i.e. random reboots when a new kernel is being tested). If you spot a bug then tell the actual developers. However if you stumble upon something that would benefit this ROM that isn't a feature (like an even better kernel or some other cool thing) then please do tell me (PM preferred) or if any mod I introduced is giving you trouble, sound off here in this thread.
I've already mentioned it, but I like to stress it again: There is no guarantee that builds work. I'm playing around with things and at some point things may go "BOOM" and be broken until I fix it. So far the builds have all booted up and operated just fine under a daily driver condition, but this may change for one or the other new build that I'm putting out. It's a risk I can't eliminate. We're working on the cutting edge here, you see. Either be in for the adventure or play it safe and decide that my ROM isn't for you. Nightly stays Nightly for a reason.
The V4A stuff is a pretty dirty hack that removes a whole bunch of neverallow policies in order to have the mediaserver policy that V4A requires in order to work. That means a huge sacrifice in security. But:
Your phone is already rooted to the teeth when you have installed CM basically, which when we get real makes it pretty easy for rogue apps to go wild if you grant root access to the wrong apps. SELinux enforcing wouldn't make much of a difference. One command and SELinux is in permissive mode allowing all naughty stuff.
I can't tell if you will have to wipe your device when updating to the cherry-picked builds once they are out or when flashing back to official CM14.1. You'll just have to make a backup and try.
Downloads:
Last legacy CM13 build: 28/09/16 codename "Debuggering"
https://drive.google.com/folderview?id=0Bw-aZKY98vPCcG5wRmE3UWlaYVU&usp=sharing
CM14.1 20/11/2016 codename "Renaissance":
https://www.androidfilehost.com/?fid=385035244224399989
Alexandroid0.1 codename "HelloWorld" (EXPERIMENTAL!):
http://forum.xda-developers.com/showpost.php?p=69960899&postcount=203
Requirements:
Radio / Baseband: M897A-2.0.50.2.30
Bootloader: HHZ20h
Screenshots
https://imgur.com/a/I0FB8
Installation:
CM14.1 Installation:
Install TWRP hammerheadcaf
Wipe /data (without internal storage if you like), /cache & /system if coming from an incompatible ROM
Flash zip
Flash Gapps from opengapps.org
Perform a rain dance
Profit
CM14.1 BUGS:
Lol which bugs?
Sources and Credits / Special Thanks:
CyanogenMod (ROM source):
http://github.com/CyanogenMod
http://github.com/CyanogenMod/android_device_lge_hammerheadcaf
http://github.com/CyanogenMod/android_device_lge_hammerhead
http://github.com/CyanogenMod/android_device_qcom_common
http://github.com/CyanogenMod/android_kernel_lge_hammerhead
https://github.com/Alexandroid99/android_device_lge_hammerheadcafTheMuppets (vendor blobs): http://github.com/TheMuppets/proprietary_vendor_lge
Fix for repacking CM14 ZIPs to flash in MultiROM DIY
1) Extract the zip
2) Navigate to META-INF/com/google/android/
3) Open updater-script in a good text editor (No, notepad.exe is not a good text editor)
4) Clear the file completely and copy&paste this:
Code:
ui_print("ALEXANDROID CM14 MULTIROM REPACK!");
ui_print("NOW INSTALLING, YOU MAY SUCK YOUR THUMBS MEANWHILE");
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
unmount("/data");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ui_print("DISPENSING CAKE IN THREE TWO NONE");
show_progress(0.200000, 10);
ui_print("YES I KNOW THAT MEME IS WAY TOO OLD");
set_progress(1.000000);
5) Pack everything you extracted back into a ZIP.
6) Flash and profit!
Thank you so much!! Just showed my gf, who's a biiig Portal fan. Guess her reaction!
I'll quote...:" darlin' , get me that freakin AWESOME cR on my nexus or I swear I'm gonna get you baked"
Hehe don't even know what that means xD
it is quite stable enough for daily ? thanks
Junnie said:
it is quite stable enough for daily ? thanks
Click to expand...
Click to collapse
I am using this as a daily driver coming from AOSP CM13 and it's actually more stable than the official variant so far. Before I had multiple systemui restarts on a daily basis with random freezes and soft reboots (some of which resulted in a bootlooping until I forced a full reboot). Battery life has been quite OK, my current usage has gotten me through my entire workday of about 4 hours without having to recharge, even though it was running a VPN to my home network so I could SSH into my PC for kicking off another build. Give it a shot if you like, but do make a backup of /system /boot and /data before you upgrade from CM13.
Doctor w said:
Thank you so much!! Just showed my gf, who's a biiig Portal fan. Guess her reaction!
I'll quote...:" darlin' , get me that freakin AWESOME cR on my nexus or I swear I'm gonna get you baked"
Hehe don't even know what that means xD
Click to expand...
Click to collapse
Yeah, the hostname of my PC is GLaDOS on my network. Maybe for the lolz I will create a user just for building named "CJOHNSON". Enjoy the build. New one with updated kernel coming soon.
Alexandroid99 said:
I am using this as a daily driver coming from AOSP CM13 and it's actually more stable than the official variant so far. Before I had multiple systemui restarts on a daily basis with random freezes and soft reboots (some of which resulted in a bootlooping until I forced a full reboot). Battery life has been quite OK, my current usage has gotten me through my entire workday of about 4 hours without having to recharge, even though it was running a VPN to my home network so I could SSH into my PC for kicking off another build. Give it a shot if you like, but do make a backup of /system /boot and /data before you upgrade from CM13.
Click to expand...
Click to collapse
thanks for your kindly feedback devs im using your build right now , so far its quite good and stable... and also its battery lol..
my phone keeps cool at itself not doing overheat :good: can i make one request devs if you dont mind ??
can you add DT2W to your kernel ?? thanks .. add more goovernor also hehehe... keep up the good work , i like PURE AOSP CAF like this..
Junnie said:
thanks for your kindly feedback devs im using your build right now , so far its quite good and stable... and also its battery lol..
my phone keeps cool at itself not doing overheat :good: can i make one request devs if you dont mind ??
can you add DT2W to your kernel ?? thanks .. add more goovernor also hehehe... keep up the good work , i like PURE AOSP CAF like this..
Click to expand...
Click to collapse
Thanks. Well, dt2w would be included in the version with RACER kernel instead of pure myfluxi CAF, unless I decide to fork the kernel itself and add the appropriate cherry picks. Though since there is already all this good work out there, I'd rather rely on RACER and add patches and cherry picks to it if anything I like is missing. You can already try out this build with RACER kernel, either the version that is based on the official CM CAF or the myfluxi CAF version (I would stick with the myfluxi version, since he appears to be very good at creating things for hammerhead).
New build is up. Don't forget to backup all important partitions before you flash, in case something failed to compile properly rendering the new build broken.
Alexandroid99 said:
New build is up. Don't forget to backup all important partitions before you flash, in case something failed to compile properly rendering the new build broken.
Click to expand...
Click to collapse
Thanks Devs for maintaining CAF on our nexus 5 :highfive: keep up the good work , and dont forget to pay attention on your real life :good:
Junnie said:
Thanks Devs for maintaining CAF on our nexus 5 :highfive: keep up the good work , and dont forget to pay attention on your real life :good:
Click to expand...
Click to collapse
Pff I already said in the disclaimer; I don't code anything of this. I just build it. Only takes a bit of fixing a few errors and then waiting 3 hours for the compilation to complete. Lol
If you want to thank the developers, speak to @myfluxi or the responsible maintainers of CyanogenMod.
In test two days, it is working very well and no reboot :good:
Thank you for building this great Rom! But i have one question, does this Rom/Kernel support f2fs out of the box?
hello all i just want to ask one question , everyone facing problem on data network ?? this happening on every CAF ROM for nexus 5 i've tried...everytime i reboot my phone data network wont active automatically , i must put into airplane mode , enable and renable data network till it active...any tweaks or init.d or something ??? when i tried non caf rom its not happening,thanks.
I just bought a Nexus 5 (it's not even here yet), but could someone point me as to what the benefits are to flashing CM 13.0 versus the stock 6.0.1 update? The main reasons I use CM on my current phone is that I want the new software, better security, and de-bloated. I understand that Nexus devices do all that the way they come. Are there like added features with each ROM? I do like CM themes, but they aren't THAT important to me. Thanks.
ocarinaz64 said:
I just bought a Nexus 5 (it's not even here yet), but could someone point me as to what the benefits are to flashing CM 13.0 versus the stock 6.0.1 update? The main reasons I use CM on my current phone is that I want the new software, better security, and de-bloated. I understand that Nexus devices do all that the way they come. Are there like added features with each ROM? I do like CM themes, but they aren't THAT important to me. Thanks.
Click to expand...
Click to collapse
Of course there are! Ranging from small ones that you will grow used to very quickly and forget about they don't exist in mainstream Android to the big ones, like the theme engine. But really, you could have used google or the Q/A section for that. Please keep this thread clean.
Hi there, good to hear that CAF-Builds will continue. Thanks for that!!!
I really prefer CAF over the AOSP CM13 Builds for daily driving.
I hope there will be again an official maintainer for CAF-Builds soon at cyanogenmod!
Just two Questions:
- Do you have plans to integrate a custom or modified updater for your builds? <--That would be really cool for updating the builds!
- What is the difference between your build an this one from user "phoval". <-- Maybe you can work together and share the work!?!
Is the low recording volume in WhatsApp and other apps still an issue? Sound playback is awesome on CAF, recording not so much...
Moscha said:
Hi there, good to hear that CAF-Builds will continue. Thanks for that!!!
I really prefer CAF over the AOSP CM13 Builds for daily driving.
I hope there will be again an official maintainer for CAF-Builds soon at cyanogenmod!
Just two Questions:
- Do you have plans to integrate a custom or modified updater for your builds? <--That would be really cool for updating the builds!
- What is the difference between your build an this one from user "phoval". <-- Maybe you can work together and share the work!?!
Click to expand...
Click to collapse
Very good and productive questions there, thanks for that. Well, I am planning on modifying the CM Updater so it checks my own webserver for updates. However this will require me to reverse-engineer it first in order to understand how it works. If I can't manage to do that, maybe I will create one from scratch (I should start developing apps for Android anyway). I'll put this point on the upcoming list because I've been considering it. Again, thank you.
As for your second question, the difference is that my builds include a kernel compiled straight from @myfluxi 's github repos as opposed to the mainstream CM13caf github version. I've heard that myfluxi is very skilled at working with hammerhead (I think he was an official maintainer at some point?), so I opted for that instead. Even the custom kernel RACER offers a CAF version that is based on myfluxi's repository. So basically it already includes in some way a custom kernel that is optimised for this device (and very pleasantly stable so far, I am using my own builds myself and it's been just wonderfully reliable for me).
There will also be another change, which is already in the upcoming list: custom toolchain UBERTC. I won't get into detail on that, as I've already explained that one in the head post in a bit and a Google search will give you the answers within less that five minutes anyway.
Junnie said:
hello all i just want to ask one question , everyone facing problem on data network ?? this happening on every CAF ROM for nexus 5 i've tried...everytime i reboot my phone data network wont active automatically , i must put into airplane mode , enable and renable data network till it active...any tweaks or init.d or something ??? when i tried non caf rom its not happening,thanks.
Click to expand...
Click to collapse
anyone ? please ?
Related
[Q&A] [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Q&A for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
nikudim said:
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
Click to expand...
Click to collapse
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
ronasimi said:
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
Click to expand...
Click to collapse
Oh, you won't believe I just disable "Don't keep activities" and it works now!!!:laugh:
The problem was when i tried to put Clock for expl. the launcher crashes and appearing again without my widget. Now, i've put my widgets and turn on "Don't keep activities". Perfect! I could not spot any problems, yet!!! Good luck with developing, and thanks again!
ronasimi said:
02/03/2015 - Sorry guys, I've been slacking off on updating this post. All current builds are using my KK kernel brought up for LP, with stock frequencies instead of low_cpuclocks. I'll be posting a new build later this morning. As far as I know, this is the only CM build still using mako sources
Click to expand...
Click to collapse
Noticed this over here after looking in the Canadian section (which has most certainly be dead for a while). Great to see you're still active on this. Just want to make sure before trying this that there's nothing else required to move from KK to LP (assuming not since its on a KK kernel still). Any particular recovery recommended and/or version? I'm on a Bell E973 using PAC 4.4.4-RC2, TWRP 2.6.3.1.
Edit: Decided to update recovery to 2.8.4 from brothaedhung after doing some lurking around. Flashed 02/03 and full stock PA gapps. Everything butter so far. Cheers!
@ronasimi : Latest build is working fine, in call screen is also normal, just sensors not working some times,,
thanks..
Click to expand...
Click to collapse
I have the same issue in your latest CM12. Proximity and brightness don`t work at all. I use jb e970 modem. Don`t flash hybrid radio because I`m in Russia. Also there isn`t any frequence low than 300 Mhz...
And I try your build of CM11: 20141111. There are a lot of bugs:
1. In profiles doesn`t work ring mode "normal". It doesn`t swith to it after another modes (vibrate and mute).
2. Don`t work "Double tap to sleep"
3. In perfomance dont`t work setting minimal and maximum frequency - after rebooting they are turned to default.
I have e970 will it work with this rom?
dro3 said:
I have e970 will it work with this rom?
Click to expand...
Click to collapse
It works. You should give a try to the CM12.1 version. :good::good::good:
ryupunk said:
It works. You should give a try to the CM12.1 version. :good::good::good:
Click to expand...
Click to collapse
I have tried it but my phone gets signal lost many times
"ap watchdog bark detected"
Help!
Since i flashed 12.1 rom, this message with green screen appears frequently!
5.1.1 CM12.1 Unofficial, Watchdog Kenel Panics (green screens)
long post, so if you want the meat of the story scroll down!
hi guys, i'm an avid user of the e970 and i found this marvelous forum to be one of the most useful resources ever. freegee, lgnpst for when i bricked my phone, cm11, cm12, solid geeb kernel, validus, and now cm12.1 unofficial; it's all there. i'm certainly enjoying the experience that this device paired with this community has to offer.
first i'd like to thank the developers, and i'm seriously appreciating the active development on 12.1. i just finished using validus and while it was a much more solid experience than the short-lived cm12, android 5.0 was still killing me in terms of battery life. 5.1 certainly fixed that up though.
i want to second a few observations that are being made, which are the green-screen happenings. i want to mention something in particular though:
when i first flashed 12.1 unofficial i didn't have the recommended gapps at the time, so i flashed the minimal gapps for 5.0 (just to get wheels rolling per se). sure enough, it was a crazy experience. com.google.<insert service name here> was crashing repeatedly, often causing loss of functionality or green-screens. in a day i'd get anywhere between 4 and 7 green-screens (this was for three days, i'm talking about the 4/21 release). i re-wiped and formatted /system and re-installed 4/21 cm12.1, along with the recommended gapps this time.
NOW i'm having far fewer crashes, far fewer slow-downs and stutters; overall a much more lean experience. i also want to especially thank the developer for one thing: THANK YOU, for giving me back HSPA+ speeds on my att jb radio. validus and cm12 for some reason wouldn't give me HSPA speeds, just slow HSPA speeds that would take forever to peak at 200, 250 K/s (averaging around 70 to 140 K/s). now i can enjoy speeds up to 900 K/s (i'll run a speed test when a more stable release comes out)
so, is it gapps or a kernel issue? newer gapps reduced a lot of problems (though that's a given). also i'd like to point out another error: wi-fi. the mac address keeps changing upon reboot, namely the last three hex values. the first three are always 00:11:22. this wouldn't bother a lot of everyday users, but my workplaces utilizes mac filtering (only way around it is to use the battery-intensive 3g option instead, and i have terrible 3g reception at work where i sit; OUTSIDE my office, i get great reception, but it's bloody hot here x.x)
in any event, if someone could help me out or give me some advice that'd be great.
to summarize:
5.0 gapps + cm12.1 = lots of watchdog events
5.1 gapps + cm12.1 = a lot LESS watchdog events, still happening though
wi-fi mac address gets randomly generated at reboot
phone doesn't get detected by the computer on usb unless you leave it plugged in and do a soft reboot (advanced reboot option; common in most cm12.x instances with default kernels; solid geeb was better, and cm11 was flawless pretty much)
using built-in kernel
att jb radio
clockworksmod touch recovery, the last one (6.0.1.8 i think? it's the last one on their website)
4 gig micro sd card is in the slot, if that makes a difference
one more note: i'm having far fewer crashes on this new install maybe because there are only google related apps (other than whatsapp which i installed right away). future planned apps to be installed:
adobe acrobat
battlenet authenticator
es file explorer
facebook messenger
titanium backup
mx player
aedict japanese dictionary
busybox
greenify
orpheus music player
qr code reader
skype
supersu
terminal emulator
any increase in instability henceforth i'll let you know. also for anyone NOT having greenscreens on the e970, do you have whatsapp? if NO, interesting. if YES, still interesting, but please what version? mine's not the latest (yet)
blitz9826
so this is new:
after reaching 100% battery level on charge, the phone used to cool down. ever since switching to this rom, the battery DOESN'T cool down, it stays warm/hot. i know for a fact it's not a charger issue since i'm charging it with the same usb port as i have been in hte past (and every other phone for that matter on the same port)
any ideas?
blitz9826
sensors
Sensors isnt working. 28.04 build.
Will you fix it?
Icons are blurry?
Hey. Loving this ROM so far. Only problem is that the icons are blurry (not HD as usual). I wiped the cache and delvik cache but it's the same problem. Anyone know how to fix this? Thanks.
ronasimi, i am waiting, that you will read this. Please try to fix sensors in your unofficial 12.1 builds. I really want use your rom, but sensors is not working.
I have e970 with mako z30f bootloader, and latest twrp.
Auto rotation
The auto rotation is not working. Only staying in portrait. Can anyone help?
Mobile Data to Wifi Switching
@ronasimi
first of all thanks for the Great rom im using from almost a month with no issues at all.
Just a little question about wifi. Wifi did not connect automatically when my phone is locked. I've to wake it then WiFi connects immediately.
same is when im using mobile data and saved WiFi is in range. but phone will connect it,until i wake the device.
please help me out on this.
[SOLVED] Problems rooting 12.1 E971
Edit: For anyone else facing this issue, flashing the beta version of SuperSU from a custom recovery works.
On a previous 12.0 build I was able to get root just fine, but after clean flashing the latest 12.1 build no method seems to work. I've tried flashing the latest SuperSU update zip from TWRP, using adb to push su and busybox, and using the built in root in developer options.
Flashing the zip and using adb result in SuperSU saying there is no binary installed, and with the root in developer options it never pops up something asking for permission.
Has anyone gotten root on the latest 12.1? Thanks in advance.
Cm 12.1 Bluetooth Issue on E971
Thanks for the great rom. Works great except one minor. Bluetooth connection on and off consistently.
I have cm-12.1-20150521-UNOFFICIAL-geeb.zip rom installed.
Thanks!
Thank you for your hard work on the ROM.
On an E971 with a clean flash, as others above have reported, the sensors/auto rotation are not working.
Another request would be to add repo specifics on your description of the ROM at the start of the thread. You link to your github account where the repos are stored but there are many of them, some with similar names. I am interested in reproducing your build process and possibly contributing some changes, but I am not sure which specific device, vendor and kernel repos you are using to generate the build. Would love to get rotation sorted out and keep development going on this solid 5.1 option for a still capable device.
Still kind of suprised that CM isn't doing 12.1 builds for E973/E971 but it seems they have dropped a large number of phones with the move to 5.0/5.1 and angered a lot of people.
Thanks!
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
STATS: 500+ kernel downloads in 2 days, wow!
RELATED: Make sure you check out my TRIM-enabled kernels updated with the FPBug fix.
UPDATE: A fix for FPBug has been merged into CyanogenMod's cm-11.0 branch! The fix has not made it to the stable/cm-11.0 and cm-12.0 branches yet. Changes: this one and the previous 12. Commits: this one and the previous 12. The 20150111 nightlies are the first official CM 11 nightlies to incorporate the fix.
A little bit of history
As Android got more complex, the effects of this bug grew more visible, to the point of making the platform completely unstable for some users. Complex apps would fail for no reason, GSM, 3G and WiFi connectivity would randomly be lost, music playback would stop and require a reboot, camera would fail, internal storage and SD cards would become inaccessible, installed apps would disappear, users would experience battery drain issues ranging from inability to enter deep sleep all the way to phones becoming very hot, and the list goes on and on.
These failures all seemed unrelated and their cause was very hard to track down. Partly because events happened randomly and were not reproducible, but mostly because the bug undermines the very assumptions programmers deal with when creating any kind of code. And so years passed and the common cause of all this pain was never identified. Many ROM developers abandoned the platform out of frustration.
Then finally this past March, when analyzing the random loss of access to storage, user cgx observed a corruption event for the first time, and a connection between all these unrelated issues, sometimes hypothesized, was suddenly found. The corruption seemed to have happened in the stack, but it was later suspected then confirmed that the corruption actually happened directly in the registers of the floating point unit of the CPU. Yet processes that did not use floating point at all were also affected, because the GCC compiler typically spills registers into the FPU and uses FP and NEON instructions for optimization.
These findings allowed the creation of a stopgap fix for the "music bug" that shielded the FUSE process (which manages access to storage) from corruption in the FPU. The fix was widely applied and effectively eliminated all bugs resulting from sudden loss of storage access and returned the platform to pre-Android 4.3 stability levels: ie, sort of stable enough to be used as a daily driver. Later a working detector for the elusive bug was made and it was confirmed that all kernels since Gingerbread were affected (a thing that was already suspected given that the FirefoxOS people had described similar symptoms in 2012 under stock Samsung ICS). Finally enough of a root cause was hypothesized and a fix was worked out. And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
A short description of what the fix does can be found here.
Update
User zeitferne worked non-stop throughout this weekend and made amazing progress. He found a couple of missing commits that are apparently needed for the FPU state tracking to work through power state changes, he discovered that the FPU in CPU0 is the one that actually gets the corruption, he found an explanation why this bug never affected the 4412 platform (Galaxy S3, Note 2, etc), he narrowed down the conditions for the corruption, and finally output an alternative patchset that apparently fixes the FPU state restore optimization rather than just disabling it as mine does.
Kernel developers are encouraged to merge his changes in lieu of mine once enough testing is done and @zeitferne green-lights the patches. This is important as it might fix as-of-yet undetected bugs or prevent bugs arising from future changes. In the meantime, eager maintainers can merge my fix which is by now well tested. Users will only see a small (<< 1% ?) performance increase with zeitferne's patchset and don't really need to bother with this; my advice for them would be to wait for the changes to trickle into their kernel of choice. AMAZING JOB ZEI!!!
2nd UPDATE: @zeitferne has green-lit his patchset! Kernel maintainers merging it please take note: 1) Make sure my fix is removed before applying his, otherwise there will be a small performance hit in the resulting kernel. 2) Both our fixes also affect the 4412 platform (i9300, n7100, etc) in slightly different ways, and the effects of this have not been properly tested. I must recommend that some testing be done before distributing FPBug-fixed 4412 kernels. Please report your test results back to this thread.
WARNING: A problem was reported with zeitferne's patchset.
FOLLOW UP: @zeitferne made some changes to his patchset and initial testing looks good.
AND FINALLY: The patchset was merged into cm-11.0! (See this change and the 12 previous ones.)
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here. These kernels are guaranteed to work only with the exact matching version of CM specified in the last part of their filenames. But in reality they should work with most versions of CM that are close enough. (Don't ask me about this, I don't know, I don't even have any of these phones! Just try them and see for yourself if you are feeling a little adventurous.) For other ROMs i expect this fix to be merged in a matter of days after some more testing is done. Please be patient, and KitKat users can flash my music bug fix in the meantime.
FAQ
Q. I have flashed your music bug fix in the past. Can I flash your kernel?
A. Yes! The music bug fix has no downsides. In fact, as a side effect, that fix makes your phone slightly faster and saves some battery so it should be merged in all ROMs IMHO. If you already have it installed leave it in place, but do not flash it again the next time you upgrade the OS. Please do not flash it just for the sake of optimization: since it is based on CM11 M10, it would actually be a downgrade.
XDA:DevDB Information
FPBug-i9100, Kernel for the Samsung Galaxy S II
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2015-01-14
(reserved)
Is the BLN included ?
Lanchon said:
And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
Click to expand...
Click to collapse
It's not about i9100 ? Right ?
Can't wait till testing is complete and you merge the fix into your trim kernel for the i9100 lanchon. Thanks to all the programmers, testers and commenters in the bug thread for their hard work.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
yes, he refers to the i9100 and the n7000
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
these are all standard CM kernels. please request features on the CM thread.
Lanchon said:
yes, he refers to the i9100 and the n7000
Click to expand...
Click to collapse
Oh God ! Lollipop
I am anxious
@Lanchon thank you very much for ur hard work [emoji122] [emoji122] [emoji108]
Dammit... Never wanted to use CM again... I think I will have to at least for now until it gets integrated in other kernels
Great Job @Lanchon
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
so no bad battery life any more?
Vidura Dissanayake said:
so no bad battery life any more?
Click to expand...
Click to collapse
Yes exactly. With a little more testing a final version should be coming soon. What an awesome Christmas gift!
Thindboy said:
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
Click to expand...
Click to collapse
No it won't solve gps problems. I've had good luck using GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 and Faster GPS https://play.google.com/store/apps/details?id=org.fastergps from the Google play store. GPS status will download assistance data (A-GPS) and faster GPS setups the proper ntp server for your area. I get fixes in about 10 seconds now.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
Everything is somehow faster with this kernel. I flashed the music bug fix with this kernel. Waiting for trim kernel, it will further accelerate the phone.
I noticed that the phone is not heated as before.
You're a genius because you've done a lot for us, s2 community ... And we know that you do not own this legendary phone
Thank you @Lanchon
Sent from my GT-I9100 using Tapatalk
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
Cm12 is available?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
Waiting for your review for Spirit ROM once you've flashed it.
Lanchon said:
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
Click to expand...
Click to collapse
OK so FPBug-V1-src.zip is a flashable zip for fpbug fix for every rom stock jb and kk?And cm-11-M10-i9100-music-bug-fix.zip is for cm11 m10 only?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
x3dnd3x said:
Waiting for your review for Spirit ROM once you've flashed it.
Click to expand...
Click to collapse
Im on neatrom now ,will be on kk once a stable kk apolo kernel comes out!
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Mockingbird said:
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Click to expand...
Click to collapse
Lanchon bases his kernel on stock cm kernel, so cwm recovery is built in.
So it has been a long time in the works and feels like have been working on this forever. First it was an AOSP Rom, then Caf and at some point both. For now the Rom is AOSP 5.1.1 based.
Is still not 100% but have decided to just go ahead and post the Rom and improve and update.
If you have seen the Test Flight CM based version that had been posted with the Starship Kernel the overall theme is pretty much the same.
The mission now is to first go over a few parts of the theme that bug me or did not translate well in the CM to AOSP Transition such as lightening up some text so is easier to read with darker backgrounds. Second mission is go over every APK one by one and fine tune the theme and add in any extra features. Will post an update as each APK has been completed. Most of the work is done in some form or another but have spent ages nitpicking everything to death and have an external drive filled with already completed images, Colour XML's and lots of uncommitted features so updates will come rather quickly. Honestly at this point am just going to start with the APK's in Alphabetical order so if you like the Rom and theme but a few particular things bug you just let me know and I will not mind jumping ahead. Also with each Rom update not only expect app and theme improvements but kernel and other system enhancements as most are already lined up and just need to be tested in the Rom's new incarnation. It has probably seen some better days but with my constant picking and changing have gone back and forth with so many things I think its best to just post so Starship is out there and now start finalizing. What is currently posted is bare bones themed and featuring a Kernel I have also spent almost a year working on. If you had used the Kit-Kat version of Starship then already know how fast the Rom will be improved and updated based on legitimate feedback. I know I am making things out like this is an incomplete Rom but have been using and been very happy with what is posted as my daily. Yes still need to improve a few things but the truth is I am never happy with anything I do and would have kept changing direction until Android N.
Until next time keep looking up!!
Installing
This version was not compiled using the new block based zip format so will take a bit longer when flashing the Rom. Just a warning for anyone who may think something is wrong. It Just takes a minute longer to flash.
Otherwise besides first performing the usual Wipe of Caches, System and Data also recommend flashing the Rom first, Gapps second and SuperSU last.
Downloads
Starship Rom
https://www.androidfilehost.com/?fid=24052804347762130
G-Apps
I recommend using the Banks 5.21.15 version of Gapps and have posted a link below. I don’t like reposting someone else’s work but just now discovered the 6.17.15 version seems glichy during the set-up wizard sometimes needing to be in landscape mode when making a selection so have reposted the version used during testing. Have also posted a link to the 6.17.15 version but found for example during the restore option selecting done will only register the selection in landscape mode.
BaNkS-dynamic-gapps-L-5-21-15
https://www.androidfilehost.com/?fid=24052804347762124
BaNkS-dynamic-gapps-L-6-17-15
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
SuperSU
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Kernel
I will continue keeping a separate thread for Starship Kernels that may update faster than the Rom so can keep a look out here.
http://forum.xda-developers.com/goo...t/kernel-starship-kernels-01-08-2014-t2997470
In staying with the Rules will find Source for the Kernel that is included here
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop
Starship Github
https://github.com/Starship-Android
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=MMEVCWUX83SXJ
I am not responsible for any effect using the downloads from this forum my have on any device and you download and use at your own risk.
Screen Shots
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source(PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance