Mod Type: Kernel Difficulty: Moderate Mod Status: Nightly Mod Base: TouchWiz (Samsung) Carrier: Verizon
Requires Root: No Apply In: CWM Recovery Optional: Insecure Boot Optional: Overclocked Android Version: 2.3.X (GB)
With a big thank you very much to imnuts, the father of this project, I'd like to announce the first working build of the PBJ kernel for Samsung's Droid Charge FP5E!
I've picked up exactly where imnuts left off, pulling in his kernel and initramfs GitHub repos, and working through the problems that took having a Droid Charge in hand to fix. This release contains no new working functionality over the FP1H release from 0524. I'm experimenting with compcache, so the ramzswap.ko and lzo_*.ko modules are included, but not activated by default in any way. Activating them in a naive way will just make your phone super-slow with constant swapping and OOM killing. More work is needed.
I've put fresh builds of most of the kernel modules into /lib/modules. They're debug-stripped for size reasons. If we have significant problems I'll release a build with unstripped versions.
Please reference the original thread project for the feature list that was already included in 0524. They should all be active in 1213. If any are missing or not working, please let me know!
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy Posted Image
Download FP5E Version:
1219
Merged fast charge patch; Fast Charge *should* be working
Turned off hung_task_panic in lpm.rc, should prevent the reboots after 4-5 min of low power mode charging
Activated RCU CPU stall detector (may help identify causes of lagginess)
1214
Modularized Android logger.ko to avoid duplicate log errors
Disabled install_root script in init.rc that was causing some users to lose root
Stripped modules with strip --strip-unneeded for size reduction
Fixed add_swap script and renamed fatformat to fat.format
1213
Merged and debugged FP5E source
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, please note if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working. Please note that this kernel is "nightly" quality, meaning it has been tested only by me and not thoroughly. If you can't afford to have your phone not work for at least a little while, don't install this!
Frequently Asked Questions
How do I install this?
You flash this in CWM. If you need CWM, you can find it here
Can I use ROM Manager to flash this?
If you didn't use Odin to flash CWM, this will not work. Also, ROM Manager is not compatible with CWM when it fully replaces stock recovery.
Can I install this over another Voodoo Lagfix kernel?
Yes. Any kernel that use's supercurio's lagfix can be flashed over any other kernel that uses it.
How do I disable Voodoo Lagfix?
Create a file on the SDCard named disable-lagfix within the voodoo folder (/sdcard/voodoo/disable-lagfix). You can also use the option in the Voodoo Control app (from the market) or the option in CWM Recovery to disable the lagfix.
How do I know if it is installed?
Go to Settings > About Phone and the kernel version should read:
Gingerbread
2.6.35.7-FP5
If you have adb shell or a terminal emulator, the kernel builder signature at the top of `dmesg` should be "[email protected]"
Will this work with xxx ROM?
This should work with any currently available ROM that is posted here. It has only been tested with dwitherell's Tweaked 3.1 so far.
Can I overclock with this kernel?
Overclocking is supported on the Gingerbread version.
Can I use SetCPU with this kernel?
You can use SetCPU with this, but issues may arise if you use profiles. If you have problems and are using profiles, I'm not going to try to fix them as profiles do not always work properly on SGS phones.
Can I use Fast Charging with this kernel?
Fast charging support is experimental as of the 1219 release. Any means of writing "1" to "/sys/kernel/fast_charge/force_fast_charge" will turn on fast charge mode. The Samsung battery driver does not publish a charging current variable, so there is no way to determine the charging current exactly (without an ammeter, that is!) I have done timed recharge trials on AC and on USB with fast charge active, and the recharge rates I achieved were comparable across both cases. Community testing will determine if it's reliable for everyone.
Does this kernel include xxx feature?
If it is not listed in the first post, probably not. To be sure, check the commits to the source on Github.
Can you add/implement xxx feature?
If you can link to what you want added/changed, I can look into doing so. If you just say something like "I want bigger quadz!" with no information about what you want or where to find it, I'll just disregard your request.
I am having xxx issue, can you fix it?
See the NOTES section above. Failure to provide any steps to reproduce your error, or a log of the issue as it is occurring will not get your problem fixed. I need the output from logcat and/or dmesg to be able to fix problems. Use the following to obtain a log (easiest with ADB).
adb shell dmesg > dmesg.txt
adb logcat > logcat.txt
Enter one of the commands and attempt to recreate your issue. Logcat will run constantly until you stop it (disconnect the phone, or ctrl+c). Dmesg will dump the current buffer and end. Try to get a logcat first as it will be easier to capture the error. PM me the files once you've collected them and I will look into it. DO NOT POST THEM IN THE FORUM. Logcat and dmesg may both contain identifying information (like your phone number or email address) so PMing them to me will prevent everyone from seeing this info.
Thanks bro...
You'd da man..:beer:
SENT FROM THE DOG POUND
well... voodoo sound used to say it was working when I had the stock kernel... but it didn't sound like it... now it says it's working... and with this kernel... it sounds like it... thanks!!
Also...if anyone tries to do swap on your charge you need a level 8 sd card or higher...and I think ours is a four or three stock... anyways the hardware is too slow to keep up unless you upgrade your sd card...even if he does get the bugs out
Sent from my SCH-I510 using xda premium
lukegman said:
well... voodoo sound used to say it was working when I had the stock kernel... but it didn't sound like it... now it says it's working... and with this kernel... it sounds like it... thanks!!
Also...if anyone tries to do swap on your charge you need a level 8 sd card or higher...and I think ours is a four or three stock... anyways the hardware is too slow to keep up unless you upgrade your sd card...even if he does get the bugs out
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Oh, how I've missed Voodoo Sound!
Thank you. If been trying to get this to work as well, and not having a Charge anymore was making it difficult.
Sent from my HTC Rezound running CounterShrike 3.0 preview
awesome - will test this.
will this support EXT4? and if so, will conversion to EXT4 be the same as before (http://forum.xda-developers.com/showthread.php?t=1763951)
how about custom boot animations - as I'm installing this now, I do notice that there is no boot animation - just a blank screen for a bit.
also, per the install instructions, I presume we need to mount system within CWM first? I did wipe cache/dalvik just to be on the safe side.
I presume that if we lose root, we'll need to flash supersu again? edit: I did NOT lose root. but I have noticed the phone to be a bit sluggish. I'll give it some time though.
thanks!
jco23 said:
awesome - will test this.
will this support EXT4? and if so, will conversion to EXT4 be the same as before (http://forum.xda-developers.com/showthread.php?t=1763951)
how about custom boot animations?
Click to expand...
Click to collapse
EXT4 support is enabled. I have not tested it yet, but it's the same as it was before. If you do try it, let me know how it goes!
I think I'm going to try to pull in the full voodoo lagfix conversion script. It looks like the original supercurio source link at http://github.com/voodoo-project/lagfix is dead, though. I guess I'll probably have to diff out the changes from imoseyon's lean kernel repo, which appears to be over here: https://github.com/imoseyon/leanKernel-i500-gingerbread/tree/i510
The custom boot animations from Tweaked/Tweaktools are working for me.
{
"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"
}
converting to EXT4 now...
success!
however, my phone is still sluggish. i did experience the same sluggishness when attempting to install 0524 charge kernel earlier this week.
hoping this goes away over time - perhaps I need to reflash tweak?
otherwise, everything seems to work - I will check my wifi when I get home.
Ohhh buddy! ! Thanks bro...
Lost root just fyi
jco23 said:
awesome - will test this.
will this support EXT4? and if so, will conversion to EXT4 be the same as before (http://forum.xda-developers.com/showthread.php?t=1763951)
how about custom boot animations - as I'm installing this now, I do notice that there is no boot animation - just a blank screen for a bit.
also, per the install instructions, I presume we need to mount system within CWM first? I did wipe cache/dalvik just to be on the safe side.
I presume that if we lose root, we'll need to flash supersu again? edit: I did NOT lose root. but I have noticed the phone to be a bit sluggish. I'll give it some time though.
thanks!
Click to expand...
Click to collapse
jco23 said:
converting to EXT4 now...
success!
however, my phone is still sluggish. i did experience the same sluggishness when attempting to install 0524 charge kernel earlier this week.
hoping this goes away over time - perhaps I need to reflash tweak?
otherwise, everything seems to work - I will check my wifi when I get home.
Click to expand...
Click to collapse
jco, I found that the "sio" io scheduler is great and super-fast on a fresh factory-wiped phone. However, if you've got a lot of memory contention, its lack of fairness tends to make the phone feel jerky and intermittently unresponsive. If you're like me and have five email accounts and half-a-dozen other background apps running all the time, you might get better results with cfq or bfq. Tegrak Overclock will let you switch and test on the fly. Give it a shot, let me know if it helps?
I'm going to let you guys be my guinea pigs. Not only is my Charge my daily driver, it's my only driver. On EP4 and FP1 my phone definitely felt faster on EXT4. But then the FP5 update blew that right away. Now with dSlice's scripts and tweaks my phone is now the fastest it's ever been.
kynalvarus said:
jco, I found that the "sio" io scheduler is great and super-fast on a fresh factory-wiped phone. However, if you've got a lot of memory contention, its lack of fairness tends to make the phone feel jerky and intermittently unresponsive. If you're like me and have five email accounts and half-a-dozen other background apps running all the time, you might get better results with cfq or bfq. Tegrak Overclock will let you switch and test on the fly. Give it a shot, let me know if it helps?
Click to expand...
Click to collapse
hmm... perhaps.
anyhow, sluggish is gone now. zippier than ever! thanks!
next test is battery performance.... will report back on Monday.
kynalvarus said:
The custom boot animations from Tweaked/Tweaktools are working for me.
Click to expand...
Click to collapse
With the boot animations, does yours give you a black screen for awhile and the do the boot animation real quick? I can change the boot animation, but I only get a split second of the animation then the slight vibration and it turns on. I had the same issue running 0524. Any way to remove that delay from Samsung logo to boot animation?
I never really noticed much of a difference between ext4 and rfs. I'd be willing to try it again though.
What do you mean by full voodoo? As far as I can tell it is working fine.
Maybe full voltage support? Add far as I can tell, the Charge only gets certain options in the Voltage Control app from the market. (See their pictures vs the actual app) Looks like it offers more customization that our kernel doesn't yet support.
Also it looks like a while back the Charge had the Fast Charge function? That would be nice .
Also I heard of a thing called looping support. Have you heard of it? It allows you to run a different OS like Ubuntu or Back Track 5 on your phone! I know with our limited ram and only one processor, this could be slow, our not even worth it, but it might be something fun to play with.
Three are all just ideas, and I have no idea how to get them working. I just figured I would give you some options. I'm always willing to be the test dummy!
Thanks for your work and time.
Sent from my SCH-I510 using Xparent Red Tapatalk 2
tmanschuette said:
Maybe full voltage support? Add far as I can tell, the Charge only gets certain options in the Voltage Control app from the market. (See their pictures vs the actual app) Looks like it offers more customization that our kernel doesn't yet support.
Also it looks like a while back the Charge had the Fast Charge function? That would be nice .
Also I heard of a thing called looping support. Have you heard of it? It allows you to run a different OS like Ubuntu or Back Track 5 on your phone! I know with our limited ram and only one processor, this could be slow, our not even worth it, but it might be something fun to play with.
Thanks for your work and time.
Click to expand...
Click to collapse
In order to have "full voltage support" you need an app that can tweak those parameters on the fly. The kernel has default voltage settings compiled in for each defined CPU level, and lots of extra levels defined over the stock. Without some interface for voltage adjustment, though, you're not going to have much control.
Regarding "Fast Charge" and looping support, I'm willing to look. Do you have links to more detail on these features?
There's a couple of variants of fast charge. The most common (and safest) is to provide a way to allow any power source to be recognized as AC so the phone can pull as much power from the port as it will allow. This is usually controlled as a toggle app (such as this one) or as a CPU control app. You generally need to be able to enable/disable it because it generally (in my experience) disables USB connectivity when it's enable.
Loop device support allows for pseudo-devices (or virtual devices) to be created that can be mounted as a block device. Different OS's like Ubuntu require that it be supported because they use a .img file instead of a physical partition as disk, so they need a loop device to mount the image in.
HDid
jco23 said:
hmm... perhaps.
anyhow, sluggish is gone now. zippier than ever! thanks!
next test is battery performance.... will report back on Monday.
Click to expand...
Click to collapse
Did you reflash /factory wipe or did the phone just start running better? When I first installed tweaked 3.1 and slice tweaks it took a few days but phone is nice now... Never done this kernel thing before... Also to OP I believe I flashed CWM from odin using download method... If I'm mistaken will it just not flash correctly or could it cause trouble?
thechaoz said:
HDid
Did you reflash /factory wipe or did the phone just start running better? When I first installed tweaked 3.1 and slice tweaks it took a few days but phone is nice now... Never done this kernel thing before... Also to OP I believe I flashed CWM from odin using download method... If I'm mistaken will it just not flash correctly or could it cause trouble?
Click to expand...
Click to collapse
nope. just ironed itself out. although, I do not recall the other kernels taking that long to smooth out while on FP1.
I have not done a factory reset in quite some time - but I am a frequent wiper of cache/dalvik when flashing stuff.
the process of flashing kernels via CWM is no really different than flashing a theme, mod, or ROM
thanks jco23... i haven't done ext4 that way since a long time ago with my fascinate... i still love the robot voice...mine Is zippy too...
i know the ext4 filing system is an upgraded filing system for Linux...so it has to be better right?
and first time ext4 converters... the Samsung logo will be there for a good fifteen minutes...and it will be a good wait b4 you hear the robot lady...
Sent from my SCH-I510 using xda premium
Related
FRF91 Droid2 AOSP Final
A True Vanilla Froyo Expiernce For Your Droid2
By AngDroid, Matt4542 & Drod2169
{
"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"
}
Twitter:
AngDroid
Matt4542
Drod2169
IRC:
http://webchat.freenode.net/ #fissionrom
Thank you to all who tested. Now start getting your phones ready for the final build.
Themers:
Check Post #2 for a package of app & framework files. A good majority of the apps are from FRF91 Vanilla Android build so if you have packages that already work with that build then most should work here. Please make sure all packages are compatible. Please use the framework-res.apk provided since it is unique to this ROM. It is much different than the OEM Drodi2 packages.
ROM Developers:
Feel free to use this as a base for your own ROM. Please just respect us and give Matt, Drod and myself the proper credit and a link back to the threads.
History:
Being bored one day and sick of Blur with all the extra services I started to rip the ROM apart. Finally getting it as clean as I can and being forced to have a bit of blur I began a search on how to get rid of it all. I ended up on the MotoDev website to see what I can find when I bumped into the D2 SDK. Shockingly it was a plain vanilla build of Android. I thought why not and tried to boot it up. Ii did ( see first video here[/URL] ) with lots of bugs. The screen res as all off and we had no radio or many other hardware functions. On top of that it ran like a turtle stuck in some molasses. I sent a message of my my buddy Matt4542 and our journey began. From there Drod and I hooked up and now we have this. It has been a long rough week getting this sucker to where it is now. It was fun, frustrating and we nearly killed each other a few times but all ended well since we have a great finished project.
We kind of built AOSP ROM by hand. Some may say it is not a true AOSP ROM but it is. There is no difference between this build and a true AOSP ROM besides any tweaks that the developer may add when creating a ROM from source. We had no choice to do it this way since Moto locked us out of the bootloader (for now and next project). Many of the apps are built from source. About 90% of the app folder is built from source. We added some packages from the D2 that are a bit better and required for hardware reasons. There is NO Blur left in the ROM but for a moto-res.apk file that is required by the framework.
What will this ROM do?
It will give you a true Android Vanilla experience much in the same way the Original Droid (OD) did. It is not loaded with bloatware and everything functions as it should. Facebook will sync with your contacts and you will not have all of your memory being used by wasteful stuff on top of much more. Your phone will run more smoothly and feel a lot faster.
What can you do to help?
The most important thing is to provide feedback. When reporting bugs please be clear and with detailed explanation. Do not say this does not work and leave it that. The more feedback you provide will make it easier and quicker for us to kill any bugs. You may also give us a small donation to help with our continuing development of ROM and *POSSIBLY* get this bootlader cracked. It cannot be done with one device. I have a couple of friends who have experience with low level programming of chips and with their help maybe it can get done. They are Blackberry guys and not going to buy a device just for this. This is nothing more than a promise that it will be tried. I cannot say when and IF it can be done so please keep the questions to a minimum about it. If the project takes off then I will have updates. You can donate to the project by clicking HERE.
Install Instructions: - YOU MUST FOLLOW ALL INSTRUCTIONS!!!
BACKUP your phone using Bootstrap before installing any ROMs so you can go back to your current setup if anything fails.
Pre-Installation Tasks:
Before you install this ROM or any ROM you will need to have root and have Bootstrap on your phone. You can find out how to do all that HERE.
BACKUP your phone using Bootstrap before installing any ROMs so you can go back to your current setup if anything fails. Notice I said that TWICE!!!
Download and place ROM on SD Card
Open Bootstrap and tap Bootstrap Recovery
Reboot into Recovery
Create Backup
Mount System
Wipe Cache -You may choose not to wipe but MAY have problems
Wipe Data - You may choose not to wipe but MAY have problems
Mount System and Data - Yes double check that both are MOUNTED (Reads UNMOUNT when MOUNTED)
Install Zip from SD Card
Choose Zip from SD Card
Select your ROM
Yes - Install
Wipe Cache Again - You may choose not to wipe but MAY have problems
Wipe Data Again - You may choose not to wipe but MAY have problems
Perform a Factory Reset through Android - Settings > Privacy > Factory Data Reset. Wiping Cache and Data from recovery is not enough.
Reboot
Enjoy!
Download HERE
Themes:
Themers:
App & Framework Files - Please only use these files to create your themes. This ROM is unique to the combo of files.
Black (HTC) Status Bar
Droid 2 Theme
Add-Ons: - Install - Do not wipe anything. Just mount system, select your zip file and install.
On Screen Keyboard
Droid 2 Multi -Touch Keyboard
Android Keyboard - Default with ROM
Gallery
Droid 2 Gallery
Android Gallery - Default with ROM
Bugs:
Compass Calibrate FC in settings. - No Fix yet.
HotFix:
AOSP Dialer working now
Download HERE
Please donate to project so I can get this ROM up 100% on both devices
holding for later so sgrg
You have no idea how anxious I am to try this. Soon as I get home its going on. Thanks!
Sent from my DROID2 using XDA App
I'll be the first to ask - do we need to do all of the wipes if we are upgrading from RC1?
is this the final build?? cause its version 1.0 and are you guys going to provide ota updates?? other than that rom looks AWESOME
Appreciate the hard work guys!
Works great! So much better than the stock D2 ROM.
Cell standby is still an issue
So far so good.
Only two minor things. There is no easy to get to end-call button, which you already know about, and it seems like there is not speech to text support. Not that I really use speech to text, but it could come in handy.
Edit: Nevermind. Might just need to enable it in settings.
Contact Ringtones still don't work
Otherwise, it's gRRRRRRRRReat!
Seems like some bad blood brewing over this ROM on the droidforums page for it. AngDroid/MotoBoy, we all greatly appreciate your work (you too Matt4542! (and anyone else who doesn't get as much time in the lime light!)). As long as you are satisfied with the outcome of the ROM we all appreciate you sharing it with us. Just ignore the lamers that expect you to jump at their every beck and call. It's the first AOSP type ROM for the Droid 2, very first of it's kind for a very locked down phone, which in and of itself is a great accomplishment. If you ever fix anything in Fission, great, if not, I'll continue to look forward to what you develop in the future.
I'm still also curious about your twitter post from the other day, talking about your new Fusion ROM series. Interested to see how that one differs from both stock and Fission.
I am getting the USB problem like I was getting in Beta II. It would connect fine when I first loaded the rom up, and then half the day would pass by and then I can't connect the phone to the computer. Kind of weird. Pretty sure that I can charge from the wall. Just not sure why the USB isn't working.
darkonion said:
I am getting the USB problem like I was getting in Beta II. It would connect fine when I first loaded the rom up, and then half the day would pass by and then I can't connect the phone to the computer. Kind of weird. Pretty sure that I can charge from the wall. Just not sure why the USB isn't working.
Click to expand...
Click to collapse
I wonder if it's something underlying with your phone that's causing that issue. You'd think if it were a common bug you'd see other users complaining about it (as this thread on droid forums is about 8 pages long at this point). Given that it's you, who wrote the tutorials for some of the early D2 stuff, I have no doubt you followed all the steps for installing the ROM. Did you happen to SBF and start stock before going to Fission? I wonder if it could have resulted from flashing over another ROM. Very strange issue though, when I get a good chance to roll my phone up to Fission 1.0 I'll see if I experience the same thing (Thursday is probably a good day to flash, too many phone calls I can't miss between then and now).
bladearronwey said:
I wonder if it's something underlying with your phone that's causing that issue. You'd think if it were a common bug you'd see other users complaining about it (as this thread on droid forums is about 8 pages long at this point). Given that it's you, who wrote the tutorials for some of the early D2 stuff, I have no doubt you followed all the steps for installing the ROM. Did you happen to SBF and start stock before going to Fission? I wonder if it could have resulted from flashing over another ROM. Very strange issue though, when I get a good chance to roll my phone up to Fission 1.0 I'll see if I experience the same thing (Thursday is probably a good day to flash, too many phone calls I can't miss between then and now).
Click to expand...
Click to collapse
Before concluding the phone I would ask if it were happening before this rom. Have you tried any other usb mode to see if it recognizes it? I'm sure you have because you are darkonion...
wsfanatic said:
Works great! So much better than the stock D2 ROM.
Cell standby is still an issue
Click to expand...
Click to collapse
How is it an issue? If your phone is on for 10 hours and you use cell for 1 hour of course it is going to eat the greatest percentage of battery use. The issue is the time is off now and then.
one. said:
Contact Ringtones still don't work
Otherwise, it's gRRRRRRRRReat!
Click to expand...
Click to collapse
We tested this on IRC and it is working for everyone who tested.
if ud like a phone apk like this hit me up with a pm and ill send it to u
Does this ROM contain the ability to link contacts?
The reason I ask is because there are a few facebook contacts of mine that do not list their numbers on their profile but I have their numbers in my phone book. And when I installed Fission RC1, Facebook will list them as a contact but will not show them with the profile and with phone numbers I have in my phone. I recall being able to have that ability to link contacts in the stock D2 rom. Is this feature part of the Blur crap?
It really wouldn't even be an issue if the Facebook contacts were not read-only. I'd just add the numbers to their contact information on the phone then... But I can't. Go Facebook.
Go to the contact u want. Hit menu>edit then hit menu>join then u can pick the facebook contact u want to link it to
Sent from my DROID2
whezzel said:
if ud like a phone apk like this hit me up with a pm and ill send it to u
Click to expand...
Click to collapse
Do the sliders work on incoming call? If so can you pm me a link to it please. Does the call log work?
whezzel said:
Go to the contact u want. Hit menu>edit then hit menu>join then u can pick the facebook contact u want to link it to
Sent from my DROID2
Click to expand...
Click to collapse
And I spent hours looking for this option and it was right in front of my face.. Figures.
Ya learn something new everyday.... Thanks!
Announcement: I highly suggest you flash void. - http://forum.xda-developers.com/showthread.php?t=887281
Well, here's one more ROM for you guys: Megatron.
Why the name? Seemed only logical considering the name of our device, Optimus One.
It's basically a ROM tweaked for performance while retaining a decent battery usage. Also, with this ROM, you won't need to flash any other tweaks.
I daresay it's so far the speediest ROM for LG P500.
Features:
v2:
to be updated
v1:
root + superuser + busybox
APKs deodexed + zipaligned + png-optimized
apps2sd + dalvik2sd [1]
performance tweaks: (JIT, hardware acceleration, etc) [2]
includes drellisdee's custom kernel [3]
kernel repacked to set onboot the scheduler to interactive (tweak)
applications removed: App Advisor, Layar, Twitter, Facebook, LG Home, Think Office, Update notifications and Twitter [4]
applications changed: Genie widget (now transparent), Music (imported from CM)
applications added: Titanium backup, File Manager (imported from CM) and the awesome LauncherPro [5]
ringtones, notification and alarm sounds added (including iPhone ones)
changed boot animation to a more cute one
auto-overclock to 728Mhz and possibility to easily revert (minitron tweak) [6]
[1] Rather than move_cache_sd program used in another ROMs, I use another method for moving dalvik-cache to SDcard since sometimes using the aforementioned program won't work successfully. It's a known issue of Dsixda's kitchen.
[2] Heapsize: 32MB; without a doubt the best value.
[3] Check the original thread here and if you can, buy him some beer.
[4] I left CarHome due to popular demand.
[5] Titanium backup will allow you to uninstall any system application and to backup the ones you install. LauncherPro is in my opinion, way better (performance-wise) than ADW.
[6] As far as I've read, 728Mhz is stable for everyone til now.
Click to expand...
Click to collapse
Requirements:
In order to flash this ROM, you'll need on your device:
Having read the feature list and notes above
Root (check thread)
Drellisdee's custom recovery (check thread)
Class 4 SDcard or higher (bench it with h2testw)
Megatron (download it here)
How to flash:
First, reboot into recovery via 3-button-combo, ADB, terminal, w/e.
Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
Wipe data (data,cache,dalvik-cache,ext).
Connect the device to PC, copy Megatron over to the SDcard, disconnect.
Flash it via "flash zip from sdcard"
Reboot
Read important notes below
That's it.
Important notes:
* There were some reports on other ROMs that battery usage was very high, especially on standby. While this ROM should perform better, it won't still have as good battery usage as stock ROM mainly due to the scaling governor being set to interactive. Also because of this reason, benchmarks could be slightly lower. I however promise that the overall experience and snappiness will be quite satisfying.
* I've made an easy and friendly way to decrease the clock back to stock 600Mhz. Instead of needing to use SetCPU, you just need to create a folder in your SDcard called "minitron" (without the ""), then reboot your phone. Your clock will be now back to 600Mhz. If you wish to revert it to the default 728Mhz, just delete the folder and reboot your phone again. Since the voltage is the same for both clocks, battery consumption should be around the same too. If for some odd reason, you get a boot loop, it means your phone doesn't support (*gasp*) a 728Mhz clock. To avoid a boot loop, go back to the custom recovery, toggle sdcard-pc connection and create the "minitron" (without the "") folder. Reboot, should be fine.
* Remember, you won't need to flash anything else. Everything's here.
As you already know, I cannot be held responsible for any damage you may cause to your phone by following these instructions. Every step taken is of your entire responsability.
Testimonials:
* "I noticed that the phone was another! much better performance! I did all the tests and there are no problems!"
* "This Rom is just... Amazing!!!"
* "Feedback: working nicely untill now. So far so good - the best ROM yet"
* "Great work , phone is workin faster and booting 2times better now great work."
* "So far I can say it is arguably fast. Phone is super snappy and responsive."
Time to see for yourself.
Just remember, it's still an experimental ROM.
-reserved-
Thanks for the work, though I think I'll be passing for right now.
Auto OCd kernel with way to revert is a bad idea at this point in that kernel. I would do it the other way around. Let it be a "MegatronMax" (or something like that) folder to ENABLE the OC, but leave it at 600MHz till more testing has been done. Just because the volt is the same doesn't mean its going to perform as well long run. Not even sure Interactive will be better than say conservative because of the excessive ramping up and down in freq. I have seen in interactive. I guess bottom line is, you shouldn't include a beta kernel yet in your ROM and default it OCd. At this point in development I think you should let the users decide if they want to test out these kernel features themselves because it is easy enough for flash the kernel back and forth.
http://forum.xda-developers.com/showthread.php?t=866774
Plus the author of the kernel requested that you DO NOT include it in ROMs, but rather point users to that thread.
Other than the kernel issues, seems like it will work well for those who want those features.
Just my 2 cents, seems like a decent enough ROM, like to see how it works for people.
eigokyoukan said:
Auto OCd kernel with way to revert is a bad idea at this point in that kernel. I would do it the other way around. Let it be a "MegatronMax" (or something like that) folder to ENABLE the OC, but leave it at 600MHz till more testing has been done. Just because the volt is the same doesn't mean its going to perform as well long run. Not even sure Interactive will be better than say conservative because of the excessive ramping up and down in freq. I have seen in interactive. I guess bottom line is, you shouldn't include a beta kernel yet in your ROM and default it OCd. At this point in development I think you should let the users decide if they want to test out these kernel features themselves because it is easy enough for flash the kernel back and forth.
Click to expand...
Click to collapse
Been using it for days and no complaint.
Like I said, it's a performance-oriented ROM. Default OC makes sense to me.
If people are scared of long-term effects, they should Minitron-it then.
Anyway, I'll update the thread's title.
And interactive is way better than anything to be honest. It will even be the next default scheduler in CyanogenMOD.
eigokyoukan said:
Plus the author of the kernel requested that you DO NOT include it in ROMs, but rather point users to that thread.
Click to expand...
Click to collapse
Didn't read that and it's the first request of the kind I've seen.
For user's comfort, custom kernels often tag along with custom ROMs. Protocol has always been to credit the author, point to original thread and urge for a donation. At least to what I'm used to. However, if he insists on this and contacts me directly stating he really doesn't want his kernel included on a ROM, I will abide and remove the whole ROM since it loses its raison d'être.
Definitely not trying to flame or troll man
That was just my opinion on the matter. I am sure there are many people who will install and enjoy your work.
It is not uncommon to not want your work bundled, but at least you gave credit. I see too often credit not even given for others discoveries and hard work.
I still say default OC is a bad idea until we understand the full long term effects of having this hardware 700+MHz, but then again, this will start getting it tested.
Have installed the ROM. Works Great, No problems so far. Like the LP. But I would like to have an option to install themes and so one. That would be fantastic.
Thanks!
EDIT: Solved
There is a reason I set max freq on boot to 600mhz in kernel as its to prevent users from getting stuck in a boot loop at a speed thats too great for their device. If you kernel panic it will reboot back to stock max as as had it set up. I did also have in my post not to repack kernel in rom and posted source so rom makers could build their own variant to use. I'm not going to ask for you to pull rom however as I see no reason for that. I just made it so it would reach as broad an audience as possible even those that don't want to overclock as its optional as I had it setup. Also, by using koush's any kernel its compatible with virtually any rom.
Noejn, I've learned the hard way just because your phone runs ok at xxx freq doesn't mean others will.
hello Noejn be honest, I have updated this roms just because I had the famous problem "reboot (reset) the phone" as soon as I put everything, I noticed that the phone was another! much better performance! I did all the tests and there are no problems!
the only thing, there is more and reset!
is a week that I bought, and I can not figure out how to solve this problem you know anything Noejn
However good the ROM recommend it!
eigokyoukan said:
Definitely not trying to flame or troll man
That was just my opinion on the matter. I am sure there are many people who will install and enjoy your work..
Click to expand...
Click to collapse
Yea, no worries. Sorry if I seemed harsh in my reply, not my intention.
I do have a different opinion though, slightly more optimist.
Since the voltage is the same for both clocks and the cpu only peaks if called, I don't think there will be much overheating. Also, I've never heard of any MSM7227 that toasted itself or his hardware neighbours.
That being said, you may think it's a leap of faith but I find it perfectly safe to use a 728Mhz clock as default. I may be wrong but let's hope not.
drellisdee said:
Noejn, I've learned the hard way just because your phone runs ok at xxx freq doesn't mean others will.
Click to expand...
Click to collapse
I understand that.
So far, the least stable clock that someone had on your awesome kernel was 748. Even so, as a safety measure, I've set it @ ~728. If for some reason there's someone out there that gets a boot loop, he just have to go to the custom recovery, toggle the sdcard-pc and create "minitron" folder. Done, 600Mhz!
Also, thanks for officially letting me use your kernel on this ROM.
fr4nkr0c said:
hello Noejn be honest, I have updated this roms just because I had the famous problem "reboot (reset) the phone" as soon as I put everything, I noticed that the phone was another! much better performance! I did all the tests and there are no problems!
the only thing, there is more and reset!
is a week that I bought, and I can not figure out how to solve this problem you know anything Noejn
However good the ROM recommend it!
Click to expand...
Click to collapse
I'm glad you found it speedy!
Regarding your reboot problem that happened before, even on other ROMs, sounds to me it is a phone matter. Shouldn't you allege malfunctioning to your carrier and get the phone switched?
* Quadrant (w/ default options) attached to main post
* Forgot to add to features a different boot animation
i say thumbs up just for the name , not to mention the rom
I know there are some differences, but would this work on an Optimus T (P509)? I've been looking around for a rom and can't seem to find anything as promising as this. Any help is always appreciated.
Optimus T = O1 for T-mobile
gemarc said:
Optimus T = O1 for T-mobile
Click to expand...
Click to collapse
Yes, I know, but that wasn't my question. I understand that the processor in the O1 is MSM7627 and the Optimus T has a MSM7227. Since the kernel was made for the O1 would I need to find a different compatible kernel for this rom on the Optimus T or would this OC'd kernel work? I'm willing to test it, but I just wanted an opinion before I started.
Can you add an option on this ROM ? I would really like the softkeys to be always on.
Congratulations for your work !
Sent from my LG-P500 using XDA App
This Rom is just... Amazing!!!
Congrats
l30r0 said:
I know there are some differences, but would this work on an Optimus T (P509)? I've been looking around for a rom and can't seem to find anything as promising as this. Any help is always appreciated.
Click to expand...
Click to collapse
i think there is a ThundeROM version (originaly for optimus S) being adjusted for optimus T (not optimus one tho )
try checking androidcentral if i remember right
Nice job
xilw3r said:
i think there is a ThundeROM version (originaly for optimus S) being adjusted for optimus T (not optimus one tho )
try checking androidcentral if i remember right
Click to expand...
Click to collapse
thanks for the tip.
do games run better with this rom?
{
"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"
}
Virtuous Unity is the first custom Sense 3.0 ROM, scaled for WVGA screens, to be based on an official shipping release from HTC (1.45.401.2).
The entire ROM is brand new, taking no application or framework components from any prior Sense 3 releases.
Unity is the result of a collaborative, team effort by the following developers:
Flemmard
Diamondback2010
rmk40
chrisch1974
m-deejay
seo
eViL D:
cypis
cjward23
Screenshots
Features
Based on the official Sensation shipping ROM (1.45.401.2).
Ported for full functionality on each supported devices. Additional device support is being added regularly.
Resized for WVGA (800x480) displays, using a purpose built tool to modify HTC's proprietary m10 binaries, developed by Flemmard and Diamondback.
Heavily optimized for fluid performance and usability.
Overclocked kernels with numerous additional kernel modules.
Built-in screen state frequency scaling (1.2Ghz-245MHz/ondemand screen-on, 806Mhz-245Mz/conservative screen-off), via custom built Virtuous_OC C daemon.
Trackpad wake support (DesireZ/G2 and MT4G only).
WiFi calling (T-Mobile USA only).
Fully functional device hardware, including wifi, bluetooth, camera, camcorder, etc.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Supported Devices
Desire HD
Desire Z
Desire S
Incredible S
Inspire 4G
myTouch 4G
Porting Information and Credits
There has been an enormous amount of interest surrounding utilizing components or modifications from our ROMs. To this point, our policy was that any such work needed to explicitly be approved by the team. The fact of the matter is that the policy is simply not enforceable and any time consumed working to enforce it detracts from the time we have to work on Android (which is what we really enjoy). As such, we’ve decided to go in a different direction.
Going forward, ROM developers are welcome to utilize any portions of our ROM which are of interest.
Our only requirement is that you let us know about what you’re doing by sending an email to (devteam|at|virtuousrom.com), credit the Virtuous Team in your thread(s) and provide a link to our website. No response on our part is required whatsoever, we’re just interested to hear about how our work is helping you.
Our plan is to continue to innovate and push the envelop of ROM development; with the goal of staying enough ahead of the curve to merit a desire to clone our work.
hrk - Allowing use of ghostySMS Vision version.
cypis - For his awesome Unity-banner
robocik - Tips regarding APK compression.
capychimp - Tips with DHD audio optimization.
HTC/Google- For building such a good base system.
Important Notes
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Bugs and Errors
To ease the process of reporting bugs to the team, we made a public bugtracker where you can report the bugs you found. Please make sure you read all the existing entries there to avoid doubling the errors.
The bugtracker is located here.
Device specific information
Download :: Changelog :: More Information(Official Website of Virtuous ROM)Check out our forums
Install instructions (thanks to lollylost100):
1. Make a full wipe (please don't use Full Wipe 1.5 (EXT4) or such tools)
2. Flash ROM
3. Reboot
Please keep in mind:
You can always try to do a non wipe install, but we can't provide you support in this case.
If you find any errors in the ROM and you have NOT wiped before, please wipe and see if the errors persists.
Special features
This ROM has some unique or not widely known features which I want to explain here.
Screenshot
This ROM (in fact most Sense 3 ROMs) has the unique feature to make screenshots without any additional app.
Just Hold the "Power"-Button and then press "Home" at the same time and the phone will save your screenshot in the Images folder on you SD-Card.
OC Daemon
This ROM deals with overclocking a little bit different than other ROMs. To get further information read this post.
Fancy input animations
Unfortunately HTC removed from all their Sense ROMs the "open" and "close" animations for the keyboard.
Thanks to seo we were able to get them back
There are two different animation versions. The normal one is always activated and there is also no way to deactivate it.
The second "fancy" version can be enabled via the app "Spare Parts" which is in the Android Market.
Custom user app install during first boot
The ROM has the ability to automatically install custom user apps during the first boot (after a wipe)
All you need to do is the following:
Create an folder on your SD card and name it virtuous_unity
Create another folder inside virtuous_unity folder and name it 'app.user'
Copy all the desired apps in this directory in there paketname form, for example: 'com.quoord.tapatalkxda.activity.apk'
Now flash the ROM via your recovery
During the first boot the apps get installed from your SD card, as this will take a while, don't get impatient
Release strategy
We are planing to release our ROM in the future every week on the same day and around the same time.
This point in time will be every Monday night (GMT). Which is ca. 24h from NOW.
If there are no MAJOR bugs we will release what ever we have done at this time.
Saturday night (GMT) is the so called feature freeze, then the ROM will enter the testing phase. It gets tested until monday and then the team will talk about the results.
Once everything is approved we'll release the next version.
As you should know now when the next version arrives I won't answer ANY questions concerning ETAs.
Further information and support at #virtuousrom on Freenode
Changelog
Our changelog lives here.
Supported devices
Desire HD (Ace)
Desire Z (Vision)
Desire S (Saga)
Incredible S (Vivo)
Inspire 4G
T-Mobile MT4G (Glacier)
Addons for v1.27.0
CRT patch (add CRT animation): Flash in recovery.
NO CRT patch (revert CRT animation back to stock): Flash in recovery.
Introduction to the new Overclocking Daemon
This ROM features a completely new way of Overclocking and managing screen states.
The History
But before explaining it further, let's talk about previous solutions.
There are several different approaches to archieve "screen-state-scaling".
That means basically that the govenor changes if you turn the screen off and changes back to normal when turning the screen on.
This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.
The solutions so far were:
App like SetCPU, which change automatically the govenor based on profiles
integrated solutions in the govenor itself
Both these solutions have major problems.
The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the govenors (up to 7 seconds). This leads mostly to major lag in the lockscreen.
The second solution is the smartass govenor. It has already a screen-state-scaling included, so it reduces the frequency when the screen turn off.
This could be a really nice solution but it has some problems too.
Smartass most of the time is not really stable and has problems with its frequency scaling.
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the govenors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are plaing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
How to adjust the daemon
The daemon is configured with 6 files in the folder /system/etc/virtuous_oc/.
There are 3 files for the wake state and 3 for the sleep state. For each state one file for the govenor, one for the minimal frequency and one for the maximal frequency.
You can easily edit these files eg. with RootExplorer or any other app which can edit system files. So you can adjust the frequencies and the govenor for each state just like with SetCPU.
In order to get the available frequencies for the current kernel, just open your favorite terminal app and type
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
You could also use adb shell to show the frequencies on your computer.
To get the available govenors use a similar approach:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Please make sure, you are entering the right values in the daemon's config files.
reserved for future use4
At the risk of sounding like a complete ass, if we are already running VU 1.0, do we still need to wipe data, or can we leave that partition be? I'm asking because the previous thread for 1.0 indicated that future releases would not require a full wipe, so the instructions above are not entirely clear for those of us who are already on board.
Thanks for keeping up the great work!!!!!
BillTheCat said:
At the risk of sounding like a complete ass, if we are already running VU 1.0, do we still need to wipe data, or can we leave that partition be? I'm asking because the previous thread for 1.0 indicated that future releases would not require a full wipe, so the instructions above are not entirely clear for those of us who are already on board.
Thanks for keeping up the great work!!!!!
Click to expand...
Click to collapse
Wait for me to finish the post
Easy way : no wipe = no support, wipe = support
LOL! Sorry, pulled the trigger a bit too quick on that. Been anxiously looking forward to this release and jumped the gun.
Do the widgets with buttons still hang below Rosie or has that been fixed? I don't see it in the change log....
Nick12484 said:
Do the widgets with buttons still hang below Rosie or has that been fixed? I don't see it in the change log....
Click to expand...
Click to collapse
If you don't see it in the changelog....
No not fixed right now, not such a big issue there were more important things
Fix would be easy but dirty, i'm trying to find a better way.
Diamondback2010 said:
If you don't see it in the changelog....
No not fixed right now, not such a big issue there were more important things
Fix would be easy but dirty, i'm trying to find a better way.
Click to expand...
Click to collapse
Oh ok, just asking. in the issues that were listed in the Desire HD thread it had said it was fixed in the next version so I was confused when I didn't see it. Great ROM thanks
Nick12484 said:
Oh ok, just asking. in the issues that were listed in the Desire HD thread it had said it was fixed in the next version so I was confused when I didn't see it. Great ROM thanks
Click to expand...
Click to collapse
Oh yea, sorry my bad Deleted a line to much
Diamond, will all APKs in the virtuous_unity folder automatically installed during flashing the ROM?
destroyer67 said:
Diamond, will all APKs in the virtuous_unity folder automatically installed during flashing the ROM?
Click to expand...
Click to collapse
You can't put custom apps in there atm, this feature is planned for a future version
Ok, I had trouble flashing. Individually wiped each partition (data/cache/system/dalvik), then also wiped via 'factory reset' for extra measure. Then mounted /system and /data, chose .zip file and get the error: "Error in /sdcard/virtuous_unity....zip (Status 1). Installation aborted.
When I **UNmounted** /data and /system, then flashed, it worked.
BillTheCat said:
Ok, I had trouble flashing. Individually wiped each partition (data/cache/system/dalvik), then also wiped via 'factory reset' for extra measure. Then mounted /system and /data, chose .zip file and get the error: "Error in /sdcard/virtuous_unity....zip (Status 1). Installation aborted.
When I **UNmounted** /data and /system, then flashed, it worked.
Click to expand...
Click to collapse
Normally you don't need to mount. That was just a workaround in the first version.
Sent from my Desire HD using Tapatalk
Diamondback2010 said:
Normally you don't need to mount. That was just a workaround in the first version.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Cool. Suggest you amend the first post to indicate this.
And, for the record... WOW!
Holy $hit!!!!!
Cool.
Fast.
Stable.
What more can one ask?
ROM is excellent... tried it out yesterday. RMK was able to fix the issues I encounted when I first got this ROM.
Only issues, which I hope will be fixed/resolved ..
- The hanging of buttons from the widgets below dialer/phone button.
- Like RCMixKingdom, video playback in portrait mode is distorted.
Most of the widgets I use are affected by the low buttons, so until these are fixed .. I'm gonna stick with RCMix Kingdom.
Don't get me wrong here, ROM is excellent. Like the fact that the OC is built in without having to use an app to control .. fast, smooth etc etc .. definately a ROM I will keep my eye on, very promising
Be interesting to see if someone can port this into 2.3.4 instead of 2.3.3 .. LOL
*** EXCELLENT WORK PEOPLE ***
Hi man, this rom looks great, tell me what its the diference between this rom and rcmix3d?
What's the difference in this and rcmix? Reason I ask is i want sense 3.0,but with rcmix its sluggish for even oc'd to 1.5.
Edit: jamm13 must have posted his question as I was typing mine lol. Just didn't want it to seem like I didn't read the thread
Sent from my HTC Desire HD using XDA Premium App
{
"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"
}
This is the official bug report thread for Kyorarom. Seeing I get a lot of PMs from people who haven't got access to the developers thread already and they can't post in the official thread, I decided it's about time I make this public area for this purpose.
So report any bugs here and ask all your questions here.
Also note, please don't report bugs if you are on an old version unless even on the new version the bug isn't fixed. So say you report 'I'm on Kyorarom 0.1.0 and the browser doesn't work', you're just going to be told to update because bugs along those lines have long since been fixed.
Kyorarom Developers Thread
FAQs
Any frequently asked questions will go here.
Q: Can you upload to something other than Mediafire? It's blocked at my home/work/school/somewhere.
A: No. I like Mediafire and it's fast and I don't have to wait for like 5 hours and look at half a billion ads like you do on RapidShare, and Google Code has a terrible uploader and doesn't support large files (such as a ROM).
Q: A certain feature doesn't work on Fugumod. What's wrong?
A: Well to be honest, I usually don't know. This ROM is heavily built around G3MOD. A lot of important features in this ROM are built around G3MOD so I can't guarantee any success on Fugumod. If you experience a lot of issues on Fugumod + Kyorarom, then I suggest using Kyrillos' ROM. I'd love to debug these problems on Fugumod but it is a lot of effort switching between Fugumod and G3MOD all the time and considering the amount of projects I already have, and also a personal life I must maintain, it's too much effort sorry.
Q: Can I use Kyoraapp in my custom ROM?
A: Sorry but no. Kyoraapp is branded with the Kyorarom logo all over it because that's what it is for. I don't mind if someone puts it in their phone for themselves, but I don't want to see it in someone elses ROM if they have uploaded it. What you can use however is applock and applock_service and the init.d script S99_kyoralock and give me credit for them. Kyoraapp is actually just an interface. It doesn't do any of the processing for Kyoratweaks or Kyoralock. All of that nice stuff is done by the scripts I coded up. I did it that way because then I don't have to keep bugging moikop when I update the script. He just needs to add new options in the app when needed.
Q: What kernel do you recommend I use?
A: Well currently you have three main options:
1) Fugumod: This is proven to be reliable and stable and fast, however it has got a few quirks with Kyorarom and I lack the effort to debug for something I don't use. I'd rather spend my time using only G3MOD/Kyorakernel.
2) G3MOD: This has by far the most features out of any kernel for our phone. The problem is that for some it is way too many and it causes battery drain and instabilities. I love G3MOD but it can cause people problems and for those people I used to recommend trying Fugumod, however there is another option now...
3) Kyorakernel: This is built from the ground up. It's not a modification of G3MOD or Fugumod, this is a whole new kernel built from Samsungs source codes and it has features from G3MOD that we all love and are proven to be stable. Kyorakernel aims for simplicity, but also offering a broad featureset to make people not need to sacrifice too much. However I can't completely recommend it yet as it is still young.
Q: What will your next phone be?
A: It'll be another Samsung definitely. I have owned an LG in the past and it was good, but not amazing, HTC annoy me (the hardcore locking they do on the phone is ridiculous), Sony are evil, and Motorola are boring. My next phone will be Samsungs next top phone (Galaxy S3?).
Really you should try them all and see which works best for you.
How My Phone Is Set Up
ROM: Kyorarom
Kernel: Kyorakernel (OC version)
CPU Clocks:
- Screen On: 800-400MHz (lagfree)
- Screen Off: 600-83MHz (lagfree)
- Charging: 1000-400MHz (lagfree)
Undervolting: None (it doesn't like my phone)
Filesystems:
- system: ext4
- data: ext4
- cache: ext2
- sdext: ext2
G3MOD Data2SD Options:
- Hybrid Data2SD (app, log, dalvik-cache)
- Multi OS Data
- Bzip2 Multi OS Data Compression
Undervolting: no
Services Always On:
- imo.im signed in to Skype
- Google Sync enabled (Gmail, Contacts, Calendar, Google+)
- GoWeather sync
Networks: Always on Vodafone 3G (3.5G when in heavy use) (Sometimes on WiFi if 3G is playing up)
Battery Life: At least 40 hours of reasonable usage
If you need any further details, then just ask and I'll add them in.
hillbeast said:
How My Phone Is Set Up
ROM: Kyorarom
Kernel: G3MOD (OC version)
CPU Clocks:
- Screen On: 800-400MHz (lagfree)
- Screen Off: 600-83MHz (lagfree)
- Charging: 1000-400MHz (lagfree)
Undervolting: no
Services Always On:
- imo.im signed in to Skype
- Google Sync enabled (Gmail, Contacts, Calendar, Google+)
- GoWeather sync
- Battery Graph
Networks: Always on Vodafone 3G (3.5G when in heavy use) (Sometimes on WiFi if 3G is playing up)
Battery Life: At least 30 hours of reasonable usage
If you need any further details, then just ask and I'll add them in.
Click to expand...
Click to collapse
U did not undervolted, any disadvantage of undervolting?
Mohanshbhr said:
U did not undervolted, any disadvantage of undervolting?
Click to expand...
Click to collapse
No, there' no disadvantage of it, I just lack the effort to do all the testing for undervolting.
Messages not working
I have installed Kyorarom on my Samsung GT I5801...but whenever I try to open my messages my phone hangs up and stops working..What should I do?
toon.maggot said:
I have installed Kyorarom on my Samsung GT I5801...but whenever I try to open my messages my phone hangs up and stops working..What should I do?
Click to expand...
Click to collapse
In the SMS/MMS app?
Battery
Well that problem has been sorted out..Now the battery life ain't good...Lasts for 8-9 hours only...
toon.maggot said:
Well that problem has been sorted out..Now the battery life ain't good...Lasts for 8-9 hours only...
Click to expand...
Click to collapse
Let the battery run for about 3 or so cycles, if it's still bad then wipe the battery stats and let it run for another 3 cycles.
Thanks...Wil try that..By the way it is an amazing rom...
I've got this strange problem ever since I flashed v0.4.0b1 and v0.4.0b2. The phone stops responding all of a sudden and I've to press and hold the power button to restart it. I'm on the OC kernel and I even brought it down to 800MHz. Still no avail
No FC issues. Just random restarts.
I could use some help!
A couple of queries..How to uninstall system apps like the "dolphin browser"....And how to move some apps like Facebook to SD card.....?
Pwng3 said:
I've got this strange problem ever since I flashed v0.4.0b1 and v0.4.0b2. The phone stops responding all of a sudden and I've to press and hold the power button to restart it. I'm on the OC kernel and I even brought it down to 800MHz. Still no avail
No FC issues. Just random restarts.
I could use some help!
Click to expand...
Click to collapse
Did you do a data wipe after flashing?
toon.maggot said:
A couple of queries..How to uninstall system apps like the "dolphin browser"....And how to move some apps like Facebook to SD card.....?
Click to expand...
Click to collapse
You need to mount the system in rw and delete them from /system/app
To mount the system in rw, use Terminal Emulator and type mount -o rw,remount /dev/block/stl6 /system
hillbeast said:
Did you do a data wipe after flashing?
Click to expand...
Click to collapse
Errm... Nopes. I assumed that wasn't necessary because I had just applied the update and not flashed the whole ROM. I reboot-ed the phone a couple of times and right now it seems to be stable. But if the phone does stop responding again, I shall wipe data. Thanks
Pwng3 said:
Errm... Nopes. I assumed that wasn't necessary because I had just applied the update and not flashed the whole ROM. I reboot-ed the phone a couple of times and right now it seems to be stable. But if the phone does stop responding again, I shall wipe data. Thanks
Click to expand...
Click to collapse
If you installed from another ROM, then you will experience issues. I think even still Kyorarom is the only JPU based firmware so it has problems with older firmwares config files.
hillbeast said:
If you installed from another ROM, then you will experience issues. I think even still Kyorarom is the only JPU based firmware so it has problems with older firmwares config files.
Click to expand...
Click to collapse
I just did a data wipe. Still the same problem. Its starting to get a bit creepy now
And the problem is now on every ROM I have (CM7 and Kyrillos v8.2.1 too).
Help please!
Pwng3 said:
I just did a data wipe. Still the same problem. Its starting to get a bit creepy now
And the problem is now on every ROM I have (CM7 and Kyrillos v8.2.1 too).
Help please!
Click to expand...
Click to collapse
Flash the ROM again from ODIN.
hillbeast said:
Did you do a data wipe after flashing?
You need to mount the system in rw and delete them from /system/app
To mount the system in rw, use Terminal Emulator and type mount -o rw,remount /dev/block/stl6 /system
Click to expand...
Click to collapse
I did the same but it ain't working..I have a samsung GT-I5801
I have versions Kyorarom 0.4.0 b2. How to large icons because most have smaller size. Sorry for mistakes google translator.
adrianex9494 said:
I have versions Kyorarom 0.4.0 b2. How to large icons because most have smaller size. Sorry for mistakes google translator.
Click to expand...
Click to collapse
The default theme is MIUI based, and it comes with the smaller icons. You will have to flash a normal theme (without the 9-lock-screen-mod) to get back the bigger icons.
NOTE: I will support this here as well, and am posting here so others can see the ROM as well. However, I will keep the post and information more up-to-date on Rootzwiki. I don't have time to browse through a bunch of different forums for support questions and other requests, so please keep that in mind when posting here.
With that being said, here is what you've been waiting for. This is the continuation of the last InfinityROM that was created based on the EP1W leak. A lot has changed since then, way to much to go through and update in the posts of the previous topic, so we are starting out fresh. This ROM is based on the official OTA that just recently got sent out to DROID Charge users everywhere. From there, it went through a major weight loss session, and got a full make over to get the wonderful orange and brown stock color scheme out. Much of the theming work was originally done by Retrokid223, and has been brought into this new ROM by myself. We went for a TouchWiz 4 look from the SGS2, mainly because it is currently the look that I like.
To go through a brief history of what this ROM has gone through to get to its current release state, here is a slight Cliff Notes run-down. I took the update and went from EE4 to EP4D. I then dumped the stock ROM from my phone and deodexed it. From there, I went to work taking out a bunch of stuff that people don't want, and things that are easily installed from the market. After that, I replaced a small handful of TouchWiz apps with their AOSP equivalents, and rethemed everything, updating icons and images as needed from newer SGS2 and also SGS ROMs that have been released into the wild since EP1W came out. A few tasteful mods have also been added, and from here, TSM Parts will follow shortly.
This ROM is mainly so people can continue to use InfinityROM and the latest update without having the ugly stock color scheme. I will try to keep a TSM Parts free version updated as changes are made, but not everything will remain free of TSM parts changes forever. This initial release does not have anything major TSM additions in it yet, but those are on their way for the people that want them (myself included). Many apps have remained stock, though they have been rethemed to ditch the stock color scheme. The reason for this is to keep the added functionality of the TouchWiz versions, cause the AOSP versions of many of the apps are lacking in the usability department. Stuff that has been replaced has been from a stock, deodexed dump of 2.3.7 from the Nexus S.
To go with the great ROM, is a great repacked kernel. Since you can only do so much to a stock kernel when repacking it, I kept the EP4P kernel from the last test version of the ROM with the current update. This will be replaced in the coming weeks once I can get a source built kernel going. There are only minor changes to the kernel that is included, so it's nothing really special, but it gets the job done.
Screenshots will be added at a later date, along with what are likely to be several additions that users can put into the ROM (stock keyboards and other items). For now, this is what you get, and stay tuned for future updates, as there is more to come.
Installation Instructions
Backup your current ROM and Data before flashing
Download the ROM package and transfer it to your SD Card
Flash CWM if you have not already done so, then restart your phone into recovery
Select the ROM that you downloaded and flash it. NOTE - the package will auto-format your partitions to ext4 wiping all data in the process
Restart your phone, and enjoy
Downloads
0309 Infinity
0309 Infinity w/TSM Parts
1214 Infinity
1214 Infinity w/TSM Parts
1211 Infinity
1211 Infinity, EXT4 Formatter
1211 Infinity w/TSM Parts
1211 Infinity w/TSM Parts, EXT4 Formatter
1204 - Initial Release
Add On Packages and Other Files
Backup Assistant
DLNA Client (AllShare)
Media Hub
Samsung Keyboard
Screen Capture Service
SNS Accounts
Swype
TW3 Widgets
TW4 Widgets
Verizon Apps
Accurate Battery
{
"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"
}
Thanks
jt1134 - for helping me get started with development
sbrissen - for TSM Parts and all his smali help
Retrokid223 - for the initial theme work that was used
Miscellaneous Helpers and People that Deserve Thanks Anyway
OMJ
Adrynalyne
nitsuj17
chopperthedog
KhasMek
poitee
supercurio
The rest of TeamSbrissenMod
Changelog
0309
Fixed force close on themed OzEmail.apk
Uploaded several AddOns
Updated ad-block hosts file
1214
Minor theming work done
1211
A few framework changes (framework.jar mainly)
TSM Version Added
TouchWiz4 Launcher replaces TouchWiz3 Launcher
Google Music replaces TW Music Player
CRT On/Off animations added
TW4 Widgets available for those that want them
1204
Initial Release
Screenshots
See Here
Frequently Asked Questions
How do I get root access?
Download and install Superuser from the market. The su binary that is required should already be there via the kernel, all that is required is its complimentary application.
How do I install the ROM?
See the first post of this thread.
How do I go from XXX to this ROM?
The fastest way to go to this ROM from anything is by downloading and flashing the ROM+Kernel on EXT4 package. That will format your partitions to EXT4 and then install the kernel and ROM. Note that this will wipe all of your user data in the process, so be sure to backup anything you may want prior to flashing.
Where is Gmail, YouTube, Maps, etc.
All Google applications were removed from the ROM. This was to make sure that you are running an up-to-date version on your device and it also saves some bandwidth when the ROM is downloaded.
Does this kernel support Voodoo?
The kernel does not use the Voodoo Lagfix functions. However, it does fully support EXT4 partitions. Voodoo Lagfix is meant so partitions can be converted to and from RFS/EXT4. To do this, the boot process is slowed down for partition checks and conversion. To avoid this, I just enabled EXT4 support so you can still reap the benefits of the improved read/write capabilities without having to wait for the phone to boot up.
Voodoo sound is another matter entirely and can be enabled (in part) by using Voodoo Control Plus. This will allow you to load a beta Voodoo Sound driver that supports many of the functions of Voodoo Sound. Until source code is release for Gingerbread though, full Voodoo Sound support will be unavailable.
Does this kernel support overclocking?
No it does not. Source code will need to be released before many features, such as overclocking can be included.
Do you have plans to include XXX in your ROM?
The current plans for this ROM are to bring in TSM parts, and any updates to that it receives as well. There may be some other updates outside of TSM Parts, but currently, there are no other major plans. If you would like to see something included, please link to what you would like and it will be taken into consideration.
I am having xxx issue, can you fix it?
We can certainly try, however, we will need some information from you first. In order to fix a problem, we need as much information as possible from you about it. Please provide details of the issue, such as the application name you are having problems with. If you can reproduce the issue consistently, provide the details on how to do so, that way we can attempt to recreate it ourselves. If it is a graphical glitch, try to get a screenshot of the problem, or a regular camera picture. The most valuable information you can provide is logcat output, see below on capturing a good log for us.
How can I get a good log of a problem I am having?
There are two methods you can use to get a log for us. The easiest method is to use aLogcat from the market. An alternative method is to use adb on your computer. If you do not know how to save the adb output from logcat to a text file, I recommend using aLogcat. Once you are ready to capture a log, start logcat from adb, or aLogcat. With the log still running in the background, recreate your issue several times (3 to 4 times should be sufficient). Once you have recreated the issue multiple times, stop the logging and save the log file. With aLogcat, it will be saved to your SDCard. Then, take your log output and send it to us, preferably via PM. The reason we request via PM is that sometimes, logcat can capture personal information, such as your email address or phone number. Rest assured that we have no interest in this and will use the output strictly as a debugging tool to help fix whatever issue you are reporting. We hate spam just as much as you do. I have also attempted to remove as much of the debugging output of personal information as possible, but I can't catch everything. In any event, I still recommend learning to use logcat from the Android SDK, as it is an invaluable tool.
Also, if you are reporting a graphical bug (something that needs themed), please get a screenshot of what you see that needs changed. Note that we cannot change everything. If it is from an application that is not included with the ROM, it may be much harder to fix the problem as sometimes apps do not pull their color information from the ROM and hard code their own colors. This is most noticeable in the quick panel notifications. However, it is still possible that something was missed, so feel free to submit reports of anything that you feel has yet to be themed.
Help, I restarted into recovery and lost all of my data!
This is an issue that affects people randomly. My opinion is that you can deal with it for the time being. I recommend using a good backup solution that doesn't involve recovery. I say this because I test ROMs and have had my data wiped hundreds of times due to testing over the past several weeks. If I can deal with resetting everything all the time as the developer, you, as the user, should also be able to make due until a permanent solution can be found.
How can I thank you for your work?
Just click the thanks button on our posts. We do this for fun, but if you wish to a monetary donation, click the Donate button by my Profile Picture.
How can I get XXX app to vibrate on new notifications?
It seems that some applications are ignoring the global vibrate notification setting. To fix this, go into the application and press the menu button and go to settings (or however you get to the application settings). Find the notification settings, and turn on vibrate. It seems that messaging is the biggest complain among people, and this should solve the problem.
I created a theme for your ROM but have no where to host it
If you send me a link to your theme, I will host it for you on my site (imnuts.org). Note that I may not get to your message for hosting immediately, and also I won't host any theme that isn't tasteful and clean. If I find out that you are porting a theme without permission, your file(s) will be removed immediately and any further actions appropriate will be taken.
Can XXX be added to the FAQ?
While we strive to keep up with posts, sometimes we may overlook a repeated question or issue. If you see something you would like posted in the FAQ, feel free to ask. We only ask that you put your request in the following format:
Code:
[b]Question goes here[/b]
Answer goes here
Thanks....cant wait to see how it looks!!!
awesome job bud
it can be a pain to maintain rom threads across multiple forums, but there are those that only frequent one forum so its helpful to them
You are the man! Can't wait for tw4.
just wondering...how long should it take for first boot?
been hangin out at this SGII logo for about 5 minutes
EDIT: battery pull, reboot to recovery, wiped dc, boots fine now
I usually hang out here and on RootzWiki so if I ever see any questions about this ROM, I'll try to answer them as best as I can for you (imnuts).
obededom said:
just wondering...how long should it take for first boot?
been hangin out at this SGII logo for about 5 minutes
EDIT: battery pull, reboot to recovery, wiped dc, boots fine now
Click to expand...
Click to collapse
That happens occasionally on any rom after a dalvik wipe. Not sure why, but it seems like something just gets hung up sometimes.
LOVE IT!!!!!!
Thanks for the new rom. Works great and I love the color scheme. I just wish I could find some GS2 widgets that would work with this rom and I'd be set for life
xfearxphoenixx said:
Thanks for the new rom. Works great and I love the color scheme. I just wish I could find some GS2 widgets that would work with this rom and I'd be set for life
Click to expand...
Click to collapse
That may arrive in a future update. Need to talk with the TSM Fascinate folks about the rest of the TW4 integration.
Flashing now through CWR. Cannot Wait! Grazie!
---------- Post added at 08:33 PM ---------- Previous post was at 08:26 PM ----------
Clean, Sexy, Sleek, Simply Amazing - Love the Push mail within Em-Mail - VERY DeBloated - Comes without Google Apps - Great Work!
thank you for doing all this work. you and danalo and everyone who puts in the hours, for nothing more than a few bucks, needs to be knighted.
Anyone mind posting some screens or point me the direction where I can find some
Sent from my Gummy Charged GBE 2.0 using xda premium
bfitzpatrickd2d said:
Anyone mind posting some screens or point me the direction where I can find some
Sent from my Gummy Charged GBE 2.0 using xda premium
Click to expand...
Click to collapse
screenshots:
http://rootzwiki.com/topic/11175-rominfinityrom/
bfitzpatrickd2d said:
Anyone mind posting some screens or point me the direction where I can find some
Sent from my Gummy Charged GBE 2.0 using xda premium
Click to expand...
Click to collapse
Look at the GT-I9100 (SGS2) and it's stock look/theme and that is basically what this will look like. You could also get an idea of the look from the T-Mo/Sprint SGS2 variants, as well as several original SGS variant Gingerbread updates. I'll post some screenshots then when I get a chance to take them.
Awesome ROM!! Running smooth as butter. Only downside is i've already had the random data wipe after booting into recovery to flash the Minimal Theme. But I definitely like where this is going.
Sweet thanks, gave me another reason to stay up late and not talk to the wife.
Very nice
Very nice rom....clean slick to the point no bloat. I like being able to decide what is on my phone or not. Great Job, I may have a reason to keep this thing now...lol
Awesome and thanks! The Rom is working fabulously for me so far. Hoping that themers will take you up on your offer and begin themeing soon. Always love blue based themes myself.
Thanks again for the Rom!
Oh, by the way, do you plan on always packaging your kernel with the Rom or will you ever separate it as a stand alone download?
Sent from my SCH-I510 using Tapatalk