Develop Bugs

1800PocketPC.com WP7 App [Dev Thread] Need some help please. Pretty please.

So, Ive made the app for 1800PocketPC & thought I would make a thread about its development,
mostly because I need a bit of help from those with greater knowledge than me
Saijo (the owner of the site) has already made a thread about it over here CLICKY.
There is also a page on my website about it here: CLICKY
Features:
Displays the latest article from your chosen feed on the homepage.
Shows feeds from these different areas:
- News
- App Reviews
- Game Reviews
- General games news
- Free games news
- Xbox Live games news
Displays articles in a mobile friendly way.
Gives you the opportunity to contact the site or the developer (me).
Due to the youtube plugin not working in 3rd party apps, links to the
mobile youtube page are dynamically added to the menu.
The same applies to marketplace links, which would not open strait
from 3rd party apps, links are dynamically added to the menu instead.
You can view & add comments posted on any article.
There is landscape support throughout all but 1 part of the app.
You can also get achievements!
You can download the current version here:
Or you can like it on Facebook here CLICKY
Im currently working on the next major build, which will add:
Twitter & Facebook integration.
Overall UI improvements.
A better mobile reading experience.
Full portrait/landscape support.
Location based advertising off by default.
Now, what I need is help with at the moment is facebook & twitter.
I found a brilliant tut here & I transplanted some of the code from there, so It can now share articles to facebook.
My problems are these:
I don't know how to post to twitter.
I don't know how to get & display all posts from someone's facebook wall (namely the bestwp7games & 1800pocketpc pages)
I don't know how to get & display all posts from someone's twitter account :/
So yeah, any advice would be greatly appreciated.
Google hath fail'd me

Being as polite as possible, you need to search. If you ask questions like "how do I ..." you're not really progressing as a developer, as the two services you mentioned have amazingly detailed and well-defined APIs.
I will point you to the kind of Google queries I use to find these answers, that way you can keep developing without wasting time waiting for other people to answer:
Twitter: http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=update+twitter+status+c#
FB Wall Posts: http://www.google.co.uk/search?sour...ebook+wall+posts+c#&pbx=1&fp=b0dc1443d535784d
Recent Tweets: http://www.google.co.uk/search?sour...&aq=f&aqi=&aql=&oq=&pbx=1&fp=b0dc1443d535784d

Thanks. You're right, I probably should have searched more.
I was a bit afraid Id find something & try working with it only to find it didnt work with WindowsPhone :/

[REF] How To Post and Promote a New ROM

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.

[REQ][XDA WIKI]: Feature request thread

Request 1: Add HTML Tidy to the xda wiki stack
Template:Navbox @ Wikipedia said:
Using this template on other wikis requires HTML Tidy to be turned on. A version that does not require Tidy can be found at Wikipedia:WikiProject Transwiki/Template:Navbox. (That version generally shouldn't be used here on the English Wikipedia.) More detailed information on copying {{Navbox}} to other wikis can be found on the talk page.
Click to expand...
Click to collapse
I've been doing a LOT of work adding stuff to the xda wiki, but I've hit an impasse, some of the most complex templates used on Wikipedia depend on it being 'scripted' with HTML instead of pure wikimarkup.
The main example is Template:Navbox. While this specific template does have a pupre wikimarkup equivilent (if it even is an equivilent, it's not maintained at the level of the normal one). The other templates I wish to use dont have equivilents.
Template:Navbox subgroup is the one (among others) that I wish to add in but cant because it depends on HTML Tidy. The Template itself is already on the xda wiki, but if you attempt to use it it's completely broken.
I cant say it's as simple as "install on server and turn it on" but the fact of the matter is that without it most of the fun/magic stuff on wikipedia cant be brought over to the xda wiki.
Some examples of recent stuff i've made (for reference):
Samsung Galaxy S Series Navbox
Samsung Galaxy S II Series Navbox
New Samsung Portal on Main page
Entirety of Dell devices page
If you look at the several navboxes I've made they have hacks in the code to get around the fact that I'm just a normal level editor.
Request 2: We need MOAR editors!
Also this doubles as a request for more editors on the wiki: XDA is the largest android development based site on the internet, yet here we are weeks after the release of the Galaxy Nexus and Galaxy Note and the pages didnt even exist until I made stubs for them.
As of this past quarter I've generated more edits then possibly nearly every other user combined, but there's only so much I can do at this point by my self. (With my primary style being to organize page layouts and tidying stuff up vs writing new content for devices)
[Edit count itself is a bad metric, but edits that arnt mine only number in the dozens a month]
Sure it's reasonable for minor devices and varients to be stubs, but the Note has sold over a million units and yet not a single person has even bothered to make as much as a scribble on the wiki about the device. That's just an example, but ultimately if this were wikipedia, the amount of pages rated 'good' or higher would only number in the dozens. (There's also the fact that my belief is that it's a bad idea to add anything intensive for a device you dont own, standard fare on one device can super-brick another due to quirks)
It's a rather sad state of affairs that for such a large web site with 22000 active users at any one time that there's not a single good consistant repeat editor besides me.
Edit: changed wording to not be inflammatory
Request 3: Turn on Subpages on the main namespace
Mediawiki:Subpages are by default enabled on the template and user namespaces, but not on the main namespace. I believe it's done this way because of editor policy and not technical reasons.
The xda wiki would HEAVILY benefit from having it enabled since it already currently manually uses them, the previous example of:
Samsung <Series>/<model number>/article has long existed this way but without the automatically generated anchors.
The majority of pages are already ready to accept it, it might simply need to be turned on.

XDA Wiki
TheManii said:
there's not a single good editor besides me.
Click to expand...
Click to collapse
IMHO that is a rather sweeping statement and is likely to put off anyone from editing the Wiki. I would dispute even your claim as a good editor would not make sweeping changes to categories without discussion on the pages involved. Should I just "undo" them?
XDA has a problem with repetitive questions leading to user dissatisfaction with overlong forums and the loss of good developers such as AdamG.
One solution may be to create a FAQ Wiki for any thread over a certain size (for example 1,000 posts) and automatically link to that thread at the top of every page and above the reply box.
Cheers
Tom

It is sweeping, but the fact is there arent many repeat editors, many devices havnt not seen edits in months because a great deal of the changes dones are a one-time batch job with a single theme.
I'm not at all saying that the other editors are bad, though yes that what the impression was (and perhaps I should have worded it better). I'm saying that few wish to stay with it for the long-haul.
There's few editors that consistantly return to add/update/expand artitles for their own devices or other devices. That's my main issue. I actively want to be proven wrong in this regard, I'm inviting other to prove me wrong. I myself am somewhat guilty of this myself, I primarly concentrate on the dell devices, but I've kept them very up to date for the previous year.
One example I have issue with is: Acer A500 -xda wiki the entire page are just forum links. I have no issue at all with the contents of the posts (just as much my opinion on them is irrelevent) but the fact they are just links and not part of the article. The fact it's not on the wiki means that other editors cannot make changes themselves, which rather defeats the point of the wiki, which leads to,
The other issue is, unless the OP is excellent at keeping the thread organizied, you often have to wade though the entire thread to keep up to date. With a thread with +200 posts even if you wanted to it's a huge effort to do that. Even in the most complex of topics, they can be broken down a couple bullet points and approx a paragraph each to elaborate. There's also 'bad' advise that doesnt get edited away on topics ('bad' as in it may simply be the case that it was the right thing at the moment but there was eventually a more 'correct' method discovered later and the original 'bad' one is still reposted for whatever reason)
I could copy the posts onto the wiki verbaitm, but you really should have the poster's permission, what if the poster isnt active? It would be a bad idea to paraphrase advise/guides without context, what if you remove an important small detail. The right way to be to frequent the device and get context, but that triples the amount of work to do so properly.
It's no secret that there's always users that refuse to read topics and simply skip straight to posting repeat questions. Short pages with clear instructions are much easier to recommend then having them read though dozens and dozens of posts (which they skipped as they posted without reading in the first place)
Discussions dont really work on a wiki, esp one without consistant-repeat (or even repeat) editors. There's a fair amount of edits for various devices, but there are obviously more devices then editors. Lets walk though it: I want to make an edit, do I post it on the topic's talk page? Short of doing so on wikipiedia proper on a popular change, you wont recieve much feedback.
Do you make a post on each of their device's forums? XDA has sub-forums for each device, but not really a sub-forum for the family itself (back to the SGS/SGS2, there's the main device's subforum and each varient's subforum but none for the entire family, i think) That means making dozens of posts to talk about each major change.
What if it's an old device such as the winmo devices? The HTC HD2 is the only one left on the active part of the xda forums, because it's obviously not just a winmo device now. You're going to have to wait a very long time as they naturally only get a couple posts a month now.
Just as much, unless a mod/admin states to the contrary, you can always assume Wikipedia:Be Bold is implied to apply. I honestly have no issue if my edits are reverted if they are constructive reverts, as that's how wikis work.
If anyone has a issue with the edits I make, you're welcome to discuss it with me and hopefully we'll find a middle road.
Also I've made a reply on User_talkaveShaw#Page Name & Categories (as a fun note: & is translated to _.26_ in links while / isnt, though mediawiki has no issue with either of them, though you cannot directly use & in page names while you can use /) You should read it if the critisim is directed towards me.
tl;dr prove me wrong, Be Bold, help make the wiki better
Edit: HTC_HD2 - NexusHD2 ICS CM9 FAQ is an excellent example of why things should be on the wiki as articles instead of just merely links to a thread. It's about 3 pages of topic points and contains the majority of the topic points instead of having to read 225 (currently) pages to get the same info. (Also, just as much if I inadvertently remove valid content, revert/add it back! That was not my intention, everyone makes mistakes. The xda wiki is pretty well off in that it has little/no intentional vanadalism, you can always assume an edit is in good faith, I dont recall more then 1-2 legitamitely bad edits in nearly a year)

I've asked someone to look at Request 1.
I'm not sure what can be done about Request 2, if people don't want to maintain it, we can't make then

Thanks!
I dont really expect req 2 to be fullfilled in any real manner. Just pointing it out.

Added request 3: enable subpages on main namespace

TheManii said:
Added request 3: enable subpages on main namespace
Click to expand...
Click to collapse
Our server admin has told me this has been done.
Dave

I can confirm it's on now, all the subcatagorized pages seem to be working great now

TheManii said:
I can confirm it's on now, all the subcatagorized pages seem to be working great now
Click to expand...
Click to collapse
Thanks
Dave

XDA Forum RSS Usage/Policy

Some of you have noticed that our RSS feeds have been offline for a while. We were receiving a lot of traffic/abuse from IPs clearly scraping our content, and then using this content on their own sites in order to Google-jack search terms. That, in combination with the declining popularity of RSS, made us re-evaluate the use of RSS on the forum in general.
I've enabled the RSS feed again for those users who browse XDA via RSS but with some restrictions - namely we've put a request limit on how fast you may access different RSS feeds; as well as requiring that you be logged in to get any RSS feed.
There will likely be situations that come up that require access to data in a machine-readable way - we recommend using our API at https://api.xda-developers.com/explorer/ in order to obtain this data. If you need assistance in this, please feel free to pm me directly. This is the future of programatically accessing XDA's forum content.
We may disable the RSS feed entirely in the future depending on usage statistics.

bitpushr said:
Some of you have noticed that our RSS feeds have been offline for a while. We were receiving a lot of traffic/abuse from IPs clearly scraping our content, and then using this content on their own sites in order to Google-jack search terms. That, in combination with the declining popularity of RSS, made us re-evaluate the use of RSS on the forum in general.
I've enabled the RSS feed again for those users who browse XDA via RSS but with some restrictions - namely we've put a request limit on how fast you may access different RSS feeds; as well as requiring that you be logged in to get any RSS feed.
There will likely be situations that come up that require access to data in a machine-readable way - we recommend using our API at https://api.xda-developers.com/explorer/ in order to obtain this data. If you need assistance in this, please feel free to pm me directly. This is the future of programatically accessing XDA's forum content.
We may disable the RSS feed entirely in the future depending on usage statistics.
Click to expand...
Click to collapse
Thanks for the explanation, I'm still using RSS and I haven't been able to use the old RSS feeds for the sections I want which I created some time ago (eg. https://forum.xda-developers.com/external.php?type=RSS2&forumids=524 or https://forum.xda-developers.com/external.php?type=RSS2&forumids=5340) in Feedly as I used to do last year. Is there any chance those will start working again? Right now the only one still working is the general news feed.
EDIT: reference - https://forum.xda-developers.com/general/about-xda/xda-rss-feeds-broken-t3490031

Any follow-up on this? I would also like to follow specific forum topics via RSS (currently using Newsblur).
//timo

would like to follow new quotes/messages via rss

I was almost ready to write a new thread regarding this very topic. I am also interested in RSS and I would be better informed about what's happening around here, following more threads.
Will this ever work again?
Thanks!

It would be nice if somebody posted an FAQ for this...and made it sticky. I personally feel the feeds should be enabled for a thread and not for a topic.
Just my thoughts....

does anyone know how to get rss feed for a specific device forum? so that i will know if a new thread gets created for my device?

[APP][SHARE]slr rookie

-------------------------------------------------------------------------------
PLAY STORE LINK
An app curated with the best tutorials around the web ,calculators and photography cheat-sheet,fully offline.
Bought a new DSLR Camera and want to learn the technical know-hows?Don't bother searching the web,this app comprises of a collection of some of the most trusted photography tutorials/articles written by professionals.
FULLY OFFLINE.
This app covers the basic topics to clear your doubts regarding the technical terms such as ISO,Metering,Focusing,Aperture, and many more organized in an easy-to-use UI. Besides also containing :-
>Some the advanced tutorials such as Bokeh,Portrait,Night Photography, & Sunny16.
>Online Links to other advanced topics.
>Photography Cheat-Sheet.
>Color Temperature Chart
>Hyper-focal And D.O.F.(Depth Of Field) Calculator.
>Exposure Value(E.V.) Calculator.
(The last two might be useful for experts)
In Short,all that stuff you'll need to know to start your journey as a photographer.
NOTE:I do not own any of the articles and images used in this app.Credits have been mentioned wherever possible.
I'm 18 and made this app solo during my college breaks,so if you encounter any problem or have any suggestions/feedback,please let me know.It is highly appreciated.