Related
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'm working on a complete AOSP taskbar, however I'm having trouble with one pesky little icon (see attached). If I'm correct, then that's where the location icon should be, however for some reason it's giving me the roaming icon. Now, I'm not roaming for one thing, and for another, I have the correct .pngs in the file (sym_gpsone_[0,3]_[sprint,vzw].png in com.htc.resources.apk) but it doesn't want to use those.
Am I editing the wrong icons? Or is there another hack necessary to get it to use the correct ones?
Thanks.
What are the names of your gps icons in com.htc.resources.apk? Should be sym_gpsone_0_sprint.png and sym_gpsone_3_sprint.png. Make certain...If you can, zip up your com.htc.resources.apk and i'll take a look...
Gregalous said:
Am I editing the wrong icons? Or is there another hack necessary to get it to use the correct ones?
Thanks.
Click to expand...
Click to collapse
If you're positive that you know you're editing the correct .png file and that you aren't roaming, then next logical problem would be in the .xml programming of the taskbar...but I highly doubt many of actually mess with the code inside the .xml files.
Double check the icon and your network settings.
Take a look for yourself. It's sym_gpsone_0_sprint.png and sym_gpsone_3_sprint.png.
Gregalous said:
Am I editing the wrong icons? Or is there another hack necessary to get it to use the correct ones?
Thanks.
Click to expand...
Click to collapse
What ROM is this for? And where did you get the services.jar for it? I only ask because the same thing happened to me when I was puttin some **** together and used a .jar for Legend on Sprint(or the other way around I dont remember). Anyways, it looked exactly like that. So, you might want to check that first...
My ROM that I'll be releasing soon has, I think, all of the icons changed to their AOSP counterparts. (might be missing mail, since I don't use that apk) The headphone icons I had to derive from the black versions, but I think they look very good. (I couldn't find aosp icons for headphones??) I don't have the rest of the ROM exactly how I'd like it yet, so I'm not posting it yet... but if you'd like to look at (or steal) what I've got, you're welcome to, just send me a PM and I'll link you to it. It's highly based on the Gomorrahs Green Hero One theme, and he had most of them already fixed.
I'd also like to add that I've got the notification panel AOSP themed too, minus the carrier text color.
gomorrah said:
What ROM is this for? And where did you get the services.jar for it? I only ask because the same thing happened to me when I was puttin some **** together and used a .jar for Legend on Sprint(or the other way around I dont remember). Anyways, it looked exactly like that. So, you might want to check that first...
Click to expand...
Click to collapse
Good point, I snagged the services.jar from one of the posts in the themes thread, I think it was for one of the earlier Fresh ROM's...
I'll try a different one and see if I get different results. Thanks for pointing that out!
I want to make a minor change to the way the lockscreen looks and want to see if its something easy enough for me to do.
I'm looking to make the gray part with the dots on ether side slightly transparent. I would also like to keep the clock solid. Also not lose any of the functionality of the htc lockscreen.
Is this easy enough for someone with no theming experience to do?
Assuming you are rooted and if you are just changing images it is not difficult at all.
The lockscreen slider is actually in
/system/framework/com.htc.resources.apk
and there are 3 that start with lockscreen_arc
You need to copy the apk to your PC and open it with 7zip (my preferences) and extract the res folder to the PC. Do your graphic changes in that folder. Then reopen the apk in 7zip and drag the modified res folder over the window and drop it in.
Then you just do and adb push to put it back on the phone
You can use the same process to modify other images in the
/system/app/HtcLockScreen.apk
Changes that are not just graphics become very difficult and require de-compiling the apk to edit xml files.
AND Do a nand backup before just in case you mess up.
Awesome, sounds like a good guide. I'll post my results once I finish it.
it seems this is going to be harder than i thought.
I made the part that I wanted translucent only to find that the two pngs under it are not editable enough to remove them from behind it, so I'm left with this. I'm assuming that the only way to fix this is to do some xml editing which is a little above me.
I actually like that
If I could just get rid of the straight parts near the top of the time, I would like it. But simply editing the pngs won't cut it as I have a feeling that the xml extends the top graphic straight down because what is seen there doesn't match up with what the png looks like.
You would be correct. The problem you're running into is the 2 images behind the main lock bar are actually .9.png images and not regular .png images.
Quick, very rough explanation: To save space these images are stretched by xml files at certain points in the image to create a background. When an apk is decoded, these stretch points are represented by a 1px border around the image. This does not show up when you just use a program like 7zip.
Something to try if you want to cheat, not sure if it'll work.. Treat it all as one image instead of 3 separate ones. Make lockscreen_arc.png a taller image, and then put the top and bottom bars on it that way. Then just make the other two .9.png files completely transparent. Since it's a regular .png, it wont get stretched. I know making it smaller works out, so I'm assuming you could also make it larger.
Edit: Just thought about it some more, and that might not work, because if I had to guess, the Verizon and date text are probably set up in the xml relative to that image.
I'll mess around a little more today and see if I can't come up with something.
i also would like to do this but not the stock lock screen but this one..
To look like this...
Just the green and yellow to blue..
If all else fails, you could use the theme kitchen (http://uot.dakra.lt/kitchen). It'll allow basic changes to the whole theme (specifically the lockscreen).
Dude this thread is almost a year old and some people like to do stuff manually
-Nova's Themes and MODs for Galaxy TAB : 28DEC
Closed For business for right now. Until we get CWM.
**********************************************
I AM NOT RESPONSIBLE IF YOU OR THIS MESSES UP YOUR TAB. : )
Good to see the theming has started.
Sent from my HTC Desire
Can this be flash to Tmobile.? I know it a dum question but I want to know.
Im pretty sure this wont work for vzw tab...poked around in the files,most of the changed images are in framework/res/hdpi-v4. The path on vzw tab is framework/res/hdpi. Anyway,it was enough to scare me off. Could you tell me where those 1% increments are? Im thinking maybe battery-status.xml?I wanna pull the control file and the png's and push em into framework. Tia.
Screenshots? Also, the -v4 just means it's been decompiled.
Guys guys guys... -v4 is ok... Will work fine! lol
I am sure the framework is the same across the board. Nothing is really any different than any other 2.2 devices. No special renaming. The battery mod is a change in the battery and battery charging xml file. Instead of a img matched to a value every 20% (stock) this will display an img for every value. 205 or 125 images. In the Glass theme I have an img for every value for charging as well so it has 205 images. If you are at 22%, it will say 22% in the battery Icon. AND... This will not drain your battery any faster. This is a active Battery % Display for the Stock Icon.
Soon I will have a full Battery Mod thread with a ton of different Icons and the xmls for those who wanna use it. : )
I'm using Glass with the Magic Smoke Live Wallpaper, Looks so awesome. You must check it out. I have pics already but I'll post more and a video.
Try it!!!
:0)
Ahhh....gotcha. yeah,I noticed I got a -v4 on the end after I've used the s.c. online kitchen. Any way,recovery still exits with an error when I try to flash on vzw tab. Could it be that string in the assert command in the updater sscript? Thanks for the heads up on the XML...it got me there.
mosone23 said:
Ahhh....gotcha. yeah,I noticed I got a -v4 on the end after I've used the s.c. online kitchen. Any way,recovery still exits with an error when I try to flash on vzw tab. Could it be that string in the assert command in the updater sscript? Thanks for the heads up on the XML...it got me there.
Click to expand...
Click to collapse
Could be, ill just clear it and make it just copy. What's the s.c. Kitchen?
Sent from my SPH-P100 using Tapatalk
"Ultimate online theme kitchen"...the one with the super circle battery. Looking forward to the battery mods...thanks!
mosone23 said:
"Ultimate online theme kitchen"...the one with the super circle battery. Looking forward to the battery mods...thanks!
Click to expand...
Click to collapse
oh, lol. That's where I go to get a lot of what I do, so much easier than sitting there and editing all the xmls and hope that it recompiles right. I love using Ultra Compare and seeing what they do with that. Awesome site.
You got this to work through cw? From what I've read the assert line is no longer supported,moved on to"Edify".
mosone23 said:
You got this to work through cw? From what I've read the assert line is no longer supported,moved on to"Edify".
Click to expand...
Click to collapse
I Have fix it, this will flash in Clockwork! : )
I have also now added 10 Batt Mods for everyone. More to come soon!
Enjoy!!
The battery mods, particularly Mod #2, are nice. If I apply the images via MM into the drawable-hdpi folder, predictably it only picks up the twenty percent level ones. If I add the two XML files to the MM in the drawable folder (I used the 125 version) none of the images show up. I'm familiar with basic image replacement, but not with replacing the XML files. Is this something that would require an update.zip rather than MM?
tried the glass theme on att tab
now im stuck on samsung logo
trying to boot back up no go
thanks for trying though
BuglessFan said:
The battery mods, particularly Mod #2, are nice. If I apply the images via MM into the drawable-hdpi folder, predictably it only picks up the twenty percent level ones. If I add the two XML files to the MM in the drawable folder (I used the 125 version) none of the images show up. I'm familiar with basic image replacement, but not with replacing the XML files. Is this something that would require an update.zip rather than MM?
Click to expand...
Click to collapse
Did you use Clockwork? If your adding the images, you have to have the xmls too. xmls go in drawable.
maxtcee said:
tried the glass theme on att tab
now im stuck on samsung logo
trying to boot back up no go
thanks for trying though
Click to expand...
Click to collapse
Sorry man, I only have a sprint tab. I'll look into it more, Maybe I'll build it from each framework to make it work for all.
Nah, I was using Metamorph, which works fine for the PNGs, but somehow when it replaces the XML files in the drawables directory the battery status stops showing up altogether. I didn't have a lot of time to experiment though, so I wound up just restoring from nandroid backup. I know it must be replacing the right files, because if I run Metamorph without the XML files it perfectly places the new images, and the notification bar picks it up for the existing battery increments. If I add the XML files it winds up with a blank area where the battery status go. I'm assuming it's one of three things: MM having trouble replacing the XML files and busting something; or there's something specific to the VZW version that doesn't like one or more elments in the XML; somewhere along the lines of pulling the two XML files out of your .zip and putting them in the new .zip changed some kind of formatting (DOS v Unix linebreaks, dunno). At any rate, I can use the images easily for the 0,10,15,20,40... increments, but can't easily update the XML files with MM at the moment. I might look into doing an update.zip.
The reason I'd prefer MM for just picking up changes like battery status images, is that I don't have to worry about the framework matching, it'll just replace the files in my existing framework, so it's usually quick and dirty.
Can you see if we can get a Sprint Only Galaxy Tab Forum
Since you are a developer, Can you PLEASE look into getting the Sprint Galaxy Tab its own spot? All this Euro AT&T TMobile Galaxy Tab stuff is getting on my nerves. They need a GSM Only and a CDMA Only Tab Forum. It's too damn confusing. Appreciate it! Thx
Hi
I watched the video of the theme and at the begining you touch the upper left corner of the screen to wake up the tab. I am new to android phones and it is maybe stupid question but how to do it without pressing power-on button?
regards
Pawel
The power button is in the upper left in the video. As his thumb is at the top of the screen one of his fingers is pressing the power button. No magic swipe, sorry.
I know this is probably petty, but for me it's sort of a big deal.
I like light characters on a black screen, especially at night. There are flashlight apps to turn the screen white because it's bright and at night I would prefer to have a black screen.
Is there a way to change the conversation history to black, and lso for the background behind the balloons in an SMS?
Is there a ROM that has an option for this?
Thanks for the help!
Go sms. Totally customizable. Backgrounds, fonts, font colors, etc
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Ends said:
Go sms. Totally customizable. Backgrounds, fonts, font colors, etc
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Handcent will let you do this too.
If you get GoSMS Pro, grab the Theme builder in the market as well. It will allow you to totally create your own theme.
liquidzoo said:
Handcent will let you do this too.
If you get GoSMS Pro, grab the Theme builder in the market as well. It will allow you to totally create your own theme.
Click to expand...
Click to collapse
I should have included that I've tried all those. Yes, they're good and very customizable. But I've not been able to get them to work seamlessly and to replace the stock messaging. One of those my keyboard does't display properly with and simple other things. Plus I really like how I can go to messages and slide to the right to call. That's the easiest way to call people. That's my favorite feature and no one else has that.
What's so hard about changing the stock messaging to black with white text? lol At one point there was a night mode that made the conversation history black, but not now.
One question... For example a lock screen. There are different ones to install. Is there a different messaging to install to replace stock that someone has added things to? I don't even know if it's possible to replace messaging or not. I don't really want to install another app... I've just not had the best luck with them having the right feel.
Firstly, are you on GB or ICS? And which ROM?
If GB, you could swap out the AT&T mms.apk with the Rogers version, as they use a dark charcoal background behind matte blue and yellow bubbles (was always my favorite). Or you could try the mms.apk that Sean used to include in his GB ROMs. It was basically stock, but came with 5 themes. If you're on NexusMod GB, somewhere in the thread R4INS posted a CM7 mms.apk which has a light and dark theme.
If you're on an AOSP ICS (which I know you're not since you mention swipe to call), you could try the inverted mms.apk, which is black. If you're on stock ICS, the only thing I can think of is to just decompile the apk and use Gimp to change the colors as you'd like them (which goes for any apk really), although I think the important images are *.9.png's which are tricky. Or since you like TouchWiz, see what the T-Mobile mms.apk from their leak looks like? And if it works? As I don't know the answer to either.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I'm running ICS that I just flashed. I put in SKYICS also.
Thank you for getting back to me. I'm new to this and starting to figure things out. I opened the mms.apk with WinRar and found most of what I want to change. I've not used Gimp. For colors I usually use Office Picture Manager. I'll have to check out Gimp. I'm starting to understand a little about the xdaAutoTool. I suppose I have to decompile the mms.apk , modify what I want, then recompile it, zip it all back up, then install it through CWM. I can't get the adaAutoTool to run because of the OCX thing and I don't know how to register the files. I wish I knew someone that could decompile the apk, let me change some of the .png files and recompile it for me. I want to change the editor box from this almost black to black beause it looks incredibly grainy at 1% gray or whatever it is. The hard thing for me would be figure out how to change the text color to white if I had to on the conversation list. I think I'll do as you suggested and look for another mms.apk.
You said I like TouchWiz... I'm not exactly sure what that even is. Isn't that something to do with the buttons and how they look at the bottom?
You mentioned the CM7 something. I'm not exactly sure what the CM is. I have CM5 and it said I have a mismatch when I tried to restore my original ROM that I backed up. it was 2.3.6 I think.
Thanks for the help and I'll be back. I'm going to look for another mms.apk...
CodeRedDewd said:
I'm running ICS that I just flashed. I put in SKYICS also.
...
I'm going to look for another mms.apk...
Click to expand...
Click to collapse
I think I may have just come across a solution for you. Did you see this post in the SkyICS thread?? I'd look into that one first before attempting any of the above.
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
CodeRedDewd said:
I'm new to this and starting to figure things out. I opened the mms.apk with WinRar and found most of what I want to change. I've not used Gimp. For colors I usually use Office Picture Manager. I'll have to check out Gimp. I'm starting to understand a little about the xdaAutoTool. I suppose I have to decompile the mms.apk , modify what I want, then recompile it, zip it all back up, then install it through CWM. I can't get the adaAutoTool to run because of the OCX thing and I don't know how to register the files. I wish I knew someone that could decompile the apk, let me change some of the .png files and recompile it for me. I want to change the editor box from this almost black to black beause it looks incredibly grainy at 1% gray or whatever it is. The hard thing for me would be figure out how to change the text color to white if I had to on the conversation list. I think I'll do as you suggested and look for another mms.apk.
Click to expand...
Click to collapse
Now I'm no expert on this or anything and haven't done much research on it, so I don't know everything you're talking about. But when I manually swapped out battery icon images from framework-res.apk, I didn't do any unzipping, rezipping, decompiling, recompiling. All I had to do was *open* the archive with 7zip (NOT unzip). Delete the images in there I wanted to replace. Then drag and drop the new images into the archive. As long as they were the same names and I wasn't adding or removing any images, there was no need to change any of the XML files. And it all worked fine.
As I said though, if I recall (as I actually looked into trying to do this myself with the help of another guy -- I wanted to make the AT&T mms.apk look like the Rogers mms.apk) the background image and maybe the bubble images too are 9-patch files, which are the image_name.9.png files. They require a very special process for editing. So that might require a bit more work.
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
CodeRedDewd said:
You said I like TouchWiz... I'm not exactly sure what that even is. Isn't that something to do with the buttons and how they look at the bottom?
Click to expand...
Click to collapse
Haha something like that. TouchWiz is the graphical overlay (UI skin) Samsung puts on top of "vanilla" Android, or AOSP. Every manufacture does it. Motorola's is called MotoBlur. HTC's is called Sense. And so on. The Nexus line of phones is the only one to get stock, vanilla Android (AOSP). So it's the reason all android phones from the same manufacture look somewhat the same.
TouchWiz does consist of those buttons at the bottom and how they look (I assume you're talking about the docked apps - Phone, Contacts, Email, Apps). But it's also the system apps (Messaging, Email, Phone, Contacts, Settings, etc.) and how they look and act. The swipe right to call / swipe left to message is a feature of TouchWiz, which is why I said you liked TW because you like that feature.
---------- Post added at 06:07 PM ---------- Previous post was at 05:58 PM ----------
CodeRedDewd said:
You mentioned the CM7 something. I'm not exactly sure what the CM is. I have CM5 and it said I have a mismatch when I tried to restore my original ROM that I backed up. it was 2.3.6 I think.
Click to expand...
Click to collapse
CM stands for CyanogenMod and consists of a more AOSP feel, unlike Samsung's TouchWiz. So it doesn't have the swipe to call feature; usually just tap the contact picture inside Messaging and it gives you the option to call. CM7 was their Gingerbread build. CM9 is their Ice Cream Sandwich build.
Basically CyanogenMod has created a replacement/aftermarket firmware to replace Google Android (AOSP). It's sort of different than just a custom ROM because a custom ROM is usually just built with one phone in mind (whichever one the developer owns). CM is a firmware built the same way, with the same features, for as many phones as they can support. So your specific phone still needs to be supported and have its own specific build, but once you have it on you phone, it will look and feel just like any HTC, Motorola, etc. that is also running CM.
So it's based off of Google Android (AOSP), it's completely self-contained as its own operating system (somewhat anyway).
We have an unofficial alpha of CM9 in the development section if you want to give it a shot! (Unofficial means it's not being built by or currently supported by the actual CyanogenMod team. Just a private individual is using their source code to make it work with our Skyrocket.) It works rather well and is like 99.5% a daily driver.
Wow, thank you for that information. Some of the fuzzy things are a little clearer now but not much. lol
What you said about replacing a png - I opened the ROM in 7Zip, clicked down to the Mms.apk. I right clicked and copied to desktop. I opened that in 7Zip and dragged and dropped the png into that. I changed the file extinsion to .zip and put in on my phone. When I tried to install it though CWM touch it just aborted.
I'm not 100% sure, but I edited the png in paint. I magnified it 800 times and could see a perfect rectangle inside of this other stuff. I only made the perfect rectangle black and saved. The one I'm doing is textfield_default_dark.9.png. I don't quite think I edited it wrong since it wouldn't even install. My editing wrong would make it FC or not show right?? I don't know how to troubleshoot.
In the meantime I'm going to check out some of your other suggestions. However I would LOVE to be able to fix what I want. Why make a black that's not black and can't be displayed right by the display because the pixels are just barely on?
Suggestions on my proceedure? I read somewhere earlier that there has to be some something done to the png for permission or something strange....
I checked out the dark themed Mms.apk you mentioned at the top. This is what it says.
This is not flashable. what you'll need to do is navigate to system--> app, rename your current mms.apk to something like "mms.apk.old" or "mms.apk.bak". Then paste the attached into the same folder. Reboot your phone and voila.
I lost root access and cannot get it back when I installed SKYICS. I'm running UCLD2. I haven't been able to put together what to do about this. I tried to install my original backup and it said CM5 mismatch or something. I do believe I need root access to navigate to the system folder because I can't find it?
yeah. you need root. you dont really need to "flash" in CWM. Just replace the original in the system. But you do need root. Reboot into recovery and flash superuser
I did that a few times and nothing. I gave up on rooting for a while then now I'm rooted. Titanium, when I opened it, asked for permission. It wouldn't do that yesterday. I'm just going to have to say okay I'm rooted.
I'm trying to find the system directory right now...
CodeRedDewd said:
I'm not 100% sure, but I edited the png in paint. I magnified it 800 times and could see a perfect rectangle inside of this other stuff. I only made the perfect rectangle black and saved. The one I'm doing is textfield_default_dark.9.png. I don't quite think I edited it wrong since it wouldn't even install. My editing wrong would make it FC or not show right?? I don't know how to troubleshoot.
Click to expand...
Click to collapse
Yea so like I said, since it's a 9-patch file (*.9.png), I'm not sure if you can just edit the image and throw it back in there. I'm guessing that Paint only recognizes it as a *.png, and so saves it as such. 9-patch images need to be recompiled, as far as I know. So that might've screwed you up, even if you installed it right.
CodeRedDewd said:
What you said about replacing a png - I opened the ROM in 7Zip, clicked down to the Mms.apk. I right clicked and copied to desktop. I opened that in 7Zip and dragged and dropped the png into that. I changed the file extinsion to .zip and put in on my phone. When I tried to install it though CWM touch it just aborted.
Click to expand...
Click to collapse
So about installing it. Everything above sounds like the correct process EXCEPT for changing the file extension. A CWM flashable zip isn't just any old zip file. It's has a certain structure to it and includes a script file that tells CWM exactly what to do with the information contained inside the zip. With a system apk, all you need to do is get the file on your phone somehow (microSD, USB cable, Dropbox, etc.), and then copy and paste it into the /system/app directory, afterwards setting its permissions to rw-r--r--. To do this, yes you will need root access. It shouldn't be that hard to just root again if you lost it somehow. Or judging by your last post, you may have successfully rooted again.
CodeRedDewd said:
I checked out the dark themed Mms.apk you mentioned at the top. This is what it says.
This is not flashable. what you'll need to do is navigate to system--> app, rename your current mms.apk to something like "mms.apk.old" or "mms.apk.bak". Then paste the attached into the same folder. Reboot your phone and voila.
I lost root access and cannot get it back when I installed SKYICS. I'm running UCLD2. I haven't been able to put together what to do about this. I tried to install my original backup and it said CM5 mismatch or something. I do believe I need root access to navigate to the system folder because I can't find it?
Click to expand...
Click to collapse
Which brings us back to this mms.apk. Definitely give this app another shot using the above method once you obtain root again. You will need an app such as Root Explorer, which can be downloaded from the Market.
As far as restoring your backup, the error you received was an MD5 checksum mismatch error. You can Google what MD5 means, and possible reasons why CWM gave you that error. I think it gives it to you sometimes when you rename a backup file and put a space in the file name.
I'll have to research that MD5 thing...
I got the Mms.apk copied to the right directory and my changes worked. I have to use something other than paint that allows me to keep white as the transparant color. This is pretty awesome... Maybe I'll post my result when I figure out what's going on. I'm thinking the text field is a box within a box. I got a black box with a very dark gray one in the middle... But it's progress! Thanks for your help!
CodeRedDewd said:
I'll have to research that MD5 thing...
I got the Mms.apk copied to the right directory and my changes worked. I have to use something other than paint that allows me to keep white as the transparant color. This is pretty awesome... Maybe I'll post my result when I figure out what's going on. I'm thinking the text field is a box within a box. I got a black box with a very dark gray one in the middle... But it's progress! Thanks for your help!
Click to expand...
Click to collapse
That's awesome man, good job! Wanna post a screenshot for me? A before and after if you have it?
But if you need something better than Paint, I'd look into Gimp. It's what most of the guys on here use. It's basically the Linux version of Photoshop. And being Linux, it's free and open source... and has been ported over to Windows. It works great for quick image editing. Just takes a bit of Googling to learn all the buttons haha.
I'm using Gimp because it keeps the transparant background. I had a big white box around my box from paint.
Update: When I used paint, it seemed things worked correctly besides the white box around the editor. The transparancy was lost. In Gimp, if I change 1 pixel I get a whole distorted image for the editor. In paint, I made the blue line gold and the box black. That looked great. Nothing seems to be working right with Gimp. Wait, in Paint I did notice one thing. The box was a true black, but with a lighter black, wide stripe in the middle from end to end, as if it was another png inserted into it. Hmmm... In Gimp it looks like nothing is getting inserted and the small image is stretching all the way across with the thin blue line getting super fat. I didn't jack the image up. I only changed one pixel to red in the middle of the black. I'm thinking there's more to this. Someone posted something about a decompiled image that had extra dots around the edge and one a one pixel line on two sides or something. I didn't break anything, because I put in an untouched png and it fixed things, so it's just the image.
Any ideas? I'm headed out to watch a movie, but I'm determined.
Look for a brush diameter or feathering option in Gimp and change it to the smallest one you have. I've had to do that in both Photoshop and Gimp before to get the apk changes I've made to look right and not have that outlining that you're referring to.
I understand what you mean, but this is different.The .9.png looks exactly the same when I edit it. I'm just making it darker. The .9.png files are made of 9 sections taht are stretched individually so the image is not distorted. In my case, Gimp is destroying that ability and the image is getting stretched the wrong way when displayed. For example, if you stretch a line along its lengt it still looks like the same line only longer, which is what they do. But if you stretch it across its width, it becomes this fat line, which is what is happening in my case.
I think you're editig just .png and not .9.png files?
CodeRedDewd said:
I understand what you mean, but this is different.The .9.png looks exactly the same when I edit it. I'm just making it darker. The .9.png files are made of 9 sections taht are stretched individually so the image is not distorted. In my case, Gimp is destroying that ability and the image is getting stretched the wrong way when displayed. For example, if you stretch a line along its lengt it still looks like the same line only longer, which is what they do. But if you stretch it across its width, it becomes this fat line, which is what is happening in my case.
I think you're editig just .png and not .9.png files?
Click to expand...
Click to collapse
Do you think some information in this tutorial could be of any help? There's also a video tutorial available.
Yes it's possible that would be very helpful. I found either that or another tutorial last night. It was interesting how the .9.png files are sectioned. I conda figured that out on my own, because it would have to be to get bigger and not distort fine lines. I'll have to find that tutorial itself, because that post you linked has no links in it. I went to a 9patch website or something that had all the stuff, but it got too deep pretty quickly. In the short time I studied it, I had no clue how to even begin to install and use the program.
What baffles me is how Paint didn't screw up the .9.png. It worked fine with my edits, only it had no transparency so there was a white border. It was able to scale fine to landscape and portrait. It looked great. I totally though I had it figured out. :/ Have you looked at how to do .9.png files?
CodeRedDewd said:
Yes it's possible that would be very helpful. I found either that or another tutorial last night. It was interesting how the .9.png files are sectioned. I conda figured that out on my own, because it would have to be to get bigger and not distort fine lines. I'll have to find that tutorial itself, because that post you linked has no links in it. I went to a 9patch website or something that had all the stuff, but it got too deep pretty quickly. In the short time I studied it, I had no clue how to even begin to install and use the program.
What baffles me is how Paint didn't screw up the .9.png. It worked fine with my edits, only it had no transparency so there was a white border. It was able to scale fine to landscape and portrait. It looked great. I totally though I had it figured out. :/ Have you looked at how to do .9.png files?
Click to expand...
Click to collapse
The tutorial is contained in the OP of that post I linked to. It contains links for all the tools you need and a short description of the process to follow. And then I think the video tutorial might just guide you through the OP of that first link.
But yea, that's really interesting how Paint worked so well. Did you happen to take any screenshots of the Paint-edited apk running on your phone?
And no, I actually have never looked into editing .9.png files. Didn't really even know how they worked until you explained them a little bit in one of the above posts.
I attached an image. I'm not sure if it's going to show up in the post as an image; we'll see.
There is a white box around what is suppose to be shown as the editor. In the center of the black box it's not true black as the black surrounding it that I changed in the .9.png. The center must be another image.
I'm thinking I'm just going to make the white black, find the other gray images the buttons are on and make that one black. Who needs transparancy when it's all black, which is what I want anyway. lol
I'm going to look into the 9patch some more... It just seems so complicated with how to install and get working. It would be nice to work with someone who is actively editing .9.png's to get me on track....
Do you have an interest in editing those png's? lol