Just disable KSM in Kernel config
There are 2 related things that actually trigger camera error, they are KSM and Denoise. Having both of them enabled will cause camera error (http://forum.xda-developers.com/showpost.php?p=59077168&postcount=11)
- KSM can be found in kernel settings
- Denoise can be found in camera settings
CM11 stock cam has Denoise enabled by default and there is no option to disable it, so the only way to prevent camera error if you use CM11 stock cam is disabling KSM.
How to enable/disable KSM
aperezdc said:
For reference: using the stock CM11 kernel it is possible to enable and disable KSM, the option is at Settings → Performance → Memory Management → Kernel Samepage Merging. The stock kernel also has some tunable values, you can use Performance Control (which is Free Software / Open Source) for most kernels, even for the ones that don't have the “configbuilder” thing (like the stock kernel).
Click to expand...
Click to collapse
If you feel having KSM enabled is important, I suggest you to replace CM11 stock cam to other camera app without Denoise feature (e.g. Google cam), or camera app with option to disable Denoise (e.g. SlimRom camera, Snap camera). Don't use MIUI stock cam since MIUI camera app also have Denoise enabled without any option to disable it.
Usefull Links
Slim ROM camera (very similar to CM11 stock cam with more options including enable/disable Denoise)
http://forum.xda-developers.com/gal...slim-rom-camera-roms-based-cm11-aosp-t2901758
Snap Camera:
http://forum.xda-developers.com/showthread.php?t=2055140
Tested on Carbon ROM RC6 (based on CM11-R16) + Xcelerate kernel build 7, CM11-R20 + Xcelerate kernel build 10, CM11-R22 + Xcelerate kernel build 12
Still not working.
Tried different clock speeds including 600mhz, but no success. No matter which camera app I use, all are giving the same error message.
CM Punk said:
Tried different clock speeds including 600mhz, but no success. No matter which camera app I use, all are giving the same error message.
Click to expand...
Click to collapse
Ok I'm sorry it doesn't work for you. I will edit op.
CM Punk said:
Tried different clock speeds including 600mhz, but no success. No matter which camera app I use, all are giving the same error message.
Click to expand...
Click to collapse
Are you still having camera problem? Check original post, I updated it with working method.
Give it a try and let me know your result.
keliori said:
Are you still having camera problem? Check original post, I updated it with working method.
Give it a try and let me know your result.
Click to expand...
Click to collapse
Flashing that kernel gave me a bootloop. So I had to flash the rom again.
However, flashing the rom seems to have solved the problem for now. I can confirm the same after prolonged usage.
It is not Xcelerate's KSM option. Even Stock CM11 has it. Use Stock CM11 Kernel and replicate the error, get logcat, dmesg and send it to CM11. No one will believe you have that error if you show no logs.
gummie said:
It is not Xcelerate's KSM option. Even Stock CM11 has it. Use Stock CM11 Kernel and replicate the error, get logcat, dmesg and send it to CM11. No one will believe you have that error if you show no logs.
Click to expand...
Click to collapse
Yes, I know stock CM11 has this camera problem too because it happened to me for the first time when I was on CM11-R17 with its own kernel.
Since I'm not an expert I can only assume that KSM or something similar is enabled by default on stock CM11 kernel, and the way to disable it is by using Xcelerate kernel + Synapse.
I will do once more test, enabling KSM again now, let's see if camera problem come again.
CM Punk said:
Flashing that kernel gave me a bootloop. So I had to flash the rom again.
However, flashing the rom seems to have solved the problem for now. I can confirm the same after prolonged usage.
Click to expand...
Click to collapse
Make sure you use correct Xcelerate build to be paired with your CM11 version.
CM11-R16 (and any other ROM based on it) should use Xcelerate build 7 or older
CM11-R17 is not supported by Xcelerate
CM11-R18 should use Xcelerate build 8
CM11-R19 should use Xcelerate build 9 with additional step of flashing original boot.img (if I'm not mistaken) before flashing the kernel (I haven't tried this version myself so I can't give you much detailed instruction. You better visit Xcelerate kernel's thread and ask someone who has successfully flashed it.)
keliori said:
Make sure you use correct Xcelerate build to be paired with your CM11 version.
CM11-R16 (and any other ROM based on it) should use Xcelerate build 7 or older
CM11-R17 is not supported by Xcelerate
CM11-R18 should use Xcelerate build 8
CM11-R19 should use Xcelerate build 9 with additional step of flashing original boot.img (if I'm not mistaken) before flashing the kernel (I haven't tried this version myself so I can't give you much detailed instruction. You better visit Xcelerate kernel's thread and ask someone who has successfully flashed it.)
Click to expand...
Click to collapse
Yes, I flashed the one which said "Warning, for CM 11 only"
gummie said:
It is not Xcelerate's KSM option. Even Stock CM11 has it. Use Stock CM11 Kernel and replicate the error, get logcat, dmesg and send it to CM11. No one will believe you have that error if you show no logs.
Click to expand...
Click to collapse
For reference: using the stock CM11 kernel it is possible to enable and disable KSM, the option is at Settings → Performance → Memory Management → Kernel Samepage Merging. The stock kernel also has some tunable values, you can use Performance Control (which is Free Software / Open Source) for most kernels, even for the ones that don't have the “configbuilder” thing (like the stock kernel).
keliori said:
Yes, I know stock CM11 has this camera problem too because it happened to me for the first time when I was on CM11-R17 with its own kernel.
Since I'm not an expert I can only assume that KSM or something similar is enabled by default on stock CM11 kernel, and the way to disable it is by using Xcelerate kernel + Synapse.
I will do once more test, enabling KSM again now, let's see if camera problem come again.
Click to expand...
Click to collapse
Here is result of the latest test.
1. Camera error happens when the device under heavy usage. During my test I kept running on background 4 instant messengers (whatsapp, LINE, 2 BBMs), facebook lite, chrome with 6 tab loaded.
2. There are 2 things that will triger this error: They are KSM and Denoise
- If KSM disabled + Denoise disabled, there is no error
- If KSM disabled + Denoise enabled, there is no error
- If KSM enabled + Denoised disabled, there is no error
- If KSM enabled + Denoise enabled, there IS error
If you remember my other post on Xcelerate thread, I did mention 3rd party camera apps from Play Store (like Google camera) were not affected by this error, but 2 ported camera apps that I tried were affected (SlimRom camera and MIUI camera).
Now I can say this is not entirely true, to be more spesific: Error only happen to camera apps with Denoise function enabled and KSM enabled too.
To support my test I'm installing another 3rd party camera app which is very popular on XDA: Snap Camera
And the result? Yes, exactly same as I have said above. With KSM and Denoise enabled you will get camera error, sooner or later.
Hope this help
aperezdc said:
For reference: using the stock CM11 kernel it is possible to enable and disable KSM, the option is at Settings → Performance → Memory Management → Kernel Samepage Merging. The stock kernel also has some tunable values, you can use Performance Control (which is Free Software / Open Source) for most kernels, even for the ones that don't have the “configbuilder” thing (like the stock kernel).
Click to expand...
Click to collapse
Thanks, can you help me checking whether KSM is enabled/disabled on stock CM11 kernel's default config?
arunal_123 said:
Ok i will try and let you know. But to be true, I dont know how or what event triggered that camera error.
Can you tell me how to reproduce that error.??
Click to expand...
Click to collapse
This is what I usually do to trigger camera error:
1. Enabling KSM in kernel settings
2. Enabling Denoise feature in camera setting. CM11 stock cam and MIUI stock cam already have this feature enabled by default (there is no option to disable it). Slim Rom camera and Snap Camera also have this feature and we can choose to enable/disable it in settings.
3. Use phone for heavy multi tasking. Open many apps and let them running on background.
4. Open camera and use it to take some photos
5. Go back to multi tasking
6. Leave phone until screen off (don't use power button to turn off the screen)
From my experience, if you don't hear 'tick' sound when screen is turning off, next time you use camera it will get error.
7. Wait for few minutes, turn on screen and start using your camera to take photos again. It's a success if photo is not saving and you stuck on camera UI. You can go back to home screen using home button and force close camera app. But when you try to open camera again it will say "Can't connect to camera"
That's all I know about triggering camera error, although I must admit this method is not always working. Sometimes I have to repeat the process for several times. I haven't found better method to trigger camera error yet.
keliori said:
Here is result of the latest test.
1. Camera error happens when the device under heavy usage. During my test I kept running on background 4 instant messengers (whatsapp, LINE, 2 BBMs), facebook lite, chrome with 6 tab loaded.
2. There are 2 things that will triger this error: They are KSM and Denoise
- If KSM disabled + Denoise disabled, there is no error
- If KSM disabled + Denoise enabled, there is no error
- If KSM enabled + Denoised disabled, there is no error
- If KSM enabled + Denoise enabled, there IS error
If you remember my other post on Xcelerate thread, I did mention 3rd party camera apps from Play Store (like Google camera) were not affected by this error, but 2 ported camera apps that I tried were affected (SlimRom camera and MIUI camera).
Now I can say this is not entirely true, to be more spesific: Error only happen to camera apps with Denoise function enabled and KSM enabled too.
To support my test I'm installing another 3rd party camera app which is very popular on XDA: Snap Camera
And the result? Yes, exactly same as I have said above. With KSM and Denoise enabled you will get camera error, sooner or later.
Hope this help
Click to expand...
Click to collapse
I have this error with CM11 and Miui 6 RC 1,2. Can you fix it in miui rom?
MaxMedia said:
I have this error with CM11 and Miui 6 RC 1,2. Can you fix it in miui rom?
Click to expand...
Click to collapse
Sorry, I'm not using MIUI ROM. Can not test it.
Hi keliori
I would like to confirm with you enable ksm and disable denoise work perfectly no camera error anymore although I open alot of apps and playing HD games, thanks for you thread :thumbup:
http://forum.xda-developers.com/showthread.php?p=60899325
Disable Camera DeNoise through build.prop
found it here : http://forum.xda-developers.com/showpost.php?p=63195076&postcount=91
persist.camera.qcwnr.enabled=0
camera.eis.enable=0
persist.denoise.process.plates=0
Related
UPDATE/IMPORTANT/README 1ST
I am giving away the SGS and got a new SGS2. This means I won't be able to test updates on this kernel, this I will DISCONTINUE it soon.
I might update this kernel til i'm unable to (in a week prolly) so i'd suggest to switch over to another kernel, choices are, to my knowledge:
- zach's kernel: lots of tweaks, but people seems to have good results. its based on my kernel
- glitch's kernel: less tweaks but close, higher oc. its also based on my kernel
- cm7's stock kernel: i'm based on them of course, its the same as my kernel minus oc/uv and voodoo, but if you want something simple and stable without caring for oc/uv or voodoo color it's pretty good because it's reliable. voodoo sound works via voodoo +
Note that I'm still hanging out on the CM7 sgs channels and will most likely contribute one way or another still
**********************************************************************
Fat visible download link http://kang.project-voodoo.org/
Disclaimer:
These kernels are provided as-is without any warranty. I'm not here to provide support etc although I might when I'm able, but don't count on it. If your phone explode, it's your problem. Updates are not guaranteed as well.
I made a thread only so that it doesn't get lost in spam and have pms asking where to find it
What's included
Sometimes: testing stuff from teamhacksung before it goes into their stable upstream
Various tweaks: such as JPX screen timings, Haptic feedback and general vibration intensity slightly reduced (integrated upstream)
Voodoo sound patch
Voodoo color patch
[*]Led notification: Now integrated upstream
[*]Extra governors: Smartass, Interactive They're not that good.
Overclock/Undervoltage: I use [email protected] and 1.2Ghz max and rest default, change voltage with "voltage control" (market). Default settings to 1Ghz.
Easy building system and clear commits: for other devs, and myself too lol
Click to expand...
Click to collapse
Credits & stuff:
Thanks to Supercurio for making those great enhancement patches and to the Teamhacksung/CMSGS/CM7 contributors for the CM project. Thanks to many other authors who put their source online, they're too many to name. No thanks to the ones who don't, tho
http://project-voodoo.org/
http://forum.cyanogenmod.com/forum/85-samsung-galaxy-s-experimental-mod/
Click to expand...
Click to collapse
Sources (includes non-GT-I-9000 kernels such as Captivate, Vibrant, etc. - always up to date within ~15min of binary upload depending on my upload speed):
https://github.com/kangsterizer/android_kernel_samsung
If there's anything you don't find in the source (missing source or w/e could ever happen, i'm only another noob human)/ doesn't look correct / you don't understand, don't be shy to ask
Binaries & CWMs (aka fat visible download link - what you're looking for ;-):
http://kang.project-voodoo.org
Other goodies
Netfilter/iptables fix: http://kang.project-voodoo.org/f/iptables-cm7-kang.zip
Nexus S windows USB driver (for SGS CM7) - just like to have the link handy for ADB:
https://dl-ssl.google.com/android/repository/usb_driver_r04-windows.zip
Unpack, go into the device manager, look for the "Nexus S" device, click update driver, have disk/search my computer, put the path to the directory..
Tool for OC/UV: http://forum.xda-developers.com/showthread.php?t=1018411
Some more links
IRC: irc://irc.freenode.org/#project-voodoo irc://irc.freenode.org/#cmsgsteam
Twitter: http://twitter.com/kangsterizer (not using it a lot.. but i'm trying lol)
Click to expand...
Click to collapse
Latest changes
-- r25
- upstream sync (use new cm7 nightly!)
--r12
- upstream sync (camera stuff) (use new cm7 nightly)
--r10
- upstream sync (fix battery info/display)
-- CM7_GT-I9000_kernel_kang_20110504_r9_update.zip
- upstream sync
- some fixes for new recovery
-- CM7_GT-I9000_kernel_kang_20110504_r5_update.zip
- upstream sync
-- CM7_GT-I9000_kernel_kang_20110501_r2_update.zip
- test of new scripts x)
- fixed said new scripts since test failed x)
-- CM7_GT-I9000_kernel_kang_20110501_r1_update.zip
- Supports GB 2.3.4 (upstream)
- Reviewed some code
- Removed governors: ondemand is better in their current state anyway
- using "r" release versionning in case i'm uploading more than 1 kernel per hour or make tests etc.. avoids confusion ;-)
-- CM7_GT-I9000_kernel_kang_20110429_18_update.zip
- allocate more memory to FIMC0 / fixes googles goggles FC
-- CM7_GT-I9000_kernel_kang_20110428_23_update.zip
- upstream sync
- requires latest CM7 nightly for compass etc
- supports bml_over_mtd at flash time
-- CM7_GT-I9000_kernel_kang_20110427_02_update.zip
- upstream sync
- Voodoo sound v8
- some touchkey tweaks
-- CM7_GT-I9000_kernel_kang_20110409_17_update.zip
- upstream sync - untested release (don't have phone access this week )
Older changes are not displayed (lack of space) - see GIT for complete change log
Click to expand...
Click to collapse
NOTE: THESE ARE NOT OFFICIAL VOODOO (or CM7) KERNELS. THESE ARE TEST KERNELS INTEGRATING POSSIBLY UNSTABLE AND UNSUPPORTED VOODOO PATCHES
Fat visible download link http://kang.project-voodoo.org/
Support FAQ
Q: Do LED notification require an app, such as BLN, etc ?
A: No. It uses Android's and Cyanogen settings, other apps are not required, although some that are designed for regular LEDs may work.
Q: How to I turn off LED notifications, scheduled or/and complete turn off?
A: Use Cyanogen's Quiet Hours feature (settings>cyanogen>sound>quiet hours) and check "Dim the LEDs during quiet hours" (in reality it will turn them off on the SGS). If you schedule a complete day, then LED notifications will be off all the time.
Q: How do I setup per app, find other LED settings etc?
A: Settings>cyanogen>interface>LED notifications
Q: What to do with LED color settings?
A: We have only one color, so that doesn't work. Use Green as default setting. Some non-bright colors turn off notification, as it's the equivalent as diming LEDs (note that on real LEDs if you dim them too much they look like off too anyway, the difference is that it's gradual. On the SGS the LEDs can be only on or off, not gradual)
Q: How can I troubleshot my system, I can use ADB but...
A: adb logcat | grep lights (on linux) will show you Android requests to turn LED on or off. "status" tells you what we decide will be interpreted as "turn LED on" (1= on, 0 = off)
adb shell cat /proc/kmsg for live view (or adb shell dmesg if you're using adb after the issues occurs - careful the backlog is limited in size so don't be too slow)
notify_led_on and notify_led_off are requests to the kernel to turn LED on or off.
touch key write/read errors (cypress) are non-fatal failures to ask the touch key to do something (eg lit up the LED), when the hardware goes crazy or there's a logical error in the code (can be both)
touch key recovery routine or "stopped responding" are either hardware errors, either a logical error where the driver would try to write something the touchkey doesnt understand. in some occasion lock&unlock fix those as a work around, of course a permanent fix is required
Q: I used another kernel and some things don't work as expected / I'm the only one to have a problem / music skip with screen off / etc
A: Try this cleanup script: http://forum.xda-developers.com/showpost.php?p=13223426&postcount=1312
Features FAQ
Q: Why do you not implement jhash3?
A: This hash function is used in 3 places in the kernel, and mainly iptables. None of them are performance relevant unless you use your phone as router for a thousand of machines (and that is the *only* case). Yes, it is utterly useless.
Q: Why do you not implement XYZ?
A: Usually, same reason as jhash3. Feel free to suggest tho, some features are actually useful and I don't know everything.
It only work with CM7??? Or work in a Froyo or Gingerbread rom??
You just can't read?! CM7.
thx bilboa, it's really good
Keep up the good work
Sent from my Galaxy S using Tapatalk
Flashed cwm .zip getting force closes when trying to adjust headphone volume in voodoo app read about this on the cm7 thread might have something to do with 2.3.3 lol I got no idea, just throwing it out there you can throw it right back
EDIT: found the voodoo app on supercurios page http://dl.project-voodoo.org/apps/
Sent from my Galaxy S using XDA App
quadix said:
You just can't read?! CM7.
Click to expand...
Click to collapse
I read perfect, that's only a question, do you understand???
Medel-Silver said:
I read perfect, that's only a question, do you understand???
Click to expand...
Click to collapse
Its very stupid question, hence the a bit rude, yet truthful, answer. It says in the topic what this kernel is for.
I need to backup the WiFi modules before i get flash that?
Thanks a lot for posting this! Do you still have the "old" voodoo control app with you, that works with the headphone amplifier?
Thank you for providing the source code, that gives me an idea on what i have done wrong while implementing voodoo sound
btw have you guys experienced the volume bug mentioned here and here?
Anybody got a solution?
could not download
Sent from my Galaxy S using XDA App
Thanks heaps - installed it apparently ok - it runs the phone - the voodoo app can see the features and recognises that its a compatible kernal - but whenever trying to change the analogue volume - it force closes the app
is this relating to the broken git stuff for cyanogen - unrelated and just me doing something wrong - or its a bug and i can give you some logs or something to check whats happened?
I'll try doing a clean flash from an old firmware and come back again with the results in a few hours when i get home from work (err - probably shouldnt have tried experimenting with it at work - heh)
^^you need voodoo control app and voodoo app for it to get it to work.
@bilboa1
nice to see it's stand alone.
Edit : Crap, i can't get it to download, i've tried different browsers, using my phone. I even tried it from different computer with no luck
It seems github don't like my computer or my phone. Can anyone attach the .zip for i9000, PLEASE.
Hello, I'm from the Captivate forum, just seeing if any known bugs are found I heard Wi-Fi doesn't work.
Also had problems DL'ing. Attached the SGS i9000 file from the CM7_SGS_2011_03_04 folder. Thanks for the kernel!
sorry if this could be a dumb question, but I wanna be sure of what I'm doing:
If i use the CWM package, do I still need to flash te zImage and push the modules??
^^no need to, just flash it from recovery.
~drz
this is base on the latest kernel from the 02/03 update? it's will affect on the speed / smoothness (for bad)?
I think it was built from the latest commit.
just try it out man, if you don't like it, you can just flashed back to the "official" one.
The non-sgs kernel currently check for SGS model before flashing.. which of course won't work ;-) Ill change that when I get a little bit of spare time.
After some work here is my first rom for Mate.
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. DO IT AT YOUR OWN RISK.EVERYTHING WRITTEN IN THIS DOCUMENT WAS TESTED ON MY PHONE.
Stable and suitable for daily use .
Development Finished.
Working:
Audio
Wifi
Display
Led
GPS
Network
Wifi HotSpot
Bluetooth
Youtube HD.
USB
Multiuser
Pie-control
Compiled kernel using surdu_petru's P6 cyanogenmod kernel source.
Camera
Camera Recording (SD, HD720p, HD1080p)
DLNA
DolbyDigital Plus
Facelock
Non-Working :
- FM Radio
- USB Mass_Storage mode (MTP mode is usable without issues)
Known-bugs:
Camera HDR function is not working.
changelog 2014.05.11:
- Added OTA update possibilities.
- Fixed display physical size in kernel.
- Fixed Mediascanner crash
- Fixed MTPserver crash
- Fixed dpi reported by gralloc
changelog 2014.05.04:
- Fixed delay in Youtube HD play/pause.
- Added DLNA
- Added Facelock
- Added Dolby Digital Plus
changelog 2014.05.02:
- Fixed Camera
- Added CPU Governors to kernel (lazy, hotplug,wheatley)
- Kernel modifications (IO Scheduler, memory,minor config changes)
changelog 2014.04.20:
- Fixed PPTP VPN
- Fixed airplane mode switching. Now correctly registers to network after airplane mode.
- Fixed signalstrength , now it is correctly shown both in statusbar and in about phone.
changelog 2014.03.16:
- using compiled vold instead of prebuilt.
- Fixed internal sd handling. Now the main user files accessible only by the owner , second and third users files are separated correctly .
- Fixed USB OTG function. It supports pendrive with ntfs , exFat filesystems too because of the new compiled vold.
- Fixed liboverlay logcat errors.
- Increased headset volume (Thanks to acbka)
changelog 2014.03.10:
- changed to compile kernel from source at build time instead of using prebuilt kernel.
- fixed notification led color (our device does not support blue)
Download:
cm-10.1-20140511-UNOFFICIAL-hwmt1_u06.zip
Install it from permanent twrp recovery , and do not forget to do a wipe .
Use this Google Apps package : Google Apps
Sources : https://github.com/joestone/Huawei-MATE-CM10.1
Thanks to surdu_petru , CyanogenMod Team.
great work ,downloaded
works with the camera app Camera 360?
Thanks joe.stone somethig news
Inviato dal mio MT1-U06 utilizzando Tapatalk
Thanks for your hard work mate, it looks great, but I have a question for you (or anyone who used this ROM): is the audio volume higher with headphones than the stock rom? Because in stock it's very very low in maximum volume.
Shadowprince94 said:
Thanks for your hard work mate, it looks great, but I have a question for you (or anyone who used this ROM): is the audio volume higher with headphones than the stock rom? Because in stock it's very very low in maximum volume.
Click to expand...
Click to collapse
Here is a little TUT to solve your problem.
Click
greez Gadlion
Gadlion^1 said:
Here is a little TUT to solve your problem.
Click
greez Gadlion
Click to expand...
Click to collapse
Yes, but these are not really good solutions, sound is far more better and louder in custom roms.
EDIT: I made some changes in the method, and it works well.
this rom works app 360 camera and flash it???
Thanks.
ErSergi said:
this rom works app 360 camera and flash it???
Thanks.
Click to expand...
Click to collapse
Try it make a backup from your android, and try, you have nothing to lose.
Shadowprince94 said:
Try it make a backup from your android, and try, you have nothing to lose.
Click to expand...
Click to collapse
but if anyone has installed this rom you could try and get more!
Shadowprince94 said:
Thanks for your hard work mate, it looks great, but I have a question for you (or anyone who used this ROM): is the audio volume higher with headphones than the stock rom? Because in stock it's very very low in maximum volume.
Click to expand...
Click to collapse
hi , try my way http://4pda.ru/forum/index.php?s=&showtopic=475994&view=findpost&p=27064535 Russian forum
Tnx for your hard work dude keep on and god bless you
I have faith in you. Keep up the good work.
is it possible to make custom kernel compatible with cm10 so that we can try the p6 roms. It seems only touch driver is different for HAM kernel so is it possible to add touch driver to existing p6 kernels?
svvv said:
is it possible to make custom kernel compatible with cm10 so that we can try the p6 roms. It seems only touch driver is different for HAM kernel so is it possible to add touch driver to existing p6 kernels?
Click to expand...
Click to collapse
The touch driver is different , there is some differencies in camera . The audio is slightly different .
Once I will be able to compile a working touch driver loadable with insmod we will have kitkat.
joe.stone said:
The touch driver is different , there is some differencies in camera . The audio is slightly different .
Once I will be able to compile a working touch driver loadable with insmod we will have kitkat.
Click to expand...
Click to collapse
Not the KitKat one i was referring to 4.2.2 version. I installed p6 green kernel which is a CM compatible kernel in that touch is not working. is it possible to make a similar one for our HAM
svvv said:
Not the KitKat one i was referring to 4.2.2 version. I installed p6 green kernel which is a CM compatible kernel in that touch is not working. is it possible to make a similar one for our HAM
Click to expand...
Click to collapse
It is done , now based on P6 Cyanogenmod (green) kernel.
First post updated.
joe.stone said:
It is done , now based on P6 Cyanogenmod (green) kernel.
First post updated.
Click to expand...
Click to collapse
Thank you so much for your hard work joe.stone.....
google store not working
the google store isnt letting me install or update any of my apps. help please
noobK1user said:
the google store isnt letting me install or update any of my apps. help please
Click to expand...
Click to collapse
Did you install the correct Google Apps package (see first post) ?
Did you wipe / factory reset before ROM install ?
OmniROM for P900 Only
installation:
install custom recovery TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
install omnirom with recovery
install gapps (optional): http://forum.xda-developers.com/showthread.php?t=2397942
for root flash zip file with recovery: http://download.chainfire.eu/589/SuperSU/
Changelog:
R2:
-improve overal stability
-bug fixes
known issues:
camera is not working
buttons backlight is not working
download links:
R2:
P900 https://yadi.sk/d/SUn2aByFcaEAM
XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy Note Pro 12.2
Contributors
bonuzzz, Valera1978, arcadia2uk
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-11-04
Last Updated 2014-11-20
Reserved
To anyone who flashed this, can you do the following immediately after installation?
1) Let the rom be installed and after setting up everything that it may be required from you (your google account?), wait for a while and then reboot the tablet.
2) Once the reboot is completed go to Settings-> Apps and from there navigate to the "Running" TAB. Once there please report the "USED" amount (it would be like "700MB used", or sth like this).
Thanks.
Latest update: 11082014 2.30pm EST
Thank you bonuzzz and Valera1978. This OmniROM directly built from source is out of the box the smoothest and reactive ROM I've seen on the T-900. I have been fortunate to run this version in alpha and beta over the past 4 or 5 days and I have not seen any extraordinary issues with the release.
Note for v.2 - Be very patient in flashing v2, from that system format starts in TWRP until extraction kicks in there's currently a delay of up to 3 minutes
Just as under the SM-P900 cm11 tread, I have performed some functionality testing of the device and some extra features, they are shown below as working, not working or not tested. The functionality grid was developed based on weaknesses in earlier AOSP builds and ports for the large format Samsung Tab/Note Pro family:
- mtp - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/ activated. Check mark USB debugging notify.
- adb
- External SD - working out of the box
- Ext4 SD card mounting on external SD - Auto-mount does not work, tested on Sandisk 128Gb SD
- USB OTG including USB storage
- Off-mode charging
- Encryption tested on backup restore in TWRP 2.8.1.1 restore failed in data, but must be related to a TWRP error Encryption process in ROM takes about an hour to perform, if someone is interested in performing the test and report back it would be great, but theoretically it should work.
-----------------------------------------
- Lid sensor
- IR blaster - worked by using IR 2.0
- OC settings - located in Settings/Performance/ if you click the 3 dots in upper right corner you can chose a toggle, or a drawer mode where a multitude of performance settings and information is available, most of them are currently not used.
- Advanced reboot - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/. Check mark Advanced reboot.
- Screen rotation specific issue with T-900
-----------------------------------------
- Play Store
- Google Play movies download and playback
- Google Play streaming Movies & TV
- DRM - tested with Audible, Google Books and Amazon Kindle
-----------------------------------------
- Zona
- Popcorn Time - need upgrade to latest version 2.3 beta, includes built-in VPN and Chromecast support with subtitles, earlier version timed out
- YouTube 1080p playback - 1440p will work w. v5.9.0.12, but I believe this to be a false positive.
- Netflix
-----------------------------------------
- Chromecast with #MirrorEnabler hack, allowing for screen cast
- MHL connector
- Miracast
-----------------------------------------
- Capacitive lights - I assume this is the backlights for the capacitive buttons
- Capacitive keys
- Home button - correct function performed
- Brightness manual + auto
- Vibrator
- S-Pen according to OP only available on P-900
-----------------------------------------
- GPS lock and voice directed navigation
- WiFi both 2.4 GHz & 5 GHz are working
- Bluetooth
- Microphone
- Audio on both speakers
- Headphones
-----------------------------------------
- Camera - in progress; the camera "works", but does not allow for single shots to be taken, and crashes in video mode, but panorama shots are working
- Torch as of v2
- Camera Sensors as of v2
-----------------------------------------
- Xposed Framework and modules - need re-initialization after each boot (common to all AOSP ROM's)
- Superuser - installation of latest flashable version SuperSU through TWRP is recommended - make sure to enter into SuperSU settings and execute "Install SuperSU backup script" under the CUSTOM ROM label before re-flashing a ROM update.
- Hangouts Dialer phone calls via Hangouts
-----------------------------------------
The following are standard limitations and options for OmniROM:
Write access to your external SD-card works out of the box, but just in case i suggest to d/l JRummy's SD KitKat Fixer
init.d support also works out of the box, otherwise d/l Uni-init by Ryuinferno.
If you think to much heat is building up use Performance/Governor set to ondemand, or conservative and I/O Schedduler to bfq, in addition to increase battery time you can set Wi-Fi/Advanced/Keep Wi-Fi on during sleep/ to Only when plugged in and make sure the Wi-Fi/Advanced/Wi-Fi optimization/ is checked and reduce Display/Sleep/ to below 1 minute. You can also use some apps to improve battery eg Easy Battery Saver, or the more sophisticated AutoCon+ Save Battery & Data and and to put hanging apps to hibernation Greenify that I believe require Xposed Installer. To improve charging time, you can use an app eg Faster Charger. Finally, I have also used PurePerformances in order to further improve the performances and VIPER4AndroidFX to allow for louder speaker sound and enhanced listening experience.
Stevethegreat said:
To anyone who flashed this, can you do the following immediately after installation?
1) Let the rom be installed and after setting up everything that it may be required from you (your google account?), wait for a while and then reboot the tablet.
2) Once the reboot is completed go to Settings-> Apps and from there navigate to the "Running" TAB. Once there please report the "USED" amount (it would be like "700MB used", or sth like this).
Thanks.
Click to expand...
Click to collapse
1.1Gb RAM used, but I'm running MultiROM, besides that I had only installed SuperSU and Pico gapps, I have exactly the same usage displayed with cm11.
IR port is working. Tested with smart ir
flip cover is working also
I dont understand issue with screen rotation
bonuzzz said:
IR port is working. Tested with smart ir
flip cover is working also
I dont understand issue with screen rotation
Click to expand...
Click to collapse
The screen doesn't automatically rotate when turning the device, although I have automatic rotation enabled in System/Display/ with values 0/90/180/270. However, with some apps a forced rotation arrive that turn the screen from landscape to portrait, after this the screen stay in portrait until another app trigger a turn to landscape. Anyway, blocking the screen in landscape, or in portrait with the apps I mentioned in my post works perfectly well, but it's a forced rotation, not automatic. It could be device specific? - note issue only concern T-900, not P900/901
I retested IR and Lid and they worked when flashing the ROM with TWRP 8.2.1.1. This was either a glitch, or the fact that I flashed in MultiROM.
arcadia2uk said:
For me the screen don't rotate automatically when turning the screen, although I have automatic enabled in System/Display/. However, with some apps I have automatic rotation that turn the screen from landscape to portrait, after this the screen stay in portrait until another app trigger a turn to landscape. However, blocking the screen in landscape, or in portrait with mentioned apps works perfectly well, but it's a forced rotation, not automatic. It could be device specific?
Click to expand...
Click to collapse
download please z-device test https://play.google.com/store/apps/details?id=zausan.zdevicetest and send me screenshot of his report
multirom in current state uses kernel from primary rom in additional roms. Concerning screen rotation, I think it is specific for t900 and I'll solve it in next release.
bonuzzz said:
download please z-device test https://play.google.com/store/apps/details?id=zausan.zdevicetest and send me screenshot of his report
multirom in current state uses kernel from primary rom in additional roms. Concerning screen rotation, I think it is specific for t900 and I'll solve it in next release.
Click to expand...
Click to collapse
That kernel use can explain some of the oddities I've experienced.
On the T-900 I had the screen rotation issues as well, along with other users, so I believe it's a T900 issue. It works with stock ROM though. Also, I just forwarded some screen shots.
Hey guys thanks for yet an other custom rom you sure have been working hard! I did some reading about this omnirom and i conclude imo it is prefereable to cyan, is valeria working only on omni now i noticed she released a new cm. Thanks again looking forward to next release.
Hi friends, I wanted to thank you for bringing OmniRom to the Note Pro 12.2.
I will be sure to install it this coming weekend when I have some time
I'm currently on CM and it's very nice, but I like the idea of Omni being truly open source.
Your efforts are greatly appreciated.
Ok I was excited when OmniROM was originally announced but honestly that was mostly because of the multi window stuff the is now available via Xposed. How is Omni better than CM? I have to say I have the CM build on my tablet and it's exceptional, can't believe it's this good when the Note 12.2 just recently become supported. Is Omni really noticeably faster/smoother?
rkirmeier said:
Ok I was excited when OmniROM was originally announced but honestly that was mostly because of the multi window stuff the is now available via Xposed. How is Omni better than CM? I have to say I have the CM build on my tablet and it's exceptional, can't believe it's this good when the Note 12.2 just recently become supported. Is Omni really noticeably faster/smoother?
Click to expand...
Click to collapse
My experience running the beta release that even at this stage it is already faster and smoother than cm-11. Try it and and you can tell directly by the screen transitions, and this is just the beginning. But the reason for OmniROM is more flexibility, it's a true AOSP ROM, meaning there's a lot more flexibility in deploying the code, than under cm that start loosing its freedom in development under a corporate flag. Besides, Omni is already better prepared for this, you can see this in it's deployment of the OmniSwitch as well as other features, eg. under the performance tab, where OC, undervoltage and other settings, and there is more...
However, the best way is to try it out and judge for your self.
On the other hand, if you really want to read up about it, check out this article
arcadia2uk said:
My experience running the beta release that even at this stage it is already faster and smoother than cm-11. Try it and and you can tell directly by the screen transitions, and this is just the beginning. But the reason for OmniROM is more flexibility, it's a true AOSP ROM, meaning there's a lot more flexibility in deploying the code, than under cm that start loosing its freedom in development under a corporate flag. Besides, Omni is already better prepared for this, you can see this in it's deployment of the OmniSwitch as well as other features, eg. under the performance tab, where OC, undervoltage and other settings, and there is more...
However, the best way is to try it out and judge for your self.
On the other hand, if you really want to read up about it, check out this article
Click to expand...
Click to collapse
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Thanks for the info and that is an interesting read. I'll probably give OmniROM a try...
notspike said:
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Click to expand...
Click to collapse
I don't believe it is implemented. But, the split view feature in the video exist as the xposed module: XMultiWindow. This was Omin's first release of the multi-window feature, and the development is still ongoing for a more feature packed floating window solution. See for example this concept idea.
notspike said:
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Click to expand...
Click to collapse
multiwindow had been removed from omnirom in spring 2014.
published first release for P901. I dont have this tab, so I cant testing. I hope mobile part is working here. Write your feedback please
bonuzzz said:
published first release for P901. I dont have this tab, so I cant testing. I hope mobile part is working here. Write your feedback please
Click to expand...
Click to collapse
can't download it !! when i press the download button nothing happens!! does camera work in this build ?? Thanks.
francesco totti said:
can't download it !! when i press the download button nothing happens!! does camera work in this build ?? Thanks.
Click to expand...
Click to collapse
https://yadi.sk/d/xTQ0HUhocaBpC
no. camera is not working yet
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
Click to expand...
Click to collapse
Images
Possibly the fastest [clean] ROM for our device, benchmarks coming soon .
Click to expand...
Click to collapse
Features
Google's exclusive features for Pixel devices (except Music Ticker and Call Screening)
Lawnchair launcher
Spoofed stock device to pass SN
Widevine L3
Faster encryption device-wide
Daydream VR
Fast, optimised Zest Kernel
EAS
Markup screenshot editing
Google Sound Picker
Google Wallpapers
Digital Wellbeing
Optimised GPU rendering for Pie
Custom Clang and GCC toolchains for building - optimised LLVM with PGO, and GCC 9.1
OpenGApps pico included
GCam HDR+ support
Click to expand...
Click to collapse
Installation instructions
* Go download https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-yoshino.
* Unzip the download to get an .img file.
* Install fastboot (drivers for this can be gotten from Google directly), drivers for flashmode for Windows can be gotten from newflasher.
* Enter your command prompt or terminal whatever and fastboot flash oem THEFILEYOUEXTRACTED.img.
* Find a decent TWRP and flash it.
* Download the ROM for your device. They are all in this folder https://jenkins.cosmic-os.org/job/zfsodp-core/ws/lastbuild so click the one for your codename (eg. G8141 is single sim maple and G8142 is dual sim maple).
* Flash it in TWRP and wipe internal storage and format data (the option that has red text and makes you type yes).
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is on my Jenkins job.
Click to expand...
Click to collapse
FAQ
PM me in XDA's Sony group.
Click to expand...
Click to collapse
Special Thanks To
Code:
* @kholk for his kernel advise
* @Sultanxda for his kernel advise
* @deletescape for Lawnchair
XDA:DevDB Information
Zest-flavoured SODP, ROM for the Sony Xperia XZ Premium
Contributors
LazerL0rd, The entire SODP team
Source Code: https://github.com/ZfSODP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Sony OSS OEM binaries
Based On: SODP
Version Information
Status: Beta
Beta Release Date: 2019-07-06
Created 2019-07-06
Last Updated 2019-08-10
Reserved
Reserved
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
del
Can I flash the kernel through twrp, then flash the zip?
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Give it a week or so mate, lazerl0rd is studying/having exams for a while.
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Any screenshot of the performance?
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
still on logo android !/
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Moarten said:
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too.
Laplacetor said:
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
Click to expand...
Click to collapse
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too. ROM isn't on my website and never was .
wolfmanstr said:
Can I flash the kernel through twrp, then flash the zip?
Click to expand...
Click to collapse
Don't use my stock kernel with this.
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
It performs better, battery is decent now (after a load of changes). We now (as of today) have a Power HAL (libperfmgr) which supports DT2W on supported devices too. I may or may not update it to version 1.3.
SilverGamer_YT said:
Any screenshot of the performance?
Click to expand...
Click to collapse
No, it's EAS and you could test it out.
tronganhha29 said:
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
CRNO said:
still on logo android !/
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now.
Sjll said:
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now. EAS seems stable, here. The bugs we have aren't really EAS related.
undefine said:
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least. I changed up the thermal driver so it should be good now. Btw those thermal modules in Magisk won't change a thing as I use sultan's thermal framework now - not RQBalance stuff. DPI has an option on setup under "vision", choose what you like. I added GCam instead, it's gonna be better quality than Sony's crappy cam app. Ancient app logos aren't gonna be updated, these are ASOP packages - instead I'm replacing them with Google packages. Also I made everything Squircle shaped too. Device-wide dark mode will be coming soon, needs some kanging [with original authorship] from Q. Phone application should be de-google-ified -> you can turn off the spam filter and install any Dialer you want. I'm not dealing with darkening AOSP's package so that's why I'm using Googles. Google can get your data if Play Services is installed anyways. Option to switch resolution and frame rate on the go -> idk why SODP removed that.
Astoras said:
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
Click to expand...
Click to collapse
For Android kernels, you can't just chuck a module in. But I'll add it to the kernel config for ya.
CRNO said:
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Click to expand...
Click to collapse
Already done. And - "I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least."
AIO for NB1
This is a joint project that gives the Nokia 8 on stock rom a new life
Check 3rd post for more info+updates
Update:The Last Update for Non-Treble version has been released with all bug fixes, Now I'll focus on Treble version of AIO. Non-Treble will no longer be updated.
Ultima Boot Image+Umbrella Mod Kernel for NB1[V11]
Works on all security patches for 00WW_5_XXX
- Using an older build with modifications and can't update? Flash this Firmware First!(Then get the latest update from OTA)(Flash this using NOST) Firmware Link
- Make sure to be on Build 00WW_5_XXX_XXXX before installing this!
Here's some of the stuffs that I've included:
1.TWRP
2.Magisk(After flashing boot image open Magisk manager and follow the prompts)
3.A nicely modified kernel including Energy Aware scheduling
4.Modifications for better support
5.Contains Many Bug fixes
Download link(s)
Non-Treble(Stock Rom)
Click to expand...
Click to collapse
How to install?
Using Phone:
TWRP Method:
TWRP>Install>Install Image>Select file>Flash boot>Flash>Reboot>Done
Flasher Method:
Flash using kernel managers that has flasher support
Using PC:
Put phone in download mode
[Old ADB Tools] ADB command: fastboot flash boot [Filename] > fastboot reboot > Done
[New ADB Tools] fastboot flash:raw boot [Filename] > fastboot reboot > Done
Click to expand...
Click to collapse
Ultima Script for NB1(Maximum efficiency)
Download link https://drive.google.com/folderview?id=1RHbV3b1qPjWT1kYOBxTRRpm5VxDjsc28
Add-on(Optional): https://drive.google.com/file/d/1ROWsE854_6MOg7y55j2qE5ZZaxvj8ISF/view?usp=drivesdk
!Make Sure to use the custom Kernel for best results!
What it'll do?
-Improve Battery and Performance
-Disable Useless services,Trackers to improve performance and battery(Add-on)
Click to expand...
Click to collapse
How to use?
Run this on terminal
su
sh /sdcard/[Path to the file]
Or,
In Kernel managers, Look for script manager and run it from there(you can also make it apply at boot)
Read this part!
To fix some apps crashing and idle drain problem after using the add-on script:
1. Install this app https://drive.google.com/file/d/1MqdH1lbBaCOK2pUEXbTR4LH71vJ7PQh6/view?usp=drivesdk
2. Enable "FirebaseInitProvider"
under the "Content provider" section of the app that's crashing.
3.Enable " Auto Block" and " Force Doze" in the settings if that app
NOTE: It can take from 1-10 minutes for Add-on depending on the amount of apps you have installed and run this only once
Click to expand...
Click to collapse
Recommended Kernel Manager: https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
Update GPU drivers:
Vulkan: https://forum.xda-developers.com/nokia-8/development/update-vulkan-driver-to-1-1-128-t4090575
OpenGL: https://forum.xda-developers.com/nokia-8/development/pie-update-opengl-drivers-to-454-0-t4090699
Click to expand...
Click to collapse
Laxxed Thermal is currently being worked on It'll be uploaded under new thread
Join our telegram group for latest updates!
https://t.me/HMD_Nokia_8
Credits:
TWRP Team(For TWRP- https://twrp.me/)
TopJohnWu(For Magisk- https://github.com/topjohnwu/Magisk)
Radu-V(For custom Kernel- https://github.com/radu-v/umbrella-mod)
tytydraco(For ktweak, which was modified for NB1 by me- https://github.com/tytydraco/ktweak)
Click to expand...
Click to collapse
At last... someone did it.... although I can't call it a custom ROM, I can definitely enjoy the new kernel
I'll try it as soon as I can to give you feedback
Thx dude :good:
Stuffs Currently being worked on:
1.Laxxed Thermal
Version Changelogs For Ultimate Boot Image:
Release V1:
Initial release
Update V2, Changelog:
1.Hot-Plugging support [Experimental- May decrease performance when turned on]
2.Better Performance
3.Latest CAF tags
4.Latest Magisk Canary(works better)
Update V3, Changelog:
1.Removed Hot-Plugging support (Decreased performance, Might re-add later)
2."blu_schedutil" CPU governor added(Better Battery, I personally gained 1h30m of extra normal usage time)
3.GPU NAP State(Better Battery when GPU has low load/no load)
4."lzo-rle" z-ram compression algorithm(Upto 4.4 times more z-ram performance)
5.Force fast charge support(Fast charge enable/disable forcefully)
Update V4, Changelog:
1."pwrutilx" CPU governor added(For gamers)
2.Wireguard Support(New VPN protocol)
3.StuneBoost added
4.RTB Disabled for better performance
5.Removed unnecessary GPU codes(Should improve performance)
Update V5, Changelog:
1."CRC" Toggle[Disable to Gain Upto 30% extra performance]
2.Magisk Canary from 20425->20426
Update V6, Changelog:
1.Removed A LOT of unnecessary codes
2.(Attempt)to fix the heating issue
3.(Attempt)Battery Life improvements
4.Fully Reworked on EAS(Much better)
5.Led Notification Fixes(Using HW keys)
Update V7, Changelog:
1.Patches for CPU scheduler(Better battery)
2.Some patches for the random number generator(Improve performance on apps what require random numbers)
3.Fixes/Updates for CFQ(More up-to-date)
4.Fixes/Updates for Binder(More organized)
5.Removed dynamic stune(Useless, Worse performance+Battery)
6.Removed some logging(Unnecessary)
7.Removed A1N, PM1 and F11 code(More stability)
8.Magisk Canary Version 20426->21001
9.Attempt to fix Excessive battery drain and Heatups
Update V7.5, Changelog:
1."iowait_boost_enable" bug fixed
2.Excessive Battrey drain and Random Heatups Fixed(YAY ?)
Update V8, Changelog:
1."TTL" Fixation/Editing Support(Tethering Hack)
2.Disabled some logging(Better performance)
3.Removed POPP(Unnecessary)
4.Removed ssusb wakelock(Better Battery)
5.Scheduling improvements(Better tasking)
6."qseecom" updates
7.Battery life and performance improvements
Update V9, Changelog:
1.Fixed Random reboots
2.Updated Haptic Driver
3.TTL Changing Improvements
4.Silenced More Logs
5.Magisk Canary 21001->21004
Update V10, Changelog:
1.Fixed *Most* Bugs
2.Fixed Screen Off Audio Issues
3.Small Fixes Here and there
4.Magisk Canary 21004->21005
5.Small Adjustments for better Support
Update V11, Changelog:
1.Every Single bug has been fixed!(5ghz Hotspot too)
2.Magisk Canary 21005->Magisk Stable 20.4
3.Radical Changes
4.More bugs added to be fixed later(I'm Joking lol)
Update V12[Final(For real this time)], Changelog:
1. Based on the latest security patch
2. Full rework of EAS
3. Magisk Stable 20.4->Magisk Stable/Beta 21.1
This will be the last update since all bugs and nothing more to be added. However, I'll start working on Treble version soon!
Click to expand...
Click to collapse
Version Changelogs for Ultima Script:
Release V1: Initial release
Update V2: Disable unnecessary services(Add-on)
Update V3: Reduced Read Ahead for better Read/Write performance
Update V4: Reduced Read Ahead even more, Added extra tweaks, Latest version of Ktweak
Update V5: More power efficient
Click to expand...
Click to collapse
OneWayGamer said:
I'm working in Lineage OS. Can't tell when it'll be released tho
Click to expand...
Click to collapse
Can't wait for that one too :fingers-crossed::fingers-crossed:
Oh and I tried your image... works flawlessly... I'm liking Kcal so far... however I can't find a way to implement the kernel support for HW buttons as a notification led... Do you know any apps or mods that make use of it?
Ayhem-GH said:
Can't wait for that one too :fingers-crossed::fingers-crossed:
Oh and I tried your image... works flawlessly... I'm liking Kcal so far... however I can't find a way to implement the kernel support for HW buttons as a notification led... Do you know any apps or mods that make use of it?
Click to expand...
Click to collapse
The back button is working as a notification led.
Ayhem-GH said:
Can't wait for that one too :fingers-crossed::fingers-crossed:
Oh and I tried your image... works flawlessly... I'm liking Kcal so far... however I can't find a way to implement the kernel support for HW buttons as a notification led... Do you know any apps or mods that make use of it?
Click to expand...
Click to collapse
I use Light Flow Pro
Mod edit: Hyperlink to paid app removed!
XDA Forum Rules (please refer to rule no. 11)
Ayhem-GH said:
At last... someone did it.... although I can't call it a custom ROM, I can definitely enjoy the new kernel
I'll try it as soon as I can to give you feedback
Thx dude :good:
Click to expand...
Click to collapse
Check out the new update ?
Originally Posted by OneWayGamer
I'm working in Lineage OS. Can't tell when it'll be released tho
Click to expand...
Click to collapse
That is so cool, I guess it's sorta what all of us N8 users was wishing for, more or less. :good: to ya buddy!
Ayhem-GH said:
Can't wait for that one too :fingers-crossed::fingers-crossed:
Oh and I tried your image... works flawlessly... I'm liking Kcal so far... however I can't find a way to implement the kernel support for HW buttons as a notification led... Do you know any apps or mods that make use of it?
Originally Posted by OneWayGamer
The back button is working as a notification led.
Click to expand...
Click to collapse
I can't get that to work in Light Flow Lite, guess I'm not seeing it. Or it doesn't work in the app's test mode. (Edit, it seems to work with bk button when charging, so it might just work after all, we'll see. )
OneWayGamer said:
Check out the new update ?
Click to expand...
Click to collapse
Ohh so we have an update. Awesome. Good work!
iMaterial said:
That is so cool, I guess it's sorta what all of us N8 users was wishing for, more or less. :good: to ya buddy!
I can't get that to work in Light Flow Lite, guess I'm not seeing it. Or it doesn't work in the app's test mode. (Edit, it seems to work with bk button when charging, so it might just work after all, we'll see. )
Ohh so we have an update. Awesome. Good work!
Click to expand...
Click to collapse
Another Update is here! (Check 3rd post)
OneWayGamer said:
Another Update is here! (Check 3rd post)
Click to expand...
Click to collapse
:victory: :highfive:
This is awesome. Thanks Bro.
It works perfectly. ???
Finally things are starting to happen around here. I see the thread had a name change.:silly:
:highfive:
Hi buddy. I would if I could buy you a beer.
Q: how to control led notification? Both butrons stay ON when connected to charge. No other notificational behavior. Tried Light Flow. Searched SmartPack.
Q: I see random short freezes while working with phone, do you?
Less importantly:
Q: do you consider TWRP better than SHRP?
Q: Magisc... I had to install it again from magisc manager to make the kernel manager work.
I using v3 on sp03. Flashed by SHRP.
Arashone said:
Q: how to control led notification? Both butrons stay ON when connected to charge. No other notificational behavior. Tried Light Flow. Searched SmartPack.
Click to expand...
Click to collapse
In Light Flow you need to enable Root Mode under Device Settings and Root and under LED Control choose Control - Light Flow controls the LED (although it works for me with No Control with some limitations)
Arashone said:
Q: how to control led notification? Both butrons stay ON when connected to charge. No other notificational behavior. Tried Light Flow. Searched SmartPack.
Click to expand...
Click to collapse
A: On SmartPack Kernel manager, Look for "Device and Led" Option
Arashone said:
Q: I see random short freezes while working with phone, do you?
Click to expand...
Click to collapse
A: Get V4, Use "lzo-rle" Z-ram compression algorithm, Try "schedutil" and "blu_schedutil" CPU Governors. Should fix the random freezes[Although, Mine got significant performance boost(Check the attached screenshots in main post)]
Arashone said:
Q: do you consider TWRP better than SHRP?
Click to expand...
Click to collapse
A: Yes(For now, SHRP Has weird bugs)
Arashone said:
Q: Magisc... I had to install it again from magisc manager to make the kernel manager work.
Click to expand...
Click to collapse
A: That's Normal
OneWayGamer said:
A: On SmartPack Kernel manager, Look for "Device and Led" Option
A: Get V4, Use "lzo-rle" Z-ram compression algorithm, Try "schedutil" and "blu_schedutil" CPU Governors. Should fix the random freezes[Although, Mine got significant performance boost(Check the attached screenshots in main post)]
A: Yes(For now, SHRP Has weird bugs)
A: That's Normal
Click to expand...
Click to collapse
Great. This SmartPack thing, is quite a tool... Although under Display and LED, there is just a slider to turn everything off. Btw, that's cool. Should dig in more.
the option for overclock, does it (almost safely) work?
Arashone said:
Great. This SmartPack thing, is quite a tool... Although under Display and LED, there is just a slider to turn everything off. Btw, that's cool. Should dig in more.
the option for overclock, does it (almost safely) work?
Click to expand...
Click to collapse
What overclock are you talking about? It's already set to the highest value
Excellent work, although there are several details, the first is that the battery drains very quickly and heats up constantly only using light apps; with the last two kernel versions. Also, the UltimateScript script causes some applications to crash. The effort for the development of this device is appreciated
TlalocC said:
Excellent work, although there are several details, the first is that the battery drains very quickly and heats up constantly only using light apps; with the last two kernel versions. Also, the UltimateScript script causes some applications to crash. The effort for the development of this device is appreciated
Click to expand...
Click to collapse
We are looking into the battery drain problem. The heatups are expected, because cpu is always running at max frequency, though it shouldn't cause high drain. As for the apps crashing, install this https://drive.google.com/file/d/1MqdH1lbBaCOK2pUEXbTR4LH71vJ7PQh6/view?usp=drivesdk and enable "FirebaseInitProvider" under "Content provider" for the apps that are crashing. And to fix idle drain issue, simply turn on "Auto Block" and "Force Doze" in the settings of that app
OneWayGamer said:
We are looking into the battery drain problem. The heatups are expected, because cpu is always running at max frequency, though it shouldn't cause high drain. As for the apps crashing ....
Click to expand...
Click to collapse
I tried the app you recommend but it didn't work for me with some system apps like Google's, also when I rebooted I was stunned by the unlocked bootloader warning. Better opt to reset and not install the script to avoid that problem. Anyway good work