yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sebmw:
I am completely unable to get Kies to see my 10.1 tab on my PC win 7. I always end up with an error message (Cannot start service on the devise. Please disconnect and reconnect the devise).

I tried the trouble shooting connection option, still the same no connection. Anybody have any tips on making that connection?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Jay Rock:
I always had problems with Task 14
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] UKseagull:
I think mine stopped working via USB with the last update, although it worked over WiFi. Have you tried both?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sebmw:
WiFi works fine, but I don't see option of updating the firmware on WiFi.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] M@31:
In the same boat, trying to get ICS update but won't connect via kies......

wifi works fine.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] bertiespeed:
The only way kies connects for me is using my unrooted backup. Any custom rom won't connect for me. Have you tried that?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] NukeThemTillTheyGlow:
I have the same problem. Tried to connect to Kies before the ICS upgrade and just now after performing the ICS upgrade. Nothing works, tried turning on USB debugging, etc.

Win 7 Ultimate 64 Bit

Galaxy Tab 10.1 64 gb Verizon LTE running new ICS stock rom
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] moodloid:
Which ROM do you use?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Just_Another_N00b:
Does factory reset work? On my HC 3.2 Kies (and USB drivers) were very finicky. Re-installed KIES/Drivers many times and only a factory reset got it primed and working. Have only seen ID mismatches once in a while after Stock ICS, but when it works Kies also recognises the tab.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] fageria:
my galaxy y has same problem after rooting the galaxy y by NeoX BlackStar X1....:crying:

i need to get back my contacts.......:crying:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] okty2k:
if you are rooted, then the Tab will not connect to Kies. The same way like some Samsung applications will not work if rooted. So, there are two options that you: root and live free or stay connected to Samsung like an apple lover.... Sorry, but I am terribly upset on Samsung...

If you are stock and cannot connect... try removing all the drivers from PC (check internet for how to remove hidden devices). And try to uninstall and reinstall Kies
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
My rooted tab connected just fine to Kies.

What I think you mean is that if you're not running a stock ROM, you can't connect to Kies. That's probably the case. Mine is stock but rooted.
[Nexus 7 Q&A, Help & Troubleshooting] Uh60m Pilot:
I am trying to get my videos set up for my upcoming nexus 7. I use iskysoft media ripper and they do not have a 1280 x 800 setting. I have been using 1280 x 720 but this uses a ton of space for a non HD movie.

What is the best scaled down resolution for non HD movies on that will not have black bars? Thanks for help!
[Nexus 7 Q&A, Help & Troubleshooting] jptech:
it would be 720p

since the 80 pixels at the bottom are used for the tablet menu bar.

thus you get a content area of 720p.
[Nexus 7 Q&A, Help & Troubleshooting] artvandelay440:
Since you are manually transcoding them, use 640x360 for widescreen and 640x480 for fullscreen. This will get you standard definition movies.
[Nexus 7 Q&A, Help & Troubleshooting] animatechnica:
Good rec and dont just look at resolution also look at bit rate. Higher bit rates mean better quality but larger file size. I typically am ok with 640x360 at 1.5 mbps bitrate
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ManthanRB:
I was playing Asphalt-6 the game was running Supper Fine in my Xperia Mini:laugh: Suddenly the received a message and i wonder the game started lagging for a while.!!:(

I tried to free up the Ram from running services but it was not needed because phone was already having 182MB free Ram.!!!

Asphalt-6 was minimized though.!!

I game didn't lagged after receiving the message but it did for 3-6 seconds.!!:mad: Why?:confused:

Yes its not a big issue but would like to know the exact culprit if someone is interested to name on..

I don't think Asphalt-6 is heavy on Mini & it should not having a problem like this..

I don't like to comprise Gaming experience.

Although the Clock widget stops working after a small gameplay,instead i'm using the Stock clock widget & theres no another widget on my home screens.!!

The status bar shows the perfect time but the clock widget freezes.!!!:eek:
[Verizon Droid Charge] JihadSquad:
I have over 800mb free on /data and when I try to download >20mb apps it says I have insufficient storage. What am I supposed to do about that?

Sent from my handheld computer using electromagnetic radiation.
[Verizon Droid Charge] cujo6801:
I had this happen before..

My fix was to go into recovery mount everything ..then go to advanced and run fix permission ...hope that helps..

SENT FROM THE DOG POUND
[Fascinate Q&A, Help & Troubleshooting] stevebanks:
Hi Guys -

I'm looking for a MIUI GB Rom for the Fascinate. All of the ones that I'm finding have broken download links.

Does anyone have one that they can dropbox to me? I normally run Powerwashed GB for my fascinate, but wanted to try something new. I can install any ICS rom on my phone, because data stops working on all ICS roms for the Fascinate.

I'd appreciate it if anyone does.
[Fascinate Q&A, Help & Troubleshooting] phaetyn:
miui.us under Forum > Samsung > Samsung Fascinate

Zkate15's post about 5 down labeled "MIUI 2.1.6[Works With ES 1.12.9 Rick_S]" has a link to a good GB MIUI ROM
[Samsung Galaxy Nexus] KnuckleSandwich:
I have a play store GSM Nexus which I rooted and unlocked, but have not flashed any ROMs to. Do I need to unroot and/or lock to receive the JB update when it comes out OTA?
[Samsung Galaxy Nexus] JaiaV:
No. Your recovery must be stock, however.

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

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

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

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

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

http://xdaforums.com/showthread.php?t=1657037
[Samsung Galaxy Nexus] KnuckleSandwich:
O

Edit: thx for the links, I had done a search but my foo is weak, thx again.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Smantanasiceapa:
Hy everybody!

I'm going to install now on my Ace, 2.3.5. . I wanna know if that every presented mod/kernel on Android Development is compatible whit 2.3.5
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Prawesome:
Simple Answer,No....
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Smantanasiceapa:
do you know if there even are good workin' mods/kernels for 2.3.5? or 2.3.4?

or cyanogenmod works on 2.3.5?
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Shaaan:
Did you read the stickies?

:cool:
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Prawesome:
Read the Newbie guide in general section and you will understand :) Anyway,most of the mods present for SGA are fro GB only,so no harm done if you install it.Oh,and for Dev things,browse Development section
[HD2 Android Q&A, Help & Troubleshooting and Genera] SpoonyVoid:
Okay, I have honestly searched everywhere - Google, the xda forums, other forums and I still can't find something to help me with this strange problem I have.

PAST SITUATION

I installed TyphooN CyanogenMod ROM v3.5.8 around a month ago and I used it with no major problems (few android.acore repeated force closes that was dealt with by re-installation). During this time, I could power the phone off and power it on with no problems.

PRESENT SITUATION

This is where things go wrong. Recently, I decided to install TyphooN CyanogenMod ROMv3.8.5 (the latest one) by booting into MGDLR, doing a factory reset, wiping the system and dalvik caches and then installing the new 3.8.5 zip file. It installed properly and I booted into Android and was enjoying the new improvements and bug fixes. I had no problems until everything started force closing suddenly so I decided maybe a reset would fix it. AND THIS IS WHAT THE PROBLEM IS It boots to the Android Logo and stops there. I waited for 30 mins but it was still stuck at the Android logo and no matter how many times I took the battery out and put it back in and rebooted it, it was still stuck at the Android logo.

HOWEVER when I did a hard reset and wiped the system and dalvik caches and installed it again, it installed fine and booted into the system. When I tried to power it off and power it on again, the same problem happened where it was stuck on the android logo.

WHAT I TRIED TO FIX IT

1) A clean installtion, did a task 29 and installed everything again. Same problem happens.

2) I did a hard reset (wiped system and dalvik caches as well) AND THIS TIME I installed the previous version I was using with no problems (v3.5.8) and I had the same problem! :( Even with that version it still gets stuck on the Android logo screen.

I can use the ROM perfectly and my phone works fine, but if ever I need to reboot my phone for any issue it won't start up again and gets stuck on the android logo. I have to do a hard reset and re installation for it to work again but that means all my data, files and messages will be lost each time. So you can see the inconvenience I'm facing.

WHAT I THINK IS THE PROBLEM

1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?

2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?

Should I do a clean installation (task29) and install the previous ROM version I used with no problems and see if the problem still persists or if its only since I installed the new ROM version first?

Thanks for your help. :) And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
[HD2 Android Q&A, Help & Troubleshooting and Genera] shanman-2:
did you get things sorted?:cyclops:
[HD2 Android Q&A, Help & Troubleshooting and Genera] SpoonyVoid:
Well not yet. I am working on it. Does anyone have a download link to the latest version of ClockworkMod Recovery with 150MB and 5MB cache? I tried the HD2Toolkit and it just doesn't work for me, I plugged in my USB, it indicated USB Debugging was on and meh, it didn't click.

Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.

I'll post my results here soon. :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nigeldg:
Sadly I can't give you any new suggestions, but I can certainly rule these two out as possibilities. I've never taken out the SIM when flashing, and you can't flash without the SD card. Recovery 3.0.2.5 is actually (from what I've heard) the most stable version. Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.

You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
[HD2 Android Q&A, Help & Troubleshooting and Genera] SpoonyVoid:
Okay, So I tried this. The ROM installed fine but when I tried to power off and power on again it didn't work, the same problem happened where it got stuck on the Android logo.

WHAT I DID THEN

I decided enough's enough and that I can't really use my phone with Android if in some case something happens and I have to reboot it, I'll lose all my data and I'll have to reinstall it all over again.

So I switched to Windows 6.5 version 2.10.531.1 running Radio 2.15.50.14 and everything installed perfectly and I even rebooted the phone after installation and it worked. It came on with no problems. I'm guessing this is an issue that only affects Android then.

Thanks for the reply. :) I have not tried other ROMs out of fear of bricking my phone to be honest. Typhoon ROM is like one of the easiest for a newbie to install.

And yes, when I was searching around the forum, I did come across the issue of bad blocks. Sadly, I totally forgot to check whether it was affecting my NAND before installing WinMo 6.5. I'll try and look around the forums and google on whether I can check my bad block status on WinMo 6.5 somehow. If I can't, I think I'll use WinMo 6.5 for a while now, I can't really bear having to install and reinstall and install and reinstall, I feel like it'll make the bad block situation (If I do have it) worse.

I'm going to play around with WinMo 6.5 ROMs now. But if ever there is any development on my problem, I'll post on this thread and keep people updated. :)

I do have one question though, will upgrading to WinMo 7.5 be affected by the bad blocks? (If I have it)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nigeldg:
Just saying, although it doesn't really matter, it's Windows Phone 7 (not WinMo 7). One's sh*t, and one's brilliant ;) I don't have any actual experience with Windows Phone though, so I wouldn't know.

As for your concern about bricking your phone, there isn't any way you can do that outside of flashing an incorrect radio, and if you have an EU HD2 then AFAIK there isn't really ANY way of bricking it. Try other ROMs, they have exactly the same install process as TyphooN. In fact, starting fresh from WinMo might actually help. As long as you stick to this guide and use the correct partition size, you will never really go wrong. You can obviously also check for bad blocks after you install Android again (if you decide to do so, of course).
[HD2 Android Q&A, Help & Troubleshooting and Genera] SpoonyVoid:
I have quite exciting news! well for me at least

I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.

So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.

So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...

Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. :) Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone! :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nigeldg:
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
[HD2 Android Q&A, Help & Troubleshooting and Genera] SpoonyVoid:
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.

Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.

When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.

I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nigeldg:
Ah that may be the problem then. You shouldn't really be touching anything immediately after flashing. Let the ROM settle for 5 minutes, complete the set up and then reboot a few times. As for why the Android Market isn't opening, once again am completely stumped, sorry. Try clearing the app data and cache then opening it again. I don't know whether or not this would work, but try to install a new play store.apk (e.g. the updated one in the HD2 Android Themes and Apps section) and try again. On no ROMs have I ever had this issue.

As for your being unsure about the bad blocks, I would be inclined to agree with you there, as it seems unlikely that after so long there would still be no bad blocks, especially if you and your brother were often flashing things.
[HD2 Android Q&A, Help & Troubleshooting and Genera] shanman-2:
dmesg command from a terminal emulator might give some info on the presence of bad blocks, if you haven't already tried it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Marvlesz:
A logcat would be really useful when:

-ever your ROM gets stuck after a reboot.

- You face any random force close.

I used to have issues with the market closing without any error, it turned out to be unsupported where I was. In the new google play, it'd open, but nothing shows up. Fixed it by using DroidVPN.

Was the market working prior to this problem?

Also, have you checked the battery pins? (sometimes, they cause unpredictable problems)

You could also give cLK a shot, and see if the problem persists.
[Android Q&A, Help & Troubleshooting] Manvendra05:
Hi...since i have installed tapatalk 2 on my mobile....it crashes whenever i try to open any of sent or inbox messages...why is iy happening and how can i prevent it ?:thumbup::cool:
[Android Q&A, Help & Troubleshooting] scandiun:
Try to go to Settings -> Applications -> and delete data and cache for tapatalk (you will have to log in again in all forums)
[Android Q&A, Help & Troubleshooting] Manvendra05:
Ohkaay thanks :)
[Android Q&A, Help & Troubleshooting] scandiun:
Did it work?
[Android Q&A, Help & Troubleshooting] Manvendra05:
Yes man..thanks again :D:p:rolleyes::thumbup:
[Android Q&A, Help & Troubleshooting] Manvendra05:
Dude the problem is still continuing...whenevr i open any PM it crashes...even after doing what you told...:cool:
[Galaxy Tab Q&A, Help & Troubleshooting] butters67:
I cracked the screen on my korean shw-m180s galaxy tab. The LCD seems fine so I need to replace just the digitizer. I check on ebay and the only digitizers I see are the ones for the P1000. Does anyone know if these are compatible with the korean tabs?

thanks
[Galaxy Tab Q&A, Help & Troubleshooting] KasSGT:
Search on youtube for: Samsung galaxy tab 7" take apart by durapowerglobal. Com

Also, click on the link provided in there description. I think they will be able to help you out.

Verstuurd van mijn GT-P1000 met Tapatalk
[Galaxy S III Q&A, Help & Troubleshooting] infernosoft:
So right now, I have the nexus s 4g. I'm eligible for an upgrade today and am wondering if anyone else has been in this position and have any advice to offer?

Thanks!
[Galaxy S III Q&A, Help & Troubleshooting] Ahmato27:
I had the GNex.. I see no difference between the two.. but I suggest getting the S3.. for its speed and nothing else..
[Galaxy S III Q&A, Help & Troubleshooting] alewis2k12:
International s3 is the way to go....nothing on the market can even compare to this beast......believe me on that......
[Galaxy S III Q&A, Help & Troubleshooting] jsmasterx:
Actually i would recommend the North America model

With it's LTE chip and Qualcomm Krait it outperforms the quad core exynos in a lot of aspects
[Galaxy S III Q&A, Help & Troubleshooting] Bilhouse:
As someone who has owned both (currently with the S3) you will be fine with either one of them.

Get the Galaxy Nexus if you want:

- Quick stock Android updates

- On screen buttons

- Access to an already large development scene

Get the S3 if you want:

- Better camera

- Larger display

- Better CPU

- Micro-SD support

- Touchwiz extra's

Since I like quick updates and on screen buttons I may be moving back to the Galaxy Nexus but I haven't fully decided.
[Galaxy S III Q&A, Help & Troubleshooting] Sensamic:
Do you guys think the new Nexus later this year will have micro sd support? And maybe LCD IPS instead of super amoled?
[Galaxy S III Q&A, Help & Troubleshooting] setspeed:
If I had to upgrade today then I'd do the same thing over and get the S3. I have to admit that I am absolutely green with jealousy over the Google Now feature in JellyBean that Nexus owners have just got...

S3 is a great phone, but I think that I'm going to sell it and get (one of) the new Nexus phone(s) later in the year, presuming it's a bit smaller. S3 is a bit too big for me to operate safely (ie. held securely) and comfortably (ie. holding it too long gives me cramp) with one hand. I think something slightly smaller would be a better fit for me.

Also, the value of being the reference device for Google is something I never really appreciated before now - I've spent years flashing Android phones with ROMs that are basically beta-tests, following Google putting out a new software version.

Not taking anything away from the devs at all I really appreciate their work, but it's really hard to get a decent ROM working on a phone that it was never designed for/drivers aren't available for/OEM hasn't put out an update for. And I know that despite being a really popular device, the S3 probably has a really long wait until a nice fully working JellyBean is available for it.

---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------

I hope it'll have external storage support. The screen I'm not too bothered about - my S3 is more than good enough for me, even if it's not technically the highest res around. If the new Nexus has that, or even better a SuperAMOLED Plus, or an IPS LCD screen then I'd doubtless be happy with it.
[HTC One X] brikxz:
I would like to know what do you recommend kernel to flash after installing Coredroid ROM v3.6?