I think to fix adb we will need to recompile it with the flags#
ro.bootimage.build.date=Ср. авг. 31 19:43:08 MSK 2016
Tell me please, what means "ro.adb.secure" ? And what is diff between 1 and 0. I want to known, how you it see..
Ah..."ro.adb.secure=0" means only, thats you can connect via adb without confirm it from confirm dialog on phone! 1 means, thats you will get dialog on phone and you will be have to tap(yes) to allow adb connect..When I was googling for a fix for the adb offline error all I could find was for android 4.2.2 but I found out that at that point they made secure adb mandatory so to fix it you just updated the sdk version on your pc but I think that having ro.adb.secure set to 0 (false) you are telling the compiler to compile it with the old adb protocol so so anyone with a sdk made for android 4.2.2 or higher can't use it which includes most people and pda net users. I'm not sure how to set it to 1 (true) but I assume there is a config file some where or maybe you specify it in the lunch command.
Ah..."ro.adb.secure=0" means only, thats you can connect via adb without confirm it from confirm dialog on phone! 1 means, thats you will get dialog on phone and you will be have to tap(yes) to allow adb connect..
Just only props settings flags..
Nothing to do with sdk or somethings like this..nothing to do with binary compilations..
You go from wrong way. First you have to configure you linux-ubuntu for adb connect..add some android rules..
I dont known about win 10..I have win 7 and dont update it) Adb is working good on win 7 for my, on home pc and job pc..
I am not rush, no any ETA, because it will post, if ROM will be really ready and on 99% daily use..