yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Talek:
I hate iphones myself ( and everything apple stands for really) and I totally avoided MIUI for that reason (because I thought it was "iphone-y" But I eventually tried to just cause and I'll never go back haha! Much smoother than CM7 on the fascinate IMO (at least when I was running CM7). Also just download Launcher Pro if you don't want the iphone look. Then you can reskin everything to look totally different. MIUI has a lot more going for it than just cosmetic changes ;-) She really should give it a shot (just change the launcher)
[Fascinate Android Development] rmtobler:
So quiet. Hope that is a good thing :D
[Fascinate Android Development] sixstringsg:
All that is left to fix is BLN.
[Fascinate Android Development] calebv2:
Sweet can't wait
[Fascinate Android Development] sageDieu:
If you guys cant get that easily is there any chance we could get some builds without it? It isnt super important but sensors are.

Sent from my MIUI SCH-i500
[Fascinate Android Development] wil318466:
I can't stand MIUI in its standard setup, but like other people have said, if you change the launcher, the only thing that looks "i-phoney" is the menus somewhat.

I've attached some screenshots to prove it. My phone looks EXACTLY like it did without MIUI except for the menus (you can choose different skins for the icons), simply by using golauncherEX like I did without MIUI. Finally, MIUI runs really really well, it's stable and fast and it's smooth as butter. I can't recommend it enough.
[Fascinate Android Development] sageDieu:
Yeah i personally like the MIUI launcher but GO Launcher, LauncherPro, all of these can be installed just like if you were on CM7. For me MIUI has better performance and battery life than CM7 so it's worth it.
[Fascinate Android Development] Bubbadogg14:
Yeah baby u listen 2 my man wiz. That's good **** rite there. hopefully we will c some awesome glitch kernels today lol this is like the only thread I check on here n I do it like once an hr!
[Fascinate Android Development] speedingcheetah:
Sensors on MIUI?

Funny you guys should mention MIUI...actually just switched to it...gotta say..after the right tweaks and a change to a dark theme and using Go Launcher...its great...battery life kinda sucks..but probably need to calibrate..

Anyway, I was running CM7 with JT's 9/12 kernel which gave me torch apps working and fully functional and sensitive sensors....I mean that in games, the sensors were sensitive enough to work right.

Pocket God...for example, I can shake the phone to cause an earthquake in the game...that wouldn't work at all until I flashed JT's 9/12 kernel...

Now, I am on MIUI and the stock kernel did not have this functionality, so I flashed JT's 9/12 kernel,....torch apps working, but sensors still aren't working right...

I realize this thread is for the Glitch kernel, but I ask this because JT's stuff has been mentioned/compared here recently and I am baffled as to why the sensors would work right in CM7 but not MIUI using the same kernel. Is there some file in CM7 that affect this issue that I can perhaps copy to MIUI?
[Fascinate Android Development] PhoenixPath:
I could not get it to work properly on 1.9.9 not matter what I did it seemed. I ended up booting into recovery, formatting everything from the "mounts" menu, flashing the kernel-cleaning script and then 1.8.26.

Booted into that and then back to recovery for one more kernel-clean and jt's 9/12 kernel.

Seems flawless for what I use it for. Sensors and volume all working decently...would love my glitch back though. My OCD misses my extra OC steppings. ;)
[Fascinate Android Development] Bubbadogg14:
His screenshot with his music player he was listening 2 wiz khalifa. My buddy is his photographer.
[Fascinate Android Development] sageDieu:
The picture was to your illegible typing.

To the people talking about sensors, if you read back a few pages you will see that there has been an issue with going from the 1.9.9 kernel (with working sensors) to glitch that makes sensors not work... over the past few days ssewk2 and strings have been working their butts off and it looks like we will get a release today or tomorrow that will fix the issue.

For now either stay on the default kernel, or live without sensors for a day or two. And make sure to give strings and ssewk your thanks for all the time they've devoted to this!
[Fascinate Android Development] sixstringsg:
I didn't really want to release a build without BLN. I'll give it a quick look this morning, if nothing pops up then ill get y'all a build. How many of you have been using the sound tweaking script?
[Fascinate Android Development] speedingcheetah:
The default kernel in 1.9.9..the sensors didn't work right then either..at least for me...
[Fascinate Android Development] PhoenixPath:
Not doubting you for a minute, but on 1.9.9 it *never* worked for me. Stock kernel, jt's kernels, glitch....no sensors, random reboots....no matter what I tried (I am not new to this...)

1.8.26 + jt's 9/12 is what seems to work best on my particular device atm. Every phone (at least with these infernal devices we call "Fascinates") seems to react differently to just about everything, so my setup may be as unworkable for others as 1.9.9 seemed to be for me.

But enough about MIUI. This is about Glitch. I miss me some Glitch. :'(

*cries*
[Fascinate Android Development] sixstringsg:
Here ya go:
[Fascinate Android Development] 123SIT:
Pre4 works on build 5. Been running it since build 5 came out and no issues so far.

Sent from my Glitched CM9 Mesmerize
[Fascinate Android Development] Azuma73:
V14 pre4 workin' fine on Build 5 here too!
[Fascinate Android Development] tripacer99:
Do fixes to camera, like time lapse, still work after flashing glitch pre4 on build 5?
[Fascinate Android Development] fulaman:
I haven't had a chance to try it out yet. I do know that zoom in and out are working, Moviestudio or w/e it's called works perfectly, panoramic photo shooting works, and 720p HD Recording works.
[Fascinate Android Development] Enyo.:
Nevermind.
[Fascinate Android Development] Eris _2.1_2010:
I could swear there's a screenstate governor in the glitch recovery settings or I'm seeing things.

Sent from my Frosty Ice Cream Sandwiched Mesmerize
[Fascinate Android Development] suppliesidejesus:
You didn't HAVE to come back just because the ban lifted...
[Fascinate Android Development] joshkoss:
And you don't have to go out of your way to be offensive.

Lets keep it ontopic people.
[Fascinate Android Development] DevinLeFevere:
Is there any cure to SOD? I'm running the kernel stock settings in CM skang and getting a sod every 1-2 days once a day :( Ideas?
[Fascinate Android Development] sixstringsg:
Does it happen on stock kernel?
[Fascinate Android Development] neh4pres:
I have noticed 13.1 introduced sod for me. But not often. And when it does toggling volume you will hear the max volume notification. So the phones not dead, just the screen don't power up.. I will do research on getting logs when i get internet at home again.. Seems the snow is blocking my cell service
[Fascinate Android Development] Enyo.:
Great kernel.

My settings are -

1400MHz = -75mV

1300MHz = -75mV

1200MHz = -100mV

1000MHz = -100mV

800MHz = -100mV

400MHz = -100mV

200MHz = 100mV

Been running stable for awhile now.

Running with MIUI. Got SOD with -125mV with 200MHz-1200MHz & -100mV with 1300MHz-1400MHz.

GPS also works well (don't use GPS at all though, I don't drive) and Even without an Overclock, its still very Snappy.
[Fascinate Android Development] sageDieu:
does anyone remember ssewk2x's ETA calculation? something funny, E=QA^2 or something like that... I've searched the thread with no luck. I want to keep it for later

Sent from my ICS SCH-i500
[Fascinate Android Development] Holliday:
Just wanted to add to the comment about the screen not waking back up on power press, but the soft keys light up and appear to respond. Been happening a lot the past couple of weeks.
[Fascinate Android Development] joshkoss:
happened to me in low cell quality areas a couple times within a matter of hours. Also noticed after i turned off screenstate scaling and set the leakage to medium it didn't happen.
[Fascinate Android Development] ssewk2x:
Found it for you: http://xdaforums.com/showpost.php?p=20644481&postcount=2608
[Fascinate Android Development] foxfire450:
I've had this happen once in a great while, but it just now happened while I was in a call. I went to hang up, and the screen wouldn't come back on but the buttons would respond. It also made the "call lost" sound.

I'll start by setting the screenstate scaling to disabled to see if that will help.
[Fascinate Android Development] ssewk2x:
I think I have discovered a potential cause for this in something we introduced into the touchkey driver for V13.1 - the same code is present in the ICS kernel (in fact, that's where I leveraged it from), too. I'm building a test kernel with a fix right now.

I have at least one of these lock-ups per day, so it should be reasonably easy to see if what I've done will do the trick.

Also in the works, with a HUGE amount of help from Electric Bill (read: he is doing most of the real work), is some pretty good progress on the phantom keypress issue. Oddly enough, I think the lockup and the keypops may have the same root cause, which is crappy hardware causing bad EMI. Some phones appear to have it worse than others.

Edit:

Well .. anyone want to test this b****?

Fascinate: http://dl.dropbox.com/u/28682151/Glitch-kernels/CM7Fascinate-Glitch-TEST-01-17-2012.zip

Captivate: http://dl.dropbox.com/u/28682151/Glitch-kernels/CM7Captivate-Glitch-TEST-01-17-2012.zip

Vibrant: http://dl.dropbox.com/u/28682151/Glitch-kernels/CM7Vibrant-Glitch-TEST-01-17-2012.zip

i9000-T959D: http://dl.dropbox.com/u/28682151/Glitch-kernels/CM7i9000-T959D-Glitch-TEST-01-17-2012.zip

Included:

-- lots of bandaids for phantom keypops. you might still get a few, but it should be a big improvement.

-- hopefully no more lock-ups coming out of suspend in low signal areas.

I'd specifically like to have people who are still experiencing both issues on V13.1 or later try this out and let me know if it's an improvement or not.
[Fascinate Android Development] sarkozy:
Well it boots lol.
[Fascinate Android Development] ssewk2x:
Rofl, i knew that. I'm posting with it now. ;)

No lockups or pop-ups for me yet. knocking on wood...
[Fascinate Android Development] sarkozy:
Yea, same here. I had a couple of instances this morning driving to the dentist through some low signal areas in the swamp when I noticed the phone was off. It's sketchy at best here in my office and so far so good. We shall see.
[Fascinate Android Development] Enyo.:
Update to my last post.

Here are my latest stable settings.

1000MHz = -150mV

800MHz = -150mV

400MHz = -150mV

200MHz = -150mV

Going to test for another few hours.

The best battery life I've ever seen on MIUI.

My only complaint is that the green screen is back. But I can deal with that.
[Fascinate Android Development] neh4pres:
If you can't fix the green screen you have some lacking skills. Reading comprehension may be one of them
[Fascinate Android Development] Enyo.:
What?

I fixed it now.

It seems to be on miui. Cm7 I use my custom settings and no green screen.

Miui I use my custom settings and green screen appears.

So ill just use the default settings.
[Fascinate Android Development] neh4pres:
You don't have to go that far. - 57 gamma works for me.
[Fascinate Android Development] neh4pres:
@Ssewk2x did you get my pm?
[Fascinate Android Development] sixstringsg:
Your minimum brightness might be lower on MIUI, thus causing green screen.
[Fascinate Android Development] Enyo.:
I've always wondered why it did it on miui and not cm7.

I'm switching back to cm7 (going to test the CM7 7.2.0 Gigglebread)

Either way, solid kernel.
[Fascinate Android Development] shag_on_e:
Okay friend, I've done a total clean install starting from stock repartition, then went to one of my notorious low signal zones and came out problem free. I had about 4 data sucking apps running at the same time and had no issues. Once again, thanks for your extended work. Wish I had half your skills. I hope you smashed this bug, if not I still couldn't live without some Glitch action.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
Good to know, thank you. I can't take credit for this round of patches, tho. Electric Bill (dmriley on github) did all of the real work. I just put his code into the glitch kernel and occasionally helped interpret his lab results.

He, on the other hand, came up with the code changes, and even disassembled his phone and poked at it with an oscilloscope! Braver man than I, for certain.
[Fascinate Android Development] ssewk2x:
Well, i had a lock-up overnight. The screen was on, but black. No useful info in logcat or dmesg either.

FFFFFFFFUUUUUUUU....
[Fascinate Android Development] sendan:
Then we can only draw one conclusion...

The gremlins are back. >:0
[Fascinate Android Development] ssewk2x:
Gorrham gremlins.

Good news, though. During the blackout (F*** SOPA and PIPA), I was able to build a debug kernel which I have running on my phone. If it locks up trying to suspend or resume (which I think is what's happening), then it will tell me which device is the culprit and I can go from there on my way to debugging the issue.

Last night's lockup remains the only problem I've had so far.
[Fascinate Android Development] k_nivesout:
My phone did the SOD overnight too. No phantom presses so far, although I haven't been in a low signal area. Although it would happen (very occasionally) at my house where there's decent signal, nothing since I flashed the test kernel yesterday afternoon.
[Fascinate Android Development] shag_on_e:
I got some pop ups this morning passing through a low signal zone. Haven't had any lock ups so far though. Damn gremlins! You can doowitt(Rob Schneider guy from Adam Sandler movies voice)!

~~~~There is no spoon~~~~
[Fascinate Android Development] Holliday:
Weird thing is I have been using Glitch kernels on my Fascinate for over six months and have never had a phantom keypress. It really must be a hardware based issue.

What is a phantom keypress anyway?
[Fascinate Android Development] shag_on_e:
Ah, that would explain why multiple people have the same issue while in a low signal zone. Or flashing back to stock I don't get a pop ever.

~~~~There is no spoon~~~~
[Fascinate Android Development] shag_on_e:
~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
I've still got a few tricks up my sleeve for this, but more and more i see that it's a hardware issue. We've put a bunch if filtering code in to the kernel, but just can't eliminate all the phantom pops.

Im about to the point where in going to load a stock kernel and dump all the frakkin gpio configuration registers on the gorrham chip and see how they compare to our kernel. Ugh. Lol.
[Fascinate Android Development] stalls:
What bout all the phantom calls or rings? Can't remember if that is our isn't kernel related
[Fascinate Android Development] xsc0rchx:
I have noticed on the new test kernel that the screen state scale for lazy is not available. Not sure if this is by design or not, but I believe I had more issues with lazy than conservative. Don't know if that really helps or not.
[Fascinate Android Development] bigmike88:
When i have used a stock ROM and kernel, The pop ups and key presses are at their worst, it's what made me start flashing custom roms/kernels in the first place...I'm starting to think its hardware.
[Fascinate Android Development] sendan:
Yeah tbh I've never actually had a phantom keypress...although my sister's fascinate suffers from them all the time, I was fooling around with it a few weeks ago and it did it a few times. Keep in mind it was in my room (where I've never had one on my phone before), and at the time it had the same exact ROM/Kernel.

It seems obvious that Ssewk2x's work is helping though, it's possible the hardware and kernel both play some factor in the bug. -_-

I would definitely recommend keeping your keys clean though, I seem to remember that helping with the bug back on the old SC ROMs.
[Fascinate Android Development] shag_on_e:
I'm no pro, and I know the devices are slightly different so I suppose it very well could be hardware. Personally though, I tested full stock in a garbage signal zone and never had a hiccup. Plus, I like to try and keep up with the TW roms and kernels development, and I can't remember ever seeing anyone mention this. But, regardless, this is a must have for me, and ssewk2x, six, and TK are the pros so I trust their judgment.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
Yeah, just in the last 4 posts or so, one guy days he sees it far worse on stock rom and kernel, and another doesn't see it there at all. Another says he doesn't see it on our rom / kernel, and another gets it even with all our patches.

It's got to be hardware variations...i know the root cause is interference from the radio antenna, which is right next to the keypad's data and interrupt lines, with no shielding (for shame, Sammy) whatsoever. It's conceivable that, like leakage with oc/uv, minor variations make some phones more vulnerable than others. Sadly, im afraid the best we can do is filter as much as we can. I don't think I'll be able to eliminate it entirely for everyone :(
[Fascinate Android Development] ssewk2x:
I haven't even looked at that yet. It's probably going to be similarly challenging, tho. I get one phantom ring event per month on average, i think....not enough for me to move it to my front burner yet, lol
[Fascinate Android Development] lordnikko:
I had frequently noticed random keypresses while plugged into aftermarket chargers. Found one the other day and noticed the voltage was .5 volts higher, and the amperage was much less than the stock fascinate charger. Obviously the people having issues are having it while on battery, just trying to help you find the common link. I am not sure if this will help you at all, or if it has been mentioned before by anyone in this thread.
[Fascinate Android Development] Azuma73:
My phone just did the craziest thing! It was on charger & I was listening to music via bluetooth headphones, I disconnected charger and it went black? Then it automatically reflashed my rom, luckily I had a backup!

I'm gonna start fresh & see what's up! Just really bizarre happenings? :confused:
[Fascinate Android Development] fulaman:
So basically the random keypresses are a result of random stuff on the kernel? Like the messaging app and gmail often just exit out on their own.
[Fascinate Android Development] stalls:
I probly get to 2 - 3 a day sometimes.. it sucks especially when I'm on the phone with someone and someone else calls it will just keep ringing in my ear piece the whole time...

but as far as the phantom keypress I don't get there is hardly at all anymore with your latest kernel
[Fascinate Android Development] millwood:
I have been saying this for a while now, but I believe that the Phantom presses and SOD can definitely be contributed to Hardware more than software. I bought my Fascinate the week after it came out, I also bought my wife a Fascinate last March. I am still on my original phone with a VERY, VERY rare phantom key pop. My wife's phone has had phantom key pops with every Factory ROM, and every non-factory ROM that I have installed. Also, the same with every Kernel. She has had her phone replaced 4 times now for this very reason, and is about to get her 5th phone.

I would be interested to see what the dates are on the phones that seem to be having these issues. I would guess that newer phones are the ones having such issues and the older phones are more stable. I find it really odd that each of her phones have done the same thing, only difference from the setups I have been running is that she has a Facebook app installed where I don't. I uninstalled the app for a few days and it made no difference. Her phone had the phantom key pops so bad last night, along with the unresponsive soft keys, that I had to restore to factory settings using ODIN to get anything. I tried wiping the phone first, flashing other roms next, flashing other kernels next, and finally took it back to stock before the soft keys finally worked again. Not 2 minutes later it started in with the key pops. I have tried several different SDcards and even new formatting on them before using them. No luck. It has to be a hardware on a major level.
[Fascinate Android Development] neh4pres:
Your wifes only hope is glitch 13.1.. I had horrible issues but the new work ssew has done is About 90% better and is very apparent.
[Fascinate Android Development] sol_671:
Seems accurate I had my fascinate for a while now and never had it replaced ever and never had any key popups, its why I never reported them even in areas where I have zero bars.
[Fascinate Android Development] fulaman:
For CM9 ICS, would you think that using the kernel that comes with it would really in less program closes like when I open the messaging app, it just closes on me consecutively 4 to 5 times in a row.
[Fascinate Android Development] Bubbadogg14:
Are you using ics glitch and asking if jts kernel in build 5 would solve your problem? Did you try fix permissions?

Sent from my SCH-I500
[Fascinate Android Development] millwood:
Yeah, my wife's only hope is either a new "older" date Fascinate or a complete new phone. Glitch 13.1 and even the latest test Kernel from 1/17 are still no better. Both caused major problems. Worse than the stock Rom.
[Fascinate Android Development] yonith:
If the phone does this regularly while STOCK, then you should return it.
[Fascinate Android Development] millwood:
I already figured that out. I am way ahead of you, I was more reporting that this seems to be a reoccurring hardware issue with phones built at more recent dates.I still suspect the issue is only with newer phones rather than the first ones that came out.
[Fascinate Android Development] gawbage:
AHGHGHGH

I've been rooting, flashing, recovering, repartitioning, hacking, editing, and screwing in general with Android for well over two years now, but I have finally come to a terrible realization. I SOMEHOW F*CKED UP! It all started when I was introduced to Glitch kernel v14...

"Ahh, finally a new version of my favorite kernel ever!" I thought. Well, with that new kernel came a very interesting feature... you could manually change the clockspeed multiplier... so, that's just what i did. Maybe I went off the recommended parameters just a little bit, but nothing that was unsuggested. Nevertheless, my phone froze after one minute of use, and then when I turned it back on, It just never behaved the same ever again.

ICS slowed down to a chug, the phone rebooted randomly, and I just had enough of it. I redid everything with ODIN first, then with Heimdall flashing back to ICS between the two tries. It fixed the laggishness, but never the lockups and the performance losses. I then, after much frustration with ICS, proceeded to flash MIUI for the first time in months; the performance was okay at best, but at least the reboots weren't as frequent. Then... I plugged it into the charger. Within minutes, I was guaranteed both a lockup and a minor aneurysm if I used it as it charged.

After nearly losing all sight in my left eye due to the high stress levels, I ODIN'd back to stock, left it there, and STILL experienced lockups. I loaded up ICS again, and wow, it was indeed smoother than before, but F*CK MAN, I still got lockups. I then flashed the latest ICS version planning on coping with the reboots and then... the ***** reboots back to recovery after installation and after powercycling. I'm telling you, the phone hates me.

So, I've come tothe conclusion that I screwed up the processor beyond repair somehow. Or maybe the multiplier values are hardcoded to the system reserved memory, staying active even after a repartition. Whatever the case, I would love some feedback.