yashsingh1/xdaforums huggingface dataset:
[Android General] kestrelv2:
Have you not noticed the biggest issue of all, i cant beleive everyone that reviewed it has missed it. The touch screen lags or the display is lagging im not sure but scrolling is not smooth. You notice it big time in games. When aiming at tanks in world of tanks you cant aim at anythign properly you slowly move your finger to aim and it jumps. Imagine a square being on screen and trying to aim at something within that square but it will only jump to the outside of that square weather its up down left or right. Its totally f**ked. I actually came here hoping some magical xda user could fix it since elephone are useless. Gps is glitchy, ecompass doesnt work and they now claim it DOESNT have it. Lollipop was advertised as comign with it later change to an update over the air then saying its not even available yet some unspecified time in febuary. Everything about this phone is a joke how can they release a phone with a glitchy touch screen.

Try it for your self you will notice is big time in world of tanks or a similer game where you must aim, also when using any browser but to a lesser extent. users have tried different home apps so its not that. Elephone speak broken english and simply do not understand what anyone is saying so i dont have high hopes of it being fixed.

If reviewers on youtube had ACTUALLY mentioned this fault instead of covering it up because they got a free device i would not have bought this device.

http://bbs.elephone.hk/thread-1815-1-1.html#.VMazxy6JK70

http://bbs.elephone.hk/forum-156-1.html#.VMa1vy6JK70

[IMG="screenshot"]http://bbs.elephone.hk/data/attachment/forum/201501/26/161512yztjy5zq583djj13.png[/IMG]

A user there posted a perfect image of the screen touch lag.
[Android General] semo.pz:
[MENTION=4986108]kestrelv2[/MENTION]

Thank for the input. I think s7yler hinted to something like this in his review and now it makes more sense with your description.

I feel your frustration! GPS and bluetooth are usually the classic things that cheap Chinese phones always screw up. I think I will give this phone a miss. Why is it so hard to find 64 bit phones (not phablets) with decent amount of RAM and a removable battery?
[Android General] kestrelv2:
MTK devices always suck with gps this is nothing new anytime they say it is fixed it turns out to be a lie and is only slightly better than the previous chipset i can actually see satellites with this chipset where as with a phone with mtk 6592 and 6589 i could not. If i were you id keep watching this device to see if the major bugs are fixed but i wouldnt touch it with a large stick until then, just ignore all the lie reviews because they are misleading you and many of us had to learn the hard way. I have yet to test bluetooth i hope it works okay because i have a bluetooth set of earphones that i use when using google maps for navigation on my motorbike.
[Android General] greekfragma:
Dude it is a very new smartphone with lots of new hardware chipsets. For starters try to calm down because raging like this does not help.

Be patience about their fix that is on its way since couple of days earlier and see how it goes when it is ready.

My P6000 doesn't have a screen lag or if it exists it is so weak that I do not notice it. So please do not take for granted every user review experience you see on the internet. Maybe some P6000 have the issue and others don't.

I really do not like your tone accusing reviewers that made an effort to introduce you to a new product, and all you have to say is they said nothing to get a free device.

Stay put and have patience.
[Android General] kestrelv2:
How is that an excuse. A new phone is not an excuse for releasing a phone with a broken touch screen. It is just about usable for browsing it is not useful for anything else. Outrage certainly helps because it lets elephone know it isnt acceptable and gets them off their asses to fix the issue.

Everyones p6000 has the issue just because you have yet to notice does not mean it doesnt exist and the problem with getting a fix for a known issue is apathetic people like YOU, people have spent money on a device with an unreasonable amount of bugs and a major touch screen issue that has already been acknowledged by elephone. You tell me that complaining about an issue doesnt help no that is utterly stupid pretending the issue isnt there is what DOESNT HELP. If they think the issue doesnt exist they obiously wont fix it. Maybe you should actually use the dev options and try the same test everyone else on the elephone forum has done because everyone that did it noticed the problem immediately.

If you dont like my opinion on the 90% of reviewers who blantently lied for elephone after recieving a free device from them to review tough there is nothing you can do about it. I wont be slienced the phone is bugged and i wont shut up until the issue is address i dont waste money on a device to have to wait for the most basic function to work as it should do at release.
[Android General] bigrammy:
Did you completely remove the factory the screen protector. Not just the top one with the tab on it :confused:

Totally remove it and try it then. :fingers-crossed:

They don't put quality protectors on cheap phones.

CHEAP been the key word here. You could of paid $800+ usd for a iphone and have it snap in your pocket or not be able to make a call even.

I dont know what people expect from a $150 usd phone. :laugh:
[Android General] kestrelv2:
Iv had both a lenovo a820 and a thl t100s before this both have lasted without any issues and are still in my draw working fine. Both are well under $150.

Lenovo is a chinese brand that started only in china and is now the the 2nd if not the largest manufacturer of android phones today. Xiaomi isn't far off and is owned by an American The more you know.

The only difference between big names and chinese names is support and updates and after having owned an lg optimus 2x for 2 years i discovered that support line isn't so different. If you have misplaced distaste for Chinese products stay out of a topic talking about a chinese product nothing in your post was any help at all.
[Android General] justmpm:
I think everybody understands the frustration of getting a new device and then having something not work exactly correctly out of the box. As far as I know nobody guarantees their review to be spot on accurate, but your device should be guaranteed by the manufacturer, so it is best to take out your frustration out on them.

I really don't want to clean this thread, it is important that the good things and the bad things about a device come to light, if it isn't the review then post your own observations about the device, but please watch the swearing and replacing some letters with *'s is really still swearing.

Thanks!
[Android General] greekfragma:
Mic and Speaker Values on my P6000

Here are the Microphone and Speaker Audio Enhancement values that were asked from many people with problems. These are the values directly from my P6000 engineering mode right out of the box and I didn't touch anything because my phone mic and speaker volumes are working great. [MENTION=5143043]vicmaffia[/MENTION]

Mic

Speech Enhancement
[Android General] justmpm:
Well...I see my last post didn't help very much...and I ended up cleaning the thread. It is perfectly OK to have differences of opinion and it is even possible to discuss these differences. However, it seems I must remind everyone about xda rule 2:

Member conduct.

2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please consider who is reading what you write and don't use profanity, sexually explicit language, rudeness or swearing including the use of characters to replace letters in swear words. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

2.5 All members are expected to read and adhere to the XDA rules.​

Seriously, xda has a pretty low tolerance of personal attacks, name calling and one-upmanship. If your post is not helpful, please think twice (or three times :D) before hitting the submit button. Please consider this your final warning.

Thanks!
[Android General] vikmaffia:
Touchscreen sensitivity increase

Hey, I've found that if you use more than one finger, the resolution of the touch screen increases.

You can test it with the developer menu as well as in the Engineering mode.

The more contact points you use, the smoother the scrolling becomes in browser too! Unfortunately you cannot use this trick in some games...

But the good news is that it's not hardware related and as such it can be fixed easily :)
[Android General] xenonism:
Hardware issues and chances that they can be solved

I'd say there are three outstanding issues with the P6000 right now: lack of smoothness in touch screen interactions, the compass and the OTG function.

The screen issue has been acknowledged by a company rep and he promised a solution soon:

I don't know what TP is supposed to mean, but I would focus on the other two issues.

OTG

Situation: OTG works only if the connected USB device is powered externally.

Elephone's position:

Interesting facts:

Compass/Magnetic Sensor

Situation: Applications detect the sensor but are not able to use it.

I'm not allowed to post links but there's a screenshot of the compass being detected in the review on chinaphonearena, page 2.

Elephone's position:

Interesting facts: It seems unlikely that we simply "don't have" the hardware component if it's detected by software tools.

So, my question to those who know the hardware better than me is: is there any chance the the truth is better than Elephone's current position on these two issues?
[Android General] s7yler:
If we then set that to yes will it then work?

Regarding the sensors, Test apps can also show wrong info. Like CPU-Z always shows phones to only have a 1000 mah battery, or Antutu that shows some phones to have more sensors or higher resolution that they in fact have.
[Android General] xenonism:
About OTG, I don't know. :) In any case, in my understanding it's not an option a user can change, but a compiler flag like the ones set in the configure file in a *nix environment.

About the sensors, I agree, which is why I hope someone has the knowledge to shed some light on the situation. ;)
[Android General] s7yler:
Actually, I'm a reviewer and I DID mention it in my review. http://www.youtube.com/watch?v=NPAp4AUEdqY#t=10m15s at 10:15. I even show this clearly, so you should just check reviews better then!

But besides that, the GPS navi is working fine. You don't need compass for good GPS navigation. The compass is also not good in the P3000S, but still it navigate perfectly fine as you can see in my test video here http://www.youtube.com/watch?v=Yp1HyOQCS1c (it is similar in the P6000, but the P6000 also support GLONASS)

And Elephone speak and understand English just fine and they do work on it. I understand that your frustrated, but please remember that this is also one of the first phones with the new chipset, so you should expect some bugs in the beginning - and I am sure that the screen jumps has something to do with the software and not a hardware/screen problem.
[Android General] greekfragma:
Hello guys.

For starters I am glad the topic was cleaned and we can now discuss calmly.

Now the important things are of course

1) the screen smoothness,

2) otg proper function

3) ecompass and magnetic sensor

I am 100% sure that screens smoothness is software related and has to do with the phone reading the correct number of touches on X, Y axis of the screen in accordance to the refresh rate of reading the touch. As another guy told earlier if you press with 2 fingers smoothness come to normal. So my guess is that the reported refresh rate/speed that the phone is reading on touches has a wrong value and can be fixed with just some testing on different values. On Elephone tech support the admin stated that they are aware of the issue and they will fix it in 2 days time.

About OTG function. Also here a software issue. You just change the value to

data\misc\ProjectConfig.mk and find string MTK_OTG_PMIC_BOOST_5V = YES and it will be ok. If changing that doesn't fix the issue then either needs also an updated firmware that coordinates with the chipset command, or we are being tricked by Elephone and we should at least ask for a replacement phone because OTG is one of the major things to advertise on a phone and not a minor mistake that noone cares about.

About the last problem of the compass and magnetic sensor what s7yler says is correct. Many programs report wrong results when reading. My opinion is that the latest 64bit Mediatek chip the P6000 uses IS CAPABLE of e-compass and magnetic sensor but only if the hardware is added on the device. So the problem here is that the sensor tests read directly from the Chip (to get values of sensors supported) but not the real added ones. And my thoughts is that here we can do anything since Elephone support now says that ecompass and magnetic sensors are not included. I hope I am wrong but I the possibilities are against us.

To conclude all the above. Screen and OTG most possible will be fixed in 2 days time but for compass and magnetic will not. We bought a very cheap phone, with good build quality and specs for the hardware it has. Expect it to run good only after the first problems are fixed and do not have the illusion that you got a big brand flagship killer. For the price it is far more than good ;)
[Android General] mark manning:
Ok guys I removed a few more posts...

Here is a word of advice if you come across someone you don't like or get along with on the forum, just add them to your ignore list. Furthermore, the name calling and badgering needs to stop period. My team and won't be happy if we have to come in this thread again. This goes for anyone who might be involved.
[Android General] bigrammy:
Agreed. :good:

Hardware is very good :good:

Firmware very very poor :(

Lenovo, Asus, Acer and more all use this mt6732 now so the good news is we will hopefully be able to get the source code pretty soon and can then start to fix things in the kernel and also start porting over ROM's which is probably already well underway.

I dont expect much from Elephone by way of development but this is a perfect phone for beginner devs with it's good hardware spec's and a very low cost. ;)
[Android General] vikmaffia:
Touchscreen sample rate with multitouch

Someone was disputing that using more fingers makes scrolling smoother. So instead of talking into thin air, look at the screenshots. You can clearly see that the samples are denser in case of multitouch. Conclusion: not a HW issue :)
[Android General] kestrelv2:
One of the admins already said it is an issue with the touch panel firmware. He said around 2 days but its day 3 going on day 4 and he has not responded, it doesnt make a difference how many fingers you are using they are narrower likely because you went faster with more fingers. Otherwise you wouldnt notice it in games as much since that needs multiple touches at the same time and its even worse in games than it is for scrolling.
[Android General] jhhest:
I have the same device... And the same touchscreen bug... Even with this bug is am very pleased with the price performance.

Is there a way in mtk engineering mode to change some settings and get a better respons on the touchscreen? (By using *#*#3646633#*#*) I was looking for some kind of manual for mtk engineering mode without any result.
[Android General] bigrammy:
New Updated CWM Recovery

Hi all, Except One who we all know

I have just Updated the CWM Recovery for the P6000.

All features now work.

Thanks. :cool:

Thread Here
[Android General] semo.pz:
Thanks good to know. Still tempted to go with this mobile given how good its read/write storage stats are (there's still a risk these stats deteriorate heavily with use depending on quality of hardware and firmware). I think I'll wait for the official fix for the touch issues or the Redmi 2 with 2GB RAM and go with whatever comes out first. The Pegasus X002 looks good* too but supports Chinese freqs only.

*Good in my book is ARMv8, removable battery, expandable memory, >1GB RAM and decent cam /w flash. Hard to find unless you like phablets.
[Android General] the1024:
how to fix touchscreen twitches

here's guide

method 1: (fast & easy)

0. get files here: View attachment 3147517,unpack to any folder (preferably root of current drive)

1. plug phone to pc, enable usb debugging, install adb drivers

2. run script tpd_fix.bat (only needs couple of secs to complete)

3. if touchscreen still unsmooth, reboot device. if reboot doesn't help, repeat from beginning

method 2: (slow & painful, but original one)

0. get files here: View attachment 3145883, unpack to any folder (preferably root of current drive). archive contains config + tool

1. plug phone to pc, enable usb debugging, install adb drivers

2. run gtpadbtool, answer yes to popup question. (this program is very unstable on windows 7/8. if it crashes, just repeat until success)

3. choose touchscreen model (p.1 on screenshot)

4. choose config file (p.2 on screenshot)

5. start by clicking button (p.3 on screenshot)

6. process will end with error (p.4 on screenshot). but that's ok.

7. if touchscreen still unsmooth, reboot device. if reboot doesn't help, repeat from beginning

View attachment 3145880

results:

View attachment 3145891View attachment 3145892
[Android General] greekfragma:
Many thanks man! I got my P6000 working like a charm after this fix. My screen problem was not too obvious until I did some tests, but now it works perfect! :good:
[Android General] vikmaffia:
Do you know what it modifies? I'd rather overwrite a config file manually, than using a software to do it... :)
[Android General] vikmaffia:
Thanks!

I did a quick compare, the 'config init values' are the same, but the 'config real value' differ: all are zeroed out after the change.

Also Chip PID, VID, Driver VID, Boot status and Test status are different.

I'll try to replace it by hand.
[Android General] xenonism:
/proc is not a place where you can permanently store data: it's a virtual file system where system information can be accessed or modified while the system is running. Also, Test Status only depends on whether the screen is on or off.

If the improvement is persistent across reboots, the new configuration must be written elsewhere, not in /proc.
[Android General] HypoTurtle:
Correct, can someone post there boot.img after applying the fix. It's either stored in there or somewhere in /system.

Running ls -la on /proc will point out where the config is; if it's a symlink, but doubt it is.

Attached translated Goodix ADB pdf.
[Android General] vikmaffia:
Right... not a symlink

/proc $ ls -la gt*

-rw-rw---- root root 0 2015-02-02 14:31 gt9xx_config
[Android General] the1024:
[MENTION=3356343]xenonism[/MENTION]

well, right now you are uncorrect. as /proc/gmnode20150109 used for updating firmware of tpd.

this chinese utility basically creates a file with binary config on sdcard and pushes it to that node.

well, we have this config now, so i made a script to simplify this process.

updated my post with other method

[MENTION=4056517]HypoTurtle[/MENTION]

i reflashed my device with spft, and tpd is still good. so i think it really flashes config to tpd chip, or something
[Android General] HypoTurtle:
[MENTION=3164405]the1024[/MENTION] Yea that makes sense, if it was a .bin then I'd say it definitely was.

So either on the tpd chip is the touchscreen firmware bin and the config for the touchscreen and /proc/gt9xx_config is a copy of this config; or the config calibrates the screen using the .bin and the /proc/gt9xx_config is the output from the calibration - with the zeroes in real value meaning the screen is calibrated...
[Android General] xenonism:
I am correct in stating that persistent changes cannot be made in /proc; it can be the source of data for a change, though. This said, I want to thank you for your contribution. :)
[Android General] HypoTurtle:
You're using the boot kernel (from boot.img) as far as I can tell, have you tried with the stock recovery kernel (attached - split); and can you get an early dmesg from recovery over adb?
[Android General] the1024:
[MENTION=3356343]xenonism[/MENTION]

yes, that's why i said that you are incorrect "right now". as it makes persistent changes, using file in /proc.

yes, not the proc itself, but still ;)

[MENTION=3924647]bigrammy[/MENTION]

yes, this config only changes x_threshold and y_threshold from 30 (1e) to 0
[Android General] bigrammy:
I tried the recovery kernel in early ports and it seemed to make no difference :( I don't think I tried it with the recovery that elephone released in the firmware package though. :confused: I will give it a go and try get dmesg but don't hold your breath on that :laugh:

[MENTION=3164405]the1024[/MENTION]

Thanks

Any thoughts on the VID Driver change or does this change with each boot :confused:
[Android General] the1024:
yes, i think so. this number looks different each boot, as i remember
[Android General] Nukomod:
Any luck? I'm interested in manually editing the necessary files as well.
[Android General] HypoTurtle:
This can't be done manually - the closest thing would be method 1 on #90 as what you need to do is to cat a file to the gmnode.

From [MENTION=3164405]the1024[/MENTION]'s zip: node=$(ls /proc | grep -m 1 'gmnode') identifies the correct node; and cat tpd_cmd.dat > /proc/$node sends the dat file (made from the cfg file) to the node.

If you want to manually do it then ls /proc | grep -m 1 'gmnode' will give you the number, and for example cat tpd_cmd.dat > /proc/25 will send the dat to node 25.
[Android General] vikmaffia:
I've tried method #1 a few times (by using the bat, running the commands in cmd, also in terminal emulator), but it didn't help. Method #2 here did the trick and the touch screen sensitivity is now really fine.
[Android General] Nukomod:
Someone mentioned a line you could edit regarding the OTG function. Did that ever work? Or will we never see OTG on this phone?
[Android General] s7yler:
It did not work. So far OTG only works with a powered OTG hub.
[Android General] xenonism:
There might be some merit to that line, but it's not a runtime setting, it's a compile setting.. You can't just change it on the phone, you need to rebuild the kernel.

Where do we stand on the compass issue? Is it possible that Mediatek designed a modular SoC and Elephone acquired the "no-compass" version of it?