Feedback of A1 Pro

jonsmirl

\n\n

jonsmirl replied at 2018-7-6 11:40
A problem with the USB audio configuration is breaking Android Auto. Here is a capture of the USB  ...

To test this, use this program to enable USB audio out on the phone:
https://github.com/gibsson/linux-adk

jonsmirl@ares:~/aosp/linux-adk$ ./linux-adk -d 0e8d:201c
Looking for device 0e8d:201c
Device supports AOA 2.0!
Sending identification to the device
sending manufacturer: Google, Inc.
sending model: DemoKit
sending description: Demo ABS2013
sending version: 2.0
sending url: https://github.com/gibsson
sending serial number: 0000000012345678
asking for audio support
Turning the device in Accessory mode
Found accessory 18d1:2d05
Device should now be recognized as valid ALSA card...
  => arecord -l
Unable to open usb device [0xfffffffd]
^CSIGINT: Closing accessory
Closing USB device
----> now the device is in USB audio output mode ----
jonsmirl@ares:~/aosp/linux-adk$ ls /proc/asound
A1PRO  card0  card1  cards  devices  hwdep  modules  oss  PCH  pcm  seq  timers  version
jonsmirl@ares:~/aosp/linux-adk$ ls /proc/asound -l
total 0
lrwxrwxrwx 1 root root 5 Jul  6 09:18 A1PRO -> card1
dr-xr-xr-x 8 root root 0 Jul  6 09:18 card0
dr-xr-xr-x 3 root root 0 Jul  6 09:18 card1
-r--r--r-- 1 root root 0 Jul  6 09:18 cards
-r--r--r-- 1 root root 0 Jul  6 09:18 devices
-r--r--r-- 1 root root 0 Jul  6 09:18 hwdep
-r--r--r-- 1 root root 0 Jul  6 09:18 modules
dr-xr-xr-x 2 root root 0 Jul  6 09:18 oss
lrwxrwxrwx 1 root root 5 Jul  6 09:18 PCH -> card0
-r--r--r-- 1 root root 0 Jul  6 09:18 pcm
dr-xr-xr-x 2 root root 0 Jul  6 09:18 seq
-r--r--r-- 1 root root 0 Jul  6 09:18 timers
-r--r--r-- 1 root root 0 Jul  6 09:18 version
jonsmirl@ares:~/aosp/linux-adk$ arecord -D hw:1,0 -c 2 -r 44100 -f S16_LE ~/foo.wav
Recording WAVE '/home/jonsmirl/foo.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
arecord: set_params:1363: Unable to install hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 88200
TICK_TIME: 0


Look at dmesg and note that arecord fails because it can not set the interface.
This is the same procedure Android Audio uses to play audio, it just doesn't need a car.

Here is the correct output from my Google Pixel (also running Oreo)...
Pixel is working without problem. It is also USB-C.Also note that this works correctly on the Nokia-1 which is running Mediatek Oreo on the MT6737.

[95584.714759] usb 1-2: Product: Pixel
[95584.714765] usb 1-2: Manufacturer: Google
[95584.714771] usb 1-2: SerialNumber: FA68Z0309184
[95586.782233] usb 1-2: USB disconnect, device number 48
[95587.309479] usb 1-2: new high-speed USB device number 49 using xhci_hcd
[95587.458468] usb 1-2: New USB device found, idVendor=18d1, idProduct=2d03
[95587.458478] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[95587.458485] usb 1-2: Product: Pixel
[95587.458490] usb 1-2: Manufacturer: Google
[95587.458496] usb 1-2: SerialNumber: FA68Z0309184
[95587.459886] usb 1-2: 1:1: add audio endpoint 0x82
----> A1 pro failed here
[95587.492151] usb 1-2: setting usb interface 1:1
[95587.495659] usb 1-2: setting usb interface 1:1
[95587.502216] usb 1-2: setting usb interface 1:1
[95587.506349] usb 1-2: Starting data EP @00000000d8f304ed
[95593.402794] usb 1-2: setting usb interface 1:1
[95593.403469] usb 1-2: Starting data EP @00000000d8f304ed
jonsmirl@ares:~/aosp/linux-adk$

jonsmirl

Any progress on this? The broken code is in kernel/drivers/usb/gadget/function/android,c  
You are likely missing the USB3 version of the Android USB function driver.

Copying that driver out of the Google Pixel kernel source code will likely fix this.

JohnnyBishop

Is there any way to prevent this phone from discharging 1% every minute or so?
Apart from Gmail there is nothing else that has extra rights to access the battery.

jonsmirl

JohnnyBishop replied at 2018-7-11 01:50
Is there any way to prevent this phone from discharging 1% every minute or so?
Apart from Gmail ther ...

Cyptomining malware will run your battery down to zero in an hour.

Likely need to reinstall the factory image to get rid of it. It will hide so that you can't detect it.

jonsmirl

BTW, my A1 is sitting on my desk and not being used, but it is active on cellular. It has not been plugged in for three days and it is still at 70%. It has been receiving updates, test messages, etc during that time. Key bit is that the screen has been off for those three days until I just looked at it now.

BarneyStinson

Finally lost the plot, at first I thought the handset was having unexpected power offs.  Recently I have had the same issue (fingerprint and power button press does nothing.  Screen remains off.  Long press to reboot required). Then I got the same whilst receiving a call with the ringtone playing.  I had to reboot and then call person back.  This means whilst the phone is still active but either the software UI or screen are having issues as well as the fingerprint reader going dead.  I did a factory reset as was recommended and same problem persists.  I do not own a computer so cannot reflash the handset.
I know it is a entry level handset and a good price however... When I buy a phone I expect at a minimum the ability to answer calls when the phone rings.  I do not expect to need a PC to fix my phone when I paid for a working handset.
I have been a great fanboy of umi, had a iron pro, c note, g and the A1 pro.
I have now bit the bullet and got a Huawai P20 lite on its way, sadly needed to take out a contract as don't have £300 spare.  If Umidigi ever get to selling the devices officially in the UK market with 12 month warrenty and customer support I may return.
Its been fun and would of loved to try out the Z2 pro but I need the reliability and the warrenty.

JohnnyBishop

I think A1 comparing to C2 is a big step back for me in terms of various things, quickly discharging battery on a brand new phone (nearly 1% per minute of use, 35% drop over night), lack of notification LED, dropping wireless and inability to pair some Bluetooth devices I use to pair with my C2 without issues.

JohnnyBishop

I am giving this phone a last chance. I have flashed this phone with V1.0_20180601.
No tweaking the permissions, default settings.
1. Again it ate ~35% of the battery over night - 7h
2. Problem connecting/reconnecting to wireless persists.
3. Problem pairing/connecting to Bluetooth devices persists.
4. Some apps are crashing and will not work at all e.g. Waze (something I used frequently on C2)

JohnnyBishop

regarding the battery drainage the problem is still there, the phone has been fully charged 12h ago and now is 32%

If I go to Settings -> Battery it says "Battery usage data isn't available"
so I cannot tell what is actually happening.

The1Lion

BarneyStinson replied at 2018-7-11 03:51
Finally lost the plot, at first I thought the handset was having unexpected power offs.  Recently I  ...

I thought Umidigi has a 1 year warranty unless the resell merchant has their own specified warranty which would then override Umidigi's?

I'm in North America and an unlocked phone with these features for $99.99 is hard to come by (if at all) so jumped on it since my wife needed a phone.  So far it's been working for her with her only complaint that Messenger audio doesn't work at times (actually she just told me that last night).  I'm hoping I don't need to worry about the warranty but it's always nice to know it's there.  So if they don't honor the warranty that's a bit of a problem for someone like me that was planing to buy the more expensive handset for myself.