yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Jazz848:
Searched some more and think I found clarification in the Mez forum. I was confused about the nature of the verboten three-button recovery but I believe I understand properly now. If someone could kindly confirm that I have this right, I would appreciate it:

before flashing CM7, we Odin in CWM4fixed, which is specifically for installation of an MTD rom over the pre-existing BML file system. The MTD-based recovery exists on a second recovery partition independent of the original BML recovery partition (which still has CWM4fixed). Obviously, since CWM4fixed isn't programmed to recognize the new MTD filesystem, we can't use it to flash anything to said file system. Conversely, the SD card is never changed from FAT32, so it should still be readable by the BML recovery.

With that being said, though, since the entire filesystem is rewritten when flashing CM7 through the BML CWM4fixed, it makes perfect sense (if I understand correctly) that even after flashing an MTD rom, three-button should be a reliable way of getting out of a bootloop and reflashing a CM7 package. If I'm right, shouldn't that be a standard procedure to fix a bootloop if one doesn't want to Odin back to stock or is away from a computer with ADB or Odin to begin with? Just stop the loop with three button, reinstall CM7 (since it installs over BML or MTD out of the box), and restore your nandroid afterwards from the presumably now-functional MTD recovery?
[Fascinate Android Development] droidstyle:
yea your probably right...what about keeping the newest version paid and releasing older builds as free(obviously from v13 on)? I'm on your side here...I feel that people should donate for the most up to date development. it will help speed thing up by giving your development team incentive to release updates faster?
[Fascinate Android Development] sixstringsg:
That was the plan for the $1.50 version. We'll see, no decisions are being made now.
[Fascinate Android Development] drnihili:
As one of those currently freeloading on your fine work, let me make the following harsh suggestion for dealing with my ilk:

$5.00 gets you the app with release candidates.

$1.00 gets you the app with the current release.

Free gets you the release a month later.
[Fascinate Android Development] sixstringsg:
Now that we're back in the swing of things, we could have two stable releases out in a month's time. The kernel will always be available on XDA, it's not hard to download/flash. Also: we need to move the discussion to the app's thread here
[Fascinate Android Development] neh4pres:
Honestly, my biggest problem with donation was thinking about distribution.. I get a good paycheck with an extra $30 or so and i think about... Well there's six, ssew, tkglitch, jt1134 (made it all possible).., Andmer fixed mms on my device and i run miui.. Supercurio brings my much loved voodoo stuffs.. Sbrissen (added lots of awesome things to my touchwiz experience(still trying to meet up and buy him a few drinks cause he lives near me.. (work schedules conflict though)).... And when i get done thinking who to donate to i feel like if i split it up between you all it would be like a slap in your face.. The app takes away that dilemma, and i hope more devs enact such an app for early access to software. It makes the difference between feeling proud of being 1 of the people who paid for the app that supports the dev, rather than embarrassed that 10 different devs look at me as the chump that donated 3 dollars.

Sent from a beautiful miui fascinate
[Fascinate Android Development] sixstringsg:
I think that a lot of devs feel the same way as I, I don't care how much the donation is. It's appreciated. If five people donate $5, that's $25. I'm not charging for anything, donations are a way that I know that people like my/our work enough to put some money down, no matter how much.
[Fascinate Android Development] .Ejekt:
I'm running ML from the RC app and I've been getting a green tint when the screen dims. Any known causes for this problem. Other than that, the kernel is fantastic. Great work devs; glad to support!
[Fascinate Android Development] akellar:
It's talked about roughly one page ago.
[Fascinate Android Development] sageDieu:
With the donations thing, I personally have never donated to anybody for anything. I'm 16 years old and don't have a job or any income, not even allowance. I do what I can by offering to test and trying to give good bg reports and everything but I still owe you guys something. I have a list pretty much of what i will do with my money once I get a job (which I am looking for one now) and a paycheck; the list (in this order) is gas, insurance, phone data, buy battlefield 3, buy glitch app, donate to strings and efpophis, and then donate to the other devs.

I pick you guys first because you actually support your users and are active here; most other devs whose work I use (specifically JT) do great work and i really appreciate it, but the way the act outisde of that doesn't encourage me to donate. In any of JT's threads if you ask a question then unless it is something crazy important that is also asked by many others, then you will be lucky to just get a normal user who might know the answer to reply. almost never anything from jt; most of his posts recently that I see are flaming people in Enyo's threads.

I'm not saying he should stop doing the work if he can't devote more time here or anything negative towards him, just that if I have a few bucks with which to donate to a developer then I am going to donate to someone who is actively working and helping like you guys; if someone has a question then unless one of us normal users (scarmon, jazz, neh4pres, me) beats you to it then you have a good answer for it. You always respond to PMs and email, etc. and that makes me want to donate to you because you actually have a public presence.

/rant
[Fascinate Android Development] droidstyle:
must be nice to be 16yrs old have a smartphone and everything paid for.:p Im not flaming you, just joking lol. not everybody can donate and that is completely acceptable, but there are alot of free loaders out there that have the means to donate and dont. i agree with you 100% about donating to a active developers, which is why i do. Six is very helpful answering any questions and this is part of the reason i switched to glitch! btw sage you seem to be very mature and educated for a 16yr old!! I have found many of your posts to be respectful and helpful...not to mention you never seem to get caught up in the flaming wars of late. Your contribution to the community is very much appreciated aswell!:)
[Fascinate Android Development] sageDieu:
well thanks for the complement! I always try to be as mature as possible. I am a total nerd and in love with this stuff so I educate myself as much as possible, and I pretty much stay away from anything related to enyo unless it contributes to development. I never let myself get into the stupid flame wars, most of them have been cleaned up because I report them and move on instead of adding to the problem.

and I'm a legitimate freelance graphic designer and learning development so even if I can't donate money, hit me up for graphics or anything else and I will gladly oblige.

Sent from my MIUI SCH-i500
[Fascinate Android Development] ssewk2x:
Thanks, man. It's nice to feel appreciated now and then :)

With that said, tho, please don't bother donating to me. For one thing, the precious little I've managed to hack together is next to nothing compared to the efforts of Tk-Glitch, six, and the others -- especially lately since I've been slacking and they've been kicking ass.

I've already received all the compensation I'd ever want for my minuscule efforts in the form of a slightly better-working phone, a fair amount of nerd-cred, and the metric ****-ton of fun I've had hacking my Fassy. Plus, I already have a very cool job that I enjoy and get paid pretty well for, so I really don't need it. I do this android stuff for fun and bragging rights, and that's all I ever expect or want to get out of it.

So yeah .. send your cash to The Great Ones (i/e: not me) if you want. I'll be sufficiently thrilled if you feel like hitting my "thanks" button now and then :)
[Fascinate Android Development] sageDieu:
fair enough, haha if you say so.

Sent from my MIUI SCH-i500
[Fascinate Android Development] bschrib:
Hey question for anyone else using this + TSMPoolParty 1.5.. Are you getting Screen of Death issues? Occasionally (twice so far today) I go to pickup my phone after it's been screen off for like 5+ minutes and the display just wont come back on. The backlit buttons will activate if I touch them but nothing on the phone ever happens.

I'm trying all of this on RC13 (as of 6PM EST last night) with all stock voltages and OC to 1300. Initially I had the trouble yesterday too @1300 MHz (-100, -100, -50, -50, -50, -25).

Any advice is very much welcomed! :)
[Fascinate Android Development] Jazz848:
+9000 internets

Seriously though, there's not much I can say in agreement that hasn't already been said. You set a standard of conduct that most adults fail to achieve. Good on ya, Sage. Personally, I could stand to learn a thing or two from it.
[Fascinate Android Development] vinal:
+1 with nearly identical setup (1400M less undervolting). I have lots of downloaded apps, so I suspect wakelock issues from one of them.
[Fascinate Android Development] ssewk2x:
Same thing happened to me yesterday on CM7, and I've also had it happen with other ROMS and kernels. I chalk it up to "that's what I get for running bleeding edge software on my phone."

One thing I did notice is that the backlights coming on like that is similar to what would happen with broken BLN. I/e: the BLN wouldn't come on until you touched the keypad. No idea why it would lock the screen up, though, but it could be a clue about where to look for the root cause.
[Fascinate Android Development] sageDieu:
d'awwwww you guysssss. ;D

Sent from my MIUI SCH-i500
[Fascinate Android Development] baron4406:
Getting a ton of "SOD's" with this kernel, after an overnight charge and occasional ones during the day. Never had them before. Tried eliminating the 100mhz step, I'm not undervolting anything as of now and its still doing it. Weird.
[Fascinate Android Development] Jazz848:
Have you checked for wakelocks at all? Also, since it was mentioned a few posts back by another user, are the soft key backlights doing anything during the SOD? I had the same thing happen to me a few weeks back; can't count it here though since I don't recall which kernel I was on at the time...

Edit: Incidentally, does anyone else think "death metal" with all this talk of SOD? ;)
[Fascinate Android Development] schu9120:
I thought I was one of the only ones with SOD (phoma :-) ) issues so I didn't want to raise a stink. Twice, during the day I would click volume rocker to wake then get soft key lights for second then SOD. No undervolt stock MHz. On pool p.

Love the Glitch app and all the help you guys provide.
[Fascinate Android Development] neh4pres:
Everyone needs to try undervolting.. If you get sod turn all to -50 and see if you still get it.. And what governor/scheduler are you running?

Sent from a beautiful miui fascinate
[Fascinate Android Development] shag_on_e:
This is wild, I haven't had the sleep of death once. I undervolt ridiculously(1.4mhz-125, 1.3mhz-100mhz -150) and I've been running rc 13 since it was available. I've been testing this thing to the limits and can't seem to break it unless I go below said undervolt settings . Actually, it seems to only give problems if I undervolt 100 to -175 or below. The roms I run are cm7 nightlies, and MIUI updates.

~~~~There is no spoon~~~~
[Fascinate Android Development] droidstyle:
this fixed what few sod's I was experiencing...but now I just started getting wakelocks. I'm thinking its this nemus launcher I switched to.
[Fascinate Android Development] icemanwbs:
Been running Nemus all day now with no problem at all, undervolted 50 across the board. Keep ya posted
[Fascinate Android Development] ssewk2x:
Well, if no one else is gonna do it, then I call dibs on "Sleep of Death" as the name for my metal band ;)

Shine on, you crazy diamonds..
[Fascinate Android Development] droidstyle:
good to hear! Maybe it was the low leakage kernal not playing nice with my device. Switched back to ML, never had any wake lock issues before, so we shall see.
[Fascinate Android Development] Shinebox:
The links in the original post do not work for me :/
[Fascinate Android Development] sixstringsg:
Don't know what to tell ya, the server is up and running great, and I just checked and I'm getting good downloads.
[Fascinate Android Development] baron4406:
Hmm undervolting for SOD issues? Never tried that. BTW I was running the CM7 nightlies and my governors were BFQ and SmartassV2 with the ML kernel. Just flashed the newest nightly and kept the stock kernel and yes no SOD's.

BTW you young fellas probably don't remember back in the 80's there WAS a metal band called "SOD" but it was the Stormtroopers of Death. Guys from Nuclear Assault and Anthrax formed it. Yea I'm old. :(
[Fascinate Android Development] sixstringsg:
BFQ might be your problem.
[Fascinate Android Development] neh4pres:
It seems that different phones have different governor options.. i have 2 fascinates when both on v12 one has far more governors than the other... And i have never had a smartas v2 that everyone speaks of.. I run miui different builds but always same for both phones, and use pimp my cpu on both.

Sent from a beautiful miui fascinate
[Fascinate Android Development] shag_on_e:
That happened once with me, I believe the three governors from jt's kernel stuck through the Glitch flash. I had to re-flash, I knew the glitch kernel had more governor options.

~~~~There is no spoon~~~~
[Fascinate Android Development] droidstyle:
Just wanted to update that the wakelocks were from the nemus launcher...and still no sod's with -50uv across the board. noop/smartsss 1300mhz
[Fascinate Android Development] sageDieu:
Just gonna say that literally the only time I get SOD issues is when you guys talk about it here. My phone works fine, super-undervolted and awesomeness all around. Then there's talk of SOD in this thread and my phone gets it. every time.
[Fascinate Android Development] ssewk2x:
By Jove, I think you've got it! Ok, no more posts about SOD .. wait .. this is a post about SOD .. oh, no, I said SOD again! Aaaaaaagh!

Ecky Ecky Ecky p-tang, zooop boing! *mumble*

(Nee!)

Edit: How appropriate that this ends up being my 420th post ...
[Fascinate Android Development] bigmike88:
Strange, I had Sod once like 30 min after flashing rc 13. never again since though....

Also had a minor force close issue with a few gapps, wiping market cache did the trick tho.

any luck with that deep idle?

Edit; Oh and the keyboard popup and random soft key bug that PLAGUED me on all other kernels, I no longer experience it with rc 13! At least in the basement dead zones I'm used to... Seriously, thank you guys so much for your continued efforts.
[Fascinate Android Development] sixstringsg:
It might be because of pimp my CPU. There is no way governors/schedulers persist through kernel flashes.
[Fascinate Android Development] Bubbadogg14:
Damn you ssewk you asshole I SOD for the first time in a really really long time after reading this post you **** lol. I'm still on v12 so I think it was just a really odd coincidence since it never happened until I read this. Anyway keep the good work team glitch I am anxiously anticipating (oh yeah alliteration what you know about that lol) the final release of v13

Sent from my SCH-I500
[Fascinate Android Development] ssewk2x:
LOL, glad I could help?

Yeah, SOD happens so infrequently for me that I basically don't care much about it anymore. Success through apathy, for the win.

I actually flashed my phone back to one of my V12 development kernels today. The V13 release candidate seemed a good bit slower and less snappy for me. Plus I still need my ugly-ass hacks to try and figure out the whole audio issue and it was easier to do that than build a fresh one. Also found out I can crank up to 1.5Ghz at -75mv :D
[Fascinate Android Development] 123SIT:
I had been getting Sod every morning after been plugged in overnight charging. Changed io scheduler to noop and governor to smartass v2 and no sod this morning. No undervolt in use either.

Sent from my Glitched CM7 Mesmerize
[Fascinate Android Development] Jazz848:
I'll be impressed when you bring me a damn shrubbery.

A larch will also suffice.
[Fascinate Android Development] Jazz848:
edit: off-topic
[Fascinate Android Development] xain713:
Hm I'm using pimp My CPU and don't see smartass v2. :0
[Fascinate Android Development] sixstringsg:
What kernel are you on?
[Fascinate Android Development] xain713:
nvm I uninstalled and reinstalled pimp my CPU it showed up after, I'm on v13 rc1 HL
[Fascinate Android Development] neh4pres:
Ill try this

Sent from a beautiful miui fascinate
[Fascinate Android Development] tripacer99:
No longer able to reach 1.7/1.6/1.5 at any voltage settings after flashing v13 HL & ML

Guess its back to v12 beta for me :/
[Fascinate Android Development] neh4pres:
Try undervolting more

Sent from a beautiful miui fascinate
[Fascinate Android Development] Disneycast25:
I'm running cm7 and I'm trying to overclock it to just 1.3. Everytime I try it freezes and reboots. I've ran the script cleaner. Would the I/o scheduler, or the governor have to be on a certain setting?
[Fascinate Android Development] sixstringsg:
We set the IO scheduler and the governor to what we set them to for a reason. They are the most stable. Have you read the FAQ?
[Fascinate Android Development] Disneycast25:
Sorry. I hadn't finished reading through them, but I got it now. Thank you.
[Fascinate Android Development] knoxjon:
Ok, I give. I have read the FAQ a dozen times and have read about the voltage control app - and have used it for some time. I know the default settings are considered the most stable for the most phones, but I still want to know more. My phone has five different choices for scheduler and nine for governor. Is there an actual FAQ somewhere that explains what all of them actually are/do?
[Fascinate Android Development] sixstringsg:
http://xdaforums.com/showthread.php?t=1242323

It's not perfect, but it's close. It wasn't written for our kernel, but should work well.
[Fascinate Android Development] shag_on_e:
I pushed mine to 1.6 yesterday for the first time didn't even hiccup. That joker was crazy fast multitasking.

~~~~There is no spoon~~~~
[Fascinate Android Development] knoxjon:
I hate to clutter the thread, but I have to say it out loud: you rock.
[Fascinate Android Development] exzacklyright:
Hope this gets implemented as well in v13 :)
[Fascinate Android Development] joshkoss:
looks like it's getting put into the tomorrow's cm7.1 nightly also :)

http://review.cyanogenmod.com/#change,9773

flashing it now :)
[Fascinate Android Development] shag_on_e:
I'm wondering if the changes would stick if one were to flash back to Glitch, like last time...Don't wanna boot into the wrong recovery trying to find out though. Guess I'll unzip and compare files...

~~~~There is no spoon~~~~
[Fascinate Android Development] sixstringsg:
Unzipping won't help. I havent looked at the changes yet, but I'm almost sure when you flash back to Glitch it will revert the changes.
[Fascinate Android Development] neh4pres:
Why are you scared of booting the bml recovery? There is nothing it can do to your phone.. You just can't wipe data/cache.. Or flash roms.. That don't mean paying it a visit is a bad thing.
[Fascinate Android Development] shag_on_e:
Yeah, once I thought about it, I forgot this fix involves recovery stuff so I figured as much.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
I'm looking into the recovery thing, along with some other stuff. Fun times.
[Fascinate Android Development] shag_on_e:
You are appreciated sir.

~~~~There is no spoon~~~~
[Fascinate Android Development] droidstyle:
Just wanted to report that I flashed to jt's 3 finger kernel and flashed back to glitch, tried to three finger and the phone just reboots normally ...just a fyi for those wondering if the patch would stick.
[Fascinate Android Development] exzacklyright:
I keep seeing v13 RC then realizing it's the TELUS ONLY thread. :(
[Fascinate Android Development] ssewk2x:
So I got to do some fiddling yesterday (and will hopefully get to continue to fiddle today). Thought I'd give a progress report.

1. I pulled the latest device tree from CM7 - turns out that was a mistake. Using it, I'm currently unable to produce a booting kernel with the CM7.1 stable release. So be warned that there may be an upcoming incompatibility between CM7 nightlies and Glitch. For now, I've gotten my environment working again and can build stable kernels starting from V13 and adding my hax, so all (read: most) is right with the world. I'll investigate this further when/if it really becomes a problem. For now, I have my own fork and branch of the device tree which I reverted back to approx Oct 23 (+JT's changes for 3-button) on Github, and I'm building against that instead of the latest CM7 stuff.

2. As part of the above, I cherry-picked JT's 3-button recovery fix into my device tree. It didn't seem to do anything, but upon inspecting the ZIP file JT released, I think I know how to duplicate what he did with our kernel. It's on my to-do list, and shouldn't be too hard unless I'm completely wrong.

3. I'm almost ready to test a completely new way of handling leakage. Instead of having to build 3 separate kernels for LL, ML, HL, I plan to allow you to configure the leakage under the GLITCH menu in recovery, similar to how you can currently configure screenstate scaling. As long as the code I'm writing doesn't introduce a bunch of instability, this will mean 1 build per phone instead of 3, and a much easier time of automating that stuff for us, the devs. Plus, you the users will be able to experiment with leakages a little easier. Also, I managed to incorporate the gnarly red-spatter glitch recovery into my builds, which is frikkin SICK. :D

4. Still working on that speaker echo BS, too. What a pain in the ass. Nothing overly new to report here except I successfully migrated my changes to be based of the V13 source. Would anyone be interested in helping me figure out what's going on? It would (vaguely) involve flashing a TW based rom and custom (by me) kernel for a day or two ...

As always, if you want to track my work in real-ish time, keep an eye on my github at https://github.com/Efpophis.
[Fascinate Android Development] droidstyle:
buy the app then you will see it on your device

;)
[Fascinate Android Development] joshkoss:
I noticed on nightly 99 the glitch app (Which i purchased) aborts the install during the RC install. :cool: all other builds, work fine.
[Fascinate Android Development] PhoenixPath:
Any chance of this being configurable via the Glitch App as well? (May require a boot to activate, but it's still better than reboot-recovery-reboot)

Thanks again.
[Fascinate Android Development] ssewk2x:
Well .. maybe. If I had the source to the app (which I don't), then I could possibly give it a shot. Or I could communicate the details to Six and he could give it a shot. Since it's a change that needs to be applied ASAP on bootup, I thought recovery would be a good place to put it (and since I have source for that, lol).

The way I've done it, if you know what you're doing, you can configure it yourself by hand without needing recovery. Whenever this gets released, I'll be sure and have full details written up in the changelog.

Edit: incidentally, I just tried kanging JT's 3-button fix and ended up flashing a recovery that wouldn't load. <3 Heidmall ...
[Fascinate Android Development] tripacer99:
Was about to update cm, but then read yours and ssewk2x's posts. Thanks for the heads up.

Up to Nightly #98 I go!
[Fascinate Android Development] sixstringsg:
We will work on getting it into the app.

Yeah, I tried that as well, didn't work so well. It has something to do with the kernel bundled in the device tree I believe, but it's compiled so we can't see what's inside.