Have you ever experience your StarTrek go to restart mode with no reason for it...? I have found the cause is the "battery cover".
The gap between battery cover and the reset switch for the cover is too big, so any movement on battery cover could cause a soft reset because device think battery door was opened.
To solve the problem you only need to fill the gap between battery cover and the reset switch with a piece of plastic measuring 2.5mm x 4mm x 0.5mm, attached over the switch with a small piece of clear tape. (@3mm wide or less)
If you want to keep the switch working normally attach the "gap filler" only by one side, so if you remove the cover the switch will activate as usual and will turn off the device and enter it in restart mode.
Hope this simple solution will work to many others with this annoying problem!
For Soft Reset, some times is anoying keep pressing power button to turn off; and then again doing the same to turning on. Many people have found solution for that. For example look on this thread:
http://forum.xda-developers.com/showthread.php?t=427630
In my case I found another option, just make a shortcut for a reset or reboot application in the "Start Menu Programs". Thankfully few months ago I found in a friends smartphone the "reboot.exe" file, the right application I was looking for. To make it usable, only need to extract and copy the file to the "Windows" or "Program Files" folder on the device, make a shortcut for it on folder: "Windows\Start Menu\*.*", using a good file explorer, like Total Comander (available free from developer site: http://www.ghisler.com/smartphone.htm )
or via ActiveSync. Then you can find it on your "Start Menu Programs". It's verry simple!
I know this is not new news, but is another option availabe to choose...
Attached is the file needed: "reboot.exe" on a zip file. As explained, just extract and copy the application to the appropiate folder and make the shortcut...
Hope it work for many other the way it works for me... Best regards.
Mhhh, I didn't think this was news, I have been doing that for a long time now and I could swear there were already several threads on this.
But your are right, that pretty much fixes the reset switch which for me didn't cause soft resets but frequently caused the SD-card to be no longer recognized until the next reboot.
freibooter said:
Mhhh, I didn't think this was news, I have been doing that for a long time now and I could swear there were already several threads on this.
But your are right, that pretty much fixes the reset switch which for me didn't cause soft resets but frequently caused the SD-card to be no longer recognized until the next reboot.
Click to expand...
Click to collapse
Your experience is same as mine, sd card becomes'unavailable' until next reboot. However, I noticed that after some time the piece creates a depression which sort of worsens the problem.
sofene said:
Your experience is same as mine, sd card becomes'unavailable' until next reboot. However, I noticed that after some time the piece creates a depression which sort of worsens the problem.
Click to expand...
Click to collapse
Where does it create the 'depression'? I experimented with several materials and finally found something that works perfectly:
Do you know those little round felt-stickers that one can stick under furniture so they won't scratch ones parquet? I had some rather small and thin ones, cut a tiny piece out of one and it is now working perfectly without causing any kind of problems or further material deteoration for months on end ...
Soft Reset options...
Today was added some extra content. Look on first post...
Related
Hey everybody
I just expose my problem
1-the Folio 100 i bought is a new brand (received yesterday)
2-I turn on my Folio 100, just in beginning they is no light on the 4 buttons,
i wait android to boot and in the homescreen i try to use the 4 buttons, nothing happens, no light
3- i decide to install the Foliomod without wipe (because the home button like the 3 another button don't have any light, i try to press the buttons many time, still nothing)
4- I install foliomod successfully without wipe everything work better but still the problem of the 4 buttons (no light and don't work)
5- I install different recovery.img but impossible to use it, it's simple, when i press the power button, don't have any light on the 4 buttons, look like the 4 buttons are desactivate on boot mode or anything else
I was wondering if anyone have the same problem ?...
I battle with that, i try to do a reset mode with the button near the battery, get off the battery (power button hold like do a clear CMOS) still nothing
I'm tired to send the Folio back
I really want to fix it, they is no way to fix this problem ?
Thanks !
one thing i find pretty annoying is the fact that to press the buttons you have to make contact with your whole finger.
I dont mean to make presure, I mean to make contact with a large portion of skin than just taping the button.
I got my folio one week ago and I am still getting used to it.
Maybe you already tried to tap the buttons in several ways but... this is the only thing I can think of right now.
By the way... the default behavior es to have the lights off and to turn them on for a second when you tap the buttons.
I hope this helps...
Thanks but if you check what i said, i can't use the buttons.
Usually the home button you can use it on recovery mode but i can't do anything, it's like the 4 buttons don't exist, like desactived.
try to install folio widget and change the button sensitivity
roglio said:
try to install folio widget and change the button sensitivity
Click to expand...
Click to collapse
If the home button don't work on recovery mode, i don't think folio widget can help, foliomod 1.4/1.3 has already a folio widget and changing the value of the sensitivity didn't change anything
I think the problem is more on the boot of the folio, didn't activate the 4 buttons
Sinate said:
I think the problem is more on the boot of the folio, didn't activate the 4 buttons
Click to expand...
Click to collapse
its seen before... open folio and remove battery .. wait 20sec and reinsert and boot .. same can happen to sdcard slot and vol button etc.. very strange hardware we got..
Dexter_nlb said:
its seen before... open folio and remove battery .. wait 20sec and reinsert and boot .. same can happen to sdcard slot and vol button etc.. very strange hardware we got..
Click to expand...
Click to collapse
Like i said, i already do that i don't know what happen with this hardware, i start to regret.
If i can't fix, i will send back
Did you see the folio forum on the website toshiba was deleted ?...
Sinate said:
Did you see the folio forum on the website toshiba was deleted ?...
Click to expand...
Click to collapse
what a bummer.. (just saw it now)
does that say something about them and their next release..
i will NOT be supporting their next tab for sure!
Dexter_nlb said:
what a bummer.. (just saw it now)
does that say something about them and their next release..
i will NOT be supporting their next tab for sure!
Click to expand...
Click to collapse
When we press the power button have a small boot sequence, it's probably this boot sequence make many problem.
I try to erase the boot and change it on fastboot mode but it always fail.
Sinate said:
When we press the power button have a small boot sequence, it's probably this boot sequence make many problem.
I try to erase the boot and change it on fastboot mode but it always fail.
Click to expand...
Click to collapse
bootloader is closed source.. probably needs re-designed, and we havent seen any updates of it, since their update.zip probably cannot write a new one..
i think they forgot to add support for updating it..
just like the full wipe with power button, probably also a mistake..
That what i was thinking
Mistake to Mistake
This reminds me the TG01 (phone by toshiba, really suck)
Hi, I bought a crashed folio just to see inside it's guts and found that those bastard buttons are a board on its own.
I'm going to reverse engineer those signal and replace them with push buttons.
All these OEMs should learn that touch technology is only for the screen and nothing else!
roglio said:
All these OEMs should learn that touch technology is only for the screen and nothing else!
Click to expand...
Click to collapse
i think Google figured this out for us since they invented touch buttons somehow..
Unbelievable!
The chip on the capsense board is a PIC16F722 from MicroChip!!!
PIC16F722 <--- difficult to program and too much problem on it, they use this on clone phone in China.
I sent back my Folio, i don't know if i get a new one or wait for the XOOM or iPad 2 (but don't make any sens without USB/Thunderbolt, SD card etc)
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Having the same problem. Waiting to see others replies.
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages. Because if you put the phone in your pocket with the screen towards you body then it could be unlocking it when you get a text and the skin being close is keeping it awake. Specially if you have the glove feature turned on.
Sent from my SCH-I545 using Tapatalk 4 Beta
nativi said:
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages.
Click to expand...
Click to collapse
Good idea, but (heh) maybe I don't have enough friends but I don't get that many text messages. This happens frequently enough that I've spent a lot of time trying to figure out if some notification did something to wake up the screen, and most of the time I can find no reason for it to light up, which is why I suspect a button mash. (I also do not have the "extra sensitivity for gloved hands" option enabled.)
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Sent from my SAMSUNG-SGH-I337 using xda premium
ktetreault14 said:
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Click to expand...
Click to collapse
A reasonable suggestion. Might be the excuse I need to finally learn how to use Tasker. Wonder if I could get in a situation where I can't get my phone to wake up in a dark room, though....
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
oilfighter said:
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
Click to expand...
Click to collapse
I think this is the answer. I just got an Otterbox Defender and there's no way the buttons will get mashed in my pocket now. If the screen comes on again, I'll know there's something else causing it.
MysticCobra said:
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Click to expand...
Click to collapse
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
MysticCobra said:
Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen...
Click to expand...
Click to collapse
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
jbel25nyy said:
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
Click to expand...
Click to collapse
Great idea. That's why I posted about my Otterbox Defender in the reply right above yours.
Capp5050 said:
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
Click to expand...
Click to collapse
Good thoughts, but not exactly what I was looking for. These features might cause the screen to stay on once it awoke, but I was actually trying to prevent the screen from waking up in the first place.
I had the same thing happening to me until I put a case on the phone. I just have a hard silicone case, but the lip on the front it just enough to keep the home button from being pressed in my pocket.
I had a similar thing happening several times each day,except I would take my phone out to see that the camera was open. I figured out that it was because I had set a voice command to open the camera from the lock screen. I got rid of the command and it hasn't again
My problem is due to the intermittent wifi connection. My phone screen wakes up every time I get reconnected to the wifi network. It is so annoying.
Chris000001 said:
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
Click to expand...
Click to collapse
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Capp5050 said:
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Click to expand...
Click to collapse
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Capp5050 said:
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Click to expand...
Click to collapse
Im on a Verizon Note 3. I did as you described but it did not work. Im thinking it didnt because Root Explorer made a backup file with the non altered txt. Should I delete it to get it to work?
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.
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....