Check out the review by Blair at GizmoNinja! Droid X ROM Review, rubiX ROMs! Updated 12/26/2010 NEW rubiX ROM 1.9.5 Release!!
YOU MUST BE ON 2.3.340 OTA FOR THIS TO WORK
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
IF YOU USED THE NEW SCRIPT, YOU MUST REBOOT AFTER INSTALL AND INITIAL SETUP
This script runs on first boot to scan the SDCard rubiX Folder for apps. If they are there, it copies them to /data/app and corrects their permissions. Reboot for this to take effect.
YOU MUST wipe data before install.
Change Log for 2.0:
* Sysctl.conf adjustments:
Changed vm.dirty_background_ratio to 70 from 60
* Added rm /dev/log/main for extra performance/free memory
* Changed NO_NEW_FAIR_SLEEPERS to NO_FAIR_SLEEPERS; this was a typo, as there are no new fair sleepers in the dx kernel already.
* Cleaned up the /system/app folder
The following market apps were further removed:
Talkback
Kickback
Soundback
* Added new Interactive and Conservative kernel scaling governors (credit Milestone team)
This is a Droid X first. These two governors bring a big difference to the table; here is what they do:
(Credit Cyanogenmod GITHub for this, source is here: https://github.com/CyanogenMod/cm-k...60f39120/Documentation/cpu-freq/governors.txt)
Interactive:
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Conservative:
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered environment.
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
Basically, this means more speed and battery life control
* Adjusted 01cpu for a better sampling rate if the new conservative governor is found.
* Added script: gov
gov allows you to control which governor you use; ondemand, conservative, or interactive. The function is:
gov -ondem for the ondemand governor
gov -cons for the conservative governor
gov -inter for the interactive governor
Alternately, these can be changed via SetCPU or Droid Overclock.
To remove data throttling, click this:
http://www.droidforums.net/forum/dr...-9-7-back-better-than-ever-3.html#post1228193
Credit to Plower.Net
How to install:
Download
Place on SDCard
Bootstrap Recovery via Bootstrap App
Reboot to Clockwork Mod Recovery
Wipe data/factory reset
Select install from sdcard
Choose zip from sdcard
select rubiXFocused2.0.zip
Select yes
Reboot
Enjoy!
Download:
http://www.mediafire.com/?6s32joduwkwyhwa
Will have a mirror up shortly as well.
If you like my work, please support me going to Google I/O Developer's Conference 2011! All donations received are going towards a plane ticket.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TYYWQBR78DW7U
reserved for me
drod2169 said:
reserved for me
Click to expand...
Click to collapse
what this says ^^^^
Hey drod, thanks for the new release! Will def give this a try!
Sent from my DROIDX using XDA App
SysAdmin-X said:
Hey drod, thanks for the new release! Will def give this a try!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Is this fo real Rubix Focus 1.9.7 is it only released on here because i can't find 1.9.7 anywhere else ? .
Hey Drod, Keep Bangin em out.Rubix in General Is StR8 up Sik lookin forward to this one!
about to start installing in 2 min
Got my Approval bruh..Bring on Tron Theme..LOL
d/ling now. Can't wait to try it. Thank you for bring the art of the DX forward a notch or two!
drod2169 said:
reserved for me
Click to expand...
Click to collapse
jawonder said:
Is this fo real Rubix Focus 1.9.7 is it only released on here because i can't find 1.9.7 anywhere else ? .
Click to expand...
Click to collapse
Yes it's really rubiX Focused 1.9.7
will the themes for 1.95 work on this rom (black jiuce)?
Will this work for the droid 2 ? Since the
Old rubix was said to be working for the droid 2..
Just wanted to say the clock-speed/voltage optimization app is amazing. I get better battery life on RubiX than on any other ROM (and I have tried them all).
This is faster than liberty was for me. Glad I came back to RubiX.
Is there a zip to remove animation and put it back to stock. This is rom is so fast that I hit the quadrant score of 1500 without overclocking. Thxs for a great rom. I tried them all.
Sent from my DROIDX using XDA App
I am going to install this rom tonight. I currently have liberty installed and am happy with it and not having any trouble but unless I try other ones I won't know if I like any others better. I would like to see better battery life and it sounds like I might see it with this rom.
drod2169 said:
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
Click to expand...
Click to collapse
I was able to permanently get rid of the TranQ Toolbox without SBF. Basically, you just need Root Explorer (or equivalent) to remove all the TranQ files from /data, /data/data, /data/dalvik-cache, /data/preinstall_md5, /preinstall/app, /preinstall/md5, etc. The easiest way is to do a search (at /) in Root Explorer for tranq, and then manually remove them.
Does anybody know how to enable 3 d gallery through terminal emulator. Everytime I try to enable it, it tells me not found. Yes I give it SU permission. It gives me the options either 3d or 2d. I type 3d hit enter, then it tells me not found.
Sent from my DROIDX using XDA App
Never mind I figured it out.
I'm having problems with images showing up as black in any of the galleries or image viewers. Sometimes the thumbnails will display properly, though. In the camera app, if I take a picture and then look at the gallery, thumbnails of images on my sd card will show up, but only one for each picture I took. Pictures taken with the camera never show up. What is going on here and is there a way to fix it? I think rubix is great, otherwise, and would really like to continue using it if the camera and image problems can be fixed.
-------------------------------------
Sent via the XDA Tapatalk App
inokumum said:
I'm having problems with images showing up as black in any of the galleries or image viewers. Sometimes the thumbnails will display properly, though. In the camera app, if I take a picture and then look at the gallery, thumbnails of images on my sd card will show up, but only one for each picture I took. Pictures taken with the camera never show up. What is going on here and is there a way to fix it? I think rubix is great, otherwise, and would really like to continue using it if the camera and image problems can be fixed.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
try swapping to the 3d gallery
type in terminal emulator:
su
gallery -3d
Did anyone by any chance make a flashable zip of the modified services.jar file for this rom for uncapped data? That would be awesome if someone can post it!
Sent from my DROIDX using XDA App
Related
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
In addition, if you are an Incredikernel user, the app may also be used to toggle Incredikernel specific features on and off, namely USB fast charging and audio boost.
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work. Most non-stock gingerbread kernels have the HAVS adjustment. Very few sense kernels have the adjustment. I believe ziggy's latest is the only one that does.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
This excites me.
Neat
Sent from my Synergy Rom using Tapatalk
Great chad! Finally an app that does all the work.
Sent from my ADR6300 using XDA App
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
mikeymop said:
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
Click to expand...
Click to collapse
I concur. And will this work on the incredikernel?
J/k on the the question part (because I know someone will take that seriously ). Great work, chad.
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Great thanks!
I know viperboy was working on something similar.
I have to say though your aggressive undervolt package is the tits. It is rock solid for me, and I can't lower anything -25v from there without crashing.
RebelShadow said:
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Click to expand...
Click to collapse
That may come in the future.
@everyone: Anyone try it on other devices that have havs + sysfs interface? Evo, desire?
effing sweet..... no more term emulator for me
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
POQbum said:
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
Click to expand...
Click to collapse
The boxes are unticked on purpose, so that the file is only written when you specify that you want to set the current settings on boot. The other option is to have it ticked when the boot script is found, but then you would have to untick it when you want to just play with voltages (but not change your boot script) and then tick it again to set on boot. Would everyone prefer it that way?
I should also specify that when you tick set on boot, you also must click set in order to truly set it on boot. There is also the option to have it write the file when set on boot is ticked. I just need to know what everyone's preference is.
SDspeed might be added to a future release and would have the set on boot option.
PonsAsinorem said:
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
Click to expand...
Click to collapse
That's because new nightlies overwrite the /system folder where the boot script is stored. I'll probably add a backup option too so you can load the defaults, either that or change over to storing the values in a database and loading them via the app on boot as opposed to the boot script.
Looks cool.
Backup database - yes!
Default set on boot once it's been ticked - yes!
Thanks for this, Chad!
Zeam & Incredikernel
CM7 latest Nightly
7/19/2011 - Preview 3:
Changes include:
Added +/- All Min and All Max buttons
Reordered the + and – buttons to flank the voltages to clean up the layout a bit.
Removed the title bar for more vertical screen space
Next up is feature checking / disabling of functions your kernel doesn’t support as well as voltage checking.
Get it at http://www.incredikernel.com
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
nagasgura said:
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
Click to expand...
Click to collapse
Thanks, I'll add it for the next release.
The + on the Max voltage doesn't display for me.
Love it, fast and simple volt changing.. Makes viperMOD ancient news.
Introducing the new variant of Bali kernel, Bali for CM7. The main goal of this kernel is the same as other Bali kernel, balanced performance and battery life. I can't guaranteed you will get the same battery life as Bali for Froyo but you will definitely get an improve battery life over stock kernel.
Features:
- OC/UV up to 1.4GHz (Safe boot to 1GHz) [require setCPU from market]
- Voodoo Sound v10
- Voodoo Color
- Multiple CPU governor, smartass included (default: ondemand)
- Multiple IO scheduler (default: BFQ)
- LED notification support (no external app required)
- CIFS support
- Support SetCPU screen off 100/400 profile
- Dock sound redirector support [need Galaxy Dock Sound Redirector app from market]
Disclaimer:
As always, I'm not responsible with any damage cause to your phone.
Special Thanks:
- Team Whiskey - you guys are awesome.
- Alexia - for great work on the new splash image.
- Supercurio - for awesome work on Voodoo
- xcaliburinhand - for wonderful work on dock sound redirector.
- Everybody at CM dev community for their hard work on this awesome ROM.
- Everybody at #teamwhiskey for beta testing this kernel and their support.
I apologize if I miss anyone ..
Flashing Instruction:
- If you're coming from another kernel, flash "Ultimate Kernel Cleaning Script" by lippol94 first (http://www.multiupload.com/XFH1GCK4MB)
- Once that's done .. then flash Bali-CM
If you don't know how to flash then this is not for you.
Download:
Bali-CM_v2.2.2
Change Log:
Code:
- 2.2.2 [10/18/2011]
CM update
Re-enabled LED by default
- 2.2.1 [9/12/2011]
Fixed screen jitter issue
- 2.2 [9/10/2011]
Upgraded BFQ to v2
Added Smartass v2 with extra tweak
Fixed ondemand and tweaked for smoother experience
Set ondemand as default governor
Other fixes and tweaks
- 2.1 [9/1/2011]
Disabled SLQB and revert back to SLUB
Disabled LED notification for the time being
Added more UV settings
GPU tweaks
Added v(r) scheduler
Added Tiny Preempt RCU
And other tweaks and fixes
- 2.0 [8/25/2011]
Disabled ramzswap and switched to zram
Enabled zcache for better IO performance
Memory tweak, now gives you 340MB
More tweaks
- 1.2.1 [8/19/2011]
Fixed video playback issue
Fixed battery report when charging, it goes to 100% now
- 1.2 [8/18/2011]
Updated source with the latest CM patches
Added SLQB slab allocator for better memory management
Added more tweaks
- 1.1.1 [7/26/2011]
Fixed kernel instability that cause random reboot
- 1.1 [7/26/2011]
Added Voodoo color V2
Fixed UV portion to make it easier to manage
Added Voltage Control support
Added compiler tweak
- 1.0 [7/22/2011]
Initial release
A little explanation on different governors (taken from Lord ClockAn thread):
- interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
- smartass - Is an improved version of interactive governor
- ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
- performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
- powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
- userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Q and A:
My screen has green, yellow, or orange tint.
Use Voodoo Control to set color profiles (courtesy of d_phekt)
Screen RGB Multipliers:
Red = 230996000
Green = 230996000
Blue = 2704668800
Screen v1 Gamma Hack:
Red = -50
Green = -53
Blue = -44
is GPS still functional with this kernel?
gamikzone said:
is GPS still functional with this kernel?
Click to expand...
Click to collapse
Yes .. GPS still functional.
drhonk said:
Yes .. GPS still functional.
Click to expand...
Click to collapse
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
gamikzone said:
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
Click to expand...
Click to collapse
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
drhonk said:
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
Click to expand...
Click to collapse
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
gamikzone said:
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
Click to expand...
Click to collapse
Try smartass with this kernel ..
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
i think i will try this out tonight
I believe this will be ok to use with miui.
Nice animation.
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
jay661972 said:
I believe this will be ok to use with miui.
Nice animation.
Click to expand...
Click to collapse
Trying it out , any recommeneded UV settings?
Sent from my T959 using XDA App
jay661972 said:
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
It does work on miui,
Sent from my T959 using XDA App
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
Really, how did you do that? I did the clean script first and flash Bali.
es7241 said:
It does work on miui,
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Okay I will try this one more time.
jay661972 said:
Okay I will try this one more time.
Click to expand...
Click to collapse
confirmed .. it works on MIUI since I just flashed MIUI with it.
jay661972 said:
after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
Same here except im flashing from trigger redux #12 and ive tried flashing from trig w/glitch and w/du jour
Sent from a cell tower to the XDA server to you.
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
drhonk said:
confirmed .. it works on MIUI since I just flashed MIUI with it.
Click to expand...
Click to collapse
jay661972 said:
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
Click to expand...
Click to collapse
So you can't flash bali on miui energy? You have to revert to stock miui?
Sent from my T959 using XDA Premium App
Thread Updated: February 24th, 2012Rom Name: HoliRaider
Developer: bananacakes
Version: 1.6 / 1.6-4G
Last Update: February 23th, 2012
Features:
Based on SKT KR 2.31.911.2 LTE
Rooted
Ultra Smooth Rosie (thanks to hamdir)
the latest Beats Audio(Thanks to RcmixTeam) & cyanogen-dsp manager
A ton of languages included
Completely De-odexed
EXT4 Optimization Complete
5X5 app drawer
XLOUD engine Powered by Sony Corporation
Advanced Power Menu
some Imported Sensation Xl audio driver
Amaze Camera V8 fully working With 3.5 Stock gallery(thanks to CdTDroiD & Baadnewz)
Imported Full Bravia engine(lib, etc, framework)
Advance Powermenu
Improved Adreno220 configuration for better quality and performance
Added Bliss Default Videoplayer
Tweaks for a smooth, faster and better performance
Improved mms(Secure sms and block list, trashcan, backup & restore, enable in sms setting)
Improved Audio(Extremely enhanced sound for Delight your music)
Improved auto-brightness values
Fixed key backlight Issue
Imported paintdriver from Bliss
Full bash shell with nano
Fixed Native Screen capture
Extended quicksettings added (flashlight, hot reboot, wireless adb)
Added BatteryBar Settings (Thanks to pvyParts)
Remove unnecessary apk
Tweak DB & more (from Warm ROMS)
And more.. more tweak for a smooth..
Updates:
v1.7
SUPER FAST & BETTER PERFORMANCE
Disabled MMS Compression
Enabled 3D Home screens with toggle in display settings
Added Drop clean caches
Tweak Threshold
Tweak Render UI with GPU
Attempting to stabilizing
More Smooth & intuitive response
Tethering hopefully fixed
Disabled Scrolling Cache (Smooter UI)
Modified Beats audio
Vdd Cpu set (For stabilizing )
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Net debugging hopefully fixed
Updated some drivers
heat & bootloop & battery drain hopefully fixed
And more..
Click to expand...
Click to collapse
**Notice***
I am a full time employee & student. If something is urgent please PM me and I will add it. Otherwise I will try to update this thread weekly.
Frequently Asked Questions
Q: Highest phone can be overclocked too?
A: 1.5ghz or 1.7ghz depending on your kernel. Use SetCPU to control the ranges and profiles.
Q: How do I use SetCPU?
A: First off no two phones perform exactly the same. Trust me.
Thanks DavidCampbell
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Click to expand...
Click to collapse
Q: My phone doesn't wake up while sleeping when I get a phone call.
A: Flash the CRT Patch here
**placeholder**
What's the fastest this can be overclocked to?
bangorang said:
What's the fastest this can be overclocked to?
Click to expand...
Click to collapse
some older kernals went all the way up to 1.8 but currently the two kernals are 1.7 or 1.5 ghz on this specific rom as of the 15th
bigballa said:
some older kernals went all the way up to 1.8 but currently the two kernals are 1.7 or 1.5 ghz on this specific rom as of the 15th
Click to expand...
Click to collapse
Which kernel goes up to 1.7? I flashed the one he made a thread for but it went to 1566000... or is that equivalent to 1.7? I though that was 1.5.
bangorang said:
Which kernel goes up to 1.7? I flashed the one he made a thread for but it went to 1566000... or is that equivalent to 1.7? I though that was 1.5.
Click to expand...
Click to collapse
I think those with native 1.2 are allowed up to 1.56, and those with native 1.5 has the higher limit with the kernel. Keep in mind QC only had to make sure the processor runs at 1.2 for the Vivid and not 1.5, so even though the APQ8060 is rated up to 1.5, there is no guarantee that the Vivid will run PERFECTLY at 1.5 or beyond.
I reflashed and am now able to overclock at 1.7. I used the kernel from his kernel thread. Thanks!
Sent from my HTC Raider X710e using XDA App
dizzyraider said:
I think those with native 1.2 are allowed up to 1.56, and those with native 1.5 has the higher limit with the kernel. Keep in mind QC only had to make sure the processor runs at 1.2 for the Vivid and not 1.5, so even though the APQ8060 is rated up to 1.5, there is no guarantee that the Vivid will run PERFECTLY at 1.5 or beyond.
Click to expand...
Click to collapse
This isn't logical. The only reason HTC vivid is at 1.2 is because att likely wanted it underclocked so that the skyrocket would be showcased with higher specs. The true stock clock is 1.5. Hence oc to 1.7 to 1.8 would cause no more potential damage to it than if it were the velocity which are the exact same phone.
Sent from my HTC Raider X710e using xda premium
Thankfully mine is stock at 1.5... I suggest to those overclocking you use setcpu and set profiles to force the phone to underclock at certain temperatures, this has saved my phones in the past, I've never blown a cpu.
I beleive the vivid and raider are at 1.2 to give better battery saving. I run mine at 1.18 most of the time anyway.
davidcampbell said:
Thankfully mine is stock at 1.5... I suggest to those overclocking you use setcpu and set profiles to force the phone to underclock at certain temperatures, this has saved my phones in the past, I've never blown a cpu.
I beleive the vivid and raider are at 1.2 to give better battery saving. I run mine at 1.18 most of the time anyway.
Click to expand...
Click to collapse
What CPU settings on each profile? That should definitely be a FAQ. I have setCPU and I just use inteldemand with the min at its lowest and max at the highest of 1.7
Sent from my HTC Raider X710e using XDA App
bangorang said:
What CPU settings on each profile? That should definitely be a FAQ. I have setCPU and I just use inteldemand with the min at its lowest and max at the highest of 1.7
Sent from my HTC Raider X710e using XDA App
Click to expand...
Click to collapse
If i see some good profiles written out anywhere ill add them to the FAQ if not then ill go ahead and create a base template to how i use it.
bigballa said:
If i see some good profiles written out anywhere ill add them to the FAQ if not then ill go ahead and create a base template to how i use it.
Click to expand...
Click to collapse
Ok thank you so much, I just don't wanna brick my phone for not knowing how to set my setcpu
Sent from my HTC Raider X710e using XDA App
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
A little something you can put in this thread (just trying to help you out since you already have work and school on your hands haha).
If you have AT&T, download This and this kernel View attachment 02_15_2_flash_boot.rar. Remember to also flash the Kernel a second time after you flashed the ROM.
If you want your LTE symbol, flash the View attachment 1.6a_stabilizing_patch.zip after you've flashed your kernel for the second time
Q: How do I get my Wifi and tethering back?
A: Chances are, you only flashed the Kernel once (right before you flashed the ROM). Reflash it after the ROM is installed and it should be fixed.
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Text message issue - only 80 characters per 1 text?
I flashed my Raider already over 50 times. Tested many ROMs.
I've noticed that only Holiraider by Bananacakes (all versions) has only 80 characters per 1 txt message even when Support special accent characters is OFF.
Factory ROM or any other ROM from different Developer has all the time 160 per 1 text (as it supposed to be).
Anyone knows how to get 160 characters per 1 text msg on Holiraider by Bananacakes ?
Any fix for this issue would make this ROM completly perfect
I'm sticking with HoliRaider ROM because has integrated Beats and Amaze Camera which those features are awesome and everything else works perfectly
davidcampbell said:
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Click to expand...
Click to collapse
I know both HoliRaider as well as the WCX Rom has a native script that sets the cpu governor and clock speed on boot, it is recommended that you delete this if you want to run SetCPU or utilities as such. Without deleting the script, the settings might not stick as there could be conflict.
The file that should be deleted is /system/etc/init.d/15-screenstate_scaling
or
you could open the file with any text editor and change the setting according to your need
xavier_largeaux said:
I flashed my Raider already over 50 times. Tested many ROMs.
I've noticed that only Holiraider by Bananacakes (all versions) has only 80 characters per 1 txt message even when Support special accent characters is OFF.
Factory ROM or any other ROM from different Developer has all the time 160 per 1 text (as it supposed to be).
Anyone knows how to get 160 characters per 1 text msg on Holiraider by Bananacakes ?
Any fix for this issue would make this ROM completly perfect
I'm sticking with HoliRaider ROM because has integrated Beats and Amaze Camera which those features are awesome and everything else works perfectly
Click to expand...
Click to collapse
I'm not having this problem on stock SMS or even using GoSmsPro
I'm on 1.7 now.
cifs module?
Is there a CIFS module compatible with this kernel/ROM at the moment?
Since bananacakes would probably already include it, I'm guessing there's no cifs module at the moment. But, I just thought I'd check to be sure.
Thanks again!
need a mirror site for 1.7 depositfiles is down -_-
jh64dsb877r said:
Is there a CIFS module compatible with this kernel/ROM at the moment?
Since bananacakes would probably already include it, I'm guessing there's no cifs module at the moment. But, I just thought I'd check to be sure.
Thanks again!
Click to expand...
Click to collapse
not that i know of or see throughout the thread.
ok, nothing seemed to be making the touchscreen responsive with the ICS beta n its derivatives.
except one thing just did.
i changed the sampling rate from 200000(2 lak) to 20000 (20 hazar), n of course i had to change the up-threshold so i changed that to 95 (i did all these in rom-toolbox's kernel tweaks settings)
now everything is super-responsive (app startups, physical buttons, onscreen buttons, switching, yo name it) N while you are just lets say reading stuff on the screen, the cpu is generally at its lowest
what that means is : both responsiveness and higher battery.
please comment.
UPDATE : check the 7th post on this forum for more tweaks for snappy app launching n switching here http://forum.xda-developers.com/showthread.php?t=1570374#post24186676
UPDATE : ADDITIONAL TWEAK (more battery life) : in rom-toolbox change powersave bias to 35 (in rom toolbox) : saves a lot more battery by preventing the cpu from rushing to full-frequency while you are doing simple tasks like flicking the screen.
UPDATE : 3/31/12 : an interesting observation about "force gpu" 's causing poor performance on my post here : http://forum.xda-developers.com/showthread.php?t=1570374&page=2#post24266342
UPDATE : 4/7/12 : want even more battery life n smoothness?
add these to your build.prop save , reboot into recovery, clean dalvik-cache and /cache partition then reboot into system. things should be faster. and oh, underclock it.
ro.kernel.android.checkjni=0
dalvik.vm.execution-mode=int:jit
ro.ril.disable.power.collapse=0
ro.mot.buttonlight.timeout=1
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
you can also do a semi-odex using titanium backup's integrate system dalvik into rom thing, but then you won't be able to change any file in the rom (like applying patches, mods etc until you've either done undo integration thing in titanium backup or just used adb shell to delete *.odex from /system/apps n rebooted)
UPDATE : 4/28/12 : if you are using a derivative of the .562 ICS then you can change the kernel tweaks/sysctl settings to dirty_ratio = 80 dirty_background_ratio = 20 and vfs_cache_pressure = 20 to get snappy app startups up_threshold and powersave_bias can both be set to 90 and select ignore_nice_load. if you use lots of apps then raise the dirty background ratio and dirty ratio both by 15 points and reduce vfs_cache_pressure by 15 for low cpu usage while the apps are running. i've noticed that many of the custom roms have started getting my tweaks or similars preincluded , plus the official ics is much better than icsbeta in memory management. and oh, use arcknight kernel. its super awesome for both features and battery life. i switch my governor to interactivex or smartassv2 when i am recording using the 14mbps camcorder mod, and then back.
the android backup & restore under person in settings should be turned off. it takes a lot of cpu, battery, data n memory. its aweful.
if this works for you, press the thanks button.
How can this be done?
Duvel999 said:
How can this be done?
Click to expand...
Click to collapse
i used rom toolbox pro, its free version is available here - https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
anything else that can edit sysctl.conf (e.g. https://play.google.com/store/apps/details?id=com.jrummy.sysctl.config and https://play.google.com/store/apps/details?id=scd.atools ) will also work.
Gonna try it
system seems to be a bit snappier
thx mate
thnx mate.
for snappy app switching i discovered another bunch of settings
in rom toolbox's kernel tweaks under performance, change min free kbytes to [CORRECTION]8192[not 8096] (or [UPDATE] 6144 - whichever one you like), dirty ratio to 95, dirty background ratio to 70 and vfs cache pressure to 5 (n of course check the apply on boot option)
let me know how you like this additional tweak
UPDATE: some observations ; high dirty ratio causes lower cpu usage n faster app-switching, low dirty background ratio causes faster app startups but uses too much cpu, vfs cache pressure above 5 or 10 causes high cpu usage n lags. (i use lots of apps)
UPDATE #2 FURTHER IMPROVEMENTS (fast all around with acceptable cpu usage, super app switching, n decently fast launcher without sacrificing cpu-speed n battery life)
Kernel Tweaks :
reduce dirty background ratio to 50
check the OOM kill allocating task (if your device crashes after this, uncheck this, it may kill the android system n android os processes as well in some cases)
Auto Memory Manager :
foreground 6
visible 8
secondary 32
hidden 40
content 48
empty 120
Thnks
[white10char]
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
perhaps kickass kernel script
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
check the 98kickasskernelizer (i'd find the respective values - especially min-free n change them in the script itself), there are two other not so popular scripts out there too that you may be using.
please share with us whatever was causing the overriding of rom toolbox's (or sysctl etc)'s settings.
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
hansip87 said:
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
Click to expand...
Click to collapse
the benchmarks dont tell you about usability. better responsiveness is due to faster cpu response to situations.
antutu's benchmark tests for continuous high performance (battery hogging w/lags) while running just one app.
my settings are for giving great experience (touch, app switching and app launching as well)
think of it as antutu being a mr. universe test, while mine are a gymnastics olympics tournament.
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
darth5zaft said:
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
Click to expand...
Click to collapse
thank you.
i just posted another slight tweak for higher battery life. its in the first post.
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
Could it be that these settings are conflicting with Supercharger?
Sent from my LT15i (Xperia arc) on KA ICSony
hootnath said:
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
Click to expand...
Click to collapse
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
estuardo4 said:
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
Click to expand...
Click to collapse
i found another interesting thing today.
the force GPU for 3d in the settings -> developer options actually uses a lot of the cpu and causes lags. i turned it off and have instead done the following
Get rid of CPU rendering:
Navigate to /system/lib/egl/
Open the file named "egl.cfg"
Delete the first line. It should say "0 0 android" or something similar
Go back into the egl folder and delete libGLES_android.so
What this does is remove the entire soft-rendering pathway from the OS.
source : http://www.ifans.com/forums/threads/ics-performance-tweaks.369959/ ;
now, i have changed the powersave bias in teh romtoolbox's kernel tweaks to 95 instead of {correcton}35{not]95. the cpu is spending more time @ 122mhz and deep sleep now without lags (which means more battery)
if this thing works for you, please press thanks.
LuPuS Kernel
{
"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"
}
Built with Linaro
Has added init.d support
LuPuS-PRO-STOCK KERNEL
Hi I know I haven't updated this in a long time so going to change it. The problem was the wifi but finally I got it fixed with the help from FXP - Jerpelea
and of course my trusty tester DYMPY been trying to get wifi going on this the last week lol anyway done now
so what i'm going to do is just update this by the end of the week to add everything else in.
So here is whats added so far ------------
What Works --
Wifi - (flash modules)
Data
Camera
Panorama
Video Recording (720p now works)
Video Playback
Front Camera
Bluetooth
Everything Else that works on FXP
What doesn't work --
Anything that doesn't work on FXP
Added Governors --
brazillianwax
smartass
Smartassv2
Savagedzen
Smoothass
Scary
InteractiveX
Minmax
Userspace
Intellidemand - Thanks to faux123
This is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling,
and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such.
Intellidemand does not jump to highest frequency when screen is off.
Lazy - Thanks to Ezekeel
The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand.
Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state
on a step overriding sampling interval.
Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always
select the maximum frequency while the screen is off.
Lulzactive - Thanks to Tegrak
Based on Interactive and Smartass. When workload is greater than or equal to 60%, the governor scales up
CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step.
When screen is off, frequency is locked to global scaling minimum frequency
- Superbad
- a "superbad" super smooth rendition of a highly optimized "smartass" governor!
- Darkside
- a "slightly more agressive smart" optimized governor!
-Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
-Lionheart:
Is a conservative-based governor. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1024Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
-Virtuous
Virtuous is a modded smartassV2 which gives even more battery time then smartassV2
Added Io-scheduler --
VR io-scheduler - Unlike other schedulers, synchronous and asynchronous requests are not treated separately,
instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
- SIO- Simple IO-Scheduler
- Updated and Changed Zram (thanks to faux123)
- Updated and changed LZO compression and decompression = Double increase in performance
- Added Init.d Support
- Added tweaks on boot
-Overclocked to 2ghz--- Stable up to 1.9ghz, 2ghz may just reboot device, although I do not recommend O/C for long at high settings,
if you damage your phone I am not responsible
- Supports CIFS
- Built with LINARO
Added in v3
-SLQB - (SLAB allocator with Queue)-(both)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate).
- New Governor - Intellidemand2
- BFQ IO-Scheduler
- Cleancache
- Increased Wifi-Signal
- Tweaks for smoother & quicker UI :victory:
- 0% Battery Patch - Thanks to Bazoocaze
I would like to say a big thanks to -
FXP - Sources/help with wifi (thanks Jerpelea)
Cyanogenmod - Sources
DooMLoRD - for patches and all the work he has done for Xpeeria's
xeozus
NobodyAtAll
Faux123
Erasmus
Leedroid
Jerpelea
Anyone missing please PM me
Dympy - For helping me test alot
Dexmorr - testing
tempest918 - For the New Logo
Please Click Thanks :good:
Sources here
Downloads
If you like my work please consider buying me a beer or something else
by clicking the DONATE ME button, of course it isn't needed but greatly appreciated and keeps me motivated.
Thank you to members -
~ Frenchdroid
~ [user_99]
For your kind donations
Disclaimer
Code:
[COLOR="DarkOrchid"]#include[/COLOR] [COLOR="Magenta"][/COLOR]
[COLOR="Blue"]/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone
* bootloops and alarm does not go off. Please do some research if you have any
* concerns about features included in my kernel before using it! YOU and only
* YOU are choosing to make these modifications.
*/
[COLOR="Magenta"]#if[/COLOR]
You have a [COLOR="DarkGreen"]question[/COLOR] post it in the [COLOR="DarkRed"]thread[/COLOR],
Instead of [COLOR="DarkGreen"]Pm'ing me[/COLOR], as other users may
experience your [COLOR="DarkRed"]problems[/COLOR]
[COLOR="Magenta"]#endif[/COLOR][/COLOR]
LuPuSv3 Downloads
LuPuSv3-CM9-PRO.img
MD5 = AF25D5164DA13973EA465D25C6AF47B0
WiFi-FIX-LuPuSv3-PRO-CM9.zip
MD5 = 39BD6F753AF6E68D955E9504BA48E015
Some people are having boot problemw with v3 if you are try this
LuPuSv3.1-cm9.img
LuPuSv3.1-cm9-wifi-fix.zip
Also added CIFS support....
What is CIFS???
Server Message Block (SMB) or Common Internet File System (CIFS) are normally used to provide shared access to files on a network, mostly involving computers running MS Windows.
It allows you to conveniently mount/unmount your network accessible file resources and access the files transparently via your favourite Android app (playing music / videos, accessing documents etc.) Settings are stored on your SD card with permissions to write also to your SD card.
Instructions
- extract cifsfile.zip
- save cifs,ko file to your sdcard
- in terminal emulator
- cd sdcard
- su
- insmod cifs.ko
Not download CifsManager or similar app and configure it
- zRam is not enabled by default to enable it flash the wedgess-zram-enabler.zip in CWM
- If for whatever reason you want to disable Zram after you have flashed the .zip, just go to ect/init.d and delete 00zram
People will ask so i'll just post it here---------to check if zRam is enabled go to terminal emulator or similar and type
Code:
free
or alternatively
Code:
cat /proc/swaps
Please Click Thanks :good:
Will try and report as soon as wifi works
Sent from nowhere
HI,
Is this kernel can be used with CM10. If not, can you post one that can be used with.
Thanks
Tried it, no bootsplash, don't work with CM10.
can we get a stock rom based lupus kernel with jimbo77's (arcknight) kernel's lcd voltage lowering, wifi voltage lowering tweaks, camera-memory lowering (among some other kernel tweaks he has on there) as well as KTG anzu kernel's 2d drawing and touchscreen drivers?
also, it seems that at low vfs values and low sampling rate, arcknight does random reboots ;; while ktg-anzu has aweful battery life. even during sleep. plus, i am able to run the ktg-anzu stable at lower voltages (825 for 122mhz and 1000 for 1024) than i am able to run the arcknight stably. ktg-anzu's kernel's memory usage, strangely, moves between 20mb and over 150mb --- it has very recently started staying over 130mb after happily working at about 20mb (at least when i'd check it it'd be at 20) for weeks.
arcknight and ktg both seem to have certain awesome aspects of them while neither of them is complete --- plus, they both seem dead now.
all arc users are now relying on you.
This kernel not working for me only blank screen and does nothing does not even go to recovery/ aroma by pressing either of the buttons
Sent from my Arc S using xda premium
If there's one thing I've learnt, it's that it's never lupus.
Yay finally als disabled! btw will this support undervolting?
mekayzer said:
HI,
Is this kernel can be used with CM10. If not, can you post one that can be used with.
Thanks
Tried it, no bootsplash, don't work with CM10.
Click to expand...
Click to collapse
No its only for CM9 as stated JB is to unstable at the moment
hootnath said:
can we get a stock rom based lupus kernel with jimbo77's (arcknight) kernel's lcd voltage lowering, wifi voltage lowering tweaks, camera-memory lowering (among some other kernel tweaks he has on there) as well as KTG anzu kernel's 2d drawing and touchscreen drivers?
also, it seems that at low vfs values and low sampling rate, arcknight does random reboots ;; while ktg-anzu has aweful battery life. even during sleep. plus, i am able to run the ktg-anzu stable at lower voltages (825 for 122mhz and 1000 for 1024) than i am able to run the arcknight stably. ktg-anzu's kernel's memory usage, strangely, moves between 20mb and over 150mb --- it has very recently started staying over 130mb after happily working at about 20mb (at least when i'd check it it'd be at 20) for weeks.
arcknight and ktg both seem to have certain awesome aspects of them while neither of them is complete --- plus, they both seem dead now.
all arc users are now relying on you.
Click to expand...
Click to collapse
I can see if I can get the stock kernel I have from the play working on the arc.had no problems with it on the play.I don't have an ARC so need you all to test it for me.
PAVNEET101 said:
This kernel not working for me only blank screen and does nothing does not even go to recovery/ aroma by pressing either of the buttons
Sent from my Arc S using xda premium
Click to expand...
Click to collapse
It 100% works in the ARC pro as I said I don't have an ARC so can't test
Phrenks said:
If there's one thing I've learnt, it's that it's never lupus.
Click to expand...
Click to collapse
Huh???
Sent from my Xperia Play
Hmm, seems like an interesting kernel, would love to try this one out on my Pro.
However, I only see an .img labeled ARC, so no image for Pro yet?
Dympy.
dympy said:
Hmm, seems like an interesting kernel, would love to try this one out on my Pro.
However, I only see an .img labeled ARC, so no image for Pro yet?
Dympy.
Click to expand...
Click to collapse
That one is for PRo buddy
Sent from my Xperia Play
Awesome!
Going to download, flash and report
Dympy.
EDIT:
Just flashed it, and there's some crazy sh*t happening here..
It seems CWM is simultaneously running with android itself..
Each time I press a hardware button my screen starts flickering between CWM and my Android screen.
It does work, except for wifi, it can't turn on for some reason.
Going to try wiping some stuff and see if it gets fixed.
EDIT2:
Nope, couldn't wipe a thing because I couldn't get into CWM.
Both the home key as the volume down key booted into Aroma, never used it but it was awesome!
Hope you can help, I'll dig up some logcats if I can and I'll retry when I get home, kinda need my phone for developing at work
EDIT3:
Took out the logcat where I tried turning WiFi on, see attachment.
dympy said:
Awesome!
Going to download, flash and report
Dympy.
EDIT:
Just flashed it, and there's some crazy sh*t happening here..
It seems CWM is simultaneously running with android itself..
Each time I press a hardware button my screen starts flickering between CWM and my Android screen.
It does work, except for wifi, it can't turn on for some reason.
Going to try wiping some stuff and see if it gets fixed.
EDIT2:
Nope, couldn't wipe a thing because I couldn't get into CWM.
Both the home key as the volume down key booted into Aroma, never used it but it was awesome!
Hope you can help, I'll dig up some logcats if I can and I'll retry when I get home, kinda need my phone for developing at work
Click to expand...
Click to collapse
Hhhmmmmm strange maybe CWM 6 doesn't work with the arc I'll switch to v5.yes log cats would be good .......anyone else having this problem??????
Sent from my Xperia Play
You say it's for the Arc, but when I asked if it would work for Pro, I asked there's only 1 download available in the OP and that one was labeled ARC, you replied yes.
I think this kernel isn't compile for the Pro, but only Arc specific.
It's all a bit confusing since the Pro doesn't have his own forum.
By the way, I added the first LogCat, for the WiFi bug, in the post you quoted.
Dympy.
dympy said:
You say it's for the Arc, but when I asked if it would work for Pro, I asked there's only 1 download available in the OP and that one was labeled ARC, you replied yes.
I think this kernel isn't compile for the Pro, but only Arc specific.
It's all a bit confusing since the Pro doesn't have his own forum.
By the way, I added the first LogCat, for the WiFi bug, in the post you quoted.
Dympy.
Click to expand...
Click to collapse
Sorry ye the person who was testing was using ARC PRO so that's what it works for as of now.will it still not boot with CWM 6 it worked for the person testing it?? That's what I thought the log at was for. Wifi won't work yet because of the modules. I will try fix this once I get home.
Sent from my Xperia Play
Okay, I think I got a bit confused now.
The phone we're talking about is the PRO, since xperiap (I believe) tested it, it must work on my phone.
Anyway, Is there something I have to wipe after flashing this kernel, because I wiped absolutely nothing the first time I flashed it.
And yes, CWM worked the first time, it booted into it when I just flashed the Kernel.
Dympy.
dympy said:
Okay, I think I got a bit confused now.
The phone we're talking about is the PRO, since xperiap (I believe) tested it, it must work on my phone.
Anyway, Is there something I have to wipe after flashing this kernel, because I wiped absolutely nothing the first time I flashed it.
And yes, CWM worked the first time, it booted into it when I just flashed the Kernel.
Dympy.
Click to expand...
Click to collapse
Ok so it booted into CWM while holding the the home key?? Ye xperiap is using the ARC-PRO and he said he's having no problems it boots everytime for him, I'm not sure if he wiped anything but I never usually wipe anything when flashing kernels so don't think that could be the problem, so it just wont go past the boot screen for you, correct??
wedgess said:
Ok so it booted into CWM while holding the the home key?? Ye xperiap is using the ARC-PRO and he said he's having no problems it boots everytime for him, I'm not sure if he wiped anything but I never usually wipe anything when flashing kernels so don't think that could be the problem, so it just wont go past the boot screen for you, correct??
Click to expand...
Click to collapse
O.K mate you are confused and your confusion is confusing others.ARC and Pro are two diffrent Phones.There is no ARC-PRO.there is:
Xperia Arc
Xperia Pro
This kernel is for pro.
manasgirdhar said:
O.K mate you are confused and your confusion is confusing others.ARC and Pro are two diffrent Phones.There is no ARC-PRO.there is:
Xperia Arc
Xperia Pro
This kernel is for pro.
Click to expand...
Click to collapse
^^
Sent from my Xperia Play
Thank you.
That was indeed the part confusing me because the dev kept calling it the Arc Pro.
And no, both home and volume down button boots into Aroma, not CWM.
The first time I booted it went into CWM automatically.
After that it booted, but I had CWM flashing through my normal android screen each time I pressed a button which was also linked to a CWM function (vol up/down, home, back, etc.).
But like I said, almost home and I'm going to do a retry then
Hope you get wifi modules fixed soon.
Dympy.
Sent from my Pro using xda premium