{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*UPDATE: Both the Galaxy S4 Mini LTE and international 3G variants now have official nightlies & stable 10.1.3! Get them at http://get.cm/?device=serranoltexx and http://get.cm/?device=serrano3gxx respectively.
This thread is to discuss any issues you may have or bug reports to raise regarding the CM10.1 nightlies AND stable versions for the Samsung Galaxy S4 Mini LTE variant (GT-I9195) only.
Opened this thread so that newbies can also post their issues here, as well as to keep the release thread clean for development-related discussions only.
** DO NOT USE THE JIRA BUG TRACKER TO REPORT BUGS FOR NIGHTLIES!
Sir arco68 has suggested that all bugs still be reported here despite having a stable version as it is a more central location to view and see bug reports.
-------
Links
Release thread / Development discussion | CyanogenMod 10.1
How to install CM10.1
Root and install using ONLY CWM recovery (available here: [RECOVERY][ROOT] Samsung Galaxy S4 Mini LTE (GT-I9195))
Copy all the files you downloaded for CM10.1 (From http://get.cm) into your SD card along with the Google Applications (Optional, recommended - get the latest one for CM10.1.x)
Boot into CWM (Vol Up + Home just as the phone is booting up, navigate using Vol btns, HOME to select, POWER to back)
Make a backup of your NANDroid (Optional - Do this if you wish to return to your previous ROM)
Select "wipe data/factory reset" and press Yes
Select wipe cache partition" and press Yes
Flash cm-10.1-2013xxxx-XXX-serranoltexx.zip file FIRST (or RC or stable)
Then flash gapps (Optional)
Notes
When upgrading between CM10.1 versions, you still need to flash the gapps module after upgrading as /system is wiped.
Notes about updating to latest stock FW before flashing custom ROMs
Screenshot is Vol-Down + Home in CM10.1
The ROM comes with a Superuser app. You don't need to install another one.
When installing themes which appear to be improperly compiled, apply the default system theme and reboot and try again.
CM10.1 doesn't come with an FM Radio app.
-------------------------
It would help greatly to be detailed in your bug reports and to provide logs (in [code][/code] blocks), in an organised manner.
LIST OF ISSUES
Unverified
Auto-unlock with flip cover doesn't work [1] [2]
WLAN instability, network switching issues and low GSM call quality (vs. Samsung ROM) [1] [2]
RC1 - Sporadic reboots [1] [2] [3] [4]
Changing exposure offset in Camera causes a crash [1]
Verified & Reproduced / Work-in-Progress
Missing Format SD Card option in Storage Settings [1] [Verification needed]
Fixed / In coming build
Bluetooth music audio output has no bass / low sample rate [FIXED: 20130824]
Some sensors (compass) not usable by apps [1] [FIXED: 20130823] [If it doesn't work]
Lose GPS after long intermittent usage of GPS apps [1]
RC1 - Increased battery drain (due to SystemUpdateService) [1] [2] [3] [4] [5] [FIXED 20130901]
IR Transmitter not working [1] - IR Support for CM being worked on in 10.2 - [FIXED in 10.1.3]
User-fixable
Unable to browse SD card in file browsers
Camera doesn't work after reboot - Its an SD card issue
Unable to reproduce / Unique to certain users / Unable to fix / Kernel issue
Changing language will crash settings (but language does change) [1] [X1] [X2]
Increase in battery drain [1] [X]
Phone: Numbers always display in the format "xxx-xxx-xxxx" [1] [X1] [X2]
Phone unlocks in pocket randomly [1] [X1] [X2]
4G quick-toggle makes Data Mode quick-toggle change to 2G [1] [X]
Unable to adjust call volume with 3rd party headsets (exists on stock ROM as well) [X]
No "Personalise Call Sound" in Call Settings [1] [X]
Unable to access external SD card in apps like Poweramp & VPlayer [1] [2] [X1] [X2]
Speaker crackles at low frequencies [1] [2] [3] [X1]
-------------------------
FEATURE REQUESTS
Requests
Move apps to external SD card / set external SD card as default SD card [1]
Accepted (being/will be worked on in the future)
BLN (Back-Light Notification) Kernel (may have changes.)
FM Radio (coming in 10.2)
----
Last updated: 08 Oct 2013, 0706hrs (+8GMT)
"Changing brightness will crash settings" did not issued on my device.
Changing language does, however, crash settings.
Also the battery seems to be draining faster than stock OS, for some reasons.
The number display format issues is still there I have no idea how to change it.
In messages, use dark theme setting is ignored.
I also after half day of usage noticed my phone keep unlocking in my pocket, I don't have any special unlock features enabled like home button or so, is this normal?
Later edit: Quick-toggle for brightness will not always work - I cannot reproduce, there was one time that ignored now works fine after many tries and flashes. Safe to remove.
Sorry that was a mistake on my part in copying down the issue.
I've added your other findings to the list
Will be trying the alpha ROM this weekend as well so I'll try to reproduce your issues!
Quick-toggle for brightness will not always work [1]
you can remove this never happened again. can't remember how it happened anyway
Can someone help me port it for i9192?
the dual chip version?
I want so much to see CM on my cellphone
I am using this build since this morning so far we get along, if I can improve battery life a little will be my perfect os.
Also I cannot find that option to enable "clear sound" or something like that, I don't hear people as clear as I heard them with stock 4.2.2 samsung os...
Do you mean Samsung's Adapt Sound feature?
I believe that it won't be added because it is a Samsung proprietary feature
No there was another feature, Noise Suppression or something...
Also the format storage card option still missing, is an app that does that?
I've added the missing format SD card option.
Can't seem to find the sound option you are talking about on my stock rom (build MFA) though
i think the bug of use dark theme in message is not actually a bug. i think maybe it is the same as cm10.1 in Wonder. the dark theme is apply for quick reply only ( if you enable it, and not use privacy message ). not the whole message app. try to confirm this
geniusboy93 said:
i think the bug of use dark theme in message is not actually a bug. i think maybe it is the same as cm10.1 in Wonder. the dark theme is apply for quick reply only ( if you enable it, and not use privacy message ). not the whole message app. try to confirm this
Click to expand...
Click to collapse
yes genius you are right, after a close lookup I saw this. So no bug there.
On the other hand, battery is killing me. With stock os I ran a full day moderate usage. With this one at 4 pm I had to recharge no battery draining apps in fact no third app installed yet.
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Whosat said:
I've added the missing format SD card option.
Can't seem to find the sound option you are talking about on my stock rom (build MFA) though
Click to expand...
Click to collapse
http://cdn.pocket-lint.com/r/s/748x/assets/images/e3a23272d6002184ae94ce6c9d4a9e99bda6b716.jpg
The one pic I found. I remember seeing this on other devices...
I found it. Try going to Settings, Call, Personalise Call Sound.
On stock OS you did
ok, now the phone won't show up in my computer ( mtp I guess )
tried reboot, etc. nothing works.
Changing language will crash settings (but language does change) [1]
Click to expand...
Click to collapse
Doesn't happen here.
Increase in battery drain [1]
Click to expand...
Click to collapse
Ah, the good old battery drain issue. No phone goes without it. I'd recommend giving the battery a couple of recharge cycles and then see. When switching roms, the battery is always behaving a bit erratic at first. Also, check with BetterBatteryStats if there's something keeping a wake lock.
My battery stats:
View attachment 2186714 View attachment 2186715
Phone: Numbers always display in the format "xxx-xxx-xxxx" [1]
Click to expand...
Click to collapse
I think this adjusts itself according to the language used. I.e if you are in english language when importing contacts, it will be like that.
Phone unlocks in pocket randomly [1]
Click to expand...
Click to collapse
Probably touched the home or power button. Happened sometimes on stock rom for me as well. Maybe the buttons are just a bit sensitive.
Missing Format SD Card option in Storage Settings [1]
Click to expand...
Click to collapse
I'll look into this.
arco it the crash on changing language sure happens. however I did remove the default ime with swifkey, so I guess is reaching for it's keyboard. Also I removet velvet, and everything voice search related or search related. Maybe this could be the issue, it doesn't bother me so much.
regarding the phone number format, i wiped /data and selected romanian at boot. It's a system wide setting not a contact issue as I can see, all numbers are displayed that way, phone dialer, messages, agenda, incoming/outgoing calls, etc.
Also with the unlock issue I have this phone for a month I never got it unlocked in my pocket and today happened 3 times.
I am not trying to do anything bad here, I am just using this rom and I want to see it perfect as you and we all do.
My biggest problem on this rom and I am sure other users doesn't have it ... remains this phone number display thing. It's quite hard, because I am used in 15 years oh phone usage with a format, and now when I have to dictate a number or look into it it confuses me, even if it's the same number but those spaces are killing my habbits
Working great
I just installed this ROM and I have not ran into any bugs and I didn't notice any battery drainage. I'm unsure as what the cause is for most of the other users. I however had one slight issue which I resolved by allowing the default file manager root access, the issue was that I could not access my SD card through any normal file explorer. Other than that I'm enjoying this ROM keep up the good work!
Thanks arco68 for this early release and all the hard work you've done
No issues yet apart from one where i couldn't edit any contacts and kept saying "google something has stopped working" and keyboard wouldn't show up. But sorted itself out after a while and now is working fine.
I don't like that we cant change the theme of contacts and messages to a dark one like it is on call logs etc.. White looks out of place
Regardless great stuff arco68
@btnetro: You could maybe give the exact language you changed from and to (English -> Romanian)?
Also, try creating a new contact when your phone book is empty but your regional settings set to Romanian. Does the number issue still crop up?
Also, on your connection to computer issues, try restarting your computer and plug it in a different USB port. Or try another computer. Only post if you are absolutely certain its an issue with the ROM.
You seem to be having bugs specific to you, which could also mean that he procedure in which you installed the custom ROM was not right. Have you tried a reflash, following all the steps arco68 posted on his thread?
I won't be putting up all your issues on the OP unless someone else is also having the unique issues you are having - perhaps some users would like to try to reproduce the issues he is having as well?
Battlehero said:
I just installed this ROM and I have not ran into any bugs and I didn't notice any battery drainage. I'm unsure as what the cause is for most of the other users. I however had one slight issue which I resolved by allowing the default file manager root access, the issue was that I could not access my SD card through any normal file explorer. Other than that I'm enjoying this ROM keep up the good work!
Click to expand...
Click to collapse
I'm having the same issue as you regarding the SD card. May I know how you granted root access to the default file manager? The Superuser app provided with the latest rootkit doesn't seem to have that option to manually add apps.
EDIT: Hmm, a reboot seems to have fixed my issue. But could you still put your steps here in case anyone else has the same issue?
EDIT2: Found the steps:
Open File Manager, press Menu, Settings->General Settings->Access Mode
Choose Root Access Mode
Whosat said:
I'm having the same issue as you regarding the SD card. May I know how you granted root access to the default file manager? The Superuser app provided with the latest rootkit doesn't seem to have that option to manually add apps.
EDIT: Hmm, a reboot seems to have fixed my issue. But could you still put your steps here in case anyone else has the same issue?
Click to expand...
Click to collapse
Hello. Did I understand you correctly, that you applied the rootkit after installing CyanogenMod? If so, that's not necessary, and will obviously cause lot's of issues. Superuser app is already included in CyanogenMod.
** 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