704 replies to this topic

[The Doctor]

Yeah. Sort of working but toggles aren't working. Some still won't load either. Will play around some more

[alchemist]

Toggles work for me. I did do a clean install. Hotplugx and sio I seem to work; I haven't tried to make any of the other governors or io schedulers work. I don't use the battery script.

[djhbomber1]

Hey man thanks a million for uploading this great ROM, I flashed JellyCore Stock V1.2 (SS2.11) and it looks great.
I do have two issues that I've seen: one is that my wallpaper reverts to default after being asleep for a while (not so big a deal), and the second is something I can only describe as a "RAM leak." Starting off I have over 500MB free, but after a few hours' time it slowly but surely falls to as low as 1MB free. That's something I've never seen before; I'm not sure if anyone else has or is experiencing this, or even if it's me (I haven't done any performance tweaks), but it makes my phone unusable after a few hours uptime.

[darkavenger64]

Has anybody else been experiencing excessive overheating of the phone after upgrading from JellyCore Stock 1.1 to JellyCore Stock 1.2? My case is not the problem as the phone gets noticeably hotter then it should be even in open air without the case on. I am running standard JellyCore Stock 1.2 with the battery saver script set to run at boot, 300mhz to 1.2ghz, governor is hotplugx and scheduler is sio.

[arch7angels]

I've had the same experience and I'm running the same settings.

[alchemist]

Has anybody else been experiencing excessive overheating of the phone after upgrading from JellyCore Stock 1.1 to JellyCore Stock 1.2? My case is not the problem as the phone gets noticeably hotter then it should be even in open air without the case on. I am running standard JellyCore Stock 1.2 with the battery saver script set to run at boot, 300mhz to 1.2ghz, governor is hotplugx and scheduler is sio.

I haven't tried Jellycore, but I have experienced throse symptoms with Scalpel, so I wonder if it's not an AOKP issue. Give Cyancore a try, maybe.

[darkavenger64]

I haven't tried Jellycore, but I have experienced throse symptoms with Scalpel, so I wonder if it's not an AOKP issue. Give Cyancore a try, maybe.

I have been trying to avoid switching to Cyancore/cyanogenmod based roms for the main reason of that I prefer the customization features of AOKP over that of Cyanogenmod. I was not experiencing the issue on JellyCore 1.1 so I might just revert back to that for the time being until a new update is pushed, Hopefully they will fix this problem.

[twith70]

For those with problems after flashing, please try the following: set up phone, install and update busy box (smart install). Reboot. In recovery wipe cache and dalvik cache. Restart. Problem with flashing is no matter how diligent the dev is if there are any remnants of a previous Rom or missing binaries the Android system will go crazy trying to find everything it needs to operate. If it has conflicting programs the CPU will work away your battery..and heat up the phone. I have made this common practice after an install and found the problems usually go away.

[twith70]

In the earlier post I mentioned set up the phone..this includes installing your apps. With these Rom's the android system cannot control memory usage until you reboot with the apps installed.

[The Doctor]

Had a 100% full charge at Midnight, woke up at 6am.....Phone was completly dead. Cyancore v1.3 is draining the battery big time TSC

[TeamSpeedCore]

I agree Doctor. So..here's all the things I have noticed about this build so far, I apologize for not catching these issues right away, I was having problems getting the rom onto my phone..I believe I have a bad cable.

• battery drain, my thoughts would be build.prop. I know what to do here..
• MMS is not uninstallable, I am getting very annoyed with two messages per one message. I will fix this easily.
• CPUSleeper.apk does not work. I pulled this from a very old rom, so it doesn't surprise me. Will remove.
• Boot animation struggles to work. I have several boot animations thanks to Jaekar99 so I will just throw a different one in there. I believe that JellyCoreV1.2 is using it.

I also got a pm from Bytecode, the person who provided the battery and performance scripts, along with the links to the governors. He said his favorite governor is pegasusq, along with sio. Give that a try.

Here's the plan. I know a lot of you have downloaded CyanCoreV1.3, but I am going to fix these bugs and RE-UPLOAD the rom. This means you will need to re-download and flash, and please just delete the current CyanCoreV1.3 unless you are actually content with it. For now I am taking the link down because I don't want people experiencing preventable issues.


EDIT* From now on The Doctor and I will run roms for an entire day before posting them. I am very sorry for the inconvenience. We will let you know while we are testing so you can be all excited for a day while we test ..unless of course there are more bugs to be fixed.

EDIT#2* Also note that this CyanCore build is off of the newest (as of yesturday) CM10 build, not the 8/03 build. Instead of just fixing those bugs I listed, there is another new build as of today, (10/18/) so I am going to just start over and try the newer build. Wish me luck..

[a4udi98]

TeamSpeedCore et al,

thanks for the great work on this ROM. I've also noticed that I get FC on the Gallery when in the Camera.

Just thought I'd mention, maybe others are seeing this too.

FYI I am using SS3 with a couple other ROMs. Not sure if this is potentially an issue since the gallery is using the external card.

[The Doctor]

TSC....I think CPUSleeper isn't working because you didn't set the permissions. I can help with that, but let me know if you still are going to pull the apk. MMS is working, you just have to fix permissions, but if you want to still make stock uninstallable, tear it up brah. Fixing Permissions in SS v3.04 is pretty smooth and faster that it was in SS v2.11. I like that you give us some choices along with stock. ROM itself was snappy, felt a little quicker than JellyCore v1.2 (my daily driver). Other than the nasty battery drain, it was running pretty solid. Wifi locked right away and pretty fast. 4g took a smidge longer to lock, but that's not a deal breaker. It was a little glitchy when I started to turn on the CM10 Mods like weather, calender display, etc.

[The Doctor]

TeamSpeedCore et al,

thanks for the great work on this ROM. I've also noticed that I get FC on the Gallery when in the Camera.

Just thought I'd mention, maybe others are seeing this too.

Stock camera or was it a app from the Play Store? Only reason I ask is this bug has pretty much been squashed at the source level. If it's the stock camera, clear cache, clear dalvik and then fix permissions. I just noted above that SS v3.04 is soooooo easy to use and the Fix Permissions function is a snap. hashcode gave us status bar and you can see the code actually running. Not a big deal really, but for guys like me I like to actually see the process running.

[lazer]

...Here's the plan. I know a lot of you have downloaded CyanCoreV1.3, but I am going to fix these bugs and RE-UPLOAD the rom. This means you will need to re-download and flash, and please just delete the current CyanCoreV1.3 unless you are actually content with it. For now I am taking the link down because I don't want people experiencing preventable issues.....

Will we (whom are on the old CyanCoreV1.3) be able to simply update by wiping cache & dalvik OR will we have to start from scratch and wipe data and everything?

Thanks.

Just moved from CM10 Stock to this CyanCore V1.3 yesterday and like it overall much better.

[a4udi98]

Stock camera or was it a app from the Play Store? Only reason I ask is this bug has pretty much been squashed at the source level. If it's the stock camera, clear cache, clear dalvik and then fix permissions. I just noted above that SS v3.04 is soooooo easy to use and the Fix Permissions function is a snap. hashcode gave us status bar and you can see the code actually running. Not a big deal really, but for guys like me I like to actually see the process running.

Tried this and it didn't work. it seems like it FCs whhile the camera is trying to focus, because it isn't instantaneous. Even after clearing data on the Gallery app i still can't get the camera to open up without rebooting. Sometimes I can get it to show a message saying 'Can't connect to the Camera' also.

I am also seeing this on other JB CM10 based roms (KOA). so i dont think its a bad install

Edited by a4udi98, 18 October 2012 - 06:03 AM.

[garywojdan81]

Tried this and it didn't work. it seems like it FCs whhile the camera is trying to focus, because it isn't instantaneous. Even after clearing data on the Gallery app i still can't get the camera to open up without rebooting. Sometimes I can get it to show a message saying 'Can't connect to the Camera' also.

I am also seeing this on other JB CM10 based roms (KOA). so i dont think its a bad install

Did you, by chance, use the latest JB gapps package? I read somewhere on here that it breaks the camera in cm10.

Sent from my DROID RAZR using Tapatalk 2

[a4udi98]

Did you, by chance, use the latest JB gapps package? I read somewhere on here that it breaks the camera in cm10.

Sent from my DROID RAZR using Tapatalk 2

Ahhh, that must be it. I believe it was from October 11th. Is it possible for me to flash the previous package over it? or do I need to completely reflash the ROM?

--------------
I flashed the 7/26 jb gapps and the problem no longer persists. I'm surprised this hasn't been noted in more of the ROMs threads.

[alchemist]

TSC....I think CPUSleeper isn't working because you didn't set the permissions. I can help with that, but let me know if you still are going to pull the apk. MMS is working, you just have to fix permissions, but if you want to still make stock uninstallable, tear it up brah. Fixing Permissions in SS v3.04 is pretty smooth and faster that it was in SS v2.11. I like that you give us some choices along with stock. ROM itself was snappy, felt a little quicker than JellyCore v1.2 (my daily driver). Other than the nasty battery drain, it was running pretty solid. Wifi locked right away and pretty fast. 4g took a smidge longer to lock, but that's not a deal breaker. It was a little glitchy when I started to turn on the CM10 Mods like weather, calender display, etc.

What exactly is the issue with MMS? I haven't sent or received any in a few days; will the stock application not send and/or receive MMS with these ROMS? You said that fixing the permissions will fix MMS. Will this fix MMS with the stock application, or only with 3rd-party applications? Thanks in advance for the clarifications.

[drewreyes78]

Has anybody else been experiencing excessive overheating of the phone after upgrading from JellyCore Stock 1.1 to JellyCore Stock 1.2? My case is not the problem as the phone gets noticeably hotter then it should be even in open air without the case on. I am running standard JellyCore Stock 1.2 with the battery saver script set to run at boot, 300mhz to 1.2ghz, governor is hotplugx and scheduler is sio.

I haven't tried Jellycore, but I have experienced throse symptoms with Scalpel, so I wonder if it's not an AOKP issue. Give Cyancore a try, maybe.

Try using "interactive" as you Governor, hasn't overheated nearly as much as hotplugx and has had great battery life