problems after latest 64bit update. zoom + app stopping

[zohar]

I’ve updated to the latest 64bit system and now I’m having two problems:

1) If I change the zoom level of the display, the display gets totally distorted!
I had my boot.ini setenv zoom_rate "90", so a minute after the system loaded I had the display unusable.
Could only fix this by setting it to 100 (and now I don’t see the edges of the display)

IMG_20200124_171545.jpg (144.91 KiB) Viewed 987 times

2) While on the desktop I keep getting an error:
“android setup keeps stopping” with “app info” and “close app” option


Is there a way to revert to previous update?

[Luke.go]

I'm sorry that this update caused abnormal behavior.
Can I know your resolution setting value?
And if you can get the logcat message, Please Share the logs to find clues.

[zohar]

I'm using 1080p60Hz
I've tested many other resolutions and they all have the same effect when zoom takes place (1080p50hz, 720p60hz, 480p50hz)

I will be very happy to send logcat or run any other test that you may need.
I just don't know how to get the logcat. I've installed "logcat reader" app, but it needs root (I don't have) or ADB command (not sure how to connect the N2 to my PC).
I also saw that there are many switches to logcat.
Is there some instruction about how to get the needed logcat?

Also the error messages from android setup stops after some time (currently, while the system is running for some days I don't have any of them)

Thanks,
Zohar

[Luke.go]

I'm using 1080p60Hz
I've tested many other resolutions and they all have the same effect when zoom takes place (1080p50hz, 720p60hz, 480p50hz)

I will be very happy to send logcat or run any other test that you may need.
I just don't know how to get the logcat. I've installed "logcat reader" app, but it needs root (I don't have) or ADB command (not sure how to connect the N2 to my PC).
I also saw that there are many switches to logcat.
Is there some instruction about how to get the needed logcat?

Also the error messages from android setup stops after some time (currently, while the system is running for some days I don't have any of them)

Thanks,
Zohar

The zoom in/out problem will be solved in next release.

[Luke.go]

Please check it on the latest update!

[zohar]

Please check it on the latest update!

Thanks,
Latest update fixed the zoom problem.

I still get the “android setup keeps stopping” it appears for ~3 times and then stops.
Would have sent a log cat if I had a clue how to get it.

[Luke.go]

Oh, Please Connect Odroid-N2 via OTG cable.
And,

Code: Select all

$ adb logcat

if you faced permission problem, you should set the permission.

please follow the wiki page.
https://wiki.odroid.com/getting_started/adb_fastboot

[zohar]

Oh, Please Connect Odroid-N2 via OTG cable.
And,

Code: Select all

$ adb logcat

if you faced permission problem, you should set the permission.

please follow the wiki page.
https://wiki.odroid.com/getting_started/adb_fastboot

Is it safe to use a normal USB to uUSB cable to connect my laptop to the N2?

Sent from my ONEPLUS A5010 using Tapatalk

[Luke.go]

Oh, Please Connect Odroid-N2 via OTG cable.
And,

Code: Select all

$ adb logcat

if you faced permission problem, you should set the permission.

please follow the wiki page.
https://wiki.odroid.com/getting_started/adb_fastboot

Is it safe to use a normal USB to uUSB cable to connect my laptop to the N2?

Sent from my ONEPLUS A5010 using Tapatalk

Just check the OTG port type. It is safe the cable if that match the type.

[zohar]

Just check the OTG port type. It is safe the cable if that match the type.

I could not get the OTG cable to work, but found out that I can do it over the network:
adb connect 192.168.nn.mm
adb -s 192.168.nn.mm:5555 logcat > ./logcat.txt

sending you the output in PM

[Luke.go]

Just check the OTG port type. It is safe the cable if that match the type.

I could not get the OTG cable to work, but found out that I can do it over the network:
adb connect 192.168.nn.mm
adb -s 192.168.nn.mm:5555 logcat > ./logcat.txt

sending you the output in PM

Did you certified your android device after install the Open Gapps?

[zohar]

I'm pretty sure I did.
I remember that before don't it, the android keeps beeping and popping errors.
I have Device ID app installed (So I probably used it).
I'm logged into the play store.
I have no strange errors (except for the "android setup keeps stopping" after bottling)

----
strange, under pay store -> settings -> play protect certification" I have "device is not certified"
searching to see what need to be done...

[zohar]

According to here:
https://www.xda-developers.com/how-to-f ... gle-error/
"Your device will still say it is uncertified in the Google Play Store settings. This is normal. All this fix does is white-list your uncertified device so you can still use Google apps and services."

So I believe that I'm relay certified.
Is there any way to check this for real?

[IgaBiva]

I updated my N2 Android 64bit yesterday and I also have this annoying “android setup keeps stopping” error. It pops up couple of times and than stops. However, If I enter settings or plug in controller or USB drive, it comes again.

Any idea on how it could be solved? Based on a comments, couple of people are affected by this issue.

[codewalker]

Do you use either an eMMC or a SD card?
Do you install GMS apps?

If you provide your logs, It can help us solve that problem.

I updated my N2 Android 64bit yesterday and I also have this annoying “android setup keeps stopping” error. It pops up couple of times and than stops. However, If I enter settings or plug in controller or USB drive, it comes again.

Any idea on how it could be solved? Based on a comments, couple of people are affected by this issue.

[IgaBiva]

I am using sdcard and i have installed nano Gapps - I don't know if GMS apps are part of this package. This was not an issue before last update.

I will provide logs as soon as I can.

[codewalker]

We forcely recommand to use eMMC for android.
I guess If you use eMMC, there are no more Dialog abort Settings.

When system is busy, ANR( Stopped Message) dialogs appear.

I am using sdcard and i have installed nano Gapps - I don't know if GMS apps are part of this package. This was not an issue before last update.

I will provide logs as soon as I can.

[IgaBiva]

We forcely recommand to use eMMC for android.
I guess If you use eMMC, there are no more Dialog abort Settings.

When system is busy, ANR( Stopped Message) dialogs appear.

Yes, this would be nice but eMMC is reserved for CoreELEC whic is active 80% on my N2.

I beleve that this has something to do with Settings app. One of users mentioned that he reinstalled app and after that error was gone. However, for this I would need root and I have not rooted my image yet.

Logs are here https://write.as/8rd8vczghepzy.md, maybe you will be able to see something.

[Sholander]

I beleve that this has something to do with Settings app. One of users mentioned that he reinstalled app and after that error was gone. However, for this I would need root and I have not rooted my image yet.

If you want, I can send you the Odroid Settings app from /vendor/apps folder so you can side-load it and see if that will fix your problem.

[zohar]

I'm also with SDcard and none root.
I've sent the logcat to luck.go in PM

Sent from my ONEPLUS A5010 using Tapatalk

[IgaBiva]

If you want, I can send you the Odroid Settings app from /vendor/apps folder so you can side-load it and see if that will fix your problem.

Thank you but I tried that and it did not help. Maybe some older version of app would work better.

I have tried SlashTV Android (HK version plus some additional software) and situation is same. Before update everything fine, after update same issue - tested on a different SD card.

[IgaBiva]

After playing around with this error, I have installed LineageOS 64Bit - zero problems so far. I think that I will stick with it for a while.