yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units General] typos1:
Not "*****ing" but valid criticism, things are more difficult and more complex than they were before, theres far too many threads and forums to keep track of everything, as I said, things have gone from one extreme to the other and theres seems to be a total lack of moderation - theres a thread for Joying units when Joying simply re-sell Joyous units, you think a moderator would allow an "Amazon Glaxy S6" thread in the smartphones section ? It would be merged or closed cos of dupilcation. I wanna keep abreast of all the latest develoment and now I have to spend a HELL of a lot more time checking multiple threads to do that, whereas before I had just one thread to read. I ve been participating in the the original thread for the last 2 years I ve often called for a proper forum for these units, but as I said in my post, we ve gone from one extreme to the other and things are worse than they were previously, I d never have called for our own forum if I knew things would be like this.
[MTCB Android Head Units General] halloj:
I agree.
[MTCB Android Head Units General] dgcruzing:
I think you are missing the point...

Granted you have been in that same thread for two years..and you have got a handle on it..

But what about the thousands of users that are going to be looking for the same answers that are getting mapped out in their own q@a threads.

Let's revisit this again in a few months and see how we are going..

All good ...
[MTCB Android Head Units General] typos1:
No, you have TOTALLY missed my point - its partly them I m thinking about, theres stuff theyre never gonna know cos they dont realise that their JY unit is effectively the same as a KGL unit so they wont check the KGL thread cos as far as theyre aware they dont have one of those. The MASSIVE thread that was running for 2 years proves that hardly anyone bothers to read the first posts/sticky, so its highly unlikely they ll ever realise . . . and yet, they might well decide theyd prefer the KGL ROM, or the KLD built in apps, for instance, but they may never know about it or that they can use it.

We need multiple threads relating to different branded/manufacturer's units merged, because they are effectively the same product. Similarly, software mods apply to all versions, so threads for instance, about apps or a ROM for JY units (probably started by well meaning, but less knowledgeable posters) should be merged or re-titled because the software can be run on ANY MTCB headunit type with matching processor/screen res (with the exception of some screen mirroring apps for the RK3188 which wont run on RK3066 versions). But separate hardware mod threads like for example, how to do the mic mod to JY version - which is slightly different to the mic mod for a KGL version, which in turn is slightly different to the one for KLD version - left alone as this is done to the slight hardware differences between the different units.

Whats needed is a half way house between one massive thread and multiple forums and threads weve suddenly got now.

BTW, you DONT have a "CarJoying" unit, CarJoying are simply re-sellers of units made by Shenzhen Joyous, your unit is no more a "CarJoying" unit than a Galaxy S6 bought from Amazon is an "Amazon" Galaxy S6 - you have a Joyous unit, or a JY. I think this kinda proves my point.

Soon, there ll be "CarJoying" threads and JY threads for units that are identical ! - MADNESS. Needs to be sorted.
[MTCB Android Head Units General] dsa8310:
My opinion on forum & threads

--
[MTCB Android Head Units General] Brendo:
Not to knock all the effort that has gone into splitting off the massive thread, I agree with the sentiments posted here

Dedicated forum was good in theory...

Perhaps I'm just old and used to how it was
[MTCB Android Head Units General] dark alex:
Okay let me sort out some things:

We were fighting for our own section a logn time on the main thread. Now we goot it you don't want them anymore...

Wow...

Okay to come to your arguments:

I told [MENTION=335322]MikeChannon[/MENTION] it would be better to have a "device" but he decided to do it that way as it's fitting better here.

Of course we can reopen the main thread but it's better to have knowledge separated.

What do you guys think about this:

Re-Open the Main thread for general questions (e.g. searching for information).

Leave the rest as it is and especially leave the information (knowledge) at their own threads.

It is much easier to find things like Apps, Mods, ROMs etc in that strucutre as it was in this big thread. also it's easier to follow specific topics.

What I agree with you is that it's harder to keep track of the mass of new thread or of greater masses of topics.

You now don't have one thread bloated with masses of information but four sections with "masses" of threads.

I am sure [MENTION=335322]MikeChannon[/MENTION] will have a look into this thread and I hope he will think about changing our section to a device section again.

It really is a bit irritating to have our forums directly next to the other Android Auto sections.

I suggested to do things that way: XDA -> Android Auto -> MTCB -> Sections here but Mike told me there is a problem with some mobile apps when having forums deeper than two levels.

//Edit:

I also received a PN suggesting to reduce the number of forums.

Let's discuss that here please.

What would you want? Just split up into Knowledge and Q&A? Or even just one big forum with everything in it? But I think that yould be too mixed up then. I would suggest - if we decide to request to change the structure again that we leave at least Q&A and Knowledge sepearated.

When it comes to the issue that people split up between pumpkin, klyde etc I can ask Mike to change the info box above the forums.

Please also note that some of those mentioned threads are from the past? I moved them here from android auto section as it's of course also MTCB.
[MTCB Android Head Units General] dgcruzing:
Honestly I don't know what the fuss is about..apart from a individual not wanting problems he has brought in the main thread started as a thread.. If that's the case then 'can' those threads and let nature take its course..

as am example..and laid out pretty much as a dummies guide to how XDA has always been once a piece of equipment warrents its own sub-forums.. And note.. It not just a joy thing..any of these sub forums can morf in the " best of'.. Ie.. If a super manufacture comes along and blows everyone out of the water then..there will be roms, software and q@a going for them under these very sub forums..

K.. So lets use some examples..

The sub forums as they stand..

Right let's go and have a look at the Samsung S5 forums..as they stand..

K...to keep this debate fair..let's throw in a few more that I personally follow.. Via mostly the tapatalk app..

So with the understanding that as Mike has pointed out..going deeper then 2 layers causes problems for mobile.. We can see a very clear pattern that is emerging..

So lets revisit how it is now and take in to account..with a little more modding (and don't get me started on that unless you want to put your hand up to be a mod.. I haven't as I have another life outside XDA forums.. But with that in mind..I take my hat off to mods who give thier free time to keep such threads under control..a thankless task..)

Anyway..back on track..back to where we stand..

So tell me after viewing my post what is so vastly different then any other device that gets a huge following..zip..zilch..

We now have a well laid out plan of sub forums in which an organic growth of inputs can be directed..instead of a unwieldy huge thread that contains posts of hardware mods..software and roms..

As stated..let it ride for a few more months to sort its self out..

Wipe the threads that people want wiped as for sure the same question is going to pop up and it will be answered.
[MTCB Android Head Units General] dark alex:
First of all thanks for your thoughts and statement on this, Mike.

I comply with this 100%.

What do you guys think about that: Keep the old ultrabig thread closed but create a new one in Q&A for people feeling lost.

Its meant for people searching for directions and for simple minimalistic questions.

A second thread could be for choosing the right unit and questions a la "Is this a MTCB unit".

Both could be pinned for easy access and good presence.

What is the exact reasons why you would like to have the old thread reopened? Can't we achieve this on another way?
[MTCB Android Head Units General] MikeChannon:
Done.

Mike
[MTCB Android Head Units General] Brendo:
In hindsight...

I feel the original thread could have been left open and used for genreal stuff (sticky). If user's want their own thread (split off from main), that could be arranged otherwise left as it was. Can reference back if required

MTCB

- General

-- main thread

- Software

- Hardware

No individual device maker/maunfaturer/type (probably not something that can be controlled)

End of the day, search and wiki had pretty much everything covered. But these days noone reads/searches anyway. The total page number would be intimiating
[MTCB Android Head Units General] dark alex:
Now this is the reason why splitting it at all. If even posters can not find information easily how should new users do?

Unfortunately (as I wrote to you in PM) this is not possible. vBulletin alsways orders posts chronological.

So as you say those threads are missing the story before your posts? Could you then lead me to the correct originating posts to be moved to those threads though. I just took pakidermo's links as a reference.

Is it just that you do not want to be OP? If yes I am sure we could change this but that would just mean you will lose the connection beetween post and name.

I guess you are saying I missed an originating post while moving? This Is what I meant in PN and my statement post. If I miss something tell me I will correct things.

And my two cents to the statement of [MENTION=2471548]mike.s[/MENTION]:

That is not entirely true. We were "fighting" for our own subforum or even device for (at this time) HuiFei-Type Units. Then XDA created Android Auto but that did not change things and that was complained in the thread, too. The thread kept on growing. Then voices became silent on this - in my opinion it looked like hope was lost (along with searchability).

//Edit:

Mike informed me that he moved dsa's posts back into the main thread upon his request.

My Request to you still consists. I would like to solve that on a behalf that makes everybody happy.
[MTCB Android Head Units General] mike.s:
If someone can't search a single thread, what makes you think they will be able to search across multiple sub-forums with multiple threads? It makes no sense.

Oh, and finding one's own posts is very easy - here are yours. If someone can't even figure that out, the problem is not a big thread, but the user being unwilling to learn how to use XDA.

Precisely, people weren't complaining, then you went off and did it alone because you thought a big thread was a problem. It takes time for people to adjust to a change - it seemed that many people had a bookmark to the big thread, and didn't even realize for a while that it was moved to a new category. It took a some time simply for people to get used to posting new threads instead of adding to the old. Now, it's been changed again, with multiple boards for a mysterious "MTCB" unit - a name NO ONE has ever called them. Now, instead of new users having to search one big thread or a single forum, they have to search at least 4 sub-forums, and multiple threads. So now to do an effective search, instead of typing in the "Search this thread" or "Search this forum" box and pressing enter, a user has to figure out how to find and select multiple forums in the advanced search options. How does that make things easier to find?
[MTCB Android Head Units General] dark alex:
Normally onw should know what he or she is searching for.

And as you know 90% of people who do not know what they are looking for take no efford to search but just post how do I.... or what is...

The MTCB was a suggestion from my side as HuiFei is not correct anymore. How should we have called it instead in your opinion?

You can still search whole Android Auto category but our subforums have one big advantage:

you can filter out the other devices if you know how to use the search.

I know finding own posts is easy. I never said anything else.

But does a new person know, who had posted about what topic? I am in doubt...

Did you ever compare seqarching for threads against searhcing for posts?

It's much easier to identify a Thread by its title than a post by its content.

No word on following a discussion...

If you take a topic in the main thread that took lets say 10 pages then wou will see that there have been about 10-15 posts (10-15%) for this topic and a lot of (in the eyes of the one searching) clutter.

Of yourse both ways have advantages and disadvantages. But as Mike already said this is the way XDA normally works and I will state this one last time:

http://xdaforums.com/showthread.php?p=63553394&highlight=android+auto#post63553394

http://xdaforums.com/android-auto/android-head-units/poll-android-head-units-subdivision-t3217036

And this is just what I found within 5 minutes of qiuck searching (btw: I knew exactly what to search for...). But no... no one complained...

I left out the discussion between goosy an typos as thats a discussion like this. Some find it good some don't.

But it's a fact that we have a thread over 20.000 posts and it's hard to keep track of it.

I tried to find the post where someone first noticed that we are now moved to android auto.

I could not find it... can you? ANd I know how to use vB-Search and I know what I am looking for.

Imagine I am a newer user and don't know exactly what to search for...

//Edit: Ah and I have another note: I know the sections in my link were meant to be more generic but thats not practically manageable becaus when mixing up different software and hardware we will cause mor problems than we solve. You know what happens when flashing KLD MCU on a KGL. Imaging flashing that on a AN-21U
[MTCB Android Head Units General] Neo:
Precisely. So why not adapt to the change? As Mike pointed out, the split was inevitable. As a device becomes more popular, you have to split into separate topics/sections. For those of you who were used to a single thread where all your hopes and dreams can be found via search, you will need to adapt to the structured change. That's part of XDA. It's constantly growing and evolving. 1 thread for an anything/everything can get messy (and has gotten messy) so the change was the right move.

So let's get used to it, and continue to enjoy XDA for what it is, and not what it was.

All the best,

Neo

Senior Moderator
[MTCB Android Head Units General] robertut:
Can you please move this topic: http://xdaforums.com/android-auto/android-head-units/adding-dab-functionality-t3208344 to the mtcb-hardware-development section?

Thanks...
[MTCB Android Head Units General] dark alex:
Did it.

Btw: there is a stickied thread in general for moderation requests.
[Galaxy Note 4 Q&A, Help & Troubleshooting] vercetti:
Hey everybody,

besides the different image processing taking place in every camera app which in turn leads to different results in images, are AOSP custom roms capabale of taking complete advantage of the note 4 hardware (utilizing all its features like focus, shutter speeds,...)?

The answer would be comparing a pic taken with a 3rd party camera app on a stock rom vs the same pic being shot with the same 3rd party app on an AOSP rom.

3rd party camera apps on stock roms profit from all the original samsung drivers which are not present in custom roms.

Has anybody done a comparison on this? I'd be greatful for links in that case. Your personal thoughts/experiences are welcomed just the same!

Anything to help me figure out if i should get a note 4 so i can flash custom roms and have great (stock like) image results coming from a AOSP rom with specific camera apps. Or if you think that only the stock touchwiz camera app can profit from certain features (again, I'm not talking about saturation, sharpening, etc. which is done via software and can be edited in a way you/i like. I'm speaking of the actual integration of all the hardware capabilities, drivers, API,...).

Thx for your help,

greetz,

vercetti.
[YU Yureka Android Development] Shivam Kumar Jha:
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on CyanogenMod so use custom kernels compatible with them!

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/

All the source code for crDroid is available in the Github repo. And if you would like to contribute feel free to pull a request.

Rom features

* Volume panel timeout

* Slim recents panel

* Clear recents button location

* Lock app on recents panel

* SlimRoms Heads up (with snooze time, timeout, touch to hide and swipe behavior)

* SlimRoms custom lockscreen shortcuts

* SlimDim (dim navbar icons)

* Ticker notifications

* Navbar on/off

* Hardware keys on/off (in devices supported)

* Power menu in navring targets

* SlimPie controls with all working

* Sound panel option on power menu

* Superuser indicator on/off

* Force expanded notifications on expanded statusbar

* Power menu and notifications tiles

* Four tiles per row

* Vibrate on tiles touch

* Disable quick settings on secure lockscreen

* CAF task manager

* Kill app back button configurable timeout

* Ambient display with a bunch of options

* ADBlocker

* System apps remover

* IME advanced settings

* SELinux switch

* Network traffic meter

* RAM bar in recents panel

* Wakelock blocker

* Battery saver enhancements

* Non intrusive incoming call

* Option to disable battery saver orange bars

PS: All CyanogenMod features are also inside

First time installing crDroid to your yureka, or coming from another ROM:

- Make sure you're running a proper working Recovery (CWM or TWRP)

- Copy GApps and crDroid zip to your internal SDCard

- Boot into Recovery

- Flash crDroid zip

- Flash GApps zip

- Flash SuperSU (not mandatory. We have CyanogenMod su access inside)

- DO A DATA WIPE / FACTORY RESET

- Reboot

- Don't restore Apps using Titanium Backup!

Upgrading from earlier version of crDroid:

- Copy crDroid ZIP to your internal SDCard

- Boot into Recovery

- Flash crDroid zip

- Reboot

Special thanks:

- Google

- CyanogenMod

- crDroid Contributors

- SlimRoms

- AOSPA (Paranoid Android)

- OmniRom

- NamelessROM

- Many others... (if you're feeling upset being out of the thanks list just send a PM )

XDA:DevDB Information

crDroid Lollipop 5.1.1, ROM for the YU Yureka

Contributors

Shivam Kumar Jha, Shivam Kumar Jha

Source Code: https://github.com/crdroidandroid

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Unlocked bootloader & Custom Recovery CWM / TWRP.

Based On: crDroid

Version Information

Status: Snapshot

Created 2015-11-12

Last Updated 2015-11-20
[YU Yureka Android Development] Shivam Kumar Jha:
Download Link:

crdroid-5.1.1-20151119-tomato.zip

What works?

Camera

Wifi

Mobile Network

Bluetooth

and so on... everything ...

Whats not working?

None observed in my light usage.

You tell me..

Screenshots:

View attachment 3539931 View attachment 3539932 View attachment 3539933

Note: I know its MM age now, you can expect it soon.
[Galaxy View Q&A, Help & Troubleshooting] abdimo:
Could any one help how i unlock sim network of my Galaxy S5 G900T freely
[8525, TyTN, MDA Vario II, JasJam ROM Development] alylea:
Does anybody know if prolonged use of Superbright will do any damage to or shorten the life of the screen. Also, anyone know how detremental using it is to battery run-time?
[8525, TyTN, MDA Vario II, JasJam ROM Development] jompao:
Wrong forum.
[8525, TyTN, MDA Vario II, JasJam ROM Development] alylea:
Sorry. Figured it would be OK here since it came in VP3G's ROM. Where should I repost it to?
[Nexus 5X Q&A, Help & Troubleshooting] IVBela:
I plan to unlock my bootloader, but not rooting the phone yet, want to see if I can live without root. But in case I find out I couldn't I don't want to wipe my device again, thus unlocking now before actually moving all my stuff over from my old Nexus.

My question is, does it have any drawback to unlock bootloader? Does it actually affect anything (besides the hyper-annoying nag screen on boot), that would make it better just to leave it locked, and do the wipe and everything only if I ever decide to actually root it? Tough decision, I'd love to hear your opinions.

Thank you!
[Nexus 5X Q&A, Help & Troubleshooting] PhoenixTank:
Assuming you aren't flashing TWRP, right?

Drawbacks... Security, maybe? Can't really think of anything else. OTAs will still work, as will all the usual upsides.

Upside, you can flash the latest factory images as soon as they are released.
[Nexus 5X Q&A, Help & Troubleshooting] IVBela:
Yes, no flashing nothing, just a plain fastboot oem unlock, then pretending to be a basic user with a locked phone. :) I wonder if from the OS side anything can be perceived by apps, security/integrity checks, etc.
[Nexus 5X Q&A, Help & Troubleshooting] PhoenixTank:
Yeah, then nothing in android will know, apart from the checkbox you need to enable in developer options.

Only when you change the boot or system images, does it really flag up anything. Hope that helps.
[Nexus 5X Q&A, Help & Troubleshooting] IVBela:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
[Nexus 5X Q&A, Help & Troubleshooting] woodydog:
It stays checked. I haven't tried to unchecked it yet
[Nexus 5X Q&A, Help & Troubleshooting] sordup:
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
[Nexus 5X Q&A, Help & Troubleshooting] IVBela:
This. So far this is the only drawback I found.
[Nexus 5X Q&A, Help & Troubleshooting] gleggie:
Not really sure what device protection does, as Android Device Manager still works.

Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
[Nexus 5X Q&A, Help & Troubleshooting] Witek_M:
It may work with casual thug. Sophisticated thief will turn device off, reboot into bootloader, wipe device and take possession. Device protection is meant to discourage theft.

https://support.google.com/nexus/answer/6172890?hl=en
[Nexus 5X Q&A, Help & Troubleshooting] Jemmy Ducks:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
[Nexus 5X Q&A, Help & Troubleshooting] Witek_M:
There are three sets of drivers needed. One for fastboot, one for adb and one for MTP. When device is in fastboot mode you use command "fastboot devices" or Mac equivalent.;)