Very strange thing happening on my device after i updated my kernel from hXORe v3.2c to 3.3 and now 3.4, the 4th core is not doing anything even under full load, this is shown in 3DMark benchmarks, especially in the physics tests.
hXORe 3.2c:
{
"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"
}
hXORe 3.3:
hXORe 3.4:
Anyone got any idea why this is happening or any way to fix this?
Update
Update: It was the GPU coupling that was disabling the 4th core, I'm not a developer so i've no idea what this is or what it does but I've disabled it now and i'm getting much better performance.
UK_Frosticles said:
Update: It was the GPU coupling that was disabling the 4th core, I'm not a developer so i've no idea what this is or what it does but I've disabled it now and i'm getting much better performance.
Click to expand...
Click to collapse
are you sure? i'd rather say you did not select 4 cores in core manager after reboot. i remember bedalus said something about 3 cores allowed by default and you have to select the number of cores you want after every reboot.
GPU coupling has nothing to do with that, it just means that GPU frequency scaling is linked to CPU frequency scaling (high CPU frequency -> high GPU frequency). by disable GPU coupling (decouple) the GPU frequency scaling depends on graphics workload.
reaper90 said:
are you sure? i'd rather say you did not select 4 cores in core manager after reboot. i remember bedalus said something about 3 cores allowed by default and you have to select the number of cores you want after every reboot.
GPU coupling has nothing to do with that, it just means that GPU frequency scaling is linked to CPU frequency scaling (high CPU frequency -> high GPU frequency). by disable GPU coupling (decouple) the GPU frequency scaling depends on graphics workload.
Click to expand...
Click to collapse
well all i did was go into core manager and turn off GPU Coupling and tried the tests again and the 4th core was then active, i didn't even reboot.
UK_Frosticles said:
well all i did was go into core manager and turn off GPU Coupling and tried the tests again and the 4th core was then active, i didn't even reboot.
Click to expand...
Click to collapse
That's not what i meant. When rebooting the phone, default kernel settings are loaded, which means in case of hXORe kernel only a maximum of 3 cores is allowed. So you have to select the desired number of cores in CoreManager and press Save&Exit, no reboot needed for the changes to take effect. You have to do this every time after reboot or you will be locked to a maximum of 3 cores.
But it seems the app always applies all settings and since your core slider is on maximum (i don't know why there's a 5 at your screenshot) the core number is also set to maximum by pressing Save&Exit even if you did not change the core slider.
So after every reboot, just open the app and check if core slider is on maximum and press Save&Exit to allow 4 cores.
reaper90 said:
So after every reboot, just open the app and check if core slider is on maximum and press Save&Exit to allow 4 cores.
Click to expand...
Click to collapse
Much appreciated, thanks for the information and yeh i wasn't quite sure why it was set to 5 by default? the only thing i could think is that it was including the power saving core.
EDIT, to avoid double post: Bit off topic but when i reboot my phone its really really sluggish and the CPU load is pegged at 100% for like 5 minutes, it'll also sometimes appear to crash and reboot again on occasions. Seems a little strange :/...
UK_Frosticles said:
Much appreciated, thanks for the information and yeh i wasn't quite sure why it was set to 5 by default? the only thing i could think is that it was including the power saving core.
EDIT, to avoid double post: Bit off topic but when i reboot my phone its really really sluggish and the CPU load is pegged at 100% for like 5 minutes, it'll also sometimes appear to crash and reboot again on occasions. Seems a little strange :/...
Click to expand...
Click to collapse
Try deleting app data or sliding to a lower number of cores and back up to 4, i think it's a small bug. It is not possible that LP core and quad core are active at the same time.
It is normal that Phone is a bit slower directly after reboot, because all processes and must load first, wich takes some time. But it should not crash or reboot. What rom do you use? Also did you install any additional mods and/or tweaks?
reaper90 said:
What rom do you use? Also did you install any additional mods and/or tweaks?
Click to expand...
Click to collapse
ARHD 6.2 and the lyapota modpack 6.5 i think.
UK_Frosticles said:
ARHD 6.2 and the lyapota modpack 6.5 i think.
Click to expand...
Click to collapse
ARHD should be stable, i don't know about the modpack, but it may cause issues. If you often get System freezes/crashes and reboots, you should try doing a nandroid backup and install a clean rom and see if your phone still crashes.
UK_Frosticles said:
ARHD 6.2 and the lyapota modpack 6.5 i think.
Click to expand...
Click to collapse
the mod pack really really kills the speed of the ROM. IMHO - don't use it...
Tried it on both ARHD & Elegancia and really slows down the device....
So unless and until you really need the features it provide - do not use it... my suggestion
Addicted2xda said:
the mod pack really really kills the speed of the ROM. IMHO - don't use it...
Tried it on both ARHD & Elegancia and really slows down the device....
So unless and until you really need the features it provide - do not use it... my suggestion
Click to expand...
Click to collapse
Right ok then I had no idea that it did, so how would one go about removing it? is it something like wipe cache and delvik , or is it something more complicated
UK_Frosticles said:
Right ok then I had no idea that it did, so how would one go about removing it? is it something like wipe cache and delvik , or is it something more complicated
Click to expand...
Click to collapse
Unless you have taken a backup before installing the mod pack, you are out of luck. You need to reinstall the ROM with full wipe. However if you have a backup before installing it - just restore the backup
UK_Frosticles said:
Right ok then I had no idea that it did, so how would one go about removing it? is it something like wipe cache and delvik , or is it something more complicated
Click to expand...
Click to collapse
Addicted2xda said:
Unless you have taken a backup before installing the mod pack, you are out of luck. You need to reinstall the ROM with full wipe. However if you have a backup before installing it - just restore the backup
Click to expand...
Click to collapse
You can also try reinstalling rom without wipe, this should overwrite all system relevant files with default ones. However you can't be sure that it really does so. I'd give it a try just flashing rom again without wipe, you can still full wipe when the issue persists.
Related
{
"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"
}
hi all,
my first android app ever ....
but maybe it helps you undervolting.
it has 3 textboxes for Vsel and an apply button
update:
now it has 6 textboxes 3xVsel 3xMhz
update2:
now it includes and load overclock.ko (you can uninstall milestone overclock)
update3:
autoapply at boot works now! but use with care!!!
update4:
-set values @ boot
-set to lowest mhz if screen off ...
update5:
-bugfix
update6:
-added the option to run stabilitytest (it ask to install if it's not installed) while scaling_max_freq is fixed to i.e. vsel1,vsel2 or vsel3
update7:
when i set my defy to 300mhz while screen is off then when a phonecall is incoming the defy is so slow that it takes ages for the screen to go on....
sometime it takes 2-3 ring befor i can answer the call
so setvsel set it to maximum speed on phoneringing befor the screen is on!!
if you have installed v6 you have to uninstall it first (its because it was a debugversion the new one is signed)
get it un market ! QR is attached
market://details?id=com.SetVsel.Inteks.org
big thx the milestone-overclock project that make this all possible !!!!!
http://code.google.com/p/milestone-overclock/
have fun
inteks
Thanks but can it's possible to include frequency ?
Like if i would like to have 1Ghz or 1.2Ghz 800Mhz on standard mode, 250Mhz when not use like this post :
http://forum.xda-developers.com/showpost.php?p=10195181&postcount=50
Its a good idea if battery charge level is include like Set CPU .
Thanks
mick711 said:
Thanks but can it's possible to include frequency ?
Like if i would like to have 1Ghz or 1.2Ghz 800Mhz on standard mode, 250Mhz when not use like this post :
http://forum.xda-developers.com/showpost.php?p=10195181&postcount=50
Its a good idea if battery charge level is include like Set CPU .
Thanks
Click to expand...
Click to collapse
Agree. That would be a great option! But it's already on you To-Do-List, so it will come, I guess
Anyways, the App is awesome! Makes things much easier. Thanks for that!
updated. see first post. its called SetVsel.apk now
inteks said:
updated. see first post. its called SetVsel.apk now
Click to expand...
Click to collapse
Great work
Sent from my MB525 using XDA App
updated.
it includes overclock.ko modul so you could uninstall milestoneoverclock. BUT till now no apply @ boot , sorry ......
Be patient
let me get this straight.pressing apply,leaving the numbers as is and tick the boot option, will make my phone underclock and save my battery? cos thats what i just did now.and i dont need to fiddle with setcpu or milestone...? i hope im right.thanks!
ok i saw the boot info just now. but apart from that i need to start this after boot,im all set?
mattisekholm said:
let me get this straight.pressing apply,leaving the numbers as is and tick the boot option, will make my phone underclock and save my battery? cos thats what i just did now.and i dont need to fiddle with setcpu or milestone...? i hope im right.thanks!
ok i saw the boot info just now. but apart from that i need to start this after boot,im all set?
Click to expand...
Click to collapse
yepp
but its beta (i should note that in the first post...) so setcpu or adb is usefull to check the result
danke schön!
Good work!
The app does work on my defy to overlock & change vsels once I press "apply".
But it seems doesn't auto apply after rebooting.
(I have checked the "Apply @ Boot" box...)
After I reboot and manually launch SetVsel.apk, the frequency & vsels value in the 6 boxes are exactly the same with what I set previously.
However, the "Apply @ Boot" was not checked, and the values below shows those settings are not applied.
Is it only me? Or should I also use some other apps in conjuction with SetVsel?
Thanks for any helps.
---------------------------------
Edit: Sorry, I didn't notice inteks said "till now no apply @ boot"...
I think the apply on boot checkbox is just a place holder (does nothing for the time being)
updated....
have fun
Thanks inteks
Can u help us in example values?
also include in first post which are stable.
Can you make some presets in app so we can select?
for example performance, battery save, etc?
my values are ->
300/30
700/46
1100/58
but every cpu is diffrent.....
tnx for the answer.
I cant get lower than 300mhz.
I set 250 but SystemPanel app shows me 300mhz as the minimum value.
my values are:
300/28
600/38
900/46
No issues with these values so far. Cant get lower then 300 as well Setcpu shows that it runs at 600 insteadt of 250.
Sent from my MB525 using Tapatalk
When rebooted, can the program autorun hidden? Actually show a black screen 1 or 2 seconds.
Thanks
nice app, thank you
demolition23 said:
tnx for the answer.
I cant get lower than 300mhz.
I set 250 but SystemPanel app shows me 300mhz as the minimum value.
Click to expand...
Click to collapse
I'm pretty sure lower is possible, but you need to change another file to display this - it's described at the overclock module site I think.
I can do 300/26 but only at 250MHz vsel 22 is stable.
Other values are:
600/32 and 800/44 or 1000/56.
hello everybody.
i would like to know what´s the best configuration for the hero to have a better battery perfomance with flykernel.
example:
{
"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"
}
Thanks
1200mhz? Is that a hero?
Its not hero , the resolution is to high.
what the.... flykernel runs on other systems? cool - I guess it makes sense that he builds it for other systems but I just never thought about that happening.
I think the screen is just a screen. Kernel from one device won't run on another.
tomekk_nt said:
I think the screen is just a screen. Kernel from one device won't run on another.
Click to expand...
Click to collapse
oh, so he grabbed a setcpu screenshot for example's sake?
ok, original poster, are you using a hero? LoL
I'm pretty sure of this
The screenshot is from another device / kernel, he was just using it as an example.
As for best configuration, there isn't one I am afraid. It is dependant on so many differing factors:-
- what apps update in the background and how often?
- how often you use the screen?
- what brightness do you have your screen on?
- how good is your signal?
- how many widgets do you have running?
- how well written the apps you use are (sky news for instance used to be a massive battery drain)
- how efficient your battery is (old batteries drain quicker)
that it is impossible to say. I personally don't use any profiles at all, I run at 19MHz min / 748MHz max and use the smartass governor, but I am so often around my charger (at home or at work) that I don't know what the battery life is like. It lasts more than 24 hours and linpack over 5.2 MFLOPS, which is enough for me.
yea - most common sense way to improve battery life is this:
reduce screen brightness manually as much as you can live with
slow down top speed of cpu as much as you can live with. in most roms I can live with something in the 450 mHz range or whatever that kernel provides as a lowish top end speed.
smartass is good for battery life - nice low bottom speed, very quick to speed up if necessary. but if you can live with some occasional slowdowns on unlock (the only side effect I get from the following setup) just use a low conservative-governor speed with screen off profile and higher but still low as you can live with speed with screen on using the ondemand governor.
oh, and turn off wifi when not using it, turn off bluetooth when not using it, make sure no apps request gps when not using it or turn it off too if you're paranoid (but gps only runs when an app asks it to run), and if you really want great battery life when screen is off then t urn off background updates except when you really want to update your data.
The image is only example
...and if you really want great battery life when screen is off then t urn off background updates except when you really want to update your data...
Click to expand...
Click to collapse
Can you do that automatically ?
yan74s said:
Can you do that automatically ?
Click to expand...
Click to collapse
there are apps you can install that do that automatically for you, but of course then you have another service running in the background all the time managing this stuff. I would imagine it's worth a try, but I personally need background updates enabled so my wife can ping me whenever she wants.
Let me just say this.
Look in the FlyKernel topic. He has a darn huge part there on what the best speed is.
And to make it lazy for ya.
172/614 smartass, and totally no profiles.
But it is more what you like.
If you want to go like I want to have a P4 and go to the 2.2 Ghz and try to run XP on it. Have fun
But in short, First read out a whole post of a kernel before making a new topic. next time post it inside the topic of the kernel. Less clutter on the board.
EDIT: I personally dont use setCPU because its another app running for something you can just configure with flykernel package itself. Same for all kernels. Just have to find out how . And now its time to go to bed, that was something I was planning to do 4.5 hours ago
12a is a great kernel..
I find 19/576 (interactive when screen on, conservative when off) works perfectly on froydvillain 1.7.2, but I'm using the included app cpu speed, not setcpu.
I don't have any problems with lag during games or anything else, so why overclock more if not needed? I have gone up to 730 though I didn't find performance was that much better, so I leave it at 576 unless otherwise needed.
Download: this post.
[AT&T] in the thread heading means that this kernel is not for the international version. This kernel is for sense ROMs only.
Enjoy flashing this with Hasoon2000's toolkit
{
"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"
}
Features
-A complete lack of aptitude for kernel development (see the download link for the configuration and tweaks)
Useful Links
-Thanks to reaper90 for providing an init.d template
Thanks to maxwen for a few bits of source code and generous help, hasoon2000 for his toolkit, and nik3r for his kernel module injector and the walkthrough he gave me to use it correctly, and a few other bits of source code. Mostly thanks to HTC for releasing the source! Thanks to Notechis for the artwork above. General thanks to LLoir who appears to be helping everywhere, and mike1986 for ARHD. Thanks to the community here, and my old haunt, the Nexus S section: without them I would still be less than an almost complete idiot.
Source: https://github.com/bedalus/ATnT
TOOLCHAIN: I'm going to do my best to stay up-to-date with the linaro toolchains courtesy of Christopher83: his thread (4.8.* are not yet compatible, use the latest 4.7.*)
v1.0 is here: http://d-h.st/7db
CoreManager.apk is here: http://d-h.st/R5l
-after rebooting, remember to open/save+exit to restore your preferences
-Please grant super-user permissions
Version 1.0 Notes
This version has the same features as the 3.4 version of my international version. You'll need to use the app above to set your preferences, and please feedback if there are problems, and feel free to ask any questions.
My kernel config
-Slide to Wake [S2W]
-Hotplugging with a user defined limit (using the above app)
-The low power core is prevented when awake, and the high-power quad-core is forbidden when the screen is off. This is to ensure performance when the screen is on, and power-saving when it is off (+ there is a two core minimum when device is awake)
-smartmax governor by maxwen
-added fast-charge to kernel (thanks maxwen)
-added BLX (thanks ezekeel)
-Available IO Schedulers: BFQ, CFQ (as default), Deadline, NOOP, SIO, ROW, and V(R).
-Miscelaneous tweaks: ticket based rwsem algorithm; Google's tcp proportion rate reduction algorithm; cifs; zcache with latest LZO; SLUB
Reserved in case I need it later
I noticed after flashing kernel looked in system /lib /modules nothing in there empty??? Everything is working far as I can see..edit I will flash it again didn't see v1.0 downloading it now to try
Sent from my HTC One X+ using xda premium
V1.0 has better performance to date guess that's what I'm really after.anyway..haven't been following ur thread from beginning so I may be trying to catch up is it normal to see module folder empty after flashing these kernels..also this feels smoother then all the other kernels for at&t .lol hope to get some OC soon
Sent from my HTC One X+ using xda premium
It's already OC'd to 1.7GHz (it should be 1.6GHz)
GPU OC I'm still thinking about
I normally use fastboot for kernels instead of hasoon2000's toolkit (it's a great toolkit, I'm just a CLI junkie). is this just the same "fastboot flash boot hxore_v1.0_ATnT.img" then "fastboot erase cache" and call it a day?
EDIT - I went ahead and did the above and it seems to have went well, so far so good. The only weird thing I noticed is that the capacitive buttons seem to be a lot less sensitive than before. they dont register most taps. have to really ham-fist them.
Running smoothly here! Awesome will see what happens after using this for a day! :thumbup:
iggdawg said:
I normally use fastboot for kernels instead of hasoon2000's toolkit (it's a great toolkit, I'm just a CLI junkie). is this just the same "fastboot flash boot hxore_v1.0_ATnT.img" then "fastboot erase cache" and call it a day?
EDIT - I went ahead and did the above and it seems to have went well, so far so good. The only weird thing I noticed is that the capacitive buttons seem to be a lot less sensitive than before. they dont register most taps. have to really ham-fist them.
Click to expand...
Click to collapse
Is it just a case of needing precision when tapping the centre of the button?
Yes, fastboot, but erase cache is not necessary
After some tinkering it seems like its probably a precision issue. Like the hotspots for the buttons are a little too far north or something.
Sent from my HTC One X+ using xda premium
---------- Post added at 04:38 PM ---------- Previous post was at 04:30 PM ----------
Also is there any place I can read up on some reference info for the Core Control apk? like what impact the hotplug and charging limit setting have
EDIT - did some hunting and found some descriptions: http://forum.xda-developers.com/showpost.php?p=41686727&postcount=321
I am also having problems with the buttons not registering when i press them..gunna go back to the stock kernel for now til this is fixed...other than that is seems to be going great!
I'm sure I can figure out what the problem is. I'll have a look later today
Test version: http://d-h.st/e7c
I've updated the slide to wake code. Has this fixed the buttons?
bedalus said:
Test version: http://d-h.st/e7c
I've updated the slide to wake code. Has this fixed the buttons?
Click to expand...
Click to collapse
I'm not sure what slide to wake is, but the capacitive buttons still has no feedback and it takes a lot of pressing to use them. But when screen is off, rapidly pressing the back & recent application capacitive buttons turns the screen on
S2W =Slide the tip of your finger across the button area to sleep/wake the device
bedalus said:
S2W =Slide the tip of your finger across the button area to sleep/wake the device
Click to expand...
Click to collapse
Ah it works! Btw, the capacitive buttons works but you have to swipe across it until you feel a vibration.
Maybe this is also a similar hotspot issue related with s2w?
bedalus said:
Test version: http://d-h.st/e7c
I've updated the slide to wake code. Has this fixed the buttons?
Click to expand...
Click to collapse
Sorry if this is a stupid question, but do I need to flash any modules with this kernel?
I've actually flashed Zarboz's custom kernel and associated modules a while back so should I revert back to stock?
Sent from my HTC One X+ using xda app-developers app
No need to worry about the modules, it's dealt with by nik3r's injector
great work bedalus!
bedalus said:
Test version: http://d-h.st/e7c
I've updated the slide to wake code. Has this fixed the buttons?
Click to expand...
Click to collapse
I still can't hit the buttons like I usually do. The hotspots still seem to live a little north of where they're supposed to. I kind of have to roll my thumb up from the bottom of the screen till it registers the tap on the buttons, it's close enough to the "real" screen area that trying to hit the hotspots usually ends up hitting something on the active part of the screen instead (like the app tray or the text message icon)
ROM CONTROL V 1.5
Tune settings, add tweaks, mods, all is working guys.
WHAT YOU NEED
-rooted phone
-custom kernel
-for crt-off animation a rom that has crt off anim support
-4.1+ android version
FEATURES
Code:
-Fsync enabler/disabler
-CRT-off anim enabler/disabler
-ext4 enhancements
-Disable IO stats
-Net tweaks, removing redirections, speeder browsing
-vacuum for optimize databases
-Edit deepest sleep state
-Disable battery fair sleepers for better battery backup
-vacuum for optimize databases
-GPS country chooser
-Governor and IO scheduler chooser
-GPU rendering
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOADS
V 1.5: http://d-h.st/7jf
EXPLAINING TWEAKS
KERNEL TWEAKS
-Added entropy
-Edited dirty_expire_centisecs and writeback values to an highter to improve battery
-reduced swappiness to 30
-cache pressure value reduced to improve performance
-page cluster set to 3, better multitask
MALI: mali max read set to 48 more smooth, mali debug level set to 0 more fluency
FSYNC: fsync is an android capability that allows the system to write continuously data from ram to flash to avoid data loss due to a sudden shoutdown. It is enabled by default, if you have a stable system you can also disable it because it can improve performance (less writing by cpu, less battery using, better performance!) It's at your risk!
CRT-OFF EFFECT: Introduced in 2.3.6 it is a screen of animation, if your kernel supports it you can enable or disable it in time by this app
CPU TUNE: included a cpu control, you can choose frequencies, governors and schedulers, and the settings are sticky also after reboot!
IO STATS: disabling this the system overall is more smooth
EXT4 enhancements: various tweaks to the ext4 partitions, all should be better and smoothly
SD CARD TWEAKS: increase sd card r/w from 128 (def) to 2048, now you will have better read and write speeds of your sdcard
BATTERY: You can set the deepest sleep state (3-4-5) and disable the fair sleepers, this can improve batery backup
VACUUM: It cleans the system, the apps, it is such a cleaner that keeps clean the sqlite databases.
GPS: choose your favourite country and enjoy a faster gps locking! No more waiting!
GPU renderer: You can disable the hardware render to enable the software one. UI is snappier.[/CENTER]
MAJOR TWEAKS WILL BE ENABLED ONLY AFTER REBOOT!
ENJOY!
Thank you to all that have helped me to make possible this little project.
Tips for new features or improvements are welcome!!
Thanks, but you must describe more what exactly do every settings.
Powered by CM10.1
R_a_z_v_a_n said:
Thanks, but you must describe more what exactly do every settings.
Powered by CM10.1
Click to expand...
Click to collapse
Just done, yesterday I had no time
Great work guy.
I know that you want to make this kernel tweaking app universal for all android devices, but I hope that you also can make another app only for tweaking cocore kernel because the only cocore tweaking app is not in development anymore( I think so). Cocore kernel has a lot of settings to play with, so I hope that you can make an app for it to make all the users easier to play with the kernel It is not a request, just a suggestion
[email protected] said:
I know that you want to make this app this kernel tweaking app universal for all android devices, but I hope that you also can make another app only for tweaking cocore kernel because the only cocore tweaking app is not in development anymore( I think so). Cocore kernel has a lot of settings to play with, so I hope that you can make an app for it to make all the users easier to play with the kernel It is not a request, just a suggestion
Click to expand...
Click to collapse
Yes i will do)
Inviato dal mio GT-I9070 utilizzando Tapatalk
What does vacuuming do besides clean floors LOL... curious tho as I not tried that setting yet. Nice app though!!
bobfrantic said:
What does vacuuming do besides clean floors LOL... curious tho as I not tried that setting yet. Nice app though!!
Click to expand...
Click to collapse
new update it s coming:highfive:
I also hope that you can add all the necessary explanation for each settings in the app as well
[email protected] said:
I also hope that you can add all the necessary explanation for each settings in the app as well
Click to expand...
Click to collapse
Including that
Inviato dal mio GT-I9070 utilizzando Tapatalk
Version 1.5 online!
[email protected] said:
I also hope that you can add all the necessary explanation for each settings in the app as well
Click to expand...
Click to collapse
New UI, new style, hope you like it.
Added a guide into the app.
V 1.5: http://d-h.st/7jf
[/IMG]
A big thanks to @GæxD for new graphic!!
See ya
EDIT: op updated
hastalafiesta said:
New UI, new style, hope you like it.
Added a guide into the app.
V 1.5: http://d-h.st/7jf
[/IMG]
A big thanks to @GæxD for new graphic!!
See ya
EDIT: op updated
Click to expand...
Click to collapse
Great! Now I am waiting for your cocore tweaking app
[email protected] said:
Great! Now I am waiting for your cocore tweaking app
Click to expand...
Click to collapse
Released:victory:
hastalafiesta said:
Released:victory:
Click to expand...
Click to collapse
Thanks, downloaded
Q&A for [ROM][UB][4.4.4][W27-S3][XperiaSTE Team] CyanogenMod 11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Boia11 said:
Dear Dev ( @Info4Geek, @Gava97 and @Garcia98), I have many problem with the last build (W27):
- The system.UI go in loop crash also the reboot the problem persist :crying:
- Occasionally the screen not wake up from standy-by (I think that happens when the battery level drops under 20%), after more attemps to wake the phone...I have found that if I connect to USB the phone return to work normally.
This is the joke of ROM of the last two day when the screen not wake up:
- View attachment 2964671
- View attachment 2964672 (in this moment the touch work bad....too low reactive)
- View attachment 2964684
- View attachment 2964674
Thanks for your time and work!!!! :highfive:
Click to expand...
Click to collapse
The same happens to me.
However, which governor and i/o is suggested to use to reduce the battery drain?
Insane93 said:
The same happens to me.
However, which governor and i/o is suggested to use to reduce the battery drain?
Click to expand...
Click to collapse
Hi, for me the best governor to reduce battery drain are SmartAssV2 (regular scalining) and the LionEarth (Now I use it - It's similar to Interactive but It scale to low frequency too fast).
For the I/O.... I use ROW (It's more linear to control write and read); more people suggested the SIOPLUS (an evolution of the original SIO) but It's not avaliable in this CM11 kernel (If you would test it, you can try the Garcia98 kernel...know as "Bravekernel")
Using Album/Camera reboots the phone
Hey there ,
Using The Album App makes the phone reboot [Weekly 27] , Any Solutions ?
Boia11 said:
Hi, for me the best governor to reduce battery drain are SmartAssV2 (regular scalining) and the LionEarth (Now I use it - It's similar to Interactive but It scale to low frequency too fast).
For the I/O.... I use ROW (It's more linear to control write and read); more people suggested the SIOPLUS (an evolution of the original SIO) but It's not avaliable in this CM11 kernel (If you would test it, you can try the Garcia98 kernel...know as "Bravekernel")
Click to expand...
Click to collapse
Thank you
What do you think about Conservative governor?
Insane93 said:
Thank you
What do you think about Conservative governor?
Click to expand...
Click to collapse
It's good but the system lost the reactivity....I have try more governor and the LionHeart (with ROW) it's the best compromised between battery life and reactivity.
With the conservative governor (and if you set max frequency to 800Mhz) you can increase the normal battery life up to 4/6h. (if you use the phone a lot it is the best governor because the display drain battery in short time)
From my experience...the SmartAssV2 it's very good but create lags of reactivity in certain case because the frequency don't scale to high frequency more fast (it's evident when load callUI in inbound call).
Boia11 said:
Dear Dev ( @Info4Geek, @Gava97 and @Garcia98), I have many problem with the last build (W27):
- Occasionally the screen not wake up from standy-by (I think that happens when the battery level drops under 20%), after more attemps to wake the phone...I have found that if I connect to USB the phone return to work normally.
Click to expand...
Click to collapse
Same problem here, but the problem is not occasional, just when battery goes under 20%, and i have to charge the phone.
Wallpaper also gets removed.
First install, fully wiped.
Thanks.
EDIT: How to manage CPU Governor \ Scheduler?
GPS not working
Guys thanks for developing this Cynogenmod11 .. stupid xperia wont even think about lower end phones like Xperia U
GPS is not working please look into it, I have attached some screen shots of logcat and gps test app ...
P.S sometimes gps work fine ( I get all the signal and lock in few seconds.. when I get that (to check hardware faults) I restart the device and it wont even get a signal )
{
"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"
}
google music
there is the possibility that it also solves the problem of google music?
Lockscreen
Is it possible to reset the lockscreen apps to default (with telefon, contacts,sms etc) ???
Thank you very much I have tested cm11 weekly 27 and stable 4 and I find them really smooth although it reboots sometimes in general I consider it as an official rom!!
Weekly 28 is working well, no more battery under 20% problems.
By the way, sometimes the back button is failing, someone with the same problem?
And again, is there a menu to change CPU Governor \ Scheduler? Battery gets down fast, and i have to put "energy save" every restart.
wifi direct?
How do you enable or run the wifi direct? Because of the wifi in the settings where it should be there.
[weekly 28]cLock crashed and call
Hi guys., I've updated to weekly 28 and it's great but I've got some issues :
-cLock crashed everytime I try to modify an alarm; it doesn't allow me to turn off or delete any alarms.
-Everytime I try to call someone I've got a black screen and I can't hear anything.
Should I try a clean install?
Thanks anyway
nexusj said:
Hi guys., I've updated to weekly 28 and it's great but I've got some issues :
-cLock crashed everytime I try to modify an alarm; it doesn't allow me to turn off or delete any alarms.
-Everytime I try to call someone I've got a black screen and I can't hear anything.
Should I try a clean install?
Thanks anyway
Click to expand...
Click to collapse
For the problem of the calls you have to help a developer (I not be a dev). If you need the alarms and the alarm not used cLock, but try to use the stock clock app.
luca20 said:
For the problem of the calls you have to help a developer (I not be a dev). If you need the alarms and the alarm not used cLock, but try to use the stock clock app.
Click to expand...
Click to collapse
Thanks for reply.
How can I help the devs? Should I provide a log? ^^
About alarms I installed a new app, "Timely", and disabled cLock app