Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062018-02-23T20:37:30ZReplicant
Redmine Replicant - Issue #1874 (New): Samsung Galaxy Note ll SIM Vodafone Spain, not detectedhttps://redmine.replicant.us/issues/18742018-02-23T20:37:30ZJUAN ROMERO BANDERAjohannes61@outlook.com
<p>Good evening: Sorry if the question is for you or not, is that it is my first consultation and I am somewhat disoriented. Today I received my Note ll and for more bad shadow does not detect the sim Vodafone of Spain, micro SIM, and I am quite green in this Replicant and also do not speak or understand English almost nothing, this is a translation, excuse me again. What can I do, since I have not found a similar question? I'm at your disposal. Receive greetings. Thank you.</p> Replicant - Issue #1659 (In Progress): The device pages don't warn about proprietary (and likely ...https://redmine.replicant.us/issues/16592016-03-06T19:25:05ZPaul Kocialkowskipaulk@replicant.us
<p>Most of the devices currently supported by Replicant (except the GTA04) support TrustZone, which is likely used on most devices. It is likely the reason why manufacturers enforce signed bootloaders while allowing unsigned kernels to run.</p>
<p>TrustZone TEE runs in parallel to and with greater privileges than the regular operating system (Replicant). Since it is proprietary and stored with/loaded by the (signed) bootloader, it is a great threat to both freedom and privacy/security. TrustZone is often used to allow decoding DRM contents without any possibility for the user</p>
However, since little is known about TrustZone TEE implementations (and exactly how it's loaded, how it's contacted), we should do some research about:
<ul>
<li>Whether there are TrustZone bindings in the kernel (e.g. related to DRM decoding).</li>
<li>How the (signed) bootloaders load the TrustZone TEE image and where it is stored. If not part of the bootloader image, knowing whether it is signed would be crucial.</li>
</ul>
<p>Looking at some documentation and known free implementations for that could help (ARM's reference trusted firmware). Some platforms and devices come with more documentation about TrustZone (e.g. i.MX53 and USB armory, Tegra X1).</p> Replicant - Issue #1605 (New): SIM card not recognized GT-i9300 (modem crash)https://redmine.replicant.us/issues/16052016-01-25T14:14:09ZAnonymous
<p>I have installed Replicant 4.2 (0004) on my samsung galaxy S3 and unfortunately my SIM card is not recognized.<br />Following your Wiki, the installation was correctly done. In attachment, the radio log file.</p>
<p>Please can you help me?<br />Thanks in advance</p> Replicant - Feature #1515 (New): Support for more video software-decoding codecshttps://redmine.replicant.us/issues/15152015-12-11T13:29:24ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>Support for free codecs such as Theora and VP8/VP9 would be nice.</p> Replicant - Feature #1497 (New): Missing audio scenarios for bluetoothhttps://redmine.replicant.us/issues/14972015-12-11T13:24:26ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>Missing scenarios are: (AD2P, calls, etc), dock audio.</p> Replicant - Feature #1485 (New): Samsung-RIL missing featureshttps://redmine.replicant.us/issues/14852015-12-11T13:04:56ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>Implement the missing parts of samsung-ril.<br />They are documented in the wiki, at <a class="wiki-page" href="https://redmine.replicant.us/projects/replicant/wiki/Samsung-RIL">Samsung-RIL</a></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 #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 - 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>