yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] scryan:
How is it only worth $200? By what measure? Can you get one for $200? Could you get a regular S4 new for $200? $300? $400?

Nope, not with out signing a contract to have someone else pay the rest for you. Thats how subsidized phones on contract work.

It's like Verizon owns part of your phone because they do. Because you didn't pay for all of it. Notice how the cost to cancel a contract is similar to the difference in price of the subsidized phone and retail cost?
[Verizon Samsung Galaxy S 4] jamesd1085:
I have seen soooo many attempts to get a company to unlock bootloaders/release source code through the petitions... Not once have I seen success... Our best chances come through our devs...Verizon/Samsung don't care about petitions
[Verizon Samsung Galaxy S 4] Evocm7:
I know you can't get one for 2-400 off contract. What I was saying was that the off contract price is ridiculous. Most people don't want to spend $800 dollars on something that should only cost 2-300 dollars. Alot of us need that extra $500. I don't object against an unlocked developer edition, just the awfully high price tag
[Verizon Samsung Galaxy S 4] richii0207:
If you can't afford it, then you can't get it. I would like a Ferrari but I'm not going to start a petition for lowered prices or another company to pay for some of it.

If you can't afford it, then don't get it...you have to pay a premium to enjoy
[Verizon Samsung Galaxy S 4] Chitala383:
I don't think I've ever heard a more true statement :good:
[Verizon Samsung Galaxy S 4] Evocm7:
I guess I'll be joining the crazy people someday then. It just angers me that something so cheap is so over priced. :banghead:
[Verizon Samsung Galaxy S 4] douger1957:
The average unsubsidized phone costs about $500. You do understand what "unsubsidized" means, don't you?

Almost a year after introduction, this phone is still a top of the line product. The notion that this phone should retail for ~$200 is not grounded in reality.
[Verizon Samsung Galaxy S 4] scryan:
Its basically a computer. How much for a laptop with a 1080P multitouch display, quad core processor, GPS unit, ect...

You cannot even match the specs of an S4 with a full sized laptop for $200... and that is before you make it fractions of an inch thick and throw in a 13mp camera.

I'm with you. Its awesome to be able to hack your cellphone and do whatever you want... but that is not the intention and not what you are owed its just something you have managed to take advantage of until this point. Now it seems that if you want full access to your cellphone, you have to pay full price for it... and as long as you ask Verizon to pay for part of it, they will have some say.

I don't like it, and I will circumvent it when I can... But its reasonable.
[Verizon Samsung Galaxy S 4] Surge1223:
You know what irritates me? What's the difference between a dev s4 and retail? Do you guys know? I do. It's literally 80-some characters of code in aboot. So there going to charge 500 dollars more for 80 characters? You gotta be F 'ing kidding me.

So they're worried that people with unlocked bootloaders are going to file more warranty claims and that will lead to more expenses for them right? Any one who had half a brain would just dd an aboot from MDK onto their device and hard brick it and since they technically were flashing an unmodified stock factory signed partition they wouldn't be in the wrong doing so. That is to say Verizon can't blame you for bricking due to trying to run custom software.

If we had an unlocked bootloader there would be less bricks because we'd have more freedom to be able to bring devices "back to life". Qhsusb_dload wouldn't be an issue if secure boot and Knox didn't have to be there as royally PIA roadblocks.

This is all about Verizon wanting more money and overcharging for devices and Samsung could care less because they get more money out of the deal as well. Sorry I just hate when people defend carriers and their "developer devices". If you think about it, the VZW developer edition S4 is no different than The i9505 or S4's on any other carrier not named Verizon or AT&T.

[/rant]
[Verizon Samsung Galaxy S 4] richii0207:
You can brick an S4 with the locked BL? I've seen MANY people brick devices with unlocked BLs.

You also have to realize that others manufacturers are now starting to offer dev editions like motorola.

For some reason the s4 has more drama about it than the moto x.
[Verizon Samsung Galaxy S 4] tech_head:
I haven't seen that many devices with unlocked bootloaders bricked.

I have seen plenty with locked bootloaders bricked.

On the other hand, I paid retail for my phone. Once out of contract the difference between developer and non-developer is nothing except a locked bootloader.

Once the device is completely paid for, then what is precluding, treating a device like a developer device when asked?
[Verizon Samsung Galaxy S 4] Surge1223:
You can easily brick a device with a locked BL. With root and adb shell and/or terminal. dd'ing aboot from MDK on any build after MDK will leave you in qhsusb_dload mode ( hard-bricked on the s4, other devices can still recover from qhsusb/qdl dload mode though). Recovery from qhsusb_dload on a locked BL is still doable but difficult without JTAG. Most people who think they've bricked their device haven't actually bricked their device.
[Verizon Samsung Galaxy S 4] ryanbg:
Good information here. Also, if you are using a tool like Heimdall, if you flash anything signed (TZ for example) to SBL1 (for example), because the signature is still correct it will flash right over it. Meaning if you flash anything over SBL1, RPM, or ABOOT you are done. That's how I permabricked my device. Especially RPM and SBL1. Especially especially especially a couple more times RPM.
[Verizon Samsung Galaxy S 4] cybertec69:
The reason is the developer edition is Not subsidized "you pay full retail price for the device" same would go if you did not want to be tied down to another two year contract with the carrier you would have to buy the phone outright, what here do you not understand.
[Verizon Samsung Galaxy S 4] Surge1223:
I don't understand why in the hell Verizon and Samsung think they can sell a $650 dollar unsubsidized developer edition device at the same price they sell the retail locked down unsubsidized GS4. T-mobile, the international edition and other carriers offer a retail GS4 that does the same thing as the developer edition GS4 and they offer it with a 2 year agreement so its also at a lower cost. Basically, what I don't understand is who the hell does Verizon think they are? I intentionally help unlock tethering on all devices I can just because they piss me off.
[Verizon Samsung Galaxy S 4] myfishbear:
lol Verizon is a company based in basking ridge NJ... do you know how corrupt my state is? it is where the sopranos took place lol.
[Verizon Samsung Galaxy S 4] tshelby73:
I have given up all hope.
[HTC Droid DNA] trinity343:
So today while i was listening to music via AmazonMP3 in my car through the radio, it was also plugged into the charger. the phone went idle and turned the screen off, nothing abnormal here, however, this time when i went to turn the screen back on it would not. music was still playing and the orange charge light was on.

This happened twice today. the first time i was able to hold down the power button and force it to reboot. the second time it won't even do that. i hold down the power or hold down power+vol down/up and nothing happens. not even the buttons flashing. i've gone to the point of holding them down for 2 mins just to see if long term holding may somehow do it.

when i got home i plugged it into the computer to see if the computer would recognize the phone and to see if i could force reboot it using ADB. the computer did not see it and i tried ADB devices and it did not see it either. i'm basically at a loss at this point and any ideas would be welcome

little about the phone

running Viper 2.0.3 with S-off
[HTC Droid DNA] trinity343:
well the LED just turned of... so i went and plugged it in to see if it would come back on and boot up.

neither the charging light or the phone came on....do i now just have a paper weight?
[HTC Droid DNA] sdamark:
Have heard a couple people say to leave it on charge, whether the charge light comes on or not, for 24 hours. Then try to reboot.

Hope you get it figured out. Good luck. :fingers-crossed:
[HTC Droid DNA] trinity343:
i'll give it a try... hopefully that'll work.... if not, guess i'll be going to Big Red on wednesday to see if i can use my Wife's upgrade early (it's due in march) since she's happy with her phone (dumb/flip phone) and isn't interested in using it
[HTC Droid DNA] trinity343:
ok after letting it sit off the charger for a couple hours last night i plugged it in to start t he 24 hour charge and the charge light started flashing like it would normally to let you know of low battery. after about a minute this didn't change but i took the chance and attempted to turn it on. which it did come back on at this point. however, it didn't have enough charge to stay on since the charger is not a fast charger and wasn't giving more then it used. it shut back off. i unplugged and replugged and this time it flashed and then turned solid. turned the phone back on and it stayed on without issue.

this morning it was still coming back up. though i have had one instance where it didn't today but i was able to force it off by holding the power button.

i went ahead a few minutes ago and updated to viper 2.5 and i'm hoping that the reload will correct the issue... guess we'll find out

Thanks for the help!
[HTC Droid DNA] trinity343:
though now i'm getting errors in Viper tweaks... to the Viper forum!!
[HTC Droid DNA] thayl0:
Post your errors in the venom thread.
[HTC Droid DNA] trinity343:
i did.... the original error this post is about isn't venom related. it's hardware. once i reloaded/updated to the latest venom i was getting something different.. thus why i said 'To the Viper Forum!" on my last post :)
[HTC Droid DNA] trinity343:
well at this point i'm saying it's a hardware issue. after i updated to 2.5 (and got the viper tweaks error resolved) i'm still having this issue. even had it this morning without it going screen off and i was looking at it this time when it happened. what it did was the screen just looked like it currupted the image with vertical lines and everything went grey as it was fading out. and then the charge light stayed on again. at least this time i was able to force it off again and turn it back on.. but yeah. i'm going with hardware issues. i'll probably go to Verizon tomorrow or this weekend and ask if i can take my wifes upgrade 1.5 months early. it'll be nice if they let me.. though now i need to figure out what i'd want to get..choices...
[HTC Droid DNA] sdamark:
Too bad about your DNA. Personally I kinda like the One Max. Nice big screen and expandable memory.
[HTC Droid DNA] trinity343:
expandable memory is always nice!

though i'm also looking at the LG G2. my dad has one of those and it's been great. the 3000 battery is nice, as is the 13 MP camera...i'll just have to compare and see which one i like better over all. price may play a part as well since right now the G2 is $50 while the One Max is $300....

just looking at them compared though. the One Max doesn't have as good a processor as the G2. 1.7 GHz vs 2.26 Ghz (both quad). i suppose a take the good with that bad would come on either phone since the G2 doesn't have expandable storage.

also... i'm not sure i'd want a phone that size. 5.5 would probably be the largest i'd want. i'll hold it when i go to the store. maybe i'll find it more comfortable then i think...
[HTC Droid DNA] thayl0:
You can't really tell the different in speed. Its actually been proven the HTC one max load webpages faster,
[HTC Droid DNA] trinity343:
yeah i wouldn't think it would be to noticeable. but you know..MORE POWER!! ha ha. it may come down to price being what makes the decision for me really...
[HTC Droid DNA] thayl0:
Go with s4 or note 3 if your a samsung fan
[HTC Droid DNA] trinity343:
i've never actually had a samsung phone, either as a dumb phone or a smartphone. i've had a OG Droid, Xperia play and the DNA and that's it so far. one of my co-workers is trying to convince me to go with the note 3 since that's what he has. but i don't really want a phone/tablet. it wouldn't fit in my phone pocket that's built into my pants :)

i've rooted and unlocked samsung S2 before. but that's about it....
[HTC Droid DNA] Jaggar345:
I had a Samsung phone for 2 years and hated it, it constantly froze and I had to do a battery pull daily. There was also little development for it though u doubt you will have that problem if you get the note 3. After owning that phone for 2 years and then picking up the DNA I have become an HTC fan. I had a Samsung continuum. Jut my little rant about Samsung.
[Captivate Q&A, Help & Troubleshooting] LanreLogic:
I have checked all the related Q and A's and none of them seem to fix my problem. My brother's Samsung Captivate I896 Rogers was rooted with running CM10.2 but it kept crashing no matter what Gapps I installed or factory reset so my brother decided that he wanted to go back to a Stock Rogers Rom. While trying to do this with the ODIN one click App the USB accidentally came out and now the phone is stuck in Download mode and even though Odin recognizes the phone. None of the bootloaders work and Odin is hanging every time on "Setup Connection". If anyone could tell me how to fix this it would be much appreciated. Thank You.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Flash the non-bootloader Odin kk4 from this post: http://xdaforums.com/showpost.php?p=18370912&postcount=3

It doesn't have to be the Rogers' one. As for Gapps, Usually the correct one to flash are in the thread's OP.
[Captivate Q&A, Help & Troubleshooting] donnasbrt1:
I also had this problem , what worked for me was remove the battery , couple minutes , insert back in ,open odin , have it ready to go at this point , button combo , or jig to download , as soon as odin sees device , start flash , a one click back to stock would be the better way to go , start with a clean slate and all

captivate i896 , cyanfox 2.0.2

---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------

woops , double post

LanreLogic

I also had this problem , what worked for me was remove the battery , wait couple minutes , insert back in ,"

open odin

" , have it all ready to go at this point , use button combo , or jig to download , or any way you can get there lol

as soon as odin sees device , start flash , a one click back to stock would be the better way to go , start with a clean slate and all

captivate i896 , cyanfox 2.0.2

( softbricked , many times )
[8125, K-JAM, P4300, MDA Vario General] agent_lead:
how do i disable this annoyance??

i cant use my phone at all while on a phone call other then to talk...cant browse thru my contacts...emails..nothing..cause this annoying pop up keeps popping up saying it cant connect..

there mst be something in the registry that can fix this..

please advise..
[8125, K-JAM, P4300, MDA Vario General] agent_lead:
no ideas?

noone ever has this problem but me??

i wonder if its some software im using like implus or somthing trying to connect
[8125, K-JAM, P4300, MDA Vario General] jberylec:
Old topic, but here ya go anyhow...

Start > Settings > Sounds & Notifications > Notifications Tab > Pull down menu and choose "Connection Established" > Uncheck "Display message on screen" > Press "Ok"

This gets rid of all GPRS connection status popups! (It worked perfect for me and others atleast)

:)
[Verizon HTC One (M7)] wickedcheeselover:
Ok, So being a total a noob that I am, I attempted to get google edition ROM using a tut called How to Convert Any HTC One into a Stock Google Play Edition with Bootloader, Recovery, & OTA Updates. I can't link sorry, not realzing it's only for GSM phones. I just changed the model ID in android-info and didn't think and changed my CID. Tho, when it finished flashing, it stayed at 100%, so I just turned it off and went into bootloader. Then, I went into recovery to fix it, and it just boots into google edition. So, you're thinking WOOOO! Unfortunately, not the case. I was put into a boot loop, so I just turned off my phone, went back into bootloader. The problem is, I can't do anything without a boot loop, besides going into fastboot. I have successfully changed my CID back to VZW__001, but when I try to flash cyanogenmod(what I was using before) it says C:\Users\(My name)\Desktop\sdk\platform-tools>fastboot flash zip C:\Users\(My Name)\Downlo

ads\cm-10.2.0-m7vzw.zip

target reported max download size of 1526722560 bytes

sending 'zip' (192433 KB)...

OKAY [ 8.808s]

writing 'zip'...

FAILED (remote: not allowed)

finished. total time: 8.843s

:( Now I'm brick. Brick Tamland. Will someone please help me?
[Verizon HTC One (M7)] mmuzzy:
Install a custom recovery like: http://xdaforums.com/showthread.php?t=2416431 then

ADB copy the CM ROM to the phone and install it using the custom recovery.

You're obviously s-off and unlocked so whatever you do keep it that way. There are decrypted RUUs that you can use in the forums if you need to get back to a working state and then you can go from there.

EDIT: You said you were using CM before. I'm not sure if you lost your recovery using that tutorial. If you reinstall your custom recovery (TWRP or CWM), that's where you want to reinstall CM from.
[Verizon HTC One (M7)] wickedcheeselover:
Skrewy Rom?

So this rom was a RUU for the google edition, so it replaced my bootloader and deleted CWM. Unfortunately, factory reset in bootloader, flashing zips, backing up or restoring in CWM do not work because of this weird rom. I have a RUU downloading from htc1guru(google it and find 1.10.605.10 Verizon RUU Zip) and it said it was decrypted. Does this mean that I have to encrypt? Or would I just fastboot oem rebootRUU and then flash the RUU? Also does bootlock need to be on or off when flashing?
[Verizon HTC One (M7)] DEFNUB:
not sure what boot lock is, unlocked boot loader?, if you run the ruu I thinknyou need to be in fast boot is all
[Verizon HTC One (M7)] wickedcheeselover:
Unlocked Bootloader

So ya that's what I meant unlocked bootloader. There is not an exe file I can find for RUU verizon HTC one. If u can find on that'd be awesome, but for now I have to download this RUU and try to flash it. I will update when I flash it, but it's a big download so it won't be soon.
[Verizon HTC One (M7)] wickedcheeselover:
Fixed it!

I successfully flashed that RUU and my one is back up and running. Thanks xda!:good:
[Nexus 7 (2013) Q&A] situman:
How are the tablets bought in the new yr? Does it still have screen issues like us early adapters?
[Nexus 7 (2013) Q&A] z0phi3l:
My first run N7 2013 has no issues at all
[Nexus 7 (2013) Q&A] situman:
I guess I should clarify the question is for people that bought theirs very recently like in Dec/Jan timeframe
[Nexus 7 (2013) Q&A] z0phi3l:
My point is that like everything else it's more than likely you will get a good device, the percentage of bad devices is always low, forum posts aside
[Nexus 7 (2013) Q&A] gnotelover97:
I bought my Nexus 7 in December. I am not noticing any major issues so far. Although sometimes there are ghost touches after many hours of continuous usage.
[Nexus 7 (2013) Q&A] rik-sik:
after having mine for a month im noticing what i thought were just software issues.

Screen stops responding to touch randomly or takes ages to notice you have your finger on somthing

and loads of coloured splodges on the screen when showing a dark image !

grr !

i love it though but once you notice its hard not to notice!!
[Nexus 7 (2013) Q&A] Michealtbh:
Mine is just a couple of weeks old, it has difficulty registering touches when laying flat
[Nexus 7 (2013) Q&A] situman:
You would think Asus and Google would quietly fix the hardware on new batches. Probably a design issue that cant be easily fixed. Yes yes kudos to the ones that doesn't have screen problems.
[Nexus 7 (2013) Q&A] CarsonKT:
Have mine (LTE version) about a week or so, it sometimes fails to register touch when it's on desk.

but I notice another thing that , its back is not flat?? it can spin on my desk:confused:
[Nexus 7 (2013) Q&A] NekroWolfen:
Had this device since it was released, it had the screen issues(incredibly annoying on apps like PS Touch and the keyboard), now bought a Note 8, rapidly noticed the better screen responsiveness. I got curious about that too, I wonder if they fixed that for the new batch, I knew that not all flo devices had those problems but nevertheless still a shame if they haven't fix that by now.
[Nexus 7 (2013) Q&A] situman:
Based on the responses....apparently not.
[Nexus 7 (2013) Q&A] hughlle:
Mine had pretty bad issues when i first got it (initial release batch), the device was even crap enough that opening youtube app would hard reset the tablet every time. After the various updates that got rolled out, there is nothing wrong with my device. So they certainly fixed things for me following customer feedback.
[Nexus 7 (2013) Q&A] Viologen:
I bought mine back in December and it misses touches in the upper region of the screen unless it is ground with either you hands or the charger. I did a few experiments to try and fix it, one thing I noticed when I tied a thin copper wire to the USB port is that it only took a finger on that piece of wire to ground it out and it worked perfectly. My question is whether there is a ground source inside the device where I could possibly solder this wire to in order to ground it out (ie. Battery ground or something)
[Nexus 7 (2013) Q&A] demkantor:
First nexus 7 (2012) worked flawless for over a year, gave it to mother as she needs to learn technology and bought the 2013 in November

The non presses and random presses plagued me from the start of this one but I was naive and pretended not to notice, after a few weeks I did get annoyed and wanted my old one back! (But didn't) so being I needed mine for school I didn't want to RMA right away so I kept trying to find fixes for awhile longer. About 2 weeks ago I got fed up and was about to RMA it but then decided to just try the latest factory image (haven't used stock anything in a long time)

And well, haven't had one issue with touch since!

So to all with the common touchscreen issue I suggest trying pure stock KOT49H first along with bootloader, haven't had a chance to test any custom Roms for it yet as I've been too busy but I added twrp and rooted it and still zero issues so at least for me it has been fixed

Still one of the best buys out there, even with the 2 months of annoyances
[Nexus 7 (2013) Q&A] beanboy89:
I got my N7 2013 in early December. There's a small piece of dust under the screen, near the middle. I didn't even notice it until a few weeks ago. I can see it when I'm thinking about it, but most of the time I just ignore it or just fail to notice it.
[Nexus 7 (2013) Q&A] rtfm1777:
Got my N7 2013 at the end of January. No problems initially, then a few small annoyances with a crossword puzzle app that I was willing to blame on the small letterboxes. Yesterday it did a full freeze, no responses to any touches anywhere. A power reboot cleared it up. I could blame it on the 4.4.2 upgrade which I did pretty soon after I got it, but this thread leads me to believe I should be going for an rma.
[Galaxy S III Q&A, Help & Troubleshooting] zhuoxian:
Why my xda premium 4 ofen get force close .I am on mk6 stock ROM ,boeffla kernel. Everything is Ok except this. Anyone help?
[Galaxy S III Q&A, Help & Troubleshooting] kadir456:
Did you buy it, or use a cracked Version?

Device: Samsung Galaxy S3

ROM: CyanogenMod 11 (Temasek Unofficial V30 )

Kernel: Boeffla-Kernel-CM11-2.1-Beta9-
[Galaxy S III Q&A, Help & Troubleshooting] jukyO:
I'm using normal version, free one. also crashes sometimes on latest 4.3 official stock.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Premium is paid for on Play .

Suggest standard practice remove and install again .
[Galaxy S III Q&A, Help & Troubleshooting] zhuoxian:
thank you,i try again