Instagram issues?


kdisc98

Members
Jun 29, 2013
108
28
NO ISSUES WITH NO MIUI ROM - JUST IN MIUI ROM...and here the guys saying it's Xiaomi Hardware issue?! wired as h3ll
 

ubelai

Members
Feb 5, 2013
209
40
Hahaha.
Certain it has to do with the MIUI framework and the kernel of the Mi2(S).

A ported MIUI on my Galaxy S4 had no problems with the effect whatsoever!

Sent from my GT-I9505 using Tapatalk 2
 

eddie9684

Members
May 10, 2012
222
52
Hahaha.
Certain it has to do with the MIUI framework and the kernel of the Mi2(S).

A ported MIUI on my Galaxy S4 had no problems with the effect whatsoever!

Sent from my GT-I9505 using Tapatalk 2
i would add that it affects mi-1 too =(
 

jauling

Members
Jun 4, 2013
266
62
Not surprised, but 3.7.19 also has the FC when accessing the Following tab.

BTW, if anyone has any pixelation from uploading photos from your Mi2S to Instagram, I suggest turning off the 'Use High-Quality Image Processing' and see if that makes a difference. I just read about it today, so haven't yet tested, but this XDA thread seems promising:
http://forum.xda-developers.com/showthread.php?t=1887252

To give you an idea of the pixelation, take a look at this photo I took recently on Instagram:
http://instagram.com/p/bt1IXPrXdG
 

kdisc98

Members
Jun 29, 2013
108
28
Its bummer to know that this instagram crash is also on mi2s...
Instagram guys + Xiaomi guys saying it's only miui issue and not any other roms.
 

Animor

Members
Apr 21, 2013
143
28
Perhaps you should try to report the bug in miui.en forums.
But don't hold your breath for a fix. I've reported the Tango application bug (no audio from external speaker), and got no response... I hope you'll be luckier :)
 

jauling

Members
Jun 4, 2013
266
62
I say we post as much about this Instagram problem on the Facebook pages of MIUI and Xiaomi. I hope that the more annoying we are there, the more publicity and more likely it will get fixed!
 

eddie9684

Members
May 10, 2012
222
52
nope its no fixed, in my case i switched to CM 10.1 for my mi-1 i can use instagram and dont crash there.

people with cwm recovery and True dual boot cool switch back and foward between miui and cm
 

seyko1

Members
Jul 17, 2013
6
11
I tried like 5 modified miui versions including the original ones, still crashing everywhere :(
 

jauling

Members
Jun 4, 2013
266
62
Just upgraded to Instagram 4.1.0, which allows video file uploads. Still FC's on Following tab, not surprised. The video upload doesn't seem to want to work. I tried using a 90fps clip I made, and it just keeps failing. I dont really know what to make of these errors, other than something is screwed up. Maybe some kind of codec support? Running 3.7.26.

Code:
E/WVMExtractor( 3072): Failed to open libwvm.so
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 5
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
E/MM_OSAL ( 3072): ValidateAACFile failed
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
E/WVMExtractor( 3072): Failed to open libwvm.so
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 5
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
E/MM_OSAL ( 3072): ValidateAACFile failed
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
W/QComExtractorFactory( 3072): Didn't match the sniff <=== status = 1
E/OMX-VDEC-1080P(  175): In OMX vdec Constructor
E/OMX-VDEC-1080P(  175): vidc.dec.debug.ts value is 0
E/OMX-VDEC-1080P(  175): vidc.dec.debug.concealedmb value is 0
E/OMX-VDEC-1080P(  175): vidc.dec.debug.extradata value is 0
E/OMX-VDEC-1080P(  175): omx_vdec::component_init(): Start of New Playback : role  = OMX.qcom.video.decoder.avc : DEVICE = /dev/msm_vidc_dec
E/OMX-VDEC-1080P(  175): omx_vdec::component_init(): Open returned fd 179, errno 22
E/OMX-VDEC-1080P(  175): omx_vdec::component_init() success
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamVideoPortFormat: nPortIndex (0), nIndex (0), eCompressionFormat (0x7), eColorFormat (0x0), xFramerate (0x0)
E/OMX-VDEC-1080P(  175): Set_parameter: OMX_IndexParamVideoPortFormat: nPortIndex (0), nIndex (0), eCompressionFormat (0x7), eColorFormat (0x0), xFramerate (0x0)
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamVideoPortFormat: nPortIndex (1), nIndex (0), eCompressionFormat (0x0), eColorFormat (0x7fa30c03), xFramerate (0x69added0)
E/OMX-VDEC-1080P(  175): Set_parameter: OMX_IndexParamVideoPortFormat: nPortIndex (1), nIndex (0), eCompressionFormat (0x0), eColorFormat (0x7fa30c03), xFramerate (0x69added0)
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamPortDefinition: nPortIndex (0), nFrameWidth (1920), nFrameHeight (1088), nStride (1920), nSliceHeight (1088), nBitrate (0), xFramerate (0x1e), nBufferSize (2097088), nBufferCountMin (1), nBufferCountActual (2), bBuffersContiguous (257), nBufferAlignment (1), bEnabled (1), bPopulated (0), eCompressionFormat (0x7), eColorFormat (0x0)
E/OMX-VDEC-1080P(  175): Set_parameter: OMX_IndexParamPortDefinition: nPortIndex (0), nFrameWidth (1280), nFrameHeight (720), nStride (1920), nSliceHeight (1088), nBitrate (0), xFramerate (0x1e), nBufferSize (2097088), nBufferCountMin (1), nBufferCountActual (2), bBuffersContiguous (257), nBufferAlignment (1), bEnabled (1), bPopulated (0), eCompressionFormat (0x7), eColorFormat (0x0)
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamPortDefinition: nPortIndex (1), nFrameWidth (1280), nFrameHeight (720), nStride (1280), nSliceHeight (736), nBitrate (0), xFramerate (0x1e), nBufferSize (1433600), nBufferCountMin (11), nBufferCountActual (15), bBuffersContiguous (257), nBufferAlignment (1), bEnabled (1), bPopulated (0), eCompressionFormat (0x0), eColorFormat (0x7fa30c03)
E/OMX-VDEC-1080P(  175): Set_parameter: OMX_IndexParamPortDefinition: nPortIndex (1), nFrameWidth (1280), nFrameHeight (720), nStride (1280), nSliceHeight (736), nBitrate (0), xFramerate (0x1e), nBufferSize (1433600), nBufferCountMin (11), nBufferCountActual (15), bBuffersContiguous (257), nBufferAlignment (1), bEnabled (1), bPopulated (0), eCompressionFormat (0x0), eColorFormat (0x7fa30c03)
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamPortDefinition: nPortIndex (0), nFrameWidth (1280), nFrameHeight (720), nStride (1280), nSliceHeight (736), nBitrate (1721741624), xFramerate (0x1e), nBufferSize (2097088), nBufferCountMin (1), nBufferCountActual (2), bBuffersContiguous (33554433), nBufferAlignment (1924660636), bEnabled (1), bPopulated (0), eCompressionFormat (0x7), eColorFormat (0x0)
E/OMX-VDEC-1080P(  175): omx_vdec: Async thread start
E/OMX-VDEC-1080P(  175): omx_vdec: message thread start
E/OMX-VDEC-1080P(  175): send_command: Recieved a Command from Client
E/OMX-VDEC-1080P(  175): send_command_proxy(): cmd = 0, Current State 1, Expected State 2
E/OMX-VDEC-1080P(  175): send_command_proxy(): OMX_CommandStateSet issued
E/OMX-VDEC-1080P(  175): Current State 1, Expected State 2
E/OMX-VDEC-1080P(  175): send_command: Command Processed
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamPortDefinition: nPortIndex (0), nFrameWidth (1280), nFrameHeight (720), nStride (1280), nSliceHeight (736), nBitrate (1), xFramerate (0x1e), nBufferSize (2097088), nBufferCountMin (1), nBufferCountActual (2), bBuffersContiguous (1), nBufferAlignment (1), bEnabled (1), bPopulated (0), eCompressionFormat (0x7), eColorFormat (0x0)
E/OMX-VDEC-1080P(  175): Allocate i/p buffer Header: Cnt(2) Sz(2097152)
E/OMX-VDEC-1080P(  175): ION: alloc_data: handle(0xEBDCEC00), len(2097152), align(8192), flags(0x2000100), fd_data: handle(0xebdcec00), fd(0xb7)
E/OMX-VDEC-1080P(  175): ION: alloc_data: handle(0xEE495FC0), len(2097152), align(8192), flags(0x2000100), fd_data: handle(0xee495fc0), fd(0xb9)
E/OMX-VDEC-1080P(  175): Allocate done for all i/p buffers
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamPortDefinition: nPortIndex (1), nFrameWidth (1280), nFrameHeight (720), nStride (1280), nSliceHeight (736), nBitrate (1924660432), xFramerate (0x1e), nBufferSize (1433600), nBufferCountMin (11), nBufferCountActual (15), bBuffersContiguous (1924660432), nBufferAlignment (1773000228), bEnabled (1), bPopulated (0), eCompressionFormat (0x0), eColorFormat (0x7fa30c03)
E/OMX-VDEC-1080P(  175): get_parameter: OMX_GoogleAndroidIndexGetAndroidNativeBufferUsage
E/OMX-VDEC-1080P(  175): ION:non_secure_mode: nUsage 0xc0000000
E/OMX-VDEC-1080P(  175): Get_parameter: OMX_IndexParamPortDefinition: nPortIndex (1), nFrameWidth (1280), nFrameHeight (720), nStride (1280), nSliceHeight (736), nBitrate (190), xFramerate (0x1e), nBufferSize (1433600), nBufferCountMin (11), nBufferCountActual (15), bBuffersContiguous (1102245220), nBufferAlignment (1076343089), bEnabled (1), bPopulated (0), eCompressionFormat (0x0), eColorFormat (0x7fa30c03)
E/OMX-VDEC-1080P(  175): Use_op_buf:Allocating output headers
E/OMX-VDEC-1080P(  175): Use o/p buffer case - Header List allocation
E/OMX-VDEC-1080P(  175): GET_MV_BUFFER_SIZE returned: Size: 245760 and alignment: 8192
E/OMX-VDEC-1080P(  175): ION: alloc_data: handle(0xEC121340), len(3686400), align(8192), flags(0x2000100), fd_data: handle(0xec121340), fd(0xc2)
E/OMX-VDEC-1080P(  175): Failed to set the H264_mv_buffers
E/OMX-VDEC-1080P(  175): ERROR in allocating MV buffers
E/OMXNodeInstance(  175): OMX_UseBuffer failed with error -2147479552 (0x80001000)
E/ACodec  ( 3072): registering GraphicBuffer 0 with OMX IL component failed: -2147483648
E/ACodec  ( 3072): Failed to allocate buffers after transitioning to IDLE state (error 0x80000000)
E/MediaCodec( 3072): Codec reported an error. (omx error 0x80001001, internalError -2147483648)
I/BatteryStatsImpl(  510): Stop partial wakelock PendingMediaService.WakeLock(uid=10067, pid=3072) nesting 1
E/PendingMediaService( 3072): Media failed video render/upload
E/PendingMediaService( 3072): java.lang.IllegalStateException
E/PendingMediaService( 3072):  at android.media.MediaCodec.start(Native Method)
E/PendingMediaService( 3072):  at com.instagram.android.video.render.FinalRenderController.initVideoDecoder(FinalRenderController.java:233)
E/PendingMediaService( 3072):  at com.instagram.android.video.render.FinalRenderController.onInit(FinalRenderController.java:103)
E/PendingMediaService( 3072):  at com.instagram.android.video.gl.GLRenderContext.runSafe(GLRenderContext.java:209)
E/PendingMediaService( 3072):  at com.instagram.android.video.gl.GLRenderContext.run(GLRenderContext.java:133)
E/PendingMediaService( 3072):  at com.instagram.android.service.PendingMediaService.renderVideo(PendingMediaService.java:326)
E/PendingMediaService( 3072):  at com.instagram.android.service.PendingMediaService.handleVideoMedia(PendingMediaService.java:249)
E/PendingMediaService( 3072):  at com.instagram.android.service.PendingMediaService.handleMedia(PendingMediaService.java:190)
E/PendingMediaService( 3072):  at com.instagram.android.service.PendingMediaService.handleGoIntent(PendingMediaService.java:174)
E/PendingMediaService( 3072):  at com.instagram.android.service.PendingMediaService.onHandleIntent(PendingMediaService.java:153)
E/PendingMediaService( 3072):  at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
E/PendingMediaService( 3072):  at android.os.Handler.dispatchMessage(Handler.java:99)
E/PendingMediaService( 3072):  at android.os.Looper.loop(Looper.java:137)
E/PendingMediaService( 3072):  at android.os.HandlerThread.run(HandlerThread.java:60)
 

eddie9684

Members
May 10, 2012
222
52
as usual i cant even install instagram from google play.... sigh need to sideload the new version to try...
 

skido

Members
Jun 2, 2013
4
13
hello
Today I upgraded to Instagram 4.1.2 , and green "on burn" image bug, seems to be fixed!!!!
=) =) =)
 

kdisc98

Members
Jun 29, 2013
108
28
i can confirm:

In instagram version 4.1.2 there is no more green camera issue. ;)
BUT :mad:
still got this news resfresh FC / instagram close/back to home issue....(only in miui)
 

jauling

Members
Jun 4, 2013
266
62
It looks like 3.8.16 has FINALLY fixed the FC'ing when I load the 'Following' tab. I'm using Instagram 4.1.2. I've tried loading it and refreshing it, closing the app, then trying again also with reboots. Each time it hasn't FC'd! Hope everyone else is experiencing the same? :)

Forgot to mention, I have a Mi2S.. looks like Mi2A is still screwed...
 

kdisc98

Members
Jun 29, 2013
108
28
Nope..its aint fixed... Im usinf 3.8.16 and instagram 4.1.2 and its stl crashing when refreshing news tab of me or of everyone...even on a clean mi2a or mi2s from the box.
 

arnonymous

Members
Jun 13, 2013
31
18
Finally, for me, 3.8.16 fixed the issues.
No more FCs, so far.
And espcially before it.would fc when i had no internet connection(also vine had this issue). Now instagram works fine offline.

Sent from my Mi 2S