Related
We make a couple of very useful applications for rooted users, some of you may know and use them. I was wondering if anyone would be interested in adding one or two of the free versions to their ROM builds. Its seems like a win-win situation.
I use 2 Inc Ss myself and all these apps are well tested and working flawlessly, so there should be no issues.
The ones i think would fit well are Call Master:
http://forum.xda-developers.com/showthread.php?t=1291587
Its an advanced call and SMS manager (blocking, routing, private inbox, lots of other stuff). The free version has no ads and full functionality. The only restrictions are nag screens.
Screenshot ER:
http://forum.xda-developers.com/showthread.php?p=17212860
I know this may seem superfluous, but this is a proper screenshot tool with lots and lots of features. Again, theres no ads in the free version, full functionality is only restricted by a short delay.
Maybe Prepay Widget:
http://forum.xda-developers.com/showthread.php?t=1006487
A USSD balance manager with higly configurable text wisgets. Its completely free, no ads.
And finally Power Switch:
http://forum.xda-developers.com/showthread.php?t=1153788
This is something of a chimera app that does cool things like turn off the screen when you shut the case of your device. Free, no ads, only restricted by delays.
Please let me know if youre interested!
Any takers? We do make some of the coolest apps on android...
as for the power switch, does it shut the screen down upon placing the phone in your pocket? i'd like to give it a go =)
Screen off doesnt work for me on ice cold sandwich nutella
Sent from my HTC Incredible S using xda premium
Try a different sensitivity. It works fine for me.
Hey guys, random thoughts/rant for a software idea.
I was thinking of the next evolution of the Intent system on Android. I always thought OSs seemed to spend almost no effort on integrating softwares on it. It was almost like an afterthought every time. Android was a huge step in the right direction. The next step would have to be very definitive, and backwards comparable of course. It would have to be something users want, and make it easier on the developers as well.
This system would be called something along the lines of 'Sentence'. It evolves with developer and end-user choices and, if I'm right (here's the big pitch, would have the potential to make software measurably more stable, secure, efficient, and user-oriented without really changing any behavior on the developer's side. Of course it has the same potential to be stagnant, but I think the users would punish (unwittingly) developers who lagged behind or didn't put in the effort.
The sentence system allows a user to build a sentence to discover not only the correct application, but an infinitely specific task before ever encountering UI. It is reminiscent of auto-completing sentences in Google Search. An example is the quickest way of demonstrating. The [] specify user interaction and ** specify user choice (probably a button press):
I would like to
[*send*] [search] [open][...
[a][*multiple*][...
[2][*3*][4][5][CUSTOM][UNTIL...
[files][emails][smss][*pictures*][...
[*to*][GO][...
[emily][drake][*george*][...
[*and*][GO][with message][...
[emily][*drake*][george][...
[and][GO][*with message*][...
[CUSTOM][*check this out*][...
[*GO*][and]
this immediately opens the camera app for exactly 3 pictures. Once the 3rd picture is taken, the UI informs the user that the next action is about to take place. After a short time out, the 3 pictures are sent to George and Drake. After the first shot, the user can shut off the screen or pocket the device knowing the timeout will occur and then the task will continue. Being an OS-level function, the user can trust it regardless of the app.
Unless the app task fails. If Apps that use this system can't provide tasks that don't fail, they will become unpopular far quicker than the tasks that do fail that users just deal with anyway.
Furthermore, many apps can be published virtually without any UI at all, significantly cutting down on development time and allowing the dev to focus on the task and functionality.
This could turn around voice activation as well, since the user quickly understands the routine task format to get the best results, and would be more confident to provide far more complex long-winded sentences that the OS could understand perfectly to the detail.
While some sentence lines will be defined by the OS, the developers and users alike will be able to define the evolution of the sentence tree. Developers will make the smart decisions, while the users will crowd-source the popularity of each possible route. The most logical and/or common sentences would quickly be the norm. If the OS prioritizes specific routes over general ones, then developers will be incentivised to make their apps as task-specific as possible as well as as task-plentiful as possible.
The losers in this quickly become apps that use ads, apps that rely on 'convincing' the user of something with UI, and of course utility apps. Of course, this brings back the main reason for 'pro' apps: functionality. The pro version will have these features. The free version will only have these.
There wouldn't be a way to exploit the system or flood it. If the functionality doesn't work, the app becomes not only intrusive and annoying, but offensive to the user as it promised a specific task and performed something else entirely. Those apps simply wouldn't survive.
Of course, application for this kind of thing would have to be imposed by Google et all for it to exist, but there is another way. It can be implemented as a shared library that provides the necessary interfaces and cache all the necessary information for other compatible apps. That would work for a full implementation, and I can't see any features that would be missing. Backwards compatibility would still work just fine, as the app would simply fit existing intents into this sentence tree as well as it can. The sentences would simply end up being smaller. The best part is that with the right effort, this sentence tree could act as an 'Intent builder' for existing android apps. I bet I could build a handler for the tree that would get me through the above demonstration with the standard Gmail app using known intents. See where I'm going with that?
I would build it myself if I had more time, but I'm def interested in helping (or instructing) anyone who would like to take a crack at it. I think if someone got this idea into Cyanogenmod, we'd have a pretty huge win, and Cyanogenmod would have an incredibly unique UI gem to show off to stock users.
Honestly, I see no way that a system similar to this won't be built and become the standard within a decade. It would be trivially easy to build as well although some of the decisions to be made might not be so easy. So yeah, that's it. Rant over.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: This version of the app has hit its token limit, for more info on my plans and its future, check out this post: http://forum.xda-developers.com/showpost.php?p=56228193&postcount=553
Hello guys! From the creators of Sliding Messaging Pro, I would like to announce one of our new projects: Talon for Twitter!
This one, along with klinkdawg's EvolveSMS are the two brand new apps that we have been creating the past few months. They are full of polish, features, and beautiful design and KitKat style! Both of these apps are availible on the Google Play store today, but lets get to know Talon a little first
Talon for Twitter - Google Play Store
-----------------------------------------------------
Play Store Description:
Get fully immersed in your Twitter with this beautiful, feature PACKED Twitter client with a design that actually makes sense!
Created with Android 4.4 (KitKat) in mind. Includes full screen layouts, stunning animations and more! Of course that doesn't mean earlier versions of android get left out! The only thing that wasn't able to be recreated in Android 4.3 and below was the transparent navigation and status bars... Sorry! It just isn't possible
Beautiful, up-to-date layouts, designs, and neat animations isn't the only thing Talon has going for it though! The list of features is enormous as well, doing everything you could ever want from a Twitter app right off the bat. Even though it is new, I have added every single major and minor Twitter feature that I think is absolutely essential plus a ton that most people wouldn't even think of. Here is a pretty comprehensive list of its features:
Twitter features:
- Live streaming support
- Support for 2 accounts
- View your timelines (main, mentions, direct messages, links, and pictures)
- View retweets, favorites, Local and world trending, user profiles, Twitter lists, and more
- Favorite users
- Search Twitter
- Delete, favorite, retweet, quote, and reply to statuses
- view replies to statuses
- Update your profile picture, banner, location, and user description
- block, follow, and add users to lists
- search for your friends to tweet at
- Attach pictures to your tweets
- Attach locations to your tweets
- And the list goes on
Customization features:
- Extremely powerful developer theme engine (Read the second post )
- Choose between either "Talon" or "Hangouts" layouts
- Choose from 3 beautiful base themes (light, dark, and pitch black)
- Custom text sizes
- Night mode
- Auto-Refresh options
- Custom notification settings
- And many other goodies in there as well!
App Features:
- "Talon Pull" to be always listening for interactions (mentions, retweets, favorites, new followers, and direct messages)
- Expandable, actionable, and dynamic notification system
- Full app popup
- Full emoji support
- View in-line Twitter and Instagram pictures
- View in-line YouTube thumbnails
- Native YouTube player
- In-app browser
- Complete landscape and tablet modes
- Advance to new pages in a "windowed" viewing mode
- Never leave your timeline with in-line replies, favorites, and retweets
- Actionable toast bar so you always know where you are and can jump to the top
- Hiding action bar
- "Do not disturb" mode
- Widget for main timeline
- DashClock Extension
- Draft system for unsent/failed tweets
- Google style pull to refresh for quick refreshing
- Save tweet pictures
- Share content with other apps, to and from Talon
You will never go back to your old Twitter client again!
Enjoy Talon and don't hesitate to contact me with questions, requests, or bugs!
Thanks!
Contact me (Luke Klinker):
Email: [email protected]
My Twitter: @lukeklinker
Talon's Twitter: @TalonAndroid
Google+ Beta Page
Emojis
Here are two different emoji plugins for you to choose from, choose whichever suits you best, install it and never worry about it again!
Sliding Emoji Keyboard - Android
Sliding Emoji Keyboard - iOS
Permissions Explained:
- Write to Storage: Saves pictures to your SD card and writes them into the cache.
- Read from Storage: Used when backing up settings.
- Location: Used for trends and attaching locations to tweets.
- Network Communication: Obviously have to be able to interact with Twitter
- Network State: Used so the user can toggle background sync to only over WiFi.
- Run at Startup: Re-schedules the background refreshes.
- Keep Awake: Used for background refreshes and waking the screen.
- Vibrate: Used for the notifications.
Credits:
- Jacob Klinker: to many things to list! Tons of ideas, support, and inspiration
- Aaron Klinker: Icon Design
- Other open-source libraries and resources used can be found under the 'Get Help' section in settings.
-----------------------------------------------------
Screenshots:
-----------------------------------------------------
Closing Comments:
I have worked really hard to bring you guys a great experience right from the start this time and it really shows, from the login screen to the timelines, you will be fully satisfied with the design, execution and finesse that Talon brings to your phone. It isn't going to take months to get up to speed like Sliding Messaging did. I have designed this to be efficient, fast, and just work, right from the start. I learned a ton from that app and Talon goes to show just how much.
Hope you enjoy it as much as I do, sound off in the comments with question, concerns, suggestion, or whatever else you feel like saying about the app!
One more thing to say before I leave you here, please remember that this is XDA, and you are all expected to be a little bit different Android users, if you are having a force close or something, I would like you to be able to post a logcat of it. If you are wondering about why I did something the way I did, then I will probably explain it to you in a programming sense instead of how I would to a normal user on the Google+ beta page or something, because that makes much more sense to me, is easier on me, and you should be able to understand it a little bit better... Just keep that in mind and stay on topic please
Frequently Asked Questions
Frequently Asked Questions
1.) Push Notifications
I am just going to say this now, before anyone asks: Push notifications will not be coming to Talon unless something changes with the Twitter APIs. I have created "Talon Pull" with is simply an always on, listening/streaming service that will receive new tweets from Twitter whenever your Twitter handle is included. To read more about this option, look at the "Talon Pull" section below the "Reasons" section.
Reasons
This will be the more technical part of this post, if you don't want to read and understand it, then you will have to just accept my answer from above. If you don't accept that I know what I am talking about... Then by all means, read on, I will try to keep it as simple as possible.
To access Twitter, they have provided us with the REST APIs (currently version 1.1). These APIs allow developers to communicate with Twitter in real time by just submitting requests to get data from the network. They make it relatively simple - if you know what your doing - to obtain the data that they allow you to get and store, but there are plenty of limitations to these APIs, which make sense: Twitter is a completely free service and make their money off of advertisements. They want people to use their official Twitter products (such as the web or their own Android app) to access their services because they are able to place advertisements in them and that is the only way they make money. So they just aren't going to make some things available for 3rd party developers.
One of those things is their push notification system. As I said before, they allow us to access their services with these REST APIs, but they also have a Streaming API available so that a 3rd party service, such as this one, could be "always connected". Sounds great right? Maybe, maybe not. More testing probably needs to go into it, because it is very new in Talon. For the past few weeks though, I can say that it doesn't seem to take up much more battery than sycning on an intervol does. So try it and let me know. I have done the best I can to optimize this service, but if you want to know more about it, read below in the "Talon Pull" section
What these streaming APIs should be used for is a server side interaction that would then connect to GCM (Google Cloud Messaging) and send push notifications from there. I would love to say I am working on something like this, but it isn't possible for a developer like me. I don't have the time, resources, or knowledge to set up a complex server like this. The knowledge I could get, but I am a 20 year old kid, working off of this 1 MB/sec internet connection while being a full time college student at the University of Iowa. I wouldn't be able to handle the upkeep of the system like this or the traffic. I just don't have the backend necessary for this type of thing, and there aren't many developers who do. So push notifications from the server side? Way out of the question.
That leaves only one thing to do: wait. Maybe Twitter will open up some kind of push notification service to it's developers, but I wouldn't count on that. The ideal thing for them to do would be to set up their own GCM server for us to communicate with, but I don't see that as being likely at all because of the advertising. That would take away one of the main draws for their app, leaving it with almost nothing that 3rd party developers can't do. For now though, "Talon Pull" seems to be working well and I would encourage you all to try it out. Battery seems to be fine, the one drawback is that you must be connected to a datasource right when the interaction happens or it won't be saved or shown.
Talon Pull - My solution/workaround
As I said before, this is NOT push notifications. Push notifications are sent to your device to notify you from some kind of server. They aren't always on, and only turn on when your device receives the info from the web service.
Talon Pull on the other hand, uses Twitter's Streaming API to just create an "always on" service to be constantly listening for and streaming tweets that contain your Twitter Handle. The way this works is that you are signed in with your API keys after you turn on the option to enable Talon Pull. I then just create this "listener" that Twitter's servers will send new tweets to. Luckily, they will take care of most of the filtering of those tweets on their end, to reduce the load as much as possible on your device (because before the filtering, it literally will receive every single public tweet that is happening. It was amazing when I first flipped and saw the tweets flowing over my log haha). So we filter it down to as few of tweets actually reaching your device as possible, then I start broadcasting the notifications when you receive the new ones.
Overall, it is a relatively simple process, the problem with it though, you have probably already realized, you have to be constantly connected with a data service or the app won't know when to receive the new tweets. Obviously that is the part that is going to end up taking the battery (if it does), not "bloated" or "un-optimized" code as some of you I sure believed. So far though, through my testing, it doesn't seem to have a very big impact on battery overall, but I suppose that it potentially could if you are using Twitter that much more than I do.
If there was a better way, I wish I could find it. I think that this is the method that most 3rd party services use to send you those fake "push notifications". So there ya have it, hope you learned something. It works well and it is the only way to get a lot of information like who favorited or retweeted your statuses
Conclusion
Thanks for the read, if you made it all the way, hope that gives you an idea as to why push notifications just aren't even an option at this point and what my solution to that problem has been, even if it is not ideal. It works, and it seems to be working quite well for me.
So just know: "Talon Pull" isn't quite the same as push notifications, but it is as close as you are going to get and is working better for me than I would have ever imagined. Enjoy!
2.) Translucency
Why aren’t my status bar and navigation bar translucent like in all of the screenshots?!?
This is an Android 4.4 KitKat feature only. Get a new phone/ROM if you want it.
3.) Theming Support and Limitations
We have created a pretty powerful theme engine for Talon and EvolveSMS this time around, but it isn't without its limitations.
The main app color will always be orange. Don't ask to change it. That isn't something I can theme dynamically or read from an add on package, themers can change the orange glow on the in-line buttons (favorite, retweet, and send), but that is as much as your are going to get with that one.
4.) Viewing users who "retweet" and "favorite" your statuses
This is another thing that isn't going to happen at this point. It isn't possible to get the user ID's or their names with the current version of the API's.
Maybe Twitter will open this up in the future, but I wouldn't get your hopes up.For now, the best you will get is the numbers on them
The only way to get this information is through the use of "Talon Pull" and the Streaming API's. When you get a retweet or favorite, it will be put in the interactions drawer on the right side of any activities with drawers.The only way to get this information is through the use of "Talon Pull" and the Streaming API's. When you get a retweet or favorite, it will be put in the interactions drawer on the right side of any activities with drawers.
5.) Clearing the Cache
If you know much about caching in Android, then you may wonder why in the world I would want to clear it every time you switch themes.
The answer is pretty simple: to vastly improve the performance and the smooth scrolling in the app, I save the profile pictures according to the current theme's style, whether that is circle (like the "Talon" layout) or square (like the "Hangouts" layout). This preference is also available to themers in the add-on themes.
By caching them directly as circles, it alleviates the need to do it on the fly which could consume quite a bit of processing power on older phones and would just be a complete waste to render them like that every time.
You may think it is a hassle, but you would be thanking me if you knew the difference it makes.
You can also view the current cache size and clear it manually from "Advanced Settings".
6.) Battery Consumption
If you use Talon a lot throughout the day, it is going to take up battery, simple as that. I find that on a 30 min refresh intervol for the different timelines and manually going in and browsing/updating throughout the day, it takes about 4-5% of my battery. I would say this is pretty normal because there are days that Google+ takes up to 10% with just casual browsing.
If that isn't acceptable for you though, then there are a few things you can do to reduce battery consumption:
1.) Turn down the refresh interval on the timelines. This is the big one. It is those background services that are going to drain your battery.
2.) Turn off "Refresh on Startup".
3.) Turn off "Talon Pull" and "Live Streaming"
4.) Don't have it sync the second account's mentions
And if all else fails... Get off Twitter and do something productive for awhile =D haha any app that accesses the internet and refreshes as much as a Twitter client is inherently going to use more battery in the background. There are ways to reduce it, but not always ways around it!
7.) Custom ROMs Immersive Mode
My custom ROM has "Immersive Mode" and Talon doesn't seem to play nice with it! What's up with that?!
The way that immersive mode works in your ROMs currently isn't so hot unfortunately. There is a reason Google didn't put it into the whole system because app developers would have problems implementing the "translucency" with conflicting system stuff.
Not to fret to much though, I was able to get things working smoothly with it in Talon. The problem was that my ListView's are expanded through the different system bars. This can be a big problem if you try to switch to "Immersive" in the middle of doing something in the app. You will notice the margins get all wanky on the top and the bottom of your lists.
It can be easily solve though by just restarting the app by swiping it out of your recent apps screen. Sorry, but that is the best I am going to be able to do here, Translucent bars an "Immersive Mode" just weren't meant to work together.
Theming in Talon
Theming in Talon for Twitter
Real quick, before you get to far into the content, I want to let all you developers know about one of, if not the standout feature of Talon and EvolveSMS: one incredibly powerful theme engine.
Along with these apps, me and Jacob have completely redesigned and rethought our old "Theme Engine" from Sliding Messaging! Although the Sliding Messaging one was cool and great for the average user to customize, it was slow, cluttered, limited, and just bad design from a developer perspective. This won't be an issue with these apps though. We remade everything about it to bring you the ultimate themeing and customization experience, without the bloat and slowdowns. You won't be disappointed when you see what it can do!
All this theme engine takes is a little bit of knowledge about layouts and resources in Android, along with the Android SDK to compile and distribute your package as an APK, then you can make both of these apps into literally ANYTHING you want. We are able to read the layouts, drawables, and some of the colors directly from your compiled package and place them in our apps! Sweet huh, you thought this kind of design your own thing was only for homescreens
And the best part: it is completely free and you can easily share these themes with anyone when you are done by just sending the APK or putting it on the Google Play Store!
For more info on these and to start making Talon really your own, check out these links:
1.) Talon Theming Example/Walkthrough on GitHub
2.) Google+ Community Theming Section - A great place to share so anyone can see and use your themes, not just XDA users
3.) Google+ Theming Post
gonna try it out soon
Amazing Twitter app, absolutely loving it so far. It is just stunning, and kudos to going with transparent navbar instead of immersive, it looks fantastic and doesn't require a gesutre to get to.
Yeah, I completely agree that transparent is the way to go over immersive on something like this, it takes more work, but definitely with it!
Why do you only support for 2 accounts? It's just a question!
Pac-Man said:
Why do you only support for 2 accounts? It's just a question!
Click to expand...
Click to collapse
Well, a little embarrassing, but because the logic behind coding more than that gets way complex... haha
klinkdawg24 said:
Well, a little embarrassing, but because the logic behind coding more than that gets way complex... haha
Click to expand...
Click to collapse
Don't worry! But I hope you'll add multiaccount. There're a lot of people that love it
Anyway it's a good app with a perfect design. My sincerelly congratulations!
Enviado desde mi Nexus 4 mediante Tapatalk
Will love to try it, I paid for falcon and then it got free
Hoping for xda version
Maybe I'm just stupid.. How do you pull up replies to others tweets? Beautiful app btw... Love it...
wow this app looks beautiful, would love to try it, unfortunately, i dont have a credit card and can't purchase from google play. Will there be a free or xda version coming soon? if not is there any way for me to try this out? signed up for the beta as well
I got the app a couple of hours ago and it's amazing.
Just a few things..
Where did the Talon Pull notifications go when they are received? I have to manually to update the timeline anyway.
You have to pull down for too long in order to update. You should adjust it
You should definitely implement threaded DMs, that would be pretty cool
Great app btw,
donwhall70 said:
Maybe I'm just stupid.. How do you pull up replies to others tweets? Beautiful app btw... Love it...
Click to expand...
Click to collapse
right now, you can only look backwards at tweets, looking forward will come when i figure it out haha
alkspo said:
wow this app looks beautiful, would love to try it, unfortunately, i dont have a credit card and can't purchase from google play. Will there be a free or xda version coming soon? if not is there any way for me to try this out? signed up for the beta as well
Click to expand...
Click to collapse
No, because of the token limit, this app is going to be paid, I thought about an XDA version with different tokens, but that would just go against Twitters rules still
Kage0x said:
I got the app a couple of hours ago and it's amazing.
Just a few things..
Where did the Talon Pull notifications go when they are received? I have to manually to update the timeline anyway.
You have to pull down for too long in order to update. You should adjust it
You should definitely implement threaded DMs, that would be pretty cool
Great app btw,
Click to expand...
Click to collapse
1.) They go to the interactions drawer on the right, make sure you are on the newest version and it will work better (1.01)
2.) i changed it for the version im releasing now
3.) yeah the dm's have a lot of work i know!
Version 1.05
(up in ~2 hours)
Well, day one is coming to a close and i have added some nice stuff for all of you
There was an update earlier that solved some issues with the Talon Pull service not working and tweets being saved twice in some places. That was version 1.01.
Changelog for 1.05:
Correctly mute retweets
- Higher quality images on timeline
- Dismiss all on interactions drawer
- In-app browser is now optional
- Lowered swipe length for Pull to Refresh
- Option to display both screenname and name on timeline tweets
- Open app from clicking icon on widget
- Finished German translation
- Fixed contact images on layout change
- Attempted fixes for Play Store crash reports
I hopefully got the force closes that were reported today taken care of. Although there weren't many, which makes me happy
Let me know how this version works for all of you!
hi mate
the last update is wonderful
it fix almost every complain ppl have.... BUT.....
PLEASE and i repeat PLEASE don't use the same way of plume to manage DM
the DM must be in threaded conversations, with the ability to delete entire threads, just like a normal "sms" application does, and just like tweetbot does.
please fix the dm section and this could be the real deal for android users.
faremoney said:
hi mate
the last update is wonderful
it fix almost every complain ppl have.... BUT.....
PLEASE and i repeat PLEASE don't use the same way of plume to manage DM
the DM must be in threaded conversations, with the ability to delete entire threads, just like a normal "sms" application does, and just like tweetbot does.
please fix the dm section and this could be the real deal for android users.
Click to expand...
Click to collapse
DMs will get a big rewrite, but I have a few other things I need to do first
klinkdawg24 said:
DMs will get a big rewrite, but I have a few other things I need to do first
Click to expand...
Click to collapse
Very nice app. I only have two "issues" Local Trends is displaying trendings from another country. The same happened to me with Falcon Pro so, I guess you both use same location service. It would be nice to have an option to select trends manually for people who is living in another country and wanna know what is happenning in their "home"
The other issue I found is that I think data loading is faster in other Twitter clients especially with timeline refresh
OK, this gets better and better.
The pull to refresh is better than before, but it still needs some improvement. Take a look at how the one from the gmail app behaves. That one is perfect. But this is just a minor issue, so it's not a big deal
Regarding the DM issue, could you at least change the order in which they are displayed, or at least give us the opportunity to do so? It's kinda weird to have the old ones first. But it really depends on long will it take to rewrite the whole thing, if you're going to do it
Also, I really think mentions notifications from the Talon Pull should go directly into the mentions tab instead of the additional drawer, but maybe that's just me
awesome. perhaps the only competitor falсon. you can do that display images if given a direct link to it? (everywhere)
view who retweet/favorite. display real-time, I mean like 20:14, but not 14 minutes ago. thx, man.
Reposting from where I previously put this, on the suggestion that folks here might have more idea what I am talking about.
Yes, this is a question but I couldn't see that it fit in better to one of the other forums. If I am wrong please accept my apologies and redirect me, thanks.
I'm trying to work with a custom build of Android based on KitKat to incorporate a stylus, copying some of the functionality (though not code) from Samsung which sells Android-with-stylus builds for e.g. the Note 3. I'm not including details of the specific device because right now I am working on a custom dev device and my aim is to write code which is generic enough to be usable from any Android (based on KitKat). The build (written by others) already incorporates drivers and sends stylus events correctly as motion events etc. Programming at the app level I can receive onHover, onTouch, onClick etc
The specific functionality I am trying to achieve is to pick up a stylus-button-click while hovering. It's perfectly possible to do this in any app, using an onGenericMotion Listener.
However, I want to make my "stylus-action" have system-wide effect - so that anywhere (in any other app, or in the launcher or whatever) I will pick up the event (prior to any other app) and bring up my custom menu. (just like AirCommand in Samsung Note 3) I guess in my custom Android this would then make that particular action somewhat protected or unusable for other users, but I'm ok with that.
In older Android (prior to ICS) you could try something by putting up a System Overlay (i.e in regular app code, without hacking the ROM at all), but this is no longer possible.
This is not an attempt to tapjack or whatever, I understand why this functionality has been removed from the domain of the regular programmer, and I don't want to regress my ROM back to pre-ICS behaviour by allowing the System Overlay hack. Now I am programming the system (if my change is good enough I'd like to submit it back to AOSP) so I would like to know the best method to address this. Since Samsung have already done this, it must be legal (using legal in the terms of "Android will allow it"), and I want to do it right.
Is it possible to write something similar to the System Overlay when you are running from a system service? Or is there a good choke-point to capture events before they are broadcast to the current running apps?
I was looking at (sorry, not allowed to post links) AndroidXRef /frameworks/base/core/java/android/view/View.java specifically in the function dispatchHoverEvent() which looks like a promising place. My naive idea is that I would place code here checking the MotionEvent to see if the button is pressed and if it is, don't call any listeners and instead call my little menu app (or broadcast a custom message, or something anyway). However, I've never written code on the ROM level before (LOTS of experience writing app code) so I don't know if this is a really bad point or a good point to add in code. Should I be putting things at a higher level or a lower one? Will this capture all events or not? Is it all just trial and error?
If this is the wrong place to ask questions like this, please tell me where on XDA I should be asking it. If it's the right place - please answer
Thanks
Kibi
Maybe some things are a lil bit old but everytime gold,lol.
Work in progress.......
------
What is a kernel?
If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
-----
What is a Nandroid backup?
If you've read about hacking or rooting your Android phone (or tablet, or media player) you've seen the word Nandroid used. When tinkering with your device, there's always a very good chance you'll be left with firmware that won't boot, leaving you in a bit of a lurch. A Nandroid backup can mean the all the difference here.
What it is, is a full backup of partitions on your device's NAND flash (NAND stands for NOT AND, a type of electronic logic gate -- it's like the hard drive of your Android device) storage. Think of it as a snapshot of the current running system, and it can be used to restore that that point at any time. Both user data and system files are backed up, and it's a far cry from what we think of when talking about a traditional backup from other software. In fact, it's something that many folks wish was part of the stock Android recovery. Yes, to preform a Nandroid backup you'll need a custom recovery on your device so that the executable files and scripts are there. These have been left out of the stock recovery, likely over issues that would arise if users can backup proprietary files.
Getting the custom recovery on your device is the hardest part, thankfully. Once installed backing up and restoring with Nandroid is simple, involving nothing more than choosing the option and verifying -- no wires needed. Even if you never plan to hack your phone, flashing a custom recovery and running a Nandroid backup is always a good idea. You can find more information about custom recoveries, as well as methods to install and use them, in the device-specific section for your device in the Android Central forums. Give it a look, and decide if it's something you're interested in doing.
-------
What is an IMEI?
The IMEI (International Mobile Equipment Identity) number is a unique set of 15 digits used on GSM phones to identify them. Because the SIM card is associated with the user and can be swapped from phone to phone, a method is needed to keep track of the hardware itself, and that's why the IMEI was developed. Math nerds will enjoy the way they are calculated -- the first 14 digits are decided by the GSM association, and the final check digit is computed using what's called the Luhn Formula -- crazy base-8 math that mere mortals like most of us don't understand, nor want to understand. You can see the IMEI of your Android phone by looking in settings > About phone if you're curious. (Or on the box if you still have it. Or under the battery or on the phone itself.
What is this number used for? That's the real question, isn't it. Like the MEID number on CDMA phones (think Sprint and Verizon), the IMEI is used for network control. It's not very common, but your mobile operator can block a phone based on it's IMEI in cases where it's been reported stolen or someone didn't pay the bill. Because it's not easy to change the IMEI of your phone (and maybe even illegal -- check your local laws) it's also used to keep track of phones that were involved in criminal activity, and the UK in particular has a handy database of phones used for these purposes. The IMEI number is also used to specify a phone for wiretapping by federal governments worldwide.
On a lighter note, Android apps can also use your IMEI number. The app will declare that it has access to your personal information, and the IMEI can be used to keep track of the device in a remote database. This sounds pretty scary, but it's an easy way (though not necessarily the best way) for app developers to keep a settings database online for your phone, in their app. Let's say you mark a bunch of favorites in a wallpaper app. Those favorites are kept in a small database file online, and when you reconnect to the app it reads your IMEI number to find your preferences. Not an ideal method, but it's easy.
One last thing -- now that we know a little more about IMEI numbers, they will soon be changing to IMEISV numbers. The use-case scenarios are the same, but the data structure and method of calculation is different. An IMEISV gets rid of the check digit (and its complicated Luhn formulated calculation) in favor of two digits used for software version numbering. Like everything else in the mobile space, network identification changes rapidly.
-------
What is a bootloader?
What is a bootloader? At its most basic level, your Android smartphone is like a hard drive, made of up several partitions. One of those partitions holds the Android system files, another holds all the app data you accumulate (which is how you're usually able to update without losing all your stuff), and others to do more behind-the scenes stuff.
Think of the bootloader as a security checkpoint for all those partitions. Because if you're able to swap out what's on those partitions, you're able to break things if you don't know what you're doing. Or, with a little hackery, you're able to run custom ROMs.
There's a lot of squawking about bootloaders being "locked." Actually, most phones shipped with a "locked" bootloader, including the developer-friendly Nexus devices. (Nexus devices and a couple tablets are easily unlocked with a single command.) No, more accurately, most bootloaders are locked and encrypted, meaning the traditional "fastboot oem unlock" command won't do a thing.
And that's a bone of contention for those who love a manufacturer's hardware and want to tinker with their devices. HTC and Samsung and Motorola -- just about everyone, really -- ships devices with locked and/or encrypted bootloaders. Tinkerers (we really don't like calling 'em "hackers") have to find a way around the encryption, usually with some sort of an engineering bootloader that wasn't supposed to be available to the general public. But in recent months, we've seen HTC provide a free tool that will unlock the bootloaders on a number of its devices, and ASUS just got on board, too. Sony Ericsson recently has provided unlocking tools. Motorola's promised to do so as well, but there's been little movement. LG and Samsung ship with unencrypted bootloaders.
Why keep a bootloader out of reach? Probably the biggest reasons are that the carriers and manufacturers don't want to have to support hacked phones. The other is that a lot of time and money is spent developing these things. HTC Sense ain't cheap. Neither is TouchWiz. But Samsung and HTC both have managed to find a middle ground with the modding community, and pressure is on other companies to do so as well.
-------
What is Dalvik?
What is Dalvik? We hear that word getting thrown around a lot on the Internet when talking about Android and its inner workings. While there's no easy explanation we can give in just a few paragraphs, we can cover the basics and point you in the right direction if you need to feed your nerdly side. In its simplest terms, Dalvik is a virtual machine that runs applications and code written in Java. A standard Java compiler turns source code (written as text files) into Bytecode, then compiled into a .dex file that the Dalvik VM can read and use. In essence, class files are converted into .dex files (much like a jar file if one were using the standard Java VM) and then read and executed by the Dalvik Virtual Machine. Duplicate data used in class files is included only once in the .dex output, which saves space and uses less overhead. The executable files can be modified again when you install an application to make things even more optimized for mobile. Things like byte order swapping and linking data structure and function libraries inline make the files smaller and run better on our devices. The Dalvik VM was written from square one with Android in mind.
Confused yet? Don't feel bad, geeky programming talk usually has that effect. Think of it this way -- when you build a Java application for your computer, a Java Virtual Machine runs the compiled output of the source code. This is why Java runs on just about any operating system. Dalvik is a mobile-optimized version of a Java Virtual Machine, built with code from the Apache Harmony project, which is open-source and runs better than a standard Java VM would on our limited hardware, designed so that you can run more than one instance of the VM at a time -- ie multitasking. Because Dalvik is open-source, it's also been ported to other operating systems, like the one on the BlackBerry PlayBook. It's pretty damn complicated, pretty damn cool, and Oracle (the company that bought Java from Sun) hates it.
Android uses Dalvik because while the license for the standard Java Virtual Machine is GPL2 (free and open-source), when placed in a mobile device and using the Java Micro Edition, it is not. The big dispute between Google and Oracle is all based around Dalvik. Google claims it was written in a "clean-room" environment without using any of Oracle's code, and Oracle disagrees. We claim to have no idea, we're just glad it works as well as it does.
For more on Dalvik, see the Google I/O website.
--------
LG's L-series
They made a big splash earlier this year at Mobile World Congress, and a few carriers in Canada jumped at the chance to sell them, but then they seem to have fallen off the map. I'll admit, even I have to look and see what we're talking about when we have potential news about the L3, L5, or L7. Let's have a refresh.
Imagine LG's Prada phone, but remade for folks who don't buy Prada. The L-series phones are all stylish (and really resemble LG's iconic Prada phones -- check out our look at them in Barcelona) and have an emphasis on good looks. The entry-level L3 competes with phones like HTC's One V and Samsung's entry-level Galaxy phones. It's running Gingerbread on a 3.2-inch display, but it looks nice doing it. Compared to something like the Motorola Defy Mini, you get good looks along with your dirt-cheap pricing. The L5 takes things up a notch to Ice Cream Sandwich and a 4-inch screen, placing it in the middle of the road where most people look first when buying a new smartphone. They'll see the L5, and notice the build materials and design. Finally, the L7 looks to compete with the big dogs of the Android world, with all the bells and whistles you would expect from a high-end smartphone, in a damn fine looking external shell. All three are eye-grabbing, and getting people to notice is the first hurdle. We're really not sure why we don't hear more and see more about them, but we're guessing a saturated market has something to do with it.
Maybe we'll see the L-series phones make their way into the spotlight, maybe we won't. But at least now we all know what we're talking about when we see them mentioned.
-----------
Multitasking
Multitasking is a word you'll hear a lot around here and at other places on the Internet that talk about smartphones or other tech. It doesn't mean what it used to, back when dinosaurs with long beards first dreamed up computers, but it still makes a very big difference for some folks and can be the deciding factor when picking a smartphone operating system. Let's have a look and see what the fuss is all about, and how it relates to Android.
A long time ago, in a laboratory far, far away, some Jedi masters decided that computers should do more than one thing at a time. They really already were doing plenty of things behind the scenes, but to the user it was a case of entering a command, and waiting for it to finish. Using threads and schedulers, and probably a little magic and a lot of luck, engineers were able to work up an operating system that could run more than one user command at a time, and multitasking was born. When you switch to a new VT (virtual terminal) on a Unix box with no GUI, you're multitasking. When you have more than one window open on your Windows or Mac or other computer that does have a GUI, you're multitasking. You're doing more than one thing at a time, and the computer is running more than one user task at a time. You can now read Android Central while your completely legal torrents are downloading in the background.
On a smartphone, multitasking is a bit different. We don't have the luxury of a 20-inch monitor, so showing more than one "thing" running at a time isn't a big deal. Samsung is testing the waters and trying it with the Galaxy S III with the Pop-Up Play feature, but for the most part whatever we're doing takes the whole screen to do it. We also don't have tons of RAM and video memory available and have to watch the power usage. This means smartphone multitasking has to be a bit, well, smarter.
Smartphones have been multitasking for a long time. All the mobile operating systems do it a bit differently -- some suspending all other apps in the background, some saving the state and closing the app itself, and others just letting everything run. The way Android does it is to let threads and processes run depending on their priority. If you're using Google Play Music, the processes that make the sound come out of the speaker have a high enough priority to stay running when you switch away from the app. Not all of it is running in the background, but enough of it is to keep the tunes playing. Other apps can be killed if they aren't being used, and some apps get "frozen" (for lack of a better word) and restore themselves when brought back to the foreground. What's important, and prioritized, is decided when the application is written and compiled so the end user doesn't have to worry about it. It's not perfect, but it follows the very strong multitasking model from Linux and tweaks it for Android. It's all open-source, so manufacturers and ROM builders can (and have) tweaked things to allocate memory the way they want it allocated. Sometimes the tweaks are great, sometimes not so much.
In the end, remember the next time you open an app and start up where you left off that you're seeing multitasking at work.
----------
Haptic feedback
It's one of those little things that can make a big difference, and something we never really think about. Simply put, haptic feedback (commonly referred to as haptics) is the use of touch feedback to the end user. You know how your Android phone vibrates a tiny bit when you tap one of the navigation buttons? That's haptics at work.
Since the screen on your Android phone or tablet is pretty much just a smooth sheet of glass of some sort or another, it's difficult to register any sort of tactile feedback to our fingers. When we type on a computer keyboard, we know when our fingers have pressed a key down. Our mouse (and some trackpads) do the same thing with a healthy click when we press the button. On a smartphone, we just have to trust we've done something, and wait for it to happen. Haptics helps here. The short and light vibration when typing out a message with an on-screen keyboard can make a big difference for many of us, and I can see myself being pretty frustrated if an on-screen button didn't let me know I had pressed it.
Haptics go beyond navigation and the keyboard though. They can be a very important part of mobile gaming. Gunning your way through an enemy horde is much more satisfying when you feel every shot from your rifle, and nothing lets you know you've hit the wall in your favorite racing game like a harsh vibration from your phone or tablet.
Probably the best thing about haptic feedback on Android devices is the way it can be customized. The OS itself is open, meaning OEM and developers can adjust things to get them just the way they like, including leaving the settings wide open to the user like we see in CyanogenMod ROMs. More importantly, application developers have access to the hardware controller to customize haptic feedback for their products. It goes one step further with the addition of things like the Immersion haptic SDK to the mix, where developers have an almost unlimited way to make their applications register with your fingers as well as your eyes and ears. Sometimes, the little things mean a lot.
--------
F is for Factory Reset
A factory reset is the ultimate cleansing of your Android device. It's usually either a last resort to fix a problem, done before you sell it, or because you like to flash ROMs. When you perform a factory reset you're essentially wiping out everything you've ever done to the phone and restoring it back to the basic manufacturer software. As we've mentioned before, it doesn't uninstall any software updates you've received from the folks who made your phone, but it does wipe out any core application updates you've grabbed from the Google Play store. The technical details are as follows:
/system is untouched, because it's normally read-only
/data is erased
/cache is erased
/sdcard is untouched
When your phone or tablet reboots, it's like it was when you opened the box as far as apps and user data goes, except for your data on the SD card partition (either a real, physical microSD card or a partition named sdcard).
Doing a factory reset is easy -- open the settings, do a little digging (different manufacturers put it in different places, but start with privacy or storage), select it and confirm. Your device will reboot into the recovery partition, erase everything, they reboot into the setup again. One thing to note though -- if you've rooted and ROM'd in any way, you should never do a factory reset from settings. Often times it works just fine, but some devices and some ROMs are so different once hacked that you'll end up with a bricked phone. We hate bricked phones around these parts. Follow the instructions from the folks who developed the software you're running instead, and use the reset method they recommend.
-------
End of life
End of life is a term none of us ever want to hear. We envision it means the death of our phone, and we should just throw it away and get a newer model. After all, it's at the end of its life, right? Not really. End of life means something different to carriers and manufacturers than it does to enthusiasts like us. The easy way to look at it is that when the folks in suits get together and decide that a phone isn't going to make enough money so it's worthwhile to keep producing it, it has reached the end of its life. That may mean a refreshed, newer model (like the Droid RAZR MAXX), or a shift to a newer model with new, and arguably better, features like the EVO 3D. We have to remember that the folks who make these phones do it so they can make money, and like any good business they want to maximize their profits.
But what does end of life mean in the real world? First off, it means that once the current stock sitting on the shelves is sold there won't be any more new ones to replace them with. There may be refurbished units floating around, but no more new phones of that model are being made. It doesn't mean that the phone is done getting updates, but don't expect too many new features to come along -- things are in maintenance mode and bug fixes and security patches are the only things that will be addressed. It also doesn't mean your warranty is affected in any way. Even if you were to buy a brand new phone that has already reached the end of life status, you'll still get the full manufacturers warranty.
Most importantly, it doesn't mean that the phone is going to stop doing anything it already does today. The HTC EVO 4G is a great example. It was a huge hit for HTC and Sprint, and actually stayed in production longer than any of us would have thought. Some places are still selling them new (although they're getting harder to find), and those EVO 4G's sold new today are every bit as good, and have the same warranty from HTC, as the ones sold in 2010. Sprint still offers customer service, and it's still one heck of a phone.
Don't be put off by the words end of life. While we wouldn't recommend you search out a new phone that's already been discontinued, they still perform as they should and you'll find lots of folks who still love them.
----------
DLNA
DLNA, or the Digital Living Network Alliance is an organization set up by Sony in 2003 that determines a universal set of rules and guidelines so devices can share digital media. The devices covered include computers, cameras, televisions, network storage devices, and of course cell phones. The guidelines are built from existing standards, but manufacturers have to pay to use them and have their device join the DLNA.
With DLNA devices, you can share video, music and pictures from a Digital Media Server (DMS) to your Android phone or tablet. A DMS could be your computer, a NAS (Network Attached Storage) device, a television or Blu-ray player, or even another Android device. Anything that has a DLNA server, or can have one installed will act as a DMS. Fun factoid: when a DLNA server is installed on a cell phone, tablet, or portable music player it's called a M-DMS -- the M stands for Mobile.
Once a DLNA server is in place, our Android phones usually have two functions -- to act as a Digital Media Player (M-DMP) or a Digital Media Controller (M-DMC). The player is easy enough to figure out, it finds content on a DLNA server and plays it back. A DMC will find content on a DLNA server, and push it to another connected player. For example, my television has a DLNA player, and my laptop has a server. With the right software, I could use my Android phone to find the content on my laptop and play it on my television. DLNA can really be fun if you have all the right equipment.
But chances are Android (and eventually other mobile devices) will be moving away from DLNA. With Ice Cream Sandwich, Wifi Direct is part of the operating system and has the potential to do everything DLNA can do, and more. We already have seen it replace DLNA streaming in the HTC One series with the Media Link HD receiver, which streams content from a Sense 4 device to a monitor with HDMI input. It uses native Wifi Direct, and by all accounts works really nicely. Or Samsung, who is using NFC to kick off a Wifi Direct session for fast data transfer on the Galaxy S III. We'll have to wait and see what manufacturers do with Wifi Direct, because having it built into the OS is a big plus -- even for a company like Samsung who makes millions of DLNA devices each year.
---------
Bloatware
When you think of Android phones, you think of bloatware. We wish it weren't so, and not every phone comes with, but the majority of Android phones out there come from carriers and are chock full of bloatware. We've complained about it, and found ways to remove it, but what exactly is it?
Most folks consider any applications that your carrier (or the folks who built your phone) pre-installed to the system as bloatware. Usually, these applications are a front end to some service or content that you'll have to pay for, and usually it's something you would never download and use on your own. All the carriers, and all the manufacturers, are guilty of including it, and we tend to hate it all equally. When you open the app drawer on your new phone, and see City ID staring back at you, just waiting for you to click it, you can't help but hate it.
But why is it there? It's one down side of Android's open nature. Google gives Android away to anyone and everyone, but realistically only a very few companies can afford to make cell phones. And they don't make them with you and me in mind as their customer. HTC, or Samsung, or LG (you get the picture) makes Android phones for the carriers. They work out deals to decide hardware and software they want to include, and part of those deals are these "value-added applications" we lovingly call bloatware. Verizon and HTC love you, but they still want you to click the app and send in the money. Because Google isn't involved and doesn't make any rules about it, they can include any app they like in your new phone. Nobody likes it, but it is the side effect of being open.
Thankfully, Ice Cream Sandwich brings along the ability to disable (most of) these apps without rooting or tinkering with the system files on your Android device, and that provides the best solution we can think of. Certainly there are some people who found a use for City ID or VZ Navigator, and they should have the opportunity to use those apps if they like. And we can disable and hide them, and forget they exist.
What is the AOSP?
AOSP is a term you'll see used a lot -- here, as well as at other Android-centric sites on the Internet. I'll admit I'm guilty of using it and just expecting everyone to know what I'm talking about, and I shouldn't. To rectify that, at least a little bit, I'll try to explain what the AOSP is now so we're all on the same page.
For some of us -- the nerdly types who build software -- the full name tells us what we need to know. AOSP stands for Android Open Source Project. The AOSP was designed and written by folks who had a vision that the world needed an open-source platform that exists for developers to easily build mobile applications. It wasn't designed to beat any other platform in market share, or to fight for user freedom from tyrannical CEOs -- it exists as a delivery mechanism for mobile apps -- like Google's mobile apps, or any of the 400,000+ in the Google Play store. Luckily, Google realized that using open-source software would ensure that this operating system/mobile application content delivery system is available for all, for free. And by choosing the licensing they did, it's also attractive to device manufacturers who can use it as a base to build their own mobile OS.
The premise plays out rather nicely. Google writes and maintains a tree of all the Android source code -- the AOSP. It's made available for everyone (you, me, manufacturers you've never heard of and not just big players like Samsung or HTC) to download, modify, and take ownership of. This means the folks at CyanogenMod can add cool stuff like audio profiles. It also means folks like HTC can change multitasking in ways that many of us don't like. You can't have one without having the other. The big players then use their modified version of this source to build their own operating system. Some, like Amazon, radically changed everything without a care to use Google's official applications and keep their device in compliance with Android guidelines. Some, like HTC radically changed everything yet followed the Android Compatibility Program (ACP) so they could include Google's core application suite -- including the Google Play store. Some, like the folks at CyanogenMod, enhance the pure AOSP code with additions but don't change the overall look and feel. Again -- that's how this open-source thing works. You can't have it without allowing folks to change it as they see fit, for better or worse.
Any of us can download and build the AOSP. We can even stay compliant with the ACP and contact Google about including their applications. Yes, any of us could build our own device using the AOSP code in our garage or basement with Google's full blessing. That's the beauty of the AOSP, and we wouldn't want it any other way.
--------
What is a widget?
What is a widget? In Android, the word widget is a generic term for a bit of self-contained code that displays a program, or a piece of a program, that is also (usually) a shortcut to a larger application. We see them every day on web pages, on our computer desktop and on our smartphones, but we never give too much thought into how great they are. Widgets first appeared in Android in version 1.5, and really gained traction thanks to HTC's Sense-flavored version of the operating system. Prior to the release of the HTC Hero and our first taste of Sense, widgets were functional, but pretty bland in appearance. Since then, OEMs and independent developers alike have done some marvelous things with widgets, and it's hard to imagine using Android without them.
Android widgets come in all shapes and sizes and range from the utilitarian 1-by-1 shortcut style to full-page widgets that blow us away with the eye-candy. Both types are very useful, and it's pretty common to see a widget or two on the home screen of any Android phone. A full-page widget, like HTC's weather widget for late-model Android phones, tells you everything you need to know about the current conditions, and is also a quick gateway to the weather application where you can see things like forecasts and weather data for other cities. At the other end of the spectrum, the Google Reader 1x1 widget watches a folder in your Google Reader account and tells you how many unread items there are, and opens the full application when pressed. Both are very handy, and add a lot to the Android experience.
Most Android phones come with a handful of built-in widgets. Some manufacturer versions of Android offer more than others, but the basics like a clock, calendar, or bookmarks widget are usually well represented. This is just the tip of the iceberg though. A quick trip into the Android Market will dazzle you with the huge catalog of third-party widgets available, with something that suits almost every taste. With Ice Cream Sandwich supporting things like higher resolution screens and re-sizable widgets, it's going to be an exciting year seeing what developers can come up with.
--------
What is tethering?
What is tethering? Besides the grounds for a giant debate about ethics (the kind that you can only find on the Internet) tethering, in this case, means to share the Internet connection from your phone with other devices. There are several ways to accomplish this -- connecting your phone to your computer via USB, setting up your phone as a wireless hotspot and router, and sharing a data stream over Bluetooth. All these connection types are built into Android, with native Bluetooth tethering new in Ice Cream Sandwich. Of course, different manufacturers can, and have, modified things so that these options are excluded -- at the behest of the carrier, of course. We'll talk more about why in a few minutes.
Tethering itself is pretty easily done. USB tethering involves installing device drivers (Windows only) and plugging in your phone to a high-speed USB port on your computer, then using your computer's built-in connection manager to use the phone or tablet as a USB modem. Bluetooth tethering will need the phone paired with the computer, and the connection type set up correctly in your computer's Bluetooth settings. Wifi is the easiest way -- you just turn it on and connect as you would any other wireless hotspot.
Except that many carriers, especially in the United States, have blocked tethering this way.
You see, your carrier wants to charge you a premium to use your data plan from any device besides your phone. Nobody likes it, but it's in the terms you agreed to when you signed up. They have all sorts of ways to block tethering on their end, and they are pretty diligent about it. Android hackers and developers also have found ways to work around these blocks, and it's a big cat and mouse game. An inside source with one the the biggest cellular carriers in the world has specifically told me that if your usage pattern draws suspicion, there is no current method that can't be detected by you carrier, including the newer VPN methods. If you do it a lot, without paying the extra fees associated with it, you'll get caught.
We're not going to judge anyone, and a few of us here at Android Central think charging extra for tethering is silly -- especially with data caps. Just know what may happen before you start so you don't get caught unaware.
---------
What is sideloading?
What is sideloading? It's a term you see a lot thrown around while talking about Android applications, and it's simple to explain. It means installing applications without using the official Android Market. What's less simple is how it's done and why you would do it. That's where this post comes in. Let's explain it, shall we?
How to do it is easy enough, so let's start there. In the Application settings on your Android phone, you'll find a check box to "Allow installation of non-Market applications." When it's checked, you can sideload. You'll also see a pop-up warning when you check this box letting you know that your phone is now more vulnerable to attacks from applications, and that you accept all the responsibility that comes with doing this. It makes sense -- you can't hold Google responsible for applications you didn't download through their service using their security methods.
Sideloading apps is easy to do as well. You download them to your phone, then use a file manager application to find them and "click" their entry. You'll invoke the app installer program, and it will install your app just as if it had came from the trusted Android Market. It won't be associated with your Android Market account, but it shows in your app drawer just like all the rest. It didn't used to be this easy for everyone. Under the guise of security, AT&T used to block users from sideloading by removing the Unknown sources field in the device settings. Whenever you tried to manually install an app, it would be blocked because it wasn't allowed. This could be circumvented by using adb from the SDK or by using a program like the Sideload Wonder Machine. Luckily, those days are past us and AT&T has re-evaluated their position, and now allows the installation of non-Market apps.
Why would you want to sideload. There are several reasons, one being that Google has allowed carriers to block certain applications based on the model and network your device is running on. We've seen carriers block apps that permit tethering without paying the extra associated fees, and some carriers have exclusives for certain apps and they aren't available for the others. That's a whole other mess that we'll tackle in another post -- just know that it happens. There are other reasons to need to sideload apps, too. Want to use a different appstore like the one from Amazon? You'll need to enable sideloading. The same goes for beta testing apps for developers, or even coding your own apps and testing them on your phone. There are a lot of legitimate reasons for sideloading. Of course, there's always the piracy aspect. If you want to steal from hard working developers you'll need to enable sideloading. You also suck. Sideload, but don't steal from developers.
--------
What is open source?
What is open source? Open-source software is software that makes the source code freely available, for anyone to see and use. There are different open-source licenses that have different use conditions, from the GPL (GNU General Public License) -- which allows "free distribution under the condition that further developments and applications are put under the same license" -- to more liberal licenses like the Apache License, which doesn't require modifications to be open and have the source code available. Android uses both of these licenses, and we'll have a look at them in turn.
The Linux kernel that is used in the OS is covered under the GPL. This means that any changes made to the source code must be made available when a binary (geek-speak for a compiled, executable piece of software) is released to the public. This means manufacturers like HTC, Samsung, Motorola and the rest must release the kernel source-code for any devices they sell at the same time they begin selling them. For the most part, hardware manufacturers are pretty good about doing so, but they often miss the time frame and release the source code a little later than we would like. These are the code releases you see us mention -- the kernel and other open-source "bits" that are covered under the GPL.
The Android OS source code is released mostly under the Apache License. Anybody is allowed to download the source code and change it however they like, but they are not required to make their changes available in source code form to the public. This is why we can't change and recompile things like HTC Sense or MotoBlur -- the changes to the base Android source code aren't available to us. While many folks (myself included) don't like this situation very much, it does make sense from a business standpoint. If manufacturers had to share all of their secrets, there wouldn't be as much monetary incentive to innovate, so the source was offered with a far more liberal license. It certainly worked, as we see devices from many major players in the electronics world.
---------
too,too
aaaaaand too
Good one buddy!
It's good for noobs!
And pro's!!
updated 2+3 post.
Awesome guide bro very informational
Can you emphatize in any way the questions ? Like bold it.
I try to read but i get lost easly x'D
Yeah i know what u mean,i do it with colors.
NERDIFIED TILL DEATH!!!
I like this so far. Please keep up the good work.