Database Users

The damn automatic key lock...

Just got my vibrant today and it auto locks almost immediately. Does anyone have a fix for this? Thanks in advance.
Sent from my SGH-T959 using XDA App

It's under settings->sound and display... 1 minute works great and under the appliactions->Development you can also set it so that it doesn't turn off while plugged into USB (charging). That was a god send when I rooted and put the deodexed ROM on.
Regards,
B

Thanks for the quick reply. Do u know if there is a easy way to keep it from [email protected] all? I would prefer to just lock myself...
Sent from my SGH-T959 using XDA App

Get NoLock from the market.

Yes, nolock. An essential item. I pity all the regular people that don't go on forums with these phones, Samsung and Android are really going to alienate a lot of them. I suppose regular people go for the iphone though so maybe I don't have a point after all.

There is an awesome app called LockDelay that allows you to screen-off your phone after whatever time you specify, and then it will automatically lock it after yet another time you specify.
I HIGHLY recommend it, it really allows you to secure your phone and save your battery by turning that screen off.

bwolmarans said:
I pity all the regular people that don't go on forums with these phones.
Click to expand...
Click to collapse
Just sold a Vibrant in my T-Mobile store today. My rep was showing the customer hers and the customer asked her opinion, he also noticed I had one (I'm the store manager) so I walked over and struck up some conversation to close the deal. As I scrolled through the screen he noticed the XDA app icon and inquired about it. I gave him a few pointers and explained he should joined because there's a wealth of knowledge to be found on these forums. I've found having that little app installed on my phone, as well as our Android live demos is a nice way to introduce customers and new Android owners to XDA.

stock phone is very good. but after customizing, it becomes a whole different android experience.

Thanks for all the tips... I installed no lock, and set the screen to a min an its doing the trick.
Side note, its amazing that I could make the jump from blackberry an transition to the vibrant, can u think of 2 more different phones.
Sent from my SGH-T959 using XDA App Thanks for the help this forum is a great resource.

ThinPhone vs iPhone 4...?
-bZj

ledbetter.james said:
Thanks for all the tips... I installed no lock, and set the screen to a min an its doing the trick.
Side note, its amazing that I could make the jump from blackberry an transition to the vibrant, can u think of 2 more different phones.
Sent from my SGH-T959 using XDA App Thanks for the help this forum is a great resource.
Click to expand...
Click to collapse
They are two very different phones, but as someone works in the industry, my opinion is that RIM hasn't helped themselves by keeping the Berry in the "stone age." Don't get me wrong. I understand they still have a strong following and a huge success in the business market, but Android is catching up and can be used just as well if you have the right phone. Glad you made the jump and the transition is going well.

Screen is now turning on instantly!

Today I noticed that, out of the blue, my screen is now turning on instantly!
I no longer have to wait 2 seconds for it to turn on when I press the volume rocker with widget locker.
I didn't change any widget locker settings, or settings on my phone. I was just wondering if anybody else had this happen.
Now my only problem with the phone is the WIFI disconnects every couple minutes.

What did you do to get this instant screen on?! Things didn't happens magically, please review your latest actions on your phone, this might help several users!
Enviado desde mi MB860 usando Tapatalk

Since I noticed the difference, I haven't downloaded or uninstalled any new apps, but I did do my daily updates of my current apps.
I didn't go into my settings... I DID do a full backup of apps and data using TiB.
Nothing else to note really...

It's so quick, I press the volume rocker, and move my thumb to my slider to unlocked it and I don't have to wait. One constant motion.

Please tell me you're not teasing us. That would be cruel....

I'll try a video... lol i'll have to film with my moms ipad2...
Never live in the past but always learn from it.

Tennis11 said:
I'll try a video... lol i'll have to film with my moms ipad2...
Never live in the past but always learn from it.
Click to expand...
Click to collapse
m.youtube.com/?client=mv-google&rdm=4mz6css5v#/menugrid
Thanks to iPad 2. Lol stupid apple copying android for ios5

http://m.youtube.com/?client=mv-google&rdm=4mz6css5v#/menugrid

Check out this video on YouTube:
http://www.youtube.com/watch?v=StdzAJVW6V8&feature=youtube_gdata_player
I think this one will work. Not sure about first two

Atrix doesn't come out of standby by manipulating the volume. You have an app installed....
Sent from my MB860 using XDA App

I agree.
Sent from my Moto Atrix

He said in the first post that he has Widget Locker installed. Probably pays to read everything fully before throwing around senseless accusations.

bangbang023 said:
He said in the first post that he has Widget Locker installed. Probably pays to read everything fully before throwing around senseless accusations.
Click to expand...
Click to collapse
Lol ... I figured I'd have to make a new video because people would doubt. But I have widget locker setup to turn phone on with volume rocker.
Never live in the past but always learn from it.

if i recall correctly, the screen has always turned on instantly for me, and it still does to this minute.

do you use an SDcard with your atrix, i'm assuming no?

No I never had an sdcard. Why?
Never live in the past but always learn from it.

Why do you retards keep posting these asinine off topic crap in the dev forum? Blatant dumb **** like this should be a banible offense...
Sent from my MB860 using Tapatalk

Thanks for your input but this is the general discussion forum.
Have a nice day
Never live in the past but always learn from it.

Tone it down, buddy.
As should your terrible attitude and language.
hoodlikegaza said:
Why do you retards keep posting these asinine off topic crap in the dev forum? Blatant dumb **** like this should be a banible offense...
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse

hoodlikegaza said:
Why do you retards keep posting these asinine off topic crap in the dev forum? Blatant dumb **** like this should be a banible offense...
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
because it's related scrub. As noted in another thread, screen refresh was somehow linked to a sytem process rescanning the sd card for media everytime the screen was turned on. learn to search the forums, before flaming.
more proof for scrubs:
http://forum.xda-developers.com/showpost.php?p=14254012&postcount=21
from the thread:
http://forum.xda-developers.com/showthread.php?t=1056351&highlight=lag
good day!

About to purchase a used Galaxy S I9000

Sirs,
How are you all doing? this is my very first post and I decided to ride dirty with the android OS finally (I'm late..) Originally coming from that dead Symbian OS environment.. I love customization and everything related to tinkering the phones hardware and software..
So now I am about to buy a used galaxy S I9000, I just want to know what are the things to look for this used android unit? I can see it's just slightly used so what will I look for aside from the outside appearance? How about in the software itself?
I only know that the phone is on GB 2.3.3 I think and it has like a custom way of killing apps, launching..really it's my first time on android and I need professional advises and this is the best site to ask from, I know.
Jesse

Check usb connection and it powers on and gets signal ..... Duplicate thread
Sent from my GT-I9000 using xda premium

as expected, so if this is a duplucate thread, could you please give a me a link to this thread sir? I already read the guidelines, rules, and regulations but I just want to ask from a personal standpoint and I expect this forum to be the best and expert in this Android revolution..

Someone else opened the same.thread
Just make sure usb is secure, make sure it boots ok and speaker is ok.
Sent from my GT-I9000 using xda premium

alright alright gotcha!

How do you want to use your phone?
In my opinion, this device is a disappointment for normal,everyday basic use.
If you really want android ride on SGS, keep yourself ready for be here on xda regularly for help (you tasted it already)and hacks,be ready to root your phone and be ready to reboot your phone n number of times(sometime it does auto ) and be ready to get a mixed feeling,sometime it makes you happy and sometimes you would like to throw it away.
Its my opinion based on use, not intended for anything else.
Sent from my GT-I9000 using Tapatalk

GreenSGS said:
How do you want to use your phone?
In my opinion, this device is a disappointment for normal,everyday basic use.
Click to expand...
Click to collapse
Unless you're installing the latest beta ROMs or custom ROMs, this phone is actually very stable and reliable for day to day use. And the UI is fast and responsive enough on 2.3.3. In any case, in terms of reliability and speed, the SGS is miles ahead of any Symbian device.

Wtf???
Mate. He said he likes to customize.
I have nothing but good things to say about my phone. Gps is accurate and always has been. I knocked back an sgs2 upgrade to wait for next nexus.
Check pixels and speaker.
Check Gps accuracy in maps.
Usb connects and check for 3 button combo to recovery/download mode.
Good luck and enjoy.
Sent from my GT-I9000 using XDA App

Guys,
My use of phone dialer,messaging and call logs comes under basic use.
And dialer lags, contacts gives message 'no additional info available' and then shows number.no matter which rom you use.
Even dialer removed from memory.
I have 2 phones in house one running stock 2.3.3 and one 2.3.5 so I am not imagining anything.
Dont reboot phone for a week and see what happens.
If it was all that good, all the ram tweaks,kernel tweaks,optimization tweaks, wouldn't even exists.
If your expr. & opinion differs post it.
Sent from my GT-I9000 using Tapatalk

wow thanks! a lot of tips already! my appreciation to you guys,
well i want my phone for calls, sms, internet, productive apps,some graphically good games?, storage for photos(bought a 16GB microSD yesterday for this phone, excited am I?) videos-movies perhaps? some noobie photography (BTW I love that touch to focus feature!)
I guess I'm more into content, really LOL
Again thanks!
PS how to enter to download mode?

I'll try first dealing with the stock roms, is there any 2.3.7 GB for galaxy cause I see it everywhere along with the CM7? is that an official firmware or CM7 based on that OEM firmware? maybe when I want more, that's the time I'll do a CM7 flash..what about skype video calling or google talk? is it good in this phone?

GreenSGS said:
How do you want to use your phone?
In my opinion, this device is a disappointment for normal,everyday basic use.
If you really want android ride on SGS, keep yourself ready for be here on xda regularly for help (you tasted it already)and hacks,be ready to root your phone and be ready to reboot your phone n number of times(sometime it does auto ) and be ready to get a mixed feeling,sometime it makes you happy and sometimes you would like to throw it away.
Its my opinion based on use, not intended for anything else.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Trollollololol - back under your bridge fellow.

"Do not feed the trolls"- epic quote
I will be using this phone for everyday use, k?

Another important thing to look for: if it enters Download Mode [Vol Down + Home + Power]
If not, it can be fixed, but it involves a little risk. This would be the only risky thing you'll do software wise, after your Download Mode works, it's very hard to brick the phone.

jcagara08 said:
I'll try first dealing with the stock roms, is there any 2.3.7 GB for galaxy cause I see it everywhere along with the CM7? is that an official firmware or CM7 based on that OEM firmware? maybe when I want more, that's the time I'll do a CM7 flash..what about skype video calling or google talk? is it good in this phone?
Click to expand...
Click to collapse
2.3.7 was a Nexus upgrade that added things like NFC, which most phones do not have the hardware to support this. CM7 uses Nexus source code. I don't believe anything helpful for you was added/changed.
And try not to believe the crap these people are spewing. My contacts, diallers, and whatever else that guy was rambling about are just fine. And obviously that is not a problem across all ROMs, considering most ROMs use different apps (for example, Samsung apps aren't run on AOSP ROMs—and I haven't seen this problem on either).
Good luck! It's an exciting phone.

wow, thanks to all of your advices dudes! what would be a good protector for this phone aside from the screen guards?

ICS: Tips & Tricks

With the popularity of Passion & OneCosmic posts, I'm sure there are a few Tips & Tricks people have found. Please share!!
Tip: Notification bar is accessible from 'lock screen'. No need to unlock to turn on Wi-Fi, BT, 3G, etc. or to read new SMS.

I think this is a great idea.
Let's make sure this is about Tips and Tricks and not "My GPS isn't working" or "Why can't they hear me on the other end of my call".
My tip:
USE YOUR PHONE. Unlock the potential and use it. When we see pix of CPUspy showing Deep Sleep for 20+ hours, sure you are getting great battery life, but you are not using your phone as it should be. They want to be, nay!!, they need to be used, listened to, downloaded on,...then you will truly know what your battery life is like.

In about my phone, tap 4.0.3 really quickly, hen long press the abdroid
sent from the xda app on my android smartphone.

Here's a tip to save some battery power: Settings\More\Airplane mode.
That should do it.
Sent from my SGH-T959 using XDA App

folders at the bottom
I use folders in place of the trebuchet dock apps. that way my homescreen is uncluttered.

Settings >developer options >kill app back button
I use this quite often and missed it from miui.
Sent from my SGH-T959 using XDA App

Woodrube said:
I think this is a great idea.
Let's make sure this is about Tips and Tricks and not "My GPS isn't working" or "Why can't they hear me on the other end of my call".
My tip:
USE YOUR PHONE. Unlock the potential and use it. When we see pix of CPUspy showing Deep Sleep for 20+ hours, sure you are getting great battery life, but you are not using your phone as it should be. They want to be, nay!!, they need to be used, listened to, downloaded on,...then you will truly know what your battery life is like.
Click to expand...
Click to collapse
Well said! I used to be obsessed with battery life and realized I was not enjoying my phone's full features! I bought 2 spares and a wall charger from Ebay and now carry them with me in my car and backpack. I am ENJOYING my phone now! Feels great!

Why would people complain that others cant hear them on the other end? Is that a known problem on ics passion?

Galaxy Nexus Manual
Here's a copy of the Galaxy Nexus Manual. It has lots of good info regarding using ICS.
http://dl.dropbox.com/u/17980900/galaxynexus_manual (1).pdf

when using GPS, make sure to turn wifi on even when you are driving or outdoor or out of wifi range/connection.. just turn it on..
it will make a difference..
probably works on all ROMS.. i used to always skip turning wifi on when i don't get wifi connection.. LOL,

Vibrant03 said:
when using GPS, make sure to turn wifi on even when you are driving or outdoor or out of wifi range/connection.. just turn it on..
it will make a difference..
probably works on all ROMS.. i used to always skip turning wifi on when i don't get wifi connection.. LOL,
Click to expand...
Click to collapse
What does this accomplish?

Would be nice to know how to disable roaming, not data cause I already know that, just having the ability to have your phone not roam ever, unless you want it to

phone_noobie said:
Would be nice to know how to disable roaming, not data cause I already know that, just having the ability to have your phone not roam ever, unless you want it to
Click to expand...
Click to collapse
Settings>Press menu button> data roaming
Is that what you're talking about
Sent from my SGH-T959 using xda premium

xriderx66 said:
Settings>Press menu button> data roaming
Is that what you're talking about
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
No he is referring to Voice roaming. So that if he leaves state people can't get a hold of him.

xriderx66 said:
Settings>Press menu button> data roaming
Is that what you're talking about
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
Raistline said:
No he is referring to Voice roaming. So that if he leaves state people can't get a hold of him.
Click to expand...
Click to collapse
Bingo! Like I initially said, I already know how to turn data roaming off, I want the ability for the voice roaming to be turned off. I had this feature in my previous ROM, which was Team Whiskey's Nero

Bluetooth headset - How to enable auto answer
Hi all,
using passion for quite sometime enjoying all its features, please help me in two issues:
1) While using bluetooth headset, how to enable auto answer option in the phone (Suppose I am unable to touch phone or headset to answer the call)
2) While I am talking to one person using the phone, if I want to access the phonebook, the call goes to hold, and it unholds only I resume the call, in this case what happens that I have to memorise the phone no of any contact to tell the person on call
both these features were well present in my prev ROM, bionix 1.3.1
please help

phone_noobie said:
Bingo! Like I initially said, I already know how to turn data roaming off, I want the ability for the voice roaming to be turned off. I had this feature in my previous ROM, which was Team Whiskey's Nero
Click to expand...
Click to collapse
Umm freeze telephony in titaniumbackup? Will that work?

drsgon said:
Hi all,
using passion for quite sometime enjoying all its features, please help me in two issues:
1) While using bluetooth headset, how to enable auto answer option in the phone (Suppose I am unable to touch phone or headset to answer the call)
2) While I am talking to one person using the phone, if I want to access the phonebook, the call goes to hold, and it unholds only I resume the call, in this case what happens that I have to memorise the phone no of any contact to tell the person on call
both these features were well present in my prev ROM, bionix 1.3.1
please help
Click to expand...
Click to collapse
Are you serious.
Read the title.
Ask passion questions in the passion thread.
This is not a Q&A thread.
Sent from my SGH-T959 using xda premium

Woodrube said:
I think this is a great idea.
Let's make sure this is about Tips and Tricks and not "My GPS isn't working" or "Why can't they hear me on the other end of my call".
Click to expand...
Click to collapse
xriderx66 said:
Are you serious.
Read the title.
Ask passion questions in the passion thread.
This is not a Q&A thread.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
Hmm, took longer than I thought to de-evolve into a Q&A thread.

xriderx66 said:
Are you serious.
Read the title.
Ask passion questions in the passion thread.
This is not a Q&A thread.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
Thank you for your advice Sir, I will follow this in future. Though I have read regarding this in the initial posts of the thread, I had to ask these simple questions to you learned persons as my post count is not more than 10 and so, I am not able to ask in the passion thread. I do not like to make useless posts in the forum as done by many people.
P.S.: Mods, if you think that this post should be removed you are welcome

Force immersive mode?

So now KitKat is out with a new full screen mode that apparently breaks whatever mechanism was previously used to go full screen. So is it technically possible to somehow force an app to use immersive mode?
Sent from my Nexus 4 using xda app-developers app

drinkypoo said:
So now KitKat is out with a new full screen mode that apparently breaks whatever mechanism was previously used to go full screen. So is it technically possible to somehow force an app to use immersive mode?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
"To provide your app with a layout that fills the entire screen, the new SYSTEM_UI_FLAG_IMMERSIVE flag for setSystemUiVisibility() (when combined with SYSTEM_UI_FLAG_HIDE_NAVIGATION) enables a new immersive full-screen mode. While immersive full-screen mode is enabled, your activity continues to receive all touch events. The user can reveal the system bars with an inward swipe along the region where the system bars normally appear. This clears the SYSTEM_UI_FLAG_HIDE_NAVIGATION flag (and the SYSTEM_UI_FLAG_FULLSCREEN flag, if applied) so the system bars remain visible. However, if you'd like the system bars to hide again after a few moments, you can instead use the SYSTEM_UI_FLAG_IMMERSIVE_STICKY flag."
Found at developer.android[dot]com/about/versions/android-4.4.html

It would be cool if there was a method to force this mode selectively of globally for all apps with some sort of control with root.

bunklung said:
It would be cool if there was a method to force this mode selectively of globally for all apps with some sort of control with root.
Click to expand...
Click to collapse
no, no it would not, and no, no it would not work for many!

Wtf are you talking about? Of course it would be desirable and work for many. You just add ONE FLAG to the properties (IMMERSIVE_STICKY) and the application does not even need to be aware!
Sent from my Nexus 4 using xda app-developers app

Already asked developer of full!screen to address this but no response.
Would edit comment but xda app won't let me touch latest post on kitkat, usual high quality of tapatalk
Sent from my Nexus 4 using xda app-developers app

drinkypoo said:
Wtf are you talking about? Of course it would be desirable and work for many. You just add ONE FLAG to the properties (IMMERSIVE_STICKY) and the application does not even need to be aware!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
nope... depends on the design of the app as to if it would work with the UI, it should stay a design decision not a system/platform one!

Look, apps not going full screen has already been a big problem for android for YEARS. That's why there are so many apps that make apps full screen, like full!screen+. But now Google has made it impossible to hide the navigation bar any way OTHER than immersive mode. Consequently I will be sticking with jelly bean for the foreseeable future because there is no other way to use certain apps full screen. Once again Google breaks something I am using for no reason.
Unfortunately you will get your way even though you are wrong. Apparently you can only initiate immersive mode initially, and not from outside the program. According to the developer of full!screen+ anyway.
There is literally NO valid argument against an app being to force immersive_sticky mode. NONE. The app is not aware of it at all, and it's MY phone, not the app developer's. Don't tell me how I want to use my phone, and I won't tell you where to go and what to do when you get there.
Sent from my Nexus 4 using xda app-developers app

Not about right or wrong, and it should not get you wound up. My app would be worse off if you could do it... So no... Bad idea cause I designed my app to use the back button for navigation. If the app design allows... Sure would be good.. If not... No lol
Sent from my Nexus 5 using XDA Premium 4 mobile app

deanwray said:
Not about right or wrong, and it should not get you wound up. My app would be worse off if you could do it... So no... Bad idea cause I designed my app to use the back button for navigation. If the app design allows... Sure would be good.. If not... No lol
Click to expand...
Click to collapse
Sigh. Please read up on Immersive mode: https://developer.android.com/training/system-ui/immersive.html
The user swipes from the edge of the screen to show the UI, and then they can press the back button.
Please educate yourself.

drinkypoo said:
Sigh. Please read up on Immersive mode: https://developer.android.com/training/system-ui/immersive.html
The user swipes from the edge of the screen to show the UI, and then they can press the back button.
Please educate yourself.
Click to expand...
Click to collapse
BTW I mean and intend no malice or to be condescending..
As condescending as you are attempting to be... I personally think you should come back after having designed a few apps.. Obviously I know what it is and know what kiosk mode was very early in Android... Anyway.. Look... I don't like arguing... But I like it less when someone attempts to dictate terms of Ui design.. While also assuming I need to educate myself... I think that's about the dumbest thing you could have said.. Please note that I have not intended to argue and only offer what I thought would be a valid opinion given my experience... I'm not going to explain / educate you on user flow/ Ui design.. But if you do read there are some good books that should demonstrate a few things that would say it's not the best idea. It obviously depends on design principals and methods in use in the app. Anyway I didn't comment on this thread to argue, only offer an opinion... I think you should be a little more open minded as to opinions, who people are, their experience and have a little more respect.. I apologise if anything I have said offends, as always I'm just attempting to be helpful, will leave this thread and unsub. Good luck in your search
Edit: sigh...ugh, ok my helpful nature came back to me, there are many reasons why this would/could and maybe a bad idea for some but not all apps. Here are a few reasons that initially came to mind.
Dev:
Popup view placements with custom menus in apps (rather than using absolute screen coords (as you cant and it's dependant on android version what is reported) devs sometimes have to hack a solution based on system bar and status bar metrics and calculations, this would screw them and they would now have to check the state, hence why it's an app controlled thing!)
Fixed optimized surfaceView or custom renderer handling, user controlled views that change size with no callbacks or state changes and with no android configuration calls can be very bad. Won't explain this one too much. But at the least it would require devs to implement listeners or callbacks, not something that they would do accidentally allowing it to work.
Design:
if using on screen system bar UI controls (back key, onscreen) that is offscreen, then simply going back becomes a gesture and a click, which is fine unless your design dictates this happen lots.
neways thats a few "opinions" and reasons.
drinkypoo said:
Please educate yourself.
Click to expand...
Click to collapse
I always am and do.... how about you?
Sent from my Nexus 5 using XDA Premium 4 mobile app

I hope you do unsub, and leave me alone in the future. Telling me, the user, that I shouldn't have what I want is beyond ridiculous. And since there's no reason whatsoever (and you have utterly failed to present one, in spite of your attempts to be condescending) why I shouldn't be able to decide if an app is full screen, I wish you'd delete your comments too so that this thread could be used for some useful purpose.

drinkypoo said:
I hope you do unsub, and leave me alone in the future. Telling me, the user, that I shouldn't have what I want is beyond ridiculous. And since there's no reason whatsoever (and you have utterly failed to present one, in spite of your attempts to be condescending) why I shouldn't be able to decide if an app is full screen, I wish you'd delete your comments too so that this thread could be used for some useful purpose.
Click to expand...
Click to collapse
hang on I came back to help...and no I apologize yet again if you think that I was attempting to be condescending, that is not the case, I'm attempting to say why it would be a bad idea "to let the user control the system" in such a way. Personally I think immersive mode in apps should be put in by the dev, but be accounted for and designed around. That was my point. I think you have missed what I was attempting to say... and no, despite 17 years of design/vfx/software etc, I have no more right to tell you to educate yourself than you do me, that was another point... anyways sorry you don't get what I was saying (how it would crash/fc some apps, cause that is a fair reason) or how I explained it... good luck again

deanwray said:
anyways sorry you don't get what I was saying (how it would crash/fc some apps, cause that is a fair reason) or how I explained it... good luck again
Click to expand...
Click to collapse
Apps are not aware of immersive mode, how would it crash/fc some apps, and even if it did, why is that an argument against letting the user attempt it? There's tons of apps promoted here on XDA which will cause apps or even devices to crash if misused, hell, even to be bricked. Are you against all of those apps, too? That is what you didn't explain. You're also engaging in the logical fallacy of appeal to experience when you don't have experience actually trying to do this, and you're only engaging in FUD. You didn't come back to help, you came back to continue your argument against what I want and why? Because you're insulted that someone might believe that the developer in fact does not know best?
This is not my first time around the track with a developer who thinks they're wonderful and that users are ignorant and that nobody but them could possibly know what someone might want to do with their device, or with an app. But users are extremely well-versed in one thing: what they want. And what I want is to be able to force immersive mode for apps which don't employ it, mostly because they were written and then abandoned before KitKat was released and before there was such a thing. In such a case, or in any other case, what the developer wants is irrelevant. That is to say, you are irrelevant. Someone who actually wants to help achieve the goal of being able to force immersive mode would be relevant.
For what it's worth, I'm an IT professional with a good twenty years of experience. Developers are worthless without IT, and vice versa. And neither one has a purpose without the user. Hop off your high horse, and either help or don't.

lol, omg! I don't know how you are taking me the way you are... ok this is the last time I'm going to apologize now cause I intend neither malice or to be condescending or anything of that nature, and I as a "new" dev value not only opinions of strangers but highly value opinions of users beyond what I have seen in other devs! I apologize if you think I'm questioning you in some way... again I am not at all, I'm simply pointing out what "I think would happen and why", although I'm somehow failing to explain/communicate properly.
drinkypoo said:
Apps are not aware of immersive mode, how would it crash/fc some apps, and even if it did, why is that an argument against letting the user attempt it?
Click to expand...
Click to collapse
It's the fact that they are not aware of it, android is a fair platform, but not the best when handling any change in the view tree. So here is an example of performance hit... a listView is a type of view user in almost all apps. Here is what would happen from a framework standpoint if lets say, an animation was triggered to get rid of the system bars that the app didn't know about and the dev hadn't planned for...
the listView starts to expand, the 1st indication of this is it gets incremented in height by (some pixel value/cycle animation)
the listView now triggers invalidate(), this causes all backing data to be read again and all views in the list to refresh and is "blocking" (i think) (as in hangs on the main thread and can stop/slow the UI)
it then redraws all the child views when this is done
repeat for every frame of animation..
thats just 1 little example btw, I can think of lots here and some cause FC's
There's tons of apps promoted here on XDA which will cause apps or even devices to crash if misused, hell, even to be bricked. Are you against all of those apps, too? That is what you didn't explain. You're also engaging in the logical fallacy of appeal to experience when you don't have experience actually trying to do this, and you're only engaging in FUD. You didn't come back to help, you came back to continue your argument against what I want and why? Because you're insulted that someone might believe that the developer in fact does not know best?
Click to expand...
Click to collapse
Not against any apps or mods of any kind (although I must admit that some mod influenced crashes have caused me to have to spend time accounting for them) thats not all that nice
I 100% assure you I did not come back to argue, maybe to present a point better yes, but not for any other reason than I think you took/are taking me the wrong way entirely
Also I would never say I know best, ever, there is no guarantee that it would be "ever" true!
This is not my first time around the track with a developer who thinks they're wonderful and that users are ignorant and that nobody but them could possibly know what someone might want to do with their device, or with an app.
Click to expand...
Click to collapse
Ok that is entirely wrong, and I apologize (really last time) if you got that impression!!! You are sounding more like you have had very bad experiences with android developers!
But users are extremely well-versed in one thing: what they want. And what I want is to be able to force immersive mode for apps which don't employ it, mostly because they were written and then abandoned before KitKat was released and before there was such a thing. In such a case, or in any other case, what the developer wants is irrelevant. That is to say, you are irrelevant. Someone who actually wants to help achieve the goal of being able to force immersive mode would be relevant.
Click to expand...
Click to collapse
we are all irrelevant But again I think your taking me/this the wrong way, I keep saying I would "LOVE/LIKE" apps to be designed and updated for this... I actually was very angry at android for 3.0 and forced systembar (end of kiosk mode)
I was simply pointing out why/how such a thing may cause problems if not designed for and accounted for both visually and technically!
Hop off your high horse, and either help or don't.
Click to expand...
Click to collapse
ok last time really really, there is no high horse here, so nothing to hop down off, out of most I know I am probably one of the humblest you could ever meet and actually most critical of myself too! So sorry if you took me the wrong way!
Again, yes it would be a good "design" idea, no it probably would not be good technically given how "lots" of apps are written.
I think it maybe possible with root, but I also think it may crash a large amount of apps...

Well, sorry, maybe I would have taken you differently if you hadn't attacked my idea right away. If you wanted to be helpful why didn't you try that first?
Anyway, it is supposedly impossible to activate later but I would love that to be false
Sent from my Nexus 4 using xda app-developers app

drinkypoo said:
Well, sorry, maybe I would have taken you differently if you hadn't attacked my idea right away. If you wanted to be helpful why didn't you try that first?
Anyway, it is supposedly impossible to activate later but I would love that to be false
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
well I wouldn't call what I said an "attack on the idea" but maybe I should have explained more about why it is not a good idea given on how the android framework expects things.... dont be so quick yourself to attack, defend or assume, as I think I have said all along, it would be a good idea if it wasn't for "android constraints" ... or rather maybe I should have started out that way... tbh I can see a way that it could be done with some "google" love to the api, but not without...
if you could convince google to alter viewGroups or multi view holders to have adaptive offsets for the top and bottom containers, and that there was also an interface listening by default to what window mode it was in, then lots of the problems both design and technical could be overcome. But in all honestly it took them 3 updates to fix a quite simple but annoying keyboard bug, so would not hold my breath on a request such as this
EDIT : thinking about it, would be easier to just convince developers to include support for it. There is not much to it tbh, I may try with smart messenger when I get all core features finished!

deanwray said:
if you could convince google to alter viewGroups or multi view holders to have adaptive offsets for the top and bottom containers, and that there was also an interface listening by default to what window mode it was in, then lots of the problems both design and technical could be overcome.
Click to expand...
Click to collapse
The whole point of the immersive sticky mode is that the App doesn't know it's happening! The very point is that it can be added to an app without any other changes. The app is totally unaware that the UI is being presented, and it is not intended to know because it is not intended to rescale itself! Your objections all apply to IMMERSIVE mode, I don't see how they apply to IMMERSIVE_STICKY at all. You want the app to know what is happening, but it is critical that it not know if it is going to work correctly without any changes to the app itself!
That is why you are boggling my mind so hard. The app isn't supposed to know that the UI is being presented or hidden, and I don't want it to because I don't want it trying to resize itself or do anything else "tricky", for which you should read stupid. It's stupid because if the app tries to do that stuff it will probably fail, and further there is no need for it to happen.

drinkypoo said:
The whole point of the immersive sticky mode is that the App doesn't know it's happening! The very point is that it can be added to an app without any other changes. The app is totally unaware that the UI is being presented, and it is not intended to know because it is not intended to rescale itself! Your objections all apply to IMMERSIVE mode, I don't see how they apply to IMMERSIVE_STICKY at all. You want the app to know what is happening, but it is critical that it not know if it is going to work correctly without any changes to the app itself!
That is why you are boggling my mind so hard. The app isn't supposed to know that the UI is being presented or hidden, and I don't want it to because I don't want it trying to resize itself or do anything else "tricky", for which you should read stupid. It's stupid because if the app tries to do that stuff it will probably fail, and further there is no need for it to happen.
Click to expand...
Click to collapse
not quite sure if you just called me stupid there Hopefully I read it wrong... the problem is that the available app space would change though right ? Meaning that views would change size. To prevent this the app would need a few things designed into it, so yes you are correct in that there would be no need for a listener with STICKY, but the developer would have had to set flags on both windowManager layout and the base View (SystemUi) (this is what i mentioned with offsets based on UI space, all it does is expand the app to fullscreen "underneath" the System bars) ... so yeah, in the end it is the app that needs to do this, because without that space will change and then the problems start...
Hope I explained that enough ?

deanwray said:
the problem is that the available app space would change though right ? Meaning that views would change size.
Click to expand...
Click to collapse
WRONG. This is why I told you to go read up, do your research, et cetera. It wasn't arrogance, it was because you clearly had not done these things, and needed to before you could make an intelligent, insightful contribution.
This is what differentiates IMMERSIVE_STICKY mode from IMMERSIVE mode. The UI elements appear on top of your application. The available app space does not change. When the user is done using the UI elements, or when they time out, they fade away and your app is left sitting there full screen just like it was throughout the presentation of the UI. Your app is utterly and completely unaware of and unaffected by the presentation of the UI elements.
I treated you the way I did because it was clear that you were coming from a position of ignorance, and meanwhile accusing me of the same. Now that is arrogance.