Related
Just discovered a very annoying bug with this new OTA update. I've had it for about an hour, and everything else has been good except for this.
With the lockscreen, my first shortcut icon (Phone Dialer) suddenly disappeared. I have no clue how to get it back.
When I try to re-assign it as a shortcut, it doesn't appear on the shortcuts menu.
I'm 1,000% positive that I did not erase the dialer icon in the lockscreen edit menu.
Anyways, this is just a heads up for some of you TmoUSA people who just got the OTA update.
And if anybody has any suggestions on how to prevent/fix this, or get back my phone dialer shortcut, I'd really appreciate it.
I got the phone dialer and it did not disappear from lock screen after the update.
I think this may be an isolated incident. But wow none the less. I would suggest a wipe brother.
Wow, that sucks to know that it's just me
Not that I would wish this problem on any of you, just kinda bothers me because I factory-resetted just yesterday
It's not just you. I still have the phone on my first button of the lock screen, but if I go to edit the lockscreen buttons, the first one is now blank, and Phone is not an option in the list of available apps to assign.
As long as I don't change it, it's good...
The EVO 3D had this problem with 2.3.3 at launch. HTC sent out a minor update to fix. Expect a minor update in the near future.
I wonder if I should just install a phone dialer app from the market and see if that can be a workaround.
What do you guys think?
LPChris47 said:
I wonder if I should just install a phone dialer app from the market and see if that can be a workaround.
What do you guys think?
Click to expand...
Click to collapse
I had this issue, and I made a workaround, see here: http://forum.xda-developers.com/showthread.php?t=1205384
I have phone as my 2nd shortcut and its still there, and it works.
But the 2nd shortcut is blank in the shortcut assign menu.
*my phone is totally out of box stock
new tmo update
has anyone did the tmo update with s-off yet? dit it work? is it worth my while
Wrong thread to ask that, bro. Take it to the Q&A forum
AudiHeel said:
I have phone as my 2nd shortcut and its still there, and it works.
But the 2nd shortcut is blank in the shortcut assign menu.
*my phone is totally out of box stock
Click to expand...
Click to collapse
If you save any changes from that screen you'll lose the icon.
Really, yikes. I think I like the 4 I have there now so I'll leave it alone for the time being.
1st - Web
2nd - Phone
3rd - Gmail
4th - Messages
With all these issues I'm seeing I think ima just stick to leedroid or stock rooted. I'm playing around on my myTouch before I sale it.
Sent from my myTouch_4G_Slide using XDA Premium App
I just got the update and yes, while I still have the Phone icon on my lockscreen, if I go to the Settings page for the screen the position is blank and "Phone" isn't an option in the list of programs to launch.
It looks like birgertime's work-around may be what you need, until HTC (hopefully) releases a fix for this.
In the mean time, I'm not going to change my lockscreen icons (not that I frequently do anyway).
Not just you. Same thing happened to me. Just got the update today.
birgertime said:
I had this issue, and I made a workaround, see here: http://forum.xda-developers.com/showthread.php?t=1205384
Click to expand...
Click to collapse
i had the same issue, the phone (dialer) missing from menu and lock screen. I downloaded the shortcut from the link above and it worked. Thanx for the shortcut.
I just got the update and I don't have any issues with my lock screen. maybe try to change in your lock screen htc gives us like 6 to choose from 'm using the 1 that shows status updates from facebook and such.
also my wifi is working a lot better I still lose signal when I grip it in landscape mode but it doesn't lose signal completely and I can still use wi-fi even in landscape mode holding it with both hands
The workaround works great! Thanks for the help, everybody.
I was just reading this thread when I noticed that I had the same bug after changing the lockscreen icons. Will flashing a ROM over the update help?
Hi,
Since two days I'm a happy and proud Note owner, but there's one thing, that makes me really go crazy:
I installed the program "Widgetlocker", because the standard lockscreen is quite broing. It actually works quite good, but sometimes the standard lockscreen still apears. Not instead of the widgetlocker, but additional. So I always have to unlock two lockscreens.
Does anybody else has got this problem? And how can I fix it?
I tried to find a solution in different forums and in the program configuration, without sucess!
Thanks for help!
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....
I turned on root helper and home helper in settings, that fixed it for me. I'm on Stock Rooted XXKK9 if that helps.
Sent from my GT-N7000 using xda premium
I presume you have set the lock screen to "none" in the actual phone settings too?
NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Where? Can't find any option like that....
Thanks for help
Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App
NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Lol, i accidentaly hit the thanks button. You're welcome!
Sent from my HTC Desire HD using xda premium
drjp77 said:
Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
My widgetlocker works fine. Been using it since day 1. Hmm.. Sorry. Not sure how to help.
chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close
The_Steph said:
chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close
Click to expand...
Click to collapse
Thanks @ everybody for the help, but unhappily it's still not working properly.
The problem always apperas, when the phone's sleeping and a gTalk message comes in.... but ONLY, when the gTalk ppop-up is activated......
Any (more) idea?
you are leaving it running all the time aren't you?
I use to have the same problem, very rarely but it was still annoying. I have put a lock on widgetlocker so if I ever close all programs, widgetlocker is still running. It's not happened since but it's only been a few days so I'll see.
chrcad said:
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....
Click to expand...
Click to collapse
Some pop-ups cause this if they're designed to appear underneath the stock lockscreen rather than dismiss it.
For now:
1) Easy Wake Mode disables the system lockscreen
2) WL Settings > Long-press volume down for Experimental > Aggressive Dismiss stock lockscreen. This should work, but it's not well tested yet so it's off by default.
This is an Alpha test build of CleanROM with CoreDroid Suite Tools by Sergio76; to be known as CleanTOOLS.
Test is closed! I appreciate all the help given from everyone willing to take there time to test this out on a busy Monday morning!
Reported issues
HW Buttons will not remap to "Menu"
When selecting any of the settings under the capacitive button mods for lighting duration / brightness nothing changes.
Wow, so many updates today. AOKP, Xi40, and now this. Thanks for the hardwork man and inducing my flashaholic self.
download started!
screenie coming...this looks like my desire HD but on crack. Gonna a be a great week for the One X.
Sent from my HTC One XL using Tapatalk 2
Thanks guys.
Its not fully done and I just need to see where the bugs are. Hopefully we can get some good testing and then on to the next build.
Expect issues.
Downloading now. Will report back sir.
Sent from my One X using xda premium
Should fastboot be disabled and is this de-odex?
Will give this a flash soon as I get home Scott been using your rom as a daily driver since I got my hox
Will post any bugs, fcs or reboots if I find any
And happy you stayed on xda your one of the best devs in my opinion
Downloading now, looks great.
Will report any issues.
Rom is very smooth. Currently i am testing the clean tools and few things dont work .
Mapping the recent apps button to menu doesnt work
And disabling the 3dot menu doesnt work . It just keeps coming ...
I will keep testing
Sent from my Transformer Prime TF201 using xda premium
Still trying to get a menu button, the hardware key settings in clean tools seems to be fouled. Set menu to long press home it works, three dot menu still present in apps however, custom text on lock screen doesn't work, loop scroll home pages doesn't work, custom background image quick settings doesn't work.
Will test more tom.
Sent from my HTC One X using Tapatalk 2
I can also confirm the remapping issue with the "recent apps" hw button.
Any chance to add in the app drawer dimensions as a choice?
This is looking really good, I've been waiting for a new cleanrom to come out, thanks for all the work!
Flashed and testing.
1) Battery percent icon, numbers could be thicker like the 4.1 SE battery. Hard to read.
2) Hide operator name in status bar all the time as an option would be nice, not just lockscreen.
3) Set Recent apps button to Menu. Doesn't do anything. Set long press to Menu also does nothing.
4) Would like to change the app drawer. I like more items, but some might like 4x5 or whatever instead, like stock.
Did some other settings, like no animation on unlock, quick settings as recent with no current alerts and other options, seems to be working.
That is just what I found off the bat.
Will report back with more.
Otherwise, I really like where this is heading!!!
scrosler said:
Known issues:
Flashing this ROM could perma-brick your device!
Click to expand...
Click to collapse
..and destroy your entire life! hahah nice
pantmunu said:
Rom is very smooth. Currently i am testing the clean tools and few things dont work .
Mapping the recent apps button to menu doesnt work
And disabling the 3dot menu doesnt work . It just keeps coming ...
I will keep testing
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
eraste said:
Still trying to get a menu button, the hardware key settings in clean tools seems to be fouled. Set menu to long press home it works, three dot menu still present in apps however, custom text on lock screen doesn't work, loop scroll home pages doesn't work, custom background image quick settings doesn't work.
Will test more tom.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
uiskibum said:
I can also confirm the remapping issue with the "recent apps" hw button.
Any chance to add in the app drawer dimensions as a choice?
This is looking really good, I've been waiting for a new cleanrom to come out, thanks for all the work!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Its just finicky to say the least. But it does appear the Menu option will not work at this time but the other options do seem to be working.
Keep the bugs coming.
It would appear from the screen caps that this is using the stock ICS multitasking. Does that mean it's fixed???!!!???
captiva button mods dont seem to be working ( unless a reboot is required after selecting something ) although no pop up shows stating this.
pearlbrian said:
It would appear from the screen caps that this is using the stock ICS multitasking. Does that mean it's fixed???!!!???
Click to expand...
Click to collapse
It was never broke.
eraste said:
captiva button mods dont seem to be working ( unless a reboot is required after selecting something ) although no pop up shows stating this.
Click to expand...
Click to collapse
Could you be more specific please?
scrosler said:
Could you be more specific please?
Click to expand...
Click to collapse
when selecting any of the settings under the captiva button mods nothing changes, If you select off they remain lit, etc. Tried without and with a reboot after selecting each setting.
Based on this thread:
http://forum.xda-developers.com/lg-v10/help/knock-to-wake-t3239674
So far it's only a confirmed suspicion, but it's already happened to several people including myself. Accessing the hidden menu may break the knock on feature, even without doing any modification in it.
Possible Solutions:
-Hard Reset (100% working)
-Deleting Finger Prints (I've only seen this working on 1 person in another thread)
Please report if this has happened to you and if you've done something else to solve the issue. Thanks!
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Nope, doesn't break it. Been in the hidden menu to access Engineering Mode a bunch of times already and knock-on works fine.
Went in there to unlock the APN fields. Knock-on works fine.
Sent from my LG-H901 using XDA Free mobile app
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
toastido said:
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
Click to expand...
Click to collapse
Nope that didn't break it either
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
toastido said:
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
Click to expand...
Click to collapse
Obviously we need more data on this issue, there could be other variables in play as well but that's why we're raising the awareness of the knock on issue.
@toastido haha it's all good.
LancerV said:
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
sentry07 said:
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
Click to expand...
Click to collapse
Dial 277634#*#
I'm anxiously awaiting everyone now saying their knock on is broken ?
Didnt break mine! Thanks for the info to get into hidden menu though
nope mine still works but i do have issues with the screen in calls but thats it. but but was that way when i got it.
i think your hidden menu theory is good but my knock doesnt work but it stopped after i did a rest because the apn got messed up and it wouldnt let me add a new one. so i found this out this problem seams random as hell and if i turn knock pattern on to unlock the phone the knock works to turn the screen on but not off. i also noticed my second screen doesnt have the flash light on it when off anymore. so i will be doing a reset tomorrow unless anyone knows how to get the secound screen apps back when the screen is off. i think those apps are related to the tap on
It did break mine. Went to menu and hit apn unlock. No crash or anything. I noticed it not working immediatly. Knock code does still work.
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
joachim123 said:
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
Click to expand...
Click to collapse
mines the same no quick toggles
Mines the same no quick toggles but i found the answer with out rest on another post. i figured it out that its just something crashing the hidden menu doesnt matter what even force closing causes this problem. which is what i did seeing that the first time i used it nothing happened but the second time when the problem happened i cleared all apps and it stopped working. i'm guessing they disable it if something crashes it.
the knock on actually just gets turned off. Here's the quote for the answer make sure both knock on settings are on and it works instantly so no reboot needed.
-LBT- said:
Get yourself Quick Shortcut Maker, launch it, change the search type to 'Normal', search for 'Knock On', click on 'Settings', then on 'Try'. On the next screen, switch Knock On back and forth and see if that works.
Click to expand...
Click to collapse
clockcycle said:
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
Click to expand...
Click to collapse
you are a genius and life saver!!! thank you.
hidden menu did break it, confirmed.
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.