yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] spegelius:
I compared the las_kmsg lines to AOSP bootup and those lines are there too, so nothing to worry about (well i hope at least:). It seems that the kernel spits out a lot of 'errors', hard to tell what is important and what not.

And the logcat... well to me it seems that the mediaserver is SIGSEGVaulting every now and then, causing the boot loop because servicemanager can't get all the required services running. Also the permission problems... i saw those with AOSP too, apparently they aren't bad. And do note that i haven't installed gapps, that's a fresh boot after factory reset/rom flash.

Yesterday i made a build with kernel that has most of the stuff from jf merged and with active/jf mix of blobs. Boots ok, until the same mediaserver bootloop. I added some debug to AudioPolicyManager and to my suprise it boots up to the 'Welcome to Cyanogenmod' screen, but com.android.phone keeps FCing and i can't use the phone... :(

Also, god damn Cyanogemod... why does it disable ADB after first boot? It's really frickin nice to get up to this point and then lose all the ability to debug the damn thing!
[Galaxy S 4 Active Original Android Development] patzyalex:
The install process must've gone bad at some point, for some reason. Anyway, before installing a new ROM via recovery, I always wipe data, cache partition and dalvik at least once and I install the gapps zip immediately after the ROM zip, without rebooting or anything. Never had a botched installation.

Good thing you've managed to handle the situation. The 03.05 build is the best so far.
[Galaxy S 4 Active Original Android Development] koutsa:
Of course I didn't... Did go "all natural" :D (Of course I shoulda have done that... :o )

By the way, is Titanium a good way to backup this ROM? CyanogenMod -account seems to be a littlebit crippled, does not do a backup?

EDIT: [MENTION=4630187]allram[/MENTION] just realised that it can't be a corrupted download since I now am running the same installation and everything seems to work alright. Maybe it's just that I first installed 23.4. build > installed 3.5. build (of course w/ cache+dalvik wipe) > then after testing camera crashes > again installed 23.4. build (w/ wipes). Maybe it got stuck somewhere in the middle... Well anyway it works now.
[Galaxy S 4 Active Original Android Development] patzyalex:
ClockworkMod Recovery (CWM), the same one you use when installing zips.
[Galaxy S 4 Active Original Android Development] allram:
I use titanium to backup apps and data to one .zip that i flash when i do a factory reset :)

CWM for normal rom backup.
[Galaxy S 4 Active Original Android Development] koutsa:
I assume this is a noooob-question (and sorry for being off topic), but I'll still ask it:

If you do a backup w/ CWM, and your having flaws/problems in your current build (that's why you do a factory reset, right?) - aren't those same problems repeated if you restore that backup?

That is the idea I had in mind when asking if Titanium would be the right way (back up only apps & data?) ? It would be nice and easier to do a factory reset if you wouldn't have to redo all the setups w/ screens, folders, account informations (wonder if they're ever going to be backed up by any means, though)...
[Galaxy S 4 Active Original Android Development] allram:
I use CWM in case something goes wrong in the update i'm installing.

Titanium with app+data backup in one .zip file for use after factory reset, so all my apps etc is installed when i restart :)
[Galaxy S 4 Active Original Android Development] patzyalex:
"Factory reset" doesn't necessarily mean flashing back TouchWiz, it means restoring the current OS/ROM/build to the default values. Thus you can reset CM11 too and it will ask you to configure it all over again. About backing up the whole ROM with CWM, yes - you are also backing up the flaws in it. But you never know when you may need to recover a bricked phone and a .zip backup will work a lot faster and easier than flashing TouchWiz back (via Odin). You can also backup your preferred TouchWiz ROM with CWM, just to return to something you've already configured, as opposed to a brand new, factory default/reset ROM.

For backing up apps, I also use Titanium Backup, but there are other apps as well. Some of the restored apps may not work properly if transfered from TouchWiz to CM or vice-versa.

For restoring contacts and calendar I just sync with Google.

The other things/folders/shortcuts/screens you customize have to be manually reconfigured the way you like them. That can be a pain in the ass, so I just take screenshots and use them as guidance.

You can also use a dual boot system, I've done that for a few months and it can be useful if you want to test newer builds all the time. The first OS has to be TouchWiz. Check it out: http://xdaforums.com/showthread.php?t=2610224
[Galaxy S 4 Active Original Android Development] 6783:
Hello. Does anybody know how to enable softkeys on cm11?
[Galaxy S 4 Active Original Android Development] patzyalex:
That will take some of the screen real estate.

Did you try Xposed Framework with GravityBox module for KitKat?

http://xdaforums.com/xposed/modules/app-gravitybox-v2-9-1-tweak-box-android-t2554049

Of course, you won't be able to use ART runtime, but good old Dalvik.
[Galaxy S 4 Active Original Android Development] allram:
Latest build is up:

https://drive.google.com/folderview?id=0BwwLmYElvFOmRkF4WGhEbFNoMG8&usp=sharing

Practically same as Spegelius's with sound volumes raised. Call and video sound is much better now :)

Hope we get KK from Samsung soon, so we can try to fix HDR and use KK blobs..
[Galaxy S 4 Active Original Android Development] patzyalex:
Good job, man. Keep up the good work.

Sammy is a fat guy with little interest in bringing us skinny kids the sweetstuff. Let's just hope that, when they give us KK, it will be less troublesome than it was in the U.S...

Sent from my GT-I9295
[Galaxy S 4 Active Original Android Development] koutsa:
Tried instagram with spegelius's 3.5. build - instant FC. And after that system says "cannot connect to camera" or something like that.

And another noob question about installing / updating builds:

When installing new build, do you guys recommend cleaning cache and/or dalvik cache? And in what order, first cache clean and then install new build (+gapps)? Asking this because I just don't remember how that process should be done correctly (2years since I last played with AOSP ROM's). Is the updating somehow different with ART now?

Lähetetty minun GT-I9295 laitteesta Tapatalkilla
[Galaxy S 4 Active Original Android Development] allram:
I flash the update, clean cache and dalvik, reboot. wait 5min then reboot again.

I run ART and it feels smoother, might just be me imaginating tho :P
[Galaxy S 4 Active Original Android Development] spegelius:
Personally i just flash it, screw cleaning caches ;). Actually, the installer formats /cache and /system so that happens automatically. So that leaves dalvik cleaning to the end user.

I think the order of things is to first clean what you are going to clean and then install what you are going to install. With /cache it shouldn't matter, at least with CM as CM installer only formats the /cache and doesn't write anything to it. Not sure of other roms...

No experience with ART, but shouldn't be different?

About the camera:

* as we are making the stock Camera app working by tweaking hard coded settings on the application, i don't believe they make any difference with other camera apps, unless they ask the settings from Camera app (and i'm not sure that's even possible)

* the problem with video resolution change is unimplemented config key (needsEarlyVideoSize) in CM11 sources. Implementing it now, let's see it it works...

* with CM11 and msm-8960 devices (Qualcom S4 at least?), there's a camera wrapper written in c. If i've understood correctly, this wrapper makes it possible to control the camera properly, without needing per-app settings (i.e. camera app wants to take HDR picture, commands are sent to wrapper which applies proper parameters before forwarding the command to the actual camera driver). Next step would be to make the wrapper understand our camera driver. In theory it should be possible, i believe (actually, hope is more like it...) that the Qualcomm camera drivers use common API. Investigation continues
[Galaxy S 4 Active Original Android Development] patzyalex:
ART makes a noticeable difference 4 me, things are really running smoother. The circle around the Cyanogen robot during boot logo only rotates one and a half times and boom - I've reached the lockscreen and the phone is usable.

About the flashing steps, I agree with [MENTION=3876105]spegelius[/MENTION], one needs to clean things first (cache/system/dalvik) and then install what needs 2 be installed. As a proper paranoid, I wipe them all out before flashing ROMs and gapps.
[Galaxy S 4 Active Original Android Development] olarf:
If the camera freeze / FC, just empty cache and data from the camera and galery APP and everything should be fine again.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] koutsa:
Is enabling ART when running CM recommended? When I'm going to change from dalvik > ART, CM gives me a nagscreen about it.

And yet another noob-question: If I changed to ART, should CWM also be updated? (CWM now has "clean Dalvik-cache"-option, is it "Clear ART-cache" when running ART? :) )

Now running [MENTION=4630187]allram[/MENTION] 's new build from today: So far the camera seems quite a lot more stable. Had 1 freeze > FC > had to reboot when played with the cam presets and one freeze > fc > did not have to reboot phone when switching on / off various settings...
[Galaxy S 4 Active Original Android Development] patzyalex:
No, enabling ART is an experimental feature.

What's a nagscreen? :D It should ask for restart and that's it. If it's smth worse, there must be some sort of conflict. Xposed framework, for instance, is incompatible with ART. After booting with ART enabled, you should know there are apps which aren't yet supported, i.e. they will crash: http://www.androidruntime.com/list

CWM is just fine as it is, I don't understand if "clearing ART cache" would be relevant in any way, it's beyond my knowledge. Let's leave this to other people.

If you have trouble enabling ART from CM, you can easily do it from CWM: http://xdaforums.com/showthread.php?t=2707841
[Galaxy S 4 Active Original Android Development] koutsa:
<info> Nag screen is a popup-screen that nags about <insert_topic_here> ;) :D </info>

If I'm about to choose ART instead of dalvik in the developer's menu, it says "CyanogenMod does not support ART because ART is an experimental feature and it may cause instability, force closing and even prevent the device from starting up. ..... blaa blaa.... Are you sure you want to change from Dalvik runtime to ART runtime?"

That's what it asks me :)
[Galaxy S 4 Active Original Android Development] patzyalex:
That's the nag... It's a positive nag, you are just being warned. If it were smth like "you r goin 2 burn if u touch this button" - that would've been really naggy.

If u're anxious about this, backup the ROM with CWM and u'll be safe if anything, although not much can happen. It enables ART or it just doesn't. And that's it. There's no nuke behind the setting :D

And, of course, I'm not responsible 4 whatever... :fingers-crossed:
[Galaxy S 4 Active Original Android Development] ZeroZorro:
I did try ART but the first app I used (SmartOffice) FCed so for now back to Dalvik.

Have to say it seemed to be more smooth like other people stated before.
[Galaxy S 4 Active Original Android Development] patzyalex:
SmartOffice is in the crap list 4 now, see 4 yourself

http://www.androidruntime.com/list

My OfficeSuite Pro 7 works properly, as per the same list.
[Galaxy S 4 Active Original Android Development] spegelius:
Woo, i got the CameraWrapper working; to do that, prop camera.msm8960.so must be coped as system/lib/hw/camera.vendor.msm8960.so.

Good news is that now it should be possible to set all the parameters independent of the camera app. Bad news is that switching from video to still, it crashes... time to debug some c.

Also, previous needsEarlyVideoSize parameter didn't help with video resolution change. I'm tempted to start porting AOSP 4.4 to see if it's camera app is such b*tch or are these anomalies just in CM11.
[Galaxy S 4 Active Original Android Development] patzyalex:
Good news indeed. Sounds like you're on the right track. Keep us posted.
[Galaxy S 4 Active Original Android Development] alirey:
Hello allram, spegelius,

another user has posted his at&t sg4a kk files. All credits to [MENTION=2128768]sagi232123[/MENTION]

Maybe its usefull for you ;)

Alll the lib files from i537

Enjoy...

https://www.mediafire.com/?n4qk4mn9v45cfgs
[Galaxy S 4 Active Original Android Development] allram:
Thanks :)

Will take a look at this tomorrow, hopefully good News :D

edit:

Tri'ed to build today, only using the new lib files, still no camera fix.

We need more files like those in /proprietary/bin /cameradata /etc /vendor folders :(
[Galaxy S 4 Active Original Android Development] koutsa:
Don't know if it's just me, but I'm experiencing much more better battery life with this unofficial CM11 than with previous (stock 4.2.2) ROM. Even when I have now kept the setting "Performance" on, battery life is significantly better.

By the way, is there any possibilities to have App2SD -support on this build? It'd be awesome. Correct me if I'm wrong, but you can't have apps move to ext SD on this build, can you?

Check this for example: http://xdaforums.com/showthread.php?t=2383143
[Galaxy S 4 Active Original Android Development] spegelius:
You might be right about the battery lasting longer, i've had similar feelings about later builds. Good job CM devs :).

As for the additions, yeah they shouldn't too hard to implement since the patches are available. But that would be another rom and thread. If only i had time... currently very limited time for development (not counting actual work) so not much happening. I did a SlimKat build since it's just repo sync + make and short test. It seems to have same camera problems so i'll try to tackle them maybe weekend. The camera wrapper investigation hasn't progressed, must go deeper into the camera code...
[Galaxy S 4 Active Original Android Development] allram:
Made a build yeserday, but some problems with CM fixes and many of the devices who are running nightly builds got a "busy" signal while calling every 4sec..

Fixed today, and made a new build. Seems like there are some bluetooth fixes for those who had problems with that as well :)

https://drive.google.com/folderview?id=0BwwLmYElvFOmRkF4WGhEbFNoMG8&usp=sharing
[Galaxy S 4 Active Original Android Development] mythi:
forget
[Galaxy S 4 Active Original Android Development] allram:
Download it to a Computer with google drive and upload? :P dosent Dropbox support ftp uploads? I'm gonna do a New build tomorrow myself :)
[Galaxy S 4 Active Original Android Development] mythi:
forget vaiolation
[Galaxy S 4 Active Original Android Development] a2441918:
What build did u do?

Sent from my SOKP powered Galaxy S 4 i9500.
[Galaxy S 4 Active Original Android Development] olarf:
Dies one of you is planning to move this build soon over to the official cm11 repository? I ASK because up from then we can also Start building a PAC Rom for our device. At least this unofficial one rom is very good developed!!!

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
After these conditions are met: http://wiki.cyanogenmod.org/w/Doc:_Submitting_A_Port

Propably never as we don't have the underwater camera setting (if you adhere strictly to the above conditions). Also current camera problems should be fixed before that.
[Galaxy S 4 Active Original Android Development] olarf:
Good to know that you generly plan to do it. I read the rules already before I asked and the points you came up with are also the only ones I See so far, hopefully the Sammy KK isout doon for us and provide some solutions for those 2 (1 real) bugs. For underwater pics/Video I use my gopro and never thought about using a device limited to 1 Meter ;)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
Well getting this to official status would be nice, but for some reason those CM requirements are really discouraging me... but let's see when/if those camera problems can be resolved.

Camerawrapper: got it working, so far it works like the previous method; HDR setting crashes etc., video resolution change makes crap videos. Meh. I think i'll flash my AOSP build in dualboot mode and test camera there to see if these problems are AOSP 4.4 related or so. I'm beginning to wonder if 4.4 skips somekind of camera init command when changing settings...

Also i downloaded the NC2 image from Samfirmware and i've been playing around with the blobs. Some findings:

modem.bin and NON-HLOS.bin can be flashed, i'm now on ML2 baseband

using RIL files from NC2 rom disables mobile network. Wifi works. With previous ril everything seems to work (didn't test gps)

camera files from NC2 work mostly:

normal picture mode has some bug with exposure, preview fades to black very fast. Manually setting exposure to +2 shows something on the screen when moving the camera fast to bright targets, but then it goes to black. Resulting image is black

Video seems to work, but resolution change makes crap videos

There's also quite a lot of differences with what files exist in the NC2 build. For example, few radio related files aren't there and don't know if they are needed. For now, i copied them from previous blobs. But it's really hard to know what is needed and what isn't. I also found some camera related files which aren't included currently, i'll try adding them.
[Galaxy S 4 Active Original Android Development] pen²:
What needs to be done in order to extract and flash baseband/ril?

It is good to know they are flashable, I always didn't want to flash stock just for baseband updates ;)
[Galaxy S 4 Active Original Android Development] spegelius:
In linux/(osx?) do this:

download NC2 firmware, from Samfirmware for example

untar the tar.md5sum package

modem.bin and NON-HLOS.bin are there to be flashed with Heimdall

sudo heimdall flash --MDM modem.bin

sudo heimdall flash --APNHLOS NON-HLOS.bin

It reboots between flashes. And i'm not responsible of borked flashes

In Windows, use some tool to extract the tar.md5sum package and flash with Odin. Haven't used Windows for this for a while, don't remember what needed to be checked etc...

To get stuff from system.img

use simg2img to extract system.img.ext4 to system.raw

mount system.raw to /media/temp or somewhere

Little progress with the NC2 blobs:

got radio working, now phone works with new ril files. Turns out the location of certain files was changed from system/lib to system/vendor/lib

LTE speed tad slower than MF2 or something i had previously: 75/22Mbps vs. 85/18Mbps. Could be just normal variance...

Been having slow GPS lock times for a while, but tried with new ril blobs and Sports Tracker got lock almost instantly, inside the house. Anomaly? Tried twice, worked both times. Need to test more for a few days...

Camera seems to work except the blackout bug in picture mode. Don't really know what to do about it...

And to clarify, all previous camera settings bugs are there
[Galaxy S 4 Active Original Android Development] Laum:
Could you post the new modem files since sammobile download is really slow?
[Galaxy S 4 Active Original Android Development] spegelius:
Here you go: https://drive.google.com/folderview?id=0BzJzDM42pkRvU1FLZF9sX1JUdjg&usp=sharing

---------- Post added at 09:42 PM ---------- Previous post was at 08:43 PM ----------

Camera testing with AOSP 4.3:

HDR switching seems to work, but flash is still on. Taking picture ok

Restarting camera, HDR is on and flash is gone. Taking picture ok

Disable HDR, flash comes back on. Taking picture OK

Disable flash and camera freezes. Need a reboot

After reboot, not touching settings. Taking picture freezes, need reboot

After reboot, set flash back on. Taking picture OK

Disable flash and try HDR again. Freeze, reboot...

Video: switching resolution without restarting Camera app produces crap videos

So there it is, camera really hasn't been working properly ever in AOSP based roms. So back to debugging... Seems to be centered around HDR and maybe flash. The video problem seems like a bad/missing init command or something...
[Galaxy S 4 Active Original Android Development] marcelser:
exfat problems in all builds CM10.2/CM11

Hi,

I really love the CM builds from you guys spegelius and mythi and all the others, but I'm very surprised that no one reported the exfat problems in these roms. If you have tons of apps installed and you're copying thousands of files exfat just gives errors. On my device this happens constantly with TitaniumBackup. So I started testing if it's an error with TitaniumBackup or if it's a general exfat problem. So I switched Titanium to internal card and problems were gone. Then I copied the TitaniumBackup folder from internal to external sd card and ES Explorer reported an error repeatedly. Not always with the same file, the error happens randomly. Sometimes it copies 20% of the files sometimes, then it bails out at 74%, 37%, 11%, 82%, so I stopped trying any further. in my test case, I tried to copy about 1600+ files with a total size of 3.73GB.

Then I thought maybe my sdcard is bad and I replaced it with a brand new Samsung SDXC UHC-I 64GB card (which is the same size & type I had before just a different manufacturer) but the problems still exist. And I have/had this problems in all CM11 builds and they also existed in CM10.2 which I used before. In CM10.2 I then formatted the card to fat32 and problems were gone. As there were lots of reports that exfat in CM10.2 is unstable and it is fixed in CM11 i switched to the CM11 build. But obviously it's not. Since I use CM11 with card formatted with exfat problems are back. ROM works perfectly apart from that, but for me it's kind of a showstopper because fat32 is just so terribly slow. Can anyone confirm this and is there a chance that this will be fixed. Does anyone know if an AOSP ROM would have different exfat drivers or are they all the same since they are somehow based on some parts of code from LeJay?

Thanks for any help on this.

Best regards,

Marc
[Galaxy S 4 Active Original Android Development] sicHiRsch:
Hi there,

I just flashed rom and gapps from the first post in this threat (may 5th build), but after a reboot the cm logo spins once and then the phone sits on a black screen. Does anyone have a suggestion on what to do?

Cheers
[Galaxy S 4 Active Original Android Development] patzyalex:
Boot in recovery.

Wipe data, wipe cache partition, wipe Dalvik cache (although [MENTION=3876105]spegelius[/MENTION] prefers not to wipe anything).

Install again the CM11 zip, install gapps.zips right after that, without rebooting between the installs.

Reboot.

It should work.

If it doesn't, check the zips, maybe they got corrupted.
[Galaxy S 4 Active Original Android Development] sicHiRsch:
Did all that, same thing though. I made cwm show me the log and that says the following:

I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.

mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: Invalid argument

W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)

Signature check: Enabled

I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.2/mmc_host/mmc2

I don't know if those errors may have anything to do with it?
[Galaxy S 4 Active Original Android Development] patzyalex:
Are you using CWM 6.0.4.7?
[Galaxy S 4 Active Original Android Development] sicHiRsch:
yes