Hello!
I have problem with 4.4.4 roms. Phone works normally, then suddenly normal calls do not work. I can answer and decline the call but no audio comes trough and also the receiving end can not hear me.
After reboot everything works again, then passes hour maybe two and then dead again.
Works ok, with stock rom.
Any recommendations, how to fix this problem?
(also offtopic problem, screen does not always turn on when pressing the lock button, i have to smash couple of times. I found that you had to turn up the lowest cpu clock speed - did that- did not help)
kukke5 said:
Hello!
I have problem with 4.4.4 roms. Phone works normally, then suddenly normal calls do not work. I can answer and decline the call but no audio comes trough and also the receiving end can not hear me.
After reboot everything works again, then passes hour maybe two and then dead again.
Works ok, with stock rom.
Any recommendations, how to fix this problem?
(also offtopic problem, screen does not always turn on when pressing the lock button, i have to smash couple of times. I found that you had to turn up the lowest cpu clock speed - did that- did not help)
Click to expand...
Click to collapse
On your wake lock issue, its the governor you need to adjust. I think its ondemand, but try your options. Your phone issue.....first many may ask is, did you flash clean?
You can always try flashing ROM twice. Because you can get 2 different reactions to 2 separate flashes, I always flash ROM twice, then gapps and so forth.
Sent from my Nexus 6 using XDA Free mobile app
Yes, I always do a clean flash. I will try to flash it twice, lets see what happens.
Thanks for the suggestion!
Related
i have galaxy s2 . i have installes wanamlite ics stock rom...everything except the phone works gr8. whenever i try to make a call my phone freezes or reboots after 10-20 seconds in to the call. more over my proximity sensor is acting crazy.
when i put the phone near my face during a call the phone screen shuts but does not turn on when i movemy phone away from my face...please help
mlovesu said:
i have galaxy s2 . i have installes wanamlite ics stock rom...everything except the phone works gr8. whenever i try to make a call my phone freezes or reboots after 10-20 seconds in to the call. more over my proximity sensor is acting crazy.
when i put the phone near my face during a call the phone screen shuts but does not turn on when i movemy phone away from my face...please help
Click to expand...
Click to collapse
hi, try to redownload and reinstall the rom,
bad downloads sometimes results to a corrupted file,
and install the rom after full wipe, but backup first...
thanks for your advice...but i have tries every thing you mentioned above...
mlovesu said:
i have galaxy s2 . i have installes wanamlite ics stock rom...everything except the phone works gr8. whenever i try to make a call my phone freezes or reboots after 10-20 seconds in to the call. more over my proximity sensor is acting crazy.
when i put the phone near my face during a call the phone screen shuts but does not turn on when i movemy phone away from my face...please help
Click to expand...
Click to collapse
It doesn't sound that great to me. If a reflash didn't work, why don't you try an different rom. Just to rule out a rom error.
mlovesu said:
thanks for your advice...but i have tries every thing you mentioned above...
Click to expand...
Click to collapse
Did you do a full wipe when you flashed it?
Sent from my GT-I9100 using xda premium
kilometers4 said:
Did you do a full wipe when you flashed it?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I have the same problem as mlovesu...I have done a complete wipe everytime i flashed a new ROM..also tried different kernels(siyah 3.2.2 tried latest)...
now have gone back to stock firmware XXLPH and rooted again..the dialer works for now but the proximity sensor still doesnt along with the screen brightness sensor..
any help pls guys...have been doin everything possible for a week now...i dont think its a hardware error as the proximity sensor does light up(the infrared light) but not on calls...have tried the samsung tests for sensor..but that seems to not show any change in values if u move ur hand closer..
thanks
freeze omg
stupidflanders1 said:
I have the same problem as mlovesu...I have done a complete wipe everytime i flashed a new ROM..also tried different kernels(siyah 3.2.2 tried latest)...
now have gone back to stock firmware XXLPH and rooted again..the dialer works for now but the proximity sensor still doesnt along with the screen brightness sensor..
any help pls guys...have been doin everything possible for a week now...i dont think its a hardware error as the proximity sensor does light up(the infrared light) but not on calls...have tried the samsung tests for sensor..but that seems to not show any change in values if u move ur hand closer..
thanks
Click to expand...
Click to collapse
Same problem here. .flashed several times with difrerent roms all workes but when i.make i call phone freezes and restarts
.any solutions pls help!!!!
miroslavpena said:
Same problem here. .flashed several times with difrerent roms all workes but when i.make i call phone freezes and restarts
.any solutions pls help!!!!
Click to expand...
Click to collapse
I have no problem for calling action.
Enter in clorkworkmod and try fix permission
I have a problem in my U.
Everytime someone calls me, first the led lights up, then it vibrates about 2-3 times in the middle starts ringing and only after all that the screen turns on so i can answer or reject the call.
After i answer a call sometimes it takes 3-5 sec to hear sound from the other phone, but the caller says he can hear me the whole time.
When receiving SMS, first the led lights up, then after a while it vibrates and after that it rings, but sometimes it doesn't ring.
Another thing, it lags to much to open the contacts, phone and messages app.
My wifes Tipo dual, opens almost instantly the phone app after i touch it.
I'm using The ROM, etc that are stated in my signature.
Please help!! Already tried different kernels, etc. :crying:
It can be something in the mods or it can be the rom itself.
Didi you get these bugs before the mods?
The stock rom sucks, mine did this as well, made the phone unusable.
mirost1 said:
It can be something in the mods or it can be the rom itself.
Didi you get these bugs before the mods?
Click to expand...
Click to collapse
Already had the excessive lag opening the apps with a fresh stock ROM. Honestly i put and did so many things that i don't know now.
But i installed the Sliding XU 3.3 kernel and it's working almost fine now, only has the original lags opening the apps of the stock ROM.
theronkinator said:
The stock rom sucks, mine did this as well, made the phone unusable.
Click to expand...
Click to collapse
So wich ROM do you use
Hello!
I recently switched to the m4 from my trusty LG OG, an it is perfect except for one thing... it doesn't ring.
I have tried all Sony-solutions, including PC software repair, etc... but no joy. My wife also has an M4 and has the same problem.
It is worked-around by using a 3rd party lockscreen (I use Hi-Locker), which is awesome.. but not ideal due to security problems, most notably Android Pay.
My question?
Can I replace the lockscreen at the ROM level? Can I replace the basic function with maybe a lockscreen from the Z5?
Unless someone knows how to fix this
I have never compiled my own rom, but I have a reasonable level of tech-savvy. I can flash ROMS and do work in Linux.
I have rooted and unlocked my bootloader, and I am using Stock Sony ROM
I have the latest firmware
Kernel 3.10.49
build 26.1.A.2.99
I have NOT tried using an old firmware- or an alternate ROM. I probably will, but my wife doesn't love the idea for her. Thus, I would like to work out a precision fix.
My thoughts?
Idea 1. find where the stock lockscreen/security module lives.. and try and replace with something from a different phone.
Possible?
Thank you for reading.. I know some other people have these problems, as I read them in threads here.. but I didn't find much in the way of fixing.
just for reference- THIS is the problem.
just for reference- THIS is the problem.
Mustang243 said:
My phone doesn't ring when it 's locked. If phone is unlocked ringtone rings and vibrates. When it's locked no sound or vibrate. Whatsapp messages vibrate but they have no notification sound. I have checked all the settings, volume is up. Last resort is factory reset but i'm not there yet. I don't wanna lose all my settings.
E: Okay I used Sony PC Companion and used the Fix phone/tablet -thing and it downloaded the firmware and installed it so I think it reset my phone. Still my phone doesn't ring if its locked. If I press the power button when someone is calling to me, I can see the lockscreen notification on the screen but it doesn't ring or vibrate. FFS. Any ideas guys?
E2: I guess I find a solutions. Or a temporary solution. I noticed that if I disabled the screen lock, my phone would ring and vibrate normally. So I decided to try and download "Next" lockscreen app. Guess what. When I use it, my phone works perfectly. I don't know why it stopped ringing because there wasn't any new updates from Sony but it's clearly problem in Sony's software.
Click to expand...
Click to collapse
Mustang243 said:
I still have the "silent phone" issue with this update. I have to use third party lock screen app. If I use Sony's lock pattern or pin code and use my gf's phone to call my phone: screen doesn't wake, no ringtone can be heard and no vibration. When I press power-button I can see that someone's trying to call me. Anyone else experiencing this problem? I hope you understand what I tried to say, the issue is kinda hard to explain.
Click to expand...
Click to collapse
Yeah this is a huge problem and we're not the only ones suffering from it. Now I use CM Locker because Next drained my battery. I also noticed that my phone works fine if I boot on safe-mode. Still haven't figured it out which app causes the problem. Gotta wait for the 6.0 update and hope that fixes things.
Same issue with out-of-the box...
Well, have M4 'out of the box' - meaning - no custom software installed, no customized ROM, no custom lock-screen... and well - to make the ring work back I have to restart phone every few days (as soon as realize that it's not working) - oh Sony, what should I say ....
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.
Hey all,
A few days ago, I noticed my phone was only vibrating during incoming calls. I checked the Ringtone section in the sound settings and found that the selected "Tone" was "Silent."
I've tried changing the ringtone to various different sounds, but it continues to revert back to silent. The ringer, itself, ISN'T on silent. It's just the ringtone that seems to get changed somehow.
Anyone else encounter this issue and know how to get it resolved?
Thanks in advance for your help.
Are you trying to set it to one of the built-in ringtones, or a custom one you added? If it's a custom one, is it on the SD card? I've had problems in the past with phones "losing" ringtones that were installed on the SD card, rather than internal memory.
meyerweb said:
Are you trying to set it to one of the built-in ringtones, or a custom one you added? If it's a custom one, is it on the SD card? I've had problems in the past with phones "losing" ringtones that were installed on the SD card, rather than internal memory.
Click to expand...
Click to collapse
I thought you might be on to something there, so I made sure that all of my ringtones and notifications were copied to internal storage and deleted all sounds from my SD card.
I rebooted, setup my sounds again, and had my wife call me a few times over a period of about 2 hours. Rang every time.
Then, just now, I noticed I had 3 missed calls from clients. NOT good. Checked the ringtone settings and it was back to "Silent" again! Infuriating.
It's not the location of the file. And, now that I think about it, if it HAD been the issue, I would've been experiencing loss of notification tones in all of my other apps too.
This problem has seemingly arisen out of nowhere. The ringer worked perfectly fine during the first few weeks I've had the S9+. It just started doing this to me a couple of days ago. I'd really rather not go through the annoyance of a hard reset...
Damn it, this is getting REALLY annoying
HaaaaLP MEEEEEH!
I'm having the same issue on my Samsung Note 8. Began happening after the device received the Android 8.0 update. I've tried everything and it seems to happen completely randomly. HELP!
Mine is working fine. I have mine on the internal storage in the Ringtones folder /0/Ringtones/ it's an mp3 less than 2MB in size. Not that I know any of that makes any difference.
Mailbrat said:
I'm having the same issue on my Samsung Note 8. Began happening after the device received the Android 8.0 update. I've tried everything and it seems to happen completely randomly. HELP!
Click to expand...
Click to collapse
I hated doing it, but I just performed a factory reset. Been setting up my phone again for hours and I'm not yet done.
So far, it's ringing, but I'm going to be really disappointed if it reverts to silent again. I'll keep you posted.
yuppicide said:
Mine is working fine. I have mine on the internal storage in the Ringtones folder /0/Ringtones/ it's an mp3 less than 2MB in size. Not that I know any of that makes any difference.
Click to expand...
Click to collapse
Tried that too. It worked for a while then randomly went to silent again. It will stay on the ringtone I set for sometimes as long as a day, but eventually it reverts to silent.
Mailbrat said:
Tried that too. It worked for a while then randomly went to silent again. It will stay on the ringtone I set for sometimes as long as a day, but eventually it reverts to silent.
Click to expand...
Click to collapse
So far so good. I've had 7 incoming calls and the ringtone I've selected has stayed in place. For me, before the reset, it would revert to "Silent" after the 2nd call. Fingers crossed.
Same exact thing is happening to me on my HTC U11.
It started happening right away after a full wipe and install of Bad Boyz ROM (Android 8.0). No one else in that ROM thread seems affected.
I have tried just picking a built in ring tone too, and that will also revert. Sometimes it happens within a few minutes, sometimes it takes hours.
ccs86 said:
Same exact thing is happening to me on my HTC U11.
It started happening right away after a full wipe and install of Bad Boyz ROM (Android 8.0). No one else in that ROM thread seems affected.
I have tried just picking a built in ring tone too, and that will also revert. Sometimes it happens within a few minutes, sometimes it takes hours.
Click to expand...
Click to collapse
That is exactly what happens to me. Custom ringtones make no difference. I've assigned rintones to all my important contacts and those ring through no matter if on silent mode or not. Like you, sometimes it stays put for hours and other times it changes back after a few minutes. Rebooting seems to help it last longer, but I find myself checking my phone all the time to be sure it hasn't gone to silent ringtone. Frustrating!
Hard to blame Samsung if you're not running their software.
meyerweb said:
Hard to blame Samsung if you're not running their software.
Click to expand...
Click to collapse
I don't believe anyone is *blaming* Samsung although the thread did begin in a Samsung forum. We're just trying to find out why our phones are behaving badly and hoping to find a way to fix a really frustrating problem. Do you have a suggestion on where we might look?
Well, I think it's safe to say that the hard reset did the trick. Ringtone is sticking now. Hooray.
pieces of cake said:
Well, I think it's safe to say that the hard reset did the trick. Ringtone is sticking now. Hooray.
Click to expand...
Click to collapse
Glad to hear this seems to be working, but not glad that the answer is factory reset. I really, really don't want to go through that. I think I'll suffer along a bit longer and see if someone comes up with a work around or perhaps an app that can lock the ringtone. One can hope.
Mailbrat said:
Glad to hear this seems to be working, but not glad that the answer is factory reset. I really, really don't want to go through that. I think I'll suffer along a bit longer and see if someone comes up with a work around or perhaps an app that can lock the ringtone. One can hope.
Click to expand...
Click to collapse
Yeah, it was a bit of a pain in the a$$, but worth it. Reset definitely did the trick.
I have the same problem on my S9+ since the last update. the basic sound settings revert to Silent as do custom settings. Has anyone contacted Samsung to dee what their excuse is?
Hi Folks, I've been having the same issue since 3 weeks ago. Called Samsung and was told to delete my customized settings. That DID NOT WORK. Finally a Fix. I wipe my cache partition and it worked.
Turn off your phone. Turn it on while holding Power, Bixby, and Vol. Up buttons until you get the menu. Use volume down to get to Wipe Cache Partition (NOT wipe Personal data/factory reset.) Press PWR to accept.
This does not erase anything and it's worked problem free for about a week. I read in other forums that changing the SIM has fixed this issue, but changing your SIM will clear the Cache as well.
Hope this works for you.
The solution is to quickly remove the old ringtone and replace the new ringtone for the phone