SenseUI - Landscape mode - G1 Android Development

I may have found out on random how to rotate rosie.
All i did was:
Pressed power button, so screen goes black.
pressed menu while in portrait mode, while lockscreen was there, slided out keyboard, the lockscreen unlocked itself. Powered down the screen several times, reverted the keyboard, pressed menu, and tada, i think a bug, which may can be fixed.
I attached 2 pictures and the log when it happened.
I can press the softkeys for phone, apps and add widget!
REPRODUCED a second time with the instructions i posted !
Maybe this is the solution! And, rosie is superfast while in this mode!
Only thing to fix now, is letting the screen below the bar rotate
Good luck at all devs!

Wow! Nice find maxisma =) Will report back haha, only thing I don't like is that it looks very...trashy in landscape

It only rotates the bar, that's why it looks trashy.

i can't do this can you be more explicit like when you slide keyboard the phone is on landscape or portrait?

Here is a little secret:
You probably need to remove all of the android:screenOrientation lines in AndroidManifest.xml. That is all.

cyanogen said:
Here is a little secret:
You probably need to remove all of the android:screenOrientation lines in AndroidManifest.xml. That is all.
Click to expand...
Click to collapse
It's encrypted..
And as I read, there is no way to decrypt it. The only way to get it, is to get the source.
But rosie is closed-source

maxisma said:
It's encrypted..
And as I read, there is no way to decrypt it. The only way to get it, is to get the source.
But rosie is closed-source
Click to expand...
Click to collapse
Not encrypted, just converted to a binary format. Try AXMLPrinter2.jar or a hex editor

Thanks for the tip! Unencrypted it!
Removed all "android:screenOrientation"-lines!
Going to test now..
Hope i don't have to convert it back to binary. If so, i have to work with an Hex-Editor.
But first, I pushed it. result follows..
Result: It died. Testing now with hexeditor.
CAn't find anything with an hexeditor :-( Any way to convert nonbinary into binary?

If you honestly want auto rotate that bad you can go into the manifest.xml for rosie. converit it from binary to readable text turn on auto rotate it recombile the manifest add it back into the apk and then resign it

If thats true why has nobody done it?

pentace said:
If you honestly want auto rotate that bad you can go into the manifest.xml for rosie. converit it from binary to readable text turn on auto rotate it recombile the manifest add it back into the apk and then resign it
Click to expand...
Click to collapse
Yeah, but HOW to recompile?

maxisma said:
Yeah, but HOW to recompile?
Click to expand...
Click to collapse
If you throw it into a dummy program in eclipse and then export it with out signing it and then remove it from the app that you made, like with the .9? maybe i dunno for sure never had to do it

Jrbourque said:
If you throw it into a dummy program in eclipse and then export it with out signing it and then remove it from the app that you made, like with the .9? maybe i dunno for sure never had to do it
Click to expand...
Click to collapse
Eclipse won't let us export an apk if it has errors, and this xml introduces errors (too many to fix by hand)
Any other ideas for compiling this non-binary XMLs into binary?

I found out, it wouldn't work, even with a modified XML.
Ok, only if you would use widgets, but what's Rosie without widgets?

maxisma said:
I found out, it wouldn't work, even with a modified XML.
Ok, only if you would use widgets, but what's Rosie without widgets?
Click to expand...
Click to collapse
I found out how to do other things with modified XMLs, like reduce the number of home screens. How did you do it?

i found this minutes ago joking around with the phone trying to set it on ladspace mode and randomly i see that the bar went lands scape, and also the notification bar, hope the devs can make something to have it fully

Related

uninstalled HTC Lockscreen and got bad flan lockscreen

I have searched the forums but cannot find a fix for this.
I am a noob when it comes to rooting/flashing but just rooted my hero and am running ddamage control v2.02, i think it is great but I have always hated the HTC lock screen, the flan one imo is much better.
I looked around and found that by entering
adb remount
adb shell
cd system/app
rm HtcLockScreen.apk
rm HtcLockScreen.odex
reboot
and rebooting the phone I get a messed up version of the flan style lock screen. It was supposed to remove the HTC lock screen and give a flan version. I am thinking that it may be because I did not type exit, but rather safely removed the hardware.
Anyway the problem is that the flan lock screen is the green lock circle that is supposed to slide to the right is in the bottom middle part of the screen, the only way to unlock it is to slide it up/the silent circle must be slid down to enable it to be silenced. Also the time is on the left side, and it is currently 12:15, however the time will show
12:1
5
because of the unusual version of the lock screen.
I looked around and found a fix that was supposed to re add the HTC lock screen, however the fix was for a 1.6 version and I cannot find the thread.
If anyone could help me either reinstall the original HTC Slider or preferably a properly working flan style I would appreciate it. I am thinking that because it is not an official ROM the developer did do a great job, but did not make it with the original flan style.
Here ya go.........................BTW there is no fix yet....
mjz147 said:
I have searched the forums but cannot find a fix for this.
I am a noob when it comes to rooting/flashing but just rooted my hero and am running ddamage control v2.02, i think it is great but I have always hated the HTC lock screen, the flan one imo is much better.
I looked around and found that by entering
adb remount
adb shell
cd system/app
rm HtcLockScreen.apk
rm HtcLockScreen.odex
reboot
and rebooting the phone I get a messed up version of the flan style lock screen. It was supposed to remove the HTC lock screen and give a flan version. I am thinking that it may be because I did not type exit, but rather safely removed the hardware.
Anyway the problem is that the flan lock screen is the green lock circle that is supposed to slide to the right is in the bottom middle part of the screen, the only way to unlock it is to slide it up/the silent circle must be slid down to enable it to be silenced. Also the time is on the left side, and it is currently 12:15, however the time will show
12:1
5
because of the unusual version of the lock screen.
I looked around and found a fix that was supposed to re add the HTC lock screen, however the fix was for a 1.6 version and I cannot find the thread.
If anyone could help me either reinstall the original HTC Slider or preferably a properly working flan style I would appreciate it. I am thinking that because it is not an official ROM the developer did do a great job, but did not make it with the original flan style.
Click to expand...
Click to collapse
u didnt do anything wrong when deleting the files. the flan screen is messed up on sprint release so far. No one has attempted or has failed to fix is so far
thanks alot, appreciate it. Obviously I would rather have the working HTC Lock screen than a broken flan one.
Did the same way. Could find no way to get the htclockscreen to install again. Pushed it, ran it, whatever...I ended up just re-flashing.
mjz147 said:
thanks alot, appreciate it. Obviously I would rather have the working HTC Lock screen than a broken flan one.
Click to expand...
Click to collapse
maybe one of the dev out there could look at it and fix it for us. maybe one day.
My HTC Sense lock screen is working again. Thanks for the link again.
I think a majority of Sense users love sense but don't like the lock screen, it is easier to open in the pocket and the flan style is smoother and more natural
mjz147 said:
My HTC Sense lock screen is working again. Thanks for the link again.
I think a majority of Sense users love sense but don't like the lock screen, it is easier to open in the pocket and the flan style is smoother and more natural
Click to expand...
Click to collapse
Yeah and flan looks better IMO. And being able to silence the phone easily is another plus.
Wasney said:
Did the same way. Could find no way to get the htclockscreen to install again. Pushed it, ran it, whatever...I ended up just re-flashing.
Click to expand...
Click to collapse
I may be a little late with this..... but i found when i removed the .apk and saved it for replacing later via estrongs I was able to simply copy and past back in /system/app and reboot. my original lockscreen was back with no problem. Although you must have the root options checked in options of estrongs file manager to be able to move the file.
Figured I post up what i found.
Bret
forgot to mention.....
I am sure others may know but you can also download lockbot from the market for free which has a few lockscreens, the pay or pro version has the flan lockscreen and have confirmed it works on DC2.1 treve mixture that I am running with no problems.... battery life good, VVM works, Location spot on, and no prl issues..(anymore)
anyway there my 2 cents And thanks to everyone out here I am starting to learn. All the devs keep it up!!!)Your Awesome
Looked at it a little bit
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Quick question. How are you looking into the .xml files? I tried looking into this as well and got stuck at not being able to view the xmls.
daryelv said:
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Click to expand...
Click to collapse
Good work. The heck with the Flan lockscreen, lets figure out how to remove the wallpaper to have a clear lockscreen. LOL
maxium01 said:
Quick question. How are you looking into the .xml files? I tried looking into this as well and got stuck at not being able to view the xmls.
Click to expand...
Click to collapse
There's a java utility called AXMLPrinter2 that will take the Android XML files and create a text file. Unfortunately it's only a one-way process, so editing of the XML files requires Hex-editing. That's how I edited the status_bar.xml file to change the font from white to black on the Taskbar.
-Daryel
daryelv said:
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Click to expand...
Click to collapse
Wow, you have put in a lot for that.
I am running damage control v.2r2 and I believe that because it is not an official rom, damageless did not put in unneccesary android suff, the lockscreen being one of them. Their wouldnt be a point in installing or including in the rom a perfect standard messaging app, if HTC has their own.
However someone earlier in this thread gave me an .apk of the HTC lockscreen after installing it and rebooting it worked perfectly again.
I know this sounds stupid because I have no knowledge of developing at all but is their anyway to get an .apk of the 2.1 or even the 2.0 lock screen and just install it, it seems that it would just repair the broken version in damages rom, and all we would need to do is manually disable the HTC lock screen.
Any thoughts?
mjz147 said:
Wow, you have put in a lot for that.
I am running damage control v.2r2 and I believe that because it is not an official rom, damageless did not put in unneccesary android suff, the lockscreen being one of them. Their wouldnt be a point in installing or including in the rom a perfect standard messaging app, if HTC has their own.
However someone earlier in this thread gave me an .apk of the HTC lockscreen after installing it and rebooting it worked perfectly again.
I know this sounds stupid because I have no knowledge of developing at all but is their anyway to get an .apk of the 2.1 or even the 2.0 lock screen and just install it, it seems that it would just repair the broken version in damages rom, and all we would need to do is manually disable the HTC lock screen.
Any thoughts?
Click to expand...
Click to collapse
The Android lockscreen is part of the framework, separating it out would create other problems within the ROM. There isn't an "Android lockscreen" APK, the code is built into services.jar, framework.jar, policy.jar, and framework-res.apk.
I did have another thought, maybe there's something in the HTC code that is conflicting or overriding the stock settings. I'll take a look at some of the com.htc files tomorrow and see if anything jumps out at me.
-Daryel
daryelv said:
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Click to expand...
Click to collapse
I luv to see someone trying to fix this.....still using the screwed up version still like it messed up more than anything else.... *** dcv1.0 it was working fine as well as some others** Thanks for keepin this going!
daryelv said:
The Android lockscreen is part of the framework, separating it out would create other problems within the ROM. There isn't an "Android lockscreen" APK, the code is built into services.jar, framework.jar, policy.jar, and framework-res.apk.
I did have another thought, maybe there's something in the HTC code that is conflicting or overriding the stock settings. I'll take a look at some of the com.htc files tomorrow and see if anything jumps out at me.
-Daryel
Click to expand...
Click to collapse
that would be great. That sounds about right perhaps their is something in damages rom that are overriding the stock setting?
I wonder though if someone running a stock rooted hero rom, could remove the hero lock screen and get the normal android "menu" lock
You know what? I bet it IS somewith with the HTC settings. Why else would they push out the ROM with all the HTC stuff working and not the Android lockscreen working? Because we're not supposed to be modifying the phone in the first place! So therefore HTC is adjusting the settings without regards to what Android stuff will be broken (because they assume we are going to only use Sense). Good thought.
if i remove it? when i unlock it will i get the animations? like on the normal htc losckreen or no?

Solution to the HD2's crappy keyboard!(updated 10/3/2010!now with working xt9 button)

Ive managed to edit some of the xml files for the built in keyboard and i have to say that it works so much better now.
the idea to make the keyboard work better was inspired by how the buttons were spaced on the iphone. i noticed that they were spaced farther apart compared to the hd2 so i painstakingly edited every buttons' "virtual" position and this has resulted in a keyboard that is much more responsive(the lags seem to have lessened considerably) and accuracy in typing is now at par with an iphone.
i never use xt9 so i just removed it(in the 1st three attachments)w/c also resulted in reduced mis pressing it when trying to press an "A".
i also moved the dpad arrows(also in the 1st three attachments) to the top making the period, comma and spacebar easier to press without mistakes.
the backspace button has been enlarged for better ergonomics.
to lycox, thanks for letting me use your skin. heres the link to the original skin's thread http://forum.xda-developers.com/showthread.php?t=709916
thanks also goes to p107r0 for leading me in the right direction.
this wouldnt have been possible without XmlGui so big thank yous to programatix.
Instructions: download the attached rar files.unrar and copy all files inside the folder directly to the windows directory of your HD2(you will need a 3rd party file explorer like resco to overwrite the existing files). soft reset. thats it...
i strongly suggest to backup all the files to be replaced just in case something goes awry.
do this at your own risk.please dont blame me if your phone suddenly gets bricked. mine worked perfectly after replacing all files.
please leave a comment after youve tried it.
this is only for portrait mode. i didnt touch landscape coz i dont use it...
if theres anyone kind enough to make a cab file out of this please do.
EDIT: if you need xt9 use the Orig KB Edited attachment
Update: i made a version 2 of the mod with the spaces between the buttons even farther apart. some people might find this more comfortable but the mod sometimes results in "no presses". and by the way i succesfully skinned the spacebar and shift key thanks to dinik and p107r0.use the attached sipmap.dll in the fallout keyboard rar file but its far from perfect.eg:the .com button has disappeared.i have to look into this a bit more to fix it...
if you want the original gtx skin just replace the fallout png files with the ones from the edited kb rar file.
EDIT 2: i added an original version with the arrows at the bottom and the xt9 working.
EDIT 3: i know its a bit confusing but to shed some light on all the attached files heres an explanation.
the first one(Edited KB.rar) is exactly like Edit KB by boogiecornejo.cab except in cab form.
the third(FAllout KB.rar) is like the first two except that its semi skinned with a fallout theme.
the last(Orig KB Edited10-3-2010) contains the files needed to replace in the windows folder to get the functionality of my mod using whatever keyboard you already have(assuming its a normal layout eg: with the directional arrows at the bottom) in your device.
i hope that shed some light on whatever questions there are about the files...
Thanks!
I abandoned the original due to the many typo's. My first impression of your modded version is very positive.
Regards,
How do you switch from alpha to numeric keys (can see how to get back but how do you get to it in the first place)? Does it still use XT9 and error correction as per original even though you've removed the XT9 button?
Dunc001 said:
How do you switch from alpha to numeric keys (can see how to get back but how do you get to it in the first place)? Does it still use XT9 and error correction as per original even though you've removed the XT9 button?
Click to expand...
Click to collapse
hello dunc!to switch from alpha to numeric just press the @ button.
xt9 is completely disabled and im not really sure how to turn it on without having to go back to the drawing board. editing the xml file is to say the least "tedious" but if a lot of people would request it back i might, as i said, "go back to the drawing board"
its actually a miracle of sorts that this mod worked coz im not really into developing anything on these forums. this is actually my first real contribution to the community despite having been around for the last 6 or 7 years...
I would like to give it ago but i do use the XT9 function all the time, at the moment i've gone back to the old style phone keypad rather than a qwerty keyboard as it seems to be less laggy and the buttons are far larger (i got fat fingers)
Good work on this though i'm surprised no one else has done something before wish i knew where to start
@boogiecornejo
this is a cab for you..
great work
If i install the cab and don't like it, will it restore back to the original keyboard ?
boogiecornejo said:
if theres anyone kind enough to make a cab file out of this please do.
Click to expand...
Click to collapse
[attachment removed: the same 2 posts above]
lol congrats on this release.
to me it is difinately looking very impressive.
+1 to go on the xda portal
oh would difinately try it out once it has got some decent skins cause it currently looks.... kinda like a little bit like spiking my eye. along would my screwed up today screen I just dont want anything else added into the phone....
will report back once I reflashed and installed the keyboard.
congrats, good luck, and keep up this master piece
cheers
if you want to turn t9 on/off switch keyboards to another e.g. compact keyboard hit the t9 switch option and then change back to your normal keyboard and t9 will be changed
alesscam said:
@boogiecornejo
this is a cab for you..
great work
Click to expand...
Click to collapse
thanks so much!
wakers said:
If i install the cab and don't like it, will it restore back to the original keyboard ?
Click to expand...
Click to collapse
i actually dont know so i suggest you download both the cab and rar files.open up the rar and see what files are there then backup the original ones of your hd2. install the cab file and if you dont like it then just put back the original ones into your windows/ folder.
hope that helped...
ClementNg23 said:
lol congrats on this release.
to me it is difinately looking very impressive.
+1 to go on the xda portal
oh would difinately try it out once it has got some decent skins cause it currently looks.... kinda like a little bit like spiking my eye. along would my screwed up today screen I just dont want anything else added into the phone....
will report back once I reflashed and installed the keyboard.
congrats, good luck, and keep up this master piece
cheers
Click to expand...
Click to collapse
hahaha! i know!i tried making a fallout style skin but the letters are kinda muddied so bye to that but rest assured one of these days a good looking skin will certainly pop up.
btw does anyone know which files to replace to change the spacebar and shift button?
Boo hoo
boogiecornejo said:
btw does anyone know which files to replace to change the spacebar and shift button?
Click to expand...
Click to collapse
Yeah, noticed this on mine - left space and shift keys in original style unskinned. Also keys don't line up on mine - i.e. when I press 'H' I get a 'B' and so on. Looks like I'll have to stick with Resco KB Pro for now!
boogiecornejo said:
i actually dont know so i suggest you download both the cab and rar files.open up the rar and see what files are there then backup the original ones of your hd2. install the cab file and if you dont like it then just put back the original ones into your windows/ folder.
hope that helped...
Click to expand...
Click to collapse
for restore an original KB
simply unistall my cab
Dunc001 said:
Yeah, noticed this on mine - left space and shift keys in original style unskinned. Also keys don't line up on mine - i.e. when I press 'H' I get a 'B' and so on. Looks like I'll have to stick with Resco KB Pro for now!
Click to expand...
Click to collapse
is everybody experiencing this? i might have upped the wrong xml file...
I've got the same issue. None of the keys match up even though the pop-up of each key press is correct.
EDIT: It looks like it was just an issue with XT9. XT9 must be turned off before using this layout. Just go into any of the other keyboard layouts, select ABC instead of XT9, switch back to Full QWERTY keyboard, and everything works like its supposed to do.
Thank you Boogiecornejo for making HD2 keyboard finally functional. I went from an iPhone to the HD2 and I always missed how well the keyboard worked. Great Work!!
bluxero said:
I've got the same issue. None of the keys match up even though the pop-up of each key press is correct.
EDIT: It looks like it was just an issue with XT9. XT9 must be turned off before using this layout. Just go into any of the other keyboard layouts, select ABC instead of XT9, switch back to Full QWERTY keyboard, and everything works like its supposed to do.
Thank you Boogiecornejo for making HD2 keyboard finally functional. I went from an iPhone to the HD2 and I always missed how well the keyboard worked. Great Work!!
Click to expand...
Click to collapse
youre very welcome!
i concur with bluxero, you cant use this layout with xt9.
so now im so hyped about this that i gave skinning the keyboard another try and heres the result...
i pretty much like it coz i use the fallout theme but i cant seem to skin the space bar and the shift key. any help pls....
boogiecornejo said:
btw does anyone know which files to replace to change the spacebar and shift button?
Click to expand...
Click to collapse
check bitmaps in Windows\SIPBitmaps.dll: it seems to contain all the shifts, spaces and XT9 button graphics
p107r0 said:
check bitmaps in Windows\SIPBitmaps.dll: it seems to contain all the shifts, spaces and XT9 button graphics
Click to expand...
Click to collapse
how do you open a dll file?

ICS ShapeWriter...

I know not everyone prefers ShapeWriter, not sure why it's the best keyboard out there, but with all the ICS stuff and themeing, here's a ICS themed ShapeWriter Keyboard.
ps-if anyone knows how to change the tracer color, please let me know. I've asked, pm'd, googled, all with no luck.
TheBeardedMann said:
I know not everyone prefers ShapeWriter, not sure why it's the best keyboard out there, but with all the ICS stuff and themeing, here's a ICS themed ShapeWriter Keyboard.
ps-if anyone knows how to change the tracer color, please let me know. I've asked, pm'd, googled, all with no luck.
Click to expand...
Click to collapse
just like swipe. its in the libshapewriter.so file. only way to edit it is to use a hex editor. use this as a guild http://forum.xda-developers.com/showthread.php?t=1162558
you will need to figure out what the HEX code for the stock color and find it in the .so
OK. So any help on finding that color in Hex Editor? I knew it was in the .so file but don't know the location.
TheBeardedMann said:
OK. So any help on finding that color in Hex Editor? I knew it was in the .so file but don't know the location.
Click to expand...
Click to collapse
you would have to decompile it and see what the hex code is used for the color then search the .so for it.
its easier in linux. i will see what i come up with then i am home tonight.
synisterwolf said:
you would have to decompile it and see what the hex code is used for the color then search the .so for it.
its easier in linux. i will see what i come up with then i am home tonight.
Click to expand...
Click to collapse
Thanks. I appreciate it. No worries if nothing happens.
I thought I was the only person alive that still uses shapewriter. Is there any way to remove the background image? It's a bit distracting
Akomack said:
I thought I was the only person alive that still uses shapewriter. Is there any way to remove the background image? It's a bit distracting
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=812313
Check this out. It's a few replies in. If you want a certain color or background or whatever, I could probably do something for ya.
After I posted that, I did a little playing around.. Made an orange and black one to go with my orange MIUI 4.0 theme
Got it. I posted on other thread.
Shapewriter bug
HI
long time shapewriter user - recently upgraded to ICS (BCM on the desire)
did a restore of shapewriter from a titanium backup of it i had (this was from CM7 ie gingerbread). Works perfectly but for one problem: Whenever i switch to the number keyboard it duplicates the last digit when i switch back to the alpha keyboard.
Any ideas how to fix or workaround?
Presume the "data" part of the titanium restore is the bit that cointain info on my writing style etc so would be up to 2 years worth of learned data that i would rather not have to wipe and relearn. Maybe the app isnt as clever as this. Im not sure?
I think you might be able to do a fresh install and then copy over the library files. Once I get to a computer I'll look into it.
TheBeardedMann said:
I think you might be able to do a fresh install and then copy over the library files. Once I get to a computer I'll look into it.
Click to expand...
Click to collapse
Shaspewriter isnt available on the market/play any more i know that there are modified variants out there but i'm not so comfortable getting it from a lesser source do to the security/easy ability to capture all keyboard input - do i need a special installer file etc or will the data stored by titanium backup suffice. Not sure if it has the apk file.
Any help appreciated.
I have a galaxy note and am still using shapewriter as it is STILL the best tracing keyboard out there. BUT unfortunately it appears on the note in a compacted form, only taking up 2/3 of the width of the screen. Does anyone know if there is a version that would adapt to any screen size??
ICS Shapewriter [Now with xhdpi support!]
Here is a nice ICS themed shapewriter. It also has support for hi res devices. :laugh:

[Q] A Path to Take

Hey Guys,
I wanna learn modding and developing Android. I'm new to XDA and don't know which path to take. Should I start by modding some .apks or should I use Android SDK to learn to develop apps. BTW, I use Linux (Xubuntu 1.04) and I'm familiar with the Command Line. I just want somebody to point me in the right direction.
Thank you...
JasonKZLY said:
I'm new to XDA and don't know which path to take.
Click to expand...
Click to collapse
Hi.
Take which ever comes naturally, but you should have some idea before signing up as modding an apk or two is a bit different to developing a full app I would say. I would start by reading reading and reading some more.
Hmm...
XperienceD said:
Hi.
Take which ever comes naturally, but you should have some idea before signing up as modding an apk or two is a bit different to developing a full app I would say. I would start by reading reading and reading some more.
Click to expand...
Click to collapse
I found this thread by Cyanogen --- http://forum.xda-developers.com/showthread.php?t=667298. I decided to take his advice but I have another question, a bit stupid one perhaps, I was trying to edit my Android's Phone.apk. I was changing the colour of the numbers in the dialpad to blue, I used Gimp (Yes, I changed the mode to RGB) and edited the .png files in both drawable-hdpi-finger and drawable-mdpi-finger. I signed and zip-aligned the .apk, after putting it in my phone's system/app, changing permissions and rebooting. The Numbers in the dial-pad was still white in colour, I had also edited the unknow-caller png and that worked but the dialpad thingy didn't work. Any ideas???
JasonKZLY said:
I found this thread by Cyanogen
Click to expand...
Click to collapse
A third path then. :silly:
JasonKZLY said:
The Numbers in the dial-pad was still white in colour, I had also edited the unknow-caller png and that worked but the dialpad thingy didn't work. Any ideas???
Click to expand...
Click to collapse
It might not be an image but controlled by an xml, or the buttons you've changed aren't what's used by the Phone etc, for example the dialer buttons in my Phonebook to make a call aren't the same as when I'm on a call, as the ones used while I'm in a call are in another apk, which for me is SEMCPhone.apk, which you'll only find on SonyEricsson/Sony Phones.

Help with Framework-res

Hi guys
I have edited my framework-res.apk (de and recompile with advanced_apktool and ticklemyandroid )for reducing the navbar height to 36 dip and i got this after booting my devices...
Image1
Image2
I have tried to change the theme and rebooted but the issue is not solved ...
Thanks for helping me
lordriguez said:
Hi guys
I have edited my framework-res.apk (de and recompile with advanced_apktool and ticklemyandroid )for reducing the navbar height to 36 dip and i got this after booting my devices...
Image1
Image2
I have tried to change the theme and rebooted but the issue is not solved ...
Thanks for helping me
Click to expand...
Click to collapse
i cant understand that language
arismelachrinos said:
i cant understand that language
Click to expand...
Click to collapse
Sorry it's in french the first image is power off, reboot and so one, the second image is the message for safe reboot
You're referring to how the popup dialogs have that white around them, right?
I could be wrong, but from your screenshots, it looks as if the images that are used for the dialog box lost their transparency for some reason, so you're seeing white with the shadow over it, instead of the shadow over whatever is behind the dialog as it should look. Is the nav bar size the only thing you've modified? If so, then maybe APKTool and/or TickleMyAndroid is/are at fault. I believe APKTool compresses images before recompiling, so it might have saved those images incorrectly without transparency. I'm not sure how to make it handle images differently, though (I feel like there should be some parameters if you're using it through the command prompt and not with a GUI tool).
A good way to test my theory would be to start fresh, decompile your framework-res.apk and then just recompile it without modifying anything. Push it to your system and see if you still see this issue. If you do, then you know the tool is messing up the images somehow, but if not, then something you modified the first time is causing the problem. If it seems like APKTool is your culprit, then I would suggest first trying something like APK Multi-Tool. It's the only tool I use for modifying APKs and it never gives me any problems. Try it out and see if it produces the same results. If it still does, you can try the "Keep folder" option it has, which will copy over all the original files from the APK that you didn't modify exactly as they are, without touching them at all, to prevent errors.
neonixxx said:
You're referring to how the popup dialogs have that white around them, right?
I could be wrong, but from your screenshots, it looks as if the images that are used for the dialog box lost their transparency for some reason, so you're seeing white with the shadow over it, instead of the shadow over whatever is behind the dialog as it should look. Is the nav bar size the only thing you've modified? If so, then maybe APKTool and/or TickleMyAndroid is/are at fault. I believe APKTool compresses images before recompiling, so it might have saved those images incorrectly without transparency. I'm not sure how to make it handle images differently, though (I feel like there should be some parameters if you're using it through the command prompt and not with a GUI tool).
A good way to test my theory would be to start fresh, decompile your framework-res.apk and then just recompile it without modifying anything. Push it to your system and see if you still see this issue. If you do, then you know the tool is messing up the images somehow, but if not, then something you modified the first time is causing the problem. If it seems like APKTool is your culprit, then I would suggest first trying something like APK Multi-Tool. It's the only tool I use for modifying APKs and it never gives me any problems. Try it out and see if it produces the same results. If it still does, you can try the "Keep folder" option it has, which will copy over all the original files from the APK that you didn't modify exactly as they are, without touching them at all, to prevent errors.
Click to expand...
Click to collapse
Thanks I will test it and and let you know!!!
By the way I solve the issue by changing the apktool_2.0.3 to apktool_2.0.1 on Advanced apktool the resources.arsc was way bigger with 2.0.3 and all is fine now!
lordriguez said:
Thanks I will test it and and let you know!!!
By the way I solve the issue by changing the apktool_2.0.3 to apktool_2.0.1 on Advanced apktool the resources.arsc was way bigger with 2.0.3 and all is fine now!
Click to expand...
Click to collapse
Awesome! Sounds like it could have indeed been what I was saying, judging by the increased resources size, but I guess it doesn't really matter now unless you're curious Glad you got it working!
neonixxx said:
Awesome! Sounds like it could have indeed been what I was saying, judging by the increased resources size, but I guess it doesn't really matter now unless you're curious Glad you got it working!
Click to expand...
Click to collapse
Yeah Curiousity is the mother of XDA :good::highfive:
Thanks for help buddy!

Categories

Resources