114 replies to this topic

[flibblesan]

wazy, on 04 December 2011 - 11:15 PM, said:

Cheers for the reply Fibble..

I didn't realize they'd removed them!!  Do you recommend a certain keyboard?  I'm just getting back into this android stuff

Is there no way you can add a dictionary to the existing android keyboard then?  or any way to do it?

Thanks again,
Wazy

PS - Is this Swype I hear of any good?

I don't like Swype much. I always use Swiftkey X for a keyboard.

Try this Android keyboard out. I've not tested it fully but it should work ok.

http://www.mediafire...miamuf5798akv47

As always, install using recovery.

[admanirv]

SwiftkeyX great keyboard, I'm glad we don't have xt9 any more.

[Flumpster]

flibblesan, I have decompiled the framework-res.apk but I have no idea what folder and file those settings for the buttons are in.

Can you point me in the right direction please so I can get the lights to come on as I want them.

[flibblesan]

Flumpster, on 05 December 2011 - 02:01 PM, said:

flibblesan, I have decompiled the framework-res.apk but I have no idea what folder and file those settings for the buttons are in.

Can you point me in the right direction please so I can get the lights to come on as I want them.

framework-res\res\values\arrays.xml

Then you need to make changes to config_autoBrightnessLevels, <integer-array name="config_autoBrightnessButtonBacklightValues"> and possibly <integer-array name="config_autoBrightnessKeyboardBacklightValues"> too

I'm not totally sure how the values work but so far it seems that the higher the value, the more the lights will light up.

[Flumpster]

Thanks very much for that.. I will have a play with them this afternoon and report back any findings or optimum settings I find.

Cheers one again.

[Flumpster]

I had a quick play and the best settings for me seem to be :

	<integer-array name="config_autoBrightnessButtonBacklightValues">
		<item>200</item>
		<item>100</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
	</integer-array>

I have recompiled it and zipaligned for anyone else wanting to try.

**link removed**

flibblesan, any idea why your framework-res.apk is 7,283kb where mine is 4,439kb compiled? When decompiled they are both exactly the same size and same contents but yours is nearly double the size?

Edited by Flumpster, 05 December 2011 - 04:12 PM.

[flibblesan]

Flumpster, on 05 December 2011 - 03:46 PM, said:

I had a quick play and the best settings for me seem to be :

	<integer-array name="config_autoBrightnessButtonBacklightValues">
		<item>200</item>
		<item>100</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
		<item>0</item>
	</integer-array>

I have recompiled it and zipaligned for anyone else wanting to try.

Button Light Fix

flibblesan, any idea why your framework-res.apk is 7,283kb where mine is 4,439kb compiled? When decompiled they are both exactly the same size and same contents but yours is nearly double the size?

resources.arsc will be compressed in your file. Normally it isn't compressed in framework files

Having it compressed can cause bootloops. Just tested your file and it has given me bootloops but if I add the resources.arsc file in uncompressed then it works fine.

[Flumpster]

ahh.. How can I compile without compressing that file ? is there a switch ?
At the moment I am just running "apktool b decompiled compiled.apk"

Also I just tested it on the second phone and these settings are not quite right.. It looks like the light sensor is inconsistent between phones.

Looks like if people want it right for their own phones they'll have to play with them manually.

Thanks again.

[flibblesan]

Open framework-res.apk with winrar (rename to .zip) then drag resources.arsc into the zip, then use store in the compression type.

[Flumpster]

awesome... thank you .

[fr0do]

Linky again pls Flump?

[Flumpster]

fr0do, on 05 December 2011 - 05:58 PM, said:

Linky again pls Flump?

I removed it because I had too much compressed in the apk during compile.

I'm still working on better settings and will upload a proper one for you when I'm finished mate.

But it does seem that both my devices require different settings.

[fr0do]

Ah ok

[snowbord]

Is the option to redirect cache/ to RAM enabled in this rom?  I ask as we potentially now have repartitioning sorted on this device, thanks to Amphoras;

http://android.modac...st__p__1859061 

[flibblesan]

snowbord, on 06 December 2011 - 12:22 AM, said:

Is the option to redirect cache/ to RAM enabled in this rom?  I ask as we potentially now have repartitioning sorted on this device, thanks to Amphoras;

http://android.modac...st__p__1859061 

Not yet. I can add it though.. easy to do.

[snowbord]

flibblesan, on 06 December 2011 - 01:36 AM, said:

Not yet. I can add it though.. easy to do.

If you could mate, that would be much appreciated.

[PsYcHoKiLLa]

Hey guys, I'm having problems. Hopefully someone can help.

I have the San Fran II, I tried flashing both this rom and Sebastian's rom but when I try to use the keyboard, the tracking is off by half a letter in portrait (Very difficult to sign into google). I tried flashing the ouk-stock.zip file afterwards but then on the next boot it just hangs with the robot logo. I'm guessing the problem with the keyboard tracking is due to the roms being based on the vivacity?

The method I used to flash was the QPST method listed here : http://android.modac...d-now-complete/

I tried using the ADB fastboot method but it kept saying "no device found", I'm using Windows 7 64 bit, is this why? ..and would the fastboot method allow the roms to install properly?

Also, I presume the clockwork recovery was supposed to replace the "FTM" screen? I managed to get into clockwork recovery to install the roms but I assumed that I would be able to get into clockwork any time after that but when I reboot with vol down held in I just get the "FTM" screen again.

Hopefully someone can help me get the roms working properly

Edited by PsYcHoKiLLa, 07 December 2011 - 02:22 AM.

[PsYcHoKiLLa]

Update...

Managed to get the Clockwork Recovery installed using fastboot (Just a hint for other folks, try using the driver installer and then use the adb inside ZTE's own folder, copy all the other stuff you need from the ADB pack into this folder too and then just follow all the Clockwork Recovery instructions from within this folder.

Then flash whichever custom rom you want to use but if you're doing this with a San Francisco II, your keyboard will probably be off like mine was, just flash the ouk-stock.zip, it fixed my skewed keyboard, works fine now. Thanks so much guys for all your effort, really do want to get my hands on a CyanogenMod port tho, just for all the extra CM goodness

EDIT: Hmmm, Maybe all is not good. Wireless won't connect now, I checked my mac address and it's correct so I'm not sure why it's not connecting, I flashed the r2a rom, then the ouk-stock.zip, keyboard works properly but the wireless just keeps dropping/not connecting.

I might just try to put the stock rom back in for now Boo Hiss!!

Edited by PsYcHoKiLLa, 07 December 2011 - 03:37 AM.

[t.reddings]

Thanks for all the work. I have used this since Tuesday all seems okay. So much better than Stock T Mobile especially with A2SD as I have lots more space now. One issue I noticed, the stock browser doesn't display images, I've checked the tick box in settings, unticked and re ticked to no avail. A workaround for me is use Dolphin browser.

Any ideas why this issue could be there?

Edited by t.reddings, 08 December 2011 - 12:40 PM.

[admanirv]

Hi what did you use to partition your memory card? And partition type did you create?

When doing this does it wipe your memory card?

Thanks