Related
Hi everybody,
I'm using CyanKang on my Nexus 4 device. As of late I'm still able to flash a custom kernel, but after boot up my screen color is just garbage.
I read the CyanKang thread and Schubi (one of the main developer) wrote something about "having not implemented CAF media drivers". Could this be the reason? And if so, what is the technical explanation
I would have asked directly, but as this is my first post ... Well you all know the rules
So thanks in advance.
IcedTux
IcedTux said:
Hi everybody,
I'm using CyanKang on my Nexus 4 device. As of late I'm still able to flash a custom kernel, but after boot up my screen color is just garbage.
I read the CyanKang thread and Schubi (one of the main developer) wrote something about "having not implemented CAF media drivers". Could this be the reason? And if so, what is the technical explanation
I would have asked directly, but as this is my first post ... Well you all know the rules
So thanks in advance.
IcedTux
Click to expand...
Click to collapse
the kernel contain the drivers for hardware, so i agree this is be'coz of the driver not right to your Nexus 4.
rxz
rxzcums said:
the kernel contain the drivers for hardware, so i agree this is be'coz of the driver not right to your Nexus 4.
rxz
Click to expand...
Click to collapse
Thx for the reply.
I know that all hardware support comes through the kernel and kernel modules. But what I don't understand, the same kernel happens to function with other roms or e.g. vanilla CM10.2 (on my Nexus 10).
So what could be the reason for one and every custom kernel not working with this kang?
Thx IcedTux
Ok after some more searches I found something in Francos Kernel thread.
There is a AOSP colorfix.zip (http://forum.xda-developers.com/showpost.php?p=46223069&postcount=9677)
I flashed the kernel, flashed the fix and voila... works.
Still I don't understand what the fix is supposed to actually do. The zip contains some liboverlay...
So if there is anybody who could satisfy my curiosity :cyclops:
thx
IcedTux
Hello, can't post in the N4 franco kernel thread so I'm posting here as instructed by the website
To ask Questions about developing your device, installing ROMs, software and themes you must go to the Q&A or General Forum.
Click to expand...
Click to collapse
I'm a Nexus4 user, with paid version of franco's app, and as of the latest update r213 the camera has not been working properly, it works for a few pics then next time I want to use it, it won't save any pics, and then say camera could not be initialized, then it doesn't work again until I reboot the phone.
Q&A for [KERNEL][n80xx][Samsung JB] Boeffla-Kernel 2.5 stable (03-09-2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][n80xx][Samsung JB] Boeffla-Kernel 2.5 stable (03-09-2014). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Lord Boeffla said:
Hi all,
3.0-beta3 is now ready for you (both n8000 and n801x variants).
Change log is the same for both kernels.
Version 3.0-beta3
22.10.2014
Update zzmoove to version 1.0-beta1 (credits to ZaneZam)
Update exFat driver to 1.2.9
Update the flash binary in the boeffla-kernel-reset recovery script, bump to version 3.1
Enjoy
Andi
Click to expand...
Click to collapse
It sjust awesome
help to find kernel n8013
Someone.. anyone.. where can i find this kernel ? a download link would great.. thanks in advance..
3.0-beta3 is now ready for you (both n8000 and n801x variants).
Change log is the same for both kernels.
Version 3.0-beta3
22.10.2014
As always... Read the op.
Then you will see everything is here:
www.boeffla-kernel.de
Andi
hello I'm New On Android, I want to ask regarding flashing the kernel ...
Do I need to run Kernel cleaning Script Afterflashing the kernel? Thanks
Sent from my GT-N8000 using Tapatalk
Araragi said:
hello I'm New On Android, I want to ask regarding flashing the kernel ...
Do I need to run Kernel cleaning Script Afterflashing the kernel? Thanks
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
Hm... are you talking about leaving Boeffla-Kernel or moving to Boeffla-Kernel?
If you leave Boeffla-Kernel, you do not need to use any cleaner script. Boeffla stores everything under /data/.boeffla, and this cannot be used by any other kernels.
If you move to Boeffla, also usually no cleaning before required.
Only exception: If you were on a kernel before that stored all his configuration into init.d scripts, then you should cleanup your /system/etc/init.d folder before flashing Boeffla.
That's all however.
Andi
Where can I find ur beta version of the kernal and how can I flash it...im using gnabo rom..could u plz guide me through
w_ayon said:
Where can I find ur beta version of the kernal and how can I flash it...im using gnabo rom..could u plz guide me through
Click to expand...
Click to collapse
All you need is on the homepage, as stated in the OP of all kernel threads.
www.boeffla-kernel.de
Andi
ALL: Google is again playing games and locked down the first of my 3 donation apps in Playstore. Of course no compelling reason provided.
But as I already prepared for that half a year ago, I would like to remind you to use your personal unlock key to gain donation functionalities.
If you have not yet generated (this can be done in the donation app itself) and entered it into Boeffla-Config, it is now urgent to do that!!!
I cannot ensure Google will not lock down the other two donation apps as well soon, so you should be prepared now.
From my side, next Boeffla-Config app version will not support these donation apps anymore but only personal unlock codes.
Also, I will replace remaining donation apps in Playstore very soon (today or tomorrow) with a dummy app that tell users to get in touch with me manually.
Thanks for understanding... and alohas Google, all done wrong, guys there.
Cheers
Andi
Hi all. I have a gnabo rom v7 on my n8000. Can I install this kernel to my device? Android version is 4. 4. 2. Thanks beforehand.
sarvar97 said:
Hi all. I have a gnabo rom v7 on my n8000. Can I install this kernel to my device? Android version is 4. 4. 2. Thanks beforehand.
Click to expand...
Click to collapse
Absolutely, take latest 3.0-beta version for your device (n8000, not the n801x version).
Andi
Lord Boeffla said:
Absolutely, take latest 3.0-beta version for your device (n8000, not the n801x version).
Andi
Click to expand...
Click to collapse
Thanks a lot, the kernel is fantastic.
Hi from Russia. Excellent operation! I tried to pay, but my payment system of it doesn't allow to make. Sorry. The kernel for N8000beta5 isn't set through TWRP2.8.3.0 "error bynary". I set through Odin. Everything is great. Good luck!
And you can also use Boeffla-Config app to flash kernel updates now.
Surprised twrp throwing an error, s3 and opo kernels flash fine with twrp. But I only report what others say, I never use twrp. I am a philz touch guy...
Andi
Lord Boeffla said:
And you can also use Boeffla-Config app to flash kernel updates now.
Surprised twrp throwing an error, s3 and opo kernels flash fine with twrp. But I only report what others say, I never use twrp. I am a philz touch guy...
Andi
Click to expand...
Click to collapse
OK! I set Philz v6.48.4. The kernel of beta5 was normally stitched. Last versions of kernels were normally sewed on TWRP. Thanks! Good luck!
Guroff1974 said:
OK! I set Philz v6.48.4. The kernel of beta5 was normally stitched. Last versions of kernels were normally sewed on TWRP. Thanks! Good luck!
Click to expand...
Click to collapse
But this is unexplainable then... the flash binary has not changed for more than half a year.
However I got to know in the OnePlus One thread, TWRP seems to have introduced some issues lately. But never used TWRP myself, so it is just second hand information I have seen.
Andi
Guroff1974 said:
OK! I set Philz v6.48.4. The kernel of beta5 was normally stitched. Last versions of kernels were normally sewed on TWRP. Thanks! Good luck!
Click to expand...
Click to collapse
Ah, but can be something else.
In order to avoid people are flashing wrong kernels, I put asserts in.
Could you please just boot your tablet and look in /system/build.prop file what the entries are there for:
ro.build.product
ro.build.model
ro.build.device
Many thanks
Andi
Ok, for the time being I uploaded the kernels again without the assert checks.
So be careful to not flash the kernel on a different device than the Tab10.2
Please redownload the zip again, it should work now also in TWRP.
Thanks
Andi
Lord Boeffla said:
Ok, for the time being I uploaded the kernels again without the assert checks.
So be careful to not flash the kernel on a different device than the Tab10.2
Please redownload the zip again, it should work now also in TWRP.
Thanks
Andi
Click to expand...
Click to collapse
I redownload N8000beta5 of 31.01.2015. Now everything is good. The kernel is set through TWRP and Philz. Gnabo v8 firmware. Thanks! Good luck!
problem with boeffla kernel v3 beta 6 for samsung note 10.1 (n801x)
Hi ! I am using the samsung kitkat stock rom 4.4.2 rooted in a samsung galaxy note 10.1 (n8010). First time trying a kernel. I have tried to install the boeffla kernel mentioned in the title, both via odin and trwp, but i have the same problem once installed... when rebooting the tablet it just stays in a black display after the "samsung galaxy note 10.1" title. It just does not start, i have to boot in download mode and reinstall the stock rom via odin. Help please! I would like to try this kernel in my tablet ! Thanks!
Q&A for [rom] [unofficial] cm-12.0 915f/915fy [beta][12/05]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [rom] [unofficial] cm-12.0 915f/915fy [beta][12/05]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
File not found
Hi Mickey,
something is wrong with the file. Google Drive says "file not found".
Will S pen will work? with all options? (Smart select, Action memo etc)
Anybody tested the rom in detail? Is "active display" working?
Where will be the notifications shown if "edge" is not working? (e.g. S Pen removed)
greetings
Hello.
Try again and look into my thread for more info.
Yes i haved delete last file. New link out with minor fix.
The Changelog is?
your work ist unbelievably
Look in OP.
But i think many thing are fixed.
what is with the edge Display? Works?
I have great respect for your work.
Gordon1979 said:
what is with the edge Display? Works?
I have great respect for your work.
Click to expand...
Click to collapse
Edge display doesn´t work. See OP.
Ambilight Display works.
Gestures are not working.
Performance is better than stock Samsung.
HW-Buttons have different function now.
Same Issue here. I can´t hear anything while calling.
Can anybody pls post version 1?
I need my phone
Pille702 said:
Same Issue here. I can´t hear anything while calling.
Can anybody pls post version 1?
I need my phone
Click to expand...
Click to collapse
Here you go
https://docs.google.com/file/d/0B4HWI1X5rVxeZFU3MnVkU1kyMWc/edit?usp=docslist_api
Hey. the generic.kl method works. The Haptic feedback works fine, but the recent app key has become a menu key. Another thing i noticed was that when i remove the s pen, the touch keys work fine even before the generic.kl modifications. but they only worked with the s pen not with the finger.
Thanks for the ROM btw. Great work.
thanks for your report.
I dont have much time now for expect anything.... but i do the best for making a new build working with some surprise ....
After spent some time to do try & error, I think i found the fix for incall voice problem
Please download file attached
1. Flash 1st version CM zip file from here
2. Download file Generic.kl below
3. Replace this file to system/usr/keylayout
4. Change permission
5. Reboot
Click to expand...
Click to collapse
Works great!
So is the edge panel working now? great work btw
No. Sorry
Kamera not working
Hi Mickey,
great ROM. Runs he hell...But camera is not working.
Pille702 said:
Hi Mickey,
great ROM. Runs he hell...But camera is not working.
Click to expand...
Click to collapse
Yes .but working sometime. It's know issue.Look OP
open and close camera app many time and working after.
Use google camera if you want apk working great
Big news, Xposed for Samsung Lollipop by arter97
:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
When is comes an update?
No stabile Version for 5.1. untill now.. No question oft Rom.
Can this ROM run on Tmobile note edge
Sent from my SM-N915T using XDA Free mobile app
No. To many change in T-Mobile variante. And i cant test if i try....
Hi fellow xda members!
I'd like to share with you something that I had been very curious about.
Well if the title hasn't already given it away, it's the generic version of Double Tap to Wake (for almost all devices)
And what's different is that I've studied, refactored and restructured the code myself to be more efficient, faster, and shorter.
As a result, I've decided to bump this good ol' kernel module to V2.0
First of all, huge thanks and respect to Dennis Rassmann who gave us the original dt2w v1.0 kernel module (for almost all devices)
Here's the precise changes :
1) Restructure (and rewrote parts) dt2w main function code.
2) Remove useless variables. It is possible to achieve the same thing with less space.
3) Rewrite the distance formula. Change it from rectangular linear to circular radial.
4) Remove unnecessary checks which are either always true or never reached.
5) Reduce space and time complexity for the algorithm.
6) Use vibrator call method AFTER queuing the pwr_on so that there is no delay between calling the vibrator and the power button emulation.
(Step 6 explained : Calling power method before vibrator is a UX tweak. When we call power method first, it queues the power command to the sched (or so I think what queue does) and we know the screen doesn't wake up immediately. So, while the screen is in the mid of waking, we next run the vibrator method. This causes the vibrator to react after the screen on is triggered, and that creates a feeling of spontaneity that the vibrator is running while the screen is turning on. In version 1, the vibrator starts vibrating before the display is even queued. This feels like it takes longer (although it doesn't, it's just a UX placebo))
Click to expand...
Click to collapse
Result : Final dt2w main function is about half the length of earlier one, and more effective.
Here is the source for DT2W v2.0 - https://github.com/tanish2k09/Doubletap2wake-2.0
Guide about how to add it :
---It's all already written in the README.md in github, it's better to check that instead---
Code:
Follow these steps if you have the good ol' v1.0 from dev Dennis Rassmann :
(For feasibility, I've added port-dt2w-functions.txt with all the necessary code)
(Also note : doubletap2wake.c has been referenced as dt2w.c just because I'm too lazy)
1) Replace the whole "detect_doubletap2wake" function from v2.0 to v1.0
2) Remove "calc_feather" function from v1.0 and place "calc_within_range" function from v2.0
3) Define "DT2W_RADIUS" in the beginning of dt2w.c, along with other defines. Copy from port txt.
4) Remove "DT2W_FEATHER" definition from the defines.
Optional step 5: Change Version, author, desc, etc. Find "/* Version, author, desc, etc */" and replace next 4 lines from port file.
6) Remove the third argument from all "detect_doubletap2wake" calls. Usually it's "true"
7) That's it! You're good to compile it now.
8) If it works nicely, make sure to give me a thanks on xda thread :D
Follow these steps if you don't even have the good ol' v1.0 from dev Dennis Rassmann :
1) Get dt2w-v1.0 by Dennis Rassmann and compile it successfully first.
2) Follow the steps in above part.
Note for mods :
In case you find this thread to be in the wrong subforum, please move it to the right section while informing me.
In case you find anything inappropriate according to xda forum rules, please contact me before taking any actions so I have a chance to correct any and all mistakes I might have commited.
I see @xanthrax is a forum moderator here. Please be kind enough to review the thread.
Edit : xanthrax moved the thread to appropriate subforum already and reviewed the thread and confirmed nothing wrong here.
It's available for Redmi Note 3 MTK?
GreatStorm said:
It's available for Redmi Note 3 MTK?
Click to expand...
Click to collapse
This is a general module.
The steps I have provided will work for all mtk phones.
Just ask any of your experienced kernel developers (or you yourself, if you're one of the Devs) to check my thread (and the GitHub source readme) to add it.
If you already have dt2w, this will work 100%
Feel free to contact me for any doubts. :laugh:
In some time I'll also post trace2sleep (or t2s) module.
any link for dt2w v1.0 kernel module ?
sougata7684 said:
any link for dt2w v1.0 kernel module ?
Click to expand...
Click to collapse
Unfortunately you'll have to search for GitHub commits "add dt2w".
I couldn't find a generic all-driver file itself, so you need to find the one with your driver.
ChinmayDalal said:
I saw some commits on GitHub on 3.10.xx kernels, but my device's dev told me that he already tried porting from 3.10.xx kernels.
He needs 3.18.xx kernels to port.
(MT6737)
Click to expand...
Click to collapse
This thread is just for dt2w module.
The device must have a working touch panel support for gestures before adding v2
module working on Samsung phones
Does this module work on any Samsung phones? I've got an s7 running Nougat via "The Galaxy Project" rom, the SuperKernel, and i'd really like this feature. The processor is an exynos8890.
I'd love to have this feature, miss it from my old g2.
tech927 said:
Does this module work on any Samsung phones? I've got an s7 running Nougat via "The Galaxy Project" rom, the SuperKernel, and i'd really like this feature. The processor is an exynos8890.
I'd love to have this feature, miss it from my old g2.
Click to expand...
Click to collapse
Ask a kernel developer for your device to do that and maybe link him this thread.
Or, if you are one yourself, check the instructions on the linked GitHub page. It's really not difficult at all if you've had since experience with kernels.
doubletap2wake
Where can I get the doubletap2wake v1.0 code that seems like a prereq?
tech927 said:
Where can I get the doubletap2wake v1.0 code that seems like a prereq?
Click to expand...
Click to collapse
I guess you can find it in almost every custom kernel on GitHub, according to your chipset of course.
The most important part is configuring the touch panel to be active and receive input even with screen off. That, however, should be no difficulty for an experienced kernel maintainer
Sent from my Samsung Galaxy J1 Ace using XDA Labs
Hi......may I know if this works with Sony XA1 Ultra? It uses Helio P20.......
eddie24902005 said:
Hi......may I know if this works with Sony XA1 Ultra? It uses Helio P20.......
Click to expand...
Click to collapse
If you already have a custom kernel with dt2w working then this upgrade will work too
tanish2k09 said:
I guess you can find it in almost every custom kernel on GitHub, according to your chipset of course.
The most important part is configuring the touch panel to be active and receive input even with screen off. That, however, should be no difficulty for an experienced kernel maintainer
Click to expand...
Click to collapse
OK I'm new to android kernel development and I'm having my mind melt trying to add the v1 code.
Could you please write a tutorial or make a complete d2w api without needing to hunt for codes. Thanks.
xDoge said:
OK I'm new to android kernel development and I'm having my mind melt trying to add the v1 code.
Could you please write a tutorial or make a complete d2w api without needing to hunt for codes. Thanks.
Click to expand...
Click to collapse
I could and I would if I had time. Just rolled into the fall sem so I'll be a LOT busy. Sorry
tanish2k09 said:
I could and I would if I had time. Just rolled into the fall sem so I'll be a LOT busy. Sorry
Click to expand...
Click to collapse
Why don't you rollback with sem reset hard.
Sorry for double post. XDA app messed the post.
xDoge said:
Why don't you rollback with sem reset hard.
Click to expand...
Click to collapse
Gesendet von meinem SM-G950F mit Tapatalk
may I ask. My device already have featur dt2w/dt2s and sweep up to wake on settings (in Zenmotion). But, unfortunately when I use custom rom this feature gone. Can I use this file to bringing back that feature (dt2w/dt2s)? or maybe adding SU2W too? please help. My device is X00RD