• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

Fixing problems on my Ported ROMs- ROM #1- AtomicMod

1 post in this topic


Hello there.

I ported a few ROMs to our devices and now it's time for me to go through and attempt to fix each one. First on my list is 'AtomicMod' which is a ROM based on stock 2.3.5. I'm trying to find problems and fix them. So far, I have found a few issues, some are probably easy fixes whilst some other may be a pain. As I am far from a developer and I lack the knowledge to fix the ROM on my own, I need help from you guys.

General stuff like calls/texts/mobile data/all camera functionality/usb mass storage works fine. But there is a few issues- Bluetooth and proximity are my biggest targets.

I'm trying to fix the proximity issue first.

Here's a screenshot of the built in proximity menu on Atomic Settings;


I tried to run a logcat but I honestly have no clue what I'm expected to find regarding the proximity. On the plus side I searched the .txt file and there is no fatal issues, just normal errors.

I've attached the logcat.txt just in case anybody wants to check it out for me. The things I can spot are just general proximity failures and none of them give me a sense of direction on where to go from here.

E/EMODE_SensorTest( 836): *************CalibrationProximity res=ffffffff

E/EMODE_SensorTest( 836): **************low=0

E/EMODE_SensorTest( 836): **************high=0"

^ Like so.



Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.