[CM 10][BUG][XPERIA MINI ST15] MTP and WiFi bugs - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

Hello, dear.
I have installed the CM 10 rom from FXP, and I have found some bugs.
I don't know what should I do, so I am creating this thread. If I am wrong, please, excuse me and tell me.
So, in FPX 151, I don't have access to my SDCard while I connect my telphone in my notebook, that is OpenSuSE Linux. Before this version, my SDCard was connecting correctly.
Ps.: In Windows operating system I can open my SD.
Ps².: Maybe is a OS unrecognizing, but I already do the udev rules correctly.
/etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666", GROUP="users"
Click to expand...
Click to collapse
My lsusb while telephone connected in MTP:
[email protected]:~> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
Bus 006 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse
Bus 002 Device 021: ID 0fce:0167 Sony Ericsson Mobile Communications AB
[email protected]:~>
Click to expand...
Click to collapse
The other bug I found occur just in my ST15 and it's occuring in all releases after FX152. I haven't tested the FX152, but all releases until the FX207, my telephone doesn't start the WiFi.
When I try to start my WiFi, I get the message that is starting, but still ever there. Maybe it's a kernel bug.
Can someone help me?
Regards,
Rudah Ximenes.

RudahXimenes said:
Hello, dear.
I have installed the CM 10 rom from FXP, and I have found some bugs.
I don't know what should I do, so I am creating this thread. If I am wrong, please, excuse me and tell me.
So, in FPX 151, I don't have access to my SDCard while I connect my telphone in my notebook, that is OpenSuSE Linux. Before this version, my SDCard was connecting correctly.
Ps.: In Windows operating system I can open my SD.
Ps².: Maybe is a OS unrecognizing, but I already do the udev rules correctly.
/etc/udev/rules.d/51-android.rules
My lsusb while telephone connected in MTP:
The other bug I found occur just in my ST15 and it's occuring in all releases after FX152. I haven't tested the FX152, but all releases until the FX207, my telephone doesn't start the WiFi.
When I try to start my WiFi, I get the message that is starting, but still ever there. Maybe it's a kernel bug.
Can someone help me?
Regards,
Rudah Ximenes.
Click to expand...
Click to collapse
Hi
I can't help you with the linux stuff, but I can help you with the wifi!
[INDEX] ROMs, KERNELS, FTFs, TOOLKITS and GUIDES - http://forum.xda-developers.com/showthread.php?t=2148684
Check out this list of all the kernels,
find the kernel you use,
go to thread , find modules,
flash modules in [cwm, twrp], ??????, click thanks after rebooting the phone:fingers-crossed:

Related

Phone not detected by ADB Coolpad E239

I apologize if this is in the wrong area, but there is no sub-forum for the phone in question and this seemed the most relevant place to post.
I'm trying to get ADB to detect my wife's phone, a Coolpad E239. My Nexus One detects fine. However, whenever I plug in my wife phone and run the command adb devices, I get this:
Code:
[email protected] ~ $ adb devices
List of devices attached
[email protected] ~ $
I don't get a bunch of question marks so I don't think it's a permissions issue. When I type lsusb into terminal, I get this:
Code:
[email protected] ~ $ lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
Bus 005 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 048: ID 1ebf:6045
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $
I'm thinking the 1ebf:6045 is the phone, but it doesn't seem to be showing up. Does anyone have any suggestions?

[Q] My adb devices list is empty!

Hi guys,
I have used the following tutorials:
http://forum.xda-developers.com/showthread.php?t=735375
http://forum.xda-developers.com/showthread.php?t=921169&page=2
But still when I type "./adb devices" or "sudo ./adb devices" all I get is "List of aevices attached" followed by a blank. Do you know a way to fix this?
I'm using a Samsung Galaxy Tab.
Thanks in advance.
Could you paste your dmesg? What's your OS?
Could you paste your 51-android.rules and output of lsusb?
My OS is Ubuntu 11.10
The output of lsusb is:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:5c11 Hewlett-Packard PhotoSmart C4200 Printer series
Bus 003 Device 002: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000
Bus 006 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 006 Device 003: ID 045e:0730 Microsoft Corp.
Bus 002 Device 005: ID 04e8:6877 Samsung Electronics Co., Ltd
Click to expand...
Click to collapse
The 51-android-rules file contains
SUBSYSTEM==usb, SYSFS{idVendor}==0bb4, MODE=0666
Click to expand...
Click to collapse
Are you using the stock USB cable that came with your tablet? Is the cable in good shape?
I had a Samsung device that would not show up under my devices in Ubuntu. I later discovered it was because my cable was damaged internally. It charged, but had trouble connecting for data.
Is there any way this could be the issue?
adb driver
are you sure you have install the adb driver ?
The vendor id in your udev file is the HTC vendor id.. you should use the samsung one: 04e8
Besides, you can just try:
adb kill-server
and then:
sudo adb start-server
and see if you can get your device listed
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.

Alldaymall A88S stuck after "adb reboot bootloader"

Hi,
I guess I brought myself into trouble today.
I have an alldaymall A88S 8GB tablet which I have bought on eb*y. Today I sent a "adb reboot bootloader" to it. That resulted in a mode where a little green robot is visible in the middle of the screen.
Now I can't power down the device. Pressing the power button results into a dark screen and then the green robot again. Power+Vol leads to the same.
Adb and fastboot show no device. lsusb still lists the device.
Any suggestions?
I was lucky.
Although fastboot did not show any devices, a "fastboot -i 0x1f3a reboot" did the job.
theodleif said:
I was lucky.
Although fastboot did not show any devices, a "fastboot -i 0x1f3a reboot" did the job.
Click to expand...
Click to collapse
Thanks man! This really helped. I was stuck for couple of hours.
My Mediacom SmartPad Go MP726GOG was stuck after issuing "adb reboot bootloader". My vendor device was the same as yours (1f3a), but in case someone else is stuck, you can check the connected devices (on linux, at least) with the command lsusb.
Code:
$ lsusb
Bus 007 Device 047: ID 1f3a:1010 Onda (unverified)
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0cf2:6230 ENE Technology, Inc. SD Card Reader (UB623X)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 09da:0260 A4Tech Co., Ltd. KV-300H Isolation Keyboard
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 09da:9090 A4Tech Co., Ltd. XL-730K / XL-750BK / XL-755BK Mice
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
where you can see the onda device with id 1f3a:1010.
There should also be a windows specific way to get the vendor id, probably device manager or similar, but I am not familiar with windows.
Cheers!
Need Firmware for this unit any help
alldaymall model:A88S
A33

Onyx not recognized by Ubuntu

My oneplus x is rooted and running latest orion os. The problem is that it is not appearing in lsusb command in Ubuntu 16.04. When I connect my phone nothing appears. But I can use my phone for usb tethering to connect my pc to internet. I want to be able to use mtp & adb. Can anyone help?
And here is the output of lsusb:
Code:
$ lsusb
Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 005: ID 05c6:6769 Qualcomm, Inc.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 008: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 006: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Update: Interesting when I disconnect my phone "Bus 002 Device 005: ID 05c6:6769 Qualcomm, Inc. " disappears.
Bump!
I don't know..but my onyx is recognized on Ubuntu. I have installed Android Studio from here, maybe that's why.
raulx222 said:
I don't know..but my onyx is recognized on Ubuntu. I have installed Android Studio from here, maybe that's why.
Click to expand...
Click to collapse
Can u send me the default mac os driver .sh file which can be obtained by emulated cdrom of onyx? May be installing that will help.
raulx222 said:
I don't know..but my onyx is recognized on Ubuntu. I have installed Android Studio from here, maybe that's why.
Click to expand...
Click to collapse
Ok after installing android studio, my device is actually being shown in the nautilus as mtp device but when I click on it following error occurs:
Unable to open MTP device '[usb:002,009]'
The output of lsusb is still the same i.e.:
Code:
$ lsusb
Bus 002 Device 009: ID 05c6:6765 Qualcomm, Inc.
Bus 002 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 003: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sixline said:
Ok after installing android studio, my device is actually being shown in the nautilus as mtp device but when I click on it following error occurs:
Unable to open MTP device '[usb:002,009]'
The output of lsusb is still the same i.e.:
Code:
$ lsusb
Bus 002 Device 009: ID 05c6:6765 Qualcomm, Inc.
Bus 002 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 003: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Make sure you are using latest Ubuntu and have your phone's screen unlocked. Also make sure that your cable works properly, maybe try another one.
raulx222 said:
Make sure you are using latest Ubuntu and have your phone's screen unlocked. Also make sure that your cable works properly, maybe try another one.
Click to expand...
Click to collapse
Well I am using ubuntu 16.04 lts as i mentioned in the op so its the latest. And i am using the oem cable came with the device. I ve also checked with two more cables which are working with other phones.
Sent from my ONE E1003 using XDA-Developers mobile app
Well atleast adb is now recognizing my device by following the procedure given by Evan Carroll at http://askubuntu.com/questions/461729/ubuntu-is-not-detecting-my-android-device
Now only problem remains is the mtp which return error: Unable to open MTP device '[usb:002,018]'
sixline said:
Well atleast adb is now recognizing my device by following the procedure given by Evan Carroll at http://askubuntu.com/questions/461729/ubuntu-is-not-detecting-my-android-device
Now only problem remains is the mtp which return error: Unable to open MTP device '[usb:002,018]'
Click to expand...
Click to collapse
Can you try to reboot phone while the phone is plugged?
Kéno40 said:
Can you try to reboot phone while the phone is plugged?
Click to expand...
Click to collapse
Yes I can reboot my phone using adb.
sixline said:
Yes I can reboot my phone using adb.
Click to expand...
Click to collapse
Edit sorry , I meant :
Try to reboot your computer while the phone is plugged
Edit : An outdated french guide with Go-MTPFS (not sure it could help)
http://korben.info/installer-nexus-7-android-4-0-ubuntu.html
Kéno40 said:
Edit sorry , I meant :
Try to reboot your computer while the phone is plugged
Edit : An outdated french guide with Go-MTPFS (not sure it could help)
http://korben.info/installer-nexus-7-android-4-0-ubuntu.html
Click to expand...
Click to collapse
Thanks for your concern but I switched rom to sultan's cm13, after that its working.

New kid (and mobile model) on the block...

Hello all, I have a little project I'd like some help on. I have recently bought an Alba 4 inch with android 7 (Nougat). I'd like to use this phone purely for SatNav work, but it appears that it doesn't like working the GPS without SIM or wireless. I have done some research and apparently, a few people have experienced a similar issue when updating from android 6 to 7. So I thought I'd root my 'Alba' and flash it back to 6 to see if that improves the GPS usage unless someone can tell me otherwise. It's quite maddening as I have an old Nokia Lumia 925 (Windows 8.1) which has no problem using the internal GPS device without wireless or SIM card - in fact, my old N8 and X6 have no problem at all and I still use those but software is now almost defunct. However, I'd like to pursue with the 'Alba' as I want to install OsmAnd or equivalent app and upload created gpx routes from my laptop, for me to use on my mountain bike or road bike. The reason I'm going for a fairly simple mobile, but should fit the bill, is that it can be charged while out in the wild with a basic solar power pack. My other phone the Honor 8 requires more than a simple solar pack....
Details of phone - Alba 4 3g (AC40AS3G / SKU133814622) with Archos android 7.
Steps taken...
'OneClickRoot' doesn't have a root app entry for my particular phone. Now I've done the build number trick, allowed usb debugging, got the PC authorised on the phone, installed android sdk on my Ubuntu 12.04 laptop and I can run adb and some commands:
'adb devices' creates:
[email protected]:~$ adb devices
List of devices attached
18643080980731 device
'adb shell' creates:
[email protected]:~$ adb shell
ac40as3g:/ $
'adb reboot bootloader' - gives a screen with 'fastboot mode' in the top left corner of the mobile.
'fastboot oem unlock' and 'fastboot flashing unlock- both give "< waiting for any device >" but no listing
'fastboot devices' - this then produces "no permissions (user in plugdev group; are your udev rules wrong?); see [developer website] "
My lsusb command produces this, with phone connected in normal mode:
userATlaptop:~$ lsusb
Bus 002 Device 004: ID 0e79:5604 Archos, Inc.
Bus 008 Device 002: ID 8086:0189 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
My 51-android.rules file contains :
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666", GROUP="plugdev"
I also have a custom rule called '70-abdroid-custom-device.rules' which I created from some 'googled' page...
# Archos 4
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", ATTRS{idProduct}=="5609", TAG+="uaccess"
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", ATTRS{idProduct}=="5604", TAG+="uaccess"
'fastboot flashing get_unlock_ability' - this produces "< waiting for any device >" but nothing.
So questions are:
Have I got my udev right?
What would be the next step after correcting the first question?
...any other suggestions? Apart from 'throw it in the bin...' thanks.

Categories

Resources