yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] akkh99:
3.5. in TWRP mount /vendor partition and run on the PC (this fix for disable ForceEncryption):

adb push fstab.qcom.txt /vendor/etc/fstab.qcom

3.6. in TWRP mount /system partition and run adb:

adb push uinput-goodix.kl.txt /system/system/usr/keylayout/uinput-goodix.kl

When I do these steps, it says failed.

I mount the mentioned partition, then go to adb sideload and run these commands on pc, right?

After that, I boot system and it bootloops. How to fix that? Also, can i just simply flash zip to disable FE?

P.S after I've downgraded to stock oreo, my sim slots changed. When I place sim card in slot 1, the phone shows card is in slot 2 and vice versa. How to fix this.
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
yes, just flash zip

no need this step, all newest GSI have fixed fp ghost-taps

"adb sideload" is wrong here, you shouldn't have activated it

flash modem-fix zip
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] akkh99:
flash modem-fix zip[/QUOTE]

I can't find fix-modem.zip
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
https://xdaforums.com/showpost.php?p=78892919&postcount=1
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] akkh99:
Is there a way to re-calibrate accelerometer and proximity sensor? I've tried some apps from playstore but it only works for a while.

Sorry for off-topic post.
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
oh i really don't know how to open engineering menu in the GSI

try to ask in phhAOSP tg chat https://t.me/phhtreble
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
man it's oreo.

is't this rom for pie?
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
Camera and flashlight full-bricked...
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
aosp v117 on the 9.6.11 base

all works fine, see attachments
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
Reflashed Magisk and all working fine!

Thanks for always supporting us man
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
Man how can i fix in-call mute?
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
what do you mean? explain. i didn't have problems with calls
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
when I answer a call, there is no voice exchange

i hear nothing
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
i'm never faced

i know that problem exist when used Pie vendor + Oreo kernel. check you installation
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
using your DragonHeart v3.3
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
I don't have ideas... try to reinstall all from zero and do all right
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
hey, does vanilla/no su version have google apps or i have to manually install via TWRP?
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
gapps not included
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] remained:
i think gapps for pie, am i right?
[Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth] eremitein:
yes, pico or nano recommended
[Asus ZenPad 10 Questions & Answers] Gipiv:
Hi,

having a few problems with a screen replacement of this tablet. The original screen cracked and I have tried to replace the screen twice but in both times the replacement screen is out of calibration. By that I mean that the touch area does not correspond to anything (ie any menus or buttons) on the screen making the tablet unusable.

I have the tablet updated to the latest available upgrade and factory reset.

Any ideas on how to get around this ?

Thanks in advance for any help.
[Upgrading, Modifying and Unlocking] Killer_2008:
how i can unlock Spv M3100 any body helpme plz .......................any body post any trick plz........
[Upgrading, Modifying and Unlocking] scousemartin:
for one why are you asking this here, of all places. does this forum say unlocking requests. I dont think so. Try searching for tytn sim unlocking as that is what you want
[Xiaomi Mi A2 / 6X Questions & Answers] jprock85:
Hi, so I got an A2 which has been submerged in water for a while. I was not turning on at all (just showing the white led light blinking), so I bought a new USB part and battery for it, replaced it, and now it seems to react.

However, it keeps switching between the charging logo for a second, then vibrates and shows the Android One logo (this switch goes on and on forever). I have tried the button combo to go into recovery, but as soon as the Android recovery boot logo appears, it'll still timeout into the charging logo.

Does anyone know what may be going on? Or what component to replace? (the phone was only days old when it accidentally got soaked, so everything is new and it's a shame to just throw it away)
[HTC 10 Questions & Answers] FTWDiesel:
Hello everyone! Some time ago I rooted my phone + used custom Leedroid ROM. Unfortunately I forgot how did I do that and right now I am expiriencing some problems with my phone. I would love to update my phone. I am considering to change the ROM too. Right now my phone uses android 7.0 so i would like to update that. I have the TWRP recovery installed but probably outdated version.

Could anyone help me please to get through this without my phone getting messed up? I am little bit lost in these kernel, ROM and recovery words.
[HTC 10 Questions & Answers] FTWDiesel:
I can provide any information required about the phone.
[HTC 10 Questions & Answers] Mr Hofs:
Don't open questions in the rom development section, has nothing to do here.
[HTC 10 Questions & Answers] andybones:
1) update TWRP (plenty of tutorials on how to do this)

2) download ROM of choice

3) flash the ROM in TWRP

Edit: answers in your other thread.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
Thread closed as duplicated with https://xdaforums.com/pixel-3-xl/help/call-announcer-t3893296/post78752007#post78752007
[OnePlus 3 Accessories] lockac:
Guys im trying to track down a proper dash charge cable i only need small one as it goes with my dash charge power brick. Now i could carry around my wall cable but thats too long. Checked the threads and amazon ebay etc cannot fine one is that size and is defiantly going to dash charge cable i currently have does not when tested.

Anyone got one they can recommend?
[OnePlus 3 Accessories] skymera:
Smallest is 100cm

https://www.oneplus.com/uk/dash-type-c-cable
[Nook Touch General] Winston S.:
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://xdaforums.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.

The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.

Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.

Thanks!
[Nook Touch General] nmyshkin:
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://xdaforums.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I

can

tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://xdaforums.com/nook-touch/general/battery-usage-phone-apk-t3341370
[Nook Touch General] Winston S.:
Thank you for all your work, you are very methodic and logical, and I appreciate your generosity sharing all your knowledge about the NST (I have been reading up on different things here before I decided to buy one.) :good:

So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
[Nook Touch General] nmyshkin:
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.

So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
[Nook Touch General] Winston S.:
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?

And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.

EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://xdaforums.com/showpost.php?p=34433959&postcount=3

Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.

Is there a preferred way to do this and still keep the device registered and battery life unscathed?

I appreciate your help!
[Nook Touch General] nmyshkin:
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.

OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.

Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).

Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
[Nook Touch General] Winston S.:
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)

So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?

I can't wait for the battery consumption to be normal, because I am really enjoying my NST with its great ergonomy and the ability to install different readers. Mine is going to be a dedicated offline ebook reader, but a great one. And much of the reason it is so amazing is thanks to folks like you and Renate who have contributed so much. :good:
[Nook Touch General] nmyshkin:
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.

As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life :)
[Nook Touch General] Winston S.:
Thank you for clarifying that, I think I have had an overdose of information from reading too many threads in a short span of time and somehow I got the idea NookManager had some sort of issue after the 1.2.2 update that required some tinkering. The fact that the update is limited to the TLS update means it doesn't affect me, so things would be OK. On the other hand, not installing the update also seems like wouldn't be an issue and I really wanted to get ADB going anyway to install things wirelessly, so the most logical path seems to go through the minimal effort required to change that setting anyway. It turns out I already have sqlite3 installed (I am running an Ubuntu system,) so even more reason to do this!

I'll be reading up on the way to get ADB working.

BTW, I know you have proposed probably changing NookManager to address different issues you have encountered. Let me know if I can be of any help. I have no experience building Android components and limited experience compiling, but I would be happy to learn a new skill.

Thanks! :good:
[Nook Touch General] Winston S.:
[MENTION=5562185]nmyshkin[/MENTION] I easily managed to change the OTA setting through USB ADB. (I'm keeping track of all this process so when I have everything set up I will create a thread for posterity to help anyone else with the same questions.)

Now, the problem I wasn't anticipating is that I didn't foresee the battery problems, so I used that procedure to avoid the Register prompt on startup (Bypass OOBE procedure.) But of course now I don't know how to register the Nook. Do I need to reset to Factory using NookManager, root, disable OTA, and then register? It would be nice if there is a way to avoid this?

EDIT: Searching through another thread I saw your suggestions (almost 3 years old) to use the DeviceRegistrator, so after creating a B&N account I did and it said that the registration was successful, but in Settings the Account is showing up as unavailable, so I restarted the NST, and still I am getting Account Unavailable under Settings. Does the Device Registrator not work anymore? Or have B&N stop registering NST devices?

So I checked by logging into the B&N account and as expected there are no NSTs linked to my account. The DeviceRegistrator app has a few options (Register Device, Authenticate Device, Register User, and Authenticate User.) I didn't touch the User options so I guess that is to create a new account. I just used the "Register Device" option. Do I need to Authenticate Device too, or is this just not working anymore?

I read somewhere that there is also another app called OOBE Reg or something like that that basically runs the default registration procedure, but I haven't found that app in my NST.
[Nook Touch General] nmyshkin:
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.

Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
[Nook Touch General] Winston S.:
I will Authenticate using DeviceRegistrator and see if it works. The Catch 22 is that if I revert to Factory and then register the device I might have a problem with the 1.2.2 update I want to avoid (but yes, I realize at this point my aversion to 1.2.2 is basically irrational.) So I will try this approach first and report back. I will double check to see if the Nook Device shows up in my B&N account too, and I'll report again.

I agree 100% about putting the device in a sound baseline state before installing a lot into it. I'm documenting all that I do, and when I reach that state I'll create a thread about it. Hopefully it can be of use to someone down the road, because I do see new NST units being bought still every week in eBay.

I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
[Nook Touch General] nmyshkin:
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
[Nook Touch General] Winston S.:
Yes, apparently ADB Konnect is set up so that if you start ADB Wireless it sets the flag, and then unsets it. I just tried ADB through Wireless and it also works.

To update on the DeviceRegistrator, I tried to Authenticate the Device and it didn't work (I got a banner saying that the operation is no longer supported.) So it looks like I will need to restore to Factory, register, and then root (which defeats the purpose of disabling OTA updates, as I can't do that until I root.)
[Nook Touch General] Winston S.:
[MENTION=5562185]nmyshkin[/MENTION], is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?

I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
[Nook Touch General] nmyshkin:
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.

I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.

I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
[Nook Touch General] Winston S.:
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
[Nook Touch General] nmyshkin:
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
[Nook Touch General] Winston S.:
Thank you for looking at this. I am a little confused, because you helped [MENTION=6884580]ALinkToTao[/MENTION] who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..

So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
[Nook Touch General] nmyshkin:
Yeah, so I need to redeem myself there. In my lame defense, I was just going with what was posted here: https://blog.the-ebook-reader.com/2...artial-refresh-and-page-button-support-video/

Clearly that is bogus. So I checked out [MENTION=3000393]wozhere[/MENTION]'s listed working version, or something close.

I think the place to start is with the 3.1.2 series from the SourceForge home of CoolReader. The attached version looks a lot more like what I remember and has screen refresh options (only visible as settings while viewing a book).

There were many more options on the version I once had, so this one is a starting point only.
[Xiaomi Poco F1 Guides, News, & Discussion] krilok:
On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.

This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.

I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?

Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.