yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Hen-3:
I use XBlast for some stuff and all is good.
[Galaxy S 4 i9505 Original Android Development] __Miguel_:
I see you are taking the same approach as CM.

Hopefully there won't be setbacks for this... I had CM before, and because M releases are being held back because of issues with CDMA devices, I got stuck with a February release for my I9505 (and yes, I know I could have used nightlies, but the whole point of the CM installer and auto-updater was not having to).

Can you elaborate on how SlimOTA will handle current Stable 4.0 users, when a new Stable comes out?

Cheers.

Miguel
[Galaxy S 4 i9505 Original Android Development] kantjer:
That explains why my build today had issues. I need to change my build script.
[Galaxy S 4 i9505 Original Android Development] Tylog:
Yes sorry , I forgot to mention it this morning

I dont know. I realy have absolutley nothing to do with the OTA Updater :)
[Galaxy S 4 i9505 Original Android Development] kantjer:
No problem, no harm done. Thats why we have backups.

New version is already booting :fingers-crossed:

And up and running now!
[Galaxy S 4 i9505 Original Android Development] s3icc0:
I dont see KTweaker app there ... are we on Slim kernel now? I mean in the package

getting my stupid question back ... of course we are on Slim kernel when the build is unified :)
[Galaxy S 4 i9505 Original Android Development] Tylog:
After first boot nfc is greyed.

Put Nfc in the Tiles , activate it there and reboot, after reboot it's no longer greyed ( for me )

Tapatalk GT-I9505 / Nexus 5
[Galaxy S 4 i9505 Original Android Development] Tylog:
In the build.prop or use texdroider_dpi from play store for now.

https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=de

Tapatalk GT-I9505 / Nexus 5
[Galaxy S 4 i9505 Original Android Development] vpnair:
Go to /system/build.prop and change the ro.sf.lcd_density=361 to whatever you desire. I change mine to 401
[Galaxy S 4 i9505 Original Android Development] Tylog:
I have the third post some screenshots posted.

Tomorrow after work I'm going to the thread even revise a little.

Edit:

I use Kt kernel, original is stock, I will change this screen tomorrow :)
[Galaxy S 4 i9505 Original Android Development] aturbs:
Does the microphone work with this ROM for Hangouts and Soundhound?
[Galaxy S 4 i9505 Original Android Development] malybru:
Hi,

I am confused.

My SELinux is enforcing.

Yours is permissive.

Do you have any idea why it would be different?

:)
[Galaxy S 4 i9505 Original Android Development] Tylog:
Please test this.

Go to settings, developer settings , set root to apps/adb and reboot. I use superSu 1.80.

After this settings my SELinux show permissive.

If this not change it let me know, then i need to look if it comes from kt kernel. But enforcing SELinux is no problem.

Tapatalk GT-I9505 / Nexus 5
[Galaxy S 4 i9505 Original Android Development] Tripledrop:
Hi, I noticed that for jf devices the autorotate is broken. Is there a way to make this work? I had the same on OmniROM and figured it was the ROM, but looks like it's not?

Also, does audio out work when docked in car?

These are the 2 features that I care most about at the moment, hoping there's something I can do to make them work?

Thanks in advance
[Galaxy S 4 i9505 Original Android Development] malybru:
Hi,

Nope.

Installed superSU 1.80,set root to apps/adb rebooted several times,but still enforcing.

:(
[Galaxy S 4 i9505 Original Android Development] Tylog:
Then it comes with kt kernel, I will reflash the rom tomorrow and test it, I am now at work and can't test it.

But enforcing is really no problem :)

Tapatalk GT-I9505 / Nexus 5
[Galaxy S 4 i9505 Original Android Development] s3icc0:
finaly enforcing is what you want to be there ... so it is good news for you
[Galaxy S 4 i9505 Original Android Development] __NBH__:
Just installed the rom and it is working quite nicely but how do you get the quick settings in the notification screen? Like before there was wifi, bluetooth etc and you could customise the list, is this all done from the tiles now?

There is an option for quick settings but they go to the bottom of the screen.
[Galaxy S 4 i9505 Original Android Development] 1nstan7riod:
nice rom but skype voice calls dont wok, any fix?
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Time will fix it :D
[Galaxy S 4 i9505 Original Android Development] CallumMarks77:
no notification behavior :(?
[Galaxy S 4 i9505 Original Android Development] Tylog:
Guys, please don't forget, this is the first build , more features you know from 4.3 and before will come in the future.

This is the first release, all other things come from time to time, with every weekly :)

Tapatalk GT-I9505 / Nexus 5
[Galaxy S 4 i9505 Original Android Development] CallumMarks77:
true! will you be updating the feature list on OP as more gets added?
[Galaxy S 4 i9505 Original Android Development] Tylog:
Yes :) I will keep the thread up to date for 100 percent :)

All changes, news and all other you will find here in the thread in the future :)

Tapatalk GT-I9505 / Nexus 5
[Galaxy S 4 i9505 Original Android Development] CallumMarks77:
Great, will keep my eyes out for this feature as it's a must for me

---------- Post added at 09:46 PM ---------- Previous post was at 09:26 PM ----------

Anyway to get the stock launcher?
[Galaxy S 4 i9505 Original Android Development] Tylog:
I have test it for you, the difference comes from the kernel, with stock enforcing too :) but enforcing is really ok :)

Tapatalk GT-I9505 / Nexus 5
[Galaxy S 4 i9505 Original Android Development] kantjer:
Do you use an exFAT formatted sd?

If you don't need >4GB file size support just format it FAT32 and it will work with any Rom/kernel combination.

---------- Post added at 04:50 PM ---------- Previous post was at 04:03 PM ----------

How much memory have you assigned in VM?

I received a reply from the Slim guys and they now think the process is killed due to an outofmemory error.

I increased the assigned memory from 2 to 4GB now and started a new build :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] harise100:
2 GB of RAM. Should be enough for make -j2, I guess.

Reading my own last post again... I think I found my problem: DevDistro comes with 4.3 SDK.:cyclops: :eek:

Building a KitKat ROM might need a 4.4 SDK don't you think.....? :rolleyes:
[Galaxy S 4 i9505 Original Android Development] kantjer:
LOL that sounds logical
[Galaxy S 4 i9505 Original Android Development] tylok:
Thanks for the answer.

the question is: is this APK related? So if I use the Browser from the 4.3 gapps will the sync work?:confused:

By the way, can you point to an article that describes ART? I have no clue what it is... except that it is an alternative to Dalvik in some way...
[Galaxy S 4 i9505 Original Android Development] s3icc0:
1.6

1.6 booted slightly longer after flashing, but now it's flying :) thanx
[Galaxy S 4 i9505 Original Android Development] CallumMarks77:
Not going to bother updating to 1.6 as 1.5 is so stable for me so far, no fc and it's so fast!
[Galaxy S 4 i9505 Original Android Development] Tylog:
Fine , good to see you guys like it :)

Tapatalk SlimKat 4.4.2
[Galaxy S 4 i9505 Original Android Development] dikime:
Wooow... first ROM I see for any device ever where the boot animation doesn't lag :D
[Galaxy S 4 i9505 Original Android Development] kantjer:
Like it, I love it :)
[Galaxy S 4 i9505 Original Android Development] ImpheOtus:
As [MENTION=3306843]kantjer[/MENTION] said, not just liking it, but loving it!!!!

One feature I'm missing is hardware keys rebinding. When a build includes it, then I won't be needing anything else from this excellent ROM :D:cool:
[Galaxy S 4 i9505 Original Android Development] asfpf:
Does anyone can explain me what is the matter with the SlimKat kernel?

I saw a lot of people saying they cannot boot, stuck on Samsung logo.

I just downloaded rom and pretend to install it later night so I want to know what to expect.

BTW, which KT kernel version (or any other kernel) you guys use instead of slim kernel? And why?

Thx in advance.
[Galaxy S 4 i9505 Original Android Development] Tylog:
It's no big deal and the fix will come when we have time for it. If you have boot problems you can use aosp 4.4 kt kernel 12/04/13. It's the only custom kernel for now you can use.

If you have no problems stay on stock. It's not only a problem of slim stock kernel, it's a aosp problem on the S4. It will be fixed in the future but I can't tell you a exact date / time or whatever.

Tapatalk SlimKat 4.4.2
[Galaxy S 4 i9505 Original Android Development] mabmed:
Agree with you! But last tree days i had tested cm11 without boot problem! It boots normal!

Via Galaxy S4 GT-I9505 Black Mist!
[Galaxy S 4 i9505 Original Android Development] wonsky21:
http://xdaforums.com/showthread.php?t=2297379

this one?
[Galaxy S 4 i9505 Original Android Development] Tylog:
Yes, this one

http://ktoonsez.jonathanjsimon.com/sgs4/AOSP/KT-SGS4-KK4.4-AOSP-INTL-12.04.2013.zip

Tapatalk SlimKat 4.4.2
[Galaxy S 4 i9505 Original Android Development] Tylog:
Yes, could be.

I will speak tomorrow with the other guys and look if we can fix it in the next Weekly, I promise nothing but I take care of it :)
[Galaxy S 4 i9505 Original Android Development] ImpheOtus:
I haven't had a single stuck boot with Beta 1.6

I've done around 10 boots already; each and every time the phone booted without problems.

I'm on Canadian version though, I don't know if that matters.
[Galaxy S 4 i9505 Original Android Development] mabmed:
Don't forget the network type! Using the cm network type causes force close when you change network! Other rom uses nexus5 network type: Lte or 3G or 2G!

Via Galaxy S4 GT-I9505 Black Mist!
[Galaxy S 4 i9505 Original Android Development] RxLiTrO:
i have a noob question, sview cover works with this rom?
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Wakelock detector from play working again ...!!!
[Galaxy S 4 i9505 Original Android Development] kantjer:
You are correct, I hadn't noticed it because my script always removed KTweaker during flash.

I flashed alucard straight after the ROM so didn't even booted with stock kernel.

But when building the ROM earlier today I noticed a lot of kernel building activity that I normally never saw, so it's looks for the unified ROM where back at the stock (CM?) kernel.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
already updated my "stupid" question ...

btw the unification of builds was mentioned in the changelog Tylog posted earlier :) at least I noticed

finaly back to standard flash procedure - ROM - GAPPS - KERNEL :)
[Galaxy S 4 i9505 Original Android Development] kantjer:
ROM-Kernel for me.

Are you using the released alucard kernel? The reason why I ask

By pure coincidence I'm using a alucard version atm build with the unified Ramdisk.

I didn't read the changelog very well then :o
[Galaxy S 4 i9505 Original Android Development] s3icc0:
yes the IA version ... and everything is fine .... only SuperSU forgotten all my apps so I have to again allow root access to all ...
[Galaxy S 4 i9505 Original Android Development] Tylog:
Right :) I say it before some time that we go back to stock, now it's happens :)

Tapatalk Team SlimRoms
[Galaxy S 4 i9505 Original Android Development] kantjer:
That SU issue will be solved with the next kernel.

Alucard is already moving things back to how it was (git is being updated)

Thats why i'm using my own kernel build with that script already removed. I lost root completely.
[Galaxy S 4 i9505 Original Android Development] nexuspur:
Hey I have read some bugs with the stable release. Is this true and what should I use 4.0stable or 4.2 weekly? Thx

don't worry be happy :)
[Galaxy S 4 i9505 Original Android Development] kantjer:
The new weekly is less than 30 min. old and you already heard rumours about bugs?
[Galaxy S 4 i9505 Original Android Development] Tylog:
He asked about bugs in the Stable :)

Please test 4.2 or you have to wait for user feedback about the latest Build.
[Galaxy S 4 i9505 Original Android Development] kantjer:
Some users didn't have previews for video on stock gallery.

I have never had that issue, worst thing that can happen is that it isn't solved yet.

Never had any issues with weeklies, it's just a version number, so don't worry about it and just flash it.

---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------

Sorry your post was only 3 minutes old and I already managed to misread it.
[Galaxy S 4 i9505 Original Android Development] BustedFly:
I have now tested the Rom with the integrated KT kernel and Alucard 2.6.3gga.

The following result (Rom FullWipe, no additional apps or programs, minimal gapps)

Battery consumption with 1h test

KT kernel: 2.3% / h

Aluccard: 0.6% / h

So I go now but assume that the KT kernel problems with the battery drain has.

PS: Who do I contact me with the answer of 5 Min invisible barrier?
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
kt kernel can also have a good battery drain, but it strongly depends on your setting, which werent optimal in your case. both kernels are great btw. with kt kernel try to find your ideal usage with scripts and profiles.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
It's not really a fair test unless you give each kernel at least 2-3 full cycles to settle in then test in exactly the same way with exact same set up for a complete cycle.
[Galaxy S 4 i9505 Original Android Development] Kondra007:
No problems with dirty flash 4.2 over 4.0 ?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Hey, I'm going stir crazy and not sure if I'm being blind, dumb or just plain oblivious, but I can't for the life of me see the 4.2 build anywhere. I also noticed that you have taken your unofficial build down so I'm guessing the problems I experienced earlier (losing radio) must have been a wide spread problem for the rom and not just local to me?? Thanks as always for building for us though :)
[Galaxy S 4 i9505 Original Android Development] Kondra007:
What about this: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1184-jflte ?
[Galaxy S 4 i9505 Original Android Development] aeroman:
wiped Sytem/Cache/Dalvik and flashed over v4 works fine all so far. ;) :good:

Regards

●Sent from my Galaxy S4-LTE√
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Ah, yes - I read something about slim being unified, so jflte is good to go on jfltexx ?
[Galaxy S 4 i9505 Original Android Development] Kondra007:
Yep, though I haven't tested it myself.
[Galaxy S 4 i9505 Original Android Development] steveria79:
@ tylog

Flash with fullwipe 4.2

Vibration strength not change! ?

Picture gallery bug!? Look picture

Video preview bug is not fix!

slimKat Build. 4.2
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
flashed 4.2 with the latest alucard kernel and works great, gallery previews are okay, but for some videos it doesnt generate the thumbnails which i dont mind really :).
[Galaxy S 4 i9505 Original Android Development] Tylog:
Ok thanks. Then I will take a look myself and look for a fix at the next build.

Tapatalk Team SlimRoms
[Galaxy S 4 i9505 Original Android Development] steveria79:
I hopeful[emoji29]

slimKat Build. 4.2

---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------

Bug!?

slimKat Build. 4.2
[Galaxy S 4 i9505 Original Android Development] Tylog:
Yes, but only for now, the new build order is the reason for it, we need to change a few things in Slim Center :)

Tapatalk Team SlimRoms
[Galaxy S 4 i9505 Original Android Development] __NBH__:
My slim centre shows 4.2 as the latest version, looks fine but I didn't think weekly versions were included?

What is the section about cell broadcast all about? Amber warnings and all sorts of weird stuff.
[Galaxy S 4 i9505 Original Android Development] Tylog:
Yes, it only shows you the current build, updates are as ever only with stable builds on OTA possible.

About the broadcast settings I post tomorrow a few things , it's time for sleep now :) please remember me in the evening if I forget it :)

Tapatalk Team SlimRoms
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Has something been changed in the trigger for slim pie, it seems more difficult to trigger now when I have gel case on, before it just opened with no effort, now it seems quite hit and miss again??
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
Slimpie works perfectly here. Can't live without it. It makes multitasking much easier and fast. No need to spam the home button. A goddamn good feature:good::good::good::good::good:.
[Galaxy S 4 i9505 Original Android Development] Technical:
Any technical reason to abandon KT Kernel and drive back to Stock one?

Compatibility (due to merge with other S4 variants)?

Turning back to AOSP even more?

Performance?

I was getting used to KT and the ability to customize the kernel, then, suddenly, back to stock :silly:
[Galaxy S 4 i9505 Original Android Development] steveria79:
https://www.dropbox.com/s/imgimt6xlr8myac/bugreport.zip

Media Scan bug!

https://www.dropbox.com/s/imgimt6xlr8myac/bugreport.zip

slimKat Build. 4.2
[Galaxy S 4 i9505 Original Android Development] s3icc0:
The merge of jflte models maybe? You can flash KT manually now ... no one is forced to used any kernel and everyone can have a choice ;)
[Galaxy S 4 i9505 Original Android Development] kantjer:
Everything will be uploaded again as soon as I modified my build script to reflect the change to the unified ROM.
[Galaxy S 4 i9505 Original Android Development] latino147:
how is that possible to unify build? I assume that each device has an own camera and other hw that's device specific? It's not only the SoC that's the same is it?
[Galaxy S 4 i9505 Original Android Development] kantjer:
The ROM is unified for phone types that are closely related hardware wise. It's not one size fits all.
[Galaxy S 4 i9505 Original Android Development] wonsky21:
The bad side of unifying builds is that SGS4 Flasher, a very useful tool, doesn't work anymore. It shows the popup that the device is not supported (yet) :/

GT-I9505 | SlimKat 4.4.2 UNOFFICIAL build 4 by kantjer
[Galaxy S 4 i9505 Original Android Development] s3icc0:
u kidding right? :(
[Galaxy S 4 i9505 Original Android Development] wonsky21:
Nope. Try it yourself. I tried to flash different recovery img file... No go :/

GT-I9505 | SlimKat 4.4.2 UNOFFICIAL build 4 by kantjer
[Galaxy S 4 i9505 Original Android Development] s3icc0:
I sent a dump file to the dev ... hope he will get it working ... else back to ODIN .... (anyway we still have to stick with odin due to modems ... )
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm not saying we have no choice.

I just want to know why do the developers take this way, i.e., what do they have in mind.

This help me (us) to understand the technology behind the scenes :cowboy:
[Galaxy S 4 i9505 Original Android Development] Bejda:
About sgs4flasher,it still works fine on others unified jflte builds.

The thing is that the app probably make a "getprop ro.product.model" command to check which device it is running on and on latest SlimKat weekly ro.product.model (model number in settings>about phone) is still set via build.prop but to "jflte" (fortunately in a way it allows us a simple trick if really needed: if you change ro.product.model build.prop SlimKat entry to GT-I9505 and reboot sgs4flasher will work).

On others jflte builds this value is still GT-I9505 (visible in settings>about phone) but now settled on kernel side (probably via another getprop command,at every boot/init maybe),ro.product.model entry doesn't appear anymore in build.prop

Maybe we'll face others incompatibilities with some others apps if our product.model stays settled to jflte
[Galaxy S 4 i9505 Original Android Development] wonsky21:
That did the trick, thanks ;)

GT-I9505 | SlimKat 4.4.2 UNOFFICIAL build 4 by kantjer
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
you can try flashify app for flashing recovery and to flash multiple zips at once, kinda simulates an OTA update so you have 2 features in 1 app :).
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
I also have problems with my external sd card. Fixed permissions, clean install still a no go. Inrecovery it is recognized just perfect. Just a folder "sdcard1" with nothing in it. Will try to manually mount it and report.

Edit: No i am not able to access my external_sd. Anyone?
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
works with fine here. did you do full wipe prior to flashing? there might be a problem with the kernel. i suggest you try alucard kernel.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
I moved from cm to kantjers unofficial build from today with integrated alucard. Full wipe before flash and so on. Used Alucard before on Cm, so i am really confused :eek:
[Galaxy S 4 i9505 Original Android Development] kantjer:
The Rom doesn't support exFAT formatted cards. Make sure your sd is formatted FAT32
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
Ok like i thought, had to be the reason. Just thought this could not be possible because Alucard has build in exfat...

What exactly do you mean with the Romans?

Without exfat i am not able to use the rom, need it for Media Files.
[Galaxy S 4 i9505 Original Android Development] kantjer:
Typo
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
Ah ok.

Too bad with exfat...especially because the kernel can do this. Are there any plans about that?
[Galaxy S 4 i9505 Original Android Development] kantjer:
Try flashing original SlimKat and Alucard see if that solves it. Could be I removed a module too much.

EDIT: try to flash the attachment.
[Galaxy S 4 i9505 Original Android Development] Tylog:
The next few days before Easter I'm lancer again very busy. I have given kantjer right things to change in the thread, if a update comes and I should not be there :)
[Galaxy S 4 i9505 Original Android Development] ivankolev:
First of all we are waiting kantjer's alucard settings ;)
[Galaxy S 4 i9505 Original Android Development] kantjer:
Uploaded and linked in my sig.

---------- Post added at 07:57 PM ---------- Previous post was at 07:55 PM ----------

For those who want to experiment with ART but are afraid they will run into trouble have a look at the Enable ART Or Dalvik From Recovery thread. There you can find 2 flasable zip so if you for whatever reason end up in a bootloop you can always flash back to the desired Runtime compiler directly from recovery .

2 handy files to have stored on your SD just in case of.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Great link for such cases,thanks.

Way much more handy than type this every time someone's stuck lol
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
Don´t know whjat you did there but you are my hero :D

THANKS!!! Working like a charme
[Galaxy S 4 i9505 Original Android Development] theroar:
Greetings,

I have a 9505 that I updated today to slim kat from a stock 4.3. I used 2.7..0.0 to backup and flash.

I unfortunately lost my flash to page plus. I tried to go back and the restore fails.

I tried to update to 2.7.0.1, which I think from what I read will fix the restore issue. Twrp Manager and sgs4 flasher both say I am not supported.

Read that I need to change by build prop, so I used build prop editor to change it to jfltexx (currently jflte) but that is not working either.

Any tips on where I am wrong?

Thanks tons!

Mike
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
try philz recovery or remove the assert lines from the updater script

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] theroar:
Would philz work with my current twrp backups?

I tried to track down the updater script, but it is something have never messed with before. Is it inside one of the twrp manager .gz files?

Sorry if I sound clueless... but I am when it comes to scripting.

Thanks tons for the tips!

---------- Post added at 08:43 PM ---------- Previous post was at 08:35 PM ----------

Worked like a champ! Thanks.