yashsingh1/xdaforums huggingface dataset:
[Galaxy S Advance I9070 Android Development] mkaluza:
[MENTION=5695278]ChronoMonochrome[/MENTION]

You asked about quick method of comparing cm and vanir repos:

1) get vanir tree:

repo init -u ... -b kk44

repo sync

2) switch to cm

* repo init -u cm.... -b cm-11.0

* edit .repo/manifest.xml

- rename remote "github" to "cm" and add proper fetch url

* repo sync -n

3) undo edits (use git checkout -p or git reset --hard in .repo/manifests directory) to manifest.xml (so that repo init doesn't complain)

4) repo init back to vanir

now...

repo forall -j 8 -c "echo; echo \$REPO_PROJECT \$REPO_REMOTE \$REPO_RREV; git fetch --all"

it'll fetch all the repos fully

Now use

repo forall -j 1 -c "echo; echo \$REPO_PROJECT \$REPO_REMOTE \$REPO_RREV; git log --oneline vanir/kk44..cm/cm-11.0" | less

or

repo forall -j 1 -c "echo; echo \$REPO_PROJECT \$REPO_REMOTE \$REPO_RREV; git log --oneline cm/cm-11.0..vanir/kk44" | less

to get stuff that is in cm and isn't in vanir and vice versa

Empty entries mean that either there are no differences or that one of the remotes doesn't match (you can try use \$REPO_REMOTE and \$REPO_RREV instead of vanir/kk44)

But one way or the other it's a quick solution - a bit coarse grained maybe, but is a good start.

Of course the script in -c might just be a call to a script that can be made much smarter than simple git log, but that's for later.

BTW guys - I can see that there are some more security fixes missing from vanir, so you might expect another build in the future. I'll probably also try to:

- replace vanir stuff with cm where things are not vanir-specific

- enable lto flags

- use gcc 4.9 for android-eabi and gcc 5+ for the kernel

- replace linaro toolchain with something newer - latest linaro 4.8 I could find is from 04.2014 and I was unable to build my own. I'll probably try uber toolchain, Archi's toolchain, maybe sabermod.

"someday" of course ;)
[Galaxy S Advance I9070 Android Development] wolverinemaister:
thanks for still bringing us updates for this awesome rom :) one bug I experienced in all builds, if i set the statusbar and the notifications background panel to 50% transparency it forgets the setting everytime i reboot the phone.

Other thing, is it possible to add network speed to statusbar like in slimsaber? I'm not asking you to put it in the next update just asking whether i can add this feature to the rom :) i tried with different apps but they didnt "worked together" with the statusbar icons
[Galaxy S Advance I9070 Android Development] thetupacshow:
Dear Mkaluza could you advise me a file .zip or a mod that increase the audio quality? I tried viper4ndroid but it seems do not work on my decide, and your DSP manager neither...
[Galaxy S Advance I9070 Android Development] mkaluza:
Ok, will look into it.

If/when I find the commits, probably yes. In the mean time - have you tried xposed module?
[Galaxy S Advance I9070 Android Development] isaak:
Some commits for you, just in case:

https://github.com/hastalafiesta/fr...stemui/statusbar/policy/NetworkStatsView.java
[Galaxy S Advance I9070 Android Development] wolverinemaister:
I haven't tried it cause i heard it can cause a lot of trouble and it don't want to touch this perfect rom on that level.

Anyway sometimes i get the playstore fc when i start to use endomondo but only for the first time
[Galaxy S Advance I9070 Android Development] thetupacshow:
How can I change the State of SELinux?? I tried SelinuxModeChanger apk but it says "looks that you don't have Selinux or it is disabled"...

I need the Permissive mode of selinux
[Galaxy S Advance I9070 Android Development] mkaluza:
Thanks! It's a good lead for sure. When I'm done with my current (seriously overdue) stuff, I'll get to that ;)

it won't hurt to try (dalvik only of course) - until I changed all the things I needed I used xposed for some time - it's very stable, esp considering how it does things ;). The good thing about it is that it touches only the necessary things (with the modules of your choice), so if you don't enable the module, you don't make any changes - I wish more software worked like this... but simplicity is one of the most difficult things to achieve ;)

You need a different kernel - mine has it removed. But: you probably don't need it - unless you do some security related stuff, you're fine with 'disabled' (effectively it does the same as permissive). But if you were, you probably wouldn't be asking this question....
[Galaxy S Advance I9070 Android Development] thetupacshow:
I need it because I want to install a mod that increase the audio quality like THIS: could you please try it and tell me if it works, on my device it crashes. Someone advise to change the Selinux permission... If I can't tell me another mod please, right now with your DSP manager I do not hear differences
[Galaxy S Advance I9070 Android Development] isaak:
[MENTION=3329816]mkaluza[/MENTION]

Stagefright is still an issue despite latest set of patches, according to this article:

http://blog.exodusintel.com/2015/08/13/stagefright-mission-accomplished/

Basically Google is still distributing a faulty set of patches. :rolleyes:
[Galaxy S Advance I9070 Android Development] mkaluza:
Yes, I'm aware of it. It seems cm11 already has a patch for this (not included in my build). But from the articles I've read it seems this particular bug isn't so easily eploitable, and is only mp4 related, so no big emergency. But next build will have it.

I've tried using uber toolchain, but the rom didn't boot :( same with sabermod.... it seems linaro is the only one that works. But I didn't go deeper into this yet - it was just a quick test...

Anyway, thanks for being alert ;)
[Galaxy S Advance I9070 Android Development] thetupacshow:
I tried this AMAZING mod and it works perfectly!!

Did anybody else try?

Mkaluza you should put this on the next update, what do you think?
[Galaxy S Advance I9070 Android Development] Toni5830:
I noticed that with this ROM (actually also with other cm11 based roms if I'm not wrong) the lowest part of the screen, for about 2-3 millimetres the touchscreen is insensitive! I noticed coming from stock 4.1 where this problem did not existed!

Am I the only one?

Sent from Italy using Tapatalk
[Galaxy S Advance I9070 Android Development] Zouhuo:
Yes it's correct. Checking with a application drawing full screen. They are 2 almost 3 millimeters. I did not know it.
[Galaxy S Advance I9070 Android Development] #Henkate:
[MENTION=3329816]mkaluza[/MENTION] : Hello. I have found by mistake an app regarding stagefright issue, which claim to disable it: https://play.google.com/store/apps/details?id=devnull.stagefrightpropchanger . I haven't tested and i won't because I'm tired of restoring backups haha.

EDIT: An stagefright detector: https://play.google.com/store/apps/details?id=com.zimperium.stagefrightdetector . It found these vulnerability for me (on AOSP 4.4 at this moment):

1) CVE-2015-3829

2) CVE-2015-3864

3) CVE-2015-3827

4) CVE-2015-1538
[Galaxy S Advance I9070 Android Development] mkaluza:
I don't know about the first app... I wouldn't install it... As for the tester, my Vanir has only 3864 - will look for a patch and then upload a fixed version.
[Galaxy S Advance I9070 Android Development] Zouhuo:
I tested various combinations of calibration with .idc in /system/usr/idc files, but always the same result, no change is like that ignores these files.
[Galaxy S Advance I9070 Android Development] wolverinemaister:
Thanks for the tip i successfully installed xposed then the network indicator module :)
[Galaxy S Advance I9070 Android Development] GROY91:
Reboot Issue

Hi,

Found that after downloading or during dload phone is rebooting. Otherwise stable, how to correct it?
[Galaxy S Advance I9070 Android Development] mauromol:
This article might be useful to know what CVS-3864 is: www [dot] securityweek [dot] com/android-stagefright-vulnerability-not-patched-properly-google

Thanks for your work on keeping this ROM updated!!
[Galaxy S Advance I9070 Android Development] mauromol:
Do you have any news regarding Skype? It does not work for me with Dalvik either :(

It did work in CM 10 and 10.1 by Team Canjica, as well as in stock JB. I use Skype a lot and, so far, it seems to be the only bug I've found on your ROM :(
[Galaxy S Advance I9070 Android Development] mkaluza:
No. I don't have time for this and since I don't use Skype, it's not a priority for me. Maybe someday.
[Galaxy S Advance I9070 Android Development] mauromol:
Ok, thank you. Anyway, if I may do something to help you understand what's going on (i.e.: providing you with some logs or such), let me know. I understand you're doing this ROM mainly for you, anyway Skype is a quite popular app, I would help myself if I had the knowledge :(
[Galaxy S Advance I9070 Android Development] mkaluza:
It's not that I don't want to - I simply have no time because of other things I must do... And while I'd be happy to have Skype working, it's not essential, so it must wait...
[Galaxy S Advance I9070 Android Development] Zouhuo:
Hello [MENTION=3329816]mkaluza[/MENTION]!

When you can!

You can see the subject of the dead zone of the touch screen, it's pretty and all the edges!

I tried to change some settings in the .idc files and nothing.

A greeting
[Galaxy S Advance I9070 Android Development] Cyberdog78:
The automatic lighting is more darkness, why?

Inviato dal mio GT-I9070 utilizzando Tapatalk
[Galaxy S Advance I9070 Android Development] Zouhuo:
[MENTION=3329816]mkaluza[/MENTION], a track would think that Teamcanjica first generated ROM for the Codina model (3.8") and then migrated to Janice (4"), there maybe this problem, some preseteo at some C source coming from Codina.

---------- Post added at 01:32 PM ---------- Previous post was at 01:26 PM ----------

The automatic brightness has several parameters, see these details, the setup icon on the right, and restore values to see how he reacts.
[Galaxy S Advance I9070 Android Development] mkaluza:
I think this is a good lead - 0.2" gives 2.5mm on each side, so it makes sense. Try to poke around device specific repos - device_samsung_janice and device_samsung_codina - maybe you'll find something.

Automatic brightness sucks balls... Unfortunately those 5 levels are hardcoded in Samsung binary files. The sensor is much better - it has 512 different values which could be used for continuous brightness regulation, but it requires writing new sensor. It's not difficult (quite simple actually when you look at the sources), but i don't have time for this neither now nor in the foreseeable future :(

But if someone wants to learn something about android/Linux/c/java, it's a good exercise.
[Galaxy S Advance I9070 Android Development] isaak:
[MENTION=3329816]mkaluza[/MENTION]

Brightness issue in attachment, easy to reproduce.

Thank you to Triboo & gianpassa from Androidiani community.
[Galaxy S Advance I9070 Android Development] Zouhuo:
I think I found something!

It is in the kernel, more precisely:

drivers/input/touchscreen/mxt224e_devconfig.h

#define T9_XRANGE (800-1)

#define T9_YRANGE (480-1)

#define T9_XLOCLIP 20

#define T9_XHICLIP 20

#define T9_YLOCLIP 40

#define T9_YHICLIP 31

#define T9_XEDGECTRL 143

#define T9_XEDGEDIST 40

#define T9_YEDGECTRL 143

#define T9_YEDGEDIST 80

#define T9_JUMPLIMIT 18

....

quite different from the initial values of teamcanjica diego-ch (values 0):

drivers/input/touchscreen/device_config.h

#define T9_XRANGE (480-1)

#define T9_YRANGE (800-1)

#define T9_XLOCLIP 0

#define T9_XHICLIP 0

#define T9_YLOCLIP 0

#define T9_YHICLIP 0

#define T9_XEDGECTRL 0

#define T9_XEDGEDIST 0

#define T9_YEDGECTRL 0

#define T9_YEDGEDIST 0

.....

It will be something to this?

there are many more values that have to see that it is, but in principle it would have to prove how you react to this change.

When you can!
[Galaxy S Advance I9070 Android Development] edukardo:
Could someone please take a look at cocore kernel for those values?
[Galaxy S Advance I9070 Android Development] Zouhuo:
It would be good comparison, however believe that also have different values.

It is a subtle problem than you realize when you using particular applications and notice that only now we realize.

We would realize if someone tells us if have the same problem with the ROM Stock + Kernel Cocore.

What we should do is try to modify, compile the kernel with the new values and test.
[Galaxy S Advance I9070 Android Development] edukardo:
Couldn't find device_config.h in Cocafe's kernel. No line like "#define T9_XRANGE".

I think we need [MENTION=3329816]mkaluza[/MENTION] take a look on it.

Must wait for him.
[Galaxy S Advance I9070 Android Development] Zouhuo:
Keep in mind that the file device_config.h is the first, almost starting point, now it seems to have become mxt224e_devconfig.h. It is my guess.
[Galaxy S Advance I9070 Android Development] edukardo:
Easy method to test the bug.

Enabling `Show Point Location` in Developer Settings to debug the touches

You could see top and bottom dead zones.

---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------

Found Cocore's in https://github.com/cocafe/i9070_ker...drivers/input/touchscreen/mxt224e_devconfig.h

#define T9_CTRL 0x8B	// Disable amplitude change : 0x1 << 3

#define T9_XORIGIN 0

#define T9_YORIGIN 0

#define T9_XSIZE 18

#define T9_YSIZE 11

#define T9_AKSCFG 1

#define T9_BLEN 0x10	// Gain of the analog circuits in front of the ADC [7:4]

#define T9_TCHTHR	32	// touch Threshold value

#define T9_TCHDI 2

#define T9_ORIENT 1	// 0x4 : Invert Y, 0x2 : Invert X, 0x1 : Switch

#define T9_MRGTIMEOUT 10

#define T9_MOVHYSTI 1	// Move hysteresis, initial

#define T9_MOVHYSTN 1	// Move hysteresis, next

#define T9_MOVFILTER 0x2F	// Filter Limit[6:4] , Adapt threshold [3:0]

#define T9_NUMTOUCH 10

#define T9_MRGHYST 70	// Merge hysteresis

#define T9_MRGTHR 70	// Merge threshold

#define T9_AMPHYST 10	// Amplitude hysteresis

#define T9_XRANGE (800-1)

#define T9_YRANGE (480-1)

#define T9_XLOCLIP 20

#define T9_XHICLIP 20

#define T9_YLOCLIP 40

#define T9_YHICLIP 31

#define T9_XEDGECTRL 143

#define T9_XEDGEDIST 40

#define T9_YEDGECTRL 143

#define T9_YEDGEDIST 80

#define T9_JUMPLIMIT 18

#define T9_TCHHYST 5	/* V2.0 or MXT224E added */

#define T9_XPITCH 50	/* MXT224E added */

#define T9_YPITCH 50	/* MXT224E added */

#define T9_NEXTTCHDI 2

Could someone test the bug in stock+cocore?
[Galaxy S Advance I9070 Android Development] Zouhuo:
mhhh this seems to have been a false alarm!

I just installed the stock rom with the same result. That is, the nearly 3 mm dead exist in both custom ROM and the Stock ROM. [MENTION=4769087]Toni5830[/MENTION], something to say?
[Galaxy S Advance I9070 Android Development] Toni5830:
Well, I would say the problem does not appear on stock, but since I'm not on stock (still on Vanir) and you are testing this on stock, you must be right! :)

Whenever I'll try again stock rom (probably not very soon) I'll report

Sent from Italy using Tapatalk
[Galaxy S Advance I9070 Android Development] isaak:
I tested it yesterday, stock rom with cocafe kernel has the same issue.

Maybe we should focus on skype issue (crash at startup), there is a new major version here:

http://blogs.skype.com/2015/09/03/skype-redesigned-for-android-iphone-and-ipad/
[Galaxy S Advance I9070 Android Development] mkaluza:
If you've come this far, maybe you could try and build the kernel yourself? ;) It's not difficult and i think i even added a readme on how to do it (where to get initramfs etc.) - my raid array is nearly dead, I have no cash for new hdds and I'm running off an USB stick, so i don't have much space to work with (maybe i could build the kernel (not atm), but rom is out of my reach)

Values seem to suggest that this might be it, especially that it happens on cocore as well, which also has non zero values there... has anybody tested stock _kernel_? I suspect ROM doesn't have much to say here.

Btw all you guys are a great community ;)
[Galaxy S Advance I9070 Android Development] barD1k:
Mkaluza fix the Skype! :banghead:
[Galaxy S Advance I9070 Android Development] isaak:
You forgot to add this:

:D
[Galaxy S Advance I9070 Android Development] mkaluza:
Now go and read my last post carefully...

Besides guys - I'm no java/android programmer. All the things i did here were quite generic and system-wide, but when it comes to debugging java/native app/lib, it's a black box for me - i have no experience, no environment set up to do it efficiently, and right now even no pc... It goes double for app i don't have source code for...

Your best chance of having this fixed is to find someone, who has already fixed it on some Vanir 4.4 based ROM (or any other where Skype wasn't working initially in a similar way) and ask him/figure out how to do it. But if no-one has fixed it so far, I'm quite sure it's beyond my reach for reasons as stated above (not to mention severe lack of time).
[Galaxy S Advance I9070 Android Development] Epirex:
You have to understand that the developers do not make magic :p
[Galaxy S Advance I9070 Android Development] edukardo:
Waiting for Zouhuo kernel. Hohoho

---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------

Related to the dead zone of the screen, we must not forget that our device was developed for Gingerbread. Since and thanks to Odin, no one flashes gingerbread. But could be good to take a look if this problem comes from the start.

We need volunteers to test it in GB. Don't look at me!
[Galaxy S Advance I9070 Android Development] wolverinemaister:
You banged your head too much into that keyboard maybe that's why you forgot how to search :]

Here is the skype you need
[Galaxy S Advance I9070 Android Development] mkaluza:
Does it work? I can't test it myself because i use ART, and they say it doesn't work with it
[Galaxy S Advance I9070 Android Development] wolverinemaister:
It's working (with dalvik*), I've been using this version of skype years ago :) Couldn't try it with art cause after reboot it stays dalvik
[Galaxy S Advance I9070 Android Development] isaak:
ART or dalvik?

If you don't know the difference, most probably you used dalvik (default setting for KK).
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Hello, just wanna to ask, how did you apply lto flags to build? When I added -flto to TARGET_arm_CFLAGS and TARGET_thumb_CFLAGS in build/core/combo/TARGET_linux-arm.mk, I got clang complaints about unused optimizations flag, and also some errors when linking libdl library(unfortunately I can't remember what exactly). When I apply -fwhole-program, I don't have libdl linking errors but there are many undefined references when bionic is being linked(and also same story with clang). My toolchain is uber GCC 4.9, I also tried GCC 4.8, without a success.
[Galaxy S Advance I9070 Android Development] mkaluza:
I didn't - at least not successfully - that's why it's a to-do ;). There are variables inside one of the makefiles - grep build dir for LTO to find them.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Yes, l know, but you mentioned that previously you tried to apply lto and it failed to boot, so it at least should was be compiled, and that why asked it.

UPD. ah, okay, right now I remembered that you mentioned on github some problems with bionic https://github.com/mkaluza/android_...621a#diff-a5ecec4305a32a2cd2de357b6b74b682L64 .

Thanks, I'll try!
[Galaxy S Advance I9070 Android Development] mkaluza:
About link errors. I had those with uber toolchain - the only toolchain i was able to boot from was linaro and of course aosp. Uber and sabermod either didn't build or didn't boot.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Applying LTO worked for me with Uber tc 4.9, apparently because of default vanir optimizations removal. I also applied almost everything from your vanir_build repo (only except -O3 flag), partly applied -ffast-math and has built everything in ARM mode(according to some math benchs I has built, ARM mode behaves much better than THUMB). The only issues were chromium(had to use prebuilt one) and libavcodec, which failed to build(didn't get what flag was an issue, just reverted all flags to default for this lib). Honestly, I didn't expect that it even will boot, especially because of applied ffast-math(which is only partly applied, though), which some claim impossible to apply. Btw, just in case, following patchset allows to apply LTO to kernel as well: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/experimental .

UPD. yes, although I somehow avoided bootloop, there are severe problems with bionic, I've to try once again with linaro or aosp toolchain or/and either without -ffast-math, because bionic might not like it.
[Galaxy S Advance I9070 Android Development] Sidman3278:
Blueiss screen display at 10% or lower brightness

Hi [MENTION=3329816]mkaluza[/MENTION] [MENTION=4982868]hastalafiesta[/MENTION] [MENTION=4881398]PolishVodka[/MENTION],

I am getting blueiss screen at 10% or lower brightness after flashing your roms since 22/6 to latest update. I am getting same since halstalafiesta's august builds. :confused: Not sure what is causing this.

I tried with stock rom as well as polishvodka's omni 5.1.1, this is not the issue with these roms.

Can I get quick suggetions guys?

Thanks,

Sidman3278
[Galaxy S Advance I9070 Android Development] Zouhuo:
Vanir is dead again?
[Galaxy S Advance I9070 Android Development] mkaluza:
It's as dead as my pc :P but since you've successfully compiled the kernel, maybe you can take up from here as well ;)
[Galaxy S Advance I9070 Android Development] isaak:
I found a working skype version for this rom, right here:

http://www33.zippyshare.com/v/geoSJdoJ/file.html

It's 4.9, more recent than 4.7 version posted before.
[Galaxy S Advance I9070 Android Development] mauromol:
Thanks, but version 4.9 was already posted before as well. A recent Skype is the only thing I really miss for this ROM, it's an application that really needs updates, because older versions are quite buggy.
[Galaxy S Advance I9070 Android Development] isaak:
4.9 is the most stable I found, 5.2 would be great except the fact skype call is broken.

Only hope for you to have continued skype updates is asking support in this vanir section (in particular to Derek Hunter):

https://plus.google.com/communities...0/stream/cbf38439-f183-4240-ae87-d853d442ed62

If you want to produce a logcat, I can help you with that.

These skype bugs are present also in their 5.1 vanir roms, so they could be interested to produce a commit for our old kitkat rom, if you link this topic. Chances are small, though.
[Galaxy S Advance I9070 Android Development] mauromol:
I am of course available to provide logs and anything else (if I'm told how to), however I don't think the Vanir team will ever fix this if they haven't yet. Also, even if they did, I don't have the necessary knowledge to then build a new Vanir Resurrection ROM image by myself to apply such fix (my programming experience is on other platforms and contexts). And I understand mkaluza has given up, unfortunately.

It's sad because I'm at the point that I'm almost forced to buy a new phone: after many years of experiments with this crap-phone (the Galaxy Samsung S Advance), having an unusable stock ROM (freezes all the time, even on phone calls => phone calls lost => quite bad for a smartPHONE!) and many other unofficial ROMs full of many big or small (and very annoying) bugs, I finally came here in the hope to find just an Android 4.x working/stable ROM (with recent security fixes) but soon after I did it was abandoned too. I use Skype for work and I need it, I also find it much better on VOIP calls than Whatsapp (for which this phone seems to be not fast enough), other apps are not widely spread in my country, so they are not an alternative.

Just my own thoughts, no offence to anyone (on the contrary, I'm really thankful to mkaluza!). If I had the knowledge, I may have tried myself to fix this, but although I'm a software engineer, I don't really have the time to learn all the things that are required to do that.