Discussion in 'Android Devices' started by jimsmith80, Aug 24, 2013.
We may have to build a 3.4 kernel before fiops will work
Are both cores unlocked and run all the time?
No they are not. A little wile back in DSF I had created an init.d script to run both cores full time, and the only noticeable difference was that the battery discharged much quicker
earlier today i noticed that fiops would need a 3.4 kernel. im backporting the deps now to get it to run. I backported hyper cpu gov which needs 3.4 kernel and added to my github.
i just need a few more hours
I'm excited! I think I'm coming back to dsf from cm10, I'm gonna miss the features of cm10 though, but I think I use GPS more than most people on this forum and GPS isn't working correctly on cm10 and it's really upset me.
I use the heck out of GPS navigation too.
And I'm still on stock rom,But I did weed it out.
Weed what out?
Can screen sensitivity be toned down in the kernel? Idk if any of you have noticed how sensitive the screen is but I can hold my finger over a button and accidentally press it without actually pressing it. The sensitivity tones down if I use a screen protector, which I recently had to remove because it became old, but will replace because it improves the touch screen and I find the glass to be a big finger print magnet.
I'm sure it can be done, but I'm not sure its a good idea. A lot of people have screen protectors, and I haven't noticed the screen being any more sensitive than stock
I'm saying the screen without the screen protector is ridiculously sensitive, with one it improves and tones down a bit but is still highly sensitive.
really anything can be done with the kernel, as for doing it....well I'm not sure how well jimsmith80 is with kernels but I know I can't do it right now. I need to improve my programming skills first
New to the game my self but learning a lot
Just benched over 16k in antutu
awesome dude, on current version?
Yes no changes as of yet. My next move is to underclock
lower clock speeds down to 245 mhz are already in there. you just need to undervolt. drop like 25mV starting at 918 mhz (learned this from HTC One S/X because they are the same board and I did this for Galaxy Victory)
I'll get to work then. I'm wanting to take it down to 128 or so
A lot of times when you go below 245 your gonna end up with issues with the phone waking up. 245 IMO is the safest way to go.
You may be right. This is my first time working with the 8960, but I did manage to take the warp all the way down to 30. Even if sub 200 speeds won't work, 245 will extend battery life some
I love the 8960 krait platform. its alot more work but worth it and seems more straight forward than the 7x30. the best part it the platform/msm_sdcc.1/by-name/ partitions.
im currently patching the Galaxy Victory kernel way too much than it needs to be (this is a good thing!) and will make my way to applying patches to Matrix_Force and see if it compiles in.
here is a commit for Krait OC to 2.1 GHz by faux123 (perhaps the greatest kernel dev in history!)
he did i tried to do (if i tried to OC that high it would bootloop) but he's just that good
I'll check it out, but honestly I'm a little nervous about taking the CPU that far over stock. The chip was designed for 1.7, so I know it can do it. My concern comes form the heat that this little phone generates.
well...u can hack it in a specific way
make it clock that high and go back and #define MAX_CPU_CLOCK as 1.6 and have a secondary modified performance gov (also keep original in with max 1.6) with max set to 2.1 for those who just want it (and only the modified secondary perf gov will clock up to 2.1)
thats what i like about kernels. if you can program it in, its possible
Very true. I'm working on underclocking. the idea is to keep the default low speed and include a script to lower the CPU frequency and reset the governor while the phone is asleep. We did this on the warp, and we greatly extended the battery life, and kept all of the performance we had gained.
Looks like I have underclocking sorted out. 192 Mhz seems to be stable so far. I will do some more testing and tweak the source a little further, but Matrix Kernel 1.2.? should be ready soon.