Scripting Question - Android Q&A, Help & Troubleshooting

Ok I'm working on a custom rom and writing some scripts for it to tweak things and automate a few functions. I was messing around today with the android scripting engines for python and java just to see what it was capable of and it basically allows you to write java and py scripts that allow interaction with the android api.
I was wondering; would it be easier to implement the script engines into my rom I'm working on now to create a sort of frontend for my shell scripts adding the usage of api functions like reading sensors, displaying alert pop ups etc.. or just code up an app to act as a script frontend and incorporate it into the rom.
Personally I really like the idea of being able to write scripts directly on the device that can do pretty much anything most apps can do but for the sake of ease of debugging and the end user of the rom it may be better to go with an app to do everything instead.
Any feedback is appreciated.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.

The first one. It's better to implement the script engines into your rom. This would allow the scripts to always boot with your rom making it faster and optimized (etc. depending on what scripts you included). Doing this via an app will give the user a choice to use it (and even remove it). If they are necessary, then the rom won't work too well after that. You could also make some tweaks to the build.prop and init.d (if you are including that in your rom) to make the rom even better.

Theonew said:
The first one. It's better to implement the script engines into your rom. This would allow the scripts to always boot with your rom making it faster and optimized (etc. depending on what scripts you included). Doing this via an app will give the user a choice to use it (and even remove it). If they are necessary, then the won't work too well after that. You could also make some tweaks to the build.prop and init.d (if you are including that in your rom) to make the rom even better.
Click to expand...
Click to collapse
I do have init.d incorporated into the rom and am making use of it and have tweaked build.prop quite thoroughly. I've also been tweaking the kernel for the rom. Everything you said though is the same thing that had me leaning towards this option. It would add tons of functionality to my scripts and it'd be very easy to make changes to whatever I need to.
I've also been thinking more about the debugging part and I also believe this would be much easier as every part would be seperate from the main function. So if there were any problems you'd only have to run through the offending scripts code or the call coming from the "main" script instead of an entire program.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.

Related

[Q] Speed/Performance Scripts Overview

Sorry for the incredibly newbish question. (Feel free to refer me to other places this may have been answered.)
There seem to be a lot of "Speedy"/Performance scripts listed in the Sticky on the X2 Dev forum, and I was just wondering if someone would be kind enough to provide a line or two to describe each.
It seems to me like there is a lot of overlap between some of these scripts, especially when considering the tweaks added by various ROMs. So I am most interested in finding out basically which are compatible, and which are most likely to conflict with the available custom ROMs.
Here are a couple, but feel free to add more.
Speedy V6
Init.d Re-hack (required for some scripts)
Init.d Hack v0.6 (required for some scripts)
Speedy Gonzales v1.0 (thread closed)
Power Boost v2.0
-=V6 SuperCharger=-
SetCPU (an app that may/may not work in conjunction with some of the above scripts)
Again, sorry for my nativity here. I know this information can be found in the individual threads, but I'm sure a basic overview would be a really big help for those of us who are just now trying to get into the installation of some good speed scripts. It's also really unclear to a beginner which scripts/apps/ROMs will conflict with each other or which combinations might actually reduce effectiveness & stability.
Thanks!
ya i agree...too many of these overlap with each other.....which work with what kernal???....which works the best....benefits of each??....etc....
init.d hack is a way to allow you to store scripts in a directory called /etc/init.d that will fire up when the phone reboots. Without it, you could create the directory but your phone won't run the scripts.
It's best to flash the init.d hack first which "hijacks" the boot process and will execute any scripts located in the /etc/init.d directory.
Once that is flashed, I find the V6 Supercharger Scripts to be the best for making the phone speedy. I use options 9 and 12. 9 sets the optimal memory settings that seem to prevent music from skipping. Option 12 makes the launcher not get killed in memory which can cause skipping and hi cupping in the X2 as it unloads and reloads from what I understand.
I really haven't used anything else except the V6 Supercharger Scripts. They seem to be the most popular, but what it all boils down to is, experiment with each one and see which gives you the best performance you are seeking.
I also know many ROMS, such as Eclipse, have incorporated the init.d hack and have their own versions of many of these performance scripts in them, so mileage will vary.
Also, the kernel doesn't mean anything. It works with all kernels. But, many of them require Busybox installed since they use various UNIX commands that are not available in the stock image.
question: can't you just save the 99 v6 script as run as root, run at boot after you create the init.d directory instead of having to run the init.d hack? i've never run the init.d hack but have used the run as root run at boot save and it always loads fine on boots.
I really hope I posted this in the right place...
I loaded Eclipse v1.3 yesterday on 2.3.4 and I love it! It works really well. I had the issue about the gps but it went away after 2 battery pulls. I don't have any problems with iheartradio skipping or any other music for that matter. I have even noticed my X2 runs way faster. But, my internet is slower. No matter downloading or browsing, I can tell it is slower than before. Since Eclipse has the init.d already inside, can I download the Speedy V6 zip and flash it when I go into recovery mode? From what I have read in the forum, that should increase the overall speed of the phone. Or, being a noob, am I going about that the wrong way?
---------- Post added at 01:58 PM ---------- Previous post was at 01:37 PM ----------
tallyforeman said:
I really hope I posted this in the right place...
I loaded Eclipse v1.3 yesterday on 2.3.4 and I love it! It works really well. I had the issue about the gps but it went away after 2 battery pulls. I don't have any problems with iheartradio skipping or any other music for that matter. I have even noticed my X2 runs way faster. But, my internet is slower. No matter downloading or browsing, I can tell it is slower than before. Since Eclipse has the init.d already inside, can I download the Speedy V6 zip and flash it when I go into recovery mode? From what I have read in the forum, that should increase the overall speed of the phone. Or, being a noob, am I going about that the wrong way?
Click to expand...
Click to collapse
I'd also like to note: On my CPU tuner app, it always says the Active CPU's are 1/2 and does not pass the test under the "check capabilities" portion of the app. I also had the same result before rooting and loading Eclipse. Will the new script cure that?
h_10 said:
question: can't you just save the 99 v6 script as run as root, run at boot after you create the init.d directory instead of having to run the init.d hack? i've never run the init.d hack but have used the run as root run at boot save and it always loads fine on boots.
Click to expand...
Click to collapse
The main reason for the init.d hack is so u don't NEED script manager to run init.d scripts at boot. One less thing for ur phone to have to start up. One less application running on startup.
What I used to do(when not running a rom w/init.d support...eclipse HAS init.d hack built in along w/liberty (others too I believe)
Is I would flash the hack. Delete all init.d scripts and just run supercharger scripts from there.
that way there was no need to run the supercharger scripts at boot etc...

[Q] Looking for a guide/FAQ on rooting terminology?

I remember seeing guides on here to help the newbs out with terminology about rooting and so on. I've never had an HTC phone, just returned my GNEX for the REZOUND. I really want to understand what kernels are, what RUU means, etc. Are there any tutorials out there to help learn about all this. Any help would be appreciated.
I'll help what I little I can. Ruu is a program that is run from a pc that returns it to like new condition minus the relocked. You have to relock before using it. Kernels you have to flash from bootloader unlocked without S-off.
sent from my newly unlocked Rezound
Collection of Root Guides
Here's some links I have bookmarked for studying. These are mostly about the Evo but most info still applies, but of course don't do any of the step by step stuff on your phone, just read it for educational purposes. I think what you were looking for is in the first and second links.:
The Beginner's Guide to Rooting
A universal primer for rooting concepts on Android devices
Quick INTRO TO ROOTING for those new to rooting
ROOTING For Dummies
ROOTING For Dummies Guide.....the Gingerbread Edition
Evo Root Only Apps
Thanks for all the guides. Right now I'm trying to understand Kernels. For example; http://forum.xda-developers.com/showpost.php?p=19895706&postcount=1
What is the point of this and what are the benefits from flashing this?
this should help.............http://www.freeyourandroid.com/guide/how-to-overclock-part-one
bal1985 said:
Thanks for all the guides. Right now I'm trying to understand Kernels. For example; http://forum.xda-developers.com/showpost.php?p=19895706&postcount=1
What is the point of this and what are the benefits from flashing this?
Click to expand...
Click to collapse
A kernel is literally the actual OS. The bits you see and interact with on the screen is the GUI (graphic user interface) which is just an application layer that allows the user and apps to interact with the kernel. This applies for Linux, Windows, MacOS, and Android.
The kernel is what has access and control over the device hardware. Different kernels have different settings and options in them. E.G. CPU frequency steps, CPU voltage control, GPU control, bluetooth module, GPS system, and others. It controls everything basically.
Like I said before, what everyone tends to think of an OS is just the GUI, (some OS's only have command line interfaces) but that is just an abstraction layer that allows users an easier method to control the kernel. (OS)
The benefits of new kernels are the changes and tweaks they contain for improving various phone functions.
Marine6680 said:
A kernel is literally the actual OS. The bits you see and interact with on the screen is the GUI (graphic user interface) which is just an application layer that allows the user and apps to interact with the kernel. This applies for Linux, Windows, MacOS, and Android.
The kernel is what has access and control over the device hardware. Different kernels have different settings and options in them. E.G. CPU frequency steps, CPU voltage control, GPU control, bluetooth module, GPS system, and others. It controls everything basically.
Like I said before, what everyone tends to think of an OS is just the GUI, (some OS's only have command line interfaces) but that is just an abstraction layer that allows users an easier method to control the kernel. (OS)
The benefits of new kernels are the changes and tweaks they contain for improving various phone functions.
Click to expand...
Click to collapse
Yeah, as he said Kernels are one layer down from the GUI (Graphical User Interface). Imagine it like a onion. The core is your hardware, kernel is up one. It's the software that interacts with the hardware, then there is the CLI (Command Line Interface) or GUI that interacts with the kernel.

[rom][tweaks][4.0,5.0] Speed tweaks for all Galaxy Players!

This thread Is a compilation of speed tweaks and mods I have gathered from the forums and used on my Galaxy Player 4.0. I can vouch for all of these tweaks, and all provide at least a modest performance improvement. I claim no credit for any of these mods, the glory goes to the fabulous devs who have created them.
To show you the possible performance increase, I have all of these tweaks installed with the Terrasilent kernel and Klin's R5 ROM, plus an Overclock to 1.5 GHZ, and I have scored over 2750 in Quadrant, as indicated in the screenshot below.
If you have any potential tweaks or suggestions, PM me, and I will check them out!
Note to devs: I believe I have posted this in the right section, as this does not 100% pertain to development.
Now, let's get cracking!
Tweak No. 1: convert RFS filesystem to EXT4.
RFS has been tweaked since it debuted on the galaxy S over two years ago, but still is not quite up to par with today's standards.
Steps:
1. Flash the Terrasilent kernel/ Klin's R3 (basically a kernel with Clockwork recovery 5+ on it)
2. Make a nandroid backup (make sure you have enough free space!)
3.after you reboot, navigate using a file explorer on the Gplayer to the recovery directory and rename all files (excluding boot.img) from .rfs.tar to .ext4.tar.
4. Open up nandroid.md5 and change all filenames (again, excluding boot.img) from .rfs.tar to .ext4.tar
5.Save that, reboot into recovery, perform a full restore, and reboot into download mode.
6. reflash the kernel you were using, and you are done!
The performance improvement is amazing, and I would recommend using this tweak to anyone, since it's safe, and provides a huge boost!
Tweak no.2: Universal Adrenaline shot.
This is an amazing tweak that has provided the biggest improvement for me. It should be pretty risk-free if you follow my directions. Do NOT try to unzip and manually install, as you will have to reflash you rom (bootloop). Additionally, you will have to reinstall any init.d tweaks you have currently, as this script wants to ensure no conflictions, and deletes them all
Steps:
1. Head to this link, read, and download Adrenaline shot v14 (don't worry, our device can handle the two risky tweaks).
2. Boot into recovery, and flash!
3. After flashing, I would optionally format /cache. After reboot, you should see a drastic performance increase!
Tweak no.3: EXT4 Journalism tweaks.
EXT4 is much faster than RFS, but on our Players, the lag is still noticeable, just navigating around the UI.
WARNING:This provides a nice speed increase, especially to large games, but if you have an unclean shutdown, or force restart your Gplayer, YOU WILL HAVE TO RESTORE!
Dire warnings said, This actually increases the smoothness of the Gplayer a decent amount, although for me the risk far outweighs the benefit.
Your partitions are as follows:
System: STL9
Data: mmcblk0p2
Dbdata: stl10
cache (use this partition if you want to test):stl11
Remember, you need su permissions for all of this!
Instructions:
1.First, FSCK the partitions (make sure you answer no to all but the first questions, as that could lead to file corruption! the errors are generated when the partition is accessed during the FSCK, which generates an error, since data is in a different section than it was before. Don't worry, most/all of those errors are flukes. The instruction is: e2fsck -f /dev/block/(partition name)
2. Disable journalism with tune2fs: tune2fs -O ^has_journal /dev/block/(partition name)
Note: tune2fs will not have the capabilities necessary unless you install the one from the one shot adrenaline tweak above.
3.reboot and enjoy!
If you want to reverse this, you will have to restore a nandroid backup, as CWM formats EXT4 with journalism, and a format is required to reset it. On the same note, you will have to reapply this tweak every time you restore a nandroid backup, just something to keep in mind.
Tweak no.4: Supercharge, and apply Loopy smoothness!
I am sure everyone knows about the ubiquitous v6 supercharger script out there, and it provides a big performane increase! Also, Loopy smoothness helps a lot in stabilizing launcher performance, and I view them to be equally valuable.
1. Visit here to download the latest supercharger script, and here to download T2 of loopy smoothness.
2. Launch the supercharger from the /sdcard/download directory, go throught the basic instructions, and the custoomize, reboot, and install nitro lag nullifier. Optionally install for easier access. I would also explore some of the other options especially reindexing.
3. move the loopy smoothness script into the init.d directory, open it, and remove the quotation marks around the launcher name if you are using the touchwiz launcher, or delete the quotations and name and add your launcher's process name (run ps in terminal emulator and find the most likely name, or look it up).
That's it! you should notice a definite performance increase, especially improvements in multitasking thanks to v6 supercharger. The launcher should also be a lot smoother.
Bonus (I have it in R5 rom, but have not actually applied it)
head here, download the latest script, and run it. It should add some extra build.prop tweaks that will greatly boost performance!
Some final suggestions:
1. Move to a custom launcher.
Using touchwiz, I always had about 125+- ram free after using a taskiller, but when I moved to go launcher EX (imho, the best launcher for the gplayer out there, beautiful, not hard on resources, and very customizable), I had over 160+ free after using a taskiller, which resulted in far smoother operation, and excellent multitasking!
2. use ondemand or ondemandx.
All the Gplayer profiles are good, but ondemand, although not the best at power saving, provides the best performance on our aging system, and gives a little extra juice when you need it.
3. use the deadline governor.
None of the other I/O governors come even close to NOOP and Deadline, but deadline is better for everyday use, and noop is better if you have several file transfers occurring at once (eg. hooked up to a computer, updating apps, and browsing the web). It comes down to your usage style, but I prefer Deadline.
4. Disable uneeded /system/app apps.
Fortunately our Gplayer is pretty bloat free, but you can disable more apps if you want. You should rename them to .apk1 instead of deleting them, just in case. Do not delete phone.apk, because for some reason it breaks the default camera app ( you can delete it if you don't use it).
Open up a terminal, run the ps command, and disable any system, apps you recognise in the list (una, fota, etc.).
Beta: Format sdcard as ext2
I had limited success with this mod, and it is definitely worth hassle of converting to ext2. Unfortunately, you must have an init.d script that runs at boot, and there will be the occaisonal permissipn issue, but chmoding the sdcard fixes that.
Steps:
1. Backup all of your /sdcard data
2.connect the gplayer to a linux computer in mtp mode.
3. Open a terminal, and type:
sudo umount /dev/sdx
sudo mkfs.ext2 /dev/sdx
4. Disconnect it from the computer. It will output an error when the media scanner runs, this is okay.
5. Create an init.d script with the following info:
#!/system/bin/sh
mount rw /dev/block/vold/179:1 /mnt/sdcard
chmod 777 /mnt/sdcard
chmod 777 /mnt/sdcard/*
chmod 777 /mnt/sdcard/Android
chmod 777 /mnt/sdcard/Android/*
6. Reboot, and restore your data.
That should be it! I used ext2 because i got permission errors with ext3/4 constantly, and ext2 was stable. The performance improvement is amazing, especially with apps that store data to /sdcard. My performance is at least doubled! Even thouh this is beta, I STRONGLY recommend doing this, as the performance is incredible (as I said)!
Note: after doing this, windows machines will not recognize the player, you will have to do all file transfers via linux.
Note: of app data is not recognized after restore, delete and redownload, after backing up the save file/s. At the moment, it is the only way I have to fix it.
Enjoy the speed!
Dalvik machine: the ULTIMATE speed booster.
I was poking around lately, and I discovered that dalvik settings are really far more powerful than most people give them credit for. Using them on an (unreleased) version of EtherealRom gave me a nice speed increase!
All of these can be added/edited in build.prop, if you so choose, under the variable "dalvik.vm.dexopt-flags=".
The most important one is u=y. This indicates that you want all VM code to be optimized for a single core, and provides a NICE speed boost. The next most important is o=a, as that indicates that you want it to optimize ALL the code, instead of selective batches.
I will update this later, I am exhausted right now, and need some sleep.
I now have my own custom rom that you can flash, that includes most of these amazing features (no ext converting, that has to be manual), plus some more! Note: this rom is ONLY for the 4.0. you will have to restore if you flash it onto the 5.0!
Download
That's it! I will certainly add on as time progresses, but at the moment that is all I can remember/know about, so be sure to pm me with potential tweaks so I can put it up here!
hanthesolo said:
This thread Is a compilation of speed tweaks and mods I have gathered from the forums and used on my Galaxy Player 4.0. I can vouch for all of these tweaks, and all provide at least a modest performance improvement. I claim no credit for any of these mods, the glory goes to the fabulous devs who have created them.
To show you the possible performance increase, I have all of these tweaks installed with the Terrasilent kernel and Klin's R5 ROM, plus an Overclock to 1.5 GHZ, and I have scored over 2750 in Quadrant. If you don't believe me, I will put up a screenshot, as I don't have screen capturing software on my Gplayer right now, and it's too much of a hassle.
If you have any potential tweaks or suggestions, PM me, and I will check them out!
Note to devs: I believe I have posted this in the right section, as this does not 100% pertain to development.
Now, let's get cracking!
Tweak No. 1: convert RFS filesystem to EXT4.
RFS has been tweaked since it debuted on the galaxy S over two years ago, but still is not quite up to par with today's standards.
Steps:
1. Flash the Terrasilent kernel/ Klin's R3 (basically a kernel with Clockwork recovery 5+ on it)
2. Make a nandroid backup (make sure you have enough free space!)
3.after you reboot, navigate using a file explorer on the Gplayer to the recovery directory and rename all files (excluding boot.img) from .rfs.tar to .ext4.tar.
4. Open up nandroid.md5 and change all filenames (again, excluding boot.img) from .rfs.tar to .ext4.tar
5.Save that, reboot into recovery, perform a full restore, and you are done!
Note: after converting, my /data partition is deleted/not recognized when booting into recovery on the terrasilent kernel. I think this may be an isolated incident, but you have been warned!
Tweak no.2: Universal Adrenaline shot.
This is an amazing tweak that has provided the biggest improvement for me. It should be pretty risk-free if you follow my directions. Do NOT try to unzip and manually install, as you will have to reflash you rom (bootloop). Additionally, you will have to reinstall any init.d tweaks you have currently, as this script wants to ensure no conflictions.
Steps:
1. Head to this link, read, and download Adrenaline shot v14 (don't worry, our device can handle the two risky tweaks).
2. Boot into recovery, and flash!
3. After flashing, I would optionally format /cache. After reboot, you should see a drastic performance increase!
Tweak no.3: EXT4 Journalism tweaks.
EXT4 is much faster than RFS, but on our Players, the lag is still noticeable, just navigating around the UI.
WARNING:This provides a nice speed increase, especially to large games, but if you have an unclean shutdown, force restart your Gplayer, YOU WILL HAVE TO RESTORE!
Dire warnings said, This actually increases the smoothness of the Gplayer a decent amount, although for me the risk far outweighs the benefit.
Your partitions are as follows:
System: STL9
Data: mmcblk0p2
Dbdata: stl10
cache (use this partition iuf you want to test):stl11
Remember, you need su permissions for all of this!
Instructions:
1.First, FSCK the partitions (make sure you answer no to all but the first questions, as that could lead to file corruption! the errors are generated when the partition is accessed during the FSCK, which generates an error, since data is in a different section than it was before. Don't worry, most/all of those errors are flukes. The instruction is: e2fsck -f /dev/block/(partition name)
2. Disable journalism with tune2fs: tune2fs -O ^has_journal /dev/block/(partition name)
Note: tune2fs will not have the capabilities necessary unless you install the one from the one shot adrenaline tweak above.
3.reboot and enjoy!
If you want to reverse this, you will have to restore a nandroid backup, as CWM formats EXT4 with journalism, and a format is required to reset it. On the same note, you will have to reapply this tweak every time you restore a nandroid backup, just something to keep in mind.
Tweak no.4: Supercharge, and apply Loopy smoothness!
I am sure everyone knows about the ubiquitous v6 supercharger script out there, and it provides a big performane increase! Also, Loopy smoothness helps a lot in stabilizing launcher performance, and I view them to be equally valuable.
1. Visit here to download the latest supercharger script, and here to download T2 of loopy smoothness.
2. Launch the supercharger from the /sdcard/download directory, go throught the basic instructions, and the custoomize, reboot, and install nitro lag nullifier. Optionally install for easier access. I would also explore some of the other options especially reindexing.
3. move the loopy smoothness script into the init.d directory, open it, and remove the comments around the launcher name if you are using the touchwiz launcher, or delete comments and name and add your launcher's process name (run ps in terminal emulator and find the most likely name, or look it up).
That's it! you should notice a definite performance increase, especially improvements in multitasking thanks to v6 supercharger. The launcher should also be a lot smoother.
Bonus (I have it in R5 rom, but have not actually applied it)
head here, download the latest script, and run it. It should add some extra build.prop tweaks that will greatly boost performance!
Some final suggestions:
1. Move to a custom launcher.
Using touchwiz, I always had about 125+- ram free after using a taskiller, but when I moved to go launcher EX (imho, the best launcher for the gplayer out there, beautiful, not hard on resources, and very customizable), I had over 160+ free after using a taskiller, which resulted in far smoother operation, and excellent multitasking!
2. use ondemand or ondemandx.
All the Gplayer profiles are good, but ondemand, although not the best at power saving, provides the best performance on our aging system, and gives a little extra juice when you need it.
3. use the deadline governor.
None of the other I/O governors come even close to NOOP and Deadline, but deadline is better for everyday use, and noop is better if you have several file transfers occurring at once (eg. hooked up to a computer, updating apps, and browsing the web). It comes down to your usage style, but I prefer Deadline.
4. Disable uneeded /system/app apps.
Fortunately our Gplayer is pretty bloat free, but you can disable more apps if you want. You should rename them to .apk1 instead of deleting them, just in case. Do not delete phone.apk, because for some reason it breaks the default camera app ( you can delete it if you don't use it).
Open up a terminal, run the ps command, and disable any system, apps you recognise in the list (una, fota, etc.).
That's it! I will certainly add on as time progresses, but at the moment that is all I can remember/know about, so be sure to pm me with potential tweaks so I can put it up here!
Click to expand...
Click to collapse
Very nice thread! I'll try it once my device finishes charging. How did you manage to get 1.5 OC?
Thanks! you can tell I am more than a little OCD about my device's performance
I was able to achieve a stable OC by setting the internal voltage to 1.19V, and my core voltage to 1.4V, using Tegrak Overclock. This gives a nice increase to the performance of my player!
hanthesolo said:
Thanks! you can tell I am more than a little OCD about my device's performance
I was able to achieve a stable OC by setting the internal voltage to 1.19V, and my core voltage to 1.4V, using Tegrak Overclock. This gives a nice increase to the performance of my player!
Click to expand...
Click to collapse
I'm not really familiar with OC at all but you just change the voltage and the 1.5 OC option will appear? Didin't you modify your kernel a bit to do this?
As I said in the OP, I have the Terrasilent kernel installed, which allows by default overclocking up to 1.2 GHZ. If you install Tegrak Overclock Ultimate, you can load it's module and overclock up to 2 GHZ with a max internal voltage of 1250mv, and a max core voltage ov 1400MV. Suprisingly easy, actually, and an invaluable tool. You can also change the I/O governor like I suggested from it as well. Attached is A screenshot of my quadrant score (I decided to do it anyway). The score is slightly lower than I said because I have Journalling disabled (to much of a hassle to keep restoring every day).
hanthesolo said:
As I said in the OP, I have the Terrasilent kernel installed, which allows by default overclocking up to 1.2 GHZ. If you install Tegrak Overclock Ultimate, you can load it's module and overclock up to 2 GHZ with a max internal voltage of 1250mv, and a max core voltage ov 1400MV. Suprisingly easy, actually, and an invaluable tool. You can also change the I/O governor like I suggested from it as well. Attached is A screenshot of my quadrant score (I decided to do it anyway). The score is slightly lower than I said because I have Journalling disabled (to much of a hassle to keep restoring every day).
Click to expand...
Click to collapse
Oh ok you have tegrak ultimate. I had tegrak free and the limit was 1.3. Also for the journaling why don't you make a script to execute it at each boot?
Yeah, You can do some crazy stuff in the ultimate version!
I will upload the screenshot in the OP, the way I did it wouldn't work the first time
I didn't make journalism a init.d script because it is a one-time tweak, you apply it, and you have to reformat to go back! I also didn't spell out the instructions verbatim in case someone wants to selectively apply this tweak or use it as reference.
zaclimon said:
Oh ok you have tegrak ultimate. I had tegrak free and the limit was 1.3. Also for the journaling why don't you make a script to execute it at each boot?
Click to expand...
Click to collapse
Also, I have triesd to make an init.d script to disable journaling and putting tune2fs in /system/xbin, but it errors out because you can only disable journaling when the partitions aren't mounted. So what I did was copy tune2fs to a directory, boot into recovery, unmount all the partitions and then disable journaling.
Surprisingly my quadrant score jumped by 400 points.
Sent using Tapatalk
klin1344 said:
Also, I have triesd to make an init.d script to disable journaling and putting tune2fs in /system/xbin, but it errors out because you can only disable journaling when the partitions aren't mounted. So what I did was copy tune2fs to a directory, boot into recovery, unmount all the partitions and then disable journaling.
Surprisingly my quadrant score jumped by 400 points.
Sent using Tapatalk
Click to expand...
Click to collapse
I was able to do it (albeit with warnings during e2fsck) using merely the terminal emulator, and after fixing permissions on tune2fs (I manually placed it). I checked it with tune2fs -l /dev/block/(partition) | grep features, and it claimed that I removed the has_journalism flag. Plus, I got the wonderful benefit of corruption after an unclean shutdown.
Is Rom compatibile with SGP 5.0(International) if not can you please pm me some advice about how to port it on SGP 5.0 ?
Unfortunately, This rom is based soly on the SGP 4.0, and would be very difficult to port onto the 5.0. I am currently working on a flashable zip file that contains most of these tweaks, so you won't have to use the rom.
Ok thanks mate , i try two tweaks and its amazing....its awesome feeling when onecore processor 1.5Ghz defeat dualcore Tegra 2
Which two did you try?
what score did you get?
It DOES feel pretty awesome to see quadrant shoot up past a tegra device
Sneak preview: me and Klin are working together on his next version of his rom, and it will have all of these tweaks, plus some extras (read: ext4 sdcard)!
One thing I am not certain about with the adreneline shot; do I need to manually delete my init.d scripts, or will flashing this delete them?
Sent using Tapatalk
The scipt will delete them for you when you flash, but it shouldn't cause any issues if they are not deleted. If some conflict, it may reduce the overall performance boost, but that's the worst that could happen.
hanthesolo said:
Which two did you try?
what score did you get?
It DOES feel pretty awesome to see quadrant shoot up past a tegra device
Sneak preview: me and Klin are working together on his next version of his rom, and it will have all of these tweaks, plus some extras (read: ext4 sdcard)!
Click to expand...
Click to collapse
I try Ext4 and Adrenaline and i get 2612 points I enjoy for flashable pack of tweaks Nice work mate and good luck with all your projects PS sorry for my bad english
Glad it works! I am almost done testing ext4 sdcard, and I will have the steps up here soon. Additionally, Klin will release an update to his ROM with my tweaks includded in the next couple of days, along with more than one new goody
I don't get how you get such a high io score! My io is around 800!? I installed the adreneline tweak, but nothing noticeable, perhaps even worse performance. I have ext4 (I think, since I installed klin's r5). I use deadline scheduler. I also use v6 supercharger. What are you people's quadrant score with just the adrenaline and supercharger? No overclock.
Sent using Tapatalk
Klin's R5 only formats /system as ext4. to get the full benefit (and the noticeable increase), do it on all partitions using the guide on the OP. I would also use noop, as it seems to be slightly faster than deadline on ext4. Once you do that, you should get the increase.
Well, I just tried to convert to ext4 following your instructions, but following the reboot, it has been on the solid "samsung" (not the pulsing one) screen for several minutes, is this normal, or did something bad happen?

Tutorial/tool to modify a kernel to hide non-debuggable apps ?

Ever since I've moved to AOSP based roms (SlimKat, CyanogenMod, OmniRom, Resurrection-Remix,...) , I've noticed that in the DDMS tool (a tool for developers) that it shows all processes, and not just debuggable processes, including all third party apps' processes and OS's processes.
This never occurred for me on stock roms, no matter which device or stock rom I've looked at.
This issue annoys me as a developer, since I usually run only a single app that I develop and when I go to DDMS to choose the app's process, I need to find it amongst many processes (even of WhatsApp) , and, provided it hasn't changed its position on the list, click it and debug it.
So I asked about this on some kernels forums, and usually people didn't mind about it (and for good reason - it can bother only few people).
I've found the next tweak which can do it, but since I'm a complete newb in creating/modifying kernels, I have no idea how to patch it:
setprop ro.debuggable=0
Click to expand...
Click to collapse
Found from here .
I've contacted a few kernel developers and one of them agreed to check it out. I've tested it on CM and it worked just as it was intended :
Only debuggable apps' processes were visible and ready to be debugged.
Anyway, I wish to ask whoever is an expert in developing/modifying kernels those questions:
1. Why isn't this tweak enabled by default?
I mean, this is not the normal way roms work. It's not like this on any stock rom I've seen, not even on Nexus stock roms...
I also don't get why it's this way even for "final/stable" version roms (meaning not nightlies or experimental ones), since you'd probably not need to be able to debug them (users won't give you their device just for that...) .
2. Can you please explain to me, step by step (but don't assume I know anything about kernels development), how to take a rom's zip, and change its kernel so that this tweak will be enabled?
Maybe I could make an automatic tool that does it, either in Java for desktop or for Android.
3. Is there any way to enable this tweak without modifying the kernel? Maybe by using a tool that works with it?
Or maybe, provided we got root, change something to enable it?

[Q&A][ROM][STOCK, CUSTOM] Lenovo Tab 3 8/TB3-850F

Lenovo Tab 3 8/TB3-850F
Question & Answer Forum
Link & General Resource Guide
RE: Stock & Custom ROM(s)​
INTRODUCTION & PURPOSE:
I have started this thread as a Q&A forum and general info guide for my Stock 6.0 ROM for the Lenovo Tab 3 8, and as a forum for my stock-based custom ROM which is nearing completion. In addition, I have posted some useful threads for this device below. It has been brought to my attention by XDA Senior Member @pndwal, as well as other members, that topics regarding systemless rooting, dm-verity, force encryption, Trusted Execution Environment (/tee1 & /tee2), etc., need a dedicated forum for open discussion and brain-storming, all while adhering to XDA's policy of staying on topic in the device threads. In addition to the topics outlined, this forum welcomes any questions, concerns and colloquy regarding ROMs, kernels, recoveries, & other development for this device.
LENOVO TAB 3 8/TB3-850F LINKS:
Stock Android 6.0 ROM Thread: https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-t3617594
Bootloader, TWRP & Rooting: https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786/page17
Unbricking/Restoration Tutorial: https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Stock Firmware Partition Images: https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
Lenovo Tab 3 8" User Manual (PDF)
for TB3-850F & TB3-850M: English: https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
RULES:
Rule 1: Be respectful to XDA policies and to one another. We are all here to learn and to grow. The only stupid question is a question not asked;
Rule 2: Read Rule 1.
MotoJunkie01 said:
It has been brought to my attention by XDA Senior Member @pndwal, as well as other members, that topics regarding systemless rooting, dm-verity, force encryption, Trusted Execution Environment (/tee1 & /tee2), etc., need a dedicated forum for open discussion and brain-storming, all while adhering to XDA's policy of staying on topic in the device threads.
Click to expand...
Click to collapse
MotoJunkie01 said:
@pndwal I would like to invite you, first & foremost, to the ROM Q&A for this tablet. I'm hopeful that the Q&A will provide answers to relevant questions like yours, and provide input, user experiences, & ideas for future ROM development for the Tab 3 8.
Click to expand...
Click to collapse
A generous interpretation... Thanks for invitation. I'll be sure to come up with a curly one or two.
For now, could you give a rough idea of what needed changing to bypass force encryption? And also, reasons for pre-rooting? Thanks, PW.
pndwal said:
A generous interpretation... Thanks for invitation. I'll be sure to come up with a curly one or two.
For now, could you give a rough idea of what needed changing to bypass force encryption? And also, reasons for pre-rooting? Thanks, PW.
Click to expand...
Click to collapse
Reasons for pre-rooting are merely as a convenience to the user. Many users will use the stock build I compiled and root themselves, while others will take the more convenient route and flash the ROM which is pre-rooted. The advantages of the rooted ROM are that it will be moderately debloated, deodexed, zipaligned, and will of course have BusyBox binaries pre-injected and the Magisk Systemless User Interface installed.
To bypass force encryption, I first needed to bypass dm-veriity. Both are enabled by default on this tablet within the ramdisk/fstab. So the boot image needed to be unpacked, the values of "1" enabling both dm-verity & force encryption needed to be changed to values of "0", thus disabling both features. The boot image was then repacked and then archived within my ROM installation package (zip).
I'd also like to take a poll to ask whether members want Viper4AndroidFX v2.5.0.5 (with NEON audio drivers) on the custom ROM, in lieu of the Dolby Digital Sound audio package that comes pre-installed on the tablet. Any input would be appreciated.
MotoJunkie01 said:
I'd also like to take a poll to ask whether members want Viper4AndroidFX v2.5.0.5 (with NEON audio drivers) on the custom ROM, in lieu of the Dolby Digital Sound audio package that comes pre-installed on the tablet. Any input would be appreciated.
Click to expand...
Click to collapse
Viper can be installed as a module in magisk. PW
pndwal said:
Viper can be installed as a module in magisk. PW
Click to expand...
Click to collapse
Yes it can, but it breaks the stock camera completely, due to the SELinux policy mod which is installed by the module. If included as a feature of the ROM, I have a workaround which sets SELinux to permissive on boot, instead of permanently disabling the policy from within the kernel. This prevents breaking of the stock camera.
MotoJunkie01 said:
Yes it can, but it breaks the stock camera completely, due to the SELinux policy mod which is installed by the module. If included as a feature of the ROM, I have a workaround which sets SELinux to permissive on boot, instead of permanently disabling the policy from within the kernel. This prevents breaking of the stock camera.
Click to expand...
Click to collapse
I did that in past too. Don't think its needed now.
Viper working fine for me as Magisk module (phone and TB3-850f tablet). SELinux enforcing, camera working fine (incl. video), 2.5.0.4 driver, 2.5.0.5 app.
Seems SELinux policy change no longer required as V4A module for Magisk installs AML (Audio Modification Library) as Magisk framework which no longer requires permissive. Let me know if I'm missing something. PW.
pndwal said:
I did that in past too. Don't think its needed now.
Viper working fine for me as Magisk module (phone and TB3-850f tablet). SELinux enforcing, camera working fine (incl. video), 2.5.0.4 driver, 2.5.0.5 app.
Seems SELinux policy change no longer required as V4A module for Magisk installs AML (Audio Modification Library) as Magisk framework which no longer requires permissive. Let me know if I'm missing something. PW.
Click to expand...
Click to collapse
You are pretty well correct. But, in order to enjoy the full spectrum of the NEON audio drivers, SELinux must go permissive. The Viper version I am speaking of was compiled by Deuteronomy Sound Technologies (and Arise) and is known as Viper4 AriseFX (a modded, themeable, and undoubtedly the most feature packed Viper package available for Android). The Viper module available on Magisk is a bare bones package, and when used in combination with my patched boot image (due to SELinux policy) it breaks the stock camera and causes other instabilities within the ROM.
I'm working also on a custom kernel for the TB3-850F, which will have some audio tweaks available from the kernel itself, as well as some tuneable governors, preset TCP congestion algorithms, etc.
MotoJunkie01 said:
You are pretty well correct. But, in order to enjoy the full spectrum of the NEON audio drivers, SELinux must go permissive. The Viper version I am speaking of was compiled by Deuteronomy Sound Technologies (and Arise) and is known as Viper4 AriseFX (a modded, themeable, and undoubtedly the most feature packed Viper package available for Android). The Viper module available on Magisk is a bare bones package, and when used in combination with my patched boot image (due to SELinux policy) it breaks the stock camera and causes other instabilities within the ROM.
I'm working also on a custom kernel for the TB3-850F, which will have some audio tweaks available from the kernel itself, as well as some tuneable governors, preset TCP congestion algorithms, etc.
Click to expand...
Click to collapse
I see. Perhaps you could explain the benefits of neon audio - I wasn't aware.
Also, would permissive SELinux not break SafetyNet check? Thanks, PW.
pndwal said:
I see. Perhaps you could explain the benefits of neon audio - I wasn't aware.
Also, would permissive SELinux not break Safety net check? Thanks, PW.
Click to expand...
Click to collapse
Yes and no. Depending on how you set the SELinux policy. I've found that setting SELinux to permissive on boot only, by way of a third party app like Kernel Adiutor-Mod or The SELinux Toggler, does not break SafetyNet. However, permanently disabling SELinux as enforcing, by way of modding the kernel itself, has been reported to cause a SafetyNet fail on both custom and stock ROMs.
You raise a good question though, and it is a factor to which I'll be paying close attention during development for this tablet.
I think I've decided to include Viper4AriseFX in my ROM as optional, and available by flashing a separate zip installer subsequent to installing the ROM itself.
By the way @pndwal, you seem to know your way around Android pretty well. What are some other features you would like to see in a custom built ROM for the Tab 3 8?
MotoJunkie01 said:
Yes and no. Depending on how you set the SELinux policy. I've found that setting SELinux to permissive on boot only, by way of a third party app like Kernel Adiutor-Mod or The SELinux Toggler, does not break SafetyNet. However, permanently disabling SELinux as enforcing, by way of modding the kernel itself, has been reported to cause a SafetyNet fail on both custom and stock ROMs.
You raise a good question though, and it is a factor to which I'll be paying close attention during development for this tablet.
I think I've decided to include Viper4AriseFX in my ROM as optional, and available by flashing a separate zip installer subsequent to installing the ROM itself.
Click to expand...
Click to collapse
Optional install sounds like a good idea, especially if SELinux permissive is optional to. I'm hesitant to use permissive environment as many apps etc require enforcing, and attempts to circumvent this, eg Magisk's ability to hide permissive etc, are reportedly not foolproof.
Not sure about attraction with Neon and ARISE, but seems permissive SELinux requirement to use these may be short-lived anyway. See post from today, at https://forum.xda-developers.com/an...d-systems-auditory-research-t3379709/page3125
problem:
NEON Enabled: No
Enabled: No
Status: Abnormal
ETC...
How solve it please?
Magisk 14.3 thats why. You need permissive. ARISE hasnt been updated for the new changes to how magisk handles selinux. Just for now you'll need to switch to permissive to get viper to work. Hopefully we'll have a build up soon to make it work, I know that ZackPTG and Ghost started to update it although i'm not sure on progress.
Hope it helps, PW.
pndwal said:
Optional install sounds like a good idea, especially if SELinux permissive is optional to. I'm hesitant to use permissive environment as many apps etc require enforcing, and attempts to circumvent this, eg Magisk's ability to hide permissive etc, are reportedly not foolproof.
Not sure about attraction with Neon and ARISE, but seems permissive SELinux requirement to use these may be short-lived anyway. See post from today, at https://forum.xda-developers.com/an...d-systems-auditory-research-t3379709/page3125
problem:
NEON Enabled: No
Enabled: No
Status: Abnormal
ETC...
How solve it please?
Magisk 14.3 thats why. You need permissive. ARISE hasnt been updated for the new changes to how magisk handles selinux. Just for now you'll need to switch to permissive to get viper to work. Hopefully we'll have a build up soon to make it work, I know that ZackPTG and Ghost started to update it although i'm not sure on progress.
Hope it helps, PW.
Click to expand...
Click to collapse
I've got Viper4AriseFX fully functional with Magisk v14.3. SafetyNet pass. I'm using a method which does not permanently set SELinux to permissive, but which toggles it to permissive only upon boot.
My pre-patched boot image is probably key to the successful installation as well. I'll list a complete change log of the exact mods once my beta release is ready. From what I'm gathering on logcat, Viper4AriseFX is "seeing" SELinux as permissive, while other system components are seeing the policy as enforcing. I believe I've stumbled upon the key to this SELinux policy dilemma.
MotoJunkie01 said:
By the way @pndwal, you seem to know your way around Android pretty well. What are some other features you would like to see in a custom built ROM for the Tab 3 8?
Click to expand...
Click to collapse
No really unique ideas, but interested in improved performance (speed and battery), battery being pretty good already.
MT8161p CPU specs say Quad-Core, 1.3 GHz, but TB3-850f is limited to 1.0 GHz, so a kernel modified to allow overclocking should achieve 30% boost easily (and CPU can usually go ~30% higher than specs, so perhaps 1.7 GHz or so would be achievable) unless I'm missing something.
Could improve Adoptive Memory (SD) handling, but may have to wait for port to N or O for this as anomalies with handling Dev. manifest values to make moveable apps automatically go to SD (as well as not allowing some even to be moved manually that should move fine) seem to an Android M limitation. (Works beautifully/ as expected on my phone with lineage N, and if Dev. hasn't enabled 'move apps to SD', can 'Force allow apps on external' in Developer Options [Makes any app eligible to be written to external storage, regardless of manifest values].) Guess N / O may be a way off, but would be nice.
Lenovo is now pushing ~30MB OTA update to TB3-850F_S100031_171010_ROW, so you'll probably want to capture / incorporate this in your ROM. (Is it possible to modify OTA update to allow flashing on rooted devices without restoring stock recovery? [Edit: Seems this would require merging differential update with complete files updated, and likely should only be flashed as complete ROM unless stock restored. Saw this: https://twrp.me/faq/officialota.html]) This is not available as a complete downloadable ROM on Russian Websites (lenovo-forums.ru or 4pda.ru) or others as yet as far as I can see.
Hope ideas are helpful, PW.
pndwal said:
No really unique ideas, but interested in improved performance (speed and battery), battery being pretty good already.
MT8161p CPU specs say Quad-Core, 1.3 GHz, but TB3-850f is limited to 1.0 GHz, so a kernel modified to allow overclocking should achieve 30% boost easily (and CPU can usually go ~30% higher than specs, so perhaps 1.7 GHz or so would be achievable) unless I'm missing something.
Could improve Adoptive Memory (SD) handling, but may have to wait for port to N or O for this as anomalies with handling Dev. manifest values to make moveable apps automatically go to SD (as well as not allowing some even to be moved manually that should move fine) seem to an Android M limitation. (Works beautifully/ as expected on my phone with lineage N, and if Dev. hasn't enabled 'move apps to SD', can 'Force allow apps on external' in Developer Options [Makes any app eligible to be written to external storage, regardless of manifest values].) Guess N / O may be a way off, but would be nice.
Lenovo is now pushing ~30MB OTA update to TB3-850F_S100031_171010_ROW, so you'll probably want to capture / incorporate this in your ROM. (Is it possible to modify OTA update to allow flashing on rooted devices without restoring stock recovery? [Edit: Seems this would require merging differential update with complete files updated, and likely should only be flashed as complete ROM unless stock restored. Saw this: https://twrp.me/faq/officialota.html]) This is not available as a complete downloadable ROM on Russian Websites (lenovo-forums.ru or 4pda.ru) or others as yet as far as I can see.
Hope ideas are helpful, PW.
Click to expand...
Click to collapse
You may have read the wrong specs. There has been much confusion between the TB3-850M (which runs on the MT8161p), and the TB3-850F (which runs on the MT6735m). A lot of online sources have misstated the board platforms on these two tablets.
My TB3-850F build.prop clearly lists the board platform as MT6735m, as does the hardware reading given by the SP Flash Tool when I sync the device on my PC. I wish mine did have the MT8161 (1.3GHz) versus the 1.0GHz of my MT6735.
But just to be certain there are not variants of the TB3-850F, read your build.prop via file explorer or build prop editor and let me know if yours is in fact the MT8161p.
Thanks for the heads up on the OTA. I wasn't aware of it and I'll definitely be updating my stock ROM thread accordingly.
Oh to answer your question on the OTAs, yes you can flash an OTA to a rooted/modified device by editing the updater-script and omitting the crypto-hash checks performed during the typical OTA installation, and by editing the incremental target and source lines (or omitting them entirely).
Just got the 33mb OTA captured. Looks like there are the usual bug fixes & stability improvements, but also the KRACK exploit has been patched, the partition index updated, and kernel updates. I'm currently compiling an up-to-date stock ROM with TWRP flashable installer.
MotoJunkie01 said:
You may have read the wrong specs. There has been much confusion between the TB3-850M (which runs on the MT8161p), and the TB3-850F (which runs on the MT6735m). A lot of online sources have misstated the board platforms on these two tablets.
My TB3-850F build.prop clearly lists the board platform as MT6735m, as does the hardware reading given by the SP Flash Tool when I sync the device on my PC. I wish mine did have the MT8161 (1.3GHz) versus the 1.0GHz of my MT6735.
But just to be certain there are not variants of the TB3-850F, read your build.prop via file explorer or build prop editor and let me know if yours is in fact the MT8161p.
Thanks for the heads up on the OTA. I wasn't aware of it and I'll definitely be updating my stock ROM thread accordingly.
Oh to answer your question on the OTAs, yes you can flash an OTA to a rooted/modified device by editing the updater-script and omitting the crypto-hash checks performed during the typical OTA installation, and by editing the incremental target and source lines (or omitting them entirely).
Click to expand...
Click to collapse
Yes, I'd forgotten this confusion.
Actually, didn't check online sources, but assumed Phone Tester was reporting correctly. It gives CPU Info: MT8161p.
Just checked Kernel Auditor which gives MT8161p as vendor, but MT6735 as hardware.
CPU-Z gives MT6735 as SoC.
My build.prop also gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P.
Russian 4PDA forum gives 850f Processor Type: MT8161, with MT8735 for 850M variant. (http://4pda.ru/devdb/lenovo_tab3_8:850f)
So it's hard to know what or who's correct, but looks to me that newer CPUs have likely been installed on boards originally designed for MT6735. (My CPU could actually be MT8735 as given by build.prop if Lenovo had excess chips from 850M, or simply decided to use these in both models. - I guess they may even have started with MT6735 for 850f before progressively using MT8161 and MT8735.)
So seems to me to be in the realms of possibility that a kernel allowing overclocking may just render spectacular results (as long as later CPUs were in fact used, and these are not crippled by an older board chipset.) But then, I may be way off base . . . Let me know your thoughts. PW.
pndwal said:
Yes, I'd forgotten this confusion.
Actually, didn't check online sources, but assumed Phone Tester was reporting correctly. It gives CPU Info: MT8161p.
Just checked Kernel Auditor which gives MT8161p as vendor, but MT6735 as hardware.
CPU-Z gives MT6735 as SoC.
My build.prop also gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P.
Russian 4PDA forum gives 850f Processor Type: MT8161, with MT8735 for 850M variant. (http://4pda.ru/devdb/lenovo_tab3_8:850f)
So it's hard to know what or who's correct, but looks to me that newer CPUs have likely been installed on boards originally designed for MT6735. (My CPU could actually be MT8735 as given by build.prop if Lenovo had excess chips from 850M, or simply decided to use these in both models. - I guess they may even have started with MT6735 for 850f before progressively using MT8161 and MT8735.)
So seems to me in the realms of possibility that a kernel allowing overclocking may just render spectacular results (as long as later CPUs were in fact used, and these are not crippled by an older board chipset.) But then, I may be way off base . . . Let me know your thoughts. PW.
Click to expand...
Click to collapse
Yeah I agree with you wholeheartedly that overclocking - at least moderately - could provide some benefit. I'm seeing that our current 1.0GHz maximum clock could safely be overclocked to about 1.33GHz. Definitely something I will be considering. I've been able to optimize this device's meager 1GB RAM by zipaligning the apk files, and by setting a maximum background process limit to build.prop. I've also found that setting the stock kernel's Adaptive Low Memory Killer to Very Aggressive helps as well.
I've installed the OTA and it seems to improve general stability of the device, and provides us with much needed security patches. I'll be updating my stock ROM to the most recent version later today. Here is a link to the captured OTA if anyone is interested in exploring it. However, in order to flash it to a rooted/modified device, the updater-script first needs to be modified. But again, I'll have the updated build posted later today.
OTA_TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/11xo-7X06ST1RV8X5TJHjM5o2MHfcsNhl/view?usp=drivesdk
MotoJunkie01 said:
Yeah I agree with you wholeheartedly that overclocking - at least moderately - could provide some benefit. I'm seeing that our current 1.0GHz maximum clock could safely be overclocked to about 1.33GHz. Definitely something I will be considering. I've been able to optimize this device's meager 1GB RAM by zipaligning the apk files, and by setting a maximum background process limit to build.prop. I've also found that setting the stock kernel's Adaptive Low Memory Killer to Very Aggressive helps as well.
I've installed the OTA and it seems to improve general stability of the device, and provides us with much needed security patches. I'll be updating my stock ROM to the most recent version later today. Here is a link to the captured OTA if anyone is interested in exploring it. However, in order to flash it to a rooted/modified device, the updater-script first needs to be modified. But again, I'll have the updated build posted later today.
OTA_TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/11xo-7X06ST1RV8X5TJHjM5o2MHfcsNhl/view?usp=drivesdk
Click to expand...
Click to collapse
Great. What do you make of build.prop entry: ro.lenovo.cpuinfo=MT8735P? PW.
pndwal said:
Great. What do you make of build.prop entry: ro.lenovo.cpuinfo=MT8735P? PW.
Click to expand...
Click to collapse
It's simply a typo that was made in build.prop I believe. Going by ro.board.platform, they seem to have it correct with the 6735 entry. I was just messing with some components of the unpacked boot image from this device, and it seems that except for the SoC differences, the 850M and 850F are otherwise identical. Of course, the 850M, by way of its mt8161p, has full SIM & 4G/LTE data support. In our variant, the SIM slot (next to the micro SD card slot) is blocked off, whereas it's fully accessible in the 850M.
P.S, if you're rooted, add this line to build.prop and let me know if you see a difference in RAM optimization: ro.config.low_ram=true

Categories

Resources