Related
About a month ago some of you may remember my posts that I was working on a kernel. Here is my first public release. The whole thing works at about 95% or so.
==============
The advantages I notice while using it besides the normal issues associated with Eclair are as follows:
1. Memory management has changed (has good and bad effects) Good: when you fly through 45 websites the browser does not crash as it eats memory. Bad: when you blow through 45 websites the browser will hang (easy fix hit home, and use app killer to free memory from apps you are not using) (Personally I like not losing my place as I get lost in the web, it also will prevent apps from dieing in the background when you are using multiple apps at the same time, if memory gets low enough the OS WILL KILL the offending apps). I personally found Eclair for Fascinate to handle memory available worse than this kernel, and I find this kernel handles memory more like Eclair on the Moto Droid did, and the Moto Droid had far less memory to work with.
2. UI has a faster response vs stock kernels, the kernel is also running AS scheduling vs BFQ but I updated BFQ to run as well if you want to revert.
3. Internet Connectivity appears to be faster with those apps that properly use the API. Web browsing, CheezeBurger, youtube etc all load content faster (efficiently? / Maybe related to memory management?)
Want something added to this list? Post your requests, just please be reasonable If I like the idea I will try to implement it. Remember this is for kernel features not system ROM modifications.
==============
Issues to fix (ToDo List, I am working to fix these issues / Updated 01/30/11):
1. Investigate and address bluetooth connection issues [ Confirmed that this issue does not affect everyone / or all bluetooth devices ]
2. Investigate and address remaining data connection issues (Orbot activates and test show as using tor on normal websites, tor addresses fail to connect to servers, also Orbot is unable to de-activate [Confirmed]
3. Investigate and address remaining camera crash issues [ Please zip and send in logs from /proc/kmsg, specify if you used the volume control zoom or pinch to zoom ]
4. Improve on touchscreen timing for quick flicks on the first attempt without burning up processor time.
5. Investigate and fix stutter/crash on camera zoom followed by attempt to take photo.
Notice something that should be in this list? Please make a post describing your issue, remember to include the kernel version/rom and the steps you performed to reproduce the issue.
==============
For those doubting, this IS 2.6.29.6, I personally merged the code myself, IT IS NOT 100% COMPLETE. Some drivers still need merging, and the V4L2 code is not completely converted because Fascinate uses different (updated?) V4L code (compare Fascinate's Eclair to Eclair on AOSP)
If anyone wants to help bug hunt I will forever be grateful. I would like to finish squashing bugs in this in the next 2 weeks as I really want to attempt to work on a Froyo for Fascinate. Even if it uses Eclair code to run the only RIL code we have.
I also semi-blindly fixed about 50-100 coding problems in the Eclair Kernel, varied from not returning data from a function that should have, simple void definitions that were returning when they had no data to return and no function collected it. Correcting order of operations in if statements. Declaring data types that were vague (unsigned vs signed). You will notice it compiles a lot cleaner...attempting to fix the camera code nearly kills the camera completely, I am thinking the broken code dumps variables by accident that the corrected code does not.
Edit: I wanted to share a few things every dev (some of it specific to kernels) should remember when nights are long and sleep is a half world away.
1) Keep a backup of your most recent WORKING work safe, because it is too easy to....uh oh *[email protected]$
2) If you edit the config file, remember to make clean and make mrproper before you make, otherwise your still on your original config file (a copy of the one you actually edit .config)
3) Do not put comments to the right of options in the kernel config file...apparently they will be discarded (the entire option line, not the comment, you'll see it in your compile error message logs).
4) Automate the mundane, I have a nice build environment setup, I type one line and it will make a brand new kernel from scratch (I'll be sharing that later, keep an eye on this post)
5) Work with what you have, don't wait for someone else too. Somewhere, someone is working on something better, and tomorrow it will be out.
6) Laugh...at something...anything because lets face it, you make better decisions in a good mood, in a bad mood...entire trees (code) die, either from rm -Rf /work/crap//* or a sledgehammer to the motherboard. Which brings us back to the first thing to remember, where did you put that backup...different drive I hope?
Attached is a working kernel, it will have issues using DI01 (such as no vibrations), it works great with DJ05 ROMS and maybe DL09 system roms. At this time I can not recommend a DL09 system rom with this kernel, during my initial tests it appears to drop GPS and cell data connectivity frequently resulting in having to relock on GPS satillites, and losing data connections in networked applications.
I highly recommend the setup I am running, DL09 Radio, Son Of Skywalker Blackhole v2.4 and this kernel (if you can handle the few bugs that is, it is beta).
Please feel free to post bug reports please include detailed information about the issues, I AM NOT FIXING APP PROBLEMS. Please remember to only report kernel issues and information specific to the kernel crash. If an app crashes on other kernels and not just this one please do not submit a report. This kernel is NOT setup for debug info, I will post one setup with debug turned on later. Right now, play around with it and report your results! Enjoy and have a great time :-D
GITHUB: https://github.com/sirgatez/
Edit 1: I thought I would mention that I originally started with the JT1134 kernel source from late Nov. - mid Dec. and the Samsung Fascinate stock source (from Samsung's Opensource website) then I merged in source from 2.6.29.6 from www.kernel.org and from Cyanogen's 2.6.29.6 Eclair kernel. I stopped on 2.6.29.6 instead of moving higher because of 1 reason, once you step in to 2.6.30 there are major driver changes requiring a lot of double verification and back trekking....In a few words, it is lots and lots of work, and I think that jumping from 2.6.29 to 2.6.29.6 will help transition to the 2.6.30 (Froyo?) series of kernels because then the majority of the work is in restructuring the driver code (which would likely best be done backwards, from the system .h files, to the .c handlers, down to the device drivers) from Samsung to match that in the stock 2.6.30 set. Complexity will be reduced by a measurable amount
Notes 1: Samsung's Android code has some significant differences under the hood from AOSP Android code, I have not sorted it all out yet, but it is possible that without an AOSP stock system that a full kernel update to the current AOSP code may not be possible. There is a built in virtual CD driver for what appears to be hosting the ISO built into the base Samsung system image, I have not opened the image yet but it appears to perhaps be drivers? Also it does not sleep the SD card like standard AOSP does, attempts to do so will disable the SD card from use with no ability to remount without a battery pull. (This is in 3 of 4 lines of code that AOSP had that must be commented out from the Samsung kernel for this SD issue to be prevented). For those wanting it, CIFS and NFS are compiled modules in this kernel. The current kernel is not over-clocked, and does not have voodoo. It does support both with a kernel configuration edit required for voodoo with the proper init scripts, and over-clocking requires changing just a few files and recompiling, I did neither as I wanted a true comparison to compare changes against the original stock kernel. The kernel does have the BLN notification code built in. BLN, Voodoo, and Over-clocking code are not my own creation they are pulled from their respective creators.
REMOVED ALL OLDER KERNEL INFORMATION
Update RC3 v2.2.4-VooDoo/NoVooDoo: This is a minor/major (depending who you ask) bug fix to adjust the processor throttles. Think I've got it too set to a good sweet spot now, the peaks are steep and a little harder to climb but the falls are also quicker. After turning it my phone on with it last night and about 2 hours of use I went to sleep, wake up a couple times to silence various alarms (I wake to wake up, but I want to sleep a little more, can't I do both?), and these are the numbers that setcpu reports for time in state:
1.2Ghz = 0 (Had the phone thottled to 1.0Ghz for this test, but with 1.2 on it only uses it when it needs it, might could leave it on?
1.0Ghz = 164978 (Not such a big a number as before)
0.8Ghz = 292008 (much more reasonable than before, could be a little lower)
0.6Ghz = 117672
0.4Ghz = 114250
0.2Ghz = 104715
0.1Ghz = 2965562 (This is what I was aiming for proportionally for 0.1Ghz)
Remember these times are mostly from idling, the idea was to reduce clockspeed when not in use to save some juice. The phone might take a moment to wake up from idle, but once it is going you shouldn't feel hardly any difference between this and RC2. Bootup clockspeeds from your first 3-4 minutes will almost always remain in the top tier due to applications still loading, media scanner running, etc.
Update v2.2.4-VooDoo/NoVooDoo: This is a major fix kicking us out of RC status and into actual release. Now for the menu, prepare your appetite, for the appetizer we'll be serving a much demanded voodoo color fix, and voodoo sound fixes. Followed by a main coarse of throttle tweaks, throttle shift updates (these are new they decide what the next cpu speed will be when a throttle is exceeded up or down, every kernel to my knowledge including my last used the default for a 5 slot kernel, here is a true 8 slot), and for desert a reduction in logged touch screen data from the touch screen, and an additional surprise to everyone, a reduced cpu load when using the touch screen!
Apparently the touch screen had authority to force the cpu into any slot it wants, it defaulted to slot 1 (which was 1.0Ghz for Blazed, now it's 1.2Ghz). The result of which meant that if you pressed the touch screen your cpu load catapulted up to 1Ghz for as long as you touched it even if you only held your finger in one place with no apps open. I have changed that to only go to 400Mhz, we'll see how this goes, if anything we might bump it to 600Mhz, so far besides a slightly slower response when first touch my touchscreen after leaving it alone for a long period it doesn't effect normal use from one app to another. If your processor is already at 400Mhz or higher it will not up it further. You will find this kernel will likely end up being the most battery conscious you have ever seen, once you get things moving the speed follows. If you find this kernel has a slower response than you feel it needs let me know, because when I fixed the touch screen from blasting the cpu load through the roof, it through off my throttle settings some, now they may be too conservative, report back and we'll fix them if it is a problem. Ah yes, please don't forget to tip your waiter if you enjoyed the service... [ REMOVED - Aggressive throttles not configured for use without aggressive touchscreen driver ]
Update v2.2.4R2-VooDoo/NoVooDoo: This is a minor fix to correct the choppy feeling that v2.2.4 had, the choppiness was due to aggressive throttles to fight off the excessive high speeds the touch screen forced on. This should correct those issues. Unless I have another bugfix for 2.2.4, I will be adding 1.1Ghz in the next release making it a total of 9 slots. The higher speeds still need some tweaking, if your looking to hit benchmarks please set min and max to the speed you are testing, otherwise the throttle is trying to save you power that doesn't need to be used. But for everyday use, these settings should be good
Update v2.2.5-VooDoo/NoVooDoo: Voodoo sound is still broken, anyone have the patched files I could compare to? The screen should be about 15% dimmer than it usually is on the lowest setting (and scaled up from there to 100% at max), I found the dimmest setting just too bright in the dark for my self, and hopefully it will help me save a little extra juice because I usually use my phone on the lowest brightness setting anyway. Major fix to throttles, now they are better tailored to this many slots. Slots updated to 9, 100Mhz, 200Mhz, 400Mhz, 600Mhz, 800Mhz, 1.0Ghz, 1.1Ghz, 1.2Ghz, and 1.3Ghz. Increased processor voltages (my ultra low voltage was about 25uv lower in most slots than everyone else who has a uv kernel...I was a little too aggressive on that one). Update bluetooth driver, it should remain connected now, could someone please verify this? Stability has improved alot with the higher voltages and better handling of throttling for different situations. Several other pieces of hardware discover that have authority to play with processor. I capped highest touch screen processor forced at 600Mhz (the higher I set it the faster your battery goes, default stock is 1Ghz), and all other hardware at 1Ghz (not very many requests, but this is where rouge 1.2 use came from). If you had issues before except for camera zoom or data connectivity in apps give Blazed another try. The slightly higher voltages should improve a lot of the random issues people were having. You may see an improvement in cellular signal now, 1.3Ghz is also stable, but I wouldn't run it all day either due to heat generated etc...Well I hope everyone enjoys, this should be the best release of Blazed Yet!
Update v2.2.6-VooDoo/NoVooDoo: This is a major fix for cellular signal issues many people have been having, the issue again was related to timing and the kernel modules not waiting long enough for the modem to respond before proceeding with action resulting in errors that caused a disconnect or forced a modem reset (requiring a phone reset to regain signal). I found waiting too long only slowed the entire phone down, so I opted to go with nanosecond wait times, waits that short however are active and will warm the phone up some, please report back if it becomes an issue as I am looking for a better wait device than udelay, preferable more like sleep that doesn't keep the processor busy. There is some performance stutter in the phone on the high end of internet connectivity speeds, but your not going to be losing your connection either, I'll continue to attempt to improve on this issue later on. [ REMOVED - Timing further improved in v2.2.7 ]
Update v2.2.7-VooDoo/NoVooDoo: This is a minor for that makes a major difference. Improved timing for communication with GPIO/modem this should be the end of the majority of network connection issues. It was entirely a mailman problem, put package in box, check for package, package still there? no=do other stuff/yes=...wait,repeat at package still there?, etc. The fix is put package in mailbox, wait long, check is package still there? no=do other stuff,yes=short wait and check again...Hope this helps alot of you out, I am aware the touch screen is a little slow to respond and I will be looking into that issue. This little fix should also improve usable speed over v2.2.6 because the waits are better timed.
Update v2.2.8-VooDoo/NoVooDoo: Timing is everything with electronics and this post...as promised today before 11:59pm is v2.2.8. Working Voodoo Sound v4, updates to the dpram/dpio communications again improving connection stability, if you lose your connections please report back (permanent loss requiring a restart only, fluctuations are different issue). Throttles set a little more aggressive about 5% so (helps ease on light loads), stepped up the first throttle jump from 100mhz to 400mhz (touch screen snaps back now). Dropped the 1Ghz permission for misc hardware to 400mhz if you have issues let me know, touch screen retains it's 600mhz permissions. Also screen brightness is reducible to gamma 1 brightness 10, typically reserved for battery about to fail status (I found the lowest setting just too dang bright). Enjoy everyone! I've been hammering away on this since 7am this morning and only had voodoo sound working about 9am. Thanks to JT1134 for his prebuilt kernel containing voodoo sound v2 working, adding v3 & v4 was a snap after that. Please report if you have any issues with it and remember you MUST be using the new voodoo sound app from the market.
Update v2.2.8R2-VooDoo/NoVooDoo: Another dpram timing adjustment (will lower your upload speed a little but will be more stable in operation, down speeds should be around 200KB down 44KB up on a good connection). Adjusted 1.1Ghz dividers per nemesis (not sure that it looks right, appears to get better benchmarks than 1.2 now will follow up on it). Made throttles a little more aggressive, 2.2.8 looked all over the place and having difficulty controlling processor use.
Update v2.3.0-VooDoo/NoVooDoo: Alot of work went into fixing dpram.c and multipdp.c it seems they were incompatible from the very beginning resulting in alot of ril issues and stability problems not just on my kernel but others as well, especially with nonstandard clocks and multiple slot kernel. I also added a fix to the framebuffer courtesy of JT1134 that has long since been overdue but a rare bug most probably have never seen. I fixed all the timing in dpram.c I also fixed the non-matching buffer sizes for multipdp and dpram (they talked to each other using different sized buffers...come on?!) There are still some bluetooth compatibility problems and the camera may still crash on zoomed photo, but I'd say it's 100% out of Beta! Enjoy! :-D I will be working on a Froyo kernel so stay tuned folks!
Update v2.3.0R2-VooDoo/NoVooDoo: Minor fix to help prevent dpram crash by handling and disposing of invalid commands sent to dpram, should fix seeming random lockup. [ Edit: corrected incorrect version numbers in original v2.3.0 series xda posts, thanks to s44 who caught the error, this does not affect kernel downloads, this were named correctly ]
Update v2.3.1-VooDoo/NoVooDoo: I reduced the delays in the ce147 camera driver, repairing the dpram driver resolve many of the seemingly random issues that had once plagued Blazed. Also a special treat for all you Blazed users, a new voodoo sound option that I have named "HEADPHONE_STICK" essentially the option when enabled (per boot) will force all audio directed to the external speaker to be instead directed to the headphone jack if the headphone jack has a plug in it. I find it excellent for not disturbing others around me with notifications when I would rather the phone be silent but I have headphones plugged in. Also excellent for using that awesome amp you have in combination withr you fascinate to wake you up in the morning. I will be contacting the maker of the Voodoo sound app in the market to get this option added to his application for quick and easy access. Also a major rework in the way kernel modules are loaded, all modules non-essential to booting are now stored in /system/kmodules. So if you reflash your system folder reflash your kernel or it may not boot, a quick browse will reveal what modules are kept there, I have more readily compiled and will release a separate "modules only" update.zip for those interested. By moving the modules it will allow for more options that are only available for including in the kernel boot image.
Update v2.3.1R2-VooDoo/NoVooDoo: Reverted some of the CE147 delay changes, reducing all of them caused some minor camera instabilities. EXT3/EXT4 moved back into the kernel, for some reason even with it's depends loaded ext4 doesn't load correctly as a module (resulted in broken boot on voodoo, now fixed). Also You MUST USE RED CLOCKWORKMOD TO FLASH IF USING VOODOO, you may use green clockwork only if Voodoo is NOT enabled due to the fact that some modules required for bootup are now stored on the system partition and if your using Voodoo only red clockworkmod has access to it. Also if you flash a different system or restore a backup you must reflash the kernel to ensure your modules are up to date. Also is a new file KMODULES-FULL contains all of the modules I have been compiling for Blazed thus far, several nifty ones but I have not setup any of the configs to use them, anyone versed in Linux command line can utilize them or setup scripts to use them, have a look inside the zip too see what there is to play with, request and I will add more if the module could prove useful to others. Several of the modules in FULL are also in the Kernel due to being required for startup redundancy (such as the 3D video/LCD drivers etc, which without a Android system folder, Android won't boot, nor will it boot without these modules so system seemed like a reasonable place to store them. The kernel/initramfs file is less than 6MB with Voodoo due to moving these modules to the system folder. I plan to add ClockworkMOD as soon as I have time to test it, then Blazed will also work for Recovery.
The Great Voodoo Debate: I have also been benchmarking Blazed against stock, to determine the difference Voodoo has on the kernel, so far it would appear Blazed has modifications either in the file system handling or the manipulation layers that are nearly equal to negating the speed lost to RFS's use before Voodoo or EXT4 is even brought into the equation. Just compare Stock vs Blazed (novoodoo) using 'RL Benchmarks SQLite Performance" from the market. A difference of 33.246 seconds in favor of Blazed, my preliminary results are (124.944 Seconds Blazed-NoVoodoo) (158.19 Seconds Stock) using the same exact system install less than 20 minutes apart between boots, with over 300 applications installed and several running like any other day. Based on this alone I find Quadrant is at least partially flawed at measuring proper I/O transfer timing, and I would NOT rely on it for an accurate benchmark in regards to I/O at this time until the issue is resolved by the Quadrant team. Voodoo does not produce the outlandish high scores that Quadrant makes out that it does, and Blazed is plenty fast in I/O even with RFS in use as shown by these preliminary results that any one of you can verify on your own using the "RL Benchmarks SQLite Performance" application, Voodoo does improve transfer compared to RFS in my tests but I am still putting together the results on Blazed NoVoodoo vs Blazed Voodoo. But as far as a 1800+ or 2000 score, so far my results say it just doesn't look realistic...sorry guys. On the flip side, if there is an error in my kernel causing a misread on the score you guys are welcome to help me find it and I will push the correction, but right now it looks like the issue is in how Quadrant measures I/O time, and I think non-atomic disk writes are the reason for the high scores, theoretically they would return claiming data is written to disk almost immediately when in reality it is still in memory and the kernel will write it to the disk at later time without the write time being considered as part of the benchmark (Google: write-caching, also known for providing significant performance improvements over atomic-writes).
If you appreciate Blazed and enjoy using it, please consider making a donation. Thank you for trying it out and have fun!
My initial impression after playing around with it for 15 minutes:
Seems to have given my phone new life/snappiness back that it had when I first installed super dark rom and stupidfast 1.54. My phone seemed to be bogging down lately. The internet definitely feels quicker too.
So far so good!
will try, thank you for the release.
Great work!
Sent from my Galaxy-S Fascinate
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Great work, the kernel seems to have given new life to my test fascinate! ADB does however appear to be dead (I got error device not found every time I tried to connect) Other than that I have no complaints, keep up the good work
That is very odd, as I have not had any issues using adb. Please reload your drivers to be safe and double check debug mode has not accidently become disabled. I wired up my fascinate just now and confirmed that ADB is working. (It was invaluable in working with the camera crashes). Also it maybe related to a conflict in the system rom vs the kernel. I personally have not have any issues with DI01 Fascinate stock, and everything worked great using DL09 radio, DJ05 system from SonOfSkywalker (BlackHole 2.4). Right now I am running DL09 Radio, DL09 System Rom from SonOfSkywalker v3, and my kernel from this post, thus far no issues. I am using Ubuntu v9.04 to test right now, and not windows to confirm that ADB is working. I will check on windows later today when I have a chance.
anyone else having an issue with bluetooth? It says "Turning On" but does not turn it on just reverts back to "off" status.
I still have DJ05 modem and on blackhole 2.3 something but updated market and swype maunally.
Camera force closes when you go to zoom in.
Sent from my SCH-I500 using XDA App
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
wizang said:
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
Click to expand...
Click to collapse
Yes, you MUST disable voodoo before using this kernel. I will put together a voodoo and OC flavor of this for those interested later. As of now I have only been working with non-OC and non-Voodoo in this kernel to gauge how the work changed the experience.
Edit: Oh yes, it uses the default partition scheme. It is a goal of mine to eventually change the formats of partitions (similar to voodoo) but keep the layout, it is my thought that doing so provides the largest window of compatibility between stock Samsung/VZW Roms and custom Roms. With a proper recovery, the change could be performed and backups and restores would work no matter the format of the internal media as the layout remains the same.
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yea my phone is not recognized by the computer either, even after a restart.
Naturally I double checked usb debugging and the drivers (adb connected to my white fascinate just fine and I made a jump back to Geeknik's test kernel to double check that something hadn't died in ole blacky and it registered there as well) I wonder if its just this fascinate (as it has had a laundry list of its own issues). This phone is running Superclean DJ05 completely stock and was fresh off a complete wipe and restore
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can confirm that I am unable to access the phone via Samsung's drivers using Windows XP. [Added this too my list]
Wireless tether does work in case you need it, that is why I hadn't noticed this issue. Good catch!
I really like the transparency of your work. It's refreshing to actually read about the process you're working on and the way you explain it definitely makes seems like you have a good grasp of what's going on. I can never quite tell with the other devs. Anyway good luck!
FDro said:
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Click to expand...
Click to collapse
Agreed! If they can get GB running nobody is going to be interested in Eclair or Froyo.
I like the sound of this kernel. Imma flash it when i get home. Looking forward to seeing the OC version
SCH I500 Super Clean v.9 DJ05 Revolution 3.6 OTB oc'd lv1200 Voodoo5
2 SirGatez.
It sounds like you are pushing towards performance optimizations. Have you checked supidfast sources? I tried it before geeknik left and it was significantly faster then stock. May be you can get something from him.
I really appreciate what devs do here, cool stuff! However I do not understand why that much talent spend in vain... Every developer has his own build, mods and bug fixes. Is this real open source spirit to have so many versions? Looks like brownian motion to me.
Now, you can say that I'm free to do it on my own etc, as other devs pointed here. But, full fledged development it not for everybody by various reasons. I hope it is obvious. Would be nice to see some consolidated development! Then it will be much more easy for mere mortal to contribute to that product. We all have same phone!
Once again I do not want to upset anybody.
bendbowden said:
Great work!
Sent from my Galaxy-S Fascinate
Click to expand...
Click to collapse
Also, great write up! I will report back if I notice any bugs not mentioned above.
The point of this thread is to put together a list of optimizations that can be done on the stock rom with root access. I figured there would be others like me who can't unlock (or don't want to) but now can root who might be interested and all contributions will be added.
At the end of this the Prime feels much faster. I think most of it can work for the TF300 and TF700 too. Thanks to so many out there who make this possible and I appreciate all feedback in comments.
NOTE: This involves rooting your device and doing dangerousish stuff. I am not responsible if your Prime softbricks or if you have trouble installing updates. If you mess up and it softbricks you might lose all your data on the Prime. My official answer to updates is that every step has backups or checkboxes, so just undo everything after the pre-amble before you update.
If a tweak is done wrong and you can't boot, unbrick via these directions (data will be lost!):
Download latest firmware from Asus site.
Unzip this file once - it contains a zip inside it. Rename this zip to EP201_SDUPDATE.ZIP
Copy the file to the root of a FAT32 formatted MicroSD card
Turn the tablet off via the power button.
Now turn it on holding down the Volume Down button on the tablet
In a minute you will be in the recovery screen. Hit volume up.
Wait for it to get done. It can take a while.
Pre-Amble:
First thing, update to the newest Jellybean Asus has given us and root it using this method (thanks Morlok8k and djrbliss and sorry again Morlok8k).
Install Voodoo OTA Rootkeeper and protect that root:
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Install Quick boot to get an easy way to reboot:
https://play.google.com/store/apps/...medium=appbrain_web&utm_campaign=appbrain_web
Now lets optimize:
1. Get Rid of Bloat (Undo this step before installing updates)
Use Titanium or the built in disable function under settings to freeze some of the apps. This gets back a lot of your RAM and cuts down on the boot time. Here is what I have disabled/frozen (don't disable something you use), but note some can only be disabled with Titanium:
@vibe fun center
App Backup
App Locker
Asus Email (I don't use it)
Asus FAcebook Poster
Asus MyZine
Asus Sync
Asus Weather
com.asus.pcsynclauncher
com.asus.quicksearch
com.asus.youtube search
Email
Exchange Services
Google Play Books
Google Play Movies and TV
MyCloud
MyDesktop
MyDictionary
MyLibrary
Nvidia Glowball Demo Installer
Street View
Supernote
Talkback
Webstorage
Zinio
Click to expand...
Click to collapse
2. Install an Ad blocker.
My choice is Adaway:
https://code.google.com/p/ad-away/
This will speed up browsing.
3. Disable FSYNC
(HUGE PERFORMANCE BOOST BUT SOFTBRICK RISK IF YOU DO IT WRONG)
First of all, before we get started know that disabling FSYNC has some risks. But its the single biggest tweak you can do. Will let you update or install apps and still do something else.
Secondly, please go here and thank eminent1410 for inadvertently fixing our Primes. He did it for his OPTIMUS Z ROM but we benefit!
http://forum.xda-developers.com/showthread.php?t=2203345
Steps to install:
Download the zip file named FSYNCFIX.zip attached to this post and extract the files in that zip to your Prime.
Open Root Explorer and go to /system/lib folder. Rename libsqlite.so and libsqlite_jni.so to libsqlite.so.bak and libsqlite_jni.so.bak respectively.
Copy the libsqlite.so and libsqlite_jni.so files that came from the attached zip (using root explorer for example) to the /system/lib folder (Mount that folder as RW if necessary).
Set permissions on the two files to rw-r--r-- (picture of what it looks like attached to post)
Reboot.
If something went wrong your prime will not boot but will be stuck at the booting screen. At that point use the directions at the top of the post.
CREDIT: http://forum.xda-developers.com/showthread.php?t=1691669
4. Fix Entropy
This is a big deal to fix lagginess. Confirmed by richardmlea to improve the browser. Also helps with apps that have lists in my experience.
You can get Seeder from the Play Store and support the developer (or search and find the thread on XDA):
https://play.google.com/store/apps/details?id=com.lcis.seeder&hl=en
Run the app, turn on everything and tell it to start at boot.
5. Replace build.prop (Undo this step before installing updates)
(softbrick risk and might cause problems with upgrading if not undone)
Credit to MR.WOOKIE for the base I used to make the build.prop. It improves all sorts of stuff in little ways- network improvements, UI improvements, JPEG viewing improvements.
To install:
Download the attached correct (US or WW depending on what Prime you have) build.prop.zip files from this post and extract it to your Transformer.
NOTE: Currently the attached build.props are only for the TF201. Will brick other Transformers.
Using Root Explorer or something, go to your /system folder and find build.prop and rename it to build.prop.bak
Then copy the build.prop file from the zip to the /system folder and change its permissions to rw-r--r-- (picture of what it looks like attached to post).
Reboot
6. Install the Pimp My Rom app (Undo this step before installing updates)
NOTE: This step must be done AFTER step 5 if you are going to do step 5. If you don't do step 5 the using Root Explorer or something, go to your /system folder and find build.prop and rename it to build.prop.bak before using Pimp My Rom.
Get it here:
https://play.google.com/store/apps/details?id=com.androguide.pimp.my.rom
I did a lot with this app, give it Five Stars!
Under Tools:
First I activated "Universal Init.d Support". Then confirm it works
Entropy generator is much like Seeder, but not as good.
Under Tweaks:
Under "Network and Internet" I enabled "Wifi Connect Speed Tweak" and "Faster Media Streaming" at the top part. Under Init.d ans Sysctl Tweaks I enabled "avoid Time-Wait," "Block Redirects," Block Source-Routing," and "IPv4 Tweaks." Now the play store doesn't act up any more saying it can't load.
Under "Android Features" I enabled "Hardware acceleration," Force CPU rendering,"
Under "Miscellaneous Tweaks" I enabled "Optimize sqlite Databases," "Ext4 File-Systems tweaks," Internal SD-Card I/O Tweaks," External SD-Card I/O Tweaks," and "Zipalign all APKS at each boot." These changes make a huge difference in the performance of almost everything.
7. OOM and SD cache
This will help responsiveness and RAM management. As per nhshah7
Download Kernel tuner:
Go to OOM and set it to 1000 aggressive.
Go to Misc and set the SD cache to 4096
8. Wipe the Dalvik Cache
Thanks to pooblej for this one.
Download this app:
https://play.google.com/store/apps/details?id=com.j.y.daddy.customizer
Open the app.
Go to "SET"
Select the "Wipe Dalvik-Cache" option.
It will then reboot with a pretty long boot time.
9. Trim
Do this last.
Use the lagfix program to TRIM your Prime:
https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en
Just open it and hit Run.
Extra Optional Stuff to do
10. Install Browser2RAM
http://forum.xda-developers.com/showpost.php?p=34885711&postcount=58
Let it run as root. Can work with stock browser or Chrome. Thanks qskile for pointing it out and t3hSteve for the apk.
Personally I think this eats a lot of RAM and is not needed when you do all the other tweaks, but it is FAST! Hard to resist probably.
11. Install and use PieControls
These are all the rage now. Getting this feature is as easy as installing this apk to use the LMT Launcher:
http://forum.xda-developers.com/showthread.php?t=1330150
Here is a good guide that goes over setting up this feature with pictures:
http://highonandroid.com/android-ap...rooted-android-smartphonetablet-lmt-launcher/
Things left to do:
1. Data2SDish hack
2. Volume boost that works with Jellybean (Don't try anything Beats it won't work)
3. V6 SuperCharger - Can cause more problems than solutions unless done right and I need to research more. Kernel tuner goes a long way.
Thank you in advance for any and all responses or thanks.
I also wanted to know about the build tweaks now possible if we can root stock ...
I will let you know what I discover. So far the biggest boosts are browser2ram and freezing all the Asus bloat. It already feels like a different tablet now.
Set performance mode to performance. Enables it to clock at 1.4 ghz (wish we could go higher with stock kernel!)
download Kernel tuner, go to OOM, presets and set it to 1000 aggressive. Also in kernel tuner, set SD cache to 4096.
I didn't find seeder to actually help. Also download Rebooter from the play store and "Hot boot" if you slow down. It essentially kills all non-system apps.
Haven't tried the other apps you linked to the play store. My prime FLIES now
Edit: also have not tried build prop tweaks. Don't see a need just yet, might affect future OTA upgrading as well.
EDIT: Talking about performance, for browsers, I use dolphin with dolphin's jet pack. Doesn't have flash, but sunspider shows this to consistently be the fastest between any other browser on the market. Stock and Chrome come in slightly behind (in that order).
Maybe it is just the euphoria of getting root but seeder works great for me. first thing i installed after rooting. The stockbrowser and xda homepage (showing all devices) would crash the browser every time (stop responding, and require restarting) with seeder it is fine. I even uninstalled seeder to test if imagined the effect but didn't. For me seeder makes the stock browser fully usable. I dont think the browser has stopped responding since i installed seeder.
I will have a go at some of the other tweeks now.
poofyhairguy, Good idea to compile a list of tweeks, maybe you can keep the OP tidy and list and tweeks that other posters suggest in the first post.
One from me that you have already mentioned, to increase the volume get Volume+ from the play store. There is a free version and a paid version that claims to increaseit more. Maybe someone can suggest something better for the same job and completly free.
Also there was/is an app or tweek to improve the touchscreen persission and sensativity. Anyone know what thats called?
More idea's....?
Afternoon all, I have done most of the tweeks and i am seeing excelent gains in smoothness and responsiveness.
Quick question, i have disabled loads of the bloat apps using settings/apps/all selecting the app and selecting disable, but is there any advantage using titanium backup to freeze or remove the bloat app's?
richardmlea said:
Afternoon all, I have done most of the tweeks and i am seeing excelent gains in smoothness and responsiveness.
Quick question, i have disabled loads of the bloat apps using settings/apps/all selecting the app and selecting disable, but is there any advantage using titanium backup to freeze or remove the bloat app's?
Click to expand...
Click to collapse
Don't remover, just freeze it. If you need to OTA, it checks to make sure all the Asus apps are still there.
Also interesting tidbit on seeder. I'll try it again.
As far as changing governors, I could never get it to stick on anything other than interactive...?
Sent from my HTC One X using xda app-developers app
richardmlea said:
poofyhairguy, Good idea to compile a list of tweeks, maybe you can keep the OP tidy and list and tweeks that other posters suggest in the first post.
Click to expand...
Click to collapse
Good idea. I will also add the stuff I discovered.
richardmlea said:
One from me that you have already mentioned, to increase the volume get Volume+ from the play store. There is a free version and a paid version that claims to increaseit more. Maybe someone can suggest something better for the same job and completly free.
Click to expand...
Click to collapse
Looking into it volume plus no longer works in jellybean. So something else is needed.
I have updated OP with new findings.
Just PMed a mod to move this to General. I'll try Pimp My Rom when I get some time this week and report back if it works or not!
Please keep this list going - Everyone will need to know these things as more people root.
pooblej said:
Please keep this list going - Everyone will need to know these things as more people root.
Click to expand...
Click to collapse
I plan to. I am going to keep working on it until we get as much as we can get out of it. Plus I have crosslinked this guide on the TF300T and TF700 forums.
OP has been updated with my recent attempts.
Nice tweaks without root.
Maybe some things will work with my s3 because my Prime is rooted from the first second
Kind of slow at work tonight so I know what I'll be doing. :good:. Any benchmark numbers before and after doing all this?
I used to use Volume + but is seemed to quit working on JB. I am now using Music Volume EQ. It may not boost your volume as much as Volume + but it works well and I like the EQ, virtualizer and Bass boost functions. I just wish they would optimize their interface for tablets, it's kind of small for a 10 inch screen.
Music Volume EQ
One thing I've noticed with Music Volume EQ is sometime you have to open the app (or press the widget) for it to turn on. I haven't tested it if this is just after a reboot or it happens randomly.
EDIT - At this point all I can is WOW. This stuff really works. Pimp My Rom is the bomb. I've done everything in the list but install Seeder. With Pimp I don't think it's necessary but I may try it later. Also I can't get the CPU manager to boot into Performance mode with Pimp. Not really a big deal since ever since I've had my Prime and rebooted the first thing I do is to switch to Performance mode. It's like second nature to me now. I'll keep messing with it, it's probably something I'm doing.
Thanks for this very good Thread!!!
Thanks for this guide. At least I got root again easily. I did all the tweaks, lets see is the device any better.
theandies said:
Any benchmark numbers before and after doing all this?
Click to expand...
Click to collapse
A lot of these improvements show up in feel, not in benchmarks. But I might add some to the OP. Glad it it helped.
I am going to have a big update tonight. Got FSYNC turned off, almost done with build.prop tweaks plus maybe another surprise or two.
poofyhairguy said:
A lot of these improvements show up in feel, not in benchmarks. But I might add some to the OP. Glad it it helped.
I am going to have a big update tonight. Got FSYNC turned off, almost done with build.prop tweaks plus maybe another surprise or two.
Click to expand...
Click to collapse
Can't wait! I am now rooted and working through the list!
How did you turn off Fsysc? do you know what the risk is? ie if an app force closes and the TF201 reboots - ie is it safe?
Please let me know your thoughts...
pooblej said:
Can't wait! I am now rooted and working through the list!
Click to expand...
Click to collapse
If you are going through the list now please don't install Seeder ( I found something better I think) and hold off on Pimp My Rom or you will have to redo it.
I am going to make a TON of changes to the guide tonight.
How did you turn off Fsysc?
Click to expand...
Click to collapse
I found a libsqlite.so that was compatible. I promise as soon as I make sure it is safe today I will post how to do everything.
do you know what the risk is? ie if an app force closes and the TF201 reboots - ie is it safe?
Please let me know your thoughts...
Click to expand...
Click to collapse
This post basically sums up the risk:
http://forum.xda-developers.com/showpost.php?p=27122865&postcount=42
I think it is safe enough given that. The ROMing community here has bought into it 100% and so if it was a big deal it wouldn't be used. I never would make my life depend on my Prime.
And I almost can't explain how much faster it is with FSYNC off. Like everything else in the guide put together doesn't do as much. It is amazing.
poofyhairguy said:
First thing, update to the newest Jellybean Asus has given us and root it using this method (thanks flumpster).
Click to expand...
Click to collapse
My name isn't flumpster...
If your going to credit someone, either credit my name correctly (Morlok8k) or the original creator of the method (djrbliss).
Morlok8k said:
My name isn't flumpster...
If your going to credit someone, either credit my name correctly (Morlok8k) or the original creator of the method (djrbliss).
Click to expand...
Click to collapse
Sorry about that. I will change my guide now.
Look in the link below to consolidate. Thanks
http://forum.xda-developers.com/galaxy-s6/help/app-potential-bloat-safe-to-freeze-t3161615/post61958829#post61958829
thread pinned..interesting will look tomorrow evening again..will sleep now
Sounds good
Look at the link in the first post to see what I have running.
MementoM said:
I did it's really awesome, I thank you. It's a tad hard to determine exactly what was disabled as you were unable to provided a list and I'm unable to piece together all the posts as to what truly was uninstalled/disabled here is what I have always running at the moment. Any advice?. Is it safe to say everything that's running here and not in your screenshot is safe to disable?.
Click to expand...
Click to collapse
Yes, but if you disable the Catch people than I believe your Edge feature will not work. I don't use it but if you do keep it. Also if you don't use the factory email client you can safely disable that as well and not have any email issues if you use other clients.
What carrier are you on? If you reboot and have just those loading on startup you should be near 1.5GB. Now there may be events which trigger apps to run behind the scenes and there are apps to let you see what is running at startup and give you the ability to change their behavior based on specific events, however I'm not sure if those programs really work as advertised for modifying the app behavior. Tmobile users have had all kinds of memory management issues, there are mods you can make to modify the memory management aggressiveness but I have not found a need to make those changes, also with 5.11 it looks like they made it even more aggressive but again on boot up you should be closer to 1-1.5GB free RAM.
[GUIDE][LP-MM-N][CM-CAF-AOSP] Workaround for "apps with access to usage data" bug!
There are A LOT of (even good) LP/MM ROMs out there that has the "apps with access to usage data" bug (it seems some Nougat too...).
There are two main types of this bug:
- the first, more spreaded on "branded" LP ROMs is that this menu has fully removed from Settings at all (should be inside Security section, as last choice available...). This happened on some old Samsung & LG ROMs if I don't go wrong...
- the second, more spreaded on MM (& N?) "cooked" ROM as CM, AOSPA, RRmx, etc... is that apps reported inside the menu are not the ones eventually needing this security settings introduced with LP, BUT totally RANDOM and, worse, quite ever, the needing ones are missing, limiting this way their complete functionality...
I'm *quite sure* this could be fixed by an Xposed Module but, as of today, I've not find one and nobody seemed able to realize one! :crying:
This bug is very discussed on the web, since it limits hardly the functionality of a lot of "technical apps" like many antivirus apps (e.g. Sophos, Malwarebytes...), anti thefts (e.g. Avast...), battery stats (e.g. Accubattery & 3C Battery Stats Pro...), battery savings (e.g. Greenify, Leandroid...), blue filters (e.g. Eyefilter...) and so on...
All these can't fully work or work at all since of the "apps with access to usage data" bug.
Many people at the end decided to switch from good ROMs only since of this bug, because for advanced users this is surely a "major one".
And nobody, as of today, was able to fix/patch it or to find a workaround.
I've so investigated on this with the intention to find at least a workaround for this (a fix/patch requires at least an Xposed module to be realize and this is out of my actual possibilities...).
At first I've found that granting that permission could be done even via adb and/or terminal: having root permissions (I'm talking to advanced users, OK? You have root for sure... ) there is a comand to grant permissions to apps, in this specific case it is:
>su
>pm grant <package_internal_name> android.permission.PACKAGE_USAGE_STATS
This probably should work fine on ROMs where the related settings menu has been removed, BUT on "cooked" ROMs affected by the bugged menu this simply doesn't work: command is accepted with no error BUT... it simply doesn't change anything!
This is interesting for who eventually will investigate on this bug, since it is clear that it is not a "cosmetic" bug related to settings submenu functionality, but it is something more core related since of the commands not working too...
At the end I've found a really *great* app, developed probably for other needs but that I've found it working perfectly as a workaround for this issue too! :highfive:
The app is App Ops or, better, one of the numerous apps with that name present on Play Store (most of not working at all... ), so you can search it as rikka.appops
Starting first time this app, it asks if you have root or not, to decide how to install it (yes, it seems able to work without root too, but functionality with our needs has to be confirmed), so, after have chosen "root mode" it will scan and show complete app list.
Then you have to go to your limited-since-of-the-bug-app ant tap on it. It will show you a list of the permission of that app and their actual status.
You have to go to get usage stats permission and you will find it indicated as "Default". Tap on it and simply change to "Allow", then exit.
Since now (even without a reboot!) your app will ignore (wrong...) system settings and will work fine as you have granted normally that permission. :highfive:
I've tested it with a lot of apps and all work fine after this workaround. :good:
I guess this could be useful to *many*!
P.S.: please note that on bugged settings menu nothing will change... but, who minds!
Thank you so much for this information! This is exactly what I was looking for and now I can use all my apps as they are supposed to be used:good::laugh:
tengwer said:
Thank you so much for this information! This is exactly what I was looking for and now I can use all my apps as they are supposed to be used:good::laugh:
Click to expand...
Click to collapse
You are the welcome... on what ROM did you applied this?
It was the Marshmallow version of Resurrection Remix.
been looking for this for a last few days... and actually find it now...
thanks.
you should add a screenshot of the step by step to make it easier to understand for some people, its just my opinion.
I was trying to find another ROM.. But there's nothing like RR man! So i'm restoring my backup & will try this ASAP. Really hope it'll works THANK YOU! Link : https://play.google.com/store/apps/details?id=rikka.appops&hl=fr
thanks man, you have saved me from a big app security problem.
I am using rr rom. Surprisingly, permission in this respect is not found in privacy tab in settings app on the rom.
Any way, thanks a lot??
It worked.. thank you saviour
enetec said:
The app is App Ops or, better, one of the numerous apps with that name present on Play Store (most of not working at all... ), so you can search it as rikka.appops
Click to expand...
Click to collapse
Thanks so much for this! This solved a permission problem I ran into on a Kindle fire 8.
PSA for @Wizballs and any other miPad 4 owners of the WiFI-only model...
Most of us have probably been looking for a ROM that is actively and officially developed that doesn't have the bug where it looks for the non-existing SIM card and drains the battery during standby. I'm happy to report that MoKee appears to use a different base than most ROMS for clover that are based on LineageOS, and MoKee 10 for clover seems to work really well. I left my device in Airplane mode for 7 hours, and the battery percentage was exactly the same as I left it. Finally!
删库跑路 - 马丁龙猪的博客
刷机的时代其实早已落幕，迟迟下不定决心只是希望能让魔趣多存续一些时间，但该来的终究会来。 马丁龙猪今天决定删库
download.mokeedev.com
A few other observations and first impressions:
I hate the tacky cartoonish boot animation, but the com.jrummy.apps.boot.animations app works fine to change it after rooting with Magisk.
For the initial setup screen the default option is Chinese, but just scroll down until you see your language, it appears to support all the usual ones.
I didn't install GApps, but somehow it still has the official Gboard keyboard with swipe enabled out of the box.
For some reason on my first install it didn't have a camera app. Then I wiped it and reflashed it and now it has a camera (org.mokee.snap). I honestly don't understand how it could be different from one flash to another, but at any rate it appears to be quite a nice camera with lots of configurable options and a working panoramic mode, which is rare in AOSP based ROMs.
The default gallery app is also good, SimpleMobileTools Simple Gallery Pro, which is my preferred open source gallery app. Some ROMs preinstall Simple Gallery, but it's not the pro version and it's much more limited, and it conflicts with the Pro version when you try to install it over top of it. MoKee does it right from the start.
Lots of configurability in the settings, including an option to control the cursor with the volume keys and on the bottom bar, which I find extremely useful. Only missing option is putting the date on the status bar next to the clock.
Working notification LED, unlike ArrowOS.
So this has been a great find. I'll report back if I find anything else. Thanks a lot to the devs if any see this thread.
Nice find and PSA
I just had a quick read about Mokee, and it appears to be a legit rom.
- From what I've read, playstore is installable
- States open source, get a tick for that
- Any chance you've run a quick virus/malware scan?
- I can see a few 'experimental' builds for 11.0, I'll keep an eye on that progress..
Cheers
Wizballs said:
Nice find and PSA
I just had a quick read about Mokee, and it appears to be a legit rom.
- From what I've read, playstore is installable
- States open source, get a tick for that
- Any chance you've run a quick virus/malware scan?
- I can see a few 'experimental' builds for 11.0, I'll keep an eye on that progress..
Cheers
Click to expand...
Click to collapse
Hi there, no I haven't run any malware scans, I don't have much faith in the antivirus/anti-malware sort of programs due to the false positives and FUD that they seem to depend on. I can give it a shot though if you know of any trustworthy ones.
Yes, the Play Store should be installable, they have normal Gapps packages that they recommend at the downloads page. I prefer to run with MicroG instead and I use the Aurora store. A small disadvantage is that MoKee doesn't support signature spoofing out of the box (needed for MicroG), but with Magisk and NanoDroid I got it working.
I also saw the 11.0 builds, maybe we should try to post over on their forum to let them know that there are some very interested and determined clover owners still out there.
sb56637 said:
Hi there, no I haven't run any malware scans, I don't have much faith in the antivirus/anti-malware sort of programs due to the false positives and FUD that they seem to depend on. I can give it a shot though if you know of any trustworthy ones.
Yes, the Play Store should be installable, they have normal Gapps packages that they recommend at the downloads page. I prefer to run with MicroG instead and I use the Aurora store. A small disadvantage is that MoKee doesn't support signature spoofing out of the box (needed for MicroG), but with Magisk and NanoDroid I got it working.
I also saw the 11.0 builds, maybe we should try to post over on their forum to let them know that there are some very interested and determined clover owners still out there.
Click to expand...
Click to collapse
The only scanner I really use is ESET for windows, and new android roms and then uninstall after scanning. I've never got a false positive from it.
But I'm downloading Mokee now to give it a try...
So far so good. I'll leave it sit now for 24 hours and report back on standby battery use. And yes I think posting a thanks in their forums is a good idea. And will just be a thanks as there are no real issues to report! Actually is a very well finished and working ROM.
Couple or more points:
- Mokee recommended gapps (opengapps) just wouldn't install - error code 64
- Nikgapps installed and ran perfectly fine however. lol.
- USB debugging turned on by default, some users like me will want to turn this off
- Does appear to be a lineageos base, but only a guess
- Can actually turn off double tap to wake. Arrow stayed on regardless of setting. Wonder if this will help standby battery marginally? I have flip case that turns screen on, works with this rom
- ESET scan 100% clean
- Disabled a few of useless apps (like I do with every ROM, without root) using:
adb shell
pm uninstall -k --user 0 package.name
- Nutflix not available directly from Playstore. Not a problem, install using SAI
- Encryption turned on by default (great!)
- Lately I'm finding that built in launchers are giving me the best stability / performance in any ROMS . Always used nova in the past.
- Turned off that status bar upload/download speed doobie. Personal preference.
- Appears to have OTA updater, will give a spin next update
Overall, awesome so far
Good find @sb56637
@Wizballs Great, and I'm glad it scanned clean too.
Appears to have OTA updater, will give a spin next update
Click to expand...
Click to collapse
Yep, although there are a few quirks here. First is that they limit the download speed to about 250 KB/s for non-donators, fair enough. But the bigger issue is that it downloads it to the internal storage (obviously), which MoKee automatically encrypts, so normal TWRP can't see it and it can't be installed. They supposedly have a MoKee flavor of TWRP that works with the encryption. I briefly tried to download it, but it was a Baidu site in Chinese that offered me Linux packages (DEB or RPM), which didn't make sense, so I stopped there. But I'll look into it more again and report back.
Fair enough, will stick to manual updates then. Would prefer to keep stock twrp.
Approx 2.5% battery over 24 hours standby. Very good.
I decided to switch to the MoKee flavor of TWRP, linked here in a more accessible location:
Android10.New Mokee MK100
Download: https://download.mokeedev.com/clover/file/MK100.0-clover-201912021712-EXPERIMENTAL.zip/download -First boot in cn language only. setting----System----Add Eng language to Gboard---deselect from CN to Eng in first order option you...
forum.xda-developers.com
With that flashed, OTA updates work well. (Plus it allows for manipulating /system and /data from the TWRP file manager, which is very useful sometimes. Plus, it allows for flashing other scripts like Magisk from TWRP, which adds an addon.d hook to allow it to survive upgrades.)
Wizballs said:
- Lately I'm finding that built in launchers are giving me the best stability / performance in any ROMS . Always used nova in the past.
Click to expand...
Click to collapse
Quick post to note that in later Android versions (from A10+?) the default launcher is always in charge of displaying recents, so it can't/shouldn't be uninstalled -- this may explain stability issues...
pnin said:
Quick post to note that in later Android versions (from A10+?) the default launcher is always in charge of displaying recents, so it can't/shouldn't be uninstalled -- this may explain stability issues...
Click to expand...
Click to collapse
I never uninstalled the default browser, just left it there while using nova...
Look at that battery saving. Worldwide could account to millions dollars saved each year
sb56637 said:
I decided to switch to the MoKee flavor of TWRP, linked here in a more accessible location:
Android10.New Mokee MK100
Download: https://download.mokeedev.com/clover/file/MK100.0-clover-201912021712-EXPERIMENTAL.zip/download -First boot in cn language only. setting----System----Add Eng language to Gboard---deselect from CN to Eng in first order option you...
forum.xda-developers.com
With that flashed, OTA updates work well. (Plus it allows for manipulating /system and /data from the TWRP file manager, which is very useful sometimes. Plus, it allows for flashing other scripts like Magisk from TWRP, which adds an addon.d hook to allow it to survive upgrades.)
Click to expand...
Click to collapse
Can you share the Mokee recovery via a different link? That link doesn't work and the one on Mokee's website points to Baidu, which seems to require a Baidu account to download. I can't create a Baidu account though, since it requires you to use a China mobile number to register.
UPDATE:
NVM, found the link via another XDA thread. Here it is:
TWRP-20200628-3.3.1.0-clover.img
drive.google.com
This ROM is missing face unlock, which isn't a big deal considering that the battery life is a big improvement over the last ROM I was using, but still would be nice to have...