yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy 551 Callisto] steve8x8:
A factory reset wasn't enough for my (s2e-enabled) Callisto (at build 1177) to install Jenkins 1201. Only after formatting /system, the flash succeeded. Susprisingly enough, the QWERTZ keyboard (protected by a /system/addon.d script) did survive (how?).

Wakeup time is brilliant (close to what I know from GB times).

Zausan DeviceTest still thinks that there's a flash, as does the camera. (And wasn't there a light sensor?)

Bluetooth turns on, and sees my laptop (and more), pairing request is sent/received properly.

IPSec VPN connection to my Fritz!Box at home is established.

Edit 1: USB connectivity to a Debian Wheezy laptop: MTP starts Rhythmbox; PTP wants to start Shotwell; UMS gives

Dec 10 13:03:03 marvel kernel: [13695.497722] Initializing USB Mass Storage driver...
Dec 10 13:03:03 marvel kernel: [13695.512095] scsi4 : usb-storage 1-7:1.0
Dec 10 13:03:03 marvel kernel: [13695.512410] usbcore: registered new interface driver usb-storage
Dec 10 13:03:03 marvel kernel: [13695.512418] USB Mass Storage support registered.
Dec 10 13:03:04 marvel kernel: [13696.520786] scsi 4:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
Dec 10 13:03:04 marvel kernel: [13696.528445] sd 4:0:0:0: Attached scsi generic sg1 type 0
Dec 10 13:03:04 marvel kernel: [13696.533032] sd 4:0:0:0: [sdb] Attached SCSI removable disk

but fdisk doesn't see the disk, and cat /dev/sdb returns "No medium found".

"adb devices" returns a serial number of "0123456789ABCDEF".

Audio files (transferred using "adb push") can be played, even in the background and while asleep. I don't have my BT speaker with me, though. (A utility to rebuild the media db would be nice.)

At the moment there's little more I can test, but I like it :D Thanks a bunch!
[Samsung Galaxy 551 Callisto] ehsan-black:
device: beni

build #1203

first of all thanks for your hard work.

here are the things that I've tested in 3 days:

- kernel is much more stable. freezes and random reboots are rare. it just happened once in 3 days.

- in previous build wake up delay with ondemand Governor was about 7 - 8 seconds. in this build wake up delay is around 2-3 seconds. it's not annoying anymore.

- I can hear audio stutters while screen is off.

- Bluetooth works well.

- wifi is not really as stable as last build. sometimes when my RAM is almost full ( when i use viber and line simultaneously ) wifi disconnects and it can't find any network till I restart wifi from setting.

- USB transfer rate(UMS) is still low. around 800 KB/s !

- data connectivity indicator works well in both mobile network and wifi.

I attached dmesg and latencytop .

thanks again! :)
[Samsung Galaxy 551 Callisto] steve8x8:
After half a day more:

- WiFi indeed sometimes "forgets" what it was connected to, after sleeping (with WiFi disabled during sleep)

- Battery discharge curves seem to get worse, but that's the first one, dated Jan '11, it might just be too old and worn out by now

- GPS: I was not able to get a GPS fix, not in Zausan, and not in GPS Status - the latter even "primed" with A-GPS data. After 15 minutes each, and an insane amount of battery capacity gone, I stopped watching :( (The Callisto never was really breathtaking when it comes to GPS fix times, that's why I used to use a BT GPS instead.)

(**Edit: I was able to get a fix eventually, after replacing the battery it still took about an hour with no obstacles but also no A-GPS. Rinse, repeat?

**Edit2: To my surprise, I could even pair with a very old GPS-12C that didn't work with the GB Callisto. Both BlueGps and BT GPS Provider worked well. My favourite configuration.)

- Can we have a SmartAss governor incorporated into the next build, pretty please?
[Samsung Galaxy 551 Callisto] kronflux:
I would love to see the SmartAssV2 and/or the SmartAssH3 governors added, as well as bumping the max clock speed to 800mhz, as we already know from very similar phones/devices that the processor will run very smoothly and stable at 800, without compromising battery life -too- much.
[Samsung Galaxy 551 Callisto] Venkatesh:
[MENTION=5051035]Mm7[/MENTION], thanks for your efforts on kernel 3.x. Well, i built aokp 4.1.2 using your kernel 3.x sources. The problem is, it is not booting. Goes back to recovery after some seconds(at that time, the screen went black for a few seconds ~2-3 secs, before going back to recovery). Any thoughts on this?
[Samsung Galaxy 551 Callisto] Mm7:
Do you get the same behaviour in cm-11?
[Samsung Galaxy 551 Callisto] Venkatesh:
No. Cm11 is good. And even tried porting cm11 kernel and flashing it over jb compiled with kernel 3.x sources. Still the same behaviour.
[Samsung Galaxy 551 Callisto] steve8x8:
As build 1177 is no longer available on Jenkins, could someone please update post #3? Thanks...

Re the latest (1201) build, is there hope to get UMS working with Linux? I don't really hope for OTG (as the USB chip FSA9240 [?] doesn't seem to support this)...
[Samsung Galaxy 551 Callisto] Venkatesh:
[MENTION=5051035]Mm7[/MENTION], why is kernel 3.x not booting with older versions? Flashing 2.6 kernel on top of it boots the device. For a testing, i extracted kernel 3.x from aokp build and packed it with kitkat ramdisk, flashed it on cm11, kernel loaded fine.

Kernel loads for ~4-5secs(adb device shows device serial for some secs) and goes back to recovery. Can you help me, please?
[Samsung Galaxy 551 Callisto] psyke83:
You can't just drop a newer zImage into a boot image and expect the ROM to work. Several userspace libraries are built using the kernel headers, so when you update the kernel, the userspace libs will be incompatible. You have to recompile the full ROM with the 3.0 source.
[Samsung Galaxy 551 Callisto] Venkatesh:
You missed my previous post. I actually ran a full compilation using 3.x sources. And the rom refused to boot with new kernel. See, What i am trying to say is that kernel isn't booting with jb 4.1.2, but the same zimage works with cm11(so, it compiled fine and no problems with zimage). I thought, it might be my mistake, but after flashing 2.x kernel, jb booted fine(so, there isn't any issues with rom). I thought the problem is with kernel 3.x. Just enquiring with Mm7.
[Samsung Galaxy 551 Callisto] psyke83:
OK, well, the problem is most likely with the TLS register. Older versions of Android userspace are expecting the kernel to use TLS emulation, but we support TLS emulation on CM11 only for the recovery kernel. The solution: enable CONFIG_TLS_USERSPACE_EMUL=y in your main defconfig.
[Samsung Galaxy 551 Callisto] Venkatesh:
[IMG="pico cm12"]http://i.imgur.com/bYvtmaI.png[/IMG]

Pico booted with 3.0.101 kernel.

And, about kernel 3 on 4.1.2, using that config enabled the kernel to boot but before that, device rebooted(after pressing "reboot system" in recovery) itself 4 to 5 times before it gets detected by adb. But the screen is all black after that(screen stuck here) and logcat shows memory map issues. I am making a clobber and will check again to make sure everything is good.

And one more thing, i can't flash cm11 or cm10(with 3.x kernel) normally like factory reset, flash rom and boot. There are many dexopt erros if i flash normal way. I had to format system, wipe dalvik cache(sometimes 2-3 times wiping required) to successfully boot cm11.

---------- Post added at 02:42 PM ---------- Previous post was at 02:01 PM ----------

@psyke83, is this change required? I am getting compile error without that config.

hardware/qcom/display/libgralloc/framebuffer.cpp:281:27: error: aggregate 'mapFrameBufferLocked(private_module_t*)::msmfb_metadata metadata' has incomplete type and cannot be defined
hardware/qcom/display/libgralloc/framebuffer.cpp:283:19: error: 'metadata_op_base_blend' was not declared in this scope
hardware/qcom/display/libgralloc/framebuffer.cpp:286:18: error: 'MSMFB_METADATA_SET' was not declared in this scope
make: *** [/home/venkatesh/aokpjb/out/target/product/tass/obj/SHARED_LIBRARIES/gralloc.msm7x27_intermediates/framebuffer.o] Error 1
[Samsung Galaxy 551 Callisto] psyke83:
Without that change it will compile the old kernel... so, yes. Your problem is most likely caused by old kernel headers installed to device/samsung/*/include (which is something we've stopped doing in the androidarmv6 branches as much as possible). Remove them so that they don't override the 3.0 kernel headers and it might work... but I can't really help any further if you don't point me towards your current source.

Edit: I looked at the link again - it's not the change I was expecting. That's only for fetching the proper repo during first sync, so it's not important. The change won't affect the build error you quoted.
[Samsung Galaxy 551 Callisto] Venkatesh:
No, i was talking about boardconfig NO_HW_VSYNC(to enable fake vsync events or to tell the compiler that our hardware don't support hardware vsync events?).

ifdef BUILD_WITH_30X_KERNEL
TARGET_NO_HW_VSYNC := false
endif

It is set to true in my aokp board config. And about kernel headers, i removed 2.x headers, when i started compiling with 3.x kernel. Replaced with headers from kernel 3(i know you set the config to use headers directly from kernel).

https://github.com/CyanogenMod/andr...ellybean/libgralloc/framebuffer.cpp#L280-L289

I just commented out that NO_HW_VSYNC part to avoid build error. Is it any useful?

source
[Samsung Galaxy 551 Callisto] psyke83:
I don't remember why it was needed (to fix a build error, or to fix a display issue with the mdp kernel driver). You're opening yourself up to lots of problems by working with old and unmaintained branches; that's one reason why I don't like to touch older branches...
[Samsung Galaxy 551 Callisto] Venkatesh:
In cm10.1 display drivers you used that code inside target_msm7x27 and something like msmfb. Okay, you removed that config from boardconfig in resurct kernel 3 commit(specified that commit in my previous post). Why did you removed it? As far as i understand armv6 devices used it to fake vsync events.

Offtopic: It is just personal preference. I like stability+performance. Till cm10.1 everything works like camera etc. But cm10.1 is a bit too heavy(but aokp 4.2.2 is too good) and above versions are heavy laggy and ofcourse missing camera too.

Jb 4.1.2 and ics are a bit lightweight in resources and fully stable. I can run 50-60 apps without any lag(including gapps, play services too).

Aokp,slimbean are very close to pure stock android and are full stable in my opinion. Why not compile aokp or some aosp based roms? Is it any specific reason to compile cm only?

I am not discouraging any one, it is just my opinion. You, androidmeda, erikcas, Mm7 are heroes for us. You people took us to kitkat and we would never forget your contribution. We are fans of you and your work( you may be a fan of some actor/actress/person). Because you always to tried to listen and help us out. Thank you from the bottom of my heart.

Edit: Do i need to update bionic sources like you did in cm11 sources for tls support?
[Samsung Galaxy 551 Callisto] psyke83:
I don't compile for other devices simply because my laptop is not up to the task of compiling multiple projects lately (lack of disk space, etc). The problem specifically with the older branches, however, is a lack of support and security updates.

The newer Android branches probably have support for fake vsync baked into surfaceflinger that wasn't present before. That's most likely the reason why it's no longer necessary. MDP 3.0 doesn't really support vsync events, so there's no point in enabling it.

To get hardware TLS working you might need to make changes in several projects - not just in bionic. You can grep the source for ARCH_ARM_HAVE_TLS_REGISTER to be sure.
[Samsung Galaxy 551 Callisto] Venkatesh:
Offtopic: No, no. I am not asking you people to compile for other devices.

Why not aokp kitkat or omni or slimkat? Anyways leave it. It is just a few changes needed to build those branches if we have a working cm tree. People like me can do it, if people like you are there to lend a hand.

Ontopic: okay. I'll check with the sources.
[Samsung Galaxy 551 Callisto] WinKarbik:
[MENTION=3877378]psyke83[/MENTION]

Could you update the links?
[Samsung Galaxy 551 Callisto] Venkatesh:
[MENTION=3877378]psyke83[/MENTION], is gerrit under maintenance? It is not opening for the last 2 days(at least for me).
[Samsung Galaxy 551 Callisto] psyke83:
No, there haven't been any major changes. Most androidarmv6 developers are currently focused on initial cm12 support, so it'll take a while for attention to return back to the kernel bugs.

It's been working fine for me (and I've been using it a lot in the past few days).
[Samsung Galaxy 551 Callisto] Bhargav97:
Working fine for me too.
[Samsung Galaxy 551 Callisto] steve8x8:
If that refers to the "please update links" request - all (!) Jenkins links in posting #3 now throw an error (and even the horribly broken Callisto build 1193 cannot be reached anymore. 1201 for Callisto is still there (but for how long? I still don't understand when builds get dropped from the list, and the server in general)
[Samsung Galaxy 551 Callisto] psyke83:
The Jenkins server has limited disk space, so any experimental builds that are not manually set to "keep forever" will eventually get purged in order to free disk space for other builds. I didn't mark any of the 3.0 kernel builds with this flag, because they weren't intended to be kept for a long time. The focus was on getting some specific testing done in order to identify and fix the remaining bugs (mmc, audio stutter, etc.).

Take a look at the recent history feed for the experimental builds on Jenkins, as well as our gerrit, and you'll see that we're currently preoccupied with the task of getting the cm-12.0 branch operational. The issues with the 3.0 kernel can wait, but won't be forgotten - the new kernel is going to be used on the new branch as well.

So, for the time being, the kernel 3.0 builds are gone. The only way to update the links is to trigger new builds, and that would be a waste of time and resources, as we haven't committed any new fixes that need to be tested. Once things have settled down with cm12, we'll get back to working on the kernel bugs. I'm fairly confident that development on the cm11 branch won't be dropped, at least not until the new branch has become stable enough to replace it (if that ever happens).

BTW, in case you or anyone asks, the cm12 builds on Jenkins are not working. Don't risk your device by flashing any of those builds.
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks a lot for this thorough explanation!

While I'm still unsure whether USB storage behaviour is a kernel issue or not, I'll try to keep my patience. As not even my "backup" Moto-E has received L yet, I'm not in a hurry.

Enjoy the season!
[Samsung Galaxy 551 Callisto] Venkatesh:
[MENTION=3877378]psyke83[/MENTION], why not disable selinux for now in cm12? Because adreno2xx is failing to load when selinux is enabled. I don't know much but this guy http://xdaforums.com/showthread.php?p=57479348 is having the problems like us and he managed to boot it anyway(i know it is an armv7 device, still he got same problems like us).
[Samsung Galaxy 551 Callisto] psyke83:
[MENTION=5400898]HandyMenny[/MENTION] and [MENTION=5051035]Mm7[/MENTION] are working on the msm7x27 integration changes, I'm just helping with small bits and pieces when I can. The SELinux stuff can be fixed, but I already recommended for them to leave SELinux disabled, at least temporarily, so that other issues can be focused on.

I've already disabled SELinux on bcm21553 so that I can focus on other things (but that's also because the yaffs2 driver is corrupting partitions after security contexts have been set in the filesystem).
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] 20141227 OTA works fine on Callisto, updated via delta updates.
[Samsung Galaxy 551 Callisto] steve8x8:
But that's a ROM using the "old" kernel, right? Or did you manage to merge 3.0 and nightly?
[Samsung Galaxy 551 Callisto] Mm7:
OTA builds use the old kernel
[Samsung Galaxy 551 Callisto] steve8x8:
That's what I was wondering about (thank you for clarifying) - it would be clearer if there wss a separate thread for cm11/kernel3 (not necessarily callisto-specific then) but probably it's too late to get this separated, so well...
[Samsung Galaxy 551 Callisto] Venkatesh:
[MENTION=3877378]psyke83[/MENTION], can you make and merge a commit that accepts any version of libcamera.so? Because, I can take 640*480 pictures and record video using cooper libcamera(source built libcamera lacks colors). And people like me likes to have partial working color pics rather than colorless pics. Thank you.
[Samsung Galaxy 551 Callisto] steve8x8:
Um, I might be missing something again, but my Callisto camera is colourful with Jenkins build 1201 (Dec 7). Panoramas are a PITA (slooow, not b&w though), and video recording doesn't even start (is this a codec issue, perhaps?), but I get colours where I get images.
[Samsung Galaxy 551 Callisto] Ansh2000:
Any news about cm12. development ?
[Samsung Galaxy 551 Callisto] steve8x8:
What has happened to Jenkins?
[Samsung Galaxy 551 Callisto] Ansh2000:
RC 14 is coming soon as last update for cm11. Our callisto is going to die here.

Thanks to all of the members of Armv6 team for your hard work and support for our device.
[Samsung Galaxy 551 Callisto] steve8x8:
Is this a typo? My RC14 copy is dated back from early January...

... and actually I had to reflash my Callisto with this one today - there was an issue with the CWM 6053 recovery unable to boot into the system, even after a full reflash (had to use Odin to flash a CWM from Jenkins).

What puzzles me now is that the NIGHTLYand RC builds still use the 2.6 kernel - what has happened to the KERNEL3 efforts? Could they not be merged? And, if they could, would I be able to dirty-flash the ROM over the existing one?

Checking the download area again - I had missed the "final" build (from Feb 11, not marked as such, but as it's the last one...).

As UMS mode still doesn't work (and probably never will - what about OTG?), I'll push the ROM using adb, and dirty-flash that now.
[Samsung Galaxy 551 Callisto] JoshinPl:
So this is the end of the support for cooper?
[Samsung Galaxy 551 Callisto] steve8x8:
Apparently, and unfortunately, yes - now the whole jenkins host androidarmv6.org domain has gone.
[Samsung Galaxy 551 Callisto] Corvisier:
Hi guys,

Does anyone have the last build from around 11 February? I can't find a zip anywhere in the interwebs.

I tried building from androidarmv6 sources but I always get a out of memory exception and can't build anything.

Thanks
[Samsung Galaxy 551 Callisto] JoshinPl:
There are updates of this rom? Are they 5.0 based?
[Samsung Galaxy 551 Callisto] John Blueh:
The download links are not working
[Samsung Galaxy 551 Callisto] steve8x8:
http://xdaforums.com/showpost.php?p=61722839&postcount=14
[Samsung Galaxy 551 Callisto] JoshinPl:
is there any possibility to port the version of the proevious post into cooper? and the same with the keyboard fixes, that are only for callisto. Thank you :)
[Samsung Galaxy 551 Callisto] Mm7:
Hi,

I belive that new builds should be released in order to protect users from the recent android flaws:

"Stagefright"

"Serialization"

NOTE: Accordingly to this post, "Certifigate" doesn't affect cm (and so androidarmv6).

Download links:

cooper [TESTED: YES]

beni [TESTED: NO]

tass [TESTED: NO]

galaxy5 [TESTED: NO]

callisto[TESTED: NO]

gio[TESTED: NO]

Screenshots
[Samsung Galaxy 551 Callisto] steve8x8:
Where are these builds coming from? It makes little sense to fight a vulnerability using something that has unknown sources.
[Samsung Galaxy 551 Callisto] Mm7:
I built them myself.
[Samsung Galaxy 551 Callisto] steve8x8:
My apologies for being over-cautious. Back in the times of jenkins at androidarmv6.org, I used to download from there, and also got the "release notes" (list of changes since previous version, or of the last couple of weeks). What has actually changed in the new ROM?

I cold see a CMUpdater.apk still referring to download.androidarmv6.org/api, but that domain doesn't exist any longer, and I failed to find out who might have owned it before. Anyone has some details?
[Samsung Galaxy 551 Callisto] Mm7:
Basically nothing (no new features or msm7x27 specific fixes/updates). I just pulled frameworks_av security patches + some extra commits (from this to this) and libcore security patch

Ignore CMUpdater, we no longer release OTAs. As far as I know, erikcas owned Jenkins and gerrit servers.
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks a lot for the explanation. I did some inspection of the ROM myself and was surprised to see no changes to everything named *stagefright*... Too bad that the original download location doesn't exist any longer, this will reduce the user base of the new ROM a lot :( How many people will find this particular thread, and read its 28 pages?

Nevertheless - did I already say Thank you?
[Samsung Galaxy 551 Callisto] steve8x8:
Ummm... doesn't seem to work on my Callisto.

Error executing updater binary. First thought: Doesn't this ROM cooperate with TWRP 2.7.0.0?

Restoring TWRP backup, to go back to CWM, for further tests...

With CWM 6.0.5,3 restored, I get the same error "(Status 7)".

Flashing the original ROM works :(

Memory limits??? I remember that /system had been quite tight...

( Edit: )

Unpacking 20150905 and 20150211 (last official release), on my laptop

$ du -sh 2015*/system/
177M	20150211/system/
181M	20150904/system/

Indeed /system has grown in size by almost 4MB.

The partition on my phone has 181.3M; Final has 672.0K free in /system, with s2e installed and configured.

So there's an explanation for the install error.

The lion's share of the additional size seems to come from priv-app/, but there have been gradual growths overall, it seems (Apollo +600k, Gallery +400k, etc.).

Checking apk files there seems to be a general trend towards bigger .png and resources.arsc files.

Where to start cutting out redundant stuff? (I noticed that Term.apk has gone.)

I'd suggest to remove app/LiveWallpapers{,Picker}.apk (1.3MB), Pico files (tts/lang_pico, 1.4MB), and at least half a MB somewhere else (leave out Gallery2.apk, suggest QuickPic?; remove Calendar.apk?) - looks like a tough job. Is there still hope?

( edit2: )

Have there been any special tricks during the build of the 14 RCs and the Final, to keep resource images small? [MENTION=3877378]psyke83[/MENTION], were there any modifications applied during previous Jenkins builds we're missing now?

I also observed that the files in the Jenkins builds, up to RC14 and Final, carry March 2014 timestamps while the new build has the "magic" but midleading Feb 29, 2008 (although both don't seem to be true).
[Samsung Galaxy 551 Callisto] Mm7:
I switched to "releasetools-extras-tiny" also for callisto, this should move some more apps to extras. This is a new build. Please, can you test it?

AFAIK, nothing was done to reduce build size. But: 1 Jenkins server may have a different build environment than my computer, so something could be different 2 In the last post I forgot to say that I re-synced my source tree so a lots of packages got updated and this lead to a higher packages size (more updated -> more features -> bigger) [especially translations got many updates].