So, I have the feeling this isn't the place to post this, but seeing as how I was unable to find a section for the Focus S (yet there is one for the HTC Titan, which isn't even out yet) I figured I might as well post somewhere.
I've interlop unlocked and loaded a few different .xap's onto my device and have found that most either will not work (they close shortly after loading up) or they allow you to navigate around, but not edit anything. Advanced Config, Registry Editor, Samsung Tools, etc. will not allow for any kind of registry changes. Is there anyone who can point me to the right place for solving this issue?
Give me, oh, another hour. Reverse engineering the Focus S DLLs now. Already have registry, provxml, quite possibly filesystem, and a few other things (including the interface for call blocking, which doens't seem to exist in the older phones - sorry people with first-gen phones).
The new SecProxyClient.dll is super-useful. The new FCRouterProxy.dll looks to be amazing too, with lots of new APIs, but they obfuscated the function signatures, so it's going to take me a while to figure them out.
Of course, I don't have Focus S or Focus Flash, so I'm going to need some testers to make sure I've reassembled these APIs correctly. Any takers? I make no guarantee that these functions will work correctly, and if they don't it could mess up something, but I'll try hard to avoid that.
EDIT: Of course, the apps will need to be modified to use the new APIs and DLLs. It's not like I can publish my results and eisting apps will magically just work. I'll include the source of course, though, so it should be easy to build on my work. If schaps were willing to distribute the source for his own apps, I could fix them myself, but no such luck. That's what you get for closed-source, I guess.
I'm right here to test what you need.
I am more than willing to test. Just post it here or shoot me an email: [email protected]
I'm western time, so ill be up for a while
Yeah, I'm not.
Ill leave the testing for you, hope you guys have **** worked out by the morning.
i'm also willing to test as well, but please don't break my phone
All right folks, have at it. I'd like a few testers from each device, if possible, but mostly I just want good reports. PLEASE read the first post carefully - yes, I know it's long, but it will save both of us time.
http://forum.xda-developers.com/showthread.php?t=1348914
Moved to WP7 Q&A
You are correct there is no focus s forum. There are some posts relating to that phone there, but they are different so i will not move it there. As it is a question it has been moved to WP7 Q&A. Hopefully if and when a focus s forum is created you can request the thread is moved again.
Take it easy
O_G
You know, I'm beginning to wonder of the reason that the call blocking app is struggling so much is just because there's a problem with this DLL that it is (and I am) trying to use. Sigh...
Speaking of which, if anybody can get me the XAP for the Call Blocking app, or for any other Samsung Gen2 app, that could be very helpful.
Here you go
Related
Hi all,
I have a concept for a single update application that would be driven from the AndroidSPIN release database so all developers could use it for ROM, Themes, Applications and anything releases to devices.
If you wouldn't mind taking a couple of minutes to read this post, I would greatly appreciate it.
http://www.androidspin.com/forum/viewtopic.php?f=260&t=226
I'd really love to get a group together to collaborate and either help design this and/or write an application and back end to do it.
Let me know what you think.
Thanks
Simon
Sounds like an awesome idea, I'd love to help any way I can, but I dont fit in any of the needed positions for the post. Looking forward to see what develops though
Fantastic idea!
I only ever use XDA so god knows what I'm missing out on elsewhere and to be honest after searching the word android on google and trawling through one crap site after another becomes tiresome so hence the 'XDA only' policy.
Sorry I can't offer any programming skills but you have my support on this project whole heartedly, not that it counts for much I know buh MeH!
Hope you can get this off the ground.
As I mentioned to Simon already, I was thinking about building an update application for my ROM. I love the idea of having an on-phone ROM database, update capability, something that can easily be used by any developer in the community.
Some initial thoughts on functionality:
- Browse ROMs
- Download ROMs to SD Card
- Monitor specific ROMs for updates
- Monitor currently running ROM for updates
I'm willing to lend a hand on the Android side of things, but this will be a large undertaking and we will also need some people to contribute to the UI, server side of things, etc.
I do iPhone UI design for applications now (I don't have an iPhone, but most of my contracts and clients are iPhone based), but let me know and I can whip up anything you guys need UI related.
Send me a PM and I can get the ball rolling on how the functionality can be laid out as well.
Even tho I know I wouldnt be able to help out with this. I know I would love to test this out if you needed it.
Its a great idea!!!
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
michinohatoresu said:
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
Click to expand...
Click to collapse
Well, we can reuse a lot of code from Cyanogen updater.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Well, of course.
If anything else needs doing, however, I volunteer what spare time I have.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Could be easily done, would require quite a lot of laborious work ripping out all the stuff you wouldn't need though.
I would take a look at this but unfortunately I have another Android project on at the moment which is taking all my development spare time.
@SimonNWalker What sort of backend having you got going? REST? SOAP?
Ups wrong theread
not that it matters (since i kept the source 100% open)....
you have my blessing to tear the cmupdater to shreds if it will give us a unified solution to all our ROM cravings
firefart has done a good job of keeping the code pretty clean so there shouldnt be too many issues with grabbing it
and the new code for the screenshots for themes could probably be used to the advantage of this project with ease
I'm not really interested in a rom updater, but a market replacement with an "upgrade all" feature (à la apt-get / yum) drawing from multiple repositories would be most exciting.
The Cyanogen updater could be used, it just needs some modifications. Stuff like sub-sections and update all
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
The only other method I would consider, besides JSON, is an advanced and well thought out web-based form that the developer is forced to complete upon uploading a ROM. This would place more burden on the server, but should be relatively easy to attach the provided ROM information to the rom database.
Think: Check boxes for firmware compatibilities, check boxes for device compatibilities, version number, change log, etc.
Maybe something a little like this?
Wow this would be/ is gonna be awsome!
I would suggest also that you can backup your sd card settings (and maybe also sms...) to an ftp server (or some other server you can install on your pc) from this app...
like (incremential) backup>partition>wipe>install update>boot>getbackupback
problem is to get the server adress back after wipe. maybe stored in web database and encrypted with phone imei number? or uploaded as google
whatever...
or just not wiping that single adress
just saying ^^
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
JSON is just a file format. The CM Updater works via a static JSON file that gets updated manually. The way I'd design this (which is what I asked a couple of posts back) is a dynamic web service (probably REST based) which delivered JSON dynamically. Wouldn't be too difficult at all.
As SimonWalker said he's using PHP + MySQL I'm guessing that's already being done.
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
senab said:
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
Click to expand...
Click to collapse
I know it is open and I don't need to give my blessing for people to use the source. I did so because a lot of people don't feel comfortable using other peoples code without permission, regardless of whether or not its 100% open source.
And as for the 'credit crap'... I don't see you asking for your name to be removed from the 'about' section of the app
I am not asking for any credit
Anyway, lets not get off topic...
Guys, before this becomes Android Open Alliance, the sequel (you all remember how that went), I think we better set up a way to work together first and then toss in the speculative stuff later.
How about starting simple; set up a wave?
Looking for possible ROM testers.
I'm currently learning about the all of the potential that the android operating system has and would like to get feedback and reports from other users. I'm looking for one or two testers (if i get quite a few PM's, i will definitely consider changing this, but I want to stick with a captive audience at least in the beginng). The knowledge level can vary, as I'm looking for feedback and checking to see what works/doesn't work. I only have a few specific criteria that I'm looking for in testers which I will note at the bottom.
A little something about my expectations...
I will in no way ever refer to myself as a developer. I'm merely a person that can follow directions, ask the right questions to the right person, and learn along the way. I'm not starting this to make money, to show off any sort of skills that i may posess. I would just like to make this a hobby as other "developers" and users like myself have done. I cannot promise a fast ROM. I cannot promise that it will look the best (at least in the beginning). I can promise I will take in all feedback and suggestions and have some consideration towards them. My biggest reason for testing is to find all the nooks and crannies and make sure they're clean. I do not have 4G here in arizona, so i have no clue if it works or not (It's based off stock so I don't see any reason it shouldn't). Etc etc..
Tester Criteria
I would like at least one user that has not formatted their SD card with ext2/ext3 file system for apps2sd. I will provide help with this if/when needed and I would like to give instructions to verify that it is working.
Someone who has 4G in there area, that also uses social networking.
Some sort of Instant Messanging application, you name it and I'll download it and make a username. It makes it so much easier to talk and get feedback when a conversation can be held. A definite plus is someone that has a headset and knows how to use programs such as Ventrilo or Teamspeak (think xbox live for Windows).
Patience with myself.
PM me and I will get back with you as soon as i can.
I'll help no apps2sd and I have 4g I'm not a dev dev but know a lot of android stuff b
Hi, I was wondering if there was a list of HTC One S (Ville) Build.Prop tweaks. I did some searching and saw some lists in other forums, but I wasn't sure if the build.prop was the same for all devices, I guess I'm assuming not as some organizations are totalitarian and such.
In any case, I think we should create a list of build.prop tweaks specifically for the One S that are very effective, saying what the tweak changes and how it effects the device, also what other settings you can give it and what those effects do. Maybe I'm thinking of to much information, but I think a lot of people would be interested in the other information as well.
Maybe I just don't know enough about the build.prop file yet, but if someone could give me any links about more information on it that would be great. Or if anyone has a link to a list already like this that would be great as well. Sorry if I'm being a noob, but I've done quite a bit of searching and haven't found anything yet.
Thanks in advanced for any posts,
Cobra
It doesn't matter which phone, android is android.
But everyone uses other build.prop edit's, there are no original one's..
Thanks for that information.
So if there aren't any original ones, are there possibly ones that work well specifically for the One S? I know the Fast.Dormancy one is supposed to be effective for some carriers. And though, this may be a setting that could be effective for many devices, does it not make sense to maybe start a thread or some sort of page listing all the settings that effect this device in particular in certain ways and which carriers they work effectively on?
I ask these questions because, yes I am a newb and I feel like these things could be helpful to other noobs. it's almost as if I'm trying to learn some sort of ITIL based thing I guess. I guess to me it just seems effective to have a list of things that can help make your device work more effectively. For instance, have one page, say the wiki, linking to different things to help you setup your phone how you want it, and to make it so it will work as effectively as you want it for yourself.
Now I realize that the Wiki currently has things such as how to unlock, root, flash roms, lists of roms, etc. But, it doesn't really say, "Hey, here are a list of things you can do to make your phone more efficient without having to flash a new ROM, and here are ways you can make your own ROM, here are some paths to certain things specific to this phone.
I know the Wiki is new, but I guess what I'm saying is if nobody else is working on this stuff, can someone give me a hand in finding all this information so I can start adding it to the Wiki?
Hi everyone at XDA and Sidekick users.
Hopefully one of that reads this post, has had or is familiar with the *.sq Squash files, that were flashed to early Danger Sidekick models, particularly in my case at least, for flashing the developer Key. I have come into contact with a key on 5.x Lib version, but that key is in the form of a .JAR file. Even extracting the JAR file yields no precise match to these older squash files.
As my quest continues to restore internet capabilities in my interest to my phone, a dev-key would be the neatest way, as I could use the SDK to write apps that neglected dead Danger servers, and once again functioned properly. I do this with my love for the Sidekick 2.
So, anyone out there who still has access to a Squash dev-key file, please PM me. Or, if you have any knowledge that pertains, please contact me.
Thanks in advance,
You may want to search on these forums for a link to the old SDK if that might help. I also wonder if someone has a developer key someone for another phone. With that and the IMEI of the device it was intended for, you *MIGHT* be able to figure something out, but someone with more knowledge than myself would be able to tell you better. Maybe Orange808?
ged92781 said:
You may want to search on these forums for a link to the old SDK if that might help. I also wonder if someone has a developer key someone for another phone. With that and the IMEI of the device it was intended for, you *MIGHT* be able to figure something out, but someone with more knowledge than myself would be able to tell you better. Maybe Orange808?
Click to expand...
Click to collapse
I can look over the contract again, but I am certain the dev contract forbids me. After they started really locking down the platform, I remember signing an agreement that is only rivaled by Apple's dev contract.
With that said, they handed out developer codes like candy in the early days (with no strings attached). I bet you can find another source.
So I am going to post this here, because the development section is ferboten to people trying to offer useful suggestions. Geez, I hope this is the right section.
Let me set it up. ANDROID IS BASED ON THE LINUX KERNEL. Everything, and I mean everything after that fact becomes android and bloat. Given this as the basis of all things android, I have a simple set of guidelines that should be used to create a solid, reliable, bullet proof operating system for devices able to use the android operating system.
#1. Create the kernel boot section of the basic platform that supports the very basic hardware features, including touch screen, radios, power/charging/battery management, wifi, bluetooth, nearfield, audio, microphone, s-pen,etc. Basics only. Root access is standard and can be turnd on/off just like developwer functions. No special tricks or addon hoops to jump through.
#2 At this point STOP. Every single process or service to be run on the device from this point forward should be able to be individually selectable - or not. Yes, I understand that individual services or apps may have dependancies to other processes and that thouse need to be functional in order for a particular app to work. That is why, each additional service or app must list the dependencies and in the selection process, the installion will be required to verify you have the proper services installed and functioning, if not to list them and allow you to make the decision to proceed. Viola, we have NO MORE BLOAT WARE.
#3 Make selecting additional services/apps selection process a menu driven, tag selectable process. Make the unselection process smart to verify and identify the other apps dependant on the item you are killing/removing.
#4 Allow a built in snapshot option to capture the entire system as you have customized it for yourself and allow it to be backed up to external memory with the ability to bring it back, AT WILL. With no big hassles.
Those 4 items are a good start. By themselves alone, it would put all of us in the drivers seat of controlling and living with our devices.
I am aware that such a system is not for everyone. It does require some basic technical understanding of the process. But for the vast majority of users, I am certain, that an a la carte system is far superior to the bloated monstrosities being forced down our devices.
I would appreciate any refinements to my suggestions.
The silence is deafening. It has been days. Kind of says something, don't you think?
I am so very happy (not) that these boards a compartmentalized to the point where you can't get through.
Pretty much a waste of my valuable time, especially considering the fact that if my suggestions where applied, people would be clamoring for an installation with those features. I guess there is not much true "developer" in xdadevelopers anymore.
Funny guys, with the pay to remove ads spam here. Really? Why? For what.
I leave here disappointed. Not angry. Just sad.
I'm not a developer so I have nothing valuable to contribute to your suggestions in your original post but I can offer an observation regarding your perception of the level of contribution to your thread and that is the fact that is particular area of the forums probably isn't the ideal spot to have a discussion such as this. You figured that out already so sure you can call me Capt. Obvious if you wish but I'm just pointing out that yes the forums are compartmentalized (as you've stated) in such a way that development for each device is separated out. This development is centered around AOSP based ROMs or "stock" ROMs (using manufacturer released source) so if you're looking to have higher level discussions about what AOSP should look like then deep down at this device specific level probably isn't where you want to be. So there's that . . . then there's the fact that for this particular device you can basically hear a pin drop in the sub-forums as it is since nothing much is going on by way of development.
Where specifically such a discussion would see more input I'm not sure, perhaps the main general discussion section?
Thank you for your sobering reply. I get frustrated. Already had my post bounced out of "wrong" forum while trying to speak directly to "developers" (i wanted air quotes because the term does not accuratly describe its target) So I tried this. The note pro 12.0 is still the best hardware giving the ipad a run for its money. The problem its monkeyshines kiddie software running it, or not running, or barely running it. ANDROID, indian word for crappy wannabe software, developed by clueless kids.
Again, thanks for the gentle nudge. I appreciate someone willing to conduct a conversation
Are you looking for an Ubuntu or SUSE type of setup?
I think what you are looking for is similar to apt-get type of installs, I could be wrong of course. This might be helpful for many "users". I think one of the barriers is that there are slight differences between the models of tablets, and creating the logic to put in for the sub-dependencies might prove problematic. You might get more answers to this possibility by asking one of the developers directly and sharing with them. Not a developer myself.