Database Develop

[ROM][6.0][AOSP][{Un,}Official] LineageOS 13.0 (Marshmallow)

LineageOS 13.0 (Marshmallow) {un,}official builds for the Droid 4
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Use these builds on your own risk!
Builds:
Current official builds:
https://download.lineageos.org/maserati (Droid 4)
(When migrating from CM (official and unofficial) or Lineage unofficial, flash this first (manually mount /data in TWRP before flashing and unmount it afterwards) and then directly flash the new image without rebooting)
Su addon for official builds: http://droid.cs.fau.de/lineage-13.0/addonsu/ (The official addon doesn't currently install on Omap4)
Current unofficial manual builds:
https://droid.cs.fau.de/lineage-13.0/
Old official CM nightly builds and snapshots:
https://droid.cs.fau.de/Official_CM_Builds/maserati/ (Droid 4)
Old manual builds:
https://droid.cs.fau.de/cm-13.0/test/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2017-03-25:
Sync with LineageOS (March security level)
2017-03-02:
Sync with LineageOS
2017-02-19:
Fix 10 kernel security bugs
Add SGX Omap4-changes
Sync with LineageOS
2017-02-10:
Sync with LineageOS (January security patchlevel)
2017-02-01:
Sync with LineageOS
2017-01-11:
Sync with LineageOS
Rebrand to lineage
2016-01-21:
Official CM13 nightlies: http://review.cyanogenmod.org/#/c/129192/
2016-01-16:
Added SELinux rules to allow fsck on stock-partitions and fixboot to unmount safestrap-partition
Graphics glitches fixed
zRAM uses 2 compression streams now
2016-01-14:
Implemented LiveDisplay/Color Calibration
2016-01-13:
More fixes for switching CDMA devices to GSM
T-Mobile CZ APN corrected
2016-01-11:
Preferred network type is now set earlier
Audio-routing through dock-audio (desk/car) added
Mouse-pointer (USB/Lapdock) fixed
2016-01-08:
Camera no longer crops pictures in portrait mode
USB storage integration added
Initial root-mode setting fixed
Migrated from busybox to toybox, busybox is gone
Fixed duration of boostpulse in power HAL
2016-01-06:
VZW data fixed
Reboot to recovery fixed
Wifi configuration updated
Widevine blobs updated (from sprout)
2016-01-04:
Adoptable storage fixed
Many kernel patches to filesystem-, block- and mmc-layers
2015-12-25:
Fixed internal storage for real. You need to manually remove /data/system/storage.xml and reboot when upgrading from previous builds. After that the internal storage will be the primary sd.
2015-12-24:
Fixed crashes of com.android.phone on GSM/UMTS (XT894/XT912)
Configure internal storage like expected in M (can't be adopted, would kill safestrap)
Fixed GPS initialization failing most of the time
Run wifi calibration at an earlier stage
Workaround for VZW data: toggle airplane mode after boot once
Something which needed ffmpeg and imagemagick
2015-12-18:
Switching of preferred network fixed
SELinux rules updated
SELinux is now enforcing
2015-12-14:
Audio-routing fixed
2015-12-11:
Capacitive buttons on {umts_,}spyder are no longer recognized as an external stylus, but as buttons
SELinux policies updated
Update widevine from mako
Added (very slow) emulation of idiv-operations not supported by Omap4 but required by newer blobs (gapps swype, widevine)
2015-12-07:
First build for most devices
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data
WiFi
GPS
Camera
HDMI
Playback of DRM-protected content (using Widevine from sprout)
Reboot to recovery
What's not working:
Probably most everything else, including, but not limited to:
Data encryption (due to safestrap)
Gapps:
OpenGApps
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
Installation:
You need a recovery supporting SELinux
A version of Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
These versions (both unofficial and official) automatically switch to GSM/UMTS without installing additional patches.
Source / Repositories:
maserati device-support: https://github.com/LineageOS/android_device_motorola_maserati/tree/cm-13.0
omap4-common device-support: https://github.com/LineageOS/android_device_motorola_omap4-common/tree/cm-13.0
omap4-common kernel: https://github.com/LineageOS/android_kernel_motorola_omap4-common/tree/cm-13.0
local manifest to build cm-13 for the Motorola Omap4 devices: http://droid.cs.fau.de/lineage-13.0/local_manifest.xml
XDA:DevDB Information
LineageOS 13.0 on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Beta Release Date: 2017-03-25
Created 2015-12-14
Last Updated 2017-04-05

Good job

Thanks again!

Excited.

Installed 151214 this morning over the top of 151210.
The "low in call volume " issue appears to be fixed, as per the notes above; I've had a few phone calls this morning with only one issue:
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?

hahahaha thanks stargooo one step more for our droid 4!

Hi,
Shobai said:
Installed 151214 this morning over the top of 151210.
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?
Click to expand...
Click to collapse
All low-level audio-routing problems should be fixed, this sounds like a problem with the IncallUI (it probably did not specify that the audio should be routed over the headphone out). Haven't looked there yet...
Cheers,
Michael

Thanks Michael, much obliged!

Apologies for the double post! @stargo, I think this may have been mentioned in the CM12 thread - I've got "Playback control" turned on under Buttons, but a long press of the volume keys doesn't have any effect on playback. The volume keys work properly for volume, though.
Thanks again!

Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?

LuH said:
Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?
Click to expand...
Click to collapse
Flash the build from the 14th.

Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?

Septfox said:
Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?
Click to expand...
Click to collapse
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!

So has the build from the 14th fixed the DATA issue?
By no LTE/CDMA support right now, does that mean I wouldn't be able to receive emails and online push notifications unless I am on WiFi or they are Text/SMS based?

hi, can i have noob question? is there some tutorial how to make own build (i have tried to google what to do in which order but i didnt have much luck - create folders, get local manifest, init repo but when and how get omap4 common files required for build...)?

Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).

Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
So by finding this out, it would seem that the Data connection for any provider is not functioning due to a permissions issue in which the OS cannot write the given APNs from the "search" function to the file which stores the data... is that correct?

Hi,
Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
Click to expand...
Click to collapse
Great
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
Does it work after a reboot, too?
Or do you then need to toggle airplane mode again? It might be that toggling airplane mode is what actually causes the connection to be established. Judging from the radio logs I have seen, the RIL responds with an error after bootup and toggling airplane mode might fix it.
Btw, for the people on UMTS: I'm testing a fix for the crash of com.android.phone after boot.
EDIT: Confirmed by @joojoobee666: toggling airplane is enough to get data working
Cheers,
Michael

Bobcus Leper said:
Flash the build from the 14th.
Click to expand...
Click to collapse
Yup, switching Vibrate on touch off in sounds settings helps from this build on. Thanks, I have decided to make this my primary system, so far great impression
Bobcus Leper said:
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!
Click to expand...
Click to collapse
I second that; especially Trebuchet, Settings, dialer, contacts and messaging are way more responsive. I clean installed system (1218 build; wipe /system, install just this and Open GApps Pico) with keeping data from 12.1, it went pretty smooth.
Also it's been laying in standby for about 12 hours now, Wi-Fi on, and it's still charged ~96%. Either it's a battery level reading bug and will soon drop fast, or huge improvement over L - usually I'd lose 10% - 20% at least.

GREAT JOB I was looking forward to CM 13 since June. However, right after flashing GAPPS the processes crash and can't make any progreses. Doesn't matter if I use Slot 1 or 2, already tried mount no-mount /system and /data.

Problem with connection

Hi. When I changed in settings network mode to 2G only, signal icon started to flicker. After reboot I have no signal at all (it is impossible to call, send/receive SMS, use data connection etc.). In info (*#*#4636#*#*) preferred mode is set to "WCDMA preferred" and I cannot change it - I can chose another value from list but changes are not saved.
In settings phone says that none of SIM cards are inserted - but I can now access SIM 1 settings. However, everything is blocked and beneath the network type there is a description: "Invalid Network Mode (-1). Ignore.".
It happend when I was on latest official CM 13.0 nightly but this is probably not ROM's fault. Problem didn't disappear after clean flash, after restore or even after flashing whole set of images with official MiFlash tool.
After some research I found that setting ro.telephony.default_network from 22,22 to 10,10 should work, as 10 is for "LTE/GSM auto" when 22 is incorrect value. Separated by comma for two SIM slots. Ok, so I tried to edit build.prop with some apps without luck - access denied (rooted). I tried to mount system rw from Root explorer - nothing happens, still ro. From ADB - no, "dev/block/bootdevice/by-name/system is read-only". I even tried to change SELinux to permissive but still nothing
Every idea is welcome, I just need to get my phone to work as a phone again

Anyone found ROM or kernel that allows tether on O or P?

Tether used to work fine on Nougat, then in Oreo and Pie, google baked-in the inability to add "dun" to an apn whether existing or new, resulting in an error message of "carrier does not allow apns of type dun." This resulted in a really slow, erratic tether function in the ROMs I tried.
Anyone found a ROM, or kernel, or know of a dev that is actively adding the same functionality as was present on Nougat--that is, tethering worked properly out of the box, or adding dun to the apn makes it work properly? I know for a fact that SOME Oreo and Pie ROMs now allow one to add the dun parameter to the apn, but it still didn't make tethering fast and stable like before.

lineageos

I'm a little surprised no one else has weighed in on this--it is as if @namanjr and I the only ones who have an interest in tethering.

namanjr said:
lineageos
Click to expand...
Click to collapse
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.

pbergonzi said:
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.
Click to expand...
Click to collapse
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.

namanjr said:
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.
Click to expand...
Click to collapse
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?

pbergonzi said:
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?
Click to expand...
Click to collapse
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.

namanjr said:
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.
Click to expand...
Click to collapse
Thanks. If I decide to upgrade to pie again, I will do this.

Dirty Unicorns V13 (Pie)

ZVNexus said:
Dirty Unicorns V13 (Pie)
Click to expand...
Click to collapse
Thank you. Can you tell me or show a screenshot of your tether download speed with (and/or without) the DU rom or with the dun parameter in/absent from the apn, illustrating the difference in quality?
I am lax to immediately install another P rom knowing that if I need to come back to N, there is extra work/risk involved.

Hey, I've also been struggling in this boat for a few months now. Went from a nexus 6p with Los 14.1 to the oneplus 3t. Only rom available at the time was 15.1 , which I remember kind of sucked when it first came out the gate on the nexus 6p, so I was hesitant to use it. Quickly ran into this issue where the tethering speed was dramatically terrible. For months I've just assumed it was the oneplus 3t's fault. Maybe the radio is weaker, or my carrier doesn't approve of this Chinese import versus the other...
I bounced between Stock, Ice Cold, and Los trying to find the best settings for the best result. With my carrier (tmo) the trick was to make a new apn and set it up to use a different address, meant for devices without lte support. "epc.tmobile.com" . This immediately made everything fast again, however it sort of pipelines any tethering activity. So like it would have the good expected transfer rate with one thing, but if you tried to load anything else, that thing would hang until the first thing finished transferring.
I'm glad I finally caught wind of this question/thread. It's relieving to know that it's just because google f***ed with something in oreo and pie, and not that Los suddenly updated into inconvenience. I'm going to try Dirty Unicorns 13 as ZVNexus suggested, and will report back to you with results. Also if any of you can help better articulate this 'global dun 0 apns-conf.xml trick' for me that'd be great and I'll gladly try that out and give results. I flashed magisk and navigated to the apns-conf.xml file just to be suddenly reminded I have no idea what on earth I'm looking at.
** Dirty Unicorns 13 Result
A big maybe? Tmobile out of the box shoots down tethering speed to ~70 kb/s . I usually use the TTL trick to work around this, but that requires I set/use any APN protocol to IPv4. For whatever purposes, the version I tried (du_oneplus3-v13.0-20190109-0432-RC) doesn't allow you to edit the initial APN settings, however I can see that it has "dun" listed in the types. Inconvenient, but I figured whatever I'll just make my own BUT NO. It won't let you save a new APN with dun anywhere in the types. So in the end I can't give any solid result, sorry. If it means anything the upload speed was good, so this could be an issue exclusive to my carrier.

[ROM][UNOFFICIAL][10][Q]LineageOS 17.1 for z5c (suzuran)

Hi all:
Here is a LineageOS 17.1 ROM for Z5 compact (suzuran).
Download 2022-09-11
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 10.0 (Q)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 September 2022
Using sony blob's from stock version 32.4.A.1.54
Memory issues finally fixed!
Battery consumption significantly reduced! For further reduction, please follow these instructions.
Google Pay does not give an error when starting the app. This does not mean, that payment is working. I can't test it, because I don't use this feature at all. Please report if it's working or not.
Updated aptX encoder blobs.
P2P-Crashes fixed.
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!) There is a version 3.2.3 out there, but with that version I had problems to restore my backups. 3.2.1 is just working perfect for me!
OR use my self built TWRP-version 3.6.2!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Bluetooth
Camera; both built-in camera (Snap) and 3-rd party camera apps.
Snap may be a little bit laggy, please use 3-rd party camera app instead; for example OpenCamera. If you're running into errors, please report.
Enforced SELinux support (see attached screenshot)
Fingerprint
FM-Radio
GApps (pick this version: ARM64, 10.0, pico [tested])
German app AusweisApp2 working (see this post)
GPS
Headset
LiveDisplay (see attached screenshots)
Location services
Notification LED
Offline charging
Phone calls (see attached screenshot)
SafetyNet test passed successfully
Signed build
SMS
Torch
WiFi
These things are NOT (or badly) working:
Camera focus at low distances.
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.
If you have problems with GApps:
Sometimes the SetupWizard of GApps crashes on and on. Then you have to boot into TWRP, mount system, and go into terminal, where you have to delete SetupWizard (see screenshots):
Code:
cd /system/system/priv-app
rm -rf SetupWizard
Reboot.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Benefits:
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.

Hi Bernie,
First things first : Thank you so much for your amazing work on this device.:highfive:
So hard to find a good, compact and up to date smartphone.
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
On your Los14.1 (i tried with the last one you created, a few days ago) : it would be something like 0.8go ram (so everything run smoother) still without gapps and other apps / settings.
Maybe, now our days, 3go ram is mandatory for android + gapps + 3rd party ...

Ryu--X said:
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
Click to expand...
Click to collapse
I know about that. I've tried with gapps and I can confirm that ram is running out of free space. Sometimes the system is not responding any more (screen is flickering and it seems that nothing happens) and I have to restart it (press power button quite a long time until power menu appears).
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?

Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs

Berni-0815 said:
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Click to expand...
Click to collapse
I can confirm that unfortunately GPS isn't working.
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
casouzaj said:
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
i didn't have this behavior on my tests, but i usually let the system start and wait for few minutes before using it (especially on 1st boot).
Also, i always reboot once after the 1st boot.
Hope it will help

casouzaj said:
after the language selection, my phone reboots on the 'Just a sec', endlessly.
Click to expand...
Click to collapse
Clean install?
That should not happen...

Ryu--X said:
I can confirm that unfortunately GPS isn't working.
Click to expand...
Click to collapse
You have to enable google's location service in location settings. With that, maps is working with correct location; but I don't know if the location comes from gps, wlan or network. It's raining since many days and I don't want to stand outside in the rain and wait for gps connection... :angel:
I've tried to install f-droid and their location services; no better results...
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
Click to expand...
Click to collapse
Yes, I know. The problems are always the closed-source binaries from qualcom and sony that are not properly working on LineageOS versions > 14.1
We're working on it but I'm not able to say if we can fix these issues.

BTW: Is anyone able to make an outgoing call successfully?

Berni-0815 said:
Clean install?
That should not happen...
Click to expand...
Click to collapse
Yup,, every single time!
Sent from my Xperia Z5 Compact using XDA Labs

As I said, that should not happen...

Berni-0815 said:
BTW: Is anyone able to make an outgoing call successfully?
Click to expand...
Click to collapse
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)

Ryu--X said:
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Click to expand...
Click to collapse
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?

I'm not on any aspect a Dev but I give you all my energy on continuing the developpment of this ROM.
Any other support available ?

Berni-0815 said:
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
Click to expand...
Click to collapse
Here it is !

And you can make an outgoing call sucessfully? The other end rings and you can make a call?

Berni-0815 said:
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Click to expand...
Click to collapse
Yes exactly , both ways are ok (incoming and outgoing).

Ryu--X said:
Yes exactly , both ways are ok (incoming and outgoing).
Click to expand...
Click to collapse
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...

New version out; see 1st post

Berni-0815 said:
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
Click to expand...
Click to collapse
Pretty strange, indeed.
The phone i tested with is on another provider than my z5c.
I got to say that i checked the apn before making my tests, and they were good.
I will retry with the new version tonight .
Thanks

The APN shouldn't matter for regular calls unless you're using Wifi calling or VoLTE, maybe disable both and see if it works.

Question Issues on Google Setup Wizard on every ROM (probably)

Hi, I'm having issues while syncing my Google account during the Setup Wizard's process, after choosing to restore data from a previous backup.
What happens?
(Tried several times on ArrowOS 12.1 20220808 and on crDroid 8.7 20220801 with either NikGapps 20220709):
- I connect to any type of network (both mobile data and Wi-Fi give the same result);
- the setup wizard asks to "Copy apps & data", but I "can't use old device";
- I apparently successfully log in to my account by solving the 2FA;
- I enter the PIN of the old backup and I choose what to restore everything already selected (Apps, Contacts, SMS and MMS messages, Device Settings and Call History);
- the setup wizard shows the agreement screen where you can toggle stuff (Location and Device maintenance) for a second with a disclaimer explaining how data is used;
- THE WHOLE SCREEN DISAPPEARS;
- a new "loading, please wait" screen appears for less then second;
- the agreement screen shows up again (without the how-data-is-used disclaimer), letting me toggling stuff (but there's no "Back up to Google Drive" option);
- completing the setup wizard, I have to log in again as it looks like the device has never had a Google account linked (even though there's a notification saying it's restoring apps and related data, but it's stuck on 0 over X apps to install);
- logging in again lets me restore apps data but not device settings and it also lets me choose to back up to Google Drive;
What doesn't solve this problem?
- changing ROM version
- factory resetting the phone or any sort of clean flash
How did this problem came up?
I flashed ArrowOS vanilla over the GApps build for error, then I dirty flashed the GApps build and some errors came up, therefore I clean flashed and started having issues.
I have no clue on how to solve this and on why this happens either, and I found no one facing the same issue on the net. I don't think it's a ROM-related issue (since changing ROM doesn't solve the problem), this is why I'm asking here.
How can I solve this?

Can you use another device to login to your google account via a web browser and check there is a backup in existence ?

dst212 said:
Hi, I'm having issues while syncing my Google account during the Setup Wizard's process, after choosing to restore data from a previous backup.
What happens?
(Tried several times on ArrowOS 12.1 20220808 and on crDroid 8.7 20220801 with either NikGapps 20220709):
- I connect to any type of network (both mobile data and Wi-Fi give the same result);
- the setup wizard asks to "Copy apps & data", but I "can't use old device";
- I apparently successfully log in to my account by solving the 2FA;
- I enter the PIN of the old backup and I choose what to restore everything already selected (Apps, Contacts, SMS and MMS messages, Device Settings and Call History);
- the setup wizard shows the agreement screen where you can toggle stuff (Location and Device maintenance) for a second with a disclaimer explaining how data is used;
- THE WHOLE SCREEN DISAPPEARS;
- a new "loading, please wait" screen appears for less then second;
- the agreement screen shows up again (without the how-data-is-used disclaimer), letting me toggling stuff (but there's no "Back up to Google Drive" option);
- completing the setup wizard, I have to log in again as it looks like the device has never had a Google account linked (even though there's a notification saying it's restoring apps and related data, but it's stuck on 0 over X apps to install);
- logging in again lets me restore apps data but not device settings and it also lets me choose to back up to Google Drive;
What doesn't solve this problem?
- changing ROM version
- factory resetting the phone or any sort of clean flash
How did this problem came up?
I flashed ArrowOS vanilla over the GApps build for error, then I dirty flashed the GApps build and some errors came up, therefore I clean flashed and started having issues.
I have no clue on how to solve this and on why this happens either, and I found no one facing the same issue on the net. I don't think it's a ROM-related issue (since changing ROM doesn't solve the problem), this is why I'm asking here.
How can I solve this?
Click to expand...
Click to collapse
hello mate
could you solve it? something similar is happening to me

diegots said:
hello mate
could you solve it? something similar is happening to me
Click to expand...
Click to collapse
Hi there. Now I'm running a different ROM, tho, PixelOS. I just clean flashed it. Also, it might be the old backup that caused the problem with those ROMs, while the newer backup I used (created on ArrowOS) didn't cause any.