yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] Custodian:
A whole lot of rah rah going on in " ACS " dens nowadays...what gives? I mean first it was thomas's latest kernel that got literally skinned and flammed without seasoning by 5 dfferent nerds making " omfg herpity derpity derp derp vision 1.2 stole my virginity and gave me herpes " threads in general/q&a...now we have muslims that believe in aliens and chatholic koreans that don't eat pork throwing stones and calling SRF a curse on their phones...what gives? Hell, read the disclaimer at the beginning of the threads and understand that when they say " we will laugh at you for blameing us" they mean that ****.....and hell, I'm leaving the liquor store right now with a 12 pack of carona and a few dutches(wth?) Anyways..... /senseless bickering off
[Epic 4G Android Development] kynetx:
Thanks for coming forward with this despite the "if you don't have anything good to say, don't say anything" attitude. This explains the runaway software rot I've been having on this ROM despite maybe a handful of bad dismounts, all of which were due to lockups and spontaneous reboots.

I was gonna bail anyway, but it's nice to know what the source of the problem is so I can avoid it in the future.
[Epic 4G Android Development] Nerva:
Sorry, I'm new to Android -- how do I install the 24hr fix?
[Epic 4G Android Development] spyder09:
i am patiently/eagerly awaiting the new update :D

k0nane did you ever get a new phone in? samsuck and their lack of customer support all around haha wouldnt be supprised if you havent got it yet

btw still loving this rom and still trying to figure out a few of my themeing questions

2d 2h 5m 18s since unplugged and i dont think i had it at 100% when unplugged...only down to 26% :) love this rom

display has been on for 2h 22m 15s :)

data mode is disabled btw and a few services stopped that isnt used
[Epic 4G Android Development] theimpaler747:
Flash it from recovery.
[Epic 4G Android Development] qbking77:
Go to the second post, download the 24 hour fix, and put it on your sd card. Then boot into clockwork, power off - volume down camera button and power button at same time... And then just flash the 24 hour fix zip through clockwork and reboot.
[Epic 4G Android Development] tclarkey:
Your posts have been noted and responded to by the developers.

Please put your soapbox away so we can all move on with our lives.
[Epic 4G Android Development] jockovonred:
i have a friend and he is a tool. there's no way a guy like him (my friend) or any other who isn't the least bit able to do their own work and search on a

developers

forum should be allowed to modify anything (without a great deal of hand holding). hand holding aside, i reserve that for my children.

key word: nandroid
[Epic 4G Android Development] noisuf0:
having an annoying problem.. other than this, i love the rom.

my bottom 4 essentials won't work. the touch sensitive buttons under my screen don't work right. the menu button works, the back button works ( but the back button has no haptic feedback for some reason ), but the home button has haptic feedback but doesn't do anything or hold(for task management) and does not respond at all(aside from the haptic feedback). it doesn't take me home no matter what.

if I can't figure this out by tonight I'm gonna try something else I guess, but it's a real bummer. like it a lot.

any suggestions?
[Epic 4G Android Development] mystica555:
I just hope it gets fixed. *waits patiently*
[Epic 4G Android Development] Nerva:
Thanks.

I see there are four other addons -- should I install them as well?

"Removed Stock Apps" -- I briefly looked at these before installing SFR. Are any of them worth a damn? Am I missing anything?

"AOSP Lockscreen" -- Am I right in understanding the tradeoff is the AOSP has volume control, while the Epic 4G lets you go directly to text messages and voicemail? Do most people prefer one or the other?

"Network Name to Sprint (fix bloat apps)" -- I'm going to make a wild guess and say this allows Sprint-specific apps like TeleNav to work? Is there a reason not to install this one?

"Lockscreen Date Fix" -- This sounds like an easy "yes" but is it for one lockscreen or both? Is there a reason not to install this?
[Epic 4G Android Development] theimpaler747:
Honestly, sounds like a phone issue. ODIN back to stock and see if it works.
[Epic 4G Android Development] theimpaler747:
Only if you'd like to ;)
[Epic 4G Android Development] jockovonred:
Removed Stock Apps - contains apk removed by ROM in case u need something that's not in the full version

AOSP Lockscreen - different lock screen

Network Name to Sprint (fix bloat apps) - in case u use sprintTV, NFL stuff or samsung apps requiring the network name to be the original value

Lockscreen Date Fix - for months that end in Y
[Epic 4G Android Development] stir fry a lot:
Waiting for you to make a proper rom of your own #notholdingmybreath
[Epic 4G Android Development] mystica555:
Should I, instead, have lied and said that I indeed do own such a device, and I myself had these issues? Would this have prevented the rude comparison to your 'tool' friend comment?

Ah the truth seems to never get me anywhere.

Nandroid is fine. But who keeps preemptively nandroiding their phone every day just in case it crashes that day? Like, wake up at 6am, power on the phone, nandroid, go thru the day, it crashes, oops lost all that days work but not the rest of the days inbetween flashing.

This is an exercise in futility.

I've been using Cyanogen firmware on my phones for a long while whereas my friend just got into the Android thing late last year. He considers me a go-to geek when he can't figure stuff out.

(His initial descriptions of "just playing music and then it stops playing and then nothing works" also confused me until I looked further into it)

After he tried everything your forum here has mentioned, he was at an entire loss. Every other day during random chats "I had to reflash my phone, the permissions screwed up." and I kept telling him "what are you doing wrong, why does this only seem to happen to you".

I finally discovered the root failure point being unclean dismounts.

If I jumped the TMobile ship and went back to Sprint and bought myself an Epic4G and tried your ROM myself, the message would have been the same. I may have had even more to report having used it personally...
[Epic 4G Android Development] mystica555:
I just might make an exact clone of this rom with e2fsck just to spite all you jerks.

Hell, screw it; If the next one that comes out doesn't have e2fsck, plan on this. I'll give credit where credit is due, link back to this forum, and promise not to change a single thing but add in e2fsck. I'll even give you a patch.

Its just not my concern yet, as I have provided the info on why things are dying, and will wait to see what the devs do with it.

But damned if I will sit by and allow another iteration of a flaky rom that could be fixed VERY EASILY to sit around unfixed.

*You've enabled the "Mike is now annoyed with idiocy" mode.*
[Epic 4G Android Development] jockovonred:
point = missed; nandroid isn't a daily thing. titanium backup or mybackup root would be a daily. the answers you seek are within...

tools are tools, in all shapes and sizes. my friend also comes to me because he's too lazy to do the work himself. it's not rude, it's just what they are...also it sounds like he missed a few posts where the answers exist.
[Epic 4G Android Development] tclarkey:
- OR -

You can keep your pompous attitude in TMO-land and shut the hell up.

- OR -

You can tell your friend to uninstall the ROM and shut the hell up.

- OR -

You can go ahead and create your own ROM on some other forum and have a whopping user community of 2, you and your friend, and shut the hell up.

Bottom line is JUST SHUT THE HELL UP!
[Epic 4G Android Development] noisuf0:
tried it. works fine on anything but the syndicate rom. and now the lock screen is gone. it just goes on or off without any lock screen. sigh. maybe i'll just go back to the old viper rom i had before :[
[Epic 4G Android Development] jockovonred:
custom lockscreen? or using the lockscreen with the pattern to open? reset the lock screen in the settings and see if that helps.
[Epic 4G Android Development] DrKaotica:
Haven't been on xda all day #rareoccurance

Troll alert on acs haha!

Don't lecture the devs plz.. make a suggestion.. and leave it at that.. good lord

sent from the couch most likely..
[Epic 4G Android Development] mystica555:
:D *ROFL* your amount of anger is amusing.

It'd be on XDA, just a different thread. Meh, forum/thread/topic... I go through so many dumb online bulletin boards the names escape me sometimes. Just a repackage with a missing useful feature. I'd plop it in a thread, link back to here and say "this one won't crash as much randomly on you, here's why, try it instead".
[Epic 4G Android Development] mystica555:
Sent from my desk actually. No room in my home-office for a couch.

.. er was that your signature? ... doh.
[Epic 4G Android Development] DrKaotica:
Try starting from scratch.. odin to ec05, flash sfr 1.1.0, restore your apps see if that helps, its amazing the things that will fix haha.. if that fails maybe reflash the twilight kernal over sfr that has fixed a few things for me too (don't ask me why)

sent from the couch most likely..
[Epic 4G Android Development] MysteryEmotionz:
Its one thing if you made a suggestion. you came here demanding things like your barrack obama.

Tell your friend to enable journaling if he's having data corruption issues.

Journaling wasnt disabled for any performance gain. That was a side effect. Journaling was turned off to save life on the onenand chip. Less writes less wear n tear. Some of us may keep are phones longer then 2 years so nand life is important. running a e2fsck on boot up is point less. It defeats the purpose why journaling was disabled in the first place.
[Epic 4G Android Development] stir fry a lot:
I've ran every iteration of this rom since froyo was leaked without any issues. Perhaps you're the idiot.
[Epic 4G Android Development] mystica555:
And e2fsck would preclude the absolute requirement to always keep backing up crap daily just because of a random failure waiting to happen...Defense in depth, not pulling at straws because the real problem isn't fixed.
[Epic 4G Android Development] mystica555:
Actually, it definitely does *not* defeat the purpose. As I have said about 3 or more times now, *if the filesystem is clean, fsck replays the journal. JUST LIKE A NORMAL MOUNT.*

If it is dirty, it gets FIXED, versus being MOUNTED UNCLEAN.

You only expend slightly more data by moving a few blocks to fix it.
[Epic 4G Android Development] mystica555:
Or maybe you're just lucky? I won't discount this possibility.
[Epic 4G Android Development] jockovonred:
daily backing up is user preference...some do, most don't. however those that do, do it because they want journaling disabled.
[Epic 4G Android Development] MysteryEmotionz:
If the the fs is dirty and needs to be cleaned it means it has to write to the nand. Its data corruption where suffering from a un safe dismount that is easily re-pairable from restoring a back up from titanium backup.

Personally my phone backs it self up at 4am every day with tb. If I ever ( I don't ) I restore the data from the backup.
[Epic 4G Android Development] stir fry a lot:
I don't think this would be the #1 rom if everyone were experiencing the same problems your friend is. I sure as hell wouldn't be as stability is my #1 priority. Just because you're an idiot and can't figure out how to enable journaling does not mean that this is a crap rom.
[Epic 4G Android Development] mystica555:
And titanium backup will write back probably as much data from the restore process. As will a nandroid restore.

Simply put: fsck scans the drive in read-only mode, finds errors, and fixes perhaps 5 or 10 inodes that are bad. This to me seems much less wasteful than a full nandroid restore or even a largeish backup restore.
[Epic 4G Android Development] mystica555:
And this misses the ever-present possibility that journalling can sometimes still fail and leave the disk in an unclean state.
[Epic 4G Android Development] MysteryEmotionz:
It is gonna write back less data if you just select the apps that are fc. No need to restore everything.
[Epic 4G Android Development] stir fry a lot:
This rom comes preinstalled with MyBackup Root. I have it scheduled to make a backup evry morning at 4am just in case but I have never once found the need to use it nor do I believe a majority of the users of thi rom have. If they can turn this from a 99.5% perfect rom to a 100% perfect rom because of your suggestions then more power to you. At this point however my phone has been 100% perfect and you're just making an ass out of yourself by coming in here so hot when there really isn't even an issue.
[Epic 4G Android Development] DrKaotica:
sent from the couch most likely..
[Epic 4G Android Development] mystica555:
And how big is an app? 500K to multiple megabytes? How big the broken set of inode table entries? maybe 50-100 actual problems i am guesstimating, writing a few K to the inode table to fix each. On rare occasion does data get physically copied from one point to another.

I still think fsck is going to be less writes than even as few as 3-4 apps being restored.
[Epic 4G Android Development] mystica555:
Nice choice! I love ST:TNG!

"...Only question I ever thought was hard, was 'Do I like Kirk or do I like Picard...'" :p
[Epic 4G Android Development] MysteryEmotionz:
In general its usally 1 app. What ever app that was currently up front during the up proper dis mount. It can be. As minimal as 1k depending on app
[Epic 4G Android Development] soundman1024:
I did as advised. ODIN to EB13, OTA to EC05, CWM3.0.0.6, EXT4 and wiping 3x, flash Syndicate (re-downloaded) from a freshly formatted microSD. Same issue. Blue text happened, then on 1st boot I got Android with the glint flashing over Galaxy S, both animated. Phone got caught in a boot loop. Battery pull, wipe 3x, re-flash Syndicate, get blue text again, but the flash goes further and it shows that it flashed the Kernel. 1st boot with Syndicate logo failed, phone looped and on 2nd boot succeeded. This time everything seems to be working, and the battery life is fantastic!

Does it sound like everything went normally?

Possibly worth noting, I had the blue text with CM7 Alpha 1, but not with Alpha 4. Perhaps one of those developers knows something? I got my phone on launch day, so if the hardware has changed at some point I have the older hardware.
[Epic 4G Android Development] mystica555:
And its that "depending on" that again could be a lot more. The filesystem really does need to be fixed upon rebooting, because even some of the non-android-apps, the core linux level stuff, could still have sporadic issues.

Your solution is still akin to putting a band-aid on a chainsaw wound. It may just nick the surface, or it may cut your entire arm off; If it nicks the surface, the cut can still be pretty long.. That one band-aid may not cover it all.
[Epic 4G Android Development] Nerva:
Thanks.

Sorry -- yet more questions...

Can I flash all of them in sequence, or do I need to reboot after each one?

If I install the stock apps, can I uninstall them again later?

What is the network name without the "Network Name to Sprint" addon? Is there an advantage to not having the Sprint network name, or is it just a style thing? I've heard about Google market filtering certain apps based on who your carrier is -- does not having the Sprint network name allow me access to more apps in the market?
[Epic 4G Android Development] dreamsforgotten:
The main reason or two actually, that your arguing with the users (besides MysteryEmotionz) in the thread and not k0nane are as follows:

1. The dev is working on the next release with journaling enabled by default. Its a pain in the ass on our phones because the method our update zips format the partitions aren't as advanced as a program you have run on a true linux server and the partitions behave in and unpredictable manner after the flash (which have just been resolved btw.) We are testing the beta now and its spectacular so instead of giving credence to your comments and I'm waiting post hes actually getting **** done all without his device to even work out the issues.

And

2. This has all been discussed both the fact the update will be journaled and the developer tools will be included in the bin this time. Instead of repeating himself hes putting in work. He doesn't even have the time to stop and tell you about the search feature you bypassed if you didn't want to look back a few pages and see the repost from impaler explaining the same thing before you started trying to convince him, the users, or yourself you had the miracle cure for the downfalls you believe the rom has. His device went down shortly after releasing the current update so your concerns have been addressed repeatedly before you made your first post. This device, its mounts, and the os are a different animal than the unix servers of 96. And with all that experience with unix and ocing q 6600 processors when your friend explained that listening to music on a 1.3 oc kernel and it kept freezing, the first advice you should have given him was that he don't have a way to cool his processor generating all that heat in his pocket after the oc. obviously his phone can't handle it and he should have not returned to set cpu to continue to overclock it since by default it stays on the 1 g step.
[Epic 4G Android Development] musclehead84:
Can't wait for the update acs. Look mystica you would have been welcomed better if your attitude was better. When you come on a rom thread demanding things u know what happens. Seriously though all jokes aside if you think you can make something better than develop it. On not trying told be a smartass here I'm serious. If its something that miggr benefit everyone then I'd like to see it. Just don't demand. This rom is awesome and I haven't had any corrupt data on it. Ko and acs are top notch developers that I have a lot of respect for.

Sent From My Evo Killer!
[Epic 4G Android Development] h4kudoshi:
Aww, that makes me muy triste. :(
[Epic 4G Android Development] mystica555:
Which is better than not on by default. Still doesn't address 5 other issues:

1: barriers=0 means the journal commit may be written before the journal actually updates. This gives the journal invalid info.

2: the ext4 barrier code may (and has in the past) have bugs, so even if its on, it may not work right.

3: data=writeback also can leave random file data or old data inside the files even though the journal thinks they were written fine. This mode induces is a 30 second caching time before data is forced out to disk. Any app that doesn't fsync() will have stale/broken data.

4: The journal with its corrupted data may not properly play back at which point the system cannot continue mounting the filesystem if it tries.

5:Finally any random FS corruption by any other silent method.

Journalling by itself will not be able to fix/prevent these problems.

Actually, I did search the thread, for firstly journal: many results, often they weren't exactly what I was looking for, as journalling is secondary to fixing an error.

Impaler's post stating that journalling removes the problem is not 100% correct, as journalling alone does not address the above issues. So I searched for 'fsck' which produced 1 post from February which I don't think ever got a reply.

Then I became very bothered by the fact there was no fsck. As my sheer WTFness at a rom that's doing funky stuff with filesystems and without fsck increased, I got riled up. For this I apologize. I do admit not searching for bash/profile tweaks, as I just spent the previous 2 hours ssh'd into my friends computer, running adb shell / logcat and trying to reproduce the issue while conferencing over Skype to completely verify.

No, I don't think that between 1998 and 2011 there have been many 'groundbreaking' changes with regard to how the filesystems work. Most major filesystem semantics and even the one example of the fsck utility were written for 4.3bsd, circa the mid-80s. Sure, there are newer filesystems, but the same problems of cache and power loss flinging your data into the bitbucket have always existed and will at some level always exist, no matter how fast the storage media becomes to instantly save changes. Race conditions are fun!

At first his problems sounded like bugs in the software he was running, force quitting, crashing, as he never properly denoted 'the phone powers off'.

After this revelation the first thing I said was "Crap! your CPU is toasting."

(Yes, he's a bit terse with all the pertinent details and I am sometimes averse to dragging it out of people, but finally I had enough of listening to his neverending problems that I decided to take the initiative and dig deeper as such issues seemed extremely odd.)
[Epic 4G Android Development] siirus09:
Many of the problems found in the thread end up being bad flashes or doing something you shouldnt have without having Journaling on. The Epic 4G is just a fancy phone, not a server, it doesnt need any of the stuff you mentioned because Journaling is doing just fine. Plenty of people, if you do search the thread, few problems with the ROM that had nothing to do with what you are trying to implement. There are also many who have ZERO problems since day one, like myself.

It's hilarious how you are so appalled by something to trivial and keep wasting your time trying to change the Devs' minds. In the end, no one cares. The devs arent going to do any of what you asked so stop wasting your time. Go cook your own ROM and be on your way.

Also, your knowledge of Linux is laughable. :rolleyes:

P.S. With an ego like that, how do your "friends" stand being with you? By the way you've acted so far in this thread you must be one of those guys who pushes their so called knowledge of computers on people, thinking everyone to be stupid but you.
[Epic 4G Android Development] mystica555:
Until it doesn't. I mentioned : ram cache, which the filesystem is using. The I/O layer caches a lot of stuff. I mentioned: barriers, which indeed, can cause the journal data to become out of order. I mentioned unclean remounts causing data corruption. All of these *can* be mitigated by simply fscking on boot. Why is everyone so averse to a simple principle that your bloody desktop runs every day?

"If dirty, check it!"

Every android device with a SDcard slot has a fsck_vfat for when the sdcard gets corrupted. Yep, it fixes that for you automatically, why not let the phone fix itself too?

I'm appalled by something that should work (a phone) regardless whether or not I am using a nice rom that gets rid of Sprint's BS and works well. Its just that 1 small step from working better in more scenarios. Nobody should have to worry about data loss/corruption/apps going south every single time the phone gets rebooted unexpectedly due to any cause.

I've already committed to fixing the next release if it isn't taken care of, and giving the devs a diff.

Also, in what aspect do you consider my knowledge to be laughable? Please explain where I have errored. You can even take it private if you don't wish to clutter this already annoyed thread. I seriously am curious.

I don't think that at all, until I have a proper chance to get to know someone for a while. I start out discussing with the highest level I work at, and then if they don't understand, I elaborate, simplify, etc. I assume that such a project, an alternative ROM for a popular smartphone, would be headed up by someone who understands that filesystems need to be correct to not screw up in random ways later on. By not having fsck on the phone, I already consider that 1 step down at least from the knowledge I've gained seeing my filesystems go corrupt, die, null themselves out due to improper metadata, the whole 9 yards, and the steps I've taken and others continue to take to minimize the losses.

How do they 'stand' me? Because over time they have learned that I am passionate sometimes to a fault with what I think is right vs what isn't, and this is one of those cases.