★★ CROMi-X 7.x Q&A Thread ★★

[sgalanov]

Ah right, I sorry misunderstood. I know Google only allow mounts to be seen by the app doing the mounting since 4.2. Not sure how NFS differed from a cifs setup?

I personally use es file explorer which sees my network PCs and drives fine and allows me to share files that way.

Right, from what I understand NFS does not differ from cifs wrt. mounting. But as you noted about a possibility to build cifs module, is it supposed to work somehow with this >=4.2 problem?
I also use file browsers to access cifs shares, but I wanted to try NFS, since it is much faster, and I am not aware of any file browser supporting it, so it's natural to simply mount it. Unfortunately Google has complicated this path

 

[sbdags]

Just reskinned the Asus Keyboard as I hate all the blue

 

[YayYouFixedIt]

Should I be able to raise and lower min and max frequencies? using trickster mod for example. They both seem stuck at the maximum? Any idea?

WARNING: Some screen protectors have rubbery surfaces not suitable for a stylus(ZAGG,Skinomi). RUBBER on RUBBER!

 

[sbdags]

Should I be able to raise and lower min and max frequencies? using trickster mod for example. They both seem stuck at the maximum? Any idea?

WARNING: Some screen protectors have rubbery surfaces not suitable for a stylus(ZAGG,Skinomi). RUBBER on RUBBER!

Nope over clocking / under clocking are not enabled in the kernel.

 

[sbdags]

CROMi-X Reodexer Released

CROMi-X REODEXER DOWNLOAD

Rather than release a whole new rom I made a small flashable zip file that will take CROMi-X DEODEX and ODEX the framework and system apks. This way you can do it yourself (And save me lots of work)

It takes about 5 mins to do and the result afterwards is you have a fully ODEXED rom. The odexed version feels smoother than the DEODEX version to me Although theoretically it should make no difference.

Instructions: Flash the DEODEX ROM then flash this after and reboot (Remember it takes about 5 mins to reodex a rom fully)

TF701T CWM ODEX Flashable Zip

Don't try this on a CM11 based rom or a non Asus 4.3 based rom as it will cause boot loops

Click here to discover which is best : ODEX or DEODEX

 

[AngryDinosaur]

gray keyboard looks good!!

 

[YayYouFixedIt]

It worked I guess. Odexed.
After changing the resolution to 1900×1200 density 240 It worked just fine except I noticed in Rom ToolBox Pro in the build.prop section. dpi was still 320? Seems this was causing issue with some apps. Thumb keyboard looks fine.

 

[YayYouFixedIt]

Hi. I reflashed the Rom Asus Optimized to include missing apps. I wiped cache, dalvik and it got stuck at the boot animation. Wasnt sure what was happening so I repeated that and in addition wiped system. Also stuck at boot animation. Any ideas?

Oh nm it just kicked in. I guess thats the 10 mins you were talking about.

 

[sbdags]

CROMi-X v6.0.1 Patch

Version 6.0.1 Update Patch Released:

Change Log:

16/02/2014 CROMi-X v6.0.1 Patch
o Updated Asus Keyboard with my darker theme - removed most blue background and normal keys
o Updated Super User and binary to version 1.93
o Updated Google Maps to version 7.6.1
o Updated Google Search to version 3.2.17
o Updated Google Music to version 5.4.1409N
o Updated Google Core Services to latest version
o Build.prop updates:
Added pm.sleep_mode=2
Added ro.ril.disable.power.collapse=0
Updated dalvik.vm.dexopt-flags=m=y,o=v,u=n to dalvik.vm.dexopt-flags=v=n,o=a,u=n

Enjoy!

 

[YayYouFixedIt]

How com stock shows at 301 density and this one is at recommend 320? Nice KB.

 

[sbdags]

How com stock shows at 301 density and this one is at recommend 320? Nice KB.

What shows 301?

 

[YayYouFixedIt]

I think the build.prop. It shows that when I look in rom toolbox pro build.prop section. Also cm11 was set at 301 as well. This change looks like it puts it in another dip range no?

---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------

I think it's in the xhigh range at 301. Not sure about 320.

 

[sbdags]

I think the build.prop. It shows that when I look in rom toolbox pro build.prop section. Also cm11 was set at 301 as well. This change looks like it puts it in another dip range no?

Asus stock is 320 dpi. CM may drop down to 301 which would break compatibility with the play store.

This is how I calculated it:

TF700 Res is 1.333333 times bigger than the TF201/TF300
TF701 Res is also 1.33333 times bigger than the TF700

TF201 / TF300 Res = 1280 x 800 at 160dpi
TF700 = 1920 x 1200 @ 240dpi

therefore

TF701 = 2560 x 1600 @ x where x calcs to be 320dpi

240 x 1.333333 = 320dpi

 

[sbdags]

My Asus Stock Apps Installer / Remover is now available. Of course this works with Asus Stock and CROMi-X. Not tested it on CM11 so may or may not work.

Enjoy!

http://forum.xda-developers.com/showthread.php?t=2650721

 

[pershoot]

good catch (i derped, hehe)!

updated build with it remediated will be up in a lil while.

 

[pelago]

Version 6.0.1 Update Patch Released:

Change Log:
o Build.prop updates:
Added pm.sleep_mode=2
Added ro.ril.disable.power.collapse=0
Updated dalvik.vm.dexopt-flags=m=y,o=v,u=n to dalvik.vm.dexopt-flags=v=n,o=a,u=n

Enjoy!

Can you explain in simple terms what the above changes mean for end-users?

 

[sbdags]

Can you explain in simple terms what the above changes mean for end-users?

OK better battery performance when sleeping and more efficient dalvik cache optimization. Should help with performance.

 

[sbdags]

CHANGE LOG

21/02/2014 CROMi-X v6.0.1a Patch
o Updated dalvik.vm.dexopt-flags=v=n,o=a,u=n to dalvik.vm.dexopt-flags=m=y,o=f,u=n,v=a
This patch includes all the changes in 6.0.1
This should fix the issues with bootloops on 6.0.1 - thanks LetMeKNow and YayYouFixedIt!

:good::fingers-crossed:

 

[micker31]

update a cromix 5.X to 6.01

hello
i am in cromix 5.X and i want to update to 6.X
but i am not sure :
-only flash new version ?
-need flash new bootloader + new recovery + new version ?
Thanks for any help

 

[sbdags]

hello
i am in cromix 5.X and i want to update to 6.X
but i am not sure :
-only flash new version ?
-need flash new bootloader + new recovery + new version ?
Thanks for any help

YOU can't - this thread is for the TF701T - if you are on CROMi-X 5.x then you have a TF700 and you should stop flashing TF701 stuff on it as you are lucky you haven't bricked it

Different devices mate