yashsingh1/xdaforums huggingface dataset:
[YotaPhone] Kytrix:
Yes my screen looks normal. Seems a little darker, but my wallpaper is dark (in mirror mode)

I also add a config file for an app called geotracker. I put the same config as google maps. The result is perfect (before I was unable to see littles roads)

Since the update It seems for me :

- When I flip from mirror EPD to oled I have to close mirror mode first, because the oled screen doesn't respond, stay off.

- In mirror mode with TuneIn Radio there is some micro lag . If close the mirror mode shutter lag is gone..
[YotaPhone] skha:
After the update to Android 6 the backdisplay seems very brigth. The result is a lower ghosting but its hard to read, especially at WhatsApp. WhatsApp now has the standard SMS Keys. The flipping has a bug, they backdisplay is very lagy especially the pin context. The key-icon overlaps the mirror icon. And they killed the mobile internet icon. What the hell is that?^^
[YotaPhone] look-aa:
Yes, my phone now shows the Russian baseband (S01_003_4240RU1_M05) after the OTA to MM, right before in LL I had just the EU radio flashed: I put that one after coming back from a trip to Italy, where I would get mobile network coverage only for 20% of the time, and no data whatsoever when I had some mobile network, even though data in roaming was allowed. {And yes, originally my phone is a Chinese YD206 from tinydeal}

Then, I decided to "come back here" and get better information (I have had an account since when xdadev was a meaningful name, I mean, when the actual O₂ xda’s were around, and had one :D — I think deactivated because of no use, but here I am again)

By the way, the email I sent was then forwarded to the Tech department at yotadevices, and got the reply to wipe the cache (done – but hasn’t sorted out anything), and if the problems persist to reset to factory standards: I am working now, later I’ll do that and report here – maybe it can help others.

For the booting up problem, at least for those who have an excessive battery drain that can render the charging session absolutely endless (yesterday from 11am to 8:35pm, with no apps running, and no usage of the phone), I discovered that the phone can be charged in bootloader too, it gets warm but doesn’t overheat, and it seems faster.

UPDATE: I’ve just wiped the phone and it now works much, much better. Normal temperature, normal battery drain..
[YotaPhone] xNiux:
Since the update to MM, the sms button on EPD does'nt open the message window. Juste vibration, then nothing ... And the message counter is currently blocked to "1" ....

Is it a known problem ?
[YotaPhone] alienBaboso:
I have noticed that sometimes I would get one keyboard, and other times I would get another keyboard in the EPD while using WhatsApp. This is what I have found.

1. If you are on the OLED screen, inside WhatsApp, and click the mirror icon in the bottom right corner, Whatsapp on the back screen will have the basic keyboard (in my case, only spanish and chinese).

2. If you are on the YotaHub EPD screen with a notification widget, get a WhatsApp notification, and tap on it, WhatsApp will open and you will have the basic keyboard.

3. However, if you are on the YotaHub EPD screen, and start Yotamirror tapping on the bottom right corner, you can access WhatsApp, and you will have your current keyboard in the OLED (in my case, google keyboard with several languages)

It looks like a bug, but as I prefer the 3rd option I will mostly exploiting that bug to access WhatsApp.

Regarding the bright EPD display, I think there is a way to change the settings by adding a .cfg file on /Android/epd_optimizer and restarting the phone. But I still don't know how to achieve the rendering effect I had on whatsapp in Lollypop. Some user has tried the same settings as google maps, so I'm going to test it.

Edit: It works!! Create a file named com.whatsapp.cfg with the following content, and put it into epd_optimizer folder:
[YotaPhone] JavaDroid_:
I do not know if it's just me, but after the update the ink screen of my yota is practically unusable from so much ghost image, a total sucks. !! Is there a solution to this?

I already think about going back to the lollipop
[YotaPhone] i8890321:
Do i need a reboot to have that take an effect after creating the com.whatsapp.cfg?
[YotaPhone] skulpturfungus:
Does rooting work the same way with 6.0.1? When I'm doing the whole fastboot oem unlock thing, it does say that the device is unlocked, but the phone itself does not boot into the bootloader afterwards. I have to manually reboot, but I can't seem to be able to apply TWRP that way.
[YotaPhone] queser.info:
In conclusion if you have custom recovery with TWRP and root and try to update with OTA you will have a error, the best way to update to android 6.0 is to download the torrent and instal-it from TWRP menu.
[YotaPhone] veggiedelicious:
Hello people, I am a proud owner of a YotaPhone 2 bought 5 days ago with Android Lollipop :) I bought my YotaPhone on a european physical shop (not internet shop) and it came already with Lollipop last version. I have a 2 year warranty for my Yota . How can I update to Android 6 Marsmellow ? Does it comes automatically to my YotaPhone the update ?
[YotaPhone] shokmah:
finally updated my YD201 to Marshmallow exactly 1 week Ago (TWRP and adb Sideload)

Rooted through latest Systemless superSU.

Installed Magisk latest (does'nt install modules)

Installed Xposed

Downclocked CPU to 1.5 Ghz

Activated Marshmallow Split Screen

Battery Life is better than Lollipop but not perfect, standby mode still consume far too much (I can only compare with Moto G Lte).
[YotaPhone] skulpturfungus:
Is it just me or is ghosting much more of an issue with the EPD on Marshmallow?
[YotaPhone] MrPuddington:
I think there are different display hardware detail around. On mine, (YD206), the ghosting was very strong on the RU Android 4.4.3, but that was the most stable software version for me. Android 6.0 has much less ghosting, and a few other advantages, but it seems not quite as stable.
[YotaPhone] look-aa:
Hi, so far only the Russian firmware is updated On The Air (OTA). I read somewhere (possibly on the first post of this thread) that Yotadevices said that eventually the update to Android 6 will be rolled out also for the EU firmware. So you just have to wait :)

EDIT: Yes, it was the opening post:
[YotaPhone] alokrk:
Is anyone having issues with NFC after the upgrade? My NFC stopped working. The screen stays stuck when I toggle the NFC button.

Aside, any clues on how to change the default language on YotaSports to English?
[YotaPhone] ~El Julio~:
There are two issues I know about regarding NFC on YP2 :

1) NFC toggle stays stuck to off, impossible to enabbe it. Happens on both YD201 & YD206 reflashed.

2) YD206 (reflashed but with CN radio, haven't tested with RU radio) can't use Android beam, make a payment nor read/write a tag. In short NFC doesn't work at all - except it detects​ other NFC devices/tags.

Your case seems to be related to the first which is often fixed with a reboot or two (talking about weird..)

As for the second, the hybrid radio does fix the NFC altogether so it fully works. ;)
[YotaPhone] GoJo ^^:
Anybody please? :)
[YotaPhone] yb45324:
Has anyone successfully updated from 6.0.1 beta to RU1.1.147? I tried with sideload the zip but got error 7. Here are my phone's status

Model: YD206

Baseband: CN1_M05

OS Build: MMB29M.6.0.1-RU1.1.31

Rooted: YES.

thanks.
[YotaPhone] ~El Julio~:
The FOTA did work for me from 1.1.43 to 1.1.47, maybe you want to give that one a try. It worked for others too.
[YotaPhone] cvzalez:
I think your problem is relative with unlocked bootloader, Ggoogle Wallet won't work with unlocked boot-loader phones, they do that because of security issues.
[YotaPhone] ~El Julio~:
I don't have any safety net pass problem at all.

I'm precisely saying that it works on YP2 with the bootloader locked or unlocked.

Safety net checks for unlocked bootloader on Nexus devices & others, that we do know for a fact. But it doesn't on ours. :)
[YotaPhone] yb45324:
thanks. is your phone rooted? I tried the FOTA but it failed too. Mine was rooted. May I need to unroot?
[YotaPhone] ~El Julio~:
It was at the moment I updated, yes, systemlessly. But the update did obviously break it by flashing the new boot.img so I simply flashed SuperSU right after flashing the update and only then I rebooted.

That should not be an issue with the FOTA, but in general, better have a fully unmodified boot/system image before updating.

It's weird the FOTA failed. From which region/version were you updating ?
[YotaPhone] kbal:
Exactly the same situation in my case (206->201 RU).

I unlocked LTE, flashed hybrid radio and after update to Android 6 phone was warm and battery was draining like crazy (3h remaining at 80%). After Factory Reset from Android, battery usage is normal.

And unlocked LTE band(s) work 100% OK.
[YotaPhone] LadTy:
Hi,

Ever since my upgrade to Android 6, I am desperately searching for a way to have some clock on the EPD that do not fall behind and update every minute. I tried disabling optimizations for qualcom.time process as well as clock. When that was not enough, I tried disabling optimization for pretty much every reasonable 'yota' app, after that even tried fully disabling Doze (using https://play.google.com/store/apps/details?id=de.andip71.boeffla_doze_control ) which seemed to work for a while and then it didnt (?).

I tested multiple widgets for the EPD, even https://play.google.com/store/apps/details?id=com.zakharchenko.yotabasewidgetsfull (which is supposed to be updated for Android 6), but even when set not to be optimized in my baterry settings, it still does not update as it should.

Did someone manage to run clock on the EPD 100% reliably on Android 6?

Edit: With the default clocks, disabled optimizations for qualcomm.timeservice and clock app, I get the best results, but even then I caught the widget to be up to 3-4 minutes late at one point, so I never know if I can really realy on it :|
[YotaPhone] fsjon:
Update after some testing over the weekend:

Flashed the newly repackaged hybrid radio with YotaFlasher, it now say S01_003_3034_CN1_M05

Did not notice any difference with signal strength from before, where I flashed with just the radio file from the Hybrid radio .zip for TWRP using YotaFlasher.

With regards to Wifi stuck at scanning, it appears to be a OS bug that is still not fixed with android N:

https://code.google.com/p/android/issues/detail?id=196120

The only way to have Supplicant State: Complete is to be connected to a wifi network prior to turning off your wifi manually. Otherwise, it will stuck at scanning until you are connected to a known network and turn off wifi again. I tried to automate this process with the help of IFTTT by turning off wifi outside of an area, but it runs too slow even with a small location area to get wifi to turn off before it lost connection. Battery life seems to be the same with wifi turned on full time vs turned off with IFTTT. However, if you can get the Supplicant State complete, I do notice a slight battery saving with wifi turned off.

Conclusion, Supplicant State: Scanning appears to be a wifi bug with the OS as a whole and not because of different radio/modem we are using.
[YotaPhone] GetSAS:
Ok, this is interesting to know.

i have the same situation here.

When i turn off wifi when it has saved a known wifi, supplicant state says: Disconnected;

otherwise if i remove known wifi networks and turn it off, it says: Scanning.

Also i didn't notice a big difference in the battery usage when i turn off the wifi.

(with a full battery and very less usage, i get about 4-5 days, a good value though, but it should be more with wifi turned off).

EDIT:

Also tested it on a different phone (moto G3). I can confirm the same behaviour. It seems to be an OS problem.
[YotaPhone] keeeper:
Nice to read about your adventures with Android M, sadly I can't do the update - whatever I try it always ends up with a bootloop (Powered by Android screen):

RU1.134 + OTA = bootloop

RU1.134 + Stock recovery + sideload MM134-147 = bootloop

RU1.134 + TWRP + MM147 = bootloop

Tried different versions of adb, twrp and stock recovery. Perhaps it's because I have my EPD disconnected and use Y201 as a regular phone. Any ideas?
[YotaPhone] fsjon:
Not sure how you disconnected your EPD, I assumed you mean manually? Why not reconnect your EPD and see if that makes a difference?

But if you are not using the EPD, I don't really see much difference in performance wise with the update other than security update. And to be honest, I like the swipe to launch Google Assist/now than the long hold home button in MM.
[YotaPhone] cyanID_:
Structural deficites and no hash sums/integrity checks

Android 6.1 works with adb sideload installation from yotaphone2_5.0.0-RU1.1.134

[strangely called yotaphone2-user-full-RU1.1.47.zip]

Which twrp version do you use? That is one https://xdaforums.com/yotaphone-one/help/guide-everything-to-yotaphone2-t3547194 ?

From yotaphone2_5.0.0-RU1.1.134 on, twrp-v5.img was removed and could somehow not be flashed on.

No error code/reason is given which is quite weird.

With adb backups take much longer and stock recovery can not simple install .zips.

Or am I wrong about .zip files?

The guide is nicely summing up things, but should be shorter/more structured with clearer language.
[YotaPhone] jeanchri:
I find the guide quite precise and really nicely done.

And yes I've flashed the TWRP with this guide on Lollipop without hassle.

Maybe the best solution is to do step by step again with the guide and note where and when you got problems?

Good luck-
[YotaPhone] cyanID_:
Ups, yeah I meant in the link, not this one, sorry.

Alright, maybe I forgot to boot into recovery directly.
[YotaPhone] keeeper:
Yes, manually. Sadly I broke one cable so EPD can not be connected again. However I don't think that's the issue here - I successfully installed KitKat or Lollipop without the need for second screen. What makes me wonder is the different structure of the KK/LL and MM zips, as I prefer to install images through fastboot:

fastboot flash aboot firmware/emmc_appsboot.mbn

fastboot flash boot firmware/boot.img

fastboot flash cache firmware/cache.img

fastboot flash modem firmware/radio/NON-HLOS.bin

fastboot flash sbl1 firmware/radio/sbl1.mbn

fastboot flash rpm firmware/radio/rpm.mbn

fastboot flash tz firmware/radio/tz.mbn

fastboot flash userdata firmware/userdata.img

fastboot flash -S 512M system firmware/system.img

These files are simply not present in the yotaphone2-user-full-RU1.1.47.zip or any other zip I found.

PS. I tried every version of twrp/stockrec. I could find here.

PS2. Why to install? Simple - curiosity and hope for at least some small improvement in the battery life.
[YotaPhone] kbal:
Welp, I was wrong. Still gets warm as hell and battery lasts only 2 hours just browsing :(
[YotaPhone] Estrada88:
I updated last week from kitkat to marshmallow (y206), I still have original CN radio (I haven't time to change recovery) and everithing works apparently well...but CPU management.

Two days ago I was using a scores app on EPD and it drained battery like hell. It is a simple app, even using 3G and updating permanently it was weird. So I downloaded CPU Z to check de CPU with simple tasks....and I realized that with all simple tasks (updating apps, using chrome, using twitter...using one single app) CPU was working over 80% all the time, 100% almost the full time. Even doing nothing but the screen on, no apps opened, there are 2 cores working at 40-50%. So, even using only the EPD, battery life is really bad because of this. It's normal? any idea how to fix this?
[YotaPhone] polu16:
Clean Install - Full Fota? OR wait for FTP

Hi,

I would like to make a clean Install without old files from the previous ROM. Should I wait until the release on the FTP Server or is the Full Fota exactly the same?

Thank you very much!
[YotaPhone] i8890321:
Want to ask does anyone tried the slimport function after the update

I lost my slimport function after the update

I want to report the bug ,but how ?
[YotaPhone] cyanID_:
Removing google search bar does not work, purging apps

After rooting and exchanging baseband, I wanted to purge google apps I do not use.

$ adb devices

$ adb shell 'pm list packages -e' &> enabled_apps.txt

$ sed -i.bak s/package:/pm disable /g enabled_apps.txt

$ cat enabled_apps.txt | grep 'google' &> ToDisable.txt

gave me [first entry different, because that breaks phone operation completely, you can not accept debugging etc]

pm enable com.google.android.googlequicksearchbox

pm disable com.google.android.onetimeinitializer

pm disable com.google.android.apps.messaging

pm disable com.google.android.configupdater

pm disable com.google.android.marvin.talkback

pm disable com.google.android.launcher

pm disable com.google.android.deskclock

pm disable com.google.android.setupwizard

pm disable com.google.android.webview

pm disable com.google.android.syncadapters.contacts

pm disable com.google.android.gsf

pm disable com.google.android.tag

pm disable com.google.android.tts

pm disable com.google.android.partnersetup

pm disable com.google.android.feedback

pm disable com.google.android.calendar

pm disable com.google.android.gsf.login

pm disable com.google.android.backuptransport

Though I can not remove com.google.android.googlequicksearchbox to remove the quicksearchbox.

It is also not removable via hand. Any recommendation from your side ?

What experience did you have on purging preinstalled apps ?

---------- Post added at 06:46 PM ---------- Previous post was at 06:33 PM ----------

In recovery mode one can not install apps (even if rooted).

You might want to restart instantly after rooting only flashing the rooting zip.

You can see that your phone is not rooted, if

busybox / busybox --version / busybox --help returns nothing if not rooted and you get "/sbin/sh: pm: not found".

This also solves https://android.stackexchange.com/questions/162544/sbin-sh-pm-not-found I guess though I am unsure about the internal function of play store/app installation.

In data mode/usual startup I could not install apps on phone unless the phone was rooted. :confused:

$ adb install package.apk

fails without root.

Any idea why?

The Im not a robot chapta is annoyingly slow.

---------- Post added at 06:59 PM ---------- Previous post was at 06:46 PM ----------

The update is a patch that replaces the files, if needed. (+integrity checkups, but sadly not for the download file)

As for the rest, in my opinion it makes no difference, just needs a little more time. You shall do backups anyway.

I guess they need around 1-2 months, therefore you might want to check reviews.

You can download russian version 134 flashing with fastboot and using the patch with adb sideload (there is a torrent file somewhere as well) and backing up your /data and apps via other tools.

Not sure, if twrp can backup user apps as well, but there are plenty of tools for this.

If you are unsure, there is still adb though the data rate is slow (at least it was for my s2).
[YotaPhone] shokmah:
almost same for me downclocked cpu up to 1,5GHz and set governor to conservative.

but I still lose 7-8% of battery when phone is in standby.
[YotaPhone] look-aa:
What is it, sorry? So I can test it too.
[YotaPhone] casaprocida:
http://www.slimportconnect.com/
[YotaPhone] MrPuddington:
YotaEnergy

I have to say I like the new Android 6.0. It has more features for the second screen, and generally works very well.

But I do struggle with YotaEnergy. Whenever I activate it, I lose network connectivity, both on WiFi and on mobile. This is related to the "Limit processor frequency" setting - if I turn that off, internet is fine.

Any idea what could be going on? In my experience, limiting the CPU frequency is a great way of extending battery life, so it would be nice to get it to work.
[YotaPhone] ygrigory:
I have a slimport to vga and it never works.

Enviado desde mi Redmi Note 3 mediante Tapatalk
[YotaPhone] i8890321:
it works fine when i am using yotaphone with android 5.0 version (my slimport output a hdmi signal)

check this official supported list

http://www.slimportconnect.com/slimport-supported-devices/

try plug and replug the wire, mine is a cheap one, sometimes shaking the wire will lose/give you the signal to TV

---------- Post added at 03:03 PM ---------- Previous post was at 02:54 PM ----------

It seems i figured out another bug.

after playing for a while (using opera to surf the net, switching apps. etc)

my EPD got some problem. When i try to scroll down the page (in opera), the screen keep flashing(annoying Full/Whole Screen white and blank) while scrolling down. It also happens on some other apps, it looks like the EPD keep refreshing for each tap/scroll on the screen.

The only solution is to reboot the devices.

I try to reproduce the bug and report it here.

but i 've heard it had been a bug since the beta version.

hope to see someone reply.

Many Thanks
[YotaPhone] kbal:
And from my understanding Yotaphone "abandoned" 206 version (on their FB post), so there probably won't be any fix :(
[YotaPhone] JernejKobal:
ftp://fw.ydevices.com/YotaPhone2/ is down?
[YotaPhone] look-aa:
ftp://fw.ydevices.com is up, but then there are other folders, all the firmwares and yotaflasher disappeared!

There’s just "maven" and "addon". What are they?
[YotaPhone] ercicalone:
ftp://5.200.42.210/YotaPhone2/

ftp://5.200.42.210/YotaPhone2/Firmwares/
[YotaPhone] look-aa:
Out of curiosity, how did you find them? :laugh:
[YotaPhone] ercicalone:
i have searched on google: /YotaPhone2/Firmwares/

et voilà! FOUNDED

sorry for my english and french
[YotaPhone] JernejKobal:
^Yes, but Yotaflasher isn't working. I wonder what they are doing.
[YotaPhone] look-aa:
non importa si capisce :D

(doesn’t matter it’s understandable)
[YotaPhone] shokmah:
I've a YD201 version, even it comes also from HK. I don't have time to fix this those days. I might try a factory reset. I don't know if we have same bug but it's kind of pissing off.
[YotaPhone] JernejKobal:
Is yours actual 201? Could you please check.

Imei = 356... -> yd201

imei = 359... -> yd206

PS: I'm not actually sure if they talk about warranty only or support also (updates)?

https://www.facebook.com/YotaPhone/?hc_ref=PAGES_TIMELINE&fref=nf

Dear Customers,

Since September 2016 we have been tracking significantly increased number of grey import sales of YotaPhone 2 Chinese variant to EU countries and Russia. Due to this fact, we should inform you on the following:

1. All YotaPhone 2 stock of EMEA variant (model number YD 201, IMEI starts with digits 356) was sold in EU and Russia in 2016.

2. We do not provide warranty service to non-EMEA variant (model number YD 206, IMEI starts with digits 359).

3. The warranty support shall be made by Yota Devices Official Service Centers after a preliminary verification of IMEI of each smartphone. You can check your IMEI number by dialing *#06# to understand which YP2 variant you own.

4. If there are any issues concerning sales and aftersales in connection to YP2 sales by or through Chinese (re)sellers and/or any (re)sellers marketing and selling China variant of YP2, please contact respective (re)sellers directly.

5. (Re)Sellers mentioned in point 4 above are likely providing their own warranties to customers.

6. If you have any questions, please contact us at https://yotaphone.com/gb-en/feedback/
[YotaPhone] crimsoncustom:
I have waited for official release for MM but have just known recently that it's there already. Is there any way to sideload the yotaphone2-user-RU1.1.47-from-RU1.1.134 without connecting to PC? My USB cables are all very flimsy so any connection to my laptop doesn't last (I'm trying to get new ones, but currently they are all I have) but I'm trying not to do the OTA update so that I don't need to re-root or do anything with a PC. I have the zip files both in my phone and my computer, I tried to do the adb sideload+TWRP using my computer but I guess because of the cable it gave me "error: device not found" so couldn't continue.

Any idea?

Thanks, I can't really read all pages, but I've tried to look a bit, seems like it's either adb sideload or OTA update.