Related
Ive installed the latest cyanogen mod rom and i have been using it for a while. There are a few bugs i have noticed through my use of the phone and they are kinda getting annoying.
First of all i have noticed randomly while i am listening to music the music app that came with cyanogen will freeze up and then it will start again but after it does that there is no sound. And when i force close the application, i use the controls on the side of the phone to change the volume and it will only change the media volume not the ringer volume. to fix this when it happens i have been having to restart the phone and go on from there.
Another bug i have been noticing is when i turn the phone to vibrate mode using the controls on the left of the phone when i recieve a text i do not get a notification. I would excpect that it would vibrate as well.
Another one is that when i am listening to music and i recieve a text it will turn off the sound similar to the first bug i talked about. It says it is still playing but there is no sound coming from it. To fix it i have been having to restart the phone.
To listen to my music with my earphones i have an adapter and some times when i am using that the phone will go into a reboot loop until i take out the adapter and then once the phone is back up plug the adapter back in.
These are all quite annoying and i would like to see if you guys have any input on the matter. Thank you
I don't think that any of these are platform bugs, but rather are cyanogen bugs. I suggest you post bug reports to cyanogen's bug tracker.
lbcoder said:
I don't think that any of these are platform bugs, but rather are cyanogen bugs. I suggest you post bug reports to cyanogen's bug tracker.
Click to expand...
Click to collapse
Well i thought about that as well but i looked at the rules for the bug tracker and i am currently in the process of making more accurate bug reports for the bug tracker. I came here to see if i could get any quick fixes or to ask if these are common things or i may just have to format my phone and reinstall cyanogen. So yeah i hope i can get some feedback from other users. I may just have to format as i said but i hope that there could be something else i could do. dont want to just go to all that trouble to not get it fixed.
edit: I looked further into the bug tracker for cyanogen and i dont have the required materials to make a report as i dont have a log of the issue. its just something that tends to happen.
Its happening alot today and well yeah its getting really bad, i dont think there is anything wrong with my phone. So i think i am just going to format and reinstall a new rom. idk if i will stay cyanogen or not. anyone have any recomendations for the rom i should install?
Super D is pretty awesome. It's an improvement on the Cyan roms. So you get Cyan plus some extras.
Could i get a link to the correct version i should use?
Yep here is the link for Super D
thank you installed it and i am no longer having any issues. Wonderful
Hi all im having to post here because i dont have permission to post in development thread.
I have been using cm9 for few days went from build 5 to 7 yesterday and i have an issue with both builds, after a while my sound just goes i cant hear phone calls youtube videos or games sounds. As far as i know all sound has gone even woth volumes turned right up. I have searched the forums and cant find anything on this issue, anybody else have it/know how to fix it. The only way i can get sound back is rebooting. Any helo much appreciated
GaVLaR123 said:
Hi all im having to post here because i dont have permission to post in development thread.
I have been using cm9 for few days went from build 5 to 7 yesterday and i have an issue with both builds, after a while my sound just goes i cant hear phone calls youtube videos or games sounds. As far as i know all sound has gone even woth volumes turned right up. I have searched the forums and cant find anything on this issue, anybody else have it/know how to fix it. The only way i can get sound back is rebooting. Any helo much appreciated
Click to expand...
Click to collapse
was it working fine on Sammy's ROM?
yes i have never had an issue until using cm9. i think the microphone stops working too. i think it maybe when i try using the spirit fm app would this make sense? im not going to try the app now and see if it happens again. i thought that app should work?
GaVLaR123 said:
yes i have never had an issue until using cm9. i think the microphone stops working too. i think it maybe when i try using the spirit fm app would this make sense? im not going to try the app now and see if it happens again. i thought that app should work?
Click to expand...
Click to collapse
Well, i think that's not a hardware issue to be worried about & don't mess with unknown and bugged up apps .
Why not try a re-flash (wipe cache & factory reset ) of BUILD8 ? If that doesn't also solve the issue then try Odin re-flash back to 2.2/2.3 and then again CM7.1 [with a Modem flash] to CM9 ?
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
I have been ROM-hopping for 3-4 months and I have tried many ROMs for my i8190.
I found some I really enjoyed, some did not work well for me.
Without meaning to "compare" the ROMs or find "the best ROM ever" I am just looking for some suggestions on ROMs that I can try.
My requirements are very simple:
-OTG support
-No clock freezing
-No battery drain
What ROMs would you suggest?
Please note, I have no intention of comparing the ROMs with one another, I am just looking for suggesstions in case there is something good that I have not tested yet.
Thanks!
Novafusion CM10.2
sent from Hell with my GT I9100
tobi-19777 said:
Novafusion CM10.2
Click to expand...
Click to collapse
Thank you for your time. This was the ROM I installed last and seems to be a good option.
I have been using it for almost a week, I really like the stability, looks like a solid ROM.
I only have one issue with it (all cyanogenmod ROMs basically).
Even though I have turned the backlight of the hardware buttons off, they keep lighting at random times, I have not found what is causing that or how to fix it, can you suggest something or do I just get used to it?
anpel said:
Thank you for your time. This was the ROM I installed last and seems to be a good option.
I have been using it for almost a week, I really like the stability, looks like a solid ROM.
I only have one issue with it (all cyanogenmod ROMs basically).
Even though I have turned the backlight of the hardware buttons off, they keep lighting at random times, I have not found what is causing that or how to fix it, can you suggest something or do I just get used to it?
Click to expand...
Click to collapse
Download this app, then open it, uncheck "activate bln" then go to system settings-buttons-backlight & uncheck illuminate buttons
mauam said:
Download this app, then open it, uncheck "activate bln" then go to system settings-buttons-backlight & uncheck illuminate buttons
Click to expand...
Click to collapse
I managed to break my phone's screen so I haven't been using it for the past couple of months but I'm back here to say this solution worked 100% for me, just in case anyone is reading. Thank you!
P.S. Sorry I had to remove the url to the app, but I'm a new user and I am not allowed to post external links, obviously even when quoting more experienced users.
This thread is for discussion of the Resurrection Remix build on the Exynos
The RR build is available for download here
After turning camera on for a few times this happens.
Also there's an icon for multiwindow in recently menu but it doesn't work and cannot be turned off, kind of bothers me.
Just wondering @dl12345 , so if we have any issues or we find a bug that related with RR but not lineage it won't get fixed, even if we provide logs? I'm kind of confused on how you phrased it when you said that you wouldn't deal with RR bugs but you would still update this after every lineage build release. Would the newer builds of RR that's based on the newer builds of lineage cause issues later on?
RetroSpect_17 said:
Just wondering @dl12345 , so if we have any issues or we find a bug that related with RR but not lineage it won't get fixed, even if we provide logs? I'm kind of confused on how you phrased it when you said that you wouldn't deal with RR bugs but you would still update this after every lineage build release. Would the newer builds of RR that's based on the newer builds of lineage cause issues later on?
Click to expand...
Click to collapse
I mean that if there is an RR specific bug then it won't get fixed until such times as the LineageOS build is fully stable. I'm already spending a lot of time getting the LineageOS build stable and I really don't have time to deal with two ROMs simultaneously. I released this RR build because quite a few people want it.
RR is based off LineageOS so actually compiling a build is not time consuming - I just point it to the same repository as my LineageOS build and tell it to build. This is why I am happy to release a RR build whenever I release a LineageOS build.
Thanks for this build, flashed now and all is working ok.
ROM faster and super smoothly.
In addition to the camera, which after some photos fails, there is the bug of the previous RR build, after a call all the audio are muted. Only rebooting or using Tasker to kill mediaserver after call audio work again.
Jc_Py said:
ROM faster and super smoothly.
In addition to the camera, which after some photos fails, there is the bug of the previous RR build, after a call all the audio are muted. Only rebooting or using Tasker to kill mediaserver after call audio work again.
Click to expand...
Click to collapse
You have any tips on how to use Tasker to kill media server after call?
DahakePL said:
You have any tips on how to use Tasker to kill media server after call?
Click to expand...
Click to collapse
This is my Tasker backup.
Install Tasker and restore this.
Basically Tasker will kill media server and play a beep after a call.
The run shell task must be root granted.
Jc_Py said:
ROM faster and super smoothly.
In addition to the camera, which after some photos fails, there is the bug of the previous RR build, after a call all the audio are muted. Only rebooting or using Tasker to kill mediaserver after call audio work again.
Click to expand...
Click to collapse
Try run /system/bin/unmute-call-audio after making a call.
This is the app I use to unmute the audio on boot up. Be interesting to see if it fixes the problem....
dl12345 said:
Try run /system/bin/unmute-call-audio after making a call.
This is the app I use to unmute the audio on boot up. Be interesting to see if it fixes the problem....
Click to expand...
Click to collapse
Only for testing, flashed ROM again and now after call audio works normally, without Tasker.
If the bug appears again I will try your suggestion.
Thanks
Has anyone noticed something with wrong with their accelerometer sensors? After awhile mine seems to stop working and don't change between the landscape and portrait modes.
I'll try to get logs for the next time it happens.
P.S. Do you guys have any suggestions for logging app for convenience?
webmanya said:
Has anyone noticed something with wrong with their accelerometer sensors? After awhile mine seems to stop working and don't change between the landscape and portrait modes.
I'll try to get logs for the next time it happens.
P.S. Do you guys have any suggestions for logging app for convenience?
Click to expand...
Click to collapse
From what I heard on the lineage thread try opening YouTube app and go back to the other application you were using. For some reason he said that it works.
RetroSpect_17 said:
From what I heard on the lineage thread try opening YouTube app and go back to the other application you were using. For some reason he said that it works.
Click to expand...
Click to collapse
Just do screen OFF/ON by power button and all works again...
Отправлено с моего SM-N910C через Tapatalk
best rom is ever used for n910c I think. Thank you so much for building this rom.
RetroSpect_17 said:
From what I heard on the lineage thread try opening YouTube app and go back to the other application you were using. For some reason he said that it works.
Click to expand...
Click to collapse
Yes this one works... But not always.
ukrbroker said:
Just do screen OFF/ON by power button and all works again...
Отправлено с моего SM-N910C через Tapatalk
Click to expand...
Click to collapse
I tried this but it doesn't work...
https://drive.google.com/open?id=1t3J78N0tqOMmQj2NDma6wf28MPPeryEh
If anyone is interested here's a RR boot animation which is normal sized since the one in the rom is really tiny (flashable)
I haven't find these mentioned yet but can someone confirm this isn't just me? Also I'm not sure if this is related to a WhatsApp bug or the ROM. Thanks in advance.
while you're using WhatsApp voice call it looks like screen closes but it continues to register touches even if you turn off the screen using the power button.
Also while listening to the voice messages of you cover the proximity sensor it turns off the screen and stops the playing message.
Hi guys, can I flash the stock Android 6.0 over this, or will it brick my phone?
I have TWRP and rooted with Magisk
thanks
Any way to fix the system apps keeps crashing? only factory reset solves the problem but after 1 hour the problem occurs but on different system app.
example
stock email app
Keeps closing when opening a mail
after factory reset
email works
contacts closing
email closing