[Q] bluetooth mouse makes phone vibrate - General Questions and Answers

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.

Related

[Q] Samsung Galaxy Tab 2 10.1 + Stylus issues

Hi all.
I've reading and researching about using Tab 2 and a stylus, in every page or blog I found ppl keep saying "Install Touchscreen Tune". Unfortunatelly, touchscreen tune is not compatible with Tab 2 version.
Does anyone know how to get rid of this problem? Some console code, some parameter to change, anything?
I would really appreciate if you can help me finding a solution...
Thanks in advance,
Herman
Not sure what could be done. I had one and disliked it. Bought a $30 decent model too (and returned it) Even with the touch sensitivity on 10 it sucked.
scottx . said:
Not sure what could be done. I had one and disliked it. Bought a $30 decent model too (and returned it) Even with the touch sensitivity on 10 it sucked.
Click to expand...
Click to collapse
I bought a Samsung Conductive Stylus but it's the same... I hope Touchscreen Tune developers hear us xD
SYNAPTICS S7301 driver?
incanus76 said:
I bought a Samsung Conductive Stylus but it's the same... I hope Touchscreen Tune developers hear us xD
Click to expand...
Click to collapse
i heard from vitalyj, the guy behind touchscreen tune, that samsung used the SYNAPTICS S7301 chip (which is incompatible with his app as of now) for the tab 2. The guys from cyanogen mod project wrote a driver for the chip at least for a s2 fork or something, i saw the code on github but i do not have enough posts here to post the direct link unfortunately
Its CyanogenMod / android_kernel_samsung_smdk4412 project, "synaptics: Add S7301 touchscreen driver " commit.
Could this help for a development of a similar app for the tab 2? Could one compile the kernel and post the console commands for the settings or is it too hard to do fast or a t all?
PS: Hello XDAforums!
Increasing the sensitivity won;t improve the resolution of the touch screen. If you are thinking you will get results like the Samsung note with S-pen, think again. These screens are made to work with fingers.
DigitalMD said:
Increasing the sensitivity won;t improve the resolution of the touch screen. If you are thinking you will get results like the Samsung note with S-pen, think again. These screens are made to work with fingers.
Click to expand...
Click to collapse
yes but being able to set the dead movement delay to zero would be nice...
Kargoroth said:
yes but being able to set the dead movement delay to zero would be nice...
Click to expand...
Click to collapse
+1 Just setting min-movement from 10-20px to 0px or so, would help a lot. Now I'm just unable to "draw" small things because it requires a "big" movement to start painting. Of course, not that I bought the Tab 2 instead of the Note 10.1 to draw... but sometimes I'd like more precision.
Tried all apps, but it's the same. I hope someone gets around it. The Synaptics driver post looks promising maybe.
I have a tab2 and the best thing I have found is to use a fine point stylus. I then just use the erase to clean up. Unfortunately these tablets just aren't going to give a fine detail sketch. I have seen my friend knock out some good drawings by zooming in then out and erasing to clean up, l've had no luck.
same request
Kargoroth said:
i heard from vitalyj, the guy behind touchscreen tune, that samsung used the SYNAPTICS S7301 chip (which is incompatible with his app as of now) for the tab 2. The guys from cyanogen mod project wrote a driver for the chip at least for a s2 fork or something, i saw the code on github but i do not have enough posts here to post the direct link unfortunately
Its CyanogenMod / android_kernel_samsung_smdk4412 project, "synaptics: Add S7301 touchscreen driver " commit.
Could this help for a development of a similar app for the tab 2? Could one compile the kernel and post the console commands for the settings or is it too hard to do fast or a t all?
PS: Hello XDAforums!
Click to expand...
Click to collapse
I have been going through the comments and giving "Helpful"ratings to compatibility requests on the Touchscreen App in Google Play, to hopefully bring Tab 2 development to the foreground. From what you mentioned above, it might be awhile before we see any solid development.
Omariot said:
I have been going through the comments and giving "Helpful"ratings to compatibility requests on the Touchscreen App in Google Play, to hopefully bring Tab 2 development to the foreground. From what you mentioned above, it might be awhile before we see any solid development.
Click to expand...
Click to collapse
Any news on this?
I have his email address so can shoot him a message if someone can link me the right files.
I'm using the same cheapo stylus with my tab 2 7.0 that I bought for my S3. It works wonderfully on my S3 but horribly with the Tab 2. I can't Swype at all, it keeps losing contact. I need a solution. I have to press really hard with the stylus to select as well. I am honestly thinking of returning it.
Sent from my GT-P3113 using Tapatalk 2
TadeoNYC said:
I'm using the same cheapo stylus with my tab 2 7.0 that I bought for my S3. It works wonderfully on my S3 but horribly with the Tab 2. I can't Swype at all, it keeps losing contact. I need a solution. I have to press really hard with the stylus to select as well. I am honestly thinking of returning it.
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Still paying attention on this issue.
Waiting for solution.
incanus76 said:
Hi all.
I've reading and researching about using Tab 2 and a stylus, in every page or blog I found ppl keep saying "Install Touchscreen Tune". Unfortunatelly, touchscreen tune is not compatible with Tab 2 version.
Does anyone know how to get rid of this problem? Some console code, some parameter to change, anything?
I would really appreciate if you can help me finding a solution...
Thanks in advance,
Herman
Click to expand...
Click to collapse
guys u can make ur own stylus am using it now its great check this video
http://m.youtube.com/#/watch?v=opm0B1jd19A&desktop_uri=/watch?v=opm0B1jd19A
press thanks if helped
antonio1475 said:
+1 Just setting min-movement from 10-20px to 0px or so, would help a lot. Now I'm just unable to "draw" small things because it requires a "big" movement to start painting. Of course, not that I bought the Tab 2 instead of the Note 10.1 to draw... but sometimes I'd like more precision.
Tried all apps, but it's the same. I hope someone gets around it. The Synaptics driver post looks promising maybe.
Click to expand...
Click to collapse
Great observation-- it's my problem EXACTLY.
Kargoroth said:
yes but being able to set the dead movement delay to zero would be nice...
Click to expand...
Click to collapse
Well said, also true.
I believe that if the above two parameters could be tweaked it would solve 99% of the touchscreen sensitivity issues with the 2nd generation G-Tabs, and would probably allow use of a stylus with good performance, instead of dismal performance.
GUTTED
This is just ridiculous! It's bad enough that you can't adjust the screen sensitivity but I just can't believe there some sort of hack to make stylus use acceptable!
Up to now I have been really happy with my Tab 2 but its inability to be used with a stylus has just destroyed the main reason I got it - for annotating PDFs with drawings & handwriting.
Extremely disappointed, I still can't believe it! Such a basic feature!
No-one has any thoughts?
I'm going to sell me Tab 2 and get something else. What do you recommend?

S-tablet use our note as little wacom bamboo wireless :)

The app is : S-tablet, It's still in development, but already looking sharp,
Basically it let use our beloved galaxy note as a companion wireless wacom digitizer under Windows,or in plain lenguage:greeaaaat wireless tablet-mouse for our pc I'm using it with my penabled
Stylus and works pretty similar to my wacom, there are things missing like middle or right mouse button setup and sometimes lags a little, but overall great app!
I long for this app
sorry my bad english
Where can we find that app?
mundano said:
Where can we find that app?
Click to expand...
Click to collapse
It's in the Google play market look for s-tablet
Also have a look here:
Stablet.co. kr
looking good, but on my laptop when I connect my mouse go to right botton corner and not moving. it like stuck, I can just click nothing else. whats the problem?
scorpio1991 said:
looking good, but on my laptop when I connect my mouse go to right botton corner and not moving. it like stuck, I can just click nothing else. whats the problem?
Click to expand...
Click to collapse
Try re-installing it? Mine worked like a charm here!
Great little app!
Works well on my laptop and PC in several programs. Tried Photoshop, Paint.net, and even AutoCad...
Some fine tuning still needed (both me and the app.), but I suggest you try this, even if only for fun...
Thanks to OP.
haronte said:
Try re-installing it? Mine worked like a charm here!
Click to expand...
Click to collapse
ok, I will try to reinstall it on Note
Mouse Jumps to Screen Corners, unusable for me, i have been waiting for a app like this for a very long time, someone please share a Fix
Windows 8, LSC ROM
I have the same problem, cursor is always al the corner and i can't move it using spen. i'm using Windows 8 but i'm not sure if that's the problem, i reinstalled both programs with no changes...
Same here rom xxlsc kernel phılZ 3.75
Sent from my GT-N7000 using xda app-developers app
Working great with me, win7 and lsa... havent tried it on painting programs yet like photoshop or anything but the stock windows paint, horrible.
Apart from that it needs time to get used to this thing especially using it as a cursor is a bit of problematic when doing a double click
There are 2 types of expression docks i found in the internet from same developer as well, the differences is the touch feature, using your finger to move the cursor around. The other one didnt have the feature
Here is the md5 for the pc program that has finger touch feature. Compare with the zip, not exe. I believe the one from stablet.co.kr is the latest one and the other is from tweeter
3b6c5453dda980927aa17b1653c38bfc
Try using this program on win7, win8 might be the one giving the problems of unusable stablet apps
Sent from my GT-N7000 using xda app-developers app
Asylum rom & windows 8 doesnt work. Just goes to bottom right corner.
Looks like fun though...
jogai said:
Asylum rom & windows 8 doesnt work. Just goes to bottom right corner.
Looks like fun though...
Click to expand...
Click to collapse
It does, try using it on windows 7 pc, i dint have windows 8 pc so cant try
Sent from my GT-N7000 using xda app-developers app
I read some posts from all you guys using windows 8, so I formatted an old(ish) laptop and installed win 8 on it. There does seem to be a problem, but I think this may be related to graphics, and not win 8 itself.
I will prepare a PC to run win 8 with NVidia graphics and latest drivers etc this weekend, and post anything I find on sunday 30th.
Hope this helps....
Whenever i hold the click, eg press the spen on the pad, i always get a click lock. What i mean is, whenever i tried to paint over an area and hold the soen on the surface for about 10 seconds and longer, the system registers that i still holding the spen on the surface even though i lifted the spen.
Anyone encountered this problem?
P.s
Solved it by disabling the clicklock feature in mouse setting, funny it didnt work when i used the mouse but working when i used this stablet
Sent from my GT-N7000 using xda app-developers app
This is FREAKING awesome! Thank you very much!
a lot of people get right bottome corner problem :/ maybe it ROM problem, or kernel :/
scorpio1991 said:
a lot of people get right bottome corner problem :/ maybe it ROM problem, or kernel :/
Click to expand...
Click to collapse
Most likely an Windows 8 Issue, gotta wait for the Developer to do something about it, Tried my Laptop with Win 7 and it works flawlessly.
Just tried it on my Win8, run S-tablet as Admin. Wow, nice!
I didnt install the dotNetFx4 that came with the package, already enabled on my Win8.
-Ultimate5.1 LSC

[Q] Help: App Teamviewer Quicksupport doesn't work

Hi guys,
I'm writing this post for a friend.
He just bought a N5 device but he needs the app "Teamviewer Quicksupport" in order to use the phone.
He's already got it on a Samsung GS3 with android 4.1.2 and it worked perfectly, but now on the Nexus5 with android 4.4 Kitkat it seems not to work.
I explain you the problem:
When he connects the phone to his laptop using the app Teamviewer Quicksupport, the client on windows shows a black screen.
The app doesn't crash and N5 doesn't freeze.
Is there someone who can help us? i think it's an incompatibility (communication) problem, due to the new version of Android.
We will be very grateful if someone could recompile this app or can suggest us how to fix it.
PS: The device is already rooted (with stock rom).
PS2: If i made some mistakes, I apologize to the moderators.
Thank you!!
Stefanone_91
[Edit] it works on my nexus 4 with AOKPK 4.3.1
I've attached a screenshot
Stefanone_91 said:
Hi guys,
I'm writing this post for a friend.
He just bought a N5 device but he needs the app "Teamviewer Quicksupport" in order to use the phone.
He's already got it on a Samsung GS3 with android 4.1.2 and it worked perfectly, but now on the Nexus5 with android 4.4 Kitkat it seems not to work.
I explain you the problem:
When he connects the phone to his laptop using the app Teamviewer Quicksupport, the client on windows shows a black screen.
The app doesn't crash and N5 doesn't freeze.
Is there someone who can help us? i think it's an incompatibility (communication) problem, due to the new version of Android.
We will be very grateful if someone could recompile this app or can suggest us how to fix it.
PS: The device is already rooted (with stock rom).
PS2: If i made some mistakes, I apologize to the moderators.
Thank you!!
Stefanone_91
Click to expand...
Click to collapse
I suggest contacting the developers. Support ticket, or something.
I've yet to be able to use TeamViewer without a TouchWiz ROM, even on my S4.. if I flashed CM10 or something else, it wouldn't work. But if I went back to a TW ROM, it works.
Aerowinder said:
I suggest contacting the developers. Support ticket, or something.
Click to expand...
Click to collapse
Thank you For the answer...could you tell me how to contact a daveloper? And who could i write to?
Thank you in advice
In my experience team viewer doesn't work on any device that i've had with 4.3 or above. It would not display my note 3 screen stock or rooted. it worked on my s4 and about 4 other s4's on different networks. But I'm not surprised it doesn't work on kitkat.
I think teamviewer needs to update their software.
I've already written to the teamviewer support, but they didn't answered me
galaxy s4 with original 4.3 not working. i can only see a black screen, although it seems that keyboard input from the PC is working ok (entering text, moving through icons etc.)
i'm also interested in a resolution to this...
I have the same problem and I've messaged the developer to see if they can look into it. Are there any good alternatives to QuickSupport?
According to their page, QuickSupport only works on Samsung phones. Between this fact, and that even recent S4 owners cannot get it to work, seems that it was mainly for SGS3, which I can confirm does still work. Unless they update, I doubt it will work on any non-Samsung phone.
wideasleep1 said:
According to their page, QuickSupport only works on Samsung phones. Between this fact, and that even recent S4 owners cannot get it to work, seems that it was mainly for SGS3, which I can confirm does still work. Unless they update, I doubt it will work on any non-Samsung phone.
Click to expand...
Click to collapse
Hi,
as i said in a previous message, the app works on my LG Nexus 4, which is not Samsung.
This is a link to a page that shows the app's compatibility whith other devices/brands:
"androidpolice.com/2013/07/12/teamviewer-quicksupport-drops-samsung-exclusivity-now-offering-free-remote-support-on-all-devices"
This weekend i'll have a test with my Nexus 4 (mounting Android 4.4 Kitkat) in order to see if the problem is caused by a newer SO.
DeanPall said:
I have the same problem and I've messaged the developer to see if they can look into it. Are there any good alternatives to QuickSupport?
Click to expand...
Click to collapse
there aren't any other alternatives for android 4.4
The support has just sent me an e-mail:
Dear Sir,
Thank you for getting back to us.
We got some news from our developers that this is unfortunately a known problem in the current version. Our developers are already working on a solution and this will be fixed as soon as possible. We are really sorry about the inconvenience.
There is Webkey, which also works as remote access for Android devices. I got it working on Nexus 7 (2013) and Nexus 5 with KitKat, but only on the same WiFi network. Can't seem to get it to work on mobile or outside WiFi networks.
The developer also seems to be on hiatus or abandoned the app - no update in over a year.
Hopefully TeamViewer comes up with a fix for KitKat soon.
sierratango88 said:
There is Webkey, which also works as remote access for Android devices. I got it working on Nexus 7 (2013) and Nexus 5 with KitKat, but only on the same WiFi network. Can't seem to get it to work on mobile or outside WiFi networks.
The developer also seems to be on hiatus or abandoned the app - no update in over a year.
Hopefully TeamViewer comes up with a fix for KitKat soon.
Click to expand...
Click to collapse
Thank you!!! It works fine!!
I just checked Nexus 5 and 6 with the latest Teamviewer Quick Support. There is still no screen-sharing or true remote control. I am running Pure Nexus 6.0.1.
I also checked both with the webkey app and I am pleased to say webkey works for remote control on both.
del

Help! Google Play Newsstand and Google Now crash after launching

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

[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.

Categories

Resources