yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] sixstringsg:
You're also not the only thread with a poll. In the captivate thread, stay on is winning, and I have a captivate :)

just so everyone's clear, this poll was not the winner gets their way. It's, ssewk2x and i will take into consideration the poll, then decide if we should spend the time to "fix" it. That wasn't directed to anyone in particular, just a public service announcement so people will know what to expect.
[Fascinate Android Development] scarmon25:
My BLN is working great.
[Fascinate Android Development] chrisexv6:
What kind of issues are they seeing?

Ive seen a couple times where the BLN didnt turn on (using Blinky), but 99% of the time it seems fine for me.

Its not 100% clear to me why its better to have to use an app for BLN vs the way it used to be (built into the kernel?) It seemed to react a lot faster and more reliably before we had to rely on an app. Its not a complaint, Im sure there are reasons that I dont know of, just stating my observation.
[Fascinate Android Development] 4FatSno:
BLN is working fine for me also.

sent from outerspace
[Fascinate Android Development] sixstringsg:
Personally, i like blinky. It is still built into the kernel, it just uses the bln app instead of cmparts. I think I just missed a part of the captivate defconfig, and that's why they're having problems.
[Fascinate Android Development] Bubbadogg14:
BLN works fine here. Espresso ROM build 28.
[Fascinate Android Development] sageDieu:
have you guys looked into how the softkey backlight thing works? iirc it was a little flashable that modified something in the rom, not the kernel back in the froyo days; it was one of the mods phidelt did along with statusbar clock things and stuff. I'm pretty sure it isnt part of the kernel, rather it is in the rom.

I voted for turn off in the poll, but im fine either way. You guys have a monopoly on kernels; even if I don't really like having the lights on when listening to music or watching a video or something, if you guys make my lights always stay on then I will get over it.

Sent from my MIUI SCH-i500
[Fascinate Android Development] sixstringsg:
I know it's something in services.jar. Ssewk2x, Tk-Glitch, and I have to decide if we're willing to modify a part of the ROM with a kernel flash, especially considering the number or different ROM's that people run with our ROM. Another solution is using Hacksung's LED notifications, which we'll look at as well. To be honest, I haven't looked at it, and I don't think anyone else has yet either. I've been doing cleanup/organization stuff, and ssewk2x has been doing audio stuff.
[Fascinate Android Development] thachizzle:
I'm with sage, love this kernel. Blazing fast, but with the backlights on 24/7 it distracts me while I'm watching videos or playing games late at night with all the lights turned off and screen on lowest setting. Thank you for the great work, I'll continue to support glitch to the end :D
[Fascinate Android Development] pntballer505:
BLN works great, with Blinky of course.

I love this kernel, but my voodoo color or gamma or whatever

was perfectly setup on JT's kernel. Therefore, I was wondering if anyone

knew the default RGB and gamma on JT's kernel, so I can set them

alike on this kernel. Unless everyone's turns out differently...

Thanks.
[Fascinate Android Development] sixstringsg:
If JT's kernel has voodoo color, then the values will be the same. If it doesn't, then you will have to find what you like on your own, or search for the "recommended" settings that others have given throughout the thread.
[Fascinate Android Development] hejay:
The only reason I even mentioned the softkey light timeout in this thread is because it seemed like in pre-BLN Glitch, they would stay off until touched after a screen on/off toggle.

I just didn't know if it had been adjusted in the kernel or if it was changed elsewhere.
[Fascinate Android Development] bigjobber69:
I still cant get bln to work with handcent with the kernel

What am I doing wrong, I have it enabled
[Fascinate Android Development] sixstringsg:
Are there LED settings in Handcent as well? I use Go SMS, and there are settings in the app itself for LED's that have to be turned on.
[Fascinate Android Development] bigjobber69:
Yah I have them turned on.
[Fascinate Android Development] ekowanz:
Mine works perfect.. I use bln pro

Sent from my SCH-I500
[Fascinate Android Development] ssewk2x:
My answer to modifying the ROM would be an emphatic "hell no." It was bad enough when we had to bundle in those sensor libraries recently.

In fact, I think I want to take that out. Maybe move that stuff to its own separate .zip file that people can flash if they need to. Tho if you're running a recent ROM you won't need to.

Anyway. I'd really rather not blur the line between ROM and kernel any more than we already have.
[Fascinate Android Development] Coolsaber57:
Reporting back after a few days of use: no more reboots for me after I flashed the ML kernel. Huzzah!

I haven't had success yet with Handcent and BLN either, but I'll keep digging in the settings to see if I missed anything.
[Fascinate Android Development] sixstringsg:
Yeah, that's kind of what I'm thinking too.
[Fascinate Android Development] akellar:
+1 - It only sets you guys up for more complaints if it breaks something in a Rom. Unnecessary headache in my opinion.

To everyone complaining about the backlights being activated while the screen is off - clear your notifications and/or get the BLN app and turn BLN off. Problem solved. Please stop posting complaints about this when you can fix it yourself if you don't like the way it works.

Oh yeah, and BLN and Handcent have never played well together in my experience so this isn't something new.
[Fascinate Android Development] Coolsaber57:
Actually when I ran a TW rom back in the day I was able to get them to cooperate just fine, but maybe the application was updated so that it broke those notifications. :rolleyes:
[Fascinate Android Development] ssewk2x:
I tried handcent for a couple days and ended up trashing it in favor of ChompSMS. I haven't looked back.

Anyway .. it's not even about the possibility of more complaints. I don't mind hearing about stuff that's broken (once, lol). It's more a matter of maintaining good software engineering discipline. There's a very good reason that ROM and kernel are kept nice and separate, with a well-defined interface between the two. To start blurring that line would result in more bugs, less compatibility, and overall an inferior product. If you want that, go grab a Windows Phone or iPod or Blackberry, lol ;)
[Fascinate Android Development] DakotaS96:
I think I've noticed a problem with Glitch V12 and the app Words with Friends. It randomly locks up everytime I launch a game. It usually happens within the first 30 seconds of running the game.

I've tried Glitch V12 LL, ML, HL and had the same issue with all of them. I kept the default settings and didn't mess with overclocking. Went back to using Glitch V11 and it works fine.

Anyone else notice this issue?

I am running a Fascinate

Baseband Version ED05

Cyanogen Mod 7 nightly 35
[Fascinate Android Development] sixstringsg:
Mind grabbing a logcat? Or updating to the latest nightly for your device and then seeing what happens?
[Fascinate Android Development] bigjobber69:
they were doing just fine toegther in cm7 when i went to espesso they know worky no more...might have to go back. but there should be a way to make it work...
[Fascinate Android Development] sageDieu:
people having problems with messaging apps, go try GO sms, it's the best messaging app other than the miui default one. it has a great UI, much cleaner and nicer looking than chomp or handcent and much faster as well. it has a lot of options as well and works perfectly with BLN.

Sent from my MIUI SCH-i500
[Fascinate Android Development] akellar:
So wouldn't that imply that it's the rom and not the kernel? Sounds like you should contact Enyo.
[Fascinate Android Development] sixstringsg:
If it works on CM7, that's all I'm worried about honestly. I can't support espresso, because I don't have a fascinate and can't run it, therefore have no idea where to start the troubleshooting for you.
[Fascinate Android Development] bigjobber69:
ok go sms salesman im going to try it....off that bat bln works for it perfectly lol. ill try it for a day and see if i likes it
[Fascinate Android Development] DakotaS96:
I just tried the latest v12 Glitch and newest Nightly and Words with Friends does seem to be working fine now.

Thanks for all your work on this kernel! I used to have so much trouble with my Fascinate randomly popping up the keyboard and backing out of apps. It happened a lot with the CM7 kernel and even happend back when I used the Superclean rom.

I was starting to think it was just an issue with my phone but I haven't had any problems with it since using Glitch.
[Fascinate Android Development] sixstringsg:
Well good, I'm glad you like it.
[Fascinate Android Development] Mikes30000:
So I just flashed CM7 nightly #65 as I usually do (wiped dalvik and cache first), then when I tried to install the Glitch kernel I received a Staus 7 error and it aborted. I did realized that the latest nightly also flashes a new recovery version 5.0.2.3 (i think the same as espresso rom latest nightly) and this recovery does not seem to be compatible with flashing Glitch. I reverted back to nandroid w/ Glitch and nightly 64 and all is good again.

Anyone else experience this?
[Fascinate Android Development] ekowanz:
Im on latest espresso.. Still can flash glitch.

Oh and i have issue bout voltage control in espresso, better to choose pimp my cpu.

Sent from my SCH-I500
[Fascinate Android Development] sixstringsg:
CWM5 will be in the next release. You shouldn't get that issue though.
[Fascinate Android Development] :
I am on the Nightly #65 and the Glitch v12 kernel and did not experience any issues.
[Fascinate Android Development] iofthestorm:
Has anyone tried dock audio with this? I'm not sure if I need an app or something. Seems like the kernel has support for it though, correct me if I'm wrong. Do you guys merge with jt's kernel or the mainline CM kernel?
[Fascinate Android Development] sixstringsg:
Jts is the mainline cm kernel basically. Dock audio should work, I don't have a dock. On CM7 there is a setting for it though if that's what you're looking for.
[Fascinate Android Development] sixstringsg:
Public service announcement: first of all this was posted in the forum of five devices, so if something in this post doesn't apply to you, ignore it. Now on to the info: for everyone asking, Tk-Glitch is doing much better. He might not be in the forums for a while, so I will still be maintaining them. He is feeling a lot better though. Next, we feel like V13 is nearing completion, so no new builds will be made until then. We know about all the small bugs, none of them are terrible, all can be worked around or ignored, and they will all be fixed in V13. That said, if a nightly breaks the kernel again, I will release an interim kernel that works for that nightly. Speaking of V13, here's what to expect: everything in past kernels, with all the bugs worked out, plus a few surprises :) so for the i9000, you have your last builds before V13. For the vibrant and captivate, I'll make you builds with gingerbread bootloader compatibility, and that will be it until V13.
[Fascinate Android Development] shag_on_e:
Lucky number 13 !!!!!!

~~~~There is no spoon~~~~
[Fascinate Android Development] jvincent08:
Just flashed this kernel for the first time and now I'm stuck in the recovery. I can't boot into the ROM, it automatically boots to recovery no matter what I do. I've tried a complete wipe and reflash of MIUI and still nothing :/

Ideas?
[Fascinate Android Development] sixstringsg:
What version of MIUI?
[Fascinate Android Development] jvincent08:
FascinateMTD from this thread: http://xdaforums.com/showthread.php?t=1150045

Version 9.16.
[Fascinate Android Development] sixstringsg:
Update to the newest MIUI.
[Fascinate Android Development] Bubbadogg14:
Thanx for the update good sir. Can't wait for v13. You guys are awesome. Glad to here tk glitch is doing better!!
[Fascinate Android Development] jvincent08:
Still no luck. Flashed 9.30 over 9.16 and got the blue CWM 5. Did a full wipe from there and tried 9.30 again, still nothing. Reflashed the kernel and now I'm back to the glitchified cwm 4.

Edit: If it helps, this is the error I get when I click "show log" after enabled logcat from the GLITCH menu: "I:Checking for extendedcommand... I:Skipping execution of extendedcommand, file not found..."
[Fascinate Android Development] sixstringsg:
OK, thanks. I'll look into it. Though you're the only one with the issue. We will be on CWM 5 soon.
[Fascinate Android Development] shag_on_e:
I misread, sorry about the useless post guys.

~~~~There is no spoon~~~~
[Fascinate Android Development] Enyo.:
Is their a problem if I have the interactive governor with a 1.4ghz overclock? Overheating? Hardware damage?
[Fascinate Android Development] sixstringsg:
Other than ondemand is better than interactive, you won't have any issues. It's practically impossible on a well built kernel to get hardware damage by overclocking. There is also a hardware limit on our device that prevents hardware damage anyway.
[Fascinate Android Development] Enyo.:
I noticed that with 1.4ghz Oc and interactive gets really hot. Ondemand is good too, but interactive is faster.
[Fascinate Android Development] sixstringsg:
Lower your voltage on 1.4 then. Some phones react differently to Overclocking, you just have to be smart about it.
[Fascinate Android Development] Enyo.:
All steps as UVed -75mV. Ill try -100mV.
[Fascinate Android Development] sixstringsg:
Also try different leakages. That could help you out.
[Fascinate Android Development] Enyo.:
I've couldn't get Low leakage to get past 1.2ghz. But It helped alot. Medium leakage works sometimes and will crash after a while. High leakage has been the only one that has worked for a long period of time
[Fascinate Android Development] sixstringsg:
Are you using my files, or the ones you built yourself?
[Fascinate Android Development] Enyo.:
Using Mine. I tried your medium leakage today, was able to get it to 1.4ghz with -75 mV and not that much overheating.
[Fascinate Android Development] sixstringsg:
I can't help you with the kernel you built yourself. I doubt you are using the correct toolchain, did Tk-Glitch or ssewk2x teach you how to compile it?
[Fascinate Android Development] Enyo.:
Does anyone know how to enable swap?
[Fascinate Android Development] sixstringsg:
Why do you want to enable swap?
[Fascinate Android Development] Enyo.:
Because I use about 1GB of ram.
[Fascinate Android Development] sixstringsg:
Android devices aren't designed to use swap. Also, it will deteriorate performance quite a bit if you use swap space, because both the SDcard and the ext-sd card will be quite a bit slower.
[Fascinate Android Development] Enyo.:
What if you had a class 10 16gb sdcard?
[Fascinate Android Development] Enyo.:
Also is it dangerous to the hardware if I set it to the performance governor @ 1.2GHz?
[Fascinate Android Development] sixstringsg:
http://zerocredibility.wordpress.com/2009/08/24/why-android-swap-doesnt-make-sense/

http://wiki.cyanogenmod.com/wiki/Swap_and_Compcache

First two results on google.

Not technically. It could conceivably decrease the life of your device though. Not enough to matter, but that is there.
[Fascinate Android Development] Azuma73:
Man, check this weirdness out!!:confused:

Today I just hooked up build#66, everything was fine until later on, when I plugged my phone into my Comp. It just boot-looped on the CM7 bootanimation? I've never had this happen before and all I can do is re-Odin and start all over....again!

Like I said, I've updated many times and never had this happen? All I did was installed Glitch, like I always do. It only happens when I mount USB storage, I don't get it?
[Fascinate Android Development] Enyo.:
Try aa different rom. Like biffmod, espresso, or trigger. And if worst comes worst, then flash #65 build (assuming you came from that build)
[Fascinate Android Development] sixstringsg:
It won't reboot into recovery when that happens? And honestly, it might be a bug on my end. We have a lot of rewritten code for V13, so it should be fixed for that if the issue is on my end. You could use an FTP app on your phone to push files, or ADB.
[Fascinate Android Development] Azuma73:
Nope, won't go into recovery at all! Now I've noticed I've lost root permissions for my busybox installer and I can't run my Root tools app because I can't install busybox? I need busybox 1.18.2 to run V6 Supercharger, so I can't even run scripts? I've tried going into superuser and it doesn't even show it's been approved or denied? :confused:
[Fascinate Android Development] sixstringsg:
Reflash SU through ROM manager.
[Fascinate Android Development] ibsk8:
Just flashed the v12 beta, I'm running miui and got caught in a bootloop.

My question is since we can't boot into recovery from an off state do I have to go back to stock, re root and re load miui?

I'm not as familiar with the fascinate as I should be.

is there any way to adb reboot recovery at any point during the boot process?

TIA for the speedy reply guys
[Fascinate Android Development] scarmon25:
Yeah. I have had to do it a few times. You just gotta do the reboot recovery as soon as you can in adb. Before the device reboots again. At least that's been my experience
[Fascinate Android Development] ibsk8:
it just reboots at the bootanimation, so just keep trying during that time for a connection?
[Fascinate Android Development] sixstringsg:
adb wait-for-device reboot recovery
[Fascinate Android Development] tonu42:
I've gotten that boot loop 7+ times. Like twice I managed to quickly adb into recovery after spamming the command for a good minute each time. Sadly I had to start over from scratch every time........... I learned not to flash glitch anymore.
[Fascinate Android Development] ibsk8:
i just decided i'd start over with odin, now the problem is when i load the phone and odin up with the ed05.tar.md5 and the .pit file odin is not comming back with the usual yellow com.

when i attempt to start anyway it just show

<OSM> All threads completed. (succeed 0 / failed 0)

I just reloaded CWM from the cm7 like an hour ago and all worked well.

I'll try again. Any help would be appreciated.

is it a big NO NO to disconnect when the phone is Download mode? if it seems nothing is happening?
[Fascinate Android Development] sixstringsg:
It would suggest heimdall. It's more reliable.
[Fascinate Android Development] sixstringsg:
Everybody with bootloops: Are you on the latest MIUI? I think that's the problem.
[Fascinate Android Development] ibsk8:
so in heimdall

load package: load the edo5.tar.md5 (showed no firmware.xml file)

flash: load atlas.pit file and check reparition

anything else i need to be aware of?

---------- Post added at 11:30 PM ---------- Previous post was at 11:30 PM ----------

battery in or battery out?
[Fascinate Android Development] sixstringsg:
Battery in, unless that's different for the fascinate.
[Fascinate Android Development] ibsk8:
when i load everything up and add the pit file the start button doesn't pop up?

is this because the firmware.xml file is missing?

---------- Post added 2nd October 2011 at 12:19 AM ---------- Previous post was 1st October 2011 at 11:51 PM ----------

thanks button hit. appreciate the speedy help.

any idea what may have went wrong with the my install of the kernel? I wiped cache and dalvik and flashed the kernel like any other kernel. I chose the high leakage to be safe.

I'd love to have the voodoo sound and color. should i try version 11?
[Fascinate Android Development] sixstringsg:
Just so everyone's aware, he was on an incompatible version of MIUI.
[Fascinate Android Development] DarthCivicus:
I'm having an issue after installing this kernel that data will not work. I can't access anything. Should i go back to the original kernel? I installed the mid voltage beta 12 and then added the 90call_vol file as requested. Should I remove that file?

---------- Post added at 03:26 AM ---------- Previous post was at 02:55 AM ----------

Yeeeup, answered my own question, once i renamed the file it worked again.... Should I have not done this to begin with? I just want to make sure there aren't any issues with the calls not going through and people can hear me.
[Fascinate Android Development] sixstringsg:
That file has nothing to do with cellular data, therefore that had to be a coincidence.
[Fascinate Android Development] tonu42:
I've had these boot loops since the 1.8.X times. Something with glitch and MIUI just isnt playing nicely. And cm7. Must be a bug somewhere?
[Fascinate Android Development] sixstringsg:
What version have you been flashing? This is not a bug everyone is having, therefore there has to be some kind of user error, or else nobody would be able to use the kernel due to bootloops.
[Fascinate Android Development] shag_on_e:
I haven't been on cm7 for a couple weeks, but I rock this kernel non stop on MIUI and have no issue at all. MTD is just updating rapidly, so I make sure I stay updated and all is well.

~~~~There is no spoon~~~~
[Fascinate Android Development] sixstringsg:
If you have actual reasons for wanting them, we can look into it. Not simple though, we tried that already, didn't work well.
[Fascinate Android Development] rmtobler:
Just found them reviewed here and piqued my interest:

http://xdaforums.com/showthread.php?t=1242323
[Fascinate Android Development] sageDieu:
Read that too. Good link. thumbs up from me for the smartass2 governor (just an updated/better version of smartass2) and the VR scheduler.

Sent from my MIUI SCH-i500
[Fascinate Android Development] tripacer99:
Took the words right outta my mouth. I'm extremely interested in seeing the smartass v2 governor and VR I/O scheduler ported over to this kernel.

If this could happen, I would be most, most apprecitave. But I also know you guys work on this in your free time with hardly any donations, so no complaining here. Just happy with all the work you put into this for us (and the whiners :| )
[Fascinate Android Development] Glocjt:
Thanks for all the hard work, guys. I've been rock solid on CM7 nightly #34 and the 0906 HL beta for 24 hours now. Settings are as follows:

I/O: CFQ

Gov: smartass (screen off: powersave)

1000 MHz: -50

800 MHz: -100

400 MHz: -125

200 MHz: -175

100 MHz: -200

Batter life has been pleasing, as well. At 56% after ~15 hours. Admittedly lighter usage than usual today, though, e.g. only half an hour of screen-on time.
[Fascinate Android Development] Jazz848:
Wait, you've got 100MHz set to 750mv with no apparent issues yet? Sounds like you got champ there...
[Fascinate Android Development] Glocjt:
Yeah, I've actually had it that low since Glitch's v11, and I kept it for the 0720 and 0827 betas, so I just kept it when I updated to 0906. :P I have gotten a little more aggressive with the UV from 200-400 MHz with the 0906 beta, though.
[Fascinate Android Development] ssewk2x:
You might see better battery life with the sleep gov set to conservative, actually..depending on how many background apps you have running.
[Fascinate Android Development] Glocjt:
Hmm, you don't say - I usually run conservative/conservative, and have been generally pretty pleased with my battery...this is my first time giving the smartass/powersave combo a try - guess I'll give smartass/conservative a spin and see how it goes. Thanks for the tip! :)
[Fascinate Android Development] sixstringsg:
The biggest advantage of smartass is the screen off profiles. With our screenstate scaling that is irrelevant, so we've found ondemand to work better and be more stable.
[Fascinate Android Development] ssewk2x:
Yeah the thing is, all powersave does is keep the cpu at it's lowest possible frequency. That's great if nothing much is running, but if some big task gets started (like a background sync, for example), that task will run way longer and use more battery at 100mhz than it would use if the cpu were able to ramp up to handle it faster. Does that make sense?