yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] aroy002:
hey guys, still at a bootloop. I downloaded the latest nightly, and flashed it with the 3 button approach... no go.

Then flashed the latest JT kernel and still no go. And then I flashed JT's kernel followed by Glitch's...no go.

I'm thinking I'm going to have to start over in some way. All I have access to right now is blue CWR, unless there's a way to access the glitch CWR without using the reboot button?
[Fascinate Android Development] shag_on_e:
Sorry, I'm too drunk to be posting. Ignore this...carry on.

There is no spoon ~~~~
[Fascinate Android Development] scarmon25:
The only other way to get it to reboot into the glitch recovery is with ADB. Once you have access you can type reboot recovery and it will reboot you into the right recovery. But given your problems it may be beneficial to just odin to stock and start fresh.
[Fascinate Android Development] iofthestorm:
Sweet, confirmation. As you can see it's full. Now, there's a slightly more permanent solution that you can use to keep your apps with lots of data, but it involves more terminal trickery. Nothing complicated for someone who's comfortable with linux but there is a definite potential to cause more force closes if you don't do things right.

Basically, /data/data is where apps store their data (duh). On the galaxy s cm7 builds there's a partition called /datadata that is symlinked to this address for performance reasons (from my googling it seems like it was an early lagfix). For us, especially with everything on ext it's completely pointless. Before you do anything, back up all your apps with titanium backup or something similar.

You can simply delete /data/data (the symlink - don't do "rm -rf /data/data", just "rm /data/data"). Then, "mkdir /data/data" and finally "chown system:system /data/data" (all in a root session). At this point to get your data back you can use titanium backup and restore data only for your apps, although you might need to reboot to get superuser to actually work (it took me quite a while to realize I had forgotten to set the correct owner on directories so I'm not sure if this is actually an issue if you do it right). You can also just cp the contents of /datadata since you shouldn't have actually deleted or unmounted that partition anyway. Make sure to use the -p flag to preserve ownership of directories, otherwise apps will just be unable to access their data because each app has its own user for its own files. Just do "cp -rp /datadata/* /data/data/" and it should work.

As a standard disclaimer of course, I take no responsibility if you **** up your phone, but if this helps feel free to hit thanks or something and definitely let me know if it works for you since I've only done this for myself.

One final note, if you wipe data it recreates the symlink so delete it again when you wipe (and in fact you can even do this and then make the folder in adb shell if you just plug in a usb while you're in clockwork, which should in theory let everything just work).
[Fascinate Android Development] euklid:
Sorry if this was answered already, but I just installed cm7 and I want to flash this kernel. Do I use voltage control or the built in app in settings to create profiles for my phone? Like on demand and min and max frequencies and use vc to just undervolt??
[Fascinate Android Development] scarmon25:
Well if you're not going to undervolt then you can use the built in options. But if you want to be able to adjust the voltages and tweak it a little more then I would use voltage control or pimp my cpu. Either one is fine.. Also if you go with an app. I would use it for everything.
[Fascinate Android Development] boldfilter:
Thanks for the info, thats very interesting. I wouldve never expected this to be the problem. I dont think Im going to worry about it too much if it just resets after you wipe. Ill just keep an eye on it from now on. So, does this kernel use that partition alot? Ive only experienced this with this kernel and miui, this kernel and cm7 is fine. I havnt experienced this with JTs kernel. Is it a kernel problem?
[Fascinate Android Development] sixstringsg:
No, it was just a coincidence. It's a CM7 and MIUI problem in general, doesn't happen to everybody and doesn't happen often.
[Fascinate Android Development] sixstringsg:
The only problem with this is it is moving the Apps data to a slower memory, therefore decreasing the speed and smoothness of your system in general. It should only be used as a last last resort. But come on, how many of you really need all the Apps you have?
[Fascinate Android Development] boldfilter:
Its really only a handful of apps that are taking up the majority of the space, the bigger games, so its not a big deal.
[Fascinate Android Development] fstbusa:
Anyone else getting insane UVing using this new build?

I'm running CM7 build 56 and the latest glitch

Not OC as I'm shooting for battery life

Running LL, bfq/conservative

1000mhz: -125

800mhz: -125

400mhz: -200

200mhz: -225

100mhz: -225

No SOD, hang ups, FCs, ect. Running this for 3 days straight. Going to shoot for -175 up top and -250 down low!!
[Fascinate Android Development] sixstringsg:
Make sure it's reporting right once, and push everything to the lowest UV possible and see if it freezes. I'm beginning to think we broke something in the way of UV, but I have no idea what it could be.
[Fascinate Android Development] fstbusa:
How do I verify if its reporting correctly?

I was using Pimp my CPU and downloaded voltage control and the schedulers and all the voltages matched up with the settings in PMCPU
[Fascinate Android Development] sixstringsg:
This is how:
[Fascinate Android Development] akellar:
Just did this and it froze up and rebooted.
[Fascinate Android Development] :
I can also verify a freeze when pushing voltages all the way down.
[Fascinate Android Development] xain713:
I also UV it to the lowest and it froze also , running medium leakage
[Fascinate Android Development] sixstringsg:
Perfect, that means it's working right.
[Fascinate Android Development] fstbusa:
As soon as I lowered 1000mhz to -250 it froze.
[Fascinate Android Development] wessiide:
I just wanna give a shout out to the amazing devs who finally got this kernel exactly perfectly right! I've been weary of coming back to glitch after the super glitchy first porting of jts latest tweaks but am so happy I have taken the dive. The latest kernel is so so clean and snappy, never been so smooth. Overclock and undervolt works better then ever. THANK YOU SIX AND ALL! great work here you are all very appreciated sirs.

You guys = +1 !!
[Fascinate Android Development] wessiide:
One quick question is there something I need to do to get my settings in voltage control to stick? After applying changes I leave app come back to it a few hours later and everything is reset. Sorry if this has been addressed I try to keep up with the forum best I can but this thread is a happening spot it seems!
[Fascinate Android Development] fstbusa:
If you restart your phone the settings will default unless you've set them to load at boot.
[Fascinate Android Development] ssewk2x:
What he is saying is that the reason you have to hit the button however many times is that the sensor that would automatically light the screen is not working. Once we get the fix for that proximity sensor merged into the code, the screen will wake up as soon as you move the phone away from your face, just like you'd expect.

Meanwhile, it's not a show-stopping problem, so please, everyone just shut the f*ck up and be patient.
[Fascinate Android Development] PhoenixPath:
Teezle:

The blasting will happen no matter what anyone does. This is true. The "solution" provided was merely to make it so that once you brought the phone to your ear...you could hear the caller. This works. It has been tested by many users on multiple roms.

What you describe in your "also note" is the sensor issue I made note of in my first response to you that you had originally called the "sleep of death or whatever". It has been fixed by jt with the mez source-drop. The devs for this kernel are working on getting it into this one.

If you need more info, PM me. This has gone from Development to support/complaining way too long now.

Edit: Beaten by ssewk2x by a matter of seconds. Soz...
[Fascinate Android Development] rmtobler:
Using Smartbench 2010 I tried out a number of different scheduler/govenor settings at 1ghz on MIUI 7.22 w/ v12 glitch kernel. Ran each setting 5 times and the averages came out to be:

deadline/ondemand = 927/2108

deadline/interactive = 953/2243

deadline/interactivex = 946/2188

deadline/smartass = 910/2209

deadline/conservative = 941/2262

Took the top 3 governors: interactive/conservative/ondemand to run with different schedulers

bfq/ondemand = 956/2257

cfq/ondemand = 941/2190

bfq/interactive = 948/2276

cfq/interactive = 955/2300

bfq/conservative = 931/2281

cfq/conservative = 956/2316

Winners:

1. CFQ/Conservative

2. CFQ/Interactive

3. BFQ/Ondemand

Difference being:

Ondemand is the default choice due to its balanced settings which offers a good compromise between battery and performance. However, it has no suspend profiles and falls a bit short on performance in smartphones.

Conservative is a slower Ondemand when it comes to ramping. For example, when you turn on the phone and start interacting with it, Ondemand will increase frequency until it reaches max at x speed. Conservative will do the same at x/2. Faster the ramping the more battery it consumes so conservative while a worse governor for performance it's also a good one for battery.

While Conservative is a slower Ondemand, Interactive is a faster one. Ramping will be slightly faster so interaction will seem more snappy with battery comsumption just increasing a tiny bit. This has been the most popular governor for the past year.

(descriptions taken from: http://xdaforums.com/showthread.php?t=1242323)
[Fascinate Android Development] PhoenixPath:
Wow. This totally opposite of how I'd have guessed they would score.

Currently using cfq/smartass (@1.3Ghz) with no jittery or lagging screens/swipes and scrolling is fluid. Have been unable to reproduce the smoothness or fluidity of this on any other combination. Battery life isn't really a concern as mine lasts a day and a half without charging (extended Naztech), so I cannot comment on it being good or bad in that regard.
[Fascinate Android Development] neh4pres:
Shut up troll!

Sent from a beautiful miui fascinate
[Fascinate Android Development] MJMcMahon:
I'll toss my own two cents in here just to add a little perspective: I've worked a lot with community development projects and have found the quickest way to lose a developer is to start *****ing at them. These folks are investing their own time in an effort to help. While there may be unresolved issues with some of the current solutions, they're better than where we were and represent some 'out of the box' thinking on the part of the developers involved.

I, for one, want to say THANK YOU to those who dedicate their personal time in an effort to make using my phone a better experience. Thanx guys. :)
[Fascinate Android Development] rmtobler:
Okay I just noticed something I have my settings at cfq/conservative, but whenever my screen turns off the governor resets to ondemand. After rebooting it returns to conservative, but resets again to ondemand once the screen is turned off. (Note: for my benchmarking results I never turned the screen off to keep everything the same)

This happening to anyone else?

Fixed. Cleaned and reset the settings in recovery.
[Fascinate Android Development] ssewk2x:
Make sure you're using the V12 beta version of this kernel. What you're experiencing is a known issue in V11 that I fixed for V12beta.
[Fascinate Android Development] akellar:
It happens to everyone that has their screen scaling set to ondemand. Go into recovery, GLITCH, and change it to what you want it to be when the screen is off. Or turn off scaling all together.
[Fascinate Android Development] sixstringsg:
Thank you for this.
[Fascinate Android Development] MJMcMahon:
my pleasure sixstringsg - a lot of people forget that you guys do it for the joy of coding and helping others. A gentle reminder from time to time is always a good thing. :)
[Fascinate Android Development] sageDieu:
guys like you guys need to like fix everything that isnt perfect about my phone like right now and if you don't you like totally suck. waaah.

Sent from my MIUI SCH-i500
[Fascinate Android Development] sephirothhoo:
Report bugs but be nice with the developers. If you don't like it, move on to other alternatives. Remember, they work for free! Why don't you try to contact samsung or verizon see if they care.
[Fascinate Android Development] calebv2:
+1 I love it this made me laugh.
[Fascinate Android Development] tripacer99:
[/sarcasm]
[Fascinate Android Development] neh4pres:
Teezle.. Please delete your xda account right after you flash a verizon stock rom.. Thanks

Sent from a beautiful miui fascinate
[Fascinate Android Development] neh4pres:
Sixstring, I have never been able to run 1700 for more than a few seconds.. But I just found that if I set every thing above 1000 to -25 (as I do anyway when overclocking above 1ghz). Then set 1500 as max, then also set 1500 as min.. Locking myself into a high overclock.. I then set 1700 as max and min.. locking my phone into the 1700 state and it ran flawlessly.. I smashed records on every benchmark.. I even hold the record for the i500 on antutu now. I ran my phone like this for almost a hour with no issues.. Then I used pimp my cpu to set 100mhz to minimum and within a few seconds it froze... After this test I'm positive most fascinates will run 1700 without much issue.. I think Its just stepping between states that freezes the phone. :)

Sent from a beautiful miui fascinate
[Fascinate Android Development] sixstringsg:
I highly doubt most fascinates will run that high. In our testing of 1700, only a few phones could run 1700. A couple locked to that frequency as you describe, and three including mine and Tk-Glitch's that can run it with scaling. 1600 is a stretch for most phones, you're just lucky you could taste 1700.
[Fascinate Android Development] rmtobler:
Any chance of adding some new governors and schedulers to the kernel?

Governors: Smartass2, MinMax, SavagedZen

I/O schedulers: VR, Simple.
[Fascinate Android Development] chrisexv6:
Thats when you know the kernel rocks, it works so well its that hard to break.
[Fascinate Android Development] ssewk2x:
I was going to say, I specifically didn't touch any of the OC/UV code when I did this latest merge, so it should be as Glitch left it.

With that said, I think that he did play with it a little bit for beta 12, so I'm not overly shocked that people are seeing improvements.

Hell, maybe I'll even try backing some voltages down and see what happens :)
[Fascinate Android Development] LifeInTheGrey:
Forgive the intrusion, I did a little reading back and noticed no one was really having this problem (without dropping voltages WAY down of course). Also forgive the naivete, as I'm an Evo user but my boss has a Fascinate.

My boss is running OMGB, which normally runs the CM kernel so I figured that it would run Glitch okay. But when I flashed it, he was getting a LOT of random freezes that required battery pulls. I didn't mess with any of the voltage settings, and he wasn't even running PMCPU or anything. I also followed the flash instructions in the OP to a T (I know better than not to read).

The main reason I installed it was for the Volume fix (he *****ed endlessly about the volume being so low). If someone can help me out with either proper techniques to flashing v12 beyond the kernel cleaner script or applying the volume fix to v11, I would greatly appreciate it.
[Fascinate Android Development] scarmon25:
The problem man be that the cleaner script is being used. Don't use it. It breaks things from what we've been told. If you're not using it then forgive my misunderstanding of your post
[Fascinate Android Development] LifeInTheGrey:
I did use it ... dam. If this were my own phone, I'd have no problem just up and reflashing, but its my bosses. I'll see if there are other responses or ideas, so that I can come to him with multiple options.
[Fascinate Android Development] scarmon25:
I know the feeling. I did the exact same thing but with my phone. The only thing that fixed it for me was to reflash my cm7 build. Others may have other options though.
[Fascinate Android Development] GizmoDroid:
Slightly confused right now. Running a previous Glitch beta, I was able to run at 1.7ghz with not very much trouble.

Now, I am able to run 1.6ghz with -200 UV, yet I can't seem to get it to run at 1.7ghz at any voltage level without it crashing. I've tried all three leakages.

Not that big of a deal since 1.7ghz isn't obtainable for most people anyway but I just thought I'd mention it.
[Fascinate Android Development] sixstringsg:
What version did you flash? When was it downloaded?

Honestly, **** happens. As ssewk2x and I have both said, we didn't touch voltages a bit, therefore it will have been the exact same as the last beta that Tk-Glitch put out. Your phone's ability to OC and UV is dynamic, between kernels, ROM's, and age. It isn't an exact science, otherwise it would have been done at the factory. Samsung didn't OC it or change voltages any because it fluctuates, and probably something on yours just changed so that you couldn't OC as much.
[Fascinate Android Development] FJRSport:
Using Glitch v12 (9/22/11) This thing rocks!!!

Quick question.

While using Voltage Control, I have set Mhz between 200-1300 in the 'General' tab, then go to the advanced tab and begin adjusting uv settings. Voltage control will allow me to make the adjustments, save those changes as "Save Profile", I can even see those changes 10-20 minutes later when I return to Voltage Control. However, after some extended time (like nearly a day worth) I'll return to Voltage Control only to find the advanced settings all returned to 0 UV. As a note, I have yet to save as boot setting for obvious reasons.

It is not due to a reboot as my min. and max. Mhz remain the same (i.e. 200-1300) and when I do reboot, I have to manually reset the min-max Mhz.

Has anyone encountered this and is there a fix, or something I'm overlooking?
[Fascinate Android Development] LifeInTheGrey:
It is v12 beta High Leakage, downloaded 9/20. I noticed that the version is 9/22 in the OP, would this updated version have many changes to potentially rectify the problem?

Edit: I also just noticed the Call Volume script. Would this work on v11, or does this only work on v12?
[Fascinate Android Development] sixstringsg:
You don't save as profile to apply. You hit apply down at the bottom. The save as profile is useful for keeping your settings when doing something that will wipe /etc/init.d (such as flashing a nightly)

9/22 was completely redone, because 9/20 is bad. Therefore yes, you need 9/22. It is the only thing that will fix your problem.
[Fascinate Android Development] FJRSport:
sixstringsg,

agreed. That is what I do. It did not keep. I then saved as a profile hoping that would resolve the problem; all values in the advanced tab still return to zero. I noticed on page...98 of this thread someone else having a similar problem.

I'll see if I can link to it.

Post #978
[Fascinate Android Development] sixstringsg:
What ROM are you on? If it's the one in your sig, you shouldn't be having any problems like that.
[Fascinate Android Development] FJRSport:
Agreed. That's what throws me off. It's not that big of a deal, but I like to find issues and try to fix them. It's in my nature. ;-)
[Fascinate Android Development] GizmoDroid:
Si, Señor.

Actually, I remember what I originally meant to post about which had to do with the governor switching itself from ondemand to conservative by itself. This has happened twice now. Probably was just a fluke with the Voltage Control app. I'll do some investigating if it happens again.

Thanks again for the hard work!
[Fascinate Android Development] sixstringsg:
Make sure to check your screenstate scaling. It shouldn't effect your screen on settings, but you never know. Also, make sure your settings that are saved as boot settings are to ondemand, not conservative.
[Fascinate Android Development] tripacer99:
I read that sentence and thought you had obviously mistyped something. 1.6 @ -200? Wtf?

And then I tried it myself...my mind is boggled right now. How...the...?
[Fascinate Android Development] Enyo.:
Holy. I Might Try This.
[Fascinate Android Development] PhoenixPath:
Just want to re-iterate what an amazing job you've done here. My phone, which never reliably overclocked before is now running beautifully at 1500.

It didn't play well on 1600, but I haven't tried any UV yet so there's still plenty of room to play.

I'm sure I haven't thanked all of your posts yet, so here goes. :D
[Fascinate Android Development] sixstringsg:
I have to UV by -100 on both 1.6 and 1.7, so you might get there.
[Fascinate Android Development] Enyo.:
It will just lock up on me. I can only do -100 on 1.0-1.4ghz
[Fascinate Android Development] nklenchik:
Alright guys,

I'm using the old v11 kernel and want to switch to the beta v12 but I can't get past the bootloader. Anyone have any suggestions?
[Fascinate Android Development] sixstringsg:
What ROM are you on?
[Fascinate Android Development] sixstringsg:
Any graphic designers use this kernel? I'm looking for a banner to put in my/other team member's signature, and I was wondering if anyone was interested in making one for me. PM me if you are.

Edit: Nevermind. One is being made for me :)
[Fascinate Android Development] boldfilter:
Anyway to restore the stock cm galaxy s one and orange recovery?
[Fascinate Android Development] sixstringsg:
The stock galaxy s what? And why do you want orange recovery?
[Fascinate Android Development] nklenchik:
Using CM7...I dont get it :D
[Fascinate Android Development] sixstringsg:
Newest CM7?
[Fascinate Android Development] nklenchik:
Oh no...I had no idea a new one was out. Any links?
[Fascinate Android Development] sixstringsg:
New poll at the top of the thread. In a week, I'll count the votes between the threads and decide.
[Fascinate Android Development] boldfilter:
Are you taking about the MTD splash screen, that changes when you flash the glitch kernel?
[Fascinate Android Development] sixstringsg:
No, we were talking about signatures for the signature section of XDA. To answer your question now that I know what you're talking about, there isn't a way to change either of those without re-compiling.
[Fascinate Android Development] schu9120:
Thanks for the latest (9-22) Glitch magic. Its running very nice with CM7 #61. Is there a way to increase the ringtone volume in the sound script that I'm not seeing? I figured out how to fix the other in-call issues.

I work around heavy machinery all day and just can't hear an incoming call no matter what obnoxious ringer I choose.

Thanks for any help...
[Fascinate Android Development] sixstringsg:
It isn't designed to work on that. But you've given me another thing to add to my to-do list!
[Fascinate Android Development] sageDieu:
Im also a graphic designer if you guys need anything done; I'd be glad to do anything for you guys for free.

Sent from my MIUI SCH-i500
[Fascinate Android Development] sixstringsg:
I'll keep that in mind, thank you!
[Fascinate Android Development] Eris _2.1_2010:
What's a good setting for voodoo color?

Sent from my Glitched MIUI Fascinate
[Fascinate Android Development] sixstringsg:
Search "voodoo color" and you'll find the answers that have been posted.