yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] snadge:
I've noticed that my microphone doesn't work in the current 10.1 build (1.1), if I place a call on speaker. Certainly not a show stopping thing, but it is a casual annoyance. Particularly if you're not aware of it. Oh well.

I synced my 10.2 repo and spat out a build last night, still no call audio at all in that one. Speaker or earpiece. Kind of annoying, because the sounds, microphone (voice note recorder) all seem to work fine. Bluetooth audio etc, no problem. Someone with some experience of how call audio routing works, may be able to point me in the right direction. I have had a look at simple things like audio_policy.conf, but I seem to be grasping at straws.

I don't want to sound like too much of a whinger, but I'm kind of dismayed at the lack of activity for this device. It's taken quite a while for XDA to even bother to create a seperate category for it. Of course that's nobody's fault (except maybe Samsung) for nearly screwing up a device that could have been at least as popular as the regular S4. AT&T get an equal share in the blame, for completely gimping the USA market, which has a massive influence on the popularity/success of any given device, from a developer perspective.

On that note, I'd like to publically acknowledge the work LeJay has done in particular, creating and maintaining both this thread and the recovery thread, which is of enormous assistance to anyone who actually wishes to get in there, and get their hands dirty. Well done! :good: It is just a shame that so few have chosen to publically take advantage of that, so far.
[Galaxy S 4 Active Original Android Development] :
this rom boots right?
[Galaxy S 4 Active Original Android Development] aquarat:
/me starts downloading cm10.2 source :D .
[Galaxy S 4 Active Original Android Development] mrvovven:
Hosting space

I can give you hosting space on a web server with unlimited bandwidth if you need.
[Galaxy S 4 Active Original Android Development] LeJay:
It would be great with a mirror. The compile finally finished, so I put it up on dropbox.
[Galaxy S 4 Active Original Android Development] mrvovven:
Ok.

I PM you login
[Galaxy S 4 Active Original Android Development] LeJay:
Thanks. It's up.
[Galaxy S 4 Active Original Android Development] snadge:
I've just built this rom using the above described method, and got my prop files from the supplied github link. Copied them into where they are supposed to go (I think, it confused me). Anyway, everything appears to be working except I don't see any camera preview. I've obviously ballsed something up. :silly:
[Galaxy S 4 Active Original Android Development] LeJay:
You're supposed to use the extractfiles shell script (in device/samsung/jactiveltexx) in order to copy the files. I'm not sure I understand what you did. The rom is also,up, so you can download that
[Galaxy S 4 Active Original Android Development] snadge:
I tried copying the files from the github link provided in the OP. I wasn't exactly sure of the structure or where to put those files. Usually they go into vendor/samsung. Anyway, I flashed your build 10.2 rom, camera worked on that. Ran extract files, rebuilt the rom, and now it appears to be working. :) So I must've had a derp moment when copying the files into vendor/samsung, or simply copied the wrong ones. No matter.
[Galaxy S 4 Active Original Android Development] LeJay:
You can't just manually copy the files into vendor. The extract files script builds makefiles as well as copying them.

I do see a lot of reports on issues with Titan and cm10.2. I don't use Titan so I can't test myself, but did you try:

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

I don't think there's any reason to install supersu on cyanogenmod, unless someone specifically suggested it as a solution.
[Galaxy S 4 Active Original Android Development] msmall22:
Is this a working ROM now?
[Galaxy S 4 Active Original Android Development] aquarat:
I just want to say... I've been using this ROM for the past couple of hours and it is AWESOME :D .

Thanks LeJay!
[Galaxy S 4 Active Original Android Development] skimboynemo:
its great rom since CM has not released their official yet, thanks for the hard work.

just flashed and everything seems working fine, has not tried the HDR or other fun in the Camera set, but normal shoot works brilliant, I will try out few days then will update more thoughts.

again, thanks alot for this rom.

re

T
[Galaxy S 4 Active Original Android Development] colida:
Just a quick question. The IR Sensor isn't mentioned, so I assume it is working properly?

Big thanks to the developer!

Cheers

Edit:

Just found out, that you can use Samsungs "Watch On" App. Should work, but I did not try it yet.
[Galaxy S 4 Active Original Android Development] LeJay:
If the hardware is the same as in SGS4, it should work. At least in theory :). I haven't tested though.

Camera HDR does not work and it will crash the camera app. A 3rd party camera app, such as CameraMX will probably give a better experience for the time being.
[Galaxy S 4 Active Original Android Development] aquarat:
This ROM is amazing LeJay! It's actually usable :D . I tried it today and my battery disappeared really quickly(12 hours)... but I think it's because I was doing speed tests on LTE the whole time :P (LTE and the CPU were the major reasons I got the phone over my Nexus 4).
[Galaxy S 4 Active Original Android Development] snadge:
Just a heads up everyone. I don't want to steal LeJay's thunder, but the next build may or may not include a fix for the low quality video camera preview. ;)

Make sure you guys click "Thanks" on the OP, and whenever someone posts something that you personally find useful/informative. :good:
[Galaxy S 4 Active Original Android Development] msmall22:
Is there a way to speed up the Wi-Fi connection? It's the only thing that seems slower than stock. Great work!
[Galaxy S 4 Active Original Android Development] LeJay:
Hah... I really don't mean this as stealing my thunder back, but I think I solved that. Don't know if you've solved it a different way?

Also, by removing ZSL you can make hdr mode slightly more stable. Though, I think the problem is deeper. Look at logcat and /proc/kmsg when the camera app is open. It's a mess. I'd love to talk to someone from sgs4 development team.
[Galaxy S 4 Active Original Android Development] emersonas:
So far so good. Nice ROM.
[Galaxy S 4 Active Original Android Development] snadge:
No, I had only just noticed your patch when I synced, but saw that the build hadn't been updated, and that it hadn't been noticed or mentioned yet.

I haven't ever played with HDR before, so I don't think it's something I'm really going to be all that bothered about. If that's the only issue of great concern. Happy days. :laugh:

I have noticed that the lowest volume setting for the loudspeaker, is actually quite loud. Turning the volume up above that, makes it louder again, and at the highest levels, it's quite distorted. I wonder if there's a gain setting somewhere that can be adjusted, or if that's just normal.
[Galaxy S 4 Active Original Android Development] LeJay:
No, I hadn't mentioned it. Sorry if you spend time coming up with same solution. I, for one, have certainly spend way more time on this stuff than I should :).

I'm really just learning on the fly, so i don't know how volume is adjusted, but I'd guess it's similar display brightness that's controlled by device a file:

# echo 0 > /sys/devices/platform/mipi_samsung_full_hd.2305/lcd/panel/backlight

turns backlight to lowest setting. It's probably some user space setting(i.e. not the kernel) how volume is adjusted.

Edit: It could be some of the audio blobs. They are still taken directly from SGS4:

# Audio

lib/libacdbloader.so

lib/libaudcal.so

lib/libcsd-client.so
[Galaxy S 4 Active Original Android Development] mrvovven:
LTE data problem

I am now using CyanogenMod 10.2 - 20130910 rom.

It's running nice, but i have one problem. When I'm connected with LTE my mobile data is not working. It looks like it only works wit 2G.

*edit*

I solved the problem, looks like it was a problem with the network operators OTA config.

If you are user the Swedish operator Tele2/Comviq you need to manually enter the APN: 4g.tele2.se to get LTE data to work. The default internet.tele2.se was not working for me with LTE.
[Galaxy S 4 Active Original Android Development] dest4b:
On my 9295 it works without problems..

only the light sensor seems to be a bit confused.

Also i did not tried the HDR function.

puh im away from touch wizz ;)
[Galaxy S 4 Active Original Android Development] ShimaMiku:
Is this now usable on the AT&T version via SS, or are we only suppose to use AOSP at this point?
[Galaxy S 4 Active Original Android Development] Fortune090:
Use AOSP for now. When installing the zip for this, it comes up with build.prop errors and won't install.
[Galaxy S 4 Active Original Android Development] ShimaMiku:
Okay, thank you!
[Galaxy S 4 Active Original Android Development] leonpr:
Just got 10.2 installed. Working great so far, thanks again :)
[Galaxy S 4 Active Original Android Development] br0adband:
Just to ask so it's out there in the open once and for all:

Since we can now install custom ROMs on the GS4A I537, the AT&T variant with the locked bootloader, using Safestrap is there any chance this ROM can be modded so that it'll install without crapping out because of detecting the wrong device during the initial stage of flashing it? Safestrap (using TWRP) craps out at the detection of the device due to mismatched build.prop info.

I attempted to modify the build.prop to match as close as I could the "settings" seen used in the AOSP ROM that a lot of us are now using but it still takes a dump during that device check. Since the I9295 and the I537 are in essence the same devices, this device check seems to be all that's holding me/us back from installing/using this 4.3 based ROM on the AT&T variant with Safestrap and I'd sure as hell love to see what it can do.

You folks are much better at this stuff in terms of modifying the ROMs and knowing how to get the devices detected properly, but it would be pretty damned awesome to see how Android 4.3 fairs on the GS4A I537, most definitely. ;)
[Galaxy S 4 Active Original Android Development] LeJay:
I still haven't understood how safe strap works. Does it allow you to change the kernel?
[Galaxy S 4 Active Original Android Development] Devo7v:
Unfortunately not quite yet. Hashcode is still working on getting custom kernels working, so currently SS only supports stock kernels. If you take a look at the third post in the SS development threat you can see the procedure for installing ROMs in SS. This probably means that we can't install this ROM via SS until custom kernels can be used.

On the bright side there's no harm to users to installing incompatible ROMs since the stock rom remains untouched. So it may be possible to install this ROM and try to run the MF3 kernel with it and see what happens. I think all [MENTION=907867]br0adband[/MENTION] is requesting is for a way to be able to flash this ROM using SS so he can then flash the MF3 kernel and see what happens. Hopefully you can help us out.
[Galaxy S 4 Active Original Android Development] br0adband:
I don't think the MF3 kernel modules (for the 4.2.2 kernel) will work with this 4.3-based ROM, my intention is just to get the damned thing installed period and then see about getting the hardware to function a piece at a time.

Right now because the ROM will not install whatsoever that's the sticking point. Gotta get it installed to see what's borked and then be able to fix it... ;)
[Galaxy S 4 Active Original Android Development] LeJay:
Yeah, it checks for the device name so it refuses to install on the att version. You can simply remove the first line of the updater-script. If you're not sure how, I can upload a version that by passes the check.
[Galaxy S 4 Active Original Android Development] br0adband:
Seriously, that's all it takes? Ok, so let me see here... which line should I yank out or would it be better for you to perhaps post an SG4A I537-specific version of the ROM (which would get you my ever loving gratitude, and I'm sure I wouldn't be alone)... ?

I'm still somewhat new to modding a flashable ROM zip so in some respects I'd prefer you tell me specifically how to do this... just extract the zip, go in and edit the updater-script removing the first line? I'm gonna try it and report back.

/me runs off...
[Galaxy S 4 Active Original Android Development] LeJay:
In META-INF/com/google/android/ there's a file called updater-script. It handles the install. The first part of that file says.

assert(getprop("ro.product.device") == "jactive" || getprop("ro.build.product") == "jactive" ||
getprop("ro.product.device") == "jactivelte" || getprop("ro.build.product") == "jactivelte" ||
getprop("ro.product.device") == "jactiveltexx" || getprop("ro.build.product") == "jactiveltexx");

Remove that line and save. Delete CERT.RSA, CERT.SF and MANIFEST.MF in META-INF/. Then sign the entire thing with testsign.jar and flash. Sorry, it's not the most comprehensive guide ;).

You can probably also change the device name to jactivelte in build.prop and it should flash.

I'm also uploading to dropbox, so you should be able to d/l that in 10 mins or so.
[Galaxy S 4 Active Original Android Development] br0adband:
Yah, I tried the edit and rearchived as zip and of course it just went all dead and nothing... BUT... Safestrap to the rescue, yank the battery and I'm good to go, I should have gotten into this whole Android side of ROMs and tinkering years ago, never too late I suppose.

/me still has much to learn

Will be patient (taps foot very aggressively as he's typing this) and wait for your "professional" edits. Thanks...

One last question: I'll test the I537-specific ROM when you post it, but should I do that without using the MF3 kernel modules? Shouldn't I see how things go with just the native ROM itself first, and then perhaps try flashing the MF3 kernel modules and see what happens? Seems like the best course of action but I know the default 4.3 ROM isn't going to handle the hardware as it should, that's pretty much a given.
[Galaxy S 4 Active Original Android Development] LeJay:
Dropbox crashed. Have to re-upload with my great 1mbit line :).

I'm honestly not completely sure what the challenges are to get it running with stock kernel. I think several hardware specific libraries expect certain functions to be implemented in the kernel. Functions that simply aren't there. Not sure how that'll work out. I'm mostly just learning as I go.

The link will be up in half an hour or so on http://felia.linje12.net/lejay/cm-10.2-20130917-UNOFFICIAL-jactiveltexx-noassert.zip

It's still uploading. It's done when the file size is around 225 mb.
[Galaxy S 4 Active Original Android Development] br0adband:
Thanks again. I got sick of Dropbox and their slow damned upload speeds and finally started using Google Drive for this kind of stuff, the uploads are basically "uncapped" and I have a 20Mbps upload (as part of my Cox Ultimate package, 150Mbps down/20Mbps up) and I can upload pretty much at close to 2MB/s without issues to Drive, it's pretty damned awesome.

Dropbox takes/took forever, disconnected me entirely too much whether I used the browser or their dedicated software, and I finally said "ENOUGH IS ENOUGH" and moved on... :D

Stepping out for a few to see some friends but I will test this ASAP and report back.

As for your earlier question about Safestrap and the kernel thing, I'm not honestly sure but it seems like when you use it you're basically hijacking the boot process of the device and then turning the control over to Safestrap which passes control to whichever ROM/slot is active as set. Hashcode would be the man to ask for that info, obviously.

<I just uploaded your ROM to my Drive account, took all of about 45 seconds... :D>
[Galaxy S 4 Active Original Android Development] AndroidState:
Can I have the link?

Please give me the link. :angel:

Thanks,

TransformixS4
[Galaxy S 4 Active Original Android Development] yankeesfan714:
I'd like to take you up on the version that bypasses said check. Thanks in advance.

Never mind. I saw the post up there^^

GT-i9295(i537) running SafeStrap

---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------

So [MENTION=907867]br0adband[/MENTION] we just flash ROM,modules, and camera fix as we did before right?

GT-i9295(i537) running SafeStrap
[Galaxy S 4 Active Original Android Development] gamephreaker:
Version bypass

Could you please upload it it makes it easier then trying to edit on my phone.
[Galaxy S 4 Active Original Android Development] gamephreaker:
Boots into black screen :(
[Galaxy S 4 Active Original Android Development] LeJay:
Sorry, I should probably have been clear.

he wanted a build that would install on the att version. I was actually almost certain it wouldn't work.

It was part of a one on one conversation. But im learning to be more careful about what I post :)
[Galaxy S 4 Active Original Android Development] gamephreaker:
I understand

I am also try to run it on att via SS. I can say I don't think it is fully installing installs way to fast.
[Galaxy S 4 Active Original Android Development] LeJay:
Cm is much more lean than stock roms and installs much faster. But I couldn't tell you what the issue is. My point was you're getting caught up in a development conversation. That's fine, but unless you can get me more technical details, I can't really help. I'm neither running ss nor the att version.
[Galaxy S 4 Active Original Android Development] gamephreaker:
Understood I will stay out of the way and let br0adband work it out with you. 1 quick side note I would love if the otg ethernet drivers are included in the build.

Thx and good luck!
[Galaxy S 4 Active Original Android Development] br0adband:
Yeah, it's a black screen/stuck device issue, not sure what's causing it on the I537 - the "install" process seems to happen much much too fast, and during the "install" there's no updates of any kind on TWRP which is something I usually notice: most ROM builders/makers will add in some kind of log text so you see what's going on, or tag the ROM with their identifier, etc - that doesn't happen here, all you see is "Installing..." and then that's it, in a matter of seconds.

I know the GS4A is powerful but it ain't that powerful, so somewhere down the line the install process just isn't working. And again, it could be because we're using Safestrap which is hijacking the phone's boot process to get around some restrictions, but some other ones might just be causing grief in this whole process for 4.3, or it could be just this particular ROM, or a whole host of other things, I really can't say for sure.

Wish I was more knowledgeable about this stuff and could just crank out a pure clean 4.3 ROM that worked 100% for everyone... would be damned nice at this point. :p
[Galaxy S 4 Active Original Android Development] whizz:
Wow! I just installed this to my S4A, and so far I think it is AWESOME! Great work!
[Galaxy S 4 Active Original Android Development] uvbeenzaned:
Black screen for me too.

Sent from my Galaxy S4 Active.
[Galaxy S 4 Active Original Android Development] LeJay:
I'm sure people appreciate the help. Just a few notes, the assert line is already removed from the updated script from the modified upload. I have no idea how ss handles mounts, so,that could potentially be an issue. I did try early on to get CM to boot with the stock kernel, but didn't get anywhere dropped it in favor for a kernel from source. It may not be rocket science, but it's really hard to find good sources of information on the ins and outs of how he setup works.

I hope I didn't give the impression I'd work on this. I neither have the time or an AT&T sgs4a to figure out how to fix it.
[Galaxy S 4 Active Original Android Development] gamephreaker:
Plus I know the display drivers are different between the S4 and the S4 active
[Galaxy S 4 Active Original Android Development] br0adband:
Which is completely understandable and we all appreciate your efforts even this far. If I had a spare I537 I'd send it your way but but but... :p

I think that would probably be the biggest culprit more than anything else considering the differences in the display hardware - the obvious result for trying to force or run something for the GS4 on the GS4A and not having complete support for the GS4A's LCD panel (even in spite of both using the same Adreno GPU) and associated display controllers would be a black screen and a 'dead' device.

We'll get it worked out in time, I'm sure. Right now the AOSP ROM works fantastic, and someone just dropped a hint that potentially there could be a 4.3 official ROM coming for the I537 in another thread as soon as tonight, but haven't had any confirmation of it (was just posted like 15 minutes ago - meaning the prediction/rumor - so we'll see what happens).

I'll believe it when I see it... ;)
[Galaxy S 4 Active Original Android Development] LeJay:
If you have the time, you can consider trying to port the 4.3 version of the google experience SGS4. It's possible the kernel for SGSA could function together with that. I recall manage to boot it in mine, but the touchscreen was funny. Maybe you have better luck. If an official 4.3 kernel for the active is released, I would certainly have high hopes that could be used together with the 4.3 google experience.

Edit: just a quick search, perhaps something like this: http://xdaforums.com/showthread.php?t=2404687 and then add the kernel modules provided for ss
[Galaxy S 4 Active Original Android Development] whizz:
BTW, I also noticed the notification LED no longer works for apps (GMail, WhatsApp, SMS); however it does work when you're being called..
[Galaxy S 4 Active Original Android Development] killkillkill:
The display driver you are referring to, is built into the kernel. Since the i537 can't have its kernel changed due to the locked bootloader, you are guaranteed to maintain your proper display drivers.

This is not likely to be the problem.

When we got the initial 4.3 drop and started working on it for Samsung Relay/S3, there were a bunch of kernel changes needed in order to make it light up the screen. There were changes to surfaceflinger that had to be adapted to. This is why I was suggesting in my last post that the kernel may be the stumbling block.

Just what is needed.... locked down even harder. Believe me when I say that this is not a good thing, because the root exploit being used now will be patched up. Its fine if you've already taken control, yes, it can be useful, but when you have people who don't know any better actually accepting the update, and new units shipping with the update, it is definitely bad.
[Galaxy S 4 Active Original Android Development] JEZZEJAMEZ:
Sent from my SAMSUNG-SGH-I537 using Xparent BlueTapatalk 2
[Galaxy S 4 Active Original Android Development] :
Now I can build some roms, but I need testers because I don't own this phone. Anyone?;)
[Galaxy S 4 Active Original Android Development] dave5777:
Are you talking about the i537? I can be a tester :) I've only Odin'ed my phone a couple dozen times so I'm not worried about bricking it.
[Galaxy S 4 Active Original Android Development] :
Nah, im talking about the int'l version
[Galaxy S 4 Active Original Android Development] jd1866:
How stable are the Builds? I'm willing to test. I have my phone rooted but that's about it. I played around with AOKP on my s3 so I know what I am doing except I am unsure what SafeStrap is and I am scared of Boot Looping. Let me know how I can help!
[Galaxy S 4 Active Original Android Development] LeJay:
Just make a thread and upload your rom. Have you made any improvements?
[Galaxy S 4 Active Original Android Development] :
I dont know how stable, and sense your scared of a bootloop(which is extremely easy to recover from) I would suggest you not test.

I don't want to make a thread due to not knowing the stability of the roms, I will pm the testers builds. Users don't like that. But I need a tester who knows how to recover from a softbrick (bootloop) and is fairly familiar with android:D