Related
Does anyoe else's tab do this
When I scroll in a webpage or app, and I stop scrolling but still have my finger pressed on the screen, the screen starts to shake a little until I move my finger again, is it just my tab or is it a common thing?
Sent from my SCH-I800 using XDA App
the only thing i can suggest is that you are slightly moving your finger, its sensitive so might look like its shaking?
kenfly said:
Does anyoe else's tab do this
When I scroll in a webpage or app, and I stop scrolling but still have my finger pressed on the screen, the screen starts to shake a little until I move my finger again, is it just my tab or is it a common thing?
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
Mine does that too. I wouldn't be too worried about it since it only happens in the web browser for me.
Sent from my AT&T Galaxy Tab using XDA App
its not defective, its cause your holding your finger on it, especially in a web browser if your zoomed in a page and scroll it might happen.
its just your finger moving a tad bit that the tab senses. Also it might be catching two touch responses from your finger, not the tabs fault. Its the way you use it really.
Dont worry. The tabs touch response is pretty sensitive, which is VERY good thing trust me. Its better to be responsive then crappy on a touch tablet.
Sorry, but yes, it is a problem
I'll respectfully disagree. I have the same issue in my galaxy tab, and I've tried several others, this behavior is found in just a few.
I've made a video and a drawing test to illustrate it. I've put them in a page in a domain that I own.
(XDA still doesn't allo me to paste a link, but the address is fgfaria.com )
I've tried an app called touchscreen booster, which appeared to be appropriate from its description, but didn't notice any difference.
But there is a very intriguing point. It doesn't look like it's a hardware problem. I have installed touch test app, and with that the touch is perfect, no shaking. Also, specifically in youtube app, when scrolling the list of videos, it doesn't happen.
I need to find out why it happens pretty much everywhere, but not on youtube app and touch test apps.
Just to make it even more complex: as you'll see in the picture in the url above, towards to the right edge of the screen the problem is much lighter or doesn't happen.
If someone can help, that would be hugely appreciated!
Thanks,
Fabio
I'm getting this problem too. I get TERRIBLE shakiness when i hold finger input especially in google maps.
I highly doubt it's a hardware issue because this only started happening to me ever since i installed the italian gingerbread rom.
This this GB rom giving anyone else the same issue?
Same problem here
I am also having the same problem, installed an application called "Touchscreen Booster" but no avail.
Strange thing is that the problem seems to not happen on Youtube application.
I also have GB 2.3.3, in my case, the overcome room 2.0.0
One possible solution
Did you guys check the url I've sent? (fgfaria.com)?
Is your problem just like mine? In my case, I had the problem since Froyo 2.2, and still have it (the same way, no change) after an update to 2.2.1.
My GT is not rooted, and I'm waiting for gingerbread to be made available through Kies in Brazil to proceed with the update.
Another interesting thing is that most touch test apps behave normally (no shakiness).
Possible good news: I've found an app in the Market called "ILITEK Touch Utility".
Unfortunately I couldn't use it in my GT as it appears to require the device to be rooted. But it has several features from calibration to screen software reset. Hopefully this may help, specially as it seems to be a software issue.
Let me know if this works for you.
Regards,
Fabio
mine does EXACTLY the same thing as per your website.
the app does not seem to fix anything...
sigh...
at least good to know someone else is experiencing the same problem.
The problem is app specific
Hi all,
In addition to touch test apps and youtube app, there are some other apps that don't present the problem. One specific interesting case is the one of the HelloListView tutorial presented in Android Developers website.
I've followed the tutorial, and created this illustrative app that just creates a list and allows you to scroll up and down. This specific app doesn't present the problem we've been discussing. I've made it available for download as apk file in the end of that same testing page (fgfaria.com)
That application being so simple and not presenting the problem, and the other apps that also don't present it, makes me think that the problem may appear when some specific library gets included in an app. Possibly something related to hardware acceleration, for example (just guessing, no specific reasons to believe that).
If only we could isolate the cause of the problem, we could notify Google and/or Samsung and influence a new patch release.
This is as far as I have gone so far. Ideas, reactions?
Regards,
Fabio
Or the libraries being used in this tutorial include some kind of filter not used in problematic apps...
I posted about the same problem here:
http://forum.xda-developers.com/showthread.php?t=1096698
I've included pics from my tests. Notice how before I installed the custom rom, the lines were perfectly smooth. This definitely has something to do with the software. We need to have one of the rom devs look at this and find out what might be the cause.
grukko said:
I posted about the same problem here:
http://forum.xda-developers.com/showthread.php?t=1096698
I've included pics from my tests. Notice how before I installed the custom rom, the lines were perfectly smooth. This definitely has something to do with the software. We need to have one of the rom devs look at this and find out what might be the cause.
Click to expand...
Click to collapse
hi grukko, thanks for your comment!
To me, the most intriguing part is that the behavior happens in some apps, and not in other. I have done a very similar test, which I've published in the address http://fgfaria.com
As you see in the thread, the problem doesn't happen in youtube app, and screen touch test apps and in the list tutorial app I've created following instructions in Android Developers website.
Can you check if your problem is the same checking if youtube doesn't "shake"?
Thanks!
Fabio
fgfaria said:
hi grukko, thanks for your comment!
To me, the most intriguing part is that the behavior happens in some apps, and not in other. I have done a very similar test, which I've published in the address http://fgfaria.com
As you see in the thread, the problem doesn't happen in youtube app, and screen touch test apps and in the list tutorial app I've created following instructions in Android Developers website.
Can you check if your problem is the same checking if youtube doesn't "shake"?
Thanks!
Fabio
Click to expand...
Click to collapse
Your test results look similar to mine. I just tried youtube and it does not shake.
New discovery:
It may be a hardware problem (at least in my case). A friend, in another forum noticed that the jittering only happens in screens with a light background, specially white.
This can be quickly tested, by opening a web page that has a white and a black part. Zooming in the white part (so that all background you see is white) and keeping the finger still, the screen starts shaking. If you move to the black part, zoom and keep you finger still, no shake at all.
Regards,
Fabio
Anyone? There is a solution for Galaxy S (forum.xda-developers.com/showthread.php?t=844216&page=3#). There must be a solution for Galaxy Tab 7 too...
Touch screen issues
Count me as another member of the shaky touch screen club! Anyone found a resolution yet?
No luck yet. Official upgrade to Gingerbread is not yet available in Brazil. I'm waiting for this upgrade to check if things get better, but I'm not so optmistic, as I've seen reports from many people to whom the problem actually started after the upgrade. Does anyone know if the problem has already been officially reported to Samsung?
Nope. Not mine, the tab working flawlessly
Sent from my GT-P1000 using XDA App
i have the same annoying issue on my GT P1000 with gingerbread 2.3.3 Kernel: 2.6.35.7
i also have the vibration on Youtube app and any black background slightly.
Hi all,
This is my first post in these forums but I've been lurking for some time. I just want to bring attention to a few minor issues I'm having with CM7.
1) Sometimes randomly, the main dock disappears and only comes back after a reboot. Anyone else experience this?
2) On the stock HTC Sense, all running apps, or recently run apps, would show up when I brought down the notification bar. For instance, if I was playing Angry Birds and decided I wanted to send a text, I could press Home, write the text, then quickly drag down the top bar and click Angry Birds, which would be sitting next to the Text icon ready to go. On CM7, the apps in use do not appear there (only Lookout security shows up under "ongoing"), so I have to go back into the drawer or choose the icon from the home screen. I found that having all running/recently running apps was very convenient to have on the drop-down bar.
3) When I first started using the camera it was okay, and then at some point every picture I started taking with the stock CM7 camera becomes extremely grainy. When I take a picture with other apps this does not happen, so I know it is not the hardware, but the actual app causing the problem.
4) Camera app menu is oriented only for landscape. Any possibility of changing this? Also [side note], the stock Incredible S camera used the entire screen for the picture which I really enjoyed - I haven't been able to find an app that does this on CM7
5) Contrary to what I've read, I find the audio is actually less powerful than the stock HTC Sense for Inc. S. Anyone agree?
6) On the mail app (not Gmail), there is no way to add mail to spam
These are all extremely minor issues. Overall CM7 is great, quick and lightweight. Kudos to all the developers on this, I'm sure I speak for everyone when I say your work is beyond appreciated. You take the possibilities to enjoy these devices to the next level.
Hi key2gb, here's my experience with your above points:
1- This happened to me, but only once and it was fixed with a reboot. Although I thought it was because of ADWLauncher at first..
2- I hadn't realized this as I didn't get to play enough with Sense before moving on to CM7, but now that you mention it it does sound like a cool feature!
3- I have taken a few pictures with the CM7 camera and I haven't seen too much grain in the images. Maybe it depends on lighting and if the camera changes ISO's (I don't know if a phone camera can do this).
4- I am running CM7 Nightly#68 and the camera icons rotate when I place the phone in portrait "stance". Although I did overall prefer the Sense camera and have yet to find one in the market that comes close to it.
5- When you talk of audio, do you mean the front speaker, back speaker or headphone jack? I haven't used headphones with it yet, but as for the two speakers I have found the volume adequate for my needs as of now.
6- I only use Gmail
I have found that Nightly#68 "fixed" or added a lot of features from RC1 and since my switch to the Nightly build I feel that the phone is near perfection.
Thanks for the response. I am hesitant to switch to the Nightly build because I am not experienced enough with the tech-world yet, though I am getting more into it. It warns against non-experienced people using those so I don't mind waiting a few months for updates and more confirmation that the Nightly is completely stable. Then again, that's what backups are for, right?
For audio - I use my speaker phone for conference calls often and the speaker isn't nearly as loud as it was on the stock.
For the camera - it's a very strange problem on my phone because it only happens with the stock camera. You know how when you take a picture, as it's done processing the picture kind of sets into itself? Right after I take the picture, it sets and then it gets this weird staticy-grainy layer. It doesn't happen on other camera apps, just the stock. I use Streamzoo and that works fine. I really with I could get the Sense camera though it was really great.
I'm sorry I won't be able to furthur aid you as my knowledge in the field is limited. Hoping someone else comes along!
Although I was wary at first as well in trying the nightly builds. I gave it a try on #68 and it has been very stable (no problems at all).
For the audio, I just got an idea. Have you tried playing in the DSP Manager options? I don't know if there might be something there that might help a bit?
Sent from my Incredible S using xda premium
Good idea, I'll play around with the DSP Manager next time I'm on speaker.
Noob ? ... I have a blue cast over all photos and what seems to be a blue tint on other screens. I didn't have the problem with Gingerbread.
Flashed several different ROMs from Cyanogenmod to get to Android 4.2.2 with photosphere. Finally flashed ATT Captivate with Cyanogenmod 10.1-20130416-EXPERIMENTAL-captivateMTD-M3 (Android 4.2.2). Then deleted the gallery and added 4.2Camera_OG.zip.
Loaded Nova launcher thinking in might solve the problem.
Photosphere works but, still have blue photos.
No help on Cyanogenmod site, Google etc. Can someone please tell me (in relatively simple terms) how I can fix this problem. I'd really like to keep Photosphere and have the results be multicolor instead of blue.
You got photosphere to work on captivate? Strange since since photosphere is not supported on captivate due to lack of gyroscope?
Sent from my SGH-I897 using XDA
elbonnor said:
You got photosphere to work on captivate? Strange since since photosphere is not supported on captivate due to lack of gyroscope?
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I'm surprised that 4.2.2 runs at all on the i897. I found a mod that installs a new camera/gallery that includes photosphere. Only tested for a minute or two since any photos made would be useless with the blue cast. But ... I only chased the blue dot up and down and didn't test left or right.
Maybe photosphere isn't working after all, but I'd still like to know what's causing the blue photos. It's like someone place a blue gel over my lens. My son is getting the camera once it's working again. The longevity of him keeping track of a Nexus 4 would be measured in weeks. I'd rather lose the i897.
Just can't figure out why my photos are blue. I've tried everything except going back to Gingerbread.
Is it JUST the photos?
Nandroid, go back to stock see if it's still blue. If it is then replace the camera (very VERY easy, it's just connected with a ribbon cable). If not, try a different camera app.
x0ne215 said:
Is it JUST the photos?
Nandroid, go back to stock see if it's still blue. If it is then replace the camera (very VERY easy, it's just connected with a ribbon cable). If not, try a different camera app.
Click to expand...
Click to collapse
Not the camera. Went back to GB and the photos were color balanced correctly. With Cyanogenmod 4.2.2, there is a definite blue cast on the photos. Other screens don't look 100% correct as there appears to be some minor tinting of areas that should normally be white.
I read where I can use Jellybean 4.2 Camera APK on Gingerbread 2.3.6. Not sure if that will solve my problem.
Any other suggestions on camera app replacement would be helpful.
Read somewhere about photosphere not working properly with captivate. Maybe that is the case of your blues. As BB King sang, "Everyday, Everrryyy Daaay, I have the Blues"
Sent from the wholly ROMin' empire. SGH-I897 CM10.1
Unofficial, no warranty, express or implied. Not final, nothing to do with the CM people, not backed by them, not made by them, may cause corruption of innocent kittens if used irresponsibly. I am posting this only because the main CM sources are not perfect right now for building for Qualcomm devices just yet, and need some tweaks in new branches.
CM 10.2 Android 4.3 built for, and working on Pollux_Windy, once again thanks to Sony using such nice, open-source-friendly devices.
Working:
WiFi
Compass + sensors
Sound
Bluetooth
Front + Rear Camera
External SD (including ExFAT)
Not Working:
GPS
This is for the Pollux_Windy (SGP311) Wifi ONLY tablet. It should work on the SGP312 (32 GB wifi only) as well, but will NOT work on the Pollux (with LTE).
http://goo.im/devs/pulser/TabletZSGP311/CM10.2/cm-10.2-20130810-UNOFFICIAL-pollux_windy.zip
Tried to flash this but i'm getting an error about device build prop not matching requirements. I had a 312 rom on first, and flashed a 311 stock rom, but still get the error. My device is 311 by default.
Do i need to edit my build.prop? Even though my device shows as SGP311?
EDIT: Ah nevermind, i had the stock bootloader still installed. Doh!
If anyone needs Gapps I found them here:
http://forum.xda-developers.com/showthread.php?t=2378992
Sent from my SGP311 using xda app-developers app
Updated to 30 July build - includes the new Focal camera app. Yes, it has a few bugs with tablets and orientation. It's known.
Is root possible yet? I tried the supersu zip that was attached in op, but still needs the binary according to the supersu app. Do we need to adb push the binary?
Edit: Nevermind, just tried the latest supersu and works fine.
I can't get a restricted user to work for the life of me. All kinds of processes are force stopping and I couldn't pick trebuchet from the list on setup either, though I did manage to work around that with Apex eventually, though Apex kept crashing too.
I assume apps might have to support this (or at least launchers?) But core processes?
I did dirty flash so it's possible that has something to do with it.
Still digging around. I'll clean flash later to retry restricted users too.
C
cjdalessio said:
I can't get a restricted user to work for the life of me. All kinds of processes are force stopping and I couldn't pick trebuchet from the list on setup either, though I did manage to work around that with Apex eventually, though Apex kept crashing too.
I assume apps might have to support this (or at least launchers?) But core processes?
I did dirty flash so it's possible that has something to do with it.
Still digging around. I'll clean flash later to retry restricted users too.
C
Click to expand...
Click to collapse
Restricted profiles are not tested or a priority right now in CM I believe.
Got this working on my xtz SGP311 seems really quick so far recovery plays nice, only real issues I've encountered is that the screen flickers black every now and then using the aosp browser and MX player pro doesn't work as android 4.3 isn't supported yet which has nothing to do with the rom.
WiFi and GPS seem to working used google maps to find a location and navigate there had no issues with those yet.
Definitely something different over the Sony ui and less cluttered just need the sony remote
Gonna have a play with it and see how I get on with it lots of options to play with hehe
Sent from my SGP311 using XDA Premium HD app
andymg350 said:
Got this working on my xtz SGP311 seems really quick so far recovery plays nice, only real issues I've encountered is that the screen flickers black every now and then using the aosp browser and MX player pro doesn't work as android 4.3 isn't supported yet which has nothing to do with the rom.
WiFi and GPS seem to working used google maps to find a location and navigate there had no issues with those yet.
Definitely something different over the Sony ui and less cluttered just need the sony remote
Gonna have a play with it and see how I get on with it lots of options to play with hehe
Sent from my SGP311 using XDA Premium HD app
Click to expand...
Click to collapse
Check out the project by @Apache14 that brings infrared remote control support to non Sony ROMs!
Are you sure gps is working? I don't think it should be in this ROM...
I had a go at the open source IR by apache but had no luck getting it to work, but I'm not sure if I installed it right.
I'll have another play with GPS today as I've got more time and let you know I could have jumped the gun on this one lol. I quickly downloaded an app called GPS test and although it says the GPS is on it doesn't show anything else like coordinates or location I'll keep playing for now though.
Sent from my SGP311 using XDA Premium HD app
Updated 3rd August
Updated 7th August.
Thanks a lot for throwing this together... everything seems to be working great, I'm impressed by focal.
I'm still struggling with is the absence of tablet UI (trying to hit the home softkey in landscape is impossible, so I've been forced to full!screen, which is working well), but it's a small price to pay for the jump from Sony's 4.1.2 to a functional 4.3 Rom.
zylstrajs said:
Thanks a lot for throwing this together... everything seems to be working great, I'm impressed by focal.
I'm still struggling with is the absence of tablet UI (trying to hit the home softkey in landscape is impossible, so I've been forced to full!screen, which is working well), but it's a small price to pay for the jump from Sony's 4.1.2 to a functional 4.3 Rom.
Click to expand...
Click to collapse
Interesting. Out of interest, how do you use your tablet ? I'm just trying to work out if there is any link or difference - personally I thought the same, that tablet was good, until I used my Nexus 10... Then I was "sold" - tablet UI was sub-optimal. I tend to use the tablet with 2 hands - one holding it, another free across the top for use. I find keeping navigation to the centre more logical personally, and more ergonomic. It also keeps the notification tray at the top, consistent with the phone. At other times, I use the tablet as a "monitor" and type with a Bluetooth keyboard, where I do not interact with the touchscreen much (except at arm's length), and find phablet UI quite convenient. Moreso than I felt with tablet UI.
It's intriguing though. I am sure I can look at readding it some time, but I'm fairly busy so it will take a while. I noticed Sony seem to be moving to phablet UI for 4.2 as well though...
I hold mine on the sides and mostly interact with my thumbs, thus central on screen controls are hard to reach. But, to each his own. I also use Thumb Keyboard exclusively on my tablets, much more natural than trying to type with one hand holding with the other.
so yeah i finally got around to testing the GPS navigation and it just says "Searching for GPS" the whole time so confirmed its not working.
i also found a issue with the swipe to type on the AOSP keyboard as soon as i tried to use swiping it force closed the keyboard, not a big issue just thought id mention it.
i noticed you've done a couple of updates as well whats the best way to update the rom just flash as usual using the file in op?
andymg350 said:
so yeah i finally got around to testing the GPS navigation and it just says "Searching for GPS" the whole time so confirmed its not working.
i also found a issue with the swipe to type on the AOSP keyboard as soon as i tried to use swiping it force closed the keyboard, not a big issue just thought id mention it.
i noticed you've done a couple of updates as well whats the best way to update the rom just flash as usual using the file in op?
Click to expand...
Click to collapse
Just like with CM nightlies, just flash the latest update right over whatever you have.
In rare cases other changes will be needed, maintainers will usually let you know in these cases.
I'm investigating GPS on 10.1 on the windy - it's proving to be a bit of a headscratcher, although it has many of the hallmarks of the same problem we had with the modem on mint (Xperia T) months ago. Unfortunately, we can't use the same fix/workaround we used on mint.
pulser, may want to check the CM10.1 thread for my SMD debugging patch, might give some useful info - although what I need to do is get a build environment together for stock kernels so I can apply that patch to .370 for comparison.
i hate to sound like a noob but i am still learning lol is it safe to just flash the updates with cwm or is it best to do it with the flash tool?
it seems like gps has got a lot of people scratching their heads at the moment but im sure with so many looking into it there is sure to be a solution soon
Edit: its OK I went ahead and flashed the update using cwm and it worked, I'm to impatient to wait lol but at least I've learned something
Updated to 10th August build
Will you continue to tweak now that official nightlies are out?
Hey everyone,
So I've been trying to "modernize" my phone, since I'm under the impression that I can get another 2-3 years out of it. So far I have:
-Running 7.1.1 stock rooted w/Franco kernel
-Hacked to include Pixel launcher (works great)
-Hacked to include Assistant (works great)
-Hacked to run Daydream (works great(ish)) -These tutorials are all available online and are pretty simple if you kinda know what you're doing
I bought a Daydream headset and have been playing with the apps. Some seem to work fine, and some won't run, some won't install. This seems like pretty fresh territory, so I haven't found much help online.
I know our phone supposedly doesn't meet the intended hardware specs (thermal characteristics, and GPU speed?), but it sure seems capable enough to me.
-Home screen and remote - works no problem.
-Playstore - works no problem.
-Netflix VR - works no problem.
-Arts & Culture - works no problem.
-Asteroids - This is pretty awesome. It's a demo of an animated episode (not the old game). It has 3D sound, which I wasn't expecting since the Netflix VR app didn't have it.
-Youtube VR - won't install (sideload). A little research, and it sounds like this app won't run on our phone's architecture. As far as I know, I can't force it to run. I'm very interested in getting this to work though.
-NextVR - Launches to blank screen.
-Hello Mars - works no problem. Lacking content it seems.
-JauntVR - works no problem.
-Littlestar - opens to non-side-by-side screen.
-InceptionVR - opens to non-side-by-side screen.
-Etc.. haven't tried very many yet.
For some of these, I wonder... I have my phone "posing" as a Pixel XL. I wonder if it would make a difference if I changed it to Pixel regular instead.
Anyhow, there must be others out there who are interested in exploring Daydream on our Nexus 6. Please share your experiences/expertise or point to relevant threads I may have missed!
Unfortunately I am in the same situation as you are, but I am just as interested in getting it resolved. The Daydream UI and the apps that are working actually work very well. What I found is the apps that are opening single screen are doing so because of our device info. I can go into the build.prop and edit the ro.product.device to marlin instead of shamu the app will open in a side by side screen. The only problem is that my phone reboots after running for a few minutes (even if I am not in daydream). I emailed the app developer of "AFFECTED:The Manor" and he said they will adjust the app requirements in their next update, but we can't expect everyone to be so helpful. We need to come up with a way to edit the build.prop info without causing rebooting. Keep me posted and I will do the same ...
Very cool, glad I'm not alone here.
I did notice that Netflix seemed to have picked out that my device was a Shamu, but luckily at least that app doesn't care.
FYI it looks like a bunch more apps just got added to the in-Daydream app-store. Going to try a few of those, and also trying to get google photos working.
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
zelendel said:
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
Click to expand...
Click to collapse
Yes good point. I personally am prepared for the worst, but yeah, disclaimer to others...
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
needleyepoke said:
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
Click to expand...
Click to collapse
Get what to work?
stev067 said:
Get what to work?
Click to expand...
Click to collapse
The daydream app... Isn't that what this forum is about?
needleyepoke said:
The daydream app... Isn't that what this forum is about?
Click to expand...
Click to collapse
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
stev067 said:
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
Click to expand...
Click to collapse
I'll go back and check my steps.. Thanks
stev067 said:
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Click to expand...
Click to collapse
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
adbFreedom said:
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
Click to expand...
Click to collapse
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
stev067 said:
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
Click to expand...
Click to collapse
Yea, I had tried all combinations one at a time and all at once and my device would always reboot. I found during the trial and error that only the ro.product.device was what the app was reading, but could not stop the rebooting.