Related
Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.
I have the Chinese version of the Find 7 currently running MoKee 44.4 because I thought this issue was caused by AOSPA, which I flashed for the first time yesterday. Anyway when I make a call the screen turns off as it should and will not come back on no matter what I do. I have to reboot the phone every time. I looked through similar threads but they all seem to be unrelated to having a custom rom; this problem only started occurring after I flashed one & everything worked fine when I was running Color OS 2.0. I tried installing a new dialer but the same problem happened.
Does anyone know of a way not to have the screen turn off when making a call or better yet how to fix the issue?
Thanks very much!
I'm having a very similar situation with Paranoid Android 4.6 (both beta4 and latest beta6).
If I long-press home button, I'm sent back to the lock screen, but only after the call is finished.
Maybe there's a problem with AOSPA's proximity sensor during calls?
Sometimes, the screen will not turn off, but the screen will not react to any touch input during the call.
Power button will turn screen off but not back on again.
This is a problem coming from ColorOS 2.0.x.
I will try to flash back to and older version of ColorOS. After that try an AOSP rom.
Sent from my X9006 using Tapatalk
same problem
Whit all rom use CM11 based or similar, I have black screen when I call, and no input possible!
the only ROM stable is the Kakulay, bet it have several problem whit the contacts management! it confuse the name and numbers in the memory and SIM card!
Hi,
My nexus 7 screen doesn't rotate back from landscape mode. This happens when I watch the BBC iPlayer. Then I have to uninstall the iPlayer and reboot the device each time. This was fine before going to Lollipop.
Any ideas what might be happening?
Sent from my Nexus 5 using XDA Free mobile app
crywolf_68 said:
Hi,
My nexus 7 screen doesn't rotate back from landscape mode. This happens when I watch the BBC iPlayer. Then I have to uninstall the iPlayer and reboot the device each time. This was fine before going to Lollipop.
Any ideas what might be happening?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Check the settings in Display > Auto Rotate Screen. It might be disabling auto rotation but not toggling back.
If that's the case, you could use Tasker to turn auto rotation back on when you exit iPlayer.
I don't use the BBC iPlayer, but like the OP, I have been having this problem as well. Auto-rotate would work again after a reboot, but then just fail at any given time. I've also had this problem ever since Lollipop was installed to my device, and never when I had KitKat or even Jellybean on it. My Nexus 7 2013 is a 16 GB model, and it's on Lollipop 5.1.1 build number LMY47V.
I have this problem on CleanROM 6 with both Elemental and Glitch Kernel. It only happens after a couple of hours of use and a reboot fixes it. I have not been motivated enough to flash the stock kernel to see of that fixes it. I haven't seen it mentioned by anyone else in the Clean ROM thread.
Me too, came here to look for answers.
I hope it's not hardware related.
try clean restore to "stock"
I had this issue with grogg's rom (mostly stock) and went back the the cleanrom (closer to stock) with a full wipe, and it's back to working as it should. So, maybe just some sort of side effect or bad data somewhere.
Try a really "clean" reset of the OS/environment and see if that helps
Same here. Have to use certain apps to force the orientation to change
Sent from my Nexus 7 using XDA Free mobile app
I've been having this problem on 4.4, 5.0.1, 5.1, stock rom, oakp, pa. And I found the following (in hope it would help fixing it):
1. Rebooting doesn't always fix it. Sometimes I have to clear cache + dalvik.
2. The issue happens less often when not using Nova Launcher and sticking to the Google Launcher.
3. The issue happens less often when switching off the magnetics sensor (that turns off the device when closing a 'smart' lid) using ElementalX kernel.
Could anyone confirm that?
Turn off your tablet. Try to press back cover hardly on N & S at nexus logo for a few second. Then turn on your tablet again. It should work.
I don't know why, but I also had this issue. I flashed stock 5.1.1 and rotation works normally.
If I had to guess, and I do..., I'd say it was an app causing the problem. Don't know what one or how though.
Flashing the stock kernel solved it for me. It's been a week and I have not seen the issue since.
I believe the problem is because the sensor board is either failing or just faulty and works on and off.
I hate the same problem and if you open CPU-Z and go to the sensor section when the screen doesn't rotate you can see most/ all of the sensors are not being picked up/detected
My fix is to shut down the hit my knuckle out of anger on the bottom of the tablet (On the screen and the back) Its as if the board is loose or has something that isn't making contact
Hello everyone, I got LeEco Le Pro 3 two weeks ago. For the past two weeks of testing, I notice that the screen quickly turns red when pressing the power button to turn the screen off. Is any of you facing this problem? It happens randomly, not every time. I have attached the video in slow motion capture in the 7z zip file. So you can see, what I am talking about. Let me know if any of you see it.
In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?
marik1 said:
In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?
Click to expand...
Click to collapse
I did not power sleep my phone rapidly. The red screen still persist. I don't know if force kill app cause it. I submit the feedback through the leeco experience center about this issue. This is what I got from them:
"Le Engineer
Hello,
I just get some information for this issue, in low battery level the red screen issue will happen sometimes. We also find the same thing on other brand device.
However R&D team are working on it. Hope it will be fixed in next generation product.
Sorry for inconvenience. Thank you for choosing the LeEco."
So I don't know if my phone is defective or not. It's hard to tell. Base on this message, look like there is no fix for this.
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.
crazy1990 said:
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.
Click to expand...
Click to collapse
It could be a software issue since I don't have that on CM.
marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.
losteagle said:
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.
Click to expand...
Click to collapse
If you have another phone with slow motion support just like I did, you can try that.
Other thing I want to mention, I would like to know that if the red screen does not happen to people who have CM or MIUI on lepro 3, can any of you go back to EUI and try to do the same steps? If you can. This would more confirm that the software is the issue and not the hardware defect.
Any update?
Hi folks! I've been searching for this rare issue since I got my LM2 last week. I have the very same issue and I notice the same @crazy1990 mentioned here. Besides, I notice this red light is more noticeable when the brightness is higher.
IMO, I don't feel it's a matter of bad hardware (I hope so), as there are no clues of any other issues at all. I'm also using stock (23s) and I suspect it's some poorly designed fade for the ROM.
Any updates from anyone?
Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.
crazy1990 said:
Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.
Click to expand...
Click to collapse
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?
razmth said:
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?
Click to expand...
Click to collapse
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.
crazy1990 said:
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.
Click to expand...
Click to collapse
Great to know it doesn't happen on Omni/Purity. My biggest concern was an increasing degradation and/or flickering issues arising when changing to a stock ROM.
Thanks for your information.
Sent from my Le X820 using Tapatalk
Hi Guys! I am new here, my samsung A52s 5g just freezes and always going back to home screen specially when connected to wifi. It just happened all of a sudden, I didn't even downloaded anything, I just use my phone on social media platform and some games.
Here's what I did
I tried factory reset - issue still persists
I tried hard reset, clear cache - issue still persists
I tried reprograming with Odin the latest version of Odin - still didn't fix the problem I even downgraded the android version with the old A52s firmwarw with Odin but the issuw still persists.
Does anyone encountered the same issue? And know a solution? Please let me know. TIA
Welcome to XDA
Sounds like a hardware failure.
If you did all that not much else left.
I hope someone know a solution how to fix this problem. It just happened all of a sudden. The phone was working fine beforw my son just turned it off. When I turned it back on it freezes wherever I go and going back to homescreen by itself. It happens all the time when the wifi is on. But when the wifi is off, it is somehow ok.
Well leave the wifi off. You went back to a known good firmware version and set the data user partition to its default settings. Unless you installed a buggy 3rd party after that there's not much left other than a hardware failure.
Data user partition should be in default settings I guess since flashing to known good version.
Wilsaryu said:
Data user partition should be in default settings I guess since flashing to known good version.
Click to expand...
Click to collapse
You did a factory reset as well.
blackhawk said:
You did a factory reset as well.
Click to expand...
Click to collapse
Yes sir!
Sounds like you're having the same issue as me: https://forum.xda-developers.com/t/a52s-randomly-rebooting-freezing.4503129
When this happens, do you see the Samsung logo that you normally see when you turn on your phone?
Stonos said:
Sounds like you're having the same issue as me: https://forum.xda-developers.com/t/a52s-randomly-rebooting-freezing.4503129
When this happens, do you see the Samsung logo that you normally see when you turn on your phone?
Click to expand...
Click to collapse
Yes, restarting phone is fine like normal, but whenever I browse on my a52s it keeps lagging but when press the return/back button it goes back to normal but when I repeat browsing the same thing it keeps lagging, sometimes it freezes and going back to home screen.
Wilsaryu said:
Yes, restarting phone is fine like normal, but whenever I browse on my a52s it keeps lagging but when press the return/back button it goes back to normal but when I repeat browsing the same thing it keeps lagging, sometimes it freezes and going back to home screen.
Click to expand...
Click to collapse
What browser? Try clearing that browser's data.
Try a different browser like Brave.
Google chrome browser but not just on browser also in every app. Even in Settings it keeps freezing and going back to home screen
Wilsaryu said:
Google chrome browser but not just on browser also in every app. Even in Settings it keeps freezing and going back to home screen
Click to expand...
Click to collapse
That's likely a hardware failure of some type probably the mobo.
Hello guys! My A52s is now working in properly, no more freezing/lagging. What I did is I drained the battery to zero and had it fully charged then I saw an update from android 12 to android 13. Voila my a52s is back to normal like new . Thank you guys for your time to reply. God bless us all
Wilsaryu said:
Hello guys! My A52s is now working in properly, no more freezing/lagging. What I did is I drained the battery to zero and had it fully charged then I saw an update from android 12 to android 13. Voila my a52s is back to normal like new . Thank you guys for your time to reply. God bless us all
Click to expand...
Click to collapse
Time will tell. I find that disconcerting. Did Samsung release that model with that big of a glitch in the firmware for some models of that production run? Yes, well... that's Samsung.
I've had this issue. Sent it back for warranty claims and they sent me a replacement unit, Initally I though GalaxyMax Hz caused this issue - so I haven't used it again.