Guest MadEye Moody Posted November 27, 2012 Report Posted November 27, 2012 Put a "HQ" video file on the Sd card and have a file manager installed, open the videofile and judge by the smoothness or the logcat if it uses OMX eh... HQ? can u give me a resolution, av codecs and container so that i can encode a video in that format and test?
Guest gbosh Posted November 27, 2012 Report Posted November 27, 2012 Resolution 640*480 Codec : H.264 Frames 30 Bitrate 566 Kb/s Container Quicktime Is the file I use for testing OMX
Guest MadEye Moody Posted November 27, 2012 Report Posted November 27, 2012 Resolution 640*480 Codec : H.264 Frames 30 Bitrate 566 Kb/s Container Quicktime Is the file I use for testing OMX thanks... i'll test it and post the results... flashing newly compiled ROM... lets hope my phone doesn't explode or anything ... :P
Guest MadEye Moody Posted November 27, 2012 Report Posted November 27, 2012 (edited) The file won't play - "Can't play this video." Logcat W/WVMExtractor( 1525): Failed to open libwvm.so E/Trace ( 1525): error opening trace file: No such file or directory (2) I/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] Non-Interlaced format detected I/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] AVC profile = 100 (High), level = 30 I/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] Enable frame by frame mode E/QCvdec ( 1525): Setparameter: unknown param 2130706434 W/OMXCodec( 1525): Failed to set frame packing format on component E/QCvdec ( 1525): Error: get_config Not Implemented I/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] video dimensions are 640 x 480 D/MediaPlayer( 1012): getMetadata E/QCvdec ( 1525): Unsupported profile, level, or widht, height E/QCvdec ( 1525): Unsupported clip E/QCvdec ( 1525): Unsupported profile, level, or widht, height E/QCvdec ( 1525): Omx Flush issued when vdec is not initialized yet. E/QCvdec ( 1525): Unsupported clip E/QCvdec ( 1525): FTB in Invalid State E/QCvdec ( 1525): Omx Flush issued when vdec is not initialized yet. E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 E/QCvdec ( 1525): FTB in Invalid State E/OMXCodec( 1525): [OMX.qcom.video.decoder.avc] fillBuffer failed w/ error 0x80000000 W/OMXCodec( 1525): Dropping OMX EVENT message - we're in ERROR state. W/OMXCodec( 1525): Dropping OMX EVENT message - we're in ERROR state. E/SoftMP3 ( 1525): mp3 decoder returned error 1 E/OMXCodec( 1525): [OMX.google.mp3.decoder] ERROR(0x80001001, 1) Video specs (encoded .mp4 file using VLC): VideoResolution 640 x 480 Aspect ratio 1.7771 Format H264 Bitrate 709 kbps Frames per second 29.833 Selected codec ffh264 EDIT : Then again tried to play the original file, and it played with a lot of yellow artifacts . logcat : D/HardwareRenderer( 1012): Disabling v-sync W/Adreno200-EGLSUB( 1012): SetSwapInterval() interval: 0 not set I/ActivityManager( 447): Displayed com.android.gallery3d/.app.MovieActivity: +140ms W/WVMExtractor( 1578): Failed to open libwvm.so I/OMXCodec( 1578): [OMX.qcom.video.decoder.avc] Non-Interlaced format detected I/OMXCodec( 1578): [OMX.qcom.video.decoder.avc] AVC profile = 66 (Baseline), level = 51 W/QCvdec ( 1578): ====================================================================== W/QCvdec ( 1578): Open Max Statistics W/QCvdec ( 1578): ====================================================================== W/QCvdec ( 1578): empty this buffer rate = NaN W/QCvdec ( 1578): empty this buffer total time = 0 W/QCvdec ( 1578): empty this buffer count = 0 W/QCvdec ( 1578): ====================================================================== I/OMXCodec( 1578): [OMX.google.h264.decoder] Non-Interlaced format detected I/OMXCodec( 1578): [OMX.google.h264.decoder] AVC profile = 66 (Baseline), level = 51 I/OMXCodec( 1578): [OMX.google.h264.decoder] Enable frame by frame mode W/OMXCodec( 1578): Failed to set frame packing format on component I/OMXCodec( 1578): [OMX.google.h264.decoder] video dimensions are 320 x 240 I/OMXCodec( 1578): [OMX.google.h264.decoder] Crop rect is 320 x 240 @ (0, 0) D/MediaPlayer( 1012): getMetadata I/OMXCodec( 1578): [OMX.google.h264.decoder] video dimensions are 720 x 576 I/OMXCodec( 1578): [OMX.google.h264.decoder] Crop rect is 720 x 576 @ (0, 0) I/SoftwareRenderer( 1578): Buffer color format: 0x13 I/SoftwareRenderer( 1578): Video params: mWidth: 720, mHeight: 576, mCropWidth: 720, mCropHeight: 576, mCropTop: 0, mCropLeft: 0 I/AwesomePlayer( 1578): we're much too late (0.50 secs), video skipping ahead I/AwesomePlayer( 1578): we're much too late (0.50 secs), video skipping ahead W/InputEventReceiver( 447): Attempted to finish an input event but the input event receiver has already been disposed. W/InputEventReceiver( 447): Attempted to finish an input event but the input event receiver has already been disposed. I/AwesomePlayer( 1578): we're much too late (0.61 secs), video skipping ahead W/TimedEventQueue( 1578): Event 91 was not found in the queue, already cancelled? D/ExchangeService( 1026): Received deviceId from Email app: null D/ExchangeService( 1026): !!! deviceId unknown; stopping self and retrying I/InputReader( 447): Reconfiguring input devices. changes=0x00000004 I/InputReader( 447): Device reconfigured: id=6, name='atmel-touchscreen', surface size is now 480x800, mode is 1 I/ActivityManager( 447): Config changed: {1.0 404mcc72mnc en_US sw320dp w533dp h294dp nrml long land finger -keyb/v/h -nav/h s.8 themeResource=null} W/Adreno200-EGLSUB( 1012): SetSwapInterval() interval: 0 not set Video spec: VideoResolution 720 x 576 Aspect ratio 1.7778 Format H264 Bitrate 2959 kbps Frames per second 25.000 Selected codec ffh264 Played exceptionally slow (may be because of the higher res and bitrate) So is OMX working or not, im confused Edited November 27, 2012 by MadEye Moody
Guest MadEye Moody Posted November 27, 2012 Report Posted November 27, 2012 (edited) The compiled (OSF2) zip and trimmed zip should get uploaded to http://db.tt/wZ2bpm0j within an hour. Keep in mind that this is an almost untested build. This is not like the build Daz gives. I have absolutely no idea what all changes are inside this, and if any of the changes (in progress ones) from CM, CFX or Daz himself would have any undesired effect. use at your own risk. And, I have no idea how to fix something if anything is found to be out of place, sorry. Edited November 27, 2012 by MadEye Moody
Guest MadEye Moody Posted November 27, 2012 Report Posted November 27, 2012 Anyone know how the compilation of P736E and P736V are handled? cm_blade2-userdebug seems to give P736V, so how are builds for P736E created ??? :unsure:
Guest gbosh Posted November 27, 2012 Report Posted November 27, 2012 Use '"P736E=1 brunch cm_blade2-userdebug" to compile for the Vivacity
Guest MadEye Moody Posted November 27, 2012 Report Posted November 27, 2012 Use '"P736E=1 brunch cm_blade2-userdebug" to compile for the Vivacity Thanks
Guest MadEye Moody Posted November 27, 2012 Report Posted November 27, 2012 Use '"P736E=1 brunch cm_blade2-userdebug" to compile for the Vivacity Any way of verifying if the output zip if E or V ?
Guest gbosh Posted November 27, 2012 Report Posted November 27, 2012 I think the outputfile will be named accordingly, but I am not sure
Guest MadEye Moody Posted November 28, 2012 Report Posted November 28, 2012 (edited) Use '"P736E=1 brunch cm_blade2-userdebug" to compile for the Vivacity This doesn't seem to give the E build. Opened up the build.prop of the output zip and in Additional build properties, it says ro.build.baseband_version=P736VB01 Also, the file name for both were the same : cm-10-20121128-UNOFFICIAL-blade2.zip Edited November 28, 2012 by MadEye Moody
Guest MadEye Moody Posted November 28, 2012 Report Posted November 28, 2012 So it's work ? :) Well, it does work, but haven't tested it much. I'll suggest that you wait for a day or two. I'm running the ROM and will report if I find any issues with it
Guest razzmataz1478 Posted November 28, 2012 Report Posted November 28, 2012 This doesn't seem to give the E build. Opened up the build.prop of the output zip and in Additional build properties, it says ro.build.baseband_version=P736VB01 Also, the file name for both were the same : cm-10-20121128-UNOFFICIAL-blade2.zip Did it work? If not try export P736E=1[/CODE] Before you brunch/lunch.
Guest MadEye Moody Posted November 28, 2012 Report Posted November 28, 2012 (edited) Did it work? If not try export P736E=1 Before you brunch/lunch. That too gives the same result /system/build.prop ro.build.baseband_version=P736VB01 Shouldn't it say P736Esomething EDIT : the build output has this line make -C kernel/zte/msm7x27 O=/home/renjith/android/source/cm10/out/target/product/blade2/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/renjith/android/source/cm10/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-" blade2_jb_p736e_defconfig [/code] so it might be working EDIT 2 : or it might not tried brunch again with export P736E=0, and that line was still there Edited November 28, 2012 by MadEye Moody
Guest -Mind- Posted November 28, 2012 Report Posted November 28, 2012 Well, it does work, but haven't tested it much. I'll suggest that you wait for a day or two. I'm running the ROM and will report if I find any issues with it Okay, Thanks ! :)
Guest MadEye Moody Posted November 29, 2012 Report Posted November 29, 2012 Well, it does work, but haven't tested it much. I'll suggest that you wait for a day or two. I'm running the ROM and will report if I find any issues with it Hi, I've been using the ROM I compiled and posted here earlier for about 2 days and the results are not satisfactory. So I will not recommend using it. Issues : A few of yellow artefacts (random rectangles) are seen when content on screen changes - this is almost unbearable when trying to play videos, the area where there is no video is dancing with yellow rectangles Camera app has a lot of artefacts as well - it has so much of it that a lot of times I was taking photos blindly. here the artefacts are not yellow in colour. There is also the tearing that we had in previous ROM as well. The only positive about the camera is that the preview is smoother (when not considering the artefacts) The battery life is very bad. I'm not a heavy user and used to get 16-20 hours, but with this build, I'm only getting about 6-8 (but this could change with a few days usage) The phone is very slow sometimes even when I overclocked to 902MHz. Some times it would take about a minute for the launcher icons to appear after sliding from one screen to another. Positives : Bluetooth headset is working - tried stereo mode Turning off GPS removes the GPS notification as well
Guest reedo_17 Posted November 29, 2012 Report Posted November 29, 2012 (edited) Hi, I've been using the ROM I compiled and posted here earlier for about 2 days and the results are not satisfactory. So I will not recommend using it. Issues : A few of yellow artefacts (random rectangles) are seen when content on screen changes - this is almost unbearable when trying to play videos, the area where there is no video is dancing with yellow rectangles Camera app has a lot of artefacts as well - it has so much of it that a lot of times I was taking photos blindly. here the artefacts are not yellow in colour. There is also the tearing that we had in previous ROM as well. The only positive about the camera is that the preview is smoother (when not considering the artefacts) The battery life is very bad. I'm not a heavy user and used to get 16-20 hours, but with this build, I'm only getting about 6-8 (but this could change with a few days usage) The phone is very slow sometimes even when I overclocked to 902MHz. Some times it would take about a minute for the launcher icons to appear after sliding from one screen to another. Positives : Bluetooth headset is working - tried stereo mode Turning off GPS removes the GPS notification as well I tried an updated Cm10 and i installed KonstaT's 4.2 camera app it removed the artifacts a lot better but panorama still has glitches/artifacts so try that. Also im using the cm-10-20121118-UNOFFICIAL-blade2-p736e.zip rom and im trying to get the google play store and it wont install ive tried the normal gapps, minimal gapps and pruned gapps and non give me the play store Edited November 29, 2012 by reedo_17
Guest Test007 Posted November 30, 2012 Report Posted November 30, 2012 I also tried this updated CM10 on my SFII and I must say that is very promising. For me battery life is great, however I don't using this phone daily too much (it is my spare phone). I using TPT variant 200 40 200 which is enough for ROM+GAPPS, anyway I using S2E which can move apps, private apps and dalvik cache to ext partition, so internal space for data is not very important. Also flash 4.2 camera app, it working very fast and removed any artifacts. I don't expect miracles but...overall phone working very smooth for me (using great SmartassH3 governor @200-825MHz) First time I update this rom from Dazzozo version CM10 and had some problems with root, but clean installation solves this problem. When I will have some more time (think about weekend ;-) ) then I'll try longer and deeper, anyway thank you for your work. At this moment rom working good for me and contains most of latest updates, also including screen off CRT animation - nice job MadEye Moody. I hope that you want continue developing this great ROM for Crescent :-) Thank you again.
Guest iharrybao Posted November 30, 2012 Report Posted November 30, 2012 have you guys ever noticed that it appears some yellow shadows on the status bar. and when i try to connect wifi, the password input window just shows on the status bar, just too small to see it,any idea to fix it? and many thanks to rom makers!
Guest ruyzalim Posted November 30, 2012 Report Posted November 30, 2012 y I using S2E which can move apps, private apps and dalvik cache to ext partition, hello my friend , can you help me? How do you create an ext partition to move all that stuff to there and how do you move them to there , my problem is that im allways running out of space! thank you very much my friend
Guest CurtisAndroidSF2 Posted November 30, 2012 Report Posted November 30, 2012 Just wondering where I can find the Konsta T 4.2 camera zip, can't seem to find his zip. Found one on AndroidCentral but I think it's a different one. Thanks
Guest reedo_17 Posted November 30, 2012 Report Posted November 30, 2012 (edited) http://www.modaco.co.../page__st__2220 it is the 5th post down :) It does make a big difference to removing the artifacts Edited November 30, 2012 by reedo_17
Guest CurtisAndroidSF2 Posted November 30, 2012 Report Posted November 30, 2012 http://www.modaco.co.../page__st__2220 it is the 5th post down :) It does make a big difference to removing the artifacts Thank you, much appreciated.
Guest reedo_17 Posted November 30, 2012 Report Posted November 30, 2012 Thank you, much appreciated. Just wondering what rom your flashing this onto
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now