Develop Bugs

[Q] Google goggles ipv6

Hi all,
I have Fat Free Froyo installed with the latest 14th Jan 2011 kernel voguimg-240x320-2.6.32-froyo-14-01-11_14.nbh edited to froyo & panel type 2 from t029000.massey.ac.nz but Google Goggles needs ipv6 support.
Is this a kernel problem or a problem with the build itself? I am experienced in linux, so can modprobe or insmod the ipv6.ko but I don't know where to get it from
Any help would be appreciated!

(message for kernel's developers) take this man! he can dev ipv6!

Jumping the gun there a bit
I triage bugs and work on stuff for Ubuntu. Have also ported a few linux bits to ppc64 (PlayStation 3).
I'm pinching the ipv6.ko from slayhers latest kernel build, hopefully that will work insmod-ding or modprobing it into the kernel thru the terminal on the Kaiser itself.
So, fingers crossed, this may be solved in 5 minutes!!

Didn't work, it must be compiled for a different platform...
Anyone have or know where to get a kernel for the Kaiser with ipv6 support, or failing that the correctly built ipv6.ko for the Kaiser so that it can be insmodded?

Getting it compiled in the kernel is the easy bit, although it does use up a lot of space which is limited in the kaiser's kernel so a little tweaking is needed. Getting it to work with the Kaiser's modem and the builds we currently use is a different matter unfortunately. It will take a bit of modding for it to work but it's more then achievable with a bit of free time. Wish i could buy that stuff!!If i get a chance i will get you the ipv6 module for the kaiser's kernel or a kernel with support for it so you can have a play.

I definitely look forward to it! If I knew how and what to modify I'd do it myself, but I thought arch-specific kernels had to be compiled on the arch itself? If that's the case, I can see how free time would be needed, it'd take hours or days to compile the linux kernel at 400MHz
I have compiled kernels before so if/when I learn how to do it myself, I could start to use my own git repo for more recent daily builds or something.
I'm also thinking about starting working on some *buntu stuff (I know Ubuntu is there for the Kaiser, but soem tweaks would help if I get a chance.)

Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?

xteejx said:
Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?
Click to expand...
Click to collapse
Yes, that is th correct make file to use. I have built the kernel with IPV6 support, haven't tested it but have attached the module to the post for you to try

Brilliant! I'll try it sometime within the next couple of days, although I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build, but I haven't economised too much.
I can see the the options for ipv6 in the ncurses menuconfig, so I guess it's just a case of enabling it and building the zImage right?
I seem to be having the old problem with the wifi though, and I know it's kernel related, but there are only patches for it, i.e. the wlan.ko, but can't see how to implement it myself so it's an all-in-one solution
When I get the hang of the Kaiser hardware properly, I might just push through a newer kernel from the armlinux site so watch this space

xteejx said:
I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build
Click to expand...
Click to collapse
How have you managed that??? What have you done?

I have no idea how it happened, perhaps the other devs add a load of useless options, but all I did was follow the instructions at that link above and compiled a zImage from the 2.6.32 arm branch, using the 2010 arm tools. Used NBHeditor to edit it for Kaiser, panel 2, froyo, flashed it and bang (not literally thank god).
I can't answer any better than that. I used the default options (for now at least) that the vogue build script uses for the kernel, but bluetooth, camera and gps work. No internet connection as yet either through the network or wifi, dumno what I've missed there, and no ipv6 (but can add that easily enough). Wifi doesn't work either, but I'm working on it, although that MAY be the reason why it's so fast...maybe it's missing a few options...still unsure at this point.
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.

xteejx said:
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.
Click to expand...
Click to collapse
That isn't true, all tested changes are pushed to git, you can see what has been changed and how from here: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32

*facepalm!*
Didn't see that, will bookmark it and keep an eye on it, perhaps work with it. Thanks for the link

the androidhtc.com site is not related directly to the develop project because no developer is connected to it. Also the git repository it not hosted in linux to go but on sourceforge (so download the correct git). That site is very outdated.
wifi works if you use the correct branch (on sourceforge) and modules.

Am I right in thinking that http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD is the prebuilt kernels and nbhs from the source at http://androidhtc.git.sourceforge.n...og;h=62f075ddd13f378fd252be94c77e4f93d12584fb ??
I think I'm looking at the right tree now.
Flashing the latest NBH: VOGUIMG-320-FROYO-01-16-11.NBH still gives me the wifi error. Do I need to manually add the wlan.ko to it or ??
I could've sworn that an NBH I flashed before had all that in the NBH and it worked fine.

Ok, got it back to how I had it:
Flashed latest.NBH from http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD and dropped androidupdate.tgz to the /andboot folder of the SD card, installed update thru the boot menu and done.
So in reality there's nothing stopping me grabbing the same kernel source, building it and adding ipv6 support in the ncurses kernel config menu and making an NBH from it and flashing that over, and then doing the androidupdate.tgz, although I think with HTCFlasherGUI you can flash a zImage directly right??

Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me

xteejx said:
Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me
Click to expand...
Click to collapse
No, nothing wrong with it. Just do:
git clone git://androidhtc.git.sourceforge.net/androidhtc/kernel.git
You then need to set it to the correct branch using 'git checkout -b <branch you want> '
It's the 2.6.32 branch you are interested in, you can find out exactly what it's called using 'git branch -a' which will list the available branches.

Cool. Knew something went wrong somewhere, had to be me lol!
I added that ipv6.ko to the NAND via a androidupdate.tgz (only way I could do it), and it didn't work, something about incorrect module format (or something like that).
Are there any prebuilt kernels or NBHs for the Kaiser that include ipv6? Either as a module that I can insmod it in the terminal or built-in?
I hate being upstaged by people that can use Goggles without any problems.
I know slayher's kernels have ipv6, but I flashed the new stock one from http://forum.cyanogenmod.com/topic/4434-froyo-kernels-by-slayher/ and it didn't work. I mean the kernel did, but Goggles didn't - couldn't insmod it either - same invalid module format as the ipv6.ko scooter did for me

Also the git clone didn't work:
Initialized empty Git repository in /home/name/android-git/kernel/.git/
fatal: The remote end hung up unexpectedly

[KERNEL][SOURCE][android_kernel_lge_msm7x27-3.0.x (3.0.8)]

I waited to post this over here until it was debugged and all the hardware works.
Even though this forum's been kinda dead quiet for a while, xda gets searched and I want this source code out there.
Derived from androidarmv6 project and tweaked over to thunderc from the p500 developers' awesome work getting it running on the Optimus One.
source:
https://github.com/bigsupersquid/and...7x27-3.0.x.git
(branch squid, for lack of imagination.)
make thunderc-test_defconfig
you'll want to change or remove the toolchain path in the config. it is highly unlikely that your cross toolchain is in the same path as mine.
I set it in the config to avoid having to add "CROSS_COMPILE=/blah/blah/etc" to the make command every time I rebuild the kernel.
it is for jellybean and kitkat roms.
use on older android versions messes up various things. Especially USB.
it conflicts with /sbin/chargerlogo or /sbin/charger for offline charging and bootloops unless that file is removed.
Use the attached removecharger.zip in recovery with signature verification off for that if you don't want to edit the ramdisk yourself.
md5sum b1a9f21285e09e06dc94422a8578dc98
enjoy

@bigsupersquid Know if anyone's willing to have a stab at building Firefox OS, now with the 3.x kernel?
EDIT: Well apparently there's no full ArmV6 support in it so, I guess not...

[Q] stock kitkat kernel with selinux permissive?

looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: kind @xluco has built a kernel just for us:
http://forum.xda-developers.com/show....php?t=2756679

ionflux said:
looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: for p600. thanks!
Click to expand...
Click to collapse
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.

injola said:
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.
Click to expand...
Click to collapse
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful

ionflux said:
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful
Click to expand...
Click to collapse
I was trying to edit my last post because I saw that you have tried that kernel.
I have spent way more time compiling kernels over the past 20 years than I care to, which is one reason I haven't tried this task yet. I flashed the pre-kitkat selinux permissive kernel a while back and it simply wouldn't boot. I had saved the stock kernel with online nandroid backup. I reflashed stock kernel and there was no problem. I guess, the same would happen with an any unbootable kernel. I never have built an android kernel though.

Here you go guys, try this.. Stock KitKat kernel with SELinux in permissive mode and Knox removed: d-h.st/uCX
EDIT: slight update with NTFS support / HTCP and Multi-core scheduler support.. all completely stable as they're already in the kernel just not selected
EDIT 2: http://d-h.st/ziH - V3 [19/05/2014] (fixes a small derp in ramdisk)
http://forum.xda-developers.com/showthread.php?t=2756679

Any chance of a p605 kernel with SElinux enabled?

patchseven said:
Any chance of a p605 kernel with SElinux enabled?
Click to expand...
Click to collapse
samsungs opensource website is so slow, it would literally be about 5 hours of download time to get the source, I can do it but it'd be next week now

Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.

patchseven said:
Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.
Click to expand...
Click to collapse
Check the thread over in original development if you haven't already, p605 for jellybean just added

[DEVELOPERS-ONLY]CyanogenMod 12 EARLY Builds Discussions

Hello all,
I've started working on CM12 for RedMi 1S. So here I'm going to discuss about the further status and builds for the rom.
For those who wants to join and help out :-
Current Status :-
Tree is now buildable without any sort of errors
ROM doesn't boots stucks at MI logo
So Kernel ain't loading up yet
I'd request to make pull request if you've any fix for anything.
CREDITS :-
armani-dev(fefifofum, Kra1o5 for all their work and base tree)
CyanogenMod
If anyone missed here please pm me

ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F

kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707

Tarun93 said:
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Click to expand...
Click to collapse
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.

kD said:
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
Click to expand...
Click to collapse
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal

Tarun93 said:
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Click to expand...
Click to collapse
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.

kD said:
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
Click to expand...
Click to collapse
kkkkkkkkk keep me updated i will dig more info i can

kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.

jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?

jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
kD said:
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
Click to expand...
Click to collapse
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?

Awesome!

kD said:
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Click to expand...
Click to collapse
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.

i do agree with jsevi83 pal even i tried with my noob knowledge now m bored

jsevi83 said:
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
Click to expand...
Click to collapse
I went through your changes. I've came to some conclusions.
Add display_config header
Well it adds display_config header at CM11 but at CM12 it is already present.
display_config header at CM12 just add this line at the bottom rest all is same.
Code:
// set the view frame information in hwc context from surfaceflinger
int setViewFrame(int dpy, int l, int t, int r, int b);
This is the only extra part at CM12's display_config header?
So can you tell em do actually need to comment out this line?
Now libmemtrack is already present at CM12.
Now at media
mm-core/inc/QCMetaData.h is edited to disable few components but if i do the same at CM12 it throws the build error?
Build error is already posted above.
Any idea for fix would be really helpful.

good luck
:fingers-crossed: i am not a dev , but i can be a tester for yu guys .. good job friends , i wish to apreciate your effort towards redmi 1s.. hope to seee lolipop on our devices soon

the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b

thewisenerd said:
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
Click to expand...
Click to collapse
I've done those commits for fixing display. They were applied at CM11 same needs to be applied at CM12. So I need them.

https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))

thewisenerd said:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
Click to expand...
Click to collapse
yeah just figured out you're right. changes at media were just done to override the path because it was changed display-caf-legacy.
Removed those edits.
Now just need to fix display build error.
Building now will post error here soon.
p.s. thank you

Any update ?

[DEV] CAF kernel 3.10.x

Hi guys, only few words:
I'm working on a 3.10 kernel just for fun, i dunno if i'm able to make it stable.
If someone want to help any help is appreciated!
it's based on LA.BF.2.1.2_rb1.5 CAF branch
source code is here branch LA.BF.2.1.2_rb1.5 and test_usb
test boot.img is here: http://www58.zippyshare.com/v/eqVBaQhc/file.html
Working list:
- it boots!
- touch screen
- backlight
- sms and call
- audio
- Bluetooth
- NFC
- 3D Graphics
- adb
everything else is not working. use it with a usb cable plugged in or it will not work.
Major issue atm: it doesn't work without usb plugged in.
thanks to @myfluxi for his caf kernel & ROM
thanks to @Sultanxda for some suggestions

That's a good news! Maybe @myfluxi can help?
Inviato dal mio Nexus 5 CAF utilizzando Tapatalk

Very interesting project. I'll keep an eye on this. I'm also available as a tester if you want [emoji5]
Sent from my Nexus 5 using Tapatalk

Interesting.
How did you get past what this guy said?:
Sultanxda said:
Stopped working on it :/ I managed to get modem firmware to load (modem still doesn't work), but 3.10 as a whole has one big problem on the Nexus 5: proprietary TrustZone (TZ) firmware. 3.10 is much, much more reliant on TZ than our 3.4 kernel. 3.10 is so reliant on TZ that the CAF 3.10 branch does not boot with the latest PM (power-management) drivers (I had to use the 3.10 source from the LG G Watch as a base to get this completely booting). There are scm calls to TZ everywhere in 3.10, and in particular all versions of 3.10's PM code are broken to some extreme degree with our ancient firmware (kernel always crashes on CPU idle power collapse). I'm sure it's possible to make everything work with our firmware, but you'd likely need to know things that only Qualcomm engineers know, such as the actual internals of the TZ firmware to see where there are incompatibilities between TZ and the new kernel (TZ firmware source code is confidential/proprietary, so it is not available to the public).
Click to expand...
Click to collapse

nagalun said:
Interesting.
How did you get past what this guy said?:
Click to expand...
Click to collapse
probably because now CAF source has got more patches than 1 year ago! maybe they used patches that already were in lg smartwatch source, who knows... luckily now we have got a booting CAF kernel

Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.

nagalun said:
Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.
Click to expand...
Click to collapse
thanks for the tests, adding to OP

You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858

I hope you get the help, collaboration and input you need to succeed!

3.10.x on N5? OMG Yeeees

Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.

Creative9170 said:
Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.
Click to expand...
Click to collapse
read from here to here, replace the kernel version in the url from 3.4 to 3.10 to get all improvements over the time. yes, backport features from 3.x/4.x to 3.4 will lower the gap between 3.4 and 3.10 but there's a motivation if newer devices use 3.10 instead backport stuff (caf will drop support for 3.4 sooner or later)
blackbird5308 said:
You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858
Click to expand...
Click to collapse
i'll take a look

small update:
got adb working (using 3.4 driver), now it's easier to debug for everyone!
http://www58.zippyshare.com/v/eqVBaQhc/file.html

Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL

kwjhgjh said:
Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL
Click to expand...
Click to collapse
Hi!
I already knew that those things are broken, i'm working on it

rmbq said:
Hi!
I already knew that those things are broken, i'm working on it
Click to expand...
Click to collapse
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!

kwjhgjh said:
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!
Click to expand...
Click to collapse
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable

rmbq said:
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable
Click to expand...
Click to collapse
'hilarious' means...unfamiliar vocabulary to me, but enough to understand your purpose.
I think to consider my main rom as CM-Caf. Good luck to your project!
I'll waiting your work. d=_=b

@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?

rachanta said:
@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?
Click to expand...
Click to collapse
i don't know where is the problem atm, i don't think it's related to USB drivers, sultanxda said it's TZ related... it isn't easy to track, i saved a log with something more than "watchdog bytes". also i don't know if LA.BF.2.1.2 is a good base, some drivers (ex adreno) are older than LA.BF.1.1.3 (our caf 3.4)!! xperiadev are working on LA.BF64.1.2.2 also for msm8974 soc, that branch is very up to date but i can't get it boot on hammerhead, and i don't know if they can get it boot on xperia devices with msm8974 soc...