Related
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
Please confirm if this works or not. Tiamat 1.0.4 has:
ported sysfs interface for VDD levels from Tiamat_8x50 (cayniarb, eviollet)
But I'm not sure where the path to the levels are since I can't find the commit in his git.
EDIT: I found the commit, it looks like its SVS. I will update later and post a new build. I need an individual who is proficient with using adb or the terminal emulator to please pm me.
Chad, sorry, I know this is off topic, but does your Incredikernal work on the Incredible2?
rfarrah said:
Chad, sorry, I know this is off topic, but does your Incredikernal work on the Incredible2?
Click to expand...
Click to collapse
No it does not. I don't really like to do kernels for devices I don't have because its difficult to properly test. If someone comes across an extra device that they are willing to donate I'd be more than happy to start working on one though.
chad0989 said:
No it does not. I don't really like to do kernels for devices I don't have because its difficult to properly test. If someone comes across an extra device that they are willing to donate I'd be more than happy to start working on one though.
Click to expand...
Click to collapse
Okay, I didn't think so, but on the off chance they DID, I'd be downloading immediately. Your kernals - at least on my Incredible - were the Gold Standard. Thanks for all that work!
My DI1 died last Saturday and Assurion replaced with a DI2. Still getting my feet on the ground with it, but after rooting and loading MIUI, it's almost like a big DI1.
Anyway, thanks again.
Does anyone.know if the china version of sense3 work with this
Sent from my HTC Incredible 2 using XDA Premium App
Anybody available to test?
I would if I knew this china rom met the requirements
Sent from my HTC Incredible 2 using XDA Premium App
I wouldn't mind giving it a shot.
Sent from my Droid Incredible 2
ruvort said:
I wouldn't mind giving it a shot.
Sent from my Droid Incredible 2
Click to expand...
Click to collapse
Thanks, I'll be sending you a PM in a few minutes
I'll try it how do I know my kernel supports it
Sent from my HTC Incredible 2 using XDA Premium App
REDSCARFACE1 said:
I'll try it how do I know my kernel supports it
Sent from my HTC Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
I believe Tiamat 1.0.4 is the only one that has user changeable voltage scaling right now. Are you running that one?
Edit: I think jdkernel stable 1.0.0.1 may also
Please make an incedikernel for our phones! I loved it for the Inc1
06stang said:
Please make an incedikernel for our phones! I loved it for the Inc1
Click to expand...
Click to collapse
Refer to http://forum.xda-developers.com/showpost.php?p=16075489&postcount=4
Maybe someone will fall over an exra refurb at some point or something. I'd love to just do it, but its really difficult on a short time schedule to wait for feedback from someone just to see whether or not something boots. Or if a new feature works. I usually go through 100+ testing builds between releases. Hope you guys understand.
i would too but i have no idea if my kernel supports it. i'm on jdkernel stable 1.0.0.1
bik2101 said:
i would too but i have no idea if my kernel supports it. i'm on jdkernel stable 1.0.0.1
Click to expand...
Click to collapse
I believe it might. I'm going to send you a PM.
Titmat does not work with china ota sense3 rom.
Sent from my HTC Incredible 2 using XDA Premium App
REDSCARFACE1 said:
Titmat does not work with china ota sense3 rom.
Sent from my HTC Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
Then you will have to wait for a sense kernel that supports sysfs voltage changing. Sorry. I'm sure one will come around pretty quickly.
07/28/11 - Preview 5-2
Changes include:
A restore defaults button. NOTE: You must reboot for the changes to take effect.
A text box that lets you know if you currently have saved boot settings or not.
Support for SVS kernels (and subsequently support for msm7x30 devices, e.g. inc2)
Started to work toward database storage of voltages instead of boot scripts. There is still a boot script, but it has been relocated to /etc and is now run by a service at startup.
NOTE: As of now, the only inc2 kernel that supports voltage adjustment is Tiamat 1.0.4
Get it at http://www.incredikernel.com
chad0989 said:
Refer to http://forum.xda-developers.com/showpost.php?p=16075489&postcount=4
Maybe someone will fall over an exra refurb at some point or something. I'd love to just do it, but its really difficult on a short time schedule to wait for feedback from someone just to see whether or not something boots. Or if a new feature works. I usually go through 100+ testing builds between releases. Hope you guys understand.
Click to expand...
Click to collapse
Hope it works out. Love your work on the Inc1
# I am not responsible for anything that happens to your phone
# Please keep in mind that many of these roms have ideas from other developers, so you will see some of the same tweaks. This is a learning process
# for me. I intend to keep learning with your constructive criticism. If you think I stole something from you, please pm me and I will either remove it or
# give you credit. If you have something that you think will help me, please feel free to tell me. This is just my way of sharing my current progress with
# the development community. If you know more about something than me,
# let me know.
This is a stock looking Rom with lots of tweaks. It runs smoothly. I would use it with Go Launcher. I have tested it with Synergy kernel and recommend it. This Rom comes with a new feature that is not completely ready. You can run it in terminal:
Code:
su
cd /etc/init.d
sh start.sh
sh fkturbo1.sh
This is not a completed rom but all the bugs I found have to do with the added scripts. All of the tweaks should work. Others will be added when I have time. I was hoping to get more done, but I started out in Notepad. It took me a day to remember that's why the script doesn't work. I hate Win 7. lol
Also, themes will be included when it is out of beta.
#NEW# FKTurbo v.2b
This feature allows you have a turbo in your phone. The higher the frequency goes, the faster and more powerful it will be. When completed, this will increase multiple settings towards performance when your phone is used heavily. It will automatically set them back to save power. It will be improved to remove all bugs and errors and work seamlessly with your phone. It is in beta, so I know there are some bugs that will be fixed. It will not activate on boot until it runs perfectly. I will add code to make it activate in a much smoother way in the next release.
Advantages:
-Easily switch to max power when you absolutely need it, automatically.
-Easily switch to power saver mode when you need good battery life, automatically.
-Go longer between charging by using extra power only when you need it.
-No more adjusting multiple settings to go from max power to max saver.
More new features as soon as this gets running right!
GB.6.tweak v.1b (Removed due to problems.)
fktweakedv0.2b (name changed)
fktweakedv0.4:
All features listed below.
Lightly themed.
Improved fkturbo.
Base on Mr.X's CIQ free 2.3.6
In the rom:
CIQ free 2.3.6
WiFi Calling
Deodexed and Zipaligned
SU
BusyBox
Init.d support
Kernel tweaks
VM tweaks
Data tweaks
Scrolling responsiveness tweak
Zipalign at boot
launcher in memory
UI with GPU
Delvik increased to 64mb
Wifi interval increased and other tweaks for better battery life
JPEG quality at 100%
Defrag database at boot
Touchscreen sensitivity increase
deadline scheduler tweaks
Sdcard cache increased
Lots of other tweaks
Team Kang's Toggle Buttons
Loopy smoothness
#NEW#FKTurbo#NEW# *
*not completed
Installation with CWM:
1. Download the Rom and your favorite kernel. (Synergy,Bullet,Faux,Darkside) (fkturbo works in synergy, but I haven't checked others yet)
2. Boot into recovery. (Hold Volume Up/Down and power on)
3. Install the Rom first and then the kernel.
4. Reboot and allow it a few minutes on the first boot, then reboot. *No boot animation means that it will go blank for a long time at first boot.
Link to the ROM (4shared):
http://www.4shared.com/zip/qzMe7f6n/fktweakedv04.html
Looks great. I love the MIUI battery gauge. I'll give it a try after v-day.
Thanks Buddy
Looks Nice! Ill report after I flash Thanks man!
Does this rom come with a custom kernal or a stock kernal out of the box
What do u mean of data tweaks and scrolling tweaks ?
Sent from my SGH-T989 using xda premium
fallenmk4 said:
Does this rom come with a custom kernal or a stock kernal out of the box
Click to expand...
Click to collapse
It has a stock kernel, but it will have other available kernels very soon. I plan to update this with the current version I'm running by this weekend. You can use any modified stock kernel. Not AOSP kernels.
ymcmbforever said:
What do u mean of data tweaks and scrolling tweaks ?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
It is a very rough estimate of all the stuff that's in it. Data speed tweaks can potentially increase speed on networks. Scrolling tweaks makes scrolling smoother. Look in /etc/init.d/new2 or /system/build.prop for many of the tweaks. This is the old version, so the new one will have more stuff and a better explanation. Not all the tweaks are listed. There are many more to come!
Im doing this at work, so I don't have the time right now to list everything properly.
system rebooted, please keep the virus away
hit the report button for anyone off topic
Thank you Json. we are waiting for tje new rom coming.
@ Allgamer thank you for cleaning the thread.
New rom. Lightly themed. Almost done with the new feature!
Json'Smyth said:
New rom. Lightly themed. Almost done with the new feature!
Click to expand...
Click to collapse
So the rom is not complete???
Im a little lost
So is the rom in the op the updated or are you in the process of updating?
Not asking for an eta just wondering what rom is in the link.
tdizzle404 said:
Im a little lost
So is the rom in the op the updated or are you in the process of updating?
Not asking for an eta just wondering what rom is in the link.
Click to expand...
Click to collapse
The rest of the rom is working. It is version .4. I am still trying to perfect the code the new feature. I have lots of tests coming up (Bio, Chem, etc.), but I will try to get it perfected by the end of this week. This code is just a teaser that may have bugs in it. It will be updated. Thank you for your patience. Feel free to try it, but keep in mind that it may not work right just yet. If it messes up something, just run fkpower1.sh or powersaver.sh. fkpower1.sh is the better choice.
Code:
su
sh fkpower1.sh
bbobarino said:
Wow what a dousche. Rom control is beast absolutely brilliant and as for the 20 roms we have are awesome and the development in this forum is great. Only thing missing is an operational miui
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Everybody has a right to an opinion, even if it not something you agree with. Please try to keep the thread clean by posting your personal attacks to a different location. I understand that all original work takes lots of time and effort, but name calling is not necessary. Thanks.
Ill give it a whirl. there are a couple features I haven't seen advertised in other roms. _I thought all the haters had left the sgh-t989 tread. Must have just been at the haters ball instead of reading up on the Android kitchen. There is a link some where in the dev thread. Build something better and stop being an ass douché.
superuser696 said:
Ill give it a whirl. there are a couple features I haven't seen advertised in other roms. _I thought all the haters had left the sgh-t989 tread. Must have just been at the haters ball instead of reading up on the Android kitchen. There is a link some where in the dev thread. Build something better and stop being an ass douché.
Click to expand...
Click to collapse
I like your statement. very impressive.
Yes i pm you not posted in the thread posted in your pm rookie keep it to the pm *****
LOL he so butt hurt over. Rom control .....get a life man...[/QUOTE]
Sent from my SGH-T989 using Tapatalk
How about we don't ruin this devs thread for a second time?!? Thanks for your work jasn.
Sent from my SGH-T989 using Tapatalk
So in the sake of getting back to the point at hand what is this feature and what does it do for us?
Edubyah said:
So in the sake of getting back to the point at hand what is this feature and what does it do for us?
Click to expand...
Click to collapse
Good question!
This feature, which still needs some polishing, will allow you to save power when you are not using the phone heavily. It does this by modding the governor settings, which need some tweaking, and the voltage settings, which are being tested today.
When it senses that you are using the phone heavily, it will automatically increase the settings towards performance. As soon as the phone is no longer used heavily, it will automatically change all the settings to favor battery life.
This allows for a perfect balance between the power savings of undervolting, underclocking, and stiffening up the governor and the performance benefits of overclocking, etc.
This eliminates the need to decide between the full power of the phone and the ability to use the phone for longer between charging.
By the end of this week, I will have the settings tested (to make the power change smooth) and more steps between full power and full economy will be added. More settings will be adjusted by fkturbo by the end of the week. It may also be made more universal, but that will take longer than this weekend.
It is being updated to v0.5 for the rom and v0.3 for the feature.
You've heard of that car mode epidemic happening to evo users all across america right? well, it finally happened to me. i didn't think it would because i dont even use my usb port unless its for transferring files.
Now, ive looked all across the web and it seems to be just a hardware issue. I dont have warranty nor do i have insuarance.
Finally I found this thread: http://forum.xda-developers.com/showthread.php?t=1212260
and this guy in there wrote:
sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
http://forum.xda-developers.com/attachment.php?attachmentid=687912&d=1313280355
Click to expand...
Click to collapse
I've tried devving but i suck at it. So could someone be nice and kind and stuff and do that for the cfs havs savaged zen kernel?
I dont even know if its a difficult task or if its easy peasy, i just wanna get rid of this god damned car home virus.
Here are some links for ya:
the kernel thread it self: http://forum.xda-developers.com/showthread.php?t=917755
the post i quoted mentioned the need for source, so: https://github.com/Savaged-Zen/Savaged-Zen
PLEASE HELP ME! and thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...axDev Developers Present...
...In association with Team Inferno...
axDev GENERATOR
Like a rock... Like a planet... Like a ****ing atom bomb
Keeping the thread very basic for now.
I found my glacier not too long ago and decided to do some kernel work while I started over on my Linux machine with Mint.
The goal here is to squash some long-running bugs in our 3.0 kernel and add a little sauce on the side whenever I can.
The kernel is experimental, but I'll keep my main axdev branch as clean and stable as possible.
I would also like to note that this kernel is primarily tested on the latest evervolv nightlies (other roms likely supported [must be linux 3.0 compatible]).
Features:
- Compiled using Sourcery CodeBench Lite 4.7.3 ARM-EABI toolchain
- Rewritten display panel (based on stock vivo 3.0 kernel)
- Audio/Headset driver updates from vivo 3.0 kernel
- Reduced logging
- mm adjustments from ck1
- see github source
NOTE:
I don't really have a SIM card for my glacier or an adapter to get my current SIM to work with my glacier, so my ability to work with phone calls, signal, and things of that nature will be limited (though some of those problems probably aren't kernel problems). So that being said, if you have problems with things related to using data/signal, provide a dmesg or I simply will not be able to help you. This also effects any way of me accurately testing for real-time battery life.
Acquiring dmesg/last_kmsg:
http://code.google.com/p/tegraowners-ics-rom/wiki/How_to_get_logs
Bugs:
- Our 3.0 kernel/4.3 roms seem to have some weird graphical glitches. (Reboot and pull down notification bar before shutting off screen to fix)
[NOTE: You should only need to do this once per boot.]
- Headset heat. Don't know if its any better or worse.
(Let me know; please include dmesg in bug reports if possible)
(The following zip is an AnyKernel flashable zip. Just flash in recovery
[your recovery may work, but I only support madmaxx's 4ext recovery due to consistent problems with others. If you encounter any problems, try using 4ext])
(I will make mirrors, boot.img flashables, etc. by popular request)
Downloads:
D-h.st Archive: http://d-h.st/users/synthetic.nightmare/?fld_id=25972
Goo.im Mirrors: http://goo.im/devs/aokpx/glacier_generator
Changelog:
Current -
Code:
2013-10-21 -
b66b994 Merge tag 'v3.0.100' into HEAD
da672f8 input: atmel: Updates from official HTC msm7x30 devices
88137b6 glacier: defconfig: Update based on android configs
c613340 glacier: defconfig: Allow ARM unwinding
fb04966 glacier-panel: fix timings
8016c4d msm_audio: Clean up non-msm7x30 specifics from header
29c65af 7x30-smd: cb_list_lock is now a spinlock
9122e87 mach-msm: unify the 7x30 wifi driver
11f47d5 glacier: remove cable detect
07cc5ff msm: cpufreq: Break out early if target frequency is the same as the current
7572726 Revert "mdp: increase timeout to 5s"
2526863 glacier: defconfig: Enable rpc vibrator for msm
a0d6d17 msm_vibrator: Update driver
680d097 board-glacier: Update htc headset configs
d183c6f htc_battery: Update battery call
Archive - http://pastebin.com/raw.php?i=rpUnmCjn
Testers:
OMGtylenol
Jenis123
John XX
Thanks To:
Virtuous Team
elgink8r
evervolv
codeaurora
HTC
conkolivas
stratosk
ripke
MentorGraphics
Linaro
TripNRaver
fransiscofranco
existz
My fellow MyTouch4Gers
Anyone I forgot....
I dont have glacier right now but would like to say thanks for the effort...I had used it for over 2yrs & loved the phone
Also something that I had pointed out earlier but was ignored and I couldnt flash & test but I have seen JSS screen flickering/tearing issue resolved on N4 so maybe you or evervolv could take the time to fix it for us
Thanks....& here is a link to JSS tearing fix http://forum.xda-developers.com/showthread.php?t=2368548 & also attached as file so you could try. I would have tried it by now if I had the device so thought someone could make it compatible for glacier users.
Thanks again
Thanks so much for your work Synthetic.Nightmare. It really means a lot to everyone here.
Just to clear things up, this isn't forked from Evervolv? Its all new from you?
Or is it forked from the Flemard github?
Thanks again for your work
Sent from my myTouch 4G using xda app-developers app
IndianKarmas said:
I dont have glacier right now but would like to say thanks for the effort...I had used it for over 2yrs & loved the phone
Also something that I had pointed out earlier but was ignored and I couldnt flash & test but I have seen JSS screen flickering/tearing issue resolved on N4 so maybe you or evervolv could take the time to fix it for us
Thanks....& here is a link to JSS tearing fix http://forum.xda-developers.com/showthread.php?t=2368548 & also attached as file so you could try. I would have tried it by now if I had the device so thought someone could make it compatible for glacier users.
Thanks again
Click to expand...
Click to collapse
Checked out the zip and it seems to be egl/hw stuff for msm8960 rather than kernel related. Not much can be done with hw-specific stuff, esp. without any source code to go off of.
N_otori0us_ said:
Thanks so much for your work Synthetic.Nightmare. It really means a lot to everyone here.
Just to clear things up, this isn't forked from Evervolv? Its all new from you?
Or is it forked from the Flemard github?
Thanks again for your work
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
No, its an evervolv fork.
No need to work on something that has already been done brilliantly. Just working forward. Besides, this way Elgin and I can share code, fixes, etc. easily.
Sent from my SGH-T999 using xda app-developers app
So heres what i got:
Clean install on all
Coderz Carbon ROM 10-02
Generator Kernel 10-03
Dont have access to logcat atm and not sure if it would help. When using carbon ROM with its kernel everything seems fines so far except dropped call issue with all 4.3. I then tried your kernel with his ROM and everything seems fine until the first time the screen locks. Then everytime after that, the screen is stuck showing upside down and wont rotate properly.
Could be ROM compatibility issues or something else but just sharing.Will try to get more info later.
Thanks for the kernel.
OMGtylenol said:
So heres what i got:
Clean install on all
Coderz Carbon ROM 10-02
Generator Kernel 10-03
Dont have access to logcat atm and not sure if it would help. When using carbon ROM with its kernel everything seems fines so far except dropped call issue with all 4.3. I then tried your kernel with his ROM and everything seems fine until the first time the screen locks. Then everytime after that, the screen is stuck showing upside down and wont rotate properly.
Could be ROM compatibility issues or something else but just sharing.Will try to get more info later.
Thanks for the kernel.
Click to expand...
Click to collapse
Well I cleaned up some weird-looking mdp flip/rotation stuff out of my display panel for sharp since it wasn't there for vivo and I wasn't quite sure why we had to have the panel flip by default, which worked for my device but I'll revert that though since it seems to cause a regression on certain panels and get you a test soon. If you'd be willing to test for me.
EDIT: If anyone else is experiencing the same, PM me and I will send you a test kernel with the revert so that we can get this sorted ASAP.
Sent from my SGH-T999 using xda app-developers app
Update to 04 build , i think signal drop issue fixed
Sent from my PER5274B using XDA Premium 4 mobile app
Bad Religion!
Sent from my Nexus 4 using Tapatalk 4
I'd be willing to do some testing.just lemme know.
Sent from my myTouch 4G using xda premium
coderzs said:
Update to 04 build , i think signal drop issue fixed
Sent from my PER5274B using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For real is it fixed?
Sent from my Nexus 4 using xda app-developers app
Big thanks to those who offered to test and help me fix the screen issue with the panel. I think I've got a nice little batch of testers and I JUST realized what it was as I was laying down for the night. I've got a little trick I want to try though before I just fix it... so, tomorrow, once I get a build done and get confirmation on whether what I have in mind works or not on the sharp panel, I'll try and get an update out soon after.
EDIT: Update posted.
WHAT TOO LOOK FOR:
Fixed upside down panel
Optimized vsync for our devices (should clear up screen tearing)
Audio adjustments (some reductions... just sounds better on this old speaker to me)
Some gcc optimizations and kernel built using -O2
Check the changelog/github for more info.
Sent from my SGH-T999 using xda app-developers app
Hey synthetic.nightmare,
I flashed your Oct 6 build on the evervolv ROM and still get headset heat up. Went up to 50 degrees Celsius. Which is over 100 degrees Fahrenheit
So should I be using carbon ROM if I want to use headphones ? Also I wont mind testing kernels but ill be testing on evervolv if that's alright with you?
Sent from my myTouch 4G using xda app-developers app
N_otori0us_ said:
Hey synthetic.nightmare,
I flashed your Oct 6 build on the evervolv ROM and still get headset heat up. Went up to 50 degrees Celsius. Which is over 100 degrees Fahrenheit
So should I be using carbon ROM if I want to use headphones ? Also I wont mind testing kernels but ill be testing on evervolv if that's alright with you?
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Nah i think its still a problem i just couldn't get very persistent results... But i have fixed headset keys w/ long press detection (somewhat, it detects the +,-,btn keys from my sgs3 headset as forward, back and play/pause) & headset mic... Though its not very useful when your device is heating up with a headset. I think I'm going to look over some of the glacier specific updates and see what all else has been changed. Gonna be kinda difficult to find since i don't really have any leads on exactly what is causing the heat. Especially since the previous idea of it being headset detection might not be the issue anymore.
Sent from my myTouch 4G using xda app-developers app
Hey bro BTW thanks for this Kernel.I dont use this device much but .It brought my glacier out of the drawer for a few days to play with it and enjoy your work!
Synthetic.Nightmare said:
Nah i think its still a problem i just couldn't get very persistent results... But i have fixed headset keys w/ long press detection (somewhat, it detects the +,-,btn keys from my sgs3 headset as forward, back and play/pause) & headset mic... Though its not very useful when your device is heating up with a headset. I think I'm going to look over some of the glacier specific updates and see what all else has been changed. Gonna be kinda difficult to find since i don't really have any leads on exactly what is causing the heat. Especially since the previous idea of it being headset detection might not be the issue anymore.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
I stopped looking into the detection as being a heat producer a while ago. It just seams that the sound processing for headset output is out of whack. Voltage or something. it wouldn't make sense that the CPU would heat up because it couldn't figure out if there was a mic or not.
bertscookie said:
I stopped looking into the detection as being a heat producer a while ago. It just seams that the sound processing for headset output is out of whack. Voltage or something. it wouldn't make sense that the CPU would heat up because it couldn't figure out if there was a mic or not.
Click to expand...
Click to collapse
I haven't been able to work on this for "a while ago" but yeah. That's what its been looking like. I was looking into the way some of our rpc stuff is configured and there might be a good bit of that which needs fixing/reconfiguring. Not entirely sure but I know we have been running things like vibrator without the proper RPC config for some time now (didn't really effect us though since msm_vibrator was still using the code that is now rightfully ifdef'd as rpc).
Also looking into zeng's kernel, it seemed he was using a lot more code from caf than what we seem to be using now (don't know if that's just because we were more inline with virtuous' work). So working with those drivers may help... Difficult to say though, because I've gotten a couple ideas for fixing things, looked at evervolv's commits, and seen elgin tried (and later changed) the same thing months ago.
Sent from my SGH-T999 using xda app-developers app
What do you think the lowest we could undervolt before the kernel gets messed. Is -500 crazy? Lol
Sent from my myTouch 4G using xda app-developers app
Synthetic.Nightmare said:
I haven't been able to work on this for "a while ago" but yeah. That's what its been looking like. I was looking into the way some of our rpc stuff is configured and there might be a good bit of that which needs fixing/reconfiguring. Not entirely sure but I know we have been running things like vibrator without the proper RPC config for some time now (didn't really effect us though since msm_vibrator was still using the code that is now rightfully ifdef'd as rpc).
Also looking into zeng's kernel, it seemed he was using a lot more code from caf than what we seem to be using now (don't know if that's just because we were more inline with virtuous' work). So working with those drivers may help... Difficult to say though, because I've gotten a couple ideas for fixing things, looked at evervolv's commits, and seen elgin tried (and later changed) the same thing months ago.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Sorry I may have come off a little douche-y. I didn't mean like "WTF stop wasting your time I'm awesome." it was more of a "I saw that too." Compared to me you are Master and I defer to you.
Yea elginsk8r does that to me ALL the time. I'll think to myself "I'm going to change this see what happens" only to see he commited it 12 hours ago.....
I was going to start looking into htc_acoustic. Also, if you know, the htc_35mm_jack (I think that's the right file.) is that for different hardware than the glacier or does that also effect i2c?
I'm not great with kernel so forgive me for sounding nubish.
Would this file have anything to do with the headset heat?
Its in --> sys/devices/virtual/htc_accessory/headset/
then there is a file that says state, and when theres no headset in the file says unplugged, but when you plug it in it says headset_no_mic, and thats also where it fails because I remember a post that Elgin made that it fails to detect the mic or something like that.
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
Found the post
http://forum.xda-developers.com/showpost.php?p=41663597&postcount=150
N_otori0us_ said:
What do you think the lowest we could undervolt before the kernel gets messed. Is -500 crazy? Lol
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Theres a point to where undervolting will actually not help at all, since your clocks wont be getting proper voltage, they'll be working harder. Dunno exactly what point that is for these devices, but its likely to vary. Test and find out. Just be careful about setting voltages on boot before testing them.
bertscookie said:
Sorry I may have come off a little douche-y. I didn't mean like "WTF stop wasting your time I'm awesome." it was more of a "I saw that too." Compared to me you are Master and I defer to you.
Yea elginsk8r does that to me ALL the time. I'll think to myself "I'm going to change this see what happens" only to see he commited it 12 hours ago.....
I was going to start looking into htc_acoustic. Also, if you know, the htc_35mm_jack (I think that's the right file.) is that for different hardware than the glacier or does that also effect i2c?
I'm not great with kernel so forgive me for sounding nubish.
Click to expand...
Click to collapse
I'm not too sure. I haven't been playing with the kernel much since another project took priority (not glacier specific but definitely usable by glacier, once completed). But I know vivo and I think saga use a flag like that for their HTC headset configs. I wonder if elginsk8r's messed around with that yet.
N_otori0us_ said:
Would this file have anything to do with the headset heat?
Its in --> sys/devices/virtual/htc_accessory/headset/
then there is a file that says state, and when theres no headset in the file says unplugged, but when you plug it in it says headset_no_mic, and thats also where it fails because I remember a post that Elgin made that it fails to detect the mic or something like that.
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
Found the post
http://forum.xda-developers.com/showpost.php?p=41663597&postcount=150
Click to expand...
Click to collapse
Edit: I don't think I've seen that in any dmesgs I've taken recently. But its been a few days so I dunno.
Sent from my SGH-T999 using xda app-developers app
WildKernel
for T-Mobile Samsung Galaxy S II
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
v013: AFH
TRU Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
[#WildKernel-Celox-CL]
[/HIDE]
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultanxda
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
My recommended Governor/Scheduler setups:
Battery w/ Good Performance at 96-1350mhz:
Intellidemand/SIO (personal choice)
Lazy/SIO
Badass/SIO
Ondemand/SIO
Wheatley/SIO
'lil more Performance at 96-1512mhz:
Smartass/SIO
Hyper/Deadline
Samsung/Deadlne
lulzactive/Deadline
Savagedzed/Deadline
Best Performance (worst battery): 384-???mhz
Gaming/Deadline
Performance/Deadline
Did you read the announcement? (page header)
XDA:DevDB Information
WildKernel for the T-Mobile Galaxy S II (hercules), Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_samsung_msm8660/tree/android-msm-hercules-3.0
Kernel Special Features: Too many features to list, just install it.... now.
Version Information
Status: Stable
Current Stable Version: 013
Stable Release Date: 2015-01-29
Created 2014-05-28
Last Updated 2015-02-01
Wow I'm glad I was up late tonight! Downloaded this installed... Working cam 100% plus we can overclock again! Ole herc still running strong!! Thanks for this!!!
Thanks bro for doing this. I will flash and report
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
---------- Post added at 08:36 AM ---------- Previous post was at 08:31 AM ----------
Emmanuel, do you recommend CPU tuner or trickster or just stock performance to tweak settings?
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Just flashed it on Carbon 5/21. Initial thoughts are that it seems to get to the boot animation quicker than Uber. But initial reboot is long... I thought my phone was stuck in a bootloop... Also does not kill vibration after subsequent reboots after the initial reboot after flashing the kernel. It's just as quick as Uber and seems to work with Kernel Tweaker. This kernel also won't crash the phone playing 1080p in portrait... Love the fact that this kernel has sleep2wake as well. Will report back after using it for the day...
Any chance of a 2ghz version? And does this work with PAC outta the box?
Edit: Forgot to say thanks for giving us another kernel for the good ol' Herc. So, thanks.
Sent from my SPH-D710 using Tapatalk 2
Not sure if its kernel related but after rebooting my phone because of play store issues. After rebooting, I lost all of my widgets that I placed on 4 screens.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Emmanuel U said:
WildKernel
for T-Mobile Samsung Galaxy S II
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms.
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please wipe cache and dalvik cache to avoid any possible issues.
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Download Latest WildKernel for Android 4.4+
Mirror (HTTP) / (FTP)
View all public kernel releases (Mirror)
Changelog:
Code:
[B]May 27, 2014 - ver001[/B]
1. Initial Release (based off Diablo 3.1 & Merged with all latest CM vidc changes to fix camera/camcorder issues)
2. [B]Voltage Table Overhaul: All clocks have noticeably reduced voltages to improve battery life without compromising performance.[/B]
3. [B]Add More GPU Scaling steps to create a new 'low power' idle and more intermediate steps until an OC[/B]
4. Various FS, IRQ, MM, Mutex patches
5. Enable All tweaks for Badass (including low-bat powersave, allow bypass etc.)
6. [B]New 'Ultra low' CPU Idle steps (96-153mhz) - Low power idling[/B]
7. Mpdecision allowed to scale down to 96mhz
8. BadAss and SIO set as default gov/sched
9. Update all Ondemand based governors to upstream (Google)
10. Update LZO (faux123)
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultan
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
XDA:DevDB Information
WildKernel for the T-Mobile Galaxy S II (hercules), Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Emmanuel U
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 001
Beta Release Date: 2014-05-27
Created 2014-05-28
Last Updated 2014-05-27
Click to expand...
Click to collapse
I haven't tested this yet, but it is on my "to test" list. I'm going to download it on my lunch break and flash it sometime on the weekend. Had a quick question though: what is the recommended date of the ROM one should use with this Kernel? The ROM I'm running was last updated back in March so I am unsure if any new CM features were implemented or removed from the kernel since that time and I would rather not be stuck in a boot-loop or nothing. The kernel I'm currently sporting is "3.0.101-DIABLO-3.3". You say yours is based off of Diablo 3.1, so I THINK it should play nice with this ROM, but I'm nervous I'll soft-brick my phone.
Is there a reason you didn't use Diablo 3.3 as the base?
Also, your OP states there are screenshots, but none are included? I don't need them (kernels don't really need screenshots, eh?), but just thought I'd point it out.
Thanks for being one of the ones keeping the t989 alive.
EDIT: I'm dumb... just saw the screenshot tab at the top. 18 hours on battery is pretty good. I get about 10 with how I have things set right now, so getting an extra 8 would be awesome.
bmg002 said:
I haven't tested this yet, but it is on my "to test" list. I'm going to download it on my lunch break and flash it sometime on the weekend. Had a quick question though: what is the recommended date of the ROM one should use with this Kernel? The ROM I'm running was last updated back in March so I am unsure if any new CM features were implemented or removed from the kernel since that time and I would rather not be stuck in a boot-loop or nothing. The kernel I'm currently sporting is "3.0.101-DIABLO-3.3". You say yours is based off of Diablo 3.1, so I THINK it should play nice with this ROM, but I'm nervous I'll soft-brick my phone.
Is there a reason you didn't use Diablo 3.3 as the base?
Also, your OP states there are screenshots, but none are included? I don't need them (kernels don't really need screenshots, eh?), but just thought I'd point it out.
Thanks for being one of the ones keeping the t989 alive.
EDIT: I'm dumb... just saw the screenshot tab at the top. 18 hours on battery is pretty good. I get about 10 with how I have things set right now, so getting an extra 8 would be awesome.
Click to expand...
Click to collapse
It'll work fine with older KitKat builds.. And I don't think you'll have compatibility problems with using it with a ROM that came with a newer version of Diablo. I was at one point using older builds of Cl3kener's kernels on newer builds...
Sent from my Carbonized GS²
suaverc118 said:
Thanks bro for doing this. I will flash and report
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
---------- Post added at 08:36 AM ---------- Previous post was at 08:31 AM ----------
Emmanuel, do you recommend CPU tuner or trickster or just stock performance to tweak settings?
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will always recommend the stock performance app as it's apart of the system so you know for a fact it won't be holding any child proccesses which may effect battery etc.
mp3deviant721 said:
Just flashed it on Carbon 5/21. Initial thoughts are that it seems to get to the boot animation quicker than Uber. But initial reboot is long... I thought my phone was stuck in a bootloop... Also does not kill vibration after subsequent reboots after the initial reboot after flashing the kernel. It's just as quick as Uber and seems to work with Kernel Tweaker. This kernel also won't crash the phone playing 1080p in portrait... Love the fact that this kernel has sleep2wake as well. Will report back after using it for the day...
Any chance of a 2ghz version? And does this work with PAC outta the box?
Edit: Forgot to say thanks for giving us another kernel for the good ol' Herc. So, thanks.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yes it should work out of the box with ALL KITKAT roms. As for Jellybean and before I'm not 100% sure as they may and most likely use different ramdisks. Also I doubt you will see me push out a 2ghz version as I don't really like to OC, but when I do I like to stay in the OC 300-400mhz stage. Once getting above that you risk damaging your hardware overtime which can stunt it's life.
suaverc118 said:
Not sure if its kernel related but after rebooting my phone because of play store issues. After rebooting, I lost all of my widgets that I placed on 4 screens.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How many times did this issue occur to you? Did it happen right after kernel installation? Because it's sounding more like a rom related issue.
After about 12hrs into it, video recording added a nonstop buzzing sound in all video res. Reboot fixed the issue. See catlog. I am currently on AlpineRom.
Emmanuel U said:
Yes it should work out of the box with ALL KITKAT roms. As for Jellybean and before I'm not 100% sure as they may and most likely use different ramdisks. Also I doubt you will see me push out a 2ghz version as I don't really like to OC, but when I do I like to stay in the 300-400mhz stage. Once getting above that you risk damaging your hardware overtime which can stunt it's life.
Click to expand...
Click to collapse
I meant all older builds of KitKat ROMs. My bad. I didn't claify. I'll edit my post. And I thought I'd ask about 2ghz, it was nice when I had it...
Sent from my Carbonized GS²
woot
a wild kernal appears
Is Hyper supposed to stay a higher frequency on Core 0 when you are playing music or running an app and not doing anything else and with the screen on? I'm currently set at 1836/192 and the frequency settles more at 756 on Core 0. If I set minimum to 384 then it seems to settle more on 384. I couldn't find much info on how Hyper works so I'm just wondering if this is normal.
Sent from my Carbonized GS²
Something went very wrong....
About an hour after installing this kernel last night I picked my phone up off the table and noticed it was in a boot loop.
I went into recovery and wiped the cache and it eventually booted to the CM-11 Welcome screen asking me my language preference.
I rebooted back to recovery to restore from my backup and (long story short), I couldn't because the partition table on my external sd card has been destroyed. I don't know what would have done that I wasn't actually using the phone at the time.
Sorry I don't have logs, but if anyone knows how to recover an sd card with no partition table i'd love to hear about it. I tried gpart/gparted with no success. I assume the partition was some kind of FAT but I don't know for sure.
Last night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
sfleury said:
About an hour after installing this kernel last night I picked my phone up off the table and noticed it was in a boot loop.
I went into recovery and wiped the cache and it eventually booted to the CM-11 Welcome screen asking me my language preference.
I rebooted back to recovery to restore from my backup and (long story short), I couldn't because the partition table on my external sd card has been destroyed. I don't know what would have done that I wasn't actually using the phone at the time.
Sorry I don't have logs, but if anyone knows how to recover an sd card with no partition table i'd love to hear about it. I tried gpart/gparted with no success. I assume the partition was some kind of FAT but I don't know for sure.
Click to expand...
Click to collapse
That happened to me a short while back using A different ROM and kernel. For me, my sd card died and I sent it back under warranty.
Sucks cause you lose all the data and no way to recover but if you can warranty it,I would.
Sent from my SM-T310 using XDA Free mobile app
bmg002 said:
That happened to me a short while back using A different ROM and kernel. For me, my sd card died and I sent it back under warranty.
Sucks cause you lose all the data and no way to recover but if you can warranty it,I would.
Sent from my SM-T310 using XDA Free mobile app
Click to expand...
Click to collapse
Ya I suspect the card has failed based on how it is behaving in my computer. I will look into warranty but I'm not very good at keeping the paperwork for such things.
sfleury said:
Ya I suspect the card has failed based on how it is behaving in my computer. I will look into warranty but I'm not very good at keeping the paperwork for such things.
Click to expand...
Click to collapse
I'm not either, but if you know where you bought it from (online sources are usually the best as you will have an email receipt) AND you have an account with them, they MAY be nice and pull your receipt up for you. Sandisks warranty info though states that you need to have your original receipt AND the original packaging. When mine died they were happy enough with a photocopy of the receipt being emailed to them and they didn't need the original packaging.
It sucks when it does die because you lose your data and you don't know if it was due to the new stuff you were trying or simply a fluke. I've been meaning to try my new stuff again on my card (moving /data to external storage), but I'm nervous that that is what killed it. It gave me a nice performance boost (surprisingly), but I only got about 2 months before things died for me
Now I back up my SD cards roughly once every 2 months just in case one dies on me again. Well, unless I make no changes OR I only add stuff I can re-download easily.
Boot loop for me, using the latest Pac Man nightly...
ricthot said:
Boot loop for me, using the latest Pac Man nightly...
Click to expand...
Click to collapse
Same here dude.. Cannot change governor or phone will freeze and then go bezerk...boot loops etc. Will not work on alpine or carbon for me
Nice, new kernel. Something to play with this weekend.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app