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?
Related
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'm a big fan of the Hero slide-to-unlock function, but the only way it appears to get something like this on non-Hero builds is the Lock 2.00 app, which appears to have lots of problems since Android is not designed to have a user replaceable lock screen.
I would like to dive in to the framework and find where the (non-pattern, just push 'menu') lock screen is and see about replacing it. Things like a battery meter, emails, etc., that appear on Hero wouldn't be included since that requires tying in to all sorts of other things, as well as being a battery drain. In my mind ideally it would work as so:
1. Any key press wakes the screen
2. Slide down to unlock
The Android platform source is pretty intimidating when you don't know where to look though. Any devs want to point me to where in the tree the source for the 'Push Menu to unlock' screen is?
layout xml is in core/res/res/layout/keyguard_screen_lock.xml
some strings in core/res/res/values/strings.xml
That should get you started, I'm not sure where the rest of the code is, but this seems to be all Stericson modified.
[edit: I found the keyguard code for you. Check out various files in: android_frameworks_policies_base/phone/com/android/internal/policy/impl/ ]
Ah, OK, that helps, thanks. This will at least let me fix another pet-peeve: the giant carrier name and small date/time under it. (Because I really need to be reminded I'm on T-Mobile's service every time I unlock the phone. Just in case I miss the branding on the handset or the large text in the notification tray or something.)
pm'd you, in case you didn't notice my edit
Aha, there it is in LockScreen.java. As a test I changed it to allow a simple touch to unlock in addition to pressing the menu key. Now to figure out how to build this thing. (Even better, how to build cyanogens ROM, as I know that one works and works well.)
atomtom said:
Aha, there it is in LockScreen.java. As a test I changed it to allow a simple touch to unlock in addition to pressing the menu key. Now to figure out how to build this thing. (Even better, how to build cyanogens ROM, as I know that one works and works well.)
Click to expand...
Click to collapse
My bet would be to message Stericson or Cyanogen for some help compiling it and implementing it if you need it. To my knowledge, the Cyanogen roms still use some mods that Stericson made to the lockscreen.
So I can see that the stock jog dial images are in there... does anyone know the xml file which tells the phone to use the zz_moto files instead of the stock ones? I would like to
remove the moto files and make it use the default ones because I think moto's are ****in' UGLY!
NegativeOne said:
So I can see that the stock jog dial images are in there... does anyone know the xml file which tells the phone to use the zz_moto files instead of the stock ones? I would like to
remove the moto files and make it use the default ones because I think moto's are ****in' UGLY!
Click to expand...
Click to collapse
I'm not too sure. This is just a shot in the dark which probably has no chance of working but..if you're backed up and/or have means of restoring to at least a stock build...do you think maybe just a simple name switch for the png's could work (ie rename the stock joggers to "zz_moto")? I know this has a good chance of failing but hey you never know...
Yeah - I thought about that. I bet it will work. I was just hoping to get rid of the excess images altogether, to keep in theme with deblurring my phone .
I guess i'll give it a shot Friday though. (Won't have time until then)
Hmm.. the jog dials were used for the rotary lockscreen... wonder can I modify the android.policy.jar to get that back...
That'd be cool, but I think we're talking about different ones.
I'm talking about the jog dials jog_tab_bar files.
Yeah.. I'm thinking of the jog_dial_*etc*
Renaming them to zz_moto should do the trick. Might want to open them up and verify size and position of the .9 pixels though.
about size and position... so basically I should overlay them and see if the black border things line up?
NegativeOne said:
about size and position... so basically I should overlay them and see if the black border things line up?
Click to expand...
Click to collapse
yeah, and just edit as needed. recompile, then throw it in the apk or use ninja.
upon actual inspection, it looks like the files aren't exactly the same (in which files there are, and what they mean semantically)
Grr.. I really hate the stupid moto sliders.
There's gotta be a way to modify the XML files to make the screen like stock.
I was browsing around and found this:
http://forum.xda-developers.com/showthread.php?t=813162
and tried pushing and pulling the anim folder and all worked great, except everything!
the flip animations worked, but every app FC'ed.
so i basically only saw the flipping during the fc screens!
looks great, but doesn't work.
i have NO CLUE how to make it work.
what needs done to the files to get it to work?
and i MAY need the stock anim folder from our phone please!
by MAY i mean i do badly!
thanks!
:scooter:
Back when I was running Zen-ROM I was using Envynet's Elegant Envy theme, seen here: http://forum.xda-developers.com/showthread.php?t=768540
It had very similar animations to what I saw in the video...hopefully you can pull something from that.
i'm going to look into that.
thank you very much
Just wanted to say first time I pulled com.htc.resources.apk and pushed to that (made a backup before I modified) so after I pushed it nothing happened..
Then I pulled framework-res.apk and ploped the anim files in that.
Well now I get some really cool flip style transitions on my status bar up top, but no flip clock... Or is this what it's about? BTW, I got NO fc's on this either. If you want the framework-res.apk file, i'll post it.
Either way at least the flip style status bar will make a great addition to my roms
i could only get the ones from the dark to actually work.
all others wouldn't unzip.
so i'm giving them a go now.
i'll keep you posted.
sure, let me have what you got.
i'll toy around with them a little too.
thanks
so, the aria dark framework-res didn't work.
same thing.
force closes, but they flip!
by the way,
i'm using cm6 with adw launcher.
andro green theme.
i'm going to try LP instead of adw.
I believe envynet has did this before with his Envy Aria theme as I remember the flipping animations when i used that rom and his theme.
http://forum.xda-developers.com/showthread.php?t=768540
i tried those from Envy.
no avail.
still the same FC's as before.
rideascooter said:
sure, let me have what you got.
i'll toy around with them a little too.
thanks
Click to expand...
Click to collapse
Here's my framework-res.apk file:
http://www.mediafire.com/?1xdbf9w9308cwe2
All I did was pull the original from my phone, merge the anim directories with the file you provided and pushed back and voila! flips animations (between screens)
....
I just noticed you said your using cm6...
Well, I guess I better warn you.
I am using HTC Stock 2.1(base). And I am on Cellular South not Sprint, so definitely make a backup of your current framework-res.apk file before pushing this one.. dunno if it will work or not but hope so.
Thanks Hex:
Still gettting FC's.
i'm guessing it doesnt like AOSP.
i haven't had any luck with anything i've come across.
but they have ALL been from sense based roms. i think ....
i think i'm going to need some help on this.
anybody?!
Man this would be cool
it looks great,but ....
i can only see it on the FC screens!
Sounds to me like the xmls in that anim folder have settings pointing to various Sense related stuff (as I am finding out the hard way on my minimalist rom atm)
What you would need to do is decompile the xmls from cm6, and the xmls from the flipping anim folder and go through one by one merging just the flip code related to the animations and remove any sense related links... Which if I remember correctly are going to be addresses AND memory pages. This may prove to be quite tough to decipher.
Yeah I just think the .zip you found doesnt like aosp. I got it to work on my sense rom thanks to Hex. Now I like the animations.
Thanks man, always glad to help!
and how do i edit / decomplile these?
point me in the right direction, and i'm on it.
i want this to happen.
i'll probably hate it after a while, but i keep getting teased with the fc screens.
so for now, i want it!
what do i use to view xmls to edit them?
bump this up for a little help?
Shoot man, mah bad. I was meaning to help you.
#1 you need apktool:
http://forum.xda-developers.com/showthread.php?t=640592
This decompiles apks. I have never used it so... ymmv, but I have heard this is the best tool to do so.
Alternatively you can use xmlprint:http://forum.xda-developers.com/showthread.php?t=514412
This decompiles apks to text files, however it does it 1 by 1 and does not re-compile them into native bytecode, however at the same time since it's just one folder you may prefer this to apktool for decoding (but you still need apk tool to recompile them)
For CM6, instead of decompiling all of them, it may be better to just go grab the source for CM6. You can get that here:http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero_CDMA
This wiki also gives a howto for compiling the code afterwards. The upside is you can tweak CM6 to your liking. The downside is... compiling the whole thing.
If you find a fast easy way of compiling just the files you need, you can just merge them with your current cm6 install.
DO A NANDROID FIRST SO IF YOU MESS IT UP YOU CAN GO BACK!!!!!
Hope this helps man!
I found a guide that mentions basic Sense porting to another Sense device. I tried this with this Wildfire S ROM for a few reasons:
--I prefer the "standard" HTC Sense as found on any other device (ie. Black status bar, black apps, etc.)
--I wanted to see how well it'd run
--I wanted to see if there'd be any problems with anything
After following the above guide, I notice only the following bugs:
--Camera is upside down
--Rosie keeps force closing because of forced landscape orientation so I have to use an alternate launcher
--Lockscreen is always in Portrait no matter what
--Keypad backlights don't turn on
--Facebook button doesn't work (duh)
--(New)GPS doesn't work - need to mess with GPS libs when I have more time
--(New)The FM Radio app's graphics are messed up
To try and fix the Rosie problem, I tried copying over the Rosie.apk and Rosie.odex from the Chacha's 2.3.5 OTA, but no dice, the system doesn't even see it.
Anyone have any tips on how I could fix any of the above? I'm no dev, and I only tried this for (basically) the fun of it to see how it'd turn out and my "experience", so to speak, only goes as far as swapping files here and there - I felt like the Development forum was the best place to post this. Apologies if it isn't.
good attempt! nice to see to back into work. May be some developers can help you out.
I would like to apologize first, as it is 08:19 in the morning and I'm already drunk. lol.
Well, let's start with the easy bits:
1. --Keypad backlights don't turn on
Mainly the thing is that the Wildfire S ROM does not have support (or it is not activated) for a physical keyboard; therefore the need for backlight is redundant. To fix this you will either have to manually add the code lines or un-comment them. I suggest talking with adlx or xdbg since both of them have implemented this feature in the two custom ROMs.
2. --Facebook button doesn't work (duh)
As above, the ROM doesn't know (or doesn't want to know) about the physical keyboard. Same suggestions as above.
3. Landscape/portrait issues.
Well. The main problem here is the android system. By definition it detects the longest size on the display and sets it as the height. Therefore you'll have a tough time fixing the standard display to landscape. As above, I suggest speaking with the devs that worked on these roms and implement the ChaCha kernel files into the Wildfire ROM.
Aaaaaand that's about it I guess. I wish you good luck!
Drunk, this early??
Good effort!
Sent from my A810e using Tapatalk
qzfive said:
I found a guide that mentions basic Sense porting to another Sense device. I tried this with this Wildfire S ROM for a few reasons:
--I prefer the "standard" HTC Sense as found on any other device (ie. Black status bar, black apps, etc.)
--I wanted to see how well it'd run
--I wanted to see if there'd be any problems with anything
After following the above guide, I notice only the following bugs:
--Camera is upside down
--Rosie keeps force closing because of forced landscape orientation so I have to use an alternate launcher
--Lockscreen is always in Portrait no matter what
--Keypad backlights don't turn on
--Facebook button doesn't work (duh)
To try and fix the Rosie problem, I tried copying over the Rosie.apk and Rosie.odex from the Chacha's 2.3.5 OTA, but no dice, the system doesn't even see it.
Anyone have any tips on how I could fix any of the above? I'm no dev, and I only tried this for (basically) the fun of it to see how it'd turn out and my "experience", so to speak, only goes as far as swapping files here and there - I felt like the Development forum was the best place to post this. Apologies if it isn't.
Click to expand...
Click to collapse
Nice!
For the backlight, maybe you could try using system/lib/hw/lights.msm7k.so from the stock Chacha rom, or even from SuperOSR...
You cannot copy/paste an apk+odex file, it will probably never work. Try deodexing it first, then copy it.
I guess this is the right place to ask
adlx.xda said:
Nice!
For the backlight, maybe you could try using system/lib/hw/lights.msm7k.so from the stock Chacha rom, or even from SuperOSR...
You cannot copy/paste an apk+odex file, it will probably never work. Try deodexing it first, then copy it.
I guess this is the right place to ask
Click to expand...
Click to collapse
I copied lights.msm7k.so from SuperOSR, and the keyboard backlight works now.
I used an application on my laptop called xUltimate to deodex both this ROM and Chacha 1.54 stock, and the only things that wouldn't deodex are the Lockscreen and Rosie :/
Camera appears right-way round/up if a 3rd party camera app is used
Additional bugs I've noticed after trying it out a bit again:
--GPS doesn't work - I'll mess around with gps libs tomorrow when I have a bit more time
--The FM radio app's graphics are messed up
For gps try also to use stock chacha libsensors (or something like that)
the right names for the files are:
/system/lib/hw/gps.chacha.so
/system/lib/hw/sensors.chacha.so
try using the one from SuperOSR.
Is this ROM going to be official released anytime soon because I am working on a ROM from another HTC device aswell and was wondering if you needed any assistance on final touches?
TechMayhem
This would interest me greatly, as I really love the "standard" sense and was quite disappointed with the amount of white/light colours used in the ChaCha's version, and how it just doesn't seem to fit in very well at all with the HTC family. Would it be possible to use the Desire Z's rosie? As that supports landscape natively.
TechMayhem said:
Is this ROM going to be official released anytime soon because I am working on a ROM from another HTC device aswell and was wondering if you needed any assistance on final touches?
TechMayhem
Click to expand...
Click to collapse
Tbh, I haven't done anything on this for a while because I started flashing CM7/SuperOSR.
From what I can remember, the following things wern't working:
-Lockscreen - Always in Portrait, won't rotate
-Rosie - Force-close loop, had to replace with an alternate launcher
-GPS - Icon doesn't appear in the status bar
-FM/Dailer/maybe others - Graphics messed up due to forced landscape resolution
That's all I managed to check before I got caught up in crackflashing XD
I am by no means a dev - all this was done by replacing files in a Wildfire S ROM with ones from SuperOSR/stock Chacha
Atomix86 said:
This would interest me greatly, as I really love the "standard" sense and was quite disappointed with the amount of white/light colours used in the ChaCha's version, and how it just doesn't seem to fit in very well at all with the HTC family. Would it be possible to use the Desire Z's rosie? As that supports landscape natively.
Click to expand...
Click to collapse
Precisely why I tried this in the first place - I wasn't expecting all this white, which doesn't make the Chacha feel like an HTC as much to me - I already tried the Desire Z's Rosie - while it did work, all the icons were huge (because of it being scaled for HDPI screens). Dunno about widgets.
Once I find it amongst all the crap I have on my laptop, I could upload it if anyone might have an idea how to fix what's left and to see what else is broken?