yashsingh1/xdaforums huggingface dataset:
[HTC One X] Mr Hofs:
You can keep it unlocked and rooted, only you loose the root after updating to stock JB. And the bootloader does NOT have to be locked.

When you are done updating you can easily reroot the phone. I don't see the big deal there......
[Nexus 7 Q&A, Help & Troubleshooting] QuackzMcDuck:
Well recently I've been looking into buying a Nexus 7; however, I have a few unanswered questions that I couldn't find using the search tool, so I thought I'd create an account.

(These questions could seem a bit noob-ish, I'm new to the tablet tech and looking for one to buy)

First question, is the Nexus 7 display pressure sensitive?

Second question, in your opinion is a screen protector necessary? (I'm generally pretty careful with my eletronics and plan on purchasing a case for this. I don't have a protector on my Galaxy S3 and after 4 months of usage I've managed to scratch it twice in my pocket; however, you really have to be looking for the scratches to see them and sometimes they are only visible when finger print oil is wiped over them.)

Third question, if the display is pressure sensitive and if I happened to purchase a screen protector, would said screen protector affect the pressure sensitive capabilities? (I know this could vary depending on the thickness of the screen protector).

Appreciate the help.. :silly:
[Nexus 7 Q&A, Help & Troubleshooting] Miami_Son:
Well, there is this forum named Q&A for things like this. A capacitive touch-screen (same as what your S3 has) is not pressure sensitive. That's why it is called a touch screen. A screen protector will have no discernible effect on usage. I highly recommend the use of a screen protector. I also recommend more descriptive thread titles so that the search function works better. Adding the word screen to the title would have let others with similar questions find this in a search.
[Nexus 7 Q&A, Help & Troubleshooting] QuackzMcDuck:
Thanks, I'll take those suggestions into consideration and I have already gone and reported the thread to be moved to the Q&A section, I usually don't make these mistakes on forums, but it seems that I have missed that section.

In regards to you saying that this has a touch screen, do you know how well the tablet fares at drawing? I'm not a professional artist or anything just wondering if the tablet does decent in a drawing situation.
[Nexus 7 Q&A, Help & Troubleshooting] Miami_Son:
I've done very little of that on mine, but unless you need a level of precision it should be OK.
[Nexus 7 Q&A, Help & Troubleshooting] NoSeRider:
If you attach a Wacom digitizer to a Nexus 7, the tablet displays pressure sensitivity.

Since there's a script for the HP Touchpad to make the Touchpad pressure sensitive,

and both tablets use the same CPU, would it be possible to make the Nexus 7 pressure

sensitive without the Wacom?

http://www.youtube.com/watch?v=x4otTtqN6u8

http://www.youtube.com/watch?v=C6ghnM7VH0w
[Nexus 4 Themes and Apps] SubyWill:
Matted Blues is a really great theme, It's not really compatible with 4.2+ ROMs though. Has anyone heard about the theme being updated? Or is there already an updated version somewhere? :cyclops:
[Nexus 4 Themes and Apps] eep2378:
Brainmaster has a Mattedblues theme for rasbean ROM. He took it down though(had to work something out with the original creator I believe).
[Samsung Galaxy S (4G Model)] Shinydude100:
My sister has this phone and its pretty cool, still love my epic more though. :p ahem anyway. I've been part of the community at the Epic 4G for some years now and I have realized the importance of gathering the few devs you have and going towards a common goal, only then will you achieve more than what you've been able to do so far.

I see an unofficial CM7, unofficial CM9, and unofficial CM10 and unofficial CM10.1

My suggestion? Depreciate CM7 or finish that with your devs from their respective talent. If that gets depreciated/fails, you as devs of this community will learn from it and grow that much stronger/smarter from it.

Of course, from here I'd try to fix CM9, although, if it takes you more than 3 months to make it to stable, move on and depreciate it as well, you devs are more than capable and by no means should you feel this is under a time-constraint but set your volounteer goals and stick to it, or allow new devs to step in.

If CM9 proves to be a challenge, and you weren't able to progress much, might I suggest you make sure you've made the jump from the 2.6.7 kernel and move on to making yourselves the 3.x.x kernel? You'll be able to use it on ICS and it will prove helpful for Jelly bean 4.1.2/CM10..

CM10 will be yet again another task for you guys, although imo, crucial if you plan on fixing CM10.1

Again, this is just an observation and I did not research for the possibility that you guys may already have a mostly-working 3.x.x kernel. I sure wish I could help you guys, I know the brains that would assist, and I have the pc power to give it a shot, but yeah. I hope you guys have your testers giving you logcats.

Good luck guys!

GS4G Devs working on CM Builds, pm me what you're doing to help, what you guys are stuck on, and I'll forward it to the appropriate geniuses who have already dissolved those issues on different variants of your phone myself.

I wish nothing but the best to all of you, you have a sweet phone, and you all deserve official CM Support like the rest of us.

Note Bene: FYI, your Heimdall One-Click solution is useless on 64-Bit setups unless you go through the hassle of using Heimdall FrontEnd. Also, I suggest you update the stock tar of your latest GB Odin, while unreliable for some, we should not be left to dry with just a download link from the outdated multi-upload site. I had to dig deep to find an odin tar that worked for this.
[Samsung Galaxy S (4G Model)] itzik2sh:
Heimdall works perfectly on my 64bit windows 8. I know only on an Ubuntu issue.

sent from me
[Samsung Galaxy S (4G Model)] eollie:
No heimdal one clicks work fine on 64-bit ubuntu. Now with the updates ubuntu could have broken a function but 12.04 was working fine for me.

This post will be met with a lot of hostility, so be prepared. There is limited people working here since this isnt a very popular phone. Some people share everything while others keep everything they can to themselves. Its a good stepping stone phone and is capable of running JB. But there are plenty other devices with more developers and rom porters. Most people get this phone because its the best phone offered for the monthly 4G plans. Not sure what T-mo is offering now but a year ago this was the only phone with atleast a 4inch screen they offered for the monthly prepaid plans.
[Samsung Galaxy S (4G Model)] Shinydude100:
No dice on Windows 7 64-Bit. All proper drivers installed? Check. Brand New Cable used? Check. Odin (while rare) worked better for my new laptop. (All 3.0 ports) which may not be a factor, but yeah.

I see, and yes, its not meant to be taken as ordering around or anything, I'm just a bystander from a different section who has seen and closely followed progress of development and as I see how fragmented your android development section seems to be, it just seems like something to post as an observation. Mostly 2-3 people got our phone to official cm support status, so don't feel discouraged guys. Your devs could always reach out to the other dev community for direction, but anyway I hope you guys get official soon.
[Samsung Galaxy S (4G Model)] eollie:
If you cant get it to work on windows7 64 look at lumin30s guide. He has a program that will remove any samasung drivers so you can install the ones from heimdal. It sounds like that is the problem. Also make sure you are not using the same port for heimdal as you did for odin.
[Samsung Galaxy S (4G Model)] Theraze:
Yeah... Heimdall works for me on 64-bit Windows 7 and Windows 8 both. So if it doesn't work for you, it's something on your setup, not an issue with Heimdall itself.
[Samsung Galaxy S (4G Model)] GFX.myst.:
just so you know, use the usb ports on the back of the pc. the ones on the front have been known to cause problems and not recognizing the device. that is of course if you are trying to use the front ones. ;)

sent from within pure darkness
[Samsung Galaxy S (4G Model)] Shinydude100:
I used and troubleshooted with different ports, it just is so stubborn. I'll take a look at it. It's weird because I've used Heimdall before.

It's got to be my setup then, although, just the fact that I had the samsung drivers, it being properly recognized, and then heimdall not recognizing it sure fooled me at who to blame.

Oh dear, I don't think I've used a desktop for programming/flashing (nothing wrong with that though). All of it on laptops.

By the by, it sure did seem easy to blame heimdall everything else checked out. Although I've already odin'd the T959V phone, I'll still check out the guide. I'll run some command lines and uninstall everything that has to do with android to see if that may allow Heimdall to recognize it in download mode.
[Samsung Galaxy S (4G Model)] Theraze:
Mine is on laptops as well. And note that with Heimdall, I believe it was supposed to be using the drivers from Heimdall (from zadig) rather than from Samsung. Believe I'm using the WinUSB driver type. :) Hope it helps. Also, remember to reboot after installing...
[Samsung Galaxy S (4G Model)] Shinydude100:
Explains why I figured front-end heimdall worked fine (usage of zadig) as opposed to the packaged version. Makes sense. New laptop so zadig was probably not a priority in my work apps. Lol thanks.
[Samsung Galaxy S (4G Model)] eollie:
The SGS4G is a real finicky phone things that work for other samsung phones just fail on it. Most of the time it is a driver issue. And for a select few they just cant use heimdall.

Again my response above the SGS4G is a real finicky phone. I even think AdamOutler mentioned it in one of his posts/videos at how super finicky it is. I know I avoided it for so long because the first couple times I tried it it would fail. Ive helped a couple people that just could not get it to work on their laptop. Most people that have issues are using laptops and for some reason there is nothing that can be done to get it working. You might fall into that category for this device.
[Kindle Fire Q&A, Help & Troubleshooting] LambdaCalculus379:
Hey all,

I'm trying to root a Kindle Fire running 6.3.1. I have downloaded FireFire Fire 1.3 from http://xdaforums.com/showthread.php?p=23492717 and am following along with the instructions on that thread to get FFF onto the device. I'm running this install from

Mac OS X 10.7.5.

The command given is as follows:

From stock bootloader:

fastboot -i 0x1949 flash bootloader u-boot.bin

With FFF installed:

fastboot flash bootloader u-boot.bin

Running the former, fastboot tells me <waiting for device>, but nothing else seems to be happening. adb sees the device, giving me this when I run 'adb devices':

List of devices attached
56F6000600000001 device

However, I have noticed a repeating pattern in my kernel logs. Here is an extract of what I'm getting:

Jan 18 20:54:03 gallifrey kernel[0]: USBF:	387094.126	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:05 gallifrey kernel[0]: USBF:	387096.179	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:06 gallifrey kernel[0]: USBF:	387097.206	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:07 gallifrey kernel[0]: USBF:	387098.236	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:11 gallifrey kernel[0]: USBF:	387102.360	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:12 gallifrey kernel[0]: USBF:	387103.387	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:13 gallifrey kernel[0]: USBF:	387104.414	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:14 gallifrey kernel[0]: USBF:	387105.444	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:15 gallifrey kernel[0]: USBF:	387106.475	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:16 gallifrey kernel[0]: USBF:	387107.507	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:17 gallifrey kernel[0]: USBF:	387108.536	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:18 gallifrey kernel[0]: USBF:	387109.564	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:20 gallifrey kernel[0]: USBF:	387110.595	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending
Jan 18 20:54:21 gallifrey kernel[0]: USBF:	387111.626	AppleUSBOHCI[0xffffff800b019000]::SuspendUSBBus Processing WDH before suspending

What it looks like to me is something might be timing out, either the device or fastboot itself. I can send commands via adb, but nothing works through fastboot. Running 'fastboot devices' gives me no listings of any sort. I can try again on a Linux box later on, but would any OS X users have an idea as to why fastboot isn't working properly here?

Thanks to all. :)
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
Why not just use this method http://xdaforums.com/showthread.php?t=1443071 .The bootloader you are attempting to install is obsolete 1.4a is the newest.
[Kindle Fire Q&A, Help & Troubleshooting] LambdaCalculus379:
Thanks for pointing this out. I'm trying this method now, but I'm now running into another obstacle. I'm following the directions very carefully, but now even at Step 1, fastboot seems to have gotten stuck here:

Pushing fastboot mode by Pokey9000
-----------------------------------------------------------
-----------------------------------------------------------
-----------------------------------------------------------
-----------------------------------------------------------
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
2449 KB/s (510876 bytes in 0.203s)
Sleeping for 15 Seconds
Flashing bootloader (fff 1.4a)
ERROR: could not clear input pipe; result e0004051, ignoring...
ERROR: could not clear output pipe; result e0004051, ignoring....
sending 'bootloader' (243 KB)...

And the KF is simply sitting at the Kindle Fire logo and appears to be doing nothing. It's been like this for a few minutes already, and I don't want to stop the process or pull the plug.

Ideas?

EDIT: Never mind; it's working! :)
[Samsung Galaxy Nexus] hazmattt:
My heading on GMaps is always at least 45 degrees off, sometimes the complete opposite direction.

This only happens of I'm stationary. Once I start driving, it then figures out which way I'm heading.

Is this an issue with the GPS or other calibration? I tried that funky "wave it around in a figure 8 trick" with no luck.

Thanks

Matt
[Samsung Galaxy Nexus] simms22:
try giving the device a few firm pats on the battery cover.
[Samsung Galaxy Nexus] namtombout:
Best advice ever lol. If that doesn't work try a different kernel
[Samsung Galaxy Nexus] simms22:
my g1 would get "stuck" showing the wrong direction, way back when. a few firm pats on its back always fixed it :)
[Samsung Galaxy Nexus] hazmattt:
I guess I should try blowing on the cartridge too?
[Samsung Galaxy Nexus] hazmattt:
Are there any other possible fixes I could try?

Thanks

-

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hazmattt:
Anyone?

-

Sent from my Galaxy Nexus
[Galaxy S III Accessories] cadetgusv:
I recently bought the dongle and have had a issue with audio. I connected it first to my phillips lcd display. its a older model flat panel tv about 6 or so years old. I first got no audio until I switched over hdmi ports then I was able to get audio. I tried it next on my New TCL lcd display and it worked great. I then went back to the phillips thinking maybe it was a issue with the connection the first time, no luck I got audio briefly but lost connection and also lost audio when it did connect. So I am guessing since it works fine with my newer model tv that if you do run into this issue that it will be the tv not the dongle. Please update me if you find this do be wrong or find a solution

good luck thanks for having me on your forums
[Galaxy S III Accessories] Rikmk90:
Hi,

From what i remember there was an update posted on google play for the all share app, this was meant to fix audio issues if i remember correctly. Try going on google play and checking for updates. Personally i don't use it, but its just a thought.
[Galaxy S III Accessories] cadetgusv:
As far as I know I am up to date I looked into the update 2lj I believe and I have it already. I am not really looking for a solution b/c I have troubleshooted and I am pretty confident the problem lies with the tv. I am putting it out there b/c I know for some running into this issue it is very annoying and there seems to be no resolutions out there so I figured I'd post up for people on the search . If there is a solution I would like to hear it though so thank you for the reply
[AT&T, Rogers HTC One X, Telstra One XL] opto_isolator:
I do the two restores, and it boots up into the bootloader screen. I press any key on the keyboard, and it says "getting CID" and "waiting for device" and doesn't go any further. I can reboot the phone just fine, but I can't get it go any further then this. Any ideas?
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
do you have the required drivers installed for your phone?
[AT&T, Rogers HTC One X, Telstra One XL] opto_isolator:
never mind - installed HTC sync from the phone and it worked. so I watched the video, and got all the way to permaroot - I ran the permaroot, but don't see any sort of menu come up like in his vid. How do I get the permaroot to work???
[AT&T, Rogers HTC One X, Telstra One XL] opto_isolator:
OK - got it to work....the vid that he posted wasn't very intuitive since it was made for a different phone. Have to go to recovery mode.
[Samsung Epic 4G Touch] bobtsunam:
Had the e4gt for about 4 months now and all of the sudden, my 32gb SD (or any SD) will show up on my external mount. Posting on here to get some ideas of what to try hoping that its not a hardware issue.

What I've done so far:

- I've formatted the card several times on my phone and on my laptop.

-Odin'd back to stock and rerooted on a different rom.

-Tried different SD cards

Still, no luck. :confused:

Any help would be appreciated. Thanks in advance.

Edit: Solved easily with the suggestions below. Ribbon cable wasn't loose, but it didn't have a good connection apparently. Disconnected and reconnected the end of the ribbon cable for the SD cradle that plugs into the main board. Took a couple of tries but my SD card is available once again.
[Samsung Epic 4G Touch] graydiggy:
Sounds like you have a bad slot. It is an easy fix. You can get a new cradle online. I would try to see if the flex cable came loose though.
[Samsung Epic 4G Touch] xDecapitator:
I agree. Lucky for you, SGS2s are extremely easy to disassemble. Check eBay for replacement SD slots. They are dirt cheap.
[Samsung Epic 4G Touch] bobtsunam:
Re: [Q] SD Card not mounting

Sounds like this might be a semi-common problem. Thanks guys. Will check back when I figure it out.

<Blaze One>
[Samsung Epic 4G Touch] bobtsunam:
Re: [Q] SD Card not mounting

Issue solved. Took the phone apart and fiddled with the SD cradle connector on the main board. Took a couple of tries but it worked. Thanks for the help people.

<Blaze One>
[Defy Q&A, Help & Troubleshooting] cosaki:
Hiho,

go to the problem:

I changed the original rom to CyanogenMod (NIGHTLY EUROSKANK [21/12/12]). used one month, until one day I was playing, and the battery was low, so I left him there, went to sleep. I woke up, and he was discharged and placed in wall charger, and went to watch. some hours later, I tried to turn on, and nothing happened, I thought I plugged the charger in the wrong way, I put to charge again, and noticed that out instead of white LED appears, was the red led. Loading left for some hours, I turn on and nothing happened .. (@! #! @ # $) And then plugged in the USB, and lit the white LED, and could not access it.

I did the MacGyver method, to bootloader battery, and did SBF flash:

" JDGC_U6_2.12.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANGCCORE_P013_A033_HWp3_Service1FF.sbf ", was all right for some time, when I put it to charge and lit the red light again, and then pulled the plug, and he hung up. and is now well. and no more MacGyver mode solves the bootloader

Please help

Sorry for the horrible english, I'm using google translate.:silly:

And also the huge text (I would explain how it happened)
[Defy Q&A, Help & Troubleshooting] cosaki:
can someone help?
[Defy Q&A, Help & Troubleshooting] woodman:
Hi,

Sorry but in case you don't know, when the phone is discharged (under 7 or 10%) and when we plug it, it's normal to have red led. But you must have the "battery charging animation" with percentage when it charges... When it's charged enough (above 7 or 10 %) you can turn on the phone (power button long press).

Your battery could be dead, yes... But :

How old is your battery ?

Have you checked your wall charger ?

Is your USB cable charges your battery ?

Is your battery charges well with your original SBF (without CM) ?

If you know someone else who owns a Defy, you could test with his battery and his wall charger....

Your USB connector could be damaged....

Need some more informations to help you....
[Defy Q&A, Help & Troubleshooting] cosaki:
the cell completed one year this month (January / 13). I know that when the led is red because it is very low on battery. But let Loading 4 hours +. and when I connect to the computer it does not charge. it only illuminates the white LED, and can not connect or power on. anyway, the exchange led to suppose that shows the usb part is okay. I've used various chargers.

I can not run the SBF, why he does not recognize.

The phone is not turning on. apparently only led.
[Defy Q&A, Help & Troubleshooting] woodman:
Re: Defy Battery dead?!

Try another battery... Your system could be corrupted, I mean, it seems your phone can't charge in 0-7 % step, so it will never boot... Dunno why, it could be an issue even if I don't really think so... But, to save your phone it's the better thing you can do. Couldn't you borrow someone's Defy battery ? A friend ? A shop ? Then you could test !

Sent from my Defy MB525 green lens
[Defy Q&A, Help & Troubleshooting] cosaki:
I got a battery from a friend, who possesses defy red lens, same as mine.

nothing. still does not power on.
[Defy Q&A, Help & Troubleshooting] woodman:
OK

Did you try to unbrick your phone with this thread ?
[Defy Q&A, Help & Troubleshooting] cosaki:
I can not because the phone only comes in the boot when it is plugged into the wall charger. when I connect usb, it only illuminates the white LED. and I can not get into the boot or do anything.
[Defy Q&A, Help & Troubleshooting] woodman:
Are you sure you can't do any of these two steps (3 or 4) of the "bricked defy Step by Step Walkthrough" thread ??

Even the 4th ?

[...

3.First shutdown your phone, hold the Vol down and boot the phone up keeping the volume down pressed. you should come up to a triangle android logo, press the vol up and down key and then tap the screen ( this is a touch screen gui), choose the wipe data/cache and press ok, this should take up to 5 minutes.

4. Now, shut down the phone (pull the battery out and return it back in), Hold the Vol Up button and power up your phone.

you will enter the Bootloader (or BL as its called in the forums) and you should see the phone stating that (usually 9.10 version)

...]

If not, even with a charged battery, I 'm afraid your defy has a hardware issue...

Is your power button still alive ?
[Defy Q&A, Help & Troubleshooting] cosaki:
Power it on, when connected to wall charger. sometimes starts, sometimes they're showing is charging (the battery symbol with percentage in the middle). but I just pull it off. ie power on it, just in wall charger.

if a hardware problem it would not mind at all. (I think)