For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
If you would like to contribute to Evervolv, please visit our Gerrit Code Review.
Current version: Based off 9.0 (Pie)
Features:
Extended PowerMenu
Battery %
Battery icon shapes
Volume button music control
Lineage Styles
Key rebinding
Expanded desktop
Bug Reporting:
Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use EVPaste to post your logs.
Downloads:
Available downloads
Source:
Evervolv Github
Branch: p-9..0
Changelog:
Nightly changelogs are available on download page (EVUpdater too!)
or you can view them at the Evervolv Gerrit
Bug list:
Bluetooth (In progress)
Camera (In progress)
Donations:
If you wish to donate please do so here (Paypal)
Can't be installed with TWRP 3.1.0.
Error message is "wrong device".
Does it include swap partition (as latest DU build)?
Gesendet von meinem Mi MIX 2S mit Tapatalk
Geomatic said:
Can't be installed with TWRP 3.1.0.
Error message is "wrong device".
Does it include swap partition (as latest DU build)?
Gesendet von meinem Mi MIX 2S mit Tapatalk
Click to expand...
Click to collapse
I'll investigate when I get time tonight. The swap partition is not updated yet to match DU, however the rest of the performance enhancements are.
elginsk8r said:
I'll investigate when I get time tonight. The swap partition is not updated yet to match DU, however the rest of the performance enhancements are.
Click to expand...
Click to collapse
I was able to install the ROM using TWRP by removing the following code from the updater-script
Code:
assert(getprop("ro.product.device") == "tenderloin" || getprop("ro.build.product") == "tenderloin" || abort("E3004: This package is for device: tenderloin; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: hp/hp_tenderloin/tenderloin:6.0/MRA58K/2256973:user/release-keys");
But it goes into a boot loop, it does not work.
HP_TOUCHPAD said:
I was able to install the ROM using TWRP by removing the following code from the updater-script
Code:
assert(getprop("ro.product.device") == "tenderloin" || getprop("ro.build.product") == "tenderloin" || abort("E3004: This package is for device: tenderloin; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: hp/hp_tenderloin/tenderloin:6.0/MRA58K/2256973:user/release-keys");
But it goes into a boot loop, it does not work.
Click to expand...
Click to collapse
what twrp are you using? im using twrp 3.2.1 from flintman
elginsk8r said:
what twrp are you using? im using twrp 3.2.1 from flintman
Click to expand...
Click to collapse
The TWRP version I am using is 3.1.0-0 from Flintman from here:
http://downloads.codefi.re/evervolv/misc
The ROM install after removing the verification for the device, but it won't finish booting not even the animation starts, then it reboots again.
Can you provide the link to the TWRP 3.2.1 from Flintman?
here you go. I'm going to recharge my device and make sure I posted the build I have running on my device.
elginsk8r said:
here you go. I'm going to recharge my device and make sure I posted the build I have running on my device.
Click to expand...
Click to collapse
I flashed the TWRP 3.2.1-0 version and flashed the ROM file you posted.
It does not boot into Android, after selecting Android from the moboot menu it displays and active screen but black, after a minute it reboots.
HP_TOUCHPAD said:
I flashed the TWRP 3.2.1-0 version and flashed the ROM file you posted.
It does not boot into Android, after selecting Android from the moboot menu it displays and active screen but black, after a minute it reboots.
Click to expand...
Click to collapse
That's probably because the Android uImage isn't being removed, which is what the DU uImage is named. Delete it manually and reinstall the ROM. Then you'll have the Evervolv uImage to boot.
So after testing and rebuilding, it looks like i forgot to push a bionic commit which is breaking libs. So when I resynced and rebuilt before uploading the commits never got pulled in
shumash said:
That's probably because the Android uImage isn't being removed, which is what the DU uImage is named. Delete it manually and reinstall the ROM. Then you'll have the Evervolv uImage to boot.
Click to expand...
Click to collapse
I always test a new ROM on a complete clean Tablet, nothing in boot.
But by looking at the updater-script, that is what would happen.
Code:
package_extract_file("moboot.splash.Android.tga", "/boot/moboot.splash.Android.tga");
package_extract_file("moboot.default", "/boot/moboot.default");
run_program("/sbin/busybox", "rm", "/boot/uImage.CyanogenMod");
run_program("/sbin/busybox", "rm", "/boot/moboot.splash.CyanogenMod.tga");
run_program("/sbin/busybox", "rm", "/boot/uImage.Dirty-Unicorn");
run_program("/sbin/busybox", "rm", "/boot/uImage.Evervolv");
run_program("/sbin/busybox", "rm", "/boot/moboot.splash.Evervolv.tga");
It should removed everything and then copy the new uImage.
I did installed it manually, with the same results.
---------- Post added at 01:30 AM ---------- Previous post was at 01:28 AM ----------
elginsk8r said:
So after testing and rebuilding, it looks like i forgot to push a bionic commit which is breaking libs. So when I resynced and rebuilt before uploading the commits never got pulled in
Click to expand...
Click to collapse
Good to know you were able to find the needle in the haystack!
Here are the settings that I have applied to get the most out of the Tablet, is very basic and simple if you decide to incorporated into your ROM it will be as fast and stable as the current DU v13.
The Boost Optimize settings for all Android ROM ever created for the HP Touchpad
new build uploaded that actually boots, swap was added as well
elginsk8r said:
new build uploaded that actually boots, swap was added as well
Click to expand...
Click to collapse
This is to confirm that the new posted build of Evervolv 9, boots and works!
It also using the swap partition, is fast and smooth.
I will take more time and report any suggestions.
Thank you for providing this new ROM!
HP_TOUCHPAD said:
This is to confirm that the new posted build of Evervolv 9, boots and works!
It also using the swap partition, is fast and smooth.
I will take more time and report any suggestions.
Thank you for providing this new ROM!
Click to expand...
Click to collapse
Extremely important:
If the Tablet goes to sleep or standby it will not wake up, the user may think that the Tablet is brick (is not).
A hard reset is require and the buttons needs to be hold down for long time.
I also notice from the Ramdisk files that KMS and CPU boost are enable. From my testing, those modules create more problem than the benefit it try to provide, more useful on a phone.
The idea of using the swap partition is to allow Android to place processes there without killing it or creating an unstable system. KMS is the opposite to swap it will Kill anything to make more RAM. The CPU Boost will make the CPU jump to a higher frequency only when touch, that will create double tap when typing and not an smooth user experience. Once the governor is set to performance the CPU will work just like it does on a PC, the way all computer works.
HP_TOUCHPAD said:
Extremely important:
If the Tablet goes to sleep or standby it will not wake up, the user may think that the Tablet is brick (is not).
User BGrosse tested the ROM and made me aware that there was not a problem wake up the tablet.
I re-tested today using the Home button, or menu button and it does wake up.
A hard reset is require and the buttons needs to be hold down for long time.
It seems as the power saving is very aggressive.
When connected to PC, when screen is off it will lose connection.
I also notice from the Ramdisk files that KMS and CPU boost are enable. From my testing, those modules create more problem than the benefit it try to provide, more useful on a phone.
The idea of using the swap partition is to allow Android to place processes there without killing it or creating an unstable system. KMS is the opposite to swap it will Kill anything to make more RAM. The CPU Boost will make the CPU jump to a higher frequency only when touch, that will create double tap when typing and not an smooth user experience. Once the governor is set to performance the CPU will work just like it does on a PC, the way all computer works.
Click to expand...
Click to collapse
BGrosse flashed the Pico Open Gapps and the Android Keyboard (AOSP) keeps stopping.
I can verify that is does happen with mine as well. That is an easy fix, a flash zip file can be provided to fix the issue as I do with the other ROMS.
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
@elginsk8r
If you allow me I can apply all my settings that I have done to all the other ROMs and all should be fix.
I only need a direct link to the specific kernel version been use for this ROM, and I will re-compile a new version.
Not tested now, but thank you!
thanks a lot for the rom
HP_TOUCHPAD said:
Extremely important:
If the Tablet goes to sleep or standby it will not wake up, the user may think that the Tablet is brick (is not).
A hard reset is require and the buttons needs to be hold down for long time.
I also notice from the Ramdisk files that KMS and CPU boost are enable. From my testing, those modules create more problem than the benefit it try to provide, more useful on a phone.
The idea of using the swap partition is to allow Android to place processes there without killing it or creating an unstable system. KMS is the opposite to swap it will Kill anything to make more RAM. The CPU Boost will make the CPU jump to a higher frequency only when touch, that will create double tap when typing and not an smooth user experience. Once the governor is set to performance the CPU will work just like it does on a PC, the way all computer works.
Click to expand...
Click to collapse
Ksm does not kill anything. Is called the kernel same page merger and it allows for any program to share common pieces of code in ram instead of creating duplicates and it has a purpose in reducing ram usage. I use it on servers and it does wonders you can run 24 VMS in the ram space of 6.in no way it's involved in the oom mechanism
sireangelus said:
Ksm does not kill anything. Is called the kernel same page merger and it allows for any program to share common pieces of code in ram instead of creating duplicates and it has a purpose in reducing ram usage. I use it on servers and it does wonders you can run 24 VMS in the ram space of 6.in no way it's involved in the oom mechanism
Click to expand...
Click to collapse
Correction: I double check the kernel modules and all is removed.
The wakelock settings is different and causing the Tablet not to wake up.
You are correct, is the Low Memory Killer ( LMK ) and not Kernel Samepage Merging (KSM)
Both are removed, but settings are present in the Ramdisk files, but are not active anyways.
Tested the ROM and youtube videos does not play, audio does but not the images.
Related
Rom (Ice Cream Sandwich):
A Near stock image, modified for a clean root, busybox install
ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
(MD5: 7e9fe5642b6e082fb4382288337d8dfa)
The long overdue update to my previous Honeycomb rom
==~== Requirements ==~==
This rom requires the unlocked ICS bootloader, I also recommend my A500 Public Recovery, however all recoverys patched for the new bootloader ought to allow installation of the rom.
Bootloader install instructions are: here thanks to civato. Note for step 4 simply ensure my update zip above is either in on the device instead of the ones listed. Note instructions below before actually flashing the rom.
Additional information can be found at Skrilax_CZ's bootloader development thread here
And my A500 Public Recovery development thread here
==~== Installing ==~==
Once you have the new bootloader and ICS recovery installed (again preferably the A500 Public Recovery but any ought to work)
Cleaning your tablet:
If you are attempting to upgrade the tablet without wiping (and there is no need to wipe if you are currently running my acer7.014.14 rooted image
Select "cleanup tab" in the main menu of the A500 Public Recovery
(If you are using another recovery, select the options for a. Wipe Cache, b. Wipe Dalvik Cache, and c. Fix Permissions)
Install the rom:
Select "install zip from sdcard" and navigate to ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
Thats it
==~== Root ==~==
Applications are granted Superuser access from ChainsDD's Superuser.apk as usual (a request asking you will appear when an application requests root, and permissions granted before the upgrade may still be active post upgrade)
adb shell: ADB by default will not have root access here you have the following options:
> if you run 'adb root' all adb operations will have root until reboot (aka 'adb shell' and 'adb remount')
> If you have a non-root 'adb shell' you can switch to root with the 'su' command
> If you wish to restore the permanent adb root on boot add the following line to the build.prop 'service.adb.root=1' this will force the old behavior of root always via adb without using the 'adb root' command.
This change has been made as its a little more secure, (However obviously still lets anyone with access to the USB port access to all the tablets data)
==~== Features ==~==
This rom is intended for users that wish a nearly stock system configuration, however either need root and busybox, or enjoy conducting more advanced tasks at the command line and wish a smooth root experience.
In addition some other small mini-fixes have been applied to the image in hope of a smooth experience.
Here is a list of the features and changes in the rom
Modified ADB to allow adb root to operate without changing the production build properties
Kernel patched to allow system remount
Busybox built from CM9 source tree and integrated into the rom
runparts (ie /system/etc/init.d functionality)
GPS lto fix thanks to waydownsouth
FDUpdater (ie system update) removed to not be prompt for an update you can't install.. if you want it the original app is in the system folder of the update.zip, (FDUpdater.apk) its not odexed so install normally)
Kernel modules md4.ko sha512_generic.ko and cifs.ko added to the rom (md4/sha512 is loaded on boot via an init.d script, users of cifs need to check the "Load cifs module" option in CifsManager.
Added Superuser
DHCP Infinite Lease bugfix (why has google not fixed this) applied as a patch to the framework.odex
Rom is still odexed (and I re-odexed the one changed odex for the DHCP patch)
Developers wanting more details or the source to anything I changed can see this detailed modification guide: http://pastebin.com/ApUjMDJ7
Note to anyone wishing to make a modification to the rom they are flashing, everything in the system folder of the update.zip is unchanged from the original rom. (when flashed the system is patched and augmented via various files and tools in the custom directory, also the boot image is pre-patched)
==~== Extras and Addons ==~==
** Overclocked test kernel: See my ezT20 kernel here (previously OCTestV3 here
(kernel last updated June 18th 2012)
** Disk IO enhancement: significantly increase diskio scores, and make the table slightly more responsive when reading/writing to flash: On this post
(diskIO last updated June 5th 2012)
==~== Tips and Tricks ==~==
This section is where I try to explain how to get the most of your tablet, and solutions to common complaints due to changes between versions.
-----) Rom "Bloat" (------
First half of what people call rom bloat is not quite true, (there is such a thing, and problems related to it)
Our tablets have 590MB system partition, a 97MB vendor partition, a 1GB cache partition, and the rest of your tablets space in a data partition (mine is 27GB, but if you have a smaller tablet model it will be less) All roms will have currently the same split between the partitions.
Its only that last partition that contains your data, the system/vendor partitions are by default read only, and the cache partition is temporary data.
System apps are on the two read only partitions, thus removing them for the most part will not cause more data to be available to your apps. Also this is storage space so having more "free" will not speed up your device (well as long as we are not too close to full.. and this rom is not)
Most of these apps play nice, they don't run unless you select them thus you can ignore they are on your tablet and all will be just as fast as if they were never installed
There is however one *Problem* Applications pre-installed that run constantly in the background that you the user are not interested in.
Solution: Freezing apps
* Goto Settings-> Apps-> All
* For any of the following that you do not use:
> Photo Browser 3D
> SocialJogger
> Acer Media
Select the app,
Choose Disable
Clear Data
If you use the app, obviously keep it enabled, also you can return to this screen and re-enable the app.
-----) Screen flickering/brightness oddities (------
I have had some brightness issues initially, simple fix was to go into settings->display->brightness uncheck auto bightness, lower the meter, and re-check auto brightness
-----) Sluggish system (------
Make sure on first boot you give the system some time (2h/3h after upgrading or re-installing where there is a large collection of media on the tablet) before measuring speed, as the system may be still sorting/indexing tablet data and will speed up when done.
Also while apps are installing the system may behave slower (if you have many market updates happening in the background)
Otherwise check running processes in settings to see if anything may be slowing down your tablet in the background (Settings -> Apps -> Running)
==~== Credits ==~==
civato - for his guide to installing the new bootloader and some testing of some of the tools I use to patch the rom up
waydownsouth - for the GPS patches (and work on CM9 for our tablets as it helped create some of the utilities in use here)
CyanogenMod and Team - For the idea of the root change, modifications to the bustybox build, and Koush's ClockworkMod recovery
vache - various insight all over XDA on how our device works (and leaks but this build is from the official OTA I recived)
Skrilax_CZ - for the unlocked bootlaoder, without which we couldn't run these roms
And the many others that provide development insight, source code, and examples here on XDA
2nd Post
reserved for future
Nice and congratulations with your release.
I will ad a link to this rom in the unlocked bootloader guide.
Overclocked kernel [May 23rd 2012]
(wow I think we can hear crickets in here..)
Anyway using the now released source code from acer, and richardtrip's OC patches from HC I now have an overclocked kernel.
As of V3 I also have the voltage controls patched up from richardtrip's kernel.
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Instructions are simple: flash from recovery
Links to the github source and other information on the AcerOCTest kernels is in this related notecard
While I've only tested it on this rom, the installer is using koush's anykernel logic (or one of my own flavors of that logic anyway) and thus this ought to cleanly install on any rom based on the stock ICS kernel regardless of the tweaks the rom creator may have added.)
Also I've not had much time to test so let me know if there are issues
----
List of all versions:
V3 - AcerOCTestV3_S.zip (md5: 6907e7585fedf534261cc8ebe23d824a) May 23rd 2012
V2 - AcerOCTestV2_S.zip (md5: da01a90dda3916ec55ebb62bbb1164f1) May 22rd 2012
V1 - no public binary (caused reboots on tablet sleep)
Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.
Jigga0o7 said:
Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.
Click to expand...
Click to collapse
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
edit: although I'll look into it some may be a new verification in the updated kernel. the tegra2 OC logic is much more complicated than the msm logic I'm used to on the HTC dream.. I'm more worried about reboot-on-wake bugs I had in earlier revisions
ezterry said:
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
Click to expand...
Click to collapse
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.
Jigga0o7 said:
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.
Click to expand...
Click to collapse
looking closer its a but..
So now I have two OC tests I've made.. the first one I didn't publish because while it could go > 1.2 it crashed when you put the tab to sleep. (at least when USB wasn't connected)
This one crashes when you go over 1.2.
maybe if a combine them I can get something that works...
Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.
Jigga0o7 said:
Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.
Click to expand...
Click to collapse
No.. well maybe but you not getting that far.. its a kernel BUG condition, meaning some code found some invalid input and refused to process it, instead triggered a reboot.. looking at the diff of mycode and the code in the CM thread.. no logic is different so i'll need to poke min/max rail voltages. (still sorting out all the voltages and CPU speeds.. the dream had it all in one large table .. here it seems spread out in various places between two files..)
(I'll also try to include the voltage manipulation patches just making sure things are stable first thus 1.2ghz is a better testing speed for me than trying to Max my device)
As for CM..it seems to have many interesting features.. but at some point I'm not sure its direction matches my interests.. (maybe its just become too much of a kitchen sink i don't know, that or too much now in aosp) I'm sure to look at it but probably start an aosp build with cherrypicked features I like.. until then this tweaked ics rom will need to do.
Fyi I haven't had a single issue on your kernel.
Been waiting on this! Thanks ezterry.
Jigga0o7 said:
Fyi I haven't had a single issue on your kernel.
Click to expand...
Click to collapse
Well next version will have voltage controls and working higher overclock speeds
(just ironing out some minor issues with the voltage control)
Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Just had a other pm today confirming it worked.
And I'm testing your modules and OC zImage with this modded in the boot.img-ramdisk (and my other tweaks) and I don't get any SoD , screen off , back on no problem.
Also confirming 1200 is max , over that it will reboot.
Ezterry,
Thanks!
very nice kernel, I flashed the 'civato' version to avoid SOD ...
Works nicely in 1.2 Ghz...
Btw, the old "No-Frills CPU control" apk doesn't apply the upper 1.2 Ghz frequency at Boot as asked.
Do you know another tool working to apply OC at boot?
(I'm using Civato's last version of flexreaper ROM)
=================================================================
>>>>> I have found a solution: I now use System Tuner PRO with its OC setting and it works <<<<<
=================================================================
civato said:
Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Click to expand...
Click to collapse
.. I think this solution has nothing to do with the debug variable and everything to do with *forcing* the user to install a ICS kernel and stop messing around with the HC kernel they had earlier. (since you are installing a new boot.img)
So says the code anyway. If you want to prove it wrong after the crash + quick reboot get your users to dump the last_kmsg and output of dmesg so we can actually debug what is going on.. well unless its just the wrong kernel
But if the "obecalp" works to get some your users to install the right thing and so they fix there own problem.. so be it.
--
I have to inform users of my rom its no longer my rom if they install one of your (or anyone else's) full boot images and not to complain of any resulting bugs here.. If anyone with this rom has a SoD (none reported yet.. but I block installation on the old HC bootloader) let us know if you have such an issue. (just want to add if the full boot image was modified from the one in this rom, and intended for users of this rom that isn't an issue.. the issue is when its for another rom)
Its a bit different when you flash my update on another rom, since I only swap the kernel and leave the ramdisk as is, (by unpacking and repacking the boot.img) the rom designers changes stay intact.. well unless they had a kernel module that I've not included.. but even then we will need to re-build that module)
and you can test this after boot enter terminal and run echo '3> /sys/module/wakelock/parameters/debug_mask' that is the default.
(If it is disabled it just won't print the list of wakelocks to the kernel log on suspend..)
UPDATE @@
http://forum.xda-developers.com/showpost.php?p=26432810&postcount=4
ezterry said:
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Click to expand...
Click to collapse
Hopefully fixed the max speed bug, and added in the voltage controls.
Not much else yet has changed. but seems stable.
Its the same anykernel package as last time so it should cleanly swap the kernel (leaving the previous ram disk) for any ICS stock kernel based rom.
(Is there one app out there that actually knows how to successfully set *both* cores frequency and set voltage on boot, without giving the world access to the /sys files [so a malicious app cant overclock+fry the device or under clock it so it feels painfully slow]... soon I'll just write an init.d script for myself to echo the values directly into the kernel settings /rant)
I use setcpu.
civato said:
I use setcpu.
Click to expand...
Click to collapse
I don't like that he (and has always) granted global write permissions to the /sys/ files controlling the CPU/Voltage settings .. and it was acting flaky on voltage settings on boot.
Voltage Control looked good until a verification in /sys indicated if left the second CPU core at 1GHz
Now poking system tuner/system tuner pro.. many interesting features. Not sure they quite understand use root to write the value.. or set the file to your own ownership..
*ANYWAY*
you can check these yourself manually at the command line/adb shell:
CPU0: /sys/devices/system/cpu/cpu0/cpufreq
CPU1: /sys/devices/system/cpu/cpu1/cpufreq
current status of the voltages is in the readonly: frequency_voltage_table
list readonly of available frequencies is: scaling_available_frequencies
list readonly of available governors: scaling_available_governors
the current min frequency: scaling_min_freq
the current max frequenct: scaling_max_freq
the current cpu governor: scaling_governor
the current undervolt levels (negative values are over volting): UV_mV_table
UV_mV_table is in the same order as frequency_voltage_table, and if written to with the same number of values will update the voltage levels.
I got a question , why :
sha512_generic.ko = what does this do ?
modules.order = why does it need to know the order ?
Hello there! I have created a small flashable .zip with some tweaks I came up with, while experimenting with my MIUI V4 by geno.
This should be compatible with CrazyMIUI (as it is based on geno's release), but only if you have the same release number.
Before flashing make sure you have the same MIUI version as the patch (see version number below). Otherwise you can make the changes on your own with a root file manager at the specific version you are using.
Finally, if you don't want any of the included mods, you can delete the corresponding file from the .zip before flashing. For example lets say you don't want Google play to be installed. Open the .zip file, go to system/app/ and delete the GooglePlayStore.apk file. Then flash normally. The update script manages to flash only the included files/tweaks so you should have no problems.
In case you have problems after flashing, fix permissions.
Tested with CWM 5.5.0.4.
Download at the attachments.
UPDATE: If you have root problems check out this post
http://forum.xda-developers.com/showpost.php?p=31285923&postcount=350
Version [2.10.12] Changelog:
NOW BASED ON MIUI PORTUGAL (SHOULD WORK ON GENO'S TOO)
FIX PERMISSIONS FROM CWM AFTER FLASHING. I don't know why but the permissions I am setting doesn't work even though they are the same...
...the rest are the same...
Version [2.9.14] Changelog:
...same
Version [2.9.7] Changelog:
(SAME) Erase the /system/media/video folder. This folder includes some video samples but are useless. I delete them everytime in order to have some more space at the system.
(NEW) Erase some Chinese apps. (supermarket, baidu input, root explorer)
(SAME) Add Google Play (v.3.8.17) as system app because otherwise system can't always update/install apps.
(NEW) Add google Talk because it was killed by the system if it is installed as a user app.
(SAME) build.prop changes. Set composition to gpu, default language english, non-killable launcher.
(SAME) /system/etc/gps.conf tweaks. Use European gps server.
(SAME) /system/etc/enhanced.conf tweaks. Enable ZRAM (SIZE: 80), enable VSYNC (No screen tearing, lower battery consumption, but I think lower benchmark scores), default I/O sheduler: noop.
(SAME) /system/etc/firmware/wlan/qcom_cfg.ini tweaks. Based on sbasil's patch for Aurora. I have doubled my wifi speed!
(SAME) tweaked media_profiles.xml in order to record videos as mp4 (instead of 3gp).
(NEW) added binaries and init.d folder for init.d scripts compatibility. Now every script inside the /system/etc/init.d folder will be executed at startup. A 00test script is by default there which, if it is executed, creates a Test log inside /data. Use it to test if the scripts are executed correctly.
(NEW) fixes some permissions.
Version [2.8.31] Changelog:
(SAME) Erase the /system/media/video folder. This folder includes some video samples but are useless. I delete them everytime in order to have some more space at the system.
(NEW) Add Google Play (v.3.8.17) as system app because otherwise system can't always update/install apps.
(SAME) build.prop changes. Set composition to gpu, default language english, non-killable launcher.
(SAME) /system/etc/gps.conf tweaks. Use European gps server.
(SAME) /system/etc/enhanced.conf tweaks. Enable ZRAM (SIZE: 80), enable VSYNC (No screen tearing, lower battery consumption, but I think lower benchmark scores), default I/O sheduler: noop.
(SAME) /system/etc/firmware/wlan/qcom_cfg.ini tweaks. Based on sbasil's patch for Aurora. I have doubled my wifi speed!
(SAME) tweaked media_profiles.xml in order to record videos as mp4 (instead of 3gp).
Version [2.8.24] Changelog:
(SAME) Erase the /system/media/video folder. This folder includes some video samples but are useless. I delete them everytime in order to have some more space at the system.
(NEW) Doesn't add Google Talk apk and Google Play (v.3.7.15) as these can be installed as user apps.
(SAME) build.prop changes. Set composition to gpu, default language english, non-killable launcher.
(SAME) /system/etc/gps.conf tweaks. Use European gps server.
(SAME) /system/etc/enhanced.conf tweaks. Enable ZRAM (SIZE: 80), enable VSYNC (No screen tearing, lower battery consumption, but I think lower benchmark scores), default I/O sheduler: noop.
(SAME) /system/etc/firmware/wlan/qcom_cfg.ini tweaks. Based on sbasil's patch for Aurora. I have doubled my wifi speed!
(NEW) tweaked media_profiles.xml in order to record videos as mp4 (instead of 3gp).
Version [2.8.17] Changelog:
Erase the /system/media/video folder. This folder includes some video samples but are useless. I delete them everytime in order to have some more space at the system.
Add Google Talk apk and Google Play (v.3.7.15)
build.prop changes. Set composition to gpu, default language english, non-killable launcher.
/system/etc/gps.conf tweaks. Use European gps server.
/system/etc/enhanced.conf tweaks. Enable ZRAM (SIZE: 80), enable VSYNC (No screen tearing, lower battery consumption, but I think lower benchmark scores), default I/O sheduler: noop.
/system/etc/firmware/wlan/qcom_cfg.ini tweaks. Based on sbasil's patch for Aurora. I have doubled my wifi speed!
UPCOMING:
some init.d tweaks from AOKP ROM. Under testing...
anything else you ask and I know how to do it
thanks to dzo, geno, sbasil, crazyGamerGR.
nice
zram really work? I had tried to edit /system/etc/enhanced.conf manually (on miui 2.8.3), but did not achieve any effect..
almelion said:
zram really work? I had tried to edit /system/etc/enhanced.conf manually (on miui 2.8.3), but did not achieve any effect..
Click to expand...
Click to collapse
If you look at /system there should be a log.txt which has some boot information. One of these should be open zram... if it is on at the enhanced.conf file.
In terms of performance i noticed fewer redraws and faster opening of apps... but maybe it is a placebo...
Sent from my U8800
spirosbond said:
but maybe it is a placebo...
Click to expand...
Click to collapse
please enter 'free' in the console and look at the 'swap' line. if the column 'total' has a value other than 0, this is not a placebo :cyclops:
ps. at the moment I am unable to install miui and test this tweak..
pps. sorry for my english
ROM will be great when sources will be optimized, but tweaks is like a push candy to dead man. Modifications of how ROM works - yes, but tweaks for performance...
As I saying - customize the source, but not that what goes after when all of customizers understand this meaning all goes on the next level of good things
Sent from my ragelis
bronxitas said:
ROM will be great when sources will be optimized, but tweaks is like a push candy to dead man. Modifications of how ROM works - yes, but tweaks for performance...
As I saying - customize the source, but not that what goes after when all of customizers understand this meaning all goes on the next level of good things
Sent from my ragelis
Click to expand...
Click to collapse
I agree 200% with that but as long as i don't have the time to mod sources and kernel i am just waiting as you are... I am pretty sure that geno isn't making any progress for U8800 apart from updating the MIUI sources so I append my hopes on MIUI. I think there is room for improvement in 3.0.8 kernel and the smali codes of our patchrom, in order to be optimized for MIUI but i cannot be sure of that as long as i haven't dig the codes enough...
Apart from that i am having better performance with these tweaks so i thought sharing them.
Sharing is caring
Cheers and thanks !
Sent from my U8800
New version is up. I hope you'll enjoy it.
Cheers!
can it have Multilingual?and how to install?
sory for my english,very bad
Hi ! Original post http://bbs.anzhi.com/thread-5534191-1-1.html
u8800's oil still remember stockwell, if you remember his MIUI x5settings (device settings), today brought a modified version of a device is set, the source code from stockwell wrote Part 2, I hope you like it, U8800 have not tried, but guess no problem [Software Description] Software Name: Huawei to set the software version: v1.1 software author: stockwell, Ry09iu Updated: 20120828 test models: Huawei u8800pro test rom: Alastor MIUI 2.8.25 software, introduced: - remove the original x5settings in useless settings, including audio settings, vibration intensity u8 + useless - interface changed slightly - Repair set back the progress bar when setting interface automatic recovery issues - support the four kings buttons vibration feedback of the open and close, also supports vibration intensity adjustment - Support internal / external memory options (if you have an external sd card, this Do not alter, can not otherwise connected to the computer mount internal / external card) - support the button backlight turned on and off, divided into closed and re-open the two options, shut down permanently closed, that is, whether to restart or not would have been shut down, turn it back on, you need to lock screen and then unlock to take effect - Support for I / O scheduling mode settings - Support for FPS set divided into unlocking FPS and re-locked the two options, I will not say the role, are permanent, restart as effective (warning : Do not repeat unlock locked operation, avoid unknown problems) [Support models Huawei models can try 2.3/4.0, support init.d script from the start, you can try [Note 】 - temporarily does not support the official package from the start should be no problem with the script rom support init.d, the next version update will try to support the official package - If you use the ROM keyboard light is not bright, then turn on the keyboard light invalid
Click to expand...
Click to collapse
Igory0k said:
Hi ! Original post http://bbs.anzhi.com/thread-5534191-1-1.html
Click to expand...
Click to collapse
Thanks! Unfortunately, it doesn't save the settings across reboots...
New version is up.
Cheers
spirosbond said:
New version is up.
Cheers
Click to expand...
Click to collapse
Hi frnd....How improved it is then .24 ver. I have sent my Phone for repair. ,,,
krish_nank said:
Hi frnd....How improved it is then .24 ver. I have sent my Phone for repair. ,,,
Click to expand...
Click to collapse
Unfortunately, I haven't noticed any differences/improvements yet...
I just can't manage to get root connection with any of miui v4 rom's, except with crazygamer rom...
I tried the super user and failed too, am i doing something wrong?
I clear data, format data, clear cache, format system, reboot to recovery, then i install the room. I wait like 5 minutes the reboot, after the reboot i change the language to english and aloe ask for root in the miui manager, then not one single app that asks for root permitions cab get it, it always fail
Am i doing something wrong?
Thanks in advance
Sent from my U8800 using Tapatalk 2
Hevvy said:
I just can't manage to get root connection with any of miui v4 rom's, except with crazygamer rom...
I tried the super user and failed too, am i doing something wrong?
I clear data, format data, clear cache, format system, reboot to recovery, then i install the room. I wait like 5 minutes the reboot, after the reboot i change the language to english and aloe ask for root in the miui manager, then not one single app that asks for root permitions cab get it, it always fail
Am i doing something wrong?
Thanks in advance
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
You are not doing anything wrong.... There is a App in folder on 2nd page Permission...there it will show all the apps you have installed there you can give the permissions.... hope this helps.
krish_nank said:
You are not doing anything wrong.... There is a App in folder on 2nd page Permission...there it will show all the apps you have installed there you can give the permissions.... hope this helps.
Click to expand...
Click to collapse
Thanks i will try to figure it out.
Sent from my U8800 using Tapatalk 2
never mind...
volume wake please?
my power button is kinda wonky, and i already managed to remap my search button as a power button. so now I need the volume key to wake the phone up.
ericmaxman said:
volume wake please?
my power button is kinda wonky, and i already managed to remap my search button as a power button. so now I need the volume key to wake the phone up.
Click to expand...
Click to collapse
Well there is this option already at settings->Button->Volume rocker wake
spirosbond said:
Well there is this option already at settings->Button->Volume rocker wake
Click to expand...
Click to collapse
ooooo.. that's how u make me look now :silly: :silly: :silly: :silly:
thanks a million!!! :good: :good: :good:
** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa5 v1.3 is a Lollipop ROM for Sero 7 Pro owners worldwide. It focuses on core functionality that must be built-in and relies on 3rd-party apps to provide features that can be added-on. This release also offers a version of TWRP Recovery that is compatible with all models of the S7P.
Key Features
International Support - a single ROM for all Sero 7 Pros sold worldwide (US, UK, Australia, Germany, and elsewhere)
Speed Control - speed when you need it and stock performance when you don't
OTG Charging - charge the tablet while an external device is attached to the USB port
Flexible Formatting - full support for both F2FS and EXT4 on your internal storage, and exFAT/FAT32/NTFS/F2FS/EXT4 support for external storage
Installation
First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install TWRP or Philz Touch Recovery
Users outside the US must use the DoPa versions of these recoveries to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use them just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install TWRP or Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip the recovery zip and put the .img file (twrp.img or philz.img) in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter, as appropriate, fastboot flash recovery twrp.img or fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then either the TWRP or Philz menu
CWM
If you have CWM installed, copy your choice of recovery zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the TWRP or Philz menu
Regardless of how you install your chosen recovery, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
using Philz, select "Backup and Restore", then "Backup to /storage/sdcard1" -if there's enough space on the card, the backup will start without any further prompt;
using TWRP, select "Backup", then tap "Storage" (halfway down the screen) and ensure that "sdcard" is selected; on the previous screen, swipe the slider to start the backup;
it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: for TWRP, you can check "Enable compression" on its main backup screen; for Philz, select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
STEP 3: Install the DoPa5 ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See the TK Gapps thread for details. I recommend the "Nano Modular" package which gives you the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
using TWRP, select "Wipe", then "Format data"; on the next screen type "yes" to confirm you want to proceed;
using Philz, select "Wipe and Format Options", then "Custom Format Options"; next select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice;
return to the main menu
using TWRP, select "Install"; at the top it should show "Storage: sdcard" - if not, tap there and change the setting
using Philz, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp511-dopa5-v1.3.zip, then OK your choice - the install process should take about 40-60 seconds
next, install your Gapps package
return to the main menu, select "Reboot" then "System" if using TWRP, or "Reboot System Now" for Philz, then hold your breath for the next 3-4 minutes
the Hisense screen should be up for 30 seconds, followed by the DoPa boot animation for another 3 minutes
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
UK, AU, and DE users must use the DoPa versions of TWRP or Philz Touch to install the ROM because they are the only ones compatible with your tablet. US users can use any SELinux-enabled version of CWM, Philz, or TWRP.
from DoPa5 AOSP Lollipop ROMs - no need to wipe or format anything!
from DoPa AOSP Kitkat ROMs (v1.0-v2.7) - a clean install is recommended but not required
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp511-dopa5-v1.3.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa5-v1.3.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed TWRP or Philz Touch Recovery, please do so first.
TWRP
make a backup to your external SD card
select Wipe then Advanced Wipe
select the partition to reformat, then tap Repair or Change File System
on the next screen, tap Change File System, then F2FS (or EXT4 to restore the default file system)
swipe the slider below to start formatting
when done, use the Restore option on the main screen to restore the contents of the partitions you reformatted
Philz
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Changes since DoPa5 v1.2
Xposed and GravityBox - these staples of the DoPa KitKat ROMs are back and preinstalled to provide all the tweaks you want - and none of the ones you don't
ArchiDroid Optimizations - this version of Android was built using gcc 4.9 and is highly optimized thanks to settings provided by JustArchi. To help ensure stability, the kernel uses standard optimization levels but is better tuned to our Cortex A9 processor due to the use of linaro 4.9 (a version of gcc optimized for ARM processors).
No Odex-ing - odex-ing has been abandoned because Xposed recompiles all apps, making the .odex files redundant. There should now be enough space on the /system partition to install the TK-Gapps Micro package.
Adaptive Brightness - a longstanding bug that could cause the screen to go black has been fixed. Overall brightness levels have been adjusted to provide greater dynamic range in low lighting conditions.
Notes
Xposed - having the Xposed framework installed shouldn't cause any issues, but if you wish to remove it you can do so using the xposed-uninstaller available in the Xposed XDA thread. The Xposed Installer and GravityBox apps will remain but will be inactive - you can use a root-enabled filemanager to remove them if you wish.
Encryption - if you wish to encrypt your /data partition, you must first use Philz Recovery to format it. Using TWRP to format may cause the partition to become un-decrytable, resulting in the complete loss of all your data. This is NOT an issue if you don't plan to use encryption.
WiFi Display - end a WiFi Display session from your television, not the tablet; doing so from the tablet may cause it to lock up. Chromecast is reportedly not subject to this issue.
USB Audio - booting up with a USB audio device attached may result in a bootloop.
Gapps - due to limited space on the /system partition, the TK Gapps's "Mini Modular" and larger packages will not install. I suggest using the "Nano" package, then downloading those apps you really want from PlayStore.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp511-dopa5-v1.3.zip the full ROM
sero7pro-nexus7spoof-dopa-v1.3.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-twrp287-dopa5-v1.3.zip a customized version of TWRP Recovery v2.8.7 usable on all versions of the Sero 7 Pro
sero7pro-philz6.58.0-dopa-v2.7.zip the final version of Philz Touch CWM-based Recovery v6.58.0 compatible with all models of the Sero 7 Pro
TK Gapps an XDA thread with links to various Gapps packages
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to a previous version (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
XDA:DevDB Information
Sero 7 Pro (US/UK/AU/DE) - DoPa5 AOSP, ROM for the Android General
Contributors
dolorespark
Source Code: https://github.com/dolorespark
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v1.3
Stable Release Date: 2015-09-26
Created 2015-01-28
Last Updated 2016-01-02
Reserved
Thx for all your hard work
on these tablet
Thx
ok, so I have a question or several as I remember them...
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models.
Has this been fixed yet?
If not, is there a workaround?
If so, what is it?
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Also, can the cpu be overclocked beyond 1.5 Ghz?
If so, is this already enabled, or is there some magic involved?
I really liked the beta 4 (beta r3) Rom and the way it looked, felt, and ran.
I found it to be better at managing free memory than kitkat in that I had at least 50% more free ram than Kitkat. I believe this contributed to some of the performance increase. But I had a hard time with the Google Play Movies bug. And some people were saying it was a general problem within the os's video subsystem.
Legend, keep up the great work
Excellent work! Looking forward to this!
Sent from my Nexus 7 using XDA Free mobile app
alpurl said:
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models. Has this been fixed yet?
Click to expand...
Click to collapse
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug. Here's the fix - install it from Recovery:
sero7pro-video-drm-fix-dopa5-v1.0.zip
I'll repackage the main ROM in the near future to include this fix, but first I want to investigate a few possible problems I noticed while getting this fixed.
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Click to expand...
Click to collapse
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off. If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Also, can the cpu be overclocked beyond 1.5 Ghz?
Click to expand...
Click to collapse
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Loving the first build. Very silky smooth speed and pretty stable as well as far as Lollipop is concerned at this point. As far as themes are concerned I haven't had too many issues using them on the current CM12 nightly for the Sero 7 Pro despite the DPI difference. Can't wait to see where this goes from here. Thanks for all the hard work! :highfive:
dolorespark said:
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Click to expand...
Click to collapse
Well, on nVidia's page it recommend a maximum of 1.6 GHz, so 1.7 is not too much of an overboard if Hisense had built these units well enough. However, even with 1.5 GHz the chips is already running uncomfortably hot so it would be wise to back off from any higher clock. I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz? (granted that there would be a possibility of artifacts )
dolorespark said:
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug.
Click to expand...
Click to collapse
Being under that magic number of 10 posts, I couldn't post this in that main thread, and when I tried to post in the q&a thread where "reply" sent me, the forums bot catcher tripped me up.
Thanks, that worked like a charm.
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Click to expand...
Click to collapse
To my knowledge, they don't, or at least I haven't figured that part out yet. Haven't figured it out in trickster mod either. I'll try the code. I only remember seeing one init.d file, does it matter where in that file I add the code?
Yeungers said:
on nVidia's page it recommend a maximum of 1.6 GHz
Click to expand...
Click to collapse
The Tegra3 is a family of SoCs with models designed for mobile, automotive, and embedded use. Ours is the low-power mobile version. Some variants do have higher maximum clock speeds but they use more power at every frequency step than ours.
I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz?
Click to expand...
Click to collapse
Possibly. The original overclock patch just upped the GPU speed to 520mhz without increasing the voltage any - and that seemed to work. When I rewrote the o/c code, I increased the voltage when running at 520mhz for what I considered solid reasons, Since it now has more power, I suspect I could up the speed somewhat without causing problems. However, even at a higher speed, it's still going to be an also-ran in today's market.
alpurl said:
dolorespark said:
If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
Click to expand...
Click to collapse
Having some other app set the CPU or GPU speeds isn't going to make it any more or less stable than having the built-in facility do it.
Be aware that if you're trying to use one of these apps to set the Interactive Governor's parameters, you're wasting your time. Not only does our Interactive Governor NOT work like you'd think - and not work like other implementations - it's totally ineffective. Every time the kernel brings another core online, it kicks all cores to the maximum allowed speed, totally sabotaging the governor's efforts. If you use Trickster to track the time at each speed, you'll see that the bulk of the time is spent either at very low speed or max speed, with all the intermediate speeds hardly used at all.
I only remember seeing one init.d file, does it matter where in that file I add the code?
Click to expand...
Click to collapse
Create a new file named, f'rinstance. "02gpuspeed". Put "#!/system/bin/sh" on the first line, then the code I provided on the following lines. The files will be executed in alpha-numeric order: 00banner, 02gpuspeed, 99SuperSUDaemon. Be sure to set its permissions to '755' so it is executable.
I pretty well figured that would be the case, but...
Based on my somewhat limited understanding ,If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise. Based on my pc understanding, conflict equals poor performance and instability.
And it was honestly one where I was using performance settings for the gpu, and then one of the other apps for the cpu.
So, I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable. So I was asking about how to get the higher gpu clock without using the cpu overclock portion of the performance tab.
You pretty well answered that, and I thank you.
Now, do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520?
Also, I don't understand setting permissions to 755. I understand setting read, write, own, etc, but not 755, if that's the case, then what app do I use for that? I created the file as a blank text document on my tablet directly and input the code there, then rebooted. Or did I screw the pooch on that one?
Sadly, I know nothing about the individual governor settings within each governor configuration. Therefore, I figure that the wisest and safest course of action is to leave it alone. It's easier and safer to work with the stuff I DO know until I can get feedback and advice from someone who DOES know.
I realize that some of this may seem stupid to you, but it's the only way I know to learn.
I will make another post later when I have more time to comment on some other things I keep seeing and would like to know what to do there.
alpurl said:
If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise.
Click to expand...
Click to collapse
The CPU/GPU settings on the Performance page are set-and-forget values. They simply set the maximum speeds once bootup is done, and again when you display that page. They don't monitor anything - the CPU governor does that, and it is constrained by these settings. The corresponding settings in the other apps you've tried operate the same way.
You should be aware that the "performance" governor is really no governor at all. It simply sets the processor to the maximum permitted speed and never changes it. On the whole, this governor generates more heat than performance.
I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable.
Click to expand...
Click to collapse
This strongly suggests that your device really can't handle the higher speed - at least when the CPU is running full-bore at all times. You may want to search for the postings in some of the early S7P threads where people described attaching copper foil to the SoC to dissipate excess heat.
do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520? Also, I don't understand setting permissions to 755.
Click to expand...
Click to collapse
Anything after a '#' in a shell script is a comment. As to '755', that's "read/write/execute" for the owner, and "read/execute" for the group and other users. Do a search for the 'chmod' command for more details on setting and interpreting Unix permissions.
Ok, that's fair enough.
Occasionally, I'll boot and get an error that the process called system is not responding and then it wants to know if I want to wait, or close it. It will do this every subsequent boot until I wipe cache and Dalvik (because I end up doing both out of habit) from recovery and then all is well again for several boot cycles where we start up again.
What am I missing here?
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Sent from my XT1034
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Click to expand...
Click to collapse
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on.
Click to expand...
Click to collapse
AngryManMLS said:
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
Click to expand...
Click to collapse
Of course you're welcome to discuss RRO - especially since it gives me an opening to throw in my 2 cents
Runtime Resource Overlays provides a way to override and/or replace the "resources" (icons, layouts, colors, strings, and fixed values) that are built into an .apk file. Since the resources used by Android itself are packaged into an .apk, you can modify the OS as well as individual applications.
RRO has been around for a long time but no one other than Sony ever used it. BitSyko's greatest contribution has been to make people aware that it's a superior way to do theming which is already built into the OS and is fairly easy to use. Unlike CM's theme engine, no custom code is required.
Beyond that, their contribution is somewhat less revolutionary than their many admirers seem to think. Their efforts are directed primarily at ease of use. The Layers app is essentially a file manager that makes copying themes into place a bit easier. What the app does you can do yourself using ESFileExplorer or ADB (though without some niceties they've added).
Their tweaks to the OS are designed to make life a bit easier for themers by changing hard-coded color values into "symbolic references". In other words, rather than specifying the color for each checkbox, you say each one should be the "checkbox_color", then define what that means somewhere else. That way, rather than having to modify the color of many different checkboxes, you change the definition of "checkbox_color" once and they all become that color.
Now, as to what all this means to the Sero 7 Pro and the DoPa5 v1.0 ROM... I delayed the ROM's release for several days until I could get their patches in place and tested, so this facility is in there and ready for use. The problem is that none of the themes I've seen really support the S7P. Any color changes a theme makes will show up just fine (I'm using someone's orange theme currently). However, all the icons are targeted at higher resolution screens than ours, so the OS ignores them and uses the same ones it has always used. If you can find themes for the Nexus 7, or some of the older Asus or HP tablets that also have a 1280*800 screen (213dpi), they should work just fine.
FYI... if you want to install a theme without using Layers, create an 'overlay' directory in '/system/vendor' (i.e. '/system/vendor/overlay'). Next, get some theme packages from this thread and unzip them. Select the .apk files you want, copy them into the 'overlay' directory, then reboot. If you don't like the result, delete them and reboot again.
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
AngryManMLS said:
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
Click to expand...
Click to collapse
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Sent from my XT1034 using XDA Free mobile app
kenundrem said:
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Click to expand...
Click to collapse
That would be amazing if you could. Here is an example of what I mean as well.
http://forum.xda-developers.com/android/themes/theme-dark-holo-theme-v1-0-01-25-15-t3012227
Trying to keep Vanir up-to-date for our otherwise dead phone . Fix minor bugs, add minor features, a bit of compiler optimization.
I'm not updating the whole rom here! Development of branch cm-11.0 for both Vanir and CyanogenMod has stopped, so there won't be any surprises here!
Bugs:
- adb over usb doesn't work in android (but works over wifi and in recovery it works normally, so no problem)
- clear notifications icon missing when switching from quicksettings
- call recording doesn't work
- synapse doesn't work
ART:
Apart from 2 inconveniences, ART works and is fast
- optizing one app on reboot - it's a bit annoying, but otherwise harmless (happens only sometimes)
- immediately after switching to ART phone won't sleep (power button doesn't work. Just leave it for a while (15-30 minutes) and let it settle - once the screen turns of by itself, everything wil be normal
Deep sleep issue (if exists):
Check using Better Battery Stats or any tool of your choice. If it is caused by Google Play Services, simply deny them wakelock priviledge: Go to Settings/Security/Privacy Guard/Google Play Services and set Keep awake -> denied. It won't hurt sync, no worries.
Feature requests:
- Smart Pulldown from Omnirom Done
- NonIntrusive incoming call screen (@force)
XDA:DevDB Information
Vanir 4.4.4, ROM for the Samsung Galaxy S Advance I9070
Contributors
mkaluza
Source Code: https://github.com/mkaluza/
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: Vanir
Version Information
Status: Stable
Current Stable Version: 2015-08-11
Stable Release Date: 2015-08-11
Created 2015-05-28
Last Updated 2015-08-11
first of all, thanks again for keeping this ROM updated and alive you should add some tags in the topic title such as [ROM] [KK] [4.4.4] and the release date, so that it's more visible and captivating
Found. Dowloading. Torrent is the best way to share information. All developers must use it.
Thanks and reporting...
@mkaluza @edukardo @TheSteve87 May i have some screenshots please....
experimenta 2015-05-30
Hi!
New experimental build. It is _fast_ Added more optimization flags from ArchiDroid. It still has the location FC issue though, so if it's a problem for you, stay with stable.
Enjoy
$4ND!P said:
@mkaluza @edukardo @TheSteve87 May i have some screenshots please....
Click to expand...
Click to collapse
here's a bunch of screenshots, the last ones have the vanir black theme
@mkaluza i'm having a weird bug with the last stable build, i want to install two apps as system apps (cm file manager since this rom dowsn't have one and novathor settings because of power and volume options) but everytime i try to install them, after rebooting the phone works for 30seconds, then freezes and reboots and it becomes unusable. any idea about why?
I have a problem with hotspot shield vpn
It won't start
And says
Af openvpn inti. Faild
I tried other vpn apps but they don't work
Any suggestion
mhmod222 said:
I have a problem with hotspot shield vpn
It won't start
And says
Af openvpn inti. Faild
I tried other vpn apps but they don't work
Any suggestion
Click to expand...
Click to collapse
Yes, load tun module. Either via KoControl app or from terminal: su and then "modprobe tun"
TheSteve87 said:
@mkaluza i'm having a weird bug with the last stable build, i want to install two apps as system apps (cm file manager since this rom dowsn't have one and novathor settings because of power and volume options) but everytime i try to install them, after rebooting the phone works for 30seconds, then freezes and reboots and it becomes unusable. any idea about why?
Click to expand...
Click to collapse
NT settings are old and mess with the kernel. Besides it's a ROM app, so you can't just take any version - it had to be built with the ROM. I don't support it.
Attached cm file manager to post 1 - try it (just drop it to /system/app as it doesn't seem to install the normal way)
@TheSteve87 what exactly do you need from nt app? Maybe I'll be able to add it into synapse.
mkaluza said:
@TheSteve87 what exactly do you need from nt app? Maybe I'll be able to add it into synapse.
Click to expand...
Click to collapse
i mainly use two settings, the battery voltage (?) control to have a faster charge and the audio gain options to higher the earbuds/speakers' volume
btw novathor settings are not that old, i actually extracted the apk from epirex's latest cm11 build and pushed it to /system on your vanir with no issues at all at least on the build before the beta version
Sent from my GT-I9070 using XDA Free mobile app
How to install that? I done Odin ,temp CWM, flash rom and my phone stuck on boot.
xxziolo13xx said:
How to install that? I done Odin ,temp CWM, flash rom and my phone stuck on boot.
Click to expand...
Click to collapse
If you come from another ROM with mk kernel, don"t forget to delete ramdisk
edukardo said:
If you come from another ROM with mk kernel, don"t forget to delete ramdisk
Click to expand...
Click to collapse
I was on stock LQL with CoCore, then i did odin, format everything in temporary CWM and flash rom. My phone stuck on boot whole night. Any ideas?
xxziolo13xx said:
I was on stock LQL with CoCore, then i did odin, format everything in temporary CWM and flash rom. My phone stuck on boot whole night. Any ideas?
Click to expand...
Click to collapse
Install aromafm and search /efs for a boot.cpio.gz file. Delete or rename it and try again.
edukardo said:
Install aromafm and search /efs for a boot.cpio.gz file. Delete or rename it and try again.
Click to expand...
Click to collapse
LOL. I forgot about it when i was on Loilipop, now it is working.
It was muy mistake too. This vanir is superb
edukardo said:
It was muy mistake too.
Click to expand...
Click to collapse
Yeah... I can see this ramdisk stuff causes a bit of trouble. I already have an idea for 'smart' installer, that will autodetect system version and install correct ramdisk for the user.
This vanir is superb
Click to expand...
Click to collapse
And it'll only get better I almost nailed the correct compiler flags, so the next stable version will have the speed of beta (or more ), but of course without the NetworkLocationService bug.
Battery backup
Hi, my friend.
I've seen a known bug in CM11 derivated roms like this one. This is related to systemupdate service, the rom tryies to connect to cm software update but couldn't and causes a lot of aware.
I made this script and ran it at every boot
Code:
#!/system/bin/sh
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateService
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateService$ActiveReceiver
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateService$Receiver
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$ActiveReceiver
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
It make the system wake ups almost dissapear. You could try to put it in your code if you think is correct.
Regards.
edukardo said:
Hi, my friend.
I've seen a known bug in CM11 derivated roms like this one. This is related to systemupdate service, the rom tryies to connect to cm software update but couldn't and causes a lot of aware.
I made this script and ran it at every boot
Code:
#!/system/bin/sh
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateService
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateService$ActiveReceiver
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateService$Receiver
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$ActiveReceiver
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
It make the system wake ups almost dissapear. You could try to put it in your code if you think is correct.
Regards.
Click to expand...
Click to collapse
I'm not 100% sure, but it could be related to this one:
http://review.cyanogenmod.org/#/c/94128/
Androidx86 & Forks using custom kernelsfor UEFI Windows tablets
Android 6.0 Marshmallow [Stock Download] [Source]
Android 4.4.4 KitKat [As above]
RemixOS 2.0 (Android 5.1.1) [Stock Download] [Source]
PheonixOS 1.0.3 (Android 5.1.1) [Stock Download]
Custom Kernels Included
Cube i7_Stylus
kernel device_tree
Android 6.0 MM -- post @Wootever
Android 4.4.4 KK -- post [Additional Files] @Wootever
RemixOS 2.0 -- post @asplash
PhoenixOS 1.0.3 -- post
Kernels -- located here
Hacks-Scripts-Tools
Hacks and workarounds that can be used to overcome reported issues. These will be primarily bash scripts; hopefully these can be included in the source code in some way if useful/needed.
Scripts
General scripts - use an app to launch them at boot; or make use of /etc/init.shSleep mode [effectiveness will depend on what sleep modes your device/kernel has access to (`dmesg | grep ACPI`); and will need to be modified if your screen brightness is reported elsewhere]
Code:
watch -n 60 '[ "`cat /sys/class/drm/card0/card0-eDP-1/intel_backlight/actual_brightness`" = "0" ] && echo "mem" > /sys/power/state' &
Which watches the brightness level every minute and if it's zero then puts the device into S3 sleep.
This can be modified in cases where specific modules don't comeback after sleep like the following for a rotation sensor
Code:
watch -n 60 '[ "`cat /sys/class/drm/card0/card0-eDP-1/intel_backlight/actual_brightness`" = "0" ] && setprop ro.sleep 1 && echo "mem" > /sys/power/state' &
watch -n 60 '[ "`getprop ro.sleep`" = "1" ] && [ "`cat /sys/class/drm/card0/card0-eDP-1/intel_backlight/actual_brightness`" != "0" ] && setprop ro.sleep 0 && am force-stop com.android.launcher3 && rmmod kxcjk_1013 && modprobe kxcjk_1013' &
Which restarts the kxcjk_1013 module and restarts the launcher on wakeup
Build.prop edits RemixOS
ro.remixos.box=true
changing this value to false opens up more options in settings/taskbar and is preferable on tablets
ro.remixos.no_wallpaper=true
changing this to false will let you have a wallpaper if you turn of the file based launcher in settingsRMXTool by @imadlatch is a great tool for resizing data/system.img and having a poke through the system.img while in WindowsProposition
It should be trivial to modify the ramdisk of Androidx86 ROMS to bind mount an additional .img to host the device specific modules/firmware for trying out new generic ROM releases - obviously full ROM build are preferrably but not always available.
Will need to have a look into the module packing that the build does in order to pack correctly when just compiling a kernel & modules.
XDA:DevDB Information
Androidx86 & Forks, ROM for the Android General
Contributors
HypoTurtle
ROM OS Version: KitKat; RemixOS/PhoenixOS (Lollipop); Marshmallow
Version Information
Status: Stable
Created 2016-02-12
Last Updated 2016-02-12
Reserved
INSTALLATIONThere are numerous ways these can be installed and there are numerous post reporting different methods, so please don't repeat posts detailing the same issue.
I will list tried and tested installation methods (using Grub2) and a quick rundown of what makes upa grub.cfg file
Reserved
FAQIf you have a question that hasn't been answered so far - have a look here first before posting
Thanks @HypoTurtle for making a separate thread for Android releases on the Cube i7 Stylus device! The original thread became quite messy, and it is important to have a dedicated one for Android.
First of all, I think we should really thank the great developers in this forum, @Wootever @asplash @HypoTurtle and all other members and testers for their contribution in preparing a good android image for this tablet.
I've been testing all Android releases in the main thread, and the most stable and usable one was Wootever's 4.4 release.
All other Lollipop (RemixOS and Pheonix OS) and Marshmallow releases seem to suffer from a few major problems:
1) lack of efficient stand by / sleep mode
2) high battery drain
3) no video codecs supporting hardware acceleration
I wonder if this is the case with other x86 based laptops/tablets , and whether the x86-android team are working on fixing these essential features.
Keep up the great work everyone!
@HypoTurtle
Can you please post the script in the first entry for sleep mode in the lollipop releases?
also, any new updates or releases ?
A new beta release of RemixOS has been released.
http://www.jide.com/en/remixos-for-...rce=sendgrid.com&utm_medium=email#downloadNow
Has anyone tested it?
KamaL said:
A new beta release of RemixOS has been released.
http://www.jide.com/en/remixos-for-...rce=sendgrid.com&utm_medium=email#downloadNow
Has anyone tested it?
Click to expand...
Click to collapse
Stock RemixOS Beta, runs with a reported 4.4.2 kernel with as expected wifi not working, switching to the 4.4.0 kernel/modules/firmware we are currently using will work, but I'd rather wait until when/if the kernel source is released.
EDIT. Cube i7 Stylus kernel + modules attached. These are taken from RemixOS Alpha - so it's the kernel @asplash compiled. You need a rooted system.img or unpack/repack system.img within Windows/Linux. Just copy files over / and run the sh while running to set permissions. Then switch the kernel.
Too big to attach so available here
Just a couple of screenshots, it's seems very few people have figured out how to get rotation to work, and I'm sure even fewer have found how to enable apps like Twilight, Lux or Tincore Keymapper...
I'll post procedure in a bit just making sure it doesn't irreversibly mess with anything.
HypoTurtle said:
Stock RemixOS Beta, runs with a reported 4.4.2 kernel with as expected wifi not working, switching to the 4.4.0 kernel/modules/firmware we are currently using will work, but I'd rather wait until when/if the kernel source is released.
EDIT. Cube i7 Stylus kernel + modules attached. These are taken from RemixOS Alpha - so it's the kernel @asplash compiled. You need a rooted system.img or unpack/repack system.img within Windows/Linux. Just copy files over / and run the sh while running to set permissions. Then switch the kernel.
Too big to attach so available here
Click to expand...
Click to collapse
Thanks.
Can you explain step by step how to do it?
Also, any improvements over the previous builds in terms of battery consumption and sleep mode?
Thanks
<MOD EDIT - Non-English Quote Removed.>
Bluetooth not working (same with remix os) for me and I expand data.img with RMXtools but still in android I see 3gb,is there other way to expand?and i can see only 2678MB of ram
asplash said:
essayer d'ajouter
"blacklist btusb" dans /system/etc/modules.blacklist
et redemarre
Click to expand...
Click to collapse
Thanks,bt is working now,for data.img and ram?
leo06 said:
Thanks,bt is working now,for data.img and ram?
Click to expand...
Click to collapse
<MOD EDIT> data.img
KamaL said:
Thanks.
Can you explain step by step how to do it?
Also, any improvements over the previous builds in terms of battery consumption and sleep mode?
Thanks
Click to expand...
Click to collapse
Download it and have a look it should be fairly clear simpilest way is to copy to somewhere you can mount in android (usb, sdcard etc.), then with root file browser copy over, then replace the kernel.
Alternatively use something like RMXTools to open the system.img, copy the files over then repack system, boot, fix module permissions, then switch kernel.
Jide have just released their 4.4.y sources, so going to compile (at least the wifi driver) asap unless @asplash is already setup for a compile. There is a benefit with it at least with exfat (my exfat partitioned sdcard auto mounts with 4.4.2 but not with 4.4.0).
asplash said:
avez vous essayez ceci data.img
Click to expand...
Click to collapse
Do you know why i can't see usb stick and sd card in es file explorer?
asplash said:
de quel format son t'il ? exfat? ntfs?
Click to expand...
Click to collapse
The usb i formated from inside android but still i can't see from es file explorer and sd card is ntfs,i can see both from settings
leo06 said:
The usb i formated from inside android but still i can't see from es file explorer and sd card is ntfs,i can see both from settings
Click to expand...
Click to collapse
/mnt/media_rw/****
Can we install xposed framework in Android?
leo06 said:
Bluetooth not working (same with remix os) for me and I expand data.img with RMXtools but still in android I see 3gb,is there other way to expand?and i can see only 2678MB of ram
Click to expand...
Click to collapse
I answer to myself for 3gb of ram, just realized that is x86 not x64
@asplash
Thank you for your great work on Android for the Cube.
About your latest CM13 ROM:
-Deep sleep seems to work (at last). After coming back from sleep brightness goes up and the device remains unresponsive for a while but after pressing the Windows button everything comes back to normal.
-My 128 GB NTFS formatted MicroSD card can be read from settings and from a file explorer using /mnt/media_rw, but it isn't easily accessible from many apps.
-Battery level isn't read properly, it shows 100% all the time.
-Built-in root doesn't remember a previously granted access, installing SuperSU solves the problem.
-The app GMD Gesture Control (a must have for me) doesn't recognize the touchscreen device. It worked on your Lollipop ROM.
-Only 3 Gb of RAM seem to be accessible, your Lollipop ROM aparently could see the full 4 GB.
-The device doesn't boot with the 8 Gb data.img, it gets stuck on the boot animation.
Speaking about your Lollipop ROM, it's been my Android choice for more than a month. Since its only drawback was the inability to enter deep sleep it would be lovely if you could post a new Lollipop ROM with that issue solved.
ariadnejro said:
@asplash
Thank you for your great work on Android for the Cube.
About your latest CM13 ROM:
-Deep sleep seems to work (at last). After coming back from sleep brightness goes up and the device remains unresponsive for a while but after pressing the Windows button everything comes back to normal.
-My 128 GB NTFS formatted MicroSD card can be read from settings and from a file explorer using /mnt/media_rw, but it isn't easily accessible from many apps.
-Battery level isn't read properly, it shows 100% all the time.
-Built-in root doesn't remember a previously granted access, installing SuperSU solves the problem.
-The app GMD Gesture Control (a must have for me) doesn't recognize the touchscreen device. It worked on your Lollipop ROM.
-Only 3 Gb of RAM seem to be accessible, your Lollipop ROM aparently could see the full 4 GB.
-The device doesn't boot with the 8 Gb data.img, it gets stuck on the boot animation.
Speaking about your Lollipop ROM, it's been my Android choice for more than a month. Since its only drawback was the inability to enter deep sleep it would be lovely if you could post a new Lollipop ROM with that issue solved.
Click to expand...
Click to collapse
For the battery it happens the same to me but after reboot is OK, drops by 4,5,8% and not by 1%,i mean now is 55% and after some time it shows 50%,for 3gb of ram self-test my previous post, it's 32bit Version of Android so only see 3gb,for data.img I use wootever 6gb data.img and it works