1. Download our Official Android App: Forums for Android!

Root [ROM][ALPHA] CyanogenMod 10 for the LG Connect 4G MS840

Discussion in 'Android Devices' started by PlayfulGod, Mar 7, 2013.

  1. carolcityboyz

    carolcityboyz Well-Known Member
    Rank:
    None
    Points:
    63
    Posts:
    124
    Joined:
    Mar 6, 2012

    Mar 6, 2012
    124
    31
    63
    Male
    Miami Gardens, FL
    PG, can you help with this error?

    HTML:
    1. target thumb C++: libOmxVdec <= hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp
    2. In file included from hardware/qcom/media/mm-video/vidc/vdec/inc/h264_utils.h:46:0,
    3.                 from hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:48:
    4. bionic/libc/include/stdio.h: In function 'char* fgets(char*, int, FILE*)':
    5. bionic/libc/include/stdio.h:547:48: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    6. bionic/libc/include/stdio.h:553:47: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    7. In file included from hardware/qcom/media/mm-video/vidc/common/inc/extra_data_handler.h:37:0,
    8.                 from hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:49:
    9. device/lge/iproj/include/linux/msm_vidc_dec.h: At global scope:
    10. device/lge/iproj/include/linux/msm_vidc_dec.h:85:7: error: variable or field '__user' declared void
    11. device/lge/iproj/include/linux/msm_vidc_dec.h:85:7: error: expected ';' at end of member declaration
    12. device/lge/iproj/include/linux/msm_vidc_dec.h:85:15: error: ISO C++ forbids declaration of 'in' with no type [-fpermissive]
    13. device/lge/iproj/include/linux/msm_vidc_dec.h:86:7: error: variable or field '__user' declared void
    14. device/lge/iproj/include/linux/msm_vidc_dec.h:86:7: error: expected ';' at end of member declaration
    15. device/lge/iproj/include/linux/msm_vidc_dec.h:86:15: error: ISO C++ forbids declaration of 'out' with no type [-fpermissive]
    16. device/lge/iproj/include/linux/msm_vidc_dec.h:236:7: error: variable or field '__user' declared void
    17. device/lge/iproj/include/linux/msm_vidc_dec.h:236:7: error: expected ';' at end of member declaration
    18. device/lge/iproj/include/linux/msm_vidc_dec.h:236:15: error: ISO C++ forbids declaration of 'bufferaddr' with no type [-fpermissive]
    19. device/lge/iproj/include/linux/msm_vidc_dec.h:486:7: error: variable or field '__user' declared void
    20. device/lge/iproj/include/linux/msm_vidc_dec.h:486:7: error: expected ';' at end of member declaration
    21. device/lge/iproj/include/linux/msm_vidc_dec.h:486:15: error: ISO C++ forbids declaration of 'ptr_seqheader' with no type [-fpermissive]
    22. device/lge/iproj/include/linux/msm_vidc_dec.h:493:7: error: variable or field '__user' declared void
    23. device/lge/iproj/include/linux/msm_vidc_dec.h:493:7: error: expected ';' at end of member declaration
    24. device/lge/iproj/include/linux/msm_vidc_dec.h:493:15: error: ISO C++ forbids declaration of 'ptr_errormap' with no type [-fpermissive]
    25. device/lge/iproj/include/linux/msm_vidc_dec.h:498:7: error: variable or field '__user' declared void
    26. device/lge/iproj/include/linux/msm_vidc_dec.h:498:7: error: expected ';' at end of member declaration
    27. device/lge/iproj/include/linux/msm_vidc_dec.h:498:15: error: ISO C++ forbids declaration of 'bufferaddr' with no type [-fpermissive]
    28. device/lge/iproj/include/linux/msm_vidc_dec.h:506:7: error: variable or field '__user' declared void
    29. device/lge/iproj/include/linux/msm_vidc_dec.h:506:7: error: expected ';' at end of member declaration
    30. device/lge/iproj/include/linux/msm_vidc_dec.h:506:15: error: ISO C++ forbids declaration of 'desc_addr' with no type [-fpermissive]
    31. device/lge/iproj/include/linux/msm_vidc_dec.h:524:7: error: variable or field '__user' declared void
    32. device/lge/iproj/include/linux/msm_vidc_dec.h:524:7: error: expected ';' at end of member declaration
    33. device/lge/iproj/include/linux/msm_vidc_dec.h:524:15: error: ISO C++ forbids declaration of 'bufferaddr' with no type [-fpermissive]
    34. In file included from hardware/qcom/media/mm-video/vidc/common/inc/extra_data_handler.h:38:0,
    35.                 from hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:49:
    36. device/lge/iproj/include/linux/msm_vidc_enc.h:169:7: error: variable or field '__user' declared void
    37. device/lge/iproj/include/linux/msm_vidc_enc.h:169:7: error: expected ';' at end of member declaration
    38. device/lge/iproj/include/linux/msm_vidc_enc.h:169:15: error: ISO C++ forbids declaration of 'in' with no type [-fpermissive]
    39. device/lge/iproj/include/linux/msm_vidc_enc.h:170:7: error: variable or field '__user' declared void
    40. device/lge/iproj/include/linux/msm_vidc_enc.h:170:7: error: expected ';' at end of member declaration
    41. device/lge/iproj/include/linux/msm_vidc_enc.h:170:15: error: ISO C++ forbids declaration of 'out' with no type [-fpermissive]
    42. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'boolean H264_Utils::extract_rbsp(OMX_U8*, OMX_U32, OMX_U32, OMX_U8*, OMX_U32*, NALU*)':
    43. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:307:58: warning: suggest parentheses around assignment used as truth value [-Wparentheses]
    44. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::hrd_parameters(h264_hrd_param*)':
    45. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:763:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    46. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::sei_buffering_period()':
    47. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:854:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    48. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:871:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    49. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::sei_picture_timing()':
    50. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:923:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    51. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::sei_pan_scan()':
    52. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:998:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    53. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1012:7: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    54. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1017:41: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    55. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::print_pan_data(h264_pan_scan*)':
    56. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1044:3: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    57. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1049:39: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    58. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1051:5: warning: format '%d' expects argument of type 'int', but argument 4 has type 'OMX_S32 {aka long int}' [-Wformat]
    59. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1052:5: warning: format '%d' expects argument of type 'int', but argument 4 has type 'OMX_S32 {aka long int}' [-Wformat]
    60. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1053:5: warning: format '%d' expects argument of type 'int', but argument 4 has type 'OMX_S32 {aka long int}' [-Wformat]
    61. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1054:5: warning: format '%d' expects argument of type 'int', but argument 4 has type 'OMX_S32 {aka long int}' [-Wformat]
    62. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1056:3: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    63. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::parse_sps()':
    64. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1083:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    65. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1085:12: warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
    66. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1102:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    67. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::scaling_list(OMX_U32)':
    68. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1127:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    69. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::print_frame_pack()':
    70. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1331:3: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    71. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1332:3: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    72. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1336:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    73. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1338:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    74. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1340:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    75. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1342:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    76. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1344:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    77. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1346:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    78. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1348:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    79. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1350:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    80. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1352:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    81. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1354:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    82. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1356:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    83. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1358:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
    84. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'void h264_stream_parser::fill_pan_scan_data(OMX_QCOM_PANSCAN*, OMX_S64)':
    85. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1453:42: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    86. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1448:6: warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
    87. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp: In member function 'h264_pan_scan* panscan_handler::get_populated(OMX_S64)':
    88. hardware/qcom/media/mm-video/vidc/vdec/src/h264_utils.cpp:1605:6: warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
    89. make: *** [/home/kgraham/Source/out/target/product/ms840/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/h264_utils.o] Error 1
    90. make: *** Waiting for unfinished jobs....
    91.  
     

    Advertisement

  2. jlede

    jlede Android Expert
    Rank:
    None
    Points:
    78
    Posts:
    905
    Joined:
    Jul 11, 2012

    Jul 11, 2012
    905
    84
    78
    Male
    N/A
    Bardwell,Texas
    Good luck getting him to respond he just left us here to die
     
  3. kiroshi23

    kiroshi23 Android Enthusiast
    Rank:
    None
    Points:
    43
    Posts:
    352
    Joined:
    Oct 21, 2011

    Oct 21, 2011
    352
    31
    43
    Male
    student
    new york
    no hate man he worked on it out of his own time
     
  4. SegamanXero

    SegamanXero Well-Known Member
    Rank:
    None
    Points:
    38
    Posts:
    134
    Joined:
    Oct 10, 2011

    PG doesn't owe us anything... Infact no one here who have contributed to making roms, research into the Connect, finding root, or porting CWM/Superuser or whatever owes us anything... I am thankful for the work people have done for our phone, regardless if the work was fruitful in bringing us something or not.

    I do really want CyanogenMod Jelly bean mega bad for our phone. However, I am understanding that if it cant be done, or he/others do not have the time to work on it.

    I am very thankful for the work everyone has put in thus far with this though. Hopefully we can sort out the UICC card issues eventually...
     
    nOeTiK, schemppjr80 and djramod like this.
  5. Spec2nirvash

    VIP Member
    Rank:
     #73
    Points:
    233
    Posts:
    1,783
    Joined:
    Jul 19, 2011

    Jul 19, 2011
    1,783
    744
    233
    MA
    Agreed. PG gave us a 95% functioning CM10. He has done more than enough here. Perhaps somebody can tinker around with it and get 4G data going. I'd love to; but no service on my Connect = can't test data even if I could find a 4G fix anyway.

    Ya know, the 4G problem could be something as simple as a build.prop edit or a patch from XDA. If nobody tries this shit out we'll never know.

    The LG Motion forum got their CM10 damn near 100% operational because they were extremely determined to do so. Lots of them came together, experimented and tested all kinds of shit. Its a group effort guys.... Whenever y'all are ready for some serious brainstorming let me know and I'll help. I can't do all of this online research and testing by myself.
     
    nOeTiK likes this.
  6. kiroshi23

    kiroshi23 Android Enthusiast
    Rank:
    None
    Points:
    43
    Posts:
    352
    Joined:
    Oct 21, 2011

    Oct 21, 2011
    352
    31
    43
    Male
    student
    new york
    im up for testing im getting the moto x soon so i can mess with this phone all i want. it don't matter if it bricks
     
  7. droidlos

    droidlos Newbie
    Rank:
    None
    Points:
    26
    Posts:
    35
    Joined:
    Jul 29, 2012

    Jul 29, 2012
    35
    3
    26
    student .. ASE master mechanic
    Fort Worth, TX
    I have been testing this since march and have posted before (not in this great of detail) that in cm10 in one of the hidden menus there's an option that is checked that shouldnt be ( at least its unchecked zv8 - vv5) SIM LOCK and you need a PIN to "unlock" it i think this is the reason the SIM is not being read... Idk what the pin is ( if there is any ) or how to uncheck this box, b4 or after ROM (cm10) installation ... when i revert back to the stock rom it is unckecked and everything works as normal.. maybe one of y'all can get it unchecked to see if it is causing it not to read the sim.. ive run out o ideas
     
    SegamanXero likes this.
  8. trashbat

    trashbat Lurker
    Rank:
    None
    Points:
    5
    Posts:
    2
    Joined:
    Aug 12, 2013

    Aug 12, 2013
    2
    0
    5
    Hi,

    My mother-in-law brought an LG Connect over here to the UK to give to my wife, but I'm struggling to get it working for her. Although I considered myself fairly technically-minded, I've never installed a custom ROM or anything like that before, so this was all a bit of a learning experience to say the least!

    It was originally running the LG firmware that comes with the device (version MS840ZV9), but it seemed to be SIM-locked and so I ended up on this thread and decided to give CM10 a try (ignoring all the warnings about it being an alpha release ;)). I rooted the device, copied the first build from this thread (0317, yeah I should've checked for a later build) and Gapps onto the SD card, installed CWM from the Play Store (is there any reason not to install it this way?), rebooted holding Power and Volume Down, then did factory reset + clear cache + clear Dalvik cache before installing CM and Gapps.

    It all worked pretty well except it wasn't picking up any mobile network, so I went to bed. This evening I've revisited it and installed the most recent build I could find (0421) after factory reset + clear (Dalvik) cache, but I still get the same problem - it's not picking up any mobile network, so she can't use it to make or receive calls. The SIM I'm using is just a regular UK 3G SIM (Three network), which ought to work AFAIK, even though it's a 4G device?

    Any ideas? I can't access the mobile network settings, it immediately just says that com.android.phone has died, and this happens even without a SIM in it. I started out just trying to get around the fact that it was SIM-locked, so is there another ROM that's more likely to work for us?

    EDIT: I have been right through this thread before posting and seen people saying they get no signal, but then they usually say it's working for them a few posts later with a new build.
     
  9. droidlos

    droidlos Newbie
    Rank:
    None
    Points:
    26
    Posts:
    35
    Joined:
    Jul 29, 2012

    Jul 29, 2012
    35
    3
    26
    student .. ASE master mechanic
    Fort Worth, TX
    Hate to break this to you but that connect is a CDMA phone the Sim is only for the 4G service it more likely will not work at all over there
     
  10. droidlos

    droidlos Newbie
    Rank:
    None
    Points:
    26
    Posts:
    35
    Joined:
    Jul 29, 2012

    Jul 29, 2012
    35
    3
    26
    student .. ASE master mechanic
    Fort Worth, TX
    Plus the main problem with cm 10 is its not reading the sim at all
     
  11. Spec2nirvash

    VIP Member
    Rank:
     #73
    Points:
    233
    Posts:
    1,783
    Joined:
    Jul 19, 2011

    Jul 19, 2011
    1,783
    744
    233
    MA
    I thought of most, if not all cellular networks overseas to be GSM. Even if you can find a carrier over there like Orange, etc that runs on a CDMA network, I don't know how you could unlock that phone to make it work.

    Here in the US, when a CDMA carrier like Verizon markets a worldwide phone, its usually a dual-band CDMA phone like a Blackberry, that also accepts GSM SIM cards to work abroad....

    Sorry mate, I think you may have inherited a WiFi powered media player :(
     
  12. SegamanXero

    SegamanXero Well-Known Member
    Rank:
    None
    Points:
    38
    Posts:
    134
    Joined:
    Oct 10, 2011

    Yup the SIM card in the LG Connect is not a normal SIM card that you might see in GSM phones. The LG Connect is a CDMA phone that can do 2g/3g CDMA, and the card is actually a UICC card for use on MetroPCS's LTE network.

    A GSM simcard and a UICC card are two different things.
     
  13. trashbat

    trashbat Lurker
    Rank:
    None
    Points:
    5
    Posts:
    2
    Joined:
    Aug 12, 2013

    Aug 12, 2013
    2
    0
    5
    Cheers guys, well that definitely clears it up! Oh well, one more device for me to put Spotify on, then! ;-)
     
  14. zandersig

    zandersig Android Enthusiast
    Rank:
    None
    Points:
    88
    Posts:
    515
    Joined:
    Apr 6, 2012

    Apr 6, 2012
    515
    27
    88
    Male
    Prepress, graphic arts, macintosh
    Atlanta, GA, USA
    The only firmware that will work and pick up a signal is the vv5 version any other version and you will get the error com.android.phone has stopped working (or something like that) metro has made it that this phone will only work on vv5. That is why I paid Dan to figute out how to root vv5 so that we can all have superuser on vv5. The only rom that works right now is lg stock but ldrifta is working on getting version 2 rom running on vv5. Those are your only 2 choices. For cm10 to work on vv5 it will have to be rebuilt using vv5... ;(
     
  15. SegamanXero

    SegamanXero Well-Known Member
    Rank:
    None
    Points:
    38
    Posts:
    134
    Joined:
    Oct 10, 2011

    Not necessarily, from my understanding CM 10 doesn't use much if anything from stock ZVA, so there isnt much to rebuild in that respect I think. Maybe find what network settings have changed in VV5 from ZVA/ZVE and port them into CM 10 and we will be fine...

    Actually from my understanding we still have to get the UICC card recognized or something? Until that is done we are stuck at a brick wall we have been at for months with it...
     
  16. Spec2nirvash

    VIP Member
    Rank:
     #73
    Points:
    233
    Posts:
    1,783
    Joined:
    Jul 19, 2011

    Jul 19, 2011
    1,783
    744
    233
    MA
    One of the only couple 'o things used from ZVA were supposedly the APNs, which we can't access anyway. If you.manage to get APNs to open on CM10 it shows nothing. Use a third party app like APN manager and you will find +/- 80 different APN names? I did find 3 of the APNs that are required for our service in there; whether or not the phone can read them/apply as necessary is another can of caterpillars altogether, but may be an issue along with reading the UICC. That is, if "reading" the card is the actual problem here LOL
     
  17. Silverkx2000

    Silverkx2000 Well-Known Member
    Rank:
    None
    Points:
    43
    Posts:
    130
    Joined:
    Jan 21, 2011

    Jan 21, 2011
    130
    48
    43
    God
    At Home

    So while I can't help out with the error. I THINK i can tell you what it is.

    From my understanding its the video compression codec which would probably explain why capturing video doesn't work. So it wants the codec for this device to compress the video before it can even record it.

    We MIGHT be able to pull it off another ROM and inject it into the code but considering how freaking this version of CM10 is...very unlikely.

    Right now I think we're more worried about the 4G signal not working.

    I might try and give it another shot but I'm really bad at working on roms because im a noob
     
  18. Bigbj

    Bigbj Newbie
    Rank:
    None
    Points:
    16
    Posts:
    41
    Joined:
    May 2, 2012

    May 2, 2012
    41
    2
    16
    Back on the 4g thing. If the uicc card is only used for 4g data then why won't 2g/3g work since we can't read the card? The problem has to go deeper than just not readings the card.
    I was looking a round a little bit and if you check system/etc/apns.xml in vv5 and in cm10, they are way different. The vv5 one shows nothing but some empty code (apparently apns are stored elsewhere, whereas cm10 shows tons of networks). Both of them also day that that file must match one in a different directory, but I can't find the directory it specifies. Any ideas?
     
  19. Spec2nirvash

    VIP Member
    Rank:
     #73
    Points:
    233
    Posts:
    1,783
    Joined:
    Jul 19, 2011

    Jul 19, 2011
    1,783
    744
    233
    MA
    2G/3G does work... For some people and not others. I'm not one of the lucky ones, I get no data on mine, only voice/SMS.
     
  20. jlede

    jlede Android Expert
    Rank:
    None
    Points:
    78
    Posts:
    905
    Joined:
    Jul 11, 2012

    Jul 11, 2012
    905
    84
    78
    Male
    N/A
    Bardwell,Texas
    Guys i tried flashing the lucid cm 10 to what will happen but i keep getting status 7 i forgot what i needed to delete. a line of code in the scrpit to get past that if anyone whats to try and flash that hmmm does anyone have an idea if not back to google

    Edit:Reason full of errors and mistypes
     
  21. Bigbj

    Bigbj Newbie
    Rank:
    None
    Points:
    16
    Posts:
    41
    Joined:
    May 2, 2012

    May 2, 2012
    41
    2
    16
    Oh alright. What about the apns.xml file?
     
  22. Spec2nirvash

    VIP Member
    Rank:
     #73
    Points:
    233
    Posts:
    1,783
    Joined:
    Jul 19, 2011

    Jul 19, 2011
    1,783
    744
    233
    MA
    It's in the ROM, and the proper MetroPCS APNs were in it. I just don't know if the phone is using them... If you manage to get APNs to open in the Android system, it doesn't show any APNs whatsoever. Nothing to select, no tic boxes to select, nothing to highlight and edit.

    EDIT:

    The MetroPCS APN properties have changed slightly since the merge, so they need to be updated anyway. You could make a copy of your current apns-conf.XML and maybe paste into CM10. I would like to find a way to actually view/enable APNs with Android system first.... I think pasting a new apns-conf.xml won't do anything if you can't even open them up in system.

    Sucks... I got all kinds of motivation to work on this now, but unfortunately my Connect has no active service. Can't fix a data problem on a phone that is deactivated :D
     
  23. rannz7

    rannz7 Lurker
    Rank:
    None
    Points:
    5
    Posts:
    7
    Joined:
    Feb 20, 2013

    Feb 20, 2013
    7
    0
    5
    Male
    DJ
    Florida
    I have this rom on my phone but was thinking I was crazy testing the data on this and surprisingly loads youtube and playstore on service using 1x but with the speed of 3G. You think it might be my phone or you guys are getting this rom better?
     
  24. Spec2nirvash

    VIP Member
    Rank:
     #73
    Points:
    233
    Posts:
    1,783
    Joined:
    Jul 19, 2011

    Jul 19, 2011
    1,783
    744
    233
    MA
    Nobody has touched it in a while. As I mentioned in a previous comment, some people who flash CM10 get data working and for some the data will not work at all. I think whoever lives in an area that has 3G coverage will find that it works for them. I'm in MA, and in my typical range of travel I get either 1x or 4G coverage with my phones; we don't have the 3G option here LOL. That makes having a 4G phone here necessary; a non-LTE android with 1x only in my area is sooooo......slow..... making it pretty damn near useless :)

    But yes, if you are seeing a 1x, it is in fact 3G. You're one of the lucky ones. If I had 3G coverage here I would have definitely used CM10 as a daily :(
     
  25. Spec2nirvash

    VIP Member
    Rank:
     #73
    Points:
    233
    Posts:
    1,783
    Joined:
    Jul 19, 2011

    Jul 19, 2011
    1,783
    744
    233
    MA
    Lol are you trying to brick that phone?? :D

    You know what? I remember a ways back, that Un1ocked somehow flashed the Verizon Lucid ICS firmware to his Connect and it actually booted up :eek: I think it also came with some major headaches trying to get that firmware off of the phone afterwards..... I myself had thought of trying that at one point.
     

Share This Page

Loading...