[ROM][BETA] Quattrimus ICS

Toggle sidebar Toggle sidebar
im wondering if maybe rmnet0 drivers in the kernel need updating? here's logcat from what happens during wifi hotspot tethering:

Code: 
D/DHCP    ( 1800): configuring rmnet0
D/ConnectivityService( 1910): ConnectivityChange for mobile: CONNECTED/CONNECTED
D/ConnectivityService( 1910): ConnectivityChange for mobile_hipri: CONNECTED/CONNECTED
W/NetworkStats( 1910): dropping UID delta from unknown iface: iface=wl0.1 uid=0 set=DEFAULT tag=0x0 rxBytes=0 rxPackets=0 txBytes=56 txPackets=1 operations=0
W/NetworkStats( 1910): dropping UID delta from unknown iface: iface=rmnet0 uid=0 set=DEFAULT tag=0x0 rxBytes=612 rxPackets=2 txBytes=76 txPackets=1 operations=0
[B]E/SecondaryTablController( 1798): ip route add failed: /system/bin/ip route add 28.194.86.161/32 via 0.0.0.0 dev rmnet0 table 60
W/FrameworkListener( 1798): Handler 'interface' error (No such device)
E/ConnectivityService( 1910): Exception trying to add a route: java.lang.IllegalStateException: Unable to communicate with native daemon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route add rmnet0 secondary 28.194.86.161 32 0.0.0.0} failed with code 400 : {ip route modification failed (No such device)}
E/SecondaryTablController( 1798): ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 28.194.86.161 dev rmnet0 table 60
W/FrameworkListener( 1798): Handler 'interface' error (No such device)
E/ConnectivityService( 1910): Exception trying to add a route: [/B]java.lang.IllegalStateException: Unable to communicate with native daemon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route add rmnet0 secondary 0.0.0.0 0 28.194.86.161} failed with code 400 : {ip route modification failed (No such device)}
D/NetworkPolicy( 1910): applying policy NetworkPolicy[NetworkTemplate: matchRule=MOBILE_ALL, subscriberId=valid]: cycleDay=19, warningBytes=2147483648, limitBytes=-1, lastSnooze=-1 to ifaces [rmnet0, rmnet0]
D/NetworkPolicy( 1910): applying policy NetworkPolicy[NetworkTemplate: matchRule=MOBILE_ALL, subscriberId=valid]: cycleDay=19, warningBytes=2147483648, limitBytes=-1, lastSnooze=-1 to ifaces [rmnet0, rmnet0]
D/ConnectivityService( 1910): NetTransition Wakelock for WifiStateMachine released by timeout
I/GTalkService/c( 2063): [AndroidEndpoint@1092301488] connect: acct=1000000, state=CONNECTING
D/Tethering( 1910): TetherModeAliveState.processMessage what=3
D/Tethering( 1910): chooseUpstreamType(true), preferredApn =5, got type=0
D/TetherController( 1798): setDnsForwarders(0 = '68.28.230.132')
D/TetherController( 1798): setDnsForwarders(1 = '68.28.231.132')
D/TetherController( 1798): Sending update msg to dnsmasq [update_dns:68.28.230.132:68.28.231.132]
I/dnsmasq ( 3284): using nameserver 68.28.231.132#53
I/dnsmasq ( 3284): using nameserver 68.28.230.132#53
D/Tethering( 1910): notifying tethered with iface =rmnet0
D/Tethering( 1910): TetheredState.processMessage what=12
E/NatController( 1798): IP rule -6 rule add from fe80::/64 table 60 got 65024
D/PicasaSyncManager( 2817): active network: NetworkInfo: type: mobile[CDMA - EvDo rev. A], state: CONNECTED/CONNECTED, reason: (unspecified), extra: , roaming: false, failover: true, isAvailable: true
D/PicasaSyncManager( 2817): background data: true
E/NatController( 1798): IP route route add fe80::/64 dev wlan0 table 60 got 65024
I/MediaUploader( 2844): No need to wake up
E/NatController( 1798): Error setting forward rules
E/NetworkManagementService( 1910): enableNat got Exception com.android.server.NativeDaemonConnectorException: Cmd {nat enable wlan0 rmnet0 2 fe80::/64 192.168.43.0/24} failed with code 400 : {Nat operation failed (No such device)}
E/Tethering( 1910): Exception enabling Nat: java.lang.IllegalStateException: Unable to communicate to native daemon for enabling NAT interface
E/WifiStateMachine( 1910): Tethering reports wifi as untethered!, shut down soft Ap

full logcat:

http://pastebin.com/Ba35gWRv
 
  • Like
Reactions: Badboytoast
magus7091 said:
Sitting in recovery with not much else to do, anything I can try to do to fix it or diagnose it? I'll be a guinea pig for a while if it'll help me or anyone else...
Click to expand...

Check that /data/app exists and is a normal directory and is empty. Then reboot and capture a log with logcat -d and post it in an attachment.
 
  • Like
Reactions: magus7091
@tcrider84 does rmnet0 exist? What does the shell say when you run these commands?
 
Sorry, kinda nub-ish with adb, but would this just be booting from recovery and then dumping the logcat to a file?
 
tdm said:
@tcrider84 does rmnet0 exist? What does the shell say when you run these commands?
Click to expand...

LOL i just checked build.prop:

#mobiledata.interfaces=rmnet0,rmnet1,rmnet2

it's commented out. maybe we need to allow it and change it to whatever our 3g's interface is? that doesnt make sense though because later down under the #BT section it has #mobiledata.interfaces=wlan0,ppp0
 
Last edited:
magus7091 said:
Sorry, kinda nub-ish with adb, but would this just be booting from recovery and then dumping the logcat to a file?
Click to expand...

No you capture logcat from the running system. On your pc run "adb logcat -d > logcat.txt"
 
tcrider84 said:
LOL i just checked build.prop:

#mobiledata.interfaces=rmnet0,rmnet1,rmnet2

it's commented out. maybe we need to allow it and change it to whatever our 3g's interface is? that doesnt make sense though because later down under the #BT section it has #mobiledata.interfaces=wlan0,ppp0
Click to expand...

Paste contents of /proc/net/dev.
 
Code: 
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    1440      20    0    0    0     0          0         0     1440      20    0    0    0     0       0          0
dummy0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet0:     612       2    0    0    0     0          0         0      764       4    0    0    0     0       0          0
rmnet1:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet2:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet3:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet4:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet5:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet6:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet7:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  usb0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  sit0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
ip6tnl0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
 wlan0:  405658     596    0    0    0     0          0         0    75066     612    0    0    0     0       0          0


I wonder if this commit might have anything to do with it(reguarding channel names):
https://github.com/marc1706/desire_kernel_35/commit/4b1737cdc19379fecfd19b192dbcad7f9d684428

nope. not a channel issue.
 
Last edited:
Okay, I waited until all the boot stuff was done, should I grab it as soon as I have a desktop, immediately after "upgrading applications" disappears? That does appear every boot, I don't know if it's everyone or just me FWIW.
 
ryder815 said:
when will u have a different boot animation for AOKP ?
Click to expand...

what are you looking for?? Isnt the unicorn their trademark?
Picture-11.png
Would you prefer farting unicorns??
 
tcrider84 said:
im wondering if maybe rmnet0 drivers in the kernel need updating? here's logcat from what happens during wifi hotspot tethering:

Code: 
D/DHCP    ( 1800): configuring rmnet0
D/ConnectivityService( 1910): ConnectivityChange for mobile: CONNECTED/CONNECTED
D/ConnectivityService( 1910): ConnectivityChange for mobile_hipri: CONNECTED/CONNECTED
W/NetworkStats( 1910): dropping UID delta from unknown iface: iface=wl0.1 uid=0 set=DEFAULT tag=0x0 rxBytes=0 rxPackets=0 txBytes=56 txPackets=1 operations=0
W/NetworkStats( 1910): dropping UID delta from unknown iface: iface=rmnet0 uid=0 set=DEFAULT tag=0x0 rxBytes=612 rxPackets=2 txBytes=76 txPackets=1 operations=0
[B]E/SecondaryTablController( 1798): ip route add failed: /system/bin/ip route add 28.194.86.161/32 via [B][B][COLOR="Red"]0.0.0.0[/COLOR][/B][/B] dev rmnet0 table 60
W/FrameworkListener( 1798): Handler 'interface' error (No such device)
E/ConnectivityService( 1910): Exception trying to add a route: java.lang.IllegalStateException: Unable to communicate with native daemon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route add rmnet0 secondary 28.194.86.161 32 [B][COLOR="Red"]0.0.0.0[/COLOR][/B]} failed with code 400 : {ip route modification failed (No such device)}
E/SecondaryTablController( 1798): ip route add failed: /system/bin/ip route add [B]0.0.0.0[/B]/0 via 28.194.86.161 dev rmnet0 table 60
W/FrameworkListener( 1798): Handler 'interface' error (No such device)
E/ConnectivityService( 1910): Exception trying to add a route: [/B]java.lang.IllegalStateException: Unable to communicate with native daemon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route add rmnet0 secondary [COLOR="Red"]0.0.0.0[/COLOR] 0 28.194.86.161} failed with code 400 : {ip route modification failed (No such device)}
D/NetworkPolicy( 1910): applying policy NetworkPolicy[NetworkTemplate: matchRule=MOBILE_ALL, subscriberId=valid]: cycleDay=19, warningBytes=2147483648, limitBytes=-1, lastSnooze=-1 to ifaces [rmnet0, rmnet0]
D/NetworkPolicy( 1910): applying policy NetworkPolicy[NetworkTemplate: matchRule=MOBILE_ALL, subscriberId=valid]: cycleDay=19, warningBytes=2147483648, limitBytes=-1, lastSnooze=-1 to ifaces [rmnet0, rmnet0]
D/ConnectivityService( 1910): NetTransition Wakelock for WifiStateMachine released by timeout
I/GTalkService/c( 2063): [AndroidEndpoint@1092301488] connect: acct=1000000, state=CONNECTING
D/Tethering( 1910): TetherModeAliveState.processMessage what=3
D/Tethering( 1910): chooseUpstreamType(true), preferredApn =5, got type=0
D/TetherController( 1798): setDnsForwarders(0 = '68.28.230.132')
D/TetherController( 1798): setDnsForwarders(1 = '68.28.231.132')
D/TetherController( 1798): Sending update msg to dnsmasq [update_dns:68.28.230.132:68.28.231.132]
I/dnsmasq ( 3284): using nameserver 68.28.231.132#53
I/dnsmasq ( 3284): using nameserver 68.28.230.132#53
D/Tethering( 1910): notifying tethered with iface =rmnet0
D/Tethering( 1910): TetheredState.processMessage what=12
E/NatController( 1798): IP rule -6 rule add from fe80::/64 table 60 got 65024
D/PicasaSyncManager( 2817): active network: NetworkInfo: type: mobile[CDMA - EvDo rev. A], state: CONNECTED/CONNECTED, reason: (unspecified), extra: , roaming: false, failover: true, isAvailable: true
D/PicasaSyncManager( 2817): background data: true
E/NatController( 1798): IP route route add fe80::/64 dev wlan0 table 60 got 65024
I/MediaUploader( 2844): No need to wake up
E/NatController( 1798): Error setting forward rules
E/NetworkManagementService( 1910): enableNat got Exception com.android.server.NativeDaemonConnectorException: Cmd {nat enable wlan0 rmnet0 2 fe80::/64 192.168.43.0/24} failed with code 400 : {Nat operation failed (No such device)}
E/Tethering( 1910): Exception enabling Nat: java.lang.IllegalStateException: Unable to communicate to native daemon for enabling NAT interface
E/WifiStateMachine( 1910): Tethering reports wifi as untethered!, shut down soft Ap

full logcat:

tetherbroke - Pastebin.com
Click to expand...

ok, im not able to code...but what is the 0.0.0.0? what does that refer to? is that a dns address? a blank address isnt going to go anywhere in dhcp or dns. only a guess, but with this address, maybe this is where its looking for the device that it cant communicate with?
 
cbucz24 said:
ok, im not able to code...but what is the 0.0.0.0? what does that refer to? is that a dns address? a blank address isnt going to go anywhere in dhcp or dns. only a guess, but with this address, maybe this is where its looking for the device that it cant communicate with?
Click to expand...

0.0.0.0 is an empty or null address. It can be valid for certain uses but probably not in this case.
 
tcrider84 said:
Code: 
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    1440      20    0    0    0     0          0         0     1440      20    0    0    0     0       0          0
dummy0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet0:     612       2    0    0    0     0          0         0      764       4    0    0    0     0       0          0
rmnet1:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet2:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet3:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet4:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet5:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet6:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
rmnet7:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  usb0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  sit0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
ip6tnl0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
 wlan0:  405658     596    0    0    0     0          0         0    75066     612    0    0    0     0       0          0


I wonder if this commit might have anything to do with it(reguarding channel names):
https://github.com/marc1706/desire_kernel_35/commit/4b1737cdc19379fecfd19b192dbcad7f9d684428

nope. not a channel issue.
Click to expand...

So it does exist. Those routes looked screwy though.
 
You must log in or register to reply here.

Similar threads

tdm
[ROM][BETA] Quattrimus ICS
Replies
296
Views
64K
LG Vortex
mdlash
M
tdm
[ROM][BETA] Quattrimus ICS (ZVD)
Replies
488
Views
71K
LG Optimus S Rooting, ROMs, and Hacks
williek113
W
D
HELP with going from GB to ICS on my Optimus V (AOKP Quattrimus)
Replies
6
Views
3K
Virgin Mobile Optimus V
AndyOpie150
A
D
Would MHL work with Quattrimus ICS CM9 ROM
Replies
5
Views
3K
Optimus V Rooting, ROMs, and Hacks
cole2kb
C
B
  • Locked
Quattrimus ICS ROM now available for Optimus S!
Replies
30
Views
9K
LG Optimus S Rooting, ROMs, and Hacks
cole2kb
C

Latest posts

Trending Posts

Members online

Total: 3,199 (members: 11, guests: 3,188)

Forum statistics

Threads
957,956
Messages
6,975,084
Members
3,163,948
Latest member
fulapmu2

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom