12
Return to list Post new posts
Author: Buddy

OrangePi 2G-IOT: ADB mode(Under Android OS)

[Copy link]

0

threads

7

posts

48

credits

Novice

Rank: 1

credits
48
Published in 2017-8-10 10:06:24 | Show all floors
Edited by batojay at 2017-8-10 10:07
gtrangoni replied at 2017-8-10 03:25
You have the USB debugging enable or have you had to enable it?
Have you tried installing differen ...

It was enabled by default in the new firmware, although before that I took the same steps as you did for the old firmware (before upgrading to the new one, unfortunately I had no lcd screen back then so cannot verify the key). Now I have the lcd screen but problem with the adb. I tried the ADB installer but it did not recognize the phone. I will try a few different things & will let you know the results.

0

threads

5

posts

36

credits

Novice

Rank: 1

credits
36
Published in 2017-8-12 05:44:39 | Show all floors
Edited by gtrangoni at 2017-8-12 05:48
batojay replied at 2017-8-10 10:06
It was enabled by default in the new firmware, although before that I took the same steps as you di ...

Thanks for the reply batojay.  
I accomplished update the android image (I tried to press the power button before connecting the otg cable and it worked) but now has the same problem which i mentioned earlier
Apparently the update does not completely replace the android system and the problem persist.
Of the TTL debug pins i get the following:


  1. [  845.062805] Suspending console(s) (use no_console_suspend to debug)
  2. [  845.318603] <rda_msys>: pid = 1021, v_sdmmc: ext_len = 0
  3. [  845.318603] <rda_msys>: end of pending msg
  4. [  845.320129] PM: suspend of devices complete after 243.426 msecs
  5. [  845.324279] PM: late suspend of devices complete after 4.103 msecs
  6. [  845.328613] PM: noirq suspend of devices complete after 4.341 msecs
  7. [  864.741210] Suspended for 19.412 seconds
  8. [  864.744201] PM: noirq resume of devices complete after 2.603 msecs
  9. [  864.746887] PM: early resume of devices complete after 2.449 msecs
  10. [  864.755126] <rda_msys>: pid = 1018, v_sdmmc: ext_len = 0
  11. [  864.755126] <rda_msys>: end of pending msg
  12. [  864.768432] PM: resume of devices complete after 21.552 msecs
  13. [  864.780578] Restarting tasks ... [  864.786071] healthd: battery l=86 v=4010 t=36.0 h=2 st=2 chg=a
  14. done.
  15. [  864.790954] PM: suspend exit 2000-01-01 00:14:24.003148980 UTC
  16. [  864.791809] PM: suspend entry 2000-01-01 00:14:24.004002980 UTC
  17. [  864.792419] PM: Syncing filesystems ... done.
  18. [  864.798889] Freezing user space processes ... (elapsed 0.002 seconds) done.
  19. [  864.802246] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
  20. [  864.805297] Suspending console(s) (use no_console_suspend to debug)
  21. [
Copy code


I have been reading and apparently it goes into suspend loop.
For now, i must resolve this problem (no idea how) before continuing.
I wait for your comments and i hope you succeed with the adb.

0

threads

5

posts

36

credits

Novice

Rank: 1

credits
36
Published in 2017-8-13 10:30:54 | Show all floors
I made it!
This post helped me to stop the suspend loop: http://forum.legato.io/t/suspend ... uspend-to-debug/251
Then, combining the last post for enable adb, and this: https://forum.xda-developers.com/showthread.php?t=893434
I do not why this time dont request me to verify the key and after a reboot all work fine, and automatically opened the vysor and i see the screen.
Finally i won, and i'm so happy that don't know what do now

This thread contains more resources

You need to Log in to download or view,No account?    Register

x

0

threads

7

posts

48

credits

Novice

Rank: 1

credits
48
Published in 2017-8-14 12:26:11 | Show all floors
gtrangoni replied at 2017-8-13 10:30
I made it!
This post helped me to stop the suspend loop: http://forum.legato.io/t/suspending-console ...

Hi gtrangoni,

I also experience the console freeze, but dont know what to do , since in the GUI mode using LCD screen all works fine. It is great that you have resolved the problem. I will try your solution when I get the time.

Thanks....

0

threads

7

posts

48

credits

Novice

Rank: 1

credits
48
Published in 2017-8-14 16:06:05 | Show all floors
Edited by batojay at 2017-8-14 16:59

I finally able to use ADB using this command:

  1. setprop persist.sys.usb.config "adb"
Copy code

0

threads

5

posts

36

credits

Novice

Rank: 1

credits
36
Published in 2017-8-14 20:25:23 | Show all floors
batojay replied at 2017-8-14 16:06
I finally able to use ADB using this command:

Congrats batojay! Enjoy it now. Is the beginning for do something more, i guess.
Yes i saw that command. Another useful is "svc" command. With this you can control power, wifi, data and usb.
For example:
svc usb getFunction -> gets list of currently enabled functions on device
(https://www.xanh.co.uk/control-android-device-with-svc/)

Regards!

0

threads

7

posts

48

credits

Novice

Rank: 1

credits
48
Published in 2017-8-18 12:16:22 | Show all floors
gtrangoni replied at 2017-8-14 20:25
Congrats batojay! Enjoy it now. Is the beginning for do something more, i guess.
Yes i saw that co ...

Thanks gtrangoni. Well, for starter, I have managed to toggle some io pins on & off from adb terminal if you are interested.

0

threads

1

posts

8

credits

Novice

Rank: 1

credits
8
Published in 2017-11-7 22:58:49 | Show all floors
I found solution for unauthorized device in adb:
Copy file from %USERPROFILE%\.android\adbkey.pub to folder /data/misc/adb
Rename file /data/misc/adb/adbkey.pub to adb_keys
This could be done easily by mounting device in mtp mode:
  1. svc usb setFunction adb,mtp
Copy code
copying key file into phone storage and in console:
  1. cp /mnt/sdcard/adbkey.pub /data/misc/adb/adb_keys
Copy code


12
Return to list Post new posts
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list