Develop Bugs

[KERNEL] -2.6.35- Eternity Project for HTC Vision --- DIRTY --- TEST

Welcome to the Eternity Project Kernel for HTC Vision Thread!
The Eternity Project Kernel for HTC Vision (T-Mobile G2 & HTC Desire Z) is developed for gaining the maximum possible speed mantaining the maximum safety on our devices.
Features:
- Updated kernel (2.6.32.17 -> 2.6.35)
Kernel GIT Repository: http://gitorious.org/eternity-prj/eternityvision_2-6-35
Still some errors to correct.... and need help :|
Stay TuneD!

Thanks! Will test.

good stuff. porting the board files/dependancies, etc. is quite a bit of work, so my hats off to you!
will check it out.
thx for your efforts.

wow another?

I'm not 100% sure that I've ported all correctly (excluding some compiler errors that prevents the building ... and that I'm correcting)... so, well, pershoot, knowing your work I'd be proud if you take a look at the code
Anyway, I've corrected some other things, now I'm dealing with some errors on mddi.c ... I hope it'll be ready to test in some hours
Returning at work!
P.S.: It's ----SO---- dirty! I've uploaded it while testing and error checking!

kholk said:
I'm not 100% sure that I've ported all correctly (excluding some compiler errors that prevents the building ... and that I'm correcting)... so, well, pershoot, knowing your work I'd be proud if you take a look at the code
Anyway, I've corrected some other things, now I'm dealing with some errors on mddi.c ... I hope it'll be ready to test in some hours
Returning at work!
P.S.: It's ----SO---- dirty! I've uploaded it while testing and error checking!
Click to expand...
Click to collapse
yup for sure. i've gotten as far as the new QSD SPI bits, and put it down to work on other things... haven't gone back to it yet.

The new QSD SPI bits in the files uploaded are broken (prevents compilation), but locally I've already corrected them.
I've uploaded the files because I've done almost all the work, it needs only another percent of finalization...and I'm not committing every change in the same moment 'cause it would be painful
EDIT: Other things checked and fixed. Changes committed.
EDIT2: I'm stuck at the end. Anyone can help? Thanks!

Has there been any headway on this? I for one think this has a lot of potential.
Sent from my G2

thanks for your work. Is this kernel designed for AOSP or Stock or both? I'd love to have it compatible with Stock Rooted Rom

It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01

kholk said:
It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01
Click to expand...
Click to collapse
Ooo, you do what you have to do buddy and take your time! Have a great time with your loved ones and Happy new year to all!

Can I test this kernel on gingerbread/cm7 builds
Sent from my HTC Vision using XDA App

kholk said:
It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01
Click to expand...
Click to collapse
That is completely understandable, make sure you enjoy yourself. We can wait a little while in the backseat, but an updated kernel would be awesome . Just know that your efforts are appreciated. Thanks, and have fun!
thatruth132 said:
Can I test this kernel on gingerbread/cm7 builds
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Nandroid, and go for it . At it's current state I would expect a few things to be broken. Actually, gingerbread was designed to work with a .35 kernel so results might be favorable. The absolute worst thing that could happen is a bootloop, and you can fix that by flashing the stock kernel with adb. Let us know how it works.

Sounds cool..... stay safe
Sent from my HTC Nightmare G3

Bump for justice!
Do I need to build this to test on MIUI?
And can I OC to 1GHz with it? Or will I need to build one?
Or get someone else to build it

[KERNEL][12/17/10] Pershoot (v1.2) & Cyanogen (v1.3) Kernels for HTC Sense ROMs

Mod Edit: Redirect Removed

Reserved in case it's needed at some point.

Thank you for your work! Its greatly appreciated !
Sent from my HTC Vision using XDA App

I have the pershoot v1.2 running on euro DZ with stock sense since yesterday.
I can confirm : no issues whatsoever.
WiFi, bluetooth, FM-radio, GPS, Overclocking to > 1.5GHz all working perfect.

Are these kernels compatible with the US T-mobile G2 Stock ROM? Sorry i just need to clear it out of my way. thank you

Which kernel is included with the Virtuous 0.8 by default?

sonofabit said:
Which kernel is included with the Virtuous 0.8 by default?
Click to expand...
Click to collapse
G2 / Vision Changlog
1. Version 0.8.0
4. Default kernel switched to Pershoot (based off latest sources from 12/13/2010). (Thanks: Pershoot, Cyanogen Project).
Click to expand...
Click to collapse
thanks for the hard work!

rmk40 said:
So if you like the kernels and are planning to donate, please make sure you donate to them and not us. The work we've done and continue to do to assure Sense/HTC compatibility is minuscule in comparison to the upstream work by the actual maintainers.
Click to expand...
Click to collapse
I don't use Sense myself, but I think it's important that the Virtuous team is recognized for all THEIR hardwork. As humble as you are in your post, you & your team deserve recognition for your efforts too.
Your contributions are definitely not without merit and appreciated by many, many people. You guys are important in your own way for making the community (G2/DZ & beyond) what it is, so thank YOU for your hard work.

BlueTooth won't turn on for G2 Stock ROM with both Pershoot and Cyanogen Kernels
Thanks for the work though.

androidtoy09 said:
Are these kernels compatible with the US T-mobile G2 Stock ROM? Sorry i just need to clear it out of my way. thank you
Click to expand...
Click to collapse
No. Just Htc sense-based roms.

Oh wow, thank you so much for this.
Gonna send a donation your way.

PanCubano said:
No. Just Htc sense-based roms.
Click to expand...
Click to collapse
oooh man, that's too bad. So, no love for Stock G2 Rom than. Oh wel,, I might as well wait for Bingerbread.

androidtoy09 said:
oooh man, that's too bad. So, no love for Stock G2 Rom than. Oh wel,, I might as well wait for Bingerbread.
Click to expand...
Click to collapse
Deleting my post. I believe the ramdisk needs to be different.

Hi.
Excuse my ignorance, but trying to find out how to update stock kernel to this.
Tried searching, but rather new to Android and there seems to be a lot of varuois advise.
Am I to understand that all I need to do is download for example the pershot kernel, put it on my SD and make a fastboot update? Since it contains a "boot.img"
Or is ADB involved?
Simply put, how would I upgrade my "old" stock kernel?
And before upgrading, how would I go ahead and backup my old. Nandroid?
Thanks for your time.

If your sig is current, then your first step should be to S-Off. Check one of the stickies.
Then the easiest way to go about updating the Kernel/doing a backup would be to grab Rom Manager off the Market and flashing ClockworkMod.

Thanks alot for the kernals everything works on desire z fine fm radio etc..
the only problem i am having is the phone freezes if i set the max fre over 1094 mhz on set cpu it allows over clocking to over 1400 mhz right? well i am a proper noob though so maybe i am doing something wrong? i need to change a setting perhaps? or maybe this kernal is not for overclocking ?
thanks
or maybe i am just unlucky and 1094 mhz is the max my phones cpu can handle since every cpu is unique?

Random black-screen on wake-up
Tried both 1.2 and 1.3, same problem.
The issue is: When I wake up my phone from sleeping( either using Power Button or D-Pad), I have random chance to get a black screen. It's special, unlike those "freeze black-screen", the "home,MENU,Back,Search" buttons below the screen light up normally,open the keyboard and the backlight will turn on too ,but not the screen, it just remain black.
When I press the PowerButton again, the screen light up for about 0.1s (I can see the lock screen) then back to sleep.
Sometimes I have to press the Powerbutton several times get the screen on. but sometimes it works just fine.
I have no problem with the "Unmodified kernel" from ROM Manager, but when using these two kernels, it happens again.
Is there any solution or similar case?

Just installed the CM kernel on my DZ with stock sense rom. Everything seems to work perfectly. Setcpu works great with it. I can OC to 1.5ghz with small steps.

What are the difference in between the kernels??
Using 1.3 atm and no problems at all whatsoever. However I would like to know the differences in between kernels. Does anyone know?
Thanks in advance
Sent from my HTC Vision using XDA App

I can confirm this black screen on wake up as reported by jzhyok while I am test running right now the CM 1.3 kernel on my german DZ with unmodified Sense ROM, perm root, s-off.
I used setcpu with 1.5ghz and 1.2ghz with same results, just in case this could make a difference.
One more thing. My DZ instantly froze when I changed the governor from on demand to smartass in setcpu while I was at 1.5ghz with this CM 1.3 kernel, so I removed battery and now stay with the on demand governor.
Any fix for this anoying black screen wake up problem and any hint for the smartass governor? Which governor would be better, on demand or smartass?
Sent from my HTC Vision using XDA App

[ROM][VISION][11/8/11] HoneySenseHD Port 2.0 ---STABLE---

This is the HoneySense ROM ported from the desireHD to the desireZ! i like it, its fast, and looks elegant. What cuts it apart from the others, is the speed of a sense 2.1 rom, the versatility of sense 3, and the slickness of honeycomb. This uses virtuous OC daemon, so if you install setCPU or any other overclock app, it will disable.
How to install
(OPTIONAL) NANDROID BACKUP
(optional, RECOMMENDED! Some of the updates wont work if you dont) 1.Wipe EVERYTHING
2.install the ROM ZIP in clockworkmod
ROM Download 1.1 : ( http://www.megaupload.com/?d=IXM84O1M )
2.0 : http://www.megaupload.com/?d=PA4NVZQ0
Click to expand...
Click to collapse
Android 2.3.3 (Gingerbread) - OFFICIAL HTC RUU 2.50.405.2 (RELEASED 3.7.11)
Honeycomb themed
Brain **** CPU Scheduler as default (CFS optional)
VR I/O Scheduler as default (Deadline, Noop, SIO, BFQ V2.1 & CFQ Optional)
OpenVPN - CIFS - UTF8 - - EXT3 - EXT4 - JDB2
Audio boosts - 10% all outputs, 15% External speaker
WiFi Driver improvements & greater range
Rooted and Superuser added
Unsecured boot.img
Various tweaks for speed improvements
Battery calibration script (Thanks to the dev seo)
Multilingual ROM as all WWE are
Zipaligned @ system/app and data/app on boot
Fully de-odexed
init.d scripts (BusyBox run-parts) support
NANO text editor & sysro/sysrw commands support
EXT 4 VERSION
EXT 3 VERSION - for you non adventurous types (Coming soon)
Improved battery life, imagine a newer car vs the older car.. (Older car being STOCK ROM)
Includes support for customization and flash 2.50 mods ONLY over this release
Arabic and hebrew support find them in the addons section!
Click to expand...
Click to collapse
IF YOUR WIFI DOES NOT WORK, FLASH THE UNITY V4 KERNEL ONTOP OF THIS. Here is the LINK !
Anything with a V infront of it (V1, V2, V2873924 etc) is an RC, so V1 is RC1. Anything without a V is not an RC.
THE DESIRE Z HBOOT IS REQUIRED!
Read the tutorial at http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html to migrate to it.
Alternative Way to install Desire Z HBOOT
1. Download the PC10IMG.zip from the link above
2. Place it on the root of your SD
3. Boot into Bootloader
4. Choose the appropriate options
5. Remove the PC10IMG from the root, or else you cant boot into clockwork mod.
BTW, THIS ALSO CHANGES THE RADIO, SO YOU WILL HAVE TO FLASH A DIFFERENT RADIO
Thanks to
Adamholden85 For help with swype and the theme
Killersloth for the swype release and his Undervolt script, cheers pal
Seo for sense 3.0 for 2.1 and for help
Leedroid for the kernel + inspire 4g patch
Mike1986 for EXT4 Help and O/C Daemon help
Krzysiec for help and links
Cappy & Co for bringing half of this to us
Leith51 for inspiration and the help
Major thanks to he_stheone64 for all the help and the theme.
andyharney for the ftp and helping me with CM7 theme
Click to expand...
Click to collapse
Also, a special thanks to bsbokc, as without him, i would not know how to do this!
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE OR ANYTHING LIKE THAT
The Function XYZ is missing from this ROM.
Well, this is a PORT of a DHD rom, so they have the same features. it will only be added if its in the real HoneySense from DHD, or if its an optimisation, or something small, i may add it though.
Click to expand...
Click to collapse

CHANGELOG:
1.1: 29/7/11
removed gmail (install from market!!!)
fixed settings (showing as desire hd, showing incorrect ram, wrong MPX etc)
removed magicsmoke wallpapers
added keyboard without arrows
Friendstream widget added back in
1.0: 28/7/11
NO LONGER RC!
deleted stocks
updated adobe reader
FIXED WIFI!!!
now uses RMK's kernel (can install unity over it)
added DSP Manager
Removed: fmradio widget, friendstream widget, Twitter 3d widget
deleted facebook.apk (install facebook from market!)
deleted flickr.apk (install flickr from market!)
RC2: Speed improvements, included gingerbread ghostly so sms dont get lost (just incase), trackpad wake enabled - 27/7/11

if you are experiencing frequent freezes, it may be because your CPU is overclocked too high. flash http://www.megaupload.com/?d=A5ASHRM4 to stop it.
wifi calling patch: (I HAVE NOT TESTED IT, AS I AM AN O2 UK CUSTOMER SO IDK IF IT WORKS)
http://www.megaupload.com/?d=PIZNZ6O9
if apps are being killed frequently, it is due to gingerbread's aggressive RAM system. to make it better, use this guide http://forum.xda-developers.com/showthread.php?t=1126940
if MMS messages are too small, apply this fix (thanks to RMK!!!) http://www.megaupload.com/?d=YICSXR5W

what 3.0 sense features are included?
It looks fantastic!!

kowal_001 said:
what 3.0 sense features are included?
It looks fantastic!!
Click to expand...
Click to collapse
It's a complete sense 3 rom, but its not slow. it may be slow first, but give it time to settle in, and it will speed up plus in the next version i will make corrections to make it faster, and create a patch to remove the CRT animations, as they cause an orange led bug to occur.

Very nice and congrats can't wait to try it.

Just when I thought I found a rom I wont have to leave for a while..sigh..dammit..well, fueling my flashaholicness even further
Sent from my Synergy Rom using XDA App

Galery 3d ( sense 3.0 )included?

Good to see new dev added to the list of talented devs for DZ, and this is a time of sense 3.0 Roms rather than 2.1, guys welcome this new developer

is ext 4 recomended for a class 2 card or should i just not bother?

Happy to see another dev here. Excited to see what you can do!

slapshot30 said:
Happy to see another dev here. Excited to see what you can do!
Click to expand...
Click to collapse
+1
Sent from my HTC Vision using XDA App

master.peterm said:
is ext 4 recomended for a class 2 card or should i just not bother?
Click to expand...
Click to collapse
I believe ext4 requires at minimum class4 sd cards and up
Sent from my HTC Desire Z using XDA Premium App

Hi there, thanks for posting up this supposed teaser. A couple things:
A: What exactly about this rom sets it apart from the plethora of other Sense3.0 ports to the DesireZ/G2.
B: You posted 5 completely identical screen shots of the exact same four screens, all of whom were undersized and difficult to see. Considering that this is a step up from the usual zero screen shots I can see why you felt that somehow more=better but let me assure you we would all be better off that if we could actually see one set of four, this would make me happier than punched beets.
C: There is a thread naming scheme in place to prevent confusion, is there any way you can edit your OP to reflect this? (On second look it seems you just forgot the date)
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!

astriaos said:
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!
Click to expand...
Click to collapse
+1
Sent from my HTC Vision using XDA App

On one hand, I appreciate the positive vibes. On the other, you're contributing to the overall gentrification and stupidity of this forum so I am torn between if I want to set you on fire for being an intentionally obtuse ****, of trying to buy you a beer via the internet.

astriaos said:
Hi there, thanks for posting up this supposed teaser. A couple things:
A: What exactly about this rom sets it apart from the plethora of other Sense3.0 ports to the DesireZ/G2.
B: You posted 5 completely identical screen shots of the exact same four screens, all of whom were undersized and difficult to see. Considering that this is a step up from the usual zero screen shots I can see why you felt that somehow more=better but let me assure you we would all be better off that if we could actually see one set of four, this would make me happier than punched beets.
C: There is a thread naming scheme in place to prevent confusion, is there any way you can edit your OP to reflect this? (On second look it seems you just forgot the date)
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!
Click to expand...
Click to collapse
dude are you serious? Make or port a rom and make perfect to your standards....
Sent from my HTC Desire Z using XDA Premium App

Yes I am perfectly serious. We have thread naming standards for a reason. He posted a ton of the same screens, they're undersized and hard to see. He also didn't really say what puts him apart from the rest. I fail to see the issue here.
I'm certainly not denigrating his work or the amount of time he put into its development. I believe all of these are valid questions. Why you gotta hate the fact that I'm not immediately sucking **** over a rom that hasn't even been put up for download yet?
PS: It's people like you that make me want to set fire to the internet. Go soak your head.
Edit: Now, shall we all grow up a bit and let the OP address my questions or shall we continue this pointless derail until one or the both of us gets banned, OR the mods decide to "delete offending material" which may or may not include perfectly legitimate questions.

astriaos said:
Hi there, thanks for posting up this supposed teaser. A couple things:
A: What exactly about this rom sets it apart from the plethora of other Sense3.0 ports to the DesireZ/G2.
B: You posted 5 completely identical screen shots of the exact same four screens, all of whom were undersized and difficult to see. Considering that this is a step up from the usual zero screen shots I can see why you felt that somehow more=better but let me assure you we would all be better off that if we could actually see one set of four, this would make me happier than punched beets.
C: There is a thread naming scheme in place to prevent confusion, is there any way you can edit your OP to reflect this? (On second look it seems you just forgot the date)
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!
Click to expand...
Click to collapse
A:what sets it apart is the look, it gives it a classic honeycomb look, whilst maintaining the functionality of sense 3
B: I have resolved this issue.
C: i will have a look on the naming scheme, and change it accordingly. Thanks.
BTW, im 15, in the UK, but i dont have all day to bugtest
THE ROM IS UP!!! ENJOY!!! REMEMBER TO REPORT ANY BUGS

HURRY UP! I HAVE WORK IN THE MORNING! In Arizona (US) and its 1:04 AM haha ;-)
Sent from my Synergy Rom using XDA App

[KERNEL][AOSP-3.0.y][AXDEV] Generator - 10/21/13

{
"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

[KERNEL] | WildKernel v013 | Featurlicous | Tame Companion | January 29th

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