<div dir="ltr">On Sun, Mar 24, 2013 at 9:18 AM, Boris Borisov <span dir="ltr"><<a href="mailto:bugyatl@gmail.com" target="_blank">bugyatl@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">My latest device that I bought from BigLots is cheap tablet 4" with<br>
moderate specification written on the box but in reality the situation<br>
is different. As I mentioned in previous post some of the RAM is<br>
locked so there is only 340 MB available. CPU claims 1 Ghz but<br>
actually Android uses between 500 and 800 Mhz. Third thing is the SoC<br>
itself. Is not one of the ARM cores it is MIPS 74Kc something with no<br>
FPU so there is software FPU running by Linux kernel. I don't mind all<br>
issues but the latest is little frustrating. I have tried to download<br>
pocket version of Minecraft game ( Yes I have two kids ) and Android<br>
warned me " Portion of the game contain native code so it may not run<br>
at all on this system" . So it does not run :)<br>
<br>
This is not really a question but just thought. Isn't that some kind<br>
of security issue for Android, running native code, isn't that code<br>
running outside Dalvik VM. And using native code rejects all other<br>
platforms but ARM ...<br></blockquote><div><br></div><div style>The Android NDK (<a href="https://developer.android.com/tools/sdk/ndk/index.html">https://developer.android.com/tools/sdk/ndk/index.html</a>) exposes selected Android APIs to run in native code which offers the ability to reuse existing C code for CPU-intensive operations on Android. NDK itself supports ARM, x86, and MIPS instruction sets, but each NDK library obviously only works with one platform (and sometimes only specific versions of that platform). If the MIPS CPUs had the capabilities Minecraft needed and the developers were interested in targeting MIPS, they could build MIPS NDK libraries and ship them in the app as well. According to the Android security documentation (<a href="http://source.android.com/tech/security/">http://source.android.com/tech/security/</a>): "<strong style="font-size:13px;color:rgb(0,0,0);font-family:Arial,Helvetica,sans-serif;line-height:16.890625px">Android Application Runtime</strong><span style="font-size:13px;color:rgb(0,0,0);font-family:Arial,Helvetica,sans-serif;line-height:16.890625px">: Android applications are most often written in the Java programming language and run in the Dalvik virtual machine. However, many applications, including core Android services and applications are native applications or include native libraries. Both Dalvik and native applications run within the same security environment, contained within the Application Sandbox." In other words, the Android kernel enforces the sandbox on applications, rather than depending on the Dalvik VM.</span></div>
<div style><span style="font-size:13px;color:rgb(0,0,0);font-family:Arial,Helvetica,sans-serif;line-height:16.890625px"><br></span></div><div style><span style="font-size:13px;color:rgb(0,0,0);font-family:Arial,Helvetica,sans-serif;line-height:16.890625px">[Obligatory disclaimer since we're discussing Android: I work for Google and the views represented here are my own and do not represent Google. Also, for what it's worth, I don't work on Android and this is all just from my understanding from playing around with the Android SDK.]</span></div>
</div><br clear="all"><div><br></div>-- <br>David Tomaschik<br>OpenPGP: 0x5DEA789B<br><a href="http://systemoverlord.com" target="_blank">http://systemoverlord.com</a><br><a href="mailto:david@systemoverlord.com" target="_blank">david@systemoverlord.com</a>
</div></div>