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

[Jinded]

Could also have to do with the lack of journaling.

 

[ragnarokx]

True. Having journaling turned off increases the chance of getting corrupted data.

 

[Donmeister85]

Even us Advisers and mods have trouble from time to time.. LOL.. Story, everything fine for oover 24 hrs running SFR with Bionix Black 4.1 theme and then all the sudden my device started to freeze up because I had my min Mhz on the Twilight Kernel set to 100 which my device just doesn't agree with at times. Anyways I did a soft reboot to get out of the mass lag it was throwing me and I end up booting up with fc's on logsprovider process. So I attempted to get into apps>manage to clear things but that wasn't gonna happen with the FC window popping every sec. So I hit CWM wiped cache/dalvik 3x reboot, still the same. This time I hit CWM and try fix permissions, no good either... So I end up having to reflash the whole ROM because naturally my "working" Nandroid backup is met with fc's as well.

Bottom line I'm so sick of fc's, we just never had these type of problems prior to CIQ removal. You really had to goof something to start popping fc's. Now it seems like whenever it decides its time to screw up it will do so.... Not happy at all... Almost forced into going back and running EB13 pre-CIQ removal ROMs. :'(

Note: this is not being blamed on k0nane he has done a great job. My device for some reason no matter what I do doesn't react well to it.

Wow Paul. That's a heck of a situation you've had there. Been running this ROM since last Thursday, so I'm wondering when my phone will decide to screw up on its own?

 

[sammmmmyg]

I noticed one other user post that youtube upload is no longer possible after flashing the frozen 1.1.0. This happened to me as well. I wiped and reflashed from scratch and got the same issue. The upload feature is completely removed from the Youtube app as well as in the phone's UI (Share with...Youtube). Has anyone developed a work around or confirmed that this is an issue with the rom across the board?

 

[Paul627g]

Wow Paul. That's a heck of a situation you've had there. Been running this ROM since last Thursday, so I'm wondering when my phone will decide to screw up on its own?

I doubt it.. I'm a part of a small group of people that just don't seem to have luck with CIQ removal.. I think its a combination of the outdated CWM and as others have mentioned possibly the fact that journaling is off...

Not sure really... I've never successfully ran a CIQ removal ROM past the 2 days mark yet without FC's coming into play and requiring a full reflash of the ROM.

 

[ragnarokx]

I wonder what the difference is - I've been running Syndicate 1.1.0 since it was released and haven't had a problem. I even locked up my phone a few times by getting a little overclock-happy and no data was corrupted.

 

[Paul627g]

Bad luck I guess... Really starting to feel beaten here... I advise users all day long on how to fix their devices and get the job done but yet I can't get my own device working the way it should... What is up with that? HAHA

 

[ragnarokx]

I'll let you borrow my lucky rabbit's foot

 

[jd195]

Bad luck I guess... Really starting to feel beaten here... I advise users all day long on how to fix their devices and get the job done but yet I can't get my own device working the way it should... What is up with that? HAHA

Fwiw, Paul I was having issues yesterday with FCs, lockups, and apparently random issues of the phone turning off (woke up with it having turned off overnight). This was after having updated to 1.1 from 1.02 on friday night. I started just flashing addons 1 at a time to identify the cause and it seems that the AOSP lockscreen thats posted in the Syndicate thread was causing some issues for me. I used the on posted for Bonsai and it seems to be working...for now at least

Bonsai 4.0.0 aosp lockscreen - xda-developers

 

[blada4life]

when is the next syndicate update coming? i noticed 1.1 was released 3/27 so i dont want to deal with the process unless another one wont be out for awhile.

any input is appreciated.

 

[stilesja]

when is the next syndicate update coming? i noticed 1.1 was released 3/27 so i dont want to deal with the process unless another one wont be out for awhile.

any input is appreciated.

I think you are pretty safe to go ahead with 1.1.0.

Once you get it going its trivial to upgrade.

Sent from my SPH-D700 using Tapatalk

 

[slwelsh]

I've been running this mostly trouble-free for the last few days.

Today I had a freeze while in Google Navigation, right when I rotated from vertical to horizontal. No choice but to pull the battery.

After reboot, the tilt sensors are no longer working. I have no screen rotation, and the GPS Status app shows zero tilt in any direction no matter how I move the unit.

I've tried wiping cache and Dalvik cache with no change.

Several threads elsewhere on this issue say to delete ms3c_yamaha.cfg, then run calibration. However, when I try to rm this file I get this error:

"rm failed for ms3c_yamaha.cfg. I/O error"

trying to run sensorcalibutil_yamaha starts the utility, but then right after saying "Starting calibration utilities..." I get:

access: I/O error
msmachdep_Init failed
calibration utilities failed

Yes, I am rooted (obviously, on SRF), and yes I su'ed before attempting these commands.

So here are my questions:

1. Has any one else experienced freezes when rotating?
2. Short of wiping and reflashing, is there anything else I can do to recover my sensors?
3. Any other suggestions?

Thanks.

-Sean

 

[GSF1200S]

I've been running this mostly trouble-free for the last few days.

Today I had a freeze while in Google Navigation, right when I rotated from vertical to horizontal. No choice but to pull the battery.

After reboot, the tilt sensors are no longer working. I have no screen rotation, and the GPS Status app shows zero tilt in any direction no matter how I move the unit.

I've tried wiping cache and Dalvik cache with no change.

Several threads elsewhere on this issue say to delete ms3c_yamaha.cfg, then run calibration. However, when I try to rm this file I get this error:

"rm failed for ms3c_yamaha.cfg. I/O error"

trying to run sensorcalibutil_yamaha starts the utility, but then right after saying "Starting calibration utilities..." I get:

access: I/O error
msmachdep_Init failed
calibration utilities failed

Yes, I am rooted (obviously, on SRF), and yes I su'ed before attempting these commands.

So here are my questions:

1. Has any one else experienced freezes when rotating?
2. Short of wiping and reflashing, is there anything else I can do to recover my sensors?
3. Any other suggestions?

Thanks.

-Sean

I would wait for a dev to confirm this, but every time Ive seen "I/O error" (Input/output error), it has been due to a corrupt filesystem. Since Syndicate runs with no journaling, the freeze likely caused that part of the filesystem to be corrupt (unreadable), and with no journal to playback, it is not fixable. This is why the sensors dont work and why you cant run the calibration. This is just my conjecture though...

Personally, I run with Journaling on when messing with heavily modded ROMS like Syndicate. All ROMS are in a pretty rough/growing state right now since Froyo hasnt been out that long. Something like ACE or midnight I could see running without journaling (ACE doesnt have a version w/ no journaling I dont think; Midnight Rom v5 does) as they arent super heavily modified...

 

[slwelsh]

I would wait for a dev to confirm this, but every time Ive seen "I/O error" (Input/output error), it has been due to a corrupt filesystem.

I suspect you are right. Further examination reveals that "ms3c_yamaha.cfg" shows up in a vanilla "ls" command, but if I do "ls -l" it does not (I thought it might be a permissions issue). That suggests file system badness.

Since Syndicate runs with no journaling, the freeze likely caused that part of the filesystem to be corrupt (unreadable), and with no journal to playback, it is not fixable....
Personally, I run with Journaling on when messing with heavily modded ROMS like Syndicate. All ROMS are in a pretty rough/growing state right now since Froyo hasnt been out that long. Something like ACE or midnight I could see running without journaling (ACE doesnt have a version w/ no journaling I dont think; Midnight Rom v5 does) as they arent super heavily modified...

I will look into getting journaling turned on when I get this running again. I know I saw the how-to on that earlier in the thread.

In the meantime, can someone tell me how far back I have to go here? Wipe 3x, re-flash, and restore from backup, or do I also need to reload CWM?

-Sean

 

[GSF1200S]

I suspect you are right. Further examination reveals that "ms3c_yamaha.cfg" shows up in a vanilla "ls" command, but if I do "ls -l" it does not (I thought it might be a permissions issue). That suggests file system badness.



I will look into getting journaling turned on when I get this running again. I know I saw the how-to on that earlier in the thread.

In the meantime, can someone tell me how far back I have to go here? Wipe 3x, re-flash, and restore from backup, or do I also need to reload CWM?

-Sean

No need to reload CWM. Most people will say to be absolutely safe, odin back to EC05 rooted/deodexed, then flash Syndicate, but Ive had no issues just doing wipe data 3x, wipe cache 3x, reflash.

By the way, a relatively simple way to enable journaling is to make a backup of your setup, then restore it with CWM. If I remember correctly, this should enable journaling. Hopefully a dev can confirm this..

 

[slwelsh]

No need to reload CWM. Most people will say to be absolutely safe, odin back to EC05 rooted/deodexed, then flash Syndicate, but Ive had no issues just doing wipe data 3x, wipe cache 3x, reflash.

Update: Looks like just wiping data ("factory reset") in CWM and rebooting cured the sensor problem. Did not need to reflash the ROM.

By the way, a relatively simple way to enable journaling is to make a backup of your setup, then restore it with CWM. If I remember correctly, this should enable journaling. Hopefully a dev can confirm this..

I thought that's what I'd read, too. I should be good to go, then, since after the wipe I restored my latest backup with CWM. Got back almost everything.

-Sean

 

[gitit20]

Update: Looks like just wiping data ("factory reset") in CWM and rebooting cured the sensor problem. Did not need to reflash the ROM.



I thought that's what I'd read, too. I should be good to go, then, since after the wipe I restored my latest backup with CWM. Got back almost everything.

-Sean

So i just backup with cwm then restore it and that turns it back on?

 

[gitit20]

Thanks, again.

After some more research I think I found the cause: turning on WiFi tether with 4G already enabled is apparently known to crash the phone, followed by the aforementioned FCs on Services Framework, Swype, and maybe some others.

Re-flashing now. First I did a "manufacturer's reset" as outlined here:
Fix GPS on Froyo (EPIC 4G) | PaulSpoerry.com
because my GPS was still losing lock even after the SRF flash. That seems to have also taken me back to RFS so CWM is converting again.

I'm hoping I'll have no further issues assuming I can remember not to launch Tether with 4G turned on. I will file a bug report on that, too, if it has not been filed already.

-Sean

You should get in to the backup habit using cwm its your friend saves a lot of set up time... also my back up pro is nice because it works with most roms i back up about once a week delet the old one so i don't wast a lot of space...

Get it set up the way u like it back up then if u get a crash u just restore it

 

[bdog421]

So i just backup with cwm then restore it and that turns it back on?

That is correct, there are other ways to verify, but if you use sQlite(file system benchmark) before and after you will see a speed difference of about 25%. You can also remove it by flashing a no journaling rom over it.

 

[k0nane]

I started just flashing addons 1 at a time to identify the cause and it seems that the AOSP lockscreen thats posted in the Syndicate thread was causing some issues for me. I used the on posted for Bonsai and it seems to be working...for now at least

Did you wipe cache and dalvik-cache after flashing the addon? Did you try re-downloading it? Did you try "fix permissions" in CWM? Others have had no issues with the addon, it's odd it wasn't working for you.

Found this post on XDA Developers if anyone was wondering about a solution to this. Loading the mediauploader.apk to /system/app does fix this issue.

Thanks for the heads up, I might have missed this post on XDA (sometimes it's hard to keep up, especially overnight, but Impaler does a great job handling support and usually passes issues on to me). I'll either post an addon, or include this in 1.1.1.

Deffinatly a great ROM. I've been running it for about a week with no issues at all. My wife won't let me "play" with her epic which is running stock EC05 because she fears that something might mess up. Now I find her using my phone alot because "it's so much faster" I think it's only a matter of time before she is running SyndicateROM.

-Wes

Thanks for your support!

Bottom line I'm so sick of fc's, we just never had these type of problems prior to CIQ removal. You really had to goof something to start popping fc's. Now it seems like whenever it decides its time to screw up it will do so.... Not happy at all... Almost forced into going back and running EB13 pre-CIQ removal ROMs. :'(

Paul, while I hate to correct a long-time adviser in public... Your problems have absolutely nothing to do with CIQ removal. What you've experienced is classic symptoms of data corruption due to journaling being off. You are one of the unlucky ones - but one of the unlucky ones that gets hit with data corruption when something crazy happens (like a battery pull).

I can say with absolute certainty that CIQ's removal does not, will not, and cannot produce instability. I can say this with such certainty because of the process I went through to remove it. Most of the code for the IQ agent itself was located in framework.jar, in a subdirectory of com/carrieriq. The rest was in ext.jar, also under a subdirectory of com/carrieriq. Any other code was references to it in framework.jar, services.jar, DialerTabActivity.apk, and a single reference in ext.jar.

These references, calls to the IQ service, were hooked in everywhere - as you can see in the third post of the XDA thread - but they were mostly tacked on to the end of methods, or in the middle of methods. The calls were essentially "call an instance of the IQ agent, and send this piece of personal information to it". They didn't affect the functions of other items around them. During the first removal process, with SyndicateROM Frozen 1.0, there was trial and error involved. First, I tried removing the native libraries. Doing that would hork the boot process. Then, I was digging around, and located the actual IQAgent service (which, ironically, is less horrid than the 'client' part) in framework.jar. I removed that, but got errors during the boot process, and found some things didn't really work. So I went back and, long story short, fished the rest out.

These modification's can't produce FCs or other issues on their own unless I - or whoever created the ROM; Bonsai did the mod themselves (I can't speak to the completeness or efficacy, but read on and you'll see why it must have worked) - screwed something up in the process. If I did, everyone would see it. I wouldn't even let that escape my local PC, however - I've gotten the mod down to an exact enough science that with 1.1.0 I did it in only around an hour.

So if you ever face oddities again, hook up to logcat. Unless you see "iq" somewhere in the log (other than android.iqd, an empty shell of a process that takes no resources and no CPU time, and will only show up at the beginning of a log during the boot process - hop on IRC for an explanation)... your issues have nothing to do with CIQ's removal.

Sorry for the book.

Has anyone developed a work around or confirmed that this is an issue with the rom across the board?

Please see the quote above.

Not sure really... I've never successfully ran a CIQ removal ROM past the 2 days mark yet without FC's coming into play and requiring a full reflash of the ROM.

See above.

I wonder what the difference is - I've been running Syndicate 1.1.0 since it was released and haven't had a problem. I even locked up my phone a few times by getting a little overclock-happy and no data was corrupted.

The difference is that you're one of the lucky ones like me that have to try pretty darned hard to get data corruption on a no-journal ROM. I've done the crazy things that are supposed to cause corruption, but never got any.

Paul, and anyone else with corruption issues - when you've got a cleanly-working system, just take a Nandroid backup and restore it right after. You'll be converted to a journaled file system. There will be a journaled option in 1.1.1.

when is the next syndicate update coming? i noticed 1.1 was released 3/27 so i dont want to deal with the process unless another one wont be out for awhile.

Go ahead and flash. We'll have an update soon enough, but do go for 1.1.0. You'll be glad you did.

Today I had a freeze while in Google Navigation, right when I rotated from vertical to horizontal. No choice but to pull the battery.

After reboot, the tilt sensors are no longer working. I have no screen rotation, and the GPS Status app shows zero tilt in any direction no matter how I move the unit. <snip>

EDIT: I see you've solved this issue. On the 4G + Tether issue, I wish I could do something about it, as it's a real pain, but it's a bug in Wireless Tether itself. The author is aware, but is limited right now without an Epic to test with.

Something like ACE or midnight I could see running without journaling (ACE doesnt have a version w/ no journaling I dont think; Midnight Rom v5 does) as they arent super heavily modified...

For what it's worth, midNIGHT is a modified version of Bonsai, and Bonsai is modified almost as much as SRF.

Admins: Please, please, PLEASE add a multi-quote feature! It's a real pain to quote all of these, across multiple pages, by copy-and-pasting, then back, then copy-and-pasting...