• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory
Search This thread

FL0OD

Senior Member
Jul 27, 2010
2,596
963
sounds fc's for me tooooooo :D

not sure when it started doing that, only thing non-stock i'm running is dark froyo theme. on latest nightly

it may be the theme. i was running a nightly with that matted blue theme and i used to get the same fc trying to get into sound settings. i wiped cache and dalivik and removed the theme and no problems since. i am using dark froyo now though and i am not having issues.
 
it may be the theme. i was running a nightly with that matted blue theme and i used to get the same fc trying to get into sound settings. i wiped cache and dalivik and removed the theme and no problems since. i am using dark froyo now though and i am not having issues.

just to clarify, mine only FC's when going into volume controls from the sound settings. all the other stuff seems to work fine.


tried this but still volume FC's.. YMMV

http://forum.cyanogenmod.com/topic/7813-menu-settings-sound-force-close/
 
Last edited:

alwaysbelieve1

Senior Member
Aug 29, 2006
1,167
74
St. Charles
www.BobGaronTraining.com
Yea seems as though every one has varing degrees of success with different set ups. You may want to try calibrating your battery if you haven't already. I do it every time I switch rom's and some times if I have problems with my battery just from flashing so much. I am currently running Toasts. 35 with setCPU used for underclocking only and every thing has been good.

Sent from my SUPERSONiC

OK cool! Thanks

Bob

P.s. How do YOU calibrate YOUR battery?


Sent from my PC36100 using XDA App
 
Can the guys who're getting FC's post up logcats?

Swyped from my EVO via the XDA app

will this work?


D/alogcat ( 1062): stopping ...
D/alogcat ( 1062): stopping ...
D/alogcat ( 1062): paused
W/Process ( 165): Unable to open /proc/1076/status
W/ResourceType( 165): Skipping entry 0x7f040005 in package table 0 because it is not complex!
W/KeyCharacterMap( 1008): No keyboard for id 65537
W/KeyCharacterMap( 1008): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/ActivityManager( 165): Displayed activity com.android.settings/.Settings: 324 ms (total 324 ms)
D/dalvikvm( 1083): GC_FOR_MALLOC freed 2844 objects / 225872 bytes in 34ms
I/ActivityManager( 165): Displayed activity com.android.settings/.SoundSettings: 325 ms (total 325 ms)
D/AndroidRuntime( 1083): Shutting down VM
W/dalvikvm( 1083): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
W/Process ( 165): Unable to open /proc/848/status
I/Process ( 1083): Sending signal. PID: 1083 SIG: 9
D/dalvikvm( 1008): GC_EXTERNAL_ALLOC freed 1839 objects / 100560 bytes in 63ms
D/alogcat ( 1062): resumed
D/alogcat ( 1062): canceling periodic saves
I/ActivityManager( 165): Displayed activity org.jtb.alogcat/.LogActivity: 116 ms (total 116 ms)
D/dalvikvm( 996): GC_EXPLICIT freed 1457 objects / 99624 bytes in 43ms
D/dalvikvm( 1008): GC_EXPLICIT freed 923 objects / 47752 bytes in 62ms
 

FL0OD

Senior Member
Jul 27, 2010
2,596
963
OK cool! Thanks

Bob

P.s. How do YOU calibrate YOUR battery?


Sent from my PC36100 using XDA App

this is what I have been doing although it has been made a little more challenging with the removal of the green charging light "feature". I usually see my best result after doing this and letting the rom settle in for about 24 hours. some times i see result right away. its a wonderful world of trial and error.:D
 

SantinoInc

Senior Member
Jun 19, 2010
3,447
868
NYC
Dr. u day man! I checks out that link. The second poster sad that all he had to do was clear the Data under Settings (in Manage APPLICATIONS) It did alter my desktop theme and God knows what else but I'm satisfied. I was about to flash back to stock, lol. Speaking of stock, is there anyway to get the stock keyboard on this? I miss the directional arrows, exit keyboard button and long press for numbers/characters.
 
Dr. u day man! I checks out that link. The second poster sad that all he had to do was clear the Data under Settings (in Manage APPLICATIONS) It did alter my desktop theme and God knows what else but I'm satisfied. I was about to flash back to stock, lol. Speaking of stock, is there anyway to get the stock keyboard on this? I miss the directional arrows, exit keyboard button and long press for numbers/characters.

if you reboot u will be able to get your wallpaper set back up & u'll just need to go thru settings & set things up like u want them.

regarding the keyboard just do a search, there are sooo many choices out there.
 

ninjaquick

Member
Mar 20, 2009
28
2
will this work?


D/alogcat ( 1062): stopping ...
D/alogcat ( 1062): stopping ...
D/alogcat ( 1062): paused
W/Process ( 165): Unable to open /proc/1076/status
W/ResourceType( 165): Skipping entry 0x7f040005 in package table 0 because it is not complex!
W/KeyCharacterMap( 1008): No keyboard for id 65537
W/KeyCharacterMap( 1008): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/ActivityManager( 165): Displayed activity com.android.settings/.Settings: 324 ms (total 324 ms)
D/dalvikvm( 1083): GC_FOR_MALLOC freed 2844 objects / 225872 bytes in 34ms
I/ActivityManager( 165): Displayed activity com.android.settings/.SoundSettings: 325 ms (total 325 ms)
D/AndroidRuntime( 1083): Shutting down VM
W/dalvikvm( 1083): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
W/Process ( 165): Unable to open /proc/848/status
I/Process ( 1083): Sending signal. PID: 1083 SIG: 9
D/dalvikvm( 1008): GC_EXTERNAL_ALLOC freed 1839 objects / 100560 bytes in 63ms
D/alogcat ( 1062): resumed
D/alogcat ( 1062): canceling periodic saves
I/ActivityManager( 165): Displayed activity org.jtb.alogcat/.LogActivity: 116 ms (total 116 ms)
D/dalvikvm( 996): GC_EXPLICIT freed 1457 objects / 99624 bytes in 43ms
D/dalvikvm( 1008): GC_EXPLICIT freed 923 objects / 47752 bytes in 62ms

Try without DarkFroyo. Also, what is your dalvik heap size set at?
 

LifeInTheGrey

Senior Member
Dec 2, 2009
1,304
231
Boston
This could very well be a kernel issue but the snap turbo doesnt wanna play nice with RC1... i tried twice doing a clean install nd following instructions but everytime the snap program reboots it freezes at the white htc screen... im going to post in the snap forum too but just thought id post the issue here as well. Also is anyone else getting a fc when.opening the radio? It appears bt is hanging the cpu...

Sent from my PC36100 using XDA App

Covered ... too ... many ... times ... head ... will ... implode ... AHHHHHHH ...
 

barnacles10

Retired Recognized Developer
Mar 25, 2010
4,257
1,317
This could very well be a kernel issue but the snap turbo doesnt wanna play nice with RC1... i tried twice doing a clean install nd following instructions but everytime the snap program reboots it freezes at the white htc screen... im going to post in the snap forum too but just thought id post the issue here as well. Also is anyone else getting a fc when.opening the radio? It appears bt is hanging the cpu...

Sent from my PC36100 using XDA App

wow-thats-really-interesting.jpg


haha sorry. but guys..

SNAP TURBO IS NOT COMPATIBLE WITH RC1 without issues
FM RADIO IS ENABLED IN CMs NEW KERNEL, SNAP KERNEL WILL BREAK IT
SNAP 7.6 HAS BLUETOOTH ISSUES
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 105
    CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.

    THIS IS NOT HTC SENSE AND NEVER WILL BE. DO NOT ASK ABOUT IT IN THIS THREAD. THANK YOU.

    Code:
    #include <std_disclaimer.h>
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.

    Visit the CHANGELOG for a full list of changes and features!

    All source code is available at the CyanogenMod Github!

    If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.


    INSTRUCTIONS:
    - First time flashing CM 6 to your Evo (or coming from another ROM)?
    1. Unlock/root your device and install Clockwork Recovery via ROM Manager or Amon_RA's recovery image (You MUST be NAND unlocked!)
    2. Do a Nandroid backup!
    3. Update your radio if necessary
    4. WIPE
    5. Install the ROM
    5. Optionally install the Google Addon

    - Upgrading from earlier CM6?
    1. Do a Nandroid Backup!
    2. Install the ROM (your Google apps will be backed up automatically)

    HOW TO REPORT BUGS OR PROBLEMS?
    - Was it a hard reboot? Get me the file "/proc/last_kmsg".
    - Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
    - Pastebin links preferred
    - Please use the issue tracker whenever possible!

    Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.

    The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.

    Known Issues:
    * No 4G or HDMI yet.

    Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
    16
    Anyone know if they moved the nightlies to another host? TeamDouche was last updated on the 17th. Or have they just not released any since then?

    There haven't really been any updates since we've been working on CM7. We'll be starting the nightly builds for the new version soon :)
    10
    I like the "almost inspiring" part. Like the world may initially be enough to inspire, but that's temporary.

    the "almost" bit is due to my recent experiences with certain people i've come across in the android world. it's a slight bias. take that out of the equation and my trust in humanity goes up quite a bit.

    Hmm ... two stalwarts questioning faith in mankind has inspired me to form a new years resolution, and perhaps others will join me in this voyage.

    No one appreciates flaming, beration, derision, or otherwise malicious acts cast upon them when they display ignorance in forum protocol. While their action is not excusable persay, when met with repugnance it only festers into defensive anger, and when the noob becomes the veteran, they carry this faulty tradition to the next noob, creating a vicious cycle of ambivalent malevolence. I myself am guilty of propogating this cycle, but no longer.

    Henceforth, I vow to be nothing but positive and helpful when responding to questions. Failure in following established protocols (such as reading back and searching) will of course be pointed out, but rather than villify I will educate, rather than strike down I will raise up. No longer shall I further five-page flameathons dedicated to chest-beating and grunting. No longer shall I respond with spite and disregard to a simple question that could more easily be answered with a simple answer. I ask that others join me on this quest to improve this and other threads, to make XDA the community of help and support it was founded to be, and to assist in recruiting future members that can lead this community further into the future.

    XDA brothers and sisters, join me.
    9
    6.1.2 is up with the new hardware support :cool:
    7
    You know, as much as everyone likes to flame this person, I can actually say that I had a similar situation (except for the fact that I never blamed CyanogenMod ). My old Evo used to have problems with random rebooting that seemed related to overheating. I recognized that everything ran more smoothly on CM, but unfortunately it was like turbocharging a ****ty car. Despite wiping my phone every way possible, it would crash and reboot like nothing else.

    Now I turned in my old phone for this new one and can sing the praises of Cyanogen! I rooted my phone, installed Cyanogen once and haven't needed to reboot since.

    That is actually the exact reason for the flaming ... you didn't lash out, you troubleshooted. In your case it was the phone itself, and as you say everything is running smoothly now. On that note ... /begin soapbox

    In America today, there is a rampant epidemic, and that is the lack of self-awareness and the inability to doubt oneself. In times past, the ideas of honor and integrity meant that when faced with a difficulty you work as best you can to overcome it, and if you made a mistake along the way, you accept it and own up to it. Now, we don't even get to the point we recognize possible mistakes we made ... all that occurs is blame. Something is not working on my phone, in my car, in my life ... it must be someone or something ELSE's fault. There is no self-awareness anymore, so there is no need to work to resolve your own problems (as complaining about it is much easier). This comment is a microcosm, a personification of that lack of honor, that lack of integrity, that plagues the masses. That is why CM is so vigorously defended by its users, and why the flaming commences, because it too is a microcosm ... but for the restoration of that integrity, the willingness to put in the hard work necessary to reach the goal you seek instead of complain when others don't reach it for you. I personally fight for these ideals, these principles, and while this rom is "just another rom" to others ... to me, it is a very small realization of what I believe to be important, a small truth of humanity that is rarely recognized in the modern world.

    /end soapbox