I notice that the double click of the power button still opens the camera in nougat and now there doesn't seem to be a way to switch it off. I've accidentally triggered this twice, hit home to close camera, then pressed the power button to switch off. Soon after on both occasions the phone has partially rebooted in my pocket, sticking on the Wiley fox boot logo.
Anybody else confirm this behaviour? Not something you do everyday I guess......
Hi Ratbags, I tried it for you... I never noticed that tapping the power button twice starts the camera, but indeed it does; however my phone didn't reboot (so it also didn't get stuck).
Hallo ratbags, i can confirm this behaviour in my Swift 2 Plus with Nougat Android. Noticed that randoms reboots some while ago and with your hint about power double click i am able to reproduce it.
To switch it off
Go to parameters
Use the search option and search gestures
Click on Gestures and then you'll find the option you are looking for
naegi said:
To switch it off
Go to parameters
Use the search option and search gestures
Click on Gestures and then you'll find the option you are looking for
Click to expand...
Click to collapse
Thanks for that. I believe Wiley fox are bringing out an update to fix this issue. Strange you can only get to that setting by searching or is it hidden away somewhere deep in a settings submenu?
ratbags said:
Thanks for that. I believe Wiley fox are bringing out an update to fix this issue. Strange you can only get to that setting by searching or is it hidden away somewhere deep in a settings submenu?
Click to expand...
Click to collapse
I didn't find it anywhere else so I think it's hidden
There's others hidden menu (and some are not even working at all - like battery percentage). I think that it's the trace of some modifications of parameters that weren't done correctly, or those parameters were disabled because the option didn't work well.
With latest update Build no. TOS118C the Gestures are available in Options Menu. The "not quite random reboot" seems to befixed too. Tested it several times and got no reboot since 3 hours.
Was just scanning the forum for any reports of random reboots as I've also been having reboots and it hanging on the white WileyFox logo screen.
Have noticed it more since the more recent official updates and have even gone so far as a full factory reset, however, I've had the issue reoccur several times since then (reset done earlier in week) so will be interesting to see if disabling that camera gesture will help
Beyond that I'm thinking possibly a corrupt or "worn" SD Card as I have a MicroSD card, used to extend the internal storage, that I think I used for a year or so in my previously Swift so possibly suffering some mild wear....
Related
Hi guys,
I finally installed Windows 7 bootcamp on my Mac, and went away on flashing kernel to XWKDD_insecure.tar, and rooting the S2 with S2 Root app. Everything went smoothly, and I now have TB Pro with a couple of apps frozen.
However, one very noticeable change after I flash and rooted was that my Applications button is very hard to activate. I thought I had imagined it, but when I unlock via Widgetlocker slider, and tap the Applications icon on the bottom right, nothing happens with the normal pressure I am used it. To activate it, I must push down with a little force for a second or two, let go, and it will go to the application folder. Also, I have also notice that when I wake the phone, the unlock widgetlocker slider is slightly unresponsive at first, I must also apply more force, hold it for a second, and slide for the slider to work. Before I rooted (6 hours ago), I can lightly tap the application icon, or light slide the unlock slider, and it would work.
Another weird thing is also buttons on the screen works fine thus far.
Anyone have this rather weird problem? I am slightly regretting rooting the phone, because the applications icon just wouldn't budge despite multiple taps... I've tried battery pulls, etc, but the problem persists, especially right after I unlock the phone.
Any input is much appreciated!
Thank you
Did you found a solution? I have the same problem, but I don't know if it's because rooting? This is really annoying.
Same here after CF-root.
and let me add that the return touch key (below the applications icon) isn't so responsive as before rooting!
I thought I was just imagining but I am "glad" you guys having the same problem.
Looking forward for a solution.
Maybe asking Chainfire ?
Well I just installed a stock rom, same thing.
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Am having the same issue with the back key and i am still stock non rooted
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
Non rooted you say, interesting...
I thought it is because I rooted it.
gil80 said:
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Click to expand...
Click to collapse
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
This is certainly not the first time I've heard about such complaints, infact a few friends also had this issue as well they had their phones replaced.
I recently got a strange touchscreen issue.
When the device comes out of deep sleep (turn on the screen with power button) my touchscreen behaves weird. Normally, when I touch the unlock slider, it follows my finger. But not now....it's like long press is not recognized. I am able to unlock the screen by wiping my finger to unlock. But the slider is not following my finger. The strange thing is, after about 10 seconds, the issue is gone, and the slider follows my finger....
Also long press on the homescreen is not working during the first 10 seconds.
What I tried to solve:
I completely wiped the phone and reinstalled .42 firmware. Then updated tot ICS using Sony Update Service and also completely wiped my phone. The problem still there...then I flashed a custom ROM (shardur_seth spacious...and also his firmware) but the problem stille there.
Anyone else experienced this? Or any solutions I could try? It was there suddenly....could it be a hardware problem? But why is it gone after 10 seconds?
Thnx for your help
it happens for me sometimes, but most of the time when someone calling me i cannot at slide to answer. what im doing is i just press power button ones and it will silence and press the home key and it will work the slide key...
any solution for this also?
mavado said:
I recently got a strange touchscreen issue.
When the device comes out of deep sleep (turn on the screen with power button) my touchscreen behaves weird. Normally, when I touch the unlock slider, it follows my finger. But not now....it's like long press is not recognized. I am able to unlock the screen by wiping my finger to unlock. But the slider is not following my finger. The strange thing is, after about 10 seconds, the issue is gone, and the slider follows my finger....
Also long press on the homescreen is not working during the first 10 seconds.
What I tried to solve:
I completely wiped the phone and reinstalled .42 firmware. Then updated tot ICS using Sony Update Service and also completely wiped my phone. The problem still there...then I flashed a custom ROM (shardur_seth spacious...and also his firmware) but the problem stille there.
Anyone else experienced this? Or any solutions I could try? It was there suddenly....could it be a hardware problem? But why is it gone after 10 seconds?
Thnx for your help
Click to expand...
Click to collapse
i face the same problem
my phone is in service center for repair
see the video below and check if ur problem is the same
Sounds like your phone is just sluggish, you're probably running too much in the background/have too much installed on the phone and it takes a while for the RAM to optimally load everything you need again after having cleared some of it whilst the phone was in sleep mode.
SCHUMI_4EVER said:
Sounds like your phone is just sluggish, you're probably running too much in the background/have too much installed on the phone and it takes a while for the RAM to optimally load everything you need again after having cleared some of it whilst the phone was in sleep mode.
Click to expand...
Click to collapse
i repaired my phone via SEUS but the problem usa still there
went to service centre ,they downgraded it to Gb the problem was still there!!!!
dhwanik said:
i face the same problem
my phone is in service center for repair
see the video below and check if ur problem is the same
Click to expand...
Click to collapse
Yes, that's exactly the problem.....I also have the problem that I cannot longpress the home screen...U have the same issue? After 10 seconds or after tapping the screen multiple times, the issue is gone until the phone goes to sleep.
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
mavado said:
Yes, that's exactly the problem.....I also have the problem that I cannot longpress the home screen...U have the same issue? After 10 seconds or after tapping the screen multiple times, the issue is gone until the phone goes to sleep.
Click to expand...
Click to collapse
yes i have the same issue we are not the only users who face this problem
there are many users who face this problem
arunsankar said:
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
Click to expand...
Click to collapse
i am on locked boot-loader so can't flash kernel
arunsankar said:
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
Click to expand...
Click to collapse
Tried using your settings..first I had governor set to performance...but the problem still persists. Wheneven I turn on the screen I have the issue. It is possible to unlock the screen if I wipe fast enough....but it really is strange...why is the issue gone after a couple of wipes or some touchscreen pressess..
Could it be a hardware error....a sensor not getting ready or something? But why is the problem gone when the screen is on for a while.....
mavado said:
Tried using your settings..first I had governor set to performance...but the problem still persists. Wheneven I turn on the screen I have the issue. It is possible to unlock the screen if I wipe fast enough....but it really is strange...why is the issue gone after a couple of wipes or some touchscreen pressess..
Could it be a hardware error....a sensor not getting ready or something? But why is the problem gone when the screen is on for a while.....
Click to expand...
Click to collapse
I have the same problem. Is there any solution?
Thank you for help.
same problem
Feri8850 said:
I have the same problem. Is there any solution?
Thank you for help.
Click to expand...
Click to collapse
me also having same problem and touch is awesome but when the lock is open then this problem will occur and it will open after 2 to 3 attempts..
what's this i think this is not an hardware problem this is only the software ??//??
i have the same problem too. i think there is a problem with cpu.
I had these sometimes with certain combinations of kernel and ROM. Actually it's gone... (Alliance V1/JJs Hybrid ROM 3.1)
I suppose it's a combination of hardware and software configuration...
Anyone tried to higher the minimum CPU speed?
Nachttier73 said:
I had these sometimes with certain combinations of kernel and ROM. Actually it's gone... (Alliance V1/JJs Hybrid ROM 3.1)
I suppose it's a combination of hardware and software configuration...
Anyone tried to higher the minimum CPU speed?
Click to expand...
Click to collapse
i tried. also i tried to set governor to different versions. and i tried nightelf rc5 kernel. nothing changed. problem still there.
today i realized that's not about only touchscreen. sometimes phone freezing.
problem with neo (mt15i) touch screen
use alliance night-elf v1.1 kernel.I had this problem but when I flash this kernel to my neo my touch screen works good same as the first day...
Well....for me suddenly the problem is solved!!!!
I'm very glad that my display is working again! It has been for about 3 months since I was facing the problem.
Unfortunately I do not have a clear solution to this, but I can explain what I did that day, and hopefully the solution is in there. But I can not garantee it.
What I did that day
1. I tried to get beats audio working, so I had installed a numerous of Beats libs. (see xda-developers for some of those libs). The last one I tried was Walkman port by ThilinaC. Not sure how this can be related to the display issue
2. I flashed a new rom. But this time I formatted /system and /data in CWM. Normally I just did a factory reset and installed the new rom. (but guess factory reset also formats /system and /data)
Still....guess this has nothing to do with the display
3. I did a offline charge. When my phone was empty I wanted to charge it fast. So I switched off my phone, and then connected the charger to offline charge the phone.
Really not sure how the above points could be a solution to de display failure, but guess if it was the digitizer that was the problem, it's strange that it is fixed out of knowhere....but the above actions are what I did that day....so maybe it's helpful and is the solution in there...maybe.
I'm glad the problem is gone
Yes, I am facing this exact problem, I am going to take my mobile to the service center !!!.
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
srdempster said:
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
Click to expand...
Click to collapse
My test device - that I picked up very cheep as it had been dropped and the SIM reader no longer works - displays the same issue, I had always assumed it was because of the fall it had.
Sorry if that doesn't help you
like this?
http://youtu.be/oyv5QmD5uQA
Exactly the same issue thanks
Same here but my phone is allways in case and i never dropped it. Oh and factory reset or flashing another ROM is not solution.
Any ideas?
I can only guess that either the RAM fills up with the screen off and once it starts to clear when the power button is pressed it suddenly can draw faster, or it's because the CPU and GPU clock down and slowly ramp up on wake. I'll change my performance settings see if that changes things?!
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
srdempster said:
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
Click to expand...
Click to collapse
So it's actually software problem right? Not damaged screen or something inside the phone.
Jecmenn said:
So it's actually software problem right? Not damaged screen or something inside the phone.
Click to expand...
Click to collapse
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
srdempster said:
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
Click to expand...
Click to collapse
mine is a hardware issue. you will see that it is currently on cm12 but it has done that on Stock, 4.4.x custom and 5.0 CM/AOSP as well. It will only do this if it hasn't be used for a few hours.
Since getting my Pixel 6 I've noticed that notifications, in every way are absolutely horrible on this phone. So far I'm chalking it up to Android 12 (which I hate the interface of BTW, I can't wait for a custom ROM to fix this mess that Google gave us). From low notification volume (even if the volume is turned up) to not receiving notifications, to the notifications not synching to my Fitbit (which I had 0 issues with on my ROM'ed OP6) I seem to have a lot of issues with this Pixel 6. It is not rooted, just some standard apps installed, including aodNotify.
Also, does anyone else have the issue of when you swipe up and hold to go to the recent apps, it just shows you a zoomed out home screen and you can't swipe right to see recent apps? So no way to switch between apps or close them...very annoying.
Anyone else having issues with not receiving notifications or texts at all? I just had my girlfriend tell me she sent me a message, but I never go it at all. It would have been a basic SMS from her iPhone, and we're both on Mint Mobile (T-Mobile MVNO) in a major city in the US with 5G.
Notification work fine.
I would first look at aolNotify which clearly effects the notification system and is in beta testing.
sic0048 said:
Notification work fine.
I would first look at aolNotify which clearly effects the notification system and is in beta testing.
Click to expand...
Click to collapse
I just uninstalled it, let's see if that helps, good call. I was just thinking if it's an aodNotify issue surely other people would be talking about it :\
I guess I'm just having a ton of different issues since being on this phone, that I'm eagerly awaiting TWRP and ROMs to come out.
Any news on TWRP? I had pretty much written it off, but I guess they are still working on getting A11 support. I think they had a working version for the Pixel 3a series that was released (beta testing) in the last month or two. I never bothered to try it because A12 was right around the corner.
Diablo2424 said:
Also, does anyone else have the issue of when you swipe up and hold to go to the recent apps, it just shows you a zoomed out home screen and you can't swipe right to see recent apps? So no way to switch between apps or close them...very annoying.
Click to expand...
Click to collapse
I have this issue happen occasionally, both before and after installing aodNotify app. I'm using the buttons though, not gestures. Very weird.
Diablo2424 said:
Also, does anyone else have the issue of when you swipe up and hold to go to the recent apps, it just shows you a zoomed out home screen and you can't swipe right to see recent apps? So no way to switch between apps or close them...very annoying.
Click to expand...
Click to collapse
KindofBlues71 said:
I have this issue happen occasionally, both before and after installing aodNotify app. I'm using the buttons though, not gestures. Very weird.
Click to expand...
Click to collapse
Same here using the navbar but it only happens every once in a while, no idea why.
I find notifications to be very low indeed and some of them (like email) are delayed. Not sure if we should blame this horrible A12 (yes I also absolutely HATE it) or the device
sic0048 said:
Any news on TWRP? I had pretty much written it off, but I guess they are still working on getting A11 support. I think they had a working version for the Pixel 3a series that was released (beta testing) in the last month or two. I never bothered to try it because A12 was right around the corner.
Click to expand...
Click to collapse
No news as of yet, that I know of. But now that there's a working root and the firmware and kernel is released, I would imagine it is being worked on, or at least I hope it is. Just as custom ROMs, as I am hoping to run Lineage or CalyxOS once available.
KindofBlues71 said:
I have this issue happen occasionally, both before and after installing aodNotify app. I'm using the buttons though, not gestures. Very weird.
Click to expand...
Click to collapse
Good to know it's less common using navigation buttons. I just switched back from gesture (I was trying to get used to it and adopt the new way of life lol, but guess not - back to the same old buttons it is!) and I have already noticed that the recent app menu has been working much better.
Nimueh said:
Same here using the navbar but it only happens every once in a while, no idea why.
I find notifications to be very low indeed and some of them (like email) are delayed. Not sure if we should blame this horrible A12 (yes I also absolutely HATE it) or the device
Click to expand...
Click to collapse
Yes, notifications have also been delayed at times as well I've noticed. I doubt it's the device, as hardware is hardware, and apps open/close quick and smoothly, browsing the web is no issue, as is scrolling on apps like Instagram in my experience. Though with this being the only phone (P6/P6P) with A12 so far, I guess time will tell if it's a device issue or Android issue. I still feel like it's a P6 ROM issue, and hopefully ROMs will come soon to resolve issues like this.
Just as an update, since uninstalling aodNotify and switching to navigation buttons instead of gestures my notifications have been better and my recents list showing has been more reliable. It's still a bit laggy when loading recent apps, but at least it's working more often now
One weird thing I've noticed with the notifications is when I swipe down on the status bar and tap the triangle to expand the notification, the window stays small but I can scroll the entire notification within it. I'll try to get a screenshot the next time it happens.
That's not normal and not what I am experiencing. A reboot doesn't clear it up? If not. it may be that you'll need to do a factory reset just to clear out whatever the issue is.
Ugh, I hope I don't need a factory reset. I had enough trouble getting my eSIM setup on Fi already. I haven't experienced the notification issue again, so fingers crossed, wood knocked, etc.
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Nimueh said:
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Click to expand...
Click to collapse
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Lughnasadh said:
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Click to expand...
Click to collapse
No, Power Saving Mode is disabled and the battery wasn't low enough for it to even have kicked in. When it happened (twice!) yesterday the battery was 40-50% both times. Adaptive battery is disabled too so battery "shouldn't" be causing it in any way.
Thanks for replying though
Just a small update:
Oddly enough since I started this thread it hasn't happened again
I did sideload that mid-month update right around the same time of my post, maybe that fixed it ... no idea really, I'm just glad it's not happening any more