yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
On the general theme of obsolescence:

I have a Google (Asus) Nexus 7 (2013).

After years of use the battery has swelled up.

I decided to do something before it blew up.

Although batteries are widely available for under $15 I decided to go batteryless.

If you're not familiar with this:

You peel the plastic and foil from the top of the battery to access the battery management PCB.

You cut the metal tabs that connect the actual battery.

You connect a 4.1 V power supply to where the tabs used to go on the PCB.

(The voltage varies by system. I found that 4.2 V triggers over voltage.)

You need the PCB because the management ICs interacts with the system.

The Nexus 7 is about the same generation as the NST.

While the NST was a very modest design, the Nexus 7 was cutting edge for the time.

Wikipedia says: "Despite the age of the Nexus 7, in June 2018 it was still the fourth most popular tablet in use around the world."

Edit: I did have some problems turning on the Nexus even when it had 4 V for the battery.

Going from cold dead to on it requires "charging".

So connect the USB up to something, you get the battery charging thing, then you can turn it on (and remove the USB, obviously).
[Nook Touch General] criticalmass:
After years of absence I decided to look in again this morning, ans what can I say? You glorious bunch of rebel scum had kind of the same thoughts I was dragging around in my head.

I like my NSTs and Glow2 a lot, but other than reding sideloaded books offline, they haven't been doing much in the past. At some time along the road, I looked into Boox devices, and got a NovaPro (1.6 Quadcore, 2GB RAM, Android 6.0.1) - and have been in two minds about it ever since. It has a huge amount of quirks that almost overshadow the niceties, and my efforts in taming the beast (ADW Launcher, F-Droid) have been cursory at best. So a dedicated Boox forum may be a lot of help - even if I need to ditch the Nova and get a Poke.
[Nook Touch General] Renate:
Very true. The underlying code is a train wreck too.

The Home gesture is quirky.

It either goes to home or does nothing.

It seems to be themed or set in "High Contrast Text" (without the Android stock setting on).

That means gray goes to white.

White text turns into an outline font.

The front light controls are incompetent.

You can't just adjust brightness.

You have to adjust cool and warm separately.

Locking the two controls gives you a nice red.

The code that controls this has over 20 methods and that's for each of the four models.

The hardware itself simply takes an 8 bit value to /sys/class/backlight/white & /sys/class/backlight/warm

I haven't figured out yet where/how the setting is saved.

It's not in the Android stock settings.

Some of the code is Proguard obfuscated (with method names like a.b.c.d.E.f(); )

There's a lot of bloat.

Most of this stuff is in /system/priv-app/kcb-release

Edit: Huge amount of quirks? I'm making a sound like "Lurch" if you can remember that TV show.

If you try to draw text or even rectangles of white, the super intelligence of High Contrast will kick in and do something that you didn't want.

Normally I'm used to a GDI where you say, "These pixels over there? I want them white" and it happens.

Nope, we don't get that here.

Here is a test case where I draw some black on the left and some white on the right, like a progress bar.

I do 6 different ratios (0.0, 0.2, 0.4, 0.6, 0.8, 1.0) with two sets, one 4dp high, one 5dp high.

That is the only difference between the two sets.

In the 0.0 & 0.2 stripe of the 4dp it looked at the command to draw 80-100% of the width and 4 dp of the height white and just decided not to do it.

Notice how ugly the words "Demo" and "Go" appear.

Notice that even though "Go" is wrap_content, when they made it thicker they didn't expand enough and they clipped the right side.

The title is supposed to have a dark gray background but something took an editorial decision against it.
[Nook Touch General] criticalmass:
That succinct quirk analysis puts an Uncle Fester smirk on my face...

Not being much of a developer myself, more the concept and get-money-from-management guy, I've been trawling the other end of the net and looked at Boox user groups and forums. A lot of frowning and knitted brows there - the company is, put mildly, erratic in its release, patch and product strategy.

Quick example: My Nova Pro was promised an Android 9 upgrade right from the start, now the released it - in form of a manual install procedure hidden in a google doc, literally on display at the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'beware of the leopard'. Oh, and you have to sign a warranty waiver.

BUT - and that's the catch; they seem to be the only ones producing android-based ereaders with something of a perspective to the modern age. Boyue Likebooks are there too, but what they do mostly is steal from other companies and rebrand it.

To cut this long story short: Do you think it's worth investigating and investing time into that line?
[Nook Touch General] Renate:
I looked at the updates coming in to the Poke3.

They are stored in the open in /sdcard/update.upx

(This is not the UPX compression standard.)

They are encrypted, but somebody figured it out already:

GitHub - Hagb/decryptBooxUpdateUpx: Decrypt `update.upx` the encrypted ROM update package released by Onyx Boox, so as to get the zip format update package which can be read by Recovery directly

Decrypt `update.upx` the encrypted ROM update package released by Onyx Boox, so as to get the zip format update package which can be read by Recovery directly - Hagb/decryptBooxUpdateUpx

github.com

The boot.img is ramdisk-less with System-as-Root.

This makes it a bit trickier to put Magisk on it.

They don't seem to do any incremental patches.

That means every time they tweak some tiny thing you have to download 1.1 GB
[Nook Touch General] SJT75:
I have mixed feeling about those updates for Onyx. Encryption should prevent using corrupted update file as if hash and/or signature does not match it should not undertake an update at all to protect user from man in the middle kind of attacks (why would anyone target e-ink device is beyond me but it is possible anyway as they generally use older more vulnerable hardware base in order to compensate prohibitively high price of e-ink screen). It is an old school of backup of device that worked exactly like this just extract/rewrite a device disk/partition with backup file and carry on. Now it is rather silly today not to be able to do incremental backup or update and force user to download huge amount of redundant data.

Since we discussed in this thread several e-ink devices mentioned by various users and also we discussed about icons elsewhere it seemed appropriate to link this thread on another site that mention although other device but in a comments there are links for launchers that Renate might be able to test on Onyx as the user say it works also there.

https://www.reddit.com/r/NiagaraLauncher/comments/mtd0z1

E-ink browser -

https://www.reddit.com/r/ereader/comments/mbxuef
If I understood well can be downloaded from Git or F-Droid. It require Android 6+.
[Nook Touch General] Renate:
Before:

Poke3:/ $ uname ‒a
Linux localhost 4.4.194-perf-gad92c13-dirty #170 SMP PREEMPT Thu Mar 25 18:18:59 CST 2021 aarch64

After:

Poke3:/ $ uname ‒a
Linux localhost 4.4.194-perf-gad92c13-clean #170 SMP PREEMPT Thu Mar 25 18:18:59 CST 2021 aarch64

Summary: Got it to run a modified kernel! Now I have to make a better mod than this. :)

Edit: I extracted all the kallsyms and I patched sel_write_enforce to do nothing. Now I got:

Poke3:/ $ getenforce
Permissive

Ok, but what does that get me?

Edit: Mmm, it gets me here:

Poke3:/data/local/tmp $ ./exploit
setuid(0) => 0
setgid(0) => 0
Poke3:/data/local/tmp # id
uid=0(root) gid=0(root)
[Nook Touch General] SJT75:
If we take into consideration that highest Linux kernel version that could realistically run on NST would be 3.10 then Renate is right her new reader is way better in several aspects.
[Nook Touch General] Renate:
I'll say this about that.

Sometimes you dig yourself in a hole.

So you keep on digging. And you're in a deeper hole.

Sometimes, though, if you keep on digging you come out the other side. :)
[Nook Touch General] Renate:
Yes, that's the new Onyx Boox Poke 3

The three wires are the console UART, the tiny wire is the reset line (for when I was experimenting).

This has a Qualcomm Snapdragon 636 processor which has EDL (Emergency Download Mode).

You can reach that by ADB but in worst case you have to reset while shorting the two points below where the UART wires are.

I've already installed a connector (instead of the wires) for the UART and I want to avoid having to open the case needlessly.

I've ordered a magnetic reed switch that I can put across these points.

You'll just need to place a magnetic on the right spot on the case and do a long power button press.

I'll show a photo when the part comes in.

The Onyx folks forgot (intentionally?) to build the kernel with the driver for the serial line.

That means that you just get UART data out while the Poke is booting, but not after it hits Android.

I'm working on that too.
[Nook Touch General] SJT75:
Might be slightly off topic but what do you mean about Kobo Rakuten Elipsa 10.3" Renate? I know you have chosen your new device yet some of us that did not go still down that line would like your opinion on this matter.

​
[Nook Touch General] Renate:
Mmm, all the Kobos seem to be straight Linux.

I don't see anything that indicates otherwise on the Elipsa.

The 1G of RAM is probably enough for a Linux ereader, but skimpy for Android.

My main need is always a 6" ereader that hasn't tried to save every nickel.

That means enough flash, enough RAM, up to date OS, Bluetooth.

If I had more need for documents an 11" ereader would be a nice addition.

I hardly have a need to scribble.

Well, actually I do, but I use notebooks that I buy at the dollar store,
[Nook Touch General] SJT75:
Thanks for reply Renate! Linux or not is not important to me. Reason why I am interested for this reader is that it have large screen which supposedly make PDF documents more usable on it. Being table to scribble notes on it is rather unexpected bonus from mine point of view. Linux could be both blessing and the punishment. Depending on distribution and how tight they choose to lock it down.
[Nook Touch General] Renate:
I've not much experience in writing Linux GUI applications.

I've got a spare Kobo Aura 2nd and I can run command things on it.

I can draw to the frame buffer (easy) and activate the eink refresh (more tricky).

I really should use it for something.
[Nook Touch General] SJT75:
Wouldn't screen refresh be just a variation of writing to the frame buffer? Could you elaborate please Renate?
[Nook Touch General] Renate:
In Android you have /dev/graphics/fb0, in Linux you have /dev/fb0

It's a chunk of memory that is used for (usually?) two separate frame buffers.

To find out the size, location and which one is active you use two "ioctl"s.

FBIOGET_FSCREENINFO, FBIOGET_VSCREENINFO

In Windows an ioctl is just a 32 bit number assigned in sequence.

In Linux/Android it is an encoded value that includes the size of the input/output structure.

This gives it a simple versioning system.

You can write all day to an eInk frame buffer and you will never see a change.

You have to activate a refresh through the driver with another ioctl.

Since everything to do with E Ink is secret and voodoo what we know is from leaks/reverse engineering.

The fbink project has some examples.

GitHub - NiLuJe/FBInk: FrameBuffer eInker, a small tool & library to print text & images to an eInk Linux framebuffer

FrameBuffer eInker, a small tool & library to print text & images to an eInk Linux framebuffer - NiLuJe/FBInk

github.com

The MXCFB_SEND_UPDATE ioctl (specific to the iMX driver) uses a structure with two other structures in it.

These structures went through different versions and have different sizes.

An ioctl will only do something if you have the total size correct.

So you try with an ioctl and twiddle the size up and down until you see some kind of change.

Then you know the total size of the structure and can figure out the actual size of all the structures.

I've only written stuff for throwing up full screen splashes on Glow and Kobos.
[Nook Touch General] SJT75:
Well my previous searches about drivers for e-ink screens revealed that there supposed to exist such support in Linux but I did not get myself harder into that subject. Renate you bring some very good information on the table here. From what I know most reader devices now use iMX.
[Nook Touch General] Renate:
Yes, it has mostly been iMX6SL, but my new Poke3 has a Qualcomm Snapdragon 636.

Some older Onyx Boox used "RockChip" which I know nothing about.
[Nook Touch General] klemperer:
Hi, Renate, is it possible for Poke3 to add some virtual volume up/down buttons on the screen? Have to swipe to turn page for some app, for example, Feedme RSS reader. It would be great to simply tap on the left/right side for page up/down.
[Nook Touch General] Renate:
Ugh, I hate swiping. It's so stupid for common things.

You could add something like ButtonMagic, but even that would require two actions.

Then there's the "Navigation Ball" which I hate (and don't use) for any number of reasons.

So the seazon/FeedMe uses PAGE_UP/PAGE_DOWN and (if enabled in app prefs) VOLUME_UP/VOLUME_DOWN for everything.

A Bluetooth clicker would work.

I don't know, it's best to have tapping part of the original application.

It would take a bit of modding.

Unrelated: I'm waiting on apktool 2.6.0 to fix some stuff with the framework.
[Nook Touch General] klemperer:
I just noticed that NOOK released a 10'' tablet in March. It would be great if there wil be a new NOOK eink reader this year, with newer android version, more memory and physical buttons.
[Nook Touch General] Renate:
B&N offers two current Eink readers (Glow3, 4) and one refurbished (Glow2).

All the statistics point to a downturn on Eink readers.

I know a few people who bought an Eink reader a few years ago and stopped using them.

I can't see B&N making an effort to bring out a new model.

The fact that they even brought out the Glow4 amazed me.

B&N was always competing against Kindles for $50

I think that Android has gotten a bit out of hand, the bloat is enormous.

I can't really think of compelling advantages of Android 10 over 4.4

Things that I do appreciate are multicore processors, more memory and Bluetooth.

Opening a book on my Poke3 blows away any Glow.

The new B&N 10.1 is pretty lackluster 1280 x 800 = 150 DPI

They are selling a refurbished other model 10.1 1920 x 1200 = 225 DPI

As always with B&N they never quote any model numbers so that "10.1 Tablet" is ambiguous.

Physical buttons are always in conflict with making the smallest bezel.

I believe that the Poke2/3 are the smallest 6" readers around.

Still, I wish that they had stuck the regular 3 Android navigation buttons hidden as capacitive switches in the bottom bezel.

People who don't like them could disable some/all of them.
[Nook Touch General] Renate:
Just a little update...

I've been pretty much happy with my Poke 3

I disabled the Onyx stuff with gets rid of the "optimization" on the fonts (although you could disable them per app with a long press).

You need to be rooted to pm disable com.onyx

In short, use EDL mode to get the recovery image and install magisk.
[Nook Touch General] Joydeck:
I understand you bought an Onyx Boox Poke 3 last year. My old NST just keeps on keeping on but, a year after your posts, I am interested to learn whether your reservations regarding the Poke 3 were justified. Are you happy with your purchase or have other downsides surfaced? Is web browsing on the Poke 3 pleasurable?
[Nook Touch General] Renate:
I am very happy with my Poke3. It's not very hard to avoid any of the stock software that you don't like. I only use it for reading and I never use a web browser.

Two things that I wasn't sure if I would like that, for me, at least, worked out well. I like having a cover with the magnetic sensor to automatically turn on/off. The other is that I use a custom Bluetooth clicker to turn pages. You might think that cumbersome but I find it convenient. In bed when it's cold I can keep my hands under the covers. Even reading at a desk I find it more convenient than poking the screen.

The old NST was fine, but the newer Glows have the 300 DPI resolution and front light, but the Glow '21 has multicore. Still, B&N dropped the ball on the latest model. It only has USB 2.0 (not 3.0, despite a Type C connector). It doesn't have USB host mode. They sell covers, but there is no cover sensor. I have a Glow '21 but I hardly use it. The cover is poorly designed. The side buttons just make it bulky. I prefer the flush face of the Poke3 to the bezel of the Glow '21.

I sync my Poke3 over USB 3.0 (using my AdbSync) and it's ten times faster than the Glow '21.

Frankly, I don't understand why everybody clings to their decade old NST.
[Nook Touch General] Joydeck:
Thank you for the information.

I usually read seated in a recliner rocker, never in bed, and have no need for a glow light. I have been too happy with the NST, CoolReader, and AARD to bother to upgrade.

While reading, I would frequently use a web browser for Google Translate and obscure terms or phrases.
[Nook Touch General] Renate:
Well, don't dismiss the utility of a bit of front light. You don't have to have it illuminating your face. I keep mine on 30% all the time which is just enough to make the slightly gray screen a little bit more white. Unless it's dark you don't even notice that it's on.
[Nook Touch General] SJT75:
I know that Renate has long ago resolved the question she made in this thread. I just stopped by to wrote what I have read today about Kaleido 3. It seems that finally somewhat affordable color e-ink will support 150dpi that is absolute minimum in my opinion to make it count as significant improvement. Still lot of room for improvement there. Man can not ask himself will ACeP become cheaper with time or will Chinese made screens using electrowetting that they tested last year replace e-ink on this market as next big thing.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Aadil Gillani:
MOD EDIT: Content removed
[Xiaomi Mi A2 Lite Guides, News, & Discussion] LinkBoi:
~ Kanged from Telegram.

PSA: Aadil is a known spammer in Mi a2 lite Telegram so it is my recommendation that you don't trust him. He has raided 2-3 groups and caused many problems.

Thanks in advance to the XDA Mods and sorry for the offtopic
[Xiaomi Mi A2 Lite Guides, News, & Discussion] SunlightV2:
This guide its outdated most new roms dont require FDE now , and yes this guide its kanged from telegram thanks in advance
[Xiaomi Mi A2 Lite Guides, News, & Discussion] andraslate:
Should mention that MIUI ROMs doesn't require A/B slot change after installing.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] LinkBoi:
new guide coming sir
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Os_Herdz:
Lol, u gonna win my report for a bad guide, u don't know nothing
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Aadil Gillani:
How to delete Post on xda
[Xiaomi Mi A2 Lite Guides, News, & Discussion] strongst:
Thread closed

Please read the FORUM RULES:
[HTC Excalibur] dav2276:
is there a way to have the led flash orange or some other color when there is an unread text message or email?

I know that the blackberry curve and the blackjack2 both have this feature and was curious as to whether or not a wm6.1 phone could do the same.

Thanks
[HTC Excalibur] vwgtiron:
Try this out see if you like it. Then get the most current version.
[HTC Excalibur] jdoggraz:
I use the same one and I like it a lot. I suggest that people use this one because it works great.
[HTC Excalibur] uansari1:
What version is stable with our phone?
[HTC Excalibur] falleny:
yes...it works...but once u input a wrong reg code...then u will never be able to register this soft unless u hard reset your device...thats bad.
[HTC Excalibur] vwgtiron:
any other ideas then?
[HTC Excalibur] phamhien:
I've installed. The LED is just blink faster but not change color. Anyway thanks!
[HTC Excalibur] jdoggraz:
Yah thats all it does, where you looking for something different...
[HTC Excalibur] uansari1:
It would be cool to find something where you could set various LEDs as notification for various messages...i.e. blue led = vmail, amber led = email, green led = text, etc.
[HTC Excalibur] dav2276:
im having troubles getting dontforget to work... does anyone have it working on 6.1 yet?
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] Newbiee01:
I want to uninstall and reinstall gapps without losing data. Is it possible to do so? I want to install a bigger version of gapps
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] palmbeach05:
This is my first a/b device, and without this guide, i would have flashed as if this was an a-only device and probably would have messed something up. Thanks for this, it worked perfectly. Enjoying 10 now
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] palmbeach05:
One note that should be added, in order to get cts to pass, you need to use the magiskhide prop config module and set it to our android 9 fp. RETUS using q will not pass cts without that change.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
If u flash new 9 retus I didn't need to run the props but did any ways
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] shawndak:
Good Lord! That's a lot of work to flash over to Q! There has to be an easier method. Can you describe more on how to do the 4 *.img file flash method? Also do you have to erase userdata? I just unlocked & flashed my Metro G7 power to retus to allow Verizon sim to read. Will have to wait for an update method as I'm not ready to erase everything again. Good work though!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] palmbeach05:
That might be the difference then. I went from June Android 9 OTA without reflashing the fw, to a/b copy zip, then to flashing the q fw from above.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] ozmage:
I just Uploaded The Blankflash for Pie 9 and for 10 Q .

I hope no one bricks but follow what i wrote and no one will have any problems , There is The CopyPartitions-AB.zip never forget to flash it after flash stock pie. And "NO" to Clarify No There IS no Need To Flash Any Custom Kernel On This Firmware.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] smartasiankid:
Hey what about for the regular Moto g6? Can you please make a separate post on it telling me how to flash the latest stock firmware for the us retail because i cannot hear audio when calling with the defualt dialer and instead i have to use a different app and that is very inconvenient. Please, someone make a thread on RETUS channel for moto g6 stock firmware flash with all steps as well as the files and code for executing the code. Or DM/PM me. PS: i am only 15 and i shouldnt have tampered around with my device but i badly wanted more customization so i decided to do so without my dads persmission and now i am stuck here with call audio not working. any help is greatly appreciated.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] smartasiankid:
BTW my discord is badassrajesh508#1529
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
do agree all these guides help on XDA .that's what i do read an research before attempting anything new.these newer a/bdevices require more care and work to flash custom roms and stuf like that.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
will this work for international version like 1955-2.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] smartasiankid:
NVM I figured that most of them have wrong modem versions.
[OPPO Find X2 Pro Questions & Answers] kevinireland11:
What are the difference there?
[OPPO Find X2 Pro Questions & Answers] WeDBstMsic:
Cph2023 - "standard" Oppo find x2

Cph2025 - Find X2 "Pro" Which has 2 variants (Single sim & Dual Sim)