[ROM][ACS]SyndicateROM Frozen 1.2 (Updated 6/20)

[Paul627g]

I have a quick question... is this ROM overclocked to 1.3ghz by default or do I need an app to overclock it?

Go to the source link in the OP of this thread and it will take you to the devs thread for Syndicate. There is in the OP of the thread a link to get SetCPU for XDA members. Otherwise you will have to purchase it from the Market or you can use a free utility called OverClock Widget

 

[Jinded]

Good evening,

I installed the SyndicateROM Frozen 1.0.2 (Malanga) today and everything worked flawlessly with exception to the in-car bluetooth voice recognition. Prior to this rom I had no issue utilizing the voice commands over bluetooth through the car system.

I can make calls by saying "dial by number" but when I say "dial by name" it fails. I can dial by name if i use the voice recognition by talking into the phone just fine, its only over bluetooth that it can not understand the commands. For what it's worth I am using the in-car bluetooth system on a 2011 hyundai sonata.

Thanks!

I've tried the included Voice Dialer and Voice Search, as well as a few other applications (VLingo and Voice Actions), but none seem to let me speak into my bluetooth headset or my in-car handsfree device. I always have to speak into the phone's mic. Kinda sucks.

 

[Sirus213]

I haven't had issues saving photographs.

I have noticed, however, that when shooting video I will occasionally get skips in the video. Maybe this is due to the saving issue.

Is it your MicroSD card?

Not sure if it has anything to do with my microSD, everything else seems to run fine, except today I was experiencing SMS bug when i would receive a text the time stamp would be super off. I.E.i received a message at 12:55pm but the time stamp on the message said it came in at 6:34pm. so any message i sent to respond to that text would be place above that 6:34pm message making it really confusing...I was roaming at the time this could be the issue.

 

[darkdan]

Is anyone else having a problem with the browser after watching a youtube video? I have to close it and reopen the browser because the images are screwed.

 

[ZiggSVO]

Not sure if it has anything to do with my microSD, everything else seems to run fine, except today I was experiencing SMS bug when i would receive a text the time stamp would be super off. I.E.i received a message at 12:55pm but the time stamp on the message said it came in at 6:34pm. so any message i sent to respond to that text would be place above that 6:34pm message making it really confusing...I was roaming at the time this could be the issue.

Its definately cuz u were roaming . I roam in my office all the time and it happens...everyday so I know what u mean by confusing lol

 

[ZiggSVO]

Is anyone else having a problem with the browser after watching a youtube video? I have to close it and reopen the browser because the images are screwed.

Happens on mine also...use dolphin mini...fixes it right up lol

 

[ZiggSVO]

Ok...idk what happened...but my Market app is now the default green??? Didn't download anything or flash anything...how do I get the blue one back?!??

 

[jrz5024]

Ok...idk what happened...but my Market app is now the default green??? Didn't download anything or flash anything...how do I get the blue one back?!??

+1 on this. What the eff? Just happened today.

 

[Paul627g]

Market must of updated.

 

[ZiggSVO]

Market must of updated.

Just getting ready to say uninstall the updates and its back to blue lol

 

[mjbelknap]

I still have the blue market, but it asks me to accept the user agreement every time I open it. Is this just me?

Also, I dis a 3 finger reset on the phone and now severl of my apps are force closing. This have anything to do with the fact that this rom isn't journaled? What is the simplest way to fix without restoring a backup from 3 weeks ago?

 

[Paul627g]

I still have the blue market, but it asks me to accept the user agreement every time I open it. Is this just me?

Also, I dis a 3 finger reset on the phone and now severl of my apps are force closing. This have anything to do with the fact that this rom isn't journaled? What is the simplest way to fix without restoring a backup from 3 weeks ago?

You could attempt booting back into CWM and clear Cache and Dalvik only and see if that helps out. Most likely if your running journaling off and you now ended up with FC's something got corrupted and your going to have to use the backup or start fresh... Price you pay for running without journaling.

BTW, I really doubt the 3 finger reset (soft reset) had anything to do with it.

 

[Jinded]

You could attempt booting back into CWM and clear Cache and Dalvik only and see if that helps out. Most likely if your running journaling off and you now ended up with FC's something got corrupted and your going to have to use the backup or start fresh... Price you pay for running without journaling.

BTW, I really doubt the 3 finger reset (soft reset) had anything to do with it.

Actually I disagree, I think the 3 finger reset is exactly what caused it (same thing happened to me a few times in the past). The 3 finger reset is essentially the same thing as pulling the battery, meaning some stuff is most likely still running when you do it, and the lack of journaling can corrupt this data.

You can enable journaling in this ROM by loading a CWM backup of the ROM (which is probably what you're gonna have to do at this point anyway).

 

[jrz5024]

Actually I disagree, I think the 3 finger reset is exactly what caused it (same thing happened to me a few times in the past). The 3 finger reset is essentially the same thing as pulling the battery, meaning some stuff is most likely still running when you do it, and the lack of journaling can corrupt this data.

You can enable journaling in this ROM by loading a CWM backup of the ROM (which is probably what you're gonna have to do at this point anyway).

You are correct. A 3 finger reset is an improper shutdown which can cause corruption on no journaling roms.

Anything but selecting "shutdown" or "reboot" from the power menu is considered an improper shutdown and runs the risk of corruption.

 

[Paul627g]

You are correct. A 3 finger reset is an improper shutdown which can cause corruption on no journaling roms.

Anything but selecting "shutdown" or "reboot" from the power menu is considered an improper shutdown and runs the risk of corruption.

Okay if this is correct then why now, or more specifically more recently say sometime after EB13 hit the scene? I started running DK28 back on release day about December 3rd, not more than a week or two later we had EXT4 introduced to us. Now from that time period to somewhere after EB13 I used the soft reset (3 finger reset) and also programs like Quickboot/Reboot Manager until we lost redirector function for those apps literally dozens of times a day for flashing... Never had issues, then like I said sometime after EB13 I started to notice these fc issues but that was only when I attempted to run the new CIQ removal ROMs so I blamed it on that. Since then I was told by k0nane that CIQ removal doesn't have anything to do with it and its the lack of journaling... I just don't understand it. Its like something triggered this recently because it started happening to people not long ago and those same people like myself never had issues previously.

I don't mind running journaling enabled. If my device fails due to the wear and tear journaling adds I will simply use my Sprint ESP plan to replace the device if need be. Still I would really like to have a real explanation of why recently this effects me but never did before. Also you can't really blame this on the period of time that I used this method and say that it eventually started to break down my device, there are people that have recently purchased brand new devices and have this happen right out of the box so it I would think it can't be blamed on repeated abuse over time doing the soft reset or battery pulls.



Sorry I didn't mean to hi-jack this thread or go off topic.

 

[Jinded]

Okay if this is correct then why now, or more specifically more recently say sometime after EB13 hit the scene? I started running DK28 back on release day about December 3rd, not more than a week or two later we had EXT4 introduced to us. Now from that time period to somewhere after EB13 I used the soft reset (3 finger reset) and also programs like Quickboot/Reboot Manager until we lost redirector function for those apps literally dozens of times a day for flashing... Never had issues, then like I said sometime after EB13 I started to notice these fc issues but that was only when I attempted to run the new CIQ removal ROMs so I blamed it on that. Since then I was told by k0nane that CIQ removal doesn't have anything to do with it and its the lack of journaling... I just don't understand it. Its like something triggered this recently because it started happening to people not long ago and those same people like myself never had issues previously.

I don't mind running journaling enabled. If my device fails due to the wear and tear journaling adds I will simply use my Sprint ESP plan to replace the device if need be. Still I would really like to have a real explanation of why recently this effects me but never did before. Also you can't really blame this on the period of time that I used this method and say that it eventually started to break down my device, there are people that have recently purchased brand new devices and have this happen right out of the box so it I would think it can't be blamed on repeated abuse over time doing the soft reset or battery pulls.



Sorry I didn't mean to hi-jack this thread or go off topic.

So are you saying that you've had these issues on a journaling-enabled EXT4 ROM? You said you started having the issue when you started using the CIQ-removed ROMs, but could it be that each ROM you had an issue with just happened to have journaling disabled as well?

 

[jrz5024]

Okay if this is correct then why now, or more specifically more recently say sometime after EB13 hit the scene? I started running DK28 back on release day about December 3rd, not more than a week or two later we had EXT4 introduced to us. Now from that time period to somewhere after EB13 I used the soft reset (3 finger reset) and also programs like Quickboot/Reboot Manager until we lost redirector function for those apps literally dozens of times a day for flashing... Never had issues, then like I said sometime after EB13 I started to notice these fc issues but that was only when I attempted to run the new CIQ removal ROMs so I blamed it on that. Since then I was told by k0nane that CIQ removal doesn't have anything to do with it and its the lack of journaling... I just don't understand it. Its like something triggered this recently because it started happening to people not long ago and those same people like myself never had issues previously.

I don't mind running journaling enabled. If my device fails due to the wear and tear journaling adds I will simply use my Sprint ESP plan to replace the device if need be. Still I would really like to have a real explanation of why recently this effects me but never did before. Also you can't really blame this on the period of time that I used this method and say that it eventually started to break down my device, there are people that have recently purchased brand new devices and have this happen right out of the box so it I would think it can't be blamed on repeated abuse over time doing the soft reset or battery pulls.

Sorry I didn't mean to hi-jack this thread or go off topic.

I'm not a developer, so I'm speculating here, but my guess is that certain shutdown scripts have to be performed before the phone shuts off, just like when you turn off your computer via the start menu. The 3 button press bypasses all that and restarts the phone instantly, like restarting your computer by long-pressing the power button. However, computers are constantly making backups should such an event occur - this is why if you restart your computer because Microsoft Word froze, you're greeted with a recovery copy upon next boot. When journaling gets disabled, those backups don't get made, and the bypassing of proper shutdown scripts causes data corruption if a particular file is being accessed at the time of shutdown.

As for why we haven't ran into these problems until recently, I was under the impression that roms didn't start disabling journaling until recently, but then again I'm fairly new when it comes to the rom scene (I rooted back when TER was the rom to beat). Personally, I haven't ran into any data corruption myself, so I can only speak to others' experiences.

 

[Paul627g]

That is what I'm saying, something along the lines of them disabling journaling must have taken place after EB13 was released. Up to that point I never had any FC problems from the 3 finger boot or from flashing themes and getting an FC frenzy. Bottom line, now that I know that enabling journaling fixes my issues that is what I'm going to stick with. There was much talk about EXT4 and how it was going to kill our devices early and now its talked about again with journaling being enabled. I guess some people may worry but to someone like myself that has the ESP insurance, first signs I see of NAND chip problems or memory issues the phone will be taking a rough little slide down the pavement or something to that effect and then going to Sprint for an exchange.. LOL...

To me that extra few bucks a month is does pay off for occasions that may arise like this eventually or a used up USB port from to much use which is now happening to many users...

 

[Jinded]

That is what I'm saying, something along the lines of them disabling journaling must have taken place after EB13 was released. Up to that point I never had any FC problems from the 3 finger boot or from flashing themes and getting an FC frenzy. Bottom line, now that I know that enabling journaling fixes my issues that is what I'm going to stick with. There was much talk about EXT4 and how it was going to kill our devices early and now its talked about again with journaling being enabled. I guess some people may worry but to someone like myself that has the ESP insurance, first signs I see of NAND chip problems or memory issues the phone will be taking a rough little slide down the pavement or something to that effect and then going to Sprint for an exchange.. LOL...

To me that extra few bucks a month is does pay off for occasions that may arise like this eventually or a used up USB port from to much use which is now happening to many users...

Yeah before EXT4 we were all on RFS, which has something like journaling built in (I think it's called something different on that file system). I remember when EXT4 first started being used, reading warnings about how it could potentially cause data corruption if journaling was not handled properly by the ROM developer.

 

[Paul627g]

Yeah before EXT4 we were all on RFS, which has something like journaling built in (I think it's called something different on that file system). I remember when EXT4 first started being used, reading warnings about how it could potentially cause data corruption if journaling was not handled properly by the ROM developer.

Yep. Like I said, I had no issues ever until shortly after EB13 hit... Thats when I first started having troubles. Before then I would use the 3 finger boot whenever and multiple times a day flashing ROMs. That was during my time working with Ragnarokx on TER doing the Mini Theme for it and trust me I flashed like a junky.... I soft reset like a mad man... Never had an issue...

Oh well.. Journaling enabled for me