There are many people here asking on how to fix the low in-call volume bug present in our cyanogenmod and cyanogenmod based roms.
They have been posting everywhere creating useless threads asking for fix or posting in original development threads of the respective roms on how to fix it.
So, here it is:
There are TWO methods to fix it:
1. Press Vol - and then Vol + after picking up the call EVERYTIME.
2. Or, you can simply install the attached file and run it ONCE, it will be activated and everytime you accept a call, it will automatically do the work
PS: I did not create this tweak, somebody else did, I'm just sharing it with you
szzlgupta said:
PS: I did not create this tweak, somebody else did, I'm just sharing it with you
Click to expand...
Click to collapse
I have created this app.
Anyone can take it from here: http://forum.xda-developers.com/showthread.php?p=50965848 where I'll post updates.
P.S. Sajal, manny thanks for sharing this to anothers!
szzlgupta said:
There are many people here asking on how to fix the low in-call volume bug present in our cyanogenmod and cyanogenmod based roms.
They have been posting everywhere creating useless threads asking for fix or posting in original development threads of the respective roms on how to fix it.
So, here it is:
There are TWO methods to fix it:
1. Press Vol - and then Vol + after picking up the call EVERYTIME.
2. Or, you can simply install the attached file and run it ONCE, it will be activated and everytime you accept a call, it will automatically do the work
PS: I did not create this tweak, somebody else did, I'm just sharing it with you
Click to expand...
Click to collapse
That is not the problem,Even at full volume I get half the volume I used to get on my stock rom (sense) (I am using the HTC one m7 running Cyanogenmod)
Does this work on any ROM?
darkandroid13 said:
That is not the problem,Even at full volume I get half the volume I used to get on my stock rom (sense) (I am using the HTC one m7 running Cyanogenmod)
Click to expand...
Click to collapse
I agree
Related
I went through this whole thread...http://forum.xda-developers.com/showthread.php?t=1738055 and i still was unable to find a solution a solution for a couple of things...I am beginning to think I have another rom than what the pictures indicate. But I only found one download link. Any help would be appreciated.
I was missing the "Framework Modification" but i then saw that they replaced it with the "Xperia Home Preferences" which i still cant find it in my rom
I still cannot find a solution for the Clock
I do not have "Recovery" option when i hold down the Power button to power down.
Didnt get the Walkman app when i installed i installed it after.
** Also if anyone can tell me how i can disable the vibrate when i unlock the phone that would be wonderful.
**Also i know i can put in an aftermarket unlock screen but just wondering if i can add another shortcut to the lock screen maybe slide up to get to the dialer or messaging ?
I believe all the screen shot which are updated there do not belong to Rls 11, there are some old screen shot also. Regarding the recovery it depend on the your custom Kernel, if you are on locked BL you will not get it.
Hit Thanks if i helped you
Recovery not essential
Understandable, the Recovery is not something essential I was just pointing the things out that led me to believe i was on the wrong rom...what about the absence of the Xperia Home Preferences and or the Framework Mod? And the Clock?
india86 said:
I believe all the screen shot which are updated there do not belong to Rls 11, there are some old screen shot also. Regarding the recovery it depend on the your custom Kernel, if you are on locked BL you will not get it.
Hit Thanks if i helped you
Click to expand...
Click to collapse
Calm down, all the things that you are asking were previously asked in the ROM thread. I asked first some of these. So you could use search button.
Now, most of the screenshot you see in the first post of pureness are from build 10 or even before this. In build 11 there is not home preferences anymore, and the clock has been put into the scroll menu. This is because of the new xperia GX launcher and Jelly Bean UI.
If you still want the clock in the top bar you can search for a battery icon mod, someone who said something like "I didn't like the pureness icon, so I made it by myself". If you flash one of those you will get clock in the middle, too.
Recovery option in the power menu has been deleted beacuse of some incompatibiles. If you don't want to press volume down when rebooting, you can download "X-parts" from the store and use its "Reboot into recovery" tool.
Walkmann app is an addon, you can read it in the firsts posts of pureness. You can download walkmann from ThilinaC thread in "Themes and Apps"
** You can't, as I know. Maybe you can search about editing some values in system files
*** The pureness lockscren is something like a beta, it is wrote in the firsts post of pureness, so you can't do much about. You can dowload an aftermarket locker.
Hit thanks if I helped you
So, As the title suggests, I've got a problem with my volume buttons in the FaaastJB v2.5 ROM.
The problem is they simply don't work. I've used a key testing app and when pressed, they both give "Unknown Key". However they work on my recovery and on the stock rom so its not the hardware itself. I've managed to get everything else working using the drivers on the site but I don't know if there is a driver related to the volume buttons or whether there is a file somewhere that I need to change? I have a backup of the system of the stock rom so can copy any drivers/files from there but so far nothing I've tried has worked.
So I'm wondering if anyone could point me in the right direction to fix this?
I would have posted this in the ROM thread but I haven't posted enough on XDA yet
Any help would be greatly appreciated!
EDIT: Doesn't Matter, It's been fixed. Turns out it was sun4i-keyboard.kl. The volume up and volume down were some random numbers instead of 115 and 114.
Thanks!
Adam
ajp8868 said:
So, As the title suggests, I've got a problem with my volume buttons in the FaaastJB v2.5 ROM.
The problem is they simply don't work. I've used a key testing app and when pressed, they both give "Unknown Key". However they work on my recovery and on the stock rom so its not the hardware itself. I've managed to get everything else working using the drivers on the site but I don't know if there is a driver related to the volume buttons or whether there is a file somewhere that I need to change? I have a backup of the system of the stock rom so can copy any drivers/files from there but so far nothing I've tried has worked.
So I'm wondering if anyone could point me in the right direction to fix this?
I would have posted this in the ROM thread but I haven't posted enough on XDA yet
Any help would be greatly appreciated!
EDIT: Doesn't Matter, It's been fixed. Turns out it was sun4i-keyboard.kl. The volume up and volume down were some random numbers instead of 115 and 114.
Thanks!
Adam
Click to expand...
Click to collapse
Hi, can you explain how you fixed that? I got the same problem, I replaced sun4i-keyboard.kl that worked for me in ics, and chmod 755, but still don't working. Any idea?
Edit: My mistake, I readed sun4i-keypad.ko, To fix this I¨ve just edited /system/usr/keylayout/sun4i-keyboard.kl and get volume buttons working again. I used my keys volume_up 139 volume_down 102
I have been using epinter's CM10.1 for Atrix 4g and following the Atrix 4g CM10.1 developer discussions. I am trying to get the camera flash to work. krystianp posted that one should extract from CM9, the files tcmd and tcmdhelp and put in /system/bin. But I cannot find a CM9 for the Atrix 4g (olympus) that has these files. Does anyone know where to find them? (Would have posted to the CM10.1 thread but don't have permission to do so.)
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Thanks
andresrivas said:
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
rhcohen said:
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
Click to expand...
Click to collapse
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
reply
Feche said:
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
Click to expand...
Click to collapse
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
rhcohen said:
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
Click to expand...
Click to collapse
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
reply
Feche said:
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
Click to expand...
Click to collapse
For what it is worth, I just installed the 12/31 kernel and the flash with stock camera app now DOES work for me*, and the timing even seems to be OK. So someone ought to be interested in understanding the difference between your configuration and mine. (If anyone is actually following this, my sequence, executed over the past week or so, was a wipe/clean install of epinter's 12/11 CM10.1 rom, followed by his latest gapps, followed by a second flash of the 12/11 rom. Then this morning putting the tcmd and tcmdhelp files in /system/bin, with appropriate permisssions; and then finally flashing krystianp's 12/31 kernel.) Too soon to comment on battery life.
I think this kernel is supposed to be logging network disconnects (which I also seem to experience, about one a day, requires reboot to reconnect). Do you know where we find the resultant logs, and how (lacking permissions to post at the developers' site) we are supposed to deliver them to krystianp? I notice that, in response to a submitted log file, krystianp made a post about restarting the radio from a terminal, which didn't actually achieve a re-connection for the one person who tried it.
* small update: the flash works with stock app, but only if I do a spot ("touch") focus first. Small price to pay!
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks --- so I found the relevant krystianp post on the logs:
http://forum.xda-developers.com/showthread.php?p=48954198&highlight=dmesg#post48954198
Specifically,
"To get kernel log just do (as root):
dmesg>/sdcard/kernel.log
And for radio log do:
logcat -b radio >/sdcard/radio.log
(Logcat works continuously so you might have to use ctrl+c to cancel it) "
Question is, what do I do with these logs? I could attach them to a reply at the developer forum if I had permission to reply....
Presumably I don't want to keep running this kernel with debugging turned on forever.
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks, I will wait a couple of days so there is some accumulated info in the logs and do that. So far, no drops and one spontaneous reboot.
reply, to forward to krystianp
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
rhcohen said:
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
Click to expand...
Click to collapse
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
You should have mention him by @krystianp . Not sure it will work from the phone
Hit the damn thanks button instead!
Enviado desde mi MB860
RE turning radio off and on
overboard1978 said:
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
Click to expand...
Click to collapse
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
further update
rhcohen said:
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
Click to expand...
Click to collapse
----------
OK I have a further update. Using the testing tab from the dialer gives me the option of turning the radio off; when I click it nothing changes -- in particular no option to turn the radio on.
When I try krystianp's echo "shutdown" and echo "powerup" commands, I get a system prompt back but no indication that anything has changed with the radio (though maybe it would be reflected in the radio logs). In any event, certainly no connection to the network.
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
rhcohen said:
----------
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
Click to expand...
Click to collapse
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
reply; and what is "uv"?
PolesApart said:
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
Click to expand...
Click to collapse
-------------
Thanks. Sending the logs may no longer be relevant; @krystianp posted a new kernel a day and a half ago. I flashed it yesterday, and so far, no radio drops. If I get any I will post another message with logs and also send a message to krystianp.
I notice in describing the new kernel he says he made changes to radio and UV. Can someone tell me what is UV? I tried a search in the 10.1 developer forum and a more general google search but find nothing useful (I suspect this use of "UV" does not mean "ultra-violet".)
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
reply
PolesApart said:
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
Click to expand...
Click to collapse
I saw today's post but didn't interpret it the same way. He had already said that this kernel, along with the one from 12/31, were for people with the disconnect errors (which I was getting), but when he posted the Jan 5 kernel he indicated there were changes to radio and UV; I thought today's notice was just reaffirming the purpose of both the 12/31 and 1/5 kernels.
The 12/31 kernel clearly did more than just turn on logging however, as it seems to have fixed the camera flash for many (including me).
And the 1/5 kernel seems to be working more stably for me -- 1 1/2 days now without a radio drop. Maybe just luck.
Q&A for [ROM][SIRIUS][LP][5.0.2][SM-4.9] CyanogenMod 12 Unofficial [NIGHTLY BUILDS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SIRIUS][LP][5.0.2][SM-4.9] CyanogenMod 12 Unofficial [NIGHTLY BUILDS]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Google play and audiofx
The audiofx app doesn't appear to have any effect on the music playing from the google play music app. I've tried going into the audiofx app from within play music, but I just can't get it to work on play music. Not too sure whether audiofx has any affect on other apps other than the default music app. I'm on the latest build (20150111 V2)
Other than that, I can't find any problems. Great work!
no vibration
Hi! This is a great ROM!
Is there a option to activate Vibration?
Bluetooth audio fix by one click
At least for me with my car hi-fi (LAC7000) on the latest nightly dirty flashed over 12. Click Bluetooth, than the device connected for, the gear next to it. Uncheck the first and the third. Like the screenshot attached.
Recovery is not Ok. Lopping on boot.
I have flashed recovey like that
fastboot flash recovery openrecovery-twrp-2.8.3.0-sirius.img
After it, My ph is looping on logo. Pls fix bro.
greenhorn82 said:
Hi! This is a great ROM!
Is there a option to activate Vibration?
Click to expand...
Click to collapse
As in vibrate mode? Sure! Just keep pressing the volume down button when there's no media playing and you'll feel the phone switch to vibrate.
TheDefaultState said:
As in vibrate mode? Sure! Just keep pressing the volume down button when there's no media playing and you'll feel the phone switch to vibrate.
Click to expand...
Click to collapse
No, I mean sound and viration at the Same time.
greenhorn82 said:
No, I mean sound and viration at the Same time.
Click to expand...
Click to collapse
Media volume can be changed within the sound and notification settings in the settings and also when media is playing. There's also an option to also vibrate for calls in the sound and notification settings as well.
Thanks!
After closely watching the development for a month, yesterday I decided to flash it with some outdayed cwm based PhilZ Touch recovery. The install was not successful, and even broke the recovery :S This freaked me out a bit, but after successfully fastboot-flashing stock firmware and newest cwm, I tried again today. The result was the most butter smooth android lollipop experience! Thanks for this amazing rom
Recovery Doesn't work for me
Hi !
First thanks for your amazing rom Infected_ .
For me I have a problem with recovery , it doesn't work with CM12 Recovery ( I can't flash any zip files from my sd card), I must install CM11 recovery V6.0.5.1 which is working very well. When I want to update cm12, I must install CM11 recovery each time.
Do you have a solution for this?
Reboot doesn't works for me, only power off my phone.
Thanks a lot
Build 2015-01-14
Big thx to you infected for your amazing work. Keep it up !
build 2015-01-14 with included kernel
- bluetooth is seriously ****ed up (reboot, switching on/off doesn't help) (i hear something for a second or two then it stops)
- call keeps ending after a minute or so (without speaker phone, i didn't try speaker phone)
That's it
Lockscreen background
Maybe i`m blind, but is there a point to change the Lockscreen background ???
Upgrading to the 20150116 from 20150112v2 via a dirty flash caused it to fail to boot (stuck at the Sony logo). Required me to format System and clean install. Total pain in the ass cause I hadn't done a backup (I'm an idiot, complacency is gonna be my downfall).
Just a gentle reminder to do backups frequently when flashing nightlies!
Super stoked with the ROM, the camera quality is fantastic (better than stock I think - I rooted before you could backup your TA partition and I think my camera quality was never quite the same).
Solution?
I had the exact same problem with the kernel you use, only I managed to wipe both the rom and the recovery. After I flashed a stock fw and the newest cwm (http://forum.xda-developers.com/showthread.php?t=2702001) I could finally flash this rom.
Testing Results for latest version (nightly 1-16-15)
This build is in very good shape. Throughout my wanderings, I have noticed that only a few things that could be fixed (these might have already been recommended, but I am posting them anyways). First, the physical camera button does not work. I understand it is hard to build that button into a CM build, but I figured I would just write it down. I already know that someone has posted this recently, but I would just like to confirm. Another thing is that the double tap to wake feature in the display settings does not function. It can be selected, but the feature will not function, and sometimes the toggle undoes itself after a short period of time anyways. Although, it does not function even right after enabling the feature through the settings. I would also like to ask about charging. I believe CM does not support quick charging at this time, but I have noticed that it takes significantly longer to charge my device than stock rom. I have tried a variety of chargers, and I achieve the same result. I am just using standard 2.0-2.4 Amp chargers that my device has always used. I just have noticed that it takes a long time to charge (significantly longer than my OPO, but that thing charged faster than my Z2 in the first place). Last thing that I have noticed is very minor. On stock rom, the camera had an option for 16:9 15.5 MP shots that I frequently used since I do not really like 4:3 photos. I know the camera was a pain to get working in the first place, but this setting is not present anymore (in the included app and third-party apps). Anyways, these builds are really nice, much better than I expected for nightly revisions, so thank you!
DT2W works 20150118.
TWRP
Hi there,
first of all great work! The Rom ist just running fine on my device. The only problem seems to be the delay on calls.....but that's nothing to worry about^^. The other problem i have.....i flashed the twrp recovery several times. The twrp recovery does start....but only with the *.bat installer in windows. When i try to start it from the device it doesnt work. Instead, the cm12 recovery does start. Did i miss smth?
Greets form germany ;D
Got some problems with last build. Phone restarts after shutting down. Calls on Viber, Hangouts and Skype are broken. So I cant hear the other person. but he can hear me.
Su binary
cannot update my su binary..any suggestion?
Updating SuperSu
freshvibez77 said:
cannot update my su binary..any suggestion?
Click to expand...
Click to collapse
This is an issue, but you can update supersu by flashing the latest zip file here: download.chainfire.eu/supersu
I'm sorry for not posting a link, but XDA won't allow me to because of how new my account is. Just copy and paste that to get to Chainfire's SuperSu download page
BTW, this problem also happened to me with stock everything, no root, no kernel, no nothing (except oem unlock).
Sometimes (not everytime, but a lot of times, so it´s bothering) when I click a media (photo or video) in whatsapp, and I press the back button, whatsapp freezes for about 30 seconds, I can pull the drawer and use the phone normally, but if I try to use whatsapp, it just hangs there and eventually comes back. This started happening with Lollipop and older versions of whatsapp, but it´s still bothering me even after a clean flash and Im now on 6.01 with Elemental X 6.11 on my Nexus 5. I´ve tried diferent default media players but same thing happens. I contact whatsapp and at first they blamed my phone being modified (rooted), but it happened after a clean stock flash also. Please can anyone help me diagnose this?
I saved a video of the problem so you can see what I mean: https://plus.google.com/+TarcísioLopesGFC/posts/2fum2Nd2RY5
Thank you
Have you managed to solve it? I'm facing the same issue and cannot find any solution for it
niiiro said:
Have you managed to solve it? I'm facing the same issue and cannot find any solution for it
Click to expand...
Click to collapse
Hi niiiiro, Im glad Im not the only one, but unfortunately I have not found a fix for this. and believe me, I've tried a lot of different things.
-Whatsapp has a support email, that won´t respond.
PLEASE come back to the forum and share if you ever fix this.
Thank you
##- WhatsApp Support -##
Hi,
We apologize that we have not gotten back to you. If your issue has been resolved, please ignore this message.
Most issues can be resolved by using our FAQ. Please visit our FAQ if you have not done so already.
If your issue has not been resolved, we want to help you as quickly as possible. Please write us back with as much detail as you can provide about the issue that is occurring. Anything under five words will likely not be enough information for us to figure out your issue.
If you are able to open WhatsApp and WhatsApp is verified, please send us logs:
Launch WhatsApp.
Press the [Menu Button].
Tap [Settings] > [Help] > [Contact Us].
Enter a description of the issue into the description field.
Select [Next].
Tap [This does not answer my question] at the bottom if any results are displayed.
Send the email.
The above steps will automatically generate a log file as an email attachment.
We are looking forward to hearing from you!
--
WhatsApp Support Team
Interested in translating for us? Please visit our website: http://translate.whatsapp.com
Take a look at our FAQ: http://www.whatsapp.com/faq
Attached an adb logcat file
After installing new version from whatsapp.com/android I still have the back button bug AND now I can´t connect to web.whatsapp.com anymore.
niiiro said:
Have you managed to solve it? I'm facing the same issue and cannot find any solution for it
Click to expand...
Click to collapse
Were you able to solve this?
Is your bootloader unlocked? Mine is... maybe that´s causing it?