PS: Should t be in development?
Hi,
I'm working on my AOSP branch of my ROM but I get a weired problem that I cannot solve since almost a week.
So I check'ed out the AOSP code from scrach and try it.
I/ Point #1: It hangs
Here is what happens:
- compile
- flash
- flash gapps-up frf91
- reboot
Now SetupWizard.apk hangs for ever on the "Signing in..." screen.
I tried branches: froyo, android-2.2_r1 and android-2.2_r1.1... all the same.
adb logcat shows me:
Code:
I/SetupWizard( 211): Got response: SUCCESS
D/SetupWizard( 211): in mWaitForAndroidId.run()
D/GoogleLoginService( 211): in waitForAndroidId result=0
D/SetupWizard( 211): waitForAndroidId returned: 0
then
Code:
D/MobileDataStateTracker( 83): replacing old mInterfaceName (rmnet0) with rmnet0 for hipri
D/MobileDataStateTracker( 83): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default
D/NetworkLocationProvider( 83): onDataConnectionStateChanged 3
D/MobileDataStateTracker( 83): replacing old mInterfaceName (rmnet0) with rmnet0 for hipri
D/MobileDataStateTracker( 83): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default
D/NetworkLocationProvider( 83): onDataConnectionStateChanged 3
D/SntpClient( 83): request time failed: java.net.SocketTimeoutException: Connection timed out
Over and over and over again...
II/ Point #2: It partially worked
Then I do a hard reboot.
When it reboots, I go to Settings, accounts etc.
From there I can see my account... sync is on so I click on it:
- Contacts: OFF
- Gmail: OFF
- Picasa: ON
- Calendar: ON
I tried douzens of times and no matter the time I wait on the "Signing in screen", I always get the same logcat and results.
Please, help me guess what's wrong.
Full logcat: http://fpaste.org/xNXT/
-----
What could I do wrong by building strict from AOSP?
Thanks a lot!
http://pastebin.com/im1v07hZ
Jr33 said:
http://pastebin.com/im1v07hZ
Click to expand...
Click to collapse
Yeah I'm trying thanks bro!
I'm wondering... if "@null" was in place, does it means my AOSP build was not using NetworkLocation.apk ?
Because I saw on CM' git repo and its: "@null" and "@null"... wonder how CM get it working
leonnib4 said:
Yeah I'm trying thanks bro!
I'm wondering... if "@null" was in place, does it means my AOSP build was not using NetworkLocation.apk ?
Because I saw on CM' git repo and its: "@null" and "@null"... wonder how CM get it working
Click to expand...
Click to collapse
i think he has it in the vendor overlay. if "@null" is in place it will not use any network location
Well still not a go.
I'm having the same sockets timeouts...
When logging from the "normal" way and when logging in the "browser" way (menu then "Browser sign-in"):
D/Genie ( 540): Can not get the location from network
D/SntpClient( 89): request time failed: java.net.SocketTimeoutException: Connection timed out
...
Here is the fix!
Thanks to Jr33 !!!
In order to get the SetupWizard.apk properly working when building from AOSP, in my case, android-2.2_r1.1 (full-passion-eng), you need to merge this:
- http://pastebin.com/im1v07hZ
- http://pastebin.com/yqjnY3xP
And it simply works!
Thanks to Jr33 !!!
I actually spent 7 days on that issue...
Every day I get at least one or two random reboots... Anyone know the issue or have it too?
Sent from my C6903 using xda app-developers app
teamHTC said:
Every day I get at least one or two random reboots... Anyone know the issue or have it too?
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
+1
Experienced the same issue 2 weeks ago twice:
first time after clearing RAM with NQ Android Booster (all my apps collected in folders got "unfoldered" and some icons were suddenly missing (phone-icon, TXT-msg-Icon etc.)
After uninstalling NQ Android booster I got it a second time while adjusting camera settings during a photo-session.
Uninstalled "junk cleaner" too, since then no reboot any more.
Seems that SOME functions of Z1 get killed by optimizing apps and might cause a reboot. Check if You have apps like junk cleaner, RAM-cleaner or whatsoever installed ........
I had similar problems. Phone rebooted without me having even touched it. Noticed it when sitting in a passive car holder since it´s in my field of view.
I reflashed the phone with the latest firmware using the pc companion software from the sony mobile web page. Have not had any reboots since.
I got one random reboot per day after the new firmware update. I don't know if it was the same with the old firmware cause I used it just few hours. I don't have any app that optimize the system.
Sorry to bring this up again. But I somehow managed to collect the log from the kernel panic causing my Z1 random reboot (same every time).
I have a C6903. I have been suffering from random reboots since upgraded to firmware 14.1.G.2.257. Software ID: 1276-7842 R9A. Did the usual such as factory reset, PCC repair etc. but still happened.
Perhaps we can take a look at it if Sony releases the kernel source. Here is the stack trace:
<3>[41418.428108] ocmem: Failed to lock region graphics[0 -- fffff] ret = -22
<3>[41418.428119] ocmem: Failed to secure request de02fd00 for 0
<3>[41418.428129] ocmem: Failed to map ocmem request
<3>[41418.428148] ocmem allocation failed
<3>[41418.428159] kgsl kgsl-3d0: |adreno_start| OCMEM malloc failed
<3>[41418.429800] kgsl kgsl-3d0: |kgsl_pwrctrl_wake| start failed -12
<6>[41418.429812] SurfaceFlinger (1027): undefined instruction: pc=c0410014
<6>[41418.429822] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.429852] ------------[ cut here ]------------
<2>[41418.429861] kernel BUG at /home/hudsonslave/root/workspace/offbuild-rhine-1.0.2-honami-matrix/HUDSON_PRODUCT/honami/HUDSON_VARIANT/user/label/CM_OFFBLD/kernel/drivers/gpu/msm/kgsl_pwrctrl.c:1577!
<0>[41418.429880] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
<4>[41418.429888] Modules linked in: wlan(O) adsprpc adsp_loader cfg80211 texfat(PO) hid_sony(O) [last unloaded: wlan]
<4>[41418.429916] CPU: 0 Tainted: P W O (3.4.0-perf-g66807d4-02450-g9a218f1 #1)
<4>[41418.429929] PC is at kgsl_active_count_put+0x28/0x1f0
<4>[41418.429937] LR is at kgsl_ioctl+0x224/0x2f8
<4>[41418.429945] pc : [<c0410014>] lr : [<c0402a00>] psr: 60000013
<4>[41418.429947] sp : e2ca9e98 ip : 00000000 fp : 00000002
<4>[41418.429958] r10: c040395c r9 : 00000001 r8 : 40533814
<4>[41418.429966] r7 : c0402a00 r6 : fffffff4 r5 : e2ca9eb4 r4 : c0e66258
<4>[41418.429975] r3 : 00000000 r2 : c0ea7094 r1 : c0b53d24 r0 : c0e66258
<4>[41418.429984] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[41418.429993] Control: 10c5787d Table: 2b5f006a DAC: 00000015
<4>[41418.430000]
<4>[41418.430001] PC: 0xc040ff94:
<4>[41418.430008] ff94 eb007d50 e3a00000 e8bd8038 e5943418 e3530005 da000004 e5940000 e1a03005
<4>[41418.430034] ffb4 e59f102c e59f2018 eb007d24 e1a00004 e3a01000 ebfff917 e3e00015 e8bd8038
<4>[41418.430058] ffd4 c0b5017f c0940dff c0b50166 c0940e12 c0940e19 c0b50195 e92d41f0 e1a0700e
<4>[41418.430083] fff4 e5903354 e1a04000 e3530001 1a000000 e7f001f2 e5903370 e3530000 1a000000
<4>[41418.430108] 0014 e7f001f2 eb0002bd e5943370 e3530001 9a000026 e59f21a8 e2433001 e5843370
<4>[41418.430133] 0034 e5923004 e3530000 08bd81f0 e1a0100d e3c13d7f e3c3303f e5931004 e2811001
<4>[41418.430157] 0054 e5831004 e5926010 e3560000 0a00000c e2868008 e1a05006 e5953000 e1a01004
<4>[41418.430182] 0074 e5950004 e1a02007 e2855008 e12fff33 e0663005 e0833008 e5133008 e3530000
<4>[41418.430208]
<4>[41418.430209] LR: 0xc0402980:
<4>[41418.430215] 2980 13a0b001 1a000008 e5932410 e3520005 da000034 e5930000 e1a03004 e59f1128
<4>[41418.430240] 29a0 e59f2118 eb00b2aa ea00002e e5970000 e2800fd5 eb114b07 e35b0000 0a000003
<4>[41418.430265] 29c0 e5970000 eb003415 e2506000 ba000009 e3a09001 e1a00007 e1a01004 e1a02005
<4>[41418.430290] 29e0 e12fff3a e3590000 e1a06000 0a000006 e35b0000 0a000001 e5970000 eb00357a
<4>[41418.430315] 2a00 e5970000 e2800fd5 eb114a7e e3540000 aa000015 e1a0100d e3c13d7f e3c3303f
<4>[41418.430340] 2a20 e7ed2854 e5933008 e0981002 30d11003 33a03000 e3530000 1a000003 e1a00008
<4>[41418.430365] 2a40 e1a01005 ebfd4e55 e1a02000 e3520000 13e0600d ea000004 e3e0600b ea000002
<4>[41418.430389] 2a60 e3e0600d ea000000 e59f6060 e7ed4854 e354003f 9a000001 e1a00005 ebf8e429
<4>[41418.430415]
<4>[41418.430416] SP: 0xe2ca9e18:
..... <truncated>
<0>[41418.432046] Process SurfaceFlinger (pid: 1027, stack limit = 0xe2ca82f0)
<0>[41418.432055] Stack: (0xe2ca9e98 to 0xe2caa000)
<0>[41418.432063] 9e80: c0140910 e2ca9eb4
<0>[41418.432074] 9ea0: fffffff4 e3377b00 40533814 c0402a00 00000041 00000002 41433528 00000002
<0>[41418.432086] 9ec0: 00016e49 00000004 000003e8 0000000f c024767c e219f200 c0e1dcf8 011da09c
<0>[41418.432098] 9ee0: 02448000 d9ed20c8 e49c9190 00000000 c0252304 271ae91c e4803600 e3804b60
<0>[41418.432110] 9f00: 40533814 e3375b40 00000012 c0105f84 e2ca8000 00000000 00000000 c024f1ac
<0>[41418.432122] 9f20: 417157b8 c0252304 e219f200 00000000 e219f200 00000000 e219f24c c0252c48
<0>[41418.432134] 9f40: 00000002 d9ed20c0 e4641d78 e219f200 00000010 c0241ff0 c010b3e8 c01c5190
<0>[41418.432146] 9f60: e2ca9f90 e3375b40 40533814 c0140910 00000012 c0105f84 e2ca8000 00000000
<0>[41418.432158] 9f80: 00000000 c024f254 00000012 00000001 40533814 4056a04c c0140910 00000012
<0>[41418.432170] 9fa0: 00000036 c0105e00 4056a04c c0140910 00000012 c0140910 40533814 405337d4
<0>[41418.432181] 9fc0: 4056a04c c0140910 00000012 00000036 40533814 00000004 41433528 00000000
<0>[41418.432193] 9fe0: 40569f10 405337b8 40105a71 400f2088 00000010 00000012 00000000 00000000
<4>[41418.432209] [<c0410014>] (kgsl_active_count_put+0x28/0x1f0) from [<c0402a00>] (kgsl_ioctl+0x224/0x2f8)
<4>[41418.432224] [<c0402a00>] (kgsl_ioctl+0x224/0x2f8) from [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc)
<4>[41418.432238] [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc) from [<c024f254>] (sys_ioctl+0x34/0x54)
<4>[41418.432253] [<c024f254>] (sys_ioctl+0x34/0x54) from [<c0105e00>] (ret_fast_syscall+0x0/0x30)
<0>[41418.432266] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.432277] ---[ end trace 1b0d75d46d636dc3 ]---
<0>[41418.432286] Kernel panic - not syncing: Fatal exception
<3>[41419.435763] wcnss crash shutdown 0
patwang0311 said:
Sorry to bring this up again. But I somehow managed to collect the log from the kernel panic causing my Z1 random reboot (same every time).
I have a C6903. I have been suffering from random reboots since upgraded to firmware 14.1.G.2.257. Software ID: 1276-7842 R9A. Did the usual such as factory reset, PCC repair etc. but still happened.
Perhaps we can take a look at it if Sony releases the kernel source. Here is the stack trace:
<3>[41418.428108] ocmem: Failed to lock region graphics[0 -- fffff] ret = -22
<3>[41418.428119] ocmem: Failed to secure request de02fd00 for 0
<3>[41418.428129] ocmem: Failed to map ocmem request
<3>[41418.428148] ocmem allocation failed
<3>[41418.428159] kgsl kgsl-3d0: |adreno_start| OCMEM malloc failed
<3>[41418.429800] kgsl kgsl-3d0: |kgsl_pwrctrl_wake| start failed -12
<6>[41418.429812] SurfaceFlinger (1027): undefined instruction: pc=c0410014
<6>[41418.429822] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.429852] ------------[ cut here ]------------
<2>[41418.429861] kernel BUG at /home/hudsonslave/root/workspace/offbuild-rhine-1.0.2-honami-matrix/HUDSON_PRODUCT/honami/HUDSON_VARIANT/user/label/CM_OFFBLD/kernel/drivers/gpu/msm/kgsl_pwrctrl.c:1577!
<0>[41418.429880] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
<4>[41418.429888] Modules linked in: wlan(O) adsprpc adsp_loader cfg80211 texfat(PO) hid_sony(O) [last unloaded: wlan]
<4>[41418.429916] CPU: 0 Tainted: P W O (3.4.0-perf-g66807d4-02450-g9a218f1 #1)
<4>[41418.429929] PC is at kgsl_active_count_put+0x28/0x1f0
<4>[41418.429937] LR is at kgsl_ioctl+0x224/0x2f8
<4>[41418.429945] pc : [<c0410014>] lr : [<c0402a00>] psr: 60000013
<4>[41418.429947] sp : e2ca9e98 ip : 00000000 fp : 00000002
<4>[41418.429958] r10: c040395c r9 : 00000001 r8 : 40533814
<4>[41418.429966] r7 : c0402a00 r6 : fffffff4 r5 : e2ca9eb4 r4 : c0e66258
<4>[41418.429975] r3 : 00000000 r2 : c0ea7094 r1 : c0b53d24 r0 : c0e66258
<4>[41418.429984] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[41418.429993] Control: 10c5787d Table: 2b5f006a DAC: 00000015
<4>[41418.430000]
<4>[41418.430001] PC: 0xc040ff94:
<4>[41418.430008] ff94 eb007d50 e3a00000 e8bd8038 e5943418 e3530005 da000004 e5940000 e1a03005
<4>[41418.430034] ffb4 e59f102c e59f2018 eb007d24 e1a00004 e3a01000 ebfff917 e3e00015 e8bd8038
<4>[41418.430058] ffd4 c0b5017f c0940dff c0b50166 c0940e12 c0940e19 c0b50195 e92d41f0 e1a0700e
<4>[41418.430083] fff4 e5903354 e1a04000 e3530001 1a000000 e7f001f2 e5903370 e3530000 1a000000
<4>[41418.430108] 0014 e7f001f2 eb0002bd e5943370 e3530001 9a000026 e59f21a8 e2433001 e5843370
<4>[41418.430133] 0034 e5923004 e3530000 08bd81f0 e1a0100d e3c13d7f e3c3303f e5931004 e2811001
<4>[41418.430157] 0054 e5831004 e5926010 e3560000 0a00000c e2868008 e1a05006 e5953000 e1a01004
<4>[41418.430182] 0074 e5950004 e1a02007 e2855008 e12fff33 e0663005 e0833008 e5133008 e3530000
<4>[41418.430208]
<4>[41418.430209] LR: 0xc0402980:
<4>[41418.430215] 2980 13a0b001 1a000008 e5932410 e3520005 da000034 e5930000 e1a03004 e59f1128
<4>[41418.430240] 29a0 e59f2118 eb00b2aa ea00002e e5970000 e2800fd5 eb114b07 e35b0000 0a000003
<4>[41418.430265] 29c0 e5970000 eb003415 e2506000 ba000009 e3a09001 e1a00007 e1a01004 e1a02005
<4>[41418.430290] 29e0 e12fff3a e3590000 e1a06000 0a000006 e35b0000 0a000001 e5970000 eb00357a
<4>[41418.430315] 2a00 e5970000 e2800fd5 eb114a7e e3540000 aa000015 e1a0100d e3c13d7f e3c3303f
<4>[41418.430340] 2a20 e7ed2854 e5933008 e0981002 30d11003 33a03000 e3530000 1a000003 e1a00008
<4>[41418.430365] 2a40 e1a01005 ebfd4e55 e1a02000 e3520000 13e0600d ea000004 e3e0600b ea000002
<4>[41418.430389] 2a60 e3e0600d ea000000 e59f6060 e7ed4854 e354003f 9a000001 e1a00005 ebf8e429
<4>[41418.430415]
<4>[41418.430416] SP: 0xe2ca9e18:
..... <truncated>
<0>[41418.432046] Process SurfaceFlinger (pid: 1027, stack limit = 0xe2ca82f0)
<0>[41418.432055] Stack: (0xe2ca9e98 to 0xe2caa000)
<0>[41418.432063] 9e80: c0140910 e2ca9eb4
<0>[41418.432074] 9ea0: fffffff4 e3377b00 40533814 c0402a00 00000041 00000002 41433528 00000002
<0>[41418.432086] 9ec0: 00016e49 00000004 000003e8 0000000f c024767c e219f200 c0e1dcf8 011da09c
<0>[41418.432098] 9ee0: 02448000 d9ed20c8 e49c9190 00000000 c0252304 271ae91c e4803600 e3804b60
<0>[41418.432110] 9f00: 40533814 e3375b40 00000012 c0105f84 e2ca8000 00000000 00000000 c024f1ac
<0>[41418.432122] 9f20: 417157b8 c0252304 e219f200 00000000 e219f200 00000000 e219f24c c0252c48
<0>[41418.432134] 9f40: 00000002 d9ed20c0 e4641d78 e219f200 00000010 c0241ff0 c010b3e8 c01c5190
<0>[41418.432146] 9f60: e2ca9f90 e3375b40 40533814 c0140910 00000012 c0105f84 e2ca8000 00000000
<0>[41418.432158] 9f80: 00000000 c024f254 00000012 00000001 40533814 4056a04c c0140910 00000012
<0>[41418.432170] 9fa0: 00000036 c0105e00 4056a04c c0140910 00000012 c0140910 40533814 405337d4
<0>[41418.432181] 9fc0: 4056a04c c0140910 00000012 00000036 40533814 00000004 41433528 00000000
<0>[41418.432193] 9fe0: 40569f10 405337b8 40105a71 400f2088 00000010 00000012 00000000 00000000
<4>[41418.432209] [<c0410014>] (kgsl_active_count_put+0x28/0x1f0) from [<c0402a00>] (kgsl_ioctl+0x224/0x2f8)
<4>[41418.432224] [<c0402a00>] (kgsl_ioctl+0x224/0x2f8) from [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc)
<4>[41418.432238] [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc) from [<c024f254>] (sys_ioctl+0x34/0x54)
<4>[41418.432253] [<c024f254>] (sys_ioctl+0x34/0x54) from [<c0105e00>] (ret_fast_syscall+0x0/0x30)
<0>[41418.432266] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.432277] ---[ end trace 1b0d75d46d636dc3 ]---
<0>[41418.432286] Kernel panic - not syncing: Fatal exception
<3>[41419.435763] wcnss crash shutdown 0
Click to expand...
Click to collapse
So it was a software failure?
El.Guaje said:
So it was a software failure?
Click to expand...
Click to collapse
Think it is. When I was using 1.534, I didn't even see a single random reboot. I have now just reverted back to that older firmware to see if it will last a week without reboot.
I recall seeing Google claimed to have fixed Nexus 10 random reboot issue with the release of 4.3 (btw, N10 was having similar kernel panic with GPU code a while back) - not sure if that's really fixed. Hopefully Sony is aware of this rather than denying it and give us a fix some time in the future.
I have mentioned in another thread that you can actually accelerate the occurrence of random reboot by turning on 'Force GPU Rendering' in 'Developer Options'. That will force all 2D apps to render with GPU -> which will make it crashes a lot sooner. Not ticking that option won't make the problem go away, just delaying it from happening unless you don't use your GPU at all.
patwang0311 said:
Think it is. When I was using 1.534, I didn't even see a single random reboot. I have now just reverted back to that older firmware to see if it will last a week without reboot.
I recall seeing Google claimed to have fixed Nexus 10 random reboot issue with the release of 4.3 (btw, N10 was having similar kernel panic with GPU code a while back) - not sure if that's really fixed. Hopefully Sony is aware of this rather than denying it and give us a fix some time in the future.
I have mentioned in another thread that you can actually accelerate the occurrence of random reboot by turning on 'Force GPU Rendering' in 'Developer Options'. That will force all 2D apps to render with GPU -> which will make it crashes a lot sooner. Not ticking that option won't make the problem go away, just delaying it from happening unless you don't use your GPU at all.
Click to expand...
Click to collapse
I see, me phone reboot after 3 days. Sometimes one day it reboot twice.
It does not reboot while I'm using the phone. It happen when I leave the phone alone in my desk or in my pocket.
I hope 4.3 will fix this problem, with 4.2.2 build 534 I've heard that It may cause Sleep of Death so I don't reverse back.
Same problem, I need solution
teamHTC said:
Every day I get at least one or two random reboots... Anyone know the issue or have it too?
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
I am having the same problem with my Xperia Z1, I have tried too many things and read a lot of threads to solve this issue but no one solution or trick works on this issue.......... Help me..
I have the same problem - the phone restarts. But I can stop the restarts by:
1) Turn of Bluetooth. When Bluetooth is on, it restarts 1-2 times a day. When using bluetooth for external devices it restarts more often.
2) Turn off wi-fi. And just using 3G/4G/LTE. When entering a 'known' wi-fi (home or Work) it surely restarts every time.
It's not a solution, but hopefully it's solved in 4.3 and 4.4. I have tried to reset phone, new simcard etc.
Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
So I am not alone
hsafenix said:
Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks
Click to expand...
Click to collapse
+1 here
I believe that it all started around 0427 Nightly, not sure, though.
I thought of switching to 2g network only yesterday after reading an old post in CM forums.
Did not have time to pull a logcat, yet, thanks for sharing! Hope somebody will figure out what the problem can be...
Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
My settings are as per wind IT specifications, but I noticed that in CM settings there is much more than specified by Wind, such as apn protocol, apn roaming protocol and bearer, which values are unknown to me. Will investigate on those values.
Tried also with official CM11 stock kernel, with no success.
No, I did not try with no apps installed, I will keep this test as the very last resort. I did not install new apps since when the problem started.
Inviato dal mio GT-P3110 utilizzando Tapatalk
Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
I checked the apn settings and they are ok..
It happened with a fresh install as well, when I fleshed CM10.
I didn't try another kernel yet, but Ottonet did and it did not solve the problem
SignalStrength: Hotfix TD-SCDMA
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.
Ottonet said:
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.
Click to expand...
Click to collapse
Just confirming, I also installed the last nightly (05-24) and the problem persists.
Does anyone think it could be a hardware problem?
hsafenix said:
Does anyone think it could be a hardware problem?
Click to expand...
Click to collapse
Hi..the problem still persists (I'm on Wind). I've always used Vanir, now I switched to official Cyanogen Nightly...still nothing happens
Hi. I had cellular network problems (no signal) in omni ROM and cm official too. Anyone tryed changing base band? I have v20a EUR ... Anyone tryed different?
Inviato dal mio LG-P880 utilizzando Tapatalk
I'm posting some modem.log , hoping it's not against forum rules (can remove if it is)
06-12 15:28:24.105 D/GsmDCT ( 896): overall state is CONNECTED
06-12 15:28:24.105 D/GsmDCT ( 896): startDataStallAlarm: tag=61578 delay=60s
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 0
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: wakelock acquired
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [UNSL]< _LGE_RESTART_RILD {AT Command Timeout}
06-12 15:30:00.745 D/use-Rlog/RLOG-AT( 151): dlc[12] atchannel: at_send_command_full() end; err:-4
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [1666]< DATA_CALL_LIST fails by E_REQ_TIMEOUT
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12] lge-ril: requestInterface(DATA_CALL_LIST) invoking *requestFunction(req:57, data: 0x00000000, len:0)...DONE
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 1074013352. s_dlc_handler_create_tracker - 0x301ff
06-12 15:30:00.755 D/RILJ ( 896): *********RILJ: LgeRestartRild Start
06-12 15:30:00.755 D/RILJ ( 896): ### Show RIL Recovery popup ###
06-12 15:30:00.825 E/RILJ ( 896): Uncaught exception read length=52Exception:java.lang.NullPointerException
06-12 15:30:00.825 I/RILJ ( 896): Disconnected from 'rild' socket
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Poll ServiceState done: oldSS=[0 0 home I WIND I WIND 22288 UMTS UMTS CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 home null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=1 mNewMaxDataCalls=1 oldReasonDataDenied=-1 mNewReasonDataDenied=-1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] RAT switched UMTS -> Unknown at cell -1
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/PhoneProxy( 896): [PhoneProxy] updatePhoneObject: radioTechnology=0
06-12 15:30:00.825 E/use-Rlog/RLOG-RILC( 151): error on reading command socket errno:104
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Iwlan feature available = false
06-12 15:30:00.825 D/RilRequest( 896): [5314]< DATA_CALL_LIST error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=null
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): libril: new connection
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_SIM_READY}
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): RIL Daemon version: android lge-ril 1.0
06-12 15:30:00.835 I/RILJ ( 896): Connected to 'rild' socket
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: radio is on but out of service, set plmn='Nessun servizio.'
06-12 15:30:00.865 D/RILJ ( 896): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.865 D/RILJ ( 896): [0213]> RADIO_POWER off
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: changed sending intent rule=2 showPlmn='true' plmn='Nessun servizio.' showSpn='false' spn=''
06-12 15:30:00.885 D/RILJ ( 896): [0214]> REQUEST_SET_PREFERRED_NETWORK_TYPE : 0
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]> RADIO_POWER (0)
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]< RADIO_POWER fails by E_RAIDO_NOT_AVAILABLE
Inviato dal mio LG-P880 utilizzando Tapatalk
I have additionally extreme battery consumption.
I have this problem too.
With Resurrection Remix (CM 11 based) and Wind IT....
complete logs
Happened today, gathered all the logs i could. Kernel dmesg, modem log And main log.
All with official CM11 from 17/06. But it's the same on other cm11 based.
Time is:
<4>[14:06:18 18:49:45.571] ##@acm_read_bulk !ACM_READY
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] !!!!! ts_ldisc_close !!!!!
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] ### CP Crash : 1, USB DISCONNECT : 0 ###
I have the same problem as well, it started around 2 - 3 weeks ago, I was on beanstalk 4.4.2, a build from march, if I remember correctly. I had no issues before, but suddenly I lost signal every time on 3G. I tried several Roms with and without the RIL-Patch by Flying_Bear, but nothing helped so far. The only "workaround" is to stay on 2G. I'm starting to get tired of constantly reflashing my phone to try other Roms.
Its strange, that the same error occurred around the same time for so many people. I would like to know if it also happens on stock, or if its a special hardware-revision that fails. My phone version is SWS-Black (Swiss market, but bought in Germany).
It looks like something in the connection behavior got changed. When using earlier nightlies you could observe the phone connecting via HSPA+ (H+) everytime it was possible. But in later builds the phone only connects via HSPA+ if you actively use mobile data and changes back the connection to HSDPA (H) afterwards, thus resulting in constant changes between those network types. I believe this change was included to save battery but it really doesn't if your phone constantly loses connection and you have to reboot. Maybe this change was a global one but as you can see our phone can't handle it. Hopefully demetris can either identify that change and revert it or fix it.
@rob3110 , i understand your frustration, i'm changing ROM too. I also did try EPRJ RIL without success. Now I'm experimenting a RIL from CM 10.2. It seems no Dev is looking into it, it's a pity. I'm trying to analyze error logs but I'm no real Dev... You can post your logs if you like
Inviato dal mio LG-P880 utilizzando Tapatalk
Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
1. install your rom of your choice.
don't modify anything, no ril, nothing...
2. shutdown your system and remove your battery. Now press the power button for 30 seconds. Wait further one minute. Now insert your battery back and start handy. enjoy your network... ?
Click to expand...
Click to collapse
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?
rob3110 said:
Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?
Click to expand...
Click to collapse
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.
rootarded said:
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.
Click to expand...
Click to collapse
Yeah, didn't work for me either. I still get those disconnects on 3G. I will ask my carrier (E-Plus) if there was a recent change to the 3G-network that might have brought us this error, but I don't think they will give me a useful answer...
I am using unlocked and activated HTC One M7 sprint edition in GSM network, rooted. ViperOne appeared to be the best ROM for my device, along with brilliant ElementalX kernel. but as some other people I've suffered from dotfstrim kernel wakelock that usually came at nights when phone was charged and sleeping on the table.
I've found that trim file system service could be made manually using fstrim tool and starting from 4.3 trim events processed at the volume daemon (vold) triggered by idle maintenance event. that event is interesting thing, triggered only when battery charge is > 80% and phone was not active for more than 73 minutes, but not more than once per day. now I was almost sure that dofstrim orphaned wakelock was left by that event processing.
instead of waiting for next event, I did more research and found that event can be fired anytime by shell command:
am idle-maintenance
voila! wakelock was there. knowing that idle maintenance running vold internal procedure for trim, I've checked daemon sources and found the following:
fstrim.c //
......
#define FSTRIM_WAKELOCK "dofstrim"
......
SLOGI("Finished fstrim work.\n");
release_wake_lock(FSTRIM_WAKELOCK);
......
acquire_wake_lock(PARTIAL_WAKE_LOCK, FSTRIM_WAKELOCK);
......
//
so wakelock was set before trim process but never released. logfile shown me following:
E/Vold (32356): failed to open /fstab.m7
E/Vold (32356): Error reading configuration (No such file or directory)... continuing anyways
......
I/fstrim (32356): Starting fstrim work...
...and then.. boom!
F/libc (31832): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 32353 (vold)
I/DEBUG ( 248): Build fingerprint: 'htc/sprint_wwe/m7wls:4.4.2/KOT49H/325784.5:user/release-keys'
I/DEBUG ( 248): AM write failure (32 / Broken pipe)
I/DEBUG ( 248): Write to AM fail, close AM fd
I/DEBUG ( 248): Revision: '4'
I/DEBUG ( 248): pid: 31832, tid: 32353, name: vold >>> /system/bin/vold <<<
I/DEBUG ( 248): debuggerd: checkTellHTCSettings
I/DEBUG ( 248): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
I/DEBUG ( 248): r0 2a01abd5 r1 fffffff0 r2 00000003 r3 00000000
I/DEBUG ( 248): r4 2a02017c r5 2a025290 r6 00000000 r7 b6b28d08
I/DEBUG ( 248): r8 00000000 r9 2a018bf6 sl b6c282d4 fp b6fac2f4
I/DEBUG ( 248): ip 00000003 sp b6b28ce8 lr b6fd1de1 pc 2a00f6ca cpsr 200b0030
so vold crashed but orphaned wakelock remained and prevents phone from sleeping ((
in theory problem caused by additional protected partition that exists on sprint model only but I had no time for vold recompiling so I've created a quite straightforward hex patch that simply removes trim process. so wakelock released and everyone's happy. just a note. vold will not run trim anymore so it must be done manually from shell by fstrim tool or from UI by LagFix app like once per week.
attached archive contains new (patched) and old (original) vold files that you have to upload to device using adb or any other method:
adb push vold /system/bin/vold
make sure you have fixed vold permissions from terminal like
chmod 755 /system/bin/vold
or you risk to stop on boot screen.
ps. this night my phone spent only 2% of battery for 7 hours. radio + wifi was on. so it was sleeping well ))
Verizon M7 solution?
I have the same issue with the dofstrim kernel wakelock preventing my phone from going into deep sleep after a charging cycle. Will your solution also work for the Verizon M7? I am rooted with the NuSenseSIX rom and ElementalX kernel.
aewald73 said:
I have the same issue with the dofstrim kernel wakelock preventing my phone from going into deep sleep after a charging cycle. Will your solution also work for the Verizon M7? I am rooted with the NuSenseSIX rom and ElementalX kernel.
Click to expand...
Click to collapse
I'd say probably not.. it's best not to flash zip files which are for different variants (they have different partition maps). Try posting here.
Any chance you can post sort of a noob guide on this fix? I'm a little confused with the steps you already posted, and then the additional steps needed for the weekly fix. Thanks.
fachadick said:
Any chance you can post sort of a noob guide on this fix? I'm a little confused with the steps you already posted, and then the additional steps needed for the weekly fix. Thanks.
Click to expand...
Click to collapse
While I cannot guarantee it will work for you, heres what I did:
1.) Extract the vold file from the .zip to the adb directory
2.) Have adb installed
3.) Do this:
Code:
adb devices
adb root
adb remount
adb push vold /system/bin/vold
adb shell
su
chmod 755 /system/bin/vold
CTRL-C
adb remount
Reboot and it should work.
Hello people.
I'm using a custom rom for my S Advance (CM11 Janice based). But since last month my phone is randomly rebooting when I use WCDMA (3G Network). The phone works ok when I use 2G only (GSM).
After searching a lot, I found other users with the same issue (including the same build of the rom). Apparently my carrier (TIM, Brazil) and Movistar (Argentina) changed recently something on their WCDMA network, it causes to phone overheat. The proccess "m.android.phone" consumes CPU and the
Code:
adb locat
throws this odd error:
Code:
[...]
E/DataBuffer( 2570): Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
D/AndroidRuntime( 2655): Shutting down VM
W/dalvikvm( 2655): threadid=1: thread exiting with uncaught exception (group=0x41856ce0)
E/WifiManager( 2774): Channel connection lost
E/StrictMode( 2570): RemoteException handling StrictMode violation
E/StrictMode( 2570): android.os.DeadObjectException
E/StrictMode( 2570): at android.os.BinderProxy.transact(Native Method)
E/StrictMode( 2570): at android.app.ActivityManagerProxy.handleApplicationStrictModeViolation(ActivityManagerNative.java:3770)
E/StrictMode( 2570): at android.os.StrictMode$5.run(StrictMode.java:1408)
[...]
I contacted the rom developer (great guy, btw), but he says he could not do anything, because it's a problem with the carrier. I contacted the carrier and they didn't help so much (bunch of generic questions, take to tech support, blablabla)
Someone had the same problem? I tried so many configurations, build.prop editing, secret menu, etc,etc.... Is kinda annoying use only 2G.
- adb logcat 01: http://pastebin.com/FHGipHvk
- adb logcat 02: http://pastebin.com/ZnsKXmwE
- adb logcat 03: http://pastebin.com/A7tFVAw6
Thanks!