yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] flipster64:
I gather the non-OTA (Recovery zips and Odin tars) out on the official root66 page don't require any particular modem pre-flashed since it doesn't mention it, but given my experience I hate to assume. I'm guessing the modems they need are included in the ROMs there.

Right? (*cringe*)
[T-Mobile, Samsung Galaxy SIII] Perseus:
Since now you have the AT&T 4.3 Modem working fine with your IMEI, perhaps you *could* try and flash just the StockMod Rom for T-Mobile. Don't flash the T-Mo modem or you will loose IMEI.

I am hoping that the T-Mo 4.3 Stockmod rom is compatible with the ATT 4.3 Modem. So as a result you will get ATT modem (to keep IMEI intact) and T-Mo's Stcokmod for Wireless Calling.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Yeah, me too.

I might NOT lose IMEI ... if DocHoliday is right, the fact that I nvbackup'd *should* protect me. If it loses it it should automatically pick it up from the nvbackup.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you flash an incompatible modem, the imei may read unknown. Its still there but the modem is wrong. The backup I mentioned wont help that situation because technically the imei is intact.
[T-Mobile, Samsung Galaxy SIII] flipster64:
And then if I subsequently flash a modem compatible with that ROM, it should pick it up, right? That's what I was thinking.

I'm going to run it like this for a few days and see how I like it. Besides, I don't see a Root66 zip out there and I don't think Odin's going to want to flash one of the tar.md5's to this phone because it'll see it's not really a T999. Could be wrong, but I kept running into that with the last one and ended up flashing a different zip.

For the record, here's what I think happened to me last night. I flashed the modem for the new ROM, which wasn't compatible with the 4.1.1 ROM that it came with, so it didn't show me the nvdata when I booted into 4.1.1.

Then I flashed the Team Inferno ROM and when I checked the nvdata after it booted into Android, the system really hadn't thoroughly finished updating itself. On top of that, through an unfortunate coincidence in screen position, I thought the IMEI was still gone, corroborated by the fact that the status said NO NETWORK. Like I said, the reception in my house is not great and there are dead spots.

Funny thing is ... down at the bottom of the screen (attached) it looks like the IMEI is all dashes. But what we're really seeing is the tops of the numbers! DOH!

I took the sim out at that point, but should have realized the IMEI was in fact there when the phone came back up and said "Emergency Calls Only".

This morning that occurred to me, so I looked at the status and actually saw the IMEI, so I put the SIM back in and voila!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
This is correct.

Root66 is in general for use in Odin only. Id probably agree to play it safe here at this point. The closest you will likely get to this with a recovery flashable rom is saranhi's original StockMod or my Stock deodexed rom. (Pretty much the same, id go with saranhi's as the thread is more active for support. Thst is, if you are looking for one to flash.)

so is everything good for you at this point?
[T-Mobile, Samsung Galaxy SIII] flipster64:
Yes, I believe so. Battery life with this mod seems ... unprecedented. Had the GPS activated full time all afternoon yesterday and battery at 6:00pm was still 82%! Usually that sucks battery like The Tick™ at a soda fountain.

Playing it safe is the plan. I may try at some point to get a TMO mod on here, and thanks for the suggestion -- but only if I am convinced I can safely get back to this one if it doesn't work. I may have to just give up on WiFi calling. Everything ELSE about this seems to be working great.

I want to thank everyone here who chimed in, especially Perseus71 and DocHoliday77.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Glad to hear it! If you havent already, and you have cwm or twrp recovery installed, make a nandroid backup and keep a copy on your computer, just in case. If you do ever try to flash another rom, this should be able to restore to the state its in now should things not go well.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Good to know everything is working Great. As Doc said, [MENTION=3760726]saranhai[/MENTION]'s StockMod for T-mo (Same one I had mentioned in case you are confused) can be flashed via Custom Recovery after a complete Nandroid. Make Sure NOT to flash the modem that thread recommends. Best case scenario you will get Wi-Fi Calling. Worst Case, it won't boot or won't have signal. Restoring Nandroid will bring you back to current state.

Either way is all right. Glad you are a happy camper.
[T-Mobile, Samsung Galaxy SIII] flipster64:
The REST of the story.

You guys knew I wouldn't just be able to let it rest, right? :cowboy:

Flashed the TMOBILE Rom Perseus71 suggested. Everything came up fine except ... for WiFi calling. When I tried to enable it it said " ER05 Invalid Sim". Incidentally, the phone (probably due to build.prop) now shows up to Windows as a T999.

Looked on the forums, and several people said just call T-Mobile and have them reset your iHLR. I called ... T-Mobile said "Your SIM is 10 years old, you need a new one".

I got a new one (they didn't charge for it since it was a tech issue)

It works.

Yay.

So apparently you can, using an i747 modem (the particular one I flashed to put the ATT Rom on it) and then flash a T999 ROM on it, and you get a functional T-Mobile phone.

Now I just wish I had the on-screen keyboard the Team Inferno ATT StockMod had. With the numbers across the top. Bet I can find a way to alter that, too :)

Thanks, guys.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Glad to have it all working out to your liking. :good:

There are bunch of Keyboard Apps in Play Store. Particularly Swiftkey seems popular one. On the other hand, the Google Keyboard might just be what the Doctor Ordered ?
[T-Mobile, Samsung Galaxy SIII] flipster64:
In the immortal words of Farmer Hoggett, "That'll do, pig. That'll do." :)

Thank you!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The note 3 keyboard has the numbers across the top. Should be in T&A section. ;)

Or pull the apk from the rom and copy to /system/app.
[T-Mobile, Samsung Galaxy SIII] scifan:
So, which modem were you using on your I747 that worked fine on T-Mobile? (and are you getting 1700 mhz hspa+ or just LTE and edge?)
[T-Mobile, Samsung Galaxy SIII] flipster64:
Oh... wow... missed this note, sorry.

Um ... have to go back to that thread to find out. Hang on, I can find it if you still need it.
[T-Mobile, Samsung Galaxy SIII] flipster64:
The more I think about it ....

I can't really say I can verify it ever actually DID LTE. I just know the i747 has an LTE antenna. T-Mobile did NOT have LTE here at the time. But I did get HPSA+, because I did get a 4G signal here, which is all T-Mobile offered at the time.

The kicker is, I accidentally knocked that phone off of a table and destroyed (it landed just exactly wrong) a couple of months after I got it working. Ended up ordering a T-999 ... and got a real one this time. Which does NOT have an LTE antenna. But now T-Mobile has LTE here. I'm still getting HPSA+, and I'll just live with it.
[Android Q&A, Help & Troubleshooting] andyjm:
Hi,

my gfs S3 mini display keeps lighting up and the home button has stopped working. The only way to stop this is by closing all apps and turning off the internet. This sometimes works. When charging and the phone is off the display lights up then also. Does this sound like a hardware fault?
[Moto X Q&A] ghstudio:
I have a Verizon DE moto-x (now running 4.2.2) and a 2014 MB linked together using bluetooth. The line worked perfectly with my galaxy nexus but now with my new moto-x, the bluetooth link drops at random times, sometimes in the middle of a call. This happened with android 4.0/4.2 so it's not the new update. It does reconnect automatically...but that drop shouldn't happen. I don't think it has anything to do with the MB Comand unit which never lost it's link to the nexus.....so there seems to be a problem in the moto-x bluetooth implementation...or it's interaction with something else running on my moto-x

Does anyone else have this problem...or hopefully, has anyone had this problem and figured out how to fix it?
[Moto X Q&A] someguyatx:
No issues with the bluetooth connection to my Hyundai. Do you have any power saver apps or anything like tasker that could turn things on or off?
[Moto X Q&A] KennyG123:
Questions and help issues go in Q&A and Help section

Thread moved

Thanks

FNSM
[HTC First] lastrastuff:
Is there any chance that the HTC First will have a 4.3 or a 4.2 upgrade any time soon? Or is it just not a possibility yet?
[HTC First] russian392:
BOTH HTC and ATT have denied any future updating or support for this device...aka "discontinued" as they say...although its not a bad device and with the resources that HTC has they could easily pull of an update since the one mini is pretty much a clone.

To get cyanogenmod support we need to be a bigger community and although the device is pretty good, i guess we wont get official CM.

Ports? Um people have tried and so far zero results...we know its possible just no dev has bought himself a first, they go with the One, or the Nexus 5...u know the more popular stuff (which should be an apple thing. Android fans should go for the promising devices and not whats popular or whats good).

so...we are dead.
[HTC First] lastrastuff:
Ah well darn. I found some stuff online that let me upgrade some select apps to look and feel like 4.3, but it just wasn't the same. It seems like the Myst has a lot of potential, especially with being able to over clock to 1.7Ghz. I think everyone sees it as the "Facebook phone" which is really unappealing to the majority of the Android market who tend be a little more tech savy and less into sharing every detail of their life on Facebook. I think the first thing most of us did with the phone was remove the Facebook launcher anyways. Thanks for your help!
[HTC First] russian392:
Yes i have done that to my device...there is a android 4.2 clock somewhere in this HTC First forum that i used to replace the uselss 4.1 clock. You just need to find the original clock apk in /System/App and /Data/data and /Data/app and remove it. Then install that clock instead.

The Myst / First has even more potential. The cpu was originally developed to be clocked BY DEFAULT at 1.7GHz, so it can be overclocked to 2Ghz easy.

Yeah i just removed that launcher, but for some reason on the First most launchers LAG like crazy and the best one i found so far is Nova. And yes the facebook marketing was a fail BUT i think it was more of a test run for the hardware. Because now HTC has the One Mini and the desire 601 (i think its the 601) that have very similar/same hardware.

Personally i am loving this phone. Its not too big like a 4.7 inch, but its not too small like a 4 inch. Its perfectly proportionate, its not wide like the old bulky htc phones which had the 2:1 aspect ratio. So it really is a great phone. The glass is shatter resistant. Metal will scratch it deeply and if dropped, the body dents (its actually aluminum with a soft touch finish!) so you can just bend the body back to how it was and it wont seem dented. The body does scratch easy though:( and ive cracked the screen in the top corner but thank god no shatter, it just a crack that i cant feel anyways...also the glass chips easy, like pieces come off lol

Overall i think its worth my 140 bucks when i got it new off contract
[HTC First] lastrastuff:
I agree! Its an excellent phone and works very well. The default Google launcher works very well for me, but I think I'm going to try Nova now and see if it works any better. Have you overclocked yours to 2ghz? Did you have to flash a new kernel? Have you had any experience with Google Music lagging on lock screened playback?
[HTC First] russian392:
No i haven't over clocked. i actually under clocked. I run my phone at 1GHz performance governor with deadline as my I/O scheduler.

No google music works fine for me. i have over 160 songs downloaded to the device that i bought.

You can flash a new kernel and idk what the max is on that, but you would need to do a factory reset.
[Nexus 4 Q&A, Help & Troubleshooting] HamzaEzzaidane:
Hello! i got Nexus 4 with Android Jelly Bean 4.3 it was work perfectly, sometimes i dropped it but it still working, but after upgrading to kitkat 4.4.2 exactly when i drop it the camera problem begins i though its a hardware problem but from time to time the camera works 5 or 10 min and back to say CAN'T CONNECT TO THE CAMERA i tried everything with no solution from hard reset the phone to install custom roms and root unroot unlock the bootloader to lock it install stock 4.2.2 and 4.3 and 4.4 and 4.4.2 all of that doesn't work but im sure the problem in the 4.4.2 kitkat cuz all who has nexus 4 or 5 are complaining this problem after upgrading to kitkat 4.4.2 sorry for my bad english and i hope find a solution nearly thanks!
[Nexus 4 Q&A, Help & Troubleshooting] Mashed_Potatoes:
Find the Camera app in Apps, and clear the data & cache. Reboot. If it doesn't work, i think it's hardware.
[Nexus 4 Q&A, Help & Troubleshooting] RolF2:
its time to check camera connector
[Nexus 4 Q&A, Help & Troubleshooting] HamzaEzzaidane:
i did that more than 100000000 time and i went into safe mode :/ and with no result :( and its not hardware problem cuz from time to time the camera works for 10 or 15 min and back to the problem :/
[Nexus 4 Q&A, Help & Troubleshooting] HamzaEzzaidane:
how to do that? there is any video explane this one?
[Nexus 4 Q&A, Help & Troubleshooting] Mashed_Potatoes:
I don't know then, sorry....it is usually software related
[Nexus 4 Q&A, Help & Troubleshooting] HamzaEzzaidane:
so is there any more ideas?
[Verizon Galaxy Note 3 Themes and Apps] kalkat579:
This is a theme created for my owN enjoyment it based off of tw 4.3 it is anime based with my personal favorite theme color screens below

If You Like my Work Please Leave Thanks

any suggestions let me know andi will see what i can do

im looking for suggestions on a custom Flashbar (multiwindow bar) tell me what you would like to see

DOWNLOAD HERE
[Verizon Samsung Galaxy Note II] dillonorden:
I know in order to mount a usb to my phone I need a otg cable but I was curious if there was a work around. I have a usb to mini usb adapter to plug in a usb device but my phone doesn't reconize it. If not its cool just curious
[Google Chromecast] tomkiv:
I've posted chrome extension that allows to stream mp4 files on the pages to Chromecast. I can't post links :(, so you'll have to search for it in the chrome Web Store, just search for "chromecast webcast"

It's early preview and is buggy. The idea it that it detects when .mp4 file is played on the page and adds page action to omnibox. Clicking there will show you list of video files found on the page and screenshot if it can get one.

To cast to Chromecast you currently are sent away to simple site with player that supports Chromecast. It turned out to be forbidden to cast video from extension, that's why for now this workaround.

I would appreciate feedback and overall thoughts if this extension is useful.
[Google Chromecast] drivenby:
This sounds like vget
[Google Chromecast] tomkiv:
yes to some point, but vget doesn't support Chromecast yet. Extension page says support will be added soon.
[Google Chromecast] DJames1:
Installed, but doesn't seem to work for me. I tried opening a couple of local mp4 files in Chrome, and also mp4 streams from the internet archive site suggested earlier to test vGet, like: https://archive.org/details/dick_tracy_detctive

The Webcast symbol never appeared.
[Google Chromecast] tomkiv:
It's not supposed to work with local files. There are other extensions to do that. It works only with embedded HTML videos.

Example with on the link didn't work because it was on HTTPS. I changed permissions to support https and updated extension. In ~60 minutes it will get published. When it updates for you it should work on the example you sent. (You might need to restart browser to force refresh extension).

Meanwhile it does work on site like Vimeo :).
[Google Chromecast] DJames1:
Ok, it works now. The controls seem to be limited to Pause/Play.
[Android Q&A, Help & Troubleshooting] lets_zock:
Hi!

I'm currently working on a little rom for myself, and I read that Google's planing to release a new android version soon (4.4.3) because of the battery issue on the N5. I know that many roms just merge the new release in their repo when it's just a minor release. (android-4.4.2_r1->android-4.4.2_r2) How can I do this?
[Android Q&A, Help & Troubleshooting] brajesh.sharma87:
This should be helpful.

https://github.com/Mahdi-Rom/platform_manifest/commit/28a902bf703858d62a88b702f8508f7e58d28ab8
[Android Q&A, Help & Troubleshooting] 920981023:
谢谢 我是来自中国的学习者 但是权限太低了

谢谢 我是来自中国的学习者 但是权限太低了
[8125, K-JAM, P4300, MDA Vario General] creynish:
Sorry if this has been asked but i could not find it through search.

If i try to transfer file or picture or ringtone to another phone i dont have beam by bluetooth.

The manual says right click then beam file but this only opens infra red screen.

I dont seem to have bluetooth for transfering but i can connect to other devices and use hands free in car no problem.

Any ideas?

Clive
[8125, K-JAM, P4300, MDA Vario General] Tezcatlipoca:
You need to edit the registry to enable OBEX transfer:

http://xdaforums.com/viewtopic.php?p=289941#289941
[8125, K-JAM, P4300, MDA Vario General] lsnizzle:
it still doesnt work

even with that registry tweak, it won't show any options to transfer files. any other solution?
[8125, K-JAM, P4300, MDA Vario General] creynish:
how do you see registry

cant find registry how do i get into it to edit it

clive
[8125, K-JAM, P4300, MDA Vario General] Koksie:
I found out that that reg tweak does the same as in Start-Settings-Connections-Beam. Tick the box receive all incoming beams and the setting in the registry switches from 0 to 1. I do not advise anyone to change it to a 1 in the registry, since that means that your infrared port is also active all the time, which is battery consuming.

For sending a file, turn on bluetooth and tap and hold the file in File Explorer. Than select beam file. It will start with looking for infrared ports but after it finds none, it will automatically continue to look for bluetooth connections. it will then ask the other device to accept the connection and start sending. For receiving a file, you have to tick "accept all incoming beams" in the settings-connections menu as well.

Concluding: there is no beam by bluetooth menu, it is the same menu that the infrared connection uses. It is somewhat tiresome that it starts with IRdA first, perhaps a reg hack can change that, but I don't use it often enough to find out.
[8125, K-JAM, P4300, MDA Vario General] creynish:
looks correct

hmm !

seems to be ok i tried this and it transfered files i hid my nokia in the draw but it found it immediately on the infrared screen seems to be saying it is sending by infrared but i thought that would not work if they were lined up.

Will try with nokia in another romm then will be convinced it is sending by bluetooth

thanks for your help

clive
[8125, K-JAM, P4300, MDA Vario General] Koksie:
You're welcome. It is not very clever design, hiding the BT interface in the infrared beam menu, but it does work! Be sure it is sending by BT, for infrared there has to be a line of sight connection, so putting your Nokia in a drawer rules out infrared.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ahmetgiray37:
Hi everyone, completely S5 style that will make rum weather widget theme and also with the general theme ringtones and icons S5 S5 thank you in advance if you have friends that are capable of Rom.

SM-N900 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note 3 Q&A, Help & Troubleshooting] stanley08:
Posted in the wrong section mate...
[Android Apps and Games] orbin:
Boot Logs

Want boot statistics?

Turned your phone off or ran out of battery, and now want to know how long you were unavailable?

Suspect your device to be out-of-order?

Boot Logs logs your device's boots (and shutdowns), a.k.a. when was your device powered on and off.

Using Boot Logs, you can:

- Review the logs

- Sort by boot date or downtime (ascending or descending)

- Filter logs by date: display only logs from last year, last month, last week, last 3 days, last 2 days and today (there is also an option to display all)

- View your device's current uptime (time since last boot)

​
[Nexus 7 (2013) Q&A] m@h:
Hi all,

I recently damaged the micro usb socket on my Nexus 7 2013, which stopped it from charging. After some searching I found a replacement pcb (daughterboard / lower motherboard pcb) from Asus parts. I fitted the board and the tablet will now charge. Unfortunately the touchscreen is now completely unresponsive!

At first I thought I had damaged the digitizer or ribbon cable in the disassembly process, but to check I re-fitted the damaged board. The touchscreen worked again!

So I now wonder if there is some issue with swapping boards on the Nexus 7 2013. I checked the part number etc of both boards and they are identical. So I'm confused as to why this problem has occurred.

Does anyone know about this issue and how I can resolve it please? I have been very careful in swapping out the parts and cannot see any damage to any components.

Any help would be greatly appreciated!
[Nexus 7 (2013) Q&A] dottat:
So does the screen work or not? You probably just had it temporarily not detected by the system. Had you tried holding the power button for a minute to force a reboot?? Probably would have worked.
[Nexus 7 (2013) Q&A] m@h:
Thanks dottat, but that does not seem to cure the problem. It's a weird one. The screen is on and displaying as usual, just no response from digitizer. Do you think it is possible that the board is simply faulty? It seems unlikely seeing as it will allow the Nexus to charge, power on etc. Asus parts have agreed to send me another in the meantime so I will report back when it arrives.
[Nexus 7 (2013) Q&A] m@h:
Ok so the new board arrived today, fitted it with no issues but unfortunately the problem still persists. It is strange that the touchscreen works with the original board, there must be something I'm missing!
[Nexus 7 (2013) Q&A] plznote:
I know this isn't a solution to the current problem, but how about a wireless charger?
[Nexus 7 (2013) Q&A] m@h:
I took a risk last night and removed the damaged micro sd socket from the original board and replaced it with the good one from the new board. The tablet will charge now and the touchscreen is working, although it is very unpredictable, think I may have damaged the ribbon cable terminals on the board from too much swapping over.

I really need to get the new board working so I can make sure it is just the board at fault, so I know I haven't damaged the digitizer or its ribbon cable.
[Nexus 7 (2013) Q&A] phonefreaks:
There are a few revisions of that daughterboard. On the board there is a stamp that identifies any revision. If it is the original it has no revision number stamp.

It sounds now as though you have damaged something other than the board such as the flex cable as you have suggested, but the incorrect revision model was the original cause of your digitizer issue. 99%.

Thanks.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] brav9565:
I have learned all I know about flashing ROM's and rooting phones thanks to all of the helpful people here! I'm running the latest stock NAE, which I found as an automatic download via KIES, on my unlocked sph l720, with the StraightTalk network and AT&T SIM. Everything works great except for the data, it will toggle on, but not actually receive data.

Has anyone else came across this issue and been able to resolve it? Or any advice for a new guy? I'd really appreciate it!

-Adrian
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Dez Playamade:
Dont use the lte apn for att use the one that has cingular in it and you will be connected to hspa+/4G