Hi all,
If this is in the wrong place, i apologise unreservedly. It's really a question about android generally, but it's a question which has arisen specifically due to the behaviour of many of the various android builds available for the HD2, so i figure this is a sensible enough place to put it.
Enough waffle; the question:
Given the screen freezing issues associated with the gsensor/autorotate (i know this is at least relatively widespread as it's mentioned in many of the rom threads, and at least one dedicated thread), is there a setting/widget/app that can be used to force-rotate the screen and lock it in that orientation, if auto-rotate is disabled? For example, if i know i'm about to launch my browser or texting app, i can flip to landscape.
Many thanks all!
_tangent said:
Hi all,
If this is in the wrong place, i apologise unreservedly. It's really a question about android generally, but it's a question which has arisen specifically due to the behaviour of many of the various android builds available for the HD2, so i figure this is a sensible enough place to put it.
Enough waffle; the question:
Given the screen freezing issues associated with the gsensor/autorotate (i know this is at least relatively widespread as it's mentioned in many of the rom threads, and at least one dedicated thread), is there a setting/widget/app that can be used to force-rotate the screen and lock it in that orientation, if auto-rotate is disabled? For example, if i know i'm about to launch my browser or texting app, i can flip to landscape.
Many thanks all!
Click to expand...
Click to collapse
1. That is a very good idea and might fight the freezes caused by autorotation.
2. I want this anyway, because I want to be able to force a specific orientation when lying in bed. With autorotation the screen usually rotates the wrong way...
So any help would be appreciated!
+1 on this ^
Sent from my HTC HD2 Using the XDA App on ANDROID 2.2
MAMeingast said:
1. That is a very good idea and might fight the freezes caused by autorotation.
2. I want this anyway, because I want to be able to force a specific orientation when lying in bed. With autorotation the screen usually rotates the wrong way...
So any help would be appreciated!
Click to expand...
Click to collapse
I have this problem also
I've tried googling for an app of this sort, but so far no joy. Might try and create one myself. Never written something for android before, but software development is my day job, so i'd be willing to give it a crack. Crazy-busy at the moment though, so not sure when i'd get time
how about assigning a longpress-homekey something like rotate by 90° each time it is longpressed?
something like longpress-endkey menu in windows mobile devices.
shouldn't be that much of a problem to write such a program with appinventor?
I have Switch Pro Widget (it's a customizable energy control widget). One of the shortcut buttons enables/disables auto-screen rotation, so that does the trick for me.
I'm not sure if it has something to do with SMOLED in general, or if it's particular to the Nexus S, but I'm noticing oddities with the screen. Can't be sure if it's software related, or if it's hardware related.
There are two things. One, it sometimes doesn't register presses, even when an icon is clearly pressed; the orange highlight that surrounds an icon is clearly seen but it doesn't launch the app. It requires a second touch. I'm guessing this is mostly software related, but either way, it's disappointing to see Android like this (or, if hardware related, sad to see SMOLED like this).
The 2nd thing is, the screen seems problematic for the complete opposite reason sometimes. Has anyone ever hovered their fingers over the screen without actually touching it? Sometimes it'll register presses this way. I'm guessing this is hardware related? Either way, I have no doubt this causes unintended screen presses, and might go a long way in explaining typos and frequent errors that occur when typing quickly where your fingers glaze over the screen (like I often see double letter hits, like tthis or thiss - very annoying).
Not sure what the deal is, whether it's software or hardware contributing to these two oddities/problems - or a combination of both. Either way, these two things can make the Google Android experience feel second rate.
Additionally, I think this goes a long way in explaining my frustrations with typing on Android. Missed space bar presses are particularly frequent, resulting in words likethis; while other times, double hits occur, per my example above (like tthis or thiss). Again, it detracts from the overall Android experience and can be frustrating when thumbing out long messages.
The first issue might be related to the Launcher you're using. Are you on stock launcher or did you install something else like ADW or Launcher Pro? If you're on a third party, try it back on stock, or dig into the settings for your 3rd party launcher and see if there are tweaks you can turn on/off that might impact it. I know ADW has a "keep in memory" toggle; stuff like that is what I'd play with.
The other problem is something I've seen several people mention in here. I'm not sure I notice it or not, BUT, I just read this interesting article yesterday, which suggests to me that the screen is ultra-sensitive to touch. The article authors are amazed that they can use the back of their fingernail, or even wear gloves and still register touch on the screen. Other phones aren't so sensitive.
It seems they did something to increase the capacitive touch sensitivity, and perhaps a bit too much. Hopefully it can be software fixed.
The NS is such a lovely device, but it's got it's fair share of quirks, both hardware and software that really mar the experience for many. I love the phone, but am still considering returning it when my 30 days is almost up.
distortedloop said:
The NS is such a lovely device, but it's got it's fair share of quirks, both hardware and software that really mar the experience for many. I love the phone, but am still considering returning it when my 30 days is almost up.
Click to expand...
Click to collapse
I agree.
As for the launcher, I am currently using ADW because there are a slew of glitches and issues with the stock launcher, including the unresponsive issue I wrote about in my OP. ADW Launcher is unquestionably more reliable, smoother, and stable.
It's unfortunate the experience with the Nexus S can be so polarizing: sometimes the screen is not responsive, and other times, too responsive.
And I have to reiterate, the experience typing on this phone (and on Android in general) remains a particular sore spot for me.
distortedloop said:
I'm not sure I notice it or not, BUT, I just read this interesting article yesterday, which suggests to me that the screen is ultra-sensitive to touch. The article authors are amazed that they can use the back of their fingernail, or even wear gloves and still register touch on the screen.
Click to expand...
Click to collapse
No kidding. I don't have to actually touch the screen at all. Just hovering the tip of the finger 0.5mm over the screen is enough. Which is not really a problem, because it's quite difficult to do that.
I have found the same issue with the screen, it is very sensitive to touch. As for the bad selection and typing errors, I think that is more more likely software related, try a different keyboard?
Sent from my Nexus S using XDA App
Corvidd said:
I have found the same issue with the screen, it is very sensitive to touch. As for the bad selection and typing errors, I think that is more more likely software related, try a different keyboard?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I'm currently trialing Swiftkey. It is impressive the few times it works to perfection, but this is usually a rare occurrence. More often than not, I'm still having to type out my words, however, perhaps it's still "learning" how I type. For now, I feel like the experience is actually slower than manually thumbing out messages because you're so busy concentrating on picking the correct predicted word. In some ways, it's counter intuitive to messaging quickly. I have until the end of the month before the trial expires, so we'll see if the experience is improved.
Prior to that, I was using either stock keyboard, or Smart Keyboard Pro. Both have their positive and negative issues, but those two offerings are as good as it can be on Android, it seems. Which is to say, it's disappointing. I have many typing woes. I have to say, the typing experience pales in comparison to typing on iPhone/iPod touch devices. I can type far more confidently and smoothly on an iPhone than I can with any Android device I've used so far. I'm hoping, one day, when Blindtype is implemented, this will change.
I didn't like swiftkey, and don't understand its popularity, having to check the scrolling bar for which word i wanted slowed me down. I agree that the typing accuracy on an iPhone is superior to android devices, there are many things I don't like about the iPhone keyboard but the accuracy is very good.
Have you tried Swype? I believe the beta is now open to all to try, google it, as its not in the market. Failing that, apps like Shapewriter (when it becomes available again) and SlideIT keyboard are other similar options. Or if you want to go all-out weird with text input, try 8pen.
i found the same bugs
and my guess it has to do with the Concave design, that throws off the screen calibration.
on the SGS, the touches are 110% accurate
you just hover your finger on top, and the work
Corvidd said:
I didn't like swiftkey, and don't understand its popularity, having to check the scrolling bar for which word i wanted slowed me down. I agree that the typing accuracy on an iPhone is superior to android devices, there are many things I don't like about the iPhone keyboard but the accuracy is very good.
Click to expand...
Click to collapse
Agreed. However, I'm trying my best to give Swiftkey ample opportunity to grow on me, and as I said, when it actually predicts your words accurately, it's quite intuitive, but this happens rarely. Most of the time it guesses incorrectly and you end up thumbing in almost all the letters to a word anyway. Swiftkey slows me down too and I, ironically, end up taking longer to type out messages. Like you, I'm too busy making sure it's predicting correctly the next words I want to say. In many ways, it's counter-intuitive.
And it's a shame Google didn't set itself apart from Apple's keyboard. They could/should have included custom auto-corrections, etc.
Have you tried Swype? I believe the beta is now open to all to try, google it, as its not in the market. Failing that, apps like Shapewriter (when it becomes available again) and SlideIT keyboard are other similar options. Or if you want to go all-out weird with text input, try 8pen
Click to expand...
Click to collapse
Thanks for the suggestions. Yes, I forgot to mention I have the Swype Beta. Swype is quite fun and often impressive, but like Swiftkey, I find it cumbersome when I'm trying to type 'personal' words like unique names of places, or uncommon lingo and words, etc. Plus, when you start getting into long words, Swype becomes difficult to track. Perhaps I just need more practice, but ultimately found it slower than thumbing it out. I have tried a few other options, like the one where the keys change sizes depending on predictions, and even 8pen (novel, but no thanks), but nothing seems capable of accurately mimicking the iPhone/iPod Touch typing experience. Anyone who has typed extensively on both platforms will know the difference.
I would just like to be able to thumb out messages minus the odd errors and mis-presses/unregistered presses, or the overly sensitive presses. Smart Keyboard Pro remains the best choice, in my opinion, but even that has hiccups and my aforementioned problems. It's probably a combination of software and hardware that is contributing to my typing woes.
Blindtype, please hurry.
I don't have problems with it not registering presses, but it certainly is sensitive. Depending on conditions, you can register a press by hovering your finger 1-2mm off the screen surface. This has rarely bothered me, but if you keep your fingers very close in while you're typing, yeah, I can see it being really problematic.
EDIT: Actually, Android Central posted a short article and video just this morning about how you can use your Nexus S with certain types of gloves on in the winter cold because of this.
zorak950 said:
I don't have problems with it not registering presses, but it certainly is sensitive. Depending on conditions, you can register a press by hovering your finger 1-2mm off the screen surface. This has rarely bothered me, but if you keep your fingers very close in while you're typing, yeah, I can see it being really problematic.
EDIT: Actually, Android Central posted a short article and video just this morning about how you can use your Nexus S with certain types of gloves on in the winter cold because of this.
Click to expand...
Click to collapse
Right, you are. I mention about the hovering finger thing in the OP.
AllGamer said:
i found the same bugs
and my guess it has to do with the Concave design, that throws off the screen calibration.
Click to expand...
Click to collapse
But my understanding is that the actual touch screen itself isn't curved...?
onthecouchagain said:
But my understanding is that the actual touch screen itself isn't curved...?
Click to expand...
Click to collapse
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
zorak950 said:
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
Click to expand...
Click to collapse
Yes, that makes sense.
Not sure if I'm liking what I'm hearing. If the screen is indeed too sensitive and is the cause of my typing woes, I don't suppose there's a way to dial it down via software, is there?
onthecouchagain said:
If the screen is indeed too sensitive and is the cause of my typing woes, I don't suppose there's a way to dial it down via software, is there?
Click to expand...
Click to collapse
I don't know enough about how the technology works to answer that authoritatively. I'm curious too, though.
onthecouchagain said:
The 2nd thing is, the screen seems problematic for the complete opposite reason sometimes. Has anyone ever hovered their fingers over the screen without actually touching it? Sometimes it'll register presses this way. I'm guessing this is hardware related?
Click to expand...
Click to collapse
I've had this happen to me a couple times. I could see how its annoying, but I'm coming from a nexus 1 where you could mash the screen at times and nothing would happen so its nice to have a sensitive screen.
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
distortedloop said:
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
Click to expand...
Click to collapse
I agree. Voice input is very good with the S, much better than it was with the N1.
Smart keyboard pro is also a good one.
distortedloop said:
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
Click to expand...
Click to collapse
Yes, I've attempted to use Voice Actions, especially while driving. Usually it gets what I want to say correct, but unfortunately, it doesn't always get the person I'm trying to send it to correct. In fact, it never does. Same is true for when I'm not driving. So I end up having to cancel the command and type it out anyway.
I bought Better Keyboard long ago. It was one of the first third party keyboards I tried. I found the experience atrocious (at the time, it lacked true multitouch. If you think stock keyboard missed letters... you should try BK!). My understanding is that multitouch is implemented now, so perhaps I'll give it another try.
Edit: Also, Smart Keyboard Pro offers touch points and calibration to help you see where you mistype and to calibrate it to your typing style. These features help, but there's no mistaking that the phone (softward or hardware?) often misfires or misses presses altogether. Problems that appear like tthis or thiss or whenever it misses a space bar press (despite the space bar clearly being highlighted on the keyboard) resulting in words likethis are far too frequent and have nothing to do with pressing accuracy.
zorak950 said:
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
Click to expand...
Click to collapse
exactly... too much empty space in between, that's why the areas around the edge at the bottom are harder to register
Hi, curious question.
I'm wondering why the N7 doesn't allow you to slow scroll/pan down at single pixel steps. Always seems to be in 2-3 pixel jumps. I got a bad habit of scrolling web pages while reading from iOS but on my N7 I get these kinda anoying start/stop jerks.
Is this related to the virtual pixel resolution being lower than the actual screen resolution? And would changing it allow one to match the virtual pixels to the screen pixels and get smoother slow speed panning?
Anyone know if some custom ROMs optimize for this?
BR
POTS101 said:
Hi, curious question.
I'm wondering why the N7 doesn't allow you to slow scroll/pan down at single pixel steps. Always seems to be in 2-3 pixel jumps. I got a bad habit of scrolling web pages while reading from iOS but on my N7 I get these kinda anoying start/stop jerks.
Is this related to the virtual pixel resolution being lower than the actual screen resolution? And would changing it allow one to match the virtual pixels to the screen pixels and get smoother slow speed panning?
Anyone know if some custom ROMs optimize for this?
BR
Click to expand...
Click to collapse
I have been struggling with this issue for days. Looked into kernel code hoping to find anything related to scrolling or touchscreen but nowhere to find such a thing. It has nothing to do with virtual pixel resolution. If you swipe your finger at a degree of between 45-90 (accapted as scroll up by the system), Y coordinates change by 3 pixels where as X coordinates can change by 1.. Therefore its not a limitation, it is kind of scroll sensitivity which is 3px.. I've seen other devices can scroll by 1 pixel.
I believe google has set this value to 3 because of rendering issues, since its gonna render the screen 3 times more if it is set to 1. Maybe it is the optimum sensitivity. Lower than 3 pixels may disrupt buttery smoothness but its just a guess..
I hope one dev can lead us the right piece of code where it is set to 3 and we can change it ourselves to test the best..
You guys can try the problem yourself actually by installing the "Multi-touch accuracy check" app from market, which shows the exact pixel of the touch..
Interesting not to see anyone interested in such an improvement
UP!
Did anyone see this described in another thread? Perhaps the description is too obscure.
POTS101 said:
Did anyone see this described in another thread? Perhaps the description is too obscure.
Click to expand...
Click to collapse
It's been also discussed here..
http://forum.xda-developers.com/showthread.php?t=1932407
Any news on this?
As far as I can see, this is only related to touch screen; if you use a usb mouse, you can actually see the scroll by one pixel at time, and there is no graphical issues. With mouse all seems smoother...
At this point, I think It's an hardware issue of the touch screen, as the system can easly support 1px scrolling
I have the issue as well. Does this affect all Nexus 7? I am surprised so few people are discussing this issue.
Hi
I have a nook simple touch - 1.2.1 firmware not rooted yet, I only want to use it as an e-reader but the ghosting is awful compared to my wifes kindle of the same generation (non touch).
I've been trying to look around and find out what I can do, is there a way to force it to refresh every page, some searching seems to suggest the issue was better on older firmwares, why B&N didnt include an option like amazon to force refesh every page who knows (that's not enabled on my wifes kindle) - the Kindle is just much easier to read in direct bright sunlight but I'm sure theres some tweaking that can be done to improve it
I have to say I am surprised by your description of your NST. I've been paying close attention to mine today while reading and I may be losing my vision but I can't see the ghosting you are describing. I've always felt the native Reader and its default settings worked really well. In some other apps there may be issues with ghosting, but not in the reader.
I'm running FW 1.21 also and while I have rooted and altered my device a lot, to my knowledge I haven't done anything to the functioning of the Reader app. Are you sure you don't have some kind of hardware issue?
nmyshkin said:
I have to say I am surprised by your description of your NST. I've been paying close attention to mine today while reading and I may be losing my vision but I can't see the ghosting you are describing. I've always felt the native Reader and its default settings worked really well. In some other apps there may be issues with ghosting, but not in the reader.
I'm running FW 1.21 also and while I have rooted and altered my device a lot, to my knowledge I haven't done anything to the functioning of the Reader app. Are you sure you don't have some kind of hardware issue?
Click to expand...
Click to collapse
It could be a hardware issue but it's well out of warranty, I do notice the ghosting on the kindle too so maybe im just susceptable to spotting it and having it irritate me, just wondered if there are any tweaks to control thow often it refreshes as its ok once it refreshes the screen
damianiw said:
It could be a hardware issue but it's well out of warranty, I do notice the ghosting on the kindle too so maybe im just susceptable to spotting it and having it irritate me, just wondered if there are any tweaks to control thow often it refreshes as its ok once it refreshes the screen
Click to expand...
Click to collapse
OK, so look here at what Renate suggests.
nmyshkin said:
OK, so look here at what Renate suggests.
Click to expand...
Click to collapse
Seemed to be very complex, so I went for root and under there is the option for how many pages before full refresh
also installed cool reader for good measure and very happy - problem solved
damianiw said:
Seemed to be very complex, so I went for root and under there is the option for how many pages before full refresh
also installed cool reader for good measure and very happy - problem solved
Click to expand...
Click to collapse
Excellent! Your rooting method must be different from mine but now we're both happy
Good job, @nmyshkin!
Thanks everyone, my main concern was rooting would stop it behaving like an e reader but relaunch I a great launcher and the default options for home and library mean I have best of both and importantly control over the refresh as my nook does appear to ghost far more than a friends on comparison, for the £29 paid over a year ago the nook is awesome
Comparing my nook to a friends the contrast looks really different so maybe this unit wasnt calibrated right - i'm now looking for a contrast adjuster to see if that solves me needing to fully refresh the screen so much as that will be using more battery
Can somebody pleasy help me out, I have just recieved my YP2 and I would really like to find a way to control the frequency of the flashing/full screen refresh on the e-ink display as you can do on most kindles. I would like to decrease this/make it as un-frequent as possible. I do understand it will cause ghosting issues.
All help will bbe greately appreciated
Help needed
there must be a simple way to disable the 'full screen refreash' on the EPD? I suffer from a very peculiar form of motion sickness when e-ink screens flash to black and thats why i couldnt use the early kindles.
If anybody can give me any guidance/advice in this regard it would be very helpfull.
Ive done al imited amount of playing about with linux based source codes and was able to fully disable the full screen refresh on my kindle when used as a vnc monitor. Can anybody tell me if this would be dont by playing around with the kernel source code for the yotaphone, or if there is an app that can do this function?
Regards
Things I can answer:
a - no such app exists yet (and given dev interest in this phone is minimal, by all appearances, it doesn't seem likely to be created. The phone is getting close to (if not already there) being low-spec comparatively, so further adoption of this phone by the masses seems unlikely. To me, that's a shame (I use a yp2 as a daily driver, but I keep other phones around as needed (for lte speed for video, proc intensive gaming, etc)))
b - while a sdk for the yp2 exists, it doesn't appear to address low-level epd function (which your request would seem to be). The kernel sources, at least of current date, have yet to be released; whether they ever will be is an open question. It's already difficult getting a large-scale manufacturer to release source, getting a small-scale shop like yota would be even harder for multiple reasons.
I'm sorry the epd in its current state isn't working for you; that's a shame.
(I was super excited by the project ara phone, since it seemed likely that someone would release an epd main screen at some point, so I could switch out between screens as the whim took me; the current plan for ara has dashed my hopes, c'est la vie. I still hold out hope for future epd-screened phones.)
staphoent said:
Can somebody pleasy help me out, I have just recieved my YP2 and I would really like to find a way to control the frequency of the flashing/full screen refresh on the e-ink display as you can do on most kindles. I would like to decrease this/make it as un-frequent as possible. I do understand it will cause ghosting issues.
All help will bbe greately appreciated
Click to expand...
Click to collapse
There's no setting for modifying the full screen flash frequency. However, the older Kitkat flashed only when the content of the entire screen changed. The periodical screen flashing was introduced in the Lollipop update. So if you think that would be of any help, you could try downgrading to some older Kitkat.
a- that is a shame as i love the non reflective aspect of the e-ink screen, and it functions quite well for browsing/reading (apart form the refresh for me)
b- where can i find the sdk for this phone?
What is the 'ara phone' you are reffering to?
shogzilla said:
Things I can answer:
a - no such app exists yet (and given dev interest in this phone is minimal, by all appearances, it doesn't seem likely to be created. The phone is getting close to (if not already there) being low-spec comparatively, so further adoption of this phone by the masses seems unlikely. To me, that's a shame (I use a yp2 as a daily driver, but I keep other phones around as needed (for lte speed for video, proc intensive gaming, etc)))
b - while a sdk for the yp2 exists, it doesn't appear to address low-level epd function (which your request would seem to be). The kernel sources, at least of current date, have yet to be released; whether they ever will be is an open question. It's already difficult getting a large-scale manufacturer to release source, getting a small-scale shop like yota would be even harder for multiple reasons.
I'm sorry the epd in its current state isn't working for you; that's a shame.
(I was super excited by the project ara phone, since it seemed likely that someone would release an epd main screen at some point, so I could switch out between screens as the whim took me; the current plan for ara has dashed my hopes, c'est la vie. I still hold out hope for future epd-screened phones.)
Click to expand...
Click to collapse
Thanks for the reply, was their a noticable difference between the frequency of the flash on kitkat and lollipop?
In order to change back to kitkat will it require me to root my YP2?
Regards
Jeopardy said:
There's no setting for modifying the full screen flash frequency. However, the older Kitkat flashed only when the content of the entire screen changed. The periodical screen flashing was introduced in the Lollipop update. So if you think that would be of any help, you could try downgrading to some older Kitkat.
Click to expand...
Click to collapse
staphoent said:
a- that is a shame as i love the non reflective aspect of the e-ink screen, and it functions quite well for browsing/reading (apart form the refresh for me)
b- where can i find the sdk for this phone?
What is the 'ara phone' you are reffering to?
Click to expand...
Click to collapse
sdk: on yota's website, developer section (search term: 'yotaphone 2 sdk')
ara: google project, currently specced for release q4 this year, iirc. (search term: 'project ara')
EPD flashing frequency
Hi, I have a similar motion sickness problem. I just got a YP2 and was wondering if you ever figured out how to change the refresh/flashing of the EPD?
Alexey Zakharchenko might help he has produced several apps on the play store
yotaclock+ has a epd screen refresh
contact via play store or [email protected]
hope this helps