yashsingh1/xdaforums huggingface dataset:
[HTC Desire C] uchihasparky:
Yah. I tried to make this thread safe but I really don't think it will work... :(

EDIT: technically this is not Einstein.frat's work anymore...
[HTC Desire C] addictz10:
mods said that works of einstein.frat is named as "warez" ... dunno if mods will accept it... :rolleyes:
[HTC Desire C] aashay960:
:confused:Why exactly was he banned?
[HTC Desire C] Aman_Arora:
For not following the rules :p

HE actually talked quite angriliryprobably)

SO he was banned.
[HTC Desire C] webhijacker:
He could create another account with another email -.- but he left
[HTC Desire C] aashay960:
You dont know that.. Maybe he is here and has kept it a secret :p
[HTC Desire C] uchihasparky:
He is saying that he left because he was addicted to xda, in a conversation with LaKsHaY on the android forums. (Which is a lie in my eyes)
[HTC Desire C] LaKsHaY1997:
Yea..He said that :eek:
[HTC Desire C] aashay960:
Why do I find it hard to believe that there are other android forums that exist, apart from XDA :p lol
[HTC Desire C] webhijacker:
Yeah that's possible :D :°
[HTC Desire C] Aman_Arora:
It great that till now this thread has not been closed :silly::p
[Samsung Galaxy Mega] Warnahly:
Hey guys, am I the only one who us dumping the mega 6.3 for the note 3 and I actually think its worth it

Share your thoughts
[Samsung Galaxy Mega] Kangburra:
Crazy, I love this phone, there is nothing I would change, even the lower power results in better battery.

I bought the mega for the screen, and was worried I would miss the S3, well nope, I am so happy with this phone I am not even looking at the tiny Note 3.
[Samsung Galaxy Mega] zeyadhan:
i will buy note3 and keep mega 6.3
[Samsung Galaxy Mega] jpeps:
Keep mega 6.3 hopefully get root soon and get note 3
[Samsung Galaxy Mega] rakesh_4utoo:
I am a huge screen fan that's why I love Mega 6.3 , if by any chance I can use Galaxy gear with Mega I wouldn't opt Note 3.

But sometimes I feel that my Note 2 is way faster than Mega :)
[Samsung Galaxy Mega] Techngro:
I went to the AT&T store today and played with the Mega 6.3 for the first time. HOLY COW that thing is ginormous! I really did love the screen and that of course is the main reason anyone would buy this phone.

The only problem I had was that it seemed kinda laggy. It was running a store demo program that you had to exit to play with the actual device. I don't know if that had anything to do with it.

I really do want to love the Mega. I mean, I opened up a Google Play Book and it looked so beautiful reading on that massive screen. But if it is gonna be lagging, then I might have to go with the Note 3.

[MENTION=4691826]Warnahly[/MENTION]: Maybe i'll buy your Mega if I decide to go that route (if it's still around). :)
[Samsung Galaxy Mega] inurb:
If they made a 6 inch note 3 I would leave the mega. Until then...... Mega is perfect for everything I do. I feel like i9200 performs better than the i9205..... weird.
[Samsung Galaxy Mega] gx3k:
Sticking with my Mega and waiting for Mega 2.
[Samsung Galaxy Mega] kipue:
What he said!

Also, regarding day to day performances of 6.3, I can't say there is anything to report one way or another.

I'm coming from the Nexus 4, which was really smooth, and the Mega isn't as smooth but it certainly isn't a bother.

Also I don't play too much 3D games (got my PC for that :)) but for example, if you go highest settings on Riptide GP 2 it is really barely playable. So that's something to know if you do like that. Maybe when and if we get CM it will get better.

And lastly, my wife got the Note 2, and damn it's small :D. I'm sure Note 3 will destroy the Mega 6.3 when it comes to performances, so your priorities are what matter; I read, work, browse and watch videos, so I would have nothing to gain with a faster CPU and such :)
[Samsung Galaxy Mega] gx3k:
High end flagship phones tend to focus on boasting rights than actually giving people what they need. Mid range phones are more value for money. Why pay for specs and features you don't need? Until I find apps that I need which won't work well with the Mega, I'll be sticking to it (until the Mega 2 that is). I change phones almost every year so I'll probably get this year's high end specs on a mid range price next year.

Note 3: £649 <-- I don't think the features/specs are more than double from what you get from the Mega

Mega: £315 <-- I can get 2 of these and still get £19 change for the price of the Note 3 (for cases or sd card)
[Samsung Galaxy Mega] Warnahly:
if it comes to that we will arrange and i'll be happy to sell it ( if my dad didnt take it first ) :p
[Samsung Galaxy Mega] koniakki:
"Returning or passing on a great phone that many and I really want, because as I was swiping my homescreen it took 0,002ms longer(lag)...."

Just puting the thought out there. Everything lags in life... I can even say that mostly for humans also... ;)

Does the Mega lag a lot? Does it lag when opening the camera? Does it lag when opening phone book? Does it lag when opening the phone dialer/call log? Does it lag when opening messages? Does it lag when opening the Market? Does it lag when opening the music player? Does it lag when opening Settings? Does it lag everytime? Does it lag everywhere?

If someone answers YES to all those above, please let me know... :P
[Samsung Galaxy Mega] marcdunn82:
Yeah man I'll wait to see what the mega 2 is all about. The note 3 screen is too small. Also that's too much money. I would have loved a 600 chip in this phone though or at least the full 2gb of ram.
[General Topics] NitroGEEK:
There is a new Technology called power transfer technology which sends electro magnetic fields in specific direction... This technology is currently being used in the electric busses that charge wirelessly(In South Korea)
[General Topics] S0AndS0:
It's not that new, as a technology, perhaps in this application or nation. Nikolai Tesla (inverter of radio and much more) used induction to transmit power over many miles, the lab was burned down twice and tech long forgotten because none at the time could figure out how to meter and charge for it. I'm glad that it's getting revised because the charge mats just don't cut it for wireless power.

Sent from either my SPH-D700 or myTouch3Gs

Debian Kit/QEMU Linux Install guide for all android devices that I'm writing:

http://xdaforums.com/showthread.php?t=2240397

Now have working Installers for ARM Java 7 JDK + Maptools + jMonkey
[General Topics] clapper66:
I would rather charger my phone via wire. For the galaxy s4 there is a wireless charger that only charges at around 1/2 an amp where as my wall charger charges at 2 amps a second. Wireless charging is ones of those things that is cool but charges slower and cost more than the basic USB wall charger. :cool:
[General Topics] drewwtek:
This pretty much says it. I'd rather use the wire too, since you can at least maneuver and use the phone while it is charging. Your usage is very limited when it is stuck to the mat. It's cool for show and tell, but not much use afterwards.
[General Topics] RuffaloBone:
With said technology your device would not be stuck to a mat, or anything for that matter. You would have to be near the transmitter though. I agree with sticking with wired charging for now. I do like the magnetic charging they are using in the Xperia Z1. Still uses a dock but it will be nice while I'm working at my desk.
[General Topics] ivene:
not new eh..

:D wireless charging is not really good for those places that is temperature higher than 20 degress C
[General Topics] chan.sk:
Contactless, induction chargers - those are items the "wireless" charger refers to.

Electric toothbrush has been using it for a very long time and they come in various forms, usually a stud or a ring to hold the toothbrush in place while being charged. The cellphone indcution charger uses the mat type.

The working principle is all the same. The simple attached diagram shows a basic charger. Nowadays, there are sensors and microprocessors to detect the level of charge and to apply "intelligence" to the charging process.
[Android Q&A, Help & Troubleshooting] Soo G:
Hey, I'm kind of new to this rooting and what not but I watched plenty of xda-dev videos from plenty of users. Got the Unlock, Clockwork-Recovery, and Root going and the last thing I was doing was putting a ROM on. (Xperia ROM). Nothing was wrong with the rom, my phone has had no problems putting it on the sdcard. So when I turned off my phone to install the rom, I went into bootloader, then into clockwork-recovery, started to install the rom, restarted my phone so it would boot-up into the rom. Then the Xperia start-up logo thing was going so I automatically thought everything was working. Then it stayed like that for 10-15 minutes. Thats when I knew something was wrong. So I was gonna go into bootloader and then into Clockwork-recovery to try to reinstall it but it wouldn't let me go into bootloader. Just went straight to Clockwork-recovery. So I just rebooted, tried to start the rom back up but kept staying at that loading logo. So I looked up on xda forums on how ot fix it (brick) and so I tried all these different types of steps in order but at this point, I cant go to bootloader. I cant download a file off my pc to my phone (vice-versa). I cant start up the phone normally. I don't have any files. It's just stuck on Clockwork-Recovery no matter what I do. I've downloaded different types of files and what not but nothing has seemed to help me. At this point I think the phone is done for.

Someone please help.
[Android Q&A, Help & Troubleshooting] dxppxd:
Post in your device forum. And read your device specific section. You probably flashed a wrong rom (for a different model).
[Android Q&A, Help & Troubleshooting] Soo G:
The rom was only for my phone (HTC One S). Mine was up-to-date so was the rom. I can't see my phone specs because its bricked.
[Android Q&A, Help & Troubleshooting] demkantor:
Is your recovery fully functional? If so does it have sideload functionality? If so, do a full wipe in recovery and then side load a working ROM

Also, you still have a bootloader or your phone wouldn't even turn on. If the above doesn't work hopefully you can find some combination of button pressing to get you into fastboot mode
[Android Q&A, Help & Troubleshooting] Soo G:
good hbmics

Its functional, but I can't do anything with my sdcard. Everytime I try to mount or wipe, it'll say "error mounting /sdcard" or "E: can't mount /sdcard/".

And I do not see a option for sideload.

I also found a trick to get into bootloader and fastboot.
[Android Q&A, Help & Troubleshooting] Soo G:
These are my specs. On bootloader.

*** Tampered ***

*** Unlocked ***

S-ON

HBOOT

RADIO

eMMC-boot

Whenever I press "FACTORY RESET" or "CLEAR STORAGE" it just goes to "htc quietly brilliant" w/ the dev. stuff in red text, then screen goes black (as if it was reseting) and shows the "htc quietly brilliant" w/ red text again then loads recovery and does nothing else.
[Android Q&A, Help & Troubleshooting] demkantor:
Try wiping through fastboot and flash a new recovery there. Make sure to check md5sum for recovery

If your not sure how to run fastboot commands look through this

http://xdaforums.com/showthread.php?p=41374534

Being you still have radio secure flags many commands won't be avalible
[Android Q&A, Help & Troubleshooting] Soo G:
I can't do majority of those steps because in cmd almost everything I type in gives me either a "<bootloader> [ERR] Command error !!!" or "FAILED <remote: not allowed>".

I'm able to flash a .img to my phone but i'm not able to send a .zip.

After doing most of the steps that I could on that link in order, when I try to go to recovery it just pops up "HTC Quietly Brilliant w/ red text" then goes straight to bootloader.
[Android Q&A, Help & Troubleshooting] demkantor:
They aren't steps, its a tutorial on how to use fastboot. You are s-on and don't have an engineering bootloader so many things aren't available to you. Try this

fastboot erase system -w

fastboot erase recovery

fastboot flash recovery recovery.img
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] paketecuento:
i've upgraded with 1.60b.96wwe version of wm2005 my xda II. after that the bluetooth connection was ok. my radio version was 1.14.

but when i changed to 1.18, 1.17, 1.10 and 1.08, a problem with my parrot ck3000 appears.. i'm allways hearing a strong beep or noise when the phone is dialling. it's very hard and disappoint me.

i want to solve that or take back my 1.14 radio...

anyone help me?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] SaBo:
Had the same problem with Radio 1.18.

Will try 1.14 now.

Thanks

Sascha
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] r0ger:
Parrot & Radio version

Ciao I'm tryng the 1.08 version but I'm experimenting the same problem. Some news?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] paketecuento:
after testing almost every combination, I stayed with radio 1.14 and 1.60c.

this is the most effective combination. still having the problem,but less few times...
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] SaBo:
I tried 1.14 now and have to say: no difference to 1.18

Strange sound from ck3000 when dialling

Will now try 1.08 and 1.10

Sascha
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] paketecuento:
i am, now, thinking that the problem is the m$ bt stack. in wm2003, we have bt HEADSET, and now we have HANSFREE profile.

in headset mode everything is wonderful (quick connect and disconect. also your parrot doesn't switch off the radio, only short beeps when receiving a call phone in wm2003)

when you're dialling in wm2003 the radio is active until the call is conected to the other person. in wm2005 not. when you are calling, it stops inmediately everything.... :(

any ideas?
[Xperia Arc Q&A, Help & Troubleshooting] GreatVegeta:
Hey guys, i was searching for the walkman visualizer as a livewallpaper but I founded nothing. Does someone know where I can find it?
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
You can extract this wallpaper from any stock ROM.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] GreatVegeta:
Its a Feature in the walkman app itself, but I want to set it as a livewallpaper
[Xperia Arc Q&A, Help & Troubleshooting] GreatVegeta:
Does anyone understand me?
[Xperia Arc Q&A, Help & Troubleshooting] GreatVegeta:
?

Xperia arc s Stock ics .587
[Xperia Arc Q&A, Help & Troubleshooting] farazbaig48:
I also searched. Didn't find. Have to design it yourself
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Superrman:
Hello,

i have WT19A live with walkman, i wanted to update from GB2.3.4 to ICS 4.0.4,

1.i open "Update Service" it was ready for update,

2.before apply the update ,just in case if something goes wrong, i opened the bootloader,

because my phone have carrier ROM,

if update will fail i can change rom,)

,

3.i return to "Sony Update Service" and now it saying ,can't update because "modification detected"

i know flashing any stock rom will fix this &also i can upgrade this way with flashtool, but the carrier ROM is better and built in with my primary language and i dont have backup of the that rom, what can i do to fix it?

it is possible lock the bootloader again another way that i can using sony service update again?

thanks!
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
Locking the bootloader now after all doesn't really make sense, as your warranty is void now and you can take all the advantages of an unlocked bootloader :)

Why don't you flash a custom rom/kernel now? What's your native language, because I guess there should be roms supporting many languages? ;)

Sent from my Nexus 4 running Android 4.3
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Bishal Pranto Roy:
[ QUOTE=Superrman;45393128]Hello,

i have WT19A live with walkman, i wanted to update from GB2.3.4 to ICS 4.0.4,

1.i open "Update Service" it was ready for update,

2.before apply the update ,just in case if something goes wrong, i opened the bootloader,

because my phone have carrier ROM,

if update will fail i can change rom,)

,

3.i return to "Sony Update Service" and now it saying ,can't update because "modification detected"

i know flashing any stock rom will fix this &also i can upgrade this way with flashtool, but the carrier ROM is better and built in with my primary language and i dont have backup of the that rom, what can i do to fix it?

it is possible lock the bootloader again another way that i can using sony service update again?

thanks![/QUOTE]

U Should Collect Ur Flashable .ftf firmware For Ur Device and flash it via flashtool.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Bolussimo:
Check this thread, maybe somehow SUS downloaded firmware and U can make ftf by Yourself.

http://xdaforums.com/showthread.php?t=2075736
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Superrman:
Thanks everyone

my native language is hebrew
[7" Kindle Fire HD Q&A, Help & Troubleshooting] MichaelBrock:
I realize there are dozens of similar threads but none so far has helped. I'll keep looking but in the mean time I thought I would try asking for advice.

I screwed up somehow attempting to root my Kindle HD 7". It was stuck in a loop returning to the "restore factory" screen w/ orange triangle every time. I bought a factory cable and the kindle is now in Fasboot mode.

However, every set of instructions I can find to take the next step of restoring the original firmware requires adb and/or fastboot to recognize the kindle. I cannot figure out how to get that to happen. Both fail to recognize it. I modified my adb_usb.ini file to add the line 0x1949 and I modified

sdk\extras\google\usb_driver\android_winusb.inf file to have the required hardware ids for the kindle (I tried the "stock" ids as well as the ids currently listed for the tablet in device manager). I added the sdk paths to my environmental variables. adb & fastboot commands work but neither finds the kindle.

Windows Vista is recognizing the kindle HD as Other Devices > Tate-PVT-08 but fails to load any drivers when it is first found (I get an error).

Any ideas?

Edit/update: I found a thread explaining how to force Windows to change the drivers. I forced it to change to the Android Sooner Composite ADB Driver and it is now listed as an ADB Interface device. still not recognized in adb though.

Another thing is that I am unable to update the drivers to use the adb kindle drivers. Windows simply reports that it "could not find driver software for your device".
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Try the drivers in my SIG, they might do what yours already did though and not show up, but they should work if you update the driver to them. I am not a fan of vista, but I can think of several reason why u could be having issues offhand, like uac or driver signature enforcement, I believe driver signature enforcement was on vista, not positive though. Anyways try out my drivers and if that doesn't work maybe the command prompt isn't running with admin privis.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] MichaelBrock:
Your drivers were recognized and installed by Vista! Windows now sees it as an Android Phone > Android ADB Interface. Still no luck getting adb to find the kindle though. I think next I'm going to try deleting/uninstalling adb & the sdk and starting again. It isn't spelled out anywhere but I half suspect the paths are wrong somehow.

I can update to Windows 7 if there is any chance that would help.

Thanks for your help!

Michael
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Your device is listed as a Tate device correct? That is not going to work with adb because that means it is in fastboot. You can't use adb commands with fastboot. Try running "fastboot -i 0x1949 getvar product" and see if it reports anything back.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] MichaelBrock:
Yes, if I uninstall the device and let Windows Vista find it, it is listed as a Tate device. My kindle is indeed in fastboot (I have a factory cable). If I manually force it to switch drivers I can have windows list it as a ADB interface device.

Ahh, I tried fastboot -i 0x1949 getvar product and I get a response from the kindle!

So...I guess on to the next step! One of these 40 tabs I have open probably has something on flashing the rom.

Thanks all!

Michael
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Craigzyboy:
I know this is an old thread, but it seems to be the one most relevant to my problem.

I've got pretty much the same issue, but its because i was trying to install chainfire on my rooted kindle fire hd 7 (tate). Installation was taking longer than expected, actually thought my kindle had frozen so did a hard reset....big mistake as now it doesn't load past the kindle fire logo screen.

Done the same, but when in fastboot, nothing.

This is pretty much where i'm at now, except on a windows 8 laptop, tried uninstalling everything related to my kindle, all adb, fastboot and sdk etc from my laptop before reinstalling and trying to update drivers but still not being recognised, did all the same things as above post, as been trying to sort this off and on for a while.

I've tried to install the drivers from your sig but keep getting the message "the hash for this file is not present in the specified catalog file, the file is likely corrupt or been the victim of tampering" so i'm at a bit of a stand still at the minute.

Any command i try use through fastboot just gives the <waiting for device> message with no response from my kindle. If either of you (or anyone else who reads this) can help it would be greatly appreciated.

EDIT: Got it recognised by windows finally, I opened "device manager", clicked "update driver software", "browse my computer for driver software" then "let me pick from a list of device drivers on my computer" where i found the right driver to enable fastboot to work and windows to recognise my tablet. Now to fix the damn thing.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Questionar:
Having same issue where my kindle isn't found in fastboot for some reason. When I type

fastboot -i 0x1949 getvar product

I get back Tate-PVT-08, but when i do fastboot devices I get nothing. I have Andoid ADB drivers installed and a factory cable. What is the problem?

Edit: Turns out i had to paste this in before everything -i 0x1949.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] grande25:
I'm glad this is a current topic again. I also need help. I've been running my rooted Kindle Fire HD 3d Gen going on two years now. I was using the firerooter to get it updated to 4.5.5 today and I'm pretty sure I bricked it--again. But this time I think I bricked it up real good.

I was doing this to hopefully get a recently updated game working again. But when it got hung up I freaked out for a second and made a mistake... I went ahead with a factory reset but then I realized that this would delete my game progress and I hadn't made a game backup before the update came on today so I was pretty much screwed in several ways.

Right, so when I was in the middle of the factory reset I was like... "****! I don't want to lose all my game progress!" and I immediately powered it down. And I immediately punched myself in the face after I turned it on and it did the lovely "kindle_fire" grey-scale initial load screen loop over and over. Based on what I've read, I'm pretty sure I've corrupted the bootloader or possibly deleted some boot partition.

I'm about sick of Amazon's bull****. They don't manager this part of their business very well at all. /RAGE

But before I throw this garbage in the dump where it belongs... I'm tempted to try to get this thing working.

I have a fastboot cable and some time. I can get to the fastboot info such as "fastboot -i 0x1949 getvar product" and it returns "product: Soho-PVT-Prod-07" . But, I can't get anything out of the adb commands to recognize the device. I've updated the .ini files from the android SDK.

Is there any boot partition I can load to this thing? Some way to hack into this? thx for any help