yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Q&A, Help & Troubleshooting] nicholaschum:
Thanks for the update. Then we can start porting Note 4 ROMs to Note 3!
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
This somehow doesn't seem very accurate. The Note 2 isn't supposed to be getting 4.4.4... (According to Samsung itself, which is bound by Google's 18 months contract.)
[Galaxy Note 3 Q&A, Help & Troubleshooting] r-l:
I thought samsung would skip 4.4.4 because of android l
[Galaxy Note 3 Q&A, Help & Troubleshooting] nicholaschum:
4.4.4 could bring more updates to the KNOX system, and since it was released 1 year ago, deployed on all devices, it would look bad for the company (Samsung) to drop support for KNOX on a legacy device they started supporting last year..
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
Except that the latest 4.4.2 updates already brought KNOX 2.0.

KNOX runs fine without needing the newest update every day. 4.4.4 is not mandatory for it to continue running.
[Galaxy Note 3 Q&A, Help & Troubleshooting] jdomadia:
I think 18 months contract is for major updates like Jelly bean to kitkat, question is 4.4.2 to 4.4.4 is count as a major update?
[Galaxy Note 3 Q&A, Help & Troubleshooting] dajumper:
I ask sammobile and This list is fake
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
18 months applies to all updates. It's the length of the contract for Android on any device. (LG, Sony and HTC are bound by the same contracts) That's why the 'or two major upgrades' addendum exists.

There are a few rare exceptions, and any vital security updates still get rolled out to popular previous flagships, but that's it.

Samsung said the same thing when I asked them. Although I take that about as seriously as the guys who say it's real.
[Galaxy Note 3 Q&A, Help & Troubleshooting] mircea89fzr:
The 18 months rule means if we're not getting Android L until February 2014, we're not getting it at all?
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
Not precisely. It means that if Samsung didn't get Android L February 2014, we're not getting it. There's about 4 months between Samsung getting the next Android version, and it actually rolling out to its users. Once Samsung has the firmware, they can roll it out whenever they like, even after the contract has expired. But only on devices included in that contract at the time of transfer. So if the Note 2 wasn't supported when Samsung got Android L from Google, it won't be getting Android L at all.

So even if Samsung gets Android L in January, our Note 3's are still included in the contract, even though we might not be seeing it before march (S6 release). (That's not a timetable by any means.)

The final L release is expected around late 2014 (End November/early December), so in theory we should be getting it. It depends on whether Samsung sees 4.4.4 as a major release or not, as that would mean we've had our share.

It is also fully possible that they're skipping 4.4.4 in exchange for L, as they've done with 4.2 for many devices, amongst which the Note 2. Considering 4.4.4 has been out for the Sprint edition for over a month, and we've not heard a peep, this is a strong possibility.
[Galaxy Note 3 Q&A, Help & Troubleshooting] nicholaschum:
18 month rule has been sidetracked since a long time ago...

Nexus One: ~20 months to 2.3.6.

Nexus S: ~22 months to 4.1.2.

Galaxy Nexus: ~19 months to 4.3.

Nexus 7 (2012): ~23 months to 4.4.4. ~28 months to 5.0.

Nexus 4 & 10: ~19 months to 4.4.4. ~24 months to 5.0.
[Galaxy Note 3 Q&A, Help & Troubleshooting] robwiel:
Living in PL have 4.4.2, and update to 4.4.4. ota appeared however it fails...? Towelroot issue?
[Galaxy Note 3 Q&A, Help & Troubleshooting] DiRT_360:
try restoring it on odin to the latest version available for your csc (back to full stock without root) and than try again.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
Were you listening? It's the contract Google has with other companies.

The Nexus may be manufactured by a third party, but management of it is done by Google itself, thus negating any such contracts. That's the whole point of the Nexus line-up, they serve as Google's Beta devices.
[Galaxy Note 3 Q&A, Help & Troubleshooting] nicholaschum:
Actually, if you were part of the Galaxy Nexus community back in the day, there was a version of Galaxy Nexus that was managed by Samsung and not Google. But they both still had support up to 4.3 and that was 1 month more than the 18 months.

http://feeding.cloud.geek.nz/posts/how-to-get-android-ota-updates-from/
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
As I've thoroughly explained in other posts on this subject, the contract applies not to the release date of the actual OTA, but the date the new Android version is handed over to Samsung. So if Samsung got the new Android version before the 18 months are over, regardless of the delay in release, the device would still get 4.3 because it fell within the timespan. The issues with 4.3 that Samsung experienced which led to the recall of it several times were not bound by the actual contract with Google, as the device at the time of transfer fell within the 18 month period.

I'll put it more simply: If Samsung get the green light from Google for the Note 3 before the end of February, we'll be getting L. (Provided 4.4.4 doesn't count as a major update). Even if it takes Samsung 6 months to roll it out due to unforseen issues, the original time of approval fell within the 18 month window.
[Galaxy Note 3 Q&A, Help & Troubleshooting] nicholaschum:
Sure, that makes more sense.

However, in the OPO terms, as the CM11S is a build branched off from CM11, a version of release must already be completed then submitted to Google for approval. It takes around 1 month for approval. But that also shows that a submitted final version must be sent to Google to check for use of Google Apps in the ROM, root and Android etiquette.

So if this is the same rule that applies, that means a final version of TW Android L has to be submitted before the 18 month contract.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
There's a difference.

CM has to submit to Google's open product procedures before the Gapps are approved for it after completion, as CM is an independent release that has no legal contract or deal with Google. It's just a matter of 'If you want to use our apps, this is what you have to comply with." (crudely put). If they don't comply, that's that, Google won't allow the use of its apps. If they release it without approval, there won't be legal action, there just won't be any Google Apps.

The smartphone companies like Samsung, HTC, LG and the rest have legally binding business contracts with entirely different terms and agreements. Once Samsung has the Android version from Google, the firmware doesn't go back for approval. Mandatory requirements are included in the contract, and Gapps are included in the firmware from the start. If the contractual agreements are broken, there are fines and legal repercussions. There is also the matter of the fact that companies pay for the Android license.

So whilst any non-contractual goes Google > CM > Google > CM > Release, for the companies it goes Google > Samsung > (Provider > Samsung > Provider > Samsung >) Samsung OTA Release.
[Galaxy Note 3 Q&A, Help & Troubleshooting] robwiel:
Suprisingly upgrade through cable did work instead. In meantime upgraded towelroot (did not hurt).

Current firmware version : PDA:NC2 / PHONE:NC2 / CSC:NC1 (PLS)

Latest firmware version : PDA:NG1 / PHONE:NG1 / CSC:NG1 (PLS) - Apparently its 4.4.2, and kind towelroot does not work on anymore, ideas?
[Galaxy Note 3 Q&A, Help & Troubleshooting] nicholaschum:
Well there's only one way to prove your statement and that's to wait if 4.4.4 gets released and/or L.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
Nothing to do but wait :) (And watch people speculate wildly). Best case scenario is 4.4.4 being counted as a minor update around mid November (or skipped) and getting L somewhere in February.
[Micromax Canvas A1] Captain sparrow:
Hi guys,

Reverting back to stock untouched firmware is always needed when especially when you are in need of warranty or stuck at bootloop and many such cases.

Here is my small step by step guide on how to flash your stock firmware on android one devices.

Mod Edit on links.
[Micromax Canvas A1] hyelton:
For anyone looking to download any of the files you Can get them here: http://xdaforums.com/canvas-a1/development/official-stock-rom-canvas-a1-t2887150 ( I dont think the "Click to like to see downloads" is allowed here.
[Micromax Canvas A1] Clark Joseph Kent:
Either provide the links or not, but having Members go off site just to hit your "like" button, not happening.

Thread Closed.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] SPV2010:
I rooted my Galaxy Note 10.1 2014 Edition (P600) tablet using CF AutoRoot. I ran odin and flashed the two tars. (autoroot mj4 and stock recovery mj4).

Next I decided to put TWRP on, so i opened odin and flashed TWRP. It worked fine for a few days, then suddenly i lost root on some of my applications. I opened up TWRP and tried to flash Super SU again and it had a problem clearing the cache. It then wouldn't mount the cache at all. Meaning my tablet wouldn't boot.

I managed to fix it by running autoroot again and flashing the stock recovery, but now i have issues with my tablet only working for about 5-10 minutes, then it restarts itself. I'm assuming the cache might be corrupted and it ends up getting filled and then crashes. After about 5 minutes, it freezes and then goes to a black screen and restarts itself.

Can anyone help me fix this?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] lightman33:
you should try this method : http://xdaforums.com/showpost.php?p=53125229&postcount=409
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] SPV2010:
As i said previously, that's the method I used.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] buhohitr:
Try reflash stock recovery, clear cache, davik cache and data, let it boot up then power down and start over with re root method again. MAKE SURE you use the correct CF autoroot for the p600 device.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] lightman33:
you are saying you loose root after a few days, did you remove or freeze knox apps ?

see previous message advice, you should restart with a full wipe and full flash and it should be ok. An other way is to flash a custom already rooted and knox freed.

hope it will help you, good luck.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] SPV2010:
I lost root after a few days, not that i lose root. It happened the first time and from then the problems started occurring. I froze knox applications (all 8 of them).

I did a logcat using adb to see what errors occurred and i got an error saying

Does anyone know what this error means and how to fix it? I heard its a data alignment problem, but not sure how to fix it, but i assume a full format would do it.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] buhohitr:
I would say a corruption would cause this and until you reformat, otherwise, you're going to get it again. Data corruption could cause many "unknown" errors, so you should reformat and do a clean install.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] DarkDarwin:
Whats the best way to format if you havent got a custom recovery,stock recovery? Odin? (scary)

My issue is I get rooted ,freeze up knoxes but then when I go to install TWRP (any ver.) it doesn't take..

sorry to piggy-back but it sounded similar to my situation
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] majorassface:
Hey guys, I have the p600 and was running stock NIL1 and decided to root. I ran in to all kinds of issues, very similar to what you are experiencing but managed to fix it so haven't had the instability. I believe you're missing a crucial step. I wasn't able to mount system or wipe cache until I did this.

Here's what I recommend:

Odin back to stock recovery

Boot to stock recovery and perform a factory reset and clear cache, this part was important

Reboot to download mode

CF Auto root again

Flash TWRP

Flash rom of your choice, I'm running http://xdaforums.com/galaxy-note-10-2014/development/p600ueucni1-pure-stock-rooted-t2896910 and it works great!!

Hope it works for you!!
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] DarkDarwin:
Hey What TWRP was it?

Me too! ......Ill let you know :) Thanks
[Xperia Z3 Q&A, Help & Troubleshooting] istrikerx:
Hey all,

Is it normal for the top speaker to buzz/crackle when certain sounds are played, particularly those that are somewhat bass heavy?

A good example would be the stock notification sounds, as a lot of them cause this. In particular, the Polaris notification sound makes it rattle like crazy. The Aquila ringtone causes it too. These are just 2 of many examples I could pick out.

Test it yourself, is it normal?
[Xperia Z3 Q&A, Help & Troubleshooting] Geeks Empire:
Info

No

ask for replacement cause it s weird hardware issue!

:good:
[Xperia Z3 Q&A, Help & Troubleshooting] istrikerx:
:(

This is my 3rd replacement too...

Edit: I opened up my faulty z3 due to be returned, and it also has the issue with the top speaker crackling.

Seems to be normal then. I assume with the top speaker being responsible for the lows, it just couldnt handle the bass at high volumes.
[Xperia Z3 Q&A, Help & Troubleshooting] Wavey57:
Same here

I just had my first replacement and the problem persists :(:crying:
[Xperia Z3 Q&A, Help & Troubleshooting] mrscaly:
I just got the Xperia Z3 this week and noticed this issue as well. I'm a little disappointed because I expected more from the purportedly improved speakers but I guess I'll live with it for now.

I also noticed that the Z3 gets pretty warm if you play music via walkman with the speaker volume at the max. What also bothers me is that there is speaker noise when using the camera app, even with sound disabled.
[Xperia Z3 Q&A, Help & Troubleshooting] GhostLeader:
yeah, my Z3 has the same issue :(

Even if you are phoning with load speakers on max volume it crackles.
[Xperia Z3 Q&A, Help & Troubleshooting] apple_lover_just_kidding:
i have the same pb

my top speaker crackles during some calls at max volume...

I hope this is a software related problem...

any news on this?
[Xperia Z3 Q&A, Help & Troubleshooting] AlexusJ:
Well, I don't really have "crackle" but there's a noticeable "static noise" from top speaker whenever it is active (like when watching a movie/video or even when talking to anyone), especially at high volume setting. More than in any other smartphone that I've ever used. And what's more disappointing is that I am currently using a replacement unit, the original unit had EXACTLY the same issue. I really, REALLY hope that it's a software issue and Sony will be able to improve it with future updates and it's NOT because Sony used low-quality speaker or amplifier components :(
[Xperia Z3 Q&A, Help & Troubleshooting] kirankannan:
I have top speaker issue after 2months...the speaker crackling sound get higher.,,and really annoying.,, sometimes not even hearing.

What to do?

My phone got 6month older??

How to solve?

Can I go for replacement?
[Xperia Z3 Q&A, Help & Troubleshooting] nedooo:
So this is generic Z3 issue :( bad move for such a pricey phone...
[Xperia Z3 Q&A, Help & Troubleshooting] orangzeb:
Count me in too..
[Galaxy S 4 Q&A, Help & Troubleshooting] Etrnlwanderer:
Hi, I'm from India and have a GT-I9500 which has been running flawlessly for the past 1 year on BSNL service right up to OS version 4.4.2 firmware vers. I9500XXUFNE4. Since then I upgraded the firmware twice to I9500XXUFNG1 and subsequently to I9500XXUFNI2. Midway while using firmware I9500XUFNG1 in rooted version, I started noticing that my phone data would run normally for a while and then suddenly the data connectivity would drop from H+ mode to 3G but would not return to H+ even though I know that I am in an area that has consistently strong H+ signal. The only option to get H+ mode back was to go to Settings/More networks/Mobile networks/Network mode/ and change the setting to WCDMA only mode for two minutes and then switch back to WCDMA/GSM(autoconnect), then the phone would get H+ service back again for a few hours. I thought that it might have been some problem caused by rooting, so when the latest firmware (I9500XXUFNI2) was released this month I upgraded the firmware but since I lost root on upgrade, I did not root the phone, fearing the problem will come back since I thought root was causing it.

Now in stock firmware running on I9500XXUFNI2 I am still getting the same problem of the phone dropping to 3G mode from H+ and not reverting back ( the speed is not even 2G. Just the 3G icon shows it - data packets hardly get transferred) and I can rectify it only by switching to WCDMA mode and back to autoconnect, as previously stated.

I checked online for solutions, but I don't seem to see anyone facing such an issue.

I thought it could be a service provider problem, so I used SIMs from Idea and Airtel as well, but while using those networks also, the same problem persists, so I have deduced it is a problem pertaining to the phone only. Not sure if it is a hardware malfunction or firmware based.

Does anybody else from India running the latest firmware for GT-I9500 have similar problems, and is there a solution?

Thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] Devilslasher:
The problem is with the modem firmware. Change it back to the original or get a kernel.
[Galaxy S 4 Q&A, Help & Troubleshooting] Etrnlwanderer:
Thank you, Devilslasher. Could you please link me to a thread where they have listed the original modem firmware? I did a search under the Samsung S4 subsection on xda but could not find any thread where modems/radios for Indian version was hosted.

Thanks in advance.
[One (M8) Q&A, Help & Troubleshooting] QA Bot:
[Q&A] ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants

Q&A for ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
[One (M8) Q&A, Help & Troubleshooting] gyoder:
Red boot text removal help

I'm new here and wanted to see if someone may be able to help me out. I would like to run install the updated hboot to remove the red text from my VZW HTC One m8 but can't figure out which version to use since TWRP knocked out the mainver/OS info. Here's my getvar:

C:\adt-bundle-windows-x86_64-20140702\sdk\p

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.18.0.000

(bootloader) version-baseband: 1.09.20.0702

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: XXXXXXXX

(bootloader) imei: XXXXXXXXXXX

(bootloader) imei2: Not Support

(bootloader) meid:XXXXXXXXXX

(bootloader) product: m8_wlv

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B20000

(bootloader) cidnum: VZW__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 6092c531

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.094s

In case it is helpful I started on 4.4.2 then rooted/S-Off and installed ViperOne. When the OTA 4.4.3 came out on Verizon I flashed stock recovery and took the update. Then I reflashed TWRP. I am currently not Super CID but I can change that if I should. Any help on figuring out which version of the files I need to remove the red boot text would be greatly appreciated! Thanks!
[One (M8) Q&A, Help & Troubleshooting] Boostitem:
vodaP021

Hi was hoping to get a remove red text for VodaP021 here is my GETVAR info

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.16.0.0000

(bootloader) version-baseband: 1.16.2133156.UA15_2G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: SH43JWM04395

(bootloader) imei: 358716055044951

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B11000

(bootloader) cidnum: VODAP021

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: RUU

(bootloader) commitno-bootloader: ab0efa49

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.026s

thanks in advance
[One (M8) Q&A, Help & Troubleshooting] jxcorex28:
Which recoveries would you guys recommend ? I've been using twrp by CT for the longest time, but every so often after firmware changes I'll get problems when trying to wipe dalvik cache,system data,cache,etc...Every time these problems occur, I always have to resort to backups.

---------- Post added at 03:51 AM ---------- Previous post was at 03:51 AM ----------

Santo recommended a recovery change,so I am just seeing which recovery you all would recommend
[One (M8) Q&A, Help & Troubleshooting] jxcorex28:
Pic
[One (M8) Q&A, Help & Troubleshooting] turboblaz:
I suggest you to hide your imei number and serial number

Poslano z mojega HTC One_M8 z uporabo Tapatalk
[One (M8) Q&A, Help & Troubleshooting] ceyo14:
What's the difference between 3.28.401.6

3.28.401.7 and

3.28.1540.5?
[One (M8) Q&A, Help & Troubleshooting] jxcorex28:
I asked the same question earlier...

.7 is the Croatian update...401 and 1540 are from what I understand regional affiliation,maybe carrier ( someone back me up if I'm wrong).
[One (M8) Q&A, Help & Troubleshooting] gyoder:
Thanks

Thanks for putting this together. And the unbelievably quick 3.28.605.4 turn around.
[One (M8) Q&A, Help & Troubleshooting] sidi adam:
Thx for your time to make it possible to get rid of the red text.

Can you tell which file I need to get rid of the red text?

CID-Vodape17

Hboot: 3.19.0.0000

Radio: 1.21.21331147A1.19_2G

OpenDSP-v45.2.2-00542 - M8974_HM. 0422

OS-3.29.161.5

Many thx!
[One (M8) Q&A, Help & Troubleshooting] wilean0120:
Htc One M7

Will this work on HTC One M7 UL?
[One (M8) Q&A, Help & Troubleshooting] jlkill3r:
Can I Flash International:WWE Mainver: 3.28.401.7?

I have the International:WWE mainver: 3.28.401.9 on a AT&T HTC One M8 and I'm not certain if I it's safe to run the International:WWE mainver: 3.28.401.7 hboot file. Would it be safe to run this or should I hold off?
[One (M8) Q&A, Help & Troubleshooting] gauravbhawsar:
[quote name="starbase64" post=58237583]4.16.401.9 no red text > http://ul.to/4ryklcin[/QUOTE]<br />

Unable to download from ul.to as it is blocked in India... Can somebody plz mirror it to zippyshare or Google drive... <br />

Thnxx in advance... <br />

<br />

Sent from my HTC One_M8<br />

---------------<br />

<b>Admin Note: this thread has a dedicated questions and answers section which you can access here -->.</b><br/>

Sent from my HTC One_M8