yashsingh1/xdaforums huggingface dataset:
[Java for Android App Development] deanwray:
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.

I always am and do.... how about you? ;)
[Java for Android App Development] drinkypoo:
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.
[Java for Android App Development] deanwray:
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
[Java for Android App Development] drinkypoo:
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.
[Java for Android App Development] deanwray:
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.

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

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!

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!

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!

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...
[Java for Android App Development] drinkypoo:
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
[Java for Android App Development] deanwray:
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!
[Java for Android App Development] drinkypoo:
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.
[Java for Android App Development] deanwray:
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 ?
[Java for Android App Development] drinkypoo:
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.
[Java for Android App Development] deanwray:
calm down again... I never said you were arrogant or ignorant ... I think you are attempting very hard to start an argument here and I do not engage that, I accept I could be wrong as I have only watched the overview dev talks. No need to be nasty about any of this!

But if you look at https://developer.android.com/training/system-ui/immersive.html and read how they are triggered and controlled, I think you may change your mind as these are centric to the app window, not the system ui!

EDIT : I think you should be more community sharing helping spirited, you seem too angry to me, sorry if I caused that in any way, but I read what I'm saying and how I'm saying it, and I look at what your typing/saying and something must be horribly wrong here, you are actually all the things you're calling me, what's worse is that you seem to intended to be this way, all I have done is in good faith attempt to express why I don't think it would work, regardless of either of our knowledge being correct or wrong, you're just presenting yourself as not a very nice individual at all, now I know this may result in you calling me more names, and I really dont mean to insult or anger you... Just felt you should know.
[Java for Android App Development] drinkypoo:
http://www.youtube.com/watch?v=cBi8fjv90E4
[Java for Android App Development] KennyG123:
Let's not get personal in this discussion

Keep to the facts and not insinuate anyone is either stupid, arrogant, ignorant, flamboyant...uh...you get the idea.

Please keep it civil and professional and help each other learn

Thank you for your cooperation

Friendly Neighborhood SeniorMod
[Java for Android App Development] Ironic:
There is a xposed module called Immersive me. :D
[Java for Android App Development] drinkypoo:
As it turns out, the App Settings module for Xposed also does this job, per app.
[AT&T Samsung Galaxy Note II] ckavvouras:
I recently had to downgrade my rom so I could use of of the unlocking methods I found here on xda. I went over to sammobile and downloaded the appropriate rom ( android 4.1) for my carrier and phone, I flashed it using mobile odin, turns out it was a rom for a rogers phone even thought the description and even the file ended with BMC and not RWC which indicated it was for bell, any case I unlocked the phone all went back an restored the system image from cwm all was fine till about 24 hours ago when my phone started acting up very glitchy and i decided it was time to to a full clean up and resort the stock rom. I again mobile odin to flash stock but for what ever reason the apps being loded on to the phone are for rogers carrier. I am using I317MVLBMA3_I317MOYABMA3_BMC which by all indication tells me its for bell, so what the hell is going on ? I have downloaded this and flashed it both from mobile odin and from my pc and ever time its a rogers rom. any help would be great.
[AT&T Samsung Galaxy Note II] koreancanuck:
They're the same roms. All Canadian versions are the same except the system carrier apps included. Your glitches probably happened from something else. Is there any app that you've installed in the last 24 hours or have you done something unusual on your phone in the last 24 hours?
[AT&T Samsung Galaxy Note II] ckavvouras:
they are for the most part the same roms with minor differences for instance the rogers rom displays a 4g icon where as the bell displays a HSDPA icon or something lol, and also the carrier bloatware is not the same bell has its own bloat, even the browser launches to rogers website. I even removed the bloat with titanium and when i flashed the new rom it came right back so i have no idea why this ghost apk files are coming from.
[AT&T Samsung Galaxy Note II] ckavvouras:
update, I downloaded the telus firmware and tried to flash that with odin, flashed fine but rogers apps are still there. can not return to bell stock firmware, any help would be great.
[AT&T Samsung Galaxy Note II] 32dave:
Download csc changer from play and set it for bmc whats funny is mine is rogers but when I flash it I get all bell stuff
[AT&T Samsung Galaxy Note II] ckavvouras:
worked out great thanks a lot man, I was racking my brain why this was not working.
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
When i was using 4.2.2 the wifi timer worked fine, i had it set to come on at a certain time and off, and it worked fine

Since updating to 4.3 i have set the same timer again (as i done a clean install of 4.3) and now every time it gets to the on time, i get a notification saying the wifi timer has started but the wifi it's self doesn't come on, when i look at my short cut tabs at the top the wifi one if off, even after the wifi timer says its started.

is this a known issue?

James
[Galaxy S 4 Q&A, Help & Troubleshooting] maanz "L":
Hi.

I don't think this a known issue.

I'm using it myself and it works good in 4.2 and 4.3.

Does yr WIFI on yr device working without the timer?
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
Yes the Wi-Fi is working fine when I put it in myself, the timer just doesn't seem to be working in my phone, when it gets to the on time, I get a notification saying that the timer has come on but when I bring the notification bar down the Wi-Fi isn't turned on.
[Galaxy S 4 Q&A, Help & Troubleshooting] maanz "L":
Strange..

U might want to re-install the firmware again.

Make sure to do clean wipe, wipe cache partition and wipe dalvik cache before reinstalling.

Other that that, some 3rd party apps u had installed might have prevented the WIFI timer to be activated (some apps are poorly made by the developers).

This is all I can I think of.

Hope that this may help u.
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
thanks for your replies, ive done a bit more testing with it and have found that if i have my phone on when the timer comes on then the wifi does connect, its when the flip case is closed and the phone screen is off it doesnt seem to come on.

also i have also found that everytime the timer comes on i get a security message saying an application attempted to access system on your device, this has been blocked..

the wifi timer is the built in one though and not a 3rd part app, so not sure why thats saying that.
[Galaxy S 4 Q&A, Help & Troubleshooting] maanz "L":
Ok, that is normal when the screen is off, mate.. ;)

I read somewhere here that the security message is kinda bug by Samsung...

btw, are u using the original firmware?

If so, u will get that message.
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
Yes I'm using the original non rooted Rom, when I was 4.2.2 my Wi-Fi would also come on by timer even if the screen was off, that's why I was confused by it not coming on in 4.3

When in 4.2 I was using a rooted version, but decided to go official with 4.3
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
if i download the original fw and reinstall it with odin, will it wipe my apps / settings or will it keep them the same?
[Galaxy S 4 Q&A, Help & Troubleshooting] maanz "L":
Yes..
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
Lol yes to which part of your answer?
[Galaxy S 4 Q&A, Help & Troubleshooting] maanz "L":
Both. It will wipe yr apps and yr setting configurations.:)
[Galaxy S 4 Q&A, Help & Troubleshooting] Nabucodonosor:
I have the same problem of the wifi timer. I have noticed that the wifi timer only works when the phone is plugged in power
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
I eventually fixed the issue i was having by ticking the always allow scanning option in wifi > advanced options.
[Galaxy S 4 Q&A, Help & Troubleshooting] Nabucodonosor:
Thank you.

I tried as you suggest and it works well now but maybe scan wi fi always active discharge more battery. We'll see

Hopefully they will solve the problem with the upgrade to kitkat
[Galaxy S 4 Q&A, Help & Troubleshooting] sten_amund:
Same with brand new i9506

Hi!

I'm seing the exact same with a brand new GT-I9506, 4.3 pre-installed (XXUBML6), completely stock, no root, no odd 3rd party app. Anybody else seing the same for this specific model?

Rgds,

sten_amund
[Galaxy S 4 Q&A, Help & Troubleshooting] james_lpool:
Sten, i fixed this by ticking the always allow scanning option in wifi > advanced options.

See if that works.
[Galaxy S 4 Q&A, Help & Troubleshooting] sten_amund:
Thanks

Thanks James!

Can't believe how I missed that... :o It's pretty clearly stated in your above post.

Rgds,

sten_amund
[Android Themes] alper.s:
Here is a kitkat theme for APEX Launcher

download Version 1.0

Sent via HTC One X!
[One (M7) Q&A, Help & Troubleshooting] CikaKURE:
Hello guys, I need help.

My kid locked phone with entering wrong password too many times and I cant recover it because dont know his google accaunt id and password. When he did that on his tablet, i just enter recovery and reset device, but I cant do that here. I try holding VOLUME DOWN and POWER. Countdown screen appaers but it stuck on 1 second and just keep blinking buttons on botom of device. I tried to find solution with google, and only thing that I found, it can be that fastboot is checked in phone setting? Can you help me how to solve this problem?
[One (M7) Q&A, Help & Troubleshooting] elvisypi:
Keep holdind the power button and than place the light sensor in front of some strong light. After the phone turns off press the vol down button while keeping the power button pressed. You'll get to recovery
[One (M7) Q&A, Help & Troubleshooting] CikaKURE:
You are pure genius man!
[Android Q&A, Help & Troubleshooting] GoldSoft:
hi

i try to install the kitkat 4.4 on my nexus 4

and now i stuck on recovery mode.

i see this

:

fastboot mode

product_name - mako

variant - mako 16gb

hw version - rev_11

bootloader version - makoz20i

signing - production

secure boot - enabled

lock state - unlocked

what can i do ? can i fix it ? :crying:
[Android Q&A, Help & Troubleshooting] demkantor:
Flash a recovery through fastboot and then flash a stable rom
[Nexus 4 Q&A, Help & Troubleshooting] Riel:
When using Fastboot oem unlock to flash the kitkat image, I got this message:

C:\Users\riel>fastboot oem unlock

...

FAILED (status read failed (Unknown error))

finished. total time: 122.501s

Now, I cannot see to get the phone on. When I plug the phone in the PC, I hear the usb connection sound but unknown device. It did boot once after this error, and got me into a fresh 4.3. Then, after turning it off to charge, it is not turning on again.

I saw the red light very shortly, and now it is doing nothing when I press power button or power / vol down.

Any next steps? I only see 'red light fix' but maybe something went wrong with fastboot?
[Nexus 4 Q&A, Help & Troubleshooting] simms22:
not to get down on you or anything, but fastboot oem unlock does not flash anything. it only unlocks your bootloader. and fastboot oem lock locks it back up. if you are trying to flash the factory image, its also done via fastboot and the bootloader, but there are other commands for it. theres a how to flash the factory image thread in general, you should check it out.
[Nexus 4 Q&A, Help & Troubleshooting] Riel:
I only did fastboot oem unlock for now, and rebooted.

My battery is very dead maybe? It's not turning on anymore, no lights, nothing.
[Nexus 4 Q&A, Help & Troubleshooting] eksasol:
It has nothing to do with fastboot. Search for Nexus 4 red light fix on this forum or google. Or let your battery charge for a while.
[Nexus 4 Q&A, Help & Troubleshooting] simms22:
its possible. if you turn off the device, and plug it in, it charges?

have you flashed a custom recovery yet? try charging it a little, the go into your stock recovery(if you didnt flash a custom recovery) and factory reset/wipe data. see if you will boot then.