Pipo M9 Pro RileyROM 2.5.2 KitKat

[amhonra]

filesystems is NOT a directory, it's a file.

My mistake, now I get it .... Sorry

[netRAT]

My m9 pro is finally becoming usable with this new kk ROM!
All previous jb ROMS where slow and unstable.
Looking forward to future improvements and optimisations!

[rrileypm]

I'm glad to hear from a satisfied user!!!!!! Thanks!!!!!!

Sent from my M6 using Tapatalk

[netRAT]

btw, has anyone successfully switched to ART?
When attempting on my tab it defaults back to dalvik after reboot.

Cheers.

[leeomendes]

My m9 pro is finally becoming usable with this new kk ROM!
All previous jb ROMS where slow and unstable.
Looking forward to future improvements and optimisations!

same here, no problems so far, all working! *No, no gps.. anyway, more useful than any 4.2.2 rom!

THANK YOU

[belier]

same here, no problems so far, all working! Even GPS...

3G version?

[knawnd]

nfs

Yes, but I also add nfs.ko.

I've just flashed that ROM. I can't load nfs module. I executed the following commands in Android Terminal Emulator:

$ su -

root@rk3188:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
root@rk3188:/ # lsmod
rk29_ipp 9957 1 - Live 0x00000000 (C)
mali 152580 50 - Live 0x00000000
ump 30472 23 mali, Live 0x00000000
rk30xxnand_ko 162075 0 - Live 0x00000000

root@rk3188:/ # insmod /system/lib/modules/nfs.ko
insmod: init_module '/system/lib/modules/nfs.ko' failed (No such file or directory)

root@rk3188:/ # ls -al /system/lib/modules/nfs.ko                              
-rwxr-xr-x root     root       357553 2014-01-05 00:12 nfs.ko

"nfs" is not mentioned in /proc/filesystems as well. So it seems nfs is not supported yet in that ROM and kernel needs to rebuild for that.

[Starcopy]

I included cifs.ko in the ROM, but these modules have not been tested with KitKat. You guys are doing that. It may be that we need to obtain a new set of ko modules, or find out if we need to do something other than insmod them in the boot.img to get them working in KitKat.

Have you tried using CifsManager to mount the nfs drive?

I have been using "andsmb" and "mountmanager". They do both work with CIFS and NFS. I can connect with al my devices on the internal network. So for me I can say, your afforts for the mounting issues are working. Great job.

[Bytebitten]

'Simulate secondary display' option - DON'T ACTIVATE

I don't know how I did it, but this is how it went;

If you activate 'Simulate Secondary Display' you will boot loop your device. So DON'T ACTIVATE ON ANY KIT KAT device for now!

But I still did...

After a lot of bootloops and resets, I was left with the image you see in the attachment.
Only way to get out of this mode with bootloops is with safe mode: which it done with the (missing) menu key :P



I read some post about the annoying power button behavior;
It seems a protection methode, press twice to unlock after long inactiveness. It's gone when just using the device.

[the5th2000]

btw, has anyone successfully switched to ART?
When attempting on my tab it defaults back to dalvik after reboot.

Cheers.

Are you using xposed framework? That changes the runtime back to dalvik.

I was actually all set to respond to you, "yes, I'm on ART..." I did change it to ART. My tablet rebuilds the cahche every time I power it on, for 76 apps, which is something my Nexus5 does on ART too, but only for two apps. It takes about 8mins and is a bit annoying, but i just turn the tablet on a few minutes beofre I need it. But then it occurred to me, I just assumed this was a bug and it was compiling the apps for ART every time I power on, but I've never actually chekced the runtime since I changed it. Maybe it's rebuilding the dalvik cache? I don't think so, i'm pretty sure it's ART, it certainly seems faster and smoother when opening apps.
The tablet is turned off at the moment, and I'm not waiting ages for it to boot up, but I'll check next time I have it turned on and let you know

[netRAT]

Are you using xposed framework? That changes the runtime back to dalvik.

I was actually all set to respond to you, "yes, I'm on ART..." I did change it to ART. My tablet rebuilds the cahche every time I power it on, for 76 apps, which is something my Nexus5 does on ART too, but only for two apps. It takes about 8mins and is a bit annoying, but i just turn the tablet on a few minutes beofre I need it. But then it occurred to me, I just assumed this was a bug and it was compiling the apps for ART every time I power on, but I've never actually chekced the runtime since I changed it. Maybe it's rebuilding the dalvik cache? I don't think so, i'm pretty sure it's ART, it certainly seems faster and smoother when opening apps.
The tablet is turned off at the moment, and I'm not waiting ages for it to boot up, but I'll check next time I have it turned on and let you know

Yep, that must be it.... Xposed appears to be the culprit.
Hope the dev is able to make it compatible soon. Left with the choice I'm inclined to stick with xposed for now. Tradeoff price is too high...

Cheers.

[pablog]

GPS

Does the RileyROM 2.5.2 KitKat supports GPS module on m9 pro 3g?

[belier]

With this ROM, when you leave the tablet on stand-by, and having selected the wifi option of being active only when charging, does the wifi stay on?
With Finless ROM wifi will never stop, what drains the battery.

[ludoke]

Does the RileyROM 2.5.2 KitKat supports GPS module on m9 pro 3g?

NO...NO...NO...READ...READ...READ...READ IF YOU CAN!!!!

[knawnd]

HDMI output problem

Has anyone faced on that ROM with problem to output signal from tablet to external monitor via HDMI cable?
I've just tried. First there was problem to get signal on the screen (I had to check and uncheck "Turn on HDMI" a several times in a raw otherwise I got "no signal" on external monitor). Second when I finally got android desktop screen on monitor it looked very bad: seemed scaled to 1920x1080 from some smaller resolution and with red and green horizonal lines. Choosing different resolutions and frequencies changed nothing (see attachment).

update: for completeness I have to mention that with same hardware (tablet, monitor and HDMI cable) I had no such problem on Pipo stock ROM.