[mod]choppy HD recording fix (maybe) - myTouch 4G Android Development

Inspired by this, this, this thread, as well as my own frame drops during recording.
Most agreed that the class of the sdcard did not effect the frame drops.
Not sure if anyone has tried this yet:
Code:
/system/etc/media_profiles.xml
Music in this vid is from the Pandora app running in the back ground, White balance = incandescent
Lighting was pretty low, and I did not touch the screen for it refocus while shooting.
YouTube's video info log showed every little frame drop compared to other vids I saw, my original 4000000 setting had even less. So maybe I will settle for 4400000?
This is the profile I used. per usual, YMMV. I haveStock ROM on diet/ stock Kernel/class2,8gb sdcard/32mb VM heap
I don't know what the quality 90/80/70 and the memCap do, if you know, please help.
Code:
[URL="http://forum.xda-developers.com/#"]-[/URL] <MediaSettings>
- <!-- Each camcorder profile defines a set of predefined configuration parameters -->
[URL="http://forum.xda-developers.com/#"]-[/URL] <CamcorderProfiles>
[URL="http://forum.xda-developers.com/#"]-[/URL] <EncoderProfile quality="[B]high[/B]" fileFormat="[B]mp4[/B]" duration="[B]60[/B]">
<Video codec="[B]h264[/B]" bitRate="[COLOR=Red][B]4800000[/B][/COLOR]" width="[B]720[/B]" height="[B]480[/B]" frameRate="[COLOR=Red][B]30[/B][/COLOR]" />
<Audio codec="[B]amrnb[/B]" bitRate="[COLOR=Red][B]4800[/B][/COLOR]" sampleRate="[B]8000[/B]" channels="[B]1[/B]" />
</EncoderProfile>
[URL="http://forum.xda-developers.com/#"]-[/URL] <EncoderProfile quality="[B]low[/B]" fileFormat="[B]3gp[/B]" duration="[B]30[/B]">
<Video codec="[B]m4v[/B]" bitRate="[B]256000[/B]" width="[B]176[/B]" height="[B]144[/B]" frameRate="[B][COLOR=Red]30[/COLOR][/B]" />
<Audio codec="[B]amrnb[/B]" bitRate="[COLOR=Red][B]4800[/B][/COLOR]" sampleRate="[B]8000[/B]" channels="[B]1[/B]" />
</EncoderProfile>
<ImageEncoding quality="[B]90[/B]" />
<ImageEncoding quality="[B]80[/B]" />
<ImageEncoding quality="[B]70[/B]" />
<ImageDecoding memCap="[B]20000000[/B]" />
<Camera previewFrameRate="[B]0[/B]" />
</CamcorderProfiles>
<EncoderOutputFileFormat name="[B]3gp[/B]" />
<EncoderOutputFileFormat name="[B]mp4[/B]" />
- <!-- If a codec is not enabled, it is invisible to the applications In other words, the applications won't be able to use the codec or query the capabilities of the codec at all if it is disabled -->
<VideoEncoderCap name="[B]h264[/B]" enabled="[B]true[/B]" minBitRate="[COLOR=Red][B]64000[/B][/COLOR]" maxBitRate="[COLOR=Red][B]4800000[/B][/COLOR]" minFrameWidth="[B]176[/B]" maxFrameWidth="[B]1280[/B]" minFrameHeight="[B]144[/B]" maxFrameHeight="[B]720[/B]" minFrameRate="[B][COLOR=Red]30[/COLOR][/B]" maxFrameRate="[B][COLOR=Red]30[/COLOR][/B]" />
<VideoEncoderCap name="[B]h263[/B]" enabled="[B]true[/B]" minBitRate="[COLOR=Red][B]64000[/B][/COLOR]" maxBitRate="[COLOR=Red][B]4800000[/B][/COLOR]" minFrameWidth="[B]176[/B]" maxFrameWidth="[B]800[/B]" minFrameHeight="[B]144[/B]" maxFrameHeight="[B]480[/B]" minFrameRate="[COLOR=Red][B]30[/B][/COLOR]" maxFrameRate="[COLOR=Red][B]30[/B][/COLOR]" />
<VideoEncoderCap name="[B]m4v[/B]" enabled="[B]true[/B]" minBitRate="[COLOR=Red][B]64000[/B][/COLOR]" maxBitRate="[COLOR=Red][B]4800000[/B][/COLOR]" minFrameWidth="[B]176[/B]" maxFrameWidth="[B]1280[/B]" minFrameHeight="[B]144[/B]" maxFrameHeight="[B]720[/B]" minFrameRate="[COLOR=Red][B]30[/B][/COLOR]" maxFrameRate="[COLOR=Red][B]30[/B][/COLOR]" />
<AudioEncoderCap name="[B]amrnb[/B]" enabled="[B]true[/B]" minBitRate="[COLOR=Red][B]4800[/B][/COLOR]" maxBitRate="[COLOR=Red][B]4800[/B][/COLOR]" minSampleRate="[B]8000[/B]" maxSampleRate="[B]8000[/B]" minChannels="[B]1[/B]" maxChannels="[B]1[/B]" />
- <!-- FIXME: We do not check decoder capabilities at present At present, we only check whether windows media is visible for TEST applications. For other applications, we do not perform any checks at all. -->
<VideoDecoderCap name="[B]wmv[/B]" enabled="[B]true[/B]" />
<AudioDecoderCap name="[B]wma[/B]" enabled="[B]true[/B]" />
</MediaSettings>
this one min 128000 max 4400000
fast motions low lighting
original profiles
this was the vid that really got me wanting to do something about the frame drops

Interesting. It does seem to be improved.... nice find!

I've been waiting for something like this!!!

Tried the following w/out any success.
First:
Video codec - bitRate cut in half to 4000000
Audio codec - bitRate lower to 9600
Then:
Video codec - bitRate cut in half to 15000000
Audio codec - bitRate lower to 9600

Forgot to mention i chnaged vm heap to 32m as will in build prop as well before all this. Fwiw Galaxy 4g is at 48m
[via XDA premium]

I'll try changing the vm heap and post again later or tomorrow.

What's the functionality of changing the vm heap size?
Rom: orange sense v1.01
Kernel: Faux .975 LV
Governor: Smartass
Recovery: CWM 3.0.0.6

Update: No luck, changed vm heap to 32m, and duplicated your bitrate settings no changes. I was hoping it'd work...
anyone else test this w/any success?

Look up vm heap tool on market, there is a short explanation on there.
[via XDA premium]

So lowering it to 32 will give better performance to the camera/ camcorder
Rom: orange sense v1.01
Kernel: Faux .975 LV
Governor: Smartass
Recovery: CWM 3.0.0.6

markjnj said:
I'll try changing the vm heap and post again later or tomorrow.
Click to expand...
Click to collapse
Edit, try 50fps.
[via XDA premium]

Well. I just tried 50fps. Seems to shoot fine.
*edit, changing the fps does not make it shot any higher fps according to YouTube video info log.
[via XDA premium]

Ok, i reverted the bitRate to 8000000 correct me if that is not the stock setting. And used 50fps, shot 2 vids and Wow.
But for the sake of file size, i will be lowering the bitRate to prob 4800000 rage. But i think the fix is upping the fps.
[via XDA premium]

Edit: I thought that was it. but I think for mine bitrate was at 30000000 stock...I don't even remember anymore. Let me try changing fsp to 50. btw, are you running custom kernel? wondering what you're running at. I'm using faux latest build.
mine stock had bitrate of video 30000000 and audio 12200
I think i realized why I may have been getting choppiness after changing the settings. I forgot that I was underclocking... :X
Anyway. I'm currently got video bitrate at 15000000 and audio still at 12200. I've been taking a few test videos at 1.3mhz max. no freezing yet. will try a more videos throughout the rest of the day and keep you posted.

Where is the profile for HD 720p I only see high and low
Rom: orange sense v1.01
Kernel: Faux .975 LV
Governor: Smartass
Recovery: CWM 3.0.0.6

@mark. Nope stock rom/kernel /sdcard. 32mb vm heap
kyokyle said:
Where is the profile for HD 720p I only see high and low
Rom: orange sense v1.01
Kernel: Faux .975 LV
Governor: Smartass
Recovery: CWM 3.0.0.6
Click to expand...
Click to collapse
Just few lines down from the high low
{
"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"
}
[via XDA premium]

It doesn't seem to change. When I open up in windows and checked the the recorded file. Fps is still 20 even though I changed max to 50 and min to 30. I restarted my phone too
Rom: orange sense v1.01
Kernel: Faux .975 LV
Governor: Smartass
Recovery: CWM 3.0.0.6

Anything after the camcorder profile tag doesn't affect camcorder I think
Rom: orange sense v1.01
Kernel: Faux .975 LV
Governor: Smartass
Recovery: CWM 3.0.0.6

sleepyfu said:
@mark. Nope stock rom/kernel /sdcard. 32mb vm heap
Just few lines down from the high low
[via XDA premium]
Click to expand...
Click to collapse
ok, did you change anything under high? I kept entries under high at default w/the exception of changing the fps to 30 there.
and now all the entries below that for the different sizes I have matching yours. So far so good vm heap 32.

kyokyle said:
It doesn't seem to change. When I open up in windows and checked the the recorded file. Fps is still 20 even though I changed max to 50 and min to 30. I restarted my phone too
Rom: orange sense v1.01
Kernel: Faux .975 LV
Governor: Smartass
Recovery: CWM 3.0.0.6
Click to expand...
Click to collapse
Interesting, i never check it with other software. It should have been at least 30 since that's default if by editing the xml didnt change anything. I do notice the files sizes being smaller so the xml has direct effect to the cam. Asides from the possible false fps, hows is the recording part? Still dropping frames like it used too?
@mark, in the 'high' profile i have lowered the bitRates(vid+aud) and 50fps. "online hd 10min" is what it effects.
[via XDA premium]

Related

[APP][24Nov] - 4.9 - SGS1+2] Voltage Control - control OC/UV for OC kernels

I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
4.9 - THIS IS HIGLY TEST RELEASE
+ Profiles support
+ Bus frequency switching for Siyah kernel
+ Widget with profile switcher and app launcher (passive!)
+ Recovery instructions: lets you place CWM flashable boot settings deleter
+ CPU history: now can reset and refresh graphs
+ Root detection improvement (I hope...)
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ More than two profiles
+ CPU History page
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"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"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
- Siyah kernel interfaces (Charging current and GPU OC/UV)
- device info page
- (extreme) CPU usage history page
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot
3.0.1 - OLD version;
Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.
Thanks for this app! it's a nice tool. Once feature request for the OP would be an explanation of the different schedulers. I'm using noop after some research.
Edit: I guess it would be an OP request, not a feature request.
curious, may i ask what is the difference between noop, anticipatory, deadline, and cfq?
Just search it on wikipedia.
It seems noop is the best with flash memory.
Sent from my GT-I9000 using XDA App
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.
Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works
oswade said:
Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works
Click to expand...
Click to collapse
YA-OK is not using my UV code hence this app wont work. he hardcoded the UV values if im not wrong
Lio78 said:
Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.
Click to expand...
Click to collapse
I use the same kernel and same settings but all i get when i open this app is a black screen and the su popup. Is there something else i have to setup so that app will work?
May it have something to do with setcpu?
An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.
ggonzalez7777 said:
An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.
Click to expand...
Click to collapse
I've been on 0, 25, 50, 75, 100, 100 on 1.2 Ghz - its been stable for "normal" use - but i dont stress it out with video/ 3D etc - so YMMV.
New version posted, first post updated.
nice bro!
one suggestion: add checks so it wont show blank screen if the values are not read properly or folders/file not found and display messages
sometimes peeps run a wrong kernel and expect your app to work
Which version is better for SetiroN's 1.2 kernel?
Will look into it, most of checks are there, but I might have forgotten about some
MikeyMike01 said:
Which version is better for SetiroN's 1.2 kernel?
Click to expand...
Click to collapse
As of today: 1.61. Both use old UVLF and UVHF implementation.
0 50 100 75 75 125 seems to be working here
Alright... I wont upgrade then.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
DataInputStream osRes = new DataInputStream(process.getInputStream());
BufferedReader br = new BufferedReader(new InputStreamReader(osRes));
res.add(br.readLine() + "");
br.close();
Click to expand...
Click to collapse
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.
xan said:
Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.
Click to expand...
Click to collapse
Glad you know of this issue, on my captivate the older version works fine but when upgrading to the new one it is stuck on the black screen forever. It says SU permission granted but just stays on the black screen. I tried uninstalling the old first, rebooting, then installing and also just overwriting the old with new. Nothing but black.
Good luck on the fix, this is a very handy app
loco- said:
Just search it on wikipedia.
It seems noop is the best with flash memory.
Click to expand...
Click to collapse
I agree, here are a couple of comments that convinced me:
You want to use noop scheduler on devices where there are no seeking penalty, such as flash drives. That's why USB stick wants noop. Unfortunately, harddisks are very mechanial beasts and their performance is highly controlled by their seeking abilities. All these schedulers above are really trying to figure out how to extract maximum performance off the harddisk without causing bad behaviour in other cases.
noop is often the best choice for memory-backed block devices (e.g. ramdisks) and other non-rotational media (flash) where trying to reschedule I/O is a waste of resources.
http://www.linuxhowtos.org/System/iosched.htm
http://stackoverflow.com/questions/1...-i-o-scheduler
Click to expand...
Click to collapse
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.
Click to expand...
Click to collapse
When I installed the new version 1.97beta, it too sat at a black screen for an unusually long time, then after almost a minute, the supperroot permission screen poped up, I granted it root rights, and then voltage control came up fine.
Hm, read first post.
xan said:
Hm, read first post.
Click to expand...
Click to collapse
Umm, what post is this comment directed to?
Unclear what topic, and what in the first post we are looking for?

[KERNEL] GALAXIAN [344MB][JVU][Voodoo Sound][EXT4][BLN][COLOR]

{
"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"
}
*
Galaxian kernel was made to improve your Galaxy S usage experience.
If you are looking for fast and stable kernel, this one is for you!
Why Galaxian?
Based on latest source from Samsung Open Source Release Center and always latest initramfs
344MB RAM memory without side effects like loosing HD capabilities
EXT4 and RFS support with autodetection
ClockWorkMod Recovery v3.0.0.5
Ondemand governor with tweaked up/down scaling
Voodoo Sound v10
Slightly increased charging current limits for both AC and USB charging modes
Improved touch sensitivity
Front camera is working (no snapshot when recording support)
Video calls are working
Modules compiled with -O2 flags
LZMA kernel compression, GZIP initramfs compression
Low Memory Killer levels are just perfect
Unbelivable colors and sharpness
Brightness levels are now fixed (no more red tint on each)
Fixed MDNIE profiles (outdoor mode can now work together with selected color temperature).
Light sensor driver fine tuned
WiFi driver buffer is now bigger
New jpeg compression mode from Galaxy TAB
Read A Head parameter increased to 512KB
BLN support
Optimized compile flags
CPU clock speed switch is now faster
Custom bootanimations support! just name yours as sanim.zip and place in /system/media/
Minor tweaks
Where to get it?
Click here!
How to apply?
Please use Odin and choose Galaxian....tar in PDA section (without pit file, repartition or bootloader update!)
Want to convert your RFS -> EXT4?
There are two simple ways to do that:
Use Chainfire's EXT4 Tools (ignore warning message)
Use Galaxian ROM which will do that for you automatically
Any sources?
Click here!
I would like to say thank you to everyone
who helped me with this project!​
*Logo is a trademark of NAMCO BANDAI.
let's see how it works
Edit: Great kernel, best one for StockRoms.
WoooHooo what a Features
nyc one Brother
nice!
will try it out
is there a jvh edition?
No but can be if community want to
Do I disable lagfix before flashing the kernel?
is there any way you could implement voodoo color in this kernel ?
fuzzvirus said:
Do I disable lagfix before flashing the kernel?
Click to expand...
Click to collapse
No! There is autodetection system build-in! Kernel boot's up with RFS and EXT4.
reneimas said:
is there any way you could implement voodoo color in this kernel ?
Click to expand...
Click to collapse
No, sorry, I've tried voodoo colors and I'm not happy how it performs. Check this version, I've applied Speedmod color fix with my own changes, all is sharp and vivid.
Lukiqq said:
No, sorry, I've tried voodoo colors and I'm not happy how it performs. Check this version, I've applied Speedmod color fix with my own changes, all is sharp and vivid.
Click to expand...
Click to collapse
I am using your kernel right now. The colours are not bad but still wish i could control the contrast through the voodoo app. P.s does this kernel automatically converts everything to EXT4 or is it manual because weirdly i get really rubbish quadrants scores on [F1 Galaxy S2 V3.1] rom :/
Nice.
Couple of things to note, OC WILL freeze on some phones, including mine... every phone is different.
Ondemand sample rate of 40000 may cause music to stutter and will need to be raised to something like 60000+.
Nice work though.
features look good i want to try right now
lpy said:
Nice.
Couple of things to note, OC WILL freeze on some phones, including mine... every phone is different.
Ondemand sample rate of 40000 may cause music to stutter and will need to be raised to something like 60000+.
Nice work though.
Click to expand...
Click to collapse
Thank you! I've tested it on 3 phones and didn't noticed any problems with OC, but you have right, things may happen. If so, tell me, I'll tune some voltage values.
reneimas said:
I am using your kernel right now. The colours are not bad but still wish i could control the contrast through the voodoo app. P.s does this kernel automatically converts everything to EXT4 or is it manual because weirdly i get really rubbish quadrants scores on [F1 Galaxy S2 V3.1] rom :/
Click to expand...
Click to collapse
Read carefully 1st post There is something about EXT4, even attached apk to do so.
on my phone neocore and quadrant shows 48-49 fps only. but quadrant is around 3300
if i have lagfix enabled can flsah it?
Lukiqq said:
Thank you! I've tested it on 3 phones and didn't noticed any problems with OC, but you have right, things may happen. If so, tell me, I'll tune some voltage values.
Click to expand...
Click to collapse
Unfortunately, raising/tuning voltages can sometimes make things more unstable. Some CPU's simply can't handle it no matter what you do. That's just my experience though, we'll see how it goes for others.
mar90 said:
on my phone neocore and quadrant shows 48-49 fps only. but quadrant is around 3300
Click to expand...
Click to collapse
Neocore 64.5
Quadrant, tunnel test about 520 points, overall result as I've said in description.
the spica master from samdroid.net come back to here ..hhe..
i'll test your kernel..
Sent from my GT-I9000 using Tapatalk

[KERNEL]Lightning Zap *OC/UV* (Updated 1/9/13)

{
"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"
}
Krazeecracker, Thomas.Raines and Team Fah-Q! presents
The Lightning Zap! kernel for the Hercules
ATTN:
I Krazeecracker, thomas.raines, Team Fah-Q!, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise screw up your device.
I revamped the Lightning Zap! kernel across the board. Since I have so many of them I was loosing where I was on each one. So I have now broken it down into 3 phases:
Phase 1: Introduction of LZ kernel to device
Phase 2: Fine tuning of tweaks, values, etc
Phase 3: Implementation of OC/UV
Phase 4: Continue updating and adjusting as necessary
From now on I will name the .zip accordingly as well:
Sky_p2.1
On a good note, I think this latest update will finalize phase 2 and now I can work on OC/UV...
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Instructions:
Make a backup
Download LightningZapv1Sky.zip to PC
Transfer LightningZapv1Sky.zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Phone will automatically reboot after install**
Wait 10 minutes
Enjoy the Lightning Zap!
ATTN!
If you are currently on any version of Lightning Zap! kernel, you must either replace your build.prop from your ROM or re-flash your current ROM. Or you can open your build.prop with a text editor and delete all lines below the Lightning Zap Tweaks entry.
This kernel was tested on ParanoidAndroid. This kernel and tweaks will work with any version of CM10 post 14OCT.
**First boot, especially after a fresh install of your ROM (wipe system cache etc, flash ROM gapps Lightning Zap) will take a while. It will seem to hang between a blank screen (which use to be the 2nd boot splash) and the boot animation. There is no need to panic. Everything is fine. It is the vacuum script trying to clean databases that have yet to be created. After first boot, your phone will boot as normal (a little faster actually)...
After first boot, ensure your I/O scheduler is set to cfq and your governor is set to ondemand to gain the maximum benefits of Lightning Zap!
See 3rd post for further instructions on improving and customizing your Lighting Zap! experience.
Source Code:
msm8660-common_lz_kernel
vendor_lz-kernel.git(scripts and zipalign binary)
Special thanks to:
gs2usr for the link to source code...
xan for Voltage Control app
Download links and changelog
Downloads and changelog
Sky_p3.2-1.zip
Vibration fixed thanks to tmob.
Sky_p3.2.zip with rotation fix included
Skipped 3.1 because it was incomplete
Added userspace voltage control (You can now use an app or script to control your voltage. I tested with Voltage Control (preferred) and Antutu CPU Master)
For badass battery life, I am using noop io-scheduler, Lionheart governor, underclocked at 1026Mhz, and globally dropped voltage by -100mV
Deep sleep is working right again (doesn't take forever for it to enter ds)
Leaned up thread and removed old versions. They are gone for good so please don't ask...
Sky_p3.0.zip
Fixed the ability to set max/min cpu frequency. Thanks to car vs driver for pointing me in the right direction
Added OC/UV from flappjaxxx h0tcakez kernel source
Fine tuned ondemand governor
Archived changelog
Plans:
I want to trim down the oc frequencies. I think that 29 is just too much. I also want to cut back on the governors and io-schedulers. There are so many to choose from and everyone has their preferences. How bout some feedback in the general scetion here
Enjoy the Zap!
More tips and tricks
This is already included but left for reference.
The governor tweak is set for a fairly balance of performance and battery life. If you find yourself needing battery life over performance, you can make some minor changes. Here's how:
1 Download Script Manager from the market (it's free)
2 Open Script Manager and navigate to /system/etc/init.d
3 Press menu/more/advanced options and select mount as RW
4 Select 01governor and select "edit" at the top (this will open the file in atext editor)
5 Uncomment (remove # in the particular line) and change:
Code:
echo "45" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
To:
Code:
echo "[COLOR=red]70[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
6 Select menu/save
7 Press the skull and cross bones icon at the top (this will allow Super User)
8 Press run, close app and enjoy
This will result is slightly slower performance but higher battery life.
If you want even better battery life:
1 Following steps 1-4
2 Add a # at the begining of lines 11 to 19
3 Scroll to "pwoersaver" section
4 Remove the # at the begining of lines 28, 30-38 and 43
Code:
#AWAKE_GOVERNOR="ondemand"
#SLEEP_GOVERNOR="ondemand"
# echo "70" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
etc
Code:
AWAKE_GOVERNOR="powersaver"
#SLEEP_GOVERNOR="powersaver"
echo "20000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate;
5 Follow steps 6-8 (no need to select super user icon if you already did)
This will result in lower performance, but ultimate battery life
When running in a higher performance mode (especially for gaming) you can disable powersave_bias by changing the 1 to a 0 like this:
Code:
echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
echo "[COLOR=red]0[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
Powersave_bias only allows the CPU to peak for small increments at a time, and not allow the CPU to remain peaked even when the system calls for it. In gaming, that could result in choppy, laggy perofrmance and slow FPS..
Although it says not to in the script, you can change the sampling rate as well. Do not go below 50000. I left it at 57500 as I found this seems good setting for smooth scrolling and performance.
Code:
echo "[COLOR=Red]57500[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate;
Always leave SLEEP_GOVERNOR="powersave" uncommented (no #) and do not uncomment any other SLEEP_GOVERNOR as this will keep ultimate battery save while screen is off.
Only change values in increments of 5 for the up_threshold.
This is already included but left here for reference.
Source code tips
Needs updating.
just add this to your local_manifest.xml:
Code:
<remote fetch="https://github.com/TeamFahQ" name="LZkernel" />
<project name="msm8660-common_lz_kernel.git" path="samsung/msm8660-common" remote="LZkernel" revision="jellybean" />
<project name="vendor_lz-kernel.git" path="vendor/lz-kernel" remote="LZkernel" revision="master" />
Then add this to your cm.mk file i your device directory:
Code:
# adding Lightning Zap tweaks to build
$(call inherit-product, vendor/lz-kernel/lightningzap.mk)
And don't forget to remove the kernel entry in your cm.dependencies found in your device directory...
First! This should be fun...
Sent from my Nexus 7 using xda app-developers app
Nice... If only it had OC/UV... the dev said he would add it later.
Nice, but I have to admit this is quite confusing for me to read, a lot of stuff. (I'm ADHD)
TheLastSidekick said:
Nice, but I have to admit this is quite confusing for me to read, a lot of stuff. (I'm ADHD)
Click to expand...
Click to collapse
Lol, basically just flash with the rotation fix and your good to go. If you have the need for more juice then follow the third post. And fourth is for adding to an existing ROM your going to build, i.e. your kangs
Wait so this is the same as the one on skyrocket? So we still need rotation fix?
Sent from my All-Starred P.A.C SGH-T989
ArcticFish said:
Wait so this is the same as the one on skyrocket? So we still need rotation fix?
Sent from my All-Starred P.A.C SGH-T989
Click to expand...
Click to collapse
Correct lol
Couldn't you just merge the rotation fix zip and the kernel together? It would make things easier in a sense.
Shmi117 said:
Couldn't you just merge the rotation fix zip and the kernel together? It would make things easier in a sense.
Click to expand...
Click to collapse
done!
Thanks! I'll be sure to incorporate your kernel in an upcoming build dedicated to battery life!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
https://www.dropbox.com/s/vofmxdvp1mbuqkp/SkyLZv3.zip rotation fix included and now in OP!
Pardon me if I missed it, but is this kernel for Jelly Bean or Ice cream sandwich? Thanks.
GreggoryD502 said:
Pardon me if I missed it, but is this kernel for Jelly Bean or Ice cream sandwich? Thanks.
Click to expand...
Click to collapse
Jellybean only
I am currently on all-star ROM and on speed test the download is about 1mb slower but the upload was about 1.5mb higher on my network. I also notice the vibration isn't as strong is that me or does it have to do with the kernel as for battery I'm not sure yet. Thanks
Sent from my SAMSUNG-SGH-T989 using xda premium
Flashed on Dec 1 AOKP nightly.. working good so far.. thanks!!!
Sent from my Jellylicious T989
Running now, thanks man! Gonna run a full cycle tomorrow and will report back on battery
droidz79 said:
I am currently on all-star ROM and on speed test the download is about 1mb slower but the upload was about 1.5mb higher on my network. I also notice the vibration isn't as strong is that me or does it have to do with the kernel as for battery I'm not sure yet. Thanks
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Vibration is fine on my end. And its also sleeping like a baby. And running it through the yes yesterday before posting it ran comparable to kko! :thumbup:

[FIX] Speaker playback distortion solution (CM11/AOSP 4.4 only)

Hi! this fix is for AOSP/CM android 4.4.2 roms only (root required)
It fixes speaker distortion occurring on loud playback. What it does it applies high pass filter on the lower frequencies that a speaker so small cant really playback anyway. Enough lower frequencies still come through so playback sound is good.
edit /system/etc/mixer-paths.xml
scroll / search for the "speaker" path
add this before the closing line of the speaker path:
<ctl name="RX7 HPF cut off" value="MIN_3DB_150Hz" />
same can be applied to "voice-speaker". it will give a slightly better speakerphone quality.
its gonna look like this:
Code:
<path name="speaker">
<ctl name="SLIM RX1 MUX" value="AIF1_PB" />
<ctl name="SLIM_0_RX Channels" value="One" />
<ctl name="RX7 MIX1 INP1" value="RX1" />
<ctl name="RX7 Digital Volume" value="67" />
<ctl name="SPK DRV Volume" value="6" />
<ctl name="SPK DAC Switch" value="1" />
<ctl name="RX7 HPF cut off" value="MIN_3DB_150Hz" />
</path>
reboot to recovery, clear cache&dalvik, reboot system.
i've included a flashable zips with a moded mixer paths file taken from CM11. it can be flashed on any CM11/AOSP/AOKP rom. although backup of the original file is recomended as the devs could apply their own tweaks or changes to this file.
so sometimes its better to edit it manualy.
initial-just HPF applied to speaker
v1.1 - has the seam HPF tweak applied to speakerphone + set vol 70 to speakerhpone
v.1.1.louder- well guess. (speaker 70, speakerphone72)
i dont recommend using the louder or even values beyond that.. as it may damage your speaker
i am on rom cloudyflex 1.3 and there is no such file.
however, what exactly does that command?
noris08 said:
i am on rom cloudyflex 1.3 and there is no such file.
however, what exactly does that command?
Click to expand...
Click to collapse
oh yeah.. forgot about LG roms.. this is AOSP/CM only.
it just cuts off the low frequencies which such a small speaker has most trouble playing.
It works great!
thanks man, I suggest to submit this fix to cyanogenmod repository so it can be included into the official rom
in the meantime, is it possible to have this fix in a flashable zip from recovery? it would be very handy when you flash new builds (so you don't have to manually edit the file each time)
provolinoo said:
thanks man, I suggest to submit this fix to cyanogenmod repository so it can be included into the official rom
in the meantime, is it possible to have this fix in a flashable zip from recovery? it would be very handy when you flash new builds (so you don't have to manually edit the file each time)
Click to expand...
Click to collapse
I'll look into it...meanwhile you can just save the file and copy it over, or replace the one in zip. Will have to check sometimes though if the file gets changed in any way by cm.
Sent from my LG-D802 using Tapatalk
darkobas said:
I'll look into it...meanwhile you can just save the file and copy it over, or replace the one in zip. Will have to check sometimes though if the file gets changed in any way by cm.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thanks a lot
btw, editing the same file, line
<ctl name="RX7 Digital Volume" value="88" />
could be useful to increase maximum volume
so we could create a fix for distorsion+volume
noris08 said:
i am on rom cloudyflex 1.3 and there is no such file.
however, what exactly does that command?
Click to expand...
Click to collapse
for cloudyflex you want to go to system/etc/snd_soc_msm and open the file called snd_soc_msm_Taiko.
freebee269 said:
for cloudyflex you want to go to system/etc/snd_soc_msm and open the file called snd_soc_msm_Taiko.
Click to expand...
Click to collapse
i have 3 files named:
- snd_soc_msm_Taiko
- snd_soc_msm_Taiko_revA
- snd_soc_msm_Taiko_revB
1. i have to edit just the first one, right?
2. all i have to do is to add the same line like in the first post?
3. where do i add it?
thank you!
noris08 said:
i have 3 files named:
- snd_soc_msm_Taiko
- snd_soc_msm_Taiko_revA
- snd_soc_msm_Taiko_revB
1. i have to edit just the first one, right?
2. all i have to do is to add the same line like in the first post?
3. where do i add it?
thank you!
Click to expand...
Click to collapse
yes it's the first file that doesnt have _rev after it. you put it in the same spot as the OP mentioned.
freebee269 said:
for cloudyflex you want to go to system/etc/snd_soc_msm and open the file called snd_soc_msm_Taiko.
Click to expand...
Click to collapse
I was unaware flex roms had this problem too. So is this confirmed working? Can i add in op or was this fix for flex already listed somewhere?
Sent from my LG-D802 using Tapatalk
darkobas said:
I was unaware flex roms had this problem too. So is this confirmed working? Can i add in op or was this fix for flex already listed somewhere?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
i dont have a distortion problem on my cloudyflex. i was just helping out the person that wanted to try this.
freebee269 said:
yes it's the first file that doesnt have _rev after it. you put it in the same spot as the OP mentioned.
Click to expand...
Click to collapse
the file is way to complicated for me. i have no ideea where to add that line, i am totaly lost
if there isn't too much trouble, can you post a screen shot with the exact position where that line should be added?:angel:
thank you very much!
noris08 said:
the file is way to complicated for me. i have no ideea where to add that line, i am totaly lost
if there isn't too much trouble, can you post a screen shot with the exact position where that line should be added?:angel:
thank you very much!
Click to expand...
Click to collapse
{
"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"
}
Sent from my LG-D802 using Tapatalk
this is strange
my snd_soc_msm_Taiko file doesn't look like yours,
i have no <path name=....>. nowhere!
noris08 said:
this is strange
my snd_soc_msm_Taiko file doesn't look like yours,
i have no <path name=....>. nowhere!
Click to expand...
Click to collapse
Are you sure you have distortion? I have not heard of this on 4.2.2 lg roms.
My fix is not tested on taiko as I don't use it.
But it probably already looks something like this.
Sent from my LG-D802 using Tapatalk
Finally I'm no more ashamed when my speaker plays a song on full volume. Really sounds better. At least less distortion. Thank you very much!
darkobas said:
Are you sure you have distortion? I have not heard of this on 4.2.2 lg roms.
My fix is not tested on taiko as I don't use it.
But it probably already looks something like this.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
that is exactly how my file looks
maybe i understand this wrong
i have a slight distorsion during calls, for some voice speaking frequencies and i thought this is a solution for that (i was thinking to replace my headset speaker)
if this is not the case, then please disregard all my previous posts
noris08 said:
that is exactly how my file looks
maybe i understand this wrong
i have a slight distorsion during calls, for some voice speaking frequencies and i thought this is a solution for that (i was thinking to replace my headset speaker)
if this is not the case, then please disregard all my previous posts
Click to expand...
Click to collapse
Nope sorry.
darkobas said:
Hi! this mod is for AOSP/CM roms only
anyone with distorted speaker on high volume can try this: (root only)
edit /system/etc/mixer-paths.xml
scroll / search for the "speaker" path
add this before the closing line of the speaker path:
<ctl name="RX7 HPF cut off" value="MIN_3DB_150Hz" />
reboot to recovery, clear cache&dalvik, reboot system.
Click to expand...
Click to collapse
very nice, under review for NamelessROM right now , hit me back a PM with your email so I can give you proper credit for this :good:

[MOD][DEV] Enhanced Camera & Audio

Right now i'm doing some research to make some improvements on Camera and Audio to our device.
Things i've done so far:
Code:
[LIST]
[*][COLOR="Red"]V2[/COLOR]
[*]Enabled AGC
[*][COLOR="Red"]V1[/COLOR]
[*]Doubled to 320kbps with stereo audio encoding (Recorded videos, whatsapp and probably any other app that record sound will get crystal clear audios, caution with your data usage. Doubled encoding means doubled size)
[*]Doubled to 20 Mbit/sec video encoding 720p
[*]Bumped to 99% JPEG
[/LIST]
To do list:
Force 1080p recording (it has no affect playing with media_profiles.xml yet)
AGC - Automatic Gain Control (if you record something very loud like a concert, the sound will get very ****ed up)
What I know:
Motorola has disabled AGC for some reason I don't know. If you look at audio_effects.conf you'll find some Dolby code and AGC, AEC and NS as commentaries.
AGC, AEC and NS relies on pre_processing and libaudiopreprocessing.so, which wasn't declared on the file in first place.
The sensor has 1080p capabilities (pipeline and everything), since we share the same camera module as Nexus 5. I believe we can fine tune some stuff with the camera apk. For now I want to try this first to later research with libs/drivers.
I've managed to decompress the APK file but i have no idea how to decompile DEX, ARSC and the XML files (are XML compressed/obfuscated? It wasn't readable).
Can someone enlight me over?
Flash at your own risk.
Tested on CM12.1
Stock not tested yet
The audio graphs i've analyzed with and witouth the mod seems that AGC is on(maybe with a very moderated preset). Can someone try to record a video on a very loudly place?
sky0165 said:
The audio graphs i've analyzed with and witouth the mod seems that AGC is on(maybe with a very moderated preset). Can someone try to record a video on a very loudly place?
Click to expand...
Click to collapse
With stock 5.0.2 camera and libs or cm12.1 camera? (I'm on my way to an edm rave party lol jk)
Sent from my Moto G 2014
Great work!
Can someone post some pictures/videos for comparison vs stock?
RAW support for the camera would be amazing as well.
I believe it works from 4.4 KK to 5.0.2 and CM 12.1.
I'll post something to compare with later.
If someone help me to understand and manipulate DEX ARSC and those weird XML i would be very happy
i think it's not possible, but maybe add camera2 api is possible?
Please mention if this mod is for stock rom or it will work on any rom...
I noticed an improvement in the quality of camera friend
Hi all, can confirm this works on stock 5.0.2, no bootloops, audio quality REALLY impressive, as for AGC, I tried screaming into the mic a couple times and there was no audio distortion, I still need to check out the increased video bitrate, but it looks really sweet, thank you, keep up the awesome work, really looking forward to 1080p video working on this device
Anyone tried this on a CM rom?
Here remains the same resolution, I am in rom AICP
emistery said:
Anyone tried this on a CM rom?
Click to expand...
Click to collapse
OP says that it's been tested on CM 12.1 and users have reported it also working on stock moto.
TheLS said:
Here remains the same resolution, I am in rom AICP
Click to expand...
Click to collapse
Resolution still the same (8MP). What was changed was the post-processing compression to 1%.
sky0165 said:
Resolution still the same (8MP). What was changed was the post-processing compression to 1%.
Click to expand...
Click to collapse
How can you increase camera's resolution more than hardware specs?
wifestealer said:
How can you increase camera's resolution more than hardware specs?
Click to expand...
Click to collapse
That's not possble for photos, but the video resolution could theoretically be increased from 720p (aprox. 0.9 Megapixels) to 1080p (2MP).
Is there a way to enable recording with 60 frames per second? I would also like to see some comparison pictures/videos if possible.
uiuiuiui said:
That's not possble for photos, but the video resolution could theoretically be increased from 720p (aprox. 0.9 Megapixels) to 1080p (2MP).
Is there a way to enable recording with 60 frames per second? I would also like to see some comparison pictures/videos if possible.
Click to expand...
Click to collapse
Hmmm i don't think so, not without messing with the .so files.
In low light conditions out device records at 15 FPS to increase sensor exposure to compensate the light. In sunny conditions it records at 30.
I've been trying to decompile the lastest moto camera but it seems i can't find some portion of the code. I'm still trying to understand how those stuff works and how Android manage and rely in things.
I'll reserch some more about decompiling/recompiling APK and .so files.
Just a quick update:
{
"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"
}
Obviously, it doesn't work. My guess is: Sensor DOES support and app detects it, but libs don't.
Here's a logcat while trying to record something. "Cannot start vídeo capture. Another app may be using the mic" is the error.
https://www.dropbox.com/s/t7ed8cuzr6bpqk0/snp_log.txt?dl=0
Well, this is far beyond my skills.
@sky0165
Grt work dude...i just flashed.....drastic change in audio....
Rom- euphoria
---------- Post added at 01:02 PM ---------- Previous post was at 12:49 PM ----------
One more thing how to uninstall this zip if i dont want it....pls provide a uninstaller zip flashable
@op
Hi OP, is it possible to integrate the libs and drivers from the Snapdragon 410 MSM8916? If yes, its possible to port it from the Moto G3...
I flashed this MOD on Candy Rom and my themes stopped working, not sure why, now I can't install any theme; is there a way to revert the changes? Thanks!

Categories

Resources