yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Skhulile:
Hello

I've recently been experiencing some very power battery life, losing like 11% during the night without touching the phone, so I have looking for solutions and none of them are working, I installed Gsam and it shows that "WIFI Active" drains a lot of battery and my device is held awake for like 1hr25mins through the night, that is without touching it in 4hrs. Tell me if this is normal or i'm just freaking out but I feel like it shouldn't be held awake for that long. Anyway I used to get pretty good battery life like 1 day and around 5hrs SOT, with some optimizations managed to get 9hrs of SOT with just less than a day of battery life,... but after the recent two updates U2COIK and now U3QOJ5, things have been really bad. Now since I saw WIFI sucking the most I decided to change some settings, but noticed something weird with this build I can't find "SmartSwitch" setting under WIFI like I had before, which has led me to think that it might be on by default and sucking my battery... does anyway with the build i have still have the SmartSwitch feature?? And any help with regaining my good battery life would be much appreciated, just not yet ready to trip my Knox.

Thank you
[G4] schup:
Hello,

in my infinite stupidy I updated my rom on my G4 QTEK 9100 with faria's WM6 rom without the use of shelltool (found the 5-step guide afterwards :S).

Anyhow, it went wrong and I ended up installing the original ROM again from QTEK (WI_DT_NLD_2180706_106_020710_Ship.exe).

Installing the original rom went well and my device is running again with no problems using the QTEK ROM, so I thought I'd give it another shot using the guide this time around. Only problem is, the shelltool displays my rom as this:

blversion: crossbow

device: wizard

language: wwe

brand: HTC

CID: n/a

ROM: n/a

instead of the correct information from the QTEK ROM I installed, which is a WM5 ROM in Dutch (and which works properly) :S.

My guess is that some part of the faulty installed ROM is lingering somewhere in my device :). Does it really matter and can I install the faria rom again using the shell tool (following the steps in the guide offcourse). Or do I have to fix my device properly first (in some way) before I can give it another go?

Any advice is appreciated.

***edit: feel free to move this thread if I misplaced it, didn't really know if I had to post in the upgrade, WM6 or this forum. ***
[G4] dr_tracker:
I am not an expert, but will try to help you a bit. Reading around a guide by Mfrazz, he advises to install the original ROM before using a custom one, this because it might be possible to be some leftovers lurking around, just like you said.

I would do a hard reset then install the original ROM again, test it and if necessary repeat the process until everything is working like it should. Then after that try again the custom ROM you want to install.

This is just my opinion, maybe some of the guys that REALLY know this stuff can come up with something that works better.
[G4] schup:
I had the original ROM installed before I tried the one from Faria. Afterwards my device didn't boot properly anymore, so I already did a hard-reset before installing the original from QTEK again. So I don't really know where shelltools gets the faulty information from. So your advise doesn't really help, but thx for the help anyways.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Raynbow74:
So I just dropped my phone into water. It was still working, but there was no sound anymore. Turned it off immediately, take out battery, sd card, sim card. Now what should I do? Help me please :S
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Chamelleon:
Disassembly Your phone, take out motherboard, buy some 98% alcohol, take old toothbrush and clean whole motherboard and flex connectors using alcohol. After that dry it using hair dryer to evaporate alcohol. When You be sure that it's clean and dry You can check is it working. If not go to the nearest service. Quick reaction = bigger chance to repair.
[HTC One A9] Loushi:
Hey everyone,

Im thinking to order the HTC one a9 from the US (because in canada they dont have the deep garnet color) and since on telus carrier, will the unlocked version from htc us work?

Thank you guys,

Ali
[Nexus 6 Q&A, Help & Troubleshooting] MoeDaddy:
I have tried the buildprop edit used in lollipop and it doesn't work for me. Is there anyway to enable miracast on the release version of android 6.
[Galaxy Note II Q&A, Help & Troubleshooting] jeff83:
give me linked
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
I'm curious for those who sent their phone in to get the OIS replaced did Samsung update the OS software as well? Did anyone request they not update and they still updated the software?

Thanks
[T-Mobile Samsung Galaxy S6 Edge] caspernetherlands:
I have installed unikernel on my g925t s6 edge regular edge.*

Now i need to revert to stock kernel but i can't. If i do a fresh install of the lateset build OI1 from odin the flash procedure complete succesfuly but the phone after that wont boot because it stuck at Samsung logo powered by android. And when i go to download mode Recovery mode is Samsung official and System status is custom. I tried to factory reset with recovery but nothing. I have also tried to fully wipe the phone with twrp but nothing. After i flash the official lastest build with odin the system status is still custom and the phone is stuck at Samsung logo. I have to flash this kernel again in order to boot the phone. But i need that phone works with stock kernel and stock system. I also did an efs folder wipe, which means i have flashed another efs with odin and after that imei said unknown. Than i have repair imei and have my phone back to function. But i cannot revert to stock

Any ideas ?
[LG Watch Urbane] CSUrbane:
Several times a day my watch is "freezing" and the screen displays White Snow background with colored spots. Pressing the side button for 10 seconds results in the watch restarting and returning to the same screen. Pressing and holding it for more than 20 seconds the watch shuts down. If I then restart it some time later it sometimes starts ok!

I have tried resetting this back to default but this made no difference.

Is anyone else experiencing this? Any suggestions?
[General Questions and Answers] Rajat sood:
Is any one have original rom please help me out i need that.
[Sony Xperia E1] dushandiaz:
Guys i found this video.

https://www.youtube.com/watch?v=vUAF977n9I8

the lollipop rom is made by android ice cold project for our Xperia E1(falcon).

http://dwnld.aicp-rom.com/

it could be buggy, it sure is working okay.

The video confirms it is E1 . so i guess not fake. :cool:

download the falcon zip file.

http://xdaforums.com/crossdevice-de...ent/rom-android-ice-cold-project-9-0-t3105894

i still didn't flash it. i think everyone should know about it.

i am going to try it tommorrow.it is late night.

hope it works.

Credits to AICP for supporting the E1.

:) :D :good:
[Sony Xperia E1] Saatvik Shukla:
falcon is moto g.

If you flash that thing, you will wreck your device most probably.
[Sony Xperia E1] Zsenyka:
Yep, Falcon is Moto G, FalconSS is Xperia E1
[Sony Xperia E1] Saatvik Shukla:
D2005 is E1. There is no falconss.
[Sony Xperia E1] dushandiaz:
yes you guys are correct. ;)

I didnt see SS.

but it is worth asking AICP???

Because the video seems realistic.

they might have a Rom after all.

the video is just 2 weeks old .

:fingers-crossed:

sorry for posting a new thread.

:D
[Sony Xperia E1] Kizoky:
The video you saw is maybe a fake

But more importantly, to boot into Lollipop requires a modified KK kernel that is compatible with Lollipop, because E1's kernel does not have any ART support, it does not boot.

A heavily modified Lollipop was bootlooping at CM logo because of this.

---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------

If you make a checker script, and try to flash it through CWM it will say "Got falconss" and terminates.
[Sony Xperia E1] Saatvik Shukla:
If you just look into your build.prop. there is no falconss. The device codename is D2005. You have the device. have a look for yourself.
[Sony Xperia E1] THEZAK:
I working on lollipop rom for Xperia E1 :)
[Sony Xperia E1] jameschintu:
I have try to flash the link's fist file an also falcom zip file also it didn't work... what should i do to install. i want lolipop rom......?:confused:
[Sony Xperia E1] rootdefyxt320:
That ROM is for Moto G 2013 NOT for Xperia E1. Moto G has MSM8226 chipset and Xperia E1 has MSM8210 chipset. As [MENTION=5416670]Saatvik Shukla[/MENTION] said it will not boot.
[Sony Xperia E1] jameschintu:
Android 5.1.1 lollipop for E1 (AICP rom) but the title is this. and how can i found falcons Zip for my phone.
[Sony Xperia E1] Zsenyka:
It's a misunderstanding, there is no useable 5.1 ROM for E1, THEZAK is working on one http://xdaforums.com/xperia-e1/development/xperia-e1-unofficial-cm12-t3232545 but there's no link yet.
[Sony Xperia E1] hru200:
this one is fake according to the aicp community on google plus.
[Sony Xperia E1] marijnenco:
Flash problem

Hey all,

My device can't flash this rom can your help me please?
[Sony Xperia E1] Kizoky:
Because there is no AICP ROM for E1.
[Off-topic] vladimir2989:
how would u copy protect DVD (video/photo) ?

there is a lot of tools to crack the cd/ dvd protection but i cant find any soft to protect cd/dvd from copying !

is there any way of making content of cd/dvd wacheble/ visible but prevent it from being copyed
[Off-topic] Bulldog:
there are few copy protectio for CD (audio/rom etc) look for Midbar, scurerom etc. for DVD is CSS. all those are professional copy protection.
[Off-topic] g35driver:
nero has tools to do this before your burn the cd/dvd.......
[E 2015 Q&A, Help & Troubleshooting] SteWieH:
So i have a boost mobile LTE model and i thought i got rid of my root but my OTA keeps failing to successfully install. ANy tips or tricks?

or can someone recommand me a good custom rom? i feel that the stock rom on my phone seems super laggy alot of times and hoping he upgrade would cure that
[E 2015 Q&A, Help & Troubleshooting] ASKdroid:
Try this combination

I've tried most of the roms but PAC-ROM was the best up till now with the combination of squid2's kernel!
[Nexus 5X General] Jexx11:
I'll start off by saying I didn't come up with any of this method myself, its just different information I found scattered on different threads on XDA and Reddit. Maybe some other 5X users will find it useful contained in this thread.

Secondly, this requires an unlocked bootloader, also working adb and fastboot with correct drivers for your 5X, enable USB debugging. I won't go over that here, there are plenty of other guides on how to do that, and know that it will erase all your data. As long as you can find your device via "adb devices" and "fastboot devices" you should be fine.

Lastly, you will get the corrupt data message on phone startup. I don't see any negative effects with this, other than an annoying message. Also I'm still able to use the fingerprint scanner as well as set up Andoid Pay. I can't verify Android Pay as I don't have any stores near me that accept it.

You also won't have to flash any custom recovery or root the device, which keeps it closer to stock, which hopefully will allow Android Pay to still function, hopefully someone with a Android Pay store nearby can test this to verify.

First grab TWRP for 5X from here. Save it in the same folder as your adb/fastboot install.

Make sure your phone is connected to your computer, open command prompt and verify adb sees your phone.

adb devices

Now reboot to bootloader.

adb reboot bootloader

Now we boot from TWRP without having to flash/install it.

fastboot boot twrp-2.8.7.0-bullhead.img

When TWRP finishes booting, click Mount and check the box for /system

Now we need to pull the build.prop file.

adb pull /system/build.prop

Using a text editor add this line to the end of the build.prop file and save it.

net.tethering.noprovisioning=true

Now we push it back to the phone.

adb push build.prop /system/

Make sure the permissions are correct.

adb shell chmod 644 /system/build.prop

And lastly

adb shell settings put global tether_dun_required 0

Now we just reboot

adb reboot

and your tethering should be working!

I'm currently using this method and it is working for me. I'm on Verizon with a Grandfathered Unlimited Plan, so I can't test it for any other carriers.

Most of this information I pulled from this reddit thread, I just did my best to condense it down and simplify it, and make it aimed toward the Nexus 5X specifically.

edit* People are confirming on the Reddit thread on their Nexus 6 that Android Pay is still working after making these changes!
[Nexus 5X General] peon1-9:
Thanks! This works exactly as stated, even the "corrupt data" warning on boot. :)

I will add that - this being my first Nexus device since a Galaxy Nexus - the "fastboot oem unlock" step needed prior to this guide has an additional step where you have to enable the "OEM Unlock" option in the Developer Options menu, within the booted system. After confirming this you can unlock the bootloader via the standard "fastboot oem unlock" command prior to starting this guide.
[Nexus 5X General] XF1ber:
Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!
[Nexus 5X General] ytsejam1138:
Thanks. Worked great for me. I'm on AT&T, weird thing though, I never had any problem activating the hotspot on my OG Nexus 5.
[Nexus 5X General] ijeenyus:
AWESOME!
[Nexus 5X General] olivercervera:
Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default? :(
[Nexus 5X General] Jexx11:
This method bypasses the subscription check for tethering, those of us with unlimited data have to pay a separate fee to use tethering with Verizon, and this fixes that. It should be the same for other carriers as well.
[Nexus 5X General] strongergravity:
I was so excited to play with my 5x when I got home (that and dealing with my 2 sick kids) and I completely forgot to unlock the bootloader before I got too carried away. Now all the time I spent downloading apps and such is lost. Our DSL connection is slow, so all that took one time. I've been rooting and romming way too long to make such a rookie mistake.

So, I get the joy of blowing the whole thing way and re-setting it up again...
[Nexus 5X General] paul_one:
Could you confirm the steps?

Can you confirm you can still use supersu? I thought the kernel had to allow su.

Also, I guess you can also install the bootunlock app and see if that works?
[Nexus 5X General] ravichopra:
Thank you thank you thank you!

This is huge for me.

BTW, I assume you can just push the original unmodded build.prop back for OTA updates. Anyone know if anything else is required apart from that?
[Nexus 5X General] coneguy:
Confused on why we need TWRP just to do this.
[Nexus 5X General] Jexx11:
You're not flashing twrp, just booting into it. Twrp allows you to pull and push files to /system without root, which is needed to make these changes.
[Nexus 5X General] Busnut:
Can someone confirm Android Pay actually works?
[Nexus 5X General] WizADSL:
T-Mobile/MetroPCS users additional steps to enable tethering

If you are on T-Mobile or MetroPCS you will need to perform some additional steps for tethering to work. After you have performed the steps outlined earlier in this thread do the following:

Under Settings -> More -> Cellular Networks -> Access Point Names

Touch the name of the APN that is selected (there may only be one) then:

1) change "APN Protocol" to "IPv4"

2) change "APN roaming protocol" to IPv4

3) Edit "APN Type" and add "dun" to the comma separated list so it reads something like "default,supl,mms,dun"

4) OPEN THE MENU IN THE UPPER-RIGHT AND CHOOSE SAVE!

5) You MAY have to reboot for this to take effect
[Nexus 5X General] coneguy:
Ok needing it for that reason makes sense now.
[Nexus 5X General] MarkGbe:
So... I'm getting about 30% packet loss on att with my 5x.

If I take my sim out and pop it into my nexus 6(also with marshmallow), everything is fine.

Could someone with att run some extended pings from a device connected to your phones tether and note any ping drops?

I don't know if this is a sw bug, or hardware issue.
[Nexus 5X General] Ascertion:
Does this work if the device is still encrypted?

My TWRP seems to have trouble accessing /system partition with encryption.

Sent from my Nexus 5X
[Nexus 5X General] MarkGbe:
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?
[Nexus 5X General] Ascertion:
Ah my bad. It's not reading my /sdcard partition. No matter. That's what adb is for. Please disregard my post. I'll update my progress when I get home later today and try it on my personal PC.
[Nexus 5X General] Skitals:
Yeah I get that, but I'm talking about incremental OTAs that upgrade from one specific build to another. Google doesn't post the links for these, I usually find the links on Android Police. There is no point downloading a 1GB "complete" OTA when the 20MB incremental OTA will do... I'm talking about updates going forward. The incremental OTA wont have the entire boot.img... just the bits that are different.
[Nexus 5X General] Mark12343:
I hear what your saying. I would make sure you restore the original unmodified boot.img before you flash any of those though. Me I personally download the full factory image as soon as it's available just so I have it. I guess I'm spoiled with my internet speed. Anyway it was good info you posted and hopefully it helps some other people
[Nexus 5X General] nateand:
I can confirm that the following steps worked, as outlined above.

I already have 7.0 installed and running fine on my device. I downloaded the factory image for N, extracted "boot.img" from "image-bullhead-nrd90m.zip", then used the AIK toolkit from the link (I'm on linux) and modified "default.prop" found in "ramdisk" (from opened up boot.img). I added the line "net.tethering.noprovisioning=true" to the end of the file, saved it. Then ran "repackimg.sh" to get a new file "image-new.img". Rebooted into bootloader, ran "fastboot flash boot image-new.img", then "fastboot reboot". Took FOREVER and I suspected I had a boot loop, about 5 minutes of the google/android logo spinning around with the colors. Hard restart (held down power button for a while), then it booted up normally (thank god). Ran "adb shell settings put global tether_dun_required 0", rebooted, and it works!

I'm pretty sure these are the exact steps outlined above, just want to confirm for anyone reading that this definitely works and appears to be relatively safe/easy.
[Nexus 5X General] andTab:
So tethering works on 7?

Is there a fix yet to also get Bluetooth tethering to work?

The above mentioned makes it possible to Wifi tether but Bluetooth tethering connects but passes no traffic.
[Nexus 5X General] bagsofcole:
Yep, works for me too, thanks! Since I've been using this method for a while now I figured it out (after a few failed attempts trying to flash the new file in TWRP), but for the less experienced, might want to note that you do need to boot into TWRP to pull the file (see OP) then boot into bootloader to push it.
[Nexus 5X General] Mark12343:
Bluetooth tethering works fine with this maybe you aren't going into Bluetooth settings on your phone and selecting the internet connection sharing check box after you connect your device.
[Nexus 5X General] jrotert:
Bluetooth Tethering

Works for me with Nexus 5X running 7.0 Official BT tethered to N9 tablet, albeit a little slow: 1.3mb/s vs 20+mb/s on WiFI tethering. Fine for run-of-the-mill browsing but not for streaming Hulu/Netflix etc.
[Nexus 5X General] tabormeister:
Hey! Here's a little guide that I wrote up that works for sure. In my experience, trying to edit settings db while in TWRP doesn't work. This way, you still keep Pay but get tethering too.

Obviously I'm not responsible for your mom exploding or your phone disowning you, but.....

I got tethering and Android Pay working on stock Nougat - that's Android N, folks - on a Nexus.

(confirmed will work on Marshmallow and up on 5, 5x, 6, 6p...etc.)

Thanks to [MENTION=631273]Chainfire[/MENTION], [MENTION=4268910]ManHands[/MENTION] and [MENTION=839943]interloper[/MENTION], and you!

click thanks if this helps, or buy me a beer or something.

prerequisites:

working adb and fastboot (from platform-tools in the Android SDK if you don't know where to find it)

twrp .img for your device

latest stable systemless supersu

1. be on Marshmallow or Nougat obviously

2. flash twrp

(volume down + power on nexus gets you into bootloader, then after flashing recovery, use volume buttons to scroll and power button to select recovery mode)

3. flash systemless root while booted into twrp (unsure if .supersu SYSTEMLESS=true in /data is still needed, but can't hurt - mine is still there from earlier.)

4. while still in twrp, go to mount and check system. Make sure you allow changes.

5. from your computer, do this

adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop

6. reboot into Android.

7. Install Terminal Emulator from the Play Store.

8. Launch it, and in Terminal Emulator, do this

su
settings put global tether_dun_required 0
exit

9. go into Supersu, expert, scroll to the bottom and hit full unroot. No, you don't want it to patch you back to the stock boot image or recovery*. If it hangs, just reboot and try doing it again.

10. ????

11. Profit! You should have tethering unlocked, be unrooted, and have full Android Pay goodness working.

To take an OTA, do this, because Flashfire gets confused after you've done build.prop edits -

1. go to About Phone, scroll down. Find your build number.

2. download that Nexus Factory Image.

3. Unzip it all. ALL OF IT.

4. Make sure you have Android SDK & platform-tools (or just a working Fastboot and ADB)

5. just flash boot, system, and recovery - you can now OTA with no problems. Then repeat the above guide on your new OTA. Confirmed working 10 minutes ago, OTA'ing from Marshmallow to Nougat and then getting tethering working again

ALTERNATE IF YOU PREFER FLASHFIRE:

All the above steps, but you only have to flash the System image to fix the build.prop hash fail then flashfire should work for you. Wouldn't necessarily recommend upgrading version numbers (6.0.1 to 7.0.0) with Flashfire, but who knows, it might work great! Chainfire is a wizard.

*you can do this if you want, but when I let it patch my boot image I got the dreaded "device corrupt!!!!1" message at boot. Did not try letting it flash stock recovery image.
[Nexus 5X General] Skitals:
This doesn't make any sense to me. You don't need root to edit the settings db. Boot the phone and do it via adb: "adb settings put global tether_dun_required 0"

Second, the only reason the process has changed from the first page is because editing build.prop in twrp doesn't stick in

Nougat

on the

5X

. Add the line to build.prop, boot the phone, pull build.prop and it's not there. Go back to twrp... pull build.prop and it's back. When the phone boots its sym linking an unmodified build.prop from some other partition or something. My workaround was to edit default.prop in boot.img which seems to supersede.

For whatever reason the 5X has always behaved differently than the other Nexuses.