yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] vojtah1:
I'm sorry but I don't know how/what file.

It does not boot so no logcat and I'm unable to copy file from a system to sd card.
[HTC Desire S] moschman:
Hi Kylon

i use at the moment the KK rom from Mokee an i will check out your rom soon.

Is Lollopop faster as Kitkat on the desire S?
[HTC Desire S] vojtah1:
I managed to get this file from a system, is this helpful?
[HTC Desire S] kylon:
This does not seems a cm12 log

Which system?
[HTC Desire S] vojtah1:
I formated everything, installed cm-12-20141221-UNOFFICIAL-saga, gapps and than moved that that file using twrp to sd and posted.

After installind it says "script succeeded result was [/system]" not sure if that is OK.
[HTC Desire S] ren0065:
20141221 darkness

Hava the same problem, when installed reboot then darkness.

rom: "cm-12-20141221-UNOFFICIAL-saga"
[HTC Desire S] docertabum:
Do you have latest twrp recovery?
[HTC Desire S] kylon:
Seems the problem is related to new changes (thx Mustaavalkosta) so it will not boot.
[HTC Desire S] Mustaavalkosta:
Yeah, I was just about to share a log from a new ace build from today so here it is in case someone wants to compare to saga: https://dl.opendesireproject.org/mustaavalkosta/logs/20141223_surfaceflinger_vsync_loop.txt

Build made on December 13th is still working fine. I'm taking a break for the holidays so figuring this out will be on halt on my part.

Edit: Here's also git log since 2014-12-13 00:00:

https://dl.opendesireproject.org/mustaavalkosta/logs/changelog-since-201412130000.txt
[HTC Desire S] Saf98:
Maybe you have to make it compatible with the new hboot reengineered 7.2x?
[HTC Desire S] ralfbergs:
I have a pretty recent one, 2.8.0.0, and I have the same issue w/ cm-12-20141221-UNOFFICIAL-saga people reported here (black screen after reboot).
[HTC Desire S] ren0065:
My TWRP ver is v2.8.0.0

Do I have to delete ".android_secure" in SDCARD?
[HTC Desire S] kylon:
new test build up
[HTC Desire S] ralfbergs:
[MENTION=3334728]kylon[/MENTION] Did a clean install (i. e. wiped everything, even used a clean uSD card) -- got same black screen as w/ previous build (cm-12-20141221-UNOFFICIAL-saga.zip)...
[HTC Desire S] kchaisu:
Same here. I could not get the log. Thanks, Kylon.
[HTC Desire S] JonathanKang:
same here. black screen for the latest build
[HTC Desire S] ralfbergs:
I tried it again to make sure that I didn't do anything wrong -- same result. So I fear there's a problem with this latest build.

Thanks anyway, [MENTION=3334728]kylon[/MENTION]. I very much appreciate your efforts... I'm still enthusiastic how well Lollipop performs on this old phone, and I will gladly spend more time testing new builds...
[HTC Desire S] kylon:
I should have some free time today, i ll try an other way.
[HTC Desire S] Mustaavalkosta:
It's probably good to note that ace didn't have blackscreen issue last week. Bootanimation plays just fine. The issue is that it just keeps playing and playing and boot doesn't go forward.
[HTC Desire S] kylon:
Mmm, this is not a good news.

Which recovery are you using on ace? maybe there are new changes that break installation(i mean, you can install but it s not installed properly)

About your error i reverted latest surfaceflinger changes about qsb(in next build).have you already tried this?
[HTC Desire S] ralfbergs:
Sorry for being ignorant, but with "ace" you mean a Galaxy Ace?
[HTC Desire S] Ammiraglio:
Desire HD
[HTC Desire S] vojtah1:
Last available twrp is 2.8.0.0. Some Lollipop related changes were made in version 2.8.2.0.

Maybe [MENTION=352178]devilkin[/MENTION] can update his recovery?
[HTC Desire S] ralfbergs:
Thanks!
[HTC Desire S] Mustaavalkosta:
My recovery has been TWRP 2.8.1.0 for sometime now. Yeah, I already rolled frameworks/native back to remove those latest BSP changes but it didn't help which makes me conclude it's not surfaceflinger per se. paulb_nl suggested that those flooding surfaceflinger warnings have been there before but they haven't been so floody because log fills with other things too. This makes sense too but I haven't verified how many occurances of that warning are there with previous working builds. No new ideas or thoughts yet what could be causing ace's issue though. I'll keep you updated if I make any progress although our symptoms are not identical.
[HTC Desire S] paulb_nl:
Happy new year!

I found the issue with the black screen freezing. Its caused by /system/bin/auditd. If you flash that file from a previous working build then it should boot. For ace we had an extra issue with /sd-ext added to our fstab which caused the infinite bootanimation.
[HTC Desire S] ralfbergs:
Happy New Year to you and all the others as well!

You're da man!

The above indeed fixes the boot freeze issue, I'm currently booting the DEC-29 build... :)

Thanks a million!

---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------

Just in case people don't know how to update the ZIP file and re-sign it the following may help (I had to find out first, too!):

http://www.learn2crack.com/2014/02/sign-android-apk-zip.html

I used

unzip cm-12-20141211-UNOFFICIAL-saga.zip system/bin/auditd
touch system/bin/auditd
zip -uv cm-12-20141229-UNOFFICIAL-saga.zip system/bin/auditd

to update the ZIP file, then re-signed as per the above URL.

---------- Post added at 08:55 PM ---------- Previous post was at 08:02 PM ----------

First observations:

Home button not working

Status Bar "Quick Pulldown" feature not working (right edge of status bar pulls down Quick Settings); this used to work in most (all?) previous builds.

Can't add Google account with the Google Apps I successfully used so far (gapps-lp-20141117-minimal-edition-gps736-320dpi-signed.zip); I realize that we're now on Android 5.0.2, maybe this is the reason? Will try it with newer Google Apps...

Front cam still not working
[HTC Desire S] paulb_nl:
Does your home button work if you don't install gapps? Format /system before you install CM12.
[HTC Desire S] ralfbergs:
NAK.

ACK.

I formatted everything BUT my /sdcard. Should I also delete .android_secure on /sdcard (which I forgot this time)?
[HTC Desire S] JonathanKang:
report for the latest build 1229

In the latest build 1229,

1. The home button doesn't work

2. The lockscreen doesn't work (when I turn off the screen and then turn it on, the lock screen doesn't appear)

3. The notification doesn't work and cannot access the quick settings (It worked at the every beginning, but later on it just didn't work)

4. The Messaging app works well.

5. AudioFX and Music app work well.

6.front camera doesn't work.
[HTC Desire S] kchaisu:
Thanks, paulb_nl, by replacing the mentioned file the system booted up. Google Play, front camera, lock screen, and home key do not work. Wifi hotspot is working fine. Here is the logcat is case someone is interested.
[HTC Desire S] Mustaavalkosta:
Nightlies

I test ran my build script last night and now the first nightly build is out. Our website download mirror info is updated accordingly. These will be built 6 hours later than 11.0 nightlies for now. I'll probably drop 11.0 builds to weekly schedule soon and then 12.0 nightlies will take the regular 00:30 PDT schedule spot.

As saga's first nightly went past the midnight (UTC) and got today's (20150102) timestamp it will be overwritten with new build tonight when the build script runs from crontab. Just keep this in mind if you talk about the cm-12-20150102-UNOFFICIAL-saga.zip here. There will be 2 different versions of it. This won't affect future builds though.

I'm not sure what's exactly going on with the previously announced codefi.re maintenance as there were some complications so nightlies may be suddenly disrupted if they take the server I'm using down for OS change and upgrades.
[HTC Desire S] kchaisu:
Thank you very much Mutaavalkosta for being so kind in bringing DS up to date with Android development. I am very appreciated your contribution. I shall try the nightly, whenever there is any issue, I shall keep your team informed.
[HTC Desire S] ralfbergs:
I'm very thankful that you, [MENTION=3334728]kylon[/MENTION], and all the others involved here bring new power to this old handset.

I hope you don't mind if I ask a couple of newbie questions, as I would like to understand everything behind.

So there is a project called OpenDesire, which strives to bring new Android releases to HTC Desire devices, so far Desire HD and Desire S. I assume that the previous firmware builds [MENTION=3334728]kylon[/MENTION] has kindly published here were also due to this project, right?

Now you announced that you will also make available nightlies for the Saga device. Does that mean development for Saga has now become BAU (business as usual), and Saga will profit from any progress the same way the Desire HD (Ace?) will do?

Also, I noticed that you have a GitHub project, and that seems to include a FOTA server. Does that mean that "one day" there might be FOTA updates available, so that users can conveniently benefit from any (security) fixes you might be publishing? Will your code changes/additions eventually be merged with the CyanogenMod sources one day, so that there is a big chance for long-term support?

Moreover you operate a BugZilla. Would you prefer to receive any issues via BugZilla, or via this thread here in the forum?

Finally, there is an IRC channel. Is this for "ad-hoc" support requests, like if I have bricked my device and need help urgently?

Thanks again, this is my first dive into installing alternative firmware builds on Android handsets, and I'm greatly impressed by everything!
[HTC Desire S] Mustaavalkosta:
Yeah, I just have access to a server that will produce nightlies automatically. No big differences to builds kylon has build on his own machines. These are just automated from repo sync to upload.

As long as there's someone to maintain saga and codefi.re servers keep running there will be automated builds. These devices share some parts and differ from others but in general, yeah, we benefit from each other.

There are no plans currently to bring OTA updates to saga due to technical limitations on the server side. Ace users paid for a server I'm using to host backend server and also builds and it has very limited amount of space available. If we can scrape up enough donations to upgrade the virtual server to one with larger disk space available then there's a possibility of OTA updates for saga too but like I mentioned there are no plans for it at the moment.

I don't think there's much chance to be getting official CM status/support and I haven't been very interested to even try as there is next to nothing to gain from it. Lollipop may also very well be the last iteration of Android that is even meaningful to run on this old devices.

Kylon decided not to use bugzilla for saga so report saga bugs here on XDA. I wanted to have bugzilla for ace but this purely about personal taste of how to do things and I don't want to force anyone to do anything they don't want as long as this is a hobby.

There are not that many people on the IRC channel yet that it would be reasonable to assume to get quick help there but I'll help as much as I can when I'm around. Without a device and thus experience my help for saga issues is quite limited though. I've been using IRC for various communication needs for over a decade so it's just natural for me to have place to talk about this and that in addition to Android related things thus the channel was created.
[HTC Desire S] ralfbergs:
This is about the above build downloaded today (2015-01-02) at 17:50 UTC+1.

Lock screen works

Home button works

All four icons in app dock populated.

"Quick Settings" available by pulling down right edge of status bar

"Flashlight" icon suddenly available in "Quick Settings"

There's suddenly a new "Performance" section in "Settings"

Correct APN activated (for the very first time! Previously I had to manually activate it!)

Full IPv6 connectivity via WiFi (although this hasn't been an issue so far) using built-in "Browser" web browser

Front cam still not working

Messaging > Settings > Manage SIM card messages > SIM capacity: correct values shown for first time (IIRC!)

"Music" app working

Phone > Settings > Call Settings > CDMA Call Settings: Do not seem to apply to Saga (since it's not a CDMA phone?)

Titanium Backup can restore backups!

(2015-01-04) Google Account setup: Whereever your Google Account is required: The text entry field where you need to enter your login (e-mail address) is still invisible (or at least extremely hard to recognize, actually you can only guess where it is and then "blindly" click there).

This is by far the most stable, most complete build I've ever tested on Saga. Very well done, guys!!!

I will update this list later with any eventual new observations,

KR,

Ralf
[HTC Desire S] ralfbergs:
I have bare metal. What do you need? How much HD space, how much traffic (per month) would you expect?

Ok, I was naive enough to think that as soon as your code has been included into the official CM code, Saga users might even more benefit from OSS development, and also chances that some day development ceases are lower.

Why? Due to memory (RAM or flash?) constraints?

Ok, fair enough, and of course fine for me.

Sure. I personally would also prefer some kind of issue-tracking software, but as you say people should have fun doing this, and if they want issues reported here that's fine of course.

Thanks for your response and patience.
[HTC Desire S] kylon:
op updated

thanks [MENTION=3382363]Mustaavalkosta[/MENTION]
[HTC Desire S] ralfbergs:
I can't get any GApps package working -- any recommendation which package to try?
[HTC Desire S] Mustaavalkosta:
5-10GB storage and 2TB / month traffic (if we estimate 200 downloads of 220MB zips every day) is probably a good starting point to land on the safe side. Cheapest OVH VPS provides 10GB storage and 10TB bandwidth.

Nah, there are some general quality standards too in addition to having fully compatible device tree (which we don't have and probably won't have without CAF 3.4 kernel and so on). CM support for devices works pretty much the same way as ours does now: no device maintainer, no official builds. So, I don't think there's much safety in official status either. Builds will end if device maintainer quits and no one fills in.

It's just getting awfully slow. I went through Google's startup wizard today and I must say it wasn't very fast and pleasant experience like it should be. And then there are also internal storage size issues arising as the base system size increases. ART also increased storage requirements quite a lot. In a nutshell, physical hardware limitations will start causing more and more issues and line must be drawn somewhere if we want to hold some kind of level of usability and not just run the newest Android because we can. Personally, I'm not very interested to keep going beyond what's reasonable.

---------- Post added at 11:58 PM ---------- Previous post was at 11:57 PM ----------

Can you check how much free space is there on /system partition after flashing just the nightly?
[HTC Desire S] paulb_nl:
Is the Desire S laggy for a few mins after booting e.g. much stuttering while scrolling?
[HTC Desire S] vojtah1:
Not sure where to get free space at /system

Storage says that there is 0.92GB available and 114MB used by apps.

btw. First boot took +-2 minutes.

So far no lags.

Flashlight is not working

edit:

No Gapps, Mikey (Pressy) does not work.
[HTC Desire S] kchaisu:
Yes, it is a bit.

---------- Post added at 11:31 PM ---------- Previous post was at 11:24 PM ----------

gapps-lp-20141218-minimal-edition-gps434-240dpi_signed.zip is working for me. But I could not set google account so google play and browse do not work for me.
[Galaxy Note 3 Q&A, Help & Troubleshooting] QA Bot:
Q&A for [factory]-(firmware-sm-n900)

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [factory]-(firmware-sm-n900). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy Note 3 Q&A, Help & Troubleshooting] alihaleh:
not update

Why do not update dear friend :crying:
[XPERIA X1 Q&A, Help & Troubleshooting] QA Bot:
[Q&A] [ROM] PURE Windows Mobile 6.5 upgrade for the SE XPERIA X1 [26 NOV 09 | SEX1 R

Q&A for [ROM] PURE Windows Mobile 6.5 upgrade for the SE XPERIA X1 [26 NOV 09 | SEX1 R5.07]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM] PURE Windows Mobile 6.5 upgrade for the SE XPERIA X1 [26 NOV 09 | SEX1 R5.07]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[XPERIA X1 Q&A, Help & Troubleshooting] ArgyrisneoV:
Upgrade to 6.5

Does this rom support Greek language?
[XPERIA X1 Q&A, Help & Troubleshooting] gtrab:
Support for this ROM was abandoned after 5 years live and on line

To be honest, this ROM is quite obsolete and I can't remember if it supports greek or not...
[XPERIA X1 Q&A, Help & Troubleshooting] ArgyrisneoV:
Upgrade to 6.5

So is there a way to update this old phone?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] japun:
hey guys is it possible 2 zoom videos in o2 exec ... and if it is ... watz the procedure ... thanx sry if m sounding dumb ... new 2 dis .... hope u understand ... watin 4 rep .... thanx again
[Android Q&A, Help & Troubleshooting] MeDo ALi:
Hello Everyone, this is my first thread here.

A couple of days ago I received Android L on my LG Nexus 4 via OTA and I got to say that I'm really loving it :good:, it's been very smooth and fast . . I'm having some problems with battery draining faster than KitKat, but I can live with it.

My main problem is that I discovered a very strange bug - or maybe it's a bug in my OS only - and I would like to share it with u. Today I was trying to get some lives in Candy Crush Soda and in order to do that I have to forward the date as if it was tomorrow (28/11) and then hit the multitasking button to go back to the game and click on the level I'm at and then I should hit the button again and go back to revert the date to today's date (27/11) and then I have to hit the button again to go back to the game and click Play. But here I discovered the bug .. the multitasking button doesn't work when you change the date and then revert it back, and in order to make it work you have to change the date again to whatever date you set the first time or you just restart your phone.

This bug maybe doesn't affect a lot of people but it's still a bug.

I would appreciate if you tried that and told me if you encountered the same bug and if there's a solution for this please share it with us. Thank you in advance
[Android Q&A, Help & Troubleshooting] MeDo ALi:
anyone??
[Android Q&A, Help & Troubleshooting] MeDo ALi:
Did anyone even try to see if this bug exists??
[Android Q&A, Help & Troubleshooting] simmac:
Maybe we are not cheaters.
[Android Q&A, Help & Troubleshooting] MeDo ALi:
well .. forget about how I found the bug, but it exists! even if you just tried to change the date and then revert it back without any purpose, the multitasking button will stop working .. so it's not about the game or the cheat, it's about a bug in the system
[Android Q&A, Help & Troubleshooting] simmac:
Have you tried rebooting?
[Android Q&A, Help & Troubleshooting] MeDo ALi:
well, rebooting seems to solve the problem .. but that's not a solution I guess because when I change the date again the problem will be back
[Android Q&A, Help & Troubleshooting] MeDo ALi:
looks like it's a known bug .. found this https://code.google.com/p/android/issues/detail?id=79307
[Android Q&A, Help & Troubleshooting] MeDo ALi:
anyone facing the same bug? any solutions??
[Themer General Discussion] TUNAKHAN:
Hi,

I've already sent you e-mail about it but let me do it again but this time here. I'm volunteer for the whole translation (i dont know how many stirngs do i have to translate). What i know is totally worth it. I'm working 8:30 am to 05:30 pm so every other minute i'm available.

Looking forward to your response.

Have a nice week!

Yaşar Tuna Zorlu

Civil Engineer

+905393595969
[Galaxy Note 3 Q&A, Help & Troubleshooting] QA Bot:
Q&A for [ROM][4.3][beats sound]fast and powerful-NoTe3 N900 v2.0/02.01.2014

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][4.3][beats sound]fast and powerful-NoTe3 N900 v2.0/02.01.2014. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy Note 3 Q&A, Help & Troubleshooting] alihaleh:
problem

The plan does not create a problem for the phone :confused:
[Galaxy Note 4 Q&A, Help & Troubleshooting] lockieio:
Hi folks. I love so much this game but dont understand why this game stutter with such powerful phone as note 4. Is this game related or what? This happens specialy when lot of zombies appears on the screen. Thank you for your support
[Galaxy Note 4 Q&A, Help & Troubleshooting] Iamapotato:
Interesting... PvZ2 is the only game that has actually lagged on my Exynos Note 4 (SM-N910C). I especially notice it right after every level when there's the flower in the middle of a white background. The flower lags and I have to wait quite a long time before the map begins to react to my fingers after a slow load.
[Galaxy Note 4 Q&A, Help & Troubleshooting] lockieio:
So is this game related? I dont understand...
[Galaxy Note 4 Q&A, Help & Troubleshooting] lockieio:
Anyone knows the solution? :(
[Galaxy Note 4 Q&A, Help & Troubleshooting] paniqueado:
I have the same issue with PvsZ 2 and my note 4 is SM-N910C too.

:confused:
[Galaxy Note 4 Q&A, Help & Troubleshooting] bronx:
Must be an issue with optimalisation for Exynos, as on sd805 it runs perfect regardless of action in the screen.

Game is so so though, part 1 is much better imho.
[Sony Xperia M] QA Bot:
Q&A for Deodex for Xperia M Dual

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Deodex for Xperia M Dual. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Sony Xperia M] nawar.t:
Will it work on C2005
[Sony Xperia M] RedLedLight:
It says in the title XPERIA M DUAL.

It only takes 2 taps to thank somebody here.