yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 Android Development] twerg:
got this wotking on bb49, looking good.

couple things, does not go into landscape for me, need for speed does not work (loads to splash screen then back to launcher), when i press screen on launcher all icons widgets glow orange (adw as wells as adw ex), linpack wlod but got one result of 37.

sms works for me, battery life looks great, feels very nice to use, love the extra features and customisaztion of miui. Great job done here
[XPERIA X10 Android Development] DooMLoRD:
@Ricardo

OMG this is beautiful!!!!!

amazing ROM...

THANK YOU RICARDO FOR UR BRILLIANT WORK

will get LP working on it... and post the files soon...
[XPERIA X10 Android Development] FelipeRRM:
Will download as soon as camera is working :p
[XPERIA X10 Android Development] o0k00l:
Same here waiting for camera till then Trip MIUI 2.3.4 is my daily rom ...:(
[XPERIA X10 Android Development] Crowds:
@Doim

Thx. As soon as you send me the files ill post them or if you want post them and ill link them on 2nd post;)

Regarding camera im on the same steps as others. If trips didnt release hes code...
[XPERIA X10 Android Development] b3yond:
@doomlord can't u check on the SMS problem thank u
[XPERIA X10 Android Development] Crowds:
Are you on 49?

Seams whos on that bb doesnt have sms issue (read a few posts back)
[XPERIA X10 Android Development] b3yond:
I'm rick; but i don't know what's going on..I'm on Bb 49
[XPERIA X10 Android Development] lollen:
PROBLEM!

Ive installed Xrecovery, downloaded this ROM and ran it through Xrecovery..

BUT!

When booting up my phone, it first introduces the MUIU ROM and the bootscreen for this. it boots up and I end up in the unlockscreen...

BURT! (again) now it suddenly reeboots to normal sony ericsson..

After this it reboots into MUIU and so on

this keeps going like a circle...

WHY?
[XPERIA X10 Android Development] cjsabaki:
What base band??? 49 or 52 or higher with patch.??
[XPERIA X10 Android Development] lollen:
I dont know what that is...
[XPERIA X10 Android Development] lollen:
Might the problem be that when i installed ROM from SD that it was called update.zip.zip???

The two .zip.zip???
[XPERIA X10 Android Development] DooMLoRD:
tested on baseband 2.0.52 (from baseband collection)...

can confirm that SMS issues is there... whenever i send / receive SMS the app FCs...

same problem on 2.0.49 from baseband package...

trying reflashing rom/fresh install on baseband 2.0.49
[XPERIA X10 Android Development] b3yond:
Yup I used 52 and 49 and the problem continue even with stock kernel
[XPERIA X10 Android Development] Pierre Duc:
Seriously.. it really says in the first post..(or read below :p) Only use this on BB 49. Why are ppl still so confused and baffled when it won't work on another BB..

(and i know some said they reverted back to bb 49 and are still having the issue.. bla bla :p flash it better, format it better, wipe everything better, and it should really work......)

Sorry, just had to say that. Anyhoo, updated to v1.2 now, just to get rid of the random reboots which were kinda annoying to say the least ;) Glad you say you fixed it now. I really hope so.

but i still have a little downer, bluetooth is still showing irregular problems. But I guess thats out of your hands.

Keep up the good work, and ill test this version till it breaks! (hit you back on bugs i come along)

x
[XPERIA X10 Android Development] Crowds:
basebands on 2nd post to test;) let`s see how it goes...

edit: new file on 2nd post to see if it helps :D "format-system-only"
[XPERIA X10 Android Development] Crowds:
on witch bluetooth?

i use it on my car and on MW600 and it works fine.
[XPERIA X10 Android Development] Crowds:
If anyone had some stability issues and have SetCPU or Droid overclock installed, remove them cause this build already have some tweaks in it that may conflit.
[XPERIA X10 Android Development] Pierre Duc:
Pioneer DEH-P8100BT! It used to work without a problem.

Now it disconnects without a reason. But not completly disconnects. Its weird and hard to explain..

it works fine if I make a phonecall

it works fine if I start the car, and it autoconnects and plays my music.

it (sometimes) fails to work if i receive a call and try to answer it. It does answer it through my radio, but disconnects immediatly. Which means i sometimes have to drive dangerous to get my phone out of my pocket ;). (where it still says im connected and calling through bluetooth, although i can't hear them)

it (sometimes) fails to work when i'm all ready driving for a while, and start music on my phone. Phone still says its connected with bluetooth, so it won't use the phonespeakers. But there is no sound coming out of my radio

it worked without an issue on 1.6 and 2.1.

I tried to bluetooth fix .apk which got suggested on wolfbreaks ROM, but that didnt really help

and now that i mention all this, it could be my radio as well. Although, it works fine on other android versions...
[XPERIA X10 Android Development] Crowds:
In that case seams to me thats an hardware bluetooth issue since that happen on any custom rom, right? Only work with stock SE roms.

Ask some friend to borrow his bluetooth to see.
[XPERIA X10 Android Development] Pierre Duc:
mm, good idea, ill try that thx.

(still hoping its a ROM problem.. ;))

Anyhoo, I just had a random reboot..after trying to login to market (well, just typing my password actually). Perhaps its just a singular event, but it happend 30 minutes after installing the new ROM.

This version is much smoother btw, i can really notice the difference. nice job
[XPERIA X10 Android Development] ksquared_au:
here's what i have done......

1) BB52 added Rom = message FC

2) wipe cache added Rom = Message FC

3) wipe , flash bb 49 = message FC

4) factory reset , added rom = message FC

WHAT AM I DOING WRONG?????
[XPERIA X10 Android Development] Mask-1:
Uninstall TelocationProvider.apk and reboot ;)
[XPERIA X10 Android Development] Pierre Duc:
Btw, it would had been nice if i could still rotate my screen rendeiro :p

Setting is on..

Reinstalled rom still not working

Works on 1.0 and any other ROM

X
[XPERIA X10 Android Development] ksquared_au:
Sorry......but how? Cant seem to for Manager programs....
[XPERIA X10 Android Development] ksquared_au:
Just tried installing Root Explorer and i get an FC there too.
[XPERIA X10 Android Development] cjsabaki:
Try file expert free in market, should work fine!
[XPERIA X10 Android Development] ksquared_au:
Ok, deleted the apk. rebooted. Same issue.....
[XPERIA X10 Android Development] cjsabaki:
Check websites miui.au and miuiandroid.com for bug info n fixes. Good info
[XPERIA X10 Android Development] b3yond:
Great ill do this
[XPERIA X10 Android Development] b3yond:
I have the same issue and I can't find was causing that
[XPERIA X10 Android Development] cjsabaki:
Guessing here.. try turning wifi off n see if text will send?????
[XPERIA X10 Android Development] b3yond:
Hey unistall what the guy told u fo into xrecovery wipe cache dalvix and batterie that works for me
[XPERIA X10 Android Development] Realorasz:
So before I try this out..

I'm currently on Wolf's ROM V061. I'm running K010 on BB52.

1. Can I just backup, then flash the update.zip?

2. Will I need to flash the kernel again or does this rom come with it?

3. Will it hurt anything if I restore my Wolf backup?

4. Do i need to flash the 'Test File' or is that optional?
[XPERIA X10 Android Development] ksquared_au:
yes my friend....i have done all that already. I wouldnt be asking if i hadnt.
[XPERIA X10 Android Development] b3yond:
Got sms working but when i click in a contact and choose sms and sent a message i get invalid recipient unless i type it manually
[XPERIA X10 Android Development] Crowds:
@ Pierre Duc

works fine with me...

@ Realorasz

1. yes. (i suggest that you format sdcard after backup only the files you want)

2. no. k10 as default already

3. i don´t think it will work

4. that´s just an option (that file will format your system)

@ b3yond

you`re right. sms works but not fully. had to look at that contact issue.
[XPERIA X10 Android Development] Crowds:
Temporary SMS fix:

Download the attached file and install then open Contacts Clean-up app, leave the 2 boxes empty and choose from the 4 options the last one (+XXYYZZZZZZZ). Enjoy;)
[XPERIA X10 Android Development] b3yond:
You done a great job!
[XPERIA X10 Android Development] Crowds:
Hidden features:

Hidden phone tests: Open dial pad type *#*#MIUI#*#* or (*#*#6484#*#*);

More hidden phone tests/settings: Open dial pad type *#*#4636#*#* (more for advanced users!!! If u don't know what u doing than don't change any settings here !!!)
[XPERIA X10 Android Development] Realorasz:
Ok so If I wanted to go back to my backup what would I have to do?
[XPERIA X10 Android Development] Crowds:
what do you mean?

i don´t think you can restore anything from another rom. you must install all apps one by one unless u have another MIUI rom and use MIUI backup tool.

to restore to any other rom you must install the rom first and then restore your backup from xrec
[XPERIA X10 Android Development] Realorasz:
So, install the WB ROM and then restore backup, and that should do the trick?
[XPERIA X10 Android Development] Crowds:
to revert to wolf`s rom...yap
[XPERIA X10 Android Development] Crowds:
Language pack

Italian Language Pack added on 2nd post;)
[XPERIA X10 Android Development] gogogu:
once my battery got to 15% I ended in bootloop, is that normal?
[XPERIA X10 Android Development] Realorasz:
Yes, that's a Kernel issue. I thought they removed the UV, didn't they? So it makes no sense to me.

Thanks.
[XPERIA X10 Android Development] Crowds:
nop!

doesn´t happen to me. witch version you have? the 1.0 or 1.2?

can´t remember on 1.0 but on the last one that shouldn´t happen
[XPERIA X10 Android Development] Crowds:
if he change kernel...
[XPERIA X10 Android Development] gogogu:
I did not change the kernel, and I installed the rom that was up about 12 hours ago. so whichever one it was then. Did you upload another one??
[XPERIA X10 Android Development] Crowds:
check version on:

settings > ayatem > about phone > more information > build number
[XPERIA X10 Android Development] gogogu:
I can't, I had to install a different rom to get it out of bootloop
[XPERIA X10 Android Development] b3yond:
Will this fix sms issues and rick can u please post the tmz for the black theme..please ..thanksss
[XPERIA X10 Android Development] Crowds:
do you mean the default theme (mtz)?

see attach and install through xrec
[XPERIA X10 Android Development] b3yond:
You the a beast thanks ..
[XPERIA X10 Android Development] Crowds:
beast?!

i´ll take that as a compliment and read...best :D:D:D
[XPERIA X10 Android Development] b3yond:
Lmao
[XPERIA X10 Android Development] Realorasz:
Seens the screenpower anims dont always behave. Its fine though. Also, and not as fine, the text is black in the add to home screen menu and its subfolders. This is a problem.

One more thing. My animations across the board are choppy. Is this a problem from my being on bb52 or is GB just not optimized for X10 yet?

Sent from my X10 BlackEditionHD
[XPERIA X10 Android Development] Crowds:
regarding black text on black yeah...it´s a known issue.

can´t tell about 52. im on 49 and everything works fine
[XPERIA X10 Android Development] Realorasz:
All animations completely smooth?
[XPERIA X10 Android Development] Realorasz:
If i flash bb49, will i need to reaash the ROM?
[Galaxy Tab 10.1 Android Development] Chandelure:
Tested, walked through the steps to my friend (Skype :D). Works 100% on Linux Mint too :)
[Galaxy Tab 10.1 Android Development] Konklone:
Everything worked for me up to the GMTP part - I can grep through /dev and I can see the "gtab" device there. But GMTP insists "Detect: No raw devices found."

I'm still running Maverick, but I added the maverick-backports repo, which has gmtp, so I would think it would work.

This is a Samsung Galaxy Tab 10.1v (from Google I/O). Any ideas?

EDIT: I also tried the automounting option with FUSE. Attempts to cd into it with bash or open it from the Places menu in GNOME both give the message "Transport endpoint is not connected".

EDIT again:

OK, I disabled USB Debugging and now have a different set of problems. mtp-detect sees the device now, but the message upon running it is:

libmtp version: 1.0.3

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:6860 @ bus 2, dev 26
Attempting to connect device(s)
ignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
usb_clear_halt() on IN endpoint: Device or resource busy
usb_clear_halt() on OUT endpoint: Device or resource busy
usb_clear_halt() on INTERRUPT endpoint: Device or resource busy
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
[Galaxy Tab 10.1 Android Development] bcmobile:
Can you post the output from 'lsusb' ?

re the "Transport endpoint is not connected" - I just got this same error on 64bit Natty. Will try and see if I can find out why..
[Galaxy Tab 10.1 Android Development] Konklone:
Ah, just saw your reply. I edited my post up above, but the gist is - you can't do this while USB Debugging is enabled. The Tab has to be running its "MTP Application".

Now I'm getting the stranger errors above. I'm going to try mounting it with FUSE now to see if that helps for some reason.

EDIT: For the record, I'm using the correct vendor and product IDs in my rules file:

ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666" SYMLINK+="gtab"
[Galaxy Tab 10.1 Android Development] bcmobile:
You may be right. When I wrote this guide, I was using a VM. It is possible that the fact that I was using both MTP and ADB at the same time has something to do with how VMWare presents the devices to the guest OS.

Now I am using 'bare metal' Natty 64 bit and have the same problem as you.

I have to go out for a while but will look at it again when I get back.

EDIT: Just tried mtp-detect and it is finding the device. I suspect USB Debug is not the issue, but I'll leave it in your capable hands - really got to go now

EDIT2: See here http://www.usb.org/developers/devclass_docs/MTP_1.0.zip OK - Im really REALLY going now. Back online in a few hours :D
[Galaxy Tab 10.1 Android Development] Konklone:
I couldn't get anywhere until I turned off USB debugging. When USB debugging is enabled, I *can* use adb to get into the shell, see files, install apps, etc. I can even transfer files over adb, through the command line! Can you get MTP to detect it with USB debugging enabled?

With USB debugging off, I have once in a great while (only twice in all my attempts) while gotten mtp-detect to connect to the device and print sane output describing the device. Even when those happened, running the command immediately again didn't connect correctly, and gave me the same error messages I was getting before. Both times I got it to connect, it was soon after plugging in the cable, but it doesn't happen every time.

Intermittent heisenbugs are the worst, yet I don't think I have a busted cable, given that adb works perfectly consistently.

Maybe I should try this again after updating to Natty...I'd been meaning to do it anyhow...

EDIT: One thing I notice is that on the Tab, when the "MTP Application" is running after plugging in, the 5-dot "in progress" animation is extremely choppy, as if the device were very very busy. If the device were very very busy for some reason, this could explain why a successful connection can happen only once in a great while. I'll try rebooting the device, I guess.

EDIT2: I rebooted the device, and I removed the USB extension cord I was using, but neither helped, still getting the same intermittent success. (I got mtp-detect to connect to it a few more times - all soon after plugging in the cable, and none were repeatable without unplugging and replugging it in.) The animation actually wasn't choppy before, that's just how it looks - 5 discrete animation frames, one for each dot.

Something interesting though: this time I had the Tab resting on my knee, and I felt a haptic buzz after running mtp-detect on one occasion. I looked down and saw the MTP Application restart itself. Then I ran mtp-detect again and I felt 3 haptic buzzes in quick succession, followed by a successful detection and output. But when running mtp-detect *again*, no dice.

This is messed up.
[Galaxy Tab 10.1 Android Development] bcmobile:
Messed up indeed.

Yes, both work simultaneously on 32bit Natty

Note that you have to unmount the gtab for mtp-detect to work. I compared the output from mtp-detect on the 32bit working VM and the 64bit non-working 'bare metal' machine and the output was identical. I suspect this means that mtpfs is not where the problem is :confused:

Re the strange problem with haptic feedback - I have had mine power off all by itself when testing some different parameters in the rules file.
[Galaxy Tab 10.1 Android Development] bcmobile:
[64bit working]

OK. Problem solved... kind of. There seems to be some kind of bug in fuse which requires the filesystem to mount with higher permissions to run properly (at least on Natty AMD64)

If you use the new 64bit rules file I have attached, it should work. Basically it uses 777 permissions instead of 666. Not great, but working nonetheless.

New rules file for 64bit:

ACTION!="add", GOTO="gtab_rules_end"
SUBSYSTEM!="usb|usb_device", GOTO="gtab_usb_end"

ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0777" SYMLINK+="gtab"

LABEL="gtab_usb_end"

LABEL="gtab_rules_end"

EDIT: If someone wants to experiment with lesser permissions and see what the minimum is and post back, that would be helpful for all.
[Galaxy Tab 10.1 Android Development] Konklone:
Sigh, thank you for taking so much time to help me so far, but I wonder if I'm a lost cause.

I spent a bunch of today finishing my upgrade to Natty, including a full wipe and reinstall. (I have a 32-bit machine, btw.) Now I can't even get it to detect my MTP device at all (mtp-detect says "No raw devices found."), with or without debugging enabled.

One possibly important topic - it's really surprising to me that yours works either way, because lsusb shows that a different product ID is exposed to the host, depending on whether debugging is on or not. With debugging disabled, it's 6860, like your example. With debugging enabled, it's 685e. When I run lsusb, only one of those will show up, never both. So if yours is the same device, I have no idea how your rules file could be agnostic to debugging being enabled. If yours is not, then that might explain our different experiences.

Anyway, I've Thanks'd all your posts in this thread, solved or not. I appreciate your help.
[Galaxy Tab 10.1 Android Development] bcmobile:
You're more than welcome.

I noticed that in Windows, both devices appear in device manager. That is a very strange problem you have discovered.

I just posted instructions and files to give you root access! Might take your mind off the MTP issues for a while :)

Who knows... the problem might just go away :D
[Galaxy Tab 10.1 Android Development] ajvogel:
Are you sure? On my device its the other way around. Without debugging its 685e and with debugging its 6860?
[Galaxy Tab 10.1 Android Development] ajvogel:
Ok I got it working on my device, I switched on usb debugging in settings. lsusb now returns 6860 and I am able to mount the galaxy tab using the process outlined above.
[Galaxy Tab 10.1 Android Development] Konklone:
This is craziness. Is my Galaxy Tab a rare mutant piece of hardware who had its USB numbers switched?

Also - I noticed that Ubuntu somehow automounts my tablet and can read/write to its disk, through a Nautilus plugin. But I still get nothing with mtp-detect. I don't understand how the world works.
[Galaxy Tab 10.1 Android Development] mimidede:
I've also got an I/O tablet (updated to 3.1) and I followed this tutorial, so thanks for the help you provided! I managed to copy some files to the device but it ended up freezing my computer (running Ubuntu 10.10).

So I unplugged the tablet, and saw that effectively those few pictures and pdf files had been copied to the device successfully. Pictures are in the Gallery, pdf can be read with Aldiko... but the funny thing is that when I mounted again the tablet -using Ubuntu again- it shows all folders as empty!

That is, 0 files in all tablet folders.

I tried "showing all hidden files" with Nautilus. No luck, nothing is shown. Went to the folder using command line, did an ls -la (just in case who knows! maybe it would show something!). No luck either, directories are apparently empty and have "1 January 1970" as modification date... if it helps.

I can see the files inside the folders using ADB but it's obviously not ideal, specially compared with simply using Nautilus.

Does it happen to you too?
[Galaxy Tab 10.1 Android Development] ikon8:
Anyone get this working? I'm having the same exact issues as Konklone. I'm on Maverick and tried the different udev rules and it still doesn't work. I'm gonna be pissed if I have to buy the stupid Samsung USB adapter just to get USB mass storage.
[Galaxy Tab 10.1 Android Development] setoelkahfi:
[ASK]Noobs need solution

gMTP tells me that there is no device. Any ideas?
[Galaxy Tab 10.1 Android Development] Lou2serious:
I'm having the same issue. First try I was able to plug in and mount to my netbook. Tried to plug into my mac and it didn't work. Hasn't worked since then, i'm considering doing a factory reset.
[Galaxy Tab 10.1 Android Development] kungfoofool:
I'm running Ubuntu 10.10 64-bit. Note that you do have to enable backports to install gmtp.

Edit /etc/apt/sources.list, uncomment the lines with:

deb (http-url) maverick-backports main restricted universe multiverse
deb-src (http-url) maverick-backports main restricted universe multiverse

Run

sudo apt-get update && sudo apt-get install gmtp

I had to unplug the device and replug it back in a couple of times before gmtp would connect to it properly. It seems to be pretty flaky.
[Galaxy Tab 10.1 Android Development] xipher_zero:
Wow...........

This is nonsense ..... is there a way to enable USB Mass Storage or are we completely hosed with MTP?
[Galaxy Tab 10.1 Android Development] lassegs:
I remember this **** from back in 05, struggling with Creative's MTP mp3 players. It sucked then, still sucks apparently.

Retail 10.1 32 gig rooted. lsusb shows

USB Debugging Enabled = 685e

USB Debugging Disabled = 6860

So I've tried them both, changed the udev rule, rebooted, gtab shows up under /dev/ , but both mtp-detect and gmtp tells me the same

No raw devices found.

EDIT: a bit off topic, but are there really no one who have considered making a GUI tool out of USB debugging and adb push?
[Galaxy Tab 10.1 Android Development] BlackOtaku:
So have people been getting this to work on the retail Tab 10.1?
[Galaxy Tab 10.1 Android Development] Entropy512:
It looks like no, but I think I might have figured out why - will test tomorrow.

Apparently libmtp will only find devices it "knows".

The commit for the Galaxy Tab support was 5/26/11, Ubuntu has version 1.0.6 of libmtp which was released 2/11/11.

So it looks like we need to find a PPA that has 1.1.0 for libmtp

Edit: None seems to exist and trying to install the Oneric packages doesn't work - too many packages in Natty depend on libmtp8 and this is libmtp9. Can't have both at once.
[Galaxy Tab 10.1 Android Development] BlackOtaku:
Is there anyway to compile the SGT support into libmtp8 and then replace it with the repos' libmtp8?
[Galaxy Tab 10.1 Android Development] Entropy512:
I just tried backporting the timeout and detection patches to libmtp8. (libmtp-1.0.6)

At this point the tab is now detected by MTP but all operations hang/timeout, even beyond the "extended" 60 second timeout added by the patch.

Maybe there's another dependency I'm missing.