[ROM][UNOFFICIAL] CyanogenMod 12 Nightly Builds / OpenDesireProject

[kchaisu]

Presumably, CM-12 build has been scheduled to weekly update on Saturday. Thanks, Mustaavalkosta.

 

[Aizotech]

Is anyone else experiencing microphone problems in call? It works sometimes but far from always. Everything else is really good with this rom though so I wonder if there's a fix for this? I think it's a problem with the dialer app.

Sent from my Desire S using Tapatalk

 

[ralfbergs]

CM12.1 and F2FS?

Hi guys.

Sorry that I have been silent for so long time, but I simply couldn't spend any time on this project due to personal and business reasons.

Now that I'm back I'm really very happy about the progress you made. Congrats to all involved!!!

I just tried to install today's (JUL-20) CM12.1 build, and as a prep I upgraded TWRP to 2.8.6.1. I converted my partitions to F2FS, and in the beginning it seemed it could work, but after correctly determining the FS type as "F2FS" for .../by-name/system only two lines later I noticed that it was suddenly "detected" as ext4?!

Why is this? Does the CM12.1 image not support F2FS for /system? (/data and /cache are on F2FS, but not /system, it's still on ext4... Otherwise everything seems to work fine...)

Thanks in advance for your help.

Kind regards,

Ralf

 

[kchaisu]

Just data and cache could be use on f2fs.

Sent from my Desire S using Tapatalk

 

[ralfbergs]

Just data and cache could be use on f2fs.

Thanks.

Do we know why this is?

I know that with CM12.1 for the S4 /system can also be on F2FS, so it seems it could be a limitation of our build?

 

[Mustaavalkosta]

Thanks.

Do we know why this is?

I know that with CM12.1 for the S4 /system can also be on F2FS, so it seems it could be a limitation of our build?

fstab is missing dual entries for system partition. OS side is likely fine if other devices can do F2FS on system partition. I can probably add the fstab entry.

 

[ralfbergs]

fstab is missing dual entries for system partition. OS side is likely fine if other devices can do F2FS on system partition. I can probably add the fstab entry.

Hi Mustaavalkosta, why do we not just try this?

If you're willing to do it, please let me know when I can test, and I will then report my findings here.

Thanks!

---------- Post added at 11:07 ---------- Previous post was at 10:24 ----------

Hi @Mustaavalkosta.

Now that I'm playing around w/ that build for some hours I must say I'm very impressed with how stable and mature it is. Even the frontcam is working properly...

Thanks much, we're getting there!!!

KR,

Ralf

 

[ralfbergs]

CM12.1: OTA update to 20150721

@Mustaavalkosta, all:

I just updated via FOTA to the latest nightly, and boy, I. Am. Impressed.

Everything worked very smoothly, no hicup. CM automatically booted into recovery, non-interactively installed the new flash image, rebooted back into the system. The usual ODEX'ing ("Optimizing apps") took place on reboot, and then I was back in CM, but in the updated build...

Amazing stuff, guys. Thanks to all who made this possible!!!

Best,

Ralf

 

[Mustaavalkosta]

Hi Mustaavalkosta, why do we not just try this?

If you're willing to do it, please let me know when I can test, and I will then report my findings here.

Thanks!

Actually this is more complicated with system partition because it's formatted with zip flash thus filesystem is kind of hard-coded in updater-script. I don't think it will be as simple as just adding dual fstab entries and I couldn't find any official CM devices with such entries either. It might be possible to switch it to either EXT4 or F2FS at build time but it would still be hard-coded to one of those and not be dynamic like cache/data partitions.

I'm not sure how it behaves with block-mode flashing but we are still using legacy way of flashing.

 

[ralfbergs]

Actually this is more complicated with system partition because it's formatted with zip flash thus filesystem is kind of hard-coded in updater-script. I don't think it will be as simple as just adding dual fstab entries and I couldn't find any official CM devices with such entries either. It might be possible to switch it to either EXT4 or F2FS at build time but it would still be hard-coded to one of those and not be dynamic like cache/data partitions.

I'm not sure how it behaves with block-mode flashing but we are still using legacy way of flashing.

Thanks, I understand (or at least a bit).

I think I will ask the S4 guys for advice, maybe they can give me some hints which you could then consider in one of the next builds? I think it could be helpful to have F2FS even for /system...

 

[Mustaavalkosta]

Thanks, I understand (or at least a bit).

I think I will ask the S4 guys for advice, maybe they can give me some hints which you could then consider in one of the next builds? I think it could be helpful to have F2FS even for /system...

Yeah, that might be helpful if they have some hints as I'm having some personal issues AFK limiting my time spent with this project.

If you mean SGS4 with S4, official CM device tree is only supporting F2FS for cache and data partitions: https://github.com/CyanogenMod/android_device_samsung_jf-common/blob/cm-12.1/rootdir/etc/fstab.qcom

 

[ralfbergs]

Yeah, that might be helpful if they have some hints as I'm having some personal issues AFK limiting my time spent with this project.

I know exactly what you're talking about... As I was "away" myself for 3 months...

If you mean SGS4 with S4, official CM device tree is only supporting F2FS for cache and data partitions: https://github.com/CyanogenMod/android_device_samsung_jf-common/blob/cm-12.1/rootdir/etc/fstab.qcom

I'm using this one:

http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696

 

[Mustaavalkosta]

I'm using this one:

http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696

Yeah, they have dual entries for system too: https://github.com/JDCTeam/android_device_samsung_jf-common/blob/opt-cm-12.1/rootdir/etc/fstab.qcom

I guess I can add that and let's see what happens. I checked updater-script and it's actually using F2FS for data partition with hard-coded value so the filesystem detection is apparently somewhere else and maybe there is support for F2FS on system partition too so it won't be reformatted to EXT4 on zip flash. Dunno.

 

[ralfbergs]

I guess I can add that and let's see what happens.

Please do. I will check it out then...

 

[ralfbergs]

Please do. I will check it out then...

Not sure whether you modified something already, @Mustaavalkosta. I just tried it in 20150726, and /system was still reformatted to ext4. So either you haven't done anything yet, or if you did it wasn't successful.

 

[Mustaavalkosta]

Not sure whether you modified something already, @Mustaavalkosta. I just tried it in 20150726, and /system was still reformatted to ext4. So either you haven't done anything yet, or if you did it wasn't successful.

Nah, I haven't done anything yet. It's easy to try out on ace too once I get to cooking up a build with necessary changes. Results will be clear even without booting it up.

 

[kenkitt]

Hi guys, sorry but i'll have to post this here. I'm trying to activate the framebuffer console for Htc Desire S. If you are a dev and know something about how to do this please help out.
I created a post and it seems no ones interested.
I've tried contacting some devs but am yet to hear from them.
If you know something please checkout http://forum.xda-developers.com/htc-desire-s/general/how-to-enable-famous-frame-buffer-t3168143
Thanks in advance .

 

[ralfbergs]

I'm trying to activate the framebuffer console for Htc Desire S. If you are a dev

I'm not a dev, so I can't help (apart from maybe testing), but I think your mod would be very helpful investigating boot failures and such, so I appreciate very much that you're working on this.

Thanks!

 

[Mustaavalkosta]

Thanks.

Do we know why this is?

I know that with CM12.1 for the S4 /system can also be on F2FS, so it seems it could be a limitation of our build?

Well, F2FS on system partition works, kind of. F2FS reserves more disk space than EXT4 for filesystem internals which pretty much means installation with F2FS is too tight for gapps to fit in (19MB free with test build and no gapps).

System freshly formatted:

• EXT4: 540MB free
• F2FS: 437MB free

I think I will leave it out just because it's not that viable feature to use and will cause confusion if user formats system to F2FS and tries to install gapps (which necessarily won't error out).

 

[ralfbergs]

I think I will leave it out just because it's not that viable feature to use and will cause confusion if user formats system to F2FS and tries to install gapps (which necessarily won't error out).

Absolutely agree. Thanks for testing!