Develop Bugs

Can't lock phone / put in standby (solved!)

Hello all,
My phone is not working properly. I've had some bugs most people seem to be having, but now I have something which is quite annoying. I can't find it on these forums or anywhere on the internet.
I have seen a 1 line reference to my problem here:
/showthread.php?t=666332&highlight=standby
Flaws & annoyances with the HTC Desire (with workarounds!) [updated Apr 23, 2010
Hardware defects. Eg. Dust under screen, device not going into standby properly. Most of us don't experience these. Contact your retailer to exchange the unit or HTC to claim warranty.
So, I seem to have this problem. The phone wakes up with whatever button I press, and I don't have to unlock the phone. I have a unlock pattern set. It also doesn't ask me for this.
I couldn't find a proper topic about this problem, but I assume I'm not the only one. Is there a fix, or is it a hardware problem?
It wouldn't make sense to me if it's a hardware problem since the screen does turn off when I press the 'power' button.
Any info would be appreciated.
Thanks, Bart.

Which Lock?
are you using the built in lock or a third party lock app? I had the same problem when I used LockBot. If it's the standard lock, have you tried Powering the phone off then back on?

I am just using the built in application. I haven't used any other lock app.
I have tried turning the phone off twice, and both times it came back (might have been after charging it, but I don't know at all if that's the reason).
edit: I'm gonna try to recreate the problem with restarting and trying to find out when it stops working properly.
edit2: I restarted now... and it hadn't saved the new background I set... strange... :/
edit3: Ok, it still locks itself... I guess I'll just need to wait and see when it doesn't work anymore... maybe it's just a matter of time for it to stop working...

The problem that you quote in your opening post is probably the problem concerning the Desire (or rather an application running on the Desire) not properly releasing a wake lock which causes severe battery drain, e.g. the calendar app about which another thread exists.
Your problem seems to be quite strange. You do not happen to have an application called 'No lock' installed, right?

No, I don't have 'No lock' installed.
I use 2 calander widgets though... (the little one on my home screen, and an more advanced one on another screen.)
I've got quite some applications installed though... I'll just type them here, maybe someone can see something wrong...
Math Workout Lite
EStrongs File Explorer
Alarmering Droid
Groceo-NL
Q-Park parkeerfaciliteiten
ATM Locator NL
Text-To-Speech Extended
Google Translate
G-MoN for Android 2.x
Buienradar.nl v2
Gesture Search
Scoreboard
Listen
My Tracks
Air Horn!
Bonsai Blast
Star Wars Light Saber
Kaloer Clock - Night Clock
Coloroid
AudioManager Widget
IMDB Top 250
Pobs
Simply Cyanide
Voetbal nieuws
Barcode Scanner
Classic Simon
XDA-Developers
Backgrounds
SchottGunn
Shazam
Funny jokes
Ringtones
Google Maps
Google Goggles
I'm just trying some of the stuff of course... It's quite a long list...
Maybe Kaloer Clock brakes something?
I'll use it tonight again, going to sleep soon... Maybe it'll be broken again tomorow.
Lets hope it wont brake again... but that's probably too optimistic.

First off: sorry for the double post, but I have some new information which will also mean the end of this topic.
This morning it didn't work anymore, and the only application that did it's thing this night was the kaloer clock (night clock).
I looked at the settings, and there are some settings about screen lock.
It's not clear at all, but I changed some settings, and it locks again.
So, I guess it was just me using an app which I didn't fully understand. I'm glad you guys helped me though. And I'm definitely glad that my problem is solved!

Helicopter view problem

I don't know if anybody else is experiencing the same issue but my desire has this problem now and then. Sometimes when i move around htc sense and i will go to the helicopter view I don't see 7 home screens, just first one that is located in the top left hand corner.
When this occurs and will leave helicopter view mode my contacts widget is being funny and I can't select any contacts on it. Just Luke I said it doesn't happen very often, but still it occurs and its very frustrating. Is that ROM problem? After hard reset problem still exists.
After few minutes phone is working fine.
-------------------------------------
Sent via the XDA Tapatalk App

Had that happen once. A reset fixed it and I didn't get it again. I think it may have been one of the widgets I don't use anymore, maybe friend feed?

I've had this a few times. If I just put the phone on stand-by it seems to sort it.
I have a feeling it's the calendar widget that acts a bit funny on mine.

Widgets that I use:
1. Full screen calendar
2. Full screen mail
3. Full screen messages
4. Clock with weather + one line calendar widget + some program icons
5. Full screen contacts
6. 2 lines music player + one line power management + few programs
7. Full screen news
-------------------------------------
Sent via the XDA Tapatalk App

it is the calendar, there is somewhere another post here ...
just kill it with a taskmanager and it should work again.
btw: because the calendar is so sucky, i use now "Calendar Pad" ... actually i dropped all HTC widgets

I had this exact same problem, but did not know how to describe it.
When it happened, sometime, going into "all programs" it seems the phone tried to be in landscape mode.
I tried disabling some widget. After disabling the HTC Contact Widget, the problem never occured again.

Sometimes I get it. I just press standby then again and it fixes it.

I used to have this problem often but i havent seen it for a while now so i had forgotten about it. It may be the calendar widget like someone said, and come think of it, i havent had the problem since i moved my calendar widget to the homescreen on the far left. (used to have it just to the right of the main)

Widgetlocker Lockscreen Issue: Slider slow to respond. Help!

Hey guys,
I've been having issues with the Widgetlocker lockscreen recently, and was wondering if any of this will ring a bell with someone.
I recently flashed the KJ2 2.3.5 ROM (the XEU non-wipe Frankenstein one), and i've also flashed CF-Root and then the Speedmod kernel. I'm in the UK, on O2 (debranded to XEU) and i have no issues with the phone whatsoever. I even get great battery life. It's just this damn widgetlocker issue that's grating on me!
For some reason when i wake the phone up and try to unlock it by using the slider (i just use the default 'Android' one for unlocking - the only other things i have are a couple of widgets for missed calls & texts and a battery % one) a lot of the time the slider does not repond to touch. It doesn't always happen, but maybe a good one out of every three times it happens. And the weird part is, if i then just wait about 5 seconds, then it suddenly responds and i can unlock the phone. Obviously having another 5 seconds on top of the already present lag when pressing the home button is not good, and because of this i'm thinking of not using WL anymore.
I've been through all of the settings, i'm almost 100% sure it's not something in there. Can anyone help with this?
Cheers guys.

Happens with me too sometimes. Another issue is if you keep pressing Menu button 4-5 times the phone gets unlocked and takes you to the home screen.

Hey, just wanted to post that i finally figured out what the problem was.
I'm using an .apk to help with the touchscreen sensitivity. See vitalij's thread here:
http://forum.xda-developers.com/showthread.php?p=18999801#post18999801
Well it turns out on 2.3.5 vitalij's .apk has some issues with the most up-to-date superuser. The solution, so far, isn't great but gets the job done, is to uninstall the .apk, and then re-install. The important part is not to click on 'enable service' in the app! So basically each time you want to use the app you have to open it and hit 'apply' on whatever setting you need. The setting will work until you next turn the screen off. For me this workaround is actually ok, as the only time i ever really used it was for the odd game, so i'm happy to just do it manually on these occassions.

disable root helper

madrano, can you expand on what you mean by this? i have tried enabling & disabling root helper but if i remember correctly the problem was still there.

Keyboard does not type after unlock - Whatsapp

I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David

Dubadai said:
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Click to expand...
Click to collapse
Happens sometimes to me too and I am rooted on stock. Pretty sure it has nothing to do with us and everything to do with whatsapp having an ICS bug.
Sent from my Galaxy Nexus using Tapatalk

Whatsapp used to have exact same problem on my Nokia 5800XM too, I think it happens because of Whatsapp.

confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back

Confirmed bug for me too
Galaxy Nexus GSM
AOKP M4
Franco M2

To everyone who replied, thank you! Makes my life easier knowing its not ROM/Kernel etc...
Filed a complain to Whatsapp, such a great app apart from this bug!
Miasmic said:
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Click to expand...
Click to collapse
I usually press home button and then my Whatsapp icon on my main screen, usually goes fast, but still... rather annoying
How deep would this 'error' lie? Could devs fix it?

I get this exact same problem with Handcent! Currently using Swype, and like 30% of the time I will have to go back to the conversation list and re-select my conversation to start typing again.
Sent from my Galaxy Nexus using Tapatalk

Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp

ohh3nry said:
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
Click to expand...
Click to collapse
I am also using Nova, but I'm not sure why that would affect other apps like this.

Any solution to this problem?
Got the very same at my galaxy s6, too. Android 5.1.1

I'd also like to know if there's any workarounds for this. My wife's having the issue and she's blaming me. :silly:

I may have a workaround. I have the galaxy note 3 and i use a custom rom thats pretty much close to stock and I notice that if I lock the device and unlock shortly after, I can't type anywhere, on kik, what'sapp, gosms pro, even google search. So I've just decided to test things out and see what's going on and here is what I found....
Eventually I can type again if I simply wait, but no one likes to wait but this is the longest solution.
Clearing the RAM using built in cleaner or 3rd party memory cleaner seems to allow me to type again.
I didnt like playing the guessing game in knowing how long to wait before I can type again so in kik or go sms pro, I would type one of the native apps' emoticon and then hold the backspace button down until it erases it...then I knew it was ready to let me type again (I have haptic feedback on for keyboard presses so I can look away as I hold down the backspace button - this would let me know when it eventually erased due to the haptic feedback of the smiley getting deleted).
Since the issue occurred only after unlocking, I tried turning off the lock screen completely and turning off phone and back on again....keyboard types right away with no issues!
Its more secure to have a lock screen on the phone so turning off lock screen isn't the best option unless you're like me and are the only person at home with no worries of someone else taking your phone so I decided to try something else that seemed to solve the issue, and that is..............turning off "Multiple Widgets" in lock screen.....tested and worked! I can totally type again right away after unlocking the lockscreen shortly after locking it.
This is what worked for me and for you developers out there....if you can use this to pinpoint why this happens on android, perhaps you can use this information to rectify it.
Hope I helped!!!

List of bugs I have experienced

I've been using the OnePlus 3 for a couple days now and I have started to notice some bugs. I'm going to use this thread to document them and track whether or not they are fixed with updates. Unfortunately, bugs in Oxygen OS were the main reason I decided not to keep the OnePlus 2 last year, so hopefully I don't discover any more than I already have. These were all discovered in Oxygen OS 3.1.2, completely stock and not rooted.
1) If you open the dialer app, go to its settings, and select "Sounds and vibration", it kicks you back to the main part of the app instead of letting you change the sound and vibration settings.
2) This morning I woke up and noticed that my alarm didn't go off at 6 AM. When I looked at my phone, the time in the status bar showed 6:33, the time when I swiped down the notification shade showed 6:55, and my clock app (Google Clock) seemed to think it was about 5:37 based on telling me my 6 AM alarm would go off in 23 minutes. Three different times, WTF? I restarted the phone and now everything seems to be working correctly, but that was weird and disturbing.
3) When I turned on my bluetooth speaker this morning (Bose SoundLink Color), it kept telling me "OnePlus 3 connected" over and over about every 5 seconds until I started playing a podcast from the phone. The speaker has never done that with any other phone.

gtg465x said:
The time in the status bar showed 6:33, the time when I swiped down the notification shade showed 6:55, and my clock app (Google Clock) seemed to think it was about 5:37 based on telling me my 6 AM alarm would go off in 23 minutes.
Click to expand...
Click to collapse
That's very disturbing. It should literally never do that. Like it should have a dedicated clock circuit that would alarm even if your phone battery dies. My Sony Ericssons as far back as I can remember would turn themselves off from low battery and still come on to alarm.

Wow, that clock bug is a deal breaker.

Hmm, I wasn't sure if I slept through my first alarms or if there was an issue with the phone. That may explain it..

I tried to replicate #1 but could not. No issues for me.
Are you on 3.1.2?
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

#1 works for me too. I'm on 3.1.2.

Can anyone else confirm the clock bug? Mine hasn't arrived yet

martinezma99 said:
I tried to replicate #1 but could not. No issues for me.
Are you on 3.1.2?
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah. 3.1.2. I am using a custom ringtone that I moved over from another phone into the Ringtones folder, so maybe that's part of that one.

gtg465x said:
I've been using the OnePlus 3 for a couple days now and I have started to notice some bugs. I'm going to use this thread to document them and track whether or not they are fixed with updates. Unfortunately, bugs in Oxygen OS were the main reason I decided not to keep the OnePlus 2 last year, so hopefully I don't discover any more than I already have. These were all discovered in Oxygen OS 3.1.2, completely stock and not rooted.
1) If you open the dialer app, go to its settings, and select "Sounds and vibration", it kicks you back to the main part of the app instead of letting you change the sound and vibration settings.
2) This morning I woke up and noticed that my alarm didn't go off at 6 AM. When I looked at my phone, the time in the status bar showed 6:33, the time when I swiped down the notification shade showed 6:55, and my clock app (Google Clock) seemed to think it was about 5:37 based on telling me my 6 AM alarm would go off in 23 minutes. Three different times, WTF? I restarted the phone and now everything seems to be working correctly, but that was weird and disturbing.
3) When I turned on my bluetooth speaker this morning (Bose SoundLink Color), it kept telling me "OnePlus 3 connected" over and over about every 5 seconds until I started playing a podcast from the phone. The speaker has never done that with any other phone.
Click to expand...
Click to collapse
I can confirm the first bug
My alarm did go off this morning at 7am, when it should have done.
I'll test Bluetooth in my car - I've an FM transmitter.
Can we report these to OnePlus?

#1: no bug here

I've noticed the clock acting really strange, too!
Sent from my SM-N910U using Tapatalk

#1 (sound settings for phone) bug in 3.2.1
In phone just received -
Set a custom ring tone (mp3 file). Now can not go to settings "Sounds and vibration"
Kernel version from Jul 5th 2016
How to solve this?

#1 i have it too
#2 never had a problem with any build. I have had the device since June 30th.

1 can be solved by giving the phone app permissions to storage
Go to apps press the mechanic icon and go to access permissions, select storage turn on the switch for phone....

m_usmanayub said:
1 can be solved by giving the phone app permissions to storage
Go to apps press the mechanic icon and go to access permissions, select storage turn on the switch for phone....
Click to expand...
Click to collapse
Worked for me. Thanks.
Sent from my SM-T810 using XDA-Developers mobile app

I have none of those bugs reported above.
On OOS 3.2.1

Worked for me!
m_usmanayub said:
1 can be solved by giving the phone app permissions to storage
Go to apps press the mechanic icon and go to access permissions, select storage turn on the switch for phone....
Click to expand...
Click to collapse
Thanks very much.

I also could not replicate those bugs.

#1 : Same bug with my Oneplus 2