yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] 2021redmi2fans:
where can be download this rom? it seem to deleted:(
[HTC Desire S] DDeenis:
Open Desire Project

CyanogenMod builds for HTC Desire HD and Desire S.

opendesireproject.github.io
[HTC Desire S] 2021redmi2fans:
Thank you very much, bro!(y)
[HTC Desire S] ralfbergs:
ADB over network doesn't work?

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

ADB over network doesn't seem to work in 2015-12-27. I can't telnet to port 5555, neither from my Mac, nor locally to localhost:5555. A logcat doesn't show any activity at all when enabling or disabling the switch in "Developer options" (or maybe I'm blind?).

Kind regards,

Ralf

---------- Post added at 22:39 ---------- Previous post was at 22:36 ----------

Sure, enjoy your time off! :)

Thanks. As I'm always very security-focused I use CM, and I was really surprised to see this one test failing...

Best,

Ralf
[HTC Desire S] kylon:
Thanks!

I will add the kernel patch today :)
[HTC Desire S] ralfbergs:
Great, thanks a lot. It's amazing to see that such an old mobile phone still is current with respect to security issues. best regards, Ralf
[HTC Desire S] ralfbergs:
[MENTION=3334728]kylon[/MENTION]: I checked it again in 2015-12-29, but the device is still vulnerable.

I assume the patch is simply not yet included as you might not have had the time? Or will it be in tomorrow?

Thanks a lot!

Best,

Ralf

---------- Post added at 14:02 ---------- Previous post was at 13:43 ----------

My bad, I forgot to flash the new boot.img. ;)

Sorry about the false alert. Our Saga is safe now. ;)

Thanks a lot for your great job!

Best,

Ralf

---------- Post added at 14:14 ---------- Previous post was at 14:02 ----------

Hi [MENTION=3334728]kylon[/MENTION],

when trying to run the test for CVE-2014-4943 in NowSecure's VTS an error 22 (EINVALID) pops up, and the following can be seen in logcat:
12-29 14:10:01.137 D/VULN_TEST( 4492): Running test: CVE-2014-4943
12-29 14:10:01.138 W/System.err( 4492): java.lang.Exception: Error running test. Errno: 22
12-29 14:10:01.138 W/System.err( 4492):	at fuzion24.device.vulnerability.vulnerabilities.kernel.CVE_2014_4943.isVulnerable(CVE_2014_4943.java:41)
12-29 14:10:01.139 W/System.err( 4492):	at fuzion24.device.vulnerability.test.VulnerabilityTestRunner.doInBackground(VulnerabilityTestRunner.java:58)
12-29 14:10:01.139 W/System.err( 4492):	at fuzion24.device.vulnerability.test.VulnerabilityTestRunner.doInBackground(VulnerabilityTestRunner.java:15)
12-29 14:10:01.139 W/System.err( 4492):	at android.os.AsyncTask$2.call(AsyncTask.java:295)
12-29 14:10:01.139 W/System.err( 4492):	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
12-29 14:10:01.139 W/System.err( 4492):	at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
12-29 14:10:01.139 W/System.err( 4492):	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
12-29 14:10:01.139 W/System.err( 4492):	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
12-29 14:10:01.139 W/System.err( 4492):	at java.lang.Thread.run(Thread.java:818)
12-29 14:10:01.139 D/VULN_TEST( 4492): CVE-2014-4943 failed with: Error running test. Errno: 22

Not very helpful, huh? :(

The test is about L2TP sockets.

I checked, but L2TP seems to be built into this ROM, at least you seem to be able to set up L2TP VPNs (can't check whether it actually works, but the functionality seems to be present).

Any idea what could be going wrong? Any input what else I could do to get more info?

Kind regards,

Ralf
[HTC Desire S] richardz123:
i have a few things to say

1. is it flasheble with the same recovery as used for CM12.1?

2. can i flash the boot.img on windows 10 ?

and 3. its good to see sutch a new rom for so old phone to come out

4. does it have the new Google Now On Tap
[HTC Desire S] ralfbergs:
As long as you use the "sagaopt" version of TWRP, yes. :)

Yes.

Yes.

I don't see why this should not work, but I haven't tried it yet. I tried it on another phone, but it was a bit hard to set up as it needs a couple of Google apps plus relevant settings to work together...

---------- Post added at 16:16 ---------- Previous post was at 16:13 ----------

Hi [MENTION=3382363]Mustaavalkosta[/MENTION], [MENTION=3334728]kylon[/MENTION].

Happy New Year! (My best wishes and regards also to the other fellow users here in this thread...)

Any news about the camera support? Are you working on this, or do you have other priorities?

Kind regards,

Ralf
[HTC Desire S] Mustaavalkosta:
Happy New Year to you too!

Nope, no news. I've been sick again (winter flu part 4) and having compilation issues on my home PC.
[HTC Desire S] ralfbergs:
Thanks!

Sorry to hear about that. Hope you feel better now... I was also sick a couple of days at the end of the year... I think by that time the batteries are simply discharged, and your body needs a break...

Thanks for the update, and hope you can fix your PC issues soon...

Best, Ralf

--

Sent from a mobile device.

Please excuse my brevity.
[HTC Desire S] kchaisu:
I have been playing around with Chainfire Systemless SuperSU Beta 2.66 on CM-13 sagaopt nightlies and facing with some issues on internet connection for some time. So finally, I use the feather on SuperSU Pro, Full Unroot function to uninstall SuperSU, let the device rebooted then rebooted to TWRP recovery, flashed SuperSU Beta 2.66 again. This time I have solve the issue on internet connection. Thank you very much Mustaavalkosta, Kylon and the team in making CM-13 Sagaopt for the community to play around. Currently, I have been using CM-13 sagaopt for my daily usage. Happy New Year 2016 to everyone.
[HTC Desire S] Sefy:
Just been installing this on my spare phone, and i gotta say that i'm very impressed! :good:

This works way better then the 12.1 worked on my phone! and i've even loaded it up with all HTC's stuff (Sense Home, Keyboard...) and it's working very smoothly!

Amazing Work!

Thanks to: kylon, Mustaavalkosta, paulb_nl, PhantomShadow

Waiting for you guys to fix the Camera and whatever other little bugs that may exist! :p

Stuff that doesn't work:

Camera

Compass

GPS - (Seems to be Reversed?)

MTP - File Transfer / USB - PC can't see the device and phone doesn't give the option

I'll add what I find that isn't working (except calls, i've no seem on this phone)
[HTC Desire S] richardz123:
im using TWRP v2.8.6.1 so no not the sagaopt one (sagaopt fails to work)

to youre awnser of saying yes its actualy NO since it fails to see fastboot usb and retunes the error

the last usb device you connected to this computer malfunctioned and windows doesn't recognise it

unknown usb device (device failed enumeration)
[HTC Desire S] ralfbergs:
Have you installed the drivers for your phone? There's also a generic driver that should work with "most" Android phones and includes adb and fastboot...

--

Sent from a mobile device.

Please excuse my brevity.
[HTC Desire S] richardz123:
M8 can you not read

I am having an error that exist since windows 8

There's a update fix for it but its only for windows 8.1

---

Send from a HTC desire X
[HTC Desire S] DDeenis:
Sagaopt...

I flash twrp for sagaopt but it not working! It dont see zips! I cant install the ROM :crying:

Please, help me!
[HTC Desire S] kchaisu:
Make sure that you have installed TWRP-2.8.7.1-sagaopt recovery, not the TWRP-2.8.7.0-sagaopt recovery. Thanks.
[HTC Desire S] DDeenis:
Thank you! :D

P.S: I try it, but this recovery don't see my sd card :crying:
[HTC Desire S] ralfbergs:
Which filesystem are you using for your micro SD card?
[HTC Desire S] DDeenis:
Which filesystem I must have?

Screenshots of recovery (look at recovery version and at sd card):

https://drive.google.com/file/d/0B-F_li0nzEepNXJVdnlMd3M5OFU/view?usp=sharing (TWRP 2.8.7.0)

https://drive.google.com/file/d/0B-F_li0nzEepLVozREhXNU9IMW8/view?usp=sharing (TWRP 2.8.7.1 (Its foto because I cant do screenshot of this recovery))
[HTC Desire S] ralfbergs:
ext4, fat, f2fs should all work, IMHO...

Have you maybe missed the (non-?) obvious to click on the button(!) immediately below "Select Zip to install" to select your external SD card? /sdcard is not your external SD card, but your internal flash storage...
[HTC Desire S] Mustaavalkosta:
Nope, only EXT4 and F2FS are supported with opt variant due to using sdcard as data partition. FAT may work but it's not really recommended option to use due to lack of proper permission support.

Did you follow the conversion guide? There's a lot more to it than just flashing a recovery.

Note: the guide is for ace so download appropriate stuff for saga instead of ace stuff linked in the guide.
[HTC Desire S] DDeenis:
Thank you :D

I flash ROM! :victory::cool:
[HTC Desire S] richardz123:
also the sagaopt recovery seems to not work on my desire s just saying
[HTC Desire S] fadival:
Didn't know, there is still development coming around. good to know. great rom. :good:
[HTC Desire S] ralfbergs:
Sorry, I simply missed that fact. It's working so well that you forget it's there... :)

--

Sent from a mobile device.

Please excuse my brevity.
[HTC Desire S] Mustaavalkosta:
No worries, I just wanted to correct it before the flood of "why this isn't working?" questions rush in when people are trying to use it with FAT. :)
[HTC Desire S] ralfbergs:
You did well correcting my error, thanks!
[HTC Desire S] kchaisu:
Hi Kylon and Mustaavalkosta,

On 20160124 build, the camera did not showed up as usual and browser could browse but could not download big file as well. Thanks for your kind contribution.
[HTC Desire S] Mustaavalkosta:
There's no proper shimming yet in that build for camera libs. 20160125 should play ball.
[HTC Desire S] kchaisu:
Thanks Mustaavalkosta. It just a report because I have seen your message about camera on DHD thread. Thanks.
[HTC Desire S] kchaisu:
Hi Mustaavalkosta and Kylon,

Camera on 20160125 build is working well both front and back camera. On top of that, I have been testing for browser and it could be able to download a big file successfully, however, if the first push for download fail, then repeat the download. The second time will be successfully downloaded. Thank you very much for your kind effort and brilliant works.
[HTC Desire S] Mustaavalkosta:
Ok, good to know that saga cam is also functional. Did you have crazy blue flickering while booting up and often when closing / moving away from camera app? Or is it just ace that is having LCDC underrun issues?
[HTC Desire S] kchaisu:
I did not notice any crazy blue flickering as you mentioned neither on booting up nor moving away from camera apps. It is functioning normally. Thank you very much for your kind contribution.
[HTC Desire S] Mustaavalkosta:
Hmm, ok. Let me know if it occurs at some point. It was gone on ace on some bootups too on 12.1 test builds but then made it back on the next one.
[HTC Desire S] kchaisu:
I will let you know if it is noticeable. Thanks.
[HTC Desire S] kchaisu:
I have noticed some kind of flickering on apps as you mentioned occurring on Ace; so, I guess Saga shares the same flickering as well as Ace.

Thanks.
[HTC Desire S] tieff:
Hello, I've noticed heavy blue flickering on booting and so on... and bootloop in the end after this message :. Thank you for the ROM!
[HTC Desire S] Mustaavalkosta:
You have done the opt conversion somehow in a wrong way if you are getting that encryption message.
[HTC Desire S] kylon:
OP updated:

1 - faqs

2 - second post: sagaopt instructions (thx Mustaavalkosta)

3 - microG link

Whats microg?

This is an incomplete, free, secure and anonimous Google Play Services framework, you can find everything in the official thread.

Only for advanced users.

Why should i use microg?

it s source is open!

+CPU - lightweight compared to google services

+RAM - same as above

+Battery Life - less wakelocks

+Space on /system
[HTC Desire S] Mustaavalkosta:
Blue flickering (e.g. LCDC underflow warning color) is expected since the camera libs started loading properly (20160125 and newer builds) because they somehow cause the flickering.

Yeah, me too. Sadly this has been an issue that makes very little sense and nothing apart from killing camera libs and thus camera seems to have any effect on it. I can't even count the full days I have already spent scratching my head and paulb_nl's head with it. :(
[HTC Desire S] kchaisu:
Thanks Kylon, Mustaavalkosta, and Paulb_nl for your kind contribution which made CM-13 sagaopt 20160127 build so far in the stable state to use as daily phone. Though 20160125 and 20160126 builds which camera shimming has been initially included were causing set up troublesome and consuming longer time in finding info for google account somehow including problems on starting apps after optimization and process system does not response sign on later reboot. I also somehow face some problems on replacing stock webview with google webview on google account. The 20160127 build provided superb clean up what the mess 20160125 and 20160126 introduced both in term of easy and shorter time consuming in setting up and functional. However, the blue flickering on boot still intermittently shows up, anyway it is not annoying for me because I am not observing the booting anyway, just set reboot and gone for doing some other thing and came back later. For FOSS apps, I shall experiment with it later. Thanks you guys for the great contribution. I apologize for complaining so long.
[HTC Desire S] Mustaavalkosta:
Yeah, in addition to causing blue flickering camera libs also slow down the system noticeably which is probably what you are experiencing with longer waiting time to get accounts setup etc. Sadly no idea why libs can cause such high load on the system. :(
[HTC Desire S] DDeenis:
Can you add Doze and App Standby?

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

Can you add Doze and App Standby?

Thank you!
[HTC Desire S] ralfbergs:
Is it naive to think that libs can cause an effect only on binaries which are linked towards them?

Can we not "just" use "ldd" or a similar tool to find out which binaries depend on them and then look into why these are slowed down?
[HTC Desire S] Mustaavalkosta:
Well, that's likely true but no attempts toward figuring out which binary is causing it has been a successful one this far. I guess you could just remove all the vendor cam binaries from the device and prove/disprove this theory for those binaries and hope it's nothing in base system side. I'm not that good with native level debugging and there's no one else available for that job anymore. :(

Edit: I actually just removed /system/bin/{awb_camera,lsc_camera} binaries and camera seems to still function. I can't tell if there's much difference in bootup speed since I have gapps installed and those slow things down significantly too. I dropped those binaries from future builds though for now. No use to drag them along if they serve no purpose. I need to test further without gapps and with stopwatch at some point if no one else wants to waste their time rebooting over and over again for hours collecting test data. :p

---------- Post added at 15:52 ---------- Previous post was at 15:34 ----------

Sure but I don't know if we have necessary sensor to make it work. We have accelerometer but I don't know if it's low-power sensor which is required for doze.

Source
[HTC Desire S] DDeenis:
:confused:

OK. App Standby is not working too?:confused:
[HTC Desire S] Mustaavalkosta:
That doc page I linked earlier says nothing about build system toggle for App Standby nor specifics how it functions with or without Doze functioning properly. So I don't know. Doze is enabled in future builds but that doesn't mean it will function as expected if our accelerometer isn't suitable for Doze usage.
[HTC Desire S] ChristianFerrer:
Wi-Fi keeps on disconnecting on the latest build. Anyone has the same problem?
[HTC Desire S] kchaisu:
I sometime used stock webview and stock browser and had problem with downloading big files> So I switched to google webview and firefox browser, I have no problem with wifi on the latest build. Thanks.
[HTC Desire S] Mustaavalkosta:
I have been killing off some network tweaks recently that may have had a negative effect on network traffic. I think running with the OS defaults is the way to go since they should be the most generic configuration for every purpose imaginable. Just like Linux kernel defaults.
[HTC Desire S] kchaisu:
Thanks Mustaavalkosta for the info. When I flash nightlies, I normally maintain stock webview and browser; however, when I faced download problem, I would switch to google webview and Firefox browser.. And sometime I also faced a problem on switching as well. I totally agreed with you on the matter. Thank you very much for your kind contribution.
[HTC Desire S] DDeenis:
Can you give me Doze or App Standby apk?:)
[HTC Desire S] Mustaavalkosta:
It's a framework switch. Even if it's possible to enable it via a single apk I have no idea which one the switch affects. Just download the latest build, it's a lot easier that way.
[HTC Desire S] kchaisu:
Hi Mustaavalkosta,

On the 20160130 build, booting and set up time is only 30-40 min, however, wifi set up has to be skipped at first because it is still slow to catch up with the set up. Sign of starting app and the process system is not response have gone. What I am talking is clean ROM flashing and clean app flashing. On top of that I flashed Chainfire Systemless SuperSU beta testing version 2.67. I forgot to tell that the first booting up is looking like double reboots Thank you very much for your kind contribution.
[HTC Desire S] richardz123:
so a few ours ago i flashed 20160130 and it took a heck of a long time to boot like mabey 1.5 hours and then when it was there i dit all the setting up and stupp just like i dit with cm 12.1 and downloaded open_gapps-arm-6.0-mini-20160130.zip because the one above was jus to big so i flashed those gapps and first i booted up normally only after like 20 min the setup app of google was FC every 0.5 seconds so i restarted and it dit the same thing so i was thinking maybe just maybe it wil work if do a factory reset so i dit it and now it wont go to the system i flashes dark blue stripes at bootup and it is stuck at optimizing app 3 out of 27
[HTC Desire S] richardz123:
new note got the os working only asop keyboard keeps crashing
[HTC Desire S] richardz123:
Just saying the md5checksum is not found by the OPD updater
[HTC Desire S] joolli:
For the force close error on the keyboard; you need to boot into recovery, mount the system partition and either delete or rename: system/lib/libjni_latinimegoogle.so
[HTC Desire S] richardz123:
i installed the google keyboard and removed the stock one

and on the last update it wont boot further than the screen saying optimizing app 1 of 6 see attachment

and yes that the screen is blue is not the camera buth the screen turning blue the moment i made the picture
[HTC Desire S] joolli:
I've had that problem, except optimizing 1/2 and when it finally finished after about an hour or two... It would reboot and start over. That's when wiped and startwd from scratch. :) When I started over I flashed the rom, gapps-mini and renamed the keyboard file and all was back to normal.
[HTC Desire S] DDeenis:
Very good ROM

Отправлено с моего Desire S через Tapatalk
[HTC Desire S] mithe:
Daily use

I installed the first cm13 nightly about a month ago with open gapps nano and put swiftkey via sideload on my Saga. Since then I regularly updated.

The boot/app optimizing loop after an update took sometimes very long, but eventually finished. Sometimes after several hours or trivial changes like unplugging the power supply.

Camera: Is working fine now, takes often some time to load. App is not listed but you can reach it on the lock screen.

Telephony: Outgoing it works perfectly, with incoming calls it takes a second to display the app while already ringing. But it does not crash and I never missed a call.

Bluetooth: Crashes when trying to connect another device. It does not find my bluetooth headphones (My audio jack is broken, for music I depend on bluetooth.)

I upgraded from stock 4.0.4 to the cm13 nightlies and I do not want to go back. Even with the problems and glitches here and there, the ROM is significantly faster and looks much nicer. I can count on one hand the times the nightly ROM completely crashed in the last month. Great work!

If there are any questions or you want me to try something out, post it to me.
[HTC Desire S] mickw1:
I have been using this and the only problem is the g-sensor calibration... when I bring the phone down from my ear it will stay on the blank screen :( ?? . so I put it back to stock and used the g-sensor calibration and now it works fine.

so how do I use the g-sensor calibration with 13 nitghtlies...
[HTC Desire S] Mustaavalkosta:
Doesn't Desire S have proximity sensor? That's the one you should be worried about if you mean the screen stays off during or after call and you move the device away from your face. Desire HD has proximity sensor calibrator that fixes the problem but I don't think it works as-is for Desire S.

You can also try to clean up the proximity sensor in case it's filled with dust etc.

You can also verify that it's not broken with an app like this one.

http://xdaforums.com/showthread.php?t=1626611
[HTC Desire S] mickw1:
Yes your right my phone even on stock now is broke again. so I will try that ap.... think I must have a dodgy sensor :(

thx
[HTC Desire S] mickw1:
yeah fixed it... you were right it was dust, I took it apart and cleaned it and now it's working great..... now to install 13 nightlies again.:D:D

THX
[HTC Desire S] kchaisu:
20160207 build has improved first boot time and reboot faster than previous builds. Getting smoother and smoother. Setting Google account is also faster. Thanks Mustaavalkosta for your hard works.
[HTC Desire S] Sefy:
Running 20160207 on my spare phone, tested GPS successfully (using iGO, Here, Google Maps and Waze), Camera also worked flawlessly.

I only seem to be having issue with the root, while it does seem to work (using SuperSU 2.65), I can't copy the emoji font file to /system/fonts even though ES File Manager has write access.

Also, i've noticed some white graphical flashing on the bottom half, usually only after a reboot.

Lastly, after every reboot, it also Optimizes 1 App which slows the boot process...

This is after a clean install!

Either way, loving it so far and might switch to this phone once the little things are smoothed up :good:
[HTC Desire S] kchaisu:
I have been trying Chainfire Systemless Root for sometime and found that SuperSU beta 2.67 is working fine on CM-13. However, the responsiveness to request root access is rather slow in comparison to Privacy guard. On top of that when starts calling and some functions Privacy Guard is still working regardless of SuperSU being installed on the system. So, I decided to stick on Privacy Guard for CM-13, unless SuperSU beta 2.68 has been released and proved to be a better choice. Currently, CMFile manager has an issue on Privacy Guard and from Builds 20160207 onward, I have noticed some kind of white flickering during starting some Apps. However, these issues are too small to be annoying. Thank you very much Kylon, Mustaavalkosta, Paulb_nl and others who have been so kind in contributing their valuable spare time supporting the community.
[HTC Desire S] kchaisu:
I made clean installation of CM-13 sagaopt 20160210 build together with clean installation of Open Gapps 20160210 Pico. I found that the nightly provides very smooth boot up and setting with 30 mins of boot time, However, reboot time is less than one min. Tried not to delete system/lib/libjni_latinimegoogle.so; no keyboard FC sign shown and no keyboard showing up either. So the file should still be delete or rename as usual to get AOSP keyboard working. So far, the nightly is getting to good function, however, I did not test all functions, just regular phone usage. In addition, battery is very good; I am not a heavy user though. Thanks Kylon, Mustaavalkosta, Paulb_nl and other teammate for the contribution.