Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062015-12-11T12:53:57ZReplicant
Redmine Replicant - Feature #1473 (New): BCM4751 GPS supporthttps://redmine.replicant.us/issues/14732015-12-11T12:53:57ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
It applies to the following devices:
<ul>
<li>Nexus S (I902x)</li>
<li>Galaxy S (I9000)</li>
<li>Galaxy Note (N7000)</li>
<li>Galaxy Tab 2 7.0 (P31xx)</li>
<li>Galaxy Tab 2 10.1 (P51xx)</li>
<li>Galaxy S3 (I9300)</li>
<li>Galaxy Note 2 (N7100)</li>
</ul>
<p>There is (very few) information about it at:<br /><a class="external" href="https://redmine.replicant.us/projects/replicant/wiki/BCM4751">https://redmine.replicant.us/projects/replicant/wiki/BCM4751</a></p> Replicant - Issue #1275 (New): Screen content (shortly) visible before unlockinghttps://redmine.replicant.us/issues/12752015-06-16T16:16:45ZMy Self
<p>This bug-report is an result of of the forum-issue: <a class="external" href="http://redmine.replicant.us/boards/9/topics/9633">http://redmine.replicant.us/boards/9/topics/9633</a>, where some more details could be found.</p>
<strong>Summary</strong>
<ul>
<li>Issue:<br />The device automatically locks after the configured countdown-time (over settings).<br />If the device will be activated again (by the buttons for example), the last screen content is shown for a short time (~ one second) before asking for the password (or PIN).</li>
</ul>
<ul>
<li>Suggestions:<br />- Android screenshots functionality in context of the missing proprietary accelerated graphics drivers.<br />- The framebuffer, which is only updated moments after the backlight goes up again.</li>
</ul>
<p>Because this "is a bug that is worth fixing", I opened that ticket.</p> Replicant - Issue #1215 (New): REQUEST_GET_NEIGHBORING_CELL_IDS error: REQUEST_NOT_SUPPORTEDhttps://redmine.replicant.us/issues/12152015-03-09T08:27:20ZThomas Kitchinmuleyryan@fastmail.fm
<p>D/RILJ ( 3052): [5838]> REQUEST_GET_NEIGHBORING_CELL_IDS<br />D/RIL ( 2545): 1 RIL request in the queue (1 pending, 0 handled, 0 unhandled)<br />D/RIL ( 2545): Unhandled RIL request: 75<br />D/RIL ( 2545): 0 RIL request in the queue (0 pending, 0 handled, 0 unhandled)<br />D/RILJ ( 3052): [5838]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED</p> Replicant - Issue #1149 (New): Image gets "broken" when putting samsung galaxy s3 in landscape po...https://redmine.replicant.us/issues/11492014-12-29T06:23:03Zcristi ghcristianghe2002@yahoo.com
<p>When using replicant 4.2 on Samsung Galaxy S3, the image on the display gets "broken" when swithcing from portrait position to landscape position.</p>
<p>It is still readable , but annoying.</p> Replicant - Issue #1125 (New): The "additional settings" option in the "phone" application doesn'...https://redmine.replicant.us/issues/11252014-12-19T03:23:37ZRichard "Cylus" Palmerc@cyl.us
<p>When selecting the "additional settings" option in the "phone" application's Calls settings menu, a popup displaying "Call settings error" and "Network or SIM card error." pops up. Upon confirmation, the user is returned to the settings menu.</p> Replicant - Feature #1017 (New): Sim ToolKit (STK) support is missinghttps://redmine.replicant.us/issues/10172014-10-30T16:19:39Zdl luddllud@riseup.net
<p>According to the <a class="wiki-page" href="https://redmine.replicant.us/projects/replicant/wiki/Samsung-RIL">Samsung-RIL</a> wiki page STK (Sim Toolkit) commands are either missing or disabled.</p>
<p>Without them one cannot use devices like the "magic" dual-SIM adapters, which could be a great way to circumvent the lack of Replicant support for a dual-SIM phone.</p> Replicant - Issue #1011 (In Progress): USSD codes don't workhttps://redmine.replicant.us/issues/10112014-10-30T16:13:11Zdl luddllud@riseup.net
<p>As reported on bug <a class="issue tracker-3 status-27 priority-27 priority-high3 closed" title="Issue: USSD codes don't work (Closed)" href="https://redmine.replicant.us/issues/32">#32</a> USSD codes aren't working on Replicant 4.2. I get:<br /><code>Connection problem or invalid MMI code.</code></p> Replicant - Issue #939 (Feedback): Phonecall terminates without busy signalhttps://redmine.replicant.us/issues/9392014-06-16T09:45:27ZJan Prunkjanprunk@gmail.com
<p>Hi Paul,</p>
<p>I occasionally experience the bug on the S3 during calling.<br />Sometimes, when I start the call and my phone rings for about some random seconds 5-20 sec. the call gets silently terminated.<br />It doesn't provide a busy signal or anything it just hangs up the call. I assume that it happens when the other side cancels my phonecall<br />during when their side is ringing. I have the 4.0.4 replicant build.</p>
<p>Kind regards, <br />yang</p> Replicant - Feature #837 (New): Replicant Native Development Kit (NDK) build and releasehttps://redmine.replicant.us/issues/8372014-02-20T14:07:34ZAnonymous
<p>It is great to have the Replicant SDK available for download. However, to build some native apps, the NDK is required. Any chance the replicant project can publish a NDK built from replicant sources?</p> Replicant - Feature #351 (New): Camera and video recording supporthttps://redmine.replicant.us/issues/3512012-12-02T22:54:43ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>Playing a youtube video seem to fail....very similarly from the camera failure<br /><pre>
E/OMXCodec( 807): Attempting to allocate OMX node 'OMX.TI.DUCATI1.VIDEO.DECODER'
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetHandle:204
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
E/OMXCodec( 807): Successfully allocated OMX node 'OMX.TI.DUCATI1.VIDEO.DECODER'
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
E/OMXCodec( 807): [OMX.TI.DUCATI1.VIDEO.DECODER] Video O/P format.eColorFormat 0x40b9e1b1
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetConfig:564
I/OMXCodec( 807): [OMX.TI.DUCATI1.VIDEO.DECODER] video dimensions are 320 x 180
I/OMXCodec( 807): [OMX.TI.DUCATI1.VIDEO.DECODER] Crop rect is 320 x 180 @ (0, 0)
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SetParameter:348
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_SendCommand:644
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] eError = 0, line 1037
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetParameter:419
D/DOMX ( 807): ERROR: [DBG] eError = 0, line 1116
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_UseBuffer:1080
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync write errno error 22
D/DOMX ( 807): ERROR: DOMX Write failed 0xffffffff -1
D/DOMX ( 807): ERROR: failed check:status >= 0 - returning error: 0x81001 - Write failed
D/DOMX ( 807): ERROR: RPC function returned error 0x81001
D/DOMX ( 807): ERROR: [DBG] eError = -2147479551, line 1192
D/DOMX ( 807): ERROR: PROXY_UseBuffer in PROXY_AllocateBuffer failed with error -2147479551 (0x80001001)
E/ion ( 807): ioctl -1073460991 failed with code -1: Invalid argument
E/OMXNodeInstance( 807): OMX_AllocateBuffer failed with error -2147479551 (0x80001001)
E/OMXCodec( 807): [OMX.TI.DUCATI1.VIDEO.DECODER] allocate_buffer_with_backup failed
D/DOMX ( 807): ERROR: [DBG] RPC_sendPacket_sync RPC_GetState:700
F/libc ( 807): @@@ ABORTING: HEAP MEMORY CORRUPTION IN dlfree
F/libc ( 807): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
</pre></p>