I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day.
The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure.
I have tried everything - loaded stock firmware back and ran casual again, flashed Beans 14 and set my entire device back from a fresh install.
Again, tonight, screen froze twice and I had to to a battery pull
Does anyone have any idea what's going on? I never has this issue before and it's driving me nuts - having flashbacks of blackberry battery pulls
Clean or dirty flash? This happened to me the other day, froze out of nowhere for no reason
jcastagnino said:
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day.
The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure.
I have tried everything - loaded stock firmware back and ran casual again, flashed Beans 14 and set my entire device back from a fresh install.
Again, tonight, screen froze twice and I had to to a battery pull
Does anyone have any idea what's going on? I never has this issue before and it's driving me nuts - having flashbacks of blackberry battery pulls
Click to expand...
Click to collapse
Do you have ripple effect, ink color or any of the TW features enabled while using AOSP Lockscreen?
Because if you do, and your phone times out, your phone will freeze and you will need to do a battery pull.
If you use AOSP lockscreen, you have to disable any of the TW lockscreen features.
jcastagnino said:
I have been having an issue with my device recently. I am not sure if it is ROM related or a defective device, but it only seems to happen when auto rotation is enabled. I first noticed the issue last week when I flashed Beans 16 then 17. When the screen would auto rotate, the device would sometimes lock up and I would need to do a battery pull to restart the phone. This was happening over 5 times per day. The strange part is, I never had this issue before when I was on Beans 14, or its just possible I didn't have auto rotate on, not sure...
Click to expand...
Click to collapse
You will get more input if you post in the Beans thread
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
trentb12 said:
Do you have ripple effect, ink color or any of the TW features enabled while using AOSP Lockscreen?
Because if you do, and your phone times out, your phone will freeze and you will need to do a battery pull.
If you use AOSP lockscreen, you have to disable any of the TW lockscreen features.
Click to expand...
Click to collapse
Wow, I didnt know the AOSP lockscreen would casue those issues....so turned it all off, and so far so good!! Guess I never had those options selected before.
I have not had a single lockup/freeze yet. I wonder why Beans does not gray those options out when the AOSP lockscreen is selected.
Let me begin by saying that this rom is hands down one of the best I've used on this device. Flashed the July 8 Uber kernel and have had absolutely no reboots. There are only a couple of problems I have, but they're more cosmetic than anything..I really miss the settings app from the 7/01 release (which I managed to get in the 7/14 release by using Root Explorer, so it's not an issue anymore). The only real problem I have is that the on screen menu button won't go away. I have it disabled in uTool, yet it's still there. How can I disable it?
what else have you changed? i just flashed 7/14 build and i dont have an on screen menu button. i havent changed anything yet.
Q&A for [ROM][4.4.4][CyanideMod]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][CyanideMod]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CyanideMod V2 volume
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
ke7vng said:
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
Click to expand...
Click to collapse
After media volume shows up click to make the volume extendable and then adjust the notification volume. I just noticed this so I'll be looking before I start working on it again
Sent from my SGH-I317 using XDA Premium 4 mobile app
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
radoo7701 said:
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
Click to expand...
Click to collapse
Will you check if omniswitch can be set as default recent app still? I fixed the stock recent issue before I uploaded but if omniswitch can still be selected as default then I uploaded the unfixed version. I'll upload V3.5 soon. Working on a kernel/recovery mod at the current time
Sent from my SGH-I777 using XDA Premium 4 mobile app
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
radoo7701 said:
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
Click to expand...
Click to collapse
Well poop lol. That's actually good tho. Like I said I did already fix this, I just apparently uploaded the unfixed version. Oops. I can run a build fairly quickly as a still have the s2 build cached but I'm using build environment to build and make some recovery changes at the moment
FUSE support?
Hi,
I found this ROM last night and flashed it, and want to say thanks. I was having trouble with other ROMs aborting installation, but this one installed without a hitch. Everything works as it should, and way better than my old CM9 ROM. This was completely painless.
Question: Does the kernel have FUSE support?
I'm trying to get SSHFS working; I can ssh into the target server via terminal emulator, but SSHFS will not mount. It appears to mount but doesn't really. When I click unmount, It complains:
fusermount: error getting lock: Invalid argument
I know this isn't the place to get help with SSHFS, but it will only work if the kernel has FUSE support, so that enters into your bailiwick.
Oh, and a possible issue: It seems I'm not getting as strong a network signal now as I did before flashing this ROM. Is it even possible this could be due to a software issue?
Thanks again for the great work. You are awesome!
Stock recent panel is not working. Could just be my dirty flash. Thank you for your hard work. This ROM is amazing.
Sent from my SGH-I777 using XDA Free mobile app
modem not working
I've been running a CyanogenMod-9 version for quite awhile, until about a week ago when I decided to upgrade. I tried some of the CM-10 versions, and installation aborted midway, leaving me stuck with a non-working phone for a few days.
I flashed CyanideMod-V3-S2 a few days ago, and was very pleased to see it install effortlessly. It looks great, and everything seems to be working, EXCEPT the modem.
The network signal is very weak. I can make calls if I am in town, or on top of a high hill, but often I get no signal at all. I do live in a rural area, but it has never been this weak. Even when I get full bars, they are always white, never blue as they should be. I have no access to data.
I don't know much about AT&T's network; frequencies, etc., but my semi-educated guess is that I'm not picking up all the frequencies I should.
In my settings:
Mobile network is on.
Data is enabled
Preferred network type is set to 3G
Network operators is set to ATT
Access Point Names was set to ATT LTE. I stopped in today at an ATT store, and the rep's phone was set to "ATT Phone" so I experimentally changed to that and rebooted, but saw no change. The settings in the 7 available choices match the setting in other working phones in our household, so I don't think this is a settings problem.
I found the "Consolidated Modem" thread on this site, which lists 13 choices for modems. My phone reports a "Baseband version of i777UCKK6, which is one of the choices in that page, which I assume was installed with the ROM. I don't know if the modem is my problem, and wouldn't have a clue which of these to try. Are they installed through recovery in the same way as the ROM and gapps?
I love this ROM, but the phone is nearly unusable as it is. Has anyone else had this problem, or does anyone have any pointers?
Thanks so much for all your hard work.
Newest modern is UCMD8. Rom wouldn't affect the modem other then the usual kk signal issues
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
dagwoodmash said:
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
Click to expand...
Click to collapse
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
radoo7701 said:
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
Click to expand...
Click to collapse
Thanks for helping him. Yes just reflash gapps. Not sure why it's like that but for some reason it is. I don't need it while testing but then do later on. Strange
Awesome build (V4). Coming from CM of a few months ago, everything is real snappy (also due to flashing afresh).
A few bugs so far:
1) Tapping on notifications in the pull-down drawer doesn't seem to link to anything (the animation works, but the associated action doesn't fire). Additionally, the Halo/Quick Settings buttons at the top of the notification drawer seem to get pushed off the edge of the screen (Would be nice if the Halo button could be removed/Halo disabled).
2) Lock screen slider shortcuts cover up cLock
3) Volume buttons (including from home screen) control system volume, not ringer/notification volume.
Amazing work, in any case! Some day I'll need to get a new phone.
b
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
tri0xinn said:
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
I'm driving but maybe @creepyncrawly could point you there. Flash odin rom, flash odin custom kernel for recovery, make a backup, do a factory reset and wipe system, flash shift kernel, tenor to recovery abs flash rom and gapps. Use V3 of this rom. It's all here. You could probably fine before he sees this. I'm voice typing or I'd help you out
Sent from my SGH-I317 using XDA Premium 4 mobile app
tri0xinn said:
...which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
Use latest stock 4.1.2, I777UCMD8 which you can get from the download repository (link in my signature) Also some other stuff there if you need it, but not the recovery and firmware you need.
thanks a ton, got everything back to square one with that I777UCMD8 tar, easy after that and now running cyanidemod and it's running as slick as my gs5.. at least it seems to be. thanks again:good:
After a couple days of use its still running super slick.. only issue thus far is pretty bad battery life.. any settings i can adjust to improve things? Or another kernel maybe.. anyone else have issues with battery life?