yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] houmles:
Hmm, I am not sure if this is app related. I tried ES File Explore, TotalCMD and maybe another 10 file explorers on Play and all had same results. Even ES file explorer was recently updated and they said in changelog they fixed the sd write bug on SGS4.
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Hmm some users said it was OK, that's why I find it kinda odd. Android is so complex sometimes :silly:

I will figure it out, just might take some time (as usual XD)
[Galaxy S 4 i9505 Original Android Development] houmles:
It's definitely weird, even as root I don't have perms to write :(

shell@jfltexx:/ $ cd /external_sd
shell@jfltexx:/external_sd $ su
root@jfltexx:/storage/sdcard1 # id
uid=0(root) gid=0(root) context=u:r:init_shell:s0
root@jfltexx:/storage/sdcard1 # mkdir test
mkdir failed for test, Permission denied
255|root@jfltexx:/storage/sdcard1 # echo "a" > test
tmp-mksh: can't create test: Permission denied
1|root@jfltexx:/storage/sdcard1 #
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
hmm that's pretty odd yes. Do you use VFAT or EXFAT?

Maybe there is something with the mounting of it. you could try to remount it manually.

Also PLEASE make a logcat when the error occurs, hope it says anyting
[Galaxy S 4 i9505 Original Android Development] watnuweer:
Without the booster pack the fast charging is available again (no freezes).
[Galaxy S 4 i9505 Original Android Development] houmles:
It's ext4 with default flags, formated by phone and also tried it formating in linux.

Logcat is quiet. Nothing is here about permissions or problems with mount/storage.

This is from cat /proc/mounts

/dev/block/vold/179:33 /mnt/media_rw/sdcard1 ext4 rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0

/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

EDIT: remount didn't help
[Galaxy S 4 i9505 Original Android Development] skeamznz:
Thanks brood is there anyway to disable fast dormancy with a build prop edit or dialer codes? I remember there used to be and also the fast dormancy toggle dosent work on aosp ROMs which sucks
[Galaxy S 4 i9505 Original Android Development] Swanseatom:
Hey guys, been a while since I've been here. Loved your previous work on aosp for s4.

I've Recently been forced back to my s4 due to nexus 5 screen break. Being used to and a lover of aosp, I initially went to aosPA. Now wanting to be more stock. Dont like the CM base of aospa legacy so much. I've turned here. Big issue for me seems to be kernel issues. I've read through pages and pages and pages of this thread. Is anyone able/willing to sum up what issues there are currently with kernels for s4 aosp/cm and such. Seems so many issues but nothing consistent anywhere to give guidance.

Any help appreciated.

I am usually a long time dedicated faux user as far as kernel's go. Mainly cause I love his app.

I'm not asking for best kernel just advice on what the issues are currently in general with using custom kernels.

Regards,

Edit: reason I am asking here is cause I've decided to stick with broods aosp.
[Galaxy S 4 i9505 Original Android Development] RagingHarry:
Was just looking into the Dutch KPN/Hi network settings, had some connection trouble at work only, so thought, might be better to review them since CM has more often putted that idiot apn settings with password and username as default KPN apn(so those could be forked over from there).

if you use the by kpn provided settings there are only 2 apn's needed, and not a separate for mms stuff, cause that can all be within 1 apn config as kpn provides them.

And that was indeed the case.

Then went to the KPN site to see if they had some new stuff for LTE/4G network apn stuff, and it is there, and am currently on those settings, and while my living location is actually the very last part of the Netherlands that will get 4G (yep surrounded by it, but that is me in a circle of 35KM where 4G starts from off) but the 4G apn settings work if you have a 4G contract.

(CM really should remove that line in the apn configs with username and password, you even can't find those anymore on the KPN.com site ;)

But they/KPN have a nice pdf file ready with the correct settings for both needed versions of APN settings, 4G and non4G, so won't type them so that I can't make a typo :cyclops: .

But you can find them here.

https://www.google.com/url?sa=t&rct...GheUpsLIcTkt4YSvSw&bvm=bv.63934634,bs.1,d.bGQ
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
RRs and freezes are the problem, the most stable kernel I have found for aosp is the one in my signature ;)
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Oh how I wish I could run this. Jflteusc
[Galaxy S 4 i9505 Original Android Development] skeamznz:
Edit build prop and updater script?
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Yes and no, the code for that menu is *#9900# I believe, but when i run it I get invalid MMI code.

(almost every code returns that except a few which are uesless)

check out if it works

Lol the kernel is not that bugged XD. its actually pretty good. and has very little problems, but everything has been told already for a thousand times, if you do a simple search you can find all problems in this thread. only last remaining kernel bug is EGL bug (wrong sync behavior, fixed when disabling hw overlays, msmfb related) and maybe an other minor one but not more.

Random freezes fixed, video player crashes fixed.

CM is pretty stupid sometimes, no offense but a team with that many members may have to look better after their work then they do. (you dont even want to know how many times their build got derped because of reckless merging), since CM is the source for patches for all custom roms it impacts the problems on many roms.

Ill submit those kpn settings to CM. thanks for linking

freezes were the problem (are now solved) and RRs never happened! this is typical google edition behavior, my rom hasn't give me a single random reboot since the very first alpha that i ran!!:mad: so please know what you are saying..

:silly::silly:

you can, and you don't have to adjust anything at all. just install and boom

I removed assert lines from there, was tired of removing them manually each time.
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Even thought mine is CDMA? Is this unified?

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

Gonna give it a go. Crosses fingers cause if this works and runs good then I'm gonna be extatic.

---------- Post added at 06:33 AM ---------- Previous post was at 06:14 AM ----------

Holy cow. Dude this is awesome. Curious. Did Google change the button and text coloring from blue to white? I know they changed it in their icons.
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Yes unified since RC5.

and no I did that with help of some topic to make it extra kitkatty
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Just whatever you do don't use qcril. Apareny that's what cm did and it caused all kinds of issues on CDMA. But seriously man. You are tha man
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
I won't, funny that you say that I just was talking about cm merging way too many things that actually break new things.

Thanks! I'm out of thanks for today xd
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Its all good. I've been hearing this KitKat white theme thing. Is that what they did to the new source.

---------- Post added at 06:39 AM ---------- Previous post was at 06:37 AM ----------

This is seriously rock solid dude. Finally I have pure aosp. Only reason j ask about that is it seems every one I've tried using KVT the blue sliders and text throughout the ROM is now white.

---------- Post added at 07:16 AM ---------- Previous post was at 06:39 AM ----------

Never mind. I see the mention of the theme in the OP. Is there any way to revert that without having to decompile. Like pull the apks from a nexus ROM or something like that? Kind of like the blue accents and can't stand using xposed.

As for the cm deal. I love cm. I have been a huge supporter of them for a long time. This build shows that you can do a unified ROM and it actually work. They merged that qcril and it hosed all the CDMA devices. We can't even get 3G on USC. The other either can't connect or won't stay connected. To me the benefits of qcril aren't great enough to cause a hundred issues across 6-7 devices. So yeah I agree. Now they're about to release a M5 build and not even sure they'll have data working. So a stable release that isn't stable. Its not the devs fault. They're busting they're ass. Its the higher ups. OK I won't rant anymore.lol. seriously amazing work. I remember when you started this. You have come so far with it.
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Ok well what you can do is this, you only need to replace the res folders inside frameworks-res.apk and SystemUI.apk in order to get the old colors back, you can get the normal res folders from RC3, take it from there. (just replace in archiver)

and yes idd, as I said the merging is really reckless, the developers only contribute. AOSP is the best example how it should be done. their merging is really strict. (and devs from many big companies commit as well)

and thank you! I do my best to make flawless android products for all devices ^^
[Galaxy S 4 i9505 Original Android Development] skeamznz:
Your right I get an invalid mmi code. Would be great if someone could make a xposed module or an app that's universal (dreaming)
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
you are indeed dreaming, that is impossible. biggest problem even is that when entering the correct codes it still doesn't work, so other apps can also not deal with this. it has to be fixed internally.

these are the codes according to SamsungServiceMode

if (TextUtils.isEmpty(code) || code.equals("197328640")) {
// Use default (this exists to prevent NPE when code is null)
}
else if (code.equals("0011")) {
modeType = OemCommands.OEM_SM_TYPE_MONITOR;
subType = OemCommands.OEM_SM_TYPE_SUB_ENTER;
} else if (code.equals("0228")) { // 0BAT
subType = OemCommands.OEM_SM_TYPE_SUB_BATTERY_INFO_ENTER;
} else if (code.equals("32489")) {
subType = OemCommands.OEM_SM_TYPE_SUB_CIPHERING_PROTECTION_ENTER;
} else if (code.equals("2580")) { // ALT0
subType = OemCommands.OEM_SM_TYPE_SUB_INTEGRITY_PROTECTION_ENTER;
} else if (code.equals("9090") || code.equals("7284")) { // PATH
subType = OemCommands.OEM_SM_TYPE_SUB_USB_UART_DIAG_CONTROL_ENTER;
mAllowBack = false;
} else if (code.equals("0599") || code.equals("301279") || code.equals("279301")) {
subType = OemCommands.OEM_SM_TYPE_SUB_RRC_VERSION_ENTER;
mAllowBack = false;
} else if (code.equals("2263")) { // BAND
subType = OemCommands.OEM_SM_TYPE_SUB_BAND_SEL_ENTER;
mAllowBack = false;
} else if (code.equals("4238378")) { // GCFTEST
subType = OemCommands.OEM_SM_TYPE_SUB_GCF_TESTMODE_ENTER;
mAllowBack = false;
} else if (code.equals("0283")) { // 0AUD
subType = OemCommands.OEM_SM_TYPE_SUB_GSM_FACTORY_AUDIO_LB_ENTER;
} else if (code.equals("1575")) {
subType = OemCommands.OEM_SM_TYPE_SUB_GPSONE_SS_TEST_ENTER;
} else if (code.equals("73876766")) { // SETSMSON
subType = OemCommands.OEM_SM_TYPE_SUB_SELLOUT_SMS_ENABLE_ENTER;
mAllowBack = false;
} else if (code.equals("738767633")) { // SETSMSOFF
subType = OemCommands.OEM_SM_TYPE_SUB_SELLOUT_SMS_DISABLE_ENTER;
mAllowBack = false;
} else if (code.equals("7387678378")) { // SETSMSTEST
subType = OemCommands.OEM_SM_TYPE_SUB_SELLOUT_SMS_TEST_MODE_ON;
mAllowBack = false;
} else if (code.equals("7387677763")) { // SETSMSPROD
subType = OemCommands.OEM_SM_TYPE_SUB_SELLOUT_SMS_PRODUCT_MODE_ON;
mAllowBack = false;
} else if (code.equals("4387264636")) {
subType = OemCommands.OEM_SM_TYPE_SUB_GET_SELLOUT_SMS_INFO_ENTER;
mAllowBack = false;
} else if (code.equals("6984125*") || code.equals("2886")) { // AUTO
// crash
subType = OemCommands.OEM_SM_TYPE_SUB_TST_AUTO_ANSWER_ENTER;
} else if (code.equals("2767*2878")) {
// crash
subType = OemCommands.OEM_SM_TYPE_SUB_TST_NV_RESET_ENTER;
} else if (code.equals("1111")) {
subType = OemCommands.OEM_SM_TYPE_SUB_TST_FTA_SW_VERSION_ENTER;
mAllowBack = false;
} else if (code.equals("2222")) {
subType = OemCommands.OEM_SM_TYPE_SUB_TST_FTA_HW_VERSION_ENTER;
mAllowBack = false;
}
[Galaxy S 4 i9505 Original Android Development] skeamznz:
Thanks for all your help brood I'm loving this ROM so much I'm changing to Vodafone NZ they have fast dormancy
[Galaxy S 4 i9505 Original Android Development] venneke93:
I do have random reboots like 3 times a day. Either screen goes white, or reboots while locked with screen off.

Came back from omni to this ROM for battery, yet those RR kinda make me question my choice.

Did fully clean install btw.
[Galaxy S 4 i9505 Original Android Development] !crazy:
[MENTION=4354408]broodplank1337[/MENTION] I suppose CM also uses new SELinux policies, and I flash it without any problems with TWRP.

I'll ask this again :), haven't you decided to ditch SELinux out of your ROM/kernel? Is it back for good?
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Hmm still sounds strange to me.. Never had RR

Yes it does, mabye I have still missed some commits. and no I did not ditch it, since AOSP uses it initially, and this is AOSP. but I did remove a while ago some NSA backdoor
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Do you have a link to the RC3 I can pull those pngs from. Been a while since I've been theming so systemui and framework right. Is it the entire res folder or just the main ones?
[Galaxy S 4 i9505 Original Android Development] Broli@666:
Hello brood! Thanks for your great Rom! Works very stable with no problems so far.

Just 2 things: need to Disable hw overlays for gaming and the picture of the front camera is deformed in Skype or tango, while video Telefonie. (on other aosp Roms (slim or cm) I have the same problem, but not under tw or ge roms)

If you need, I can send you a Screenshot, but therefor I need you address.

Greetings broli

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] venneke93:
They started occuring when I switched from RC3 or 4 to omni and back, after that skipped RC5 due to the RR, now back to PreFinal and still having RRs.. It might be just me, but seeing other people also have freezes and RRs, it might be something in the code perhaps.

Still the best ROM out there though, lost 2% battery in 10 hours sleep :laugh:
[Galaxy S 4 i9505 Original Android Development] !crazy:
Some 30 pages before:

http://xdaforums.com/showthread.php?p=49938803

---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------

@broodplank1337

This is even better :

http://xdaforums.com/showthread.php?p=49933864
[Galaxy S 4 i9505 Original Android Development] scarmon25:
I did what you said and replaced the res folders. Still have some whit text that should be blue. I am assuming that's in smali? Seems I would have to smali the classes.dex to fix that wouldn't I?
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
look at www.broodplank.net/files you can find all versions that still exist there

and yes the whole res folder

You're welcome, yes I know this, this is because AV enhancements are ON in this build which bugs it

Ok hmm, will wait what other users says.

and nice, thats a really little percentage!

Well.. I just did that PreRC4 build without SELinux, I have never said anything about me permanently removing it.

it doesn't say unoffical for nothing :P

did you also do SystemUI.apk ?
[Galaxy S 4 i9505 Original Android Development] scarmon25:
How many framework-res.apk edits where there between rc3 and the latest other than UI edits? Cause if I replace the framework it fixes the ui parts.

Seriously though. This thing is so solid. Even with the RC3 framework-res.apk in it. The only thing I see is the Samsung thing I see in every unified aosp ROM. The network name is roaming indicator off. That's so little I could care less. All I can say is wow.

Oh. One thought I had. Since this is your build and not sure you would want to do this. But you may consider null the system update option in settings and killing the option in there. Just something I've seen other people do. Nothing important.
[Galaxy S 4 i9505 Original Android Development] K900i:
um....did as per instructions ...now the status bar is missing :P ( shadow is not there anymore :P)

and I need to remove the shadow at the bottom aswell.
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Yeah I did the system ui. The text coloring is in framework. I swapped the rest folder like I was supposed too. When that didn't do the text I just swapped the entire framework. That fixed it. My question now is how many edits were made to framework-res.apk between then and now other than UI parts? Wanna make sure I'm not shooting myself in the foot and killing off improvements by doing that.
[Galaxy S 4 i9505 Original Android Development] Broli@666:
Hey brood, short question, why can't I use swipe with the included keyboard?

Edit

Got it.. Needed the goggle keyboard...

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] -sandro-:
I have one question, I used this ROM months ago...is the screen brightness still jerky while changing and not smooth like tw ?
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
the bottom? has no shadow right?

I think 3, but in framework-res.apk nothing has changed for 3 releases. also it does not contain any java. the improvments are in the kernel and in other non framework related files. don't worry

I see you figured it out already ;p

Yes it is fixed now haha, it was because of the qualcomm powerhal, you must be happy hehe:silly:
[Galaxy S 4 i9505 Original Android Development] scarmon25:
These two commits should fix the Roaming Indicator bug.

http://review.cyanogenmod.org/61713

http://review.cyanogenmod.org/62157

They did for CM. Figured I would let ya know.
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Thanks a lot!
[Galaxy S 4 i9505 Original Android Development] scarmon25:
That was really the only little "bug" I found in this build. Personally would still null the system update just to keep someone from accidentally taking an update. But that's just me. Gotta give ya some credit bro. You've done an amazing job with this. There are very few vanilla aosp builds out there that are as smooth as this is. I have always loved pure Google. Gonna definitely check out your new custom one as well. If you do half as good a job on it as you did this then it will be rock solid. I have a feeling it will be better.
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
I just merged it, thanks. and you cannot update trough that function in any possible way, so I will disable it though because it only eats battery. And thank you very much, I am just dying to have a fully functional AOSP on every device that I own, so that is what I will do. and my custom rom will also be become like this, I prefer only to make good products, since android and programming is my passion hehe.
[Galaxy S 4 i9505 Original Android Development] scarmon25:
Just keep going in the direction you are going man. Most people out there just fork cyanogen and cherry pick. Not taking away from them as it takes some work to make those picks work. But you have put some actual screen time in this. Be proud my friend. Very proud.
[Galaxy S 4 i9505 Original Android Development] Barthlon:
Good man. This kind of posts is what keeps developers going! :)

Brood, do you think the 4.4.3 update will give you a direction for the few remaining 'bugs'? Will 4.4.3 be the base for your Final? :o:o
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
I will! and yes its a big adventure to get aosp working from google sources, but its worth it! I have spent over 500 hours working on this rom I think so that's definitively true and yes I am proud of it.

Indeed that is true, it makes you feel appreciated, but thats always the case here! as long as you don't produce crap hehe.

and the final V1 will be 4.4.2 or 4.4.3, I don't know but I will keep updating the finals, just for huge things only such as a version upgrade.
[Galaxy S 4 i9505 Original Android Development] -sandro-:
Hi did you look into Samsung Service Mode I once asked to see if it could work on non-TW ROMs?
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
yes I did. but I don't really know how to use it. I tried it to make the MMI codes work (like #*9090#) but it didn't make any difference. and the mmi codes is what is inside the core of the app. maybe I have missed something?
[Galaxy S 4 i9505 Original Android Development] Edgio60:
Broodplank lad, this rom is quality. Can't find a fault with it. If you can eliminate all holo blue it will be perfect.
[Galaxy S 4 i9505 Original Android Development] umd:
I'm not sure if it's just me but I was getting up to 3.5 hours screen on time with RC4 and RC3. Now with the PreFinal I'm getting 2+. RC5 was the same.

And I definitely agree with the posts above. This rom is the main reason I still keep my i9505. This is the real "Original" Android Development.
[Galaxy S 4 i9505 Original Android Development] hlxanthus:
[MENTION=4354408]broodplank1337[/MENTION]

A bug I don't see listed is keyboard related. It has to do with autocorrect. So misspell a word that doesn't get auto corrected. It shows up red underlined. Touch that underlined word and it brings up a selection of potential correct spellings. Select one and it FC's the app you are in. Usually I see it the most in hangouts. I know there the first word in the input field will correct properly, but any other FC's the app. We have seen this in OctOS for months, but doesn't in the other major Roms out there. It was there before cm unified the jflte tree. I am jfltevzw, and usually use the latest pa stock gapps
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Thank you :) there are some minor ones but they won't bother you, look a page back or so how they fixed it

It definitely the network type. I also have poor battery life atm.. I have to fix that because some people have a very good battery life and some very poor.. the ones that have a very good battery life are the people on LTE I assume. not sure though

just added F2FS file system to the rom/kernel btw, this is the new filesystem from samsung that has better performance.

hmm I have heard something about a missing libemoji but not sure if its that. to be honest I don't know how to fix this, mabye some patch in frameworks/base is missing in my tree and so thus in yours. I will take a look
[Galaxy S 4 i9505 Original Android Development] scarmon25:
When you said you will freeze the updater did you mean you would also take the option out the about phone section? Going through and looking for anything he he. I think me and you may be alike in the perfectionist aspect. I can't get over how solid this thing is. Samsung and AOSP has always been quirky. Always some major issue.

Oh. As for the qcril deal. From what I understand most of the beneficial parts of it are already in the aosp source. They finally found the fix for the CDMA stuff on cyanogen. But seeing as the good parts are already in the source seems like there's no need to mess with it further. Go figure huh LOL.
[Galaxy S 4 i9505 Original Android Development] TemporaryTester:
IIRC, when you delete the updater, the menu option automatically vanishes. I'd assume identical behaviour occurs when you freeze it.