Pipo M9 Pro RileyROM 1.7

[Bytebitten]

Sure. Go to settings Go to About Tablet System Updates Turn off Auto check update ALL DONE!

Found some info that might be usefull;

build.prop
ro.product.ota.host
www.jinson.com.cn:2300

OK...I think I may have found a fix...but I need a little help testing it, if anyone is willing.

Since you are rooted...you can use an advanced File Manager app like Xplore or ES File Explorer and set it to root read/write permissions in preferences. You will need to confirm this when Superuser pops up.

Browse in the root to /system and look for a file named build.prop.

Choose edit or open in text editor and scroll down to the bottom of the file and you will find a line saying:

ro.product.ota.host=www.jinson.com.cn:2300 (or something like that...it may be a different address)

And just put an # in front of the line to comment it out.

Save

Reboot

And see if this prevents the tablet from nagging you about an update.

You can delete some apps like provision.apk or rkupdate.apk, but other things may quit working...so I'm trying to prevent having to do that.

Please, let me know what you find out.

You can also use Build.prop Editor

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

[rrileypm]

The actual build.prop command to turn off OTA is:

ro.rk.ota.enable=0

Thanks to Neomode for finding that for me today.

The other way works, too...but this is the official way. I will be including this line in future updates.

[BillinCA]

FWIW, changing OTA to be disabled in settings does something (unknown) different from changing build.prop to have that line. Adding
ro.rk.ota.enable=0
to build.prop and rebooting with Settings enabled will still display
"Find a OTA upgrade package! do you want to update? ..."

You might want to do more testing before using the line. I could also not be doing something right!! Changing the Settings value doesn't change the modif date on /system/build.prop for me.

[rrileypm]

Re: Pipo M9 Pro RileyROM 1.7

Whether the setting goes away or not isn't as important as stopping the nagging prompt that pops up constantly. In fact, the less we do to change the makeup of the firmware the better. This setting change is the least invasive approach...as opposed to deleting apk files.

That being said...not being able to save an edited build.prop is another problem I must solve. Its partly because I haven't left much extra room in the system.img file. You have to leave some wiggle room...which isn't there.

If Pipo doesn't release an update soon, I will make an updated version of this ROM to include the prescribed fixes. Maybe tonight when things settle down here at the firehouse. The same problem exists in all of the latest Pipo ROMs....so I have some work cut out for me.

I really appreciate all the testing you guys are doing for me. That makes deciding what to change much easier. Keep up the good work...and let me know how it goes. I couldn't have anticipated how this new "feature/bug" would play out.

[rrileypm]

Re: Pipo M9 Pro RileyROM 1.7

FWIW, changing OTA to be disabled in settings does something (unknown) different from changing build.prop to have that line. Adding
ro.rk.ota.enable=0
to build.prop and rebooting with Settings enabled will still display
"Find a OTA upgrade package! do you want to update? ..."

You might want to do more testing before using the line. I could also not be doing something right!! Changing the Settings value doesn't change the modif date on /system/build.prop for me.

I use an app called Xplore free from Google Play Store.

In the configuration I set root access to the highest setting root mount read write.

Scroll to system/build.prop and press and hold the file until you get a menu. Press edit txt.

Scroll down to the bottom and enter the ro.rk.ota.enable=0 line.

Press save at the top.

See if that works to edit the build.prop.

Be sure to reboot for the change to take affect.

[asoft4dex]

FWIW, changing OTA to be disabled in settings does something (unknown) different from changing build.prop to have that line. Adding
ro.rk.ota.enable=0
to build.prop and rebooting with Settings enabled will still display
"Find a OTA upgrade package! do you want to update? ..."

You might want to do more testing before using the line. I could also not be doing something right!! Changing the Settings value doesn't change the modif date on /system/build.prop for me.

well you have to delete the downloaded update file from the root sd card
thats all, after with edited build prop will never give you update.

[BillinCA]

well you have to delete the downloaded update file from the root sd card
thats all, after with edited build prop will never give you update.

It didn't exist in the root - at least until I just went ahead and allowed the update to attempt. Red ! on an Android. I don't know if it put it in the root as soon as it downloaded, or when it immediately (I expected it to ask) setup recovery and rebooted. Reboot eventually asked if I wanted to delete the file, but I picked no to investigate. Deleted it manually. Reboot is still prompting about OTA update as long as Settings have update set to On - build.prop line seems to have no effect for me.

So I:
cd /mnt/external_sd/
su < OTAtestIn.txt > /mnt/external_sd/OTATestOut.txt

OTAtestIn.txt says
echo grep for ota
ls -l /system/build.prop
grep ota /system/build.prop

echo LS of SD
ls -l /mnt/sdcard/

echo from when I did allow it to update and install failed
cat /cache/recovery/last_install


OTATestOut.txt says:

grep for ota
-rw-r--r-- root root 3431 2013-09-27 10:05 build.prop
ro.sf.fakerotation=true
ro.sf.hwrotation=270
ro.product.ota.host=www.jinson.com.cn:2300
ro.rk.ota.enabled=0
LS of SD
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Alarms
drwxrwxr-x system sdcard_rw 2013-09-26 18:57 Android
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 DCIM
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Download
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 LOST.DIR
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Movies
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Music
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Notifications
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Pictures
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Podcasts
drwxrwxr-x system sdcard_rw 2013-09-26 18:54 Ringtones
drwxrwxr-x system sdcard_rw 2013-09-26 19:22 TitaniumBackup
-rwxrwxr-x system sdcard_rw 124155 2013-09-26 19:36 Xposed-Disabler-CWM.zip
drwxrwxr-x system sdcard_rw 2013-09-26 19:21 data
drwxrwxr-x system sdcard_rw 2013-09-27 09:13 romtoolbox
from when I did allow it to update and install failed
/mnt/sdcard/1.0.1.zip
0



I *suspect* having done the search for an OTA update once may have put something in data that is causing it to keep popping up for me. I read a little but everything I find for OTA is to clear things so that an update is found ASAP, not to get it to stop checking.

I'm VERY much a novice here. I don't have any problems editing build.prop in ES File Explorer, but Build Prop Editor suggested by Bytebitten in post 121 is a LOT easier than me changing /system/ to R/W.

If adding the line to build.prop works for others, it isn't an issue and I've just done something to myself. It certainly doesn't seem to be working for me. I can let it attempt the update again but tell it OK to delete this time - it does say something about continuing to prompt if it isn't deleted. Maybe it deletes MORE than just the .zip??

[rrileypm]

OK, Folks.....

Before I begin work on a new ROM, let me ask some questions of those who experienced the 1.7a And 1.7b ROM's.

The OTA update feature only exists in the 1.7b ROM. This was the firmware posted on the Pipo site on 9/17/2013 with a file name of PiPO M9pro software_OTA_20130824. v1.7a is actually based on firmware with a newer file name date, but posted on 9/12/13 and 9/9/13.

So this OTA feature seems to be implemented on a firmware that was older than the 1.7a ROM's firmware, but was posted on a later date with this nagging feature.

What I need to know is which ROM is better performance wise?

Do I need to invest the time in making a new ROM with the necessary tweaks to disable the OTA feature on a ROM based on older firmware??????? I'm not sure I see the logic in that.

What do Ya'll think? [Yes, that's really the way we talk in Arkansas...hahaha!!!!!!]

[PipoM9Pro]

I vote yes for the new ROM with the nagging OTA silenced...Also wonder when pipo will do a firm for the m9 pro with 4.3.x??





C

Dispatcher: Pipo Max M9 Pro Quad Core / RileyRom USA / Autu. 19474

[rrileypm]

OK, I'll redo the 1.7b ROM with some revisions.

Stay Tuned!!!!!!

[Rhenie]

I think those who are on 1.7b need OTA since this the new feature we want to experience.Yes Randy..I am patient to wait for you to update the rom and don't pushed yourself to hard . I am happy with 1.7b for now.

[rrileypm]

But, I think OTA isn't working properly on my custom ROM's.

May I suggest if you have more problems to switch back to 1.7a.

If anyone successfully gets the OTA to finish installing an update, please let me know.

[BillinCA]

I had loaded the PiPo img named 9/17 (9/13 date) and did process the OTA update without issue. I did try adding my wife as a user and had lots of trouble.

Loaded 1.7B but turned off OTA updates very soon. I declined updates until I started testing build.prod change, but then allowed one to proceed - it didn't work (didn't expect it to). Still getting nags, but they seem to be less and less frequent.

I assume you were only interested in OTA updates to 1.7B, but thought I'd mention the original version worked for me.

[rrileypm]

OK, thanks for the report.

[jmiturbe]

I installed 1.7a yesterday on my M9Pro wifi and then restored apps via titanium.

So far the rom is excellent - most notably, my tablet now has the best wifif reception of any device in the house. Also scored a fair bit higher on antutu (up 2k from rileyrom 1.3a)

My tablet scores in the 17's but some users are claiming antutu scores in the 19's.... ....what else have you guys done to boost your score further other than flashing a new rom?

Hello,

Did anybody try both 1.7a and 1.7b? Any differences on the wifi reception between them?

I went directly to the 1.7b because I suposed that it was a newer rom, but the wifi recepction is not so good. Too far from having the best wifi reception of any device in my home. It has the worst wifi of all my devices (Blackberry, Android phone, Nokia phone and Laptop).

I also read on this post that it seems 1.7b is based on an older firmaware than 1.7a, so I wonder if changing to 1.7a will improve my wifi reception.

Best regards.