{
"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"
}
PLEASE DO A NANDROID BACKUP BEFORE FLASHING THIS ROM
-Special thanks-
* Thanks XDA for getting me here. I have learnt so much from this place!
* pawtipwithout you SGS would be left in the dust....but now you give us an awesome lease of life again, far better than what samsung could have done! Awesome work man
* MyUI ICS for a base to work with that allows use of Samsung Apps
* OneCosmic for the smooth as gloss RC3 **Now 3.1** and thanks for the frustrations of migrating from RC2.11 LOl
* Perka and Zatta Perka for his graphical battery animation thread linked here -> Perka[MOD]ICS based on teamhacksung's ICS Port [20-01-2012] Updated! Zatta for his scripting techniques
* Special thanks especially to asianbobo15 - who ever you are? and you patch fix for wifi calling on earlier gingerbread ROMs on DarkyROM forum - I owe you a beer!
* denverg and his themeing techniques using apk tool
* dsixda for his totally awesome ROM kitchen!! Thanks man I owe you haps!
* cyanogenMOD team for being able to decompile and look through the remnants of CM7 that I used as a hop-skip-and jump to ICS and being a saviour and fallback when ICS chucks a sh!t and does backflips on me LOL
* credits to my grass roots in the DarkyROM forum and the inspiration for me to launch into the ICS ROM building in the firstplace...onwards and upwards you guys are progressing to bigger pastures with samsung firmwares and I am trying to build some of that awesome Darky style and bring the samsung feel (and less ASOP - sorry nothing against it) back into to ICS - It's what I and alot of others LOVE! otherwise I would have gone and got a Galnex
* vibranturk for for provision of some build_prop details that have strengthened my ROM, one of his GPS files as well as some themed user apps....also for pulling me out of the sh!t last week when I crashed my phone and providing a stable ROM for me to boot to till I ironed out my bugs - Thanks man ;-)
* RaymondPJR & adm1jtg - for all your dedicated hard work with positive feedback, your provision of information from around the forum and helping me the most out of anyone else every step of the way...your a champion dude!
*****************************************************************************************************************************************
-Whats included -
*Wifi and 3G/4G Calling (Embedded application for T-mobile Wifi) standard JVU modem but I recommend flashing something more suited to USA & T -mobile like KB5
DOWNLOADS
Jarmez enhanced SGSICS RC 4.2 deodexed ROM, upgraded build.prop, coloured battery % mod, extensive framework modifications. Took me ages hopefully it works prey to god. Sync of facebook! What we have all been waiting for SGS1...fingers crossed on this one.
FM radio.....yes thats right the standard bloomin Samsung one. I may need additional drivers yet so don't jump for joy just yet. Give me feedback i.e. not random **** like "DUDE ITS BROKEN" cause that doesn't help me and i will ignore you
http://dl.dropbox.com/u/43088692/T-mobWifiCall-GTi9000-RC4.1deodexed+batmod+more.zip
Also some of the build.prop info is spoofed to enable you guys downloads to better games from T-mob website and because as far as I know only the infuse has 4g? correct? either way leave the build.prop as is.
NOTE. the framework WILL NOT work in any other ROM other than RC4.2 deodexed.....which is this ROM, sorry. I always want to remain open and help people from all ROMs cause I don't take sides, but unfortunately with the build prop work and the framework work(work work work all this darn work ) is enduring. Please if you want wifi on your ROM please contact your dev and have them chat to me and I'm more than open willing to share if they want to embed my work into their ROM.
NOTE: All non-wifi users and non T-mob wifi users, wifi scanning rate is high you may experience higher than usual battery usage with wifi on. You've been warned.
NOTE: THIS IS SUPER ALPHA NEVER BEEN FLASHED OR TESTED - FLASH AT YOUR OWN RISK AND DO NOT ***** ABOUT YOUR PHONE SCREWING UP!
please do a backup before flashing.
alpha T-mob Vib WIFICALL JARMEZ RC4.2 base batmods, deodex, sync, FM rad, TWcal+more!
Its after 1am here in Australia and its past my bed time, and I suffer with narcolepsy soooooo your lucky I am even awake.
This is FYI those coming from other ROMs just so you can't say I didn't say so...please read
[KERNEL]03.01.2011 test-kernels [CM7/MIUI/CM9 preview] platypus;SECURITY,VOODOO,OC/UV
zacharias.maladroit said:
First step before install & kernel switch:
Always have this cleaning script on your internal SD card ready
If you're
- switching kernels,
- have issues with auto-rotation,
- the cam,
- bootloops
- want to remove init script
- recover from a failed overclock attempt
please give either:
- lippol94's updated cleaning script (apply via CWM recovery): http://www.multiupload.com/XFH1GCK4MB
or
- WiwiPouPou's SYSTEM CLEANER SCRIPT (also apply via CWM recovery): (http://forum.xda-developers.com/showpost.php?p=14805606&postcount=21739)
a try
the kernel already applies some cleaning steps during install but sometimes that's not enough ...
Click to expand...
Click to collapse
reserving this post.
ok, i will trying, and have problem with scan of wifi, and i dont from T-Mobile, so it's can do video call 3g if i'm from israel??
FM rad?
do you mean the FM works in your ROM? (or should be.)
thanks dude.
sent you pm
with updated findings
"awesome Darky style and bring the samsung feel (and less ASOP - sorry nothing against it)"
afaik, darky has "AOSP" style status bar and... almost everything is AOSP style`d.
first signs are good....no bootlooping. Thats a start at least lol.
Anyone heard of data restore causing bootlooping? Thats what I have got. So right now I have an awesome blank phone. raw. nothing on it.....that works. And everytime I restore data, I get corrupt android phone process bla bla bla and /or bootloops from hell. Reflash and I am good I feel sad. All data is goneskis
TheGunner22 said:
ok, i will trying, and have problem with scan of wifi, and i dont from T-Mobile, so it's can do video call 3g if i'm from israel??
Click to expand...
Click to collapse
T-Mobile wifi-calling only works for T-Mobile USA customers. It can't be used by anyone else. I have read once that there is T-Mobile for France and someplace else that could possibly use it, but I can't confirm that. It can't be kanged to work for any other carriers. It can be ported to phones that T-Mobile does not sell, however, if you take, say your ATT phone to T-Mobile and you find someone to port the app for you, adding it directly to your stock ROM, or a custom ROM.
Its back online again now fellas.
I will have a small incremental update that's come about from adjustments on my own phone, but this still doesn't quite fix facebook sync as such. I have full account sync, profiles, contact details, joining profiles all thats missing is how to open the final field in sqlite for the picture/image to display and then we are rockin-n-rollin
As for the wifi, I will be doing slow updates on the framework until this is sorted. I pretty much NEED logcat outputs from any users otherwise I am totally screwed.....I am not a Tmo user so that will be a necessity as I apply updates and getting feedback.
Wifi-calling
Jarmezrocks said:
Its back online again now fellas.
I will have a small incremental update that's come about from adjustments on my own phone, but this still doesn't quite fix facebook sync as such. I have full account sync, profiles, contact details, joining profiles all thats missing is how to open the final field in sqlite for the picture/image to display and then we are rockin-n-rollin
As for the wifi, I will be doing slow updates on the framework until this is sorted. I pretty much NEED logcat outputs from any users otherwise I am totally screwed.....I am not a Tmo user so that will be a necessity as I apply updates and getting feedback.
Click to expand...
Click to collapse
I don't know how I missed this post yesterday, but I guess it's a good thing as i had a very busy and frustrating day. Jeez, there are so many emotionally ill people in the world. Anyway, I'm in no mood to flash anything so I'll have to do this tomorrow. I would rather have given it a quick test in Doc Masters, but I understand that the amount of work that went into doing this was great and the framework files are no longer compatible. Life took a lot out of me today, so again, I'll do this tomorrow. Thanks!
NOTE: All non-wifi users and non T-mob wifi users, wifi scanning rate is high you may experience higher than usual battery usage with wifi on. You've been warned.
Click to expand...
Click to collapse
What we've always done is freeze the app with Titanium Backup, then unfreeze it when it was necessary to use it. I'd like to add to the warning above for clarification; the wifi-calling app uses battery even when someone is not using it. Freeze it, freeze it, freeze it, to save your battery when not using it. Did I mention to freeze it, lol?
Cheers for adding that Raymond. Such a help with information.
I have brewing a very smooth, very nice and sharp ROM for release shortly. Non-wifi, but I have mastered the battery consumption v performance balance (I think) and coupled with stability. A week past, multiple flashes, coming from multiple ROMs pure stability every time.
Alpha T-Mob
It's 8:26 Pacific time and I'm doing my backups right now. Will have something to report soon.
EDIT: Wiped data/factory reset, wiped cache partition, wiped dalvik cache, formatted /system, flashed twice, rebooted, forgot to flash KB5 modem (damn, what's wrong with me), letting it sit.
EDIT: Wow, Jarmez, this seems really fast and snappy so far.
EDIT: OK, when I first started setting it up I got the message about wifi-calling and connected to my network. It seemed stuck on 'reading sim card' but I rebooted to flash the KB5 modem and didn't wait. I thought not having the right modem would make it fail anyway. Update: No signal after flashing update, and settings fc's, the same as your second Vibrant ROM did. I will try restoring APN manager to see if I can get it up and running that way. Not worried yet.
EDIT: Rats, I looked in 'About phone', and under Baseband version it says 'unknown'. That means the modem did not flash correctly, which means also there was nothing wrong with your second ROM, (remember, I couldn't get the modem to flash) So, why would that cwm from Scrizz not flash on your ROMs? I'm in a pickle 'cause I never took care of the Nexus drivers, so I can't use Odin.
EDIT: OK, I take back the previous statement. For some reason modems won't flash on this ROM, the cwm is fine. We need to find out why, right away. I tried another one and it wouldn't work either. No way to test wifi-calling unless the sim can be read and with no modem, it can't be. Help!
EDIT: Got smart, I think, switch the modem.bin out of an earlier version of Onecosmic's for the one in this ROM and am trying a non-wipe install.
EDIT: Baseband still unknown. Jarmez, we have a problem. No modem=wifi-calling can't be tested. ROM is fine otherwise though.
EDIT: I looked in /radio and modem.bin was there. I pushed the KB5 version manually then rebooted, no dice. 'No Service' notification,'Baseband unknown' in 'About Phone' and Settings>More>Mobile networks>force close.
Alpha T-Mob
We need a Vibrant version of this. This has that i9000 speaker mismatch (to hear sounds out of the speaker, you must have earbuds in the 3.5 mm jack. Also I've noticed 4 copies of each song in the Music player. The volume buttons may be reversed, but that doesn't really matter. All the soft key buttons behave as they should for a Vibrant.
The wifi connects extra fast, and the signal is excellent, however, with no sim recognized, I can make no calls. If there is no system settings/modem fix by tomorrow morning, I'll have to restore so I don't miss calls.
Looks like straight AOSP (ughh!) would like your Touchwiz touches, not much but something.
Alpha T-Mob
Oh, well, I guess it's back to Doc Masters. I was just informed of yet another ICS build that's strickly AOSP. I don't get it, it's like a hatred of anything Touchwiz even though some things Twiz are miles ahead of anything AOSP. Plus, I've waited too long with the hope of wifi-caling to not be able to flash a modem.
Don't get me wrong, this is an incredble ROM, just like your first one. But I can't test the one thing it was made for.
Jarmezrocks said:
DOWNLOADS
Click to expand...
Click to collapse
Hey Jarmezrocks,
I've been trying to download this for a couple of days now and every time I check the link its says your links are generating too much traffic and have been temporarily disabled!
Is there any chance you can put up another link please?
Cheers
Your an aussie? T-mob wifi calling bro.....not Australian lol. Wait and look in my other thread this arvo maybe.
Dropbox is delete...please other link...thank
Sent from my GT-I9000 using xda premium
Yeah I'm an Aussie, I'm living in France though.
I'm actually more interested to try it out to see how many Samsung TW apks you have working. I'm on teamhacksung's ICS atm, it's great but I miss a lot of things from the Samsung roms...
I guess I'll just wait patiently for your 2.6 update
Related
[GPL][ROM] 2010-08-20 FroydVillain 1.3.0 "villainrom.co.uk, I knew thee well..."
Quick Update for FV 1.3.1
Ok guys I can confirm the Tethering FC issue is fixed and working.
GPS is ok so far, fresh boot, launched GPS Status and it was almost instantly aware of 10 sats. Bear in mind this is indoors. Took a minute or two to get a lock where it locked 8 sats out of 11, with a 16 metre margin for error.
I'm going to keep testing this and leave the phone running stuff overnight with logcat running in case there's any weird issues.
FroydVillain 1.3.2 will hit some time tomorrow.
Thanks for your patience, sorry about the lame duck release. I'm off to flog myself silly with spaghetti. If you don't think that's harsh, you've never eaten my grandmother's spaghetti.
KNOWN ISSUES - FroydVillain 1.3.1 - KNOWN ISSUES
Selecting Tethering from Wireless menu causes an FC. - FIXED in 1.3.2
GPS -still- having some issues. - HOPEFULLY FIXED in 1.3.2, still testing.
FroydVillain 1.3.2 will hit either later today or tomorrow folks. It will be another full ROM, I couldn't avoid it sadly. Someone upstream of me decided it'd be a good idea to stop librpc being built against libgps which is the root of a lot of the GPS problems (not all the problems, there were others that have been fixed as well).
So keep those backups current. I'll be adhering to the poll and putting my preferred liblights back in place as well folks. Thanks for voting.
FroydVillain 1.3.0 "villainrom.co.uk, I knew thee well..."
Code:
*fzzzt* Hello??
...
Code:
Where is everybody? Where is everything?
...
Code:
Why is no one downloading me?
Code:
Here I am, all dressed up, nowhere to be posted...
Ah the life of the poor ROM. It can be as awesome as the very latest batch of AwesomeSauce (tm) but without a home it may as well just be a kanged knock off that nobody wants.
*Dusts off hands* Well I guess we should explain the delay in release and what the hell happened to villainrom.co.uk.
Aliens. That's right, aliens. Since I cannot fathom any other reason that a whole site hosting cluster would fall over in a giant crumpled heap and take every single backup with it that isn't older than dirt, my only explanation is, aliens.
It would appear they blitzed through the datacentre with an EMP larger than the battery on Jeremy Goh's phone* and took out everything. Now our server is back however it's suffering a rather serious bout of amnesia. It knows not of England's dismal display at the world cup**, it doesn't even know I've joined the Villain team yet. It appears to be only dimly aware of FroydVillain in that it feels it might be "coming soon".
* Jeremy Goh and his (semi) portable power station powered Hero:
{
"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"
}
** Ah if only an EMP worked on me. Sigh.
Right before we go into what's included and what's new, let's get the thanks out of the way.
Thanks to:
CyanogenMod team for keeping a step ahead of the original AOSP tree.
Alankila for his usual contributions (DSPManager/CPUSpeed).
Mikebeecham for the awesome artwork and wallpapers.
mpgrimes for his awesome wallpaper contributions.
markitoxs for helping me flesh out the wallpaper collection with some nice photos/abstract art.
Everyone who saw fit to donate recently, your generosity is greatly recognised, appreciated but never required.
Everyone who whined about issues in the last releases. I only fix stuff to make you shut the hell up yanno.
All the folks on IRC who downloaded the pre release and helped to test.
Alex24 for all his work with theming, thanks to him we'll be able to have themes good to go with each release really soon.
NikuelTrasgu for the original bootanimation and Alex24 for adding in the loading part.
My family, my friends, who all contributed to me receiving this prestig.....oh oops wrong speech.
SO what's new in 1.3.0? How can I possibly top 1.2.1? How can I justify making you all wipe your phones again?
Well it turns out 1.2.1 can easily be topped just by making GPS work properly. OH oh...there we go, 1.2.1 topped, GPS works properly.
GPS working correctly in this release without random reboots.
This had better be well received because I ran 15 individual tests of a fresh boot, get a lock on and then rebooting to test first boot lock ons. 15 out of 15 locked on with the usual varying lock on times with no random "GAARRGH" from the phone as it committed suicide.
That's right, we've eliminated the Emo factor of FroydVillain 1.2.x. Emos just don't have what it takes to help you navigate yourself around accurately. Too much effort you see. So we've given it a haircut, spruced up the clothes, washed all the make up off and given it a good stern kick in the arse with a smidgen of framework fixes to turn it into a fully functional member of the navigation society. Hurrah.
Wired Tethering works AT LAST.
Leave it to HTC to make a kernel that's about as future proof as a car made entirely out of tissue paper. From now on HTC kernel "devs" will be permanently thought of by me as evil and mad Jaffar types (Google Disney's Aladdin) with a child's chemistry set bubbling and frothing around them as they set about scuppering any possibly future useful feature just to make us buy newer phones because we can't get Froyo to work properly. Well screw you HTC! Muhahahaha.
Erm, where was I? Oh yeah. Wired tethering works from the Wireless & networks menu. You'll still need an app for the wireless tethering though since the wifi drivers don't support the Froyo method. Yet.
New wallpaper collection.
You can tell I've had extra time on my hands when I start putting things in that people have complained about since FroydVillain 1.0.0 that I consider incredibly low priority. We've brought back the original wallpapers that Nathan put in place and then some. If anyone dares complain about not liking one or all of them I will find out where you live and pay a visit with a TENS machine with the name of your testicles on it.
CMParts makes a return with a different face.
As the changelog for my fork of CMParts states, I've carried out a "Shameful SHAMEFUL rebranding for the Villain project". In the menu it's there as Villain Settings. This satisfies my want for aesthetics and your want of having features from other ROMs all in one ROM. Well maybe not the last part but you've at least got a tool that lets you play around with things you don't understand. Incidentally compcache isn't included in any Froyd release and never will be, so that option will continue to have no effect. It's also worth noting the Battery Percentage setting works with themes too. Hooray.
Japanese keyboard support.
Enough said really. OpenWNN keyboard is included. Pinyin would have been too, however it sucks goats and insists on being the default keyboard and promptly crashing. This is being worked on but for now anyone wanting this keyboard will have to grab it from the market.
More kernels.
The USB tethering fix was a kernel patch so with that and another few minor bug fixes a new batch of Nindroid 2.2 kernels are available. The included in ROM kernel is already up to date. You're welcome.
Better sleep states.
This kernel allows for a deeper sleep when idle not just when the phone is suspended. It should provide a bit of a boost to battery life.
ADW Launcher included alongside LauncherPro.
Since there are weirdos out there who don't consider LauncherPro to be the best launcher since before LauncherPro was invented, you can use ADW. No I will not include more launchers in the future. Two and that's your lot. If you want more ask Santa Claus. Or go to the Market. You might get more luck with the latter. Usually.
Vlingo included.
I don't want to hear whines about including apps people are just going to remove. If you decide to remove Vlingo you might as well remove yourself from the genepool too. Vlingo is awesome. It is awesomely awesome. Vlingo is so awesome I have to brace myself just prior to launching the app. It makes Google's voice recognition look like a partially deaf guy with a hearing aid being affected by radiation from Jeremy Goh's battery semi portable power station.
Themed HTC IME mod.
If you don't like it delete HTC_IME_themed.apk from /system and push the original HTC IME mod. Or theme your own. I don't care. Called it developer's privelage, I included a keyboard that I think looks sweet. It's worth noting that voice input works on this version.
WaveSecure included.
Anyone who doesn't use/like it feel free to delete it but for people with a WaveSecure account it's much better to have it loaded in /system/app. So it is. Yay.
Notification lights improved.
They're still not perfect but the battery LED flashes now for notifications. I personally preferred the 1.2.1 method of jogball for everything and LED for battery. Apparently you lot didn't.
The only bugs I've really noticed with it, is it'll often flash both the LED and the trackball as if it's just detected a nuclear attack. The other bug is if you boot with USB connected and then disconnect USB the LED turns red. This goes away at some point, but I can't remember if it's replugging the USB that makes it go away or a notification turns up while off power. But yeah, thems the breaks.
"OK NINPO ENOUGH YAPPING WHERE THE HELL IS MY DOWNLOAD LINK??"
Ok, ok. Here they are:
FroydVillain 1.3.0
Kernels:
19-614 MHz (default)
19-652 MHz
19-691 MHz
19-729 MHz
19-748 MHz
19-768 MHz
Remember kids, you'll need a full wipe for this one.
Anyone caught flashing an overclock kernel then coming to IRC bleating their phone doesn't start, will be extremely ridiculed.
ignore my stupidity in reading simple english....Thanks for this!!
w00t! I just saw this! Downloading now!
Full wipe? Really?!
Sent from my HTC Hero using XDA App
Yeah, full wipe as it's a new base, and new frameworks.
Oh my God.you really made my day..thanks villain team.
Sent from my HTC Hero using Tapatalk
orangeclanz said:
Oh my God.you really made my day..thanks villain team.
Sent from my HTC Hero using Tapatalk
Click to expand...
Click to collapse
LOL. I am sure Ninpo is glad to make your day for you
And ninpo, nice work on the release notes mate
Woot, finally!
VillainRom LIVES!!!
Whoop! DLing NOW!
Wired Tethering works AT LAST.
Click to expand...
Click to collapse
it worked for me on 1.2.1, just had to use the hndis driver
pulser_g2 said:
Yeah, full wipe as it's a new base, and new frameworks.
Click to expand...
Click to collapse
Oh,so I have to port my themes from 1.2.2 to 1.3.0 again!
But big Thanks for this great ROM.
Downloading now,too
Is USB-tether the same RNDIS solution as in sense roms? (I.e it doesnt work with OS X?)
Removing ADW launcher
Hi
First of all, thanks for the great VillainROM releases, especially FroydVillain.
Just installed 1.3.0, and just to be sure:
To remove ADW Launcher, I just do an adb shell, go to /system/app and remove ADWLauncher.apk?
Edit:
And same approach with the WaveSecure?
Json_81 said:
Is USB-tether the same RNDIS solution as in sense roms? (I.e it doesnt work with OS X?)
Click to expand...
Click to collapse
Well it works with Linux so I can't imagine it not working with OS X unless it really is that big a pile of...oh wait, it's Apple.
rd-Target said:
Hi
First of all, thanks for the great VillainROM releases, especially FroydVillain.
Just installed 1.3.0, and just to be sure:
To remove ADW Launcher, I just do an adb shell, go to /system/app and remove ADWLauncher.apk?
Click to expand...
Click to collapse
Aye.
It's 2.00am and I was about to sleep. But once I found out there's update, now am sitting in front of the computer , backup everything , downloading the rom , thou tomorrow morning have to go church .
Thanks for the new rom !!!
Ganii said:
Oh,so I have to port my themes from 1.2.2 to 1.3.0 again!
But big Thanks for this great ROM.
Downloading now,too
Click to expand...
Click to collapse
I hope you port your themes. They complete my villainrom!
Yeah guys!!! You are more awesomely than awesome!! LOL!!! Nimpo you are still my favourite comedian...
THANKS A LOT!!!!
Villain team smashing it up once again. Thank you, will definitely be giving this a try later. Is this likely to cure my OCfD?
Sent from my HTC Hero using XDA App
Hey Ninpo I really really wish to do two things right now.
Firstly to Kick your ass for the funniest release notes and secondly to Kiss your damn ass for the nice work on the most stable and smooth Froyo Roms for Hero. Definitely worth praise, great work and great effort.
rd-Target said:
Hi
First of all, thanks for the great VillainROM releases, especially FroydVillain.
Just installed 1.3.0, and just to be sure:
To remove ADW Launcher, I just do an adb shell, go to /system/app and remove ADWLauncher.apk?
Edit:
And same approach with the WaveSecure?
Click to expand...
Click to collapse
Root explorer can remove the ADW.
Sent from my HTC Hero using Tapatalk
FroydVillain 1.4.4 OTA update released!
Changelog:
Code:
GPS NTP time sync now configured somewhat locally.
New libhtc_ril.so
GPS configuration fixes.
FroydVillain 1.4.4 update for EUROPEAN users.
FroydVillain 1.4.4 update for NORTH AMERICAN users.
FroydVillain 1.4.4 update for ASIAN users.
If your continent isn't listed use the one closest to you.
Also make sure if you flashed the Nindroid-2.6 test kernel, flash back to Nindroid-2.5. Use whatever radio works best for you with your carrier.
Kernels (also available in OTA, turn on experimental updates):
19-576 with bootanimation
19-576 without bootanimation
19-614 with bootanimation
19-614 without bootanimation
19-652 with bootanimation
19-652 without bootanimation
19-691 with bootanimation
19-691 without bootanimation
19-729 with bootanimation
19-729 without bootanimation
19-748 with bootanimation
19-748 without bootanimation
19-768 with bootanimation
19-768 without bootanimation
FroydVillain 1.4.3 OTA update released!
Changelogs:
1.4.1
Code:
Restore missing file for Villain Updater app.
Fix Google Framework crash.
Supply missing Wifi tethering app.
1.4.2
Code:
Fix outdated library crashing Google Shopper app.
1.4.3
Code:
Restore Clicker.apk for HTC IME Mod keyboard calibration.
Fix apns-conf.xml not being correctly configured for new GPS implementation.
Supply newer libspeex.so to prevent SoundHound crashing with Vlingo installed.
Nindroid version 2.5
Code:
Replace unnecessarily long app waits with sleep timers to eliminate "background noise" from drivers causing futile cpu usage. Improves battery life and stability especially noticeable with games that use accelerometer.
Allow for IP header compression on both IPv6 and IPv4 to improve Google app performance.
Add 245MHz clock speed into the table to facilitate correct clock timings when in power collapse suspend or SWFI.
Add 576MHz kernel variant for phones that cannot clock to 614MHz. Ondemand governor used due to frequency table being too narrow.
Workaround for Market stalling problem (thanks Revoked)
If your Market downloads are sticking, do the following:
Code:
adb shell rm -f /sdcard/.android_secure
Or mount the sdcard to your PC and delete the file from there.
All OTA updates from 1.4.0 - 1.4.3 download links for those who can't use the OTA app:
MUST BE APPLIED IN SERIES E.G. 1.4.1 THEN 1.4.2 TO GET 1.4.3
FroydVillain 1.4.0 - 1.4.1
FroydVillain 1.4.1 - 1.4.2
FroydVillain 1.4.2 - 1.4.3
Kernels (also available in OTA, turn on experimental updates):
19-576 with bootanimation
19-576 without bootanimation
19-614 with bootanimation
19-614 without bootanimation
19-652 with bootanimation
19-652 without bootanimation
19-691 with bootanimation
19-691 without bootanimation
19-729 with bootanimation
19-729 without bootanimation
19-748 with bootanimation
19-748 without bootanimation
19-768 with bootanimation
19-768 without bootanimation
FroydVillain 1.4.2 OTA Update:
Now live in the Villain Updater app is an OTA update that fixes the FC with Shopper.
GPS ISSUES: People having a problem with GPS, go to Menu, Settings, Applications, Development and UNCHECK Allow mock locations.
To make it as simple as possible:
Minor Update:
Just a small update for FroydVillain 1.4.0 folks to add in some missing files.
FroydVillain 1.4.0-1.4.1 Hotfix.
The fix contains a missing file for the VillainROM Updater, aNetShare for wireless tethering and the GoogleCalendarSync that stops the Google framework FC.
FroydVillain 1.4.0 "Smoother than a cashmere codpiece"
Well ****. You're probably getting tired of me saying every new release is awesomely awesome and fast and stuff.
Well tough tits because FroydVillain 1.4.0 is the fastest and smoothest FroydVillain TO DATE. Smoother than a buttered banister. For those who don't know what a banister is, it's a ****ing handrail.
Hell this release even contains boobs. Oh yes. Boobs. No penises though. Not gay. Honest.
Never let it be said that I let a small issue such as an entire website crash slow down my development work. Oh no. By the way my missus would like me to pass on that you can all go to hell and die slowly in a fire. She'd also like to ask for her other half back.
Sheesh. Anyone would think I only half listen to her as I rattle off on my keyboard. Oh, wait. Woops.
SOOO what has Uncle Ninpo kicked Santa out of bed to bring you today? Well there's a bit of a story to this. Bet you saw that comin...
How can I best intro this? Oh yeah.
{
"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"
}
Seriously. There I was cocking about with Webkit (DA FING THAT MAKES INTERWEB PAGES APPEAR for the newbs) and I somehow managed to make my way over to...DALVIK. Yes, that dark and mysterious place that many have gone and few have returned from alive. Dalvik, the heart that beats for Android, the second most important thing after the kernel.
Dalvik has eaten many a developer alive and spat them out in a gibbering wreck. It turns java fans over to .NET, it's even made a few go and buy an iphone. This is not a place for the faint hearted.
**** it, I thought and dived straight in. This is where the WTF/min picture comes in. Someone on the AOSP project -really- hates MSM7200A class phones. If it hasn't clicked, your Hero is an MSM7200A class phone. That's the processor/chipset inside. Google hate it, just FYI and so do HTC.
Well I ****ing don't so I grabbed Dalvik by the short and curlies and informed it that it was going to play nice with our Heros from now on. Which brings us to FroydVillain 1.4.0. What was supposed to be a quick fix to Tethering and GPS turned into an epic and bloody battle with Dalvik. I won.
I also got JIT enabled in the JSC rendering engine for the browser too, which considering that was my original goal, I'd call that a result.
SO what's new?
Well.
Completely new Dalvik build...
...the likes of which you won't see in any other ROM until someone either looks at my github and yanks it all, or they accept the changes upstream. Given that I think upstream consider me as some madcap insane scientist type person, I wouldn't hold out too much hope on the latter. Knowing these forums though, the former will probably happen pretty soon. Wibble.
So er yeah where was I? Oh right, new Dalvik build. Instead of being a giant lazy bastard when it comes to the Hero, Dalvik is now painfully aware of the processor our phone uses and how best to make use of it. Dalvik is already losing weight. It's about time, the fat ****er. Last time I ran into something this badly built it collapsed on my head when I slammed a door. Never did see any money back from that house.
JIT enabled in the browser engine
This was actually enabled in 1.3.x but I forgot to mention it. Plus I wasn't sure if it was really working because online benchmarks suck nut. It's at least as fast as the Eclair V8 engine though, which is good. Unfortunately the V8 engine on Froyo has been snatched away from us because it has armv7 code hardcoded in. Bastards.
AndChat makes a return
Because I don't use it, I kept forgetting to include this alright-ish-sorta IRC app (hey at least it's free) in FroydVillain builds after we got the go ahead from the dev. If you ask me, and I'm sure you won't, Android IRC is one of the best paid apps on the market.
New kernels again
Oh yes new kernels again. For those ITCHING for me to trip up over the GPL, tough ****, bang up to date source is in my signature. Muhahahaha.
This one has some IP improvements that apparently make Gapps play nicer. Given how badly Gapps have been playing lately, we could use some niceness from them. It was the kernel this time Google, next time it'll be pitchforks on your lawn.
Oh I've also made a set of kernels that turn off the bootanimation. Why? Does a 40 second boot time from power on to lockscren sound attractive? I thought it might. That's why.
More wallpapers
Since I added in a Villain wallpaper collection I've been hammered with suggestions for it. The good ones are in. The ones that had me looking for a bottle of bleach and a cotton swap are out. You're welcome.
Incidentally, speaking of eye candy, if you want a pure visual orgasm with the Hero, install Alex24's Galaxy theme+fonts and select the 5th wallpaper from the Wallpaper app (the blue FV wallpaper). Then get off your cheap arse and buy Beautiful Widgets and use the NeonTransparent clock skin with the Simply Beautiful weather skin.
If you disagree that they're not the most awesomely awesome things ever to grace your home launcher screen, you're clearly a moron and should sit in the corner away from everyone else.
I mean come on:
After popular demand, notification lights...
...work as you voted for. We're back to jogball for everything, LED for *****ing about battery status. Hurrah.
GPS really works, this time.
I promise. Almost two days testing this **** and it's been fine. So many reboots. My poor Hero. It thinks it's running Windows now. I've had to give it a completely blue theme to calm it down.
DSP Manager updates
****ed if I know what changed. The last time I asked alankila about DSP Manager he said some stuff that had me running and screaming for my happy place. He is one scarily smart bastard. It could have been satanic chants or it could have been mathematical formulae for how DSP Manager works. Who knows, I certainly don't. All I do know is my Hero has gone from sounding like trash, to outputting Dire Straits - Money for Nothing out in decent quality out of my car stereo. Score.
Woops, almost forgot...
Thanks to:
Cyanogenmod. Without their help and their repo, I wouldn't be the gibbering mad developer cackling over the code that I am today.
Alex24 for his theming work.
Mikebeecham and mpgrimes for some stellar wallpapers.
All my IRC minions for testing.
NikuelTrasgu for the original bootanimation and Alex24 again for making it smoother and loop for Froyo.
Anyone I forgot, just to avoid bleating. Imagine your name is here in a giant red font, flashing your sexiness per minute.
So, onto the links I guess.
FroydVillain-1.4.0-release download.
Themes:
Alex24's awesomesexysauce Galaxy theme.
Now, for those who cannot help but beg and plead that they don't want to have to wipe, we've had good reports from a few testers after just flashing the ROM. So give it a try. However if you want to report problems I suggest you nandroid and do a completely clean install before reporting those problems. No need to wipe dalvik, the install script does that for you. Aren't I nice?
I know these release notes will come as a bit of a disappointment to some, but come on folks this is the third release in what, a week? Lol. I need more breathing space to recharge my creative batteries. Hopefully this release will be stable enough for you all to give me that breather.
Enjoy.
EDIT: Woops forgot aNetshare for wifi tethering. Attached.
I'm soo gonna Flash it before i go to bed!! Thanks again!! Appreciate!
Fantastic job...
Smooth as silk indeed my friend...
Great job.... tested the GPS, could see 11 satellites immediately... but took about 4-5mins before it locked on to 5 birds...
Beyond that.... it's a masterpiece... flashing the galaxy theme now!
Great job mate!
Downloading, can't wait to this for a spin
Sent from froyo hero
good day mate, you are definitely a guy that keep promise, i just woke up and viola, here's the 1.4.0 . gonna b a nice day . downloading now
thepittbull said:
Smooth as silk indeed my friend...
Great job.... tested the GPS, could see 11 satellites immediately... but took about 4-5mins before it locked on to 5 birds...
Beyond that.... it's a masterpiece... flashing the galaxy theme now!
Great job mate!
Click to expand...
Click to collapse
Galaxy theme from previous post 1.3.0 works?
ShiDi said:
Galaxy theme from previous post 1.3.0 works?
Click to expand...
Click to collapse
NO IT DOES NOT. I'll add it to the OP.
EDIT: Added.
Hacre said:
NO IT DOES NOT. I'll add it to the OP.
EDIT: Added.
Click to expand...
Click to collapse
Woot!! Woot!! Appreciate itt dawgg!!!
(=
Hacre said:
NO IT DOES NOT. I'll add it to the OP.
EDIT: Added.
Click to expand...
Click to collapse
Thanks once again for taking matters into your own hands and showing the world that the Hero is not an endangered species, and for the HIGHLY entertaining post! The cartoon was just perfect lol
EDIT: ahh you cunning man you, another trick to see if we're paying attention, eh? link on villainrom.co.uk is missing the /galaxys/ folder for the theme and fonts
you rock! :-D
Downloading. Will have a try once ready. Good job! Thanks.
thanx i will flash it now
Looks like im having freeze screen & reboots. Flashed it the 3rd time & w/o OC kernels & Galaxy theme.. will see how.. =\
This definitely made my day, laughed my ass of on the train, don't ever stop with these awesome release notes!
Waited up last night hoping for 1.3.2 and what do i see when I wake up, 1.4.0, oh yeah!
Will download now and try it out! thanks!
Sent from my Hero using XDA App
Thanks
& Yeah really nice release notes
great, galaxy 1.3 worked for me but i'll reflash 1.4 (wrong link btw)
i saw you changed back vilain setting to cyanogen mod
looks like you fixed internal usb tether, yep it works
Amazing job again mate
Flashing as soon as I get into work.
Is the gallery bug still there?
Also, where are the boobs exactly? Screenshot anyone?
Which version of gapps in included in this rom?
what doesnt work?
or does it means everything works :S
Welcome to OverDrive
OverDrive is a ROM me and a few people have been working on for the past few months. This ROM poped-up first in Android Central by me Redbaron, The reason this poped-up was the main fact that there are only a hand full of ROMs for the LG Optimus V, and I am a flashing junkie, meaning I change ROMs like I chew gum, chew it up until the flavor is gone, then spit it out. So here is a ROM created from Stock, and built from the ground up. Having both tested to work on new and older Optimus V's in this thread you can find StockOV which is a rooted and modified running Android 2.2.1 updates are coming soon for this ROM. As for OverDrive, OverDrive is a heavenly modified ROM ported from Stock, running Android 2.2.2 removed all VM's stock apps, kept the Activate app, imported modules and files from kernels for optimum use and performance.
I AM NOT RESPOSIBLE FOR ANY DAMAGES OR FLAWS IN YOUR PHONE, NOR BRICKED PHONES, YOU DO WHAT YOU DO TO YOUR PHONE BECAUSE YOU DO IT. A LITTLE KNOWN FACT DO NOT LG FACTORY RESET!!! UNDER ADVANCED MENU. DO NOT!!
StockOV v2.2.1 [v1.1 +Picasticks]
{
"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"
}
The Goods v1.1
Fixed TWS (Time Without Signal)(Battery saver)(Can be undone by removing "xtr50fix-v1.apk" from system files)
Deodexed
added Picasticks, tweaked kernel
Removed VM Crapware (Except Activate APP)
Updated Market to Google Play Store
Removed kickback, soundback, talkback, gmail, youtube, maps, talk, email, protips and google talk
Edited build.prop
Overclockable - Not recommended above 824
v1.0 The Goods
Everything stock 2.2.1 has to offer
Superuser 3.0
Latest Busybox
Better 3G Speeds
Tested and runs beautiful
DOWNLOAD v1.1
StockOV-1.1
DOWNLOAD v1.0
StockOV-OverDrive1.0
This ROM will run with newer phones, also this ROM is best flashed with Xionia Recovery
-----------------------------------------------------------------------------------------------------
OverDrive v2.2.2 [v2.2]
v2.2 The Goods
Android 2.2.2
Swype
Removed all VM Apps except Activate
More support, as the Dev of this ROM, if you have ANY problems I can help
Added bin and other files from Optimus S for better speeds.
build.prop updated and modded.
proximity.delay=20, vm.heapsize=38m, wifi.supplicant_scan_interval=160
Apps2sd added[Not the app]
Superuser 3.0.7
De-Odexed this increases speeds
ZipAligned
Not overclocked yet, please flash the temporary kernel at the bottom of the page or wait for kernel
Removed Email, and VoiceDialer from system files.
v2.1 The Goods
Android 2.2.2
Swype
Removed some VM Apps
Removed boot sounds
2.2.2 DOWNLOADS!
DOWNLOAD v2.2 Stripped
OverDrive-2.2- de-odexed.zip - Media Fire
Mirror - Sky File
Mirror - Dropbox
DOWNLOAD v2.1 Stripped
StockOV-OverDrive2.2.2-stripped-2.1.zip
Instructions on how to flash
1)Back up / Nandroid
2)Wipe - boot, data, system, cache.
3)Flash
3a)Flash kernel (if chosen to)
4)Reboot
5)Enjoy!
Keep posted for more updates and roms from me, Redbaron.[2/11/2012 9:55 PM] Currently working on 2.2.2+ also custom kernel.
[2/28/2012 12:35 PM] Finishing OverDrive 2.2 (2.2.2+ Kernel + build.prop Tweeks)
Also finished de-odexed 2.2.2
Been working on a side project for fun.
Removed more bloatware (Virgin Apps, Keeping Activate, never know when you need it)
[3/2/2012 12:49 PM]Working on custom kernel, Working on a new ROM.
A Special thanks to:
vegetajin8 - My Tester
LeslieAnn - A Great Dev
obijohn - Bumble Bee Kernel
Ive noticed with the stripped rom launcher pro isnt the one to use. What a good launcher for this? Would go ex be good. Great rom by the way and fast. Im using overdrive deodex
cell2011 said:
Ive noticed with the stripped rom launcher pro isnt the one to use. What a good launcher for this? Would go ex be good. Great rom by the way and fast. Im using overdrive deodex
Click to expand...
Click to collapse
Interesting let me look into that, as for a launcher, I know ADW works great. Please try out GoEX and see what happens, maybe let me know what happens?
Thank you for the complements
Hi there yes im running go launcher i like it. I think when there is alot of apps you have that illusion that its faster because of scrolling. I use horizontal launcher pro setting on this and its pretty nice too. But so far scrolling sideways works best for me. ADW is nice too. The kernel works nice for me too i use 480/806. Battery still seems to be good
I know exactly what you mean, I'm currently working on a custom kernel for OverDrive, I am also working on a custom ROM
I just bought my Optimus V and roms Display a Blackscreen. I can tell they are booting and things seem to work based on sounds but the video drivers are not working with this new phone.
Scratch That, I Just Tried To Install It And It Won't Load For Me Either. Just Getting The Black LG Screen, Please Help (It Was The 2.2.2 Version)
Edit: I'm Trying The v1.0 Now.
Edit: v1.0 Works But 2.2.2 Is What I'm Looking For.
Very interesting, I'm assuming both of you have newer Optimus V phones. Am I correct about this? If so then I need to investigate this issue, because this ROM has been known to work on both old and new phones. So all you guys get is a black screen yet you can hear the start up sounds? Sounds like my kernel needs the latest display drivers for the new Optimus V.
Sent from my LG-VM670 using XDA
Don't know how handy you are with a kernel but I have but two requests if at all possible.
Multitouch typing is a bit of a pain on the OV. Alot of the times close taps (like C+H on the keyboard) get registered as a slide. Sometimes even further away keys like U+P. Dunno if its possible to fix that in the kernel but it would solve a major annoyance of mine.
The other, being implementation of "Deep Idle". I figured since CDMA eats more battery than GSM when connected, it could grant some extra time on battery.
And lastly, good luck on the ROM. I am stuck with Froyo due to IHO performance/battery woes and outside of my failed attempts to theme BumbleBee as Gingerbread, I've had nothing to look forward to. Will be testing more when you have your kernel up to go with the ROM.
One last Q Iforgot to ask. With regards to your current Stock version, is the Time Without Signal bug fixed there? Overclocking is of no real use to me, so flashing the BB kernel does me no good _for now_ (I could just use BB! ).
redbaron2005 said:
Very interesting, I'm assuming both of you have newer Optimus V phones. Am I correct about this? If so then I need to investigate this issue, because this ROM has been known to work on both old and new phones. So all you guys get is a black screen yet you can hear the start up sounds? Sounds like my kernel needs the latest display drivers for the new Optimus V.
Sent from my LG-VM670 using XDA
Click to expand...
Click to collapse
Yeah I just bought my phone about a week ago. I can hear the Start up sound and even unlock the phone and start to dial. The Screen is on I can see the back light but The Screen is completely Black. I would assume this is due to the Display Driver issue.
therealguppy said:
Yeah I just bought my phone about a week ago. I can hear the Start up sound and even unlock the phone and start to dial. The Screen is on I can see the back light but The Screen is completely Black. I would assume this is due to the Display Driver issue.
Click to expand...
Click to collapse
Thank you for your input, every peace of detail helps.
I have been investigating this problem ever since you posted the bug, It would seem the stock kernel is meant for the older phone, but this is an easy quick fix, Give me today to fix this and I will release an update today. Thank you again for your detailed bug report.
captaincrook said:
Don't know how handy you are with a kernel but I have but two requests if at all possible.
Multitouch typing is a bit of a pain on the OV. Alot of the times close taps (like C+H on the keyboard) get registered as a slide. Sometimes even further away keys like U+P. Dunno if its possible to fix that in the kernel but it would solve a major annoyance of mine.
The other, being implementation of "Deep Idle". I figured since CDMA eats more battery than GSM when connected, it could grant some extra time on battery.
And lastly, good luck on the ROM. I am stuck with Froyo due to IHO performance/battery woes and outside of my failed attempts to theme BumbleBee as Gingerbread, I've had nothing to look forward to. Will be testing more when you have your kernel up to go with the ROM.
One last Q Iforgot to ask. With regards to your current Stock version, is the Time Without Signal bug fixed there? Overclocking is of no real use to me, so flashing the BB kernel does me no good _for now_ (I could just use BB! ).
Click to expand...
Click to collapse
I'm a little bit new to kernel development, yet I have experience but I just cracked the book on linux kernels which is the same basis of Android kernels, I can't promise anything, but I can do my best. The multi-touch might not be that hard to work on, as for the "Deep Idle" I will be looking into this and all about it, I have been working on perfecting my ROM(s) before continuing and finishing my kernel development, but I have taken your input into consideration, I think having more then 2 points for multi-touch will be a great advantage, but lets see what I can do. I have no team, no help, and still learning in the process, there are so many things to learn and so little time. As for the "Time Without Signal" I have found this fix for that problem, I don't think my StockOV ROM has the fix yet, because I did port it from the Stock Optimus V ROM. So I will be adding that to StockOV.
Hmm, ok. Obijohn had fixed the TWS bug in the kernel itself; would be helpful to have his BB kernel source. Dunno where he got/how he did the patch though. Would be much better than using the app.
As for multitouch, I think it's just how the phone handles the proximity of the two points. Unsure myself, I am just a power user, but I don't think the phone is capable of more than two points.
I wish your ROMs well. I'll be lying in the bushes in wait to test.
Updated StockOV 1.0 to 1.1!!!
StockOV has been updated to v1.1
Picasticks Modded Kernel
New Google Play Market
Dedeoxed
Rooted
Overclockable
Check out the first post for more info.
Hope you all enjoy the new update
Keep your eyes pealed for OverDrive turning into a FroyoBread ROM.
Keep an eye out for the new GingerBread ROM coming soon!
Fixed StockOV's 1.1 download link...
I guess 1.1 was not up.
Link can be found on the first post.
or here
thank you Meowdib
I've been running Bumblebee 2.4 ever since release, and I've tried loads of other ROMS. They all are either too bloated, too slow, crash too often, or have features missing. I've been running 1.1 ever since release and I'm impressed. Works great - fast, and no problems. The new go-to ROM.
rivethead23 said:
I've been running Bumblebee 2.4 ever since release, and I've tried loads of other ROMS. They all are either too bloated, too slow, crash too often, or have features missing. I've been running 1.1 ever since release and I'm impressed. Works great - fast, and no problems. The new go-to ROM.
Click to expand...
Click to collapse
Thank you very much, I have spent a great deal of effort towards these two ROMs, I'm happy to know its the new "go-to ROM"
Just installed 2.2.2, so far so good. I installed the OC kernel but don't see any options under Settings to configure OC speed - do I need a particular app, or are the OC speeds not configurable?
anonim1 said:
Just installed 2.2.2, so far so good. I installed the OC kernel but don't see any options under Settings to configure OC speed - do I need a particular app, or are the OC speeds not configurable?
Click to expand...
Click to collapse
You need an Overclocking app,
Search the market for
OverclockWidget, or CPU Tuner.
You can also use ROM Toolbox.
I don't add these apps because everyone uses different overclocking programs, I didn't want another app that takes up space.
Just for the convenience of the user,
Got it. Thanks for the quick reply.
anonim1 said:
Got it. Thanks for the quick reply.
Click to expand...
Click to collapse
No problem, glad I could help!
First I would like to give credit to everyone who has worked on GBX0* in any way. ACL, arrrghhh, detule, and Stinger22 to name a few important faces around here. I do not take credit for 99% of this. It is a modded version of the GBX already published on XDA.
Stinger22 is responsible for building the killer new kernel. I packaged the kernel into a boot.img and collected all the compatible updates into a single installable Zip with lots of tweaks.Stinger22 deserves big thanks for his work here.
There will be limited support for this build. Feel free to ask questions, and even better if you can help answer them. If you know how to fix something that is broken I would love to hear from you. I would be happy to include anything that you can contribute.
Due to the number of people unhappy with the RHOD100s phones and this rom, we do not recommend it for the RHOD100s (not that we ever did as we only have RHOD400s to test with).
New install guide.
Now what you came for:
GBX*
Includes:
GBX 5-8-12 lib update.
Slightly smoother boot animation used.
Build.prop tweaks.
Added a couple of ringtone/media sounds.
Superuser replaced with SuperSU .97
Modded audio.conf file to allow for the streaming of media metadata from apps like Pandora when the advanced menu / car bluetooth mode is enabled in the app. Also this change should allow for more Bluetooth devices to connect to the phone. Does only appear to support AVRCP 1.0, so no metadata without extra app support. However track forward/back/pause will work with some setups.
Added circle battery icons with %s for more precise gauging. Shows in 5% blocks. What you see is +/-3% of what the battery is really reporting. Based off the themes here. It is better than a half filled bar IMHO. It might take a full discharge or two before the battery gague/acl code becomes accurate. The battery also tends to drop quickly in the first 10% and then levels off.
RHOD300 keyboard fix. Credit to Detule
Changed RHOD100 from default keyboard to RHOD100_UK keyboard map.
Fix to ramdisk to resolve error reported during boot.
Fix to bluetooth main.conf to prevent bluetooth media devices from crashing OS. *only included in the 3.4.26.1 and newer full build*
-Still have issues where connecting/disconnecting the sink device can sometimes cause the phone to reboot. Seems sink device dependent. Mostly fixed in 3.4.26.13
Fixed bluetooth typo bug to 3.4.26.1 in 3.4.26.11
Boot animation in 3.4.26.13 credit.
3.4.17 Kernel update:
Including ACL's newer battery code.
More accurate readings from battery gague.
Maybe slightly better sleep battery usage.
Small Bluetooth fix (I find paring to be easier).
Kernel panic fix that may help prevent phone lockup if apps crash.
Many other small patches.
Fixed USB detection issue in 3.4 kernels.
Overclocking still supported. (SetCPU is free to XDA members)
Added a hack supplied by detule to prevent the sd card reader from suspending to prevent unexpected sd card removal errors.
Added a kernel splash screen to cover up some of the rolling text during boot time. Credit.
Sleep works with wifi turned on. - Battery life should improve where wifi prevented sleep before. Wifi tethering will prevent wifi sleep.
Zoom slider bar now works. Acts like a two finger touch moving from the center of the screen. If you tap on the zoom bar it will be just like tapping in the middle of your screen. Something to keep in mind if you get unexpected touches while holding the bottom of your phone. More benefit than a draw back IMHO. Added permission files. Link at bottom for those who just need this (based off of mankineko's work).
3.4.24 Kernel *minor update*
Includes updates from source.
Added code to cause system to reboot rather than hang from a system crash.
3.4.26 Kernel
Reboot function in shutdown menu has been fixed (power off is still broken)
Host file is no longer over written on boot up. This had been preventing ad blocker apps from working correctly.
ACL's panel code has been used. Hopefully this will resolve some issues for the RHOD100 users. We have no way to test, so it is as-is.
Auto brightness has been fixed. You may need to press the power button and force the lcd off, after it has been enabled, before it will take effect.
Device name is no longer reported as 00000000 by ADB. It should show as the serial number.
3.4.35 Kernel
Slight performance tweaks.
Added CrossBreeder mod. Basically helps tethering internet.
Added "Smartassv2" cpu governor. Can be set using apps like SetCPU. Should be slightly better performance, but may come at the cost of battery life.
Added "row" scheduler.
3.4.41 Experimental Rhod400 Kernel.
Shutdown working
Fps limit fixed, plus a slight gpu performance boost (previously was benching about 19fps for both 2d/3d, now I'm getting up to 60fps 2d, 26fps 3d)
Enabled more compiler optimizations. Kernel is slightly larger, but seems to perform a bit better
USB: No need to plug/unplug once before adb works, faster cable connection detection
Other miscellaneous tweaks that may or may not help battery life
Known bugs:
Many of these bugs are found in the 3.X kernels, and so they may be found here too.
MMS does not work out of the box. Add this APN info if you want it.
Google maps newer than 5.9 shows graphic distortions with street names, and other graphic issues sometimes. Waze is a good gps alternative if you want something with more features.
Shutdown and reboot options on the power button menu do not work.
Auto backlight does not work.
8-15-12 RIL update breaks radio (on CDMA for sure/no reports from GSM owners).
SD card unexpected removal errors when the phone wakes from sleep on *some* phones. -try a non SDHC sd card if all other standard troubleshooting fails. I have been able to use a 512mb and 1gb card micro sd card without issue. However all my 4,8,16, and 32gb micro SDHC cards have this issue. Hacked work around as of update 3.4.17.
May have to remove and reinsert USB cable a few times before the phone will recognize it has been plugged into a data port. Also you may need to turn features on/off to get the correct tethering/usb storage/usb debug to work correctly.
No front facing camera support for RHOD100.
Deleting bluetooth.apk may be necessary to get the phone to connect to some Bluetooth devices that have any advanced features.
If Bluetooth is left on and the phone is rebooted/crashes, the unit may bootloop. I have not found a fix other than reloading the Rom from recovery.
This bug seems to effect A2DP and other audio streaming devices the most v.s a bluetooth mono ear piece for calling with. This is a bug I have been able to repro on the GBX*+ 3.3.6 kernel as well. Make backups before using Bluetooth. If you are a CDMA user, you could try the original Ril from inside the GBX+3.x rom. It seemed to cause the reboot loop a little less. However GSM users must have the 5-8 Ril to use this Rom.
Found that this bug seems to be for devices that support multiple profiles. I have a Bluetooth receiver that will use phone and media profiles. If the phone profile is disabled the lock-ups do not happen. This work around will not let you use the phone features, but you can stream media. You need to pair the device. Then long touch it to get a to an options menu. Uncheck the phone profile option to stop the crashes when playing any media.
Sometimes if the phone locks up during the boot animation from this issue, then you reboot once or twice, and leave it alone for a long long time it will sometimes finally finish booting. It is worth a couple of reboots, and a lot of waiting vs reloading the rom. It also seems to help if you plug the phone into the usb on a computer after the boot process has passed the blue screen.
Pandora's internal/advanced bluetooth settings must be turned off, otherwise it may crash the phone on device disconnect.
Bluetooth is not 100% stable, and may crash the phone on connecting or disconnecting devices. During use it is stable.
If the phone crashes while bluetooth is turned on it may boot loop. If this happens connect the phone's usb port to a charger or usb port on a computer. This should cause it to boot correctly on the next time around.
Sprint phones must be activated on the Sprint network in WM before loading Android. Android can not activate everything correctly.
It has been reported that the keymap for the RHOD300 is not correct.
Not an Android bug, but Sprint DNS services are crap. I found good working links not working correctly due to bad dns info. Of course you can use any public dns server you like.
A suggestion for getting your own dns in more easily is this App.
If you tether on Sprint I suggest that you put your own DNS server in under the TCP/IP settings on client device as it will only use sprint's by default. I leaned this the hard way.
RHOD100 WIFI may not reconnect to access point automatically upon waking from sleep. Disable and reconnect to work around.
This Rom was only tested on the Sprint TP2 RHOD400. It will probably work on any that worked with the GBX0* + 3.3.x kernel, but we can't promise it.
Updated RIL from Skysoft here. Not included in any build. 4-16-2013
Full Downloads:
GBX0*+3.4.17 Full.
GBX0*+3.4.24 Full
GBX0*+3.4.26 Full
GBX0*+3.4.26.13 Full *feedback on if Bluetooth is still crashing the phone after a clean rom load would be interesting.*
GBX0*+3.4.35 Full
Kernels:
3.4.26 Kernel update.
3.4.24 Kernel update.
3.4.17 kernel update.
3.4.35 kernel update.
3.4.41 Experimental Rhod400 Kernel.
If you download please hit thanks at the bottom and/or post feedback. I'm curious as to how many people are downloading.
New install guide.
Old install directions for all other NAND roms.
It is assumed that you have unlocked your phone. If not read here and/or here, and/or here.
If you are running the 8-15 ril that was patched, and you are unable to get a cell signal, I would highly suggest that you install the older patch ril file.
If you want to add just the permission files for the zoom bar (and a few other things) rather than downloading the whole thing again here they are. When I did this it broke Zeam. I had to add another launcher, and then switch between the two. That fixed it for me.
As always BACKUP, BACKUP, BACKUP before doing anything. Please use at your own risk.
*Related goodies*
Gapps package.
For those of you who want an ICS facelift, check out the modded Zeam launcher.
Most recent recovery thread. - this recovery creates a md5 error on a backup's restore. Anyone know how to fix it?
ACL's known good recovery.
Good chance you will need to calibrate your touch screen. This thread covers that,and how to make it stick.
I may have found a launcher that is more lightweight than Zeam from what I can tell. I am running Lighting Launcher, and am quite happy. Seems to have an even smaller memory footprint, which is great for phones without much memory.
Swapper2 app. This is an interesting thing I found the other day. It allows you to use your SD card for swap (Virtual ram). I did verify that a 64mb swap file (did not test swap partition) can work on our phones. I would love to hear some feedback from people who might be interested in playing with it. I would suggest a Micro sd card with a high random read/write speed. Here is a guide that is already made if you want to use a swap partition rather than a swap file. It will probably wear out your sd card faster, but sd cards are cheap these days. Also note that SD storage vie USB may not work if you use this mod.
Update.
I got out my 32gb high random speed sd card today, and I whipped up a swap partition according to the guide above. I bumped the swappyness setting to 100. I was in a generous mood, so I lopped off 1gb of space for swap (256mg would have probably been a better choice). I did get a name error when I enabled it, but it seemed to work just fine. The swap space of 1gb showed up by the free command, and the swap space showed use after I ran a few apps. It is a subjective observation, but I think multitasking is a little smoother. I plan on leaving it setup like this for now.
{
"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"
}
I did manage to max out the cpu, and crash the system resulting in a reboot. I was running two gps apps, and two music apps, and two or three other apps all at the same time (abit poorly though). It might not have liked having multiple apps access the same resources.
Here is a handy app for rebooting the phone quickly, and entering into recovery.
Possible way to disable the proxmity sensor for people who have bad ones causing a non-waking screen here. Credit.
*Bonus for Sprint RHOD400 TP2 users*
If you are tired of the white HTC splash screen here are two nbh files you can flash just like a rom from the SD card. They should only touch the splash screen. Everything else is left alone. Flash one, or both in any order. These probably work on other Rhod phones, but I have no way to test them. So no screaming if something gets bricked. Based off the work in this thread. Reported not working on RHOD100 by this post. Reported working on RHOD300 here.
If you know of an image (480x800 res) that is even more amazing than these, and you feel it would be a good replacement drop me a link to it. If I love it, it will make it to the first post. Otherwise I might just whip one up special for you for contributing.
Primary
Secondary
As of 3-25-13 I have moved onto the EG4G/SII phone after reading about it and SERO legacy at Howardforums.
I will stop in from time to time, and if I am given a newer kernel I will post it. However I will no longer be using this phone.
So long, and thanks for all the fish.
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Slipdoozy said:
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Click to expand...
Click to collapse
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
wizardknight said:
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
Click to expand...
Click to collapse
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Slipdoozy said:
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Click to expand...
Click to collapse
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
wizardknight said:
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
Click to expand...
Click to collapse
im not happy with google selling my info so i refuse to give them any space on my phone lol
i tried the modded zeam all the ways i could think of, before flash, after flash, through adb didnt matter. maybe corrupt apk?
no worries. ill try to redownload it and try it your way with launcher2 first
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Slipdoozy said:
i tried the modded zeam all the ways i could maybe corrupt apk. before flash, after flash, through adb didnt matter.
no worries.
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Click to expand...
Click to collapse
Be ok with loosing the money. Some people have reported that they didn't get the unlock info, and the dev for that is next to impossible to get to respond.
You might check this thread. Not sure if they got it working.
Most of the credit goes to Stinger22. The man is kicking some serious code butt!
I would try re-downloading the apk. I was able to install it with a adb install. Not sure what else it could be. Did you hold your tongue just right while dancing madly during the install?
Slipdoozy said:
im not happy with google selling my info so i refuse to give them any space on my phone lol.
Click to expand...
Click to collapse
You do realize where Android is coming from... Right? lol
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it... Glad it did not get forgotten!
Zoombar!!
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Caldair said:
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Click to expand...
Click to collapse
HAHA. I didn't think the zoom bar would be the selling feature of this rom, but I am glad you are happy.
arrrghhh said:
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it.
Click to expand...
Click to collapse
Didn't know who did the base work. - Gave credit in the post.
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
CodaHighland said:
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
Click to expand...
Click to collapse
Wow. I had no idea that the zoom bar was so popular. Just doing what we can to keep the phone going.
Thank you so much for your hard work (especially fixing zoom bar!!!.)
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
Yes, overclocking is supported. This should be the same as 3.3.6. I believe the frequency range you can choose from is 122-825. Download your favorite overclocking app from the market, and have at it. I use quick cpu overclock lite.
*edit. I think we have some new governor options. Link for descriptions.
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Slipdoozy said:
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Click to expand...
Click to collapse
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
wizardknight said:
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
Click to expand...
Click to collapse
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Slipdoozy said:
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Click to expand...
Click to collapse
I am assuming that you mean OMGB by ACL's rom. To the best of my knowledge there is no way to port the feature without building your own kernel. It is my understanding that the 3.x kernels (what we use) are not compatible with that rom. OMGB userland is no longer receiving updates, so unless another dev adopts that rom it will never work.
I will take the 1% credit for this rom. I have done behind the scenes, packaging, some Bluetooth mods, and testing stuff. The other 99% goes to everyone (esp Stinger22) who has worked on it before me or with me.
On the phone that the zoom bar is not working, did you download that rom zip before or after 11-3? I didn't change the file names or links with the last update. You might try downloading the perms file at the end of the post, and installing that. Otherwise I would re-download, wipe, and reinstall.
If you are still having trouble let me know, and I will go check the zips to make sure that something didn't get busted in the last round of updates.
As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
What is CarbonROM?
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-PIE
-HALO
-Floating Application windows (long press app in recent apps list)
-Lock screen rotation is back
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
*not all features are available on the A100 tablet.
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"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
Download the ROM
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup device as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your device in settings.
Change Log
8.01.13-B1:
initial build for experimenting, didn't boot.
8.01.13-B2:
Next try, boots, SystemUI crash makes it unusable, no nav/status bars
8.02.13:
WiFi works, SystemUI persistent crashing still makes device unsable.
8.02.13-B2:
BT, WiFi, sound all work, persistent SystemUI crashes still occuring.
8.03.13:
All works, SystemUI crash fixed, PIE crashing, battery mods missing, Torch doesn't work.
8.03.13-B2:
All works, Torch works
8.03.13-B3:
Fixed PIE crashing, fixed missing battery mods. Rom is now fully operational.
FAQS
If you didn't read the bugs list below, go down and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to use this build(s) as a base for my ROM, or I want to host/re release it in another country/forum, can I?
A. You may, but only if you send me a PM about it first. I've had a bit of trouble with people taking credit for my work, and I'm getting sick of it. I don't mind sharing and whatnot, but taking my build, adding a build.prop tweak and releasing it on another forum with no mention of my name is not acceptable. As for re releasing on another forum, you may if you just shoot me a link to the post about it, I would rather you link directly to this thread if possible. For those posting in forums of other languages (I know some users might in Russia, for example, use my ROMs) feel free to post for your native languages, and please include a link here also.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, thats basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. I'm not going to write a guide, I did write one for CM9 which is 99.99% still a working guide aside from source urls for updated jellybean. Otherwise there are plenty of very well written guides on how to build ROMs, individual questions about build it can be asked here if you wish as this is a development thread.
Q. Can I use -insert kernel name here-?
A. You can probably use any kernel you want, but WiFi and such won't work. If you don't mind no WiFi feel free to use any kernel that will boot.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyo urass.zip"
Bugs:
MIC doesn't work
Camera crashes when you change resolutions
WiFi may not connect after being turned off, needing a reboot to come back up
Google Search doesn't work (no MIC)
Headset MIC also doesn't work
ROM may get stuck booting, powering off and on will have it boot again, not sure where this is coming from.
More, I'm sure.
Downloads:
Please visit http://pio-masaki.com for all my ROM builds
CARBON-JB-UNOFFICIAL-20130803-2330-a100.zip
WHOA BUNDY! This ROM is amazing! Finally some 4.2.2 action on the A100. Thanks!
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
MrCubbins said:
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
Click to expand...
Click to collapse
Actually, try a headset, or plug then unplug headphones, it works on the thrive for audio to get working properly, may work here too, they use the same audio system, drivers and libs.
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
MrCubbins said:
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
Click to expand...
Click to collapse
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
pio_masaki said:
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
Click to expand...
Click to collapse
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
MrCubbins said:
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
Click to expand...
Click to collapse
Well as I said unless it was reported (to me) I wouldn't have known. Hardslog wasn't reporting issues or fixes to me so I never knew it happened or how it was fixed.
The mic should be fixable, and yes it works on the thrive, so its likely a minor routing issue on the vangogh vs Antares or Picasso boards. Sound is my weakest point though, I always have troubles with it for some reason.
As for pie, there's options for all kinda shiz in there, just gotta go through them all and restart systemui to make them active in some cases. That bar is, I think, just decoration, though.
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
AngryManMLS said:
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
Click to expand...
Click to collapse
I'm just curious why anyone
A: uses the crappy camera on these things for anything but Skype
B: bothers changing the resolution of the already low resolution cameras
The kernel included is already modified just hasn't had the juice turned on yet. I'm not a fan of his kernel for my personal device, it never got along with it. If you venture into its settings you'll notice it has some extras in governors and io, no longer stock CM.
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
AngryManMLS said:
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
Click to expand...
Click to collapse
I think he used ezterrys kernel, why he chose to over the godmachine kernel you'll need to ask him about lol. It was a nice kernel for sure, but my a100 just didn't like it. My thrive kernels love mine but hate some others, such is electronics I guess.
I'm still testing the kernel for when the juice is turned on so its a pretty basic kernel otherwise, bit it should wake up real nice when its let loose.
Looking over the notes from several of hardslog's ROMs he's mentioned they have used godmachine kernels (or as I mistakenly called them "Linuxsociety"). No idea on the latest ROM that he's released since there's no mention. Let me know if you need to me to test any kernels here. My A100 is ready.
Well the kernel has some odd issues, for one lulzactive seems to just stay at top speed, it doesn't seem to scale at all. In the overclock enabled builds anychanges to min/max speeds will result in no deep sleep, the kernel stays awake at all times. Not sure whats causing either of those, lulzactive can be gone over but why the speed change locks the system awake I have no clue.
I really wish I knew what I was doing with kernels lol
Edit:
Vote, who thinks I should just update the linux society/god machine kernel to 4.2 and leave it at that? lol
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
AngryManMLS said:
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
Click to expand...
Click to collapse
The deep sleep issues are only on the overclock enabled kernel that I use, it shouldn't appear in the released build, it only shows up if min/max speeds are changed from stock. Scaling issues appear only in lulzactive, its defaulted to interactive so unless you change it, its scaling properly.
I'm not using the ezterry or god machine kernels, so its a problem unique to mine I think.
It uses cache or it wouldn't be booting at all, and you shouldn't back that up anyways I think twrp has some bugs no one ironed out and its causing oddness with older devices.
Oops. I thought you meant godmachine's kernel had those issues. My bad. I should read better next time. :laugh:
Also checking CYANOSAKI_FLEX_V2.0 the kernel it's using believe it or not is by ezterry. SetCPU defaults to interactive on this for me as well running at 1.5 ghz max speed, 312 mhz minimum. No idea if hardslog has done any mods/changes to the kernel however. Run perfectly fine on my A100. :good:
And you are right about cache let alone the TWRP bug. Just finished wiping and restoring my CarbonROM backup by the way. Successful swapping from 4.2.2 to 4.1.2 and back via TWRP backups.
Ugh I hate kernels, and I hate working IN them even more. But, it's coming along. It'll basically be the GM kernel all over again when I'm done lol.
So far vs the source I began with:
GPU/CPU/system speeds are tuned a little more, voltages tuned a little more
Adding in those missing governors, like Smartass and lagfree.
Converted/updated to BCMDHD from BCM4329
OC up to 1.5, UC to 216
I'm building this to include with my 4.2 builds, and I suppose I could just release a flashable version, it may even work on 4.1, who knows.