yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dorpmuller:
FWIW, I'm rooted and the first thing I did was install Titanium and froze:

All Knox files (obvious reasons)

S-Finder (having it pop up every time I hit the menu key for too long was driving me insane)

Gallery. Sucks up battery and the device actually got hot. Soon's I froze it problem went away.

Index service. A real disaster ! Ditto the above. Between this crap and Gallery the battery actually started to swell.

My Magazine and other useless apps, live wallpapers, screen saver, Yahoo finance. (broke anyway!:() Search around the forum and you'll find what else you can freeze.

I use the NY Times app, but I went into the settings and disabled all notifications, as I do with most apps anyway. No more crap now!

Oh, yeah, one more. I had Nova Launcher and got fed up with the crashes and lockups it was causing on a more and more frequent basis on more than one device. I switched to KK Launcher and took care of that. I don't think Nova like Samsungs much-had the same with a Note 8.

Hope this helps!

Rich
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] ~nikkilondon:
Disable S finder

I got my phone damp, and now the annoying S Finder pops up NON STOP. I'm talking every couple seconds. Everything else works fine....but I have to end what I'm doing every couple of seconds because that stupid app pops up and I can't get it to leave. I need help :(
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] jasonsc1:
I have the SAME PROBLEM. S finder will NOT quit popping up unless I have my stylus out & it's touching the screen it's driving me NUTS. did you get yours fixed. I was using my phone on an important call in the rain & it's started & hasn't stopped. I'm going to go crazy. I'm rooted and don't want to go through the trouble of un-rooting to use my warranty but dang
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] jasonsc1:
I froze S Finder Via Rom Toolbox Pro & left my Note 3 in some rice for a couple days & it's been fine since
[Moto X General] Derbyman32:
If I understand correctly we will void our warranty if we root our 32GB Moto X. The owners of the developers model is excempt to this rule. I believe from everything I have read that the software and hardware with these phones are identical. My question is how do you feel about not having the ability to root without losing warranty. I can see reasons both ways good and bad but color difference and a logo that says Developers Eddition should not change things for identical phones in my oppinion.

Interested in seeing what others think and maybe someone has asked Motorola about this?
[Moto X General] charlie-n:
If you root as long as you return to stock you're not voided for warranty service, it's unloving your boatloader that your talking about, if you unlock that then yes for sure it voids your warranty.
[Moto X General] Derbyman32:
Thanks for that, I thought rooting was the problem. I guess I have always unlocked the bootloader and rooted my previous android devices in the same step and just didn't realize the differnce. So the people with developers phones can unlock their bootloaders but I can't. Do you know why Motorola would cover one and not the other?
[Moto X General] Vivjen:
Motorola needs reason why DE more expensive:laugh:

Sorry for asking here, but do you know how to remove unlocked bootloader warning during start up (just have got e-mail with bootloader unlock code for DE, but worry about reselling it in future)
[Moto X General] dew.man:
Simply flash a replacement logo.bin file from the themes section.
[Moto X General] Cubfan99:
Screw Motorola. I am going to unlock mine. When is the last time you had to do a warranty claim on a phone? I wonder if unlocking also cancels the $85 protection plan for those who bought it?

-- Sent from my Moto X on Tapatalk Pro
[Moto X General] Rhiannon224:
It does.
[Moto X General] mech1164:
At this point I don't have a need to unlock and root. That said I will probably do it anyway. More than likely after the year warranty is up. For now I'm fine with it.
[Moto X General] kolyan:
If you have a hardware defect, not always root would mean your warranty 100% voided. I don't know about Motorola, but I had my HTC replaced without any issues before
[Moto X General] erikiksaz:
I always test out the phone for a good week or so before unlocking. Just in case there are any problems.

But, as the previous poster said, unlocking shouldn't prevent them from fixing obvious hardware issues like broken speakers or something else that's a hardware failure.
[Moto X General] Rhiannon224:
Read their terms, if you unlock bootloader your warranty is void period. They warn you when you ask for the unlock code, the only exception is DE devices. You have to agree to their terms to get the code. I unlocked mine but it's a DE, I exchanged my custom T Mobile X for the DE during the first Cyber Monday deal.
[Moto X General] mschumacher69:
Think about it this way:

Unlocking your bootloader means you can do all sorts of stuff with ur phone's firmware making it very easy to change the way it works and/or brick it and many people do.

Now if unlocking ur bootloader doesn't void ur warranty, then u would have the right to get support and/or get ur phone repaired under warranty in case u mess it up and/or get it bricked. Now put urself in Motorola's shoes, would you be willing to provide support for your customers because they decided to mess up their phone? No. Warranty only covers manufacturing defects, not defects caused by the user such as physically damaging the phone or unlocking the bootloader and messing with the phone's firmware. Unlocking your phone's bootloader will make it very easy to mess up ur phone making the number of people who would have a messed up phone high and Motorola would need more resources to be able to manage and provide support for such a high number of people.

Now in order to keep customers happy, they allowed Dev Edition owners to unlock their bootloader and keep their warranty as a compromise solution. Why? First of all, the Dev Edition is more expensive, which means the number of people that are going to buy it is going to be less. A lower number of people is easier to manage when having to repair or replace phones damaged because of an unlocked bootloader. Moreover, people who are likely to buy a Dev Edition phone would be experienced devs who are less likely to damage their phone because of an unlocked bootloader or who would know how to fix it if they damage it without having to bother Motorola customer support. Again, this narrows down the number to even less.

I hope this explains it, it's all about limiting the number of people who can claim a warranty because of unlocked bootloader to a manageable number.
[Moto X General] sunnycheeba:
The 32GB Developer Edition phone is the exact same price as Moto Maker T-Mobile off contract 32GB, both are $549.99. It is ridiculous that Motorola threaten to void the warranty because the phone is a different color. The T-Mobile edition "off contract" phone has nothing to do with T-Mobile other than being able to get 1700 AWS. T-Mobile does not have anything to do with the sale of the phone and their website makes no mention of the Moto X anywhere.
[Moto X General] mschumacher69:
Again, it's all down to reducing the number of people that can unlock without voiding the warranty making it easier for them to manage it. It has nothing to do with the phone model or the color of its cover.

Even if they are the exact same phone with the exact same price and the only difference being the color of the cover, lacking color options makes it inconvenient for some people. This means that less people will buy it reducing the number of people who claim a warranty because of a problem related to unlocking the bootloader to a manageable one.
[Moto X General] sunnycheeba:
Seems like it's all about the color to me.
[Moto X General] Derbyman32:
Thank you guys for all the feedback. I see the points for and against the idea. If I could pick I would rather have them do it like most Samsungs I have had. I was able to root and unlock, use the phone and then restore to original without Samsung ever interfering. I know that if my phone crashed while the bottloader was unlocked then it was on me but I always felt I could recover from most anything thrown at me with the help of xda and google search engines. The way Motorola wants to do it is just void your warranty for unlocking bootloader period. I would be willing to unlock and root if I could do it without Motorola's help and would take the chance that if I bricked it then that was on me.

Either way I love my Moto X and really do not feel the need to root like I did with Samsung and all the junk they install on the phones. Everything that came on the Moto X is fine with me but I did buy a no contract unsubsidized off contract phone so I feel that should give me some room to use my equipment the way I wish but still have a degree of protection from failed hardware that has nothing to do with rooting, should that ocur.
[Moto X General] mschumacher69:
Does Samsung allow unlocking their bootloaders officially?
[Moto X General] Jayrod1980:
I would really like to find someone who has successfully done a warranty claim on an unlocked motomaker XT1053. I returned mine after it was unlocked but that was a return, not a warranty claim. I'm on moto x no3 right now for various reasons. First I returned because it was the only way they would honor the price change since I ordered a few hours before the announcement of the cyber deals on that same day. They couldn't cancel building the phone after only a couple hours. They made it right with a coupon and allowed me to return it. I'm regretting saving that money because now its all headache. I got the same color, etc phone after for the cyber monday price... and it came with corrupt flash or something else hardware related. Phone would not successfully boot, even after flashing stock firmware. They did an advanced replacement and now I'm on device no. 3. Thought the phone was perfect, but they put a big nick right by the silver keys of the phone. They really are sloppy when they make these things. I called them and they put a note on my account that I could get a replacement at anytime... indefinitely because of that, but I'm sure it will be voided if I were to unlock the phone. I'm trying to just live with the blemish, but I'm OCD with my devices. Even exchanging to save money, I probably have spent at least $100 on cases and screen protectors.

Is there anyone out there that has successfully done a NON SOFTWARE related warranty claim on an unlocked non-dev (T-Mobile) Moto X?
[Moto X General] rockingondrums:
:eek: I'm definitely going to re-read these terms. Insurance, in which I pay a deductible to replace the device, is not the same as a free replacement due to a factory defect. And if unlocking the bootloader negates my paid insurance... well that's a pretty dirty business practice. It also doesn't seem very enforceable, as I could just drop my phone from a very high distance and successfully file a claim... Let us double check the fine print.

That's racist!:p
[Moto X General] sunnycheeba:
I noticed that Motorola updated the language regarding the T-Mobile - no contract Moto X on the Moto Maker site yesterday. What just used to show the T-Mobile logo and "No Contract" when selecting a T-Mobile Moto X, now reads: "GSM Unlocked" in Large font with the T-Mobile logo reduced to a smaller type face. It also says: "Comes with T-Mobile SIM. Use with AT&T and T-Mobile 4G LTE, and Global HSPA"

In the updated Moto X FAQs, T-Mobile is not mentioned as a carrier, the phone is now simply referred to as the "GSM Unlocked" model.

https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/97692/action/auth

I hope this more un-carrier distinction will have Motorola reconsidering making the XT1053 'GSM Unlocked' model (formally known as the 'T-Mobile - No Contract' model) have the same warranty as the XT1053 Developer Edition, since there is no carrier involvement in either.

Also relating to 'no contract' Motorola phones was a comment made by Motorola CEO Dennis Woodside in his interview with MKBHD last week. When talking about the Cyber Monday sale, Dennis said: "...we learned alot. There's clearly demand for devices that are not tied to a contract, at prices that are reasonable, and I think were gonna listen hard to that, to what the consumer told us on Monday and on Wednesday....". Dennis later goes onto to mention that AT&T was just releasing new wireless plans which include "Bring Your Own Phone" discounts; this is probably the reason for the more generic "GSM Unlocked" moniker been given to the XT1053, since Motorola plan to now market this model to AT&T BYOP customers as well as T-Mobile.

https://www.youtube.com/watch?v=kpqBNn_BfKE&feature=player_detailpage&list=UUBJycsmduvYEL83R_U4JriQ#t=133
[Galaxy S II Q&A, Help & Troubleshooting] Aristona:
Hi XDA.

First off: I HAVE A 9100G!

Yesterday I tried to root and flash PACman.

Rooting went allright, even though I didnt backup/grant superpermissions.

Then I tried to flash Pacman 9100, the non-G version. At that moment I didn't know I had a 9100G.

I did get the error code 7, which meant it wasn't for my phone, but I googled a workaround to fix this. This was mistake #1.

After this, my phone pretty much broke.

I tried to flash other ROM's but every rom would fail at this:

<ID:0/003> hidden.img

<ID:0/003> MLO

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

.

So at that point I didnt have any ROM installed, and could install no other ROM.

After trying to install a ROM I had to flash a new kernel to be able to get into recovery.

After a while I couldnt install kernels anymore. In Odin the flash would 'Pass', but after the reboot it would freeze halfway in the kernel-install.

After freezing, it would go in a loop.

So currently, I have a phone which only says Galaxy SII with the yellowtriangle under it.

I can, however, still get into download mode, so I don't think it's done yet.

If someone, could help me get my phone working again, U'll be my hero of the month..

I'll be really active to answer all questions and try all possibilities.

- Sam
[Galaxy S II Q&A, Help & Troubleshooting] LYandroid:
can you acces recovery mode right now?if odin fails try to use to flash another ROM with Recovery.;)
[Galaxy S II Q&A, Help & Troubleshooting] Aristona:
I can't enter recovery, but neither can I flash via Odin. Odin keeps failing after factoryfs.
[Galaxy S II Q&A, Help & Troubleshooting] mosespl:
Try to flash 2.3.6 3 files via odin maybe it will works

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[8125, K-JAM, P4300, MDA Vario General] phaijai:
Hey guys,

I have a questions about the "Contacts" soft key. I recently installed and then uninstalled Contacts Breeze on my 8125. After uninstalling, the "Contacts" seems to have lost it's path. When I press the button, it doesn't take me to my contacts. I now have Pocket Informant installed. Is it possible to change the path in the registry to direct me back to the default Contacts or PI's Contacts?

Also, is it just me or is the ringer not loud enough?

Thanks for your help.
[8125, K-JAM, P4300, MDA Vario General] mike freegan:
no idea about the contacts softkey, but my ringer's quiet too. I read somewhere that it depends on what ROM you have. I'm on 02 UK
[8125, K-JAM, P4300, MDA Vario General] phaijai:
Been checking here, hofo, and other forums and still can't find the fix. Can anyone tell if it is possible to change the path of the Contacts right soft key back to it's default location?
[8125, K-JAM, P4300, MDA Vario General] vijay555:
phaijai: check in the wiki for how to change the softkeys to whatever you want.

V
[T-Mobile Samsung Galaxy Note 3] smaisonville:
I am rooted and I want to freeze or delete T-Mobile IQ from my phone. In Titanium Backup I found the following :

System.Manager.Application

System.Manager.Notfication

System.Manager.Toggle

It appears to me the Carrier IQ is in System.Manager.Toggle. Will someone please confirm or guide me in the right direction.

I have seen posts where T-Mobile Carrier IQ has been removed but it does not list the files to remove or freeze.

Thanks in advance.
[T-Mobile Samsung Galaxy Note 3] trek7000:
Those are the right files to remove. If you look at the properties of them in TiB, they each contain com.carrieriq.tmobile in the name of the apk.
[T-Mobile Samsung Galaxy Note 3] smaisonville:
Thanks I appreciate your help
[T-Mobile Samsung Galaxy Note 3] circuit.007:
I was wondering what dpi everybody is running. Currently I am running stock but was wondering if there is a good dpi level everybody is using that gives more space and does not cause force closes.
[T-Mobile Samsung Galaxy Note 3] cpufrost:
400. No problems with FC on any DPI in the past.

However it does mess with a lot of apps. To fix this you need the Xposed framework and an app called App Settings.

I've dialed it down to 320, sure makes things TINY but love the extra real estate. 480 on this phone is huge, reminds me of the folks running 800x600 on 21" monitors! :D
[T-Mobile Samsung Galaxy Note 3] rlee008:
400 sounds pretty high to me. i haven't rooted my N3 yet so i cant change my DPI but on my N2 i was running 280 and it seemed perfect to me. Thats what ill use on my N3
[T-Mobile Samsung Galaxy Note 3] CalcProgrammer1:
320, and I think it makes things look normal. I put it at 220 in per-app DPI and that was tiny. 320 on the Note 3 is comparable to 220 on the Note 1 which was what I always set my Note 1 to (ran it at 200 for a while even to get the Nexus 7 style tablet UI). I use per-app DPI to set the dialer and camera and other Samsung apps back to stock since they get distorted at 320dpi.

Edit: You realize the N1/N2 and N3 are not comparable in dpi right? The increased resolution means to get N2 280dpi you'll likely need 380-400. 280dpi on N3 is getting pretty small. N1 220 compares roughly to N3 320.
[T-Mobile Samsung Galaxy Note 3] cpufrost:
It's a 1080 display, 320 is definitely the lowest I'd go!

280 would definitely be small.

320 on 720 devices such as the Note II look about the same as 480 on the Note 3, in my experience.

Nice thing is it's easy to change in build.prop.
[T-Mobile Samsung Galaxy Note 3] jahnbodah:
I like 360. Its a nice round number... Puns aside, I really do like this dpi.

That or 380
[T-Mobile Samsung Galaxy Note 3] circuit.007:
Thanks for the replies. Okay so if I set it somewhere around 360 to 400 I will have no problems with system ui only apps that I will have to adjust with app settings module? Would I have to go into each one and adjust or adjust all at once. I have a lot of apps. Also what is the stock dpi set at? To change it I would edit it under build prop using rom toolbox?

Was wondering if you guys could post screen shots to get a better idea.
[T-Mobile Samsung Galaxy Note 3] cpufrost:
If you use app settings you can fix issues with programs not displaying correctly OR just looking too small...

Default is 480 in build.prop.

I use root explorer, open the system folder R/W and click and hold build.prop and select open with, text editor. Make changes and it will save original as build.prop.bak. Reboot to see changes.

I can post a screen shot of the settings used in app settings. Once you get the hang of this you can adjust as you wish. With some apps I prefer to use a slightly different DPI in app settings so it's not as big as it would appear at 480 yet not as tiny as it would appear at 320. That's the nice thing as you can pick anywhere in between for a balance that suits your needs/wants.

Furthermore, all these settings will be saved/backed up if you use Titantium Backup to back up your device. That's a good thing if you're a flashaholic like I tend to be! :cowboy:
[T-Mobile Samsung Galaxy Note 3] Police666:
ignore this post please, i posted in wrong thread
[T-Mobile Samsung Galaxy Note 3] mscion:
Globally I use default settings but I like to adjust the dpi for certain apps using App Settings. For example, for some apps I like a tablet look to them which can be achieved sometimes. Notablly this can be done with gmail app. In this case I set dpi to 320 and screen dp to 800x1280. Here is a screen shot. Maybe not for everybody but I like it.
[T-Mobile Samsung Galaxy Note 3] tpowell.ca:
I personally use 400 for most apps except for media player style apps as the large button interfaces help for use on the go.

That said, do you guys have issues with the gallery photo editor app and other apps that display pictures using stock libraries (or so I'm guessing) where the picture is zoomed and cropped where you cannot see the whole pic even if you try to zoom out?

So far the google gallery photo editor, the samsung photo editor and ES file explorer all have the same problem for all DPIs other than 480 applied globally or specifically to "Android System".

Even if I set the photo editors to 480, as long as the "Android System" package is not 480 the pictures will be cropped.

:confused:

Thanks
[T-Mobile Samsung Galaxy Note 3] Techngro:
How did you change your dp (i assume that's the resolution) to 800x1200? I already did the global DPI change to 400, but I want to see how that resolution looks for myself.
[T-Mobile Samsung Galaxy Note 3] mscion:
Hi. I'm just using the xposed module called App Settings. In the screen shot you can see where I change the dpi for the gmail app and the screen dp. There are a set of dp you choose from. Some make a difference and other settings don't seem to have an effect. Might want to do a back up before trying. Sometimes a bad selection can cause problems when booting up. Hope it works out!
[T-Mobile Samsung Galaxy Note 3] Morningstar:
I run almost everything at 340, as 320 is just a little too small for me. For the Samsung apps (that I haven't removed), I either use ones modded for multi-dpi from the International Note 3, or ones that I have modded myself, at 320. I don't think I have anything that still runs at the stock 480. Having a screen this size, but with everything blown up that large just seems like an incredibly bad utilization of space to me...
[T-Mobile Samsung Galaxy Note 3] alobear:
does anyone know how to make it so that your keyboard won't shrink? I use SwiftKey and though you can make it bigger it's not big enough and of you try using app settings it messes with it and turns out all bonky. I want to go down to something like 400 but the keyboard gets a tad small.
[Samsung Galaxy Tab Plus] TheHypebeast:
This is Great!!

Thank you for all your great work, it is running smooth on my tab. And camera is working now for me on this 4.4 build. It more than enough for a daily, again thank you so much for keeping my tab alive!
[Samsung Galaxy Tab Plus] LuciferAust:
+1 for still developing this beast :) :cyclops: :good:
[Samsung Galaxy Tab Plus] TheHypebeast:
I downloaded the multi-window zip but in recovery it stated it was a p6800 zip and was not installed...

2013/12/12

Just Mange to include the preliminary multi-window source for the 4.4.2 test build. I made a patch for the existing OmniROM. Although the codes is preliminary, it works great. Some apps might not work but overall is worth trying. I might include it in the later builds if it doesn't cause crash. Files will also be found in the download links. Flash the MultiWindow-patch zip in recovery. (A revert zip is also provided) Cheers! :cool:
[Samsung Galaxy Tab Plus] mrgill:
I got wifi issue on my P6200. It alway loop turn-on and turn-off wifi not work for me. However I think you can fix it soon. Cheers:good:
[Samsung Galaxy Tab Plus] daniel_hk:
Sorry, didn't think of that, will fix it and re-upload in an hour!

Files are replaced, but goo.im may take longer to upload. Try AFH and mirrors first. ;)

See the Tips (#2 post) in my 7.7 thread. For some router, turn OFF the Wi-Fi optimization will fix that.

Good luck!
[Samsung Galaxy Tab Plus] mrgill:
Broked link. Can you edit plz.