yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Not true.

Please read this: https://source.android.com/devices/storage/adoptable.html

If it doesn't work with this ROM, then it's not per Marshmallow design, but due to some defect.

---------- Post added at 11:05 PM ---------- Previous post was at 11:01 PM ----------

Without a SIM you cannot attach to the network (except for emergency calls which you can place on some networks even without a SIM), and therefore you cannot obtain the time via the mobile network.

Getting the time via WiFi is independent of a SIM and should always work.
[Galaxy S 4 i9505 Original Android Development] walttheboss:
Great work [MENTION=5968293]side[/MENTION]. One small non essential I would like is a quick settings toggle for VPN. Now it takes four clicks to turn off vpn. Would be nice to have a button to kill all vpns.

Another small thing. How hard would it be to add a dropdown to select your country in location settings. That selection would edit gps.conf so the correct servers are selected.

Thanks again for all the great work.
[Galaxy S 4 i9505 Original Android Development] side:
you can change it through stweaks

about vpn.i will check it
[Galaxy S 4 i9505 Original Android Development] echo_21:
Sorry for being not clear with "If so wouldn't it make sense to build stable 3 on the snapshot cm13 state of stable 2 to prevent introduction of new issues?"

So let me revise: " If so wouldn't it make sense to build an optimized stable 3 on the Basis of the cm13 state as of stable 2 to prevent introduction of new issues?"

What do we win if we always upstream from newest cm13 nightlies with new but yet unknown issues?

I vote for building next stable n+1 on the same cm code as of stable n. If after 1 week stable n+1 has been proven error free there could be a stable n+1.1 with upstream from newest cm sources. Its a pretty good practice in Software development not to change too many things from one release to a successor: in case you have a new issue it is sometimes hard to find the root cause.

Thus, i vote for smaller steps in optimized cm13 releases.
[Galaxy S 4 i9505 Original Android Development] side:
this is what we are currently doing mate...the sim issue is not caused by upstream merge.

think about i released 11 build to test team since stable2.all issues were caused by anything else but not upstream :)

The sim issue was VERY SPECIAL since noone from test team had that issue.
[Galaxy S 4 i9505 Original Android Development] echo_21:
I didn't know that (how could i as i am not a member). Sounds to me as if these 11 builds were exsctly the smaller steps i mean.
[Galaxy S 4 i9505 Original Android Development] markiarom:
[MENTION=5968293]side[/MENTION]

On previous builds i had Qmuxd problem. I always turn logcat off. I read you said Qmuxd is related to logcat off, so also on stable 3 is better to keep it on?
[Galaxy S 4 i9505 Original Android Development] side:
yes.those are the smaller steps :) dont worry about it
[Galaxy S 4 i9505 Original Android Development] side:
[MENTION=2309228]Chibbo[/MENTION] can u help him :D ?

He is our "crash the gps" guy :cool::cool:
[Galaxy S 4 i9505 Original Android Development] markiarom:
FEAR T.T

Please don't eat me :P
[Galaxy S 4 i9505 Original Android Development] side:
hahha no mate.chibbo is team's gps guy.he surely got a better troubleshoot than me
[Galaxy S 4 i9505 Original Android Development] sjamie:
Yes, otherwise you will have the qmuxd issue.
[Galaxy S 4 i9505 Original Android Development] markiarom:
Uhm, interesting.. ok, i'll keep it on, thanks a lot!
[Galaxy S 4 i9505 Original Android Development] sjamie:
You're welcome! The Test Team determined there is no real battery savings by disabling logcat.
[Galaxy S 4 i9505 Original Android Development] hemmie:
[MENTION=5968293]side[/MENTION] and team;

Thanks for coming up with these build and know these require lot of testing and is practically impossible get all issues irons out, especially when you guys are providing a community service. We do greatly appreciate effort and time.

Is stable 3 build fixes the nagging Viber speakerphone Bug. I have found in previous build Banks gapps are better/stable than Open gapps pico. Any potential issue with Banks gapps.
[Galaxy S 4 i9505 Original Android Development] side:
finally a guy with patience :angel::angel:

hmmm..i use viber...can u tell me how to reproduce the viber bug ?i didnt touch anything related to sound on stable3.whats going on at stable2 according to viber?

I dont use gapps.i got my apks to sd ...no battery drain-no sh%ts
[Galaxy S 4 i9505 Original Android Development] Spriz:
Undervolt

Hello to all.

someone tell me if the alucard kernel already has a preset undervolt ??

or has only the option and parameters that you see are those of the factory ??

thank you
[Galaxy S 4 i9505 Original Android Development] side:
generally alucard supports it.although we set it up as disabled.undervolt is causing many issues that sometimes can cause ur device to not even turn on again..also sometimes it doesnt notify u etc....i dont agree with it.as i know synergy kernel supports it.u can use it
[Galaxy S 4 i9505 Original Android Development] -Deco-:
Further research of this brings you to the following:

Provides a unique disk GUID and unique partition GUID for each partition - A good filesystem-independent way of referencing partitions and disks.

The GUID which the device is assigned is stored on the "internal storage" partition.. the SD card's UUID however is not. It is stored on the /system partition of the ROM, and as such that particular partition is wiped before flashing an updated version of ROM.. which destroys your encryption keys.
[Galaxy S 4 i9505 Original Android Development] side:
its how deco says....

adoptable storage works fine with our ROM.but let me say something about it and make it clear.

as deco sayed adoptable storage uses encryption.that means u cant share that sd card anymore to other device...

.............TO OTHER DEVICE....

our storages ,sdcard internals are always located to /data/media/

the /storage/0 is just the mounting point(think it as a shortcut)

-yes but what happens when i wipe with twrp ?can i still access it ?

-yes and no.

when u run aroma and u are about to select wipe there are 4 options called

"extreme wipe" -> Wipes EVERYTHING...wipes data/media too.that means all storages(internal and adapted but not external sd)

"full wipe" -> wipes everything except the partition /data/media (that means wipe but not internal)

"dirty install" -> wipes only the cache/system

"Do nothing". -> do nothing (theoritically u have done ur wipes at twrp before aroma)

so...if u used ur sdcard as internal and extremelly wipe ,then u r done-byebye files

if u "dirty install" the same rom ,the files are accessable.

if u "full wiped" the files are not accessable but are still there

in conlusion....

my experience says : adoptable storage is fine only when u flash 1 rom per 2-3 months....

my experience also says: COME ON.........whos using that sh$t...we are s4!...we got over 16gbs of internal....sdcards are made for photos and media..not apps...also,even if u adopt ur sdcard as internal,the speed wont be the same OF COURSE...

i find no reason for adoptable

So the statement "your rom doesnt support it" cant even exist...we are custom roms.we flash rom once per week.we are not stock...stock stays as it is for years.

PS.

not an aggressive answer .i am just explaining :)

PS2.

New poll added​
[Galaxy S 4 i9505 Original Android Development] kenetix:
Yes. I flashed Stable 2. Still downloading stable 3. I have had this sim card thing pop up from a couple of different roms. Just an FYI. It says for me to reboot. I cleaned out my sim slot, thinking it would help. It did, but periodically I have the same message. Thank you guys for making this old phone still rock.
[Galaxy S 4 i9505 Original Android Development] sjamie:
Where do you live and have you had any trouble getting AT&T's LTE service on your i337m?
[Galaxy S 4 i9505 Original Android Development] kenetix:
Live south of Chattanooga. Yes, LTE is sometimes on and off. I change my APNs around and can finally get it. But it is iffy. The other day the phone showed no service until i tried to make a call. Then it suddenly started working.
[Galaxy S 4 i9505 Original Android Development] sjamie:
Has LTE always been iffy for you or just on Stable2?
[Galaxy S 4 i9505 Original Android Development] kenetix:
I don't think it's your rom. One way i found to get it to work is to toggle LTE off to 3G, then back to LTE. Sorry i can't provide more info. I can install Stable 3 in a bit and try to get some info for you through logcats. Just let me know.
[Galaxy S 4 i9505 Original Android Development] sjamie:
Yes, please let us know how stable LTE seems to be on your i337m once you are on Stable3. We'd greatly appreciate that.
[Galaxy S 4 i9505 Original Android Development] hemmie:
Hello [MENTION=5968293]side[/MENTION], I think that could be related to gapps, have good feeling about that. When you go to speakerphone in Viber mic gets muted, but only in Viber spkeakerphone mode., Also in Video mode Viber automatically goes to speakerphone mode hence with video as well other party can't hear your voice. Viber with normal mode works fine.

I've had some of these Viber issues in the past with some of previous builds too, I think you might not have seen these Viber issues coz you don't install any gapps, could be somehow gapps takes over Viber mic for some of the listening modes, but I do not see any issues with phone app, only with Vber.

Let me know your thoughts, thanks!
[Galaxy S 4 i9505 Original Android Development] kenetix:
Ok. Will flash in a bit.
[Galaxy S 4 i9505 Original Android Development] VirusPT:
Hi,

Anyone using eXtremeBeats Aural Maximizer with this rom? It works?

Have a nice weekend, thanks.
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Source?

This is not true. It is always stored on the partition itself. It may be referred to on /system to mount the partition, sure.

Read Google's article again. It is crystal-clear and leaves no doubt. Do you really think Google are so dumb and short-sighted to design it in a way you said?
[Galaxy S 4 i9505 Original Android Development] sjamie:
I think the best way to discover the absolute truth is to set up your device using adopted storage then attempt to update the ROM build and see what happens.
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
You seem not to confirm what deco said, but rather to contradict him.

Let me recall what he wrote:

You said:

This is crystal-clear -- Google even explicitly mention it in their article.

You are confirming what I said from the very beginning.

Just for the record: I didn't say it doesn't support it. I said the following (which is quite different!):

That's "if..."! Note that I didn't write:

It doesn't work with your ROM, but it's not per Marshmallow design, but due to some defect.​

I cannot really make a statement myself if it works in your ROM or not, since I never tried it, as I only have very old, sow uSD cards, so I didn't see a point in slowing down my phone...

---------- Post added at 10:16 ---------- Previous post was at 10:14 ----------

Exactly what I will do now.
[Galaxy S 4 i9505 Original Android Development] side:
Well... If that "it's how Deco said" was the issue, remove that sentence. I may misunderstood what Deco said.... The rest I said is my opinion
[Galaxy S 4 i9505 Original Android Development] mismamente:
When I configured adopted Storage (Stable1), and then upgraded to Stable2, my files disappeared. Also, the SDCard identifier changed.

So I'm not going to use again adopted storage, I want to be able to update from Stable n to Stable n+1

That's my experience with adopted storage and this ROM.
[Galaxy S 4 i9505 Original Android Development] -Deco-:
https://wiki.archlinux.org/index.php/GUID_Partition_Table

/system *is* a partition. Internal storage is it's own partition. The system itself is essentially a derivative of MRT (hence why I said the boot sector at first).

If you choose Internal, things change. The device is formatted as a local, 128-bit AES encrypted EXT4 drive and mounted as part of the system. (It's mounted with the /system partition).

http://m.androidcentral.com/inside-marshmallow-adoptable-storage

What do you mean "so dumb"? It would make more logical sense to elevate the keys to the /system partition which is/cannot be mounted on a non-rooted device instead of storing both keys on a mountable partition. (The internal storage).
[Galaxy S 4 i9505 Original Android Development] okidokiss:
See how easy is too turn on/off VPN.

https://youtu.be/d8P6JCk3vPU

[MENTION=5968293]side[/MENTION] maybe you can fix L2TP next build.

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] :
Hi,

I just dirty flashed s3 over s2.

on the first boot while the apps going to be optimized, there is a missing "d" letter on the german translation.

it says: "wir" engl: we

might be: "wird"

br & happy coding :D
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Well, there definitely seems to be an issue w/ adopted storage in this ROM.

I just installed "stable 2" (as I wanted to upgrade to "stable 3" to see whether I can still access my "adopted storage"), and the ROM couldn't "adopt" the card. All I got was the error msg depicted here. I used an unpartitioned SD card for this.

Then I tried again, this time the SD card was formatted to VFAT from TWRP. At first it seemed that the procedure would be successful this time, the partition was formatted/encrypted, but when I wanted to move my existing files to the adopted storage, I got another msg.

Before you ask: This was a "Can't-be-cleaner-than-this(TM)" install. Everything was formatted (apart from TWRP).

I guess this "adopted storage" feature has simply not been tested much, if at all, as people are always recommending to format as "portable."

I can see that for most people "portable" will probably be the best choice, but for some "adopted" might be better.

My view is also that if you have a feature built into the ROM, it should work. If you do not want to support it -- which is totally the decision of the maintainer -- then it should be removed.
[Galaxy S 4 i9505 Original Android Development] abdelkader azhar:
Side

You are amazing

All my respect to you
[Galaxy S 4 i9505 Original Android Development] rolandvrielink:
About my camera problems I had posted here before, they asked me I should post a logcat. I have syslog on my phone and can select several logcats but which one do I have to select?
[Galaxy S 4 i9505 Original Android Development] mbaeri:
Viper won't install its driver . I've installed and bootet new 3 times...

What can I do?

greetings Swen
[Galaxy S 4 i9505 Original Android Development] cybersaif:
[MENTION=5968293]side[/MENTION]

Official V4A 2.5.0.5 is up with a revamped UI, download link: http://www.audlabs.com/dists/ViPERFX_v2.5.0.5.apk

I would recommend you to flash A.R.I.S.E. Sound Systems- Numbers 3.3 everything is pre-installed. Download, flash and forget :good:
[Galaxy S 4 i9505 Original Android Development] -Deco-:
It's a necessary function which is required for the majority of apps, be it working or not. If it was removed then users who simply flash the updated version would simply say that "So and so has crashed, the SD card needs to be formatted as Adoptable Storage, what can i do?". It's better for the simplicity of things to have it built in.
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Yes, of course. I never doubted that.

What's MRT? You mean MBR?

I don't get what your point is. Yes, adopted storage uses the new, modern GPT partitioning scheme, while traditional storage uses the MBR scheme. But so what?!

To make it clear: The part typeset in "bold" characters was added by you, it is not part of the source you quoted. And actually you misunderstood what the article you quoted says.

When they say "mounted as part of the system" they are not saying that the adopted storage somehow becomes part of /system, which could indeed mean it's lost when you reinstall the OS (as this often formats /system).

The article is of questionable quality anyway. They don't add any info to what Google write here, and they even state wrong facts.

Quote from the article:

Now here's how it looks like on my system (Optimized "stable 2", I finally succeeded in formatting my SD as "adopted" when I retried a couple of times):

/dev/block/dm-0 on /mnt/expand/db01b6a8-af6a-4836-978c-90a0289d49ad type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,acl,inline_data,extent_cache,active_logs=6)

As you can clearly see, the FS type is "f2f2."

Now you're completely confused. Of course /system is always mounted even on a non-rooted device, because it contains the OS, but it's mounted read-only.

The point is: The encryption key is stored on the original internal storage (and only there!), which is not easily accessible, as you cannot remove it as you can remove an SD card.

I don't know why you talk about "both keys." There is only a single encryption key for adopted storage, and it resides within the original internal storage.

With "so dumb" I was referring to Google, who for sure do not design a system that ties users to a certain given ROM build.

---------- Post added at 21:32 ---------- Previous post was at 21:26 ----------

Adopted storage? Uhm, no.
[Galaxy S 4 i9505 Original Android Development] -Deco-:
Whoops, that was a typo on my behalf, yes i was emphasising MBR. By "/system not being able to be mounted", i was meaning for a user to not have any write permissions.

The platform randomly generates an encryption key for each adopted device, and that key is stored on the internal storage of the Android device. This effectively makes the adopted media as secure as internal storage. Keys are associated with adopted devices based on the adopted partition GUID. The adopted device is encrypted using?*dm-crypt?*configured with the?*aes-cbc-essiv:sha256?*algorithm and a 128-bit key size.

Encryption uses "2" forms of keys in order to be successful. You can't have one and not the other otherwise it's useless. One for the "request" and one to "validate" that the "request" key is correct.

You misinterpret me at most points. I was stating that the SD card is mounted with the /system partition, not that they somehow magically fuse together. Google themselves do not care for users who root their devices, they are already aware that the user (us) chose to do this and they so presume that we can fend for ourselves. Recent examples of this are from Android Pay. Google tend to have a disdain for rooted users in general, and would plug the hole if they weren't held bound by the GNU.

Again, you misinterpret me. General users who do not check the changelog and will just happily flash the ROM and move on. I was using the "vast majority" to highlight that general users will not notice that the feature is missing, so it's better (in general) to have it implemented.

I'll cut this off here. Recent statements have said that you cannot dirty flash an updated ROM and expect Adoptable Storage to be working; i said this from the beginning.
[Galaxy S 4 i9505 Original Android Development] tonyaross:
I'm not sure whether this is rom related, but does anybody have "screen overlay" issue that gets in the way of changing permissions?

After I (clean) installed Stable 3, this has become a real problem. Basically, everything goes fine until suddenly, the "Screen overlay detected" message comes on WHEN I TRY TO CHANGE THE PERMISSION of an app. It asks me to go to the setting and turn it off. But when I follow the link go there, many apps have this option greyed out so that I can't turn it on or off. Without being able to change the overlay setting, I can't change the permissions for my apps. I have tried several clean installs and even going back to Stable 2, still the same, although I never had this problem with Stable 2 prior to Stable 3.

The real weird part is that this message comes up after a while. It looks like some app or process triggers it and yet I can't find what it is. Anybody else?
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
If we discuss such extremely technical topics, we should be precise.

You quoted the following from Google's article without making clear it's a quote. That's very bad practice.

Now where does that come from?! You are using terms which are not commonly used in cryptography.

We are talking about symmetric encryption here (AES). It uses a single key to encrypt and decrypt data (which is why it's called "symmetric.")

You are making a lot of fuzzy or even wrong statements, which might be the reason why I "misinterpret you."

I do not get what you're trying to get across with the above.

But "general users" might use a (partially?) broken feature that has not been removed and then come here with their problems.

Dirty flashing is the only way to keep your adoptable storage. If you do a "clean flash" you destroy your adopted storage encryption key, and all data on that partition is lost.

I just upgraded from "Stable 2" to "Stable 3", and my adopted storage is still present and working. I'm not saying everything is stable, because I simply cannot make a statement about that yet.
[Galaxy S 4 i9505 Original Android Development] inestion:
I'm experiecing the same problem. Anyone found a solution? Happened on both stable 2 and 3, I've already updated my baseband.
[Galaxy S 4 i9505 Original Android Development] roke92:
Me too updated baseband and bootloader but nothing , wifi keeps dropping and being very weak not far away from router. i' m getting mad. Help me please!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] -Deco-:
I am not writing an article... this is a forum.

Symmetric encryption follow the same rules. It uses 1 key sure, but it is still counted as 2 separate keys as they both serve a different function.

Telling me what is "bad practice" is... amusing to say the least. I apologise due to my informal response... but i am bound to the limitations of Android.

Anyways, i hope we can put this "issue" to rest already, so I'll leave this as the last response.
[Galaxy S 4 i9505 Original Android Development] okidokiss:
External SD card problem

Hi all

From nothing I've received a message reporting that my sd card is damaged.

Rebooted, same problem. The message says I've to format SD card to recover.

Tried at PC and everything seems OK, so I made a backup a formated.

Same message on the phone.

The weird thing is that I format the SD card in the phone and right after that the message about damaged SD card is there again, it's a loop.

Tried a new SD card, same thing.

Is this a ROM issue? or What??

https://www.youtube.com/watch?v=_TFr1ZjdExg

Made a small video with the issue, but text is in Portuguese.

Some help?
[Galaxy S 4 i9505 Original Android Development] sjamie:
Just swipe away the corruption notification.
[Galaxy S 4 i9505 Original Android Development] okidokiss:
I did that, but no sd card available.

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] WnG88:
Twrp has burned 2 of my sdcards where they are stuck in read only mode. Check to see if you can write to the card.
[Galaxy S 4 i9505 Original Android Development] okidokiss:
I can. In computer works fine. Tried 3 different cards.

There's no error when formatting in the phone, just the message returns.

Must be something with the ROM. I can format, repair and copy files to card while in TWRP. After booting ROM, there's the error.