Search This thread

TJKV

Senior Member
Jun 25, 2011
1,927
2,747
Yup. What's today's date? ;)

Anyone knows whats going on?[/url]

When the camera torch is on, the brightness of the led during focusing is lesser than when the picture is being captured. Is it possible to make the capture brightness lower when in macro mode, maybe equal to the value it is at for focusing?

Sent from my MB525 using XDA
 
Last edited:

maniac103

Senior Member
Jan 3, 2008
758
946
When the camera torch is on, the brightness of the led during focusing is lesser than when the picture is being captured. Is it possible to make the capture brightness lower when in macro mode, maybe equal to the value it is at for focusing?

Sent from my MB525 using XDA

Nope. The torch brightness is controlled by the camera blob, and there's no chance of overriding it.

Sent from my Defy
 
  • Like
Reactions: TJKV

pedromole

Member
May 3, 2011
16
1
@Maniac103

Just to let you know that the wifi calling app does not work on Orange UK. Getting an error 'Invalid SIM'.

Any chance you could look at putting the Orange app 'signal boost' into a future build?
 

[] AL []

Inactive Recognized Contributor
Feb 22, 2011
2,870
4,637
Unwanted Blacklisting.

I can't pinpoint exactly what triggers it yet, but there's something at call ending stage that sometimes offers you to add the person you were talking with to your blacklist.

I've noticed this before and it just happened to me again when in an elevator.. I don't know if the signal got lost or not and I might have pressed the hang up button a couple times... But nwvertheless that option to blacklist pop'd up and I almost did accept the offer..

I'm posting this in fact, because it also reminded me that my gf has blacklisted her dad by mistake (for 2 days) last week - probably in the same manner..

She thought that her face touched the screen during the conversation somehow and did it...but I doubt so since display is off by proxy sensors and that shouldn't be possible....

Anyway, I will keep an eye on this and try to find out when that happens...might not be a real bug but might be worth a change at least...
 
Last edited:

maniac103

Senior Member
Jan 3, 2008
758
946
Question if I may..

Could this commit (Fix rare crash on phone app startup.) be related in any way to the DSP Manager FCs on incoming call pick up?

Because I've experienced a few (3-4) of those recently as well [M-0328].
Did not ge too many calls lately and still no logcat about this though...

How reliably can you reproduce those? I ask because I have two options:
  • Sprincle a number of debug statements into the code, which will hopefully pinpoint the root cause when captured in logcat
  • Add a number of try-catch blocks, which avoid the FC, but leave the root cause of the FC intact
Option 1 is only feasible if it's reproducable within a relatively short timeframe, though.

EDIT: OK, I did option 1. New nightly is currently uploading. As soon as you have the crash again, please grab the logcat. Thanks.

@Maniac103

Just to let you know that the wifi calling app does not work on Orange UK. Getting an error 'Invalid SIM'.

Any chance you could look at putting the Orange app 'signal boost' into a future build?

Depends what is different between T-Mobile and Orange. If it's only the app, it should be feasible. If it's also the GAN layer and/or the libkineto, it'll get ugly.
Where can the Orange kineto be found? In any case, it should be harmless to try:
  • Enable kineto in DefyParts
  • Delete (or rename file extension of) /system/app/MS-MOTOJDN-FROYO-KNT20-02-A0-24.2.apk
  • Copy the Orange version to the phone
  • Does it work?
 
Last edited:

[] AL []

Inactive Recognized Contributor
Feb 22, 2011
2,870
4,637
How reliably can you reproduce those? I ask because I have two options:
  • Sprincle a number of debug statements into the code, which will hopefully pinpoint the root cause when captured in logcat
  • Add a number of try-catch blocks, which avoid the FC, but leave the root cause of the FC intact

EDIT: OK, I did option 1. New nightly is currently uploading. As soon as you have the crash again, please grab the logcat.

I will install it whithin an hour or so and will sure try to catch a log.

But I must admit that I might not be the best tester here since I barely get a call/day on my Defy these days....
 

Sigray

Senior Member
Aug 15, 2011
1,645
280
Google Pixel 7 Pro
Whats the real difference between maniac's and euroskank's builds? Which one the better for every day use?




@maniac : can you add the torchlight option to the lockscreen?
 

[] AL []

Inactive Recognized Contributor
Feb 22, 2011
2,870
4,637
DSP FC

OK got one!

Recieved 2 calls: no problem, then after hanging up on 3rd call: DSP fc [log attached - loopers on lines 57 & 73].

I don't know if this could be related at all, but I've used the custom equalizer settings in N7Player (then exited the app) before I made the last call.

Cheers.

Edit: I wasn't using the headset or speakerphone either; don't know why the log shows many entries like this one (re headset): --> ok headset is not headphone: my bad I guess --> well, DSP calls headphones headset so.. don't know...

"E/HeadsetService(2618): Could not apply bass boost settings"

And why is band 2 set 6 times at the end of the log? What about the other bands?

04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 0
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 1
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 2
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 3
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 4
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 5
 

Attachments

  • DSP_fc.txt
    15.7 KB · Views: 10
  • N7_EQ.JPG
    N7_EQ.JPG
    37.6 KB · Views: 357
Last edited:

maniac103

Senior Member
Jan 3, 2008
758
946
OK got one!

Recieved 2 calls: no problem, then after hanging up on 3rd call: DSP fc [log attached - loopers on lines 57 & 73].
Thanks, but is that the complete logcat? The reason for the exception being thrown is the 'bad status -19' line ... status -19 is NO_INIT, which must have its reason (perhaps way) before that.
logcat -d | wc -l says 1337 (nice coincidence ;) ) here, so did you apply any filtering?

I don't know if this could be related at all, but I've used the custom equalizer settings in N7Player (then exited the app) before I made the last call.
I don't think so, but trying to reproduce it under the same scenario surely can't hurt.

Edit: I wasn't using the headset or speakerphone either; don't know why the log shows many entries like this one (re headset): --> ok headset is not headphone: my bad I guess --> well, DSP calls headphones headset so.. don't know...

"E/HeadsetService(2618): Could not apply bass boost settings"
The service enabling and disabling the various effects in DSPManager is called HeadsetService for whatever reason (probably history).

And why is band 2 set 6 times at the end of the log? What about the other bands?

04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 0
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 1
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 2
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 3
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 4
04-03 17:35:17.155 I/Effect-Equalizer(17781): Setting band 2 to 5
That debug message is just broken.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 728
    CyanogenMod 7 for Motorola Defy

    Status CyanogenMod 7.2.0 Stable:

    Changelogs:
    Code:
    [B][COLOR="Red"]7.2.0[/COLOR]:[/B]
    
      The official 7.2.0 and actual official nightlies doesn't include
      all our features. That is the purpose of the this release.
    
    Common: Connection Profiles and Notifications Enhancements
    Common: Lockscreen Calendar and options
    Common: Phone Landscape Dialpad Layout*
    Common: Keyboard : Swipe Gestures (caps, keyboard modes)*
    Common: Device specific Settings Menu
    Jordan: Multitouch and LED mode settings
    Jordan: Compass calibration and DSP settings (from motorola)
    Jordan: Better Battery Life
    Jordan: Button Backlight Tuning
    Jordan: Camera and videos Enhancements, enhanced stability*
    Jordan: Fake pds partition to prevent alterations
    Jordan: Enhanced ADB over Network (Notification icon)*
    Jordan: Recovery 5.0.3.1 with devtree support
    Jordan: Open source ADBD and Busybox "adb shell" with history saving
    Jordan: Busybox 1.19.3*
    Jordan: Market fingerprint and stability
    
    (*Not merged in upstream for the moment)
    
    [B]03.09.11 7.1.0-RC1.5 Jordan (3 Sep 2011):[/B]
    USB/Wifi/Bluetooth Tethering.
    New set of kernel modules built from sources: MMC-fix, overclocking, multitouch
    Camera: Touch to focus
    Camera: video flashlight for red camera
    N-point MultiTouch (persist.sys.multitouch)
    Fixed geotags in the photos
    Fixed dual SIM adapters which use Stk not working
    Increase boot speed. (merged in CM7)
    Bionic libc optimization (merged in CM7)
    CrystalTalk (Voice filter)
    Bootmenu 1.0.4 with adb modes and new Mass storage modes
    Overscroll custom color (not only set by themes)
    Adb over Network with warning
    Camera shutter mute setting (persist.sys.camera-mute)
    BusyBox v1.19.1-cm71 bionic
    [B]28.06.11 RC1v2:[/B]
    179 Kernel
    Wifi indicator fix
    Fix BT when FMradio is started
    Fix FMradio APP
    Added 'ro.battery_light=true' in build.prop, true - enable BatteryLight while charging
    CIFS module.
    Widescreen photo.
    Some improvements in 3D..
    Overclock configuration is automatically backuped and restored, if you install new version of rom.
    Fix zoom problem.
    Fix Secure login by wifi (MotoPortal, IE Only)
    Fixed exposure setting in camera app
    Fixed camera timestamps for green lens
    Cosmetic fix 'Scaling Range' & 'CPU Frequency Range'
    Fix camera timestamps for BAYER camera
    [B]04.06.11 RC0:[/B]
    fixes SMS troubles for Chinese users
    Fix 100% CPU usage.
    [URL="http://xdaforums.com/showthread.php?t=1033654&page=370"]1% step for battery[/URL]
    Removed "factory reset" from settings.
    Removed  reboot dialog.
    Latest CWM/Bootmenu
    [COLOR="RoyalBlue"]New safe frequencies:[/COLOR]
    [COLOR="RoyalBlue"]300-30
    600-46
    1000-58[/COLOR]
    Adobe flash HW.
    New Wifi.
    Speakerphone fix
    Pattern lock timeout (same as stock froyo) (author quarck 4pda)
    WVGA video recording for green camera (author vick33)
    Added NetworkMode in settings: GSM only, WCDMA only, GSM/WCDMA auto, GSM/WCDMA preferred
    Increase boot speed.
    Proximity workaround patch (author quarck 4pda)
    [B]13.05.11 Beta6:[/B]
    [URL="http://xdaforums.com/showpost.php?p=13563743&postcount=2835"]Fixed a problem waking device when switched off the lock screen. If you press the volume buttons and the headset button.[/URL]
    [URL="http://xdaforums.com/showpost.php?p=13569142&postcount=2865"]issue #130 - Beta 5.1 Can't charge when shutdown![/URL]
    fix 2USB Storage icon 
    Enables SIP on WIFI only - False 
    Fix Autobrightness levels
    Fix camera frame drops.
    Maybe fix batt drain.
    Busybox 1.19
    Increase of brightness
    Increase of brightness flashlight (High brightness) so as ledefy on max.
    Clockwork 3.0.2.8
    Bootmenu 0.8
    latest Android.
    Some small fixes
    
    [B]07.05.2011 Beta5.1:[/B]
    AGPS...
    Some fixes.
    New Update.zip
    [B]03.05.2011 Beta5:[/B]
    Added SIM Toolkit app
    Fm-Radio
    Re-Reworking sensors.
    Some changes in Wifi and Video codec's.
    Stock Torch APP/Widget. 
    Update to 2.3.4 -> CM 7.1.0-RC0:
    - DSP Manager: equalizer presets
    AAC+
    Maybe even have forgotten ...
    
    [B]29.04.2011 Beta4.1:[/B]
    Fix DroidWall/Iptables ( kang.project-voodoo.org/f/iptables-cm7-kang.zip )
    Reworking Wifi.
    Update busybox to 1.19 - [COLOR="Red"]Disabled in beta4.1[/COLOR]([URL="https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/57"]issues #57[/URL]) )
    720p Playback. [url]http://xdaforums.com/showpost.php?p=13136257&postcount=1526[/url]  - [COLOR="red"]Disabled in beta4.1[/COLOR]
    Reworking Overlay & Codecs (No more proprietary)
    CM -> 7.0.2
    AAC/WMA codec in the video now has hardware acceleration. (improvement 720p )  - [COLOR="Red"]Disabled in beta4.1[/COLOR]
    Added MotoPortal.
    GPS_fix2 included.
    basebandswitcher V3.1 multilanguage V0.1  included.
    Fix Auto-Brightness
    min_free_kbytes -> 4096
    Fix red camera.
    
    [B]20.04.2011 Beta3:[/B]
    Fix Skype and some other programs. 
    Fix Red Camera... thanks for solution to [URL="http://xdaforums.com/member.php?u=3911109"]pabx [/URL]
    Fix Headset button ([URL="https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/1#issuecomment-1021778"]issues #1[/URL]) - [URL="http://ge.tt/4mEYIiv/Fix_Headset_button.zip?type=download"]Update.zip for beta2[/URL]
    GPS icon fix -  ([URL="https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/4"]issues #4[/URL]) - [URL="http://ge.tt/6CLUIkP/Fix_GPS.zip?type=download"]Update.zip for beta2[/URL]
    Fix double USB icon.
    Small fix for GPS(Searches faster satellite)
    Added Baseband Switcher.
    Fix Camcoder (big thanks to [B]morpehus[/B] (4pda.ru))
    Charging of battery with the phone off  ([URL="https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/36"]issues #36[/URL])
    
    [B]17.04.2011 Beta2:[/B] 
    Fix RIL.
    Fix APN's
    Fix Compass.
    Fix Opengl 2.0
    Fix Live Wallpapers.
    The volume keys do not wake device
    
    [B]16.04.2011 Beta1:[/B] 
    [B][COLOR="Blue"]RIL Now Works![/COLOR][/B]
    All sensors works
    GPS now Works
    Reworking Audio
    Rooted.
    Kernel from new 3.4.2-177
    
    [B]15.04.2011 Alpha2:[/B] 
    Bluetooth now working for transfer files
    USB Fully working.
    Camera: Photo working with prewiev. FLASH working.
    Added more languages
    2nd-init by default (unstable)
    Audio and DSP Manager now works
    G-Sensor(KXTF9), LM3530, AK8973.
    LED: All colors
    DSP: H264 Video
    3D:  Improve Performance
    Superuser added / not works correctly.
    
    [B]13.04.2011:[/B] 
    First release for demostration work CM7 on Defy. (and not fake)
    INSTRUCTIONS:
    1. Flash froyo
    2. Copy *.zip to sdcard
    3. Reboot your device in BootMenu/ClockWork
    4. WIPE (wipe data/factory reset + wipe cache partition)
    5. Install the *zip
    6. reboot

    If you liked this project, you can donate
    Paypal: quarx@yandex.ru
    WebMoney:
    USD:Z319203344726
    Yandex money: 4100188263979
    Or you can buy this app: https://market.android.com/details?id=com.donatecm7
    ---------------------------------------
    Donate to Epsylon3 (tpruvot)
    PayPal: epsylon3@gmail.com
    http://xdaforums.com/donatetome.php?u=803131
    ---------------------------------------
    Donate to Maniac103
    PayPal: dannybaumann@web.de
    http://xdaforums.com/donatetome.php?u=765758

    All the found issues, please send to GITHUB - https://github.com/CyanogenDefy/android_device_motorola_jordan/issues

    Sources on github:
    Download:
    repo init -u git://github.com/CyanogenDefy/android.git -b gingerbread
    repo sync
    Build:
    . build/envsetup.sh && brunch jordan

    F.A.Q

    Latest Google APPS

    Download:
    Official cyanogen builds
    Epsylon Nightly Builds
    Quarx Nightly Builds
    Maniac103 Nightly Builds
    28
    Disclaimer: The next lines are by no means meant offensive or as a personal attack. It's just my personal opinion that I feel needs to be expressed.

    Yea, indeed. There are so many extra function in CM7 that I don't use it. I hope that the experimental phase will be transferred to ICS project. XDA's CM7 need to be finished by removing as many bugs as it's possible.
    I think you should get your expectations correct (refering to 'need to be finished'). Unlike e.g. Motorola, we don't need to deliver a completely finished, totally bug-free 'product'. Unlike e.g. Motorola people, we aren't paid to work on this stuff, we are volunteers working on this stuff for fun in our free times. That includes the fact that we are free to choose what we want to work on, including working on e.g. ICS (if we, or in this particular case, Epsylon3) are interested in that or not working on anything at all for some time and devoting time to the new-born son instead (in this particular case, me at the moment).

    You also need to understand that some things are incredibly hard to fix (due to the complexity of the code) or near to impossible to fix (because we're dealing with binary blobs).

    Edit: I guess it boils down to one thing: Writing bug reports is nice and welcomed, but they shouldn't be understood as tasks, but as information to us (the developers).


    Talking about your particular examples:

    Is this happening with headset only? The report is lacking details.

    This is the 'dealing with binaries' case. If you feel like spending countless hours hacking smali disassembly code, go for it. If you feel like spending weeks writing a replacement: Even better.

    This is fixed in our nightlies since some time. I invested a number of hours debugging this in the complex video recording code, BTW, without even having personal interest in the video recording feature.

    Never encountered that issue so far, how am I supposed to debug this now?

    6. Screen locks after hang up the conversation if the talk was longer than time for screen off.
    It should go back to call log according to:
    Settings > Call settings > Always back to call log - checked.
    I think that's behaving as desired from the code. When you unlock the screen, you should see the call log.

    7. Battery lifetime
    8. Battery lifetime
    9. Battery lifetime
    Sorry, but without giving any particular battery drain scenario, ruling out e.g. apps or 3G usage etc., it's a waste of time to even talk about this. I personally got 2.5 to 3 days of battery lifetime from the stock ROM, and I get the same from CM7.
    This 'CM7 drains my battery' story really is getting old, especially without any data backing it.

    Maybe the devs should start a vote for the most annoying bugs the users want to have fixed? I'd rather like to see a very stable CM7 than another 5 months with a pre-beta CM9. Just my 2 cents.
    We don't need a vote, we need people helping with the code, devoting time and fixing bugs. See first paragraph ;)
    27
    maniac has branched Qkernel for gb :silly:

    Don't hold your breath ;)
    I'm experimenting with it, mainly to see whether I can get it working stably.
    At least it's booting already ;)

    Gesendet von meinem MB525 mit Tapatalk 2
    27
    Uploading new build.
    Main change is 720p rec for red lense.
    In defy+ hd rec enabled by default.
    In defy build hd rec available too, but not in media_profiles.xml.
    21
    Yes, there is still a kernel problem regarding the wifi module... But its the first bootable (and moddable so) kernel built from sources... for cm7

    to be continued....

    Sent from my GT-I9103 using xda app-developers app