yashsingh1/xdaforums huggingface dataset:
[Fairphone 1] simsalonaut:
Here's your magic: Fairphone ClockworkMod Recovery. Backs up all partitions, including data. Just adb it into Fairphone, back up everything to SD card, partition phone, and restore from backup. Done.
[Fairphone 1] Fisher_AZ:
[MENTION=5494566]simsalonaut[/MENTION]: thanks for the suggestion, I hadn't considered going that route. I'm not 100% convinced though that it will be compatible with the planned Fairphone re-partitioning tool. If I understand it correctly, currently the /data partition has 2 subpartitions (labelled "Internal Storage" and "Phone Storage") while after the update there should only be one. My concern is that a recovery-based backup based on partition system X will not restore correctly if the underlying partition system has been changed to Y in the meantime. It might not work, but even worse it might mess things up. [MENTION=5757561]_keesj[/MENTION]: have you done any testing regarding this ?

On a related, but more general note: can anyone point to a decent tutorial/reference explaining the Android partition system ? I have a pretty good understanding of how a Windows-based system partitions a hard drive, but lack a comprehensive understanding of how Android does that (which probably shows in some of my questions).
[Fairphone 1] chrmhoffmann:
Hi,

it doesn't compile. And it seems that the Project configuration has changed (alps/mediatek/config/ahong89_wet_jb2/ProjectConfig.mk). Someone has significantly changed the hardware component settings there (sensors, camera lenses, sound). So I wonder if this is really for the FP1. Maybe it is for the next FP?

Chris
[Fairphone 1] tobwes:
[MENTION=361777]chrmhoffmann[/MENTION]: You're right that the sources as fairphone delivered them don't compile, but it seems that [MENTION=5959593]_tmp[/MENTION] was able to modify them that way that they indeed work. Have a look at the thread Want Mediatek sources? Read this! [Page 3] where you can find more information (one recent post of myself and another hint of [MENTION=5959593]_tmp[/MENTION]).

I agree that it would be better to actually get working sources from fairphone/mediatek but as long as we don't get them I hope that it will be possible to work with these sources and make the best out of it.
[Fairphone 1] _keesj:
Hi,

I have only done normal backup restore while running Android and this indeed lost my settings. After the partition upgrade fuse is used to emulate the phone storage. For a normal user this is great but this depends on Android's fused and therefore the storage is not present in the recovery(we use /cache for this). MTK's recovery has some support for backup/restore in the recovery but this was also not tested(and does require the user to insert an external sd-card)

shell@android:/ $ df

Filesystem Size Used Free Blksize

/dev 487M 52K 487M 4096

/mnt/secure 487M 0K 487M 4096

/mnt/asec 487M 0K 487M 4096

/mnt/obb 487M 0K 487M 4096

/system 639M 351M 288M 4096

/data 13G 503M 12G 4096

/cache 452M 8M 444M 4096

/mnt/cd-rom 1M 1M 0K 2048

/protect_f 8M 4M 4M 4096

/protect_s 8M 4M 4M 4096

/mnt/shell/emulated 13G 503M 12G 4096

/storage/sdcard1 7G 945M 6G 32768

shell@android:/ $ mount

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/emmc@android /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0

/emmc@usrdata /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0

/emmc@cache /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0

/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0

/emmc@protect_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0

/emmc@protect_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0

/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Fairphone 1] MarcoToo:
Why not just modify the partition tables? I just used an ordinary hex editor to screw around with the headers, then manually formatted the 'new' partitions.

What I am trying to say is: if you can automate these steps for the set-it-and-forget-it user it would be much less complex than your current approach sounds to me.
[Fairphone 1] superdragonpt:
Hi

A friend of mine have one of this...

Can you please provide the proper kernel source?

Looking at the one we have acess, there are several build errors (fix them all, but they wont boot on the device itelf) , of course i already know some MTK hacks, and none of them worked on this case.

--> Also you should check under ../mediatek/custom/project/common/ the partition define, does NOT reflect the proper device partition layout.

--> There's an issue with the compiled kernel and the device bootloader (is this the real device source???)

Regards
[Fairphone 1] _keesj:
Hi,

The solution chosen to do the partitioning problem is the FUSE approach. The upgrade is indeed more complex but this is also the solution shipped with FP1 second batch phones (FP1U) . To keep things uniform the partition up grader removes the FAT partition, increases the cache partition (to store updates) and unifies the /data and and internal storage using FUSE. The end result is optimal.

BTW the EBR1/2 format is the same as a normal partition table.

---------- Post added at 11:36 AM ---------- Previous post was at 11:12 AM ----------

We will continue to work on that. The kernel related discussion should be moves to an other thread.

Greetings
[Fairphone 1] _keesj:
Hi,

After all the update will not happen this week but next week. We will need one more round of testing and prepare the users for the update (via a post).
[Fairphone 1] tobwes:
[MENTION=5238428]superdragonpt[/MENTION] The thread [MENTION=5757561]_keesj[/MENTION] was talking about is MediaTek driver sourcecode and [MENTION=5959593]_tmp[/MENTION] managed to do a great job so far in geeting the sources running on his phone. Unfortunately, there seems still to be an issue with the touchscreen, so if you are looking for a starting point, just follow the conversation in that thread (and actually two earlier posts in this thread as well).
[Fairphone 1] superdragonpt:
Just replied there with some infos ..

Regards
[Fairphone 1] _keesj:
Hi,

I got an answer from MTK that the patch did not apply e.g. they do not have a AtPhonebook.java. To get fixes best would be to provide some logs (e.g. logcat with a description of the probem).
[Fairphone 1] joemier:
Outlook on next Fairphone software update (August 2014)

Hi,

I wanted to share our latest news about the next software update. We've just posted an article to our support section here, contents follow:

https://fairphone.zendesk.com/hc/en-us/articles/200849829

Cheers,

Joe

FP Community Manager
[Fairphone 1] _keesj:
If you want to get a preview it zip files can be found here.

For Fairphone OS 1.3 users:

http://storage.googleapis.com/update-v1_6/FP1_Fairphone_OS_1G13G_v1_6_OTA_2014-07-31.zip

After this install the updater will contains a new section called OS library that allows to install the cherry partition upgrader.

For Fairphone OS 1.5 users:

http://storage.googleapis.com/update-v1_6/FP1_Fairphone_OS_v1_6_OTA_2014-07-31.zip

good luck!
[Fairphone 1] Quallenauge:
Thanks for the update! When I connect via adb and getting the logcat, I thought there where much lower log output since this is a mentioned feature of the new firmware version:

Here is some output of

adb logcat

(Note that I/D/V tags are used, means the phone is very verbose...)

D/PowerManagerService( 519): wakeLock.pid= 3931,tag= fingerprint_scanner_local
D/PowerManagerService( 519): wakeLock.pid= 876,tag= RILJ
D/PowerManagerService( 519): updateWakeLockSummaryLocked: mWakefulness=Awake, mWakeLockSummary=0x1
D/PowerManagerService( 519): newScreenState = 2
D/PowerManagerDisplayController( 519): requestPowerState: screenState=2, useProximitySensor=false, screenBrightness=102, screenAutoBrightnessAdjustment=0.0, useAutoBrightness=true, useEcoBrightness=f
alse, blockScreenOn=false, waitForNegativeProximity=false
I/PowerManagerService( 519): setBrightness mButtonLight 0.
D/PowerManagerService( 519): updateScreenStateLocked: mDisplayReady=true, newScreenState=2, mWakefulness=1, mWakeLockSummary=0x1, mUserActivitySummary=0x1, mBootCompleted=true
D/PowerManagerService( 519): handleSandman: canDream=true, mWakefulness=Awake
D/TelephonyManager( 987): getDefaultSim is sim1
D/PowerManagerService( 519): releaseWakeLockInternal: lock=1115409128, flags=0x0
D/ActivityManager( 519): currentAppPid= 2639
D/PowerManagerService( 519): wakeLock.pid= 3931,tag= fingerprint_scanner_local
D/PowerManagerService( 519): updateWakeLockSummaryLocked: mWakefulness=Awake, mWakeLockSummary=0x1
D/PowerManagerService( 519): newScreenState = 2
D/PowerManagerDisplayController( 519): requestPowerState: screenState=2, useProximitySensor=false, screenBrightness=102, screenAutoBrightnessAdjustment=0.0, useAutoBrightness=true, useEcoBrightness=f
alse, blockScreenOn=false, waitForNegativeProximity=false
I/PowerManagerService( 519): setBrightness mButtonLight 0.
D/PowerManagerService( 519): updateScreenStateLocked: mDisplayReady=true, newScreenState=2, mWakefulness=1, mWakeLockSummary=0x1, mUserActivitySummary=0x1, mBootCompleted=true

Note: I'm using the 1.6 preview version updated from the 1.3 version.
[Fairphone 1] fredflegel:
Nice

I think it is a very good idea to announce preview here (and only here) so that some more savy users like we are can test it and reported by issues as we are probably more frustration tolerant and know how to recover our phone from dead :) Thank you! Will have a look at the preview now!
[Fairphone 1] ralf_xda:
I wonder why CVE-2013-6272 was not fixed since it is quite trivial to fix. The bug resides in Phone.apk and allows every app to make unauthorized phone calls and send USSD codes without extra permissions.

--- AndroidManifest.xml.orig 2014-08-01 17:08:16.681903706 +0200

+++ AndroidManifest.xml 2014-08-01 17:08:30.585909698 +0200

@@ -457,7 +457,7 @@

<action android:name="com.android.phone.UPDATE_CALLER_INFO_CACHE" />

</intent-filter>

</receiver>

- <receiver android:name="PhoneGlobals$NotificationBroadcastReceiver" exported="false">

+ <receiver android:name="PhoneGlobals$NotificationBroadcastReceiver" android:exported="false">

<intent-filter>

<action android:name="com.android.phone.ACTION_HANG_UP_ONGOING_CALL" />

<action android:name="com.android.phone.ACTION_CALL_BACK_FROM_NOTIFICATION" />

Reference:

blog.curesec.com/article/blog/35.html
[Fairphone 1] fredflegel:
Preview works fine so far.

I am running the preview since release day now and had now issues so far. I chose to repartition which run smooth and fast enough. As the Updater warned me, i lost all my data. The Fairphone bootet fine afterwards and i enjoy the new space.

After a day, i enabled the device encryption which took a less than an hour (almost no data on the device yet) and that worked as well! Great job!

So my feedback is asolutly positive! And i instantly noticed a small changed detail i liked a lot. I do not want to spoil, so do not mark space following the colon if you want to be suprised!: The new default ringtone is the music from the fairphone videos, very upbeat :D
[Fairphone 1] FlamingoKid:
Just installed the preview and all went smooth. I see the new section OS library, but this does not show the Cherry Partition Upgrader, only two (non-responsive) blocks, called "Fairphone OS" and "Stock Android". Partition scheme is still old school. Are there any extra actions you took?
[Fairphone 1] FlamingoKid:
Did a factory install and used English as language and now the "Fairphone OS" responded to touches. Now I could use the partitioner, works very well. Maybe the language settings was the case or the screen just wasn't responsive, because I clicked to hasty. :eek:
[Fairphone 1] Quallenauge:
Hi!

Indeed, the language has some influence on the functionality. I didn't perform a factory reset but switched to "English" as system language.

At this point I was able to interact with the "Firephone OS" button as well with the "Stock OS" button.
[Fairphone 1] _keesj:
Hello,

We have seen this problem. It happens when updater did not download it's configuration file yet. A reboot (or patience) fixes this . No need to switch to English.
[Fairphone 1] ThommmF:
Not my phone

I got one of the first Fairphones and I was very happy! It looks and feels good.

After a couple of days I decited to sell it to a friend because in many ways it was to slow and small for me.

But still I like the idea and the message!
[Fairphone 1] Fisher_AZ:
Still not sure how to preserve settings through the partition upgrade ...

Sorry for the late response, but it still is not clear to me what the answer is to my original question, which I 'll rephrase for good measure:

CONTEXT: I have a lot of apps with settings fine-tuned, which would cost many hours to set-up again. Therefore, I would like to carry over all these settings through both the OS update and the partition merge. The partition merge will wipe all data, so the procedure would become: 1. backup all apps+settings / 2. update the OS / 3. upgrade the phone storage / 4. restore the apps+settings from backup.

QUESTION: can this be achieved ? (Using an external SD card is no problem)

A. Yes, using (the already included) MTK recovery (as hinted at somewhat by [MENTION=5757561]_keesj[/MENTION]) [Was it tested to work through the partition change ?]

B. Yes, using the Fairphone ClockworkMod Recovery (as suggested by [MENTION=5494566]simsalonaut[/MENTION]) [Was it tested to work through the partition change ?]

C. Yes, using another method [Was it tested to work through the partition change ?]

D. No [Why not ?]

I'm sure a lot of people don't mind much if they loose their app settings, but for me it represents a big hurdle that I would like to avoid if at all possible. I would consider this an important aspect of "sustainability", and I'm sure I'm not alone in that. Hence, a clear answer on A-D would be highly appreciated.
[Fairphone 1] Unrelashade:
Hello, I know what you're talking about as this always annoyed me when flashing new ROMs on my phones. You will find a lot information about this per internet search, like for example how to save your data and restore it and how everything works. However, there is a simple solution for people who just want to get it done without studying everything thoroughly first. However you need root for this. The solution is the app Titanium Backup and it's free in the play store. What it does is, it creates backups of the apps and your personal data and settings and can restore it afterwards. (You can even try it out and make backup of an unimportant app, like a game with a score/ settings saved by you. Then uninstall it and reinstall/ restore data with Titanium Backup (no need for internet connection :) ). It will install the app and restore your data.) It also works if you upgrade your ROM and partition change should be no problem.

Now I get that you want to be sure that it works. However that is not necessary since you can make (and always should!) a complete backup of your phone system (that includes the ROM, Apps and all your data. It includes everything except external storage (SD-card)). It's called nandroid backup. So even if something goes wrong you can always go back to your backup. Make sure that your SD-card has enough storage left for your backup (at least 150 MB).

I can't guarantee that it works, so of course use at your own risk. However both Titanium Backup and nandroid backups always worked for me. Have fun! :)

Also consider (goes for everyone) writing a guide on the xda fairphone wikipage so others will have your help!

http://xdaforums.com/wiki/Fairphone_Fairphone#Guides
[Fairphone 1] Fisher_AZ:
[MENTION=2011059]Unrelashade[/MENTION], thanks for the suggestions. Having root is no problem (Fairphone comes rooted out-of-the-box) but even with the use of apps like Titanium or Helium it still requires a lot of work. As I wrote before:

As for the nandroid backup, if I understand correctly these are made from within recovery. Which brings me back to the question whether either of both available recoveries are compatible with / can cope with the change in partition structure ?
[Fairphone 1] Donat.Callens:
Backup and restore

I did the partition upgrade and used Helium to restore my data from the sd card with great success. It is not that tedious :cool: Be sure to ask it to back up the APK's as well for very easy restore. Some apps won't be backed up (system apps an some others) :crying:. Don't expect to do a full re-installation of an OS without some work!

As per the restore of Nandroid backups: I used Nandroid Manager to restore some applications' data but with much less success :( I guess you need the same storage specifications for that. Having the storage changed between backup and restore made the restore NOK. I had to re-configure those apps manually.

Special mention concerning the popular GravityBox (usefull Xposed Framework app): I was not able to restore my settings. An in-app purchase is available for that if you really need it
[Fairphone 1] JYPDWhite:
Btw for all people as information: the FP1 can handle 128 gb sd cards. Not as mentioned in the wiki only 64 gb.
[Fairphone 1] KaiserEmperor:
Made my backup with Titanium and it was able to restore the settings of almost all Xposed modules. Activated modules, rebooted and everything worked like a charm.

XPrivacy is a problem, see their FAQ here: https://github.com/M66B/XPrivacy?frequently-asked-questions

(5) Can I backup XPrivacy's restrictions, settings, and usage data?

Starting with version 1.11.13, you can no longer backup XPrivacy's data with standard backup tools, such as Titanium Backup. This is because database is no longer stored in the XPrivacy data folder, but in a system folder. I have tried to store the database in the XPrivacy data folder, but this leads to all kinds of permission problems.

Somehow it also seems to have problems with Accounts in some apps. It restored my WhatsApp Acc but wasn't able to do this for Facebook.

Does anyone know what was fixed with the GPS in 1.6? TTFF is still pretty long for me... up to 1 minute with current EPO files.

Thanks!
[Fairphone 1] _keesj:
The NTP server was set to use EU based servers and AGPS was enabled by default. We are still waiting for the EPO download fix.

Can you please describe your test conditions?

When outside with network connectiviy (not even GRPS) I typically get a fix within a few second (and like 15 seconds MAX).
[Fairphone 1] Donat.Callens:
The fix may be sometimes long but it is not as bad as the errors I regularly get. I am considering buying a separate GPS device because of the lack of precision of the one of the FP1. I am regularly mistakenly located on a road 20 meters off the one I am on and the Maps application reroutes me uselessly because of this. It makes the FP1 very useless for GPS. I think the GPS is actually off course when the road turns too much. The maps application anticipates my position based on my speed and thinks I am still going straight on and I get lost on the map...
[Fairphone 1] KaiserEmperor:
Are you wating for MTK to fix the EPO download? Honestly, I don't think this will ever happen ;) MTKs FTP servers have nerver worked for me. Currently I have to download the files (original post by simsalonaut below) manually and cp them to /data/misc via Terminal Emulator since ES file Explorer fails on that. Then I have to chmod 777 those files. Several MTK fix apps (FasterGPS, MT GPS EPO Fix) have not worked for me.

The only fix that I could imagine would be to set up your own FTP servers, and those will crash soon, too.

For the TTFF:

In my room at the window a fix needs about a minute, WiFi enabled. My brother's S4 needs 12 seconds for that.

Outside, with about half the sky visible, the fastest I could get was 17 seconds.

Does AGPS work with WiFi? Both SIMs have GSM connection, but no mobile data since WiFi is connected.

_keesj: Can you tell us if these problems (TTFF, accuracy) are hardware or software related? Since only very few Qualcomm devices have problems like these, I assume it's hardware but an official confirmation would be good.

Sorry for this messed up post! ;)
[Fairphone 1] manu_26:
Since the latest update (1.6), I have weird icons in the play store. Icons with transparency have a black background, which looks really ugly. I already tried to clear the data of the play store app, but that didn't help. Anybody having the same problem?

Btw: I installed using the fairphone updater, used the unified storage installer and then installed google apps using the fairphone widget.
[Fairphone 1] mgkoeln:
I can confirm the black backround - but I probably wouldn't have noticed it without your posting. So, I'm not sure if this came with the update or was there before.
[Fairphone 1] JYPDWhite:
It is not related to the update. I have the same issue here with 1.3 chestnut running.
[Fairphone 1] manu_26:
I definitely got this problem after the update. But maybe it's just the version of the play store app. Depending on when you installed Google apps you might also have gotten the newer play store app. I have version 4.8.20. Maybe someone without the problem can post his or her version.
[Fairphone 1] manu_26:
Uninstalling updates for the play store brings me back to the stock version 4.3.11. That version works fine. But that's not really a solution.
[Fairphone 1] simsalonaut:
It seems to be a bug related to the latest Play Store update.
[Fairphone 1] _keesj:
We might also have other options (like hosting the EPO ourself) but I think it is necessary to also understand that MTK is also trying. I think we will be able to fix this with MTK.

We obviously I have a different experiences I will do some more testing. Having such a "quick" fix also means A-GPS is working. Without you are looking at minutes not seconds

Yes, you can have a look in the A-GPS settings to mare sure it is enabled.

This is very hard to say. With the correct settings I find the GPS usable for what I do (e.g. running). Certainly there must be better GPS receivers on the market that have a real proper antenna and better performance but for a smartphone I think the accuracy is alright.

The accuracy of a pure GPS solution will never be great e.g. being 10 meters next to the actual position is not uncommon and navigation software takes this into account by for example clamping you to the road and predicting your position based on our last position and velocity.
[Fairphone 1] _keesj:
GPS accuracy

To make things a little more tangible I did a ride in the car. I installed osmtracker (from the f-droid repository) on 4 Fairphones and one Galaxy SII

http://www.mygpsfiles.com/app/#DgLGaXXF

You can compare the tracks against each other and the Galaxy SII.
[Fairphone 1] Unrelashade:
Just change that, that is the purpose of a wiki! :) I've gone ahead and did it.
[Fairphone 1] haiag:
Hey [MENTION=2438866]keesj[/MENTION]

Last time, when using my FP in the car and having GPS fixed, when putting in the charger to the cigarette lighter it lost the gos signal after approx. 30 sec, when disconnecting it found it again.

I tried it 2-3 times.

Anyone else can confirm this?
[Fairphone 1] fredflegel:
Yery good idea! What i think is interesting is the difference in elevation in Fairphone and S2. It would be great to include a pro gps device in the comparison to see which device is more correct.
[Fairphone 1] haffenloher:
Mediatek's GPS usually provides wrong elevation data if I'm not mistaken, so probably the S2 is more correct. See also xdaforums.com/wiki/Fairphone_Fairphone/Guides#How_to_fix_location_issues