[ROM] CTMod 3.80 (04/07/13)


Last Updated: 2014-06-26 18:04:24
  1. gkak

    gkak Well-Known Member

    --------- beginning of /dev/log/system
    --------- beginning of /dev/log/main
    E/CAM_FD (20493): Inside s5k5ccgx_process_start
    E/CAM_FD (20493): s5k5ccgx_video_config, sfd = 21
    E/CAM_FD (20493): Entered s5k5ccgx_set_wb, ctrl->sfd = 21, op_mode = 3
    E/CAM_FD (20493): Setting wb to 0
    E/QualcommCameraHardware(20493): Maximum zoom value is
    E/QualcommCameraHardware(20493): [ASWOOGI] setRotation end
    E/QualcommCameraHardware(20493): setZoom: 0
    E/QualcommCameraHardware(20493): mDatalineChk : 0, new datalinechk value : 0
    E/QualcommCameraHardware(20493): <=PCAM=> current Vtmode : 0
    E/QualcommCameraHardware(20493): setPreviewFrameRate
    E/CAM_FD (20493): Entered s5k5ccgx_set_flash, ctrl->sfd = 21, op_mode = 0
    E/CAM_FD (20493): Setting flash to 0
    E/QualcommCameraHardware(20493): [ASWOOGI] setFocusMode value: 2, mFocusMode: 2
    E/CameraService(20493): getOrientation=0, 0
    E/CAM_FD (20493): config_proc_CAMERA_STOP_SNAPSHOT: ctrl->state = 0
    E/CAM_FD (20493): cam_conf: CAMERA_EXIT
    E/MediaPlayer(20493): message received msg=5, ext1=0, ext2=0
    E/MediaPlayer(20493): message received msg=1, ext1=0, ext2=0
    E/MediaPlayer(20493): message received msg=5, ext1=0, ext2=0
    E/MediaPlayer(20493): message received msg=1, ext1=0, ext2=0
    E/LockPatternKeyguardView(20503): 5. updateScreen
    E/PowerManagerService(20503): CurLock p:2 mPS:7
    E/LockPatternKeyguardView(20503): 6. updateScreen
    E/PowerManagerService(20503): CurLock p:3 mPS:7
    E/PowerManagerService(20503): CurLock p:2 mPS:7
    E/lights (20503): ***** Charging : RED Solid *****
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 18 mWorkingMessage.isWorthSaving() = false mSentMessage = false
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): onDataSetChanged
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 19 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 19 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 19 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 19 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/LockPatternKeyguardView(20503): 5. updateScreen
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 19 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 19 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 19 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/AbstractCompatWrapper(20577): Invalid input to AbstructCompatWrapper
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 20 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 20 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 20 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 20 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/LockPatternKeyguardView(20503): 5. updateScreen
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 20 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 20 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/SmsReceiverService(21262): handleSmsReceived: CMAS = FALSE
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 21 mWorkingMessage.isWorthSaving() = false mSentMessage = true
    E/Mms/compose(21262): isRecipientsEditorVisible() = false isRecipientsEditorVisible() = false mdeleting = false
    E/Mms/compose(21262): startMsgListQuery conversationUri = content://mms-sms/conversations/7
    E/Mms/compose(21262): onDataSetChanged
    E/Mms/compose(21262): cursor.getCount() = 21 mWork

    Advertisement
  2. gkak

    gkak Well-Known Member

    sorry for all that above. I noticed I get reboots when sending a text message and/or hitting the hardware power button. so I sent myself a bunch of texts and hit the power button in between
  3. ruinevil

    ruinevil Member

    So I am using it on a Sprint FG11, and it works pretty nicely so far. Just one crash of the launcher when I was in Settings.

    Anyway, what kind of adblock do you use. I need to go around it for a program.

    EDIT: Nevermind, just used adfree.
  4. cjoeone

    cjoeone Well-Known Member

    I love this rom. Is there a way for me to use your control panel on a different rom. I am trying to experiment with other roms. Thank you for this wonderful work.
  5. Mako 230

    Mako 230 Well-Known Member

    ""
    That wouldn't happen to be a HTC Evo design 4g by chance would it? I bought one off Cl (this time checking the esn before paying the seller). I'd love to see a ct mod for that!
  6. Bloodawn

    Bloodawn Well-Known Member

    no

    nah, the Marquee is my main phone and MIUI V4 is the rom i was talking about. the Evo really isn't much of a upgrade for me.
  7. Bloodawn

    Bloodawn Well-Known Member

    ok, the logcats really don't say anything useful and I haven't been able to reproduce a single problem with the camera, launcher, messenger or chrome and I just opened/closed the camera like 30 times, switching between the icon and the button.

    are you guys overclocking or restoring anything at all from another rom? setting the clock higher then your phone can handle will make it reboot, and restoring things from other roms will break the rom.

    try just flashing CT 3.69 (make sure its 69 and not 68), after its finished boot up, don't touch voltage control or install anything. now try what you were having problems with before and see if it still does it.
  8. gkak

    gkak Well-Known Member

    I'm OC'ed only up to 1.2 Mhz, used TB to restore some user apps (not system apps). When I get a few minutes I'll follow ur recommendations and grab another logcat if needed
  9. fatnickd1

    fatnickd1 Active Member

    That"s prol it. My phone was doing the same thing when I hit power during anything. I did restore things and mess with voltage. It started glitching. Is that term still in use? lol. Anyway, wiped everything and took on 3.69 it fixed it, until after I made it the configuration it was (app WIse) with TI. That caused more of the same random (seamingly) reboots. Wiped some cache that helps.
    So how are we supposed to get phones back to the way we like them (I like Go Launcher) without messing up everything, or sitting at the Play Store for twenty minuets, then setting all those apps over again?
    Nvr want to seem unappreciative, I very much am. Have donated in the past and hope to be able to in the future. Great work Everyone. Glad you have the same phone has me now Blood Dawn. Hope the keep learning more. Down with The Apple losers. Those big cry babies.
  10. Bloodawn

    Bloodawn Well-Known Member

    theres a reason I have the rom installation wipe out everything and thats to stop problems from happening.

    think of installing a new rom as installing a operating system on a computer, you don't try copying Program Files from Windows XP to Windows 7 and expect everything to work. so why try doing it with android?

    if you don't want problems just install the rom, turn on wifi, do fresh installs of all your apps from the market and you should be good. if a new version of CT comes out you can probably backup some stuff and restore it after updating without issues but doing it when switching to completely different roms isn't going to work out.
  11. Paradoxx

    Paradoxx Well-Known Member

    Titanium backup will cause problems if you used it and are having problems dont come here complaining
  12. Zintus

    Zintus Well-Known Member

    Blood so are you telling me that i shouldnt do an advanced restore in cwm to get my data back that was backed up on a stock rom??? Maybe that was what broke my rom and makes it reboot... its doing it during text messaging single vibe then three which denotes a force close correct??? Then reboots... im usung holo launcher as my system launcher....
  13. Bloodawn

    Bloodawn Well-Known Member

    yes, thats what broke everything.

    don't use backups that weren't made while on CT.
    Zintus likes this.
  14. gkak

    gkak Well-Known Member

    sorry for the noob question but I can't seem to find a good explanation. I understand how restoring a system app across roms with TB might be an issue given the symbiotic relationship of system apps and roms but how does restoring a random user app across roms mess up a rom, how is restoring different then getting from the market?
    I'd hate to have to redownload 9 Innings mid season, but if it means stability for this great rom ...
  15. xaelith

    xaelith Well-Known Member

    My best guess is this: when you download and install an app from the market or other sources, there's a bit of "handshaking" going on to let the system know what apps are there, or for the app itself to know what system resources are available. When you restore an app, it's already gone through the process, and carries over the info from whatever ROM was there previously, and freaks out when the handshake info doesn't match.

    Put it another way, let's say I'm an app. If I'm told I'm moving from city A to city B, it's pretty easy to adjust to my new surroundings, regardless of the changes. On the other hand, if I'm living in an apartment and am told to go to sleep so I can be packed in a box, bet your bottom dollar I'm gonna start flinging poo if I wake up to find myself in a 10ft x 10ft cardboard shack. ;)
    Bloodawn and gkak like this.
  16. vmed

    vmed Well-Known Member

    Hey Blood I've was trying to recreate the problem with the camera that some guys are having. and then it started happening. At first just random then it went away but now video won't work.. it freezes up when switching from camera to video. And the music player won't work either. No I didn't install anything. I believe it started after I moved the settings app to the home page into the tools folder from there it went down-hill. By the way it was a fresh reinstallation cuz I started getting a few FC's with the camera. I tried taking some logcats but not sure if I did it right, there pretty long. I'm not complaining its a cool rom I was just curious and now I'm trying to help. Hopefully these logs & screenshots help! Anyways thanks for all your hard work!

    Attached Files:

    Bloodawn likes this.
  17. vmed

    vmed Well-Known Member

    I forgot to say that all I did to start these problems was to keep starting each app one by one (Camera to video, then gallery, quickpic, gallery, then hardware camera button) in random order for about 30min. And again this was after a fresh install, no apps added I reorganized apps in alphabetical order in the app drawer, tested each app, and always rebooted after each step. No I'm not complaining, just trying to help! I'll check back later to see what you think. Thanks Blood!
  18. Bloodawn

    Bloodawn Well-Known Member

    I'm probably going to ditch the FF27 base and use FG11 for both sprint and boost. FG11 looks like it would have less issues.
    gkak likes this.
  19. gkak

    gkak Well-Known Member

    thanks for clarifying. this is a great rom and I'm willing to use it even with the issues I'm having. but if it starts flinging poo I'm definitely going to have to go back to stock...
  20. jdogrambo

    jdogrambo Well-Known Member Developer

    thanks im happy your working on getting everything fixed and my phone got shipped today so ill be able to play with it really soon
  21. DMajor239

    DMajor239 Well-Known Member

    Pic messaging doesn't work on my Sprint phone.
  22. vmed

    vmed Well-Known Member

    Were my 2 last posts any help to you Blood? Just wondering if those logcats and screenshots shed a lil light or were they just jibberish lol. Hey this is a great rom & everybody really does appreciate the hard work your doing here! Thanks again Blood!
  23. Bloodawn

    Bloodawn Well-Known Member

    thats cause the rom isn't made for sprint.

    the next update there will be both a sprint and boost version.

    they really didn't say what was causing the problem, so I'm just gonna redo the rom with the sprint base instead of boost. I usually like working on sprint's more anyway and I should of just did it to began with.

    thanks for posting them tho bro.
    vmed and DMajor239 like this.
  24. jdogrambo

    jdogrambo Well-Known Member Developer

    im so ****ing happy that this rom is out
  25. DMajor239

    DMajor239 Well-Known Member

    I'm getting this while trying to play mp3s and m4as
    [​IMG]
    Edit: both on the music and play music app. I can still play music but I have to press play multiple times after receiving those errors.

Share This Page