yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] bobloblaw1:
Thanks man. For some reason I thought that you guys had disabled/increased that limit but maybe I'm thinking of the CM7 version....or maybe I'm just crazy =)

Do you think the RAM and or database IO information from Antutu has any value? Has anyone done anything similar with a reliable 2d/3d benchmark or other objective test?
[Fascinate Android Development] jbr05ki:
Can you get into your Power Amp settings? Power Amp would close every time I hit settings.

I'm using AOKP which is THS 6.1 based and Glictch V14b3

EDIT: Nevermind I just reinstalled and it werks na0.
[Fascinate Android Development] droidstyle:
Just wanted to thank team glitch again for there hard work!! Im currently running THS build 6.1 w/ Icy glitch and everything is working great!! I am now officially done with cm7 :p
[Fascinate Android Development] shelby04861:
Is there a way to get myself out of recovery if it will only boot into gitch recovery. I can flash roms and restore known good backups but it wont boot back up again. This is the second time I did this and I am not sure why it happens. I was trying to flash one of the themes for the gummy rom. At this point I am stuck in recovery until I get get to my home computer. It's my fault I guess but I am hoping for some help. maybe this will help others. thanks
[Fascinate Android Development] Nemeth27:
For those who don't have issues with music playing when the screen turns off, can you let me know what scheduler/governer/and any other settings you are using?

I can't seem to get music to keep playing correctly when the screen turns off.

Thanks!
[Fascinate Android Development] sixstringsg:
Were you using ROM manager?

Are you using screen state scaling?
[Fascinate Android Development] shelby04861:
I was not using rom manager, and I ONLY changed the regular overclock value up to 1300. It has been runningfine with zero issues. What I actually did was try to swap the framework-res out for another without flashing or adb(yeah I know, not a good way to do it but it worked on the reg roms). When I rebooted the phone it went into your glitch recovery and I thought...nobig deal. I rebooted and it hung on the boot animation and would not bootall the way up. I pulled the battery and restarted the phone but can only get to glitch recovery now nomatter what I do. I can still flash files fine and do retores but it wont boot out of recovery at all. I feel like it can be fixed easily, just not sure what I need to do. I know I did not do things the "right" way but I am trying to be as honest as I can so I can get the proper help.
[Fascinate Android Development] sixstringsg:
First: clear cache/dalvik. If that doesn't work,

Second: make a full backup, wipe data/factory reset, format /system, reflash the ROM without the kernel. See if it boots. If it does and you want to go back to Glitch at that point, do that, see if it boots. Then, either restore with titanium, or go into recovery and restore only data. Then see if it boots. Sometimes gremlins just happen.
[Fascinate Android Development] shelby04861:
stuck in blue recovery now 5.x. tried clearing the above from blue as well. i can flash your kernel and get back to glitch, just stuck in reco mode. this is weird.
[Fascinate Android Development] mkuehl06:
Gotta say thanks for this. On build 6.1 beta is working flawlessly and the stupid volume bug that plagued me on stock cm9 kernel does not exist. Thanks to all involved in the dev team and to six for a well maintained forum.
[Fascinate Android Development] sixstringsg:
I am all out of ideas.
[Fascinate Android Development] shelby04861:
It was suggested to try flashing CM7 so I am going to try that and will report back.

edit:still stuck
[Fascinate Android Development] ekowanz:
It happens to me too... for me, i think i screwed up with the nstools setting. I change the oc (forget the details) then it hang, then restart. But stuck in recov mode. Anything i do (flash,restore) but still booting up to recov mode. Only odin help me out of this probs.

So for now in nstools, i always unchecked the save boot. It helped me from screwed up like that before.

Sent from my SCH-I500
[Fascinate Android Development] k_nivesout:
If the issues with screen off and music you're talking about are skipping/glitching then I definitely know what you're talking about. The combo of THS 6.1 + glitch v14 has been the best for me as far as uninterrupted, clean music playback, I rarely every run into skipping/glitching anymore.

I'm using default settings aside from a 110% liveOC and 1320mHz max frequency. Governor is glitchOndemand, scheduler is fiops, voltages are untouched.

You can delete your voltage/OC settings in the glitch recovery menu, did you try that? Your issue sounds like what happens when you 3-finger into recovery on ICS. If you ever did that instead of selecting reboot > recovery from the power menu, you will end up in the same situation that you're describing.

Ditto! Agreed 100%. Well, except for "there", which should be "their". :p
[Fascinate Android Development] Nemeth27:
Actually, I believe when I was playing around with the glitch recovery I think I turned it on. I'll try to turn it off and see what happens. THANKS!
[Fascinate Android Development] gt43aw:
I've had a problem where even though I was using the power button to get into recovery w/ the glitch kernel on THS 6.0, it was still going into recovery mode as if I had used the 3-button salute (i.e. not the glitch recovery). And once that happened, i'd eventually get into a recovery bootloop when i tried to boot back into THS 6.0. Again, i had the glitch kernel but i could never get into glitch recovery.

Anyway, the only way i could solve this is go back to stock, flash cwm fixed for cm7 and then flash build 2, use recovery to delete all the partitions/wipe, and then flash build 6.

I could never really figure out what caused the problem. But it's all good now.
[Fascinate Android Development] tonu42:
http://rootzwiki.com/topic/15496-how-to-get-out-of-recovery-boot-loop-on-ics-fascinate/

Fixes my ICS recovery bootloop problems. Saves data, but I didnt realize that till after.
[Fascinate Android Development] neh4pres:
I don't understand it either. There are no options on ths. It's plain vanilla. And with all being equal, that would be a valid choice. But there not anymore. With the extra ram the phone is all around more responsive, and you don't need to use the aokp modifications If the plain old ics is what your looking for.
[Fascinate Android Development] Stephen.k.spear:
yeah the ths builds literally don't have anything the kangs don't. But the kangs got glitchy goodness.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] Aali1011:
Honestly i have no reasons what so ever and will try it infact. While following the THS thread a couple people have come and gone complaining about other ICS builds for the phone in comparison. Obviously results will vary from user to user. That was a slight sway away for me. Other then that for what THS was providing me I was happy. But i will give it a shot come tomorrow and see how it goes.
[Fascinate Android Development] ssewk2x:
Yeah, what he said ;)
[Fascinate Android Development] droidstyle:
I would take in great consideration whos information your reading...AOKP is the best rom ever for our device. THS was a great stepping stone in the begining, but AOKP is much improved. Think of THS as the old vanilla gingerbread(much improved of course) and AOKP is the new and improved cm7(which is now cm9)
[Fascinate Android Development] shag_on_e:
So, with all the new hype and as far as it's come, I'm wondering if it would be possible to incorporate Team Win's recovery for us as opposed to the CW based one. I'm sure it would cause much work, just curious if it's possible.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
If you'd like to point me to where I can find this recovery and source code for it, I can check it out at some point.

---------- Post added at 11:30 AM ---------- Previous post was at 11:25 AM ----------

Also, I wanted to report that I just observed some .. interesting .. behavior related to Fast Charge. I'm posting it in the kernel thread since fast charge is a feature of the kernel.

Anyway, I was just fiddling with my phone, and I needed to ADB for something. So I shut off fast charge and plugged in, and everything was great. When I was done, I used NSTools to toggle fast charge off, exited NStools, waited a few seconds, and plugged my USB in. It says "USB connected," wtf?? Like fast charge wasn't on.

So, I adb into my phone to check on a few things. I look at the sysfs interface, and it says that fast charge is enabled, yet I'm looking at it through ADB, which should be disabled if fast charge was really on. So what the heck? I poke around at a couple other things I wanted to check in the meantime, like callboost, init.d permissions, etc., when all the sudden, my ADB shell exits, the device disconnects from my computer, and it starts fast charging. This was at least 30 sec to a minute AFTER I had toggled fast charge back on.

So I guess the moral of the story is, "when toggling fast-charge back on, patience is a virtue, but it will eventually work."
[Fascinate Android Development] sixstringsg:
Team Win isn't available for the Galaxy S as far as I know.
[Fascinate Android Development] sarkozy:
While it's nice for sure, you're talking about a proverbial re-inventing of the wheel (I'm exaggerating slightly, but it's a PITA) to get that to work

properly

on the phone, especially considering the differences between AOSP and non-AOSP stuff.
[Fascinate Android Development] bobloblaw1:
I would deduce that he meant to change the setting to 0 where the problem exists and not where it doesn't. That would be 0 for the SPK boost value and leave the others the same... but he wasn't 100% clear.
[Fascinate Android Development] shag_on_e:
Exactly. Once you've enabled it you can also change the values in the init.d script, either way only lower the speaker related values. The echo is almost completely gone like this, and makes for a useable speaker phone once again. I love this kernel.

~~~~There is no spoon~~~~
[Fascinate Android Development] gt43aw:
Ok, i've set In-call bost for SPK to 0 from 2 and MIC gain for SPK from 18 to 10. i'm on a plane right now, but i gotta say, i'm pretty excited to try this out....
[Fascinate Android Development] ssewk2x:
Let me know how that works for you - and are you on a Fascinate or some other device?
[Fascinate Android Development] gt43aw:
I'm on the fascinate. However, i won't be able to test it out until late tonight. But as soon as I do, i'll make sure to post my thoughts.

I'll try it with and without TV on to give some background noise as well.
[Fascinate Android Development] ssewk2x:
Sounds good. Have a safe flight :)
[Fascinate Android Development] Tkun:
I find AOKP (even the latest one, build 31) to be annoyingly laggy on my device (especially noticeable when opening apps), whether I'm running glitch or not. THS's builds on the other hand are usually smooth, build 8 even more so.

I'm not hating on AOKP, because I love all the features that it has over CM9, but THS's builds are generally more usable for me.
[Fascinate Android Development] sendan:
I don't know about that...I actually mistook my phone for a giant stick of butter the other day. But really, I compared with my friends gnexus on the same ROM and it was 100% the same until we started comparing bigger apps like MC3.

You may want to look into re-flashing or something. :(
[Fascinate Android Development] Tkun:
Hmm, now that's interesting to read. I'll odin to stock and flash build 32 whenever it's released, and see if my outcome is any different.
[Fascinate Android Development] neh4pres:
Mane sure you download steves build, not from aokp site
[Fascinate Android Development] Stephen.k.spear:
Yeah I think its a fair bet that the glitchy versions of all these roms are going to be significantly better. The ROM Source devs are hard at work with new framework stuffs but we are constantly working on the device stuff and we can add it to ours as it comes pushing to theirs is getting more and more difficult... lol
[Fascinate Android Development] Deliquified:
See if using supercharger scripts make your device smoother too
[Fascinate Android Development] sarkozy:
These phones are all over the place it seems. Steve's builds with the added free ram run like dog poop on my phone, no matter my nstools settings. Freezes, video problems, etc. Yet I know plenty of others that run smooth as silk with the same settings.

On the flip side, I can run the AOKP builds from the buildbot with glitch b6, and it's perfect with a 200-1200 clock and Conservative governor.
[Fascinate Android Development] sageDieu:
my phone runs better than a stock galaxy nexus, by far. the nexus with axiom and leankernel can give it a run for its money but this phone is still smoother than the nexus until you open up a 3d game or something.
[Fascinate Android Development] gt43aw:
hey ssewk2x,

so i tried out the speakerphone with in call boost at 0 and mic gain at 10 (both for spk, i left everything else at the default). I can confirm that speakerphone is very usable (no echo and the other end heard me load and clear). At that setting though, it doesn't work in noisy places (like traveling down the highway) because the speaker is way too soft even at full blast. But i just had a 15 minute conversation with my girlfriend from my hotel room on speakerphone and she didn't notice. I did have to talk a little louder than normal (but not much, it was the typical speakerphone voice i always have)

Regardless, it seems this callboost thing can make your speakerphone useful in a good number of situations. I haven't tried out any other settings. Maybe there is a sweet spot that will make it usable in the car too.

Thanks all for the tips. I'll be interested in hearing other peoples experiences with other settings.
[Fascinate Android Development] Deliquified:
Try using smooth ass governor and fiops and at 200/1100 with 110 OC and see how it runs for you.also, in developer options under settings pick Max 4 background processes and lmk if that helps.
[Fascinate Android Development] Stephen.k.spear:
Sounds good I think we are going to implment those settings into the source so you have it all set on the first boot and you shouldn't have to touch it. I want to test it a bit more but I think you can expect it in the next glitchy AOKP.
[Fascinate Android Development] dablitzkrieg:
This blows. I have two different fascinates and my phone runs like crap with this kernel unless I Odin everytime a new release is put out. Why is that?
[Fascinate Android Development] bobloblaw1:
You are using 3 finger to get into recovery? You are using nandroids and they are borking your partitions? Your /datadata is full? You aren't wiping caches and/or data between flashes? You don't use a cache cleaner like Cache cleaner NG? Your downloads or flashes are bad? Your phone is an attention whore and loves that Heimdall spa treatment? Your phone hates you?

I dunno man.... All I can say is most people don't have a problem wiping caches and flashing the next build. Odds are if its just you and it's on 2 phones it is something you are doing. =(
[Fascinate Android Development] dablitzkrieg:
I wipe all three. Never use nandroid backups. Always wipe data. How do I clear my datadata? I know it it's me, just weird because I always wipe and never 3 finger recovery
[Fascinate Android Development] droidstyle:
data wipe clears datadata, but if you restore apps with data then it fills back up. try moving some apps to your sd card. i have 30 apps installed with no datadata issues!
[Fascinate Android Development] bobloblaw1:
I have also moved all non-essential (don't use it daily, it isn't a widget on my home screen) to the sd card. I also have cache cleaner ng set to run nightly. I have no data data issues.
[Fascinate Android Development] Stephen.k.spear:
I just finished up a script with Efpophis that fixes the datadata issues. It well come with the glitched up bulls from now on and ask you have to do is run it in terminal

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] nmalready:
With headphones (without a mic) plugged in, the person on the other end of a call can't hear me. I tried turning HP Mic gain up all the way. I'm on aokp31 with glitch. Is this a known problem or is it just me? Thank you
[Fascinate Android Development] ice.candi:
First off id like to say sorry if im posting this in the wrong place...

Im looking into learning how to create a custom kernel using mostly aspects from glitch for cm7 but porting the gb usb host drivers into it (my main goal) and possibly if that goes well the updated sound improvements

Im extremely new to this and wanted to make sure i was allowed to do this with your kernel. And being that ive never developed anything for the phone before does anyone know of any reliable reference sources that could point me in a direction of how to get going and what programs i will need?

Sorry again if this is the completely wrong place for this but i know no one maintains the glitch v13.1 thread anymore...
[Fascinate Android Development] sixstringsg:
Who said noone maintains that thread anymore? And yes you are allowed to do that, it is an open source project, we can't stop you from doing anything. You will need all the packages required for compiling Android. There is not a specific program we use to develop, just github and a text editor.
[Fascinate Android Development] Stephen.k.spear:
Diffmerge can be helpful too, especially if your trying to find out why one file works and the other doesn't .
[Fascinate Android Development] speedingcheetah:
As far as i know, no headset works on the fascinate running custom roms...only stock roms recognize the mic on a headset.

When i have my headphone plugged in, it still routes the audio of the call to them, but it uses the phones built-in mic on the bottom of the phone...so if the phone is in your pocket, the other person won't hear you.

Not sure if this is the issue your are having...
[Fascinate Android Development] sixstringsg:
Is there an Ubuntu version of Diffmerge? I only have the OSX version.
[Fascinate Android Development] sendan:
It looks like it they have it for all three platforms. http://www.sourcegear.com/diffmerge/downloads.php
[Fascinate Android Development] Stephen.k.spear:
Yep I've used it on all three.
[Fascinate Android Development] freshveggies:
I use the inline Mic that is with my headset. It has worked with many custom ROMs.

When I use headphones without an inline Mic then it works exactly as you've described.
[Fascinate Android Development] ice.candi:
Sorry i just figured i posted on it a while ago about the drivers and there havent been any post since so i figured that everyones pretty much moved on to ics now

Thanks though i knew the roms were open source i just wasnt sure about kernels. Didn't want to step on anyones toes (if i even get it working) ill let you know if i do though in case anyone may want to use it, this is just a personal project for me trying to get usb host on cm7 and still have the best kernel ive found :D
[Fascinate Android Development] xsc0rchx:
I am not sure if other people are having this issue or not. But I am running the Glitch kernel that is on the Nightly CM9 Kang releases and my phone locks in a loop whenever I attempt to set the sleep governor. I am attempting to use smoothass if that makes a difference.
[Fascinate Android Development] droidstyle:
I bet your oc is maxed at 1500mhz...the latest nstools update was causing this.
[Fascinate Android Development] shag_on_e:
Agreed with droidstyle, NSTools can act crazy especially if you change your settings a few times without flashing the NSTools reset zip. I make sure to set OC high to 1400, OC low to 100, max clock 1400, low leakage int voltage, -50 arm voltage, and 102% LiveOC and mine is insane fast and stable. I think it's important to find the right int voltage for your phone like the leakage versions did, plus be gentle with the LiveOC.

~~~~There is no spoon~~~~
[Fascinate Android Development] xsc0rchx:
My max OC is set to 1300 with no live overclocking. I use Glitchassv2 as my governor and fiops as my scheduler. I have gotten locks at the kernel boot screen or loops at the kernel boot screen.

I am setting my sleep governor from recovery.

I can upgrade nstools to see if that fixes the issue, but I am not sure how this would correct the issue because everything breaks from rebooting out of recovery. This would be before nstools has the ability to load and enforce settings.
[Fascinate Android Development] sarkozy:
Honestly after messing around with LiveOC for months now, it seems at least for my phone that keeping things between 200-1200MHz with no OC and Conservative governor yields an identical user experience I'd get with hefty use of LiveOC, and at much lesser battery consumption.
[Fascinate Android Development] shag_on_e:
Flash the reset NSTools.zip. I have a feeling it'll help.

~~~~There is no spoon~~~~
[Fascinate Android Development] thisguy23:
This has been asked before but benchmarks say LiveOC gives better overall performance vs straight 1500 clock that gives higher numbers overall. Idk which is better for everyday use and battery.

Faster clock more power in short bursts.

Vs.

Lower clock less power in longer bursts.
[Fascinate Android Development] sendan:
Just find a balance to get the best of both perhaps? I found my sweet spot at min: 100 MHz max: 1000 MHz (1100 MHz with LiveOC) LiveOC: 10% and everything else stock.
[Fascinate Android Development] bobloblaw1:
Yeah I do similar on the conservative governor but with a 20% liveoc giving me a 100-1200 range. 800-1200mhz have the live oc applied.
[Fascinate Android Development] xsc0rchx:
I have v1.16 of NStools installed and I have tried the rest NSTools.zip app with no change.
[Fascinate Android Development] shag_on_e:
Do the default settings work for you? Does this only happen when you change the governor/scheduler? I stick with the defaults with that because those are the ones the devs have tweaked for best results, so I haven't experienced that because I just leave them default.

~~~~There is no spoon~~~~
[Fascinate Android Development] Deliquified:
Wipe dalvik/cache, Flash the reset nstools zip, mount everything except sdcard in recovery, run fix permissions in advanced tab in recovery, reboot. Under settings > rom control > performance, keep it at 1000 MHz. Afterward, open nstools and try 200/1000 with 110% OC. I have a feeling your phone doesn't like over clock over 1100 MHz. Personally, mine hangs frequently at 1200mhz or higher.
[Fascinate Android Development] neh4pres:
You may have to adjust voltages of your phone don't oc to at least 1200. Samsung released source with a 1200 mhz step in it.
[Fascinate Android Development] xsc0rchx:
My understanding is that OC settings would not actually take effect until the Android OS boots, my phone is hanging during the kernel initialization. The settings in NSTools are executed as part of init script which does not load until after the kernel is executed. My understanding is that the kernel initialization process is performed during the Glitch (GB Bootloader) Image. The CM9/Glitch boot logo is executed as the init scripts are executed and the OS loads.

If I flash the Glitch kernel for this thread I can modify my Sleep Governor but the Kernel in the Kang CM9 Nightlys does not appear to work. I am not sure how to capture logs as this is getting hung during the boot process and I don;t believe I will be able to get adb to connect.
[Fascinate Android Development] Deliquified:
Its possible that screen state scaling is causing your phone to hang.
[Fascinate Android Development] xsc0rchx:
That is the issue I was attempting to report. I believe there may be an issue with the custom kernel that is build into the Kang CM9 Nightly's, didn't know if this was the correct place to mention it or not.