Has anyone found a way to resolve / or found a workaround for the 'double-tap' bug in P8 lite ?
It is quite quickly reproduceable when you use any keyboard (Google Keyboard, Huawei Swype, Swype, Hackers Keyboard, Blackberry Keyboard, Go Keyboard, etc) to type a message and try to do it quickly. In this case - if you are writing a lot (business e-mails, text messages, etc) - the screen is starting to be a nightmare. I was able to reproduce the problem on my P8 Lite, my fiancees P8 Lite, P8 Lite's of few of my friends and various P8 Lite devices I was able to find in any of the stores in Krakow (PL) (Saturn, X-Kom, Media Expert)...
NOTE: If you are happy user that is NOT typing letters by tapping the letters on keyboard but using sliding/swiping - please don't reply to my post - as this is quite obvious that it IS working this way but some people would like to TYPE instead of SWIPE...
NOTE2: The problem is also NOT with the "protector screen" or gloves mode, etc (these settings, tools do not affect the bug in any way - it is all the time still present).
NOTE3: As far as I can see, the problem appears on all P8 Lite devices I had in hand regardless of the software version and place it came from... I hoped that since the upgrade to 6.0 problem would be resolved but it is not (guys from Huawei technical support claimed over the phone that this issue should have been resolved with B170 update, then they claimed that they're sorry it's not and it will be with 6.0 but... it seems it is still present and can be considered as widely existing device bug).
NOTE4: Since this concerns ALL keyboards my guess is that the problem is with the digitizer or the software which is controlling it (kernel modules?) or other screen-related issue.
----
EDIT: 10.04.2016 and 27.04.2016 and 12.05.2016
The firmware bug IS FIXED in B190 or later firmware of 5.X android line and B560 or later firmware of 6.X line
Sorry but the only workaround it's swipe or buy another smartphone.
I had this problem, some said it was because of the screen, some said the screen protector... Or the key vibration.
A month ago, i accidently deleted my android while flashing a program.... And i had no backup...
I re-flahed the firmware with all updates, and I dont have double tap problem any more
Never seen this trouble since I have the p8 lite (I have two p8 lite ).
I always use swiftkey beta and never use swipe. (All the keyboard is too small for my bigs fingers)
But I'm sure it's not related to the kernel.
Many guy's said this trouble was fixed on the B190.
Make a logcat is the only way to find what's happen and it's really easy.
If you don't know how to logcat you can find how to on xda and few apps available on the playstore works fine .
How can i reproduce the problem, i tried it on my phone but no problem.
What do you need to git the problem?
You can solve the problem flashing C432B190 (dual-sim) firmware. You will find here posts for any help on downloading and flashing.
@ItalianWolf
I hope there is another way I don't want to get back to my old (but solid) Samsung Ace2 (too little ram or to buy another one (the specs of P8 Lite are quite good and it is hard to find anything better for this price).
@konopla4
I reflashed firmware couple of times and ended up with the same problem. Currently I have european EMUI 4.0 (Android 6.0).
@dkonect
I don't think that logcat will actually help here but worth trying anyway to get some more details (if there would be any). Once I have more free time to play with the stuff will post the logcat as well (unless I will do downgrade and it would fix the problem.
@olrak
Just try to write something quickly (turning on or off the dictionary is not affecting this - so just type quickly any long message / string in messaging, FB messenger, notepad, anywhere. But you need to be kind of quick Typing single letter per second is not enough.
@sebasty
Thanks - you're the second person who points me to this firmware - I think I'll go with the downgrade to B190 first as this is the only firmware I haven't tried yet (unless the update to Marshmallow for EU would be released sooner that would fix the issue).
Okay, tested and confirmed. So far I do not have any issues with "double tap" on B190 (hoorraay!). Thanks again @sebasty
Also I can confirm that issue exists on all firmwares pre-B190 and Beta of EMUI 4.0 (B524 for EU)
Yes indeed, all other firmwares have this problem, even both beta tests of MM and the China version of MM.
I've tested all. Glad you solved it
sebasty said:
even both beta tests of MM and the China version of MM.
I've tested all.
Click to expand...
Click to collapse
I have version B535 and never got this bug, im using Swiftkey but type as always!
I am using the B170 firmware and I never had this problem.
As I wrote previously:
1) You need to be on firmware older than B190 (I have also tested on B170 and problem is 100% reproduceable)
2) Problem also appears on EU Marshmallow (I haven't tested on China one)
3) For sure it appears on EVERY SINGLE P8Lite on polish market unbranded by default and branded by play and t-mobile (I did not test the orange branded phones).
4) You need to type really fast in order to reproduce the problem (if you are quite slow when typing on keyboard or you use swype, etc - you will probably hardly ever see the issue).
If this works for you on different firmware - good for you - but then - please also post other details like if the phone is branded, rooted, additional software installed etc, as the above issue is confirmed by Huawei as the bug with all firmwares (pre B190) so far. ( @Letsego @toncek333)
If this does not work for you on different firmware - you can be more or less sure that after the update to B190 it should get resolved.
I'm pretty sure it's related to the screen sensitivity and "touch radius".
Basically, what happens: when you type quickly, it registers a few presses (finger on, and finger off)
From what I have tried:
Enabling "Glove Mode" makes it worse. (screen sensitivity)
Adding a thick glass screen protector makes it better. (still, screen sensitivity)
Changing ROMs, keyboards, etc. doesn't help. (screen sensitivity)
I think it would be possible to fix it by increasing the radius of the touch register (you would need a more firm touch to click anything on the screen). This should be doable with some software coding.
empy16 said:
I'm pretty sure it's related to the screen sensitivity and "touch radius".
Basically, what happens: when you type quickly, it registers a few presses (finger on, and finger off)
From what I have tried:
Enabling "Glove Mode" makes it worse. (screen sensitivity)
Adding a thick glass screen protector makes it better. (still, screen sensitivity)
Changing ROMs, keyboards, etc. doesn't help. (screen sensitivity)
I think it would be possible to fix it by increasing the radius of the touch register (you would need a more firm touch to click anything on the screen). This should be doable with some software coding.
Click to expand...
Click to collapse
As I wrote before. Bug is fixed in B190 firmware.
Huawei also confirmed that the bug exists in all previous firmware. It also exists in 6.0 BETA.
wolfensg said:
As I wrote before. Bug is fixed in B190 firmware.
Huawei also confirmed that the bug exists in all previous firmware. It also exists in 6.0 BETA.
Click to expand...
Click to collapse
It's not a software bug. It's a hardware bug that can be fixed with software.
Maybe they've done just that (increased the touch diameter) to fix it.
What we need is to have a good look at the touch/screen/etc. code and find what's been changed.
Unfortunately I'm just not competent enough to do that.
empy16 said:
It's not a software bug. It's a hardware bug that can be fixed with software.
Maybe they've done just that (increased the touch diameter) to fix it.
What we need is to have a good look at the touch/screen/etc. code and find what's been changed.
Unfortunately I'm just not competent enough to do that.
Click to expand...
Click to collapse
No offence implied but how you can be so sure that this is a hardware issue since you are "not competent enough" to review the code change and know what was the real problem about? (You also are not able to get the source code for review as it is not available for public).
The fact is that it has been fixed with B190. Period.
I hope Huawei will apply the fix to upcoming EMUI 4.0 firmware as well.
wolfensg said:
No offence implied but how you can be so sure that this is a hardware issue since you are "not competent enough" to review the code change and know what was the real problem about? (You also are not able to get the source code for review as it is not available for public).
The fact is that it has been fixed with B190. Period.
I hope Huawei will apply the fix to upcoming EMUI 4.0 firmware as well.
Click to expand...
Click to collapse
I might not be competent, but I have a brain. You can reproduce the bug in the recovery.
empy16 said:
I might not be competent, but I have a brain. You can reproduce the bug in the recovery.
Click to expand...
Click to collapse
...ok and what is your conclusion? What recovery you are reffering to? Which firmware are you reffering to?
when the OTA arrives, can I go back to my stock firmware? and I'd like to keep my warranty too. and also, my phone is not a dual sim variant.
tayfuntb1393 said:
when the OTA arrives, can I go back to my stock firmware? and I'd like to keep my warranty too. and also, my phone is not a dual sim variant.
Click to expand...
Click to collapse
The answer to "when the OTA arrives" is more country specific i.e. I did not see B190 OTA in Poland, but I used local update.
Related
For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.
yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.
can anyone provide a flashable patch to try? Thanks
This problem is starting to annoy me really badly D:
I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.
This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5
Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133
Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.
I have a Nexus 4 and I am on Android 4.4. I recently encountered the issue of my soft touch buttons (back, home, recent apps) being unresponsive, the rest of the screen works but my buttons don't respond to touch. I can still slide ip for Google now though.
I tried restarting my device and even upgraded to a newer build of 4.4, no luck.
R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app
parveen75 said:
R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.
soulcedric said:
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.
Click to expand...
Click to collapse
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?
lopezk38 said:
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?
Click to expand...
Click to collapse
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc
soulcedric said:
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc
Click to expand...
Click to collapse
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)
popinterfaces said:
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)
Click to expand...
Click to collapse
I will try that, but it seems odd that other people would have the problem fixed after a screen replacement, which would identify it as a hardware issue.
maybe the screen replacement method (used by repair services/centers) came with a reset/flash of the rom.
What is even more strange is that some people seem to encounter the same bug again even after a screen replacement.
Please, keep us informed if the flash method solved the bug.
I'm currently still on 4.4.2 (for development needs) and i'm worried i could face the same problem !
I've confirmed that it's a hardware issue and has affected a lot of users who updated. I cannot touch the area of the screen in full screen apps.
Google should be warned and issue a statement about this, this is very bad news for us users.
The fact that it works after a screen replacement with no software modifications is proof enough. Time to vow to never buy a Google product again...
Temporary solution
any one has this problem should download any soft key app
BUTTON SAVIOR IS A good APP
it solved my problem
i advice you to try it
you can try any other app it's not advertisement you can use any soft key app i wrote this name just because i have tried it
good luck every one
Hi
Now that we have our own corner (still, our own forum would be better), but, until then ...
Any hardware issues?
Post here!
Please mention:
Version: Advanced / Basic
EU/USA or CH Version
Purchase date (aprox.)
Where you got it from (official stores/ other _ )
Rom / OS Version
In order to try to reach a conclusion ...
cheers :laugh:
Let me start ...
Advanced
EU Version
~April 2015
Official Jiayu Deutschland (Germany)
LP 5.1
Issues: None so far
Regards
- advanced
- CH version
- March 2015
- Jiayu-store.com
- KK 4.4.4 OTA 507
Phone works aok for me.
Note: can't use charger with less than one amp draw or touch screen flakes out.
Had to use name brand SD 64gig card from Samsung as it would not recognize generic SD card of equal size.
Basic
CH Version
~Mid of February
SpeMall
KK 4.4 20150430
Issues:
-Gyroscope is too sensitive and inaccurate.
-Magnetometer (Compass) is really bad, keeps spinning even if the phone is still. And doesn't show real north (actually misses too much).
-Slight pressure points on screen (Like when you press a bit harder, looks like when you press LCD monitor and "bleeds" a little). Probably isn't laminated well. It doesn't bother me so I just mention it.
And I hope someone will help me solve problem with gyro and compass!
Advanced
EU Version
~June 2015
Antelife (China)
Originally installed with 20150314 KK, since upgraded to superdragonPT's beta 3 and then unoffical 1Jul15 LP 5.1 - latter both working well
Issues:
Lower microphone only works in Sound Recorder/Video Camera, fails to work on calls or OK Google - suspect software glitch somewhere, but have ordered replacement USB/lower mic board, and will report back when fitted
Occasionally under KK (stock), when hitting the slider to unlock the phone it would 'stick' and the only way to resolve was to take battery out
Deezer does not work well under KK (stock) - have to keep screen alive to allow it to play one track then the next on an album, otherwise the second track will not load properly - suspect Deezer issue not optimised to work with octacore models
Basic
CH Version
February 2015
Aliexpress
(1/7 LP ROM)
Issues: Low Mic Volume Call. But Google Now works.
•Version: Advanced
•CH Version
•Purchase date June 2013
•Where you got it from : Jiayu-store
•Rom / OS Version : KK 4.4.4 S3SW 20150314-141844
Works perfectly, no issues
(when I first received the device, it wouldn't detect my simcard and didn't have an imei stored, after I contacted support they advised that all I had to do was perform a factory reset and the phone would allocate its IMEI... I did so and now the phone is working perfectly)
sirdickens said:
Basic
CH Version
~Mid of February
SpeMall
KK 4.4 20150430
Issues:
-Gyroscope is too sensitive and inaccurate.
-Magnetometer (Compass) is really bad, keeps spinning even if the phone is still. And doesn't show real north (actually misses too much).
-Slight pressure points on screen (Like when you press a bit harder, looks like when you press LCD monitor and "bleeds" a little). Probably isn't laminated well. It doesn't bother me so I just mention it.
And I hope someone will help me solve problem with gyro and compass!
Click to expand...
Click to collapse
one thing:
The GPS status program allows to calibrate compass (rotate all 3 axes). Does it help?
Nofan Tasi said:
one thing:
The GPS status program allows to calibrate compass (rotate all 3 axes). Does it help?
Click to expand...
Click to collapse
No my friend, I've tried everything and dozen of compass apps that "calibrate" this way and even some apps that are just for calibration.
I've seen however in engineering mode when going to msensor (magnetometer) it says with data is wrong so it might be broken sensor, but it is kinda unimaginable. I've seen many people report these two (gyro, compass) not to work correctly. Also, my friend got S3 and he has the same problem.
sirdickens said:
No my friend, I've tried everything and dozen of compass apps that "calibrate" this way and even some apps that are just for calibration.
I've seen however in engineering mode when going to msensor (magnetometer) it says with data is wrong so it might be broken sensor, but it is kinda unimaginable. I've seen many people report these two (gyro, compass) not to work correctly. Also, my friend got S3 and he has the same problem.
Click to expand...
Click to collapse
Accuracy 0.0 looks odd. Mine is 0.2 but also mentiones 'NOT GOOD'. It works though.
When I leave compass on table it keeps drifting, sometimes it can make few circles even though phone is still.
What ROM do you have?
And what are your experience with gyro? Can you try google camera and see if photo sphere works?
Cheers!
sirdickens said:
When I leave compass on table it keeps drifting, sometimes it can make few circles even though phone is still.
What ROM do you have?
And what are your experience with gyro? Can you try google camera and see if photo sphere works?
Cheers!
Click to expand...
Click to collapse
Very strange indeed. I fired up my engineering mode to see what I got, and it started the same, 0.0, NOT GOOD. but after about 90seconds, the green bar spiked and I got good data. See the attachment.
Sent from my JY-S3 using XDA Premium 4 mobile app
same here alex ... I had not noticed switch from 'no good' to 'good'
basic
Eu. S3w 20150325
Pandawill
Does anyone experience kind of this.......
Quote:
Originally Posted by ylaandroid
hi
I'm thinking my phone is overheating abnormally since most user says no heating issue.
Area around the rear camera getting really hot while i play 3d online games. Sensors showing:
Web surfing 50-55°C
3d games&benchmarks 65-70°C
I tried bunch of roms and tweaks, no change.
Is this values normal compare to yours?
Mine heats up also when playing online 3d games with heavy graphics, no overheating wile browsing (i'm talking about 3g and wi-fi though - don't use 4g).Have you tried to lower the CPU frequency to 1,5 for example. Some guys here thing it heats up because of the turbo function 2 cores are getting boosted to about 2.0 mhz. When needed. Don't know how to switch that off... If someone has solution is welcome to share.
Is there a way to know jiayu s3 manufacturing date in software?, maybe via engineering mode or some special code? (like, for example, "Phone INFO ★Samsung★" on Google Play Store does for Samsung)? Knowing date might perhaps help correlate hardware issues.
Good news - got the replacement lower USB/mic board today - swapped out easy enough, and now finally have a working lower microphone. Very pleased, fix cost about £5 from Vifocal (http://vifocal.com/usb-connector-with-mic-deputy-board-repalcement-for-jiayu-s3-smartphone.html), took 24 days to get here from China.
Now I can finally use the S3 as a phone, not just a tablet.
It's good to see that spare parts are available for the S3 (particularly with the future of Jiayu in question) and self repairs are achievable. I would choose a self fix if the parts are cheap enough rather than waiting weeks for warranty service anyway.
I have two devices and the LCD calibrations are noticeably different. On one the whites have a very slight pinkish hue(like red needs to be turned down a touch). It also has a very small amount of backlight bleed in the bottom corner which is more noticeable due to the backlight being white and the screen being slightly pink. Simple RGB calibration tools could correct this (like the franco kernel on the nexus devices) but so far I cannot find a tool to do this at kernel level so filter overlay apps are the only option and miravision doesn't help.
Has anyone else noticed backlight bleed or slightly pink screen? Admittedly it would be difficult to detect if you don't have a second device to compare it to.
Sent from my JY-S3 using XDA Free mobile app
Version: Advanced
EU (PT)
June/2015
Everbuying
KK 4.4.4 S3SW 20150314
Issues:
Well, at first, i was pretty excited when i received. I had to cut my old sim cards to micro sim.
And when i tried to connect them, the phone was not recognize them. My though: "Maybe it's because they are old sim cards, i asked to my operator a new ones".
While i was waiting, i've tried a micro sim from a friend, and it didn't recognize as well.
My surprise, when searching on the net, for this kind of problem, i dialed *#06# to see the IMEI, and both are "Invalid"..
Since then, i've tried many ways to restore the IMEI.
"#4634# - After put the IMEI, shows a message that IMEI was successful changed, but when i check, they are the INVALIDS again.
I've tried the IMEI_FIXING MTK. (with sn_gen.exe ) replacing the old file for the new one that is created. And nothing happens too. :crying:
My last thought, is to update my phone to that S3S Lollipop v5.1 – Release Candidate, and see if it fix the problem.
But, for now, it seems that ROM it has a some bugs..
Can anyone help me with this?
Many Thanks
CAATS said:
Version: Advanced
EU (PT)
June/2015
Everbuying
KK 4.4.4 S3SW 20150314
Issues:
Well, at first, i was pretty excited when i received. I had to cut my old sim cards to micro sim.
And when i tried to connect them, the phone was not recognize them. My though: "Maybe it's because they are old sim cards, i asked to my operator a new ones".
While i was waiting, i've tried a micro sim from a friend, and it didn't recognize as well.
My surprise, when searching on the net, for this kind of problem, i dialed *#06# to see the IMEI, and both are "Invalid"..
Since then, i've tried many ways to restore the IMEI.
"#4634# - After put the IMEI, shows a message that IMEI was successful changed, but when i check, they are the INVALIDS again.
I've tried the IMEI_FIXING MTK. (with sn_gen.exe ) replacing the old file for the new one that is created. And nothing happens too. :crying:
My last thought, is to update my phone to that S3S Lollipop v5.1 – Release Candidate, and see if it fix the problem.
But, for now, it seems that ROM it has a some bugs..
Can anyone help me with this?
Many Thanks
Click to expand...
Click to collapse
When I received mine it didn't recognize the sim cards at all but a factory reset sorted it, have you tried that?
Sent from my JY-S3 using XDA Free mobile app
guido21 said:
When I received mine it didn't recognize the sim cards at all but a factory reset sorted it, have you tried that?
Sent from my JY-S3 using XDA Free mobile app
Click to expand...
Click to collapse
you just have made my day!!! It worked perfectly!! :good:
Untill now, i had a 5.5" Jiayu Tablet :silly:
Now i have a smartphone!!
Thanks a lot
Hello good people of XDA,
My father's P9 Lite (VNS-L21) just developed an issue with the camera and I have no idea what the cause is. As soon as you try and use the camera the app crashes and it keeps restarting. The issue is also happening with 3rd party apps which use the cam (such as facebook app). I have factory restored the phone and still no luck... Video can be found here: [youtube_url]/watch?v=pxQIOnpawNE
Until a month ago the phone was still under warranty and I tried going to Huawei support for help. But customer care is utterly useless and a total waste of time! They've been sending me from one place to another ever since, and recently stopped replying to any of my emails, to the point that I have now given up on them and their bull..... So I am now trying to salvage what I can myself.
Apparently the phone is a Chinese model and in fact the box says 'G9' although the phone's info menu states that it is a P9 Lite. The problem seems to be just with the cam but my father said that he never dropped it and that the problem emerged just after a firmware update. So I was wondering if anyone here could point me to the right direction of how I can re-flash (if that is a correct term) the phone. Any help would be highly appreciated!!
Thanks in advance,
Chris
Exactly the same problem with the phone of my girlfriend (it's a G9 as well, chinese version of the P9). The problem appeared after the EMUI 5 upgrade. I have no idea what to do appart from downgrading to EMUI 4 I guess...
Thordelan said:
Exactly the same problem with the phone of my girlfriend (it's a G9 as well, chinese version of the P9). The problem appeared after the EMUI 5 upgrade. I have no idea what to do appart from downgrading to EMUI 4 I guess...
Click to expand...
Click to collapse
Yes its a software issue. I've been browsing around the forums for the last two days trying to learn how to revert back to old firmware and it was actually easier than I thought.
Follow this thread and you should be fine. The cam is working again on EMUI 4
outsid23r said:
Yes its a software issue. I've been browsing around the forums for the last two days trying to learn how to revert back to old firmware and it was actually easier than I thought.
Follow this thread and you should be fine. The cam is working again on EMUI 4
Click to expand...
Click to collapse
Thanks man, I'm not going to waste more time and probably follow this guide then but before I do, just a quick question : I remember reading somewhere on another forums which I don't remember the name, some guys complaining about the video (not the whole camera) not working on the P9 lite, and it seems it was a problem with google options (don't ask me why, I have no idea...).
I'm not saying those 2 problems are related but could be, have you found that thread as well by any chance and maybe try the solution given by changing some google options ?
Thordelan said:
Thanks man, I'm not going to waste more time and probably follow this guide then but before I do, just a quick question : I remember reading somewhere on another forums which I don't remember the name, some guys complaining about the video (not the whole camera) not working on the P9 lite, and it seems it was a problem with google options (don't ask me why, I have no idea...).
I'm not saying those 2 problems are related but could be, have you found that thread as well by any chance and maybe try the solution given by changing some google options ?
Click to expand...
Click to collapse
No prob! No never saw that thread to be honest. But I did a factory reset and completely wiped the phone and the problem was still there. So I doubt it how the default settings would be set in such a way that the camera doesn't work. Would be worth giving it a try if you manage to find it though.
The instructions in the link I posted take 30min tops, so you won't waste too much time either
outsid23r said:
No prob! No never saw that thread to be honest. But I did a factory reset and completely wiped the phone and the problem was still there. So I doubt it how the default settings would be set in such a way that the camera doesn't work. Would be worth giving it a try if you manage to find it though.
The instructions in the link I posted take 30min tops, so you won't waste too much time either
Click to expand...
Click to collapse
Actually come to think of it, my girlfriend has a P9 (not the lite one) and she had issues with videos only, and yes there was some thread which suggested to turn off the "OK Google" option "From any screen". In that case the setting worked but as you rightly said. But it was only the video which was problematic and it worked in 3rd party apps such as FB - just the original camera app wouldn't record videos. So I think this problem is a bit different but it wouldn't hurt if you tried before downgrading. I had completely forgotten about that sorry
Thanks by the way, I downgraded and it works again as expected now.
Still I hope there would be another solution that would allow us to upgrade to EMUI 5, have you found another solution since by chance ?
Hello,
this question might seem somewhat stupid. I've run into serious bugs on my 3 year old Note 4, they come and go, sometimes they appear many times a week and sometimes not for several months in a row. I have insurance, which ends mid-July. I wanted to send it in over a week ago, but after I've read the terms, I thought that it would be hard to get something from them, since the bug doesn't appear every day. Since I moved the SIM card to another phone over a week ago, the Note worked perfectly. Before it would from time to time refuse to call, tell me that some system app had crashed and reboot. After reboot I'm unable to call again (no signal) and have to turn it off and on again, for it to work. Couple of times it froze completely (had to remove the battery) and some months ago I had WiFi problems (connected, but no data transmission) a couple of times.
I think that it's a hardware problem, but I doubt they would wait for weeks for a bug to appear and I want to rule out software problems first. I want to try "the best possible" ROM (I know, it's in the eye of the beholder). I took a look on the threads about LineageOS 15.1/14.1, 14.1 is called stable, but there are pretty much the same bugs mentioned. I need:
- Perfectly working cameras, phone calls (is it important that I have two numbers (normal and "landline") on the same card?), mobile Internet, WiFi, SD-card support, preferably docking station support (the 5in1-one, OTG, HDMI, SD and whatnot. I would like the S-Pen to work, if not to its full potential, then at least "somewhat". PlayStore/GApps (?) are important. I don't need Fingerprint sensor, NFC, Bluetooth. Though it would be nice if all the builtin sensors would work, since I might get to install FL Studio Mobile/IL Remote on it eventually or play some games (very unlikely).
- Ability to record calls automatically would be nice (I know, GDPR, but whatever)
- The most important thing is that it's as stable, as possible
It would be awesome if I could test the new FirmWare in DualBoot. I have a 32GB microSD card.
I'm not an idiot, but lately I'm seriously lacking free time and concentration skills (I don't feel my best mentally). I don't feel able to go through all the Firmware topics (LineageOS 14+15 alone are 1000 pages long), I would ask very kindly if someone could suggest a suiting Firmware and give me a link to a hopefully straightforward flashing how-to with all the latest download links. I would forever be in your debt. Especially if you could also give me a link on "how to get into that" (migration/getting started). I want to be done on Tuesday, if possible, so I'd have 2+ weeks to test everything as thoroughly, as possible.
I don't know anything about customizing one's phones, except for what's possible out-of-the box and with 3rd-party-apps. But I'm a fast learner. I understand English, German and Russian.
Regards,
k_u_
Hi
[Joke] The perfect ROM is the one YOU build :laugh: [/Joke]
As you speak English, German and Russian (too bad I'm French :laugh: ) I'll assume you live in Europe and you own a N910F.
To get all sensors working (heart rate included) you need stock: one just got out on Sam Mobile with updated BL and modem (DRD1) and April 2018 security update.
You also may consider Alexander's last built.
LOS 15.1 is pretty good as daily driver but I don't think it meets your needs (especially about sensors...), I've been using it for few months.
Can't help about any other custom ROM but in any cases you won't have all sensors on any of them.
You can use SPen Command for the stylus.
I hope this help...
Sent from my Zuk Z2 Pro using XDA Labs
Edit: you own a 910F! The title told me :silly:
IMHO you'd better keep on full stock (or close to) here is a link for Alexander's https://forum.xda-developers.com/no...se-multi-csc-safe-bloat-t3033881/post58925494
Dual boot is a hard work on N910F (never been able to get it work flawlessly :crying: )
barlu said:
Hi
To get all sensors working (heart rate included) you need stock: one just got out on Sam Mobile with updated BL and modem (DRD1) and April 2018 security update.
You also may consider Alexander's last built.
LOS 15.1 is pretty good as daily driver but I don't think it meets your needs (especially about sensors...), I've been using it for few months.
[...]
IMHO you'd better keep on full stock (or close to) here is a link for Alexander's https://forum.xda-developers.com/no...se-multi-csc-safe-bloat-t3033881/post58925494
Dual boot is a hard work on N910F (never been able to get it work flawlessly :crying: )
Click to expand...
Click to collapse
With "all sensors" I meant accelerometer, gyroscope and whatever else is used in games and music software. I don't need heart rate/o2/UV sensors, etc.
I see that there was a German update in February, which I didn't receive (maybe it's for Vodafone-BRANDED devices? I have DQ(I/J/A)1 installed, latest update came on January 1st, I believe) and the latest one is indeed the DRD1 for UK. Does EE stand for the British mobile network operator? Will the firmware work the same in Germany or what would differ? WIll OTA continue to work?
I'm already downloading, the best (first) thing to try would be the original firmware, of course. I just thought, Samsung gave up on that model.
One question:
Add each file to it's respective field in Odin v3.13.1. Use CSC_OXM if you want to do a clean flash and HOME_CSC OXM if you want to keep your apps and data.
Click to expand...
Click to collapse
Is "keeping apps and data" possible/"advisable" in my case? I want to keep everything, but if another firmware "branch" could install with new bugs, maybe it should be installed cleanly.
---
As for Alexander's stuff link - I took a quick look and it's all Chinese to me :laugh: If I'll keep having problems with UK firmware, maybe, I'll take another look on that or LOS 15.1/14.1.
Did you have any problems with LOS? Camera problems are mentioned in bugs (maybe would work fine with a different app?), GPS problems (didn't understand that exactly, "doesn't fix satellites"???). I'd like to have up-to-date Android without Samsung's bloatware, but mostly I'd like a STABLE system.
P.S. Oh, yeah, one more question - what do you mean with "updated BL"?
P.P.S. Will flashing the UK firmware "void my warranty" (I don't have warranty anymore, but will the insurance company see, that I flashed a different firmware? KNOX counter or whatnot. (I called my "meta-insurer" (a proxy company) today and asked if I'm allowed to flash a custom ROM, he said, he's not 100% sure, but thinks, I'm not. I would have to ask the actual insurance company tomorrow or re-read the policy, which I might do later.))?
Hi
My feelings are you're not used to mess with your phone , so you better (for now) stick with official firmware. (No Knox trouble or whatever its Samsung's firmware)
IMHO the best for you is to install the last full stock ( did you already download it?) and follow this tutorial step by step https://samsung-firmware.org/download/GALAXY__Note4__/o2ll/EVR/N910FXXU1DRD1/N910FEVR1DRD1/
You should keep your data and still be able to use your phone in Germany.
If you still have issues you should backup every things you can't afford to loose. Because the repair techs will obviously delete all your data (even if they don't fix anything )
In any cases, with you want to go for a custom ROM, I'll give you an help for it.
Sent from my Zuk Z2 Pro using XDA Labs