yashsingh1/xdaforums huggingface dataset:
[Moto 360] roccom33:
I noticed this myself right away my first day. It hasn't been distracting for me fortunately, Android Wear definitely needs a car mode.
[Moto 360] lanwarrior:
Oh man, that is dangerous! I mean driving with bright light coming on your left side? Google needs to be notified of this. You should email Android blog site, like Android Central.
[Moto 360] dpwhitty11:
That is exactly how I drive.

It activates itself every now and then, mostly when turning. I don't really care though, at the end of the day, it impacts the battery by maybe 5%.
[Moto 360] Ozark_8125:
:svetius: :highfive: I second the motion to amend the complaint to confirm the agenda as proposed, all in favor of banning the bright light on the left side, say 'aye'! :crying:
[Moto 360] lanwarrior:
Can't tell if you're joking or not.. but driving at night with little street light (some freeways in the CA are like that) and have a full-blast white light coming suddenly is a distraction.

I had Llama on my Note 3 and configured it incorrectly and one time, it put the brightness at 100% (suppose to be 10% at night) and it's quite blinding when it happened suddenly at 75 Mph.

Of course, I don't have the watch yet (coming this week!), so I don't know how bright this is.
[Moto 360] dolebomo:
I just drove 1 hour on a road so twisty that it is impossible to go the posted 45 mph limit. At 4am, It's so dark you could see the milkyway clearly...my 360 turned on 3 times and two of them were when making 90 degree right hand turns. I wasn't bothered, but ymmv.
[Moto 360] Ozark_8125:
Change it to a black watch face.
[Moto 360] johnus:
Why not just mute the watch... That's what I do while driving.
[Moto 360] Stormbot:
Agreed

Yes and it is annoying. Everytime you turn the wheel it lights up. There doesn't appear to be a setting to change its behavior (though if you mute it at least notifications don't pop up at you).
[Moto 360] times_infinity:
This. Screen doesn't light unless you tap it.
[Sprint Samsung Galaxy Note 3] sothus:
That this is the Note 3 with sprint?

Samsung N900GRY-Gray
[Sprint Samsung Galaxy Note 3] jimzweb1:
Hopefully this will help:

Sign List Of Model Numbers for Note 3

Update:

SM-N900 - Exynos Version (International).

SM-N9005 - Snapdragon Version(International).

SM-N9002 - Snapdragon Double SIM(Chinese).

SM-N9005T - Snapdragon Version (T-Mobile)

SM-N900P - Snapdragon Version (Sprint)

SM-N9005P - Snapdragon Version (Sprint)

SM-N9005A - Snapdragon Version (AT&T)

SM-N9007 - Snapdragon Version (Optus)

SM-N900W8- Snapdragon Version (Canadian)

SM-N9000Q - Exynos Version(Turkish)

SM-N9000- Exynos Version(Supposedly International,but don't know the difference with n900)

SM-N900X -Snapdragon Version(Retail Live Demo Unit)

Still need h/w info of these:

SM-N9000Q_MEA

SM-N900K--(KT Telecom South Korea)

SM-N900L--(LGU+ South Korea)

SM-N900S---(SK Telecom South Korea)

SM-N900W8_LA

SM-N900_MEA

SM-N900_SEA

SM-N900_SWA

SM-900 - International Exynos

SM-9005 - International S800

SM-9002 - International Double SIM

SM-9005T - TMobile S800

SM-9005P - Sprint S800

SM-9005A - AT&T S800

SM-N900

SM-N9002

SM-N9005

SM-N9006

SM-N9007

SM-N9008

SM-N9009

SM-N900A

SM-N900D (SC-01F)

SM-N900J (SCL22)

SM-N900K

SM-N900L

SM-N900P

SM-N9000Q

SM-N900R4

SM-N900S

SM-N900T

SM-N900V

SM-N900W8

SM-N900X

Have not found anything with GRY yet, except a note 3 model for New Zealand. Not sure that's accurate, of course there's the Nokia n900gry.
[Sprint Samsung Galaxy Note 3] sothus:
Hmmm, When I did my insurance claim, Said they were sending me the Samsung N900Gry.... Looks to me like it's the international version. Issue with that is i live in the states.
[Sprint Samsung Galaxy Note 3] jimzweb1:
Maybe that code belongs to the insurance company so they know it was issued by them. Just have to wait and see what is in settings about device.
[Sprint Samsung Galaxy Note 3] sothus:
That's my plan. The the phone should be here in a couple hours.
[Sprint Samsung Galaxy Note 3] jimzweb1:
Did you mean 2hrs 14 min and 35 seconds not that anyone is counting !!! Lol Been there !!!
[Sprint Samsung Galaxy Note 3] sothus:
Lol yea counted down every min till it got here. And thankfully it is the sm-900p for sprint so lte works. But I guess to the insurance company gray means black lol.
[Nexus 5 Q&A, Help & Troubleshooting] const_char:
Hello! I built AOSP for Nexus 5 in eng and userdebug mode without issues. Everything is working. I just noticed that if I build in "user" mode the same sources the resulting image seems to be unable to create what is needed to get the external memory working. This results in many crashes obviously. It seems the system tries to create directories but fails and therefore it can't mount the external memory. This is what I get with logcat:

E [ 977] cutils Failed to mkdir(/mnt/shell/emulated/0): Read-only file system
E [ 977] dalvikvm cannot mountExternalStorage(): Read-only file system

Probably because of this many applications crash. Any idea why this happens? I tried 4.4.2 and 4.4.4 but still the same occurs: eng and userdebug are ok, user is not. How is it possible that the default sources generate an image with this issue? Anyone who successfully built the "user" image for the N5?

Thanks.
[Nexus 5 Q&A, Help & Troubleshooting] bitdomo:
I have successfully built "user" image without any problems. Did you do clean flash or you just dirty flashed the user image over userdebug or eng?
[Nexus 5 Q&A, Help & Troubleshooting] wulsic:
As far as I see, your internal storage, 0 folder/emulated is read only file system so you have to change the permissions of it.
[Nexus 5 Q&A, Help & Troubleshooting] const_char:
Yes, question is why the result of the build is like that only in user mode?
[Nexus 5 Q&A, Help & Troubleshooting] const_char:
I erased and flashed all the partitions one by one. This is the script I use when I don't use the update package:

sudo $1/fastboot erase boot

sudo $1/fastboot erase cache

sudo $1/fastboot erase recovery

sudo $1/fastboot erase system

sudo $1/fastboot erase userdata

sudo $1/fastboot erase radio

sudo $1/fastboot flash bootloader bootloader-hammerhead-hhz11k.img

sudo $1/fastboot reboot-bootloader

sleep 5

sudo $1/fastboot flash boot boot.img

sudo $1/fastboot flash cache cache.img

#sudo $1/fastboot flash recovery recovery.img

sudo $1/fastboot flash recovery recovery-clockwork-touch-6.0.4.5-hammerhead.img

sudo $1/fastboot flash system system.img

sudo $1/fastboot flash userdata userdata.img

sudo $1/fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img

sudo $1/fastboot reboot

Maybe I should do a clean build? I commonly have one source tree, and simply run lunch aosp_hammerhead-* and make. That seems to work for userdebug and eng, but maybe not to be done for user?
[Nexus 5 Q&A, Help & Troubleshooting] bitdomo:
Do make clean then lunch aosp_hammerhead-user then make

Also CWM recovery can cause the miss behaviour of the internal storage.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Why are you using sudo? if you mkdir using sudo, it would create the directory with only access to root user. Maybe this is similar?
[Nexus 5 Q&A, Help & Troubleshooting] const_char:
Didn't check the sources of fastboot, but I suppose fastboot only writes the bytes it finds in the images. fastboot must be run as root on my system because of the permissions of the usb device node. I didn't want to change those.

Now it seems to work, but I'm not entirely sure why... I changed the recovery as suggested but seemed not to work. Probably a wrong radio partition. I just tried not to flash it and the result is the same. So I was probably doing something wrong flashing the radio partition...

Thanks!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] novikyuval:
Hey,

I got my Galaxy S4 AT&T SGH-I337 as I337UCUAMDB, and ever since then was running cyanogenmod 11.

Recently after a stupid mistake (updating to a nightly, then to M10) I had to return to stock ROM, and on a CM dev's lead installed a NB1 ROM.

Since then, I wasn't able to install TWRP (installing it would make the phone boot only into download mode), and installing CM would produce constant "com.android.phone/acore/media" errors.

Right now I'm running Google Edition for SafeStrap (v1.1 - 4.4.4), which, TBH, isn't nearly as good as CM11 and still very buggy...

I read as much as I could about the whole AT&T GS4 bootloader situation, but still haven't understood it fully:

Could my bootloader have been locked by the update?

If not, why can't I install a custom recovery and CM again?

If so, is there anyway I can downgrade back to MDB (maybe from here?) Or to anything that can allow me to install CM again?

Thanks in advance,

Yuval.

Edit: If I can still use safestrap to install

any

custom ROM, why can't I install CM? (I did a clean install [full wipe] a couple of times, w/ and w/o gapps, to no avail) Or did I not understand well the safestrap custom ROM options?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RAID Xero:
Your bootloader was always locked, loki just exploited it.

You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.

No, you can't downgrade back. Sorry.

I would highly recommend reading before you make any major changes to your phone in the future.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] novikyuval:
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).

No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:

I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.

I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.

I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RAID Xero:
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] novikyuval:
Okay, I think I now fully understand this. Thank you RAID Xero and jd1639 for the help!

I guess I learnt my lesson to look into evil AT&T ROMs before updating to and from them :)

Also, too bad I never noticed any warning regarding this on Cyanogenmod's website (or maybe I just missed it)...

Thanks again, and unless there's a new magical way to bypass the locking, this thread may be marked as locked.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RAID Xero:
You're welcome, and happy flashing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dezhezzi:
Hi is there a way to root the i747m running stock 4.4.2? i used to root it with Towel Root but that does not work anymore, does someone know a way to root it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Use method 2 from here.

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

Be sure to read the last several pages of the thread as well.
[X 2014 Q&A, Help & Troubleshooting] mms678:
Anyone receive their order for the pure edition yet? Is the FCC ID IDHT56QA1 with LTE 2/4/5/7/17, or IDHT56QA3 with LTE 2/4/5/12/17/25/26/41?
[X 2014 Q&A, Help & Troubleshooting] knitler:
With the fact mine was built Thursday I'm guessing they are just holding the orders until the 24th to ship them.
[X 2014 Q&A, Help & Troubleshooting] wryun:
I just got my Pure Edition today and the FCC ID is IDHT56QA1
[X 2014 Q&A, Help & Troubleshooting] Al936:
Are you sure that it is IDHT56QA1 and not IHDT56QA1 ?
[X 2014 Q&A, Help & Troubleshooting] wryun:
Good catch, I didn't notice that. Sorry, it is IHDT56QA1
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lellobello:
I have two SIM card.

my personal phone is a Sony Ericsson K800i, excellent fun/night phone. I'm a un upgrade addict. No matter Moto or Samsung or SE, I upgrading every thing, I'm stick with Sony Ericsson mostly because of its update service.

After couples of Palm and Symbian phones, WM and HTC leadership was too strong to be ignored. In early September 2006, I picked up a an HTC TyTN undranded and unlocked.

Is that normal that in almost 5 months of market life (so at around its half life), Italy has never had a ROM update and I'm still using that Southafrican one?

What's wrong with HTC? Have I missed something?

Thanks
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] fone_fanatic:
Yah it is taking a while for rom updates and custom cooked roms. I just purchased my JasJam 2 weeks ago or so and when i log onto club imate they only show 2 roms available (both the same, just different ext roms) ones Arabic and the other is WWE.

Still patiently waiting for custom roms
[General Topics] drogers81:
I currently have a S5 but I know someone wanting to trade their M8 for an S5. My question is.....which device currently has more value? And which one will hold its value longer? I know Samsung is probably the more "popular" device out but the M8 sure seems to be more premium hardware wise. Wanting to hear your opinions to help make my decision. [emoji1]<br/>
[General Topics] NevekThaKillah:
That's a good question. I'm an M8 owner and love it but have heard the S5 is nice too. I would say the they're the same value wise, maybe the S5 a little bit more due to the higher megapixel camera but other then that it's really a user preference. I would stick with my M8 until another HTC device with better camera.
[ONE Q&A, Help & Troubleshooting] tohno:
Hi all

i Just got my one plus one last week

it was amazing , it was snappy , the screen is gorgeous , and the CM is plain great , albeit many apps did find unresponding oddly enough

i've had many phones in the past that are not so great x10 mini , x8 , galaxy ace, galaxy nexus

all of which are miles away when compared to the one plus

and since they are so freaking lag i decided to root them and gave them root and changed their bootloader

but from one phone to the other all of them seems to die out in about 9 months after i root them , and i don;'t know what i did wrong , most of them are dead because i fried the motherboard or something

still why would you root the one plus when it's already so fast ? i am considering rooting mine but i am really scared i might kill it
[ONE Q&A, Help & Troubleshooting] DANDANA:
First, rooting doesn't make it faster or slower. Also, it doesn't broke the phone neither now or in 12 month time.

Second, you need root for some in depth access on your phone, or some programs like Titanium Backup may require root to work.

Third, the rule of the thumb say, if you don't need it, don't do it!
[ONE Q&A, Help & Troubleshooting] thelestat:
greenify, adblock, titanium more than enough reasons to root.
[ONE Q&A, Help & Troubleshooting] WoodburyMan:
I go by the old saying "If you have to ask, you'll never know"

Generally anyone who's asked me if they should root their phone, or install 3rd party firmware, my answer is no. It has to be something you want to do and something you're willing to accept the risk doing. I'm a flashaholic. I flash a new rom every few days, or update existing ROM i have. I'm never content with the status quo on my phone and devices and always play. I accept the risk of running into a situation where I go to make a call, watch a movie, or open a email and my phone locking up due to running bleeding edge untested code. Mind you I can always recover from bootloader and know how so I know I won't permanently screw a phone, just until I can flash a older rom, or recover with a PC. If you have to ask, it means you're not sure about what you're getting into. If you fall into this situation I would refrain from asking others and instead read around in the 1,000's of posts in this OnePlus forum and decide for yourself.

Not that being said, root is simple. It's a more of a "Set it and forget it" type of deal, at least until a OTA update arrives. Custom roms is where the aforementioned comes into play mostly. If you want to start getting into the Flashing world with Android its the place to start. Myself I read and read after I got my Galaxy S4, first real Android phone, and went straight to CyanogenMod with it. Skipped rooting.
[ONE Q&A, Help & Troubleshooting] marinespl:
He may not be aware of what can be accomplished with root access and find the profits interesting. He doesn't necessarily know if he wants to do if he doesn't know it exists/is possible.
[ONE Q&A, Help & Troubleshooting] Gamm86:
I don't want to flame or anything, but since you've been around for almost 3 years, you should really know better.

Firstly, rooting does not fry your motherboard. Seriously, why would you think so? :p

The fact that your previous phones became slow after a short while is because you probably got them stuffed with bloatware and have not maintained your phone in a healthy way.

As to why you should root your phone,...

Well, most apps that help you maintain your phone and keep it as optimized as possible require root.

This kind of proves my previous point regarding the speed of your previous phones.

I would start reading some more and eventually you'll be able to answer your own question.

Good luck!
[ONE Q&A, Help & Troubleshooting] J_Dutch:
Well that's easy, if your not interested in using apps that need root access there's no use in rooting your device. It's nothing magic which will make your device fly or make a cup of coffee for you.
[ONE Q&A, Help & Troubleshooting] extrem0:
Why not?
[Galaxy S III Q&A, Help & Troubleshooting] xkons:
Dear xda community,

recently I've found a perfectly working Galaxy S3 in the trash, only the front glass was broken.

I removed it with the help of my heat gun and put a replacement glass on.

I'm afraid that the lcd somehow got damaged in the process.

Would someone be willing to take a look at this?

https://imgur.com/QitO8OX

I really hope I can fix this somehow with the help of you :highfive:

Thanks in advance

xkons
[Galaxy S III Q&A, Help & Troubleshooting] CoreyD97:
Looks like you had the heat gun too close / too hot / on the phone for too long.

You've damaged the LCD's and the only fix is to replace the LCD and digitizer pair.

Probably not what you wanted to hear, Sorry!
[Galaxy S III Q&A, Help & Troubleshooting] xkons:
thanks still. I guess I'll have to live with it since the whole lcd is not too cheap P:
[Galaxy S 4 Q&A, Help & Troubleshooting] Dark Blitz:
Hey Guys,

I'm quite new on the forums, so forgive me if I ask questions that have already been answered a lot. Yes, I've read loads about 'how to root the Samsung Galaxy S4', but I just want your guys confirmation about my ideas.

1. I know for a long time now that you can use the CF-auto root to root your S4. But I'm wondering if it still works after such an amount of updates. Currently my phone's build number is I9505XXUGNG8

2. After my phone is rooted, I would like to have CWM as my costum recovery. I know that a really easy way is to install the ROM manager app from the playstore and from there, flash the CWM recovery. Again I was wondering if it still works that easily for the S4

3. After my phone is rooted and has CWM, I think I don't receive any OTA updates anymore right? (even when I just stay on the official TouchWizz rom)

If I don't get these updates anymore then what is a good way to get the newest Android TouchWizz versions? Can I just use the official TouchWizz roms from Sammobile that will come out in the future?

Already thanks to everybody who comments on this thread!

I hope that I can teach other people also something new.
[Galaxy S 4 Q&A, Help & Troubleshooting] Dark Blitz:
Anyone?
[Galaxy S 4 Q&A, Help & Troubleshooting] tomtro74:
1. Yes

2. I'm not sure. I always flash first non stock recovery with Odin.

3. Yes, You don't get official updates anymore. If You use latest rom from Sammobile You will loose root. Instead You can use prerooted stock roms easy to find on S4 forum. Or alternatively use any of custom TW based roms. Imo Omega rom is closest to stock.
[Galaxy S 4 Q&A, Help & Troubleshooting] Skipjacks:
If all you want to do it install a custom recovery and root the stock rom, you might consider just flashing Clockwork Mod Recovery in ODIN. Then using ClockworkMod to root the phone directly from recovery. It's 1 less ODIN step and it gets you to the same place.
[Galaxy S 4 Q&A, Help & Troubleshooting] Dark Blitz:
Thanks for your reply! That is exactly what I want to do.

Just to be sure, should I do it this way?

1. Download CWM_6.0.4.7_Non-Touch_GT-I9505.tar

2. Flash the CWM_6.0.4.7_Non-Touch_GT-I9505.tar file with Odin v3.07

3. Download UPDATE-SuperSU-v2.02.zip

4. Boot into CWM recovery and flash the UPDATE-SuperSU-v2.02.zip from the external SD-card (Because I would place it on the external SD-card)

Then I should be rooted right?
[Galaxy S 4 Q&A, Help & Troubleshooting] Skipjacks:
Yes.

And you can replace the version of CWM you mentioned with any other recovery that makes you happy, as long as it's a .tar install file for ODIN.

Why the non touch version?
[Galaxy S 4 Q&A, Help & Troubleshooting] Dark Blitz:
Thanks A LOT!!!

I prefer the non touch version, because I'm then just a little bit more confident that I don't misclick because of touch (although that probably won't happen) and I think that the volume keys are therfore just a little bit more accurate to navigate with,

Also, if I have CWM installed and rooted my phone, can I then just install ROM manager to keep my CWM recovery up to date or do I have to flash a new one to get an updated version?
[Galaxy S 4 Themes and Apps] SchawanHD:
Hey,

today i found in the folder /0/Android : two files

udid , udid and when i'm open one of the 2 files there are written numbers

And in 2. udid file there are written numbers and letters

So if i change in both some letters or numbers i will be able to enter more Invite codes for (example : junowallet, appnana...) ?
[Android Q&A, Help & Troubleshooting] dolence:
Hey guys, how are you?

I will try to explain what suceed to me yesterday...

My wifey Blu Dash 5.0 was on KitKat original rom, and since she doesn't liked it I tried to restore to a 4.2.2 backup. First thing I did was root it using VRoot. Using Mtk Droid Tools I did a rom and IMEI backup. So far so good...

Next thing I did was trying to install a custom recovery to be able to flash 4.2.2 rom. And here started the cause of all of my problems! At first I noticed every recovery I flashed wasn't compatible with KK. After flashing, when I tried to boot in recovery I always ended with a black screen and the phone booting normally after a few seconds. At this point I was becoming a little concerned about this, but it's ok... I had my phone backup. What could go wrong? My mistake. When I tried to download my backup back to the phone using SP Flash Tool v5.13 I received an error message like the one in the picture above and the phone didn't powered on anymore. When connected to the charger battery indicator didn't showed anymore...

I've tried every button sequence I heard about while powering on the phone but nothing actually works. Already tried to remove all the MTK drivers using usddeview and reinstalling again but at this point I'm not sure drivers are being installed correctly.

There is any way to unbrick this? Anything I should try? USB jig maybe?

Any good soul could help me, please?

Thanks in advance and sorry for my bad english
[Android Q&A, Help & Troubleshooting] dechronic:
Try my thread to see if that helps if not I will see what I can do to help.

Thread is below:

http://xdaforums.com/android/software-hacking/blu-dash-5-0-d410a-stock-rom-images-t2967900