H headingwest Member Licensed User Longtime User Sep 14, 2013 #1 Hi All, when I use log() the message is shown twice. In fact, looking a the attached screen shot everything seems to appear twice in the log window?? Any ideas?
Hi All, when I use log() the message is shown twice. In fact, looking a the attached screen shot everything seems to appear twice in the log window?? Any ideas?
NJDude Expert Licensed User Longtime User Sep 14, 2013 #2 It might be related to THIS issue. Something similar HERE Upvote 0
klaus Expert Licensed User Longtime User Sep 14, 2013 #3 I still have it too. Asus TF 700 Android 4.2.1 B4A 2.71 B4aBridge 2.08 Only in Debug mode. Best regards. Upvote 0
I still have it too. Asus TF 700 Android 4.2.1 B4A 2.71 B4aBridge 2.08 Only in Debug mode. Best regards.
Daniel Towers Member Licensed User Dec 1, 2015 #4 I have this problem too - it's driving me up the wall!! Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Dec 2, 2015 #5 You can switch to usb debug mode. It will fix this. Upvote 0
Daniel Towers Member Licensed User Dec 2, 2015 #6 Erel said: You can switch to usb debug mode. It will fix this. Click to expand... Hi Erel - Thank you - I was using USB debug. However, I wonder whether the bridge was connected at the same time. Perhaps that was getting the log entries from both sources? Upvote 0
Erel said: You can switch to usb debug mode. It will fix this. Click to expand... Hi Erel - Thank you - I was using USB debug. However, I wonder whether the bridge was connected at the same time. Perhaps that was getting the log entries from both sources?
Erel B4X founder Staff member Licensed User Longtime User Dec 2, 2015 #7 It might be related. Try it with B4A-Bridge disconnected (there is no reason to use B4A-Bridge if the device is connected in USB debug mode). Upvote 0
It might be related. Try it with B4A-Bridge disconnected (there is no reason to use B4A-Bridge if the device is connected in USB debug mode).
Daniel Towers Member Licensed User Dec 2, 2015 #8 Hi Erel - it does fix the problem - and I think it would be the likely cause for anyone else getting the double log entry problem. I had to use the bridge until around lunch time yesterday when I finally got the Intel Android USB driver working for my HUDL 2. I guess I just didn't shut the bridge down properly at both ends. For anyone else experiencing HUDL 2 USB debugging problems - (1) Download and install the INTEL Android USB driver https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices (2) On the USB connection options on the HUDL 2, un-tick BOTH boxes. USB debugging should then work. (Don't forget to enable it under developer options!!). Ps. B4A is superb - I can't understand why Google haven't bought it off you. It knocks spots off their clunky development environment. Android development has gone from nightmare to great with this product. Debugging is so much faster. Very well done!! Upvote 0
Hi Erel - it does fix the problem - and I think it would be the likely cause for anyone else getting the double log entry problem. I had to use the bridge until around lunch time yesterday when I finally got the Intel Android USB driver working for my HUDL 2. I guess I just didn't shut the bridge down properly at both ends. For anyone else experiencing HUDL 2 USB debugging problems - (1) Download and install the INTEL Android USB driver https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices (2) On the USB connection options on the HUDL 2, un-tick BOTH boxes. USB debugging should then work. (Don't forget to enable it under developer options!!). Ps. B4A is superb - I can't understand why Google haven't bought it off you. It knocks spots off their clunky development environment. Android development has gone from nightmare to great with this product. Debugging is so much faster. Very well done!!
warwound Expert Licensed User Longtime User Dec 2, 2015 #9 I never had any success with my Hudl2 and the Intel ADB driver. I tried many times and with various different versions. I did though have success with this method: http://ktnr74.blogspot.nl/2014/11/how-to-make-truly-universal-adb-and.html Upvote 0
I never had any success with my Hudl2 and the Intel ADB driver. I tried many times and with various different versions. I did though have success with this method: http://ktnr74.blogspot.nl/2014/11/how-to-make-truly-universal-adb-and.html
