[ROM][UNOFFICIAL][11.0][raphael] LineageOS 18.1

[KingRichardTheFirst]

anyone got google maps my timeline working? it worked on the testbuild before.. but doesnt worked on the build posted here on xda before.
so i just got it working on a build released in devs telegram channel.

Ah, you have the same issue as me! I never thought the ROM could be the cause of this. I tried everything (I think) except formatting data.

 

[z1022]

anyone got google maps my timeline working? it worked on the testbuild before.. but doesnt worked on the build posted here on xda before.
so i just got it working on a build released in devs telegram channel.

The build from xda or telegram should be same location. Therefore, it should be no difference.

https://downloads.akhilnarang.dev/LineageOS/raphael/lineage-18.1-20210602-UNOFFICIAL-raphael-gapps.zip

https://downloads.akhilnarang.dev/LineageOS/raphael/lineage-18.1-20210602-UNOFFICIAL-raphael.zip

 

[cheppetto]

He did not mean the official k20pro channel.
Dev has an own channel - for testers

 

[RaeesD]

anyone got google maps my timeline working? it worked on the testbuild before.. but doesnt worked on the build posted here on xda before.
so i just got it working on a build released in devs telegram channel.

Did you need to clean install the dev build? Or just dirty flash? I'm on this xda build and timeline isn't working, hadn't noticed till seeing these posts.

 

[z1022]

" I use pattern login but touch vibration is very weak when I login. I have already turn on touch vibration."

Any one have this issue? How can fix it ?
Thank

 

[vZmj4DUHVEHw8B]

did you have System default touch Vibration issue ? I use pattern login but touch vibration is very weak when I login. I have already turn on touch vibration.

I actually disabled that setting, but before I did, I had no issues with the strength.

 

[paparansen]

I had previously considered answering your original post with the same advice as Mauam, but held back because I wasn't certain that this is the problem. In a lot of cases, with this phone, where bootloops occur after flashing, the problem is related to encryption, and formatting the data partition removes encryption and solves the problem, at the expense of losing data, if you didn't back it up previously.

My understanding is this.
Flashing over MIUI or a MIUI based custom ROM, you must format data, because MIUI encryption is modified from stock AOSP encryption. (This isn't unusual and many phone manufactures modify the standard AOSP encryption). If you don't format data when flashing you will find that the phone remains encrypted, but the encryption 'flag' is deleted, causing the system (and TWRP) to believe the phone is unencrypted and so unable to read any data because the data is actually encrypted.

Ordinarily, flashing over AOSP ROMs, the encryption flag will remain set and so booting into a new ROM, it recognises the phone is encrypted and prompt for the PIN (or whatever lockscreen security was set).
However this isn't always the case. I personally, in the early days of this phone, had it happen to me where flashing one AOSP ROM over another had caused the phone to boot only into TWRP. Formatting data has then fixed the issue. I have never yet found any answer as to why this sometimes, seemingly randomly, happens. This is why you will see it advised that it's best to remove all lockscreen security before any flashing.

Sorry for the long reply.
So to get to your case.
It certainly sounds like a typical case where your problem is caused by encryption. i.e. The phone is physically encrypted, but the encryption 'flag' is unset, causing the system to not 'know' that it is encrypted.
Formatting data fixes this because it unencrypts the phone.
However the circumstances of your case, to me, aren't typical of the usual cases of this problem, hence I wasn't fully confident that it may be the problem. The easiest way to determine this issue is when you boot into TWRP. With this problem TWRP fails to ask for the unlock PIN (etc.) and so browsing the file system you see all the folders have garbage unintelligible file filenames, because TWRP has not unencrypted the filesystem.
When this happens you can be confident that formatting the data partition will fix the problem.


As far as TWRP backups are concerned, that's a different kettle of fish.
It may be caused by encryption (again temporarily removing lockscreen security, and therefore encryption, is recommended before making a backup). It may be caused by dm-verity and how you backed up various partitions.o You need to make sure that partitions protected by dm-verirty are backed-up using the partition image option, which do a full bitwise perfect copy of the partition instead of just backing up the data in that partition.
It may also be caused if you have some apps configured so that they have multiple installations to allow multiple accounts 'side by side', e.g. Normally used to have social media apps running with multiple accounts without needing to login and out of each account.

thx for that information

here you got more information from me:

- i had encryption before
- i never had pin/key setup before
- in twrp i can see all files
- in android it says phone is encrypted - how is that possible? ^^
- twrp backup there is no partition image option
- and still: why does the actual release boot, but the previous not ? ^^

 

[Robbo.5000]

thx for that information

here you got more information from me:

- i had encryption before
- i never had pin/key setup before
- in twrp i can see all files
- in android it says phone is encrypted - how is that possible? ^^
- twrp backup there is no partition image option
- and still: why does the actual release boot, but the previous not ? ^^

For a few years now encryption happens automatically in Android as soon as lockscreen security is setup. If you never setup lockscreen security the phone is never encrypted. The first time you setup lockscreen security encryption is automatically enabled.
In order to enable lockscreen security, but remove encryption you need to flash a disable forced encryption (dfe) patch. If you've never done this, but you've setup lockscreen security, your phone is encrypted.

With the previous version installed and not able to boot, could you still see the file system correctly in TWRP? If yes then the problem wasn't likely to be encryption. Without more information it's hard to know why it wouldn't boot. Possibly an issue with GApps?

Depending on the version of TWRP you might see backup options for System and System Image.
With dm-verity you need to backup using the System Image option. See the official FAQ for more details.

What should I back up in TWRP?

The default backup options in TWRP are system, data, and boot. For most cases, this is sufficient for backing up a ROM. (Note that in some rare cases, boot i...

twrp.me

If you only see an option for System, you need a different version of TWRP. I'd recommend the official version.

 

[paparansen]

For a few years now encryption happens automatically in Android as soon as lockscreen security is setup. If you never setup lockscreen security the phone is never encrypted. The first time you setup lockscreen security encryption is automatically enabled.
In order to enable lockscreen security, but remove encryption you need to flash a disable forced encryption (dfe) patch. If you've never done this, but you've setup lockscreen security, your phone is encrypted.

With the previous version installed and not able to boot, could you still see the file system correctly in TWRP? If yes then the problem wasn't likely to be encryption. Without more information it's hard to know why it wouldn't boot. Possibly an issue with GApps?

Depending on the version of TWRP you might see backup options for System and System Image.
With dm-verity you need to backup using the System Image option. See the official FAQ for more details.

What should I back up in TWRP?

The default backup options in TWRP are system, data, and boot. For most cases, this is sufficient for backing up a ROM. (Note that in some rare cases, boot i...

twrp.me

If you only see an option for System, you need a different version of TWRP. I'd recommend the official version.

- how can the phone show it is encrypted, when it is not ? ^^
- the backup is boot, system, data
- i was on previous release, everything was fine. then i updated
to the actual release and got bootloop into twrp. so i restored
the backup and got bootloop to twrp again. so wiped all, but
no format data, installed the actual release again and it worked.
but all my apps and stuff are of course gone, only files like mp3
and stuff is there on data.

i hate this ^^

 

[olus]

Did you need to clean install the dev build? Or just dirty flash? I'm on this xda build and timeline isn't working, hadn't noticed till seeing these posts.

no, just dirty flashed. its buggy since android 11, the telegram build wqs the only build it worked. tried clean flash etc before. sometimes i think gapps is the problem.
will try dirty flashing non-gapps build with nik gapps..

 

[KingRichardTheFirst]

no, just dirty flashed. its buggy since android 11, the telegram build wqs the only build it worked. tried clean flash etc before. sometimes i think gapps is the problem.
will try dirty flashing non-gapps build with nik gapps..

I dirty flashed the last official build and then flashed NikGapps (again, as the survival script always seems to mess things up). My timeline is not working, as in the previous build.

 

[olus]

I dirty flashed the last official build and then flashed NikGapps (again, as the survival script always seems to mess things up). My timeline is not working, as in the previous build.

i got it working again.

i dirty flashed newest non-gapps build with NikGapps-basic-arm64-11-20210501-signed.zip. now my timeline is working again..

 

[KingRichardTheFirst]

i got it working again.

i dirty flashed newest non-gapps build with NikGapps-basic-arm64-11-20210501-signed.zip. now my timeline is working again..

Thanks, I'll try that. I used the non-Gapps build and NikGapps-omni-arm64-11-20210601-signed.zip, by the way.

 

[Kamkol]

download magisk23.apk and rename it to magisk23.zip and then flash via recovery. I worked

you dont have to rename it, flashing magisk.apk works just fine

 

[kumarsid7]

I did a complete clean flash.
The internal storage is really slow. Transfers from a PC is taking 5 times longer than usual.
Tested the same transfer from TWRP and it is normal, so it's something to do with the ROM. Anyone else facing the same? Any possible solutions?

 

[Organized]

I did a clean flash (gapps version) with latest vendor, but connecting to a WiFi with WPA2+WPA3 is not possible

 

[bacardischmal]

Hello,
does this ROM already have the front camera calibration option like other Roms have or is it possible to add?

 

[olus]

Hello,
does this ROM already have the front camera calibration option like other Roms have or is it possible to add?

can you describe it? front cam calibration? never heard of..

 

[bacardischmal]

can you describe it? front cam calibration? never heard of..

I have big problems with my front camera sensors like this:

https://xdaforums.com/t/guide-fix-popup-camera-calibration.3987251/

And I saw on telegram in a change log from: AncientOS 5.4 Society Stable | Android 11
Initial Build: 28/06/21

Added front camera calibration.

Don't know how it works on this ROM,
maybe the developers can add this function?

 

[derproblembaer]

Try this to calibrate the Front Cam:

https://xdaforums.com/t/app-root-xiaomi-motor-control-for-k20-pro.3984181/