My Canadian galaxy s4 has been having lag problems while running today's (June 29th) version of CyanogenMod 10.1, and the same problem occurred with the version from the 27th.
I experience periods of heavy lag, and even random reboots. This problem did not occur for me on earlier veraions of CM10.1 and I am wondering what is happening.
Can anyone help?
You may have reached a point where you need to do more than dirty flash this update. Have you tried backing up and performing a full wipe before flashing?
dalediciocco said:
My Canadian galaxy s4 has been having lag problems while running today's (June 29th) version of CyanogenMod 10.1, and the same problem occurred with the version from the 27th.
I experience periods of heavy lag, and even random reboots. This problem did not occur for me on earlier veraions of CM10.1 and I am wondering what is happening.
Can anyone help?
Click to expand...
Click to collapse
I face heavy lags too here on the final release of CM10.1 for my N7. Happens too much. Tried the franco kernel but still the same.
dalediciocco said:
My Canadian galaxy s4 has been having lag problems while running today's (June 29th) version of CyanogenMod 10.1, and the same problem occurred with the version from the 27th.
I experience periods of heavy lag, and even random reboots. This problem did not occur for me on earlier veraions of CM10.1 and I am wondering what is happening.
Can anyone help?
Click to expand...
Click to collapse
I had the same issues. Running the 6/26 build on my US AT&T version was fine. Any update after that I would get lag and reboots when dirty flashing without wiping data. Tried 6/27, got the same issue as you, and same with 6/28. What fixed it was doing a full wipe (Factory Reset, wipe data, then advanced wipe data, system, cache, dalvik) then flashing the latest daily. Something in the firmware changed significantly that required a fresh clean install.
Related
Hi Guys,
Ive flashed AOKP Milestone 3 (3g version) to my Galaxy Tab 10.1. After flashing it i cant even start the initial setup because I keep getting a message "Unfortunately. the process com.android.phone has stopped working" I keep clicking ok and it wont go away.
Ive tried wiping the dalvik, cache, and Factory reset with no luck. If I flash the WiFi only version it seems to work fine but trying to flash the 3g version always brings up that message.
any advice?
ricochet69 said:
Hi Guys,
Ive flashed AOKP Milestone 3 (3g version) to my Galaxy Tab 10.1. After flashing it i cant even start the initial setup because I keep getting a message "Unfortunately. the process com.android.phone has stopped working" I keep clicking ok and it wont go away.
Ive tried wiping the dalvik, cache, and Factory reset with no luck. If I flash the WiFi only version it seems to work fine but trying to flash the 3g version always brings up that message.
any advice?
Click to expand...
Click to collapse
I never flash the aokp m3....but i flash the aokp build 23,24,25,26....only in build 23, the 3g connection is working...
amiruramli93 said:
I never flash the aokp m3....but i flash the aokp build 23,24,25,26....only in build 23, the 3g connection is working...
Click to expand...
Click to collapse
I might try flashing one the builds then. Any annoying bugs with build 23? all i want is a fairly stable ICS rom for my tablet that will allow for 3g sharing. As far as i know there are only two roms out with ICS cyanogenmod and AOKP and Cyanogen doesnt have the camera working.
I didnt try any of the builds as they are meant to be less stable and the milestone should work with 3g (its not like what im getting is listed on any of the known issues) so kinda thought it was something i was doing wrong.
BTW my tablet is a Vodafone Ireland one, shouldnt make any difference as its not the Tab 10.1V its the P7500 thin tablet that most people have.
ok tried that and it worked, put the apn's in and even though i dont get that com.android.phone has stopped message anymore it wont connect to data. im sure the apn settings are correct. Im going to try and flash a newer build and post back if im still having any issues. Thanks for your help guys. BTW ICS totally rocks on my tablet i get crazy battery life out of it (although that might be because i cant get any data )
Flashed milestone 4 and everything works great. Thanks for your help guys
Hi everyone,
I've had my RAZR M for just over a year now and I've had several different custom ROMs on it. Several months ago I updated to a newer CM 10.1 nightly and noticed horrible input lag. Scrolling in menus was extremely slow and apps took way longer than usual to open. I tried several different ways of wiping, flashing and installing the ROM but failed to solve the problem. I also tried all kinds of options in the developer menu and the performance settings. No dice.
I fell back to a stable 10.1 ROM until a few days ago when I decided to try the same thing with CM 11. The CM 11 ROM suffers from the same horrible input lag as the older CM 10.1 nightlies. All ROMs after a certain point have the same behavior (I don't know the nightly it started on sadly). I'd really like to use a newer ROM but the ROM is unusable with the input lag.
Has anyone had similar problems? Thanks for any input. I'll provide any additional info that helps.
Additional info:
Using TWRP 2.6.3 from here here
Getting my ROMs from the official cyanogenmod release.
I've tried many combinations of wiping everything but external SD while installing. Recently tried mounting /system while wiping but that didn't help either.
I've tried googling the problem and I've found some similar problems but no one seems to have found a solution.
http://www.droidrzr.com/index.php/topic/30889-43-custom-roms-lag/
http://forum.cyanogenmod.com/topic/79209-major-lag-on-nightlies/
The lag also happens on Carbon ROM when I tried it a few months ago.
Stock is better. We will have to wait for official 4.4 for a fix.
Some say my version of pure perfomance helps, I have not tried the cm ver much. Go dev section. Jeeko is back & said he would make a newer.
I've recently moved to a new state and have been having to use my phone's GPS several times a week.
At the time I was using one of the Cyanogenmod 11 snapshot builds(sorry, I can't remember which one ). The GPS worked flawlessly. I would always update to the next snapshot build as they came out. One our two updates later my GPS couldn't seem to get a fix on my location. I tried wiping and doing a clean install of the ROM. Still had issues.
Eventually I got fed up with cyanogenmod and wiped my phone and installed Paranoid Android 4 beta 1. Had the same problem with the GPS. I tried several of the other beta releases as they came out to see if the problem was resolved. It wasn't.
So I restored my phone to stock using the Google factory images (4.4.2). The GPS worked beautifully. So I stuck with stock for a while and did the OTA update to 4.4.3.
After a while I started to miss the features and customizations that come with custom ROMs. So I wiped and flashed Paranoid Android 4.4 RC2. The GPS still can't seem to lock. On the rare occasion that it does it can't keep up with my car, especially if I turn onto another road.
Does anyone know what's up with the GPS? Didn't seen to have this issue at all on Jelly Bean custom ROMs. Is this an issue with Kitkat custom ROMs? Possibly a hardware issue? Any help would greatly appreciated.
Current setup:
Phone: Nexus 4(16gb)
ROM: Paranoid Android 4.4 RC2
Sent from my Nexus 4 using XDA Free mobile app
There appears to be an issue with KitKat and GPS. I'm running stock 4.4.4 and I can't get a GPS lock. I've tried everything I can, including a factory reset. I don't remember having the issue with 4.4.3, but I've seen issues reported going back to 4.4.2.
I don't know about you, but a reboot usually does it for me.
I have recently installed Cyanogenmod 13 to my Galaxy S4.
Since then, i have some Problems with my Sound and randomly Closing applications.
1. The Sound disappears after some Time. The Sound works fine for a few minutes after I started the Telephone.
I have tried some Things:
Fullwipe the Phone, reinstall everything
Reinstalling the newest Samsung firmware, installing Cyanogenmod 13 again.
Reinstalling an older Samsung Firmware, Installing Cyanogenmod 13 again.
The Problem is still the Same.
A Reboot fixes the Problem temporarely for a few Minutes.
2.Applications close or Freeze.
Apps like Twitter or 9Gag freeze, most time when I want to Open a Picture, Video etc.
Just reading works fine.
Closing the app and Restarting the app will Fix it temporarely.
I am Currently Running the 01/20/2016 Nightly, Older Versions or the newest CM12.1 Snapshot have all the same Problems.
Baseband Version: I9505xxugnf1
Are these Problems known or am I the only one who has this Problems?
Problems vary from user to user. So you might very well be the only one.
There are some other CM13 versions (Kushan, Synergy) you could try. Assuming you have a GT-I9505.
Or CM based roms like Resurrection Remix, AICP, etc. But since they are based all on CM, the problems might persist.
Could anyone of you guys kindly help me. I first flashed the unofficial Bliss rom based on cm13 first on my n910c. It was stable enough for daily use, maybe a bit rusty on kernel performance end but nothing too drastic. I however found one of my favourite and must have app Netflix would refuse to work on it whatsoever (loading spins forever when trying to play any movie/tv show). I have searched all over the net to understand why and now I also flashed this cm13 image to see if it could work in this rom. Result same issue!, I did the following and achieved no success
1) cache/dalvik clean and rebooted (the obvious) ALSO full factory wipe as well
2)a suggestion to rename/delete a certain liboencrypto.so
3)change my product model in build.prop
4)try a old xposed hack for tricking the app to think you are on unrooted phone
None of the above worked. I then flashed a lolipop simplerom5c image just to check if this issue is universal for all roms and I was wrong. Netflix ran with no issues in this one which uses a custom kernel and full rooted.
NOW MY actual question (pardon me for the boring and lengthy prologue)
Would flashing a custom kernel to CM13 for n910c possible? if so which one could anyone suggest? AND could it possible solve the dreaded Netflix issue?