yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] neh4pres:
Am I reading the op right? Looks like a september 5th release, but there is no change log for it.. or is that a old may 9th release?

Sent from a beautiful miui fascinate
[Fascinate Android Development] pntballer505:
I am also confused to where the latest "enhanced In-call receive audio"

kernel is!?
[Fascinate Android Development] sixstringsg:
The changelog at the bottom of the second post is it.

In the OP, its the second set of download links.
[Fascinate Android Development] pntballer505:
Oh okay, thank you.

Is that the same one as before, where the lag was very obvious?

If so, what 'governor' or cpu settings do i have to modify?
[Fascinate Android Development] sixstringsg:
Nope. Its fixed.
[Fascinate Android Development] GizmoDroid:
To the OP:

For clarity, you might want to fix the second set of links to say v12.

Also, you might want to change the date format to MM/DD/YY, since it is the US standard.

Just suggestions to consider :)
[Fascinate Android Development] neh4pres:
I just want to point out that the change log on the bottom of the second post says its for a august release... That is the one I'm running. Its the first glitch to have call audio fixed. But the op had a download for what seems like a september 5th update.. (months/days) backward confuse sometimes.. Just wanted to point that out as it may confuse ppl.. I am not sure if something has changed sense the call audio fix in august... Thanks for all the hard work making this phone better than the new junk coming out. :)

Sent from a beautiful miui fascinate
[Fascinate Android Development] sixstringsg:
To everyone correcting the OP; ill work on it. Keeping up with 4 threads takes a lot of time, not to mention actually maintaining the kernel. Also remembering that I do this for free, having received no donations. I'll get to it soon.
[Fascinate Android Development] GizmoDroid:
It's cool, just seen a lot of questions that stem from the discrepancies. Didn't know if you had noticed the mismatch or not.

Multiple threads are fun to maintain, eh? I don't miss that from my "modding days".
[Fascinate Android Development] rmtobler:
Are we looking at the same screen? Those settings look horrible!

BTW What's the deal with Quadrant scores? First test 1500, next 1700, next 2000.

Seems like the phone has to warm up first...? Is that normal? Just kind of makes it hard to compare different settings :(
[Fascinate Android Development] GizmoDroid:
Quadrant isn't an accurate way to measure performance. Hence all the varying scores. I have no idea why it is the benchmarking standard that people use.
[Fascinate Android Development] rmtobler:
Is there an alternative?
[Fascinate Android Development] splashattack:
Antutu and Smartbench 2010/11
[Fascinate Android Development] Bubbadogg14:
Will these builds have adverse effects on non cm7 roms such as omfgb, pool party or vgb that aren't based off the new nightly
[Fascinate Android Development] sixstringsg:
I have absolutely no idea. If they break stuff, just reflash the old one.
[Fascinate Android Development] sixstringsg:
That doesn't answer the question that you quoted. Do you actually notice a hit in battery life? If not, it's just cosmetic.
[Fascinate Android Development] scarmon25:
I don't know about battery life but Blinky does seem to cause my phone to lag. I've done everything to make sure that was the cause of it.
[Fascinate Android Development] neh4pres:
Oh. I misunderstood.. hard to say.. I'll know tomorrow

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] FJRSport:
neh4pres,

Thanks for your assistance here and in the Q&A section!!!

fstbusa,

What was discovered is that the older version of Glitch v12 was being utilized. Just installed Glitch v12 dated 9/15/11 and it's working as it should with MIUI 1.9.16.

Thank you all for putting up with my newbie'ish questions. ;-)
[Fascinate Android Development] Talek:
Is anyone else having issues with music playback? Since installing this kernel my music constantly has pops and breaks up the music.

I had this problem once before a long long time ago. At that time it was a widget hogging resources. But this time, I haven't changed anything except the kernel.

Any ideas on whats going on? Could it just be a setting? Anyone else experiencing this? Its incredibly annoying!

Running Miui 1.9.19 on glitch 9/15 . As a note, I did not have these problems on any of the previous glitch kernels or miui roms.

Thanks in advance!
[Fascinate Android Development] Talek:
I should also mention. I have already tried factory reseting, reinstalling rom, and reflashing kernel
[Fascinate Android Development] sixstringsg:
What governor are you using, and are you using screenstate scaling?
[Fascinate Android Development] morbiddk:
Ok, so I've got CM7 build 35 running and installed Glitch v12. Everything is running great with the phone, service is awesome, battery is great, everything, or so I thought.

I decided I was tired of the constant on soft-keys when receiving a notification, so I came across this fixedlights.zip from http://xdaforums.com/showthread.php?t=1018093 that is supposed to lower the time the soft-keys remain on. Upon rebooting into recovery I notice that Glitch has install a new green CWM v4.0.1.4. Ok, thinking nothing of it I go to try and "choose zip from sdcard". I am returned with the errror "E:Can't mount /sdcard". So I check with adb, 'adb shell mount /sdcard', only to be returned with "mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory". So I ls the /dev/block directory and the closest I have to mmcblk1p1 is mmcblk1. Before that is mmcblk0p3 and the device following is mtdblock0.

I got some advice to remove /sdcard dir and re-make it and try to mount it again. This I have done through adb to no avail.

The phone can see and read the SD card when in CM7 without any problems. I was hoping someone had something else to try before I odin'd back to pre-MTD. I also wanted to post so I could report the issue I was having.

All in all, I am very happy with Glitch though and so far Light Flow is working to stop the soft-key notifications, so I can stick it out for a bit. But, seeing as we're getting nightlies again, I may be trying to fix this sooner than I previously would have cared to. Especially with Torch coming in the 55 release.
[Fascinate Android Development] sixstringsg:
What device do you have, and what kernel did you flash?
[Fascinate Android Development] morbiddk:
Fascinate and v12 Beta High leakage.
[Fascinate Android Development] sixstringsg:
I don't know what all you've done to your phone, but I do know that the sdcard problem is not one with my kernel, since you are the only one experiencing this.
[Fascinate Android Development] neh4pres:
I used to get a dual recovery.. Where the first I rebooted to had a bunch of errors. I would then hit reboot and go into the good recovery.. But have not seen that sense the new glitch recovery

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] kallell:
in the past, this was a result of too much undervolting at the 100mhz state.
[Fascinate Android Development] morbiddk:
I'm not trying to place blame at all, only trying to get some assistance. I do know that flashing through CWM worked fine until I installed the v12 kernel which installed the modified CWM. That said, would there be any harm to odin jt's CWM over top the Glitch verson?
[Fascinate Android Development] neh4pres:
When you first enter cwm are you getting like 5 can't mount errors?

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] morbiddk:
Not when I boot into the correct recovery through the Phone options menu, which is the Glitch version now.

I do if I try to the volume button power on method.
[Fascinate Android Development] Zacisblack:
Last time that happened to me I had to go back to stock DI01 and re-partition with the atlas_v2.2.pit file in the sticky. Luckily there is now a full Odin and re-partition available for ED05 so you won't have to go back to DI01. Check the sticky thread for Odin files and getting back to stock.
[Fascinate Android Development] sixstringsg:
Test Build

Here's a new build that should work with the newest nightly. Don't ask me for any other leakages, this one is ML. I only made this one to make sure it will work, I'll make more tomorrow. As always, don't forget to hit the thanks button.

Edit: I am getting reports that this didn't fix it, so try at your own risk.
[Fascinate Android Development] GizmoDroid:
Any benefit for miui users, or is this just a recompile of the previous beta including the fix for the new CM7?

Thanks!
[Fascinate Android Development] sixstringsg:
Well, I'm going to assume it boots, and go to bed. If something blows up I'll fix it in the morning,
[Fascinate Android Development] sixstringsg:
Well when MIUI get's updated with the CM7 fix this friday, then you'll need it. Until they I don't even know if it will boot with it. You can try.
[Fascinate Android Development] neh4pres:
What is the cm7 fix?

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] iofthestorm:
The latest nightly of CM7 isn't compatible with previous kernels. Sixstringsg fixed glitch so that it does work with the new CM7.
[Fascinate Android Development] sixstringsg:
http://xdaforums.com/showpost.php?p=17693047&postcount=576
[Fascinate Android Development] neh4pres:
I have no understanding of what that means. You said a fix from cm7 was going to be added to miui. Was just wondering what was being fixed.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
That was the change that occurred. It's little, but CM7 changes always get added to MIUI. I honestly don't care to spend the time to find out what it does its so minor, I just know if you have a kernel before it and a rom after, they cause bootloops. I presume the same happens the other way around too, but I don't know not having a fascinate to try it with.
[Fascinate Android Development] Eris _2.1_2010:
I have the the new kernel and I have tried the HL and ML versions and whenever I'm playing music/slacker the audio skips. Been U/V but not more than -50 across the board. Is anyone else having this issue?
[Fascinate Android Development] Talek:
I've tried all different governor and scheduler combos. Im on stock settings now (on demand, govenor)

Not sure what screenstate scaling is...
[Fascinate Android Development] kuronosan:
Maybe if the two of you bothered to read the topic, you would find out.

And people wonder why developers are leaving.

edit: Not directed at Eris, but the one above sixstring.
[Fascinate Android Development] Eris _2.1_2010:
Lol I was like "WTF!" I never seen anything in the OP. Any ideas why it was doing that. I tried different governors and schedulers and tweaked the U/V but I just can't figure it out.
[Fascinate Android Development] CHANGiism:
It's the same for me. I tried every combination, and even with no UV at all, my audio would skip and I would have occasional lag here and there. I just reverted back to stock CM7 kernel and it's stable and fast enough for me.
[Fascinate Android Development] ssewk2x:
I just wanted to let everyone know a couple things:

First off, in an effort to ensure the maximum level of complexity in my personal life, I am starting a new job this week. Better pay, nicer company, less BS, but a much longer commute. This means I have to sort things out for a while and figure out how to get time to work on the kernel. I apologize for the inevitable delays, but please understand that I love this phone, this kernel, and this community, and I want stuff to work as badly as all of you. I'll get to it, I promise. I just don't know when.

Second, since it seems like we picked up a bunch of weirdness from the merge, I think the first thing I'm going to work on is getting a version out there with some useful debugging messages enabled. With all the wonkiness going on (some on my phone too), log-cats and dmesg dumps will no doubt prove invaluable. Once we can get our hands on those, squishing the other bugs will hopefully be a lot easier.

Thanks again for your patience.
[Fascinate Android Development] *Luke*:
Take all the time you need, sir! IRL is always the most important thing... thanks so much to you and six for all your invested effort and support to make our phone so much better
[Fascinate Android Development] :
First, thanks for the quick turnaround on this. I think I speak for the group when I say that we all appreciate it.

Unfortunately this kernel + CM55 didn't work for me. Am I the only one?

-

Jim
[Fascinate Android Development] sixstringsg:
More information please? I can't do anything with "didn't work for me"
[Fascinate Android Development] gabe565:
When I tried the test kernel with 55, I got stick on the bootscreen and accidentally left it there all night...so the next morning I flashed back the stock CM kernel, and its working nnow!
[Fascinate Android Development] :
Sorry about that, it's stuck at the CM boot animation.
[Fascinate Android Development] sixstringsg:
As far as the newest nightly goes: don't update, or don't use this kernel. I'll look into it soonish, but unless someone has an extra fascinate lying around, getting other bugs worked out is easier for me to test, therefore higher priority for now.
[Fascinate Android Development] Talek:
Maybe you should read the conversation before ya start pointing fingers... I posted like 2 pages back and was asked specifically by the developer what my governor was and IF I was running screenstate. (I accidentally hit reply and not quote so it may have seemed out of context)

So find out what's going on before you start putting your foot in your mouth.

Thanks
[Fascinate Android Development] neh4pres:
Good luck at the new job.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] rosser725:
Will this work with the new MIUI MTD for Fascinate?
[Fascinate Android Development] sixstringsg:
Define "new"
[Fascinate Android Development] rosser725:
the latest one. i think its 1.9.16 FacinateMTD. i couldnt get the cm7 nightlies to boot from the medium one. Do any of them work with MIUI MTD 1.9.16
[Fascinate Android Development] sixstringsg:
The newest CM7 won't work at the moment. MIUI should, because it doesn't have the CM7 changes get.
[Fascinate Android Development] rosser725:
Ok thanks! I'll give it a go. Does it matter which leakage i do?
[Fascinate Android Development] sixstringsg:
Read the OP please. I don't make three leakages just for ****s and giggles. Here is also what I said a few pages back:
[Fascinate Android Development] kallell:
Hmm, so after a few days running this, it works ok... But unfortunately I think I may have to revert to the older version for stabilities sake. I noticed it locks up completely a lot when going on the Internet, requiring a battery pull or soft reboot.

I also noticed, that there is just delays in general with random actions. For instance, I'll set my alarm, it will take but ill get the notification message 5 minutes later - your alarm will go off in 8 hours 21 minutes from now. Same with adjusting volume... I'll turn it up with the hard buttons on the side, it will take, but a few minutes later the volume control window will pop up from the top , indicating the change.
[Fascinate Android Development] neh4pres:
what rom? ..I don't have those issues.. You may just need to tinker

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] brett10:
I don't have the delay when using the buttons, but I have the alarm delay and the locking up. I'm running MIUI 1.9.16 on a mesmerize with the 9/15 version of the kernel. I also tried MIUI 1.9.9 and 1.9.16.1, all of them had the locking up and the delay thing. The 9/19 version stuck at the samsung screen and I had to odin back to stock to fix it.
[Fascinate Android Development] sixstringsg:
Yeah, I'm getting the same issues on my captivate. Not everyone is though, so I'm trying to figure out the common denominator. What are all of you OCing to that are getting the lockups? I know that you had it stable before, and I'm not saying it's not stable now, but it could be a factor. Mine seemed to get better when I lowered my clock speed.
[Fascinate Android Development] shag_on_e:
I'm running 9/16 MIUI, latest HL, averaging my clock at 1.4 with voltage at -25 to -50 across the board usually. I've been getting some lock ups occasionally too. Since the beginning HL has been the one for me, but for ****s and giggles I've tried all three at normal to average performance setups and seem to get the freeze no matter what. It seems to happen when I'm multi-tasking most often but sometimes from opening an app. I haven't tried getting a logcat yet, but I'm gonna give it a go and send it to ya if you want. Thanks for the support man, this thing is still a beast regardless!

Just sent.
[Fascinate Android Development] brett10:
I get the exact same lock ups as you. I was overclocked at 1.3 at -50 to -75, bit I have been running at stock voltages for about the last 2 or 3 days. It hasn't had as many lock ups but still a few.
[Fascinate Android Development] pwshadow:
Lockup happens for me with no overclock when using heavy data. YouTube seems to cause it the most. Most times the phone will reboot itself. I am back on Jt's 0912 with no issues
[Fascinate Android Development] kallell:
MIui .16.

I had it at stock voltages and stock frequencies. I bumped it to 1200 at one point in attempts to remedy the slowness/lockups to no avail. I haven't undervolted this version at all yet.

P.s. not to derail, but does anyone know if this is JT's newest ? http://www.mediafire.com/?9arxskbsfnqa2n8
[Fascinate Android Development] sixstringsg:
As of right now, we're redoing the whole merge. Too much stuff is broken, so we're starting over. Please don't ask when it will be done, it took a while the first time, and will take some time this time too.
[Fascinate Android Development] shag_on_e:
You are appreciated kind sir.

Just sent.
[Fascinate Android Development] shag_on_e:
Yes.

Just sent.
[Fascinate Android Development] ssewk2x:
I rofled. At the doctors office. Thanks for that. :-P
[Fascinate Android Development] rosser725:
Will this work on vanilla gingerbread ROM?
[Fascinate Android Development] sixstringsg:
Please search before asking. This has been asked and answered already.
[Fascinate Android Development] rosser725:
It's kind of hard to do that on a phone. You don't have to be rude. I just asked a question.
[Fascinate Android Development] akellar:
Menu - browser - search
[Fascinate Android Development] rosser725:
Really. you can't just type yes or no
[Fascinate Android Development] :
please read first page

Note : These kernels are only compatible with CM7 and MIUI roms ![/CENTER]
[Fascinate Android Development] akellar:
No, there's a 10 character minimum. :p
[Fascinate Android Development] rosser725:
Wow.
[Fascinate Android Development] Jazz848:
In all honesty, if searching makes your "hard to do on a phone" list, you should review some stickies pronto; flashing a rom or kernel is nigh impossible by comparison...
[Fascinate Android Development] rosser725:
i didnt mean that its hard to do i meant i couldnt do it. i tried that but the search box wouldnt come up in browser. jeez. u guys don't have to be so rude. i just asked a simple question. its not like a created a new thread in development to ask my question about this.

---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------

search didn't help me. thanks so much everyone. it must be so hard to type yes or no. appreciate it.
[Fascinate Android Development] gabe565:
Yes, it will work on vanilla GB!
[Fascinate Android Development] rosser725:
Thank you!
[Fascinate Android Development] sixstringsg:
I apologize, but it honestly makes me mad when people can't take the time to find the answer to their own question. I have spent countless hours on this kernel, as have others, the least you could do is spend 20 minutes maximum looking through this thread for your question. Also if I'm not mistaken, the Vanilla gingerbread ROM states that it is CM7 based. Therefore by default it uses the stock CM7 kernel, therefore it can use any custom CM7 kernel.
[Fascinate Android Development] sixstringsg:
Just an update, we have the important changes merged in again, including the camera issue for the i9000. We're working on adding a few more things (like BLN and printk) and then there will be new builds out. Thank you for your patience. As always, please don't ask for an ETA, it will be ready when it's ready, probably within the week. Don't forget to hit the thanks button!
[Fascinate Android Development] bigjobber69:
im assuming it will work with the latest cm7 builds? Im glad ur intergrating BLN i miss it for text messages
[Fascinate Android Development] sixstringsg:
Yeah, it will work. And this kernel has always had some sort of BLN.
[Fascinate Android Development] shag_on_e:
Once again, thank you for all the work. I've lost a lot here lately in my life and may be losing more here soon, so y'all have given me stuff to look forward to. Thanks man.

Sent from tin cans and a string.
[Fascinate Android Development] sageDieu:
I'll do it again, I swear haha

Sent from my MIUI SCH-i500
[Fascinate Android Development] sageDieu:
on current kernel build you have to use blinky from the market and set it up for BLN to work correctly.

Sent from my MIUI SCH-i500
[Fascinate Android Development] sixstringsg:
We'll probably keep it that way.
[Fascinate Android Development] brett10:
Will the issues with the phone locking up be fixed? I think it might have something to do with data. It only happens when I'm using data, I haven't tried Wi-Fi though.
[Fascinate Android Development] neh4pres:
No.. You are not entitled!

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
Yes, we're working on it. That's the entire point of the work we're doing right now...
[Fascinate Android Development] kriddle04:
Any thoughts on when using Friendcaster and you shake the phone to refresh, even though I don't shake it just constantly shakes with the new glitch and jt's updates?
[Fascinate Android Development] shag_on_e:
By the way, thanks to calebv2 for this info.

Sent from tin cans and a string.
[Fascinate Android Development] kriddle04:
Thank you sir.
[Fascinate Android Development] kriddle04:
Just reinstalled and deleted what you posted and it still shakes.

scratch that forgot to reboot.
[Fascinate Android Development] akellar:
Is the plan to fix it so it works for everyone? Currently it does not work unless you allow the lights to blink.
[Fascinate Android Development] sixstringsg:
As I said, we're working on it.
[Fascinate Android Development] neh4pres:
Common everyone... This is starting to sound like a press conference. Do you plan to fix this? Do you plan to fix that? Will this happen?

Just know these guys will do their best for as long as they support this kernel and these phones..

Try to keep eta's, will my phone work again, and does this work on jts vanilla, questions absent for a bit, or forever.. and please read ATLEAST the last 5 pages or more before asking something.. I'm guessing more ATM because people have not even been reading the current page lately before posting it seems..

these devs offer some of the best support I have seen.. Always on top of questions and concerns. Lets not abuse that with questions that don't need to be asked

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] shag_on_e:
+1 Agreed.

Sent from tin cans and a string.
[Fascinate Android Development] neh4pres:
Do you happen to be on miui?

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] Eris _2.1_2010:
XDA app search sucks, wish there was a way to search within the threads.

Sent from my MIUI Fascinate
[Fascinate Android Development] neh4pres:
Reading op and last 5 pages work fine.. These phones have browsers too

Sent from the fascinate that holds the record benchmark on antutu