Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.
I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).
Help??? How to fix gps on this Rom plzz
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.
Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.
@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?
p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.
Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...
Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not
It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.
moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).
Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?
Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run
One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!
..
Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers
Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU
Related
FOR 32A, RADIO 6.35 and SPL 1.76
this port only have very little modification from original official ROM, some kernel driver tweaks, camera libs replacement, our bt firmware, sensors files and root.
first boot could be not very smooth. screen may go blank, if you would encounter this problem, just wait for a while, and press some keys. when you make all your settings done, a reboot is highly recommended. I have used it daily now.
download:
latest update [Jun 26]::
OC: http://forum.xda-developers.com/attachment.php?attachmentid=349885&d=1277499752
non-OC: http://forum.xda-developers.com/attachment.php?attachmentid=350638&d=1277631885 , under testing, plz report bugs.
changes:
HTC's battery driver
a new driver extension to support default USB netshare *
a newer sanpei helper which is reimplement **
non-OC version: screen on 528/352, screen off 240/176 ***
OC version: screen on 576/384, screen off 245/176 (4.0 in Linpack with JIT)
other fixes, many error reports in aosp kernel (which version > 2.6.29) have gone, we have a clean dmesg now
ROM itself:
apply update after you flash the ROM:
http://www.4shared.com/file/XHlI-Kdl/3pei_hero_21_alpha.html
mirror: http://www.multiupload.com/RRWFEYLPP1 , by malachaskos, thank you
wipe and flash in recovery, and you should delete the generated files (by android) in your sd card.
please make sure that you have installed driver properly. a little more details: http://forum.xda-developers.com/showpost.php?p=6180261&postcount=986
addition:
for JIT, download this: http://forum.xda-developers.com/attachment.php?attachmentid=345213&stc=1&d=1276842897
you have to set your Home Wallpaper and Lockscreen Wallpaper to something on sdcard before the first boot with JIT enabled, (and you can set them back after that: I have tried other HTC wallpapers except default). the workaround is found by klothius, thx .
if you encountered any trouble, and want it disabled, flash this: http://forum.xda-developers.com/attachment.php?attachmentid=345214&stc=1&d=1276842897
for Gallery3D, download this version: http://forum.xda-developers.com/attachment.php?attachmentid=338391&d=1275828997 , it could work with HTC Camera app in most HTC's ROM.
known issues and workaround:
keyboard light and some other led features : flash update plz
gps may need to boot with gps setting on, or you could try capychimp's gps files
official USB netsharing: flash update plz
if you find infinite logs about database queries which are generated by bt components, what I know is a reboot, or kill the bluetooth process
APN list shows nothing (unless your mobile operator is Chungwa in Taiwan), plz manually add your APN
* it could work under windows, but you must enable netshare in settings, and not in notification area. and you must disable netshare in settings if you want to use DiskDrive.
plz don't turn mobile network setting off when wifi is on. HTC's software will disable netsharing and uninstall the driver when you turn off mobile network.
** dev could set the button led timeout now.
just setprop sanpei.buttonlight.delay 20 (in sec) when phone is running, or set it in build.prop. plz report any issues.
*** I don't test the non-OC version myself yet, if you encountered any problem plz tell me, since it have lower frequency when you don't touch the phone.
and if the screen doesn't turn on during boot with OC version, plz press red button to close screen then press any other button to active the screen.
this issues happened once when first time I used this ROM after it was ported, though we don't have a kernel OCed that time. so I had said "first boot could be not very smooth" before. now I found that with higher CPU freq, it will happen more frequently.
so I won't support higher frequency at current. they are not so stable as I considered before. maybe you think that we could boot it with a lower frequency then use higher after boot. but I think if it have troubles when booting, it will have more troubles in heavily usage.
old changes:
some new commits to aosp kernel are included
qdsp driver changed to htc 2.6.29 version with some hacks
other little tweaks, not very important
for developers, many modules are included, you could check the modules folder. but I don't enable things like compcache by default. OC is not included, my phone is heated and I don't want to take a risk before I could have time to verify it carefully.
HTC Sync will work with with version 2.0.25, you can find it here (thank paultoan): http://www.htc.com/us/support/magic-rogers/downloads/ .
other pure ports:
you can find them here: http://forum.xda-developers.com/showthread.php?t=642125 .
legend port is a bit slow, but it have more features: the new way of select text、copy、wiki、translate and dictionary, etc.eris port may be faster then this one, and has been tested for a long time, but with old looks.
could someone test for us, if the new kernel binary and boot.img (in update.zip) could work with legend/eris ports? then we could use it to upgrade these ports too.
sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？
wuguohui109 said:
sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？
Click to expand...
Click to collapse
是。在这最好说英文，不然版主说不定对咱们有意见了...
yes, please write in English here, otherwise moderator may have some thoughts...
ok，Download now，thanks，haha
Can You check what languages does it have?
i think both “繁体中文&english”，thats all
sanpei how about rc e100 ? does it work?
Welcome back Sanpei!
Great thanks to sanpei
thanks
Bug ：
Footprints cam Preview no work (photo OK after shooting)
edit---
First Preview rotating, right and bottom Flicker
Second Preview rotating
looking forward to a more stable version
Nice to see you back sanpei.
Would there be any point in trying to throw your new kernel build into one of the older roms (like the legend or eris)?
@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom
account1 said:
@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom
Click to expand...
Click to collapse
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.
sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job
sanpei said:
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.
Click to expand...
Click to collapse
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here
Re: [ROM][6.35] a very pure HERO 2.1, new look and eris ...
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App
helderp said:
sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job
Click to expand...
Click to collapse
.33 is a experimental project by Google, and our device won't get benefits from the increased digit. I will only work on kernels which will be chosen by Google and other manufacturers. and sadly, for some nonsense reason, I and some people couldn't work together.
account1 said:
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here
Click to expand...
Click to collapse
i am really sorry for that. when I was fixing the battery drains, I don't know much about the right behaviors that bt features should have. so I just leave the prevent-sleep mechanism there because I think it is necessary.
and now I don't have enough time as before. but from you and others, I know what the right behaviors are. I will try to fix it in next release, for people who use bt heavily.
Bladyle said:
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
yes (we should make more things could be controlled by users in the long run), but not now.
we still have some issues that are important to other users, though personally, I don't use those features heavily.
my order:
1. lights in Sense ROM for other devices and battery drains when bt is on
2. android 2.2 or big improvements in android 2.2 (port them to daily usable ROM)
3. default USB netsharing, netsharing under windows and other features like this
4. other hardware supports and features like CPU freq control.
5. some hidden bugs in aosp sources or htc drivers we used (though they don't affect anything in most cases)
hope I could get enough time end of this month and next month, then I could repair/add one or two of them.
I only referenced the .33 kernel since that's what's used on cyanogen 5 series mod, and if it could be adapted to the new radio it would be a good way for us to have CM5 with the modifications cyanogen and otheres sometimes do to the kernel. Just my 2 cents
Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food
Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file
You sir are an absolute saint
Thanks so so much
5 STARS!
very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks
How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance
cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod
i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply
Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do
can't wait and i'll try it now
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it
cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...
cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks
thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..
PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.
ROM:
http://www.mediafire.com/download/wkzcatpp7az4r5f/LS-KK-v3.2-2014-10-17-ovation.zip
MD5:
http://www.mediafire.com/download/piwirf8ee421dqv/LS-KK-v3.2-2014-10-17-ovation.zip.md5sum
A shoutout and thanks goes out to Rhyang for his help with the Slimkat rom, (to which this is somewhat similar).
Compiled with Sabermod toolchains. 4.8 for the rom and 4.7.4 for the kernel.
O3 optimized.
I made an attempt to fix 'OK Google'. Dunno if it's working or not (haven't tested). If it's still broken then it will be in the board files and will be a bear to try and find....
Dunno, it seems to work fairly well (ALMOST as good as Cyanogenmod 10.1 ) I kinda like it in a way (except it's KitKat).
I'll try and upload some source later. My internet connection has been giving me problems lately (took four hours or so to upload this). Even with source this is somewhat difficult to compile anyways (I fought with it some).
Cheers!
Great. I'll download now and try it out today :good::good:
Oh man I love LiquidSmooth! I am using it on my phone and have never looked back.
I guess I will have to give this a try. Thanks a lot for this. Is it also running on your yellow kernel or something different?
Which Gapps file is used with the rom please?
Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.
Things are running well. OK Google doors not appear to work too well
Jon Lee said:
Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.
Click to expand...
Click to collapse
Hey Jon, thanks for yet another new rom. :good: Looking pretty cool so far but as already mentioned, "Ok Google" is not working properly. I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder. I hated to lose the yellow kernel as I feel that it has better performance than stock CM11 but I love using OK Google. Btw, I did the same with your Slim rom with similar positive results.
Also, I see in the build prop that the density is set to 320DPI instead of the standard 240. I happen to prefer 320 but I would think that the masses might want the standard density and would be wondering why their desktop looks so big.
Anyway, thanks again for your contributions. It's appreciated.
Mike T
Ooh, nice!
Wow, is this fast!
So many ROMs, so little time.
I've been using CM 11 nightlies for a couple months now and didn't have many complaints. The usual CM 11 screen flicker problem when charging, some screen black outs (and crashes) on a certain screen in one of my aviation apps. That was about it. CM 11 was fairly fast and incrementally getting better all the time.
CM 11 doesn't have zRAM built in (yet), so I got a lot of app restarts when switching between my high memory aviation moving maps and other apps. But we're trying an experimental zRAM build that's helping with the HD+'s limited RAM.
But then I got a wild hair and decided to look around in the HD forum to see if perhaps Jon had an OC kernel for CM 11. Then I found his build of Liquidsmooth for the HD+. I didn't want to spend a half day wiping and installing a completely different ROM. But I'm glad I did. Wow.
I don't know if it's the overclocking or the other tweaks or all the above, but my AnTuTu score jumped from 17300 to 19100! Thanks, Jon!
(Hotplug governor seems to work best for me in both LS and CM 11. Too early to tell, but battery life doesn't seem any worse in LS.)
I assume that LS does not force the CPU to 100% when running AnTuTu, as CM 11 does. So the 19100 is probably a realistic reflection of performance.
(I haven't experimented with the I/O scheduler yet. I left it set at fiops for now. (Supposedly best for flash memory. Heretofore I've always used Deadline.) I lowered the SD cache to 512, which I found worked best in CM 11. (Using SD Booster to make that change.) FWIW, I enabled the GPU Acceleration and Super Tweaks in LS. )
[FWIW, the word "compiler" is misspelled (twice) in the "Just in Time Complier [sic]" setting.]
I'm happy to report that the screen flickering/crashes are gone when on that special page in my aviation moving map that always flickered - and sometimes crashed - in CM 11. (Requiring that I disabled HW overlays in Developer Options in CM11.) And since I set the "Low Memory Killer" to "Light" in LS, it doesn't kill my apps as aggressively as CM 11 did. (Not apples and oranges, because I was running ART in CM 11, whereas LS implies you shouldn't even try ART.) LS should be even better with zRAM. (And the boot animation is better than the frowning, scary CM alien face. )
(Speaking of zRAM, I noticed that someone in the Slimkat forum is running zRAM on Slimkat. I read here that Slim and LS are kinda the same. Is there a way to turn zRAM on it LS?)
I'd be curious to know what the major differences are between LiquidSmooth and Slimkat. Since Jon says LS is "similar" to Slimkat, why does LS exist?
Not much I could find on the web about it. I looked at the Slim home page. It's main advantage seems to be fancy interface stuff. (Although LS has PIE too.) Kinda like a toned down version of PAC? But the LS home page is silent about what makes it better/different.
Like I need to spend another half day wiping and flashing can customizing another ROM. (Titanium Backup is supposed to save data/settings. If it does, it doesn't seem to work for me. I have to reset the Settings on my apps when I restore from Titanium.)
---------- Post added at 10:34 AM ---------- Previous post was at 10:21 AM ----------
Every trying for that last bit of performance, some questions:
Q: On zip align apps on boot. Should I expect a toast or a notification if an app needed to be zip aligned?
Q: In CM 11, there's a Developer's Option to kill an app with a long press of the Back button. (Seems to be different from swiping "closed" in Recents, in that it completely shuts down the app.) Is there a similar trick in LS?
Q: I updated the host file for disable ads. I got a message that it worked, 0/4. Zero out of Four? That doesn't sound right. Is it?
Q: In CM's Launcher settings, you can disable transitions, stop scrolling wallpaper, etc. But I can't find a way to disable transitions - especially in the App drawer - in LS. (I see ways to change the transitions, but none of the options have "None.") Where are they or what's the trick to kill them?
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?
PMikeP said:
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?
Click to expand...
Click to collapse
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
I like Slim because it's minimalist -- no bloated theme engine and its associated bugs. That said, their drivers tend to be a little more out of date than CM. The framework source is also slightly different. This makes sharing code between the two a PIA sometimes. I have no familiarity with LS, so I'm not sure how applicable these comments are to it.
Looks like you've been busy Jon
rhyang said:
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
Click to expand...
Click to collapse
Thanks. I found the pinch gesture serendipitously while trying to swipe away a running app in Recents. Still, it's problematic trying to get it to 'close all' all the time. I went back to stock Recents for now. (Favorites implementation in LS Recents might be nice, as they've implemented in Slim, but I haven't figured out how to invoke it in LS if it's there.)
Here's the device and vendor source as promised:
http://www.mediafire.com/download/z3llb4mauxo8m16/liquidsmooth.tar.gz
Let me know if you need help or any other source to build.
I kept this one very much "original"/plain, meaning I didn't add the zram script (or anything else extra).
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d
(make sure it is executable & root:shell owned), and reboot.
I believe as far as 'ok google' is concerned, the next step would be to compile with the normal vanilla Cyanogenmod defconfig (sorry, but I refuse to install Gapps just to test). Microphone works, mixer values are the same, so... There's a reason I disabled some of that IPv6 stuff...
Behind the scenes I've been (rather unsuccessfully) attempting a port of ION CMA Heap.
http://pastebin.com/J1Ptxz3W
(Which is why I shared the first build without adding any extras, because I knew I was going to break it immediately following).
BTW, I'm still very new at compiling android and it will take me some time to become better acquainted with the build process.
A hack to fix auditd error "protocol not supported"
Jon Lee said:
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d (make sure it is executable & root:shell owned), and reboot.
Click to expand...
Click to collapse
Thanks again Jon! The Permissions for your script file were correct from the start. I don't know how to make sure it was root:shell owned, but it worked nevertheless.
Now, a hack to stop auditd errors:
After I got my apps reinstalled and set late last night, I decided to run catlog, just to see what I could see.
LiquidSmooth is definitely quieter than CM 11. (In the sense of less processes starting and stopping.) To be fair, not quite apples to apples because I'm back to running Dalvik on LS and was running ART on CM 11. (ART comes alive frequently to trim memory.)
But there was one process in LS, that I didn't notice in CM 11, auditd, that just kept starting and stopping with an Error, "Protocol not supported."
Despite that fact that auditd is constantly trying to run, it doesn't stop one of the CPU cores from shutting down (with Hotplug governor), nor does it prevent the CPU from dropping to its lowest freq. So, in practice, it doesn't seem to be a problem. Still, it can't be good to have this one thread constantly starting and stopping and it bugged me.
Now, maybe I caused the problem, because I typically uninstall a lot of Google junk and I disable a lot of Google services in the junk I can't remove. (Boy, Google just keeps pinging and pinging you!) And I hadn't run catlog with a virgin build of LS to see if the auditd Error was there at first.
Having said that, I did find a few other people on Google asking about the same auditd Error. (Apparently, auditd is a process from Sun.)
On the assumption you all get the same Error too, the best way to stop this would be to find out why it's trying to start. And to stop it. (Duh.) But that's WAY beyond me. So instead, I simply renamed the auditd file in /system/bin (it's a binary) to auditd.old.
I cringe when I think about it, but it worked anyway. (Worked in the sense that I don't get the auditd Error anymore.)
(As I write this, I wonder if the "d" at the end of audit is Unix convention to signal a daemon? If so, the I suppose there's probably a start up folder or file somewhere in Linux that's trying to start it? Or do daemons start themselves?)
When streaming video on any room using yellow kernel I get occasional freezes that require powering off my nook
Can I use Yellow Kernel in CM 11?
webdroidmt said:
I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder.
Click to expand...
Click to collapse
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?
PMikeP said:
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?
Click to expand...
Click to collapse
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Mike T
webdroidmt said:
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Click to expand...
Click to collapse
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a second Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)
PMikeP said:
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)
Click to expand...
Click to collapse
You did it right. I did a total clean install of the Liquid rom with the newly "implanted" CM11 kernel. I wouldn't mess around with the partitions, dangerous territory. :laugh:
There's possibly some "hook" that Yellow is looking for that is not contained in CM11.
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error. With the ease of making nandroid backups, stuff like this is always worth a try when it's something you want or need. I'm thrilled that it works the other way, as I do use "Ok Google" a lot on all my devices and this Liquid rom runs nicely on the Nook.
In addition, with the introduction of Lollipop, Google has revamped GN and it's even better to use than before.
Mike T
webdroidmt said:
You did it right. . . .
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error.
Click to expand...
Click to collapse
Good to know I'm not alone then. Oh well, it was a promising experiment.
(Last night I tried experimenting (hacking) to get zRAM to point to a swap file on /cache. Not really a LS thing, but I might write about it later.)
I tried installing this today and it ran really nice and smoothly, but it doesnt seem to have the full HD+ screen resolution. Seemed more like 720p than 1080, large fonts and icons, just a lower resolution. Am I missing a setting or is it not working at full resolution?
Code:
*** Disclamer ***
[U][COLOR="red"]NOTE: This is an experimental build with some bleeding edge features enabled.[/COLOR][/U]
I'm not responsible for anything that may happen to
your tablet as a result of installing custom roms and/or kernels.
You do so at your own risk and take the responsibility upon yourself.
CREDITS:
Ziyan , Sheffzor for setting up their Unlegacy Android project, which is the base of this experimental build.
If you can afford to support some of the developers, please donate to them instead of me.
Shout-out to:
AndDiSa, ParrotGeek, daniel_hk, and franciscofranco for their involvement in Nexus 7 kernel/ROM development.
Features:
The same as Unlegacy Android's kernel, with the addition of ZRAM & ZSMALLOC from upstream kernel 3.10 , and with the addition of SDCARDFS.
Installation:
0. MAKE A BACKUP
1. This kernel is compatible with Unleagcy Android's ROM only, and nothing else.
2. If you have the above mentioned ROM installed, boot in to bootloader mode and flash the boot.img with the following fastboot command:
Code:
fastboot flash boot boot.img
3. If you were previously rooted, don't forget to re-apply root to avoid any related boot loops.
4. Altough ZRAM is added as a feature you have to actually set a size to it in Kernel Adiutor (or some other similar kernel manager app)Download#1/Download#2 and tick "Apply on boot" and reboot your device to turn it on.
Or alternatively create an init.d script to enable it with your desired size at boot.
You can verify if your swap/zram device is working by typing "free" or "vmstat" into a terminal emulator.
If the size of the swap device is anything but 0, it will work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zram is set to LZ4 compression and 4 streams by default, swappiness is set to 50.
5. [Optional] SDCARDFS is enabled by default , you can verify that its working by typing the following commands into a terminal emulator:
Code:
su
df -t sdcardfs
If some lines shows up like on the picture below then SDCARDFS works just fine.
6. Various ramdisk scripts like re-mounting the drives and trimming are currently not added, to avoid any bug reports related to these additions. You can still use SSD Boost or FSTrimmer app to achieve these effects. If this build proves to be stable enough we can look in to adding the scripts to the ramdisk.
7. Have fun
Bugs:
Same as on the base 3.4, for example I rarely encounter a hang/freeze with some graphical glitches, but it's pretty much the same with the unmodified base version.
Due to the lack of a Tilapia device, I was only able test the kernel on a Grouper.
SDCARDFS is highly experimental, it caused some issues on other devices for some users (like space not freeing up after deleting some files), although it works fine for me, you should bear this in mind when you install this kernel.
As mentioned above, you have to either enable swap for zram via an init.d script or via a kernel manager app like Kernel Adiutor.
This is despite the fact that the block device is added to the fstab and swapon_all is added to the init.grouper.rc . Still have to figure out how to get around this, but currently i don't have the time to do so.
Downloads:
Check the downloads tab at the topic title, or
click here for the download link
Sources:
https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Changelog:
2017.06.26
Initial release
Added and enabled ZRAM & ZSMALLOC from upstream 3.10
Added and enabled SDCARDFS
Enabled F2FS for both Cache & Data
XDA:DevDB Information
[TEMPORARY HALT][ALPHA][3.4][ZRAM][SDCARDFS]Experimental Nexus 7 kernel build, Kernel for the Nexus 7
Contributors
namerke, Ziyan, Sheffzor
Source Code: https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Kernel Special Features: SDCARDFS, ZRAM, F2FS CACHE/DATA
Version Information
Status: No Longer Updated
Created 2017-06-26
Last Updated 2017-11-10
Reserved
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
Geko45 said:
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
Click to expand...
Click to collapse
Well, as said in the list of bugs, tilapia is not tested at all due to lack of device.
But if you didn't perform a clean install than it can take it's time to get through the bootloader screen, even on grouper. So make sure you wait there for a while.
On clean install I didn't encounter this issue.
Aside from the freezing issue, this is way smoother than stock.
My current config includes
200MB Zram (swappiness 100 - like Andisa's)
CPU quiet policy: runnable (experiment in reducing the freezes)
interactive perameter 'midrange_go_maxspeed_load' reduced to 90 from its default of 95.
Root Killing SystemUI when the screen is off (Again to try to prevent freezing/need for manual reboot)
SSD Boost
Running this command at startup :
Code:
service call SurfaceFlinger 1009 i32 1
(old habit - suggestion of parrotgeek's to speed up rendering of transparency)
Current result: freezing maybe eliminated, time will tell...
Current theory: Freezing may be due to excessive background cpu load, ie. the system trying to do too much at once. SystemUI may have nothing to do with it, but I still have my suspicions.
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
adstraylight said:
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
Click to expand...
Click to collapse
why the force gpu 2d rendering?
abhifx said:
why the force gpu 2d rendering?
Click to expand...
Click to collapse
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs ?
adstraylight said:
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs
Click to expand...
Click to collapse
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.
abhifx said:
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.
Click to expand...
Click to collapse
Amateurs of the world unite!?
It was something I remembered from trying to optimise MM on grouper that made a lot of difference at points.
So I've stopped killing the systemui, rebooted, and have had 19hrs of uptime since, so I think we can discount that as a cause.
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good ?
adstraylight said:
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good
Click to expand...
Click to collapse
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
abhifx said:
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
Click to expand...
Click to collapse
My guess is that they're already aware of what's been posted here, how are you finding it?
adstraylight said:
My guess is that they're already aware of what's been posted here, how are you finding it?
Click to expand...
Click to collapse
they are relying more on changes pushed to their gerrit rather than tracking all the thread. so i dont know posting in their thread is also a good idea.. but hey its better than nothing.
@namerke great to see someone build something off of the work the 3.4 guys achieved. This was the sort of thing we hoped for from the beginning and I really am surprised that you're the only one so far, years after the project started, to brave the source code and use it for a project.
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream? Cheers
I am running @adstraylight suggested tweaks and its running Rock Solid. The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy. After the initial start the tablet stops having any system ui, force close, or mtp reboot issues. Boot is much faster and functions more like a normal tablet. I would recommend these changes to be incorporated into grouper unlegacy because as of now, running stock unlegacy with updated builds still has freezing, random rebooting and general issues with slowdowns. Honestly I still don't know why F2FS got scrapped for data and cache. I get that they are working on adding support for a lot of devices but it's just not useable in its current form with stock Unlegacy, unless you are okay with systemui freezes and random reboots.
New version is up, please refer to the #1 post for the updated changelog.
adstraylight said:
My current config includes
200MB Zram (swappiness 100 - like Andisa's......
Click to expand...
Click to collapse
Hi @adstraylight , thanks for all the feedback, it's been helpful , really, since i don't have much time to pressure test our device.
New version is including some of your suggestions to the interactive governor + some adjustments to it from Unlegacy-Android gerrit.
Also, @AndDiSa uses 250MB of ZRAM with swappiness of 60 by default , therefore this is the way I have configured the latest version since it seems to work just fine on 3.1 .
Number of ZRAM streams have been reduced to 1, just like @AndDiSa 's config, again , to reduce CPU load.
HTCDreamOn said:
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream?
Click to expand...
Click to collapse
Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
chosin137 said:
The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy.
Click to expand...
Click to collapse
@chosin137 , thanks for the feedback. As it turns out, based on my experience F2FS on cache causes some instabilities on this version too, therefore I have removed the option to use in in fstab.grouper on the updated version.
Also, this way it will be closer to the base , which can help with merging if @Ziyan and @sheffzor decides to go that way.
Thank you all for the feedback, happy testing
Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
Click to expand...
Click to collapse
Makes sense, I've seen a lot of kernels using zram and similar from 3.10. That could be it, it doesn't look like zram is enabled at all in the default kernel but I find it odd that it would be missing the files. I only just flashed the recent version of the ROM a few days ago so it's running fine on the stock kernel, will give yours a go once I've bogged it down with some more apps though.
sadly my experience is on the negative side as i can easily completely freeze my tablet. only reboot is the solution. i guess i have seen this issue more in the stock 3.4x kernel too so i guess its more of a rom / memory leakage issue. However the tab does feels smother than other 3.1x kernel based rom. so the tweaks does seem to help more. i might try flat rom+kernel for while, if things are better then i can blame gapps and remove it altogether (although i do want maps for navigation purpose)
Hey everyone! Hope you're all doing fine. I just updated to Android 10, coming from AICP Pie, and I noticed that battery life took a serious hit compared to AICP. Now I know that AICP (and probably many other custom ROMs) use EAS by default, which could be credited for the great performance and battery life you get with these setups. This didn't stop me from conducting some tests and experimenting with some changes in order to try and improve the battery life I am getting on Android 10 (and possibly all previous versions of the stock ROM). Anyway, without further ado, here is a script that tweaks the phone a little, which should improve your phone's battery life on STOCK ROMs, mainly Android 10 but it is also applicable to Android 9, though I have mainly tested it on Android 10 and the deprecated developer previews and beta builds of Android 10. A link to download the script is provided down below, right below the prerequisites and instructions.
Prerequisites
1- An Essential PH-1 (of course!)
2- Magisk (make sure to have the latest version installed)
3- A terminal emulator app -- I use this one here:
https://play.google.com/store/apps/details?id=jackpal.androidterm
4- Any file manager app.
Instructions
1- Download the script from the link below.
2- For more convenience, move the script you just downloaded to the root of your internal storage (/sdcard) using any file manager if your choice.
3- Open the terminal emulator app.
4- Type "su" (without the quotes) and hit the enter/return key on your keyboard to grant it root access (Magisk could display a pop-up window asking whether you want to grant this app root access. Make sure to tap in Grant. This usually happens once).
5- Afterwards, type "sh /sdcard/essential-tweaks" (without quotes) and hit the enter/return key on your keyboard to execute the script.
6- Voila! You're done!
--> In case you think the script has caused any regressions your are dissatisfied with, simply reboot your phone since this script doesn't automatically get applied on boot.
--> In case you rebooted your phone and wish to re-apply the script, simply follow the same instructions again.
Download
G Drive: https://drive.google.com/file/d/101Z_Co7uVU_h2blanJ88MV8x9PpRcOvg/view?usp=drivesdk
Let me know your thoughts down below. Cheers!
Reserved
Reserved 2
Sounds interesting and I'd like to try it. I don't know if you know this though, but the file on Google Drive is set to "ask permission" to download it.
Tanner1294 said:
Sounds interesting and I'd like to try it. I don't know if you know this though, but the file on Google Drive is set to "ask permission" to download it.
Click to expand...
Click to collapse
Fixed. Sorry for inconvenience. Thanks for letting me know!
#justgoogledrivethings
Mostafa Wael said:
Hey everyone! Hope you're all doing fine. I just updated to Android 10, coming from AICP Pie, and I noticed that battery life took a serious hit compared to AICP. Now I know that AICP (and probably many other custom ROMs) use EAS by default, which could be credited for the great performance and battery life you get with these setups. This didn't stop me from conducting some tests and experimenting with some changes in order to try and improve the battery life I am getting on Android 10 (and possibly all previous versions of the stock ROM). Anyway, without further ado, here is a script that tweaks the phone a little, which should improve your phone's battery life on STOCK ROMs, mainly Android 10 but it is also applicable to Android 9, though I have mainly tested it on Android 10 and the deprecated developer previews and beta builds of Android 10. A link to download the script is provided down below, right below the prerequisites and instructions.
Prerequisites
1- An Essential PH-1 (of course!)
2- Magisk (make sure to have the latest version installed)
3- A terminal emulator app -- I use this one here:
https://play.google.com/store/apps/details?id=jackpal.androidterm
4- Any file manager app.
Instructions
1- Download the script from the link below.
2- For more convenience, move the script you just downloaded to the root of your internal storage (/sdcard) using any file manager if your choice.
3- Open the terminal emulator app.
4- Type "su" (without the quotes) and hit the enter/return key on your keyboard to grant it root access (Magisk could display a pop-up window asking whether you want to grant this app root access. Make sure to tap in Grant. This usually happens once).
5- Afterwards, type "sh /sdcard/essential-tweaks" (without quotes) and hit the enter/return key on your keyboard to execute the script.
6- Voila! You're done!
--> In case you think the script has caused any regressions your are dissatisfied with, simply reboot your phone since this script doesn't automatically get applied on boot.
--> In case you rebooted your phone and wish to re-apply the script, simply follow the same instructions again.
Download
G Drive: https://drive.google.com/file/d/101Z_Co7uVU_h2blanJ88MV8x9PpRcOvg/view?usp=drivesdk
Let me know your thoughts down below. Cheers!
Click to expand...
Click to collapse
Neat...
A kranel tweaker...
In my opinion:
The damn powerhint is probably the worst offender to battery...
Currently, with magisk, I just remove /vendor/etc/powerhint.xml
I am also using kernel touchboost so I can idle down to 300...
If your battery doesn't suck... You can switch back to 518 and 806 for minimum frequencies, disable msm touchboost, and kill the powerhint... And get MUCH closer to where you were with AICP on Pie
rignfool said:
Neat...
A kranel tweaker...
In my opinion:
The damn powerhint is probably the worst offender to battery...
Currently, with magisk, I just remove /vendor/etc/powerhint.xml
I am also using kernel touchboost so I can idle down to 300...
If your battery doesn't suck... You can switch back to 518 and 806 for minimum frequencies, disable msm touchboost, and kill the powerhint... And get MUCH closer to where you were with AICP on Pie
Click to expand...
Click to collapse
Is that similar to disabling perfd?
Because that is what I did (and incidentally what my script does).
Thanks a lot for your suggestion!
Mostafa Wael said:
Is that similar to disabling perfd?
Because that is what I did (and incidentally what my script does).
Thanks a lot for your suggestion!
Click to expand...
Click to collapse
No sir...
The powerhint has something to do with the PowerHals directly...
You'll notice if you watch any frequency monitor that when you touch the screen... It jumps to 1.1Ghz on both big and little ... That's NUTS...
It also will run the processor at 1.9 and 2.5 for 5 seconds on app launch... Also CRAZY and unnecessary
Perfd controls the profiles in /vendor/etc/... I think there's 8 of em...
And like mpdecision before it... It sucks...
On a side:
I've been on Q since beta 2... And have put together a magisk module that cuts frequencies down... 1.8 Max for little and 2.0 for big... Kills perfd... Kills the powerhint by replacing with a 0 byte file... Ups zram to 1 GB... And puts touchboost to 825 and 499...
I just incorporated your scheduler changes and I'll let you know what I come up with...
If you're interested in the module ... I'll share it .. just let me know
Edit: @KuranKaname approves the frequency choices BTW
rignfool said:
No sir...
The powerhint has something to do with the PowerHals directly...
You'll notice if you watch any frequency monitor that when you touch the screen... It jumps to 1.1Ghz on both big and little ... That's NUTS...
It also will run the processor at 1.9 and 2.5 for 5 seconds on app launch... Also CRAZY and unnecessary
Perfd controls the profiles in /vendor/etc/... I think there's 8 of em...
And like mpdecision before it... It sucks...
On a side:
I've been on Q since beta 2... And have put together a magisk module that cuts frequencies down... 1.8 Max for little and 2.0 for big... Kills perfd... Kills the powerhint by replacing with a 0 byte file... Ups zram to 1 GB... And puts touchboost to 825 and 499...
I just incorporated your scheduler changes and I'll let you know what I come up with...
If you're interested in the module ... I'll share it .. just let me know
Edit: @KuranKaname approves the frequency choices BTW
Click to expand...
Click to collapse
Yes I know about the max frequency values. These used to be the default in Kuran's AICP too
Interesting, so you mean to say that this is completely different from perfd? Well, I only disabled perfd and I am not seeing the phone jumping back to 1.1GHz while interacting with the screen or locking on max frequencies while launching apps.
Also, what command are you using to disable perfd on Q? I just found out that the usual "stop perfd" command is not working anymore like it used to on Pie :/
I used EXKM to disable it and it works just fine :good:
Let me know if my sched tweaks bring any further improvements to you. Cheers!
EDIT: these input boost frequency values used to be the ones Sultanxda go for too iirc right?
Mostafa Wael said:
Yes I know about the max frequency values. These used to be the default in Kuran's AICP too
Interesting, so you mean to say that this is completely different from perfd? Well, I only disabled perfd and I am not seeing the phone jumping back to 1.1GHz while interacting with the screen or locking on max frequencies while launching apps.
Also, what command are you using to disable perfd on Q? I just found out that the usual "stop perfd" command is not working anymore like it used to on Pie :/
I used EXKM to disable it and it works just fine :+1:
Let me know if my sched tweaks bring any further improvements to you. Cheers!
Click to expand...
Click to collapse
Interesting ..
stop perfd
getprop|grep perfd yields the service has stopped for me
rignfool said:
Interesting ..
stop perfd
getprop|grep perfd yields the service has stopped for me
Click to expand...
Click to collapse
Weird. I will check again when I am home.
Thanks for chiming in! :highfive:
Mostafa Wael said:
Weird. I will check again when I am home.
Thanks for chiming in! :highfive:
Click to expand...
Click to collapse
Interesting... I just put back the powerhint... While stopping perfd and now it's listening ... I wonder if I came up with that when I had the typo in my script...
Thanks for forcing me to debug...
---------- Post added at 02:30 PM ---------- Previous post was at 02:18 PM ----------
Mostafa Wael said:
Weird. I will check again when I am home.
Thanks for chiming in! :highfive:
Click to expand...
Click to collapse
OHHHH...
Are you using service.d to run your script?
If so... You need
while [ "$(getprop sys.boot_completed)" != 1 ];
do sleep 1;
done
sleep 5
Before... Otherwise init gonna reset your stuff...
And post-fs-data.d is WAAY too early
So I have been doing a lot of tracing and testing some new changes and, well, I think it is very difficult to squeeze any more battery life on stock ROMs. Which means that it is highly unlikely that this script is going to be updated with new additions as this is practically the best we could reach at the moment. However, I will keep digging deep and see if I can come up with any updates.
To put things into perspective, here is a quick comparison with the default stock ROM tunings.
By default, I would get an average active drain of 14%/h per charge cycle, peaking at 16%/h
After applying this script the average active drain rate would drop to around 12-13%/h, peaking at 15%/h.
In other words, there is around 1-2%/h improvement in active drain rate as per my usage.
Idle drain rate is fairly similar though.
Mostafa Wael said:
So I have been doing a lot of tracing and testing some new changes and, well, I think it is very difficult to squeeze any more battery life on stock ROMs. Which means that it is highly unlikely that this script is going to be updated with new additions as this is practically the best we could reach at the moment. However, I will keep digging deep and see if I can come up with any updates.
To put things into perspective, here is a quick comparison with the default stock ROM tunings.
By default, I would get an average active drain of 14%/h per charge cycle, peaking at 16%/h
After applying this script the average active drain rate would drop to around 12-13%/h, peaking at 15%/h.
In other words, there is around 1-2%/h improvement in active drain rate as per my usage.
Idle drain rate is fairly similar though.
Click to expand...
Click to collapse
hello. Thanks for your work. It's nice and works very well.
How I can add this script to autorun?
P.S. Here is screenshots of my battery life after tweaks
@Mostafa Wael Hey mate, do you remember what the experiment was that you wanted to do recently ?
Was meant to help with smoothness and battery on Android 10?
St.Noigel said:
hello. Thanks for your work. It's nice and works very well.
How I can add this script to autorun?
P.S. Here is screenshots of my battery life after tweaks
Click to expand...
Click to collapse
I really don't have any idea, I just run then every time after boot via terminal emulator ?
CamoGeko said:
@Mostafa Wael Hey mate, do you remember what the experiment was that you wanted to do recently ?
Was meant to help with smoothness and battery on Android 10?
Click to expand...
Click to collapse
Well, it was a desperate attempt by me to try and squeeze more juice on Android 10 custom ROMs, not sure it will work out on stock ROM. Basically, I am experimenting with different values for the cpusets and stune settings of each cgroup.
I'm still evaluating whether it has a significant impact or not. So far, it is almost the same...
Mostafa Wael said:
Well, it was a desperate attempt by me to try and squeeze more juice on Android 10 custom ROMs, not sure it will work out on stock ROM. Basically, I am experimenting with different values for the cpusets and stune settings of each cgroup.
I'm still evaluating whether it has a significant impact or not. So far, it is almost the same...
Click to expand...
Click to collapse
If you're running Artemis... You're wasting you're time...
Military Dictator @KuranKaname does not allow for the powerhal to accept adjustments from stune other than what HE deems required ...
You MIGHT be able to adjust scheduler values and have them mean something ...
rignfool said:
If you're running Artemis... You're wasting you're time...
Military Dictator @KuranKaname does not allow for the powerhal to accept adjustments from stune other than what HE deems required ...
You MIGHT be able to adjust scheduler values and have them mean something ...
Click to expand...
Click to collapse
Cpuset and stune values are open (besides the top-app stune boost)
I'm using elementalx kernel on android 10 nov update, and my battery drain in deep sleep is unusually high at 2 - 2.5% per hour.
I'm wondering if this script conflicts with anything with the kernel.
I took a look at the script and it looks like some of the settings I can apply in the kernel manager.