Related
This is my journey from Eclair to Froyo - read only if you have ample time. You have been warned !
I had never tried even rooting my Galaxy I5801 so I was a bit hesitant to upgrade my DDJG6 Eclair to DDJP2 FROYO even via Kies. After some days of the official release I finally plugged my phone to update. But alas, Kies constantly showed "operation timed out" (poor connectivity ?) and I was left with no other choice but Odin
DAY 1:
Downloaded the flashing package and the relevant firmware, connected and fired up Odin as per the tutorial. Loaded the packages and started the process with a prayer on my lips. The first boot nearly gave me a panic attack but the tutorial did calm me down and voila ! I had successfully flashed Froyo. Thereafter I also loaded my backed up contacts & memo data through Kies sync.
DAY 2:
I was happy with my effort and started explorin the possibilities of FROYO including app2sd. All fine until I decided to install a flashlite plugin later that day. The system starting freezin so I rebooted. The problem recurred and I again rebooted. This my boot screen got stuck on the "GTI5801 - Samsung" screen. I knew I was screwed but since I could access download / recovery mode (even though wipe data or cache didnt work) I knew it was only a "soft brick"
Day 3:
Geared up to reflash my phone through Odin. This time I took some unusual steps - removed bootloader & sbl and extracted dats.rfs from DDJG6 & added it to DDJP2 tar package. Flashing was succesful and I had started to sort of like the entire process.
Day 4:
Was disappointed with the improper implementation of swype so I decided to install swype beta. Root, delete, register and install - simple ? That's what everybody says.... Downloaded superoneclick, enabled USB debugging and rooted (Z4root didnt work). Now the delete process was tricky. Couldnt make sense of titanium backup so tried another method. Since root explored is paid app and terminal emulator is beyond my scope, installed super manager from market. Gave superuser permission and started deleting relevant swype files - I think it was 2 from /system/app, 1 from /system/lib and 1 from /data/data. Registered for swype beta and downloaded it as advised on the website. I write this post with swype beta.
Everything is working fine now - almost !
PROS - learnt flashing, knew the benefits of rooting, now can manage my apps and memory a bit better
CONS - My music player is screwed. For that matter, any music player I have downloaded and tried is having the same problem. The player doesnt play some music files, skips it or even if forced to play remains mute although the music play status bar moves. I checked the file properties and played them on PC. They are either Mp3 or M4a. Do I need to reinstall the music player coz it sounds like its become corrupted ? But then it plays some tracks flawlessly
I am in debt to XDA Galaxy 3 forum members and rudolf in particular for helping me out at crucial junctures. Now if only I could solve this problem !
jg6 is an eclair rom right? That could be causing problems, mizing eclair and froyo.
Did you do a factory reset after flashing (I suspect you did if you followed a tutorial).
Also, removing boot and spl is not unusal, it is HIGHLY RECOMMENDED, always do it! (this is mostly for other people reading this thread)
Nice story... Waiting for day 5+
@stubborn - yup, i did a reset but the music player problem persists. I included the data.rfs file from eclair to froyo coz I was somehow convinced that its absence in the DDJP2 had causes my system to freeze the first time
@kyrillos - Day 5+ testing isnt exactly detailed. The only thing I noticed is that the battery drain was more than DDJG6 eclair or maybe its the battery bug acting whimsically (as it usually does). Havn't modified or tested the GPS so no comments. Installed Gingerbread keyboard but not exactly to my taste. Still using a combo of swype and regular tap.
BTW - ur ROMS are damn good judging by the features, performance feedbacks and screenshots. However, It will take me another leap of faith to flash one of those since the complexity involved is beyond my current level of expertise (or rather the lack of it !)
Any ideas / tutorials on deleting the stock music player app and reinstalling it (with apk files, if possible) ?
Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:
Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...
what?
i havent got this
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?
Read the freezing thread sticky .
Delete this non working fix as well .
JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?
Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.
Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.
EDIT: Here's a verbose log that was being recorded before the device rebooted as explained below. It happened 2 seconds after I locked the screen with the lock key...
http://www.fast-files.com/getfile.aspx?file=74248
I know it's a big file, and it's long but it does open in regular Notepad, just wait 40 seconds. Hopefully you can find the cause at the bottom of the log. I can't make sense of it.
---------------------------------------------------------------------------------------------------------------
Hey guys, any idea how to find out why my S4 seems to be rebooting every few hours, mostly after being woken up?
Some tech info:
Baseband: I9505XXUGNE5
Stock Kernel
SE For Android: Enforcing
Build Number: KOT49H.I9505XXUGNE5
Phone is rooted & Xposed installed
Quick bit of info:
It seems to happen 90% of the time when the screen goes off. By this I mean, the screen can go off no problem and then I can turn it back on without an issue. However if the phone does reboot, it seems to be when the phone is woken up after being locked/asleep. However it does happen sometimes whilst I am using the phone. Though very rarely.
It's also important to note that the phone does a 'fast reboot', not a regular one. Like it skips the 'Samsung Galaxy S4' screen and just goes straight to the spinning logo. It does reboot very fast, but it is really annoying.
However I don't have to put my SIM PIn in again, it just asks for my phone PIN and then starts to load apps as normally.
Is there some sort of App I can install that will log all errors right up to the point where it crashes. Then I could view the log and work out what caused the crash? I have the Donate of aLogcat but it doesn't seem to allow me to do this...
Any ideas guys? Any info would be absolutely awesome.
I really don't mean to bump guys but I've flashed 3 times now and still get reboots...
Could I need to flash a new boatloader or something?
The download is to slow. Just post your log in pastebin and post the link here.
What I would do in your case is to fully wipe (also wipe your sd card) and return to a clean rom. Don't install any apps, dont restore backups and see if the problem persists.
If even with a fress install you have to issues, then it's a hardware issue.
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I updated the post HERE if somebody is interested. More KNOX remains to freeze or delete
leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I would suggest performing a factory reset before freezing the Knox stuff. That way you have a clean start.
I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.
wild wadi said:
I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.
Click to expand...
Click to collapse
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.
Lennyz1988 said:
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.
Click to expand...
Click to collapse
Chainfire asked in another post people who are experiencing these reboots to list their installed root apps which I sent to him.
http://forum.xda-developers.com/showthread.php?t=1538053&highlight=random+reboot&page=551
Maybe it is SdFix. I will check that out but, I would like to know if others who are experiencing reboots here have SdFix installed or maybe to list their installed root apps (like Chainfire suggested) so we can compare notes as to who is and who is not experiencing random reboots.
Hey guys,
after flashing the 5..1.1 rom my Note 4 started to lag at the keyboard after typing few letters or reading the website or in menu.
I use the N910FXXU1COH4 software. The worst part is that it happened yesterday. I havent got lags before (never ever).
Now I've got also lags when I downgrade to 5.0.1
Do you have any idea why this happened? My phone is ofc rooted and I've deleted most of the useless (for me) crap out of it like Instagram, NFC etc.
Do you have this kind of problems with your phone?
Thanks for reply.
I had the same issues you've stated after flashing a 5.1.1 Sweden rom with ODIN.
It lagged like crazy while other aspects were buttery smooth.
After a factory reset and a re-install with ODIN (just the way I did it- not saying it's the correct way of doing it) my phone is running as it should- super quick, smooth and as a Note 4 should be.
So I'd recommend full-wiping and then re-installing the 5.1.1 tar via ODIN.
I've also rooted now too with no issues.
Good luck.
I've got also problem in games. Sometimes the animation just freeze for about 0,5 s and then it runs again. It happens everywhere. And I've got it from yesterday. Dunno whats the problem...
I'm having lags and stutter too my friend, but i'm gonna leave it like this for now and wait for a proper release of 5.1.1 for my country instead of frankenstein mix it like i did now.
If that does not fix the lags im going back to 4.4.4 and never upgrade it again.
Guys, this problem is quite strange.
I've downgraded to 5.0.1 and then to 4.4.4 and every time Ive got lags on keyboard and TW. My phone started to freeze for about 0.5 s - 1 s. Its very annoying and I dont know how to deal with this problem. And it scares me ! Cuz knox is [1] and the warranty went for a walk I guess so i dont know what to do now...
Have you ever this kind of problem with your phone? Even the downgrade did nothing. Before flashing the 5.1.1 system it was fine. Now going down and wiping whole system gives me nothing ;(
Please help! I dont know what to do now...
On cyanogenmod 12.1 works fine. The problem is I guess with the touchwiz systems...
On 5.1.1 touchwiz is also overheating now :/ maybe thats the problem?
So the problem looks like this : After flashing the Swedish 5.1.1 system it all started up.
I can see it in:
1) Games - when it randomly freezes for second
2) Keyboard - after hitting multiply in letters typing something like asidiasjdasijdsaid -> it sudennly stucks and then after about 1 s the button ive smashed shows up in the text message with the lag3
3) touch wiz - after swiping from homescreen to another screen just dont answer and after about again 1s it changes
4) the top bar - with wifi, sounds, brightness, clock, battery etc) also goes down with lag - I swipe with my finger and after 1 second - it react.
5) sometimes it shows the grey suqare at the bottom "Phone is in factory mode" - red letters. It shows only for a while and suddenly disappear.
I've changed every rom now - from 4.4 to 5.1.1 and its still broken! On the Cyanogenmod it works just fine. Something might be broken but I dont know what. Also in cyanogenmod the only game i play have this lags. Other things works fine.
Any solution, what can i do? everything was ok before flashing the 5.1.1? Ive got the EFS folder backuped via TWRP
// EDIT
So - after I've found the backup which I've done just after buying Note I've restored full system (EFS, cache, system etc) and it helped. I guess 5.1.1 flashes makes that my Note 4 had a very bad day.
You can close the topic. My advice is to always have backup ! Glad Ive done it before.
So, it just popped up while my phone was idle, without anyone calling it in here first, YotaPhone finally decided to give us EU users the RU124 firmware! It looks from the changelog to be the exact EU equivalent to its RU counterpart, including YotaTravel, the return of the YotaStore and other stuff. It's been so long that I don't even remember, but I should be fine flashing this and then reflashing SuperSU and Xposed without losing anything, correct?
If you have stock recovery it will install fine. If not you should be able to grab the update zip from /cache and side load. Then reflash what you want.
Sent from my iPhone using Tapatalk
Yep I'm still on the stock recovery (I just boot TWRP every time I need it). Gotcha, then I'm just dumping my Titanium Backup folder onto my PC as a precaution, and then I'll update and report back on SU\Xposed.
Looks like whatever Yota pushed at 117MB was the wrong thing - a failed update attempt and a reboot later, it's now 0.94 GB. Seems like it's the correct size in ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/ so now it should work.
Update from RU1.1.112 to RU1.1.124 issue
https://r.tapatalk.com/shareLink?ur...share_tid=3436224&share_fid=3793&share_type=t
Sent from my iPhone using Tapatalk
Just as expected the 0.94 GB update file worked, I reflashed SuperSU and Xposed and the phone is working great on 1.124b.
What version were you coming from?
Sent from my iPhone using Tapatalk
EU1.87. I wanted to go to the RU version but never could get a KitKat RU firmware to boot on my device, so I just gave up and went back to the latest EU firmware.
Ah OK that makes sense. Glad you got it working.
Sent from my iPhone using Tapatalk
Go mine today (1.1.44HK)
Updated to EU 1.1.124b with official yotaflasher.
No Su nor any hack.
So far no bug, it's a great device.
Hi there!
I'm waiting for my yotaphone 2 from this new wave from chinese shops. I ordered the International version. Is it safe to flash the EU version firmware over the "international" version?
And please, can anyone provide an alternative downolad link for the yota flasher?
The one from offcial website:
https://yotaphone.com/us-en/ypflasher/
is a corrupted zip file.
Thanks!
Edit:
I could get it from here:
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Seems there's a bug.
Almost each time i try to unlock phone (with power button) from EDP the pin keyboard isn't showing up, i must tap all over the EDP screen, way it's relocking then i can have the keyboard again.
Solved by using gesture instead of pincode
satsuki_yatoshi said:
Solved by using gesture instead of pincode
Click to expand...
Click to collapse
Gutted they removed the Instagram Cover instead of fixing it!
Rarelyamson said:
Gutted they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
Instagram restricted access to its API, so none of 3rd party apps now work properly. Thats why Instagram Cover was removed.
Hello
I deployed this great update a few days ago, and it clearly brings numerous improvements and fixes.
One visibly new bug annoys me a lot anyway, and that's why I am posting :
When I type a SMS on the EPD, lots of freezes occur. And today, I found a simple pattern. I type a word, and then I back-delete one or a few letters of it. Then I add new letters, and that frequently freezes the EPD for a long moment.
It's not 100%, lots of times it freezes under these conditions, few other times it does not.
I setup 3 languages to choose from (thanks to the update !) and the auto correction is ON.
Does someone else experience the same issue ? Any workaround or fix ?
Thanks
Appens to me 2 times, each time i needed to look/unlook the edp screen to solve
My problem is that with the latest update I need to restart my phone until it starts charging. Otherwise it will not charge ... does this happen to anybody else? Probably I should try to reset ...
no charge bug here
No charge bug here neither. Quite the opposite in fact, I would even say that autonomy obviously improved since this update.
And I confirm I have the same bug with the PIN keyboard not showing up on the EPD when using the Powa button. It happens very often after using the other screen, but unlocking by tapping twice is an easy and efficient workaround.
Surprising obvious bugs anyway, I hope the Yotagods watch us and intend to fix them.