help!some problems need to be solved

[FlyingHarman]

3 problems

log in via nextcloud account,then crashed.but when I finish pre-app auth I could via nextcloud account so I just wonder why？test in android ver 11

(android ver 11 or 12)no any notification popup on screen,but only can see notification when open app;(android ver 9 or 10)—working well

long time lock screen then foreground service will be killed?service is not running but If I want to start service,nothing but reboot???

plz consider what I said and make it compatable with lateset SDK

[0xf104a]

Hello. Please tell more about your ROM: what is your vendor lineage/carbon/crdroid/dotOS/etc. and ROM version? Also check that agressive battery optimization is disabled for the app(From launcher(if you use QuickStep or its fork): Long press on app > About app > Battery > Background activity limit)

[FlyingHarman]

Hello. Please tell more about your ROM: what is your vendor lineage/carbon/crdroid/dotOS/etc. and ROM version? Also check that agressive battery optimization is disabled for the app(From launcher(if you use QuickStep or its fork): Long press on app > About app > Battery > Background activity limit)

Made by Chinese,I think its customsize ROM base on Android 11 by manufactor....maybe its hard for u to make it?

[0xf104a]

Unfortunately chineese ROMs are usually over-customized and theirs SDK differs from AOSPs SDKs. They may do not support some features either intentionally or just because developers misunderstood documentation.
I think that problem is that some vendor app(like "Phone Manager" or something else) tries to optimize background activity even when notification is shown and so crashes the app. Also you can try to send logs of app here( Enable developer mode and then on Linux do adb logcat | grep com.polar or use Android Studio/any Android logcat viewer) and I will try to figure out what happens(but remember that logs may contain private information, so look through before you send them).
Additionally as I see that you are using stock ROM, so probably Google Play services are installed there and so Nextcloud should send notifications without this app. Does your Nextcloud app works correctly?

[FlyingHarman]

Unfortunately chineese ROMs are usually over-customized and theirs SDK differs from AOSPs SDKs. They may do not support some features either intentionally or just because developers misunderstood documentation. I think that problem is that some vendor app(like "Phone Manager" or something else) tries to optimize background activity even when notification is shown and so crashes the app. Also you can try to send logs of app here( Enable developer mode and then on Linux do adb logcat | grep com.polar or use Android Studio/any Android logcat viewer) and I will try to figure out what happens(but remember that logs may contain private information, so look through before you send them). Additionally as I see that you are using stock ROM, so probably Google Play services are installed there and so Nextcloud should send notifications without this app. Does your Nextcloud app works correctly?

well.let me try later.unfortunately,both Play Store and Play Servcie not working in chinese Rom because of limit unknown

(android ver 11 or 12)no any notification popup on screen,but only can see notification when open app;(android ver 9 or 10)—working well

how about this?why happened?because of over-customized? but it begin to working well on my friend's phone(ver 12) in 16 hrs when installed,that's so wired!!!!!!

Status:i/o error time out how can I fix it?

[FlyingHarman]

May I help u to translate into Chinese?

[0xf104a]

Sorry for long response. Yes, if you are able to help with translations you are welcome and I will be really grateful to you for your work.
In order to translate you need to fork this repo, clone it to your machine and then create a folder app/src/main/res/values-<LOCALE, e.g. cn>(not sure whether there is only one Chinese locale) and copy app/src/main/res/values/strings.xml to this folder. After this you need to translate strings in app/src/main/res/values-<LOCALE>/strings.xml, commit and push changes and create pull request(I also can merge your changes to this repo after you push it)

[0xf104a]

how about this?why happened?because of over-customized? but it begin to working well on my friend's phone(ver 12) in 16 hrs when installed,that's so wired!!!!!!

This strange behavior is also observed on Huawei, but one with Google Play services. One of users of my Nextcloud have experienced troubles with getting notifications within official app: they usually came too late, despite Google Play services were working well. The issue was that for some reason "Phone Dispatcher" has optimized Google Play services and was constantly killing its' connection to Google. So the problem may be exactly that developers are trying to prolonge battery life by killing background processes. This also can affect my app as it constantly holds internal connection to Nextcloud app or external(depending on settings) to your Nextcloud instance. So if you can you need to disable all optimizations for this app and also try logging-in not with Nextcloud app it self, but with instance, login and password, since it reduces notification polling scheme from:
NextcloudServices -> Nextcloud App -> cloud.example.com
to:
NextcloudServices- > cloud.example.com
and so reduces probability that system will optimize the app in order to save battery.