Exif date problem - ONE Q&A, Help & Troubleshooting

Hi folks,
Exactly as described in the link below, I am running in the exif date on my stock OPO:
https://forums.oneplus.net/threads/2002-12-08-exif-date-problem.104599/
In particular, if you take a picture (it is not important if with the Cyano camera or Google's one), you will find that the exif metadata "Create Date" is always "Create Date 2002:12:08 12:00:00" and it does not display the right data.
This bug has been experienced both on CM11s and on CM12s.
You can find a screen cast of the issue here:
https://youtu.be/bgsED_ty9Sc
How to reproduce the bug (from the phone):
1. take a picture
2. open the picture with Exifviewer
3. you will see that "Date/Time Digitized" (which is the same tag of "Create Date" on exiftool) is 2002:12:08 12:00:00 instead of "Date/Time Original (with the right date)".
Click to expand...
Click to collapse
The support service at OPO proposed me to install this batch file containing CM11S44S version of the ROM "which has a new kernel, updated drivers and a few partition reset which is known to fix some of the most common issues that some users have already faced with their device in the past" (their words): https://s3.amazonaws.com/oneplussupport/ONEPLUS+ONE-FIX-Windows.zip
Unfortunately this solution didn't work and upgrading to CM12 didn't solve the issue either.
The final suggestion received by the OPO support was to flash the OxygenOS (following the link below https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/) as they claim that this will fix the issue (the same thing they said with the initial solution).
I didn't tried to install the OxygenOS yet as I would prefer to stay with the CM and before wiping everything again I would like to be sure it works.
If you wonder to know, this bug has a major impact on my backup and archiving strategy on my NAS: http://forum.qnap.com/viewtopic.php?f=21&t=108692
The same impact will be with whatever photo collection manager software you will use.
Could someone help me finding a solution with the CM12s or anyone could kindly confirm me that this bug does not exist on the OxygenOS?
Thanks,
giopas
EDIT: bug track added here https://jira.cyanogenmod.org/browse/BACON-3497

Related

[Rom][Main version munjeni]Photon Android release thread

I think you need an update? Ok, here is new release bassed on release r134 and fixes from release r149 http://code.google.com/p/photon-android/source/list , all credits go to r0bin, schlund, pwel, mweber1980 and all who reported bugs, so now:
- battery full working!
- lightsensor full working
- headset working
- owerclocking enabled (just, disable perfloock and set owerclock you want!)
- bluetooth working (not tested audio routing!)
I want to say something. Diference beetwen mine release and release from google page is indentic, but have some diferences: mine release have diferent initrd, google page release use cache folder but mine release use cache partition, block size is smaler in mine release...etc (I think some sd cards previous not worked, working now), so if you not know what you are doing you will lose something like gps, 3g, ...etc becouse between mine/google release have small diferencies (but all is compiled from same sources and use same fixes), so if you want to use mine patches you need to use clean munjeni release! But if you use google release with mine patches (example: use mine initrd), you will lose something in compatibility!!! I no want to be misunderstandabled, but I think our forum need an changes (an release) becouse gone to be death forum... If you not have mine release installed, and you want to apply our update, please first delete all folders and files from previous version and install clean munjeni release, and than apply our update! If you have mine release installed, just apply update. If you have r134 release from google page, please dont use mine update! Currenltly we trying to clean other bugs but new release will be clean mix of our two version with other fixes and will be in next release!!! So enjoy with our upgrade bassed on r149 release
If you want bigger data.ext2 read this -> http://forum.xda-developers.com/showthread.php?t=1234215
DOWNLOAD munjeni r134++
Delete folder update and use all files from attachment, and run haret!!!
If you have problems with 3g please read this http://forum.xda-developers.com/showpost.php?p=15753895&postcount=256
Please ALWAYS give one comment, ask something, report new bug (please dont report known bug), report fixed bug...etc, if you want our photon forum to be non DEAD forum!
EDIT:
DmK75 said:
Seems little bug - russians file names on sdcard looks like ????? now.
Click to expand...
Click to collapse
Fixed bug, attachment reuploaded!!
EDIT:
I forgot to say about time bug. Time bug is not presented in mine version, but is presented only if you have not checked option "prevent sleep when charging" in options/development!!! So you need to enable that option becouse when that option is not enabled and phone charging, you will get time forward if your phone go to sleep (screen go to off), so don't forget to enable it!!! Also uncheck automatic time!
EDIT:
Sorry guys I forgot something for 3g internet, it's fixed now and attachment reuploaded!
EDIT:
Inproved stability for usb connection!
Full fixed msm fb_console and enabled on boot!
Attachment reuploaded!
EDIT:
Memory propertly realigned (++2M more memory), fixed htc console [htc_fb0] enabled!!! Attachment reuploaded!
EDIT:
problem with usb is fixed now (was in battery code when I enabled 3rd state), fixed division by zero in kernel, small changes to owerclocking code, added preparation for buttons led "3rd level lights like in windows", fix audio glitch when activating headset by r0bin...
If you interested to see what I changed here is link
EDIT:
battery polling updated: avoid level glitches and saves power by r0bin, updated defconfig, fixed camera, fixed alarm in sleep mode...
EDIT:
27.08.2011
- imported fix from r169 -> http://forum.xda-developers.com/showthread.php?t=1236229
Attachment reuploaded, changes is inside zImage, initrd.gz, gps.conf and startup.txt. Open startup.txt and read comented lines with ### for how to set some new parameters!
EDIT:
My final version will be here -> My final version will be here -> http://forum.xda-developers.com/showthread.php?p=17628363
thanks munjeni... u are the man... i'll download and try it...
Thk Munjeni, i will try this new release immediately!!!
Seems little bug - russians file names on sdcard looks like ????? now.
DmK75 said:
Seems little bug - russians file names on sdcard looks like ????? now.
Click to expand...
Click to collapse
fixed, please try again, I reuploaded attachment! Diference is in initrd.gz!
munjeni said:
fixed, please try again, I reuploaded attachment! Diference is in initrd.gz!
Click to expand...
Click to collapse
Yes, it's fixed now.
I have a question. This release have the same fixes that Cyanogen release? Because i alredy installed Cyanogen release and all is great. Thanks munjeni
Thanks for this release. I downloaded the files Photon_R134__.rar & froyo_update.rar. Extracted first file, deleted folder update and then unzipped second file. Deleted everything from SD card. Booted "haret", everything seems to work fine, it's all booting .
But I have no data connection. I do not really understand what to do, I followed the link, but am a little bit lost... Sorry .
Before I used r134 from google page and data connection worked fine "out of the box".
Anybody some problem? What can I do to get 3G / data to work?
michjosi said:
But I have no data connection. I do not really understand what to do, I followed the link, but am a little bit lost... Sorry .
Before I used r134 from google page and data connection worked fine "out of the box".
Anybody some problem? What can I do to get 3G / data to work?
Click to expand...
Click to collapse
I had the same problem. I then booted Android without the SIM card once and now everything works fine. Great release so far, thanks to all devs!
@michjosi:
have a look in munjeni´s post here:
If you have problems with 3g please read this http://forum.xda-developers.com/show...&postcount=256
I have one question,
I don´t want to loose my data. I use Version 127 with updates from munjeni. Is it ok, only to use the froyo_update.rar, or do I reinstall everything?
Pls help ;-)
THX,
Andy
andyecht said:
@michjosi:
have a look in munjeni´s post here:
If you have problems with 3g please read this http://forum.xda-developers.com/show...&postcount=256
Click to expand...
Click to collapse
Thanks Andy, I read that but do not really understand what to exactly do...
munjeni said:
I think you need an update? Ok, here is new release bassed on release r134 and fixes from release r149 http://code.google.com/p/photon-android/source/list , all credits go to r0bin, schlund, pwel, mweber1980 and all who reported bugs, so now:
- battery full working!
- lightsensor full working
- headset working
- owerclocking enabled (just, disable perfloock and set owerclock you want!)
- bluetooth working (not tested audio routing!)
I want to say something. Diference beetwen mine release and release from google page is indentic, but have some diferences: mine release have diferent initrd, google page release use cache folder but mine release use cache partition, block size is smaler in mine release...etc (I think some sd cards previous not worked, working now), so if you not know what you are doing you will lose something like gps, 3g, ...etc becouse between mine/google release have small diferencies (but all is compiled from same sources and use same fixes), so if you want to use mine patches you need to use clean munjeni release! But if you use google release with mine patches (example: use mine initrd), you will lose something in compatibility!!! I no want to be misunderstandabled, but I think our forum need an changes (an release) becouse gone to be death forum... If you not have mine release installed, and you want to apply our update, please first delete all folders and files from previous version and install clean munjeni release, and than apply our update! If you have mine release installed, just apply update. If you have r134 release from google page, please dont use mine update! Currenltly we trying to clean other bugs but new release will be clean mix of our two version with other fixes and will be in next release!!! So enjoy with our upgrade bassed on r149 release
DOWNLOAD munjeni r134++
Delete folder update and use all files from attachment, and run haret!!!
If you have problems with 3g please read this http://forum.xda-developers.com/showpost.php?p=15753895&postcount=256
Please ALWAYS give one comment, ask something, report new bug (please dont report known bug), report fixed bug...etc, if you want our photon forum to be non DEAD forum!
EDIT:
Fixed bug, attachment reuploaded!!
EDIT:
I forgot to say about time bug. Time bug is not presented in mine version, but is presented only if you have not checked option "prevent sleep when charging" in options/development!!! So you need to enable that option becouse when that option is not enabled and phone charging, you will get time forward if your phone go to sleep (screen go to off), so don't forget to enable it!!!
Click to expand...
Click to collapse
Thanks, download the test
data connection not possible
Hi,
I have same problem with data conection. With new release and blank SD card it is not possible!
After backup and restore there is no data connection possible. I do it like subscribet in post
http://forum.xda-developers.com/showpost.php?p=15753895&postcount=256
but negativ.
No data connection!
Pls help.
THX,
Andy
no data connection
Hi DEV and guys,
I tried new version, but I can´t get data connection.
System try to connect, but nothing. I tried all tips and tricks, but nothing.
I don´t have this issues with r127 with all updates of Munjeni.
So, what do I wrong? I did same installation like r127....
Any answers?
Andy
andyecht said:
Hi DEV and guys,
I tried new version, but I can´t get data connection.
System try to connect, but nothing. I tried all tips and tricks, but nothing.
I don´t have this issues with r127 with all updates of Munjeni.
So, what do I wrong? I did same installation like r127....
Any answers?
Andy
Click to expand...
Click to collapse
Maybe this fix help?
http://forum.xda-developers.com/showpost.php?p=15711778&postcount=173
Yes, THX,
fix works with new release!
Many THX.
Sorry guys I forgot something for 3g internet, it's fixed now and attachment is reuploaded in first post!
Bugs
Bug report:
- backside of mobile is getting hot, I will check when mobile is inactive
- data connection only with update possible (look former post)
- watch is running fast, check over this night during loading
Andy
Is hot because you tried camera shoot and not restarted phone?
Time forwarding because you charging your phone with screen off?
Time forwarding becouse your phone conected to usb with screen off?
Do not use cammera and youtube app becouse need to be fixed!
test
Don`t know if I have installed everything correctly..
But, data works, wi-fi works..
Heating effect present although not as dramatic as before.
Sync data is not saved..
Charging is still difficult, because suddenly the phone thinks that battery is 100% full. And its not.
Testing on the battery life...
Works much faster for some reason )
Excellent work.

[Q] Someone want to create a thread for a Lollipop ROM?

I have created a mostly-functional build of OmniRom 5.1 (Lollipop) for the T959V
However, I don't have enough posts to post in the development section or to put in links. Does somebody want to do this for me? If so, let me know.
The current status of it is:
What works
Taking pictures (very laggy switching between FFC and rear)
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
What is definitely not working
App to SD - not working on i9000 either, complains about insufficient space fixed in git
Tv-out as Omni's aries-common has removed it
Video recording - only captures fuzz fixed in git
What is untested
Everything else
What is probably not working
Microphone mute option doesn't work during calls - not working on i9000
GPS - I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset (hence why I have no clue on the status of the GPS) and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess from teamacid and others' device trees.
Selinux is set to permissive as I don't know how to create the proper policies for the GPS.
For a download and more information, see drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk (replace "*" with "/")
Source code can be seen under my github account (username is xc-racer99 there as well) under the android-5.1 and android-5.1-t959v branches
Ooooomg ...im wait ....is amazing the new proyect .....thanks thanks
Quick update:
I've got the video record to work properly now as well as being able to move apps to the SD card.
Selinux is left!
Should I upload a build?
Sure...I have a spare phone somewhere that I can test it. Do you have a Gapps package to go along with the ROM? As far as GPS is concerned, back when Beanstalk 4.4.2 was being worked on, a patch was developed to make GPS work...I'll have to root around in my files and see if I can dig it up...I think the developer deleted all the Beanstalk threads for some reason or another.
Yeah, I took the GPS files from CM-11.0 but I can't test if they work. With regards to the Selinux portion of things, only some parts of it were being enforced in KitKat while everything is now being enforced in Lollipop. GPS was not enforced in KitKat so the policies for it were not in place.
I haven't tried any gapps on it yet but I would recommend trying any of the three from the Omni i9000 thread
forum.xda-developers.com*galaxy-s-i9000/i9000-development/rom-t3054101 (again, replace "*" with "/")
I'll upload a new build as soon as I can verify that it boots - it fixes several issues such as apps2sd and camera that weren't working in the one I already have uploaded.
Also, I'm curious as to what the command "cat /sys/class/sec/gps/hwrev" shows. In CM11, one of the GPS files check this and depending on what it shows it loads a different file. Does this mean that there are two hardware variants of the SGS4G?
Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....
xc-racer99 said:
Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....
Click to expand...
Click to collapse
Link shows Not Found Error 404
Sammpls said:
Link shows Not Found Error 404
Click to expand...
Click to collapse
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.
Doesn't work... Why use google drive when there are others better for uploading your files.
xc-racer99 said:
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.
Click to expand...
Click to collapse
Sammpls said:
Doesn't work... Why use google drive when there are others better for uploading your files.
Click to expand...
Click to collapse
I was using Google Drive as its something I have an account for already and has plenty of space on. Do you have a suggestion of a site I should use? In the meantime, a direct link to the file is https://drive.google.com/file/d/0B7vXjzo0Hj-iZ0YtQTdoTG5KVW8/view?usp=sharing Hopefully this works...
Google Drive isn't bad at all. I was suggesting that you use another cloud service for uploading the files if it didn't work. (which i didin't do a really good job telling you that)
Thanks, that link works!
Alright, I have opened a devDB thread at http://forum.xda-developers.com/gal...official-omnirom-5-1-galaxy-s-4g-sgh-t3146611
Please post anything there and do not use this thread as I will not be monitoring it.
Google drive is at least better than Mega(especially if you use non top-end devices).

Important. For those who are using AOSP/AICP 7.0 ROM

1.Okay so, in this thread I'm going to post a fix for the infamous mobile data bug I.e mobile data which stubbornly refuses to turn on until restart
2. Substratum weird notification toasts after installing dark themes in which the lowercase y,g,q are incompletely rendered or else, in simple terms, they look weird because the lines don't seem to fit the toast
3. Only 2g bug
3. Overheating bug and battery drain
4. People who are sceptical about doze
5. No sim detected problem
6.Video recording bug
7. And if any more bugs, please mention. The above ones are all fixable although 5th and 1st require some workaround.
Important note. : to make sure that you don't encounter any sim card problem, clean flash this ROM only if you have flashed the official ROMs
Fixes :
1. Install any cm13 nightly. Dial *#*#4636#*#* and change the network type to WCDMA(3G) Preferred (or any G according to your choice). I recommend this step as a must because it hardwires the device to use all of types of desired networks and not enforce only 2g. Also, *please note to insert the data sim in the first slot only* in order to properly use this functionality.
If you are done with the above step, congrats, 80% of the work is already done. Open root explorer and go to /system/etc/apnconfig.XML (something related to APN and I'm sure it'll be the first file). Copy the file and save it somewhere in the internal or external memory.
Now flash android 7.0 and replace the same file in /system/etc/ and set the permission to read only I.e disable every right to write that file.
(This will work in most cases. If not then its a modem issue perhaps )
Edit : I found a new fix. Change the APN name to EE
and APN to everywhere
2. Go to display, change the display size to large and text size to small.
3. Flash the latest ROM of AOSP and disable clusterplug. There's already a tutorial on it in moto x play section. Please google it also govtuner is reportedly working.
4.doze works and phone goes to deep sleep. Observed via EX kernel manager
5.flash the stock ROM properly and then reflash this. Also possibly this is due to .70 volte update. So make sure you use the .52 update before flashing this ROM
6.use google camera and set the quality to 720p
7.you mention.
I'm no developer and I love to experiment. I'll make it a point to experiment on any other bugs if present
Thank you and please post your opinions.
Update : I disabled the aggressive doze in greenify and the data seems to work with the normal apn settings 'apparently'. Although this is the case with android n only. I didn't face this whole using cm13
Also I recommend periodic clearing of partition cache
This is definitely posted in the wrong section. What about this thread implies "Original Android Development" ?
Should be in the general discussion section.
Men thks for the post but, can you xplain how can i do the cluster plug off ? can you help me please
FanDroid09 said:
This is definitely posted in the wrong section. What about this thread implies "Original Android Development" ?
Should be in the general discussion section.
Click to expand...
Click to collapse
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
anderson.laverde said:
Men thks for the post but, can you xplain how can i do the cluster plug off ? can you help me please
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...r-plug-enable-disable-stock-cm-t3422345/page4
kpamkar said:
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
Click to expand...
Click to collapse
Still the wrong section
Why is this needed? Most workarounds are told already. And this should be in general not development
kpamkar said:
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
Click to expand...
Click to collapse
It doesn't matter what your logic is. This section is for developers that are posting their original work.
The point is to keep the forums properly organized. Not to make it as easy as possible for users who can't search a thread for solutions that have already been talked about.
kpamkar said:
1.Okay so, in this thread I'm going to post a fix for the infamous mobile data bug I.e mobile data which stubbornly refuses to turn on until restart
2. Substratum weird notification toasts after installing dark themes in which the lowercase y,g,q are incompletely rendered or else, in simple terms, they look weird because the lines don't seem to fit the toast
3. Only 2g bug
3. Overheating bug and battery drain
4. People who are sceptical about doze
5. No sim detected problem
6.Video recording bug
7. And if any more bugs, please mention. The above ones are all fixable although 5th and 1st require some workaround.
Important note. : to make sure that you don't encounter any sim card problem, clean flash this ROM only if you have flashed the official ROMs
Fixes :
1. Install any cm13 nightly. Dial *#*#4636#*#* and change the network type to WCDMA(3G) Preferred (or any G according to your choice). I recommend this step as a must because it hardwires the device to use all of types of desired networks and not enforce only 2g. Also, *please note to insert the data sim in the first slot only* in order to properly use this functionality.
If you are done with the above step, congrats, 80% of the work is already done. Open root explorer and go to /system/etc/apnconfig.XML (something related to APN and I'm sure it'll be the first file). Copy the file and save it somewhere in the internal or external memory.
Now flash android 7.0 and replace the same file in /system/etc/ and set the permission to read only I.e disable every right to write that file.
(This will work in most cases. If not then its a modem issue perhaps )
2. Go to display, change the display size to large and text size to small.
3. Flash the latest ROM of AOSP and disable clusterplug. There's already a tutorial on it in moto x play section. Please google it also govtuner is reportedly working.
4.doze works and phone goes to deep sleep. Observed via EX kernel manager
5.flash the stock ROM properly and then reflash this. Also possibly this is due to .70 volte update. So make sure you use the .52 update before flashing this ROM
6.use google camera and set the quality to 720p
7.you mention.
I'm no developer and I love to experiment. I'll make it a point to experiment on any other bugs if present
Thank you and please post your opinions.
Click to expand...
Click to collapse
Moved out of the Development sections to here....
can you give the important parameters from: /etc/apnconfig.XML
thnx
New fix is mentioned. Please check
E:Unknown Command[log]
E:Unknown Command[log]
Error when flashing any nougat rom
PSxplay said:
E:Unknown Command[log]
E:Unknown Command[log]
Error when flashing any nougat rom
Click to expand...
Click to collapse
Not an error. Happens with everyone. Don't worry
I'm trying to go with RR5.7.4 / CM13 but AOSP / AICP N7.0.0. Returning to .52, install the kernel from axxx007xxxz / only for N, full wipe, wipe data. Does not help. "Insert SIM". When flashing an error in a previous post.
Rive188 said:
I'm trying to go with RR5.7.4 / CM13 but AOSP / AICP N7.0.0. Returning to .52, install the kernel from axxx007xxxz / only for N, full wipe, wipe data. Does not help. "Insert SIM". When flashing an error in a previous post.
Click to expand...
Click to collapse
Wait. Why are you flashing a different kernel other than what was given in the rom already ? Also you need to do a full flash which includes flashing of every single file in the retasia/reteu package
I need to go back through the fastboot on the stock?
Rive188 said:
I need to go back through the fastboot on the stock?
Click to expand...
Click to collapse
I guess so. It seems you messed up with the kernel settings. And please give me the exact details of the files you flashed
kpamkar said:
I guess so. It seems you messed up with the kernel settings. And please give me the exact details of the files you flashed
Click to expand...
Click to collapse
All files are taking on XDA. Now it sets RR 5.7.4. I tried to install AICP, AOSP.
Rive188 said:
All files are taking on XDA. Now it sets RR 5.7.4. I tried to install AICP, AOSP.
Click to expand...
Click to collapse
I'm sorry I didn't get you. Can you elaborate properly?

Magnetic Sensor doesn't work/missing

Hi,
Short story, I bought another Mi4C. It's new, not a refurb one, though "new" here has a chinese label which state that the production date around 2016-10.
First thing, apparently the battery was emptied, so it drained very quickly. Second, it came with a non official MIUI rom (marshmallow 8.0.4.0.0), but fortunately for me, the bootloader is already unlocked. I played a bit a little, all sensors were working fine along with all other feature (cameras, digitizer, etc), so I quickly grabbed latest lollipop TWRP, and flash latest nightly AICP, and also 8.5.1.0 firmware.
Everything was working well until I installed a compass app, it's not working. Strange, so I looked up CPU-Z and find out that magnetic sensors doesn't appear.
Now, I've read this might be caused by malfunction/broken persist.img, so quickly grab latest official fastboot MIUI chinese stable (8.5.1.0), extracted the persist.img, but I was worried how small it is. And if I view it under a hex viewer, most of it's file are filled with 0x00 value, is it a correct persist.img?
Before I do anything stupid flashing that suspicious persist.img with fastboot, I need a confirmation whether anyone here ever came across the same problem? I've seen other thread regarding missing sensors too and that thread also suggests to flash the persist.img... But the file quite the same, ~5mb with most of its entry filled with 0x00.
Any helpful feedback is welcomed.
PS: I saved an old mi-globe ROM 8.1.3.0 (lollipop) stable, clean flash to that, and called the MIUI diag (*#*#6484*#*#), this time when I tried the magnetic, the app always crashes.
Anyway, so I had /persist partition backed up using Wanam Partition backup, but before I proceeded to flash the persist.img from mi4c official china stable fastboot, I checked using DiskInfo (and compared it to my old mi4c). I found that /persist at my new mi4c didn't show mounted (it's mounted at the old one). I fired up some sensor test app, but it was never mounted, strange. I've attached both screenshots.
I tried to mount it manually from terminal, but it always ends up with invalid argument error or I/O error (see attachment). I need to know whether this might caused that problem. If anyone could shed some light, I'd really appreciate it.

Discussion of OFFICIAL LOS 19 & LOS 20

I've created this thread to discuss LOS19. Hopefully, one of the maintainers will create a proper thread.
Downloads
Official: https://download.lineageos.org/sunfish
Installation
https://wiki.lineageos.org/devices/sunfish/install
Upgrading from 18.1
https://wiki.lineageos.org/devices/sunfish/upgrade
Updating
https://wiki.lineageos.org/devices/sunfish/update
If you find their work useful, don't forget to support all their work.
https://paypal.me/LineageOS
https://patreon.com/LineageOS
Visual Voicemail Error
I'd like to thank @razorloves for working on a fix to the VVM problem. Razorloves has already provided the work to the Android project. Let's hope all goes well. The work is greatly appreciated.
Razorloves created a new "Dialer.apk" for LOS19. The LOS18 version is already being shared in that thread.
I've attached "Dialer-19.1.zip", which contains the file razorloves created with the fix. There's also a sourceforge download link. I don't know if that would be better.
To try this fix....
Enable USB debugging in your phone.
Enable ADB root in your phone.
Use these adb commands....
'adb root'
'adb remount'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is from 2008
'adb push Dialer.apk product/priv-app/Dialer/Dialer.apk'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is now from 2022
reboot your phone.
Hopefully, the fix will make it through AOSP & onto the official LOS19 ROM soon.
Got notice that the VVM issue has been closed. The Dialer app will be fixed in next build.
So, if you're on LOS19, you can just wait for the June 2 build.
Big thanks to @razorloves for the work that made it happen
EDIT: Sorry! Deleted this post because my lack of knowledge made it appear like I was insultingly impatient. Many thanks to all the people who make LOS available for us dunces.
Sincere apologies to anyone whom I might have offended.
Since I switched from LOS18 to LOS19, I'm having a couple of issues.
This is NOT a complaint. I'm simply sharing to see if others are also experiencing these.
I updated per the LOS webpage instructions (ie. not a clean install). Phone has no custom-kernel,
no GApps, and no Magisk. Build is June 9th (latest).
1) Calendar notifications.
I'm not getting calendar notifications. This was working fine in LOS18. I'd get a notification at the defined time before an event. Sometimes, while I'm working on the Calendar, I get old notifications (as in events from days ago). Today, while testing, I got a "Calendar keeps stopping" popup.
My calendar data is offline. I deleted my calendar and created a new one. Nothing changed.
2) Charging.
When I plug into my PC, I get the sound acknowledgment from my phone. The Battery screen tells
me "Charging". However, it is not charging.
EDIT: As always, I'm a day late and a dollar short.
This is a known LOS19 issue (with USB) that was being processed. They have a fix in place that we should see next build (June 16th). Thanks (again) to the LOS team for their time/effort!
Is anyone else having the Calendar issue? If you're not, did you update to LOS19? Or, did you perform a "first time" install (wipe data & such)?
Thanks for your time.
@mangokm40 How is the battery life on LOS 19?
AkumDX said:
@mangokm40 How is the battery life on LOS 19?
Click to expand...
Click to collapse
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
mangokm40 said:
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
Click to expand...
Click to collapse
Oh okay ... Haven't used LOS 18 for few months now... Currently on 13 beta, battery isn't that great so thought of switching
4a LineageOS 19.1 Update 2022-06-16 - Security Bump
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-09 + lineage-19.1-20220609-recovery-sunfish to build 2022-06-16. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 12 minutes.
There are a bunch of changes as you can see here:
I tested the USB fix. It's not working for me. Thanks to user razorloves. I toggled the "Always allow USB connections" setting in "Settings->Privacy->Trust". My phone is now charging, even when locked.
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "June 5, 2022".
The Vendor security patch level (just below) is also "June 5, 2022".
The Build number at the bottom is now "SQ3A.220605.009.A1".
The Baseband updated to "g7150-00090-220406-B-8411773".
See Android Security Bulletin - June 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220616" and active slot 'a'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
lefteyecat said:
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
Click to expand...
Click to collapse
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
mangokm40 said:
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
Click to expand...
Click to collapse
Thanks,looks like i have to hold out on 18 for as long as i can.
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
Nope.
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
i use swiftbackup and nova launcher, its not as good as twrp ( still need log in verifications) but does restore all apps and screen positions , best and easiest solution i have found so far. Root reguired.
Is anyone running the latest version of LOS19 (lineage-19.1-20220623-nightly-sunfish-signed.zip) ?
I'm asking because there's this VVM issue open for a OnePlus7, running LOS18.
VVM is working for my 0616 build of LOS19, and the issue mentions it broke when they installed their device's 0619 build. Thus, I looked at the list of changes for our device here.
There are 5 changes to "android_packages_apps_Contacts".
There are also many changes to "android_vendor_lineage" that mention APN changes for various carriers.
I'm wondering if anyone is running the 0623 build & has VVM working.
Thanks.
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
mangokm40 said:
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
Click to expand...
Click to collapse
Thank you mangokm40 for all the infos, tips, tricks and hints you post! Really appreciate it!
4a LineageOS 19.1 Update 2022-07-14 - Security Bump, Calendar Update, Hidden Apps
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-16 + lineage-19.1-20220616-recovery-sunfish to build 2022-07-14. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 11 minutes.
There are a bunch of changes as you can see here.
The ones that I noticed are:
1) Security Bump - see details below.
2) Calendar Update - the update to version 1.0.30 didn't clear the search crash problem. The battery use is now forced to "Unrestricted", to allow all notifications to appear on time.
3) Hidden & Protected Apps - It remembered all my hidden apps from LOS18 & they were hidden without needing any new input from me. WooHoo!
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "July 5, 2022".
The Vendor security patch level (just below) is also "July 5, 2022".
The Build number at the bottom is now "SQ3A.220705.003.A1".
The Baseband remains as "g7150-00090-220406-B-8411773".
See Android Security Bulletin - July 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220714" and active slot 'b'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Hello, can someone help me with the following question?
* Does Google Pay / banking apps work good with this rom? I suppose that magisk is needed along with some safetynet fix?
Thanks!

Categories

Resources