Related
Holy moly! My cell just called itself! It showed my number and it said Incoming Voicemail! So, I don't know if I should I have, I picked up and didn't say anything and it seemed like the sound on the "other side" was where I was at.
Think someone needs to go to bed earlier JK
Rather bizzare and never heard of phones calling themself except in rather bizare horror movies.
Could have just been some freak call of nature, could have been a problem with carrier....
If your worried hard-reset device not that i think it will help but may put your mind @ rest, if happens again after i'd phone your carrier to ask why your phones is calling you? "try not to laugh when calling"
I'm sorry to make humour but i just had so many funny visuals soon as read it.
Get some sleep all will be well
I know its funny man but I found this so far.
Seems like other T-Mobile people had this issue.
http://forums.wirelessadvisor.com/t-mobile-users/61805-phone-calls-itself-defective-sim-card.html
I told my friend, he started to crack up!
How do you turn off the Paging Notification Options in the Dash? That seemed to have fixed things for these guys.
UPDATE: This is weird. I called the Voicemail, went on my Paging notifications and it says they are turned off. Yet, I still got the call? Anyone...
You remind with my Dash, i have the same issue for very long time, immediatly after reciving a voice mail my phone rinngs twice and stops, recently i flashed my phone to the latest 6.5 WM and i did not see this issue anymore. What causing it??? God knows.
Probably a flashing error with the RADIO. That, or some essential program for making calls is malfunctioning due to a bad flash. I honestly see no other reason for this than a bad flash. The ROMs are designed by our master-chefs to work well. Any glitches that a small percentage of people have are usually flash-related. The solution...REFLASH! I know i have had to do this because I have gotten funky results.
*this also taught me that when they say "Do not touch the link line", they really mean don't touch it at all. I have made a habit of stepping away from the desk when flashing haha, but that is just the very worried me *
I had the same situation long time ago
My excalibur called itself!
It never repeated but it was an unsolved strange problem
I never touched anything when flashing but its weird that its something flash related because everything works fine other than this and I called my voicemail, my paging notifications are off!
So I flashed it back to stock ROM, still getting the calls. I pick up, I say HELLO? And Jigsaw voice from SAW movies says, DIE! You will die in 5 days... or something like that. No joke, I heard that SAW had something on their site to prank call people but they took it down. I wonder if some dumb person I know is pranking me. Anyone had or know about this?
Capitan Totti said:
So I flashed it back to stock ROM, still getting the calls. I pick up, I say HELLO? And Jigsaw voice from SAW movies says, DIE! You will die in 5 days... or something like that. No joke, I heard that SAW had something on their site to prank call people but they took it down. I wonder if some dumb person I know is pranking me. Anyone had or know about this?
Click to expand...
Click to collapse
Just feel off my chair you made my day
I so hope that you are providing comedy here and not being a realist
Sorry if i take you wrong way
I am not kidding man. I called my buddy and Googled it, there are many sites that prank call. I also read that the SAw website had something where you could prank people and they to take it down. Guess what! First time I got the call it was Oct 23. Guess when SAW VI came out... OCT 23! So, I hope that is it. I think I know who did it, but not 100% sure. Just wanted to know if you guys heard about these things.
hmm, i think theres a hole in your story... your first post says October 19th not 23rd. haha but funny nonetheless.
dermann said:
hmm, i think theres a hole in your story... your first post says October 19th not 23rd. haha but funny nonetheless.
Click to expand...
Click to collapse
Yep it's just a plug for SAW VI
ah damn i wish i knew about this before the website got closed. lol
What do you mean a plug?
I am pretty sure I got the call Oct 23 because I even circled it on my calendar.
Either way, I am still gonna call T-Mobile.
Capitan Totti said:
What do you mean a plug?
I am pretty sure I got the call Oct 23 because I even circled it on my calendar.
Either way, I am still gonna call T-Mobile.
Click to expand...
Click to collapse
A plug is advertising generally dropped in when on different subject. 'google will give a better definition'
Good luck with t-mo and hope they make more sense of it than us, i'm baffled untill today i was thinking same as you linked, now i just got a comedy sketch similar to Crazy Movie in my head
Still alive! Thank God!
It only happens when I use any ROM based off the .47 OTA and now the newer froyo 2.2 versions that have been released. I realize they are not final but a final version is obviously not going to fix my problem.
I feel I am probably a very small number of people with this issue. If I run any other ROM I don't have the issue but obviously there is something either with my phone or in the kernel or something effecting my phone.
What do I mean by ghost screen touch? Randomly using the phone it will register touches at the top of my screen. Bad enough to make the screen unusuable and I have to turn the screen off and on multiple times till it goes away.
If it is happening in my app tray it will always select the first top left icon on my screen.
This is on a completely stock ROM without me adding any software or anything. I also have no screen protectors etc. I have eliminated everything I can.
The only thing I can think of is I know before the .47 OTA some people complained about a grounding issue. I never had that problem personally but whatever they changed I think may be causing this because any ROM before that is fine.
This also does happen to me more when the phone is plugged into the charger.
thanks for reading.
I have gotten it when I'm charging, to the extent I have to disconnect my phone to use it without the screen going crazy.
Have you tried running dotty to see if anything is registering?
Sent from my PC36100 using XDA App
SharkUW said:
Have you tried running dotty to see if anything is registering?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Installed dotty and nothing was showing. decided to touch it and when i stopped touching it 3 points were still showing as registered(i can max at 5 points) they are still showing as i look at the phone now not evening touching it. now they are flashing as if i was touching them both!
update..it seems like its normal for there to be points after you stop touching the screen in dotty i dunno..however when my screen does start going crazy in dotty it will show two touches parallel to each other on the top left corner just down a bit. it will actually flash between the two as if i was cycling my fingers back and forth.
MrDSL said:
It only happens when I use any ROM based off the .47 OTA and now the newer froyo 2.2 versions that have been released. I realize they are not final but a final version is obviously not going to fix my problem.
I feel I am probably a very small number of people with this issue. If I run any other ROM I don't have the issue but obviously there is something either with my phone or in the kernel or something effecting my phone.
What do I mean by ghost screen touch? Randomly using the phone it will register touches at the top of my screen. Bad enough to make the screen unusuable and I have to turn the screen off and on multiple times till it goes away.
If it is happening in my app tray it will always select the first top left icon on my screen.
This is on a completely stock ROM without me adding any software or anything. I also have no screen protectors etc. I have eliminated everything I can.
The only thing I can think of is I know before the .47 OTA some people complained about a grounding issue. I never had that problem personally but whatever they changed I think may be causing this because any ROM before that is fine.
This also does happen to me more when the phone is plugged into the charger.
thanks for reading.
Click to expand...
Click to collapse
the only time I saw something like this on my phone, the screen shaking, icons moving, like delayed touches, vibrating movements, ghost screen touches, etc. etc. and unresponsive, was when I ate a "Subway" sandwich, I had mayonnaise on my fingers, and I tried to use the phone, it looked like it was experiencing a seizure. I really worried that day. I even though of pulling the battery. It went away when I wiped the screen....
I can confirm the odd touch behavior while charging.
This may be unrelated but I recall seeing a post saying the HTC Music widget was causing scroll lag and touch issues on the new OTA over in the dev forum.
So does that mean you ruled out the fps hack?
I woudlnt worry much.. been getting this every once in a blue moon since the first OTA (while charged to PC.. not the wall)
I also have this issue, but its rare when it happens... I've seen this exact issue with my old pre as well...
Sent from my PC36100 using XDA App
baiatul said:
the only time I saw something like this on my phone, the screen shaking, icons moving, like delayed touches, vibrating movements, ghost screen touches, etc. etc. and unresponsive, was when I ate a "Subway" sandwich, I had mayonnaise on my fingers, and I tried to use the phone, it looked like it was experiencing a seizure. I really worried that day. I even though of pulling the battery. It went away when I wiped the screen....
Click to expand...
Click to collapse
Seriously? So you're what 12 then?
AssassinsLament said:
So does that mean you ruled out the fps hack?
Click to expand...
Click to collapse
Correct..I am not sure what has changed since the .47 OTA but from there on up the issue is there even stock.
DataDork said:
I woudlnt worry much.. been getting this every once in a blue moon since the first OTA (while charged to PC.. not the wall)
Click to expand...
Click to collapse
I'd love to not worry about it but it happens to me without it being plugged in also. Often enough to be very annoying.
You should take your phone back.
Sent from my PC36100 using XDA App
Are you using the stock htc USB cable? I know that certain cheap (i.e. Monoprice) chargers/cables cause people's screens to become unresponsive and just basically act weird. Though it doesn't explain why it is only doing this with Froyo. Okay nevermind, just throwing some ideas out there. =)
My screen is less responsive to touch when charging via A/C adapter sometimes. Probably a grounding issue. Doesnt bother me.
I am also having this issue, except it happens w/o it being plugged in and it is happening to the point that my phone is completely un-usable. I bought it on launch day, I am trying to get back to stock 2.2 using the OTA and take it into sprint and play dumb I dont know what to do at this point.
Update: I was able to roll back to 1.32.651.1 (initial release) and I did not have any "ghost input" issues at all, loaded up dotty (which interestingly only let me use *2* multi-touch inputs at a time, if I put three fingers down the 3rd wouldn't show) played with it for 10 minutes. Usually I encounter these symptoms within a minute or two. Then I started updating, It loaded that very small update 1.32.651.6 i think, again no problems at all. Next up was 1.47.651.1. This update is the one that is causing the problem for me. Within 45 seconds of getting into the OS after 1.47 I started encountering the issue and Dotty is showing the same symptoms that MrDSL is having (two dots flashing in the top left handish corner). For ****s I then installed the official 2.2, in hopes that it would resolve the issue, but I still have the same problems. So, at this point I can either run pre 1.47 which really isn't an options for me, or deal with the ghost input issue which also really isn't an option for me, it literally drives me insane and I can't even use my phone as it just does it's own thing, or take it back to sprint.
At this point since I purchased this phone on launch day from Radio Shack what should I do? I want to exchange it but I don't know if Sprint or Radio shack will take it back (we're coming up on two months since launch). I should not have to use Insurance for something that is their problem. Suggestions?
Anyone else having this issue besides me and DSL ? DSL what have you done to remedy this or are you just living with the hell?
nvous23 said:
Anyone else having this issue besides me and DSL ? DSL what have you done to remedy this or are you just living with the hell?
Click to expand...
Click to collapse
Since the offical 2.2 has come out I emailed Sprint to let them know and they created a ticket for me and told me to bring it to the nearest Sprint store who has a tech on site.
I played dumb and said the issue started at the .47 OTA and that I was hoping the 2.2 OTA would fix it but instead it actually got worse. So when I need to go to the Sprint store I'll just flash the offical 2.2 OTA.
I really don't have much of a choice other then that unfortunately
Do you have a screen cover?
Sent from my PC36100 using XDA App
I do not have a screen cover. Even if i did and it was causing the issue it would happen on pre 1.47...
No screen cover! Nothing!
This is even without adding any software..Completely stock!!
Yep, got the same thing here. It's some of the most annoying stuff in the world. I'll be typing on the keyboard, and it'll give me a triple-tap, then it'll flip down the notification panel, and it just does strange stuff. And then it'll be fine for the rest of the day. And then, it'll do it again. It's such a pain. I figured it was the FPS hack, since it runs everything at 110Hz or something, but then I noticed, like you guys, that it happens on stock as well. Pretty much a total pain.
Sooooo I think I F'd up.
I just dusted off my Tilt and charged it up and was attempting to put Android on it...apparently somewhere along the away I wasn't paying attention and was mixing up instructions between these two threads:
http://forum.xda-developers.com/showthread.php?t=680518
http://forum.xda-developers.com/showthread.php?t=621001
I think I flashed the nbh from http://forum.xda-developers.com/showthread.php?t=621001 and attempted to use the instructions from other other thread with it.
It actually booted into Android once, but it was apparently a build I had on my SD card from a while back. not sure why it booted into that, but I deleted the files off the SD and rebooted the phone and that was where my issues started.
Please save the "you're a moron, you shouldn't have tried this if you didn't know what you were doing", etc. I am not retarded and have done lots of messing around with this phone and others, I just was trying to do it too early in the morning and obviously wasn't paying close attention. =P
oh and I am hardSPL'd.
Basically my symptoms now are.......nothing. I hit power and the LCD doesn't even start to turn on, and neither do any LED's. No bootloader, LED's, backlight, anything. It's as if the battery isn't even installed (which it is...)
I've been looking around and haven't found anything related to this specific issue... If there is a thread on this already I apologize, and please direct me to it.
Did you try entering bootloader by holding cam button down and power on (no usb cable plugged)?
Did you try a hardreset?
ahhhh there she is.... removed USB and reseated battery and held cam and power and got into bootloader... simple oversight, I think I forgot to unplug USB the first dozen or so times. =P
Should be fine from here. =x
k, please commence the impending dozen posts calling me a noob and bustin my balls for creating a thread for this. =P
thanks man.
Funkwheat said:
ahhhh there she is.... removed USB and reseated battery and held cam and power and got into bootloader... simple oversight, I think I forgot to unplug USB the first dozen or so times. =P
Should be fine from here. =x
k, please commence the impending dozen posts calling me a noob and bustin my balls for creating a thread for this. =P
thanks man.
Click to expand...
Click to collapse
Actually the OP is a good example of a well thought out, informative troubleshooting post, all the information you thought would be needed was there, what you did, what went wrong, the symptoms, and finally, the solution, OK is was a silly mistake, but not an obvious one, leaving the USB plugged in wouldn't stop WM from booting, and this one might help someone else in a similar situation.
So don't beat yourself up about it, a late night/early morning mistake like that is just about inevitable once in a while
zenity said:
Actually the OP is a good example of a well thought out, informative troubleshooting post, all the information you thought would be needed was there, what you did, what went wrong, the symptoms, and finally, the solution, OK is was a silly mistake, but not an obvious one, leaving the USB plugged in wouldn't stop WM from booting, and this one might help someone else in a similar situation.
So don't beat yourself up about it, a late night/early morning mistake like that is just about inevitable once in a while
Click to expand...
Click to collapse
Thanks! It's so nice to see non douchey posts like this once in a while. =P
Although we have a relatively relaxed community on xda versus other forums I've seen.
oh and after realizing I was a moron, I was able to successfully install Cyanogen Mod 6 just fine! =D
Actually that was informative, will bookmark this one for when I get into difficulties, which will no doubt happen
But note to self, before attempting ANYTHING in the morning, drink a strong coffee first
Anyone playing games on their Epic 4G Touch seem to have a common problem:
During intense gaming, the game either freezes or crashes returning you back to home screen. Everyone I know is experiencing this and yet we tend to ignore it for the love of our device, but this doesn't mean Samsung should pretend their $600 device is functioning as normal.
Dear XDA'er
If you are experiencing this problem, please post something here. Let's see how wide spread this problem truly is.
I for 1 am having problems playing "Galcon and Airport Mainia", since these are the only two games I play, I get frequent crash often. Post, post, post... I hope this thread grows to the attention of Samsung so that atleast they could acknowledge there is a problem!
There's already a starred issue, or what ever it is about it, and a thread here.
phatmanxxl said:
There's already a starred issue, or what ever it is about it, and a thread here.
Click to expand...
Click to collapse
You got link?
Btw, more threads on this the better? I read a post and someone said they contacted Samsung but they refused the problem. Are you experiencing crash?
There is a code issue out, I couldn't find it. Maybe it was closed already. I remember seeing another thread about it with the link a few weeks ago, if I find it ill link it.
I thought it was just me. I figured it was the result of me screwing up a file when playing with things or a bug with the kernel I was using. Kind of wish it was....woulda been able to fix it then.
Here is a detailed explanation of what's going wrong:
http://forum.xda-developers.com/showthread.php?t=1284086
Here is another thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1283712
There are a ton of games that didn't give me this issue, but I've been having this problem on Robotek and Zenonia 3.
Read my posts. Only reason I dropped tmo and came over was this phone for gaming and my vibrant had none of these god damn.....just check my profile and read my posts. Pisses me off to no extent.
Sent from my SPH-D710 Galaxy S II [suck it]
manekineko said:
Here is a detailed explanation of what's going wrong:
http://forum.xda-developers.com/showthread.php?t=1284086
Here is another thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1283712
There are a ton of games that didn't give me this issue, but I've been having this problem on Robotek and Zenonia 3.
Click to expand...
Click to collapse
Yea that's what I was talking about.
phatmanxxl said:
Yea that's what I was talking about.
Click to expand...
Click to collapse
My Evo3D works just fine... This phone is on my nerves with crashes
I don't game a ton on my phone but I do like to game occasionally. This is just a rough estimate but I'd say half of the 20 or so games I've tried will crash on me within 20 minutes of playing. Out of the ones that crash about a quarter can be fixed by disabling some portion of the audio; either music, sf or both. The other quarter continue to crash in the same manner no matter what you do with the games audio.
Pretty big bug IMO, can't believe there's not more hype about it.
Ok, so like...two days ago, I followed qbkings video on how to root & clockworkmod an epic with EI22, well it worked. I got recovery working A ok and played around with some roms and stuff. They all worked for the most part, but after rebooting my phone, the SAMSUNG loading screen wouldnt fade away, realizing it had been soft bricked. I tried recoveries but they didnt work. tried tutorial after tutorial after tutoria, but no luck. When trying the Odin unroot method It'd always be stuck on like a factory. file, and keep getting the phone - ! - computer error afterwards. Ive tried looking around the forums and such, but no go. I really need help with this.
You didn't look to hard. There have been 5 threads like this in the last 2 weeks. Go to the stickies, top of development and follow post 1 of How to restore a semi-bricked Epic.
Sent from my SPH-D700 using XDA App
Uh yeah, that was one of the first posts I tried. Never worked for me. Followed exactly step by step and repeated the process five times, but ive been constantly getting stuck on factoryfs.rfs
oh ****, now it wont even turn on. tried charger usb, nothing! no indicator or anything. damn. am I screwed?
I think you were better off leaving your phone alone. If following instructions is difficult, than that should have been your first clue. Id post a link to help you, but you have already read and tried it, and even that didn't work........time for you to buy an iphone I guess.
Sent from cyandroid
Try pulling the battery and sd card, let sit for an hour with usb unplugged, then connect to usb cable with odin running and try to boot into download mode.
If it goes, pop the battery in and load up ei22 or another odinable tar along with the recovery in qbkings videos. Make sure only reboot is checked in odin.
If not, go back and try every step in the sticky. I doubt that you have a problem that has not been experienced already.
Sent by my CleanGB Epic using XDA App
So you tried buying and using a better cable? And tried with both the battery and sd card out using only the computer as a power source like the thread in Development said to do?
b16flybye said:
I think you were better off leaving your phone alone. If following instructions is difficult, than that should have been your first clue. Id post a link to help you, but you have already read and tried it, and even that didn't work........time for you to buy an iphone I guess.
Sent from cyandroid
Click to expand...
Click to collapse
That's a bit flamish.
shane6374 said:
That's a bit flamish.
Click to expand...
Click to collapse
Sometimes the truth hurts.
I tend to agree with that sentiment, nothing against you OP, but there are some that gravitate to technology and feel at home, and then there are some that gravitate and lack the necessary skills for something like this.
This is a very straight-forward task, especially with all of qbking's hard work in making those very easy to follow videos, and other's time typing out tutorials, so I really fail to see how most have so much trouble making it work. Maybe they belong in the latter analysis.
Sent from my SPH-D700 using Tapatalk
azyouthinkeyeiz said:
Sometimes the truth hurts.
I tend to agree with that sentiment, nothing against you OP, but there are some that gravitate to technology and feel at home, and then there are some that gravitate and lack the necessary skills for something like this.
This is a very straight-forward task, especially with all of qbking's hard work in making those very easy to follow videos, and other's time typing out tutorials, so I really fail to see how most have so much trouble making it work. Maybe they belong in the latter analysis.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
We all started somewhere on this, and I bet most people didn't have success right away. I know I didn't on either platform I've worked on. I'm just sick of the n00b flaming around here. These people might be the ones who's roms or kernels you running in a year. Just show some respect.
Sent from shane6374's Epic via Tapatalk
Youll have to find one of them jigs to get you back into download mode I assume usually time heals all mistakes though if your inpatient id look up how to make an odin(download) reset jig ( I think its called that). I think there a thread about that lying around here somewhere...
Sent from my OG Epic
Yeah, not trying to knock on you too hard, but qbkings videos should be all you need for successfully rooting and flashing. He works hard on them and is very clear with instructions.
Sent from cyandroid
Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.
Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.
With the soft brick you might have been able to save it. It happened to my brothers phone and what I did to fix it was wipe everything, factory reset
Then flash stock rom. Wipe everything again
Then flash stock kernel
Wipe everything again
Then it was perfect.
If you had already been flashing roms.and such then your problem wasn't following directions.
You just might have flashed a rom without a supported kernal. Causing bootloop
As far as where you are now.. maybe tell then you dropped it and it never turned back on?
I don't think they can ever find out you rooted it if it never turns on again lol
Sent from my PG86100 using XDA App
Jbluna said:
Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.
Click to expand...
Click to collapse
Don't use the broken screen as the reason or they will charge you around $100. Just try and make sure you get across the point that its the faulty phone (even if it isn't) and make sure you have an accurate believable story on how it got bricked. If you mention anything about messing with root or anything similar they won't replace it.
True. But on another note you can't say much. Only other thing I can think of is saying maybe you tried updating the device and it died
Sent from my PG86100 using XDA App
Seriously you ignored the odin mode jig? it jumps you back into download mode and you should be able to odin back to eco5........ Ill find a how to for ya.
Its all over a simple google search and you can find a usb jig for about 8 bucks.
Sent from my OG Epic
I just unbricked my wife's EPIC with this: http://forum.xda-developers.com/showthread.php?t=1052813
thanks dyehya for the howto tutorial!
Jus tell them you took it off charge this morning and it wouldn't come on.
Did you try the mythological magic button? The pin hole behind the cover next to the camera lens?