yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] Broon:
It may sound too simple but when you close the XDA, programs still run but the LCD goes off.
[JASJAR, XDA Exec, MDA Pro General] numanoids:
I'd go with the above suggestion, but if you do need, for some reason, to leave the screen open, press and hold the power button and the light should turn off.
[JASJAR, XDA Exec, MDA Pro General] heidy:
When you mean "close", do you mean close the clam shell so that the screen faces the keyboard? How can one be sure the screen is off at that point? The light is off for sure... but the actual screen?

Turning it 'off' (standby mode) by pressing the power button would kill the modem connection.

But I don't just want the light to turn off -- under good lighting, one can still see the screen is still 'active'; and I'm afraid that prolonged usage would cause stuck pixels.

Thanks for the tips from both of you though.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] imablackhat:
We have generic 3g icon but anyway to get the generic 4g. I don't care for the Verizon one.
[HTC Droid DNA] CoyotesFan4Evr:
OK, so I haven't posted much in this forum in general because I haven't had a need to really. I find what I need read and move on. But because of that I can't post in the developer section to ask this question before I flash this ROM so I will ask it here. So I'm going to take the plunge and flash Newts NOS m7 ROM. But after reading about 60% of a 949 page thread I do have some confusion. There were some updates and patches I'm going to call them for a lack of better term. I don't need to run any type of beast mode kernel. So what patches or fixes do I need to add in order for everything to work on this ROM? And I'm choosing this one over the alpha Sense 5 ROM based on data working with Verizon and not working with the alpha. At least nothing has been posted that it's working in all aspects now. I appreciate the help and hope that I can be rocking the NOS rom by tonight before I go to bed.
[HTC Droid DNA] CoyotesFan4Evr:
Really? No help out of 60 views?
[HTC Droid DNA] nunyazz:
If you install the full rom, you don't need any of the patches.
[HTC Droid DNA] CoyotesFan4Evr:
Well I have the full app plus a couple of the other downloads that are mentioned to have off the bat. But has the ROM download been updated with the patches that fix stuff? Thank you for your response by the way.
[HTC Droid DNA] .torrented:
3.0.7 is the only thing you need to have as of today it contains everything, patches are minor small updates and newtoroot usually will tell you what patch you need when they are released.
[HTC Droid DNA] CoyotesFan4Evr:
So you are saying that the kernel patch, the call patch, and the other patch are all included in the 3.0.7 build and I shouldn't worry about them even though people are having issues with the ROM in certain areas such as what the patches fix? I'm asking for clarification because I can't afford to screw up my one and only phone. Besides Viper Rom this Nos 7 Rom seems to be the best out there for what I want until the update comes out. This is me being cautious and doing my research. I don't want to sound like a jerk. Just trying to have everything lined up right.
[HTC Droid DNA] nunyazz:
Again.... just install the full rom. All is included.. Don't see how you could be confused with that statement.
[HTC Droid DNA] .torrented:
All you really need to worry about if it says full Rom or not. If it is a full Rom flash it after that there is nothing else to do.
[HTC Droid DNA] CoyotesFan4Evr:
Thanks for the help. I should just take the plunge but like I said before I'm just trying to do all the research that I need and to be as well read on it before I just jump into something. I'm not a first time rooter or flasher of ROM's. This one just has me timid because even the latest posts in the thread of the ROM is saying there are data issues. So I hope you can see where my concern is coming from. I'll flash it tomorrow and see what happens from there though.
[HTC Droid DNA] CoyotesFan4Evr:
OK, so I just took the plunge and did the flash. One problem I have right off the bat is that Gmail keeps closing and failing. I can't have that because all of my most important e-mails come in thru that. So is there a fix or do I just have to go back to stock?
[HTC Droid DNA] nunyazz:
Never heard of that issue. I would just re-wipe and re-install the rom.
[HTC Droid DNA] twelfth:
Did you even wipe data or did you just install the rom and hope that you wouldn't have to do anything about your already installed apps?
[HTC Droid DNA] CoyotesFan4Evr:
Seriously??!! Oh just install the ROM it's totally fine. Yeah well it's not fine. GMAIL is broke and I HAVE TO HAVE IT WORK!! Come on people help me out!!
[HTC Droid DNA] nunyazz:
You won't get any help if you don't tell us what you did..... I have never heard of ANY rom that gmail doesn't work.

and YELLING AT PEOPLE DOESN'T HELP EITHER.
[HTC Droid DNA] CoyotesFan4Evr:
Well, it wasn't meant to come out as yelling. And I didn't do anything but install the ROM just like everyone kept telling me to do. Oh and the weather on the lock screen is broke too. It always says no weather data available.
[HTC Droid DNA] CoyotesFan4Evr:
Well nothing like feeling even more of an ass. I never saw the replies I had already gotten from you guys. I guess my page wouldn't refresh. I'll wipe it and re flash it on I guess. I did all the stuff I needed to do before flashing it so I"m in the clear on that one. I'm not sure as to what all the extra apps that I've never seen before are but I'm ok with that for now. Oh, um isn't there suppose to be a swipe screen to wake feature on this ROM? I can't find it.
[HTC Droid DNA] CoyotesFan4Evr:
So G-mail is back to working now. I reflashed the ROM and did a cache and dalvik cache wipe. I also did the lock screen patch and volume to wake patch. I still don't have weather on the lock screen though. And the little click sounds that are turned on for me for when I unlock or lock the screen....yeah I can't hear them.
[HTC Droid DNA] CoyotesFan4Evr:
So, everything works now. Go figure....well minus those sounds that for some reason I actually really really liked having turned on before I flashed this. Maybe they will just start working again too.
[HTC Droid DNA] twelfth:
So, in other words, all of your problems were self inflicted.

Do the flashing process properly next time and you won't have these issues.
[HTC Droid DNA] CoyotesFan4Evr:
Nope not self inflicted. I did the flash exactly the way I was suppose to. Not sure why flashing it a second time worked but it did. Now to figure out how my nanddroid back up got deleted.....or if it's just hidden and I don't know where it is. I use TWRP recovery by the way.
[Sprint Samsung Galaxy Note 3] freeza:
Here's the uncompressed MMS apk with screen on/off notification option as well as a bunch of other unlocked options.

NOTE: People who can't send large MMS to other carriers--you should make sure that what you're sending is 5MB and under. Anything over is risking it. Now that the app doesn't compress or resize your photos, that is up to you to do!

NOTE2: Some unlocked options may not work or may make the messaging app force close. I'm counting on you guys to let me know what doesn't work so I can remove it.
[Sprint Samsung Galaxy Note 3] JoshBeach:
Nice Work man!!!

:)
[Sprint Samsung Galaxy Note 3] eurominican:
Just run apk and it will replace stock one? Thanks!
[Sprint Samsung Galaxy Note 3] joe1blue:
I'm not sure was I supposed to flash this because that's what I did also what does this do just curious sorry for the questions
[Sprint Samsung Galaxy Note 3] strongsteve:
I've sent a odexed copy to freeza for posting
[Sprint Samsung Galaxy Note 3] CNexus:
Could you add a guide/walkthrough on how you did this?
[Sprint Samsung Galaxy Note 3] joe1blue:
This is what happens when I try to install the apk. I also tried to flash it and nothing happened.
[Sprint Samsung Galaxy Note 3] KennyG123:
Discussion is in here
[HD2 General] GuestK00433:
Well actually I just want my HD2 back the way it was, recently it's been giving me issues with the screen. I couldn't unlock it, and it would periodically work when I put immense pressure on the Call End button, however, after about 2 months of doing so, it stopped working completely. Normally it would work after 10-20 tries of unlocking it, but i tried for days, I tried every possible thing, and I really didn't want to resort to replacing the digitizer. Being 13 and all, it wasn't going to be easy, but I knew if my parents found out I'd be dead meat (I wouldn't blame them for going ballistic, I have a weird tendency to break things).

So I'm going to attempt a screen replacement, I've already opened it up (having an eBay account with money in it is is really helpful in my situation) and it isn't looking good... I've already snapped the ribbon cable for the lower button panel... luckily I ordered one off of eBay just in case it was on its last legs anyway. I've bought the following things.

-HTC HD2 Digitizer + Screen + All tools (Socket Digitizer) - £24.55

-T4, T5, T6, T7, and T8 Screwdriver set - £1.55

-HTC HD2 Lower button panel - £2.51

-HTC HD2 Anti-Glare Screen Protectors 5x - £1.19

-*MAYBE* HTC HD2 Rear battery cover £2.00

At first I was going to replace the digitizer until I saw all the risks, like damaging the screen itself and all that, and having to apply adhesive and using low level heat etc. So I just bought the whole assembly. Before I took it apart, I checked if I had a Socket Digitizer or a Solder Digitizer... yep, without taking it apart. I did this by holding the

Volume Down Button

and the

Red Power Button

, and I held this until I saw the 3 colour screen. On the 4th line down, this should be written 0x50 or 0x30, if it is 0x50, then you have a Socket Digitizer, if it's 0x30. It is the solder type. As you can see, my Digitizer is socket type, but this didn't really matter as I am going to replace the screen as well. I found the information about 3 coloured screen from somewhere from XDA, I can't quite remember where though.

All of those things should be coming soon (except for the button pad, it was from china) so hopefully, I will have a perfect HD2 soon, however, for the moment, I am stuck with a T-Mobile Vairy Touch 2... Oh and can someone give me suggestions for the smoothest JB ROM for the HD2?

I just hope my HD2 doesn't die in the process...

Thanks for reading, I'll update as I go along :)
[HD2 General] Mister B:
Worth noting the bootloader screen doesn't show the digitizer version always correctly when HSPL is installed, not that matters as you have a complete assembly anyway.

Only tips I will give is take a lot of care & keep all screws etc safe so not lost when re-assembly time comes. Take care when handling device not to damage snap off the spring fingers that contact against the aerials as they easily bent & break off when repositioning if not careful.

If you have lifted the entire ribbon board with volume key be very careful not to damage it or loose the small push caps on face of volume key & refit volume key properly.

When your parts turn up you can test function prior to assembly by plugging screen assembly into mainboard & attaching new button ribbon to mainboard, then hold the battery onto the mainboard contacts & press the power button & see screen & digitizer is working ok.

Good adhesive tape is needed to mount & hold the lcd to centre chassis & adding bit more tape than standard in places such as corners is not a bad thing.

Rest comes down to taking care & a bit of luck. Hope works out for you .
[HD2 General] GuestK00433:
I can confirm that the bootloader was correct as my digitizer is the socket type. Oh and, when I took everything apart to check it actually was a socket type, the volume keys fell off, I put everything back together (without the motherboard and stuff) I put the volume keys back and It didn't feel right. I couldn't press the Increase Volume Button, however when I screwed it in place it felt better -but still wobbly and it feels like it's going to fall of with a little bit of pressure.

Can I check the condition of the screen and digitizer without the lower button panel. The Screen + Digitizer should come on Monday, but since the button panel was from china, it will take 2-3 weeks. And If I put extra adhesive will the rear frame fit?

Thanks for the tips :)
[HD2 General] Mister B:
Be careful with those volume keys as the volume board is easily damaged, you will have to review that area carefully when doing final assembly.

If you have not fully stripped it yet then do not remove the flex board completely or all the cables running down by the volume key.

You can just loosen the flex ribbon across the bottom where plugs to mainboard & about 2cm+ up. With button board disconnected along with other cables the board will lift enough to access the lcd connector on the back. Use a toothpick to work the locking bar up off the lcd connector then lcd ribbon can be worked out using a tool or toothpick.

Saves a lot of work & all the tape on volume board remains factory spec with small strips wrapped round the push caps & build label is mainly untouched.

All you are doing with extra adhesive strip is putting it in a few areas that originally did not have strip laid on it & would look beneficial to aid support as none of the tapes have the same bond strength as original. Don't build up more than one layer of tape or thickness will make digi too high from housing edge.

I personally use PU40 adhesive and add 5 rice grain spots down sides & in corners & make gaps in tape for it as really holds the assembly nicely like original build were as tapes tend to come loose & lift in corners or feel spongy.

I would wait till button board turns up as very easy to test with that & other options just result in a lot of hassle & possible mishaps.

Do take care when removing & inserting the lcd ribbon as the mainboard socket is easily damaged then you will have lcd display issues or no touch & probably no chance of rectifying it. Sometimes those chinese orders can be surprisingly quick ...
[HD2 General] GuestK00433:
Thanks for the extremely helpful information!

I will take care in replacing the Digitizer, I don't know what type of adhesive to buy, do I need adhesive strips; would something like this work?

Thanks for all the info, and I really do hope it's quick...

I really don't want my parents to find out :p

EDIT:

Would this tape be sufficient?

http://www.ebay.co.uk/itm/LCDFIX-Frame-Repair-Sticker-LCD-Tape-for-HTC-HD2-T8585-Adhesive-/130999079729?pt=UK_MobilePhones_MobilePhoneAccessories_MobilePhoneFascias_JN&hash=item1e80275331
[HD2 General] Mister B:
Yes the LCDFIX frame tape would do & has the advantage of having the pre shaped black foam adhesive pads that seal & bond the top & bottom edges of digitizer.

The actual tape they supply is not that high tack as I have used it before but ok & if used with a little pu40 silicone adhesive the final build is much better long term ...

Don't think your parents should be complaining seems you are saving money & being environmentally active in repairing rather than scrapping.

Digitizer is common issue on the HD2 so probably not your bad on this occasion :)

Hope works out well & another HD2 is revived ...
[HD2 General] GuestK00433:
I will look into that PU40 Silicone Adhesive as I don't want to be constantly opening and closing my HD2 so I do want it to be long term.

I think if they find out they will think I'm going to break it. I've already broken the button board ribbon cable, but as I said before I already bought one. Yeah, I noticed the amount of people with the same issue was a lot. But I have only had this phone for like 5 months (got it on eBay for £60), thought it was a good deal... 5 months down I need to replace the screen + digitizer. Why did HTC make an amazing phone with such a common fault :(

Thanks, I hope I don't kill my precious HD2 :)
[HD2 General] Mister B:
Well they can last about 2 to 3 years before failure which not too bad. Digitizer of that screen size & minimal bezel bonding was quite unique when HD2 came out & bezel size is only just being beaten now.

Ribbons tend to get brittle with age due to heat cycles they endure from the device & the one on digitizer also flexes a little when device twisted about in your pocket or right hand side keys used hard which all helps the failure.

As you found out with button board tail they are easily torn ... Would not beat yourself up over that as most people do a lot worse when opening an HD2.

If you use pu40 or similar adhesive sealant only very little spots are required, really does hold the corners in nicely & gives a more firm untouched feeling finish to the build.

Do check everything & plan the reassembly before actually doing it so nothing missed or made awkward, also you want device assembled before sealant fully dry so can lay HD2 on its back with a thick card spacer cut slightly smaller than the digitizer then add a book or 2 as needed to help seat the new assembly on the adhesive tape & get glass sat at right height. Normally if centre chassis not bent from removing old lcd assembly the rebuild fits back rather easily & perfect.
[HD2 General] GuestK00433:
Well this is awkward...

Ah yes... so i did fix my phone, it was working perfectly!

However I forgot the key thing about myself, I destroy everything. Yep! The same day I fixed it, I was outside and i dropped it face first and now it has stopped working completely. The poor thing fell from quite a distance.

To make matters worst, I somehow lost my SIM Card, which had a good amount of credit. Luckily I'd been saving up and I've bought a HTC Sensation. Damn I miss my HD2
[T-Mobile Samsung Galaxy S 4] MrPapito429:
Can any one confirm if this rom is working for our phones, like lte, wifi, etc http://xdaforums.com/showthread.php?t=2402208
[T-Mobile Samsung Galaxy S 4] PesTicide.:
I couldn't mind using Sense on our Galaxy S4. :good:
[Nexus 7 General] eWich:
Hello I'm trying connect my Nexus 7 (2013) Tablet to pc and its doesn't working for me.

Windows 8.1 64 Bit.

Please Help.
[Nexus 7 General] eWich:
Ok I Fixed a ADB drivers but now i cant connect Tablet -> PC ( MTP)
[Nexus 7 General] GoldenNexus7:
Dude, this is already a known problem with the first generation and second generation nexus 7s when connecting via USB to a windows 8 laptop. I've had this problem myself and I contacted Asus support which was really helpful but the Asus representative could not fix my problem. There was some talk of a PC-sync update which would be carried out to nexus 7 devices, but it has been proven untrue. This problem however occurs 85 percent of the time when attempting to obtain adb with the computer.

There are some things you can try though,

1. You can go to nexus 7 developer options and turn USB debugging on and turn on camera type connection at the same time. Delete any former file connections which were installed on the computer at first attempt FIRST!

2. Disable windows 8 signature check. Please Google how to disable drivers check windows 8.

3.download drivers from many different sources, I recommend the Asus drivers, universal or Google drivers for the nexus 7 then install the drivers manually on PC.

---------- Post added at 06:53 PM ---------- Previous post was at 06:50 PM ----------

Use ptp with USB debugging and turn off mtp. That method worked for my first generation nexus 7 when trying to confirm adb on windows 7.

Then to check if it is working, please open your command line or cmd from your windows 8 computer and type in adb devices exactly as I just typed it and if the command line picks up your device, good to go. Remember the device has to be plugged first.
[Nexus 7 General] eWich:
Nothing Working ;/
[Nexus 7 General] GoldenNexus7:
Well my friend for now there is no solution, my suggestion is that you use an alternate method to share file with your nexus 7 to your computer, use a app called airdroid. Download it for free at the Google play store, let's you easily transfer files from your device to the computer using the internet, turn on airdroid on your device and then go to the airdroid website on your computer, log in and then you are good to go. Sorry that you couldn't fix the issue as well.......
[Nexus 7 General] eWich:
Thx for help :(
[Nexus 7 General] GldRush98:
No one here can help. It's a Windows/Driver issue. Thank Microsoft.
[Nexus 7 General] Groid:
Try this with usb debugging on and MTP selected as a media device:

http://xdaforums.com/showpost.php?p=46440030&postcount=25
[Nexus 7 General] eWich:
Nothing :<
[Nexus 7 General] annoyingduck:
I posted this a little ways back when I switched to 8.1:

http://xdaforums.com/showthread.php?p=46589201

Windows 8.1 upgrade driver reinstall
[Nexus 7 General] worldwidepmp:
All I did was uninstall the adb composite interface driver, plug the Nexus back in and let it install on its own and I was back in business.
[Nexus 7 General] eWich:
' Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP.'

I'm @ this moment and cant find MTP on list.. when i pick patch to google drivers its shows
[Nexus 7 General] gamer649:
For me I had to download Wugs Nexus Root Toolkit from the android dev section and use that to get all the drivers installed properly.
[Nexus 7 General] eWich:
I have NRT too ADB drivers are good but cant connect with MTP ...
[Nexus 7 General] eWich:
Guys i found solution to connect Nexus 7 on Windows 8.1 :) YAY !! :)
[Nexus 7 General] xateeq:
Idont know what i did but when i connect nexus 7 (android booted up) it connect in mass storage mode. and when i boot into recovery or fastboot it loods into that mode auto. i guess i am having best of both words :D
[Nexus 7 General] sergap:
I've solved it

So...

I've had almost the same problem with Nexus 7 (first gen) and 8.1 64 bit (non-prof).

Symptoms were almost the same - USB cable (to USB2 and/or USB3 ports) - and I was able to see Nexus 7 device in 'this comp' - and nothing more.

Solution to see (and transfer) folders/files _via_ usb cable is ridiculous, stupid and idiotic (all three together) - just turn on Bluetooth (and pair it with Win8.1 if it's not paired already) on Nexus 7 (usb connection remains in place)....

That's all...

exactly the same situation and solution to Nexus 7 (2013)
[Nexus 7 General] Loganberry:
A solution... of sorts (here be dragons)

WARNING - this is how I fixed it on my system. I offer no guarantees that this will work for you. The folder and/or file names may well be different on your system. Do not delve into C:\Windows and C:\Windows\System32 without either knowing what you're doing (I've been administering Windows since 1998 and NT 4.0) or being prepared to restore from backup.

So, with that caveat out of the way, here we go.

After playing around with Helium, WugFresh, and more, while unlocking my Nexus 7, I had a rogue ADB driver on my system and no amount of uninstallation would kill it. This post (http://xdaforums.com/showthread.php?p=46589201) gave me a clue. The "Nexus 7" device had three driver files, two of which were signed by ClockworkMod:

C:\Windows\System32\WdfCoInstaller01009.dll
C:\Windows\System32\WinUSBCoInstaller2.dll

So I deleted those two files and tried again. No dice. The driver files were restored and the device was still showing up as an ADB device instead of letting me browse the Nexus' storage via MTP.

I then went digging...

Windows 8.1 kept cached copies of those driver files in

C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_05f4ed2dfa7ff8b9

I removed that directory (the one beginning with "android") and reconnected my Nexus 7. This time Windows couldn't restore the ADB drivers from its cache (Plug & Play is useful, but not without its idiosyncrasies) so it installed the MTP storage driver just like I wanted.

I can now browse my Nexus 7 via USB on Windows 8.1