Ok so I was reading that bootloader effort thread and _base2 had mentioned overclocking his RAZR I tried to link the post and it wasn't working well on the app...kept foreclosing so anyways...I made a script that activates the second core...the way I verified this is looking in system tuner with it running and with out...also without it shows as an ARM processor in antutu benchmark and a dual core with it. with the limits of our kernel its not going to let us multithread obviously if I am not mistaken
Razz1 was the original poster if this on rootzwiki for the razr
If you choose to make changes or try it and something bad happens its up to you and I can't be held responsible
Ok so to further clarify what im trying to say with this is....prior to using this the second core was not visible using cat proc /cpuinfo nor was it available to java according to quadrant or antutu...after it is available and shows in the cat
This is what I used when I built my script
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
trafalger888 said:
Ok so I was reading that bootloader effort thread and _base2 had mentioned overclocking his RAZR I tried to link the post and it wasn't working well on the app...kept foreclosing so anyways...I made a script that activates the second core...the way I verified this is looking in system tuner with it tunning and with out...also without it shows as an ARM processor in antutu benchmark and a dual core with it I will go online and attach it it is very simple script and yall can tell me if you think it works or makes a difference for you...with the limits of our kernel its not going to let us multithread obviously if I am not mistaken
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
sir, im confused as to what this script does
Sent from my Milestone X2 using Tapatalk 2 Beta-4
ztotherad said:
sir, im confused as to what this script does
Sent from my Milestone X2 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
Ok so from what I could find and tell the second core was not being utilized on our phone correct? So what I was trying to do and from what I can see is enabling the second core...
And I am having trouble uploading it will paste what I made into a script...
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
trafalger888 said:
Ok so from what I could find and tell the second core was not being utilized on our phone correct? So what I was trying to do and from what I can see is enabling the second core...
And I am having trouble uploading it will paste what I made into a script...
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
Click to expand...
Click to collapse
okay so what youre saying is that this script should use the other core efficiently, right?
Sent from my Milestone X2 using Tapatalk 2 Beta-4
Just looking for feedback if what I am seeing is correct because prior to doing this the second core was not visible at all and from what I see in system monitor its running at least
Sent from my DROID X2 using xda premium
ztotherad said:
okay so what youre saying is that this script should use the other core efficiently, right?
Sent from my Milestone X2 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
What I am saying is that this is the stock out put from cat /proc/cpuinfo before
ocessor : ARMv7 Processor rev 0 (v7l) processor : 0 BogoMIPS : 1992.29
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x1 CPU part : 0xc09 CPU revision : 0
Hardware : Daytona Revision : 83a0
This is after
{
"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"
}
I can't make any guarantee that it will be efficient lol....but all im trying to say is that it would appear that its working
Hopefully I am making sense in what im trying to explain
Nice! I need to give this a try.
Sent from my DROID X2 using Tapatalk 2 Beta-4
hedwig34 said:
Nice! I need to give this a try.
Sent from my DROID X2 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
Tell me what you see, improvement wise, or not...im just going by what I see right now and haven't done a lot to test or anything like that
Sent from my DROID X2 using xda premium
Umm how do u implement this particular mod? For dummies lol.
Cyanogenmod
king..kranium said:
Umm how do u implement this particular mod? For dummies lol.
Cyanogenmod
Click to expand...
Click to collapse
What I did is made a script in rom toolbox pro....under the scripter option mainly because script manager and I never got along great app just never worked well foe me....which ia probably user error...anyways if you copy the lines above and go to the scripter hit make new script paste it in and press on it select at boot and then you can just run it from there as well...you can enter it in the terminal but from my testing it that way you will lose it when you reboot so you would have to re enter it
Sent from my DROID X2 using xda premium
I had some time to try this out this morning.
I made a script called cpu1 with this in it:
Code:
#!/system/bin/sh
echo "==================================="
echo "cpuinfo before:"
echo "==================================="
cat /proc/cpuinfo
echo ""
echo ""
echo "==================================="
echo "activate cpu1:"
echo "==================================="
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
echo ""
echo ""
echo "==================================="
echo "cpuinfo after:"
echo "==================================="
cat /proc/cpuinfo
echo "==================================="
I put that script /mnt/sdcard/
Then ran it in a terminal in a terminal (i'm using eclipse and there is one built in):
Code:
$ export PATH=/data/local/bin:$PATH
$su
# cd /mnt/sdcard
# pwd
/mnt/sdcard
# sh ./cpu1 > cpu1.txt
# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS: 1998.84
processor : 1
BogoMIPS: 1992.29
Features: swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part: 0xc09
CPU revision : 0
Hardware: Daytona
Revision: 83a0
Serial : 02804105417f8657
#
the # sh ./cpu1 > cpu1.txt line saved the output to /mnt/sdcard.cpu1.txt
Here is what is in cpu1.txt:
Code:
===================================
cpuinfo before:
===================================
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1998.84
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 0
Hardware : Daytona
Revision : 83a0
Serial : 02804105417f8657
===================================
activate cpu1:
===================================
===================================
cpuinfo after:
===================================
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1998.84
processor : 1
BogoMIPS : 1992.29
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 0
Hardware : Daytona
Revision : 83a0
Serial : 02804105417f8657
===================================
I have not done much with benchmarks so I just picked Antutu and ran one before and then after.
Take a look at the screenshots attached. The after looks slightly better but it also shows that I had more ram. So I don't know if it helped. Interesting stuff though.
hedwig34 said:
I had some time to try this out this morning.
I made a script called cpu1 with this in it:
Code:
#!/system/bin/sh
echo "==================================="
echo "cpuinfo before:"
echo "==================================="
cat /proc/cpuinfo
echo ""
echo ""
echo "==================================="
echo "activate cpu1:"
echo "==================================="
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
echo ""
echo ""
echo "==================================="
echo "cpuinfo after:"
echo "==================================="
cat /proc/cpuinfo
echo "==================================="
I put that script /mnt/sdcard/
Then ran it in a terminal in a terminal (i'm using eclipse and there is one built in):
Code:
$ export PATH=/data/local/bin:$PATH
$su
# cd /mnt/sdcard
# pwd
/mnt/sdcard
# sh ./cpu1 > cpu1.txt
# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS: 1998.84
processor : 1
BogoMIPS: 1992.29
Features: swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part: 0xc09
CPU revision : 0
Hardware: Daytona
Revision: 83a0
Serial : 02804105417f8657
#
the # sh ./cpu1 > cpu1.txt line saved the output to /mnt/sdcard.cpu1.txt
Here is what is in cpu1.txt:
Code:
===================================
cpuinfo before:
===================================
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1998.84
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 0
Hardware : Daytona
Revision : 83a0
Serial : 02804105417f8657
===================================
activate cpu1:
===================================
===================================
cpuinfo after:
===================================
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1998.84
processor : 1
BogoMIPS : 1992.29
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 0
Hardware : Daytona
Revision : 83a0
Serial : 02804105417f8657
===================================
I have not done much with benchmarks so I just picked Antutu and ran one before and then after.
Take a look at the screenshots attached. The after looks slightly better but it also shows that I had more ram. So I don't know if it helped. Interesting stuff though.
Click to expand...
Click to collapse
Thank you for the thoroughness...I was actually going to post what I found which is very similar...I don't know but to me there does seem yo be some improvement in the smoothness of my ui as well as in the speed if loading games and some smoothness as they run...I have also noticed that I have had less force closes with different apps...of course there really ia no way to quantify those observations but it is what I have been seeing....I also notice that I get 3-5 fps enabled than I do not...while not a huge difference was just something I noticed
Sent from my DROID X2 using xda premium
trafalger888 said:
Thank you for the thoroughness...I was actually going to post what I found which is very similar...I don't know but to me there does seem yo be some improvement in the smoothness of my ui as well as in the speed if loading games and some smoothness as they run...I have also noticed that I have had less force closes with different apps...of course there really ia no way to quantify those observations but it is what I have been seeing....
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
No problem there. You got me curious and I wanted to know too. I've not really used it too much after setting cpu1 on. I think I'll add this to /etc/init.d/ so it sets automatically on reboot and see how things go for a few days.
Hey if it feels better and doesn't hurt anything. I say leave it activated.
hedwig34 said:
No problem there. You got me curious and I wanted to know too. I've not really used it too much after setting cpu1 on. I think I'll add this to /etc/init.d/ so it sets automatically on reboot and see how things go for a few days.
Hey if it feels better and doesn't hurt anything. I say leave it activated.
Click to expand...
Click to collapse
I agree
Sent from my DROID X2 using xda premium
I haven't done or used any scripts on my x2.. but I've had it for the past 7 months and have been doing a lot of flashing.. so anyway someone would be willing to put this in step by step format so that others can have dual core enables as well?
I can probably mess around with it and figure it out.. but I would rather follow a guide that ensures I'm doing it correctly.. anyway thanks for all the new dev stuff going on.. I feel brighter days for the x2.
-sips coffee, sparks a blunt *.*
I would like to warn everyone that performing this mod WILL severely impact your battery usage. The Android operating system is designed to operate on ONE processor and turn the second one on on-demand. IF you choose to enable both processors, your phone will run better/fast/snappier, however, this will eat your battery. Just a warning.
You can monitor what is happening with the command:
Code:
htop
Ciao!
Moon Shadow - NM said:
I would like to warn everyone that performing this mod WILL severely impact your battery usage. The Android operating system is designed to operate on ONE processor and turn the second one on on-demand. IF you choose to enable both processors, your phone will run better/fast/snappier, however, this will eat your battery. Just a warning.
You can monitor what is happening with the command:
Code:
htop
Ciao!
Click to expand...
Click to collapse
Except it seems with this damn phone, that second processor never helps. With a phone with these specs you'd expect it to be able to run a live wallpaper smoothly or not chug to a halt when installing something while multitasking.
My data gets really slow after a while with this script on. I tried it twice in the same area, but I only got it to work normally after a reboot (the script is not on automatically).
Sent from my Android
RValentinF said:
My data gets really slow after a while with this script on. I tried it twice in the same area, but I only got it to work normally after a reboot (the script is not on automatically).
Sent from my Android
Click to expand...
Click to collapse
Sounds like an unrelated issue. I fail to see how enabling a second core could disrupt cell service.
Though, I suppose anything is possible.
Moon Shadow - NM said:
I would like to warn everyone that performing this mod WILL severely impact your battery usage. The Android operating system is designed to operate on ONE processor and turn the second one on on-demand. IF you choose to enable both processors, your phone will run better/fast/snappier, however, this will eat your battery. Just a warning.
You can monitor what is happening with the command:
Code:
htop
Ciao!
Click to expand...
Click to collapse
Mine has not been too bad but its something that I am currently evaluating
Sent from my DROID X2 using xda premium
Related
Link to original thread so that can be up-to-date with the latest updates for this module: http://forum.xda-developers.com/showthread.php?t=1053587
Thanks to owain94 for reminding me!
Originally posted by doixanh...
Rom cookers: if you include this module in your ROM, please make a link to this post in your release post, so your users can know how to work with it and update the module themselves
Intro
Perhaps all of you know that all of our custom ROMs are laggy. It lags every 5 to 7 seconds. Fps2d clearly shows that.
dmesg shows that also:
So what to do? It seems that the stock driver is buggy.
I've been working with those stupid lags for some days, and now, here it is my friends No more stupid MDDI lags
{
"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"
}
Release history
April 28 v001. Release for x10 mini pro. Need more test.
Source will be provided soon (tomorrow) at github : https://github.com/doixanh/X8Features
Requirements
- Rooted
- Latest baseband (xxx015)
- Some basic knowledge
Instruction for manual installation:
- Remount /system as rw, either with adb or with root explorer
- Download attached file, unzip, push x8mddi.ko to /system/lib/modules
- Change hw_config.sh in your /system/etc, add this code at the beginning
Code:
insmod /system/lib/modules/x8mddi.ko # fix mddi lags
- Push modified hw_config.sh back to your phone, reboot
xRecovery updates:
There are many ROMs and many modules right now. I will not be able to maintain update.zip. You have to follow manual installation above.
X10 mini pro : I've just uploaded a x10 mini version. Test it carefully by manually type insmod /system/lib/modules/x8mddi.ko before applying to hw_config.sh, otherwise you may get boot loop!
Bug reports
When you report a bug please attach the following files:
- /system/etc/hw_config.sh
- A copy of logcat (you can use adb logcat > logcat-bug.txt)
- A copy of live dmesg (you can use adb shell cat /proc/kmsg > dmesg-bug.txt as soon as the device is ready)
Zip 3 files above and attach in to your post. Thanks.
Disclaimer
I'm not responsible if this module damages your lovely phone. Use it at your own risk!
X10 Mini Pro: http://forum.xda-developers.com/attachment.php?attachmentid=580654&d=1303993333
__________________
If you like my post, click the
button!!
Added to my tweaks, it's stable
"The integration of MDDI is said to enable the adoption of advanced features, such as high-definition (QVGA) LCDs and high-resolution megapixel cameras for wireless devices, and supports capabilities such as driving an external display or a video projector from a handset." Wikipedia
So we can expect that the camera is going to work?
Need help
D4rKn3sSyS said:
Added to my tweaks, it's stable
Click to expand...
Click to collapse
@D4rKn3sSyS can you please make update.zip for above mentioned MDDI please..
for mini pro.......and give us link so we can check dat out......
that kid death214 really annoys me posted each module doixanh do he know we got the x8 forum ourselfs and that we have eyes?
although doixanh nice ****ign work! and death214 no thanks for the ****ing ugly annoying repost!
owain94 said:
that kid death214 really annoys me posted each module doixanh do he know we got the x8 forum ourselfs and that we have eyes?
although doixanh nice ****ign work! and death214 no thanks for the ****ing ugly annoying repost!
Click to expand...
Click to collapse
Lol owain xD... yeah thats annoying, but well i think he's trying to help.
And the people who wants a update.zi, check my signature, and then click on tweaks cm6 and cmm7, i will ALLWAYS ADD DOIXANH post, to this tweaks, so i think death you should not do this post, if someone dont want tweaks, he should go to x8 forums
D4rKn3sSyS said:
Lol owain xD... yeah thats annoying, but well i think he's trying to help.
And the people who wants a update.zi, check my signature, and then click on tweaks cm6 and cmm7, i will ALLWAYS ADD DOIXANH post, to this tweaks, so i think death you should not do this post, if someone dont want tweaks, he should go to x8 forums
Click to expand...
Click to collapse
i mean it is really annoying that he doesn't link to original topic from doixanh (damn why not an easy forum name?)
just put a link here to original topic and remove download link so users here will be sure they download the last version
now dark!
**** you colombians and export your best coffee to us NOW! coz i really want an colombian coffee right now
owain94 said:
i mean it is really annoying that he doesn't link to original topic from doixanh (damn why not an easy forum name?)
just put a link here to original topic and remove download link so users here will be sure they download the last version
now dark!
**** you colombians and export your best coffee to us NOW! coz i really want an colombian coffee right now
Click to expand...
Click to collapse
Lol you won't have it , maybe if you come here, I will let you try something , but I dont care if you come back to holland with a Hearth attack! XD
NICE!
This tweak fixes that annoying lag/unresponsiveness of the touch screen that renders playing games useless or eeven scrolling through apps that you get every few seconds.
The reason I wanted to buy a new phone was due to this annoying bug, and now it has been fixed!
I love my mini pro now! & I love you too for discovering this!
awesome...thanks for the fix now no annoying unresponsive touch screen while playing games
Ur welcome guys!!
Sent from my X10 Mini using XDA Premium App
with this if multi touch is also available it would be more awesome
can i copy paste "insmod /system/lib/modules/x8mddi.ko # fix mddi lags"
or i must type it?
You can copy it, btw, you should thank original creator on X8 forum
I copied it by I still get lag, do i put it on the very first line? and someone where in the middle?
How do you add code tags?
Code:
insmod /system/lib/modules/x8mddi.ko # fix mddi lags
# hw_config.sh
# Hardware configuration file
# Version 2010-09-21, JN
# Values imported from delta: Version 2010-01-25 Mimmi.
# Vibrator configuration
dev=/sys/devices/platform/msm_pmic_vibrator
echo 2400 > $dev/voltage_mv
# lm3530 LMU configuration
dev=/sys/devices/platform/i2c-adapter/i2c-0/0-0036
echo linear > $dev/br::mapping # BL mapping method [linear exp]
echo 32768 > $dev/br::rate::up # BL ramp up rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 32768 > $dev/br::rate::down # BL ramp down rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 226 > $dev/br::limit # BL full scale brightness 255 correponds to above [0 - 255]
echo 22.5 > $dev/br::fsc # Backlight full scale value in mA [5.0, 8.5, 12.0, 15.5, 19.0, 22.5, 26.0, 29.5]
echo 4,80,160,250 > $dev/curve::borders # Light sensor zone boundaries
echo 60,102,144,185,227 > $dev/curve::targets # BL zone targets
echo high-z > $dev/als::r1 # LS resistor, ohm. Allowed values below.
echo high-z > $dev/als::r2 # LS resistor, ohm
# [high-z 13900 9260 5560 2320 1980 1850 1630 1160 1070 1030 957 771 731 712 677]
echo 512 > $dev/als::avg-t # LS average time, ms [32, 63, 128, 256, 512, 1024, 2048, 4096]
echo i2c_pwm_als > $dev/mode # BL control modes [i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als]
# Proximity sensor configuration
dev=/sys/devices/platform/proximity-sensor/semc/proximity-sensor
echo 15 > $dev/led_on_ms # sensor LED on time in ms
echo 35 > $dev/led_off_ms # sensor LED off time in ms
# Flash LED configuration
dev=/sys/devices/platform/msm_pmic_flash_led
echo 80 > $dev/spotlight::current_ma # spotlight current
echo 4700 > $dev/spotlight::boost_mv # spotlight boost voltage
echo 480 > $dev/cmaflash::current_ma # camera flash current
echo 5000 > $dev/cmaflash::boost_mv # camera flash voltage
# Keyboard LED configuration
dev=/sys/devices/platform/msm_pmic_misc_led.0
echo 3 > $dev/als::cut-off # would be active only in ligh zone "0"
echo user_als > $dev/control::mode # user, als, user_als
echo 40 > $dev/max::current_ma # 0, 10, 20 .. 150 mA
[code]
Put the x8mddi available in first post in /system/lib/modules and paste this in your hw_config.sh:
Ray_jai said:
Code:
#fix mddi lags
insmod /system/lib/modules/x8mddi.ko
# hw_config.sh
# Hardware configuration file
# Version 2010-09-21, JN
# Values imported from delta: Version 2010-01-25 Mimmi.
# Vibrator configuration
dev=/sys/devices/platform/msm_pmic_vibrator
echo 2400 > $dev/voltage_mv
# lm3530 LMU configuration
dev=/sys/devices/platform/i2c-adapter/i2c-0/0-0036
echo linear > $dev/br::mapping # BL mapping method [linear exp]
echo 32768 > $dev/br::rate::up # BL ramp up rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 32768 > $dev/br::rate::down # BL ramp down rate, us/step [8, 1024, 2048, 4096, 8192, 16384, 32768, 65538]
echo 226 > $dev/br::limit # BL full scale brightness 255 correponds to above [0 - 255]
echo 22.5 > $dev/br::fsc # Backlight full scale value in mA [5.0, 8.5, 12.0, 15.5, 19.0, 22.5, 26.0, 29.5]
echo 4,80,160,250 > $dev/curve::borders # Light sensor zone boundaries
echo 60,102,144,185,227 > $dev/curve::targets # BL zone targets
echo high-z > $dev/als::r1 # LS resistor, ohm. Allowed values below.
echo high-z > $dev/als::r2 # LS resistor, ohm
# [high-z 13900 9260 5560 2320 1980 1850 1630 1160 1070 1030 957 771 731 712 677]
echo 512 > $dev/als::avg-t # LS average time, ms [32, 63, 128, 256, 512, 1024, 2048, 4096]
echo i2c_pwm_als > $dev/mode # BL control modes [i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als]
# Proximity sensor configuration
dev=/sys/devices/platform/proximity-sensor/semc/proximity-sensor
echo 15 > $dev/led_on_ms # sensor LED on time in ms
echo 35 > $dev/led_off_ms # sensor LED off time in ms
# Flash LED configuration
dev=/sys/devices/platform/msm_pmic_flash_led
echo 80 > $dev/spotlight::current_ma # spotlight current
echo 4700 > $dev/spotlight::boost_mv # spotlight boost voltage
echo 480 > $dev/cmaflash::current_ma # camera flash current
echo 5000 > $dev/cmaflash::boost_mv # camera flash voltage
# Keyboard LED configuration
dev=/sys/devices/platform/msm_pmic_misc_led.0
echo 3 > $dev/als::cut-off # would be active only in ligh zone "0"
echo user_als > $dev/control::mode # user, als, user_als
echo 40 > $dev/max::current_ma # 0, 10, 20 .. 150 mA
[code][/QUOTE]
_________________
[SIZE=1][B]If you like my post, click the [IMG]http://media.xda-developers.com/images/thanks.jpg[/IMG] button!! :) [/SIZE][/B]
Click to expand...
Click to collapse
Some things still lag for me.
is this considered a custom rom?
http://forum.xda-developers.com/showthread.php?t=895370
That's what I'm using right now.
Ray_jai said:
Some things still lag for me.
is this considered a custom rom?
http://forum.xda-developers.com/showthread.php?t=895370
That's what I'm using right now.
Click to expand...
Click to collapse
Custom roms = Froyo and gingerbread, but that's kinda a custom rom, but 2.1 have not MDDI lag issues.. so if you have lag, its because 2.1 is SLOW
Oh, thanks for clearing that up.
D4rKn3sSyS said:
Custom roms = Froyo and gingerbread, but that's kinda a custom rom, but 2.1 have not MDDI lag issues.. so if you have lag, its because 2.1 is SLOW
Click to expand...
Click to collapse
2.1 has MDDI issues, playing games like fruit ninjam ninjump was hell, the touch screen didn't respond most of the times(atleast in my case there so many others who have similiar issue) even scrolling in some apps was not that responsive, this this module fixes this
Sent from my U20i
Welcome to the most customizable N7 kernel on xda
Bricked-Kernel Nexus 7 (grouper)
Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision
Features:
Based upon Googles tegra3 source
Fixed section mismatches
Various other fixes (look @ github)
Compiled with gcc4.7.2 toolchain (linaro 09.12)
Replaced NVIDIAs hotplug manager with tegra_mpdecision (better battery life + performance)
Extensive sysfs interface for mpdecision with all the tuneables you want
Highly modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
Fixed usage of 51Mhz clock
GPU OC (416/484/520Mhz)
Truly variant free CPU OC for all devices (51 - 1600Mhz)
Fixed max cpufreq resets throughout the kernel
All cores now use the max frequency (before: only in singlecore, otherwise -100Mhz)
Undervolting (faux123)
Default clocks: 102min & 1300max (+100Mhz overclocked) & 475 Maxscroff
earlysuspend/lateresume for ondemand including special screen off settings to save power
Aroma Installer by amarullz
cmdline interface for cpu min/max/maxscroff/gpuoc/scheduler/governor
---Just flash the kernel with your desired settings, no more need for oc apps. Reflash if you want to change sth. It's that easy!
FSync Control by Ezekeel
export t3 variant to debugfs by faux123 (adb shell cat /sys/kernel/debug/t3_variant)
lowered panel min brightness to 8
ZRAM
enabled NFSv3&4
Check the compare links for the rest
Where is tha Changelog???
There will be no more changelogs.
Instead the download pages were outfitted with compare links to github for each download.
How to install?
Flash through recovery. #done.
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
[email protected]
IRC Chat: Freenode IRC #bricked
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
Donor List:
> Hall of fame <
With special thanks to all N7 piggy bank donors!
Thank you very much!
Source:
Benchmark:
Knowledge base:
What is tegra_mpdecision?
100% kernel based multi core decision! (should cpu1/2/3 be online or not, do we need the low-power/ninja core now?)
This replaces the stock nvidia hotplug solution.
Check /sys/kernel/tegra_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (130)
pause = if something else plugs in the cpu, fall asleep for 10000ms (10 secs)
scroff_single_core = Force low-power mode if screen is off (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (475000)
lpcpu_up_hsyteresis = minimum number of requests that have to be send in order to switch to low-power mode (4)
lpcpu_down_hsyteresis = minimum number of requests that have to be send in order to switch to g-mode (quadcore-mode). Overridden by a requested freq that is higher than the max supported lp-mode frequency. (2)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
This will regulate when we switch to lp-mode, effectively replacing the quadcore g-mode core with the ninja lp-mode core.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
(all times are in ms)
If you want to see the mpdecision magic happening:
Code:
adb shell
cat /proc/kmsg | grep 'MPDEC'
mpdecision's input event boost, aka project butter
This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
In those events the min cpu freq will be risen to a predefined value (look below) on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)
Configuration files:
[email protected]:/sys/kernel/tegra_mpdecision/conf # ls
boost_enabled
boost_freqs
boost_time
All of them work like the usual sysfs files, except one special case:
boost_freqs will list all frequencies from cpu 0 to cpu x. Cpu 3 and any following cpu will share one frequency.
To change those frequencies echo the cpu number + the frequency in khz. To change the boost freq of cpu3 (and 4,5,6,7,8, etc) the echo would look as follows:
Code:
echo "3 1026000" > /sys/kernel/tegra_mpdecision/conf/boost_freqs
for cpu0:
Code:
echo "0 1026000" > /sys/kernel/tegra_mpdecision/conf/boost_freqs
Defaults:
Code:
cat /sys/kernel/tegra_mpdecision/conf/boost_freqs
910000
910000
760000
620000
Recommended governor?
Ondemand.Why do I have no WLAN?
This kernel is too big for our boot.img with WLAN included into the kernel, so it is built as a module. That means it needs to be inserted into the kernel upon boot up, which needs to be automated for maximum comfort = userinit (init.d) support.
The zip adds init.d support to your ramdisk, if that fails for some reason the wlan module cannot be inserted.
if
Code:
adb shell lsmod
doesn't show this:
Code:
tun 14060 0 - Live 0x00000000
cifs 239646 0 - Live 0x00000000
bcmdhd 433083 0 - Live 0x00000000
Then init.d support is probably missing.
You can test it by going to /system/etc/init.d/ and executing 00wlan.
Code:
adb shell
su
. /system/etc/init.d/00wlan
Wait a few seconds and try to enable wifi and repeat the above lsmod command (should now show bcmdhd as live, you can execute 01cifs and 02tun too).
If WLAN now works, init.d support is missing.
You need to have busybox installed in order to be able to get init.d support going, this shouldn't be a problem for most people, since it is usually installed when rooting your phone anyway (and who does unlock but not root their phone? :/)
It does not matter if busybox is installed in /system/bin or /system/xbin, my script will detect the location upon flashing and patch the ramdisk accordingly.
If no busybox is found, the script will add init.d support to your ramdisk with the default location: /system/xbin/busybox. All you need to do is install busybox there and reboot your phone.
show-p1984 said:
Knowledge base:
(under construction)
tegra_mpdecision manual:
coming soon(tm)
Click to expand...
Click to collapse
looks great is this kernal compatible with cm10 based roms such as paranoid android
Flypants101010 said:
looks great is this kernal compatible with cm10 based roms such as paranoid android
Click to expand...
Click to collapse
Yes, ofc
Running cm10 nightlies myself.
show-p1984 said:
Yes, ofc
Running cm10 nightlies myself.
Click to expand...
Click to collapse
All AOSP roms work with Bricked
* Hello World *
What tweaks did you make to on-demand, if you don't mind me asking? The only thing I've noticed is that frequency switching seems to happen faster & more often.
Feel like flashing something tonight!
Sent from my Nexus 7 using xda premium
I tried flashing this a few times and it fails with each try.
Dabaum said:
What tweaks did you make to on-demand, if you don't mind me asking? The only thing I've noticed is that frequency switching seems to happen faster & more often.
Click to expand...
Click to collapse
I mostly adapted it to work with the lpcore while the screen is on and also with special power saving setting while the screen is off.
The 2 phase frequency was changed to accomplish that.
It also applies a powersave bias while screen is off.
Additionally I changed the settings to allow faster scaling with less load. (70% > freq incr)
Source is currently being uploaded, but since I kept the history intact it is taking ages. You can look it up there in more detail once the source is up
airmaxx23 said:
I tried flashing this a few times and it fails with each try.
Click to expand...
Click to collapse
With what message?
I guess because your recovery does not identify your device as 'grouper'.
show-p1984 said:
With what message?
I guess because your recovery does not identify your device as 'grouper'.
Click to expand...
Click to collapse
It just says failed, I've had no problems flashing anything else and I'm flashing mutilple times a day usually.
airmaxx23 said:
It just says failed, I've had no problems flashing anything else and I'm flashing mutilple times a day usually.
Click to expand...
Click to collapse
It most certainly does not say "failed" and nothing else. Look harder.
Using twrp recovery me and my beta testee had no problems at all.
show-p1984 said:
It most certainly does not say "failed" and nothing else. Look harder.
Using twrp recovery me and my beta testee had no problems at all.
Click to expand...
Click to collapse
It says "unable to open zip file. Error flashing zip."
show-p1984 said:
Yes, ofc
Running cm10 nightlies myself.
Click to expand...
Click to collapse
And just to be clear, with non-CM based ones as well? I'm running the 'Glazed' ROM....
airmaxx23 said:
It just says failed, I've had no problems flashing anything else and I'm flashing mutilple times a day usually.
Click to expand...
Click to collapse
Nothing wrong with the zipfile, maybe corrupted download? did you do md5 hash check before flash?
It's either your custom recovery or a corrupted download, period.
ps. Happy Flashing.
airmaxx23 said:
It says "unable to open zip file. Error flashing zip."
Click to expand...
Click to collapse
corrupt download? checked md5/sha1?
corrupt phone upload? checked md5/sha1?
friedsonjm said:
And just to be clear, with non-CM based ones as well? I'm running the 'Glazed' ROM....
Click to expand...
Click to collapse
As long as it is AOSP you should be fine.
But just try it and report back, then we are all a bit more enlightened
(Sorry, I can't possibly test all the ROMs out there ^^)
T-junk said:
Nothing wrong with the zipfile, maybe corrupted download? did you do md5 hash check before flash?
It's either your custom recovery or a corrupted download, period.
ps. Happy Flashing.
Click to expand...
Click to collapse
If I try downloading it directly to my tablet the resulting file is only 17.51K in size, downloading it with a computer takes care of the problem.
airmaxx23 said:
It says "unable to open zip file. Error flashing zip."
Click to expand...
Click to collapse
I get the same.
Sent from my Nexus 7 using xda premium
airmaxx23 said:
If I try downloading it directly to my tablet the resulting file is only 17.51K in size, downloading it with a computer takes care of the problem.
Click to expand...
Click to collapse
StrangerWeather said:
I get the same.
Click to expand...
Click to collapse
I guess same problem for you StangerWeather.
Try downloading on your pc, I will look into that webserver issue tomorrow. (or maybe it's a chrome issue? who knows ^^)
Welcome to the most customizable N4 kernel on xda
Bricked-Kernel Nexus 4 (mako)
Features:
* Based upon Googles msm 3.4 source
* Various other fixes (look @ github)
* Compiled with gcc4.7.2 toolchain (linaro 09.12)
* -O3 optimized
* Snapdragon S4 & CortexA15 optimizations
* Sweep2wake
(Disabled as default, activate through an app like KControl or over sysfs: echo 1 > /sys/android_touch/sweep2wake)
* DoubleTap2Wake
(Disabled as default, activate through an app like KControl or over sysfs: echo 1 > /sys/android_touch/doubletap2wake)
* replaced qcoms hotplug binary with msm_mpdecision (IN-KERNEL, better battery life + performance)
* Extensive sysfs interface for mpdecision with all the tuneables you want (/sys/kernel/msm_mpdecision/)
* replaced the thermald binary with my IN-KERNEL solution. (/sys/kernel/msm_thermal/)
* export krait version to: /sys/kernel/debug/krait_variant
* modified ondemand governor
* Allow OC up to 1,83Ghz, faux123 (from a thermal point of view that is now SAFE)
* Allow UC down to 94,5Mhz
* Fixed min cpufreq resets
* Undervolting (faux123)
* Default clocks: 384min & 1512max
Zip features:
* ramdisk module insertion
* removes governor overrides from the ramdisk
* adds init.d support to your ramdisk (if not already supported)
Check the compare links for the rest
Where is tha Changelog???
There will be no more changelogs.
Instead the download pages were outfitted with compare links to github for each download.
What is sweep2wake?
How to install?
Flash through recovery. #done.
How to uninstall?
Flash this through recovery:
Bricked_uninstaller
Bye.
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://github.com/showp1984/bricked-mako/issues
[email protected]
IRC Chat: Freenode IRC #bricked
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
Donor List:
> Hall of fame <
Thank you very much!
Stock Nexus4 JELLYBEAN JWR boot.img (flash this if you come from another kernel)
Source:
What is msm_thermal?
Kernel based 3-phase thermal control!
This replaces your /system/bin/thermald binary which is renamed by the installer to thermald_bck.
It will throttle your cpu speed to keep it cool and unleash it if the cpu has cooled down enough. (3 phases: low, mid and high)
Check /sys/kernel/msm_thermal/conf/ for the thermal configuration
allowed_max_high = highest threshold (phase 3)
allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
allowed_max_freq = max frequency if throttled (limit)
[...]mid[...] = same as above, just for phase 2
[...]low[...] = Lowest threshold (phase 1)
check_interval_ms = how often shall we check? (sampling rate)
Default: 100ms (=0.1sec)
shutdown_temp = if we reach this shut down the device!
Default: 80°C
If you want to see msm_thermal doing it's job:
Code:
adb shell
cat /proc/kmsg | grep 'thermal'
What is msm_mpdecision?
100% kernel based multi core decision! (should cpu1/2/3 be online or not?)
This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_bck.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (70)
pause = if something else plugs in the cpu, fall asleep for 10000ms (10 secs)
scroff_single_core = if the screen is off, don't plug in cpu1/2/3. Additionally: Unplug all cpus except cpu0 when screen is turned off (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (486000)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
Since we can't unplug cpu0 this is '0'.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
The default values are:
NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
Where the position and function of the number equals the result of the above explained formula.
(all times are in ms)
If you want to see the mpdecision magic happening:
Code:
adb shell
cat /proc/kmsg | grep 'MPDEC'
mpdecision's input event boost, aka project butter
This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
In those events the min cpu freq will be risen to a predefined value (look below) on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)
Configuration files:
[email protected]:/sys/kernel/msm_mpdecision/conf # ls
boost_enabled
boost_freqs
boost_time
All of them work like the usual sysfs files, except one special case:
boost_freqs will list all frequencies from cpu 0 to cpu x. Cpu 3 and any following cpu will share one frequency.
To change those frequencies echo the cpu number + the frequency in khz. To change the boost freq of cpu3 (and 4,5,6,7,8, etc) the echo would look as follows:
Code:
echo "3 1026000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
for cpu0:
Code:
echo "0 1026000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
Defaults:
Code:
cat /sys/kernel/msm_mpdecision/conf/boost_freqs
918000
918000
702000
594000
How does sweep2wake work? Does it keep my phone awake?
Short answer: No.
Long answer:
Sweep2wake works with IRQs (Interrupts).
An interrupt can be best imagined as you doing something, like shopping at the local super market, when someone jumps in front of you and punches you into your family jewels. You will most certainly not just continue shopping.
In technical terms: An Interrupt interrupts the normal operation of a program and executes "special" code instead.
So if you touch your screen, an interrupt is send on which the touch driver reacts. That's it.
Since we have a capacitive touchscreen you also do not need to worry about any pressure onto the screen.
If you want to disable sweep2wake execute this command on your phone (adb shell or directly), you can also add it to an init.d script.
Code:
echo "0" > /sys/android_touch/sweep2wake
(echoing "1" activates it, which is the default setting)Recommended governor?
Ondemand.Why do I have no WLAN?
Due to this kernels very high optimization settings it is too big for our boot.img with WLAN included into the kernel, so it is built as a module. That means it needs to be inserted into the kernel upon boot up, which needs to be automated for maximum comfort.
The zip adds this to your ramdisk, if that fails for some reason the wlan module cannot be inserted.
if
Code:
adb shell lsmod
doesn't show this:
Code:
tun 14701 0 - Live 0x00000000
cifs 275399 0 - Live 0x00000000
wlan 2964650 0 - Live 0x00000000 (C)
Then something went wrong. (My fault)
You can test it by executing
Code:
adb shell
su
insmod /system/lib/modules/wlan.ko
Wait a few seconds and try to enable wifi and repeat the above lsmod command (should now show wlan).
If WLAN now works, I messed up.
Open a new issue in the issue tracker and it will be fixed asap.Last release for 4.2.2?
STABLE: 20130622_233007_master-8fa9be1
BETA: 20130727_023549_exp-d64cabc
If you look for an app to control your kernel: http://forum.xda-developers.com/showthread.php?p=47773391#post47773391
it is finally here!!!
i spy sweep2wake
So over clock is safe with this???
Sent from my Nexus 4 using XDA Premium HD app
Looking forward to trying this out! Looks awesome. Just out of curiosity is there any reason why this zip is so much larger than the zips for other kernels?
I can't wait to get bricked!
alewis2k12 said:
So over clock is safe with this???
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
OP is your friend
Sent from my Nexus 4 using xda premium
---------- Post added at 08:38 PM ---------- Previous post was at 08:38 PM ----------
Locksmith81 said:
OP is your friend
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It's a yes
Sent from my Nexus 4 using xda premium
Flashed it and will report soon
Do it need to wipe cache ??
jarjar124 said:
it is finally here!!!
i spy sweep2wake
Click to expand...
Click to collapse
Soon(tm)
I am currently making final adjustments to sweep2wake
Perhaps it will be a christmas present?
alewis2k12 said:
So over clock is safe with this???
Click to expand...
Click to collapse
From a thermal point of view: Yes.
But if you set a too high clock and your chip craps out because of too much voltage, that won't save it.
Overclocking is dangerous. It will never be safe, the thermal guard just makes it as safe as on any other phone.
cmikeh2 said:
Looking forward to trying this out! Looks awesome. Just out of curiosity is there any reason why this zip is so much larger than the zips for other kernels?
Click to expand...
Click to collapse
Yes, because of sooooo many optimizations I pumped into the kernel it was getting pretty big, too big for it to fit inside the boot.img with the ramdisk. SO I had to remove stuff from the kernel and put it into modules (wlan,cifs,tun) which are inserted into the kernel upon boot.
You won't feel the difference but it enabled me to include these optimizations.
(the prima wlan module is 22megs or so... freaky big thing.)
mpttrung said:
Flashed it and will report soon
Do it need to wipe cache ??
Click to expand...
Click to collapse
It wipes cache for you.
show-p1984 said:
Soon(tm)
It wipes cache for you.
Click to expand...
Click to collapse
Opps ! It stucks at Google logo @@
I am using stock, any idea ??
mpttrung said:
Opps ! It stucks at Google logo @@
I am using stock, any idea ??
Click to expand...
Click to collapse
I am too on stock, works for me though.
Gimme last_kmsg after you got it into recovery.
show-p1984 said:
I am too on stock, works for me though.
Gimme last_kmsg after you got it into recovery.
Click to expand...
Click to collapse
Red : what do u mean ??
mpttrung said:
Opps ! It stucks at Google logo @@
I am using stock, any idea ??
Click to expand...
Click to collapse
Were you on Franco's kernel?
harpo1 said:
Were you on Franco's kernel?
Click to expand...
Click to collapse
Yeah ! U got stucked too ???
Anybody got a safe OC limit?? And thanks for the help....and coming from Franco as well
Sent from my Nexus 4 using XDA Premium HD app
alewis2k12 said:
Anybody got a safe OC limit?? And thanks for the help....and coming from Franco as well
Click to expand...
Click to collapse
1.7 should be safe, apq8064 is built with that max freq in mind.
Though to be clear: THERE IS NO SAFE OC FREQ. OC IS ALWAYS DANGEROUS!
To all those who have problems, I will provide a stock boot.img in the first post. (gimme a few seconds)
Stock Nexus4 boot.img (flash this if you come from another kernel)
mpttrung said:
Yeah ! U got stucked too ???
Click to expand...
Click to collapse
Yeah if you're kernel hopping make sure you reset back to stock. :good:
UZ7 said:
Yeah if you're kernel hopping make sure you reset back to stock. :good:
Click to expand...
Click to collapse
Flash to stock using fastboot ?
you could also reflash your rom
Hello folks! how are you doing?
Since we've seen Alpha kernel is still an alpha and we need to provide developers with every detail of our device we can.
I've decided to search through threads and get some commands from there to gather the information required:
You can gather these data by downloading Terminal Emulator from the market or by properly installing Google SDK and doing an adb shell then running the commands.
If commands do not seem to work at first glance, please reboot the phone then try again running the commands below.
Edit 1:
For all the people having problems not mentioned on the bug list, please report the problems in this spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0AkQTVc3TvAUxdFNBOWFFRzNneWRHcW56MEtLVGJqdVE#gid=0
There are several sheets to fill with the mentioned problems
Edit 2:
For all users who might have problem gathering Tegra Revision, Speedo ID, CPU Process, Core Process; please install leaked rom / AtrICS, reboot and try searching again.
Else; please send me the dmesg command output via PM and I'll upload the results.
Please note that I'll discard dmesg from kernels that are not the leaked and/or 3.1
---
Identify Memory type:
Grab a terminal then run after a reboot
Code:
su -
dmesg | grep LPDDR2
Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0001 (0x0101)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 40nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0006 (0x0606) = Hynix (Manufacuter)
LPDDR2 MR6: 0x0000 (0x0000)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 54nm (Note that this is still 54nm for MR7 = 0x0001 (0x0101))
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
---
Identify which Panel Type do we have:
After a fresh reboot
Grab a terminal
Code:
su -
dmesg | grep atag
or
Code:
su -
dmesg | grep panel
Examples:
Code:
dmesg | grep atag
mot_parse_atag_motorola: panel type: 0x80000740
or
Code:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
---
Identify Tegra Revision:
Code:
su -
dmesg | grep Tegra
then search for something similar to
Code:
"Tegra Revision: AXX prime"
---
Well, let's see if we can help Atrix Kernel Team to improve the kernel with this useful information
Also, if anybody would like to contribute showing how to gather more data; that'd be awesome and I'll edit this post
Thanks guys, have a good day!
You are the man!!!....good work my friend...:good:
Thanks for this.
Thanks
This is super helpful. Now if I can just get my post count up high enough to post to dev forums....
Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
Identify which Panel Type do we have:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
However, using command: "dmesg | grep Tegra" doesnt give me anything close to any revision information.
Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.
ravilov said:
Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.
Click to expand...
Click to collapse
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
I tried dmesg | grep revision
and got this:
CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c53c7d.
vintage47 said:
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
Click to expand...
Click to collapse
No idea, but you can use grep -i Tegra, that should make capitalization irrelevant.
Solved, I was looking on dmesg from old kernel
--------------------------------------------------------------------------------------------------------------------------
Hello,
how I find the Tegra Revision, Speedo ID, CPU Process, Core Process that request Kristianp in my dmesg? I am stupid or it show diferent?
best regards,
Ferenc.
I cant find the tegra revision either. I can see the first thing in the log, but not the tegra revision.
Do after a fresh reboot in leaked kernel and Rom ( 10.1 epinter is mine)
Reboot when SD Card is present
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier
ingelectronico said:
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier
Click to expand...
Click to collapse
PM'ed you regarding the missing info
Also, users who might have spreadsheet access problem, please let me know via PM.
new fields
I want to add my info on the modem drops spreadsheet.
How do I find what values my phone has for these fields?
Speedo ID
CPU Process
Core Process
CPU governor
Connect the phone to usb and activate adb. Reboot. As soon as finished reboot, use adb shell and type dmesg > /mnt/sdcard/dmesg.txt
Now search that file.
This has been answered many tines before.
Next time use search
Enviado desde mi MB860 usando Tapatalk 2
Welcome to the most customizable N7 2013 kernel on xda
Bricked-Kernel Nexus 7 2013 (flo/deb)
Features:
* Based upon Googles msm 3.4 source
* Various other fixes (look @ github)
* Compiled with gcc4.7.2 toolchain (linaro 09.12)
* -O3 optimized
* Snapdragon S4 & CortexA15 optimizations
* vastly improved touchscreen drivers, which made it rock stable even before Google patched the firmware
* Sweep2wake
* DoubleTap2Wake
* replaced qcoms hotplug binary with msm_mpdecision (IN-KERNEL, better battery life + performance)
* Extensive sysfs interface for mpdecision with all the tuneables you want (/sys/kernel/msm_mpdecision/)
* replaced the thermald binary with my IN-KERNEL solution. (/sys/kernel/msm_thermal/)
* export krait version to: /sys/kernel/debug/krait_variant
* modified ondemand governor
* Allow OC up to 1,83Ghz
* Fixed min cpufreq resets
* Undervolting
* Sound Control (faux123)
* Default clocks: 384min & 1512max
Zip features:
*** ON-THE-FLY-RAMDISK EDITS!
*** THIS KERNEL USES YOUR RAMDISK, it will just modify it on the fly while flashing. These changes are not creating any incompatibilities with roms/other kernels. (Except those roms which intentionally go incompatible to stock/aosp on a driver level)
* removes min freq overrides from the ramdisk
* removes governor overrides from the ramdisk
* adds init.d support to your ramdisk (if not already supported)
* modifies stock ondemand settings
* add module insertion
Check the compare links for the rest
Where is tha Changelog???
There will be no more changelogs.
Instead the download pages were outfitted with compare links to github for each download.
What is sweep2wake?
Yes that is a mako, works the same way on the flo though
How to install?
Flash through recovery. #done.
How to uninstall?
Flash this through recovery:
Bricked_uninstaller
Bye.
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://github.com/showp1984/bricked-flo/issues
[email protected]
IRC Chat: Freenode IRC #bricked
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
Donor List:
> Hall of fame <
Thank you very much!
Source:
What is msm_thermal?
Kernel based 3-phase thermal control!
This replaces your /system/bin/thermald binary which is renamed by the installer to thermald_bck.
It will throttle your cpu speed to keep it cool and unleash it if the cpu has cooled down enough. (3 phases: low, mid and high)
Check /sys/kernel/msm_thermal/conf/ for the thermal configuration
allowed_max_high = highest threshold (phase 3)
allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
allowed_max_freq = max frequency if throttled (limit)
[...]mid[...] = same as above, just for phase 2
[...]low[...] = Lowest threshold (phase 1)
check_interval_ms = how often shall we check? (sampling rate)
Default: 100ms (=0.1sec)
shutdown_temp = if we reach this shut down the device!
Default: 80°C
If you want to see msm_thermal doing it's job:
Code:
adb shell
cat /proc/kmsg | grep 'thermal'
What is msm_mpdecision?
100% kernel based multi core decision! (should cpu1/2/3 be online or not?)
This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_bck.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (70)
pause = if something else plugs in the cpu, fall asleep for 10000ms (10 secs)
scroff_single_core = if the screen is off, don't plug in cpu1/2/3. Additionally: Unplug all cpus except cpu0 when screen is turned off (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (486000)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
Since we can't unplug cpu0 this is '0'.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
The default values are:
NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
Where the position and function of the number equals the result of the above explained formula.
(all times are in ms)
If you want to see the mpdecision magic happening:
Code:
adb shell
cat /proc/kmsg | grep 'MPDEC'
mpdecision's input event boost, aka project butter
This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
In those events the min cpu freq will be risen to a predefined value (look below) on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)
Configuration files:
[email protected]:/sys/kernel/msm_mpdecision/conf # ls
boost_enabled
boost_freqs
boost_time
All of them work like the usual sysfs files, except one special case:
boost_freqs will list all frequencies from cpu 0 to cpu x. Cpu 3 and any following cpu will share one frequency.
To change those frequencies echo the cpu number + the frequency in khz. To change the boost freq of cpu3 (and 4,5,6,7,8, etc) the echo would look as follows:
Code:
echo "3 1026000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
for cpu0:
Code:
echo "0 1026000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
Defaults:
Code:
cat /sys/kernel/msm_mpdecision/conf/boost_freqs
918000
918000
702000
594000
How does sweep2wake work? Does it keep my phone awake?
Short answer: No.
Long answer:
Sweep2wake works with IRQs (Interrupts).
An interrupt can be best imagined as you doing something, like shopping at the local super market, when someone jumps in front of you and punches you into your family jewels. You will most certainly not just continue shopping.
In technical terms: An Interrupt interrupts the normal operation of a program and executes "special" code instead.
So if you touch your screen, an interrupt is send on which the touch driver reacts. That's it.
Since we have a capacitive touchscreen you also do not need to worry about any pressure onto the screen.
If you want to disable sweep2wake execute this command on your phone (adb shell or directly), you can also add it to an init.d script.
Code:
echo "0" > /sys/android_touch/sweep2wake
(echoing "1" activates it, which is the default setting)Recommended governor?
Ondemand.Why do I have no WLAN?
Due to this kernels very high optimization settings it is too big for our boot.img with WLAN included into the kernel, so it is built as a module. That means it needs to be inserted into the kernel upon boot up, which needs to be automated for maximum comfort.
The zip adds this to your ramdisk, if that fails for some reason the wlan module cannot be inserted.
if
Code:
adb shell lsmod
doesn't show this:
Code:
tun 14701 0 - Live 0x00000000
cifs 275399 0 - Live 0x00000000
wlan 2964650 0 - Live 0x00000000 (C)
Then something went wrong. (My fault)
You can test it by executing
Code:
adb shell
su
insmod /system/lib/modules/wlan.ko
Wait a few seconds and try to enable wifi and repeat the above lsmod command (should now show wlan).
If WLAN now works, I messed up.
Open a new issue in the issue tracker and it will be fixed asap.
If you look for an app to control your kernel: http://forum.xda-developers.com/showthread.php?p=47773391#post47773391
Wohoooooo the best kernel on sensation thread now reaches nexus 7!!! That's awesome :highfive:
Sent from my Nexus 7 using xda app-developers app
Drunken_elk said:
Wohoooooo the best kernel on sensation thread now reaches nexus 7!!! That's awesome :highfive:
Click to expand...
Click to collapse
It's been on the flo since September the 19th, there just wasn't an xda thread for it
Oh damn . Anyway good choice to add the thread
Sent from my Nexus 7 using xda app-developers app
no fsynch trigger? or just not mentioned in features?
L-ViZ said:
no fsynch trigger? or just not mentioned in features?
Click to expand...
Click to collapse
Whoever disables fsync is a maniac. It is not in this kernel and will never get in. That's my totally honest opinion.
Using a no fsync, or 'dynamic' fsync kernel is the equivalent of jumping from a skyscraper with nothing but a napkin.
Best Nexus 5 kernel il now on N7 ! Awesome ! Thank's for this
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Assume this is based on the new 4.4.1?
Sent from my Nexus 4 using Tapatalk
ogrillion said:
Assume this is based on the new 4.4.1?
Click to expand...
Click to collapse
Indeed.
Hey man, good to see more talented kernel devs on this device, yours was one of my favourites back on my HTC One X
Any chance of merging kexec patch for multirom support?
http://forum.xda-developers.com/showthread.php?t=2457079
Nexus 7 LTE
Stock rooted KOT49E
Faux Kernel
show-p1984 said:
Indeed.
Click to expand...
Click to collapse
Oh god ! Downloading now !
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Can you include the MultiROM patch in the kernel?
Sent from Tapatalk, using Tapatalk
show-p1984 said:
Indeed.
Click to expand...
Click to collapse
made for 4.4.1 means only usable on 4.4.1 or works on 4.4 too?
Will this brick my phone
Does Slimport work with this? I have had other kernels flick out after 5 minutes or so.
Sent from my Omni 4.4 Galaxy S3. Proud Googy Beta tester.
Works with CM11?
L-ViZ said:
made for 4.4.1 means only usable on 4.4.1 or works on 4.4 too?
Click to expand...
Click to collapse
I can tell you that I am running it on Bruce's 4.4 odexed and is running brilliantly so far. Installed it early this morning and running great so far.
Quiksilver78 said:
Works with CM11?
Click to expand...
Click to collapse
It should.
Give it a try, the install process make a backup of your current Zimage, if something goes wrong, just flash the uninstaller and your'll get back to your unmodified rom.
lionelia said:
It should.
Give it a try, the install process make a backup of your current Zimage, if something goes wrong, just flash the uninstaller and your'll get back to your unmodified rom.
Click to expand...
Click to collapse
Turning on WiFi caused boot loops for me lol
I figured it wasn't supposed to work so I didn't report it so I flashed slimkat