It seems that my menu and back button is possibly broken cause it is not working in "some time". Working then few min, not working.
So is it a hardware problem? or firmware problem? possible conflict in firmwares? I noticed it when i flashed DXLC1 from DXLB1. I've try hybrid v3.0 and repencis v3.0, same problem occurred.
Anybody have the same problem?
makeoutactics said:
It seems that my menu and back button is possibly broken cause it is not working in "some time". Working then few min, not working.
So is it a hardware problem? or firmware problem? possible conflict in firmwares? I noticed it when i flashed DXLC1 from DXLB1. I've try hybrid v3.0 and repencis v3.0, same problem occurred.
Anybody have the same problem?
Click to expand...
Click to collapse
I dont think flashing would damage your buttons. Its not the problem with only you. It happens with me too but a restart resolves it. Have you ever dropped your phone or something?? That could be the only possible reason for that problem
if only they put the question if FAQ section...this forum will looks nice and they'll get the answer.
hell_lock said:
I dont think flashing would damage your buttons. Its not the problem with only you. It happens with me too but a restart resolves it. Have you ever dropped your phone or something?? That could be the only possible reason for that problem
Click to expand...
Click to collapse
Never been dropped. Yeah restarting resolves it temporarily,for me, then it will come back again.
search a post about cleaning the screen in accessories secction. read the method suggested below. try it.
kurotsugi said:
if only they put the question if FAQ section...this forum will looks nice and they'll get the answer.
Click to expand...
Click to collapse
Oh. wrong post? Can mods merge it? or perhaps delete this thread.
kurotsugi said:
search a post about cleaning the screen in accessories secction. read the method suggested below. try it.
Click to expand...
Click to collapse
Thanks, i will try it. I'm out of thanks. Will press it tomorrow.
no need to do that...give your thanks for the real dev instead of me
Related
My P3300 can't open. When ı connect to charger no light coming. Press to Power or reset can't open(with sim or without sim). Also ı have one more P3300. so I tried to battery. It has not any problem at the battery.
hhhmmm
There are some amazing guys in this forum but I dont think any would be able to help you because this sounds like a hardware problem...
i was thinking maybe u have problem with ur charger but hence u said u tried a different battery then i will rule that out
did u install anything recently
any recent flashing (rom details)
dogus06 said:
My P3300 can't open. I tried to charge no light. Press to Power or reset can't open(with sim or without sim). Also ı have one more P3300. so I tried to battery. It has not any problem.
Click to expand...
Click to collapse
jahrami said:
i was thinking maybe u have problem with ur charger but hence u said u tried a different battery then i will rule that out
did u install anything recently
any recent flashing (rom details)
Click to expand...
Click to collapse
I have flashed with "Carty' Fastest WM6.1 - Artemis" But It was working after flashing.
dogus06 said:
I have flashed with "Carty' Fastest WM6.1 - Artemis" But It was working after flashing.
Click to expand...
Click to collapse
EDIT : "My P3300 can't open" is Won't start?
I though it was can't charge or something... Sorry
My opinion is that the motherboard is dead.... If nothing happens, then is a failure in the hardware.
Well.. Hence it's dead you can try out two things that can solve some (not all) hardware failures. But only if it's out of waranty.
First : Try to search for sticked keys. Then give your PDA some spanks (Sometimes can solve bad connections problem).
Second: You can try to open it and clean it up. That whould be your last choice because you have to do it very carefully. See here how too:
http://wiki.xda-developers.com/index.php?pagename=Artemis_Disassemble
Cheers
Zecanilis said:
EDIT : "My P3300 can't open" is Won't start?
I though it was can't charge or something... Sorry
My opinion is that the motherboard is dead.... If nothing happens, then is a failure in the hardware.
Well.. Hence it's dead you can try out two things that can solve some (not all) hardware failures. But only if it's out of waranty.
First : Try to search for sticked keys. Then give your PDA some spanks (Sometimes can solve bad connections problem).
Second: You can try to open it and clean it up. That whould be your last choice because you have to do it very carefully. See here how too:
http://wiki.xda-developers.com/index.php?pagename=Artemis_Disassemble
Cheers
Click to expand...
Click to collapse
Thank you for your opinions. But ı have bought it one weeks ago. So warranty time is not finished yet.
If you have flashed the ROM will that not void your warranty?
ednap said:
If you have flashed the ROM will that not void your warranty?
Click to expand...
Click to collapse
But it can not open. So ı think technicial services can not understand the flashed.
dogus06 said:
But it can not open. So ı think technicial services can not understand the flashed.
Click to expand...
Click to collapse
Good luck then. Hope you get it up and running again quickly.
Do you know HTC Repair Center in Leipzig/germany or Bologna/Italy.
i have successfully booted android many times without this problem, but ever since i switched to BLAZRs 2.2 build, my phone wont wake up after it goes into standby mode. i already tried to solve this problem by removing the p.m. sleep=x from my startup.txt. is there anything else that could be causing this problem? oh, also, my battery was fully charged for all this
set pm.sleep_mode=2
That is the same line of code that i deleted to try to fix the problem! But i will try putting it back in and see what happens. If this fails to work, what else could be the problem?
queleb said:
That is the same line of code that i deleted to try to fix the problem! But i will try putting it back in and see what happens. If this fails to work, what else could be the problem?
Click to expand...
Click to collapse
Try to reinstall android.. Id recommend you to use the .rar
Sent from Froyo 2.2 using XDA App
queleb said:
That is the same line of code that i deleted to try to fix the problem! But i will try putting it back in and see what happens. If this fails to work, what else could be the problem?
Click to expand...
Click to collapse
uhhhhhhh deleting command lines isnt going to help dude. lol
It doesnt wake up because you deleted sleep_mode=1.... thats the default, so deleting it means it stays on sleep mode 1. If youre using the BLAZN, with the overclock, it needs to be at sleep_mode=2.... You NEED the code in there or, you need to remove the overclock line.
It says all of this in the FAQ by the way.... you could have saved time fixing your problem and avoided posting a thread for a questions that's already been answered.
Here is the FAQ. I suggest you read it, you may not be as lost.
http://sites.google.com/site/androidport/faq
Just put the code back in and it worked. And for the record Reefermattness, I DID look at the FAQ before I posted, and the information was misleading about deleting the code to disable deep sleep. That is why I posted, so don't get all butt hurt; I know the rules.
queleb said:
so don't get all butt hurt; I know the rules.
Click to expand...
Click to collapse
LOL ok.
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.
Hi guys, yesterday i flashed a stock image for my galaxy nexus maguro, because i had 1 problem..
But the problem is still here, and now i have another one..
The 1st problem : When i call somebody or i receive a call, the earphone (or however it is called) doesn't work, the mic not work too, but this happes the most time, and sometimes it works well...
[The 2nd problem : My camera app seems to take pictures, but there is nothing in the gallery... it don't even save the photo in the memory..] <---- SOLVED BY WIPING THE INTERNAL STORAGE !!
For both problems, they happen on any rom...
Actually i'm on Vanir Rom..
Please guys help me :/
follow the return to stock guide in my signature. do not skip any steps.
Zepius said:
follow the return to stock guide in my signature. do not skip any steps.
Click to expand...
Click to collapse
I solved my 2nd problem by my self, i don't know why, but my internal storage was locked, i was't able toi write anything on it.. i just wiped it throught the twrp recovery, but still the 1st problem is still here... and it's really anyoning.. :/
martinko23 said:
I solved my 2nd problem by my self, i don't know why, but my internal storage was locked, i was't able toi write anything on it.. i just wiped it throught the twrp recovery, but still the 1st problem is still here... and it's really anyoning.. :/
Click to expand...
Click to collapse
might be a hardware issue; still, have you tried flashing another baseband, just to see if it changes anything? and please, don't ask me on how to flash a baseband, plenty of guides around here (hint: stickies, general and q&a forums)
beekay201 said:
might be a hardware issue; still, have you tried flashing another baseband, just to see if it changes anything? and please, don't ask me on how to flash a baseband, plenty of guides around here (hint: stickies, general and q&a forums)
Click to expand...
Click to collapse
I'll look at that thanks...
But how it can be a hardware issue ? Sometimes it work all fine, sometime not...
martinko23 said:
I'll look at that thanks...
But how it can be a hardware issue ? Sometimes it work all fine, sometime not...
Click to expand...
Click to collapse
iminent hw failure?
beekay201 said:
iminent hw failure?
Click to expand...
Click to collapse
oh :/ You think it can be fixed somehow ?
martinko23 said:
oh :/ You think it can be fixed somehow ?
Click to expand...
Click to collapse
replacing the damaged hw component? maybe the ifixit guys have a tear down.
beekay201 said:
replacing the damaged hw component? maybe the ifixit guys have a tear down.
Click to expand...
Click to collapse
Okay thx, i'll take a look at it, but now i'm going to try the baseband thing.
Phone WAS soft bricked. Could only boot into fastboot because recovery and OS were both deleted. Using the hard brick guide worked like a charm
Crisschan said:
fixed.
Click to expand...
Click to collapse
LOL!
Leaving the original post and adding how you solved the issue would have helped someone else facing the same issue. Instead you had to go and delete the OP itself!
tnsmani said:
LOL!
Leaving the original post and adding how you solved the issue would have helped someone else facing the same issue. Instead you had to go and delete the OP itself!
Click to expand...
Click to collapse
Right sorry! I'll get to fixing that