{
"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"
}
DISCLAMER
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.
Click to expand...
Click to collapse
LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device.
We ask that you do your part to know your device and know how to recover from problems before you flash!
Liquid0624
Deadman96385
jsnweitzel
Somber73
TheBr0ken
CPA-Poke
Cdub50
Code:
Linaro 4.9 GCC Toolchain
O3 Strict-Aliasing & ISO C++11 Mode
ARM Optimized String Handling Routines
Linaro and Code Aurora Optimaztions
Slims DPI on the fly
Custom animation controls
TRDS 3.0 (Liquid Blackout in settings)
Active Display
Slims QuickSettings
Halo (Renamed to bubble in settings)
Ram Bar
T-Mobile Theme Engine
Privacy Guard
Built in SuperUser
Working wifi Tethering
Cell Broadcasts
Slims Configurable Power Menu
Slims Configurable Nav Bar
Custom animation controls (Listview)
LockScreen Notifications
And way more than this...
Code:
[url="http://pastebin.com/WNTJMS6k"]LiquidSmooth v3.0 Full list of features[/URL]
Code:
[url="http://github.com/LiquidSmooth"]LiquidSmooth Github[/URL]
Code:
[url="http://www.drdevs.com/devs/teamliquid/Nightly/Xperia%20TX/"]ROM Download[/URL]
[url="http://www.drdevs.com/devs/teamliquid/Gapps/"]Slim AIO Gapps Download[/URL]
Please Support Liquid by Donating HERE
XDA:DevDB Information
LiquidSmooth v3.0 Beta - Hayabusa {TX}, a ROM for the Sony Xperia T
Contributors
deadman96385
Version Information
Status: Testing
Current Beta Version: 3.0
Created 2014-03-06
Last Updated 2014-03-09
This is a untested build because I do not know anyone with the TX, it should work fine.
Bugs:
No confirmation that Theme has been applied, requires reboot to see the theme
Pie needs a reboot to show up
Click to expand...
Click to collapse
Xperia TX specific bugs:
None so far
Click to expand...
Click to collapse
Mine just in case
Sorry, but how to turn off touch by cursor and use just normal touch ?
caer_ayu said:
Sorry, but how to turn off touch by cursor and use just normal touch ?
Click to expand...
Click to collapse
do it like that of cm11
Leo said:
do it like that of cm11
Click to expand...
Click to collapse
But I didn't even know how to turn it off on cm11 ..this rom is just too amazing not to use
Do you know how to change it? ..
Does this rom stable to use ??
Shobr said:
Does this rom stable to use ??
Click to expand...
Click to collapse
don't know yet ..i'm still waiting for the touch setting solution then i will use this for a long term then
caer_ayu said:
But I didn't even know how to turn it off on cm11 ..this rom is just too amazing not to use
Do you know how to change it? ..
Click to expand...
Click to collapse
In /system/usr/idc there is a file named "sensor00_f11_sensor0.idc" (or something like that). Rename it to "clearpad.idc", and reboot.
Testing so far. Boots fine, but I'm mainly interested in seeing if it has the same kernel bug as FXP's CM11/10.2/10.1 which prevent the phone from sleeping.
Another thing I've noticed is that both this ROM and CM ROMs check for the device product/name in the updater-script before flashing, and in every case I've had to erase those initial lines because the phone name never matches. I've tested coming from an Official USA FTF, so I think maybe there should be more checking options or remove it altogether, because odds are it won't match, depending on the ROM you're coming from.
EDIT:
Not the exact same wakelocks as in CM11, but still nasty. On the initial boot I couldn't turn GPS off, it apparently turned off eventually, but I'm quite sure it's what caused that wakelock.
So, to follow up, it does have the exact same problem as FXP's CM ROMs, with the exact same wakelocks. I might add, this happens only on WiFi, as can be seen in the attached screenshots.
If you have any suggestions and/or fixes I'll be glad to help with tests.
thank you very much ..it worked ..
Antiga Prime said:
So, to follow up, it does have the exact same problem as FXP's CM ROMs, with the exact same wakelocks. I might add, this happens only on WiFi, as can be seen in the attached screenshots.
If you have any suggestions and/or fixes I'll be glad to help with tests.
Click to expand...
Click to collapse
Thank you for these i will work to fix them, but for the time being try and use the wakelock blocker and see how it goes with that.
deadman96385 said:
Thank you for these i will work to fix them, but for the time being try and use the wakelock blocker and see how it goes with that.
Click to expand...
Click to collapse
That would be ideal if it weren't for the fact that those wakelocks aren't detected by Wakelock Blocker. If you think of anything else, LMK.
EDIT: Attached are logs I pulled with BBS after flashing again in order to confirm whether those wakelocks are detected by Wakelock Blocker. Maybe I should have pulled a proper logcat/dmesg...
GPS is not working in CM11(the symptom is exactly the same as members have mentioned above - cannot turn Location Info off and an awful wakelock appears)but if you replace the folder kernel/arch/arm/mach-msm with OmniROM's and then re-compile the kernel,GPS will work,and the GpsLocationProvider wakelock disappears,you can also turn Location Info off at once.I don't know which file in that folder caused this...There are so many differences in the files.Maybe some SMD/RPC/NMEA related files are the ones to blame?(JUST GUESSING)
And one another problem:after turning off the screen,surfaceflinger will start to eat CPU(50% usage,see in adb shell - top) and comsumes a lot of energy.Strace its threads and I found only one thread is doing system calls(doing really frequently...What's that?Software simulated VSYNC?).If the screen is on,the process behaves normally.The dirty fix for GPS doesn't work for this...
updateing said:
And one another problem:after turning off the screen,surfaceflinger will start to eat CPU(50% usage,see in adb shell - top) and comsumes a lot of energy.Strace its threads and I found only one thread is doing system calls(doing really frequently...What's that?Software simulated VSYNC?).If the screen is on,the process behaves normally.
Click to expand...
Click to collapse
Did you happen to test this with WiFi on? The reason I ask is because, as I stated before, while the screen is off and WiFi is on, there is something keeping the CPU active, for at least half of the time the screen is off.
Antiga Prime said:
Did you happen to test this with WiFi on? The reason I ask is because, as I stated before, while the screen is off and WiFi is on, there is something keeping the CPU active, for at least half of the time the screen is off.
Click to expand...
Click to collapse
Maybe it's just the crazy surfaceflinger?Persistent 50% CPU usage is a nightmare for battery...And whether WiFi is on doesn't matter.It's JUST driving the CPU and killing the battery.
Antiga Prime said:
Did you happen to test this with WiFi on? The reason I ask is because, as I stated before, while the screen is off and WiFi is on, there is something keeping the CPU active, for at least half of the time the screen is off.
Click to expand...
Click to collapse
I tested it this afternoon.The outcome is the same as I predicted:after the screen is turned off,surfaceflinger eats CPU (and since it's a kernel process,it doesn't need to hold a wakelock to run while screen is off - just like adbd)
updateing said:
I tested it this afternoon.The outcome is the same as I predicted:after the screen is turned off,surfaceflinger eats CPU (and since it's a kernel process,it doesn't need to hold a wakelock to run while screen is off - just like adbd)
Click to expand...
Click to collapse
Well, then it would seem that there are two different issues, which might be phone specific(?). In my case, I know for a fact how to stop the CPU usage while screen is off and stop the battery drain, which is turn off WiFi. What I don't get is what does the "mmc1_detect" wakelock have to do with WiFi anyway. The other wakelock, "suspend_backoff" does actually seem related to WiFi:
Rationale: suspend_backoff is triggered whenever there's a rapid succession of sleep-wakeup-sleep transitions in a short period of time (10 occurrences within x ms IIRC). When that happens, SB makes sure the device is continuously awake for a bit instead of alternating a lot. The KWL count indicator could give a hint about the source of those continuous wakes, but not a definite answer because it doesn't show their time distribution.
Known conditions of occurence:
In relation with Chrome: http://forum.xda-developers.com/showpost.php?p=28676218&postcount=24 In relation with Wifi turning on/off when the screen goes on/off
Click to expand...
Click to collapse
The problem is FXP ROMs, as with this LS, don't come with Chrome installed; and I've already seen it get fixed by turning WiFi off.
Of course, that doesn't seem to have to do anything with Surfaceflinger, at least not in my case (although, I didn't check, but would be good if I flash FXP or LS again), and if other people aren't getting the same battery drain under the same conditions as I am (i.e., they can use WiFi normally without having the same nasty battery drain and/or same wakelocks), then it would seem the ROM is sort of choosy when it comes to the phones it's installed on.
Antiga Prime said:
Well, then it would seem that there are two different issues, which might be phone specific(?). In my case, I know for a fact how to stop the CPU usage while screen is off and stop the battery drain, which is turn off WiFi. What I don't get is what does the "mmc1_detect" wakelock have to do with WiFi anyway. The other wakelock, "suspend_backoff" does actually seem related to WiFi:
The problem is FXP ROMs, as with this LS, don't come with Chrome installed; and I've already seen it get fixed by turning WiFi off.
Of course, that doesn't seem to have to do anything with Surfaceflinger, at least not in my case (although, I didn't check, but would be good if I flash FXP or LS again), and if other people aren't getting the same battery drain under the same conditions as I am (i.e., they can use WiFi normally without having the same nasty battery drain and/or same wakelocks), then it would seem the ROM is sort of choosy when it comes to the phones it's installed on.
Click to expand...
Click to collapse
On my phone,turning off WiFi doesn't reduce CPU usage.I can see in System Tuner Pro that it's running.And while the screen is on,CPU usage is also high,nearly ~80% all the time...
Another interesting thing:if you make a kernel with OmniROM's zImage and LS/CM's ramdisk,the phone can boot with no screen display(display driver mismatch?Surfaceflinger should be working though).But in DDMS you can see GPS is working correctly and off-screen CPU usage is normal...
Related
Due to many DHD's being incorrectly factory calibrated with regards to the proximity sensor, I wrote a little app to allow one to change the calibration on-the-fly and persist it over reboots.
This app is specifically for those experience issues with the proximity sensor.
Well known symptoms include the following:
- Screen fails to turn off when holding to face on a call
- Screen does turn off when holding to face on a call, but fails to come back on, requiring taking out the battery
These problems are common in custom kernels/ROM's. HTC has addressed this issue however in their kernels from 1.32 onwards, but have failed to provide an acceptable solution for some.
I present DHD Proximity Sensor Recalibrator. Download from the attachments below.
Here are some screenshots:
{
"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"
}
Usage:
1. Install app.
2. Run app.
3. Press the toggle button to start monitoring.
4. Move your finger over the proximity sensor (the little LED next to the front facing speaker).
5. Adjust the High and Low threshold values to your liking.
For those whose screen does not turn off, it probably means the factory values are set too high.
For those whose screen does not turn back on, it probably means the factory values are set too low.
The setting will be saved, and will be applied every time you reboot your phone. No need to go through any of the steps unless you want to change the calibration. When the settings are applied at boot time, you will get a toasty indicating the calibration value applied.
Possible calibration procedure:
1. Put both values high (will show FAR).
2. Cover sensor with finger.
3. Lower High threshold till it says NEAR.
4. Lower Low threshold by a notch or 2.
5. Test behavior
Removal:
If for whatever reason you find the application does not work, or you do not want it anymore, just uninstall the app, and reboot. Your original factory settings will be in effect again. This application does not modify your system. It might require root rights.
Source code repo:
https://github.com/leppie/DHD-Proximity-Sensor-Recalibrator
Known issues:
- Permissions have changed in CM7 RC2, preventing the application from working correctly. The application will need root. Will investigate how to add that, if needed.
- Some reports that the Gingerbread leaked ROM is not working.
Gingerbread/newer kernel update:
Due to changes in the source code made by HTC to overcome this issue in the kernel, this app will probably not run correctly.
There are 2 problems (as found from latest CM kernel source):
1. When the kernel recalibrates the proximity on the fly, it fails to update the internal structures in the kernel. This makes the kernel not report correct values. I have made a kernel patch to rectify the issue. Please ask your kernel developer to apply the following changes: https://github.com/leppie/htc-kernel-msm7x30/commit/b1d0a85f3fe5252c8ab43ba98261bcb1b8498d8a
2. Secondly and more seriously, depending on the initial calibrated value (if LT is greater or equal to 0x50), the kernel will kick off a polling thread. This will overwrite the changes made by this app, as soon as you use the proximity sensor for the first time (eg the phone). Afterwards you can apply the values from this app again, and from my experiments the value sticks then (up to the next reboot). Unfortunately, this polling mechanism fixes the issue for most users, so it cannot just be disabled. It is easy to disable in the kernel source however, but will probably break most other people's proximity behavior if they do not have this app installed. As you can see, there is not much I can do about this. The best option is to compile your own kernel.
Manual cleaning of the sensor:
After time the sensor will become dirty from the environment. See http://forum.xda-developers.com/showpost.php?p=28495941&postcount=357 for details on cleaning it.
Please report any bug and suggestions.
Cheers
Revisions:
1.0
- Initial public release
1.1
- Replaced toggle button with normal one to resolve known issue
1.2
- Removed amount from Paypal, feel free to donate whatever you feel like. Beers are around US$2 here.
1.3
- Add some better handling when something goes not as planned (likely on non-DHD hardware).
1.4
- Added some alert dialogs to aid with the problems people are experiencing. (In case of error, please note both the title text, and the first few lines in the text of the alert dialog.)
1.5
- Only for CM7 users. Use nightly 92 or above. This includes the necessary kernel patch.
- Should work on SENSE with custom kernel. Apply this patch (or ask your kernel 'builder' to do so).
- Removed Beer button due to crappy paypal policy...
1.6
- Added support for calling 'su' when permissions are wrong. Thanks VampireWicked.
1.7
- Correct boot permissions for ICS
1.8
- Prevent app from being installed on SD card (which will cause issues) (thanks makarand14)
1.9
- Fix issues with sensor listener not getting disabled (thanks Roberto_Lim and Stoffl_)
1.10
- Fix issues with slow process manager in Android, notably in BlackOut ROM (thanks tonylee000 and others)
Supported kernels:
- CM7 nightly #92 or later
- LorDModUE V2.6 or later
great .. gona try this now ..!!
Simply works. Great job!
jkoljo said:
Simply works. Great job!
Click to expand...
Click to collapse
how do you get it to work? when i move my finger over the sensor nothing happens. it always says near?
Them you have to change the settings. The app works great btw!
Sent from my Desire HD using XDA App
If it says near, make your values higher.
In a bad case, keep your finger over the sensor, and then increase the low threshold till it changes.
Then work from the settings there.
Awesome!
This is my favorite app to date! I couldn't use any Cyanogen mod because of this issue. (My device was not waking up after the first phone call) Everything else worked fine.
Now I can use my phone as a phone too!
Would recommend to any O2 Germany DHD user having similar issues.
Stuclint said:
This is my favorite app to date! I couldn't use any Cyanogen mod because of this issue. (My device was not waking up after the first phone call) Everything else worked fine.
Now I can use my phone as a phone too!
Would recommend to any O2 Germany DHD user having similar issues.
Click to expand...
Click to collapse
Yep i'm O2 Germany DHD user too and had this issue.
This is really a life-saver app, thanks!
You are awesome, leppie!
I didn't even have a problem with my sensor, but I tuned it a little bit anyway. Awesome. THANK YOU
Thanks man! Helped me a lot!
Burkow
I had this sensor problem and did make enquiry in other thread but can't find anysolution.
However, (don't konw since when) it works without any problem now.
Guess I should subscribe this thread just in case I need it in future (hopefully not).
Thanks leppie!
5 stars rated.
Thanks for all the complements.
Added a link to the public source code repository on github.com for those interested.
Hi!
hi!! does anyone know about this app but for the HTC HD mini?
thanks!!!
boxer39 said:
hi!! does anyone know about this app but for the HTC HD mini?
thanks!!!
Click to expand...
Click to collapse
Sorry, that is a Windows Mobile phone. Can't help with that
Thank you guy!! Finally!! Great work
Ace app! Even though I'm on stock, I sometimes get problems with my screen coming on during a call, and my accidentally muting the call. This should help me fix it, by fixing the threshold distance!
Awesome, thanks
leppie said:
Sorry, that is a Windows Mobile phone. Can't help with that
Click to expand...
Click to collapse
it's ok, this thing is killing me!! I just didn't find a buyer yet, but i'm definitly changing it for the desire HD! the best one!!
thanks!!!
T-Mobile G2
hey
will this work on the T-Mobile G2 (Desire Z). If so I will be SOOO grateful to you and I probably will actually buy you a beer. My girlfriend and I both have G2's and the proximity sensor is the only problem with these phones.
Dave
hi,
i have both sensor problems! every second time my phone turns off the screen while phoning but not on again or somtimes the sreen is still on while phoneing
with the app i can set the sensor but still not working during a call
can someone help me?
sry for my bad english
Thank you. Will try it on my Desire HD later
{
"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"
}
If you have building/development concerns or issues, Please visit the BeanStalk Development Thread to avoid cluttering this thread.
CyanogenMod 13 based
Quicker system animations
Trimmed down fat and excess bloat
Option to enable all widgets
Numerous extra lockscreen options
LCD Density
Custom original BeanStalk Wallpapers by skyliner33v
Custom BeanStalk bootanimation by skyliner33v
3-minit battery support
Clock and date options
Contextual Header - Original and Polygraphic
Battery styles - Includes specific colors and styles. Also includes battery bar
Do not disturb option
Show notification count
Recent screen options
Customizable navigation bar
Use Omniswitch as default recents
Built-in screen record
Toast animations
App Circle bar
Gesture Anywhere
Disable FC warnings
Disable Immersive message
Force expanded Notifications
Configure scrolling cache
Build.prop MOD options to enable/disable tweaks as preferred
Less frequent Notification sounds options
CRT screen off/on options to specify how the animation shows
Enable/disable wake up on charge option
Superuser fully embedded into the build and accessed from settings menu
CM Performance options and features
Hide superuser icon
Developer options and advanced reboot enabled by default
Numerous cherry-picks and improvements throughout the build, baked into the
awesomeness of existing CM layout.
Numerous other options hiding throughout the build. For a full list of changes and features, please
be sure to checkout change log below.
DISCLAIMER:
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.
Camera2 doesn't work. 3rd party camera apps work.
Open Gapps
BeanStalk Changelog
* Download ROM, the latest GAPPs.
* Full wipe and format is ALWAYS suggested to avoid odd issues.
* Flash ROM, GAPPs.
* SUPERSU INSTALLATION
* Wipe cache & dalvik cache
* Reboot and enjoy the BeanStalk goodness.
@monster1612 @Hashcode @spezi77 @transi1
Special thanks for the assistance
@monster1612
BeanStalk source can be found HERE
Skylinerv33 - Graphics and bootanimation - Thanks!
Vaughn N - Endless support and help throughout the years.
Cyanogenmod - HERE
AICP - HERE
CRDRoid - HERE
Imoseyon, Flar2, Beanstown, anyone I forgot
Donate to scott.hart.bti by clicking HERE
SOURCE
local_manifest
jem
bowser-common
omap4-common
kernel
proprietary
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
Contributors:
@alexander_32
Version Information
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.72+; 3.0.101+
Based On: CyanogenMod
Status: Release Candidate
Current Version: 6.25
TWRP BUILDS
Created 2016-08-10
Last Updated 2016-10-09
Wow a new ROM! I'm going to install this right now.
*EDIT*
It runs pretty nice and the camera actually works. Using Open Camera. Is HDMI working or is it broken like the other CM13 ROMs?
Good ROM with Root tools. Quite smooth and good battery cost. But sometimes wifi disconnect. All good but wallpapers is too ugly....
sirp0p0 said:
Wow a new ROM! I'm going to install this right now.
*EDIT*
It runs pretty nice and the camera actually works. Using Open Camera. Is HDMI working or is it broken like the other CM13 ROMs?
Click to expand...
Click to collapse
FOR THE RECORD: I DON'T HAVE JEM.
HDMI is probably broken, because the source is almost identical.
Hope you guys like what you see.
UPDATE! BeanStalk 6.20 (MOB30Z)
Special thanks to @r3t3ch for the assistance.
https://www.androidfilehost.com/?fid=24591000424954047
Installation: full wipe / flash ROM + GApps / wipe cache + dalvik cache.
This is actually a very good build, so props to you OP!
A few things though. The device isn't deep sleeping at all. This causes a roughly 1-2% per hour discharge. Not a huge deal, but definitely should be fixed. Also, GPU and CPU performance leaves a lot to be desired. The system becomes quite unresponsive with simple tasks.
balleron24z said:
This is actually a very good build, so props to you OP!
A few things though. The device isn't deep sleeping at all. This causes a roughly 1-2% per hour discharge. Not a huge deal, but definitely should be fixed. Also, GPU and CPU performance leaves a lot to be desired. The system becomes quite unresponsive with simple tasks.
Click to expand...
Click to collapse
Do you use Greenify? If not there is no wonder "the device isn't deep sleeping at all" as well as "GPU and CPU performance leaves a lot to be desired". Don't forget it's a budget device with dual core processor, don't overload it, especially with live wallpapers.
balleron24z said:
The device isn't deep sleeping at all. This causes a roughly 1-2% per hour discharge. Not a huge deal, but definitely should be fixed.
Click to expand...
Click to collapse
Can you try changing ro.ril.disable.power.collapse in your build.prop to equal 0 and see if deep sleep is affected after a reboot? You can do this easily from kernel aduitor in system settings.
I tried this rom, but return to cm 11, the deep sleep issue is a big problem: From morning to night more than 30% of the battery drain, with cm 11 the kindle remains 98% more than a week without use.
alexander_32 said:
Do you use Greenify? If not there is no wonder "the device isn't deep sleeping at all" as well as "GPU and CPU performance leaves a lot to be desired". Don't forget it's a budget device with dual core processor, don't overload it, especially with live wallpapers.
Click to expand...
Click to collapse
@alexander_32, not sure if you're copping a condescending tune with me or not, but Greenify is only good for controlling what the system cannot as far as wakelocks. Running the OS barebones, it wasn't sleeping, and there were/are no apps keeping it awake. I know you have to assume that us "testing" the ROM don't know what there doing, but trust me, I've been at it long enough to know what I'm doing. But just so we're clear, I've frozen all of the apps from waking up the device, and after multiple reboots, it still won't sleep. And also, I understand this is a dual-core device, I know it has performance limits. But I've ran dual core devices that exhibited a lot less stutter running CM. All I was saying is what I've experienced, as to potentially offer assistance with making the ROM run more efficiently. And also, I personally think Live Wallpapers are garbage, and for the sake of device performance, would've already disabled them in an effort to improve device performance.
@r3t3ch thank you for your contribution to a potential resolution for one of the issues listed. I'll report back to provide an update if that fixes it. My screenshot shows its vbus USB, and honestly, nor sure if that's some sort of USB detection system or what.
balleron24z said:
@alexander_32, not sure if you're copping a condescending tune with me or not, but Greenify is only good for controlling what the system cannot as far as wakelocks. Running the OS barebones, it wasn't sleeping, and there were/are no apps keeping it awake. I know you have to assume that us "testing" the ROM don't know what there doing, but trust me, I've been at it long enough to know what I'm doing. But just so we're clear, I've frozen all of the apps from waking up the device, and after multiple reboots, it still won't sleep. And also, I understand this is a dual-core device, I know it has performance limits. But I've ran dual core devices that exhibited a lot less stutter running CM. All I was saying is what I've experienced, as to potentially offer assistance with making the ROM run more efficiently. And also, I personally think Live Wallpapers are garbage, and for the sake of device performance, would've already disabled them in an effort to improve device performance.
@r3t3ch thank you for your contribution to a potential resolution for one of the issues listed. I'll report back to provide an update if that fixes it. My screenshot shows its vbus USB, and honestly, nor sure if that's some sort of USB detection system or what.
Click to expand...
Click to collapse
My personal experience: after deleting useless system apks (before flashing) in system/app and priv-app folders, greenifing almost everything except Smart Launcher, Twilight and system apps like CyanogenMod Syetem, CM Settings Storage etc, disabling boot at start for each app except Smart Launcher, Twilight, Youtube (doesn't work without it), Cleaning junk, cache, art/dalvik cache, it changes from 100% to 99% in 6-7 hours and no complaints about that.
jaramosparra said:
I tried this rom, but return to cm 11, the deep sleep issue is a big problem: From morning to night more than 30% of the battery drain, with cm 11 the kindle remains 98% more than a week without use.
Click to expand...
Click to collapse
balleron24z said:
@r3t3ch thank you for your contribution to a potential resolution for one of the issues listed. I'll report back to provide an update if that fixes it. My screenshot shows its vbus USB, and honestly, nor sure if that's some sort of USB detection system or what.
Click to expand...
Click to collapse
I found the source of the deep sleep issue. It'll be fixed in the next build in about a day or so.
Edit: flash this boot.img from twrp (Install > Install Image > select boot) for a quick deep sleep fix
Works perfectly!
r3t3ch said:
I found the source of the deep sleep issue. It'll be fixed in the next build in about a day or so.
Edit: flash this boot.img from twrp (Install > Install Image > select boot) for a quick deep sleep fix
Click to expand...
Click to collapse
Flashed the boot image and now deep sleep seems to work just fine - thanks!
NEW UPDATED BUILD (DEEP SLEEP FIXED)
https://www.androidfilehost.com/?fid=24591000424955286
alexander_32 said:
NEW UPDATED BUILD (DEEP SLEEP FIXED)
https://www.androidfilehost.com/?fid=24591000424955286
Click to expand...
Click to collapse
I already flashed this boot.img, do I need flash the new rom ?
wizard_mini said:
I already flashed this boot.img, do I need flash the new rom ?
Click to expand...
Click to collapse
Likely not, we just made it like it should be.
wizard_mini said:
I already flashed this boot.img, do I need flash the new rom ?
Click to expand...
Click to collapse
Boot is the same; maybe the one posted earlier doesn't have holding volume down to go into fastboot, not sure. For the rom itself, I think the only big change upstream from cm13 was hexolibre.
SUPERSU INSTALLATION
NEW BUILD (6.25)
https://www.androidfilehost.com/?fid=24694152805485281
there seems to be an issue with the wifi, i have 5ghz wifi set to channel 149 and for some reason the tablet wont find any network with the channel higher than 48, any idea how to solve this? for me using a channel lower than 149 is not an option.
{
"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"
}
PAC-ROM is built with the best features out there!
Why choose among ROMs, when you have All-in-One?!
Double tap to wake (device dependent)
Double tap statusbar to sleep
Double tap navbar to sleep
Navigation bar customization
Lcd density tweaks
CM theme engine
Live lock screen
Lockscreen music visualizer
Weather notifications
Navbar arrows when typing
Editable power menu
Swappable back and recents buttons
Ambient display (device dependent)
Battery Statusbar tweaks
Battery bar with gradient color option
Clock customization
Lockscreen charging current
Network traffic monitor
Statusbar brightness control
Quick pulldown
Smart pulldown
Show/hide statusbar icons
Time contextual headers
By flashing this, you automatically void your warranty!
If your phone breaks, blows up,or runs away from you, do not cry to us!
Do not ask for ETAs!!
Download PAC-ROM and GApps
Reboot to recovery
Wipe data/factory reset
Flash PAC-ROM and then GApps
Reboot your device
Enjoy!
Download the latest version
Reboot to recovery.
Flash the latest PAC-ROM.
Reboot your device.
Enjoy the latest version of PAC-ROM!
Submit a bug report
Submit a patch
None for now
PAC-ROM Downloads
GApps
PAC-ROM Team
CyanogenMod
DirtyUnicorns
SlimRoms
Omnirom
Special thanks to all our Jenslave Maintainers (see Contributors list for all names)
PAC Graphix Team - Graphics, logos and images (see Contributors list for all names)
And of course, thank you for your love and support! *
Support us with these banners:
Help with server costs
Downloads
Download infopac_serranodsdd_MM.Beta.Unofficial_20160821-111524.zip MD5:177ac32611cd9684aa98d0cf95e69956
pac_serranodsdd_MM.Beta.Unofficial_20160904-100143.zip MD5:dc28344afb010d3087ac64313a68b2e9
pac_serranodsdd_MM.Beta.Unofficial_20160911-115106.zip MD5:037e4aeeec6242dcc5e7df16d8243df3
pac_serranodsdd_MM.Beta.Unofficial_20160918-120650.zip MD5:3ce06bf2ec7f064ab7ea8d8384b109f8
pac_serranodsdd_MM.Final.Stable_20161002-120455.zip MD5:2e0bba722bbd646885d7b7d5bae5c13a
pac_serranodsdd_MM.Final.Stable_20161016-104720.zip MD5:553555d30e29189f2a12978acf96767d
pac_serranodsdd_MM.Final.Stable_20161023-125045.zip MD5:9e1f88b0e1a5c7bceff68dba3fcc0111
pac_serranodsdd_MM.Final.Stable_20161218-095458.zip MD5:2a3bae2e705f0564ecbca914455ae6fc
Great to see you took this on! Are the extra features added in now?
Woow nice
csendre said:
Great to see you took this on! Are the extra features added in now?
Click to expand...
Click to collapse
Yes some features was added but nothing new, most roms had that features; last week PAC just become beta, they do their move before Android N arrive. Maybe you are able to test it? I appreciate some feedback.
Looking forward to support for other models. 9190/9195
tenshi_xp said:
Yes some features was added but nothing new, most roms had that features; last week PAC just become beta, they do their move before Android N arrive. Maybe you are able to test it? I appreciate some feedback.
Click to expand...
Click to collapse
Just tested it, all seems OK. I was a bit surprised by the size of the ROM, seems about 50MB larger than other MM ROMs. I wonder if it is because of the boot animation.
Call volume seems a little low, but this is typical since arco lowered it. You may want to consider reverting this commit, I have done so for my AOKP and CM builds because many people were complaining. If you want, you can use my serrano-common repo, this commit is reverted in it and also have a proper sized boot image included. I will keep the pac-6.0 branch updated.
Finally I see extra features, hopefully it turns into a great ROM by the time Android N surfaces
One more note, commit your changes to the kernel, it shows up "dirty" but runs well
csendre said:
Just tested it, all seems OK. I was a bit surprised by the size of the ROM, seems about 50MB larger than other MM ROMs. I wonder if it is because of the boot animation.
Call volume seems a little low, but this is typical since arco lowered it. You may want to consider reverting this commit, I have done so for my AOKP and CM builds because many people were complaining. If you want, you can use my serrano-common repo, this commit is reverted in it and also have a proper sized boot image included. I will keep the pac-6.0 branch updated.
Finally I see extra features, hopefully it turns into a great ROM by the time Android N surfaces
One more note, commit your changes to the kernel, it shows up "dirty" but runs well
Click to expand...
Click to collapse
The rom is bigger than others due is pic odex that give a fast first boot and updates also save space for user, of course not all apps in system are odexed, have some configs for installed apps you can see it in build prop. I will change the volumen values for the next release, the kernel just have KSM enabled you can see it in init.d. I will check your device tree, thanks.
tenshi_xp said:
The rom is bigger than others due is pic odex that give a fast first boot and updates also save space for user, of course not all apps in system are odexed, have some configs for installed apps you can see it in build prop. I will change the volumen values for the next release, the kernel just have KSM enabled you can see it in init.d. I will check your device tree, thanks.
Click to expand...
Click to collapse
Good idea, I did notice the faster boot but wasn't sure if just seemed to me because of the clean install
Sent from my GT-I9192 using XDA Free mobile app
Just notice a bug related to camera and save pics in external sd, that cm bug will be solved in the next release, just save the pics in internal sd atm.
Thanks, awesome work, btw this is my favorite ROM so I'm really happy to see MM now)
@tenshi_xp do you plan building for the lte model too?
Sent from my GT-I9195 using XDA-Developers mobile app
umuturunc said:
Looking forward to support for other models. 9190/9195
Click to expand...
Click to collapse
MikeL. said:
@tenshi_xp do you plan building for the lte model too?
Sent from my GT-I9195 using XDA-Developers mobile app
Click to expand...
Click to collapse
The idea was provide support for i9192 because that is my device, so i can test the release also do a build take long time for my pc is only 4Gb of ram. I will see in the future for untested releses for i9190 and i9195 but will take some time. Usually i do weekly releases but my internet is really bad now and im not able to sync the sources.
Update ready, Merged all CM, PAC and ARCO changes.
Revert Audio changes.
@tenshi_xp great rom, the features are great love the fast boot and boot animation. Everything works good except for some touch error. Tell me if this is my screen, or everyone is facing this problem. I like that it takes less space in internal storage than cyanogen. Great work!
NAmanpuri123 said:
@tenshi_xp great rom, the features are great love the fast boot and boot animation. Everything works good except for some touch error. Tell me if this is my screen, or everyone is facing this problem. I like that it takes less space in internal storage than cyanogen. Great work!
Click to expand...
Click to collapse
Can you describe the touch error?
After long usage, it starts to interrupt wherever I touch. Like if I am typing and I type any alphabet, it shows touches on notification bar. It usually happens after 3-4 hours usage.
NAmanpuri123 said:
After long usage, it starts to interrupt wherever I touch. Like if I am typing and I type any alphabet, it shows touches on notification bar. It usually happens after 3-4 hours usage.
Click to expand...
Click to collapse
Some times i notice that, turn the screen off/on helps. also you can try remix kernel and enable Zram I use 128Mb, if have some problems for install it, tell me I can upload a flasheable with Zram enabled by default.
Problem solved. Thanks
Hi. Great Rom.:good:
How can I run Xposed on this rom? Can any1 give me a link or something?!I've tried all the frameworks but none is good!!!
Thx in advanced
{
"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"
}
This is Cypher. An extension to pure Android. Cypher tries maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving Simplicity.
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.
*/
Features:
- Status bar Customization
- Quick Pulldown (Right, Left, Always)
- Smart Pulldown
- Network Traffic
- Clock Positions
- Etc.
- Quick Settings
- Enable or disable data on tap
- Layout Customization
- System
PowerMenu Custimization
And plenty more....
BUG
What's not working :
Nfc
SELinux is permissive
Download
OLD
Download(OLD)
Credits
CyanogenMod
AICP
PureNexus
AOKP
Dirty Unicorns
and more..
XDA:DevDB Information
CypherOS, ROM for the Moto X 2014
Contributors
linckandrea
Source Code: [url]https://github.com/CypherOS[/URL]
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-02-22
Last Updated 2018-08-12
Oh man another 8.1 rom this is awesome!
Thanks a lot. Time to test!
Enviado desde mi Moto X 2014 mediante Tapatalk
Awesome, great keep the lights burning for Moto X2
Archangel said:
Oh man another 8.1 rom this is awesome!
Click to expand...
Click to collapse
Hey did you try this ROM?/It's very good, battery seems slowly draining, i know it's early and later will confirm, please confirm if Torch is working if you installed?
The ROM is wonderful, very smooth, good battery, I'm really enjoying it, the best so far, I just had problems with the freeze on the lock screen, I decided to disable it, but I know you'll find a solution soon, looking forward to the next versions, Congratulations to all collaborators!
I am going to flash this tonight,,,how is the battery compared to Mokee?
zahidm said:
Hey did you try this ROM?/It's very good, battery seems slowly draining, i know it's early and later will confirm, please confirm if Torch is working if you installed?
Click to expand...
Click to collapse
zahidm said:
Hey did you try this ROM?/It's very good, battery seems slowly draining, i know it's early and later will confirm, please confirm if Torch is working if you installed?
Click to expand...
Click to collapse
its working
Archangel said:
I am going to flash this tonight,,,how is the battery compared to Mokee?
Click to expand...
Click to collapse
Look at SS it seems very good. 2d is obviously not correct but 14Hr are correct
Installed.
Opening the camera app takes a looong time loading.
Enviado desde mi Moto X 2014 mediante Tapatalk
Been using this ROM for 16 hours and I can say that it's one of the best Oreo ROM for victara. Everything seems fluid and stable. I got a freeze for some seconds while trying to wake my phone. I tried unchecking in pocket detection and it seems fine now. Love the extra options of this ROM. I like the double tap to sleep the phone anywhere on the screen. I will stick to this ROM.
does the sound stutter when you play games like AOV(Arena of Valor) ?
How is the temp and battery on this rom? I have noticed that some 8.1 roms have spikes of temp with moderate to high usage and some deal of battery drain even when not being used?
I just got to know one thing,,,how did you get the Now Playing for songs to work, even with the screen off? Now I really dont miss my Pixel that I sold LOL Great job!
Does it need Gapps?
Interesting read,,,the only problem is for me,,,Now Playing or Ambient Play,, does not stop. I am getting a huge battery drain partial wake lock with audio in,,,which I can only assume is this service. I have tried to shut it off in settings but it is still on. I cant seem to find "Luna Ambient Service" in my apps to force close it either? Is there another way to shut it down so I can only use it when I want?
Kinda weird that no one knows anything about these 8.1 roms or even bothers to answer including the dev for them?
Sapper Morton said:
All credits to Chris Crump:
"So after checking out Carbon Rom's port of the Google Now Playing feature, I shortly realized it's only working on Pixel devices. So initially I began working on getting it to work for any device, but I remembered my post from the other day about reverse engineering a Now Playing alternative.
So I did some digging and found a music app called Encore that has music recognition built it. I learned afterwards it was open source. You know what that means
So over the course of 8 hours I've been stripping the music recognition code out of out the app. It wasn't alot and very simple actually. Its very similar to Google's Now Playing except it pulls the songs fingerprint from a third party database and compares it to the one grabbed from the audio recording. I rewrote it into our own service called Luna Ambient Services (A spin on Pixel Ambient Services)..."
see more here:
https://plus.google.com/+ChrisCrumpSirhc/posts/M1ixDu4bMaG
Click to expand...
Click to collapse
Totaroz said:
Does it need Gapps?
Click to expand...
Click to collapse
Yes
Can't find the customisation options
Where are the customisation options like statusbar, swap navigation buttons, lock screen etc.? Otherwise fantastic ROM. Thanks.
I installed this ROM last night and its been 22 hours since I am using this.
Few issues I have noticed:
- As mentioned by @huatz84, phone was freezing for 5-8 seconds while waking it up from lockscreen. I turned off "pocket detection" as suggested by @huatz84 and now I do NOT have freeze wake issue
- Biggest problem I am facing is data connectivity issue. Phone does not connect quickly to mobile data connection. Though bar shows full signal with 4g, still speedtest/browser/youtube/apps says no connection. After trying for a minute or two, I am then able to open the links/videos. However, this problem repeats whenever I am using mobile data after few mins of internet inactivity. When it's connected, the data works fast. So it is NOT a problem with signal reception. Tried APN reset, airplane mode off/on, restart phone, 3g/4g toggle - but same results.
- Ambient sound keeps running. Still have not tried the solution that was posted before.
- Apps take couple of seconds longer to open up, especially when using the phone after sometime (might be something related to deep sleep)
What I love
- smooth transitions (except opening of apps mentioned above)
- like the new Oreo look and feel
- battery life good so far but need to monitor closely
- biggest thing--it has support for Moto gestures & wakeup on wave, which I love
If anyone has any suggestions for data connection issue, please let me know. I liked this ROM overall but if data connection issue persists, I will go back to 7.1
Andyvn said:
I installed this ROM last night and its been 22 hours since I am using this.
Few issues I have noticed:
- As mentioned by @huatz84, phone was freezing for 5-8 seconds while waking it up from lockscreen. I turned off "pocket detection" as suggested by @huatz84 and now I do NOT have freeze wake issue
- Biggest problem I am facing is data connectivity issue. Phone does not connect quickly to mobile data connection. Though bar shows full signal with 4g, still speedtest/browser/youtube/apps says no connection. After trying for a minute or two, I am then able to open the links/videos. However, this problem repeats whenever I am using mobile data after few mins of internet inactivity. When it's connected, the data works fast. So it is NOT a problem with signal reception. Tried APN reset, airplane mode off/on, restart phone, 3g/4g toggle - but same results.
- Ambient sound keeps running. Still have not tried the solution that was posted before.
- Apps take couple of seconds longer to open up, especially when using the phone after sometime (might be something related to deep sleep)
What I love
- smooth transitions (except opening of apps mentioned above)
- like the new Oreo look and feel
- battery life good so far but need to monitor closely
- biggest thing--it has support for Moto gestures & wakeup on wave, which I love
If anyone has any suggestions for data connection issue, please let me know. I liked this ROM overall but if data connection issue persists, I will go back to 7.1
Click to expand...
Click to collapse
Hi! No data connectivity here! Any workaround?
Thanks!
---------- Post added at 04:16 PM ---------- Previous post was at 03:26 PM ----------
patricio_torre said:
Hi! No data connectivity here! Any workaround?
Thanks!
Click to expand...
Click to collapse
Fixed it! Removed proxy and port values from wap details in APN.
Had to install footej for video recording to work.
Battery so far seems fine!
Excellent work here! Thanks!
{
"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"
}
Evolution X 5.X for the Xiaomi Mi Note 10 / 10 Pro [tucana]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
WiFi Display
SELinux Permissive
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Reboot to Recovery
2. Download the proper ZIP for your device
3. Wipe Data/Cache/System when coming from non-AOSP ROMs
4 Mount vendor (Needed for IMS patch)
5. Flash the ROM
6. Format data, reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper ZIP for your device
3. Flash the ROM
4. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
Android OS version: 11.0_r20
Security patch level: December 2020
Build author: Chemuski1
Source code: https://github.com/Evolution-X
Kernel Source code: GitHub-----Kernel Source
ROM Developer: joeyhuab
CHANGELOG
----------------------------------------------------------------
23/01/21
*Solved calling issue
*Device certified in Play Store
*Disabled power boost interaction
*FOD stability improved (For best result on enroll, use white fod icon, white theme and max out brightness)
----------------------------------------------------------------
21/01/21
*VoWiFi and VoLTE Fixed
*Added fake enforcing status
*Adressed SELinux denials
*Improved FOD
*Improved battery life
*Updated security patch
*Forced basic attestation for passing SafetyNet
*Now the ROM includes the firmware needed for work
-Don't ask about MIUI camera, because at this moment is broken.
-For having SafetyNet pass, you need to have Magisk installed and MagiskHide enabled. Remember to clean Play Store cache to ensure working properly.
nice job, thank you for your hard work
amazing rom
testing...
* google play store device not certified
Great job. Payments are working. Akorat fingerprint doesn't work as it should.
bmapilote said:
nice job, thank you for your hard work
amazing rom
testing...
* google play store device not certifiedView attachment 5166079
Click to expand...
Click to collapse
Use Magiskhide and clear Play Store data
Lukasek112 said:
Great job. Payments are working. Akorat fingerprint doesn't work as it should.
Click to expand...
Click to collapse
Fod is kinda buggy (needs time), testing off screen fingerprint now, when i get it more stable i would add update
Coming from rr 10 , should i follow steps above or i need to format data too?
Chemuski1 said:
Fod is kinda buggy (needs time), testing off screen fingerprint now, when i get it more stable i would add update
Click to expand...
Click to collapse
Updated to a room but my fp is completely missing
Hudinited said:
Updated to a room but my fp is completely missing
Click to expand...
Click to collapse
If you come from any 10 ROM, you need to clean flash the ROM
Chemuski1 said:
If you come from any 10 ROM, you need to clean flash the ROM
Click to expand...
Click to collapse
Just did it correctly yesterday, for one day usage i could tell that this seems to be most fluid rom for me despite a lot of customisations, fingerprint for me works well if light is cyan... Works just like it did on miui mutch-less .... Only parts of the system i could wish to be better are battery and charging optimisation.... Is there anyway to improve that? I mean implement miui charge and play with background tasks a bit ?
Overall best rom out there for me personally....
Hudinited said:
Just did it correctly yesterday, for one day usage i could tell that this seems to be most fluid rom for me despite a lot of customisations, fingerprint for me works well if light is cyan... Works just like it did on miui mutch-less .... Only parts of the system i could wish to be better are battery and charging optimisation.... Is there anyway to improve that? I mean implement miui charge and play with background tasks a bit ?
Overall best rom out there for me personally....
Click to expand...
Click to collapse
As you know, MIUI turbo charge is based on closed-source QC3, so no way to get 30W charging... But better to have 18W, It doesn't harm too much the battery.
About optimization, i'm working to reduce active drains changing some implementations (my first build for internal testing before this one drained a lot more of battery, remembered me a Galaxy S6, but with time hope Will get better).
My tip for now is to use Franco Kernel Manager and change little governor to powersave, with min freq ~700 MHz, improves the battery life
Chemuski1 said:
As you know, MIUI turbo charge is based on closed-source QC3, so no way to get 30W charging... But better to have 18W, It doesn't harm too much the battery.
About optimization, i'm working to reduce active drains changing some implementations (my first build for internal testing before this one drained a lot more of battery, remembered me a Galaxy S6, but with time hope Will get better).
My tip for now is to use Franco Kernel Manager and change little governor to powersave, with min freq ~700 MHz, improves the battery life
Click to expand...
Click to collapse
Im using smartpack with min Freq of cpu at 300 for both big and little cores... It really save standby drain but its only in deep sleep. Even if it's set to 300 that doesn't mean that it will stay there when it's not in deep sleep so , my thinking is that it would be great to reduce required time to enter into that mode... You know a lot already trust me.. we have been waiting for rom till about 2-3 weeks so you guys really helped us and thanks for that... About qc3 i have noticed that sometimes when i plug in the phone it goes to 3000 mah for a 10-15 secs and then revert back to 18w 2000 mah that's why i assumed that it is possible indeed. Looking at charger specifications it doesn't look like qc3, more like miui custom solution
Edit: my govs are schedutil instead of powersave
Hudinited said:
Im using smartpack with min Freq of cpu at 300 for both big and little cores... It really save standby drain but its only in deep sleep. Even if it's set to 300 that doesn't mean that it will stay there when it's not in deep sleep so , my thinking is that it would be great to reduce required time to enter into that mode... You know a lot already trust me.. we have been waiting for rom till about 2-3 weeks so you guys really helped us and thanks for that... About qc3 i have noticed that sometimes when i plug in the phone it goes to 3000 mah for a 10-15 secs and then revert back to 18w 2000 mah that's why i assumed that it is possible indeed. Looking at charger specifications it doesn't look like qc3, more like miui custom solution
Edit: my govs are schedutil instead of powersave
Click to expand...
Click to collapse
I play on powersave on little cores, schedutil on bigger ones... Saves me a lot on inactive, but on active i will look into telephony services to get better battery
Chemuski1 said:
I play on powersave on little cores, schedutil on bigger ones... Saves me a lot on inactive, but on active i will look into telephony services to get better battery
Click to expand...
Click to collapse
Actually i figured out what causes battery drain... Always on ambient display consumes about 9% battery for about 5hrs with modified gov
Hudinited said:
Actually i figured out what causes battery drain... Always on ambient display consumes about 9% battery for about 5hrs with modified gov
Click to expand...
Click to collapse
Thx to share that. I'll play with some things, like IMS and kernel governors to squeeze the battery better
Chemuski1 said:
Thx to share that. I'll play with some things, like IMS and kernel governors to squeeze the battery better
Click to expand...
Click to collapse
Turned off that AOD and than this happens
Hudinited said:
Turned off that AOD and than this happens
Click to expand...
Click to collapse
Okey, i'll work into that, thanks
Chemuski1 said:
Okey, i'll work into that, thanks
Click to expand...
Click to collapse
Look, im not bashing the rom im Indeed using it as daily driver, i just pointing out things that can be better over time so ve can have absolutely best experience possible
No new update ? Bliss got an update 2 days ago