yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ssewk2x:
Yeah, I thought I had done that. That's also why I flashed vgb - just in case I had some old binaries laying around. I'm pretty sure there is something wrong in the kernel itself still.

I had all of jt's binaries and .so files in place .. The kernel was the only difference between working and not - even on the latest vgb.

Edit: damn you, swype
[Fascinate Android Development] sageDieu:
that's odd.. maybe theres some way you can copy specific files from his to yours and test like just the accelerometer or something, like just one sensor at a time?

just a shot in the dark, I really have no idea if that is possible. :P

Sent from my MIUI SCH-i500
[Fascinate Android Development] jt1134:
Fwiw, I have yet to update the vanilla ROM with the new sensor blobs. I've just included them with any kernels that i've distributed.

I looked at your sensor commit, everything looks fine. I may have failed to mention before that you'll also need an updated sensors.default.so from a gingerbread ROM.

If there are still problems, send me a logcat and dmesg from a fresh reboot.
[Fascinate Android Development] sageDieu:
Haha apparently I'm limited to five thanks a day, haven't seen that before. Sorry if i don't seem grateful today, boosting strings put me over the limit :P
[Fascinate Android Development] gabe565:
Is there any way I could use cifs with jt's if I wanted to try his newest kernel out?
[Fascinate Android Development] ssewk2x:
Ok, that might explain something.

Is the last cm7 nightly a good place to get that

Sensors.default.so ? And where does it need to be placed when flashed?

I'm also seeing in my /system/lib: libsensor_yamaha.so, libsensor_yamaha_test.so, and libsensorservice.so

But I'm only seeing libsensorservice.so and libsensor_yamaha_test.so in your kernel update .. could that libsensor_yamaha.so be screwing something up if it's not replaced with one from a GB rom?

Also, what's bcm4329.ko? I know it's a kernel module, so I'm wondering if its safe to steal yours or if I should use the one that's part of this kernel?

Thanks, JT. You da man!
[Fascinate Android Development] sixstringsg:
Ask him, its his kernel.
[Fascinate Android Development] jt1134:
Pull all the sensor files from one of my newer kernel zips. Sensors.default.so goes in system/lib/hw. The bcm module is the wifi driver. You have to use the one built with your kernel each time or the kernel will refuse to load it.
[Fascinate Android Development] ssewk2x:
Ok, that's what I thought and what I did.

Ok .. that's exactly what I did last night, using your 9/12 kernel update .zip. And I made sure I got the sensors.default.so into system/lib/hw also. In fact, I made sure everything landed right where your ZIP would have put it.

I'm leaning more and more towards the idea that I missed something in the merge. So .. I re-did it this morning with a completely different approach:

git merge jt1134/android-samsung-2.6.35

<resolve conflicts> <commit>

git merge jt1134/vanilla_gingerbread

<resolve conflicts> <commit>

Does that seem like a reasonable way to do it? Did I miss anything else I should try to merge in?

There actually seemed to be less conflicts than I got when I cherry-picked individual commits. I have yet to determine whether the result will even build or not, though. It's on my github branch "merge-exp" if anyone wants to have a look. I won't be able to compile it until I get home later and get some baby-free time.

I just now switched over to the last CM7 nightly to be published, and then flashed JT's 9/12 kernel update. Confirmed that torch and sensors are working just fine with it. Now, I'm hoping that I can build my "merge-exp" branch, flash it, and everything will be great.

BTW, nice work on the accelerometers! I notice a wildly faster response time out of them now - at least I know what to look for when I test my stuff. Thanks for walking me/us through this.
[Fascinate Android Development] jt1134:
Don't worry about the Android-Samsung-2.6.35 branch, it's the same as my vanilla branch minus a few changes that don't fit cm's model. Cherry-pick is recommended IMO, so if there are conflicts you can sort them out one at a time.
[Fascinate Android Development] ssewk2x:
Let's see if we can get JT up to 1337 thanks ;)

I did my part.
[Fascinate Android Development] Azuma73:
Where is this 9/12 build? I'm feelin' extra lazy today!!:D
[Fascinate Android Development] sixstringsg:
As stated earlier, there isn't a 9/12 build of the Glitch kernel.
[Fascinate Android Development] Azuma73:
Oops, sorry dude!!:rolleyes:

I see that it's in reference to JT's action!
[Fascinate Android Development] ssewk2x:
So I got another merge attempt together. But, I seem to have removed voodoo color, lol! I need to get that back and then try to get a build together. Right now I've got a baby sleeping on my lap, tho. :)
[Fascinate Android Development] shag_on_e:
I wish I could double thanks every post that comes from you, sixstringsg, or jt1134. All three of y'all are the beez neez! Along with everyone else taking time to make this phone more phun!

Sent via Morse code.
[Fascinate Android Development] sageDieu:
freaking adorable, you better be teaching that thing how to merge and compile. you could be growing your own customized buildbot :D

Sent from my MIUI SCH-i500
[Fascinate Android Development] xain713:
in going to give it a try
[Fascinate Android Development] neh4pres:
My bad.. It is pimp my cpu with that feature..

It automatically will load profiles at different times.

You get to choose when what profiles get used

Options are

Plugged in

Screen off

Battery <	40

<30

<20

<10

So you have a pretty good range of control.. But i started using vc again because i did not know how it would affect glitch.

@tk-glitch you mentioned for ppl to give ideas. Maybe a selectable sleep governor for pimp my cpu users.
[Fascinate Android Development] sixstringsg:
The issue with that implementation is that then Pimp my CPU stays in your RAM, and stays open all the time, using system resources.
[Fascinate Android Development] scarmon25:
That is one major advantage to voltage control over pimp my CPU. Voltage control loads a script in etc/init.d and spent have to stay running. Pimp my CPU doesn't. It seems to have to run all the time to maintain your voltage settings. I preffer to use a script instead.

Just another post from a CM7 junkie.
[Fascinate Android Development] shag_on_e:
I'm loving how thorough logcat is on V13, not that I completely understand the output, but for debugging it looks to be top notch. Once again, I love this kernel and Team Glitch.

~~~~There is no spoon~~~~
[Fascinate Android Development] xain713:
So i take it that is what caused my batter to go down faster, i was using pimp my CPU ,after uninstall is there any files i should delete after?
[Fascinate Android Development] Not_So_There:
I still had the issue happen once after trying your fix.

I had not adjusted any settings at all so none of the files should have been rewritten but I checked to make sure it was still setup with your fix and it was there.

It does not seem to happen all the time, but when it does it seems to be when I am doing something like texting and turning the screen on and off rather then after it has been sitting for a while.
[Fascinate Android Development] sixstringsg:
it shouldn't make that big of a difference, but it is possible. As far as I know, there isn't anything to delete for pimp my CPU.
[Fascinate Android Development] droidstyle:
Question, How do I get my voltage settings to stick? Meaning, after I flashed glitch v13, I set my settings in VC and they stuck. Now when I try to change the settings and "reapply save settings at boot", my previous settings still remain. I have deleted boot settings in VC, also tried deleting voltage settings in cwm,,no luck. thx
[Fascinate Android Development] exzacklyright:
I had the same issue but then they magically sticked

Sent from E.T.
[Fascinate Android Development] chrisj22:
ive been having trouble with the touch keys never working. ive tried on EE19 And EH09 and different ways of flashing and they never work. anyone know what to do or what im doing wrong?
[Fascinate Android Development] pntballer505:
I've been messing with BLN to try and get it to work.

Still no luck. It will come on for about a second, then remain

off no matter what i do.

I did notice that while the phone was charging from the computer,

BLN decided to work. Strange.
[Fascinate Android Development] sol_671:
Same here on the strange part, but mine started working when I started using RickS' MIUI version, then tried dfgas's version then it went away.
[Fascinate Android Development] Enyo.:
Would you be interested in implementing my "Focus" Governor in next release?
[Fascinate Android Development] sixstringsg:
What's good about it?
[Fascinate Android Development] Enyo.:
Uses the lowest frequency and highest frequency at all times. Any load will cause it to jump to the highest. Screen off also jumps to the highest. Gives better responsiveness and speed. Battery maybe would decrease though.
[Fascinate Android Development] sixstringsg:
How is that different than the performance governor?
[Fascinate Android Development] Enyo.:
Uses lower frequencies. I have to do some work on it though.
[Fascinate Android Development] ssewk2x:
Well .. ****.

Shame on me. So I was looking at the screenstate scaling script today, and I noticed there are a LOT of bugs in it. Things like certain parameters not being set correctly because I put them into the wrong (and non-existant) sysfs path. Ugh! So .. I basically completely re-wrote the thing.

Rather than release a whole new glitch kernel, I decided to put out a patch. The patch can be flashed in CWM, and will do the following:

1. clean up any old screenstate scaling stuff that's laying around

2. put a new S99screenstate_scaling file there and configure its permissions

5. Three, sir!

3. The new file will actually work in terms of setting and restoring various settings when asleep vs. awake.

4. Also added some experimental settings for the new 'lazy' governor while asleep. I guess at some point I should add that as an option to the recovery configuration as well, huh? For now, you can change it manually by putting the word "lazy" into /system/etc/glitch-config/sleep_governor. If you don't know how to do that, then don't bother. Reboot for the change to take effect.

5. when/if it changes the governor, it now waits a second before mucking about with its settings, giving the drivers a chance to catch up. If sleep and wake governors are the same, then it doesn't sleep, nor does it redundantly set it. It just plows ahead.

Without knowing exactly what the VC app is doing, I don't know if this patch will fix the ninja-gov-swap issue or not. There may very well be no fix to that.

Anyway. Here's the patch:

http://dl.dropbox.com/u/28682151/Glitch-kernels/screenstate_patch.zip

Flash in CWM and let me know if that fixes things. Due to the bug fixes, you may notice different behavior - hopefully it's all positive, let me know if something goes haywire.

---------- Post added at 11:23 AM ---------- Previous post was at 10:50 AM ----------

You can get the exact same behavior using conservative and enabling only the lowest and highest frequencies in VC app. Also, why on earth would you want the highest frequency while the screen is off?? That's just silly, IMO.
[Fascinate Android Development] sixstringsg:
Kinda what I was thinking as well. If you want that kind of responsiveness, just use performance screen-on, and ondemand screen off. Or performance the whole time, so long as you make sure you don't have apps that hold tons of wakelocks.
[Fascinate Android Development] ssewk2x:
Well, I stand kind-of corrected. Turns out that having a high CPU speed with the screen off can save some battery under certain circumstances. It does that by allowing operations to complete faster and thus allowing the phone to go into deep sleep sooner. In theory, anyway, this could be advantageous. I think the Lazy governor is configurable to exploit that, but I also admit that I only skimmed the article I read, so I could be full of crap.

Anyway, happy thanksgiving, folks!
[Fascinate Android Development] sixstringsg:
That would be correct, if we had deep idle on our devices. It works well on the Nexus S. Lazy was designed to have that in addition, but we don't use that part of Lazy. The theory is called "race to idle". It suggests that if you get everything done faster with a higher clock speed, it will be able to get to idle faster. The problen with that logic on our devices is that we don't have deep idle, so the device wakes up more often and uses more power, so Max frequency when screen off isn't reasonable for our kernel with its current idle states. It is effective on other devices with working deep idle however.
[Fascinate Android Development] sageDieu:
I know you guys were playing with deep idle... any chance of trying to get it working again? If I remember right it was sticking for a couple of users or something. I'd definitely be interested in testing that if it's on the plate anymore.

Sent from my MIUI SCH-i500
[Fascinate Android Development] ssewk2x:
For some reason, it's just not ready for prime time yet. Maybe someday, tho.
[Fascinate Android Development] Enyo.:
So not interested then?
[Fascinate Android Development] neh4pres:
Enyo.. Again.. You quoting things that have nothing yo do with what you're referring to.
[Fascinate Android Development] Enyo.:
Sorry.

Just going to hit the reply button
[Fascinate Android Development] brettdacosta:
Am I just dumb? Where is the download for the 11/19 update? Did I just overlook it in the op? Thanks in advance.
[Fascinate Android Development] scarmon25:
www.androtransfer.com

Just another post from a CM7 junkie.
[Fascinate Android Development] ssewk2x:
Not if you're just going to Kang the conservative / ondemand / lazy governor and claim it's your own work, no.

Here's a thought: get it working first. Show people that you know wtf you're doing before you open your proverbial mouth. And make sure it's a useful contribution, not just a re-hash of stuff we already have. If you can come up with something original-ish that adds value to this project, then great! I'd be glad to take a look. If not, then at least refrain from being a nuisance and making more of an arse of yourself than you already have elsewhere.
[Fascinate Android Development] brettdacosta:
Could someone tell me what I need to do to get the bln working the way it works with the stock cm7 kernel. I flashed the newest nightly, and I've always loved the bln that comes with it, but I love the glitch kernel too. Thanks so much for any help you guys can provide.
[Fascinate Android Development] bigtlt:
can't download kernel...arghh

I was extremely frustrated when the app first dropped and I didn't know yet, I couldn't figure out where to download any of your kernels. Well I found the app and donated without hesitation because this is by far my favorite kernel that I've used on the Fascinate. The only problem I'm having is that the app will not download the kernel and it's becoming quite annoying. Im stuck with v12 whilst I would really like to see what kind of progress is being made with v13.

Every time I try to download a kernel it not only thinks that I would like it auto-installed (I don't), but to top it off it fails to do so. Then when I check the Glitch folder on my sd card, the kernel never actually downloaded. So now im stuck with whats looking like now an expensive app that tells me which RC I can't use.

Sorry for the rant, but I really do love the kernels you guys are building and want to be able to use them.
[Fascinate Android Development] PhoenixPath:
V13: http://androtransfer.com

This is not the app thread. The app thread is linked in my sig. For support on the app....go there.
[Fascinate Android Development] tallnerd1985:
I don't know if its me but my dock audio routing is not working for the life of me on v13 but if I revert to v12, perfecto!!
[Fascinate Android Development] skynet11:
[EDIT]: I don't know what I was thinking when I made this post...

Has anyone seen John Connor?
[Fascinate Android Development] ssewk2x:
Can you provide a logcat? And the output of dmesg would help, too.
[Fascinate Android Development] bdanders:
Doesn't work for me either.
[Fascinate Android Development] skynet11:
Two logcats are better than one; I'm sure ssewk2x could use them for comparison (but then, I know very little about kernel development)

Has anyone seen John Connor?
[Fascinate Android Development] ssewk2x:
Honestly, logcat is a long shot in kernel land. Dmesg is marginally more useful. Both might tell me wtf is going on. Or I might be stuck reverse engineering it all again, lol.

I wont get to it until after the holiday, tho.
[Fascinate Android Development] bdanders:
Yes. Pie first.

Is the "Dock Sound Redirector" app needed to get it to work, or is it supposed to work without that? Before installing V13, CM7 nightly 112 redirect worked without the app (in fact the kernel wasn't compatible with it). Now the app recognizes the kernel as compatible, but no sound is being redirected.
[Fascinate Android Development] ssewk2x:
I honestly don't know. It may just be that the code got removed by accident. I think our intent was to .. leverage .. (pronounced "Kang") JT's cm7 kernel stuff for that. So at least that should make it easy-ish to track down.

Edit: I like pie
[Fascinate Android Development] brettdacosta:
Anyone know? Thanks, guys.
[Fascinate Android Development] chopper the dog:
Yeah, compile your own kernel :p. CM7 uses a different bln module in the kernel. Where glitch kernel uses "nelders bln" module.

good day.
[Fascinate Android Development] sixstringsg:
Please use the search feature before posting. This has been asked so many times, and answered almost as many.
[Fascinate Android Development] brettdacosta:
My apologies, but I didn't feel like waiting till Sunday when I got back home. I'm on vacation and my phone is the only real internet I have, and when I click search this thread, and try to click in the search box, the search tool disappears. Any thoughts? Not sure why this happens. I always try to search before asking a question that I'm pretty sure is already in the thread. Could I get a page number of the last time it was asked from someone that can search? Thanks foot all your hard work, guys!
[Fascinate Android Development] sixstringsg:
Answer: do it yourself, or wait until we fix it.
[Fascinate Android Development] skynet11:
Don't bother with the search function in the XDA app... it sucks a basketball through a garden hose.

Just go to this thread in the app, hit the menu button, choose more/browser and when the browser launches, click the "search this thread" button

*** Or ***

Use Google - type as follows

site: forum.xdadevelopers.com Glitch Fascinate BLN

Then just scroll down to view the results from this thread.

Has anyone seen John Connor?
[Fascinate Android Development] shag_on_e:
It's just my opinion, but I don't see the importance of bln. I don't even notice those buttons anymore. I just tap em out of pure instinct. We're talking about a six mb flash that let's you comfortably overclock/undervolt as far as your little heart desires, makes gps perfect, allows full color control, gives endless choices of governor/IO, control of sleep governor, full control of mic gain and speaker volume...the list goes on. I'd be willing to sacrifice much more than we have to! That's just me though, I'm a sucker for control and feature. Love this kernel fer sher!

~~~~There is no spoon~~~~
[Fascinate Android Development] 123SIT:
Would someone mind directing me to the 3_button_recovery.zip? The link in the changelog didn't seem to work anymore, at least not from my phone. Thanks in advance.

Sent from my Glitched CM7 Mesmerize
[Fascinate Android Development] ssewk2x:
Oh crap. I move the file. You can now find them on the glitch kernel github: https://github.com/GlitchKernel/misc_libraries look on the downloads page.

Sorry about that. But I figured that was a better place for it than my personal github.
[Fascinate Android Development] droidstyle:
Just wanted to let ya know that patch you posted a couple pages back is working really well. I got my battery life back and the phone quit doing random reboots. I would see the softkey lights come on w/ no screen, then the cayanogen logo would come on....it had a wierd distorted blue/green color(not the normal blue logo), then it would reboot. That all has stopped.

Thanks!

*here is my VC settings

No overclock, deadline/ondemand/conservative sleep scale/-50uv across the board.
[Fascinate Android Development] 123SIT:
Thanks and no worries I figured it was something along those lines.

Sent from my Glitched CM7 Mesmerize
[Fascinate Android Development] shag_on_e:
So far I'm seeing some nice results with lazy as my sleep governor and ondemand as wake governor. Thanks for that patch ssewk2x.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
Good to know. Sorry I left it broken for so long, lol.
[Fascinate Android Development] xain713:
how do I select lazy as the sleep govener? Is* it through VC or glitch app
[Fascinate Android Development] sendan:
Through glitch recovery or root explorer I believe.
[Fascinate Android Development] shag_on_e:
Check a couple posts back where ssewk2x released a patch.

~~~~There is no spoon~~~~
[Fascinate Android Development] skynet11:
I searched this thread and found no results, so I am posting the following question: does this kernel support zram/compcache? Thanks in advance for your non-flammable replies :)

Has anyone seen John Connor?
[Fascinate Android Development] Enyo.:
Is 1.2GHz OC even speed noticeable?

I haven't had good battery lately and wanted better battery.

I have 3G turbocharger, supercharger, and kick ass kernelizer installed as well.

-75mV across the board (medium leakage as well)

I also have powersave sleep governor and ondemand wake.

My phones usually awake always.

What do you recommend on having the best battery life with performance?
[Fascinate Android Development] neh4pres:
Conservative sleep is said to be better on battery with screen off. powersave locks to lowest freq. And can cause long wake locks if the system needs to do something. Other than that it looks good..i would calibrate battery.

The BEST way to save battery is to keep data toggled off if your not using it.

And if that's not enough battery life for you then the other option is going back to Touchwiz which in my opinion is far better on the battery at the cost of everything else sucking
[Fascinate Android Development] Enyo.:
Thank you. My battery seems better.
[Fascinate Android Development] fstbusa:
+1

I started using juice defender for this reason and having it only come on every 15 min to check for email,ect and I can get 48hrs between charges with average use pretty consistently.
[Fascinate Android Development] ssewk2x:
It's not available in recovery .. yet. I have a project in the works to have the recovery automagically check to see what governors are available and let you select from them. Until then, if you put the governor's name into /etc/glitch-config/sleep_governor and reboot, you can set it to whatever governor you want that way. To do that, you'll have to remount /system as read-write and use root explorer or whatever to edit the file.

Just make double-sure that you spell it right and select one that's actually available (i/e: it appears in the drop-down box in VC or whatever). I have no idea what will happen if you put an invalid entry into the file, but I imagine nothing good could come of it. If you try this and screw it up, and something really horrible happens to your phone because of it, it's not my fault, but it will be my responsibility to point at you, laugh, and say "I told you so."
[Fascinate Android Development] dr_w:
Fyi, very nice kernal. I did run into a snag though. It rebooted to the glitch splash screen and got suck. Any suggestions?
[Fascinate Android Development] sixstringsg:
What ROM?

10char