Related
Thanks to Leshak , AndSecTest, mimocan, Unhelpful, xan, Supercurio and husq510 for the help.
This project started based on information found here:
http://forum.xda-developers.com/showthread.php?t=740514
But is has soon revolved into more fixes, patches and hacks. Thanks to all the developers involved and do buy them beers so they can continue to work on the fixes.
I've tested it to work on my phone but i cannot guarantee it will work on yours or if it will damage your phone so use it at your own risk. See known issues below if the problems have been resolved
Primary Features
- ext2/3/4
- Support I/O Scheduling for CFQ (stock), Noop, Deadline and Anticipatory
- Overclock and Undervolt support
- Overclocking for better performance. If you do not want to OC, use SetCPU to set Max at 1Ghz and enable checkbox Set on boot
- User defined Undervolt to save battery especially at lower frequencies. Use Xan's app for easy GUI control - here
- Also use Xan's app to change IO scheduling
- Rooted ADB shell for Android commander compatibility
Requirement
- i9000
- For Eclair 2.1 Only (Will not work on Froyo firmware)
My setup for cross compile without wakeup lag
- Use ct-ng crosstool
- Copy config file from arm-unknown-linux-gnueabi
Download
See attachment
Stock Kernels for reverting
Stock JM3 v3 kernel
Stock JM2 kernel
Stock XWJM5 kernel
Instructions:
- Extract the tar file from .7z
- Load tar file in PDA using ODIN and flash
- Do not check repartition and do not use pit file
- Use SetCPU to adjust frequencies
Reporting Problems
Please provide information below to help me understand:
kernel version: (eg oc120uv2-ctng)
UVLF setting (if kernel supports): (eg 50)
UVHF setting (if kernel supports): (eg 25)
descriptions:
Known Issues
- ondemand setting is unstable (need more verifications)
TO DO LIST
- BFS scheduling
- kernel modules (submit request)
Changelog
oc120_voodoo_b4.2
- enable CWM support even with voodoo ext4. Caveats: CWM will unmount /data after nandroid backup, you will not be able to remount /data in ext4 until you reboot back to recovery. Also, restore does not work when trying to restore /data.
- fixed check for debug_mode (it used to create logs in /sdcard/Voodoo/logs regardless if you enable*debug in /sdcard/Voodoo/)
oc120_voodoo_b4.1
- BLN patch v4 from neldar (http://forum.xda-developers.com/showthread.php?t=772672)
- All credit goes to author
- Signed update.zip format so rename file to update.zip and copy to /sdcard
- use recovery to flash
oc120_voodoo_b4
- updated to voodoo b4 (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120_voodoo_b3.1
- fixed init.d not working
oc120_voodoo_b3
- remove performance governor from startup cos i9000 dont need that
- added init.d support
oc120_voodoo_b2
- Use stock GPU ~200mhz table
- Voodoo2 lagfix (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120uv2
- Unhelpful patch for GPU table (http://github.com/Unhelpful/linux-galaxy/commit/5a729d3e2189159a20b00e0c331f0b112490e075)
- Interactive governor (http://github.com/Unhelpful/linux-galaxy/commit/aea72a98a2f261901d6f28f2d1deae3921d35948)
- user configurable UV settings (default value = 0 for UVLF and UVHF) for conservative governor only
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (for 100-800mhz)
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (above 800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (will UV by 50mV for 100-800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (will UV by 50mV for 1-1.2ghz)
- Setting increment of 25 (eg 25,50,75,100). Anything out range may hang
- Anything above 100 will be set to 100 (but I doubt you can get 100mV without crashing)
- After setting, do ur benchmarks and if everything is stable, you can add the command above into your init script depending which lagfix you have, add into your script.
Thanks!
Some questions:
1) the first thread about oc mentioned 1.2ghz, was this unstable for you?
2) Is this over-volted, under-volted, or no changes in voltage?
3) I'm guessing if I update to this kernal, I will loose any features of other kernals, like the lag-fix kernal?
I hope you can persuade the other devs to include this in their roms.
It this just for the unbranded SGS or does it work for TMO vibrant too?
Novek said:
It this just for the unbranded SGS or does it work for TMO vibrant too?
Click to expand...
Click to collapse
the kernel is just for the international version
it is just a test, i hv not test the limit yet.. this is a new phone so want to take it easy
i kept the voltage stock so just overclock a little and if its stable, will do more . More testing and reading is needed before i touch on the voltage.
it does not include mimocan's mod, i will work on it next release
Not Work
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Sir-ay said:
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Click to expand...
Click to collapse
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Nice job cant wait to see how high the new hummingbird cpu can go. The galaxy s 2 has same cpu and is running at 2 ghz (if the leaked info is correct). I hope we can push it up to 2ghz with out to much voltage/heat increase.
[[ Cold ]] said:
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Click to expand...
Click to collapse
upps
I will OC!!!!!!!!!!
Do you notice the postive effects of the overclock in any way? What does it do with benchmarks? Also do you test for (temperature) stability with some games as well, as they use the graphics card a lot which is on the same chip. Even when not overclocked the SGS can get prettty warm.
Installs nicely, oc ok to, but dont see that much increase in linpack.
Nice work tho.
Any chance to have ext 4 support in next update?
Thanks :
updated to v2
raspdeep said:
updated to v2
Click to expand...
Click to collapse
you're fast, lol. Thanks.
INeedYourHelp said:
your fast, lol. Thanks.
Click to expand...
Click to collapse
update before i go to bed
Guys, how do I use SetCpu?
Was 1.2ghz unstable?
Sent from my SGH-T959 using XDA App
interested in this... Allthough the phone does seem to get hot during heavy use, it doesn't get 'too' hot.
I have seen about 47 degrees celcius max read from battery temp (which seems to be cpu temp on our phones as my battery was stone cold)
Hi any possibility get v1 without mimocan.
Got samset including it nd sgs wnt boot cause of mimocan included.
thanks
I am using JM2. Does this make my phone any faster? Does it maked it lag free?
After tested this oc.. i am bit unsure: i get no performance increase... Is it confirmed that its functional?
[15.July.2011][ROM][GSM][2.3.3] ◄► Overcome ROM v3.0.1-JUPITER ◄► Kernel v3.3.0 ◄►
DISCLAIMER: You know the drill, I am not responsible if loading this rom makes your Tab melt, explode, disintegrate, or cause harm to anyone near it. (I am fairly certain none of that will happen though )
Change log in second post.
ROM FEATURES
BGJP4 Base Rom - ANDROID 2.3.3
Overcome kernel v3.3.0 included
No Modem is included - due to a variety of personal preference I decided to leave that a la carte
Fully Deodexed
Fully Zipaligned
Rooted with busybox installed
Reboot/Recovery/Download options added to the power menu
Accurate battery mod with gingerbread styling
Blur removed across system (i.e. behind power option menu) - significantly improves performance
Power Off confirmation disabled
Screen off animation enabled
Overscroll Glow effect enabled
Added AppWidgetPicker
CSC set to XEU
Ads Blocked
Updated Market to 3.0.26
Updated Maps to 5.7.0
Flash Player removed due to compatibility issue - install from market and you'll be all set.
Updated GMail to 2.3.4
Updated YouTube to 2.1.6
Updated SamsungApps to 2.5.039
Updated StreetView to 1.6.0.6
Updated Thinkfree Office Suite
Removed Startup/Shutdown sounds
Cool boot animation
A2DP Bluetooth Connection Fix Integrated
SIP calling enabled over 3g AND WiFi
Fugutweaks integrated
Browser mods (enabled "Default Zoom" in settings, added "User Agent" in settings, set plugins to "on demand" by default)
KERNEL FEATURES
Support RFS/EXT2/EXT3/EXT4
OC/UV with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Replaced kernel jhash2 with jhash3
Adjusted kernel HZ value to improve smoothness
Optimized lowmemorykiller values
Optimized compiler flags
Voodoo Sound v10 (courtesy of supercurio)
Voodoo Lagfix (courtesy of supercurio)
Overcome CwM Recovery v4.1.0.9 (Custom built Clockworkmod v4.0.0.9)
Full support of internal/external SD cards in Recovery
Simple I/O Scheduler added and set as Default
Kernel tweaks to VM and Scheduler for better performance
Built in CIFS/TUN/SlowWork support
Touchscreen Undervolting (courtesy Koxudaxi)
RAM Undervolting
Stochastic Fair Blue (SFB) Network Scheduler
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications (Thanks to Neldar for the mod and Koxudaxi for the patch)
INSTALL GUIDE
http://www.teamovercome.net/?page_id=64
DOWNLOADS
http://www.teamovercome.net/?page_id=558
TIPS AND TWEAKS
http://www.teamovercome.net/?page_id=68
FAQ's
http://www.teamovercome.net/?page_id=66
SOURCES
https://github.com/alterbridge86
The best is yet to come!
ROM AND KERNEL CHANGE LOG
http://www.teamovercome.net/?page_id=171
Overcome v3.0.1-JUPITER
Overcome Kernel v3.3.0 Included
Themeing tweaks (Thanks to DarkPal and friends)
Market updated to 3.0.26
CSC Changed back to that from JQ1 (this should resolve the issue with downloading zinio/kobo/etc.)
Overcome Kernel v3.3.0
Built using CodeSourcery 2011.03 toolchain (faster and more power efficient code)
Overcome CwM Recovery Updated to v4.1.0.9 (Based off ClockworkMod Recovery v4.0.0.9)
[CWM] Option under Tweaks to enable/disable shortened backlight fix
[CWM] Nandroid restore no longer borks the kernel
[CWM] No more annoying "back button disabled" (Hooray!)
[CWM] Shortened Yes/No confirmation menus
[CWM] Make /dbdata wipe when executing "factory reset/data wipe"
[CWM] Make /emmc/.android_secure wipe when executing "factory reset/data wipe"
[CWM] Complete restructuring of menus
[CWM] Streamlining of commands and elimination of some never used features that were cluttering the interface
Updated to Voodoo Sound v10
Numerous upstream patches
Add V(R) I/O Scheduler
Increase voltages to pre-Icarus levels
Removed device detection script (should resolve all issues with some users getting hung at Samsung screen or having no conversion/cwm)
Tweaks to lowmemkiller behavior
Added arm enhancement to allow CPU-supported unaligned accesses
New release - new thread! Idea behind this is to keep the amount of posts people have to crawl through down to a minimum. Enjoy!
OH WOW!!!!!!
You're Great AB86 and all the OC team
Thanks
Sent from my GT-P1000 using XDA Premium App
Downloading
So definitely solved the recovery problem?? What was causing such a messy recovery??
Pharaohnough said:
OH WOW!!!!!!
Click to expand...
Click to collapse
thanks friends
Wow, new release? that was really fast.
Thanks again guys.
Just one question, what is the version of the kernel in this new version? Because Kernel v3.3.0 is now on download page but in change logs of Overcome v3.0.1 JUPITER in the second post it says: Overcome Kernel v3.2.0 Included.
theduke89 said:
Downloading
So definitely solved the recovery problem?? What was causing such a messy recovery??
Click to expand...
Click to collapse
I'm assuming you're referring to the "disappearing" recovery...basically the way Voodoo works, since its designed to support a broad range of devices, is it runs a script to identify exactly which device its running on. This script dumps the partition table from the /dev/block/mmcblk0 and compares it to a list of known dumps. From then, it decides how to set up the file system. If it fails to find a match, it just exits out and goes to samsung init. As a result, you will either 1) boot into the ROM with the RFS file system or 2) boot into stock recovery, because that's what the stock init does.
What I've done is just remove the detection part and hard code it to a particular file system structure. The issue should definitely be resolved now.
alterbridge86 said:
I'm assuming you're referring to the "disappearing" recovery...basically the way Voodoo works, since its designed to support a broad range of devices, is it runs a script to identify exactly which device its running on. This script dumps the partition table from the /dev/block/mmcblk0 and compares it to a list of known dumps. From then, it decides how to set up the file system. If it fails to find a match, it just exits out and goes to samsung init. As a result, you will either 1) boot into the ROM with the RFS file system or 2) boot into stock recovery, because that's what the stock init does.
What I've done is just remove the detection part and hard code it to a particular file system structure. The issue should definitely be resolved now.
Click to expand...
Click to collapse
Understood, thanks it was less complicated then I thought
Feedback coming soon for Jupiter!!! You are great, friend
Just drop by to say thanks that the jupiter kernel now works on my set up (DXJPE /w ext4). I'm going to drop off to sleep too as it's over 2am here, will post impression later.
sohrab1985 said:
Wow, new release? that was really fast.
Thanks again guys.
Just one question, what is the version of the kernel in this new version? Because Kernel v3.3.0 is now on download page but in change logs of Overcome v3.0.1 JUPITER in the second post it says: Overcome Kernel v3.2.0 Included.
Click to expand...
Click to collapse
I don't know what you're talking about
(It has the proper changelog now )
This looks and works beautiful. Thanks!
Remember, for every whiner there are hundreds of satisfied users which never say a word.
Awesome rom! Thanks! Can someone tell me how to get my market to log in? I am already logged into google. But it keeps telling me to log into google and crashes. Is there a switch somewhere?
is there away to change the color of backgorund and notifaction bar to white instead of black thanks in advance
chevy383surfing said:
Awesome rom! Thanks! Can someone tell me how to get my market to log in? I am already logged into google. But it keeps telling me to log into google and crashes. Is there a switch somewhere?
Click to expand...
Click to collapse
Had the same problem, made factory reset in CWM and then it worked.
Peter Unger said:
Had the same problem, made factory reset in CWM and then it worked.
Click to expand...
Click to collapse
I just tried a factory reset and it crashed. I just now got done going through the whole procedure again. I did a factory reset under privacy in the settings. Should I be doing a factory reset from within clockwork recovery?
I actually just got it working! Thanks again for the rom!
darkness1414 said:
is there away to change the color of backgorund and notifaction bar to white instead of black thanks in advance
Click to expand...
Click to collapse
Look, theming is really personal preference. Its impossible for us to satisfy everyone's taste. The team thinks that black notification bar rocks so that's that. If you wanna change it to white, you either..
1. Apply stock theme patch
2. Learn how to theme and change it to white yourself
Sent from my GT-P1000 using XDA App
Lovely work, once again, guys. Updated using the no-wipe method. No problems at all everything working fine. Love the signal and wifi icons. Looking forward to your next offering. Thanks heaps.
Sent from my GT-P1000 using XDA App
Thanks Alterbridge and Team.
Just installed JUPITER (no wipe) over ICARUS and everthing seems to be working A-1. Love the new boot screen and the ROM is very fast and very smooth!
Just for those that may encounter the same issue:
Had a little anomaly the first time I flashed. All seem to go as it should and everything worked as it should, however, under 'SETTINGS' > 'ABOUT DEVICE', it said that the kernel was 3.3.0 (#79), but the build number was still 3.0.0- Icarus (Also, on initial boot up the boot screen was still the old Icarus screen). So, I repeated the no wipe flash procedure and everything is now working as it should. Correct kernel and build number in settings.
Thus far everything is working A-1 on this super fast and smooth ROM.
Many thanks again to Alterbridge and the Team.
This is a rebuilt nandroid backup from dsixda's Android Kitchen. Be sure to do a nandroid and do NOT flash this on any other model wildfire s[A510c ONLY]. 2.3.4 as is stock to us, added everything including busybox, A2SD, and su, If any devs would like to pull it apart and meld your kernel in, go for it; otherwise it just works on Virgin US. Again, make nandroid. Should have full HTC sense 2.1. Download Link2SD from market for some space savings, and don't say I didn't warn you to nandroid [three times].
Also, as with any new rom installation. I recommend doing the following in your recovery: a factory reset [which wipes your data and cache] and advanced clear dalvik cache. If you do those two things, you usually don't have any transference issues.
Code:
Android OS version : 2.3.4
Device : marvelc
Model : HTC_A510c
ROM Name : 1.02.652.00
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : YES
BusyBox installed : YES
BusyBox run-parts support : YES
Apps2SD (Apps to EXT) enabled : YES
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : YES
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
--Download Link-- v1.0
Why do you leave your rom build odexed?
Well, first that's how it came, and I wanted a clean stock to build from. Also let us define odexed because for some reason it gets a bad rap.
*ODEX-
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
Click to expand...
Click to collapse
Did we see something about being faster? yep. Did we also see something about saving space? yep.
Basically I deodex on roms under 100 meg, but sense roms are almost always going to be more than that.
Not happy about VM hiding/disabling WiFi and wish your stock had FM Radio?
See this post [same thread] for v1.1
Changelog:
01-01-12 v1.1 [see post link above]
changed hosting sites
updated system apk's
added some useful apk's
made a guide for Apps2sd
enabled, unhid WiFi
added HTC FM Radio
12-04-11 v1.0
totally scraped first build
Found oldest nandroid I had (made shortly after root)
built from that.
Did not deodex this time around.
Known Issues:
Friendstream only has Facebook - no other choices
This is how it came stock; I tried to fix it, but will have to port another sense to get it right.
Thanks
So many I can't remember them all.
eoghan2t7 - for his work developing s-off [w/o xtc clip]
GotsOJ - for being the first to document his s-off experience (was very helpful).
alquez - for his work on the Unoffical CWM Recovery and port of CyanogenMod [which is where I'll be spending some development time next (kernel editing)]
dsixda - of course for his kitchen
jikantaru - lots of sense development for the Euro-side of this phone
BigChillin - for being my first tester
Tera Tike - for very useful contributions to the thread
etc.
P.S. the RUU in the first thread [Football's] is not for Virgin US... maybe Canada or something... didn't work right on my first cook.
You, my dear sir, are fecking amazing.
Sent from my HTC_A510c using Tapatalk
Development Rom
might make this my temporary development rom. I've buit it up with ADW to a minimalist kind of existence. Will recook and add guides for those that care.
Do you all get marvel boot animation and black htc down animation [thanks to Jikantaru]?
Rob
Yes. But the marvel animations framerate might be too much. It's very jumpy.
Sent from my HTC_A510c
rework
I think I'll try to make stock rom flashable; then build this up a bit. No official RUU makes it more difficult. But I think I can find a way. Side project: might release some flashable kernels. We might then be ok to flash behind existing roms [also experimental]. This would meld our ramdisk with some other kernel(s)... Not breaking out any editors yet; trying to get lucky.
Rob
Not bad all that is needed now is overclocking kernel. I can add everything else I need.
Installed a2sd and gotten 133mb free and installed 20 apps and still have lots of free space. I'm keeping this on now.
Bluetooth connected to my laptop.
Seems as though mms isn't working too.
Reverted back to stock due to mms issues. Need mms for work. I did make a backup just in case somebody can tell me how to fix the mms issue. Other than that I FREAKING LOVE IT!!!!!!
Mms force closes anytime you try to add a picture. I also get the phone app fc sometimes on start up. But that one doesn't cause any call problems.
Sent from my HTC_A510c
So do I understand correctly that this ROM lacks HTC Sense?
jmcamos said:
So do I understand correctly that this ROM lacks HTC Sense?
Click to expand...
Click to collapse
It has the lock screen and some other small parts. But mostly, sense is gone.
Sent from my HTC_A510c
Rework
Guys:
Reworked this rom. Test it and tell me if you find anything broken. From what I've seen, Sense is back, its odexed, and seems to work. Thanks in advance.
Rob
PS I believe bt and mms will both work now.
insink71 said:
Test it and tell me if you find anything broken.
Click to expand...
Click to collapse
MMS is working. Camera/Flash work. Everything seems to work. I don't have any BT devices or else I'd test that, too. Will let you know if I run in to anything down the road. Seems good, though. Now to remove all this BLOAT.
---------- Post added at 04:44 PM ---------- Previous post was at 04:07 PM ----------
loveVII said:
MMS is working. Camera/Flash work. Everything seems to work. I don't have any BT devices or else I'd test that, too. Will let you know if I run in to anything down the road. Seems good, though. Now to remove all this BLOAT.
Click to expand...
Click to collapse
Installed DarkTremor's A2SD and No Bloat Free... Removed some bloat programs (Where, SCVNGR, etc) and then restarted my phone. Got stuck in a boot loop.
The first version [which I scrapped] was debloated, but I hacked out something neccessary or the deodex got me. Booted with no themes, no bt stack, no mms, etc. Be careful when you trim the hedges.
Rob
insink71,
You might try enabling the WiFi Hotspot (ie. WifiRouter.apk) in your ROM by changing the build.prop in the system folder,
ro.wifi.hotspotUI = 0
to
ro.wifi.hotspotUI = 1
Here are a few tweaks that I use you may want to try;
Code:
# Set Bootloader & Unlock Status as unknown
ro.lb = unknown
ro.bootloader = unknown
# Disable sending usage data
ro.config.nocheckin = 1
ro.config.htc.nocheckin = 1
profiler.force_disable_err_rpt = 1
profiler.force_disable_ulog = 1
# Disable Google location features
ro.com.google.locationfeatures = 0
ro.com.google.networklocation = 0
# Decrease dialing delay
ro.telephony.call_ring.delay = 0
# Disable blackscreen issue after call
ro.lge.proximity.delay = 5
mot.proximity.delay = 5
# Enable proximity sensor in call if you disable most Sense features
gsm.proximity.enable = true
# Smooths out reconnects
ro.mot.eri.losalert.delay = 1000
# Fix some application issues
ro.kernel.android.checkjni = 0
Force launcher into memory
ro.home_app_adj = 1
# Disable graphic dithering
persist.sys.use_dithering = 0
# Improve scrolling responsiveness
windowsmgr.max_events_per_sec = 100
# Improve overall touch responsiveness
debug.performance.tuning = 1
video.accelerate.hw = 1
# Disable Zygote loader
ro.wmt.blcr.enable = 0
# Increase heapsize for better performance
dalvik.vm.heapsize = 48m
would love wifi hotspot
Tera Tike said:
insink71,
You might try enabling the WiFi Hotspot (ie. WifiRouter.apk) in your ROM by changing the build.prop in the system folder,
ro.wifi.hotspotUI = 0
to
ro.wifi.hotspotUI = 1
Here are a few tweaks that I use you may want to try;
Code:
# Set Bootloader & Unlock Status as unknown
ro.lb = unknown
ro.bootloader = unknown
# Disable sending usage data
ro.config.nocheckin = 1
ro.config.htc.nocheckin = 1
profiler.force_disable_err_rpt = 1
profiler.force_disable_ulog = 1
# Disable Google location features
ro.com.google.locationfeatures = 0
ro.com.google.networklocation = 0
# Decrease dialing delay
ro.telephony.call_ring.delay = 0
# Disable blackscreen issue after call
ro.lge.proximity.delay = 5
mot.proximity.delay = 5
# Enable proximity sensor in call if you disable most Sense features
gsm.proximity.enable = true
# Smooths out reconnects
ro.mot.eri.losalert.delay = 1000
# Fix some application issues
ro.kernel.android.checkjni = 0
Force launcher into memory
ro.home_app_adj = 1
# Disable graphic dithering
persist.sys.use_dithering = 0
# Improve scrolling responsiveness
windowsmgr.max_events_per_sec = 100
# Improve overall touch responsiveness
debug.performance.tuning = 1
video.accelerate.hw = 1
# Disable Zygote loader
ro.wmt.blcr.enable = 0
# Increase heapsize for better performance
dalvik.vm.heapsize = 48m
Click to expand...
Click to collapse
Had wifi hotspot w/ Tmo and loved it; however, quick edit to build.prop netted me a bootloop Didn't try the other tweaks but I will. Wanted something as close to stock as I could get, and this is it [good or bad] with a2sd thrown in.
Rob
insink71 said:
Had wifi hotspot w/ Tmo and loved it; however, quick edit to build.prop netted me a bootloop.
Rob
Click to expand...
Click to collapse
Just curious how and what did you use to edit the build.prop file that you got the boot loop?
Root Explorer?
Yes root explorer; text editor.
Rob
Strange that's what I use and not a problem. What property did you modify?
just the wifi router
Tera Tike said:
Strange that's what I use and not a problem. What property did you modify?
Click to expand...
Click to collapse
;
Only
ro.wifi.hotspotUI = 0
to
ro.wifi.hotspotUI = 1
Doing some reading on cdma build.prop s now. Thanks for inspiring me to read; from cursory look it seems they can be quite different.
Rob
On the T-mobile GSM version the line, ro.wifi.hotspotUI is not in the build.prop file. You might just remove it all together. Just a thought....
Hello all,
I have flashed DARKSIDE.EVOLUTION.3 v7 and flashed with DARKSIDE.VENOM #3. My question is how do I manage my CPU OC/UV. any and all information will be greatly appreciated.
Thanks
Use System Tuner and hit the Voltage tab, then proceed to +/- 25 and change it from there
Prolly shudda stuck with one thread, I agree with shinigenEddy on system tuner.
Good morning ☺ ,
I've flashed custom ROM and added a custom kernel ( cleanrom 3.8.0 + glitch kernel r226 ) in order to overclock my N7 . I definetly see some improvements over the stock ROM and it got better ( at least in benchmarks ) but when i was tweaking the kernel with tricksted mod i found an option "Dynamic FSYNC" , I never saw it before so obviously i have on idea what it is . Should I leave it enabled or disable it ?? What do we use it for ?
Thank you ?
If i get it right 'dynamic fsync' disables linux file buffering when the device goes into sleep mode. I can remember on CM7 they said it helps preventing data loss when the device crashes during sleep.
But its still in nearly every custom kernel nowadays. To my understanding disabling async/buffering is a very bad thing on flash/eMMC memory as every single byte written leads to an 128KB (erase block size) write operation (much higher cell wear-out) whereas the standard behavior would buffer a specific data size or time (commit=5 seconds for ext4). Also, ext4 is backed by journaling so data loss shouldn't be a problem anymore on most situations. I'm wondering as well what the benefits/purpose of this mod should be these days.
Maybe @faux123 can shed some light?