yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] i23098:
I was referring to the zip with the rom...

You can check the original cm 12.1 instructions. Basically:

On a computer, ensure your sd card has only one partition, formated with ext4. You can use gparted, for instance.

You can try and flash 2.8.7.1 recovery.

Reboot to recovery even if you are already in TWRP.

Ensure partition is ok by under Advanced wipe choosing data partition > Repair or Change File System > Change File System > EXT4

Wipe everything under Advanced wipe.

At this point your sdcard is completely empty so you will need to move the ROM zip and any additional zips into sdcard or use adb sideload.

Install cm-13.0-XXXXXXXX-UNOFFICIAL-sagaopt.zip (at the moment, cm-13.0-20151226-UNOFFICIAL-sagaopt.zip) and gapps.
[HTC Desire S] jokergermany:
Thanks, this recovery works!
[HTC Desire S] kchaisu:
I don't realize that there are two builds on holidays. Thank you very much Kylon and Mustaavalkosta for your kind contributions. Happy Holidays every one.
[HTC Desire S] ralfbergs:
2 y/o vulnerability not fixed?

[MENTION=3334728]kylon[/MENTION], [MENTION=3382363]Mustaavalkosta[/MENTION]:

We seem to be vulnerable to a bug found more than two years ago, according to this tool. I ran this on 2015-12-27, and it failed on one test, CVE-2013-6282. Please also see attached screenshots.

I also ran this tool on some other CM13 or AOSP "M" builds for other devices, and they were all "safe."

Can you please check whether the tool is wrong, or whether we for whatever reason use unpatched source?

Thanks a lot.

Best,

Ralf
[HTC Desire S] Mustaavalkosta:
Yeah, sure when I get back. Nice catch!
[HTC Desire S] i23098:
I did tried removing the latest commit (git reset --hard HEAD^) and adding the return 1; and it boots :D This time I even have phone network :victory:
[HTC Desire S] Mustaavalkosta:
Nice because my dual-boot is still b0rked! :)

build/core/main.mk:1008: *** missing separator. Stop.

It seems the builds stopped after the last build repo merge. Dunno what's up. I'm looking into it a bit now.

Edit: It was just a small mishandling of makefile's obsession to be tab vs. spaces sensitive and I guess while fixing merge conflict your editor had input spaces when makefile requires tabs to function. I don't like forcefully overwrite git branches at all because it makes tracking changes impossible but on this occasion it seemed like a only way to fix it without any manual labour with text editor. Sorry about that since it was your work that was forcefully overwritten. I reverted our openjdk hack so the upstream HEAD would merge without conflicts thus avoiding any need for manual intervention. It looks like build repo doesn't care about JDK vendor too much anymore.

Yeah, I actually have EFI MB but I think it's even more messy when it comes to dual-boot. Arch Linux's bootloader wiki/guide is a huge pile of confusion with GPT/MBR and BIOS/UEFI. It used to be easy with grub. Now I have had to use syslinux to get it even work at all. Anyways, wrong forum for Linux headaches. :D
[HTC Desire S] 0lvin:
Everything looks correct, i don't know what wrong with it. I have rechecked all commits with desire hd, so i don't have ideas for now.
[HTC Desire S] kylon:
Ah, sorry about that

My nano is set to use tabs, i ll look into this.

Do we still need the build fork?
[HTC Desire S] Mustaavalkosta:
No worries. Yeah, we need this still due to prebuilt blobs not being PIE compatible and that situation is unlikely to change. :(

https://github.com/OpenDesireProject/android_build/commit/710550ba4b4a9844d26d86bb431a0ae2ac6cb851
[HTC Desire S] 0lvin:
Do you can commit your changes to some repository(for be on same page :) )? If you want i provide you rights for my repository.

Also can you try to move "return 1;" further as you can in early_init_dt_scan_chosen?

Best case when you put "return 1;" after early_init_dt_check_htc_board and check all "if's" by but return after each "return".

I suppose maybe we have issue\mistake with early_init_dt_check_for_initrd. If it is true - "return 1" before check_for_initrd works, but with return after check_for_initrd does not.
[HTC Desire S] i23098:
Yep, that's exactly what happens (making the changes without the last commit in the android_kernel_htc_msm7x30)

Edit: Made a bit more experiments, and commenting out the call to early_init_dt_setup_initrd_arch it is working. Could not find that function to try and see how far can it process...

---------- Post added at 11:33 PM ---------- Previous post was at 10:58 PM ----------

Created a fork of your project in github to track any other changes you might want me to try.

As I said previously, I had to git reset --hard HEAD^ before doing the changes, as with the most recent code, it won't even successfully start the boot process (shows HTC logo, blank screen, then reboots)
[HTC Desire S] kchaisu:
For the last two builds, 20161018 and 20161019, I could not make up clean installation, failed to detect wifi and setup google account. So I used ODA update by download both the ROM and MD5 files to cmupdatter directory and update. However, wifi setup button still grey out. Thanks.
[HTC Desire S] nijawang:
Same failed to detect wifi issue with aceopt 20161019 build.
[HTC Desire S] kylon:
Wifi should be working again on today nightly
[HTC Desire S] kchaisu:
Thank you very much Kylon for your kind contribution.
[HTC Desire S] kchaisu:
Still the same as previous build, 20161020 is no wifi function as well. Thanks
[HTC Desire S] kylon:
Again, wifi should be fixed in tomorrow nightly.

Is the bluetooth working?
[HTC Desire S] kchaisu:
No, it is not working. Thanks.
[HTC Desire S] 0lvin:
Good to know :) I will add little more debug code for get real values for initrd position, it looks like atag -> dts conversion works not perfectly;)

Image for check: boot-saga-1d0504a.img , please check it by : fastboot boot boot-saga-1d0504a.img && adb shell dmesg > dmesg.txt - i need lines with: "must be initrd_start ..." and "initrd_start...."
[HTC Desire S] nijawang:
--------------

20161021 aceopt always reboot with htc logo, could not enter system.

I think sagaopt should have the same issue.
[HTC Desire S] kchaisu:
Back to normal with 20161021 build; wifi is working now. However, BT is still not working. Thank you very much Kylon, Mustavaalkosta, and your teammates for kind contribution.
[HTC Desire S] Mustaavalkosta:
Baud rate was dropped from 4000000 to 3000000 in the fix commits. Not sure if it has anything to do with BT not working but might be something that is HW depended and should be left at 4000000.

https://github.com/OpenDesireProject/android_device_htc_aceopt/blob/cm-13.0/bluetooth/vnd_ace.txt#L5

https://github.com/OpenDesireProjec...agaopt/blob/cm-13.0/bluetooth/vnd_saga.txt#L5

I didn't commit a change yet so the ones who have been involved with this can give input for the baud rate issue if they have any.
[HTC Desire S] kylon:
Do a full wipe

We should ask this to [MENTION=842726]bastei[/MENTION].
[HTC Desire S] bastei:
I don't have the device at hand at the moment, but I hope I can still help.

It actually worked for me with the baud rate of 3000000.

I think the problem could be something else. Am I right in assuming that you build the userdebug flavor? Because in my change the bluetooth module is only installed in eng:

https://github.com/OpenDesireProject/android_device_htc_sagaopt/blob/cm-13.0/bluetooth/Android.mk#L9

Sorry, that should be corrected to user. I hope it works afterwards.

By the way: It actually worked for me without your last wifi fix.
[HTC Desire S] Mustaavalkosta:
Yeah, I suppose we could change that setting to "optional" and build it from PRODUCT_PACKAGES variable thus retaining control over building BT module while making it a bit more flexible.
[HTC Desire S] 0lvin:
Image for check

[MENTION=5313896]i23098[/MENTION] Please check image from http://xdaforums.com/showpost.php?p=69232621&postcount=395 .. ;)
[HTC Desire S] i23098:
Sorry, missed it...

Here it is:

[ 0.000000] must be initrd_start=0x5400000 initrd_end=0x54d66b9
[ 0.000000] initrd_start=0x5400000 initrd_end=0x54cfdc9
[HTC Desire S] i23098:
Hi, today's changelog has

project device/htc/aceopt/
837850d aceopt: bt: return to previously used baud rate

but no equivalent for sagaopt :confused: is this intended?

I haven't tried the latest builds, I usually update once a month or so, when things seem stable enough :) just wondering... Btw, anyone testing newer builds? How's bluetooth going on our device?
[HTC Desire S] 0lvin:
Could you please try commit...
[HTC Desire S] kchaisu:
It is not working. Thanks.
[HTC Desire S] Mustaavalkosta:
Well, yes and no. If that fixes ace and saga is still broken with different baud rate, then it would be wise to try the same change for saga too. I didn't have time today to verify if anything has changed regarding BT after switching to old baud rate so I don't know and no one has said anything in ace forum. I'll see if I have time tomorrow to test run a build myself with old baud rate.
[HTC Desire S] i23098:
I checkout out branch initrd-check, build and it boots :good: dmesg attached...
[HTC Desire S] 0lvin:
next step

Thank you :)

Please try such commits(updated devicetree-rebuild brunch).
[HTC Desire S] i23098:
HTC logo, followed by black screen :crying: Tried dmesg out of curiosity and it worked, some issue initializing graphic card

[ 5.234497] >command 'write /proc/1/oom_score_adj -1000' (/init.rc:19)
[ 5.234558] no graphics
[ 5.234588] troubles with framebuffer
[ 5.234710] >command 'restorecon /adb_keys' (/init.rc:22)
[ 5.234771] no graphics
[ 5.234802] troubles with framebuffer
[ 5.234863] init: SELinux: Could not get canonical path /adb_keys restorecon: No such file or directory.
[ 5.234924] >command 'mount debugfs /sys/kernel/debug /sys/kernel/debug mode=755' (/init.rc:24)
[ 5.234985] no graphics
[ 5.234985] troubles with framebuffer
[ 5.235260] >command 'start ueventd' (/init.rc:26)
[ 5.235321] no graphics
[ 5.235321] troubles with framebuffer
[ 5.235534] init: Starting service 'ueventd'...
[ 5.236083] >command 'chmod 666 /proc/cmdline' (/init.htc7x30.rc:6)
[ 5.236175] no graphics
[ 5.236175] troubles with framebuffer
[ 5.236572] >command 'wait_for_coldboot_done' ((null):0)
[ 5.236633] no graphics

Attached dmesg file...
[HTC Desire S] 0lvin:
Looks as issue related to:

[ 3.724700] zram: Created 1 device(s) ...
[ 3.724853] pmem: pmem_setup: unable to register pmem driver(pmem) - zero size passed in!
[ 3.724884] android_pmem: probe of android_pmem.0 failed with error -1
[ 3.724975] pmem: Initializing pmem_adsp (user-space) as non-cached
[ 3.725402] pmem_setup: allocating PMEM region from hard-coded address.
[ 3.725433] allocating 31457280 bytes at (null) (2c300000 physical) for pmem_adsp
[ 3.726257] i2c-core: driver [isa1200] using legacy suspend method

I will look to code base.....
[HTC Desire S] vgm_ua:
Hello,

i have a problems with keyboard and google play service stop too.

What should I do with file f2fs-ksigned.zip?

How to flash this kernel?
[HTC Desire S] kchaisu:
Please take a look at post #21, it might be a solution there. Thanks.
[HTC Desire S] kchaisu:
I have been unable to access the download website for the whole day. It has been originally unable to access the OpenDesireProject.Org website from yesterday but Codefire website could be accessing by yesterday. It is just for notifying. Thanks.
[HTC Desire S] Mustaavalkosta:
Hmm, looks like the server answers to ping but HTTP and SSH is quite dead. I'll see if something can be done from the VPS web management.

Edit: Reboot seems to have fixed whatever was wrong with it. You should be able to access opendesireproject.org sites again.
[HTC Desire S] kchaisu:
Thanks Mustavaalkosta for your kind contribution. So far all the download mirrors are working. Thank you very much.
[HTC Desire S] kchaisu:
For the record,the 20161104 build is a unique build on fast setup time in comparison to previous and later builds. Thanks Kylon, Mustavaalkosta and other team members for your kind contribution.
[HTC Desire S] mumuni:
When would our device get Android 7.0 Nougat
[HTC Desire S] 0lvin:
Could you try to boot with commit?

And try to compare dmesg with last commit(87050d4bcf279e3c66094d187369f40e8dc3dedd) and last commit where device booted without issues with gpu.
[HTC Desire S] i23098:
Doesn't initialize screen too :( although looking at dmesg, there's a different error...

[ 3.590179] saga_init_panel: Panel not yet supported (0)

Full dmesg attached...
[HTC Desire S] i23098:
Can't do it today, but I'll might try revert one commit at a time tomorrow evening.
[HTC Desire S] lingowistico:
What is the difference between "SagaOpt" and "Saga"?

I thought it was the same device until I got this message in 4Ext Recovery:

"This package is for device sagaopt: this device is saga".

So there's no CM13 for Desire S 510e?
[HTC Desire S] ralfbergs:
Sagaopt uses a different filesystem layout: what was /data is now /system (because it's larger), and /data is your external SD card.
[HTC Desire S] lingowistico:
Oh, I see. What is the simplest way to achieve this (and reverse it)?
[HTC Desire S] kchaisu:
Connection time out, an error on download sites have been com back again. Thanks.
[HTC Desire S] Mustaavalkosta:
dl.opendesireproject.org seems to work just fine here. I just downloaded a zip file and there's nothing wrong with it. Maybe it was something temporary or regional issue.
[HTC Desire S] lingowistico:
Hey guys, could you help me out?

What is the simplest way to convert Saga into SagaOpt? Is there a guide somewhere?
[HTC Desire S] kchaisu:
Please take a look in the first page of this thread. Thanks.
[HTC Desire S] lingowistico:
If you're talking about this:

Then that doesn't work. TWRP 2.8.7.1 for SagaOpt doesn't recognize any sd card that I've tried.
[HTC Desire S] i23098:
Have you converted your card to ext4? I find it better to prepare it first in a PC...

You can check the original cm 12.1 instructions. Basically:

On a computer, ensure your sd card has only one partition, formated with ext4. You can use gparted, for instance.

You can try and flash 2.8.7.1 recovery.

Reboot to recovery even if you are already in TWRP.

Ensure partition is ok by under Advanced wipe choosing data partition > Repair or Change File System > Change File System > EXT4

Wipe everything under Advanced wipe.

At this point your sdcard is completely empty so you will need to move the ROM zip and any additional zips into sdcard or use adb sideload.

Install cm-13.0-XXXXXXXX-UNOFFICIAL-sagaopt.zip and open gapps.

---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------

Hi Mustaavalkosta, I know you said that you probably won't pick up Android 7.0 :crying:

But... what about 7.1 :confused: :silly:

"CM14.1 nightly builds (based on Android 7.1)" will start tonight... Just so you know ;) There's always hope :fingers-crossed:
[HTC Desire S] lingowistico:
Thanks alot.

About gapps, is it only me or is it like that for you too? That Gapps in cm12.1 slows down the device significantly?
[HTC Desire S] i23098:
Don't know if it is gapps to blame, but cm12.1 (haven't tried for way too long, really) and cm13 are a bit slow in our device :( Sometimes it is working fine, then it stalls for a while... :rolleyes: I guess it's just that our device is showing it's age... :(

Maybe CM14 will improve it :silly: (if someone builds it for us ;))
[HTC Desire S] lingowistico:
Ok, well that's good to hear. That it's not just me doing something wrong. Just wanted to make sure that I'm not missing out on anything.

Thank you, once again, for the reply. :highfive:
[HTC Desire S] i23098:
I was going back in the commits in the devicetree-rebuild branch, and it boots when I'm at commit 6c565e0, meaning 2e8c0eb is to blame...

You can find attached dmesg of successful boot with 6c565e0
[HTC Desire S] i23098:
I'm not really sure what to look at :confused: Tried to look into it...

In failed one we have:

[ 0.000000] [dt]panel_type = 0x400010

[ 3.542816] ram_console: found existing buffer, size 1048564, start 518454

[ 3.577178] BD_ADDRESS=00:00:00:00:00:00

[ 3.590179] saga_init_panel: Panel not yet supported (0)

in the one that works, we have:

[ 0.000000] [dt]panel_type = 0x400010

[ 3.647033] ram_console: found existing buffer, size 191672, start 191672

[ 3.671020] BD_ADDRESS=64:a7:69:8e:ef:d3

[ 3.684173] saga_init_panel is sony panel: 4194320

[ 4.078399] sonywvga_probe: id=0
[ 4.078399] lcdc_config_gpios: power goes to 1
[ 4.078430] panel_sony_power: 1
[ 4.113128] Registered led device: lcd-backlight
[ 4.113159] display_sysfs_init : kobject_create_and_add
[ 4.113189] display_sysfs_init : sysfs_create_file
[ 4.114135] setting pdata->panel_info.fb_num to 3. type: 3
[ 4.119354] FrameBuffer[0] 480x800 size=2310144 bytes is registered successfully!
[ 4.119720] mdp4_lcdc_vsync_init: ndx=0

(the last block has no equivalent in the one that fails)

Hope it helps :)
[HTC Desire S] linqdesires:
is headset mic bug confirmed please? is not working? thank you
[HTC Desire S] 0lvin:
Possible fix?

Lets try with such fix.
[HTC Desire S] mproshkin:
Hi, just curious, any chance to move to 14.1?

ÐžÑ‚Ð¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¾ Ñ Ð¼Ð¾ÐµÐ³Ð¾ Pixel XL Ñ‡ÐµÑ€ÐµÐ· Tapatalk
[HTC Desire S] i23098:
Panel initializes correctly :good: but then the phone doesn't boot :crying: Stays with the blue face forever... You can find dmesg attached.
[HTC Desire S] i23098:
Hi, there has been no builds on the last few days. Latest build is 20161211. just so you know :)
[HTC Desire S] Mustaavalkosta:
More about that here in the comments: https://github.com/OpenDesireProjec...bc3541de6e9db065fd9517#commitcomment-20207616
[HTC Desire S] i23098:
Hi, what does the end of cyanogenmod :crying: means to this project? Will it move to Lineage?
[HTC Desire S] kchaisu:
Hi Kylon, Mustavaalkosta and Paulb_nl,

Thank you very much for your contribution to the community over the years. I am doubt that up to this point at the end of CyanogenMod, it might be the end of the project. However, recently the community has been less active for sometime. Thank you very much. Merry Christmas to every one.
[HTC Desire S] kylon:
Hi,

Merry Christmas.

Cm13 is almost dead and there is no working opd 14 branch.

Lineage is still linked to CM, time will tell if it will survive.

Anyway i doubt this device will see lineage, or at least not soon.
[HTC Desire S] ralfbergs:
I will be able to support with testing, if that is of any help...
[HTC Desire S] Mustaavalkosta:
I have already announced that 13.0 is the last version that I'll be doing for ace so at least I'm out of any possible future around Lineage.
[HTC Desire S] ralfbergs:
Thanks for all your past contributions.
[HTC Desire S] i23098:
That's sad to hear :crying: but all must come to an end... Thank you very much for all you've done for our little great device. There's always hope someone can follow your great work :fingers-crossed:

All the best
[HTC Desire S] jkrhu:
The AOSP Google Keyboard is force closing all the time on the latest nightly. I've tried with Gapps pico and mini. Didn't make any difference.
[HTC Desire S] kchaisu:
Just delete /system/lib/libjini_latinimegoogle.so. It should be working.
[HTC Desire S] Mustaavalkosta:
There's a null pointer exception. It's possible that source isn't in mint condition in the last nightlies because of the CM domains died etc. If the last build is broken, try earlier builds. You might be able to downgrade by flashing older build manually on top of the broken installation.
[HTC Desire S] kylon:
Cm repos are dead, no more updates there.

You should keep your <31 builds.

[MENTION=3382363]Mustaavalkosta[/MENTION]

I think cm nightlies should be stopped.

If you are going to download lineage cm13 branch i ll rebrand the 13 branch to build laos.

If you are going to shutdown the server:

a big thanks for your time and effort, all this was possibile because of you :)
[HTC Desire S] Mustaavalkosta:
I shut everything off from crontab for the time being on 31st of December. I don't know when I'll have time to assess the situation. If Lineage is going to maintain something equivalent to cm-13.0 branches it's likely those branches will see some maintenance changes for some time in the future but I really don't have any clue what's going on with Lineage and its intentions towards old CM stuff.
[HTC Desire S] i23098:
It seems they do :)

We'll wait... At least, there's hope...

20161225 build did not work on my phone either, so I went back to Android 4.0.4 based on latest official... Didn't remember how old it feels to use it, and it has bugs on its own, so whenever new builds are running I think I'll be back to cm13 (or 14, hope is not yet lost ;) :D)
[HTC Desire S] 0lvin:
Sorry, i don't have time and ideas to check for now :(.

Looks as related to pmem issues, that is blocked gpu initialization:

[ 3.219238] pmem: pmem_setup: unable to register pmem driver(pmem) - zero size passed in!
[ 3.219268] android_pmem: probe of android_pmem.0 failed with error -1
[HTC Desire S] TiceRex:
My phone runs the 20160307 version of SagaOpt, everything seems to be running fine.

I just would like to know if it's worth to upgrade to the latest available version (20161225-20161231)? I've read so many complaints...

Please, advice. Thank you.
[HTC Desire S] kchaisu:
I have been using 20161225 and 20161231 builds (actually it has the same feature) up until now with out any major problem. However, I am not a heavy user. Thanks. Just backup and try.
[HTC Desire S] nijawang:
Really?

I have been using 20161231 aceopt from that date it released.

And there is no major issue till now.

Although there are some differences between sagaopt and aceopt.

But you could have a try after backup your data.
[HTC Desire S] kauh:
Mustaavalkosta, any news on new builds on Lineage 13?
[HTC Desire S] TheBrainCandy:
new builds can be set easily as there's no problem changing to LineageOS repo, but improvement is what we're looking for!

I already made a Lineage OS build here it's almost the same as this ROM except Lineage name and bootanimation and some basic stuff.

last time i edited a CM12.1 ROM and a CM13 work has started, I'm sure Mustaavalkosta can make LineageOS 14 for us if he sees things can get better :)
[HTC Desire S] kchaisu:
Thanks for bring up the Lineage OS 13 update here otherwise it is so quiet.
[HTC Desire S] kylon:
No plans for "official" builds.

Lineage 13 does not bring any improvement, it still lack a lot of cm features and they are doing things differently.

Same for lineage 14.

I have the source but i m stuck with an error about alsa.

I haven t looked deeply on this.
[HTC Desire S] TheBrainCandy:
Agreed and i don't think CM/LineageOS 14.1 will make our device any better I'm thinking if we make CM12.1 any better will be much worth it :rolleyes:

:highfive: for that
[HTC Desire S] kchaisu:
Deleted
[HTC Desire S] i23098:
Hello :D

You probably seen that TheBrainCandy did a Lineage 13.0 build. Just wondering if you miss our little device :confused: :silly:

I have 2 bugs with that build (no rotation of screen when rotating the phone and no sound on video recording)... Maybe you could take a look into Lineage :confused: :rolleyes: :o

All the best and thanks for all your work :highfive:
[HTC Desire S] ralfbergs:
Android Go may inhale new life to our fine little device...

https://www.xda-developers.com/android-go-optimizes-android-o-to-run-on-low-end-devices/
[HTC Desire S] kchaisu:
Recently, Mustavaalkosta has posted his intention to abandon the development of ROM for Ace in which Saga is inclusive. Well it is about time for 6 year old devices. No matter how the recent ROM have been developed, but the aim is for the new technology. So aged devices would never been able to fully exploit of the new technology because of the capacity of hardware differentiation, i.e CPU and RAM. Albeit Google intended to develop Android Go for low end devices, but it is not for sure for aged devices. New devices would have been exploited current CPU and RAM available on the market. So small memory of aged devices and new devices are not the same capacity. So I would say that Android Go is not for neither Ace nor Saga. Thank you very much Kylon, Mustavaalkosta, Paulb_nl and others of the team who have been dedicated to Open Desire Project for a long time. I am very appreciated your contribution.