哪个好?猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

http://padhz.com/exynos-4412-tegra-3-rk3188.html

 

顺应今年新的发展趋势,本土四核方案近期相继亮相,不过由于种种原因的限制,包括全志A31、炬力ATM7029、联发科MT6589在内均没有采 用高性能的Cortex A9架构,并且CPU频率均比较低,给人感觉在性能上跟之前的高主频双核没有拉开明显差距。瑞芯微电子作为国内老牌芯片厂商,此次厚积而勃发,也在今年初 带来了自家的四核新平台,代号RK3188的这款处理器应用高主频A9核心,28nm的先进工艺也达到了业界尖端水准。近期,该方案产品已经开始出货,在 对其首发机酷比魔方四核豌豆2进行完整测试后,我们不妨再把它和猎户座Exynos 4412、英伟达Tegra 3这两款知名四核处理器进行下对比,看下RK3188跟同类高端平台的较量。此次对比选用的产品分别是酷比魔方四核豌豆2、蓝魔W42和谷歌Nexus 7。

 

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

三个方案的基本参数如上表所示,部分细节规格以此次对应产品实际表现为准,不完全代表方案所有可能的配置。从对比来看,发布最晚的瑞芯微 RK3188在制程方面更为领先。工艺精细度越出色,CPU的功耗相应也越小,同时元器件尺寸集成度更高,也有利于性能的发挥。当然,三者是不同时期的产 品,RK3188在这方面领先也是顺理成章的。但也应该看到,相比本土同期推出的全志、炬力四核,瑞芯微新方案能够率先采用28nm工艺,还是相当引人关 注的。另外,除了制程的领先,RK3188主频也要更高一些,不过暂时并没能达到官方标称的1.8GHz,也许后续固件可能实现这个频率。图形核心方面, 瑞芯微继续沿用同型号的Mali系列GPU,不过进一步提升了频率,在跑分时可以达到600MHz,可惜实际使用时限制在了400MHz。其它方 面,RK3188的二级缓存不算大,内存位宽只有32bit比较遗憾,但对性能的影响应该比较有限。另外,1080P的硬解码性能倒依然很主流。单从参数 来分析的话,RK3188很像是频率增强版的猎户座处理器,细节方面倒是有一些不同。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

以上是对应三款产品的规格,四核豌豆2具备全高清屏幕,因此在接下来的性能比较方面会略受些影响。当然另外两个平台也有全高清屏的机型,可惜条件所 限不方便拿来对比。因此,涉及到流畅度方面的体验仅供初步参考。顺便要说的是,在频率调节机制方面,RK3188的最低主频比另外两个要高一些,相对而言 不利于降低待机功耗。内存大小是瑞芯微所选产品更占优(另外两个方案也可搭配2GB内存),硬件占去的空间比较大主要是因为屏幕分辨率高,在低分屏产品上 可用空间则会大出很多。

硬件性能跑分对比:

跑分可以直观显示新平台硬件性能的优劣,下面还是按部就班的来看一看:

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

安兔兔测试的跑分结果当中,RK3188的多项数据都占据领先优势,这应该和它的高频率、大内存有直接关系。不过同时应该看到,安兔兔这款软件虽然 在安卓产品评测时广泛使用,但它的版本更新频繁,测试标准也经常修改,不同版本间往往结果会有不小差异,因此它的公信力也并不那么高,权且看看就可以。另 外,测试用的版本是安兔兔3.2.1,相比之前3.1版安兔兔跑分略有下降,前版跑分可破18000大关,这是测试工具本身引起的差异。并且分辨率对跑分 也有些影响,在低分屏的原道N80四核RK上面3.2.1版安兔兔跑分能达到17319。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

NBench可以比较好的反映CPU真实能力,在这项测试中,RK3188的分数也明显要超过猎户座跟英伟达四核。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

NenaMark是针对GPU的测试,这款测试工具会受分辨率的压力影响,但在此情况下,RK3188高频率的GPU仍然跑出了接近自身屏幕刷新率极限的高分数,分辨率稍低的N80四核RK这项测试可到61.6帧,更为强劲。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

GLBenchmark测试中,1080P Offscreen项目的结果是统一在1080P分辨率环境下的数据,方便在不同平台间直接对比。从结果来看,RK3188的三个分项测试整体处于领先位置。

单从跑分来看,RK3188基本上遥遥领先,这是它在采用主流Cortex A9架构的基础上,拥有高频率、大内存的直接结果,有力证明了RK3188的理论性能足够强劲,实际表现更多则看方案的优化了。比起低频率的Cortex A7或A5四核方案来说,瑞芯微四核从硬件基础上就占据了显著优势。

稳定性对比:

稳定性方面主要考验的是方案商的固件优化能力,具备Google官方支持的Nexus 7表现最为出色自然不用再多说,Tegra 3方案的产品曾经基本都是大厂的中高端机型,整体优化效果都还不错。猎户座Exynos 4412的产品表现则莫衷一是,此前三星自家Galaxy系列的四核平板或手机大多采用该处理器,整体表现还算比较好的。但国产的猎户座四核平板优化效果 要差不少,稳定性并不比新出来的RK3188平板好。就四核豌豆2这款产品来说,测试的几天内没有出现太大的BUG,倒是遇到过无线网络连接偶尔不正常的 小问题,而蓝魔W42多次出现锁屏界面操控失灵的现象。另一款RK3188平板原道N80四核RK整体运行也很稳定,证明了此次瑞芯微方案优化确实是比较 不错的。

流畅度对比:

流畅度虽是主观方面的体验,不过也可以量化成桌面帧率来对比。由于采用了全高清屏,RK3188的四核豌豆2桌面滑动帧率在50FPS左右,程序列 表界面还要低3~4帧。而Tegra 3的Nexus 7在桌面和列表界面的滑动帧率都能达到刷新率的极限,也就是稳定在60帧的水平,无疑要更加流畅一些。猎户座四核的蓝魔W42流畅度也比四核豌豆2要稍微 好一点,这则跟它的分辨率低有直接关系。在低分辨率的N80四核RK上面就流畅了很多,当然这不是说四核豌豆2用着就很卡,只是全高清屏的应用难免会降低 一些流畅度,在整体具备更高水平的横向对比中,还能看到存在进一步可改善的空间。

影响流畅度的除了分辨率、硬件性能和系统优化效果外,应该还跟触控IC有关,因此即便同样平台下,不同厂商的产品由于用料的区别,在流畅度上也会有 所不同。应该说,RK3188还是提供了很不错的硬件基础,但要想做得更加流畅一些,最好还是不要采用太高分辨率的屏幕(但不排除后续优化可以更好支持全 高清或视网膜屏产品的可能)。而除了系统优化之外,加强触控IC的品质也有利于流畅度体验的提升。

装卸软件速度表现:

一些体积较大的Android程序在装卸过程中往往会有一段等待时间,影响这方面的显然主要是CPU性能,此外内存带宽和速度应该也有一定关系。针对这个项目,笔者选用几款体积比较大的程序来做下测试。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

安装大型软件速度最快的是蓝魔W42,这应该是发挥出了它双通道内存的优势。RK3188的机型在此项对比中不占优势,除了卸载速度比较快外,安装 大软件的速度比不上Tegra 3机型,估计是它的内存速度影响。其32bit DDR3-1066内存运行频率为528MHz,跟Nexus 7所用Tegra 3的667MHz DDR3-1333还有些差距。

打开大体积PDF速度:

接下来看看用同款阅读器(智阅)打开大体积PDF的速度表现,并比较一下在快速翻页时的新页面加载延迟快慢。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

也许是受高分屏的影响,加之内存性能的限制,在打开PDF速度方面比起前两个方案也没有大的优势,但差别非常细微(要明显快于全志、炬力四核)。实 际体验中如果不是拿来做仔细比对,基本上感觉不到这三款产品间的差异。而且它的翻页加载基本没有延迟,配合全高清屏幕看电子杂志的效果非常好。

载入大游戏速度:

接下来再看看载入大型游戏的速度表现——

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

载入大游戏的速度基本相仿,不具备明显区别。针对速度方面的测试总体看出,由于内存带宽和高分辨率屏幕的影响,虽然同样是Cortex A9四核处理器,瑞芯微RK3188的速度表现跟NVIDIA和三星四核相比并不占优,但差别并不大,也体现出较高的水准。

网页性能:

在浏览器的效果表现方面,由于系统自带浏览器针对多核有所优化,因此四核平台的产品表现都还是不错的。Nexus 7的自带浏览器是Chrome,不支持Flash,所以跟后两者对比起来不太合适。猎户座四核的W42网页浏览流畅度跟RK3188的四核豌豆2基本相 仿,后者滑动时Flash显示前的延迟更长一些,可能是跟高分屏下的渲染有关吧。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测
土豆网的1080P原画视频在RK3188平板上可以流畅播放

说到网页性能,不得不说的就是在线视频能力。瑞芯微在这方面的优化一直比较好,在RK3188上面也体现了出来,在Flash模式下,优酷超清、腾 讯超清、奇艺超清视频和土豆1080P原画都可以流畅播放,但也存在播放时间一长不太稳定的情况(偶尔白屏或加载缓慢),不过整体要好过Tegra 3跟猎户座四核是毫无疑问的。

本地视频解码:

三款方案均支持1080P视频硬解码,此次对比只选用了一组1080P及以上规格的极限测试片。RK3188方案的四核豌豆2集成有专用的视频播放器,而前两个平台所选产品没有专门软件,测试时使用安装的MXPlayer。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

在视频兼容方面显然还是本土方案更强劲,即便RK3188相比此前双核的RK3066在解码方面没有变化,可是比起两个外来的方案支持度无疑更好。不过还没能达到目前全志、炬力支持4K视频的水平。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

在细节选项方面,RK3188方案做的也算比较完善,虽不及全志、炬力那般花哨,但也拥有基本的字幕、音轨切换等选项,并且从RK3066起率先加入了浮动窗口视频播放的功能,在RK3188上面也继续将其沿用。

游戏性能:

前面已经说过,四核豌豆2的GPU只有在跑分测试时才会飙到600MHz频率,平时则是运行在400MHz(当然也有一些更低的档位)。因此,这样 看起来,它的理论性能还是比猎户座Exynos 4412稍弱一点。加之此次对比选用的机型采用了全高清屏幕,很大程度上影响了实际游戏的流畅度,好在兼容性方面基本没有什么明显问题。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

四核豌豆2运行极品飞车17效果很棒,平均30FPS以上的帧率要超过Nexus 7的25FPS和W42的27FPS。在对比中,还测试了现代战争4、Gangstar Rio、真实赛车3等几款游戏,四核豌豆2的帧率要比另外两款机型低一些。由于三款产品的屏幕分辨率差异比较大,这对游戏效果有着很直接的影响,因此这个 对比不能完全说明三者的游戏性能高低,仅供简单参照。待后续RK3188机型更加丰富时,我们可以再来看看它在低分屏机型上的实际游戏表现会有多大提升。

功耗与发热:

RK3188处理器在制程工艺方面比另外两款芯片更加先进,这对功耗控制也有直接的作用。首先我们来看看待机耗电情况的对比,从18:00关屏进入待机状态,到第二天10:00唤醒屏幕查看剩余电量,之后的半小时都保持屏幕长亮的状态,每十分钟查看一次实时电量。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

根据唤醒屏幕后的几次观察结果来看,三个机器电量监测都比较准确,不会有电量突降的现象。从18:00到第二天10:00这段时间的耗电分别对应 2%、6%和11%,RK3188的产品并未在待机功耗上占得优势,也许跟它的CPU最低主频较高有关系,即便在待机情况下,四核豌豆2的CPU频率也会 运行在312MHz,明显高过Nexus 7的51MHz和W42的200MHz。同时,电路设计和元件本身的选用也会影响待机功耗。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

再看续航表现,首先是统一采用GLBenchmark自带的电池测试工具,它可以循环运行一段复杂的画面,基本可以代表重度使用环境下(如持续玩大 型游戏)的续航状况。测试前,将产品都充了一夜电,确保电量达到100%状态。在开着WiFi的状态下,将亮度设为最高,清理无关进程,然后进行测试。以 上是这三款产品的测试结果,最后一项功耗指数是采用电池容量(mAh)直接除以续航时间(h)得出的结果,相当于看一下每小时耗电多少mAh。

从结果来看,仍然是大厂机型Nexus 7的续航最长,这其实也是无可厚非的,毕竟CPU制程工艺只是其中一个影响因素。处理器频率、电路设计、屏幕配置、实际亮度、电池规格等方面都会造成影 响。这项测试对于四核豌豆2的考验显然会更大,它的屏幕分辨率比另外两款都要高出很多。尽管如此,单从时间上来看,四核豌豆2持续得仍然最长,即便套用此 次的功耗指数来看,也要比猎户座的W42更加省电。另外,在此前评测中单独对四核豌豆2的视频续航进行了测试,播放高码流的全高清影片能持续接近8个小时 半,表现相当出色。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

最后看下发热情况,以上温度数据是运行GLBenchmark续航测试半小时之后测得的结果,基本可以代表重度应用环境下的热量表现。不过这只是通 过红外温度计对主机表面测试的温度,显然要比芯片表面温度低不少。同时,影响温度表现的因素还有很多,除了芯片工艺外,模具的材质、散热结构设计等方面也 都会造成干扰。从初步测试的结果来看,RK3188机型只有37度,跟体温相仿,并不会觉得烫手。优化出色的Nexus 7温度也很低,只有本土猎户座机型测得的发热相对最明显。

总结:

本篇文章作为前段时间《国内外4款四核平板方案多方位对比》的延续,主要考察了最新亮相的RK3188方案跟两款主流四核A9处理器的表现异同,对比的项目也基本一致。

猎户座Exynos 4412、英伟达Tegra 3和瑞芯微RK3188对比评测

从多项对比结果来看,RK3188一定程度上展现了高主频Cortex A9的优势,采用28nm制程工艺也是很有远见卓识的选择,让其具备了叫板大厂高端芯片的能力。不过从规格解读的话,它的二级缓存稍低,内存带宽应对全高 清屏略显力不从心,GPU在跑分和游戏模式下频率差异也比较大。当然,对于一款新面世并将广泛普及的方案,它的优点也是很明显的,出色的续航和发热控制、 相比其它A7/A5四核更强劲的CPU性能、优秀的网页视频表现等等都值得肯定。瑞芯微方案一向在后期优化上比较出色,相信随着更多产品的登场,它的整体 表现会进一步提升。

原文出自PB派,以上内容仅供参考,实际体验最重要。

FW:AndrewDB, http://www.slatedroid.com/topic/41654-pre-alpha-03-ubuntu-linux-for-mk802-iii-ug802-mk808-ug007-imito-mx1/

http://www.slatedroid.com/topic/41654-pre-alpha-03-ubuntu-linux-for-mk802-iii-ug802-mk808-ug007-imito-mx1/

https://docs.google.com/file/d/0B-xyWOsjMDJPQS1vTVgwbmNTWXc/edit?pli=1

 

Posted 04 December 2012 – 11:07 AM

Title says it all. No hand holding at this stage as this is really for people who know what they are doing.
Note that this is the last of the pre-Alpha releases, intended for developers only. In around ten days I’ll post an Alpha 0.4 release with more/some support and simplified installation steps!
Folks, I can’t stress this enough: these pre-Alpha releases are only for people who have already cross-compiled the Linux kernel for an ARM device and are used to having things not working out-of-the-box.
And no, it won’t play movies nor will it run XBMC at this stage, and you can’t play any games with it yet (no OpenGL support).
Also, please at least read this first post COMPLETELY before asking any questions in this thread!

Present version is pre-Alpha 0.3
It has been tested on the UG802, Rikomagic MK802 III, MK808, UG007 and iMito MX1.

These are the features for the pre-Alpha 0.3 release:

  • Ubuntu 12.10 Quantal armhf based.
  • Easy to install and dual-boot (does not erase your Android installation).
  • HDMI 1920×1080 60Hz aka 1080p.
  • XFCE desktop.
  • Linux framebuffer consoles.
  • HDMI sound support. USB sound support.
  • Full array of cpufreq governors (I suggest the interactive governor).
  • USB mouse, keyboard and USB storage tested. Webcam tested by Alok.
  • nbench benchmark included (source code and binary) so you can check the real clock speed / performance of your Android stick.
  • OpenSSH server included and installed so you can use the Android stick headless.
  • Internal WiFi is not functional yet. You’ll need a $4 Realtek or Ralink USB Wifi dongle or a $5 USB 2.0 10/100 ASIX or SR9700 Ethernet dongle to connect to your network. A list of tested, known to be working adapters is available in the second post in this thread.

Download links:

The kernel kernel-0.3.img (<10MB) https://docs.google….QS1vTVgwbmNTWXc
The Ubuntu 12.10 filesystem linuxroot-0.3.tar.gz (700MB) https://docs.google….SU9hOWN4Z0JEVEE

IMPORTANT: kernel-0.3 can only be used with linuxroot-0.3, do not mix kernel and root fs versions.

Requirements:

To install:
– Rooted Android stick and SuperUser.apk installed.
– Terminal emulator in Android.
– microSD card (4GB, 8GB or 16GB) or USB key (4GB, 8GB, 16GB, 32GB).
– A Windows/Linux PC.
RKAndroidTool v1.35 (Windows program to flash RK3066 devices). This is the program you need to flash the kernel!

If you have installed a Finless Android ROM on your Android stick using the Flash method then you already have everything you need to proceed with the installation.
The zip file that includes Bob’s ROM also has the RKAndroidTools v1.35 and full, detailed installation instructions, so please get it!

To use Linux you’ll probably need:
– USB 2.0 hub
– USB keyboard and mouse.
– HDMI monitor (Full HD capable i.e. 1920×1080@60Hz – 1080p).
– An inexpensive USB WiFi b/g/n or Ethernet 10/100 adapter dongle.

Changelog

– pre-Alpha 0.1: Initial release, requires microSD card.
– pre-Alpha 0.2: Simplified boot requirements. Can now boot from a root partition labeled linuxroot on any mass storage device accessible at boot time e.g. a 4GB USB key, a 8GB SD card in USB card reader plugged into the USB hub, or a microSD card in the microSD card slot of your Android stick. Also can boot from a USB hard disk (tested by Alok).
– pre-Alpha 0.3: Tested on a wider range of RK3066 devices, kernel source removed to save space (if you need the kernel source you can still copy it over from the pre-Alpha 0.2 rootfs file). Added cifs-utils package (SMB). Recompiled kernel with different settings, supports NFS V3 and V4 client, NTFS read/write. Cleaned apt archive cache. Some extra artwork (wallpapers, icon themes) and various chess engines.

 

Forward: AndrewDB, Pre-Alpha 0.2 Ubuntu Linux for MK802 III / UG802 / MK808 (Superseded by Pre-Alpha 0.3)

http://www.slatedroid.com/topic/41453-pre-alpha-02-ubuntu-linux-for-mk802-iii-ug802-mk808/

https://docs.google.com/open?id=0B-xyWOsjMDJPZjUwNzFjZ1lqMTg

https://docs.google.com/open?id=0B-xyWOsjMDJPUnM4RlllWGpScXc

 

 

 

Posted 29 November 2012 – 03:11 AM
Title says it all. No hand holding at this stage as this is really for people who know what they are doing. In a few days I’ll post a proper Alpha with more/some support!
Folks, I can’t stress this enough: these pre-Alpha releases are only for people who have already cross-compiled the Linux kernel for an ARM device and are used to having things not working out-of-the-box.
And no, it won’t play movies nor will it run XBMC at this stage, and you can’t play any games with it yet (no OpenGL support).
Also, please at least read this first post COMPLETELY before asking any questions in this thread!

Present version is pre-Alpha 0.2
It has been tested on the UG802, Rikomagic MK802 III and the MK808.

These are the features for the pre-Alpha 0.2 release:

Ubuntu 12.10 Quantal armhf based.
Easy to install and dual-boot (does not erase your Android installation).
HDMI 1920×1080 60Hz aka 1080p.
XFCE desktop.
Linux framebuffer consoles.
HDMI sound support. USB sound support.
Full array of cpufreq governors (I suggest the interactive governor).
USB mouse, keyboard and USB storage tested. Webcam tested by Alok.
Kernel source code and full compiler toolchain suite included (gcc-4.7.2), so the RK3066 device becomes an autonomous mini development system.
nbench benchmark included (source code and binary) so you can check the real clock speed / performance of your Android stick.
OpenSSH server included and installed so you can use the Android stick headless.
Internal WiFi is not functional yet. You’ll need a $4 Realtek or Ralink USB Wifi dongle or a $5 USB 2.0 10/100 ASIX or SR9700 Ethernet dongle to connect to your network.

Download links:

The kernel ug802recovkernel.img (<10MB) https://docs.google….ZjUwNzFjZ1lqMTg
The armhf Ubuntu 12.10 root filesystem linuxroot.tar.gz (<1GB) https://docs.google….UnM4RlllWGpScXc

PLEASE MIRROR THESE FILES AND POST A LINK BELOW!

Requirements:

To install:
– Rooted Android stick and SuperUser.apk installed.
– Terminal emulator in Android.
– microSD card (4GB, 8GB or 16GB) or USB key (4GB, 8GB, 16GB, 32GB).
– A Windows/Linux PC.
– RKAndroidTool v1.35 (Windows program to flash RK3066 devices). This is the program you need to flash the kernel!

If you have installed a Finless Android ROM on your Android stick using the Flash method then you already have everything you need to proceed with the installation.
The zip file that includes Bob’s ROM also has the RKAndroidTools v1.35 and full, detailed installation instructions, so please get it!

To use Linux you’ll probably need:
– USB 2.0 hub
– USB keyboard and mouse.
– HDMI monitor (Full HD capable i.e. 1920×1080@60Hz – 1080p).
– An inexpensive USB WiFi b/g/n or Ethernet 10/100 adapter dongle.

Kernel Installation
(there are many ways to do this, here is a simple one that should take less than a minute)
– Install RKAndroidTools v1.35 on your Windows PC following exactly the instructions provided by Bob Finless.
– Download the kernel.img file to your Windows PC. Rename it recovery.img.
– Connect Android stick to your PC and run RKAndroidTool v1.35.
– Open the terminal emulator and “su”, then “reboot bootloader”
– RKAndroidTool should now detect Android stick.
– Flash only the new recovery.img to the recovery partition in the NAND. This takes 5 or 6 seconds, and your Android stick will immediately reboot into Android. THIS IS NORMAL.

Now that you have installed the Linux kernel in the recovery partition of your Android stick, you can dual boot Android or Linux.

To boot Linux, boot into Android, open the terminal emulator and “su”, then “reboot recovery”.

If you get the “dead Android bot” with red triangle, it means the Linux kernel image was not flashed correctly to the recovery partition. :nea:
Power off, power on, and repeat the procedure above paying attention to all details, and it should work.

Notes:
* There is only one user defined: user ubuntu password ubuntu. Needless to say, change the password ASAP!
* The kernel config is available in /proc/config.gz.
* The kernel source is in the home directory of user ubuntu.
* And you have the nbench benchmark in /root.

Rootfs Installation
(again there are many ways to do this, here is a simple one)
Requires a Linux PC.
If you don’t have a Linux PC, you can use the GParted LiveCD: http://gparted.sourc….net/livecd.php

1. Use GParted to create an ext4 partition of at least 4GB on a USB key or a microSD card. Label the partition linuxroot.

2. As root, extract the tarball, and copy (using cp -a) all the files in the extracted directory to the partition labeled linuxroot. This will create a Ubuntu root filesystem on the USB key or microSD card with all the proper permissions.

If when you boot Linux, you don’t get the LightDM login screen, it means you didn’t copy the rootfs files properly (probably you weren’t root) and they don’t have the correct permissions. :nea: Repeat the two steps above paying attention to the instructions!

Changelog

– pre-Alpha 0.1: Initial release, requires microSD card.
– pre-Alpha 0.2: Simplified boot requirements. Can now boot from a root partition labeled linuxroot on any mass storage device accessible at boot time e.g. a 4GB USB key, a 8GB SD card in USB card reader plugged into the USB hub, or a microSD card in the microSD card slot of your Android stick. Should even boot from a USB hard disk, but I haven’t tested this.

Sponsors

– Thank you Slatedroid user gsandiego for sponsoring a nifty Infrared Digital Thermometer that will allow me to take precise temperature measurements on the RK3066 running different loads at different clock frequencies!

This post has been edited by AndrewDB: 04 December 2012 – 05:11 PM

backup vps with dropbox storage

Create account at www.dropbox.com

Login to www.dropbox.com from web browser

Create app of dropbox from: https://www.dropbox.com/developers/apps

Copy App key & App secret from Dropbox result web page

Download shell upload tool from  https://github.com/andreafabrizi/Dropbox-Uploader

Remove config file of upload tool from home, if have:
~/.dropbox_uploader

Get Dropbox exchange token by launch upload tool:
dropbox_uploader.sh list

Copy Token key from ~/.dropbox_uploader to your application

 

 

***************************************

Update at 2014/11

When create app on Dropbox:

What type of app do you want to create?

==> Dropbox API app

 

What type of data does your app need to store on Dropbox?

==>  Files and datastores

 

Can your app be limited to its own folder?

==> Yes

 

Provide an app name, and you’re on your way.

==> project name

 

 

clone svn repository into git

## Install git-svn tool
# if CentOS
yum install subversion-perl

# if Ubuntu
sudo apt-get install libsvn-perl

## In git server, Create empty repo of exfat as my project

## Create Bare repo of /repo/exfat
cd /repo
git init --bare exfat.git
cd exfat.git
cp hooks/post-update.sample hooks/post-update
git symbolic-ref HEAD refs/remotes/trunk

## Clone svn with git-svn in work repo of /repo/svn/exfat
cd /repo/svn
git svn clone -s http://exfat.googlecode.com/svn /repo/svn/exfat
cd exfat
git config core.worktree /repo/svn/exfat
git gc

## Convert SVN Tag to Git Tag
/usr/local/bin/svn2git

##   Add svn ignore, if have
git svn show-ignore > .gitignore
git add .gitignore
git commit -m ‘Convert svn:ignore properties to .gitignore.’

# # Push git rep to bare repository
git remote add origin /repo/exfat.git
git push origin –mirror

## Put other svn branch into bare repo
# git branch -r
git checkout -t -b svn-trunk trunk
git push origin –mirror

git checkout -t -b svn-v1.0.x v1.0.x
git push origin –mirror

 

## Verify by checkout in workstation

cd /tmp/test
git clone ssh://git.zhenglei.net/repo/exfat.git
cd exfat

Adb driver on ubuntu 10.10

lsusb
sudo touch /etc/udev/rules.d/51-android.ruls
sudo chmod 755
gedit /etc/udev/rules.d/51-android.ruls
sudo /etc/init.d/udev restart
sudo adb kill-server
sudo adb devices

cat /etc/udev/rules.d/51-android.ruls

SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″, GROUP=”lzheng”
SUBSYSTEM==”usb”, SYSFS{idVendor}==”18d1″, MODE=”0666″, GROUP=”lzheng”
SUBSYSTEM==”usb”, SYSFS{idVendor}==”05c6″, MODE=”0600″, GROUP=”lzheng”
SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0600″, GROUP=”lzheng”
SUBSYSTEM==”usb”, SYSFS{idVendor}==”710d”, MODE=”0600″, GROUP=”lzheng”
SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0600″, GROUP=”lzheng”
# adb protocol on passion (Nexus One)
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1″, ATTR{idProduct}==”4e12″, MODE=”0600″, OWNER=”lzheng”
# fastboot protocol on passion (Nexus One)
SUBSYSTEM==”usb”, ATTR{idVendor}==”0bb4″, ATTR{idProduct}==”0fff”, MODE=”0600″, OWNER=”lzheng”
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1″, ATTR{idProduct}==”4e22″, MODE=”0600″, OWNER=”lzheng”
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1″, ATTR{idProduct}==”4e20″, MODE=”0600″, OWNER=”lzheng”
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM==”usb”, ATTR{idVendor}==”22b8″, ATTR{idProduct}==”70a9″, MODE=”0600″, OWNER=”lzheng”
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1″, ATTR{idProduct}==”708c”, MODE=”0600″, OWNER=”lzheng”
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM==”usb”, ATTR{idVendor}==”04e8″, ATTR{idProduct}==”6860″, MODE=”0600″, OWNER=”lzheng”
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1″, ATTR{idProduct}==”4e30″, MODE=”0600″, OWNER=”lzheng”
# adb protocol on panda (PandaBoard)
SUBSYSTEM==”usb”, ATTR{idVendor}==”0451″, ATTR{idProduct}==”d101″, MODE=”0600″, OWNER=”lzheng”
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM==”usb”, ATTR{idVendor}==”0451″, ATTR{idProduct}==”d022″, MODE=”0600″, OWNER=”lzheng”
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM==”usb”, ATTR{idVendor}==”0451″, ATTR{idProduct}==”d00f”, MODE=”0600″, OWNER=”lzheng”
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM==”usb”, ATTR{idVendor}==”0451″, ATTR{idProduct}==”d010″, MODE=”0600″, OWNER=”lzheng”
# adb protocol on grouper (Nexus 7)
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1″, ATTR{idProduct}==”4e42″, MODE=”0600″, OWNER=”lzheng”
# fastboot protocol on grouper (Nexus 7)
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1″, ATTR{idProduct}==”4e40″, MODE=”0600″, OWNER=”lzheng”

setup git server on centos 5

# Install Git on git.zhenglei.net
yum install expat-devel zlib-devel gettext-devel openssl-devel
unzip git-1.7.2.5.zip
cd git-1.7.2.5
make prefix=/usr/local install

## Create empty repository of test.git in /repo of git.zhenglei.net
mkdir /repo
cd /repo
GIT_DIR=test.git git init
cd test.git
git –bare update-server-info
cp hooks/post-update.sample hooks/post-update

## Access git.zhenglei.net via port XXXX over ssh
# Config ssh on workstation
echo “Host git.zhenglei.net” >>~/.ssh/config
echo “hostname git.zhenglei.net”>>~/.ssh/config
echo port XXXX >>~/.ssh/config

## Clone test.git
git clone ssh://root@git.zhenglei.net/repo/test.git

## Add README in local
cd test
touch README
git add README
git commit -m “add readme”

## Push back to server
git push origin master

Delete spam wordpress comment by script

bash tool to delete spam or un-approved comment in WordPress:

http://dl.dropbox.com/u/45095875/wp_comment_v1.sh

where:

WP_DIR is the directory where WordPress instaled.

Call WP_del_SPAM_Comment to remove spam comments

Call WP_del_UA_Comment to remove un approved comments.