yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ssewk2x:
Hrm. I don't think so. This should have all the files you need to fix your sensors .. but I guess it's possible I goofed. You shouldn't have to flash any other sensor fix after you flash this.

Now, are you talking about your google maps compass? Cuz that's a different issue.
[Fascinate Android Development] neozen21:
I'm using Smart Compass. What's that app that you used to test? I'll try that one as well...

Everything else seems unchanged so far..
[Fascinate Android Development] ssewk2x:
I used elixir and gps status.

Edit: i just grabbed smart compass and tried it out on my latest test kernel. It works perfectly. Also, nice app! I think I'll keep it.
[Fascinate Android Development] neozen21:
OK. I just installed Elixir2 (it replaced Elixir), and the going into the sensors, the accelerometer seems OK, the Mgantetic field sensor gives values, but I'm not sure what they mean..

Using Smart compass, when I leave the phone on my desk (level surface), and rotate it.. the North changes every time I turn my phone. It's not pointing to the North...

Not sure what could be the difference between your phone and mine..

Just a straight THS 7.1 with no sensor fix and I flashed your latest kernel, wiping cache and Dalvik...

EDIT: I just borrowed a coworker's Moto Droid X, and using GPS status and other compass app, his compass behaves the same as mine!!

Maybe it's the environment, there are TONS of computers here at work and I have 2 computers and 3 monitors in my cube. Since his phone is behaving the same as mine, I guess I can say the compass works fine :P

Anything else I can do to help?

Thaks and keep it up!
[Fascinate Android Development] ssewk2x:
Yeah, ambient magnetic fields will even screw up an analog compass, lol. Try it outside maybe?

Mine goes a little nuts in my office, too.
[Fascinate Android Development] neozen21:
I'll try it when I get off work in a little bit.

Thanks for all your great work!
[Fascinate Android Development] newbie4ever:
V14 B6 seems to be an awesome kernel but the 1 thing I noticed is the accelerometer is going wild
[Fascinate Android Development] pntballer505:
Normally I wouldn't ask this without reading around first,

but I don't seem to see too much or know

much about active schedulers.

Which one is recommended, do they have

an effect on battery life?
[Fascinate Android Development] speedingcheetah:
Using NSTools to adjust the IO Scheduler: deadline and Fiops are the best.

I find Fiops to have much better battery life, but some people have reported issues while using it, such as lockups, SOD, etc...

I an not sure if those issues have been fixed, but I haven't had any issues with the latest stuff.

Each device reacts differently. Your millage will vary.
[Fascinate Android Development] yonith:
wrong thread
[Fascinate Android Development] mrjake1970:
until recently deadline was my rock..since i moved to aokp, esp with later b5 and new b6's deadline has been freezing me and causing sod's. i have been using fiops for last 2 weeks.

i used s sweet spot posted about 10 days ago by someone in this thread (fiops, smoothass, 200 min with 1000 max, live oc of 110) and im getting insane battery life and very snappy response.

every unit is different..keep playing until u find a good mix

rock on

AOKP M4 :: Glitch V14B6 fastcharge Kernel :: EH03 Radio
[Fascinate Android Development] 00ffej:
For some reason when I try to use these settings NSTools reverts every time I reboot

Edit:Ugh, bricked. Looks like a long night for me :(
[Fascinate Android Development] 00ffej:
I was an idiot and forgot the warnings about 3 finger recovery.:D
[Fascinate Android Development] bobloblaw1:
Another nice place to play is on the 800mhz step for max frequency with a 120-122% live oc. I nudge the arm volts down one step on 800.

That should give you a nice experience since the gpu takes care of rendering in ics.
[Fascinate Android Development] andymetoo28:
Cool I'm going to try these settings. Been messing around with different ones the past few days. This pairs with the new 3rd party batts I got will make me uNsToPpAbLe!1
[Fascinate Android Development] kallell:
Anyone have the link to the post? I've been searching page by page, but not exactly sure which you are referring.
[Fascinate Android Development] Deliquified:
It may have been my post.. I posted those settings about two weeks ago.. 200 min, 1100 max, 110% OC, Fiops & Smoothass. Stable as can be, Super quick.
[Fascinate Android Development] kallell:
Any UVing?

Also, anyone use power saver functionality on aokp?
[Fascinate Android Development] mrjake1970:
ive tried undervolting, it really didn't make a difference in battery life. i would get random reboots few times a week..

i havent tried power saver...i got some good aftermarket batteries suggested by sage (can be found in accessories section) and im getting just about 24 hours consistently off those.
[Fascinate Android Development] Deliquified:
No UV.. I've done extensive tests and found the potential battery savings isn't worth the instability UV introduces.. I use Supercharger scripts but that's it.
[Fascinate Android Development] droidstyle:
anybody tried this kernel with the latest AOKP build 29?
[Fascinate Android Development] dave3588:
Yeah runs great!
[Fascinate Android Development] shag_on_e:
Yeah man, she's a beast for sure. Running great.

~~~~There is no spoon~~~~
[Fascinate Android Development] bobloblaw1:
Uv is basically only useful for stability. Any battery savings is pretty much negligible at best. Better battery savings can be achieved with a black wallpaper and black apps tbh
[Fascinate Android Development] kallell:
You feel like that script even makes a difference anymore? I used it in the past, but havn't since i've been on ICS.
[Fascinate Android Development] madmike0408:
Using stevespears Cm9 nightly ports for fascinate I lose 3G connectivity. Which is kind of weird, b5 for 6.1 worked perfectly for me.

Edit, using the THS 6.5 data fix, for mesmerize, I was able to get my data back functional.
[Fascinate Android Development] Deliquified:
It feels a bit smoother to me. You have to replace the service.jar file to really see a difference in ICS.. Refer to supercharger thread for reference.. I also use the 3G script and kernel script. Be sure not to do i/o tweaks cause it'll bootloop
[Fascinate Android Development] droidstyle:
nandroids appear to be working on 3/27 glitch b6
[Fascinate Android Development] JoeDat:
Sorry, can you clarify? Nandroid backups have always appeared to work (ie, no obvious errors), but it's the restore that bootloops.
[Fascinate Android Development] droidstyle:
I meant nandroid restore works now on the latest, atleast for me.
[Fascinate Android Development] djk21108:
I'm having a real difficult time with NSTools.

I'm on a phone that originally what would be considered "High Leakage"

I can't get any voltage settings that allow my phone to run smoothly. I get a lot of freezes when I wake up my phone from a lock. A lot of freezes during intensive applications, and a lot of random restarts.

Anyone have a very stable set of NSTool settings I can copy? Or maybe someone could help teach me which settings lean towards stability, so I know what to play around with? Thanks.
[Fascinate Android Development] shag_on_e:
HI

I'll post a copy of mine in a minute for you, but a couple things that help me is whenever I switch settings on NSTools I go into recovery and flash the reset settings .zip. I've noticed settings that normally are stable aren't after switching settings a couple times. Plus I don't suggest pushing LiveOC much, unless you've found the perfect voltage settings.

https://www.box.com/shared/c39e80628eb2dbea9369

If you want to try my settings drop this in /data/data/mobi.cyann.nstools/settings then open the app and load settings. Hope it helps...

~~~~There is no spoon~~~~
[Fascinate Android Development] Deliquified:
Going back a whopping 15 posts would of gave you an answer.

200 min, 1100 max, 110% OC, Fiops & Smoothass. Stable as can be, Super quick. Don't touch voltages.
[Fascinate Android Development] djk21108:
Thank you very much.

Tried those settings and it seems to be not working too well.

My screen will turn off and the phone will vibrate around a little bit and the soft key lights will still flash on.

A lot of times after that my launcher says it isn't responding. Any ideas?
[Fascinate Android Development] mwebs13:
Try setting the OC down to 108% or 105% and see how it performs. usually it is a trial and error.
[Fascinate Android Development] Deliquified:
Make sure screen state scaling is turned off under the Glitch menu in recovery as well. It can cause instability.
[Fascinate Android Development] djk21108:
Thank you. Will do!
[Fascinate Android Development] knoxjon:
I have started getting weird interference with audio out after the last glitch build or two when I try to charge while playing music. Does anybody know if this is a sign that my mez is just getting older or if this could be related to the kernel? It started doing it all of the sudden, and I wondered if it could be too much amplification in the sound modifications, etc.

How do we enable the fast charging? I see there's an app, but I can't figure out if that's the only way.
[Fascinate Android Development] shag_on_e:
I made a script to turn it on going by the fast charge thread, then made a widget for it using script manager. This should let you change it on the fly, I'm sure that's the same thing his widget does anyway...

~~~~There is no spoon~~~~
[Fascinate Android Development] shelby04861:
One way is do do the above post method. some of the roms have the feature built in. If you happen to be on AOKP 29 for instance, go to rom control, then performance settings and scroll down to where it says fast charge. Check that and then reboot the phone. I do not know if the phone needs to be rebooted for the script to work. This is just one way that is already present in some roms. Yet another way(if you are into the free options) is to download his app that he made. It has other features as well but it does also contain a fast charge enable check box that does work without having to reboot the phone. This is the app that I use and it does work well(better than resetting phone).

https://play.google.com/store/apps/details?id=com.incredicontrol
[Fascinate Android Development] .Ejekt:
I've found very stable settings for my phone but I've been running into a small issue upon reboot. Whenever I open NSTools after my phone has been turned off or restarted my min and max values are both at 1100 (110% OC). I have my settings saved with a 200 min. Anyone else run into this issue/know how to fix it?
[Fascinate Android Development] jcurley:
That is a Kernel related issues that are rare. I had this happen back with Touchwiz superclean a while back. Sometimes I get the feedback, sometimes I don't. It has nothing to do with too much amplification. Even if you turn down voodoo sound, it still gives you feedback.

I did not have it with the stock AOKP Rom, but I do get it with glitch. I am not sure if everyone does, this is just my experience.
[Fascinate Android Development] Keithn:
Has anyone tried using usb host? I have a cable and a powered 2.0 usb hub. I see the hub and host mode with usb host controller but no drives or devices appear for me
[Fascinate Android Development] shag_on_e:
Same here man. I literally just got my adapter 5 minutes ago and can't find any drives.

~~~~There is no spoon~~~~
[Fascinate Android Development] dssheeley1:
Same issue here...
[Fascinate Android Development] k_nivesout:
There's a "save on boot" checkbox in NSTools settings.
[Fascinate Android Development] .Ejekt:
...I'm well aware. The problem is that my voltages are set correctly and the box is checked, but upon reboot the min gets bumped up to 1100.
[Fascinate Android Development] kallell:
Is "fast charge" enabled?
[Fascinate Android Development] mrjake1970:
just noticed this is happening to me as well. i posted about a week ago that i was getting wakelocks and burning battery like hell. i change the setting to drop the min to 200, check the boot box. Doesn't matter, defaults back to 1100 on reboot.
[Fascinate Android Development] dssheeley1:
+1
[Fascinate Android Development] shag_on_e:
Nope, fast charge is off.

~~~~There is no spoon~~~~
[Fascinate Android Development] kuronosan:
That was happening to me too, until I wiped application data for NSTools.

Sent in an Ice Cream Sandwich from my SCH-I500.
[Fascinate Android Development] Deliquified:
make sure you got the correct drivers.. unless I'm mistaken, you need nexus s drivers for normal use and galaxy nexus for recovery adb.
[Fascinate Android Development] k_nivesout:
That's strange, I've never run into that issue before. Sorry, I don't remember seeing it specified if the save on boot box was checked, I remember it defaulting to that before and thought it might be worth a shot.
[Fascinate Android Development] shag_on_e:
I'm talking about USB host actually. But upon some searching, I may not be set up right yet. I'm gonna dig a little deeper.

~~~~There is no spoon~~~~
[Fascinate Android Development] Keithn:
There is a topic on it if you look into it. the phone cannot power the usb, you need a powered hub or something, and use an app like usb host controller to manage settings.
[Fascinate Android Development] knoxjon:
FYI - NSTools just updated and does this now, thank goodness. I don't like having so many apps do similar functionality like that. Anyway, playing with it now; the update adds selective live oc, which seems to have set my minimum at 800.
[Fascinate Android Development] droidstyle:
boot into recovery and wipe voltage settings.
[Fascinate Android Development] shelby04861:
Good to know. Going to get the newest version now.
[Fascinate Android Development] sarkozy:
It's actually a bug when using LiveOC. I haven't seen any fix yet. Not sure if it's NSTools or LiveOC.

Mine would do it every single reboot (phone gets rebooted a couple of times a day out of habit) with the LiveOC at 110%. Any other percentage seemed to not be affected though.
[Fascinate Android Development] knoxjon:
Have you figured out any way to get it to go away? odin back to stock and reinstall, maybe?

It's maddening because I use my phone all of the time for spotify, and I don't like having to choose between running the battery down vs having that horrible feedback!
[Fascinate Android Development] bobloblaw1:
READ THIS IF YOU ARE OVERCLOCKING WITH NSTOOLS

If you upgrade to the newest version, "Set on Boot" will be rechecked by default. Un-check this box until you have settings that you know are stable or you will end up in a boot loop and potentially corrupt your database. If you are already in a bootloop grab the CWM flashable "reset_nstools_20120405.zip" from the NSTools thread.

I hope this saves someone some annoyance.
[Fascinate Android Development] 123SIT:
+1 on this. Was about to come post this myself. Great info sir.
[Fascinate Android Development] ssewk2x:
So, did everyone notice that the update for NStools has support for toggling the fast-charge option on-the-fly? It's the very first item on the Tweak page. I have been messing with it and it appears you have to let it sit and cook for a while after toggling in order for it to take effect.

Still, I guess we couldn't have timed that better if we'd tried, lol.
[Fascinate Android Development] bobloblaw1:
Just keep in mind the fast charge setting in NStools won't stick on reboot as per the dev. Still damn useful to have.
[Fascinate Android Development] ssewk2x:
Yup. What this lets me do is leave it on by default (using ROM control), and then have the ability to shut it off temporarily without having to reboot if I suddenly decide I want to ADB into my phone. :)
[Fascinate Android Development] shelby04861:
I was wondering what would happen. I was not sure if there would be a conflict or not between the two.
[Fascinate Android Development] pntballer505:
So this feature just allows for a 'fast charge' when connected to a

computer, correct?
[Fascinate Android Development] shelby04861:
Not just a computer. Check the other thread here. It will give you a better description than I could and it all makes sense...I can't. You can miss it, it is titled fast charge in the fascinate dev section
[Fascinate Android Development] dragon1357:
is it OK to flash this on fascinate aokp milestone 4?
[Fascinate Android Development] sixstringsg:
Yes.
[Fascinate Android Development] Tone_Capone:
For some reason I do think have this option. Does anyone know why?
[Fascinate Android Development] sageDieu:
did you update?
[Fascinate Android Development] jcurley:
I do the same with Pandora and Jango. If you play with your power plug, you can Jimmy it to stop. it is strange, but only happens every now and then for me.

Milestone

icy
[Fascinate Android Development] .Ejekt:
So how does this OC Target stuff work? Maybe I'm overlooking something but I don't see the point. Also, since the last NSTools update CPUSpy shows only two active voltages other than derp sleep.
[Fascinate Android Development] sixstringsg:
Minimum OC target: below this, LiveOC won't be applied. Maximum, anything above this won't LiveOC.
[Fascinate Android Development] Tone_Capone:
Yes I did. Does this work correctly with beta 6?
[Fascinate Android Development] sageDieu:
go to the far right page of nstools and hit the xda link at the bottom, download 1.16
[Fascinate Android Development] Tone_Capone:
I did that. Still no dice.
[Fascinate Android Development] pntballer505:
I've noticed my phone's battery efficiency, when the screen

is off and doing nothing while I'm sleeping, seems to be way

worse than in the past. Even when it's on AP mode.

Does this have to do with the whole Deep Idle not working?
[Fascinate Android Development] k_nivesout:
Deep idle and deep sleep are two different things, so issues with deep idle wouldn't affect anything while the screen is off and the phone's doing nothing (when it should be in deep sleep). If you look at your time in states in CPU spy, are you getting a good amount of time in deep sleep? You can also use "better battery stats" to check for wakelocks.
[Fascinate Android Development] bobloblaw1:
I've noticed that the battery stats are funky if you don't cycle the battery and few times. That is the case with every rom though. Give it some time to calibrated before drawing conclusions.
[Fascinate Android Development] pntballer505:
Thank you. From what I've noticed in CPU spy, Deep sleep is a significant portion of the percentages. Which is great, i believe. I'll start looking into wake locks. Not really sure how to use Better Battery Stats. What do you look for?
[Fascinate Android Development] k_nivesout:
Under "processes" in better battery stats, just look for anything that's keeping the device awake for extended periods of time. If the times given are all pretty low (seconds), then you're probably fine. I'm not sure what the graph with the red and blue bars mean, maybe someone else could chime in. Also, this is just my interpretation of the data given in the app, I could be completely off base.

If you checked with CPU spy and you're getting a lot of time in deep sleep, then that's definitely what you should be seeing.
[Fascinate Android Development] pntballer505:
Thanks for the info.
[Fascinate Android Development] k_nivesout:
No problem, sorry I can't be more helpful. Still have some figuring out to do of my own with better battery stats.
[Fascinate Android Development] neh4pres:
I have noticed that no changes seem to be made until you leave the app.. Then the super user message comes up.
[Fascinate Android Development] Eris _2.1_2010:
^^^^Same here^^^^

Sent from my Glitched AOKP Mez
[Fascinate Android Development] Aali1011:
Has anybody tried this with sbrissen's test build or build 8 for that matter. I tried the test build which i believe is pretty much build 8 and the kernel broke sensors which i guess he has fixed. It could be a isolated incident as well on my part. Went back to rom Ver 7.1 with Glitch V14 B6 and that is working fine. Oooooo and while i remembered in NStools what is the whole point of target high OC. I am 105% for OC Value and Max CPU freq is 1260. OC Target Low is 800 and OC Target High is 1200 this seem right or no.
[Fascinate Android Development] neh4pres:
Yes.. High target would be to shut live oc down at a selected high clock. I don't see a reason to use it so i set mine too 1500
[Fascinate Android Development] Aali1011:
Is that a yes to V14 Beta 6 Working with Rom Version 8?
[Fascinate Android Development] Stephen.k.spear:
if you use the one in the OP you will break your sensors. You need to use the Efpophis fixed test build floating around. Do not use the big ram kernel. It will break video and camcorder on the ths builds.

Just out of curiosity why are you guys waiting for THS builds when our kangs have the newest frameworks, all the glitch tweaks and kernel, and did I mention at least 47MB (or ~15%) more ram?

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] sixstringsg:
efpophis.glitchteam.com will have whatever they need.
[Fascinate Android Development] sendan:
It means you flashed the wrong version, try flashing the "other" one.
[Fascinate Android Development] bobloblaw1:
EDIT: The information in this post is quite probably erroneous according to the man behind the kernel, himself. I may try to do some more benchmarks at some point but at the moment I'm rather burnt out on this. Sorry for any confusion that may have been caused. Again, DON'T TRUST THE INFORMATION IN THIS POST AS PER TK-GLITCH.

Another long post. I hope this makes sense to someone and helps them in planning their overclock.

Stock Bench for reference

(110% Live OC 1100mhz max.................................................................................................. 120% live OC 1200 mhz max ......................................................................................................................115% live OC 1380 mhz max)

So, what is the point of these images? Basically these are helping us see whether it is more beneficial to go for a high bus overclock (RAM, GPU), a high clock speed, or a blend of both.

We can see that both CPU measures continue to increase across the image set as clock speeds increase. I think the main thing to focus in on is the 2D/3D GPU benchmark. We see that the results are rather consistent across the spectrum from a 10% bus overclock to a 20% bus overclock. In fact, the result are nearly identical at 15% and 20%. This would lead me to believe that the GPU and RAM is actually bottlenecked by the CPU at 120% and 1200mhz.

(for the record, at 115% and 1150mhs (1000mhz step) the GPU preforms equally to the 1380 image. RAM scores only 412 vs 496. CPU scores are lower. THis reconfirms that the RAM is bottlenecked by the CPU speed.)

In the 3rd image we decrease the Live OC but increase the CPU clock. Despite being clocked lower than in the second image, the RAM preforms better and the GPU preforms equally to as it would with an additional 5% overclock. I think it's pretty clear that Android and our phones are still generally CPU bottlenecked.

So what should we take-away?

1. Android still highly relies on CPU clock speeds over GPU.

2. Bus (live) overclocking is useful up until roughly 115%. Anything over that and it is unlikely to be stable at the 1200mhz step. Therefore you are going to have to stickwith the 1000 step and will be unable to avoid a CPU bottleneck thus negating the additional power on the GPU level.

3. It still may be worthwhile to see if we can push past 115% but maintain stability at the 1200mhz step. This is the holy grail but seems quite unlikely at least on my device.

4. this is a synthetic benchmark and user experience may vary..blah blah blah
[Fascinate Android Development] Tk-Glitch:
Antutu 2D/3D tests are the poorest available for our phones. Remember we are stuck at 56 FPS due to our screens. These tests will run at ~56 FPS at all times even on stock clocks, that's why it doesn't improve with OC. Nothing to do with CPU bottleneck.

If you want to benchmark your GPU and measure overclocking gains, use Nenamark2, An3DBenchXL or GLBenchmark, not antutu.