shezzy

I usually switch between cam apps, I use the stock one for things that don't move and if I want best quality. Any way to have both? Weird how the stock cam app locks the camera yet I haven't even opened it.

jdogrambo

ok then what you do is copy the apk on your sd card then delet it and then reinstall it from your sd card

Bloodawn

I just installed Fast Burst Camera Lite and opened it, took some pictures and everything is working fine. so I'm not sure why its doing that for you.

did you try rebooting to see if it fixes it?

if that doesn't fix it try going to settings > applications > manage applications > all > camera and hit force stop

__________________
Goo - Github

Last edited by Bloodawn; August 27th, 2012 at 06:35 PM.

jdogrambo

oh i didnt think of force stopping it but i was thinking if that doesnt work he should try reboot

Bloodawn

I see the problem. next time I update the rom I'll fix it.

TeachMe

Thanks dude you rock love the rom .

jdogrambo

ok so do we have to use the touch screen keyboard till this is fixed?

Bloodawn

the keyboard works fine

jdogrambo

ok thanks blood fer porting this over to the ultra do you think you could work on cm7 when you get some time

xaelith

Sounds like this is a Boost TU ROM....has anyone with a Sprint TU tried it yet?

Great work, by the way, Bloodawn, and welcome to the TU forums. Happy to see the Ultra get another dev.

Bloodawn

you have to remember that I do shit for 3 different phones, have a job and all kinds of other shit going on right now. I did a CTMod for you guys like I said I would but don't be expecting me to be releasing any other rom's anytime soon. I haven't even got the rom I use for my own phone out of alpha yet.

Bloodawn

yea its for boost. I'll set something up for sprint next time I update it.

jdogrambo

thats why i said when you get some time

Bloodawn

I'm just letting you know that I may not get time so you don't get your hopes up.

DMajor239

I have.

shezzy

I have tried force stopping camera and still no go. I also reinstalled ctMod and tried it again. I use the full version of Fast Burst Camera v3.5 - I appreciate your work but have decided to switch back. Thank you for your time & effort

gkak

Running this awesome rom, updated baseband to FF27 manually, froze xperia launcher and using ADW ex. I'm getting random "mini" reboots, seems to be happening when using the messaging app or when hitting the power button. I tried factory resetting, reinstalling ctmod 3.69 but doesnt help. Also the camera acts up sometimes only accessible via hardware button sometimes only via icon. thanks for this great rom...

jdogrambo

why would you stop using it because of the camera

DMajor239

Maybe its just a feature he personally likes and uses alot.

shezzy

This. Having a young child its almost impossible to get pics with the stock shutter speed on the regular cam. Also, I noticed only about 100 points increase in benchmark tests (antutu?) It def is a really nice ROM I just couldnt go without the cam app

Rick1488

I tried the rom but everytime I use the stock messaging app it soft crashes the whole system.

casperischinky

Try go sms I been using it since my prevail days and I love it,even has themes for it too.

Zintus

I have downloaded and have used this rom before... as a matter of fact it's on my friend's prevail thanks to me lol he knows nothing about computers or rooting phones lol...

So on my TU I am experiencing the launcher reboots as well... holo launcher seems to work well with the phone as i was using it with the stock rom yesterday lol... i am going to root uninstall xperia... and use the holo launcher as a system launcher... now, can i just copy the apk to /system/app/ or do i have to edit something to get it to recognize holo???

Anyways Blood, you da man! :-)

Bloodawn

If you guys are having a FC or a reboot that you can actually make happen more then one time post a logcat of it and/or tell me with detail exactly what you did with to make it happen. If I don't have a log or I can't recreate the problem I can't fix it. Chances are if you can't get it to do it again it was just a one time thing.

You can just copy it there.

Last edited by Bloodawn; August 28th, 2012 at 09:33 PM.

bobcan13

I'm getting the "mini" reboots too. Mostly when using chrome and hitting the power button. I haven't been able to reproduce it it the last 30 minutes to capture the logcat. I also get random camera failures using the shortcut and hardware button. I've attached the logcat of the camera button failure. Will keep trying for the "mini" reboots.

Love this rom though!! Thanks for your work.

Got a mini reboot in chrome attached logcat. Thanks!

Attached Files

	camera_error.txt (6.5 KB, 5 views)
	Mini-reboot.txt (38.6 KB, 29 views)

Last edited by bobcan13; August 28th, 2012 at 11:12 PM.

gkak

--------- 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

gkak

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

ruinevil

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.

Last edited by ruinevil; August 29th, 2012 at 01:24 AM.

cjoeone

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.

Mako 230

""
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!

Last edited by Mako 230; August 29th, 2012 at 06:40 AM. Reason: spelling

Bloodawn

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.

Bloodawn

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.

gkak

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

fatnickd1

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.

Bloodawn

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.

Paradoxx

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

Zintus

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....

Bloodawn

yes, thats what broke everything.

don't use backups that weren't made while on CT.

gkak

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 ...

xaelith

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.

vmed

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 Images

	screenshot-1346318772279.png (63.5 KB, 30 views)
	screenshot-1346320488477.png (62.9 KB, 26 views)
	screenshot-1346321037200.png (57.5 KB, 23 views)
	screenshot-1346321108432.png (63.1 KB, 25 views)

Attached Files

	alogcat.2012-08-30-04-54-38-0500.txt (55.6 KB, 6 views)
	alogcat.2012-08-30-05-00-52-0500.txt (55.7 KB, 0 views)
	alogcat.2012-08-30-05-03-27-0500.txt (55.1 KB, 1 views)

vmed

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!

Bloodawn

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

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...

jdogrambo

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

DMajor239

Pic messaging doesn't work on my Sprint phone.

vmed

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!

Bloodawn

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.

jdogrambo

im so ****ing happy that this rom is out

DMajor239

I'm getting this while trying to play mp3s and m4as

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.

Last edited by DMajor239; August 30th, 2012 at 05:59 PM.