yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] maxwell80:
It probably makes no difference..

I found this:

"Is there any difference between the Signal app on the Play Store and the website APK?

The only difference between the two is that the website APK includes some code that allows it to update itself if your device does not include the Google Play Store. Both the Play Store build and the website distribution build are signed by Signal's developers, both are open source and reproducible, both will use FCM for wakeup events if you have Google Play Services installed on your phone, and both will fall back on a WebSocket connection if your device does not include Google Play Services."

https://www.reddit.com/r/signal/wiki/faq#wiki_what_features_can_we_expect_in_the_future.3F

Sure, thank you!:good:

Regarding my Signal-delay-problem:

Is it safe to dirty-flash your lin14rom over this one?

Just to check whether it works there.

Or - another thought:

Could you imagine (if it made sense at all) to make just one unaltered Chil360 Lin16 -build with microG and your signature-key which could be dirty-flashed over yours to check Signals behavior there?

I really don't mind if you just say no...

I have an other issue:

Standort, Sensor- und Funknetzwerkstatus (App) always crashes.

logfile: https://www.file-upload.net/download-14097963/log.html

Regards,

M
[Moto G 2015 Android Development] MSe1969:
I don't think so. Of course you can try, but make a nandroid backup first. Even if the package signatures get reset properly, I seriously doubt, that the result will be usable.

But why dirty-flash? Make a nandroid backup, backup Signal and clean-flash - should be okay for some tests...

The key-word is "just"... To make a comprehensive explanation short, this is still a lot of work (if supposed to " make sense"), so my answer is no.
[Moto G 2015 Android Development] maxwell80:
Well, I thought it could be too much work..

I will do some testing as you suggested.

The crashing app I mentioned in my last post is called "Satstat"

Regards,

M
[Moto G 2015 Android Development] MSe1969:
Satstat (F-Droid version) works just fine on my osprey (Lineage 16.0 microG build Variant), all options as it should
[Moto G 2015 Android Development] maxwell80:
True - F-Droid Version works, App-Store Version does not.

Thank you!
[Moto G 2015 Android Development] MSe1969:
Was curious now and looked carefully: SatStat (com.vonglasow.michael.satstat) isn't offered outside F-Droid, the Play store however offers a fork of this app (as described in its docu), a package named com.drunkdeveloper.location.radio.network.wifi.status - receiving a lot of negative feedback due to app crashes.
[Moto G 2015 Android Development] nodens76:
Sorry for the late answer, but you were right. After some proper config in microG the force close seems to have disappeared.
[Moto G 2015 Android Development] maxwell80:
Hi MSe1969!

Regarding the issue with the delayed Signal messages:

I did some testing and can report that Signal works flawlessly with the LOs16-roms

of chil360 and althafvly (both with Magisk/ Nanodroid MicroG).

To double check, I did another fresh install of your rom and had delayed messages again. (I incidentally installed your first test build, so I flashed the migration build and made an update as recommended. I don't think that there is a difference to a clean install of your recent build so I didn't try.)

Best regards,

M
[Moto G 2015 Android Development] MSe1969:
Thanks for the additional tests!

Yes, the clean install doesn't make a difference, in the contrary, it excludes the possibility of a migration issue.

Will have to make some tests on my own then...

EDIT: I think I have misread your comment - you're saying that you went the migration path now - did you ever try a clean install?
[Moto G 2015 Android Development] MSe1969:
Repost from my cm-14.1 Osprey thread -as this is about my LineageOS 16.0 Osprey build (after migration):

I don't see that, but I am using the microG build myself.

Are you using Gapps and the "Standard" build?

I am aware of two commits for another msm8916 device in LineageOS, where two not really necessary Google services (Discovery service and nearby messaging service) are switched off in the device configuration - and this is said to solve your described issue. I'll include this in my next build.
[Moto G 2015 Android Development] maxwell80:
Not of the may-build (lineage-16.0-20200505-UNOFFICIAL-microG-signed-osprey)

But of this one: lineage-16.0-20200426-UNOFFICIAL-microG-osprey,

and the problem was there as well.
[Moto G 2015 Android Development] MSe1969:
OK, thanks - Will do some testing tomorrow
[Moto G 2015 Android Development] sponk0:
I'm using gapps and standard build, yes. Thanks a lot for looking into this. I'll test the next version once it's released and post my experience.
[Moto G 2015 Android Development] Pradeep1998:
Hii can you please build a microG los 17.1 same like this ,we all will be thankfull to you,and yes thanks for this rom,i appreciate your hard work.
[Moto G 2015 Android Development] MSe1969:
Eventually yes, but definitely not immediately. This will take some time to port the sec. features etc.

Besides "being happy having the latest & greatest", I do not really see any urgency to switch to Android 10 right now.

Some news for those of you keen on having default LineageOS 17.1: The Osprey device will soon get OFFICIAL LineageOS 17.1 support...
[Moto G 2015 Android Development] Pradeep1998:
Today i tried los 16 build but it had also same issue in location just like los17.1 with microG can you guide me how to get location services run with microG on los 16 & 17.1.but both are really so smooth with almost all things working its really gonna be so good if our ospery gets offical los 17.1 thanks....
[Moto G 2015 Android Development] MSe1969:
OK, I did now some testing with Signal on my Osprey device using a prepaid SIM and new registration. Despite microG, Signal said "no play services" and used the Background task method, which really works flawlessly, no delays at all.

On my OP3T (main device), Signal registers with microG and also works without delay. But previous versions of Signal also used the no-gms functionality, don't remember, when that changed...

I may have de- and re-installed Signal, as normally, Signal remembers the install decision and keeps it forever.

Some issue discussions on GH in the Signal app indicate difficulties with microG on some devices and it is e.g. said, that you could e.g. temporary switch off cloud messaging before installing Signal to force the no-gms option. (As said, Signal remembers this setting, even if you enable GMS again later)

So that's one workaround.

When you did your tests with chil360 and althafvly's 16.0 ROMs, did Signal register with microG or also use the no-gms functionality?

In case of microG registration, the only relevant difference to my build compared to your test setups would be the kernel. I have applied many sec. patches on top of chil360's kernel. Maybe there is an influence? (But then no chance to identify the reason, in general the kernel really behaves great)
[Moto G 2015 Android Development] MSe1969:
What issues do you have? Did you configure microG properly?
[Moto G 2015 Android Development] maxwell80:
If apps (in general - it is not a Signal issue, and I had this with the falcon as well and with every rom I ever flashed) do not register for Google Cloud Messaging, a (the) solution is to dial: *#*#2432546#*#* and reboot.

https://www.reddit.com/r/MicroG/comments/b3poti/apps_wont_register_for_gcmfcm_says_current_state/

Registration should work then, maybe check with an other app that uses GCM, for instance CX File Explorer, before installing Signal.

If you already have Signal running on it's own service, de-install it first.

Could you please check how Signal behaves then (with GCM)?

Regarding the workaround: I will think about it, it is just that I have other GSM-apps and would prefer just to use one always-on push service (for less battery drain(? No idea how much difference it makes))

Regards,

M
[Moto G 2015 Android Development] Pradeep1998:
Yes i configure corretly and also enabled signature spoofing,you can see the issue in this image,i am not able to enable the last option thats why location services are not working....
[Moto G 2015 Android Development] MSe1969:
On my Osprey, it works. However, what you show is not unknown to me. In fact, please consider 3 points:

1. You have of course to also configure the location provider(s) - different menu in microG settings

2. Location must be enabled and coarse location as well

3. It is normal first after the initial config that this last option is inactive, first of all reboot the device after first config and also, after reboot, sometimes it is necessary to launch an app (e.g. weather widget) making use of coarse location.
[Moto G 2015 Android Development] MSe1969:
I knew about *#*#CHECKIN#*#* and tried it as well, but I did not reboot, will try that later today and report back.

In regards to that background notification approach, this is the comment of Telegram-FOSS app: https://github.com/Telegram-FOSS-Team/Telegram-FOSS/blob/master/Notifications.md

Also based on my own experience, there is no significant battery drain - it might be slightly worse (Telegram-FOSS say no, Signal doesn't exclude the possibility of slightly worse battery), but not to a noticeable extent.
[Moto G 2015 Android Development] MSe1969:
UPDATE:

I de-installed Signal, re-downloaded newest version . I did *#*#CHECKIN#*#* and rebooted. Same result: Signal says "no play services". Other apps normally register (visible in microG) and testable as well (e.g. push notification tester).

Newest Signal version is 4.62.4

As said, the background notification method works w/o issues...
[Moto G 2015 Android Development] MSe1969:
New builds with June 2020 ASB

Hi all,

new builds with June 2020 sec. patches are available for download - they will also be offered for OTA update by the updater app within the next 30 minutes:

A. Standard LineageOS 16.0

https://sourceforge.net/projects/li...0200610-UNOFFICIAL-signed-osprey.zip/download

Sec. string 2020-06-05

System Webview on 81.0.4044.138

Kernel: Wireguard tag v1.0.20200520

Disabled NearbyMessagingService and DiscoveryService (only relevant, if genuine Gapps are used) to improve WiFi performance, when BT is used

B. Security hardened microG build

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

Sec. string 2020-06-05

Bromite Webview on 83.0.4103.101

Kernel: Wireguard tag v1.0.20200520

Sepolicy: Netmonitor exception f. "Tracker Control" app (microG build variant)

Note:

This month, no platform patches have been applied (only kernel has been updated with many sec. patches):

The AOSP tag android-9.0.0_r56, which was merged already in May, did already contain all patches, which were pushed again by Google in tag android-9.0.0_r57, which represents the June 2020 ASB.
[Moto G 2015 Android Development] sponk0:
I just updated to the latest June version using OTA ("standard" build with opengapps). Working great so far, and the Bluetooth fixes seem to do the trick. Now WiFi speed looks the same again no matter if Bluetooth is switched on or off. Great work, thanks a lot.
[Moto G 2015 Android Development] alanthelinuxguy:
Updates downloaded, installed, and working perfectly - as usual. Many thanks.

Alan
[Moto G 2015 Android Development] MSe1969:
Hi, thanks for the log - I think it's necessary to upload the entire log somewhere. In the pasted section I see the crash itself and the "chain reaction", but I am missing the "trigger" (so to say).

You indicate "constantly", and sine neither I have observed this nor got I so far this feedback from others, I right now assume something specific to your device. Have you flashed e.g. anything specific?
[Moto G 2015 Android Development] dSeta:
Yes, they happen constantly and randomly, it's not specific to an app. I didn't flash anything else besides the ROM.

I think I can't post links or attachments yet, so I uploaded to Mega: /file/6E8nGbKT#mX7jTanaNeSrcl1-sBKZBpXhcck6X2IS_D6yvchiniU
[Moto G 2015 Android Development] MSe1969:
Thanks for the whole log. I had a 1st look yesterday and again, I saw only the obvious, that surfaceflinger crashed (and then of course everything else can't work anymore either). But I haven't really seen any "trigger", i.e. any action before, which could have caused this (or I fail to see it) - is the log "complete" or was it somehow "filtered" or "edited"?

As I did not experience myself that behavior and so far nobody else stepped in to indicate similar issues, as said, I assume something specific to your situation.

You told already, that you cannot reproduce by doing anything specific and/or using a specific app, correct? You did not flash anything on top, either, you said.

Further, you even tried a clean install as well.

Right now, I can only make some "wild guesses":

- Have you played with any hardware settings in the developer options?

- Do you use any "extraordinary" app? I mean, I saw some well-known apps crashing in the log, but is there maybe some "cool" app promising something special amongst your apps, like a "cleaner" or "task manager"? Or some app, which you neither get on Playstore nor F-Droid? Could you e.g. create a list of your installed packages with the command "adb shell pm list packages" ? (You may not want to post that list here, so offering you to send a PM, if preferable for you)

- Do you use any app requiring root, which does not come with the ROM?

Edit: Oh, another potential cause of many weird crashes could also be a badly behaving SD card, maybe reformatting the SD card could be an option? Also, just in case, "adopted storage" also isn't really a good solution but rather a potential cause of trouble...?
[Moto G 2015 Android Development] dSeta:
- The only thing I edited out of the log was my Gmail account that appeared a couple times, everything else is untouched.

- I can't reproduce it intentionally, happened with almost every app that I use regularly.

- The only dev. options that I changed (and I've did this on every ROM I used) are:

• ADB

• Show taps

• Window animation scale .5x

• Transition animation scale .5x

• Animator duration scale .5x

• Kill app back button

- I don't use "task managers" or "cleaners", I know they don't really work. The only app I installed outside Aurora or F-Droid is ShuffleTone, which basically switches the ringtone every time I get a call. Worked correctly with LOS 14.1 and works correctly now. I'll PM you the package list.

- None of the apps I use require root.

- I stopped using SD cards because my device always killed them (couldn't write in them anymore), but from what I've read, it's something normal on this model. Now I only use it for flashing, but as soon the system is running, I remove it.
[Moto G 2015 Android Development] MSe1969:
Nothing wrong with the mentioned dev options IMO. The app list doesn't show anything special, either. Of course, I don't know every app in action... So no good idea really at the moment.
[Moto G 2015 Android Development] dSeta:
Ok then. Thanks for taking the time of trying to solve the problem anyways. I'll try to redownload the ROM and perform a clean install. Hopefully it'll solve the problem.
[Moto G 2015 Android Development] @VelcronSpecter:
Using the latest build, after unlocking the phone using the PIN option, I get black screen sometimes. It is solved by restarting the phone. Any other solution than that?
[Moto G 2015 Android Development] MSe1969:
Hi, as I do not observe this on my device, it would be helpful to somehow have a log. Also, any info regarding the device specifics (e.g. build variant, anything flashed on top of my build) is needed. Finally, does this behavior also occur, if you perform a clean install?
[Moto G 2015 Android Development] phool4XC:
The OTA update for Build B went flawlessly, and the device is working perfectly, as expected. Thank you!
[Moto G 2015 Android Development] MSe1969:
[MENTION=10762195]maxwell80[/MENTION] :

I think this pull request to microG contains the explanation for the issue that Signal wouldn't register for push messages with FCM and uses its fallback.
[Moto G 2015 Android Development] maxwell80:
Thanks! - that that explains a lot. (Though not all ;))

The Signal push service works fine for me.
[Moto G 2015 Android Development] MSe1969:
Just created a test build using the prebuilt microG GmsCore from /e/ which has the respective pull request (and others) to fix the push registration.

I deinstalled Signal and reinstalled.

Result: Registered with FCM and there seem no delays. :good:

So in my next build this updated microG version will be present.
[Moto G 2015 Android Development] alanthelinuxguy:
I have found one item that no longer works on my Moto G3 - the flashlight app. In addition, the flash on the camera doesn't work. So, is this a problem with the build, with my Gapps add-on, or with my particular phone (i.e. the LED is dead)? Does anyone have the flash LED working under the June 2020 release?

Alan
[Moto G 2015 Android Development] MSe1969:
On my Osprey, the flashlight works w/o issues (June build). Just tried camera and torch tile in pull down.
[Moto G 2015 Android Development] alanthelinuxguy:
Many thanks for checking. Since the LED light is working for you, it seems likely that the problem is that my specific phone is starting to fail. Right now, the loss of LED functionality isn't a huge problem for me as I don't use the flashlight or the camera flash on any regular basis. So, I will soldier on with the old (by current standards) device - and look forward to your July update!

Alan
[Moto G 2015 Android Development] MSe1969:
New builds with July 2020 ASB patches

Hi all,

new builds are up and will soon be offered also as OTA update:

A. Standard LineageOS 16.0

https://sourceforge.net/projects/li...0200712-UNOFFICIAL-signed-osprey.zip/download

ASB Security string 2020-07-05

Kernel: Wireguard tag v1.0.20200623

B. Security hardened microG build

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

ASB Security string 2020-07-05

Kernel: Wireguard tag v1.0.20200623

microG: updated prebuilt GmsCore fom /e/ project to fix FCM registration issues (fixes also the delay with Signal messenger)

F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11

Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

Happy flashing - cheers, M.
[Moto G 2015 Android Development] alanthelinuxguy:
Downloaded and installed the July file with no issues. Many thanks

Alan
[Moto G 2015 Android Development] jemail:
Clean installed July ROM for testing.

Selecting wallpapers, scrolling is very jerky, it improves once you scroll past images to solid colour selection.

I will edit this post as I continue testing.

Battery drain is acceptable, however some times the phone has difficulty waking from sleep.

Haven't experienced any show stopping bugs so far.
[Moto G 2015 Android Development] jemail:
In settings for clock, alarm flip to snooze and shake to dismiss do not work for me.

Can anyone confirm this?
[Moto G 2015 Android Development] phool4XC:
Build B installed OTA flawlessly. Thanks!
[Moto G 2015 Android Development] MSe1969:
New builds with August 2020 ASB patches available

Hi all,

new builds are up and will soon be offered also as OTA update:

A. Standard LineageOS 16.0

https://sourceforge.net/projects/li...0200809-UNOFFICIAL-signed-osprey.zip/download

ASB Security string 2020-08-05

Kernel: Wireguard tag v1.0.20200729

System Webview on 84.0.4147.89

B. Security hardened microG build

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

ASB Security string 2020-08-05

Kernel: Wireguard tag v1.0.20200729

Bromite Webview on 84.0.4147.113

The location of the firewall functionality has moved to Network > Data usage in Settings (latest cherry-pick from here)

Happy flashing - cheers, M.
[Moto G 2015 Android Development] alanthelinuxguy:
Latest build downloaded and installed. Working normally. Many thanks.

Alan
[Moto G 2015 Android Development] KamiOh:
i have issues with last update.

Sorry my english. i don't wanna soft-reset T_T

solution?

Edit:

I can't activate data mobile. T_T
[Moto G 2015 Android Development] MSe1969:
I did not see that, when testing the new build with my own device.

Which build variant do you use? Do you use Magisk? How did you upgrade? OTA? Or manual flash?
[Moto G 2015 Android Development] KamiOh:
1. Variant B

2. yes i use magisk

3. OTA
[Moto G 2015 Android Development] Ritik99:
× Navigationbar and statusbar not working after random restart MotoG3 ×

MotoG3 system files are something quite sensitive, then restarts sudden or just even random occasions end up causing a bug in the system where the Home and Menu buttons do not work, the status bar does not come down completely and your shortcuts do not work, options developers and mobile data too.

You need Root for this :

1 - Download and install Terminal Emulator.

2 - In Terminal, type su, then press enter and give access root to the application.

3 - After this, copy the following and paste it in Terminal (confirm by pressing enter):

settings put global device_provisioned 1

4 - Finally, do the same with this code:

settings put secure user_setup_complete 1

Your phone will return to normal.

Try this, it might help.
[Moto G 2015 Android Development] MSe1969:
You may find the below linked post interesting:

https://xdaforums.com/sony-xperia-z...z1-compact-t3886233/post83288853#post83288853

If your device is encrypted AND you use Magisk AND you have TWRP 3.3.x, better manually flash the update, instead of OTA.

But in any case please try, what has been recommended by [MENTION=7301699]Ritik99[/MENTION]
[Moto G 2015 Android Development] KamiOh:
works!!! :good:

thanks so much!!

my cell phone is not encrypted.

When I updated the rom, it was using twrp 3.2.1.0.

I upgrade to 3.4.0.0 now = D
[Moto G 2015 Android Development] jemail:
I'm seeing an "Update verification failed." error message when I try to download the update using the LineageOS updater. I'm trying to update to latest build dated August 2020.

Any ideas what is causing this?

I'm also seeing a similar problem on my falcon.
[Moto G 2015 Android Development] MSe1969:
As others don't report updater issues AND you tell me it happens to you with two ROMs, I could think of two potential reasons:

- temporary issue with sourceforge.net (where the update files are stored)

- the system time of your mobile device(s) is out of sync
[Moto G 2015 Android Development] MSe1969:
New builds with September 2020 ASB patches available

Hi all,

new builds are up and will soon be offered also as OTA update:

A. Standard LineageOS 16.0

https://sourceforge.net/projects/li...0200912-UNOFFICIAL-signed-osprey.zip/download

ASB Security string 2020-09-05

Kernel: Wireguard tag v1.0.20200908

System Webview on 85.0.4183.101

B. Security hardened microG build

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

ASB Security string 2020-09-05

Kernel: Wireguard tag v1.0.20200908

Bromite Webview on 85.0.4183.86

Added eSpeak TTS engine (FOSS TTS solution)

Happy flashing - cheers, M.
[Moto G 2015 Android Development] alanthelinuxguy:
September update has been installed and is working flawlessly as usual. Many thanks.

Alan
[Moto G 2015 Android Development] mach07:
Installed without any problems. The ROM is awesome! Light, fast, and clean.

Thank you for this!!!