yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Stephen.k.spear:
Nice. Those sound about right. You had me worried. I was like man I know it feels faster... It's it placebo? Lol. A whole point in linpack sounds pretty good.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] neh4pres:
Feels far more responsive than any phone I have ever used.. still have to take my linero benches. But I ran a single quadrant and it was 100 higher..

I have all in screenshots and will post later
[Fascinate Android Development] Stephen.k.spear:
Make sure you give DT his props, his kernel is sick. I just helped him getting it running on the newest linaro toolchain and building in aokp...

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] neh4pres:
Super props dt. You are all awesome
[Fascinate Android Development] Stephen.k.spear:
If your are on my test from today I don't think there is anything new in the devil .84 dt just posted. That's for peeps running cm9 or miuiv4 or anything else.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] yeahdude38:
All i could do was laugh when i was at school last night. The kid in front of me had his phone out. Not sure brand but was something with ics. Couldnt stop laughing as i watched all the LAGGGGG he had opening up apps and switching pages on the home screen and knowing this old beast runs super fast with 0 lag. Goshh i love it. :thumbup::thumbup:
[Fascinate Android Development] yonith:
I am coming from Build 38, 1.4ghz OC from Rom Control with a 50mv UV across the board. I'm using these same settings on Build 39. Everything else is also set up exactly the same. I'm using the average of 3 runs for each benchmark.

Benchmarks for Build 38

Quadrant = 1482

Linpack = 23.527

Antutu = 3661

Build 39

Quadrant = 1453

Linpack = 23.735

Antutu = 3570
[Fascinate Android Development] Azuma73:
I'm kinda at a loss for words here, but you guys are certified Ninjas!!!! I'm talkin' some serious "Chuck Norris"**** here!! Braaaaaaaavo fellas, Bravo!!:D:victory: :D:D:victory:
[Fascinate Android Development] vrahn:
Not sure this is good...I ranked bottom in quadrant
[Fascinate Android Development] Tkun:
I'm not used to using Linpack (I've heard of it before, but I haven't actually used it) and so I wasn't sure whether to post results from a single-thread or a multi-thread test, so I just did both.

NSTools settings (for both, before and after)

smartassV2

Min: 100

Max 1000

Before

AnTuTu: 2716

Quadrant: 1216

Linpack:

Single-Thread - MFLOPS 11.552/Time 7.26 Seconds/Norm Res: 5.68/Precision 2.220446049250313...

Multi-Thread - MFLOPS 15.732/Time 10.72 Seconds/Norm Res: 3.24/Inconsistent Result

After

AnTuTu: 2650

Quadrant:1216 (again)

Linpack:

Single-Thread - MFLOPS 16.974/Time 4.94 Seconds/Norm Res: 5.68/Precision 2.220446049250313...

Multi-Thread - MFLOPS 15.474/Time 10.9 Seconds/Norm Res: 3.24/Precision 2.220446049250313...
[Fascinate Android Development] sageDieu:
these results are interesting. everything is lower or the same in b39, except the single thread linpack test which is much higher. so from what I know about linaro and linpack it looks like this maybe takes a minor hit on underlying (chipset?) performance but it is going to increase the general responsiveness of the UI overall.

basically it isn't going to make your phone handle intensive tasks any better, but it will make scrolling/app opening/general UI more quick and responsive.

I'm interested in battery though, has anyone kept track of battery before and after? I wonder just how much of a hit linaro will take on average battery life.
[Fascinate Android Development] TomTcom:
I was at 66% before the flash. After the flash, configs, app/system settings I was doing some usual reboots and it dropped to 16%.

I think I forgot and reboot with wifi on which I usually don't do so I'll let it drain a bit more, recharge, and wipe stats.

*edit* Yep my fault, I remember an issue a long time back with rebooting while on wifi but I don't recall it affecting the battery. Either way after turning off wifi and rebooting while charged I'm back at 70%.

I didn't use the devil option on increasing wifi antenna power.
[Fascinate Android Development] neh4pres:
Is call boost in this kernel? Aires parts is not showing the menu
[Fascinate Android Development] Stephen.k.spear:
settings device options...
[Fascinate Android Development] neh4pres:
I'm having second thoughts about my pre-order sgs3. I just woke up and unlocked my phone directly to a website, the response time is instant.

I ran some antutu benches on linero. I find the results inconclusive. I aborted testing any further. Steve, if you want I will continue and post results. But I feel the real boost is in the experience of this beast, not benchmarks.

This also reminds me of the days of "one click lagfix" and the 3000 quadrant scores that came with it. How foolish I was that I really believed those results.

Maybe if you include bench apps in the Rom during build, then they will get linero love and explode in the results screen. But I don't think I need any app to tell me this is not a placebo.

Don't forget to buy these guys a beer.
[Fascinate Android Development] shelby04861:
I was going to say the same thing. The numbers are about the same but much of the experience seems snap pier to me.
[Fascinate Android Development] yonith:
I agree that the phone does feel much more responsive. It's almost as if the animations were sped up or something because the phone just moves so confidently while navigating. Steve, DT, and everyone else, we can't thank you enough! I'm still looking forward to my SGS3 in July though :-)
[Fascinate Android Development] Monkeyzzzzz:
Nice
[Fascinate Android Development] Stephen.k.spear:
I'm cooking up a deviled linaro b40 for testing. Although I think it's running very solid, I need this to be a test for other reasons.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] ssewk2x:
A few observations / nitpicks:

1. The etc/init.d scripts seem screwed up. They have all been moved into a sub-directory called "backup". This seems to cause the start-up tweaks setting in ROM Control to not work right, and settings don't persist past reboot. I got them back by moving the scripts out of the backup folder, removing the backup folder, and rebooting a couple times. I noticed this same issue when I flashed the devil kernel over the previous glitch build, too.

2. My initramfs changes to support shutdown scripts in /etc/shutdown.d have not been included in this build. :(

3. My *228 fix is present in its entirety, tho, yay! :)

4. In devil kernel manager, it's tricky to get the bigmem setting to stick. Gpu oc setting also does not stick after reboot.

5. Startup seems a little slower, but once it finishes, this thing rocks! Also, the new boot animation is nifty.

I'll post more as I find it, if I do. :)
[Fascinate Android Development] vrahn:
I'll be a test subject. Since I learned how to root/mod this phone its been waaaaaaaay snappier for me in the the means to response time and game play. Quadrant tells me I'm in the very bottom as far as results go though. I'll include a picture at the bottom of this post, but as mentioned earlier I also believe the results are not necessarily numbers alone. But the overall experience
[Fascinate Android Development] thisguy23:
Are you using 2d hardware acceleration? 420 is a really low score. I get 935
[Fascinate Android Development] rmtobler:
Even though I don't anticipate any issues I will honestly have no problem sticking with this phone if the unlimited data/sg3 activation becomes a problem!
[Fascinate Android Development] yonith:
:::FACEPALMS:::

I forgot about that setting. I just turned it on and it bumped up my Quadrant score. You are probably right in that he didn't have that setting on. I'm wondering why this setting isn't on by default. Would it drain battery more?
[Fascinate Android Development] Tkun:
Am I the only one experiencing random closes within apps? They're not even force closes as they don't have that dialog pop-up, they just...close and send you back to your home screens. It only occurs with certain apps and it's not immediate (usually after using them for around a minute it happens), but this seems to have only started happening since flashing the new Build 39 with Linaro.

SMS Backup & Restore is one of the apps I'm talking about. A backup doesn't always complete before exiting.
[Fascinate Android Development] ekowanz:
I hav this issue, but only with app that i restore from TiBu

Sent from my SCH-I500
[Fascinate Android Development] TomTcom:
Originally Posted by Tkun View Post

Am I the only one experiencing random closes within apps? They're not even force closes as they don't have that dialog pop-up, they just...close and send you back to your home screens. It only occurs with certain apps and it's not immediate (usually after using them for around a minute it happens), but this seems to have only started happening since flashing the new Build 39 with Linaro.

SMS Backup & Restore is one of the apps I'm talking about. A backup doesn't always complete before exiting.

I hav this issue, but only with app that i restore from TiBu

Sent from my SCH-I500

I have the issue mainly with Opera. I cleanly install Opera every time and do not restore it with TiBU but I sometimes have to open it 2 or 3 times, then good for a while, then just closes and that's it.

This has been since build 36 and all the way up to the latest test build from Steve. Logcat never reveals anything other than the java activity being destroyed or something like that.
[Fascinate Android Development] vrahn:
Where do I turn 2D acceleration on? In quadrant or is it in from settings
[Fascinate Android Development] thisguy23:
Settings. Development options. Force 2d hardware acceleration
[Fascinate Android Development] Stephen.k.spear:
Ok build 40 Devil is up. I'll update to OP later.

The kernel says v.81 that's cuz I didn't up date the version it has everything v.84 no need to flash it. The whole build is compiled with the latest linaro toolchain which I still consider in testing even though everything is working so far...

Happy build day everyone. Enjoy.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] sageDieu:
when that happened to me, it ended up being a corrupt SQL database. didn't fix itself till I did a full wipe and started from scratch, as in don't restore any data or anything.

as for build 40 I have been running it since this morning and I will be the first to say it has once again put new life into my poor old mesmerize. I had been starting to get awful lag and choppiness and slowness on b38, and so when steve sent me build 40 I took the bait. it is running great, all lag and slowness completely eliminated.

haven't bothered with benchmarks since they're usually full of crap anyways, I don't need an app to tell me how much better my phone is running now.
[Fascinate Android Development] sendan:
I booted up the Glitched build 40 and wow, games perform great! Don't get me wrong Shadowgun was always "playable," but there is a lot less latency now. Plus MC3 starts in half the time, I am impressed. :D

The only problem I found was the init.d is messed up, I did the same thing ssewk2x did and I *think* it's working properly now...so that's not a big deal!

Thanks for putting this together to everyone involved!

Edit: It looks like something is causing s30datafix to be created (and activated) every reboot. Couldn't this explode some unsuspecting people's backups? And also it's a bit problematic as I'm trying to run a different version of the script but it won't disable. :(

I'll post this in the devil thread too though as I think the kernel is what handles init.d.
[Fascinate Android Development] k_nivesout:
Anyone else have any luck getting videos to play? Tried youtube and some locally stored videos I recorded, nada.. However, things do feel buttery smooth otherwise.
[Fascinate Android Development] vrahn:
I did the b40 and after boot up it was trying to tell me my phone wasn't active...Im kinda scared now.... Im re-doing the whole phoje again as we speak...If it is as simple as *228 then I will give it a go but my phone was active from when I got it in the mail...So I hope it will work this time
[Fascinate Android Development] sageDieu:
just watched a YouTube video without issues. I have a 720p mkv I'm trying to get working, with moboplayer I can either get smooth video and no audio on hardware rendering, or choppy video and audio on software rendering. but that's a high quality mkv which has never been good on a single core processor and 384mb ram.
[Fascinate Android Development] Azuma73:
Yeah, I'm not having any luck with videos either? Also, when trying to run Quadrant Advanced, it stops on 10/12 video decoding? ....Hmmm??
[Fascinate Android Development] vrahn:
Not too sure if this is better or not
[Fascinate Android Development] Stephen.k.spear:
Im betting your either a dirty dirty flasher or your RAM is set to 402mb...

Am I right or am I right?

Try turning the ram down and rebooting if that doesn't work wipe it all and reflash.
[Fascinate Android Development] sendan:
Video doesn't work here either, RAM setting is good and its a fresh flash.

And I just realized my init.d isn't functioning at all anymore, I don't know if that's a problem from linaro or what...but it's a deal breaker.

:o
[Fascinate Android Development] droidstyle:
i couldnt get videos to play either on linaro build 39..that was coming from 38 with a data wipe. went back to official aokp 39 and video played fine and still did after restoring data.(391mb ram setting btw)
[Fascinate Android Development] Stephen.k.spear:
Both my real phone and dev phone had no video on first flash. Wipe reflash and both are working now.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] yonith:
FWIW I wiped going from build 38 to 39 devil, am using the XL 391 RAM setting, keep 80 MB RAM free setting, and have no problem playing 720p mkv files in MX Player (restored app only from Titanium Backup).
[Fascinate Android Development] Stephen.k.spear:
Well it looks like if I turn the memory up to 391 or 403 I lose video. I'll let dt know and I will look at the logcat later. Just stick to 378 for now it's faster than 391 without linaro anyway...

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] ssewk2x:
I don't know if I got a bad download / flash, or what, but the build 40 test completely and totally ****ed my phone. Hard. No lube at all.

I'm in the process of recovering now. Also, I just discovered that the backups I had made using TWRP were invalid and don't restore anything.

FML
[Fascinate Android Development] vrahn:
First time phone told me it wasn't active. Second time its ok now.
[Fascinate Android Development] ssewk2x:
I WISH that was all that happened to mine. I got stuck at the devil kernel logo. Couldn't get an adb shell, nor could I adb into recovery. I kept getting an error saying a libc.so was missing - which tells me bad flash or bad download. Especially since you guys have all been flashing build 40 just fine, and if libc.so was really missing from it, you'd be ****ed, too.

I'm restored to something reasonable-ish now. I managed to get into a TWRP that would restore the backup I had, and I'm afraid I'm going to be sticking with Glitch until I have more time to figure out what exactly is going on with the Devil, or at least until I can get a proper backup made that I can restore.

But for now, it's sleepy time.
[Fascinate Android Development] adamklo:
This happened. B40. Feels a million times snap pier, but it could just be placebo.

The boot ani I've got is the bubbles like one with the aokpicorn. Is that expected?

Glitch'd AOKP
[Fascinate Android Development] Toddw:
I don't know why but I've been having a bad problem with my phone getting stuck in recovery with recent builds. It's only when I flash an update and reboot, it'll reboot into recovery every time. I'll ODIN back and start over. It also likes to boot into safe mode alot.
[Fascinate Android Development] dave_k605:
Build 40 is running amazing here...super smooth.

If I could make my screen grow, I wouldn't buy the g3 or any new phone for some time.......this outdated fassy puts in work and makes better speced phones seem lesser.

Sent from my SCH-I500
[Fascinate Android Development] Stephen.k.spear:
I am bummed that some peeps are having issues. You guys are missing out. This thing has never been this fast. Plus I am gonna try a armv7 optimization I found on cm9 gerrit today for a touch more speed. ;-)

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] schu9120:
I too have had some issues with this transition to the devil. Im not sure if it was bad downloads, flashes, or recoveries but I have been spending a lot of time lately reconfiguring my phone due to unforeseen issues.

Dont get me wrong, I don't mean to whine. I enjoy being on the bleeding edge and I understand the risks that come with it.

I have been very faithful to the glitch kernel since its release on the fascinate and I feel kinda guilty running with the devil ;) @ssewk2x without your contributions, we would still be dealing with extremely quit in-call volume, capacitive button issues and many other bug fixes. I don't want your contributions to be forgotten. Thank you

/end rant
[Fascinate Android Development] sageDieu:
decided to pop in my stock battery when I flashed 40, to see how linaro affects battery life and because not everyone has an extended battery.

this is not much worse than my extended battery, for medium usage. I'm impressed, especially with the drastic increase in speed on this build.

I will use my extended battery tomorrow and see how it fares.
[Fascinate Android Development] vrahn:
Are you making sure that when you select atlas that re-partition is checked? also make sure you are wiping data after you flash cwm. After you install build o e or two make sure you wipe then too.

Btw...

A.....FRICKEN.......MAZING
[Fascinate Android Development] k_nivesout:
Switching RAM back to CM9 level did fix the video issue for me, thanks for the tip. Build 40 is excellent.
[Fascinate Android Development] phxshadow:
Just flashed B40. I have to say wow very snappy. I have not had any issues, everything is running very smooth. Its a great leap for this rom.

Thanks for all the Great work on this rom Stephen !!
[Fascinate Android Development] ssewk2x:
So this morning I'm now experiencing the issue of the thumbnails in the photo gallery being all screwed up. LOL it never ends ... Did anyone ever figure out a work-around for that?
[Fascinate Android Development] kuronosan:
I know it seemed odd but I haven't done anything different with my phone. For some reason deep idle wasn't working too well and I'd have about 40% battery left at the end of the night. I turned up the screen a and had 80% last night. Same amount of use and my data is always on.

Sent in an Ice Cream Sandwich from my SCH-I500.
[Fascinate Android Development] sageDieu:
put your card in a computer and run fsck or chkdsk on it if you can. I had issues with my gallery and it was due to corruption on my SD card, I did that and then deleted the images that were corrupted and it fixed gallery issues and kept media provider from eating my battery trying to make a thumbnail all day.

Sent from my AOKP SCH-i500
[Fascinate Android Development] speedingcheetah:
Lockups

So..I am definitely having issues with playing music with the screen off and having lockups...DIDLE and Screen state are both disabled...wifi is off...

I am using Amazon Mp3 to play music files from my SD card....a 32gb Class 10 Transcend....

I have tried switching io schedulers (in NS tools)from fiops, to deadline, to sio....i still experience lockups...

Under cpu I am using, GlitchOndemand, Min cpu: 110mhz, Max cpu: 1320...Live OC 110%...

I have never done anything with logcat before...so I found a free app for it 'aLogcat"....I noticed by sorting the log by "Fatal"..that I see this at the time the lock up happened:

[03-15 09:44:12.113 1541:0x605 F/libc ]

Fatal signal 13 (SIGPIPE) at 0x0000060a (code=0)

For whatever reason...I do not see that in the full log..once I reboot from the lockup and go into the app and save the log...guessing it clears it out...but I am attaching the log cat anyway....Open in Wordpad...as it seems to preserve the formatting...

One other thing I am noticing...In CPUSpy...after the lockup and reboot...the app is reporting that 1650Mhz is a used state...but lists all 0's for time and %...It's odd because it only reports this AFTER the lockup and reboot...I know because I cleared out the stats the first time I had a lockup....played a song and check the stats..played another song and it locked up 1 min into the song..rebooted..and cpuSpy reported that step....

So it appears to me that (maybe) something is causing the cpu OC limit to go past its limit and thus lock up the phone...I know that my hardware WILL freeze at the 1400mhz step....That was the case back on cm7, the old versions of the glitch kernel (as well as the other kernels out)then on Froyo and GB...

yes..I have tried stock settings...no live oc and steps set to 100-1000mhz...still have issues

I am posting this in both the Glitch kernel thread and the AOKP thread....because I am using both...

Hope this helps...
[Fascinate Android Development] droidstyle:
quick pic?
[Fascinate Android Development] ssewk2x:
Oddly enough, I did that, and that's when the errors started. Windows chkdisk found no problems with the sdcard, and then on the next boot my thumbnail images were all screwed up. Maybe I need to do it again, idk.

I'll try quickpic, too.
[Fascinate Android Development] thedoman:
Small issue and in no way a deal breaker: my battery text is green and shows "charging" when unplugged and discharging.
[Fascinate Android Development] Bad Bimr:
Have not touched a Fascinate since July of last year. Wife's fascinate is bloated and stock and she wants it speedy again. This ROM seems pretty awesome but for the life of me I cannot find the latest greatest CWM needed to install this. Any help/link will be greatly appreciated.

Thanks

BB
[Fascinate Android Development] ssewk2x:
Here are the odin files I use:

http://dl.dropbox.com/u/28682151/cwm4_fixed_for_cm7-ODIN.tar

You'll want the gingerbread bootloaders, too:

http://dl.dropbox.com/u/28682151/GBBootloaders.tar
[Fascinate Android Development] sarkozy:
I had that happen when I restored a backup. You can delete Gallery data, or manually delete the Thumbnails folder on you SD card. Reboot and you'll be golden. That's happened to me on CM9 and AOKP.
[Fascinate Android Development] ssewk2x:
Yeah, it's apparently the Gallery app that's doing it, and not the media scanner. QuickPic handles everything just fine, and it doesn't make me crop the hell out of a nice pic before letting me set it as wallpaper. #winning
[Fascinate Android Development] andymetoo28:
Yeah Quickpic is pretty nice when gallery decides to crap out on you.
[Fascinate Android Development] neh4pres:
You need to follow Droidstyles guide in the general section
[Fascinate Android Development] mrjake1970:
One simple request for future builds.

Add the ability to add ANY shortcut/option to the statusbar and/or general UI.

To be specific, I cannot for the life of me figure out how to add either a shortcut or get a toggle in the status bar for the "security" options.

I love quick access to this, and haven't been able to get it in this ROM.

I like to be able to have a quick one button push to be able to set a password on the phone for during the day when my phone is unattended at my day job, and switch to "slider" mode when im not at work. I had this on MIUI prior to the CM9 codebase. I could add it right to the statusbar dropdown.

If I'm just missing something and can do that, please share..
[Fascinate Android Development] andymetoo28:
Mod is working great so far. Gmail only crapped out on me once but prob a gapps issue. I have this itch to flash glitch kernel but reading through here seems some people are having more issues while on it and while I want it bad...hey...if it ain't broke don't fix it. Does that seem to he the case with most people?