yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] lmarranzino:
That very well could be part of it, BUT I am also getting the reboots as others are stating on the new JLS builds when using any JSS kernel.

Sure that Schubi will work it out. Not complaining yes it bugs me BUT again not a complaint exactly.:D
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
Can we get some sort of faster mirror? For the US, downloading at 40kb/sec takes forever. Plus, there's a chance for failure. I kept trying on the 19-SEP build so many times until it was pointless that I should've just moved onto the next build :(
[Nexus 4 Android Development] Der_Schubi:
No, These 20MB are caused by the removal of Focal.
[Nexus 4 Android Development] Der_Schubi:
As finnq's Server is down, please use http://erlangen.ccc.de/~schubi/roms/

I just uploaded the recent builds :)
[Nexus 4 Android Development] abaithad:
Hi Der_Schubi

If it was not asked before, how to deactivate volume limitation on headset? I'm unable to get the popup when increasing volume while playing music hence i'm blocked with medium volume level

Danke!
[Nexus 4 Android Development] Der_Schubi:
There is a checkbox for cutting down the headset volume in gringtone settings volume
[Nexus 4 Android Development] chris6278:
Anyway to fix the navbar keys showing up on the lockscreen sometimes?
[Nexus 4 Android Development] 75markus:
Hi Schubi,

I´m facing a problem with your latest builds since 20130919, i´m not able to connect the N4 to the computer.

When i plug in the usb, "process android media" stops, and the device doesn´t show up ...

I flashed back the 20130919 nightly and everything works fine again ...

anybody else faces the same problem ?
[Nexus 4 Android Development] abaithad:
Hi

Working fine here on today's nightly.

May be that providing logs will help
[Nexus 4 Android Development] chris6278:
Im pretty sure the navbar keys showing up on the lockscreen has to do with the active notification feature. The same bug is occuring on crdroids rom as well. It only shows up when u turn ur screen on, then dont unlock ur lockscreen but turn ur screen off and then turn it back on an the navbar keys as well as the clock in the status bar will be there. I hope this gets fixed soon cause its really annoying
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
[MENTION=2825227]Der_Schubi[/MENTION] Pretty impressed with this ROM. I just have 2 questions/requests that I'm wondering if you can address:

1) In CM 10.2, the lockscreen dims/darkens the wallpaper. Is it possible we have the option for that in this ROM?

2) Would it be possible to have the default boot animation or some sort of checkbox? I'd prefer to keep it close to base CM as possible. But that's just me.
[Nexus 4 Android Development] 0.0:
I noticed it happens when waking the phone, then turning it off while on the lockscreen, then waking it again. it's consistent and happens every time :(
[Nexus 4 Android Development] sc0use:
thank you for this rom i like it a lot.

i problem i have found that it is not registering my wireless charge like the stock rom does? it keeps dropping connection and then stays at a low charge then suddenly jumps up say from 49% to 69%.

its nothing major but a bit annoying.

will using a different kernal fix this? or am i better staying with the built in kernal?
[Nexus 4 Android Development] LarsPT:
Gosh... I'm tired of the deadlocks from official CM nightlies... but I have no idea what to flash...

I guess I'll try this ROM! Does franco kernel work well with this ROM? It seems to be the most popular kernel around... I have no idea!! Thanks!! :)
[Nexus 4 Android Development] chris6278:
Yea its very annoying. Im staying on the 9/21 build until its fixed. Im pretty sure it has to do with the active notification feature cause thats when the problem started when it was added. The same thing happens on crdroid as well
[Nexus 4 Android Development] respider:
guys what problem does that deadlock cause?

how to reproduce it?

I see everyone talking about that and I have no idea what it is
[Nexus 4 Android Development] LarsPT:
What happens (in stock 4.3 and also happened in official CM) to me often basically is when using the standard keyboard on facebook or writing a text message, if I type fast enough, it just hangs for like 10 seconds completely unresponsive. I wait it out and it comes back to normal. I also think uptime plays an important role in it. If you reboot often you should get it less.

I just flashed this ROM with linaro kernel. At first strange things were happening... like in settings when I clicked on "storage" it FC'ed. I reflashed the ROM and now it's ok. So far I'm happy. Finally I'm able to change the frequency of the notification lights! They were way too slow for me in stock and in the CM nightlies :D

Thank you!!

(I didn't get any difference in performance in Quadrant though compared to CM nightlies... but the 3D performance seemed much better during the benchmark)

EDIT: Hey, actually the problem seems to be with linaro franco kernel... Which kernel works well with this ROM? Thanks!
[Nexus 4 Android Development] chris6278:
Hey OP can u please look into the issue where the navbar keys are showing up on the lockscreen when u wake the phone, then turn off the screen and then wake the phone again
[Nexus 4 Android Development] c@p:
Why don't you use the included Hells-Core? It's fast an very battery friendly.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Android Development] LarsPT:
Hi! Thanks for your reply!

What kernel included? When I look in the settings in kernel I get a 3.4.0 cyanogenmod "standard" kernel... or so it seems! If this already is a "custom" kernel shouldn't I get a performance menu somewhere? So that I can adjust the governors, max cpu freq, etc? :/

Thx again!

EDIT: Oops, forgot that I had to press the build 7 times for those menus to appear... ok so but is it normal that I have the cyanogenmod thing in the kernel? :p

PS: I saw somewhere there was the possibility to change the behavior of a long press on the buttons? Is this available in this ROM? In my previous phone I used to have a long press to shut off the screen... I like that because it saves some clicks to the power button (which in my previous phone was already beginning to fail), so I'd like to start doing that as soon as possible on this one! Thanks!!
[Nexus 4 Android Development] c@p:
Since a few builds there is the Hells-Core included. Bevor it was the CM Kernel. It should look like my Screenshot. It's an older one, actually is b38 included.

If you want change settings, use Trickster Mod, but it's no need to change anything because the optimal settings are coded in the ramdisk.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Android Development] LarsPT:
I definitely don't have that... I flashed 20130924 nightly... should that kernel be included? Because it's not... but I don't mind flashing it separately... where can I find it? Thanks!!

(Also, I edited my post above and added a "PS", could you look into it? Thanks a lot man...)
[Nexus 4 Android Development] c@p:
You can find it here:

http://www.android-hilfe.de/showthread.php?t=410455

[KERNEL][JB][JSS15J / JWR66V] hells-Core b38 [19/09/2013]

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Android Development] millomonk:
You're both right. I think they switched back to cm-kernel again recently
[Nexus 4 Android Development] LarsPT:
Forget about my "PS", I can add "screen off" to a quick shortcut! This is great!! Thank you!!!

Would be really great if "menu" button could be added to the quick shortcuts! Does anyone think this might be possible?

---------- Post added at 09:51 AM ---------- Previous post was at 09:35 AM ----------

There's one AOSP and one "normal" version of hell's kernel. I'm guessing I should go for the AOSP?

Thanks in advance.
[Nexus 4 Android Development] Der_Schubi:
I have no idea... :(

Yes, may try to use another Kernel.

Yes, its caused by ActiveDisplay. But the guys from ChameloenOS don't answer any questions... :(

Yes, I've already done some tests, but no luck until now.

We've switched back to CM kernel yesterday. :D

I didnt advertise it in the threads.

:D

Menu button? This wont work I guess, as it would close as soon as the qs panel closes...

You need the AOSP one ;)
[Nexus 4 Android Development] LarsPT:
Thanks for your reply!!

Well... the way I look at it... you would long press home, choose the menu button, and the menu (equivalent to the 3 dots button) of the app would open...

I've seen other people around the forum that change the "long press" behavior of the buttons to have a menu button without having to add the "proper" 3 dots menu button, which is what would be ideal for me, but I'm enjoying your ROM so far and I'm not going to change just for this functionality...
[Nexus 4 Android Development] Der_Schubi:
Youre talking about the NavBar Shortcuts. Now I got it. :D I'll have a look if thats possible. ;)
[Nexus 4 Android Development] chris6278:
Thanks Schubi for lookin into. Maybe u should remove active display til iys gets fixed. It also appears to be buggy in other areas as well. Dont mean to tell u what to do with ur rom, its just a suggestion. For me its so annoying that i havnt updated since the 9/21 build.
[Nexus 4 Android Development] Der_Schubi:
How can I fix it, if I remove it????? :D

If its too buggy in the moment, leave it deactivated. ;)
[Nexus 4 Android Development] chris6278:
Good point lol however the navbar keys on the lockscreen still show up even if its disabled
[Nexus 4 Android Development] Der_Schubi:
I know. Thats the only problem. But as this is not a real problem (back and home keys are not working, recents key does, but behind the lockscreen), I guess its possible to live with it, till I can fix it. :)
[Nexus 4 Android Development] chris6278:
Getting installation aborted on build 9/25. Ok i got it to work. Mustve been a bad download but good news is that the navbar keys on the lockscreen went away. Thanx Schubi
[Nexus 4 Android Development] lmarranzino:
Flashed the Experimental Build (why experimaental ?) and than let it sit after setting up , I then flashed Hells Core b38 and so far no reboots or issues. I know Hell had mentioned something about flashing stock kernel or kernel that ROM is with and then flash alternate later on. Hope this is correct yet has worked far better for me. Thanks again
[Nexus 4 Android Development] LarsPT:
Great, thanks so much!

Or the possibility to change the behavior of long pressing the recent apps button and the back button (which currently do nothing). That would be the best!!
[Nexus 4 Android Development] Der_Schubi:
It's not gone here...

Experimental, as it was a testbuild. ;)

We switched back to CM kernel, so just flash any kernel you want after the ROM. ;)

The back button long press is tied to "kill app" ;)
[Nexus 4 Android Development] 75markus:
[MENTION=2825227]Der_Schubi[/MENTION], i found the culprit, it´s franco kernel. i think the problem exists since you added USB OTG ...

when i´m running your build with stock kernel, everything is fine, after flashing franco kernel it´s not possible to connect the phone to the PC anymore... process android media crashes when plugging in usb, and the device doesn´t show up ...

is there any way to fix it from your side ? franco won´t change his kernel for sure ...

it´s a pity, cause i wanna stayx with your ROM & franco kernel ...
[Nexus 4 Android Development] Der_Schubi:
Thanks. Already found it with a logcat from a user.

The error:

getVolumeState(/storage/usbdisk0): Unknown volume

I revertet OTG just a few minutes ago.

:D
[Nexus 4 Android Development] 75markus:
looking forward for tomorrows build ;)
[Nexus 4 Android Development] chris6278:
Yea schubi im still gettin the navbar keys on the lockscreen but only when active notification is enabled where before they was showing up even when it was disabled so i guess its partially fixed lol
[Nexus 4 Android Development] Der_Schubi:
Changelog for the coming nightly and few past days:
[Nexus 4 Android Development] Der_Schubi:
whoops. double post...
[Nexus 4 Android Development] Sblast:
Does it have OTA like in file name? :p
[Nexus 4 Android Development] Der_Schubi:
Whar file name???
[Nexus 4 Android Development] Sblast:
CyanKang-10.2-20130926-EXPERIMENTAL-mako-OTATESTDNF.zip

;)
[Nexus 4 Android Development] Der_Schubi:
DNF = do not flash! ;)
[Nexus 4 Android Development] 0.0:
Is "show WiFi name" a feature that is in the ROM?

sent from my Nexus 4
[Nexus 4 Android Development] 0.0:
Having AOKP custom animations would be cool to include. here are the links
[Nexus 4 Android Development] Der_Schubi:
I don't like such features. :(

Such things are exacty that, what makes ROMs slow. :D
[Nexus 4 Android Development] chris6278:
I agree. All those features are nice and all but id hate to see this awesome rom go down the same road as crdroid. That rom went from acm based rom with some cool extra features to basically a slimsrom which is why i stuck with this one. I really love what schubi has done here!
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
Yea CrDroid went a bit too far by trying to add everything. I prefer that ROMs don't try to add the while kitchen sink. It just becomes a very messy implementation. Correct me if I'm wrong but this seems like it should be a CM based ROM with a few cherry picks and addons? For those who want all of aokp and PA there is PAC after all...
[Nexus 4 Android Development] 0.0:
I agree. I don't like slim nav bar and pie. crDroid is a good ROM, and has a good dev, but maybe he got a bit carried away

However, the aokp animations are cool to me. But of course, if it won't be added, then I respect that :)

sent from my Nexus 7
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
Yah. Not to get too carried away but I don't use PIE and so the nav bar did affect me in that sure it was a great upgrade in that SLim's interface was easy to use, but it fundamentally altered and took away CM functionality in that the back button was incorrectly sized in landscape. Somehow the CrDroid dev is not addressing that or at least hasn't informed us that it can't be fixed. The vibration is all whacked because now the buttons only vibrate when you let go of the button (counterintuitive). Furthermore, you used to be able to add small buttons on the left and right in CM, but that's gone. So my stance is that new features are great, but if they take away CM functionality, then I think that's a step backwards. But of course what do I know? I'm not a ROM kanger... haha. Just my 2 cents.
[Nexus 4 Android Development] Cristiano Matos:
Shubi my friend excuse while I invade your thread.

Dear user do you really know what you're saying?

Kitchen sinking, really!

Slim roms, really!

Slim ROMs is a perfect source of very good features and 90% of ROM projects have their functions (a lot).

Nothing more useful in crDroid than pie and navbar of slimroms, in my opinion.

All "bugs" related by you in my thread are new behaviours and not bugs.

Respect first this thread, since here it's not crDroid one and be welcome to continue your flames in my thread.

In my first page exists my github link. Feel free to click and read the commits.

Regards.
[Nexus 4 Android Development] Sblast:
I don't agree with that. I think the popularity is justified - SLIM navigation is better than CM's and every user gets used to features he loves and utilizes for greater productivity.

Besides, you can't get carried away if it works ;).
[Nexus 4 Android Development] 0.0:
The problem is the vibration part of the nav bar. My source built ROM from DJL works fine :p (yes, a self plug for my ROM lol)

I still don't care for the slim nav bar. I'll still keep up with the one I built though

sent from my Nexus 4
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
OP, any way to include BOTH the default gallery and the modded gallery? It seems the SLIM gallery FCs when I look at the details of a photo.
[Nexus 4 Android Development] Der_Schubi:
No problem, it was talked about you. ;)

And I agree, I dont really like Slim as ROM, but they are one of the best source for kangers.

Kufikugel is just a top coder! :)

Btw, whats going on there? He didnt commited anything since over two weeks...

What SLIm Gallery do you mean?

And yes, you can use two of them.

Google Cam/Gallery in named GalleryGoogle.apk, CM Cam/Gallery is named Gallery2.apk. So just copy the missing file into /system/app or /data/app
[Nexus 4 Android Development] :
Thank you very much for the rom.... runs smoothly :good:
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
What I meant was that doesnt CyanKang's camera contain SLIM commits? I'm calling it the Slim camera/gallery because it has Slim commits. Non-official Galleries seem unable to browse Google+ Photos and I seem to be getting some FCs if I check the details of specific photos. That's why I'm wondering if I can also run the official camera/gallery as well.
[Nexus 4 Android Development] :
Where is the link for the stable version? I Dont want nightly
[Nexus 4 Android Development] Der_Schubi:
There is no stable and it never will be...
[Nexus 4 Android Development] TheDarkDefender:
Its just a name. Nightlies are very stable

Sent from my Nexus 4
[Nexus 4 Android Development] 0.0:
[MENTION=2825227]Der_Schubi[/MENTION] what is the link to the multi-user commit(s)? thanks :)

edit: is it only this commit? https://github.com/CyanKang/android_frameworks_base/commit/e7e844f0bb21bfbf316dbfe400aefe7cba4978a5. I couldn't find the Settings for it
[Nexus 4 Android Development] sidVici0us:
Isa This rom jss or jwr? I want try semaphore kernel the cm kernel it's showing some problems like reboots and data lost
[Nexus 4 Android Development] 0.0:
This is a jss ROM

sent from my Nexus 4
[Nexus 4 Android Development] sidVici0us:
Thank you. As I can know that? This it somewhere in the rom or referred?
[Nexus 4 Android Development] chris6278:
No one is trying to flame you or your rom. He was just giving his opinion and apparently is also the same as many others. I used your rom since build 1 and loved it but it quickly became more of a slimrom than cm whichis great if that's what you like. I like this rom cause its more cm based. I think ur a great dev but don't take things so personal
[Nexus 4 Android Development] 0.0:
well, people know this because CM is based off of AOSP, and AOSP is currently at JLS. JSS kernels still work with JLS. I flash JSS kernels and it works fine
[Nexus 4 Android Development] sidVici0us:
I tried to flash jss semaphore kernel and never boot up, stuck in Kang logo. What kernels had you flashed?
[Nexus 4 Android Development] 0.0:
I flash faux kernel

I wonder why semaphore doesn't boot up...I do know CM is moving to CAF, so that could be a problem with some kernels if they aren't updated (don't take my word for it)
[Nexus 4 Android Development] 0.0:
this is a small UI tweak. when the HALO button is pressed in the notification drawer area, I don't see it getting pressed when my finger is on the icon. the icon (attached) is supposed to activate but it doesn't. is it possible to make it do so? thanks :)

Edit: also, should the app ops shortcut be removed, since it can be accessed via privacy manager?
[Nexus 4 Android Development] hellsgod:
As ever, CM do it their way. They don't care about other Developers and their Custom Kernel. franco for example won't add support for CM. If you want to add CM Support, the best you can do, is build your Kernel on CM Sources, what I did in the last days. I've made 3 rebases on JSS, JWR and CM Sources. The rebase on CM Sources was initially planned, because my Kernel will maybe be added back as CyanKang Stock Kernel. But because I use CM by myself, it wasn't only work for others :)

Maybe tomorrow I'll post a public Test Kernel for you guys. In the german board I've already done that in the last two days.

stay tuned ;)

hells
[Nexus 4 Android Development] 0.0:
sadly, after CM has gone public as a company, it will be going downhill from here. It's good that CM is a company for the average consumer and investors, but for builders like yourself, it hurts you all. Money can destroy things, and it looks like CM is being swallowed up by it :(
[Nexus 4 Android Development] hellsgod:
Time will tell us whats going on. I dont have a problem with Cyanogen Inc. They've done what they want in the past and they will do it in the future. And honestly, I dont care. As long as I can build a bootable Kernel, they can do whatever they want. Its their way. I dont have to use CM, if I'm not happy with their turn, but I can build a Kernel for Users, who are happy with CM.

CM should never forget why they are, what they are now. That's all.

hells

vom Knotenpunkt aus der Hölle gesendet now Free
[Nexus 4 Android Development] 0.0:
could this be added? is it good?

MediaScanner behavior on boot (1/3)
https://github.com/DJL10-2/android_frameworks_base/commit/7f0c23100509733b7149a5aee3425424fad7d911

MediaProvider: MediaScanner behavior on boot (2/3)
https://github.com/DJL10-2/android_packages_providers_MediaProvider/commit/94202ea8276317a4648f5de0a27d80d89790ab36

Settings: MediaScanner behavior on boot (3/3)
https://github.com/DJL10-2/android_packages_apps_Settings/commit/cca8921ca866b6bf5d41679fbd0d462e20c47a20

I tried to add it in my own builds using your source code, but I couldn't figure it out :(
[Nexus 4 Android Development] Der_Schubi:
Yes, only this one. But multiuser only works without PDroid. ;)

Does Faux Kernel work for you with the nightly from today?

I only get a cyan striped screen. :(
[Nexus 4 Android Development] c@p:
CM and their Kernel madness - flashed the wrong one and got bootloop with data loss. :banghead:

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Android Development] chris6278:
In the last 2 builds I noticed that the glowdots that shows up around the lockring when u press it has been blue. Anyone else seeing this?
[Nexus 4 Android Development] 0.0:
I'm using the AK faux kernel. It has been fine. I did not try today's nightly. I'm scared to do so after reading users complaints. I am also using the ROM I built from your source code, so it may be different since I revert some commits

sent from my Nexus 4
[Nexus 4 Android Development] millomonk:
I had the same trouble yesterday and my nandroid didn't restore data partition. Did a full restocking just to find out that the backup was broken... An older one without compression finally revived my N4 :) Will try the newest nightly now. Fingers crossed ;)
[Nexus 4 Android Development] c@p:
Waiting for feedback - good luck :thumbup:

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Android Development] millomonk:
For now I better stay on cm kernel ;) We'll see what the next days will show up in kernel development. I'm more scared about my nandroids...
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
So what's the latest rev of CyanKang I can use with Franco Kernel?
[Nexus 4 Android Development] Der_Schubi:
Thats a good question...

Should be 09/30 or something.

Anyone knows exactly?
[Nexus 4 Android Development] 75markus:
10/01 is working fine :)
[Nexus 4 Android Development] 0.0:
good feature? :)

https://github.com/cristianomatos/android_frameworks_base/commit/ddb587437375ab2782c56b753506857797a82dee
https://github.com/cristianomatos/android_packages_apps_Settings/commit/fdd6a68c87de48a779cbccdf4189a2eab49f9443
[Nexus 4 Android Development] Der_Schubi:
Haha, I'm about to port it right in this moment. :D
[Nexus 4 Android Development] 0.0:
Have you gotten a chance to look at this? Idk if it will be good for this ROM or not. thanks :good:

MediaScanner behavior on boot (1/3)
https://github.com/DJL10-2/android_frameworks_base/commit/7f0c23100509733b7149a5aee3425424fad7d911

MediaProvider: MediaScanner behavior on boot (2/3)
https://github.com/DJL10-2/android_packages_providers_MediaProvider/commit/94202ea8276317a4648f5de0a27d80d89790ab36

Settings: MediaScanner behavior on boot (3/3)
https://github.com/DJL10-2/android_packages_apps_Settings/commit/cca8921ca866b6bf5d41679fbd0d462e20c47a20
[Nexus 4 Android Development] Der_Schubi:
I will have a look right after this port. :)
[Nexus 4 Android Development] 0.0:
Sorry, one more if you don't mind. I tried to look for code to have this in cristiano matos github, but couldn't find it

sent from my Nexus 7