Well, I've been loving Voodoo on my Galaxy S Fascinate for quite a while now, so I've decided to get it running on our Tab. This version has a fully functional version of Voodoo CwM. It is based off of CWM 2.5.x and not 3.0. 3.0 isn't nearly as good IMO. You do not need to have Koush's bootstrapper or recovery installed. However, if you do, it's okay as well.
I haven't tested the conversion process yet, so I'm just going to say this until someone tells me otherwise.
YOU DO NOT NEED TO HAVE CWM INSTALLED!
Fixing it is the next big thing on the list. I promise.
Preamble
1. Don't ask me on how to install koush's recovery, that's what his thread is for. Laymen's terms- Did you do THIS? If you did, you're good to go, if not. do it.
2. I am not going to teach you how to use, or set up the applications that you need to use/flash this. I have included links to everything you need to know, just click and read for a second. If you are not willing to put out a little bit of effort to better your experience with your Tab, I am not going to waste even more of my time that could be dedicated towards making my kernel better. Also, if you aren't willing to give yourself the fundamental knowledge required for flashing this and something goes wrong, you will then have the required skill to fix it, instead of blaming me for bricking your Tab. I don't need that. I am willing to support my ROM and help with some confusion, but if you want me to do everything for you- lo siento.
What is Voodoo
Read about it HERE. Note, some of the information is outdated, but it's still a good general idea.
Features
Voodoo CwM v2.5.3.x Recovery for all your flashing/backup/restore needs.
TBH, I can't remember them all off the top of my head. I'll need to double check for all of them.
Tun.ko support
CIFS support
Slow-work.ko support
ext4 support
Voodoo lagfix!
Voodoo Sound fix!
Optional 1.4GHz overclocked kernel.
AOSP Boot animation support (I haven't tested fully yet)
init.rc speed/stability optimizations
many, many other tweaks
Changelog
v5 Major Update - Highly recommended install
Based on EC02 kernel source
Added Powersave, Userspace and Ondemand CPU Governors
All patches and modifications from before have been added to the EC02 kernel source
Fixed a conflict with TinyRCU (a goof up I didn't notice I made with the DJ11 source, this helps an immense amount with stability)
Tweaked the touchscreen voltage to help with battery life
Added ext4 patches from the 2.6.32.11 kernel (found here http://kan.gd/8hp), thanks to imnuts for pointing them out.
Overall this kernel is much smother and stable from the last 12 hours of my testing. Take it for a spin and let me know what you think. BT HID? Maybe, I've given up trying to get it to work until I have the ability to test some of the devices myself.
I didn't update the Odin tars or heimdall/SGS kernel flasher links from v4 because A. Most of you should have CWM installed at this point anyway and B. If you're not, step 2 will write over the kernel partition anyway (the recovery partition is only used on very rare occasions and the version difference won't make a difference)
v4 Major Update - Highly recommended install
I'm just including the updates from v3 (that never made it to the first post) in v4 for the changelogs sake.
Voodoo Sound updated to version 7, many thanks to supercurio again, and thanks to JT for reminding me that SC actaully updates his code like a madman!
Lzma compresson on the intiramfs (lowering the file size to just over 6MB, from 7.4) This will increase the speed a bit, but mostly it allows for more room for me to add more BT HID modules (lots of devices require their on module, which is why some devices work and some don't currently) and other features I find down the road
Replaced Samsung's RCU with TinyRCU (ported to the tab by jt1134, many thanks)
Added lowmemorykiller, this should give you a good 240MB free at boot
Okay, I don't want to shoot myself in the foot, but I think I really got BT HID this time, for most common products. We'll find out though!
More modules built from source (vibrator.ko, dhd.ko, tun.ko, dpram_vzw.ko, s3c_lcd.ko, s3c_bc.ko, pvrsrvkm.ko, dpram_recovery.ko and cifs.ko)
I'm stopping the production of the 1.0GHz branch of kernels, if you don't want to run it at 1.4GHz, just use setCPU to have the max be 1000MHz, there will be no difference.
Also, If you test this for BT HID please report back to me on the working, or non working status including the information below
PLEASE
device - Manufacturer and Model number would be great.
status - did it pair and work? did it just pair and not work? did it not pair at all? did it not detect at all?
It would be really, really helpful. This is one feature I'm adding for you, the users. I have a pure and utter hatred for the bluetooth protocol and have no BT hardware, at some point it would be cool to have onna those little apple keyboards though.
v3 Major Update - Highly recommended install
Fully functional CwM. This is about the only change, but it's a huge one. This allows for flashable zips, clearing of dalvik cache, normal cache, toggling of Voodoo features and more! I am working on a tutorial for those new to how Voodoo CwM works.
Other small tweaks and init optimizations.
Rebuilt initramfs from base code to insure optimal build and function.
New Branch 1.4GHz overclocked Version added. It's fast.
See below for downloads.
Don't forget to download the Voltage Control App | (source)
v2 - Feature update
Added Voodoo Sound! Thanks to some (a lot) of help from supercurio, we know have the benefits of his sound fix in addition to his lag fix. Get the Voodoo Control App off the market to see it's full feature set. It's a difference you have to hear to believe.
v1.1 - Maintenance update
Added slow-work.ko
v1 - Initial Public Release
Primary Recovery is jacked. to get into a (more) functional backup recovery, boot into recovery, go into the advanced menu and reboot recovery will bring you into the backup recovery.
Plans
streamlining it some more and sorting out any issue that make revolve around current features. Got an idea, throw it my way, but I am not going to guarantee I'll do anything about it. Full Bluetooth HID support (wimote, apple keyboard, etc).
Known Issues
Sometimes on the first boot after flashing I will have a FC window pop up, but with no description of what is force closing. If I click force close on this, I end up having wifi problem. If I click wait I do not wifi issues.
This will work with Sprint Tabs, however there are some compatibility issues, namely, it will mount on your PC as a CDROM drive, not a removable disk. Fix - Use dropbox or CIFS. Also, the camera doesn't work properly on the Sprint Tab. I will start a new branch with 100% Sprint compatibility As soon as I can.
If you run into any issues, boot into recovery, clear cache and dalvik cache (in advanced menu)
If you have any further issues with the initial boot/conversion, hold down the power button until the device powers off and reboot into recovery (power + volume up). Go into the advanced menu, turn off voodoo lagfix and voodoo system lagfix. Now Reboot, you should fully load into android. Reboot into recovery and enable the lagfixes. Conversion should happen successfully now.
Conversion will not occur if you don't have a SD card inserted or if your SD card is full.
Installation
Read the instructions all the way through before starting
Part 1
For initial installation only! If you have v3+ installed already, skip to part 2!
I have documented how to flash your initial installation two ways. If one way doesn't work for you, try another. You do not need to use all 3 methods! Using the SGS Kernel Flasher should be the most fool proof method, FYI.
Option A: Heimdall
Download a kernel zImage- 1.4GHz Overclocked Kernel
Power Down your device
Boot into download (Power + Volume Down)
Flash Via heimdall GUI in the kernel and recovery or via command line with heimdall flash --recovery *filename* --kernel *filename*
Pay attention to the progress.
When the progress bar gets to 100% your tab will reboot. If everything has gone as it should. Your installation is now complete. If you have any issues, see above in the known issues section.
You do not need to continue to step two, but I would recommend it, just to make sure everything is flashed correct.
Option B: SGS Kernel Flasher
READ ABOUT SGS KERNEL FLASHER HERE
Download a kernel zImage- 1.4GHz Overclocked Kernel | (Voltage Control App) | (source)
Flash via SGS Kernel flasher (really, just select it. I don't think anyone should be lost by this process).
Continue to Part 2
Option C: Odin
Download a kernel tar package- 1.4GHz Overclocked Kernel | (Voltage Control App) | (source)
Power Down your device
Boot into download (Power + Volume Down)
Flash via PDA in Odin. Do not change any other options.
Continue to Part 2
Part 2
This step insures that the recovery partition was successfully flashed and that everything is functioning successfully. Also, a how to flash zip's via recovery tutorial for those that haven't before.
Download a kernel zip package- 1.4GHz Overclocked Kernel | (Voltage Control App) | (source)
Power Down your device
Boot into recovery (Power + Volume Up)
Voodoo CwM controls! Volume up/down = Navigate up/down || Power button = Select/confirm || Back = Back || Menu = Screen Toggle || Home = Screen Toggle || Search = Nothing
Select install zip from sdcard
Select select zip from sdcard
Navigate to the location of your downloaded .zip
Select zip
Select yes in confirmation screen. My install script will scroll through and say install from sd card successful if all has gone as planned.
Rejoice and be happy
Make themes/mods/ROMs/hacks/awesomeness to share!
Thanks
jt1134, Adrynalyne, rotohammer, TCMAN, Supercurio, koxudaxi, Punk.Kaos, mike, buggs, 1techydude everyone in IRC as usually is great help. Kangers, women, kittens, ninjas, Open Source.
Finally, if you like my work, donate to me so I can donate money to devs that make my world easier (and therefore yours).
i knew we were bound to see voodoo for they tab, willing to make for gsm?
I've been thinking about it, but no promises.
Boushh said:
I've been thinking about it, but no promises.
Click to expand...
Click to collapse
at least you thought about it. adding this to the bible
What is difference between standart ext4 fs and voodoo lagfix when the sound improvements arent ported yet?
Sent from my GT-P1000 using XDA App
Is there a noticeable speed boost with kernel? I don't have a galaxy s phone and I've never uses the lag fix so I'm curious as to the real world benefits and risks of this kernel
Sent from my SPH-P100 using XDA App
futuregerald said:
Is there a noticeable speed boost with kernel? I don't have a galaxy s phone and I've never uses the lag fix so I'm curious as to the real world benefits and risks of this kernel
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Yes it is. if you care about benchmarks I'm getting around 14mflops in linpack and 1750 in quadrant, which is more than I was getting with just the ext4 conversion. I've done a lot of other optimizations to this. However, the only real way to see if you like it is to try it out yourself and see if it works for you.
I see you say this should work on sprint, but there is no working CWM for sprint so how the hell do you get ext4 then?
Sent from my SPH-P100 using XDA App
idumych said:
I see you say this should work on sprint, but there is no working CWM for sprint so how the hell do you get ext4 then?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
I am not saying you are rude I am just saying that sounded rude... don't take it personal it's just that coming off a little more polite is more likely to get you some help/answers.
You are awesome! Once everything is ironed on ill bust my Sprint tab out the drawer! Can't wait!
Sent from my PC36100 using Tapatalk
idumych said:
I see you say this should work on sprint, but there is no working CWM for sprint so how the hell do you get ext4 then?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Well, I have heard of people flashing CWM 3.0 on their sprint tabs using the vzw kernel. it's in the CWM 3.0 beta thread. So, there's that. Or you can manually convert your system to ext4.
What does any of that have to do with my thread? Seriously.
sh!t sorry, to many threads open and this is the wrong one. I am working on extracting a working modem.bin for the sprint device is all. I'll edit those out or have a mod delete them, sorry folks.
HAH! No worries, I thought as much, just wanted to make sure.
Boushh said:
Well, I have heard of people flashing CWM 3.0 on their sprint tabs using the vzw kernel. it's in the CWM 3.0 beta thread. So, there's that. Or you can manually convert your system to ext4.
Click to expand...
Click to collapse
I just read that thread an no one says they got it working
Anyone know where I can find info how to convert it manually? Everything I've read says you must have CWM.
Fantastic! As a verizon tab user, i'm grateful to you boush for working on giving us cdma people some options.
I'm going to wait until the recovery is ironed out before flashing, but great work!
b0ricuaguerrero said:
i knew we were bound to see voodoo for they tab, willing to make for gsm?
Click to expand...
Click to collapse
+10
I actually PM'd Hardcore also if he wants to make his kernel for Tab as well... but I think the dude has no Tab
Read it again, I just did last night on my sprint tab, posting details later tonight.
Sent from my SPH-P100 using XDA App
If the title says it's for Sprint/VZW why would you come in here asking about GSM?
I'm also curious how to convert to EXT4 manually?
cruiserbax said:
Read it again, I just did last night on my sprint tab, posting details later tonight.
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Looking forward!
shoman24v said:
I'm also curious how to convert to EXT4 manually?
Looking forward!
Click to expand...
Click to collapse
Not sure, since im still too noob to mess with this and to top it off, just went full time with ubuntu and got rid of win7, and need to figure out all this driver stuff ,
soo i think the manual method its listed in this thread via ADB , but please dont flame if im wrong, still new to this tab stuff
http://forum.xda-developers.com/showthread.php?t=870690&highlight=recovery+BETA
Flash the kernel using flash_image: http://koush.tandtgaming.com//test/flash_image (This will flash both boot and recovery)
adb push flash_image /data/local/bin/flash_image
adb push verizon_zImage /sdcard/
adb shell
su
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/verizon_zImage
sync
exit # This should take you back to your computer's console
adb reboot recovery # Boot into recovery
Related
Hi everyone !
http://project-voodoo.org/
I tweet about progress on the project.
Last but not least, the wonderful community-build page for the Voodoo 5 Froyo preview (not yet up to date)
Voodoo 5.x releases with Voodoo sound, build from sources, recommended:
Checkout the Sound bounty thread:
I propose also versions only the lagfix only, called stock+Voodoo because they are build around the kernel compiled by Samsung
stock+Voodoo-latest XYJS8:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XWJS8.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XWJS8-unsigned-update.zip
stock+Voodoo-latest XYJS5:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XWJS5.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XWJS5-unsigned-update.zip
stock+Voodoo-latest XYJS3:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XWJS3.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XWJS3-unsigned-update.zip
stock+Voodoo-latest XXJPY:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XXJPY.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XXJPY-unsigned-update.zip
stock+Voodoo-latest XXJPX:
Flash with Odin: http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-GT-I9000-XXJPY.tar
Flash with CWM: http://dl.project-voodoo.org/stock+...odoo-Froyo-GT-I9000-XXJPY-unsigned-update.zip
JPX, JPY, JS3 versions are based on Samsung pre-compiled kernels. This is why those are feature limited (no Voodoo sound, no BLN, no sharpness adjustment).
This project is 100% opensource and i'm proud of it
You can build everything from sources using https://github.com/project-voodoo
Important note, I don't recommend installing this relase with Odin if you don't have a direct access to the Download mode with the 3 buttons combination.
Odin is known to give a % of flash fails. This has no consequences for most because if you retry it works, but for people unable to go to the download mode this is a serious problem (and a Samsung official bug, they distribute a hardware part internally to force the download mode access)
5.1 changes:
Updated lagfix
Voodoo sound support (Download Voodoo App from the market)
5.0.3 changes:
added cool shell with tab completion
Final changes:
So many it will be hard to describe everything here:
converts /data /dbdata /cache /system to optimized Ext4 for each partition
more reliable and faster
beefed up conversion process, with conversion time estimation
memory management optimizations
VFS (disk write behavior) optimisations
BLN notification built-in
ClockWorkMod recovery built-in (optional) with total Rom Manager compatibility
Standard bootanimation support
linux standard /etc/init.d/ boot scripts support with integrated run-parts (additional busybox not necessary)
Click to expand...
Click to collapse
Short FAQ:
Does it includes Voodoo sound and color ?
- Voodoo color: sharpness adjustment and color rendering in videos only.
- Voodoo sound: YES
Also in stock+Voodoo builds ?
Nope, thos contains only the lagfix option (and su)
I want root !
Who doesn't
The technical setup is made automatically. If you want root, install Superuser App from market, that's all.
Hey, curio, do you have an eta for bêta 2? I mean first public release at least.
Will this kernel work on soon-to-come official froyo and less officiel Cm6?
Sent from my GT-I9000 using XDA App
I heard about a possible heavier battery draining using Voodoo lagfix comparing with a stock FW.
Anyone has an extensive feedback about that? (Maybe a direct comparison with/without?)
@Supercurio
Is heavier battery draining "kernelly" possible with your lagfix?
Hi,any way to get rid of clockword mod incompatibility issue?
Any other way to uninstall the fix,besides disable-lagfix file and flash of other firmware (it seems that some settings remain modified,i.e. wifi sleep time)?
Yes i can confirm the battery draining ...
I'm on M6 and after flashing the voodoo kernel the phone is really fast and smoooth...no lag anymore....really really fast. But too much battery draining...i fully charged till 11am ....at 23 pm the phone was completely exhaust with normal use of data connection and a bit of wifi...
So i removed the lagfix with the disable_lagfix file with no extension in the sd card and another little problem comes out. The wifi doesent turn off in idle with screen off..
Ryanza found a solution about this:
http://forum.xda-developers.com/showpost.php?p=7998188&postcount=458
Now my only trouble is about the battery draining...I just removed and fully charged my galaxy s and i'm wondering if the battery efficency is back as before the lagfix or i need to reflash my JM6.....or is there other solution like flashing only a kernel....
i dont know..
if someone know something about this let me know : >
(sorry for my bad english)
ivan
Narcissus85 said:
Yes i can confirm the battery draining ...
I'm on M6 and after flashing the voodoo kernel the phone is really fast and smoooth...no lag anymore....really really fast. But too much battery draining...i fully charged till 11am ....at 23 pm the phone was completely exhaust with normal use of data connection and a bit of wifi...
So i removed the lagfix with the disable_lagfix file with no extension in the sd card and another little problem comes out. The wifi doesent turn off in idle with screen off..
Ryanza found a solution about this:
http://forum.xda-developers.com/showpost.php?p=7998188&postcount=458
Now my only trouble is about the battery draining...I just removed and fully charged my galaxy s and i'm wondering if the battery efficency is back as before the lagfix or i need to reflash my JM6.....or is there other solution like flashing only a kernel....
i dont know..
if someone know something about this let me know : >
(sorry for my bad english)
ivan
Click to expand...
Click to collapse
well i unplugged it by 9am yesteday and I still have 74% battery left so I think the fix improved my battery life...
To every people experiencing Wifi sleep issue.
- Does it persist after flashing another kernel (OC kernel, Stock kernel) ?
- Does it persist after flashing another firmware ?
Thanks for your answers.
supercurio said:
To every people experiencing Wifi sleep issue.
- Does it persist after flashing another kernel (OC kernel, Stock kernel) ?
- Does it persist after flashing another firmware ?
Thanks for your answers.
Click to expand...
Click to collapse
Hello.After applying your fix the wiffi will turn off after 15 minutes on my jm7 firmware and to be honest i can live with that.I dont know about other firmware.Thank you for your work waiting for the full fix to be available
About battery draining i think its the same as before i didnt notice any raise on the draining.
Wifi sleeps after 15 minutes on JM7 after the lagfix was removed. I then replaced the kernel with stock and no change.
After that I restored a nandroid backup of JM5 and still no change.
I honestly couldn't tell if this was different after I installed JPC and then went back to JM5. I also had the NEW version of JM1 on there not too long ago. Mabe JM1 or JPC made changes or removed a setting. I would have thought that a wipe would clear /dbdata anyway.
Using RyanZa's database edit the wifi now sleeps again ;-) I needed to put the setting into both tables btw.
I think the 15 minutes to turn wifi off after display is off hasnothing to do with this kernel, i think (not sure 100%) it has already been with jm3 and jm7 without supercurios kernel.
First I wish to thank supercurio for the fix. It's perhaps one of the best I had tested so far. Been using it ever since and never had been happier.
Anyway are there anyway to reverse the lagfix ? I had did a few flashing between JPC and JM7 and it seems like the ext4 partition was never wiped off. The prior apps that were there before the wipe had persisted.
Thanks.
I have not noticed a difference in battery drain actually.
Hmmm.....so those on beta1 might have trouble upgrading to beta 2?
Well, my wifi takes 15 minutes to get disabled. I have never tried the Voodoo Lagfix, so that can't be the source of the issue. I was previously on JPC and currently on XXJM1. I don't remember if it used to take just 30 seconds for Wifi to turn off on my stock firmware - sorry.
No noticeably difference in battery drain here.
80 hours since last reboot of the phone on voodoo and not a hint of lag or slowdown. This one seems like the real fix for sure. (And no, that's not 80 hours without a charge, just no reboots.)
The lack of clockwork or some other whole-rom backup facility is slightly concerning, but I've only needed it once, and a fresh install plus appbrain/titanium backup are still available.
I did not notice any extra battery drain either.
As for the wifi. Has it ever been different? Anyone who has a different time in there?
Sent from my GT-I9000 using XDA App
WiFi sleep settings
Settings->Wireless and network->Wi-Fi settings->menu button->Advanced->Wi-Fi sleep policy set to never
You can change it to turn off WiFi when screen turns off, or keep it on if your phone is on charger.
..
kgk888 said:
Official instructions are to create a blank file with no extension in /sdcard with the name "disable-lagfix"
If you don't know how to do this from the desktop environment (extensions are disabled by default in Windows7), just use Root Explorer on your phone, navigate to the sdcard directory, hit the menu button, go to More, and create new file with that name. It will have no extension by default.
Then reboot.
What I did personally after the normal instructions was an SD card format, and a factoryreset/cache wipe just to be sure afterwards.
Then I flashed to a diff firmware. It wiped the EXT4 partition for me.
Click to expand...
Click to collapse
How's that video coming?
Sorry to be a noob, but how do I download beta 1? Do I have to sign up for the beta or something?
News
1/31/11: v0.1 is released; initial beta.
-A JS3-based ROM with a focus on simplicity, stability, speed, and battery life.
Hello XDA.
I wanted to create a ROM on the latest firmware with an emphasis on simplicity, stability, and speed, and battery life. I wanted to be able to customize the ROM without the use of extra software, gimmicks, or any unnecessary tool. I wanted it to be as close to the stock ROM as possible (in terms of appearance, not performance), with only the bloatware removed, and a few key applications added. I also wanted it to be blazing fast without sacrificing battery life.
So, I started working on seeARMS' XWJS3. This ROM gives users the choice of installing their preferred kernel, modem, bootanimation, etc, and using either a wipe / non wipe version (and soon: themes, applications, everything) simply by deleting and renaming a few files.
Using a handful of shell scripts, this ROM checks for, say, the SpeedMod kernel (named "speedmod") in your SD card. If it's found, it installs the speedmod kernel. If you prefer Super Optimized Kernel, that's alright: leave the file named "sok" and delete the other kernels. This ROM will automatically install whichever kernel you choose, without the need to use additional tools or software.
Note before proceeding: This is the initial BETA release, so there are bound to be bugs. I've been running this build for a few days and everything's been fine, but that isn't to say it's completely bug-free. Have a backup on hand in case anything goes wrong.
Also, read the first few posts before asking a question, as I'll try to address everything I can. When you are posting a question/problem, please include the logfile located at "seearms/log/seearms.log" (if it exists). If it doesn't exist, please say so.
Alright, so now that that's done, heres the index:
1. Download and Installation Instructions
2. Changelog, To-Do
3. FAQ and Common Problems
4. Screenshots, Media, User Comments
Current Kernels: SpeedMod K12T-T1, Super Optimized 4.7.2, Advanced Voodoo v666.1+2.
Current modems: JL2, JPY
Current addons: Nexus Bootanimation, Wipe
Features
Based on XWJS3 (v2.2.1) [Latest firmware; fast, battery efficient]
Choice of SpeedMod, Super Optimized, Advanced Voodoo kernel [All have Voodoo sound, sharpness + color, BLN, faster, better battery!]
Created an error-checking script which prevents battery drain and force closes [Ensures the installation goes smoothly]
WiFi Firmware Version Fix [Better battery life]
Circle Battery Mod installed by Default
3 Launchers - Gingerbread, Stock, Launcher Pro
3 Keyboards - Gingerbread, Stock, Multi-Language Swype
Fully deodexed [Easily Themable]
Fully zipaligned [Better RAM Usage]
Fully updated Google Apps (YouTube, Flash, Market, Gmail, Maps)
Latest Su and Busybox [Preinstalled, no extra effort required]
All protected apps in market visible - modified build.prop
Big APN list, which allows instant internet + MMS access
Stock AOSP Lockscreen
Backlight Notifications
Removed startup + shutdown sounds
Phone Ascending Ringtone Fixed
Modified Applications
+ Gingerbread Keyboard
+ Launcher Pro
+ MIUI Music Player
+ SGS Info, Toolbox, Tools
+ Swype 2.15 Multi-Language
- Press Reader
- Write and Go
- MiniDiary
- AllShare
- Buddies Now
- Android Books
- ThinkDroid
- Aldiko eBook
- Layar
- FileIndex, Telegraaf, Samsung Shortcut from stock JS3
Downloads
Latest and Greatest
v0.1: seeARMS' XWJS3 v0.1 (1/31/11)
http://www.multiupload.com/842IKYJ8FU
Addons
Coming soon
Installation Instructions
Before installing, make sure to disable any lagfixes, create any backups that you need, etc.
Long version:
1. Extract the downloaded file to the root of your SD card.
2. Navigate to the "seearms/kernel" folder, and here you should see 3 files: sok for Super Optimized, voodoo for Advanced Voodoo, and speedmod for the SpeedMod kernel. Delete two of them, leaving only the one that you want to install.
3. Navigate to the "seearms/modem" folder, and here you should see 2 files: jl2 and jpy. For Canadians, or other users who want the use of the 850MHz band, leave the "jl2" file untouched, and delete the jpy file. For everyone else, delete jl2 and leave jpy.
4. Navigate to the "seearms/extra" folder. Here you should see nexus_bootanimation, and a "wipe" file. Leave the bootanimation untouched if you want the Nexus S bootanimation, and leave the wipe file if you want the ROM to format /data.
So, before installing, you should have one file in kernel, one file in modem, and anything in extra, depending on your preferences.
5. Boot into CWM or Recovery 2e, select "Install from zip", navigate to the ROM you copied, and install.
I'd recommend the following files left untouched:
seearms/kernel/speedmod
seearms/modem/jpy
seearms/extra/wipe
This will install the SpeedMod kernel, JPY modem, and will wipe your data to allow for a brand new install.
Short version:
1. Extract the downloaded file to your SD card.
2. Delete any kernel and modem you don't want, leaving only 1 in each folder.
3. Delete seearms/extra/wipe if you don't want it to wipe. Delete anything else in this folder you don't want.
4. Boot to CWM, flash the zip.
After it boots, I'd recommend doing a few things to ensure your phone is as fast as possible:
1. Enable the EXT4 lagfix in recovery
2. Enable all tweaks in recovery
3. Overclock if you wish using SetCPU
Changelog
1/31/11: v0.1, initial beta release
To-Do
-Extended power menu
-More modems, kernels
-Choice of applications and themes to install
FAQ
Contents (Use control + F to find the question)
Q1 - I'm on stock Froyo and I have 3e recovery!
Q2 - I have a Bell Galaxy S, and I'm afraid of my phone bricking! What can I do to prevent it?
Q3 - I'm encountering force-close issues, and general app issues right after installation.
Q4 - My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Q5 - My battery is running out very, very quickly!
Q6 - What's all this talk about the 850MHz band and modems?
Q1 - I'm on stock Froyo and I have 3e recovery!
Click to expand...
Click to collapse
If you're on stock Froyo (ie: not running Eclair with recovery 2e or ClockworkMod) then you might have to do a bit more work before installing any custom ROM. Just follow these steps:
1. Download Odin from here.
2. Download the latest Super Optimized kernel (or any other kernel that has CWM) in the attachments. Make sure to download the Odin kernel, not the CWM one!
3. After downloading, extract the .TAR file from the file you just downloaded.
4. Open Odin, and turn off your phone. Connect your phone to your PC via USB, and enter download mode by holding volume down + home + power.
5. Odin should detect your phone. Load up the .TAR file in the "PDA" box in Odin. Make sure the other boxes are left blank. Untick "Repartition". Start flashing.
6. Your phone should automatically reboot with the new kernel! To double check, shut it off and boot into recovery. If you see CWM recovery, you're successful!
After doing this, follow the normal steps to install this rom.
Q2 - I have a Bell Galaxy S, and I'm afraid of my phone bricking! What can I do to prevent it?
Click to expand...
Click to collapse
It isn't entirely known right now why the phones are bricking; some say it's a hardware issue involving the motherboard, whereas others say it's strictly a software issue. Both Samsung and Bell have stated that the new firmware, JL2, fixes this problem and will prevent the internal SD card from dying. However, there have still been reports of phones running the JL2 firmware and dying (albeit much, much less reports).
A bit more technical: Included in the stock JL2 firmware from Bell is a new secondary boot loader (Sbl.bin). This deals with the phone at boot-time; it handles three button recovery, etc. Typically, the Sbl isn't included in a new ROM, as nothing needs fixing and the boot loader doesn't need touching. Except for this time! The Sbl.bin is apparently the file which fixes the internal SD card problem.
So, if you're wondering what to do in order to prevent your phone from dying, your best bet would be to flash the JL2 firmware using Kies (or Odin if you know what you're doing - tick bootloader update), then you're basically free to flash any other firmware you wish (except for firmwares which contain the Sbl.bin, because that would overwrite the current Sbl. But, every custom ROM and essentially every stock ROM lacks this file, so you're fine to flash anything).
Again, I'm going to restate that not everything is known involving this problem and the above is based on my own research. A handful of people have done this and have still had their phones die.
Q3 - I'm encountering force-close issues, and general app issues right after installation.
Click to expand...
Click to collapse
If you installed the ROM without wiping, try leaving the "wipe" file untouched so the ROM performs a completely clean install. If you're still encountering issues after doing this, boot into recovery, perform a factory reset, and clear the cache + Dalvik cache.
Q4 - My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Click to expand...
Click to collapse
Try clearing the GPS data on your phone. Do the following: (Original poster unknown. Reposted by dpvu.)
1) Enter *#3214789650# into the dialpad.
2) Under "Application Settings" set the Start Mode to Coldstart.
3) At the main menu "Delete GPS Data".
4) At the main menu "Get Position Test".
If you're still not finding many satellites try setting Operation Mode to "MS Based" in the "Application Settings". I did all of this then set the GPS back to hot start.
Lastly, if you desperately want to fix your GPS, try flashing the JK4 modem. There have been different reports, but it has been regarded by some as the best modem for GPS. To flash it, download the modem, and use Odin to select the "modem.bin" file in the PHONE box. Go to Settings -> About on your phone after flashing and look at Baseband to ensure it flashed correctly.
Download the JK4 modem from the Downloads section. http://www.multiupload.com/3HOKWMBHO2
Q5 - My battery is running out very, very quickly!
Click to expand...
Click to collapse
There are many, many things which may cause the battery to run out quickly. I'll go over a few of the problems here:
1. After a fresh install of a ROM, the battery may be uncalibrated. Try charging your phone, and use it normally until it discharges. Repeat this 2-3 more times; your battery meter should be accurate again.
2. Clearing your batterystats.bin has been said to help fix the problem, and improve battery life by a lot. Charge your phone to 100%, then boot to recovery and clear batterystats.bin (by selecting wipe battery stats). Reboot, and use your phone normally until it shuts off by itself. After it does, charge it up fully, and you're good to go.
However, it's worth stating a few things: the above method has been put down by some users, who state that the batterystats.bin only contains a history of the battery usage and nothing more. Also, the Galaxy S contains a Li-Ion battery, which technically shouldn't be fully discharged (in order to extend the life of the battery). Do the above at your own risk.
For a few more fixes, please visit this thread.
Q6 - What's all this talk about the 850MHz band and modems?
Click to expand...
Click to collapse
The 850MHz band is a 3G band which apparently has better range and reliability (as opposed to the higher frequency 1900MHz band). It's basically only used in Canada (and I guess Australia?) but cell carriors like AT&T in the US are trying to make it the standard. Because of this, the i9000 International (not the Bell Galaxy S, i9000M) doesn't have the functionality to connect to the 850MHz band.
To get back this band, you have two options: flash any international ROM (JPY, JPX, JPO, etc), then flash a Canadian modem (JK4, JL2) afterwards. The second option is a lot easier: just install a ROM that contains a Canadian modem already (ie: this ROM, or stock JL2).
Screenshots
User Comments
Existence. said:
running great with speedmod and jl2 modem - thanks a lot.
battery life is amazing too - its at 85% and ive been using it all day!
Click to expand...
Click to collapse
Hi, well done. Nice to see you releasing another rom.
Sent from my GT-I9000 using XDA App
I will have a look at it.
thanks! seems very interesting!
PS: 3G 850Mhz band is also used all over central and south america, from mexico to argentina
[[ Cold ]] said:
thanks! seems very interesting!
PS: 3G 850Mhz band is also used all over central and south america, from mexico to argentina
Click to expand...
Click to collapse
Got it, thanks.
running great with speedmod and jl2 modem - thanks a lot.
battery life is amazing too - its at 85% and ive been using it all day!
Existence. said:
running great with speedmod and jl2 modem - thanks a lot.
battery life is amazing too - its at 85% and ive been using it all day!
Click to expand...
Click to collapse
Thank you.
Nice job seeARMS! It is running well so far (speedmod + JL2 modem).
I want to use SOK and overclock it but I can't seem to disable the VSF that is included with the kernal.
Your rom also works with the Generation X theme, which includes the extended power menu too! The AOSP lockscreen included could still be unlocked with the menu key but the Gen X theme solved that. Have you seen the 4 lockscreen? It looks very nice but I can't seem to find it.
Keep up the good work!
Hey found a bug every time i install anything from samsung apps it vibrates and then takes me to the bootanimation screen going to flash it again and see
ok tried it again i can't install any apps even from market
seeARMS said:
Screenshots
User Comments
None yet
Click to expand...
Click to collapse
Great choice of music
JJustin said:
Nice job seeARMS! It is running well so far (speedmod + JL2 modem).
I want to use SOK and overclock it but I can't seem to disable the VSF that is included with the kernal.
Your rom also works with the Generation X theme, which includes the extended power menu too! The AOSP lockscreen included could still be unlocked with the menu key but the Gen X theme solved that. Have you seen the 4 lockscreen? It looks very nice but I can't seem to find it.
Keep up the good work!
Click to expand...
Click to collapse
Not sure how to disable it since I don't use SOK, but try setting the file "/sys/devices/platform/s3cfb/VSF_enable" to 2. This should disable VSF.
dlzp said:
Hey found a bug every time i install anything from samsung apps it vibrates and then takes me to the bootanimation screen going to flash it again and see
ok tried it again i can't install any apps even from market
Click to expand...
Click to collapse
That's odd, I've installed many apps just fine. Try clearing the market cache by going to Settings > Applications > Manage Applications > Market, then select "Clear Data" and "Clear Cache".
If that doesn't fix it, a factory reset would almost certainly.
Hi seeARMS,
As you know, I am currently running your custom JL2 ROM as I am with Bell, etc and I am loving it except for the speedmod kernel as that VSF function just drives me crazy so I flashed one of Hardcore's kernels instead.
I have read your info on this JS3 ROM and I am curious and may like to flash it to see what it is all about but I have a question.
Obviously my base is the Bell JL2 and in saying that I should have the .SBL file that I need in order to keep my SGS from bricking (or so the theory goes) so my question is... If I want to flash this JS3 ROM, do in need to first install the JS3 firmware and then flash your ROM "OR" can I just download the .zip file, make my modifications (as described in your instructions for kernel, bootload animation, wipe, etc) and flash directly over my current seeARMS ROM / JL2 and keep my important JL2 items?
Sorry if this question is confusing but as my signature says... Im still a bit of a NOOB and still learning.
Also... Still waiting for my Blue theme for your JL2 ROM! LOL!!!
yiannisthegreek said:
Hi seeARMS,
As you know, I am currently running your custom JL2 ROM as I am with Bell, etc and I am loving it except for the speedmod kernel as that VSF function just drives me crazy so I flashed one of Hardcore's kernels instead.
I have read your info on this JS3 ROM and I am curious and may like to flash it to see what it is all about but I have a question.
Obviously my base is the Bell JL2 and in saying that I should have the .SBL file that I need in order to keep my SGS from bricking (or so the theory goes) so my question is... If I want to flash this JS3 ROM, do in need to first install the JS3 firmware and then flash your ROM "OR" can I just download the .zip file, make my modifications (as described in your instructions for kernel, bootload animation, wipe, etc) and flash directly over my current seeARMS ROM / JL2 and keep my important JL2 items?
Sorry if this question is confusing but as my signature says... Im still a bit of a NOOB and still learning.
Also... Still waiting for my Blue theme for your JL2 ROM! LOL!!!
Click to expand...
Click to collapse
To flash this ROM, all you need to do is download the zip, follow the instructions, and flash it from CWM recovery. This will leave your secondary boot loader untouched, hopefully preventing your phone from getting bricked. The only way your Sbl.bin would ever get overwritten would be if you flashed a ROM in Odin that contains the Sbl.bin, with "Bootloader Update" checked. (Or, updating it from Kies to a ROM that has the Sbl).
So, you're generally quite safe regarding the secondary boot loader.
Lol, sorry about the theme :/ Good news is, if you flash this ROM, you should be able to flash the blue theme right after installing it without me needing to port it over. (If it's compatible with JS3, which I'm pretty sure it is.)
seeARMS said:
To flash this ROM, all you need to do is download the zip, follow the instructions, and flash it from CWM recovery. This will leave your secondary boot loader untouched, hopefully preventing your phone from getting bricked. The only way your Sbl.bin would ever get overwritten would be if you flashed a ROM in Odin that contains the Sbl.bin, with "Bootloader Update" checked. (Or, updating it from Kies to a ROM that has the Sbl).
So, you're generally quite safe regarding the secondary boot loader.
Lol, sorry about the theme :/ Good news is, if you flash this ROM, you should be able to flash the blue theme right after installing it without me needing to port it over. (If it's compatible with JS3, which I'm pretty sure it is.)
Click to expand...
Click to collapse
Ok, so... Would you say in your EXPERT opinion that me flashing this onto a Canadian i9000M is safe?
Also... When and where do I make my modification to the install .zip file? Do I download the package to my desktop, make the modifications and then move it to my internal SD card "OR" do I download the package directly to my internal SD card, navigate to the package (with Astro for example), make my modifiactions from there and THEN flash?
Please advise...
PS... Id still like to see the blue theme available for the JL2 ROM just incase I get too chicken to try this JS3 one... LOL.
Hey yiannis.
Here's what I did:
Download to computer. Unzip it to the sd card when,plugged into computer. And just under my computer, I deleted the files I didn't need. Also, remember to disable lagfix beforehand
Sent from my GT-I9000 using XDA App
yiannisthegreek said:
Ok, so... Would you say in your EXPERT opinion that me flashing this onto a Canadian i9000M is safe?
Also... When and where do I make my modification to the install .zip file? Do I download the package to my desktop, make the modifications and then move it to my internal SD card "OR" do I download the package directly to my internal SD card, navigate to the package (with Astro for example), make my modifiactions from there and THEN flash?
Please advise...
PS... Id still like to see the blue theme available for the JL2 ROM just incase I get too chicken to try this JS3 one... LOL.
Click to expand...
Click to collapse
I'd say it's quite safe. While building this ROM I flashed my device well over 30 times, and it's still running great. My previous SGS I flashed less than 10 times and it died, so I'd wager it's perfectly safe.
And it really doesn't matter where you do the modifications. It's probably easier to just copy the files over to your internal SD card, delete anything you don't want using your PC, then simply flash the ROM.
First off, this is not for the faint of heart. Backup your junk, don't flash modems or bootloaders if you don't what you're doing, in fact, don't flash anything, if you are not aware of what is what... Read this ENTIRE GUIDE FIRST, THEN DO IT... that way you have a clear understanding of what is suppose to be on your sd card, etc....
Second, none of this is my own work. I take no credit for the development of any of the following, this is more of a guide than
a rom on how to get a Sprint SPH-P100 working with a custom recovery, kernel and rom.
I should note, I have tmobile US, and my interest in this tablet is a secondary device, hence it being a sprint device. It is not meat to be a phone for me... I dont plan to make calls or text, only tether it to my phone, use GPS as well as the other functions. It is, essentially, a laptop replacement with extra goodies...
That being said, if you test this, it is at your own will and I will provide no further instructions on how to undo something you have done... this forum has a search feature, use it. Any contributions to developing it further and providing fixes for the problems listed below are welcomed.
Before I begin, big, BIG thanks to alterbridge for providing me with excellent tips.
Also to Khasmek for his kernel and everyone who helped in the production of heimdall.
Again I say, this guide is meant to give you overclocking features for your tablet. As-well-as the ability to reboot to a custom recovery from the gui (in this case cwm 3.0.0.0).
What works?
Wifi
Camera
Video Recorder
Gallery
all other apps
What does not work?
GPS
What may or may not work?
Calls
MMS
SMS
Voicemail
What's included:
Refer to:
http://forum.xda-developers.com/showthread.php?t=932082
I'm assuming here that you are rooted. If you are not, use superoneclick. Google it...
I'm assuming your are stock also, if you are not, I advise you to get that way using this: http://forum.xda-developers.com/showthread.php?p=9753941#post9753941
Please read it carefully as you can complete bork your tablet if you are not certain. Thanks to gordesky1 for the guide.
When/if you are back to stock you can begin this process. I insist that you do this, because it is the method I started from after flashing various roms/kernels etc...
Now preload your microSD card with the following (i'm assuming you have formatted and can load it with a pc-usb attachement)
[ROM] Overcome 1.6.3
Link: http://www.multiupload.com/8XVZ2JPE4V
Source: http://forum.xda-developers.com/showthread.php?t=932082
[Kernel] KhasMek Voodoo Plus v5
Link:http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip
Source: http://forum.xda-developers.com/showthread.php?t=941781
You will also need a new vold.fstab file, a link is within the instructions.
Lets begin (flashed with Windows 7, sorry mac/linux users, you are on your own):
Step 1: Flash the VZW kernel, as it contains cwm custom recovery and allows you to flash kernels and roms.
Source: http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Download zImage file here: http://www.megaupload.com/?d=SV6IKL1D
Process: (thanks jkurl15)
"To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechi...ducts/heimdall/ <--------click on the binaries
link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechi...ducts/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft...&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the
drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab. when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab. " - zkurl
Step 2: Your screen should show you cwm 3.0.0.0 and be ready...
1) Wipe Data/Factory reset (for good measure)
2) Wipe Cache
3) Wipe Dalvick
Step 3:
Install the [Kernel]. It will flash and let you know when it is successful.
Step 4:
Install the [ROM]. It will flash and let you know when it is successful.
Step 5:
Install the [Kernel] AGAIN. (i know, it seems retarted, however I've had bootloops otherwise and it didn't matter if i didn't flash it before the rom or not, it would screw up) Anyways, it doesn't hurt.
Step 6:
Wipe again, just for good measure
Step 7:
Reboot device (first boot will take a few but doesn't hang at anything. Which means, if you see the samsung logo for longer than 60 seconds (actually takes right at 30 seconds)... you screwed up. The boot animation of the blue android with astro stars thingies going around it means you are on the path to booting)
Step 8:
The external and internal memory are jacked up. A fix has been provided and you will need to push it to your phone, and reboot.
Download vold.fstab here: http://www.multiupload.com/EKYF3CW39R (thanks to alterbridge)
bring up adb (if you dont know how, stop reading this, re-stock your phone and quit)
adb remount
adb push vold.fstab /system/etc
adb reboot
Your tab will reboot and when it comes back up, no more memory errors.
You've done it! You've flashed a oc'd kernel and a custom rom. From here, you can tinker with fixing the auto-rotate and gps and any other bugs you may encounter. I admit, i'm new to certain things, fixing it isn't my forte
I encourage you to post fixes/bugs here in the thread so that other sprint users can benefit from it all as there is a serious lack of development for them.
Future Updates: I'm assuming we can continue to flash whatever overcome updates come our way, we just have to then reflash the khasmek kernel and re-push the vold.fstab file. If we fix GPS, Screen orientation and it's through pushing means, that will have to continually be redone also. The alternative, someone cooks roms just for us... I myself could probably do it, however have never attempted to. If i get time, I will look into it, however, there are no promises...Maybe gingerbread/honeycomb variants will trickle out soon and we wont have to worry about it.
If you enjoy the rom/kernel, I encourage you to donate to the devs mentioned above, I myself will not require any donations, as this is merely a guide using other peoples materials. A big, big thanks again to the people who contributed to these roms, kernels and tools. Thank you!
Update 1: (4.30.2011 @ 6:49PM CST)
Fix for rotation using a method from the voodoo thread. Can either push it, or copy to usb with pc, then use root explorer or similar to move it into place (requires reboot)
"Try pushing the sensors.default.so file from bauxites thread. I have attached it.
unzip this and place it in /system/lib/hw (backup your old file just in case!)"
Update 2:
When you first boot, your keyboard is selected as "chinese". Simply change it to samsung or whatever else you may want to install...
Thanks to Bauxite!
File: http://forum.xda-developers.com/attachment.php?attachmentid=562977&d=1302188558
Source: http://forum.xda-developers.com/showthread.php?p=12722251&highlight=sensors.default.so#post12722251
Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App
Obama's>god said:
Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
will give that a shot, thank you
Edit: that worked like a charm thank you so much, love XDA!
No problem its one of the last pages. Someone also posted a file gralloc.something.so dont use that. It gave me a weird boot crash where id get the 3 vibrates from a force close over and over again.
Sent from my SPH-P100 using XDA App
just curious, are you using this same setup as myself?
curious if sprint can still make/receive calls send/receive messages... etc...
if you're even utilizing those features... just wondering, thank you again
You mean stock sprint? On stock you can send or recieve messages but no calls
Sent from my SPH-P100 using XDA App
ah no, i meant sprint with the overcome rom and the voodoo kernel. I know there is a lot different so i'm sure it wont work, was just curious
From what I understand its only gsm that can do calling. It's either going to take aosp or some serious serious hacking to get calls on cdma. Im hoping for cyanogen, but I still cant get a stable version of that for my brother's samsung epic.
Sent from my SPH-P100 using XDA App
This worked like an absolute charm!
can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!
galexandr said:
can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
1) Yes
2) No.
galexandr said:
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
You are very welcome
My Wifi all of a sudden quit working. I turn the Tab on, press the wifi toggle in the notification bar, and then it says "Error" and turns off.
That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.
mr2324jgf said:
That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.
Click to expand...
Click to collapse
I wiped data from CWM 3.0 and wifi started working again. I wonder what the issue was.
I'm also curious - would this technique work for the GSM CM7 port? Or is CM7 too far away from stock?
I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.
mr2324jgf said:
I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.
Click to expand...
Click to collapse
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App
followed the guide and still stuck at the samsung screen after flashing kernel, rom kernel.
This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?
cmoreno911 said:
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
I've since returned to overcome, I really wouldn't mind having my gps back... but i'm testing different options on it. It's fun to tinker with it, whatever the case, lol
idumych said:
This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?
Click to expand...
Click to collapse
the stock firmware has bloatware for any given carrier. the overcome rom is stripped of some of the nonesense without having to go into titanium and delete crap trial and error...
also, in the overcome rom, i can boot into recovery, reboot etc from the power button, whereas with the stock rom i can only power off....
not to mention, i dont have sprint and the sprint branding bothers me... custom boot etc makes me feel like i'm in control of my tablet.
the other benefit of myself and others doing this, is to try and FIX the gps, thus making this the best CDMA/Sprint option for the tablet.
etc etc etc....
thanks.
CyanogenMod 11 KitKat for Optimus S/V
This is a basic CyanogenMod 11 rom for the Optimus S/V. It has NOT been tested extensively and I take NO responsibility for any bricked phones, data loss or damages that occur as a result of flashing any version of this rom. It requires ClockWorkMod 6.0.4.5 or later, or TWRP 2.6.3 or later, in order to flash.
What works:
Phone calling (ZVH and ZVJ radios require a patch)
Wifi
Mobile data (thanks to thekraven)
USB tethering
Camera
USB mass storage, MTP
What's broken:
Bluetooth
Wifi tethering
SELinux
You tell me
CWM 6.0.4.6 can be found in the rom directory. Flash Skinny_4.4_Gapps.zip after flashing the rom to get Play Store and Google Sync. Other Gapps will probably be too big to fit on /system.
https://www.mediafire.com/folder/nfgfef6qpril7/CM11
Contributors:
skinbark
bigsupersquid
thekraven
Special thanks to the CyanogenMod and androidarmv6 teams, also gu5t3r for GOptimize.
CM11 KitKat os2sd Version:
cm-11-20140116-thunderc-skinbark-sd.zip is a version of CM11 which is designed to run off your sd card.
To use this version:
1) create and format 3 ext4 partitions following the fat32 partition on your sd card (use gparted not a windows partitioning tool)
/data - at least 256 mb (512 mb or more recommended)
/system - at least 256 mb
/cache - at least 256 mb
2) format /boot in cwm
3) install cm-11-20140104-thunderc-sd.zip
4) install Skinny_4.4_Gapps-sd.zip and reboot
Known Issues (in addition to those in post #1):
formatting/backup/restore issues
possible reduced performance (older/slower sd cards)
reduced battery life (?)
Add wipe zips to a folder on your sd card and flash them from recovery to clear external /data, /system, /cache, or all three.
CWM_6.0.4.6-thunderc-sd.zip is a special version of CWM for os2sd that should only be used if you understand how it works.This version of CWM is not necessary to flash the os2sd rom. See this post for more info about recovery issues with this rom.
A Class 10 microSD card is recommended for best performance.
Power off or reboot to recovery before removing sd card.
os2sd mod courtesy of bigsupersquid
https://www.mediafire.com/folder/dj2d4vpp0hzvb/CM11sd
Warning: This is a highly experimental setup and a work-in-progress. You should have adb installed and know how to use it, along with the flash_image command, before attempting this install. If you have trouble installing this and are unsure how to resolve the problem ask for help on this thread. I take no responsibility for bricked devices, data loss or any other damages resulting from the use of this software. USE AT YOUR RISK.
New build with rild fix for ZVD/ZV5. You'll want to upgrade to this for stability and battery life even if you're not activated.
cm-11-20131225-thunderc-skinbark.zip
Link in OP.
Merry Christmas guys!
Sweet! Will flash once o find my ov...
Virgin fix uploaded.
Virgin.fix.CM11.0.zip
Link in OP.
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
captaincrook said:
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
Click to expand...
Click to collapse
Well the biggie right now is getting data going which is sort of difficult for me since my phone's not activated (next week I hope). I'm assuming you're not activated? I guess just general stability and performance, battery life, see what you can run on on it, put it through the wringer. All info is welcome since I really haven't had much feedback yet. It seems to be pretty stable. Let me know if you have any problems, thanks.
really works well...nice job. No chance to test 3g data yet, but everything else works very well...I had to install a keyboard manually, and the battery stats are wrong (fully charged, and stayed fully charged all day) but it is def a daily driver for me.
I uploaded a new 'OS2SD' rom with special recovery, gapps and virgin fix:
cm-11-20140101-thunderc-sd.zip
CWM_6.0.4.6-thunderc-sd.zip
Skinny_4.4_Gapps-sd.zip
Virgin-fix-CM11-sd.zip
Link in post #2. Happy New Year!
Got the order of the partitions wrong in post #2, sorry. Fixed now. 3G fix coming soon!
I uploaded new standard and os2sd builds with data fix.
cm-11-20140104-thunderc-skinbark.zip
Link in post #1
cm-11-20140104-thunderc-sd.zip
Link in post #2
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
captaincrook said:
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
Click to expand...
Click to collapse
long press home and press the three-bar onscreen button to close running apps.
also fast reboot off market is very handy to manually clear ram. heard about that one from andyopie150, like it.
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
For now I can just suggest the usual speed-up stuff - turn off animations, ksm, cpu/governor etc. There may be some build.prop tweaks you could use, and I'm expectiing zram support to be enabled soon. Crossbreeder might be something else to try. If we could get ART going it might help some but I don't know if that's likely. I probably won't try to tweak the stock keyboard, there's plenty of alternatives available.
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Trozzul said:
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Click to expand...
Click to collapse
regular rom or os2sd?
skinbark said:
regular rom or os2sd?
Click to expand...
Click to collapse
regular i tried a different CWM 6+ and that one gave me the error*
Trozzul said:
regular i tried a different CWM 6+ and that one gave me the error*
Click to expand...
Click to collapse
Here's another recovery you can try.
https://www.mediafire.com/?s8c94941y8kubdd
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
Any information is a good thing, positive or negative. Harmonia with the Xionia kernel fairly flies speed-wise, but everything since that seems to choke my phone somewhat. And Mirage is the best Gingerbread available... but I enjoy the extra features more than the speed, which is what keeps me trying for the bleeding edge.
(example: the double-tap-hold-and-slide to zoom is built in all over 4.4, in 4.2 I only saw that in Maps.)
ART may or may not happen. I have to learn more thumb assembly to fix it. My decent class for school this session (the easy one since I did 8088 back in 1991) is x86 assembly. Doesn't apply, but maybe I can get more parallell info from it. There's lots of good info out on the net with minimal searching as well, but not much if any on downconversion of thumb2 to thumb1 code. I found enough to fix a few files but there's still more to go. I'd be impressed with myself if I got that to run.
CrossBreeder seems to work.
Shiny ROM: Android 4.4.4, KTU84P for VZW Galaxy Nexus (Toro)
Skip right to the downloads (if you dare )
Hello there XDA GNex community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:
Overview
This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.4, build KTU84P
Source (AOSP) built kernel (boot.img)
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!
Other IMPORTANT Information
Root
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.
Updates
Now that the ROM has gotten to this stage, the update policy needs a bit of editing Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.
Radios
This ROM will (most likely) work with any toro radios; however, I of course recommend using the most recent, Verizon-approved radios which are the FK01 and FK02 radios. My ZIP installation package for these radios can be downloaded here.
Bootloader
Once again, I'm assuming that this ROM will work with all tuna/toro bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.
ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, 6.0.4.3. You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.
Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. The file name for all builds up to and including the 11/10/13 build always begins with baldwinguy77_toro_aosp so you know that it's my build for toro. All builds after 11/10/13 begin with the prefix ShinyROM_toro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
Source
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!
File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/
Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!
Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
ROM
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, the radios installation ZIP, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash FK01_FK02_Radios-signed.zip
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_toro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!
**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.
Mods
1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.
ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!
ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!
Credits
As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the Shiny ROM server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy who helped me out with a GPS issue that popped up in 4.2.
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
XDA - By providing such a great Android community, ROMs like this one are able to easily connect with users and get their work out there
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention.
Schoat333 - A user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him!
Yarly - The most experienced admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev who also took the time to talk with me and answer a few of my questions.
Thanks to everyone for their hard work and sharing that work with others!
DISCLAIMER
Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.
Okay that's about it! THE ROM DOWNLOAD LINK AND A SUMMARY OF ALL FILE DOWNLOADS CAN BE FOUND BELOW!
ROM Download & Changelog
ShinyROM_toro_aosp_080914-125720-signed.zip
MD5: 5844c6e48fb30bbafc976199c5c1effd
Fixes/Changes Included So Far
(older changes)
6/21/14 CHANGES
Updated to Android 4.4.4, KTU84P
8/9/14 CHANGES
Added system-side support for native screen casting
Added Italian translations for the Shiny restart menu (courtesy of XDA user lparcshinoda)
Switched to prebuilt version of CellBroadcastReceiver in an attempt to fix issues with it on toro
Mods
Before installing any of the packages below, please be sure to check out the mod installation instructions in the OP!
Key
To make mod installation more convenient, all mod links will now be color-coded based on the files they change. The key shows what each color corresponds with:
Red - SystemUI.apk
Blue - framework-res.apk
Purple - SystemUI.apk & framework-res.apk
Green - Other
If you install mods that are in the same color group, it is likely that they will overwrite each other. It is OK to overwrite a previously installed mod, but please note that the originally installed mod will no longer be there. If you want to completely revert to stock, flash the "Back to Stock ZIP" mod under the baldwinguy77 mod section. This mod replaces your SystemUI.apk and framework-res.apk files with ones from the stock ROM.
Developer-specific Mods
All of these mods have been provided by some really awesome mod developers who take the time to continue to make updated mods for my newest ROM builds. That being said, they have lives and can't always get the mods out right away, so make sure the date next to their name matches the build you're running! They usually are around the thread and are open to doing custom mods if you ask Be sure to thank them and check out the credits section for more info!
Baldwinguy77 (Updated for 8/9/14 build)
Back to Stock ZIP - Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Stock kernel flashable ZIP - Overwrites any custom kernel you have installed with the stock kernel normally packaged with the ROM.
Inmanster (Updated for 3/9/14 build)
36 DPI Nav. Bar - Replaces the stock navigation bar with a smaller (height-wise), 36 DPI version.
Black Dash-style Softkeys - Replaces the stock navigation bar buttons with black, dash-style ones.
Blue Stock Softkeys - Replaces the stock navigation bar buttons with blue-colored ones.
Carrier Text Replacement - Replaces the carrier text on the lockscreen and pulldown notification shade with "Galaxy Nexus".
Extended Battery Framework Mods - Improve accuracy of battery level reporting for those using extended batteries.
2100 mAh (with Carrier Text Replacement mod)
3050 mAh
3800 mAh
5900 mAh (with No CRT-off Animation mod)
Grey Battery Percentage - Enables display of the current battery percentage in the status bar with grey-colored font.
InmanMod - A combination of the 2100 mAh battery, no CRT-off animation, carrier text, 36 DPI nav. bar, and white zenyth softkeys mods.
No CRT-off Animation - Removes the stock, default CRT-like screen off animation.
White Zenyth-style Softkeys - Replaces the stock navigation bar buttons with white, zenyth-style ones.
Universal Mods & Downloads
These mods have been compiled by myself, sometimes in conjunction with the modders above, to always work with any version of the ROM (but not necessarily any device). Therefore, you don't have to worry so much about these being up-to-date because they should always work. If that is ever not the case, simply PM me and we'll get it fixed This section also includes some other Verizon Galaxy Nexus related downloads such as the latest radios and bootloader. You can use these according to the installation instructions in the OP.
Universal Mods
AOSP Web Browser (for Android 4.4) - Installs the AOSP web browser with Chrome bookmark syncing for Android 4.4.
DSP Manager(for Android 4.4) -Installs the DSP Manager app along with the audio libs and configs important to running the service, allowing you to customize the audio equalizer of your device. At the moment, certain apps on Android 4.4 do not work with the modular DSP service.
ClockworkMod Images
Touch 6.0.4.3
Non-touch 6.0.4.3
ClockworkMod Recovery Flashable ZIPs
Touch 6.0.4.3
Non-touch 6.0.4.3
Chainfire's SuperSU Root Control App and ROOT Flashable ZIP (Works with 4.3 & 4.4)
Download (Latest version, v2.02)
Toro Radios[/size]
FK01 & FK02 Radios Flashable ZIP (Latest)
FF02 & FG02 Radios Flashable ZIP
Tuna Bootloaders[/size]
PRIMEMD04 Bootloader Flashable ZIP (Latest)
PRIMELC03 Bootloader Flashable ZIP
Thanks for your roms, they have been the daily driver on my wifes GN since you started posted them way back when.
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
Are you sure it's only when plugged into a wall charger? If that's true, it sounds like a hardware issue, but I think you probably just happened to notice it at that time. You may want to try out the 1/4 build as that one seems to work well for people with mobile data-related problems in the newer builds.
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
hotrodwinston said:
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
Click to expand...
Click to collapse
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
kielby said:
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
Click to expand...
Click to collapse
By the way I reflashed the 4.1.1 (JRO03O) radios from radio thread without changing anything else and the problem seems to have gone away.
What kernel should I use with this ROM to get the best performance/battery life combo. Link please!
Sent from my 2013 Kindle Fire HD
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
RoxRedEye said:
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
Click to expand...
Click to collapse
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
3/9/14 Build Information
Hey there everyone! It seems like it's been awhile since the last time I got make one of these new build posts, and I have to say it feels good to be able to do it again! I first have to apologize for my absence both in terms of development and communication in the thread. I'm getting close to the end of my sophomore year in college, and let's just say it has been keeping me extremely busy. I don't mind it, but I just wish it still left more time for me to do Android-related things! Luckily, I had a whole week off to catch up on a lot of things, including Shiny ROM development. So with that, we have a new build ready to go that includes a very minor update to the AOSP base of the ROM as well as some not so minor updates to the telephony stack. What this means is that mobile data and voice performance/reliability may have some big improvements in this build. We didn't get a chance to do a wide-scale test with these changes, and they're only in the master branch of AOSP, but after reviewing the code I'm hopeful that they'll bring improvements for us. That being said, be sure to leave your feedback here on the thread so we know how it's working! If you experience any problems, try to grab a logcat and let us know about them so we can try to get everything straightened out! So after reviewing the other information and installation instructions below, head over to the download post to grab the new build!
I also want to take this opportunity to point out that Shiny ROM has a new website! For now, the URL/domain is still http://shinyrom.goofball.org/ to stay consistent. The website has a lot of information about Shiny ROM as well as some future plans. It also lists details for the newest build of Shiny ROM along with download links, etc. I'm hoping that this website serves as a good platform for Shiny ROM to grow as we can now deliver a lot of information without having to worry about it getting buried in the forum and whatnot. So check that site frequently for Shiny ROM news and updates as well as information about new builds! There is also a contact form there for everyone to leave their suggestions, report bugs, etc. I hope you all like it!
(You can still access all of the Shiny ROM files here.)
Thanks to everyone for your continued support of myself and Shiny ROM!
Installation Instructions
Download desired ZIP files (ROM, SuperSU*, mods, etc.) and place on internal storage.
Reboot to the latest version of your preferred custom recovery (CWM or TWRP).
Wipe cache.
Wipe dalvik cache.
**OPTIONAL** Wipe data/factory reset (will erase user data like apps and saved games, etc., but may fix strange bugs).
Flash ROM.
**OPTIONAL** Flash other desired ZIPs (SuperSU, mods, etc.).
Reboot.
Enjoy!
*As of 3/9/14, the latest version of SuperSU is v1.93.
baldwinguy77 said:
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
Click to expand...
Click to collapse
No worries. Thanks for the reply and thank you for your hard work bringing us a stable stock KitKat. Glad I have extra batteries with me - gonna download and flash asap.
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
asilentcivilian said:
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
klobkelosh said:
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
Click to expand...
Click to collapse
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
asilentcivilian said:
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Glad to hear it! Thanks for your support!
baldwinguy77 said:
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
Click to expand...
Click to collapse
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
klobkelosh said:
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
Click to expand...
Click to collapse
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
baldwinguy77 said:
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
Click to expand...
Click to collapse
I'll take that under consideration, but man it was really killing me. Following new rom flash, for everything set up, charged up to 100 percent. Good. Drive to dinner, 30 mins, in and out of 4g and 3g, battery at 80 percent. After 2 hour dinner on 3g, 60 percent. Back home 40 percent, lots of hand offs. She's nearly dead now and I haven't even used her tonight. I love this ROM, but she's not right...