yashsingh1/xdaforums huggingface dataset:
[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] reist:
HI first of all, thanks for this great rom!

I was wondering is it is possible to turn of the Volte icons without actually disabling Volte.

So just Hide the icons.
[Upgrading, Modifying and Unlocking] bommel0815:
Hi!

well, after a bit of googling and experimenting, i found the perfect solution to get a german QWERTZ layout working with an English ROM (like EFNs excellent ones).

actually it is easy and works much better thank PQzII:

1.) download AEKMap:

http://ae.inc.ru/aekmap.php

2.) install to main memory

3.) copy the attached file i780-qwertz.aek.txt to \Program Files\AEKMap and rename it to i780-qwertz.aek

4.) start AEKMap Settings from the Programs menu

5.) on the first drop down box, chose i780 QWERTZ instead of <Default layout>

6.) make sure you have "Run on Startup" checked.

thats it. maybe you need a soft reset, but afterwards it will work.

it will even work with shift+y = Y and shift+z = Z, so it is better than PQzII in this regard. Also, the hardware buttons continue to work in the camera application, unlike with PQzII.

if you want to have easy access to umlauts, like in the german ROM (ie pressing o and the áü key afterwards = ö instead of pressing it a dozen times), copy the attached file sym.0409.txt to your device. once it is on your device, use resco explorer or total commander to move it to the \Windows directory. Soft reset.
[Upgrading, Modifying and Unlocking] ssr_german:
hey

i hav found a bug: when i will type *#0002# or so, the i780 get me at the y# key a + ?! when i type shift and y then i get the # ?! when i type the z there is the # ;-)

its a bug oder a future :) ??

thnx ssr
[Upgrading, Modifying and Unlocking] bommel0815:
just tried that and it works for me. hm.

but it sounds like z/y are still wrong for you then? hm.

i use exactly those two files (with the aek.txt renamed to just aek).
[Upgrading, Modifying and Unlocking] ssr_german:
z and y works fine, when i type a sms oder email !

but when i type at the today screen *# dont work

or when i have a call, i type z and i got the # ;)

its no prob.. i want only tell this bug

and sorry for my bad english !

ssr
[Upgrading, Modifying and Unlocking] bommel0815:
ah, now i get it.

you press alt+S for the * and get to the phone app

there you press alt+Y for the #, and this still works. but pressing Y results in a + being shown instead of the #.

hm. I think this is because we only catch the code for Y, but not for alt+Y.

you can alter the AEK file to circumvent this. we are not catching and replacing the button press, but the outcome, the letter.
[Upgrading, Modifying and Unlocking] lsyzq:
Thanks very much + Danke schön!!!
[Upgrading, Modifying and Unlocking] bolzi:
Hi,

ich bekomme den Fehler, dass in Zeile 6 eine "Invalid key definition" vorliegt.

Ne Ahnung woran das liegen kann?
[Upgrading, Modifying and Unlocking] bommel0815:
mit meinem file? das ist sehr eigenartig.

da steht nur das drin:

Layout i780 QWERTZ

Hint i780 deutsch

Key 0059 c007A

Key 005A c0079

Key 0159 c005A

Key 015A c0059
[Upgrading, Modifying and Unlocking] shahabsiddiqui:
thanks

thanks sir........................
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Ahsan008:
Hello,

I'm an Ex Poco F1 user (now own F2 Pro) and i was using Iphone XS Max Screen protector for it and it used to fit better than the original one. Has anyone found an alternative like this for F2 pro :confused: I've tried poco X3 & X2 Protectors but those are a little shy at the edges...
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] zyasin:
try Huawei Y9 Prime
[ASUS ROG Phone 3 Questions & Answers] kepetrov:
Hello,

Im using two viber accounts on my Asus Rog 3 Strix Edition.

First account on original Viber is working without any problems , but on second account on twin (cloned) viber I have some problems:

1. I cant send or receive pictures. It gives me an error that the picture isnt available.

2. I cant backup or restore data. It gives me an error that Drive isnt configured correctly.

Is there any fix for that ? Asus support didnt help me.

Thanks and sorry for bad English..
[Vivo Nex Questions & Answers] Twotems:
I think I may have finally solved this issue and it should work for all Vivo phones, in fact all phones.

I've had the Ping Tools app on all my devices forever so I went in there and lo and behold there's a "watch" function where you can set a constant ping interval and the condions under which it will trigger. Been using it for a couple of hours and it seems to be working with negligible effect on the battery. Give it a try and see how it works for you.

P.S. I know few people still have this phone but at least it will help others facing the same issue. This has been a great phone but I'm moving on myself.
[Vivo Nex Questions & Answers] Hexagono11:
Hola makina me puedes pasar capturas de pantalla como tienes configurada esa app para las notificaciones por favor? 650913192 si puedes también me tiene negro las notificaciones.

Por cierto creo que está al caer otra actuazacion
[Vivo Nex Questions & Answers] Twotems:
English only bro.
[Vivo Nex Questions & Answers] Hexagono11:
Vivo nex s

Hola makina me puedes pasar capturas de pantalla como tienes configurada esa app para las notificaciones por favor? 650913192 si puedes también me tiene negro las notificaciones. Por cierto creo que está al caer otra actuazacion

---------- Post added at 01:43 PM ---------- Previous post was at 01:41 PM ----------

​

Hello makina, can you give me screenshots, how do you have this app configured for notifications, please? 650913192 if you can also have me black notifications. By the way I think another performance is about to fall
[Vivo Nex Questions & Answers] Twotems:
I don't know what screenshots to give you because there are several steps. Download Ping Tools from the playstore, click on the menu and select "watch". Follow the setup from there. Let us know how it goes.
[Vivo Nex Questions & Answers] Magiver83:
Could you help me with ping tools on what I need to do to set up watch
[Vivo Nex Questions & Answers] 13k.VodkaSoda:
Greetings.

Just got my first Vivo phone and I'm having issues with delayed or no notifications at all from apps like "Messenger", "Email", "Whatsapp" etc.

I'm not sure how to set the ping tool to fix the notification issue as mentioned in the above post.

Was wonder if anyone can help me out.

thanks.
[Samsung Galaxy S9+ Questions & Answers] orifori:
I am trying to do something very simple which is described here:

https://xdaforums.com/nexus-6/help/help-editing-mixerpath-xml-android-10-t4032481

but when I open the file to edit it, I cannot find any of those values.

What values should I modify in order to increase the in-call volume of my Exynos Galaxy S9+?
[OnePlus Nord Guides, News, & Discussion] daksh143:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you're getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

I have extracted Stock Recovery for OnePlus Nord, Currently tested in Indian Version. EU and Global users please test it if you can.

There are two methods to restore stock recovery TWRP or Fastboot

Requirements:

- Working ADB and Fastboot (e.g. Google's Platform Tools)

- TWRP Backup or Stock Recovery

Steps for TWRP:

- Download archive from AFH

- Extract the content of archive, There will be a folder named 'BACKUPS'.

- Paste 'BACKUPS' directly into TWRP folder in your Internal Storage.

- Boot into TWRP and restore the recovery partition.

- Reboot

- Profit

Steps for Fastboot

- Download Recovery image from AFH

- Open terminal in your ADB folder

- type "adb reboot bootloader"

- Copy stock recovery image you have downloaded to your ADB folder

- type "fastboot flash recovery <file-name>.img where filename is the name of img file you have downloaded.

- Reboot

- Profit

Mirrors:

TWRP Backup

Recovery Image

I have extracted the backup by booting into TWRP and backing up the recovery partition. The img file has been extracted from my device with dd command.

Enjoy.
[OnePlus Nord Guides, News, & Discussion] daksh143:
Reserved

**Reserved**
[OnePlus Nord Guides, News, & Discussion] pugoless20:
im in PixelExperience rom i want to go back to oxygen os can i do this method? or i will use msm tools?
[OnePlus Nord Guides, News, & Discussion] JD00:
Did somebody check the recovery with the EU model?

Or maybe have the EU recovery....

(I want to go full stock OOS11 after the Pixel Experience)
[OnePlus Nord Guides, News, & Discussion] gorro8:
You can do it through unbrick tool for EU region. Unbrick tool for EU is only with android 10. You can flash it firstly and after that update to android 11.
[OnePlus Nord Guides, News, & Discussion] robdg80:
Where can I get the "unbrick tool for EU region"?
[OnePlus Nord Guides, News, & Discussion] gorro8:
Here
[Upgrading, Modifying and Unlocking] hays:
I have the option save sent messages unchecked

Each time I soft reset my phone, this item gets checked and it starts saving all my sent sms

I'm told this is most likely a registry setting that needs changing

Any ideas which setting please ???
[Huawei Y5 (2017) Guides, News, & Discussion] marcin17_18:
Hello, I need a rom to be uploaded by twrp. I played AOSP OFICIAL 7.1 HUAWI Y5 II CUN-L21 Y CUN-L23 but the phone hangs on the dots for about 10 minutes and nothing.
[Huawei Y5 (2017) Guides, News, & Discussion] mahesh_gupta:
Do you have your bootloader unlocked?
[Nook Touch General] albrow:
EDIT: The files have now reappeared on B&N's servers. For safety and convenience I've attached the Nook-1.3.0 and Nook-1.3.1 Delta files here in one Zip file. Hope this helps someone else. I'm off to try patching this kernel.

Hi all!

Does anyone have a copy of the source code for the 2013 Glowlight? The links on B&N's site aren't working. I've tried hunting around on XDA, but it doesn't seem as though anyone has ever uploaded them here.

Nook OS version on my GL 2013 is 1.3.2, but I'm guessing 1.3.0 and 1.3.1 aren't that different and would be better than nothing.

Thank you!

Alex
[Nook Touch General] albrow:
Found them! B&N must have fixed their site, because the links are working again. I've attached them here in one Zip file just in case they go missing again. I've also popped them on the Wayback Machine.
[Nook Touch General] albrow:
I've managed to build the kernel using the Sourcery G++ Lite 2010q1-202 toolchain. There was a tiny tweak needed to get it to work with newer versions of Perl, but otherwise it's compiled without a problem. I've tried with a couple of later Linaro toolchain builds, but they failed.

Patch-wise I'm trying to get features as close to the NST modded kernels as possible. The kernel on my old NST has the smartassv2 CPU governor and the SIO scheduler, so I've found patches for those and added them.

I have a few other patches, but no success so far. FastMode needs quite a few tweaks for the patch to work. USB Host Mode compiles fine but does nothing, with no chipset shown in Renate's USB Mode Utility. Finally, I can't work out how to overclock to 1000 MHz.

I'm sure a lot of these issues are solved somewhere in this forum, or there are at least clues (the "Hacking the New Nook Glowlight" thread has certainly helped). I haven't found the answers yet. It's not an urgent project - my NST is still hanging on for dear life - so I'm just working on it when I have a few minutes or feel inspired to do so.

I'll post updates here as I work things out. If anyone has any tips or can offer any help, please do reply to this thread.
[Nook Touch General] Renate:
The old driver(s) exposed:

/sys/devices/platform/musb_hdrc/mode
/sys/devices/platform/musb_hdrc/vbus
/sys/devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-0048/twl4030_usb/vbus
/sys/devices/virtual/sec/switch/adc
/sys/devices/platform/bq24073/regulator/regulator.5/state
/sys/devices/platform/bq24073/force_current
[Nook Touch General] albrow:
I've uploaded what I've done so far to GitHub.

GitHub - PocketNerdIO/nook-kernel-1.3.1: Kernel for the Nook Glowlight 1 (BNRV500), based on B&N's stock kernel (nook-1.3.1, Android 2.1, Linux 2.6.29-omap1) with some extra patches.

Kernel for the Nook Glowlight 1 (BNRV500), based on B&N's stock kernel (nook-1.3.1, Android 2.1, Linux 2.6.29-omap1) with some extra patches. - PocketNerdIO/nook-kernel-1.3.1

github.com

Currently the only changes from stock are adding SIO and smartassv2. I've attached the uImage and .config files, should you want to give them a go yourself.

I don't know how many NG1 users are still out there, but hopefully someone will find this useful.

Sidenote: I'm a Linux user. If you run ADB in Linux first, Renate's ADBGRAB runs perfectly in Wine. See the screenshot below.

View attachment 5224589
[Nook Touch General] nobodyAtall:
I'll try look into it.
[Nook Touch General] albrow:
I thought I should add that I've already adjusted the partition table. My NG1 currently has a uRamdIsk that mounts /sdcard as a simlink, but some apps really don't like this. I think I'm going to repurpose "reserve" as /sdcard instead.

NAME FSTYPE FSVER LABEL SIZE
sdb
├─sdb1 vfat FAT32 boot 76M
├─sdb2 vfat FAT32 rom 16M
├─sdb3 ext2 1.0 factory 190M
├─sdb4
├─sdb5 ext2 1.0 288M
├─sdb6 vfat FAT32 NOOK 2.5G
├─sdb7 ext3 1.0 cache 239M
├─sdb8 ext3 1.0 reserve 15M
└─sdb9 ext3 1.0 userdata 300M
[Nook Touch General] Renate:
Gosh! Glad to hear it.

Don't forget that for a simple grab give it a filename:

adbgrab grab.png /o90

Rotate works on this (but not Scale /s)

For interactive:

adbgrab /s.5

Rotate & Scale work.

Mouse clicks and most keys work on this (but slowly due to Android "input" command which does it in Java).
[Nook Touch General] albrow:
Thank you! I'm going to try running a few more of your tools with Wine in the next few days. I'm especially interested in patching the Reader using MergeSmali, as well as swapping versions (seeing if the one in 1.2.1/1.2.2 is better than the one in 1.3.1).

I added some compilation tweaks to the code so that it aimed at Cortex-8 rather than a generic ARMv7 build. The changes are on Github and will be part of the next binary I release.

I've been wondering if it's worth trying to find some other patches for this old kernel to give it a speed boost, or maybe more battery savings. I'm guessing it's not worth trying to get it running with a newer kernel (2.6.32/35/36). To be honest I don't know much about kernel hacking beyond some beginner-level C and adding patches. For now I'd like to get things like multitouch and FastMode running, which shouldn't be too tough.
[Nook Touch General] albrow:
With a quick tweak to the code, the kernel now compiles and boots with Linaro 2012-08 (gcc 4.7.2). I'll push the change to Github later.

I was also able to compile it with Linaro's gcc 4.9.4, but unfortunately the NG1 wouldn't boot. I probably need to work out how to look at u-boot and kernel logs to see if it's fixable, but it's not as important as getting the other patches working.
[Nook Touch General] albrow:
I'm slowly going through Guevor's old patch file (v4) for the NST. I've added the option for Veno TCP congestion control to the kernel. The change is up on Github. Plus, here's my latest kernel compiled with Linaro gcc 4.7.2, along with the config. To recap, here's the changelog from the stock Nook 1.3.1 kernel (2.6.29):

Compiles (and boots) with Linaro gcc 4.7.2

Fixed to compile with modern versions of Perl

Use SIO I/O Scheduler as default

Use smartassv2 as default

Add Veno TCP congestion and set as default

Not a huge number of changes from stock, but hopefully still some improvements. Next up are FastMode, Multitouch and USB Host. There are also the overclocking settings, but I'm less sure about whether they're all that worthwhile.

EDIT: Realised that I'd uploaded a kernel compiled with the Sourcery toolchain, so I've just uploaded one compiled with Sourcery and one with Linaro gcc 4.7.2. Feel free to test both.

In other news (cc @Renate NST), the stock Reader on my device really doesn't like files loaded using the Temblast Library, which is a massive shame as it's my preferred library app. It takes a long time to load the file, and then has no indexing whatsoever: "Content" does nothing, "go to" shows "Page 3 of 0", and highlighting a word crashes the reader. It's not the end of the world as I can use the stock Library, although I don't know if it's going to read the files in /sdcard. Further research required.

View attachment 5227601

Also, this version of the stock reader REALLY dislikes Button Savior drawing over the top of it. This is most noticeable when the trigger fades out. It will try to refresh the screen at every gradient of change, sometimes making the device unresponsive for up to 30 seconds. I thought there was a way of turning off the fade-out, but I can't find it. One workaround is to close the Button Savior panel, press home, wait for the button to fade, then go back to the reader. It's times like this when I actually miss the "n" button bar on the NST. I can live without physical buttons if the virtual ones do the job well enough.

Think my next task will be to rearrange the partitions so that there's a proper /sdcard rather than a symlink.
[Nook Touch General] Renate:
That's very strange. If it opens the intended book then it should be ok from there.

In my world the reader gets the last reading point by itself.

Maybe your reader is expecting something extra in the intent and it isn't handling the lack gracefully?

Does it always go to page 1 even if you've read further?

Mmm, I dislike those things too.

I was looking at the Onyx Boox Poke 3. It has only a power button, no home, no anything.

It has this arc of icons that follows your finger, a bit like Button Savior.

It's great hardware but I'd have to do a bunch of work to make it clean.
[Nook Touch General] albrow:
I'm certain you're right on this, but I have no idea how to monitor that.

Yes, unless you're re-opening the same book that is currently open (i.e. Reader is already running in the background with that book.

I've just noticed something with this Reader. It NEVER does a refresh on a page turn, nor when the bottom menu appears or disappears. It sometimes does a refresh when it first loads a book, but not always. But if something tries to draw over the top of it (Button Savior, the Android volume HUD), it refreshes on every change to the screen.

I have a theory on this. When trying to apply the FastMode patches, I noticed that the nook 1.3.1 kernel has more functionality than the one from 1.2.x. I've attached them both here, along with a diff of the two files. Could it be that this newer Reader uses a "new" (given the device is 8 years old) screen drawing method that the NG1 is switching in and out of when something draws over the top of Reader?

I might compile another kernel with the old kernel driver to see what it does.

Oh, don't tempt me! Hacking around with Android 2.1 does feel futile in 2021, but I'm not sure if I want to spend $189 on an ereader right now.
[Nook Touch General] albrow:
So, a quick update. I've managed to get the OTG patch on and enable the right kernel options (thanks to guevor's old NST .config file). It can now see devices!

View attachment 5230153

Unfortunately, even though I've enabled block devices and SCSI, no new devices are showing in /dev. I'm sure I'm just missing some kernel options.

I found a later version of Linaro's gcc, specifically 4.7.3 from April 2013, which creates a bootable kernel. I think this is the latest version of gcc that will work properly with this code - any later and I just get a freeze at boot, not even a bootloop. It would've been nice (for me) to run a 64 bit compiler, but this works for now so I'll stick with it.

Latest amendments are on Github. I'm not at my laptop at the moment so I don't have a copy of the uImage or .config, but I'll add them when I'm next about.

Finally, I was wondering how easy it would be to "backport" this kernel to work on the NST or NST/G. It might just require an old .config file such as guevor's one. I don't know how useful that would be for anyone, especially as it doesn't have multitouch or FastMode, but it might provide some better screen writing code. I guess it could be a good experiment.
[Nook Touch General] Renate:
Hmm, it's interesting that it's not showing any interfaces or endpoints.

Are you using UsbMode-2.2.apk?

What does dmesg say when you plug it in?

Does a keyboard or something else work fine?
[Nook Touch General] albrow:
I think I've only got 2.1 on there actually - an old copy from when I was setting up my NST many years ago. I'll download 2.2 and get the dmesg log tonight. I don't have the USB stick or an OTG cable with me.

Do I need usbhostd as well, or is that only for the KitKat Nooks?
[Nook Touch General] Renate:
No, that's only for Glow2/3/4
[Nook Touch General] albrow:
I couldn't get UsbMode 2.2 to install on the NST or the NG1, but 2.1 runs fine on both. I've tried my Microsoft Ergonomic Keyboard on the NG1. It's showing in UsbMode, but dmesg comes up with this:

<6>[ 283.243438] usb 1-1: new low speed USB device using musb_hdrc and address 7
<3>[ 283.445098] usb 1-1: device v045e p00db is not supported
<6>[ 283.452697] usb 1-1: configuration #1 chosen from 1 choice

View attachment 5230691

For the Sandisk OTG memory stick I get the following (of course, this could just be the stick asking for too much current):

<6>[ 589.997344] usb 1-1: new high speed USB device using musb_hdrc and address 9
<3>[ 590.163635] usb 1-1: device v0bda p0109 is not supported
<6>[ 590.171295] usb 1-1: rejected 1 configuration due to insufficient available bus power
<4>[ 590.179595] usb 1-1: no configuration chosen from 1 choice

View attachment 5230693

Here's an Apple Mighty Mouse:

<6>[ 666.583343] usb 1-1: new low speed USB device using musb_hdrc and address 10
<3>[ 666.771850] usb 1-1: device v05ac p0304 is not supported
<6>[ 666.779510] usb 1-1: configuration #1 chosen from 1 choice

View attachment 5230687

And for a laugh I thought I'd plug my NST into the NG1:

<6>[ 1193.856811] usb 1-1: new high speed USB device using musb_hdrc and address 21
<3>[ 1194.021789] usb 1-1: device v2080 p0003 is not supported
<6>[ 1194.029296] usb 1-1: rejected 1 configuration due to insufficient available bus power
<4>[ 1194.037597] usb 1-1: no configuration chosen from 1 choice

View attachment 5230697

I'm sure I've just not enabled something in the kernel, but right now I'm not sure what.
[Nook Touch General] albrow:
OK, here's an interesting thing.

I thought I'd try plugging in an unpowered USB 2.0 Hub, which was recognised:

<6>[ 1858.059326] usb 1-1: new high speed USB device using musb_hdrc and address 25
<6>[ 1858.222869] usb 1-1: configuration #1 chosen from 1 choice
<6>[ 1858.229644] hub 1-1:1.0: USB hub found
<6>[ 1858.233978] hub 1-1:1.0: 4 ports detected

View attachment 5230717

And then I plugged in the USB stick into the hub... which also worked and created /dev/block/sda and sda1!

<6>[ 2031.161499] usb 1-1: reset high speed USB device using musb_hdrc and address 25
<6>[ 2031.968811] usb 1-1.3: new high speed USB device using musb_hdrc and address 26
<3>[ 2032.104217] usb 1-1.3: device v0bda p0109 is not supported
<6>[ 2032.111999] usb 1-1.3: configuration #1 chosen from 1 choice
<6>[ 2032.130249] scsi0 : SCSI emulation for USB Mass Storage devices
<7>[ 2032.139739] usb-storage: device found at 26
<7>[ 2032.144134] usb-storage: waiting for device to settle before scanning
<5>[ 2037.149627] scsi 0:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0 CCS
<6>[ 2037.273895] usb 1-1.3: reset high speed USB device using musb_hdrc and address 26

View attachment 5230719

Unfortunately the Apple Mighty Mouse did what it did before, although it showed as being plugged in to the hub.

<6>[ 79.115997] usb 1-1.2: new low speed USB device using musb_hdrc and address 3
<3>[ 79.238891] usb 1-1.2: device v05ac p0304 is not supported
<6>[ 79.246276] usb 1-1.2: configuration #1 chosen from 1 choice

View attachment 5230725