yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] Theziggy:
Detection's advice above is great. In my first tf101 I used Frederuco's method which uses Easyflasher and it worked a charm. I got my other half a TF101 for Christmas and for whatever reason Easyflasher didn't work so I googled and tried PERI and it worked.

Please note that if you intend using TimDuru's ROMs 4.3 or 4.4 etc to use the TWRP recovery, and to flash the newest version of it once you are rooted. Frederuco's guidelines talk you through how to do that.

I was very hesitant before I rooted the TF101 - being a noob, but it wasn't as daunting than I imagined and the rewards of the much quicker ROM are well worth the 15 minutes that the rooting and flashing ROM take.
[Eee Pad Transformer Q&A, Help & Troubleshooting] KingUltron:
There we go, used Frederuco's method and it gave me no problem.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Theziggy:
Happy Days

What it says on the title
[Android Software Development] Serilei:
Ok, I want to start out by mentioning; some of you may or may not know about a project I've been working on since March 2013, the Android Desktop OS which is now in version 2.0.

Can test the interactive demo online here: http://invis.io/95IKINK4

I've been on this project by myself, putting together ideas and re-imagining how Android should be on a desktop. Now, I know that Android x86 does exist, so please don't announce that android on the pc has been done already, because it's not how I envision any of this.

I think also they have started this as a hobby with no real distinct intention, I started my idea to give Android a very bright future. I believe as well as many others who are excited for this project that Android could be massive on desktops.

Yes, I know that it is written with a Linux kernel and it is aimed for mobile, but my goal is to change that. I want it to be able to run all the apps from the Market Place in it's normal fashion without anything complicated, but I want the core of this, the heart of this to be written for Intel hardware for starters.

I know there are some guys wrote some Intel hardware code for android, but I don't think they did it to be anything major. I want to take this to a whole new level, I really want this project out there, I want it to stand out.

Why does Windows, Mac and Ubuntu get pc and mobile counterparts but not Android? I feel personally it isn't quite fair and that Android should have its potential shown.

For those of you who have never seen my project, you can check it here: http://xdaforums.com/showthread.php?t=2214161

Everything is still subject to change, but overall I am happy with what I have. I want to advance on Android without steering away from the heart of it. There are more ideas I have, but have been short on time with doing what I want.

Now here comes the icing.

I am stuck at a crossroad; I need a team, I need to find those who are just as interested in this as I am, but I don't know where to find them. I've posted this in numerous places without much coming back as far as coders.

I've been told to do a kickstarter, but I don't know the first thing about it, how to find the people, manage the money, who to trust, bring this to completion etc... So this brings me back to square one, where I just continue to develop this idea in it's visual form, because I don't know what to do.

I have been dedicated to making this happen for a long time, this can and will be a long term career, but I need the man power, those who believe in this. But where to find it? I figured since the internet is vast people would come at least wanting to give it a crack, but it has been dry out here.

I am open to feedback and really hope this can get off the ground.
[T-Mobile Samsung Galaxy S 4] peeps67:
Hi Guys,

Has anybody had any issues trying to update their phone with the jump program.

I went into the tmobile store on 1/12 and the rep pulled up my account and indicated that I an eligible on 1/14. I would need to go into the store to do the upgrade.

On 1/14 I went into the store and asked to update from the S4 to a white G2. Well, to my surprise they did not have any white G2's and could not have one shipped to me because they jump program does not allow shipping to an address. They could not even ship it to the store. They called around and found a store 45m in from me that had a white G2.

Off I went to the store. I spent 1.5 hours in the store while the reps tried to process the upgrade but could not. Had customer service on the line and still no luck. Eventually I had to leave because this was taking 2.5 hours out my day.

I called customer service about 3 times yesterday and still no luck. They indicated that they cannot do anything as the Jump program must be done from a store. I stopped in at another store last night and the same issue. Unable to complete the process.

I am so frustrated with tmobile right now. Do they not test this before they launch it. Maybe the same company that build the Obama Care is managing the tmobile site.

:crying::crying::crying:Let me know if you guys have had any luck.

Sean
[T-Mobile Samsung Galaxy S 4] fracture8:
Wow I've never heard of a situation like this but, what I would do is call around to make sure that theres a T-Mobile that has the N3, (that's what I did) and just go pick it up
[T-Mobile Samsung Galaxy S 4] The Sickness:
Not to get off topic. ...but did you have pay anything? Like a down payment?

My S4 Is Insane

DEVIANT DEVELOPMENT
[T-Mobile Samsung Galaxy S 4] peeps67:
Were you able to get a new phone with the jump program? The guys at the store seemed like a bunch of "Yahoos" and I'm not sure they know what they are doing. Nobody seems to have completed the jump redeem procedure yet.:p
[T-Mobile Samsung Galaxy S 4] peeps67:
So, I called customer service today and the rep said they are looking into the issue with the jump program and she has all my details and would give me a call on Wed, Jan 22 :(

You would really think it would take them a day to fix this issue.

Not impressed.
[T-Mobile Samsung Galaxy S 4] nbeebe24:
They told you jump has to be done at a store? I did it online.
[T-Mobile Samsung Galaxy S 4] peeps67:
My local tmobile store fixed my issues finally. I went to the store close to my house and the guys there are really helpful. He got all my issues with the account fix up and today I got my white G2 in the mail.

Thanks guys at the store for taking the time to resolve my issue and spending all the time on the phone with customer care.

Thanks tmobile.
[T-Mobile Samsung Galaxy S 4] travispittman:
Complaint Box

When anything first comes out it is not buttery smooth expect a little hiccups with the first round of using jump. You got in on the opening days of jump and got a new device. You experience some turbulence but got your new phone. It is because of people like you that complain about the smallest inconveniences in a great thing that give good things bad names. If you plan on keeping up with the best and latest devices you cant beat jump. Why dont you go out and buy a 4k tv as well and complain about it looking the same as 1080p as well while you are at it. (if you dont know what I am talking about. It is because there isnt a whole lot of stuff that is 4k quality yet it is all still 1080p and that is all you would get. even though 4k is better you just have to wait for the services to come available)
[Android Q&A, Help & Troubleshooting] amamartin999:
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
[Android Q&A, Help & Troubleshooting] streetdev22:
Solution may be here soon.

No one has the stock rom on hand yet. We are working on building a custom recovery for the phone, so please be patient.

Hopefully we can have a working recovery by this weekend, then you will have a way to still access your phone.

What files did you mess up on your phone? If i know the files, I can get someone to upload the files and then you can push the files to your phone using adb. If you haven't yet, I would recommend unlocking your bootloader via the instructions here:

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

By unlocking the bootloader, you will be eligible to test the custom recovery as soon as it is available. Also, list the foiles you messed up, so that we can possibly upload them for you.

It will be a while until someone can form a stock rom update.zip for you.

Also, you can view the progress that we are making on the custom recovery.
[Android Q&A, Help & Troubleshooting] CtrlAltDelIrl:
You don't want to go into details but you still want someone to help you? Hahahahaha!!!

Good luck with that plan!
[Android Q&A, Help & Troubleshooting] Deeeno:
:confused: Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
[Android Q&A, Help & Troubleshooting] CtrlAltDelIrl:
Yes and in those cases they're usually eager to share all the details required, unlike the OP.

When the proper details are supplied it's easy to help, nobody likes to mindread here.
[Android Q&A, Help & Troubleshooting] Deeeno:
Probably doesn't know exactly what they did to mess up.. so doesn't know how to explain it.

Merely asked for the stock application to try and fix it themselves is what I gathered.

But Whatever :rolleyes:
[Android Q&A, Help & Troubleshooting] amamartin999:
Explanation.

Was using Android tweaker 2 and accidentally hit the "On Screen Navigation Keys" and then when I went to turn it off it wouldn't switch. It stayed on. Updated the T weaker app, hoping for a fix but the option disappeared and I was stuck with them. Searching the internet I found a option that allowed to disable the soft keys in the Build.prop. But when I save it and restarted the phone was stuck at the T-Mobile screen.

Also I never figured out how to do ABD it tried for a long time but it didn't work. Since I got it in October, I need to know who to send it to be repaired, since I have a warranty (But I don't really want to send it away so that's why I asked.) So, there's and explanation. I'd tell you what I edited if I could find the website.
[Android Q&A, Help & Troubleshooting] amamartin999:
ADB

Okay, I got ADB working. But if I unlock Bootloader, does that that void my warranty?

And basically I need a default Build.Prop. Thats the only file I edited.
[Android Q&A, Help & Troubleshooting] streetdev22:
Return the phone since you are under warranty, you won't be without a phone

If you are under warranty with tmobile, you should be able to get a replacement if you are on their JUMP insurance, even if it was accidental.

I would recommend first going to your tmobile store and asking them to send you a replacement(and to waive the restock fee). They will send you one by mail in a few days, then all you have to do is send the old phone back to them in the prepaid shipping package(instructions are included).

I would recommend doing this instead of unlocking your bootloader and waiting for a recovery and custom rom to come out. My belief is that unlocking your bootloader does NOT directly void your warranty, unless the company can prove that the unlocking directly bricked your phone(which it doesn't). A thread with the legality of unlocking your bootloader is found here: http://xdaforums.com/showthread.php?t=2250113

Again, I recommend just bringing in your phone and saying your phone just refuses to boot anymore since an update or something of that like. You won't have to wait long. Also, the phone is $63 on ebay, if you are uneasy about going to tmobile to return it.
[Android Q&A, Help & Troubleshooting] Prism 2:
build.prop for Android 4.1.1

default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
[Android Q&A, Help & Troubleshooting] magix01:
Dont do this, you will brake it even more, every version has specific build prop.
[Android Q&A, Help & Troubleshooting] amamartin999:
Okay, but no.

Not on insurance....

They didn't offer it at Walmart, that I know of. The real reason I got it was that I was sick of my unlocked Pantech Link (An AT&T on T-Mobile...)

And plus, I'm just broke right now -_-
[Android Q&A, Help & Troubleshooting] Prism 2:
Are you sure you have Android 4.1.2? I have the latest stock T-mobile rom (just tried updating today) and I'm "up to date" with 4.1.1 :confused:
[Android Q&A, Help & Troubleshooting] streetdev22:
How do you have 4.1.2?

That's strange. Can any other users confirm that their Prism Ii has 4.1.2?
[Android Q&A, Help & Troubleshooting] amamartin999:
Well...

Well.. I may be mistaken. But I can't check =/
[Android Q&A, Help & Troubleshooting] streetdev22:
Almost certain you have 4.1.1

Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.

I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.

To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.

If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.

Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed adb to, in order to use the adb command.

The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
[Android Q&A, Help & Troubleshooting] amamartin999:
Pushed the Build.Prop, but still does the same thing. Lost the old one though, because I forgot to rename it.
[Android Q&A, Help & Troubleshooting] streetdev22:
Try Factory Reset once more

You are stuck in a bootloop? Try factory resetting once more.

If that does not work, you may be our first live install recovery image tester, and you'd just have to wait until a custom ROM was released.
[Android Q&A, Help & Troubleshooting] amamartin999:
Reseted... Still stuck.

Omg. They must make these phones just to make us upset when they break.
[Android Q&A, Help & Troubleshooting] streetdev22:
Wait until I get the unlock code from Huawei, also some other things to try

It should be any minute now, and I will see if there are other fixes. For now, unlock your bootloader according to the guide.

We will need access to recovery anyway, through recovery, we will try wiping cache/dalvik cache if available, and that may be the fix you need.

Also: I think you may need to change the permissions on the build.prop you pushed!

You would have to change the permissions to 644 according to this thread: http://xdaforums.com/showthread.php?t=2152850&page=2

To do this, we would still need to use adb.

Commands in adb:

adb shell

remount rw

chmod 644 /system/build.prop

Also, are you sure that the file actually pushed successfully?
[Huawei Ascend P6, Mate] rupro327:
Has someone here the same problem like me? Every time if I open whatsapp/+ the resolution changes. Also if I change between chats, it gets every time smaller and smaller. It looks like it goes on tablet mode. If I delete my ram and start whatsapp again, it gets normal but than after a close or a switch of the chats, it gets again smaller. This Problem is on whatsapp+ now. On Stock whatsapp I haven't this problem, but there is also a resolution problem. like if I press menu button, the menu window is only on the half the other part is gone. I will post some screens tomorrow. Let me know if you have the same experience like me.
[Huawei Ascend P6, Mate] husen4u:
Try changing whatsapp+ theme. If problem still exist try factory reset.
[Huawei Ascend P6, Mate] rupro327:
I've already done factory reset a couple days ago. Also I've tried a lot of themes but the problem is still there. -.-
[Huawei Ascend P6, Mate] klincharov:
Try installing xposed framework and then installing the AppSettings module, or it was called something similar. There you can set specific pixel density/resolution for Whatsapp. That way I fixed similar problems with Flipboard on my chinese tab.

Good luck!
[Huawei Ascend P6, Mate] RaxToTheMax:
Hi, i recently updated to 4.4.2. KK (I went pristine as well) but when I reinstalled WhatsApp it looked different AND I can't send mp3 files anymore! Any idea on why?
[Huawei Ascend P6, Mate] rupro327:
Thx man! That fixed the half problem. It's much better now. If I change the screen (dp), the resolution jumping is still there. Only if I change the DPI, the resolution stay fixed. The DPI on the Ascend P6 is 312, if change it to 312, its all to small (very small) and the background wallpaper does no match. I've changed now to 349 DPI, this looks perfekt for me.

The first picture is with the Appsettings mod, the DPI is 349. You can see, the menu is lost in the edge.

The second picture is stock whatsapp+ with a theme. The last picture is also stock whatsapp+ with a theme, but here I've changed the chat after I made the second screenshot.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Pierre118:
I have read all KitKat topics till now. It looks nice, but still i'm not convinced to update to 4.4.2. My Note 3 at this moment : 4.3 MK2 UK rooted with Knox 0x0. (csc: Vodaphone UK)

I read posts about success, and also read posts about failure. For example :

- cannot write to SD card (or partial)

- bootlooping

- rooting failures

- soft bricking

I am curious how you think about this.
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
My honest opinion, stay on 4.3. There are a lot of bugs on 4.4.2 - at least with 4.3 you have options with ROMS etc

Some issues I have had

SD cannot write/delete

Rotation issues

STUPID battery drainage

Pain in my A$$
[Galaxy Note 3 Q&A, Help & Troubleshooting] Pierre118:
It looks like this a 'leaked' firmware, so many major bugs. But I also read success, how can that be so different?
[Galaxy Note 3 Q&A, Help & Troubleshooting] blackknightavalon:
I'm having a number of problems with 4.4.2, but they're nothing I can't work around with some tinkering. If you can't handle bugs on your phone, stay with 4.3.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ultramag69:
If you're looking for big differences you won't find it visually. Most differences are "under the hood".

Haven't had any of the problems spoken about -

SD cannot write/delete

Rotation issues

STUPID battery drainage

But then again I might just be lucky....

If you're happy with 4.3 then est to stay as you are. You will loose root though you can get it again easily enough now Chainfire has released his cf-autoroot for Kitkat (you will trip Knox however).

A lot of cosmetic mods don't work and a fair few xposed mods work partially or not at all.

framework seems to be altered so themes don't work and until these are fixed you are "srtuck" with stock android look. There are some things you can do but not the range of stuff I did in 4.3.

All up its a mixed bag... Just needs time to be cracked and hacked and all will be well again...
[Galaxy Note 3 Q&A, Help & Troubleshooting] FFC_Note3:
Hi,

I just updated my note 3 to 4.4 and it's true that there's nothing extravagantly new on the update.

But, I did notice that my device is no longer rooted. I tried rooting my note 3 via ODIN but there's a problem (bootlooping)...

What can I do about this? I want to root my device but I can't because of the 4.4 update. Is there any methods or available download that I need to do so that I can root my device? And is it possible if I can switch back to 4.3 since 4.4 I flashed was the leaked version?

Looking forward to helping me out with my problem. More power!

---------- Post added at 01:49 AM ---------- Previous post was at 01:35 AM ----------

Sir,

I noticed you mentioned about that Chainfire released a cf-autoroot for Kitkat. Where can I find this? Have you updated yours to 4.4 and is still rooted? Can you help me out? I appreciate it much. Thanks.
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Here is the file you need to root 4.4.2
[Galaxy Note 3 Q&A, Help & Troubleshooting] pete4k:
I think after upgrading to 4.42 you can't go back, can't root without tripping Knox, SD is limited, I think you can't use Appop to set program permissions (not sure if there is any replacement), ART is disabled and some other minor bugs and issues.

Come again with benefits please.
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Correct to KNOX and downgrading. Appops does work. But not natively supported. ART isn't implemented.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Estoroth:
But that's not a bug. It's a kitkat feature, apps need to be updated to work with the new permissions for sd-card access.
[Galaxy Note 3 Q&A, Help & Troubleshooting] GuestK00445:
Can I use this method (http://xdaforums.com/showpost.php?p=49047469&postcount=1127) to upgrade to Kitkat? So I'll have root but not the new knox bootloader.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Andrewtst:
If you don't play CM/AOKP/AOSP ROM and never intend to downgrade, your device is not Hong Kong Variant. Just go ahead update to 4.4.2 KitKat.

The most smooth experience I ever get in stock ROM.

No more delay when click the pull down menu for contact search at Phone Keypad. 1st open is slow but after that it is instantly open. This really important to me as I use it often, really appreciate Samsung finally fixed it.

I don't have rotation issue as small portion user report.

Solid stable.

Those facing bootloop is because either

User never tick Phone Bootloader Update.

Using not compatible custom recovery.

Accidentally flash the ROM at Hong Kong Variant Note 3.

Things to aware on KitKat.

Samsung do S View chip detection, now only Genuine Samsung S View Flip cover is working, all counterfeit and 3rd party include Spigen will stop functioning.

Due to new implementation of KitKat, need new permission for writing data to external SD card, thus making certain apps no longer able to write to SD Card. Currently they is a fixed for root user, or just wait the apps developer updates it.

No way to downgrade to any 4.3 ROM due to new bootloader, also means cannot install any CM/AOKP/AOSP until those developer updates them to new bootloader.
[Galaxy Note 3 Q&A, Help & Troubleshooting] maidangisme:
stay with 4.3, update you will regret it.

-Generic S-View case won't work ( just like Iphone ios 7 detect none genuine hardware= rip off)

-Call recording feature is NOT implement with Samsung KK (shame on Samsung), therefore call record WILL NOT work.

-New bootloader (No way to revert back older Bootloader) = IOS can not re-install older version.

-Samsung firmware is now just like f**k IOS.

-This will be my last Samsung Handset.
[Galaxy Note 3 Q&A, Help & Troubleshooting] GalaxHe:
No. You need the new bootloader to have 4.4.2 work
[Galaxy Note 3 Q&A, Help & Troubleshooting] Ry2mkk:
This sucks, android was meant to be the more open source friendly software!! It's basically becoming iOS with all the locks and restrictions it's placing everywhere, I think after this note I'm jumping ship to.. Well god knows what! It seems soon everything will be "your device will be this and you can't change that"

Let the consumer buy the product, then f*** them over time.... Thanks Samsung. Glad my new TV was an LG.

:crying:
[Galaxy Note 3 Q&A, Help & Troubleshooting] iqsoft:
Stay on 4.3

There are no two answers to this! Stay on 4.3

4.4.2 is garbage, believe me! I have tried it and am regretting it! It is slow, buggy and worse of all can crash at any time! So till Google don't release an update, don't even think about upgrading!

From a victim of 4.4.2