Related
Hi all,
say that I'd like to try a CM7 custom compilation (e.g., removes half of packages, ...) for the sake of learning, what steps do you suggest to get into?
Compiling a full debuggable ROM and test it in the Android emulator?
Could I test It along with SE kernel (e.g., with the latest)?
In the emulator should i to install the SE related packages in order to set up the Xperia HW emulation?
Cheers!
There's a package of scripts named kitchen, made of a member here that let you customize a rom. There is even a root method that we were talking about the other day.
https://github.com/dsixda/Android-Kitchen
Hi kissmyarch,
i meant bulid It from the sources, not through the kitchen way ;-)
Oook sorry then.
LoL take a rom add ur theme, choose ur fav apps! Choose ur modules! And ur done! Custom rom is ready!
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
LoL nevermind then! This is what happening lately on mini pro forums, I just revealed how its being done!
Ravencz said:
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
Click to expand...
Click to collapse
I agree with Ravencz, building from sources is more funny than cooking... the fact is that you find a tutorial on cooking in the forum (and it's simplistic as hell) and no an hint on how to port your own CyanogenMod on your mini pro... what a pity...
Hoping someone on the devs' side will read this post ;-D... Cheers!
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
galvic said:
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
Click to expand...
Click to collapse
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
@galvic: CM doesn't seem a cooked ROM to me, since they provide the repository from which you could clone the sources. CM seems more a fork (with enrichments/improvements) of AOSP and cooking a CM isn't the same of building its source.
So the thread is correct, because if i fetch and edit the Gingerbread branch of CM source, actually i've built a custom CM7.
Instead of linking those megabytes of ROMs, shouldn't be better working on CM's branch and attach the related patches that brought to a custom CM ROMs, as patches for kernel modules and so on? Benefits of patches are small downloads size, learning what people do in making your beloved ROM, ... On the other side you've to set up a developer's environment, that is a bit expensive (Gingerbread sources are around 7 Gigabytes, if i'm not wrong).
I don't know if Gingerbread is the best choice with the unchangeable kernel that SE stuck on our smartphone, but say Gingerbread or Froyo or whatever the fix you've to make on a CM are (logically) the same until someone will make an hackish strike and take down that damned bootloader.
See you!
Ravencz said:
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
Click to expand...
Click to collapse
Sorry but CM is also bult on sources of AOSP
galvic said:
Sorry but CM is also bult on sources of AOSP
Click to expand...
Click to collapse
Of course it is, but it's modified
Ravencz said:
Of course it is, but it's modified
Click to expand...
Click to collapse
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
thats what free-xperia project did, use miniCM resources!
galvic said:
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
Click to expand...
Click to collapse
Nope, compiling gives you control over things such as source code, compiling options/flags for optimization (say that our mini pros have ARMv6 processor, why having a ROM built for generic ARM architecture? It doesn't make any sense... that's the source-oriented GNU/Linux distro way as Gentoo: compiling kernel and all application for your machine in order to have best performances and responses), possibility of adding removing code (e.g. libraries, system applications) and so on.
Cooking let's you modify something pre-made and doesn't give you *full* control on it ;-)
If we've to take over the world, we've to do it in the proper way! :-D
Cheers
Hey...just wondering...How to put acpuclock-7x30.c in boot.img?or after rooting the phone and use root explorer?
I found this file from another thread(http://forum.xda-developers.com/showthread.php?t=1320270&page=2)
Kudos to hartej
for a this device which has the same cpu/gpu as mine and i wanted to know where this file is and how can i replace it in order to use the new frequency and steps!!
Thank you!! (Yes i am a lil bit noob,sorry)
nfsmw_gr said:
Hey...just wondering...How to put acpuclock-7x30.c in boot.img?or after rooting the phone and use root explorer?
I found this file from another thread(http://forum.xda-developers.com/showthread.php?t=1320270&page=2)
Kudos to hartej
for a this device which has the same cpu/gpu as mine and i wanted to know where this file is and how can i replace it in order to use the new frequency and steps!!
Thank you!! (Yes i am a lil bit noob,sorry)
Click to expand...
Click to collapse
Not a trivial matter. Here's a synopsis: You'll have to get a compatible kernel source tree, then get a linux environment set up with the cross compiler chain for your target system (Arm), then modify and compile the kernel. Once you've got a good working kernel, you need to put together a boot.img for your device. You'll need a working boot.img to tear apart. You break the boot.img down into its ramdisk and kernel, then rebuild it using your new kernel. Once you've got a working boot.img, you flash it to your device.
Each of the above steps involve substeps that could fill entire posts or more. Like I said, this is anything but trivial.
Are you sure there's not a custom kernel/boot image already compiled for your device? That would be the easiest route.
Thank you sooo much for aswering!!
No,there isn't any kernel available for my device WT19i really only cm7 is the other option instead of stock rom/kernel...
It has though the ability to chose 1.6ghz instead of the stock 1.0ghz for my device,but i was just asking weather this could be done...
Sooo...i need to follow some kind of tutorial to do this on my own huh..?
nfsmw_gr said:
Thank you sooo much for aswering!!
No,there isn't any kernel available for my device WT19i really only cm7 is the other option instead of stock rom/kernel...
It has though the ability to chose 1.6ghz instead of the stock 1.0ghz for my device,but i was just asking weather this could be done...
Sooo...i need to follow some kind of tutorial to do this on my own huh..?
Click to expand...
Click to collapse
Are you sure about the kernel source? The Linux GPL requires that OEMs provide their modified kernel source code as part of the terms of use. I don't know what a WT19i is, but they probably have a site somewhere that has the kernel source code. If not, then there's really not much you can do.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
answer...
Well...it's a very new device(Live with walkman is it's normal name)
The only site i could find something is http://developer.sonyericsson.com/wportal/devworld/search-downloads/opensource?cc=gb&lc=en
but it doesn't have my device name anywhere except only the firmware version(which is the same with 4 more devices!!!! :S )
Soo...i can't do anything huh..?
Gene Poole said:
Are you sure about the kernel source? The Linux GPL requires that OEMs provide their modified kernel source code as part of the terms of use. I don't know what a WT19i is, but they probably have a site somewhere that has the kernel source code. If not, then there's really not much you can do.
Click to expand...
Click to collapse
Gene Poole said:
I don't know what a WT19i is
Click to expand...
Click to collapse
This: http://pdadb.net/index.php?m=specs&id=2979&c=sony_ericsson_wt19__wt19i_walkman.
Been looking on Google but can only find resourses related to Android 1.5. Any advice where to start would be awesome! Thanks
Sent from my GT-S5830 using xda premium
Custom kernels = github
Herpderp Adreno + Tegra.
Github is really hard to underdstand :-(dose anyone have any good link on how to use github.ok github on website and other is on terminal how to intergrate both.dose ketut have github so we can learn from his source.....:-\
Sent from my GT-S5830 using xda premium
Github is kinda easy to work with.....
Herpderp Adreno + Tegra.
nope, github is like heaven to coders and modders. its pretty easy to understand. just view the commit and see the difference, then apply the difference to ur local source. or just download the commit as *.patch file and patch ur local source using it. but if u urself had github account, just pull the commit and merge with ur source.
btw op heres a good reading
http://forum.xda-developers.com/showthread.php?t=1377467
http://forums.androidcentral.com/htc-hero-rooting-roms-hacks/8072-how-build-your-own-kernel-package-source.html
but basicly and most important thing is u need to know howto use linux.
Hello people
I flashed the new rom Feralab v18 and DoomKernel v.06 on my phone x10i but I have seen that sometimes it block or it goes in spurts.....I don't sure that it's the kernel, but because I wanted to prove even more, I'm here to ask you :
What are the new and best kernel after DoomKernel with over / underclocked or not?? thx
no answer?
I found this link:
http://forum.xda-developers.com/showthread.php?t=1345913
some of you have already tried these kernel?
for example:
2. Free Kernel 4.05.4 SE233
- Direct port of Free Kernel 4.05.4
- Include dual recoveries
ftf File: http://www.mediafire.com/?3tolzmam2tid2qu
Wifi Module: http://www.mediafire.com/?6f8zwogejf3i4gg
has anyone ever tried this kernel?
Almost all of kernel for X10i are very similar, because are based on stock SE sources. I am using Doomlord kernels, because they are stable and have good scailng and undervolting capability.
It also depends if u want locked or unlocked bootloader version
HeliumX10 said:
Almost all of kernel for X10i are very similar, because are based on stock SE sources. I am using Doomlord kernels, because they are stable and have good scailng and undervolting capability.
It also depends if u want locked or unlocked bootloader version
Click to expand...
Click to collapse
i have unlocked bootloader now i search the best kernel for flowing, performance and without big bug
Raschild6 said:
i have unlocked bootloader now i search the best kernel for flowing, performance and without big bug
Click to expand...
Click to collapse
As I told - I recommend Doomlord kernels. There are not any kernel with "big" bugs (i know only about Usb host bugs). Look into section "Android Development" and choose the right one you thing is for you
HeliumX10 said:
As I told - I recommend Doomlord kernels. There are not any kernel with "big" bugs (i know only about Usb host bugs). Look into section "Android Development" and choose the right one you thing is for you
Click to expand...
Click to collapse
i had found this post :
http://forum.xda-developers.com/showthread.php?t=1345913
but in this days i don't have time to try all kernel.
you know something about (2.3.7 Roms) :
2. Th Kernel Rev08-5 Cob06c
- Based on Th Kernel Rev08-5
- Include dual recoveries (xRec and doomlord modified CWM5)
- change in ramdisk to support fxp netd
ftf File: http://www.mediafire.com/?1981mxs5ifvx82s
Wifi Module: http://www.multiupload.com/0RODM897XW
or :
5. Free Kernel 4.05.4 Cob06d
- Based on Free Kernel 4.05.4
- Include dual recoveries (xRec and doomlord modified CWM5 with Touch Screen)
- change in ramdisk to support fxp netd
ftf File: http://www.mediafire.com/?zvv311m1oo4ay78
Wifi Module: http://www.mediafire.com/?6f8zwogejf3i4gg
Try a FreeKernel version, they are under freexperia team and their development were one of the bestest
HeliumX10 said:
Try a FreeKernel version, they are under freexperia team and their development were one of the bestest
Click to expand...
Click to collapse
ok i try in this days and then I'll tell you how it went
if you have other news write here
but.....i have 2.3.3 version stock but with Feralab Rom v18 i passed 2.3.9.
the Free Kernel 4.05.4 Cob06d is compatible with the Rom?
Raschild6 said:
ok i try in this days and then I'll tell you how it went
if you have other news write here
Click to expand...
Click to collapse
Goodluck!
Personally its just a guess for you - I am still on locked bootloader and tested all of locked kernels and free kernels were the best all the time.
HeliumX10 said:
Goodluck!
Personally its just a guess for you - I am still on locked bootloader and tested all of locked kernels and free kernels were the best all the time.
Click to expand...
Click to collapse
thx so.....why you still on locked bootloader?
Raschild6 said:
thx so.....why you still on locked bootloader?
Click to expand...
Click to collapse
Anytime bro
I am on locked bootloader still because I dont have any reasons to unlock it and because:
- there is no rom/kernel which requires unlcked bl which has something really necessary for me (eg. new major version of OS or some extra functionalities)
- once bootloader is unlocked you can brick your phone totally (and I dont have JIG and UART adapter for X10i).
- i have completely modded WB rom by myself - extremely clean with huge of free RAM and great CPU performance. Didnt found something like mine yet
Only one reason why I will (in future) unlock my bootloader is CyanogenMod 9 which is in development but currently it hasnt deep sleep and camera working. Only one reason is Android 4.0 no else
HeliumX10 said:
Anytime bro
I am on locked bootloader still because I dont have any reasons to unlock it and because:
- there is no rom/kernel which requires unlcked bl which has something really necessary for me (eg. new major version of OS or some extra functionalities)
- once bootloader is unlocked you can brick your phone totally (and I dont have JIG and UART adapter for X10i).
- i have completely modded WB rom by myself - extremely clean with huge of free RAM and great CPU performance. Didnt found something like mine yet
Only one reason why I will (in future) unlock my bootloader is CyanogenMod 9 which is in development but currently it hasnt deep sleep and camera working. Only one reason is Android 4.0 no else
Click to expand...
Click to collapse
yes!!! it's true!!....but i have unlocked bootloader even when I was a noob xD
last question : you have learned himself to build and program kernel-rom?
I'd like to start doing something, in java for example
Raschild6 said:
yes!!! it's true!!....but i have unlocked bootloader even when I was a noob xD
last question : you have learned himself to build and program kernel-rom?
I'd like to start doing something, in java for example
Click to expand...
Click to collapse
Haha I am really NOT a noob, but still dont have it
No no its too difficult - yes I am able to build a android kernel from sources a make a really few mods in it, but I cant say, that I am a developer... Even I am programmer in desktop C++ and desktop Java, I cant write any app for android, its much more difficult than a programm app for PC in C++ and desktop Java is completely different from Android Java for a pity I have tried some tutorial for veleoping on android and I was disgusted how it works badly...
I recommend you to start programming in C++ or Java in desktop environment first and later move on Android Java
And ROMs no, still modding released ones and for personal usage at a time. I wasnt ever thought about to release my mods here on XDA yet
HeliumX10 said:
Haha I am really NOT a noob, but still dont have it
No no its too difficult - yes I am able to build a android kernel from sources a make a really few mods in it, but I cant say, that I am a developer... Even I am programmer in desktop C++ and desktop Java, I cant write any app for android, its much more difficult than a programm app for PC in C++ and desktop Java is completely different from Android Java for a pity I have tried some tutorial for veleoping on android and I was disgusted how it works badly...
I recommend you to start programming in C++ or Java in desktop environment first and later move on Android Java
And ROMs no, still modding released ones and for personal usage at a time. I wasnt ever thought about to release my mods here on XDA yet
Click to expand...
Click to collapse
i just study 2 year of C# (class,OOP,windows form) and 1 year of C++ and java at school but i'm still far from create app
have you got some guide of programming in C++ or Java for create app or complete guide of developing on android ??? i can try with eclipse and some guide but there are only court and incomplete
Raschild6 said:
i just study 2 year of C# (class,OOP,windows form) and 1 year of C++ and java at school but i'm still far from create app
have you got some guide of programming in C++ or Java for create app or complete guide of developing on android ??? i can try with eclipse and some guide but there are only court and incomplete
Click to expand...
Click to collapse
Bad school then I have studied half a year of C++ and year of Java and it tought me to build some apps myself now. Must note that all with no UI, just command line but its more usable and resources free.
No sorry mate, I bought two thin books for C++ and Java, but sold them back very early. I prefer myself playing with code
As I told, not evan for android app - few months ago I searched how-to make a Hello World! for android. It was for Eclipse as I remember... And was disgusted how long was the whole code for it - about 40 lines of something between XML and Java.
So I dont have any...
121212121212121212
I vote for AOSP maybe the CM9 will be more hard to fix all that bugs and it's so much better start in 0
Good idea Fera!!!
also benjamin (scritch007) helped me a lot with 32kernel and actually we are doing it together...anyway , soon I'm gonna push the sources to github so we all could work on it...we hope to get it work perfectly but as fera said there is some limitations...
I think cm9.1 base would be a more clean, just released from google looking experience. And with you all the others working hard to accomplish x10 rebirth things should go well (If unwanted I'll delete this comment)
Sent from my X10i using xda app-developers app
if there is stuff that i can do to help in anyway once i recive my x10 my machine is good enough to compile roms and kernel leeme know :0 goodluck amin,scrticht and fera! maybe we could get some jelly flowing through our x10s
Don't wont to spam this thread but there is one more thing that is missing in CM9.
Its implementation of DASH sensor, especially light sensor, which might have great influence on battery.
Sensor in SE Stock ROM causes:
- increasing backlight (and power consumption) while phone is in intense light (sun) - which improves usability
- decreasing baclight (and power consumption as well) while in low light.
I know that J has some problems with finding a file for light sensor maybe U'll find it out
Sony released DASH sensors libs as open source but I'm not sure if its for 2010 xperia line http://developer.sonymobile.com/201...l-dash-developers-can-contribute-open-source/
Created new thread for CM9.1 based rom with fixes that Fera is talking about. The Hardware Video decoders video patch, I couldn't find one define, don't know where it comes from TARGET8x50.
Regarding the .32 kernel KTG based. I managed to get a booting kernel, when removing kgsl. But no camera, no charger (which can be annoying after a day of use ).
When activating the kgsl I had a blinking screen, and after a while it would reboot. And I would have to struggle flashing back a working kernel.
For info you can check my sources. The merge_fxp branch here
I would like to help, i have a pretty fast machine to copmpile but very slow internet (512/128).
I just have a small idea for the one like me that want to help.
Could it be possible for someone who already compiled a CM9 to build a VMWare VM with already all the needed stuff installed.
The linux version, SDK, make and build tools and a checkout of the CM9.
Then someone that want to help will just need to sync the repo and build.
What do you think of this ?
Best regards,
U.
ok firstly my two cents here
1. i have a access to goo.im build servers so i can make builds without any problem
2. we should maintain common repository for all this stuff (i think scritchz's repository for device tree is best, and Fera's kernel tree should be ok)
3. from the beginning we need to focus on 'fixing' rather than 'adding' GOLDEN RULE : fix stuff that is not working before adding tons of features to kernel and rom.
4. please no 'thank you for this' posts. someone please get in touch with original_ganjaman and get ensured that this remains dev-thread. i understand all feelings, but it becomes difficult to find necessary info there are posts that have nothing to do with development. if you want to chat come the General CHat thread and i will chat with you all day but not here please.
5. Linaro : forget it for now. let's just be able to build it. Linaro does not make ROM 500% faster or anything. i have used linaro and non linaro compilations for Xperia S. trust me nothing makes a difference.
6. kernel : focus on .29, .32 is not fully working yet. we will just upgrade parts and backport stuff from new kernels as and when needed.
right now one stuff that needs be done importantly is inline kernel and wifi building. (it's not good using prebuilts, because inline method will allow us getting changes merged to kernel at every ROM release. )
see this https://github.com/freexperia/vendor_atheros_wlan is the wlan driver released with X10 latest kernel source
this file https://github.com/freexperia/vendor_atheros_wlan/blob/master/Android.mk is compatible with GB build system
if you compile GB you'll see it builds, but when you go to ICS it fails because PRODUCT_COPY_FILES is depreacted.
we need a newer ar6002 wifi source that will enable hotspot. (because right now we use prebuilt libs so we use AWEXT in wifi_supplicant so it's not hotspot compatible)
and yeah we need to work with CM... it's the easisest to continue working with.
scritch007 said:
Created new thread for CM9.1 based rom with fixes that Fera is talking about. The Hardware Video decoders video patch, I couldn't find one define, don't know where it comes from TARGET8x50.
Regarding the .32 kernel KTG based. I managed to get a booting kernel, when removing kgsl. But no camera, no charger (which can be annoying after a day of use ).
When activating the kgsl I had a blinking screen, and after a while it would reboot. And I would have to struggle flashing back a working kernel.
For info you can check my sources. The merge_fxp branch here
Click to expand...
Click to collapse
Big thanks man.. the sources you mentioned is for. 32 kernel right? If so.. I'll damn juice it now...for Khalid i think maybe it's will try to mess with that.. being back from university.. thanks again
Peace
Sent from my ST18 using xda app-developers app
FeraVolt said:
Big thanks man.. the sources you mentioned is for. 32 kernel right? If so.. I'll damn juice it now...for Khalid i think maybe it's will try to mess with that.. being back from university.. thanks again
Peace
Sent from my ST18 using xda app-developers app
Click to expand...
Click to collapse
Yes sources are based on KTG.
One thing you should look at before anything is a definition
kernel-2.6.32.9/include/linux/msm_mdp.h
in struct mdp_img
remove uint32_t priv;
https://github.com/skritchz/KTG-Kernel_es209ra/commit/36c84cfc82e0f6092b4224f225edfe29619c8d0f
The mdp_blit request used by the Rom doesn't have this field, so it mixes every thing after this. This was leading to a "mdp_ppp src img size of zero" message in the kernel
You'll see in the code that there is still kgsl definitions, in fact I got into a bug when porting FXP sources, which made the rom boot . if you want to enable kgsl, you have to remove some lines in board_es209ra.c
line 2331 comment the whole following block
size = gpu_phys_size;
if (size) {
addr = alloc_bootmem(size);
kgsl_3d0_resources[1].start = __pa(addr);
kgsl_3d0_resources[1].end = kgsl_3d0_resources[1].start + size - 1;
pr_info("allocating %lu bytes at %p (%lx physical) for "
"KGSL\n", size, addr, __pa(addr));
}
That will enable kgsl but the rom won't boot.
thanks man.. i got it.. but without kgsl..its bad right.. so i think i will try to dig into board config..
and few words about linaro..yeah.. i didnt see much difference in kernel..at least..thought it will make some sence for rom compiling..at least everybody was saying about that..
peace
FeraVolt said:
thanks man.. i got it.. but without kgsl..its bad right.. so i think i will try to dig into board config..
and few words about linaro..yeah.. i didnt see much difference in kernel..at least..thought it will make some sence for rom compiling..at least everybody was saying about that..
peace
Click to expand...
Click to collapse
Actually for the use I've done of the rom, i don't feel that much a difference without kgsl, but I haven't try using games and stuff like that. The real main issue was the charger . Since flashing really take some battery I had to go back to current kernel really quickly.
Regarding linaro, don't know much about real improvement on our current rom.
scritch007 said:
Actually for the use I've done of the rom, i don't feel that much a difference without kgsl, but I haven't try using games and stuff like that. The real main issue was the charger . Since flashing really take some battery I had to go back to current kernel really quickly.
Regarding linaro, don't know much about real improvement on our current rom.
Click to expand...
Click to collapse
Lol i understand you.. btw..maybe you forget battery driver to compile?
CONFIG_MAX17040_FUELGAUGE
and only this.. dont select other ones...
and about KGSL...we are plannig to use HWA right? lol..
peace
@fera
So I shouldn't apply this patch yet?
http://forum.xda-developers.com/showthread.php?t=1411317
scritch007 said:
@fera
So I shouldn't apply this patch yet?
http://forum.xda-developers.com/showthread.php?t=1411317
Click to expand...
Click to collapse
no...not this... this one is ok for applying.. i'm talking about 2d harware rendering patch.. from linaro..it seems like its incapable or so... but i sved your framework..in case..because today will mess with newer kgsl..maybe it would be ok..
It seems airplane mod wlod was not here in FXP128 ....
EDIT : Kernel related so forget about it (thanks scritch007 for his help and answers to my "noob questions" !!! ...need further investigations ....
Btw if anyone got ideas, I'm ready to read ...
Cheers
would it be possible to just edit bluetooth stuff? casue without bluetooth flies airplane works...
mcsqwizzys98 said:
would it be possible to just edit bluetooth stuff? casue without bluetooth flies airplane works...
Click to expand...
Click to collapse
Two ways of doing things.
1) Find in the kernel what causes the issue.
2) In the CM rom, do not call make kernel call when Bluetooth is disable. (Easier to do, but I would rather find the reason for the WLOD).
Don't worry we'll have the air plane mode working eventually. (When it depends on other dev and or when I'll be done with exif stuff on the camera)
scritch007 said:
Two ways of doing things.
1) Find in the kernel what causes the issue.
2) In the CM rom, do not call make kernel call when Bluetooth is disable. (Easier to do, but I would rather find the reason for the WLOD).
Don't worry we'll have the air plane mode working eventually. (When it depends on other dev and or when I'll be done with exif stuff on the camera)
Click to expand...
Click to collapse
I'll report later tests I'll make tonight.. I'll edit this post.
EDIT : could not do many thing before now ... got a dmesg log here
Will look after it to understand which variable(s) are wrong ...
Don't hesitate to have a look at the log :highfive: