yashsingh1/xdaforums huggingface dataset:
[Droid RAZR M Android Development] DiamondJohn:
I just tried a few LOS 14.1 ROMS and they all behaved similar to my crDroid (and ColtOS) builds. It seems that LOS 14.1 for our device is very sensitive to which and how you flash Gapps https://xdaforums.com/showpost.php?p=72841480&postcount=63

And he is not the only one that has had issues.

The above sounds exactly like what we get with crDroid, yet some people manage to get it to work. So maybe if we do the same with crDroid, it too will work :fingers-crossed:

Has anyone got an open GApps PICO 7.1.2 ARM, from around May?
[Droid RAZR M Android Development] RyanLeary:
I have a zip of Open GApps Pico 7.1 from April 4th but it makes no difference.

I could upload it somewhere but it would take a while since I have 0.2mbps upload.
[Droid RAZR M Android Development] DiamondJohn:
If it still fails, don't be in any rush just yet. Although I would be interested to know if it works with the posted LOS14.1 ROM?
[Droid RAZR M Android Development] RyanLeary:
Just tried, the same exact issue happened. I might try flashing crDroid again just to make sure.
[Droid RAZR M Android Development] RyanLeary:
After installing it the second time around it works. I had to skip the setup wizard since it would soft reboot the phone, but it is running. Haven't tried rebooting or any other functions yet. So far it is really quick and snappy!

[IMG="Finally running!"]https://i.imgur.com/3EllIiQ.png[/IMG]

EDIT:

Touch works

WiFi works

Can't test cell service since my device has a bad ESN

Setup crashes early on, have to tap each corner of the device in a clockwise order.

Keyboard crashes

Calculator app crashes

Camera app crashes, might try different camera app.

Clock app crashes

EMail app crashes

Gallery app crashes

Phone app crashes

Package Installer crashes

I will try rebooting next to see if it all breaks like before.

EDIT 2: Yep, after a single reboot it all breaks again.

Should I upload the GApps? Pick a file host and I'll upload it for you.
[Droid RAZR M Android Development] DiamondJohn:
If you just want a "play" with the ROM "working", just dont install GApps ;)

What I would be interested in is if you can get the standard ported LOS 14.1 ROM working with your GApps? what is the date of the GApps you are using?
[Droid RAZR M Android Development] RyanLeary:
I already tried and the same issue happened, but on Lineage I cannot get past setup and it starts breaking about half way through the setup. My GApps are from April 4th.

I find it kind of strange that GApps just break everything. At least there are alternatives to Google Play available, like Yalp Store. But there is the still the issue of the system basically self-destructing after a reboot.
[Droid RAZR M Android Development] DiamondJohn:
What really confuses me is that I posted on the LOS thread that it seemed stable, yet when I flash it now, it goes to crap :confused: The only thing I can think of is that the GApps I had at the time were in some kinda sweet spot:silly: I have downloaded two possible packages I may of used at the time. 20170326 since I posted that I found the thread on the 30th https://androidfilehost.com/?w=files&flid=11222 (pico is my norm). When I get a chance, I will test flashing pure LOS with this GApps. I will prob do it latter today; when I hope to also get a chance to make a logging build (of crDroid) that will hopefully help decifer what is going wrong in my build, just a step, even if it helps somewhat, the next step of understanding why and how to fix it may be really hard and beyind my android dev pay-grade.

-----------edit

PS: You are using the build from https://xdaforums.com/showpost.php?p=73763972&postcount=27 ? Its pretty stable for me (and others I think) if you do not flash GApps.
[Droid RAZR M Android Development] RyanLeary:
I get a File Not Found error so I downloaded the older build. This could be the source of some of my issues.
[Droid RAZR M Android Development] DiamondJohn:
Yeah, your right, the upload expired. sorry. I actually checked my local drive and I have also deleted that file; I know I can rebuild it any time if I need it (improved at least a little). Actually, you *may* get more mileage out of the original one by replacing and/or adding the lines below to your build prop (didnt try it myself, but this breaks Art and thereby forces it to run off the dalvik. slower)

dalvik.vm.always_debuggable=0
dalvik.vm.isa.arm.variant=krait
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapstartsize=8m
dalvik.vm.heapsize=256m
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.dex2oat-Xms=64m
[COLOR="DarkOrange"]dalvik.vm.dex2oat-Xmx=512[/COLOR]
dalvik.vm.isa.arm.features=div
dalvik.vm.dex2oat-filter=speed

NB the typo on the orange line which should of ended with an "m" but having this mistake "improves" things (ie behaviour).

I will probably release a new build soon, if anything comes out of the extra logging :fingers-crossed:. And I will use the other free hoster which apparently doesn't expire as quickly.
[Droid RAZR M Android Development] DiamondJohn:
Latest demo build

Here is my next build. Its still not "there", but if the instruction below are followed, its a lot better. But still better than before anyway.

As this is a build to assist in finding whats wrong, I did not optimize/correct adaway this time.However, it can be fixed with the attached script.

This build also includes a batch of CPU governors and a couple of extra IO governors. As well as an Overclock on the CPU and GPU.

NB: Some of the Govs are not compatible with the rest of the ROM and so will cause hangs followed by a reboot. I think InteractiveX and Nightmare are two from memory. I actually like wheatly's use of all steps in the clock range. And Tripndroid IO was desribed similar to FIOPS. But there are many many descriptions of each.

I managed to get the Play store up and running, and downloaded a few apps; including Kernel Adiutor to play with the Gov's and OC.

NB: even if you dont install Play store, the odexall script will correct AdAway. simply run odexall with no parameters

The instructions are:

You will need to run odexall USER Y (and reboot) after every app or groups of apps installed from play ie I did a batch of all the apps then ran the script

Its OK to share this download on other websites/forums, but you MUST include a link back to this thread, even if you slightly change the name or contents :mad:

https://www.dropbox.com/s/kqrsivp8m...7-v3.7-DiamondJohnDroid-EXPERIMENTAL.zip?dl=0

When the ROM starts to crash again, I think a boot to recovery and wipe of dalvik may help. or running odexall "" Y, followed by a wipe of dalvik can give it a little more life.
[Droid RAZR M Android Development] DiamondJohn:
Gapps now install

Just a quick update, I now have a version that basically allows the flashing of gapps, registering/connecting and downloading from the play store. However, some of the apps installed from the play store (about 50% of the ones I quickly tried) are flakey, and go through the FC's we previously saw (same errors in the logs as well). Using an updated version of the odexall script I used above, "fixes" about half of those. ie still not 100% and still basically the same issue.

I did get an FC on contact sync during registration, but my contacts appeared within the ROM.

I am running out of options, without some help from another dev I don't know how much further I will be able to get this ROM. Maybe someone could join the crDroid G+ page and highlight our issues / bring attention to my attempts; and failures...
[Droid RAZR M Android Development] juanpalacioscr:
Thanks bro! . Good rom !
[Droid RAZR M Android Development] Galaxyninja66:
Necro reply, please use multiple file hosting services. Roms going completely dead is a very sad thing, unstable or not.
[Droid RAZR M Android Development] DiamondJohn:
These are experimental ONLY. Its basically a share of a file on my disk, and even I have deleted it. Its kind of a good thing that they automatically expire. Its simply a pity the better one expired before the rubbish initial build :o

As for using multiple file hosting, well, either I can use my limited time trying to get this to work, or waste it uploading to multiple file hosts. Remember, I am not a team of developers, I am a single guy, with only 24hrs in a day, and other stuff to do.

However, I do plan to release another version kinda soonish.
[Droid RAZR M Android Development] Galaxyninja66:
I am an underage with infinite time, I just don't know how to build android. Like, I have a general Idea, but actually building for a specific device is confusing.
[Droid RAZR M Android Development] DiamondJohn:
Doh! I just found out how to turn on a plethora of logging. Maybe that will explain the issue, or just needlessly consume more of my time :mad:
[Droid RAZR M Android Development] Galaxyninja66:
Tested this on my RAZR M, here is my report:

TWRP 3.0.2-1

JBBL

Coming from STOCK 4.0.4

Wiped /System /Data /Cache /Dalvik using rm -rf

Flashed crDroid without Gapps

What I tested:

Youtube in browser

Bluetooth

Wifi

Opening various system apps

What works:

All of the things I tested.

Ran really fast, bluetooth and wifi worked at the same time, dialer opened up and made a call, and youtube played in browser with sound just fine.
[Droid RAZR M Android Development] DiamondJohn:
Thanks for testing. I have also sent an sms, to myself, and received it.

I am surprised you thought it was fast (escpecially the first/ early boots when its still compiling apps in the background), as its actually set up in a very cautious/thorough and thus a slow way. IF I get it to work, it will possibly be much snappier.

PS: I have also built a newer version of TWRP 3.1.1 https://xdaforums.com/droid-razr-m/general/twrp-3-1-1-xt907jbbl-t3652141
[Droid RAZR M Android Development] Galaxyninja66:
I am very excited to have a working nougat on my RAZR M, I just switched to KKBL as I figured out how to get CM12.1 booted up (its running rn), the reason I switched is because when I would put my device into sleep mode and power it back on the screen would flash for a half second, super annoying at night and in general. Hopefully KKBL fixes this. Happy to test new builds and stuff too, I can switch to JBBL when I can just to test a bunch of roms. I like to help development! :)
[Droid RAZR M Android Development] Galaxyninja66:
Hell yeah, I'm going to test this and report back tonight! :D

EDIT: F*ck me I thought there was a new build
[Droid RAZR M Android Development] Galaxyninja66:
Where is this ressurection remix nougat rom I here about???
[Droid RAZR M Android Development] DiamondJohn:
oooo....I may :fingers-crossed: of found the root source / fix to all our issues! so excited :victory: , but it will take some time to test, but had to let you know. watch this space:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
[Droid RAZR M Android Development] DiamondJohn:
It works!! Its alive!

YES!​

I now have a stable Nougat running on my Razr M! with Gapps installed!

Its almost embarrasing how simple the final fix was, and how it had been available probably from day dot. A lot of wasted time.

The Nougats I have built, and the Ports of LOS 14.1 are both based around the fact that there is an official LOS 14.1. for the XT897. They are almost the exact same device except for the hardware Keyboard and touch drivers.

Yesterday, after coding a tonne of logging to try and see exactly where it was failing, and hopefully fixing that; well That was the plan.

Every now and then I check the changes in the XT897 14.1 build at https://download.lineageos.org/xt897 and sometimes download the latest to test if porting it will work, and also to give LOS an idea that people are still interested and therefore they may build an Oreo version (not looking good). So, on that page there are two other links, apart from all the ROM downloads. I just cant believe they build a weekly when It would appear it doesnt work?

I thought I would check the device info again to see any other differences I missed in the hardware. Nope.

The other link was simply the install procedure, which I assumed would be nothing new...

BUT NO! ​

At the top of the page https://wiki.lineageos.org/devices/xt897/install, in RED, is the statement:

​

So, I tried this :fingers-crossed: , and low and behold, my ROM worked!!!!!! :highfive:

​

Not only that, but a new private build of RR 7.1.2 is running on my Phone as I type! Enforcing and all! not a "debug" build, with the OC and governors all there.

I also tried some other build I had done recently. ColtOS booted and ran, DirtyUnicorns (AOSP did not boot:(), AICP worked. I am guessing most LOS based ROMs will work.
[Droid RAZR M Android Development] Galaxyninja66:
This is absolutely amazing, amazing enough to convince me to switch back from KKBL to JBBL! awesome work!
[Droid RAZR M Android Development] DiamondJohn:
Just an FYI. NOT A RECOMENDATION

However, I was worried about converting to F2FS and restoring my phone back to my current LOS 13.0 ROM, so I spent a lot of time making thorough backups, in case I had to clean flash and reinstate everything from scratch. However, The backup in TWRP (3.1.1) of my ROM (plus a manual restore of the internal SD Card) from before I did the conversion and all, actually restored me back to where I was. Which was surprising because everything I read on the internet said that it wouldn't work. I did get a single "unfortunately xxx has stopped working" when I first booted this morning, but it didn't come back, so I chalk that down to the boot process (ie android trying to pretend it has finished booting before it actually has finished) plus a slew of boot scripts (including one that mimics Greenify by hibernating/killing unnecessary processes on boot)

Remember, just my personal experience, not a suggestion you will get the same results. So, I now have a LOS 13.0 ROM running with an F2FS data partition. Something I've been meaning to do for a while, but thought it was going to be hard work. I can't say its noticeably snappier (as everyone states), but its pretty definitely not slower.
[Droid RAZR M Android Development] rahimali:
F2FS and WhatsApp

Do you guys use WhatsApp? I've had dropped messages earlier on WhatsApp on different devices with data formatted to F2FS. I believe it used to be a WhatsApp specific problem.

Can you check to see if it's still there? It might be considering WhatsApp is now owned by the company with the lamest/nastiest/laziest/most retarded developers ever...
[Droid RAZR M Android Development] Galaxyninja66:
I don't have a sim card and no one I know uses whatsapp. How do I test? :silly::eek:

---------- Post added at 01:28 AM ---------- Previous post was at 01:25 AM ----------

JBBL - XT905 firmware base

TWRP 3.1.1 (your build actually)

crDroid 7.1.2 10232017

Bean Gapps Mini 7.1.x

Data is F2FS, Everything else is default

Now for the formal review. I am testing as I write this, and I will revise it before posting it. Lets get into this! :D

1. Setup: Worked great, I don't have a sim card, but that shouldn't matter much. The final "finishing touches" slide took too long (it was only 30 seconds, I'm just impatient :P) so I skipped the set up (it was the final slide anyway)

2. Camera: Everything worked perfectly. Back camera had functioning auto focus and picture/video. Front Camera had functioning video and picture. Flash worked perfectly, auto flash, manual, etc.

3. Microphone: Recorded sound well, I couldn't hear any static or other irregularity, picked up audio/sound was what you'd expect, medium volume, clear and easy to hear. average at worst.

4. RIL: I don't have a sim so I couldn't test this, but wifi works, and bluetooth works well with my headset.

5. Google play: I could set up my account just fine, and hangouts and clash of clans installed and worked well

6. Auto Brightness: Funtioned perfectly, picked up low light (my thumb covering the sensor) and bright light (via my Nexus 10 flash) levels

7. Keyboard: Worked great, I only included this because some roms have a broken keyboard. I do miss the old stock ICS and JB one (those tall keys were god-tier)

8. Speed and preformance: REALLY FAST. I am surprised, the speed is fantastic and everything is snappy (snappier than my N10 actually... maybe it's time for me to upgrade???)

9. General usage: No crashes. Everything is functioning great.

10. Reboot menu: Advanced reboot was on by default (thank you for that)

Reboot System: Functioning

Reboot System UI: Functioning

Reboot Bootloader: Functioning

Reboot Recovery: Functioning

9. Battery: It was at 71% at 7:56PM, and is after all my testing, it is at 70% at 8:12PM. Wow.

10. Live Display: Funtioning, color temp calibration works.

11. Location: Functioning.

12. Other: I was able to configure google assistant, and it picked up my voice with my razr m locked. I set up screen lock and it functioned, and custom wallpapers work.

On a side note, my screen flash issue is gone. The white static has been replaced by a much nicer and completely tolerable pitch black pause. Maybe the telstra firmware fixed it...

I think formatting data to F2FS has made this rom into a 100% usable daily driver. I'm definitely making it my daily driver now. Keep up the good work [MENTION=5417899]DiamondJohn[/MENTION]! :good: :)

Also, since I am running this as my daily, if you need anything else tested I can do it right away! :D
[Droid RAZR M Android Development] DiamondJohn:
I am running the AUS Retail Firmware, and it has the white static screen flash since I rooted it. even on factory firmware, the flash appears as soon as its rooted:confused: You may just be lucky.

This ROM is NOT ready as a daily. For starters its a permissive kernel. And there were a few other changes I made in an attempt to get it to work (before I realised we had to F2FS on data partition). However, admittedly, when I do do a new build, it should be dirty-flashable.

Did you try overclocking? any of the different CPU and/or IO Governors?
[Droid RAZR M Android Development] DiamondJohn:
Although its hard to check something that hasn't happened, have you checked your logcat for errors from whatsapp? It may of not happened with/because of a logged error.:fingers-crossed:
[Droid RAZR M Android Development] dedik46:
I will try this on xt926, right now i'm still using los14 for xt897 on my xt926 and myxt926 is on f2fs and run smoothly with los14, even this is not my daily phone but i'm exited that this phone will live again for custom rom and off course i will report back in here.

Thanks for your hardwork and free time
[Droid RAZR M Android Development] rahimali:
This is what I was talking about...
[Droid RAZR M Android Development] Galaxyninja66:
Oh no, I always run the CPU at 1Ghz Max, deafult Min, with Conservative and ROW I/O. I forgot to test it. I'm restoring a back up (I flashed back to VZW firmware) right now, I'll ping you with how overclocking works
[Droid RAZR M Android Development] DiamondJohn:
1.5GHz is the default/standard CPU clock, and by default, the OC is sorta half on :confused: I have not changed the default min, but with the correct config, it mostly stays in deep sleep when not in use anyway.

I use to use ROW for IO, but I *think* I have less lag using BFQ IO scheduler. I am personally interested to possibly use the tripndroid IO scheduler in this ROM.
[Droid RAZR M Android Development] DiamondJohn:
all just talking. No logs no way to understand what the issue really is.:rolleyes: And therefore only chance/luck to find a true solution.
[Droid RAZR M Android Development] DiamondJohn:
PS: In the xt907 builds, the build prop ro.hdmi.enable is set to false. You may wish to change that for an xt925/xt926
[Droid RAZR M Android Development] DiamondJohn:
Actually something occurred to me. see https://xdaforums.com/galaxy-nexus/help/whatsapp-deleting-messages-t3140876#post74352491
[Droid RAZR M Android Development] Krlos Eduardo:
[MENTION=5417899]DiamondJohn[/MENTION] the download link for your latest release is the same from the first page?
[Droid RAZR M Android Development] DiamondJohn:
By first [page, I am assuming you mean first post, so, no. The last public build is from dropbox (https://xdaforums.com/showpost.php?p=74272802&postcount=59). The original was from some random free web hosting site.

A new build is ready, just needs to be test flashed when I get a chance, so you may be better off simply holding for a short time.
[Droid RAZR M Android Development] Krlos Eduardo:
ok, I really appreciated your hard work.

tnks!
[Droid RAZR M Android Development] Galaxyninja66:
Yee I've got service working now (atleast with verizon :p) so I see no reason why GSM shouldn't work. I flashed the cm10.2 gsm fix, didn't bootloop so that's cool. Running perfectly with pixel launcher and all. Screen flash is back but I don't mind, nougat is worth it and I'll take a screen flash on JBBL over using KKBL or stock any day!
[Droid RAZR M Android Development] DiamondJohn:
So, I have built two Nougat ROMs :angel: and test flashed them, they both worked.:highfive: I have uploaded them to my DropBox account. The two ROMs are:

crDroid

ResurrectionRemix

I just need to create new threads, so if you see one before the other that you wish to try (as if you will only want to try the one:p), just wait, I can only type so fast ;) I will add a post here as I finish each.
[Droid RAZR M Android Development] DiamondJohn:
RR is up https://xdaforums.com/droid-razr-m/development/resurrectionremix-nougat-xt907-xt905-t3697567/
[Droid RAZR M Android Development] DiamondJohn:
And now crDroid is up, kinda... https://xdaforums.com/droid-razr-m/general/crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
[Droid RAZR M Android Development] DiamondJohn:
Since I have downloaded and tried to build (before I knew the trick of formatting Data to F2FS) of AICP & ColtOS, if I get around to it, I might do builds of these as well (since I have done them before). And maybe also a standard LOS 14.1; with my OC'd Kernel of course :angel:

I also tried DirtyUnicorns, but it bootlooped even before the boot animation started :(
[Droid RAZR M Android Development] Tech180:
I tested the rom and it works great! Very fast and fluid. The only problem is that I can't get Bluetooth, wifi, sound, and mobile data to work :(

Ps: I also couldn't get rsd lite to work...
[Droid RAZR M Android Development] beeewell:
Some feedback

I use my XT-907 as a WiFi device only, so I'm unable to test voice calling and text. I'm very excited to have Nougat running on our device. The install was just about flawless. I did reboot near the end of Google account setup, but that may have been due to my impatience.

I can confirm that WiFi and bluetooth WORK !! Also, the ROM performs better than any ROM I can ever remember running on our device.

As a side note, a strange thing that was happening prior to installing this went away !! When I'd power down the device and plug into a wall charger, the device would reboot. I thought it was due to using a generic charger. But after installing this, it doesn't reboot, and I see the battery icon as I should. I'm guessing what fixed it was reformatting the data partition, but it's just a guess.

Major kudos to DiamondJohn and anyone else that continue to support our device. :good::good:
[Droid RAZR M Android Development] DiamondJohn:
Maybe flashing back to stock firmware (my preference is for using fastboot directly, especially since RSD doesnt work), may clear some root issue you have. Just an idea. This is the script I use for AUS xt905 firmwware, USA image files will be named differently https://www.hastebin.com/fiwopedopu.vbs

RSD Lite shouldn't be broken by the ROM, so if that does not work, you have some other more deep rooted issue with your device. I personally never use it, over fastboot.

hmmm.. impatience also cant be fixed by a ROM. I would really not suggest you try ResurrectionRemix then, it has a black screen for almost a minute after the flash has completed.

Yeah, that surprised me too, but makes sense that newer code runs better.

I think you may of guessed right as well.