yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
lol thnx :P. but im going to a party in a few hours so won't be developing tonight, will continue tomorrow.:cool:

if anyone wants to attempt to fix it be my guest.

added this to init.carrier.rc

wait /dev/block/platform/msm_sdcc.1/by-name/userdata
mount ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata /data nosuid nodev barrier=1
chown system system /data
chmod 0771 /data

# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/adb 02750 system shell
mkdir /data/misc/audit 02750 audit system
mkdir /data/misc/bluedroid 0770 bluetooth net_bt_stack
mkdir /data/misc/bluetooth 0770 system system
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/keychain 0771 system system
mkdir /data/misc/radio 0770 system radio
mkdir /data/misc/sms 0770 system radio
mkdir /data/misc/zoneinfo 0775 system system
mkdir /data/misc/vpn 0770 system vpn
mkdir /data/misc/systemkeys 0700 system system
# give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
mkdir /data/local 0751 root root
mkdir /data/misc/media 0700 media media

# For security reasons, /data/local/tmp should always be empty.
# Do not place files or directories in /data/local/tmp
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app-asec 0700 root root
mkdir /data/app-lib 0771 system system
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/ssh 0750 root shell
mkdir /data/ssh/empty 0700 root root
mkdir /data/radio 0770 radio radio

and used the sepolicy of the recovery XD, only that resulted in an 99% boot, all other (default) ways dont even make dalvik-cache
[Galaxy S 4 i9505 Original Android Development] MaKTaiL:
Are you sure it is hanging? I heard on the Nexus forums that the first boot using ART can take 10 minutes to start.
[Galaxy S 4 i9505 Original Android Development] rkaede:
u need to take a break man. coz thats how kitkat works :D
[Galaxy S 4 i9505 Original Android Development] Garner:
Can you upload the build so we can try and fix it?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Kernel/ramdisk issue. 99% sure.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
uploading

http://www12.zippyshare.com/v/7065473/file.html

ok last thing I will post is a new kernel with updated selinux config. pretty large chance that it works with that.

btw nvm, doesn't work. someone needs to try the cm11 kernel ;)
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
I'll post that in chenxiaolongs thread and in ktoonsez thread. Ktoonsez is a kernel expert :)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Garner:
Woop thabkyou and have a great night tonight you deserve it!

---------- Post added at 06:32 PM ---------- Previous post was at 06:20 PM ----------

I've asked on the Cyanogen Google+ community for help

https://plus.google.com/117843946470923372607/posts/7q5bAQAtwKT
[Galaxy S 4 i9505 Original Android Development] jamal2367:
Wow nice ....:) *-*

Gapps link for kitkat ???
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Here is the kernel of cm11.

pls check the difference :)

while in bootloop:

adb reboot recovery

adb push boot.img /sdcard/

adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20

adb reboot

pls note that the splash screen sometimes hangs 2 times in a row. so just unplug battery twice if needed

edit added module
[Galaxy S 4 i9505 Original Android Development] fatlus:
Try this:

http://www.androidfilehost.com/?fid=23212708291675046

from this thread

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

EDIT: The version above is for paranoid roms. instead try this one: http://www.androidfilehost.com/?fid=23212708291675283 from this thread http://xdaforums.com/showthread.php?t=2012857
[Galaxy S 4 i9505 Original Android Development] fedef12evo:
will rom boot with cm11 kernel?
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
I don't know, try it ;) thats what I have been doing for the last 5 days lol
[Galaxy S 4 i9505 Original Android Development] jamal2367:
People Boot the Rom ???? I can not testing im not @ Home
[Galaxy S 4 i9505 Original Android Development] Garner:
I'm waiting for gapps to download then I'll try it :)
[Galaxy S 4 i9505 Original Android Development] fatlus:
I make a nandroid backup and will start to try after finishing it
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
This rom isn't fully kitkat is it? Just parts of 4.3 to make it work? Guess we have to wait for fully kitkat goodness :)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
no not really. it is in fact fully kitkat, with some commits merged that are needed for our hardware and such. but they are included in every android version else it doesn't work. but atm it doesn't work properly yet so no worries xd
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Hopefully they'll release the GE 4.4 rom soon so we can take those files to make it work perfectly :)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] MetaIIica:
for me i have a bootloop with CM 11 Kernel
[Galaxy S 4 i9505 Original Android Development] fatlus:
Do you update the zip file with the modules.zip?
[Galaxy S 4 i9505 Original Android Development] MetaIIica:
yes i did it.

both, with and without CM11 Kernel end in a Bootloop
[Galaxy S 4 i9505 Original Android Development] Me Gusta:
So I assume it will have aosp browser? Great!

Me Gusta!
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Of course I don't see a reason not to use the default browser :P
[Galaxy S 4 i9505 Original Android Development] svfusion:
When I flash, I have no signal and when I put in the "phone" apn for AT&T, the APN disappears after I save it..

Going on compile the newest build tonight
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
You can try to push apns-conf.xml to /system/etc/ and see if that helps.

btw I have external sdcard fixed, but bluetooth is still not working, it doesn't fc anymore though.
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Hey now that's progress.
[Galaxy S 4 i9505 Original Android Development] manager77:
Can you make a flashable zip with sdcard fix?...thanks!
[Galaxy S 4 i9505 Original Android Development] boterkaaseneieren:
Yes please upload the rom.
[Galaxy S 4 i9505 Original Android Development] ohcie_evo:
+1
[Galaxy S 4 i9505 Original Android Development] Mnt-XDA:
Hello [MENTION=4354408]broodplank1337[/MENTION], You are doing a great job...

As you said, taking pictures is working by modifying some parameters in build,prop. Is it so ?

May I know which build.prop parameters are responsible for taking pictures ?

Thank you so much for your hard work.
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
[MENTION=373710]others[/MENTION], I'm uploading it within a hour

I made the most LAME discovery EVER in my android history

The LENGTH yes the LENGTH of the ro.build.display.id value in build.prop determines if you can take pictures or not!!!

for example:

ro.build.display.id=full_jfltexx-userdebug 4.3 JSS15J eng.broodplank.20130813.020210 test-keys

ro.build.version.incremental=eng.broodplank.20130813.020210

This crashes the camera

but this works:

ro.build.display.id=full_jfltexx-userdebug 4.3 JSS15J eng.brood.20130813.020210 test-keys

ro.build.version.incremental=eng.brood.20130813.020210

meaning if you have a long username (like 8 chars) then it will crash, and if you have a short username it will work. WHAT THE **** :D

hahaahaha, this solves all my camera problems :D that 20 reboots was worth it

this means I can use my own build.prop which removes the choppy scrolling through text files
[Galaxy S 4 i9505 Original Android Development] ChaoticUnreality:
Sadly that doesn't even make my odd bug producing code radar. Glad to know you got it figured out.
[Galaxy S 4 i9505 Original Android Development] Mfgonfie:
Unbelievable! It remembers me an old time with windzoz and the maximum length of file's name.

We wait for your upload with pleasure, any feedback about BT?
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
What? :silly: code radar? And yes I'm happy that I found it out.

Yes idd, things like those are always so weird, I was suspecting it when I saw "strlen" in logcat.

here is the new upload:

http://www.broodplank.net/files/aosp43-i9505-allworking-nobt-alpha04.zip

fixed:

- External SDCard

- ExFAT

partially fixed:

- Bluetooth (still not working but no fc)
[Galaxy S 4 i9505 Original Android Development] Mnt-XDA:
This is very interesting soluion....

:)
[Galaxy S 4 i9505 Original Android Development] crzykiller:
Getting this error when I try to install it

Warning: No file_contextsset_perm: some changes failed

E:Error in /external_sd/SGS4 stuff/Roms/aosp43-i9505-allworking-nobt-alpha04.zip

Downloaded twice but doesn't seem to work, I'm using official CWM 6.0.3.3

---------- Post added at 02:06 PM ---------- Previous post was at 01:57 PM ----------

Also as a side note, i used to be able to flash the other Versions with a canadian Recovery but now it gives me build prop errors too which it never did
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
try wiping system first. and the assert build.prop errors are when you're not using jfltexx/i9505. so if you just remove the upper part from META-INF/com/google/android/updater-script it will work
[Galaxy S 4 i9505 Original Android Development] boterkaaseneieren:
Going to test now and see what's going on. Exited!

---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------

Status error 7 but ROM installed fine.
[Galaxy S 4 i9505 Original Android Development] crzykiller:
Wow that is awesome... never knew you could do that :p thanks a lot :laugh:
[Galaxy S 4 i9505 Original Android Development] jamal2367:
take of my rom (4.3) the Bluetooth.apk

and the libs for bluetooth

and test if it works?

what is this ? o.o https://play.google.com/store/apps/details?id=com.phk.bluetoothfixrepair&hl=de
[Galaxy S 4 i9505 Original Android Development] ChaoticUnreality:
Not sure if you noticed but when you changed the title you put [ROM][ROM]
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
same for me
[Galaxy S 4 i9505 Original Android Development] jamal2367:
this is all a kernel problem ;) .....

i hope you can fix this :)
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Yes it's a kernel problem... There's much going on on cm gerrit... Many cm11 commits..

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
not the kernel itself in particular but the selinux configuration (and the ramdisk), it's screwed up for all devices atm unfortunately. best sepolicy so far is the one from recovery XD!
[Galaxy S 4 i9505 Original Android Development] fatlus:
hmm, i have problems with the updater-script...

i've got a status 7 with "This package is for "jflte" devices; this a "jfltexx"
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
just remove the top lines from updater-script ;)

assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" || abort("This package is for \"jflte\" devices; this is a \"" + getprop("ro.product.device") + "\"."); ||
getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" || abort("This package is for \"jfltexx\" devices; this is a \"" + getprop("ro.product.device") + "\"."); ||
getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" || abort("This package is for \"i9505\" devices; this is a \"" + getprop("ro.product.device") + "\"."); ||
getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" || abort("This package is for \"GT-I9505\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

in

zip/meta-inf/com/google/android/updater-script
[Galaxy S 4 i9505 Original Android Development] overkillZ:
maybe [MENTION=3332811]faux123[/MENTION] or [MENTION=4325945]ktoonsez[/MENTION] kan help with the kernel?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Ktoonsez said we have to wait for the cm team.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
So many display_caf cm11 commits...

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
holy **** i got it to boot :D :D :D
[Galaxy S 4 i9505 Original Android Development] Garner:
Ohbmy God what did you do?
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
nothing really built with broodplank1337 sources for my jftecan used the sepolicy from recovery added his code to the init.carrier.rc .... it sticks at bootanimation for a while ""Waiting for service media.audio_policy..."" then eventually boots :D

known issues right now

- no audio

- issues with storage (cant even save screenshot)

- no wifi

- no service

working

- camera (can't save no storage)

- bluetooth
[Galaxy S 4 i9505 Original Android Development] Garner:
Can you build for jftexx?
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
i think my build should boot on the jftlexx just fine ... most jflexx roms work just fine on my device
[Galaxy S 4 i9505 Original Android Development] Garner:
Upload it then we try ;)
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
uploading .... ive pre-removed the device asserts
[Galaxy S 4 i9505 Original Android Development] MaKTaiL:
Can you post some screenshots?
[Galaxy S 4 i9505 Original Android Development] MetaIIica:
the next question is, witch CWM is needed. Last with 4.3 we needed updated CWM for fine boot... ist just a idea

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
im using philz touch... lol

havn't found a way yet .. with storage broken
[Galaxy S 4 i9505 Original Android Development] Me Gusta:
Take a different phone, take picture of phone and screen turned un. Upload

Me Gusta!
[Galaxy S 4 i9505 Original Android Development] dthomasen:
Just use ADB :)

adb shell screencap -p | sed 's/\r$//' > screen.png

(if running on a linux box)
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
Download Kitkat test build

mirror

known issues

- no audio

- issues with storage (cant even save screenshot)

- no wifi

- no service

working

- camera (can't save no storage)

- bluetooth
[Galaxy S 4 i9505 Original Android Development] jamal2367:
The bugs :

No wifi , no service , no data is easy to fix ...... Some libs must fixed ....because unknown baseband is not that working ...
[Galaxy S 4 i9505 Original Android Development] manager77:
I've got error 6...
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
bad upload? .... added another link
[Galaxy S 4 i9505 Original Android Development] jamal2367:
THX for the mirror .... I become status 6 error???:// i used Philz Touch :/ hmm
[Galaxy S 4 i9505 Original Android Development] :
Error 6 in CWM refers to a syntax error. Either it being in the Update(r)script or .sh file as well as the formatting of the file itself, as it is going to be used by a UNIX OS.
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
the mirror should work ... or you could see if i made a mistake when removing the asserts in the first zip
[Galaxy S 4 i9505 Original Android Development] :
Try to flash the zip you uploaded yourself, so we would know, that the installer script is the problem.
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
i dont have the google drive one... ill take down the link .. but i just tested the one i uploaded to the mirror and it flashes
[Galaxy S 4 i9505 Original Android Development] Klyupp:
The at&t version has a pretty much working build.. can't we just port this?
[Galaxy S 4 i9505 Original Android Development] f100cleveland:
Is there a link to the build?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
To fix the baseband and data, I bet all it would take is a merge of the JB fix when the android_packages_apps_Phone was updated for the JF device :good:. I dont have time to find it but that should give some of the guys working on the right path ;)
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Can you please tell me how you built this? Did you use my sources? and I see you used my "alpha"ramdisk, thats the reason of storage not working correctly, but better then no storage at all I guess.

No wifi probably because of incorrect dhd.ko

no data because I haven't spent any second on the qualcomm ril so far. First goal is to get it booting. then ill fix them one by one.

Good that camera (except storage) and bluetooth is working tho.

no libs must be fixed, its all in telephony-common.jar and core.jar ;), it it were libs samsung should fix them as they are proprietary files

anyways going to test the build now

edit: even with data wipe I cannot boot, did you pass any extra arguments during boot? I see that cache doesn't even exist.

W/AudioSystem( 754): AudioPolicyService not published, waiting...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
E/TemperatureHumiditySensor( 754): mCompEngine is NULL
W/AudioSystem( 754): AudioPolicyService not published, waiting...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
W/AudioSystem( 754): AudioPolicyService not published, waiting...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...
I/ServiceManager( 754): Waiting for service media.audio_policy...

this is what I get after optimizing apps

edit2: lol nvm while typing this message it appeared XD

going to try to use ART compiler as first thing :P
[Galaxy S 4 i9505 Original Android Development] thegreatergood:
just synced ur latest work and followed ur suggestions in the thread hoping i could get it to boot ... im guessing ur 99% build from before would also probably have booted after a while..?

edit* also as far as i could tell from looking though the partitions both internal and external storage wasnt mounted properly and what i found wierd was that the /data/ partition appeared to be empty :eek:
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
the horrible thing is that the data partition doesn't get mounted AT ALL. I posted a custom ramdisk with first of all my own version of creating the data dir, pls note that this is not the actual data partition, its just a tmp folder, second of all because I used the most lame sepolicy you can think of, the one from CWM!. XD :silly::silly:

the reason that the sdcard doesn't get mounted is because I haven't implemented legacy ums mount yet.

but the data problem is just weird

this is btw my build proof of concept ;)
[Galaxy S 4 i9505 Original Android Development] Garner:
99% there :eek: i have just suggested this work to the Xda editors hopefully this will make the first page ;)

What needs to be fixed??
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
RIL in general (Which includes baseband, calling and 3g)

Wifi

Sdcard

Proper data usage

Sound

And as far as I know (in my experience) they don't care about aosp builds at all. it seems in their eyes its more an accomplishment to make cm11 working rather then a clean aospk, which is actually more then just a custom rom its a base for all new custom roms. this is how I think they think, I've earlier tried to push some aosp love into the portal but no interests it seems, it might be because its not 100% pure but thats just impossible for all other devices then the nexus series. Anyways since it's a clean open source rom base for developers with an up to date kernel as well and overal runs very smooth and bug free (im talking about 4.3 here not 4.4 ;)) it might be worth it to post it on the portal right?

(the bold text represents some of the core reasons that a mod should understand ;))

anyways, i never argue with a mod, no is no. yes is yes. :silly:
[Galaxy S 4 i9505 Original Android Development] jamal2367:
http://xdaforums.com/showthread.php?t=2483220&page=4

---------- Post added at 11:16 AM ---------- Previous post was at 10:22 AM ----------

@broodplank1337 can you fix the ril or must you waiting of cm??

I See , you make the Rom beautiful :cool:
[Galaxy S 4 i9505 Original Android Development] hisname:
[MENTION=4354408]broodplank1337[/MENTION] CWM has issues with 4.4, I suggest you use TWRP
[Galaxy S 4 i9505 Original Android Development] MaKTaiL:
Yes, they got a fully working rom with only a few minor fixes yet to solve, but nothing related to functionality.

I think you should talk to them [MENTION=4354408]broodplank1337[/MENTION], maybe we can have a working build today. :)
[Galaxy S 4 i9505 Original Android Development] MaKTaiL:
They haven't released the rom to the public yet. But they can share their sources.

The link to their thread is this: http://xdaforums.com/showthread.php?t=2483220
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
leme inspect dem githubzz :cool:
[Galaxy S 4 i9505 Original Android Development] MaKTaiL:
Also, here is his twitter account where he is posting pictures of his progress.

If his latest fixes are not in the Github, try asking him what he did. :)

https://twitter.com/@kejar31
[Galaxy S 4 i9505 Original Android Development] soyusado:
Maybe the "Baseband Unknown" issue is caused by the recovery you're using.

It was the same thing with Philz and the very first builds of 4.3.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Or because of different libs. Early cm10.2 on S4 tmobile builds didn't have baseband on intl. S4. They had to flash a seperate zip to get baseband.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] soyusado:
Do you have bootanimation when the phone is starting?

The mirror link above the screenshots is the one the cab be flashable, am I right?

I want to try it myself.

Cheers.
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Ill compile CWM for 4.4 today and post it, its already has been released ;)

the baseband is dependent on the RIL which comes as a proprietary file idd.

But those are included in my build

If I remember correctly I saw in logcat once that either some firmware couldn't be loaded or it was apnhlos, anyways, both point to the same thing. so there may be a baseband issue with the new android, probably caused by the many changes they made to the security system, or could be an internal layout change in the apnhlos.mbn file. So far I have no clue, since I haven't investigated it yet, it will come when trying to make the RIL working correctly
[Galaxy S 4 i9505 Original Android Development] Garner:
[MENTION=4398685]csphelps76[/MENTION] could you help us here?
[Galaxy S 4 i9505 Original Android Development] soyusado:
Also, which gapps do you recommend for 4.4? Are the same for AOSPA?
[Galaxy S 4 i9505 Original Android Development] jamal2367:
Here the New Launcher3 from cm11 :)

https://github.com/CyanogenMod/android_packages_apps_Launcher3
[Galaxy S 4 i9505 Original Android Development] jamal2367:
https://github.com/TEAM-Gummy

https://github.com/TEAM-Gummy/android_device_samsung_jf-common