yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] nikko82:
The changes I did to sort the contact list was to edit the class used for storing the contacts inside the app (l.smali). I added sort functionality.

.class Lcom/tw/bt/l;
.super Ljava/lang/Object;

[B]# interfaces
.implements Ljava/lang/Comparable;

# annotations
.annotation system Ldalvik/annotation/Signature;
value = {
"Ljava/lang/Object;",
"Ljava/lang/Comparable",
"<",
"Lcom/tw/bt/l;",
">;"
}
.end annotation
[/B]
# instance fields
.field ah:Ljava/lang/String;

.field ai:Ljava/lang/String;

.field final synthetic m:Lcom/tw/bt/ATBluetoothActivity;

.field mName:Ljava/lang/String;

# direct methods
.method public constructor <init>(Lcom/tw/bt/ATBluetoothActivity;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V
.locals 0

iput-object p1, p0, Lcom/tw/bt/l;->m:Lcom/tw/bt/ATBluetoothActivity;

invoke-direct {p0}, Ljava/lang/Object;-><init>()V

iput-object p2, p0, Lcom/tw/bt/l;->ah:Ljava/lang/String;

iput-object p3, p0, Lcom/tw/bt/l;->mName:Ljava/lang/String;

iput-object p4, p0, Lcom/tw/bt/l;->ai:Ljava/lang/String;

return-void
.end method

[B]# virtual methods
.method public compareTo(Lcom/tw/bt/l;)I
.locals 2
.parameter "arg0"

.prologue
.line 20
iget-object v0, p0, Lcom/tw/bt/l;->mName:Ljava/lang/String;

iget-object v1, p1, Lcom/tw/bt/l;->mName:Ljava/lang/String;

invoke-virtual {v0, v1}, Ljava/lang/String;->compareToIgnoreCase(Ljava/lang/String;)I

move-result v0

return v0
.end method

.method public bridge synthetic compareTo(Ljava/lang/Object;)I
.locals 1
.parameter

.prologue
.line 1
check-cast p1, Lcom/tw/bt/l;

invoke-virtual {p0, p1}, Lcom/tw/bt/l;->compareTo(Lcom/tw/bt/l;)I

move-result v0

return v0
.end method
[/B]

I added the code in bold.

Then i called the sort function in the getter function in ATBluetoothActivity.smali

.method static synthetic o(Lcom/tw/bt/ATBluetoothActivity;)Ljava/util/ArrayList;
.locals 1

iget-object v0, p0, Lcom/tw/bt/ATBluetoothActivity;->W:Ljava/util/ArrayList;

[B]	invoke-static {v0}, Ljava/util/Collections;->sort(Ljava/util/List;)V
[/B]
return-object v0
.end method

.method static synthetic r(Lcom/tw/bt/ATBluetoothActivity;)Ljava/util/ArrayList;
.locals 1

iget-object v0, p0, Lcom/tw/bt/ATBluetoothActivity;->Y:Ljava/util/ArrayList;

[B]	invoke-static {v0}, Ljava/util/Collections;->sort(Ljava/util/List;)V
[/B]
return-object v0
.end method

One of the lists is for the phone-contacts and the other one for the sim-contacts.

I haven't found the functions that actually reads the file, but if you open the contacts-file you will see the names and numbers inside.

As mentioned before in this thread this (probably) has nothing to do with the contacts-funtionality in stock Android.
[Android Head-Units] tdt038:
Some issue is present. USB memory sticks with 64GB capacity is not working properly with firmware 2.6.62. I believe that the firmware 2.6.60 the most stable.
[Android Head-Units] scratch009:
Hi,

What about the Micro SD-card. I tried inserting a 64GB card but it doesn't seem to recognise it. Will a 32GB card work?
[Android Head-Units] :
32Gb will work, i have a samsung 32GB in my Unit.

The tech specs from the sellers also say SD card with max 32GB
[Android Head-Units] scubee:
thought i update you guys...

dont mess around with the model selection.

total brick. i think the wrong model selection was selected, somehow they dont recognise any buttons at all.

like how when you are in the upgrade mode. you can still fiddle around with the radio tuning... *mine is the 2 knob version. so the 2nd knob is for the FM radio tuning* so that still works in upgrade mode...

this time round nothing works. not the tuning knob nothing. reset button works. but its very one dimensional. it just... resets. i pressed and hold. 5 seconds. 10 seconds.. 1 minute. nothing.

press power button and reset same time. nothing..

BASICALLY. mess with model selection. or mcu think you're tethering on the line of irrecoverable damage.... like me.

so anyway ive no choice but to reorder another unit. sell agreed to do a refund when i send it back... but thats after the lunar new year.. which is another month away.

keeping my fingers crossed
[Android Head-Units] sciallo:
Wait, so you are able to use android/get to the settings menu? Just your buttons don't work?

Is it the model with the volume on the driver side (US driver - left)? Can you start MCU update from the settings->general?
[Android Head-Units] Mancubus99:
I'm experiencing the same problem on my unit. I'm running version 2.60. What version are you on? I also noticed that it's worse connected to my home Wi-Fi vs my cell phone. I just got and rooted my device so I haven't updated it yet but I'm going to try that as well as trying a different adapter to see if that works.
[Android Head-Units] sciallo:
[MENTION=5641403]scubee[/MENTION]

Well, I'll be gone all day, but if you can use android, first off in settings->about device what version MCU do you see?

Have you tried (again, if you can) change model to a different choice?

Can you begin the firmware update from the settings->general menu?

And if you can click on update mcu there, you can still extract the mcu file from /system/etc/mcu/ (need root) and unzip it to the root of your SD card, then update mcu from the settings...

I have tried all MCU I could possibly get my hands on this way without consequence (other than with some MCUs things like buttons would stop working as they were made for a different face unit) on all firmwares at least .60 and higher, and could always recover and go back to original firmware. If you are able to update MCU this way, a good safe choice (of the files in /system/etc/mcu/ would be the one that ends in -10-0101 (no sleep, no color change) if you want to try color change still the one that worked for my unit (volume on the left - Ouku like) was the ending in -10-2101 ...I tried a number of other ones where color change worked but buttons and knobs wouldn't...
[Android Head-Units] jakejm79:
Thanks Nikko, unfortunately the 2.3.7 BT apk is completely different and my understanding of smali is zero so I have no idea what I am doing, appreciate the help though.
[Android Head-Units] donaldta:
Btw, when the compatibility specs says Secure Digital High Capacity (SDHC) or up to 32GB cards then that usually means the unit does not have the ability to read Microsoft's patented and proprietary Extended File Allocation Table (exFAT) format. This is the defacto standard on the Secure Digital eXtended Capacity (SDXC) cards. It is more of a financial and licensing issue than a technical one, as Microsoft demands an intellectual property fee for every SDXC device created. Not everyone wants to pay that fee or end up in litigation with Microsoft because of it.

You can circumvent this restriction by re-partitioning the your SDXC cards as FAT32 and still have the ability to use it in SDHC slots. However, you will reduce the throughput that is attributed to using exFat file system.
[Android Head-Units] PsychoMcSatan:
I'm on 2.6.60. Is yours a model with two USB ports coming out of the back?

I received my OBDII adapter (the ebay one linked earlier) so I plugged it in to the other port. So far I've only gone on a couple short trips, but no drops so far. Both OBD and WIFI are working fine simultaneously (OBD in the one labelled "WIFI/3G" and WIFI dongle in the one labelled "USB").

In the meantime I received a response from my seller and I'm including the whole response because she includes a link to new(?) system files. I'm unable to check it out since I'm at work, but I've included it in case anyone is curious to see if there is anything new.

By the way, my unit is the OUKU-like one with volume on the right (US-passenger) side, though she seems to suggest that these files aren't even specifically for my model.

--------------------------------

Dear friend,

based on your description, it should be because of the WiFi dongle or the USB port on the cable. We suggest you to check another WiFi Dongle if you have.

As for the updates, we did have one, but we are not sure whether it is compatible with your bought model, because this file is for other android 4.1 models.

http://betopseller.com/img/dvd/newandroidupgrade.zip

(Just download it and decompress it to microSD card, then insert into the radio, it will be upgrade automatically)

Best Regards

Lisa

- our_sty1e

------------------------------
[Android Head-Units] cf2005:
USB-modem Huawei E171 work fine on my TH8683GN
[Android Head-Units] mmm1961:
Dear All,

I need your advice.

I have installed firmware 2.6.23 in order to fix gps problem.

Can i install firmware 2.6.62 without any unexpected bad consequences.
[Android Head-Units] tdt038:
I use a memory stick ("Transcend" 64 GB) formatted as FAT32, and it works fine with firmware 2.6.60 and does not work with firmware 2.6.62. I meant this issue.
[Android Head-Units] KID52:
Thank you, I will add it to the list.

Do you know what chips the modem uses?

Interesting to know, you would have thought an update would keep the previous functionality...

Does 32GB work in 2.6.62?

The update is 2.6.68, and the same link as posted a few pages back. It is also the same as the 2.6.68 firmware file in the main post.
[Android Head-Units] PsychoMcSatan:
Thanks for checking. I think I'll wait till the current wave of GPS-breaking and bricking calms down a bit, or there are confirmed and substantial upgrades to the system apps.

Actually I still haven't wrapped my head around where system specific files come from. It seems that it is in the MCU that hardware level differences like colour LEDS and physical buttons are defined. Does that mean that everything else in these packages is transferable from one model to the next (as long as they're what we refer to as AN-21 U).

If so, would a package like this add new MCUs? If so, do they get updated automatically or do you have to manually apply them?

Sorry if this has been addressed already. And wasn't there a Wiki setup somewhere? Just checked the first page of this thread and I didn't see it referenced.
[Android Head-Units] gghghgh:
sd support

For those who have rooted units try paragon NTFS &HFS app from google market to mount exfat and 64 gb cards has to be supported (in prevoius head unit 2.3 it worked, but it had fuse.ko module) I didn't root my unit yet, so not sure it works with our 4.1 units.

Who can make modules for our kernel it will make usb bluetooth work...so bt obd will be available:(insmod /system/lib/modules/bluetooth.ko

insmod /system/lib/modules/sco.ko

insmod /system/lib/modules/l2cap.ko

insmod /system/lib/modules/rfcomm.ko

insmod /system/lib/modules/btusb.ko)

And info from factory. Our units will be updated to android 4.3 approximately at the end of the April
[Android Head-Units] KID52:
Agreed, I think 2.6.68 seems to be a bit buggy, maybe the previously mentioned 2.6.70 will be better.

The software update doesn't change the MCU, but choosing a model does. It seems that the update includes specific unit files, such as the "Color" app, but then changing the model moves this app to a different folder depending on the model chosen, so out of the system/apps directory if "Color" is not needed. Which means the system image seems to be transferable between all units, as long as you have the right MCU installed.

To apply MCU updates you need to choose "Update MCU" from the settings menu, the MCU files should be extracted to the MicroSD card root just like a system update.

The Wiki link is in the FAQ on the main post.

I heard that too regarding 4.3, but wasn't given a date. I wonder if they will stick to that time scale... I was also told it should include a wireless mirror link function for your Android phone.
[Android Head-Units] ackyo:
Now that would be cool! my VW "version" of this unit is on its way from the ebay Pumpkin store, can i assume this would get the 4.3 update?
[Android Head-Units] donaldta:
I noticed that Roadmaster has MirrorLink listed for sale.

I've also noticed that they have a few other units with interesting part number differences.

The RM-6902 AN has a similar look than the MK4 from the Amobile page but with different specs.
[Android Head-Units] Mancubus99:
Ok, it seems that we're on the same version though my unit is the one with 2 knobs and I believe there is only one USB port on the back and another on the front. My volume control is also on the left. So far today Wi-Fi hasn't been a problem via tether with my phone.
[Android Head-Units] KID52:
I don't see why your unit wouldn't get the update, the hardware is the same, just a different face.

That is a lot of similar looking models...

So according to that, this thread actually relates to the AN-214U.

The mirror link box just appears to be a HDMI to composite converter, not even a special app or anything.
[Android Head-Units] patrickoneal:
Yeah, there's no mention of any USB or bluetooth interface for the touchscreen to work on a mirrored phone. Looks to be nothing more than an HDMI to composite converter, which would probably look even worse than apps running directly on the stereo. The other problem with anything that mirrors the display off of a phone to a display of any sort is the fact that the screen on the phone has to stay on. Even if you can charge the phone, most of them will end up discharging faster than they can charge when running apps, outputting video, and keeping the display on. To me, the point of this stereo is to eliminate those problems by running everything natively.
[Android Head-Units] donaldta:
Well, MirrorCast's foundation is built on RealVNC technology. So, I won't be surprise if the "com.realvnc.viewer.android.automotive" package was was included with the dongle. You can already get a similar experience by installing a VNC server on your phone and a VNC client on your head unit. Though it won't be tied down to just a few selective apps like MirrorCast, and might not run as optimized as the real thing.

Though, I do wonder if any of it would be necessary once your head units receive a version of Android past 4.2 which has Miracast compatibility baked into it. I know that Dr. Huihong Luo, whom is the developer of VMLite VNC Server, is working on Miracast VNC receiver for Android since he offered me to beta test it. Apparently, since it is using WiFi direct, it is supposed to be much faster than the current implementation. And it supports audio in addition to the video.
[Android Head-Units] cf2005:
Huawei E171 (MTS Russia)

Chipset : Qualcomm MSM6290
[Android Head-Units] KID52:
I think you mentioned you had a video of the issue with your unit after changing the model, do you have a link please?
[Android Head-Units] nadmail:
I just got this deck and while installing it, the WIFI dongle fell behind the dashboard and is nowhere to be found. :eek:

The girlfriend is pissed at me and needs internet on it. I have a TP-Link TL-WN722N dongle but it doesn't work on this (lack of drivers).

I tried USB tethering from another phone with no luck.

Any way to get the internet working on it ASAP?

Thanks
[Android Head-Units] KID52:
Have another look for the dongle in the car :) Has to be there somewhere...

Or just buy another with a compatible chip, I think it was mentioned before by [MENTION=5389783]donaldta[/MENTION] which chip the unit had the driver for.

Edit: Think it needs to be one with a Realtek 8192CU chip.
[Android Head-Units] donaldta:
Post #1052

Yep, at least from what was posted from [MENTION=5554780]bmj67[/MENTION]'s lsmod results in Post #113

Here is a list of possible hardware that the driver supports, "CONFIG_RTL8192CU: Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter".
[Android Head-Units] Samir Sogay:
I have a rooted Xperia Z. Can you suggest me how to add support for prolific pl2303 in it so that i can take terminal from terminal?
[Android Head-Units] sciallo:
WOW, New brick alert

Ok, really screwed it up now...

These units are not too hard to brick. Granted mine was already bricked (no MCU), I managed to further brick it, I'm assuming to the extent described by [MENTION=5641403]scubee[/MENTION] in this post although a completely different way.

I received an update from Ben at tonghai Create, so I went to try it out... I have the unit hooked up to a PSU, so with one hand I was holding "home", with the other, I connected power and immediately after connecting (stupid Idea) went to hold the volume knob/power I briefly saw the update process had started - too late, holding power I interrupded it. I think I'm left with absolutely nothing working on my board... Powering up shows a "hard sutdown routine" I've seen before... Screen weirdly shading to black, I haven't been able to restart the update process, (as far as I know, I'm trying a few different ways leaving enough time in case the update is happening without me being able to see it... Not holding my breath).

I think I really finished it. there doesn't seem to be a bootloader working anymore... Video coming later...

Moral of the story/lesson to be learned: When updating (not from the settings) either

Power the unit up with power supply/ignition key while holding "home"

OR

By turning unit off with power button and back on by holding "home" and power button

Not both.

On to find out if I can get a new board rather than shipping the whole thing back again...
[Android Head-Units] fcortes626:
i havent heard anything from Ben. The other lady Alison asked for videos too so i sent her one showing how i cant update mcu via settings. My ebay seller responded saying his technicians sent me a program to restore my unit but i dont see it anywhere in my inbox.
[Android Head-Units] donaldta:
I am not entirely sure what you're trying to do. But, if you want the unit to support a Prolific USB to Serial adapter directly then you'll need to compile the drivers for the headunit and then implement them in the startup scripts. Otherwise, you'll need to compile the drivers as a JNI library in your Android package so that your app can communicate with it through the Android USB APIs, like Torque Pro does with ODB2 adapters with FTDI or Prolific serial to USB adapters.

o_0

Thanks for sharing how it happened, as I am sure others will learn from your mishaps on what to avoid. Most likely you've cultivated a big enough fear of updating or changing the MCU that nobody will even look at its option it, let alone change it.

I think you deserve a nickname, like Sciallo "Destroyer of Headunits" or Sciallo "Android Bricklayer".

I hope they didn't mail it to you as opposed to email it. (or worse smoke signals?)
[Android Head-Units] fcortes626:
lol i hope not. the message says "mail box" not inbox. :confused:
[Android Head-Units] kschumake83:
So seeing as every time someone screws up their head unit the china sellers send over another updated system software, we need to keep bricking units until they send over the 4.3 that someone said will be here in april. I am really hoping that the miracast works well when it comes out so that I can just mirror my nexus 7 screen and have 4.4, or better yet skip 4.3 and just give us 4.4.
[Android Head-Units] sciallo:
Funny thing I will still change the MCU when I get it again without thinking twice about it... Yeah, I guess I'm getting to deserve that nickname ...not too flattering but I earned it, one OUKU and an AN-21 twice!! beat that record... I hope I helped others in the process if in no other way in "don't do what my damn ass keeps doing".

Seriously though, it shouldn't be all this easy to brake these units...

---------- Post added at 06:01 PM ---------- Previous post was at 05:59 PM ----------

NO PROBLEM!!!

Send me all your units, I'll have them bricked in no time!!
[Android Head-Units] donaldta:
The only caveat about that is that the Master Key Exploit which provides you guys with root access has been officially patched in Android 4.4 by Google (and by select manufactures in 4.3).
[Android Head-Units] kschumake83:
What do you think about OTA root keeper, I have had good experiences with that back when I used to use samsung devices. We may just need to root it in android 4.1 and use that to keep root through whatever update may come.
[Android Head-Units] donaldta:
You mean, "OTA RootKeeper -no 4.3 support? These root keeping/saving apps, like root saver in SuperSU Pro app, hides the su binary in another another part /system filesystem. I think for RootKeeper it is in /system/usr/we-need-root directory. It will work as long as the update is an incremental update and doesn't overwrite the directory. However, if the update overwrites the entire system filesystem (which is common in non Over The Air updates) then you need to re-root it. Unfortunately, if the means to gain root is patched then you're locked out of the device as a normal luser.
[Android Head-Units] smallie42:
gps

hi everyone. Im new here. I have a system at .68 and lost my gps. I read

that the fix was to downgrade to .23 then reset, but the link has been taken down. I tried to pm the

for the file, but no response yet.Thanks for all your help in advance
[Android Head-Units] fcortes626:
thats because .23 is known to brick the units if you dont know what you are doing.
[Android Head-Units] smallie42:
gps

I am aware of that, but it looks like that was only for units that did a MCU update, or installed for the wrong model. I could be mistaken of course, I have read a lot of this thread, but not all 144 or so pages. When I installed the radio and update last saturday, there was no warning about the gps failing, and there was no mention that the updates were not tested. When I pm'ed the OP, I told him my the details, I will repeat with more info here.

Bought unit from Peter Chan, believe it to be the AN-21-U. It's identical to the picture on the OP. Unit came with version .62. I upgraded to .68 and lost my GPS. I have not done an MCU update, and have not seen where to do a model change. I have tried factory reset, and reinstalling .68 before it was posted in the OP that it breaks GPS. On page 138 or so of this thread, there appeared to be a fix of downgrading to .23, do a factory reset, then upgrade ... The link was removed while I was reading and writing down the steps.My MCU is at 4.1.0-1-10-0101.

I dont know of any other options at this point, and the discussion seems to have moved away from GPS fixes. I use the gps more than any other function in my truck.

I have tried to be patient, assuming someone was working on a fix, and maybe someone is, but it has been several days now with no new news, and well over a day since my pm to the OP. The OP asks to pm for the file if needed, and if .23 is a problem, I certainly understand that. But without a response and no new posts here about the issue, I dont know what to do...
[Android Head-Units] KID52:
Thanks, didn't know the video had actually been posted already! And thanks for the other links too.

I think a nickname is definitely deserved!

Sorry the PM system is useless as I get no notification and the top right corner text is not very obvious... Does anyone know if it is possible to get an email when you get a PM?
[Android Head-Units] fcortes626:
have you tried installing .62 and doing a factory reset? dont install .68 because thats what breaks the gps.
[Android Head-Units] jakejm79:
Click "Control Panel up in the upper right" then scroll down to "Edit Options" under the "Settings and Options" section on the left side and then click the check box next to "Receive Email Notification of New Private Messages"
[Android Head-Units] KID52:
Thank you, that will make life easier :)
[Android Head-Units] smallie42:
gps

I will try that before I do the .23, although from what I read, .23 is what fixes it. Kid52 sent me the link, Thank you very much! Downloading now...

PutLocker is such a pain, If we could move the files to another host, I would be more than happy to donate to help with hosting...
[Android Head-Units] KID52:
Mirror 1 is Putlocker, Mirror 2 is direct HTTP in the main post, although I only sent you the Putlocker link via PM. Reason why I used Putlocker is my own experience as a free user of it has been the best, due to unlimited downloads and speed.