Evening all.
I'm hoping there's some developers out there that can give me some help.
I work in the telecoms industry and we send out field staff out in the middle of the night to some unsavoury locations. I am aware of staff being robbed, beaten up, even once a long time ago a farmer pointed a shot gun at one of our techs!!!!!
I'm trying to write an "Emergency Beacon" app in c# that when a hardware key is pressed (probably nav wheel) 5 times within 5 seconds it'll wake the device and run the program. Vibrate once to alert the tech it's been activated, enable the GPS, read the CGI (Cell ID) from the RIL, and then send a SMS detailing the Tech needs urgent help at GPS lat/long (if it gets a fix) and the (CGI) Cell ID, and do this every minute until its manually deactivated with a PIN code.
The idea is that if a tech gets in trouble, if he can get to his Kaiser, find the nav wheel, tap the button a few times, it'll vibrate and send the SMS, and he'll know help will be on its way without having to go through the "unlock", phone someone, where are you, don't know lark.
So far I've done the ... GPS, got the Cell ID and LAC, and got it sending the SMS every minute.
I can't for the life of me figure out how to wake the device from a hardware key and run a program. I've only been developing on WM6 in c# for 2 months!!!
I'm thinking along the lines of a Today screen plugin but I think they go to sleep in sleep mode.
Anyone any ideas??
Cheers
Phil
I think it'll be a killer application and of course I'll be publishing it here first!!
Can't help with this at all, but that sounds like an amazing idea.
*watches thread with interest*
Cheers .... It's going to be a while .. I'm flat out at work!
Hmm.. I have zero development background on WM, but maybe a few cues...
In the settings you have a "Key Lock" control panel. In there, by default the hardware keys are deactivated when the device is in standby. By changing that you can enable the keys again.
After that, a press on any hardware key will wake up the device and do what it's supposed to.
So the waking up would be sorted. Now if you don't want the phone to wake up all the time and do random stuff in the pocket, I guess your program would have to put a kook to capture all the hardware keys, whenever it's running (all the time in the background).
When the device is on standby and a key is pressed, if it's not the intended one the device is put to sleep again. If it's the right one, start counting the presses.
When the device is on, if it's not the intended one, the key event is passed to system so it can be handled normally. If it's the panic key, start counting too so that operation is guaranteed also if the phone is already on.
Ahhh I see what your saying .... capture the keys and if it's not the right one put the device to sleep BEFORE it wakes up properly.
I think this would have to be done as otherwise all the keys other than the "power button" are ignored. I don't want to go down the power button route as it's a hard button to find .... the nav wheels dead easy.
I'm very new to WM too, Even though I've got pretty much a working application. How to get it working at the press of a button ... no idea (yet).
I "think" it's possible, If a "proper" developer wants to take the idea and create a working application I think we'll all be winners!
That would be an amazing app, im in the telecomms industry too and would be a nice tool to have. I wouldnt mind doing some testing on the app when you have a version ready.
Hope my code helped you get this going. I would like to see this working.
A good Idea would be to configure the button, if possible, that way if you port it to another device (say artemis) it would work without the jog wheel.
Drop us a PM if you need a hand with owt else
Ta
Dave
What you helped me with Dave was another part of the project ... your code allowed me to write the alarm function of my "Lone worker" Today screen plug-in which, IF the tech doesn't book off site it wakes up and beeps a lot ...
Sadly it's not an application that anyone one here would find useful UNLESS they work for a company with a SMS based Lone Worker system.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that's finished I can concentrate my efforts on the beacon app.... please note my C# WM development experience is a wopping 2.5 months!!
The ONLY and most probably difficult thing left to figure out is making an application launch at the repeated press of a button, even if the device is locked. Can't be that hard .... CAN IT??? LOL.
You could always write it Dave!!! *hint hint* And then you could sell it and make lots of money and buy a speed boat *.
* as long as I get a free copy!!
DRZ400 said:
What you helped me with Dave was another part of the project ... your code allowed me to write the alarm function of my "Lone worker" Today screen plug-in which, IF the tech doesn't book off site it wakes up and beeps a lot ...
Sadly it's not an application that anyone one here would find useful UNLESS they work for a company with a SMS based Lone Worker system.
Now that's finished I can concentrate my efforts on the beacon app.... please note my C# WM development experience is a wopping 2.5 months!!
The ONLY and most probably difficult thing left to figure out is making an application launch at the repeated press of a button, even if the device is locked. Can't be that hard .... CAN IT??? LOL.
You could always write it Dave!!! *hint hint* And then you could sell it and make lots of money and buy a speed boat *.
* as long as I get a free copy!!
Click to expand...
Click to collapse
Not enough hours in my day, I'm affraid
I work long hougs and don't normally get on my PC until gone 10pm.
Dave
I'll supply the Red Bull ... crack on!!
Dam .... looks like I'm REALLY going to have to give it a go.
DRZ400 said:
I'll supply the Red Bull ... crack on!!
Dam .... looks like I'm REALLY going to have to give it a go.
Click to expand...
Click to collapse
Quick help I can do, sitting down, designing and implmenting is the hard part.
Sorry.
Dave
Is this project over cant see any progress... or am i late?
DRZ400 said:
Evening all.
I'm hoping there's some developers out there that can give me some help.
I work in the telecoms industry and we send out field staff out in the middle of the night to some unsavoury locations. I am aware of staff being robbed, beaten up, even once a long time ago a farmer pointed a shot gun at one of our techs!!!!!
I'm trying to write an "Emergency Beacon" app in c# that when a hardware key is pressed (probably nav wheel) 5 times within 5 seconds it'll wake the device and run the program. Vibrate once to alert the tech it's been activated, enable the GPS, read the CGI (Cell ID) from the RIL, and then send a SMS detailing the Tech needs urgent help at GPS lat/long (if it gets a fix) and the (CGI) Cell ID, and do this every minute until its manually deactivated with a PIN code.
The idea is that if a tech gets in trouble, if he can get to his Kaiser, find the nav wheel, tap the button a few times, it'll vibrate and send the SMS, and he'll know help will be on its way without having to go through the "unlock", phone someone, where are you, don't know lark.
So far I've done the ... GPS, got the Cell ID and LAC, and got it sending the SMS every minute.
I can't for the life of me figure out how to wake the device from a hardware key and run a program. I've only been developing on WM6 in c# for 2 months!!!
I'm thinking along the lines of a Today screen plugin but I think they go to sleep in sleep mode.
Anyone any ideas??
Cheers
Phil
I think it'll be a killer application and of course I'll be publishing it here first!!
Click to expand...
Click to collapse
Related
I was looking this morning for a solution for those keys that would require a higher level of pressure in order for them to work (Hardware issue, not ROM-related), and all of them will point me to buy a new keyboard.
So after reading numerous threads I read this phrase "use it or lose it", and it gave me an idea... I decided to EXTRA-USE IT lol
Try this:
- open word or one-note or w/e and start pressing the key LIKE HELL (probably some dozen times), pretty fast, not so hard, repeatedly and without harming the phone (make sure you feel its reaching the "end").
- then press the key and move it in circles, like if you were rubbing it against the KB contacts.
If it works for you, you will see the results right away in the screen.
Ive tried this on two Tilts already and seems to work. I don't know if its a temporary fix or if its definite, I just know for sure it works in my case
My wild guess is that by doing this you clean the contacts of the aluminum pads, making them work properly. I live in a very humid country (about 90% RH) and next to the ocean, so I guess this would contribute more to the development of this failure.
*NOTE: Please if you have spilled anything over your phone, don't expect this to work as good as if u haven't
I had problems with my U and C key which it was a pain when entering a number u know U is 2 and well it made the whole experience longer and frustrating. after doing this trick (using a chopstick) my c and u keys work perfect... Now I can resume my mobile life... good luck to anyone else! and thanks Candanga!
Thanks for the trick! I'm going to try it if I have problems.
good fix man....i've got it to work with all of my keys EXCEPT for the down arrow/PgDn button....but i had been having problems with my u, p, i, s, and v keys, and using ur "fix" they work like new again.....
living in Louisiana, its probably also the humidity affecting my keys....thanks!
Good method -- thought I wander how long it will last
If your phone is out-of-warranty, and your feel adventurous (and want to run the risk of damaging the phone) you might consider taking the keyboard apart and carefully cleaning with some diluted isopropyl alcohol. This would likely give you a long-lasting result, though of course you risk damaging the phone, yada yada.
Another thing to consider is my patented what-the-hell-it-might-work method. WARNING I have not tried this on a Kaiser, it is based on something I did with an older device with a keyboard. (NEC MobilePro 780)
AS USUAL, DO AT YOUR OWN RISK
Turn the phone off by holding down the power button. remove the battery, sim card, storage card, etc. Put some DILUTED isopropyl alcohol in a small spray bottle, then spray it onto the keyboard. (I'd protect the screen and the rest of the phone as much as possible.) Let the alcohol pool up and get into the cracks of the keyboard. Wipe away the excess with a paper towel, then proceed to work each key much as described in previous post.
When you've had it, just let the phone sit for at least 24 hours so the alcohol evaporates completely. Replace the battery etc and see if it will start up, then test the keyboard
WARNING, the alcohol may damage the electronics, mar the finish of the plastic, etc. USE the 70% stuff, NOT the 90%
+1! Good advice. Worked for me.
it really works on my Australian TYTN II
bennyzhou said:
it really works on my Australian TYTN II
Click to expand...
Click to collapse
Confirmed on my Tilt I got from a San Francisco ATT store. Jeez. Nice.
I have always hated my G key. I use it plenty, but not often like an a or an e key, often enough that it's always on my mind, the anger that I will have to hit that stupid g key harder because it thinks it's special
No more. It works great. It's not special. I still hate it though, simply because I've always hated it.
Boycott G
Works great, thanks Candanga! My "s" key was not working unless I pressed it with force, now with your simple fix it's back to normal again.
PS. I too live in a humid environment.
Cleaning Keyboard on Kaiser
Well, this is my first post and hopes this help to the community that has problems while using the Keyboard.
This is my story. I bought a Tilt on ebay and after trying using it some keys did not work correctly. In order to use the keyboard I use a combination of the on screen keyboard and the keyboard. Then I ask myself, why am I doing this? Why am I needed to use a combination of the keyboard?
Time ago I work in a company that assembly Cellular, so I know the process and when a problem with the keyboard happen most of the time was because dust or fingerprint on the contacts while trying to assemble it.
What I did to solve the problem on my Kaiser was to do a deep clean of the keyboard. I follow the instruction of how to disassembly the phone [/URL]in order to take out the keyboard. Then I put the keyboard in an ultrasonic cleaner with alcohol for 10min. After that I reassembly the phone and try. But guess what, the keyboard gets worst, before that, there were a couple of keys that did not works but after clean it or try to clean it there were like 10 keys that did not work. Oh... dam it.
It could not be like this. I decide to give it a second chance to fix it but I did it in a different way.
The first thing I did was to remove the keypad. It was not so hard because the gum was kind of weak because the alcohol I use with the ultrasonic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second, I removed the contact pad with small tweezers being careful to not damage the contact pads.
After letting naked the keyboard I realized that the gum used to stick the contact pads were spread on the flex board and that was the reason of the hard keys or problematic keys.
Third, What I did was to clean the flex board and the contact pad perfectly with alcohol and swaps being careful of clean each contact.
Then I stick the contact pads again to the flex board and checking that it was aligned perfectly.
And last, Stick the keyboard.
Since 4 weeks I have been using the keyboard without problems.
My experience is that was not needed to disassemble the phone, just only disassembly the keyboard and clean the contacts.
Candanga said:
I was looking this morning for a solution for those keys that would require a higher level of pressure in order for them to work (Hardware issue, not ROM-related), and all of them will point me to buy a new keyboard.
So after reading numerous threads I read this phrase "use it or lose it", and it gave me an idea... I decided to EXTRA-USE IT lol
Try this:
- open word or one-note or w/e and start pressing the key LIKE HELL (probably some dozen times), pretty fast, not so hard, repeatedly and without harming the phone (make sure you feel its reaching the "end").
- then press the key and move it in circles, like if you were rubbing it against the KB contacts.
If it works for you, you will see the results right away in the screen.
Ive tried this on two Tilts already and seems to work. I don't know if its a temporary fix or if its definite, I just know for sure it works in my case
My wild guess is that by doing this you clean the contacts of the aluminum pads, making them work properly. I live in a very humid country (about 90% RH) and next to the ocean, so I guess this would contribute more to the development of this failure.
*NOTE: Please if you have spilled anything over your phone, don't expect this to work as good as if u haven't
Click to expand...
Click to collapse
worked for me
Maddening key press method works
My down arrow was not working. Searching on the web, I got a link for this and I pressed the keys two dozen times before it worked! Thanks!
totally works as advertised!
I used the eraser-end of a pencil to do the pushing, and the results are fantastic!
So, I was just using my Diamond to take a photo. After taking the photo, I went to take another and it said "Could not initialize camera" or something like that. I reset the phone using ResetManager, but when it came back on, the screen was not displaying anything and none of the LED's are working.
Now, the phone is working, but I can't see anything! I know it's working, because when it turns on, it vibrates, and if I plug it into my computer, it functions as a USB drive (I can see files on it).
Why is my screen suddenly not working? I tried removing the battery and putting it back in, didn't help. I tried holding the red reset button, didn't help.
Any ideas?
I'm using the most recent version of Dutty's rom (ignore what my sig says).
...quick update:
just reset tried to do a hard reset on the phone (hard to do since i can't even see anything on the screen) and turned it on.
when it came on, the LCD is working, but there is no backlight. there is a message saying something like "microp version mismatch 0" then "please upgrade latest microp firmware"
after that, it goes to the normal touchflo home screen, but there is no backlight.
i am going to try to load the latest (v3.4) version of dutty's rom to see if that works. if not, what should i do?
ok just got off the phone from someone at HTC USA support (866-449-8358).
he had no idea what the problem was. had me to a reset though the settings (clear device storage)
phone turned back on. still no backlight after completing all the steps.
then he transferred me to the "repairs" department. the guy there told me that he only deals with hardware repairs.
the repair dept told me that they didn't know what to do either, and told me to ask on www.htcwiki.com
apparently no one at HTC USA (or at least, no one i've talked to) knows about this problem.
ugh now what do i do?
What happens if you flash it with the latest original rom just to test???
owziee said:
What happens if you flash it with the latest original rom just to test???
Click to expand...
Click to collapse
haven't tried that because i don't have a copy of it...where can i download the latest official HTC rom?
at present, everything functions on the phone EXCEPT for the backlight & key LED's. the strange part is that the center (OK button) white LED does still work.
by the way, i got an email back from HTC tech support. here is what they said to do:
Thank you for your inquiry on your Touch Diamond.
I know how frustrating it can be to not have your device function the way it should. If you have any Third Paty Software on the device I would suggest removing that as a start. If that has no effect on the issue, we can hard reset the device. This will reinstall the operating system to the device and determine if it is software or hardware related. If this does not fix the issue, the device will need to be repaired.
Please follow the following steps to perform a factory default reset:
1. Press and hold both the Volume Down and OK keys (the bottom key on the left of the phone and the center, circular key on the face of the phone).
2. Insert the stylus tip into the reset hole at the entrance of the stylus holding slot (as if you were doing a regular soft reset). Once the screen goes blank release the stylus.
3. When a prompt on the screen appears asking if you wish to clear all data on the device, press the Volume Up key as indicated by the prompt.
4. Allow the device a couple of minutes to fully restart and let all device customizations finish before touching any button or tapping on the screen.
HTC Repair’s number is 1-888-617-1113. The hours of operation for HTC Repair is Monday through Friday 8 AM – 8 PM EST.
I hope we have answered your question in detail. Feel free to contact us again if you have any further questions.
HTC Technical Support
http://www.america.htc.com
http://www.htcwiki.com
Click to expand...
Click to collapse
no one has a solution to this problem? am i the only one who is having the microp firmware error and a non-functioning backlight?
tell you what. i'll offer $40 via paypal to whoever can give me (correct, working) info to fix the microp firmware error.
I had the same problem you had. It had been going on for a couple of months. Screen which stayed black after ending a call or after some time of inactivity it also stayed black after pressing the power button. When I soft resetted my diamond it vibrated, but the htc startup animation didn't show up, also after several soft resets.
I got my diamond only working by taking out the battery. Sometimes even when I put in the battery in after some seconds, it still remained black when I turned it on. Most of the times I had to take out the battery and leave it out for some minutes. After 5 or 10 minutes I put it in and it started the normal way. But after half a day or so I got the black screen again and had to remove the battery again.
I use original Dutch stock rom 1.93 with some tweaks. Nothing special or so....I managed to install a remote control utility so I could see the screen on my laptop. One day I got the exact same error you had. So I called HTC support in The Netherlands. They sent me an email with an UPS receipt so I could send it to EuroTwice, which takes care of the repairs for The Netherlands and Belgium. I could track the repair online and noticed that they couldn't find any error. I got my diamond back last week and when I turned it on, guess what....the screen remaind black. It did vibrate when booting, but the HTC startup logo didn't show up again. The repair ticket (the paper one I got with my diamond when I got it back) also mentioned that they couldn't find any error whatsoever and that they hadn't modified a thing on my device. Bad ****.
I then remembered that I had an extra insurance/warrenty I bought that together with my diamond, just in case. I went back to the store (something I should have done much earlier) and they tested it again, but because of the extra insurance/warrenty I got a brand new diamond. This one works perfectly. Tweaked it again and my screen doesn't turn black anymore. Haven't soft resetted my device in 4 days now.
So I should suggest to go back to the store and demand a new one.
I attaced the screenshot of the error I had...Btw...I bought my device on july 27 this year and got an new device last week. Normally you can get a new device here when the product doesn't work as it should within 3 days or something. It's worth a shot....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wow long story. so i guess i'm #$^$ed at this point.
i can't believe no one knows how to fix this, when it's obvious some sort of software/firmware error - not hardware.
i've offered a $40 reward for anyone who can fix this problem, but no bites so far.
i bought my diamond online back in june or july...i doubt the store will cover it with warranty. maybe i need a new phone
Maybe you can send the screenshot I made to HTC and ask them how to fix this. Or at least refer them to this thread. You said you bought it online. From a webshop or 2nd hand on ebay or something ? If you bought it in a webshop it's worth contacting them.
Furthermore I don't know how the legal stuff works in your country, but in The Netherlands we have a kind of protection for customers when it comes to products and their economic life. This means that for some devices the manufacturer has to repair it for free. For instance a washing machine or television. You can expect that it lasts for a minimum of 4 years. If it breaks down after one year or so, you can take it back to the store and they have to repair it. The vendor has to prove that you are to blame for the malfunction of the product, but in 99% of the cases they simply can't. Good luck with this matter.
http://www.htc.com/sea/CS_Mail.aspx
I'll pass on that screenshot...but who knows if it will help. HTC hasn't been too helpful so far...
anyone have any more info on how to maybe fix this?
anyone? anyone?
i'm still stuck with a phone that has NO BACKLIGHT!
i also just realized that the Wi-Fi is no longer working.
grrrrr....
ok $50 to whoever can fix the microp problem on my phone!
Have you installed the original rom yet?? By a full reset the original rom is not comming back only your duttys. If you did not flash it yet with original you should do it. When the problems after this stil occur you can send it to a repair shop. Normaly this is then under waranty.
No point of discussing when original rom has not been tried.
You can download original rom from the HTC site.
Grtzzzz
Hey man be sure You´re not the only one with this prob...check this:
http://forum.xda-developers.com/showthread.php?t=423475
I got this error on saturday n till yesterday I was tryin to find out somethin to fix it....the conclusion is - yesterday I sent it for warranty repair
Even with no display and buttons I flashed stock 1.93xx ROM and also stock 1.93 SPL - nothing changed...problem remained. I was unable to do Hard-reset ´cause "reset button" didn´t work. And very good notice - a few days before this stuck I couldn´t turn on wi-fi. I didn´t realize that it has somethin with this problem till now - I see You got same symptoms
Really didn´t find the solution so only way was to send for reapir to authorized service. Off course like a warranty service n I hope that I didn´t lost warranty - couldn´t proof if flashin of stock SPL was really succesful - but PC didn´t show any errors after the whole procedure...
Earlier today i was roaming XDA and i came across a slide to answer cab, but it was cooked to match the blue theme by showaco
needless to say i cant find this cab and i have spent a few hours drudging through various threads any help would be greatly appreciated!
This one? http://forum.xda-developers.com/showthread.php?t=474018
no not slide to unlock, slide to answer for incoming phone calls
look at my signature for that what you look for
Here you go: http://forum.xda-developers.com/showthread.php?t=466519
Well, it seems like the Slide 2 Answer is popular, but what I'm interested in is a Slide 2 Hang Up option, not using S2U2
Anyone have any options or suggestions?
steb0ne said:
Well, it seems like the Slide 2 Answer is popular, but what I'm interested in is a Slide 2 Hang Up option, not using S2U2
Anyone have any options or suggestions?
Click to expand...
Click to collapse
Hergs Slide 2 Answer has a Slide 2 Ignore option which essentially hangs up the phone instead of answering it.
Or do you mean once you have already answered, you want it to slide to end call instead of just the big "End Call" button???
I know a bunch of people like this and I do believe it was sorely missing. But it seems the chefs are including it in just about every release of thier roms and the thing is just plain buggy and does not answer the phone 50% of the time.
I have tried several of the roms, actually about 5 of them and they all include this and I continue to miss calls.
Does anyone know a way to disable it and go back to the original answer button? Missing way to many calls.
Thanks
techman28 said:
Hergs Slide 2 Answer has a Slide 2 Ignore option which essentially hangs up the phone instead of answering it.
Or do you mean once you have already answered, you want it to slide to end call instead of just the big "End Call" button???
Click to expand...
Click to collapse
Yes, I mean...Once you're on a call and want to hang up. I'd like to slide to end call, instead of the big End Call button (which I've pressed accidentally before)
steb0ne said:
Yes, I mean...Once you're on a call and want to hang up. I'd like to slide to end call, instead of the big End Call button (which I've pressed accidentally before)
Click to expand...
Click to collapse
Thats what the curtain is for in hergs s2a. You have to first slide down the curtain to be able to push the big red end call button, its not quite what you are talking about, but pretty close. And it stops your face from pushing the end call button.
jsmith7364 said:
I know a bunch of people like this and I do believe it was sorely missing. But it seems the chefs are including it in just about every release of thier roms and the thing is just plain buggy and does not answer the phone 50% of the time.
I have tried several of the roms, actually about 5 of them and they all include this and I continue to miss calls.
Does anyone know a way to disable it and go back to the original answer button? Missing way to many calls.
Thanks
Click to expand...
Click to collapse
I have the same problems. I have posted these problems on the ROM Development forum but I got blasted by the moderator because he said it is not a ROM issue. I believe it definitely is a ROM issue because all the chefs are cooking them in, and I still can't answer phone calls 50% of the time. This happens on 2 of my Fuze phones.
Look here:
http://forum.xda-developers.com/showthread.php?t=476769&highlight=ragpaoa
So, is there a simple way to disable the Slide 2 Answer?
EDIT: I have played around with the S2A for about two days now, with 4 different ROMs. I can always answer if I answer immediately after the 1st ring. If I let it ring more than once, the phone won't answer. I have found that if I dial my Fuze from my house phone, I can't answer after the 2nd ring. But if I dial from my office phone, I can answer from any ring. When my wife calls from her cell phone (same AT&T provider I have) no answer after the 2nd ring. However, when someone else calls from another provider like Verizon, I can answer on any ring.
The regular non S2A dialer always works.
ragpaoa- I have some of the same problems. I am using NATF's 4.4 ROM and my phone freezes up at the end of the call (I have to soft reset it to free it up). I reverted to the old dialer but now my face is pressing the screen and making other calls while I am talking to someone. However, it answers every time.
jsmith7364 said:
I know a bunch of people like this and I do believe it was sorely missing. But it seems the chefs are including it in just about every release of thier roms and the thing is just plain buggy and does not answer the phone 50% of the time.
I have tried several of the roms, actually about 5 of them and they all include this and I continue to miss calls.
Does anyone know a way to disable it and go back to the original answer button? Missing way to many calls.
Thanks
Click to expand...
Click to collapse
Have you tried RRE's rom? I get 60-80 calls a day and have never had an issue with the one he uses.
I have same problems with my Fuze. I've tried several different ROM's and it seems like everytime the phone comes out of standby it will not pick up the phone call. Very frusrating as I always have to call the person back. I was wondering if anyone has found a solution to fix this issue? Maybe install a different dialer. Anyone have a link for that?
At the moment I am using Energy ROM 3.0. But I had same problem with PROven ROMS. Stock At&T rom works fine. Please help.
Sorry to revive a dead thread but it appears this was never fixed.
I am having this issue with ANY ROM I USE. I have tried the #777 fix, but the #778## whatever isnt for GSM (only CDMA). Does anyone know how to fix this problem?
This one has worked for me FINALLY (on rRedux WM 6.5 28008.1 HTC Sense 2.5) so far ::knocks on wood:: I'm assuming it should work fine on other ROMs but should also be uninstallable.
Phone canvas looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Clicky, install and soft reset --
cubetto said:
Here http://www.ciccio86.it/ROM/QilinPhoneCanvas.cab
Click to expand...
Click to collapse
Charged my G Watch R last night as I always do and put it on this morning. Noticed at my breakfast meeting that it had froze earlier on 6am when it was now gone 7.
Pressed and held the power button for 8 seconds to restart and now just get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's still working underneath as it vibrates with notifications and calls etc.
UPDATE: Randomly as I'm writing this post the screen comes back to the normal face, I have a go to flick through my notifications then it freezes on email and won't move even when the power button is pressed but again is vibrating on notifications.
Obviously it will need to go back but wondering if anyone else has had similar issues?
Thanks
Try a full reset before returning it.
Sent from my SM-N900P using XDA Free mobile app
I havent had that issue? Odd for sure. Check over in the Moto section if anyone has.
In the brief moments the screen returned to normal I managed to initiate a factory reset, it rebooted with the LG logo and set back up but within minutes it went back to how it is in the photo.
Thanks for your replies.
Same problem as mine?
http://forum.xda-developers.com/showthread.php?t=2942521
Blinking screen in dimmed mode
Skickat via Tapatalk
Our devices were meant to be together
My LG G2. Same situation. I just have to whack it on a table a once or twice and it goes back to normal.
I had that pixelated screen popping up once, while I was testing some heavy customisations on the watch maker app ... since I'm using faces with less objects I did not saw that weird screen.
I suggest to do a factory reset or to choose one of the default watch faces ... anyway, something else than what has been on when that stuff occurred.
I had the same issue with my first one
Mine did this after getting fully charged, i had it next to me on the table ready to be strapped on when it happened.
I am amazed you could reboot, mine did not even responded to the main button any more, got really hot also.
after an hour in the box (ready to be send off back to the retailer) it did a spontaneous reset, and showed 5% battery left. I turned it off and send it back, my second one developed the blinking issue in dimmed state, so also back, now on my third one. I do hope this one will be all right, i love it dearly! The recessed screen prevents the random activations i had with the LG G, bloody annoying when playing music with Music Boss, pause/play every few seconds when my sleeve touched the screen..
I wanted to post the photo of the crashed screen, but i am not allowed yet
Thanks for all the replies.
I contact Clove Technology where I purchased it from and they have replaced it, awesome service from them. New one is working fine so far, fingers crossed it stays that way.
Sent from my Nexus 7 3G
Good luck!
GuyAdams said:
Thanks for all the replies.
I contact Clove Technology where I purchased it from and they have replaced it, awesome service from them. New one is working fine so far, fingers crossed it stays that way.
Click to expand...
Click to collapse
I do hope your new one will work out, i am starting to think they have a serious quality issue somewhere in the production line!
RoosW said:
I do hope your new one will work out, i am starting to think they have a serious quality issue somewhere in the production line!
Click to expand...
Click to collapse
Think so to, there seem to a lot of lgr users with this problem. Really hope the will solve this, love my lgr but hate this issue. I have a new watch on its way to me, got mine replaced to.
RoosW said:
I do hope your new one will work out, i am starting to think they have a serious quality issue somewhere in the production line!
Click to expand...
Click to collapse
Thank you
So far so good!
Got my new watch the other day. Works great so far, hope it will continue do so [emoji2]. Really like it !!
I got this yesterday when i tried to use Watchmaker watch face app for the first time. Reboot, happened again. Switched back to Facer. Haven't seen it again.
My match Same situation.
i need hepl.
I'm not sure if it might be an LG thing but I had the EXACT same thing start happening with my Nexus 5 a couple of weeks ago. The screen would freeze and be pixilated but the device would be working and ring and vibrate for notifications. I don't know what triggered it but coincidentally it was right after the lollipop update that it started to happen. A reboot usually (but not always) solved it. LG replaced the device as it was still under warranty.
Sent from my Oneplus One using XDA Free mobile mobile app.
Huh, that sounds troubling, but then again, this is the first time i hear of this on the Nexus 5, so maybe it is a software problem after all, I hope the soon to be release 5.0.2 will fix this, at least it seems to fix the battery problems some seem to have after the 5.0 update and the performance issues some see on the Nexus 7 slabs.
But as LG has swapped your N5 for a new one, i am very afraid they have a real quality issue in their production line!
S.A.M.E. ! :crying: I didn't do anything wrong with it and the screen just died after a nap.
Sent it back to Korea and it's fixed now.
http://postimg.org/image/no7xnu7bd/
Pressed and held the power button for 8 seconds to restart and now just get this
Click to expand...
Click to collapse
Strange, for me it was the other way around: the pixelated screen just appeared out of nowhere... It did seem to respond to button actions, so I decided to keep the button pressed very long.
Result: it rebooted, and I have never had any problems since
TeroZ said:
S.A.M.E. ! :crying: I didn't do anything wrong with it and the screen just died after a nap.
Sent it back to Korea and it's fixed now.
http://postimg.org/image/no7xnu7bd/
Click to expand...
Click to collapse
EDIT: DEAD AGAIN 2 DAYS AFTER THE REPAIR!!! I may probably NEVER going to buy any LG product in the future. Considering switch to the 360.:crying::crying::crying::crying:
i recently updated my A890 From 5.0.2 to 5.1.1 BOJE
After updating , my phone started disconnecting from wifi and Freezes with an annoying noise for 10 seconds then reboots.
i absolutely love this device and do not want to change it. please help me if i could solve this issue by uploading a custom rom or updating to CP12 or 14 MM.
before updating my phone. it usually restarted after a few days when gets hot or i accidentally over swipe the screen.
please help me as this phone has started making noisy restarts every now and then.
Quick Note
i ran this device in safe mode and used for couple of hours on youtube over wifi.
i had no issues at all. so basically it's just a firmware issue. i guess.
help needed anyways
Hi, use this thread to update to 6.0.1 and this should fix your problems.
http://forum.xda-developers.com/showthread.php?t=3260744
I'm using this device in safe mode now. While replying to this thread . I have updated to 6.0.1 but the problem still remains the same.
Any dev could help ?
I had restart issues in 5.0.2 as well but they were minor
Now it hangs every single minute and disconnects from WiFi constantly .
Please help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SameIssue
I have same problem. I am also on 6.0.1
Everything was perfect on 5.0.2.
I updated it directly from 5.0.2 to 6.0.1 and now having all these issues.
But it seems like there is no one to help..
Go Back to 5.0.2
Zack Brown said:
Go Back to 5.0.2
Click to expand...
Click to collapse
We Can't Downgrade because of "LockedBootloader".
Can you tell anyway to downgrade ?
Irfan122 said:
We Can't Downgrade because of "LockedBootloader".
Can you tell anyway to downgrade ?
Click to expand...
Click to collapse
You action note
"Hi Guys,
I've read this post a while ago, and I tried everything you said, but non of them worked. I have Samsung Galaxy S6, Gold, 128GB. Not edge. So, I read a lot of articles on the net and youtube. But my cell phone kept restarting from time to time and no warnings, sometimes it's just turn itself off without any warning. Most of the time I keep it on my desk where I work and suddenly it's making the song of rebooting or sometimes I find it just turned off, it could be deep sleep I never knew which of which. I tried every single solution to solve this, made back up, Restore factory defaults and it kept doing it.Probably you would say, uninstall apps that are causing the problems then I say, I have non. I only use What'sUp, imo, Tango. I don't have any other apps. It's just brand new bought from Verizon and it has of course Verizon apps and google, Samsung apps. I tried everything in the youtube, google but for vain. One day I was tampering with the settings and I found one of the settings with a weird message. I changed it then it is working 100% like a machine guys. Here is the settings and the warning message:
Go to Settings => Display and wallpaper => Screen mode => the default selection would be: Adaptive display.
When I reached this one, I read the following warning message:
"Optimize the color range, saturation, and sharpness of your display automatically. This mode may not be compatible with third-party apps."
This message draw my attention and I told myself, let's try this.
You can choose any other of the settings and non of them will show a warning message, so, I selected "AMOLED photo", I liked its colors more than cinama or basic, and voila...
I changed this settings since August 17, 2015 and I'm writing this on August 27, and never had even one restart or self turn off. it's now solid like a rock and working like a machine, very stable.. never better.
Please guys try this solution and spread the word if you find it useful.
Thanks a lot"
I'm having a somewhat similar issue. My S6 Galaxy Active is just randomly shutting down. Say I call somebody and they don't answer; I set my phone down after hitting the power button to lock the screen. Twenty minutes later I go to check it, and it's just off. I have to turn it back on and now don't know if I received a call or not (unless a voicemail was left) and it's very annoying.
This started out rare and has now become more frequent. At first it wasn't too often and generally only happened when the phone was "resting" on a desk or my bed with the screen off. In my last call with my girlfriend it shut down THREE TIMES during our conversation.
Now, during the conversation the phone was against my head so the screen was still off. I haven't ever noticed it happening with the screen on. This has started to happen within minutes of a prior shutdown, like 40 times a day, and it's insane. While I'm not 100% sure I'm about 90% that it only happens while the screen is off. It's not restarting, it shuts down completely and remains that way until I power it on again. It's not buttons being pushed accidentally as it will be set down entirely by itself and still shut down.
Another, possibly related, problem is that sometimes the screen is blank. I'll turn the phone back on and will hear the startup sounds, but there is just no picture. The screen is dead. I will have to force-shutdown the phone (volume down + power) to fix this. Sometimes it restarts with no screen again and I have to do this several times, but it always is fixed eventually. This happens much less frequently than the shutdown problem but is still an annoyance. I've also noticed some... flickering, while the phone is in use. This is even more rare but has also started to happen a bit more. I'm not quite sure how to explain it... a portion of the screen may compress, or "wrap" around. For instance, the bottom portion of the screen (let's say the bottom 1/8th of it, if you divided it with horizontal slices) will "wrap" and be shown at the top, distorted with random discolorations (generally purples, greens) along with sometimes being twisted at an angle. This usually happens for a few seconds and goes away.
My main concern is that I've taken great care of this phone. It has never been dropped outside of slight falls from pocket/hand level onto carpet. It's never been submerged or even gotten wet at all. On top of all that, it's an ACTIVE! It shouldn't really matter if it DID get wet; regardless, although it's an Active it's been cared for as if it weren't. This simply cannot be a result of physical neglect unless somebody is sneaking into my house at night to chuck my phone at a wall. The phone is... I'd say a year and a half old? I bought it when the S6 was still the newest Galaxy, I believe AT&T had somewhat recently obtained the rights to sell it. I'm sure I could find the exact date of purchase if it mattered.
I didn't want to make an entirely new thread for this, but I'm sorry if I've hijacked this one. If I should make my own thread instead I will, I just figured keeping the main boards clear of clutter was a better choice.
Thank you to anybody that can help. I'm guessing my only options are "replace it" or "take it in" but I'm hoping there's a solution. I know I can wipe the cache, factory reset, etc. I will add that I am very, very full in terms of memory; I might have around 500gb free. I'm not even sure what's really taking up all the space as all my music is in the Cloud, I'd have to check, I guess Apps? The Active not having an SD slot really sucks. I don't think low free space could result in shutdowns, I work in the IT industry and can't think of a reason why it would... unless something absurd is happening, like the phone is running out of RAM, trying to use SWAP, there's not enough space (although it would be pre-allocated and this wouldn't happen, no?) and so it shuts down? I don't know.
I'm thinking it might be as simple as a loose battery connection, as so far my tests seem to show that this DOES NOT HAPPEN while the phone is plugged in, so it seems like some sort of quick power failure? Unfortunately I am unable to check the internals myself as I do not want to void any potential warranty; I think I may have purchased the replacement plan and will be checking tomorrow. If I'm going to void my warranty it's going to be with a root, not exploratory surgery (at least not until I'm 100% sure what to look for). Anyways, thanks for any help.