Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

go to the market and download any oc app of your choice. Not sure what else you were expecting. OCing tho isnt really recommended. If it was, htc would have done it for us natively..lol.

:mrgreen:

Also dont expect it to run like a snapdragon. Someone did tests int he past showing good results which is the only reason why i did changes on the kernel to support it.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

This ^^.

I like SetCPU, seems to be popular. It's pretty simple/to-the-point, and it works great.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

I have a question - GSM works in this build? I want to try this, but if GSM doesn't works, I can't do it. PLZ Answer

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

No.

It's in the title. 400\500 only means Rhodium 400 (Sprint)? and Rhodium 500 (Verizon)

I couldn't even get it into recovery with my vzw global sim card in it....

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

you want me to answer, you need to ask the right questions.. :mrgreen:

Do you mean gsm as in using the sim on the cdma phones ? or are you actually asking about the gsm only rhodiums.

For now its NO to both anyway. However the SIM on cdma will boot just wont connect. I'm not sure if i can get this fixed for next release.

as for gsm device? well thats gonna take a few weeks. Just got a test device this week and lk is booting but there are alot of button issues that need to be solved.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

Okay, a few things:

Market crash is caused by persist.sys.country and .language not being set. Using the locale to reset it to English (US) fixes that issue (both have to be set to sane values).

WiFi tethering works, although it requires you to "set" the setting by going into the details and pressing OK, similar to how it is done in FRX.

/sdcard is mounted with mask 0702. Not sure why that is, but it causes issues if you use "file managers" to copy stuff into other places.

Wake issue reminds me of when FRX was "stuck" in deep sleep mode (19.2mhz). I think there was a kernel patch that fixed that a few month ago.

Also, I had a "stuck LED" when the phone was unplugged from the charger when it was off. Probably related to the sleep/wake thing.

-- Starfox

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

That's the known fix. Is this in build.prop tho? If that could be set by default... would be nice.

Wake issue? When receiving a call..? I didn't really seem to notice any wake issues 'cept for incoming calls.

I've had a few SoD's, and a handful of reboots... Pretty rare tho.


I have a report tho - ACL wanted me to try the whole fastboot schebang with Linux (which turned out to be WAY more difficult than on Windoze)... well the result so far is - it works! I don't have to pull the battery to properly reset, rebooting from CWM worked great, the only hiccup was initially getting the machine to recognize the device in fastboot, but I think that was mostly a user-error issue on my part. Haven't used fastboot in Linux before, only adb.. :oops:

At any rate, I'll continue to monitor this. If you want to read a (very brief) version do so here.

OMGB seems to have a hard time waking once it's put to deep sleep. I recall FRX having the same issue, until someone noticed it being stuck at 19.2MHz on wake. Basically you needed to "kick" it awake by holding buttons, plugging cable, or extending the keyboard, which generates interrupts to get it to start responding. I'm thinking something along the same line.

-- Starfox

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

Weird. I don't have this issue...

The only other thing I can think of is that I'm using No-frills to set the clock to 719/122. The default is 528/245, and I recall something about setting the minclock to 122 causing an issue.

You can use CPU Spy to check how long it's spending in each clockrate. I find it to be a very useful utility.

Also, is anyone using Opera Mini with omgb? I can't get it to go past the install screen, says it can't connect to the 'net. And what do I need to hax in order to get the provider string to something other than T-CDMA 64?

-- Starfox