Search This thread


Senior Member
Nov 11, 2012
This thing is driving me crazy... Is there ANY way at all to disable fast dormancy on CM 10?
The app "fast dormancy toggle" don't work with AOSP roms and I can't figure out how to disable fd. I'm looking for this for days and nothing...

So far, I found these possible solutions:

- fast dormancy toggle -> No effect
- Adding the line "" to build.prop -> No effect
- Adding the line "" to build.prop replacing the XXXXX with my carrier id (in my case 72411) -> I'm about to test this, but I don't have much hope.
- Manually modifying the database file nwk_info.db -> I presume this won't work because this is the same that "fast formancy toggle" tries to do.

Any other tips? Please someone shed some light about this stuff?

I would appreciate ANY help...


New member
Feb 4, 2013
Hello i got a noob queastion about flashing the CyanogenMod. At the moment i have the Android Revolution HD 28.0 rom.
I would like to test the new Cyanogenmod 10.1.3 Stable version. The question is:
Do i have to flash the stock rom before changing to cyanogenmod? Or i can just install the CyanogenMod from ClockworkMod install update from sd card?
Mar 14, 2013
Any application that can do the same as blocking mode does?? Any such feature planned for CM?

Sent from Galaxy S3 running Jelly Bean

I know I'm replying to a really old post, but hopefully it helps anyone else that might be looking. This app seems to pretty much replicate the abilities of Samsung's Blocking Mode and then some. Only just installing it on an i9300 that now has CM11, but I haven't tested it yet.



Aug 3, 2014

After upgrade every time i need manually to edit build.prop for some instances, is it possible to do that automatically or to keep change without copying or editing.

Top Liked Posts

  • There are no posts matching your filters.
  • 187
    "Samsung says they will provide Git server access starting in November 2012 at, and will have a dedicated site for the at"

    Everyone calm down.
    This is not done yet.

    Yes, Samsung will release Exynos source code. "Hurraay!!!" ??? No!

    What they mean by releasing Exynos source code, is that they will release source code for hardware modules for Exynos development boards. We had this for months on insignal website (which is down since a few weeks/months, but used to be up), which contains outdated source code for Exynos boards. We had some bits of Ice Cream Sandwich code back in March or April iirc, that helped Galaxy S II hwcomposer, but that's it. Most of the things were stuck at Gingerbread version, and they don't contain any device-related code.

    What does this mean ? For instance, Galaxy S III camera will stay closed, because it is NOT part of Exynos development boards. Galaxy S II audio is still Yamaha proprietary crap, and we will NOT get source code. RIL interface will also remain closed, so all exynos phones will keep on having broken/semi-functional GSM connection (broken Sim Toolkit, unstable data connection, unstable roaming). TV Out will still remain undocumented, and Android interface won't be opensourced (as it is part of TouchWiz on official ROMs). Same applies for FM Radio.

    Moreover, Insignal code drops were delayed as hell. As of today, we still haven't got anything from official Samsung Jelly Bean, beside kernel source code because they legally have to. As I said, most of the things on Insignal were old, hwcomposer sources for example weren't working on Galaxy S III (exynos4412), and so on.

    Now, I could be wrong and MAYBE they will make this A BIT better (faster code drops), but I'm NOT putting my hopes up on things like Sensors HAL source code, Audio source code, RIL interface documentation, or Camera HAL source code. IMO they just spoke like this to calm down community flood, and make everyone happy and make Samsung look like they're the new holy grail of developers. I'm not trusting this until I actually SEE those improvements.

    So, users, be careful, and we'll see how it's going to get.
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.

    #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. Hard. A lot.

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.


    Noob-proof edition through ODIN:
    - Download this :
    - Reboot your phone in download mode
    - Put the previously downloaded file as PDA
    - Don't tick repartition
    - Make sure repartition isn't ticked
    - Flash it

    Classic ZIP through Recovery method:
    - Make sure you run CWM or TWRP recovery. Follow instructions in the specific threads on XDA.
    - Make sure you run stock ICS rom. We won't care if you didn't and your Wi-Fi isn't working.
    - Download the zip
    - Download Gapps
    - Install the update zip from recovery
    - Install gapps
    - Reboot


    CM10 nightly builds:

    Google Apps:

    Discussion thread:

    Chat: #teamhacksung-support

    Don't expect any support if you:
    - are not running stock cm-kernel
    - have installed any mods
    - have modified system files

    If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
    This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
    Open-Source doesn't mean Out-of-Respect!!!

    If you want to donate a few bucks for the work we're doing in our freetime, goto webpage and hit the big Donate button. Thanks to all donators!
    Ok quick checkin from BABBQ. After this post I'm putting my BT keyboard away and getting drunk, and likely won't return to XDA until Monday or Tuesday evening.

    The official announcement was kinda "meh". It's really what's going on behind the scenes that is mattering.

    There are multiple devrel people at Samsung, many of whom weren't even aware of each others' existence. They now are, and I have quite a few new contacts. Now, requests from us are probably going to go through multiple chains. Whether this makes a difference, who knows - but it is a potential step forward.

    They also had an engineer from LSI that I talked to personally. It was a bit difficult due to the language barrier, but I sort of got the impression that the problems with current Insignal source on our phones aren't phone-specific - some of this **** is broken even on the OrigenBoard itself. Same case for libcamera - it sounds like the current Insignal one is pretty low-quality/broken, and the "new" source may be improved. It won't be directly usable on our devices, but it may represent a significant step forward. e.g. instead of "it's totally and completely broken", it may be "sorta working and needs some tweaking for each camera module" - See, for example, use of the Nexus S libcamera on Aries-family devices - each one has needed device-specific work, but instead of being an insurmountable task, it may be feasible. However, please keep reading regarding maintainer exhaustion...

    I also got the impression that future Insignal drops are going to be more aggressively managed by LSI. Again... none of this is official.

    November is likely to be another ICS tarball, however, one that is actually working. The engineer I spoke to said that the actual JB differences are minimal. (As in, I know what they are, and in fact we have an implementation of the JB differences in Gerrit already. The problem is the underlying hwcomposer is apparently broken even for OrigenBoard+ICS with the current Insignal source. Functional ICS HWC shouldn't be too hard to JB-ify. (Look at the Nexus S HWC as an example of what needs to be done to go from ICS to JB.)

    The new source drop might also allow us to finally fix HDMI.

    The problem is - Thanks to the lack of documentation for the past few months, the team of CM maintainers for Exynos are exhausted and far behind on other non-Exynos-specific stuff. So this isn't going to be a magic bullet. It alone probably won't get us M builds.

    However the other "behind the scenes" item is that a bunch of Samsung people were here, and they're probably going to be writing trip reports to management. This trip reports are going to likely include the massive amount of pwnsauce Sony dished out. Speaking of that - Espenfjo, xplodwild, and codeworkx, Y U NO FLY HERE? Chainfire, Jerpelea, and Supercurio were all here. U NO GET SMARTWATCH! :p

    So Samsung Mobile might be more receptive to community requests in the future. Our contacts are likely to be in a MUCH better position to facilitate things than before.

    So it's a step forward... But it's likely to be months before any of us consider a new Exynos device, and our current devices are likely to always be behind others because we're just too far behind as it is. But if Samsung keeps on improving, after a few months users might see definitive improvements.

    With all of that said, I'm off to party and feast. You won't see any more from me until Monday evening at the absolute earliest.

    Sent from my GT-N8013 using Tapatalk 2
    So.... This basically means the future of CM10 on this device is basically down the toilet?

    no. xplodwild is still there.

    It's not about samsung or sony.
    It's about the soc used. In our case exynos.

    Samsung doesn't provide proper sources or documentation for their own platform.
    And if they do after it's much to late, it's outdated and incompatible.

    Compare the qualcom or omap based samsung phones vs. the exynos ones.
    All qualcom and omap based samsung phones got jellybean and butter in zero time.
    We're still fighting with exynos and the i9100 guys have to wait another months if it will get jellybean at all.
    I assume samsung is skipping it and will only do a value pack. There's no single line of code or a leak yet.
    It's a shame.

    I9100g (omap4, same hardware as i9100) got jellybean pretty instant. opensource hwcomposer, opensource audio, butter, working tvout
    I9100: (exynos4, same hardware as i9100g) buggy jellybean, closed source and incompatible audio, no butter, no tvout, bugs which will never be solved.

    what do we learn from this?
    Don't buy exynos phones.

    I don't know it either, that's why I was asking ... though I highly doubt that. Sony is not really known for embracing open source or any other open standards for that matter ...


    the xperia s is becoming a aosp device. sony is contributing a lot to aosp.
    sony is releaseing official beta firmwares. sony cares about the community developers.

    the xperia t kernel sources are damn close to qualcom reference code.
    kernel sources are already out and the device isn't available in most countries yet.
    if it goes well, that could be the next aosp device which gets support after it hit the market.
    Download | (md5sum)