Related
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
may i know why you flashed the latest stock rom using your sd card. would it not be easier to flash through your pc using a usb cable?
you might want to check the meaning of "bricking the phone"...........
then remove it from the title of the thread........
As Rurph mentioned, flash it via your pc, still following the instructions from theHTC site
I now tried flashing through PC, same freezing occurs.
To reiterate:
I have an original HTC HD2 bought from the official HTC shop in Czech republic.
I downloaded the latest official ROM for HTC HD2 from the official htc.com/cz website using my original serial number.
The download finished successfully every time (I tried it 5 times from all the different servers), and the SHA-1 hash of the files was identical every time.
I now flashed it using the normal PC method - everything appeared successful.
I also tried extracting the nbh file from the downloaded file - both by running the .exe file, and by extracting it using winrar - both methods gave me the same nbh file with the same SHA-1 hash. Then I moved the leoimg.nbh to the root of SD card and flashed using the SD-Card method. Everything appeared successful.
Both of the above methods give me a system that freezes completely at random. For example when starting the phone, it can just freeze (left it for 8 hours over night, it remained frozed), when moving from 1 tab to another (freezes in the middle of the animation), when opening the start menu, when going into settings, when making phone call, when opening SMS, and most importantly when NOT DOING ANYTHING AT ALL.
What can I do?
Try to flash an older Version.
I don't know if its possible, but maybe that solves your problem.
Did you have SPL 3.03? If no... Install HSPL and use a custom ROM like the one from NRGZ28 (EnergyROM)
If you an't flash the older version via RUU (Rom Update Utility) try to flash it from SD card. You can also perform a "task 29" with MTTY (before you flash)
But be careful, you can brick your phone...
I have always only used official ROMs from HTC, so I never needed HSPL so I never installed it. I also always prefer the official ROMs so I would rather not use a cooked one.
I think flashing an older version would solve the problem, however I would rather like to find out what the cause is...
So far, I managed to get my phone to a useable state by running Android from the SD card - it works flawlessly for all my purposes. The only problem was to start Android through Windows before windows manages to freeze...
Given that android does not freeze, I believe that the freezing problem must be a windows mobile issue.
Any suggestions for tracking down this freezing problem? Could it be a hardware issue?
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
oh and you didn't leave the old application data folder on your sd card did you? or try to restore registry settings?
samsamuel said:
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
Click to expand...
Click to collapse
I always hard reset before and after a flash. No change - freezing still occurs.
Even when I did multiple hard resets, the freezing persisted.
The SD card is freshly formatted, checked for no filesystem errors.
I did not restore any settings or anything else - the problem occurs on a completely fresh clean flash.
Additionally, the problem occurs even with no SIM card or SD card inserted into the phone.
Overheating?
I concur with rr5678, seems more like overheating than ROM problems, esp. that I've had the same ROM for a week with no problems whatsoever
hence kind request to OP: check overheating threads and please change the thread subject to a more accurate one so it does not spread misinformation and panic
as for the overheating - 1st thing to do is installing BattClock and monitoring correlation between freezes and battery temperature
rr5678 said:
Overheating?
Click to expand...
Click to collapse
The phone is definitely not overheating. It is very cold to touch and it runs Android without a problem.
OK I did some more testing - going back to any previous ROM fixes the freezing. Then installing the newest ROM reintroduces the freezing.
Given that it is definitely not a hardware issue (works on previous ROM, works on Android, no overheating), it looks like a Windows mobile issue.
I am surprised that nobody else is experiencing this. How come I am the only one? What is so special about my phone?
And the new firmware can "brick" the phone - a less skilled user would not be able to do anything with a frozen phone...
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
b2206015 said:
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
Click to expand...
Click to collapse
Try another sim card if you can. I know it sounds crazy but...
wardh said:
Try another sim card if you can. I know it sounds crazy but...
Click to expand...
Click to collapse
Thanks for the advice - but given that the phone freezes even with no SIM card inserted, I do not think that it is the case...
I have however tested inserting a different SIM card anyway, and the freezing occured again...
I too faced constant freezing problems with the official ROM but then I used HSPL and flashed a different radio (2.12 in my case) and ever since never faced any freezing problems..worth a try I guess...
epic fail
not being picky, but "bricking" is, as far I know, by definition an irreversible problem? Hanging and freezing and re-booting are not bricking.
That said, sorry to hear about your troubles.
Sounds like going back to your old ROM is the only solution right now.
b2206015 said:
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
Click to expand...
Click to collapse
Psaldorn said:
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Click to expand...
Click to collapse
Well, to me it seems your phone just doesn't like custom ROMs.
Hi everyone.
I have recently upgraded my SGA from original 2.2.1 to 2.3.3 XXKPE and i have detected an issue when i try to use the WPA + AES combination. The phone detects the wifi but it tries to validate the password a few times and then it is disconnected...
When i tried to connect with the older firmware (Froyo 2.2.1) i could connect the first time but when i lost the connectivity my wifi changed it's state to error and the only way to reconnect was restarting the phone.
No issue detected with WEP or WPA + TKIP.
Anyone else has the same problem? If not, can you tell me your firmware version?
Many thanks in advance
Same situation: S5830 + ASUS WL500W works only with WPA TKIP. But with TKIP speed is limited to 54mbps. Android OS 2.3.4
Just picked up a Samsung Galaxy Ace running stock Android 2.3.4 (baseband S5830LUBKP7, kernel 2.6.35.7-perf-CL366939 [email protected] #1), and seem to be having this same problem.
My home wifi is set to WPA2 Personal+AES, and when the correct passphrase is entered, the Ace just continuously cycles through "Connecting... Disconnected", over and over.
If I drop back to WPA Personal+AES, I get the exact same thing. *However*, if I drop to WPA Personal+TKIP, the phone connects immediately.
I really don't want to use TKIP, as it has known exploits. Is there a known FOTA update for a US-market, unbranded Galaxy Ace that fixes this, or is there any known workaround except "don't use AES"?
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
evilxdeadly said:
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
Click to expand...
Click to collapse
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
knoxploration said:
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
Click to expand...
Click to collapse
Just update it over the air from setting -> about/phone -> update.
Make sure you have backed up the data like contacts and sms.
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
alexnm said:
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
Click to expand...
Click to collapse
Check the OP date?
Oops, didn't see that, sorry :$
alexnm said:
Oops, didn't see that, sorry :$
Click to expand...
Click to collapse
No need to be sorry. You're replying to a thread that's current, in that I replied to it with my own problem. (And I did so because it was the only thread that came up in the Ace forum on a search for AES, which seems to be specific to the problem. Didn't seem to make sense to start a new thread when this one covers the same topic.)
Fixing mobile data (3g) after installing Cyanogenmod 7 (nightly)
Hello all. I'm writing this as a long-time lurker and custom ROM / kernel user, who has been helped along greatly by this forum.
I had a long-standing issue that I couldn't find any clarity on: my mobile data access didn't work after switching to custom Roms/Kernels from LG's original Froyo Rom.
After months of thinking it was just an odd bug, and something to live with (since I rarely use data), I decided to look a little deeper into the problem. I found it difficult to even find information on the problem - there's a lot of bad information, and a lot of hard-to-read information from friendly, but not perfectly fluent English speakers.
In short, I'm hoping that others who are struggling with this issue will find this post with some Googling, and won't have to be as confused as I was.
After doing the following, I have everything working perfectly and here's how I did it:
1) I knew that the right baseband (under About Phone, in Settings) had something to do with mobile connections, including 3g data authentication and transfer. I found that v10 (and older) basebands are considered the 'old' baseband, while v20 basebands are considered 'new' basebands.
2) Cyanogenmod often reports the baseband incorrectly, so finding out what baseband you're on is unreliable through the About Phone menu, if you're already on CM7.
3) There are some scary sounding techniques to update your baseband (one involves using a poorly documented program called 'LGMDP-v1.5.exe'). These techniques can apparently brick your phone, so I avoided them. I might be wrong on some of the details here, so let me know!
4) I instead obtained the latest baseband by simply letting the LG update software (in my case from LG.ca) update my phone to Android 2.3. I noticed that I now had baseband v20. My mobile data worked!
5) I then re-rooted the phone, using SuperOneClick.
6) Installed the latest CM7 nightly. Mobile data no longer worked
6.5) I should mention, I tried other ROM/Kernel combinations and ended up having crashes and hangs on boot - thankfully I could use 'adb reboot recovery' to get back to Clockwork Recovery, when even holding various keys on reboot to do this didn't work).
7) Installed the wonderful ta-gb 1.1 kernel (thanks to all of the devs who worked on this and others like it).
8) And lastly (and possibly most importantly) I came across this:
https://github.com/CyanogenMod/andr...gingerbread/prebuilt/common/etc/apns-conf.xml
It's a list of APN information, which corresponds to different carriers, and appears to be necessary for mobile data connections. My carrier (Koodo) was not listed here, and therefore appears to not be included in even the latest Cyanogenmod 7 (as of Feb 2012).
9) This led me to find this: http://code.google.com/p/cyanogenmod/wiki/APNlist
Which happened to include the APN information for my carrier that I needed to put in, under Mobile Networks > Access Point Names.
Inputting that information made my 3g connection start up instantly. I was able to check that things looked good by typing *#*#4636#*#* in the dialer, and looking under Phone Information.
Maybe you're a veteran CM7 user, and think this is obvious newb stuff, but I want to leave this thread here for any other users who were stuck as long as I was.
If you fixed this issue with a different method, please share what you did here. If you're a ROM/Kernel dev with more insight on anything that I covered, please comment.
Cheers.
Are you doing this on v20 baseband?
I also have trouble with data on nightly's. I know DJ posted on the cyanogen forum today, saying Adam got a new Sim (128k, the ones causing problems) for testing. There should be a fix soon, fixing this problem.
Sent from my LG-P500 using Tapatalk
Paulenski said:
Are you doing this on v20 baseband?
Click to expand...
Click to collapse
Yes. Is your carrier's APN information available to try all that I wrote above?
bambu85 said:
Fixing mobile data (3g) after installing Cyanogenmod 7 (nightly)
Hello all. I'm writing this as a long-time lurker and custom ROM / kernel user, who has been helped along greatly by this forum.
I had a long-standing issue that I couldn't find any clarity on: my mobile data access didn't work after switching to custom Roms/Kernels from LG's original Froyo Rom.
After months of thinking it was just an odd bug, and something to live with (since I rarely use data), I decided to look a little deeper into the problem. I found it difficult to even find information on the problem - there's a lot of bad information, and a lot of hard-to-read information from friendly, but not perfectly fluent English speakers.
In short, I'm hoping that others who are struggling with this issue will find this post with some Googling, and won't have to be as confused as I was.
After doing the following, I have everything working perfectly and here's how I did it:
1) I knew that the right baseband (under About Phone, in Settings) had something to do with mobile connections, including 3g data authentication and transfer. I found that v10 (and older) basebands are considered the 'old' baseband, while v20 basebands are considered 'new' basebands.
2) Cyanogenmod often reports the baseband incorrectly, so finding out what baseband you're on is unreliable through the About Phone menu, if you're already on CM7.
3) There are some scary sounding techniques to update your baseband (one involves using a poorly documented program called 'LGMDP-v1.5.exe'). These techniques can apparently brick your phone, so I avoided them. I might be wrong on some of the details here, so let me know!
4) I instead obtained the latest baseband by simply letting the LG update software (in my case from LG.ca) update my phone to Android 2.3. I noticed that I now had baseband v20. My mobile data worked!
5) I then re-rooted the phone, using SuperOneClick.
6) Installed the latest CM7 nightly. Mobile data no longer worked
6.5) I should mention, I tried other ROM/Kernel combinations and ended up having crashes and hangs on boot - thankfully I could use 'adb reboot recovery' to get back to Clockwork Recovery, when even holding various keys on reboot to do this didn't work).
7) Installed the wonderful ta-gb 1.1 kernel (thanks to all of the devs who worked on this and others like it).
8) And lastly (and possibly most importantly) I came across this:
https://github.com/CyanogenMod/andr...gingerbread/prebuilt/common/etc/apns-conf.xml
It's a list of APN information, which corresponds to different carriers, and appears to be necessary for mobile data connections. My carrier (Koodo) was not listed here, and therefore appears to not be included in even the latest Cyanogenmod 7 (as of Feb 2012).
9) This led me to find this: http://code.google.com/p/cyanogenmod/wiki/APNlist
Which happened to include the APN information for my carrier that I needed to put in, under Mobile Networks > Access Point Names.
Inputting that information made my 3g connection start up instantly. I was able to check that things looked good by typing *#*#4636#*#* in the dialer, and looking under Phone Information.
Maybe you're a veteran CM7 user, and think this is obvious newb stuff, but I want to leave this thread here for any other users who were stuck as long as I was.
If you fixed this issue with a different method, please share what you did here. If you're a ROM/Kernel dev with more insight on anything that I covered, please comment.
Cheers.
Click to expand...
Click to collapse
You should be able to get all your apn information from your carrier provider even if cyanogenmod doesnt have it.
Apn is nothing to do with being a veteran cm user or that, you used to always have to enter that kind of stuff in the old phones when you used g and 3g, in my case my carrier would sms me the settigs automatically, such as it still does for my nokia e63
deniso177 said:
You should be able to get all your apn information from your carrier provider even if cyanogenmod doesnt have it.
Apn is nothing to do with being a veteran cm user or that, you used to always have to enter that kind of stuff in the old phones when you used g and 3g, in my case my carrier would sms me the settigs automatically, such as it still does for my nokia e63
Click to expand...
Click to collapse
Good to know!
I have installed the nightlyfoure v3.8 and I am not getting 3g.I am getting edge connection. When I activate 3g it shows I have only gprs. I live in a place where 3g is available and I have v20g baseband.
Can you also tell us the procedure to edit/overwrite the original apns-config.xml if you did so? Thank you dude
geoemm said:
I have installed the nightlyfoure v3.8 and I am not getting 3g.I am getting edge connection. When I activate 3g it shows I have only gprs. I live in a place where 3g is available and I have v20g baseband.
Click to expand...
Click to collapse
Is your carrier listed in either of the links I posted about in step 8 or 9?
TheBlackHawkJr said:
Can you also tell us the procedure to edit/overwrite the original apns-config.xml if you did so? Thank you dude
Click to expand...
Click to collapse
I didn't edit 'apns-conf.xml', but I did find my carrier information in the link I posted in step 9) and typed it in manually into Access Point Names.
I suppose you could edit the apns-conf.xml file either in the source code, and compile CM7 yourself (time consuming). Or you could use the adb program that comes with the Android developer kit, and shell into the rooted phone (to see it, do: adb shell; cd /etc; ls). You could then probably edit it in place (might be risky), or pull the file, edit it, and then push it back with various adb commands that you can google
The code.google.com link I posted above might be the best way to request your APN details get added to the file in the next CM7 release.
bambu85 said:
I didn't edit 'apns-conf.xml', but I did find my carrier information in the link I posted in step 9) and typed it in manually into Access Point Names.
I suppose you could edit the apns-conf.xml file either in the source code, and compile CM7 yourself (time consuming). Or you could use the adb program that comes with the Android developer kit, and shell into the rooted phone (to see it, do: adb shell; cd /etc; ls). You could then probably edit it in place (might be risky), or pull the file, edit it, and then push it back with various adb commands that you can google
The code.google.com link I posted above might be the best way to request your APN details get added to the file in the next CM7 release.
Click to expand...
Click to collapse
Perfect, thanks but wait wait wait! You also faced the "not able to save APNs" problem? Also, I've just found out that my carrier (Vodafone IT) is listed among other carriers in APNlist you've linked... what's the deal?
(please be patient with me dude, I might seem really dumb but... I'm learning as I go )
My provider's APN is already added.
But sometimes, it fails to connect to DATA let it be 2G/3G.
Reboot solves it....
TheBlackHawkJr said:
Perfect, thanks but wait wait wait! You also faced the "not able to save APNs" problem? Also, I've just found out that my carrier (Vodafone IT) is listed among other carriers in APNlist you've linked... what's the deal?
(please be patient with me dude, I might seem really dumb but... I'm learning as I go )
Click to expand...
Click to collapse
Same issue.. pushed the updated apn-conf.xml to /etc but in my settings where the apns should show up do not. I also can not save the apn when i manually input it. (tmobile)
TheBlackHawkJr said:
Perfect, thanks but wait wait wait! You also faced the "not able to save APNs" problem?
Click to expand...
Click to collapse
I did not encounter this problem. Does anyone else have any input on this issue?
Thank you bambu85 I was stuck in the same situation for the longest time. I am using oxygen mod and your post helped me greatly. Data is now working! Sure the information might already be there but for us koodoers it's not so easy to decipher. Thanks
bambu85 said:
I did not encounter this problem. Does anyone else have any input on this issue?
Click to expand...
Click to collapse
Plus one when putting in the apn manually and press save it does not save it I only had this problem with new baseband ROMs
Sent from my HTC sensation 4g using Tapatalk
HI All -
I've posted in the Help/QA forum and didn't get any responses so I thought I might be able to reach a wider audience in this forum. I have the G900T and NFC is only half working and I believe I somehow manage to break it, but now I'm trying to see if there is any way to fix it. The issue is that Tap and Pay works, but Android Beam and any app that reads anything that emits NFC signals such as NFC tags, my yubikey-neo and an app which can read passports no longer work.
I initially noticed the issue on my phone and thought it was hardware related and was granted a warranty replacement by T-Mobile. Once I received the replacement phone I went through my usual setup.
1. Rooted via the NE6 boot image and towelroot method to gain root and then flashed the NK2 boot image back.
NFC worked as expected after rooting.
2. I used PC Odin and flashed twrp which tripped knox which I didn't care about since I don't use it, although clearly it voids the samsung warranty.
NFC continued to function correctly.
3. I backed up my rooted installation and decided to flash the latest CM12 KLTE nightly and play around for a few minutes. I then restored my original rooted TW install.
This is the point where NFC began to no longer function as expected. As mentioned Tap and Pay works fine, but I can't read anything emitting NFC signals. I also can't use Android Beam or S-Beam.
I have tried the following :
I used PC Odin to flash the original stock NK2 image and the issue persisted.
Afer backing up the /efs partition just in case it was somehow related ( no clear reason led me to believe it was ) I used PC Odin option to clear EFS and also used NAND Erase and flashed the stock firmware again and performed a factory reset. The issue still remains.
While using adb logcat and looking for nfc strings while I toggled it off and on I found that it appears that there is some issue with the NFC/Bluetooth radio handoff. I'm not entirely sure if it's a red herring or not. Just a message in the logs indicating there was some form of issue, but it only showed up once after a stock rom flash and rebooting the device and performing the same steps didn't emit the same message again.
I started looking at the init.rc and ueventd.rc files and noticed references to /dev/sec-nfc and /dev/bmc2079x - neither of which exist in /dev on my device. I didn't check when I first got the phone as I was under the false assumption at the time that it was hardware related. The /data/nfc directory and directories related to the libnxp-nfc and bmc nfc appear correctly and to my knowledge contain the correct firmware images and files required for the hardware to work.
I posted this same question on the galaxys5 subreddit over on reddit.com and there is one other user who has a 900F who has experienced the exact same issue. So it seems like it's not a oneoff issue. I'm just hoping to figure out what the issue is and if it can be fixed.
Any ideas on things I can look at beyond what I have already would be awesome.
Also, if anyone has time and can see if /dev/sec-nfc and /dev/bmc2079x device entries exist on their S5 that would be super helpful. If they do exist, then perhaps it points to the hardware simply not being initialized fully, that's simply a guess on my part. If you do happen to have those 2 dev files can you attach them so I can test them out? I would be forever grateful.
Cheers.
Per XDA rules no double posts. Also all questions and request for assistance do belong in the Q&A section not in General.
Edfunkycold
Have a great day!
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?