Related
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.
Does anyone know how to speed up the window animation speed in the ROM without using Spare Parts? How to cook it into the ROM?
scrosler said:
Does anyone know how to speed up the window animation speed in the ROM without using Spare Parts? How to cook it into the ROM?
Click to expand...
Click to collapse
Great question. The quickest method which came to mind was to use look at the Spare Parst app source code and find how its controlling the window animation speed.
I purely speculate, there are two ways of controling window animation speed.
1) modifying a setting in a preference file in /data.
2) setting something in the android system via java.
Unfortunately the master source would be android.git.kernel.org (specifically http://android.git.kernel.org/?p=platform/development.git;a=tree;f=apps/SpareParts;hb=HEAD ) but the server is still offline. I'm not able to quickly find the Spare Parts app source code through google searching. If somebody does have a link to the online source code for Spare Parts, I'd be interested in taking a look and seeing how it works!
The only semi helpful link I could find is an older XDA thread: http://forum.xda-developers.com/archive/index.php/t-708774.html . Unfortunatley it appears he has taken his github files offline so I wasn't able to find the Spare Parts java source code.
Sorry for not having a specific answer but hopefully the ideas provide a lil more guidance!
joeykrim said:
Great question. The quickest method which came to mind was to use look at the Spare Parst app source code and find how its controlling the window animation speed.
I purely speculate, there are two ways of controling window animation speed.
1)modifying a setting in a preference file in /data.
2) setting something in the android system via java.
Unfortunately the master source would be android.git.kernel.org (specifically http://android.git.kernel.org/?p=platform/development.git;a=tree;f=apps/SpareParts;hb=HEAD )but the server is still offline. I'm not able to quickly find the Spare Parts app source code through google searching. If somebody does have a link to the online source code for Spare Parts, I'd be interested in taking a look and seeing how it works!
The only semi helpful link I could find is an older XDA thread: http://forum.xda-developers.com/archive/index.php/t-708774.html . Unfortunatley it appears he has taken his github files offline so I wasn't able to find the Spare Parts java source code.
Sorry for not having a specific answer but hopefully the ideas provide a lil more guidance!
Click to expand...
Click to collapse
Thanks for looking into this. I will post back if I find anything but as of now I havent found squat.
scrosler said:
Does anyone know how to speed up the window animation speed in the ROM without using Spare Parts? How to cook it into the ROM?
Click to expand...
Click to collapse
Gotcha.
Add (or edit that number..higher=faster) this line in the build.prop:
windowsmgr.max_events_per_sec=100
(MAKE SURE there's still a blank line at the end of all your build.prop tweaks, or it won't "take".)
<<bringing it since 2010>>
mazook98 said:
Gotcha.
Add (or edit that number..higher=faster) this line in the build.prop:
windowsmgr.max_events_per_sec=100
(MAKE SURE there's still a blank line at the end of all your build.prop tweaks, or it won't "take".)
<<bringing it since 2010>>
Click to expand...
Click to collapse
Thanks man!
Is there a max?
Gonna try 300 now...
scrosler said:
Thanks man!
Is there a max?
Click to expand...
Click to collapse
Lol... It gets wonky over 110 in most roms.. In fact, 100 is at the high range. Most chef's that add this usually come in about 90, but I've never had issues with 100.
LMK how it works for you.
<<bringing it since 2010>>
mazook98 said:
Lol... It gets wonky over 110 in most roms.. In fact, 100 is at the high range. Most chef's that add this usually come in about 90, but I've never had issues with 100.
LMK how it works for you.
<<bringing it since 2010>>
Click to expand...
Click to collapse
Yea, I was rocking 100... But... When I changed it up to 200 nothing changed. Gonna drop down very low to test theory.
Something that SpareParts+ is doing is making it haul ass. Much faster than what it is now.
Changed to 50 and see no difference. Hmmm.....
Are you clearing Dalvik in between changes? (If, that is, you're in one of your awesome deodexed roms?)
I think all your apps are opted in relation to build.prop guidelines, so that would be needed.
<<bringing it since 2010>>
mazook98 said:
Add (or edit that number..higher=faster) this line in the build.prop:
windowsmgr.max_events_per_sec=100
(MAKE SURE there's still a blank line at the end of all your build.prop tweaks, or it won't "take".)
Click to expand...
Click to collapse
scrosler said:
Changed to 50 and see no difference. Hmmm.....
Click to expand...
Click to collapse
wasn't much information provided on what this build.prop line edit actually does or how android implements the number values. so researched this setting - windowsmgr.max_events_per_sec.
first found an older thread on XDA about it. they claim you can adjust the value after boot but it won't change anything until after a reboot. i.e. setprop *should* work on changing the value, but won't have any impact. seems have to edit/save actual build.prop and restart.
also they state 55 is the default value and the android framework doesnt recognize values under 35.
they also say: "That value does not affect the framerate, but how many touch events are reported to the apps; this saves some cpu if the user keeps touching the screen." all this information is taken from this thread - http://forum.xda-developers.com/showthread.php?t=813309
read on another forum post, "To enable better scrolling speed through lists, I changed windowsmgr. max_events_per_sec=55 to windowsmgr.max_events_per_sec=60. Scrolling through the app drawer and contacts and any lists really is now smoother. " - http://androidforums.com/droid-x-all-things-root/164447-mod-lots-build-prop-edits.html
not able to find anything from google/android developers to reference as an "official" source .. maybe a grep through aosp code could reveal where android reads and implements this build.prop setting change.
hopefully some of that information helps sheds a bit more light on this "tweak", i.e. default value, range, areas it will impact, etc.
After reading your post I would believe this is not the golden egg I am looking for. Im going to decompile SpartParts+ and see what, if anything I can find by poking around.
mazook98 said:
Are you clearing Dalvik in between changes? (If, that is, you're in one of your awesome deodexed roms?)
I think all your apps are opted in relation to build.prop guidelines, so that would be needed.
<<bringing it since 2010>>
Click to expand...
Click to collapse
No, I didnt clear cache but I can try... Cant hurt, right? I just dont think this the correct mod... But what the heck/.... Lets see if clearing any thnig helps.
Nope, nothing.
scrosler said:
After reading your post I would believe this is not the golden egg I am looking for. Im going to decompile SpartParts+ and see what, if anything I can find by poking around.
Click to expand...
Click to collapse
first approach which comes to mind: i'd prob grep through there looking for any strings regarding window animation speed. i forget what it is called in the real app, but that is probably a great starting point. then start back tracing the code .. i don't deal much with smali but i'm sure you'll be able to trace it down.
keep us updated!
scrosler said:
Nope, nothing.
Click to expand...
Click to collapse
Sorry to sidetrack you Scott!
I "thought" I knew what I was talking about...
Good luck in the effort, bro.
(and I'll also stop editing that line into every single build.prop I see, lol.)
Thanks for the work.
<<bringing it since 2010>>
joeykrim said:
first approach which comes to mind: i'd prob grep through there looking for any strings regarding window animation speed. i forget what it is called in the real app, but that is probably a great starting point. then start back tracing the code .. i don't deal much with smali but i'm sure you'll be able to trace it down.
keep us updated!
Click to expand...
Click to collapse
That was my plan of attack.. somewhat.. Lets see how complicated the code is in this... iM hoping its using an echo command or something similar... Because the speed change sticks after a reboot so wouldn't that indicate its writing to a file?
mazook98 said:
Sorry to sidetrack you Scott!
I "thought" I knew what I was talking about...
Good luck in the effort, bro.
(and I'll also stop editing that line into every single build.prop I see, lol.)
Thanks for the work.
<<bringing it since 2010>>
Click to expand...
Click to collapse
Its all good man. Atleast you tried.
scrosler said:
That was my plan of attack.. somewhat.. Lets see how complicated the code is in this... iM hoping its using an echo command or something similar... Because the speed change sticks after a reboot so wouldn't that indicate its writing to a file?
Click to expand...
Click to collapse
yea, i would agree. wish i had taken a look at the spare parts source code when it was posted on the android aosp site!
i doubt its using echo to send a value to a sysfs file generated by the kernel. my guess would be to a data settings file on the /data partition. at least thats what i'd hope as that would be easy to duplicate!
if you want to post up the smali files, i can try and take a look through. yay for java being so easy to reverse!
joeykrim said:
yea, i would agree. wish i had taken a look at the spare parts source code when it was posted on the android aosp site!
i doubt its using echo to send a value to a sysfs file generated by the kernel. my guess would be to a data settings file on the /data partition. at least thats what i'd hope as that would be easy to duplicate!
if you want to post up the smali files, i can try and take a look through. yay for java being so easy to reverse!
Click to expand...
Click to collapse
Related dumb (awesome) geek joke:
Q: Why do all Java developers wear glasses?
.
.
.
A: Because they can't C#.
(ba dump bump).
<<I first learned about binary from Pac Man>>
Ill drop you a pm for this when I get home. It is NOT the build prop edit posted earlier. That has ZERO to do with animation speed.
SteelH said:
Ill drop you a pm for this when I get home. It is NOT the build prop edit posted earlier. That has ZERO to do with animation speed.
Click to expand...
Click to collapse
Thanks man! As always your tutorials make my ROM! They are unbeatable!
I thought it might be cool if we could set the native Sense updater (In Settings>System Updates) to check for/download/install updates to roms. It would have to be modified for each rom, but probably not that hard. I did a little digging in Settings.apk, but couldn't find anything, so I started looking in Updater.apk. That is where the gold is. Everything that has to do with FOTA, System updates, anything about that is in there. On a side note, there is a smali file called PesterActivity.smali that we may be able to modify so that we don't get the notifications. Anyway, I just thought I would point the idea out so that if anyone else wants to start on it we can get it done quicker.
correct me if im wrong, but wouldn't the updater check the digital signature on the file before a flash?
koszor said:
correct me if im wrong, but wouldn't the updater check the digital signature on the file before a flash?
Click to expand...
Click to collapse
I think we could set it not to. Everything that happens inside an update can be tweaked from that app I believe.
even if we did though it couldnt give S-off could it?
This is (I assume) an idea for future use. Hope I'm not putting words in OP's mouth.
Sent from my ADR6425LVW using xda premium
YamiYaiba said:
This is (I assume) an idea for future use. Hope I'm not putting words in OP's mouth.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yup. I'm working on it, but have nothing atm
Personally, I think it's a great idea. Checking for updates would be a lot easier lol
Isn't this already do-able through Rom Manager?
Zaphod-Beeblebrox said:
Isn't this already do-able through Rom Manager?
Click to expand...
Click to collapse
Assuming your ROM is on Rom Manager. I've never once used one that was.
YamiYaiba said:
Assuming your ROM is on Rom Manager. I've never once used one that was.
Click to expand...
Click to collapse
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Zaphod-Beeblebrox said:
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Click to expand...
Click to collapse
I personally don't use Rom manager, as I feel that you have more control ovrer the flashing. I have also heard stories of rom manager bricking your phone, and never felt like risking it.
Sent from my ADR6425LVW using Tapatalk
Zaphod-Beeblebrox said:
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Click to expand...
Click to collapse
the biggest problem. with rom manager in my opinion.. is that it's connected only to cwr, which sucks.
dmeadows013 said:
I thought it might be cool if we could set the native Sense updater (In Settings>System Updates) to check for/download/install updates to roms. It would have to be modified for each rom, but probably not that hard. I did a little digging in Settings.apk, but couldn't find anything, so I started looking in Updater.apk. That is where the gold is. Everything that has to do with FOTA, System updates, anything about that is in there. On a side note, there is a smali file called PesterActivity.smali that we may be able to modify so that we don't get the notifications. Anyway, I just thought I would point the idea out so that if anyone else wants to start on it we can get it done quicker.
Click to expand...
Click to collapse
Thats actually a good idea. I never thoguht of that! I am going to look into it.
In my Optimus and Evo 3D ROMS I have a custom App called ROM Updater. It does exactly what you are talking about but also includes themes, ringtones, etc. And its all stored on my server and downloads to SD card then flashes.
But how cool would it be to just do updates using the HTC Built in app? I like this idea...
Here are the challanges that I see...
1. We need to to be able to get the file from the server that it parses to verify if the current version is correct. Not sure how hard that would be. We would not only need to get it but hope its in json or xml or some other human readable form so we can decipher and rebuild it.
2. Redirection to a third party server. Can it be done? I assume so. I know how to stop it from checking by nuerting the build prop so why not use the same lines to direct to another server?
Have you decompiled the APK and looked at strings.xml? Any info in there?
werdna87 said:
even if we did though it couldnt give S-off could it?
Click to expand...
Click to collapse
No... Wouldnt really do anytyhing until we had S-OFF...
koszor said:
correct me if im wrong, but wouldn't the updater check the digital signature on the file before a flash?
Click to expand...
Click to collapse
Not with a custom Reocovery. It would work fine.
YamiYaiba said:
Assuming your ROM is on Rom Manager. I've never once used one that was.
Click to expand...
Click to collapse
Zaphod-Beeblebrox said:
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Click to expand...
Click to collapse
androidsupra said:
the biggest problem. with rom manager in my opinion.. is that it's connected only to cwr, which sucks.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I wont go into my ROM Manager rant like I always do... But I will just say this to answer your questions...
1. It cost nothing to put your ROM in ROM Manager
2. For a user to be able to download your submitted ROM they have to pay Koush. To me... That is so not cool he is taking cash for other Dev's ROMS. I am not fan of that.
I had one of my ROMS in ROM Manager and I was not happy to see it there. What sent me into a rampage is that someone that liked my ROM posted it in ROM manager without my permission. He accepts work from anyone with no verifiection of the author (Security Issue anyone?).
Anyways.. thats a very short synapsis of my feelings of ROM Manager.
-Scott
I looked into Strings.xml and couldn't find anything useful. I also looked into a few other .xmls and some smali files. I think that everything used to get the file downloaded is in the smalis. Not sure though, I'm not the best with smali. Strings just showed some user messages.
dmeadows013 said:
I looked into Strings.xml and couldn't find anything useful. I also looked into a few other .xmls and some smali files. I think that everything used to get the file downloaded is in the smalis. Not sure though, I'm not the best with smali. Strings just showed some user messages.
Click to expand...
Click to collapse
Yeah, most of the time the guts is in the smali but every once in a while you can find the goods in the XML's.
How many total smali files?
scrosler said:
Yeah, most of the time the guts is in the smali but every once in a while you can find the goods in the XML's.
How many total smali files?
Click to expand...
Click to collapse
I counted 103 total.
dmeadows013 said:
I counted 103 total.
Click to expand...
Click to collapse
Thats it? Thats nothing at all to look through...
Here is where I would start....
First... Look at the device build prop. Thats gioing to have the URL's of the HTC Update servers.
Second... Start searching out for either....
a) the name of those servers in the smali code
b) any strings like ".xml", ".json", "http://", "https://", ".zip" anything that would make sense (no pun).
This is just what I would do.
What are yo using for OS and app on your PC?
scrosler said:
Thats it? Thats nothing at all to look through...
Here is where I would start....
First... Look at the device build prop. Thats gioing to have the URL's of the HTC Update servers.
Second... Start searching out for either....
a) the name of those servers in the smali code
b) any strings like ".xml", ".json", "http://", "https://", ".zip" anything that would make sense (no pun).
This is just what I would do.
What are yo using for OS and app on your PC?
Click to expand...
Click to collapse
Found this in build.prop
Code:
# For FOTA setting (leave empty value to use default)
ro.htc.checkin.url = http://andchin.htc.com/android/checkin
ro.htc.checkin.crashurl = http://andchin.htc.com/android/crash
ro.htc.checkin.url_CN = http://andchin.htccomm.com.cn/android/checkin
ro.htc.checkin.crashurl_CN = http://andchin.htccomm.com.cn/android/crash
ro.htc.checkin.exmsg.url = http://fotamsg.htc.com/android/extra/
ro.htc.checkin.exmsg.url_CN = http://fotamsg.htccomm.com.cn/android/extra/
ro.htc.appupdate.url = http://apu-chin.htc.com/check-in/rws/and-app/update
ro.htc.appupdate.url_CN = http://apu-chin.htccomm.com.cn/check-in/rws/and-app/update
ro.htc.appupdate.exmsg.url = http://apu-msg.htc.com/extra-msg/rws/and-app/msg
ro.htc.appupdate.exmsg.url_CN = http://apu-msg.htccomm.com.cn/extra-msg/rws/and-app/msg
ro.config.htc.nocheckin = 1
I'm on Mac OSX 10.7 and am using Text Wrangler. I also have a Win7/Ubuntu 11.10 dualboot machine.
dmeadows013 said:
Found this in build.prop
I'm on Mac OSX 10.7 and am using Text Wrangler. I also have a Win7/Ubuntu 11.10 dualboot machine.
Click to expand...
Click to collapse
Now what you want to do is start searching the smali copde for similiar stings that are in the buildprop.
See, from my understanding, the updater looks at those build prop strings to determine where to look for and download updates.
I am assuming you have the APK decompiled?
I dont know much about Mac, a little about Ubunut but a lot about Win7.
I use Notepadd++ on Win 7 to edit smali...
What I would do next is load up the smali folder in notepadd ++. Easiest way to do this is go to the smali folder and do a search for *.smali.... when it finds them all, selct them all and choose open in Notepad++
I can get about 150 to 200 smali files open in N++ before it crashes, hehehehe
From there Notepad++ can search across all open files. I would start searching out those strings I noted and the strings in the build prop. Not sure what you will find if anything but it would be interesting to see. If you do it post any pertinent results and the file you found it in.
I'll give it a shot to but dont get out of work for another couple hours and I work 50+ hours a week for the next two weeks so time is limited but I want to see what we can figure out.
scrosler said:
Thats it? Thats nothing at all to look through...
Here is where I would start....
First... Look at the device build prop. Thats gioing to have the URL's of the HTC Update servers.
Second... Start searching out for either....
a) the name of those servers in the smali code
b) any strings like ".xml", ".json", "http://", "https://", ".zip" anything that would make sense (no pun).
This is just what I would do.
What are yo using for OS and app on your PC?
Click to expand...
Click to collapse
Found these:
In UpdaterNetworkCheck.smali
Code:
Line 13: .field private static final TEST_ADDRESS:Ljava/lang/String; = "http://apu-stage.htc.com/apu-stage/"
Line 15: .field private static final TEST_ADDRESS2:Ljava/lang/String; = "http://masd.htc.com.tw/"
Line 256: const-string v6, "http://apu-stage.htc.com/apu-stage/"
Line 308: const-string v6, "http://masd.htc.com.tw/"
Found none of the URLs. However, when looking for .zip, there was a reference to /system/etc/security/otacerts.zip. Looked inside, and it showed a release key. Looked like this:
Code:
-----BEGIN CERTIFICATE-----
MIIEnzCCA4egAwIBAgIJAIb8SbYq46gHMA0GCSqGSIb3DQEBBQUAMIGRMQswCQYD
VQQGEwJUVzEPMA0GA1UECBMGVGFpd2FuMRUwEwYDVQQHEwxUYW95dWFuIENpdHkx
GDAWBgNVBAoTD0hUQyBDb3Jwb3JhdGlvbjEMMAoGA1UECxMDU1NEMREwDwYDVQQD
EwhIVEMgQ2VydDEfMB0GCSqGSIb3DQEJARYQSHRjX0NlcnRAaHRjLmNvbTAeFw0w
ODA5MDEwODUwNTZaFw0zNjAxMTgwODUwNTZaMIGRMQswCQYDVQQGEwJUVzEPMA0G
A1UECBMGVGFpd2FuMRUwEwYDVQQHEwxUYW95dWFuIENpdHkxGDAWBgNVBAoTD0hU
QyBDb3Jwb3JhdGlvbjEMMAoGA1UECxMDU1NEMREwDwYDVQQDEwhIVEMgQ2VydDEf
MB0GCSqGSIb3DQEJARYQSHRjX0NlcnRAaHRjLmNvbTCCASAwDQYJKoZIhvcNAQEB
BQADggENADCCAQgCggEBANB9rS8wBMSZGEACPSvdQajFRPz9QPDyF26aI+W5xL7E
QX66/drzSntU0zu+M2qLBo16DYqH3irf0Pe/tvOrD3SwdTT5q25BM0tI2cEsEgR6
cw1MgEP9FvYUKhBRgqxjRXgKzdgptWSxohdli/Iq6garZhbHr0tERA1V/w3Vnj/L
hVHPdHje2svE5cGKELq+0OOZlo77jQDvXVRmdABlQrUfgam5vtYipihUY6pc1iId
yi5K8sj+KXpIcU5NMa7b1YqTfzJOdCl6BCZiZBr3JRwdC8F/J7yWlZyFtYlqKjPo
kG35rLqInp3116e195b8SJXUQflstmyN+Yv686eEhlsCAQOjgfkwgfYwHQYDVR0O
BBYEFObseus3M5qqC/iaRg7V9gTQ0KbyMIHGBgNVHSMEgb4wgbuAFObseus3M5qq
C/iaRg7V9gTQ0KbyoYGXpIGUMIGRMQswCQYDVQQGEwJUVzEPMA0GA1UECBMGVGFp
d2FuMRUwEwYDVQQHEwxUYW95dWFuIENpdHkxGDAWBgNVBAoTD0hUQyBDb3Jwb3Jh
dGlvbjEMMAoGA1UECxMDU1NEMREwDwYDVQQDEwhIVEMgQ2VydDEfMB0GCSqGSIb3
DQEJARYQSHRjX0NlcnRAaHRjLmNvbYIJAIb8SbYq46gHMAwGA1UdEwQFMAMBAf8w
DQYJKoZIhvcNAQEFBQADggEBAIfnfzMduLfgX5JCGtQ9gDsb84S6AkX7oxFA4c+T
MBqcLjwiZj168I/PB/WWMwYQls5vZnMrHCcQpz7YReK5l+DbErDE5FhqveyuhqIE
nCLJm+0bXuKdBJtjH77n8owACtafiOMBI/Ju4RKINxjLiRe1jYSwzsWcLEadWls6
bbYKbUMAdsRmH3IHkJnqwIxzsE7/TLdWCCqqVrc4aT2KvntnPG/zKL8uZuySeEmJ
ybmQeQ3D50vcNicPTVFnd43oNHUFNzdN0IKz3VedL8h/HmVqP+qoQGWaU+QF7T/y
7GpVtwjbaRo0v3aPH6t1lwxQphLHdykvt7cBzW1CGciJYcE=
-----END CERTIFICATE-----
Doubt the key would be useful, but you never know...
Hello.
I am running stock ICS 4.0.4, and would like to change my phone's operator text to my own, custom text (for example, change "T-Mobile" to "BagelDog"). I have already tried an app named "Carrier Name" which did not work. Has anyone successfully achieved this result on their I777 and can share the solution?
Thanks.
Without root at the very least that'd probably not be achievable .
My phone is rooted.
Oh well then you can definitely do it. May have to get a little technical if you don't want a simple app fix though.
Technical is fine, I'm no stranger to it. Could you provide the steps, please?
BagelDog said:
Technical is fine, I'm no stranger to it. Could you provide the steps, please?
Click to expand...
Click to collapse
First, you must discover where the text you want to change is located. I'd guess it's somewhere in the framework, maybe in system ui, but I don't really know. Then you need to learn how to edit that file or collection so that you can change the text. It may require decompiling and recompiling something, depending on where it is. Sounds like you have some study time ahead of you. These would be the first steps in becoming an android developer. If it sparks your interest, you might go down that path.
Happy hunting.
Dear All,
Recently got a Chinese phone from the net running ICS. I set the language to English, but some cuneiform text appears below the name of the people calling me. Is there any way to fix this?
theblackalchemist said:
Dear All,
Recently got a Chinese phone from the net running ICS. I set the language to English, but some cuneiform text appears below the name of the people calling me. Is there any way to fix this?
Click to expand...
Click to collapse
Other than a custom rom or knowing how to decompile the apps and edit out the coding, probably not. Only possible easy solution that might or might not (probably not...) would be to make sure the locale is set to an English speaking country using something like this: https://play.google.com/store/apps/details?id=com.bruce.setlocale
Thanks.
I am not intimidated my code as such (fluent in c++) but it'll take some time to understand android... Any idea which app I should look at? considering android is open source, I can probably patch the change in, create a replacement app and see if that works...
KR
TBA
theblackalchemist said:
Thanks.
I am not intimidated my code as such (fluent in c++) but it'll take some time to understand android... Any idea which app I should look at? considering android is open source, I can probably patch the change in, create a replacement app and see if that works...
KR
TBA
Click to expand...
Click to collapse
It's most likely either in something like a LocationProvider.apk (/system/apps) or the phone/dialer apk. If you are rooted, I'd try and free the LocationProvider,apk and see if that doesn't help. Try the easy stuff first. But I'd poke around in a thread like this: http://forum.xda-developers.com/showthread.php?t=1891962 or something similar that deals with this idea on porting Chinese roms to English.
Or you could just be lazy and see if installing another Contact/Dialer app from the Play Store just circumvents the whole deal.
Already tried using a caller id app, its more of a hit and miss... I was wondering what would happen if I just happen to replace the apps you mentioned from those of stock android? does that make sense?