yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] spegelius:
Extracted boot.img, contents:

./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz

Nothing in /dev. Apparently those files are created by kernel/something else?

I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:

I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd

From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.

And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.
[Galaxy S 4 Active Original Android Development] mythi:
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres

:silly:

edit: Even stock kernel doesnt have have guess issue is different :eek:

---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------

Looking at the logcat and staring at it for 20 minutes i think Logcats says

There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue :D
[Galaxy S 4 Active Original Android Development] spegelius:
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.

Edit: perms system:

drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin

perms /system/vendor:

drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib

perms /system/vendor/lib:

-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so

perms /system/vendor/firmware:

-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd

Maybe i'll need to set them root:shell in vendor?
[Galaxy S 4 Active Original Android Development] mythi:
try making perms in vendor as root excute user and group (i think in other words it is root:shell) :p this will inusre if we have perm issue
[Galaxy S 4 Active Original Android Development] spegelius:
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.

I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.

Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...
[Galaxy S 4 Active Original Android Development] mythi:
Why dont we cherry pick from gs4 snapdragon version qcom things since they share the same board , just cherry pick the diver files from an aosp rom for that device I am quite sure it will work .
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Don't give up! :)

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

Saturday 95℅ free time if the weather doesn't turn to warm (bike is calling)
[Galaxy S 4 Active Original Android Development] spegelius:
Heh, taking a bit of a breather, been at this quite intensively. Anyways, /system/vendor/lib/libbt_vendor.so, someone could try to replace that with one from CM build...
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Busy with my car today but as soon as I get the chance I will setup a Dual boot System with cm and your aosp build.

That will give me options to copy n paste the stuff without flashing the whole thing each time. Will report back.

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Dualboot Patcher exits the .zip with Error "unsupported zip File", need to look into this first :(
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Edit:

Bluetooth is working after I copied the mentioned File!!!

(Starts and sends/receives Files)

Awesome!!!

Sidenote

The Picture Quality of the Cam seems to be way better than on 1227 build of CM :)

There is (of course) no SD Card which caused me several switches between ROMs lol most of my Files are on external...

Else...VERY responsive and fluid

Hint for Dual Boot.. I didn't get the AOSP Rom patched so I decided to install it as first and CM as second. Worked :)

Thanks Mister Spegelius :)

---------- Post added at 09:19 PM ---------- Previous post was at 08:33 PM ----------

Found a bug..

I can start a call but can't end it..not that kind of a biggie since I've got Flat but...thought I let you know. ;)

Oh, swipe is not working with Google Keyboard. (There is no swipe, normal?)
[Galaxy S 4 Active Original Android Development] spegelius:
Woo, nice! So something is compiled bad with bluetooth driverside, but CM lib fixes it. Great, now we know that the java side patches i made work, so simply using CM compiled libbt_vendor during packaging does the trick.

Also i seem to have fixed nfc crashing, but don't have any way to test it...

Ok so now the only big bug seems to be phone. I did try to get some error out of it when calling to it, but there's nothing in logcat or dmesg when it's supposed to be ringing. Like it's not triggering any reaction :confused:. I'll dig in to it maybe tomorrow. Have a feeling it might take some doing. I've actually been using my work phone, S3 LTE for now as receiving phone calls and Sports tracker are kind of a need for me...
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Umm yes, figured it out now. You can start a call but not end it and not receive a call lol, had a angry voice on my other phone, asking me why the... I don't accept the call ;)

Back to backup for now :(
[Galaxy S 4 Active Original Android Development] mythi:
i hope we can find solution to the phone call bug :( try using ril files from cm :D
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
What are the Files needed for that? Copy n paste works fine in Dualboot, just tell me the needed Files :)
[Galaxy S 4 Active Original Android Development] mythi:
in /system/lib of cm copy all files have ril in their name and paste them in the /system/lib of this rom :D
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
OK, will try and report back!
[Galaxy S 4 Active Original Android Development] mythi:
sure :laugh:
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, that could work. No sure if the RIL files were from proprietary files downloaded from device, but lets have a look.
[Galaxy S 4 Active Original Android Development] mythi:
hmmm... they aren't proprietary but they make cause the issues with phone calls since they are rils in the end who knows it could work :fingers-crossed: , have you looked at the Phone.apk it may have issues :cyclops:
[Galaxy S 4 Active Original Android Development] spegelius:
At least these files are defined in jf-common device proprietary files and they are copied from phone when running extract_files.sh:

libreference-ril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libril.so

But then again, i don't know what else is needed so copying from CM might work.

I've had some look at the frameworks/opt/telephony java code and there are some Qualcom related changes missing when compared to CM. What i understood, Qualcom uses somekind of callback system to get notifications from lower level to framework... i'll need to see if i can cherrypick the Qualcom related stuff.
[Galaxy S 4 Active Original Android Development] mythi:
with the ril stuff and those cherry picks i think we will have solution i am sure :cowboy:
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Copying the Files from Cm didn't help.
[Galaxy S 4 Active Original Android Development] mythi:
[MENTION=3876105]spegelius[/MENTION] found some qualalcom things missing :) hope he fixes them
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah, but knowing what the proper stuff cherrypick shall be very difficult. There's lot's of changes in at least 50 files, some of them i'm not sure if they are needed... also there's that multisim stuff which i'm not sure if i want to include at this point (as it needs changes to settings etc.)

I tried just copying whole frameworks/opt/telephony code from CM but that ended badly because CM code references some things in settings package that aosp doesn't have. I fear that that's not the only dependency and we'll end up copying a lot of other stuff, which makes this not so musch aosp anymore.

Well, i noticed that there's some Qualcom realted stuff in hardware/ril, i picked all relevant looking stuff and now i'm compiling using the stock telephony. I'm not expecting it to work, but at least it should hopefully uncover what to change next.
[Galaxy S 4 Active Original Android Development] mythi:
ohh ok :good: :good: , is there a way to explore your whole source ? :cyclops:
[Galaxy S 4 Active Original Android Development] spegelius:
Not yet. Moving my changes to github has been on my todo list, but i've been doing too much debugging and testing to get to it. I'll start uploading them soon.
[Galaxy S 4 Active Original Android Development] mythi:
I can feel it ... we are near ... could you provide your latest build
[Galaxy S 4 Active Original Android Development] spegelius:
Uploading v0.3 to the Google drive. Stock telephony framework, so nothing new in that department.

Tried to add SamsungQualcomRIL and SamsungExonys4RIL to java sources, bad idea ;). But they are needed so there's work to be done...

http://pastebin.com/m0RMepiD

Edit: i'll propably start uploading stuff to github before i do anything with the phone stuff. To tell the truth, feeling bit demotivated as i'm doing quite intensive sw development at work and this is also starting to feel like work :D. But not giving up, just need a bit of time off.
[Galaxy S 4 Active Original Android Development] mythi:
it will be alot easier to help in debugging with full source code at github :good:
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Mate... you're doing this in your free time and if it starts to feel like work... Stop it...

From my point of view, you helped us a lot the last weeks and this is supposed to be fun, nothing serious!

Take your time and come back whenever you think you should!

And thank you for all your hard work!

One question tho, the picture quality of the AOSP build is way better than it was in the last cm build, is there a way to get this to cm?

Don't hurry ;)

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah, i know i should stop, but my mind keeps returning to solving problems and then i notice that i'm on it again ;). Luckily i do have other hobbies so it's not too bad yet :confused:.

And look what happened yesterday; an idea popped to my mind, have a look at SlimRom telephony code. And what do you know, it's much closer to AOSP than CM, so i did some cherrypicking and now phone calls are coming through :D. Yay!

Uploading v0.4, grab it from Google Drive when it's there. And no, nothing uploaded to github yet. But i think this is a good point to start backtracking all the changes, now that most of the basic functionality is there. I can finally go back to using my Active, woo :)
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Aweeeeesome :)

You made my day, thank you so very much :)

Will download, install and report back, awesome!!!

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] alirey:
i would like to try the ROM.

can anybody tell me if SD card is recognized? [MENTION=3876105]spegelius[/MENTION]: Thanks allot for your work
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Hey, no, it isn't. But I'm sure there is a way to do it.

Else, Call works, incoming & outgoing, End Call works, mobile Data works, WiFi works, Bluetooth works.

GPS I don't know (it's cold outside) but will test tomorrow ;)

Daily Driver for sure :)

Awesome!
[Galaxy S 4 Active Original Android Development] mythi:
Sorry for not directing any results from v3 an d v4 because I was busy alot... but I have them downloaded without testing , slim bean is near aosp cuz it is very slim, anyway we have a daily driver now:highfive::victory:

---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------

Sorry for not directing any results from v3 an d v4 because I was busy alot... but I have them downloaded without testing , slim bean is near aosp cuz it is very slim, anyway we have a daily driver now:highfive::victory:
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Didn't make SD work.

I tried to format with fat32gui, no luck..

I tried to format with Device... Caused a reboot but no luck..

The first time I released the back cover ever since I bought this phone ;)
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
But it's niiiice ;)
[Galaxy S 4 Active Original Android Development] spegelius:
Weel i haven't done anything regards that yet. Actually i don't even have sdcard yet (damn DHL and Nierle), but it's on the todo list. Hoepfully it's something simple, like missing lib...

Yeah, i think it ook a wrong choice by using CM as reference when starting to implement this, with Slim somthings would have been a lot easier. But then again, i've learned lot more :good:

Great! And GPS does work, tracked my bicycle ride to work today. There is a bug related to locationproviders, starting Sports Tracker crashed whole UI every time. Maps didn't. Turned out that Sports Tracker requested a provider named "network" which didn't exist. That threw an exception which crashed whole service framework :eek:. Fixed it by returning something more sane, so now it doesn't crash. But i think that's something that needs some attention at some point... i'm not ruling out that Sports Tracker is doing something bad.
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
From what I've read AOSP Roms are not licensed to read exfat. Formatting my spare SD Card to Fat32 didn't work but I think the Problem was on my Side of the Keyboard ;)

On the other Hand, Slim and CM do read the SD so there has to be a way..

Well, that's not a real biggie I think!
[Galaxy S 4 Active Original Android Development] alirey:
I have a 64GB card. Format is fat32. Works in CM from 27.12.2013

This was the command i found on my CM ROM in the following file: /data/local/RootToolsMounts

/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tried to copy the file on the aosp rom an restart --> no luck

tried to edit the /fstab.qcom with that string --> no luck

i hear no ringtone if anybody calls me...just me?
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
No Problems with the Sound, here, strange..

You may try this : http://xdaforums.com/showthread.php?t=2610224 until the problem with external SD is fixed, gives you, at least, the option to copy needed files to internal memory... (Not nice but works for me)
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
There is a /extras Folder in CM containing some exfat stuff, /bin Folder has some, too..

And I found this : http://xdaforums.com/showthread.php?t=2164266 but this didn't work on my Device..
[Galaxy S 4 Active Original Android Development] spegelius:
Did you install over old installation or did you do factory reset before? Could be some old setting or something... if the problem doesn't go away by changing volumes or ringtones, a logcat would be nice.

I think i haven't included exfat stuff to the build... i'll check this tonight, i'll scavenge a card from my cam. I need extra space anyways.
[Galaxy S 4 Active Original Android Development] alirey:
First i tried a dirty flash...no boot ;)

then a clean install with no ringtone but no time to check the settings.

Meanwhile i am back on cm because of work issues (couldn't hear my boss calling me two time)

But as soon as the Ext SD prob is solved, i will be back :) and if still no ringtone i will send you a logcat (or ignore my boss :victory:)

thanks in advance
[Galaxy S 4 Active Original Android Development] alirey:
Hey all,

found a way to mount the ext SD Card :victory:

mount -o remount,rw /

mount -t vfat -o umask=0000 /dev/block/vold/179:33 /storage/sdcard1

Now this ROM is my daily driver...

edit: Ringtone issue is gone
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Did you just run the mount commands in a terminal on the phone or via adb?

Woo hoo, great work all of you.
[Galaxy S 4 Active Original Android Development] alirey:
I did it with adb.

couldn't find a way to automount because fstab.qcom is overidden after boot(since android 4.3 no /etc/vold.fstab anymore)
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Gapps

I have uploaded Gapps to Mediafire if somebody is interested.

This one includes Google Keyboard with Swipe (from CM)

but I deleted Google+, GMail, Genie-Widget and all the optional stuff.

Click here to download.

I am not 100% sure if this is ok to use this modified Gapps, if it´s not, let me know and I will delete it!

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah, fstab.qcom comes from initramfs and is overwritten during every boot. But shouldn't matter, i found out that vold just didn't understand fat32 partition. Upgraded e2fsprogs, which provides newer blkid.h or something and now sdcard should work. v0.5 uploading to Google drive. I haven't tested exFat card.

Of and i have no idea about gapps. For me it's ok to post them here.
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
Dirty flashed 05 and external SD is there :)
[Galaxy S 4 Active Original Android Development] mythi:
dam .. i have just flashed v4 :crying::crying:

edit: BTW [MENTION=225651]op[/MENTION] how did you fix the sdcard issues , with and init.d script ?

edit2:exfat support needs an exfat supported kernel you could merge the exfat module by samsung from here
[Galaxy S 4 Active Original Android Development] spegelius:
Worry not, dirty flashing seems to work as long as you remember to flash gapps also. It not, stuff seems to stop working.

I didn't add any init.d scripts, it seems the framework just mounts it if it's supported fs type. It didn't work before, because original e2fsprogs didn't recognize the type of the partition (blkid was null in vold etc.). Upgraded e2fsprogs sources from CM and now it mounts properly.

Don't know if current kernel has exfat support, but if not, then we'll added them :)
[Galaxy S 4 Active Original Android Development] mythi:
ohhh... good to see this as a dialy driver for me ... i am done of samsung lagy ui :p:p, what about the camera preview issues they also affect the 1080p mode too :silly: i am going to try focal and see if the issue exsits :D
[Galaxy S 4 Active Original Android Development] ohwarumbloss:
You may change updater script to not format /system. This will make dirty flash more easy, I think.

People who want or need a clean installation can still wipe system..

For me, all good now, build is very stable :)

One question, Video recording with 1080p is very good but the recorded sound is very low. Is there a way to increase that? Not important tho..

Thanks for your efforts :)

Greetings

Thomas
[Galaxy S 4 Active Original Android Development] spegelius:
Camera problems are on the todo list at some point in the future. Haven't been testing it much. Now i'm just happy that it's currently in usable form for me. Time to get my changes to github.

Yeah, now it formats system every time, could skip that and leave it up to user to factory reset.

Recording volume and quality stuff should be changeable, just don't know how yet :D. But it'll come, sooner or later.

For now, it's github upload time. Propably no changes until that is done. And there's stuff to be done... should've started uploading sooner, now half of the time goes to finding out what is copied from CM what i've modified :rolleyes:
[Galaxy S 4 Active Original Android Development] mythi:
awesome :D:D
[Galaxy S 4 Active Original Android Development] emersonas:
Daily driver. Nice work mate.
[Galaxy S 4 Active Original Android Development] spegelius:
Damn, github started nagging about too large files... frameworks/base contains almost 1GB of stuff. Hmm might need to rethink how to upload stuff to github... one way could be to patch sources from aosp. Meh, too tired to think about that now.
[Galaxy S 4 Active Original Android Development] spegelius:
Alright, code uploaded :). No cwm packaging scripts yet, but for interested there should be a working manifest and code. To use:

repo init -u git://github.com/spegelius/manifests.git -b aosp-4.3
source build/envsetup.sh
cd device/samsung/jactiveltexx
./extract-files.sh
croot
lunch
make otapackage

Also found a bug; when taking a picture with Sports Tracker, camera dies and mm-camera-daemon starts taking cpu. No connection to camera can be re-establishes before reboot
[Galaxy S 4 Active Original Android Development] sagi232123:
work on at&t with safestrap ?