yashsingh1/xdaforums huggingface dataset:
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] hackingmem:
Samsung solved the issue on the new roms which are available realised new countries roms. For example I was using Netharlends 5.0.2 and my Logitech was out but I installed Turkey verison and it works great!
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Ausraster:
Hey guys, maybe I'm joining too late to the party but I recently bought the Logitech keyboard and connected it to my tablet. The connection works and it stays connected, but typing does not work. No matter what key I press it doesn't work. Does someone know how to fix that?

(I'm on stock 5.0.2 from xda)
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] shonkin:
This was fixed. As long as you have gone thorugh the whole bluetooth pairing process with the keyboard (scanning with bluetooth until it finds it, then typing in the code it offers to pair), it should work.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Ausraster:
I know that the connection bug was fixed, but that is not my problem. I already connected it properly, but I still can't type.

Edit: Problem "solved". I flashed another Lollipop version and it worked. No clue why it didn't on the stock one.
[Xperia Z4 Tablet Accessories] Weltherrscher:
I'm wondering about the Z4 Tablet stylus compatibility?

Has anyone already tried some pens with it?
[Xperia Z4 Tablet Accessories] Weltherrscher:
Noone tried a Stylus?

So i did:

Today i tested the Wacom Bamboo Stylus fineline and solo.

I have a IVSO-Glass to protect the Display so that may interfere with the stylus' compatibility.

The Stylus fineline did work somehow, but rather bad (not connected with bluetooth since i had no time).

Interupted lines, no clicks and so on.

The Stylus solo worked as it should (with a little input-lag), but sometimes the tablet didn't recognize a click.

Testing App was Autodesk Sketchbook.

The Bamboo Paper App crashed on opening the notes...
[Xperia Z4 Tablet Accessories] awionetka:
I have adonit jot pro 2.0 - it works.
[Xperia Z4 Tablet Accessories] pdes:
Is that the Bluetooth stylus? Does it work with any app on the tablet?

Thanks
[Xperia Z4 Tablet Accessories] awionetka:
https://www.google.com/search?q=adonit+jot+pro+2.0
[Xperia Z4 Tablet Accessories] mg210789:
what about ES22 sony ?

did someone try it ?
[Galaxy Tab S Q&A, Help & Troubleshooting] Creeper123:
Note:This is my 1st post.

I have a Samsung galaxy tab s 10.5(SM-T800) with Android 4.4.2.

I am planning to update it to 5.0 using Odin,does the 5.0 update supports USB OTG?(not DAC)

I do not want to root the device.

Thank you!
[Galaxy Tab S Q&A, Help & Troubleshooting] 3DSammy:
I'm using v5.0.2 and an USB OTG microSD card reader. It worked without issue when the microSD card was formatted with exFat. I had to root and use an additional program (OTG USB Helper) to get NTFS and ext2,3,4 support plus flash a small small system file change. So if you stick with exFat format you should not need to root.
[Galaxy Tab S Q&A, Help & Troubleshooting] Creeper123:
So, will it work like on kitkat 4.4.2?
[Galaxy Tab S Q&A, Help & Troubleshooting] 3DSammy:
I never used OTG on 4.4.2 as I upgraded the OS as soon as I got my Tab S powered on. So I cannot answer that question. What I can say is that on lollipop v5.0.2 an OTG connected micoSD card formatted in extFat was accessible. As I'm now rooted and have applied some patches I cannot add any more as my device no longer matches the parameters (stock, unrooted, lollipop) of your original question.
[Galaxy Tab S Q&A, Help & Troubleshooting] maxal:
Yes it did on for me on my T800
[Galaxy Tab S Q&A, Help & Troubleshooting] Creeper123:
After the lollipop update?
[Galaxy Tab S Q&A, Help & Troubleshooting] maxal:
Before and after.
[Galaxy Tab S Q&A, Help & Troubleshooting] Creeper123:
Thanks for helping me!:)

I will update to lollipop using Odin: htt p://w ww.android.gs/update-galaxy-tab-s-10-5-wifi-android-5-0-2-lollipop/

^ ^When pasting remove the space!

Thanks
[Xperia Z1 Q&A, Help & Troubleshooting] Nooberoid:
Hi

I am running stock 14.5.A.0.270, rooted and bootloader unlocked. Sony Xperia Z1

My camera app opens up, the camera button on the side of the phone even works. You push the capture area and front camera freezes and normal camera just shows me two buttons and won't do anything.

Please help I do not know what to do. There were a few other threads with a similar problem but I haven't found the resolution yet. Is it because bootloader is unlocked, I have read that I should restore the ta partition and relock my bootloader but I thought I will try here first.

I thought it would be fun rooting and flashing phones but so far just a big timewasting headache. I was on CM12.1 before , nightlies they were good but then it wouldn't recognise my sim card.

RR I tried but I got stuck on the bootloop.

Now I am back on a stock and my camera doesn't work :( :(

Help me please, I want to learn more

Many thanks for your time
[Xperia Z1 Q&A, Help & Troubleshooting] ven1x:
Sorry I'm a bit late it seems but i had the exact same problem, camera wont focus and take pictures, video did still work depending on firmware but unfocused. Chances are your asking here because you lost your TA partition and DRM keys, which is most likely the cause

Solution:

make sure your phones bootloader is UNLOCKED

1. Grab flashtool

2. open Xperifirm via flashtool

3. look for 14.3.A.0.757 firmware (for journalists and media) (MUST be downloaded via xperifirm)

3. Download and unpack automatically, let flashtool do its thing til its ready

4. Relock your bootloader, DO NOT start your phone or touch your phone, keep it in flashmode

5. flash the firmware you just downloaded (14.3.A.0.757)

6. start your phone, camera SHOULD be working

7. Unlock bootloader and Flash any .ftf you like, tick EXCLUDE in the box that says .TA when you flash / if its available

8. Enjoy
[G 2014 Q&A, Help & Troubleshooting] eymas:
While I am confident this issue has been reported several times and probably solved by the time I am writing this, still I remain curious to see what could be done right now to solve this.

The story goes that when using Chrome on my phone (XT1068 - Moto G 2014 with Stock 5.0.2) it doesn't take long until the device slows down to a crawl, leading to response times ranging from 10 seconds to a full minute. Either leading to android soft-rebooting or forcing a hard-reboot in order to return the phone to a normal and usable state.

Coincidentally various services tend to get killed as well (The audio player is a very obvious example) which is known behavior during these leaks.

I know the issue may have been solved already in future android builds, but until those are released; what are the current options to combat the above issue?

Don't want to flash CM again for a while as well, trying to keep it stock for as long as necessary ;)

But if it is needed, i've no objections.
[G 2014 Q&A, Help & Troubleshooting] Deleted member 4251708:
2 fixes for 2 memory leaks:

(this one requires Xposed)

http://xdaforums.com/xposed/modules/xposed-fix-lollipop-memory-leak-t3065296

(this one has been integrated into CM12)

http://xdaforums.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
[Asus ZenWatch] itm:
I'm using the Airfighter watchface and it permanently displays Google Now notifications at the bottom of the watchface (obscuring the step counter which is also displayed there). I can open each notification and swipe it away, but then it just gets replaced with the next Google Now card. How can I configure this so that Google Now cards are only displayed if I swipe down on the watchface?
[Asus ZenWatch] CSX321:
In the Wear app on the phone, tap the gear icon to get to Settings, then tap "ASUS ZenWatch" under Device settings. Turn off "Card previews". I think that will do what you're asking.
[Asus ZenWatch] itm:
Thanks for the reply. I was hoping that there was an option to keep the notifications on the watch, but not to have them automatically appear on the watchface - i.e. I only want to see them when I swipe up. I guess this isn't possible.
[Asus ZenWatch] CSX321:
I just tried it, and turning off card preview does that. They appear full-screen when they arrive, but otherwise not unless you swipe up.

Edit...I just reread what you wrote, and I guess you mean you don't want them to appear at all until you swipe up. You're right, I think there's not a way to do that, at least not built in.
[Wear OS Q&A, Help & Troubleshooting] itm:
I'm using the Airfighter watchface on my Asus Zenwatch and it permanently displays Google Now notifications at the bottom of the watchface (obscuring the step counter which is also displayed there). I can open each notification and swipe it away, but then it just gets replaced with the next Google Now card. How can I configure this so that Google Now cards are only displayed if I swipe down on the watchface?
[Wear OS Q&A, Help & Troubleshooting] onewingedangelj:
If I'm not mistaken you can do this from the Android wear app. If you go into the device settings in app there should be an option for "card previews" on watch face. Deselect that and you should have stopped them from popping up like that.
[Wear OS Q&A, Help & Troubleshooting] itm:
Ah OK I see that option. Only problem is that it also stops the BeyondPod notification entry from showing, hence preventing me from quick access to the podcast player controls (instead, I would need to open the Beyondpod app, wait for the "Connecting..." to disappear (which it doesn't always), swipe to the controls, then tap play/pause etc. That's a shame, as I only want to suppress Google Now cards, not other apps which put things in the notification shade.
[Wear OS Q&A, Help & Troubleshooting] lekofraggle:
Google now is not supposed to be constantly on your watchface. There are some things you can do...

Limit the notifications by opening Google now on your phone and customizing your notifications.

When you get one (let's say, weather or time to work/home etc.), swipe up to read it, then right to close it.

Or, swipe down to hide it and it should go away.
[Wear OS Q&A, Help & Troubleshooting] itm:
There don't seem to be many customisation options. The only pertinent options seem to be "Show cards" and "Show Notifications for card updates".

I want to be able to differentiate between recurring cards which I don't want sitting on the watch face (e.g. weather, stock prices) and control widgets which sit in the notification shade (e.g. for BeyondPod and Play Music) - which I want to stay on the watchface (or at least be available with a single swipe). I guess there's no way to do this?
[Wear OS Q&A, Help & Troubleshooting] lekofraggle:
You can.

Open up the Google app on your phone (not the Wear app), Google now (which on my phone shows up as just Google).

Slide left or press on the three lines to show the menu.

Click customize

These are the things Google now wants to notify you about. You can turn each one off (e.x. stocks). Some, you can tailor the card.

If you want to use more of a sledgehammer approach, you can disable Google now all together by checking show cards or notifications for card updates in the general settings.

Either way, you should still get notifications for non Google now activities (timers, alarms, beyond pod, music, etc.).

It should be noted that if memory serves, this level of customization only happens after you open Google now on your phone and accept Google's terms. At that point, you can customize, and they will use their algorithm to customize for you even further (the terms tell them it is okay for them to try to read your mind).
[Wear OS Q&A, Help & Troubleshooting] itm:
This will allow me to customise which Google Now cards I see, and which I don't, but it doesn't let me control which ones get put onto the watchface on my smartwatch. I also found that disabling Google Now card previews in the Android Wear app stops the BeyondPod control panel notification tray entry from appearing. So between Google Now customisation and Android Wear customisation I can't seem to isolate and prioritise notification drawer entries which aren't Google Now cards (e.g. the BeyondPod notification widget)
[Wear OS Q&A, Help & Troubleshooting] lekofraggle:
Oh, now I see your dilemma. It is one in general with wear. Your watch mimics your phone. If you want more on your phone than the watch, you need to hack it. This is easy with apps using adb and pm uninstall. If you are adventurous, you could try finding all of the pieces of Google now and disabling them. I am making the code up, but something like...

Pm disable com.Google.now stocks (you do this to your watch through adb).

The way to find the intent to disable is by looking at the manifest of the app.

The difficulty is furtherincreased by the fact that you may need su privileges to run that command on Google now.

Sorry for the long and possibly confusing answer, but hopefully now you know where to begin looking.

Alternatively, you could try a watch face that uses the bottom real estate differently.
[Wear OS Q&A, Help & Troubleshooting] itm:
I suppose the main question for me is: is the BeyondPod player control "widget" that I see in my Notification shade on the phone actually a Google Now card, or simply an Android Notification? If it's the latter (which I had assumed), then I don't understand why disabling Google Now preview cards in Android Wear should stop the BeyondPod controls appearing. Any idea??
[Wear OS Q&A, Help & Troubleshooting] lekofraggle:
Yeah, that is an oddity. I was under the same assumption. Does it share this behavior with any media player? I will experiment and get back to you.
[Wear OS Q&A, Help & Troubleshooting] itm:
Hmmm....I just tried this again - disabling card previews in Android Wear...and this time I still managed to get the BeyondPod control panel on the watch. Either I was mistaken before or there was/is some kind of glitch. So at least I have the nuclear option of killing all Google Now cards and keeping my podcast player controls.

Maybe I'll look at some of the hacks that you have suggested to selectively filter out some stuff from the watch. Last time I tried ADB I couldn't get it to connect to the watch, but I didn't spend too long on it so maybe I should set aside a couple of hours and try again....
[Wear OS Q&A, Help & Troubleshooting] lekofraggle:
Yeah, I disabled all Google now card updates and ran audible, music (I have an htc one, but think it is Google music), and beyond pod, and my watch notified me of all the files playing as well as giving me full control.

I would not write off the bug idea. It strikes me as plausible. And since I own a Sony watch (one that seems to be effected by more of the bugs in the most recent wear update), I would say seems to be likely.
[Advantage X7500, MDA Ameo ROM Development] ade0282:
Hi all,

Thus far has anyone managed to get any version of BB Connect running on WM6?

I have tried but with no joy :mad:
[Advantage X7500, MDA Ameo ROM Development] AMoosa:
I also need help with this. The WM5 ROM had BB Connect pre-installed, but the WM6 one doesn't. Does anyone have the cab from the WM5 one?
[Advantage X7500, MDA Ameo ROM Development] c0rnholio:
Yes. Tonight I took the time to get things sorted. I now have WM6 and BBC 2.1.2.54 running. (Still no luck with BBC4)

Steps that I have done:

- Extracted the WM6 NBH (duttys tool)

- Hex-Edited the windows.nb

Original HEX string is:

4D3EA0E3063083E3452FA0E30510A0E302

New Hex string is:

1D3EA0E3013083E3452FA0E30510A0E301

This resulted in os version 5.1.465 (like the original WM5 for Athena)

- Used the Athena_upgrade package to flash this modified windows.nb to my device.

One word of warning when using this flash method: Be sure to read out the proper handle for the area where the .nb will be stored.

If you want the whole wm6 on your device do the full upgrade with one of the provided WM6-ROMs before flashing the above modified .nb.

- Don't forget to change the AKU to .3.3.1

Thanks to all involved people who provided the tools, wm6 and whatever. You have my greatest respect!

Cheers
[Advantage X7500, MDA Ameo ROM Development] beginner:
Hi Cornholio: could you help me with more details on the process to charge into the pda this .nb file? I am not sure if needed to join in a full nbh all the diferent files with .nb after extract the rom or is needed only flash the os.nb

I tried unsucessfully the tools you mention and is not possible to charge the os. I think it is due my device is WM6 before..
[Advantage X7500, MDA Ameo ROM Development] c0rnholio:
Hi, you only need to flash the windows.nb file. It should also work if you already have WM6 on it. What has to be mentioned is that the itsutils in the Athena_Upgrade Package also did not work for me so I was unable to read out the handle and flash it, but I've downloaded the itsutils from here: http://nah6.com/~itsme/itsutilsbin-20070705.zip

and they worked without any problem.
[Advantage X7500, MDA Ameo ROM Development] beginner:
thanks a lot, you are great!!!

do you have some instructions on how to do it, please?

read and re-read and found it. Now working...
[Advantage X7500, MDA Ameo ROM Development] c0rnholio:
Glad to hear that you figured it out. Sorry for not replying, but I didn't had the time to write a step-by-step guide.
[Advantage X7500, MDA Ameo ROM Development] beginner:
i see that BB 4 works with Black, for 5.1.195. I tried some hacking for WM6 of Athena but BB 4 doesn't connect. I think it checks something more that the operative version.
[Advantage X7500, MDA Ameo ROM Development] walshieau:
BBC 4.* check the ModelID of the device also... hence wont work on an athena.... you have to wait for a version 4.0 for the Athena sorry...
[Advantage X7500, MDA Ameo ROM Development] beginner:
do you know where it checks it? i have the idea of replace the header of the rom file, that says what device is it, but non sure if i coul brick the device.
[Android Q&A, Help & Troubleshooting] ilikered:
After the latest update, it seems like "Touch to save" option has disappeared in Google keyboard. This really makes the process of saving new words to the dictionary painful. We need to select the word click on Add to dictionary and then Ok to save any new word which is a tiresome process.

If anyone had found an easier way to save new words to the Google keyboard dictionary easily, please post that solution here. By the way, double clicking the word also doesn't work. My device is moto g and I believe this is a common issue for any device.
[Android Q&A, Help & Troubleshooting] ilikered:
No answers at all? I thought I'll get help on xda
[Android Q&A, Help & Troubleshooting] xdaHG:
Same here CM 12.1

I too am getting this issue plus I cannot even sync my personal dictionary from the other mobile. Had loads of words saved there. Plus, the AOSP keyboard is doing the same, nothing. Wonder when will it fix. Is it just an installation problem?:confused:
[Android Q&A, Help & Troubleshooting] xdaHG:
Okay, so its been months and I don't think things would go good. The only thing I could do was to install SwiftKey and so far, the experience has not been disappointing, great actually. It does all that Google keyboard does (and did),and more .
[Android Q&A, Help & Troubleshooting] ilikered:
It syncs properly now on Google keyboard. You need to goto settings and enable sync.
[Android Q&A, Help & Troubleshooting] xdaHG:
I enable sync every single time I install Google Keyboard but still of no avail.
[Android Q&A, Help & Troubleshooting] ilikered:
Sometimes, when the keyboard can't find internet connection your words will not appear in the suggestions. I think this happens because all the words are in cloud not on the phone itself.
[Android Q&A, Help & Troubleshooting] xdaHG:
Well, my phone is almost always connected to the internet, so that should not be a problem. Anyways, I haven't tried the latest, GBoard, so I can't really say if it has been fixed.
[Amazon Fire Phone] ggow:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]

Here you can find stock firmware for the Amazon Fire Phone (Kodiak) which are safestrap flashable.

This can be useful when you come to install another ROM, but find yourself wanting to return to stock for some reason.

Please note the following:

- These images do NOT block OTA updates from Amazon so be careful with connecting to Mobile and WiFi networks. An accidental Amazon OTA can spoil your day.

- These images do NOT flash a new kernel or recovery - only a new /system image

- You must be running Safestrap V4.0.1 with a stock base software version 4.6.1

- Do NOT use these images to downgrade or upgrade your base firmware.

Installation:

- Copy file to your phone

- Flash the ROM image in Safestrap

- Flash the latest SuperSU package if you want root

- Still within Safestrap from the Main menu select Wipe

- Then Swipe at the bottom to Factory Reset.

- Finally Reboot.

4.6.1 Images:

UK - ss_update-fire-phone-33.4.6.1_user_461013320.zip <- Flashable on Safestrap v4.0.1

US - ss_update-fire-phone-35.4.6.1_user_461013820.zip <- Flashable on Safestrap v4.0.1

DE - ss_update-fire-phone-34.4.6.1_user_461013320.zip <- Flashable on Safestrap v4.0.1

4.6.3... 420 Variant Images:

UK - ss_update-fire-phone-33.4.6.3_user_463001420.zip <- Flashable on Safestrap v4.0.1

US - ss_update-fire-phone-35.4.6.3_user_463001420.zip <- Flashable on Safestrap v4.0.1

DE - ss_update-fire-phone-34.4.6.3_user_463001420.zip <- Flashable on Safestrap v4.0.1

4.6.3... 620 Variant Images:

UK - ss_update-fire-phone-33.4.6.3_user_463001620.zip <- Flashable on Safestrap v4.0.1

US - ss_update-fire-phone-35.4.6.3_user_463001620.zip <- Flashable on Safestrap v4.0.1

DE - ss_update-fire-phone-34.4.6.3_user_463001620.zip <- Flashable on Safestrap v4.0.1

4.6.6... 820 Variant Images:

UK - ss_update-fire-phone-33.4.6.6_user_466000820.zip <- Flashable on Safestrap v4.0.1

US - ss_update-fire-phone-35.4.6.6_user_466000820.zip <- Flashable on Safestrap v4.0.1

DE - ss_update-fire-phone-34.4.6.6_user_466000820.zip <- Flashable on Safestrap v4.0.1

4.6.6.1... 420 Variant Images:

UK - ss_update-fire-phone-33.4.6.6.1_user_466001420.zip <- Flashable on Safestrap v4.0.1

US - ss_update-fire-phone-35.4.6.6.1_user_466001420.zip <- Flashable on Safestrap v4.0.1

DE - ss_update-fire-phone-34.4.6.6.1_user_466001420.zip <- Flashable on Safestrap v4.0.1
[Amazon Fire Phone] dhack21:
To my understanding

Hello.

First thanks for all your hard work allowing us to install CM11 via safe strap. Quick question as it's been years since I've used a safe strap install. Once installed and CM11 is installed is it possible to boot back into Fire OS? Or is the Fire OS system over written since we're using the stock spot in SS.
[Amazon Fire Phone] ggow:
The short answer is yes you can. There are two options:

- You can do a backup in safestrap of your stock ROM.

- Or you can discard FireOS for now, install CM-11. If you need to go back I have provided a Safestrap flashable 4.6.1 zip in the OP of this thread.
[Amazon Fire Phone] dhack21:
Was my existing system formatted during the install of CM11 however? I only ask as I rooted with king root and wanted to ensure no traces remain after install of CM11.
[Amazon Fire Phone] ggow:
Yes, it's /system is formatted during install of CM-11 so no traces of Kingroot will exist.
[Amazon Fire Phone] kblikefly:
After flash this stock rom, will the fire phone brick if accidently received the OTA updates.

Thank you.
[Amazon Fire Phone] ggow:
To be honest I don't know what will happen. It wouldn't normally brick but I haven't had much experience with this device. Certainly on the kindle hdx's we have seen many bricks due to OTA updates.
[Amazon Fire Phone] kblikefly:
That's fine. Thank you so much for the effort.
[Amazon Fire Phone] rjmohit:
Can you please provide the 820 version stock zip? Thanks!!
[Amazon Fire Phone] ggow:
Yes, I'll build one on Monday.

Thanks [MENTION=6709669]Bingo Bronson[/MENTION], he is going to make US and German variants as flashable zips :)