Information of 1.29 OTA - One (M7) Q&A, Help & Troubleshooting

Here's some information about 1.29.709.12 upgrade (Taiwan version), and some responses I read from other forum.
And... sorry guys, I really don't know when will your updates come. and i don't have the phone yet . I envy you!
.
1.29.709.12(214.04MB)
1. virtual key sensitivity adjusted
Lots confirmed the home/back key issue fixed, looks solid.
2. slow motion video quality recording improved under low lit
Didn't see anyone post about it
3. better Beats Audio experience
Some said the left / right sound are better balanced.
4. reduce background noise when using headphone
a few guys said noise is "significantly" reduced.
5. better bluetooth device matching
a few guys confirmed bluetooth device matched faster.

firmware from this OTA is availablehere: http://forum.xda-developers.com/showthread.php?t=2182823

That's the russian firmware for that link there will probably be a lot more posted there in the coming days.
It's rolling out to Germany and France as we speak.

I want the fix for the home/back buttons (allegedly in this OTA) *bad*. I'm Sprint/US.

m03sizlak said:
I want the fix for the home/back buttons (allegedly in this OTA) *bad*. I'm Sprint/US.
Click to expand...
Click to collapse
If you are on 1.29 that fix might be in there already if you mean the sensitivity issue with the buttons and having to press them multiple times to get them to work.

daleski75 said:
If you are on 1.29 that fix might be in there already if you mean the sensitivity issue with the buttons and having to press them multiple times to get them to work.
Click to expand...
Click to collapse
Yes, that is exactly the problem I'm referring to. I'm on US/Sprint 1.29.651.7, and the problem definitely still exists for me and many other users of this firmware version, so I really hope the button fix from Taiwan version 1.29.709.12 does not already exist in US version 1.29.651.7, because if so...IT DOESN'T WORK.

anyway of getting this update any sooner?
Im in the uk with a 'sim free' handset so would have thought the update would come first as its not a carrier locked handset

hpsauce37 said:
anyway of getting this update any sooner?
Im in the uk with a 'sim free' handset so would have thought the update would come first as its not a carrier locked handset
Click to expand...
Click to collapse
You and me both.

Patience.. .. .. I CANT WAIT FOR THIS UPDATE!! LOL

Related

Low mic volume on speakerphone

When i activate speakerphone during a Call suddenly the mic volume drops dramatically, other persons could barely hear me.
Do you guys suffer similar conditions ?... I am not sure to return it or not, as the mic work perfectly if speaker is not activated.
Created this thread just to find out how many Note owners are having similar issues..If this is a software issue everyone of us on latest firmware should be having this issue. Otherwise I might need to send it to repair center..
_K****ij said:
When i activate speakerphone during a Call suddenly the mic volume drops dramatically, other persons could barely hear me.
Do you guys suffer similar conditions ?... I am not sure to return it or not, as the mic work perfectly if speaker is not activated.
Created this thread just to find out how many Note owners are having similar issues..If this is a software issue everyone of us on latest firmware should be having this issue. Otherwise I might need to send it to repair center..
Click to expand...
Click to collapse
yes I do. it wasn't like that when I bought the phone so I suspect the ICS update has broken it.
bashville said:
yes I do. it wasn't like that when I bought the phone so I suspect the ICS update has broken it.
Click to expand...
Click to collapse
Are you on latest firmware? I didn't had this since I updated to latest one. Running stock 4.0.4 ICS right now.
_K****ij said:
Are you on latest firmware? I didn't had this since I updated to latest one. Running stock 4.0.4 ICS right now.
Click to expand...
Click to collapse
I've updated to 4.0.4 (stock over the air update) and I still have the issue. I read somewhere that the galaxy note has 2 mics one at the bottom which is used when in normal phone mode and one at the top which is used when in speakerphone mode. I think the one at the top is faulty (given there are not many search hits for it on google I'd guess the problem is hardware and not firmware related).

Anyone facing ghost touch on rooted 4.4?

I have unlocked and rooted with the latest 4.4 but have been facing lot of ghost touch, over heating and freeze. Is anyone else facing the same issues with their z1?
ravi_buz said:
I have unlocked and rooted with the latest 4.4 but have been facing lot of ghost touch, over heating and freeze. Is anyone else facing the same issues with their z1?
Click to expand...
Click to collapse
I haven't as yet but I did notice that the touch screen issue I had where my finger / thumb would lose contact briefly with the screen.
Hasn't happened a lot and holding the metal frame fixes it.
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen.
Could be that your touchscreen is set too high for your device in particular, either that or it's a problem with the touchscreen or even some dirt.
Give it a good old clean and a few reboots.
All the above is speculation of course, just having a stab at it for you m8.
Not sure where that thread is about the touchscreen but it's definitely in the Z1 forum.
dladz said:
I haven't as yet but I did notice that the touch screen issue I had where my finger / thumb would lose contact briefly with the screen.
Hasn't happened a lot and holding the metal frame fixes it.
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen.
Could be that your touchscreen is set too high for your device in particular, either that or it's a problem with the touchscreen or even some dirt.
Give it a good old clean and a few reboots.
All the above is speculation of course, just having a stab at it for you m8.
Not sure where that thread is about the touchscreen but it's definitely in the Z1 forum.
Click to expand...
Click to collapse
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
ravi_buz said:
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
Click to expand...
Click to collapse
So on the base that you were on you didn't have any issues, Rooting itself will not cause this issue.
What base were you on prior to rooting and what are you on now?
dladz said:
What youre describing could be a knock on effect of the new firmware having a higher sensitivity to the previous firmwares, I know Sony were aware of the touchscreen issue that people were facing and there was a fix where you could alter the sensitivity of the touch screen..
Click to expand...
Click to collapse
How can I alter the sensitivity of the Touch Screen?
EDIT: sorry, I forgot you don't know where it is..
---------- Post added at 02:32 PM ---------- Previous post was at 02:23 PM ----------
ravi_buz said:
Cleaned it and rebooted. Din have this problem before rooting..but as soon as i rooted i started seeing these things happpen
Click to expand...
Click to collapse
Same here, after rooting mine, it starts again the touch screen to respond strange, but not a big problem. Did not had this on .136.
dladz said:
So on the base that you were on you didn't have any issues, Rooting itself will not cause this issue.
What base were you on prior to rooting and what are you on now?
Click to expand...
Click to collapse
Actually Rooting can cause the issue because the Pre-Rooted version can be different from the original one installed on our phone.
After I received the phone from Repair they updated the Software and then I updated to .136 officially and the issue disappear, never had even a bit of it. Then I rooted, but to do so I used a different Base, NUT use the Frence region I think, and after that on mine .136 the problem with Touch Screen appear again, not badly, all is fine but sometime it skips something.
So I think it's really related to the Software and the all the phone have a specific Base.
eclyptos said:
Actually Rooting can cause the issue because the Pre-Rooted version can be different from the original one installed on our phone.
After I received the phone from Repair they updated the Software and then I updated to .136 officially and the issue disappear, never had even a bit of it. Then I rooted, but to do so I used a different Base, NUT use the Frence region I think, and after that on mine .136 the problem with Touch Screen appear again, not badly, all is fine but sometime it skips something.
So I think it's really related to the Software and the all the phone have a specific Base.
Click to expand...
Click to collapse
Then it would be down to the rom and not the rooting process, rooting alone won't affect the touchscreen m8.
The Rom could though.
dladz said:
Then it would be down to the rom and not the rooting process, rooting alone won't affect the touchscreen m8.
The Rom could though.
Click to expand...
Click to collapse
Of Course.
i have not experienced ghost touch but i did experience the screen failing to register two finger touch sometimes.
what i mean by that is when u quickly touch another part of the screen after its been touched it would register it as a swipe.
very annoying when typing keyboard or even pressing key pin on lockscreen.
i reproduced this in touch test and
once it registers as a faulty swipe while holding down the touch
it keeps registering swipe wherever the other finger presses untill i stop touching.
also when i installed a fresh rom it seems that the touch is very sensitive.
i tried this out http://forum.xda-developers.com/showthread.php?t=2691849
its not a fix but it helps out.
I think i have drilled down to the cause for this issue.
1. I started mounting my phone on my motorbike and ride. Due to excessive vibration the screen might have started acting out.
2. I also read that x alert causes this.
I have locked bootloder and installed stock ROM. Lets see whats happens
ravi_buz said:
I think i have drilled down to the cause for this issue.
1. I started mounting my phone on my motorbike and ride. Due to excessive vibration the screen might have started acting out.
Click to expand...
Click to collapse
I don't think this cause the issue.
ravi_buz said:
2. I also read that x alert causes this.
Click to expand...
Click to collapse
What is that or where it is?
Been trying to find that adjustment you can make for the touchscreen but can't find it. Its an adjustment of a file within android which deals with how sensitive the touch screen is. Buggered if I can find it though. I commented on it too. Eluded me.
Sent from my C6903 using XDA Premium 4 mobile app
dladz said:
Been trying to find that adjustment you can make for the touchscreen but can't find it. Its an adjustment of a file within android which deals with how sensitive the touch screen is. Buggered if I can find it though. I commented on it too. Eluded me.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe that Calibration.ini file magically can help?
BTW, if you find that thread let me know because I am interested too in changing the sensitivity, I will like to play with that.
eclyptos said:
Maybe that Calibration.ini file magically can help?
BTW, if you find that thread let me know because I am interested too in changing the sensitivity, I will like to play with that.
Click to expand...
Click to collapse
Will do m8.
dladz said:
Will do m8.
Click to expand...
Click to collapse
I would definitely be interested in this as well so could you please inform me as soon as you find something? Thanks
I am unable to pin point the problem.
1. Its not bcoz of root/boot loader
2. Not bcoz of mouting it on my bike. Infact when i mount it, it functions normally.
3. Ghost touch worsens when i play clash of clans but it is there other times too.
So its either bcoz of over heating (games make the phone heat a lot) or water entered it or i am not sure.
http://forum.xda-developers.com/showpost.php?p=51742613&postcount=8
He found my thread
I always surf the forums and check out what is happening, and this thread did catch my eye
I don't like to think that the touch screen issue is hardware related. I really hope it isn't.
Don't put your heart on this 'fix', as I have lost faith in it myself...
I'm going to post there now as well, to tell people what I have said here.

Speaker crackle/distortion is it hardware och software related?

Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Jaxione said:
Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Click to expand...
Click to collapse
No problem for me here, not even on the highest volume level. If some users have this issue its probably a hardware faillure rather then software.
Jaxione said:
Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Click to expand...
Click to collapse
Some devices are facing this issue. If it's only happening on highest volume then it's a software issue or else it's a hardware issue
SAW_JOK3R said:
Some devices are facing this issue. If it's only happening on highest volume then it's a software issue or else it's a hardware issue
Click to expand...
Click to collapse
If it is a software issue, how come only some devices have it and not all?
Br J
Jaxione said:
If it is a software issue, how come only some devices have it and not all?
Br J
Click to expand...
Click to collapse
I've no proper explanation to give But same happening with force shutdown / random force reboot issue. It's affecting Many users but not All
SAW_JOK3R said:
I've no proper explanation to give But same happening with force shutdown / random force reboot issue. It's affecting Many users but not All
Click to expand...
Click to collapse
This sucks How could they solve software issues that is only affecting some phones? If I send mine back It will take 2-3 weeks for it to come back. And I think the company that I bought it from will just scratch their heads and find no problem with the phone. I from sweden and Motorola isnt represented here so I have to go through the company I bought it from sucks. Will never buy from them again.
Br J
Jaxione said:
This sucks How could they solve software issues that is only affecting some phones? If I send mine back It will take 2-3 weeks for it to come back. And I think the company that I bought it from will just scratch their heads and find no problem with the phone. I from sweden and Motorola isnt represented here so I have to go through the company I bought it from sucks. Will never buy from them again.
Br J
Click to expand...
Click to collapse
It's not their fault. It's Google's fault. Go to this Google Forum Topic and go to first page. You can see it's marked as complete by a google employee. Fix will come with the new update
SAW_JOK3R said:
It's not their fault. It's Google's fault. Go to this Google Forum Topic and go to first page. You can see it's marked as complete by a google employee. Fix will come with the new update
Click to expand...
Click to collapse
Read throught the thread. The only thing google are saying is that the cant reproduce the problem. Can read anywhere that they will fix it.
Mvh J
Jaxione said:
Read throught the thread. The only thing google are saying is that the cant reproduce the problem. Can read anywhere that they will fix it.
Mvh J
Click to expand...
Click to collapse
They can only fix it by update
SAW_JOK3R said:
They can only fix it by update
Click to expand...
Click to collapse
If you read through that thread you will se that it was set to completed because of that the google employee couldnt reproduce the problem and therefor asks people to ask for a replacement phone. So I dont think they marked this thread Completed because it will be solved in an update.
Br J
Jaxione said:
If you read through that thread you will se that it was set to completed because of that the google employee couldnt reproduce the problem and therefor asks people to ask for a replacement phone. So I dont think they marked this thread Completed because it will be solved in an update.
Br J
Click to expand...
Click to collapse
Yeah, I know. That's why said. As it's marked as completed, that means the support team of the forum was not able to solve the issue so they've forwarded the issue to Google devs to solve it
SAW_JOK3R said:
Yeah, I know. That's why said. As it's marked as completed, that means the support team of the forum was not able to solve the issue so they've forwarded the issue to Google devs to solve it
Click to expand...
Click to collapse
Lets hope they do. It must be software related in my case. Noticed a thing when testing a bit today. When I hold my phone normally the "crackle" / "bad sound" comes from the top speaker and the bottom one sounds fine but if I turn the phone to landscape mode the crackle jumps down to the bottom speaker and the top speaker sounds fine. Reaaally strange
Br J
Jaxione said:
Lets hope they do. It must be software related in my case. Noticed a thing when testing a bit today. When I hold my phone normally the "crackle" / "bad sound" comes from the top speaker and the bottom one sounds fine but if I turn the phone to landscape mode the crackle jumps down to the bottom speaker and the top speaker sounds fine. Reaaally strange
Br J
Click to expand...
Click to collapse
The crackle problem does the same on me ,except the landscape experiment which I haven't done .But if it really occurs just as you explain ,than it is most probably (or it looks like) software related issue. Anyway it indeed seems strange :|
I just enabled encryption and regarding cracks and rispy sound it seems better.
Maybe someone else who have this issue can test?
I definitely have this issue. On latest M firmware on Sprint variant. I manually flashed firmware.. Saw somewhere else on here where someone solved problem by installing viper audio and setting to super hi quality sound.. May try that. Seems like I recall on og Nexus 7 some kernels would cause the device to get too hot (like the charger that came with phone does for me..) And speakers would get messed up as a result and distort. Hope that's not the case here. :banghead:
Its most likely software. It almost sounds the same as the speaker distortion that the one m8 had when running cm due to the lack of proper audio drivers. Its most likely a driver issue which is why some have had success with viper. For now I would not max out volume when using the phone just to protect the speakers and we will just have to wait and see if google releases a fix.
toknitup420 said:
Its most likely software. It almost sounds the same as the speaker distortion that the one m8 had when running cm due to the lack of proper audio drivers. Its most likely a driver issue which is why some have had success with viper. For now I would not max out volume when using the phone just to protect the speakers and we will just have to wait and see if google releases a fix.
Click to expand...
Click to collapse
I sure hope that you and others who've said same are correct. If that is the case Google needs to get with it and push an image that fixes it asap.
Update: (Sprint N6-latest firmware-M..) I installed Dirty Unicorn test build 5.1 dated 3/29 from their G+ community and not one crackle comes out even on the highest volume my device is fine. Was not like that on stock Google rom.. I was getting a feedback sound coming from exterior speakers as well and its not present anymore. Just wanted to share that.

P10 VTR-AL00 Call Issues

Hello there!
I was travelling through China last year and bought the P10 VTR-AL00 while I was there. I checked so that all the bands were supported in my home country of Sweden and it was all good.
I've had the phone for nearly 10 months now and love it so far. I haven't had any issues apart from one thing - when I'm in a call my microphone just stops working for a few seconds at a time. It usually happens after like a minute and then every minute or so after that (though, this varies). It's just temporary (like 3-5 seconds) but the person on the other end always thinks I've disconnected and asks if I'm there. The weird part is that it's just my microphone - I can still hear them loud and clear.
I've looked around in the settings to see if there's some gesture thing or whatever but I'm at a loss. Has anyone else had this issue? Or is there some feature/bug that I should be aware of?
If I recall correctly it has been like this since the beginning but I hoped that an update would fix it. That doesn't seem to be the case!
I appreciate any help!
Umbriferous said:
Hello there!
I was travelling through China last year and bought the P10 VTR-AL00 while I was there. I checked so that all the bands were supported in my home country of Sweden and it was all good.
I've had the phone for nearly 10 months now and love it so far. I haven't had any issues apart from one thing - when I'm in a call my microphone just stops working for a few seconds at a time. It usually happens after like a minute and then every minute or so after that (though, this varies). It's just temporary (like 3-5 seconds) but the person on the other end always thinks I've disconnected and asks if I'm there. The weird part is that it's just my microphone - I can still hear them loud and clear.
I've looked around in the settings to see if there's some gesture thing or whatever but I'm at a loss. Has anyone else had this issue? Or is there some feature/bug that I should be aware of?
If I recall correctly it has been like this since the beginning but I hoped that an update would fix it. That doesn't seem to be the case!
I appreciate any help!
Click to expand...
Click to collapse
Might be:
-Bug of your firmware, what version do you have? Maybe Check for updates via firmwarefinder
-Is Wifi Calling enabled or disabled?
LwannaCM said:
Might be:
-Bug of your firmware, what version do you have? Maybe Check for updates via firmwarefinder
-Is Wifi Calling enabled or disabled?
Click to expand...
Click to collapse
Hey, thanks for the reply!
I'm on version VTR-AL00C00B217 . I've updated it a few times over the months I've had the phone. No new updates at the moment.
I looked around for WiFi calling but couldn't find it anywhere. Tried to search for it in settings and tried looking in the advanced settings but to no avail. It seems my version doesn't offer that. I found this thread where someone posted a photo of the "More" section of the settings page. It looked like this, whereas mine looks similar to this.
I have no issue with mobile data or Wifi connectivity by the way.
It is a bit embarrassing to admit, but I've had this with another device. It turned out that I sometimes accidentally covered the microphone with one of my fingers
M1chiel said:
It is a bit embarrassing to admit, but I've had this with another device. It turned out that I sometimes accidentally covered the microphone with one of my fingers
Click to expand...
Click to collapse
LOL =)
Glad you could fix your Problem
M1chiel said:
It is a bit embarrassing to admit, but I've had this with another device. It turned out that I sometimes accidentally covered the microphone with one of my fingers
Click to expand...
Click to collapse
Haha, yeah that's a possibility! I'll have to try that!
I tested recording myself with the sound recorder whilst covering up the microphone. On playback and when I covered up my microphone I only had signal in the left earphone but when I let go the channel switched to the right. Real strange. I'll be back when I've done some tests with calls

New firmware?

Hi guys is any of you guys has new firmware? 4_22B?
if you do how tp get it?
https://ibb.co/nbkqdfs
echocae said:
Hi guys is any of you guys has new firmware? 4_22B?
if you do how tp get it?
https://ibb.co/nbkqdfs
Click to expand...
Click to collapse
How to get it... apply for a job @ Nokia.... learn the definition of the last character of the firmware build... it says B guess what it means.
So unless it gets leaked, which most likely won't happen, you've to wait for an A
Hawkysoft said:
How to get it... apply for a job @ Nokia.... learn the definition of the last character of the firmware build... it says B guess what it means.
So unless it gets leaked, which most likely won't happen, you've to wait for an A
Click to expand...
Click to collapse
well if B is Beta.. then A.. is Alpha... so we need F.. Full Version...:laugh:
That looks legit and could be the new release. I wouldn't pay much attention to the letters. There's new builds of touch and camera firmware, which could mean lesser issues with the fingerprint sensor and the camera errors.
Apparently nokia said via Twitter that they had some one time issue in getting the security release on time. That we should expect a FM this week. Not sure if it is true. But I'm disappointed that they don't honor the Android One promise
I'd much rather prefer they get the update right in terms of fixing whatever camera issues/fingerprint sensor they resolved than getting it sooner half-baked that will require yet another update.
My stable version has a F in the end
isopure said:
I'd much rather prefer they get the update right in terms of fixing whatever camera issues/fingerprint sensor they resolved than getting it sooner half-baked that will require yet another update.
Click to expand...
Click to collapse
Yeah for the camera I don't mind to wait. But for the security updates I do mind to wait as this is a separate update that has nothing to do with camera
There is updateV.4.22C .Just instaling ( in Poland )
Netherlands as well
India!
Also in Spain.
New update build number
I just updated to the latest update, fingerprint enrollment hasbeen update, Its quite reliable and has a more success rate, still slow but I don't mind it since not tell me to press harder like before, hope it gets better with future updates.:laugh:
Never mind fingerprint. Camera is what most people bought this phone, and it was horiblle also ( I mean app ).Lot's of bugs
Any release notes?
Just applied update
Fingerprint reader is now perfect though aesthetically the small brackets around the thumbprint distract. Can't say anything about camera.
250Mb. Took a very long time to install over a fast wifi connection. I was afraid that I had bricked my phone.
United States. T-Mobile. Unlocked phone.
The bug in translation in Camera app still present (bokeh). Fingerprint sensor almost as ****ty as it was. I deleted all fingerprints and added four new. Press harder...
FP still ****.. maybe due to screen protector too thick...
Camera is improve littlebit Manual still have bug eventhou u set the shutter speed still go automatic
Pro mode is still buggy i think..When cam set to "ISO prority" ( ISO set on 100 ) assuming, that camera mesures exposition automatically, the time suppose to be selected in auto position, and it all suppose to give proper exposition. But when ISO is set , time goes itself to 1/33 sec, that gives total underexposition. Time has to set manually based on the display preview to have things to work. So does it mean, that in Pro mode exposition hase to be set manually, or it is another bug? Timer sound in Cam app ,still not working correctly
No... In pro mode everything is manual

Categories

Resources