Related
Hello all,
I'm new here, have read lots of the information available, but came here looking for an answer that I haven't found yet.
Situation is the following.
I got this Qtek2020 (or XDA II) from my dad who used it for his work. The reason he stopped using it is because the "phone" function itself is kind off acting weird.
Sometimes it is just nog possible to get into phone mode, neither of the two methods make te device display the dial pad...
- hitting the green button
- going Start-> phone
(It's kind off like a non responding program in windows when you want to execute it)
To make things clear, the phone works fine if we go to contacts and then choose the option to call the contact.
The question is, does this problem seem familiar and is there a way to fix it by for example putting a new rom on the device?
Any help or input about this is greatly appreciated.
Thanks in advance
I think the HARD RESET should help . After a long... long work configuration data and other settings going to be ... melted . If U don't store on devise impotrant data just remove the battery for about 20 mins .
my mother just bought an sgs2 about 1 week ago. she is not that expert in phones and all that, but she has a serious problem now. she made a lockscreen code witch she cant remember now. stupid right. how can u bypass it or dissable it. i must say i have tried my self almost anything i can think of
this is what i my self have tried:
factory reset / hardreset didnt work
flashing stock rom again, didnt work
flashing 3 custom roms didnt work, to mention with root kernels
and no my mom never made an gmail account. she only uses it for calling and sms
so what the hell is there to do??
or do i need take to a samsung service center???
You're likely looking at data loss by factory resetting and overloading it with wrong passwords from recovery mode.
http://forum.xda-developers.com/showthread.php?p=17039887#post17039887
Though you say you've factory reset already and it didn't work - what didn't work?
when i did factory reset and rebooted the phone, it went okay, and i thought i had dissablet it, but no, when the screens turns black and u want use it again, the lockscreen keeps apper
Can't you just disable it before the screen turns off then? Settings --> Location and security --> Set up screen lock --> None.
no when trying to dissable it asks for the code, u must enter the code before able to dissable, im stuck, what should i do
I just noticed your thread [Q] screen locked, need help.
vodcas said:
2 days ago i found a sgs2 on the ground outside at the city. the screen is totally ****ed but it still works. so i thought cool, who ever lost it, should have been more carefully, but honestly i dont care.
but when i turn it on, i can se its on cynogenmode but i cant use cause of some screen password. i have tried everything from re flash og several types of roms, including stock, cynogenmode and exonys, but all appear but it wont install new rom. i cant enter factory mode, cause when i try it says need password. so i cant do a hardreset. i have searched the net for everything, and i have tried almost possible ways to get around that screen lock, but nothing works. so how can i get rid of it??? when i press volume upp with home and turn on button it askes for passworld, when i do it with volume down, i get into odin mode. i have tried 0000 and 00000000 but still dont work. any one can help?? pls
Click to expand...
Click to collapse
Sounds like someone's telling porkies in this thread.
lol, that phone wasnt usefull, thats like long time ago. believe or not.
i my self have a sgs2 and i recommendet my mother. im glad i found that phone on the ground, so i could by one. anyway should i just say to my mother she must take it to a samsung service center??
vodcas said:
believe or not.
Click to expand...
Click to collapse
I choose not. Maybe you'll find someone else who does believe you and willing to help.
Hello.
I'm having problems with my Samsung GT-I9000 ( Galaxy S 1 ), and was hoping I could get some help here.
About 4 maybe 5 months my phone has been having crashes (Is as close as I can explain them)
This is what happens:
- Talking to somebody on Whatsapp (for example, but it also crashed on me while playing games, and even when calling)
- I lock the screen and lay the phone down
- After about 2-3 seconds, the screen lights up. And shows me the conversation but does not respond
- Phone goes black for about 5 seconds
- Light vibration
- Screen shows the lock screen, loads my background and scans for media
This happens randomly about 5-10 times a day now. (Depending on how much I use the phone)
It also sometimes just turns off without any animation or sound.
What have I tried:
I first thought it was the ROM, I'm sorry if I make mistakes here but I'm a noob.
The ROM was put on there by a friend of mine, it was called Darky's ROM.
I tried to put a differed ROM on it, but the tutorials failed on me and I killed the phone. Not the "Black screen of death" but beyond that point. It wouldn't even turn on anymore.
Then I send it back to the provider, they took 2 weeks to fix it and I had my phone back. I think they put the default ROM on it but I'm not sure.
Anyhow, this did not fix the problem. As soon as I had my phone back from repair, it still crashed.
I have also updated the phone with Samsung Kies, as shown in attachment 1
Now I don't know if I should send it back again, since they couldn't fix it in the first place, or to just live with it.
The phone's "About phone" page is attachment 2
Thanks everybody for taking the time to look into this.
It's the default ROM they put on again.
I have a friend with the same phone and her's is acting so slowly for such powerful device!
Try setting up a new ROM. I know it's hard, but it's better with the no-lag fix etc...
i heard Darky's Rom is really good, but I bet there are other ROMs who are amazing.
Tutorials are kinda hard to follow for that device, but you can do it
But putting a new ROM on it didn't help.
I can believe the default slows it down, but this problem started on the Darky's rom, and is also still happening with the default.
Is not so difficult, you can change a ROM in like 10min. Try to update your phone to ICS, I'm using ICSSGS and it's blazing fast
Enviado desde mi GT-I9000 usando Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Thanks I missed that one.
And thanks Dante for trying to help, but as I said before, changing the ROM did not help, nor updating it.
Anybody else any ideas?
...anyone?
Good Day, I'm hoping someone can help me, I've tried searching but I can't seem to find anything(mainly because I don't know the best way to describe it) sometimes, randomly the screen will turn off, as it should but then it wont come back on, I've installed the wake on volume mod and that doesn't seem to help.
Happened with CM7 and now with The darkside rom.
It's sporatic, it wont do it for like 10 hours then will do it 3 times in an hour.
Any help would be greatly appreciated
Thanks
Adam
Gweilo said:
Good Day, I'm hoping someone can help me, I've tried searching but I can't seem to find anything(mainly because I don't know the best way to describe it) sometimes, randomly the screen will turn off, as it should but then it wont come back on, I've installed the wake on volume mod and that doesn't seem to help.
Happened with CM7 and now with The darkside rom.
It's sporatic, it wont do it for like 10 hours then will do it 3 times in an hour.
Any help would be greatly appreciated
Thanks
Adam
Click to expand...
Click to collapse
I have a similar problem. But mine only happens when i make or recieve a call, doesn't do it everytime. I actually found a thread where it said it was possibly a broken proximity sensor. So the solution was to download 2 things from the app store and install them, and disable the proximity sensor. I am going to try that, cause when i make or recieve a call I actually turn my screen off so i won't hang up on anyone or hit several buttons. The solution they gave was to have a rooted phone, and download "android sensor box" so you can see the name of your proximity sensor, and then download "hardware disabler". Find the name of your proximity sensor and disable it. I have tried everything else, so what do I have to lose on trying this, lol.
Update, after several days i've found the culprit. There was an issue with my sd card, once I swapped it out haven't had a problem since
Sent from my MB860 using xda app-developers app
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.