yashsingh1/xdaforums huggingface dataset:
[Galaxy Note Pro 12.2 Android Development] chudu1:
The tablet screen goes blank with only the capacitive keys turned on whenever I try to choose a wallpaper from the gallery. I really want to use this ROM. Anybody else has this issue? I have tried repeated clean installs. As long as I choose just the few stock wallpapers everything is fine. The moment I choose some other wallpaper other than the default stock the tablet screen switches off with just the back and multitasking keys turned on. Restarting does not fix it. With great reluctance I am now back to the N7 port but I really would like to try pie on this massive tablet. Please help.
[Galaxy Note Pro 12.2 Android Development] chudu1:
Okay I found out what the problem is. The tablet screen goes blank and does not recover the moment you try to set a wallpaper that is less than the default resolution. In my case in my previous failed attempts I was trying to set a full HD image as wallpaper. This time I tried and was able to successfully set a 2560 *1600 resolution image as wallpaper. I have not tried a 4k resolution wallpaper yet so I am not sure if the same thing happens if i try to set an image as wallpaper which is more than stock resolution. Can somebody else try the same and let me know if they have the same issue with setting a lower res image as wallpaper?
[Galaxy Note Pro 12.2 Android Development] alexcondor:
Updates

2 months there were no updates. When will the next update appear?
[Samsung Galaxy S8 Questions and Answers] Marianitten:
Hi, I have an S8+ with a full glue tempered glass. It started to crack everywhere so i decided to remove it. All the tutorials suggested to just apply heat with an hair dryer and then pull up the screen. The problem is that the heat doesn't seem to do anything to the glue and now I'm with this mess:

[IMG="phone stauts"]https://i.imgur.com/pn7ciGt.jpg[/IMG]

what can I do? Help!
[Samsung Galaxy S8 Questions and Answers] zelenko:
https://www.youtube.com/watch?v=c_MI-7_tfbA
[Samsung Galaxy S8 Questions and Answers] TheMadScientist:
I just carefully pick it off. Took me about an hour to do mine
[Google Pixel 3 Questions & Answers] zswielder:
Hi,

I'm wondering if anyone else has this issue. In my Pixel 3, there are 2 SIMs. The eSIM used for Google Fi and a physical SIM used for RedPocket (on Verizon). The Verizon # is my main # currently, so I normally have Fi disabled (not the service itself but by keeping the Verizon sim as default in my phone). Today, I wanted to check and delete voice messages in my Fi #, so I switched Carrier to Fi in my phone. It seemingly switched just fine, and my About Phone section shows the Fi #. However, if I try to dial my voicemail or any other numbers, it goes straight to Verizon customer support. I'm not sure what's going on. I thought Pixel 3 was supposed to be able to switch between SIMs smoothly.
[Google Pixel 3 Questions & Answers] bartolo5:
I think I know what's going on, I've seen this happening.

This problem seems to arise if you just switch to the Fi eSIM without letting the app know. There's stuff that needs to be updated in Google Fi's backend that goes beyond a SIM switch. What you want to do if you want to switch to Fi from physical SIM is go to the Fi app and tap on activate. This will do a proper switch and calls will go through normally. To go back to physical SIM you can just tap on it.
[Google Pixel 3 Questions & Answers] zswielder:
You were totally right. I just tested your theory and worked perfectly. It is so dumb for Google to make sim switch so painful. Defeats the purpose of having dual sim capability... Thanks for your help!
[Samsung Galaxy S9+ Questions & Answers] jawshdarnit:
Hey! I was wondering if anyone had extracted all the sounds that are on the Google sounds app and if you have can you provide a link?
[Samsung Galaxy S9+ Questions & Answers] Epic htc 1:
Google is your best friend,but I'm sure you already know that.
[Android Q&A, Help & Troubleshooting] kamrantekkit:
I am trying to put my device into fastboot but it stays on fastboot loading screen. i have enabled oem locking but still nothing. the device i am trying to put in fastboot is SMB-H8005
[Android Q&A, Help & Troubleshooting] seba_1985_:
Could You maybe do a ROM backup of that device? I accidently flashed the wrong ROM. I can no find it anywhere on the internet. It's a nightmare.
[Samsung Gear Sport] iainmann:
Anyone know a way of getting podcasts onto my Gear Sport?

Ideally, I'd like to be able to download them onto the watch and listen offline.

I've searched for apps but can't find anything.

Can Spotify be used?

Thanks
[Google Pixel 2 XL Questions & Answers] Ph0z3:
I haven't even booted the device yet, but would like to make slight modifications.

I have to stay "stock" / non-root because of apps I use for work, but can do roms & kernels.

I intend on booting up, installing Pie / latest updates, etc....

I want to use AOSPex & ElementalX right off the batt.

So should I:.

1. Flash AOSPex & set everything up, then flash ElementalX afterwards?

Or.

2. Flash AOSPex + ElementalX together at boot?
[Google Pixel 2 XL Questions & Answers] cd993:
Shouldn't be a problem flashing kernel straight after the rom and before first boot. Though worst case scenario just reflash the rom zip, boot to system, reboot to recovery then flash the kernel
[Google Pixel 2 XL Questions & Answers] Ph0z3:
Right on. Thank you.
[Xiaomi Redmi Note 5 Pro Questions & Answers] coolakshansh:
Anyone else seeing or facing issues of image retention/screen ghosting (I don't know what it's exactly called) on redmi note 5 pro? I noticed it for the first time on grey backgrounds. I guess I've had this device for about 4-5 months now.
[Xiaomi Redmi Note 5 Pro Questions & Answers] alexmason90:
no issue here
[Xiaomi Redmi Note 5 Pro Questions & Answers] xezrunner:
I am, too, experiencing a lot of screen retention, even on low brightness and reading mode on on my Redmi Note 5 AI. Mostly noticable on gray or dark colored backgrounds. They do disappear after a few minutes.

My friend who also has a RN5AI with the same display panel but a lower TP version (0x16 as opposed to my 0x22 in the CIT test menu) experiences no screen retention whatsoever, and his display is actually generally cooler in color on the same settings.
[Xiaomi Redmi Note 5 Pro Questions & Answers] coolakshansh:
Okay, so I have a tianma 0x22 panel on my RN5P as well, and the screen retention is only visible on grey or dark backgrounds, I'm thinking of sending the phone in for a display replacement soon. But
[Xiaomi Redmi Note 5 Pro Questions & Answers] xell75:
I'm on 0x22 version too, but I not face any image retention since I bought it 3 months ago.
[Moto G6 Plus Questions & Answers] murlockhu:
I recently switched from using iPhones to a moto g6 plus in hopes of better customizability and so far I'm not disappointed. I got excited when I heard that it's actually possible to change the boot animation on android devices, but I kind of hit a roadblock while trying to apply one. :confused:

My main concern is that the default boot animation contains mp4 files while the boot animations that are available for download are frame-by-frame ones. Are these two types cross-compatible or do I have to find or make custom mp4 boot animations for my phone ? Additionally I'd like to know if there are already existing mp4 animations that are compatible with the moto g6 plus. I'm terribly sorry if this question was already answered somewhere but after extensive searching I was unable to find any solid threads discussing this topic.
[Moto G6 Plus Questions & Answers] RokCruz:
Yeah it's possible to change bootanimation on Android phones but we need root for that.

There's some apps, magisk modules and we can change it manually placing our bootanimation(.zip) on this path:

/System/media

Here an example extracted form havoc ROM from our G6 Plus

Remember if you change it, first made a backup of your stock bootanimation
[LG V30 Questions & Answers] hassanulhaq:
i want to know best v30 roms? is there any port available for v30 (us998) ?

i haven't find any on xda roms section?
[LG V30 Questions & Answers] ChazzMatt:
Every current AOSP ROM is compatible with US998, as long as it's not AOSP ROM specified only for H932.

IF you have former H931/H933 converted to US998 you'll have to do more steps to get them installed. Better is original US998, former LS998, VS996, AS998.

Sent via open market LG US998 V30/V30+
[LG V30 Questions & Answers] hassanulhaq:
AT&T

i have converted my H931 to us998... which steps you are talking about?
[LG V30 Questions & Answers] ChazzMatt:
Running any H930 AOSP ROM on an US998 converted H931

Good luck.

Even though I have original US998 V30+, I'm still on rooted stock firmware -- with Nova launcher, custom icon pack and some mods, like Anxious Magisk mod, which does a lot of stuff...

https://xdaforums.com/lg-v30/themes/anxiousv30-magisk-mod-t3865146

also this mod:

https://xdaforums.com/lg-v30/themes/enable-native-call-recording-lg-v30-t3869260

Sent via open market LG US998 V30/V30+
[LG V30 Questions & Answers] hassanulhaq:
thanks

so now i can say only aosp based roms are availble not a single port is available?
[LG V30 Questions & Answers] ChazzMatt:
If you mean stock firmware based custom ROMs, the H931 stock zip is somewhat customized.

https://xdaforums.com/lg-v30/development/lg-v30-att-h931-20f-rom-t3872926

But if you mean REALLY customized, debloated stock firmware -- only the former Boombox ROM qualifies. But the dev decided to pull it from release. (It had not been updated since August 2018, and then last month he pulled it even though it was still popular.) Even that one was based on H930, but was compatible with US998, either original or converted. Some people have said they found copies elsewhere by searching, but that's up to you.

Sent via open market LG US998 V30/V30+
[Nook Touch General] nmyshkin:
Has anyone else experienced this? I only have side-loaded books and was thinking of applying [MENTION=4474482]Renate NST[/MENTION]'s mod for showing metadata for all books when I found that I couldn't get anything with a double-tap. I just get a black screen for a moment and then I'm back where I started. I'm going to have to download a B&N freebie to see if the function is working at all, I guess....

Edit: I can confirm. Even with a B&N book I get a black screen flash on double-tap in the Library. So...either the rooting process in NookManager is not quite right for this FW or something else I've done has rendered this function inoperable :( Now the "fun" begins.
[Nook Touch General] nmyshkin:
some additional info and maybe a cause

It turns out there are small discrepancies in the file sizes of three jars often modified, two for NTMM, and one for USB audio microphone recording (and maybe other stuff). The MD5 checksums are different in all three cases between FW 1.2.1 and FW 1.2.2. These are:

android.policy.jar

services.jar

framework.jar

The differences must not be great since the device continues to function in the main, but the issue with needing to resign Opera Mobile and Tasker, along with this new failure of the Library double-tap function suggests all is not quite right "under the hood".

Once upon a time I patched framework.jar myself using files supplied by [MENTION=4474482]Renate NST[/MENTION]. I'm guessing I

might

be able to do that again with the file from the FW 1.2.2. The other two jars would require patching from whatever information can be gathered on the GitHub site where NTMM is documented. Not so sure about that {scratches head and looks woeful}.

The "good" news is that the devices are largely functional and if/when the FW 1.2.2 jars are correctly patched, they can just be copied over without restoring the device to out-of-the-box state and building up (again) from there.
[Nook Touch General] Renate:
Um... (scratches head).

Is it my Library app that we're talking about?

I don't remember anything else for getting metadata.

I did notice one bug, it will (rarely) not get metadata if the zip is corrupted with different info on the zip global and local headers.

The problem is with the underlying Android zip libraries.

If it's only a single book you can desktop unzip and rezip.

If something is flashing or crashing a logcat will tell us something.

---------- Post added at 07:24 PM ---------- Previous post was at 06:57 PM ----------

I put the latest version Library-1.13.apk up (in the signature).

I made it so that you could dismiss the details with a click (handy if you're using a Glow2 without any soft keys).
[Nook Touch General] nmyshkin:
No, and so if the patch you have in the 1.2.1 patches zip applies

only

to meta data showing in your Library app, then at least part of the issue is moot.

I'm in the process of running a back-up even as I type so I can swap out the patched jars for the originals from FW 1.2.2 (one-by-one) to see if that restores the double-tap function in the B&N Library. Probably all three jars should be repatched anyway, but at least this will tell me if I am on the right track.

As for the patching, it's clear what needs to be done with the framework.jar and the audio recording patch you supplied. I've been looking at the patches for NTMM at the GitHub site and those are pretty impenetrable for me. So far.
[Nook Touch General] Renate:
Link, please. I've never used or looked at this.

To compare jars, just apktool d them into separate directories and diff them.

You can easily see which classes are different and by looking at the smali exactly what the differences are.
[Nook Touch General] nmyshkin:
https://github.com/doozan/NookTouchPatches

Yes, I've done this with android.policy.jar from FW 1.2.1 and FW 1.2.2, but I don't see an immediate way to compare them. I come up empty on the "diff" command(?). If I could see the connection between the smali and the info at the NTMM GitHub I guess I might be able to text edit the smali by hand(?) and then recompile the jars? Is that too simple?
[Nook Touch General] Renate:
windiff is MS's graphical version of the Unix diff command.

You can get it here: https://www.microsoft.com/en-us/download/details.aspx?id=18546

It works on directories or files.

C:\>windiff thisdir thatdir
[Nook Touch General] nmyshkin:
OK, got that. So a quick look at a few smali files from the two firmwares shows only a line number difference. I'm sure there's more as there are about 80 smali files in just android.policy.jar

There are probably more proficient approaches but it seems to me that if I were to compare the original 1.2.1 jars to the patched jars distributed with NookManager I would see the patches pretty clearly. Next, I would have to examine the same smali files in the 1.2.2 jars to find the correct insertion points for the patches. Maybe? Then using something like Notepad++, I do a cut and paste. When all the smali files from the 1.2.2 jars have been patched in the same way as those from 1.2.1, then I baksmali the lot and recompile the jar.

Yes?

It sounds tedious, but I can do tedious and there are only two jars to work on.

Edit: OK, so back at the GitHub for NTMM I examined the patches and made a list of the smali files mentioned in each. Presumably these are the only ones actually patched. That narrows it down a lot! There are only 4 files patched in android.policy.jar and 6 in services.jar
[Nook Touch General] Renate:
Oh, I'm finally beginning to get what this is all about.

I hadn't ever seen that doozan stuff.

Those patches are difficult because they are diff generated.

There are only two java source files.

The rest of the patches were manually done on smali files which don't seem to be on that GitHub.

It's silly that ModUtils is installed with a patch, you could just copy it over.

My 1.2.1 patches a bunch of stuff which could easily conflict with the doozan patches or even not conflict but make their patches not patch correctly.

They might even conflict with some changes in FW 1.2.2
[Nook Touch General] nmyshkin:
You've given me some good tools (hopefully used correctly) to help see what is going on. Here's what I think I've learned:

I compared the two jars (android.policy.jar and services.jar) from FW 1.2.1 and 1.2.2. They are not completely identical,

but the smali files which are to be patched are identical

. Next, just to be sure I was correctly interpreting what info I could glean from the GitHub, I compared the original 1.2.1 jars with the patched jars. The only differences were in the smali files I had anticipated.

Unless the situation is more complicated than I think (is that even possible?!), this leads me to conclude that the patched smali files from the 1.2.1 firmware could be copied/added to the 1.2.2 firmware and the lot recompiled (apktool b) to provide patched jars for the 1.2.2 installation of NTMM (from NookManager).

Does that sound right?
[Nook Touch General] Renate:
That should do the job.

You still might have to dig down to fix your original problem.
[Nook Touch General] nmyshkin:
As usual, you are so right.

I patched the 1.2.2 jars so that NTMM would run and that all seems to have gone OK. But after a hot swap, clearing cache and rebooting (which took an agonizingly long time!), I found no change in the behavior that got me started on this in the first place. Nor was there any difference in the ability to install the few apps that needed resigning before they would install. But...I learned something, and whatever other subtle differences there were in the jars, that is now moot as things are now all updated to 1.2.2

Except framework.jar was not, because I had been lazy and didn't want to repatch for AudioRecord, so I had used the jar from 1.2.1. Since my other work had "no effect" I decided to bite the bullet and patch the framework.jar from 1.2.2 for AudioRecord (your patch). That was, um, fun. And when all that was accomplished and I swapped out that jar and rebooted (another loooooong wait) I still did not have the "fix" for the original issue.

Isn't that interesting? Ugh. Maybe it's a kernal issue. I'm not going there because there are no kernals developed for 1.2.2 and none for even 1.2.1 that have what I want. So I'll keep my kernal for 1.1.5 which does everything I want and hope nothing else shows up wonky. Maybe someday I'll return to an old backup of 1.2.2 before the kernal change and see if that is the issue.

Meanwhile I have a set of patched jars for 1.2.2. Now I need to look at the patches for NTGAppsAttack and try to get those updated, just because.

Thanks for the lesson :)
[Nook Touch General] Renate:
Well, you say that a double tap causes action, but not the right action.

(Double tap is kind of unusual, it's usually short vs. long tap.)

If something is dying, it's there in the logcat.

Is an Intent being generated?

B&N uses com.bn.nook.shop.action.show.details

My Library app also covers that. You can try temporarily installing it.

B&N uses a truly goofy Intent style.

This would make it difficult to troubleshoot from the command line with am start -a

It could be that the B&N database is screwed up.

The Intent only tells you to query B&N for the metadata.
[Nook Touch General] nmyshkin:
:o...or, it could be that what's left of my little grey cells are out to lunch:o

I'm sure if I were to search diligently in this forum I would find myself reminding people about the Law of Unintended Consequences and pointing out

exactly this issue

IF Shop.apk is disabled. I can now remember that clearly. But I didn't when I started on this wild goose chase :(

Still, a few new skills, some newly patched jars. Not a bad result overall;)
[Nook Touch General] Renate:
Just to clarify:

I meant that it queries on the device the B&N content provider, not over the network to B&N.

Still, you should have seen something on logcat.
[Nook Touch General] nmyshkin:
And I did. Something about a missing intent. I think that's what finally nudged my stuck memory loose. BTW, I did do a quick install of your Library prior to remembering about Shop.apk. It cured the "flash to black screen and back" for a double-tap in the B&N Library, resulting in only a suggestion of a screen flicker, but not the desired behavior. Thanks again for all your help.
[Google Pixel 3 XL Questions & Answers] d1nd141:
Hi,

i have rooted my Pixel 3 XL without problems.

TWRP & MAgisk is installed.

Now i wanted to disable the new gestures as described here:

https://www.xda-developers.com/disable-android-pie-gestures-google-pixel-3/

unfortunately, the USB Debugging does not stay on.

Also titanium backup always complains about this.

When i enable USB Debugging, i see for a few seconds some "le Mobile android device", but disappeared immediately after.

USB drivers are installed.

Any idea?

Thanks

Btw: adb devices shows me my device in recovery when in TWRP. So cable seems to be ok. (anyway, i installed everything with this cable).
[Google Pixel 3 XL Questions & Answers] v12xke:
Assuming you have enabled USB debugging in Dev settings. You've somehow got the wrong drivers installed. Use a program called USBDeview To remove all the Google related drivers on your PC/Laptop and reinstall the Google USB drivers. There are tutorials out there for step by step, but for some reason your drivers are wrong.
[Google Pixel 3 XL Questions & Answers] d1nd141:
I confirm, Dev options are enabled, so also USB debugging.

Unfortunately when i enable USB debugging (WITHOUT CABLE), go back, and enter again in the Dev options menu, the USB debugging is disabled again..

But nevertheless i reinstalled the drivers as you wrote -> same problem.

I think the problem is the Pixel, not windows, as everything went fine while rooting the device. (usb debugging was active).
[Google Pixel 3 XL Questions & Answers] d1nd141:
Solved!

My fault, enabled by mistake in Cerberus App the "prevent USB Debugging" option!

Should work now :)
[Samsung Galaxy S9+ Questions & Answers] jadams161:
Since the Pie update if I have bluetooth on and connected, my s9+ has no notifications sound. It will vibrate but no sound. I have checked what I think it could be and tried the device in safe mode to eliminate an app issue. Seems Pie has a notification bug. How do I submit issue to Google or get help?

Any ideas on the issue?
[Samsung Galaxy S9+ Questions & Answers] jadams161:
So I did a network settings reset on the device. Seems to have fixed the issue.
[Samsung Galaxy S9+ Questions & Answers] dt64:
I have the same issue on Samsung S9 with Pie.

Because of your post I reset my network settings but the issue is still there. (all the wifi and Blutooth settings are gone).

So, that doesn't seem to fix it.
[Samsung Galaxy S9+ Questions & Answers] jadams161:
You just need to reconnect to your wifi and Bluetooth connections. Mine worked until I restarted the S9 back to no notification sound.
[Samsung Galaxy S9+ Questions & Answers] mlr_90:
Same problem here. If my bluetooth device is connected, but not in my ear, I don't hear the regular notification sound as I did before the upgrade to Pie.
[Samsung Galaxy S9+ Questions & Answers] dt64:
Sorry, but in my eyes that is not a fix if it doesn't survive a reboot.

It's probably a workaround hack with nasty side effects of loosing all connection info.
[Samsung Galaxy S9+ Questions & Answers] JavoSpam:
Someone tried with a factory reset? I'm thinking about doing it, but if someone did it and it did not work...

Enviado desde mi SM-G9650 mediante Tapatalk
[Samsung Galaxy S9+ Questions & Answers] mohmd.nagy:
I have done the factory reset and nothing has been changed, still same issue

I believe Samsung can solve this issue, but as usual they are lazy as their monthly update