yashsingh1/xdaforums huggingface dataset:
[Sprint HTC EVO 4G LTE] OstrichSak:
I did some searching and the only related threads I can see involve account & sign in issues which this is not. I'm not getting the error message telling me that I need to sign in. The problem I'm having is that when I attempt to upload an image to Picasa my albums are not listed where you would select an existing album to upload to. I also am unable to click the '+' symbol that allows you to create a new album to upload to. When I go into my Gallery to browse folders I can select Picasa from the drop down and all of my folders are there and my account is still sync'd in the accounts section of settings. So... it's seeing the account and the images already there no problem. The issue is with uploading specifically. I tried to un-sync and re-sync my Picasa account in settings as well as rebooting and various combinations and nothing seems to help. I'm running the stock ROM but the phone is rooted. I attempted to load the GB Gallery which is related but I don't think was the cause of this because I ran into it in the past on customer ROMs on other devices. I always just chalked it up to a bug in the ROM and never was able to solve it. Now that I'm on the stock ROM there really isn't much of an excuse for this.

Anyone have a fix or any advice for this? I use this a lot so I miss not having it when I just had it the other day.

Thanks for the help!
[Sprint HTC EVO 4G LTE] frigidazzi:
I've had this problem always with ICS. My main google account doesn't show the list of albums. Where my secondary one does show the coupld it has.. I have been unable to figure it out :/.
[Sprint HTC EVO 4G LTE] Freelancerx:
Why don't you just use auto upload in google+. It is basically doing what you want to do except it does it automatically. Auto upload creates a folder that only you can see in your picasa web albums, you can then either move the image to a public folder or just share the image via link. If you just want to share one picture you can do it via email or the google plus app as well.
[Sprint HTC EVO 4G LTE] frigidazzi:
I don't want to keep all of the pictures l take though. More importantly I don't see option to move the pictures to albums from the google plus app.
[Sprint HTC EVO 4G LTE] OstrichSak:
After further research it appears as though it's an Android bug. If you have another type of account sync'd it will confuse Picasa and you won't be able to see your folders or login/upload. For instance, say your Google account is the following email address:

username@gmail.com

and your DropBox account username is the same thing:

username@gmail.com

This will cause a conflict for some reason when it comes to Google being able to log you in and it will fail. For me I think it was my DropBox account which uses the same email as my Google account so it was causing issues. I tested this w/o having my DropBox account sync'd or even installed and w/o fail I can now access my Picasa folders and upload w/o issue.

Google needs to address this bug. That's all their is to it. This is a stupid error that shouldn't be too difficult to address and it's creating heartache for customers since most won't know why it's not working the way it just should be. It also seems that the last thing Google wants is people going back to their old email accounts for sign-in and notifications from various products. This is counter-productive for all their efforts to date.

FIX THIS GOOGLE! :mad:
[Sprint HTC EVO 4G LTE] OstrichSak:
That's not really the point. Android shouldn't be denying login to DropBox so that I as the consumer can use whatever services available to me that I wish to use.
[Sprint HTC EVO 4G LTE] frigidazzi:
I agree it's silly to have that kind of error with the same email.

I just found an app PicasaTool that lets me upload to my picasa account correctly. So for now I guess I will use that.
[Sprint HTC EVO 4G LTE] OstrichSak:
I'm just not comfortable giving 3rd parties my username and password so I will just change my Dropbox email and use the built in functionality with this as a workaround until such time that Google sees fit to address this bug.
[Sprint HTC EVO 4G LTE] frigidazzi:
Understandable. It doesn't ask for UN/PW by the way. It just uses the coin authentication thing.
[Sprint HTC EVO 4G LTE] typhoonikan:
I use PhotoSync by Akira soumi.

Simple app that syncs at a time I specify (8am) so that my dcim folder on phone, dcim on tablet and picasa are all three synced everyday :)
[Sprint HTC EVO 4G LTE] AllSeeyinEye:
Several months further and on ICS (4.0.4) it wasn't fixed. JB is coming for my phone (SGSII) this month. Let's hope JB fixes this bug.

For now my solution is: changed the email of my dropbox and deleted facebook apps, doing everything on the mobile website now.
[Sprint HTC EVO 4G LTE] djscissorhands:
How do you keep your root when an ota update is pushed to the lte? Whats everyone's opinion on an app in the play store called ota root keeper?
[Sprint HTC EVO 4G LTE] Evo_Shift:
Works for my kindle fire and it worked on my transformer prime. Just have to make sure to actually click protect root in the app once you install it.
[Sprint HTC EVO 4G LTE] Riff76:
Don't take otas simple as that. Devs will examine them and update their roms, usually really quick about doing the update

Sent via XDA Premium
[Sprint HTC EVO 4G LTE] butterbuns:
Yup one of the first rules of rooting is to not take a update through OTA. Usually doesnt take long for the devs to pull then apart and post rooted versions..
[T-Mobile Samsung Galaxy S II SGH-T989] techfanatic9:
*SunKist Orange Universal Port*

Please comment on which rom it works on! Thanks!

Ported this theme from: Here

Roms have been tested and working on:

*Darkside Evolution 2 Beta 3

*Darkside UCLE2 Beta 7

*SkyICS UCLE2

______________________________

Changelog:

*V 1.0 - Initial Release

*V 1.1 - Fixed Battery Percent Issue

Contacts.apk

Mms.apk

Phone.apk

SecBrowser.apk

Settings.apk

SystemUI.apk

framework-res.apk

lidroid-res.apk

lk95-res.apk

twframework-res.apk

Please leave feedback. Thanks!:D

V 1.1 Download Link Below:

How to install theme: (This video will show you the correct step except for the file name in the video)

[YOUTUBE]bXcl0a5pdGw[/YOUTUBE]

Don't forget to hit the thanks :D

Enjoy!
​
[T-Mobile Samsung Galaxy S II SGH-T989] appdroid:
2nd theme out!:eek:
[T-Mobile Samsung Galaxy S II SGH-T989] dave2metz:
Does this work on UCLE2 Darkside 7.1?
[T-Mobile Samsung Galaxy S II SGH-T989] Rekzer:
Oh this is nice, like the lil tab effect on the notification dropdown.
[T-Mobile Samsung Galaxy S II SGH-T989] pro2kon:
How can I dl from phone
[T-Mobile Samsung Galaxy S II SGH-T989] pro2kon:
Nevermind I figured it out will report back running dse2b3
[T-Mobile Samsung Galaxy S II SGH-T989] dave2metz:
Has anyone tried this? If so, what rom?
[T-Mobile Samsung Galaxy S II SGH-T989] pro2kon:
Running on dse2b3 n the status bar does not show up other then that pretty good
[T-Mobile Samsung Galaxy S II SGH-T989] gatorstew:
SunKist orange? More like UT orange. YUK! :p
[T-Mobile Samsung Galaxy S II SGH-T989] hiz99:
Could you please make this in red?

Sent from my 4.5 inch Galaxy
[T-Mobile Samsung Galaxy S II SGH-T989] tennandcoz1:
There is only one UT brother,and that is the University Of Texas.So you need burnt orange.This is ok for ya
[T-Mobile Samsung Galaxy S II SGH-T989] suaverc118:
Hookem Horns \m/
[Samsung Galaxy Nexus] techbeck:
Using AOKP and every time I wipe/flash a new build...all my contact pictures are blurred and low quality. I have to edit the contact and reselect the image for it to display the way it should.

ideas?

thanks
[Samsung Galaxy Nexus] thiagodark:
That's not a problem, That's because google contacts, where contacts info is stored, does not support high res images...

Dont ask why...

Edit: more accurate answer here : http://xdaforums.com/showthread.php?t=1411960
[Samsung Galaxy Nexus] theking_13:
Yeah, its better to use HaxSync if you have a fb account instead.

Sent from my Galaxy Nexus running AOKP+Franco
[Samsung Galaxy Mini] dhidyawdiyan:
Anyone know how to reset/clearing mobile data limit counter?

Thanks in advance

Sorry for my english. :)
[Samsung Galaxy Mini] A_U:
Its a bug actually if u r usin rom by squad.

I guess u r usin a very old rom..so upgrade ur rom.

Squad removed it coz he wasn't able to reset the counter.
[General Questions and Answers] projax:
Hi guys,

I'm wondering, is that such an app on android market where u can tag photos onto a pdf or autocad file? For example i have an pdf file that shows a plan view of an area, then i want to tag specific area of the file to a photo?
[AT&T, Rogers HTC One X, Telstra One XL] dominican2589:
I searched and could not see a straight answer. I am current on version 1.73 and I have not rooted my phone. I would like to root it but scared about voiding my warranty. I have no desire to unlock the bootloader as I dont want to change roms. All I want is to have root access so I can backup my phone in case something goes wrong.

So can the phone be unrooted? Would AT&T/HTC know that I have rooted my phone and unrooted it?
[AT&T, Rogers HTC One X, Telstra One XL] gunnyman:
If you unroot by running the ruu nobody will know you rooted.
[AT&T, Rogers HTC One X, Telstra One XL] ted77usa:
YES the only thing right now if i'm not wrong is to flash stock 1.73 RUU http://briefmobile.com/download-att-htc-one-x-stock-ruu and u can always check the thread on xda also how to do.....just plug ur phone with all the driver needed....and walla ur phone back to ATT stock
[Android Software/Hacking General [Developers Only]] Wetzel402:
Calling all developers with extensive knowledge of NVflash :D

I know NVflash commands but I have never tried to run NVflash on a device with an encrypted bootloader nor have I had to try to source all the necessary files so I have some questions.

1. Would the following command be correct? Because even this simple sync command is exiting with a failure.

nvflash --bl bootloader.bin --sbk [boot key here] --sync

2. Is the bootloader.bin file universal or is it device specific? Where do I find one, can I edit one to work, etc?

I am working with the Acer Iconia A200 which is relatively new so no one has cracked NVflash on it yet so any help at all would be greatly appreciated.

Thanks!
[Android Software/Hacking General [Developers Only]] Wetzel402:
Thanks! I am primarily after --read and --getpartitiontable so that I can create a stock backup so those that brick have a recovery option. Sounds like the most important part now for me is getting the correct files together. I have the SBK though unconfirmed.

I personally have never used --odmdata, do you have any insite into that command?

My previous device, the Dell Streak 7, had a fully unlocked NVflash so there was no SBK or anything like that to worry about. I miss those times :p
[Android Software/Hacking General [Developers Only]] gee one:
I thought the omdata were device specific things like memory configuration? Not sure how important it is for reading partitions.

The other thing with nvflash is once you start it, you can send more commands with the resume command:

Nvflash sbk bootloader etc

Nvflash -r --read 6 blah blah

Nvflash -r -- read 7 blah blah

...

Nvflash -r --go

Or something like that...

sent while running with scissors
[Android Software/Hacking General [Developers Only]] Wetzel402:
I don't really know because at least on the Dell Streak 7 it was a command I never used and I never saw used by others either. Hopefully someone has incite somewhere on how to get the files I need.
[Android Software/Hacking General [Developers Only]] eppeP:
If you have root you should be able to read the BCT and bootloader from the device with dd and then decrypt them.
[Android Software/Hacking General [Developers Only]] Wetzel402:
I have root and an unlocked bootloader. Please explain. DD? I have Windows 7 and Linux at my disposal.

Thanks!
[Android Software/Hacking General [Developers Only]] eppeP:
Yes, dd.

Copy some raw data from the block device on the device, something like

# /system/bin/dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/data.raw

Then transfer the dump to the computer and extract the BCT and boot loader.

I started writing a description but it quickly started to get long and it is late...

So you get a small ugly script that shows the steps instead.

This requires openssl, dd and hexdump.

#!/bin/bash
#This script extracts the BCT and bootloader out of a dd dump of the block device on a tegra 2 device
#The first 6.5M should be enough, something like:
#/system/bin/dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/data.raw

#SBK written together
#e.g. 0xDEADBEEF 0xBAADF00D 0xCAFEFEED 0xBADDCAFE => "DEADBEEFBAADF00DCAFEFEEDBADDCAFE"
SBK="DEADBEEFBAADF00DCAFEFEEDBADDCAFE"

#Input file
raw_file="data.raw"

#Output files
bct_file="out.bct"
bl_file="bootloader.bin"

echo "Extrating the BCT data"
dd if=$raw_file of=bct_encrypted.bin bs=16 count=254 skip=1 2> /dev/null

echo "Decrypting the BCT data"
openssl aes-128-cbc -K $SBK -iv 0 -d -in bct_encrypted.bin -out bct_decrypt.tmp -nopad
dd if=bct_decrypt.tmp of=out.bct bs=16 count=254 seek=1 2> /dev/null
rm bct_decrypt.tmp
rm bct_encrypted.bin

#Read some general information
bct_version="$(hexdump -n 4 -s 0x20 -e '1/4 "0x%x\n"' $bct_file)"
block_size=$((2 ** $(hexdump -n 4 -s 0x24 -e '1/4 "%u"' $bct_file)))
page_size=$((2 ** $(hexdump -n 4 -s 0x28 -e '1/4 "%u"' $bct_file)))
odm_data=$(hexdump -n 4 -s 0xFE4 -e '1/4 "0x%08x\n"' $bct_file)

#Boot loader 1
bl_start_block=$(hexdump -n 4 -s 0xA98 -e '1/4 "%u\n"' $bct_file)
bl_length=$(hexdump -n 4 -s 0xAA0 -e '1/4 "%u\n"' $bct_file)

if [ "$bct_version" != "0x20001" ]; then
echo "ERROR: Unexpected BCT version: $bct_version"
exit 1
fi

echo "Block size: $block_size"
echo "Page size: $page_size"
echo "Boot loader 1 start block: $bl_start_block"
echo "Boot loader 1 length $bl_length"
echo "ODM Data: $odm_data"

echo "Extracting the booot loader"
bl_start_byte=$(( $(($bl_start_block - 64)) * $block_size ))
bl_padded_length=$(( $bl_length + $((16 - $(($bl_length % 16)) ))))
echo "Extracting $bl_padded_length starting at offset $bl_start_byte"
dd bs=1 if=$raw_file of="bootloader.enc" skip=$bl_start_byte count=$bl_padded_length 2> /dev/null

echo "Decrypting boot loader"
openssl aes-128-cbc -K $SBK -iv 0 -d -in bootloader.enc -out bootloader.tmp -nopad
dd if=bootloader.tmp of=$bl_file bs=$bl_length count=1 2> /dev/null

I may have gotten the block to byte convertion wrong, it is correct for the offsets on the device I have, but we will see.
[Android Software/Hacking General [Developers Only]] Wetzel402:
Currently way over my head considering I just finally figured out mount commands :P

I will start doing some research on the topic to learn more and before you know it I should have the files I need :D
[Android Software/Hacking General [Developers Only]] Wetzel402:
I did get the bct file but the bootloader.bin file is not working. With this line:

openssl aes-128-cbc -K $SBK -iv 0 -d -in bootloader.enc -out bootloader.tmp -nopad

I keep getting an error "option 0 doesn't exist". Any ideas? Also when you have some time could you please explain what exactly all of this is doing? I understand very little of this syntax because I am quite noobish with Linux.

Thanks!
[Android Software/Hacking General [Developers Only]] eppeP:
That looks like you don't have SBK set (so it is trying to use "-iv" as key, and then don't know what to do with the leftover 0).

The steps must be performed in order and in the same shell as some of them are depending on variables set by previous steps.

Sure, it is mostly just about reading some values at known offsets.

dd if=$raw_file of=bct_encrypted.bin bs=16 count=254 skip=1

Will read 254 blocks of 16 bytes, skiping one block from $raw_file into bct_encrypted.bin. So we are reading bytes 16-4080 into bct_encrypted.bin.

We are skipping the first 16 bytes since this is a checksum (CMAC) and not part of the encrypted data, so bringing that along would mess up the decryption of the next 16 byte due to the cipher block chaining.

openssl aes-128-cbc -K $SBK -iv 0 -d -in bct_encrypted.bin -out bct_decrypt.tmp -nopad

Decrypt the content of bct_encrypted.bin using the SBK and store the decryped data in bct_decrypt.tmp.

dd if=bct_decrypt.tmp of=out.bct bs=16 count=254 seek=1

We skipped the first 16 bytes previously, so the decrypted data is a bit incorretly offset.

So this takes bct_decrypt.tmp and writes it to out.bct offset 16 bytes so that we get a 4080 bytes file again.

bct_version="$(hexdump -n 4 -s 0x20 -e '1/4 "0x%x\n"' $bct_file)"

Reads the version field of the BCT, this is a 32bit integer at offset 0x20.

I would expect the version to be 0x20001.

block_size=$((2 ** $(hexdump -n 4 -s 0x24 -e '1/4 "%u"' $bct_file)))

Reads the block size field in the BCT, also a 32bit integer, at offset 0x24.

The block and page size is stored in log2, so then we need to raise 2 to the value we found to get the actual block/page size.

For example, if we found the value 14 the block size is 2**14 = 16384.

#Boot loader 1
bl_start_block=$(hexdump -n 4 -s 0xA98 -e '1/4 "%u\n"' $bct_file)
bl_length=$(hexdump -n 4 -s 0xAA0 -e '1/4 "%u\n"' $bct_file)

Read start block and size of the first boot loader (the BCT file have space for four boot loaders)

bl_start_byte=$(( $(($bl_start_block - 64)) * $block_size ))

We have the start position of the boot loader in blocks, but we need it in bytes.

So multiply the block number with the block size. Unfortunatly this is not quite right, so we need to offset it a bit.

bl_padded_length=$(( $bl_length + $((16 - $(($bl_length % 16)) ))))

The encryption used, AES 128, works on blocks of 16 bytes, but there is no guarantee that the length of the boot loader is a multiple of 16 so we need to pad it to make sure it is.

dd bs=1 if=$raw_file of="bootloader.enc" skip=$bl_start_byte count=$bl_padded_length

Cut the encrypted boot loader out of the $raw_file.

openssl aes-128-cbc -K $SBK -iv 0 -d -in bootloader.enc -out bootloader.tmp -nopad

Decrypt it

dd if=bootloader.tmp of=$bl_file bs=$bl_length count=1

And take only the actual length of the decrypted data, discarding the extra padding data we took just to make it an even number of 16 byte blocks.
[Android Software/Hacking General [Developers Only]] Wetzel402:
Very impressive :)

Prior to this I have messed mostly with kitchens, cd, and mount so this is definitely a learning experience for me. After you described these commands I am convinced I could use most of these minus the fact I would have no clues what values to use in them :P

Thanks! I will have to try rerunning everything and see if I can get the bootloader.bin to come out.
[Android Software/Hacking General [Developers Only]] Wetzel402:
Here is my terminal output after copying and pasting in your script.

root@ubuntu:~# cd /root/Desktop
root@ubuntu:~/Desktop# SBK="B8A4C201EB6FF106EB00150430772103"
root@ubuntu:~/Desktop#
root@ubuntu:~/Desktop# #Input file
root@ubuntu:~/Desktop# raw_file="data.raw"
root@ubuntu:~/Desktop#
root@ubuntu:~/Desktop# #Output files
root@ubuntu:~/Desktop# bct_file="out.bct"
root@ubuntu:~/Desktop# bl_file="bootloader.bin"
root@ubuntu:~/Desktop#
root@ubuntu:~/Desktop# echo "Extrating the BCT data"
Extrating the BCT data
root@ubuntu:~/Desktop# dd if=$raw_file of=bct_encrypted.bin bs=16 count=254 skip=1 2> /dev/null
root@ubuntu:~/Desktop#
root@ubuntu:~/Desktop# echo "Decrypting the BCT data"
Decrypting the BCT data
root@ubuntu:~/Desktop# openssl aes-128-cbc -K $SBK -iv 0 -d -in bct_encrypted.bin -out bct_decrypt.tmp -nopad
root@ubuntu:~/Desktop# dd if=bct_decrypt.tmp of=out.bct bs=16 count=254 seek=1 2> /dev/null
root@ubuntu:~/Desktop# rm bct_decrypt.tmp
root@ubuntu:~/Desktop# rm bct_encrypted.bin
root@ubuntu:~/Desktop#
root@ubuntu:~/Desktop#
root@ubuntu:~/Desktop# #Read some general information
root@ubuntu:~/Desktop# bct_version="$(hexdump -n 4 -s 0x20 -e '1/4 "0x%x\n"' $bct_file)"
root@ubuntu:~/Desktop# block_size=$((2 ** $(hexdump -n 4 -s 0x24 -e '1/4 "%u"' $bct_file)))
root@ubuntu:~/Desktop# page_size=$((2 ** $(hexdump -n 4 -s 0x28 -e '1/4 "%u"' $bct_file)))

I don't understand the page size line enough to know what is going wrong or to change things but after that line displays the terminal exists without errors.

Any ideas?
[Android Software/Hacking General [Developers Only]] eppeP:
You are probably hitting the exit in BCT version check, since you are running it directly in the shell that would make the terminal dissapear.

What does out.bct look like?

What does

hexdump -n 4 -s 0x20 -e '1/4 "0x%x\n"' out.bct

give?
[Android Software/Hacking General [Developers Only]] Wetzel402:
That was the problem.

root@ubuntu:~# cd /root/Desktop
root@ubuntu:~/Desktop# hexdump -n 4 -s 0x20 -e '1/4 "0x%x\n"' out.bct
0xf16cb00b

So I modified the following line:

root@ubuntu:~/Desktop# if [ "$bct_version" != "0xf16cb00b" ]; then

Everything ran and out came the bootloader.bin. This should be the correct file then? Also the other two files (bootloader.enc&.tmp) were stepping stones to the final product (bootloader.bin) and are not needed correct?

When I get home from work if I have time I will try the following and see if life is good :D

nvflash --bl bootloader.bin --getbct --bct out.bct --sbk 0xB8A4C201 0xEB6FF106 0xEB001504 0x30772103 --go
nvflash -r --getpartitiontable partition.txt
[Android Software/Hacking General [Developers Only]] eppeP:
I would not expect a different version, I think it is more likely the decryption failed.

Could you make the data.raw file available to me?
[Android Software/Hacking General [Developers Only]] Wetzel402:
Here it is.
[Android Software/Hacking General [Developers Only]] eppeP:
The data looks ok, but it can not be decrypted using that key so you must have the wrong SBK.

Assuming it follows the same format as the Iconia A500 that SBK would belong to a device with UID 042800484400D057, is this the UID of your device?
[Android Software/Hacking General [Developers Only]] Wetzel402:
Yes that is correct. So you think Acer is using a different encryption method?

I tried the NVflash commands anyway and it doesn't run. Exits with the standard failure.
[Android Software/Hacking General [Developers Only]] eppeP:
Depending on what you mean, maybe and no. They are maybe allocating the SBK differently, but the encryption in still AES128.

Nvflash uses the key you give it to encrypt the command before sending it to the device, then the decrypts the command using the builtin key. If those two does not match the result will not be a recognizable command.

Depending on how you got the UID it may be worth trying a different way, some devices does not report the UID as their USB serial number.

Save this as apxuid.c and compile this using gcc -Wall -pedantic -o apxuid apxuid.c -lusb-1.0. Then run ./apxuid directly after starting the device is in apx-mode and see if you get the same UID.

#include <libusb-1.0/libusb.h>
#include <stdio.h>
#include <stdint.h>

int main(void)
{
unsigned char data[64];
int received_length;
int r = 1;
libusb_context* ctx = NULL;
libusb_device_handle* dev_handle = NULL;

libusb_init(&ctx);
dev_handle = libusb_open_device_with_vid_pid(ctx, 0x0955, 0x7820);
if(dev_handle)
{
r = libusb_bulk_transfer(dev_handle, 0x81, data, sizeof(data), &received_length, 10000);
if (r == 0)
{
if(received_length == 8)
{
printf("uid: %#016lx\n", *(uint64_t*)data);
}
else
{
r = 1;
printf("Error: We got %d bytes of data insetad of the 8 bytes we expected...\n", received_length);
}
}
else
{
printf("Error: USB read failed!\n");
}
libusb_release_interface(dev_handle, 0);
}
else
{
printf("Error: Failed to open device!\n");
}
libusb_exit(ctx);
return r;
}
[Android Software/Hacking General [Developers Only]] Wetzel402:
When trying to compile the terminal responds

root@ubuntu:~# cd /root/Desktop
root@ubuntu:~/Desktop# gcc -Wall -pedantic -o apxuid apxuid.c -lusb-1.0
apxuid.c:1:31: fatal error: libusb-1.0/libusb.h: No such file or directory
compilation terminated.
root@ubuntu:~/Desktop#

Does that mean I am missing a library file to make this work?
[Android Software/Hacking General [Developers Only]] eppeP:
You don't have the libusb 1.0 headers, possibly not the library.

In Debian those are part of the libusb-1.0-0-dev package, for other distributions I don't know.