Develop Bugs

[Q] ics-deck-inc vs Evervolv vs OMX?

I've been following OMX and ics-deck-inc and I'm wondering which people think is better.
EDIT: Since I posted this, the Evervolv ICS ROM (posted on Twitter only) has gained popularity. It was the first to bring partial camera support, and although ics-deck has since added it, it seems most new features show up in Evervolv first. OMX is also fading away into obscurity.
These are my impressions based on the comments...
ics-deck-inc has been updated more recently (12/25), while development on OMX seems to be at a standstill (going on almost a month). I'm assuming the OMX standstill was related to the holidays though, since before that it was being updated very often.
EDIT: ics-deck-inc is now up to Alpha 5 as of this edit, while OMX is still at a standstill. It seems from this post that there is only 1 person working on OMX
OMX seems to be more further along, but maybe it's an illusion due to the fact that OMX has a much more detailed change log and explains the updates much more clearly (i.e. ics-deck-inc seems to be in "aplha1" still even through I know there have been a few updates)
EDIT: ics-deck-inc and Evervolv have far surpassed OMX. Personally,I prefer Evervolv, but I go back and forth between it and ics-deck-inc.
I see a lot of talk in the comments for ics-deck-inc about having to install Ext4 and Incredikernel, which adds more work for me and a higher chance of messing something up. I don't know about Ext4, but OMX already includes Incredikernel at least (although neither of them explain why I need Ext4 or Incredikernel).
EDIT: ics-deck-inc, Evervolv, and OMX all include incredikernel.
ics-deck-inc has a "Calendar fix" posted but I see a lot of commenters still having problems. Not sure whether or not this is a problem in OMX, but I haven't seen many people complaining about it (at least not lately).
EDIT: It's actually a lot simpler than that calendar fix... you just need to do this and all is well. There's also a fix for exchange calendar sync issues posted a little later in this thread
ics-deck-inc lists Wimax as something that's broken, but since when does the Incredible have Wimax anyway? Anyone know what the deal is with that?
EDIT: It seems this is there because the developer makes ROMs for other devices as well. Inc uses can just ignore it
So most of the above comments are obsolete at this point, but you can still feel free to use this thread to discuss changes and such. There is a separate feedback thread somewhere, but (a) that's just for deck, and (b) this is more about discussion than feedback.

I can just wait

demarcmj said:
I've been following OMX and ics-deck-inc and I'm wondering which people think is better.
These are my impressions based on the comments...
ics-deck-inc has been updated more recently (12/25), while development on OMX seems to be at a standstill (going on almost a month). I'm assuming the OMX standstill was related to the holidays though, since before that it was being updated very often.
OMX seems to be more further along, but maybe it's an illusion due to the fact that OMX has a much more detailed change log and explains the updates much more clearly (i.e. ics-deck-inc seems to be in "aplha1" still even through I know there have been a few updates)
I see a lot of talk in the comments for ics-deck-inc about having to install Ext4 and Incredikernel, which adds more work for me and a higher chance of messing something up. I don't know about Ext4, but OMX already includes Incredikernel at least (although neither of them explain why I need Ext4 or Incredikernel).
ics-deck-inc has a "Calendar fix" posted but I see a lot of commenters still having problems. Not sure whether or not this is a problem in OMX, but I haven't seen many people complaining about it (at least not lately).
ics-deck-inc lists Wimax as something that's broken, but since when does the Incredible have Wimax anyway? Anyone know what the deal is with that?
Has anyone out there used both RECENTLY and have some thoughts?
Or does anyone who has only used one or the other want to agree or disagree with any of my impressions above?
Click to expand...
Click to collapse
I've only used OMX. I got hooked on it, but unfortunately just flashed back to CM7.1 today. In OMX, calendar does not sync with google. Wifi tethering works. Cam no work. Can't use phone as external storage when connect to computer. Also, the ring tones and volume controls are all messed up: phone never rang, just vibrates. When playing pandora, sound is very low, even at max setting. Headphones are not recognized. When I connected to bluetooth in the car, i could make a call and talk over the bluetooth, but pandora or other media would not play through bluetooth.
Unfortunately it sounds like OMX will not be getting another update any time soon. And CM9 is probably still another several months away for INC, if they release it at all. So....looks like i'm stuck with stupid CM7.1 (or maybe MIUI) until i get my tegra3 ice cream phone!

I have been running ics-deck-inc since yesterday morning and here are some things I can tell you:
-Well, first off ics-deck-inc got updated a couple of days ago with loads of fixes including the camera. There are still some strange issues with the camera, but hey, it works.
-As far as incredikernel, ics-deck-inc already has it in the ROM. Therefore you don't have to flash it. There is a new incredikernel from 1/2/2012, while the one in the ROM is from December. Flash the new one if you want, but you don't have to.
-My calendar has worked without issue since I installed it. I think the issue is that calendars from Exchange and such don't sync with it.
-I think the Wimax thing is for another phone and not the incredible.
-Bluetooth works great. Syncs up with my head unit in my truck just fine. Pandora over bluetooth works great as well. The only thing is I can't get the metadata to stream to my head unit.
Hope that helps.

Well, I'll put my own experiences in now that a couple people have replied...
A couple days after posing the question, CyanogenMod decided to stop working for me (as others have noted that it tends to do after a period of time) so I decided to give some of these ICS ROMs a try since I was going to have to reflash anyway
I started with the Evervolv 2.1.0 Preview3 build posted on twitter so far [twitter.com]) because it was the first one to have camera support, which was one of the things keeping me from making the jump in the first place. The Evervolv build worked great for me. There was the occasional force close, but that is to be expected.
Then ics-deck-inc was updated to Alpha 4 yesterday to include, among other things camera support. I decided to move to deck since many people had noted that it was a bit better all-around than Evervolv. And now that it had camera support, there was no reason not to switch.
A few notes:
As awesomeo3000 pointed out, incredikernel is included. It's not the most up-to-date, but nobody has given any compelling reasons that you absolutely need the latest. (this was the case with Evervolv and OMX also)
I haven't really noticed a significant difference in battery life over my other ROMs, but that is probably because I am pretty much always around a charger so I don't really notice.
ics-deck comes with the Trebuchet (CM9) launcher, which is essentially stock ICS with some enhancements. It allows things like changing the # of homescreens, resizing any widget (stock only allows some), and other tweaks that are very useful but at the same time won't bother anyone who wants pure stock. Unfortunately, there seems to be two significant bugs in the app drawer in both the stock launcher and Trebuchet: (1) often times the next page of apps or widgets will show up in the background before you even attempt to switch pages, and (2) the launcher force closes very often when paging though the widgets. To alleviate that, I have switched to Nova Launcher which, like Trebuchet, is based on the stock ICS launcher but offers many helpful tweaks. I I still have had the occasional force close related to selecting widgets, but Nova also restores the long-press on the homescreen for widgets functionality, which can be used as another option if you experience force closes.
There are some small bugs that I have noticed here and there (like this one), but nothing really major, other than the well-known issues like calendar syncing and usb-host (see below). I also haven't yet tested a lot of things, like bluetooth for one.
My calendar syncing issues were solved by doing this: link. There was no need to replace the calender apps or anything like that. I can't speak for the Exchange Calendar syncing though. I can say that I was able to get an Exchange email account to work fine, but I don't use the calendar for that account.
As many people in the forums note, the multi-mount widget in the Android Market can be used to get usb-host support. Hopefully something will be built into the ROM in the future, but for now this should work. Alternatively, you can try what I use, the Samba Filesharing app. It's not as fast as USB, but wireless has it's own convenience advantages.
These are just some things I have noticed. There are some great features in ics-deck that I haven't even listed, and also some minor bugs. Alpha 5 is out now, only one day after Alpha 4, and I am excited to give it a try. I have to say that at this point I think they could drop the "Alpha." I think it could at the very least be considered "Beta" but that is just my opinion.
The important thing is this, anyone who is still using CM7 or any other ROM because they are waiting for an ICS ROM that is reasonably stable to use as a daily driver, I think ics-deck-inc has reached that point.

awesomeo3000 said:
Unfortunately it sounds like OMX will not be getting another update any time soon. And CM9 is probably still another several months away for INC, if they release it at all. So....looks like i'm stuck with stupid CM7.1 (or maybe MIUI) until i get my tegra3 ice cream phone!
Click to expand...
Click to collapse
You should definitely try ics-deck (see my post above)

Does MMS work? how partially working is the camera? can u at least take pictures and video

Evervolv has a build going as well, and they have 8 MP camera functional as well as USB mass storage. I'm going to try it now to see how it works.

TeeRom said:
Evervolv has a build going as well, and they have 8 MP camera functional as well as USB mass storage. I'm going to try it now to see how it works.
Click to expand...
Click to collapse
Yup, I mentioned Evervolv's ROMs. I can definitely say the 8MP camera is working (video and panorama modes still aren't). I haven't tested out USB storage yet but they swear it works.
Right now Evervolv is my favorite, but they seem to go back and forth (hence both in my signature). Best to keep an eye on both (I've given up on OMX, big time)
EDIT: I have now also added Evervolv to the title of the thread.

I've tried both ICS deck and Evervolv, but neither display my exchange calendar in the calendar app, which is a showstopper for me. Unfortunate, as I likes me some sammich. Exchange syncs fine, and sync settings claims the calendar is up to date, but the calendar app says "no calendars" for the exchange account. Anyone had any luck with this or have a workaround that you like?

Exchange calendar issue fixed in Evervolv by flashing the zip from from this tweet.

There is a fix for the exchange.apk with the evervolv ics rom peview 5. I have it posted in rootzwiki. i had someone try it out and they confirmed it did work. Just look for post by apophis9283 in rootzwiki

Actually no need to install ext4 on any of them. Its not required.
Sent from my Galaxy Nexus using Tapatalk

http://twitter.com/MongooseHelix
Here is a link to the next preview build from the evervolv guys.

ralph0015 said:
http://twitter.com/MongooseHelix
Here is a link to the next preview build from the evervolv guys.
Click to expand...
Click to collapse
Thanks... here is the link to the actual twitter post: https://twitter.com/#!/MongooseHelix/status/160269895265828864
Direct Link to the ROM: http://t.co/btSyQQ0o (MD5 Sum e193f7bf9eb83233bff02aa40bb84fd0)
Direct Link to their new gapps: http://t.co/m3DOolG8
Direct Link to their exchange fix: http://t.co/IIALIskJ
(Note: they say not to flash the new gapps if you're using the exchange fix)
P.S. I updated the main thread to add Evervolv to the title... I didn't realize I could do that when I last updated it. (I also updated some of the text in there)

demarcmj said:
Direct Link to their exchange fix: http://t.co/IIALIskJ
(Note: they say not to flash the new gapps if you're using the exchange fix)
Click to expand...
Click to collapse
Note that the exchange fix isn't needed for Preview 6 anymore, they apparently baked it in. Installed P6, latest gapps and ext4 mod from a full wipe and all is well.

"Haus" said:
Note that the exchange fix isn't needed for Preview 6 anymore, they apparently baked it in. Installed P6, latest gapps and ext4 mod from a full wipe and all is well.
Click to expand...
Click to collapse
Does this one have panoramic for the camera? its probably the only thing keeping me from using any ICS at the moment (I could care less about video.. I think I've taken 4 in since I had the phone.. and I got it day 1)

Not sure, i went back to cm7 atm only because certain apps fc with ics

I couldnt stay away from the ics goodiness. Went back to evervolv preview 6. Hope these devs get these market apps compatible with ics soon

I loved Evervolv p5 but it still felt unfinished to me. Didn't have any FCs but after running MIUI for so long, I was missing the customization options. I'll probably be back soon though...

alpha T-mob Vib WIFICALL JARMEZ RC4.2 base batmods, deodex, sync, FM rad, TWcal+more!

{
"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

[ROM] Jellytime Sosei 4.3

After the rather...disappointing way I departed and the resulting issues, I'm setting some things straight here and now.
1. No ETAs. Period. I don't want to see when will I fix or add anything.
2. No complaining. There's a line between reporting an issue and complaining. This line is crossed when it's reported more then once.
3. Requesting additions is fine, within reason. Keep it within reason, I'm not a real dev.
4. Using this ROM...this is where a lot of issues have come up, generally speaking, you can use this ROM as a base if you choose, however ASK ME FIRST. That's it! Everything could have been avoided if people had simply asked me before using my ROM and slapping their names on it then putting it out there. Please include some credit to waydownsouth, gh123man, randomblame and myself. For 4.3 Jellytime, randomblame in particular.
5. Hosting/mirroring. Please don't host or mirror this elsewhere, I will supply hosts for this ROM, I don't need more, and I prefer to keep track of how many users of a given build I have. Hosting elsewhere interferes with this. The only exception I can see is for our Russian/Ukrainian user community, my hosts may be slow there, or in other parts of the world. If you wish to host for another country, please let me know.
6. READ. For the love of all that is holy and great, READ the OPs, read at least the page before where your post will be. I will not answer questions already answered. If I respond, it may not be the nicest way I could do so. Please, save me, yourself, and everyone else the time and /facepalming and at least attempt to find the answer on your own. This is not limited to only this ROM, but anything you may wish to post about in this thread. Questions about CWM or TWRP don't belong here, but if they are valid questions that have something to do with this ROM, go ahead, after reading up on it.
7. Remaining on topic....well this one is loose. I prefer it to stay related only to this ROM, however I know things stray, and generally I'm OK with this, just try to keep it at least related to android. Or at least something related to something to do with on this planet.
Features:
Halo
PIE
Listview Animations (settings>display)
System Settings (CM)
Screenies:

Builds
Jellybean 4.1
Build 1 | Mirror
Kuroikaze-Sosei RC1
Kuroikaze-Sosei II B3 Final
Jellybean 4.3
Jellytime 4.3 - AFH | Jellytime 4.3 - DH
Gapps 4.1
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Gapps 4.3
gapps-jb-20130813-signed.zip
Change log 4.1
Build 1: Updated to 4.1.2 sources. Generally stock CM10. Everything works. I think.
RC1: Based on Black Bean AOSP sources now.
Sosei II B3 Final:
Seeder
AC!D audio
XLoud
Supercharged
Die Hard launcher
init.d memory tweaks
time killer killer mod
maximum overdrive mod
service preserver
transition animations
Final release.
Change log 4.3
Ported from Randomblame's Jellytime Build 7
Build 1: Unreleased, initial trials to get it running. Bootloops.
Build 2: Unreleased, boots, but runs badly, storage is broken, audio stutters
Build 3: Almost everything works now, fixed storage via init/ramdisk entries
FULL WIPE NO MATTER WHAT
Broken in 4.1
RC1 -
Auto Brightness
Hardware Rotation Lock Switch (use software settings, it's more flexible anyways)
GPS
Fixed -
HDMI audio should now work (again)
Switchable UI (tab or phab UIs now)
Bugs-
In tab ui the clock is messing it's rear texture on the homescreen, ie its not black there, its wallpaper instead. Doesn't interfere with anything, just a glitch.
Huge thanks to justjackyl for testing this out for me and reporting back on issues.
FULL WIPE NO MATTER WHAT
Broken in 4.3
Mic
?
Untested:
GPS
HDMI
Bluetooth
Dock
Bugs:
WiFi will not reconnect if it turns off, a reboot is needed. Turning off the always scanning option seems to help this.
Forcing GPU acceleration can help even out the framerate in some cases.
4.1 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. Get one for JB, you can try a 4.2 package, but is as yet unsupported.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Feel free to flash any kernel you want, but don't post about problems here until you use the kernel it came with first.
4.3 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. 4.3 ONLY! Don't report anything if you use anything but the gapps I linked from my site.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE Don't report ANYTHING if you did not flash 100% clean!
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation. It may blank out for awhile on the first boot, just leave it be.
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
I strongly recommend you download and install apps FRESH from the Play Store, and do NOT restore apps if possible. If you want, then go ahead...
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Do not report any issues if you:
Dirty flashed.
Restored anything with any app.
Don't use the supplied kernel.
Modified the ROM in any way prior to the issue coming up.
Did not read the entire post and noted what bugs are already known to exist.
Did not use the 4.3 GApps on my site which I linked right below the ROM download.
Can not report a bug issue without quoting Hawkeye because you skipped all of this.
Thanks:
waydownsouth
randomblame
gh123man
godmachine / linux society
justjackyl
das_webos_transformer / xbooow
Cyanogenmod
AOKP
Team Baked
The Team behind the AC!D audio engine
Plus more, I'm sure.

HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!

cdkg said:
HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!
Click to expand...
Click to collapse
Roflmao so says my biggest donater!
Sent from my SGH-T989 using Tapatalk 2

You are the freaking man!
Sent from my A100 using xda app-developers app

Go for it.

You sir, are why I miss my Iconia A100 . Hopefully can get a new one soon, miss the A100 community
Sent from my SCH-I500 using Tapatalk 2

A big thank you !!!!!!!!!!!!!!!!!!!!!
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...

rockthegod said:
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...
Click to expand...
Click to collapse
Thanks, and welcome to our little corner of XDA! Hope your new tablet is as good as mine has been to me
But really guys, randomblame did the hard work on this. I just got it running on the A100.

Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.

wild1z said:
Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.
Click to expand...
Click to collapse
Thanks for the understanding.
Also....new version with WiFi and some sound is up. Root seems to work to a point but I'll say its broken for now.
tapatalked from my A100 - Jellytime V7.7

unbelievable, I am bewildered by this topic! fantastic!

Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)

xitrumch said:
Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)
Click to expand...
Click to collapse
Thank you for the kind words, and no I'm not offended, there are certainly much better developers for sure, as I don't really consider myself a developer anyways. Most of this work has been done by randomblame and waydownsouth I just move it over for us on the A100, which isn't always easy I'll admit.

Version 7.8 is now available
Change log:
Root is now working as it should.
Open Super SU
Let it "install" binary (its already there)
Enjoy
External SD is now RW:
Fixed a permission issue in platform.xml to allow full read/write to external_sd.
Brightness control now works:
Auto brightness doesn't seem to work, manual brightness works. This was actually fixed in a previous release, and broke again, and is now working again.
Sound:
Sound works in some apps, but system sound is still broken, ie notifications, music, but some apps/games work, like angry birds now has audio.
Bluetooth:
Bluetooth has been proven fixed by a pairing, testing done by ntan97.
Still Broken:
Gallery/camera
Internal SD doesn't mount
Power LED is erratic, sometimes always on, sometimes always off
Home to wake: works when power led is ON, doesn't work while it is OFF
Video playback is still broken. Tested on stock player, dice player, mp4 and avi.
I'll be redoing the posts to be a little less confusing by moving things to change logs like this.

Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2

notsointeresting said:
Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9

I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin

notsointeresting said:
I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin
Click to expand...
Click to collapse
Yeah not a bug, that's the new 7" UI jellybean uses. Not sure why they killed the combined bar and chose a phone UI though. That's how the N7 will look too.
Oh edit there is a jb gapps but they're kinda broken, so flash them, ten icss gapps over it and itll work, that's how I do it. I'll add them into the OP sometime today, niece and nephew are staying with us for a few days so I'll be busy being the coolest uncle ever with all my modded consoles, devices and toys lol
tapatalked from my A100 - Jellytime V7.9

pio_masaki said:
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9
Click to expand...
Click to collapse
Bit off topic... but woah, thanks man. Just donated 5€

[ROM][NAND] [No longer being developed] GBX0* + 3.4.41 kernel - update 04/25/13

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.

any completely stable finished roms available?

hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3

lasuazo said:
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
Click to expand...
Click to collapse
ok thanks lasuazo ;--)

I guess omni and cm11
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice

thefusor said:
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
Click to expand...
Click to collapse
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.

Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!

I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.

Makshow said:
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
Click to expand...
Click to collapse
like i said in my first post, i do really appriciate the fact that people spend Alot of time cooking theese roms, and it easy for me to come along and moan about them, but i have found over the years that after using a custom rom for a couple of weeks or so, its like the ram seems to gradually get eaten away, the device gradually slows down, becomes laggy and ultimately unuseable (not just this fone, and not just me that says this). im not saying all are like this, just many i have used, mainly because they never get finished.
i am very open though to people suggesting that i am doing something wrong, and maybe you have picked up on that something.. you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
also thank you for the erase data tip for trebucket, i will try that.. i have not used the google now launcher yet, but i tried using miui launcher but when i went back to trebucket the lockscreen stayed as the miui lockscreen, which has happened on past cm roms, so i just deleted it.
just gets a bit frustrating when you spend hours getting everything working/setting up personalisation, then the phone just seems to start getting worse day by day, but maybe like you say, its cos i "dirty flashed"?

linuxguy42 said:
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Click to expand...
Click to collapse
i did think that, and im sure you are right, but i have had every app/folder/widget dissappear twice now, then, randomly over several restarts, some widgets/apps will replace themselves over the top of the new ones i have just newly placed there.. strange, but i have came across this before on cm roms, so im sure there is a bug there somewhere, even if it is not too common..

jmpcrx said:
you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
Click to expand...
Click to collapse
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
the device gradually slows down, becomes laggy and ultimately unuseable
Click to expand...
Click to collapse
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!

Welll here are some tip which have helped me
jmpcrx said:
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Click to expand...
Click to collapse
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .

Makshow said:
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Click to expand...
Click to collapse
ok thanks, i cleared the data in trebucket, and started again with placing apps/widgets on home screen, and i also have deleted the hacked version of adobe flash that you install with dolphin browser, and, supprisingly after a couple of days of testing, my apps/widgets are not deleting themselves, the phone is significantly less laggy, and i have had no switch offs, so, im very pleased with that! so id suggest against downloading that version of flash player with this rom..
thefusor said:
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Click to expand...
Click to collapse
some good tips there, thankyou, i havent tried any of them yet, but i will have a go at some of them and see what happens.. thanks thfusor..

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.

etherfish said:
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
Click to expand...
Click to collapse
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice

jmpcrx said:
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
Click to expand...
Click to collapse
Well, you learn by doing, I believe. Also, I have a classy - for a flip phone - Motorola Razr2 v8 kicking around I can always put my SIM into if I've managed to hose my captivate glide. Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions. So, a number of things have piqued my curiosity.
So, first of all, this surprised me in the logs:
Code:
I/Launcher( 2263): onCreate(): product model family:U1 product model : GT-I9221
I'd always wondered why I had an SGH-I927 when other phones, like the remarkably similar Galaxy R, are GT-I9103. Is/was GT-I9221 an internal reference?
Also, there are other inconsistencies, for example:
Code:
D/RILJ ( 426): [1718]> REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ ( 426): [1718]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
If you jump into the debug/field test menu system, (dial *#*#197328640#*#* ) you can bring up the list of neighboring cells in both GSM and WCDMA modes... So, why is the request marked not supported? Furthermore, why didn't samsung disable the request in the first place if they went to the trouble of disabling it from working. I imagine this has a reason, but I doubt it's a terribly great one.
And the FM receiver? I do believe our broadcom BCM4329 is a bluetooth+wifi_in_an_sdcard (well, SDIO really, but still, not pci-e and not usb.) and has an FM receiver built in, but it's omitted and hidden?
Code:
W/AudioPolicyManager( 112): FM radio recording off
Oh, the conspiracy theories. And then there's the weird lines you discover if you dump the string identifiers from /system/bin/drexe!
For example, these lines are all sequential:
Code:
broadcast -a android.provider.Telephony.SECRET_CODE android_secret_code://767*3855
InvokeOemRequestHookRaw broadcast factorst OK
InvokeOemRequestHookRaw factorst fail %d
/system/.configure.txt
(what's with /system/.configure.txt???)
Do not type 767*3855 into your phone. It's the factory wipe code or possibly part of it. I do believe drexe is the DataRouter you often see spamming the logs with:
Code:
E/DataRouter( 107): usb connection is true
E/DataRouter( 107): DSR is ON. Don't send DTR ON.
And we find these strings in drexe:
Code:
__initialize_usb_ipc
/data/.usb_stream
usb connection is true
InvokeOemRequestHookRaw usbstatus true is success
oh, and:
Code:
pipe failed (%s)
fork failed (%s)
child pid = %d.
execute sh.
system/bin/sh
execl fail %d
What do you think? Why does drexe seem to have code to support and start a shell? Well, if nothing else, thank you for reading.
P.S. I don't suspect anything the least bit conspiracy like, malicious, or devious. I've worked for some huge companies; i don't think it'd be likely.

etherfish said:
Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions.
Click to expand...
Click to collapse
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...

Makshow said:
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Click to expand...
Click to collapse
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
Other than those couple of things its been great!
im HOPING down the road for an un-buggy or at least minimally buggy version of 4.4. well see what happens with that i guess.

Some help
Pawprints1986 said:
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
.
Click to expand...
Click to collapse
well i always say stock is best cause it IS optimized however there are things like keep and total Google integration that i like so i updated to kit kat
for screen caps if they dont work i could maybe suggest an application called super manager its pretty loaded it has screen cap and may even give you prox sense wake up for device.
also customizing the drawer hmm.. i guess you could try xposed framework but please be careful and make a backup before
as for who texts you and the content of the text you could try dash clock its able to do a lot

hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock. I completely removed all the system bloat with link2sd, uninstalled all att crap. Can anyone recommend me something since I feel the ram consuption still to high... battery so far is doing kind of good almost as in crdroid
But i believe it can be improved. Any recommended settings or something else i can do? Already tried lite kernel but it gave me some issues. Rather keep stock. Any recommendations please guys. Also if you know a "ok google" like app or something as a swifty assistant would be nice. Please recommend. Thanks in advance

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
Hi,
well that depends.. on what you mean with "finished"
I have tested all (3 months ago) available ROMs for the Glide. IMO the best available ROM is PACman but as said it depends. I used pac_i927-milestone.1.RC1.4.zip for a long time (months) without having any issues besides Bluetooth Headset which is a general problem in JB and higher version). I have tried other PACMan ROM versions as well but the above one was the best of stability and battery life (in my case).
So it depends what features you really need or are a must-have for you. If you do not have bluetooth headsets I would recommend the above otherwise .. well I would recommend sediROM
Regards
xdajog
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
lasuazo said:
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock.
Click to expand...
Click to collapse
Haven't done that before but would be rooted ICS stock also ok for you?
If so:
--> search for thread ID 1994902 or search for: [ROM] Stock UCLJ3 Rooted, Deodexed, Zipaligned
(sorry not allowed to post links..)
Regards
xdajog