Pipo M9 Pro - Finless 1.4 ROM

[Starcopy]

You can do that yourself by a simple edit to the build.prop file.

Thanks, it solved my problem.

[Finless]

The reason I put Samsung in build.prop is because it is the MOST POPULAR device and thus far more apps show up in Google Play than would with it saying Pipo. So you cant have your cake and eat it too

Bob

[colinabroad]

Samsung Vs Pipo ?

The reason I put Samsung in build.prop is because it is the MOST POPULAR device and thus far more apps show up in Google Play than would with it saying Pipo. So you cant have your cake and eat it too

Bob

As Bob says, is there a contest? this is simply the name by which Google interrogates the device and decides what apps you are allowed to see or not (from my bitter experience on Google Play) Being in China I am blocked from most apps by default, so being able to 'pretend' my device is something else is a massive bonus. Change your build prop if you want, it is not so difficult - certainly not as difficult as getting the windows drivers working!

[colinabroad]

Open VPN

I use a VPN app called Private Internet Access

https://play.google.com/store/apps/details?id=com.privateinternetaccess.android

I think the underlying code is based off of OpenVNC. Although I'm not certain.
With all the custom Pipo M9 ROM's I have tested, none been able to make a connection. The app gets to authentication and then dies. My searches turned up a few others having the same issue and the answer has always been enable tun.ko
See the first post on May 2

https://www.privateinternetaccess.com/forum/index.php?p=/discussion/1023/tutorial-how-to-use-android-pia-vpn-app-apk-inside/p1

With all that said I have been playing around with getting tun.ko installed using tun.ko installer from Play. And I have tried the earlier suggestion, post 77 in this thread, about placing a file named 92tun in the /system/etc/init.d directory. I still unable to get it to connect.

There is still some type of dependency missing from this rom that is keeping my VPN app from from connecting. I guess I also may have not installed the 92tun file correctly but I think I got it right.

If you think the md4.ko could possibly have some positive results with using VPN's, then yes please include it.

Thanks for the rom work.

Brilliant to hear Bob is adding tun.ko to the next release! I was going to wait for Kit Kat, but may well jump in on this as I cannot operate here in China without my VPN. Yes Private Internet is using the same software as Open VPN - jump over to RileyROM 2.1 and you will see my replies to several people with the same problem - basically you need a VPN open in order to load the tun.ko from the internet - defeats the object I know, but if you can run a VPN on pptp or from another device with wifi hotspot you can get the module loaded - trouble is you need to load it after every reboot - NOT such a problem now with Bobs pretty stable ROM - even less of a problem if it is embedded in - I am looking forward to 1.5!

[Starcopy]

As Bob says, is there a contest? this is simply the name by which Google interrogates the device and decides what apps you are allowed to see or not (from my bitter experience on Google Play) Being in China I am blocked from most apps by default, so being able to 'pretend' my device is something else is a massive bonus. Change your build prop if you want, it is not so difficult - certainly not as difficult as getting the windows drivers working!

On one hand your right, but here in the Netherlands Are severall apps that won't work on a Samsung device. So thats why I have to change the name. Also, there are alternatives for Googleplay where I can get the apps who won't show up anymore. it is just the stupid fact that an app say's: Sorry I can't install on a Samsung device. But with the tip from Rodentkj I could change it myself. Problem solved.

On the other hand, Riley changed it from Samsung to Pipo in the M8pro rom because a lot of people asked for it. So there must be more to it than just a name.

[manao]

Hey All, the suggestion from SS900 , to help stop the evil multi window feature from rearing its ugly head ( basically it keeps turning itself on) did not work. The suggestion was to ADD a line in the build.prop : ro.rk.multi_window=false , unfortunately this did not work. It is still enabling itself.
It is truly annoying! The work around is toggle in on, then off.
Any suggestions or comments with be very much appreciated!
Note ; this mainly occurs on startup or a reboot, if that is a help..

With this modification you will delete completly the multi-window but no more hiddable bar...
Look at your build.prop the line "ro.rk.systembar.tabletUI" and change the value to true. Save and reboot. You can try. If you want revert, change the value to false. Save and reboot

You can use the following lines in build.prop
* for split top-notification bar: set ro.rk.systembar.tabletUI=false
* for bottom-notification bar: set ro.rk.systembar.tabletUI=true
* reboot after changing the value.

With the value "true" you will have only the bottom-notification bar (like 4.0 and 4.1 - no top notification bar) and no more hiddable bar .

https://play.google.com/store/apps/d...p.editor&hl=fr

[madsega]

Flashing issue

Hey guys,

From what I've read, this looks like a great ROM to have on your Pipo.
I tried flashing the M9 Pro, followed the tutorial from Read-me file to the letter, everything was going great.
The Pipo rebooted and started formatting data, cache, mnt/sdcard. This is where the problem lies.

It's been at the formatting card step for over 25 minutes. Did I do something wrong? What do I have to do now? I don't want to reboot it to brick it or something?

If you have any advice, please let me know.
Recorded a bit of the process, if you think it will help I will upload the video.

Forgot to say: I have Pipo M9 Pro Wifi only, which was previously (5 days ago) flashed with latest update from Pipo website (PiPO M9pro_software_3G&WiFi_english version_20131120)

Thank you.

[ludoke]

Hey guys,

From what I've read, this looks like a great ROM to have on your Pipo.
I tried flashing the M9 Pro, followed the tutorial from Read-me file to the letter, everything was going great.
The Pipo rebooted and started formatting data, cache, mnt/sdcard. This is where the problem lies.

It's been at the formatting card step for over 25 minutes. Did I do something wrong? What do I have to do now? I don't want to reboot it to brick it or something?

If you have any advice, please let me know.
Recorded a bit of the process, if you think it will help I will upload the video.

Forgot to say: I have Pipo M9 Pro Wifi only, which was previously (5 days ago) flashed with latest update from Pipo website (PiPO M9pro_software_3G&WiFi_english version_20131120)

Thank you.

That's a bad situation,reboot is indeed risky but a PiPo is nearly impossible to brick.
You should try something ,in this state it's unusuable and when it's bricked it's the same.
I have no idea what would happen if reboot,normally this results in a brick when interrupting the update process.
When you leave it in the process of formatting sd card the battery will run flat with the same result.

[madsega]

Thank you for your reply. I don't know what to do at this point.
Was I supposed to remove the USB cable after the flashing was over (before reboot) ?

Anyhow, here is a picture of how everything went down:

http://www.screencast.com/t/wOemfjCXjA

[ludoke]

Thank you for your reply. I don't know what to do at this point.
Was I supposed to remove the USB cable after the flashing was over (before reboot) ?

Anyhow, here is a picture of how everything went down:
http://www.screencast.com/t/wOemfjCXjA

The flashing was not over because it was formatting sd card.
In my case!!! i pressed the rest button at this point and try again,please don't'shoot me when it goes wrong,but when you leave it this way the battery will run flat and it could be it whon't power up again

[ludoke]

Thank you for your reply. I don't know what to do at this point.
Was I supposed to remove the USB cable after the flashing was over (before reboot) ?

Anyhow, here is a picture of how everything went down:
http://www.screencast.com/t/wOemfjCXjA

Did you erase IDB before flashing the rom, i can't see that step in the recording ?
In youre recording is in the flashtool the first box above schecked while i start up the the flashtool whitch is in the Finless folder this box is unchecked.
Maybe Bob can clear this out but watch out your battery is thicking and when in update procees it consumes much power,so if iwhere you i presset the reset button and see what happens.

[madsega]

Did you erase IDB before flashing the rom, i can't see that step in the recording ?
In youre recording is in the flashtool the first box above schecked while i start up the the flashtool whitch is in the Finless folder this box is unchecked.
Maybe Bob can clear this out but watch out your battery is thicking and when in update procees it consumes much power,so if iwhere you i presset the reset button and see what happens.

Yes, I erased NAND (IDB), out of 8192 it got to 8181 before the OK status. I think that's ok since it says "It MUST count up to 8192 or very close to it".

Anyhow, I followed your lead and hit the reset button. It clicked louder than any previous boot clicking. Then it just displayed the Android thing, belly-up with an error mark. I said "F**k it, it's bricked" and put the tablet aside and watched a movie.

Now that the movie is over and checked on the tablet again, look like everything is in order haha.

Here is the settings screenshot http://imageshack.com/a/img163/3015/z5j1.png

What do you guys make of this?

Thank you.

[ludoke]

Yes, I erased NAND (IDB), out of 8192 it got to 8181 before the OK status. I think that's ok since it says "It MUST count up to 8192 or very close to it".

Anyhow, I followed your lead and hit the reset button. It clicked louder than any previous boot clicking. Then it just displayed the Android thing, belly-up with an error mark. I said "F**k it, it's bricked" and put the tablet aside and watched a movie.

Now that the movie is over and checked on the tablet again, look like everything is in order haha.

Here is the settings screenshot http://imageshack.com/a/img163/3015/z5j1.png

What do you guys make of this?

Thank you.

You have Finless rom now,thats all,the louder clicking is normal.
Like i said ,PiPo is brick proof.

[madsega]

You have Finless rom now,thats all,the louder clicking is normal.

That was a weird/unique way of having the ROM installed

Now, what remains to do is opening the Pipo and fix the Wifi hardware problem (as it can't stay connected for more than 5 minutes)

Thank you for all your help,
Cheers

[ludoke]

That was a weird/unique way of having the ROM installed

Now, what remains to do is opening the Pipo and fix the Wifi hardware problem (as it can't stay connected for more than 5 minutes)

Thank you for all your help,
Cheers

Have you done a factory reset after flashing the rom ? It's the 1st thing to do before or after firmware flash.
There's nothing weird ,probably you made a mistake with flashing,as i mensioned the 1st thing i have seen in your video was that the first checbox in the flashtool was checked while if you opened the flashtool in Finless rom folder that checkbox in UNCHECKED. In your first post you are saying that you have everything followed by the letter,so that's the proof it isn't true.
Such a little mistake can cause such problems.
I had Finless 1.4 to,no probs with wifi