yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] onebyside:
same here pj...just waiting for next changelog that addresses the prob
[Galaxy S 4 i9505 Android Development] Eguy:
It was fixed today by a revert! All is well.
[Galaxy S 4 i9505 Android Development] ciabatoni:
app2sd

I have a VZW gs4, Im on the me7 build and I also have the loki bootloader patch, and rooted. Im currently running CleanRom 1.5 Everything works besides MMS, I cant send or receive. but, im over that. However, I would like to have the App2Sd. So, Im wondering if this rom would be for me, and will the app2sd definitely work? Would the be anyway I could use the app2sd patch and merge it with my current rom somehow. Curious. Ill jump on this rom If I cant and the feature works ok, Thanx

---------- Post added at 12:27 AM ---------- Previous post was at 12:14 AM ----------

2nd thought I should also be able to test run this thru the loki bootstrap beings it has several rom slots. However it will probably be a problem as I dont have that much memory left, thus being the reason I want app2sd, Hehe
[Galaxy S 4 i9505 Android Development] clshores:
Just to update the unknown device issue, I updated my wife's d2spr device to the unified build on official CM11 and it too shows the device as unknown. Sounds like something that CM will have to workout on their end.
[Galaxy S 4 i9505 Android Development] mbc663:
just add....

ro.product.model=WHATEVER DEVICE

to build.prop. reboot. probem solved
[Galaxy S 4 i9505 Android Development] clshores:
Understood but it has to be done after each flash and that means every day for most of us. :D I'm sure they will resolve it soon.
[Galaxy S 4 i9505 Android Development] buzzwyzr:
I'm on Sprint and have had no issue with "unknown" since the unification builds started.

I clean flashed the first unification build though and have been using delta to update since.
[Galaxy S 4 i9505 Android Development] gravedigger76:
Did you try today's nightly? Some folks in CM thread said its now showing model after today's nightly flash... I haven't had the time yet so don't know myself.
[Galaxy S 4 i9505 Android Development] clshores:
It is my morning ritual and yes it still shows unknown. Might have to wait until tomorrow for it to show up for us.
[Galaxy S 4 i9505 Android Development] gravedigger76:
If in fact it was fixed... I didn't see any commits that were close resembles the issue were seeing though..
[Galaxy S 4 i9505 Android Development] ciabatoni:
???

does anyone have sum advice on the things Ive asked up above, I dont know if it got skipped over due to my multi quote. I could really use a hand though thanx in advance
[Galaxy S 4 i9505 Android Development] clshores:
I think that might be what it takes to make it work. I plan to do that tomorrow. I am a severe weather reporter for our local area and we have some mean stuff coming through tonight so I need my phone 100% for posting updates.
[Galaxy S 4 i9505 Android Development] mbc663:
So the lives of many could be in jeopardy and u use nightlies??? :confused:
[Galaxy S 4 i9505 Android Development] clshores:
Always a backup! Nothing out of the ordinary on the device, just have to make sure I have something stable available.
[Galaxy S 4 i9505 Android Development] mbc663:
lol, gotcha. be careful out there then! :good::good::good:
[Galaxy S 4 i9505 Android Development] clshores:
Just noticed on today's sprint build I have lost simultaneous voice and data. Anyone else?
[Galaxy S 4 i9505 Android Development] onebyside:
why not backup your present setup and try the rom
[Galaxy S 4 i9505 Android Development] pjkiener:
So I read someone else had this same problem and he reverted back to the 15th build of this ROM. That fixed his problem and mine as well.

Mind you, I previously flashed the 19th straight from the 13th or 14 build, and that's when the problems started. Anyway, so reverting back to the 15th build fixes the problem, then you can do delta updates (I updated through delta, after flashing the 15th build, to the 19th build) and everything will be fine again. I just updated through delta today and still all good here.

I hope this fixes your problem as well. Cheers!
[Galaxy S 4 i9505 Android Development] gaww:
Didn't work. Updated from 2/14 to 2/15 and unknown device. Will probably have to do the build.prop edit until CM gets that act together.

---------- Post added at 06:05 AM ---------- Previous post was at 05:47 AM ----------

Then why doesn't CM put it in there ?

Just did it and no problem with play store. Where there other issues ?
[Galaxy S 4 i9505 Android Development] gravedigger76:
Hi Chen,

How come the first part of this commit didn't make it into the build? https://github.com/chenxiaolong/CM_frameworks_base/commit/7917bbf6b4594c0c3f411891bb0f1d138d94efde

CM Had 1/2 and 2/2

EDIT: although power shutter is no longer FCing camera. Yey! Wonder what is the quality difference in pics with powershutter on vs. Off.

:confused: :)
[Galaxy S 4 i9505 Android Development] clshores:
Bump

No one else experiencing this?

---------- Post added at 10:47 AM ---------- Previous post was at 09:54 AM ----------

UPDATE: Just clean flashed and still have unknown device and I also get the FC on the process com.android.incallui has stopped

Also defaulted me to GSM on a sprint device which game me no service until I changed it in APN settings.

Also still have no simultaneous voice/data.

Restoring the nandroid.
[Galaxy S 4 i9505 Android Development] ciabatoni:
wont work

It wouldnt matter at this point bc after installing gltools my device wont boot past the safestrapp logo, so backing it up would be pointless I assume. Bc Ill be backing up a rom that freezes once at that logo.

I found the gltools uninstall.zip, Im wondering is I install it like a rom or mudule,zip thru safestrap. would it execute the uninstallation of gltools? I do\idnt try it bc it had a notice like it could cause unknown issues or something like that.
[Galaxy S 4 i9505 Android Development] rlorange:
I would say because the universal build needs to accommodate many model names. It's the detection and build prop editing code that's broken

---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------

Are you using the stick cm kernel? Haven't check days/voice but wondering if it's bugged on kt kernel too
[Galaxy S 4 i9505 Android Development] clshores:
I am on latest KT and yesterday was on the previous KT with the same results. I might just try stock kernel for kicks to see if there is a change.

---------- Post added at 03:10 PM ---------- Previous post was at 02:52 PM ----------

It is indeed an issue with the KT Kernel. Stock CM kernel works like a champ. Off the the KT forum to let him know.
[Galaxy S 4 i9505 Android Development] rlorange:
Oh nice detective work bro :) must be that huuuuuge 2MB WiFi driver from 4.4 tw sources
[Galaxy S 4 i9505 Android Development] otto888:
I used to use the international builds since I'm using a GSM SIM in The VZW S4. The VZW builds would not allow me to receive calls or hang up outgoing calls. Now that the builds are combined, I'm having these issues again. Is there any way to force the zip to install GSM related files instead of the VZW files?
[Galaxy S 4 i9505 Android Development] clshores:
KT says not his issue. Doesn't touch modem code. I guess that makes it s CM issue possibly.
[Galaxy S 4 i9505 Android Development] gaww:
I am not having issues with kt (patched) kernel that I have been using for weeks.
[Galaxy S 4 i9505 Android Development] gravedigger76:
[MENTION=244141]Chen[/MENTION]

I see that you're build server creates a buildprop file outside of all the commit merges and file built?

The file contains jflte as model instead of i337 etc.. (Same as the one that ends up on our phones...it contains woodbury's build info etc..)

https://www.dropbox.com/s/eyybm603fdmqfr8/build.prop

Is this something that could be programmatically fixed on you're build server for unified builds that would reflect each phone model?
[Galaxy S 4 i9505 Android Development] rlorange:
My solution is to just add the modded build prop to the kt kernel zip file I flash after every update
[Galaxy S 4 i9505 Android Development] gravedigger76:
Can you share how and what?

Thanks.

Sent from my Nexus 7 2013
[Galaxy S 4 i9505 Android Development] rlorange:
Sure. You add these two lines to your build prop

ro.product.model=GT-I9505

ro.build.product=jfltexx

Or whichever model you have. Using a text editor. Then unzip kt kernel zip. And add the modded build prop to the system folder inside the zip. Then rezip. I use root explorer to do it all.

Also you can add any other files you like. Like init.d scripts or sound volume booster files.

---------- Post added at 06:07 PM ---------- Previous post was at 06:03 PM ----------

---------- Post added at 06:53 PM ---------- Previous post was at 06:07 PM ----------

Reply what device model are you on?

---------- Post added at 06:59 PM ---------- Previous post was at 06:53 PM ----------

Everyone just thought I'd share this zip I made:

You can put any file in the corresponding folder under system and it will flash and set correct permissions

https://www.dropbox.com/s/c6qfj350kskjdfe/EMPTY_RECOV_ZIP__SYSTEM_dualboot.zip
[Galaxy S 4 i9505 Android Development] ninjazin:
Had hanging on bootscreen with art enabled for latest build. Just read in official thread that this is due to ART. Disabling ART made the device boot. Just for info

Skickat från min GT-I9505 via Tapatalk
[Galaxy S 4 i9505 Android Development] clshores:
Does anyone have the last non-unified jfltespr build still floating around? I want to test it and see if simultaneous voice/data issues vanish with KT kernel.
[Galaxy S 4 i9505 Android Development] rlorange:
How long did you wait? It takes aaaages before the app cache starts building...
[Galaxy S 4 i9505 Android Development] ninjazin:
About 20 min. 3 times I tried. I have been using ART about two months now and now how long it usually takes to build cache. But when cache is building at least you pass the boot animation.

Skickat från min GT-I9505 via Tapatalk
[Galaxy S 4 i9505 Android Development] gaww:
Will this modded Kt kernel be patchable after the build.prop is inserted ?

Update - so if we just put build.prop in this zip file rather than the kernel and re-zip - it is already patched ?
[Galaxy S 4 i9505 Android Development] gravedigger76:
Awesome. Thanks man. I'm on ATT I337
[Galaxy S 4 i9505 Android Development] gravedigger76:
OK with today's build (not 100% sure I also updated KTs kernel today to today's fix release) model number is back :)

Besides kernel update and today's nightly flash didn't change a thing!

EDIT: since looking at the changelog and there are no commits with exception of calendar derp fix... Could it be due to kernel fix/update with KTs?
[Galaxy S 4 i9505 Android Development] clshores:
Mine is correct as well.. I didn't check before applying the fixed KT kernel. Anyone else notice it being fixed that hasn't update to the fixed KT kernel?
[Galaxy S 4 i9505 Android Development] AJ Newkirk:
It is fixed when you flash KT kernel. Not fixed otherwise.
[Galaxy S 4 i9505 Android Development] Bejda:
Apparently it is now based on a getprop ro.bootloader command trough updater-script + /system/blobs/cdma,gsm and vzw folders in the rom zip:

ifelse(is_substring("I337", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/gsm/* /system/"));

ifelse(is_substring("I545", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/cdma/* /system/"));

ifelse(is_substring("I545", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/vzw/* /system/"));

ifelse(is_substring("L720", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/cdma/* /system/"));

ifelse(is_substring("M919", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/gsm/* /system/"));

ifelse(is_substring("R970", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/cdma/* /system/"));

ifelse(is_substring("I9505", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/gsm/* /system/"));

ifelse(is_substring("I9508", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/gsm/* /system/"));

So on my side except editing the updater-script i can't see any workaround at the moment.
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Yep, it's due to the kernel update :) The model number and other device-specific build.prop changes are now set during boot by the "/init" program in the kernel's ramdisk. When KT updated to the latest CM sources, that made the issue go away.
[Galaxy S 4 i9505 Android Development] chenxiaolong:
You will need to open META-INF/com/google/android/updater-script, delete the two "I545" lines for Verizon and change "I9505" to "I545". That way, the files for the international S4 will be installed.
[Galaxy S 4 i9505 Android Development] buzzwyzr:
Can ART be activated on the latest nightly? From 022014 onward if i enable ART the phone won't boot.

Thank you.
[Galaxy S 4 i9505 Android Development] b1czu:
Same problem here. Stuck on boot animation forever.

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Galaxy S 4 i9505 Android Development] rlorange:
Chen have to released your dialer with the updated reverse look up providers yet?
[Galaxy S 4 i9505 Android Development] arjuna_:
Anyone know if CM11 builds for S4 will be built using KVT49L AOSP update anytime soon? I guess some phones already have it on theirs.. no rush just curious.
[Galaxy S 4 i9505 Android Development] Buster99:
SELinux status is set to enforcing, any reasons why this was changed?

cheers

buster
[Galaxy S 4 i9505 Android Development] zman2107:
When I make or receive calls this is all I see can't answer incoming can't hang up on outgoing on both 24th and 25th build this is my first update since merged build I'm a vzw user if that helps
[Galaxy S 4 i9505 Android Development] clshores:
Try and clear your data from the dialer app and see if that clears it up for you.
[Galaxy S 4 i9505 Android Development] chenxiaolong:
If you delete /data/data/com.android.dialer/dialer.db using a root file browser and then reboot before receiving another call, that should fix the issue. (You will lose your call history though).
[Galaxy S 4 i9505 Android Development] chenxiaolong:
Are you using a custom kernel? SELinux is still set to permissive in the kernel bundled with this ROM.
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Have enforcing too :(

Always had official cm builds and your builds and always ktoonsez kernel...

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Android Development] chenxiaolong:
You would need to ask ktoonsez to add "androidboot.selinux=permissive" to the kernel command line. There's nothing I can do to change the SELinux status of custom kernels :(
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Ok thanks. What's the difference between permissive and enforcing? How does it change my android rom/behaviour?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Android Development] rlorange:
Hey guys I've been working on more universal and robust way to Backup and Restore the second ROM

Here is the first release: A pair of recovery zips to backup/restore to external SD card:

https://www.dropbox.com/s/825rionf3ert0ls/DualBoot_BACKUP_ExtSD_V3.1.zip

https://www.dropbox.com/s/afmgxr2kdtionmg/DualBoot_RESTORE_ExtSD_V3.1.zip
[Galaxy S 4 i9505 Android Development] chenxiaolong:
CM's SELinux policy isn't really too bad. It mostly controls what the framework can do and what can access to the hardware, so eg. the bluetooth service cannot communicate with anything except for the bluetooth hardware, even if it runs as root. You shouldn't run into any issues unless some root app tries to access things it really shouldn't, like:

Editing certain build.prop settings in RAM instead of changing build.prop and rebooting

Directly accessing certain hardware using paths in /sys

Xposed modules doing things normally forbidden (although this doesn't happen often)

Most custom kernels and root tools will work just fine with CM's SELinux policy.

EDIT: I use bluetooth as an example, it actually, it's in the unconfined domain in CM (meaning it's unrestricted): https://github.com/CyanogenMod/android_external_sepolicy/blob/cm-11.0/bluetoothd.te#L7
[Galaxy S 4 i9505 Android Development] zman2107:
Deleted whole database file reboot same clear app data and cache reboot same not sure clean install of 24th then opendelta update to 25th
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
[MENTION=4277844]chenxiaolong[/MENTION] [MENTION=4125648]WoodburyMan[/MENTION] could you trigger a new build. Quite a few new changes.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Android Development] zman2107:
Fixed by downloading ray dialer in play store now stock dialer works
[Galaxy S 4 i9505 Android Development] clshores:
I saw that once and after clearing data it went away for me.
[Galaxy S 4 i9505 Android Development] zman2107:
Tried on phone and dialer app just glad it works now can't seem to change ROMs like this to much crackflashing addiction solved
[Galaxy S 4 i9505 Android Development] mrgreaper:
same issue as last time i tried a cm rom...wifi refuses to work, when i try to connect it drops the signal down to 1 then sticks on authenticating then switches to saved, really need wifi

searching this thread says its fixed in the latest nightlies thats why i tried it but its not fixed or i have another issue...any details you need just ask

Did a full factory wipe + formated sd card and its working ...yay!
[Galaxy S 4 i9505 Android Development] Buster99:
nah, all stock. :)
[Galaxy S 4 i9505 Android Development] WoodburyMan:
Sorry just saw this now! Busy day yesterday.

Nightly already went through this morning though so you should be good :)
[Galaxy S 4 i9505 Android Development] mrgreaper:
*URGENT* *MAJOR*

I woke up to find an update was needed, so dutifully updated

but when i make or recieve a call i get "unfortunatly com.andriod.incallui has stopped." then the only way to hang up is to pull the battery!

i consider this to be a rather major flaw in a phone os lol

any ideas on how to fix it?

*edit going back to stock, these custom roms are just too much hassle (no offense ment)
[Galaxy S 4 i9505 Android Development] gravedigger76:
Good idea

, less folks not reading the threads with the same posted just 2 posts above yours! AND a recommended fix!

:confused:
[Galaxy S 4 i9505 Android Development] mrgreaper:
yep definatly a good idea it means i also dont have to deal with snide remarks like that, its very easy to miss an error when it worked fine untill the update today and therefore i only looked at errors reported today, including googling the error, and reading through loads of pages unrelated errors BEFORE posting here but hey you werent to know that ... for future reference a simple "the solution is a few posts above your post" would of been better then trying to belittle someone you dont know, ah the anonymity of the internet where its socialy acceptable to make others feel bad.
[Galaxy S 4 i9505 Android Development] zman2107:
True but to make ROM look bad without waiting for a response to a fix isn't nice either
[Galaxy S 4 i9505 Android Development] mrgreaper:
it was never my intention to make the rom look bad, i should of phrased my "no offense ment" better, the rom looked very good, it was very responsive and much faster then the rom i used before it. it was only the issue i had first with wifi that i had before (though fixed this time with a factory reset, that didnt fix it last time), and the error with the dialer. The only critisim i have of the rom is the onscreen keyboard, i dont like not having the numbers at the top ( a very minor point as new keyboards can be installed)

For not waiting, i was expecting a call and didnt post untill i had very little time left to fix it, didnt expect a reply or fix immidiatly (im told developers and coders have lifes too, who knew?) so i went with what i saw to be the only solution. in hindsight im not sure why it hadnt occured to me to try a different dialer ui..oh well live and learn.
[Galaxy S 4 i9505 Android Development] zman2107:
Sorry please try again this ROM is awesome and if interested KT kernel works great with this
[Galaxy S 4 i9505 Android Development] clshores:
Discussion over please. This isn't the place for arguing. We are all here to help each other and support the wonderful work that our Devs have contributed their personal time and energy to. And the usual disclaimer to all is that this is a nightly build and your results may be unpredictable.
[Galaxy S 4 i9505 Android Development] buzzwyzr:
Nvm...no need for rude comment. My bad.
[Galaxy S 4 i9505 Android Development] vikash0513:
I got problems with my dialer everytime i make a call the screen turns of automaticaly and it doesn't respond when i want to turn it on is there a way to disable this
[Galaxy S 4 i9505 Android Development] gravedigger76:
Looks like builds failed a couple of times this morning. CMs commits?
[Galaxy S 4 i9505 Android Development] onebyside:
delete /data/data/com.android.dialer/dialer.db using a root file browser and then reboot before receiving another call, that should fix the issue. (You will lose your call history though)

worked for me
[Galaxy S 4 i9505 Android Development] jasonkx:
Do you chenxiaolong, have anyplan on add the Hal Sview COver to the CM base?
[Galaxy S 4 i9505 Android Development] rlorange:
I'm getting DC on my signal bar... Never seen that. Since the latest update. What is it?

---------- Post added at 08:38 PM ---------- Previous post was at 08:26 PM ----------

Ah it's DC-HSPA+ Im guessing it's just reporting the connection as such and not actually activating something that we didn't have before?
[Galaxy S 4 i9505 Android Development] bruc3lee:
Anyone got new data connection symbol /text. dc it says above signal bars?
[Galaxy S 4 i9505 Android Development] maikinho10:
Hm? Where is the Link? :D

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] alipingdante:
..got the same
[Galaxy S 4 i9505 Android Development] assasin34:
i cant find 6.0.3.3 tar version to flash with cwm..!
[Galaxy S 4 i9505 Android Development] Stevemeister:
Flash .img with the app 'SGS4 Flasher' from the Play Store. It doesn't get any easier than that....
[Galaxy S 4 i9505 Android Development] boterkaaseneieren:
Did you look in upstair, under the bed? Well I use search button and look here it is

http://xdaforums.com/showpost.php?p=44152958&postcount=353

http://xdaforums.com/showthread.php?t=2359132
[Galaxy S 4 i9505 Android Development] maikinho10:
Sometimes i wonder, it is really to hard to read few pages back????.

Few members (e.g.. Kurtcobain, boterkaaseneieren, Stevemeister and chenxiaolong) gives soo much help but its very annoying if its the same questions again and again :(:(

but of course we love to help...:highfive:
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Of course we do but some still don't get it... Oh btw I'll write you a pm tomorrow morning ;)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] assasin34:
it is not your business..!
[Galaxy S 4 i9505 Android Development] maikinho10:
ok;))

Of course not...but he will help you and he means only that its very easy to search..

No offense Buddy...:)
[Galaxy S 4 i9505 Android Development] Stevemeister:
Well it seems like it is. I've seen people ask about stuff that is answered 2 posts above theirs.

So let's see how long it takes for someone to post someting about their phone which doesn't boot :eek:.

BTW: I'm seeing audio improvements. DSP manager seems to work better but bass amp gives distortion. Google Play Music continues now after a track is finished. Not quite there yet but getting there.