yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] patzyalex:
I don't really know what to say.

Maybe the zip is corrupted, it happened to me once.

Or you could try one of the older builds, there's plenty over there.

Or one of [MENTION=4630187]allram[/MENTION]'s https://drive.google.com/folderview?id=0BwwLmYElvFOmRkF4WGhEbFNoMG8&usp=sharing
[Galaxy S 4 Active Original Android Development] sicHiRsch:
Checksums match, so no corruption there... I am downloading allrams latest and will give that a try, although I already tried the latest carbon rom and that also got stuck on its bootscreen. Will also try the current version from sammobile (however that seems to take all night to download...).

Thanks though ;)
[Galaxy S 4 Active Original Android Development] patzyalex:
I hope u solve this issue.

Let us know.

Cheers.

Sent from my GT-I9295
[Galaxy S 4 Active Original Android Development] sicHiRsch:
had no success with any other rom so i tried to put the sammobile image on via odin, but unfortunately get this:

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> sbl1.mbn

<ID:0/004> NAND Write Start!!

<ID:0/004> sbl2.mbn

<ID:0/004> sbl3.mbn

<ID:0/004> rpm.mbn

<ID:0/004> aboot.mbn

<ID:0/004> tz.mbn

<ID:0/004> boot.img

<ID:0/004> recovery.img

<ID:0/004> system.img.ext4

<ID:0/004> modem.bin

<ID:0/004> NON-HLOS.bin

<ID:0/004> cache.img.ext4

<ID:0/004> hidden.img.ext4

<ID:0/004> FAIL! (Ext4)

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

the downloadmode screen reads the following:

ODIN MODE

PRODUCT TYPE: GT-I9295

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

CSB-CONFIG-LSB: 0x30

WRITE PROTECTION: Enable

eMMC BURST MODE enabled

START (224, 1440)

BAR (240, 1440)

ODIN: invalid ext4 image

any ideas?

cheers
[Galaxy S 4 Active Original Android Development] allram:
I think you need to get hold on a .pit file and flash that correctly first.

Seems like that is the issue..

Edit: Here is a link to how to create one:

http://xdaforums.com/showthread.php?t=1916936
[Galaxy S 4 Active Original Android Development] sicHiRsch:
After much playing around and frustration i finally got it going. First I found a pit file, which however I could not flash, Odin gave errors. What did the trick in the end was a package called "CF-Auto-Root". That seemed to have cleaned up whatever i messed up in the first place, and now I can start CM11. Thanks for the tips ;)
[Galaxy S 4 Active Original Android Development] 6783:
Hello everyone. How is the sound issue during call? Is it solved?
[Galaxy S 4 Active Original Android Development] patzyalex:
Good to hear that.

We're all in Chainfire's debt somehow :)

Sent from my GT-I9295
[Galaxy S 4 Active Original Android Development] koutsa:
Any1 else having problems w/ instagram-app? For me, the app itself works ok but if I try to take a pic or add one from gallery, the app freezes > fc's. Must be due to existing camera problems, 'aight?
[Galaxy S 4 Active Original Android Development] allram:
As far as i know, it is fixed.. I talk 4-5hours during work and no problems :) both with and without bluetooth
[Galaxy S 4 Active Original Android Development] patzyalex:
No sound issues here.

Sent from my GT-I9295
[Galaxy S 4 Active Original Android Development] Laum:
Yep sound is working fine. Also the new modem works good without problems.
[Galaxy S 4 Active Original Android Development] koutsa:
Also I had problems w/ in-call volume in previous build ( [MENTION=3876105]spegelius[/MENTION] ' build).

But strange things happen:

I just updated to [MENTION=4630187]allram[/MENTION] 's build from yesterday. When updating, my S4 Active looses one or two apps. For example - on last update, I lost my twitter app, and now when updated to allram's build, the phone lost Home Smack -app. I am 100% sure I had it installed, but when updated I had to install it again from Play Store.

Another strange thing is, that I can't install two apps: twitter and I can't update Titanium Backup Pro. When trying to install / update, Play market says I have too little storage left to install/update and I do have over 6 gigs free... Should I clean a market cache or sumtin'?

And as I said before, instagram app is ok for browsing feed, but I can't add a pic or take a pic with it.

EDIT: instagram works now! But can't install twitter even I cleaned market cache...
[Galaxy S 4 Active Original Android Development] allram:
Sounds strange... Did you clean cache and dalvik cache when you installed the latest builds? Never had that problem before myself.. seems like something got mixed while updating.. Did you do a backup before? Try to revert and install mine or Spegelius's latest build again :)
[Galaxy S 4 Active Original Android Development] Laum:
Sounds really strange. Sometimes space problems are cured after removing app folder from data/app-lib and I'm pretty sure this install problem is cured by that. Still, why that happened I have no idea.
[Galaxy S 4 Active Original Android Development] spegelius:
Regarding missing apps and other strangeness: my current installation cannot access gallery from camera app. It just stopped working few flashes ago. Also i had AOSP keyboard vanish for one boot, had to reboot the phone.

All these kind of problems have vanished when starting from scratch: factory reset and clean install. There just seems to be some crap accumulating when dirty flashing stuff which is under development. Of course it's possible there's new bugs also, but i'd say that trying with clean flash first is the best bet to get anomalies to go away. It's PITA, but what can you do...

Camera: no real progress with the setting bugs, but i did some comparison of different blobs from different roms: MF5, MK2 and NC2. MF5 has the blobs we have been using since cm10.2. MK2 and NC2 are newer and they are actually almost identical. I made flashable zips if someone wants to test them: https://drive.google.com/folderview?id=0BzJzDM42pkRvRFVRSmhSQzFmVTA&usp=sharing.

I think i'll flash TW rom and hope that there's camera debug available so comparing the settings would be possible.
[Galaxy S 4 Active Original Android Development] allram:
My newest build includes your latest blobs from nc2 for those who wants to test :)
[Galaxy S 4 Active Original Android Development] patzyalex:
Dirty flashing is to blame, as the others have already pointed out.

I always flash clean: wipe data/factory reset, wipe cache partition, wipe Dalvik cache.

Thus there's no more things to mess with the install.

The lower side is you have to backup your apps in advance and restore them after flashing.
[Galaxy S 4 Active Original Android Development] sicHiRsch:
Does YouTube work for anyone? It starts loading videos and then eventually crashes. There seem to be a few people experiencing the same in the carbon threat which is based on these ROMs.
[Galaxy S 4 Active Original Android Development] patzyalex:
It works very good for me. I watch it in browser, not with an app.
[Galaxy S 4 Active Original Android Development] olarf:
Yes it works fine in Browser, I never test the app.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] allram:
Youtube Works fine for me, both app and browser-wise :)
[Galaxy S 4 Active Original Android Development] sicHiRsch:
OK I played some more and it turns out that YouTube, browser and app, work on spegelius's may 3rd build but not on allram's may 12th build.

EDIT: just tried allram's latest (may 15th) and everything works fine.
[Galaxy S 4 Active Original Android Development] snadge:
Just a heads up, the roomservice.xml needs to be updated to reflect the path change from /device/samsung/jf-common to jfactivelte-common

There was also a rename of the default kernel config kernel/samsung/jactiveltexx/arch/arm/configs/cyanogen_jf_defconfig to cyanogen_jactivelte_defconfig

For some reason this commit seems to have been done to the cm-10.2 branch and not the cm-11.0 one. Woops. ;)

What's the deal with jf-common now? Have other devices dropped this convention? What needs to be done if anything to bring jfactive up to date with the rest of the S4 devices?

Unrelated, I've turned some extra tethering debugging on to try and figure out why I can't get USB tether to work, and will report back if I find anything.
[Galaxy S 4 Active Original Android Development] snadge:
Ok so I've managed to fix usb tethering by copying the device config overlay from jflte.

There is still an MTU related issue with using PPTP connections over some 3g networks, which is unrelated, but I have found a workaround for that. Lowering the MTU to 1480 on the rmnet_usb0 interface on the phone itself, or on the usb interface of the ubuntu client seems to work around that.
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah [MENTION=3422045]a2441918[/MENTION] wanted to change jf-common name to jactivelte-common. The kernel config was indeed to wrong branch, didn't notice it when checking the pull request. Gonna update it...

I had hoped to try to use the jf-common provided by CM (with few additions), but now it's jactive's own common dir. At least now we don't have to fear breaking things for other devices...

roomservice.xml update coming up.

Oh and a2441918 has contacted CM devs about official status, but let's see...
[Galaxy S 4 Active Original Android Development] patzyalex:
I understand about USB tethering, but I can't get bluetooth tethering either, should it be working or maybe in one of the future builds? :fingers-crossed:
[Galaxy S 4 Active Original Android Development] spegelius:
What overlay is that? I could include it to github... i tried comparing jactive stuff to jf-common and jfltexx from CM, no differences with overlay's (other than camera).

On another note, i installed MK2 rom and it seems there's Camera setting debug available, yay! Had to revert to CWM 6.0.4.5, because MK2 Stocky Rom failed always with error about 'formar needs 5 params, 4 were given'... It's actually quite nice to use TW rom, haven't had on since last october or so :).

And just for kicks i made a CWM zip with NC2 stuff and it boots o.O. Strangely though, Android version says at 4.2.2 even though build is NC2 and kernel is built 27 March. Go figure... Still, some stuff seems to be newer. And no crashes yet (Except Gear Manager at boot)

Edit: NC2 is 4.2.2 ROM. I mistakenly thought it was the AT&T KitKat
[Galaxy S 4 Active Original Android Development] spegelius:
Some findings about NC2 Camera:

value auto-exposure is set in NC2, but not with CM. Possible values are matrix,center and spot.

numeric commands are sent to camera with sendCommand function. These aren't sent in CM

Numeric commands:

I/QCameraHWI( 310): create jpeg_snap_save_thread
I/QCameraHWI( 310): create jpeg_snap_save_thread
I/QCameraHWI( 310): QCameraHardwareInterface: X
E/QCameraHWI( 310): isCameraReady mCameraState 1
I/QCameraHWI( 310): sendCommand: E, command = [B]1611[/B]
I/QCameraHWI( 310): sendCommand: X
I/QCameraHWI( 310): enableMsgType: E, msgType =0xc0d
I/QCameraHWI( 310): enableMsgType: X, msgType =0xc0d, mMsgEnabled=0xc0d
I/QCameraHWI( 310): sendCommand: E, command = [B]1515[/B]
I/QCameraHWI( 310): sendCommand: X
I/QCameraHWI( 310): enableMsgType: E, msgType =0xc0d
I/QCameraHWI( 310): enableMsgType: X, msgType =0xc0d, mMsgEnabled=0xc0d
E/QCameraHWI( 310): setCallbacks: E
I/QCameraHWI( 310): setCallbacks: X
I/QCameraHWI( 310): enableMsgType: E, msgType =0xc0d
I/QCameraHWI( 310): enableMsgType: X, msgType =0xc0d, mMsgEnabled=0xc0d
I/QCameraHWI( 310): set_gamma_thread: E
E/QCameraHWI( 310): set_gamma_thread : gamma mode (0)
D/QCameraHWI( 310): dataProcessRoutine: E
I/QCameraHWI( 310): jpeg_snap_save_thread: 0x43c0a7d8 E
I/QCameraHWI( 310): runJpegSnapSaveThread: E
I/QCameraHWI( 310): sendCommand: E, command = [B]1508[/B]
W/QCameraHWI( 310): Samsung App
I/QCameraHWI( 310): sendCommand: X
D/QCameraHWI( 310): dataNotifyRoutine: E
I/QCameraHWI( 310): sendCommand: E, command = [B]1297[/B]
I/QCameraHWI( 310): sendCommand: X
I/QCameraHWI( 310): disableMsgType: E
I/QCameraHWI( 310): disableMsgType: X, msgType =0xffff, mMsgEnabled=0x0
E/QCameraHWI( 310): setCallbacks: E
I/QCameraHWI( 310): setCallbacks: X
E/QCameraHWI( 310): setCallbacks: E
I/QCameraHWI( 310): setCallbacks: X
I/QCameraHWI( 310): sendCommand: E, command = [B]1611[/B]
I/QCameraHWI( 310): sendCommand: X
I/QCameraHWI( 310): enableMsgType: E, msgType =0xc0d
I/QCameraHWI( 310): enableMsgType: X, msgType =0xc0d, mMsgEnabled=0xc0d
I/QCameraHWI( 310): sendCommand: E, command = [B]1515[/B]
I/QCameraHWI( 310): sendCommand: X
I/QCameraHWI( 310): enableMsgType: E, msgType =0xc0d
I/QCameraHWI( 310): enableMsgType: X, msgType =0xc0d, mMsgEnabled=0xc0d
E/QCameraHWI( 310): setCallbacks: E
I/QCameraHWI( 310): setCallbacks: X
I/QCameraHWI( 310): sendCommand: E, command = [B]1334[/B]
I/QCameraHWI( 310): sendCommand: X
I/QCameraHWI( 310): sendCommand: E, command = [B]1351[/B]
I/QCameraHWI( 310): sendCommand: X

From these, 1508 is related to ZLS (Zero Lag Shutter, described in CM Camera settings). Others, don't know.

Above sequence is from taking a picture: it seems that the commands are sent before and after taking a picture, because command 1611 is sent again after runJpegSnapSaveThread and dataNotify (just a hunch). I'll try to add at least 1611 cmd to CameraWrapper along with the auto-exposure setting. But first i need to clean some Samsung bloat so i can flash dualboot roms...
[Galaxy S 4 Active Original Android Development] a2441918:
my bad. spegelius please update ur tree to default branch cm-11.0. i get confused always. nd also remove android.mk file from ur vendor. i think vanir aosp official will be released tmrw. all patches given but i made a small mistake with vendor.. will fix it tomorrow.

apply for rd mate. u will surely get it.
[Galaxy S 4 Active Original Android Development] spegelius:
Set the default branch to cm-11.0. Removing Android.mk https://github.com/spegelius/device-props_jactiveltexx is not gonna work because it defines libtime_genoff library. Does it cause problems with Vanir or something else? I suppose another branch would do...
[Galaxy S 4 Active Original Android Development] a2441918:
no issues mate just leave it like that.
[Galaxy S 4 Active Original Android Development] snadge:
There's a bunch of stuff in cm11.0's jflte device overlay which seem to be applicable also to jactive. Including camera stuff, and usb/wifi/bluetooth tethering.

https://github.com/CyanogenMod/android_device_samsung_jflte/tree/cm-11.0/overlay

I just copied the whole lot over in the current build that im running, and it seems to work okay.
[Galaxy S 4 Active Original Android Development] mythi:
here's a build i made personally on our build server ... seams good https://drive.google.com/file/d/0ByEZDplbxwxJLThmVGZTZjI5N00/edit?usp=sharing

this is built from the latest sources .
[Galaxy S 4 Active Original Android Development] spegelius:
Ah, i'm comparing to jfltexx, not jflte... alright, now i can see the overlays. Great, thanks.

Edit: i tried adding the auto-exposure setting, but it doesn affect the screen going blank. I also compared the NC2 and CM11 camera setting debugs and i can spot a relevant difference that could throw the exposure too low... more digging needed
[Galaxy S 4 Active Original Android Development] jott_st:
Has anyone seen this yet?

http://xdaforums.com/showthread.php?t=2754997
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah, i had a look at this yesterday. It's interesting and i'll propably do some testing someday but for now it's just another variable when trying to debug things with camera etc. so not sure when. But if someone else makes builds with those flags, do post results here.
[Galaxy S 4 Active Original Android Development] jott_st:
I will try and build it, I don't know when I'll get to it, though... Also, there seem to be a lot of devs runing into problems while building whith these flags.. Oh well, we will see.
[Galaxy S 4 Active Original Android Development] mythi:
here is a new build from today's sources http://sonic-developers.com/testing/mythi/jactiveltexx/
[Galaxy S 4 Active Original Android Development] olarf:
Uhhh I See also a pacbuild there. Is it for our device? That would be awesome.

I cant resist to give it a try. It boots, pass the PAC animation but then stuck in PAC Logo :( So im back in cm11 now :)

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] mythi:
Hahaha... You cought me ... I won't publish this build because we are not friends with PAC guys :o

Anyway people ... Check sonic-developers.com/testing/mythi/jactiveltexx for the latest cm build
[Galaxy S 4 Active Original Android Development] olarf:
At least you didnt publish it, I just found a file somewhere. However, I got generaly green lights to do a 9295 PAC, my skils are just to low to setup a build system and Connecticut all needed sources. So lmaybe I can go for it with some support.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] mythi:
just shoot me a pm if you need help :p
[Galaxy S 4 Active Original Android Development] olarf:
Done, im just not sure if you get it :)
[Galaxy S 4 Active Original Android Development] pen²:
The 0523 build of cm shows the red flashing display border (during screen updates?) went back to the version before
[Galaxy S 4 Active Original Android Development] mythi:
thanks for the heads up ... i know the issue :silly: next build will solve it :laugh:
[Galaxy S 4 Active Original Android Development] koutsa:
This is starting to be a little funny :)

I have to re-install twitter app every day. My current build of this ROM seems to make my twitter app disappear every day. When I go to Play-store, it every day shows me that "install"-button, as I didn't have installed it before...

And yes - no dirty flashing, did a factory reset/wipe before flashing Mythi's build from 21st of may.
[Galaxy S 4 Active Original Android Development] whizz:
Apparently we are getting an official update to 4.4.2 :) Any use for this ROM? http://www.gsmarena.com/international_galaxy_s4_active_gets_kitkat_as_we_speak-news-8622.php
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Huge differences between TW and CM. You want locked in OEM and bloatware or freedom to run what you want?
[Galaxy S 4 Active Original Android Development] allram:
Finaly! Now we can extract blobs and see the differences, maybe we can finaly fix the camera problems :)

Have been trying to build CM with JustArchi's optimizations lately, not going good. getting a few build errors. Trying a new build now.

Will see if i can install this from your link and extract blobs :)
[Galaxy S 4 Active Original Android Development] whizz:
I know, but we can strip the good parts from the TW-ROM :) Camera-blobs for instance :)
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Ah, I misunderstood your meaning to ditch this and to to stock. [MENTION=4630187]allram[/MENTION] is looking into that and probably others. :good:
[Galaxy S 4 Active Original Android Development] mythi:
people who are working in this project ... i have taken a big closer look on the new blobs , sammy has done something some what strange to me they moved certain libs from /system/lib/ to /system/vendor/lib/ (i think this is a smart move allowing faster access for them) but then there is alot changed there i mean certain libs are missing (perhaps merged to others or something) and as far as ive looked sizes are different new gpu drivers and alot of changes in wifi bcm's ... (to be continued):victory::victory:
[Galaxy S 4 Active Original Android Development] allram:
Yea, i found out that also. but i can't find the missing libs anywhere... seems like they have changed the names or done something mysterious :P
[Galaxy S 4 Active Original Android Development] Laum:
Google cameras hdr doesnt seem to work with the official rom so working cm might be kinda hard...
[Galaxy S 4 Active Original Android Development] olarf:
Just want to report that the 28.05 build Form allram runs pretty fast.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] allram:
Nice! Added some of the optimizations from justArchi :)

More are on the way ;)

Trying a userbuild version as well, but get fc errors when flashed. Maybe i need to have a clean flash first...
[Galaxy S 4 Active Original Android Development] vanyel:
Going to sit tight and wait for the upcoming builds... :)
[Galaxy S 4 Active Original Android Development] sam.crowther:
Since updating 4.4.2 Samsung ROM with ne5 modem, I have working LTE on this as secondary.. And compass. Not sure if we had compass working before, but it definitely does with ne5...
[Galaxy S 4 Active Original Android Development] allram:
My latest build from today is build with Linaro 4.7 and JustArchi optimizations V3

Had to go with -O3 on TARGET_thumb_CFLAGS

But overall i think it is much faster than plain builds. Might just be me hoping that my work is faster than before :P (placebo...)

Trying to make new builds now with Linaro 4.8 as it has somewhat more optimizations than 4.7, if that goes well, i will try to make -O2 on thumbs flags ;)

Gdrive link:

https://drive.google.com/folderview?id=0BwwLmYElvFOmRkF4WGhEbFNoMG8&usp=sharing
[Galaxy S 4 Active Original Android Development] olarf:
Download is running, let's see if it beat your last one ;)

While it is slower from Benchmarking (antutu 27321 now, 28664 with 28.05 build), it feels incredible fast and smooth!!! After flashing it dirty I had a mountain of FC's but after a reboot it runs fine. Thanks for trying those performance stuff.

Edit: After testing a lot of stuff I must say that app start and all over response of the phone is REALY fast and stable.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] 6783:
Hello. Any success with Sammy libs from stock 4.4 for cm11?
[Galaxy S 4 Active Original Android Development] olarf:
If there is some process, you will find it here. I guess spegelius will try to find the fixes in the official ROM but it needs time and usually all devs have a real live beside of developing ROMs ;) So we have to wait or start developing by our self.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] pen²:
Just one quick question: do others also have the problem that if they switch to wcdma preferred or some other modes, the com.android.phone process force closes? The strange thing is, that although when I change from gsm/wcdma auto to wcdma preferred, I get the fc and afterwards it still displays gsm/wcdma auto, I still see better data rates (h/h+ where there was g only before)
[Galaxy S 4 Active Original Android Development] 6783:
Can I install it on official 4.4? Or I have to downgrade to 4.2 before? If yes, how can I safely downgrade to 4.2?
[Galaxy S 4 Active Original Android Development] baaldfg:
Hi there,

does the compass work in Osmand (viewing direction and compass based map orientation)?

On the ML3 baseband I always have the problem that the compass works in Google maps and GPS status but not in Osmand.

Best wishes,

Christian
[Galaxy S 4 Active Original Android Development] sam.crowther:
works with 2 different compass apps i tried.
[Galaxy S 4 Active Original Android Development] marcelser:
Where to get the different modems / basebands

Hi,

Can anyone tell me which rom has the ne5 modem and which one the ml3 baseband, cause currently I'm on CM11 with a MH3 baseband from allram. Are the separate flashable bin files files anywhere or do I have to flash a certain rom first and then CM11 through CWM on top of it? And which baseband do you recomment for the latest CM11?

Best regards,

Marc