yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] 0.0:
Could this be added in? It's the miui style traffic indicator :)

https://github.com/CarbonDev/android_frameworks_base/commit/c061bc90cfd287e6119ab49d4d6467be9d2676a0

sent from my Nexus 4
[Nexus 4 Android Development] Der_Schubi:
No, I spent many hours in the last two weeks with fixing and approving the traffic meter. :D

Are there any screenshots available of this one?
[Nexus 4 Android Development] 0.0:
It can show both download and upload speeds. Screenshot attached

sent from my Nexus 4
[Nexus 4 Android Development] Der_Schubi:
Damn, looks nice... :D

Changelog:
[Nexus 4 Android Development] sidVici0us:
I'm using 20131016 build and I am getting some screen flickering, it's only me or anyone it's getting this issue?

This build uses cm default kernel if I want to use hells kernel I need to use hells cm kernel or jss hells kernel???

As always this the best rom!!!!
[Nexus 4 Android Development] hellsgod:
You're not alone mate. I think we forgot to revert something from the CAF stuff (or reverted too much?) I'll try to sort this out on the kernel site. And no, it's not the default cm kernel anymore. It has some "magic" from me :D

hells
[Nexus 4 Android Development] sidVici0us:
Ok mate, I love the magic :)

I'm keep waiting for a new kernel.
[Nexus 4 Android Development] hellsgod:
I hope the commit(s) are not as hard to find as it was with a problem in the beginning (192mhz made some problems, won't boot or rebootet with a kernel panic after a few minutes). I'll keep you updated :)

hells
[Nexus 4 Android Development] TheDarkDefender:
[MENTION=647113]hellsgod[/MENTION] I've been using your kernel for a long time and the screen on time has been very good. The only issue i have is that the idle drain is a bit too much. I use your default settings, and the phone rarely goes into deep sleep. I lose like 15-16% overnight. I have also checked my apps, they dont seem to be causing it. Could you please enlighten me about this?

Sent from my Nexus 4
[Nexus 4 Android Development] hellsgod:
Did you always had this problems? Because i'm loosing between 3 and 5% overnight. In my main board (the german one) there are also no reports about that. Soo... maybe you could sent me a BBS Log or something? Because something held your device awake. Whatever it is...

hells
[Nexus 4 Android Development] TheDarkDefender:
Yes. Im using the cm version of your kernel. I ll send you a log after the next charge cycle. Thanks :)

Sent from my Nexus 4
[Nexus 4 Android Development] hellsgod:
I think we have some dilemma here...

First problem: These strange flickers. They were also here, before CM merged all the CAF stuff. So now its a mess to find a way, to use the CM kernel as base, but without CAF stuff and without flickers. In the end its easier to take a normal JSS Base, I think. But i'm trying some things, before I'll do a rebase, again...

Second problem: Fence Timeouts - Also called "Deadlocks". If CM fixed them, wouldn't it be better to go back to the CM CAF base?

I don't want to spend too much time to find a good solution, if KitKat is around the corner. In the end you can't satisfy everyone. CK is a CM-based rom, so if you know that, you have to decide if you want to use it (because of the CAF stuff), or not. I will talk with Schubi today an we are trying to find a good solution. Yes, this CAF stuff is annoying, but these flickers are annoying, too. And don't forget about the Fence timeouts... So if you don't have flickers and you don't have deadlocks, then its crystal clear to use the CM CAF stuff in my opinion. Remember, thats only my thoughts and don't represent the whole team!

hells
[Nexus 4 Android Development] c@p:
Will you give it a try? Looks really good!

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Android Development] humba80:
Thanks for this awesome rom! But I got one little problem:

I use the standard sms app with the quick sms feature. When I get a sms and write a reply in the quick sms window, and then get another sms while writing, the text I wrote disappears. Anyone else with this problem? I asked this question in the CM forums, but nobody seemed to care... Hopefully someone here does, because it's really annoying when you write more then two words. Thanks!
[Nexus 4 Android Development] ermacwins:
Would it be possible to have both but one is disabled while the other is used?
[Nexus 4 Android Development] TheDarkDefender:
The concepts themselves are hard to implement together, is what i heard from one of the PA devs.

Sent from my Nexus 4
[Nexus 4 Android Development] Vaxbox:
Screen flicker still present in 1017? I'm on 1015 and everything seems fine... safe to update?
[Nexus 4 Android Development] c@p:
Yes, but you can update and / or flash the new CK Core from today, with this it should work without.

http://d-h.st/JMj

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Android Development] ak:
I dont know where is the problem with the way of CAF .... i havent had one deadlock, freeze with new cm kernel .... and i have 0.5% 1% drain overnight with official night rom.

I think this solution is better than google one ... but this is my opinion.
[Nexus 4 Android Development] sidVici0us:
I'm now using the latest build of hell's kernel for CyangKang and have not experienced any problems so far.

No flickering or deadlocks so far.

I think it would be best to stay close to the original code CM and try to help fix the bugs that occur as well apply patch to improve the performance that Schubi and hell's that we are accustomed.
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
THIS. If this is meant to be a kitchen sink ROM, then there are other ROMs out there (PAC?), but this is a CM base with a few sprinkled features in.
[Nexus 4 Android Development] Der_Schubi:
The problem with CAF is, that you can't use any custom kernel.
[Nexus 4 Android Development] ak:
What I meant was not referred to the possibility to use a custom kernel, but to the improvements introduced by commits in the cm kernel.
[Nexus 4 Android Development] Der_Schubi:
Thats right, its a good kernel. But the most users want to flash a different one.
[Nexus 4 Android Development] ak:
Yes ... true ... at this point what is the problem for a kernel develop to maintain a cm version?

I have see alot thread with 2 vers JWR and JSS.

I do not understand this war against the choice against the libraries caf.
[Nexus 4 Android Development] Der_Schubi:
I don't know why. The problem is, that such patches should be included by all ROMs or by none. I think thats the message of the kernel devs.
[Nexus 4 Android Development] hellsgod:
That's exactly what I think mate :) My hells-Core is JWR/JSS and CM and I will continue to develop all of them. I don't understand the "problem", either...

I needed some rest. Two nights without much sleep are enough :D Like sid and c@p said, I think I found a way without flickers. I'm picking a few Commits back and look, if the flickers returns. I hope with the next Nightly (not the 18th one) the problem is gone.

hells
[Nexus 4 Android Development] TheDarkDefender:
Hells, could you add otg support to your kernel? (Or is it already there :p )

Btw, hells caf is a great combination with cyan kang and crdroid. Great battery. :thumbup:

Sent from my Nexus 4
[Nexus 4 Android Development] hellsgod:
The problem with OTG in the first place is, that you need a modified ramdisk to get it work. My hells-Core comes without a ramdisk (anykernel). The CK kernel from me don't have it, either, because its up to finnq and Schubi to integrate the Changes in the ramdisk. They've done that in the past, but reverted it, because of some troubles with it. So... It's a difficult story...

hells
[Nexus 4 Android Development] macanovic88:
I hope that screen problem will get solved, but I can live with that because for me this is the best combination! Cyankang with Hells kernel!:thumbup:

man sent this using xda & n4
[Nexus 4 Android Development] hellsgod:
I've tested something yesterday, you can flash this one in the maintime: click It's the same one as in the Rom, but without these flickers. I'm not 100% sure there are no other side effects, because I had to revert some CM commits. So I need more feedback on this one. But remember, I don't know if it's 100% stable! Thats why I didn't push the changes.

hells
[Nexus 4 Android Development] macanovic88:
Flashed this, flickers are gone! :D So far everything works great! Thanks a lot hells for great work! :)

man sent this using xda & n4
[Nexus 4 Android Development] hellsgod:
Hey guys,

We made some changes in the last hour. There were some problems with thermald (which shouldn't be active) and I've merged the CM Deadlock fix in the kernel. The flicker fix is built in also :) You can try it out here: click Yes' it's the PDROID one, and there isn't one without, because it's a test build. It would be nice, if you flash it nevertheless, I need some feedback!

hells
[Nexus 4 Android Development] worstenbrood:
Flickering is gone, dunno bou the deadlock yet since i didn't find a reliable way to reproduce it (mostly happened to me when playing music and then locking the phone, which now doesn't happen offcourse :))

Great job team !
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
OP, have you looked into the slider unlock issues where you can drag the slider in between the targets? It looks weird and is definitely a bug.

Also the Slim camera you've included seems to have a messed up option for choosing picture size. The icon is for geolocation.
[Nexus 4 Android Development] ilikenwf:
Thanks for this rom! I'm using it and the JSS b40 hell's core, as it allows more tweaking and lower frequency (192mhz) for the kernel. I'm also undervolting...

I'm not super heavy on usage, but pdroid keeps a lot of apps from wasting power, and the undervolting with intellidemand helps a lot too!

Battery: http://imgur.com/a/Grx0d

My settings: http://imgur.com/a/N32Gi

Is that fix also in the standalone hell's core from here?

http://d-h.st/users/hellsgod/?fld_id=13048#files
[Nexus 4 Android Development] morganmf:
Ok guys, two questions. One. Where I can find screenshot option for power button menu?

Two. Which app you suggest for maintaining kernel options?

Sent from Nexus⁴ via Tapatalk⁴
[Nexus 4 Android Development] humba80:
System Settings -> Buttons -> Power Menu
[Nexus 4 Android Development] hellsgod:
hells-Core doesn't need that fix, because now you have to take the JSS one. This fix was needed, because we are still using the unified CM kernel, but without the CAF stuff. I've had to revert some more to get rid of these annoying flickers :)

hells
[Nexus 4 Android Development] worstenbrood:
Just had the deadlock on that build :/
[Nexus 4 Android Development] lmarranzino:
Getting confused here.(not a hard thing to do)...LOL

Will we be able to continue to use JSS kernels without issue or ?

Either-way for me at least. Hells your Kernels are GREAT and I have used the CM version, it is perfect on the new test build you have up.

Cyan and Hells are really a perfect, perfection match IMHO ...:cool:
[Nexus 4 Android Development] hellsgod:
Yes, the rom is reverted to JSS, so you can use any JSS kernel :)

hells
[Nexus 4 Android Development] ilikenwf:
Oh yeah...thanks!
[Nexus 4 Android Development] kenshinta:
I would like to use an init.d script to set halfbreed colors. How such a script look like?
[Nexus 4 Android Development] sidVici0us:
I'm having some problems with latest hells kernel ck b5 and default ck kernel on 16 17 18 and 19 builds, Wi-Fi work the first time but if I turn off I cannot turn on never again I have to reinstall a fresh Rom. Even restarting the phone Wi-Fi don't work only work if I wipe data and cache.

I have to revert to a 20131009 build to get it working properly.
[Nexus 4 Android Development] Der_Schubi:
[MENTION=4295962]sidVici0us[/MENTION], do you use the PDroid version? Did you some changes to its settings? Its possible to get even this behaviour with blocking the wrong thins.
[Nexus 4 Android Development] sidVici0us:
No I don't, I don't use pdroid version and never change anything in source or config.

I only configured the options in configs menu.

The problem starts when I flashed the hells ck kernel over 20131017 version. I made a some clean installs and every time I get this behavior.
[Nexus 4 Android Development] itsita:
Lost root access in the latest nightly... anything I can do?

Sent from my Nexus 4
[Nexus 4 Android Development] lmarranzino:
I also lost root , I tried to fix permissions thinking that may help, still nothing.

I just went ahead and flashed back to 10-18 build with no issue.

Also WIFI working fine on 10-18 at least here, I an using Hellscore b40-JSS-t11 build (prior I was using the t9 build) running great so far.
[Nexus 4 Android Development] kenshinta:
on 10-18 pdroid build;

A) ever since 9-28 build been experiencing lots od SystemUI.apk FCs, any tips on what to do?

B) noticed that Halo blacklisting isnt sticking at all. Is this already a reported issue? Any soultion atm or still being worked out?
[Nexus 4 Android Development] sidVici0us:
The Fc's of sistemUi.apk are fixed by wipe data / cache dalvikcache

I never use the Halo is the most ugly :)
[Nexus 4 Android Development] mondaza:
A question: this kernel built for you, is updating with ROM?

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Android Development] hellsgod:
Yep. It compiles always from the repo i'm pushing to.

hells
[Nexus 4 Android Development] worstenbrood:
Deadlock on 2210 :(
[Nexus 4 Android Development] kenshinta:
That's pretty basic 1st thing to do, and of course it does not work in this case - systemui fc still occur.

I previousl havent a way to reporduce the FC they do seem random but I now have a way to reproduce them. And it appears related to Active Display.

Active Display is active.

Installed Byte Insight from play store.

When screen is locked, byte insights give notification of data used, triggering Active Display.

Unlocking phone results in systemui FC, sometimes it restarts on its own, most of the time I need to show shutdown menu for it to restart.

Basically, Active Display seems to be at fault why I hope it gets fixed.

Hope HALO blacklight is being looked into.
[Nexus 4 Android Development] Mendanbar:
Battery Options color reset not working

Hey, I wasn't sure where to post bugs, but I've noticed that on recent builds the resetting of battery circle colors doesn't work. I'm not running the latest nightly (still on nightly from the 18th) but it was present at least 2 nightlies before that.
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
What I noticed is that the reception bars and the battery circle are super close to each other. It wasn't this way before. What happened?
[Nexus 4 Android Development] itsita:
Had that problem... only workaround I found was to clear "settings" data.

Sent from my Nexus 4
[Nexus 4 Android Development] Toobie:
I made a clean installation yesterday, directly after reboot i had fc the AOSP keyboard.

So I could type in any password oder anything... any idea?

---------- Post added at 09:45 PM ---------- Previous post was at 09:41 PM ----------

I made a clean installation yesterday, directly after reboot i had fc the AOSP keyboard.

So I could type in any password oder anything... any idea?
[Nexus 4 Android Development] sidVici0us:
Wrong version of gapps?
[Nexus 4 Android Development] Der_Schubi:
Sorry for letting you all hang here for a few days! :D

That was a patch by CM, its was fixed directly one Nightly later. 21th or something...

Sorry, no idea yet...

Active Display have problems with changing notifications. Such as GPS Status or something. Just exclude such apps from Active Display by adding them to the AD excludes list.

Thats an old one. Thanks. Still havent found whats wrong there. :D

Whooops. My fault! Sorry :D

Please use 4.3 Gapps. Keyboard of 4.2 Gapps will FC!
[Nexus 4 Android Development] Toobie:
Of course I used 4.3 Gapps!
[Nexus 4 Android Development] udjat:
I am having the same problem when I have to enter in my pin number to decode my sdcard
[Nexus 4 Android Development] Sblast:
Seems like the server is down
[Nexus 4 Android Development] lmarranzino:
It is a very easy mistake to make, You may want to try a new download and see.

Just be-careful if using OC kernels as if you benchmark test you may wind up with a Blacked out useless device (as I did just yesterday while messing around). Hells is by far one of the best out here...
[Nexus 4 Android Development] Der_Schubi:
Please download directly

http://erlangen.ccc.de/~schubi/roms/
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
Be wary Franco lovers. I think 1025 nightly breaks the phone and gives you an endless FC loop.

I'm not sure if his r193 kernel that just came out a few hours ago addresses this, but I'd advise a backup.
[Nexus 4 Android Development] 0.0:
will the ROM get MIUI status bar network indicators as an option in the future? it's from ChameleonOS

Add network usage stats to status bar. [1/2]

https://github.com/ChameleonOS/andr...mmit/03dd948b380a010a5b1edf698cdb0c5cf70dd094

Add network usage stats to status bar. [2/2]

https://github.com/ChameleonOS/andr...mmit/c1f135287fa177e517a237eb5b6e937e9c3a20b4

:)
[Nexus 4 Android Development] Der_Schubi:
I'll give it a try in the next days...
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
do you think you can fix the spacing between the network icon and the battery icon in the status bar, as well as the lockscreen targets for slider unlock responding to snap targets in between the targets?
[Nexus 4 Android Development] Der_Schubi:
The icon spacing is already fixed since 2 days. But I used the old value, 2dp instead of 4dp, what is the new CM value. May I also use 4dp...

Please explain a bit more, what you meant with the lockscreen targets. :D
[Nexus 4 Android Development] Der_Schubi:
I've ported it for testing, its running fine. But there is a lot of love needed to make this ready for daily use.

E.g. the text is always white instead of blue, it doesnt support lightsout mode, and so on.

So, give mo some days to work on it. ;)

It seems that I can integrate both, the old traffic meter and the new netstats parallel. :)

--Edit--

Yep, they are able to run parallel. So I'll integrate it. ;)
[Nexus 4 Android Development] Der_Schubi:
Changelog:
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
Here's a screenshot showing the lock screen targets being weird.
[Nexus 4 Android Development] Der_Schubi:
Whats wrong with the lock screen targets? It's meant to be that way!
[Nexus 4 Android Development] 0.0:
I tried to integrate openpdroid patches like how you told me in a PM, but it won't build with the patches :(. My previous post shows the possible output error

[MENTION=2825227]Der_Schubi[/MENTION] I talked to the openpdroid dev and he has commits that'll allow the ROM to work with openpdroid again, since it fails to work in the autopatcher. Here's a link for some info https://github.com/mateor/auto-patcher/issues/191

sent from my Nexus 4
[Nexus 4 Android Development] itsita:
Anybody gets random reboots on latest nightly? I'm traveling and not sure how and what log I should get.

Sent from my Nexus 4
[Nexus 4 Android Development] ilikenwf:
Thanks for the great rom! Still running that last pDroid build, I really hope you continue on into 4.4!
[Nexus 4 Android Development] Der_Schubi:
We try to do, but its still failing. This has to do with the multisim support which was integrated by CM on Oct. 22nd.
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
No I don't think you understand what Im describing. The lockscreen targets are supposed to snap to their correct positions. Right now in CyanKang, they will snap to halfway in between the two targets.You can try to slide it to the target, and then you can move your finger up/down and it will slide to halfway in between the targets.

That's a clear bug.

Edit:

CM 10.2 Nightly 31-OCT-2013: http://www.youtube.com/watch?v=0ckV_ksBUo8

CyanKang 10.2 Nightly 31-OCT-2013: http://www.youtube.com/watch?v=JqhKMWDVMXg
[Nexus 4 Android Development] Der_Schubi:
Again, thats meant to be that way!!!

The CM way is called magnetic targets. We're using the AOSP way.
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
Sorry, I have never seen the AOSP way, and I thought the interface to change the slider shortcuts in CyanKang is identical to CM, so I thought it would be CM.

If this is the way it's meant to be, that's fine, but would you be ok changing to the CM way? I just don't see how this appears to be the way even if it's meant to behave this way. It looks totally bugged from a UI perspective. I don't get why it should snap in between two targets. To me it just looks weird and broken.
[Nexus 4 Android Development] Der_Schubi:
This decision was made long ago. As CM decided to uimplement these magnetic targets, many users complained that lockscreen is broken. So we reverted this commit.

The problem with magnetic target is: Lets say define no targets, so only the unlock icon is on the right side. Then you unlock by swiping to the top or the left of the ring. The slider will jump away from under your finger to the right side of the ring. This looks broken, not?
[Nexus 4 Android Development] Malnilion:
Any chance you all will support hammerhead when CM 11.0 kicks off? CyanKang has been my go-to ROM for several months now and I'll be sad to see it end!
[Nexus 4 Android Development] Der_Schubi:
Sure! But CM still has no device tree for hammerhead. So we'll have to wait a bit. :D
[Nexus 4 Android Development] 0.0:
since CM just finished updating to 4.4, does that mean this ROM will see 4.4 soon? :D :fingers-crossed:
[Nexus 4 Android Development] Der_Schubi:
Yep, but we'll do a clean restart. :)
[Nexus 4 Android Development] ermacwins:
Meaning what exactly?
[Nexus 4 Android Development] 0.0:
Meaning he will start from scratch. I don't think it's possible to move over all the tweaks in this ROM. So instead of trying to make each one work when moving over, might as well start from the bottom and work there. Less of a hassle

sent from my Nexus 7
[Nexus 4 Android Development] Der_Schubi:
Exactly. :)

For example: Swipe down StatusBar is now integrated in Stock 4.4, so I know SystemUI would blow up during merge. :D
[Nexus 4 Android Development] :
Will you continue using CM as the base?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] Der_Schubi:
Yes!
[Nexus 4 Android Development] itsita:
Any chance to have one last nightly before kitkat? Need my flashing fix :D

Sent from my Nexus 4
[Nexus 4 Android Development] Der_Schubi:
We will continue 10.2 for a wile. CM11 is missing too much stuff in the moment. Anyways, wee need to fix the build bot. ;)
[Nexus 4 Android Development] Der_Schubi:
There is a new nightly up!

https://erlangen.ccc.de/~schubi/roms/CyanKang-10.2-20131110-NIGHTLY-mako.zip

Building with PDroid is still not working, so only without.
[Nexus 4 Android Development] cj360:
Google led me here looking for libqsap_sdk, I saw back on pg 33 you were having some issues with it, could you say how you ot past them?
[Nexus 4 Android Development] Der_Schubi:
[MENTION=4311888]cj360[/MENTION]: What are you talking about???
[Nexus 4 Android Development] cj360:
I was refering to this ^ but I belive is was something with the aosp qcom repos I was using.
[Nexus 4 Android Development] joeshmoe08:
How is the progress coming on 4.4 scratch build?
[Nexus 4 Android Development] Sblast:
CM11 is still taking time from what it seems. So patience ya habibi.
[Nexus 4 Android Development] c@p:
Next CK will based on Omni, work is still in progress. Let's get surprised.

Tapatalked by neXus⁴
[Nexus 4 Android Development] v3n3:
No need to rush.

The current build is running great and no 4.4 ROM has as many options as this does, so I dont have a problem with a little more waiting ;)
[Nexus 4 Android Development] azrash:
Does anyone know why the next one would be omni based? Just curious of the direction
[Nexus 4 Android Development] c@p:
Because CM & their CAF things.

Tapatalked by neXus⁴
[Nexus 4 Android Development] 0.0:
I would like to start building kitkat but there is no default XML for the kitkat branch. I only see cm11. [MENTION=2825227]Der_Schubi[/MENTION] could that be added?

sent from my Nexus 7