[Development][ROM] Stock FROYO + 2.6.32 kernel

[Guest dr.flo]

what does it do with it? Masks?

I'd want to enable both :) Leds + WiFi Hotspot.

Or is it some config id in some external xml...

Also it is not proprietary lib is it? But likely those properties are hacks from Huawei...

It's not proprietary. But as you think it is likely our cmX version does not know anything about opta / optb. Will check source later.

Have you tried setting only opta or only optb?

[Guest pier11]

ro.config.hw_optb is an ISO country code!

u8150 - Safaricom (Kenya):

ro.product.locale.language=en

ro.product.locale.region=KE

ro.config.hw_opta=18

ro.config.hw_optb=404

Ascend (M860) - MetroPCS (USA)

ro.product.locale.language=en

ro.product.locale.region=US

ro.config.hw_opta=177

ro.config.hw_optb=840

um840 - Movilnet (Venezuela)

ro.product.locale.language=es

ro.product.locale.region=VE

ro.config.hw_opta=32

ro.config.hw_optb=862

ISO 3166. Country codes

KE 	KEN 	404 		Kenya, Republic of

US 	USA 	840 		United States of America 

VE 	VEN 	862 		Venezuela, Bolivarian Republic of

Edited February 21, 2012 by pier11

[Guest radodendron]

If you turn on the alarm, when triggered off the screen when the phone restarts. When the screen everything is fine

if the phone is on charge - phone does not reboot

Sorry for my english

Edited February 21, 2012 by radodendron

[Guest pier11]

Have you tried setting only opta or only optb?

tried

ro.config.hw_opta=177 (as in Ascend)

ro.config.hw_optb=862 (as in original um840)

Led lights disappeared, WiFi hotspot appeared. Magic. EDIT: the same effect for:

ro.config.hw_opta=32 (as in original um840)

ro.config.hw_optb=840 (as in Ascend)

my quessing is that opta is sort of mobile carrier code and logic enables features based on combination of both.

I.e. for example for MetroPCS(opta) in USA(optb), turn off tethering (operator is greedy and will charge separately for that :) )

the question is if it configured somewhere externally. It'd be illogical to hardcode this all.

Edited February 21, 2012 by pier11

[Guest pier11]

Looks like opta is a mobile operator ID of sort, as it is a part of official rom name:

ro.config.hw_opta=18

ro.config.hw_opta=177

ro.config.hw_opta=32

U8150 V100R001C18B842(Kenya Safaricom)

M860 V100R001C177B652(USA MetroPCS)

UM840V100R001C32B766SP01

[Guest dr.flo]

isn't ascend available from other carriers too? maybe there is one ascend-like combination allowing both leds and tether? Could also take that combination from an eclair rom (cricket?). It it's really country and carrier codes, android version should not matter.

Also ascend custom rom "beanbag" is said to have wifi tether on ascend. Would be interesting how their opts look like. Did not find download links for that...

I still wonder what leds have to do with country codes and carrier specific feaures....

Edited February 21, 2012 by dr.flo

[Guest pier11]

I still wonder what leds have to do with country codes and carrier specific feaures....

I see directories like:

xml-opta177-optb840

in Settings.apk

But that were responsible for extra screens definitions, not relevant to our issue.

Edited February 21, 2012 by pier11

[Guest dr.flo]

this seems to be "beanbag"

http://www.mediafire.com/?wzudseibr1mcrr3

[Guest pier11]

combinations to trytried (from um840 Settings.apk):

86/724 (Spain) <- Leds: NO, Hotspot: YES

69/484 (Mexico) <- Leds: NO, Hotspot: YES

153/840 (US) <- Leds: NO, Hotspot: YES

217/356 (India) <- Leds: NO, Hotspot: YES

17, 156 (China) <- Leds: NO, Hotspot: YES

kernel can be taken from u8150 roms (as I remember) on the first page to try (a normal branch kernel).

Edited February 21, 2012 by pier11

[Guest dr.flo]

ascend froyo settings.apk has (opta - optb)

in res:

153, 840

177, 840

217, 356

in assets:

17, 156

interesting: asset holds html files related to tethering (tethering_wifi_help.html)

Edited February 21, 2012 by dr.flo

[Guest pier11]

the 2.2.2 froyo is pretty much unified between ascend and um840 (BTW its name is Evolution :) ) and possibly others.

so some phones have wireless hotspot option, some don't. That's why that html help.

[Guest pier11]

updated tests above - no luck. Seems leds are assigned to MetroPCS in US.

EDIT:

also added the following - saw on u8150 cmX - no luck, hotspot doesn't appear:

ro.tether.denied=false

EDIT2:

this Ascend rom (likely not froyo) is for Cricket US,

M860V100R001C153B251SP03.zip

so opta=153 is Cricket.

Edited February 21, 2012 by pier11

[Guest pier11]

cm7 frameworks/base/services/java/com/android/server/ConnectivityService.java has this... :

// if ro.tether.denied = true we default to no tethering

// gservices could set the secure setting to 1 though to enable it on a build where it

// had previously been turned off.

public boolean isTetheringSupported() {

	enforceTetherAccessPermission();

	int defaultVal = (SystemProperties.get("ro.tether.denied").equals("true") ? 0 : 1);

	boolean tetherEnabledInSettings = (Settings.Secure.getInt(mContext.getContentResolver(),

			Settings.Secure.TETHER_SUPPORTED, defaultVal) != 0);

	return tetherEnabledInSettings && mTetheringConfigValid;

}

maybe huawei has added something there...

[Guest dr.flo]

Maybe we should just leave it as is before we know that we need it. Might turn out that we cannot get wifi hotspot to run - then we know how to get lights easily.

If we can get wifi hotspot, we might want to try a hack like this:

settings.apk includes libsettings.so which linkes against libutils.so - this is most likey where opta/optb come in.

One could make a copy of libutils.so, name it libutset.so (or anything of same length). Inside that file, edit opta / optp strings into e.g. optx / opty. Then provide optx / opty in build.prop. Hack libsettings.so to link libutset.so instead of libutils.so

That way, settings.apk would see different opta/optb then the rest of the system. The rest of the system could see ascend/metropcs -> lights and settings could see some wifi enabled combo...

Could work in theory...

Edited February 22, 2012 by dr.flo

[Guest radodendron]

I'm on another 8230 does not change mac address through SetMacAddress

[Guest dr.flo]

Just collected a few reports of remaining issues that have not yet been confirmed / discussed

but when screen is off if you press

green call wake the device

trackball wake the device

red endcall wake device.

is there something to do to make them not wake the device?

Noticed white square on prone boot? This is used to be ADNROID logo animation before libGLES_qcom.so and egl.cfg where added. It helped Neocore but killed the boot animation.

some issue problem using this rom in my pulse

- pulse keep reboot when receiving sms

Several times during the incoming sms phone reboots

If the vibration is turned on and the phone is in sleep mode, when an incoming SMS phone reboot

2/news and weather app can't give the weather...even after manually set.

4/ from time to time phone reboot ... why???

If you turn on the alarm, when triggered off the screen when the phone restarts. When the screen everything is fine

if the phone is on charge - phone does not reboot

[Guest dr.flo]

I'm on another 8230 does not change mac address through SetMacAddress

SetMacAddress needs root permission - did you make sure it got those permissions?

[Guest desalesouche]

@ pier11.Hi. i could notice that in the various um840 rom you uploaded on first page, that you made various change (addind or deleting files) in system/etc/audio* and also in system/etc/libaudio*. can you make a point about it please? would like to learn/understand....thanks a lot :)

Edited February 22, 2012 by desalesouche

[Guest radodendron]

root there, and says that the address is changed, but in fact it has not changed

[Guest dr.flo]

root there, and says that the address is changed, but in fact it has not changed

You might need to reboot. did you?

when you open setmac again, does it show the address you changed it to or always the default one?

Edited February 22, 2012 by dr.flo

[Guest radodendron]

You might need to reboot. did you?

when you open setmac again, does it show the address you changed it to or always the default one?

introduced native mac address, clicked install, wrote that the new address is set, but not really established, reboot does not result

Edited February 22, 2012 by radodendron

[Guest dr.flo]

introduced native mac address, clicked install, wrote that the new address is set, but not really established, reboot does not result

does it work on u8220 for anyone with um840 rom?

Possibly, setmacaddress has path to wifi firmware folder hardcoded. That path is different in this rom (acutally it is standard in this rom and different in cm).

Edited February 22, 2012 by dr.flo

[Guest radodendron]

may be somewhere in the address manually, you can change without this application?

But other people say that they have changed address

[Guest dr.flo]

may be somewhere in the address manually, you can change without this application?

But other people say that they have changed address

when you open setmacaddress, it shows the current address.

what does it show for you?

does it change after you set another address or does it remain the same? (both with and without reboot)

Edited February 22, 2012 by dr.flo

[Guest radodendron]

Shows the current address 00:18:82:82:20:01

When I enter the real address of the phone says that he has changed, but the first line, he remained the same 00:18:82:82:20:01

Edited February 22, 2012 by radodendron