yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] BigMacca:
Hi all,

Does anyone else have the following when streaming Bluetooth to their car...?

Instead of getting the title of the file playing and the time counter, I'm just getting the text "BT Streaming"

This happens with both of my regular audio apps (pocket casts and power amp).

This also only started happening when I switched to carbon a couple of weeks ago and everything worked as expected on my previous setups.

Is this related to the Bluetooth drivers or is there a setting I'm missing somewhere?

Cheers

Macca

p.s. Love the rom, so smooth!
[ONE Android Development] darjwx:
The car where I tested Bluetooth streaming does not support showing the title name so I can't say much about it.

I can't test it nor see if it works on my end.

I will see what I can do when I could.
[ONE Android Development] Genericxx:
I have had this Problem on LineageOS based roms a few weeks ago but they fixed it. Flashed CarbonROM Yesterday evening, so cannot tell right now. Will give it a try while driving to the office later.
[ONE Android Development] HannibalLecter:
Has anybody tried to Clean flash the latest build? wiping everything including internal storage?
[ONE Android Development] darjwx:
Why would you want to wipe internal storage.
[ONE Android Development] HannibalLecter:
been some time since I did that. don't need many files. Anyway, why is a different thing.

The ROM should work this way as well.

You may 29th build worked well. This build is giving problems.
[ONE Android Development] darjwx:
What I don't get is why is giving problems only to you. I haven't received any other report. :)

And yes, the ROM will work if you wipe also storage. I just asked because that's not what normally I would do as it's not needed in general.
[ONE Android Development] darjwx:
Two guys of the team has reported that it's working fine for them.

So it could be your cars fault. Or it could be that something is missing specific to bacon. But the ROM itself supports it.

I will let you know if I find something.
[ONE Android Development] BigMacca:
Hi mate,

My car definitely supports it, everything was working as expected before I switched over to carbon (my car and the apps I'm using to stream have remained constant).

Thanks for looking into this for me.

Macca
[ONE Android Development] HannibalLecter:
See brother, you're the developer of the ROM and you're answering questions about bugs like some other user who is just a fanboy.

It is giving problems only to me because Till Now, only I have tested this particular use case.

How can you say the ROM works in this scenario, without Clean flashing (Wiping everything inc internal storage) yourself.

The issue is that the Internal Storage is Not accessible after the super clean flash. No file can be copied to the phone from mac nor from windows. More importantly, the internal folders that get created automatically (such as Downloads, Music, Pictures etc) Are NOT getting created.

Also settings menu is blank after the clean flash.

Your May 29th Build worked perfectly. So, the issue is with this Build only.

And to test I just clean flashed Idprophecy's ROM (same procedure-Wipe everything inc internal storage) and his ROM worked PERFECTLY.

Internal storage is accessible and folders got created automatically. Everything is FINE on his ROM.

I would request you to investigate the issue, if you want to. But there IS DEFINITELY some ISSUE with this Build.

I do not mean to disrespect you by this post.

I am simply reporting a bug and Requesting you to DO the Necessary steps to Recreate the USE case before denying the issue.
[ONE Android Development] darjwx:
I'm not acting like a fanboy at all lol.

I just said that you were the only one reporting that problem so that it was weird. I'm not by any means denying that that problem exists nor I'm saying I won't look into it when I have a chance.
[ONE Android Development] HannibalLecter:
Sorry for the little outbreak. :P

I was just a little frustrated because I love your ROM (as I reported my usage stats earlier) and I had been trying to flash and use the ROM for 12 hours now.

Gt busy in between hence, left it in the middle. was without all apps and even no whatsapp for more than 12 hours now.

Flashed this build over 10 times, trying to get it to work.

For now, I have to settle with that other ROM but I don't want to.

I want to use your ROM thus request you to look into the issue and resolve it when you find time.

Thanks a bunch :)

I am the only one reporting this, because it is highly likely that no one else has tried the super clean flash till now.
[ONE Android Development] Genericxx:
In have tested it, Metachange ist working properly with PowerAmp in my Car. Artist, Title and Album ist showed correctly.
[ONE Android Development] Setting.Out:
I assure you, just as with my previous testing, I do monitor and try to reproduce reported bugs.. I don't look forward to a 30+ gb backup, but it's probably about due.. I'll report later this afternoon as I will need to find the time to perform this wipe.. Off of a normal clean install I faced no issue, I'm not confident this extra step will change anything, but we'll see..
[ONE Android Development] HannibalLecter:
Hey, buddy thanks for joining in. :)

you know, this problem has come in the past too for some very few ROMs but it used to normally go away in the next build or maybe after trying some more times.

I remember facing this very same issue and I reported this to you for this ROM only.

ou suggested to install the previous build and then dirty flash the latest over it. That made the ROM work but it didn't really solve the problem that is bringing up this bug.

If you clean flash and maybe experience it for yourself, you might understand what's going on better than me. :)

as always, many mnay thanks for your help and support :) always grateful to you and the dev :)
[ONE Android Development] Myself5:
What you could do to help us is grabbing a logcat and a dmesg after the boot (Use adb logcat and adb shell dmesg).

That way we can look into it already until someone of the devs had time to cleanflash and try to reproduce.
[ONE Android Development] Setting.Out:
I can confirm an issue on the SD card, all logs from recovery couldn't be stored or were erased? (were gone when booted). Tried to take screenshots, but errored saying insufficient storage. Couldn't install any apps to take logs because of inability to write to storage. I also could only push files in recovery, the ROM blocked all storage writes.. (wasn't at my home computer for adb).. The Settings menu was intact (was reported broken).. I reverted a weekly prior, still SD issue persisted, flashing Lineage fixed it..

[MENTION=6168349]darjwx[/MENTION]

Clean flashing didn't cause the issue, but it appears the ROM has issue writing to an untouched storage..(wiping SD) I can try again tonight if you'd like being at my computer again..
[ONE Android Development] darjwx:
I will arrive home late. If you have free time go ahead, but I'm busy af (3 exams /4 to go) and can't do anything other than minor things.

Thanks as always for your time.
[ONE Android Development] HannibalLecter:
ok. yeah.This makes sense. The ROM has some issue writing to untouched storage (wiping internal storage makes it so). Settings menu is a weird case. When I opened it, it remained blank 3-4 times when I flashed. Once, it worked.

Lineage has No problems writing to untouched storage (after internal storage wipe).

Something is def there to loom at.
[ONE Android Development] Minions_Army:
Untouch storage means no OS installed ?

May be you wrong in step by step how to install a rom

I never have any problem since 1st build official

Clean or dirty flash

Latest build using twrp k1 3.1.1 Carbon + opengapps + magisk v13 + Arise sound

Oh btw u can send a logcat to dev if u found bug
[ONE Android Development] Setting.Out:
You didn't follow the scenario.. This isn't confusion over installation, rather a bug if you happen to wipe the SD partition, causing no formatting.. I'm gathering logs, but thanks for including the sentiment again..

[MENTION=6168349]darjwx[/MENTION]

Here's some logs... I labeled them.. I pulled logs from LOS, the 6-5 Carbon and the 6-13 Carbon.. Happy reading.. I'm going to unbreak my device now.. ;)
[ONE Android Development] harsha7sai:
I just downloaded latest build

I am coming from another rom

Should i wait for the next build or can i flash the build ?
[ONE Android Development] HannibalLecter:
flash it. You won't face any problems. Just don't wipe the internal storage (which you wouldn't do either ways unless you were an OCD like me who likes it super clean :P )

---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------

at least read before replying. and if you did, take classes on how to understand the issue.
[ONE Android Development] harsha7sai:
[MENTION=6168349]darjwx[/MENTION]

This is the fastest nougat rom i have used

Thanks for the rom

But please add this features

1. Give us option to edit single press menu button action ,i use it for recents

2.add privacy guard

3.don't include modem in the rom zip
[ONE Android Development] darjwx:
1. As I said thousands of times. It's coming. Idk when but someone on the team will handle it. I can do nothing now. :)

2. Already requested. It will have to be discussed with the team, but for now probably not.

3. I included it to avoid problems that people has using different modems. This one works just fine. Do you have any problem with it? If there's a problem I have not found, of there is a modem much better than this one, let me know please.

Thanks for the feedback.
[ONE Android Development] harsha7sai:
I use c6 modem which works best for me

This is just a suggestion

In the op you add the modem link as recommended

People can decide what to flash
[ONE Android Development] darjwx:
Yeah, I get your point. I like to let users to flash what they prefer. But some modems have problems with this ROM, and the one included is tested and already reported that works fine. You can still flash the one you like anyway.

But I will think about this.

Thanks.
[ONE Android Development] Beep-Bop:
Hide this notifacation? and

http://frap129.org,

I want to try his maple, could you bring it here?
[ONE Android Development] eiwarmer:
1. There's an app for that I always install it when a rom doesn't support single press actions:

https://play.google.com/store/apps/details?id=com.irishin.buttonsremapper

And "give us option" sounds a bit harsh don't you think?
[ONE Android Development] darjwx:
I don't mind trying to bring his scheduler and governor. When I had time I will share a test boot.img with it.

About hiding that, I will see what I can do. I also kind of dislike it
[ONE Android Development] Beep-Bop:
Second thought,

Forget about "maple", "row" is just enough for me.
[ONE Android Development] Beep-Bop:
Sorry to bug ya again..

I made a list! atleast this time

Can I get the ability to have bold fonts on lockscreen? (RR)

Shortcut customization, just so I can choose "none" (Lineage)

Sound option that makes changes in "media" a default selection (Lineage)

Ps: Undervolting would be nice too (idprophecy Lineage)

Been using sub theme, lock clean, to strip lockscreen, it's removing shortcuts but its "leave charge indicator" isn't working..

<3 (Me)

Edit: Fixed
[ONE Android Development] darjwx:
1. What do you mean. Bold fonts by default or the ability to choose bold fonts on the system or lockscreen? I guess the second one.

2. That will probably be added. No ETA though

3. I already passed it to the team. Not sure if we will add it.

4. I won't add undervolting on the default kernels as it's a feature meant to be on a custom one. Sorry.
[ONE Android Development] Beep-Bop:
I edited my previous post.

Hmm, well this one better not be a waste.

“Hey!.. default wallpaper is hedious

and, setting's app FC.. Open Gaaps”
[ONE Android Development] eiwarmer:
No force close here. Clean flash with gapps from [MENTION=5165039]Setting.Out[/MENTION]
[ONE Android Development] darjwx:
The official supported gapps are dynamic gapps by Beans. We can't assure support for every gapps package out there.

[MENTION=5165039]Setting.Out[/MENTION] slim revisted gapps also works fine.
[ONE Android Development] Beep-Bop:
Ah, I understand.

btw, I hate that guy.
[ONE Android Development] Setting.Out:
Lol, I'll pm you on telegraph..
[ONE Android Development] Beep-Bop:
Can I be in the testing group also, what it takes.. ?
[ONE Android Development] HannibalLecter:
this is my settings menu. BLANK.

How do I take a log cat without enabling adb debugging in developer options when my settings menu is blank?

Please let me know if there is a way.

This time, I first flashed LOS and then clean flashed the latest build without wiping internal storage.

Can copy stuff into the internal storage but settings menu is blank. [MENTION=5165039]Setting.Out[/MENTION]

Have not flashed any mods whatsoever. just pico opengapps.

Edit: Came up after 10-15 mins.
[ONE Android Development] darjwx:
It takes me inviting you :)

It's a closed group. I won't invite anyone. You have to know how to properly test stuff. And be experienced with the debug tools. I also have to trust you to avoid leaks.
[ONE Android Development] Beep-Bop:
I am bad at those things, ) :

I can make ice-creams, however

And, I need one now.
[ONE Android Development] Setting.Out:
I've tried to recreate your steps.. Never had settings issues, and also use the recommended gapps when possible..

Root the device (if not rooted) use syslog app from the playstore to grab a log.. :)

The next weekly is coming, don't wipe the SD still, the bug is found (possibly) but not fixed as of yet.. We'll let you know if/when it's resolved.. You can try an older build for now and update to the next build when it's online..
[ONE Android Development] HannibalLecter:
clean flashed the latest build. (Did not wipe internal storage this time) the Settings menu came up Blank again and is still blank after 10 mins.

I guess it will come up after 15 mins.

There is definitely something wrong with the latest builds. I'll try to grab a logcat.

but certainly, I cannot be the only one experiencing this.

Also, I do Not experience any of this on Any other ROM. Neither on any other of my 4 devices.

having a bad taste in the mouth with carbon.
[ONE Android Development] darjwx:
I'm going to university now, I will flash the build later today to see if I face the same.

About the internal storage issue, I may know which commit caused it by I am still investigating it. And I couldn't reproduce it on my personal builds so I guess it happens juts on user builds.
[ONE Android Development] Setting.Out:
Try an older build again, one that was working, see if the problem persists.. There's no reason for the settings to be blank on a clean flash.. You really need to grab logs, screenshots and dna if you want this solved..

# the case of the settings snatcher

:)
[ONE Android Development] eiwarmer:
I'm running the 13-06 build and all went smoothly without the settings issue. Clean flashed with your gapps and no data restoring via TB. I will get dirty later today and try the 20-06 build...
[ONE Android Development] darjwx:
New weeklies out

Not much on this weekly. Life is what it is :(. On my case at least I am half way done on my way to freedom. (2 exams of 4 left).

Bacon is now using sdclang.

The next weekly will be more interesting device side. I could merge the changes for this one, but I wanted to wait to be sure there were no problems.

Changelog

Device specific:

- Enable sdclang

- Disable NfcF HCE (nothing really important for the end user)

Rom side:

- Sdclang support

Misc:

- I am now maintaining the Google pixel c (dragon) so if you own that, go ahead to its thread.

Carbonrom web

As always, check gerrit or github for a whole in depth changelog.

If you are missing something themed on Carbon and you are contacting the themer, please let him know of this repo to make his work easier.

ThemeResources

(Do not hesitate to contact me if you see something wrong on that repo)

Dario
[ONE Android Development] eiwarmer:
Semi-dirty and clean flashed build 20170620 with 3.0.2 multiromTWRP -> Set up my device as new -> Used the Slim_gapps_revisited_7.1.2_06042017 gapps by [MENTION=5165039]Setting.Out[/MENTION] and couldn't replicate the force closing or blank settings menu. Both flashes went through without any hiccups.
[ONE Android Development] HannibalLecter:
hmm. I tried clean flashing only ROM (Without gapps without root) just the ROM and reboot. Still the settings menu was blank. Took 10-15 mins to come up.
[ONE Android Development] Setting.Out:
Still missing logs.. No other reports, can't be reproduced.. Don't know what to say, other than you've got a localized bug on your device.. :(
[ONE Android Development] HannibalLecter:
yea logs missing :( i'll need to clean flash again which is too much trouble again. plus I need ti find a way to capture logs immediately after boot (cannot wait untillogging in play store and then installing an app)

I dont think it is a device specific issue. It can't be. I've tried official LOS, idprophecy's and RR. no issues with them at all. Not one.
[ONE Android Development] darjwx:
[MENTION=7466743]HannibalLecter[/MENTION]

Here is the deal.

First I am not denying that your problem exist, do not think that.

Here is what I have done:

1. Clean flash (without wiping internal storage) the latest weekly. No problems with blank settings/force closes.

2. Clean flash wiping internal storage the latest weekly. No problems with blank settings/force closes.

But what is more important, I don't have problems accessing storage in any of the two installs methods I tested (With and without wiping internal storage). I can access it normally from the phone and from the PC. The default folders (pictures, notifications, music, DCIM.....) are created. To be sure I transferred a file from my PC to the phone, and no issues.

So idk, the only thing that comes to my mind is a hardware issue, but you say that lineage and others works just fine..... No clue on this, and I can not replicate it on any way.
[ONE Android Development] HannibalLecter:
I have no words. I have been facing this issue on Carbon but not on any of the other 3 ROMs I mentioned before.

Pretty strange. My steps: Wipe everything from advanced wipe and then flash ROM and reboot. (Flash nothing else) still issue is present :/

SInce, you wiped everything before putting everything back in, can you please try to super clean flash 13th june build and see if you face the internal storage issue cz Setting.Out did face that one on 13th JUne build.
[ONE Android Development] darjwx:
Sure, I will try that build after dinner.
[ONE Android Development] Setting.Out:
We have exciting lives.. :)

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

Ext4 or f2fs?
[ONE Android Development] HannibalLecter:
LOL that hurt :P

Ext4 I guess that's the default. Never changed that.

I have never bothered with f2fs. it was a fad from day 1.
[ONE Android Development] eiwarmer:
You aren't using multirom are you? Flashing as secondary sometimes causes strange bugs.
[ONE Android Development] darjwx:
[MENTION=7466743]HannibalLecter[/MENTION]

Clean flashed weekly 20170613. Wiped everything including internal storage and no issues.

Settings are not blank nor force closes or do anything weird.

Storage is accessible just fine.

Flashed with official twrp btw.
[ONE Android Development] HannibalLecter:
what can I say now. I am the unlucky one.

BTW thanks a lot for taking out time and doing this. Really appreciate.

Just one last ques: Did you flash the official uploaded build? or your personal as you mentioned before? If so, can you share that build. I will try one last time. and please let me know if there is a way to capture logs immediately after boot or better yet during boot and afterwards?
[ONE Android Development] darjwx:
I flashed the official build.

You can take logs of the booting with the terminal.

Doing simply: adb logcat
[ONE Android Development] HannibalLecter:
no brother. I have never used multiROM nor ever will. one working ROM is enough.
[ONE Android Development] se7enlyn:
No only you. I had the same issue too. Another issue for me is that it takes a few minutes before the files in ringtones and notification tones shows up.
[ONE Android Development] indhimaga:
Which kernel manager that support tweaking to make charging faster?
[ONE Android Development] darjwx:
If it takes a reasonable time, it's normal. The media scanner had to do its work and look for all the media stuff in your phone.
[ONE Android Development] darjwx:
You are good to go with probably either kernel adiutor or ex kernel manager.

Important:

There's no support on the stock kernel for that stuff and it's not recommended as it can harm the battery. I would recommend to leave the stock values untouched. But if you go ahead and install a custom kernel or you modify the stock charge values, do not expect support from us.

Hope you understand.
[ONE Android Development] HannibalLecter:
thank goodness someone else has my issue too. See, So its confirmed now. 2 users :P

I agree with the second statement that ringtones showing up can take time but why does it Not happen with any other ROM?

Why do their stuff works from the moment the ROM boots up?

Is the code in Carbon designed to take time to perform these actions?

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

thanks for reporting brother.
[ONE Android Development] adinkwok:
Quick question to those who are facing issues; are you clearing cache and dalvik/art cache when updating to new builds? Though it is not "needed", it is usually the culprit for bugs that not everyone can reproduce.
[ONE Android Development] Myself5:
There is no way to to grad logs by default on a user build, its disabled for security reasons. You need to boot first, then enable adb debugging in Settings.

Also for your Settings issue. Try rotating the phone once. There seems to be a configuration issue with the Settings Dashboard initial value. We're looking into that, but for now rotating the phone once should fix it already.

It's like that Lineage (which all those other ROMs you talked about are based on) changed the default media scanner behaviour on boot. Carbons settings for the mediascanner are still AOSP stock, hence they do what they do. We could however add a switch to edit the default media scanner behaviour.

Also you seemed to distrust [MENTION=6168349]darjwx[/MENTION]s decisions let me assure you he's qualified for that. Feature requests always will be discussed in the "stubborn" team, which is not a matter of minutes. We try to be as open to the community as possible, but sometimes there are already things in the works already but we can't talk about them yet as they are in and early alpha stage and might not happen or happen in a different way. This "saves" us from doing false promises ands dissapointing the community.

I hope thats understandable and that your questions are solved.

I'm certain we can fix those final issues, too.

Regards,

M5

Carbon Lead Developer
[ONE Android Development] se7enlyn:
Yes coming from a different rom

Wipe all except internal storage and usb

Flash rom+ gapps

Wipe dalvik+cache

Reboot