yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] thisguy23:
Well can't say that you didn't see this coming... Is this possible for the fascinate?

http://www.xda-developers.com/android/kernel-patch-allows-force-ac-charge-for-faster-charging/
[Fascinate Android Development] ssewk2x:
I actually dug through the kernel source a little bit. It looks like our kernel is nothing like the one this patch was generated with, for starters. So it wouldn't be a matter of simply applying the patch to our kernel and BAM, nice new feature.

Second off, I dug a little deeper into the way our kernel handles charging cables, and it looks like we treat every cable the same way - meaning we should always be pulling the max charging current possible out of whatever we're connected to.

Therefore, if I've been reading the code right in the last 15 minutes, it looks like this change is not necessary for Fascinate since we already do what it intends to accomplish. If I've read our code wrong .. then it may be possible to do something similar at some point, but don't hold your breath.
[Fascinate Android Development] speedingcheetah:
Umm...the OP mentioned that "DIDLE" was the cause of the SOD's....well...somehow...i didn't read that DIDLE is actualy D IDLE...short for DEEP IDLE...I first read it as DIDDLE....sorry about that...my mistake...brain fart..

I do find it a tad confusing that the "Know Issues" so to speak... is intermixed with the Change log and not a separate section...but that is just me...and this thread is nearly 50 pages long....so bear that in mind....not everyone is going to read through everything...but i do feel stupid for overlooking the obvious in the OP...
[Fascinate Android Development] ssewk2x:
Ok. I'm in a bit of a quandary here.

I've fixed a bug I located in the ext4 filesystem code that I believe is responsible for the random failures of nandroid backups some people are seeing. Further, it can potentially cause a process to lock up any time the /data partition is accessed for reading (I hope it's only for reading, anyway). I have run this fix for a couple days now and seen a great improvement in my phone's behavior. It even seems to have calmed down the media scanner craziness a little.

The problem is I haven't heard anything from Tk or Six about what to do with this information.

I think this is important enough, though, that I should put out a quick unofficial build for people to use in the meantime. No one wants their /data partition to get corrupted, after all, and I can't rule that out as a possibility with the bug present.

Therefore, I present a build of Glitch 14 B5 for THS 6.1 ROMS. It is no different from the one you'll find in the OP except for this bug fix. It is for fascinate only. I know it works with the latest AOKP ROM (build 27).

I can't emphasize enough that this is unofficial, and I'm releasing it without permission from sixstringsg or Tk-Glitch. If either of them comes on and asks me to take it down, it will be gone.

http://dl.dropbox.com/u/28682151/Glitch-kernels/CM9-fascinatemtd-Glitch-nandroid-fix.zip

Steps:

1. flash in glitch recovery

2. reboot

If you want to make a nandroid, reboot into recovery and make it. It should work just fine now. Let me know if it doesn't.
[Fascinate Android Development] sixstringsg:
Sorry, thought that was mainly for Tk. This is fine, I'll make a public round of betas with it soon unless you get to it first. Would you like it somewhere other than your dropbox?
[Fascinate Android Development] ssewk2x:
Ok, no problem. I couldn't get all the devices to build right, so maybe you want to check out the branch and see what's up.

My dropbox would probably appreciate an alternate location ;)
[Fascinate Android Development] 123SIT:
Successful nandroid completed with the test kernel.

Sent from glitched aokp mez
[Fascinate Android Development] ssewk2x:
I'm 2 for 2 on mine :)
[Fascinate Android Development] 123SIT:
Same here and I actually wiped and restored successfully from my second nandroid.

Sent from glitched aokp mez
[Fascinate Android Development] shelby04861:
Ditto here as well on gummy mez. All worked well
[Fascinate Android Development] Stephen.k.spear:
Nice work man. I love this kernel. The whole glitch team is awesome.

Sent from my glitched aokp unicorn.
[Fascinate Android Development] htim95:
Why does this combined with the latest gummy for fassy have terrible battery life? After 2 hours I'm down to around 30% battery...
[Fascinate Android Development] Stephen.k.spear:
Have you recalibrated your battery? how long have you run the combo? What are your battery stats? How old is your battery? Have you run logcat to see if your media scanner is constantly running?

Sent from my glitched aokp unicorn.
[Fascinate Android Development] htim95:
Don't know how to recalibrate, I've run the combo for about a month, ive had the battery for about a year, the rest I don't know how to do but this only started happening when I installed ics I went back to gingerbread a while ago and the battery was fine so I doubt its the battery.
[Fascinate Android Development] Stephen.k.spear:
TW GB ? MTD Roms inherently use more battery we aren't entirely sure why.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] Stephen.k.spear:
Had a hang up on data. Wiped cache and dalvik and made it through. I feel save now. :-)

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] ssewk2x:
I noticed this as well when I made the leap to ICS. I don't even bother with stock kernels anymore and just go straight to Glitch, come hell or high water.

I believe the problem was because the media scanner process would encounter the ext4fs bug I explained a few posts back, and would consume 100% of the CPU while waiting forever on a block .. or something like that. Anyway, your best bet is to flash the unofficial kernel I posted a few posts back and use that for now. I think you'll see an improvement - I sure did!

Also, you might want to do the following after you flash the new kernel:

1. charge your battery to 100%. Leave your phone plugged into the charger for the remaining steps.

2. go under (menu)->manage apps -> media storage and select "clear data." This will wipe out all your media storage cached references (including any that might have gotten corrupted due to the ext4fs bug).

3. Reboot your phone. When it starts back up again, the media scanner will re-scan your *entire* phone. This will take a long time, probably, and eat a bunch of your battery. Be patient and let it finish. Once it's done, you should see an improvement.

Good luck!
[Fascinate Android Development] droidstyle:
you must have a rogue app installed...im running glitch with aokp 27 oc'd to 1500mhz and im at 24hrs runtime, 2hrs screen on time with 40% batt left.
[Fascinate Android Development] ssewk2x:
Oh, crap! With the unofficial kernel I posted??

Well .. now that I think of it .. it's entirely possible that something could have gotten corrupted with the older ones that would still cause the newer one to hang.

I was going to recommend minimally a cache / dalvik wipe, and possibly even a data wipe for installing the unofficial kernel because of that .. well .. now we know.

If you see that behavior again (especially if you've wiped data), please let me know, and maybe adb into it and let me see the dmesg output. Thanks :)
[Fascinate Android Development] htim95:
I wasn't running tw gb I was on cm7 with I believe glitch v13 might have been an earlier version, also the battery is terrible right after a fresh install after Odin to stock. I might try the kernal ssewk posted, how high can it be overclocked?
[Fascinate Android Development] ssewk2x:
It's the same as glitch 14 B5, but without one bug. So it can go just as high as the official Glitch 14 B5 kernel.
[Fascinate Android Development] htim95:
K, will the clear data step after I flash it literally wipe all data on my SD card like pictures and music?
[Fascinate Android Development] yonith:
So I flashed the new test build, rebooted, and then rebooted into recovery. When I tried to do the backup, it froze on backing up data. I have a Fascinate and am on THS 6.5.
[Fascinate Android Development] ssewk2x:
No, just the factory reset. Leave your sd card alone :)
[Fascinate Android Development] ssewk2x:
Did you wipe cache and dalvik?
[Fascinate Android Development] sarkozy:
Well, small update. I'm running AOKP build 27 and had no issues doing backups with the B5 kernel with AOKP for CM9. I flashed the test build yesterday and had all sorts of random lockups, so I wiped data and reflashed and all is well. Fast forward to today, tried to do a backup and it froze on /data. Wiped caches and it froze again. Argh
[Fascinate Android Development] foxfire450:
Same here with wiping cache and dalvik. Dmesg didn't show anything after it mounted the /data partition.

I also checked the /data partition's filesystem for the heck of it, but it shows to be clean.
[Fascinate Android Development] ssewk2x:
Well, back to the drawing board, I guess. I just had a nandroid failure as well.

Here's me pulling my hair out.
[Fascinate Android Development] droidstyle:
I just did a nandroid back up without wiping caches and everything worked fine. One thing I did was wipe chaches before flashing your kernel patch. For some reason on the 14.1 builds if I dont wipe both caches before flashing it will bootloop. Also not running gbbootloaders...
[Fascinate Android Development] yonith:
I did not. I thought the glitch kernel did that by default. I'll give that a shot later on.
[Fascinate Android Development] speedingcheetah:
I can not find this option...on AOKP build 27....u mean go to the setting menu...apps....or settings....storage....either of them have no option to clear data...
[Fascinate Android Development] foxfire450:
It's under System Settings -> Apps -> switch to the All tab (it's all the way to the right, you have to scroll) -> select Media Storage -> Clear data
[Fascinate Android Development] speedingcheetah:
Ah...now I understand...thank you for that clarification...
[Fascinate Android Development] droidstyle:
well it does have a cache and kernel cleaning script built in but for some reason on the 14.1 builds i get a bootloop if i dont wipe caches before flashing.
[Fascinate Android Development] speedingcheetah:
Standby Battery Life...Awesome

So...I am getting awesome standby battery life with this rom and the newest Glitch kernel...

Be warned..I have a monster of a battery...Seidio 3,000mAh....

It eats the battery when I actually using the phone...probably due to my OC settings...Live OC 105%..max step..13000mhz...so...105Mhz -- 1365Mhz

I am at 1 day 1 hour 45 min....only at 76%...that's after 2 hours of wifi tethering..and a few calls ....yesterday...

Much better battery life then when I was on CM7....

Keep up the good work guys!!...posting this in both the AOKP rom thread and Glitch kernel thread...because both deserve the praise!!

EDIT: On an other topic...I decided to try the EH03 modem/radio...speeds seem slightly less than EC09..but phone is reporting stronger signal..
[Fascinate Android Development] tonu42:
Switched over to EC09 and I noticed a 600 kbps difference in the same exact spot (on my desk). Thanks for the tip.
[Fascinate Android Development] speedingcheetah:
I am reading that as u are getting faster speeds on EC09 and not EH03....my speeds on either are crap..never going over 500kbps most of the time...

But, since flashing EH03...the phone is getting stronger signal...or at least it is reporting that it is stronger...-90's most of the time on EC09..now..in the low -80's..went to -60 in my living room...not seeing an increase in data speeds though..so I don't know just yet..going to run this for a while and see what happened.
[Fascinate Android Development] htim95:
K so I flashed ssewks kernal and wiped media data and then rebooted, I don't know what it did but when I got out of the shower it was in recovery, I hit reboot system the phone turned on and I left it plugged in until I left the house when I did I have literally a 5 minute ride and the battery is already down to 88%.

Just got in to 2nd period and its not down to 70%, battery life is even worse than before
[Fascinate Android Development] ssewk2x:
If you had read what I posted, you would see that I warned you about that. I did say "leave it on the charger until the media scanner process finishes doing its thing" and "it will take a long time." Or at least something like that. So what you are seeing is expected behavior and you should have known that going in.

Furthermore, I had posted that stuff in reply to you. I'm really trying to not be a jerk here, but you're making it very difficult.
[Fascinate Android Development] htim95:
Its still going? Notifications say its doing nothing... and after I rebooted it was in the charger for about 15 min
[Fascinate Android Development] ssewk2x:
When I did it, it went on long enough that it brought my battery from around 80% down to 1% .. and that was with my phone connected to my computer and supposedly charging. So yes, it will take a long long time and it will eat your battery for breakfast. Once it finishes, though, things should be better.
[Fascinate Android Development] Stephen.k.spear:
Ssewk2x did you get the test build I pmed you? Did it help? I'm on Gummy right now so I can't check it.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] htim95:
Should this fix still work with gummy 0.8.1 when released?
[Fascinate Android Development] ssewk2x:
First I've heard of it. I'll check it out.

Actually, i just checked. No pm from you. Did you mean on here or somewhere else?
[Fascinate Android Development] shag_on_e:
I'm getting much better battery life since doing this. Thanks man.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
Good to know, thanks.

I'm working on some other stuff, too:

1. porting the phantom keypop filter stuff from V13 (credit to dmriley@github for doing and testing a lot of it) [almost done]

2. found another potential bug in FAT fs driver (which is what the sdcard uses, I think) and fixing it [done]

3. trying to stabilize the ext4 stuff so nandroids will always work. hopefully I can get TK's performance mods back into it without the bugs. this is the most challenging of the 3, though. [not even close]

I have no ETAs .. it's all going to depend on when / if I get a chance to work on it. Life is still pretty crazy, as it always is when you have a job and a baby, lol.
[Fascinate Android Development] Stephen.k.spear:
Yes all vaccinate roms are updated device tree wise. Glitch will prolly only need to make one kernel from here on out...

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] ssewk2x:
Vaccinate ROMS? That sounds ... prickly. ;)

Someone has autocorrect on, lol.

Anyway .. building another test kernel as I type. Found a couple more things that could be the cause of the lockup. And learned a little bit about ext4 in the process.
[Fascinate Android Development] Stephen.k.spear:
Sent pm again? Lol yeah my phone knows how I think.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] Azuma73:
Has anyone tried the newest Glitch wit the "code name" ROM? I'm thinkin' about takin' it for a test drive?:rolleyes:
[Fascinate Android Development] sixstringsg:
It works great :)
[Fascinate Android Development] 123SIT:
After at least 5 successful nandroids had a bad one. Trying again. Regarding the phantom keypop, I travel to places nearly everyday that cause this so if you need another tester I'd be happy to help.

ETA, we don't need no stinking ETA's lol. Thanks for your work.

EDIT: Very next nandroid was successful.
[Fascinate Android Development] k_nivesout:
#1 in particular would be amazing! The big thing I miss from v13 is the patches that all but eliminated the phantom presses. The other bugfixes are certainly more than welcome as well :).

If you need testers I'm sure you can find willing ones here or on IRC (never see ya around there though). Understandable though, work and family gotta come first! Just know we appreciate any work you find time to do.
[Fascinate Android Development] ssewk2x:
Something is very strange here. I am now starting to suspect the problem might not actually be in ext4 but some other weirdness.

I can adb shell into the phone and successfully run the exact same command that Nandroid uses to backup /data and it works no problem. But when nandroid does it, it almost always locks up near the end. I'm very confused at this point.

If anyone has any ideas, now would be a good time to share them, lol.
[Fascinate Android Development] .Ejekt:
I'm having some trouble with the 800 step. I can't get it below 1125 without my phone hanging. Anyone else run into this?

(LIVE OC @ 110%, low leakage in Glitch app)
[Fascinate Android Development] neh4pres:
Then why are you trying? ? That makes no sense.. If you're stable at that voltage stop messing with it
[Fascinate Android Development] Glocjt:
Tweakers gonna tweak, man. ;)
[Fascinate Android Development] bobloblaw1:
YEah if you are stable at 1125 just stay there. UV/OV should be used primarily for stability as it has little to almost no effect on battery life.
[Fascinate Android Development] ssewk2x:
Well, I have made some progress.

I believe the problem with nandroid now exists in the fiops scheduler, which is (read: was) the default, and therefore was the scheduler used in recovery. After changing the default back to deadline, I am 2 for 2 on successful nandroid backups, without having to wipe cache / dalvik or anything.

So, those who have been having consistent nandroid failures, please try this kernel:

http://dl.dropbox.com/u/28682151/Glitch-kernels/CM9-fascinatemtd-Glitch-nandroid-fix.zip

If you see any more nandroid failures please let me know.

Be advised, you may see some slow-downs. I don't think deadline is quite as fast .. but it seems to be more reliable at least. For now, I've also switched over to deadline under NStools.

This kernel also has the same keypop filtration code that was in my last V13 test kernel, btw.

Enjoy :)

Also, this is my 666th post - hence the devil icon ... which you can't see. Crap.
[Fascinate Android Development] .Ejekt:
Precisely.
[Fascinate Android Development] sageDieu:
idc about nandroids, freaking key pops are where its at. downloading asap

Sent from my ICS SCH-i500
[Fascinate Android Development] 123SIT:
I wish I would have had this about 20 minutes ago, I was at one of those places I mentioned where the phantom keypops are horrible. It's a medical office with shielded walls and so I get low signal every time I work there. No worries though I'll be there again shortly and let you know. Nandroid will also be tested thoroughly cause I'm OCD about my backups lol.
[Fascinate Android Development] ssewk2x:
Perfect. Please understand that I was never able to completely eliminate the phantom keys. So you might still see a few, or even several. It all seems to depend on how crappy your hardware is and what your local conditions are. At the very least, it shouldn't be any worse. :)
[Fascinate Android Development] speedingcheetah:
I was having phantom key presses like crazy..at first when switching to ICS...I removed my screen protector...no problems since..

or is this a different issue entirely?.\
[Fascinate Android Development] bobloblaw1:
Probably a different issue. This is keypops due to signal. Yours was keypops due to contact on the screen. Well, unless your screen protector was made of lead. ;)
[Fascinate Android Development] speedingcheetah:
O..i see...well..at my college...i barely get any signal...didn't have any issues last week....will see on Mon evening if the newest kernel has any issues...
[Fascinate Android Development] blahbleh:
I've searched around but found no good answer to this. Is there anyway to selectively disable BLN for gmail? I'd like it only for text/calls and this was possible in CM7. I have NSTool but no luck finding any options. I realize BLN is kinda borked right now anyways, but I assume that was on the roadmap to fix?
[Fascinate Android Development] speedingcheetah:
well...aside form disabling notifications in gmail....not sure on that one...

BLN is working fine on my current setup...

Unrelated to BLN....I have noticed that after I send or receive a text...the phone sometimes is stuck in 1x mode....have to toggle airplane mode on and off to get it back to 3g...but I believe this is an issue on all MTD roms...as I noticed it occasionally on CM7..
[Fascinate Android Development] remicks:
I've had the best luck with SIO scheduler as default, have u tried that one for recovery scheduler?

Also, thanks a ton for all ur work!

Sent from my Ice Cream Sandwich eating flying pink unicorn... we call him Bob.
[Fascinate Android Development] shelby04861:
Any chance you can take your fixes and apply them to the 6.0 version? I only ask because I am running gummy. Your version works but I loose my data etc. Thanks
[Fascinate Android Development] ssewk2x:
Unfortunately I have no good way of telling what source code the version 6 was built from, so that's not going to be possible at the moment.

I think they're working on getting gummy up to date so you can use the newest glitch with it once they're done.

---------- Post added at 09:53 AM ---------- Previous post was at 09:49 AM ----------

I did not, and to be honest, I'm not inclined to at the moment. I'm now 6 for 6 (I think - I also lost count) now on successful nandroids since switching to deadline as default, so I'm not going to fsck with something that is working. :)

I think my next step is to maybe try and figure out why fiops was deadlocking in the first place since we really don't want that happening somewhere else, too. The good news is the ext4 stuff seems to be just fine.
[Fascinate Android Development] Stephen.k.spear:
Should start seeing nighties for Gummy tonight. They are up to date.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] foxfire450:
Just got around to making a backup, and all seems to be working well. :)
[Fascinate Android Development] speedingcheetah:
woke up today...and phone was SOD...it was not on the charger...hopefully it won't happen again..as i use my phone as an alarm clock....
[Fascinate Android Development] speedingcheetah:
Battery life during standby...seems to be draining quite fast...since flashing AOKP M4 and the second nandroid fix Glitch kernel...

Not sure if its the rom..or the kernel(the switch to deadline from Fiops)...
[Fascinate Android Development] sfobrien:
Just the opposite here. See very little drop while in standby, but a significant loss with moderate use.
[Fascinate Android Development] ssewk2x:
I've been getting great battery life across the board. Here's what i do:

1. Wiped battery stats while on the charger. Not that that really does much, but meh.

2. keep an eye on my cpu utilization...it it stays at 100 pct for a while and max speed, i hook up the charger. It's that damned media scanner, and once it finishes, you're good.
[Fascinate Android Development] speedingcheetah:
What do u use to check cpu utilization?
[Fascinate Android Development] ssewk2x:
I use a widget maker app called elixir. It's quite nice.
[Fascinate Android Development] sageDieu:
check out micro CPU monitor, it puts a little line across the bottom of the screen kinda like the miui battery bar that shows CPU usage. very handy and unobtrusive

Sent from my ICS SCH-i500
[Fascinate Android Development] blahbleh:
Hrmm there was definitely a setting in CM7 to turn this off but still leave notifications in the pulldown..

I thought it was a known issue that BLN is not fully working with this kernel? For me, most of the time the backlight will stay on for a few secs and then turn off. Sometimes it sticks until I check my phone. Is this not the case for you and everyone else? I swore I read in this thread it was a known issue
[Fascinate Android Development] TomTcom:
Try Cool Tool. Lots of options including cpu load, battery temp, clock freq as well.
[Fascinate Android Development] speedingcheetah:
BLN started working fine for me..since the nandroid fix version of the kernel..and AOKP buid 27..