@Steve
It be nice if we could figure out whether or not ofono has a role in
this bug. Could you try disabling ofono via an upstart .override file,
reboot the phone, and see if you can get it in the same state?
I managed to wedge the phone pretty good by disabling 3g, connecting to
my home AP, then heading out of range of my AP. The odd thing was that
I was able to get chewie-network-menu server to grab all the CPU vs. NM.
Maybe this was because once I got out of range, I opened the network-
indicator ( which went crazy, re-painting every few seconds, and still
showing my home AP as connected ). When I got back to my loft and
attached the phone via USB, chewie-network-menu-server had 96+% of the
CPU!
I'll re-try the same scenario without messing with the indicator and see
if NM grabs the CPU instead...
One last comment, as opposed to strace, perhaps you could start with a
fresh syslog ( remove it, then reboot ), and then do a grep of
"NetworkManager" to pull all the NM messages into a single file.
** Changed in: touch-preview-images
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206405
Title:
network-manager using 70%+ CPU on Nexus 4
To manage notifications about this bug go to:
https://bugs.launchpad.net/touch-preview-images/+bug/1206405/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
