Related
Hi,
I would like to request a feature which I think would be real help either on XDA-developers.com or wiki.xda-developers.com[
There is an excellent matrix of differences between the different HTC models & the names different phone providers give them.
I've tried using searching terms like 'comparison' or 'differences' (between XDA's) to find it, but the search engine does not seem to be speaking my language.
1.
I think having a better main page hotlink to such a comparison Matrix would be REALLy helpful, PARTICULARLY as the matrix is (hopefully) updated regularly and has lots of hotlinks to the various models.
2.
The second request is to somehow display details in a list of phones as they are released so that I can see whether the XDA I'm waiting for (or similar) has been released.
Thanks for an EXCELLENT site
OLa,
After a long wait and some leaked beta's now the first public Firefox for the PPC VGA/WVGA
http://rapidshare.com/files/197211080/fennec-0.11.en-US.wince-arm.cab
Drop a line after using it!
Fennec Milestone Release for Windows Mobile
02.10.09 - 08:40am
On behalf of everyone who have been tirelessly working towards this goal, I would like to announce that our first milestone release of Fennec for Windows Mobile is now available for download.
This release is pre-alpha, and intended to get the product into the hands of early adopters in order to get feed back and bug reports. In order to focus our efforts on getting this release out, we have targeted only one device, the HTC Touch Pro. This has a number of user interface implications, including graphics designed for a 300 dpi screen, control layout intended for a vga screen and reliance on a hardware keyboard for text input.
Installation
You can install this on your HTC Touch Pro by navigating to the cab installer with your existing browser. This will download the cab file and kick off the installation process.
Alternatively you can download the cab file to your desktop and transfer it to your device via activesync. Once the cab file has been copied to you device, navigate to it using file explorer (on the device) and click on the cab file to launch the installer.
Please note, its been brought to our attention that some carriers are filtering web traffic to preclude downloading cab files. If this is the case with your carrier, you’ll either have to download to your desktop and transfer by activesync, or be connected by wifi if you download directly to the device.
Status
Our focus to this point has been to have a working, usable browser. To get there in a hurry we have punted in a few places, and I’d like to point a couple of them out. First is the update mechanism (both for the browser itself and for extensions). After installing this release, you will not be offered updates automatically, so please stay tuned for follow up releases. Also, we have disabled plug-in support. This is one of our high priority items going forward. Finally, as I mentioned before, there is no soft keyboard support. On an HTC Touch Pro, you’ll have to slide out the keyboard to enter a url.
Besides the release, we marked another major milestone yesterday when the final patch to NSPR landed and we were able to build for Windows Mobile off Mozilla’s trunk for the first time ever. I say the first time because minimo was built from branches of both NSS and NSPR.
“leaks”
Over the last week and half there have been several blog posts and “news” articles floating around the internet about leaked Windows Mobile Fennec builds. This has been fairly entertaining to those of us working on the project for a couple reasons. First, the builds that these posts have pointed to are the builds that I pointed to on twitter. They were intended to be used by the developers working on the project (or anyone else willing to deal with really buggy software) to find bugs before we pushed anything out to the general public.
Also, the concept of secret, leaked builds flies in the face of how Mozilla operates. Our source code is out there for everyone to see. We have a bug reporting system that anyone can (and is encouraged to) access to file new bugs or track the progress of existing bugs. The majority of our discussion around the project is entirely public on irc, our wiki or our meetings and conference calls.
I have been working for Mozilla for 16 months now. At first its a bit of an adjustment to having everything you do or say out there in the public. But after overcoming that initial shock, its a point of pride. This project goes to extraordinary lengths to be open and transparent. If you are going to write about Mozilla, take advantage of that. Read our meeting minutes, hop on irc to ask a question or even dial into the weekly status meeting. Its all out there, just look.
Gr
http://ftp.mozilla.org/pub/mozilla.org/mobile/
Are you really sure about that ?
because there are no news on the mozilla's website ????
hm. after a very slow loading I see the adressbar, but cannot open the keyboard
to enter any address...
this thing is sad!
This can’t be an official release! I really don’t believe they would release this garbage.
I installed on the Touch HD and the Touch Pro and nether works.
Don’t waste your time!!!!!
OK OK please use the search function before posting !!!
This is not the official release it is the beta version and has already been posted !!
---> http://forum.xda-developers.com/search.php?searchid=20889598
This shouldn't even work anyway because it seems designed to be for vga like touch pro.
If you want you can get the windows version HERE just to see what it's like...
Looks pretty interesting and it's apparently amazingly fast on the N810.
it's beta, so no need to complain about
But, I'm looking forward to the first running version
I can also confirm it doesn't work but it does look promising, it is very jerky on the touch hd and takes forever to load and i had to use a bluetooth keyboard to input text and pages dont load but apart from that I'm still very much looking forward to seeing this completed.
From @windowsphone on twitter: http://newwp.it/i6NfzI
On the last page there's this question, "What, if anything, would you change about your Windows Phone 7?" Bombard away with what MS needs to be working on (file management or at least local document sync, direct Outlook sync, etc.) Please make sure what you guys write is thought out and most importantly, grammatically correct.
* Give us an official support page and a contact number for issues
* Clear outline & timeline of future updates
* More frequent updates and force carriers to deploy them in maximum of 45 days
* Enable to use own MP3 ringtones
* Sync directly to Outlook
* Allow tethering
* Turn by turn navigation for Australia with better maps
* Allow unlocking of the device for a one of fee! Only charge per year when someone wants to submit to marketplace
janemanno1 said:
* Give us an official support page and a contact number for issues
* Clear outline & timeline of future updates
* More frequent updates and force carriers to deploy them in maximum of 45 days
* Enable to use own MP3 ringtones
* Sync directly to Outlook
* Allow tethering
* Turn by turn navigation for Australia with better maps
* Tom Tom,Garmin etc GPS compatible software
* Allow unlocking of the device for a one of fee! Only charge per year when someone wants to submit to marketplace
Click to expand...
Click to collapse
Amen to all of these.
Just changed one thing for every other country.
More recent hardware, and I am in.
agp64 said:
Amen to all of these.
Just changed one thing for every other country.
Click to expand...
Click to collapse
agreed
Zune Pass in australia. Our zune hub isnt very pretty without it
Well, I would like to see multitasking, some options on the right of the home screen, let's say a button, that would open a line of Wifi on/off and etc., Copy paste, better browser. And what's important- update devices, give more info about the updates, what is coming and when
janemanno1 said:
* Clear outline & timeline of future updates
Click to expand...
Click to collapse
FWIW, remember a little thing called "Longhorn" (aka "Vista")? So many promised features and released dates missed. I doubt you'll ever see anything other than vague descriptions and nebulous dates, Microsoft has been slapped around too much in the past for missing promises.
My comment:
- SkyDrive if you dont have sharepoint in the officehub.
- More reliable push notifications.
- Expanding Facebook integration with ability to send private messages from the message hub to facebook and other services... but this will probably not happen so hope the fb app gets better with notifications.
I would love to have a bug free ZUNE , it is crashing all the time and sometimes with BSOD'S
Turn-by-turn voice nav
User selectable ringtones and sounds
User created email folders
More themes and UI customization
Screen capture
Copy & paste
A good one:
http://wmpoweruser.com/the-art-of-stalling/
doministry said:
A good one:
http://wmpoweruser.com/the-art-of-stalling/
Click to expand...
Click to collapse
That is unremarkably sad. I didn't know it was that serious.
That is unremarkably sad. I didn't know it was that serious.
Click to expand...
Click to collapse
I think you mean remarkably sad?
And android wasn't the same way at launch?
I purchased the HTC Magic on launch day from Rogers.. Android market wasn't made available to us in Canada until roughly 5 months later..
I didn't get turn-by-turn until aprox a year or so later..
No voice search until ...what...3 updates which took roughly a year and half (1.5, 1.6...2.1)
They day I dumped my HTC magic I still didn't have local search.. unless I opened a browser and went to Google.CA and specified my city in the search field.
WP7 wil catch up eventually, it's still a baby OS compared to the others. Android didn't really become great until after 2.XX
I agree with other with the timeline business. I'd like to see that as well.
I just put a CDMA version of WP7.... It is about time we have the option of getting one.
Things to change about Windows Phone 7
--------------------------------------
1) Password protection on email. This is needed when you hand your phone to someone to check out or use and don't want them to be able to just click on your email while that happens and read private emails.
2) The marketplace should have an option to download first and install later. This is because public wifi or data plans in general are not nearly as fast as using your local wifi. You might pop into a coffee shop or mcdonalds to try some new apps on the go and you want to maximise your use of the wifi while you are there to get through the download queue. Installing/unpacking can take quite a long time but that can be done when you are no longer connected. This also aids in saving on limited data plans. With this approach, if there is no more space currently left to unpack the queue should move on and unpack successively but keep downloaded packages on the device to be installed later once the user frees up some more space.
3) Better managaement of marketplace download queue. I have had stuck downloads before, particularly at pending or corrupted downloads that were stuck at the installing phase. You should always be able to cancel or retry something. These options only come up when "attention is required". Queue reordering is also a strong "nice to have".
4) Better Management of phone download history. For example, when I restore a phone I don't want it to queue up literally everything I have ever "purchased", especially many trial or free apps. There should be a special "restore" queue for indispensible games/apps that you do want to automatically redownload when this happens.
5) Better lock phone i.e. android combination swype. The current 4 digit system is too easy to see over the shoulder and easily brute forceable, even more so if someone remembers only some of the digits.
6) Complete application data/isolated storage sync. Anytime you are at a local computer or connection to sync, you should have an option sync the latest application data for example news feeds and media as well. This way data connection apps are still useful in places without a connection i.e. subways. I understand this is a major feature just by itself
7) VPN options
8) Local file management/drag and drop.
9) Ability for Zune to play and organise media by folders with 8 implemented.
In general I think WP7 should be stronger with local/isolated storage features and not be so cloud dependent. The combination of cloud + local services will be a killer combination. In addition I think WP7 should be going after Android's #2 spot right now and not iPhone which it currently cannot compete with. Android has many weak spots including lower requirements on apps and games resulting in weaker quality when compared to WP7, lack of SD installability for many apps. and generally unpolished "iphone knockoff" feel. Secure #2 spot for now, which will be a good base to attack iPhone from. WP7 is already superior to Android in UX now and can gain quickly in app diversity and features.
Right now the OS feels like a beachhead but a strong one. There is good work, but unpolished and incomplete but the war can still be won. Keep fighting the good fight
The bottom line is that if MS wants this OS to fly for real, in the long term, they need to get their act together.
stillriza said:
I think you mean remarkably sad?
And android wasn't the same way at launch?
I purchased the HTC Magic on launch day from Rogers.. Android market wasn't made available to us in Canada until roughly 5 months later..
I didn't get turn-by-turn until aprox a year or so later..
No voice search until ...what...3 updates which took roughly a year and half (1.5, 1.6...2.1)
They day I dumped my HTC magic I still didn't have local search.. unless I opened a browser and went to Google.CA and specified my city in the search field.
WP7 wil catch up eventually, it's still a baby OS compared to the others. Android didn't really become great until after 2.XX
I agree with other with the timeline business. I'd like to see that as well.
Click to expand...
Click to collapse
So what I hear you saying, any company that puts out products should not consider the current state of the industry? What should Apple do with the next iPhone? Put one out without all the current features and then migrate those features into it over the course of a year? Or how about the car companies, they should put out cars without navigation or high tech stereos or computer aided engine controls and just migrate those features into them over the course of a year?
Far be it from MS to stay up with even itself on new products and put out a smartphone without the current state of the industry features. Let them put those features in over the course of a year...or two. It's unwise to bring a mature product to market. People might begin to expect that kind of thing. Bollocks!
My feedback on the online survey:
-Current phone - WM 6.5
- Next phone - (i) Android
(ii) Other- Windows Mobile, if it is revived , will be preferred over Android
Suggestions:
(i) I don't like the Homescreen, it should be more customizable and at the very least the tiles
should be resizable.
(ii) There should be a favorite people hub with the option to pin a contact directly to this hub from
the contacts list (tap and hold on contact should give at least 3-4 options viz. pin to favorites, pin
to start, edit & send)
(iii) After device purchase, the user should have the option to replace the homescreen with an
approved one from reputed developers(I will prefer a solution from SPB software).
(iv) There is too much scrolling in the program list, option of grid view should also be there.
(v) Size of headings too large in the hubs. The headings should either be in a background layer or
they should Auto Hide after somtime and be replaced with blinking arrows on the left/right edges of
the screen.
(vi) File Explorer + Multitasking.
(vii) Office applictions should be more powerful.
(viii) Availability of powerful Calendar & Task management applications like pocket informant.
(x) Revival of Phone/End hardware buttons.
Forgot to add - (xi) Revive Smart-dialling
(xii) Bring back outlook sync
MartyLK said:
So what I hear you saying, any company that puts out products should not consider the current state of the industry? What should Apple do with the next iPhone? Put one out without all the current features and then migrate those features into it over the course of a year? Or how about the car companies, they should put out cars without navigation or high tech stereos or computer aided engine controls and just migrate those features into them over the course of a year?
Far be it from MS to stay up with even itself on new products and put out a smartphone without the current state of the industry features. Let them put those features in over the course of a year...or two. It's unwise to bring a mature product to market. People might begin to expect that kind of thing. Bollocks!
Click to expand...
Click to collapse
I agree with you.. but what I was saying is Android was the same way. Apple already had a pretty good grip on the market at the time Android launched. As per what you mentioned above.. it was clear Android didn't have a grasp of the then current state of the market. Several updates later.. and look at them now.
Basically, any company that puts out a product should consider the current state..but sadly that just doesn't always happen. The phone is pretty complete to I would like to say 70% of the general phone using public. It seems MS had targeted the OS to those switching from 'dumb' phones, if you will, to smart phones. The only people who are really hurting would be the power users. The updates will come.
This is a short summary of some important general points for posting new ROM's.
It should be considered as an optional "add-on" to the general thread:
"Galaxy S I9000 Android Development **STICKY THREAD** Read here first!"
The number of man hours spent working and developing new custom ROMs are astronomical! So why then, is it that so few new ROMs are successful? Basically because of lack of information and poor public visibility/involvement of the developers themselves. It's just like in any other successful business, you have to make your product or service stand out from the rest. Either by making an amazing product or by being a great inspiration for others to follow. Here I will try to explain and list some fundamental ideas, in order to make your ROM better and more popular.
When a would be ROM flasher is looking around for a new ROM, he searches the web and the XDA-forums for threads, usually beginning with the text "[ROM]". Next he/she look at the FIRST page where the developer (and his/her team) is presenting the various features of their new design. What is presented there will often be a decision maker for whether or not someone wants to try it out.
There are a few things that consistently differs between "good" ROMs and "bad/poor" ROM's. These things are often and naturally related to the amount of information available around the ROM in question. Someone who have put down enough mind, sweat and hart into the production (cooking) of a ROM, would also like to share his/her effort in the best possible way, not minding writing a detailed and useful description about their product. The items found below are part of some of these things that do MAKE A DIFFERENCE.
- Primary Purpose:
Essentially a description why you want to provide this ROM and why you think it is needed. What are the main features and driving forces for providing this ROM?
- Ultimate Gaming Experience
- Super stability
- Super Compatibility
- Great Battery Duration
- Minimalistic User Interface (UI)
- Simple to use functionality
- Latest and coolest never seen before interface behavior
- Fully loaded with ultimate editions of absolutely everything
- Mobile Penetration Testing Platform
- or perhaps just for educational or experimental purposes etc...
- Up-to-date Maintenance:
That means an active developer (or group of) who are readily available to answer questions from users of all levels, new or advanced! Often that they should be inhumanly available at all times of the day & night!
- Up-to-date Firmware Release:
That means the the source of your ROM is preferably based on the latest, but publicly available code/firmware. Not on some hidden leaks or old hacked code. When I say "hidden leaks" here, I mean the kind where the origin of the code (compiled or not) cannot be verified or downloaded. (BMW doesn't make car/sales advertisements using 2 year old engines from unknown/secret sources!)
- Detailed CHANGE-LOG:
People want to know that what they flash on their phones, is as close as possible to what they would like to see and use. Also from a paranoia perspective most of us would like to know that it doesn't contain 3rd party or other strange applications that we will never use, or which will give us trouble when we want to add/update applications, at a later time. A description of the various applications is also very useful. Most people would wonder what the "DarkBotSendHelper.apk" is doing on a phone.
A change-log would ideally consist of a list with:
- Title: Change Date and the custom ROM Version the changes apply to
- Full application name
- Full application version
- Short application description
- Link to application source-code, if available
- Link to application on "Android Market"
- Reference to what hacks has been made, if any
- Reason for why the hack is needed
- Unresolved BUG-LOG:
A brief log of bugs and unresolved issues that affects the current release. It is hard to explain without cussing how annoying it is to flash a new ROM, just to find out that some WiFi issue has not yet been resolved, which was posted on page 456/1200! If people post bugs/issues, that cannot be immediately resolved, please add those issues to the BUG-LOG, on the front page.
- Screen Shots! Updated Screen Shots!
The importance of good screen shots can never be enough emphasized! Many ROMs are updated continuously and if the screen-shots doesn't match what the user installs, he's gonna go WTF!, and will start to peppering your support threads with questions about how to install this and that, and how to get the same themes you are using in those screenshots, or from another different ROM altogether! You wouldn't be able to sell a new BMW with a picture of an old Volvo, would you? So why do you think a ROM would be any different? Also include a brief caption about the essential feature(s) shown, for each picture.
- Detailed Installation Instructions
This hardly need more explanation apart for making sure you also say something about:
- WIPE/No-WIPE
- Bootloader Requirements
- Recommended Procedure
- Detailed Device Compatibility List
Yes, the same gross model name/number of a particular device, may very well have some minor variations that can render the device completely incompatible with software from it's apparent twin-brother. Or even certain Firmwares may not be compatible to slight manufacturing variation. See for example the "Samsung Galaxy S" with their sub-models GT-I9000(B/M/T), and to complicate things further, even within the same model there may be slight differences, like in the PCB of the USB-port of the SGS2 GT-I9100.
- Detailed Language Compatibility
What do people use their phones for? Communication! Sure, some use them as a game pad, but after all it is primarily a browsing and communication device. So if you can't use your primary languages with your device, it is useless! Although some network operators are only beginning to understand that most of the connected world is at least bi-lingual and often much more. Thus it is of essence that your phone's keyboard, screen-reader and web-browser can read, display and understand most characters and alphabets around. (I.e. I still fail to understand why it is virtually impossible to find a phone with Russian, English, Spanish and Norwegian keyboard layouts/character sets or at least let me select these my self!) In addition it is very confusing for a first-time ROM flasher to understand the need for all the various PDA/PHONE and CSC region settings, which are often modified and re-packaged for a well cooked ROM, and thus no longer adhere to the original regional code.
So when you cook your ROM, please provide as much information as possible regarding how the user can adapt their phone to his/her own languages. This information includes at least:
- What languages are available for basic operation (the operating system)
- What languages are available for the keyboard mappings
- What keyboard applications can use these languages (Swype, Samsung Keyboard etc.)
- Simple instructions how to include, use and set the phone languages
- List of Technical Terms and Definitions that describe the ROM
The world of mobile device development is packed by technical jargon and abbreviated terms. Many times they are also abbreviated and used in the wrong context, although some the community know what it means. Simplify your vocabulary and clearly define your terms and stay with community standard ones!
- General Presentation
Like any other business presentation, please skip the HUGE fonts in a zillion colors. Most of us are neither blind nor illiterate, but you may risk to come across as being both, with those type of fonts. Remember "KISS"? - Keep It Simple Stupid.
- SPELL CHECK!!
It's embarrassing and very annoying to read descriptions of how great, professional and how well maintained a particular ROM is, when the text is riddled with misspellings, wrong words and childish grammatical errors. Although most of us are very understanding that we are living in a multicultural and multilingual society, sometimes all I think about is, how a person who doesn't know how to spell check, could ever be able to cook a mobile phone ROM. Most text editors feature at least some basic spell checking, bloody hell, USE IT!
- CREDITS
Most of the Android development community is completely driven by voluntary and open source work. Make sure to include the correct credits to those persons who have contributed to the various info/hacks/software that you include in your ROM. Use a separate list for the credits, that include the name (handle) and how/what he/she did to contribute.
2 Good Examples:
http://forum.xda-developers.com/showthread.php?t=1350763
http://forum.xda-developers.com/showthread.php?t=1155776
Final Words:
It is very likely I have missed something here, or that you (as a developer or moderator) disagree on something I have written here, if so, please provide your constructive comments how I can improve this list and post.
In Great Expectations and Hope for Many New Amazing ROMs!
- E:V:A -
PS. This was posted in the "Developer Section" as it applies only to new ROM development threads, and I wouldn't consider this neither as "Q/A" nor "General". But if OP/MOD know of a better suited place, please just move it there...
Also I am not aware of a similar post to this one, even after searching XDA quite a lot. So if it already exists, it is not easy to find and should be reposted or stickied!
<Reserved>
@E:V:A
The only thing that I missed so far is a thread like yours.
Agree on all requirements of released software.
Sometimes I wonder how some "devs" priorities are stacked regarding quality control vs. early delivery on pay-per-download sites.
Not sure what is best place for this thread. Counting # of posts in General asking Q already answered in stickies, it's kind of accepted to skip reading what's there. :-\
Perhaps keep it alive as hottest thread here?
Tapatalked - There's a Thanks button somewhere
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Rahulrulez said:
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Click to expand...
Click to collapse
YES! Not giving credit where due is horrible, basically just forgetting all the hard work another individual has put in to the "feature" of your ROM. Also, this should probably be in general.
RDF SEEKER
Now with more android!
For details on the windows version of RDF Seeker see my XDA thread here
Hello everyone!
Say hello to the newest RDF Seeker!
This puppy is an all new concept designed specifically with Android in mind!
Who wants to search for rdf files? I sure don't! I say let your phone do the searching! RDF Seeker for Android is designed with this exact concept in mind!
Unlike the windows version of RDF Seeker which is designed for batch rdf searches,
RDF Seeker for Android checks for the latest rdf file automatically and then notifies you when a new RDF is found!
>>Features List<<
Automatically checks for new RDF's so you don't have too.
Supports downloading RDF files into a reading friendly format
for viewing in a text editor on your phone.
>>Bugs<<
Please report any bugs in this thread.
>>Change Log<<
Current Version 1.5
- Option to keep original xml formated RDF files
- Long press to delete individual logs (Keeps data files)
- Force Check is now "Check date" and has the choice of what date to check.
- Fixed database bugs
- Fixed notification bugs
- Fixes RDF checking on devices running Android 3.2+
- Fixes graphics issues on tablets running 3.2+
Version: 1.4
- RDF checking should start when the device turns on, if it was running before.
- Added a built in viewer
- Clicking rdf links in apps should prompt to open RDF Seeker
- Added share button
- New icon
- Added change log
- Clear history now erases previous downloads as well
- Clear cache is now clear downloads
Version: 1.35
Added Epic Touch 4G support
Added Force Check
Notifications should now vibrate and make sounds
Paved the way to add more devices in the future
Other background improvements
Bug fixes
Version: 1.1
Fixed 3g rdf downloads/checks
Fixed notification bug
Version: 1.0
Initial Version
>>Things to do<<
Download RDF files to a user specified directory
Different icon for new RDF notification
(Currently uses the android download notification icon)
>>Downloads<<
Google Play
This is cool helpful for those who like to know their device is still being worked on
Sent from my SPH-D700 using xda premium
Looks like rdf checking / downloading isn't wokring over 3g. Should have that fixed early tmrw.
Wifi works great
Sent from my SPH-D700 using Tapatalk
Hey, I am jumpinh over here from the Epic Touch side. You have a popular following over there. Anyways, I had a feature request.
Would it be hard to add a custom box to search for a device that is not thought of yet. Suppose there was a SPH-XXXX that was coming out or even a HTC device. It would be great if there was a custom field. I know how to search it in the browser but your app would add some convenience for that purpose. Especially since it automatically checks.
Thanks
Sent from the guy who will never buy Klipsch again.
kc_exactly said:
Hey, I am jumpinh over here from the Epic Touch side. You have a popular following over there. Anyways, I had a feature request.
Would it be hard to add a custom box to search for a device that is not thought of yet. Suppose there was a SPH-XXXX that was coming out or even a HTC device. It would be great if there was a custom field. I know how to search it in the browser but your app would add some convenience for that purpose. Especially since it automatically checks.
Thanks
Sent from the guy who will never buy Klipsch again.
Click to expand...
Click to collapse
If you could give me a few examples of other devices then maybe I can make something happen
I would need:
- RDF urls (yes thats it lol)
snargledorf said:
If you could give me a few examples of other devices then maybe I can make something happen
I would need:
- RDF urls (yes thats it lol)
Click to expand...
Click to collapse
Sorry for bringing back a thread from the dead, but there are many new devices out there with RDFs...
Galaxy Nexus - http://device.sprintpcs.com/Samsung/SPH-L700/
Galaxy S3 - http://device.sprintpcs.com/Samsung/SPH-L710/
Boost Galaxy S2 - http://device.sprintpcs.com/Samsung/SPH-D710BST/
Nexus S 4G - http://device.sprintpcs.com/Samsung/SPH-D720/
Transform Ultra - http://device.sprintpcs.com/Samsung/SPH-M930/
Conquer4G - http://device.sprintpcs.com/Samsung/SPH-D600/
Confirmed LG RDF for Viper - http://device.sprintpcs.com/LG/LS840/LS840ZVG.rdf LG appears to just go up one letter/digit ie LS840ZVD, LS840ZVE, LS840VZF, etc
Here is a guess on a Motorola variant of the rdfs....
Photon Q - http://device.sprintpcs.com/Motorola/XT897/
I don't know what the Motorola releases are named, but its worth a shot...
Basically if you go to http://device.sprintpcs.com/*manufactuer*/*model*/ a 404 means bad request and a 403 is forbidden, meaning there is a folder there, but file listing is not available.
It would be nice if the search was variable, IE give the user the opportunity to input the Device Manufacturer and Model into the search string. Let's say the Galaxy Note 2 becomes rumored as SPH-L720, give a search where the user can select Samsung and enter a model number and your app search on it.
Also, a submission option would be great to get new model numbers to the developer for addition to the app.
Maybe make a free and paid version with the paid version being able to search for user entered strings. I'd pay a few bucks for that...
jefbal99 said:
Sorry for bringing back a thread from the dead, but there are many new devices out there with RDFs...
Galaxy Nexus - http://device.sprintpcs.com/Samsung/SPH-L700/
Galaxy S3 - http://device.sprintpcs.com/Samsung/SPH-L710/
Boost Galaxy S2 - http://device.sprintpcs.com/Samsung/SPH-D710BST/
Nexus S 4G - http://device.sprintpcs.com/Samsung/SPH-D720/
Transform Ultra - http://device.sprintpcs.com/Samsung/SPH-M930/
Conquer4G - http://device.sprintpcs.com/Samsung/SPH-D600/
Confirmed LG RDF for Viper - http://device.sprintpcs.com/LG/LS840/LS840ZVG.rdf LG appears to just go up one letter/digit ie LS840ZVD, LS840ZVE, LS840VZF, etc
Here is a guess on a Motorola variant of the rdfs....
Photon Q - http://device.sprintpcs.com/Motorola/XT897/
I don't know what the Motorola releases are named, but its worth a shot...
Basically if you go to http://device.sprintpcs.com/*manufactuer*/*model*/ a 404 means bad request and a 403 is forbidden, meaning there is a folder there, but file listing is not available.
It would be nice if the search was variable, IE give the user the opportunity to input the Device Manufacturer and Model into the search string. Let's say the Galaxy Note 2 becomes rumored as SPH-L720, give a search where the user can select Samsung and enter a model number and your app search on it.
Also, a submission option would be great to get new model numbers to the developer for addition to the app.
Maybe make a free and paid version with the paid version being able to search for user entered strings. I'd pay a few bucks for that...
Click to expand...
Click to collapse
Love all of the suggestions. Some have been previously mentioned and I had begun to look into them (User specified model number) but due to life getting in the way (Read having a full time job) I have been unable to make any headway towards another update.
If and when I get some time to get to work on this app again, I intend on doing a full rewrite in order to implement many of the features you have specified here.
Thanks for letting me know that there is still an audience out there that finds this app useful.
Thanks for the reply, I'll keep digging and adding info here.
Here are two confirmed Motorola rdfs for the Photon Q
http://device.sprintpcs.com/Motorola/XT897-SPRINT/771Q6SPR89ASA36.rdf
http://device.sprintpcs.com/Motorola/XT897/771Q6SPRASANTIG33.rdf
You can also do the following to get the latest RDF (not sure how accurate this is)
http://device.sprintpcs.com/*Manufacturer*/*Model*/latest
http://device.sprintpcs.com/Samsung/SPH-D710/latest
http://device.sprintpcs.com/Samsung/SPH-L900/latest
http://device.sprintpcs.com/Motorola/XT897/latest
http://device.sprintpcs.com/LG/LS840/latest
http://device.sprintpcs.com/HTC/APA9292KT/latest
Quick update.
I've started some basic work on a new version of RDF Seeker for Android.
The new version will include many of the features requested by users as well as some I have been thinking of since I first started RDF Seeker.
Some features which will be in the new version are:
1. User defined devices. No more hard coded devices!
2. Ability to view the latest RDF for a device.
3. Multiple device searching! No longer will you be forced to choose a single device to monitor. Monitor as many as you want!
One thing I would like to make people aware of is my intent make this app ad supported. Ad's will be minimal, and there will be a paid version ($1) which will remove them if you want. I know it's a bit of a bummer, but hey I have bills to pay ya know.
Do to the amount of changes needed to implement many of these features, I am going to have to re-imagine pretty much the whole GUI/Workflow so there still isn't an ETA.
Just wanted to let anyone out there who still uses this app know that work is being done!