I've found myself back here on the forums after getting frustrated with the official Windows updates.
There's a really big glitch I've encountered that changes the volume from Normal to Vibrate or vice versa.
It took me years to finally realize why my phone was switching profiles without me changing it.
Whenever I start a new text message and type the letter 'A' too fast as the first letter of the message it changes to Normal/Vibrate. If I slowly start typing the message, the glitch is avoided.
Has anyone else encountered this bizarre problem? I'm still trying to figure out how this could even be possible! Any suggestions from the gurus?
This problem exists on ALL Roms I believe ... I have always had it.
Here is the explanation, as I see it:
The Texting program, in all honesty, sucks. Windows decided to create the TextBox before loading up the history of messages, which meant there was a huge lag. FURTHER: They didn't do these actions on separate threads, which means the lag would occur on one thread.
Now think of it this way: While a program can have different 'threads' to run on, the keyboard, while an input to the program, will get its own thread because it is a system device. So the Keyboard gets its own thread, therefore its own buffer.
What goes on, in the second it takes to load the text message history is this:
1) TextBox appears and is activated to user [and Keyboard]
2) History load starts on same thread as TextBox
3) User types "A"
4) "A" is sent to the foreground window, which is the TextBox
5) The TextBox takes a while to respond, to process the message, therefore the system assumes the key was held down for X seconds.
6) Realizing this is the Hard-coded "change-profile" shortcut, the system then sends a message to the Profile 'manager' (if one exists, but in theory let us say it does) to switch profiles.
7) The TextBox stops lagging since the history is loaded, and it registers that the 'A' key was lifted.
The whole issue has to do with timing and buffers ... all pretty stupid errors on Microsoft's part.
I had wanted to start making a replacement, but alas, I have no time
One day....maybe one day
Brilliant Cyclone! Thanks for the simplified/understandable response.
I didn't realize the quick button to switch profiles is the 'A' button. That's much more understandable.
I just updated my phone to 3v0, but then downdated to 1.22.531.6 because it 3v0 was too buggy.
It cleared all my text messages and I haven't had the A-glitch yet. I'm guessing clearing the text history is the only way to avoid the glitch.
I'm surprised I haven't heard other people talking about this problem. I Googled it, but couldn't find anything.
Very interesting...although, these kind of problems are expected when dealing with Microsoft.
I just had a thought...
How easy would it be to change the "Hard-coded "change-profile" shortcut" to a letter that is never used? Like 'Q'. Or completely remove the change-profile shortcut.
You guys are way over my head when it comes to working with the fundamentals of phones(the registry?) like this. I'd like to learn more, but I must also say....One day....maybe one day!
I don't honestly believe it is possible..."hard coded' means that they programmed it straight into the OS.
Now realize, this is only my theory, I can be 100% incorrect..
The OS can't have any changes made to it? I thought this was possible through something like "regedit" on PC's. Changes to the registry aren't changes to the OS?
zemaoner said:
The OS can't have any changes made to it? I thought this was possible through something like "regedit" on PC's. Changes to the registry aren't changes to the OS?
Click to expand...
Click to collapse
Things in the Registry aren't 'hardcoded' ... when I say 'hardcoded' I mean that when Microsoft employees was in their IDEs developing, they typed in a few lines of code dealing with the A-Key, and then compiled it. We cannot change that, especially since it is part of the ROM.
Related
When I am typing in the messaging application, I find that many of my key presses are ignored, seeming as though I am not able to spell or use proper punctiation, even though I have actually tapped the correct keys.
My messages might look like the following:
"Thaks fo your message. I was nt able to take the call at th time buI will be avaiable after 6pm. Thanks again!"
This is really annoying. It ONLY happens in the messaging application. I can type an entire document in Word without a single problem but I correct numerous mistakes in emails and text messages in order to avoid looking like a moron to recipients of my messages.
Is there anything I can do to correct this problem? I am using the Black Edition ROM right now and thought that this version fixed the problem. I also Experienced it with the LVSW versions and the other before that. I did not experience it in WM5 at all...
pinhead said:
When I am typing in the messaging application, I find that many of my key presses are ignored, seeming as though I am not able to spell or use proper punctiation, even though I have actually tapped the correct keys.
My messages might look like the following:
"Thaks fo your message. I was nt able to take the call at th time buI will be avaiable after 6pm. Thanks again!"
This is really annoying. It ONLY happens in the messaging application. I can type an entire document in Word without a single problem but I correct numerous mistakes in emails and text messages in order to avoid looking like a moron to recipients of my messages.
Is there anything I can do to correct this problem? I am using the Black Edition ROM right now and thought that this version fixed the problem. I also Experienced it with the LVSW versions and the other before that. I did not experience it in WM5 at all...
Click to expand...
Click to collapse
I have the exact error with all the WM6 roms, very very frustrating
I too sometimes get this problem, normally at the start of a text if I start typing quickly. it doesn't happen all the time tho only occasionally. using the lvsw rom at the moment but also had it with the SA WM5 rom
I've got this problem too, but in WM5.
same here on WMXL 0.2
I have noticed this on other WM5 devices but never on the Hermes until now. Is there something that changed in the messaging application that can be changed back to the way it was in WM5...hopefully via a registry edit?
pinhead said:
I have noticed this on other WM5 devices but never on the Hermes until now. Is there something that changed in the messaging application that can be changed back to the way it was in WM5...hopefully via a registry edit?
Click to expand...
Click to collapse
I had this problem but it went away after I selected the option to have word completion only select words after typing six letters. If you have it set to do it after pressing the space bar it seems to cause a delay in typing the text after a key press.
I agree with nmonger, I have alleviated the problem by setting the autocomplete to only suggest after 3 letters (it was set to "a space" before). Also I have made it only suggest 2 words (it was set to 4).
I had this from day 1, it`s just not designed to work that fast...
i hope it`s a driver problem and not keyboard hardware problem.
nmonger said:
I had this problem but it went away after I selected the option to have word completion only select words after typing six letters. If you have it set to do it after pressing the space bar it seems to cause a delay in typing the text after a key press.
Click to expand...
Click to collapse
So far this seems to have solved my problem. Thanks!
I knew it had something to do with the word completion. I set it to suggest 1 word but it keeps suggesting four. I just changed it to after 3 letters and solved my problem. Thank you for pointing that out. Now i don't look drunk when messaging at 11am!
Thank the man above someone else is having this issue as well....trying the word completion trick and seeing what happens.
worked for me - great solutions thanks
BINGO! an obvious solution in hindsight... thanks
cheers for that guys, it was one of those things that had bugged me for a while but not enough for me to look for a fix untill someone else mentioned it.
nmonger said:
I had this problem but it went away after I selected the option to have word completion only select words after typing six letters. If you have it set to do it after pressing the space bar it seems to cause a delay in typing the text after a key press.
Click to expand...
Click to collapse
Worked for me
I was just thinking about how often I had this issue today. I was SURE I was pressing all the keys. I tried turning word completion off and that didn't seem to change anything (strange). I'll give changing it to 6 a try, that makes sense.
I have noticed this problem on the Dash, Blackjack, Universal, and a few other Windows Mobile devices...all WM 5 and newer. This is the first time I have seen a solution. I don't think this worked on any of those devices and that is why I posted. I thought there was going to be a more complicated fix on this phone too!
What really stuns me is the lack of complaining about the skipping issue on other devices, such as those that I mentioned, as I am sure I am not the only one who sees this happening on multiple devices.
I thought it was all down to me being lazy, a bad speller and having thumbs too big for the small keyboard.
Trying the solution and all seems well so far.
thanks a lot, it's working
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
Why, using numeric tast, when i write a sms, very often, the bar space doesn't work. The text, infact, if i write quickly, is whithout spaces. Afhter touching the bar space, i can't touch immediatly the next letter, i have to wait almost one second.
Is it normal?
Thank You..
I had problems with keypad when composing text too. Sometimes the back space won't work. Sometimes, spacebar behaves out of order. And other frustrating weird stuffs.
I found a few ways to temporarily set it to work properly. To avoid the time-consuming soft reset. The solutions i came up with are not consistent. Sometimes you have to try more than one of the methods, or in combinations.
1. Close down some apps. Generally, i observed that if your remaining RAM falls below 80Mb, the chances of misbehaving keypad rises. Though not consistent. Just higher risk to go out of order. Use BattClock to monitor remaining RAM, and Task Manager to close down apps.
2. Go to Text Input settings, and remove garbage words from User Dictionary. They tend to pile up real quick. Most mistyped words are sucked in, and interpreted as user's custom words. The programming of this User Dictionary really suck. I clean it up daily.
3. Shutting down, and re-running HTC Messaging can sometimes help. Really weird.
4. Install and use CleanRAM.
These are temporary solutions. It doesn't work all the time. But do work most of the time. Reducing the frequency of your trips to the soft reset planet drastically.
We'll just have to live with it for now. Until someone at HTC decided to actually read our complaints for once and do something about it.
Maybe by the next decade.
Other than these 2 niggles, I gotta say my HD7 with Mango is near perfect...
As I said, niggles... Not complaints or faults...
1. To fully exit an app you hit the back button. To keep it live and available to be jumped back into you hit the home key... Only issue? If you want to fully exit an app, but the back key in the app has another fuction like web browsing, you sometimes have to hit the back key 10+ times to fully exit...
2. When the home screen is fully scrolled to the bottom, the people live tiles pictures resets blank...
Oh, wow, because you sure have to freaking close the apps all the time. Or people will see your midgets porn?
I have several flaws to blame. But making a topic cursing the OS because you need to close the apps and its dificult to press the back button, and worse, the "People live tile resets blank". Seriously?! Does that bother you so bad?
The guy is entitled to post his opinions
There's really no need to exit a program fully unless it's actually a program that runs in the background (which will use your battery correct?). Else, just leave the browser.
If you're really going to be anal about exiting the browser, just go the browser tabs and hit the X. Now if you hit back it'll exit...
Like he said
argentocruz said:
Not complaints or faults...
Click to expand...
Click to collapse
Just stuff that bothers him, we all have something...
Having to press back to close apps does annoy me a bit. I know i technically don't need to but personally I just like having a clean multi task menu.
OCD ? maybe... just personal preference and the guy and myself are entitled to opinions. No need to get so angry about it.
So far...I've yet to even bother closing the application.
I just keep pressing the HOME key and I rarely get any problems.
By the way, how do you get rid of the Music Menu once you've started it? For example, when I press the volume up, I see the music track there with pause, play, etc. I don't see the music app running in the multi-task menu.
Anyway to exit out of that?
mikeeam said:
I have several flaws to blame. But making a topic cursing the OS because you need to close the apps and its dificult to press the back button, and worse, the "People live tile resets blank". Seriously?! Does that bother you so bad?
Click to expand...
Click to collapse
No need to get so angry about it.
I find topics like this helpful for me making a decision of when is the right time to return to WP7. It may not be a bug (the back button) but it's good for me to know what to expect shoudl I return.
I wouldn't have thought having the browser left open would be an issue but thanks for highlighting the porn, that might cause an issue.
Things that really niggle with mango.
1. Pressing the unlock button and there being a delayed animation for alerts and the date to come up, this was not present in nodo and really annoys me.
2. The jump tiles for apps. I think it looks really ugly, maybe if they were filled in tiles rather then the outlines it my be more aesthetically. Personaly i liked the serach system in symbian s60 5th where it was a jump to but the jump to would dynamicly change as you spelt a name out.
I have a few annoyances.
1.) Can't navigate to previously opened pages after closing IE. The back button turns into closing the app instead of previous page.
2.) Now this one is HUGE for me. All number fields should show up in the predictive text or be flagged as textable. I have multiple contacts who have work cell phone's as well and multiple businesses where the number is a cellphone. It's extremely annoying when I start to type the name and i get no results.
Another example is with voice commands "Text Frank Smith" i get no option to text the Work cell phone even though our entire conversation thread is from his work number and there has never been a text sent or received from his Mobile number.
Other business contact with the Work number only have no option to text the contact. I either have to hit the plus sign and scroll down or go to the contact and scroll left to history and click one of the previous text's.
mikeeam said:
Oh, wow, because you sure have to freaking close the apps all the time. Or people will see your midgets porn?
I have several flaws to blame. But making a topic cursing the OS because you need to close the apps and its dificult to press the back button, and worse, the "People live tile resets blank". Seriously?! Does that bother you so bad?
Click to expand...
Click to collapse
Um. You know... there is this thing called Prozac. It worked wonders for me!
If you look at the topic: 2 mango niggles - Otherwise perfect. That hardly sound like a scathing criticism. Maybe you are being a little defensive?
Mango does have issues, but remember people use phones differently and never come across certain useability issues.
Yeah, it can bother, but would you create a topic to speak how bad is Mango because it resets the People Tile? I noticed it too, but it make your experience worse?
Apps in background DO NOT consume your battery. It's not in background in first place. It is "frozen" in memory. So there is no need to close (using the back button) the apps. Unless you really want to close for whatever reason.
Something that really bothers: not resuming app when opening toast notification. You just cant chat with someone else if not by MSN or Facebook, because it turns to be frustrating.
PoisonWolf said:
So far...I've yet to even bother closing the application.
I just keep pressing the HOME key and I rarely get any problems.
By the way, how do you get rid of the Music Menu once you've started it? For example, when I press the volume up, I see the music track there with pause, play, etc. I don't see the music app running in the multi-task menu.
Anyway to exit out of that?
Click to expand...
Click to collapse
Dont not either, I forgot and it was gone after a while.
hwalker84 said:
I have a few annoyances.
1.) Can't navigate to previously opened pages after closing IE. The back button turns into closing the app instead of previous page.
2.) Now this one is HUGE for me. All number fields should show up in the predictive text or be flagged as textable. I have multiple contacts who have work cell phone's as well and multiple businesses where the number is a cellphone. It's extremely annoying when I start to type the name and i get no results.
Another example is with voice commands "Text Frank Smith" i get no option to text the Work cell phone even though our entire conversation thread is from his work number and there has never been a text sent or received from his Mobile number.
Other business contact with the Work number only have no option to text the contact. I either have to hit the plus sign and scroll down or go to the contact and scroll left to history and click one of the previous text's.
Click to expand...
Click to collapse
To MS, it's non sense to people have two cell phones. This is really annoying, but of course it's not worse than the cursed people live tile.
mikeeam said:
But making a topic cursing the OS because you need to close the apps and its dificult to press the back button, and worse, the "People live tile resets blank". Seriously?! Does that bother you so bad?
Click to expand...
Click to collapse
Sorry if it looks like I'm cursing the OS, but I'm not... I love it and have been a 'died in the wool' windows mobile man since day one... But I'm a virgo and if I painted a house to perfection, but missed one square inch, I would be able to not focus on that one tiny bit... It's just me...
Freypal said:
Having to press back to close apps does annoy me a bit. I know i technically don't need to but personally I just like having a clean multi task menu.
OCD ? maybe... just personal preference and the guy and myself are entitled to opinions. No need to get so angry about it.
Click to expand...
Click to collapse
That's me for sure... I only leave something available to jump back to if I know I'm going to be needing it in that same day, else, I fully exit...
Perhaps I should experiment one day and not close a thing and just try and get comfortable with it...
mikeeam said:
Apps in background DO NOT consume your battery. It's not in background in first place. It is "frozen" in memory. So there is no need to close (using the back button) the apps. Unless you really want to close for whatever reason.
Click to expand...
Click to collapse
There is a very valid reason to want to close apps using the back button. If you don't close them that way, they consume one of the (arbitrarily limited) 5 cards in the app switcher. If an app is one that you know you won't need to go back to any time soon, it makes no sense to waste a card on it, especially since Microsoft decided that we didn't need the ability to remove cards from the switcher.
leftspeaker2000 said:
Things that really niggle with mango.
1. Pressing the unlock button and there being a delayed animation for alerts and the date to come up, this was not present in nodo and really annoys me.
Click to expand...
Click to collapse
When I updated to Mango, I had this problem. For another reason I hard-reset my phone and this bug has disappeared now for me.
---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------
argentocruz said:
Sorry if it looks like I'm cursing the OS, but I'm not... I love it and have been a 'died in the wool' windows mobile man since day one... But I'm a virgo and if I painted a house to perfection, but missed one square inch, I would be able to not focus on that one tiny bit... It's just me...
That's me for sure... I only leave something available to jump back to if I know I'm going to be needing it in that same day, else, I fully exit...
Perhaps I should experiment one day and not close a thing and just try and get comfortable with it...
Click to expand...
Click to collapse
Exactly that. If there are 2 or 3 apps i'm using at once i like to have a clean multi-task card to switch between. Once i'm done i close them all.
mikeeam said:
Yeah, it can bother, but would you create a topic to speak how bad is Mango because it resets the People Tile? I noticed it too, but it make your experience worse?
Apps in background DO NOT consume your battery. It's not in background in first place. It is "frozen" in memory. So there is no need to close (using the back button) the apps. Unless you really want to close for whatever reason.
Something that really bothers: not resuming app when opening toast notification. You just cant chat with someone else if not by MSN or Facebook, because it turns to be frustrating.
Dont not either, I forgot and it was gone after a while.
To MS, it's non sense to people have two cell phones. This is really annoying, but of course it's not worse than the cursed people live tile.
Click to expand...
Click to collapse
I created a feature suggestion http://windowsphone.uservoice.com/f...344390-work-number-should-be-a-textable-field
PoisonWolf said:
So far...I've yet to even bother closing the application.
I just keep pressing the HOME key and I rarely get any problems.
By the way, how do you get rid of the Music Menu once you've started it? For example, when I press the volume up, I see the music track there with pause, play, etc. I don't see the music app running in the multi-task menu.
Anyway to exit out of that?
Click to expand...
Click to collapse
Play a video, and back-out of the player. Then the player controls are gone from the screen when you press volume keys.
So I'm working on an app, which involves the users doing various non-safe things. Things involving root, and filesystems. Considering someone with a less-than-average IQ enters the userbase, I need to make it absolutely 100% clear this is a dangerous action with kitten-killing consequences.
I was hoping to get some input on how to accomplish this. So far I have considered the following options:
1) Time-based confirmation: Anyone who did rm -rf <folder> on zsh would know this. Basically, first prompt for confirmation, then when they give it to you, wait a few seconds, all the while showing a large cancel button, and when the time is over, you display a relatively small button, with the confirmation. This button also expires (i.e we assume it was canceled) when the user either waits more than a few seconds, moves to another activity, puts the phone to sleep or goes to another app/home screen.
Advantages I see:
Pretty simple to understand for the user
Relatively difficult to butt-press
Disadvantages I see:
Painful for repeat-actions
Not impossible to butt-press
2) iPhone style swipe-to-confirm: Pretty much describes it, and this is already used by TWRP for some things.
Advantages:
Absolutely impossible to butt-press
Doesn't take very long if certain
Disadvantages:
May not make it very clear that there is danger
Might trigger a positive sentiment when an ex-iPhone user uses it, which may increese the risk of accidental use
3) Github-style type-blah-here: Basically display the name of the filesystem (or a captcha, but we are not cruel), and ask user to type it in.
Advantages:
Non-butt-pressable
Very clear message
In some cases, it may alert the user when they are performing on the wrong entity (e.g deleting wrong file)
Disadvantages:
Takes a little while, pain on multiple uses.
Please mention your preferred one, and other suggestions of you have any.
Thanks!
Also, that alliteration in the title would make my English teacher proud.
Show the warning in big bold red capital letters. Tell them there's no going back. Then if there is a confirmation dialog then put a checkbox in it as well which needs to be ticked. That would be enough. But keep in mind that sometimes when using a ****ty cable the device registers the touches on random areas, so double confirmation would be reasonable.
Think of it like the person will sue you for loss of data; Would you be able to justify yourself? If yes, then the warning is enough.