Related
Is it just me, or is it not a bit tedious to actually terminate a program?
I would suggest adding a minimize-icon to the upper right besides the X-icon. Then the minimize would do what the X does today, and the X-icon would actually truly terminate the program. This would be much more inline with desktop program-use, and to me more logical.
Alternatively the X-icon would offer minimizing or termination when holding the icon. That would be even sweeter maybe...
I'm new to the pocket/smartphone PC thing as of yesterday, but this already bugs me a bit. And I realize this might be daunting task, but it could also be a quite easy fix. But again, I know little of the Windows mobil system.
Best Regards
Bo Eriksson
Most people use a task manager, my favourite is a piece of freeware called Magic Button. Google for it and you should be able to download it, it basically allows you to close applications properly rather than minimise them when you press the x button.
HTH
Fin
smartskey (spelled the way i wrote it) is the best app for this as it remaps the softkeys and truly closes the app. do a search for it here. everyone swears by it.
some programs go loco if they get terminated
mw programs was never really ment to be terminated
the os kill them when it wants to free memory
guess they made it that way to speed up things
outlook if terminated right when you send and sms get upset
and act up and piles of ppl report it as an bug in this forum
I actually installed the first suggested. Seems to do the right thing, but are a bit unstable. Have had a few issues with it, but I'm getting used to work it as it expect to be rather than using it's "undocumented features"...
Best Regards
Bo Eriksson
If you get it to keep messaging, activesync, and the phone applications alive, and tick in the options to hide when inactive, it works perfectly AFAIK.
Fin
i use handyswitcher, is very cool and you can specify the tasks that you do not wanna terminate when you close all like activesync
hi chaps
right, here's my problem:
i've got a prophet running the latest dopod rom. all's well in pda land. unfortunately, i've had to do some fiddling to get o2's homezone app working the way it should do. more or less. see, the thing is when my device wakes up, the homezone app HZDisplayDataSMP is always in the foreground. so before i can do anything i have to press the OK button. now, i can sort of live with this, as i have homezone functionality, but it's, well, a pain in the arse, to be honest.
so, my question to you guys is this: does anyone know of a WM5 programme that will run apps, but force them to remain in the background. i was thinking of some resident startup item that would keep the app hidden away nicely from my interface, but continue to allow it to do what it needs to.
does anyone know of anything that sounds useful? if so, you're my man. i've got a hunch our good vijay555 might be able to lend a hand, but feel free to throw suggestions at me.
thanks a million, guys
I was asked about a similar app recently, to run apps minimised.
I've had major troubles rebuilding my PC after I installed the Vista Beta and it decided to eat my Documents & Settings and Program Files.
I'm finally back up to speed and able to start programming again, so will try to look into it.
But it should be easy enough for a developer to knock together with ShellExecute.
In the meantime, you might want to use a mort script to find the window by caption and minimise it. Or SK Schema should be able to do exactly what you want, run an event when it finds a window by caption.
V
righto! thanks for the heads-up. really appreciate it, pal. i'll have a look into both of those suggestions.
ps: the only reason to install vista is halo 2 pc. can't think of any other factor which would cause me to pollute my hard drive with such nonsense
Like the one in SPB mobile shell, but for apps rather than avalible screens.
like this one http://www.spbsoftwarehouse.com/products/mobileshell/
mmmalas said:
Like the one in SPB mobile shell, but for apps rather than avalible screens.
like this one http://www.spbsoftwarehouse.com/products/mobileshell/
Click to expand...
Click to collapse
not sure about this.... what if only 2 open apps? or 20 apps? how to scroll? What seems more user friendly is something like coverflow/music tab, per app like one screenshot and can swipe between apps. It is however a very big load for the system i think....
mouki_9 said:
not sure about this.... what if only 2 open apps? or 20 apps? how to scroll? What seems more user friendly is something like coverflow/music tab, per app like one screenshot and can swipe between apps. It is however a very big load for the system i think....
Click to expand...
Click to collapse
if you open 2 apps, then you have 2 windows opposite to each others, with 20 windows then big carousel .
system usage not going to be much unless you are navigating the task switcher, but once it dissapear then no need for it to run with full memory
Hmm...
mmmalas said:
if you open 2 apps, then you have 2 windows opposite to each others, with 20 windows then big carousel .
system usage not going to be much unless you are navigating the task switcher, but once it dissapear then no need for it to run with full memory
Click to expand...
Click to collapse
Having a look at this now... It is actually a little more complex than you think though. Even before we go anywhere near the carousel part (3D is well out of my league) you still have to think about how your going to get the screenshots to display on it:
Windows only actually performs paint operations on active windows therefore we need to take screenshots of that active window, how are we going to do that?
a) Use a timer taking screen shots at regular intervals (every few secs or so) of the currently active window using the last one taken as the screenshot when inactive - Obviously this still does require both memory and proc time to perform even when whatever UI you create is not actually active. This however is the most likely to work solution to the problem.
b) See if there is any way you can catch a window at the moment it is being minimized - This is potentially difficult but would probably be the most accurate. However this is may not actually possible (need to research a little more though) - i.e. can you actually catch the window before it actually minimizes or are you always going to be too late and end up capturing nothing. Kind of like trying to photograph a bullet from a gun using a handheld camera by listening for the sound of it firing (capturing the close event on the window and acting on it before the actual window it was sent to acts on that event) <---- Maybe a more experienced dev has some thought on this?
I also agree with mouki a little on this one in terms of usability. As much as your idea is much cooler to look at after about two days I would want to swap it for something where I could actually efficiently switch between tasks rather than rolling through an endless carousel trying to find that *bloody* app I wanted to switch too.
I'm going to see what I can come up with but I think it's going to end up being tile based as that is the most efficient as you'll be able to see more at one time but definitely like the idea of having thumbnails rather than just names for a switcher...
However I'm working on another project though at the mo (Leo as a fully customisable remote control for our PC's) so wont have much time just now to look at a switcher project, however will keep you posted on what I find out...
this will be more usable really in terms of switching, as you will have photo of what you are switching to rather than just a name.
it all depends on how your memeory works really.
remember how you switch windows in MS windows with alt tab, or win+tab.
its less usage on the brain that way.
as for closing, you dont care about closing, since once its closed then there is no need to display. what you care about is minimizing, or when win is inactive.
I can do this type of application on the PC very easily using AutoHotKey script. however I have no clue how PPC programing is done
A starter for ten
Fortunately my background in programming comes from the .net framework so it's reasonably easy to make the jump to .net compact framework ppc (even if I've got to get used to the reduced ammount of functions). I can see how this would be different for you... I've just taken a look at what AutoHotKey is probably the nearest equivelent for you would be MortScript (Pretty powerful)
Heres our starter for ten anyway in vb.net: http://anoriginalidea.wordpress.com/2008/01/03/getting-a-screenshot-using-vbnet-on-the-compact-framework-20/ <--- This shows the library that would be used to capture the screen shots.
I guess this is my honeycomb ignorance (still getting used to the features) but when pulling up recent apps with the softkey I really only want apps that are currently running.
Are some of these apps are already "closed" and by choosing a thumbnail from the list I'm re-opening these?
Is there a setting anywhere to "limit" the history I see? Like <5 apps or something?
I have Task Killer pro intalled now to manage the real running apps but the Softkey is handier, if I can just be sure of what its supposed to indicate.
Thanks
Sent from my Transformer TF101 using XDA Premium App
I was wondering this as well. I haven't found any way to do it yet.
I don't know of any way except to manage apps in the settings and then kill "running" apps....but remember; these are apps "in memory" like you'd think in Windows.....they are not sucking resources...
I think that there is an article here somewhere about this list and why you shouldn't use an app killer in Honeycomb....
I'm more interested in changing it to a grid layout, like a speed dial.
yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.
moo99 said:
yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.
Click to expand...
Click to collapse
I agree. I just want a cleaner recent apps list. Sometimes it's hard to find what you're looking for.
I guess a workaround would be to longpress the home screen, put a widget there that is linked directly to "manage applications" and then it would only be one press and then zap the offending apps.
You do realize the Recent Apps button on the homescreen is just that, a Recent Apps button. It's not exactly a "running in the background" button.
"I finished playing chess yesterday, I dont think the game should stay in the recent apps list."
Why not? It is a recently played app isn't it? LOL.
And yeah, agree with the other reply, if you want a list of running apps.... don't touch the Recent Apps list button lol.
Stop worrying about what's running in the background. Just enjoy the damn Android.
Im not near my TF now but I use Multitasking Pro on my Galaxy S for that. you can choose to open it by double clicking the home button and see only running apps or recent apps - its configurable in the application settings. i does cost about 2$ i think but it was the best 2$ I've spent
this is called a 'Recent apps' list for a reason...it's 'Recent'..not current running...
Well you could always downgrade to 3.0 if it really bothers you. That only showed 5 apps!
LOL. Its a nuisance, not so much a grievance; but I'm glad I'm not the only one annoyed, perhaps this will get looked at ;-)
Possibly once Honeycomb is more prevalent there will come market apps or enough reportage to have an updte with a setting for it, or a utility that tweaks it. Regardless, I appreciate the feedback. At least now I know its sort of "normal".
Sent from my Transformer TF101 using XDA Premium App
My number one wish is for Google to improve multitasking (and give back control to the user as to which programs are running).
As is, the implementation just isn't very usable if you consider it to be a multitasking device -- it's really closer to single-tasking with a memory of what it did recently and the ability to reopen with a similar state to what it last had.
For example, I use my tab during F1 races for timing and scoring. I have F1.com's timing and scoring app, and I have access to a (non-public) website which provides further real-time info through Adobe Flash in a web browser.
If I switch from the web browser to F1.com's timing and scoring app for more than say 10-15 seconds, then back again, the flash app has to reconnect to the server because the web browser ceased running, even though the browser and the F1.com app were the only programs running and had ample memory / CPU power / a mains power supply connected, ie. no reason to halt the browser.
This isn't the only time I hit this issue, it's just one easy-to-explain example.
I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.
The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.
knoxploration said:
.I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.
Click to expand...
Click to collapse
The problem is that the vast majority of users won't want to handle this themselves, and would expect the OS to do if for them.
Personally, I'm in favour of having some sort of mechanism whereby you can tell the OS not to kill specific tasks if you so choose, but otherwise task management performs as is.
With specific regard to your example, I think that the OS believes it is always OK to kill the browser, which is why it can be killed so quickly after switching away. For other apps, this doesn't seem to happen - for example, yesterday I was connected to a remote server using Wyse PocketCloud, and I frequently switched away to do something else for 30-60 minutes at a time, yet my remote desktop connection was never dropped or killed.
Regards,
Dave
Me personally don't need and don't like this "recent" app button. Or I need it to have an option either to clear it or not. You know we sometimes need privacy over such things
JCopernicus said:
The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.
Click to expand...
Click to collapse
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App
...and it should be *my* choice whether that happens. That is where this argument totaly falls on its face. *I* know whether it is vital to me that an app remain open, or can safely be closed. The tablet doesn't.
As long as it remains in the tablet's hands, it will continue to annoy me by leving open apps that I no longer need running, while closing apps that I strongly do need running.
magicpork said:
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
that's just it....it doesn't.
Revisiting Android Task Killers and Why You Still Don’t Need One
from another forum.
We almost hate to approach the topic of Task Killers on Android after all this time, but with so many new faces here at Droid Life and in Android in general, it’s something that needs to be done. In fact, after seeing the Amazon app of the day and reading through the Twitter conversations we just had with many of you, this thing needs to be posted immediately.
Let’s see if we can’t get you all some better battery life!
First off, please ignore the image up at the top of the post. If this was 2009 and we were all running something less than Android 2.2, that statement plastered on that red banner might be somewhat correct. But since it is 2011 and the majority of people on the planet are running Android 2.2, we need to get you away from the mindset that killing off tasks on your phone is a good thing.
So rather than me blabbering about the inner-workings of Android and how it manages RAM for the 10,000th time, I’m going to just pull from some posts that friends of ours have done that explain this in the plainest of ways.
First up is our boy @cvpcs who you may know from CM and his Sapphire ROM days. He knows Android inside-and-out, so when he goes into memory management which is done by the OS itself, you should listen up:
…What people don’t seem to realize is that android is designed to have a large number of tasks stored in memory at all times. Why? Well basically we are talking about a mobile device. On a mobile device things tend to be slower. The hardware isn’t as robust as say a desktop or a laptop, so in order to get that same “snappy” feeling, there have to be workarounds.
One of these is how android deals with memory. Android will load up your apps and then keep them running until they absolutely HAVE to kill them. This is because that way, if you want to re-open an app, the system already has it loaded and can then just resume it instead of reloading it. This provides a significant performance increase.
What a lot of people don’t realize as well is that android kernels have their own task manager. This means that:
it will be more efficient than any app-based task manager as it is run at the kernel level, and
it should be left up to that task killer to decide when to free up memory
There is only one case where having a task killer is a good idea, and that is when you want to kill ONE SPECIFIC APP. Killing all apps is never a good idea. You don’t know what operations they are performing or if they are necessary.
Whitson Gordon of Lifehacker suggests that you should be more worried about CPU usage than what’s going on with your RAM. We agree:
This set-up implies that the goal of killing these apps is to free up memory. Nowhere on the list does it mention the number of CPU cycles each app is consuming, only the memory you’ll free by killing it. As we’ve learned, full memory is not a bad thing—we want to watch out for the CPU, the resource that actually slows down your phone and drains your battery life.
Thus, killing all but the essential apps (or telling Android to kill apps more aggressively with the “autokill” feature) is generally unnecessary. Furthermore, it’s actually possible that this will worsen your phone’s performance and battery life. Whether you’re manually killing apps all the time or telling the task killer to aggressively remove apps from your memory, you’re actually using CPU cycles when you otherwise wouldn’t—killing apps that aren’t doing anything in the first place.
In fact, some of the processes related to those apps will actually start right back up, further draining your CPU. If they don’t, killing those processes can cause other sorts of problems—alarms don’t go off, you don’t receive text messages, or other related apps may force close without warning. All in all, you’re usually better off letting your phone work as intended—especially if you’re more of a casual user. In these instances, a task killer causes more problems than it solves.
More on how Android has a built-in memory-management system, but also on how killing all tasks is not a good thing (via: NextApp):
Android was designed from the ground up as an operating system (OS) for mobile devices. Its built-in application and memory-management systems were engineered with battery life as one of the most critical concerns.
The Android OS does not work like a desktop operating system. On a desktop OS, like Windows, Mac OS X, or Ubuntu Linux, the user is responsible for closing programs in order to keep a reasonable amount of memory available. On Android, this is not the case. The OS itself automatically removes programs from memory as memory is needed. The OS may also preload applications into memory which it thinks might soon be needed.
Having lots of available empty memory is not a good thing. It takes the same amount of power to hold “nothing” in memory as it does to hold actual data. So, like every other operating system in use today, Android does its best to keep as much important/likely-to-be-used information in memory as possible.
As such, using the task manager feature of SystemPanel to constantly clear memory by killing all apps is strongly NOT RECOMMENDED. This also applies to any other task killer / management program. Generally speaking, you should only “End” applications if you see one which is not working correctly. The “End All” feature can be used if your phone/device is performing poorly and you are uncertain of the cause.
And we could go on for hours with source after source on why task killers do nothing but work against Android, but you probably get the point now don’t you? Ready for a quick recap? OK.
Basically, Android keeps tasks handy because it thinks you’ll want to perform them again in a very short amount of time. If you don’t, it will clear them out for you. It also likes to keep as many things handy as possible so that the overall performance of your device is top notch. If Android were to completely kill off everything that your phone is doing, then it would require more resources to restart all of them and you would likely run into slowness and battery drains. By keeping certain things available to you, your phone is actually running better than it would without. So please, stop killing off tasks and let Android do the work for you.
Your goal for the week is wash your brain of the idea that having little RAM available is a bad thing. The more RAM available, the more Android will find ways to use it up which means your battery will be dead in hours. Instead, let it manage itself, so that you can spend more time playing Angry Birds or reading Droid Life.
All good now?
A simple reboot clears the list of recent apps. And as others have stated, it's not about running apps but something like the "recent documents" list in Windows 7
I've used an Android tablet for about a year now, and although I've put in a lot of time to make it useful and controllable, it still has a lot of troubling mysteries. I have a few questions for developer types that hopefully will help shed some light on things:
1. Why don't applications feature a "Close" button? In both Windows and GNU/Linux with a GUI, you get a neat little "X" at the top right of the window. Usually, when you click this, the application terminates. Is that so much to ask for on Android? The means of closing apps on Android seem to be entirely up to the devs and there doesn't appear to be a standard way at all. Some of the apps I've used on Android don't have any way to close them whatsoever, with the exception of killing them from a task manager or the "Manage Apps" section of settings.
2. Why do many of these programs suddenly and mysteriously start running entirely on their own? It's terribly frustrating for me to kill an app and in a half an hour find it there on the task manager list again, running without my having asked for it to do so. Where is this controlled? If there is some sort of task scheduler making this happen, why can't I easily see a list of scheduled tasks and choose which ones to run or not to run?
3. For programs that *are* running in the background (the ones I *want* to have running), why is it that they usually don't have some sort of taskbar icon to indicate at a glance that they are still running?
4. Why can't I see everything that's loading when the tablet starts? I guess I'm asking to see a logcat screen instead of a splash screen. GNU/Linux distros don't usually hide everything from the end user, so why isn't it optional on an Android tablet? Even in custom ROMS all I get are neat looking splash screens, not a terminal interface on boot.
5. Why doesn't a decent firewall application yet exist for Android? All I seem to be able to find are really coarse ones like Droidwall, where it's an all or nothing proposition (allow/block). I'd like to be able to control protocols, ports, zones and individual IP addresses and ranges like a good firewall on Windows or GNU/Linux allows. I am constantly under suspicion that someone is doing something on my tablet without my even being aware of it.
6. Why are permissions for applications so difficult to control? Maybe I don't want some stupid game getting a look at my contacts list. I realize I can just uninstall the game, but so many apps seem to tap into stuff that they shouldn't be allowed to, I feel like some sort of permissions control should be a default standard thing in Android. Instead all there seems to be are a couple of apps on the market that may or may not work.
7. Do any of you developers feel dissatisfied about the state of Android, and does Google take your feedback seriously?
8. Are there any forks of the Android OS that don't rely on Google for anything? I'm not 100 percent sure about the difference between a GNU and an Apache license. How much of the OS is closed-source? Is it enough to prevent a true, fully open-sourced Android-based OS from being made?
Sorry if any of these questions sound stupid, but even though Android is supposed to be more open than iOS, it's still not open enough for my tastes. I actually feel safer using Windows than Android, and that's just not how it should be. Am I alone in this feeling?
Ok. I would honestly say you should have gone with a Windows tablet if you want all those... It's not a computer. It's a mobile device running a mobile os. It's not gonna be a full blown computer.
McMick said:
I've used an Android tablet for about a year now, and although I've put in a lot of time to make it useful and controllable, it still has a lot of troubling mysteries. I have a few questions for developer types that hopefully will help shed some light on things:
1. Why don't applications feature a "Close" button? In both Windows and GNU/Linux with a GUI, you get a neat little "X" at the top right of the window. Usually, when you click this, the application terminates. Is that so much to ask for on Android? The means of closing apps on Android seem to be entirely up to the devs and there doesn't appear to be a standard way at all. Some of the apps I've used on Android don't have any way to close them whatsoever, with the exception of killing them from a task manager or the "Manage Apps" section of settings.
2. Why do many of these programs suddenly and mysteriously start running entirely on their own? It's terribly frustrating for me to kill an app and in a half an hour find it there on the task manager list again, running without my having asked for it to do so. Where is this controlled? If there is some sort of task scheduler making this happen, why can't I easily see a list of scheduled tasks and choose which ones to run or not to run?
3. For programs that *are* running in the background (the ones I *want* to have running), why is it that they usually don't have some sort of taskbar icon to indicate at a glance that they are still running?
4. Why can't I see everything that's loading when the tablet starts? I guess I'm asking to see a logcat screen instead of a splash screen. GNU/Linux distros don't usually hide everything from the end user, so why isn't it optional on an Android tablet? Even in custom ROMS all I get are neat looking splash screens, not a terminal interface on boot.
5. Why doesn't a decent firewall application yet exist for Android? All I seem to be able to find are really coarse ones like Droidwall, where it's an all or nothing proposition (allow/block). I'd like to be able to control protocols, ports, zones and individual IP addresses and ranges like a good firewall on Windows or GNU/Linux allows. I am constantly under suspicion that someone is doing something on my tablet without my even being aware of it.
6. Why are permissions for applications so difficult to control? Maybe I don't want some stupid game getting a look at my contacts list. I realize I can just uninstall the game, but so many apps seem to tap into stuff that they shouldn't be allowed to, I feel like some sort of permissions control should be a default standard thing in Android. Instead all there seems to be are a couple of apps on the market that may or may not work.
7. Do any of you developers feel dissatisfied about the state of Android, and does Google take your feedback seriously?
8. Are there any forks of the Android OS that don't rely on Google for anything? I'm not 100 percent sure about the difference between a GNU and an Apache license. How much of the OS is closed-source? Is it enough to prevent a true, fully open-sourced Android-based OS from being made?
Sorry if any of these questions sound stupid, but even though Android is supposed to be more open than iOS, it's still not open enough for my tastes. I actually feel safer using Windows than Android, and that's just not how it should be. Am I alone in this feeling?
Click to expand...
Click to collapse
1. Well, its a mobile OS and it would be rather annoying to have a close button on every (even most) apps. No mobile OS has had a close button
2. That's an app problem, the developer either wanted the app to do that for some function, or they made some mistake in creating causing that to happen.
3. There would be too many apps, and I doubt people want extra notifications in the status bar just informing them what's running. For example, my friends Stratosphere has a status notif whenever WiFi is connected, and it annoys the crap out of me whenever I use it.
4. Probably, because people don't care... remember Android (like WP and iOS) are supposed to appeal to consumers as a phone for "facebook, games, and internet," and if the splashscreen/bootanimation was a logcat, people would just go "wut?" Also, as smartphones get faster and faster, so does bootup time. And there wouldn't be enough time to read what's on the logcat before it fully boots and you're at the lockscreen
5. Ask the devs.
6. Once again, dev thing. They are entitled to putting whatever permission they want, and Google isn't going to stop them. Just think about it though, most people don't care about permissions. iOS doesn't display them (even though they are there) and people download apps like there's no tomorrow anyway.
7. I read somewhere that the main designer of Android was "40% complete" at ICS. It gets me excited at what's next to come, since 4.0+ is already pretty amazing.
8. I'm too retarded to understand this question
Sent from my DROID2 using xda premium
As gagdude said for 1-7.
8. There's the Chinese Aliyun OS which looks and feels a lot like Android but doesn't rely on Google - but I would't try it. You could try Ubuntu Linux if your device supports it.
Android needs to be like apple with updates time to close source this already and just have one phone already
Sent from my DROID RAZR using Tapatalk 2
Reopened, but if it gets unproviding and or heads Off Topic, well then I will readdress this thread.....
Thank you and you can Thank user: Syncopath
gagdude said:
No mobile OS has had a close button
Click to expand...
Click to collapse
Wrong, PocketPC 2002, which I used for 10 years on my HTC Wallaby, had a close button for every application.
@McMick, many of your points struck a chord with me and I have often asked myself the same things since migrating to Android from Pocket PC 2002 on my HTC Wallaby. Certainly points 1, 3, 7 and 8.
Since I jumped from PPC 2002 to Android 2.3.6 I've had the same thoughts. And I was for instance surprised to see that only now (Galaxy Note 2) are the very first steps being taken towards multiple windows.
I agree with point 4 too. On a PC (Linux or Windows) you can choose whether you see what's starting (BIOS and OS boot) or prefer a reassuring animation.
5. I have Avast!Mobile Security which has what is reckoned to be one of the best firewalls for Android, but even that only has, as you say, block or allow (individually for WiFi, 3G and mobile network).
6. The trouble with limiting permissions for apps is that if they can't get the access they want, they won't work. Personally I use the app Privacy Blocker which works around that by feeding the apps you choose not to allow to snoop nonsense information.
However it's not enough just to stand on the sidelines and issue one's wishes to "the developers". The point and the spirit of XDA-developers is that we can all start modifying things if we want to. So instead of saying "Why can't I" the thing to do is to start reading and learning and seeing if you might not after all just be able to ... do something yourself when it comes to your device.
Every Android developer does what appeals to them, which is why there is such a wonderful diversity of ROMs and apps for Android, particularly here on XDA.
So get stuck in and start trying to change things on your own device for a start. On point 5 for instance, you do see a logcat screen when you boot into recovery mode, so perhaps there's a way to display that when booting. If you do get started on modifications in the directions you indicate, I shall certainly follow progress with interest.
Thanks to BigJoe2675.
syncopath said:
Wrong, PocketPC 2002, which I used for 10 years on my HTC Wallaby,
However it's not enough just to stand on the sidelines and issue one's wishes to "the developers". The point and the spirit of XDA-developers is that we can all start modifying things if we want to. So instead of saying "Why can't I" the thing to do is to start reading and learning and seeing if you might not after all just be able to ... do something yourself when it comes to your device.
Every Android developer does what appeals to them, which is why there is such a wonderful diversity of ROMs and apps for Android, particularly here on XDA.
So get stuck in and start trying to change things on your own device for a start. On point 5 for instance, you do see a logcat screen when you boot into recovery mode, so perhaps there's a way to display that when booting. If you do get started on modifications in the directions you indicate, I shall certainly follow progress with interest.
Thanks to BigJoe2675.
Click to expand...
Click to collapse
+1
---------------------------
PocketPC 2002, which I used for 10 years :crying::crying: sorry for this....
syncopath said:
Wrong, PocketPC 2002, which I used for 10 years on my HTC Wallaby, had a close button for every application.
@McMick, many of your points struck a chord with me and I have often asked myself the same things since migrating to Android from Pocket PC 2002 on my HTC Wallaby. Certainly points 1, 3, 7 and 8.
Since I jumped from PPC 2002 to Android 2.3.6 I've had the same thoughts. And I was for instance surprised to see that only now (Galaxy Note 2) are the very first steps being taken towards multiple windows.
Click to expand...
Click to collapse
OK, but I wasn't born in 2002.
Lol jk I was, but I wasn't "born" to technology back then. I got my first phone only 3 years ago or so... and that just makes it seem that close buttons are now obsolete (on Mobile OSes, at least
Sent from my DROID2 using xda premium
gagdude said:
OK, but I wasn't born in 2002.
Click to expand...
Click to collapse
LOL as I believe they say these days. I forgive you instantly! I am amazed by your over 1000 posts in about 4 months.
McMick said:
4. Why can't I see everything that's loading when the tablet starts? I guess I'm asking to see a logcat screen instead of a splash screen. GNU/Linux distros don't usually hide everything from the end user, so why isn't it optional on an Android tablet? Even in custom ROMS all I get are neat looking splash screens, not a terminal interface on boot.
Click to expand...
Click to collapse
The app [root] live logcat by the one and only Chainfire [/hyperbole] should fix this. There are free and paid versions. Something to check out if you're rooted. Please let us know of the results. Added on edit: from Google Play.
syncopath said:
LOL as I believe they say these days. I forgive you instantly! I am amazed by your over 1000 posts in about 4 months.
Click to expand...
Click to collapse
Oh no that just means I'm a loser and I spend too much time on xda
Sent from my DROID2 using xda premium
@bigjoe,
bigjoe2675 said:
PocketPC 2002, which I used for 10 years :crying::crying: sorry for this....
Click to expand...
Click to collapse
Don't quite understand this message, probably due to my inability to correctly interpret emoticons (reverse autism?). Anyway, thanks for re-opening this one because I
think what is being discussed here is worthwhile. Given the pressure of spammer-threat I think the OP should respond soon (or anyone else). Otherwise it will be understandable if you close the thread if you prefer.
bigjoe2675 said:
Reopened, but if it gets unproviding and or heads Off Topic, well then I will readdress this thread.....
Thank you and you can Thank user:
Syncopath
Click to expand...
Click to collapse
I think I understand your priorities as moderator. This is of course a thread near the "top" of XDA and as such will far more readily attract spammers and other lowlife than further down in the more comfortable device threads where I am more used to posting. So you will want to quickly close any thread that seems to be becoming stale. Right?
@gagdude
gagdude said:
Oh no that just means I'm a loser and I spend too much time on xda
Click to expand...
Click to collapse
I don't think so, over 200 thanks didn't come from nowhere!
This is off subject having prob w/ no boot sound for boot anim
Sent from my Huawei-H867G using XDA Premium 4 mobile app