4.4.4 KitKat ROMS - Dialer freezes on i9505 International LTE - Galaxy S 4 Q&A, Help & Troubleshooting

Hi All,
I'm wondering if anyone else has encountered this problem?
Basically, I was having wifi issues connecting to an enterprise WLAN with PEAP/MSCHAPV2, so I (stupidly) upgraded to the OTA 4.4.2 ROM, which would have been fine if it didn't kill battery life and randomly restart. I wasn't on this version long enough to know if it had the same issue that I will describe below.
So I threw caution and my warranty to the wind and went with the 4.4.4 Pacman ROM, which was great, but whenever I had a phone call, the phone screen freezes and won't wake up to allow me to hang up a call. The same thing would occur if I called someone and had to use their automated system - I'd put the screen on loudspeaker, open up the dialpad, and when I want to hit the numbers - nothing. Locked up. Can't hang up either.
I had the same issue on the 4.4.4 Cyanhacker ROM, so I believe that it is fully related to some sort of incompatibility between KitKat and the i9505, and not the ROMs themselves.
At this point I was successful in switching to the Darthstalker 4.3 ROM, which is running beautifully and I'm really liking it so far. It's also nice having the old phone and contacts apps back, because I really hated the Kitkat one anyway...

Related

[Q] Phone sensors unresponsive for a few secs when receiving call.

Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!
I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app

Skype & Kitkat issue

Everything was perfect when i was on Android 4.3, any skype calls working, video/audio doesn't matter.
But when i updated my wife's phone to kitkat, some skype calls making phone reboot(black screen, then its loading as usual).
It happens not always. And i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
When she talks to anyone on 7&8 Windows - everything is perfect.
I have tried all custom roms, original, rooted\not rooted, anything.
I gonna write this issue to Skype too.
Skype support asked that Skype not supporting KitKat yet.
Btw it only happens on Nexus 4, when i'm on my phone (XT910) on KitKat, it works and not hangs.
In my case occurs the same...I believe is maybe kit Kat by itself and usually happens when I leave a call in the background while I use another application. Unfortunately I haven't found any solution for that.
i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
Click to expand...
Click to collapse
Not really. The problem is a bit more serious: all ROMs (stock and custom) based on 4.3 or 4.4 are affected by this overly annoying camera bug. I obviously hope you're not, but if you end up as unlucky as I did, your camera and LED flash will soon become totally unusable (on all applications), fixable only by reverting to 4.2 or updating to L (I did and it's totally worth it)
Good luck :good:
Also another issue with Skype and N4 is that whrn listening to music and an image is being sent / received in the Skype chat window, fetching that image from the gallery/disk causes the audio system to crash. It's really annoying. Probably it's the same issue as the well-known audio stutters on changing connectivity and high cpu load.
Im using the Verizon G2 and running 4.4 2...xdabebb rom..i use skype a lot for business calls and havent come across this issue at all. On unrooted stock as well as custom. Ive also faced no issues on an S4 i9500...so it might not really be a kit kat issue but a nexus 4 specific...or an aosp based rom specific issue
Sent from my VS980 4G using Tapatalk
I have another kind of issue with my xiaomi Mi2 with MIUI Rom on kitkat 4.4.4. I have systematically a black screen when the communication is established on Skype also using test sound server. The sound is working but I can't do nothing with the phone until the end of communication decided by my correspondant.. Very annoying . I have post the question to Skype 5 days ago but no answer. Skype was working properly on my phone on miuiv5 android 4.1.2
Envoyé depuis mon Mi2 kitkat 4.4.4 Miui6
I'm having the exact same problem ... I was talking on Skype video call and the phone screen went black and I couldn't hear the other party.. I don't if they were able to hear me or not. I had to hold the power button and reboot my phone manually. I don't know what the problem is but its very annoying and it happened three times in a row. I have used multiple ROMs and it was happening on all of them and they were all 4.4.4. I don't flash kernels, I just use the kernels that come with ROM because they have obviously been tested and have been found compatible with the rom. So I know its not because of kernels. Currently I'm on Slimkat latest weekly and was thinking about going back to stock but someone said its also happening on stock ROM. I'm going to try CM11 and see if it happens there as well. Will report back soon. Hopefully it's just a 4.4.4 issue and not a phone issue.
Sent from my Nexus 4 using XDA Free mobile app

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

Motherboard problems/Lollipop only

Hello guys,
I'm currently having issues with my phone since I've dropped it in a pond outside, and I guess it's the motherboard that is affected.
I cannot charge my phone (I use a desk changer + another battery), the flash is working only for half a second while taking pictures so I need to manually set the ISO, but those problems are not so important.
The reason I write here is because everytime I flash an official or any other touchwiz based LOLLIPOP OS, the phone is getting through a "plug/unplug". I don't know how to explain, it simply says that it's charging, then after a few seconds it says it's not charging, and so on, WITHOUT having it plugged.
Is there any way to simply delete these instructions from the OS? The phone is working flawlessly otherwise.
These things only happen when using official or touchwiz based LP, the KK ones are working as they should, and it's a bit weird because only with LP I have these problems. Also, if I flash some CM based OS, it's working flawlessly.
Please help.
Thanks in advance.

[Q] Mic not activating on call?

Hi guys to cut a long story short .....
Updated to lolipop from kit kat this month.
Two issues so far:
When making a call no one can hear me when someone rings me they can hear me?
The weather widget disapears but its still there as i wiz touch it it goes into the app. Have to remove app icon then stick it back onto the screen before it shows up again.
Things I'am doing:
Hard reset using kies to back up
Freed up mem and got rid of some apps
Two new apps before this became an issue nova 4 and mortal combat (kids doing)
Kit kat worked perfectly unitl now.
Hope someone can help?
N910UXXU1B0E5
Are you using stock rom or rooted one?
Stock rom problem solved the hard reset seems to have brought new life back to the device. It's on test I'll report back.

Categories

Resources