[Q] Team EOS: User control of regulatory domain.

[theretro]

Hi all

I have a xoom and installed eos about 30 mins after opening the box.

I love it but no user control of regulatory domain, that sucks.

Any pointers on how to implement this, build.prop keys don't seem to work and i'd not want to have to recompile gpu/oc kernel, but would if necessary.

It would seem that cm has it but don't want to move from eos as its ace.

 

[bigrushdog]

Well it depends on what aspect of regulatory domain you speak of. Regarding wifi channels, yes its in the kernel. I have a patch that eliminates all the regulatory crap. This is something we are still debating as to whether we should implement or not.

 

[theretro]

9Yes wifi, i understand your concerns over implementing such a patch. But also believe that full control over our own device is fair and our own responsibility, Not to placed on the shoulders of dev's like you who do all the work so we can all enjoy our kit.

I am on nightly so would that mean it's in this kernel? If so should would i need something like iw to set it or a key in build.prop?

Thanks.

 

[bigrushdog]

No iw won't help if its not enabled in the kernel. Ill likely add this to my overlay anyway so no worries.

 

[theretro]

Nice one

While your talking about overlay, when i'v flashed it i'v noticed that the gpu was not clocked
With the new kernel, any chance of a gpu version of the overlay, I know its not a mega overclock but would still prefer it in there call me cheeky if you want lol.

 

[bigrushdog]

Sorry man, gpuoc in the overlay kernel ain't happening. I've merged a regulatory remove patch. However, I'm prettty sure we have to mod the firmware calibration file as well. Ill talk with the team about a more comprehensive solution.

 

[theretro]

No worries about gpu, its not that big of deal. Thanks for the merge i appreciate it.

Keep up the good work.

Thanks.

 

[theretro]

Just wondering if you managed to talk to the team about implementing this as a feature?