Help! Google Play Newsstand and Google Now crash after launching - Galaxy Tab 7.7 Q&A, Help & Troubleshooting

I'm running stock Android 4.1.2 on an international version GT-P6800 (purchased in Thailand).
I've been subscribed to a magazine for months now. But with today's replacement (Play Magazines => Play Newsstand), the Google Play Newsstand app crashes immediately on launch. Same story for the updated version of Google Now (released over the past week).
Due to increased sluggishness of my tablet, I decided to backup data and do a factory reset. So all these problems are occurring on a "fresh" OS install. (So no significant app caches, etc.)
Newsstand and Google Now/Search are both working fine on my ASUS tablet, so these problems are definitely specific to this hardware/OS version.
Is anyone else having either or both problems? Ideas?
P.S. This is really making me more inclined to finally root my tablet and install the most stable custom ROM available.

Just tried Newsstand an I too am having issues, also been having issues with Google Now . I started a thread regarding that issue as well. Really getting frustrated
Sent from my GT-P6800 using XDA Premium 4 mobile app

adinis78 said:
Just tried Newsstand an I too am having issues, also been having issues with Google Now . I started a thread regarding that issue as well. Really getting frustrated
Sent from my GT-P6800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same issue on my tab 7.7 4.1 also.
hmm..
so far have no idea how to fix it ...

one more
+1, senda report to Google, maybe help

****mesta said:
+1, senda report to Google, maybe help
Click to expand...
Click to collapse
The problem is almost certainly caused by Samsung modifications to Jelly Bean. My other Android devices don't have any such problems.
I posted a message about my solution in another thread:
http://forum.xda-developers.com/showthread.php?t=2529929

Finally found easy fix!
Uninstall the update & revert back to factory app. Stupid updates just screw everything up! It was ridiculous!

What I don't understand is that my wife's Note I I was able to update both apps with no issues, her phone is running JB 4.1.2
Sent from my GT-P6800 using XDA Premium 4 mobile app

Were is the widget? This seems to be a flipboard take over so google needs widget.

I know I'm not the only one with this issue, anybody have an any ideas as to why Google search no longer works, even after new updates. On My wife's Note II she gets all the updates with no issue, she is also running 4.1.2. This is really pissing me off.
Sent from my GT-P6800 using XDA Premium 4 mobile app

It's happend to my tab 7.7 also..
Google Search And Newstand just crash when ever i lunch it
hopefully can get the fix soon ..

lnxcat said:
It's happend to my tab 7.7 also..
Google Search And Newstand just crash when ever i lunch it
hopefully can get the fix soon ..
Click to expand...
Click to collapse
It's been about 4 updates since problem started, I don't think Google is aware of it otherwise it would have been solved
Sent from my GT-P6800 using XDA Premium 4 mobile app

Another update released today and still same issue, what seems to be the problem?
Sent from my GT-P6800 using XDA Premium 4 mobile app

The power to solve the problem is available. But you'd rather complain.
adinis78 said:
Another update released today and still same issue, what seems to be the problem?
Click to expand...
Click to collapse
The problem is almost certainly Samsung 's work in modifying Android for our tablet model. There are no widespread complaints for other Android devices. And as I said when you started this thread: once I rooted the tablet and flashed Cyanogenmod, the problem became a far-off memory. That's the beauty of the Android community. My tablet can do more things now. And I don't have to think about whether Samsung cares about me.
What did I learn?That if I wanted a 7"tablet today, I would get the Nexus 7. I got a Nexus 4 phone when Google dropped the price. I rooted it in 15 minutes. And Kit Kat is available for it already.

goattee said:
The problem is almost certainly Samsung 's work in modifying Android for our tablet model. There are no widespread complaints for other Android devices. And as I said when you started this thread: once I rooted the tablet and flashed Cyanogenmod, the problem became a far-off memory. That's the beauty of the Android community. My tablet can do more things now. And I don't have to think about whether Samsung cares about me.
What did I learn?That if I wanted a 7"tablet today, I would get the Nexus 7. I got a Nexus 4 phone when Google dropped the price. I rooted it in 15 minutes. And Kit Kat is available for it already.
Click to expand...
Click to collapse
How can you recommend using Cyonogen when all of these issues are present?
1. Inherent from CM10.1
  - Wifi-tethering, hdmi, Incall screen landscape, etc.
2. Bluetooh not working
  - Need to see if the mojo in cm10.1 works here. (Lots of works...)
3. Camera not working yet
  - Both camera can preview, Autio focus is OK for back camera. Can't save the photo...
   (Seems bugs in framework_av cause it)
4. The default orientation of lockscreen is lanscape.
  - not respond to rotation lock. Workaround: set only one angle in settings and enable rotation.
5. Screen rotation or rapid refresh cause transient noices. (Seems the new opengl issue, will try the new r3p2 mali driver later)
Unless you have a different version where everything works as it should.
Don't get mad, just pointing out the flaws of your suggestion.
Also my wife's Note II does not have this issue so I don't think it is a Samsung issue, then again I might be wrong.
Sent from my GT-P6800 using XDA Premium 4 mobile app

First off, I want you to know I am not angry; I am just realistic. Samsung released the GT-P6800 as part of their typical tactic: they offered tablets in every possible size:
7", 7.7 with AMOLED, 8.9, 10.1.
Then they waited to see what the market wanted. Our model's AMOLED display was an expensive (but excellent) component. When the smoke cleared, Samsung followed the market's signal. They never released a follow-up and decided on the Note series as a better product family. We are never going to get Samsung's attention. Between your experience, your wife's and mine, we know that the crashing apps only happen on the 7.7. So there is a combination of Samsung OS and hardware that causes the problem. For the reasons I just cited, Samsung IS NOT GOING TO OFFER FIXES OR PATCHES.
You've done a great job listing possible reasons why someone would not do what I did. (To root and flash a new ROM.)
So let me respond directly to your points.
adinis78 said:
How can you recommend using Cyonogen when all of these issues are present?
Click to expand...
Click to collapse
It's because of my priorities: I care deeply about reading on my tablet. That includes my subscription to The New Yorker magazine (via Newsstand) and PressReader for a variety of global newspapers. If I can't read what I want, I have to find a solution. You complained about Newsstand, so I told you how to get Newsstand working.
Another fringe benefit: I can get rid of the crap Samsung put in the firmware: Social Hub, Readers Hub, widgets, old PressReader, old Pulse, etc.
adinis78 said:
1. Inherent from CM10.1
- Wifi-tethering
Click to expand...
Click to collapse
I can confirm this does not work. If Samsung would release their WiFi drivers to the development community this problem could be fixed. (If Samsung is too busy with more profitable products, they should let the customers fix the problem, no?)
adinis78 said:
hdmi, Incall screen landscape, etc.
Click to expand...
Click to collapse
I have not tested these things.
HDMI
A direct physical HDMI connection is a pretty clumsy way of communicating with a TV. I'd rather use XBMC, DLNA, or one of the streaming boxes and "cast" the content to the TV across my network. Who needs to run a cable across the living room or bedroom between TV and tablet?
adinis78 said:
2. Bluetooh not working
Click to expand...
Click to collapse
Bluetooth is working. I use it.
adinis78 said:
- Need to see if the mojo in cm10.1 works here. (Lots of works...)
Click to expand...
Click to collapse
Sorry, I don't know what mojo is.
adinis78 said:
3. Camera not working yet
- Both camera can preview, Autio focus is OK for back camera. Can't save the photo...
(Seems bugs in framework_av cause it)
Click to expand...
Click to collapse
I did not spend a lot of time testing this. But I was able to save pictures from the back camera. I did not test the front camera. A quick test of Skype was not successful connecting even though wifi is working.
adinis78 said:
4. The default orientation of lockscreen is landscape.
- not respond to rotation lock. Workaround: set only one angle in settings and enable rotation.
Click to expand...
Click to collapse
I am not having this problem. I don't remember if this happened on my tablet after flashing CM. But now I am using Xposed framework + App Settings. So almost everything can be forced to auto-rotate.
adinis78 said:
5. Screen rotation or rapid refresh cause transient noices. (Seems the new opengl issue, will try the new r3p2 mali driver later)
Click to expand...
Click to collapse
I am not experiencing any unusual noises. I've never built a ROM so I have no idea about the underlying drivers.
adinis78 said:
Unless you have a different version where everything works as it should.
Click to expand...
Click to collapse
Unfortunately if Samsung won't release all the drivers to the development community, it's unlikely that there will ever be a fully functional alternative ROM for the GT-P6800.

adinis78 said:
How can you recommend using Cyonogen when all of these issues are present?
1. Inherent from CM10.1
  - Wifi-tethering, hdmi, Incall screen landscape, etc.
2. Bluetooh not working
  - Need to see if the mojo in cm10.1 works here. (Lots of works...)
3. Camera not working yet
  - Both camera can preview, Autio focus is OK for back camera. Can't save the photo...
   (Seems bugs in framework_av cause it)
4. The default orientation of lockscreen is lanscape.
  - not respond to rotation lock. Workaround: set only one angle in settings and enable rotation.
5. Screen rotation or rapid refresh cause transient noices. (Seems the new opengl issue, will try the new r3p2 mali driver later)
Unless you have a different version where everything works as it should.
Don't get mad, just pointing out the flaws of your suggestion.
Also my wife's Note II does not have this issue so I don't think it is a Samsung issue, then again I might be wrong.
Sent from my GT-P6800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think you listed the issues of CM 11 , and he's using CM 10.X
By the way I got same problem after updating those two apps. So I just uninstalled updates.
I'm still giving the stock ROM some time , as I own this tablet from only 2 months..but I think I'm gonna move to Cyanogenmod in time, its not only Samsung thing, all stock Roms from all brands I've tested get laggy after few months..:| , even with pure android on nexues 7 , this thing I've never seen with Apple tho they still power their flagship devices with Dual Core, and 1 GB Ram.!
Sent from my GT-P6800 using xda premium

Silver-7 said:
I think you listed the issues of CM 11 , and he's using CM 10.X
By the way I got same problem after updating those two apps. So I just uninstalled updates.
I'm still giving the stock ROM some time , as I own this tablet from only 2 months..but I think I'm gonna move to Cyanogenmod in time, its not only Samsung thing, all stock Roms from all brands I've tested get laggy after few months..:| , even with pure android on nexues 7 , this thing I've never seen with Apple tho they still power their flagship devices with Dual Core, and 1 GB Ram.!
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Don't fill up the whole of your internal sdcard and fstrim (JB only) your partitions once a week or on boot. Also, improve android LMK & min frees with V6SuperCharger, or CrossBreeder etc. This may help, but involves some reading on your part.
Apple don't fill their device with as many useful features (or bloatware), which would require greater hardware capacity. There's no comparison.
Sent from my GT-I9500 using XDA Premium 4 mobile app

I tried and tested http://forum.xda-developers.com/showthread.php?t=2535734 latest Cyonoge romantic version and boy or boy was it buggy, issues with screen rotation (known factor) and bluetooth not working (known issue, and I really used this feature) so decided to go back to 4.1.2 stock and just get used to not having latest version of Google Now. At least I know I have a fully functioning rom and tab. I guess no more need to complain.
Sent from my GT-P6800 using XDA Premium 4 mobile app

These apps with updates working great with PAK 4.2.2 , so its a stock 4.1.2 issue.
Sent from my GT-p6800 using xda premium

Silver-7 said:
These apps with updates working great with PAK 4.2.2 , so its a stock 4.1.2 issue.
Sent from my GT-p6800 using xda premium
Click to expand...
Click to collapse
Could you please provide link to thread, thanks.
Sent from my GT-P6800 using XDA Premium 4 mobile app

Related

CM10 Official 8/18 NFC Issue

I have the official CM10 nightly from 08/18 and I'm still having issues with enabling NFC. When I check the box to enable it, it simply becomes disable - with the check marked. I've tried the office Samsung TecTile app to read some new TecTiles I have as well as another app from the market call NFC ReTag and neither acknowledge any tags.
NFC is supposed to fixed in this build, and I even receive MMS just fine - at least using Go SMS.- which is not supposed to be fixed, right? I did do a full wipe before installing the nightly and everything else is running perfectly, so I'm wonder if anyone else having this problem with NFC.
Also, I've tried with both the original Samsung battery in my girlfriend phone of same model and a QCell battery with NFC capability in my phone with the same results.
It is a known bug that will get fixed in the future.
Sent from my SCH-I535 using xda app-developers app
Oh, I was under the impression that MMS workaround needed applied every reboot and that NFC was working on the on the 8/18 nightly. Thanks.
Yea every one still having problems maybe tomorrow night!!! I hope I'm ready to play with Google wallet.
Sent from my SCH-I535 using xda app-developers app
any update on this yet? last tried the 21/9 nightly and was still broken.
any one able to fix the NFC issue
marcusleemitchell said:
any update on this yet? last tried the 21/9 nightly and was still broken.
Click to expand...
Click to collapse
I have installed the CM 10 stable release and everthing works fine except for the NFC . is there a fix for this ?
I am trying to find the NFCfix.zip file. Please give me the link for it if you have it. Thanks
Try this on post 9
http://rootzwiki.com/topic/36150-aosp-and-nfc/#entry1015538
Props to pimpmaneaton for finding this
Hi guys .. I'm small geek of android .. I got many things crazy with android .. The most amazing one .. Is !!!
I try to use my Xperia P smart tags with my BB bold 9900 and amazingly it appears good .. The astonishing thing is what I figure out that BB support the feature of tracking smart tags where ever it was ..
But android is not .. Or I still can't find it .. If we can develop android to that feature it would be UNBELIEVABLE ... Or can we crack BB map app to get it for android ?
Help me
Sent from my WT19i using xda app-developers app

Recommend app for android stick.

I recently got the mk908ii, so far it's been working out great. Very fast. Wi-Fi is very strong, but the antenna seems kind of fragile(accidentally turned it wrong way and heard a crack). Does anyone have recommendations for any new apps I can use?
Sent from my Nexus 4 using Tapatalk 4
I have had a mk808b for about a week now, these are my must have apps:
-full!screen: for hiding the navigation bar that was there even on "fullscreen" movie playback. I set a pie control for my right upper display corner that now totally replaces the navigation bar. This is actually the most usefull app i found.
-External Keyboard Helper: for starting apps directly with the push of a button on my wireless keyboard (Measy RC12)
-Screen Adjuster: In case you don't want to change the brightness/color settings of your tv
-XBMC (v 13 gotham alpha 1 works quite well for me, if you can live without hardware decoding, the stable v 12.2 (frodo) build would propably be better) + Plugins (1channel, icefilms etc...)
-MX Player: probably better playback of HD content than XBMC
DaPhinc said:
-XBMC (v 13 gotham alpha 1 works quite well for me, if you can live without hardware decoding, the stable v 12.2 (frodo) build would propably be better) + Plugins (1channel, icefilms etc...)
-
Click to expand...
Click to collapse
No need to go stable. All nightlies now have libsf support. I can suggest a specific build if necessary.
Sent from my R800i using xda app-developers app
drinkypoo said:
No need to go stable. All nightlies now have libsf support. I can suggest a specific build if necessary.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
What build are you using? I tried so many different ones. The first 6 alphas with hwaccel and 2 nightlys from last week, but alpha 1 was the only one where youtube worked. All others showed a network connection error. I just finished downloading the alpha 7 from yesterday. I am going to test it now...
DaPhinc said:
What build are you using? I tried so many different ones. The first 6 alphas with hwaccel and 2 nightlys from last week, but alpha 1 was the only one where youtube worked. All others showed a network connection error. I just finished downloading the alpha 7 from yesterday. I am going to test it now...
Click to expand...
Click to collapse
Don't use any of the specific alpha builds, because now ALL nightlies have libsf! I would first try the latest nightly and go from there!
I find that ALL of the XAF builds fail on my MK908. So I gave up on that thread.
Hmm, my MK908 isn't actually plugged in right now and I have to go do some work. But just try the LATEST android nightly build and if that doesn't work ask again and I'll hook up and tell you which build I'm actually using.
drinkypoo said:
Don't use any of the specific alpha builds, because now ALL nightlies have libsf! I would first try the latest nightly and go from there!
I find that ALL of the XAF builds fail on my MK908. So I gave up on that thread.
Hmm, my MK908 isn't actually plugged in right now and I have to go do some work. But just try the LATEST android nightly build and if that doesn't work ask again and I'll hook up and tell you which build I'm actually using.
Click to expand...
Click to collapse
Alpha 7 is the latest build. It was released yesterday. Does the youtube addon work in your xbmc?
DaPhinc said:
Alpha 7 is the latest build. It was released yesterday. Does the youtube addon work in your xbmc?
Click to expand...
Click to collapse
OK, I just hooked up my MK908... still waiting for my tronsmart airmouse from geekbuying so I haven't been messing with it recently
WTF, why isn't full!screen working? XBMC isn't starting fullscreen for no apparent reason. And I am getting errors I've never seen before from XBMC about "Failed to start commoncache"
Looks like my MK908 has developed some kind of problem while I wasn't using it. That's a real mark of quality hardware.
I don't think I will ever buy another android stick PC at this rate. So far I have tried two rikos and one tronsmart and they are all crap. It's too bad nobody mades any Android PC which is not crap. I guess there's some that are kind of OK but they are more expensive than an AMD nettop! WTF. This is why my MK908 wasn't even plugged in. I sure hope Pi****u supports this chip soon.
edit: that's PIC UNT U. Word filters are for children.
Well, I'm not going to be able to give you any useful information, you probably already know that Google is unresponsive to bugs and that XBMC doesn't run very well on Android. I guess I will have to re-flash my MK908. Maybe I'll try just restoring a backup.
What garbage.
drinkypoo said:
[...] And I am getting errors I've never seen before from XBMC about "Failed to start commoncache" [...]
Click to expand...
Click to collapse
That's exactly the porblem i have with all XBMC builds after Alpha 1 (besides the non-functional youtube addon, but i guess thats related because youtube needs the commoncache plugin). But all other plugins work fine, so its not that bad .
If you decide to reflash let me know if it resolves the issue for you.
DaPhinc said:
That's exactly the porblem i have with all XBMC builds after Alpha 1 (besides the non-functional youtube addon, but i guess thats related because youtube needs the commoncache plugin). But all other plugins work fine, so its not that bad .
If you decide to reflash let me know if it resolves the issue for you.
Click to expand...
Click to collapse
actually, I didn't even run youtube, although I may have it installed. and last time I turned my stick on I didn't get these errors. I haven't updated XBMC, either. it's been a week since I've used it.
drinkypoo said:
OK, I just hooked up my MK908... still waiting for my tronsmart airmouse from geekbuying so I haven't been messing with it recently
WTF, why isn't full!screen working? XBMC isn't starting fullscreen for no apparent reason. And I am getting errors I've never seen before from XBMC about "Failed to start commoncache"
Looks like my MK908 has developed some kind of problem while I wasn't using it. That's a real mark of quality hardware.
I don't think I will ever buy another android stick PC at this rate. So far I have tried two rikos and one tronsmart and they are all crap. It's too bad nobody mades any Android PC which is not crap. I guess there's some that are kind of OK but they are more expensive than an AMD nettop! WTF. This is why my MK908 wasn't even plugged in. I sure hope Pi****u supports this chip soon.
edit: that's PIC UNT U. Word filters are for children.
Well, I'm not going to be able to give you any useful information, you probably already know that Google is unresponsive to bugs and that XBMC doesn't run very well on Android. I guess I will have to re-flash my MK908. Maybe I'll try just restoring a backup.
What garbage.
Click to expand...
Click to collapse
You should buy an odroid. Much better hardware and stable
Sent from my HTC One X using Tapatalk 2
My mk908 is working fine. I can even run power hungry games like asphalt 8 on it. Don't know what kind of issues everyone has having. It's it because of xbmc? I haven't used xbmc yet so I can't tell
Sent from my Nexus 4 using Tapatalk 4
KrisPerry said:
You should buy an odroid. Much better hardware and stable
Click to expand...
Click to collapse
are they offering more than a four week warranty yet?
drinkypoo said:
are they offering more than a four week warranty yet?
Click to expand...
Click to collapse
Unfortunately not. I've had mine for 4 months now though and more than happy with it
Sent from my HTC One X using Tapatalk 2

[Q] Any word on screen capture/recording apps or any solution for it?

I recently ran into a thread here:
reddit.com/r/Android/comments/1tilcf/any_word_on_screen_capturerecording_apps_or_any
and unfortunately for me, I'm running 4.3 and adb shell didn't seem to recognize screenrecord command. I check the Play Store and all the apps seem to be useless since 4.1 (some updated only to 4.2 maybe) and newer phones since Galaxy S3, Note 2, etc.
So I was wondering if there is any news. Cheers!
(I'm a new user. Please tell me how this post was. Also, I noticed two minor bugs when posting. First bug is using "preview post" and the check on the checkbox for "Yes, this thread is a Question!" goes away even though [Q] stays in the Title and second bug(?) is having to retype CAPTCHA)
Hello there, regarding to your question, there really isnt a "good" capture or recording app for android yet. Most on the google play store are poor and scams. I suggest you do more research. There maybe one.
Sent from my GT-S5830 using Tapatalk 2
TheUnknownThing said:
Hello there, regarding to your question, there really isnt a "good" capture or recording app for android yet. Most on the google play store are poor and scams. I suggest you do more research. There maybe one.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
So you don't know if anyone's developing a decent recording software? I just tried a bit of SCR screen recorder but after one recording, my phone just crashes and it seems that I'm not alone in this looking at the reviews of screen recording apps. I didn't have such a problem when I was using 4.0... What changed?
Pathos1 said:
So you don't know if anyone's developing a decent recording software? I just tried a bit of SCR screen recorder but after one recording, my phone just crashes and it seems that I'm not alone in this looking at the reviews of screen recording apps. I didn't have such a problem when I was using 4.0... What changed?
Click to expand...
Click to collapse
Probably your phone crashed because of overload or poor ram management (screen recorders use a lot of ram) BTW what do you exactly mean by your phone crashed, did the application crash or the entire phone?
TheUnknownThing said:
Probably your phone crashed because of overload or poor ram management (screen recorders use a lot of ram) BTW what do you exactly mean by your phone crashed, did the application crash or the entire phone?
Click to expand...
Click to collapse
The entire phone, but my phone has problems. I've had a history of bad flashes (GS3 currently running Slim Bean with Cyanogen kernel). However, I've tried with Nexus 7 2013 as well and it's not working too pretty on that either (stock). As mentioned previously, if you look at the reviews in the screen recording apps, they will complain about the apps not working too well on 4.3 and 4.4. Slim Bean is 4.3 at the moment and I just can't wait to use 4.4's ADB screen capture. That would really solve a lot of things and really, no need for apps.
Pathos1 said:
The entire phone, but my phone has problems. I've had a history of bad flashes (GS3 currently running Slim Bean with Cyanogen kernel). However, I've tried with Nexus 7 2013 as well and it's not working too pretty on that either (stock). As mentioned previously, if you look at the reviews in the screen recording apps, they will complain about the apps not working too well on 4.3 and 4.4. Slim Bean is 4.3 at the moment and I just can't wait to use 4.4's ADB screen capture. That would really solve a lot of things and really, no need for apps.
Click to expand...
Click to collapse
Maybe if your phone still has problems, you may want to flash the stock rom and start from there. (Often, the stock rom is the stablest) One more thing, is recording on your phone very important to you?
Pathos1 said:
I recently ran into a thread here:
reddit.com/r/Android/comments/1tilcf/any_word_on_screen_capturerecording_apps_or_any
and unfortunately for me, I'm running 4.3 and adb shell didn't seem to recognize screenrecord command. I check the Play Store and all the apps seem to be useless since 4.1 (some updated only to 4.2 maybe) and newer phones since Galaxy S3, Note 2, etc.
So I was wondering if there is any news. Cheers!
(I'm a new user. Please tell me how this post was. Also, I noticed two minor bugs when posting. First bug is using "preview post" and the check on the checkbox for "Yes, this thread is a Question!" goes away even though [Q] stays in the Title and second bug(?) is having to retype CAPTCHA)
Click to expand...
Click to collapse
I'm not sure if it works on 4.3, so my suggestion might be entirely useless, but a friend of mine uses SCR Screen Recorder for his tutorials. The device we use runs 4.1.2, so like you said, it might not work. Figured I'd throw my .02 in.
TheUnknownThing said:
Maybe if your phone still has problems, you may want to flash the stock rom and start from there. (Often, the stock rom is the stablest) One more thing, is recording on your phone very important to you?
Click to expand...
Click to collapse
I just gave up on custom ROMs and decided to just stick with the stock ROM instead. I'm just going to get rid of the TouchWiz UI. Neither Hyperdrive nor GPE 5.0 worked unfortunately. The GPE ended up with boot loops. Hyperdrive booted, but wifi + phone radio didn't work.
Recording on my phone is okay now, but I'm still looking for a good method for future reference. Well, recording was for my Galaxy S3 and I was trying to make S3 tutorials so it's far too late now. My problem with the ROM is S4, which is also somewhat dated, so recording isn't really necessary for it either. Thanks for asking.

[Q] bluetooth mouse makes phone vibrate

Hello everyone
I just started experiencing a very strange issue in regards to a bluetooth mouse I just started using on my rooted Samsung Galaxy Note II. The mouse works perfectly on the phone, and I'm loving the interface. Just today I opened a google drive document, and immediately noticed that every time I moved the mouse, the phone would vibrate proportionately (i.e. the faster I moved the mouse the harder it would vibrate). I went through all my setttings and turned off all vibration and haptic feedback I could find, including keypress haptic feedback. This had no effect on the problem. Note that this problem ONLY surfaces when viewing google drive documents from the google drive app. All other apps (including other google apps) that I have tried haven't had any problems. Any suggestions would be greatly appreciated as I use google drive quite a bit for school.
Phone specs:
AT&T Samsung Galaxy Note II N7100
Android 4.1.2 with CleanROM ACE 4.6.1
Google Drive version 1.2.563.31
Let me know if any other specs would be useful.
Brett316 said:
Hello everyone
I just started experiencing a very strange issue in regards to a bluetooth mouse I just started using on my rooted Samsung Galaxy Note II. The mouse works perfectly on the phone, and I'm loving the interface. Just today I opened a google drive document, and immediately noticed that every time I moved the mouse, the phone would vibrate proportionately (i.e. the faster I moved the mouse the harder it would vibrate). I went through all my setttings and turned off all vibration and haptic feedback I could find, including keypress haptic feedback. This had no effect on the problem. Note that this problem ONLY surfaces when viewing google drive documents from the google drive app. All other apps (including other google apps) that I have tried haven't had any problems. Any suggestions would be greatly appreciated as I use google drive quite a bit for school.
Phone specs:
AT&T Samsung Galaxy Note II N7100
Android 4.1.2 with CleanROM ACE 4.6.1
Google Drive version 1.2.563.31
Let me know if any other specs would be useful.
Click to expand...
Click to collapse
Maybe try a different rom, custom roms can have some funny bugs
Please quote me in replies.
Sent from Dell Venue 8 3830 using Tapatalk
hunterk11 said:
Maybe try a different rom, custom roms can have some funny bugs
Please quote me in replies.
Sent from Dell Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
Thanks, that might be worth a try. I really do like this rom though, haven't had any issues with it so far. I may wait till Drive is updated again to see if its a bug with the app before I put a new rom on my phone.
Brett316 said:
Thanks, that might be worth a try. I really do like this rom though, haven't had any issues with it so far. I may wait till Drive is updated again to see if its a bug with the app before I put a new rom on my phone.
Click to expand...
Click to collapse
That is a really weird bug though best of luck.
Please quote me in replies.
Sent from Dell Venue 8 3830 using Tapatalk
Same
hunterk11 said:
That is a really weird bug though best of luck.
Please quote me in replies.
Sent from Dell Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
Same here using OPO with stock CM11S, never happened before,, just after the last docs update. It's pretty annoying :/
I appreciate this is necro posting, but I am really stuggling with this exact issue. I have a Nexus 9 and a MS Notebook Bluetooth Mouse 5000, which work perfectly together except for in google docs & slides. I have a stock ROM, and it has always done it. What is even more frustrating is I bought my Mum exactly the same model at the same time (allbeit with a different mouse), my mouse works perfectly for her and the mouse I bought her has the same problem on my device.
All this proves to me is that it is my device, and it is nothing to do with the ROM or Android version but I have no idea what is causing it. Problem is I wanted to use this as a laptop replacement and using docs and slides was a big part of that. I have tried clearing the cache and uninstalling updates on the app (I can't uninstall it completly as its a preloaded app in the Nexus 9). If anyone found a solution I would love to hear it. I might try resetting my device to factory settings to see if that cures the issue.

Swiftkey opening slowly (due to RAM problems?)

Hey all,
I'm using swiftkey on my galaxy s6 and sometimes when I press a textbox in an app like whatsapp or hangouts it takes a while before the keyboard pops up. Also, sometimes it has to reload the dictionary after the keyboard opens (this takes just around a second). Are there more people with this problem? I didn't had this on my Xperia Z1. Is this problem RAM related? Because of the aggressive app killing on the s6.
I'd like to hear from you guys!'
greets,
swa100
When I'm opening the keyboard it sometimes says "loading predictions". That's what I mean with "reload the dictionary".
Sent from my SM-G920F using Tapatalk
No issues at all with SwiftKey
Sent from my SM-G920W8 using Tapatalk
swa100 said:
Hey all,
I'm using swiftkey on my galaxy s6 and sometimes when I press a textbox in an app like whatsapp or hangouts it takes a while before the keyboard pops up. Also, sometimes it has to reload the dictionary after the keyboard opens (this takes just around a second). Are there more people with this problem? I didn't had this on my Xperia Z1. Is this problem RAM related? Because of the aggressive app killing on the s6.
I'd like to hear from you guys!'
greets,
swa100
Click to expand...
Click to collapse
What firmware version are you on? Is it the newest? Because I believe the issue is with the newest Samsung firmware. It has nothing to do with the hardware
as much as this phone lags I think this is an issue with the app. It did the same on my m8 and that phone never lagged with any other app. It was the reason I stopped using Swiftkey and I now prefer Google over it as the swipe text is way better on that
Sent from my SM-G920T using XDA Free mobile app
otariq said:
as much as this phone lags I think this is an issue with the app. It did the same on my m8 and that phone never lagged with any other app. It was the reason I stopped using Swiftkey and I now prefer Google over it as the swipe text is way better on that
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
+1
I also switched from Swiftkey to Google because of performance. That was on m7 and I tried again on S6E and, once again, preferred Google Keyboard due to performance. A shame though as Swiftkey used to be so good. Having said all that, perhaps it wouldn't suck so bad if this phone had better ram management.
I have the same issues with SwiftKey. I am running on latest Samsung 5.1.1 firmware. Sometimes everything seems to be fine and sometimes it takes years to pop up. I have no clue why. Already tried to reinstall, clear the app cache, no effect.
Sent from my SM-G920F using XDA Free mobile app
Flash this latest stock 5.1.1 ROM via odin to improve your RAM problems.
http://www.sammobile.com/firmwares/download/51431/G920FXXU2BOGF_G920FOLB2BOG9_GLB/
drock212 said:
What firmware version are you on? Is it the newest? Because I believe the issue is with the newest Samsung firmware. It has nothing to do with the hardware
Click to expand...
Click to collapse
Yes I'm on the latest firmware (BOGB). Ram management actually seems a little better then before. But SwiftKey isn't working as it should.
drock212 said:
What firmware version are you on? Is it the newest? Because I believe the issue is with the newest Samsung firmware. It has nothing to do with the hardware
Click to expand...
Click to collapse
roydok said:
Flash this latest stock 5.1.1 ROM via odin to improve your RAM problems.
http://www.sammobile.com/firmwares/download/51431/G920FXXU2BOGF_G920FOLB2BOG9_GLB/
Click to expand...
Click to collapse
I'm on the latest Dutch firmware (BOGB). That one should be latest.
Can anyone confirm that the same problems occur with the latest beta version of SwiftKey?
I confirm that the bug has appeared with latest firmware. Yes, the new firmware has much better multitasking and ram management but this bug with swiftkey is so annoying.
I've got the same issue since a few days. I have an S6 with stock firmware running (5.1.1) and SwiftKey 5.3.4.67
Any workaround available already?
Same problem here... Let's hope for a quick update from Samsung or SwiftKey...
Envoyé de mon SM-T800 en utilisant Tapatalk
I am really feeling like bought ****tiest phone. Sucks bad. My nexus 5 Galaxy s3 was better. Always face issue of keyboard. Feels little went backwards
Hey Guys, you're not alone and Swiftkey is notified about the issue but they're not sure if they can solve this problem. Take a look in the forum here: https://vip.swiftkey.com/index.php?/topic/12733-slow-showing-keyboard-on-s6-bug-reported/
But I think the biggest chance of getting this fixed is to inform Samsung about this problem and wait for a fix (if possible). Does anyone know if they are also already informed?
I have the same problem I live. I'm going crazy.. I sent it to the service. Load the software and they sent it back. The problem still continues.
Do you have any news friends?
No news.. I updated the firmware to latest version. Still same problem!
emptyragnarok said:
No news.. I updated the firmware to latest version. Still same problem!
Click to expand...
Click to collapse
Unfortunately, the last update does not solve the problem. Maybe with the next update the problem is solved.

Categories

Resources