yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] findthesky:
Oh no, I have the same ROM and kernel! To be fair, first I had the nightlies version of CM11, then I tried to switch to CM 12 to get mic function back (it didn't work), then I woke up this morning to the updated kernel for [MENTION=4800121]Sultanxda[/MENTION] 's CM 11, so I switched to that.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] raptorddd:
Can you do whats app calls?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] findthesky:
Edit: I used to have Philz recovery, but then switched to TWRP for CM12, then realized that all the links to get a version of Philz's again were dead, so I installed the ROM using TWRP, assuming it wouldn't make a difference after reading some comments in this forum.

Should I flash the Philz recovery, and try again? (And if so, does anyone still have the md5?)

Edit2: Yes, Whatsapp calls work for me, but I can't see pictures sent.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
im using twrp 2.8.6.0 no issues.

heres an attached philz if u like to try it. i'll also add it to the 1stop as i didnt know philz links were dead
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] findthesky:
Thank you! I'll try it out, and let you know how it goes (this may take a while, not sure if I can install this recovery in Odin, so I'm assuming I have to put it on the external SD and get TWRP to install it, but I'll figure it out
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
yes in twrp just flash it - thats the preferred way, either int or ext sdcard,
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] findthesky:
Yeah, switching from TWRP to Philz had no effect, I still have the same problem with Camera and Gallery (additionally, I can still access my external SD using File Manager)

This was my process: Enter TWRP>>flash philz>>reboot>>enter philz>>wipe /data>>wipe /cache>>wipe dalvik>>flash customROM>>flash pg-gapps>>flash new kernel>>reboot

Edit 2: I don't know exactly what this means, but I tried a clean wipe again, and noticed these 2 lines:

"Formatting /sd-ext

E: unknown volume for path [/sd-ext]"

I have no idea what this means, or how to fix it. Should I format sdcard0? If so, what format should I use?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ocd_amp:
I tested the Camera thoroughly throughout the day today and have no issues. I am also using TWRP and have had absolutely no issues. Hope that helps at all. In your case, you may need to wipe and flash your ROM again, but first try Uninstalling the Camera app data/cache and wipe Dalvik. Do this for Gallery and Quickpic if you have those also.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] findthesky:
How do I uninstall stock apps? Do you mean to disable them?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] findthesky:
Update: I solved the problem! After re-reading the steps I took to flash CM 12, I noticed the only step I hadn't reversed was the part where I re-formatted the internal SD to ext4. I re-formatted the internalSD to exFAT, and while that bit of code still shows up ("E: unknown volume for path [/sd-ext]"), everything (VoIP calls, Camera, Video, Gallery, etc.) appears to be in working order.

Thanks again to everyone who helped me with this!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Plague_Bearer:
my phone keeps restarting during the setup process around the same time everytime, just passed choosing a wifi connection, then goes into a boot loop :/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Plague_Bearer:
flashed back to my previous cm-11-20150115-Sultan-skyrocket.zip

and everything is fine :l
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skynex7337:
Does anyone else have unlock lag on this ROM?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
What does the kernel log say?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
I didn't look at kmsg, figured I was already behind your current build and should catch up first so I'm not reporting on old builds. It's loaded now, waiting for it to occur.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
Running beautifully so far. You are the man as always sultan.

Not that this is much feedback, but for me with the screen glitches, I experienced them very rarely. When they did occur, a simple screen off and on seemed to fix it. No glitches yet so far though.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
Today's build has the most screen glitches of them all. Kmsg has this repeatedly while it's occurring. The larger the app in memory, the worse it becomes. For instance, if I open a very large email in gmail, and press power to screen off, when I power to screen on then the phone goes glitch crazy and its almost impossible to unlock it or navigate at all once its unlocked. Conversely, if I leave it on the home screen, it often will have no glitches when unlocking.

<4>[ 3412.484405] ------------[ cut here ]------------
<4>[ 3412.484497] WARNING: at /home/sultan/cm11.0/kernel/samsung/skyrocket/drivers/gpu/ion/ion.c:750 ion_unmap_iommu+0xb8/0xe0()
<4>[ 3412.484680] ion_unmap_iommu: (2,2) was never mapped for c268ac60
<4>[ 3412.484832] Modules linked in: dhd vibrator
<4>[ 3412.485137] [<c004e5ac>] (unwind_backtrace+0x0/0xf8) from [<c00bc9d4>] (warn_slowpath_common+0x4c/0x64)
<4>[ 3412.485290] [<c00bc9d4>] (warn_slowpath_common+0x4c/0x64) from [<c00bca80>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 3412.485473] [<c00bca80>] (warn_slowpath_fmt+0x30/0x40) from [<c02b5038>] (ion_unmap_iommu+0xb8/0xe0)<4>[ 3412.485565] [<c02b5038>] (ion_unmap_iommu+0xb8/0xe0) from [<c025809c>] (mdp4_overlay_iommu_unmap_freelist+0x7c/0xd4)
<4>[ 3412.485748] [<c025809c>] (mdp4_overlay_iommu_unmap_freelist+0x7c/0xd4) from [<c025d600>] (mdp4_lcdc_pipe_commit+0x188/0x370)
<4>[ 3412.485931] [<c025d600>] (mdp4_lcdc_pipe_commit+0x188/0x370) from [<c025cd0c>] (mdp4_overlay_commit+0x90/0xac)
<4>[ 3412.486114] [<c025cd0c>] (mdp4_overlay_commit+0x90/0xac) from [<c024f17c>] (msm_fb_commit_thread+0x84/0x420)
<4>[ 3412.486297] [<c024f17c>] (msm_fb_commit_thread+0x84/0x420) from [<c00d6408>] (kthread+0x80/0x88)
<4>[ 3412.486450] [<c00d6408>] (kthread+0x80/0x88) from [<c0049960>] (kernel_thread_exit+0x0/0x8)
<4>[ 3412.486602] ---[ end trace 2025d21d03a778ca ]---
<4>[ 3412.501403] ------------[ cut here ]------------
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Just a note that it can be temporarily bypassed by disabling hw overlays in developer options until it gets figured out. I have an init.d script that can do this at boot. If your interested I can post a link to it ;)

That will make the ui slightly more sluggish, but there will be no glitches and will not lead to a random reboot ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
Thats good to know. For a portion of the day I can't risk the screen glitches or any bugs for that matter interfering with work so I have been restoring my workhorse AOKP 4.3.1 instance and then return to various KitKat builds afterward to continue troubleshooting, this ROM being the most used. Swapping so frequently really highlights the performance improvement in KitKat over JB. These are just soo close to being as stable, each flavor having just a few minor hurdles to overcome with each approach.

---------- Post added at 07:32 PM ---------- Previous post was at 06:35 PM ----------

BTW, thanks for this. You made be blurt out laughing at an awkward moment with the family on Mothers day. It ended up being a good tension breaker!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
If you want to have hw overlays to be disabled automatically at boot, just put the following file in your /system/etc/init.d directory and give it the same permissions as the other files in that directory. Now when you reboot the phone, hw overlays will be disabled automatically ;)

http://www.androidfilehost.com/?fid=23486521113837637
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] burgeswe:
Thank you! Has anyone else had their hw overlays turning back on, even with this in place and configured? Mine keeps unchecking in dev options and starts glitching
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
I just tried to download my file and for some reason it downloads with .bin appended to the end of the filename. If that was the case for you, try renaming it to remove the appended .bin
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] burgeswe:
That was it. So obvious I totally looked over it. Thank you so much!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Np, always glad to help ;) I only just noticed that the download occurs that way ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] uchechris:
Just curious, does this rom work effectively on the hercules?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
[MENTION=2560027]SoCalHTCFuze[/MENTION]

Attached a new kernel to the bottom of this post. Changes:

Synced all references to iommu in the framebuffer drivers to CAF kk_2.7_rb1.38

Glitches should *hopefully* be gone now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
[MENTION=4800121]Sultanxda[/MENTION] Sitting dead center of 4 different SoCal Fires at the moment. But I'm all over this tonight when the fires die down and i don't need my phone.

Until then... Here is a firenado!

http://youtu.be/xUTFsBhKLBU

And how to put it out.

http://youtu.be/V6JoEG-sNMY
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Freaking California weather :mad: People living in other states always say that the weather in California is nice; IT AIN'T!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
For those of you crazy about battery life, I've got an interesting kernel for you attached to the bottom of this post. In this kernel I have added the option to undervolt the display by up to 500mV. I've set the default amount of undervolt for the display to 300mV; if you're crazy about battery life then try undervolting by 400mV or 500mV and tell me if you see a difference in your battery life.

This kernel also comes in an Aroma installer package for easy configuration.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] MadnessG:
Is there any difference between this kernel and the kernel posted on post #96? Besides the undervolt of the display?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Nope, the only difference is display undervolt.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
I know this is not what you were hoping but the glitches remain, kmsg follows

<4>[ 3143.147399] ------------[ cut here ]------------
<4>[ 3143.147583] WARNING: at drivers/gpu/ion/ion.c:750 ion_unmap_iommu+0xb8/0xe0()
<4>[ 3143.147674] ion_unmap_iommu: (2,2) was never mapped for db20c060
<4>[ 3143.147827] Modules linked in: dhd vibrator
<4>[ 3143.148132] [<c004e5ac>] (unwind_backtrace+0x0/0xf8) from [<c00bc9d4>] (warn_slowpath_common+0x4c/0x64)
<4>[ 3143.148315] [<c00bc9d4>] (warn_slowpath_common+0x4c/0x64) from [<c00bca80>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 3143.148468] [<c00bca80>] (warn_slowpath_fmt+0x30/0x40) from [<c02b521c>] (ion_unmap_iommu+0xb8/0xe0)
<4>[ 3143.148651] [<c02b521c>] (ion_unmap_iommu+0xb8/0xe0) from [<c0258330>] (mdp4_overlay_iommu_unmap_freelist+0x7c/0xd4)
<4>[ 3143.148834] [<c0258330>] (mdp4_overlay_iommu_unmap_freelist+0x7c/0xd4) from [<c025d804>] (mdp4_lcdc_pipe_commit+0x188/0x370)
<4>[ 3143.149017] [<c025d804>] (mdp4_lcdc_pipe_commit+0x188/0x370) from [<c025cf90>] (mdp4_overlay_commit+0x90/0xac)
<4>[ 3143.149200] [<c025cf90>] (mdp4_overlay_commit+0x90/0xac) from [<c024f17c>] (msm_fb_commit_thread+0x84/0x420)
<4>[ 3143.149383] [<c024f17c>] (msm_fb_commit_thread+0x84/0x420) from [<c00d6408>] (kthread+0x80/0x88)
<4>[ 3143.149536] [<c00d6408>] (kthread+0x80/0x88) from [<c0049960>] (kernel_thread_exit+0x0/0x8)
<4>[ 3143.149688] ---[ end trace 0cd62fb71d81fcdb ]---

The above was after several reboots and came about on its own. Now after a reboot, I'm having a hard time recreating it. Prior to this kernel I could just open some big apps and it would begin. Now it seems it will not happen no matter how many apps are open or how big they are until after a period of time has passed with a lot of usage... so I'm not really sure what could be contributing to it.

---------- Post added at 04:19 AM ---------- Previous post was at 03:53 AM ----------

Ok, so what seems to be triggering it now is when it is allowed to screen off on its own, and sit for a few minutes, then waking it causes the glitching to begin. This seems a lot like a buffer issue, maybe a allocation mismatch or corruption.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Gahhhhh TIME FOR DIRTY HAX
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Try the kernel I've attached to the bottom of this post.

EDIT: I got glitches with this one...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Here's a screenshot of the error messages I get after the latest commit to skip unmaping ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
I haven't been able to reproduce any glitches with this one, so far its been solid. I too get the log lines:

<3>[37305.316467] ion_iommu_delayed_unmap: Virtual memory address leak in domain 2, partition 2

<3>[37308.583374] ion_iommu_delayed_unmap: Virtual memory address leak in domain 2, partition 2

But It doesn't seem to have any effect on usage.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Lol, it says there's a memory leak, but when ion_unmap_iommu is used, it says that memory for that domain was never mapped. I'll look into that when I get in front of my laptop later. Also need to see what's going on with the glitches I got on that kernel yesterday.

Titanic, are the glitches gone for you with that patch?

I feel like this problem is deeper than this... Going to investigate that as well.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
So I just had the glitches show back up. Same lines as above but this now shows as well.

[43565.474670] ion_carveout_allocate: heap sf has enough memory (3ab000) but the allocation of size 177000 still failed. Memory is probably fragmented.ld9040 start ld9040_disp_on - HW Rev: 13

.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Unfortunately the glitches are still there for me :(

What else could be causing this?

I should also mention I saw a log message about no bg_pipe at mixer 0. I'll have to check the log again for the calling function name but I wonder if that has anything to do with this?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Try this one
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
This seems better, but I can still get it to glitch while using the browser with the keyboard active and pulling the notification shade down all at the same time.

Pulling the notification shade down also results in a blackout of everything behind the shade. Not sure if that is related.

I also got the ion_carveout error in this log right before the stacktrace.

How do we disable iommu all together? Maybe that's what needs to happen?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xxboarderxx:
I'm not Android savvy. I know just enough to flash roms.

Tried the latest kernel and I can tell you that when lots of apps are open, I get glitches. When I close them all, no problems.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] obaz:
is the any way to use data tethering on this rom ?

(btw if you turn off gpu acceleration in dev settings - all glitches disappear)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] freestylejunki32:
Settings->more. Data tethering options are in there
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
I posted an init.d script to set this on boot to fix the glitches. Just make sure you remove the .bin extension from the filename after downloading, then place in your /system/etc/init.d dir with the same permissions as the other scripts in that directory.

http://xdaforums.com/showthread.php?p=52608621
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] obaz:
with last kernel I have no problems with gpu. but thanks anyway

---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------

I know where tethering options is. The problem is that tethering do not working.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
I can confirm that tethering doesn't work on the kernel. When you check the mark for WiFi hotspot, the hotspot doesn't appear on any of my devices.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xxboarderxx:
+1

Other than that, the ROM is fantastic.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
Just wondering if anyone can confirm that when using Titanics script all the glitches are gone. I mostly just don't want to go through and set it all up just to have them show up again.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xxboarderxx:
Confirmed. No glitches for days
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] MadnessG:
Seems like the bluetooth wakelocks are rearing its ugly head for me...anyone else still have this issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xxboarderxx:
Yes, that's why I switched to CM11 official.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Hmm I used Bluetooth drivers straight from CM though... Then I guess I'll use different Bluetooth drivers from my HTC Sensation kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
I'd love to give it a shot. Official cm has the bt wake lock issues as well. It's not too bad really but they are present.

Also any updated rom on the way?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
Bluetooth is supposed to cause wakelocks, but they aren't supposed to drain battery... Are you noticing significant battery drain with those wakelocks?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
Honestly not a whole lot. I mean with previous roms I've had better battery life due to Bluetooth deep sleeping better but on the other hand I hardly drop a connection with this one. I don't notice a significant drain but I suppose it could be better.

It's 50/50 really. Could be better but not a big issue...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] MadnessG:
Unfortunately for me, yes. There is SIGNIFICANT battery drain. Went from 50% to dead in a matter of 2 hours. Nothing else was on.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
New kernel, v1.1.0, attached to the bottom of this post. After 2 months of hard work and banging my head against the wall, I have successfully backported newer CAF KitKat framebuffer drivers. Seems like the glitches are still there though... Well, let's see how it works for others.

Full v1.1.0 kernel changelog:

Backported newer framebuffer drivers from CAF kk_2.7-stable

Smoother graphics due to the framebuffer driver upgrade

Updated GPU drivers from CAF kk_2.7-stable

Increased Ion SF heap size by 7MB

Userspace has 863MB of RAM
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Great Job! I noticed some of your changes on gerrit. Does the official CM 11 nightlies have the newer drivers? If not, you should mention the Backported drivers to [MENTION=4359258]topprospect[/MENTION] so they can incorporate it in the nightlies! I bet they would appreciate it:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
No, my kernel now has the newest framebuffer drivers out of any other kernel. Not sure if I want to go through the trouble of proposing it to CM because I only made it work for the Skyrocket. I'd have to worry about making it work on all the other celox devices too if I were to propose it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
[MENTION=2560027]SoCalHTCFuze[/MENTION]

Could you test the kernel at the bottom of this post (v1.1.0B) and see if it still has the glitches?

EDIT: Nevermind, glitches came back :crying:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
[MENTION=2560027]SoCalHTCFuze[/MENTION]

I fixed the graphical glitches! Kernel v1.1.0C attached to the bottom of this post with the fix :D

Now that the graphical glitches are fixed, I'll update the ROM.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
Awesome. Does ondemand work? Or is it a cm issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
What CM issue? What does this have to do with Ondemand? : confused:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
Iunno I remember anytime I selected on demand the phone would reboot.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
That wasn't with my kernel. The default governor in my kernel is Ondemand. My kernel only has 3 governors: Powersave, Ondemand, and Performance.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
Sorry sult. My bad.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Yeah the rebooting issue must be something that other kernels haven't implemented as this kernel and CM's does not have this issue. I will admit since a few days ago I did have a RR, but nothing wrong with this kernel! Awesome job as always [MENTION=4800121]Sultanxda[/MENTION]!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
New ROM build uploaded with kernel v1.1.1 included, so no graphical glitches :victory: Also, I've added a download link for the kernel in the OP so if you want you can flash it on a different ROM (however, be warned: some ROMs have removed the mpdecision and thermald binaries, which my kernel uses for CPU core hotplugging and thermal management). Also, the kernel package in the OP comes with the Aroma installer, which you can use to configure the GPU's max frequency, CPU's max frequency, and display undervolt.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Krakozawr:
Is it possible to do dirty installation over the official CM?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] copene:
is Bluetooth any more stable in this release or still busted like all the other CM 4.4.x ROMS?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
That should be fine.

Right now I'm using Bluetooth drivers from the CM kernel and the Bluetooth configuration from CM as well, so I guess it is. Next thing I'm working on is Bluetooth.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] copene:
Thank you so much. If you can get a solid BT working for car connections you'll be a hero.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
You'll find out later today. I've already finished the Bluetooth driver upgrade in the kernel: https://github.com/sultanxda/sultan-kernel-skyrocket-pure/commits/cm-11.0
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
My Bluetooth has always been rock solid on this ROM. Never drops, connects when it should, no constant wakelocks, never have to reboot. I'd say its good to go
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Thunder22:
4.4.3 rom and kernel are outstanding. Thank you very much for your hard work.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sultanxda:
New build uploaded with the new Bluetooth drivers. As an experiment for the new drivers, I transferred a 215MB file through Bluetooth (while the screen was off) over a time span of 45 minutes and the battery only drained 3%. Also, with the new kernel (v1.2.0) I removed the hack that let it boot on other ROMs, so now it will only boot on my ROM or ROMs that are built using my kernel. The reason for this is because with the new Bluetooth changes my kernel is now more incompatible than ever with other ROMs. Anyway, let me know if your Bluetooth battery-drain woes are gone now :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Krakozawr:
Thank you for explanation :) is this procedure is standard (clean system etc) or maybe it is possible to just write over? :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xxboarderxx:
I've experienced glitchy lockscreen with the latest rom and kernel.

Didn't get a chance to pull logcat....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] _Jax_:
Well that sucks.

Downloading now. I guess we could flash Titanic's zip a few.pages back. Not ideal but it works.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xxboarderxx:
Other than that, it is snappy and a good dd. Unfortunately I have no clue about programming but I wonder if it is related to me lowering gpu clock.