yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] saps:
Hopefully you get yours at months end ;)

But yeah I'm still on the same sdcard that came with my Fassy which I bought last September on launch day. I've also been on some incarnation of GB since July. Countless different MTD roms different radios and of course kernels. Through it all my card is A-OK. Equally true the frying sdcard issue is prevalent enough. I could only venture a percentage guess but I'd have to put it below 15%.

Knock on wood still going strong with original sdcard and I never get bootloops when switching radios, kernels or rom's.

---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------

Yeah but replicating the problem or formula for failure was never conclusive. Two users with the same set-up and one would fry an sdcard and one wouldn't. I'm not looking to argue but saying it happened some got bit but by and large it seems to be under control these days
[Fascinate Android Development] droidstyle:
I never was on mtd or ec09 back then...all I ran was froyo roms...Fwiw Im not complaining or placing blame anywhere. I just posted because sixstring was asking the other guy about it. I have a new sd card on the way and Ill continue to use glitch....besides I paid nothing for my fascinate, so it does not bother me if I have to buy a few sd cards. My motto has always been you gotta pay to play lol...no worries here.
[Fascinate Android Development] sageDieu:
Sorry to go off topic, but HORY SHET six, I remember getting you to 100 thanks like, a month ago. Now you've gone and gotten yourself 1300+...
[Fascinate Android Development] nklenchik:
It could be the quality of the sd card too. I've had the same 32 gb since I bought my old DX back in July and just transferred it over to the fascinate...no problems since then (knock on wood)
[Fascinate Android Development] Schmarvin:
What would you guys recommend for the longest battery life? Low-voltage?
[Fascinate Android Development] akellar:
Read the OP
[Fascinate Android Development] sageDieu:
What do you mean? I think you meant to say leakage, not voltage. Leakage has to do with the hardware chips and the lower the better if your chip supports it but high usually works for most people. Voltage is how much power is given to the chip at any given time, and it can be controlled with voltage control, pimp my CPU, etc. Lower voltages use less power but too low will make the phone freeze.

Sent from my MIUI SCH-i500
[Fascinate Android Development] ssewk2x:
That's not necessarily true. It's more like "whatever lets you undervolt the most is better for you." For example, while HL works for me, I am actually able to undervolt more with ML. This won't be true for everyone, though. You just have to spend the time and experiment to find out which is right for you, and the answer definitely won't be the same for everyone. Or if you don't care, just pick one and don't undervolt by a lot, lol.

FYI, on HL I was able to undervolt by -50, on ML I have it down to -75. I haven't tried to go lower yet, nor have I tried LL yet.
[Fascinate Android Development] sixstringsg:
And OC the highest. That was actually the original goal, UV was a good side effect.
[Fascinate Android Development] Schmarvin:
No, I meant voltage. I was asking which would uses more power? The less power used the more battery life. I haven't really used the Glitch kernel before, but everyone suggests it. So, I figured I'd try it.

Should I stick with the Medium-leakage or low-leakage?
[Fascinate Android Development] Jazz848:
YDoesn't it stand to reason that lower voltage = lower power? I don't mean to sound rude or anything, but it just seems to make intrinsic sense as long as we're not directly adjusting amperage at the same time...
[Fascinate Android Development] ssewk2x:
You are correct, sir, at least in a general sense.

http://en.wikipedia.org/wiki/Joule's_Law
[Fascinate Android Development] Jazz848:
Aye... hence 1,000,000v static not vaporizing every poor sap to touch a doorknob.

Alright, back to the current discussion everyone.

~$ sudo make bad pun
[Fascinate Android Development] sixstringsg:
How is the Mesmerize different from the fascinate?
[Fascinate Android Development] sixstringsg:
I stated the "changelog" about two posts before the links. There are days when either you get links, or you don't. Sometimes I have time to post builds, but not a changelog or update the OP.
[Fascinate Android Development] scarmon25:
honestly i dont think there is much difference, we have been using the fascinate kernels for as long as I can remember.
[Fascinate Android Development] scarmon25:
OK Its got something to do with coming from JTs kernel. I just odined back to stock and flashed CM7, then your Kernel then Gapps and sensors are working fine
[Fascinate Android Development] ekowanz:
Ok.. Sorry for not checking the page before. Cause sometimes i just drop by and only read all the discussion here. If there's a link then i download it and try it.
[Fascinate Android Development] richaoj:
yes, confirmed. sensors don't work when coming from jt's latest kernel... so much work to reflash and everything . . . going back to jt's kernel.
[Fascinate Android Development] scarmon25:
Yeah, honestly it was about time for me to do a fresh install I had been trying scripts and kernels alot lately. So I needed to do it anyway.
[Fascinate Android Development] iofthestorm:
I just updated to the build from the 6th and my proximity sensor doesn't seem to work. When calls come in my screen stays on and it doesn't come back on when I move it away. Might have to do with updating Miui though.
[Fascinate Android Development] ssewk2x:
This build was not intended to fix the sensors. Six is working on getting that stuff merged in still.

What this should fix is the audio blasting problem, and it gives you the ability to customize your audio boost and mic gain via that script. That's all .. For now.
[Fascinate Android Development] sageDieu:
It seems to be something to do with coming from jt's latest kernel, he had changes to sensors that you don't and apparently going from his v5 (bundled with the latest miui) to this breaks sensors. So whenever we get his sensor changes merged it is likely to fix it... let us know if you guys need any help with that.

Sent from my MIUI SCH-i500
[Fascinate Android Development] ssewk2x:
Yeah, I wonder if doing a power-down and battery pull after installing this kernel would help .. Just to make sure all the hardware is reset.

Hopefully we'll gave some progress with the merge soon. What sensors specifically is it supposed to fix, and do you know of a good way to test them? Thanks.
[Fascinate Android Development] PhoenixPath:
Proximity and accelerometer. Easy enough to test with doodle jump and a phone call. I’ll be on irc tonight if there's a need for testers at that point.
[Fascinate Android Development] ssewk2x:
I don't think I'll get a chance to look at anything until tomorrow. I'm on baby / house-cleaning duty today :-p
[Fascinate Android Development] sageDieu:
Yeah the main ones are accelerometer, which can be tested with games or browsers, and prox sensor which can be tested with a phone call. the light sensor isnt a big deal, just for autobrightness which most people don't use.

Sent from my MIUI SCH-i500
[Fascinate Android Development] sageDieu:
Also just checked my compass and it doesn't work either. Also not that important but it helps with gps and stuff... if you need any testing on fixes PM me.

Also as an out-there request... if you get the hang of merging and stuff, the samsung mesmerize kernel source that jt got sensors from also contains a working torch... haha it's something jt doesn't really care about but I personally really want :P so yeah idk how any of that works anyways so it might be impossible for you guys but it would rock.

Sent from my MIUI SCH-i500
[Fascinate Android Development] chopper the dog:
Since jt's v5 includes "true" GB sensor SO files and not hacked froyo ones. Flashing any previously used kernel will break all sensors. If one wanted to use glitch on current builds you would need to find sensor SO's from an earlier rom build and pull them and place in respective places. Files are: sensors.default, geomagneticd, orientationd, libsensor_yamaha_test, libsensorservice. Unzip v5 for location reference.

good day.
[Fascinate Android Development] ssewk2x:
Aha! Conversely, in order to get them working on this, we'll need to kang them from one of jt's builds, no? Thanks, chopper! Good day to you too.
[Fascinate Android Development] chopper the dog:
At this moment the only 2 roms that include the gb sensor SO's is miui and pool party. But I suppose you could just include the proper hacked froyo SO's that glitch needs and include them in the zip as jt did with the new gb SO's in v5 kernel. And people that flashed new miui and then flashed glitch should flash the v5 kernel until a glitch zip with the proper SO's is posted. Pull the froyo SO's from say vgb v6 or the previous build of miui.

good day.
[Fascinate Android Development] Bubbadogg14:
Maybe I'm not understanding what u r saying chop but I an on tsm pool party 1.3 and flashed the newest glitch over the 9/5 glitch n all sensors are broken including auto rotation. So r u saying I need 2 get the froyo SO our use the ones that came with pool party

Edit: also I noticed my voltage setting won't stick after a reboot even though I saved them as boot settings... Anyone else notice this on the new kernel?
[Fascinate Android Development] ssewk2x:
Ok. Please help me understand what parts of this equation are tightly coupled and which aren't. My understanding is that there are 3 parts in play: rom, sensor libs, kernel.

At the very least, it appears that sensor libs and kernel must match. I guess the question is, does the rom have to also match with the sensor libs? Or, can I take an old rom, like the 7/17 build of cm7, give it the new, true gb sensor libs, plus jt's latest kernel, and have everything work? Or, instead of jt's newest, can I merge jt's sensor fixes into this kernel, bundle it with the new gb sensor libraries, and have it work with the same old cm7?

I'm guessing that they all have to match up, and therefore we're kinda boned until the cm7 nightlies get going again and the new gb sensors get merged in. I'd love to be wrong about that, lol.
[Fascinate Android Development] ssewk2x:
Yeah, that was pretty reVOLTing.

Carry on....
[Fascinate Android Development] shag_on_e:
Just a refresher, flashing jt's latest kernel fixes gps completely, and even better flashing back to glitch does not affect that fix. This just keeps getting better. I'm ocd about my gps, but also ocd about my glitch. Now I got both. Life is good!

~~~~There is no spoon~~~~
[Fascinate Android Development] scarmon25:
Had the same result for anyone wondering. Don't know what it is that sticks through the flash but it does.
[Fascinate Android Development] droidstyle:
where did u get jt's latest kernal? all the links I found were broken for the 10/16??
[Fascinate Android Development] neh4pres:
power = Watts = volts x amps. Voltage and amperage are directly proportional in a circuit where resistance is constant. So by reducing voltage there is a reduction in amperage as well.

Sent from the fascinate that holds the record on antutu benchmark
[Fascinate Android Development] Jazz848:
Not necessarily; semiconductors can throw Ohm's Law out the window (ie. p-n junctions).
[Fascinate Android Development] ssewk2x:
Also, JT's GPS fix should end up in the next glitch release. I'm currently running my own debug build on my phone which includes it, and I have to agree with those who have said things like "HOLY ****," and "Finally!!"
[Fascinate Android Development] shag_on_e:
This is great news. I'm glad you were able to squeeze it in, cuz I remember you saying you may not be able to get it in in time. Y'all are great.

~~~~There is no spoon~~~~
[Fascinate Android Development] sageDieu:
great news, what was the fix?

Sent from my MIUI SCH-i500
[Fascinate Android Development] ssewk2x:
It wasn't actually a change to the kernel, it was a change to the device tree. All I had to do was run a repo sync in my environment before I built my test kernel and BAM, there it was. No big deal, really.

It looks like he changed some permissions on some compass-related driver files or something. Not terribly sure how that would affect it, but I'm not gonna complain either!
[Fascinate Android Development] Coolsaber57:
Ok, this is driving me nuts.

I've tried all three leakages, undervolted, left stock voltage, overclocked/not overclocked, changed governors/schedulers, wiped davlik/cache but I keep having this problem.

My phone will reboot itself in the middle of a phone call.

Has anyone else experienced this problem? I'm pulling my hair out trying to figure out what's wrong and had to move back to the normal CM7 kernel to prevent it from happening. Though, I'm having SOD and lag issues on that kernel :mad:

Any help? Ideas?
[Fascinate Android Development] Jazz848:
I would Odin back to stock (DL09 is my standby, but ED05 is also good) and start from scratch. Have you tried that yet? Also, were you on nightlies or the "stable" version when you were having the issue? Finally, just for clarity, was this ONLY happening on Glitch?
[Fascinate Android Development] neh4pres:
Try a data wipe.. And don't restore data and see

Sent from the fascinate that holds the record on antutu benchmark
[Fascinate Android Development] rjskalet:
i +1 this just because usually a clean wipe will solve most problems. and then download high leakage and try it with a nightly, if you arent already on one.
[Fascinate Android Development] sageDieu:
mmmmmmm 13RC is smooooooooooth

Sent from my MIUI SCH-i500
[Fascinate Android Development] droidstyle:
Link? Me want now!!:D
[Fascinate Android Development] sixstringsg:
You don't get now :p
[Fascinate Android Development] scarmon25:
Keep hearing all these great things. Like a **** tease. Hahahaha. Na seriously. Thanks for everything man.
[Fascinate Android Development] akellar:
This is why Beta testers are better served to stay quiet. Just saying. :rolleyes:
[Fascinate Android Development] droidstyle:
I was just joking lol...I know that he is a beta tester.;)
[Fascinate Android Development] AardvarkAdventure:
HALP!

Flashed V11 High Leakage on CM7, bootlooped, and can now only get into GLITCH recovery, in which I cannot access my backups.

Also cannot get device recognized with ADB, nor Fastboot.

Anybody out there?
[Fascinate Android Development] scarmon25:
If you can access glitch recovery. Try flashing this kernel and it should allow it to boot. http://db.tt/IpNiggmX
[Fascinate Android Development] sixstringsg:
You shouldn't be using V11.
[Fascinate Android Development] sageDieu:
sorry for spilling, haha my phone has never been this smooth, GPS locks instantly, etc... it is great. other than a tiny bug I sent to six already, in my opinion this baby is ready for primetime. shouldn't be too much longer!

Sent from my MIUI SCH-i500
[Fascinate Android Development] sageDieu:
if you are stuck in recovery, reflash miui or cm7 or whatever and it will flash back the normal recovery as well which you can use to restore or whatever. then go download glitch v12 and use it.

Sent from my MIUI SCH-i500
[Fascinate Android Development] AardvarkAdventure:
sageDieu, scarmon25, sixstringsg- THANK YOU for the quick responses!

In glitch recovery, I seem to have no access to, well...anything. "E:can't mount /sdcard" over, and over, and over again.

I've got it showing up with ADB now, but not sure where to go from here. I know I have a good backup on the sdcard.

I'm assuming I could push a different recovery through ADB in this state, but I'm not sure whether or not that would help (or which recovery to push). This isn't my phone, otherwise I'd be more "caught-up" with things.

Any and all help appreciated.
[Fascinate Android Development] sixstringsg:
Do you have heimdall?
[Fascinate Android Development] shag_on_e:
I would suggest your old pal Odin at this point. Start fresh.

~~~~There is no spoon~~~~
[Fascinate Android Development] AardvarkAdventure:
I've actually never heard of this...what are the advantages over ODIN?
[Fascinate Android Development] sixstringsg:
Open source, cross platform, more versatile.
[Fascinate Android Development] 4FatSno:
Follow the first three steps of this:

http://xdaforums.com/showthread.php?t=1124391

(DL09 is pretty good option.)

On step 4, remove the battery (keep it removed) before going into downloading mode. Start step 5 until Odin gives you a "PASS". Unplug the phone. Shut down Odin. Reopen Odin. Plug the phone back up. Get into download mode (hold vol down + power ). Install the radio of your choice. Here's EC09: http://xdaforums.com/showthread.php?t=1132236

Once you get "PASS",unplug the phone. Reset Odin. Plug phone one last time. Get into download mode (hold volume down + power). Install CMW 4 fixed for CM7. (you have this since you were already on CM7). When you get a "PASS", unplug the phone. Install the battery. Three finger into recovery. Flash CM7. When done, reboot phone. Enjoy.

Using the power button (not the three finger method) , you can go back into recovery and restore a backup or install glitch v12.

sent from outerspace
[Fascinate Android Development] sixstringsg:
App has been published to the Android Market, waiting for approval. For now it won't flash HL, but an update will come (maybe before you can even get the app) that will fix that.
[Fascinate Android Development] scarmon25:
What's the app called
[Fascinate Android Development] sixstringsg:
Glitch kernel updater RC
[Fascinate Android Development] scarmon25:
Yeah just found it and bought it. Says error connecting to server on ML. Haven't tried other versions.

NM. My dumbass did set it up in settings. Hahah. Works

---------- Post added at 07:16 PM ---------- Previous post was at 07:07 PM ----------

Where does it save the downloaded file too. Doesn't seem to be flashing through the app. At least the build date in CPU spy isn't changing.
[Fascinate Android Development] sixstringsg:
Did you check all three boxes? Download, prepare, and reboot?
[Fascinate Android Development] scarmon25:
Yeah. It rebooted and goes through like a 2 Ms recovery flash then rebooted again. But build date still says 922. It shows it downloading. Then says preparing recovery(which is misspelled :) no worries) then reboots
[Fascinate Android Development] bigwilly90210:
Hey so release candidate meaning V13? Cause that'd be totally worth it to me... I'll end up buying to support either way. Ha. Just really excited about V13.
[Fascinate Android Development] sixstringsg:
A release candidate for V13, yes.
[Fascinate Android Development] scarmon25:
Hey six. I got is fixed. Not gonna say how on here cause I don't want anyone redistribution of your kernel without paid. But I think there's a hiccups in the flash process.
[Fascinate Android Development] sixstringsg:
You have a PM.
[Fascinate Android Development] bigwilly90210:
Thanks. Gonna go pick that up right now. :-)
[Fascinate Android Development] scarmon25:
Awesome app man. Left you a good review. Its worth every penny to help you guys out and get access to RCs
[Fascinate Android Development] PhoenixPath:
Bought whether it's working or not. Ya'll deserve it and more. Does this just go to you, or to the group?
[Fascinate Android Development] sixstringsg:
Here is the link to the thread for the app. Please post any questions or comments on it there. http://xdaforums.com/showthread.php?p=18665472#post18665472
[Fascinate Android Development] sixstringsg:
It will be distributed.
[Fascinate Android Development] PhoenixPath:
Awesome. Insta-lock on gps with the current RC. Love it. When my son gets his phone back (and I get the tires replaced on my car) ill buy it for his as well. Thanks!
[Fascinate Android Development] LetsGoBlues:
1) What changes have you made?

2) Will you be releasing the kernel for free after the RC?
[Fascinate Android Development] sixstringsg:
1) I'll go find the changelog.

2) Of course, there will be a stable release as always.

Edit: changelog. It's probably not complete, but oh well. I'll make it all pretty for release.

- Upstream synced

- New CFLAGS again

- mfpu switched from neon to vfpv3

- BLN now working, with LED timeout (thanks to Zacharias.maladroit)

- Back to hard float

- Updated toolchain to 4.5-2011.09

- Modified screen colors to look better

- Better reactivity under load

- 348MB RAM available

- Better 720p video recording (less buggy)

- Slight speed-up on SDcard read

- USB power drain fix

- Better memory management

- Back to 3.0V for the screen

- Bugfixes
[Fascinate Android Development] LetsGoBlues:
Awesome...thank you for the quick reply.
[Fascinate Android Development] Tk-Glitch:
Ahah that's really funny to see how Six is becoming the new Tk slowly :p Glad to have this guy on my side ! I'll make an updated and full changelog before release, and of course the final kernel will always be free. See the app as a contribution/donation more than anything else, but yeah of course it's convenient, and yes you get something back for contributing with the access to RC kernels (as well as the lazy-friendly auto-flashing luxury :p).
[Fascinate Android Development] saps:
Good to see you alive and kickin' TK :D
[Fascinate Android Development] Tk-Glitch:
Thanks :D Doin' my best for that ! This app was a surprise for me, I thought it was still at basic stages, but in fact it was done already haha. I love how the beta testers became great friends and the best supporters and partners ever.

Now we are the Glitch Team, and I'm sure we'll do great things together !
[Fascinate Android Development] shag_on_e:
One could only imagine where thus will go. I've been rockin this kernel since Times Infinity was gracious enough to hook us up with the port, and it just keeps getting better. Y'all got my support for sure. Got the app already and can't wait to tinker. Great to have you back TK, and of course thanks a million to sixstringsg and ssewk2x.

~~~~There is no spoon~~~~
[Fascinate Android Development] japin:
I just purchased the app and downloaded the medium leakage RC, I have to say I am very appreciative of the work that went into this, no more yellow when the screen is on the lowest settings for the auto dim, that was a big pet peeve of mine. I can also say the memory management is better, I have more memory available with more widgets on the screen than I had before. U guys did a great job on this kernel and I am happy I could support u.
[Fascinate Android Development] Jazz848:
A big +1 to that! Hope life's treating you proper these days. Very glad to see you back in the fray!
[Fascinate Android Development] sageDieu:
I have like no way at all to buy the app, but I shall figure it out. I owe you that much :P

Sent from my MIUI SCH-i500
[Fascinate Android Development] dallas6672:
Is BLN suppose to be timing out? Tried with and without BLN Control Pro or Blinky. Also tried setting the timeout in BLN Control to 1 hour.

Running RC1 ML with MIUI 1.10.14.3

Thanks again for everything y'all have done!
[Fascinate Android Development] sixstringsg:
We know about the issue. We will be working on tracking it down. They started doing that when we implemented the timeout with screen on, they started timing out with the screen off as well
[Fascinate Android Development] scarmon25:
Yeah I just noticed this as well. They come on around four or five seconds then they go off.

Edit. NM.
[Fascinate Android Development] droidstyle:
Just wanted to say I gladly donated 5.00 and purchased the app. Thanks!
[Fascinate Android Development] scarmon25:
It did me tthat way too. Try clearing data from the app under manage apps. It has a splash screen that has trouble popping up. Once you get it open. You can disable the splash screen under settings.
[Fascinate Android Development] droidstyle:
Got it Thanks!

*on a side note, version v13 kicks A**!! Love how the bln times out now, gps has smokin fast lock time, and this is the best 5.00 I have ever spent! Thanks again team glitch!!!