Alcatel One Touch Fire 126.96.36.199 Brand new phone STR: Take Picture Open Twitter App Go to new tweet Image Gallery Select an image get the drop screen. Doesn't matter if you crop or not Hit the finish button, device freezes.
Can someone check if this reproduces on 1.1? Also, can we get a second confirmation this reproduces on 1.01 on a Buri 1.01 build?
This will be hard to test on 1.1 at the moment, since after you finish cropping a photo the device is rebooting (known issue). Will check 1.0.1 as well.
(In reply to Marcia Knous [:marcia] from comment #2) > This will be hard to test on 1.1 at the moment, since after you finish > cropping a photo the device is rebooting (known issue). Will check 1.0.1 as > well. Sorry this is happening on 1.2, checking 1.1 now.
Issue does not reproduce on Buri v1.1 build Environmental Variables Build ID: 20130830041201 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/2fb19341d934 Gaia: 577ab5105af418efc8ded00798fd3644b3dac674 Platform Version: 18.1 Issue reproduces on Buri 1.01 build Environmental Variables Build ID: 20130801233201 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/9c62297d11b0 Gaia: 054cdc27404e2daca91d3065d9783681032b2151 Platform Version: 18.0
For the 1.01 issue, can you include a logcat?
Created attachment 798022 [details] Twitter logcat.txt Logcat attached as per comment 5 for 1.01 issue.
One last thing before closing qawanted here - does this reproduce on a ZTE Open 1.01 build?
(In reply to Jason Smith [:jsmith] from comment #7) > One last thing before closing qawanted here - does this reproduce on a ZTE > Open 1.01 build? I can confirm it occurs with the 6-21 Spanish production build on ZTE device, using: Gecko Gaia fb2b088671f1cb28e2c678f7fdd56f4e79a8bf82 BuildID 20130621152332 Version 18.0
Only thing interesting in the logcat is: 08-30 13:54:20.409: E/msm7627a.hwcomposer(144): drawLayerUsingCopybit: copybit stretch failed Anyways, the best course of action here is to outreach to Twitter and tell them to disable uploading an image to twitter for 1.01 users, since it's causing freezes. Either that or if they can find a workaround that doesn't invoke a freeze, then that works too. Harald - Can you outreach to Twitter about this problem?
Just to give some background: Requested by carriers, bd and product, we fought long and on all levels to get WebActivity-enabled image upload implemented by Twitter for 1.0.1. So, if there is no workaround I will get in touch with Twitter to disable their WebActivity code for image upload. As 1.1 has file-inputs it will still work.
(In reply to Jason Smith [:jsmith] from comment #9) > Only thing interesting in the logcat is: > > 08-30 13:54:20.409: E/msm7627a.hwcomposer(144): drawLayerUsingCopybit: > copybit stretch failed IIRC, in recent rom, this error happens only on MozBuild ROM. Partner build do not generate this error. In which ROM did the error generate? Error log seems same as Bug 900029. It is fixed on Bug 905784. But it is only change to MozBuild, not partners.
But I am not sure Bug 905784 could affect this problem.
(In reply to Sotaro Ikeda [:sotaro] from comment #12) > But I am not sure Bug 905784 could affect this problem. This change save the RAM(shmem) is used for Layer's buffer. shmem can not be used for rendering by HwComposer, then "opybit stretch failed" appear.
End of the log, I found following logs. Comment 13 might affect to low memory. -------------------- 08-30 13:54:23.199: I/GonkMemoryPressure(652): Checking to see if memory pressure is over. 08-30 13:54:23.199: I/GonkMemoryPressure(652): Memory pressure is over.
Is this so severe that I need to ask Twitter to disabled upload? This is a core feature that was expected by carriers. If this isn't severe I'd recommend waiting for 1.1 release when file input is working.
(In reply to Harald Kirschner :digitarald from comment #15) > Is this so severe that I need to ask Twitter to disabled upload? This is a > core feature that was expected by carriers. If this isn't severe I'd > recommend waiting for 1.1 release when file input is working. It's a support escalation and it's causing a phone hang, so yes, this is severe enough. I'd ask to turn off the feature for 1.01 only by using UA detection to detect a 1.01 phone.
I ask them to disable it. I will recommend against UA detection as feature detection for file input is already done by Twitter and working great to have the correct upload for 1.1.