yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] Mustaavalkosta:
I'm no expert but this is my understanding of it. The whole point of ART was to move from Just-In-Time Java run-time which basicly interprets java bytecode on-the-fly to Ahead-Of-Time run-time which pre-compiles that bytecode in such a way that it can be just executed from cache thus saving the time that would go to interpret it first and then execute it but creating cache files with that data in them naturally takes more space on storage device.

Using interpret-only dex2aot compiler filter scales back this pre-compilation of bytecode and makes it behave more like dalvik VM worked earlier while saving storage space because we don't have that much of it. Opt builds are using default speed filter which uses more storage space but also behaves like ART was designed to behave thus achieving the much marketed speed improvements.

http://source.android.com/devices/tech/dalvik/configure.html#compiler_filters
[HTC Desire S] jrior001:
Hit the same link again, I replaced it. http://downloads.codefi.re/jrior001/TWRP-recovery-sagaopt-2.8.7.0.img
[HTC Desire S] kchaisu:
Thank you very much jrior001. I shall test and report later.
[HTC Desire S] kchaisu:
Hi jrior001,

The recovery is working fine; I flashed CM-12.1-20150920-Unofficial-Sagaopt.zip by ADB sideload. It is booted up without any problem, so far.

Thank you very much for your support.
[HTC Desire S] jrior001:
Very good, thanks for the update.
[HTC Desire S] kchaisu:
Hi Mustaavalkosta,

CM-12.1-20150920-unofficial-sagaopt.zip is working fine, so far. Thank you very much for your kind support.

---------- Post added at 02:56 AM ---------- Previous post was at 02:55 AM ----------

Thanks. I ran out off thanks.
[HTC Desire S] richardz123:
it could be nice if its an options in the buttons menu in the settings to where you can enable/disable them

like im not that good to code that buthif annyone could do it thanks
[HTC Desire S] i23098:
Quick look into the app store, there's an app (SoftKey Enabler) that does it. Haven't tried it but feel free to try it and hopefully it will work for you :fingers-crossed:
[HTC Desire S] Mustaavalkosta:
It would be much easier to just create init script that sets those properties. Add backuptool functionality in the mix and you have flashable softbuttons enabler zip that will be permanent until you manually wipe /system. This is like 5min job if you know what you are doing so maybe I can sacrifice 5mins of my day at some point. At the moment I'm quite busy trying to fix KK adreno blobs for us so we could get rid of WebView crash but maybe after this or when I need a break from adrenos. :)

Edit: If you want it now, you can probably edit the script in http://downloads.codefi.re/mustaavalkosta/cm-11-unofficial-ace/extras/lowram-signed.zip by yourself quite easily.
[HTC Desire S] kchaisu:
Hi Mustaavalkosta and jrior001,

Thank you very much for your kind extending opt project to saga. I installed CM-12.1-20150920-unofficial-sagaopt.zip and applied L-Speed Trinity v.3.0 of which I am using the device from 09.00-18.00 oclock and battery status is still full and continues to full after this period. I have never experienced this status of battery usage on the same version of L-Speed on normal unofficial CM-12.1 for saga. This piece of information implies that communication between ROM and SDcard consumed a lot of power on Lollipop, so converting SDcard to emulated internal memory has reduced power consumption on Lollipop. Thank you very much for your kind contribution. The opt project provides better battery consumption than normal CM-12.1. Thanks
[HTC Desire S] Mustaavalkosta:
Do you have very old battery? They tend to start reporting completely crazy charge levels when they go bad. I haven't noticed much difference after I started using opt version of ace build.
[HTC Desire S] kchaisu:
I have a new battery with high amperage, but it is almost two years old now. The original battery came with Saga was death for along time. However, for sure CM-12.1-sagaopt nightly provided less power consumption than normal CM-12.1-saga. Thank you very much two of you for the project.
[HTC Desire S] init1234:
Sagaopt

Hi kchaisu,

I tried to flash Sagaopt in recovery but faced an error :

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

E:Error executing updater binary in zip '/sdcard/CM-12.1-20150920-Unofficial-Sagaopt.zip"

can you please provide any advice?
[HTC Desire S] kchaisu:
I used Gparted to format the whole SDcard to ext4.

Copied CM-12.1-sagaopt nightly to SDcard.

Fastboot flashed TWRP-sagaopt, then rebooted to recovery.

Use ADB-Sideload to install the nightly.

Reboot and set up.

That is all.

Thanks.
[HTC Desire S] jrior001:
Did you flash the new sagaopt twrp? From your error I think not
[HTC Desire S] init1234:
hello jrior001,

yes I flashed this TWPR twice, but there is the same error

---------- Post added at 08:29 PM ---------- Previous post was at 08:27 PM ----------

thanks, I'll try your way
[HTC Desire S] Mustaavalkosta:
Assert check fails because your recovery is wrong. There's no mystery to this. You are wasting your time with other ways until you flash correct recovery.

http://downloads.codefi.re/jrior001/TWRP-recovery-sagaopt-2.8.7.0.img

This is the one you should have installed to install sagaopt builds.
[HTC Desire S] Sefy:
I'm getting the exact same error as him, and i've flashed the exact recovery in your download link several times now.

Is there any specific way to make sure we are getting the correct TWRP recovery?
[HTC Desire S] jrior001:
I know what's up, new build will be up shortly.
[HTC Desire S] Mustaavalkosta:
Well, this makes it two which raises suspicions. One odd man out is 99% of the time just user error. ;) Now I just wonder how one guy can flash it without errors while others can't but if jrior001 already knows what's up it's all good already.
[HTC Desire S] jrior001:
Let's give this one a try

http://downloads.codefi.re/jrior001/TWRP-recovery-sagaopt-2.8.7.1.img
[HTC Desire S] kchaisu:
Hi jrior001,

I have a problem on the TWRP-recovery-sagaopt-2.8.7.1.img. Flashing is fine, but every time, I reboot the system. It showed the system seem not rooted, install Supersu? I ignored the message and reboot, it is alright. Then I rebooted to recovery and rebooted to the system, it showed up the same thing that my system seem not to be rooted. So I flashed back to version 2.8.7.0. Thanks.
[HTC Desire S] jrior001:
As suspected you are still on old partition format or somehing. Its not detecting system on the right partitions. Whatever you did yesterday I'm pretty sure you are not on the proper sagaopt setup.
[HTC Desire S] kchaisu:
I shall use verion 2.8.7.1 to set up the system on the new nightly and will report the outcome. Thanks for your kind assistance.
[HTC Desire S] kchaisu:
Hi jrior001,

Yes, I was in the old partition format since I did not wipe the old system partition because it was booted up the same way as normal saga recovery did. The new installation having only one apps to finishing boot so it is fast. Thank you very much for your and Mustaavalkosta contribution.
[HTC Desire S] Sefy:
I can also confirm that installation is now working, will give an update once it's all done and system is booted! :good:
[HTC Desire S] kchaisu:
Hi jrior001,

Setting time zone in sagaopt recovery is one hour advanced to local time. Sometime when I set up the time zone, at that moment it was corrected time. However when rebooted the system and reboot back to recovery and again it changed. It is not stable though. Now, it is one hour advanced to local time, no change obviously detected. Thanks.
[HTC Desire S] Lapyyyyyy:
Hi, God of Recovery :)

Oh my God, I'd flashed recoveery and can't flash anything, restore anything - recovery doesn't see zips, all zips. :eek:
[HTC Desire S] jrior001:
Yeah that's kinda expected, go back a page or 2 and read mustaa's description of what the sagaopt builds are. System/data/sdcard partitions are all remapped differently, which requires a different recovery to match. Think of this as clean slate time. You can go back to regular saga recovery and all your stuff is still there, otherwise follow instructions to boot sagaopt instead. That's going to mean wiping EVERYTHING, copying build/gapps via adb and starting from a clean slate.
[HTC Desire S] Lapyyyyyy:
Yep, understood you. But I re-flash recovery 2.8.7.0 and have same problem - I can't flash enything (Restore-'folder'-nothing). What I do not correctly?

Thank you so much for you tenderness.
[HTC Desire S] jrior001:
If you already started wiping things there's no telling....

You can post a recovery.log, I can at least confirm things are mounting properly, and in which partition format.

adb pull /tmp/recovery.log and pastebin it
[HTC Desire S] Lapyyyyyy:
It was like this: I made a backup of the ROM, then flashed a new recovery. Reboot ...

Now, computer displays Internal Storage 1,86 of 29,7 gb is free.

Open on recovery and computer folder, and see first folder is empty and second - TWRP, empty too.:crying:
[HTC Desire S] Sefy:
A little update regarding testing the sageopt recovery and rom, I've flashed the new 2.8.71, made the SD into a full 32gb ext4 partition and flashed the rom. Basically everything went great, no issues there and things seem to work as they should. The only thing that "bugs" me is the installation/restoration of apps. I've let the OS do a restore of my account which was 3 days ago, to restore 56 apps... it still has 6 to go...

Is this normal for it to install/restore apps so slowly? i mean, this is beyond slow..
[HTC Desire S] Mustaavalkosta:
Well, it depends how complex apps you are restoring. Running dex2aot takes a while if there's a lot to compile. Like I said in the opt variant release notes: this is no cure to an old device but run-time speeds (once the ART compilation is done) with fast sdcards are likely as good as they will ever be with the latest OS version. Opt variant is also pre-compiling more than regular builds due to different dex2aot filter. Restoring loads of apps takes a while even with Nexus 5 so I'm not totally surprised of 3 days if all of your apps require a lot of compilation when we also count in download times and so on.

My 30 or so non-pre-optimized apps take an hour or two to run through "Android is upgrading" process though so maybe system has been under heavy load the whole time due to gapps doing who knows what slowing everything down and when they can't do it in timely manner everything takes a long time to finish. The whole thing feels a lot snappier if you leave gapps out.

Anyways, I'm not defending the slowness, just trying to explain why it can be slow. Things might be much brighter if msm7230/8255 devices were dual cores. Coming zram changes may ease the dex2aot slowness a bit too but I wouldn't expect miracle improvements unless someone finds out software bug that eats huge amounts of CPU cycles or something similar.
[HTC Desire S] kchaisu:
It is apparent that the question on daylight saving had been ticked, so unticked the question solve the problem. Thanks.

My apology for a wrong report question.
[HTC Desire S] Lapyyyyyy:
:confused:
[HTC Desire S] jrior001:
That is clearly still the sagaopt recovery, not the regular saga recovery. Grab the regular saga recovery from the twrp thread and try again
[HTC Desire S] i23098:
Tried 20150927 with TWRP 2.7.0.1 and I now it won't finish booting, always get a message saying encryption failed, ask to reset phone, reboots, same thing again...
[HTC Desire S] i23098:
Well, some weird thing happens on my first attempt... I had flashed by mounting sd-ext on twrp and copy the zip files there (as I had old adb, without sideload). I had partition my sdcard on TWRP, for some weird reason, it had a small fat partition and a big ext4, instead of just one ext4.

Well, I used a computer today to have just one ext4 partition, updated adb and did adb sideload of all zips (cm, gapps, addons, supersu), and it seemed all went well this time :fingers-crossed: No internet to install apps, so can't really say if all is ok, but it started :)
[HTC Desire S] mackhenri:
Your phone seems to be in a very good condition. Its my niece using this phone now and she has managed to take of all the paint
[HTC Desire S] i23098:
Google camera

I flashed the google camera addon, and it fails on going to settings :( Logcat available here

It's a java.lang.NullPointerException on google's code, but it's trying to read some Preferences object... Could it be that CM is not returning all the info it should :confused:
[HTC Desire S] sssimo96:
sagaopt

Hello! Recently I have been using a few BlackBerry devices, but since a few days I repaired my Saga so it is now my daily driver. I see there is a sagaopt build. Can't understand what does the "opt" stand for. Tried flashing it, but no luck. I don't have much free time as I both work and study now, so I hope that someone wouldn't mind to just reply to my post with some kind of explanation of the "opt". A simple link or short explanation of what opt is and how it works on the Saga is completely enough for me as I have all the basic knowledge about Android and Linux.

Please, give me some info about that "opt"! I am really interested of Its features.

Thanks in advance!
[HTC Desire S] i23098:
Use the sdcard as internal memory...

Take a look at Mustaavalkosta's post
[HTC Desire S] Mustaavalkosta:
Our cam blobs are too old for that. Stick with the AOSP/CAF camera because we are lacking all the fancy stuff that newer camera interfaces support. You don't have much to gain with Google's app.
[HTC Desire S] i23098:
I didn't know we used blobs for it :( Is there a place to download AOSP/CAF camera? I installed the google apps camera addon and it replaced the stock camera.
[HTC Desire S] Mustaavalkosta:
Nope, it ships with the ROM. You can get it back by removing backup script for camera (e.g. 83-gapps-camera.sh) from /system/addon.d and reflashing ROM zip.
[HTC Desire S] ralfbergs:
Thanks very much for that. I was used to that layout already from some XperiaSP build, and I think especially for the Saga with its very small /data partition this is very helpful.

BTW, I was "offline" for a while as I mistakenly watched the wrong thread (the one about cm-12.0), and I was wondering already why everybody was so quiet... :D

I installed the OCT-01 build, and it seems to work well (AFAICT after only 30 mins... ;)).

Just for the record, this is the new partition layout (note that I'm using an 8 GB uSD card, formatted with F2FS), FS usage is before I actually installed the OS and GApps:

~ # mount
/dev/block/mmcblk0p27 on /cache type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,acl,active_logs=6)
/dev/block/mmcblk1p1 on /data type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,acl,active_logs=6)
/dev/block/mmcblk0p26 on /system type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)

~ # df -h
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p27
143.9M 96.1M 31.9M 75% /cache
/dev/block/mmcblk1p1 7.4G 466.1M 6.9G 6% /data
/dev/block/mmcblk0p26
1.1G 22.3M 1.1G 2% /system

After install of cm-12.1-20151001-UNOFFICIAL-sagaopt and open_gapps-arm-5.1-pico-20151002

~ # df -h
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk1p1 7.4G 791.2M 6.6G 11% /data
/dev/block/mmcblk0p27
143.9M 52.1M 75.9M 41% /cache
/dev/block/mmcblk0p26
1.1G 662.3M 496.3M 57% /system

And just for comparison here is the old, traditional "saga" partition layout:

~ # mount
/dev/block/mmcblk0p27 on /cache type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,acl,active_logs=6)
/dev/block/mmcblk0p26 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /sdcard type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,acl,active_logs=6)
/dev/block/mmcblk1p1 on /and-sec type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,acl,active_logs=6)
/dev/block/mmcblk0p25 on /system type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)

~ # df -h
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p27
143.9M 96.1M 31.9M 75% /cache
/dev/block/mmcblk0p26
1.1G 22.3M 1.1G 2% /data
/dev/block/mmcblk1p1 7.4G 466.0M 6.9G 6% /sdcard
/dev/block/mmcblk1p1 7.4G 466.0M 6.9G 6% /and-sec
/dev/block/mmcblk0p25
549.8M 9.7M 540.0M 2% /system

Maybe this is useful for some, maybe later for reference...

Best regards,

Ralf
[HTC Desire S] kchaisu:
Thanks Raftbergs for your info. Actually, I am always with this forum, however, most of the members usually visit once in a while; but some members do not owe the device any more. That is the fact for old devices because it could not provide much more new features to catch up with technological development.

I myself is too old to play around with the technology, I just want my phone for communication of my own need.

Actually sagaopt is good for accomodating more apps and fast boot time on bare ROM boot up, however, when it comes to gapps boot up it takes so long. So the more apps you have, the more boot up time needs as Mutaavalkosta did mention on a few previous post back. As I already said, I shall try to test most of the nightly if not all because I respect Mustaavalkosta, Kylon, Paulb_nl, others of the team and jrior001 for their devotion to this Project and the forum. Thank you very much.
[HTC Desire S] ralfbergs:
Thanks very much [MENTION=5691218]kchaisu[/MENTION] for your response and for devoting your time on this project.

When you mention "boot up times" I guess you refer to the very first boot after a new OS install, right? So that the ART engine can perform the ahead-of-time (AOT) compilation of apps?
[HTC Desire S] kchaisu:
Yes, first boot up time which I usually flashed ROM, reboot for set up. Then flashed Gapps and reboot. The first boot up is very fast, but the second boot up is quite slow and very dependent on the size of the gapps. Thanks.
[HTC Desire S] i23098:
Facebook update crash

I'm on 20150927, opt version, and facebook update fails and causes the phone to reboot :( Logcat here
[HTC Desire S] i23098:
I'm on 20150927, opt version, and when I tried to dirty flash 20151004 on top of it, it says it is incompatible :( Does the opt version only support a clean install?!
[HTC Desire S] Mustaavalkosta:
Might be running out of memory based on that log. Watchdog is killing PackageManager which then brings down the whole system. FB is known to be too big for its pants, not sure if there's much we can do if they can't keep their app slim enough that it works on low memory devices.

Nope, upgrade flashing has been working just fine here but I haven't installed latest nightlies for a few days. At least the assert check in 20151004 updater-script is just fine so make sure you have appropriate recovery flashed although I don't know how it might have changed if you haven't changed anything after flashing the initial version.
[HTC Desire S] kchaisu:
Actually, I was successfully dirty flashed sagaopt nightlies, but it was only a day different of October`s nightlies. However, OTA update had never been succeeded. Thanks.
[HTC Desire S] richardz123:
i have not found out how to edit it
[HTC Desire S] Mustaavalkosta:
https://dl.opendesireproject.org/misc/
[HTC Desire S] karmacop:
Hey guys, firstly thanks for the ROM its great to see people still developing for such an old device! :)

I dug my old Saga out of the junk cupboard the other day with the idea of using it as a dashcam in the car. I installed CM as I thought it might be the lightest way to run 5.1.

The issue I am having is with the camera. I can use the built in camera app to take stills and videos, but whenever I try to use any of the dashcam apps, for some reason they wont load the camera. I've seen some previous posts in regards to issues with the newer Google Camera app so am wondering if I am hitting similar issues. Is this device just too old for this, should I cut my losses with this idea?

Thanks for your time!

Josh

---------- Post added at 06:43 PM ---------- Previous post was at 06:38 PM ----------

Oh scratch that, it *says* its taking a video with the camera, but the files wont actually play back. :/
[HTC Desire S] VnnAmed:
Facebook is cancer. It already metastasized into tons of memory hogs and it keeps growing. After they have realized what they have done they were trying to treat it with FB lite but it still kills you (being very thrash tier of an app), just a lil bit slower. I have 3 devices: saga, Xperia T and M7 and all of them get battery drains and lags whenever I install one of FB apps. I don't know how can it be that such a big company can have such tarded devs but whatever. I would stay away from their apps. On the Xperia (my gf's phone) FB + Messenger (why the fck split these two?) was taking like 120MB of RAM. U can have a working OS that uses this amount. Fck FB.
[HTC Desire S] kchaisu:
I use neither FB nor LINE on Saga. Just only tapatalk is installed on it. You are right these apps are cancer like.
[HTC Desire S] HA4ever:
I use Faebook lite and it works great on my Desire S
[HTC Desire S] richardz123:
thanks man :)
[HTC Desire S] soak:
FB Lite (https://play.google.com/store/apps/details?id=com.facebook.lite) is good.

It's really light and you don't need the extra messenger app.
[HTC Desire S] kchaisu:
Hi Mustaavalkosta,

Today nightly, an annoying sign on top of the screen when stock supersu has been granted was disappeared after finish up the apps. Thank you very much.
[HTC Desire S] ChristianFerrer:
What is the real difference between cm12.1-YYYMMDD-UNOFFICIAL-sagaopt and cm12.1-YYYMMDD-UNOFFICIAL-saga ?
[HTC Desire S] Mustaavalkosta:
http://xdaforums.com/showpost.php?p=62896411&postcount=282
[HTC Desire S] kylon:
Edit:

Too late xD
[HTC Desire S] kchaisu:
Actually, it had gone for one nightly and came back so far. Thanks. It seems currently Kylon has owned HTC Desire S. Thanks and welcome.
[HTC Desire S] DeKiesel:
Hi, a friend of mine asked me to update his desire s so I am doing some research which Rom would be the best. I unterstand that the second boot of this Rom can take a long time due to the art optomizations. Will the other boots be quicker then? Also, what about the radio? In other Rom threads there is a lot about radio flashing but not here,does that mean the installer takes care of everything? Thanks for any help ?
[HTC Desire S] ralfbergs:
Yes.

No. You keep the modem/radio firmware that was installed prior to installing CM...
[HTC Desire S] Sefy:
I understand that using the latest OS's on our phone is basically "pushing it too far" and to be honest, on my Primary (i have 2xSaga's) i've actually decided to go back to CM7.2 and it works super amazing and fast with all my apps. I just like "torturing" the spare one every once in awhile ;)
[HTC Desire S] Mustaavalkosta:
Yeah, while we are indeed pushing these old devices to the the limits and beyond it's good to ask questions like these because I certainly don't know everything and sometimes I don't notice to ask myself the questions that should be asked.

Case in point: I actually may have found the CPU hog that I said earlier that might exist. Disabling UKSM seems to noticeably speed up app installs and likely does that for anything that triggers page merging while being also CPU intensive. Page merging may be nice for saving a bit memory here and there by merging duplicate pages but it also requires CPU cycles to scan memory for duplicate pages which may not be ideal for a device that is already choking under the OS's demands for CPU cycles. I disabled UKSM in 11.0, 12.0 and 12.1 for now to very least reconsider its meaningfulness.
[HTC Desire S] Sefy:
This sounds rather interesting, as i'm quite fund of CM11 (i dislike the UI of Lollipop), so i'd be curious on how you disabled the UKSM? my main issues with all the latest versions is that the phone takes a long time to respond when a phone call is coming in, which in most cases i've got to call back as the person hangs up (or i even have to shut the phone down by pulling battery) by the time i manage to get the phone to respond to unlocking or even getting the screen back on! that's why I went back to CM7.2 which never gives me those issues.