Related
I was playing with the emulator and I went to a site and looked at some comments and one commenter stated that he was running JF 1.41 and he had extracted spareparts from the SDK and was running it on it...I would check my history to find the exact site but I have it set to clear upon every exit (I'm a guy...I have a girl...you know how that goes). Anyone know anything about this?
Is it possible and will it work?
It works for RC33, but the only things in it that work are the window transitions. You'd be better off installing the Dev Tools apk found here: http://forum.xda-developers.com/showthread.php?t=453686
The Dev Tools app lets you customize transitions (like Spare Parts) and it also lets you add a bunch of stuff like process limits and CPU usage monitors.
amgupt01 said:
It works for RC33, but the only things in it that work are the window transitions. You'd be better off installing the Dev Tools apk found here: http://forum.xda-developers.com/showthread.php?t=453686
The Dev Tools app lets you customize transitions (like Spare Parts) and it also lets you add a bunch of stuff like process limits and CPU usage monitors.
Click to expand...
Click to collapse
aiight cool, thanks imma try it out.
damn was hoping that option to make the font smaller was in there....oh well.
Spare Parts can also reassign the Red end button, it requires a restart to take effect, but you can change it to
-go home,
-go (home then off),
- go off,
-or do nothing
I also found that I would not auto connect to wifi with it installed, but i cannot confirm that it was SpareParts.
do you have the spare parts apk?
Spareparts
Here ya go..
soundwire said:
Here ya go..
Click to expand...
Click to collapse
Thank you, but settings aren't saved when used =[ Bummer..
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
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?
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:
Hello Devs,
To begin with I have HTC One V (using shpongle 4.2.2 rom) whose bottom ~50px (full width) are not working properly and to make it worse, somehow the rotation sensor is not working. So, I would like to restrict the display from original resolution 480x800 to say 480x750. I tried using apps like "Resolution NoMone" but many applications are crashing with that and it vertically centers the screen wasting 25px at the top.
Would modifying any system properties manually help me achieve what I want?
A simple grep shows /system/build.prop has "ro.device.screen_res=480x800". I tried changing this to 480x750 (taking ideas from this post) but it didn't work
I would really appreciate any help in this.
jatiniitdelhi said:
Hello Devs,
To begin with I have HTC One V (using shpongle 4.2.2 rom) whose bottom ~50px (full width) are not working properly and to make it worse, somehow the rotation sensor is not working. So, I would like to restrict the display from original resolution 480x800 to say 480x750. I tried using apps like "Resolution NoMone" but many applications are crashing with that and it vertically centers the screen wasting 25px at the top.
Would modifying any system properties manually help me achieve what I want?
A simple grep shows /system/build.prop has "ro.device.screen_res=480x800". I tried changing this to 480x750 (taking ideas from this post) but it didn't work
I would really appreciate any help in this.
Click to expand...
Click to collapse
Just so I'm clear on what you're actually trying to do, are you actually trying to just change your dpi? Or who suggested it to be a wise idea to try and change your resolution?
Keep in mind tinkering with your build.prop can be dangerous if you are not certain of what you're doing.
markbencze said:
Just so I'm clear on what you're actually trying to do, are you actually trying to just change your dpi? Or who suggested it to be a wise idea to try and change your resolution?
Keep in mind tinkering with your build.prop can be dangerous if you are not certain of what you're doing.
Click to expand...
Click to collapse
No I am not changing DPI. Keeping DPI same, I want to discard the bottom 50px of my screen and make the system behave as if the screen is of size 480x750px. Well I have passed through the phase of screwing up my mobile and recovering it (thanks to XDA) and I am willing to take all risks to fix this. Worst case I will need to flash the rom again and thats welcomed
OK well all I can suggest is you post your question here and wait for someone to give support
http://forum.xda-developers.com/showthread.php?t=2259645
Good luck
Thread closed