I'll try to provide as much detail as possible. I am no expert (probably obvious) at theming, but I'm interested in learning. So I decided to try my hand at adding an accurate battery to Eugene373's Ginger Clone R2. Here's what I did:
1. Decompiled the framework-res.apk using the Android Theming & Tweaking v2 Alpha5 tool. This resulted in missing chunk errors with the quick_panel_list_stroke_01.9.png, status_bar_background.9.png, and status_bar_close_on.9.png.
2. I grabbed the 3 9patch files from a stock JK6 rom to replace the corrupted ones.
3. I replaced the battery icons, stat_sys_battery.xml, and stat_sys_battery_charge.xml with the ones neccessary for the mod.
4. I recompiled the apk with the same tool.
Now the battery mod works, so I doubt any of those files caused the issue, but I did notice two things. First, the file is now almost a full meg smaller than before. Second, the directory structure inside the new framework-res.apk is completely different than previously. Eugene's framework has a "-v4" extention at the end of all the drawable directories (ex: drawable-hdpi-v4 instead of drawable-hdpi).
I have a feeling that there's some fundamental difference between my compilation and Eugene's, but I had no errors at all when compiling the apk. I've tried to find the answer without bothering anyone, but all my searches have resulted in no answers. Hopefully someone out there can help with this.
TLDR version: What the heck is the difference between drawable-hdpi and drawable-hdpi-v4 (and similar directories) and is this the cause of my force closes?
Shameless bump
any one have the answer to this?
i cant find much but this help some http://forum.androidcentral.com/fascinate-roms-hacks/45526-framework-res-apk-utility.html
roscoenr said:
i cant find much but this help some http://forum.androidcentral.com/fascinate-roms-hacks/45526-framework-res-apk-utility.html
Click to expand...
Click to collapse
I have to say this guy seems to have the answer. I was unable to build a working framework at all until using this guy's app. Thank you very much for bringing it to my attention!
MWBehr said:
I have to say this guy seems to have the answer. I was unable to build a working framework at all until using this guy's app. Thank you very much for bringing it to my attention!
Click to expand...
Click to collapse
Your welcome I just hope it works I'm the same problems have not tried this to much
Sent from my unrEVOked using xda app
roscoenr said:
Your welcome I just hope it works I'm the same problems have not tried this to much
Sent from my unrEVOked using xda app
Click to expand...
Click to collapse
Well I had to manually add the "-v4" extensions to his .bat, but it really seems to be working well. Apparently it's all about packaging the new .apk, but then copying over all the new images, xmls, etc. to the original apk. Whatever it is he's doing, I applaud him for it I was just about to give up framework edits before you found this. Thanks again!
I'm glad it works cause I was in the same boat
Sent from my unrEVOked using xda app
Related
I have used APKTOOL/APK Manager Windows 7/Windows XP (x32 bit) and not having much luck with it
Basically what I am trying to do is edit the homescreen (to re-arrange icons + widgets) in 'res/xml/default_workspace.xml'
I decompile/edit/compile/upload and all I get is a black screen (I only edited 1 line to try it inside 'default_workspace.xml'.
Can anyone assist please?
Stop spamming everywhere about your problem :-/
Brut.all said:
Stop spamming everywhere about your problem :-/
Click to expand...
Click to collapse
Someone must know the answer
/they can be deleted if needs.
andrewb84uk said:
Someone must know the answer
/they can be deleted if needs.
Click to expand...
Click to collapse
Well try AXMLPrinter instead of apktool? It is sometimes better. TBH I don't like apktool too much. It's a good tool, but I prefer smali/baksmali and AXMLPrinter
anon2122 said:
Well try AXMLPrinter instead of apktool? It is sometimes better. TBH I don't like apktool too much. It's a good tool, but I prefer smali/baksmali and AXMLPrinter
Click to expand...
Click to collapse
Yeah and I really want to know, how do you want to remove some code from XML file using AXMLPrinter
Brut.all said:
Yeah and I really want to know, how do you want to remove some code from XML file using AXMLPrinter
Click to expand...
Click to collapse
Haha. good point. I wasn't really thinking as I posted (I should really be working just now ) AXML printer is good to a point, but apktool (once i got it working due to some stupid quirk on my PC which was pretty silly) does allow the extra customisation.
I should really shut up and concentrate
lol sorry mate
Since apparently BN is still changing framework.jar, I'm making a thread to allow separate updates/downloads. framework.jar for 1.0.0 is already in market hack/autonooter/autoconfig
1.0.0 - http://www.mediafire.com/?1wb78ollpb1bd78
1.0.1 - http://www.mediafire.com/?37fugab7xo8s3j3
This framework.jar helps you get an Android ID when you first run the Market. You can replace it with the stock version once your market is working if you want, but leaving it shouldn't cause any issues either.
Um, this thread is remarkably empty.
Thank you for your work!
Not having to generate ID's manually is better than awesome ...
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
johnopsec said:
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
Click to expand...
Click to collapse
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
Thanks. That makes sense now.
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
JeepFreak said:
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
Click to expand...
Click to collapse
If you want to post your framework.jar, it would probably be faster.
clockworx said:
If you want to post your framework.jar, it would probably be faster.
Click to expand...
Click to collapse
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
JeepFreak said:
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
Click to expand...
Click to collapse
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
This might not be the place or already covered, but is it possible to make the big button in the notification bar not pop up the B&N Soft Buttons? I tend to hit that far too often.
Personally if it was gone, or did nothing, I'd be happy. I can launch the apps from ADW myself, they're all individual apps anyway.
clockworx said:
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
Click to expand...
Click to collapse
Awesome man! Thanks a bunch!
Billy
clockworx,
can i replace framework.jar from slide_update.zip (BN 1.0.1) with yours
and also what i said in your other thread (supernooter) and then flash the ereader.
I am asking too many questions as i dont want to end up with an over sized 7" ice scraper...
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
We actually ended up getting the eLocity going without using the modified framework.jar.
Billy
clockworx said:
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Click to expand...
Click to collapse
nope, stock firmware, I've been trying to re-create the custom firmware that Velocity Micro made for it, but I'm having trouble figuring out exactly what settings they used for the kernel config. I'd like to eventually roll my own firmware image and update the device to either Éclair-2.1 or Froyo-2.2, but that will be awhile.
Until just now I'd never heard of Slatedroid, so i wouldn't know if anyone has succeeded over there or not. I've tried searching using Yahoo, Google and others to no avail, so...
here's the framework.jar, pulled from the most recent firmware update
(version 091257)
'mediafire'/?c76hrb1awmtc4mq
sorry 'bout the link being butchered, I'm a new user and it won't let me post links.
thanks in advance
Edit:I found the post at Slatedroid, but he's using a modded Cruz 102/103 Tablet firmware with Éclair-2.1, and until I get my own rom cooked, I'm going to try and stay as 'stock' as possible. besides, i don't know if the Cruz 103 firmware will work on the reader.
On another note, would it be possible to pre-mod the file in question if you were building from source?
and if so, what modifications would need to be made?
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
I am working with others in another thread to determine why nootering the NC removes the access to B&N instore features.
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought? Can you share what lines in the hacked framework.jar are different that the stock NC framework.jar? Would it be possible to change these lines back to stock after nootering to gain access to the instore features?
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
nikto34 said:
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought?
Click to expand...
Click to collapse
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
nikto34 said:
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
Click to expand...
Click to collapse
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
clockworx said:
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
Click to expand...
Click to collapse
Thanks for the idea! Do you have or know where to find a stock framework.jar?
As for the fingerprint issue, we have tried returning the rooted NC fingerprint back to the stock fingerprint with no success. When replicating the stock build.prop file on a rooted NC, instore features still do not work and some apps are still not available in the market.
I have created a new custom boot animation that I plan on sharing out with the crowd, however I am having issues with the animation playing during start up. I know I have the desc.txt correct as well as the naming conventions. I have tried both png and jpg sequences and to no avail.
I am zipping them up with WinRar as bootanimation.zip w/ "Store" and the compression (no compression).
I have tried all kinds of settings on these files and they just won't display and I am tired of beating my head on the keyboard. The only thing I can think of is that it has something to do with the image files themselves. I am exporting them out of After Effects as PNG sequences as well as jpg sequences and have gotten it to start running and then it just stops once it hits a certain frame. Is there any specifics that I am missing as far as settings on jpg or pngs? Is there anything special about exporting them from After Effects?
Any help would be greatly appreciated. It shouldn't be this damn difficult, but it's always the easy crap that gives the most trouble.
Awesome, 68 views and not one response.
Sent from my MB855 using Tapatalk
Can you upload the zip file I can try to take a look.
Sent from my MB855 using xda premium
http://bonzermedia.com/android/bootanimation.zip
It can be downloaded there. Thanks.
Sent from my MB855 using Tapatalk
see if this one works for you(ran it through optimizer to make it a little smaller too).
remove it from the photon-bootanimation.zip and rename it if need be and put it where it goes
dased14 said:
see if this one works for you(ran it through optimizer to make it a little smaller too).
remove it from the photon-bootanimation.zip and rename it if need be and put it where it goes
Click to expand...
Click to collapse
Holy crap it worked. What app did you use to optimize these files? (link) And were there any specific settings you used?
I swear it had to be something embedded within the file itself. I had exported from AfterEffects and then tried re-saving them using Fireworks and Photoshop with a bunch of different settings and file types, but nothing worked. I even went as far as tinkering with permissions on the files and set them all to 777. Imagine the frustration.
Thanks a ton, I greatly appreciate it. I'm going to share this one (with proper credit to your help) and I also pitched you a donation.
Cheers!
pIxiLatEd said:
Holy crap it worked. What app did you use to optimize these files? (link) And were there any specific settings you used?
I swear it had to be something embedded within the file itself. I had exported from AfterEffects and then tried re-saving them using Fireworks and Photoshop with a bunch of different settings and file types, but nothing worked. I even went as far as tinkering with permissions on the files and set them all to 777. Imagine the frustration.
Thanks a ton, I greatly appreciate it. I'm going to share this one (with proper credit to your help) and I also pitched you a donation.
Cheers!
Click to expand...
Click to collapse
Thank you for that.
And I will send you the optimizer files later(away from pc and really easy to use if your going to use pngs) as for why it didnt work is at the last line of your desc you need to hit enter (so your last line is blank after the last line of code)open the one I made in notepad++ to see what i'm talking about. I'll pm you a few tips later if you want? Thanks again for donation(saving for more phones and tabs to learn on)
?
wow, I knew it had to be something stupid. Any addl info you can toss my way would be appreciated. Thanks again and feel free to PM anytime.
pIxiLatEd said:
wow, I knew it had to be something stupid. Any addl info you can toss my way would be appreciated. Thanks again and feel free to PM anytime.
Click to expand...
Click to collapse
Glad someone was able to help and that you were able to get it to work! It looks slick!
Thanks
Sent from my MB855 using Tapatalk
Great job and the help and gesture of future help is what its all about.
Sent from my MB855 using xda premium
So far, I have downloaded the newest MIUI Rom version, and pulled the APK for Phone, Contacts, and Contacts Provider. I am not sure where to find the rest of what I need. I know how to push them to the phone, but I don't know how to make a flashable version. I tried to push them to my phone as is, and got a FC along for phone, as well as the phone app itself didn't work.
Anyone have more info and want to help?
Edit: I uploaded the files for anyone. They are from MIUI 1.10.14.
Edit 2: Here is the link with the zipped APK's and Framework. It is in my Google Docs account so it should downlod fairly quick for anyone who wants to play with it.
https://docs.google.com/viewer?a=v&...M2U4NC00NjI5LTk5MTMtY2ZjNjg5YWZiY2Iy&hl=en_US
I think u have to decompile and then recompile with correct x2 framework... Could be wrong here...
Sent from my DROID X2 using Tapatalk
No idea how to do that, that is what I am getting at. I am just providing what I have dug up to make it easy for someone who has the ability. Or, if someone can learn me what to do, I would be happy to do it myself
If I get free time tomorrow, or this week, I'll gladly see what I can do. With a son due any day I can't make any promises. I've done some of this in the past.
I can get you links to de-compiling and what not tomorrow when I have access to my laptop.
Sent from my DROID X2 using XDA App
AtLemacks said:
No idea how to do that, that is what I am getting at. I am just providing what I have dug up to make it easy for someone who has the ability. Or, if someone can learn me what to do, I would be happy to do it myself
Click to expand...
Click to collapse
Here is a link from the Fascinate group, it pretty much applies to Android in general though. It goes over the tools needed to decompile and whatnot. I'm sure there might be more to it than this, but it will get you started at least.
http://forum.xda-developers.com/showthread.php?t=932856
Wow... thanks man! Looks a little over what I am comfortable on using/testing myself on my only device. lol
Anyone comfortable with trying this?
It can be done. You will need to add all the framework resources that the apps are calling. Pull the framework from the miui build so that you know what to add.
as far as a flashable zip, can we just repackage your flashable for eclipse nitroglycerine33? When I worked on the Fascinate I just reused a theme zip to be able to flash instead of pushing.
God, how I would love to see MIUI on the X2. I actually just bought an older phone so I could run it.
I tried to upload the APK files and the Framework in 1 zip and it won't let me attach it. Says I am missing a security token. I am going to upload it somewhere else and post the link for you guys.
Added zip with framework and apk's.
Link is not working
Can any one extract these apks and post ?
Edit: This fix is defunct as of the current OTA. For a working version of this software (Thanks Steal25!) check out the thread here: http://forum.xda-developers.com/showthread.php?t=1947686
I'll be requesting this thread be closed at this point, though I'll leave the files for anyone still on older software versions. It's served it's purpose. Thanks everyone!
Original post:
There are a number of build.prop edits out there for various fixes. One such edit gives back the ability to make a choice of what program you want for a specific action. This was removed by HTC due to Apple claiming a patent infringement of patent #5,946,647. This patent is what caused the Evo 4G LTE to be stuck in customs.
Due to the nature of build.prop files containing many areas that can be tweaked, ROM devs tend to make different tweaks between ROM's. Until now this could have caused issues.
This script makes a backup of your current build.prop, and then EDITS IT IN PLACE.
What does this mean? It means you can flash THIS file on ANY ROM on this phone and it will not mess up any tweaks your specific ROM dev has put in place.
Why is this important? There are a number of build.props edited with this fix (and others)...some of them are from the stock ROM and some are from various other custom ROMs. Simply copying one over your current build.prop could lose you important optimizations, or custom fixes your dev has set up. By flashing this script you keep those customizations and still get the benefit of having your choices back.
Instructions:
To tell if this edit worked for you, check in settings. If the app associations menu option is gone, then it worked.
You will need to clear defaults for specific programs in order to have a choice pop up.
Example:
If you have selected Chrome for your default browser in app associations, you will need to go to menu/settings/apps/downloaded/Chrome/clear defaults.
The next time you tap a URL you will have a choice of which browser to use.
Credits:
Thanks to iconeo for the original thread found here: http://forum.xda-developers.com/showthread.php?t=1693809
Thanks to Steal25 for the actual build.prop edits.
I am including two zip files. The first one will make the build.prop change to allow you to choose your own defaults.
The second one (HTCLinkify-revert.zip) will allow you to put your build.prop back to its default.
There are other build.prop edits out there and I will be creating ROM agnostic flashable zips for those as well.
Please let me know if there are any issues with this flash.
Edit: I have uploaded a new zip that should work with the latest OTA.
nice man
so people can flash this and still keep their tweaks
loving the support this phone is getting
flex360 said:
nice man
so people can flash this and still keep their tweaks
loving the support this phone is getting
Click to expand...
Click to collapse
Yep, exactly. For people that have a hard time editing build.prop on their own, this will do the trick.
Plus it's the easiest way to re-implement the fix if your ROM dev updates the ROM but doesn't include it by default.
So I'm guessing you can only use this if your phone is rooted right ?
Sent from my Xoom using xda premium
MRFERRARI23 said:
So I'm guessing you can only use this if your phone is rooted right ?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You can only manually edit the build.prop if you're rooted to begin with, so even if you choose not to do it this way, you'll still need root to make the change yourself.
To flash the zip requires root and unlocked bootloader since you need a custom recovery to flash zips.
Made a correction to the first post. It was Steal25 who came up with the original build.prop edit, not SteelH. Sorry Steal25!
Mines ready fixed by me. But still, thanks mass for this.
Edit: thinking about this makes me realize just how bad apple effd HTC. I mean, if I was one of the vast majority of users who dont root and just buy a phone and leave it how it is, I would honestly probably return this device and buy something different. And that would be hard because i love HTC and this device. But, removing the 'complete action using' dialog is just not something I could live with. Apple really, really, screwed HTC... and end users. :screwy:
Sent from my EVO using xda premium
It's fantastic, thanks man.
I've been following this issue, and it seems the build.prop fix also works for other HTC ICS phones. I assume this flashable zip would work for those phones as well, correct? Since it's editing in place, seems like it should work for all (One X, One S, Amaze 4G, etc.).
thanks, was looking for this mod
oryan_dunn said:
I've been following this issue, and it seems the build.prop fix also works for other HTC ICS phones. I assume this flashable zip would work for those phones as well, correct? Since it's editing in place, seems like it should work for all (One X, One S, Amaze 4G, etc.).
Click to expand...
Click to collapse
It should, yes. However I only had an Evo 3D and an Evo 4g LTE to test on, so I can't support other phones.
But as long as build.prop is in /system and contains the line ro.da1.enable=true this script should work.
Again though I can't test, so you're on your own.
Edit: One thing though: You'll need a modified updater-script. Right now I have 2 versions of this zip, one for Shooter (Evo3D) and one for Jewel (E4GLTE).
You'll need to modify the line at the top of updater-script to your own phone's model:
getprop("ro.product.device") == "shooter"
Replace "shooter" with "jewel" for the E4GLTE for example. Or you could simply remove the line. Should work fine without it.
Ok, I may be asking a lot...
But I'm not familiar with editing the script lines,
Could you possibly either make a zip with the jewel edit in place?
Thanx
Sent from my LtEvo using XDA
KaptainRandom said:
Ok, I may be asking a lot...
But I'm not familiar with editing the script lines,
Could you possibly either make a zip with the jewel edit in place?
Thanx
Sent from my LtEvo using XDA
Click to expand...
Click to collapse
This one already has jewel. If you want it for another device I can make a quick update for you, just let me know the device name. Or if you want to test it without the device check line I'll pull that for you and you can test it that way.
Many thanks for this. Although i was able to modify fue build prop myself, i did have a hard time. Everytime i edited the build prop with root browser it made a copy of itself . Confusing stuff. Finally sorted it with SM mánager.
Anyways this is much easier for someone with my skills
Thank you
SENT FROM MY EVO LTE USING XDA
corcgaigh said:
Many thanks for this. Although i was able to modify fue build prop myself, i did have a hard time. Everytime i edited the build prop with root browser it made a copy of itself . Confusing stuff. Finally sorted it with SM mánager.
Anyways this is much easier for someone with my skills
Thank you
SENT FROM MY EVO LTE USING XDA
Click to expand...
Click to collapse
Not a problem. It will come in handy later if your ROM dev makes an update. Just flash and go.
This worked flawlessly for me. It's SO nice to have the features back that I was used to on previous devices. Thanks!
OstrichSak said:
This worked flawlessly for me. It's SO nice to have the features back that I was used to on previous devices. Thanks!
Click to expand...
Click to collapse
Glad it did the trick for you.
smw6180 said:
Glad it did the trick for you.
Click to expand...
Click to collapse
No, thank you!
Will we ever be able to long press pics in the browser and have the menu come up with share with (list of programs)
It works now!
Sent from my EVO using xda premium