What we will do, is create a basic List Fragment and an RSSService class that we will use to populate the list.In our List Fragment we will simply tell our RSS service to populate the list: The first thing to note is that this class is extending Android's Async Task- The reason for this is that since Android 3.0, you are no longer able to perform network operations in the main application thread, so being as our class is going to have to fetch some RSS feeds we are going to have to spin off a new thread.Those of you who have worked with RSS in other JVM languages will know that there are plenty of libraries available that can handle parsing RSS - however, because the android platform doesn't actually contain all the core java classes, almost all of the RSS libraries have not been supported.This walk through will cover off the basics of getting an RSS reader app up and running quickly and will also cover some details of Android's fragment system for tablet optimization as well as some things to watch out for (such as changes in the platform that mean network operations cannot be run in the main thread, which requires some tweaking if you have worked on earlier versions).The widgets update only once after but cease to update subsequently. also, you may want to look into other (Task/Ram) cleaner apps such as CM Cleaner where you again may need to put these respective apps into the exceptions list.This is of course if you have this sort of app installed and running. Originally Posted by rumz82 Do you have greenify running at all?public void start Element(String uri, String local Name, String q Name, Attributes atts) public void characters(char ch, int start, int length) public void end Element(String uri, String local Name, String q Name) throws SAXException Because we only really care about capturing data from the leaf nodes, our start Element() method is left empty.The chars() element has to be watched, as there is no guarantee when it will be called (e.g.
All the code is available as a complete, working Android app that you can fork/download and fire up straight away on a compatible Android device/emulator.in a node like hello world this method might be called several times between the start and end) so every time we will just append the contents to a String Buffer - that way we can be sure that we will have captured all the data in the node.By the time the end Element() method is called, we know that we have the contents of the node itself, and we just have to store the data.Now, of course I contacted the developers of those apps first but a quick search on Google informed me that the problem seems to lie within the launcher in use. if you are, itll be a good idea to put Nova, Zooper etc all under the exceptions list.So, I tried clearing Nova Launcher's cache and restarting the launcher, but unfortunately to no avail. this will ensure that they do not hibernate therefore eliminating the possibility of the widgets not updating.