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

[freeze]

Changing the boot animation is fine. Trust me all devs expect their ROMs to be modified in one way or another...

You need to use a a root level access file explorer.

Root Explorer is available from the Market for a few bucks.. Nice program and user friendly.

Ghost Commander (I just was informed of this one thanks, Chris41g!) is free from the Market.

You can then navigate to the "system/media/" location and then first rename the existing bootanimation.zip to "bootanimation.bak" so you can restore it if you like at a later date. Then you can copy and paste a new bootanimation.zip into place of the existing. You will have to enable the system to "Read/Write" instead of the default "Read Only" so you can make the changes.

Root Explorer has a button on the top upper right corner I believe to make the change, and Ghost Commander on the very bottom row of buttons scroll to the right until you see "Remount /system". Hit that button to select "RW" mode.

Of course the above is only needed if you can't find a "Flashable" boot animation.

I had incorrectly assumed that the Adao File manager was capable of this. I installed Ghost Commander and was able to replace the animation once I figured out where /sdcard went (it disappeared and I had to use the real directory - /mnt/sdcard).

Thanks for the help (again).

 

[StoneRyno]

It's just listing widgets that are installed, not that are running, unless you're running all of those.

That's the thing they aren't being used on any of my launcher pages. But they are in the processes list and memory is freed as a result of selecting them to be killed. Sorry if my previous post was confusing. This is what had me confused on the stock ROM and I never could get anyone to answer as to why stuff that is not being used runs in the background. Sometimes apps I haven't even opened after a reboot show up as running processes at some point. For example music player, firefox and read it later. Other things like voice search and voicemail will remain in the processes list after closing the app. Like I mentioned before though this ROM removed due to removal of bloatware most of the processes that insisted on running. So I'm quite happy with what I have so far.

 

[jrz5024]

That's the thing they aren't being used on any of my launcher pages. But they are in the processes list and memory is freed as a result of selecting them to be killed. Sorry if my previous post was confusing. This is what had me confused on the stock ROM and I never could get anyone to answer as to why stuff that is not being used runs in the background. Sometimes apps I haven't even opened after a reboot show up as running processes at some point. For example music player, firefox and read it later. Other things like voice search and voicemail will remain in the processes list after closing the app. Like I mentioned before though this ROM removed due to removal of bloatware most of the processes that insisted on running. So I'm quite happy with what I have so far.

I wouldn't worry too much about those background processes. Froyo's memory management is pretty excellent, and it'll kill what needs to be killed automatically.

 

[traumahawk]

new glitch

So I am using SRF 1.0.1 (i do NOT like 1.1, every install i've tried, every setup, has horrid battery life, and is wrought with bugs) and have been doing so for a while now. Today i went to do a google search for my old highschools phone number. The search feature worked, but as soon as it opened the browser the screen started to change colors. It looked like it suddenly lost power (battery life was @ 81%), and the screen changed to a greenish/redish hue with horizontal lines through it. it faded to black quickly, within probably 10 seconds- and ended up being black with dark gray lines across it. had to do a battery pull / cwm cache wipe to fix FC's. hasn't repeated... but was definitely weird. any ideas what happened???





(this just makes me even MORE eager for ACE 2.0)

 

[k0nane]

So I am using SRF 1.0.1 (i do NOT like 1.1, every install i've tried, every setup, has horrid battery life, and is wrought with bugs) and have been doing so for a while now. Today i went to do a google search for my old highschools phone number. The search feature worked, but as soon as it opened the browser the screen started to change colors. It looked like it suddenly lost power (battery life was @ 81%), and the screen changed to a greenish/redish hue with horizontal lines through it. it faded to black quickly, within probably 10 seconds- and ended up being black with dark gray lines across it. had to do a battery pull / cwm cache wipe to fix FC's. hasn't repeated... but was definitely weird. any ideas what happened???

Sounds like a hardware oddity. And as far as 1.1.0... there are no bugs (outside of the kernel, and even those are individual devices, not the software itself), except the browser Save As issue. Any issues during the install process can be resolved, and we'd be happy to help get them taken care of for you.

 

[traumahawk]

im thinking all my problems might be an individual device thing. nothing i've tried has fixed everything. i WISH it did. SRF has so many big fans. IDK if what i do to the zip before flashing screws it up (i want my theming, and and its easier to actually bake it all right into the "fully loaded" zip before flashing rather than make a seperate cwm3 zip, including the pngs, audio files, boot/shutdown animations, launcherpro v.0.8.3, and a bunch of applications) 1.0.1 works great. I actually thought i was on 1.0.2 (i WAS, musta mixed up which file i used last time i changed my theming). Just have HORRID luck with 1.1. ::shrug:: i'll definitely be giving 1.2 a try whenever that comes out... although whatever rom i'm using- be it ACE, SRF, Bonsai, or some other, will not even look remotely like what it originally was. i theme the hell outa stuff haha. Its either my device or i'm messing up a file(s) somewhere.

on a good note- the fcs when somethin happens, is a real easy fix. just wish all my apps would actually run on 1.1. (or 1.0.1 too for that matter. fixed weatherbug somehow, but still cant get tapatalk to work)

 

[Paul627g]

im thinking all my problems might be an individual device thing. nothing i've tried has fixed everything. i WISH it did. SRF has so many big fans. IDK if what i do to the zip before flashing screws it up (i want my theming, and and its easier to actually bake it all right into the "fully loaded" zip before flashing rather than make a seperate cwm3 zip, including the pngs, audio files, boot/shutdown animations, launcherpro v.0.8.3, and a bunch of applications) 1.0.1 works great. I actually thought i was on 1.0.2 (i WAS, musta mixed up which file i used last time i changed my theming). Just have HORRID luck with 1.1. ::shrug:: i'll definitely be giving 1.2 a try whenever that comes out... although whatever rom i'm using- be it ACE, SRF, Bonsai, or some other, will not even look remotely like what it originally was. i theme the hell outa stuff haha. Its either my device or i'm messing up a file(s) somewhere.

on a good note- the fcs when somethin happens, is a real easy fix. just wish all my apps would actually run on 1.1. (or 1.0.1 too for that matter. fixed weatherbug somehow, but still cant get tapatalk to work)

You say your flashing the SRF 1.1.0 after you have already done modifications to it. I would first try and flash it "stock" or untouched and see how things go for a few hours even a day. If it works without issue then it is something your doing in your theme changes. This way you can eliminate problems with ROM/device/theme changes step by step.

As k0nane makes VERY clear in his OP at XDA, any theme changes must use the apps, etc. must use the same signature in order to not interfear/cause conflicts. Basically you need to pull the apks from Syndicate and theme those to minimize any chances of problems. Using older themes and stuff pulled from other older ROMs will run you into trouble.

@k0nane, if your reading this check your PM !

 

[traumahawk]

As k0nane makes VERY clear in his OP at XDA, any theme changes must use the apps, etc. must use the same signature in order to not interfear/cause conflicts. Basically you need to pull the apks from Syndicate and theme those to minimize any chances of problems. Using older themes and stuff pulled from other older ROMs will run you into trouble.

@k0nane, if your reading this check your PM !

::sigh:: so i cant mod/bake in apks from the market/internet and use them on here? and the themes i use arent really themes. i just change png files. i have the unlock button from blackout, the stat menu icons from frankenstein, custom stat window (i made .png files in the gimp), edited the srf1.1 dialer tab to have the colors i wanted, edited the srf 1.1 market to have a blue icon, edited the srf1.1 mms apk to have transparent background and bubbles, changed the font. etc etc etc. not using any theme as a whole. all i did was change pngs, and add a few files (audio and such), and bake in dolphin hd, setcpu, astro, sdx app remover, blackfacebook, xda, android central, tapatalk, and amazon appstore so they install when i flash the rom (and remove stock browser and email apps, as i use dolphin and gmail)

 

[Paul627g]

::sigh:: so i cant mod/bake in apks from the market/internet and use them on here? and the themes i use arent really themes. i just change png files. i have the unlock button from blackout, the stat menu icons from frankenstein, custom stat window (i made .png files in the gimp), edited the srf1.1 dialer tab to have the colors i wanted, edited the srf 1.1 market to have a blue icon, edited the srf1.1 mms apk to have transparent background and bubbles, changed the font. etc etc etc. not using any theme as a whole. all i did was change pngs, and add a few files (audio and such), and bake in dolphin hd, setcpu, astro, sdx app remover, blackfacebook, xda, android central, tapatalk, and amazon appstore so they install when i flash the rom (and remove stock browser and email apps, as i use dolphin and gmail)

Try my suggestion. Flash it stock.. Run it for a while to verify things are okay. Then I would slowly add things.. Something is causing your troubles and its got to be in something your adding in from the start. I know its a pain full process by one by one you will eventually find your problem.

Plus improperly themed pngs can cause FC's. I know modding 9.pngs. can be very tricky over the normal .pngs..

 

[traumahawk]

. . . improperly themed pngs can cause FC's. I know modding 9.pngs. can be very tricky over the normal .pngs..

had no idea there were different types of .pngs . . .

everything i've edited in gimp has been saved and dragged into the archives as a plain old .png file. and i haven't looked to see if anything i'm swapping is 9.png or .png. that's a whole new element to theming i wasn't aware of.

 

[StoneRyno]

I wouldn't worry too much about those background processes. Froyo's memory management is pretty excellent, and it'll kill what needs to be killed automatically.

I wasn't worrying about it too much. The only reason I realized this stuff had processes running was because when the software gets laggy I check and see that a handful of these processes were started. It will get laggy about a dozen times each day and I manually kill the previously mentioned processes and then the lag goes away until something loads those processes again. I was rather hoping there was a way to stop them before they even get loaded since they are things I likely will never use in the case of widgets I don't find useful for apps I use.

[snip] has horrid battery life [snip] the screen started to change colors [snip] to a greenish/redish hue with horizontal lines through it. it faded to black quickly, within probably 10 seconds- and ended up being black with dark gray lines across it. had to do a battery pull / cwm cache wipe to fix FC's. hasn't repeated... but was definitely weird. any ideas what happened???

Sounds like a hardware oddity.

I'm inclined to think something got corrupted like perhaps during the flash or something. Or worse the screen hardware is failing though not as likely if the problem doesn't recur regularly. I've also noticed that FCs tend to result from something having gone wrong during flashing or from restoring data from a backup. Or I assume residual data which is why, I assume, it is recommended to wipe the data and caches 3 times. In my case when I first flashed to syndicate ROM and restored my data for various things from SMS to 3rd party apps I suddenly got all sorts of FCs from stock apps like messaging, calendar, etc. I reflashed and installed all my apps again the same way I did before but this time restore the SMS data etc from a redundant backup. I used both mybackup root and titanium backup. Which turned out to be the wise thing to do. I don't remember which ones data backup caused the FC issue.

 

[traumahawk]

I'm inclined to think something got corrupted like perhaps during the flash or something. Or worse the screen hardware is failing though not as likely if the problem doesn't recur regularly.

i do the wipe 3x data/cache/dalvik everytime i put new rom on, even if the update says not necessary so thats not the issue. that whole "screen hardware failing" thing has me worried tho. if this happens.. i should be able to odin back to an untouched stock and have them replace phone still right?

 

[sandman512]

Decided to reflash the ROM so I can have a fresh start. Well, reinstalled the ROM and it is EXTREMELY slow, as in noticeably slower. So, I wiped 3x and reinstlalled it again, STILL slow. PLease, any advice? THANKS!

 

[StoneRyno]

i do the wipe 3x data/cache/dalvik everytime i put new rom on, even if the update says not necessary so thats not the issue. that whole "screen hardware failing" thing has me worried tho. if this happens.. i should be able to odin back to an untouched stock and have them replace phone still right?

According to the documents that came with mine the warranty is 1 year so if it is still under warranty that is an option. Also if you have some form of insurance (sprint or 3rd party) and it isn't under warranty then it can be replaced under the terms of the insurance.

 

[ragnarokx]

Decided to reflash the ROM so I can have a fresh start. Well, reinstalled the ROM and it is EXTREMELY slow, as in noticeably slower. So, I wiped 3x and reinstlalled it again, STILL slow. PLease, any advice? THANKS!

Format your SD card.

 

[k0nane]

Format your SD card.

And wipe data before reflashing.

 

[k0nane]

i do the wipe 3x data/cache/dalvik everytime i put new rom on, even if the update says not necessary so thats not the issue. that whole "screen hardware failing" thing has me worried tho. if this happens.. i should be able to odin back to an untouched stock and have them replace phone still right?

Any screen-related issues have absolutely nothing to do with this ROM or kernel. If you do have issues, yes, Odin will do the job.

 

[kevincwelch]

LauncherPro 0.8.5

Does anyone know if the bookmarks widget for LauncherPro 0.8.5 causes the same force close issue that was present with earlier versions of LauncherPro and SRF/TW? I really liked the bookmark widget, but did not particularly like the endless FC windows...

 

[dtm_stretch]

Does anyone know if the bookmarks widget for LauncherPro 0.8.5 causes the same force close issue that was present with earlier versions of LauncherPro and SRF/TW? I really liked the bookmark widget, but did not particularly like the endless FC windows...

I just tried this and got an FC Loop, restoring a back up now. I didn't even know this was an issue. I am on .8.5. Definitely DO NOT use the bookmark widget from launcher pro.

 

[scoots77]

Love the ROM.

Just noticed that my battery popup still occurs, with a really loud audio tone as well. My battery isn't typically so low, so I'm just now noticing it.

I thought the battery popup had been removed a few versions ago.

Keep up the good work!