NEW INFORMATION: Guys, I'm planning to implement some sort of donator's section. Slatedroid said that I can offer donators small perks as long as the Roms are identical. Donators will gain access to my CWM-Flashable versions of my MetaRom Series. Non-donators will not be disadvantaged in any way as they still get to use my MetaRom Series which is identical. Both the CWM version and RKBatchtool versions of my MetaRoms are identical. Only difference is the method of deployment. Donator's status will be awarded to users whom have donated an amount that is not too shabby but doesn't have to be too grand. Donators will gain access to my current form of CWM-zips for MetaRoms indefinitely. Once again Donation is entirely optional, both donators and non-donators will end up with identical copies of my MetaRoms.
The process of becoming a validated donator is as follows. Donate, PM me with email. I'll add you to a donator list and PM you with the download link. This download link is for you and you only. No sharing or creating mirrors would be allowed. In the event of a single breach, I will be terminating CWM-zips for MetaRoms. There will be a zero-tolerance policy.
If you have donated to me in the past, PM me with your paypal user and I'll communicate with you for further instructions
This is going to be the place where you can obtain a copy of my MetaRom series.
MetaRoms are meant to be lightweight, fast and functional. Anything fanciful that would contribute to bloat will not be added.
MetaRoms are also exclusive to the Pipo M8Pro. I personally maintain this rom for this device and this device only. This means there will be dedicated support for this device using this rom.
As for the inclusion of CWM, V0001 will not have CWM, future updates will likely have CWM included once I determine that there are significant improvements in having CWM included. Backup&Restore while nifty really isn't significant enough. There are NO real CWM-flashable roms at the moment, all I have seen so far is that CWM is only used for backup and restore and for the use of pseudo-cwm roms which are far from ideal. Until such a time when I can feasible implement CWM-roms, .img roms will be used
Note: MetaRoms have been tested to work and has been hosed down with bug spray. It still may have bugs though. please check post 2 to see if the bug has been listed before posting. Also, please be aware that I don't give a rat's behind about antutu or other benchmark scores. My emphasis is on real life performance rather than benchmarks. If you wish to ask about antutu or others, please create a separate thread.
CWM versus RKBatchTool
While RK3188 chips are generally "unbrickable" it's usually a hassle to "unbrick" your tablet
When using RKBatchTool, if you accidentally unplug the tablet mid-flash or if there's a power outage, you most likely will brick your tablet
CWM is a much much much safer way of flashing new rom, it's 99.99% un-interrupt-able.
RKBatchTool is a hassle, drivers issue and what nots
RKBatchTool ERASES all information on your tablet due to the method of flashing
CWM does not do so.
It is possible to flash my new CWM roms directly without using a PC (download and flash directly using tablet)
If something goes wrong, flash my CWM rom again
Updates using my CWM roms will preserve all existing data on your tablet.
Simply put, CWM is the epitome for android flashing
Features
Root disabled by default. (Can be enabled via "Root Enabler download link below")
Debloated of all unnecessary apps
Zipaligned to optimise ram usage
Build.prop mod to Samsung Galaxy S3 for greater PlayStore compatibility (pretty much complete playstore)
Disabled pipo bootanimation for faster boot up
Removed annoying "Pipo License"
Streamlined the initial boot, no more unnecessary wait time at 1st boot
Buttery smooth scrolling
% Battery Icon in status bar
Fine tuned Volume control
Tweak minimum auto brightness level
Extreme battery life. Idle drain is now capped at about 1% per hour
Instructions on how to flash using CWM (only valid for donators, read instructions for RKBatchTool if you're not a donator)
Make sure you have CWM
If you don't download my CWM tool and flash recovery
Copy CWM rom zip file to SD card
Reboot to recovery (If you don't know how, use adb reboot recovery command)
Swipe up and down to navigate CWM menu
Swipe to the left to select option in CWM Menu
You may choose to wipe or not
Select install from SD Card
Select CWM rom zip file
Wait
Wait
Reboot
All done!
Instructions on how to flash using RKBatchTool
WARNING: Flashing this repack will wipe your device including the internal SD card (aka Internal Storage), Strongly recommended that you remove external SD card
Download my RkBatchTool v1.6
Connect Pipo M8pro to PC (if PC does not detect download and install drivers from the tools section of this post)
Select the repack image in RkBatchTool
Press Switch
Wait till the pink box turns green
Press upgrade
Wait till its done
First boot might take a little longer than expected
Once booted, the Pipo M8pro will lag for a while as it is still initializing
Done!
If you require root, run EnableRoot.bat from the MetaRomRootEnabler after you have flashed the rom. (If your computer can't detect, download ADB drivers)
Thanks for your work. I've given it a go but I have a problem connecting to my Wifi router with your rom, it is failing the "obtaining IP address". I'll try it on another router later and see how that goes.
Please add information about stock rom version used for repack and kind of louncher
one of the most annoying thing is a very high level of minimal backlight in 4.22
It will be great if you can find a solution other than using Screen filter or Night Mode etc
Will V002 come with CWM ? Or, you could do as with RileyROM - make CWM or stock recovery, an option. Just replace the recovery.img file (Release your ROM with both recoverys included).
I'm wondering if the google maps / wifi-based location issue is related to lack of possibility to clear cache partition & dalvik cache after flash. If CWM was included, this could easily be confirmed/debunked.
Nope. I have fixed the Location Issue. It has nothing to do with cache and dalvik.
I will never include CWM by default into my roms as it is redundant at this point of time. But I will be including a CWM flash tool for those who want to flash CWM.
I want to enable root using ADB (from the Root Enabler package) but when I enable USB debugging, a GT-i9300 device shows up and no drivers are found. The drivers included in the OP does not work when installed with the i9300 device. Is there another set of drivers I have to use to get ADB working?
I might be interested in trying this out, but I'd appreciate that CWM flash. Makes working with my nandroid backups much easier, amd easier to swap between previously set-up roms for troubleshooting and comparisments.
Installed your rom yesterday and first impressions are awesome. Will do some more testing/playing around the next few days to see if i can/will upgrade your beer money.
I'm feeling confident on trying out this ROM, especially now that its clear I'll be able to flash CWM separately and do a nandroid first. However, I was a little put off when reading a previous post in this thread about the adb driver issue and the tablet showing up as a SGS3 (GT-i9300) when connected. I guess this is a consequence we'll have to live with, in order to get as much as possible out of the Play store. Adding those ADB drivers is no issue, but just so I understand this before flashing;
Will the the tablet show up as GT-i9300 when connected in debug mode? (This i suspect is true, from the previous posts).
2nd - will it still show as normal, RockShip unit, in bootloader mode? (for later flashing of other roms).
I guess anyone that have flashed the MetaRom (v002) and flashed/attempted to flash something else later, can answer this
Btw - @lambstone - I sent you a PM. Updated RKBatchTool (1.7) and RockShipUSB drivers (3.5) have been out for a while - and especially now with the SDK2.0 out, I guess its only a good thing to keep the drivers/tools bundled with the ROM, up to date. Zipped them up nice and tidy, and defaulted RKBatchTool to english language. Chinese is kept as an option though.
No, only ADB detects the device as i9300. BUT... it does not affect the usage of RKBatchTool at all.
Thanks for the link. I understand that the RKBatchTool 1.7 has been out for a while but Kaspersky detected a virus in them hence I went and used 1.6 as it is clean. I'll go see if your the version that you posted is clean as well.
I'm currently running your v002, and I must say I'm very pleased
I'm still having some wifi issues, but after connecting to some different networks around - I've concluded that the m8pro just won't play nice with my secondary router at home. Works fine with other wifi units, and conncting the m8pro to other networks including my primary router (1T1R) - just not really my 2T2R secondary router.
I haven't had any bells or whistles from Avast about this bundle, but I do seem to remember one of the random baidu links containing 1.7 triggering Avast. Not this one though.
i am discovering the existence of this metarom v2 in the same time than other roms, seems very impressive so i started to download right away... (i was already downloading the kasty-pipo-422 but yours will probably be first to be flashed)
i plan to upgrade with the 1.7 rockship flashing tool, i was just wondering if, in your experience, doing so from within a virtual machine (w7 runinng on an ubuntu host)
would do it fine or not ? do i still have to use the usb driver (by the way where is the safest place to download 1.7 flashing tool and usb driver ?) Do you know of linux apps for flashing android devices ?
Also could you please explain the role for the "adb" driver ? And as i am a real newbie concerning android, will you be kind enough to give a short explaination on the "cwm" (???) and other apps apparently used to do some backups (nandroid ???) it seems information is quite scatered so i feel a little lost (links to basic infos welcome !)
I will give you feedback and beer(s ?) after completing upgrade !
thanks
ps i had some difficulties downloading from mega, after several unsuccesfull tries, in the end it worked .
Really minor issue with the Global Time Widget. The Widget which was contained in the Stock ROM was all in Chinese, including the settings. When I checked it in your V2 ROM the selection list is now in English, however when the 2 clocks are set the display shows in Chinese. I am not able to change it to display English. Even changing the tablet default language has no effect on the clock.
As I said this is really minor. Not even sure I will leave it on the virtual desktop, as it doesn't allow very much customisation. It's only there now to fill up space.
Donated you some beer. (Marco)
Really like your Rom. Flashed it 3 hours after getting the tablet. ;-)
Very fluid and snappy!
Bug report:
1) System time issue. If the tablet is connected to wall charger , the time seems to freeze while charging.
Disconnected and again on battery, the time is totally wrong. (Simply stops)
Temporarily fixed it with clock sync, but I always must have a Wi-Fi connection...
Overriding the databases didn't help.
Any clue?
2) HDMI screen off doesn't seem to work. Tablet display never turns off. Like so the display time out.
3) Wireless display (in display options) is always ON (don't know if it is normal since I have used the stock only a few hours)
Would love to see a fixed version our maybe a workaround since I've loaded the tab with gigs of apps
M8 pro is a nice tab!
Greetings from Germany,
EDIT:
Of course I'll upgrade my donation if you help me out!
For (1), I have never noticed this issue, I'll investigate into this.
For (2), A solution would be to use this http://forum.xda-developers.com/showthread.php?t=1934495
For (3), Default should be ON but it does not affect your device at all.
UPDATES: Apparently Pipo are working on a new release with multi-window support. Next V0003 will have all these goodness.
Thank you so much for answering!
Hope your computer's will work again from crash...
we all know how much work/time it needs to setup everything again.
For my issues:
1) pending
2) WOW! SUPERBE! PERFECT SOLUTION. WORKS LIKE I NEVER EXPECTED AND BETTER!!!
Tablets display now TOTALLY turns off, by just connecting a HDMI cable. And turns on again when disconnected.
EXACTLY WHAT I'VE SEARCHED FOR. I have searched the whole net and found nothing like this.
Very good investigation.
You get more beer !
3) good to know. I thought it maybe drains my battery in the background.
Thanks for info.
Thank you very much for your work getting the best off this nearly perfect tablet.
I've tried a Vido N90FJDRK with "Retina" display before, and even it had double the resolution, it was half so good in usability, design and performance.
Giving me the HDMI solution will make me waiting happily on your V3 release!
I've been using that app for that solution since I got the tablet - but I mst say, I find it a bit disappointing that Pipo hasn't fixed this thing yet, especially considering how many updates the M8pro has gotten. - That, or take the "option" out until they can get it working.
Stock android launchers (AFAIK) don't support portrait view on home screen.
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Android Tablets Forum
551.1K posts
227K members
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!