Related
Hey every body.
I'm having a nightmare with my s3.
Back at the start of April I changed my from from stock to cyanogen mod 9.1.
It was rooted prior to this and never gave any issues.
Cyanogen 9.1 worked perfect until today. I'm not sure if its an issue with the ROM or the phone
Symptoms are if I call somebody there us no dial tone but I can tell when they answer because the timer starts timing the call but I hear nothing.
They can hear me alright but that's it.
I tried flashing back my stock from but the phone won't recognize the next SD card.
Can anyone help please. I need this phone working
Thanks
Looks like the issue sorted itself out on its own accord.
Can anyone shed some light on what to do if it does it again?
I have got the same issue. I don't know why is it happening, but I have the solution.
###
Turn ON the screen lock sound in the audio settings. Restart your S3. Thats it. Keep it on.
known issue
Where we find these issues?
Glebun said:
known issue
Click to expand...
Click to collapse
Care to elaborate
this is a known issue with AOSP ROMs.
Enable lockscreen sound in settings
qsmyle said:
Where we find these issues?
Click to expand...
Click to collapse
Search and read rom descriptions and threads is how you find them no other way .
jje
I am facing a strange problem that I don't get call waiting alert while using blue tooth. I can clearly hear notification otherwise but it goes away on bluetooth device. Tried on two different bluetooth units. This problem occurs on 4.2.2 Rom's .All the rest of sounds like music and sms notifications are fine There is no such issue on 4.1.2. Please help
sundeepnanda said:
I am facing a strange problem that I don't get call waiting alert while using blue tooth. I can clearly hear notification otherwise but it goes away on bluetooth device. Tried on two different bluetooth units. This problem occurs on 4.2.2 Rom's .All the rest of sounds like music and sms notifications are fine There is no such issue on 4.1.2. Please help
Click to expand...
Click to collapse
Which specific 4.4.2 rom are you using?
I'm using omni-4.4.2-20131219-i9100-NIGHTLY and I don't have that issue.
rhelering said:
Which specific 4.4.2 rom are you using?
I'm using omni-4.4.2-20131219-i9100-NIGHTLY and I don't have that issue.
Click to expand...
Click to collapse
I have tried various ROMs , all have same issue. Today tried senitenilrom which is android 4.3 and again the
same issue. Though i have not tried the ROM you have suggested . will try that too. Thanks for reply
sundeepnanda said:
I have tried various ROMs , all have same issue. Today tried senitenilrom which is android 4.3 and again the
same issue. Though i have not tried the ROM you have suggested . will try that too. Thanks for reply
Click to expand...
Click to collapse
I'm very happy with this rom: http://forum.xda-developers.com/showthread.php?t=2562055
In there you have the instructions about how to install it.
Hope that helps!
rhelering said:
I'm very happy with this rom: http://forum.xda-developers.com/showthread.php?t=2562055
In there you have the instructions about how to install it.
Hope that helps![/Q]
I tried this ROM. Its really nice and I want to have it on my device but my problem still remains there. I m only able to use till android 4.1.2 versions. Anything beyond that causes this Bluetooth call waiting issue. I m really missing upgrades . it's strange not to get only call waiting notification over Bluetooth. All the rest of the sounds are OK.
Click to expand...
Click to collapse
I am having the same problem. Tried many ROMs (Cyanogenmod, Jellybam, Omnirom, Revolt,...) but anything above 4.1.2 leads to this strange issue. At first i thought it was the Bluetooth device thats why I tried several of those as well (Plantronics, LG, Samsung, Bose,...) and its the same every time.
I really can't get behind this and never found anypne with a simillar issue. I have pretty much resigned myself to always having 4.1.2 until i've seen this thread. Now i have hope, please don't crush it.
Is there anybody out there who has any idea how to solve this?
Anything? I hate to be stuck on JB.
since last update 1.41 everything seems ok apart from when I am disconnected from internet via wifi or data themer crashes,as soon as I reconnect it is fine,anyone else have a similar problem ?
this only applies to any themes made in 1.41,any themes that are made in previous version do not require wifi/data access,can't believe just me having this issue.Have gone down the remove install but issue still persists.
alldroid said:
this only applies to any themes made in 1.41,any themes that are made in previous version do not require wifi/data access,can't believe just me having this issue.Have gone down the remove install but issue still persists.
Click to expand...
Click to collapse
Does it do it with version 1.42 as well?
not tried 1.42 yet will update when I get in from work and let you know
alldroid said:
not tried 1.42 yet will update when I get in from work and let you know
Click to expand...
Click to collapse
Did you try to Re-download your theme ? or try another ?
Just updated and problem seems to have vanished now,thanks to devs for quick solve
Problem not resolved yet.
I updated from 1.41 to 1.42 yesterday but the problem still persists.
Whenever i get disconnected from wifi or mobile data, i get to see an irritating pop-up every 1 minute saying: "The app found information about previous cashed. would you like to send this data to the developer?"
I have send it numerous times but it is still there. Its too much irritating.
I also tried uninstalling the themer app and deleting the my colorscreen folder, then restarted the phone and reinstalled the themer. But the problem is still there.
For additional information: This weird problem has started since addition of stupid "bollywood" category
yeah I just made a post regarding this as I now have the same issue m8,sent bloody loads of reports,and you are correct removing themer completely and reinstall does not work
the only way I have managed to get it working properly is to do a factory reset of the phone.Everything else including numerous deletes and reinstall does not work,I tried this as a last resort.Can someone let us know why themer seems to be holding onto the crash data,which as posted above is so annoying,and I or anyone else shouldn't have to factory reset to correct,Can this issue be looked into please by developers,as it can't just be the two of us having this issue.
Imranhakro said:
Problem not resolved yet.
I updated from 1.41 to 1.42 yesterday but the problem still persists.
Whenever i get disconnected from wifi or mobile data, i get to see an irritating pop-up every 1 minute saying: "The app found information about previous cashed. would you like to send this data to the developer?"
I have send it numerous times but it is still there. Its too much irritating.
I also tried uninstalling the themer app and deleting the my colorscreen folder, then restarted the phone and reinstalled the themer. But the problem is still there.
For additional information: This weird problem has started since addition of stupid "bollywood" category
Click to expand...
Click to collapse
alldroid said:
yeah I just made a post regarding this as I now have the same issue m8,sent bloody loads of reports,and you are correct removing themer completely and reinstall does not work
Click to expand...
Click to collapse
So for both of you, the problem only occurs when you get disconnected from WiFi/mobile data? Does this include going into Airplane mode?
We want to see if we can replicate this on our end.
ThemerSupport said:
So for both of you, the problem only occurs when you get disconnected from WiFi/mobile data? Does this include going into Airplane mode?
We want to see if we can replicate this on our end.
Click to expand...
Click to collapse
Yes, this includes the Airplane mode as well. (Obviously)
Yep as above and guess what factory reset does not solve it same problem this morning even though no errors in themer after reset,and agan plane mode is the same when not connected
Imranhakro said:
Yes, this includes the Airplane mode as well. (Obviously)
Click to expand...
Click to collapse
We're just trying to replicate the problem. There hasn't been anyone else with the same issue, therefore we need as much info as possible. I put my Nexus 5 on Airplane mode every night and haven't experienced the problem, hence asking the question.
ThemerSupport said:
We're just trying to replicate the problem. There hasn't been anyone else with the same issue, therefore we need as much info as possible. I put my Nexus 5 on Airplane mode every night and haven't experienced the problem, hence asking the question.
Click to expand...
Click to collapse
I assume there must be numerous people out there who might be facing the same issue, may be they are following this thread and just waiting for us to reach the resolution of the problem.
I agree with you that the more information will help you to diagnose the problem in better way, and I appreciate your support.
I own stock Samsung Galaxy Note 2 with Android 4.3. I''ll appreciate if "alldroid" and any other who is having the same issue, share their device info here.
Already did above somewhere m8 galaxy s4 running stock kitkat,it has to be themer related other wise the factory reset would have solved it.The only other solution is that the theme itself held on to the errors prior to remove and delete,but even if it did it is a themer problem imo as once an error log is sent it should be removed frm themers memory
Imranhakro said:
I assume there must be numerous people out there who might be facing the same issue, may be they are following this thread and just waiting for us to reach the resolution of the problem.
I agree with you that the more information will help you to diagnose the problem in better way, and I appreciate your support.
I own stock Samsung Galaxy Note 2 with Android 4.3. I''ll appreciate if "alldroid" and any other who is having the same issue, share their device info here.
Click to expand...
Click to collapse
alldroid said:
Already did above somewhere m8 galaxy s4 running stock kitkat,it has to be themer related other wise the factory reset would have solved it.The only other solution is that the theme itself held on to the errors prior to remove and delete,but even if it did it is a themer problem imo as once an error log is sent it should be removed frm themers memory
Click to expand...
Click to collapse
We'll keep searching to see if more people are reporting this problem. There is a huge update coming up, I'll see if the update is fixing this issue.
still have the issue and I refuse to believe only two of us have this issue,either that or we are the two most unluckiest themer app users in the world
latest update and..........problem solved no longer asks to send crash data when no net connection
No guys, you are not alone, I'm having this issue too anytime I disconnect my device from a wifi or mobile data, even during poor connection even though with the new update this should be fixed. I don't know if this happens in Airplane mode, never used that mode but I'll try and give you feedback.
Inviato dal mio macina caffè usando Tapatalk
see I knew we weren't alone,as above I have changed messed about with,used airplane mode and not had the error since the latest update here.Let us know if the update solves your problem m8
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.
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.