• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[DEV][ROM][8.1.] CyanogenMod 10 (Android 4.1.2)

3135 posts in this topic

Posted

OMG! Cannot believe that CM10 is coming to our blades. Thanks tilal, KonstaT, sej and all the other developers for their great work. This is amazing!

lol, 99% konstat and tilal, my contribution is a bit of documentation, the odd patch and an idea or two lol (and bitching about whitespace on gerrit!)

whats reassuring is that we've had no official support for cm10 and yet its still coming along anyway (we kinda partially had support for cm9) which seems to be the way for cyanogenmod at the moment, the cm9 supported devices were half that of cm7 (its only aosp/non-armv6 devices now in cm10) yet they're still plugging away.

1

Share this post


Link to post
Share on other sites

Posted

I don't see myself compiling a lot of CM9 in the near future :P JellyBean really appeals me.

I mean I wasn't too eager to try ICS when it came out, but this time - the whole "project butter awesome responsiveness" thing is something I really wanna put my hands on.

and with this promising start - there's no telling where we'll land.. a lot of great work being done by Konstat, tilal and sej.

also I'm happy to see Tom's involvement at gerrit in the jellybean branch.

1

Share this post


Link to post
Share on other sites

Posted (edited)

The file in bionic that breaks the build has been take care of, actually some minor typo mistakes.

bionic_atomic_arm.txt (rename .txt to .h)

Edited by burstlam
4

Share this post


Link to post
Share on other sites

Posted

Seems like Tilal has sorted the Signal issue (RIL) :)

1

Share this post


Link to post
Share on other sites

Posted

好牛啊,支持你,希望继续更新啊,大婶

0

Share this post


Link to post
Share on other sites

Posted

Does everybody's phone app constantly crash until PIN is entered? Or is it just mine because my operator is roaming on another network. It's this line where it fails. Index out of bound error on getting MCC value (operator country code).

The same thing happened to me. Phone app constantly crashing until PIN is entered, it even made the phone force reboot once.

You said on the OP that audio playback is partially working, what exactly is working and what isn't?

So far I haven't gotten any sound to work except when I'm talking to someone, it's not a big deal only annoying because I have somehow broken my vibrator and with no sound I can't hear texts or calls hehe.

If I encounter any problems when developing apps I can post logs if you want, I don't know if it even can help you fix errors as I don't know anything about making ROMs.

1

Share this post


Link to post
Share on other sites

Posted

can anyone let me know how to make mobile network to work step by step via terminal emulator....

sound is working perfect with jetaudio app... even phone app doesnt crashes here...... just need mobile network to receive messages .....

thanks in advance....

0

Share this post


Link to post
Share on other sites

Posted

can anyone let me know how to make mobile network to work step by step via terminal emulator....

sound is working perfect with jetaudio app... even phone app doesnt crashes here...... just need mobile network to receive messages .....

thanks in advance....

To get the Mobile network working:

you need superuser access to use terminal properly and

then go into Terminal and type:

su

chmod 777 /data/radio/* && chown radio.radio /data/radio/*

and then you'll be faced with the pin unlock screen where you enter it and then press home, it a bit dodgy and you may need to play around with it. i got mine working in the end though :)

2

Share this post


Link to post
Share on other sites

Posted

still trying ..... after i enter su.... i am root permission..... but after i enter the above command..... it comes back to start of terminal mode..... could u pls play once again after booting your rom..... so tat i could try......

0

Share this post


Link to post
Share on other sites

Posted

still trying ..... after i enter su.... i am root permission..... but after i enter the above command..... it comes back to start of terminal mode..... could u pls play once again after booting your rom..... so tat i could try......

Im not to sure why yours is doing this, once you enter the command it should take you to the PIN screen, i have switched back to CM9 now as it was too laggy, what type of blade do you have? try re-flashing the rom if all else fails using cfx flash instructions.

1

Share this post


Link to post
Share on other sites

Posted

After up ROM 4.1.1. Can I return CM7?

0

Share this post


Link to post
Share on other sites

Posted

European blade..... anyway..... developers will solve this issue in future with upcoming rom........ thanks for ur info bro....

0

Share this post


Link to post
Share on other sites

Posted

European blade..... anyway..... developers will solve this issue in future with upcoming rom........ thanks for ur info bro....

Yeah in tilal release for the skate he has solved this problem, hopefully soon it will get merged into ours :)

1

Share this post


Link to post
Share on other sites

Posted

After up ROM 4.1.1. Can I return CM7?

Use nandroid backup to return back to cm7 dude......

1

Share this post


Link to post
Share on other sites

Posted

Im not to sure why yours is doing this, once you enter the command it should take you to the PIN screen, i have switched back to CM9 now as it was too laggy, what type of blade do you have? try re-flashing the rom if all else fails using cfx flash instructions.

Even I couldn't get it to work! Tried a lot!

1

Share this post


Link to post
Share on other sites

Posted (edited)

Even I couldn't get it to work! Tried a lot!

Mine seemed to work fine, after entering the code into terminal i would be taken to the PIN screen where i would get a message saying some process is failed and once i entered my PIN and then pressed the home button my signal bars at the top went blue and i received my voicemail notification and text messages :)

This method is pointless to master anyway as you have to redo it on every boot. you may aswell wait for an update from Konstat.

Edited by Hayden3430
1

Share this post


Link to post
Share on other sites

Posted

Mine seemed to work fine, after entering the code into terminal i would be taken to the PIN screen where i would get a message saying some process is failed and once i entered my PIN and then pressed the home button my signal bars at the top went blue and i received my voicemail notification and text messages :)

This method is pointless to master anyway as you have to redo it on every boot. you may aswell wait for an update from Konstat.

yup. Im gonna wait! Im on cm9 now!

1

Share this post


Link to post
Share on other sites

Posted

Yeah in tilal release for the skate he has solved this problem, hopefully soon it will get merged into ours :)

Well, the problem itself hasn't been solved yet. It's just a hacky workaround that cures the symptoms but not the disease. ;) And you'll still have the issue with phone force-closing. I'm not going to push it to my github but I'll do separate flashable boot.img that will have this 'fix'.

Real problem is the rild crashing -> phone crashing on every boot. Here is a clean log that happens right before lockscreen is initially displayed. That's when rild should be initialized. That doesn't tell me much other than that the problem is somewhere in the native code side.


I/DEBUG ( 111): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 111): Build fingerprint: 'ZTE/P772A10D/atlas40:4.0.4/IMM76D/20120608.113547:user/release-keys'
I/DEBUG ( 111): pid: 112, tid: 112, name: rild >>> /system/bin/rild <<<
I/DEBUG ( 111): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 111): r0 00000027 r1 400428e9 r2 400428e9 r3 deadbaad
I/DEBUG ( 111): r4 00000000 r5 4047d3a4 r6 40479581 r7 00000000
I/DEBUG ( 111): r8 00000000 r9 00000000 sl 00000000 fp 00000000
I/DEBUG ( 111): ip 4047c6a0 sp beda1728 lr 400439a5 pc 40040062 cpsr 40000030
I/DEBUG ( 111): d0 0000000000000000 d1 0000000000000000
I/DEBUG ( 111): d2 0000000000000000 d3 0000000000000000
I/DEBUG ( 111): d4 0000000000000000 d5 0000000000000000
I/DEBUG ( 111): d6 0000000000000000 d7 0000000000000000
I/DEBUG ( 111): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 111): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 111): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 111): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 111): scr 00000000
I/DEBUG ( 111):
I/DEBUG ( 111): backtrace:
I/DEBUG ( 111): #00 pc 00019062 /system/lib/libc.so
I/DEBUG ( 111): #01 pc 0000dc64 /system/lib/libc.so (abort+4)
I/DEBUG ( 111): #02 pc 0000fc03 /system/lib/libdss.so (dsc_abort+2)
I/DEBUG ( 111): #03 pc 0000db35 /system/lib/libdss.so
I/DEBUG ( 111): #04 pc 0000dd35 /system/lib/libdss.so (dsc_qmi_init+108)
I/DEBUG ( 111): #05 pc 0000c68d /system/lib/libdss.so (dsc_main+256)
I/DEBUG ( 111): #06 pc 000a751f /system/lib/libril-qc-1.so (dsi_init+170)
I/DEBUG ( 111): #07 pc 0009bce9 /system/lib/libril-qc-1.so (qcril_data_init+80)
I/DEBUG ( 111): #08 pc 00025249 /system/lib/libril-qc-1.so (qcril_init+280)
I/DEBUG ( 111): #09 pc 00025905 /system/lib/libril-qc-1.so (RIL_Init+544)
I/DEBUG ( 111): #10 pc 00000e67 /system/bin/rild
I/DEBUG ( 111):
I/DEBUG ( 111): stack:
I/DEBUG ( 111): beda16e8 ffff0208
I/DEBUG ( 111): beda16ec beda1794 [stack]
I/DEBUG ( 111): beda16f0 4006b798 /system/lib/libc.so
I/DEBUG ( 111): beda16f4 4006b6f8 /system/lib/libc.so
I/DEBUG ( 111): beda16f8 00000000
I/DEBUG ( 111): beda16fc 400439a5 /system/lib/libc.so (_fwalk+32)
I/DEBUG ( 111): beda1700 400428e9 /system/lib/libc.so (__sflush)
I/DEBUG ( 111): beda1704 400428e9 /system/lib/libc.so (__sflush)
I/DEBUG ( 111): beda1708 40042c21 /system/lib/libc.so (_cleanup)
I/DEBUG ( 111): beda170c 40140000
I/DEBUG ( 111): beda1710 4047d3a4
I/DEBUG ( 111): beda1714 40479581 /system/lib/libdss.so
I/DEBUG ( 111): beda1718 00000000
I/DEBUG ( 111): beda171c 40042c2d /system/lib/libc.so (_cleanup+12)
I/DEBUG ( 111): beda1720 df0027ad
I/DEBUG ( 111): beda1724 00000000
I/DEBUG ( 111): #00 beda1728 beda1790 [stack]
I/DEBUG ( 111): beda172c fffffbdf
I/DEBUG ( 111): beda1730 4047c614 /system/lib/libdss.so
I/DEBUG ( 111): beda1734 4047c614 /system/lib/libdss.so
I/DEBUG ( 111): beda1738 4047d3a4
I/DEBUG ( 111): beda173c 40479581 /system/lib/libdss.so
I/DEBUG ( 111): beda1740 4047c614 /system/lib/libdss.so
I/DEBUG ( 111): beda1744 40034c68 /system/lib/libc.so (__pthread_clone)
I/DEBUG ( 111): #01 beda1748 40473b35 /system/lib/libdss.so
I/DEBUG ( 111): beda174c 40475c07 /system/lib/libdss.so
I/DEBUG ( 111): #02 beda1750 4047c614 /system/lib/libdss.so
I/DEBUG ( 111): beda1754 40473b39 /system/lib/libdss.so
I/DEBUG ( 111):
I/DEBUG ( 111): memory near r1:
I/DEBUG ( 111): 400428c8 0ff6068e d0022800 f0001c20 1c30fa9e .....(.. .....0.
I/DEBUG ( 111): 400428d8 46c0bd70 00028bce 06488981 47700fc0 p..F......H...pG
I/DEBUG ( 111): 400428e8 210cb570 1c045e42 40102008 6925d01e p..!B^... .@..%i
I/DEBUG ( 111): 400428f8 d01b1e28 23006826 60251b76 d1000791 (...&h.#v.%`....
I/DEBUG ( 111): 40042908 60a36963 69e0e00f 1c296ae3 47981c32 ci.`...i.j).2..G
I/DEBUG ( 111):
I/DEBUG ( 111): memory near r2:
I/DEBUG ( 111): 400428c8 0ff6068e d0022800 f0001c20 1c30fa9e .....(.. .....0.
I/DEBUG ( 111): 400428d8 46c0bd70 00028bce 06488981 47700fc0 p..F......H...pG
I/DEBUG ( 111): 400428e8 210cb570 1c045e42 40102008 6925d01e p..!B^... .@..%i
I/DEBUG ( 111): 400428f8 d01b1e28 23006826 60251b76 d1000791 (...&h.#v.%`....
I/DEBUG ( 111): 40042908 60a36963 69e0e00f 1c296ae3 47981c32 ci.`...i.j).2..G
I/DEBUG ( 111):
I/DEBUG ( 111): memory near r5:
I/DEBUG ( 111): 4047d384 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 111): 4047d394 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 111): 4047d3a4 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 111): 4047d3b4 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 111): 4047d3c4 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 111):
I/DEBUG ( 111): memory near r6:
I/DEBUG ( 111): 40479560 6e697361 68742067 6d712065 6c635f69 asing the qmi_cl
I/DEBUG ( 111): 40479570 746e6569 6e61685f 20656c64 0a206425 ient_handle %d .
I/DEBUG ( 111): 40479580 6e6d7200 00307465 656e6d72 72003174 .rmnet0.rmnet1.r
I/DEBUG ( 111): 40479590 74656e6d 00000032 5f637364 63697270 mnet2...dsc_pric
I/DEBUG ( 111): 404795a0 5f6c6c61 6f636572 6769666e 7165725f all_reconfig_req
I/DEBUG ( 111):
I/DEBUG ( 111): memory near ip:
I/DEBUG ( 111): 4047c680 40034720 40451f15 4012f9b5 40034600 G.@..E@...@.F.@
I/DEBUG ( 111): 4047c690 40033d24 40450fc5 4004a7a5 40041dd5 $=.@..E@...@...@
I/DEBUG ( 111): 4047c6a0 40034c60 4003ee35 40457415 40033ccc `L.@5..@.tE@.<.@
I/DEBUG ( 111): 4047c6b0 40034698 40456d39 400339ec 40042ea1 .F.@9mE@.9.@...@
I/DEBUG ( 111): 4047c6c0 40457479 4003463c 40035b14 40033fd8 ytE@<F.@.[.@.?.@
I/DEBUG ( 111):
I/DEBUG ( 111): memory near sp:
I/DEBUG ( 111): beda1708 40042c21 40140000 4047d3a4 40479581 !,.@...@..G@..G@
I/DEBUG ( 111): beda1718 00000000 40042c2d df0027ad 00000000 ....-,.@.'......
I/DEBUG ( 111): beda1728 beda1790 fffffbdf 4047c614 4047c614 ..........G@..G@
I/DEBUG ( 111): beda1738 4047d3a4 40479581 4047c614 40034c68 ..G@..G@..G@hL.@
I/DEBUG ( 111): beda1748 40473b35 40475c07 4047c614 40473b39 5;G@.\G@..G@9;G@
I/DEBUG ( 111):
I/DEBUG ( 111): code around pc:
I/DEBUG ( 111): 40040040 1c1ce000 2b006823 e027d1fb 2a0068e2 ....#h.+..'..h.*
I/DEBUG ( 111): 40040050 4b17d004 447b2001 47906018 20274b15 ...K. {D.`.G.K'
I/DEBUG ( 111): 40040060 70182400 ed40f7f3 f7f42106 2280ee70 .$.p..@..!..p.."
I/DEBUG ( 111): 40040070 91040551 1c0aa902 94022006 f7f49403 Q........ ......
I/DEBUG ( 111): 40040080 a901ea5e 20021c22 ea66f7f4 ed2cf7f3 ^...".. ..f...,.
I/DEBUG ( 111):
I/DEBUG ( 111): code around lr:
I/DEBUG ( 111): 40043984 4c0cb5f7 447c2600 68249001 686768a5 ...L.&|D..$h.hgh
I/DEBUG ( 111): 40043994 220ce008 2b005eab 1c28dd03 47889901 ...".^.+..(....G
I/DEBUG ( 111): 400439a4 35544306 d5f43f01 2c006824 1c30d1ee .CT5.?..$h.,..0.
I/DEBUG ( 111): 400439b4 46c0bdfe 00027b56 4f16b5f0 447f1c16 ...FV{.....O...D
I/DEBUG ( 111): 400439c4 683f1c0d 4375b089 683b1c1c 9003aa03 ..?h..uC..;h....
I/DEBUG ( 111):
I/DEBUG ( 111): memory map around fault addr deadbaad:
I/DEBUG ( 111): bed82000-beda3000 [stack]
I/DEBUG ( 111): (no map for address)
I/DEBUG ( 111): (no map above)
D/dalvikvm( 304): GC_EXPLICIT freed 89K, 20% free 11984K/14855K, paused 6ms+28ms, total 229ms
I/BootReceiver( 304): Copying /data/tombstones/tombstone_05 to DropBox (SYSTEM_TOMBSTONE)
D/dalvikvm( 434): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 434): GC_EXPLICIT freed 767K, 37% free 8487K/13315K, paused 4ms+12ms, total 78ms
D/dalvikvm( 304): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 304): GC_EXPLICIT freed 620K, 20% free 11985K/14855K, paused 7ms+10ms, total 125ms
D/dalvikvm( 304): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 304): GC_EXPLICIT freed 90K, 20% free 11984K/14855K, paused 6ms+10ms, total 123ms
D/dalvikvm( 434): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 434): GC_EXPLICIT freed 750K, 37% free 8487K/13315K, paused 5ms+12ms, total 101ms
D/dalvikvm( 304): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 304): GC_EXPLICIT freed 89K, 20% free 11984K/14855K, paused 6ms+10ms, total 123ms
D/dalvikvm( 304): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 304): GC_EXPLICIT freed 89K, 20% free 11984K/14855K, paused 7ms+11ms, total 125ms
D/dalvikvm( 434): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 434): GC_EXPLICIT freed 738K, 37% free 8488K/13315K, paused 5ms+12ms, total 74ms
I/ActivityManager( 304): Start proc com.google.android.partnersetup for broadcast com.google.android.partnersetup/.PhoneStateReceiver: pid=1064 uid=10040 gids={3003, 1028}
D/AndroidRuntime( 486): Shutting down VM
W/dalvikvm( 486): threadid=1: thread exiting with uncaught exception (group=0x40a9a300)
E/AndroidRuntime( 486): FATAL EXCEPTION: main
E/AndroidRuntime( 486): java.lang.StringIndexOutOfBoundsException: length=0; regionStart=0; regionLength=3
E/AndroidRuntime( 486): at java.lang.String.startEndAndLength(String.java:593)
E/AndroidRuntime( 486): at java.lang.String.substring(String.java:1474)
E/AndroidRuntime( 486): at com.android.internal.telephony.gsm.GsmServiceStateTracker.pollStateDone(GsmServiceStateTracker.java:867)
E/AndroidRuntime( 486): at com.android.internal.telephony.gsm.GsmServiceStateTracker.handlePollStateResult(GsmServiceStateTracker.java:681)
E/AndroidRuntime( 486): at com.android.internal.telephony.gsm.GsmServiceStateTracker.handleMessage(GsmServiceStateTracker.java:369)
E/AndroidRuntime( 486): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 486): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 486): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 486): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 486): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 486): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 486): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 486): at dalvik.system.NativeStart.main(Native Method)
V/LockPatternKeyguardView( 304): Set visibility on com.android.internal.policy.impl.LockPatternKeyguardView$4@4170f5d0 to 8388608
[/CODE]

1

Share this post


Link to post
Share on other sites

Posted

There are some new patches uploaded to the gerrit. I tested this one for bionic last night. It doesn't seem to boot on my device, so reverted back to my old hack and it was good again. I do admit that I didn't do a clean build so it also might have been because of that. It seems to be getting +1's so might have to try it again before trashing it. :P

Another one for srec that I haven't tested yet. Those two should get us to a point where no extra patches is needed to compile.

Copying media_codecs.xml from Lalit's git to /system/etc/ seems to sort quite a lot of the audio playback issues. First batch of CM features was also merged so I'll probably share a new build later today.

2

Share this post


Link to post
Share on other sites

Posted

Dazzozo did an strace on rild to see why it crashed and found that it was timing out when waiting for permissions for the /data/radio/ socket.

3

Share this post


Link to post
Share on other sites

Posted

Dazzozo did an strace on rild to see why it crashed and found that it was timing out when waiting for permissions for the /data/radio/ socket.

Ok, good to know. I'm still not perfectly happy with the current solution. ;)

Edit. Woohoo - 1000. :D

4

Share this post


Link to post
Share on other sites

Posted

@KonstaT:

Managed to fix the /data/radio or rild crash without the hack. See my github for the fix - will push it very soon.

6

Share this post


Link to post
Share on other sites

Posted

@KonstaT:

Managed to fix the /data/radio or rild crash without the hack. See my github for the fix - will push it very soon.

Damn you Lalit, I just uploaded my today's build. :D Can't be bothered to upload it again just because of one line.

I'll make it available as separate zip. We still have an issue with the phone crashing/soft rebooting until PIN is entered anyway.

2

Share this post


Link to post
Share on other sites

Posted

Yeah - could you post a logcat of that issue please? I have this feeling that the same think happened in early ICS.

2

Share this post


Link to post
Share on other sites

Posted

Yeah - could you post a logcat of that issue please? I have this feeling that the same think happened in early ICS.

It's this line where it fails. StringIndexOutOfBoundsException on getting MCC value (operator country code). Log is actually the same as couple of posts up.


E/AndroidRuntime( 486): FATAL EXCEPTION: main
E/AndroidRuntime( 486): java.lang.StringIndexOutOfBoundsException: length=0; regionStart=0; regionLength=3
E/AndroidRuntime( 486): at java.lang.String.startEndAndLength(String.java:593)
E/AndroidRuntime( 486): at java.lang.String.substring(String.java:1474)
E/AndroidRuntime( 486): at com.android.internal.telephony.gsm.GsmServiceStateTracker.pollStateDone(GsmServiceStateTracker.java:867)
E/AndroidRuntime( 486): at com.android.internal.telephony.gsm.GsmServiceStateTracker.handlePollStateResult(GsmServiceStateTracker.java:681)
E/AndroidRuntime( 486): at com.android.internal.telephony.gsm.GsmServiceStateTracker.handleMessage(GsmServiceStateTracker.java:369)
E/AndroidRuntime( 486): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 486): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 486): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 486): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 486): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 486): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 486): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 486): at dalvik.system.NativeStart.main(Native Method)
[/CODE]

1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.