yashsingh1/xdaforums huggingface dataset:
[Droid RAZR M Android Development] DiamondJohn:
This ROM has gone "Alpha" and is basically ready for daily use https://xdaforums.com/droid-razr-m/development/crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571 or you could also check ResurrectionRemix at https://xdaforums.com/droid-razr-m/development/resurrectionremix-nougat-xt907-xt905-t3697567

See the following post for the current status of this experimental build.

https://xdaforums.com/showpost.php?p=74272802&postcount=59

all the below is regarding previous build attempts

DO NOT FLASH GAPPS!

Make a nandroid (you will definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.

Flash the ZIP

It is unrooted, so I personally flash Magisk v12 (I have the zip and know its working). I also flash UnSu and Busybox remover

DO NOT FLASH GAPPS!

Reboot

Install the Magisk Manager (if you went down this path for root)

This is an experimental build of crDroid 7.1.2

The good :D

It's crDroid!:)

It's Nougat!:D

It Builds:p

It Boots!:highfive:

It has all the eyecandy!:angel:

It feels really "snappy":eek:

The bad

If you flash Gapps it falls to pieces in a never ending cycle of crashes!:crying:​

It is buggy even without GApps:(​

My Hopes:

People will flash this, get some logs and maybe someone with more knowledge (maybe the xt897 LOS device maintainers?)	will be able to decipher the logs and determine whats missing. Maybe someone here has a direct line to one of the maintainers of the xt897 LineageOS?

How I built it:

Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)

Source: https://github.com/crdroidandroid/android -b 7.1

I used a working device tree (ie local manifest) from my working LineageOS 14.1 Build machine (see attached) for an XT897 (with the touch drivers for an XT907)

Basically, I have done no "magic" here, it all just kinda worked. up to a point as its pretty buggy. BUT IT BOOTS!

I also have a ResurrectionRemix 7.1.2 I will also upload.

Almost forgot, flash this at your own risk and i take no responsibility for what happens to your device.
[Droid RAZR M Android Development] rahimali:
Since GApps seem to be the only limiting factor, did you try the various available flavors of GApps?

Also, there's one more alternate to GApps, which is the microg project. Did you try that instead? There's an unofficial flashable installer available here but that page also has links to the various components if you wish to install those manually...
[Droid RAZR M Android Development] DiamondJohn:
wierd:eek:, I just reflashed the ROM and it wasn't anywhere near as stable as it was the first time I flashed it :confused:
[Droid RAZR M Android Development] DiamondJohn:
I took a big batch of logs, read them (as much as you can with that amount of crashes:eek:), did some MAJOR changes (but "impolite" and took some major shortcuts though not so quick to actually do), and now its a LOT more stable, and I even managed to install and boot with GApps, connect to the market and download a couple of apps. :highfive::victory: But don't get me wrong, it still crashes like a &@%#$

ie there are still "some" force closes:p

I'm moving off of this one (ie crDroid) and give ResurrectionRemix a similar "attack " :fingers-crossed: On previous attempts/builds it acted the same as crDroid, but much worse.:mad:

But most importantly, my phone is on the fritz and I think (ie hope thats it's only:fingers-crossed:) the recovery image is corrupt

[IMG="doh!"]https://media.giphy.com/media/Wvo6vaUsQa3Di/200.gif[/IMG]
[Droid RAZR M Android Development] Trey n:
i flashed crrdroid for the xt907 and first boot it works like a charm but when u reboot it it goes bonkers and endless force closes

i hope u can get this stable because i have crdroid installed on all of my devices my favorite nougat rom :)

I hope someone can keep the development going for this ROM for the xt907
[Droid RAZR M Android Development] DiamondJohn:
my last build available in post #3 that I managed to get to work with GApps / Google play :cool:
[Droid RAZR M Android Development] DiamondJohn:
hmmm... I'm giving it another go to get some logs and it actually seems MORE stable after a few wipes of dalvik and cache...:confused:
[Droid RAZR M Android Development] Trey n:
Can't install apps package installer force closes :( as well as the keyboard ?
[Droid RAZR M Android Development] DiamondJohn:
Tell me something I dont know!:p

I have found its a bit of a random number generator, in that sometimes I flash and the FC's are MANY times less and others much more. But generally speaking, the faster you set the device up, the more chance you have. Also, when it starts to fail, go to recovery and clean cache and dalvik. Also delete /system/priv-app/OmniSwitch & /syatem/app/NFC/

I kicked off a new build and flashed it. As part of the build, I undid my "hacky" changes which seemed to improve stability (orig didnt allow GApps), and refreshed all crDroid code to source. I found that the new build was almost as stable as my modified build. ie as crDroid fixes bugs for their official devices, our unofficial build inherits these fixes and also becomes more stable :highfive:. So, hopefully as their builds become more mature, we may end with a stable build as well. This state of affairs (ie pure crDroid code) is the best situation / goal.

I also trued flashing (and building) one of their official devices (a Nexus 5 / hammerhead). I found that there were a number of issues even in the official builds. For example, I found that OmniSwitch caused a number of force closes in my build. In the official Nexus 5 build, although it didnt force close, it didn't actually work. ie there is work to be done in Omniswitch, which we will inherit. I also found that the official build din't have working Lockscreen album art nor music visualiser. So there is clearly a lot of coding ahead for crDroid; which again, we will inherit:D.

Also the more I think about it, we are more stable without GApps, and its nowhere near a daily yet, so I am seeing it more and more as a preview / test that we may have a very customizable Nougat ROM for our phones (in the future :fingers-crossed:)

I also noriced that for our screen resolution, the code falls back to the old B/W bootanimiation instead of the newer one. That wont do for my builds in the future:mad:

I would suggest that if anyone is really interested to see this ROM "running" and its features, then do not flash GApps; its simply a preview of what is hopefully to come.

On a side, does anyone know of a free, non registration, low advertising, fast to upload(the ones i found take 4Hrs to upload!) hosting website I can post future builds onto?:confused:

I think I will also generate a pure xt897 build to hopefully garner some interest by other devs, as the xt897 is an official LineageOS device, which is the vendor and device tree I am using to build crDroid (and ResurectionRemic and possibly other LOS based custom ROMs)
[Droid RAZR M Android Development] Trey n:
AWESOME time will tell :)

and i have noticed that bootanimation too and i hate it i love the new one

and u could upload it to ur google drive and share the file ..........
[Droid RAZR M Android Development] DiamondJohn:
Google drive not an option. Any other ideas?
[Droid RAZR M Android Development] Trey n:
Y not?

Onedrive

Dropbox

Mediafire

Mega
[Droid RAZR M Android Development] DiamondJohn:
also see the second half of this post https://xdaforums.com/showpost.php?p=73211646&postcount=79
[Droid RAZR M Android Development] DiamondJohn:
I also just found the following post of a user having what appears to be the exact same issues with LineageOS 14.1, when they install GApps :confused:

https://xdaforums.com/droid-razr-m/development/lineage-os-xt907jbbl-t3577746/post72841480

Its a pity they dont have an xt897 so that they could post an issue/bug directly with LineageOS :(
[Droid RAZR M Android Development] DiamondJohn:
Bad news all :( I had a chance to flash a build and actually take the logs, ie on top of all the logs you guys posted... NOT!:mad:

Anyway, in short, we are getting "GPU Page Faults" in the kernel. The GPU is Graphics Processing Unit, which would explain the systemUI crashes. The bad news is that I looked at our kernel code and compared it to another device which does work, and our kernel code is way behind. eg hammerhead code file on the line that logs the error is 2000 lines, ours is only 1000 lines.

I tried slowly updating more and more of our kernel, but each file I brought up to newer code triggered a dependency on another 2 files, and that file triggered a dependency on another few files. as you can imaging it got out of hand very quickly.:mad:

So, unless LineageOS does some major changes to their kernel, I don't think we are going to be running a heavily customised ROM too soon.:crying:

I also tried AICP just in case it was compatible with our "old" kernel, but no.All nougat of course,

I also have tried ResruectionRemix, also no.

Also tried DirtyUnicorns, which is an AOSP based ROM (instead of LiineageOS based like the rest) and that also has kernel issues.It doesn't even show the boot animation. Boot loop :( All of these require mods to make them compatible with their specific build process ie time :angel:)

I have compiled and have a working ResurectionRemix marshmallow.:good:

I have spent a lot of time trying to update our kernel, but failed every time or just got overwhelmed with the amount of change required:eek:

Lineage does do minor fixes to their Kernel, but most I have seen have been stability around the file system and not the display/GPU; where our problem is.

Additionally, the kernel code is shared between JBBL and KKBL, so I very much doubt we would have any better success with a KKBL ROM.:(
[Droid RAZR M Android Development] rahimali:
Why not stick to MM ROMs for now? Could you try and build a few for KKBL and/or JBBL? MM should be good enough for now on these devices and building these should give you the necessary exposure and experience to move ahead to N in the future. Just my thoughts tho m not a dev :)
[Droid RAZR M Android Development] DragonFire1024:
And where might I be able to obtain this?
[Droid RAZR M Android Development] DiamondJohn:
Because Nougat is newer! ;) Building M will not give the depth of experience needed to rebuild the kernel.

I am currently running as my daily, a custom build of LOS 13.0 (with a heap of Xposed modules). The custom build is basically a de-bloated MM with the Nougat Kernel overclocked to 1.98GHz. I compiled a RR marshmallow (with the OC'd N kernel), but during my install I noticed it had a bug whereby all my restored messages returned to being unread after every reboot.:( Should be an easy fix, but still a fix to be built and tested. The idea of compiling RR was to remove the need for Xposed.

After this experience, I realised that the LOS MM ROM with Xposed was pretty good, until I get N running...

NB: LOS13 has not had many code changes since they switched to Nougat. Hence my use of the Nougat kernel AND the fact their official xt897 builds should be pretty close to mine (apart from the kernel & OC)
[Droid RAZR M Android Development] DiamondJohn:
I am guessing that noone rememebrs or tried the following. But, if you flashed the ROM and GApps, and then when it booted, NOT TOUCH the screen, did it fail / crash?

I ask because I have been working on trying to update the kernel, and after many many MANY attempts, I got one to build , flash and boot, but the touch screen drivers are not right, so the touchscreen does not work. But there is also not any force closes popping up. So I am wondering if I have solved the force closes or if it takes touching the screen to trigger their start?
[Droid RAZR M Android Development] rahimali:
Buddy, I believe XT897 is getting official Lineage builds, could you not sync with those sources then make Xt907 specific changes and see how it goes from there? I not a dev so I'm basically out of my depth here but just an idea that popped into my head... :)
[Droid RAZR M Android Development] DiamondJohn:
I AM using the Nougat Kernel from Lineage (Its the exact same kernel for all msm8960 devices ie XT897, xt907 etc etc). That is the one that causes the GPU Page faults. Looking at this code, its well behind the kernels for other devices.

----edit

from original post
[Droid RAZR M Android Development] DiamondJohn:
I have been looking into the issues, looking at my logs etc etc and added some logging, which led me to look into the presence of actual files in my app directories.

What I have noticed is that there are NO ODEX files, while on another device running DU nougat, there are odex files (eg /system/app/LatinIME/oat/arm/LatinIME.odex):rolleyes:

Could someone please confirm that there are ODEX files being built in LineageOS 14.1? try in ADB

ls -lR /system/app/ > /sdcard/system_app_ls.log;
ls -lR /system/priv-app/ > /sdcard/system_priv-app_ls.log;

And post in https://www.hastebin.com/ and place the link here. please :fingers-crossed: or just tell me yes or no.
[Droid RAZR M Android Development] DiamondJohn:
Although not a fix, I am getting closer to the issue :good:

As such, I made a build, that as long as GApps is not installed, no FC's :highfive:)

For those who want to have a play.;)

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I found that the built in file explorer is flakey. No probs for me,I use another explorer I installed over ADB anyway.

The other thing you will notice is that the ROM boots very VERY fast. It should also be pretty snappy on starting other apps, as the ROM has been ODEX'ed. Also, the ROM boots before it gets a signal, but the signal does come in. Worried me at first

WiFi works, installing apps over ADB works, most apps work (only remember issues with the file manager :silly:) I could send SMS and make calls. Thats all I remember off the top of my head.

Enjoy.:angel:
[Droid RAZR M Android Development] DiamondJohn:
I did another install, but tried something with GApps (that didn't really work) and I noticed that on this flash the file manager seemed to be working fine.:confused:

The above suggests that if I sort this Gapps issue, the ROM may be pretty stable :)
[Droid RAZR M Android Development] jbond_00:
It does seem really stable; thank you for your work :)

I had a weird issue with the MTP not working on my pc until I checked the "charging" radio button in developer options, even though I tried switching to file transfer from the nav bar and MTP was selected/highlighted in the developer options. I did do a few backup & restore sessions to try various gapps (couldn't get beyond "I agree" in each) so I am thinking I should fresh install.
[Droid RAZR M Android Development] DiamondJohn:
For file transfers, I install an old version of ES File explorer (using ADB over WiFi) and use FTP. My pc is out of easy reach.

To my knowledge, no GApps or any flashed install of an app will work. They need to be installed in the OS (or over ADB) to work correctly. I did manage to get my account registered in play store (through persistence), but after that play services just kept crashing, so I couldn't do anything; except receive the warning that I had a new device connect on my play store account. I was installing substratum when it stopped. One thing I thought of was maybe testing F-Droid or Aptoid :silly:

My other option is to compile a GApps package for the ROM, but I would rather find the actual issue. I sent an email to one of the ROM devs directly, but he is also on XDA, so maybe would of been better to PM him. It really feels like its only a very small fix away.:fingers-crossed: but knowing what that fix is, is the problem :mad:
[Droid RAZR M Android Development] DiamondJohn:
:D:victory::laugh::victory::good::D

I got IT!!!..no I didnt... :crying::crying::crying: read below.:(

I have built and installed a version that is working, even with google apps installed and connected to play.:cool:

I also installed and tested Substratum, Magisk (I did v12 as I have used it before) and Viper. All working. I have to resist moving this to my personal daily, but there is still some work to do. :mad:

I think my next steps will be:

Finish the conversion to xt907 (from the xt897 device sources)

Switch and code in all the required SELinux to be enforcing

Overclock

Add 1 or 2 CPU Gov's (SmartassV2 & Wheatley)

Add an IO scheduler (ZEN & maybe FIOPS)

...anything else I forget right now....

Build and release it as an alpha/beta, or maybe as the first final build:cyclops:

I will start a new thread when its ready,and place a link on this one. :highfive:

PS: I also just realised no-one commented on the new boot animation:mad:
[Droid RAZR M Android Development] Trey n:
I noticed right away lol
[Droid RAZR M Android Development] DiamondJohn:
A littler off topic, but one of the things I have been using to help me debug the build, is a build on an official device (a Nexus 5). I was playing with the customisations last night, and I turned on a feature, that I now cant seem to turn off :silly: and I was hoping you may know where it is; since from memory you have a couple of devices running crDroid. The feature I turned on was the border around the quick settings panel. I looked long and hard at all the options in crDroid settings and for the life of me I cant find where to turn it off :confused: ?
[Droid RAZR M Android Development] DragonFire1024:
Idk about crDroid, but sounds like something in the developer options that have to do with the GPU overlay.
[Droid RAZR M Android Development] DiamondJohn:
sorted

nope. Buuuut... nandroid'd, flashed another ROM (AICP), restored the nandroid, and now its gone. :confused: If it happens again (especially when I am running it on my RAZR ;)), i'll ask the question in the official Nexus 5 thread :rolleyes:
[Droid RAZR M Android Development] DiamondJohn:
Just a quick update so no-one thinks I have abandoned this build.

Its getting close to be ready for a release. I got the SmatassV2 and Wheatley CPU gov; but to be honest I keep forgetting to actually check on Wheatly.:o I also got the ZEN IO filter in, but FIOPS was not going to happen without major changes to the kernel source. But the more I read on it, the more i wanted it...

I am also working on getting init.d working. It has not been working in CM since CM12.1! and therefore any LOS based ROMs since, including crDroid. The strange thing is that I have read many LOS official threads that purport to support init.d. I have personally been using Magisk, however, by building in the SE policies for ViperFX (the bare minimum), it will be one less thing I need to install/have running/taking up RAM.

In my test flashes, a couple things I have noted:

1. It REALLY takes up swap. My ZRam on first boot gets to around 99% consumed. I switch on my swap partition on my external SD, and I have seen it at 500mb+ However, it still stays fairly snappy, whereas my current MM ROM starts to really bog down to near uselessness. I would suggest maybe others look into similar; ie a swap partition or even a swap file.

2. I am building this ROM as an ODEX'd ROM, so it takes up a fair bit of the system partion; normally sitting empty/wasted on the more common DEODEX'd ROMS ;) We have 1.5GB while my handy test phone (a hefty 2.2GHz quad core Nexus 5 with 2GB RAM) only has 1GB, and so I cant even install PICO GApps on the N5:p. So, I would say anyone on this ROM would also have to stick with the smaller end of GApps. I only tried Pico. ODEX'd is what manufacturers normally release their phones as.

I really want to upgrade to this ROM soon. Even though it is missing some of my wanted statusbar item colours :angel: But I tried a ResurrectionRemix build, and it kept randomly rebooting every minute or less.:mad:
[Droid RAZR M Android Development] Trey n:
Awesome ?! Good luck and is there any chance to add zzmove govner too?
[Droid RAZR M Android Development] DiamondJohn:
You just missed da boat. I just finished adding a few other CPU govs.:cyclops: maybe on the next pass. :cool:
[Droid RAZR M Android Development] DiamondJohn:
Bad news.I didn't get it really working.I noticed every build since, did not work as smooth. so eventually I flashed the previous "working" one, and on checking I realised I had a typo that totally broke Art, thus forcing it to compile at run-time (ie use the dalvik). Really not right, but it worked on the ROM and our phone.

I also noted it did not feel as steady as I remembered it. Which may have something to actually do with me using a newer GApps package. One of the threads I follow had the follow recent post.

https://xdaforums.com/showpost.php?p=73954715&postcount=4729

Maybe we should be trying an old GApps from may :confused:

I looked at zzmove, and its still in dev. If I am reading it right, It is also based on a CPU frequency table, so it would need to be manually configured for our CPU. Not my bag sorry, especually since even the devs say its experimental at this stage.

The CPU govs I have coded in, and are building OK, but not tested, are:

INTERACTIVE

CONSERVATIVE

HOTPLUG

HOTPLUGX

INTERACTIVE

INTERACTIVEX

LAGFREE

LIONHEART

LULZACTIVE

LULZACTIVEQ

MINMAX

NIGHTMARE

ONDEMAND

ONDEMANDX

PEGASUSQ

PERFORMANCE

POWERSAVE

SAKURACTIVE

SCARY

SMARTASS2

WHEATLEY
​

Another few I tried, but were not compatible out of the bag with the rest of our kernel were:

ADAPTIVE

BRAZILIANWAX

INTELLIDEMAND

LAZY

ONDEMANDQ

SAVAGEDZEN
​

and USERSPACE I disabled just because its useless and dangerous with an OC'd kernel. NB: dont try to workout what they are for based on the name, from memory "Nightmare" is actually a conservative gov :eek:

Possibly good news :D, I actually just found a heavily customised 7.1.2 ROM, that appears to have very similar features to crDroid, but it actually sticks closer to LineageOS, which is a good thing as its Art that gives issues with crDroid, and it has been oprimised by crDroid (ie not the same as LineageOS code, while this other one uses pure LineageOS for Art) hoping :fingers-crossed: that means it may also work like LOS 14.1 works. The source is downloading as I type (50GB), and as such have not tested IF I can build it or not.
[Droid RAZR M Android Development] Trey n:
cool i wonder what the name of that rom is and cant wait to test it :)

i barely ever use my droid razr m lol i just like testing different roms and stuff on it :P it is quite fun haha :p
[Droid RAZR M Android Development] DiamondJohn:
:crying:It behaves badly as crDroid.:(

The ROM was ColtOS. I had never heard of it until recently, its fairly new and I was hopeful after I checked and it was using ART directly from LineageOS. And without any massaging, even without any GApps, the FC's occur; ie I dont think GApps is to blame. However, these guys appear to possibly help support non-official device builds (new and trying to get some exposure I think), so I'll see if I could possibly get some help from the source devs themselves:fingers-crossed:
[Droid RAZR M Android Development] DiamondJohn:
The build for our device is basically based on the build for an xt897. In its simplest form, changing the first line of the install script (which stops it from being installed on the wrong device) and changing/adding the xt907 touch drivers to an xt897 ROM, provides a usable xt907 ROM. Well, at least it used to:cyclops:

I tried building a pure LOS 14.1 ROM (with the port steps) and it behaved just like the crDroid ROM :rolleyes: hmmm.. NB: I originally build cm-14.1 and successfully flashed it before trying crDroid.

So I downloaded the latest official xt897 ROM, applied the porting steps, and low and behold, it too behaved like the crDroid ROM.

I am trying to download an older version of the lineage source to see if I can build a working LOS 14.1 If I cant even do that :fingers-crossed:, I have little chance of getting crDroid or others working.