<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with vollaphone]]></title><description><![CDATA[A list of topics that have been tagged with vollaphone]]></description><link>https://forums.ubports.com/tags/vollaphone</link><generator>RSS for Node</generator><lastBuildDate>Sat, 16 May 2026 09:10:18 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/tags/vollaphone.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 01 Nov 2022 15:57:01 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Bluetooth not working on Volla 22]]></title><description><![CDATA[@muskist thank you anyway. Hopefully it'll be working when 20.04 will be relesed.
]]></description><link>https://forums.ubports.com/topic/8259/bluetooth-not-working-on-volla-22</link><guid isPermaLink="true">https://forums.ubports.com/topic/8259/bluetooth-not-working-on-volla-22</guid><dc:creator><![CDATA[D-9]]></dc:creator><pubDate>Tue, 01 Nov 2022 15:57:01 GMT</pubDate></item><item><title><![CDATA[Volla phone touch screen freeze.]]></title><description><![CDATA[Hi, having the same problem on my device since OTA 23, I would like to share the following observation: My screen freezes like after every two-three ticks. I have to lock the scree and unlock it and then it will work again for some more ticks before freezing again. So I started uninstalling kind of nearly all the apps (I have the green light to send it to Volla). After uninstalling nearly everything, my Volla worked better. But it  did not last for long, because I needed to reinstall some apps for daily use (I use it as my only phone). Now, I see two options: Total reset by Volla or wait for OTA 24. Any other ideas?
]]></description><link>https://forums.ubports.com/topic/7823/volla-phone-touch-screen-freeze</link><guid isPermaLink="true">https://forums.ubports.com/topic/7823/volla-phone-touch-screen-freeze</guid><dc:creator><![CDATA[Jan 1]]></dc:creator><pubDate>Sat, 18 Jun 2022 04:15:00 GMT</pubDate></item><item><title><![CDATA[No caller id on outgoing calls (Volla phone)]]></title><description><![CDATA[@applee Thank you very much, it works now perfectly thanks to this.
]]></description><link>https://forums.ubports.com/topic/6535/no-caller-id-on-outgoing-calls-volla-phone</link><guid isPermaLink="true">https://forums.ubports.com/topic/6535/no-caller-id-on-outgoing-calls-volla-phone</guid><dc:creator><![CDATA[Lundrin17]]></dc:creator><pubDate>Thu, 05 Aug 2021 20:38:52 GMT</pubDate></item><item><title><![CDATA[Network Providers (O2) &amp; the Volla Phone in the UK]]></title><description><![CDATA[@domubpkm That's a good question, I didn't think to test that when I wrote my last post.
It seems to not accept MMS messages, I've yet to send one (It's been so long since I've used an OS that actually supports MMS that I've gotten out of the habit of using it), but as it doesn't accept them I doubt it will send them either.
So, to clarify my point more. As of July 2021 the Volla Phone can:

Send and receive phone calls
Voice mail works
Mobile data works (2G, 3G and 4G all tested)
MMS doesn't work

On O2 in the UK.
]]></description><link>https://forums.ubports.com/topic/6198/network-providers-o2-the-volla-phone-in-the-uk</link><guid isPermaLink="true">https://forums.ubports.com/topic/6198/network-providers-o2-the-volla-phone-in-the-uk</guid><dc:creator><![CDATA[AdLinux]]></dc:creator><pubDate>Sat, 22 May 2021 08:24:27 GMT</pubDate></item><item><title><![CDATA[Fairphone 3+ vs Volla Phone vs ?????]]></title><description><![CDATA[@stanwood Yes. When to check or uncheck which boxes, this needs to be clarified. But if a choice in one box must be compulsatory linked to an option in another box, this must be automated i think again.
]]></description><link>https://forums.ubports.com/topic/6184/fairphone-3-vs-volla-phone-vs</link><guid isPermaLink="true">https://forums.ubports.com/topic/6184/fairphone-3-vs-volla-phone-vs</guid><dc:creator><![CDATA[domubpkm]]></dc:creator><pubDate>Wed, 19 May 2021 20:29:03 GMT</pubDate></item><item><title><![CDATA[device-mapper crypto not working on Volla Phone]]></title><description><![CDATA[Replying to myself, I started reading in the original Volla phone kernel sources.  Looking at dm-crypt.c it seems that it has patches that add some very specific (and broken) hacks to accommodate Mediatek hardware encryption (everything that depends on CONFIG_MTK_HW_FD which is set on the Volla's phone kernel).
This function seems to be the culprit.  It escapes me how anybody could throw this kind of hack into a production kernel:
/*
 * MTK PATCH:
 *
 * Get storage device type (for hw fde on/off decision)
 * or id (for crypt_config).
 *
 * Returns:
 *   0: Embedded storage, for example: eMMC or UFS.
 *   1: External storage, for example: SD card.
 *  -1: Unrecognizable storage.
 */
static int crypt_dev_id(const char *path)
{
	int type = -1;

	if (strstr(path, "bootdevice")) {

		/* example: /dev/block/platform/bootdevice/by-name/userdata */
		type = 0;

	} else if (strstr(path, "externdevice") || strstr(path, "vold")) {

		/* example: /dev/block/vold/private:179,2 */
		type = 1;
	}

	pr_info("[dm-crypt] dev path: %s, type: %d\n", path, type);

	return type;
}

So whenever you are trying to device-map some block device that does not have any of the substrings "bootdevice" or "vold" or "externdevice" in them, this returns -1, which in turn will break any attempts to use such a device in the device-mapper, thanks to the over-strict check added in crypt_ctr():
	cc-&gt;id = ret = crypt_dev_id(argv[3]);
	if (ret &lt; 0)
		goto bad;

Note how e.g. any loop device /dev/loop* will thus fail.  However, this also allows a workaround.  We just use a different name (with the same major/minor device numbers) that matches 'externdevice'.  This way dmsetup will magically start working:
cp -a "${LODEV}" /dev/externdevice1
echo "0 128 crypt aes-ecb 0123456789abcdef0123456789abcdef 0 /dev/externdevice1 0" |  dmsetup create crypt2

However, I am not sure whether this kind of workaround could be applied to 'cryptsetup'.
This really destroys any illusion WRT to code-quality of the kernels that is running the Volla phone.
]]></description><link>https://forums.ubports.com/topic/6076/device-mapper-crypto-not-working-on-volla-phone</link><guid isPermaLink="true">https://forums.ubports.com/topic/6076/device-mapper-crypto-not-working-on-volla-phone</guid><dc:creator><![CDATA[Dave]]></dc:creator><pubDate>Sun, 25 Apr 2021 14:51:01 GMT</pubDate></item><item><title><![CDATA[Apply keyboard dictionary]]></title><description><![CDATA[@applee
At least I can export the dictionary as text file..
]]></description><link>https://forums.ubports.com/topic/6008/apply-keyboard-dictionary</link><guid isPermaLink="true">https://forums.ubports.com/topic/6008/apply-keyboard-dictionary</guid><dc:creator><![CDATA[ratte]]></dc:creator><pubDate>Sat, 10 Apr 2021 06:17:17 GMT</pubDate></item><item><title><![CDATA[Link to vollaphone ubuntu touch image file?]]></title><link>https://forums.ubports.com/topic/5846/link-to-vollaphone-ubuntu-touch-image-file</link><guid isPermaLink="true">https://forums.ubports.com/topic/5846/link-to-vollaphone-ubuntu-touch-image-file</guid><pubDate>Tue, 09 Mar 2021 18:46:47 GMT</pubDate></item><item><title><![CDATA[LTE, UBports OTA-15 and Vollaphone]]></title><description><![CDATA[Hi @ubtouch-newbie , I'm also currently in the process of setting up a Volla phone under ubports.  Just for clarity, can you describe the exact method by which you factory-reset your phone?  Did you just do System Settings -&gt; Reset or something more advanced?  Asking just in case I encounter a similar problem.  I've only verified working phone-calls and the wifi so far.
Dave
]]></description><link>https://forums.ubports.com/topic/5636/lte-ubports-ota-15-and-vollaphone</link><guid isPermaLink="true">https://forums.ubports.com/topic/5636/lte-ubports-ota-15-and-vollaphone</guid><dc:creator><![CDATA[Dave]]></dc:creator><pubDate>Tue, 02 Feb 2021 12:49:46 GMT</pubDate></item></channel></rss>