yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] spegelius:
Copying stuff from system image wouldn't work, the stuff in sys image needs to be working first ;). Currently it isn't, i had accidentally deleted Android.mk files from all -caf repos :/. And they seems to be needed, display driver won't be compiled without them. Now building again, but the caf libs cause more build problems as Google's version of some libs don't support qcom yet. So back to hacking... I've done some copying from CM, more than i'd like. But then again, if those files are needed to support our hw in aosp, so be it.

Also the system.img und userdata.img are ext4 filesystem images, which i believe, are directly written to partitions when flashed with fastboot. And apparently there;s no fastboot in S4. The images can be opened of course. But just copying stuff to another zip propably won't work, because CWM flash does more than just extract files to /system. It makes symlinks around and sets permissions to files. Yesterday i learned this the hard way, at one point i noticed that none of the binaries in /system/bin had execute bit on :eek:
[Galaxy S 4 Active Original Android Development] Devo7v:
First let me start off by saying that I have the i537, so I can't test anything you guys are doing, but I think you're doing a great thing for the Active and keeping development alive.

I see that you guys are working on compiling AOSP from scratch and learning how the Android OS works, this will undoubtedly help tremendously in the future. While I believe compiling ROM and creating ROMs will help continue development on the Active, I'm not sure that it would provide the most benefit. Let me explain, a couple years ago when the first Galaxy S phones came out there were several different variants also (Galaxy S, Captivate, Vibrant, Fascinate). These phones were more or less the same with minor hardware tweaks. Each of these phones had their own forum and development occurred independent of each other for awhile. At some point (I'm not sure exactly how it happened), but people figured out that you could flash a ROM meant for the Galaxy S to the Captivate and just flash a Captivate kernel afterwards to get ROMs to work. So essentially ROMs became device independent as long as you flashed a device specific kernel.

Maybe this is the same sort of thing you guys could do with the Active. There are tons of S4 ROMs whether they be for the i9505, i337, i545, etc so it doesn't seem to me that there would be much benefit to creating more ROMs. I think the most beneficial thing to do would be to develop S4 Active kernels that could be flashed. I think [MENTION=3037405]ohwarumbloss[/MENTION] created a thread with the purpose of creating a zip that could be flashed after flashing a regular S4 ROM but it doesn't look like it went anywhere. I think if you were able to create a TouchWiz-based kernel and a AOSP-based kernel you should be able to cover 90% of the ROMs.

I'm not trying to diminish the work that you are doing and I know compiling a ROM will give you endless amounts of information about Android, but I hope that one day it can be as easy as picking one of the countless ROMs for the S4 and flashing a S4 Active kernel on top of it to have a fully functioning S4 Active with a brand new ROM.

Keep up the good work and I can't wait to see what you guys come up with. Good luck.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
true-android.blogspot.nl/2014/01/install-xxubml3-android-422-jb-firmware.html

Edit: something went wrong but this is the link to firmware updates for those having trouble with SamMobile downloads as earlier stated in this forum.
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Well said and I totally agrea with you!

But (there has to be a but) we have some Problems :

- Different Display

- Different Camera

- No updated Kernel (afaik)

So, there are more things that seperate us from i9505 than it was back in the days with i9000/i9100 and and and...

This is absolutely out of reach for me so all my hope lays on [MENTION=3876105]spegelius[/MENTION] and [MENTION=3912380]LeJay[/MENTION] or probably another Developer who finds his/her way here...

Downloaded the Firmware but couldn´t see any advantages so I´ll stay with MK3/CM10.1

I created a Thread today, maybe it is interesting for some of you guys here :

Dualboot for i9295[a touch of Freedom] :)

Works for me and is a step into the right direction :)

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] spegelius:
With certain limitations, yes, it should be possible to do this. But, a lot of depends on stuff like:

- lib versions used when compiling specific rom

- device blob (proprietary libs) versions in specific rom

- hardware lib and their versions...

- compiler version? Propably not much...

For example about mismatched libs, i got another build of AOSP made, now with qcom caf libs. For some reason the kernel isn't built properly currently, so i'm using a kernel from CM build i have backed up. It does boot, but no picture, screen just flashes. Reason for that is that the graphics service dies on SIGSEGV with hefty stacktrace, meaning there's some slight mismatch with different libs and some ill memory handling or something happens and caboom. The kernel sources are the same and qcom caf libs also...

Now, with I9295 and i537, i think that this could work very well because the hw should be essentially the same. All that is missing is CM kernel sources for i537. But between S4 and S4 Active, it gets harder to pick roms with compatible libs, becuase for S4 there are a lot of ROMS and propably a lot more different combinations of libs... but any one feeling adventurous can download the ROMs and start swapping files :). It's time consuming, but it could produce something that works.
[Galaxy S 4 Active Original Android Development] mrps2:
So this might be good news for us (I9295):

http://www.smartphonesupdates.com/android-4-3-update-now-available-for-the-samsung-galaxy-s4-active/

and thanks to xAJCx who have got the .cfg file and uploaded it

http://xdaforums.com/showthread.php?t=2611278

Maybe the more experienced guys in here can manage to make it work for I9295 or make the fixes on CM?
[Galaxy S 4 Active Original Android Development] spegelius:
Ah yes, this could e interesting. I haven't any experience with Samsung roms, but might be worth looking in to at some point. Kernel might be a big problem...

Anyhoo, i'm still strugling with the AOSP build:

for some reason, even though kernel is built and boot.img is made, it fails during start and adb complains about /system/bin/sh not found. Replacing boot.img from CM, it boots (but no picture...). I extracted the kernel and ramdisk from boot.img and they seems fine but dunno...

replaced surfaceflinger stuff from CM sources and now boot fails differently ;). Screen flashes and phone goes to bootloop. Before it flashed screen as graphics service was restarting itself again and again. Cannot get logcat because adb doesn't have enough time to see the phone :(

did more thorough compare between CM and AOSP build .mk files and noticed some compile flags, gonna try them next. Also searching for QCOM make definitions might be a good idea.

all in all, seems that adding a QCOM device to pure AOSP is a pain in the arse...
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Wow, a lot of Problems :(

I really hoped it would be easier to get Vanilla running. I didn't try in that direction but maybe the i9505 Forum holds a AOSP Rom that could be used to compare some stuff..

I am on that Dualboot thingy right now and really happy. Most time I'm on CM anyways but it feels very good to have Sammy just in case..

Need to read me through backup and restore of that before I start something else..

Battery Life and Performance of 27th build is really good, btw (like the builds before as there where no big changes I think)

Let me know if there's anything I can do!

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] spegelius:
Indeed, a lot of problems. But some small progress anyways:

- now the build does boot without using CM boot.img. There was some system tools missing, copied them from CM repos

- found out that kernel stores it's last log to /proc/last_kmsg and now i'm looking at it and trying to figure out why kernel panics. The highlighted part points to GL subsystem or something, so it would seem that there's still something related to display or GL drivers...

- haven't lost hope :). Now the system i have makes a build, so most of the work should be done. Now to figure this bug out...

8.640899] [mdnie lite] mDNIe_Set_Mode end , mode(0), background(1)
[ 8.748138] mdp4_overlay_borderfill_stage_down: no base layer at mixer=1
[ 9.035827] diag: Invalid Msg type 12 proc 2
[ 9.154266] Unable to handle kernel paging request at virtual address b6f881eb
[ 9.160522] pgd = dcc80000
[ 9.163269] [b6f881eb] *pgd=9e0d2831, *pte=00000000, *ppte=00000000
[ 9.169464] Internal error: Oops: 17 [#1] PREEMPT SMP ARM
[ 9.174896] Modules linked in:
[ 9.177886] CPU: 2 Tainted: G W (3.4.0-cyanogenmod-g95ba80f #2)
[ 9.185058] PC is at 0xb6f6826c
[ 9.188110] LR is at 0xb6f6cb03
[ 9.191253] pc : [<b6f6826c>] lr : [<b6f6cb03>] psr: 200f0010
[ 9.191253] sp : b5df94c0 ip : ffffffff fp : b6f881eb
[ 9.202697] r10: b5df9b8c r9 : b5df957c r8 : 00000000
[ 9.207977] r7 : 00000006 r6 : b5df9e38 r5 : b5df9e3c r4 : 00000000
[ 9.214416] r3 : 00000073 r2 : 00000073 r1 : b6f881eb r0 : 00000003
[ 9.220977] Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
[ 9.228118] Control: 10c5787d Table: 9e08006a DAC: 00000015
[ 9.233917] [B]Process GL updater[/B] (pid: 562, stack limit = 0xdcd202f0)
[ 9.240631] ---[ end trace 94342ac627a0c03a ]---
[ 9.244750] Kernel panic - not syncing: Fatal exception in interrupt
[ 9.251068] CPU3: stopping
[ 9.253753] [<c010b9d4>] (unwind_backtrace+0x0/0xe0) from [<c010ab5c>] (handle_IPI+0x120/0x204)
[ 9.262481] [<c010ab5c>] (handle_IPI+0x120/0x204) from [<c0100468>] (gic_handle_irq+0xa8/0xb4)
[ 9.271026] [<c0100468>] (gic_handle_irq+0xa8/0xb4) from [<c0105abc>] (__irq_usr+0x3c/0x60)
[ 9.279388] Exception stack(0xdd745fb0 to 0xdd745ff8)
[ 9.284393] 5fa0: 0000003c 00000055 42f934a0 00000008
[ 9.292602] 5fc0: 41c86a58 00010000 80040002 be9f9748 406bd858 00000000 42f94b28 0000000f
[ 9.300750] 5fe0: fffffe70 be9f9738 402dbe1f 402dd008 800d0030 ffffffff
[ 9.307312] CPU1: stopping
[ 9.310028] [<c010b9d4>] (unwind_backtrace+0x0/0xe0) from [<c010ab5c>] (handle_IPI+0x120/0x204)
[ 9.318725] [<c010ab5c>] (handle_IPI+0x120/0x204) from [<c0100468>] (gic_handle_irq+0xa8/0xb4)
[ 9.327270] [<c0100468>] (gic_handle_irq+0xa8/0xb4) from [<c0105900>] (__irq_svc+0x40/0x70)
[ 9.335662] Exception stack(0xde359eb0 to 0xde359ef8)
[ 9.340637] 9ea0: de05aec8 40000013 7f147f14 00010000
[ 9.348846] 9ec0: de05ae80 00000009 de05aec8 00000024 00000000 00000059 40000013 00007dd8
[ 9.356994] 9ee0: 00000000 de359ef8 c03d7e3c c08a31b8 60000013 ffffffff
[Galaxy S 4 Active Original Android Development] spegelius:
AwwwwYYeeaahh! Got it working finally. Woo, it seems that the problem was wrong proprietary libs, for some reason i had the blobs from Samsung MK2 release... i was sure that i copied them from latest SlimRom package. Oh well, now it boots :).

There's some problems however:

- QCOM related changes have broken some services. First was GPS, which i fixed (phone wouln't boot fully before fixing). Another is Bluetooth, similar problem (function arguments have changed. Java versus C++ function definitions don't seem to be picked up during build... :/ )

- Wifi cannot get IP. Wifi authenticates, but dhcp gives up after timeout...

- No root. Gonna add SuperSu to the package and see if it works.

- Same problems with camera as CM has. Plus one new, video looks crap during recording (like a really low resolution), but the result is ok (at least 1080p)

- No APNs defined, have to feed those yourself

Other than that, didn't notice any other problems during the hour i used it. Gapps went in fine. Had to switch to CM because Sports Tracker wanted bluetooth and restarted whole Android UI each time...

Hmm, propably gonna make another thread for this later
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Awesome! I'd love to try, any chance you'll upload it as a test version?

New thread would be good, I think.

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] baaldfg:
STK app for Dual Sim

Hi all,

I am using a Dual Sim adapter. Does this room include a working STK app which works with the current MagicSim Dual Sim adapters?

Thanks for your answer.

Best wishes,

Christian
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
There is a Stk inside but I have no idea if this will support dual Sim at all.

You will have to try :)

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] baaldfg:
Thanks Thomas, in that case I will try and report back for any other Dual Sim users.

Best wishes,

Christian

---------- Post added at 09:55 PM ---------- Previous post was at 09:38 PM ----------

Hi all,

I want to test the ROM but I have Team Win Recovery installed with which I am rather happy happy happy. Is CWM recovery really necessary to install this ROM?

Can I just flash the zip files in TWRP?

Best wishes,

Christian
[Galaxy S 4 Active Original Android Development] spegelius:
Aosp discussion here: http://xdaforums.com/showthread.php?t=2395242. Test reports welcome.

Oh and i added the cm-10.2 roomservice.xml to https://github.com/spegelius/manifests/tree/cm-10.2.
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Where did you get TWRP for the I-9295? Link please.

---------- Post added at 08:18 PM ---------- Previous post was at 08:16 PM ----------

All over it, but that link comes back to this thread. The correct link is:

http://xdaforums.com/showthread.php?t=2621883
[Galaxy S 4 Active Original Android Development] baaldfg:
I don't know exactly. It was installed by the software package I used to first root the phone. I just haven't changed it as it seemed to work fine.

Best wishes,

Christian
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
As long as you're using a recovery that's made for your phone there will be no problem.

But, installing CM will install it's own recovery so you will lose your twrp.

Don't forget to make a backup before you do anything and you'll be fine :)

Also, you may use dual boot, I've written a little how to in general forum.

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] mythi:
i can help in debugging , if any dev needs help ;);) just got my new gs4a or users of gs4a in general
[Galaxy S 4 Active Original Android Development] spegelius:
I made a newer build few days agot, to tes some changes. Download here: https://drive.google.com/folderview?id=0BzJzDM42pkRvRzhHUEtPSGllSm8&usp=sharing

Changes:

- some kernel changes copied from S4 kernel, doesn't seem to affect usage. But report if anything seems odd

- changes to camera quality settings. I haven't done any comparison to earlier pictures or videos, but i assume it should be better

- repo sync done tuesday
[Galaxy S 4 Active Original Android Development] sam.crowther:
Daily ROM.

that. is. all.

Thanks, much appreciated to have CM on ALL my devices...
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Hey [MENTION=3876105]spegelius[/MENTION] :)

Son has a broken Arm but now back at home and I can finally play with my active again ;)

Yesterday, in the evening, I've set up the latest build for dual boot and it's just awesome!!

Finally Runtastic is tracking accurate again (even stock is inaccurate, shame on Sammy) and the battery life is great! Will leave Sammy as first, just in case, but there is no flaw, yet!!

One thing, the stock CM Cam shows blue pictures and the flash is crap. But it's not the Rom because as far as I tested, Focal is working 100% ok.

Thank you very much, once again, for your effort!! Hoping for better financials next month and will surely drop some euros ;)

Greetings

Thomas

P.S. S4Active is doing ok in the rain, better than the driver ;)
[Galaxy S 4 Active Original Android Development] spegelius:
Another build made: cm-10.2-20140316-UNOFFICIAL-jactiveltexx.zip, uploaded to drive.

Changes:

Camera fixes, 720p and lower video works properly now

HDR doesn't crash camera. However, looking at logcat messages, the pictures propably aren't hdr. Seems Active's camera parameters need more tweaking... if possible at all.

Tweaked audio volumes to match original jf settings
[Galaxy S 4 Active Original Android Development] mythi:
idk...but just wondering ... will these changes come to your cm 11 builds ?
[Galaxy S 4 Active Original Android Development] spegelius:
Actually currently working on it :). I did all the camera stuff with these older roms because they are more mature, just change something, build and test. I had a look at CM11 camera and things have changed, settings aren't changed like with Android 4.3 roms... but getting there.
[Galaxy S 4 Active Original Android Development] mythi:
Haha...you are just a hero in my eyes ,take your time ... your cm build is running like a dog ...I was just waiting for an update to squash some more bugs to give more proper dirty ports hope you find solutions to every bug ... this community is almost compelete :o it has devs ports people and is growing day by day with out your work this state woulf have never been reached , anyway lets see what you have for us :cool:
[Galaxy S 4 Active Original Android Development] LeJolly:
You can do it! :)
[Galaxy S 4 Active Original Android Development] snadge:
Woops, yeah I did forget to do that. :silly: After fixing that and a few other minor things, I finally got CM10.2 booting, without touchscreen support. There's a few patches from the Samsung kernel that sorted that out, and now I'm pretty much where you are. A somewhat working CM10.2 without camera.

For some reason I haven't been able to figure out, the menu and back buttons aren't working. I had a look at and a play around with board-jactive_eur.c, and noticed the Samsung kernel changes the ordering of the home button within the button array. This doesn't seem to make any difference though.

Can we put up some build instructions for 10.2? Maybe start a new 10.2 thread? It would be cool for those who are keen, if we could sync up with your current 10.2 base and build roms from that.
[Galaxy S 4 Active Original Android Development] aquarat:
You guys are awesome... I'll buy you beers when you get it working lol.
[Galaxy S 4 Active Original Android Development] snadge:
Okay, so with a bit of help from LeJay, noobnl and a couple of others on irc, and some keyboard smashing and hair pulling, I'm currently running CM10.2 on my S4 Active. So now I'm at a point where I too can have a look at the camera, and end up in a mental asylum a few days later. :eek:

Crashing camera's are uncool. What I think would be beneficial, is if we could have a bit of a discussion about the camera code in its current state, and how the i9295 differs from the i9505. What kernel driver and proprietary libs are we talking about? Are we missing any firmware? Does anyone have any insights into how the camera code may have changed between Android 4.2 and 4.3?

I think at this point, I'd like to encourage people who are interested in developing, fixing bugs, testing, or would just like to keep up with those who are, to stop by #SGS4 on the Freenode IRC network. Point your IRC client at chat.freenode.org, or head over to http://webchat.freenode.org if you don't have an IRC client, and want to chat with your web browser. The S4 Active is a little bit under-represented in this channel, so it would be good to slant the topic of discussion more in our favour. ;)

*edit* As a follow up to this post, I found out the hard way that call audio (incoming or outgoing) isn't working for me on my 10.2 build. I saw a bunch of errors in logcat about alsa missing an input device, so I'm not sure what's going on there. Since it was an important work related call that I just missed, I have restored back to 10.1. :(
[Galaxy S 4 Active Original Android Development] tigrone:
Hi, unofrtunately the link to the kernel does not work ! Says your account still has to be validated on that site :(

Any chance you have hosted the kernel .zip somewhere else ? And has it been tested (I am guessing it did) ?

Cause I am looking for a working AnyKernel structure for the S4 Active to be able to flash my self-compiled kernel !
[Galaxy S 4 Active Original Android Development] LeJay:
I think I found my way to the irc channel. I'm trying to fix the camera in 10.1. After that 10.2 should be easy.

The front cam is the same and actually works if you download an app the accesses the front cam before the rear. The rear cam driver is in s5k3h5xa. There's a imx175.c file that implies it's the same camera as sgs3, but its set as off in the kernel. Maybe they made a late change in hardware or im just confused. There are some libchromatix files that probably need to be added to /system/lib.

But... mm-qcamera-daemon seems to crash pretty early regarded of what lib files I have.

Sgs4a liboemcamera.so contain references to s5k3h5xa so it seems reasonable that we need to replace that. But yeah, im pretty confused
[Galaxy S 4 Active Original Android Development] Devo7v:
I'm not sure if this would be helpful, but @DerTeufel1980 compiles and modifies CM10.1 & 10.2 for a lot of different Samsung devices (see HellyBean). He also builds his own kernels for these devices, so he would probably be able to help you out. I would suggest PM'ing him, he's normally pretty good about responding.

I really hope we can get some developers over here to develop ROMs for the S4 Active, better yet maybe somebody could develop a kernel that would allow us to flash regular S4 ROMs to our phones.
[Galaxy S 4 Active Original Android Development] LeJay:
I don't think the problem is the kernel.
[Galaxy S 4 Active Original Android Development] snadge:
LeJay - Does in call audio work for you in your 10.2 build? I had a very brief poke around with it before I flashed back to 10.1. There are a few minor differences in audio_policy.conf, but I didn't have a chance to try to look into it further. I remember seeing a kernel or logcat message which said something like alsa cannot open capture device. Given that most of the dev focus is on 10.2 at the moment, it seems logical to me try to get the camera working with that. Does CAF have any updated kernel or camera stuff that could be of any use?
[Galaxy S 4 Active Original Android Development] LeJay:
I don't know.. I'm back to 10.1 and focusing on the camera. I prefer having one problem solved before I find more :).

EDIT: speaking of which, I just got it working. Well, I can take pictures anyway. Video and other stuff to come. Feel like an idiot for taking this long.
[Galaxy S 4 Active Original Android Development] johngreener:
Very Nice. Might have to try it!