Feedback of A1 Pro

Auto_art

another issue I am facing is GPS, A1 pro GPS is very poor. I kept another phone side by side and used gpstest application to measure the signal.

Auto_art

jonsmirl replied at 2018-7-10 16:58
Any progress on this? The broken code is in kernel/drivers/usb/gadget/function/android,c  
You are l ...

I left it to UMIdigi to fix it or honor some compensation to users, the choice is their.
everyone cannot do the good stuff you do Jon.

JohnnyBishop

Ok, an update:
1. at some point Wifi has reconnected on its own, but I don't have confidence the phone is using wifi while I am at home and uses my mobile Internet instead.
I see Wifi coming on and off and I don't even move my phone. AP is 1 meter away.

2. solution for Bluetooth devices is
   a). the devices has to be paired
   b). the only way to connect to a Bluetooth device is to turn it on 1st then TURN ON Bluetooth on A1 Pro otherwise it does not work or takes so long I am already fed up waiting

3. Waze is probably crashing because of poor GPS mentioned by Auto_art
4. the battery is still draining pretty quickly and I have no information of what is using the battery the most

jonsmirl

JohnnyBishop replied at 2018-7-12 06:06
Ok, an update:
1. at some point Wifi has reconnected on its own, but I don't have confidence the pho ...

Download 'Android Studio' from Google. It will install the adb command. Plug your phone into your PC with a USB cable (this works on both Windows and Linux). Now use a terminal and type "adb logcat'.  That will give you a huge amount of debug information about what is going on with Bluetooth and Wifi.  If you are lucky there will be obvious error messages telling you what is wrong.

Random output from my phone

1. jonsmirl@ares:~$ adb logcat
   
2. * daemon not running. starting it now on port 5037 *
   
3. * daemon started successfully *
   
4. --------- beginning of crash
   
5. 07-10 15:26:37.599  8086  8131 E AndroidRuntime: FATAL EXCEPTION: pool-2-thread-1
   
6. 07-10 15:26:37.599  8086  8131 E AndroidRuntime: Process: com.adups.fota, PID: 8086
   
7. 07-10 15:26:37.599  8086  8131 E AndroidRuntime: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.adups.fota/.ReportIntentService }: app is in background uid UidRecord{e5d325e u0a39 CEM  bg:+13m27s991ms idle change:idle procs:1 seq(6,6,6)}
   
8. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1522)
   
9. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at android.app.ContextImpl.startService(ContextImpl.java:1478)
   
10. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at android.content.ContextWrapper.startService(ContextWrapper.java:650)
    
11. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at com.adups.fota.update.d.b$3$2.a(ReportManager.java:295)
    
12. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at com.adups.fota.update.d.b$2.run(ReportManager.java:107)
    
13. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
    
14. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
    
15. 07-10 15:26:37.599  8086  8131 E AndroidRuntime:         at java.lang.Thread.run(Thread.java:764)
    
16. 07-11 02:32:44.939 17402 17402 E AndroidRuntime: FATAL EXCEPTION: main
    
17. 07-11 02:32:44.939 17402 17402 E AndroidRuntime: Process: com.adups.fota, PID: 17402
    
18. 07-11 02:32:44.939 17402 17402 E AndroidRuntime: java.lang.RuntimeException: Unable to stop service com.adups.fota.ht.internal.ht.cat.CatService@9de869e: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.adups.fota/.ht.internal.ht.cat.CatService }: app is in background uid UidRecord{6700b1d u0a39 SVC  bg:+1m0s9ms idle change:idle procs:1 seq(0,0,0)}
    
19. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at android.app.ActivityThread.handleStopService(ActivityThread.java:3549)
    
20. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at android.app.ActivityThread.-wrap26(Unknown Source:0)
    
21. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1721)
    
22. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at android.os.Handler.dispatchMessage(Handler.java:106)
    
23. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at android.os.Looper.loop(Looper.java:164)
    
24. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at android.app.ActivityThread.main(ActivityThread.java:6523)
    
25. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at java.lang.reflect.Method.invoke(Native Method)
    
26. 07-11 02:32:44.939 17402 17402 E AndroidRuntime:         at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
    

Copy the Code

jonsmirl

I just read that dump I posted... our phones are infected with malware that is opening a back door.

https://blog.malwarebytes.com/cy ... -adups-old-and-new/

jonsmirl

This has to be installed at the factory. I only have three apps installed on my phone

jonsmirl

More info on adsups...
http://www.kryptowire.com/adups_security_analysis.html

jonsmirl

I am unable to disable these without rooting the phone....
jonsmirl@ares:~$ adb shell 'pm disable com.adups.fota.sysoper'
Error: java.lang.SecurityException: Shell cannot change component state for com.adups.fota.sysoper/null to 2
jonsmirl@ares:~$ adb shell 'pm disable com.adups.fota'
Error: java.lang.SecurityException: Shell cannot change component state for com.adups.fota/null to 2
jonsmirl@ares:~$

JohnnyBishop

\n\nthis looks serious

I have the same on mine:

1. 07-12 00:18:18.625  1817  2880 I ActivityManager: Process com.adups.fota.sysoper (pid 7461) has died: cch+4CEM
   
2. 07-12 00:18:18.673  1817  2387 I ActivityManager: Process com.adups.fota (pid 7446) has died: cch+6CEM
   

Copy the Code

bencebacsi

jonsmirl replied at 2018-7-12 06:58
I am unable to disable these without rooting the phone....
jonsmirl@ares:~$ adb shell 'pm disable co ...

Adups Fota is the OTA update utility, it's not a malware and you should not disable it if you want to get wireless updates in the future. Some versions of it were infected by a backdoor thread in 2016(!) but no UMIDIGI devices were involved. Here's the related statement by Adups: https://test.adups.com/article/show_article.php?id=162