yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] mythi:
exactly , the compression plus having asked some friends and have concluded that i had to set selinux to permessive :eek: bad thing is that i got messed up and deleted the device tree from my local machine :crying: because i got upset from from circling in non-booting square :D gotta start again now :rolleyes:

edit :

this error :fingers-crossed:

/home/mythi/cm/kernel/samsung/jf/drivers/video/msm/mipi_samsung_tft.c: In function 'mipi_samsung_disp_get_power':
/home/mythi/cm/kernel/samsung/jf/drivers/video/msm/mipi_samsung_tft.c:525:35: warning: argument to 'sizeof' in 'snprintf'

fix is

adding (int) before 'sizeof' decleration in drivers/video/msm/mipi_samsung_tft.c :laugh:
[Galaxy S 4 Active Original Android Development] spegelius:
Ok, seems that i missed that commit by luck :). There's cm-12.0 branch on jactive tree in my github. Actually i think it's very much like the official cm11 tree...

Ah, i used sizeof(buf) to sizeof(*buf). Not sure which one correct, propably both work. Seems Lollipop has upgraded the gcc version :)
[Galaxy S 4 Active Original Android Development] mythi:
whats really wired is i am in an endless bootloop , no logs no adb nothing just looping :silly:

edit : moment of crap , i forget the vendor part :eek: wonder how it compiled fine :confused:
[Galaxy S 4 Active Original Android Development] spegelius:
Vendor stuff isn't mandatory, i think that could be changed in BoardConfig.. but enough cm12 offtopic, i made a thread in Development, let's continue there.

In regards CM11, i noticed a kernel config change, CONFIG_BT_MSM_SLEEP=y is set on jf but not on jactive. I'll change that. Might be it's kinda relaed to bluetooth sleep, hmm?
[Galaxy S 4 Active Original Android Development] walter79:
Do we need mpdecision binary for our device?
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, it;s there on the vendor props
[Galaxy S 4 Active Original Android Development] Grinface:
Strange...Have you done an update or did a clean install?

I did an update from version 20141030.
[Galaxy S 4 Active Original Android Development] walter79:
Device runs well without mpdecision. I use multi core cpu control to setup cpu max frequenz and more. cpu hotplug works well to. And best i got battery drain from 0.5%/h with wifi always on if device is left on my desk.
[Galaxy S 4 Active Original Android Development] spegelius:
Ok, i havent tried without it. Might try if it brings some improvements in battery or otherwise.
[Galaxy S 4 Active Original Android Development] Devo7v:
I updated through CyanogenMod update from 20141106 or 20141108, I can't remember which one.
[Galaxy S 4 Active Original Android Development] spegelius:
Kernel CONFIG_BT_MSM_SLEEP=y was merged today, so next nightly should have that enabled. Personally i haven't used bluetooth much so can't say if the battery usage is on the high side...
[Galaxy S 4 Active Original Android Development] theMasterplan84:
I also have issue when enabling Bluetooth after most recent update, it disables wifi but I can't re-enable. Wifi is on but wont connect to my router only a reboot fixes it
[Galaxy S 4 Active Original Android Development] O-T:
1122, dirty flashed, cache clean

+1 for [MENTION=4968404]theMasterplan84[/MENTION] issue when WiFi is on and then enable BT. It has been some strange hiccups before when using QuickAccess buttons http://xdaforums.com/showthread.php?p=56256562

I was able to get WiFi on using on/off switch under System without reboot.

It is reproducible.

1. WiFi on

2. BT on

3. WiFi shut down by itself.

1119 has same issue.
[Galaxy S 4 Active Original Android Development] spegelius:
In CM12 this seems to be a problem too:

1. WiFi on

2. Turn BT on

3. Turn BT off

4. WiFi icon gets an exclamation mark and seems to require off/on toggle

Might be driver related...
[Galaxy S 4 Active Original Android Development] DiaboluZ:
1120 seems OK here, switching BT on/off/on... connected or not to a headphone doesn't change wifi connection. BT on is sucking battery though :p
[Galaxy S 4 Active Original Android Development] O-T:
1.

Tested all nightly from 1119 to 1122. Still shutdown WiFi when BT turn on.

When Mobile networks and WiFi is enabled, Internet is served from wifi, BT on doesn't kill WiFi when BT is turned on.

2.

Also curious about another line in same commit. Only jf has exfat set:

jf

CONFIG_EXFAT_FS=y

jactivelte

# CONFIG_EXFAT_FS is not set

Is exfat support disabled for jactivelte?
[Galaxy S 4 Active Original Android Development] spegelius:
Not disabled, kernel driver just isn't used for exfat/f2fs. They are mounted using fuse and external exfat/f2fs libs.
[Galaxy S 4 Active Original Android Development] pen²:
Did anyone notice that the charging speed went down compared to Samsung tw rom? I'm playing ingress, an augmented reality game which uses lots of battery (display on, gps on, graphic effects). With Samsung tw, I could play with an external battery and a dedicated charging cable and my battery would still be charged a little. With cm nightly, it is constantly drained a little while playing. Charger is the same for both roms - any idea what could do?
[Galaxy S 4 Active Original Android Development] Droidilc:
Can i install this on ATT- SGS4A i537
[Galaxy S 4 Active Original Android Development] O-T:
Seems you already found the answer by yourself

http://xdaforums.com/showthread.php?p=57277135

It's also emphasized in first sentence of OP in this thread.

AT&T SGH-i537 has locked bootloader. Browse the S4A xda-forum for "Safestrap" and advice given by user [MENTION=3047491]Devo7v[/MENTION]
[Galaxy S 4 Active Original Android Development] jot82:
I have the same issue, charging is slower than expected and when I use my phone while charging (surfing the web, facebook, etc) the battery slowly drains. I thought maybe my charger is broken and does not deliver enough Amps anymore, but if this is ROM related I won't have to get a new one ;)

Other issues I have with this ROM:

* no manual provider search possible (this seems to be a bug for a lot of Qualcom phones, see CYAN-4902), a bit annoying if you are around border areas or do not have a signal with your own provider and want to check how others perform.

* after rebooting (and deactivating "get time from network" or using flight mode) the system date gets set back by about 9 months and some days (if I reboot two or three more times, it gets further back by 9 months each boot, so phone does not "forget" the time but something is reverting it)... according to some Google in the web this is also related to Qualcom chipsets and time_daemon... after renaming time_daemon this is fixed for me (have to do this with every nightly installation again). See CYAN-4915

I don't know if you guys are able to reproduce this - if so please upvote those bugs ;)
[Galaxy S 4 Active Original Android Development] spegelius:
Another solution for time problems is to use pre-KK time_daemon (and proapbly libtime_genoff.so). I have this on my own github device props, but it hasnt been accepted to TheMuppets props repo, for reasons unknown.
[Galaxy S 4 Active Original Android Development] monkeydogger:
I've been using this as a daily driver for a few weeks now and I am really impressed. :good::good: I'm currently using 11-20141209-NIGHTLY-jactivelte.

Battery life is outstanding, although I don't use a lot of social media apps - My battery last for about 1 day 18 hrs with general use (including Bluetooth to my car stereo, calls for work (a few hours a day), email for several accounts etc)

I did have a problem after using the nightly automated update at one stage but this was cured with a clean install........... I can only attribute this to a corrupted write process.

I have to say that I'm not a fan of the launcher and prefer to use Nova - But that's probably inherited from using SlimRom on my S3 for so long.

There is a small issue with the camera over exposing pictures when using the flash - I have no idea of how or why this happens - does anyone have a recommendation for settings to prevent this or a better camera app?

I haven't seen any of the wifi / Bluetooth interaction issues as described by others but will keep an eye out for them.

Thanks to everyone involved in developing, and bug testing this build. Great Job. I think it's going to take a lot of persuading to get me to move to CM12 now this is "stable" (I know it's only a nightly build).
[Galaxy S 4 Active Original Android Development] naveenmat98:
Cm 12 is already pretty stable for me haha and its now my daily driver
[Galaxy S 4 Active Original Android Development] Koraiem:
Inconsistent Mic issue

I've been using this Rom since the earliest nightlies, and it's overall performance is great, however, I've been experiencing an issue for the past 2 months, the phone Mic when in calls often sends a very low volume or a very ambiguous voice, sometimes the other person cannot hear me at all. Whilst the headphone Mic works perfectly.

I can't tell for sure if it's a software problem because i can't afford trying other Roms right now, but I've been updating the Rom every other day or so, and i think it's one of the updates that caused this. Is anyone experiencing a similar problem?

It's hardly a hardware problem because the Mic works fine in sound recording apps such as whatsapp voice messages..

Great work Spegilus and all other dev. And i wish to see a stable version soon!
[Galaxy S 4 Active Original Android Development] FORC3:
MTP isnt working anymore

I have the problem that my device wont get recognized by the Android File Transfer app (Mac osx) anymore, since the last update.

The problem has to depend on the rom because other devices get mounted via MTP perfectly.

I tried with and without usb-debugging enabled.

I am using build 11-20141206-NIGHTLY-jactivelte

Does anyone else have the same problem?

Any suggestions how to fix this?

EDIT:

Ok, nevermind - i found it. The last update completely disabled the mtp/ptp options in settings.

I just rebooted, and activated MTP and its working again.
[Galaxy S 4 Active Original Android Development] O-T:
[MENTION=3876105]spegelius[/MENTION]

1220 nightly

build.prop

ro.product.name=cm_jactivelte

Terminal - getprop

ro.product.name=jgedlteue

Not sure how far back in nightlies this strange new name jgedlteue appeared or why. What happened to jactivelte?
[Galaxy S 4 Active Original Android Development] spegelius:
jgedlteue is in default.prop, in initramfs. Don't know why, but it seems to be that on jf devices also... i have a hunch that it might be something related to some proprietary lib which expects certain product name.
[Galaxy S 4 Active Original Android Development] spegelius:
I recently installed CM11 as a Multirom insllation for testing newer KT kernel on it. I noticed that camera seems to be messed up, basically taking picture with flash on has a long lag before it takes the picture and when it takes the picture, it takes it exactly same time as flash fires and picture is all white. Also hdr and toggling flash hang the camera (can't connecto to camera after a while). Anyone else notice this? I'll have start digging wth has happened in jf or camera...
[Galaxy S 4 Active Original Android Development] anbugge:
I see the same thing, using 20141209. I'm guessing it's the same issue for monkeydogger too (also on 1209): http://xdaforums.com/showpost.php?p=57444373&postcount=1077
[Galaxy S 4 Active Original Android Development] Wegaxas:
Yes, for me to. Exact same. High lag, hdr and flash toggel brakes cam.

On 20141223 and 20150111.

If camera hangs, top shows in Terminal a still running camera process. Batery drainage is then quite high, too. Only reboot resolves it. After, the berserc cam proces is gone, and battery drainage is back to normal.

Wifi , Bluetooth, GPS, calling works fine.

Once in a while i See random reboots. Annybody else experiances random reboots?
[Galaxy S 4 Active Original Android Development] spegelius:
Alright, so it's not related to Multirom or KT kernel. I'll start digging for possible cause
[Galaxy S 4 Active Original Android Development] spegelius:
Was browsing through jf-common commits and found this: https://github.com/CyanogenMod/andr...mmit/c672de7749ccf7ae8aebb6cd7b4c927333b6e77d

One of blobs seems to need certain name in props.

Been searching for the thing that breaks camera, but no luck so far. Camera app, camera framework code, kernel and makefile changes checked so far...
[Galaxy S 4 Active Original Android Development] O-T:
Thanks for chasing this. Hope it's not hard coding making trouble downstream.

jgedlte = S4 GT-I9505G Google Play Edition

Does Active have the humidity sensor this commit is made for?

Bevare the Thanks Button ;)
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm good question... i haven't seen any libsensirion related errors in logcat, but since i haven't been searching for them, might've missed them.

For the camera, workaround seems to be to set focus setting to Auto, that way pictures with flash aren't overexposed. I'm still trying to find what commit has broken this, but reverting most of the camera related stuff to around september hasn't helped so far...
[Galaxy S 4 Active Original Android Development] O-T:
Last build 20150105

http://download.cyanogenmod.org/?device=jactivelte

Has Jenkins "left the building" ?

[emoji12]
[Galaxy S 4 Active Original Android Development] spegelius:
Depends if there are any relevant changes to make a build. OTOH, CM devs don't really communicate to me about what happens with jactive, so could be anything...

Edit: jactivelte is still on cm-11.0 build targets list, so apparently no updates to cm-11.0
[Galaxy S 4 Active Original Android Development] spegelius:
Seems that there can't be simultaneous cm11 and cm12 nightlies. So these will end when cm12 nightlies are enabled.
[Galaxy S 4 Active Original Android Development] sam.crowther:
NO Bluetooth on today's update..

*Dirty flash and downloaded with Cyandelta*
[Galaxy S 4 Active Original Android Development] monkeydogger:
[MENTION=4204064]sam.crowther[/MENTION] - I had the same issue - Fixed via

reboot recovery - Clear cache then dalvik cash

reboot - turn off wifi - turn on bluetooth - turn wifi back on.

It may work without the clear cache / dalvik cache step.

[MENTION=3876105]spegelius[/MENTION] - Is this fixable via the same method proposed in the CM12 build? Looks like it manifests itself and cures itself in the same way ;) http://review.cyanogenmod.org/#/c/85827/

Hope this helps.
[Galaxy S 4 Active Original Android Development] spegelius:
Edit: that option is already removed in CM11 jf-common vnd_jf.txt... so no effect.
[Galaxy S 4 Active Original Android Development] O-T:
20150118

Big Thanks to [MENTION=3876105]spegelius[/MENTION] for hunting down the carrier search issue [emoji111]

All carriers are now visible.

Bluetooth can be switched on if done before WiFi. If Bluetooth is switched on while WiFi is on, it will hang waiting until WiFi is turned off.

Repeatable, no need to reboot.
[Galaxy S 4 Active Original Android Development] spegelius:
I pulled latest changes to jf-common yesterday and there was same bt commit that was merged to cm12 ('un**** bt vendor props' or something). However, not the latest which fixes the wifi/bt interop bug. I'll make a build after work and see if it fixes it.
[Galaxy S 4 Active Original Android Development] spegelius:
Indeed the bt fix for CM12 seems to work in CM11 also, tuning wifi/bt on/off in different combinations and no problems Granted, didn't have any bt devices connected.... Hmm, i wonder if someone is going to make a commit about it... or maybe i'll just do it meself
[Galaxy S 4 Active Original Android Development] O-T:
If you found other way than the removed vnd_jf.txt - why not?

Good to have CM11 as a kind of stable while jenkins do weekly builds of it (if I'm right).

On the other hand - a crossroad emerging after CM12 nightly started.
[Galaxy S 4 Active Original Android Development] spegelius:
My original comment about the viability of the fix in cm-12.0 was wrong, since i didn't have latest cm-11.0 branch commits. There was other bt related commit to that same file. So the original fix works.

I cherry-picked the CM12 commit and submitted it to review.
[Galaxy S 4 Active Original Android Development] spegelius:
Aaand the bt fix is merged. Dunno if there's still CM11 nightlies coming since CM12 started?
[Galaxy S 4 Active Original Android Development] O-T:
Nice. The thing is that you instructed Jenkins to stop CM11 before that one.

http://review.cyanogenmod.org/#/q/owner:spegelius%40gmail.com,n,z

The commit you did here

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

stopped CM11 and activate CM12 - if I'm right?

ATM I don't have a private build bot setup to do the job.
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah, that seems to be the case. I was kinda expecting cm11 and cm12 to exist simultaneously, but i guess not... if needed, i'll make builds myself from now on. I've been digging into the camera code and might be quite a project...
[Galaxy S 4 Active Original Android Development] monkeydogger:
Read the update numbers carefully !!!!!!!

Just a word of caution to those that wear glasses...... The automated update check also pulls down the numbers for CM12 builds..... Ended up with an unhappy afternoon putting things back to CM11.... My fault...I should have put my specs on..

That being said....CM12 build is pretty good... Just not as stable as CM11 for me at the moment. I kept getting a lot of Bluetooth failures and I travel in my car a lot and kinda rely on it.

That being said.... The camera is pretty darned good... But I still don't like the white backgrounds...... Basic black works for me. Really responsive, great smooth animations.... Look forward to the finished product and some nice black themes... Lol.
[Galaxy S 4 Active Original Android Development] Grinface:
Same with me... :cyclops:

Also the CM Updates webpage for CM11 log isn't longer available (obviously moved to CM12).

Are there any new automated builds or CM11? Or has development stopped?

Grinface
[Galaxy S 4 Active Original Android Development] FORC3:
Why does the cm11 and cm12 builds get mixed together? Will there still be cm11 builds in the future, or am i forced to switch to cm12 to stay up to date?
[Galaxy S 4 Active Original Android Development] spegelius:
Apparently CM11 is done for, at least nightlies have switched to CM12. I'll have to ask about this from CM devs, if i ever get hold of them...

I'll be making few builds once i get the camera sorted out. Currently need to focus on work and 2nd work stuff... so might take a while. Feels like one-legged man in ass-kicking contest...
[Galaxy S 4 Active Original Android Development] spegelius:
Finally found out what causes the camera to over-expose the pictures with flash on: face-detection seems to be on all the time in CM11 camera and for some reason jactive's camera doesn't like that. I've been debugging the parameters Samsung camera and CM camera apps send to the drivers with similar settings, but none of the differing settings have helped. So the first option is to disabled face-detection for jactive. I also found few other problems and probable fix for the random hanging when changing settings.

Once i get some answers about CM11's future from CM devs, i'll be either committing the fixes to CM repos or start maintaining my own builds.
[Galaxy S 4 Active Original Android Development] O-T:
Glad to hear you are still working on cm11. Maybe the code can also gain your CM12 if needed.

Most commits to http://review.cyanogenmod.org/#/q/status:merged have been for recovery in branch CM11 since January 20th. Lot of activities in branch CM12. Understand that CM11 is hard to abandon when so close to stable that you can smell it. [emoji41]

I've not yet jumped on to lollipop because the stability offered by CM11 is my current need.
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, camera debugging hasn't been in vain in regards CM12, lot's of new insights. I'll be implementing same stuff over there once i get this stuff polished on CM11. Camera has always been problematic, hopefully from now on less so.
[Galaxy S 4 Active Original Android Development] spegelius:
Ok, so there has been some talk about M13 release, but apparently not worth holding your breath while waiting that to happen. I'll be making some unofficial builds with camera fixes, so they get some testing before i'll push them to gerrit
[Galaxy S 4 Active Original Android Development] spegelius:
Build cm-11-20150126-UNOFFICIAL-jactivelte.zip uploading to Google drive. All from CM repos, except the camera fixes.

After fooling around with the camera for a while, testing different settings and modes, no crashes and no visible problems with pictures (didn't look too closely, though). I haven't tested with any other camera app than what CM provides.

Edit: link: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing
[Galaxy S 4 Active Original Android Development] Grinface:
Nice :D

No problems found so far. Tested BT, stock camera, Pixlr, Perfectly Clear. All working fine.

Thanks a lot.
[Galaxy S 4 Active Original Android Development] tasken:
Hi spegelius, thanks for your great work!

Is there any chance of getting a CM12 build with this camera fixes? commits seems to have chilled after lasts days of rush.

regards.
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, of course. Probably have unofficial build ready tonight.
[Galaxy S 4 Active Original Android Development] O-T:
0126 unoff.

Bt/wifi/mobile data switch on-off any combination of order.

Some E/ Logcat

E/BTEventHandler(21084): A4WP is not supported

E/AudioManagerAndroid(18430): BLUETOOTH permission is missing!

This is when not paired with any device, not tested pairing and audio stream BT calling. Those functions has been good long time official and hopefully in unoff. 0126.

Not had any fc in cm camera switch HDR, flash, resolution, front using auto focus. Face detection circle seen only in front camera.
[Galaxy S 4 Active Original Android Development] spegelius:
I take that the logcat lines are just obervations and no real problems? I usually ignore all errors in logcat, unless i'm specifically searching for something which i know is broken. There's so much errors and warnings which don't mean anything bad that one has to filter them to keep depression out... ;).

Good to hear that the camera is working. Yes, face detection is only for front camera now. I have few options to try to get it enabled for back camera also, but no promises.
[Galaxy S 4 Active Original Android Development] O-T:
0126 didn't? have camera fix for face detection and exposure, still I have had no fc.

I might interpret this wrong if repo sync was from cm and Camera fixes are locally added by you. Then the fixes are in 0126 [emoji4]

Logcat is mere observation.

IR function not tested.
[Galaxy S 4 Active Original Android Development] spegelius:
None of those fixes are in CM repos yet. 0126 build was my own, with unmerged changes, not pushed even to my own github.
[Galaxy S 4 Active Original Android Development] moviecut:
Didnt test the build with the camera fixes yet. I didnt get the full conversation about it here. Is the problem with the delay between taking a picture and seeing the animation that it gets stored? I noticed, that i didnt get that delay, when i take a picture out of my telegram app. But i whould be really happy to see it fixed in the normal camera app! For me, lollipop isnt an option for now. I testet cm12 for about a day, but i really missed my xposed modules....so i think i will stay on kitkat for the next month...

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] FORC3:
Same here. I think lollipop (cm12) isn't done yet and nor its a full replacement for kitkat (cm11).

Gesendet mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
If you mean with the delay between taking pic and the save animation, yes it's fixed by disabling face detection for back camera.