yashsingh1/xdaforums huggingface dataset:
[RAZR i Android Development] flameseewa:
Ah that's a shame, I really like HERE. So it's related to the fact the phone is x86. I've tried many apps and HERE is the major one that doesn't work yet, so I'm really hoping it can work one day.

On another note, I maybe found another bug: Visual feedback for tapping (in dev options) I enabled, but it doesn't seem to work.
[RAZR i Android Development] flameseewa:
I've run into problems, discovered that my IMEI was Unknown and I don't actually get any phone signal (Emergency calls only) . I reflashed stock rom and now signal/IMEI is working again. How do I get it to work after flashing LOS?

EDIT: I accidentally used bad SIM card, used a good one and cell connection worked fine. Only IMEI missing is the problem.
[RAZR i Android Development] creezy57:
does NFC work?
[RAZR i Android Development] julianwi:
Good news: I tested a bit more and HERE Maps problem is not so big. Just a changed pthread behavior. Should be easy to patch. You can expect HERE to work in the next build.

I don't know whats the problem with the show tabs feature. Maybe a lineage bug. But I think it's not really important for now.

As mentioned in the first post. Turning airplane mode off and on is often required to get mobile cell connection. Also sometimes the phone signal works better if you disable the automatic network selection.

Yes, I tested NFC and it worked fine
[RAZR i Android Development] flameseewa:
Awesome, is the next build scheduled for release this month? Also, I tried a LOS16 rom on a Xperia and the show taps feature works well, that might mean the problem isn't related to LOS.

Actually it's not just mobile cell connection that's the issue (EDIT: my mistake, I used a bad SIM card) but the whole IMEI of my device becomes "Unknown". That's why I reverted to stock rom and I have the IMEI back. I read of other people having this issue and they suggest backing up 'EFS' partition, but my RAZR doesn't have that partition...

On a side note, I really thank you for developing this rom and am willing to donate one day. :D
[RAZR i Android Development] julianwi:
Maybe new release at end oft next week or so. Must see how far I can get in the next days

Hm, IMEI is shown as unknown for me too. I think the IMEI just doesn't get passed through the radio interface layer. I wanted to rework the ril code anyway. But the cell connection should work even if the IMEI isn't known to the framework
[RAZR i Android Development] flameseewa:
Alright, looking forward to the next build! Will SELinux be enforced in the next one? And private keys signing?

Also I may have found some other minor bugs: 1) often the system 'tapping' sound effect (e.g. in settings or the launcher) plays at very low volume at first tap, but another tap afterwards it sounds normal. 2) the auto brightness feature is pretty bad, in bright daylight it often automatically goes to a very dark low brightness. 3) in the camera app the picture on screen sometimes jars.
[RAZR i Android Development] julianwi:
SELinux and private key is planned. Will be in next release if no bigger problems occur with it.

The auto brightness works fine for me. The light sensor in this device is not the best one. It can easily get covered unwanted by your hand and then the screen becomes dark. I can add the other things to the known bugs list later.
[RAZR i Android Development] flameseewa:
OK, thanks
[RAZR i Android Development] julianwi:
The SELinux policy is almost finished. It took me a bit longer than expected and it needs still needs a bit testing. But I think a new build will be ready tomorrow
[RAZR i Android Development] julianwi:
The new build is out now. It has full SELinux support. Some bugs with houdini are fixed and Notification Access is enabled.

Here Maps, Light Flow and probably other apps should run now. Also you can now have notification dots on homescreen. This has to be enabled under Settings->apps&notifications->special app access->Notification access

Storage encryption still wont work. I had no time to fix this for now
[RAZR i Android Development] flameseewa:
Good work, thanks. The new build is good and the said apps run well now.
[RAZR i Android Development] balthor80:
Thanks a lot julianwi !

I will test your rom in a few days

Keep your very good work for all of us :good:
[RAZR i Android Development] Haverping:
I resurrected the old razrI and must admit this ROM runs like a charm. Some small glitches are due INTEL or the old hardware.

Thank you very much !
[RAZR i Android Development] Jabbzz:
The phone was unusable for me until I flashed this ROM. Pretty stable for me, since I'm using it as a backup phone/music player for speakers :D
[RAZR i Android Development] balthor80:
Hi !

So far very good for me, verry smooth and stable

I just have a problem witht sms. I can send them but sometime I don't receive any response.

I have checked the SMSC parameter and it's OK.

Any idea ?

thx
[RAZR i Android Development] julianwi:
Yes, there where problems with sms receiving when I began working on this rom. I fixed it before the first public release with this commit: https://github.com/julianwi/android...mmit/cdf1e299865efc37b39e531fef9c6243d0e8dd0e . But maybe the problem is still not fully solved. Is there anything special about the SMS you try to receive? A logcat of the radio log would be helpful at the time when the SMS tries to arrive.

adb logcat -b radio
[RAZR i Android Development] Tamsta_T:
Hi, can call recording be implemented in to this ROM? Thank You!
[RAZR i Android Development] timprod:
Hi, can't boot into twrp 3.2.3, after 20-30 sec phone just reboot and that's all. 3.2.1 works perfectly. What can i do?
[RAZR i Android Development] julianwi:
Should be possible. I can try to enable it in the next build.

Don't know why. With 3.2.1 version it's not possible to install this rom. Maybe you can take a look at /proc/last_kmsg after the reboot. It should contain the kernel log and the restart cause
[RAZR i Android Development] NewIdenty:
Wine is complaining about text relocations in the graphics driver, can you fix this please?
[RAZR i Android Development] dumkm:
I used 20190819 build for 1 month, then I noticed several points.

- Time: Sometimes system clock gains several minutes.

- Bluetooth and GPS: When I use both BT and GPS simultaneously - such as car navigation usage - sporadically both BT and GPS dead. Need to reboot for recover.

Also, during build from source, I noticed following 2 topics.

- LED always off if I build from github source. Does it require any additional procedure?

- If you delete /system/bin/pdsbackup.sh, it invokes boot loop. I know currently storage encryption is not supported, but this didn't happen with 20190704 build.
[RAZR i Android Development] julianwi:
This can't really be fixed because we don't have the source code of the graphics driver. But I can try to disable the warnings.

You could try disabling the automated network time sync.

I also noticed some rare problems with bluetooth, but don't know what to do about it. The connection is more stable when wifi is disabled.

The pdsbackup is needed on this rom because it has to change the permission groups of the wifi configs. With the security hardening you will get a bootloop. The workaround is to edit the pdsbackup.sh file and replace PDS_FILE=/data/misc/pds/pdsdata.img with PDS_FILE=/cache/misc/pds/pdsdata.img . Then the image will be created on cache partition and can be used with encrypted data partition. I added The required selinux changes to allow this. If you build with the latest github sources you can give it a try.

And btw I'm about to release a new build in the next days. There will be stability improvements with the mobile connection and we have some new performance improvements from Hazou
[RAZR i Android Development] dumkm:
Thank you for confirmation. Will try clock sync and others. Also looking forward to see new build.
[RAZR i Android Development] Tamsta_T:
Please enable call recording, I'll test it for You :fingers-crossed:
[RAZR i Android Development] Misalf:
I'm hoping to see stability improvements / a fix regarding SMS. I have tested this ROM during a week when it was my birthday and I have missed all the good whishes except for one. Went back to LOS 14.1 which is a shame because otherwise this ROM performs great.
[RAZR i Android Development] julianwi:
ok, the new build is up now. Mobile network connection should now work fine without needing to turn airplane mode on and off anymore. Call recording is enabled and show taps feature works now. Also this rom now uses the intel optimized version of the android runtime. Also thanks to [MENTION=4479363]Hazou[/MENTION], he also worked on this new update
[RAZR i Android Development] Misalf:
Has there been any work on this?

Or can anyone, maybe balthor, confirm that SMS receiving is now working reliably?

I'm hesitant to test the new version as this phone is prissy when it comes to restoring a nandroid backup. I think it's related to the system partition being too big or something along this way.
[RAZR i Android Development] julianwi:
I haven't changed anything specific to SMS since the last release. As long as I can't reproduce the problems or somebody sends me a log, I can't do anything about it.
[RAZR i Android Development] Misalf:
I understand.

Did you experience problems in restoring nandroid backups with TWRP? (I used the version you attached in the first post.)

If I am able to go back to a working android instalation easily, i'll be happy to provide logs from your build.
[RAZR i Android Development] Misalf:
OK, i took the risk and reflashed your build to run

su
logcat -b radio -f /storage/emulated/0/radio.log

directly on the phone via terminal and then sent a bunch of SMS to myself.

"radio.log" is attached.

The first SMS always comes through I believe. Subsequent SMS get stuck somewhere but sometimes one or two survive and arrive just after reboot.

Also, the SMS app doesn't get the delivery confirmation (SMS sent successfully).

---

When restoring a nandroid backup from your build the phone goes into AP Fastboot Flash Mode upon reboot.

[...]
Fastboot Reason:
fastboot: max download size: 100MB

Restoring a nandroid backup from LOS14.1 did work, fortunately.

Is there a reliable way to create a nandroid backup with your build installed?
[RAZR i Android Development] julianwi:
Thanks for the log, I think I have found the problem now. The NEW_SMS_STATUS_REPORT package was null terminated but shouldn't be.

I just uploaded a new build to mega.nz. I hope it works now. Would be nice if someone could test it.

Don't know whats the problem with the TWRP backup function.
[RAZR i Android Development] Misalf:
That was quick!

I'll test as soon as I can. Hopefully tonight.
[RAZR i Android Development] Misalf:
That fixed it. Thank you!

I did a dirty flash over LOS 14.1. Things seem to work except that lots of my contacts vanished but I have backed that up seperately.

Would be great if someone will find a solution for the error on restoring a nandroid backup. Otherwise I'm really happy with this ROM. Thanks a lot for your work, julianwi!
[RAZR i Android Development] dumkm:
I could successfully encrypt storage with PDS_FILE=/cache/misc/pds/pdsdata.img modification.

In addition, I could build "user" build with full function.

- modify device.mk to set "ro.config.low_ram=false"

- breakfast & brunch lineage_smi-user

- modify /system/build.prop and /system/vendor/build.prop to use production version of fingerprint

Indeed disabling low_ram made performance worse, besides safetynet could pass on this build, various secure application such as banking app could run, and AFW worked fine.

Again, I really appreciate for great work.
[RAZR i Android Development] Tamsta_T:
Can't get call recording working. "Standart API" method (the only one that was working in LOS11) will not record another end (my end is recorded perfectly), all other methods will not record anything at all. The only method that suppose to work on this version of Android is root, but call recorder I'm using (this one: https://callrecorder.skvalex.com/get) does not support x86 devices. Any clue if root method for any other device would work? Thanks in advance!
[RAZR i Android Development] Misalf:
It's working for me. Maybe you have to give the dialer app respective permissions?
[RAZR i Android Development] julianwi:
In the latest build call recording should be enabled in the build in dialer app. Go to dialer -> settings -> sounds and vibrations -> call recording. Then you can select an audio format. Then in a call there should be a record button next to the speaker and mute buttons. The recorded call will be saved in /sdcard/CallRecordings/
[RAZR i Android Development] nodeboy:
Working well with F2FS, Magisk and MicroG !

Thanks julianwi and hazou for investing your time.
[RAZR i Android Development] mwoch:
Thank you!

Hi julianwi,

I just wanted to say thank you for still developing for the Razr i. The rom is running like a charm :good:
[RAZR i Android Development] Hellomrboss:
I'm curious as to if there is either an official or unofficial build of LOS 16.0 for the OG Droid RAZR. All I can find when Googling it is the official LOS 14 version. I've also read that 14 is obscenely slow for some users, however I read that there are workarounds for it. I've found a Droid 4 as well as a Droid RAZR on eBay for $30 that comes with LOS 14 and I was hoping that I could just install version 16 instead. Does anyone know how or if it's possible or if there's a link that one could share to a users custom port of it for that specific device?
[RAZR i Android Development] Fedetony.:
First let me say many thanks for bringing back to life my XT890...

Os is working pretty fine, I've been testing it in the last days. I've got 2 issues:

First, I am not being able to root it. As I've installed the file but isn't working. Could someone tell me the correct way for rooting the lineage?

Second,I am having issues with the battery levels in Lineage, Its showing the wrong values. The reasons I changed to it is that the stock ROM as soon as it got any update was making the device very slow and unusable. The Stock ROM for a couple of weeks started to drop the battery level as if the battery was damaged. So I installed a new battery, is not the battery, I have 3 new batteries, tested with a Multimeter before being installed. The behavior kept being the same, as it drops from fully charged to a low level turning off the mobile, or randomly jumping to different levels, up to being fully charged showing only X% of battery. Mobile becomes unusable this way. I already had this back in 2017, and then I repair it when rooting the mobile and installing some stock ROM from another source, I just can't remember what was exactly what fixed the issue, yet I know is SW related and not HW.

On lineage, when I connect the device to the USB or a charger it changes immediately the value of charge of the battery randomly, and if it hits a low value it turns off the device. Also happens when pressing the power button. It was for 2 days stock on 100% and it was working quite fine...
[RAZR i Android Development] julianwi:
For rooting, just install the su-addon zip file and don't forget to enable root access for apps in developer settings.

The phone probably has to recalibrate the new battery. That's quite normal. You can help it to calibrate by charging the device completely full and discharging it until complete low a few times.
[RAZR i Android Development] Fedetony.:
So many thanks... I'm really happy with the lineageos and performance :). I am impressed by the freedom and options for the user. Thanks for your reply, yes root was not active on developer options.

So after checking battery voltages connected and disconnected happens to be somehow the battery's third pin is high (showing battery is empty) and all the batteries are getting overcharged. Hardware failure in the Motorola sensor. Fortunately the EG30 comes with an internal over-voltage protection to 4.2V so the battery does not explode. This explains the sudden drop to 0% every time it hits the over-voltage protection. So I bridged with a resistor the sensor pin input to a low value and battery is now showing a battery level I can somehow use to calibrate. The under-voltage and over-voltage signals are now correct and battery dropped to the 3.8V level after some hours of use, so I suppose my device is reading both OV and UV by amplifying the signal.

I'll be very careful while charging the device the first times to see the battery levels go to a correct value. Yet there is this program that limits the current to 500mA! Razrichargecurrent which is awesome! yet I have to set it on every time it restarts, how could I change the default setting to the 500mA? There must be a setting somewhere... (I am rooted so I can change the text)

You see, since I triggered the High voltage signal, It could happen it thinks it can charge voltage controlled and not current limited, which is actually dangerous since it will push, when fully discharged, all the current it wants as fast as possible.( a good explanation in "EEVblog #176 - Lithium Ion/Polymer Battery Charging Tutorial" on yt)

I was searching without any success for the schematics, if someone know where to find them I have the possibility of replacing parts on the HW.

:good::good::good:
[RAZR i Android Development] balthor80:
Thanks Misalf & julianwi !

I Don't have the time to test and send the logcat and SMS are very important for me ;)

So thanks at you two for the test and the correction !

I will reinstall this version soon
[RAZR i Android Development] Misalf:
Regarding the nandroid backup problem I encounter, in case anyone else is interested...

The only clue I was able to find was a post by Hazou stating that (if memory serves well) a TWRP bug or incompatibility prevents the system partition from being mounted correctly during installation of a new ROM if it was, at some point in time, formated using fastboot.

To cure this, one would have to install Clockwork Mod and format with that. Then, TWRP can be reinstalled and used normally.

I will only try to go this route when I get a new phone to make this one more usable before its next use. It's just not practical for me at the moment but maybe for those who are about to do a clean install anyway.
[RAZR i Android Development] tablord:
Encryption fails ("Orig filesystem overlaps crypto footer region")

Hey [MENTION=5903026]julianwi[/MENTION]: Thanks for your hard work and keeping this device alive! :good:

I am currently testing the latest build 20191018. Most things that I have tested work flawlessly so far with one major exception: Encryption.

Directly after flashing the build I made the suggested change in the pdsbackup.sh file (changing the line PDS_FILE=/data/misc/pds/pdsdata.img to PDS_FILE=/cache/misc/pds/pdsdata.img) and rebooted. However, when trying to encrypt the green Android logo appears for 20-30 seconds but then the device jumps back to lockscreen. This is true for both password and pattern screen lock.

logcat reveals:

Cryptfs : Not a valid ext4 superblock
Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place.

If necessary, I can provide full log. But there seems to be no other issue with encryption.

Did anyone successfully encrypt the Razr i with the latest build and with or without changing pdsbackup.sh file yet?
[RAZR i Android Development] dumkm:
For my case, resizing partition size with resize2fs did work.

Please search keyword with "How do you encrypt your device running CyanogenMod 12.1?"
[RAZR i Android Development] Igorhcc:
First of all, thank you for bringing new life to such an old and brave device.

But, after the installation, I got a bootloop at the unlocked bootloader screen. Does you or anyone have experieced this? I was at CM11, even when I tried LOS14, I had the same issue and was never able to put a newer ROM in my Razr.

I'm using it as a better GPS for my motorcycle, and a new Android version would be very apreciated.

Ps.: [MENTION=5903026]julianwi[/MENTION] do you have a Patreon or even a Paypal account to us (included me) bought you a coffee?
[RAZR i Android Development] tablord:
So you were successful in encrypting your razr i? Can you please elaborate on how exactly you resized your partitions with resize2fs?

Are you refering to this thread on stackexchange?

https://android.stackexchange.com/questions/117405/how-do-you-encrypt-your-device-running-cyanogenmod-12-1
[RAZR i Android Development] dumkm:
Yes, that's correct. In this thread, you can find reply with tune2fs/resize2fs method.

On XT890, partition is of course different, I believe /dev/block/mmcblk0p17 is data partition.
[RAZR i Android Development] julianwi:
As the other guys said already, it is required to resize the data filesystem with resize2fs. So a few bytes become reserved for the encryption metadata. I added instructions to the first post, how it has to be done on our razr-i.

Don't know whats the problem for you. Maybe you have an outdated bootloader version. You could try to reflash the complete firmware with rsd lite.

If someone wants to donate, I added my paypal account to my xda profile
[RAZR i Android Development] lego2097:
Magisk

Hi

I installed Your Rom on my xt890 (ver. from 20191018) and MicroG installed with the unofficial installer.

Now i try install Magisk but no luck i get reset phone after boot, on launcher screen - after Lineage logo boot animation.

Can u check is Magisk works for U?

Thx for any reply

LEGO
[RAZR i Android Development] dumkm:
I noticed that Disabling battery optimization for Bluetooth can improve stability for connection, although not perfect fix. This seems to be general workaround for Android 7 or later.

By the way, I also noticed VPN connection have problem. I tried both OS defalut VPN and OpenVPN, then connection is successful, however, no ping or any other connection happen. I used completely same setting for another device, then confirmed VPN worked correctly on Lineage 14 xt890 and Lineage 16 shamu.
[RAZR i Android Development] FourOne82:
Has anyone tried newest version with opengapps? I used the move_to_data.zip and tried nano and pico, both wont work for me because of the system partition space.
[RAZR i Android Development] julianwi:
Try the following:

In TWRP make sure system is mounted and execute this line in the terminal:

/system/addon.d/00-move_to_data.sh restore
[RAZR i Android Development] lego2097:
Yep, in twrp Just Mount system partition resolved this issue, now pico works

But i got feel now that with gapps the razr i is slower

I think i Will go back to non gapps version :)

Thx for fast replay and help
[RAZR i Android Development] FourOne82:
I always get an error even with system and data mounted (checked both in file explorer),

begin moving files to data partition...mount: '/dev/block/mmcblk0p17'->'/data': Device or resource busy
/system/addon.d/00-move_to_data.sh[43]: can't create temporary file : No such file or directory
[RAZR i Android Development] lego2097:
​

Just go to recovery TWRP, go Mount tile and check Mount system partition (mine was unchecked), Press back and click install tile and install move to data. zip script, after that i could install pico gapps.

I didnt use terminal

Should works for U too :)

I got TWRP 3.2.1 ver
[RAZR i Android Development] FourOne82:
Exactly what i tried (also via Terminal, which is the same), it copies the script but it gets me the error i posted. Like i said i checked if i see data and system via file manager in twrp, both are definitly mounted.
[RAZR i Android Development] lego2097:
I checked if system partition is mounted with command 'ls /system/' in terminal

U Should See folders names in /system/

like /system/app or similar
[RAZR i Android Development] FourOne82:
Y i checked, i can see everything in system - even the things the script should copy to data.
[RAZR i Android Development] NewIdenty:
The Razr i apparently has an FM receiver built in, is there a way to listen to radio on this ROM? Just curious.