yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] RukusX7:
That's odd behaviour. Is this with 100% stock settings? What governor and scheduler? Try any governor I've listed in the moderately conservative or the good battery with decent performance section. Pair with deadline for scheduler.

Give us as much information as you can or we can't help. I'd love to know why you're having such a terrible experience.

Did you follow the install directions properly? Is English a second language for yourself? I remember you asking if this ROM was for this phone and it's clearly listed in OP.
[Galaxy S II General] bijon440:
I wont say battery life is great, but its definitely comparable with most other builds. I'm around 14 hours to a charge. With moderate use of course. Using Samsung governor with row as a schedule. Operation is smooth but halo seems to slow it down a touch, but I like the feature.
[Galaxy S II General] manfromgta:
I recommend installing better battery stats to pinpoint the battery hog. There is a free version right here for xda members. (Link below) Also there are tons of guides to help reduce battery use on android phones. I do not believe the ROM itself is responsible for your battery drain. I am finding battery life acceptable for my daily use. Currently 15 hours with 38% remaining.

http://xdaforums.com/showthread.php?t=1179809

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] RukusX7:
To monitor battery usage and wake locks I use Gsam battery monitor.
[Galaxy S II General] RukusX7:
In settings under accessibility, there is a Greenify option for hibernating apps. Anyone not already running greenify or similar like to test that out? Possibly you [MENTION=5559120]sandhu6698[/MENTION]
[Galaxy S II General] sandhu6698:
i Tried On Demand/ Samsung/Conservative governors but not solved my problem.......but battery life in CM11 Rom is better...

can you please give me a flashable kernal zip of CM11 ROM ....want to try that kernal with this rom......because battery life in that Rom is really Great...
[Galaxy S II General] RukusX7:
No, sorry. I don't offer any other kernels at the moment. With that said, I don't know how the rom would behave without a custom kernel.

I wish i knew why your battery life is not up to par. Daily use is very subjective. Does your phone get any sleep time? or is it always on? is it going to deep sleep properly? do you run any apps that might be causing wakelocks? have you tried setting a governor and letting it "settle" for a day or so? try Samsung with ROW for more than a day or two. How is CM11 battery life better? in what aspect? on what governor? running what apps/ settings? Please give more detail.

It's unfortunate you are having such a terrible experience.
[Galaxy S II General] RukusX7:
I wonder why sweep2wake doesnt work and where I can modify that code...
[Galaxy S II General] titanic_fanatic:
Look through the commit history on github for the commit that added the feature and you'll see the exact code that was added.
[Galaxy S II General] RukusX7:
Haha thanks. :o
[Galaxy S II General] titanic_fanatic:
Try this commit:

https://github.com/Hellybean/androi...mit/bf74ad7b88fe6a7ef90cbd0e23c7dea9257effc7#

Edit:

Did you get my email with the files to replace for fixing the alignment of the qs tiles?
[Galaxy S II General] formercontra:
The highest frequency 1836 isn't stable for me, I can over clock all the way up to 1782 with no problems but 1836 causes the phone to reboot constantly. Undervolting is also working fine and stable.

And I don't know if everyone else knows this already, but art won't work if you have xposed installer. You can check the option, but it'll just reboot back into dalvik.
[Galaxy S II General] ThdDude:
Have you enabled it with trickster mod? by default its off

What fix? send a pull request of the changes please.

Every device is different some can oc to max without issue I always ran at 1728 I think it was and stable on my old Hercules. And yes Xposed does not support ART.
[Galaxy S II General] manfromgta:
I removed xposed framework from rom to get art functioning and it still reverts to dalvik. I realize xposed is included in ROM so not sure if uninstalling it actually gets rid of it.

Also noticed the kernel does not support bln feature. Better for battery but miss it. :).

ROM has been running strong for me since release. No RR or excessive lag and battery life is good. Running luzactive/row at default values. Quite acceptable. Good work guys!

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] RukusX7:
I tried enabling with Trickster MOD. I know the device is listening for input on the touch buttons. I modified sec_touchkey.kl and added WAKE_DROPPED after each line, the buttons respond to touch with the screen off. But I want the actual sweep left to right function, so the phone doesnt just turn on by a little touch in your pocket.

I havn't input any changes into the rom yet. titanic_fanatic sent me fix for the QS tiles. I havnt forked your work at all, because I am busy doing other things, but here is the fix. Thank you.

QS Tles Fix
[Galaxy S II General] RukusX7:
I'm not supporting the BLN feature in the kernel and ROM, sorry. I've just read that BLN causes way too much issues and a lot of CM-11/KK ROMS are not having it included. Though, itanic_fanatic does fantastik work on BLN in his ROMS, I haven't look into it further as battery life is better without as you said, and it just takes time that I don't have a lot of right now.

Thanks for the input on the daily use with the ROM! :) I am glad its working great for you. I find it get RR's and issues when I uncheck DIsable Hardware Overlays. So no one do that for now! I really like that governor/scheduler combination. Ive tried that one and Samsung governor so far. I like them both with ROW.
[Galaxy S II General] RukusX7:
Thanks. I was worried that undervolting and overclocking isn't working properly. I set a couple flags differently in the deconfig for the kernel that what the skyrocket and hercules called for.

For everyones referrence for the defconfig

CONFIG_SEC_DVFS_UNI is not set

CONFIG_SEC_DVFS_DUAL=y

The Skyrocket rocks UNI enabled and DUAL disabled.

By doing this, it appeared to me that voltage control was now enabled across both cores, instead of just one.
[Galaxy S II General] iDynamics:
I did something incredibly stupid. I flashed this rom on my device: http://xdaforums.com/showthread.php?t=2571133. I swapped the boot.img and the updater script and I've been running it for about an hour and a half. When it booted all I had to change was the dpi.

Please no one try what I did.
[Galaxy S II General] titanic_fanatic:
I can't believe the display is working??? We use entirely different drivers for that. Is everything working, like Wi-Fi, mobile, gps... how about your phone (calling out, receiving call), does that work?
[Galaxy S II General] iDynamics:
So far what is working: Wifi, SMS, calling out, receiving calls, and gps. I don't have a data plan so I can't try that.

I have tried only two builds and it has worked. Hellhat and Linaro by ThDude. Haven't tried any other builds yet.
[Galaxy S II General] iDynamics:
This isn't really proof. Anyone can edit the build.prop but I'll post it anyways.
[Galaxy S II General] ThdDude:
Stupid or Brave? Have a spare device lol?

Have you tried our BlueLightning? We are doing new builds of it tonight, Hercules users flash Skyrocket ROM's with I think only a rotation fix.
[Galaxy S II General] iDynamics:
More like stupid lol because my spare device is an Htc wildfire S which is absolutely horrible.

I will try your lightning build when it's up.

---------- Post added at 04:34 AM ---------- Previous post was at 04:01 AM ----------

I just flashed your latest lightning build. It is working. And Wow...It's really fast.

Edit 1: I'll be surely flashing your newest build when you upload it.
[Galaxy S II General] RukusX7:
BlueLightning is my next goal! In the past, i've done what iDyanmics has done with a skyrocket rom, but the DPI wasn't right and I wasnt able to make it look entirely correct or perfect. I am planning alternating BlueLightning and hellkat builds. But if all we need to do is swap out kernels..... [MENTION=2993366]ThdDude[/MENTION] please add my changes to support the UBER kernel. And we can start building Skyrocket ROMS???

[MENTION=4859152]titanic_fanatic[/MENTION] the reason everything works, is because they share the same video drivers. Adreno 220. But what the phones do not share entirely, is located in the kernel. the kernel stores all the information the phone needs to make EVERYTHING work. I forget where I read this, maybe it was faux123, but the kernel is like the engine and transmission, you're not going anywhere without it, and its basically what does all the work to make a car go. The body and seats, and buttons, and gauges are like the ROM, your interface to read and control the vehicle. :) Ive been researching to understand the difference entirely, and that is honestly how I came up with the kernel. I started to notice similarities and differences of things. I started to realize, that you can build almost any rom (aside from possible framework differences) for any device. titanic_fanatic has proven that to me with SlimKat, Paranoid Android, and CM11.

[MENTION=4887322]iDynamics[/MENTION] its not likely you will mess your phone up because of the wrong rom. Please someone correct me if i am wrong. But the worst Ive ever had was, things just didnt work right. Now, go ahead and flash an incorrect kernel, now you're playing with fire. But the warning doesnt stop there. Our phones share EXACTLY the same partition layout at the skyrocket and hercules. Even the Note 1. Now, flash a rom that is for say the Galaxy S 3 which has a different partition layout, you'll find dragons. I'm really excited that you found this out.

[MENTION=4859152]titanic_fanatic[/MENTION] Another thought. Ive been bothered that the vendor files for our phone perhaps aren't too different than the vendor files for the skyrocket or hercules and possibly a little more maintained (you are only one person after all) And perhaps, we've stumbled onto something really awesome here for our device. You've done so many changes based on the Skyrocket, its insanely awesome. :)
[Galaxy S II General] RukusX7:
[MENTION=4887322]iDynamics[/MENTION] so... does Sweep2wake work???
[Galaxy S II General] RukusX7:
[MENTION=2993366]ThdDude[/MENTION] is there any advantage to building your kernels with the rom? OR can we package it up like this if things work?
[Galaxy S II General] RukusX7:
[MENTION=4887322]iDynamics[/MENTION] You have no idea the awesome you just unleashed inside my brain.
[Galaxy S II General] iDynamics:
I'd like to report two issues I have noticed so far on the blue lightning rom.. I'm not sure if it is like this normally on the device it was made for or because I flashed it on our device.

1. I'm having some graphical glitches every so often. It usually happens when I wake up the screen. The right side of the screen flashes some green lines for literally half a second. I've also had the entire screen just go wonky twice so far when I returned to the home screen from closing down an app

2. When I reboot the phone, the screen brightness I have set doesn't stick. The brightness is at max when it first boots to the home screen.

No it doesn't work.

---------- Post added at 07:15 AM ---------- Previous post was at 07:11 AM ----------

Glad I was some assistance. :)

Edit: See the image attached.
[Galaxy S II General] titanic_fanatic:
The concern for me is hd display driver intended for our melfas display. The one used for the skyrocket is for a different vendor and I know from looking at the driver code that it's highly customized for each specific device which defines things like gpio's and other things like register locations and such. This is important for example to tell the display to turn on... a specific bit must be turned on for that to happen. Most will be generic values, but ours had some special values as well even when it comes to the Korean variant of our phone, there is specific code for that and the even use the same display. I don't think you would get optimal performance from your hardware by not using the drivers that are designed for it.

In regards to vendor files. Your welcome to play with them. I diff'd them against those of the skyrocket in many occasions and whenever I try to port any of it over, the phone won't boot. In the end I used the adreno package (for d2) in TheMuppets repo to update what was included with our device because those from the skyrocket caused no display. This is another reason why I'm so surprised that it worked, I've had so many difficulties with the display drivers on this device, but I think I got the right combo. If you're able to tweak it more that would be awesome.

EDIT:

Forgot to mention that building any rom is possible, however, if it is derived from cm then it's really easy. If it's based on aosp like the aospa (paranoid android) I'm trying to build, it's very difficult because aosp does not have the qcom hardware repos that we need. Allot of work is going into trying to get this to work and so far I've deleted my pa4.4 build to try the port again 5 times. I'm not exactly sure what needs to be ported so I'm talking a shot in the dark with a little bit of knowledge from following gerrit to get it working. No boot yet, just an android prompt and can't find any info on that.
[Galaxy S II General] RukusX7:
Oh! thanks! I hadnt realized that the drivers also appearing so similar are not. Thank you!! :)
[Galaxy S II General] RukusX7:
I'm working on a hellkat build with modified vendor files that follow the skyrocket and 4.4.2 kitkat Adreno drivers.

Wish me luck

Edit: Pushed the 4.4.2 drivers to my phone. Everything is working great. I should have an idea of a modified vendor file soon. Github confuses me still, so doing changes in my build directory..... I am starting to see the advantage of github. The Skyrocket forums have a great tutorial on rom and kernel building with github

Grab the new Adreno drivers here. driver install zip, located inside the zip. Flash just like a rom. Package already points properly to our system partition for flashing, I checked before i flashed, so don't worry. :)

User-mode driver binaries for Qualcomm’s Adreno 3xx GPU on Nexus 5 devices running Google Android 4.4.2 KitKat
[Galaxy S II General] iDynamics:
Going to flash. :)
[Galaxy S II General] RukusX7:
You're a flashoholic . :)
[Galaxy S II General] bijon440:
Wow. I am really impressed. Had to read everything twice to make sure I was in the right thread! Great that it worked for you iDynamics. Bit of a leap of faith with that "accident" hahaha. Flashing the new drivers now. Thanks muchly!
[Galaxy S II General] titanic_fanatic:
These are the adreno 300 drivers. Did you remove the old 200 drivers cause I'm not sure that it's using the 300 drivers. Some of the function calls to adreno are selected based on your adreno settings at build time and ours is adreno 200. Just putting the adreno 300 drivers there will not make the system use them.

Check your logcat to see the messages about the loaded version of adreno will tell you.
[Galaxy S II General] RukusX7:
Here is a screenshot of my logcat.

It appears to me that its using the mako Adreno drivers for JB? I installed 4.4.2 drivers for the hammerhead.

Maybe they aren't working. It doesnt look like I want to try and make them work anyway..... haha
[Galaxy S II General] titanic_fanatic:
Those are definitely the old drivers. Unfortunately, I don't think we can update to adreno 300 drivers since they are not intended for our gpu. Well, I suppose anything is possible but the work required to trick the kernel into thinking it has the right drivers might be more work than it's worth.

---------- Post added at 10:51 AM ---------- Previous post was at 10:48 AM ----------

@rukusx7 which app are you using to verify which governors are being used on which CPU?
[Galaxy S II General] RukusX7:
Android Tuner or Kernel Tuner. Do you want to run a different governor on the second CPU?
[Galaxy S II General] titanic_fanatic:
No, I just finished implementing some of the features of the diablo kernel into my titanium kernel such as the built in mpdecision and oc/UV. I just want a way to monitor all aspects of everything and I couldn't find an app that showed me the complete activity of the second cpu.
[Galaxy S II General] RukusX7:
Ahh got ya. A kernel built ground up for our device sounds like a great idea. :) You've more attention to detail than I can afford. :) Diablo was so convenient when I started to see the similarities!
[Galaxy S II General] RukusX7:
[MENTION=2993366]ThdDude[/MENTION] [MENTION=4859152]titanic_fanatic[/MENTION]

What makes a skyrocket similar to hercules? and what makes one more smilar to our phone?
[Galaxy S II General] titanic_fanatic:
Yeah, I'm cherry-picking what I need. And for some of the commits I had to manually add the code because there were two features in the commit and I only wanted one.

I'm running the new kernel now. Can't really say much because in just restoring all my stuff. Once that's done, I have to let it settle in and let the media scanner eat it's chunk of battery before I really get the results

---------- Post added at 11:33 AM ---------- Previous post was at 11:26 AM ----------

Mainly the board, and in or case, that's the msm8660. That defines everything like which kernel to use. Then there's the radios which are apparently the same or at least similar. The main differences are our screens and some sensors. Most of the drivers are the same. The proprietary binaries are however very different. They don't play nicely together.

My guess is that because it was supposed to be destined to become the att skyrocket hd, that the general design is almost identical to it's predecessor.
[Galaxy S II General] RukusX7:
[MENTION=4887322]iDynamics[/MENTION] Did everything fit properly? icons, text, etc... after you changed the DPI?? no blurry icons, etc?
[Galaxy S II General] iDynamics:
Everything looks fine. And my screen hasn't gone wonky for several hours like the image I attached. I'm not sure if this was the fix but I cleared my launchers data (nova) and started from scratch entering my settings, not to mention it also fixed the status bar lag on the home screen.

Every time I flash a new rom I restore my Nova backup that I made in 4.3.1, Maybe that caused issues?

Edit: Ah, almost forgot. Another issue to report.

I got several lines of graphical glitches when I first opened my browser. Happened a little while ago.
[Galaxy S II General] RukusX7:
I think thats an issue involving hardware overlays and the graphics drivers [MENTION=4859152]titanic_fanatic[/MENTION] mentioned maybe.

Anyway, here's a BlueLightning port I put together. Its my first, not perfect.

Edit: WiFi works. I used ART compatible gapps. Screen will go blank after the logo for sometime on first boot. Just be patient. Oh, sensors aren't working.

BlueLightning Folder

Further Edit: I took down the BlueLightning build. uploaded a hercules port of hellkat into the hellkat folder. I just happenned to have on my computer I was using for reference, so i used it. Everything works. Will upload a Blue Lightning one perhaps soon. [MENTION=4887322]iDynamics[/MENTION] credit goes to you.
[Galaxy S II General] titanic_fanatic:
This most likely due to the overlays as rukusx7 mentioned. Are you using my 91fixoverlays script? That may help with those glitches. I believe that is exactly why I included it with my cm11 rom in the first place. These graphical glitches will actually cause a kernel panic and reboot, at least in my rom that's how it happens, I'll turn the overlays back on and play with the notification shade a bit and get those lines while doing it, then all of a sudden... a reboot. This is what I'm trying to fix in my rom. I think when Steve finishes with our kernel these issues will be resolved.

For the blank screen, or no boot animation, this is most likely due to proprietary vendor files. There is some sort of incompatibility. This is what I got the first few months that I was trying to port cm10.1/cm10.2. I finally resolved the issue by updating two of the graphics driver files that I missed originally.

Try adding all of my vendor files in the correct places and with the same permissions as other files in those dirs. You will most likely want to do that with adb in recovery. Then boot up the phone and see if that helped

EDIT:

For the sensors, you need our sensors file in /system/lib/hw/sensors.default.so and camera is camera.msm8660.so

You won't be able to take any of the .ko modules because those are compiled specific to each kernel and will not load into a kernel they are not compiled with. It has to do with magic numbers.
[Galaxy S II General] RukusX7:
nothing worked because i ported the files over. But then i did only what iDynamics did (moved the boot,img), and everything works. properly. I dont even care if the files aren't "exactly right" at this point. As long as everything works as it should .And it does!
[Galaxy S II General] titanic_fanatic:
The boot image is the whole kernel and ramdisk, so you have all the drivers installed, you should also now take the modules from the kernel that your using and put those in /system/lib/modules. This will work better since those modules are compiled for the kernel your using and will actually load. Do you have vibration? That is a module, so if your vib is working then the modules are loaded and shouldn't need to swap the modules.
[Galaxy S II General] RukusX7:
I have not found one thing that doesn't work as expected. Users are welcome to test both my hellkat port and hellkat build. My apologies to hijack your idea to port [MENTION=4887322]iDynamics[/MENTION]. I have no problem maintaining this idea for you if you're not planning to yourself.
[Galaxy S II General] RukusX7:
The kernel was compiled inside the exact same hellkat build as the Hercules and skyrocket. Meaning, for any other purpose or phone, I would need to include the *.ko files. But they are included in the ROM already. I don't understand the innards completely, but the diablo kernel for this phone is 99% the same. Other than drivers and display. The *.ko modules should have no reason to be any different the way I see it....
[Galaxy S II General] iDynamics:
You didn't hijack anything :) Your work on the kernel is what made me think of this.
[Galaxy S II General] titanic_fanatic:
Check out this document on kernel module signing from Google

Kernel Module Signing

You can turn this feature off where the kernel doesn't check for the magic number before loading, but your defconfig doesn't have that option set, so I'm almost certain the modules aren't loading. Magic numbers are supposed to be build specific.
[Galaxy S II General] RukusX7:
I uploaded the wrong rom to my AFH, I'll be a moment getting the correct one.

I dont know why you think modules are not loading.... I'm holding my phone in my hand looking at everything work.

What do you mean by build specific?

What does this section mean?
[Galaxy S II General] titanic_fanatic:
I'm only trying to help. Even if it's "working" you can't guarantee that it's optimal that's all I'm saying.

EDIT:

By build specific I mean that the magic number is generated a

Each time you compile and the kernel is not supposed to load a module unless it's magic number matches. I even had this issue between cm11 builds when getting the device tree ready for the latest philz. I had to use the same modules or the vibrator.ko wouldn't load.

---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------

This I think is all taken care of in the build process for android. Allot of projects are downloaded and these gpg keys are most likely among one of those projects so you really don't need to deal with it since its already been accounted for in the build process.
[Galaxy S II General] RukusX7:
I've been too overzealous to get this work up so everyone can try it, but I think I got everything correct and the right file in place!

Upload coming soon.

I hope you continue to make awesome roms for us titanic_fanatic. You know your stuff and Ive learned a lot from you. :)