Hello xda!
Theres something strange going on with my Sensation..
I can not set up my own frq's.
Everytime I set some it goes higher. For example..
I am @ 1080-475 I switch the window to set some profiles and back to the main. bah.. Current max: 1134.. 1450.. 1552.. 1134.
Bar I set before should lock it @ 1080 and it does but just in practice.
I was trying to set some other governors with no succes. It goes higher everytime.
Root acces was given, ROMs tested.
I got phone from my brother. Is it even possible to change some hardware settings or wtf is it that block my ideas????
Lynxen said:
Hello xda!
Theres something strange going on with my Sensation..
I can not set up my own frq's.
Everytime I set some it goes higher. For example..
I am @ 1080-475 I switch the window to set some profiles and back to the main. bah.. Current max: 1134.. 1450.. 1552.. 1134.
Bar I set before should lock it @ 1080 and it does but just in practice.
I was trying to set some other governors with no succes. It goes higher everytime.
Root acces was given, ROMs tested.
I got phone from my brother. Is it even possible to change some hardware settings or wtf is it that block my ideas????
Click to expand...
Click to collapse
what rom do you have?
insert this line in init.qcom.post_boot.sh file
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
in the <the value> put your desired freq
do the same for cpu1
then reboot
note: put the lines where it starts with :
case "$target" in
"msm8960")
rzr86 said:
what rom do you have?
insert this line in init.qcom.post_boot.sh file
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
in the <the value> put your desired freq
do the same for cpu1
then reboot
note: put the lines where it starts with :
case "$target" in
"msm8960")
Click to expand...
Click to collapse
I am using SlimKat and Viper. Same bug excist @ both of the roms. Kernels provided with shantur, sebastian and libelty are bugged.
I've changed those values with no results. Once I was trying to set maxcpu_info my root explorer stucked @ saving process. Sth was remaking values @ 1540000 mhz just after rootacces was given to explorer. Some deep **** is going down there.
That's why Sensations are overheating, it's same bug threw all stock kernels/rom @ this forum.
Max values can not be set! They re permanent for some reason - failed coding I suppose.
Libelty Kernel fix Vipers issues. There's no kernel working with KK.
Lynxen said:
I am using SlimKat and Viper. Same bug excist @ both of the roms. Kernels provided with shantur, sebastian and libelty are bugged.
I've changed those values with no results. Once I was trying to set maxcpu_info my root explorer stucked @ saving process. Sth was remaking values @ 1540000 mhz just after rootacces was given to explorer. Some deep **** is going down there.
That's why Sensations are overheating, it's same bug threw all stock kernels/rom @ this forum.
Max values can not be set! They re permanent for some reason - failed coding I suppose.
Libelty Kernel fix Vipers issues. There's no kernel working with KK.
Click to expand...
Click to collapse
liberty's and sebastianFM's kernel aren't bugged
i have changed cpu frequencies successfully
in vipers rom disable pnpmanger from venom tweaks
then put your desired cpu freq
about slimkat rom i can't tell you somethig because i have never used that rom
also in stock kernels you can't changed nothing
they do not support overclock or underclock
rzr86 said:
liberty's and sebastianFM's kernel aren't bugged
i have changed cpu frequencies successfully
in vipers rom disable pnpmanger from venom tweaks
then put your desired cpu freq
about slimkat rom i can't tell you somethig because i have never used that rom
also in stock kernels you can't changed nothing
they do not support overclock or underclock
Click to expand...
Click to collapse
It's possible to scale CPU frequency in slimkat ROM too.
So.. Now I have a cm based ROM in my Xperia J and then volume of media when you listen through earphones or headphones is like all other devices... But when i put the stock ROM or a stock based ROM like the Alien ROM.. The in earphone/ headphone media volume is considerably low.. Can i fix this by root? Someone please help!
Yes and No,you can try Viber4Android (need root),it can increase sound by 6dB
but it's not like CM10 volume
Okay.. Will try that but can't i edit or replace any frameworks or any other files?! How is the volume high only in cm10? Is it the kernel or anything else?!
Probably the safest way to increase your volume would be to install Viper4Android FX.
After installing the V4A drivers, reboot, open the app and do the following:
1> Find "Playback Gain Control"
2> Check "Enable"
3> Under "Select Effect Strength", choose from either "Moderate" or "Extreme", depending on the volume you find comfortable.
These are the settings I use, without any problem so far.
Good day!
Please hit Thanks if it helped!
Okay thanks a lot.. Will try viper!
[Q&A] [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F
Q&A for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS
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.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
@Cl3Kener: Big thanks for your hard work. Installed your kernel yesterday, and can definately see some improvements.
@ramjet73: Big thanks to you too. I followed your posts/instructions and flashed rastapop+uber and am happy i finally took the plunge.
Now for my question: I have the tricksterMOD and I can't see any color profiles (except the default). How can I apply other profiles? I only see one.
Regards,
On LiquidSmooth LP 4.0 with UBER-L 3.4.105
Governer = optimax
Scheduler = zen
Read Ahead Buffer Size = 3072
Everything is running smooth and fast! Good battery life!
Low brightness after install
Hello, I gave a question... When I installed a last Uber kernel L v4.10 from 9 December of 2014... I have a very low brightness... How can I fix it...
Also I cannot make OC more than 2.7 or 2.8 ... Phone doesn't boot... And how I can fix it...
Thank you for a answer
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Are there any negative consequences for clocking the minimum frequency at 96MHz?
Usb-otg f2fs
I'm currently using the latest version of UBER-L kernel (01/01/15).
I have formatted my Micro USB to F2FS and would like to use it with my phone. TWRP recognises the USB and mounts it successfully, but the ROM (OptiPop) does not mount the USB. Both mount the USB fine when it is formatted to FAT32.
Is it possible for me to use F2FS using USB-OTG?
Thanks.
Edit: Got it working by using the 'Stickmount' app. ^_^
FloGatt said:
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Click to expand...
Click to collapse
I disabled trimming and I dont see a difference with f2fs. I would conclude that it isn't necessary with f2fs
Is there changelog of the new kernel version?
FloGatt said:
Is there changelog of the new kernel version?
Click to expand...
Click to collapse
Its all on github. The link is on the OP of the original thread. (The one with the download links)
GPU clock not going above 450MHz
Hey, I'm using this kernel (latest version as of now), on a clean flash of Optipop (also latest as of now - 11/01) with F2FS.
I set the max gpu clock to 650000000 in the uber_v1.3.cfg file in /etc
(also by terminal as in the 2nd post just to be sure) (echo "650000000" > the path and all)
Apps like System Monitor Lite and CPU-Z confirm that the max gpu clock is 650Mhz (Adreno 330 @ 650Mhz).
I have also set the performance governor (in the config file, and I tried via synapse + UKM 3.6.1 too) (I have set synapse not to apply settings on boot, so that should not be interfering with the init config of uber kernel until I set something in it.) I have no other kernel tweaking apps anyway.
However, the clock only goes up to 450MHz no matter what. It goes directly to 450 when touching the screen due to the performance governor, so I know settings are being applied.
However System Monitor, CPU-Z etc all show, current clock: 450MHz, Max Clock 650Mhz.
Even benchmarking with GFX bench gives results basically identical to the stock Nexus 5 with 450MHz, so there is no performance and FPS difference that should be there.
I searched the developer thread and found a few posts from many months ago that the gpu overclock was working properly for many people, with an appropriate improvement in FPS and benchmarks, with a couple of people also having my issue, that whatever of 650/533/450 max I apply, gpu doesn't go over 450MHz. However I couldn't find any solution.. it stopped working properly at some point between those builds when Chet introduced 533/650 and now?
I can't post in the dev thread (less than 10 posts).
This is reproducible, right after a clean boot, not a thermal issue (am not overclocking CPU, not running any CPU benchmarks, temp is less than 50C).
Hope someone can help. Thanks!
Installed Optipop back onto my N5 today. After a few hours of the phone being on the UI starts to act up then eventually needs a reboot to get back to being functional. I then flashed UberL kernel and now my screen is fuzzy and glitches out. Never had this problem in the past with Optipop or UberL. Please don't ask if I dirty flashed or deleted the android folder. I completely wipe my phone before I install a new ROM. I have been installing ROMs for a good minute now and have never seen this before. I have tried at least 5 other rom/kernel combos.....none have the same affect as UberL and Optipop. Yes I've tried F2FS ONLY Permissive Only and EXT4/F2FS Permissive and Enforcing with no luck.
Has the issue with the missing charging icon when the phone is turned off and plugged in reappeared? I have System, Data, and Cache formatted as F2FS and flashed F2FS-ONLY-Lollipop-Kernel-Cl3Kener-Kexec-Permissive.zip before flashing UBER, but I am still having this issue. Everything else appears to be running smoothly.
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
sirarduin said:
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
Click to expand...
Click to collapse
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
JayR_L said:
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
Click to expand...
Click to collapse
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
sirarduin said:
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
Click to expand...
Click to collapse
So you are saying that fixes the issue with the cfg file?
JayR_L said:
So you are saying that fixes the issue with the cfg file?
Click to expand...
Click to collapse
After 2 Benchmarks, i can say that doing this fixed MY problem. Uber/sabermod is now working realy well for the performance. Uses AnTuTU to check if its working. It upgraded a lot the performance for me.
Which governor gives me more performance?
[email protected] said:
Which governor gives me more performance?
Click to expand...
Click to collapse
performance ?! but it will drain your batterie a lot.
Hi,
I have installed S.H.I.E.L.D. ROM about 2 days ago... many thanks to @Tkkg1994... the ROM seems perfect so far.
The only thing (maybe a bug?) is "double tap to wake" that is too sensitive. Only a soft touch and display switch ON.
There is a solution? Some string or value in some system file?
Thanks a lot for answer
You have a functional dt2w? How come? It is only in settings and need a custom kernel to wake up.
agarth said:
You have a functional dt2w? How come? It is only in settings and need a custom kernel to wake up.
Click to expand...
Click to collapse
It's enabled in S.H.I.E.L.D. Rom... I think it has default kernel B165 with enabled value in .xml file. Maybe it is default supported in stock kernel...
Really!
How we can do it with stock rom 158 + Root?
On SHIELD ROM, I have:
Build.prop file in folder:
/System (string added by me)
/System/vendor
with this string: ro.config.hw_easywakeup=true
On /System/emui/base/xml
file:
hw_easywakeupmotion_config.xml
string:
<EasyWakeUpMotion name="Double_Touch" support="1" value="0" flag="0" keycode="131" />
In Settings>Smart Assistance>Motion Control
SCREEN OFF GESTURES - Double Touch
same here, hope someone can figure out why it's so sensitive. one tap would wake up the screen.