yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 Questions & Answers] gmfrvr:
You should try msm tool for restore to stock oos
[OnePlus 6 Questions & Answers] TexnoViking:
Oneplus update files are not "flashable" and often do not contain a full os. They are meant to be interpreted by the updater app. I would recommend flashable zips made from official files

https://xdaforums.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244

Read instructions carefully, do not skip android versions.
[OnePlus 6 Questions & Answers] t0w3rh0u53:
Thanks! The msm download tool did the trick! :cowboy:
[Touch Diamond, MDA Compact IV General] hazarry:
Bugs with 1.93 (asia) wwe

Hotmail does not like to connect via WiFI, always get connected or established GPRS/3G using phone data despite wifi is on. No problem using live messenger or using other pocket explorer / opera over wifi. So baffling. Hard reset but still remain. Anyone has the same problem?

secondly, the keyboard (full QWERTY) sometimes appear with different font. I will try to upload somephotos if i managed to see that again.
[Touch Diamond, MDA Compact IV General] dysje:
Actually i have the same issues, sort of. Wlivemessenger sometimes just won't connect over 3g/hsdpa but hotmail works like it should.

About the keyboard, that's a weird one, had noticed it before often enough. It goes away when switching to compact qwerty and then back to normal qwerty.

Oh and i have it on me dutch 1.93 rom.
[Touch Diamond, MDA Compact IV General] omidgivi:
I have als noticed a bug:

If you start the Calendar from HTC-Home, it always start in the "Agenda" view no matter if you have selected another view in the Calendar Options (like Day-view).
[Touch Diamond, MDA Compact IV General] tallen3:
I too have noticed a lot of bugs with the Europe 1.93 ROM, on my phone the tasks program is not listed anywhere not in programs. Tasks is on the device luckily I'm using Agendus. Can't say I'm very impressed so far, it's definately quicker, but what on earth made them put the Video Call option on the phone.
[Touch Diamond, MDA Compact IV General] pedmond:
That is intended behaviour - happened with the other official ROMs as well.
[Touch Diamond, MDA Compact IV General] pedmond:
I have Tasks in my Programs list...
[Touch Diamond, MDA Compact IV General] islenet:
hard keys not responding!!!

Hi ... after upgrading from 1.37 to 1.93 rom

- everything was ok for about a day.

- after trying to configure manualy the 3G settings the "answer key", "back key" and "hang up key" stopped responding.

Other possible reasons for the problem could be:

-sync with vista without deliting the previews syng settings for the same device.

-Windows_Mobile_Desktop_6.1 (not sure but everything started after I installed that app....)

:confused:

I did like the speed of the 1.93 Rom but I'm going back to 1.37 which is at the HTC site for Europe until they release something new.

Any ideas or suggestions!!!!???
[Touch Diamond, MDA Compact IV General] omidgivi:
Any way to change it? Perhaps with a reg-tweak?
[Touch Diamond, MDA Compact IV General] davekollie:
on my 1.93 rom i can hardly connect through wifi anymore.

when i turn on my wifi it finds my wireless connection and logs in for about half a minute an then loses the signal.

after that it can't even see my wifi anymore.

dutch rom
[Touch Diamond, MDA Compact IV General] halloj:
What is your wifi power setting?
[Touch Diamond, MDA Compact IV General] davekollie:
I'm sorry,don't understand what you maen by power setting.

My region is set to europe

My channel is set to 3 (best rate with my laptop)

tried all other channels with phone ,not better with any channel.

Mode is set to b and g

had no problems with the 1,37 rom
[Touch Diamond, MDA Compact IV General] rumpleforeskin:
i know how to fix your 1st problem

goto settings

connections tab at the bottom

then click connections icon

choose advanced tab at the bottom

click select networks

in the bottom dropdown box select your internet connection (ie orange internet)

click ok and your done
[Touch Diamond, MDA Compact IV General] stefsamy:
I got exactly the same problem with hotmail and my french official HTC 1.93 ROM. Everything works, even WLM, but not hotmail synch , if I am not connected before to WLM.

Tried to install an older version of WLM, but it breaked more again, so I'm good for a reflash. I will test hotmail by wifi before making any tweak to see if it comes from the rom...
[Touch Diamond, MDA Compact IV General] stefsamy:
I played with all these parameters.

You can effectively make hotmail synch by wifi working great, but then you have no GPRS/EDGE/3G data so when you don't have wifi access, you have to rechange these settings.

In the previous 1.37 rom, wifi was always prior to edge, even to synch hotmail.

Sorry for my poor frenchie english :)
[Touch Diamond, MDA Compact IV General] rumpleforeskin:
if you have these correct it should connect via wifi when available wifi and 3g when you have no
[Touch Diamond, MDA Compact IV General] stefsamy:
It should, yes, but it bugs. But all other programs work perfectly : wifi when available, Data network connection if not.

Other french users have the same problem with the 1.93 ROM
[Touch Diamond, MDA Compact IV General] stefsamy:
I've made an Hard reset and the problem is still the same.

With your solution, it still wants to connect throuth 3G/EDGE.

I realy thinks this is a problem with 1.93 ROM, more exactly the WLM version built in.

I think that the hotmail sychro module of WLM, if launched alone without launching WLM (by doing SEND/receive in message manager), doesn't check if a data connection is already active and launchs automaticaly the connection witch is in the top dropdown box of the menu you told.

But when WLM is launched and connected first, it detects the wifi and use it, and then the hotmail module uses it too...

Everything worked "normaly" in 1.37 ROM.

I will reflash completely my diamond with 1.93 ROM to see, but I've got no hope.....
[Touch Diamond, MDA Compact IV General] rumpleforeskin:
intersting problem.

The main problem i found with WLM in 1.93 is that it uses your "work" or "private network" connection to connect to the internet and not your "internet"

Nearly all other programe use your "internet" connection which is usually set up for internet (both wifi and gprs)

The "work" connection is default to "wap" connection which forces it to only use "GPRS" this makes you have the no wifi problem.

It is unusualy that now you changed your "private" or "work" connection to use "internet" that you still have this problem.

I have a french 1.93 ROM installed on a friends diamond and will investigate at the weekend and try to give better help to you.
[Touch Diamond, MDA Compact IV General] stefsamy:
Thank you.

The worst is that if WLM is launched first and connected, everything's fine. And if I disconnect WLM or close it, send/receive open a cellular data connection.
[Touch Diamond, MDA Compact IV General] stefsamy:
with wifi card netword setting to "internet" or "work", the issue is the same.

I'm going to reflash to see if it's a problem of rom install (don't think so but with chance...)
[Touch Diamond, MDA Compact IV General] htckaiseruser:
YES YES. i know, 1.93 sucks big time. have tried two different cooked roms from here but was back at 1.37 within a hour. now i have same radio that was with the 1.93 rom and no problems at all with my navigation. also all the nasty little bugs from 1.93 dont bother me nomore:)
[Touch Diamond, MDA Compact IV General] stefsamy:
I had the same config before (1.37 rom and 05 radio rom) and it was good.

I've re-flashed my diamond with 1.93, and with this fresh rom (no programm and no tweak), the problem is still the same.

A WLM update/patch could resolve it I hope.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] jonezy8873:
Just had the MIUI 12 update. Apart from the new control center ( which i have turned off) and floating windows there isnt much change ? i was expecting a bit more.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] meilbox:
But under the hood they have fixed some issues like throttling :)

Wysłane z mojego POCO F2 Pro przy użyciu Tapatalka
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] hotcarver1:
Miui 12 for poco f2 global is here.View attachment 5067543

Στάλθηκε από το POCO F2 Pro μου χρησιμοποιώντας Tapatalk
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] AsimRauf_44:
Were to able to download it?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] hotcarver1:
Received via ota.

Στάλθηκε από το POCO F2 Pro μου χρησιμοποιώντας Tapatalk
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] AsimRauf_44:
I also received it via ota, but it is not downloading, gives an error.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] maciekm3m:
Miui12 changed a lot in my poco f2 pro 8gb... Some video apps are lagging. I cannot watch movies normally without lags... Any ideas ? I have switched off power mode related options and also tried to run video app (canal+) in game turbo mode. Unfortunately it did not change anything...
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] jonezy8873:
Try using VLC from playstore
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] AsimRauf_44:
Unable to download the Update, giving error again and again.

Need help...
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Ahmad_64:
I have the same problem. Trying since morning but no use.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] AsimRauf_44:
I used Huawei phones before Xiaomi, never had this issue, quiet frustrating.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] wojasheck:
Battery stats showing 12h of uptime when it lasted 30h from last charging. Statistic bug?

Wysłane z mojego POCO F2 Pro przy użyciu Tapatalka
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] beingvishwa:
I updated to MIUI12 yesterday since then I'm unable to use banking apps Gpay or Imobile. Receiving insert sim error. Terribly disappointed with the rom after all the hype given.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] maciekm3m:
Google chrome is getting frozen very often... Is it only my phone MiUi12 is really really bad on poco f2 pro ...

Ps. I did not notice any problems with google pay or any sim errors. Just lagging videos and frozen issues with google hrome...
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] beingvishwa:
Fixed the issue:). Permission reset to default from App Ops. Only gpay doesn't work, which is manageable at least. I sense Xiaomi screwing something with gpay.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] jonezy8873:
Yeah chrome freeze on mine too
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Danchibald:
For MI it is rolled back... so thats the reason...

Try with downmi apk from play store, and install it manually, or via link

https://bigota.d.miui.com/V12.0.1.0.QJKMIXM/miui_LMIGlobal_V12.0.1.0.QJKMIXM_e14d3cd304_10.0.zip
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] AsimRauf_44:
I was able to download the app using vpn.

Why rolled back though? Any problem?

---------- Post added at 06:47 AM ---------- Previous post was at 06:25 AM ----------

Hey,

I am on miui 12.

I clicked on three dots and then download latest package,

It is again downloading something.

What is that?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Timmy_01:
Last week I've got MIUI 12.0.1.0 | Stable.

But I tested this, too. And I suppose I've got the same MIUI 12.0.1.0 | Stable as before. I see no difference.
[Nook Touch General] nmyshkin:
I am trying to change the directory in which AlReader saves a cover image for use by the "screensaver" routine. As is, the app silently places a cover image as /media/screensavers/currentbook/nook_cover.jpg when an epub is opened. There is no setting available for this choice. Clearly this version of the app knows that it is installed on an NST.

I've decompiled the app and done what I feel is an exhaustive search through all the xml and smali files, looking for things like "currentbook","nook_cover", "screensavers" and other unlikely strings. In my minimal understanding it seems like things of this sort should appear somewhere, but so far I have found nothing.

Suggestions?
[Nook Touch General] Renate:
Yes. Tell me where the apk is.
[Nook Touch General] nmyshkin:
You are too kind. I hope to be educated. Apk attached below.
[Nook Touch General] Renate:
Yes, it's right there.

Because it's a static final, you have to change the value everywhere it appears.

The compiler has already inserted the value where the member name was.

File com\neverland\formats\AlBook.smali:
.field private static final NOOK_COVER_NAME:Ljava/lang/String; = "/media/screensavers/currentbook/nook_cover"
const-string v4, "/media/screensavers/currentbook/"
const-string v33, "/media/screensavers/currentbook/nook_cover"
const-string v7, "/media/screensavers/currentbook/nook_cover"
const-string v4, "/media/screensavers/currentbook/nook_cover"
const-string v4, "/media/screensavers/currentbook/nook_cover"
const-string v4, "/media/screensavers/currentbook/nook_cover"
const-string v4, "/media/screensavers/currentbook/nook_cover"

I always thought that this was the AI, as in artificial intelligence.
[Nook Touch General] nmyshkin:
Wow! So I actually had the right idea but very poor searching techniques. Thank you so much!

Yes, the name of the app has often been garbled. I guess we can thank sans serif fonts for that. I wasn't really sure until I took it apart! Perhaps the Russian developer had "ALLReader" in mind.
[Nook Touch General] nmyshkin:
Erm...I replaced all 9 "/media/screensavers/" with "/storage/emulated/0/Screensavers/" and, alas, it does not work :(

I took that path from the stock file manager, although when something like Tasker looks at the directory it just sees /Screensavers/, while ES File Explorer sees it as /sdcard/Screensavers/

Added to that is it's KitKat with the issues surrounding writing to the sdcard and the entire ROM is on the sdcard, so....

I guess I need to try the alternate paths just to see if either works. I thought the most explicit would be the best, but apparently not.

Edit: it occurs to me now that this feature is apparently implemented for both Nook and Onyx readers. That means the app needs to determine whether the device is either of those. From where? The build.prop file or similar? Whatever the source, the expected path might now be different or the expected string might be different with this sdcard ROM. I guess I need to start looking for "NOOK" and try to find out where it tries to get that information. I see no error messages in logcat when a new book is opened so that makes me suspect the procedure is being ignored and the device not recognized as a "NOOK".
[Nook Touch General] Renate:
Huh? Is this for the NST? There is no "/storage/emulated"

There is "/sdcard".

# set
...
EXTERNAL_STORAGE=/sdcard
...
[Nook Touch General] nmyshkin:
I've been working for a few months on salvaging the abandoned CM 11 sd-based ROM (https://xdaforums.com/nook-touch/development/rd-nst-future-cm11-twrp-t3075458). There is emulated storage there (or so it seems). I've made some progress working around things that are too granular for me to fix (or understand). A screensaver routine is one of my projects and it works OK, but I'd like it to be able to pick up the few readers that offer the book cover feature.

I found a few entries in build.prop identifying the device as a "nook" that were present in the stock ROM but absent in the CM 11 version. Adding these back, rebooting and reinstalling the modded AlReader had no effect. I should add that AlReader correctly identifies and uses the path /storage/emulated/0 for data and library storage.
[Nook Touch General] Renate:
Well, what does EXTERNAL_STORAGE say?
[Nook Touch General] nmyshkin:
Interesting...

EXTERNAL_STORAGE=/storage/emulated/legacy

PHONE_STORAGE=/storage/sdcard0

SECONDARY_STORAGE=/storage/sdcard1
[Nook Touch General] nmyshkin:
No manipulations of the storage path seem to have any effect. I am thinking that the app is not detecting the device as a "nook". The file com/neverland/alr/AlApp.smali includes a flurry of "nook" references (including a glaring typo) along with other hardware references, but I haven't found any others yet. It's not clear to me from scanning the file contents whether the device detection routine lives there.
[Nook Touch General] Renate:
Did you create the screensaver directory by hand?

The original code (in longhand):

mkdir /media/screensavers
mkdir /media/screensavers/currentbook
write /media/screensavers/currentbook/nook_cover.???
[Nook Touch General] nmyshkin:
If this is working right the app itself should create the directories. I have it working now but there are new issues. The modded and original app are both installing as if this was still Eclair. The menus are all funky looking. I'm guessing one of the build.prop entries I added/changed finally got across the info that this is a "nook". So the screensaver routine finally worked with the modified directories. I didn't think the app would say "oh, it's a Nook, must be Eclair." I'll have to undo my changes to build.prop and see if I can produce a change. Should have saved a backup...
[Nook Touch General] Renate:
The graphics of the menu is only determine by the Android version, see res/menu & res/menu-v11

I'm not sure what you want.

All 16 files are in both dirs, if you don't like one style under any circumstances, just delete that whole dir and leave the other as "menu".
[Nook Touch General] nmyshkin:
This was my thought, but I didn't alter the SDK entry in build.prop. Before modding the app, and in previous unsuccessful attempts to change the screensaver image directory, the installation always gave a more modern menu system, not looking like a typical interface on a stock NST. Once I hit on the correct modification to build.prop, the screensaver image directory started to work and the GUI reverted to a sort of crippled version of what is used on the stock NST.

I think I may have located the smali file where device detection (and SDK version) is involved: com/neverland/alr/AlApp.smali

There are the various identifiers found in build.prop, with some redundency, so that model numbers and "barnesandnoble" seem to both be used. Not sure how all that sorts out. I am reluctant to further savage the app to get this one feature working again, but that may be the only way. I have extracted a copy of the original build.prop from the ROM zip so I can compare it with the changes I made. Some entry there triggered the screensaver to work and GUI to go phlooey. Whether there is a magic combination that will fix one without angering the other remains to be seen.

Edit: yes, replacing build.prop with the original version for this ROM breaks the screensaver image routine and restores the more modern menu system to the app (after clearing dalvik and reinstalling). It seems like the most elegant approach might be to let the app see the device as "other" (as soon as I find that...) since that gives the Kit

Kat GUI, and make the screensaver image routine work for "other". But there are probably better approaches. I just don't want to bend build.prop all out of whack to fix this one issue. Who knows what issues might crop up with other apps if I do that?
[Nook Touch General] Renate:
Yes, that's it.

If (ro.product.manufacture == "BarnesAndNoble" || ro.product.device == "zoom2") then it's a Nook

It only knows about (BRNV300, BRNV350) & BRNV500.

So, what is your mod to build.prop?
[Nook Touch General] nmyshkin:
I need to look at that file again and try to see what you saw. I did see "BarnesAndNoble" and "zoom2" and recognized them. In the CM11 ROM the manufacturer was reduced to "bn". This was one of the last things I changed before the screensaver routine started to work. Other entries I changed mentioned "nook" but there were case variations which probably didn't matter. There were a few entries in the stock ROM file that were perhaps redundant or obsolete. I added those originally as well.

I'm guessing the app does not check build.prop every time it runs. That would be inefficient. I just made the change to build.prop for the manufacturer and rebooted. The GUI on the existing install remains nice and modern, but no images are saved when a new book is open. I expect that if I uninstall and then reinstall the GUI will revert to Eclair standards but the screensaver will work. I need to try that before turning in. If that's what happens, your earlier suggestion about the menus is probably the next thing to look at.

Edit: Yes, that's what happens, and a little worse. The app seems to know that /media is the internal storage for the NST so the storage default and library default are set to this during installation. This makes it impossible for it to find the opening "Welcome" document since there is no "/media" so there is an error, but you can still access settings and clear that up. If it can't tell it's a Nook then it correctly identifies storage as /storage/emulated/0 but of course the screensaver routine does not work since that's only for the Nook and Onxy readers. So...need to look at the menu trick at the least today.

There's apparently some Nook specific EPD stuff in the app, so it is probably not a good idea to go for "other" as a device ID.
[Nook Touch General] nmyshkin:
SOLVED

Ugh. This app just knows too much about the NST :mad:

I tried removing one of the menu folders from res at a time, always naming the remaining folder as "menu". The behavior and results are

identical

. When the app is first run it displays the more modern menus one might expect from KitKat (or CM 11). But once you have changed a few settings and exited the app, when you return you are in Eclair menu land, regardless of which menu folder you leave in res. Perhaps there is no way. At least the screensaver image routine is working. That's almost more than I had hoped for.

Edit: Omigosh...I am so blind. Buried in a section of the Settings that I never bothered with (Tuning) because when I had looked in the past it was all weird stuff I would never care about was an option to use "slide menu" instead of the traditional menu. And that was it. I was deceived by the weird menu behavior at start up vs. the behavior afterwards. Once this selection was made I had both the more modern menu system AND the screensaver mod working together.

Thanks again, [MENTION=4474482]Renate NST[/MENTION] for all your help.
[Xiaomi Redmi 7 Questions & Answers] KaiiSukii:
So my fingerrint reader was working fine, until I took out the back panel for a battery replacement, and now the fingerprint option is gone? it doesnt even wakes up the screen when touched.

The sensor itself looks fine, i dont think its a hardware issue, can it be an encryption problem? it does says that the find device storage is corrupted (Started after going back to miui from a custom rom)

Any thoughts?
[Xiaomi Redmi 7 Questions & Answers] swaguduzo:
sounds like it's physically unplugged or something
[Xiaomi Redmi 7 Questions & Answers] ptfuzi:
If its not disconnected maybe it lost its partition when changing Rom

Enviado do meu CLT-L09 através do Tapatalk
[Samsung Galaxy Tab A series Questions & Answers] kirkzp:
Hey, I updated my 2019 Tab A 8.0, SM-P205, to Android 10. I was on the fence about it, but I figured I'd like the security updates and to check it out. But, I find now that I can no longer 'disable' apps. When I go to Settings->Apps, the only options are 'open', 'uninstall', and 'force stop'. I am hoping I can still adb disable, but for non-system apps I should hope I wouldn't need to always resort to that. wtf?

Any ideas?
[Vivo Y51L Questions & Answers] Akshay Kashyap:
Can i install other vivo phone custom rom to any vivo phone like lower vivo phone custom rom to higher configuration vivo phone... And if any one tell how to build custom rom for vivo phone or build custom rom for my phone i will pay you... I need just clean android.. nothing else.. i will pay for it