[Gta04-owner] ANN: first replicant 4 with 3.12 kernel available

[Alexandre Roumiantsev]

Hello

Here is a good discussion about a problem, connected with wakelock in
newest kernel:
https://bugs.launchpad.net/linaro-android/+bug/1006751  and
https://bugs.launchpad.net/linaro-android/+bug/1023985 
Simple temporary patch ( find in attachment ) announced there I add to
my experimental build. The result you can find and test from here:
https://drive.google.com/file/d/0B-rRgKAzYyoBQ0pOT1dNbVRXaGM/edit?usp=sharing

But possible solution of problem suggested here: 
https://android.googlesource.com/platform/frameworks/base/+/9630704ed3b265f008a8f64ec60a33cf9dcd3345%5E!/#F21
ant it is too far from our current situation, at least, it is not 4.0 or
4.2 version of Android. Please, look at table of current available
kernel versions:
>       * 4.0.x Ice Cream San, kernel 3.0.1 
>       * 4.1.x Jelly Bean, kernel 3.0.31 
>       * 4.2.x Jelly Bean, kernel 3.4.0 
>       * 4.3 Jelly Bean, kernel 3.4.39
So we should look too far ahead, in case using 3.12 kernel as base.

Alexandre

> Hello.
> 
> > > 
> > > Am 21.12.2013 um 14:39 schrieb Alexander Rumyantsev:
> > > 
> > >> Hello
> > >> 
> > >> 
> > >>>> which I have not meet when I have work with 3.0, 3.4 and 3.7
> > >>>> Problematic is wakelock facility. 
> > >>> 
> > >>> What is problematic with it? Any specific issues? What appears
> to be different?
> > >> 
> > >> If you look at any log ( adb logcat ) you will see a message:
> Couldn't get kernel wake lock stats
> > >> in many places. ( Most clean logcat you will see from this build:
> >
> >> https://drive.google.com/file/d/0B-rRgKAzYyoBbVhWZElYbC13Y0U/edit?usp=sharing )
> > >> Problem is that /proc/wakelocks is missing. 
> > > 
> > > Ok, that is something differnent. AFAIK the /proc file system is
> not an official API...
> > 
> > And I have a different view: /proc/wakelock is apparently deprecated
> > http://bamboopuppy.com/android-wakelocks/
> > 
> > "On older android builds you can check /proc/wakelocks"
> > 
> > So we should also think about upgrading Replicant from 4.0 to 4.x...
> > 
> > BR,
> > Nikolaus
> > 
> Trying to move ahead I am investigating a situation with wakelock in
> Replicant 4.2. It looks that some step to solutions is included into
> code.             
> However I do not know exactly - does full solution is included into
> Replicant 4.2 or not.
> Anyway I try to backport same code from Replicant 4.2 to Replicant
> 4.0.
> I get some success on this way. Here is a small patch:
> https://drive.google.com/file/d/0B-rRgKAzYyoBb3JGbUFqb0FYd3M/edit?usp=sharing
> and here is a build to test ( current Replicant 4.0 + this patch,
> replicant 3.12 kernel + patches, published above in thread, Lukas wifi
> patches is included as well ):
> https://drive.google.com/file/d/0B-rRgKAzYyoBOFNaWnFUOFAwZjA/edit?usp=sharing
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fb.patch
Type: text/x-patch
Size: 702 bytes
Desc: not available
URL: <http://lists.goldelico.com/pipermail/gta04-owner/attachments/20140216/b8b93546/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.goldelico.com/pipermail/gta04-owner/attachments/20140216/b8b93546/attachment-0001.bin>