yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] FernBch:
Hi Everyone,

I have been testing a build slated for release when things are ready.

Don't ask for an ETA, about when will it be ready, or anything like that. It will be ready when it is ready and not a moment before. If it hasn't been released it obviously is NOT ready yet. Sorry, I definitely do not intend to be rude but I feel it needs to be said.

Now that that is out of the way.

I have come across a repeatable pattern (may be part of the reason why there is no new CDMA release yet).

For those who are having WiFi and/or BT issues (Doesn't matter if you are GSM or CDMA). Do any of you notice the "Do Not Disturb" feature acting wierd as well? I have found a repeatable pattern and can make things either work or not work by following a certain procedure each and every time, guaranteed.

If I do the following:

Boot into recovery

Choose Factory Reset or manually wipe Cache, Davlik, and Data

Install ROM

Install Gapps

Wipe Cache and Davlik again

Reboot

The ROM will boot but I have issues with Bluetooth not turning on and WiFi is sometimes "weird". It will behave this way each and every time I follow these steps when I flash. Sometimes choosing "Erase Personal Data" from within settings>backup & restore will give the same results.

If I do the following:

Boot into recovery

Manually wipe Cache, Davlik Cache, Data, AND internal Storage (this will get /Data/Media and all personal user data - internal storage will be empty. Backup First!!!)

Install ROM

Install Gapps

Wipe Cache and Davlik Cache again

Reboot.

Good part is everything will work every time I do it this way. The FIRST time. No flashing a second time. And it is repeatable every time, guaranteed.

Bad part is it means backing up pictures, documents, etc and wiping the phone CLEAN.

I started noticing some things and spent the day today testing my theory. After flashing SEVERAL times each way I would get the same exact results with each of the above methods.

As it sits right now almost every issue I have reported is fixed. The "message not sent" error with SMS and the red underline missing with misspelled words is all I still have (can't speak for exfat support, my extsd is in vfat).

I have provided detailed reports to the developers and they are fully aware of what I have found. As for the solution, I do not know.

That is why I said: Do Not ask for ETAs and such. Progress is being made. Please be patient. We want you to have something good, not something with issues. We cannot always get things 100%, it's just the "nature of the beast". We can, however, give it our best to deliver the best we can. That is why I often say " Help us to Help YOU. Provide clear description and include logs".

Enjoy Everyone!
[Galaxy S 4 i9505 Original Android Development] Th3_uN1Qu3:
I wiped everything before installing the ROM, including personal data, because i formatted to F2FS. Still had the bluetooth issue. What fixed it for me is letting the ROM boot without gapps, then installing gapps. then booting, then wiping /data, /cache and dalvik one more time. The second wipe was necessary because i was getting lots of FCs of google play services.

The Do Not Disturb feature was fine for me even when my bluetooth was not working.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
[MENTION=535343]all[/MENTION]: please can you install OFFICIAL TWRP 2.8.7.0 JFLTEXX and procede with the flash of rom and gapps? Please report here.

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] dvhttn:
I always wipe everything except my sdcard when installing a ROM and have seen the BT issue. Same symptoms as have been reported - wifi disconnected and wouldn't reconnect even though settings said BT was off. Had to reboot.

Also seen the LTE bug. It was connected, phone went into pocket whilst shopping. Took phone out and LTE/Mobile data wouldn't connect until I went into airplane mode and out of it. But it's difficult to test this one out as LTE has only just been switched on where I live and nowhere near my house ....

Never use this. Can't understand why Google made it so bleddy complicated!!!

Oh, and using TWRP 2.8.7.2-AntaresOne ...

Cheers.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
We had a hint from Antaresone.

try to delete /data/data/com.android.bluetooth and reboot.

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
And what does this do?

Is it needed if I did a clean flash?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Try in case bt is not working.

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] AaronEmoBoi:
Can you still install the GSM version if you only use WiFi? I don't even have a sim card in my GS4
[Galaxy S 4 i9505 Original Android Development] dvhttn:
Tried this. No change - still the same problem with BT not connecting and wifi being disconnected at the same time.
[Galaxy S 4 i9505 Original Android Development] Galukon:
I have TWRP 2.8.7.2 no F2FS i think and I have 0 issues. Bluetooth does turn on and WiFi the same. I don't stream BT but i know it turns on. Further really no issues. Very happy! :D
[Galaxy S 4 i9505 Original Android Development] oli.henning:
Hey guys, i didn't want to hear why it is/should/would be a bad idea. It is clear, that you loose the standard "poor old Fat32 SD-card features" with this new Marshmallow function.

In my opinion, this Google solution could be a all-users (non-root, non-nerd, non-Custom-ROM) replacement for all "Apps-to-SD" or "Link-to-SD" workarounds.

Therefore: If you guys say, that "formatting SD card as internal storage" is a bad idea - then please also state: What is the better idea?

Note: Link2SD and App2SD (both from PlayStore) also do not work with this ROM.

So back to my original question: Did anybody used this "formatting SD card as internal storage" successfully with this ROM? Or could you please try it? Thank you
[Galaxy S 4 i9505 Original Android Development] SaulGoodman88:
How can i use this Rom without the Alucard Kernel?

And from where can i get a working stock Kernel?
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Gsm is the type of phone that you have. The international (i9505) is a gsm version. It has nothing to do if you use wifi or not
[Galaxy S 4 i9505 Original Android Development] gaww:
I am on a m919. My Bluetooth and WiFi OK, but still have to toggle airplane mode to get connected to network.
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
In 5 hours time, com.google.android.gms fired 589 alarms. Does anybody know what this process is doing? I know I can limit it with amplify, but I want to know what the source is.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
It belongs to Google Play services app.
[Galaxy S 4 i9505 Original Android Development] AaronEmoBoi:
Okay let me re define my question xD if I do not need to use cellular on my CDMA GS4 from sprint can I just flash the GSM version?
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I don't know about that. It won't hardbrick your device, so do a nandroid backup, wipe system, data, cache and dalvik and try it.
[Galaxy S 4 i9505 Original Android Development] abzjji:
Are Layers Themes save to use with this rom? Even if I filter for Android M themes it always tells me they are not supported by this rom.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Yes... most themes are ok... the message you see is not true, because probably it check the android version and 6.0.1 is not yet included... try Inversion UI for example...

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] dancekid:
Hello Community,

any chance of getting a contact manager with groups support like "contacts for lollipop" ? I use CM mostly and did sort my contacts into groups.

Michael
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Does it not survive a "regular" OTA update, i. e. a "dirty" flash where you keep everything on /data?

That would be a major design flaw, IMHO...
[Galaxy S 4 i9505 Original Android Development] thaidroid:
I just tried, installed a theme called inversion. Like it for the most part. Only one problem, uninstall does not seem to work....unless I'm doing something wrong

never tried layers before.:D
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Ciao, why do you want (many of) us to downgrade to 2.8.7.0? Is there anything wrong in 2.8.7.2?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
It is a trial to understand if recovery has influence. But from results it do not give difference.

Inviato dal mio GT-I9505

---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------

Uninstall do not work from app. If you wanna remove, go to /vendor/overlay folder, get r/w rights and delete the files... reboot.

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] dvhttn:
I use True Phone from the Play Store which does this for you ... https://play.google.com/store/apps/details?id=com.hb.dialer.free&hl=en ...
[Galaxy S 4 i9505 Original Android Development] HITMAN-CREED:
Really Strange!!!

Every game that i install, and want to enter it, after 4 or 5 seconds it gives me Force Stopped.

i tried asphalt 8 & Need For Speed No Limits & Riptide Gp & ...

Any Sugesstion?
[Galaxy S 4 i9505 Original Android Development] FernBch:
It should. I have not tried it but I can't believe that Google would release 6.0 with that kind of flaw. If I understood what I read correctly it ties the card to a specific device when it is set up as internal storage. This means that other devices cannot read it, even a PC. I don't know what effect flashing different ROMs on it is but I did read that it cannot be moved to a different device without most likely formatting.

Read more here:

http://liliputing.com/2015/10/android-6-0-can-treat-sd-cards-as-internal-storage-at-a-cost.html

https://groups.google.com/forum/m/#!msg/eyes-free/rspqjlmu_ss/ouM7TMH-BQAJ

Some of the reviews on adopting the extsd to int storage hint at the "costs" associated with it. I have even seen comments where people regret doing so.

I chose to ignore what MM was asking and leave it alone. Meaning I set up access through my file manager (Root Explorer is my choice).
[Galaxy S 4 i9505 Original Android Development] Strephon Alkhalikoi:
Considering that when I tried it TWRP wasn't able to access the adopted storage, it's difficult to install ROMs without decoupling the MicroSD from the rest of the storage using Android's built-in tools. However, given that adopted storage is encrypted by default, installing a different ROM will render the MicroSD card unusable, meaning the card will have to be formatted. This is because the new ROM won't have the encryption key needed to access the MicroSD. Installing an OTA update for the ROM currently on the device should not affect the storage since the key likely wouldn't be stored in the /system partition. If that key IS on the /system partition, then that is a problem, especially involving ROMs that do what the JDCTeam ROMs do, and wipe the /system partition prior to installing the update.

It's easier simply to ignore the prompts, and set up the storage to be portable.
[Galaxy S 4 i9505 Original Android Development] cob11341:
Deleted. Wrong thread.
[Galaxy S 4 i9505 Original Android Development] abzjji:
Installed this theme yesterday.

https://play.google.com/store/apps/details?id=com.setiawanjimmy.TheMagpie

It totaly ****ed up my phone. It wouldnt boot anymore (Stuck at boot animation). Had to flash the rom again. So better dont use this one.
[Galaxy S 4 i9505 Original Android Development] Chibbo:
that theme works you just need to read, blame the theme creator for making it complicated not the rom
[Galaxy S 4 i9505 Original Android Development] thaidroid:
Has anyone tried SuperSU 2.65?
[Galaxy S 4 i9505 Original Android Development] mico.barac:
Issues with latest ROM

I experienced the following issues with the latest ROM so far:

- I cannot switch to 3G / it always reverts back to LTE

- I experience total loss of mobile signal in the middle of the city, where the signal is proved to be strong / Restarting restored signal back

- Close all active apps option is missing

- After locking a phone, Menu and Back lights blink a few times and stay on for 10 seconds / If this was meant to be a feature, I must admit it is strange a bit :)

- When ordering quick settings tiles, I cannot make Mobile data stand next to Wi-Fi, like Bluetooth does by default

JDCTeam, thanks for a lovely ROM and Happy New Year to y'all!!!
[Galaxy S 4 i9505 Original Android Development] HITMAN-CREED:
Have downloaded the latest 24 December Version??

- i can easily swith between 2G/3G/LTE

- go to setting>display>Recent apps and turn on Clear All Button.

- i don't use backlight, you can turn it off in Setting>display>Backlight and Untick Illuminate Buttons.

- For Quick Setting, why don't u use Xposed & Gravity Box?

See my Screenshots here:

JDC Team AOSP 6.0.1 (2015/12/24)

Nova Launcher Prime + Xposed + Gravity Box + Greenify

Click on the Screenshots to get full size:

---------- Post added at 13:38 ---------- Previous post was at 13:14 ----------

Flashed it, No Problem here.
[Galaxy S 4 i9505 Original Android Development] audianer:
Hey guys! How works the sd card at this rom? I got big write access problems with the official cm13 nightly.
[Galaxy S 4 i9505 Original Android Development] FernBch:
What kind of problems?
[Galaxy S 4 i9505 Original Android Development] JohNNyum:
Hello there,

Running the latest build for two days and no issues at all.

Is there any way to turn on the "Nav Buttons on screen" ? Like we do on CM ?

Thanks,

JohNNy
[Galaxy S 4 i9505 Original Android Development] a103:
SD card works just fine. I was able to write to and read from SD card.
[Galaxy S 4 i9505 Original Android Development] audianer:
With cm13, i cant write on sd card with fileexplorer and on windows.
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
That makes perfect sense to me!

Thanks!

---------- Post added at 15:44 ---------- Previous post was at 15:41 ----------

I'm sure TWRP simply isn't compatible yet. In a while the TWRP guys will have added Marshmallow compatibility, and then this issue will be gone.
[Galaxy S 4 i9505 Original Android Development] Strephon Alkhalikoi:
[MENTION=3297960]thaidroid[/MENTION]: Yes, and it works fine. The S4 doesn't require systemless root with this ROM, so the version included in the ROM is simply replaced.

[MENTION=6224324]ralfbergs[/MENTION]: Well, TWRP can see the folder structure on adopted storage, but it cannot access any files in it, and can neither read nor write to the adopted storage. The sole reason why is that when adopted the storage is automatically encrypted. Now I know you're being optimistic here, but the TWRP guys have a lot of work ahead of them. In order for them to read the adopted storage properly they would either need the cipher that encrypts the adopted storage, or they would need to rebase TWRP off a recovery that already has encryption support, such as the recoveries in the Nexus devices.

Realistically Google isn't going to let a third-party recovery have access to its encryption cipher for adopted storage. So, as I see it, there's two options here. Either give up the custom recovery or give up adopted storage.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Google didn't really think this through when they made the option. Sure, you buy a new device and get an sdcard. But at some point you will change the device. So what do you do with the sdcard if it's formatted as internal for the old device?

Only option is to format the sdcard again and lose your stuff. Unless you backup. But this whole process takes some time. Especially if you have a 64 GB one.

If the sdcard remaines a portable storage, you just eject it from the old device and pop it into the new one and you're good to go.
[Galaxy S 4 i9505 Original Android Development] Strephon Alkhalikoi:
Why should Google think this through?

If I recall correctly, the encryption was implemented to improve the security of data in a corporate environment. In a corporate environment, you're not using root, nor are you using a third-party recovery, and therefore this issue will never come up in that scenario. Since the data is more secure, it only helps Android integrate with the corporate environment.

Google likely doesn't see this as an issue. And for the 99% of the populace with an Android phone, it will not be an issue either. For the 1%, many of which are on this site, they have to decide whether adoptable storage is worth losing most of the functionality of TWRP.

Personally, adoptable storage is not worth it. Not if you care at all about root.
[Galaxy S 4 i9505 Original Android Development] ro-mann:
I've installed the latest release after doing a factory reset. When installing Open Gapps after that and reboot I get constant errors with Setup Assistent and Google Play Services constantly force closing. Have tried it multiple times, it occurs every times.
[Galaxy S 4 i9505 Original Android Development] lemurm1n:
Try to flash gapps pico.
[Galaxy S 4 i9505 Original Android Development] dilidani:
Man you always have some lovely screenshots to post! :D Next time please share the name of the icon pack please :D (last time was moonshine)
[Galaxy S 4 i9505 Original Android Development] j0hnbh0y:
wipe cache and dalvic
[Galaxy S 4 i9505 Original Android Development] ro-mann:
Still get the errorrs and force closes.

After or before installing Gapps?
[Galaxy S 4 i9505 Original Android Development] lemurm1n:
Ok, try to formate system, data, and cache then flash rom then gapps.
[Galaxy S 4 i9505 Original Android Development] a103:
Below are the steps i follow-

Put the ROM zip and open gaaps mini on external SD card.

Reboot to recovery (I prefer twrp)

Backup your current ROM OK n external SD card

Select wipe - wipe data/factory reset

Select advanced wipe - wipe cache, internal storage,data and dalvik

Reboot to recovery again

Flash ROM and gaaps from external SD card.

Never got FC or error.
[Galaxy S 4 i9505 Original Android Development] HITMAN-CREED:
Yep, Last Time was moonshine.

And this one is Urmun.:D

And i found something better.. a mix of Touchwiz and AOSP.

I mean this AOSP Rom with Touchwiz Like Launcher. I will share screenshots here. after some minutes..
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Notice

Back on jflte, unique build/zip for any variant. :good:

https://github.com/AOSP-JF-MM/platf...mmit/74cb986f5978006d89e6b28bea1013b25d9a6acb

https://github.com/AOSP-JF-MM/platf...mmit/7e0151bd3e1158bd2d24d828b2b9a8cc2f1dc76c

https://github.com/AOSP-JF-MM/platf...mmit/83cb1c3c9d6842f28313c763d71e5cbc4b286102
[Galaxy S 4 i9505 Original Android Development] oran3e1:
If i clean flash this ROM now will my SD card still work? if so can i move apps to it when internal storage is low?
[Galaxy S 4 i9505 Original Android Development] lemurm1n:
Yes, your sd card will still work. You can move apps to sd card if you set it as internal storage but i didn't set it as internal storage so i can't confirm if it will work without issues.
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
I hope I'm not missing anything, but it should be "straight forward" (I'm not saying it is easy or quickly done!): We have the full source of the OS that can unlock and r/w the encrypted FS. So we can also add this functionality to TWRP. Seems not like witchcraft to me... ;)

N. B.: If I say "we" I mean a group of skilled developers. :)
[Galaxy S 4 i9505 Original Android Development] ro-mann:
That worked, thanks!
[Galaxy S 4 i9505 Original Android Development] Strephon Alkhalikoi:
I'd like to see it happen, but I don't expect it to happen because the entire reason Google implemented encryption in the first place was to enhance Android data security in the corporate space. Given that we're talking encryption here, you'd have to find some way to decrypt the card so TWRP can read the files. I don't know what bit-length cipher Google used, but you can probably be sure it's at least 256 bits. The amount of time it would take to break a 256-bit cipher using a brute force attack is in the neighborhood of 11 quintillion years*. Nobody is going to wait that long, so you better hope quantum computing comes about so you can break the encryption in six months. Otherwise, you'll just have to hope Google will be nice and give you the cipher, which is unlikely.

So, again, you either give up on the recovery, or you give up on adopted storage. At this time, these are the two choices available to everyone, and things I don't see changing in the near future.

* 11,000,000,000,000,000,000, or in scientific notation, 1.1 x 10^19 years. This is about 800 times the current age of the universe.
[Galaxy S 4 i9505 Original Android Development] mjrider:
Can somebody tell me why i'm wrong here

* sdcard can not be read in recovery

Why not, the key is somewhere on phone, the recoveries have to get a new feature, i'm guessing the key is somewhere in the /data/ directory, because thats the only sensible location. The system partition is readonly. ( yes we can remount it but android will not do that normally )

* sdcard content will be lost on an update

Why, the key is still somewhere on an rw patition, untill you do a wipe. recoveries learned to wipe data without wiping /data/media/ so next trick is to save the encryption key on wiping.

* sdcard is non transportable to an other phone

Makes sense, because the sdcard is now an internal and essential part of the old phone

* difficult to transfer data to it

and how did you transfer data to the internal sdcard, right with a cable or bluetooth or some other method of transportation

my sdcard never left my phone since i put it in there, and i would gladly use it as internal, to bad i couldn't get it to work. Android complains about the write speed of the card.

hopefully this will turn the discussion in a more technical and solution minded discussion instead of 'it is al broken and google is mad' kinda statements without an fundation
[Galaxy S 4 i9505 Original Android Development] -Deco-:
You have to understand that encrypted data is a part of the way that MM handles a SD card if a user would decide to use it as internal memory. Encrypted data is data which cannot be accessed, even if you managed to find the decryption key, then you would have the trouble of actually disconnecting the SD card from Android. Which by the way is a hardcoded part of Android, so the code cannot be tampered with without issues arising.
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Wait, somehow we're having a misunderstanding here...

Look, /data is encrypted, but somehow the owner can decrypt it, right? Or else the owner couldn't get access to their data...

How does that work? I assume (because I've never used encrypted storage in Android so far, so I have to guess) that at a very early point in time when booting the system it (the system) wants to mount the /data partition, but it is "locked" (encrypted). So the user has to input a passphrase that will either be used to directly derive the decryption key (by using PBKDF or similar), or to decrypt a decryption key found on the device. As soon as this decryption key is available the system can go ahead and transparently decrypt the encrypted /data partition.

So, why can this mechanism not be replicated in TWRP? I fail to see why you need to employ any sort of "brute force." You would implement the decryption in the very same way as in CM-13.

Is my point now clear?

---------- Post added at 23:52 ---------- Previous post was at 23:48 ----------

I do not get your point. Can you please elaborate on what exactly you're saying? What exactly would not work in your opinion, and why?