[DEV][ROM] CyanogenMod 7.2.0 (Android 2.3.7)
- Thread starter Quarx
- Start date
-
- Tags
- 100% no motoblur crap! 2.3.4 beta cm7 defy cm7 defy cyanogenmod defy this ! epsilon3 epsylon3 also did this knightlys knightlys?nightlys knubs! mb525 motorola defy motorola should pay quarx quarx quarx > chuck norris quarx for president quarx for world emperor quarx is our hero quarx pown motorola quarx rocks quarx rules quarx the awesome quarx the defied messiah! quarx the sole deity
its a software limitation, the green lens can theoretically record even 1080p.
the common thought is that moto didn't succeed implementing the hd recording in the green lens and then switched to another lens - the red one.
http://www.ovt.com/products/sensor.php?id=65
i personally tried to find another android phone with same lens but had no success.
some or most iph**e4 have similar lens.
zte blade have same , and maybe this will help
http://boundarydevices.com/blogs/ov5642-camera-driver-under-android
The camera on most Blades (including the one I own) is a rather crappy 3 megapixel affair.
Certainly not the same sensor as found in the Defy!
Certain versions of the Blade have a 5mpix camera but I've not heard any particularly good comments about the image quality of this, either.
Certainly not the same sensor as found in the Defy!
Certain versions of the Blade have a 5mpix camera but I've not heard any particularly good comments about the image quality of this, either.
cm7-110601-2348-NIGHTLY-Jordan camera:
when I installed it I did wipe cache and wipe dalvik cache
(green lens)
first test: (I tested all resolutions)
start camera: 5M,4M - 2592x1936, the rest resolutions- 2048x1536
I made a recording on high then I changed back to camera: all resolutions - 2592x1936
I tried to a recording on hd then changed back to camera and played with the zoom: all resolutions - 2592x1456
second test: (I tested only 5M,4M,VGA)
start camera: 5M - 2592x1936, 4M - 2592x1456, VGA - 640x480
I made a recording on high then I changed back to camera: 5M - 2592x1456, VGA - 640x480
I tried to a recording on hd then changed back to camera and played with the zoom: when was at the 6x zoom camera froze and gave the force close, so I had to reboot the phone
third test after restarting phone: (I tested only 5M,4M,VGA)
start camera: 5M,4M - 2592x1456, VGA - 640x480
...................????????????????............................
sometimes zoom go even over 4x (green lenses) but not properly the image is seen, but it is as if does not zoom, it usually happens after change from record mode to shooting mode. sorry for English
when I installed it I did wipe cache and wipe dalvik cache
(green lens)
first test: (I tested all resolutions)
start camera: 5M,4M - 2592x1936, the rest resolutions- 2048x1536
I made a recording on high then I changed back to camera: all resolutions - 2592x1936
I tried to a recording on hd then changed back to camera and played with the zoom: all resolutions - 2592x1456
second test: (I tested only 5M,4M,VGA)
start camera: 5M - 2592x1936, 4M - 2592x1456, VGA - 640x480
I made a recording on high then I changed back to camera: 5M - 2592x1456, VGA - 640x480
I tried to a recording on hd then changed back to camera and played with the zoom: when was at the 6x zoom camera froze and gave the force close, so I had to reboot the phone
third test after restarting phone: (I tested only 5M,4M,VGA)
start camera: 5M,4M - 2592x1456, VGA - 640x480
...................????????????????............................
sometimes zoom go even over 4x (green lenses) but not properly the image is seen, but it is as if does not zoom, it usually happens after change from record mode to shooting mode. sorry for English
I just flashed the lastest nightly and found that pictures taken at any resolution captures an area bellow that is showed on the screen. Anyone had something similar?
i don't know, no benchmarks were done.
but it doesn't matter, cuz the one that you have is the only relevant option.
they say they couldn't work properly with 720.. just read it
ZTE Blade has OV3640 or OV3642. Defy with green lens has OV5642. It could takes picture, preview and video uses DVP (digital video port - paraller output interface) or MIPI. Defy and ZTE Blade uses DVP - it means that raw image from sensor is processing in ISP (sharpness, rotate, flip, colour, denoise) and next DVP take it and compress, set size, output format...
Changing in hex in file system/etc/mot_ise_imager_cfg.bin we can change register in ov5642 and can disable denoise - picture are much clear, set less compression - (unfortunately pictures over 2MB cause freeze or grey image) or set video/preview resolution - see dvp timing in pdf, set preview/output format like raw, rgb, you, set sharpness and much more.
Look at: http://xdaforums.com/showthread.php?t=1030603
Maringer - do you know what file in ZTE Blade set registers in OV364X??
Changing register in mot_ise_imager_cfg.bin and verification of results ocuppies much time, maybe anybody could write small program that access, read and write registers in OV5642 like i2c tools
I think that understanding registers in OV5642 is great step to 720p recording in defy with green lens.
Attachments
Last edited:
i just flash the latest nighty and i cant make or receive calls , the phone ring but when i try respond I can not hear my contact and he also can not hear me too
new build... i made one this night also which was fast... (not in Benchmarks but the UI seems better)
M
mariosanoguera
Guest
even faster ui? lol.. I think maybe its too fast hehe in case installing the last one I have to delete everything or can just install over the one before it? (or have to wipe data, cache dalvik battery stats etc..)
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
728CyanogenMod 7 for Motorola Defy
Status CyanogenMod 7.2.0 Stable:
Changelogs:
INSTRUCTIONS: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)
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
All the found issues, please send to GITHUB - https://github.com/CyanogenDefy/android_device_motorola_jordan/issues
Sources on github:
F.A.Q
Latest Google APPS
Download:
Official cyanogen builds
Epsylon Nightly Builds
Quarx Nightly Builds
Maniac103 Nightly Builds28Disclaimer: 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.
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?
I think that's behaving as desired from the code. When you unlock the screen, you should see the call log.
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.
We don't need a vote, we need people helping with the code, devoting time and fixing bugs. See first paragraph27
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
