Android Tablets Forum banner
Cancel
Create thread New Forums

[ROM] GLASS ROM FOR RK3188 97RQ N90FHDRK U9GT5

Jump to Latest
284K views 920 replies 96 participants last post by  the_fanta  
#58 ·
My device is the Cube U9GT5 Retina RK3188.

I installed CWM and I confirm those glitches that pogodancer told us about. There is some lag in CWM and navigation is a bit tricky, just as pogodancer described. I could not mount usb too.
However wiping, installing zip, backup and restore worked like a charm.

I installed Glass v2 . It booted ok, but wifi was not working. Except for the wifi, I had some force closes (Rom Toolbox and Settings.apk). Unfortunately the lag is still there.
Image

I then restored (through CWM) my previous rom.

What do you guys think? Do i need Cube's original kernel so as to make wifi work in Glass v.2?
 
#72 ·
Very good news, that we now have a perfect CWM.

I have a silly question.

CWM is triggered if i hold volume up (+) and power button simultaneously for 2-3 seconds.

When i had the stock recovery image, that combination was triggering a black screen that was making my device visible to the RKTool, so I could flash roms etc.

How can I now use RKTool, with CWM installed? Maybe with ADB sideload?
 
#79 · (Edited by Moderator)
pogodancer said:
No fear! Everything works just like before.
Click to expand...
well i switched on the tablet with vol up & power button, and took me to CWM. While in CWM, the device was not recognised from RKTools.

anyway i installed CWM through the old "buggy" version of CWM, and now after wiping everything, i am installing darkrickpr's new rom
Image


Will report back soonish!
 
#81 · (Edited by Moderator)
pogodancer said:
You could install it with RKAndroidTool. I did install it with this tool over the old one. It's the faster operation.

Sent from my Teclast P88 / Jelly Bean 4.1.2 TNT
Click to expand...
well yeah i know, the problem is that i cant make RKTool to see my tablet, because VOL_UP & POWER Button takes me to CWM now.

Anyway, i installed the Dark's new ROM. One word : impressive!

I use nova launcher and with some tweaking scrolling is very responsive now.
I also set dpi to 264, (is a perfect match as device ppi is 264) so talk app looks great, and system settings are perfectly aligned on the very edges of the screen.
I turned off all animations from developer options too.

Well i like my tablet the way it is now. But i am pretty sure it can be further improved due to Dark's hard work. Let's also hope that the manufacturers will give more stock roms with better performance.

Thanks dark and pogodancer, my device is in a very good shape now
Image


I ll report back, with benchmark scores, and how Need For Speed Most Wanted runs.

UPDATE:

Geekbench
with interactive governor : 1314
with performance governor : 1396

CF - Bench
with interactive governor : 13589

Antutu
with interactive governor : 15416

Need For Speed Most Wanted : thery is some fps lag, it aint smooth, but it is playable. Maybe Malli is not clocked at 533MHz (who knows) or this game is not optimized for the chip. Or Retina Resolution impacts heavily this game.
Riptide GP : best graphics options set : Super smooth, runs excellent

Well CF-Bench score is pretty high. I believe there must be little thermal throttling on the RK3188 or because there is more room inside a tablet so it doesnt warm up fast. The score is higher than Samsung Galaxy S3. But CF-Bench is strenuous, and may trigger thermal throttling on phones, but not on tablets.

Geekbench score, is low. RK3188 should score around 1500 or more, but that was not the case. Geekbench unlike CF-Bench is a short on duration benchmark and may not trigger thermal throttling.

Antutu score, was ok, but keep in mind that the high resolution gets an impact on the gpu tests. Stock nexus 4, with a much faster CPU and GPU scores around 18500 with stock rom&kernel with 720p resolution. So I think Antutu runs well on RK3188.

Well i really believe that geekbench is the most reliable benchmark of the three. Imo Quadrant is rubbish. Moreover, geekbench is fast and may not trigger thermal throttling on phones, so numbers cant be easily comparable between phones and tablets. Geekbench also is multiplatform, and can compare your X86 pc performance with your phone/tablet.

I believe that RK3188 is a very good chip, much better that Tegra 3. Close to Exynos 4412. Maybe with new kernels, and better roms, we will see better potential. We also should see a kernel that runs at 1.8 GHz that is supposed this chip to run.
Can we somehow confirm that the GPU is indeed clocked at 533 MHz?

I am curious about thermal throttling. I will run Stability Test soon to see when thermal throttling kicks in.
 
#117 · (Edited by Moderator)
Wendal tools do extract the *.img file, it worked for me 100% under Windows 8 x64.

http://www.rockchipfirmware.com/developer-tools
RK3066/2918 Image Unpack/Repack Tool (Thanks Wendal from Slatedroid!)

you extract the contents of the zip, and you run the Runme.bat and then follow the instructions on the cmd window.
Those instructions are to press a button, move the img file that came from Vido inside the folder where that Runme.bat is. and to rename this img file, to wendal.img
when you do that, a folder will be created called Temp that will contain:

package-file, parameter, recover-script,RK3188Loader(L)_V1.04.bin,update-script
and a subfolder called image and containing: ext4 imgs, system.img, recovery.img,boot.img,misc.img

This system.img file is readable, and can be extracted with another tool called explore2fs (android kitchen contains this)
http://www.chrysocome.net/downloads/explore2fs-1.08beta9.zip
 
#165 ·
I am sure that the GPU has nothing to do with the UI lags.

a)Mali400 is a potent gpu (ARM's reference design), and it is clocked 33% - 50% higher on the RK3188. (533-600mhz)
b)The same gpu, can run 3d games on 2048x1536, so i am pretty sure it can handle 2D Android's transitions.
c)The lag in the UI is not the typical video lag we experience in games. It is the type of lag you see when you are out of RAM. Playstore is really laggy too.

anyway, i hope we will see a new glassrom soon, based on Visture's Firmware to see if there is any improvement.
 
#190 ·
i made a flashable zip for the AOSON Rom, and it installs fine.

No bluetooth and No wifi. Besides that, the rom is superfast, and there is no lag.

The original rom contains Bluetooth.apk that is fake, just 1 kb in size. I replaced that with a proper Bluetooth.apk from Yuandao rom but still I couldnt make the bluetooth to work.
I will now examine build.prop to see if there is a solution to the bluetooth and wifi issues.
 
#204 · (Edited by Moderator)
i tried the Aoson rom with the Cube U9GTV. There was no problem with the touch screen. The problem was with the bluetooth (we knew that the M33 has no BT) and unfortunately with the wifi. I do feel that there is no lag with the Aoson rom, because transitions are smooth. Recent button is faster too. If i had wifi working, i could do further testing, but currently i am unable.

anyway, kernel resides in boot.img . I think, but i am not really sure, that aoson,visture and vido roms, all have the very same kernel.
 
#207 ·
well I believe that the kernel is the same, on every rom, no matter it is the Vido/Cube/Aoson/Visture rom.

I am using glass v2a as a daily driver and had never any touch screen issues. Touch screen was working perfectly with any other rom i tested (vido,visture,aoson).

Anyway, i tried to fix wifi by replacing things in the Aoson rom, but in vain. Nothing worked. I am pretty disappointed right now
Image


pogo, http://goo.gl/gu2Iz here is my cwm flashable zip based on the aoson firmware and with my tries to fix the wifi (build.prop changed, some libs and confs added). Check it if you still get touchscreen issues.

btw, i opened boot.img, and then open ini.rc. There i found "insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200,266,400 mali_init_clock=50" this line. mali.ko needs a hex editor to view i think. Anyway, although I am not sure what this is, i am afraid that the kernels we have, run the gpu at a max frequency of 400mhz. Maybe i am completely wrong, but i really didnt like that line in the ini.rc.
 
#209 ·
Nope. I use the boot.img of Aoson Rom.

I make cwm flashable roms, with the Android Kitchen. In the Android Kitchen you gotta input 2 files , system.img and boot.img

When i was testing Aoson rom, i used the boot.img contained in the Aosom rom. Not the boot.img from some other rom.

Boot.img contains the kernel, the boot screen logo, the charging logo etc. Boot screen and charging might be different, among those roms, but i am pretty sure the kernel is the same. No matter which rom you use. However, for every rom i flashed through cwm, i used the boot.img contained in the rom i was trying at the time.
 
#213 ·
I am not sure which move made the bluetooth appear in settings. In the aoson rom, there were many files missing that were existent in other roms. So i added these files. I also replaced some wlan specific files that darkrickpr told me, but as you can see i had no luck with that too. For sure, bluetooth.apk is a dummy file in the aoson rom, and needs replase. I replaced settings.apk too.

I also have a Nexus 7 tablet, and every time i use my Retina RK3188, i feel a little sad about the performance.

I think that Cube should have released a new ROM by now. My last hope is on Cube.

Pipo M6, should release soon, but I really doubt that will be compatible.
 
Android Tablets Forum
posts
551K
members
228K
Since
2010
A forum community dedicated to Android Tablet owners and enthusiasts. Come join the discussion about collections, troubleshooting, displays, models, styles, reviews, software, hardware accessories, classifieds, and more!
Full Forum Listing
Explore Our Forums
New Member Introductions Android Tablet OS Apps Member Classifieds Android Tablet OS Games Android Tablets: Questions & Answers