yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] sixstringsg:
The BLN times out if it isn't set to blink. Are you sure you're not just missing it due to the timeout? Try a test in BLN control or Blinky.
[Fascinate Android Development] jmac9:
Couldn't get Blinky to work....even the test mode. Wiped cache and rebooted and was able to get BLN Pro back. Set to blink and now I have BLN back. Thanks!

Edit: Well email/calls get the BLN. But no text.
[Fascinate Android Development] davwman:
anyone using this with vanilla gb
[Fascinate Android Development] sixstringsg:
I've heard people with success with it, yes.
[Fascinate Android Development] davwman:
ok. just wanted to make sure the two were compatible. I know they are both aosp counterparts.
[Fascinate Android Development] jmac9:
Ok so BLN control only works with phone and Gmail. Other Email and SMS get no BLN and have lost data twice today......hadn't lost data since I don't know when. Any ideas again anyone? I have always liked Glitch from the very begining and have bounced back and forth lately with jt's......want to work this out if anyone has some suggestions?
[Fascinate Android Development] scarmon25:
If you configure the apps in CM7 led notification settings. Then they seem to work with bln enabled based on how they are set in there. Does for me.
[Fascinate Android Development] jmac9:
Thanks....I'm on MIUI though.
[Fascinate Android Development] PhoenixPath:
System - LED Settings, on MIUI.
[Fascinate Android Development] jmac9:
Yep... been there and it is turned on. Have used BLN before....and had no issues. Going to try and flash again and see if that helps.
[Fascinate Android Development] neh4pres:
Wow.. Just want to state v13 rc is the most stable I have seen glitch..I have always been able to run 1700 if it was the only state selected and my undervolt was right.. But I ran it last night with all the steps active for like a half hour before I froze.. Using smartass and deadline, I took a screen shot of CPU spy with a glimpse of how it ran. I'll put it up when I get to a computer.. nice progress whatever you guys did. Hope someday letting the system step itself to 1700 will be as stable as any other step.. Ill be buying a second copy of the rc app for the girls device. Thanks :p

Sent from the fascinate that holds the record on antutu benchmark
[Fascinate Android Development] calebv2:
This kernel gives me so much more battery version 13 rocks I can make it all day now tel I go to bed to put it on the charger.
[Fascinate Android Development] calebv2:
Double post sorry
[Fascinate Android Development] rjskalet:
are you on the latest beta and which leakage?? because i have had the same issue and i have turned almost everything on and it still doesnt seem to work....i havent quite figured out what i have been doing wrong.
[Fascinate Android Development] sixstringsg:
V12B3 doesn't work with BLN. V13 does though.
[Fascinate Android Development] jmac9:
V13. ReFlashed the miui room and then flashed EC09 radio...hadn't changed radios since EC01. All is good now. Great kernel!
[Fascinate Android Development] PhoenixPath:
Six, would you be offended if I suggested updating the OP with a link to the RC app? Might help direct some traffic and questions.

(if you would be offended, please know that I would never take it upon myself to make such presumptuous suggestions.)

:-D
[Fascinate Android Development] sixstringsg:
There is a link to the thread in the OP. I can't link to the market in this thread based on XDA rules because its "promoting paid apps".
[Fascinate Android Development] PhoenixPath:
Ah...sorry, I ...

...have a cold.
[Fascinate Android Development] bschrib:
Sorry but I'm a bit confused -- So V13 RC is getting rave reviews and comments but it says it's only for Telus Fascinate?

Is everyone rocking a Telus Fascinate as opposed to the Verizon Fascinate?

I've tried the two DEV builds in the root FTP (CM7Fascinate-Glitch-DEV-20110720-xx.zip) but both of them result in non-boot status (forever stuck at Cyanogen loading screen) even when I ensure clear cache/dalvik before hand.. :(

Just trying to find some glitch love. :)
[Fascinate Android Development] sixstringsg:
The links are in the OP for what you can use. What you flashed is from June, and doesn't work anymore. V13RC1 is available through the app linked in the OP, and V13 official should be around in a day or two.
[Fascinate Android Development] Azuma73:
Quadrant Scores??

I bought the app, kernel is awesome, as always. I'm running HL like I usually do and everything is working very smooth and fast!

I was just wondering why my Quad scores are so much lower than they were before V13? I know they don't really mean much, but just thought there was an explainable reason for such a big difference in scores?

How will we know when there is an update, just by following thread or will it show up as a market update?

Thanks guys and job well done, once again!!:confused:
[Fascinate Android Development] sixstringsg:
In the future, please post in the app thread. It's linked in the OP. As far as quadrant, I have no idea, I haven't run it since the eclair days. There are so many variables in Quadrant, there is no way to tell.
[Fascinate Android Development] neh4pres:
I have found that the performance governer does not hold a high CPU state on v13 for me.. Try setting your highest freq to minimum and see what happens.

Sent from the fascinate that holds the record on antutu benchmark
[Fascinate Android Development] bigwilly90210:
Getting ~3000 at 1600mhz with smartass and deadline. Rock solid too. Forgot I left it at 1.6 (overnight on the charger) until halfway through the next day. Ha. Keeping it at 1.4 for daily use. Great battery, totally smooth. Unbelievable performance. I love my phone again! Haha. Also, V13 plus EC09 locks to 25ft in 5 seconds tops and gets down to 5ft within 30-45 seconds. PURE AWESOME. Thanks guys!
[Fascinate Android Development] pntballer505:
I'm not too good with voltage settings, but I do like how the glitch kernel performs on my phone. Right now I'm using cfq/on demand. What's the difference between that and deadline/smartass? Also, when I open Voltage Controls, i see the max

at 1000mhz. Is that what you mean by 1.4?
[Fascinate Android Development] bschrib:
Sixstring, not that I'm not happy to send money to great developers like yourself but as to your RC app do you plan on updating it (changelog, version being installed, etc)? Also any idea if you'll be getting the new nexus? My fascinate will be retired soon and I'll sorely miss your work. :)
[Fascinate Android Development] Jazz848:
Page 1, 3rd post, item 8.
[Fascinate Android Development] pntballer505:
Ah...right. Thank you.
[Fascinate Android Development] neh4pres:
What is the fascinates most recent radio release?

Sent from a beautiful miui fascinate
[Fascinate Android Development] sixstringsg:
An update will be out soon. It does tell you what version is being installed already though. As far as the Galaxy Nexus, I'll have to get quite a big donation to get that. We'll see, but I doubt it's likely at this point. It's a little underwhelming hardware honestly, and I'm on AT&T, so it'll be out later anyway.
[Fascinate Android Development] pntballer505:
Question: So I was playing around with my voltage settings and

followed the instructions in the OP, but when i choose "Save as boot settings" in Voltage Control, it doesn't seem to save them. The Voltage settings i set seem to reset..
[Fascinate Android Development] fstbusa:
try using pimp my cpu and see if that works.
[Fascinate Android Development] sixstringsg:
Did you apply them as well? Also, don't ever set on boot until you know it is completely stable.
[Fascinate Android Development] pntballer505:
Yes I applied them and set it to boot settings, in which it created that voltage file.

And I'm aware of that! Went through some trials and tested the stability

with stability test and neocore. Thank you.
[Fascinate Android Development] pntballer505:
MIUI 1.9.16 (soon to be 1.10.28).
[Fascinate Android Development] xain713:
i recently bought a 32 gb sd card for my fascinate and it unmounts quite a bit, im using the glitch v13 rc ML, is this a known problem or just a bug xD just wondering and is there anyway to stop this from happening?
[Fascinate Android Development] mrjake1970:
i have to say that V12 ML is by far the best kernel i have ever had on this device..im getting 18+ hours out of the battery vs 8-9 hours with the same usage patterns on other kernels - including V12 HL!!! .. its lightning fast, and using voltage control im undervolting and overclocking at insane values (for my unit) and its completely stable.

ive never been able to run any kernel to uv more than -50 on any steps without lockups or SOD.. with this kernel, i am uv at -50 from 1440 down to 1200, -100 at 1000 and -150 at 800 to 200.. ive played and can get 1500 thru 1700 to run fine as well - but i dont want to push my luck with lockups.. so i keep those frequencies disabled most of the time.. but when they on? wow..

amazing and stable...rock on and thanks to all of the devs that put this out on this! i can't wait to experience the release of V13 which after reading the threads, is even better than V12..

i only have one question.. in VC i have the 1400 step disabled..yet, CPU spy is telling me that it's using that step quite a bit..even though its disabled..and yes, i have reset the clocks several times to check that. it still wants to run that freq..is that normal?
[Fascinate Android Development] sixstringsg:
Disabling states doesn't work in any CM7 kernel to date, so that's why it still shows up.
[Fascinate Android Development] ssewk2x:
I fixed that in an old tw-based kernel...I'll have to take a look.
[Fascinate Android Development] neh4pres:
That would be cool.. It may make 1.7ghz more stable to disable a bunch of other high clock states

Sent from a beautiful miui fascinate
[Fascinate Android Development] kallell:
So I noticed, with rc1, we are back on the issue of the screen tinting yellow once it goes idle for 30 seconds or so. It's fixed by messing with voodoo colors, but this was something we ran in to WAY back when glitch first got us a mez/fas version.

Any ideas six?
[Fascinate Android Development] sixstringsg:
It doesn't work the same way as TW did. We haven't looked at it in a while though.

Well not way back, V11 had it. There is no good solution. Fixing it breaks black/white gradients.
[Fascinate Android Development] jt1134:
Kernel drivers, libs, and daemons must all match. You can mix and match on any ROM. Froyo libs all have Yamaha in the name, daemons have sensor in the name. Just peek in /system/bin and lib on a ROM that uses them. Also libsensorservice.so would need to be pulled from an older build, as it needs to be patched to work with older sensor drivers.
[Fascinate Android Development] ssewk2x:
Ok, thanks, JT! I think I get what's going on now. I'll have a closer look tomorrow and see what I/we can hack together.

Six just sent me an interesting looking pull request, too.. :)
[Fascinate Android Development] sixstringsg:
Who was asking if we needed help with merge? PM me and we'll talk about it, it's a long and tedious task with how many commits there have been since Glitch got sick, so we need help. If anyone has any suggestions on how to make it easier as well, let me know, because I'm sure I'm not doing it the most efficient/easiest way there is.
[Fascinate Android Development] Bubbadogg14:
Is tk glitch doing well? I hope he is making a speedy recovery. My prayers are with him.
[Fascinate Android Development] sixstringsg:
Honestly i havent heard from him in quite a while. He's taking a break from coding for a bit.
[Fascinate Android Development] Bubbadogg14:
that's a good decision. Health is the most important.
[Fascinate Android Development] gabe565:
This is a little off topic, but I've always wondered, why does cifs (Mounting samba shares) work on the glitch kernel, but not on jt's?
[Fascinate Android Development] sixstringsg:
I believe that we added support for that through a module, and that's why. I could be wrong though, since I don't use it.
[Fascinate Android Development] sageDieu:
It was me that offered to help witht the git stuff, strings... I took a look at jt's stuff and decided to take back that offer. haha way over my head, I've played with basic stuff but it gets very complicated very quickly.
[Fascinate Android Development] ssewk2x:
Holy sweet mother of crap!

So, I just merged nearly every commit on JT's github since July 20 (the last time Glitch did stuff), except for the changes that were already present, and except for the commits that seem to have caused the SD card bug. I even grabbed the latest "torch fix" one from today, though that seems to need a modified CM7 torch apk or something to go with it? Idk. Oh, hell, if you want to see the log, go check out the history on my branch:

https://github.com/Efpophis/POFS/commits/jt-merge-exp-take-2

I'm building kernels right now from that branch. All I know for now is that it seems to compile ok. I have not tried to flash it yet, and it probably wouldn't work as-is on phones that don't have the GB libraries and binaries. I have to figure out what to do about those yet, so no one do anything crazy like try to grab that, build it, and run it on your phone. You've been warned, lol.

Side note: I'm actually using my phone to ssh into my box at home to do the builds. How badass is that? Can't stop the signal ...

Anyway .. it would be super awesome if someone who knows a little more about this than me could have a look and see if that branch looks right. I'm a little scared about some of the ones I skipped.

Thanks guys (and gals if there are any here) :)
[Fascinate Android Development] kallell:
Thank you ssew! Let me know if you need testers.
[Fascinate Android Development] bigwilly90210:
Saweet. What's the worst that could happen if one of us was to try compiling it? Lol. I really wanna try it out, missing that awesome glitch touch on my phone. If there's any kind of crazy alpha testing you need I'll be up all night. :-) ha. I'm just stoked to see someone working on it.

And to whoever said it before, I really do miss the torch too. I'll prolly freak of that works too. Ha.
[Fascinate Android Development] sixstringsg:
Well done you know how to compile? You're always welcome to.
[Fascinate Android Development] Bubbadogg14:
I'm using jts 9/12 kernel and its not as fast as glitch n the chiles don't look as nice but its pretty darn smooth and having the sensors and torch working is awesome. (the torch is nice :) ). I czerny wait for all that 2 come 2 this kernel!! Keep it up ssewk and six u guys r turning into a hell of a team!
[Fascinate Android Development] ssewk2x:
You all can be sure that once we have something worth testing (as opposed to something guaranteed to not work), we'll let you know. Six and I will coordinate and make sure to deliver something that's comprehensive and that we both agree is ready for the masses to try out .. it's still going to take some time, though.

For my earlier post, I just felt like I had made some good progress and figured the community would appreciate an update. I know from having been in you all's shoes that it's nice to have progress reports now and then.
[Fascinate Android Development] bigwilly90210:
most definitely. i'm in the process of building a new main desktop box and the one I'm using is only a notch above my phone (seriously, 2.0ghz AMD single core with 512mb. the fascinate prolly has a better GPU lmao) so compiling isn't in the scope of my capabilities right now. mostly cause i don't have the time to setup my linux on here like i want. lol.

and i for very much appreciate any update. even if i can't test anything myself right now its nice just to hear how awesome you guys are doing. can't wait to have a fully functional glitch kernel with cm7. there's no way i need to upgrade. i'm blowing my friends away with their inspires and their infuses. lol. Thanks guys!
[Fascinate Android Development] sixstringsg:
While he is working on fascinate specific stuff, I am doing LPM and BLN (hopefully)
[Fascinate Android Development] ssewk2x:
I think I may have pulled those into my experimental merge branch as well. Oops .. ?
[Fascinate Android Development] sixstringsg:
That's fine, don't worry about it.
[Fascinate Android Development] bigwilly90210:
hey where is everyone getting this new 9/12 updated kernel? with the torch? am i missing the thread? i tried searching... idk where thought. rootzwiki too
[Fascinate Android Development] kallell:
No problem, ill just keep my values under 50 :D.

One other thing i noticed -- the clock is a minute fast? Tell me someone else has this issue too, so i dont think i'm going crazy.

Just tested, its actually 67-68 seconds fast.
[Fascinate Android Development] GizmoDroid:
For CM7:

If you have your "Screen colors multipliers" at their default setting in Voodoo Color, then you need to raise the Screen dim level to 24 in the settings to prevent the green tint. To do this, turn on "Use custom" under Settings > CyanogenMod settings > Display > Automatic backlight, then change "Screen dim level" to 24.

If you prefer to turn all of the "Screen color multipliers" to their highest setting in Voodoo Color, you can lower the Screen dim level to 14.

You end up at about the same brightness level when dimmed, so go with whichever one you like better.
[Fascinate Android Development] Not_So_There:
Reboot problems.

I've noticed that when using the v13 RC1 LL kernel that if I lower the boot voltage for 100mhz below -200 the phone will not reboot or go into recovery when I select it. If I then remove the battery it will boot up fine with those voltage settings. It just that it will not reboot on it's own.

After rebooting and changing the boot voltage back to just -200 it still will no longer reboot or enter recovery without a battery pull until I clear voltage settings in the recovery. I can then reset the 100mhz boot setting back to -200 and reboot fine.

I am using the paid version of voltage control.

Edit, Fascinate CM7 7.1.0 Stable.
[Fascinate Android Development] akellar:
So don't lower the voltage that much?
[Fascinate Android Development] ssewk2x:
Yeah, mine does that sometimes, too. Make sure you have it set to synchronize your clock with the network. If that's already set, then it should correct itself eventually.

Computers, and especially phones that think they're computers, tend to make lousy clocks unless they were designed to be clocks in the first place. So some inaccuracy is to be expected.
[Fascinate Android Development] TheHobbyist:
Any chance of us lowly app non-owners getting access to 13 RC? My phone could really use some glitch!
[Fascinate Android Development] neh4pres:
V12 works great

Sent from a beautiful miui fascinate
[Fascinate Android Development] Jazz848:
I know this sounds crazy...

NOTE: I've searched the thread for a previous answer on this but didn't find anything. If this has in fact already been answered, just say so and I'll happily go back to searching (albeit slightly red-faced).

Running V13 RC1 HL on a clean install of CM7 Nightly 91, I downloaded Nightly 93 via Rom Manager. From there, I rebooted to recovery, wiped cache and dalvik, and flashed #93. Midway through the BML/MTD check, I got a bootloop (Samsung logo, CM logo, quick .5 second shot of recovery mounting the SD to install and borking, repeat.) Okay, pretty sure there's nothing alarming there, sometimes crap happens. No luck with ADB, so I got ready to fire up Odin. Just for kicks though, I went into the blue BML recovery via three button (I know, no three button with MTD) to see if rebooting from there would stop the bootloop; as expected, no dice. Figuring I had nothing to lose at that point since Odin was looking inevitable, I went to three button again and, despite the expected mount error messages, selected "Install zip from SD card," navigated to the #93 zip, hit install, and my jaw dropped. I got the BML/MTD check followed by an "install complete" message before the phone rebooted and loaded up CM7 without a hitch. Flashed V13 RC1 HL via the app and counted my blessings.

If I missed something about three button recovery, I'm sure I look pretty stupid right now. As far as I know, this should not have worked, but my Fascinate's been running CM7 #93 w/ V13 RC1 HL without a hiccup. I feel like I'm asking to be ripped on for even posting this whole thing, but it messed with my head and life makes no sense anymore.

Oh, and I posted this here since I was running glitch prior to the bootloop. If this belongs in the Fascinatemtd Nightlies thread (or deleted altogether), feel free to send me packing! :confused:

**I get the feeling I may lose at the Internet as a result of this**
[Fascinate Android Development] sixstringsg:
It will be out soon. I'm guessing you would like me to test for random dangerous things on my phone instead of you on yours. We are really close.
[Fascinate Android Development] droidstyle:
this is not the first time I have herd this happening...your not suppose to three finger but hey if it worked for ya... I have tried this before on my fassy after getting bootlooped and it would not work lol. These mtd roms seem to have a mind of there own.

---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------

I honestly think you guys should offer a free version and the donate version that gives you "extra" options, but maybe this was in the plan already...if so Im all for it, you guys deserve a little extra for what you guys provide for the commmunity!
[Fascinate Android Development] sixstringsg:
What would you like in the free version?
[Fascinate Android Development] scarmon25:
Maybe like the controls for the kernel. The screenstate scaling and logcat and stuff like that. I hate to say it but in order to get access to the RCs you should have to pay. Its free once its released. But early access cost

Just another post made by a CM7 junkie. :)
[Fascinate Android Development] droidstyle:
I already purchased the paid version...but I say limit the free version to the file only. keep the app as donate only.
[Fascinate Android Development] sixstringsg:
I agree with you about the pay part. The rest of the post has nothing to do with your reply, I just didn't want to make two separate posts.

In the future, there will be a second app. It will not be free, but it will only be $1.50. It won't be free for two reasons. 1) I and others already spend hours working on this kernel for the community. We get the occasional donation, but until we released the app the donations that I received didn't even cover server costs, so I was personally operating at a loss. If you can't spare a dollar, then I don't know that I want to spend time doing things for you. 2) None of the devs use the apps, we have our own scripts that we use, so these apps are purely for users. I am not putting ads in the app, it's a hassle and 90% of you use an adblocker. Therefore, it has to be in some way shape or form worth our time to put out another app, even if it is only a single dollar per download.

To be honest, nobody would buy the app just to support us. They would get the RC that they wanted, and not care. All of the people working on this kernel/app have donate to me buttons under their names, and until this app I had been donated hardly anything, with coreym making up more than half of my entire donations, so I have no reason to believe anybody would buy it if they could do it for free.