android by polyrhythmic:
Eclair 2.1 for Kaiser/Vogue/Polaris -- polymod 2.1 Delta (Final Stable Version)[Based on OpenEclair 1.3.0.1 (XDA thread)]
Please see polyrhythmics thread for screenshots
BOTH themes have updated Desire settings icons and QVGA dialer:
NAND install:
This is an beta build! I am not responsible if you brick your phone or a tornado lands in your yard due to flashing to NAND!
How to flash a ROM for Kaiser
Questions? Don't forget to use the search!! Your question has probably been asked and answered before. Also, here's an Android on Kaiser FAQ
What works:
Normal Sleep/Suspend (not hacked!)
Calls/Txt
3G Data/MMS
Wifi
Full GPS with AGPS
Network (Cell-Tower-based) Location (fixed)
Hardware OpenGLES
Google Apps
Google Sync
Exchange Calendar
Facebook
YouTube
OpenEclair 1.3 Upgrades:
Newer AOSP 2.1r1 code
Gallery3D
More Messaging Options, like:
* White-Text-on-Black
More working LiveWallpapers:
* Polar Clock fully working
* Maps
* Spectrum
* VU Meter
* Waveform
* 'Many'
Improved stability & mem management
polymod Upgrades:
Updated RIL
Hacked Market Included
MarketEnabler Now Included
BT & Wifi Updates Included
Wifi Power Level now 'Medium' by default
* Wifi Power Level Updates still work
Fully PNG-optimized, including Phone and Framework
Latest Maps, Voice, and other apps updated
More available space for apps in /data partition
* No more data/app_s for us (not needed)
* Symlinked /system/etc/wifi/wlan.ko to /system/lib/modules for our kernel
Apps included in this build:
Live Wallpapers: Grass, Beziers, Bobs, Polar Clock, Visualizations
Taskiller Free 1.8.1 (no ads + CUSTOM THEMED TASKBAR WIDGET) [Free]
Facebook (full sync working)
Myspace
Car Home
Desk Clock [new!]
YouTube
Powerbar Widget
Genie Widget (a.k.a News and Weather app)
Nav Launcher [Free]
Tetherbot [Free]
GPS Test [Free]
extra terminal tools in bin/xbin: rwsystem, rosystem, nano & more
Voice Dial/Search/Keyboard
Speakerphone
YouTube HQ
'Reboot'
Skin information & credits:
* Light Tray Launcher from gChrome by Moonspoon (link)
* Dark Tray Launcher from Gloss by Moonspoon
* Dark Theme Colored Notification Icons from Zapote21's Zapmix 0.95
* Black Notification Bar and Notification Tray Handle from OpenEclair MetaMorph put together by JAguirre1231 (link)
* custom wallpaper, robot from (link)
* custom dark-themed taskiller bar
Thanks to Polyrhythmic for his support and permission to continue to provide this build. Polyrhythmic's Original thread, Thanks also to Kallt_Kaffe for the use of his custom kernel which I have included in the download.
Zenity's Changes:
Integrated Camera update : Camera often FC's in Haret installs due to excessive startup times
Integrated Cell tower location and pin verification
Added dark themed build
Removed the following expired apps;
Astro
maps
facebook
nav launcher
(all these apps are available in Market)
For Nand users, NBH is set for panel2, 320x428 @ 143 density, use rogue tools to change density, if you prefer another resolution or if you need a different panel type you will have to edit the nbh using Loserskaters NBH Editor, and reflash it.
For advanced users: You can edit the NBH to reduce the system partition using the NBH editor, I suggest 82Mb minimum for /system, this will give more space on /data.
Light Themed Version: http://rapidshare.com/files/414148706/Final.zip (MD5: 3A6F15C2AF27048A4DF7AFB95C951DAD) (3156)
Dark Themed Version: http://rapidshare.com/files/414221873/Final-dark.zip.html (1829)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Created another Romantically Apocalyptic themed Splash screen exclusively for Polymod, download, rename as kaisimg.nbh, put on SD, flash, enjoy : Polymod/Zenity Bootsplash (16)
Having been asked about Donations, I would like to request that anyone wishing to should donate to Polyrhythmic, it is his build, I am only maintaining it.
(Note: the numbers in brackets following the download links are an infrequently updated download count)
Installation instructions.
Nand:
You must have HardSPL installed, recommended minimum version 3.29.
Recommended Radio version 1.65 or above.
MicroSD card must be formatted Fat32.
Download whichever themed version you prefer.
Unzip the downloaded file to a suitable temporary folder, then copy everything to SD card root.
You will now have an SD card with one file on root,(KAISimg.nbh), and one folder,(andboot), place this SD in your device and flash the NBH using bootloader method, ( if you are unsure of how to do this please read through Dukenukemx's excellent guide: http://forum.xda-developers.com/showthread.php?t=680518).
Once you have flashed the device you must remove the battery, then replace it and power on, once you have the scrolling text press and hold the centre of the lcd screen until you get the install menu, ( you can also use dpad centre button, or volume up button ).
Once in the installer menu check that sys on nand, data on nand are starred, then choose option 1: install (yes, you know you will wipe your present system, yes, you want to clear data).
Once the installer finishes choose quit, and wait until the initial boot completes, ( this will take a little time, but once you see the boot animation everything is going well).
This next stage is important, please read carefully, or your system will likely be unstable.
Once you reach the welcome screen, press the android, skip the intro, skip the sign in, press next to both the following screens, and once this is complete, wait, for at least 15 minutes, with this build ,(as with most deodexed builds), it is important not to dive in and mess with things, the system needs time to copy the odex files to cache, if you interrupt this you could get a load of fc's, and most likely have to reinstall.
Once you have completed the waiting stage, you are usually best to power down, and reboot, your system should now be ready to begin using.
Initial setup:
This is common to both haret and nand installs, and is my usual procedure with most android roms, it should help with both battery life and speed.
In settings;
In Sound and Display, uncheck Orientation.
Set animations to Some. (you may wish to leave this at All).
Add google account.
In Spare Parts;
Set Window and Transition animations to Fast.
Check Home app in memory.
Advanced options: These may yield additional performance.
Use either Compcache or Swap, using both may actually slow the system down, you will require an SD card that has been partitioned with a 64Mb swap partition for swap.
Installation Instructions.
Haret/SD:
You must be using at least Windows Mobile 6.1
Recommended radio version is 1.65 or above
MicroSD card must be formatted Fat32 and be at least 2GB
Download whichever themed version you prefer.
Unzip to a temporary folder, then copy the files to SD.
You may delete KAISimg.nbh from SD, it is not required for Haret installs.
Fisrtly you must rename one of the default-device.txt files to default.txt, or alternatively edit the default-device.txt file and save as default.txt.
What you may need to edit/add;
board-htckaiser.panel_type=x, panel type may be 1,2,or 3, it should be apparent on boot is you are using the wrong panel type, the screen may be wrongly coloured, or have odd pixels, streaks etc, reset the device, change this option and run haret.exe again.
mddi.width=240 mddi.height=320 sets the screen resolution, default is 240 320, other common values are 320 428 and 320 480. (see lcd density).
lcd.density this also affects how the display looks, larger values make the everything on screen look smaller, default for 240x320 is 160, 320x428 is 144, 320x480 is 120,
board-kaiser-keypad.atttilt=x sets the keyboard map, 0 is querty US, 1 is at&t Tilt, 2 is Nordic, 3 is azerty, 4 is qwertz.
Once you have edited and saved the default.txt file it is time to install it to SD.
run Haret.exe, once you see the scrolling text, press and hold the lcd screen centre, ( you can also use dpad centre, or volume up keys), until you get into the Installer menu.
Once in installer menu choose option 1: install, and yes, this will wipe any system on SD card that you may have previously installed, it will not wipe WM.
Choose yes to wipe previous system, and data, wait until the installer has finished and returned to the main menu.
Choose quit, and android will continue to boot.
This next stage is important, please read carefully, or your system will likely be unstable.
Once you reach the welcome screen, press the android, skip the intro, skip the sign in, press next to both the following screens, and once this is complete, wait, for at least 15 minutes, with this build ,(as with most deodexed builds), it is important not to dive in and mess with things, the system needs time to copy the odex files to cache, if you interrupt this you could get a load of fc's, and most likely have to reinstall.
Once you have completed the waiting stage, you are usually best to power down, and reboot, your system should now be ready to begin using.
Initial setup:
This is common to both haret and nand installs, and is my usual procedure with most android roms, it should help with both battery life and speed.
In settings;
In Sound and Display, uncheck Orientation.
Set animations to Some. (you may wish to leave this at All).
Add google account.
In Spare Parts;
Set Window and Transition animations to Fast.
Check Home app in memory.
Advanced options: These may yield additional performance.
Use either Compcache or Swap, using both may actually slow the system down, you will require an SD card that has been partitioned with a 64Mb swap partition for swap.
Data ( 3G etc), under Haret: Notice that you may have to start a data connection in Windows Mobile before running Haret.exe, failing to start data May prevent 2/3G data from working correctly under Android.
Sounds like you've got some good things to add to Polymod that it's needed for a long time. Best wishes and have fun with the build!
Always had fun with your build poly, no matter what I tried, I always ended up re-installing it
I know you stated it in the other thread but what are all the changes you did to delta?
and is your download themed like the screenshots (those are gamma I think)...I loved the dark theme.
The first post is pretty much a placeholder at the moment, It will be evolving to reflect the status of 2.1D soon, I am working on the screenshots and changes at the moment and will update the first post as soon as possible.
Delta is now available in both light and dark themes, screenshots will follow soon
Absolutely top notch instruction and ROM.
Far more stable than my previous attempts with other ROM's. Ill be watching this closely.
Thanks a lot zenity.
Thanks, it has always been my favourite build, and just needed some updating to bring it back to life
I only received my Kaiser ( well, TytnII here) on monday. Ive gone through about half this subforum already Every other build I've tried managed to go fine until I put my sim in... then it went south from there....
Will see how it goes with this build once Ive tweaked as per your guide....
Notice your using radio 1.70, not sure about SA, but it is possible that you may get on better with 1.65 series, ( European users certainly do better on this radio), really depends what the actual issue is with the sim card?
Hmmm, maybe you're onto something. I'll give the 1.65 you are running a try...
Well if it's a lot of 'no service' problems, then that may sort it, did for me
Hi zenity!
What is wrong with installing Haret?
Once you select quit, and android continue to boot, system hangs and nothing happens!
Any ideas?
Hmm, I'll look into that, but remember running from haret is slower, and the initial boot does take quite some time, it will appear to hang even on nand for a few minutes before continuing to load, if it does not reach the bootanimation within 5 minutes, then something may be wrong with the haret files, I'll flash WM and check that.
ok
Just for your information - once pressed quit, I wait more than 10 minutes!
Just reflashed to WM, installed, it does take a lot longer than nand, quit, it does appear to hang, but finally went to bootanimation, and is running now, time is under 30 minutes, and that includes the WM reflash, so there are a few things to check.
WM version, must be 6.1 minimum, anything lower and you will get problems, guaranteed.
Try another SD card, remember for haret you need 2Gb minimum, it must be freshly formatted as Fat32, you really will need a lot of free space on the SD, (it is possible on a 1GB, but it will be really tight, and things may fail if there are bad blocks).
Remember if you are copying files to SD through activesync you must remove the usb cable safely, same goes for SD card adaptor, always use safe removal, as not doing this can leave data unwritten, ( safe removal writes any cached data before telling you it is safe to remove).
It is possible that the download is corrupt, you may want to redownload just to be certain, but try reinstalling everything from scratch first.
I have been having problems with anything downloaded from rapidshare lately. all the androidinstall.tgz are unable to open. giving this error...
Code:
gzip: stdin: invalid compressed data--crc error
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
I though this was just my setup but if others are having install problems this may be
a file curruption issue. try re-downloading and see if you can open the androidinstall.tgz
this has been an issue with other builds as well as of lately.
please, make some screens
zenity said:
Well if it's a lot of 'no service' problems, then that may sort it, did for me
Click to expand...
Click to collapse
It wasn't no service, it was just plain locking up only while using the data connection. Wifi works 100% with no lockup. Will try it with the current radio then the new radio and give you soem feedback here.
Related
THIS IS NOW OUTDATED!!
It uses the old sqsh method WITH a rootfs. So if you're wanting to use the NoMoRootfs method, this won't work. Please use the already complete builds in the Kaiser/Vogue threads as they are working the best at this moment.
I hope to update this when I have some free time. Will include a how to for NAND also.
What's What:
zImage
Linux kernel which initializes hardware
initrd.gz
Initial ramdisk. Usually, startup scripts, device drivers (modules) and related files (e.g. Bluetooth firmware), as well as some basic system tools (shell etc.). This has grown and split into the rootfs.img.
rootfs.img
Contains the ril (how our phones communicate with the network) and other necessary files to get the system going.
haret.exe
Bootloader to reboot the device into Android
default.txt/startup.txt
Contains settings for the boot process, and special kernel configuration parameters
system.img/system.sqsh
Contains the Android core, default applications and some more system files and tools.
*.user.conf
Contained in conf folder. Sets compcache/swap parameters.
How it works
When you run Haret, it wipes Windows from memory so it's not running anymore, (although it keeps it on the actual phone storage) then it "reboots" the phone into android. So think of it like this... Windows is on the phone storage and Android is on the SD card. Haret shuts down Windows (keeping it on the phone storage) and then boots up the phone using the SD card in place of the phone storage. When you turn the phone off/reset it will boot back into Windows.
Haret looks at the default.txt/startup.txt for it's bootup parameters, it then loads the zImage which initializes all of the hardware (screen, keyboard, etc.) and initrd which contains the initial startup scripts. The rootfs is then called which creates the data.img and moves the system and data to partitions (if available). It looks in the system.sqsh for a file called ion.build, donut.build, tattoo.build, etc. which tells it what kind of system it is. This also tells it to run the ion.user.conf, donut.user.conf, tattoo.user.conf.
Setup:
Download this package.
If you can't run this then you'll have problems with other builds. If you can run this, things are on the right track.
Format your SD card to Fat32, if not already. Make sure there's NOTHING on your SD card.
Extract the android folder to your SD card.
Rename the default-*.txt file to either default.txt or startup.txt.
-default.txt will make it so you have to tap "Run" when you start haret.
-startup.txt will cause haret.exe to automatically run instead of having to tap Run.
Now when you run haret.exe you should see some scrolling text.
Don't touch anything and let it run.
You should soon be presented with a startup animation and then be ready to setup your new Android phone.
Advanced:
Partitioning SD
Installing Ubuntu (Live CD)
DOWNLOAD UBUNTU
You should now have an .iso image.
DOWNLOAD IMGBURN
Install ImgBurn
Select "Write image file to disc"
Click on the magifying glass/folder next to where it says "Please select a file..." and select the .iso file you just downloaded.
Uncheck Verify (underneath "destination")
Click on the picture on the bottom left to burn.
Once it's burned restart your computer with the disc in the drive.
You should then see the following image:
*If you boot into Windows you'll have to consult your motherboard manual on how to boot from a CD*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select your language and then select Try Ubuntu
Installing Ubuntu (USB)(thanks sd73ta)
I haven't tested this but you can make a bootable USB drive with Ubuntu using UNetbootin
1 - download unetbootin
2 - insert a blank usb drive
3 - select ubuntu (the highest numerical) live version and run
4 - when its done reboot your pc
when it first boots look for instructions on how to enter setup usually F2 or Delete
5 - change your startup options so usb is before hdd
6 - save changes
Now it should boot to ubuntu
Partition your SD Card
Follow my vid:
Extract the android folder to the Fat32 Partition
Install Android to Partitions
Run Haret
Pay close attention to the scrolling text.
When you see "Press Voldn to run Android Installer" press the left softkey(the key just right of the green phone button)
It should now be placing the system.sqsh onto the first ext2 partition and creating a new data.img on the second.
To see if this actually worked, when you restart your phone into Windows you should see a folder called "backupsystem" with an installedsystem.sqsh file inside.
Swap/Compcache
*WARNING: Using a swap file/partition can decrease the life of your SD Card*
To use swap/compcache you'll need to edit your *.user.conf file which can be opened using any text editor. It should be easy to follow what everything in the file does, but if you can't figure it out SEARCH FIRST and then ask.
To utilize the swap partition you'll have to change
cc_backingswap_en=0 from 0 to 1
OR
linux_swap_en=0 from 0 to 1
Very Advanced (NAND)
NAND refers to the actual phone storage (where Windows resides). This wipes Windows from your phone and writes Android to the internal storage. It's not completely developed yet, but it's getting really far really fast.
There is already a thread HERE that discusses everything you need to know about running Android from NAND.
Upgrading to different builds
Simple Install(no partitions)
Most new builds will just be a system.sqsh file. If thats the case then you'll need to replace the system.sqsh file with the new one. It's also best to delete the data.img file.
If the new build contains a zImagexx-xx-xx or rootfsxx-xx-xx.img, then you'll need to replace those too. When you replace them, make sure to rename them to zImage and rootfs.img, unless theres a new default.txt where you don't have to rename them. Make sure you READ EVERYTHING the thread says about the build so you don't ask questions that have already been asked.
Advanced Install(partitions)
Almost the same as the Simple install but instead you'll just need to place the new system.sqsh file in the android folder and then pay attention to the scrolling text. You'll want to run the installer (Voldn) and when it asks to upgrade press Voldn. You can backup your data, and I would suggest wiping the data also to prevent any bugs.
Problems & Fixes
If your screen looks like it has random dots and things dont look quite right, open the "default.txt" and change board-htckaiser.panel_type=0 to 1, 2, or 3. This depends on your device and you should try each one to get the best result.
If you close the keyboard and the screen is now stuck in landscape, go to Settings > Sound & Display and uncheck Orientation.
If you just upgraded to a new build and are getting popups about things not responding (force closes) then you probably didn't get rid of the data.img file or wipe the data partition. If you have a blank data file/partition and are still getting errors, then look through the builds thread to see if others are having the same problems and if theres a solution.
If you can't get a data connection to work, go into Settings > Wireless Controls > Mobile Networks > Access Poin Names and if there is something present, select it and make sure all the settings are correct for your carrier according to THIS LIST. If there is nothing there, press the menu key (start button) and select New APN and enter the settings manually.
*More when I can think of them.*
FAQThere's a very nice FAQ HERE
loserskater said:
Resereved just in case... maybe FAQ/etc.
Click to expand...
Click to collapse
thx for making this loserskater! i found your post through the vogue general section and the file descriptions were exactly what i needed to know.
Hey loserskater! First off great post, I followed your instructions, and unfortunately although linux initiates the boot process it halts giving me the following error: Failed to allocate the storge;
This was using the basic setup I will now try the advance setup with live cd and let you know how it goes..
-b3ck
b3ck said:
Hey loserskater! First off great post, I followed your instructions, and unfortunately although linux initiates the boot process it halts giving me the following error: Failed to allocate the storge;
This was using the basic setup I will now try the advance setup with live cd and let you know how it goes..
-b3ck
Click to expand...
Click to collapse
Sorry, I had a couple files mismatched... updating the first post now. Just tested and its working fine now.
exellent thread, im gonna link to it in my sig!!!
loserskater said:
Sorry, I had a couple files mismatched... updating the first post now. Just tested and its working fine now.
Click to expand...
Click to collapse
Awesome thanks! Downloading now, I'll let you know how it goes =)
...
So far so good, I am looking at the ANDROID animation right now, so quick question since I am running this from an exe from the windows mobile os, is windows mobile still running in the background while I am using the ANDROID part, or does it completely shut down windows and load up the linux os, just wondering.. thanks.
...
Everything works great still can't get the 3G part working but I read somewhere that is because the tilt uses a different MHz than t-mobiles 3G, dunno if I can get it to work or not.. any ideas?
-b3ck
So what androids can I use with my HTC Tilt? yours works great, can I use just any of the ones I find on the 2 other forums you liked to in your post?
-b3ck
Great (and much needed) thread, loserskater - THANKS.
I have simple question: just how is the correct *.user.conf file selected? Is there a selection mechanism in system.img, or is there some other mechanism?
Thanks again for the partitioning walkthrough. And Ubuntu 9.10 is pretty darn nice, too!
b3ck said:
So far so good, I am looking at the ANDROID animation right now, so quick question since I am running this from an exe from the windows mobile os, is windows mobile still running in the background while I am using the ANDROID part, or does it completely shut down windows and load up the linux os, just wondering.. thanks.
Click to expand...
Click to collapse
When you run Haret, it wipes Windows from memory so it's not running anymore, (although it keeps it on the actual phone storage) then it "reboots" the phone into android. So think of it like this... Windows is on the phone storage and Android is on the SD card. Haret shuts down Windows (keeping it on the phone storage) and then boots up the phone using the SD card in place of the phone storage. When you turn the phone off/reset it will boot back into Windows. (added to first post)
b3ck said:
Everything works great still can't get the 3G part working but I read somewhere that is because the tilt uses a different MHz than t-mobiles 3G, dunno if I can get it to work or not.. any ideas?
Click to expand...
Click to collapse
Look in the second post under problems & fixes and make sure you're APN settings for your carrier are correct. I have 3G and I'm on AT&T.
b3ck said:
So what androids can I use with my HTC Tilt? yours works great, can I use just any of the ones I find on the 2 other forums you liked to in your post?
Click to expand...
Click to collapse
Look in Kaiser Rom development or the Vogue General forum for builds. Follow my upgrading procedure and you should be OK. If you're having problems with that build look through the thread and see if others are using different zImages, rootfs.img's, etc.
wanderso said:
Great (and much needed) thread, loserskater - THANKS.
I have simple question: just how is the correct *.user.conf file selected? Is there a selection mechanism in system.img, or is there some other mechanism?
Thanks again for the partitioning walkthrough. And Ubuntu 9.10 is pretty darn nice, too!
Click to expand...
Click to collapse
Look in the first post under How it works. (just added)
Yes Ubuntu is a very user friendly and popular version of linux. It was my primary OS for awhile and didn't have any problems with it. The best part is if you mess something up, you can just reinstall the OS and start over.
I use unetbootin instead of a live cd. this creates a live usb drive.
1 - download unetbootin
2 - insert a blank usb drive
3 - select ubuntu (the highest numerical) live version and run
4 - when its done reboot your pc
when it first boots look for instructions on how to enter setup usually F2 or Delete
5 - change your startup options so usb is before hdd
6 - save changes
Now it should boot to ubuntu
hope this helps. I havent done this in a while so if I missed something let me know and I'll fix it
Thanks for your help, very much appreciated!
Your the man!!!!!!!!
Thank you sir for this great tutorial!!!! it was the diff between me using android and me wanting to never try it again.
Thanks for great instructions!
I don't know what I did wrong, but the "Voldn" installer did not copy my system.img to the first partition. Only after I manually copied the content I was able to boot.
Question: how big the first partition should be? The system.img is only 74Mb, but all the related to the subject demos suggest to create a 256Mb ext2. Is not it a waste of space on a 2Gb sdcard?
zc2 said:
Thanks for great instructions!
I don't know what I did wrong, but the "Voldn" installer did not copy my system.img to the first partition. Only after I manually copied the content I was able to boot.
Question: how big the first partition should be? The system.img is only 74Mb, but all the related to the subject demos suggest to create a 256Mb ext2. Is not it a waste of space on a 2Gb sdcard?
Click to expand...
Click to collapse
You can use two 128 MB partitions to save space. You just don't want to get too small or you'll start having issues
I tried to install Android on my htc touch and it comes up with "Launch a script file. Default path is the same where the executable lives." What do I need to move and where to get it to work? Thanks
Thanks for the answer.
I made 128Mb and 269Mb. After I reboot my Tilt I found the Home and the Green Call button do not work anymore! And some other system settings were changed as well.
I had to run the instaler for three times before I finally got the system working.
This is great!
Could someone alternately host the Starting_Point file please? I have tried to download it multiple times and it doesn't complete ever.
Does anyone else have data access issues? I am unable to get any data with this build
vexersa said:
Does anyone else have data access issues? I am unable to get any data with this build
Click to expand...
Click to collapse
check the second post under problems and fixes (last one)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3.2.1
This build is the exact copy of my RAFDROID HD EXT
the difference is that some parts of the system are "squashed" to give you the possibility to NOT USE any Ext partition for data.
I dont like squashedfs, but someone requested an hd build with some free space on nand (about 50mb) because some one not install a lot of apps and prefer to not use sd ext partition.
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
FEATURES
All the main features of RAFDROID HD EXT plus:
- odexed back to save dalvik cache space
- free user space after first boot: 101mb
- App2SD enabled if you use and SD with an EXT partition
CHANGELOG
Code:
3.2.1 - 3 MAR 11
Fixed Market FC
3.2- 3 MAR11
Some improvements and fixes to radio/audio driver,
this "should" fix phone freeze in some setups, also if I was not able to replicate the issues
Tweaked for more battery life on some sd cards usage
Updated hosts file with last one
3.1 - Initial release
=== INSTALL INSTRUCTIONS (CWR) - NEW USERS WITHOUT CWR INSTALLED OR WITH CWR BUT USING ANOTHER ROM ===
This process will erase everything on your nand. So, if you are already using a previous rom, backup everything!
Download PANASONIC SD FORMATTER and use it to format your card with FULL ERASE
You need to flash MAGDLR 1.13
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Download the FULL RAFDROID PACKAGE and copy the entire zip (not extracted!) on the SD CARD root.
Put the SD CARD in your phone and power it on and go in the MAGDLR menu (hold the power key while powering up)
Select BOOT AD RECOVERY
Click on INSTALL ZIP FROM SD CARD and then CHOOSE ZIP FROM SD CARD
Select the FULL_RAFDROID_HD*******.zip that you downloaded before.
Select "Yes - Install........" and wait for installation then Go back with power button and select REBOOT SYSTEM NOW
First boot can take up to 20 minutes. If you are stuck on white screen with HTC logo just wait. If you hear boot sound more than one time, you had a bootlop and something has gone wrong. Delete everything, reformat your SD card, read again the instructions and try again.
When you see the lockscreen, give at least 5 minutes to settle. Then do all your settings and then reboot again
Enjoy.
Remember: if you want to avoid Data Corruption always choose SHUT OFF and not reboot!
=== INSTALL INSTRUCTIONS (CWR) - UPGRADING FROM A PREVIOUS RAFDROID VERSION (2.2 or greater) WITH ALREADY CWR INSTALLED===
Since the data storage method is different, you cannot upgrade from a different RAFDROID HD version. You have to install fresh. Anyway you will keep your data and apps installed.
============ CONFIG.TXT ============Used some ideas and code bits from Dandiest's init script.
You can create a config.txt file on the root of your sdcard to configure some things at boot.
Actually you can configure the following options
gps_zone=[your country]
check http://www.pool.ntp.org/zone/@ for country codes (example: it for italy, us for usa.. and so on...)
ppp_mode=[1 or 0]
1 to enable PPP
0 to enable RMNET.
Default is 0
If wince=1 default ppp_mode will be 1
old_light_driver=[1 or 0]
0 to use the new light driver (working notification leds, button backlight control)
1 to use the old light driver (no notifications leds, buttons will go off after 10 seconds)
default is 0
auto_btn_backlight=[1 or 0]
1 to have the buttons backlight going off/on with the screen
0 to have the buttons backlight going off after 10 seconds from when the last button is pressed
default is 1
this work only if old_light_driver=0
wifi_mac_change=[1 or 0]
1 tells the system that you will need to change the wifi mac address to a custom one
0 tells the system that you will use the wifi mac address based on device hardware
custom_wifi_mac=yy:yy:yy:yy:yy:yy
here you have to write the wifi mac address you want.
This is needed, and will work, only if you specify wifi_mac_change=1
If you not write any mac address here, the default 00:11:22:33:44:55 will be used
Just an example on how a file could look:
Code:
gps_zone=it
ppp_mode=0
old_light_driver=0
auto_btn_backlight=1
The init script will also create an init.log file on your sd card at every boot. This will help you and me with debugging if something not works fine. If you have issues please always post your init.log file when reporting your problem.
============ KERNEL ============
You can refer to my kernel thread for updates, changelog, and comments
http://forum.xda-developers.com/showthread.php?t=940823
============ SQUASHED FILE SYSTEM ============
App, Framework and most of Lib folders, are squashed.
Anyway you can push or delete any file from those folder because any file is simlinked.
Example: if you want to use a different framework-res.apk, you can copy it in the /system/framework folder. At this point the simlink will be removed and your new file will be stored on nand, not in the squashed filesystem. This means that more "new files" you push in the squashed folders, less nand space you will have.
Anyway please note that I left only about 13mb free on "system". This means you will not able to push more then 13mb files. If you like to change a lot of things.. this build and squashfs is not for you.
============ DOWNLOADS ============
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Full Rafdroid HD 3.2 LIGHT SQ
http://hotfile.com/dl/108421743/5bfea5b/full_rafdroid_hd_3r2f1_light_sq.zip.html
MD5: 97018DD4D05FAAFBCC5F9329AEB03F28
SHA1: F6B6D67B90B96E02FCDA70D98836450B6FAE9917
CRC32: 150CCA2B
OLDER VERSIONS:
3.1 : http://www.multiupload.com/X8VBC6WKYV
============ DONATE ============
I made this version just for people that were asking, so if you think this helps you, a small donation for a coffe or a beer, is appreciated. Otherwise a click on the "thanks" button is appreciated too
============ CREDITS AND THANKS ============
Credit to all the people that made all this possible: Cotulla, DFT, darkstone, markinus, danijel, rajko and some one other I'm missing...
Big Thanks to Cass, ocm, darkstone, rajko, crawlingcity, atoore for their help in the last months and to be always available to help
Thanks to all the users who donated and helped me to keep going
Thanks to all the testers and users of my builds that with their reports helped me to solve bugs and issues.
Thanks also to Sergio76, imilka, cmylxgo for the nice talks and knowledge sharing
FAQ
Q: I have low quadrant score
A: This is normal. Nand is slower. Anyway during day usage you shold not notice big difference
Q: I have small freeze when installing apps
A: This happens with all Desire HD builds. I can't do nothing to avoid this
Q: I'm using App2SD but my internal memory keep decreasing at any app installed
A: Go in the application management and move the installed abb back in the phone. Some apps anyway keep some datas in internal mem.
Q: My phone sometimes freeze and I have to reboot.
A: Go in Settings -> Audio -> disable audible touch tones. this will solve the issue in most of the cases.
Q: Can you provide a different link or a mirror different from hotfile?
A: I'm sorry but the answer is "no". I pay hotfile every month and the downloads give me the possibility to pay it. I dont do this for money, but I also dont want to waste my money
Q: During/after boot a window appears with "System process not respoding". What I have to do?
A: This is caused from the new audio driver I used. The new audio driver has better phone stability and no robo voice. You have two choices: 1) Click on "wait" and all will be fine OR 2) download the "old_acdb_file.zip" and flash it via recovery. In this way you will not have the error anymore but you will start having robo voice on first call (you can avoid this disabling audible touch tones) and could happen that your phone freezes when receiving a call. It's your choiche. I preferred the "window error" one because for me is more important to have a working phone than an error window appearing at boot.
Q: I have robo voice when I make a call
A: To avoid this, disable "audible touch tones" from the "settings -> audio" menu. You will have no-more robo voice also if you reboot.
a) During the robo-voice call, enable the speaker, then disable it. You will have no more robo-voice until next reboot.
Q: I have very low audio during calls
A: During the call, enable the speaker, then disable it. You will have loud volume until next reboot.
Q: after boot I see only a white screen with a green htc logo
A: just wait. It can take fro 5 up to 20 minutes depending on your sd card. There are no issue. The build booted fine, it's just copying all the files to SD. This will happen only on first installation.
Q: I'm having high battery drain
A: Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
Q: It's really laggy!!!!
A: as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
Q: I have no GPS or the fix is really slow
A: Firs fixt can take up to 5 minutes. just wait.You can edit the config.txt gps_zone= to your country. See here for the right strings http://www.pool.ntp.org/zone/@ if this not solves, try use QuickGps from the market to download a-gps data.
Q: It not boots
A: partition again and format again your sd card. follow the guide linked in the first post. post your init.log. check that you flashed the custom recovery linked in the instructions.
Q: I have no data/3G/HSDPA
A: probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
Q: How do I remove BOOTSOUND / How do I change bootanim
A: bootsound and bootanim are located in /system/customize/resource
Just delete android_audio.mp3 if you dont want sound
Q: I have wake up lag
A: It's an issue that devs are trying to solve. It's not related to the build itself. In the Q&A Forum there is a thread about this problem.
Q: My screen stays off after call
a) Maybe this can help: http://forum.xda-developers.com/showthread.php?t=946012 ATM very few people have this issue, so I wonder is related to sd card.
Q: My contacts pictures are low res after sync!
A: this is a google problem, read here http://code.google.com/p/android/issues/detail?id=4147
Q: I have random reboots
A: Seems to be related to your phone, read here http://forum.xda-developers.com/showthread.php?t=941845 and here http://forum.xda-developers.com/showthread.php?t=898804
UPDATES:
Instructions:
1. Download your update and copy it to your sd card folder. Dont use MAGDLR mass storage mode because will corrupt your files. Use an sd card reader on your pc or usb mass storage mode in recovery menu
2. Boot into MAGDLR and choose BOOT AD RECOVERY
3. Make a backup! It will save your life if something goes wrong and you want to roll back! You are aware now!
4. Click on INSTALL ZIP FROM SD CARD
5. Click on CHOOSE ZIP FROM SD CARD
6. Select the update zip that you downloaded before
7. Select "Yes - Install........" and wait for installation
8. Go back with power button and select REBOOT SYSTEM NOW
Removed Apps for version 3.X -> http://www.multiupload.com/H5IPNFYBG4
old acdb file (read the faq if you dont know what this is) -> http://www.multiupload.com/AHV0UIKHZF
Stock Framework, only for version 3.X -> http://www.multiupload.com/TVDWWVDNL1
RAFDROID Framework, only for version 3.X -> http://www.multiupload.com/ZC4P6KSKWL
Replacing fonts with standard Desire HD one http://www.multiupload.com/N4VR74W8PK
Replacing fonts with Rafdroid one http://www.multiupload.com/E9UKQBEE4P
If you have issues with flash videos on website, you need an older flash version. Check this post. Thanks to Jayedamina http://forum.xda-developers.com/showpost.php?p=10584806&postcount=280
- maybe I need also this -
First! Nice!
waiting...
are there any advantages on HD2 TMOUS?
rafpigna said:
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
Click to expand...
Click to collapse
I gues not rizky_p
rizky_p said:
are there any advantages on HD2 TMOUS?
Click to expand...
Click to collapse
link is on-line
Thanks, will try
Going to try this tonight, looks good. Any one tried it yet?
Ston said:
Going to try this tonight, looks good. Any one tried it yet?
Click to expand...
Click to collapse
Yep, works a treat
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
I always had problem with data on ext partition due to easy file corruption, so I'm trying this...thanks!
thesniffer said:
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
Click to expand...
Click to collapse
You can use the update zips from my EXT build.
Very nice and smooth build
But one question: Has anyone tried to change the kernel to Rfp 1.6 or 1.5? I just tried and now the phone is stuck at "gogogo" ...
Intersting
rafpigna said:
You can use the update zips from my EXT build.
Click to expand...
Click to collapse
So via CWM Recovery as i supposed.
Thanks again for your kindness and keep up your valuable work
hi raf
i installed this one(only for proof of concept),works great and i think it is a little faster than the "normal" rafroid,i dont have any lag!!! but 101mb.....very poor...
back to rafroid HD "normal" with d2sd..... i love more space!!!
nice & good release
keep up the good work
cheers!
FEATURES
Phone
WiFi
GPS
Data connections (GPRS)
Sensors (not everything is working: accelerometer can work, but compass not)
2D/3D (Samsung not allowed to us to distribute the 2D/3D library binaries, so they are not included in the image)
MP4/3GP movie playback (camera hardware button doesn't work yet)
Camera in photo (up to 5MP) and movie recording mode (it's still not true 480p, but recording works)
_______________________________________________________________________________________________________________________________
CURRENT BETA ON MY OMNIA 2 (GT-i8000)
I tried out with different ADW theme, downloadable from Market.
BLACK GLASS ADW THEME
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EXPRESSO UI THEME
GALA S THEME
PLEASE CLICKSUBMIT TO PORTAL IF YOU THINK THAT MORE PEOPLE DESERVES TO KNOW THIS.
MY OBJECTIVE: TO SPREAD THIS NEWS TO OMNIA 2 USERS ALL ACROSS THE WEB.
MOD FILES
___________________________________________________________________
2D/3D Libraries Files By official dev member
1. Download here
2. Make sure that it was renamed to o2b3update.tar.gz
3. Place it under root of My Storage before run haret.exe for the first time.
___________________________________________________________________
2D/3D Libraries Updates + Market Fix + SD Card Fix By mihai_mihai
**FOR OFFICIAL BETA**
Download here
Placed at root of My Storage
**FOR ISO**
You guys can apply this update manually
Extract out all the files from o2b3update.tar.gz and transfer them to Storage Card.
Replaced the original files in Android using Root Explorer
___________________________________________________________________
WORKING LIVEWALLPAPER PATCHES(Only Google Live Map) By sgoo
Download here:http://www.modaco.com/index.php?act=attach&type=post&id=71920
FOR MORE LIVEWALLPAPER, CHECK HERE, NOT GUARANTEE WORKABLE ON FROYO BETA.
**FOR OFFICIAL BETA**
Download one of the files above.
Extract the file from .7z to o2b3update.tar.gz
Placed them in root of My Storage.
Launch haret.exe
**FOR ISO**
Download this View attachment system.rar
Unrar them and placed them on Storage Card
Bootup Android
Copy over and replace the original file in /system using Root Explorer
___________________________________________________________________
INSTALLATION TUTORIALS
FROYO BETA 1 OFFICIAL INSTALLATION GUIDE By l3ong91, XDA
1. Clean out SD card using Settings> Memory Settings> Storage Card > Format in WinMo mode.
2. Download Froyo Beta 1 here.
3. After finish, unrar it.
4. Download 2D/3D libraries files.
5. Make sure that it was renamed to o2b3update.tar.gz
6. Placed the o2beta folder, ext4.tar.gz, haret.exe, startup.txt, zImage and o2b3update.tar.gz in root of My Storage.
7. Run haret.exe from My Storage> o2beta folder.
8. After auto-reboot back to Win Mo, start haret.exe from root of My Storage.
*It will freeze at the Android bootup screen for a moment...please be patient.
*Some keymapping has changed:
Lock/ Turn off Android ------> Changed to Call End button
Back/ Return key------------> Changed to the default Lock key
Home Key ------------------> Set to the Back button (above Camera button)
*Camera is working now
*For those who have problems, try to download the updated 2D/3D library files by mihai_mihai.
___________________________________________________________________
ISO MY STORAGE INSTALLATION (No Ubuntu) By Quato7906, MoDaCo
For all who are tired of using Ubuntu,to make My Storage installation,do this:
1.First download this and unrar it to the root of My Storage as is.
http://www.megaupload.com/?d=LMDVA130
2.make sure you have at least 1,2 GB free space on My Storage and copy the file fs.iso from here to the \iso folder.
http://www.megaupload.com/?d=5LAOKBYI
3.start haret.exe from the root of My Storage & enjoy the new Froyo.
* The 3d drivers are inside,also calllight and task manager.iso file is 1,1 GB now.
* For more apk installation space ,also trick: when you istall some apk's ,just copy the fs.iso file to your hard drive to have a backup if anything goes wrong,just copy the file back to iso folder .
* There is a new update, which fixes the Market problem, download here. Unrar,rename to fs.iso ,copy to \My Storage\iso and run haret.
___________________________________________________________________
FROYO BETA 1 MANUAL INSTALLATION (UBUNTU REQUIRED) By l3ong91
1. Clean all the partition on My Storage, left only with one PRIMARY, FAT 32 partition using Mini Tool Partition Wizard.
2. Format Storage Card using SD Formatter.
3. Copy the beta files and o2b3update.tar.gz(official) to My Storage.
3. Bootup Ubuntu, and copy o2b3update.tar.gz and ext4.tar.gz to desktop.
4. Download gParted and run it, go to Places -> unmount My Storage.
5. Start gParted, top right corner switch to My Storage (May have different label).
6. Create a new EXT 4 Partition, label as 'android', set as Primary Partition. (around 1 - 2GB will be good)
7. Then you will see 2 external drive on Ubuntu desktop.
8. Go to Places -> Mount both of them.
9. Then start Terminal from Applications and do all the commands below step by step.
Type in cd/ Desktop
Insert your password, then click Enter.
It will appears as (username) - desktop: ~/Desktop
Then, type in ''sudo tar zxvf ext4.tar.gz -C /media/android''
A list of files will be shown and copy over to the android partition.
Wait for the process to complete and type in below after return to ''(username) - desktop: ~/Desktop
''sudo tar zxvf o2b3update.tar.gz -C /media/android"
Last step, change the startup.txt found on another My Storage partition, rename the following line:
" Set CMDLINE "rootdelay=2 root= /dev/mmcblk0p6 init=/init" to the partition number that you created, eg. mmcblk0p2.*
You should be able to bootup Android after that.
*Some device may get different number, you can look for the Android partition number through booting up the device without changing anything in startup.txt, then at this screen, check the one which has the actual partition from what you created, below is an example from jerrytech2468.blogspot.com:
___________________________________________________________________
FROYO BETA MANUAL INSTALLATION (UBUNTU REQUIRED) By jerrytech [VIDEO]
Link here
___________________________________________________________________
TROUBLESHOOTING
Below are common problems faced, the workaround or solution suggested here might not guarantee workable for you, just give it a try.
___________________________________________________________________
MARKET PROBLEM
METHOD 1
Settings -> Applications -> Manage Applications -> All
Download Manager -> "Force Stop" and "Clear Data"
Market -> "Force Stop" and "Clear Data"
Talk -> "Force Stop" and "Clear Data"
Restart Android
METHOD 2
Call *#*#4636#*#*
Phone Information -> Toggle DNS check to allowed
METHOD 3 (FOR OFFICIAL BETA)
Download this file
Placed at root of My Storage
METHOD 4 (FOR QUATO's ISO)
http://www.mediafire.com/file/1z091asou2f7oq7/froyo-fs.7z.001
http://www.mediafire.com/file/sx551uj8ajamrx7/froyo-fs.7z.002
http://www.mediafire.com/file/97x1y4pgrlc8fp5/froyo-fs.7z.003
Renamed to fs.iso
Replaced the old fs.iso in My Storage/iso folder
___________________________________________________________________
GOOGLE SIGN-IN AUTHENTICATION
METHOD 1 3G CONNECTION
Clean install
First boot, log in Google Account after welcome screen
Market ->Download
METHOD 2 YOUTUBE APPS
Run YouTube from Menu
My Account -> Sign in using Google Account
___________________________________________________________________
SD CARD UNMOUNTED
METHOD 1 SD FORMAT
Reformat SD Card using SD Formatter
Select ON for Format Size Adjustment
METHOD 2 REPLACE FILES IN FROYO
Download this files and extract it.
There are 2 modified files inside: init.rc, vold.fstab
Replace these files in Android system using Root Explorer
- /init.rc
- /etc/vold.fstab
___________________________________________________________________
GAMES/APPS INSTALLATION PROBLEM
METHOD 1
Unmount sd card (in setup/sdcard & phone storage)
Install apps (eg angry birds)
Re-mount sd card
___________________________________________________________________
INCORRECT TIME IN NOTIFICATION BAR
METHOD 1
Manually change the date to one day forward, or
Tick on show in 12/24 hours system manually
METHOD 2 BY Quato7906, MoDaCo
1.Put the time Region in Windows Mobile to London GMT;
2.Set your time in Windows ;
3.Run Android and set your time,you will notice thet time works correctly then
Also I notice that after doing this GTalk detects correct time settings and logs in,and therefore MARKET Also works always,downloads & installs apps!!!.
METHOD 3 DOWNLOAD CLOCKSYNC
1. Download the file or download the ClockSync through Market.
___________________________________________________________________
ANY WORKAROUND APPLICABLE TO YOU GUYS CAN BE SUGGESTED AS WELL IN ORDER TO HELP OUR FRIENDS WHO CAN'T GET THEIR FROYO WORKING.
___________________________________________________________________
LATEST NEWS & UPDATES
2011-04-18
Froyo beta1. It's SD card installer (1024mb only). It includes latest kernel, modules, default filesystem is ext4, new keymapping. Download it here (it will wipe Your current installation and/or whole SD card content). As always it doesn't contain 2D/3D libraries from Samsung (You have to find them and put it before first boot to My Storage as o2b3update.tar.gz).
Froyo beta1 working things are:
Phone
WiFi
GPS
Data connections (GPRS)
Sensors (not everything is working: accelerometer can work, but compass not)
2D/3D (Samsung not allowed to us to distribute the 2D/3D library binaries, so they are not included in the image).
MP4/3GP movie play (camera hardware button doesn't work yet)
Camera in photo (up to 5MP) and movie recording mode (it's still not 480p, but works)
Note: There is still error, when within telephone conversation in approx.30 seconds the LCD blanks but also the sound muted - UNTIL NOT SOLVE, please use the Call Light or KeepScreen application from Market!!!
Note2: If You have problems with registering via Google use following workaround: open Youtube app and login there with google account.
Note3: Changed button mapping: Cube -> Menu, Lock -> Back, Back key -> Home, Hang-up -> Sleep/Hang-up/Wake, Camera -> not used.
Note4: Updates have now prefix o2b3update.{tar.gz|sh}.
Thanks, I will test today
woohoo. finally!! hopefully battery life has been improved dramatically. cant wait!!...download speed is a bit slow though.
vpnair said:
woohoo. finally!! hopefully battery life has been improved dramatically. cant wait!!...download speed is a bit slow though.
Click to expand...
Click to collapse
The Froyo is awesome and I think the battery consumption has reduced and better now.
Is adobe flash works?
Any screenshot guys?
Sent from my Nexus One using Tapatalk
Works like a charm.
Just re-partitioning of my SD-Card was a bit tricky: The old Eclair-Beta-Partition was slightly smaller than the new one for Froyo. So the installation (haret within the o2beta-directory) always claimed that the SD-Card is too small (in fact mine is 2 GB). So I had to delete the old partitions and re-format it within the configuration-menu of WinMo.
If s.o. does not have a card-reader/adaptor for the microSD - just use this software linked in this post.
hey can someone upload the 3D drivers to mediafire. im having problem download it from filesonic
Looking forward to testing out FROYO. Taking a while to download as I guess a lot of people have been eagerley awaiting it!
Could someone please upload a screen shot?
soroush0313 said:
Could someone please upload a screen shot?
Click to expand...
Click to collapse
I'm trying to download apps from Market to for screen capturing software...be patient.
Instead of asking ppl to post the screenshot, why not you just try it out on your phone?
I want to but I can't download. Download link not responding.
Thanks a lot l3ong91 for your efforts, Any other hints to run android smoother and better would be appreciated. I'm completely newbie about running android in the best way to have the best results.
Again Thanks a lot, you are really great man.
soroush0313 said:
I want to but I can't download. Download link not responding.
Thanks a lot l3ong91 for your efforts, Any other hints to run android smoother and better would be appreciated. I'm completely newbie about running android in the best way to have the best results.
Again Thanks a lot, you are really great man.
Click to expand...
Click to collapse
If you want to try out stable Android that can be used on daily basis, for
**Android Eclair (2.1) on Omnia 2, see my previous thread, follow and download the links under UNOFFICIAL RELEASE.
**Android Froyo (2.2) on Omnia 2, follow my guides on this thread, the overall impression is smoother and better than the previous release.
If you follow every step by step, you should be able to run Android on your Omnia 2.
Thank you!
Followed your instructions and..... Froyo lives!
Be sure to stress enough that new 2D/3D drivers are needed in order for Froyo to work properly. Only thing, Froyo keep saying that the SD card is damaged, when, of course, is working properly. Someone else with the same issue?
tiberiusmusicus said:
Followed your instructions and..... Froyo lives!
Be sure to stress enough that new 2D/3D drivers are needed in order for Froyo to work properly. Only thing, Froyo keep saying that the SD card is damaged, when, of course, is working properly. Someone else with the same issue?
Click to expand...
Click to collapse
I don't have SD damaged problem, I can access SD card in Android, but when switch back to Win Mo, the SD card directory was missing.
Guys, please try to check if you guys have this problem with the Froyo beta.
ashburn said:
hey can someone upload the 3D drivers to mediafire. im having problem download it from filesonic
Click to expand...
Click to collapse
For those who have problems with FileSonic, this is the 2D/3D files which i upload personally in .7z format.
You'll have to extract it out from .7z format first before you put into My Storage.
I've done what you said step by step but when android booted completely, in the welcome screen every time i clicked on android there is no response and suddenly the screen went black, I've tried to turn it on with keys but no response. What Should I DO?
Thanks
It works! Great work!
i have same problem as tiberiusmusicus. SD card is 'damaged'. however i can access it in winmo. it might be because the directory for the sd card is /mnt/sdcard and not /sdcard. im not sure....any solution? cant take photos because camera is not reading sdcard.
thank you so much to dev and TS for this froyo. i want to post ss on benchmark but cannot bcause still new in this forum and dont have enough post
try to put some live wallpaper. got i problem tht i have...trying camera with setting no flash...it work but only at first time...after tht it still give flash eventhough i select auto n select again off
benchmark
total : 495
cpu : 980
memory : 320
I/O : 994
2d : 117
3d : 83
hurmm...install shake them all n cannot find to set live wallpaper
UPDATED June 25, 2011
Bumblebee ROM 2.4
What's New
------ 6/25/2011 ------
Kernel source: bumblebee-kernel-r26-source.tgz
Code:
MD5 (bumblebee-kernel-r26-source.tgz) = 6fe10367094a0c609b76bc1694d3583a
------ 6/11/2011 ------
To upgrade from Bumblebee 2.3, wipe cache (and only cache) in recovery, then install the Bumblebee 2.4 zip (the install zip tries to wipe cache, but it is not always successful due to limitations in recovery, so it's best to manually wipe cache first then install). See below for more info if installing for the first time or coming from another ROM.
Kernel updates: accelerometer improvements (makes games using it more responsive), swap support, minor tweaks here and there. This is not the major new kernel which I've mentioned that I'm working on. That will be released when it's ready and completely stable, hopefully in a week or so (crossing fingers, but no guarantees).
ROM updates: Newly released update to Superuser (also with fixed signing key so it's upgradable via Market), No Frills CPU Control as a core app, updated core apps and system libraries.
------ 5/23/2011 ------
NOTE: Due to core changes in the system, I recommend a wipe for this update. A pain, I know; sorry about that. If you want to go a little crazy, you can try just wiping cache and dalvik-cache (first boot will still take a few minutes even with this shortcut). However, because the signing has changed on a few system apps, I cannot guarantee that this shortcut will work as the new keys may conflict with keys already stored in /data from a previous install. As always, if you have any issues, do a wipe. So, with that out of the way, on to what's new!
Shiny new Android boot animation (see below for an animated pic). Boot-up takes a few seconds longer, but it's so purdy you won't mind.
New built-in apps: GScript, Terminal emulator, and Text Editor.
Built-in settings updated to include Wifi AP Hotspot. Tether app, which was used to access the Hotspot settings before, is still installed as an easy way to create a desktop shortcut.
"ls" colors are now off by default, due to the Windows cmd.exe not being able to handle ANSI color codes properly when using adb. If you're on Linux, Mac, or another *nix environment, you can use the "lscolors" command to turn them on (it's sticky, you only need to do it once). In an adb shell, type "lscolors on" or "lscolors off" to turn them on or off permanently. You can also do this in the Terminal app on the phone, just be sure to "su" first.
Fixed a signing issue with some pre-installed upgradable apps (like Google Search and Voice Search) that made them non-upgradable. There should be no more issues with this now.
Updated ad-blocking /etc/hosts, and added a fix to the file for certain apps (like sl4a) that try to resolve localhost.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot Animation
Class 2 sdcard read speed increase
<-before ... after ->
Class 4 sdcard read speed increase
<-before ... after ->
Recommended install order:
Backup current apps and their data with Titanium Backup (available in the Market).
Do a nandroid backup in recovery before doing anything else below.
Required if installing BB 2.x for the first time: Wipe. Wipe it all. Data, cache, system, dalvik-cache, sd-ext if you've got it (might need to look under Advanced or Mounts in recovery to do the last two, and while you're there format /system). If upgrading from BB 2.3, wipe cache (and only cache) in recovery.
If not upgrading from 2.3, install Wiper zip (see below), just to be extra sure that all is wiped. Don't reboot yet.
Install ROM zip (see below).
Optional. If you need the non-overclocked kernel (see below), install it now before rebooting.
Boot into the ROM. w00t!
Download any desired gapps from the Market (Gmail, Maps, Street View, YouTube).
Restore apps with Titanium Backup (not necessary if upgrading, all apps should remain). Do not restore system settings, wifi settings, or anything else except user-installed apps and their data. If you have any issues after restoring apps, launchers and possibly other root or system-related apps may need to be uninstalled and re-installed.
ROM: update_bb_rom_2.4.zip
Code:
MD5 (update_bb_rom_2.4.zip) = b92900a5a095f41702ec2905e9453039
Wiper: update_wiper_1.3.zip
Code:
MD5 (update_wiper_1.3.zip) = 9a72c3b3d108eb8f033637d7b51af027
Recovery: xionia_cwma_12518.4_virgin.zip
Code:
MD5 (xionia_cwma_12518.4_virgin.zip) = 12481185d4234fe4b0af9d8265e86fb0
Kernel-only. Included in ROM. Linked here for the curious. Not guaranteed to work on any other ROM. Contains the two init.d scripts to enable dalvik-cache to /cache and the sdcard speed tweak.
Overclocked kernel:
update_bb_oc_kernel_1.26.zip
Code:
MD5 (update_bb_oc_kernel_1.26.zip) = 746453ee4e91ee1cac43d5429d62a460
Non-overclocked (by default) kernel, for those whose phones can't handle the default overclocking. Can still be overclocked with SetCPU to find the best setting.
update_bb_no-oc_kernel_1.26.zip
Code:
MD5 (update_bb_no-oc_kernel_1.26.zip) = 91251b7dd57c4bba57092642774b3437
I had an idea a little different than just putting up a "donate" button. I also happen to be a composer/pianist. So if you like neo-classical new age, instead of "buying me a beer" with a small donation, why not purchase a couple of tracks from my album Deep Blue Goodbye on Amazon or iTunes, and get something in return that might even last longer than your phone.
-------------------------------------------------
The Bumblebee ROM
-------------------------------------------------
Includes the Bumblebee Kernel (see below). Overclocked to 768 by default with the interactive governor (480 min, 768 max). No need for SetCPU or No Frills CPU Control, but you can use them to overclock even higher and/or set a different governor and range. If you get reboots, back off on the CPU settings, or install the non-overclocked kernel (see above) and gradually increase speed.
Froyo 2.2.1 with lots of tweaks.
TWS 50% bug fixed in Android Framework. This is not an "Airplane Mode Toggle" hack, this is the real deal -- a bug fix in the Android Froyo source. This also fixes the issue where 3G data connection would get stuck after making or receiving a call.
Sdcard Speed Tweak, increases sdcard read speeds by 20% or more.
Dalvik-cache to /cache for 170MB+ free internal memory after a clean install.
Reboot and Recovery options in power button dialog.
"Factory Data Reset" is removed from Settings (it's probably still accessible through an Anycut shortcut if you look for it, but if you're dumb enough to create a shortcut to that, I can't help you. ). Hopefully no more bricks from trying to wipe via the phone Settings. The factory reset was the only option under "Privacy", so you will no longer see "Privacy" on the main Settings screen.
Wifi AP Hotspot settings are available through the main settings screen under Wireless settings. It is fully functional, infrastructure mode. "Tether" app is included to create an easy desktop shortcut.
Extra-purdy boot animation.
AppWidgetPicker included to make choosing widgets easier by grouping them together in the selection menu. Similar to CM-style widget choice.
All Apps and Frameworks deodexed
These Google apps are removed because they are available on the Market: Gmail, Maps, Street View, and YouTube.
GScript, Terminal emulator, and Text Editor included.
Activate app is here, but all other bloatware apps are gone. The Activate app is included to help reset data connection problems for some people with wonky radios. It also happens to be handy for situations where your account lapses or gets canceled and you actually need to re-activate the phone.
Note: When doing a full-wipe install, the Activate app will appear by default on the desktop. If your phone is currently activated with Virgin Mobile, the app will automatically be removed after a second or two. If your phone isn't activated, it will stay until you remove it from the desktop yourself or until your phone is activated.
Removed to save space: Non-english language TTS files; long music ringtones and music alarms (notifications and short alarms are not removed); some internal LG diagnostic sound files. The removed larger-sized ringtones are here. You can put these on the sdcard to save system space. Unzip and install with "adb push media /sdcard/". (TIP: put any ringtones you download into the /sdcard/media/audio/ringtones folder to save memory.)
SuperUser pre-installed (be sure to check the Market for any updates)
Latest versions of TalkBack, KickBack, and SoundBack. TalkBack is available as a keyboard input method. Activate Accessibility->TalkBack, long-press in a text area, select TalkBack. Do the tutorial, it's pretty cool.)
toolbox and busybox (1.18.4)
etc/hosts from mvps.org for free generalized adblocking. This doesn't block admob or apps that use custom adds. Some in-app ads are blocked, e.g. the top banner ads in WeatherBug and a few others, including ads in some games. Most website ads are blocked. YMMV.
init.d support in kernel. Included are two init.d scripts to move dalvik-cache to /cache and an sdcard speed tweak, mentioned above.
e2fsprogs and libs for creatings, checking, and resizing ext2/3/4 partitions. ext2/3/4 support is compiled into the kernel, but these binaries are useful in init.d scripts.
Installing
Don't do a factory data reset from within the phone settings menu. This has caused all kinds of problems with every ROM out there, although it may be related to the recovery you're using. Better to be safe and just don't do it that way. It's been removed from Bumblebee, but it's probably still there in your current ROM. Stay away.
If coming from another ROM, I always recommend a complete wipe. In recovery, wipe data and cache. Then, under "mounts and storage" or "advanced" (depending on your recovery), format boot, system, data, and cache, and wipe Dalvik-Cache if you have that option as well. Lastly, use the Wiper update zip above, which includes it own wipe functionality to be extra wipy. Then install the ROM.
Recommended recovery
I use the Xionia CWMA 1.2518.4 Virgin recovery (note: this is a direct download to the recovery, with flash_image and a short how-to, because the original download in the forums was not working). I find it works fairly well, even though it suffers from incomplete wipes sometimes (they all do). I can't answer questions about installing Bumblebee with other recoveries, so if you have problems, first change to the Xionia CWMA .4 Virgin recovery and try again. (Note: the Xionia 1.2518.6 CWMA recovery in the Optimus S forums is not compiled for the V, only the one linked above is. Some people find .6 works, some don't. I can only say that .4_virgin works for me and .6 didn't.) I also plan on releasing my own recovery with the Bumblebee kernel soon, so stay tuned.
Wiper update zip
This update zip does a full wipe. (Well, technically, it doesn't wipe the sdcard, just /sdcard/.android_secure, and it only cleans up the sd-ext, if you've got one, without formatting it. But just about everything else is wiped pretty good.)
Download the "wiper" update zip listed at the top of the post, and flash with recovery.
Bumblebee ROM update zip
If you don't do a wipe and you have any issues, force closes, etc, do a wipe (again, not a reset from the phone settings menu) and re-install before you report the issue here. Or try the Wiper zip above then re-install.
Download the ROM update zip listed at the top of the post, and flash with recovery.
-------------------------------------------------
The Bumblebee kernel
-------------------------------------------------
Compiled from the official bug-fixed LGVM670_02 source with the following patches and modules:
init.d support. Init scripts should be placed in /system/etc/init.d and are executed in order (convention is to begin the script filename with a 2-digit number so they are executed in numerical order). Note that /sdcard is mounted by the Android init system after the rest of the system has loaded, so init scripts should not attempt to access /sdcard unless mounting it is included in the script.
If you install Link2SD and have created the /system/etc/init.d directory, that app will create a script named 11link2sd to mount the ext2/3 partition. If you don't have an init.d directory, Link2SD will create /system/etc/install-recovery.sh as a place to put it's mount code (not to worry, the install-recovery.sh file doesn't exist in Bumblebee, so it will be empty except for the Link2SD code).
Regardless of the method, if you use Link2SD and you find that it's not working, it may be because Link2SD didn't set permissions properly on the file it created. To fix this, "adb remount", then "adb shell chmod +x /system/etc/init.d/11link2sd" (or /system/etc/install-recovery.sh).
Built-in AP Hotspot enabled
Compiled-in support for ext2/3/4. e2fs binaries and libs included.
Networking modules: tcp congestion avoidance (bic, h-tcp, westwood) and tunneling (ipip and gre)
CPU governors: interactive, conservative, ondemand, userspace, powersave, and performance. Info on most of these is here: SetCPU Documentation
The interactive governor is newer than the SetCPU docs. It is a dynamic governor that scales (if needed) when coming out of idle, instead of polling.
Overclocked. Default on boot is 480-768/interactive, but this can be changed with SetCPU, or the built-in No Fills CPU Control, to any value (valid range is 122-864). Get SetCPU from the market (donate version), or see this thread to download it free for XDA forum members (posted by the dev):
SetCPU for Root Users
Stability at the high-end values depends entirely on individual batches of CPUs. A stable max value for the V can be anywhere from 787 to 824 or higher, it just depends on the unique qualities of the batch your individual CPU came from.
My personal settings are 600-806/interactive and I get great battery life. With the screen off and 3G/wifi set to always be on, I see about 1% drain per hour. There's lots of discussion on the V and S subforums about CPU frequencies and battery life and optimal settings; feel free to browse them for all the interesting findings and info.
What Works
Everything.
Installing
NOTE: If you are installing the ROM, you don't need to download the kernel, it's included. The kernel is here as a separate download for those wishing to just use the kernel with their current ROM.
Download the kernel update zip listed at the top of the post, copy it to your sdcard, and flash with recovery (you can rename it update.zip if your recovery doesn't give you the option of selecting a zip to install).
If you're using a Virgin-based rom, you should generally be fine. If the ROM has replaced any of stock Virgin dynamic-link (*.so) library system files to play happy with their kernel, there may be issues, but that's almost impossible to predict. There are a bunch of those *.so lib files, so to install them all really requires installing a new ROM (like Bumblebee), not just a kernel. However, I've included most of everything that is required for all the hardware to work properly on boot, and if your ROM is mostly stock (e.g. Xionia_VM, Aphrodite, RomidusROM) there shouldn't be any noticeable problems. If the ROM you use has a kernel-less update after you've installed this kernel, you may need to re-install the kernel if any issues crop up.
As-is, the kernel will not work with CM7. I have a kernel install zip that does work, but only 98% (some sensors work, some don't), so I'll release it when it all works 100%.
Note on Key Mapping
Most kernels in the past for the V have been built from the Optimus S source, which reverses the Home and Menu keys due to slight hardware differences. Many of these kernels, and ROMS that use them, have altered the key layout system file to reverse those two keys. The Bumblebee kernel, coming from official source for the Optimus V, has the buttons mapped correctly already. As part of the installation process, it overwrites the existing key layout file with the original key maps, so that people coming from kernels and ROMS that swapped the keys won't find themselves with the keys reversed again. If you use Button Remapper or a similar app to set up other custom key maps, you will need to re-map those keys after installation.
-------------------------------------------------
Themes
I don't believe in ROM themes, so you won't find any here. You can do just about any customization you want with the various launcher replacement apps available in the Market (I'm partial to GO Launcher EX, myself).
Stay tuned for Kernel and ROM updates!
Wonderful!
Sent from my VM670 using Tapatalk
Excellent work. Any plans to put your config and kernel on github? Would be nice to integrate some cyanogenmod settings from CM6 into this!
Sent from my VM670 using XDA Premium App
dammitman said:
Excellent work. Any plans to put your config and kernel on github? Would be nice to integrate some cyanogenmod settings from CM6 into this!
Sent from my VM670 using XDA Premium App
Click to expand...
Click to collapse
I have been thinking about it. My current plans are to try and integrate the latest kernel from the aosp (the VM670 kernel source is 2.6.32.9, the most recent branch in aosp is 2.6.35.7). When I do that, I will put everything up on github.
Excellent description of the build! Thank you very much for very nice work
Can I flash from out-of-the-box-stock? Rooted of course...
Anyone got a black bar ready for this ROM?
slow88lx said:
Can I flash from out-of-the-box-stock? Rooted of course...
Click to expand...
Click to collapse
Yep, you sure can, assuming you have a recovery installed. See the first post for a recommended recovery. For your first flash, I would do the "full-wipe" install, since it will remove the bloatware on your phone. After that you can do the "no wipe" installs to upgrade with new versions.
ok noob here, I followed instructions to the letter and my "v" gets stuck and the droid boot screen...... Any thoughts ? Has that happened to anyone else ?
Can you please use mediafire for files?
It doesn't have the annoying timer.
gringo8831 said:
ok noob here, I followed instructions to the letter and my "v" gets stuck and the droid boot screen...... Any thoughts ? Has that happened to anyone else ?
Click to expand...
Click to collapse
Did you wipe? Which recovery are you using? Did you try the "full wipe" install zip? Were you coming from another ROM, or were you just stock-rooted?
Give me some more info and I can help you figure it out.
ok scratch my last post. I figured it out. Didnt do the delvik wipe and that solved my issue. Hey thanks for for this ROM. Most of the others that are out have problems with the mms not being able to send pix.
How does this compare to CM7 for battery life, speed, and features?
Sent from my LG Optimus V
DustbinK said:
How does this compare to CM7 for battery life, speed, and features?
Sent from my LG Optimus V
Click to expand...
Click to collapse
Battery life is much better. I get less than 1% drain per hour with wifi always on (even when the screen is off) and between 1%-2% per hour with 3G, data and sync always enabled. With normal use, I get a good 18 hours battery life, including phone calls, texts, browsing, videos, etc. With light use, I get over 24 hours. With CM7 I get around 5%-6% drain per hour in complete idle. I got about 10-12 hours with normal use before needing a charge.
Speed is better as well, but this is getting more subjective. The Bumblebee kernel is overclocked out of the box, so that does help. And don't believe the Quadrant scores, they are not accurate at all for CM7 (inflated almost double, sometimes more). There's a thread somewhere about it. Try both ROMS, see which one feels snappier.
As for features, well CM7 is tweaked Gingerbread, and Bumblebee is (mostly) stock Froyo. Also, CM7 has some things like notification-bar power controls that even stock Gingerbread doesn't have. However, bluetooth doesn't work with CM7 for the V, which has always been a deal-breaker for me. If bluetooth is not a big deal, and you can live with the shorter battery life, there's no reason not to use CM7, it's very nice apart from those 2 issues.
Can I use this Kernel with asops? I just installed 2.3.3 with the gApps, and then did the OC Kernel but it wouldn't boot at all. Just hung on the LG logo.
I reflashed again using asops and it is working again, would really like to get this thing OCed though. Any help?
nootered said:
Can I use this Kernel with asops? I just installed 2.3.3 with the gApps, and then did the OC Kernel but it wouldn't boot at all. Just hung on the LG logo.
I reflashed again using asops and it is working again, would really like to get this thing OCed though. Any help?
Click to expand...
Click to collapse
No, the kernel install zip is only for Froyo-based ROMs. I do have a testing kernel install that works 99% with aospCMod, but sensors don't work. It sure feels snappier than the default aospCMod kernel, and I'd love to get it working 100%. If I can figure out the problem with the sensors (and it's not just the sensors.thunderc.so file, or any other .so file as far as I can tell) then I'll post it as an alternative kernel for aospCMod.
Something that is odd, I had your ROM installed with your Kernel as well, and then I installed asops ROM and gApps ROMs. But the OC is still there, and it works perfectly. I have it running at 245-806MHz.
am I able to have conversations with wired headphones, or does this have the same problem as CM7 and it treats ANYTHING in the headphone jack as handsfree
rubyiris said:
am I able to have conversations with wired headphones, or does this have the same problem as CM7 and it treats ANYTHING in the headphone jack as handsfree
Click to expand...
Click to collapse
Wired headphones (and BT) work fine, it does not have the same problems as CM7.
hmm might have to give this rom a try for a while. Not gonna lie I greatly prefer cm7 but I think it needs a lot more polish before it can become my everyday rom (using it right now but it leaves much to be desired).
obijohn said:
...And don't believe the Quadrant scores, they are not accurate at all for CM7 (inflated almost double, sometimes more)...
Click to expand...
Click to collapse
Couldn't agree with you more about Quad scores. It's just a number. I ran a some quads the other day with aospCMod. I was getting an average of about 1100, but I had one that came up 4000+. I know my phone isn't that fast when EVO Shift clocked at 1.8Ghz is getting 3300 on the average. Don't take quad scores as an indicator of speed. If the phone feels fast and is reponsive then that should be good enough. Judge the speed by how it feels, not the score some benchmark gives.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is CandySiX. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM. We aim to add more features as this project progresses.
Check us out on the web @The-Candy-Shop
@matthew0776 @mar5hal @gimmeitorilltell @Cuzz1369 @rc420head @Flashalot @Venomtester @Darknites @javelinanddart @calebcabob @NoSpamDan
ROM
DEVICES/KERNELS
Disclaimer: We here at The CandyShop are not responsible for any bricks you may obtain. Please follow the thread rules and steps and everything will be gravy. Remember, backing up before flashing is always recommended.
FEATURES
Choose from CMTE or OMS (RRO Layers is DEPRECATED)
Battery bar
LCD density options
Multi-window
Status bar customization
Quick setting customization
Quick setting pull down options
Force expand notifications
Time contextual headers in panel
Dark UI switch
Advanced power menu
Extra IME options
In-Call vibration options
Lockscreen customizations:
-Shortcuts
-Music visualizer
-WeatherAnimations:
-Power menu
-List view
-System
-ToastNavbar customization (CMTE only):
-SmartBar
-Fling
-Pulse Hardware Buttons settings:
-Slim Hardware key rebinding
-Long-press/double-tap actions
-Volume rockerOn the Go mode
Screenshot Crop & Share
Fully charged notification and toggle
CPU info overlay (Developer options)
Snap camera (Sultan's)
More to come, we are never done...
CHANGELOG
WARNING!
This is a Virtually Repartitioned ROM!
What this means is that you will need to take some special steps to flash this ROM. Don't worry, it's not that hard, and you will be able to return to stock with Odin at any time. The cool thing is that it will support a ton of app and app data storage and will behave like a more modern device.
The basic idea with virtual repartitioning is that the partitions are renumbered from the stock numbering, but not resized. So the most important parts of this are (as an FYI, you don't need to know this ):
-The 2GB /data partition becomes a most adequate 2GB /system partition for the ROM and GApps.
-The 12GB Internal SD partition becomes /data, so you have that space to install apps.
It is strongly recommended to use an External SD card to store the ROM/flashing files and for backups, etc., however it is not mandatory. If you do not have an External SD and you need to format the /data and /Internal storage partitions, you will have to copy the files you need from your PC again. Easy peasy, right?
FAQ/NOTES:
When formatting the device, first go to the Mount menu and make sure none of the partitions you want to format are mounted. If they are, formatting will fail.
Make sure you have NOT selected Mount USB Storage, and that the MTP button says "Enable MTP", which means it is DISABLED. If either of these are enabled, then formatting may fail.
The /system partition is formatted as EXT4.
The /data and /cache partitions can be formatted as either EXT4 or F2FS.
The Internal Storage should be formatted as EXT4 or F2FS.
The External SD card (if you have one) would be best formatted as FAT, which you can do in your computer. When the ROM boots, it will detect the card and offer you one of two different ways to use it, as "Internal storage" that will only work with your device for security (requires formatting and encryption by Android), or as "Portable storage" that will work in other devices.
CAUTION: With Internal, you will have to entirely format your card if you have issues and it can not be used in ANY other device. In fact, it will become invisible in file managers because it becomes an extension to the Internal SD card storage. Format the ExternalSD card to Internal Format at your own risk.
When formatting /data, the default behavior is that /data/media is not deleted. In order to wipe /data/media, you need to either go to TWRP > Wipe > Advanced wipe > Format data, or delete the folder manually through the file manager in TWRP.
TWRP > Wipe > Advanced wipe > Format data is also needed if you plan to use device encryption, because this step allows for a space at the end of /data to contain the encryption information. Without this, encryption will fail!
IMPORTANT: If you have flashed a modified PIT file, flash back the STOCK PIT. You can also return to stock by using Odin and a Factory Image.
If you are trying to get back to the stock partitioning:
Flash a stock TWRP recovery ZIP or IMG file, or use Odin to push a TAR recovery over. After doing this you need to reboot your device into Recovery to load up the newly flashed version, and format each of the partitions to their defaults (ext4, for the most part). If you encounter errors formatting, reboot back into Recovery and try again.
Check SamMobile.com for stock ROM packages. (There is a Stock ROM version in my AFH account which should be used for recovery purposes only.) Odin should also find the device if it's in download mode and you can flash a stock ROM back on it if you want.
If you are not sure you used the correct recovery or you just want to check the partition structure (I may ask for this), you can run each of these commands from an adb prompt, and save the output to a file for linking in the thread for help/analysis:
blkid
cat /proc/mounts
df
INSTALLATION STEPS:
Here is what you need to do; please follow the below steps carefully!
Connect your device to your computer and FULLY BACK UP YOUR FILES from both your Internal and External Storage!
While you are backing up your files, download the following files to your computer:
A custom TWRP recovery for virtually partitioned ROMs (see Post 2).
The ROM zip file (see Post 2).
A 6.0 Gapps package, pico recommended for now. (optional - see Post 2).
Copy all of these files to your device's External SD card. If you don't have an External SD card, then you will need to copy them over from your computer after formatting your internal storage.
MAKE A NANDROID BACKUP!
Using your EXISTING RECOVERY, format /system, /data, /cache and /Internal Storage.
Flash a VIRTUAL REPARTITIONED RECOVERY.
REBOOT to Recovery to use the new one.
Select Wipe > Advanced Wipe > System, then press the "Repair or change file system" button. Choose "Change File System" and select EXT4. Swipe to apply.
Press the back button and verify the Size: and Free: values at the top. The System partition should be 2GB. Press the Repair button and swipe to apply.
For good measure, now press the Resize button and swipe to apply.
Repeat steps 1-3 for the Data partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Repeat steps 1-3 for the Cache partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Reboot to Recovery and wipe /system again.
Flash the CandySiX zip
Flash Gapps (nano or pico Open GApps or BaNks ones, etc.). You may have to experiment a little.
Reboot and Enjoy
Please give first boot a good several minutes. If you get stuck at the boot animation for a long time, try removing your ExternalSD card and reboot without it.
IMPORTANT - PROBLEMS/ISSUES:
If you have issues, I need the following:
Logs from you (logcat, last_kmsg, dmesg) linked to on pastebin.com or hasteb.in, showing the failure.
A clear description of the steps that I need to take to exactly reproduce the problem.
State what flavor build you are on: CMTE, Layers, OMS, etc...
Please DO NOT complain about problems and offer nothing to help fix it. I reserve the right to ignore you for not following insructions...
NO ETA REQUESTS!
Special thanks to @gimmeitorilltell, @bryan2894, CyanogenMod, SlimRoms, Omni and all the rest who make their source open, we can't do this on our own.
XDA:DevDB Information
[ROM-DISCONTINUED][SGH-T989][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM] CandySiX - Hercules, ROM for the T-Mobile Samsung Galaxy S II
Contributors
NoSpamDan, gimmeitorilltell
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.2
Stable Release Date: 2016-02-11
Created 2016-01-01
Last Updated 2017-01-05
Downloads
Make sure you have FULLY READ and FULLY UNDERSTAND the OP (Post 1) above before following any steps!
RECOVERY
BaNks just announced they aren't supporting TWRP versions below 3.0.
@bryan2894 has a Flashable 3.X version you can flash here:
https://androidfilehost.com/?fid=24545065934258236
(My previous TWRP 2.8.7.0 for Virtual Partitioned ROMs: TWRP_2.8.7.0.VP_hercules_NSD.zip)
TWO ROM VERSIONS: Effective 26July2016, choose from CMTE or OMS/Substratum!
(You can NOT flash one on top of the other... If you decide to switch and try the other one, you MUST Clean Flash!)
DOWNLOAD CMTE (CM Theme Engine based) ROM:
CandySiX-celox-3.2-OFFICIAL-0903.zip
DOWNLOAD OMS/Substratum themed ROM (Substratum app required - Guide to using Substratum):
CandySiX-celox-3.2.S-OFFICIAL-0910.zip
GAPPS
"Normal" BaNks Dynamic GApps
Open GApps
Your best bet is to flash a Pico GApps package made for Android Marshmallow which doesn't have an included keyboard or any keyboard modifications. Watch out for GApps that replace Gallery too!
EXTRAS
- If you want to remove the built-in SuperSU, flash this in recovery after the ROM: SuperSU_Root_Remover.zip
Previous ROM versions for convenience (can be found on my AFH account unless they are OTAs).
DO NOT FLASH a CMTE ROM on top of an OMS or LAYERS version. You must CLEAN FLASH if switching theme engines!
OMS/Substratum-based:
CandySiX-celox-3.2.S-OFFICIAL-0902.zip
CandySiX-celox-3.2.S-OFFICIAL-0817.zip
CandySiX-celox-3.2.S-OFFICIAL-0808.zip
CandySiX-celox-3.2.S-OFFICIAL-0807.zip
CMTE-based:
CandySiX-celox-3.2-OFFICIAL-0817.zip
CandySiX-celox-3.2-OFFICIAL-0809.zip
CandySiX-celox-3.2-OFFICIAL-0807.zip
CandySiX-celox-3.1-OFFICIAL-0728.zip
Layers-based (deprecated):
CandySiX-celox-2.3-OFFICIAL-0514.zip
Previous GApps versions can be found on my AFH account here.
FAQ/Info
Due to several requests, here is some further information...
DISABLE HARDWARE CAPACITIVE KEYS AND LIGHTS
NOTE: This information is now outdated, as I've added ROM features for it. I'll leave it here, but hidden for now...
Several have asked about this. I am working on an in-ROM setting for each, but I simply haven't had the time. For now you can do it manually if you like.
If you decide to try/use the following instructions, please understand that you do this entirely at your own risk
Some people like to use the NavBar soft keys (on-screen). If this is you, below you will find some commands you can use to disable the built-in Hardware Keys and Hardware Key Lights.
***NOTE: Both the HW Keys switch and the HW Key Lights switch are a WIP and do not currently work properly!
Using adb or a terminal emulator app (or the built-in one that you can install in your app drawer by enabling Settings > Developer Options > Local terminal), issue the commands under the HW Keys option you want to apply.
For each item listed, copy/paste or type the commands, one line at a time, and EXACTLY as they are shown. Press ENTER after each command.
Open adb or the terminal emulator app and issue the following commands to start a shell with root access. Press ENTER after each command.
(Be sure to accept any Superuser root access propmpts you receive while doing this.)
Code:
adb shell
su root
Now issue one or a combination of the following:
To DISABLE Hardware Touch KEYS:
Code:
echo 0 > /sys/class/sec/sec_touchkey/keypad_enable
To ENABLE Hardware Touch KEYS:
Code:
echo 1 > /sys/class/sec/sec_touchkey/keypad_enable
You should be able to use the ScreenFilter app from the Play Store to disable the HW Key lights. You can even disable the Screen Filter notifications if you like (long-press on the notification, then select the "i" button), but beware this could trick you later.
Enjoy!
Let me know how this works out for you folks. I still need Mobile Data tested and please remember it's Alpha right now, so I need logs when things aren't working.
Thanks for your work. I'm excited for testing this rom.
juni12 said:
Thanks for your work. I'm excited for testing this rom.
Click to expand...
Click to collapse
It is a WIP right now, and there will be more Candy goodness added soon... Hopefully everything works for the Herc since I don't own one (but I have a Skyrocket and have actually flashed Herc ROMs on it )
Stand by... new build compiling now... seems something was missing for Mobile Data to work. I'll update the d/l link when ready.
EDIT: New build is up, and Mobile Data works. Happy New Year!
@NoSpamDan
candy6, thanks for the great work , u really rock man
Just a heads-up, make sure you grab this build or newer for now: CandySiX-alpha-hercules-OFFICIAL-0101-06.zip
(The previous "UNOFFICIAL" builds had broken vendor blobs and no mobile data.)
EDIT: I have updated Post 2 with a modified BanKs Dynamic GApps version that has the keyboard libraries removed. Temporarily fixes the AOSP keyboard FC. You can get Google Keyboard after setting up your account on the Play Store...
Gonna try this soon.
My assessments after set up.............this rom is rocking crazy fast than cm13 (no offense) even when browsing and using play store.
Issues for me:
1. One issue is the constant show of "sd card" info after reboot (am cool with that for now).
2. No navigation bar toggle (my captivative navigation is off and I use on screen navigation to get around everytime).
3. No DPI change option (Know will come with time as above but I hate the 240 default ,too big for me)
But with Xposed, I managed to fix all of the above with the exception of "sd card" constant nagging.
This rom rocks, will update if I find any issues.
Thanks.
edwin270 said:
My assessments after set up.............this rom is rocking crazy fast than cm13 (no offense) even when browsing and using play store.
Issues for me:
1. One issue is the constant show of "sd card" info after reboot (am cool with that for now).
2. No navigation bar toggle (my captivative navigation is off and I use on screen navigation to get around everytime).
3. No DPI change option (Know will come with time as above but I hate the 240 default ,too big for me)
But with Xposed, I managed to fix all of the above with the exception of "sd card" constant nagging.
This rom rocks, will update if I find any issues.
Thanks.
Click to expand...
Click to collapse
I would call those preferences, not issues...
1. Swipe away the notification unless you have not initially set up the card (you didn't quote the notification message you are getting).
2. Nav bar is in the next build... are your touch light buttons broken?
3. DPI may be forthcoming, not sure.
EDIT: Navbar does not appear to be present in the new build. Looking into it.
New build is up in Post 2: CandySiX-alpha-hercules-OFFICIAL-0102-16.zip
This one has Quick Settings Tile Customization, Status Bar mods, Battery mods... more features to come in the near future!
...
juni12 said:
About the first build if we talk about performance, you can put beta because the rom works super fast. For a fledgling rom it is excellent. It would alfa because it lacks certain configurations and features (such as screen capture, buttons Turn off lights ...) but it is significant that installs Facebook, which in other roms including lollipop did not occur. Thanks!
Click to expand...
Click to collapse
Depends what version you are runnig because Vol Dn. + Power has always been for screenshot, plus in my last build, there were Power menu customizations like Screen Shot for those who prefer that method. Look in Settings > Candy Interface.
CandySiX was maturing on the previous CyanogenMod base but the decision was made to switch to an AOSP base. Come CAF repos are needed and still some CM too, but things are speeding back into shape! Next build should have NavBar (I hope). Will be testing soon.
New build up in Post 2 with working Navigation Bar and some other things - CandySiX-alpha-hercules-OFFICIAL-0103-04.zip. Things will be slowing down here shortly once I return to work...
New build with more features is in Post 2: CandySiX-alpha-hercules-OFFICIAL-0105-05.zip
Sorry, no time to outline the changes but should have Quick Unlock, new boot animation and several other updates...
EDIT: Seems like there is no boot animation, but it indeed boots...
I'm looking into it, but in the interim you can flash the stock Google one:
http://forum.xda-developers.com/devdb/project/dl/?id=16024
Bootloop
NoSpamDan said:
New build with more features is in Post 2: CandySiX-alpha-hercules-OFFICIAL-0105-05.zip
EDIT: Seems like there is no boot animation, but it indeed boots...
I'm looking into it, but in the interim you can flash the stock Google one:
http://forum.xda-developers.com/devdb/project/dl/?id=16024
Click to expand...
Click to collapse
Flashed the bootanimation zip now stuck in bootloop..
Anyways awesome ROM!
Fast and stable
Thanks for this.. =)
2 issues though: a) phone reboots when using camera flash (perhaps on low battery)
b) external SD card is not mounted it only shows as a portable storage - no ext SD in gallery etc.
Lucky2say said:
Flashed the bootanimation zip now stuck in bootloop..
Anyways awesome ROM!
Fast and stable
Thanks for this.. =)
2 issues though: a) phone reboots when using camera flash (perhaps on low battery)
b) external SD card is not mounted it only shows as a portable storage - no ext SD in gallery etc.
Click to expand...
Click to collapse
Bootloop? Please explain further, because it's not the boot animation file. I personally flashed the boot animation zip found in the downloads section and it works perfectly.
If you get in bootloop or have a camera flash issue (if it wasn't because of low battery), plug the device into your PC and get a dmesg log while in an adb shell, or reboot to recovery and pull a /proc/last_kmsg log. Also log the issue with logcat and post the logs on pastebin, providing the links here please. I can't fix what I can't reproduce or see in a log.
If you formatted your external SD card as portable that is how it will be used... (not as internal). Try reformatting it within the ROM.
Cheers!
Cheers![/QUOTE]
Bootloop? Please explain further, because it's not the boot animation file. I personally flashed the boot animation zip found in the downloads section and it works perfectly.
Click to expand...
Click to collapse
My bad.. I may have done something wrong tweaking settings and stuff. I changed DPI, it got bootloop, I formatted external card using TWRP VP, it got bootloop, etc. I reflashed ROM, Gapps and bootanimation. Now it's working fine.
have a camera flash issue (if it wasn't because of low battery)
Click to expand...
Click to collapse
I've switched to google camera app and the problem is gone. (Even with low battery)
If you formatted your external SD card as portable that is how it will be used... (not as internal). Try reformatting it within the ROM.
Click to expand...
Click to collapse
Honestly, I didn't know that marshmallow has introduced the new portable function for External SD. I was looking for the old way of External SD mount (I don't know what to call it.) again it was my fault.
plug the device into your PC and get a dmesg log while in an adb shell, or reboot to recovery and pull a /proc/last_kmsg log. Also log the issue with logcat and post the logs on pastebin, providing the links here please. I can't fix what I can't reproduce or see in a log.
Click to expand...
Click to collapse
I didn't post the logs because the problems were caused by my side. I shouldn't have disabled some apps and flashed boot animation after using the rom.
As you might have figured out i'm a noob (guilty! I know I deserve to die! =P ), one more thing, there's no youtube, calender, calculator and browser apps included in the package/rom. Or is it just me?
This is a perfect rom.
Many Thanks!