[APP] BraviaControl: Control your Sony Bravia Smart TV - Windows Phone 7 Apps and Games

Download from the Store.
I purchased a Sony Bravia KDL-40EX525 a few months ago and noticed that there were official remote control apps for Android and iPhone from Sony but, unfortunatelly, not for WP7 (not even an unofficial one). Since I own a LG Optimus 7 I got curious about this and started to develop something similar for myself, specifically because I hate using the stock remote control to enter text.
I based my work on this blog post http://blogs.msdn.com/b/andypennell...ws-phone-7-5-mango-part-1-ssdp-discovery.aspx. Many thanks to Andy Pennell for that, his post was really helpful and a great starting point.
The app requires you to be on the same network as the TV.
If you want to try this make sure the TV is ON (give it time to initialize the services. It cannot be turned on/off with this app because it has to talk to the IRCC service that is only available when the device is ON). See the screen of your TV the first time you run the app because it requires that you register your device in order to be able to iterate.
I appreciate your feedbacks, suggestions, bug report or questions that you may have.
Tested on models:
- KDL-40EX525 (mine)
- KDL-32HX758 (thanks lordmaxey)
It should work on:
- Blu-ray Disc(TM) players: BDP-S370, S470, S570, S770, S1700, BX37, BX57, S380, S480, S580, S780, BX38, BX58, S390, S490, S590, S790, BX39, BX59, NSZ-GP9
- Blu-ray Disc(TM) Home Theater Systems: BDV-IZ1000W, HZ970W, E970W, E870, E770W, E670W, E570, E470, E370, T57, F7, F700, F500, E985W, E980W, E980, E880, E780W, E580, E380, T58, L800M, L800, L600, N990W, N890W, N790W, N590, E690, E490, E385, E390, E290, E190, NF720, NF620, EF420, EF220, T79, T39
- Streaming Player/Network Media Player: SMP-N100, SMP-N200, NSZ-GP7
- AV Receiver: STR-DN1020, STR-DN1030, STR-DA1800ES
- BRAVIA: KDL-HX92 series, HX82 series, HX72 series, NX72 series, EX72 series, EX62 series, EX52 series, EX42 series, EX32 series, CX52 series, HX85 series, HX75 series, EX65 series, EX55 series
- Sony Internet TV: NSX-24GT1, 32GT1, 40GT1, 46GT1, NSZ-GT1
- VAIO: VAIO L (SVL241)

wow, awesome!
I'll try immediately when i'm home.

lordmaxey said:
wow, awesome!
I'll try immediately when i'm home.
Click to expand...
Click to collapse
Great! if you can post your TV model it will be greatly apprecciated so we can add it to the "tested list" of models.

etrosce said:
Great! if you can post your TV model it will be greatly apprecciated so we can add it to the "tested list" of models.
Click to expand...
Click to collapse
Hi there,
i've got a Sony Bravia KDL-32HX758
I'll tell you when i've tested it looking forward!
Edit:
one word: awesome!
It works great and i absolutely LOVE it!! Great work!!! Congrats!

lordmaxey said:
Hi there,
i've got a Sony Bravia KDL-32HX758
I'll tell you when i've tested it looking forward!
Edit:
one word: awesome!
It works great and i absolutely LOVE it!! Great work!!! Congrats!
Click to expand...
Click to collapse
Thanks and enjoy :good:. I've just updated the post to list the models we know it works... Hope to see more feedback here

Hi!
I wanted to try your app, but my television (w655) didn't want to agree on that.
Are you maybe willing to share the source code of the app?
Or do you want to check why it's not working?
Thanks!

mendel129 said:
Hi!
I wanted to try your app, but my television (w655) didn't want to agree on that.
Are you maybe willing to share the source code of the app?
Or do you want to check why it's not working?
Thanks!
Click to expand...
Click to collapse
Hey there,
I've been researching a little bit about it before. It looks like Sony changed completely the way to remote control in latest models, specially W series. No documentation about that. So, the only way to try to discover how it works now, is to have a W series to try with (which I do not have)
Sorry about that.
What you can do is try to discover how the new service works by yourself, so we can expand the compatibility of the App. If you are interested, I can guide you with some clues, tools and techinches I used in the past to do so.
I may open the code, I haven't even considered it but I think it's a good idea.

etrosce said:
Hey there,
I've been researching a little bit about it before. It looks like Sony changed completely the way to remote control in latest models, specially W series. No documentation about that. So, the only way to try to discover how it works now, is to have a W series to try with (which I do not have)
Sorry about that.
What you can do is try to discover how the new service works by yourself, so we can expand the compatibility of the App. If you are interested, I can guide you with some clues, tools and techinches I used in the past to do so.
I may open the code, I haven't even considered it but I think it's a good idea.
Click to expand...
Click to collapse
I've been playing with our 2013 model a couple of days now, and it seems the controls still works (compatible with 2012) but the registration process is not necessary anymore...
Anyway, if you put the code somehwere, i'll try if it works somehow
thanks!

mendel129 said:
I've been playing with our 2013 model a couple of days now, and it seems the controls still works (compatible with 2012) but the registration process is not necessary anymore...
Anyway, if you put the code somehwere, i'll try if it works somehow
thanks!
Click to expand...
Click to collapse
Sounds good, give me a couple of days to set it up and will let you know.
In the meantime, does your device description xml look like this one? http://www.upnp-database.info/device.jsp?deviceId=662 (See Description XML tab). If so, you may want to try ScalarWebAPI service on your modes. In that xml you can get some urls that will return some valuable (or not) information that may give you some clues.
Stay tunned,
Esteban

i have Klv 32EX330
how can i to make it working with this app

life25ak said:
i have Klv 32EX330
how can i to make it working with this app
Click to expand...
Click to collapse
I'm not sure you model actually supports to be remote controlled as it isn't event listed by sony as supported (see supported models above).
Does the app find your model? (be sure both are connected to the same lan)

etrosce said:
I'm not sure you model actually supports to be remote controlled as it isn't event listed by sony as supported (see supported models above).
Does the app find your model? (be sure both are connected to the same lan)
Click to expand...
Click to collapse
no doesnt
thank you so much

life25ak said:
no doesnt
thank you so much
Click to expand...
Click to collapse
Well, I'm afraid, as I said before, it does not provides de services required for remote control support. Sorry.

etrosce said:
Sounds good, give me a couple of days to set it up and will let you know.
In the meantime, does your device description xml look like this one? http://www.upnp-database.info/device.jsp?deviceId=662 (See Description XML tab). If so, you may want to try ScalarWebAPI service on your modes. In that xml you can get some urls that will return some valuable (or not) information that may give you some clues.
Stay tunned,
Esteban
Click to expand...
Click to collapse
Hey man,
so, I gathered some information, please check following xml-files
http://mendelonline.be/sony/
Also, almost all commands from vremote (http://falcosoft.hu/softwares.html) are actually working

mendel129 said:
Hey man,
so, I gathered some information, please check following xml-files
http://mendelonline.be/sony/
Also, almost all commands from vremote (http://falcosoft.hu/softwares.html) are actually working
Click to expand...
Click to collapse
Hey, sorry for the delay on sharing the code, I changed laptop and had to re-setup my dev env. Will try to have it done for the weekend.
In the meantime...I wonder what all this urls return:
http://192.168.1.54/sony/guide
http://192.168.1.54/sony/system
....
http://192.168.1.54/sony/irCommandProxy
Basically everything under <av:X_ScalarWebAPI_ServiceList> from dmr.xml. Actually, I would try any url available in that file
We should see where getRemoteCommandList api is located (together with other relevant APIs)
In previous models it was returned as a result from http://192.168.1.54/cers/ActionList.xml. It should be somewhere else now.
Also, did you confirmed that there is no registration required now at all?
Thanks!!!

etrosce said:
Hey, sorry for the delay on sharing the code, I changed laptop and had to re-setup my dev env. Will try to have it done for the weekend.
In the meantime...I wonder what all this urls return:
http://192.168.1.54/sony/guide
http://192.168.1.54/sony/system
....
http://192.168.1.54/sony/irCommandProxy
Basically everything under <av:X_ScalarWebAPI_ServiceList> from dmr.xml. Actually, I would try any url available in that file
--edit--
ok, we've got an entire json conversation going to http://ip:80/sony/system
We should see where getRemoteCommandList api is located (together with other relevant APIs)
In previous models it was returned as a result from http://192.168.1.54/cers/ActionList.xml. It should be somewhere else now.
Also, did you confirmed that there is no registration required now at all?
Thanks!!!
Click to expand...
Click to collapse
No problem, didn't had time myself
Well, there basically 2 webservers/-services running.
One nginx on tcp:80, and something else on tcp:52323 (tcp header contains: Server=Linux/2.6 UPnP/1.0 KDL-42W655A/1.7)
actionlist is "gone", but i'm trying to capture network traffic from the official sony app to figure out the new location
--edit--
ok, so there's an entire "json conversation" going on http://ip:80/sony/system
--edit2--
bingo
--edit--
send this json command:
{"id":20,"method":"getRemoteControllerInfo","version":"1.0","params":[]}
to
http://192.168.1.61/sony/system
and this comes back as return:
{"id":20,"result":[{"bundled":true,"type":"RM-J1100"},[{"name":"PowerOff","value":"AAAAAQAAAAEAAAAvAw=="},{"name":"Input","value":"AAAAAQAAAAEAAAAlAw=="},{"name":"GGuide","value":"AAAAAQAAAAEAAAAOAw=="},{"name":"EPG","value":"AAAAAgAAAKQAAABbAw=="},{"name":"Favorites","value":"AAAAAgAAAHcAAAB2Aw=="},{"name":"Display","value":"AAAAAQAAAAEAAAA6Aw=="},{"name":"Home","value":"AAAAAQAAAAEAAABgAw=="},{"name":"Options","value":"AAAAAgAAAJcAAAA2Aw=="},{"name":"Return","value":"AAAAAgAAAJcAAAAjAw=="},{"name":"Up","value":"AAAAAQAAAAEAAAB0Aw=="},{"name":"Down","value":"AAAAAQAAAAEAAAB1Aw=="},{"name":"Right","value":"AAAAAQAAAAEAAAAzAw=="},{"name":"Left","value":"AAAAAQAAAAEAAAA0Aw=="},{"name":"Confirm","value":"AAAAAQAAAAEAAABlAw=="},{"name":"Red","value":"AAAAAgAAAJcAAAAlAw=="},{"name":"Green","value":"AAAAAgAAAJcAAAAmAw=="},{"name":"Yellow","value":"AAAAAgAAAJcAAAAnAw=="},{"name":"Blue","value":"AAAAAgAAAJcAAAAkAw=="},{"name":"Num1","value":"AAAAAQAAAAEAAAAAAw=="},{"name":"Num2","value":"AAAAAQAAAAEAAAABAw=="},{"name":"Num3","value":"AAAAAQAAAAEAAAACAw=="},{"name":"Num4","value":"AAAAAQAAAAEAAAADAw=="},{"name":"Num5","value":"AAAAAQAAAAEAAAAEAw=="},{"name":"Num6","value":"AAAAAQAAAAEAAAAFAw=="},{"name":"Num7","value":"AAAAAQAAAAEAAAAGAw=="},{"name":"Num8","value":"AAAAAQAAAAEAAAAHAw=="},{"name":"Num9","value":"AAAAAQAAAAEAAAAIAw=="},{"name":"Num0","value":"AAAAAQAAAAEAAAAJAw=="},{"name":"Num11","value":"AAAAAQAAAAEAAAAKAw=="},{"name":"Num12","value":"AAAAAQAAAAEAAAALAw=="},{"name":"VolumeUp","value":"AAAAAQAAAAEAAAASAw=="},{"name":"VolumeDown","value":"AAAAAQAAAAEAAAATAw=="},{"name":"Mute","value":"AAAAAQAAAAEAAAAUAw=="},{"name":"ChannelUp","value":"AAAAAQAAAAEAAAAQAw=="},{"name":"ChannelDown","value":"AAAAAQAAAAEAAAARAw=="},{"name":"SubTitle","value":"AAAAAgAAAJcAAAAoAw=="},{"name":"ClosedCaption","value":"AAAAAgAAAKQAAAAQAw=="},{"name":"Enter","value":"AAAAAQAAAAEAAAALAw=="},{"name":"DOT","value":"AAAAAgAAAJcAAAAdAw=="},{"name":"Analog","value":"AAAAAgAAAHcAAAANAw=="},{"name":"Teletext","value":"AAAAAQAAAAEAAAA/Aw=="},{"name":"Exit","value":"AAAAAQAAAAEAAABjAw=="},{"name":"Analog2","value":"AAAAAQAAAAEAAAA4Aw=="},{"name":"*AD","value":"AAAAAgAAABoAAAA7Aw=="},{"name":"Digital","value":"AAAAAgAAAJcAAAAyAw=="},{"name":"Analog?","value":"AAAAAgAAAJcAAAAuAw=="},{"name":"BS","value":"AAAAAgAAAJcAAAAsAw=="},{"name":"CS","value":"AAAAAgAAAJcAAAArAw=="},{"name":"BSCS","value":"AAAAAgAAAJcAAAAQAw=="},{"name":"Ddata","value":"AAAAAgAAAJcAAAAVAw=="},{"name":"PicOff","value":"AAAAAQAAAAEAAAA+Aw=="},{"name":"Tv_Radio","value":"AAAAAgAAABoAAABXAw=="},{"name":"Theater","value":"AAAAAgAAAHcAAABgAw=="},{"name":"SEN","value":"AAAAAgAAABoAAAB9Aw=="},{"name":"InternetWidgets","value":"AAAAAgAAABoAAAB6Aw=="},{"name":"InternetVideo","value":"AAAAAgAAABoAAAB5Aw=="},{"name":"Netflix","value":"AAAAAgAAABoAAAB8Aw=="},{"name":"SceneSelect","value":"AAAAAgAAABoAAAB4Aw=="},{"name":"Mode3D","value":"AAAAAgAAAHcAAABNAw=="},{"name":"iManual","value":"AAAAAgAAABoAAAB7Aw=="},{"name":"Audio","value":"AAAAAQAAAAEAAAAXAw=="},{"name":"Wide","value":"AAAAAgAAAKQAAAA9Aw=="},{"name":"Jump","value":"AAAAAQAAAAEAAAA7Aw=="},{"name":"PAP","value":"AAAAAgAAAKQAAAB3Aw=="},{"name":"MyEPG","value":"AAAAAgAAAHcAAABrAw=="},{"name":"ProgramDescription","value":"AAAAAgAAAJcAAAAWAw=="},{"name":"WriteChapter","value":"AAAAAgAAAHcAAABsAw=="},{"name":"TrackID","value":"AAAAAgAAABoAAAB+Aw=="},{"name":"TenKey","value":"AAAAAgAAAJcAAAAMAw=="},{"name":"AppliCast","value":"AAAAAgAAABoAAABvAw=="},{"name":"acTVila","value":"AAAAAgAAABoAAAByAw=="},{"name":"DeleteVideo","value":"AAAAAgAAAHcAAAAfAw=="},{"name":"PhotoFrame","value":"AAAAAgAAABoAAABVAw=="},{"name":"TvPause","value":"AAAAAgAAABoAAABnAw=="},{"name":"KeyPad","value":"AAAAAgAAABoAAAB1Aw=="},{"name":"Media","value":"AAAAAgAAAJcAAAA4Aw=="},{"name":"SyncMenu","value":"AAAAAgAAABoAAABYAw=="},{"name":"Forward","value":"AAAAAgAAAJcAAAAcAw=="},{"name":"Play","value":"AAAAAgAAAJcAAAAaAw=="},{"name":"Rewind","value":"AAAAAgAAAJcAAAAbAw=="},{"name":"Prev","value":"AAAAAgAAAJcAAAA8Aw=="},{"name":"Stop","value":"AAAAAgAAAJcAAAAYAw=="},{"name":"Next","value":"AAAAAgAAAJcAAAA9Aw=="},{"name":"Rec","value":"AAAAAgAAAJcAAAAgAw=="},{"name":"Pause","value":"AAAAAgAAAJcAAAAZAw=="},{"name":"Eject","value":"AAAAAgAAAJcAAABIAw=="},{"name":"FlashPlus","value":"AAAAAgAAAJcAAAB4Aw=="},{"name":"FlashMinus","value":"AAAAAgAAAJcAAAB5Aw=="},{"name":"TopMenu","value":"AAAAAgAAABoAAABgAw=="},{"name":"PopUpMenu","value":"AAAAAgAAABoAAABhAw=="},{"name":"RakurakuStart","value":"AAAAAgAAAHcAAABqAw=="},{"name":"OneTouchTimeRec","value":"AAAAAgAAABoAAABkAw=="},{"name":"OneTouchView","value":"AAAAAgAAABoAAABlAw=="},{"name":"OneTouchRec","value":"AAAAAgAAABoAAABiAw=="},{"name":"OneTouchStop","value":"AAAAAgAAABoAAABjAw=="}]]}

mendel129 said:
No problem, didn't had time myself
Well, there basically 2 webservers/-services running.
One nginx on tcp:80, and something else on tcp:52323 (tcp header contains: Server=Linux/2.6 UPnP/1.0 KDL-42W655A/1.7)
actionlist is "gone", but i'm trying to capture network traffic from the official sony app to figure out the new location
--edit--
ok, so there's an entire "json conversation" going on http://ip:80/sony/system
--edit2--
bingo
....
Click to expand...
Click to collapse
This is all good. It would be great if we find the url that actually returns the list of APIs. Have you tried http://ip:80/sony/system to see what it returns in the browser?

etrosce said:
This is all good. It would be great if we find the url that actually returns the list of APIs. Have you tried http://ip:80/sony/system to see what it returns in the browser?
Click to expand...
Click to collapse
just browsing to the "site" just gives an empty page...
it only reply's on json requests
all commands i've found so far are from capturing traffic from my android tablet
check here: http://mendelonline.be/sony/sony.txt
further, the "register" function exists, but it not really necesarry...
i noticed the sony tablet app registering, but i can just send commands from upnpspy directly from my pc without registering...
another thingy: wol is just basic wake on lan

I received an email from the creator of the windows app that works for our 2013 model bravia. (http://falcosoft.hu/softwares.html#sony_virtual_remote)
Hi,
I would like to share my experiences with you, maybe it can help in the
investigation of the new API structure.
1. The registered status is not required in 2011/12 Sony TV models either to
send pure IRCC SOAP messages (or use the X_SendIRCC UPnP service) .
2. The registered status is required to get meaningful response from url
based API functions (e.g sendText, getText, getRemoteCommandList etc..)
So just an idea: You should try to test these new URL based commands with a
registered status. To achieve this:
1. You should make a new registration and send these data with your browser
2. Use an existing registration e.g. Falcosoft's Sony Virtual Remote and
send the program's data with your browser.
I suggest to use Firefox with Modify Headers plugin. For option 2 here are
the required header fields:
'X-CERS-DEVICE-ID' -> 'vaio:11111111-D7A0-11DD-119C-6D990C3C4529' ;
'X-CERS-DEVICE-INFO' -> 'falco_virtual_remote' ;
Best Regards:
Zoltán Bacskó
Falcosoft
Ps: If you can ask the topic owner to authorize my xda-developers account to
send posts to this topic I would be grateful. My new xda-developers account
is 'Falcosoft'

mendel129 said:
I received an email from the creator of the windows app that works for our 2013 model bravia. (http://falcosoft.hu/softwares.html#sony_virtual_remote)
Hi,
I would like to share my experiences with you, maybe it can help in the
investigation of the new API structure.
1. The registered status is not required in 2011/12 Sony TV models either to
send pure IRCC SOAP messages (or use the X_SendIRCC UPnP service) .
2. The registered status is required to get meaningful response from url
based API functions (e.g sendText, getText, getRemoteCommandList etc..)
So just an idea: You should try to test these new URL based commands with a
registered status. To achieve this:
1. You should make a new registration and send these data with your browser
2. Use an existing registration e.g. Falcosoft's Sony Virtual Remote and
send the program's data with your browser.
I suggest to use Firefox with Modify Headers plugin. For option 2 here are
the required header fields:
'X-CERS-DEVICE-ID' -> 'vaio:11111111-D7A0-11DD-119C-6D990C3C4529' ;
'X-CERS-DEVICE-INFO' -> 'falco_virtual_remote' ;
Best Regards:
Zoltán Bacskó
Falcosoft
Ps: If you can ask the topic owner to authorize my xda-developers account to
send posts to this topic I would be grateful. My new xda-developers account
is 'Falcosoft'
Click to expand...
Click to collapse
Interesting fact that that app works for you. I think this is because that app uses some hardcoded data by default while BraviaControl completely relies on the APIs exposed by the services. It looks like some APIs where left there "hidden" for backward compatibility purposes. I think we should try something like: Cannot find the APIs?, try to force the use. In your case, it may partially (or completely, why not?) work.
Anyway, all that json conversation looks like to be the new way to comunicate with the TV, so, it will be nice to implement that sometime too.
Thanks! I have already set up the code in the cloud. Will be sending the details on how to access it soon (Sorry, I don't currently have very much time free for this project, so bear with me )

Related

[APP] Subnet Calculator -[R]- 2011-01-24 -[V]- 1.0.0 -[U]- 2011-02-12

Name: Subnet Calculator
Hi Everyone,
Inspired by a request from Omega Ra, I decided to get my feet wet with WP7 development and build a Subnet Calculator application.
The app itself is pretty simple. You enter an ip address, and it will calculate the Network Id, Broadcast Address, and Min/Max host addresses for the configured subnet. Changing any of the settings will update the values. Here's a bullet point list of features:
Two Modes - switch between a classful and classless calculator by swiping left/right. The application implements Microsoft's Pivot control.
Flexibility - provides a selection of configuration options using the subnet mask, mask bits, subnet bits, hosts available per subnet, maximum available subnets, and the ip address.
Email - send your configuration to yourself quickly and easily.
List all subnets - for the classful calculator, you can view the list of all possible subnets.
ToDo:
Make the IP Address easier to edit/manipulate. I'm thinking of enlarging the TextBox once you click on it, that way you'll be able to select parts of the address easier.
Sexify the overall appearance
I'm open to any feedback/suggestions you all may have.
Credits/Thanks
I borrowed heavily from this online tool
Thanks to Omega Ra for the idea
!!!UPDATE!!!
Application is now available in the marketplace, please get it through there and comment if you want to show some support, but the xap will always remain available and updated on this thread
To install on your phone just rename the file from SubnetCalculator.zip to SubnetCalculator.xap
Please see the WP7 Hacking for Beginners thread for further information on how to sideload an xap.
this is the one im looking for a very long time.. i hope you make one for android
nice, it has it's own thread and thanks for the props Looking great so far!
The only other thing I can think of that might be useful would be a button that will show you the subnet address ranges (in the advanced ip calculator I linked to once you put in the address and click the magnifying glass you will see what I mean.) Other than that this is awesome!
randolph2000 said:
this is the one im looking for a very long time.. i hope you make one for android
Click to expand...
Click to collapse
Thanks. I'm glad you like it. I'll see what I can do about an android port, though it'll probably function a little differently (i.e. no pivot).
Omega Ra said:
nice, it has it's own thread and thanks for the props Looking great so far!
The only other thing I can think of that might be useful would be a button that will show you the subnet address ranges (in the advanced ip calculator I linked to once you put in the address and click the magnifying glass you will see what I mean.) Other than that this is awesome!
Click to expand...
Click to collapse
Interesting. I'll see what I can do.
abledanger said:
Thanks. I'm glad you like it. I'll see what I can do about an android port, though it'll probably function a little differently (i.e. no pivot).
Interesting. I'll see what I can do.
Click to expand...
Click to collapse
cool. I hate to be a pest lol, but this will be an awesome app for sys admins and I think a lot of people will get it.
edit:did a really crappy and fast paint of a screen shot to show you what I mean. I put it in the wrong thread lol
http://forum.xda-developers.com/attachment.php?attachmentid=415735&d=1286569553
just out of curiosity, how is this coming along? is it going to hit the marketplace soon? So far there are no IP calculators on there, though there is one hexidecimal one.
Any progress??? there is now a subnet calc up on the marketplace...though yours looks better, it looks fairly functional...
I guess development on this has stopped?
IT'S ALIVE!!!! lol glad to see this is still going.
Looks good
Omega Ra said:
IT'S ALIVE!!!! lol glad to see this is still going.
Click to expand...
Click to collapse
Yeah sorry for the delay. I just got married last month so free time has been pretty difficult to come by! I'm still thinking on how to implement the changes you mentioned above though, so hopefully I'll have an update soon.
JoelyMole said:
Looks good
Click to expand...
Click to collapse
Thanks!
Though i lost this app, but re-gooled it again and found it again (didn't have the phone yet, but now that i have it i thought I MUST FIND THAT APP AGAIN), thanks for sharing, really appreciate this.
it the zip file the actual app, and if it is how do you put it on my phone?
BotMan37 said:
it the zip file the actual app, and if it is how do you put it on my phone?
Click to expand...
Click to collapse
just rename it from .zip to .xap
Great app! Thanks!
Thanks everyone! My app was rejected from the marketplace for failing to display the app version and technical contact information :'( So I should have an update pretty soon that amends this. I also took the chance to add a couple features and clean things up. The app now recovers state properly and you can send out an email with the configuration settings. I added an app bar that you can use to navigate between the prev/next subnets, so you no longer click on min/max host ips.
I'm working on getting a view of all available subnets in the mix as well, just have to figure out how best to display it
Any chance you can upload the new version as a XAP too to let us play with it while you wait for market approval?
New version is up
awesome. so yours is the one in the market from bitconsortium? As soon as I get the Trophy (once it hits Verizon) I will get it and give it 5 stars
Omega Ra said:
awesome. so yours is the one in the market from bitconsortium? As soon as I get the Trophy (once it hits Verizon) I will get it and give it 5 stars
Click to expand...
Click to collapse
Nice! And yes it is the one from bitconsortium.

[DEV] Intercept chromecast whitelist with MITM (and update)

Hi All,
I've just managed to successfully intercept and change the whitelist for a flashed chromecast.
Steps:
Load custom cert onto device (replace nssdb with custom one) - nssdb I used and certs available here https://mega.co.nz/#!05wmDR4T!OMkBXwfO9D1wktt2bQpSwjNZ_Y9PB8q_Ryk3zSx4k1c
Load MITM on a linux host, route default gateway at linux host.
Route just google range towards MITM (so nothing else gets caught and just gets redirected)
iptables -t nat -A PREROUTING -p tcp -s 192.168.178.146 -m iprange --dst-range 74.125.237.0-74.125.237.255 -j REDIRECT --to-port 8080
load mitmproxy with
"mitmproxy -T --host -s chromefree.py"
chromefree.py is available https://mega.co.nz/#!doJX1YDS!TT3lolbgXta24QOpbj40PBAYRetZkH1s9cIvQBslBN8
note that chromefree.py refrences json.dat (which requires a gzip'd json file)
example json files are available here https://mega.co.nz/#!ghwAEI7D!a-HwECm4w_8XKfdaaZOLgFrVTx9B8xLMOYJchi1PAUY
(with this I redirected youtube to a local news site, so attempting to cast to youtube pulls up stuff.co.nz)
Appears to work well, here's a picture of my TV running the revision 3 app
http://i.imgur.com/nhLI0oC.jpg
While I applaud this news, this could likely be the reason why Google has been slow to throw the doors open. The big name media providers are probably really leaning on Google to make sure these kinds of hacks can't possibly take place.
While everyone knows that no system is infallible, I'm sure that Google is under pressure to make sure that the device is as airtight as it can possibly be, and then some, before permitting the SDK to be formally released to the public.
mkhopper said:
While I applaud this news, this could likely be the reason why Google has been slow to throw the doors open. The big name media providers are probably really leaning on Google to make sure these kinds of hacks can't possibly take place.
While everyone knows that no system is infallible, I'm sure that Google is under pressure to make sure that the device is as airtight as it can possibly be, and then some, before permitting the SDK to be formally released to the public.
Click to expand...
Click to collapse
Do you really think that people would be spending so much time trying to circumvent the whitelisting if the content was available from the get go. I was very optimistic at the start but losing patience now. I bought three and was ready to buy more, but will wait and see what happens. Don't want to invest more money and time into something that might not have a future. It is sad because it has the unprecedented potential for so many different uses.
Can this be dumbed down for the newbs
ramirez3805 said:
Can this be dumbed down for the newbs
Click to expand...
Click to collapse
I plan to have a service available for rooted chromecast in the next few days that allows access to non-google approved applications.
Kyonz said:
I plan to have a service available for rooted chromecast in the next few days that allows access to non-google approved applications.
Click to expand...
Click to collapse
Cant wait!!!:good:
networx2002 said:
Cant wait!!!:good:
Click to expand...
Click to collapse
You don't have to! I just released last night http://forum.xda-developers.com/showthread.php?t=2516164
Kyonz said:
Appears to work well, here's a picture of my TV running the revision 3 app
http://i.imgur.com/nhLI0oC.jpg
Click to expand...
Click to collapse
What did you use as the sender app?
so i have a question how do you load up an app for use in chromecast now that i have done this ? sorry for sounding so noobish but just wondering.
ahecht said:
What did you use as the sender app?
Click to expand...
Click to collapse
I used the demo html app sender to launch it (sorry not entirely sure on the name as I haven't started developing for chromecast yet). I'd really like to see someone try to reverse engineer the data that the receivers require and build apps out for these though.
BurnOmatic said:
so i have a question how do you load up an app for use in chromecast now that i have done this ? sorry for sounding so noobish but just wondering.
Click to expand...
Click to collapse
This really is a DEV thread in that it provided the exploit for chromecast, app launching would be through the demo dev apps - please check out Kyocast (http://forum.xda-developers.com/showthread.php?t=2516164) if you haven't and note that there are better things coming
Kyonz said:
I used the demo html app sender to launch it (sorry not entirely sure on the name as I haven't started developing for chromecast yet). I'd really like to see someone try to reverse engineer the data that the receivers require and build apps out for these though.
Click to expand...
Click to collapse
I must be dense, as I can't make heads or tails of the Chromecast API (I usually can't understand Google's documentation for the Android API either, but there are plenty of third-party resources for that). What do you use for Launch Parameters in the demo app?
Which boot loader number is vulnerable ? I can#t find the infos :/
12alex21 said:
Which boot loader number is vulnerable ? I can#t find the infos :/
Click to expand...
Click to collapse
Only build 12072 has a vulnerable bootloader. You have to boot into the stock OS and set the Chromecast up (on a Wi-Fi network which doesn't connect to the internet or else it will update automatically) to check the build number.

How to start custom app via http

Dear All,
I am a bit stuck. How can I start a custom receiver via http? I tried sending a GET to /apps/1234ABCD (with the code I get on the developer console) but I constantly get 404.
The same code works via ios/android/chrome sdk, but unfortunately I have to use this outside of the ios/android/chrome world...
I did not have success with Wiresharking the network traffic using the chrome sdk, the app id seems to be not trivially stored in the requests.
Any ideas?
Thank You!
The old V1 app ids like youtube, netflix, etc can be launched with a POST but that doesn't work for the new V2 app ids.
I would like to know how to launch the V2 apps as well (as I have my own). From Wireshark, it looks like it might be related to SSL traffic on port 8009 to the Chromecast, but I have not been able to figure out what to send it.
knoxbrder said:
The old V1 app ids like youtube, netflix, etc can be launched with a POST but that doesn't work for the new V2 app ids.
I would like to know how to launch the V2 apps as well (as I have my own). From Wireshark, it looks like it might be related to SSL traffic on port 8009 to the Chromecast, but I have not been able to figure out what to send it.
Click to expand...
Click to collapse
Thank You. At least I know that I am not alone with my problem!
If you find out anything, or have an idea, please don't hesitate to tell me.
It's sad that this is closed this way, can't figure out why.
The 'nodecastor' project on github (_not_ nodecast) seems interesting!
zsoltt said:
The 'nodecastor' project on github (_not_ nodecast) seems interesting!
Click to expand...
Click to collapse
Wow, that was a pain to get installed. But it was worth it. Now I can launch my app from the command line or my webserver without have to start it from an android app or a special chrome plugin. Thanks!
When I have a few hours I need to trace through it and see what it does that required so many other npm installs.

[Q] Rooted chromecast and beta tester program

I have an issue accessing to a beta tester program with a rooted Chromecast. I'm not sure if this is the expected behavior, for this reason I'm asking here.
First I want to expose the current escenario.
A few days ago a spanish web aplication es.wuaki.tv started a promotion with a Chromecast involved. The objective was to participate like a beta tester in the service. It's possible to acces to the service via browser (chrome extension) or with a native android aplication. The right app version is only accesible after registering like a beta tester. For no compatible devices there is a link to the apk file (no external link allowed).
They (the technical support from wuaki.tv) say that the chromecast that they shipped with the promotion is registered for accessing to service.
There's a option to register a chromecast that was no shipped by they. In this case you have to send the chromecast's serial number and activate the "send serial number for updates" checkbox in chromecast configuration.
And now, the problem.
I have an Chromecast imported from USA. It's rooted and I have installed the last Eureka room.
I have made all the steps. I have verified with the technical support that my serial number was registered and correct.
But I can't make it works. Neither with the android app or the chrome extension. The cast button it's not showed.
I have changed the settings for rooted chromecast to 'defaults'. That is:
* Google Whitelist
* Google DNS
I have played other configs (I believe that ALL the possible configs) without success.
My thoughts.
I expected to find some reference to the service in the google whitelist, but I didn't see anything in the next files
From Google:
http://click.xda-developers.com/api...clients3.google.com/cast/chr...ice/baseconfig
http://click.xda-developers.com/api...clients3.google.com/cast/chr.../device/config
From Eureka:
http://click.xda-developers.com/api...rs&txt=http://pwl.team-eureka.com/applist.php
In the source code from webpage, pe:
Code:
view-source:https://es.wuaki.tv/movies/la-vida-secreta-de-walter-mitty
you can find:
Code:
<script src='https://www.gstatic.com/cv/js/sender/v1/cast_sender.js' type='text/javascript'></script>
<script>
//<![CDATA[
window.LaunchCastData = {
appid: "D383FA1E",
hasSelectedStream: false,
listStreamsUrl: "https://api.wuaki.tv/movies/4607",
reqParams: {
auth_token: "WM6qW3y1hM5xnRvyWDAq",
device: 'cast'
},
selectedStream: {}
}
//]]>
</script>
I think that, in my case, the whitelisting proccess works for individual chromecast (with the S/N) and maybe this is the reason that I can't find references to aplication in the whitelist files. I don't know.
But, finally, the question that I want to make is:
it's possible to access to that kind of 'beta tester' program with a rooted Chromecast?
Thanks in advance.
PD: sorry, I can't post external links (new user limitation)
The reason your device is unable to pull the configuration is because when using Eureka-ROM, your serial # is not sent to our server, or googles, when set as the whitelist as we use a backend application to do the calls. If you need to use your device to testing applications, I recommend flashing our rooted stock ROM we offer at: http://forum.xda-developers.com/showthread.php?t=2638103 as it does not modify the way whitelists are pushed to the device.
I will look into supporting this though in Eureka-ROM when the Whitelist provider is set to google, and hopefully I can get it ready for the next ROM release.
ddggttff3 said:
The reason your device is unable to pull the configuration is because when using Eureka-ROM, your serial # is not sent to our server, or googles, when set as the whitelist as we use a backend application to do the calls. If you need to use your device to testing applications, I recommend flashing our rooted stock ROM we offer at: http://forum.xda-developers.com/showthread.php?t=2638103 as it does not modify the way whitelists are pushed to the device.
Click to expand...
Click to collapse
Thank you very much for your answer. I had thought a lot of possibilities, but I had not considered the most obvious one: a rooted chromecast will not send his S/N.
I'll take a look at that rooted ROM, but since I do not have the right wires, I think for now keep the current ROM.
ddggttff3 said:
I will look into supporting this though in Eureka-ROM when the Whitelist provider is set to google, and hopefully I can get it ready for the next ROM release.
Click to expand...
Click to collapse
Thank you very much for taking into consideration my case. It would be nice to have the option.
And, now that you mention, do you have planned out a new version? Or are you referring to the next official version?
Thanks for solving my doubt.
javicalle said:
Thank you very much for taking into consideration my case. It would be nice to have the option.
And, now that you mention, do you have planned out a new version? Or are you referring to the next official version?
Thanks for solving my doubt.
Click to expand...
Click to collapse
I am referring to the next official update to Eureka-ROM, which I do not have an ETA for. We normally only rollout updates when things break, or theres a new feature that's worth an update. There may be a minor update in the near future though, so I will see if I can get this added.
tl;dr it all varies, and depends on what else is getting updated.
Thanks to @Kyonz, the next OTA will allow for you to use your device as a development device!
ddggttff3 said:
Thanks to @Kyonz, the next OTA will allow for you to use your device as a development device!
Click to expand...
Click to collapse
GREAT NEWS!!!
Thanks to both of you for taking care of 'suggestions'.
javicalle said:
GREAT NEWS!!!
Thanks to both of you for taking care of 'suggestions'.
Click to expand...
Click to collapse
No problem, this is something we overlooked when creating the whitelist generation and it's important to us that we support features existing and that you benefit from having a rooted device!

[NST/G] R.I.P. WeatherACE for the Nook Simple Touch

Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
scotte9999 said:
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
Click to expand...
Click to collapse
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
So we move on.
Click to expand...
Click to collapse
Indeed. I spent some time yesterday exploring web-based widgets, thinking we could just point the browser at a URL, but most widgets use HTTPS and Javascript, neither of which are the strong suit of the NST, even with Opera Classic instead of the native browser.
Did this work?
disTrck33 said:
Did this work?
Click to expand...
Click to collapse
Depends on what "this" is.
I eventually wrote my own weather widget app for the NST/G: https://forum.xda-developers.com/nook-touch/themes-apps/app-nst-weather-widget-t3946270
This works.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
Click to expand...
Click to collapse
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
SJT75 said:
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
Click to expand...
Click to collapse
Didn't remember the US restriction, but all of the potential apps I looked at back then looked terrible on the NST or required network location. That is why (shameless promotion...) I eventually worked up my own Weather widget/app just for the NST. It lacks many bells and whistles but will work for any locale that OWM has stations. And, if I say so myself, looks pretty good on the NST.
nmyshkin said:
Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Click to expand...
Click to collapse
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
mycodefab said:
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
Click to expand...
Click to collapse
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
nmyshkin said:
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
Click to expand...
Click to collapse
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
mycodefab said:
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
Click to expand...
Click to collapse
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
nmyshkin said:
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
Click to expand...
Click to collapse
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
mycodefab said:
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
Click to expand...
Click to collapse
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
nmyshkin said:
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
Click to expand...
Click to collapse
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
mycodefab said:
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
Click to expand...
Click to collapse
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
nmyshkin said:
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, thanks. In case you have DarkSky API key (the app know it as Forecase.IO, it was an old name of the DarkSky API) please use it with the version 1.7.4, the app version support the weather source. Once purchased by Apple, DarkSky (Forecast.IO) no longer give out free keys. But any old keys continue to work atm, as far as I know.
Building a new version with updated support for weather sources will take some time. As usual, most problems in the case are not related with app itself, but with other libraries. For example, a library that provided map does not support Android 2.1 anymore, so probably I will need to completely remove map from the app. Google libraries related with analytics and ads - also does not support old android versions anymore. I will work on it this weekend.
nmyshkin said:
Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
Click to expand...
Click to collapse
You need GPS.
nmyshkin said:
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
The version support 2 weather sources - OWM (open weather map) and Norwegian MET.NO.
Limitations:
1. Removed weather map and adding locations via map. I cant find any android weather libraries that support Android 2.1 devices.
2. Removed ads for same reason.
3. Weather icons limited to the small set of icons inside the app + 1 custom icon set.
As for custom icon set, its mostly same as for latest versions of WeatherACE, just a bit different directory for images. Directory is "Android/data/mycodefab.aleph.weather/files/custom/icons/". It use same format as for the latest versions. So, for example, for "clear sky in day" condition it will use "d_100.png" file, "clear sky in night" will look for "n_100.png" file, "overcast" will use "d_104.png", etc.
In case the version of the appt will start, but not show the weather after weather info update, please get to Menu->Settings->Advanced->Weather Sources. Here you could see Active weather sources on the top. Tap on it. Uncheck OpenWeatherMap and Norwegian MET, tap OK. Enter Active weather sources again. Set check OpenWeatherMap and Norwegian MET, tap OK. It will recheck availability of sources for existing locations and will update the weather info.
mycodefab said:
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
Click to expand...
Click to collapse
I tried the app on both devices (with and without Network Location). Unfortunately it does not want to run
There is immediate funny business as the package shows in the file manager as a generic "package" icon rather than the app icon. Also, the package name (and generic package icon) are displayed in the launcher rather than the app icon and name.
I've attached a section of a logcat for trying to open the app. I don't know whether it has information that is helpful.
It may or may not have any bearing on what you have done, but as you're already going way beyond any expectations, I would suggest that leaving the app alone except for fixing the weather sources would be more than enough. I can understand your desire to have things "right". I have that same problem , and I do appreciate it, but maybe without so many changes there would be a better chance of the app still working, which is what it did even now, except for the access to weather sources. Of course, it's probably not that simple.
Thanks for your efforts.

Categories

Resources