Related
Q&A for [ROM][UNOFFICIAL][WIP] Cyanogenmod 11 (4.4.4 - kitkat) for fairphone FP1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth functionality
Hi, Chris,
amazing work! I am so glad to see that finally someone managed to get CM 11 running on our Fairphones! One question: Is it correct that Bluetooth functionality is still missing? Just asking because the WIKO Stairways, which you also seem to take care of, has a very similar hardware architecture and as far as I understand, the CM 11 ROM provided by you already offers bluetooth functionality. Is there a big difference between these two devices?
Apart from the missing bluetooth functionality I am very tempted to try your ROM ...
Keep up the good work and thank you!
Next steps and what can we do?
Thanks, Chris, for your great work. It's awesome to see that CM on Fairphone is possible after all.
The list of known bugs/missing features still includes some items which are a show stopper for many users. I'm one of them. Therefore I'd like to see some progress in these regards. IMHO it would be of great help for potential contributors if there was some sort of coordination on what has to be done.
Chris, do you mind elaborating what the issues with the known bugs are? What are areas which you already work on? What are problems which someone else could tackle? And, most importantly, where should one start?
I'd like to try and give it a go. However I know already that I'm not likely to get very far unless I can discuss issues and get some help. So, what are you currently working on and what do you suggest to start with?
Regards,
jftr
Error during installation of Cyanogenmod11 on Fairphone 2nd batch
Hi,
I have a Fairphone 1 but the second batch (FP1U)
I follow the install process of Cyanogenmod11 here but I had this error during flashing :
HTML:
set_metadata_recusrive: some changes failed
E:Error in /external_sd/cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.2.zip
(Status 7)
Installation aborded
(you can this the attachment)
I could restore a backup, but I'm ready to restart flashing if you have idea to pass this error
Spheerys said:
Hi,
I have a Fairphone 1 but the second batch (FP1U)
I follow the install process of Cyanogenmod11 here but I had this error during flashing :
HTML:
set_metadata_recusrive: some changes failed
E:Error in /external_sd/cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.2.zip
(Status 7)
Installation aborded
(you can this the attachment)
I could restore a backup, but I'm ready to restart flashing if you have idea to pass this error
Click to expand...
Click to collapse
A short Google search suggests to update Clockworkmod to the latest version. Have you tried that?
Here is more information regarding the issue (Unfortunately I can't post any links yet, so you have to remove the space after http)
http ://android.stackexchange.com/questions/62982/flashing-cm-11-i-get-set-metadata-recursive-some-changes-failed
http ://stackoverflow.com/questions/19860479/set-metadata-recursive-failing-on-android-install
"set_metadata_recursive: some changes failed" : solution
I have found the solution in a french forum : remplace the "update-binary" file inside the ROM : /META-INF/com/google/android/update-binary with the version on the forum below
forum-generationmobiles.net/t73067-astuce-regler-le-probleme-du-message-d-erreur-dans-le-recovery-set_metadata_recursive-some-changes-failed-25112013
Settings crashing and other bugs following
I have a series of problems at hand with my FP1 that has Cyanogenmod. I would be very grateful if anyone here could help me out with any of them, as FP zendesk etc. couldn't.
Firstly, the Systems settings menu and now even Manage apps -menu don't open. When I try, they just flash quickly on the screen without allowing any time to even read them. This problem started smaller last winter and then disappeared, but now it has come back and is getting worse and causing other problems. First it was just the system settings menu. But now it concerns also manage apps. I can't even make a downloaded new app work because the phone doesn't let me allow them any superuser rights from the settings.
-The first time this happened I could reformat my phone. But the problem now is that I don't want to loose all my stuff, so I want to do backup first. However: - the phone doesn't detect the SD-card that is inside. -I have Cyanogenmod instead of Google, so backing up using cable+Google Plus is not an option. I downloaded MyBackupPro for this, but the phone doesn't allow me to grant it superuser rights so I can't use it. So is there any other way to backup my phone?
-Now another problem that costs me actual money (I hope that my operator will compensate it later) is that some bug is "sending" non-existent SMS to some Finnish numbers and to one number abroad. In reality there are no SMS sent but on the bill it shows as if I had sent for example 2-4 text messages at the same time. Avast! Mobile security virus scanner didn't find anything. I aimed to remove some of the apps I had lately installed, in case that some of them had brought a bug along, just to notice that I can't even access the apps menu anymore in order to do so.
After schecking detailed call reports from my operator, I also noticed that all the sms that are a couple of rows longer, are sent as 2< messages. So even when I think I sent one longer message, at the bill it is counted as two or more..
Fortunately I could create a bugreport, which I will try to attach here asap (apparently need to compress it first...). It is a few days old, but soon after that I took the simcard off so & haven't used the phone much offline, either, so I guess the report should still be quite up-to-date (?).
So it would be great if someone that can interpret the report/ othwerwise has a clue what this could be about, would tell me their advise in terms of where I might start solving this bunch of problems!
(Should be the last time when person like me who doesn't understand much about software buys an alternative phone and installs an even more alternative operating system for it..and then finds herself in a mess like this with no idea how to get out..)
I'm sorry to hear that. It seems you thoroughly infested your phone with malware. I strongly suggest you reflash to get rid of the malware in its entirety.
Regarding backups: If you feel comfortable using the command line, you could try to connect to your phone from your computer using adb. There is a backup command and you can just copy files directly.
Good luck
Thanks for your reply!
I only use command line when I have step by step-instructions for it, not independently. . . Fortunately the link you gave seems to have quite clear instructions. I'll check that soon!
Try with Helium
AinoV said:
Thanks for your reply!
I only use command line when I have step by step-instructions for it, not independently. . . Fortunately the link you gave seems to have quite clear instructions. I'll check that soon!
Click to expand...
Click to collapse
I would use Helium for you backup. It can use cloud storage as backup destination. This solves your SD card issue. You also can use your PC to enable the backup without having root. This solves your root issue.
Thankyou for your expert tips!
I couldn't install neither Helium nor Android SDK that is needed for ADB , because as I said the phone settings don't open so that I could have allowed any app superuser rights.
(Actually in safe mode the settings do open but that, in turn, doesn't show any appstore available so that I could download anything new.....)
But fortunately I could upload all my photos into Dropbox and eventually managed to download and use a simple app for SMS-backups --> Dropbox. All the rest doesn't matter so much, as the apps I'll need I can download again.
So, now the backup problem is solved and I can proceed to the reformatting phase. It's probably wiser that I choose the default platform (Google ) this time in order to avoid further headaches that easily come when going too alternative with too little skills for that!
Thanks for this nice work! I was waiting long for CM on my fairphone.
Unfortunately I had to change back because of issues with the SIM management. It was not possible to switch on or off a SIM card except by going via Airplane mode and there were issues with connecting to a data network on both SIM-slots. Smaller issues were the missing BT and worse battery life than before.
Impaired battery
Summing up my problems / experiences with the battery performance after using CyanogenMod for a couple of weeks on my fp1: Over time (especially after upgrading to m11) I noticed a steadily growing loss of battery performance over time. The rear part of the device often seems hotter, especially when charging or when extensively using my phone. I can compare with my gf fp1 who uses the original FP OS. Compared with hers, the battery now seems bloated, significantly lasts shorter, shows inaccurate battery percentages (at the beginning dropping from 20 % to 0 in no time. Now even dropping from 40 - 50 % to 0).
I tried to calibrate the battery a couple of times with various apps, but the main problem with that is that I am not able to charge the battery with the phone shut down, as the phone automatically switches on when connected to an active charger. A short search revealed, that it's probably due to a kernel issue with the costum rom. Trying out other types of chargers didn't solve the problem.
Another thing I noticed, is that FPOS as well as CyanogenMod display strange MV values (2 - 4 mV while a fully charges battery should display up to 4200 MV - again see attached picture) in the app Battery calibration.
In order to figure out whether the battery is really impaired, I switched batteries with my gfs FP1. Both have been in use for the same time and both were charged with the same charging cables as well as used in similar patterns.
My battery lasted significantly shorter in my gfs FP with FP OS compared with her normal battery. Her battery worked better in mine, still it didn't lasted as long as her phone.
Another strange thing I found was that sometimes the battery doesn't only drops dead, it sometimes also gets stucked at 1 % for quite a while (see attached files). With no way to resolve this by calibrating the battery.
In all likelyhood no problem with CM as it seems to have appeared with FP OS as well see https: // forum.fairphone.com/t/battery-problem-after-cherry-1-6-update-battery-might-be-dying/
I would be interested if we could issue a bounty for @chrmhoffmann to get him working in the port again?
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showpost.php?p=56379896&postcount=19
I was just thinking the same thing.. maybe using www dot bountysource dot com ?
I too would be very glad to pay and/or to contribute with testing or code in order to get Android 4.3 or 4.4 on my Fairphone.
I need it because of the Low Energy Bluetooth feature, which would enable FP to talk with fitness tracker devices...
Is @chrmhoffmann or anybody else in here still interested in pursuing a full (or at least working) port of CM to FP?
Please note that at present days, there is not defined upgrade path for FP... so this would be quite an effort but also a very nice solution for the future of FP software.
Hi,
has anybody tried to build a custom rom using the SDK provided by Media-Tek?
I've downloaded the four SDK packages granted by Media-Tek. You get the SDK packages only on request from the MediaTek Support, if you are already registred at the MediaTek-Lab.
Kind regards
Hello guys,
Was wondering if people running the new official CM builds could give the rest of the community some overall impressions about the ROM. Specifically, what's working and what isn't, the issues they've faced so far and suitability as a daily driver. In the dev thread the only thing specified as not working is making calls.
The Dev thread is obviously not appropriate for this discussion and I'm eager to migrate from stock to AOSP since the device has long been abandoned by Samsung.
Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.
gooberdude said:
Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.
Click to expand...
Click to collapse
I'm not sure you're responding to the correct thread.
Anyone? Is there a chance the voice calls will work in the future or is it a dead end? Also how well do the cameras work (front and rear)?
Random video issues exist. Colored diagonal lines when using Netflix, Google video, etc. Also glitches sometimes when using various OS functions.
There are two of us with N5110s that have no gps output. Since I use mine for marine charts and the other is used for aviation charts it is more than an inconvenience. Sad to say that the other person (very competent, and specifically something of an expert on GPS) tried to file a bug report about it and was refused!?! Very strange.
What makes this particularly annoying is that the CM12.1 nightlies, very stable for a very long time, were converted to CM13 nightlies without any warning. Imagine my surprise when my occasional update resulted in CM13 booting (with problems) and required a wiping of /data to make it stable. Either a huge warning or a separate line of nightlies would seem appropriate.
Edit: I am also experiencing the occasional video flashing, but it doesn't get in the way of usability.
I am a big fan of CM but it does look like CM13 is still having teething problems.
Greg
The screen flicker issue is still there. Until they do not solve that issue, I cannot comfortably use CM13 on my N5100. I have to stay with CM12.1, and periodically test the nightly releases of CM13, until that bug is completely solved.
Everything else, seems to work fine.
sorry an unrelated question.
is there any cm 12.1 that works fine on n5100 which has fix calling bug.thanks
The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg
CarinaPDX said:
The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg
Click to expand...
Click to collapse
Yes, you are right. The flicker issue is solved in nightly release from May 4, 2016.
I have installed it, and make a backup of both, CM 12.1 and CM 13, to be protected if,
for some reason, something wrong will happen.
A workaround to easily change the USB mode from default, that is charging, to MTP data transfer,
will be usefull when connecting the phone to PC. It is very annoying to go every time to
Settings => Developer Options => Select USB Configuration, and choose the desired mode,
or select mode from drop down menu when you are notified for new USB connection presence.
There are third party applications on Google Play, like "USB for Marshmallow",
but it will be better if a solution to problem will be implemented directly in CM13,
that will set default mode to MTP data transfer.
I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.
parsa.io said:
I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.
Click to expand...
Click to collapse
have you followed Rgib's instructions on the first post of cm13?
Volte
Add volte support for oneplus one for the next official update
After switching to full treble builds, my battery saving location mode is showing me somewhere in Shibuya, Tokyo, Japan, whereas I am currently at Kolkata and have never been to Japan with this device.
Please suggest me something so that I can get back to a "working" battery saving location mode which is necessary for many apps without hogging on the battery.
Update : Now the problem has gone worse, I am not getting a fix at all. The location stays at Shibuya (Tokyo) even in high accuracy mode. I just cannot use GPS anymore. Please help me as it is very necessary to call a cab or ambulance at my location.
I am currently on AEX 5.5. Came clean from stock ZUI through MiFlash.
Nevermind, got the solution here :
https://zukfans.eu/community/threads/howto-fix-gps-issues-and-sim.5908/
I have an Umidigi F1 that has been working very well with multiple GSI roms, but I have never been able to get VoLTE or VoWiFi working on any of them. Everything else seems to be working great right off the bat, with the exception of obvious things like WiFi tethering. I’m currently on Bliss Rom GSI, as it has VoLte and WiFi calling baked in, but placing or receiving a call results in falling back to H or H+ and attempting a WiFi call while in airplane mode results in a failure.
I’m on T-Mobile in the USA and VoLTE and WiFi calling both work on other phones, as well as on the F1 with the stock OS out of the box. I’m in a bit over my head and don’t have a ton of knowledge in the area, but here is what I have tried so far:
1. Installed the ims.apk that is floating around, having no effect when installed as a user app or a system app. I’m assuming there is a chance that the Mediatek chip is the hangup here.
2. Extracted ImsService.apk and WfoService.apk from the stock rom and copied to system (trying both /system/app and /system/priv-app separately) and set permissions accordingly. /app folder has no effect, /priv-app folder results in complete loss of cellular signal.
3. Copied entire folders for ImsService and WfoService which include the apk files in addition to odex and vdex files and set permissions accordingly.
4. Installed the (now defunct) VoEnabler Magisk module, which I believe simply edits the build.prop
5. Attempted to install the two apk files as user apps which results in a failure.
Again, I’m not tremendously knowledgeable in this area, so not sure where to turn next. From all the reading I’ve done, I’m thinking the issue may have something to do with either the build.prop or the vendor img, but I wouldn’t know where to begin with either of those. I could do without the WiFi calling, but VoLTE is fairly important in my area, as 3G & 2G fallback is pretty weak where I am and results in a lot of dropped calls.
Sorry for the length. Any ideas would be greatly appreciated. Thanks in advance.
I'm guessing it's a MediaTek SoC, I don't remember seeing Umidigi putting Qualcomm in any of their phones.
voLTE does not work on any GSI ROMs when installed on any MediaTek device. I've not seen anything about voWiFi with MediaTek phones, so that could be specific to the Umidigi
Thanks for the reply. Unfortunately, I'm starting to think you're right about VoLTE and Mediatek. I was hopeful that I would be able to push a few APKs, edit the build prop, or create some kind of overlay in an attempt to get it working. The latter is clearly way beyond my capabilities, but after using the SP Flash Tool for the first time, I'm now pretty willing to repeatedly brick the device in an attempt to make something work!
It's fairly frustrating as these features work well in the buggy stock rom. Unfortunately all of my digging and reading has turned up a lot of dead ends. I'm not too hopeful, but if anyone has any other ideas, I'd love to hear em.
Thanks
Robbo.5000 said:
I'm guessing it's a MediaTek SoC, I don't remember seeing Umidigi putting Qualcomm in any of their phones.
voLTE does not work on any GSI ROMs when installed on any MediaTek device. I've not seen anything about voWiFi with MediaTek phones, so that could be specific to the Umidigi
Click to expand...
Click to collapse
I would actually guess that it relates to some changes that the GSI makes compared to the stock image. If I'm right, t-mobile likely grants access to base features on its network to any device, yet reserves more advanced features to authorized devices.
I'm like you, however, in that I'm not knowledgeable enough to know for sure. I say this because I'm experiencing a similar issue (same device, the Umidigi F1) with my carrier, Verizon Wireless. Everything is fine on stock ROM but no data or advanced features on AOSP roms (derived by phhusson's work so far). Verizon seems to be stricter with devices on their network, yet I believe our issues have a similar root cause.
Makes sense... I've never used Verizon, but I know it's a bit stickier than T-Mobile and some of the other GSM carriers with regard to unauthorized devices.
I just haven't been able to find a ton of information about these specific issues while using a Mediatek phone. I've randomly moved files from the stock rom over to GSI roms with no luck. Again, in over my head, but I've grabbed anything related to volte or ims from /bin /app /priv-app /framework, etc... and had no luck.
Veiran said:
I would actually guess that it relates to some changes that the GSI makes compared to the stock image. If I'm right, t-mobile likely grants access to base features on its network to any device, yet reserves more advanced features to authorized devices.
I'm like you, however, in that I'm not knowledgeable enough to know for sure. I say this because I'm experiencing a similar issue (same device, the Umidigi F1) with my carrier, Verizon Wireless. Everything is fine on stock ROM but no data or advanced features on AOSP roms (derived by phhusson's work so far). Verizon seems to be stricter with devices on their network, yet I believe our issues have a similar root cause.
Click to expand...
Click to collapse
Hello together,
since I couldn't find anything about that issue in detail beyond the usual vague articles (where one copies the mediocre content from someone else, it seems) such as this one, I'd like to share the following:
Using a SM-F926B which natively came with Android 12 (F926BXXU1BVA9 preinstalled and also after having it updated further to F926BXXS1BVB3), I have the issue that the data connection using 4G(+) (APN-wise and nowadays the lovely internet access of course) although staying connected, doesn't pass any traffic anymore at some point. The small "arrow" in the upload direction is periodically showing up then but nothing in the downstream direction, rendering the whole thing effectively offline, both directly and any tethered device connected to it, which is very annoying. Only quick resolution is to toggle the famous airplane mode.
While it is on one hand appreciated to occur not all the time, it also makes it more difficult to narrow down the error. In conjunction with the German provider O2 it occurred maybe every 1-2 days. During the last time it happened, I had a SMS being sent to the Fold which got successfully delivered so the mobile connection itself stays active (neither does the service monitor available though *#0011# shows anything suspicious) so it seems to be an issue with rather the APN-related connection. A problem with the provider network can be ruled out though as a Netgear LBR20 with another SIM from the same contract runs perfectly fine since ~ 180 days.
Meanwhile I downgraded to Android 11 (F926BXXU1AUJ7) to see if the same error occurs as well, hinting on a hardware issue (a very interesting one then, though as the overall data throughput performance of the Fold 3 is amazing) or some incompatibility with Android 12 (which would then however also raise the question why not all exemplars are affected the same way, which suggests hardware differences even within one model line such as that very F926B).
Has anyone of you experienced that or a similar phenomenon?