There's a port of native Xperia cam app as a Magisk module: https://gitlab.com/xperiance/camera/-/releasesI'm searching camera apk that have all in one ( slow motion, photosphere, selfie with powerfull flash screen).
I flashed the zip file with magisk and the camera apk disappeared from my device! so i deactivated and removed the module from magisk and restart, but now i have it again but it doesn't work anymore! she says: unknown error. Did I make a mess?There's a port of native Xperia cam app as a Magisk module: https://gitlab.com/xperiance/camera/-/releases
Try installing the module againI flashed the zip file with magisk and the camera apk disappeared from my device! so i deactivated and removed the module from magisk and restart, but now i have it again but it doesn't work anymore! she says: unknown error. Did I make a mess?
Ok, finaly I got the 18.1 Version from 16.5. to restart. I picked the "mobile data"-tile from the quick-Start-ButtonsYes, I missspelled it: I mean the 18.1 from 15.6.
Sadly, I'm not quickly able to reproduce - in German we say "Vorführeffekt". I keep it trying to reproduce!
Maybe we also catch the "do not signe-in into the LTE-Network while in VoLTE mode" - as I still have the problems with telefonica-germany reseller blau.de after restart or cellswitches while beeing out of reception - like in my employers basement parking lot. This problem was discussed earlier, but did not resolve for me, without temporarily limiting to g3.
I have re-uploaded the builds (17.1 & 18.1) builds to https://www.androidfilehost.com/?w=files&flid=322414 and downloads seem to be working (for now at least)Tried to download 18.1 unofficial version,but no mirrors found.
That would be amazing - Los19 + MicroGThanks. I prefer not to root my phone, and the aim is to have microG working "out of the box". The 19.1 ROM looks good though - I'll keep an eye on it, and maybe try a 19.1 LineageOS for microG build when I get some time.
Now require login for download?I have re-uploaded the 18.1 builds to https://androidfilehost.com/user/?w=settings-dev-files&flid=322414 and downloas seem to be working (for now at least)
I will re-upload the 17.1 builds soon
Not if I post the correct link, which is https://www.androidfilehost.com/?w=files&flid=322414
1. What officail ROM version did you had before installing lineage ?Hi, I'm from the official rom. After flashing lineageos, I can only boot into the system with a complete black screen. I'm quite new to lineageos so I want to know if I did anything wrong or missed something.
Here's what I did:
1. Unlocked BL and flash TWRP (tried the above 3.3.1, 3.5.0 links and the latest one, no luck)
2. Wiped my data(tried wiped + format, no luck)
3. Install lineage 17.zip
After rebooting, I can see the reboot animation with the lineago logo, hear the sound and the vibration if I press the power bottom. But I can only see a black screen with no wallpaper or any apps.
4. I also tried to install lineage+opengapps ( arm64, nano, 10.0, 20220215).
After rebooting, I'm at the "Hi there" start screen and can choose different languages, after I choose english and hit start, I would stuck in the "just a sec" screen and my device keeps rebooting, I just see the lineageos logo and the "just a sec" screen
I also downloaded the md5 file and checked it myself, and my download is complete.
Thanks in advance
Yes, also for me, lineageos 17 is the only best and stable rom in the world in this moment.....Thanks! So far I've seen no issues with the July update. It's still such a great phone! Fingerprint sensor in the power button and it's just small yet reasonable specs. Thanks so much for keeping it alive!
Has anyone else faced issues where the phone shows the wrong date/time on startup?
On a fresh boot, the time is 9:58am on Saturday 18 September. It stays like this for approx 15 seconds until it finally updates to the current time (using network sync).
However, if I keep the phone on airplane mode, the time stays wrong until I disable airplane mode.
I'm wondering if this is a bug
I'll update this post if and when I have more information.
- with the most recent version of the ROM (I'll try with last month's version as well)
- with the GApps package I'm using (I'm using the mini package which replaces stock clock with google clock)
----
Update 1: Reflashed the September ROM with a smaller GApps package (micro instead of mini) and date/time issue still shows up. So GApps and the Google Clock isn't to blame. I'll try August ROM and see what happens.
Update 2: Flashed the August ROM and the datetime issue still persists.
Update 3: I'm attaching steps on how to reproduce this and I'd be really interested to see if anyone else is able to reproduce this:
- Make sure your phone's time is currently normal/correct
- Put phone into airplane mode
- Reboot phone
- Time should now be wrong on startup
- Disable airplane mode, time should now be updated once network connectivity is back
I'm using that ROM (17.1) myself on my daily device and haven't encountered any issues at all. So looks like something with your device, not the ROM itself.Hello, now in latest update of LOS 17.1 for lilac 02/25 (clean install) I am experiencing random UI reboots and one bug:
If i turn off device and turn on (no reboot), system sounds arent working, freeze and FC when i want to set an alarm in clock app or play music, no flashlight, camera cannot start and maybe something else which i havent noticed.
[...]
I dont know if someone has similar problems, but this is strange.
I assume you are (still) using 17.1 as you mention the Sony camera app. I'm a bit confused: Above you said that the camera cannot start.Now battery lasted 3 days +20% with 5hrs SOT, very nice ! No gapps.
2 more bugs:
Camera taking blank photos if default storage is set to sd card.
Front camera gives white screen, freezes, FC and then i cant open camera when is flashlight turned on.
Maybe it is related only to Sony camera app, i havent tested other camera apps.
Answered there (a link to the issue in your post would be helpful as I don't get a notification on GH, but found it anyway): In short: It does work (I always do clean builds, by now 6 times), check your extracted system imageThis update seems to have broken extract-files.sh, preventing a clean build from source. Reported on github as issue 13.
Thanks for the reply! I actually think they use slightly different storage formats, so next time backing up to the SD card may be worth a try.First, my TWRP backups were all done from within TWRP with the phone running in Recovery, not using `adb backup --twrp` so I don't know if they two methods are functionally equivalent.
Maybe I'm misunderstanding the question, but my problem is exactly that I can't boot the restored backup unless I format the restored data partition... at which point it wouldn't be my original setup anymore. (The backup I created covers all partitions, and adb does not support partial restores)Are you able to get back to your original setup (i.e. your custom ROM, with your backup restored?
Yeah I've read about this project after the failed backup as well. Looks like another good line of redundancy in addition to SeedVault and partition backups.My '"if all else fails" backup' is to backup using Android Backup and Restore Tools project. You need rooted debugging enabled, and access to a Linux machine (real or virtual). I have used these scripts to backup my apps and data and then to
Not everything gets retored - any apps whose account data is handled by Accuont Manager (e.g DAVx5, NextCloud) will lose the account settings, as will K-9 Mail (though you can export your settings before the backup, and re-import them after the restore). See this post in the /e/OS community forums for more information on my experiences with this.
- Restore to the same device, running the same or different custom ROM
- Restore / migrate to a completely new / different device
Looks like something went wrong on my side and the apps were missing from the (source) where they were supposed to be. Not sure why.I did a clean flash of 19.1 2023-02-25 MicroG from stock and I can't seem to find the settings for MicroG and don't see it listed in the system apps.
When I check in /system/product/priv-app I see the folder for GmsCore and the fake store, but there is no apk in it.
Is there additional setup needed in order to get MicroG working?
There isn't a real fix yet, this happens after reboot or some time without network (e.g. Tunnel or basement)But I am on 19-20220918 - which version does fix this (or is it something completely different I'm experiencing?)...