Database Info

[ROM] CyanogenMod 10 (qwerty)

Here is where I'll post my CM10 builds.
qwerty was the name I gave to the kernel I used to post here before I started to post entire ROM builds.
This is based on the amazing dhiru1602's work, big thanks to him.
Dowloads:
Google Drive
You can't resume downloads with GDrive. If you prefer other hosting websites, you can use the direct link of my builds to remotely upload them somewhere else. Dev-Host allows you to do that and allows you to resume downloads. Feel free to mirror my files.
Sources:
Device, kernel, vendor
Misc changes/instruction to build this ROM. The patches not available on Github are here.
Please, read carefully the whole post.
There are two different versions of the ROM. One is using the kernel 3.0, the other the kernel 2.6.35. Read the known bugs and flash the one you prefer.
I did some changes to this CM-10, I updated it and added some extra features such as inbuilt SD swap (Settings > Storage > Use external storage), possibility to show the navbar without rebooting (System > Power menu > navbar and enable it from the power menu. It doesn't work perfectly, keyboards and notification panel can go behind it) possibility to limit the number of background apps and other handy options.
I also backported some performance patches and misc fixes from CM-10.1 and some apps: Trebuchet, Apollo, Gallery (camera), Clock, CM File Manager and Superuser.
CyanogenMod 10 - kernel 3.0
Click to expand...
Click to collapse
Known bugs:
Backlight issues for some users: the screen backlight will automatically turn on when it's supposed to stay off.
Audio/video sync issues while recording videos at 720p, along with frames and fps drops.
Rare reboots. If they happen, post the content of /proc/last_kmsg.
CyanogenMod 10 - kernel 2.6.35
Click to expand...
Click to collapse
Known bugs:
Missing HW composer.
WiFi doesn't work perfectly. Some users report continuous disconnections or problems connecting to netowroks. Try to use a static IP in case you have problems.
Native USB tethering doesn't work. Use a third party app (tested: android-wired-tether).
The inbuilt Wi-Fi hotspot can be used only once, sometimes more, and after that a reboot is required to use it again. You can though use this modified version of android-wifi-tether, reboots are not required.
HD video playback suffer low framerate issues.
The 720p preview framerate is intentionally limited, especially while recording. The recorded video is (almost) fine.
There are sometimes lags in the preview while video calling with the front facing camera
Poor bluetooth headset sound quality. (I don't own a bluetooth headset, hence it's very hard for me to find the problem) - flash libaudio-BT-NR-fix.zip.
Release changes:
Code:
Look for the name of the zip in this thread to find its changes. This is no more updated.
...
20130425: Camera HAL updates. Removed background apps limit. Use the modified dev settings to choose the number of background apps.
20130416: Camera HAL: experimental changes
20130407: Partially working WiFi tethering (perfect with [I]android-wifi-tether[/I])
20130402: Several kernel changes, UMS regression fixed
20130329: Video pillarbox. Regression: UMS requires adb
20130326: Optimized build
20130320: SSID fetch fixed
20130319: Better wpa_supplicant support: WiFi scan and disconnecting bug fixed. Missing WiFi signal intensity fixed.
Instructions
Click to expand...
Click to collapse
Stock ROM / CM7 / CM9 / CM10 Alpha3 (or older):
dhiru1602 said:
IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
This ROM will wipe data due to different partitioning. The device would reboot while flashing and resume again.
Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
Click to expand...
Click to collapse
Stock ROMs only: Make sure you have CWM. Flash a custom kernel otherwise
Download the zip of the ROM and save it into the internal SD or the external one (*)
Reboot to recovery
Flash the downloaded zip
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
optional: Flash Google Apps (for Android 4.1.2, many things will break otherwise)
Reboot
(*) While flashing, the device will reboot and you'll see a different recovery after that.
If the zip is inside the internal SD, the flash will re-start automatically after the reboot.
If the zip is inside the external SD, you have to re-start the flash manually re-flashing the zip. If you don't do that, only recovery will work until you flash the zip.
CyanogenMod 10:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps (if you have already flashed them once, you can skip this step)
Reboot
Data wipes are mandatory only if you are not using CM10, it's not required otherwise.
It doesn't matter if you are going to flash the version with the 3.0 kernel and you are using the other, it should work.
CyanogenMod 10.1/10.2:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
Wipe data/factory reset
Reboot
Downgrades are probably not expected, that's why you need to do a data wipe.
Important note:
The modem is always replaced with XXLE4 modem when this ROM is flashed over a stock ROM, CM9 or CM10 Alpha 3 (or older).
You can easly replace it. Take modem.bin from the tar of a stock ROM, place it in /radio overwriting the existing one and reboot. This is required only once, modem.bin is never replaced while updating the ROM. I9003L must do this, I9003 users can use the included modem, but it's better to use the modem made for your region.
Useful informations
Click to expand...
Click to collapse
The latest versions of Instagram are not working due to a problem with related to the GPU binary blob. Instagram 3.4.0 is the latest working version. Probably every device using the same binary blob is affected (Optimus Black for example). You can download a modified version from here that will allow you to login.
The latest versions of Skype do not work properly, the preview is stretched and wrongly rotated. Use Skype 2.9.0.315 or see this post.
LEDs are not supposed to blink when a new notifcation arrives. They'll light up, but they won't blink. Making them blink would prevent the device from entering deep sleep.
(3.0 kernel) Once the battery is fully charged, it will start discharging and it won't be recharged automatically if at least 90 minutes have passed. You can forcefully charge it by unpluggin and re-pluggin the cable. This is an intended behaviour, charging the battery continuosly to keep it at 100% can shortnmyself toer its life.
This ROM allows you to force two apps to stay in memory. See this post for more info.
I made possible to toggle the navbar state directly from the powermenu modifying the existing expanded desktop feature, however it's not working perfectly. The navbar can go over the notification panel and the keyboard while in landscape. However it works as expected if you enable the navbar by setting qemu.hw.mainkeys or modding framework-res.apk. I have no intention to "fix" this as I can't see the utility of the navbar on our device.
(3.0 kernel) For some reason when the screen is turned off during a call by the proximity sensor, if enough time has passed it won't be turned on automatically. You can wake the screen immediately by pressing the home button or the power button or you can increase the backlight timeout from the settings. That will make the proximity sensor work for longer (I'm not sure, but I think the proximity sensor stops working exactly after this timer has expired). this problem is maybe solved.
FM radio is available through third party apps, such as Spirit FM
"Native" 3G video calls are not supported and most likely never will, flash a stock ROM if you need them. GTalk, Skype and all the other apps works though.
(3.0 kernel) if you lost your IMEI, WiFi will probably not work. See this for more info and instructions to fix the problem. No more required.
(3.0 kernel) part of the RAM is reserved. You'll see that we have 442MB 454MB of RAM, that's fine, the missing RAM is not really lost, it's still used.
If the keyboard keeps crashing, you probably flash the wrong gapps.
The magnetic sensor sometimes reports wrong values. When it happens, the field intensity is very high. This was observed with the 3.0 kernel, but probably the same thing happens with a 2.6.35 kernel.
(3.0 kernel) my SD card (it's probably a cheap SD card) is not working properly and I often have corrupted files. It worked fine with the kernel 2.6.35, so if you often have corrupted files, try a different SD card or use the old kernel.
Weird activity in standby? Read this.
(3.0 kernel) 1.2GHz is not stable on every device. I had to disable SmartReflex because it was causing crashes on my device. This means that the voltage of the OPP5 is locked the value I chose is not universally good. I'd prefer not to increase it more, if you have too many reboots, don't overclock. WARNING: don't tick "Set on boot" unless you are sure your device can handle OC. f you are stuck in a bootloop, flash disable_opp5.zip.
In case the max frequency is 1.1GHz, then SmartReflex is enabled and the option in DeviceParts has no effect.
If you find a bug not listed, please report.
Post as many informations as possible, ways to reproduce it and logs.
You can easily grab (almost) all the logs I need by pressing vol down, vol up and power at the same time ("recent" builds only). LEDs will blink and /storage/sdcard0/logs_qwerty/log_DATE.txt will be created. In case the memory is not ready, you'll find the files in /data/logs_qwerty/log_DATE.txt.
The standalone kernel is no more mantained. Flash the ROM instead.
Click to expand...
Click to collapse
Kernel - 2.6.35
Click to expand...
Click to collapse
After months of use, I decided to publicly release my kernel.
This is for CyanogenMod 10 Alpha 4.
It's based on the GB kernel sources released by Samsung (GT-I9003_GB_Opensource_Update2.zip), modified (mostly by dhiru1602) to work with CyanogenMod.
Because of my lack of fantasy I named it "qwerty". It sucks, but at least it's easy to remember.
Main features:
XDA_Bam's code and fixes:
◦ 5 OPPs
◦ Booting at stock speed (1000MHz)
◦ Slight undervolt (3%) on all OPPs
◦ Home button double presses fix
◦ Lowered processor transition latency
◦ Stable Bluetooth connections
Modified light sensor driver: [1]
◦ Disabled hardcoded filter. CyanogenMod has its own filters, enable it from the settings.
◦ Dynamic polling interval
◦ Code cleanup
Modified battery driver [2]
CPU Governors:
◦ Ondemand (default)
◦ SmartassV2
◦ Conservative
◦ Performance
I/O schedulers:
◦ Deadline (default)
◦ Noop
◦ CFQ
◦ SIO
Toggable FSync
Fixed always ON LEDs bug when used for notifications only
VPN networks support (not tested)
Slightly increased touchkeys sensitivity (from 45 to 35)
Other minor changes and optimizations
Downloads:
version 4.0: kernel-qwerty-cm-10-galaxysl-v4.0.zip: kernel with custom DeviceParts.apk [3], hostap and tiap_drv.ko [5]
clean-qwerty-cm-10-galaxysl.zip: restore zip with dhiru1602's kernel
UPDATE: USB composite is still a bit messed up. Windows can't recognize the phone when RNDIS (USB tethering) is enabled (working fine with Linux).
If you need RNDIS, flash this kernel release or the previous one.
Additional zips:
powerHAL-cm-10-galaxysl.zip: power HAL for boosting the CPU when ondemand is used [4]
libsensor-cm-10-galaxysl.zip: custom libsensor. Read note [1]
Changelog:
Code:
22/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.1...v4.0"]v4.0[/URL]
02/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.0...v3.1"]v3.1[/URL]
01/03/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.1...v3.0"]v3.0[/URL]
12/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.0...v2.1"]v2.1[/URL]
09/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v1.0...v2.0"]v2.0[/URL]
08/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/commits/v1.0"]v1.0[/URL] - Initial release
Notes:
[1] I made it compatible with the prebuilt libsensor included in CyanogenMod, but I'm using my own libsensor and maybe I didn't test this kernel with the stock one for long enough. I hence added my libsensor, just in case. If you want to restore the original libsensor, simply remove /system/lib/hw/sensors.latona.so.
[2] You can modify "samsung-battery" wakelock length through DeviceParts. By default it behaves like the original module. If you see "Android System" or anything else eating your battery with no reasons, increase the delay or restore the default one.
[3] DeviceParts.apk (System Settings > Advanced) is included because of some additional settings useful when this kernel is used. I'm not a Java dev, so it's probably not perfect, but it works quite well. I took pieces of code from other devices (mostly Crespo, Aries and S2). The source code is available, suggestions are more than welcome.
[4] Power HAL will make the CPU jump to a certain frequency (I set 800MHz) whenever Android requires it (when the screen is touched for example). Power HAL will also limit the max freq to 800MHz (my choice, not too fast, not too slow) when the screen is off. You can change the boosting freq from my custom DeviceParts. CPU frequencies changes (See XDA_Bam's thread for more info about variable overclocking) are not expected. If you don't like it, simply remove /system/lib/hw/power.latona.so. Few more lines about power HAL here.
[5] hostap and tiap_drv.ko make WiFi tethering possible using this modified version of android-wifi-tether.
Special thanks to dhiru1602 and XDA_Bam for their awesome work.

Wow. I'll flash it for sure.
Thanks for sharing.
Update:
Flashed and it works just fine. Just changed max freq to 1200.
Deviceparts looks very professional as well.

Hats off to u buddy. Also kernel name is really good buddy. Dont worry about that
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.

Re: [KERNEL][CM10] qwerty [08/02/13]
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app

Re: [KERNEL][CM10] qwerty [08/02/13]
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003

imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Works fine for me. Try wiping cache+dalvik cache.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003
Click to expand...
Click to collapse
Are you using SIRI kernel?

Hetalk said:
Works fine for me. Try wiping cache+dalvik cache.
Are you using SIRI kernel?
Click to expand...
Click to collapse
I am just using the signal fix kernel by loSconosciuto before ...........

^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.

Re: [KERNEL][CM10] qwerty [08/02/13]
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Sent from my GT-I9003 using xda premium

Re: [KERNEL][CM10] qwerty [08/02/13]
Hetalk said:
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.
Click to expand...
Click to collapse
i post here becoz i wanna flash this kernel will try what u say later, thx
Sent from my U9GT2 from moage.com using xda premium

^ You'll need to wait for users to get thru a battery cycle to report battery drain. I did charge my phone to 100% after flashing qwerty .. so will report my experience tomorrow.

Re: [KERNEL][CM10] qwerty [08/02/13]
just flashed this kernel.. on top of my cracker that i am using previously.. no problem on boot.. upgrading apps as usual.. ive noticed the speed, scrolling and such.. its faster than cracker .. the speed of gb is there..gonna test for some time.. thanks.. via slimbean 3.1 A4..
Sent from my GT-I9003 using xda app-developers app

I am pleased thank you very much !!!
Governor smartassV2 and IO Scheduler deadline (reputable boost daily)
Mini CPU 300/1000 is an exellent choice (I guess the hotboot fix)
it's just what I need ^^
Thank you for taking us solicitous

Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?

just added a tab (specific options) available in the parameter menu

vishal24387 said:
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
Click to expand...
Click to collapse
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decisions mostly depend on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
vishal24387 said:
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Click to expand...
Click to collapse
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Click to expand...
Click to collapse
All our kernels based on the sources released by Samsung use a prebuilt module for WiFi. Dhiru tried to use the opensource driver, but it didn't work.
This prebuilt module, taken from our stock ROMs, requires a prebuilt and modified wpa_supplicant which is not completely compatible with Android 4.0+ (Samsung didn't give us the changes required to make the opensource one work). To make things worse there's dhcpcd, we have to use an old version because of the old wpa_supplicant.
In other words: it sucks.
With some access point there are no issues, with others WiFi works, but not so well and with some others nothing works.
EDIT:
Now that I think of that, there are maybe some differences when this kernel is used. I took the prebuilt module from XXLE4 instead of taking it from EDIT2: XXKPM
The warning message I get the first time I turn WiFi (maybe it happens even with the other module, I didn't try it) on suggests me that something was changed in XXLE4, but I don't know if this is a good thing or not.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Click to expand...
Click to collapse
I'm starting to think the problem is CWM. For now only you and spacebar2011 had issues. I will PM you something when I'll have some free time to find the problem. If nothing works, I'll just give you the tars to flash the kernel with ODIN as I did with my signal fix kernel.
@Hetalk
Thanks for trying to help, but he is a peculiar situation. The problem is not the updated blob or a wrong flash, he (and spacebar2011) tried to flash my signal fix kernel several times over a clean CM10 with no success.
rodero95 said:
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Click to expand...
Click to collapse
Dunno, battery life had never been exceptional for me. If you use your phone a lot, any kernel will give you a bad battery life. You can see differences only if you keep your phone most of the time in idle, with mobile data disabled.
wee2wee said:
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
Click to expand...
Click to collapse
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.

loSconosciuto said:
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.
Click to expand...
Click to collapse
Thanks...found it...

loSconosciuto said:
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decision mostly depends on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
Click to expand...
Click to collapse
Thanks for ur simplified explaination This means in order to bring smoothness ondemand will keep most of the time freq at 800 mhz (as per ur settings). But definitely its going to affect battery life as just for a simple touch freq will raise to 800 mhz directly. Anyway overall it depends on user who want battery life or smoothness
I have used ur fixed signal kernel for longer time. That kernel really works very well when we use phone (even with 2g net). But surprisingly in deep sleep mode (means with gsm network on on and 2g net off) then there is very heavy battery drain For me its 25% battery drain in 9hr deep sleep mode. But if we keep our phone phone offline in deep sleep mode then it will drain battery just 4% in 9hr. Strange...!!!
I will monitor tonight also with that signal fix kernel. and final tomorrow I will flash this kernel on clean cm10a4 so that I can compare both ur kernels
EDIT : My doubt was right. Your previous signal fix kernel works really good. Yesterday night tested and I found that lost 3% battery in 8 hrs standby. Means my previous 25% battery loss was not a correct observation. Anyway now I will flash this kernel and tell u the results

Re: [KERNEL][CM10] qwerty [08/02/13]
Well, its obvious that keeping a continuous connection with the network costs battery and that when we are connected with mobile network it will eventually change between signal modes (2g, HSDPA, edge, etc) and that also costs battery.
That's why mobile network use to consume more battery than WiFi or offline.
Sent from my GT-I9003 using xda premium

Really nice Kernel with good combination of battery and performance and many good tweaks
Thank you very much Sir :laugh:

[Kernel][23-12-2014]halaszk-UNIVERSAL5420

Changelog and downloads here:
https://github.com/halaszk/halaszk-UNIVERSAL5420/wiki

Issues and solutions :
https://github.com/halaszk/halaszk-UNIVERSAL5420/issues

https://github.com/halaszk/halaszk-UNIVERSAL5420/blob/master/arch/arm/configs/halaszk_defconfig_N900
I love your setting
Well i'm on the phone so i didn't see something but.. i advise to put row as the main scheduler (best for ssd hardware) and the conservative governor modified with the sampling rate min at 50.000.. the same for the ondemand..
If you need i'll patch those 2 for you.. (i don't know how to use github but i can patch the *.c)
Anyway the kernel seems good.. i'll test it tomorrow
---------- Post added at 04:36 AM ---------- Previous post was at 03:40 AM ----------
http://www.imgur.com/mLVh6cc.png
Works good with correct uv :thumbup::thumbup:

this is the best kernel with so many controls including LED which i was missing coz note 2's led is much brighter than ours
now i can fade in and out
cheers !

I think now I really need to root and install CWM on my phone!!!!!!!!
Features are great man. thanks. keep up the good work

When ever I change the display controls noting happened ..same in charging control when I change the voltage it does not increase

great work best kernel for n900

karthickkatta said:
When ever I change the display controls noting happened ..same in charging control when I change the voltage it does not increase
Click to expand...
Click to collapse
If you enabled "enable register hook and master sequence" in screen tab under synapse this settings works perfectly!
Sometimes charging settings some roms applied after reboot the phone. My phone on Chrisleko Rom V4, and it works perfectly without restartat the phone. (the charge control menu not a voltage settings)

halaszk88 said:
If you enabled "enable register hook and master sequence" in screen tab under synapse this settings works perfectly!
Sometimes charging settings some roms applied after reboot the phone. My phone on Chrisleko Rom V4, and it works perfectly without restartat the phone. (the charge control menu not a voltage settings)
Click to expand...
Click to collapse
Yes it works now ..what about AC main input current how to control it ? Will new features be added ?

synapse not work in screen setting in cpu and io it works i use trickster mod and its work when enabledmaster sequence or register hook

Cortexbrain script should be great. found this piece of information from dorimanx weblog,
This script will manipulate all the system / cpu / battery behavior. Based on chosen EXTWEAKS profile+tweaks and based on SCREEN ON/OFF state.
When User select battery/default profile all tuning will be toward battery save! But user loose performance -20% and get more stable system and more battery left.
When user select performance profile, tuning will be to max performance on screen ON!
When screen OFF all tuning switched to max power saving! as with battery profile, so user gets max performance and max battery save but only on screen OFF.
This script change governors and tuning for them on the fly!
Also switch on/off hotplug CPU core based on screen on/off.
This script reset battery stats when battery is 100% charged.
This script tune Network and System VM settings and ROM settings tuning.
This script changing default MOUNT options and I/O tweaks for all flash disks and ZRAM.
Click to expand...
Click to collapse

Flashed, need a couple of days testing, but at glance that is impressed
Sent from my SM-N900 using Tapatalk

Cortexbrain script functions from Dorimanx SGSII kernel with auto screen on/off module
Click to expand...
Click to collapse
You bring the best from Dorimanx kernel!!!

Synapse can't work ,FC everytime

who can recommend / advise the settings which will increase the battery life?
may be there is any instruction with examples?
thank you in advance!

Coffee
.
Hi halaszk,
Thanks for you work.
I have sent you a coffee over paypal. Confirmation number: 1C413099LN2241531
Keep up your work. Thanks again.

Sview Cover
Hi halaszk,
Everything working properly and I can UV more than other kernels. Stability is perfect.
Features you add are perfect too.
I wanna ask about two thing,
1. My Sview Cover does not work. This was happen on hannry kernel 2.0A before and solved on 3.0A. Also it is working on pekaka kernel.
2. could you put sched_mc control on synapse.
Thanks for your effort and knowledge.

No uci support detected

alleshi said:
No uci support detected
Click to expand...
Click to collapse
After a reboot it worked for me.

First of all thank you halaszk for the best kernel for our note 3. Cheers and keep up the work. Just a little confusion. On set cpu n cpu spy the min frequency is 100mhz (the whole frequency table is different than the one in synapse) I'm a little confused due to this. Can somebody explain?
kadiremrah said:
Hi halaszk,
Everything working properly and I can UV more than other kernels. Stability is perfect.
Features you add are perfect too.
I wanna ask about two thing,
1. My Sview Cover does not work. This was happen on hannry kernel 2.0A before and solved on 3.0A. Also it is working on pekaka kernel.
2. could you put sched_mc control on synapse.
Thanks for your effort and knowledge.
Click to expand...
Click to collapse
Can you post your voltages pls. Thank you

Screen wake issue - battery pull

Hi guys
I know this issue has been mention a bit, and I've searched through countless threads but I find the search system on the site a little counter intuitive, like forum searches will only bring up the thread, not the actual key word references and I have to search again within the threads to yield results, but I'd like to clarify a few things.
I'm running Cm11 nightlies on the phantom kernel and I have the screen wake issue. It takes multiple attempts to wake up the screen. OK.
I understand this is a problem with Kitkat roms for our device. However, my case is that there is a 50-50 chance that the screen doesn't wake up at all and I have to pull the battery. This makes any rom almost unusable for me as 1 out of 2 times I have to pull the battery to access the phone, Music continues to play, and I can skip tracks or play or pause, and even take photos, which means that the phone unlocks only the screen doesn't light up. If I hold down the power button, I can feel the phone vibrate to indicate the shutdown menu and sometimes I can blindly reboot or turn off the phone by tapping the screen roughly where the menus would be, so the touch is working.
Roms have been reinstalled and dalvik wiped etc but no improvement
I'd like to know if there's something I've done wrong to have so much poor luck. I don;t mind waiting for the screen to light up, or even a few tries, I'm aware of the unstable nature of nightly roms, and I am happy to use it and contribute usage stats to help further development, but not being able to get the phone on is a massive problem, especially when receiving a call
If anyone has any tips, I;d love them to let me know so I can add here as a one stop thread to general KK problems and work-arounds.
Pr m,aybe it's just my phone
Current mods
Xposed framework modules
greenify
kk bugs fixer (currently disable as seems to make no change)
minminguard
no lock home
Xposed gel settings.
No crazy overclocks or aggressive governers (tested with ondemand, intelliactive no difference, but great battery)
General rom experience apart from this - Excellent battery and very snappy, only a little skipping with audio (even with cache increased to 4010)
Cheers people!

try another kk rom
i did not use cm11 b,coz i had problems with the low reciever volume
tryout carbon rom or vanir aosp
they are too good

SOLVED
OK, thanks for the suggestions, actually I had the same issue on all roms that I tried.
The fix was the following, I disabled the NO LOCK HOME Xposed module and now all is back to normal.
i think there was an issue with it auto unlocking the screen on wifi or cel tower that caused the lockscreen to crash from time to time or get stuck. All is working like a dream now.
It~s a shame really, here in Brazilo with the rise of the Iphone and the high robbery rate, it´s quite common now for thieves to stick their gun in your face and demand your password or for you to unlock;disable the password during the robbery so that they can reset the apple acount or phone for resale. With nolock home I could save the cel towers near my home and work (for my walks to and from the subway) so that in case of a robbery, the phone just opens up and shows its unlocked, and then I can remotely wipe it later without giving up account details. Anyway, anybody else with this problem, thats the source of the Issue

simples tips and tricks to make this device awesome right now

with stuff we got :angel:
Here are mines, mostly based on personnal/subjective stuff, but I spent quite some time digging this out for me so let's share.
Whats the best custom ROM LOLOLOL ?
AICP might be https://forum.xda-developers.com/lenovo-p2/development/7-1-1-aicp-12-1-n-7-1-1rxx-lenovo-p2-t3576216
Provided you want those extra shiny custom things built over Lineage.
This is to my knowledge the only custom ROM here receiving OTA updates (correct me if I'm wrong). Nightly updates.
RR feels more polished, but no updates since second release and issues updating Magisk. (Well some had, other didn't, I know I did).
On a side note RR can go MicroG way using those scripts for more privacy and battery related interests https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
Haven't tried with AICP yet.
This is a subject on his own, so tell me if you're interested. Otherwise go OpenGapps ARM64/7.1 http://opengapps.org/ (I suggest Pico then you install everything else you might need from google on the playstore).
Mandatory custom Rom stuff
1- No Volte.
2- No Volte, at least for a long long time.
3- Stop asking.
4- No fingerprint back button. 3rd party app might do the trick, but everyone should use the mighty copied but never surpassed pie https://forum.xda-developers.com/showthread.php?t=1330150 ... And never need anything else again to control their phone.
4- If you experience idle battery drain reported as usb related by good monitor apps like Better Battery Stats, just remember to plug and unplug AC after each reboot. Not too tedious.
5- Use this mehod to get LED notification back https://forum.xda-developers.com/lenovo-p2/themes/lenovo-p2-rooted-custom-led-t3589859
-This got people confused: LED codes are to be entered in each Notification events, and it doens't matter if the main LED controller indicate it's grey, it wont be cause you're using the other one.
-Light Flow is acually awesome and doesn't drain any noticeable amount of juice contrary to what I red.
-If you want to get rid of the perma notif (works as well for LMT pie), don't use legacy version, just block the notification from android by longpressing on them. I will then work without trouble. Don't battery optimize it though.
6- Fast charge should works as expected, although not notified on lockscreen (but the timer will give you a hint).
7- "Battery life is not as good as it is on stock". I haven't made extensive tests being allergic to stock looks and lack of custom-ability, but I can tell you battery life on Aicp is STELLAR with a few tricks:
- battery optimize google play service. Oh yes ! It will works as usual.
Then choose carefully what apps absolutly needs to be left alone on that matter, they are few.
No need for greenify anything anymore unless you have some really "rogue" app (and in that case they should be disinstalled anyway).
- perma-run on data saving mode even in wifi (add your usual wifi at the bottom of the page).
You don't need anyone phoning home on your back anyway, only authorize the apps that absolutly can't do without internet.
Along those one are google contacts and agenda sync (not the apps themselves, another satellites ones). If you use google sync that is to say.
- Disable this 90% of your apps that don't need to run in background or at boot into the advanced mode of the privacy menu.
- Bonus round: manually sync everything including markets, disable all those apps that want to notify or check about things you don't care, get a nice black substratum theme like Flux, maybe make use of the suspend action function (incuded in Aicp and RR) that switch data and gps when screen is off.
Battery might even looks like it recharges itself now what a phone on that matter.
On the contrary speaking about where it falls short:
Sound sucks
Well, it's not that good, not Audiophile one bit. As a music addict I felt really bothered. Highly subjective matter, but after trying many many things I finally got my butt kicked trough my hear with this combination only: Ahrion Dolby https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342 + Ainur Audio https://forum.xda-developers.com/android/software/soundmod-ainur-audio-t3450516
Procedure to install them both was a bit tricky:
-distinstalling Dolby with provided .zip
-installing Sauron (disinstall/install as OP says)
-disinstall Audiomod in Magisk
-re-install Dolby. Wich re-installs Audiomod.
Then sonic bliss !
More to come.

duck from space said:
With stuff we got :angel:
Here are mines, based on personnal/suggestive stuff, but I spent quite some time digging this out for me so let's share.
Whats the best custom ROM LOLOLOL ?
AICP might be https://forum.xda-developers.com/lenovo-p2/development/7-1-1-aicp-12-1-n-7-1-1rxx-lenovo-p2-t3576216
Provided you want those extra shiny custom things built over Lineage.
This is to my knowledge the only custom ROM here receiving OTA updates (correct if wrong I know you will). Nightly updates.
RR feels more polished, but no updates since second release and issues updating Magisk. (Well some had, other didn't, I know I did).
On a side note RR can go MicroG way using those scripts for more privacy and battery related interests https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
Haven't tried with AICP yet.
This is a subject on his own, so tell me if you're interested. Otherwise go OpenGapps ARM64/7.1 http://opengapps.org/ (I suggest Pico then you install everything else you might need from google on the playstore).
Mandatory custom Rom stuff
1- No Volte.
2- No Volte, at least for a long long time.
3- Stop asking.
4- No fingerprint back button. 3rd party app might do the trick, but everyone should use the mighty copied but never surpassed pie https://forum.xda-developers.com/showthread.php?t=1330150 ... And never need anything else again to control their phone.
4- If you experience idle battery drain reported as usb related by good monitor apps like Better Battery Stats, just remember to plug and unplug AC after each reboot. Not to tedious.
5- Use this mehod to get LED notification back https://forum.xda-developers.com/lenovo-p2/themes/lenovo-p2-rooted-custom-led-t3589859
-This got people confused: LED codes are to be entered in each Notification events, and it doens't matter if the main LED controller indicate it's grey, it wont be cause you're using the other one.
-Light Flow is acually awesome and doesn't drain any noticeable amount of juice contrary to what I red.
-If you want to get rid of the perma notif (works as well for LMT pie), don't use legacy version, just block the notification from android by longpressing on them. I will then work without trouble. Don't battery optimize it though.
6- Fast charge should works as expected, although not notified on lockscreen (but the timer will give you a hint).
7- "Battery life is not as good as it is on stock". I haven't made extensive tests being allergic to stock looks and lack of custom-ability, but I can tell you battery life on Aicp is STELLAR with a few tricks:
- battery optimize google play service. Oh yes ! It will works as usual.
Then choose carefully what apps absolutly needs to be left alone on that matter, they are few.
No need for greenify anything anymore unless you have some really "rogue" app (and in that case they should be disinstalled anyway).
- perma-run on data saving mode even in wifi (add your usual wifi at the bottom of the page).
You don't need anyone phoning home on your back anyway, only authorize the apps that absolutly can't do without internet.
Along those one are google contacts and agenda sync (not the apps themselves, another satellites ones). If you use google sync that is to say.
- Disable this 90% of your apps that don't need to run in background or at boot into the advanced mode of the privacy menu.
- Bonus round: manually sync everything including markets, disable all those apps that want to notify or check about things you don't care, get a nice black substratum theme like Flux, maybe make use of the suspend action function (incuded in Aicp and RR) that switch data and gps when screen is off.
Battery might even looks like it recharges itself now what a phone on that matter.
On the contrary speaking about where it falls short:
Sound sucks
Well, it's not that good, not Audiophile one bit. As a music addict I felt really bothered. Highly subjective matter, but after trying many many things I finally got my butt kicked trough my hear with this combination only: Ahrion Dolby https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342 + Ainur Audio https://forum.xda-developers.com/android/software/soundmod-ainur-audio-t3450516
Procedure to install them both was a bit tricky:
-distinstalling Dolby with provided .zip
-installing Sauron (disinstall/install as OP says)
-disinstall Audiomod in Magisk
-re-install Dolby. Wich re-installs Audiomod.
More to come.
Click to expand...
Click to collapse
Quick question what's micro g?

MicroG allows you to use Gapps without Playservices, thus gaining more control over your battery and privacy while having a still fully functionning phone.

Btw RR was updated 2 days back.
Thanks for all the detailed info.

On the subject of
Camera sucks
I'd very like to hear if someone has dug the most optimal app and settings for this phone.
I'm not really into photo and the few pic I've taken outside looks perfectly fine to my noob eyes.
But on a few occasion I like to storm photos on something and that's better be ok shots :good:

- perma-run on data saving mode even in wifi (add your usual wifi at the bottom of the page).
-You don't need anyone phoning home on your back anyway, only authorize the apps that absolutly can't do without internet.
-maybe make use of the suspend action function (incuded in Aicp and RR) that switch data and gps when screen is off.
Can't find suspended action
I'm not able to understand above mentioned things please explain a those if possible.
I'm in aicp latest build.
Sent from my Lenovo P2 using Tapatalk

Data save mode is an android feature found into the data consumption menu.
Suspend action is a custom rom feature found in the custom rom options of RR and AICP. RR has a tile for it, AICP doesn't.

This Custom Ron is great, way better than i expected.

[ROM][UNOFFICIAL][12L][N7100][Samsung Galaxy Note 2][LineageOS 19.1][BETA]

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version for the Samsung Galaxy Note 2 on LineageOS 19.1.
At first I want to thank @rINanDO, @ChronoMonochrome for all your work which was reused here and helped a lot.
Spoiler: Links
TWRP
ROM Android-Filehost
ROM Mega
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
GPS
Wifi
USB
Video playback (HW/SW)
OTA Updates
Tethering via USB, WIFI and Bluetooth
Sensors
RIL
Spoiler: Whats not working
NFC
Encryption
Maybe random reboots
SD card maybe can't formated as internal memory
Maybe more
I would recommend to use microG instead of gapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Spoiler: Changelog
26.01.2022
08.03.2022
17.03.2022
25.03.2022
04.04.2022
19.04.2022
03.05.2022
15.06.2022
08.07.2022
22.09.2022
25.01.2023
Spoiler: How to install it?
Instructions
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Telegramm group:
Samsung Galaxy Note II testing group
t.me
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
XDA:DevDB Information
[ROM][12.x][N7100][BETA] LineageOS 19.1, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.0
Based On: LineageOS
Version Information
Status: Beta
Created 2021-12-30
Last Updated 2023-01-25

Alternative download link for the initial version:
File on MEGA
mega.nz

Originally posted in [ROM][UNOFFICIAL][11.0][N7100][Samsung Galaxy Note 2][LineageOS 18.1][ALPHA][TREBLELIZED]:
I just flashed the newly Android 12 LineageOS 19 build this morning.
It's currently a bit early to share my experience yet since I need some more time, but I already like to share my first impression.
First of all, I was surprised that I could just do a dirty flash over your current 18.1 dec build without any problems.
I did not perform a clean flash because I couldn't backup my Session messages, normally I always perform clean flashes.
I used TWPR 3.5.2 custom recovery to flash this ROM and only wiped Cache and Dalvik Cache/ART partition.
Everything went smooth. It didn't take too long for the first boot either.
Right after the first boot, just when it was booted, the phone rebooted.
After this reboot, I didn't encounter any random reboots yet.
Everything seems working smooth and snappy at the moment.
I can confirm that Magisk 23 is still working on this ROM. You just need to re-flash it after the first boot.
The only annoying thing I discovered is a blinking LED issue and the battery that last less longer, but that's maybe linked to the blinking LED issue.
Something I immediately noticed is that my notification LED is actually red now while charging and green when it hits 100%.
In previous 18.1 build, the LED always got a weird yellowish colour while charging.
Another thing that caught my eye was "Google Play System update" in settings.
I don't understands why it's there since it's supposed to be a degoogled ROM.
Google Play System updates is a part of the Google Play Services ecosystem.
I didn't install any GAPPS and this ROM didn't came with GAPPS pre installed.
Spoiler: What I can confirm is working
- It (re)boots correctly
- Able to receive and sending sms messages and phone calls (didn't try SIM unlock yet. I used the workaround that is mentioned in the main post)
- Camera's
- Wi-Fi (both, 2.4 GHz and 5GHz)
- Video's (YouTube in browser)
- Sensors, except compass (phone rotates correctly)
- Charge correctly to 100%
- S-pen (just as a regular styles, no button functionality)
Spoiler: What is not working + bugs
- An annoying blinking LED issue.
I never experience this before on any ROM.
Can be a coincidence, but after the battery drops below 75%, the notification LED is constantly blinking red, even when the screen is on.
I already tried to literary turn off all notifications options. I even disabled blinking LED option, but it still keeps blinking, even after a reboot. It only disappears after fully charging the phone but will come back in time.
I didn't find a way to fix this.
- Android 12 theme engine seems to be broken.
Some things like buttons (like emergency call button on lockscreen), text (search apps in launcher) and backgrounds in notifications icons in notification panel are still LineageOS teal.
Switching a wallpaper with different colours, but it doesn't change the theme colour of the device. Buttons, lockscreen clock etc. are still light blue. I try to add some screenshots to highlight this problem.
Also, the options to change the icon shape seems to be gone, even in developer settings.
Everything turned into circles after the update. Can't change it.
- USB (can't connect to pc (MTP))
- Extended screenshot beyond your screen
- There was a weird issue that my device is stuck at Samsung Galaxy II screen when turning on the device (not the LineageOS boot screen). I only had this once so can't describe how to reproduce it yet.
I just turned off my device in the power setting inside the ROM. The next time I turned on the device, it was stuck on that screen for 10 minutes. It was fixed by simply holding the power button for a while to turn off the phone.
After doing this, the phone rebooted normally again. I didn't got this issue again.
Besides the blinking LED issue, I had a very good first impression.
I really don't mind that some gimmick features are not working.
I only have this ROM for a few hours, so please keep in mind that I need more time for extensive and more in-depth testing.
Maybe there are some critical problems that I still need to discover.
I just wanted to give a quick update.
@html6405
If there are some specific things you like to try or things I need to keep an eye on, please let me know.

A big thank you to html6405 for this rom! Almost everything seems to work good.
The only thing i am missing is wake by proximity sensor. I use the app Waveup from F-droid for this. I know from trying other roms, that this is an unreliable feature. The sensor hardware is working, that much i know.
When using Lineageos 16, this is a built in feature in the rom, but it deactivates after every reboot. I have to manually turn it off and on every time to get it to work.
No big issue. Just glad to have latest Android on this device. I hope you get more appreciation from this than what you got from your Los 18.1 thread.
Let me know if you want feedback of any kind.
Happy new year!
​

It does work! I couldn't resist trying the future LOS19.
The overall impression is quite good, as the system seems to be more stable than the previous LOS18.1 for this phone. Still, the development options screen hanged a couple of times. At some point the system crashed and kept rebooting into recovery - fixed by erasing data partition. GPS works, although not well enough. The compass doesn't work in GPStest, but works in Compass app from Fdroid. I tried web browsing and viewing HD videos with Brave browser - very smooth experience. In order to access files on the phone I set up default USB mode in developer settings to files.
Two preinstalled applications are unsafe, contain trackers: camera and via. These had to be removed. Open Camera from Fdroid is installed - it works. The system web browser is preconfigured to ring Google; one may want to review its settings.
Installed Insular app (a sandbox made of the work profile) from Fdroid. The work profile works, but looses its filesystem after disabling and enabling it again. To bring the filesystem back reboot is required.
Phone encryption doesn't work, sadly. This is the same as with many previous custom ROMs for this phone.
A strange horizontal bar is seen at the bottom of the screen (nav bar home button??). Disable "Navigation hint" to get rid of it.
All together, it's an excellent result for the first attempt on LOS19. Looking forward to further releases!
Happy New Year everyone! Thank you html6405 for such an exciting present!

porcino said:
GPS works remarkably well, better than in the previous ROM, but compass doesn't work. I tried web browsing and viewing HD videos with Brave browser - very smooth experience. In order to access files on the phone I set up default USB mode in developer settings to files.
Click to expand...
Click to collapse
This are really great news, could some one else confirm that GPS is working?
I cant test it by my own...
If it's working fine, I will add it to the working list.

GPS seems to work better with "Force full GNSS Measurements" and "Use GNSS APIs" disabled in GPSTest. I also disabled "Force full GNSS Measurements" in "Developer options". From inside a room it locks on 3-5 satellites, although sometimes after a delay.
With GNSS it finds also Russian and Chinese satellites, but uses only the US constellation.
GPS performance, of course, is not as impressive as in new Samsungs, which lock on several constellations at the same time.
----------------
Added later... Still, GPS is not working well enough in this first release. It finds satellites slower than my ancient HTC DHD (ace) running cm13. Then it locks and in a moment loses the lock. I'll look into this in more detail...

porcino said:
GPS seems to work better with "Force full GNSS Measurements" and "Use GNSS APIs" disabled in GPSTest. I also disabled "Force full GNSS Measurements" in "Developer options". From inside a room it locks on 3-5 satellites, although sometimes after a delay.
With GNSS it finds also Russian and Chinese satellites, but uses only the US constellation.
GPS performance, of course, is not as impressive as in new Samsungs, which lock on several constellations at the same time.
Click to expand...
Click to collapse
Great, hopefully some one else can confirm this , you're the only person so far.

Yes indeed - working GPS very important, and needs to be confirmed by multiple sources.
But kudos to the developer for making progress on this.

hello, dear! tell me, what is the battery life? I use rr 5.8.5, the battery lasts for a day of average use. I tried to install lineage 16 - the battery was enough for several hours( now I would really like to switch to this rom, but everything depends on the battery life. thank you for the answers!

alexfire_s said:
hello, dear! tell me, what is the battery life? I use rr 5.8.5, the battery lasts for a day of average use. I tried to install lineage 16 - the battery was enough for several hours( now I would really like to switch to this rom, but everything depends on the battery life. thank you for the answers!
Click to expand...
Click to collapse
Just tried: flight mode, screen off, location off, BT and NFC off, no GApps, just sitting on the desk starting with fully charged. After half an hour the estimated battery life is 10h, 6m. Not great. The battery felt fine last night for a couple of hours of experimenting with secure messengers, then fully charged, then down to 2% by morning. I'll try uninstalling the messengers in case they are draining the battery - wait for an update.
I could not find a way of disabling the clock on the sleeping screen. It disappears after a while, but the screen power consumption is suspect.
Well, this is the first alpha release, the things with power consumption might improve soon.
----------------
Update: I found a way to disable the clock on the sleep screen and the battery life increased to 23 hours, mobile network 1% (still the flight mode is on), phone idle 1%.
The method to disable the display was to press the power button while the notification panel is open...- perhaps another bug.

porcino said:
Well, this is the first alpha release, the things with power consumption might improve soon.
Click to expand...
Click to collapse
The always on display will be turned off in the next build, this will improve the power consumption a lot.

You should be able to disable the always on display in the quick settings (AOD) and give your test a retry .

html6405 said:
You should be able to disable the always on display in the quick settings (AOD) and give your test a retry .
Click to expand...
Click to collapse
Just tried the AOD button: first enabled it and then disabled again... - it worked! Not sure, though, whether any of my previous attempts to modify the settings via adb played any role. I'll repeat timing of the battery with this setting. Thanks.

porcino said:
Just tried the AOD button: first enabled it and then disabled again... - it worked! Not sure, though, whether any of my previous attempts to modify the settings via adb played any role. I'll repeat timing of the battery with this setting. Thanks.
Click to expand...
Click to collapse
Theoretically it should be enabled by default (what I will change in the next build for sure), but anyway, it's good if you can turn it off yet.

Great news, another person confirmed with a video that GPS is working ,
so I will add it to the working list.
Nice to see, that this worked out nearly blindly, because I have no testing opportunities...

With AOD button on then off the battery life is estimated as "more than 2 days left" (flight mode, idle). Let's wait for a little longer...
-------------------
Update: after 11h it predicts "5 days left" and counting! Very good! The graph shows slightly increased power consumption in the first hour, and then it goes almost horizontal. I think it will be more than 5 days at idle, perhaps twice as many.
-------------------
Further update: after 1 day 5 hours it says 9 days left. The way the graph in Battery Usage page goes makes me think that it will last about 20 days if left idle. I don't know what caused the quick discharge in the first hour; after that the graph is a straight line pointing beyond 20 days mark...
-------------------
Yet another update: 28 days predicted after 23 hours of idling. Very good! This is with all wireless interfaces off, Always On Display off and NavBar off.
For reference - Note 4 with cdDroid 9 under similar conditions reports 45 days.

I checked this rom. the sd card is not mounted as internal memory, the phone falls into the bootloop before the lock screen, after which the bootloop again. wipe data or format does not help
-----------------
udp. the backlight of the hardware buttons does not work, although it is enabled in the settings
-----------------
upd. the indication of charge percentages in the status bar does not work when the display is selected with a circle inside the icon

alexfire_s said:
I checked this rom. the sd card is not mounted as internal memory, the phone falls into the bootloop before the lock screen, after which the bootloop again. wipe data or format does not help
Click to expand...
Click to collapse
Simply remove the sdcard.
alexfire_s said:
udp. the backlight of the hardware buttons does not work, although it is enabled in the settings
Click to expand...
Click to collapse
You're right, this will come later from lineageos.
alexfire_s said:
upd. the indication of charge percentages in the status bar does not work when the display is selected with a circle inside the icon
Click to expand...
Click to collapse
Ok, this will also be fixed from the linageos side.

html6405 said:
Simply remove the sdcard.
You're right, this will come later from lineageos.
Ok, this will also be fixed from the linageos side.
Click to expand...
Click to collapse
now I use the 7100 as the main device, I actively use it, I can quickly share bugs if I find them. is it possible to contact you directly without communicating on the formum? do you use a group of testers in telegram?