yashsingh1/xdaforums huggingface dataset:
[Droid RAZR M Android Development] DiamondJohn:
Configure the CPU the way you want

You can turn the OC off, and go back to the standard 1.5GHz modifying and using the script just above yours, or you could use Kernel Auditor. The default governor (same on all LOS based ROMs) is also very "fond" of the max frequency and hence your experience. You could even lower the max frequency below stock (1.5GHz) to get even lower heat and power usage; which shouldn't be ignored as an option, as I find the ROM to be generally pretty snappy as compared to a few (if not all) of my previous ROMs I have used:cyclops:

Personally, I prefer to use a more conservative governor (ie Scary), that way it stays cooler and uses less battery when not actually needed (it often sits on the lowest clock speed with the screen on:angel: and even regularly shuts down one of the two CPU's! ie "hotplugging"), but still has the ability to ramp up when it would help:eek: (an example of this is also in the scripts just above your post, or using kernel auditor if you don't know what to change in the script). Just be careful as the first script keeps the OC with the default Governor, and my second script although using a conservative governor, adds a higher tendency to hit the OC frequency when the screen is touched to counteract latency due to the conservative nature of the "Scary" governor.

One of the great things about Android is the ability to modify/adjust it to your desires, and the OC adds another capability, which CAN be turned off.

Almost forgot to ask, how did you go with video recording?

Did you have any issues with WiFi? some people on crDroid have had some random issues (which I don't experience :victory:)
[Droid RAZR M Android Development] mastnacek:
I know this. But you will make it as default.

I did not have a thing yesterday. When I was fully charged, my phone started to say 0 percent. When I restarted to twrp it showed 87%.
[Droid RAZR M Android Development] DiamondJohn:
I didnt "make" it default, that's how the OC in Lineage source makes it. You have to remember, this is my personal build, for me, and I simply share it for no benefit to me. ie I want the OC so I ain't going to spend time to turn it off by default, sorry, you have the option/ability already built into the ROM.:p

My battery is dying, I know this because I broke it using an overpowered charger. But generally, our batteries are getting old, or have been replaced with dodgy non OEM replacements (I just ordered a new one as this ROM has given my phone new life). Also, I think the OC will cause an unexpected voltage drop in your battery voltage causing irradic behavior; also worse if your battery is old or not up to spec. Today, my battery widget sat on 100% for hours :silly:, but Android actually showed it got down to 87% ie, there was an issue with the widget, not the ROM; first time they have been misaligned:confused:.

By the way, if you are using my build of TWRP, I think I may of used the same OC'd kernel, I cant remember, you can check while in TWRP. type the following while in a terminal window

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq;
[Droid RAZR M Android Development] mastnacek:
My battery is new from ebay but i know how is it with replacement. I return to CM11. I have xt907 only for viewing internet and Sailforms database app.

But you made good work, respect!
[Droid RAZR M Android Development] juanpalacioscr:
good rom, it's a bit slow but it can be corrected
[Droid RAZR M Android Development] DiamondJohn:
Understand, I did not personally code this ROM, simply enabled it to be built for our phones; and messed with the kernel clock speeds and Governors, so I don't take any comments regarding the ROM personally.

What I found with a couple of Nougat ROMs, is that they take some time to "settle" down. If you watch your CPU utilisation, you can see its doing stuff for a while during the first boot.

I personally use this as my daily, and its snappier than my previous LOS 13.1 build (also overclocked). That daily did have Xposed running to try and mimic some of the RR customisations, which slowed it down. I *think* the pattern I found was that ColtOS was the slowest, then RR and then very closely crDroid (but that's probably more of a guess) and then the snappiest being AICP. That rating is simply based on first impressions, not daily use of all the ROMs.

Nonetheless, I certainly do not find RR to be laggy compared to other ROMs I have run (eg LOS 13.1) as my daily.

Is there a particular ROM you are comparing it to? and did you let the ROM "settle" down?

When you say "but it can be corrected", is there something you have found in particular?
[Droid RAZR M Android Development] aggressivepixels:
I've been using this ROM since around two weeks now. It's pretty good, and feels quite snappy (I even used the Stock GApps package). I've experienced the same bugs than in other Nougat ROMs (TV-like static when unlocking the device, the MTP Host thingy, a very subtle lag that happens when switching activities, and the images of the overview panel being cut sometimes). So, overall, I'm pretty happy with it, I just had to make it look a bit more like AOSP. :P

Have you tried to build AOSPA? I know people hasn't been able to build AOSP for this phone, but...

Also, which ROM (of the ones you've built) is closer to AOSP?
[Droid RAZR M Android Development] DiamondJohn:
I have now been using (and loving) this ROM now for about 4 weeks (ie a few days after I first built it)

Thats one advantage over crDroid in that this ROM is deODEX'd which leaves enough space on the system partion for a larger GApps.

I dont think thats a Nougat specific thing. I have had that effect since Jellybean, after rooting my device. If I go back to stock it disapoears but as soon as I root, it returns,. Even on the stock firmware.:silly:

I personally use FTP to transfer files, and have turned off its notifications, and now I dont get the FC's on MTP Host.

Another BUG I have noticed, is that even though I set the OC to 1.7, during the day, it will reset itself to 1.98:mad: At least the selected GOV stays put.

I havent done an explicit comparison, but any lag between switching apps doesnt appear to be worse than on previous ROMs (maybe possibly even less) Could be due to the many boot script adjustments I have.

Yeah, I tried to build DirtyUnicorns which is ASOP, and that didnt boot.:(

If you want an ASOP look, then I would probably suggest the LOS ports. RR is the furthermost from ASOP! Is there any specific reason you didnt go with LOS? Of my public builds (I have an old LOS build somewhere), crDroid and AICP are probably more ASOP like.

Although, AICP may be worth a look, as it did seem pretty snappy to me on the one boot I did to test the build.
[Droid RAZR M Android Development] JajaNönö:
RAM

Hi there,

As I said before, by far the smoothest experience I had using this device. And it got even better using the optimisation scripts (CPU governor & SD enhancements). I was wondering however, why it says the device only has 792 MB of RAM. As far as I know it should be 1 GB or something close to that, right?

Thanks in advance!
[Droid RAZR M Android Development] DiamondJohn:
NOT specific to this ROM nor our Device

Physically the phone may have 1GB, however, the number you are looking at is generated by code, and as such is dependent on what Google devs saw fit to report as memory. eg Available memory? the other "missing" amount may be unavailable under ALL circumstances and therefore not of any use to report on? It is NOT specific to our device and / or ROM.

I have another 2 devices with 2GB, and they show only 1.8GB of "Total Memory". If you really want to know the answer, you will more likely get a better response in the general Android questions thread. see https://xdaforums.com/showthread.php?t=2259645

But a simple web search shows that for another device, some RAM is allocated to the GPU, and I would assume ours also assigns some to the GPU and possibly other hardware (such as the audio DACs maybe) : https://stackoverflow.com/questions...atically-and-not-only-what-is-only-a#26682914
[Droid RAZR M Android Development] JajaNönö:
That explains - didn't even consider that this is a device unspecific thing. Thanks anyway!
[Droid RAZR M Android Development] juanpalacioscr:
in general it is a very good ROM. I compared it with lineage of ilichva and maybe it seemed more fluid lineage. But maybe it's just a feeling of mine. I can not compare them in real time since I do not have two devices. Anyway now I'm using this ROM, I think it meets what I need and want. I hope you can compile an 8.0 rom rome in the future. Keep it up, bro. (sorry if something is misunderstood or not clearly understood.) Use Google translator
[Droid RAZR M Android Development] DiamondJohn:
New build!

New build is up! See the OP

Things that have changed (That I remember ;)):

Under-clocking of CPU. Enabled down to 96kHz (from stock 384 kHz). You can thank [MENTION=420530]arrrghhh[/MENTION] for that, I took the "frequencies file" changes from his old kernel source :good:

Over-Clocking now capped to 1.7GHz (Stock 1,.5GHz, previous at 1.98GHz)

Latest Security Patch (5 Dec 2017)

Updated Magisk

Debloated Resurrection OTA (obviously its unofficial and therefore no OTA's)

Debloated Resurrection Stats. No use to anyone as they have moved onto Oreo

Numerous LineageOS bug fixes. I was surprised that even though RR have stopped updating their Nougat branch, code sourced from Lineage OS receives updates.:victory: A lot of these changes can be seen here: https://download.lineageos.org/xt897/changes/ (up to the date of the build) I also added the sensitive numbers from LOS just "while I was there"

I have dirty flashed the ROM, and it seems ok so far. The only thing I have noticed is that its taking some time to "settle-down". But that is partially due to the number of boot scripts I have.
[Droid RAZR M Android Development] faisala66:
awsm wowwww...

:good::good::o this is awsm:fingers-crossed::fingers-crossed::good::laugh:
[Droid RAZR M Android Development] DiamondJohn:
Please please PLEASE, do not quote the OP. You can edit your post and cut out the quote of the OP.
[Droid RAZR M Android Development] DiamondJohn:
I think its an interesting fact that we are now in the top 4.5% of android phone versions :highfive:

https://www.gsmarena.com/latest_and...out__both_oreo_and_nougat_grow-news-28676.php we are doing pretty well for such an old phone.

NB: this ROM is 7.1.2, maybe the .2 moves us up even higher in the ranks ;) (but its the same API so isnt counted separately)
[Droid RAZR M Android Development] faisala66:
waiting for 8, Oreo Rom
[Droid RAZR M Android Development] DiamondJohn:
Give em an inch...:rolleyes:

https://xdaforums.com/showpost.php?p=74830299&postcount=13

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

Actually, I know you read the above, because you thanked the post!
[Droid RAZR M Android Development] faisala66:
don't be sad :o:o:):good:
[Droid RAZR M Android Development] juanpalacioscr:
hello, a consultation. Why is it necessary "You must format your Data partition as F2FS"? I own a motorola razr hd xt925 and I use these roms, they go very well. my question is because I did not do that step when installing the rom. I hope you do not mind my question, thank you
[Droid RAZR M Android Development] DiamondJohn:
There appears to be a bug in the LineageOS Kernel for the JBBL moto_msm8960 devices as/when run on the xt897, xt907 & xt905

https://wiki.lineageos.org/devices/xt897/install

https://xdaforums.com/showpost.php?p=72841480&postcount=63

https://xdaforums.com/droid-razr-m/development/experimental-crdroid-7-1-2-t3641378

https://xdaforums.com/showpost.php?p=74332305&postcount=64

You came "late to the party", and so missed the history.
[Droid RAZR M Android Development] juanpalacioscr:
I think I did not express myself well haha. I installed RR on my razr hd xt925 without the need to format data like F2FS. It goes very well of course. My question is what would I change if I format data such as F2FS ?. Sorry for the inconvenience. I really appreciate your work with this!
[Droid RAZR M Android Development] DiamondJohn:
That is a general android question and not specific to this ROM (its not even regarding a xt907/xt905!). For a better response ask it in https://xdaforums.com/showthread.php?t=2259645
[Droid RAZR M Android Development] |Konrat|:
Thanks for the upgrade ...i flashed it also dirty on my RazHD XT925...and it runs also very well. :cool:

And it´s interesting that juanpalacioscr flashed without format f2fs..and have no Problems. :good:

And by the way...F2FS shout have a little bit more performance read/write, as EXT4. But i have no compare.

Greetings Konrat
[Droid RAZR M Android Development] DiamondJohn:
It dioes say "some" on the LineageOS page. https://wiki.lineageos.org/devices/xt897/install

A few years back I had a device which became unusable with ZRAM turned on, while everyone else found it helped their device. Manufacturers switch internal parts in the middle of production runs. Maybe thats why its only "some" ie different internal hardware.:confused:

Theres more, and a simple web search would of provided MANY more details to his exact question.
[Droid RAZR M Android Development] DiamondJohn:
FYI: stericson busybox

Just an FYI

A "deal breaker" for me on any ROM is the ability to run Viper (audio mod replacing AudioFX - equalizer). A prerequisite to install Viper is to install BusyBox using stericson's one explicitly. On the latest build, stericson's busybox would not install, but all the others available that I tried, did. So, I could not install Viper :mad:.

So, I ended up flashing a Viper specific install zip, and that worked, with NO busybox installed. I had to install another busybox as I use it heavily in my boot scripts.

I also had the exact same issue on another device also running RR. So its not specific to our device/build.

So, there appears to be an issue/bug in Magisk/stericsons busybox/RR/My Build that does not allow stericsons busybox to be installed, but the workaround is to simply install a different busybox and all is good :good:
[Droid RAZR M Android Development] osum101:
Hello Everybody :)

Thank you [MENTION=5417899]DiamondJohn[/MENTION] for the hard work and keeping out little razrm alive :)

So I flashed this rom last night by following the instructions in the OP (used twrp 3.0.x and Nano Gapps) , booted fine (took about 13 mins) and registered my sim immediately.

But I'm having some very weird issues

> The "Home" and "Recent Apps" buttons don't work at all, tried both the launchers in rom (trebuchet and Pixel) and the buttons don't do anything when clicked.

>I can't pull down the notifications/quick settings panel. Only a single row of 5 icons (wifi, Data, Rotation, etc) are visible. Nothing works to expand the panel

These are major issues i experienced, following are a couple more but I'm not sure if they're related or maybe I did something wrong but here goes,

> The battery charging is EXTREMELY slow, 4 times the normal charging. I get around 1% charge for every 1.5 mins on average on my previous rpm, LOS 13 port by ilichva, but with this it was 1% for every 5-6 mins.

Also phone got hot like crazy, too hot to hold in hands.

>Where are the developer options??? Tapping build number didn't do anything

I'm downloading CrDroid build right now and I'll give that a go, followed by other Nougat builds here but if anybody can help me with the issues explained above, that'd be awesome :)

Thanks.
[Droid RAZR M Android Development] DiamondJohn:
The OP has a link to TWRP 3.1.1, not 3.0.x which makes me weary about how closely you followed all the OP instructions. NB: the "3.+" for TWRP was simply a copy of an RR template from another device's thread. I personally have only tested it with my own TWRP build (the same goes for all of my Nougat ROMs) ie 3.1.1. You may of identified an issue that 3.0.x is not advanced enough to flash these ROMs to our device. PS you are not going mad, I just edited the OP and removed the ref to TWRP 3.+"

I don't think it should be to important, but did you download the latest version of GApps? Again, not an issue, but I personally use Pico,. I suggested Pico or Nano just because they were small, and my original ROMs were ODEX'd and therefore could not be flashed with a larger GApps. Again, I dont know of or would expect any issues with larger GApps.

Neither of those issues are related to the launcher. Both regions are handled by the OS ie ROM itself, i personally never saw this behavior on any flash of a Nougat ROM; and I have done quite a few, so something going wrong with your flash would be my best explanation. If you were able to get into dev options, you could turn on the screen touch highlighter thingy. It would of been worth the time to wipe your device again and try a re-flash before you took the time to re-instate your internal SD Card (which would of been blank after formatting your data to F2FS). Just in case something random happened during the flash, make sure to read your TWRP install logs, there may of been warnings that got hidden by a quickly moving display in the log window. Within TWRP, copy the log to SD and read it on your PC

They would most likely be VERY related. The slow charge and getting hot, suggests to me that the CPU is running at the highest clock speed (something is in a hard loop). It does take some time for Nougat ROMs to "settle down" (welcome to 7.1.2...) Also, having the screen on and/or trying to play with the new ROM will drain battery fast / slow down the charge.

When you tap build number, do you get any toast messages telling you your getting close to turning on dev settings?

If any of the other ROMs "work" for you, maybe come back (if you wanted RR). As you know, I am using RR as my daily, and have none of the issues you experienced, and no-one else has (yet) reported the same issues as you regarding the Navbar and status bar. You are running an XT907 aren't you? I think in a PM you said you replaced the screen?

Have you tried the LOS 14.1 ports? if you have issues with another build I have made, that would probably be the next ROM I would try to flash to check it isn't the device (possibly your replacement screen) or something you are doing.

Another thing to always try if a ROM doesn't behave is to not flash GApps and see if it boots. However, your issues really do not appear to be GApps related.

Also, if the latest crDroid also gives you issues, the original crDroid may be worth a try, as it is ODEX'd After trying LOS 14.1.
[Droid RAZR M Android Development] DiamondJohn:
An idea occurred to me. Have you tried in landscape mode?

Do you have an external SD Card? On the first boot a common CPU consumer is the media scanner. When testing my early builds I ejected my external SD Card before first boot, and have a boot script which turns off the media scanner on boot (from experience, only really useful if you are changing SD Cards). Remember, in case I wasnt clear enough, the first boot is NO time to be checking your battery consumption as android is running a LOT in the background. Check "ps" from adb to find what is consuming your CPU.
[Droid RAZR M Android Development] DiamondJohn:
I meant to say "top"not "ps":o
[Droid RAZR M Android Development] Janik97:
Got this rom running on my Razr HD xt926 and it's much better than most other roms i've tried, thanks! It also fixed that distorted sounds my speaker has made all the time under KK! But unfortunately I just can get Edge, neither HSPA nor 4G on my Razr. And even the Edge connection isn't stable, sometimes a little cross appears at the bottom of the signal bars although I'm receiving a signal... Anyone knows how to fix that?
[Droid RAZR M Android Development] |Konrat|:
Hello DiamondJohn.

I now the RazrHD is not your Topic and you have no device for testing, but maybe you have an idea...

The question from another german user:

He have flash this Rom on the "RazHD XT926" and he have now the Problem with the network...he have no HSDPA and no LTE and EDGE is not really stable.

I now it can be to do with the difference in the modem...i can´t self test it in the moment, because i don´t have a micro Simcard...only nano.

I don´t now how exactly the difference in the modem config, between this 2 devices is, And how it "Leanage OS" used ...maybe there is a "standard modem.bin file" or so:eek:

...Janik97 was faster...:silly:

greetings konrat
[Droid RAZR M Android Development] DiamondJohn:
As you obviously know, I have not built nor ever owned a RAZR HD, but looking at the device specific source code, to me on quick inspection, there only appears to be a device specific touch driver (for device proprietary files, which is different to a RAZR M).

https://github.com/TheMuppets/proprietary_vendor_motorola/blob/cm-14.1/xt926/xt926-vendor.mk

https://github.com/LineageOS/android_device_motorola_xt926/blob/cm-13.0/device-proprietary-files.txt

https://github.com/TheMuppets/propr...cm-14.1/xt925_jbbl/xt925_jbbl-vendor-blobs.mk

https://github.com/LineageOS/androi...bbl/blob/cm-12.0/device-proprietary-files.txt

Does that mean anything?

Do they have the same problem with a ported LOS 14.1 ROM?

My suggestion would be to flash back to official stock Motorola (JBBL not KKBL) firmware for the phone, and then re-flash TWRP and the ROM. Although the ROM (including the build.prop file) can affect the modem, there are specific modem binaries (and clearing steps) in the Motorola firmware.

Not that I know or think it would be the cause of the issue, but did they reformat the data partition as F2FS? (just grabbing at straws here)
[Droid RAZR M Android Development] DiamondJohn:
So, the short short SHORT version is that if you booted the ROM before installing GApps, the Navbar works?

as for kill app on back, just assign the kill app action in the SmartBar settings to long press on the back button.

As for getting hot, never let your phone get hot! I charge mine while it lays flat on a solid table . I noticed the heating problems ever since I changed the battery to one I bought from eBay (ie non OEM). You may also change the CPU gov to something a little less aggressive. I use Scary (very conservative) with a touch boost to 1GHz for 200ms. Your phone will also run at the underclocked freq (i set it via boot script to 96kHz) during charge, which should theoretically charge faster. But nothing comes for free, so maybe Nougat on our phones is battery heavy, its hard to say for sure personally since I have a non OEM battery.

On the side, I wouldn't be using anything to restore contacts. The restore should be handled by google, and if both are used, its steps like that, that could induce strange behaviors on your phone. Personally not a fan (not recommended at all) of restoring system data either, especially between different ROMs (data and structural changes). Thats just begging for issues. I have flashed so many ROMs restoring my settings has become second nature. I basically flash ROM, GApps, Install Viper, restore SMS (i have >5300), install all apps from play, restore SELECTED apps data (absolute minimum), configure ROM settings/customization, re-instate my boot scripts (I have built & accumulated many over the years) and thats basically my process (with backups before I start).

By the way, kudos on typing all that on your phone:eek:
[Droid RAZR M Android Development] osum101:
[MENTION=5417899]DiamondJohn[/MENTION] yes the short short version is when I flashed RR and CrDroid without GApps, the NavBar, quick settings panel and developer options all worked okay

And they're still working great after flashing GApps. (Nano package) ?.

Thanks for the tip regarding "kill app with back button", I usually dig right into the settings after installing a new Rom but just can't get time for it these days.

The temperature and battery charging issues fixed themselves on Day 2 after multiple reboots and clearing cache after restoring apps and some data.

So it's all working awesome now ?

Thanks again and Regards :)