samsung galaxy ace i (gt-s5830i) not plus detected after upgrade.

[Francesco Bonanno]

I've saucy on my netbook since the repositories for it were published (I use it for every dev branches of ubuntu). So I upgrade this installation every day. Before the 28th August 2013 (utc +1 timezone) I can use my device as storage device or debug, and I've had the notifications on both pc and smartphone. Now if I plugin my gt-s5830i I don't get any notifications on both device, but where dmesg displays the usb connection lsusb doesn't give the phone on the list. The smartphone runs cyanogenmod 7 (android 2.3.7).

With a tablet everything is still ok. So a kiwie 7 tab (detected as simply google on lsusb) is still working, android 4.0.1. This is my pc as uname -a sees it: "Linux spf-laptop 3.11.0-4-generic #9-Ubuntu SMP Mon Aug 26 15:22:48 UTC 2013 i686 i686 i686 GNU/Linux" .

I usually use the 3.10.0-5-lowlatency that used to work too, but now as the latest it doesn't work.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: spf 3658 F.... pulseaudio
Date: Thu Aug 29 23:14:35 2013
HibernationDevice: RESUME=UUID=ebbfa61f-aeb2-4af6-9b6a-37d97c91a113
InstallationDate: Installed on 2012-11-10 (292 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MachineType: ASUSTeK Computer INC. 1001PX
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=14c0d5bf-f93d-46b7-b890-da6ed3a078e7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-4-generic N/A
 linux-backports-modules-3.11.0-4-generic N/A
 linux-firmware 1.113
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0904
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1001PX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd08/12/2010:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1001PX
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

We have noted that there is a newer version of the kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest kernel for this release by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get install linux

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

[Francesco Bonanno (mibo-fra)]

I've upgrated yesterday and today (4-09-2013) works on both kernels (the latest and the lowlatency I usually use). I do daily the upgrades so before I set the bug to fix released if you don't have problems I'll try with the next upgrades of the kernel and co to see if the bug is still in the system (2 or 3 releases of linux) and after I'll change the status of the bug. Thanks for the support.

[Joseph Salisbury (jsalisbury)]

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Francesco Bonanno (mibo-fra)]

Ok something strange, I've noticed that my phone isn't plus detected when the system upgrafe the dkms modules. So the next upgrade I'll add the logs of it. For this reason I don't knoe if I've to set this big as confirmed i change the target of it.

[Francesco Bonanno (mibo-fra)]

It seems fixed so I change the status of the bug.