Related
Hi everyone! Hope someone can help out on this...
I have installed MiniCM7 Pro V7x (Android v2.3.5, Kernel 2.6.29) on my SE Xperia X10 Mini Pro.
It is rooted and everything works just fine... EXCEPT Wifi tethering. It is impossible to get any tethering app to work.
Barnacle will only go as far as "Starting..." and then nothing happens.
Wireless Tether for root users says "No Netfilter! Sorry, but your kernel does not have all necessary features for running this application."
Opengarden Wifi Tethering says the same thing "No Netfilter! Sorry..."
So my question now is clearly: Is it not possible to use Wifi tethering on this phone with this rom?
And secondly, can I use my phone as a modem if I run it with a USB cable instead, as a backup if Wifi tethering wont work? If so, can you recommend a guide somewhere describing how to do it?
Thank you all in advance! Looking forward for your replies...
I finally got it to work.
I needed iptables. Found a useful guide on this URL:
http://forum.xda-developers.com/showthread.php?t=1184907
I then use Barnacle without any issues at all! Works flawless and I can connect multiple units (iPad2, Win7 x64 PC, Ubuntu 11.04 x86 PC and Debian ARM PC) at the same time...
Please help!
Hey Psyninja, or anyone else! I've been having the same problem and its driving me crazy!
I'm trying to follow the instructions on this thread you linked... but im a newbie and im having trouble with one stupid thing:
When it says I have to copy the files to the ADB folder.. where can I find it? the only adb folder I find it's on the superoneclick directory... is it this one?
Please, help!
Cheers!
hfogli said:
Hey Psyninja, or anyone else! I've been having the same problem and its driving me crazy!
I'm trying to follow the instructions on this thread you linked... but im a newbie and im having trouble with one stupid thing:
When it says I have to copy the files to the ADB folder.. where can I find it? the only adb folder I find it's on the superoneclick directory... is it this one?
Please, help!
Cheers!
Click to expand...
Click to collapse
Hi,
Yes, you can use the adb folder of SuperOneClick directory.
ADB is Android Debug Bridge, a command line tool that lets you communicate with your conected device or emulator, this folder is also found in the SDK, available on Android Developers site.
Hi people!
i'm new here.
I have this Panasonic Eluga dL1(EB-3901) android phone. It's version 2.3.5
when I plug the USB into the computer, it does not install any drivers (i'm unsure if it had any in the first place), i googled for the drivers but had not luck there.
thus when i type adb devices i do not see the phone listed. I need logcat to help me debug an application.
side note: I did transfer my developing app to the phone via sdcard but the app crashed. I am not sure if it could be due to my manifest's file minSdkVersion as 10 is already 2.3.3 and 11 is 3.0 and there is no 2.3.5.
Would appreciate any help. Thank you people!
Regards,
Paul
What Windows version do you use? (Assuming you use windows ). Should be installed automatically in Windows 7.
http://mustikamax.com/2012/05/02/how-to-syncsuite-panasonic-eluga-for-pc-windows/
Small question for you: I saw a review of this device, and the camera and gallery app looked awesome. Any chance you could share them?
[Use a file explorer on you phone, go to ROOT\system\apps and copy the camera and gallery app to your user memory and then transfer to pc.] No root needed (read only)
Thanks in advance if this is possible.
yup i am using windows.
Will try you suggestion in a moment.
Btw there is no camera app in /system/apps but there is this app called "Gallery3D". Do you want it? i can't really host it at work. perhaps i can email the app to you?
Regards,
Paul
oh. the suggestion doesn't work. its not exactly what i wanted.
I am looking for the device drivers for Eluga, apparently Windows (am using windows 7 Pro) does not install the drivers automatically and there is no installation along with the phone.
The steps suggested had this area where they needed me to have adb. Which is exactly what I am looking for from the start. I am unable to locate my device when i type "adb devices" and would like to know if anyone has a clue to get it done (i once added some codes into google/usb_driver for my kindle fire to be recognised).
Do let me know if anyone know how to make the Panasonic Eluga recognised by adb.
Thank you people!!!
Regards,
Paul
I'm not a big adb user, so I don't think I can help you with that. Are there any other apps with a camera icon or gallery icon in that folder? I don't need them right now, so take your time.
Via Tapatalk 2.0 on ICS
tinyXperia said:
I'm not a big adb user, so I don't think I can help you with that. Are there any other apps with a camera icon or gallery icon in that folder? I don't need them right now, so take your time.
Via Tapatalk 2.0 on ICS
Click to expand...
Click to collapse
Hi,
Install the correct ADB driver; here
http://panasonic.jp/mobile/support/global/software/dl_1_1.html
Cheers!
Hello all, I've been really happy with my XPS ever synce I've root it and everything is working clockwork, except there is something eating my battery.
I've used "BetterBatteryStats" app, and i've got a parcial wakelock "AlarmManager" in 1st place.
I've read that to know eacly what app is waking the phone i've got to connect the phone to a Pc, run "ADB" and type "adb shell dumsys alarm > C:\alarm_log.txt".
This will creat a log file that will show what app is generating all those wake numbers, and then unistall or limit it.
The problewm is... what is ADB.EXE??? Where can i get that program for the pc? Does the phone have to be in USB debuggin mode? If someone help me I'll post a guide to anyone in need to find the problematic apps that eat battery for others noobs out there!
Here
Sent from my ST25i using Tapatalk 2
As the above is saying you should search n read a lot... there are guides all over in net in many n here xda as well... Its a good start by learning urself from the help already here..
1. ADB is included in SDK here. get it ...http://developer.android.com/sdk/index.html
2. Here is a guide to set up SDK... http://www.talkandroid.com/guides/developer/android-sdk-install-guide/
4. Browse to folder platform-tools adb.exe is inside... but u can't just click open it.. adb is used via command prompt (cmd)
5. Easy way to open cmd to adb is Shift+ right click -> click open cmd here
6. To connect phone in adb u have to enable usb debugging mode as u said..
7.Then start typing commands....
Thank you a lot for the aswer!
I DID goodle for the answer, but I had an hard time undestanding what I should do, I'm a pharmacist, not a technician.
That beeing said, the other part of the info I posted I found using the search funcion.
Anyway, thank you a lot for that answer, I'll try it now.
s-X-s said:
As the above is saying you should search n read a lot... there are guides all over in net in many in here xda as well... Its a good start by learning urself from the help already here..
1. ADB is included in SDK here. get it ...http://developer.android.com/sdk/index.html
2. Here is a guide to set up SDK... http://www.talkandroid.com/guides/developer/android-sdk-install-guide/
4. Browse to folder platform-tools adb.exe is inside... but u can't just click open it.. adb is used via command prompt (cmd)
5. Easy way to open cmd to adb is Shift+ right click -> click open cmd here
6. To connect phone in adb u have to enable usb debugging mode as u said..
7.Then start typing commands....
Click to expand...
Click to collapse
To perform this actions, is it mandatory that phone needs to be rooted?
Because, i followed all the steps, when i executed the command in cmd prompt, i got below info
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/system/bin/sh: dumsys: not found
What should i need to do now if phone doesn't needed to be rooted?
For using adb not necessarily ur phone rooted... but if u need to get anything insdie system folder ur phone needs root access... you can pull/push files from adb.. but it makes more easier if u do those for sdcard via windows explorer after connecting via usb..
In short its for rooted devices mostly.....
Ok, still need help on this one.
I've followed all the steps, installed SDK, phone in development, command line accepted, but then I check the log file I get this:
/system/bin/sh: dumsys: not found
So... Why is it now finding my phone? any idea? When am i supposed to connect the phone to the pc?
Thank you for the help!
Miguel Pereira said:
Ok, still need help on this one.
I've followed all the steps, installed SDK, phone in development, command line accepted, but then I check the log file I get this:
/system/bin/sh: dumsys: not found
So... Why is it now finding my phone? any idea? When am i supposed to connect the phone to the pc?
Thank you for the help!
Click to expand...
Click to collapse
dumpsys, not dumsys. With a P.
Hi People !!!
I had my OP2 showing in fastboot but not being able to show in adb devices though other devices were showing correctly there.So,drivers were perfect.Also,I was able to use adb over wifi on my OnePlus 2 but not adb through cable.So,I set up on my mission to get it show.And after 10 hrs of a lot hassle,I am successful.
So,here is the guide.
Open windows command prompt (Windows Key + R)
Ènter: %HOMEPATH%\.android
and then press OK
This will open the hidden .android folder within Home Folder of the current user.
There you will see a file called: adb_usb.ini
Edit the file using Notepad or Editplus/Notepad+
Just add the text: 0x2A70
without pressing any additional enter key/new line characters, save the file
now go to command prompt and restart adb:
adb kill-server
adb devices
Now the device will start showing up!
If you don't see any adb_usb.ini file (This happened for me.) , do this :-
Click the Start menu. ...
Type "folder options" (without the quotes). ...
A dialog box with the title "Folder Options" will appear. ...
Click to uncheck the box for "Hide extensions for known file types".
Click the "OK" button at the bottom of the dialog box.
In the .android folder ,create a notepad file with name adb_usb.ini (Make sure .ini is not in the name but in the extension.)
In the notepad file , enter this :-
Code:
# add your vendor IDs, one per line
0x1949
0x18D1
0x2A70
8.) Save the file and close it...ANd follow the remaining steps.
I will be thankful to you a lot..
i have tried all the possible methods to connect via adb if this works..
ssly it will be awesome
Sent from my ONE A2003 using Tapatalk
Zeuscluts said:
I will be thankful to you a lot..
i have tried all the possible methods to connect via adb if this works..
ssly it will be awesome
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Welcome. If you still have any issues connecting to adb, grant me Teamviewer access and I will help you out.
Sent from my ONE A2003 using Tapatalk
Naman Bhalla said:
Welcome. If you still have any issues connecting to adb, grant me Teamviewer access and I will help you out.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
yes sure,
can we chat on hangouts
you can contact me on
[email protected]
Sent from my OP5.
I had the same problem! Will surely try! Thanks
Keep up the great work Naman..!!
Did somebody got this to work on Linux? Probably you need to adjust udev rules there to get it to work. Will try out today and let you know how it goes.
dansou901 said:
Did somebody got this to work on Linux? Probably you need to adjust udev rules there to get it to work. Will try out today and let you know how it goes.
Click to expand...
Click to collapse
You need to add a udev*rules file that contains a USB configuration. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. To set up OP2 detection on Ubuntu Linux:
Log in as root and create this file:/etc/udev/rules.d/51-android.rules.
Use this format to add OP2 vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="2a70", MODE="0666", GROUP="plugdev"
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Done
I am 99.99 percent sure it will work.. But you should try and tell me.
Thanks.
Sent from my ONE A2003 using Tapatalk
Naman Bhalla said:
You need to add a udev*rules file that contains a USB configuration. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. To set up OP2 detection on Ubuntu Linux:
Log in as root and create this file:/etc/udev/rules.d/51-android.rules.
Use this format to add OP2 vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="2a70", MODE="0666", GROUP="plugdev"
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Done
I am 99.99 percent sure it will work.. But you should try and tell me.
Click to expand...
Click to collapse
Didn't fix it for me, until I found out, that there also exists a ˝/.android/adb_usb.ini file . Has the same format as the Windows file.
/M
marlow925 said:
Didn't fix it for me, until I found out, that there also exists a ˝/.android/adb_usb.ini file . Has the same format as the Windows file.
/M
Click to expand...
Click to collapse
Sorry for asking, but does this whole issue affect Oneplus two devices with original stock ROM (Oxygen OS 2.1.0), too?
Or does it just affect devices with custom firmware?
coala-lumpur said:
Sorry for asking, but does this whole issue affect Oneplus two devices with original stock ROM (Oxygen OS 2.1.0), too?
Or does it just affect devices with custom firmware?
Click to expand...
Click to collapse
Probably both. I haven't tested stock Rom though.
/M
I have the opposite problem, adb works after using your guide but fastboot just doesnt :S
alankstiyo said:
I have the opposite problem, adb works after using your guide but fastboot just doesnt :S
Click to expand...
Click to collapse
Fastboot should not be affected by CM at all, as it's in the bootloader. Did it work before you made the changes ?
Maybe worth reinstalling the fastboot packages.
/M
marlow925 said:
Fastboot should not be affected by CM at all, as it's in the bootloader. Did it work before you made the changes ?
/M
Click to expand...
Click to collapse
I had a wrong driver, cant root for the moment but havent unlocked the bootloader so think that is the problem
Well. Without unlocking the bootloader you won't get anywhere. Fastboot is a bootloader feature. You don't need root for fastboot.
/M
Sent from my SM-P905 using Tapatalk
Didn't work for me.
So found mine in my install folder
c:\android\.android\adb_usb.ini
After each change below I ran adb kill-server then adb devices.
I already have the line 0x2a70, I first changed it to 0x2A70 (just in case)
tried renaming it to adb_usb.ini.bak, to see if it would recreate, nope.
renamed the folder .android to .android.bak and it created the adbkey and adbkey.pub but not the .ini.
So looking at the .android folder, I think I learned something new tonight, I assume this is the public/private key pair store for adb to do it's work? So it truly is just a usb connection issue then if it works over network and not with the usb cable connected yes?
So I even tried re-running the '15 seconds ADB Installer' version 1.3 by Snoop05 that I used originally and still no change. Any advice appreciated.
My ADB is working but the fastboot isn't working! Thank you for your help!
Still not detecting
I tried doing your steps but its not helping. My phone enters the fastboot mode but the pc never detects it.
Can u please help me out.
---------- Post added at 07:08 PM ---------- Previous post was at 07:05 PM ----------
williamt31 said:
So found mine in my install folder
c:\android\.android\adb_usb.ini
After each change below I ran adb kill-server then adb devices.
I already have the line 0x2a70, I first changed it to 0x2A70 (just in case)
tried renaming it to adb_usb.ini.bak, to see if it would recreate, nope.
renamed the folder .android to .android.bak and it created the adbkey and adbkey.pub but not the .ini.
So looking at the .android folder, I think I learned something new tonight, I assume this is the public/private key pair store for adb to do it's work? So it truly is just a usb connection issue then if it works over network and not with the usb cable connected yes?
So I even tried re-running the '15 seconds ADB Installer' version 1.3 by Snoop05 that I used originally and still no change. Any advice appreciated.
Click to expand...
Click to collapse
Same here!!!!!
any help would be appreciated
My fix was:
turn on adb over TCP on phone in developer options.
At cmd type:
adb connect <ip.address>
adb devices (now shows device)
adb reboot bootloader
Open another cmd if you don't get your prompt back and continue
still not working
i tried all the steps and my op2 only shows when connected via wifi but that is too slow for an adb backup, it still doesnt show up when connected over usb
any ideas? or is any info needed?
Hi all!
I'm testing some device because I need to install a MDM application to remote controlling the device. This Ugoos likes me but I can't find how install de MDM apk with owner permission and not getting a reboot loop.
I'm setting up the owner permission with this adb command:
Code:
adb shell dpm set-device-owner com.hmdm.launcher/.AdminReceiver
After that, if I rebooting device, when it loading the launcher the background image is displayed for a second and restarts again. If I installed MDM apk but not execute adb command, device works fine. I need owner permission for a silent install/update application, remote reboot...
I'm trying debugging with adb, but I've connected just via WiFi and with the reboot loop I can't do that. With male to male USB cable I can't to connect. I've little experience with Android, but I'm good with linux.
Can you give me any recommendations to get owner permission? Or how debugging it?
P.D: I've installed another launcher (Nova) and setup as default I device works fine.
ppalacios said:
Hi all!
I'm testing some device because I need to install a MDM application to remote controlling the device. This Ugoos likes me but I can't find how install de MDM apk with owner permission and not getting a reboot loop.
I'm setting up the owner permission with this adb command:
Code:
adb shell dpm set-device-owner com.hmdm.launcher/.AdminReceiver
After that, if I rebooting device, when it loading the launcher the background image is displayed for a second and restarts again. If I installed MDM apk but not execute adb command, device works fine. I need owner permission for a silent install/update application, remote reboot...
I'm trying debugging with adb, but I've connected just via WiFi and with the reboot loop I can't do that. With male to male USB cable I can't to connect. I've little experience with Android, but I'm good with linux.
Can you give me any recommendations to get owner permission? Or how debugging it?
P.D: I've installed another launcher (Nova) and setup as default I device works fine.
Click to expand...
Click to collapse
to make an app owner you need to add/edit device_policies.xml and device_owner_2.xml, these then need to be started by init in the post-fs-data section in the /data/system partition, to copy the XML files to system/data use init.rc to copy the files to /data/system, not sure if much help
heres some info may be useful https://burningthumb.com/setting-the-device-owner-in-an-aosp-build-for-android-9-pie/
aidanmacgregor said:
heres some info may be useful https://burningthumb.com/setting-the-device-owner-in-an-aosp-build-for-android-9-pie/
Click to expand...
Click to collapse
Thanks Aidan.
I read that days ago but in my case, the app is not developed by me. Is headwind mdm application.
Can I follow the instructions of the link even if is third party app?
Thanks for your help
ppalacios said:
Thanks Aidan.
I read that days ago but in my case, the app is not developed by me. Is headwind mdm application.
Can I follow the instructions of the link even if is third party app?
Thanks for your help
Click to expand...
Click to collapse
yes looks like you will be modifying the firmware rather than the app, the info is there but your not building from source so you will need root to add the files and to edit others
aidanmacgregor said:
yes looks like you will be modifying the firmware rather than the app, the info is there but your not building from source so you will need root to add the files and to edit others
Click to expand...
Click to collapse
Sorry for bother you Aidan, I appreciate your help so much
I've got root access and I've seen that set-device-owner adb command execution create the device_owner_2.xml and device_policies.xml automaticly and they are storage in /data/system. In fact, I'm reading dpm command (adb) is the new way to grant the owner permission without modifing xml files The bad news, I'm still getting reboot loop.
I can't to write into init.rc because the file is in /system and this partition is read only. The same way, can't copy decice_owner_2.xml and device_policies.xml in /system partition (this I read on some forum on internet).
Could I get a logcat from adb to get more info about the crash app? I've only wifi adb connection. I've a male-to-male USB and it connected to OTG port of Ugoos device.