yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] speedingcheetah:
I am on B4...

Didn't know there was a version B5...OP still has B4.

EDIT: Flashed B5..the LEDS works when tested from the BLN app...but don't work for any other notifications....blaa...only 2 functionality things not working for me...torch and BLN...course that was the was way it was in the early days of CM7..so I can't really complain at the moment..
[Fascinate Android Development] shelby04861:
Try using the legacy setting I think in bln settings. I think it was that combined with clearing stuff that got mine working right again.
[Fascinate Android Development] sixstringsg:
OP updated. Sorry it took so long, real life happened.
[Fascinate Android Development] Azuma73:
Ok, please don't give me a heckling, but is it just me or is the only updated kernel V13? I am not seeing anything for V14 b5 for 6.1 updated since 2-22-12? Please correct me if I'm mistaken!!:eek:

Thanks Guys.
[Fascinate Android Development] pmjr0987:
4 things-

1-just updated to B5 6.0 is there any benefit to 6.1?

2-i get a "gapps" error all the time even after i updated from B3 to B5 just now

3-i want to go to 09 radio from the 03 whats the best way to do this, tethering does not work (hooks up but no internet) and my signal is all over the place i think 09 is a better base band, at least it was when i was running V13

And Fourthly I want to know why "NStools" is said to be required. I have better luck running Antutu to overclock my device, seems to run more stable with NStools i was getting random reboots etc
[Fascinate Android Development] ekowanz:
For anything update, just checking it at androtransfer.com/tk-glicth/ choose the cm9 for fascinate

Sent from my SGH-T959
[Fascinate Android Development] Azuma73:
Yeah, thanks, but I'm there and the last update I see Is 2-22? Are you seeing something I'm not?

NOT to be a P.I.T.A.(pain in the ass), I just hate feeling like I'm missing something here?
[Fascinate Android Development] sixstringsg:
Have you looked in the OP? Also, the latest update is 2/22, what are you looking for that you think is newer? That was only a week ago.
[Fascinate Android Development] Azuma73:
Okay, my bad?

I just thought there was a Glitch update today? Is that not what you meant in your post above? Sorry, I'm really not trying to hassle anyone, perhaps I misunderstood?
[Fascinate Android Development] sixstringsg:
All I said was that the OP was updated. I didn't say anything about a kernel update. I haven't been in town to update the OP for the february 22 build.
[Fascinate Android Development] Azuma73:
A'ight, I stand corrected in my ASSumption(or is that presumption?)!! Guess I got a little jazzed up for new action? Sorry .......carry on!!!:o:o
[Fascinate Android Development] speedingcheetah:
What legacy setting?...i don't see any option for that in the BLN app..
[Fascinate Android Development] shelby04861:
It is under the test section of bln pro, not sure if it is on the free version. You might also try blinky, as that is supposed to be good as well. I am on gummy with b5 and I can confirm it is 100% working, if not from dumb luck maybe.
[Fascinate Android Development] pmjr0987:
can anyone answer my questions?
[Fascinate Android Development] k_nivesout:
1. Not sure what you're asking. Are you asking about the kernel itself or the rom? The 6.1 version is for THS 6.1/6.5 and any of the other ICS roms based on it. I imagine development for 6.0 will be phased out since we have newer, more functional/stable rom versions. There's a changelog, and a link for changelogs in the OP of this thread that tells you what the difference is between releases.

2. This is unclear too. Need more info to help you. What kind of error? What does it say, when does it happen, etc? What rom are you on?

3. I found little difference between EH03 and EC09 radios, and switching the radio isn't gonna make your tethering work. Radios are flashed in odin, at least the ones I've seen. For tethering (assuming you're on THS), you'll need to use the wireless tether app from google code and switch the device profile to Galaxy Nexus. I've heard that native tethering is fixed in the latest AOKP build.

4. The difference between liveOC and the "old" overclocking system (using voltage control or pimp my CPU) is explained in the liveOC guide, which there is a link to in the OP.
[Fascinate Android Development] pmjr0987:
Thanks for the help. right now my phone says im on kernel 3.1.10_IcyGlitch_V14_B5_I500 MOD- IceCreamHackish-1292011- Fascinate BUILD - IML74K

when i origionally upgraded to ICS my B3 kernel was the most recent version. Everything i read said 6.1 was completely unstable. I dont see where i can download 6.5 ill keep on looking though

As far as NStools when i messed with liveOC even just 110% my phone heated up and froze/rebooted. im running 1500mhz with antutu and the phone is so far today dead reliable.

The gapps error im getting happens every time i reboot and randomly while using the phone. A dialog box pops up saying "Unfortunately, the process com.google.process.gapps has stopped. " I notice my signal bars are almost always gray not blue, not sure what that means exactly but from what i read it seems to have a connection with the error
[Fascinate Android Development] sixstringsg:
There is little chance of you doing 110% Live OC with 1500 step. Also, the gapps issue has nothing to do with the kernel. You are getting FC's from somewhere, which is why your signal bars are also blue. Fix your ROM then those issues will go away.
[Fascinate Android Development] pmjr0987:
the 110% live OC was with stock mhz that was causing freezing and rebooting.

Im running antutu at 1500mhz with zero problems

since im updated to b5 today i suppose i can try NStools again and experement a bit. I haven't seen anywhere here stating what these phones are generally stable at. whats a good liveOC % and mhz to run to be stable and fast?
[Fascinate Android Development] neh4pres:
If your gonna just use normal overclock use voltage control. antutu can't do the things a real overclock app can.
[Fascinate Android Development] sendan:
My phone runs best at 115% liveOC, at 1000MHz step. (1150MHz) If I go any higher with the liveOC I eventually get a random reboot whiling playing a game like MC3 or something.

If I turn liveOC off and OC to 1400-1500MHz the phone doesn't seem as fluid or smooth. I haven't done any speed tests (besides a few benchmarks with cf-bench), just visual testing with games and web browsing.

I tested this very thoroughly...but all phones are different!
[Fascinate Android Development] droidstyle:
if your using live oc dont go over 115% w/ 1000mhz or 110% w/ 1200mhz. 1500mhz with no live oc is pretty stable, but will crash when playing videos or games.
[Fascinate Android Development] pmjr0987:
I tried NStools 110% stock mhz and the phone did not do so well.

Antutu (using the V14 B5) running 1500mhz GlitchassV2 Modern Combat 3 plays super smooth faster than any setting ive used with NStools. also when i benchmarked using Antutu clocked at 1500 my ram showed 619 with a final score of 3707. I thought only liveOC overclocked the ram in addition to the CPU
[Fascinate Android Development] neh4pres:
Your not overclocking the ram.. Only pushing more information to it until it becomes a bottleneck. Nstools does more than just live oc.. You can change the freq. Just like antutu.. I don't understand why your using a benchmark app to overclock .
[Fascinate Android Development] pmjr0987:
the benchmark app and there cpu controller are both made by Antutu but i was using "CPU master free" by Antutu to clock it up to 1500mhz and i used the benchmark app to benchmark exclusively. I deleted Antutu cpu master and replaced it again with NStools so I am running what was said here to run.... 1200 mhz with 110%liveOC in NStools ill see how it goes. so far the phone feels awesome.

one thing i forgot to say is my camera is 100% not working. the interface works it makes the photo sound but doesn't record anything. about 1 out of ten times id did record, when i try and pull up the photo it just keeps loading and shows nothing. common problem or did i do something wrong?
[Fascinate Android Development] neh4pres:
The camera is ROM side
[Fascinate Android Development] bones420la:
6.1 link down?

the link for build 6.1 version is down....

and aokp 27 loses data with the build 6 version
[Fascinate Android Development] mrjake1970:
On AOKP 25 with B5 for 6.0

Just noticed something - not sure if it will help with fixing BLN. Y'all are the coding experts :)

BLN shuts off and doesnt work as previously posted. However, if i use the PIN lock or password security locks, BLN works normally and the light doesnt go off right away. Stays until i power on phone like normal.
[Fascinate Android Development] sixstringsg:
Copy paste fail on my part, reading fail on your part. I appended to .zip to the filename.

http://androtransfer.com/tk-glitch/...M9-fascinatemtd-Glitch-V14-B5-ForBuild6.1.zip

We've got some test builds in beta right now that have BLN working, thanks for the input though!
[Fascinate Android Development] vshand:
Aokp27 / glitch 5 for 6.1 got stuck when backup. Aokp/stock kernel is OK. Any fix?
[Fascinate Android Development] bigmike88:
Clearing dalvik and cache allowed me to back up no problem on earlier builds
[Fascinate Android Development] DevinLeFevere:
10char edit. Sorry for the clutter XDA app is acting weird.
[Fascinate Android Development] Tk-Glitch:
By 20%, not 120%. It's running at 120% versus 100% if it's clearer this way.

About bootloops :

WARNING : THIS KERNEL IS USING MASS STORAGE USB MODE BY DEFAULT. IF YOUR ROM IS USING MTP BY DEFAULT, MAKE SURE TO SWITCH TO MTP IN GLITCH RECOVERY JUST AFTER FLASHING THE KERNEL, OR YOU'LL END IN A BOOTLOOP. YOU CAN THEN SWITCH TO MASS STORAGE IF YOU WANT AFTER A FIRST BOOT.​
[Fascinate Android Development] DevinLeFevere:
10char xda app is losing its mind.
[Fascinate Android Development] 123SIT:
Thanks guys, running the b3 for build 6 on aokp rom and so far so good. You guys are amazing and have come through as usual.
[Fascinate Android Development] Azuma73:
A swing ........and another Home-run guys!!!!!

Infinite thanks fellas!!!:D
[Fascinate Android Development] bobloblaw1:
This is damn good. Thanks guys!

If anyone wants to play with oc these are my settings. It seems to be speedy and very stable. I didn't touch voltages or anything else

Glitchondemand

Live oc: 116%

Max clock 1392

Min: 116

Oh, and you guys might want to uncheck apply at boot in nstools until you are sure you are stable. That option was ticked by default for me.
[Fascinate Android Development] madmike0408:
I literally couldn't be any happier with this kernel on THS 6.0. This is the most responsive my phone has ever been, OCed to 1.4ghz and loving it!
[Fascinate Android Development] shelby04861:
build 6 work great on Gummy Mesmerize. Havent messed too much with settings because I am at work. I also made sure to uncheck set at boot incase anything screwed up the phone again. It is super fast I must say! THANKS
[Fascinate Android Development] Azuma73:
So, anybody got the info about THS 6.1 and V14 b3 for 6.1? Is everything working?

I'm using THS 6/V14 b3 for 6 and it's really nice!!

Thanks guidos!!:rolleyes:
[Fascinate Android Development] bdanders:
What drivers should I be using to connect to the phone via USB from my computer? Right now I'm not getting the option to connect when I plug in.
[Fascinate Android Development] NoHolidaysForAHooker:
Using beta 3 on build 6 with standard steps and 20% overclock makes this phone feel a lot quicker and more responsive than the stock Galaxy Nexus I was playing with at the store yesterday, except the 4g data of course.
[Fascinate Android Development] neh4pres:
Had a 23 percent overstep with slightly increased voltages and was stable for a day then got some lines across the screen. A reboot recovers it. I know it's from the gpu. Can i fix it with voltages or do i just need to back down in oc? Never had it with v13 and I think you had the gpu clicked that high with 1500mhz.
[Fascinate Android Development] sixstringsg:
Changing voltages might work, yes.
[Fascinate Android Development] Tk-Glitch:
I'll add to Six's answer that a bit more or a bit less on Int voltage should fix it. Make sure you are doing a linear voltage bump between frequencies (+/-).
[Fascinate Android Development] neh4pres:
By linear, do you mean i should bump all of them?
[Fascinate Android Development] Tk-Glitch:
No, I mean that the general ramping up of the voltages should follow a linear logic, whatever settings you are using. Don't make too big voltage gaps between frequencies, especially the high ones.
[Fascinate Android Development] Glocjt:
I've been on THS 6.1 and V14B3 since Tk posted the kernel (I really need to download the version with Glitch CWM, lol), and so far things have been smooth. OC'd to 1300, no UV, gonna play around with live OC this weekend. I sit in a Faraday cage all day, and I haven't had any problems with data and such, although I haven't tested the handoff to/from wifi and airplane mode yet.
[Fascinate Android Development] tripacer99:
Same problem here, but something happened after the lines came on the screen and the phone froze & rebooted. Now, it refuses to boot to anything other than recovery, no matter what I do. I've tried wiping data/factory reset, flashing cm9 again, flashing glitch, nothing. Stuck as to what to do now :/

EDIT: Meh, ended up having to break out odin. Sigh, that's the last time I mess with NStools...
[Fascinate Android Development] ekowanz:
Yep it happens to me too with nstools, i change the voltage, then suddenly phone get freezed. Then always boot to recovery. Hav to odin to make it back normal.

Now i just use the rom control to choose governor and etc.

Sent from my SCH-I500
[Fascinate Android Development] shelby04861:
Same thing happened to me as well. I unchecked the set at boot until I get it all dialed in. Not sure why it happened other than I threw in unstable settings causing it to crash.
[Fascinate Android Development] sergyum:
+1 same here, ICSSGS RC4.2 / Glitch V14-B5, clearing dalvik and cache allowed me to back up until :Backing up data...then stuck
[Fascinate Android Development] 123SIT:
Same thing here regarding the nandroid backup. I actually remove the symlink from /data/data to /datadata though. Therefore, I have an actual /datadata folder and a /data/data folder. I use a script to move important objects (database etc.) to /datadata from /data/data and then a symlink is created pointing to faster /datadata location. I had experienced the problem in aokp 25 and 26, but a second try was usually successful. Since build 27, I'm completely unable to nandroid. Always hangs on the data directory usually on some trivial file. I distinctly remember a event*.txt file and xtra.bin file as my culprits.

Sent from glitched aokp mez
[Fascinate Android Development] drakester09:
For everyone having issues doing a nandroid:

Try wiping cache before backup.

That has worked for me every single time.

Hope it helps.
[Fascinate Android Development] ssewk2x:
Yeah, same thing for me. The problem is that it's the "tar" command on data that's failing, and the code is the same in both recoveries. I wonder .. those who are able to nandroid vs those who aren't .. do you remember which recovery you did your last data wipe with? I wonder if the different recoveries are formatting the data partition a little differently and that's what's tripping things up. Maybe if I get a chance soon I'll check that code out, too.

And of course, I can't remember what I did my last wipe data/factory reset with, whether it was glitch, stock recovery, or just let Odin do it. But I haven't been able to make a nandroid since jumping to ICS except for one time when I thought I had found a work-around, but that trick failed on the next attempt as well.

This same trick has never worked for me. The closest I got was when I mucked with the symlinks and mounting /datadata, but that only worked once.

If things aren't too crazy for me at work today, I'll try to take a quick look during my lunch hour. I've got a few ideas that might be worth trying in order to diagnose this issue.
[Fascinate Android Development] sarkozy:
I've wiped data in the glitch recovery and original CWM before flashing, and my backups have worked fine each time. I only have 15 third party apps installed if that would make a difference.
[Fascinate Android Development] ssewk2x:
I found a possible bug in the glitch kernel ext4 fs drivers that might be related to this. In any case, there's the potential to use a pointer un-initialized that should be fixed, whether it's related to this or not. I left a more detailed comment on github - posting here mainly in case the (active) devs aren't alerted to it right away.
[Fascinate Android Development] 123SIT:
Same results, no nandroid.

Sent from glitched aokp mez
[Fascinate Android Development] ssewk2x:
Ok, screw it. I'm going to download the source tree and start building kernels again.

Just wish it didn't take hours to pull down the build environment :-p
[Fascinate Android Development] foxfire450:
Well, it did make a complete backup for me after flashing the GB bootloader, but it's gotten stuck everytime after that. Don't know why it let me make one then.

I've noticed that the last file showing at the top that it went through when backing up data was a file in /data/property. Last attempt was persist.sys.country. The one I just tried to make shows persist.sys.language. I've also seen presist.sys.scrolingcache before. As far as I can tell, the files seem to be fine. Dunno if that helps anybody make heads-or-tails of the problem. *shrugs*
[Fascinate Android Development] shag_on_e:
He's baaack!

~~~~There is no spoon~~~~
[Fascinate Android Development] k_nivesout:
Is everyone having backup issues using B5? I made a backup a couple days ago on B4 and it completed it normally.
[Fascinate Android Development] speedingcheetah:
GB Bootloader?

So..I am reading I should have GB bootloader when using ICS....

How do I know if I have them or need them?...I was on stock ED05(long time ago)..been on CM7..now ICS....does any of the roms flash the GB bootloaders?

What is the advantage of GB bootloader vs the stock one? I havn't had any issues...with what I have..

Where can I download them?

EDIT: Found it...Look at THIS post...
[Fascinate Android Development] Deliquified:
If you haven't flashed it in Odin, you don't have it. It needs reflashed after doing a repartition. You can tell for sure using Glitch kernel.. The Glitch kernel V14 screen won't load before the boot animation without GB bootloader. Read the OP on where to get it, or go back some posts as I believe someone posted it recently.
[Fascinate Android Development] Deliquified:
From OP.
[Fascinate Android Development] neh4pres:
If you would have read a few posts before your post you would know the answer
[Fascinate Android Development] ssewk2x:
If the backup issues are caused by the bug I found in ext4 fs driver today, then they would be random after (probably) a bunch of operations. Since there's a bunch of stuff in /data, it's reasonable to guess that some of you wouldn't see it after clearing out dalvik while for others with more apps the probability of triggering the bug is higher.

Tk-Glitch is now aware and seems to indicate that this might be a bug he's been hunting for a while, too. So hopefully he'll patch things up and maybe we'll have a new build to try soon? I'm just wildly speculating, so don't go harassing the Master about it ;)
[Fascinate Android Development] shag_on_e:
Looks like there's new source allowing LiveOC for ones desired steps...

https://github.com/byeonggon/lynx-nexus-s/commit/9fe48e29f9b0f3ba43a0f887d4d0a8095a41c125

~~~~There is no spoon~~~~
[Fascinate Android Development] sixstringsg:
We have had that since we implemented LiveOC, but no app to use it.
[Fascinate Android Development] shag_on_e:
Yeah, I thought twice about posting that, shoulda known the pros knew about something I found :-P anyway, y'all rock.

~~~~There is no spoon~~~~
[Fascinate Android Development] k_nivesout:
Was actually more a response to foxfire450 but I forgot to quote. Thanks for the protip though.

Didn't see him mention what kernel version he was on. Also just thought it might be worth putting out that B4 doesn't seem to have backup issue (in my experience at least), for those reading through that might be thinking about flashing. Cheers. ;)
[Fascinate Android Development] Sheradrax:
Could some one please point me in the direction of how to fix an md5 mismatch for my nandroid?

Edit nvm it wasn't an md5 issue.

Sent from one twisted fassy. Mmm... ice cream.
[Fascinate Android Development] sixstringsg:
Are you trying to restore it and are getting that error?
[Fascinate Android Development] Sheradrax:
Ya. It was because I put a space in the folder name. I've never had that problem before that I know of.

Sent from one twisted fassy. Mmm... ice cream.
[Fascinate Android Development] droidstyle:
Just a fyi:

I just completed a nandroid on B5 with no issues...just had to wipe cache and dalvik first or else it hangs up at datadata. So it seems that this works for some and not for others for some reason...no gb bootloaders here either.
[Fascinate Android Development] fulaman:
Is the phone stable at: 1200 step with 10% live OC (110%) = 1320mhz?
[Fascinate Android Development] droidstyle:
mine is....
[Fascinate Android Development] fulaman:
When you guys say run the phone at 110% liveoc, and 1200mhz, you actually mean 1320mhz right?
[Fascinate Android Development] droidstyle:
Thats correct.....
[Fascinate Android Development] neh4pres:
I also run that setup.. all stock voltages
[Fascinate Android Development] fulaman:
Oh ok, thanks, what governor do you use currently?

That's awesome, what governor do you use?
[Fascinate Android Development] neh4pres:
I use stock
[Fascinate Android Development] speedingcheetah:
Deep Idle?

In NS Tools...What does "Deep Idle" do...(it is set to Off by default)and is it supported....or do I have to enable something in recovery to actually use this?

May have been asked before..somewhere in the 42 pages of this thread...but the search feature is disabled on XDA for some reason...so....
[Fascinate Android Development] k_nivesout:
Deep idle

That said, I can't seem to get deep idle to work. Tried a few different things but I never rack up any TOP=ON or TOP=OFF time according to the deep idle stats. If anybody has been able to get it working I'd love to hear how.
[Fascinate Android Development] speedingcheetah:
I meant specifically for the Fascinate...not the nexus S...Is "deep idle" the same as "Deep sleep"...because the phone goes into that no problem..according to CPUSpy...
[Fascinate Android Development] sixstringsg:
Deep Idle and Deep Sleep are completely different. Also, that information is as close as you'll get to "specifically for the Fascinate" It is the same concept, and it's the code that we use.
[Fascinate Android Development] speedingcheetah:
O...ok..i understand...

btw....i enabled the screen state scaling in the recovery....but with the screen off governor set to conservative or power-save...the the screen won't wake up...SOD...so I have it set to same as the on screen...GlitchOnDemand....not getting SOD now...but I was wondering, if setting it the same means that I am not actually saving power...and might as well disable screen state scaling...or is there other things going on under the hood with it enabled...regardless of what governor is used...Which governor is recommend for screen off state?...

EDIT: I am noticing one thing...When I have Wifi on and connected...and lock the screen...it won't wake up....I disabled screenstate scaling in the recover..but had no effect...
[Fascinate Android Development] k_nivesout:
Not trying to be a d*ck or anything, but I have a feeling if you read through the thread and the links in the OP, your questions will be answered. It sounds like you're using deep idle, which if it's used with wifi, will cause a SOD (one of the things that's been mentioned in the thread). I'm sure Tk-glitch will be working on getting deep idle more stable and functional, but he's been quite busy with real life as I understand.