Related
I want to try the Xtreme kernel, but I refuse to go back to non-Voodoo and the blue tint/fuzzy text of the Epic display. I realize there may be future kernels that I want to try that also do not have the Voodoo Color fix and I don't want to bother devs with my personal requests.
How hard is it to add the Voodoo Color patch to a kernel? I have basically no coding experience with Linux but I would be willing to learn a little if it is doable for a noob like me (I taught myself some PHP, MySQL and Apache so I'm not completely hopeless with computer languages).
If this is an unrealistic goal please let me know. Otherwise if anyone could help or point me in the right direct it is much appreciated! Thanks
hey i was just wondering what your voodoo settings are, cause when applied i thought that it only worked when you had brightness at 100%, so is yours at 100% all the time?
I believe that was for an older version of Voodoo. The latest should work at any setting.
Sent by a little green robot
ragnarokx said:
I want to try the Xtreme kernel, but I refuse to go back to non-Voodoo and the blue tint/fuzzy text of the Epic display. I realize there may be future kernels that I want to try that also do not have the Voodoo Color fix and I don't want to bother devs with my personal requests.
How hard is it to add the Voodoo Color patch to a kernel? I have basically no coding experience with Linux but I would be willing to learn a little if it is doable for a noob like me (I taught myself some PHP, MySQL and Apache so I'm not completely hopeless with computer languages).
If this is an unrealistic goal please let me know. Otherwise if anyone could help or point me in the right direct it is much appreciated! Thanks
Click to expand...
Click to collapse
The patch is super simple to apply. However, Devin is a good friend of mine, and right now I think the only thing XTreme has on MixUp is 1.6Ghz OC and I already have that in my tree. I also have some VooDoo Sound goodies, and a few other tweaks/fixes. I should be releasing tomorrow, if you can hold out. If not, just use XTreme. It's a good kernel.
Thanks gd! I've always been a fan of your work. Good to know you are releasing an update soon.
That definitely solves my short-term problem. But as long as I have this thread, I would still like some help on how to apply Voodoo to a kernel. There may be some super-awesome kernel that comes out in a week that doesn't have Voodoo, and I'd really like to be ready
I have tried a few kernels and I have never seen any blue fuzzy text....what is that you guys talk about?
This link should explain everything.
ragnarokx said:
This link should explain everything.
Click to expand...
Click to collapse
They really need to take real screenshots, not simulations.
The only thing I've really seen is that text does seem a bit oversharpened, but I haven't seen any of the other problems (at least not to the extent they claim)
Firon said:
They really need to take real screenshots, not simulations.
The only thing I've really seen is that text does seem a bit oversharpened, but I haven't seen any of the other problems (at least not to the extent they claim)
Click to expand...
Click to collapse
Well, it won't show in screenshots, because then it'd take on the tint of whatever screen you view it on.
You don't notice the blue unless your used to a properly calibrated screen. If you have access to one, hold your phone up next to it with both on a totally white screen. It's VERY obvious. Also, youre really unlikely to see the text issues until you see how it should look, then its clear.
The problem with screenshots is that they don't reproduce the same colors as your screen. A photo suffers the same problem, as the camera's CCD doesn't genuinely reproduce the colos you see either.
Until display technology improves a bit simulated screens are the best way to explain the effect - the intention was likely never meant to be "looks exactly like this".
My screen has a noticable blue tint (to me at least), but nowhere near the exaggerated screeshots on the voodoo page.
Voodoo should be easy to roll into a flashable patch.. when I have some free time I'll dig at it unless someone else has done so already.
[Edit] Also worth noting, if you're viewing those simulations on your epic, the blue you see might be oversaturated
Looking again at the voodoo page, there is already an udpate.zip flashable, has anyone tried this?
cicada said:
Looking again at the voodoo page, there is already an udpate.zip flashable, has anyone tried this?
Click to expand...
Click to collapse
That won't work.. The changes are in the display drivers in the kernel. Not even a module..
It takes a whole kernel build with the drivers integrated, and only Epic kernels work for the Epic of course. Not other SGS kernels even.
please don't taint your kernels with that voodoo garbage
What's wrong wth using voodoo
Sent from my SPH-D700 using XDA App
Geniusdog254 said:
That won't work.. The changes are in the display drivers in the kernel. Not even a module..
It takes a whole kernel build with the drivers integrated, and only Epic kernels work for the Epic of course. Not other SGS kernels even.
Click to expand...
Click to collapse
Hmm.. guessing the video driver isn't buildable as a module?
cicada said:
Hmm.. guessing the video driver isn't buildable as a module?
Click to expand...
Click to collapse
Never tried it. It's probably a bad idea, because if something goes wrong with the module you have no video. And, it'd still take changes in all the kernels to make it usable with all of them. Still, I like the idea.
infamousjax said:
please don't taint your kernels with that voodoo garbage
Click to expand...
Click to collapse
I don't see it on my phone. It's not as white as my LCD screen, but my phone's screen isn't blue. So I agree..go without it.
If you set 7 smartphones next to each other, you'd probably have 7 different hues of white. Just a thought. I'll admit I got lucky with my Epic cause I don't have the blue tint. I compared mine with a Vibrant and its amazing how different of hue it is. I bet this post is super confusing, I'll stop now
hi
what the hell is voodoo lol im kind of new but i know how to flash roms keyboards an plenty more but what is voodoo im a fast learner
Pretty sure, geniusdog's kernels will keep having voodoo in them as long as Herver's continues to have it.
------------------------------------------------------------------------------**DISCLAIMER**------------------------------------------------------------------------------
Ok, So I decided to get this kernel out and played with a little more. Had quite a few people test it with success, so I'm gonna release it, but of course, I have to release it with the standard disclaimer.
I nor any of the contributors to this Kernel will be held responsible for anything you decide to do on your own. By downloading and flashing this kernel, you are knowingly accepting the fact that it may not work for you. If you should have any issues though, we are more than happy to help you to try to get it working.
The Battery Tweaks Have Been Removed Until They Are Updated... I Have Permission To Use Them, And I WILL Change Them, But I Will Also Make Sure I Don't Forget Credit This Time. My Apologies For The Last One.
---------------------------------------------------------------------------------**CREDITS**---------------------------------------------------------------------------------
Rodderik - For helping me out from the start. We've been working on kernels since day one of the source drop, but I also had ROM stuff to do and he just kept his kernel wheels turning. The mans a Genius.
Supercurio - For paving the way with voodoo sound.
Mkasick - For the video and keyboard patches.
Paiyne - For putting all my tester kernels through the gauntlet and letting me know what needed to be fixed right away so I could make sure it was a stable release.
All my other testers - I wouldn't be where I am without you guys. So thank you all
-------------------------------------------------------------------------------**CHANGELOG**-------------------------------------------------------------------------------
..::Spartacus v1.0::..
*Added A2SD*
*Added A Few CPU Scripts For Verification, And For Setting Frequencies*
*Overclockable To 1.3Ghz*
*Added A 1.3GHz, 1.2Ghz, And 600MHz Step*
*Added Camera/Video Fix By Mkasick*
*Added Keyboard Patch Fix By Mkasick*
*Undervolted A Little, But Not Much Because Of The Battery Tweaking Scripts*
*Added Voodoo Sound By Supercurio*
*Added Rodderiks Malware Patch*
*Raised The FPS Cap*
*Added All Scripts Needed For A2SD*
*Added My Custom Backup And Restore Scripts*
*Built From Source*
*Removed Battery Tweak Scripts Until I Update Them*
Yes.... I will make sure credit goes to everyone else that worked on them too...
NOTE: My custom backup and restore scripts are a work in progress. I know for sure that the backup works (I've had many testers confirm this), but I've changed the restore script, so hopefully it works for you. To give you a few features of what the script does, here's a brief rundown.
Backup
1. Backs up /data/app.
2. Backs up /data/app-private.
3. Backs up /data/data
4. Creates a compressed .tar file of backed up /data/data to conserve space.
5. Creates a folder on your sdcard for easy access labeled "backuppro".
Restore
1. Restores /data/app from sdcard to phone.
2. Restores /data/app-private from sdcard to phone.
3. Uncompresses .tar file and restores data to phone.
4. Once restored, the apps show back up in your "downloads" section of the Market again so you can still update when an update is available.
5. What to restore is optional. Whether it be both apps and data, or one or the other. You have the option to choose what you want with simple "y" or "n" responses.
When running the backup.sh script, you may see "No such file" or "No such directory", don't worry this is normal, it is still performing the requested actions. Also, before you backup or restore, the script will tell you exactly how much space is being used in the folder on your sdcard. This number does not show up until after the first time you run it obviously, but after the first time, it will show you exactly how much space you are using for apps & data.
---------------------------------------------------------------------------------**SCRIPTS**---------------------------------------------------------------------------------
Here Is A List Of The Scripts Included In The Kernel Flash And Their Description Of What They Do
(All commands are typed here exactly as they should be typed into Terminal Emulator following "su")
1. 1200perf.sh - This script can be run to quickly change the CPU Frequency to 1.2GHz Max and 200MHz Min Frequencies while on the Conservative Governor.
2. 1300perf.sh - This script can be run to quickly change the CPU Frequency to 1.3GHz Max and 200MHz Min Frequencies while on the Conservative Governor.
3. backup.sh - This script was created custom by Team Viper to backup your /data/app & /data/app-private folders to your sdcard, as well as your /data/data folder.
4. restore.sh - This script was created custom by Team Viper to restore your /data/app & /data/app-private folders and your /data/data files back to your phone from the sdcard.
5. cpufreq.sh - This script sets your governor to 'Conservative' and your frequency changing thresholds to 50/10.
6. getfreq.sh - This script can be run to tell you your current CPU Frequency.
7. getgov.sh - This script can be run to tell you your current CPU Governor.
8. verifycache.sh - Force /system dalvik-cache on /data instead of /cache if it is not large enough.
9. maxperf.sh - This script sets your CPU to 'Conservative' while setting your Max frequency to 1300MHz, and your Min frequency to 200MHz.
10. minfree.sh - This script sets your phones internal memory killer to slightly more aggressive settings.
11. tweaks - This script allows you to change certain features of the phone. With it, you can change your Hardware Accelleration, Stagefright Media Player, JIT, and Dalvik Heap Sizes status to either Enabled or Disabled. It prompts you to make a backup first, or you can not use the script.
12. Malware Patch - Rodderick wrote up this script to prevent anyone from accessing your phone or causing virus like issues. Thanks Rodderik, we love your tight butt.
------------------------------------------------------------------------------**DOWNLOADS**------------------------------------------------------------------------------
Spartacus Kernel Download & Mirror
Spartacus_v1.0_EB13_1.3GHz
This Kernel Was Built Entirely From Source, But Has The Battery Tweaks Removed Until They Are Updated. I Will Post Another Version Tomorrow When I Get More Time With The A2SD Scripts In It.
------------------------------------------------------------------------------**APPLICATIONS**------------------------------------------------------------------------------
Here are a few applications that you can use with the kernel. Some applications are needed, such as Terminal Emulator, some applications are optional, such as Voodoo Control App, and some applications are just for fun, such as Linpack. Regardless of your choice, enjoy
Voodoo Control App
Terminal Emulator
Linpack
Quadrant
Smartbench 2010
Smartbench 2011
Neocore FPS Test
SimplyLock Lockscreen Replacement
Just wanted to make sure everyone was aware, even though they are posted in my thread, I am NOT taking credit for them. Just a heads up.
NOTE: All the applications that I have listed here are FREE in the market. I simply placed them here for convenience. If you like the apps, feel free to go to the market and purchase the donation versions if available.
You can also download SetCPU from the Developers page on XDA found here or you can get it from the Android Market. If you like the app, show your support for the Dev and purchase it, it's cheap, it wont break you .
------------------------------------------------------------------------------**RESOURCES**------------------------------------------------------------------------------
Team Viper
Team Viper's Official Site: Click Here
Team Viper's Official Wiki: Click Here
Team Viper's Official Tickets: Click Here
I'd like to now thank all of you for your support! All the work I do is 100% free and I will never charge for anything I do. Should you ever feel the need to donate, you are more than welcome to and you can donate by clicking this link.
Click Here to buy me a soda, beer, or Flux Capacitor for my DeLorean... Yes, that's right, you are NOT the only time traveling Ninja, set on a quest for truth and justice. The only difference between me and you... I was trained by Chuck Norris.
Downloading now.
You should of waited to see if you get the OP back,you should be ok since you said you made a mistake...
Sent from my SPH-D700 using XDA Premium App
ecooce said:
You should of waited to see if you get the OP back,you should be ok since you said you made a mistake...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I was going to, but i hate defending myself for honest mistakes... I removed any trace of anything people could yell about. I built this personally from source myself, and people can see that i did it. That way there's no questions. And for all the people that said stuff in the other thread... If you don't like my work... don't download it... seriously... developing for the Samsung Epic turned from being fun for me to living in a daytime soap opera... This may be the last thing i do.
Nothing against you ecooce... i've got no beef with you... I agree 100% with the statement you made, what he did was uncalled for... but credit DID need to be given... I just wish i would have been properly presented with the opportunity to fix my mistake before anything happened. I would have gladly done so.
I'm sorry, i don't mean to rant, i just feel like i need to present my case to everyone. If you've been a loyal follower of Viper or not, i never intended to do wrong. I understand that when ViperROM first started, yeah, we have had a few things that didn't work, but our ROM is just like anyone else's out there today... I've personally never heard of anyone needing to replace their phone after running one of my ROM's... I'm not even making the current release, and TPhillips busted his ass on it, but i'm sure someone will say something about it. ViperROM has advanced since we've started, and we're not backing down because some of the other dev's dont like us. We don't care. Again, i apologize for not giving credit to begin with, it was an honest mistake and i gladly fixed the mistake by stating i was sorry.
Here's the bottom line. I Credited other people in my thread, so it's obvious i don't have issues with crediting people. I apologize for my mistake. If you don't like me, or any other person of the team, you have the freedom to choose not to install this. To everyone else, Thank you.
Agreed,well said...
Sent from my SPH-D700 using XDA Premium App
BThomas22x said:
I was going to, but i hate defending myself for honest mistakes... I removed any trace of anything people could yell about. I built this personally from source myself, and people can see that i did it. That way there's no questions. And for all the people that said stuff in the other thread... If you don't like my work... don't download it... seriously... developing for the Samsung Epic turned from being fun for me to living in a daytime soap opera... This may be the last thing i do.
Nothing against you ecooce... i've got no beef with you... I agree 100% with the statement you made, what he did was uncalled for... but credit DID need to be given... I just wish i would have been properly presented with the opportunity to fix my mistake before anything happened. I would have gladly done so.
I'm sorry, i don't mean to rant, i just feel like i need to present my case to everyone. If you've been a loyal follower of Viper or not, i never intended to do wrong. I understand that when ViperROM first started, yeah, we have had a few things that didn't work, but our ROM is just like anyone else's out there today... I've personally never heard of anyone needing to replace their phone after running one of my ROM's... I'm not even making the current release, and TPhillips busted his ass on it, but i'm sure someone will say something about it. ViperROM has advanced since we've started, and we're not backing down because some of the other dev's dont like us. We don't care. Again, i apologize for not giving credit to begin with, it was an honest mistake and i gladly fixed the mistake by stating i was sorry.
Here's the bottom line. I Credited other people in my thread, so it's obvious i don't have issues with crediting people. I apologize for my mistake. If you don't like me, or any other person of the team, you have the freedom to choose not to install this. To everyone else, Thank you.
Click to expand...
Click to collapse
Good man.
As someone thats around you guys alot (the team), I've got to say people on here don't understand how much work gets put into these things. Even though he borrowed some Scripts, as you can see here, the kernel doesn't need the scripts at all to run, and is an amazing kernel WITHOUT the scripts, with just everything BT made HIMSELF.
The dudes helping our Epics while ACTIVELY serving our country EVERYDAY as well, and you don't see him complain or ask for anything in return. Imagine yourself being in the military all day and than dev'ing all night. I sure as hell know I'd be tired. But he still does it anyway cause he enjoys it.
But as you can tell, it seems that enjoyment is slowly being taken away from him, which is horrible. Hasn't anyones momma on here taught them the "If you don't have anything nice to say, don't say anything at all?".
Dudes a great guy yet I haven't seen much respect shown toward him on here and its kind of sickening. I mean no disrespect towards anyone on here, but anyone that's got something against BT or anyone on the ViperTeam, take it up with them privately from now on. You may also take notice that they ViperTeam doesn't go around implying they're better than anyone like some other groups you see around. If you don't like their stuff, they don't care. Just don't use it.
And a problem I saw in the other thread was people saying the kernel was breaking their root.
People, if your on Syndicate, Their root is in their KERNEL instead of their ROM. Therefore if you flash a kernel that doesn't have the root files, you will lose root on the ROM because the root was in the kernel. So stop thinking its the kernels fault when your on Syndicate and this kernel makes you lose root.
Don't know if it works but you can try flashing the kernel than one-click-rooting if you want. That may make it work. Other than that, don't keep saying "I'm running ACS's rom and this kernel makes me lose root! rage!!$%%percent%[email protected]!"
/rant.
Keep it up BT, trying er out now.
Soooo...this does have a2sd?
I know it says "added a2sd", I only ask since the a2sd instructions werent included
Btw, whats the swap partition for? I have a2sd setup from baked snack, but I don't remember it having me make a swap partition...what purpose does that serve? (Just out of curiosty)
And since I don't have a swap, I'm gonna have to remove the partitions first....is there an option to do this in cwm or will I have to adb it?
Sent from my baked and emotionless SPH-D700
thanks
thanks bro you now how i feel hahaha you the man regardless so lets just do the dang thing BT imma hit u up in the irc bro..tomorrow lol
Does this kernal still have the color problem?
Sent from my SPH-D700 using XDA App
Thanks!
10 char
**** happens people can be big ass's but don't trip everyone still loves you and the work you and the team do. Maybe next time they won't jump the gun and freak out about the little stufff in life.
Sent from my SPH-D700 using XDA Premium App
Just installed and love the speed of this.
But after I wake the phone up from from its first sleep after reboot, color goes weird. Color is all washed out.
Screen looks normal on first boot, its only after the first wake up does it go weird.
I will reinstall when this is fixed.
Can we get everything except the color changes without a2sd?
Sent from my Epic 4G using XDA Premium app
SemiGamer said:
Good man.
As someone thats around you guys alot (the team), I've got to say people on here don't understand how much work gets put into these things. Even though he borrowed some Scripts, as you can see here, the kernel doesn't need the scripts at all to run, and is an amazing kernel WITHOUT the scripts, with just everything BT made HIMSELF.
The dudes helping our Epics while ACTIVELY serving our country EVERYDAY as well, and you don't see him complain or ask for anything in return. Imagine yourself being in the military all day and than dev'ing all night. I sure as hell know I'd be tired. But he still does it anyway cause he enjoys it.
But as you can tell, it seems that enjoyment is slowly being taken away from him, which is horrible. Hasn't anyones momma on here taught them the "If you don't have anything nice to say, don't say anything at all?".
Dudes a great guy yet I haven't seen much respect shown toward him on here and its kind of sickening. I mean no disrespect towards anyone on here, but anyone that's got something against BT or anyone on the ViperTeam, take it up with them privately from now on. You may also take notice that they ViperTeam doesn't go around implying they're better than anyone like some other groups you see around. If you don't like their stuff, they don't care. Just don't use it.
And a problem I saw in the other thread was people saying the kernel was breaking their root.
People, if your on Syndicate, Their root is in their KERNEL instead of their ROM. Therefore if you flash a kernel that doesn't have the root files, you will lose root on the ROM because the root was in the kernel. So stop thinking its the kernels fault when your on Syndicate and this kernel makes you lose root.
Don't know if it works but you can try flashing the kernel than one-click-rooting if you want. That may make it work. Other than that, don't keep saying "I'm running ACS's rom and this kernel makes me lose root! rage!!$%%percent%[email protected]!"
/rant.
Keep it up BT, trying er out now.
Click to expand...
Click to collapse
I don't complain much on here, but one click root didn't work. I read the whole thing and it keeps saying not allowed throughout the process so hopefully I can figure it out how to deeply my phone. To the op, thanks for your efforts
Sent from my SPH-D700 using Tapatalk
squshy 7 said:
Soooo...this does have a2sd?
I know it says "added a2sd", I only ask since the a2sd instructions werent included
Btw, whats the swap partition for? I have a2sd setup from baked snack, but I don't remember it having me make a swap partition...what purpose does that serve? (Just out of curiosty)
And since I don't have a swap, I'm gonna have to remove the partitions first....is there an option to do this in cwm or will I have to adb it?
Sent from my baked and emotionless SPH-D700
Click to expand...
Click to collapse
Bump quoting because I want this answered (specifically about the swap)
Sent from my baked and emotionless SPH-D700
BT again THANKS!
Will try it out.
Been running Viper Roms forever but was trying others while waiting for the new release. i was on Midnight when I flashed the new Kernel and it seemed to work fine. I then put Trinity back on an did a few more things....well bottom line I cannot get the new kernel to work now with trinity. I've odin'd back to stock and worked my way up and as soon as I put the new kernel on it hangs at the Samscreen. I can flash the 03a and 4 kenels with no problem but Spartacus is out of the question. Any Idea what I may have F'd up?
BT...just trying this out and seems to be great, as usual from team viper. Just a quick question...does running one of the performance scripts eliminate the need for set cpu...or would I still need both? Thanks again! Happy st pat's day!
Sent from my SPH-D700 using XDA Premium App
lilmikeyv said:
BT...just trying this out and seems to be great, as usual from team viper. Just a quick question...does running one of the performance scripts eliminate the need for set cpu...or would I still need both? Thanks again! Happy st pat's day!
Edit: nm...the scripts didn't seem to work for me...I'll just adjust on set cpu then...superfast...thanks!
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Premium App
It eliminates it.
lilmikeyv said:
BT...just trying this out and seems to be great, as usual from team viper. Just a quick question...does running one of the performance scripts eliminate the need for set cpu...or would I still need both? Thanks again! Happy st pat's day!
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Sent From My Evo Killer!
Anyone have an idea how hard it would be to port this tiamat kernel over to Transformer? built for XOOM and others, and the XOOM hardware is near identical right? Just a thought, this thread has the info and link to the github of the sources.
http://forum.xda-developers.com/showthread.php?t=978013
I posted in the thread if he could develop for us and everyone yelled me. I thought it'd be easy too. But I agree. I hope someone could port this because this kernel seems amazing.
Thunderbolt Rooted!
andrew53517 said:
I posted in the thread if he could develop for us and everyone yelled me. I thought it'd be easy too. But I agree. I hope someone could port this because this kernel seems amazing.
Click to expand...
Click to collapse
Yeah, I was going to PM him, but he has PMs disabled, and I wasn't going to post in the thread because people hate that, me included. There is nothing more annoying in a thread when someone else comes in asking to do this all to their device. While this is a situation where at least the device internals are pretty similar, still not a polite thing to do. The github of his work should be enough for any dev here to port the work over pretty easily I'd think. We'll see though.
crater said:
Anyone have an idea how hard it would be to port this tiamat kernel over to Transformer? built for XOOM and others, and the XOOM hardware is near identical right? Just a thought, this thread has the info and link to the github of the sources.
http://forum.xda-developers.com/showthread.php?t=978013
Click to expand...
Click to collapse
The hardware is fairly similar but they are based on two completely different OEM boards. Transformer=Ventana, Xoom=Stingray.
The Tiamat kernel modificationc could possibly be ported to the transformer kernel, but it isn't as straight forward and simple as you might think.
definitely would be sweet.. dual 1.6GHZ sounds pretty good
Hopefully we get some support soon.. I wish I knew how to do this stuff.
I'm not sure what it is but the forum for the Eee pad seem a bit dead tbh, is it just because of limited stock?
bigmo7 said:
I'm not sure what it is but the forum for the Eee pad seem a bit dead tbh, is it just because of limited stock?
Click to expand...
Click to collapse
I sure hope so. I know R2doesinc is ordering one, he is a great developer. So we have another one on board soon. But I think it is a combination between that and that there are so many choices out there. I hope it picks up soon..
I talk to brd all the time. He also hangs out in the asus-transformer irc channel. I spoke to him briefly about of a few weeks ago and he was going to look into it but got busy with tiamat
Sent from my LG-P999 using XDA App
I know netarchy is currently working on a kernel for the Transformer as he has a repo up and running. In case you aren't familiar with him, he makes some killers kernels for the EVO. Just fyi...
egzthunder1 said:
I know netarchy is currently working on a kernel for the Transformer as he has a repo up and running. In case you aren't familiar with him, he makes some killers kernels for the EVO. Just fyi...
Click to expand...
Click to collapse
Yeah, he hangs out in the irc channel too. Most of the devs do
Sent from my LG-P999 using XDA App
Now this all sounds sooo exciting!! I bet once the ball starts rolling there will be no stopping it!
Sent from my TF101
funnycreature said:
Now this all sounds sooo exciting!! I bet once the ball starts rolling there will be no stopping it!
Sent from my TF101
Click to expand...
Click to collapse
I actually think there are a few dev's working on kernel projects
egzthunder1 said:
I know netarchy is currently working on a kernel for the Transformer as he has a repo up and running. In case you aren't familiar with him, he makes some killers kernels for the EVO. Just fyi...
Click to expand...
Click to collapse
Now THIS is refreshing to hear!
Sent from my HTC Eva 4G using Tapatalk
I just got this today.. rooted it.. and now I'm flashing a test OC kernel with modded ramdisk (took that stupid ntfs module out of /sbin/ and the insmod in the init.ventana script).... among other things...
so far so good.. yay.. I'm in!
yes!! that was f***n easy.. 1.2ghz... now for more speed..
Blades said:
I just got this today.. rooted it.. and now I'm flashing a test OC kernel with modded ramdisk (took that stupid ntfs module out of /sbin/ and the insmod in the init.ventana script).... among other things...
so far so good.. yay.. I'm in!
yes!! that was ****in easy.. 1.2ghz... now for more speed..
Click to expand...
Click to collapse
Thanks for sharing the kernel.
psicrest said:
Thanks for sharing the kernel.
Click to expand...
Click to collapse
there is some hardcore douchery going on with sku checks.. I'm chasing variables all over the place.. I give up for the night.. this is like the xoom source, but again fuse data screws us.. I never should've opened this god damn box.. i knew i'd hate it. I haven't used it all.. I prefer my gtab.. argh.. sorry its late.. late late. still want to frisbee it..
Can't wait for the ability to OC
I miss IRC.
And I hope we get some development on this soon. It'd be a shame to see people sticking to products like the xoom, just because the TF is so limited in its availability. We need availability to pick up for this product.
silenceforus said:
I miss IRC.
And I hope we get some development on this soon. It'd be a shame to see people sticking to products like the xoom, just because the TF is so limited in its availability. We need availability to pick up for this product.
Click to expand...
Click to collapse
Its not limited in just availability, its limited in 'mod-ability'.. It could just be the product maker following the guidelines for that particular board and making use of 'security' features specific to that board, but its still a pain in the ass. Work was put in to make the end user work harder to be able to customize.
I have the gtab (harmony), Xoom (stingray) , and eeepad (ventana). The gtab is the fastest, the easiest to mod, the hardest to brick.. and the heaviest with the worst screen. The eeepad is the slowest, the worst to mod and the lightest.. guess what .. best screen.
I am typing this on the gtab tho.. and I just got the eeepad today. It'll probably collect dust. Tried to play south park (originally avi/xvid/mp3) converted/muxed to mp4/xvid/aac and the Asus would play it... but volume control was not working it was full blast or mute. My gtab plays xvid avi/mp3 without a hiccup. Any other format I can throw at it too (sans multichannel audio and high profile h264). Its really surprising how far this has come. Since its oc'd every which way, it makes everything else seem very very slow. Only thing I haven't been able to get oc'd yet is emc.
Getting the ability and the clocks setup for the Asus was a breeze. Configuring/adjusting /making sense of all the bits and pieces of dvfs was not. speedo_id is a new one to me, and that seems to be the value that is read from fuse data and locks down max clocks
You guys got Blades and Netarchy on the case. You don't need me lol. I would LOVE to have Netarchy working on stingray.
I have started a comparison chart for the currently available ROM's for the G2X. Since we are just getting started with this device it seems like a great time.
I have made the spreadsheet editable by anyone, I encourage and would appreciate any help with keeping it current. I also do not mind any improvements you see fit, such as adding or changing columns, conditional formatting etc. I just put this together in the time I had available today and it is a rough draft. I know some of you here have much more experience in using Google docs and making something like this so do your thing! I'd like this to be a community project.
PLEASE do not intentionally falsify any information or in any way harm the integrity of this project, we all benefit from this site and there is nothing funny about ruining this for others. Also, I will make a nightly backup.
I can't seem to embed this into the post so here is a link.
G2X ROM Comparison Chart
Click to Edit Chart
Link didn't work for me
Sent from my LG-P999 using XDA App
rich2thad said:
Link didn't work for me
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Thx, try again. Seems the phone browser don't like https links.
And now we are working.. lol
Sent from my LG-P999 using XDA App
I'm almost 100% positive CM7 comes with ADW Launcer and not launcher pro, unless there was a recent change?
knuckelpuc said:
I'm almost 100% positive CM7 comes with ADW Launcer and not launcher pro, unless there was a recent change?
Click to expand...
Click to collapse
And you'd be right.
knuckelpuc said:
I'm almost 100% positive CM7 comes with ADW Launcer and not launcher pro, unless there was a recent change?
Click to expand...
Click to collapse
+1
Sent from my LG-P999 using XDA App
knuckelpuc said:
I'm almost 100% positive CM7 comes with ADW Launcer and not launcher pro, unless there was a recent change?
Click to expand...
Click to collapse
Yea.. um... I was just seeing if anyone actually read it... yea..
fixed
sl0play said:
Yea.. um... I was just seeing if anyone actually read it... yea..
fixed
Click to expand...
Click to collapse
Lmao
Sent from my LG-P999 using XDA App
And both cm7 and faux are 2.3.4 not 2.3.3.
Sent from my LG-P999 using XDA Premium App
Nice start...this could turn into something really helpful.
Bionix has kernel .1.1 according to its changelog?
It seems you are trying to make a point or something with the voodoo lagfix?
If none of the phones have it, why would there be a column then?? The column would only be necessary if one of the roms had it. Why put it in there?
We will never have a lag-fix as we already have a great file system (ext3 and ext4) only reason that would be needed is for Samsungs ****ty rfs file system. Might as well remove it from the chart
Good comparison chart though. ^^
Edit: Oh and mine does have spare parts, boot and shutdown animation changed as well
schmit said:
It seems you are trying to make a point or something with the voodoo lagfix?
If none of the phones have it, why would there be a column then?? The column would only be necessary if one of the roms had it. Why put it in there?
Click to expand...
Click to collapse
You know what, I actually re-flashed my old vibrant for the wife to use the same day I flashed my first ROM onto this phone so I remembered hearing the lagfix lady while I was flashing a ROM on here and so I thought.. well, maybe it was a little late when I put this together. Column removed.
Once again, if there is something silly like this that you guys see please feel free to make the change, I'm not claiming ownership of this spreadsheet.
tweezit said:
We will never have a lag-fix as we already have a great file system (ext3 and ext4) only reason that would be needed is for Samsungs ****ty rfs file system. Might as well remove it from the chart
Good comparison chart though. ^^
Edit: Oh and mine does have spare parts, boot and shutdown animation changed as well
Click to expand...
Click to collapse
Hi tweezit! Thanks for taking the time to reply. I am running your ROM now and its sexy Updated your info.
Removed the lagfix column, I guess it had just become a permanent part of my psyche.
Should I replace with a file system column (ext3 or ext4)? Or is that not important?
Also, is it safe to assume everyone is running the same base band at the moment?
Good topic
My ROM info is lacking
Stock launcher2
Included: T-mobile Theme Manager/Chooser, SpareParts, FileManager, Torch, DSP Manager, ROM Manager and WiFi Calling.
Kernel is 2.6.32.41 with latest patches, updates, OC/UV etc etc
Anyways, hope this will make the ROM less of a mystery
faux123 said:
My ROM info is lacking
Stock launcher2
Included: T-mobile Theme Manager/Chooser, SpareParts, FileManager, Torch, DSP Manager, ROM Manager and WiFi Calling.
Kernel is 2.6.32.41 with latest patches, updates, OC/UV etc etc
Anyways, hope this will make the ROM less of a mystery
Click to expand...
Click to collapse
Thanks for the info faux! I promise its nothing personal that yours was lacking. I actually think your ROM is brilliant, and your a bit of a genius![/suckup] I'm just sticking to froyo for now.
I really appreciate you guys (devs) posting in here. I've been working long days I just wanted to get this out there even as a really rough draft so it didn't just become a bigger and bigger task I don't get around to. I
Added Gigglebread and File System column.
Thanks to everyone who has edited with more info!
This is going to sound petty, but can we add a column for HD recording support? I know the leaked build doesn't support it (that's why I went back to stock), do any of the custom ROMs support it yet that are not Froyo-based? I presume all froyo ROMs would support HD recording with the LG camera apk.
**UPDATE 29 MAY**
CM7-RC3 and CM7 nightly 20120527 both work with the March 2012 baseband and have much higher outgoing volume! I'm not sure the issue I opened on the tracker had any part in this, but thanks to all who helped anyways! Your support was very much appreciated.
As CM7-based ROMs sync to the newer source, I am sure that they too will be fixed.
****************
I'm converting this thread into a Call to Arms! If you are frustrated with the low microphone volume on anything based on CM, please visit the thread on CM's issue tracker to leave your comments and "star" the issue. This is NOT an attempt to flood their thread with meaningless garbage. My intent is to let the CyanogenMod team know that this issue is very real and annoying. I think I can speak for most of us in saying that CM is a blessing to the Android world and that we mean no disrespect. My sole intent is to not let this issue get swept under the rug as it has in the past.
If you have a minute, please leave comments both here AND on the issue tracker to ensure this gets taken care of in due time. Please be respectful with your comments, but share your experience with the team in order to let them know that you are affected. Thank you all for your support with this issue.
r4d14n7 said:
This project is hereby abandoned by me. I don't have the knowledge, and I don't have the time to learn. If someone else wants to pick this up, I left a fair amount of documentation and research here in the thread and I will be available through PM if you have any questions. The best thing you can do right now is check the official bug report on CM's Issue Tracker, star it and maybe leave a comment or two. Sorry to let you guys down, but I pushed as many buttons as I'm capable of pressing at this point in time. Hopefully RC can figure this one out.
Original post and edits follow:
*Update again* I hit a wall and am not savvy enough to know where else to look. I submitted this bug to the issue tracker on CM's google code site here: http://code.google.com/p/cyanogenmod/issues/detail?id=5190
Feel free to head over there and "star" it to get updates. I really hope they will help us out. Thanks for the support guys. Going to give them a little bit and see where it takes us.
*Update* Changed thread title for clarity. In the process of trying to unpack/edit/repack a kernel to increase the volume of the microphone. Lucky for me, it's mostly scripts.
Let me start this thread out by saying that I am not a developer, coder, github user, etc. Yes, I'm a noob when it comes to all things coding.
Alright. I searched and searched and searched some more for the commit on CyanogenMod's github. I found it.
https://github.com/CyanogenMod/andr...mmit/a042d3bba7dc7d563ef58dfd2b0811722d924f86
I *think* this is the patch that caused the low microphone volume since October of last year. It could be one of its parent patches, but it's related. This commit is also included in CM's ICS branch, which could be causing the low microphone volume issue that some of us have been experiencing for so long.
I went to edit that file so I could try to fuddle my way through a build (which I've never done before) but I couldn't find the actual file in the github. Was this file removed? Are input volumes adjusted somewhere else now? I'm spoiled by our developers and would love it if someone would try reverting this patch if it's possible. Anyone else feel the same?
Click to expand...
Click to collapse
Update! bassmadrigal from the CyanogenMod staff helped me locate the microphone volume values. They are in the /sys/devices/platform/star_wm8994/data file. Using an older CM7 (167) build, I was able to modify the volumes until the phone reboots. I tested the voice quality by calling my own voicemail since the volumes can be different while in a call.
Having done this, I flashed a newer CM9 build. The values at the specific registers in that file are indeed different on CM9, but I was unable to modify them. Any modifications to that file via root explorer or adb were ineffective. I even went so far as to delete the file completely, but it was regenerated within seconds. There is some kind of built-in security (either in Android 4.x itself or CM9) that prevents manipulation of this file, and others I'm sure.
Does anyone know of a way to manipulate this file?
r4d14n7 said:
Update! bassmadrigal from the CyanogenMod staff helped me locate the microphone volume values. They are in the /sys/devices/platform/star_wm8994/data file. Using an older CM7 (167) build, I was able to modify the volumes until the phone reboots. I tested the voice quality by calling my own voicemail since the volumes can be different while in a call.
Having done this, I flashed a newer CM9 build. The values at the specific registers in that file are indeed different on CM9, but I was unable to modify them. Any modifications to that file via root explorer or adb were ineffective. I even went so far as to delete the file completely, but it was regenerated within seconds. There is some kind of built-in security (either in Android 4.x itself or CM9) that prevents manipulation of this file, and others I'm sure.
Does anyone know of a way to manipulate this file?
Click to expand...
Click to collapse
You're a legend man! Thanks for chasing this issue.
Sent from my LG-P999 using xda premium
From what I'm told, this file is actually part of the kernel. And I know nothing about any of this stuff. Is there anyone who knows how to modify and build their own kernel from source of whom I could ask some questions? I browsed around on Faux's github, but I seriously have no idea what I'm looking at.
DupleX01 said:
You're a legend man! Thanks for chasing this issue.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Man, I'm just trying to get the ball rolling on this ignored bug. I guarantee if I can fix it myself, I will definitely share.
Oh man, I hope this leads to the bug getting fixed. I love MIUI and CM, but the low mic volume has forced me to go back to using stock.
zenstrom said:
Oh man, I hope this leads to the bug getting fixed. I love MIUI and CM, but the low mic volume has forced me to go back to using stock.
Click to expand...
Click to collapse
I'm no kernel dev, but I'm still working on it. Hopefully I'll be able to get this issue resolved.
Edit: And by working on it, I mean asking kernel devs if they could build a test kernel with these changes included.
r4d14n7 said:
I'm no kernel dev, but I'm still working on it. Hopefully I'll be able to get this issue resolved.
Edit: And by working on it, I mean asking kernel devs if they could build a test kernel with these changes included.
Click to expand...
Click to collapse
Good luck to you sir!!!
Sent from my LG-P999 using xda premium
Lol, I just can't stop thanking. I was so happy to see that I wasn't the only one (thanks mt3g for your empathy there) to notice this annoying issue in CM based ROMs, when I've opened a thread the other day:
http://forum.xda-developers.com/showthread.php?t=1538240
IMHO, for some reason this bug just never got enough attention.
So, I'm crossing my fingers.
Sent from my LG-P999 using xda premium
Oh definitely, it just seemed to get shoved under the rug like it never happened a bunch of people in Baldwin guy cm7 thread stated it a bunch and it never got any attention if the OP can point someone in thebright direction after he does a bunch reading and reaching out to people then it can get resolved. It is honestly the only "bug" in cm7 that I hate. A bunch of people said they just switched ril's to fix it but I don't think so, I've done plenty of recording and what not with voicemails and I can easily tell between 2.3.3 to cm7 and found a build that was around 150ish
Sent from my LG-P999 using xda premium
mt3g said:
Oh definitely, it just seemed to get shoved under the rug like it never happened a bunch of people in Baldwin guy cm7 thread stated it a bunch and it never got any attention if the OP can point someone in thebright direction after he does a bunch reading and reaching out to people then it can get resolved. It is honestly the only "bug" in cm7 that I hate. A bunch of people said they just switched ril's to fix it but I don't think so, I've done plenty of recording and what not with voicemails and I can easily tell between 2.3.3 to cm7 and found a build that was around 150ish
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Almost all of the old CM7 builds are still hosted here: http://goo.im/cm/p999/nightly but for some reason the 170's are missing. Haha...
I agree with you on it being the only thing I hate about CM7/9.
Anyway, another update for you guys. I found a guide on how to unpack the kernel and ramdisk from boot.img so I can modify this file, then repack it. Downloading Ubuntu now. Going to install it in a Virtual Machine and see if I can do this. Might take me a bit though. I'm a busy guy
Well, I was able to unpack the kernel and split it into the kernel and ramdisk. The ramdisk contains the "sys" directory, but it's empty. I can't find the file that I need to modify. Maybe it's in the kernel part of the split.
I would just like to say thank you.
And I wish I could help!
Sent from my LG-P999 using xda premium
So if it's based in the kernel, do other kernels face this problem?
I'm using CM7.2 with faux kernel and haven't noticed low speaker volume.
Sent from my LG-P999 using XDA
I'll take a look at it when I get the chance.
redmonke255 said:
So if it's based in the kernel, do other kernels face this problem?
I'm using CM7.2 with faux kernel and haven't noticed low speaker volume.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Low mic volume is the issue. Speaker volume is fine.
nightf0x said:
Low mic volume is the issue. Speaker volume is fine.
Click to expand...
Click to collapse
Yea sorry that's what I meant, I haven't had complaints about that but maybe I'm just loud.
Sent from my LG-P999 using XDA
redmonke255 said:
Yea sorry that's what I meant, I haven't had complaints about that but maybe I'm just loud.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Record your self on a stock based rom or leave a voice mail its very noticeable, speaker phone is almost pointless while on cm7/9 you set the phone down 2 feet from your face and they can't hear you practically it sounds like you're whispering.
Sent from my LG-P999 using xda premium
mt3g said:
Record your self on a stock based rom or leave a voice mail its very noticeable, speaker phone is almost pointless while on cm7/9 you set the phone down 2 feet from your face and they can't hear you practically it sounds like you're whispering.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
You're absolutely right mt3g, speakerphone is horrible. And I'm typically kind of a "chin talker" who lets the phone drift down away from the mouth. If I pay attention to holding the phone up further in front of my mouth and speak firmly, I can usually get heard alright on the other side, but I'm used to phones in the past picking up a lot better, and sometimes I need to speak softly if my kids are napping, etc.
FYI, this is my test environment (to eliminate variables):
Always call voicemail to perform the tests, because the input volume can change from just using a voice recorder app to actually in a call.
I play the same part of the same song at the same volume with my phone in the same position every time.
Just nandroiding back and forth between stock/early CM7/late CM7/CM9, there is a major difference.
redmonke255 said:
So if it's based in the kernel, do other kernels face this problem?
I'm using CM7.2 with faux kernel and haven't noticed low speaker volume.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
If I'm not mistaken, custom kernels designed for CM7/9 are based on the original CM7/9 kernels. Regardless, I have personally verified this issue exists with faux's and morfic's kernels.