yashsingh1/xdaforums huggingface dataset:
[Android Software Development] BigDonkey:
[Reposting from LineageOS for Xperia 5 II forum]

Hello,

Thanks for this. Since yesterday the Xperia 5 II has been available on the LineageOS for MicroG website. Today I am attempting to install it on my device, following the instructions on the LineageOS website (as it says to follow).

So far I have got up to the 'Installing a custom recovery using fastboot' section, and more specifically to step 5, flashing the recovery. This appears to work correctly, saying okay, okay, finished. Then the device remains in fastboot mode with the blue LED in the corner and blank screen.

The next step tells me to reboot into recovery by holding volume down and power while the device is turned off, but the device is not powered off. If I press the power button nothing happens. Also when I type 'fastboot reboot recovery' it returns 'fastboot: usage: unknown reboot target recovery'. If I type 'fastboot boot lineage-blah-blah...-recovery.img' it says 'downloading, okay, booting... failed (remote: unknown command)'

The only things I have managed to achieve are:

When I type 'fastboot reboot', the device reboots into the Sony ROM

When I try to do that but hold down the volume down and power while it reboots, it just boots as normal but goes into safe mode if I keep holding the volume down button

When I press some combination that appears to be volume up for about 10 seconds, immediately followed by volume down and power at the same time, the device appears to restart but the screen stays blank and a green LED in the corner instead of blue.

(EDIT) I also tried holding volume up and power from in fastboot mode, this vibrates the phone, orange LED light, no LED triple vibrate, repeat, until I release either volume up or power, releasing power takes me back to fastboot mode with the blue LED, releasing volume up takes me back into the stock Sony ROM

Any advice on how I can proceed? (EDIT) I also tried with the official LineageOS recovery image, not microG version - same result, can only get a blank screen with a green light or boot into Sony ROM

Thank you

SOLVED:

I don't know what made it work, but the changes I made were:

Using a USB-C to USB-A cable instead of USB-C to USB-C

Opened a terminal window from within the platform-tools folder instead of using Minimal ADB and Fastboot

Instead of putting the files to be flashed in the folder with ADB and Fastboot, I dragged them into the terminal window from a different folder to copy the path.

After these 3 changes, typing 'fastboot reboot recovery' worked, when it didn't before.

Also, so happy with the results so far, the fingerprint unlock setup knowing with exact precision where the fingerprint sensor was and how it operates shows how much effort has been put into this ROM (the first custom ROM I have used). And of course, using MicroG means that I am now Google-free. Hopefully all the apps I require work correctly! Thanks again for the time and effort put into this project.
[Android Software Development] kurtn:
You are doing the right thing with those button Tricks. Don't forget to flash recovery after each failed trick. Sony ROM restores Sony recovery.
[Android Software Development] BigDonkey:
Thank you, in the end I managed to get into recovery, although I never did figure out the button tricks!
[Android Software Development] MrRulf:
Hi, I saw that there are boot.img now in the download files for multiple devices, are these required for a new installation or optional and what are they for?

And if they are required, when do I do what with them during the installation?
[Android Software Development] kurtn:
Follow the installation instruction of official wiki.lineageOS.org
[Android Software Development] MrRulf:
Hi, does somebody know if u can install microg the same way you install Gapps on lineage? It's an unofficial build so there is no Lineage for microG version available
[Android Software Development] kurtn:
The reason, lineage4microG exists, is the unavailability of signature spoofing in official lineageOS. Developers of unofficial lineageOS are free to implement signature spoofing or GApps or whatever they want. Talk to your developer.

There are various methods to setup a custom ROM. Including some flashable microG installers. But be aware: microG is not GApps.
[Android Software Development] petefoth:
Some unofficial LOS builders do make versions which include MicroG. It's not a difficult change or addition: you need one more line in a manifest, and to set one environment variable. If the devloper of your build doesn't do it already, ask if they would be prepared to try
[Android Software Development] ale5000:
If the unofficial build already include signature spoofing you could just flash a microG installer and it will work immediately.

This way a single ROM could work together microG or GApps without the need to compile it 2 times.
[Android Software Development] heinhuiz:
@kurtn Do you know if there is a special reason why LOS19.1 build are skipped?
[Android Software Development] kurtn:
19.1 has been built February 10..13 - the promise is currently one build per month. 18 19 and 20
[Android Software Development] heinhuiz:
Yes, I've seen that. At then on February 13 the 20 builds were started again, until Feb 20, when 18 started. But after those finished on Feb 23, nothing was built until March 1. And then 20 rolled out, instead of 19 as I would have expected. That makes me wonder if anything is wrong with the 19 script.
[Android Software Development] FreeLibre:
Hi, LineageOS has recently added 19.1 and 20.0 builds for Mi439 devices (Redmi 7A / 8 / 8A / 8A Dual):

Info about Mi439 variants | LineageOS Wiki

wiki.lineageos.org

LineageOS Downloads

download.lineageos.org

Could you please add them here?

"https://download.lineage.microg.org"

Thank you.

Edit: Added (2023-03-10) https://download.lineage.microg.org/Mi439/
[Android Software Development] kurtn:
Wait another day.
[Android Software Development] HippoMan:
I have a general question involving microg/lineageos. I've searched through this thread and found messages which talk about some aspects of what I want to ask about, but I couldn't find anything which directly addresses the question I'm about to ask. If I overlooked something which does indeed answer my question, then please accept my apology for the bandwidth.

My question: I know that under microg, I can manage totally device-only contacts that are not "shared" in the cloud in any way. However, if I want to send text messages or make phone calls, my understanding (which might be a MIS-understanding, and if so, I apologize) is that I would first have to access my device-only contacts, copy an appropriate phone number to the clipboard, and then paste the phone number into the dialer or the SMS program.

I'm wondering: are there SMS and phone apps which run under lineageos/microg that can access all the info in device-only contacts, so that I can make phone calls and send SMS without going through the copy-and-paste ritual that I described here? ... and also which show an appropriate contact-person's name when a phone call or SMS comes in?

Again, if I'm misunderstanding something or have overlooked a discussion about this topic, I apologize.

Thank you in advance for any thoughts and suggestions.
[Android Software Development] petefoth:
You have misunderstood :)

Apps on your device which have the 'Contacts' permission - including the default Phone and Messaging apps - can access all the contacts stored on the device. That includes 'device-only' contacts as well as contacts which are synched with cloud services.

If the default Contacts app is not showing device-only contacts, then - in the app - go to Settings | Contacts to display.

The Contacts view in the default Phone app, will show **all** contacts, and the Messaging app will access **all** contacts, whether they are device -only or shared with the cloud.
[Android Software Development] HippoMan:
Thank you very much for explaining and for clarifying that which I misunderstood!

So ... to make sure that I now understand everything correctly, is the following indeed accurate? ...

Under lineageos/microg, I now assume that I can set up device-only contacts with no sharing of any of my contacts to anywhere in the cloud nor anywhere else outside of my device ... correct?

And I also assume that this also will apply to my photos and any other information I am keeping on my device: i.e., I can keep photos and other information on my device with nothing being shared to anywhere in the cloud nor anywhere else ... correct?

The reason I want to understand these things is that I haven't installed lineageos/microg yet, and I want to make sure I can use it in these ways before I take the step to install it and try it.

Thank you again for all your help and explanations!
[Android Software Development] petefoth:
Correct

Correct

Neither LineageOS nor MIcrog implies sharing **anything** with the cloud. It is possible to do so, but you would have to install, configure and use additional apps to do so
[Android Software Development] HippoMan:
Thank you! I thought that this is probably what I can expect from lineageos/microg, but I wanted to verify, just in case.

Now, in my not-so-ample spare time, I'm going to start the move from Android to lineageos/microg.
[Android Software Development] kurtn:
Don't try that on your main phone. Set up everything on a secondary phone and swap Sim card as soon as everything is set up.
[Android Software Development] HippoMan:
Yep, that's what I plan to do.

Thank you!
[Android Software Development] HippoMan:
This is a follow-up to my earlier conversation about getting LINE Messenger to work under lineageos/microg.

I understand that Google-Drive-based backup and restore of LINE history won't work under pure microg. However, I'm wondering if the following might work ...

(1) Under my current non-microg Android OS, take a backup of /data/data/jp.naver.line.android

(2) Install lineageos/microg, and then install LINE Messenger.

(3) Restore the previously backed up jp.naver.line.android to /data/data under the microg OS.

(4) Take periodic backups of /data/data/jp.naver.line.android as I use it under microg.

(5) If i ever want to restore my LINE history under microg, repeat step 3 with the latest jp.naver.line.android backup

I'm willing to experiment with this approach, but before I do, I'm wondering whether anyone has tried this before under microg.

A variation might be to only backup and restore one or more appropriate databases (hopefully they are sqlite databases) that are resident within /data/data/jp.naver.line.android, instead of that entire directory tree.

Thank you in advance for any thoughts and suggestions.
[Android Software Development] novabright:
At the end of the last year I noticed that there were no updates since October... but now there is update, released in 22nd of Feb... I'll install that, thanks. I hope that development still goes on even for older phones (I have Oneplus 3T).
[Android Software Development] kurtn:
Oh. LineageOS 18.1 got an extension. But 3t will get no android version upgrade. I guess official support will be dropped in one year.
[Android Software Development] novabright:
Oh, that sounds sad if support is going to end. I haven't had any reason to get a new phone, this is still as good as it used to be in 2016. :P

Will there be a custom ROM to support Oneplus3/3T after LineageOS(for microG or not) ends their support? Or is it Android that ends support and then it would be hard to support these phones in any custom project?

Oneplus dropped their own support years ago I think... and I want to use open software/OS anyway.
[Android Software Development] borisSweden:
Yup, the kernel is to old.
[Android Software Development] borisSweden:
I say to the poeple who try to port Android 12 or 13 to instead work on porting kernel version 4.XX or 5.XX. Or your option is to install UBT.
[Android Software Development] ale5000:
Well, Galaxy S2 has a working Android 13 although the phone is still 32-bit only and it was born with Android 2.3.4; so nothing is really impossible it just need time and efforts :)
[Android Software Development] heinhuiz:
My lmi bootlooped after applying the 15 March 19.1 update through the system updater.
[Android Software Development] kurtn:
Magisk installed? How did you solve the issue?
[Android Software Development] heinhuiz:
I had Lygisk installed. Didn't solve it yet, I'm downloading the previous version to install it through Lineage recovery/adb
[Android Software Development] kurtn:
You can flash orangefox zip

https://xdaforums.com/t/official-twrp-orangefox-recovery-project-r10-0.3900553/
[Android Software Development] heinhuiz:
OK thanks, I'll look into it!

Edit: Can I install it through Lineage recovery? The instructions state to use a TWRP based one.

Edit 2: lmi is not listed in the device tree.
[Android Software Development] jb82:
Hello together, is this the right place to ask questions about an update from Lineage for MicroG 18.1 -> 19.1? The updater app told me that I would need to update manually on my Fairphone 3 and gave me a link for more information (https://wiki.lineageos.org/devices/FP3/upgrade) which led me to an IRC chat (https://kiwiirc.com/nextclient/irc.libera.chat#lineageos) where they told me that I won't get support there because of MicroG and redirected me to https://lineage.microg.org/#faq from where I got back to the information page from the beginning. So I got stuck in a loop and looking here for help now. If I'm not in the right place again, can you tell me where to get help, please?

So I am using an Fairphone 3 with LineageOS 18.1 for MicroG (18.1-20220616-microG-FP3) and didn't yet perform the update to LineageOS 19 because I am worried about data loss. The wiki page states that data loss should not occur, but at the same time it says that application package add-ons must be kept in the same state (installed or not installed) or a factory reset would be neccessary. In fact I don't remember if I installed the super user add-on after installing LineageOS because I switched to Magisk shortly after.

Because of this I am unsure if I am forced to do a factory reset or not. Would my phone get in an unusable state after updating with or without the root add-on if my phone is currently in the other state? I hope you can help me :)
[Android Software Development] heinhuiz:
Dirty flashing the previous release didn't work, I got the bootloop again. Flashing the original Magisk however did the trick. I don't really know what went wrong. Maybe just a failure in the download.
[Android Software Development] kurtn:
We can just recommend to follow the guides in wiki.lineageOS.org . This add-ons thingy is about GApps. That doesn't apply on microG.
[Android Software Development] jb82:
Thanks for your reply! I'm happy to got rid off all those GApps..

When I installed Lineage for MicroG there were two more addons available for download - which I cannot find in the current installation instructions nor the download page. So I guess they aren't neccessary anymore. What I read here on this forum about Magisk with Lineage 19.1 makes me very hopefull :)
[Android Software Development] Mumxek:
where i could get the last 17.1 whyred build please? I hdidnt checked the build so often and its gone, like unfortunately and for me not understandeable. thx
[Android Software Development] kurtn:
Archive.org
[Android Software Development] Regina Rainbow:
Could you please add avicii (OnePlus Nord) to the build roster for LOS for microG 20? New maintainers took over and it's officially supported again by lineage.

LineageOS Downloads

download.lineageos.org
[Android Software Development] jt12345:
Hi all. I have just clean-installed "LineageOS for microG" on my OnePlus 5T and it seems to be working perfectly except for one thing. I want to use "GMaps WV" with my location provided by my GPS. I have given "Location Access" to GMaps WV, and after having tried to locate myself using my GPS, GMaps WV correctly appears in the list of apps that have made "recent location requests". I have also checked whether my GPS is working by installing and running SatStat, and SatStat is working 100% correctly (it shows me that I am locked to 6/21 satellites, my current latitude and longitude are displayed, and my "Last fix obtained" updates every second.) But whenever I click on the "My Location" button in GMaps WV, the spinner (inside the button) just spins forever and the app never finds my location.

The microG Settings applet "Location modules" shows that I have 0 backends configured, but I assume that this is correct as I want to use neither "Network-based geolocation modules" (such as Mozilla Location Service) nor do I want to use "Address lookup modules" (such as Nominatim) - I just want to use my GPS.

I have not yet logged a bug against GMaps WV in case I have not set this up correctly. Does anyone here know whether this should work or not? If I have only clean-installed "LineageOS for microG" and the GMaps WV app (via fdroid), should I be able to use my GPS to find my location? Thank you for your help!

(FWIW, the versions are "LineageOS for microG" 18.1 20220516 and GMaps WV v1.8)
[Android Software Development] heinhuiz:
I think you should at least enable an address lookup backend, how would you navigate without street addresses?

Edit: I stand corrected. See below.
[Android Software Development] jt12345:
Good point! I'll do that as soon as I have "My location" working.

FWIW, I've just tried "Organic maps", and "My location" works perfectly. I think it's time I create a bug report for "GMaps WV".
[Android Software Development] kurtn:
Tried on several devices. Nominatim is not needed. But a short signal from a location backend. After that the gmaps wv app can work with satellite location. If you don't want to share your location with mozilla, install déjà vu
[Android Software Development] jt12345:
I've just tried this using déjà vu and it "works". I still think that this is a bug, however, so I'll submit a bug report to the gmaps wv issue tracker. Thank you for the workaround - I will include this info in the bug report.
[Android Software Development] kuga22:
I just updated my Moto Edge 30 and now the fdroid store is empty. Updating the repos does not help. What can I do? (It also shows no installed apps)

Nevermind. Cleaning App Cacha and Data fixed it.
[Android Software Development] jt12345:
I clean-flash my chosen rom (*) onto my Oneplus 5T and then boot into system to make sure that everything is good. I then attempt to upgrade Services Core (from the included 0.2.24 to the current 0.2.27) : I reboot into TWRP, copy the latest Services Core apk over /system_root/system/product/priv-app/GmsCore/GmsCore.apk and reboot into system, but the phone does not complete its boot. After about a minute of boot animation, the phone reboots itself back into recovery (I think this is called the Android Rescue Party!)

What am I doing wrong? (I thought that over-writing the relevant apk with a later version was an acceptable way of upgrading microg. :unsure:) Also, if I should open a bug report, does anyone know the best place to do so?

(*) Yes, I know this is an old version, but that's the one I want.
[Android Software Development] ale5000:
You can update it by simply installing the apk inside Android.

If you really want to manually replace the apk in the system partitions you also have to edit the relevant xml for privileged permissions (and if needed also update the relevant extracted libraries).
[Android Software Development] jt12345:
Thank you. That was a lot easier. 🙏
[Android Software Development] mll2:
Hi,

I'm at loss as to where to report what could be bugs on LOS MigroG. Hopefully this is the right place. On my main phone (a Fairphone 3) that was on LOS 19 microG, I dirty flashed LOS 20 microG that went out about 4 or 5 days ago (https://download.lineage.microg.org/builds/full/FP3/lineage-20.0-20230403-microG-FP3.zip). The reboot went smoothly. However, the install of updated apps through Aurora would fail.

Thinking a reboot might solve this, I went for it, and alas, I get a bootloop (the animated LOS logo stays for a long time, eventually leading to a reboot). Reapplying the LOS4MG upgrade doesn’t fix anything. And today I realise that the build was withdrawn, and no other LOS4MG v20 is available yet (https://download.lineage.microg.org/FP3/). Is that withdrawal related to my issue? Any idea of what could be wrong? Is there any way to revert to a functioning phone (I fear that dirty flashing the latest LOS4MG 19.1 image would make things worse)?
[Android Software Development] ekcenraw:
I am also wondering why the latest build - for p7 [panther] in my case - has been withdrawn. Updated via ota and no issues so far other than an irregular high idle drain (~1%/h). Is it safe to use it going forward or should I revert? Any advice would be helpful. Thanks a lot in advance.
[Android Software Development] petefoth:
The latest builds have been withdrawn because if problems with F-Droid: see here for details. New builds should be along soon
[Android Software Development] ekcenraw:
Alright. Thanks for the quick reply. Will chase my drain issue elsewhere then:)
[Android Software Development] stephan_h:
Cool. Did people have success dirty-flashing today's build?
[Android Software Development] petefoth:
Sorry I don't know.
[Android Software Development] mll2:
So, https://download.lineage.microg.org/FP3/lineage-20.0-20230410-microG-FP3.zip is out, but I still bootloop.

Any clue as to get out of it without wiping + reflashing?

I see https://download.lineage.microg.org/FP3/lineage-20.0-20230407-microG-FP3-boot.img just got published, could it be of any use?
[Android Software Development] laritus:
Sorry, I don't quite understand. Now I have LineageOS 20, in guide installation need migration from LineageOS - LineageOS + microGaps. For this I just need boot in preinstall LineageOS recovery (not LIneageOS+microGapps recovery), factory reset and clear all Data, and then turn on ADB mode and install the LIneageOS+microGapps rom? Why then do the developers post the lineage-20.0-20230407-microG-kebab-boot.img and

lineage-20.0-20230407-microG-kebab-recovery.img?

Do they also need to be pre-installed before flashing lineage-20.0-20230412-microG-kebab.zip rom?
[Android Software Development] kurtn:
You have lineageOS or lineageOS with GApps? And dont say "mictoGaps" microG is no GApps.

I simply sideloaded lineage4microG like a normal update on official lineageOS without GApps.
[Android Software Development] laritus:
Yes, I have lineageOS (vanile) without Gapps. Thanks for your experience. Did you clear all data before installing lineage4microG rom? and what recovery did you use for the firmware?
[Android Software Development] kurtn:
I

I used lineage recovery and did no wipes.
[Android Software Development] mll2:
So, no clue, anyone? I feel like I'm gonna have to wipe & reflash, which would be annoying since I didn't backup my Signal history. :/
[Android Software Development] heinhuiz:
Did you have Magisk installed before you flashed? I recovered from a bootloop on a different device recently, by dirty flashing the same file again (freshly downloaded just to be sure) and then flashing Magisk.
[Android Software Development] mll2:
Yes I have. After the bootloop occured, I tried to reflash Magisk too, to no avail.
[Android Software Development] heinhuiz:
I'm not sure. I would try to flash the supplied boot.img first before doing a thing disastrous like a full wipe.

(Edit: removed a leftover sentence from an earlier reply.)
[Android Software Development] mll2:
Thanks for the advice. Flashing boot.img, I've never done. Any pointer on how to do this?
[Android Software Development] heinhuiz:
E

Easiest is straight from fastboot:

fastboot flash boot boot.img
[Android Software Development] mll2:
Thank you.

1. flashed https://download.lineage.microg.org/FP3/lineage-20.0-20230407-microG-FP3-boot.img

2. Rebooted => bootloop

3. Reflashing https://download.lineage.microg.org/FP3/lineage-20.0-20230410-microG-FP3.zip 🤞🏻
[Android Software Development] mll2:
@heinhuiz, still bootloops :(
[Android Software Development] heinhuiz:
Sorry, then I can't help. I assume you used the Lineage recovery to flash the rom?