[ROM][STOCK] -=StockPlus=- Root, Busybox, Deodexed [1.0.519r2][10/10/2013][DISCONT.]

[tevil]

can someone tell me if this rom is that much more superior to the stock rom with the overclock and root?

I read some of the earlier posts and honestly cant see if its worth flashing or just sticking with what I have.

I have almost just decided to go back to plain old stock non root since nothing has really come out for this. Honestly thought XDA would be loaded with ROMs by now but I guess its just not as popular as initially hoped.

also was the fact that a system update would wipe the changes been fixed?
thanks

 

[romskii]

For me there are problems running apps from playstore. Playstore opens normaly, i can also download my apps but when I'm trying to open the downloaded app it fcs, any suggestion?

 

[cronikman84]

For me there are problems running apps from playstore. Playstore opens normaly, i can also download my apps but when I'm trying to open the downloaded app it fcs, any suggestion?

stock plus is OLD, i would stick to stock rom till Kit Kat is released soon, and trust me, it's coming and it's on the works

 

[IncognitoMan]

Pretty much as cronikman84 said... the base of this rom is OLD ( pre usb storage ) so I'd suggest to move to latest and use WonderEkin's modpack and root solution until then.

 

[primo_4c4]

OLD? This Rom is the best!!

Sent from my SGH-I337M using XDA Premium 4 mobile app

 

[vincenzo697]

Pretty much as cronikman84 said... the base of this rom is OLD ( pre usb storage ) so I'd suggest to move to latest and use WonderEkin's modpack and root solution until then.

So should we expect any new StockPus Rom from you?

Cause your rom with kholk kernel makes the experiense :angel:

Thanks for your great work!!!!!!

 

[HashBrownJM]

Hey all! I'm using a fairly old version of this ROM (before themes and whatnot were separated into an apk and such), so, if I were planning on moving to a new ROM, which one should I move to?

A stock Android 4.4 ROM, or a different version, plus the mod pack for overscan and Play Store fix? Any help would be appreciated!

Or should I just install this as it is?

 

[cronikman84]

Hey all! I'm using a fairly old version of this ROM (before themes and whatnot were separated into an apk and such), so, if I were planning on moving to a new ROM, which one should I move to?

A stock Android 4.4 ROM, or a different version, plus the mod pack for overscan and Play Store fix? Any help would be appreciated!

Or should I just install this as it is?

stick to stock rom for now, is the best option... There was a kit Kat rom on the works for the OUYA but i believe there's going to be a pause on that rom cause of the New EP kernel issues (reboots and screen flickering), i found a temporary solution to the issues but the issues need to be addressed fist...

 

[lmulli]

stick to stock rom for now, is the best option... There was a kit Kat rom on the works for the OUYA but i believe there's going to be a pause on that rom cause of the New EP kernel issues (reboots and screen flickering), i found a temporary solution to the issues but the issues need to be addressed fist...

There's a new auto update that my device just received - if you had the EP Bootloader you will need to re-enable it again and of course wait for someone to repack the latest kernel, unless you do it yourself of course!. At the moment, I can't see any reason to as it really doesn't offer anything that the stock Kernel doesn't apart from a spot of overclocking. My initial tests with Antutu had the Stock slightly ahead of the EP kernel for the same clock speed.

 

[ph1nn]

Pretty much as cronikman84 said... the base of this rom is OLD ( pre usb storage ) so I'd suggest to move to latest and use WonderEkin's modpack and root solution until then.

Honestly your mod may be old but it's still the one I run as it still handles everything. All the updates since really haven't done much to improve things by the looks of the changelog outside USB storage which I haven't needed. Now if only we could get a StockPlus update :fingers-crossed:

Anyway, if it's recommended then anyone have a guide to move to the latest (853), it's been so long and I'm still on StockPlus. I tried it once a while back and lost root/google play/etc and didn't even seem to get WonderEkin's stuff running.

Is there a step-by-step process such as (1) Full Wipe/ Install 1.2.853 (2) Install WonderEkin's Root (3) Install WonderEkin's XPOSED. etc..?

 

[nchantmnt]

Honestly your mod may be old but it's still the one I run as it still handles everything. All the updates since really haven't done much to improve things by the looks of the changelog outside USB storage which I haven't needed. Now if only we could get a StockPlus update :fingers-crossed:

Anyway, if it's recommended then anyone have a guide to move to the latest (853), it's been so long and I'm still on StockPlus. I tried it once a while back and lost root/google play/etc and didn't even seem to get WonderEkin's stuff running.

Is there a step-by-step process such as (1) Full Wipe/ Install 1.2.853 (2) Install WonderEkin's Root (3) Install WonderEkin's XPOSED. etc..?

the steps should be: wipe, flash, root, install xopsed framework, isntall and enable modpack.

or just wait a bit, as i'm working on an all-in-one-zip solution right now.

 

[IncognitoMan]

Honestly your mod may be old but it's still the one I run as it still handles everything. All the updates since really haven't done much to improve things by the looks of the changelog outside USB storage which I haven't needed. Now if only we could get a StockPlus update :fingers-crossed:

Anyway, if it's recommended then anyone have a guide to move to the latest (853), it's been so long and I'm still on StockPlus. I tried it once a while back and lost root/google play/etc and didn't even seem to get WonderEkin's stuff running.

Is there a step-by-step process such as (1) Full Wipe/ Install 1.2.853 (2) Install WonderEkin's Root (3) Install WonderEkin's XPOSED. etc..?

Yea I've been busy with a few bits in regards to CM porting on OUYA so I haven't looked into restarting StockPlus although I *may* in the future. ( unless what I'm working on does indeed work nicely enough... then StockPlus becomes pointless )

 

[IncognitoMan]

...Now if only we could get a StockPlus update :fingers-crossed:

Still working out some kinks though... but it's pretty much done.

Also as the notes say... it's now a patcher rather than a full rom.

In regards to CM porting I'm still working on it... just decided to take a break and update this a little ( and to see what ouya has added since the last time I mucked around with their firmware )

 

[Ipse_Tase]

yahoooooo

Still working out some kinks though... but it's pretty much done.

Also as the notes say... it's now a patcher rather than a full rom.

In regards to CM porting I'm still working on it... just decided to take a break and update this a little ( and to see what ouya has added since the last time I mucked around with their firmware )

Holly smokes...just when I was losing hope
Welcome back IncognitoMan.

 

[cronikman84]

Still working out some kinks though... but it's pretty much done.

Also as the notes say... it's now a patcher rather than a full rom.

In regards to CM porting I'm still working on it... just decided to take a break and update this a little ( and to see what ouya has added since the last time I mucked around with their firmware )

so is this stockplus but updated?

 

[ph1nn]

Still working out some kinks though... but it's pretty much done.

Also as the notes say... it's now a patcher rather than a full rom.

In regards to CM porting I'm still working on it... just decided to take a break and update this a little ( and to see what ouya has added since the last time I mucked around with their firmware )

This is great news Incognito. I like your patcher approach. I actually see more value in this than the KitKat project because I feel the OUYA rom is well suited for the fullscreen TV interface with gaming/xmbc and controller support. Looking forward to this released!

 

[TadeoNYC]

I haven't used my OUYA in months, because I installed a version of Xposed around the holidays that broke Play store and then had a death in the family and then it started snowing twice a week.

Does the patcher remove the TOS requirement? On principle, I don't want to agree to it. It's BS to force binding arbitration of disputes in order for me to continue using the market and OUYA launcher.

Sent from my Nexus 7 using Tapatalk

 

[Tenterhook]

Issue in CIFS portion of OUYA_StockPlus_1.0.519r2

Welcome back, IncognitoMan!

I noticed an issue in the CIFS portion of OUYA_StockPlus_1.0.519r2, which probably does not affect anyone with English-only filenames on the server, but results in filenames with Chinese characters (as part of the filename) being displayed with lots of question marks instead of correctly as Chinese (well, UTF8, so could be any language!).

Mount Manager allows mount options to be specified and, from what some web searches showed up, it looks like the necessary option to fix this is to add iocharset=utf8 to the options.

However, when doing so, the mount then fails with "mount: cannot access a needed shared library". It looks like the module in question is nls_utf8.ko (http://forum.xda-developers.com/showpost.php?p=34400889&postcount=1 actually mentions md4.ko too but I am not sure what it is for).

I verified that this problem is due to the missing kernel modules by comparing the results using sideloaded "ES File Explorer_3.0.5.1.apk" to browse the same files on the same server. (With ES, the Chinese filenames are correctly displayed using ES's built-in CIFS support, but using ES to browse under the mount point of the CIFS volume, gave the question marks instead).

Looking forward to trying this "StockPlus patcher", when it is made available!

IncognitoMan, assuming this is due to missing kernel modules (or built-in kernel support), and not just "finger trouble" on my part(!), would it be possible either to provide kernel modules for StockPlus_1.0.519r2 to work around this, or to fix it in the new StockPlus patcher, when it is made available please?

(I have attached an empty .txt file for testing, in case needed, in a .7z archive to avoid any filename issues with this site!).

 

[IncognitoMan]

Welcome back, IncognitoMan!

I noticed an issue in the CIFS portion of OUYA_StockPlus_1.0.519r2, which probably does not affect anyone with English-only filenames on the server, but results in filenames with Chinese characters (as part of the filename) being displayed with lots of question marks instead of correctly as Chinese (well, UTF8, so could be any language!).

Mount Manager allows mount options to be specified and, from what some web searches showed up, it looks like the necessary option to fix this is to add iocharset=utf8 to the options.

However, when doing so, the mount then fails with "mount: cannot access a needed shared library". It looks like the module in question is nls_utf8.ko (http://forum.xda-developers.com/showpost.php?p=34400889&postcount=1 actually mentions md4.ko too but I am not sure what it is for).

I verified that this problem is due to the missing kernel modules by comparing the results using sideloaded "ES File Explorer_3.0.5.1.apk" to browse the same files on the same server. (With ES, the Chinese filenames are correctly displayed using ES's built-in CIFS support, but using ES to browse under the mount point of the CIFS volume, gave the question marks instead).

Looking forward to trying this "StockPlus patcher", when it is made available!

IncognitoMan, assuming this is due to missing kernel modules (or built-in kernel support), and not just "finger trouble" on my part(!), would it be possible either to provide kernel modules for StockPlus_1.0.519r2 to work around this, or to fix it in the new StockPlus patcher, when it is made available please?

(I have attached an empty .txt file for testing, in case needed, in a .7z archive to avoid any filename issues with this site!).

I derped on 519 and didn't add those when I compiled the kernel... I've included them in the new patch so all should be good...

Does the patcher remove the TOS requirement? On principle, I don't want to agree to it. It's BS to force binding arbitration of disputes in order for me to continue using the market and OUYA launcher.

Sent from my Nexus 7 using Tapatalk

I've already agreed to them so I don't see the prompt anymore ( nor do I know whats controlling it off hand ) so as far as I know... no the patch doesn't remove the ToS requirement.

 

[yeahimdukenukem]

Would be so great to have a new StockPlus.
I'm still using and loving it, don't want to update to Stock ROM anymore