Is it everyone or is it only me?
When I use the camera, I feel that the camera only captures about 2-3 seconds after. The camera is very slow too, why is this?
Any tweak to make the camera captures image instantly?
Here's a couple of reg hacks that I use.
[HKEY_LOCAL_MACHINE\Software\HTC\Camera\Captparam]
"EnableCapKeyDelay"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\HTC\Camera\General]
"DisableShutterSound"=dword:00000001
Lock Strength
Hello everyone,
Since I (like most of us, I guess...) don't like others messing up with my personal data, and since a phone is by its handheld nature prone to theft, I started using the "Device Lock" option: The idea was that if I have the bad luck that somebody steals (or even simply messes around) with my TD2, at least he won't be able to see anything inside it, as he will have to hard reset it to access it.
However, I was very underwhelmed when I read somewhere that the type of password I use (simple PIN), is subject to breaking via brute-force attack. This was really bad news for me, since the other type of password (strong alphanumeric) is totally useless, since it is completely cumbersome to use: The phone locks at each power off, so one is obliged to enter 7 characters every time he wants to access his phone, with the added twist that they have to include numbers or punctuation, meaning that the keyboard has also to be switched every time... Especially if you are in hurry (and since this is a phone, there are times that you ARE in a hurry), the alphanumeric keyboard is totally inappropriate...
I would like therefore someone to explain the extent of the vulnerability of the PIN passwordand whether it can be broken by somebody with average knowledge in these things: If it cannot, then I am happy with it, since I do not have any important secrets on my phone, and therefore no world-class hacker will probably have ever any interest in me . If it can though, then there is no need to use Device Lock, anyway...
Hey guys, remember those who used Tenfar's custom Recovery to format and partition their internal SD? Remember how it damages the touch screen response on the bottom half inch of the screen? Mine is fixed!!
I don't know what it does, but that particular function damages the PDS file. I've received help from a person who cannot be named and my AT&T Atrix is 100% fixed. Touch screen works flawlessly again, no Wifi issues, no Bluetooth issues and System Updates work fine.
He is working on scrubbing my personal data (serials, etc) from the PDS file and I'll be able to share it with the entire community. But if there's a dev out there who can contact me specifically I can send both the damaged and corrected file right now. I need help figuring out how to apply these serials to a blank PDS file so others in the community can fix this problem as well.
Out of respect, I will not name the person who assisted me as it compromises their work security. They went out on a huge limb and graciously assisted me without any reason other than they're a kick ass person with a huge heart. I'm no programmer by any stretch, but if anyone could assist me I know that there's about a dozen others (maybe more) who really need help fixing this issue. Someone please PM me if they can help!!
i messed up mine too...
any chance to get any help/solution?
One thing you could do is diff the two files to see if they're different. I don't know what the file is either though. Can you ask him how he fixed it? Also can you run the program strings against it? One other thing, is this fixed on changed partitions our did you change them back to the default?
Sent from my MB860 using XDA App
currently i'm in the situation that i can only flash my device, as i cannot complete motosetup, i cannot access debug option so no adb.
i read that the partition with the pds file has been already found
100% mmcblk0p3 PDS.bin 2097152 Persistent Data Storage
(from the atris sbf thread)
would be great to know what is executed in the script of tenfar for the internal sd partitioning, but my knowledge ends here.
so i guess (i'm everything but a developer )
if could be possible to flash/restore that partition with the nvflash selective option
or integrate it in a generic sbf, or the second init will save us all or the gingerbread update...dunno
but i see we are many we touched the wrong button but i don't see any dev interested here or in the thread of tenfar's recovery
i read that psd contains unique infos like the imei so maybe none of the devs wants to release a potential cloning system...
really i don't know even if what im saying is correct
bongd said:
Hey guys, remember those who used Tenfar's custom Recovery to format and partition their internal SD? Remember how it damages the touch screen response on the bottom half inch of the screen? Mine is fixed!!
I don't know what it does, but that particular function damages the PDS file. I've received help from a person who cannot be named and my AT&T Atrix is 100% fixed. Touch screen works flawlessly again, no Wifi issues, no Bluetooth issues and System Updates work fine.
He is working on scrubbing my personal data (serials, etc) from the PDS file and I'll be able to share it with the entire community. But if there's a dev out there who can contact me specifically I can send both the damaged and corrected file right now. I need help figuring out how to apply these serials to a blank PDS file so others in the community can fix this problem as well.
Out of respect, I will not name the person who assisted me as it compromises their work security. They went out on a huge limb and graciously assisted me without any reason other than they're a kick ass person with a huge heart. I'm no programmer by any stretch, but if anyone could assist me I know that there's about a dozen others (maybe more) who really need help fixing this issue. Someone please PM me if they can help!!
Click to expand...
Click to collapse
I am willing to help. This should be relatively easy to do.
in android recovery touch screen works correctly till the bottom, menu/ok button too.
the problem is in the os i guess, but damn i cannot use adb (no debug), seems that neither the early usb+shell root works for me...i can only flash using rsd
and after flashing stock rom i'm stuck at the damned motosetup
maybe are useful infos for you
god knows how i'm desperate
edit i'm reading that for old motorola phones like v3 exist a flashbackup and a psd editor, used to unlock the phones but also to revive damaged ones. maybe...
I've got my original corrupt PDS at home as well as one which has been corrected from a legit developer (can't release any of their information due to work employment security concerns).
I guarantee that it has been 100% fixed though. Bluetooth works, Wifi works, cellular data works and I was even able to upgrade from 1.26 to the latest AT&T OTA update and root everything.
When I announced this no one gave a **** so I didn't make a fuss. I know there are still a few bros with this problem though. I sent my PDS files to another member and they're looking into it. Hopefully you guys can get this working for yourselves as well!
dear friend you are promising salvation with your words, but you're not helping too much...
you gave the phone to that developer, he told what/how he solve the problem?
i understand psd is based on personal imei, so your fixed one is not working on mine etc etc
the point is that possibly your friend as legit developers has access to software to create/flash psd to the atrix.
the question is would be possible to receive the same helping hand?
there is no support in my country for this phone, and i'm not a dev.
so the only chance for me and the rest of the halfbricked people is to get the tools and the tutorial how to from you/your friend.
do you think it is possible?
KeRmiT80 said:
dear friend you are promising salvation with your words, but you're not helping too much...
you gave the phone to that developer, he told what/how he solve the problem?
i understand psd is based on personal imei, so your fixed one is not working on mine etc etc
the point is that possibly your friend as legit developers has access to software to create/flash psd to the atrix.
the question is would be possible to receive the same helping hand?
there is no support in my country for this phone, and i'm not a dev.
so the only chance for me and the rest of the halfbricked people is to get the tools and the tutorial how to from you/your friend.
do you think it is possible?
Click to expand...
Click to collapse
Sorry, I'm not helping much? I'm NOT A DEV!!! I have no obligation to help anyone whatsoever. I lack the technical know-how to help anyone. Please don't ****ing test me.
I've begged every Atrix developer here for help - NO ONE helped other than Tenfar. And unfortunately his advice took me in a completely different direction. No one can point a finger at me for not trying my best. I was so desperate that I got another Atrix because mine was dead for over a month before it was revived.
meneomic has been working feverishly to get his Atrix working as he's encountered the same problem. I've sent him my original and damaged PDS, as well as the one which has been corrected. The strings are not in plain text format and when I viewed it in a Hex editor I found nothing useful. That's all I can do. If someone knows how to put the IMEI and other serial numbers into the fixed PDS they can write it to the appropriate block and this problem will be fixed. That's all that needs to be done... but that alludes me.
I realize there are some people who are upset that their Atrix's aren't working after messing around in the recovery menu, but I've done my best. I have literally stayed up for days working continuously on this. My wife nearly smashed both my Atrix's in frustration because of all the time I've invested in it. I've done what I could and unfortunately got no where.
/rant
bongd said:
Sorry, I'm not helping much? I'm NOT A DEV!!! I have no obligation to help anyone whatsoever. I lack the technical know-how to help anyone. Please don't ****ing test me.
I've begged every Atrix developer here for help - NO ONE helped other than Tenfar. And unfortunately his advice took me in a completely different direction. No one can point a finger at me for not trying my best. I was so desperate that I got another Atrix because mine was dead for over a month before it was revived.
meneomic has been working feverishly to get his Atrix working as he's encountered the same problem. I've sent him my original and damaged PDS, as well as the one which has been corrected. The strings are not in plain text format and when I viewed it in a Hex editor I found nothing useful. That's all I can do. If someone knows how to put the IMEI and other serial numbers into the fixed PDS they can write it to the appropriate block and this problem will be fixed. That's all that needs to be done... but that alludes me.
I realize there are some people who are upset that their Atrix's aren't working after messing around in the recovery menu, but I've done my best. I have literally stayed up for days working continuously on this. My wife nearly smashed both my Atrix's in frustration because of all the time I've invested in it. I've done what I could and unfortunately got no where.
/rant
Click to expand...
Click to collapse
Chill out buddy....
Atrix ~_~
tons of words but nothing useful guys
leaving the good manners debate aside for one moment...
bongd you say you have the 2 file corrupted and corrected, but someone had to flash somehow/somewhere into your phone. who? you or your friend? what did he use to manipulate? can you ask him or not?
second easy group of questions for every dev out there,
-not interested because no reward (for the moment)?
-not interested because impossible?
-not interested because xxxx?
i'm trying to understand please...
msd24200 said:
This forum has young people, even children on it and all tho I hope you guys get this fixed you have to watch the language!
Click to expand...
Click to collapse
KeRmiT80 said:
tons of words but nothing useful guys
leaving the good manners debate aside for one moment...
bongd you say you have the 2 file corrupted and corrected, but someone had to flash somehow/somewhere into your phone. who? you or your friend? what did he use to manipulate? can you ask him or not?
second easy group of questions for every dev out there,
-not interested because no reward (for the moment)?
-not interested because impossible?
-not interested because xxxx?
i'm trying to understand please...
Click to expand...
Click to collapse
I sent my broken file to dev, he fixed it and I flashed it.
There was no exchange of phones, nothing special done, etc. I just used the dd command to write the fixed PDS file. How it was fixed, I an uncertain. I've tried for days and days to no avail. This is what you guys will have to figure out. I've invested too much time and already have a fixed phone which was sold to a friend.
If anything from that phone is needed for whatever reason, it's been sold to a coworker and I can obtain it any time.
ok we are talking now
the question is how did you extract that file?
i don't have adb access because after partitioning my phone failed to boot and i had to flash stock rom. now i cannot pass the motoblursetup (no wifi-no data, i'm stuck there) so cannot enable debugging
KeRmiT80 said:
ok we are talking now
the question is how did you extract that file?
i don't have adb access because after partitioning my phone failed to boot and i had to flash stock rom. now i cannot pass the motoblursetup (no wifi-no data, i'm stuck there) so cannot enable debugging
Click to expand...
Click to collapse
Yes you can. To bypass the motoblur activation type this when you are on the select language screen
Fn,E,Fn,E,B,L,U,R,O,F,F
Hold the Menu button to get the keyboard to pop up. That should work.
This will allow you to get to Settings > Applications and enable USB Debugging. Just make sure not to click on the wrong icon because you can't close a program once it's opened because of the bottom portion of the screen not responding.
I had to battery pull about 500 trillion times doing different things to fix this.
If you write my PDS it will fix the screen, but of course the serials will all be incorrect. And I don't know what this could do so I'd not recommend it.
mmm my phone recognizes the menu button as the bottom of the visible screen so pressing menu results in selecting the emergency call, pressing search button moves me to "next", the home or back button in the middle bottom of the visible screen...
KeRmiT80 said:
mmm my phone recognizes the menu button as the bottom of the visible screen so pressing menu results in selecting the emergency call, pressing search button moves me to "next", the home or back button in the middle bottom of the visible screen...
Click to expand...
Click to collapse
Hold the menu button down until the keyboard pops up and give this a shot.
I'm positive you'll be able to.
Please stop the foul language. Thanks.
according to this thread http://forum.xda-developers.com/showthread.php?p=15026407
you just have to open adb shell and run
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
anyone backed up this partition??
I need it badly
tan G said:
according to this thread http://forum.xda-developers.com/showthread.php?p=15026407
you just have to open adb shell and run
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
anyone backed up this partition??
I need it badly
Click to expand...
Click to collapse
maybe you will find what you are searching about there: http://forum.xda-developers.com/showthread.php?t=1035228&page=4
gitbrew.org is down for now
http://dev.gitbrew.org/~dasmoover/android/atrix/atrix-devkit-fs.tar.gz
do you have this file on your computer?
Hello, I have an xt1080m, otherwise known as droid maxx on verizon. same guts, more or less, as ghost, and in fact i am running a ghost rom (AOKP MM) and the ghost TWRP 3.1.1 over in the development forum here.
when i attempt the move to an N rom, it usually flashes and boots without any problems, except my touchscreen records my touches as if it's been flipped across horizontal and vertical symmatries, ie top left touch reads as bottom right. worse, this persists upon reboot in twrp until i wipe it and reinstall MM.
****i am not asking for anyone to hold my hand and hold anyone who answers the next question free of any liability or even obligation to communicate with me ever again, right now before the public of xda.****
is there a config file somewhere or a kernel/mod config i can edit to instruct the sensor to read in an unflipped manner? if so, where is it? any syntax you could include would be appreciated,
Thanks
found a solution
Hello. After a few weeks reading posts here at XDA and Oneplus Community and having tried many possible solutions unsuccesfully I have given up and decided to post requesting fo help.
I've had a oneplus 3T for a couple of years, recently a section of the touchscreen became unresponsive: the area that matches the optional software buttons section at the bottom of the screen. I enabled pointer location in Dev Options and was able to confirm it.
I made factory resets, restored various TWRP backups since I do them on a regular basis, tried different kernels, etc. Nothing worked.
I wiped the phone completely and installed OOS 5.0.6 from scratch via the manufacturer's recovery. After this the affected area came back to life. "Software issue solved" I thought, but a new problem in the same area appeared a few days later.
After enabling "show taps" in dev options I was
able to define it correctly. The screen catches a fake tap in the previously dead area when touched in any part at the lower half of the screen, lets say the area used by the keyboard. The worst is that it gets stuck like if I were keeping my finger pressed. Then I won't be able to use regular touchscreen operations unless of course the +1 fingers operations like pinch for zoom, and using one finger less because it's already pressed once. See bottom left in the attached screenshot.
To remove the "sticked" dot I just have to tap on it, drag it to any other area of the screen and it desappears. It's vey annoying. It happens now and then, after a few normal touches. No pattern. I have disregarded the hardware fail since after flashing and for a few days there was no poblem at all.
Any help, no matter how simple it looks, will be very appreciated.
Hello, I'm a junior member here, I learned a lot from XDA as I read many threads but only have posted a bit.
My Note5 has been showing touchscreen malfunctions for a while, nowadays I'm using the S-pen. The first time I realized I tried to wipe the cache, and it didn't work. I booted into safe mode but it didn't fix it. I realized it was a hardware related thing. Then I tried to remove the screen protector, it did work, but not much later it happened again. I cleaned my screen and it worked (and start malfunctioning again minutes later).
I concluded that the oil from my finger was the problem, but unlike any other phones I've had, the touch begins to malfunction just because of a very tiny amount of grease build up.
(for example, if there's a small build up on the 'A' key on the keyboard, whenever I touch other areas, the 'A' key will also recieve touch input.)
I think tuning the touch sensitivity will help. So I asked for help here.
Was my conclusion wrong or is there any solution that requires no rooting?
aydanjr said:
Hello, I'm a junior member here, I learned a lot from XDA as I read many threads but only have posted a bit.
My Note5 has been showing touchscreen malfunctions for a while, nowadays I'm using the S-pen. The first time I realized I tried to wipe the cache, and it didn't work. I booted into safe mode but it didn't fix it. I realized it was a hardware related thing. Then I tried to remove the screen protector, it did work, but not much later it happened again. I cleaned my screen and it worked (and start malfunctioning again minutes later).
I concluded that the oil from my finger was the problem, but unlike any other phones I've had, the touch begins to malfunction just because of a very tiny amount of grease build up.
(for example, if there's a small build up on the 'A' key on the keyboard, whenever I touch other areas, the 'A' key will also recieve touch input.)
I think tuning the touch sensitivity will help. So I asked for help here.
Was my conclusion wrong or is there any solution that requires no rooting?
Click to expand...
Click to collapse
Type *#2663# on your phone. And press "TOUCH KEY FW UPDATE".
iminer said:
Type *#2663# on your phone. And press "TOUCH KEY FW UPDATE".
Click to expand...
Click to collapse
Nice, it works! But may I know why did it happen? Perhaps I can prevent it in the future. What happened?
(Update) The screen malfunctioned again. I tried to update the touchscreen firmware again and nothing happened. I was thinking wether flashing a custom kernel and ROM would fix this or not, should I?
Replace the phone, could be the screen or the motherboard. Don't bother fixing it.
cachanilla86 said:
Replace the phone, could be the screen or the motherboard. Don't bother fixing it.
Click to expand...
Click to collapse
The weird part is it does work perfectly sometimes but most other time, it doesn't. I'm going to do a factory reset tonight to see if it works or not, or to decide wether I should flash a new ROM or not.
In my place here, a nearby retail store is willing to buy my Note5 for around $130, pretty sad to know. I love the S-pen but can't afford the Note 9 nor the Note 8. Should I buy a Samsung tablet with an S-pen instead?(it's currently on 25% discount).
Update: Is it a coincidence if the touch is problematic during heavy task (e.g. multitasking, running demanding apps, or playing games) and working fine during standby or light tasks?