Database Develop

Home, Talk buttons non-functional.

In addition to the home and talk buttons not working. The phone will not lock when I hit end, it just puts into a sleep mode.
Holding end only gives a reboot and shut down option. This problem surfaced after installing the new SuperD mod. I did a wipe and reinstalled it two nights ago and the problem was resolved, but it has resurfaced tonight.
Anyone have any thoughts on the matter? Should I go back to the old version?

Which new version? The beta or 1.10.2? If it's beta - then you def should go back to stable. If it's 1.10.2 - then you most likely have a hardware problem. A lot of people run Super-D with no problems.
Further more, sometimes your trout-keypad-v3.kl (located in /system/usr/keylayout/) can get corrupted and cause that. It's extremely rare but you may try either re-flashing or just pushing that specific file.
Word of advice (which you may already know): if anything goes wrong and you want to rule out software problem - install a base rom (like the defanged from Cyan's wiki), complete wipe and min options (no Apps2sd, no swap, etc) and see if it fixes the problem. If the problem is gone - you're in lock and something went wrong with the rom. If problem is still there- start looking for a new phone.
Good luck.

I did a fresh install. I repartitioned the sd card, reinstalled all apps. did a factory wipe, reinstalled the base defanged, then did super D. It wasn't the beta, i had upgraded to 1.10.2 and experienced the problems.
It would work fine for two days, then if my phone would shut off (battery has weird contacts) then it would boot back up and my settings would be all messed up, and the keys would work. I would try re installing the ROM, but no fix.
A wipe remedies the problem. I went back to cyanogen last night to see if the problem appears on this rom, so far it hasn't.
I never had this problem until i upgraded from 1.9.3

[Q] Help Proximity and Position Sensor not working

Since i've update my SGS to android froyo the Proximity sensor stoped working and the position sensor taken 30sec to turn the image...
I've used the test mode code to check hardware error, but there everything is working perfectly...
If I put the Android 2.1 the problem doesn't show up.
Does anyone have the same problem or solution?

Nobody has this issue?
Is quite strange... because if i put a Android 2.1 ROM everything works just fine, but with later version of android the sensors still working (using test mode from SGS Tools, I confirmed that the sensors are just fine), but the system takes a huge time (~30sec) to do something...
Please, if anyone knows anything that could solve this problem, please say something!
I think that in the first week that I had Froyo everything warked fine, but I'm not sure...
Is there any way to do a complete reset and set everything to default values including Hardware settings?
I've already done Factory reset and Full factory reset, by CWM and Code.

Nobody??? Anything???

Is this a genuine samsung rom you are using .
A flashed rom or a genuine Kies updated firmware .
jje

I'm now using a ROM official (sam***gfirmwares.co*) flashed by ODIN.
Should I try use Kies?

No i was just trying to rule out a flakey rom .
My usual suggestion is a wipe via ODIN
http://forum.xda-developers.com/showthread.php?t=882014
But i would stop at Eclair and see if its solved the problem if OK upgrade further .
jje

Its the same thing...
Its quite awkward, because only apendds in Froyo...

why not try a custom froyo rom, head over to doc's kitchen and cook yourself one up. also try lagfix, and any other speed up tweaks. how does the phone respond normally ?? without the sensors ? is it quite speedy or does it lag ??

The phone work just fine but when i turn the phone it take a lot of time to twist the image... I can even still interact with the screen until it turns...
The proximity sensor takes a lot of time too...

No one else has this problem?

[Q] problem with touch

when I touch the screen or use swype the touch is not recognised properly and it jumps around quite a bit.
Dont know why its happening but im on 2.3.3 rom and I did install the with bootloader version.
Been working fine since this morning but its getting more and more tempremental and I havent made any changes either.
Anyone know what could be wrong?

you'd better flash to any froyo rom,if the issue is still happen,your phone may have a hardware problem

Factory reset first .
jje

[Q] Various Issues - Tried different ROMs but issues remain

Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc

Experienced flasher, soft-bricked my Note 4 real good.

Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?

My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!

Thanks. I might just send it into samsung and see what happens.