yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] VIPOA:
BUGS

Some :

1. AppBar doesn't show up.

2. HALO's action icons (dismiss all notifications, hide & silence until woken) are low quality.

3. LCD density 160 crashes system UI (I couldn't use the phone beacuse of the crashes...)

Please notify me that you read that reply :good:

That's it for now :)
[Nexus 4 Android Development] Der_Schubi:
Thats known and me and some other Devs all have the issue. Still no known solution :(

Its integrated since the last nightly ;)

I've read it :D
[Nexus 4 Android Development] lmarranzino:
Schubi... Thanks for replying to that post (you are more of a man than I) I would have ignored it for sure.

Again thanks for all your hard and GREAT work...:good::cool:

VIPOA....

I think you need to read the rules of posting and manners towards DEV'S .... Making statements of "Notify and Reply" is something I would say to one of my staff that I supervise. NOT something you say to a person who is sharing his expertise and art for FREE..People here have helped you as well with your questions which we could of easily said you need to go read the instructions. Peace and this is not meant as jumping on you. Just a freindly word of thought from another member who has seen flame wars. :good::cool:
[Nexus 4 Android Development] VIPOA:
Thanks :good::)

I just wanted to know that he read it so me and other guys won't bother him with these questions about these bugs...

Maybe it sounded like something else but if it hurt Schubi or anybody else, I'M SORRY.

And BTW,Here "Please notify me that you read that reply" I meant that he read my reply, not that he needs to reply...
[Nexus 4 Android Development] Der_Schubi:
Its okay, I understood it exactly the way you meant it.

By the way: we have a Bugtracker
[Nexus 4 Android Development] VIPOA:
Created a post there and bookmarked it :)
[Nexus 4 Android Development] Der_Schubi:
New in the last two days:
[Nexus 4 Android Development] Malnilion:
Sorry if I missed it, but any word on when or if CyanogenMod Accounts is going to be added to CyanKang? I think it'd be nice to have an additional method to remote wipe or locate a lost device. Thanks for the hard work you all put into this rom!
[Nexus 4 Android Development] 0.0:
[MENTION=2825227]Der_Schubi[/MENTION] what's the link for Mms: motion call? I can't seem to find it on cm gerrit

sent from my Nexus 4
[Nexus 4 Android Development] Der_Schubi:
CM-Account in already included. We sync every day with CM, so a new CM feature is in our ROM the next day, in worst case.

[MENTION=2281583]0.0[/MENTION]:

https://github.com/CyanKang/android...mmit/a95ec50888ae4f75e794ad9ba25e983cfa55d1c8

https://github.com/CyanKang/android...mmit/4f7c89e54efcb6aa504c0c5d7ddde8b340a78ded

https://github.com/CyanKang/android...mmit/a37a0f3fc031b01ee68a7e18e9ec3b9511f9aa6f
[Nexus 4 Android Development] plasticarmyman:
can i change the navigation buttons on this rom?...so that i have a permanent menu in place of the recents button?
[Nexus 4 Android Development] VIPOA:
Sure

Yap!

You also have PIE controls which you can change like the nav bar buttons :)
[Nexus 4 Android Development] Malnilion:
Well, I understand that, but for whatever reason, I'm not seeing a CMAccount.apk in /system/app. Maybe it's not in you guys' build manifest? Thanks for your quick response :)
[Nexus 4 Android Development] chris6278:
Absolutely loving this rom! Keep up the great work
[Nexus 4 Android Development] Der_Schubi:
Thats definately possible! In my local build, the account is included. But I sync directly with CM. Our Nightly builds are generated from what I upload.

So I guess you're right, and our build manifest has to be updated. I'll check tomorrow!
[Nexus 4 Android Development] sidVici0us:
I get a working config for appbar. I think the trigger position and heigth it's the problem. On mi installation only work with 48of of width minimum.

I think what it's better all values must be expressed as px not percent, it's less confusing.

In other news... please don't laugh to much... when I playing candy crush the game got lagged after few minutes. I have to close then and restart to get working but after a few movements get lagged again. In some cases the phone reboots and the app lost all data, one time after reboot the phone never boot up again I have to wipe data factory reset to get phone working again.
[Nexus 4 Android Development] atltrickster:
I had several random reboots that required complete system wipes while playing a different title on the last several builds myself. I finally switched over to SlimBean for the interim out of pure frustration as I'm thinking something may have changed in CM that is causing this...

Has anyone else experienced this? I love CyanKang and can't wait to reflash!!!

finnq and Schubi...thank you for all of the time and energy you have put into this...you guys rock!
[Nexus 4 Android Development] Der_Schubi:
AppBar should be fixed. May it's still not totally stable, but it's a lot better now!

That is caused by a commit from CyanogenMod that enabled all C-States on Mako. Especially C3 causes these hot reboots with data loss.

I've had these problem independent from the actual case, as Faux enabled all C-States in his kernel. It took me some weeks to identify C3 as the cause. But since I swirched it off, I never had such a reboot. Now for months.

And on 8th of September, CM did the same, they enabled all C-States. And all the problems are back...

We reverted the CM-Commit and with this fixed the issue on 10th of September. So, use a nightly from 11th or newer, and everything will be fine!
[Nexus 4 Android Development] 0.0:
That's good to know. I used your commit in one of my builds :good:

But if I flash faux's kernel, shouldn't it overwrite those sleep states and just use what faux has?
[Nexus 4 Android Development] Der_Schubi:
This is the revert of the CM Commit: https://github.com/CyanKang/android_device_lge_mako/commit/cb851aa04b27cdad63fae72e8845fd9399226366

It is baked into the RAM Disc, so Faux Kernel will use this values as long as Faux didn't set them by his own script or YOU configure it another way. [MENTION=647113]hellsgod[/MENTION]: Am I right with that? :D
[Nexus 4 Android Development] 0.0:
I understand now. I was having a lot of freezes of my phone. I was using faux and turned on c3. I didn't know it was this commit that was causing it. After my build is complete, I will test it out with my faux setup and see if I get those freezes
[Nexus 4 Android Development] Sblast:
Were Halo mods implemented in the latest build? It's so cool :p
[Nexus 4 Android Development] atltrickster:
This is wonderful, thanks so much for the prompt response! Thanks again for providing such a fantastic rom :)
[Nexus 4 Android Development] mattb3:
One feature request that I would love to see is to change/add a quick setting option to show the quick setting when there are no notifications rather then the current behavior to show the quick settings when there are no clearable notifications.

In other words an ongoing notification (like playing music) currently doesn't matter and the quick settings panel is shown. In think it makes more sense to only show the quick settings panel when there are no notifications of any sort.

In every other way the additional features in this ROM are awesome. Thanks for the great ROM.
[Nexus 4 Android Development] hellsgod:
faux also uses the anykernel method. So if all C states are activated in the Ramdisk, you will have them all enabled by default. You have to change this by yourself. So you're right [MENTION=2053764]Schubi[/MENTION].

hells

vom Knotenpunkt aus der Hölle gesendet
[Nexus 4 Android Development] :
I really wanna try this ROM but I'm afraid of the bugs.. I'm always busy with work and I don't have time to keep flashing nightlies stuff :(
[Nexus 4 Android Development] Sblast:
hmmm...It's very stable and I didn't find any bugs so far. I don't think you should worry that much about these nightlies.
[Nexus 4 Android Development] sidVici0us:
I'm now using 20130913 build and the data loss reboot still happening to me. How I can disable C3 satate manually?
[Nexus 4 Android Development] hellsgod:
When exactly do they happen? In Deep Sleep or if you use your Device?

Without a Log I cannot help. Try to turn off Dynamic FSync in Trickster and let it happen again. So you won't loose data. After the reboot post last_kmsg.

hells
[Nexus 4 Android Development] sidVici0us:
When I using my device on any application, it happen also one time a day. In deep sleep never happen to me. Now I disable Fsync and post the log when reboot happen.

Where is FSync to disable it?

Tnks.
[Nexus 4 Android Development] hellsgod:
In the "Specific" Tab. Do you use Chrome Beta for example? There are many reports that Chrome Beta let your device crash.

hells
[Nexus 4 Android Development] sidVici0us:
I installed trickster mod app and disabled fsync in specific details tab.

Yes I using chrome but it's only for the nice icon... I can uninstall it.
[Nexus 4 Android Development] Der_Schubi:
Changelog from the last few days:

The HALO mods are in the coming nightly!
[Nexus 4 Android Development] atltrickster:
Hells, I'm experiencing the same random reboots FYI. I'm running the ROM with LTE enabled. Here is a copy of the output from last_dmsg on my device: http://pastebin.com/WP52ih5d

http://pastebin.com/WP52ih5d
[Nexus 4 Android Development] hellsgod:
I't not a complete Log and in this part I don't see any reason for rebooting. Try it again if it happens again, thank you :)

hells
[Nexus 4 Android Development] sidVici0us:
I disabled dynamic fsyinc and uninstalled chrome and... finger crossed... have two days without robots.
[Nexus 4 Android Development] hellsgod:
Dynamic Fsync shouldn't be the reason for any reboots, because it only deactivates fsync durin screen on and flushes everthing, if you turn off your screen. But you can leave it disabled if you like.

hells
[Nexus 4 Android Development] sidVici0us:
I know fsync it's only the way in kernel to manage data to write in disc. Maybe chrome it's the reason for reboots and crashes.
[Nexus 4 Android Development] hellsgod:
Yes, Chrome is a reason for crashes. There are many reports of it in some kernel threads here on xda.

hells
[Nexus 4 Android Development] itsita:
Hey schub,

Could you take a second look at fixing the "reset circle battery colour"? Since I messed with it, I can't find the default colour again :(

Other then that, amazing work team !

Sent from my Nexus 4
[Nexus 4 Android Development] atltrickster:
I appreciate your getting back to me on this hellsgod.

Great news! It seems that after doing a complete wipe (including the internal sdcard) and reinstalling everything the random reboots no longer occur.

As I believe it to be the root cause of the random reboots, I should mention that I enabled LTE using an all-in-one package I found here this time around: http://xdaforums.com/showthread.php?p=43463403

Before, I was flashing a hybrid modem followed by a separate package designed to both enable and preserve the LTE setting via a script. I don't have any kernel messages or logs to prove that this was indeed the culprit, but I haven't had a reboot since :)

Thanks again for making yourself available!
[Nexus 4 Android Development] hellsgod:
I'm glad you solved your problem! No problem mate, i'm here to help :) Thanks for letting me know (=

hells
[Nexus 4 Android Development] Opentang:
What is the difference between "vibrator intensity" and "vibration strength" in System Settings > Other Device Options?

Kind Regards,

Brandon O'Keefe
[Nexus 4 Android Development] Der_Schubi:
Its the same thing, but twice. Sorry! :D

I'll remove one of them. ;)
[Nexus 4 Android Development] ermacwins:
Remove vibrator intensity
[Nexus 4 Android Development] Der_Schubi:
Hi guys!

For all of you, which are suffering under the hot reboot problems, I made a test build with stock kernel:

https://erlangen.ccc.de/~schubi/roms/CyanKang-10.2-20130919-UNOFFICIAL-mako-PDroid.zip

Please everyone of you test it! If you're normally using the version without PDroid, please also test it, you can switch back without wiping at any time!

I'm looking forward to your feedback! :)
[Nexus 4 Android Development] Sblast:
I flashed it, can't seem to get any hot reboot problems.
[Nexus 4 Android Development] chris6278:
Uh did u add a new boot animation on the latest build?
[Nexus 4 Android Development] Der_Schubi:
Do you expect an answer? What do you want to hear?

You discovered a hidden feature! :D :p ;)

Just joking...

I finally enabled it for Mako. Its not final, but good enough for now. :)
[Nexus 4 Android Development] Kev23:
Anyone having volume issues on 20th nightly? During media playback volume slider will only go half way up the scale. Thanks

Edit... Forgot to say this is just with earphones connected.
[Nexus 4 Android Development] Der_Schubi:
In volume settings there is a checkbox for clipping down headset volume. Do you search this?
[Nexus 4 Android Development] 0.0:
the commit above still isnt updated on the latest build. the new drawable isnt there. it should like this:

patch set #4 has fixed the alignment issues in the screenshot, so dont need to worry about that
[Nexus 4 Android Development] Opentang:
Nice to have a few new options within CM10.1 :)
[Nexus 4 Android Development] 0.0:
This commit looks useful for pie controls. I think you know about this since you watch Jens Doll and his commits:

http://review.cyanogenmod.org/#/c/35312/

Fix for trebuchet:

http://review.cyanogenmod.org/#/c/35368/

Thanks! :)

edit: i didnt remember that the pie control commit was in the changelog. DANG IT! it just slipped my mind...

Sent from my Nexus 4
[Nexus 4 Android Development] Der_Schubi:
Forgot to update it. ;)

Ehm, RTFM?! :D

////// NEW in this Build \\\\\\
[...]
# 35312 - Adapt navigation bar's long press behaviour for pie controls
[...]
[Nexus 4 Android Development] 0.0:
dang it man...i apologize. i saw the changelog earlier, but i didnt remember that the long press pie control commit was in it. again, i apologize... :crying:
[Nexus 4 Android Development] superleeds27:
I still have the poweramp issue.

Only seems to occur when I have headphones in?

Edit: Safe headset volume when first plugged in. Having that ticked limits overall headphone sound. Tis a bug I'm afraid!
[Nexus 4 Android Development] Der_Schubi:
Never mind! ;)

Could you please tell me exactly what to do when I want to reconstruct the issue?

Otherwise a logcat woul also help.
[Nexus 4 Android Development] Neefy:
Thanks for the new build, will flash when I get home :)
[Nexus 4 Android Development] superleeds27:
Go to the settings menu, then click on sounds

Scroll to the bottom, youll see Safe headset volume when first plugged in

This is suppose to stop the sound from being at max when you first plug the headphones in, (to stop you scaring yourself i think!)

However, if its ticked, and you insert the headphones, then try to raise the volume, it doesn't let you. It gets stuck.

If the option is unticked, the volume works just fine.
[Nexus 4 Android Development] Der_Schubi:
AFAIK this is the normal behaviour. Checking this option generally limits the maximal speaker volume.
[Nexus 4 Android Development] 0.0:
Idk if there is a commit for this fix, but it has been resolved: https://jira.cyanogenmod.org/browse/CYAN-559

It'll be in M3...so maybe a fix is already out in github?

Also, WiFi fix perhaps?

https://jira.cyanogenmod.org/browse/CYAN-558

"Enable ARP mode" should be reverted? some users have reported issues after this was enabled

edit: M3 looks like is rolling out!

Sent from my Nexus 4
[Nexus 4 Android Development] Der_Schubi:
Update!

This time without new cherry picks. But the emoji button cp is updatet... :p :D
[Nexus 4 Android Development] 0.0:
I checked the change log, and I didn't see these commits:

http://review.cyanogenmod.org/#/c/34929/

http://review.cyanogenmod.org/#/c/35439/

http://review.cyanogenmod.org/#/c/35314/

http://review.cyanogenmod.org/#/c/35472/

http://review.cyanogenmod.org/#/c/35231/

Fixes:

http://review.cyanogenmod.org/#/c/35530/

http://review.cyanogenmod.org/#/c/35365/

Thanks! :)

Sent from my Nexus 4
[Nexus 4 Android Development] azrash:
Hi, I am interested in trying out this rom because of the OpenPDroid integration. May I know if the issues with slow GPS fix and cell tower triangulation is fixed in the OpenPDroid version that you have integrated? (had issues with this back when I used the auto patcher with CM M1)

And another one is, which Pdroid manager would you recommend, the one by FFU5y or CollegeDev's?

Thanks

Flowed from my Nexus⁴
[Nexus 4 Android Development] Der_Schubi:
Hi, the GPS issues should all be gone.

Also there is OpenPDroidManager already integrated in this ROM.

But of course you could use another one.

@0.0:

Thanks. I'll pick the first two of these for sure.

To the others:

The Pie-Control stuff does nothing at all, its just a service that is unused until the Pie will be tweaked to use it.

The rest of the commits are bugfixes, but I used not tho pick such things, as they normally are merged very fast and are still in review for testing. I cant check if they work. So I let this do the guys from Gerrit.
[Nexus 4 Android Development] 0.0:
question: i was reading the comments about this SMS feature (http://review.cyanogenmod.org/#/c/35231/). would it be alright to include, or is that too buggy to include right now?
[Nexus 4 Android Development] Der_Schubi:
That commit was very ugly some days ago, but now it gets better and better. I think I'll pick it for the next build.
[Nexus 4 Android Development] Neefy:
Downloading the latest version, thanks. Does anyone know how to get IOS6 Emojis? I can only get IOS5 Emojis with most..

Btw. @ Schubi, if you want I can give you access to my FTP ("unlimited" storage) for backups in case your own domain is down now and then.
[Nexus 4 Android Development] Der_Schubi:
Thanks, Neefy. But I already have some backups where I could upload.

And erlangen.ccc.de is a high reliable dedicated server in the computer center of Frankfurt. ;)
[Nexus 4 Android Development] azrash:
Thanks, I made a clean install of the Pdroid version just now and somehow Altitude keep on FC-ing. Clearing data didn't solve it too, is it possible that this is because of OpenPDroid? I have enabled all permission in the included pdroid manager for the app.

Link to the app here

https://play.google.com/store/apps/details?id=com.asksven.betterlatitude

Flowed from my Nexus⁴
[Nexus 4 Android Development] Kev23:
Ahhhh, unchecked the 'safe headset volume' box and normal service resumed.

Thanks Schubi
[Nexus 4 Android Development] kpaolo:
This is what I was being waiting for long time! TY!!!!!

Flashing over a CM nightly, I cannot set the status/navbar transparency up... any suggestion?

THANK YOU AGAIN!!!

P.S.: can we translate your kang? how?

edit: after a reboot it works, but only if I don't touch the screen...
[Nexus 4 Android Development] Der_Schubi:
What means, you can't set? What does it do or not?

Please explain a bit more :D

Translations are welcome!

All our strings (that are not present in CM), are bundled in two files: ck_arrays.xml and ck_strings.xml.

so, at first, translate ck_strings. Then ck_arrays. BUT, in the english arrays file, there are all arrays, even untranslateable.

So, take the german ck_arrays.xml. you can look for the english equivalent in the english ck_arrays, searching for the name of the array, eg: name="battery_bar_entries".

Than just upload ck_arrays and ck_strings somewhere and pass us the link. :)

I hope this was clear enough? :D
[Nexus 4 Android Development] kpaolo:
translation: i'll surely try to study those files!

transparency: i'd like the bars to be transparent by themself and to be free to set the height of navbar as well but... I can see transparency only when

- set a navbar height, reboot and touch the screen ONE time. a second touch make the bars black as stock

- sometimes expand desktop and back may help (again one-touch-bug)

- with navbar dpi lower than 38, transparency doesn't work; only few pixels on the upper side aren't black

i cannot post screenshots because this bug comes ang goes with touches...
[Nexus 4 Android Development] Sblast:
hmmm...I'm using 38dpi and extended desktop (I switch between them) and it's fine. Are you using another kernel maybe?
[Nexus 4 Android Development] kpaolo:
completely stock.

forgive me, just change "one touch bug" with "one slide bug"

i don't like extended desktop so what i'm trying to get are tiny transparent bars.

i set them up by your control menu but they are both transparent only "sliding" (not touching, sorry again) for one time.

i.e.:

set them up> both black

slide the screen > both transparent

reslide the screen > black again during touch and then transparent

on step 2 i have to slide, a simple touch does not have effects at all
[Nexus 4 Android Development] sw6lee:
He's right! I have no idea what I did changed this, but only a few pixels on top of the navigation bar is transparent. Looks weird, and I want the whole nav bar to be transparent.. :(

Too bad..I gotta try another rom now.
[Nexus 4 Android Development] Der_Schubi:
New in the coming nightly:

Just google it, I even did'nt knew it. :D

To your problem with transparecy: I cant reproduce it. No idea what i'm doing different. :D
[Nexus 4 Android Development] lmarranzino:
Schubi I think this is it correct...Very Cool

Inside the Moto X Active Display

http://www.androidcentral.com/inside-moto-x-active-display
[Nexus 4 Android Development] Der_Schubi:
Yep. Its a much simpler implementation, but it works fine. :)

More to come ;)
[Nexus 4 Android Development] 0.0:
Focal is now in the play store. Focal doesn't have to be in the build anymore :)

sent from my Nexus 4
[Nexus 4 Android Development] respider:
any ideas if mirror will have 0922 build?
[Nexus 4 Android Development] chris6278:
Theres a bug with the latest build 9/22 the navbar keys are showing up on the lockscreen instead of the navring
[Nexus 4 Android Development] sidVici0us:
I having a bug with default camera app. If I take a picture the tumb is fine but if I see this picture late all photo is black. To workaround this I have to enable hdr take a photo and disable hdr to take normal pictures. This happen in all builds since I installed this Rom. Also happens in cm10.2 nighty.
[Nexus 4 Android Development] lmarranzino:
Primary Link is Down

Just went to download and the link is down it seems...:(

EDIT: Link back up... Going to flash 22 here shortly...Thanks
[Nexus 4 Android Development] atltrickster:
As of 3:38PM EST the primary host is unreachable. The latest build available on the two alternate hosts is from 9-19.

Just letting you guys know. This ROM is my favorite by far so will try again later.

Thanks!
[Nexus 4 Android Development] lmarranzino:
Reboots

Getting reboots right after install... I am wondering if it has to do with the Merge to r.3 and AOSP.

I only say this as I was checking out some other ROMS and testing Kernels (HellsCore b38, Matrix 11, AK v0.25) all AOSP JSS kernels. Yet it seems in the new merge something changed ?

I found on CrDroid 17 that if I use the CM kernel in the ROM all is fine yet tyring to switch out (even after letting the CM kernel settle awhile) these damb reboots occur. Someone on another thread mentioned a similar issue as well. Any thought's ??

I have tried twice with nightly 22 and all boots fine and once I go to set up WHAM incoming reboot. I had to revert back as I am On call today so can't be without my phone too long.....Thanks for any insight or help.:fingers-crossed:

PS> tried to pull a log on the second round and got another reboot sorry..
[Nexus 4 Android Development] itsita:
maybe it's related to the fact that 21/22 builds are 20MB less than the other builds?

is there any other explanation for the drop?
[Nexus 4 Android Development] kenshinta:
Just to balance things

I dont have random raboots after flashing 9/22. What I did experience - after so long without one- is a deadlock while using the keyboard.

Didnt experience that from 0/11 > 9/19 > 9/21dirty flashed. Only with 9/22.

But I have no random reboot.