Develop Bugs

Please delete this thread

Sorry Villain rom is down at the moment if you are having trouble getting the wonderful FROYD 1.2.1 here are some links
http://villainrom.jeremygohblog.com/...ase-signed.zip
and
http://villainrom.desean.net/release...ase-signed.zip
These are both for Froyd 1.2.1
OTA Update: FroydVillain 1.2.2 "GPS really needs a kick in the nuts"
VillainROM Updater app finally makes a return to the FroydVillain platform.
New in this update:
•Framework fixes for the GPSLocatorService that fix an issue causing a hang/crash when GPS was obtaining initial fix and location update.
•CPUSpeed no longer supports a screen off profile. See below for details.
•Updated lib_htcril.so to improve GSM switching, -should- also fix the people experiencing GPS+GSM not working.
•Kernel updated to fix some regression bugs in the USB stack, ARM code issues and to prevent the camera app clogging the IO bus.
•All the different OC kernels are now in the OTA app, just enable experimental updates to see them.
This OTA update clears the dalvik cache, as there are updates to the framework, so naturally your phone will take longer to boot.
We no longer support the use of a screen off profile with the interactive governor. It's really not needed. While it may make some difference to battery longevity, the benefits far outweigh the downsides. We're talking -maximum- a loss of an hour, over using a screen off profile. However you get the added benefits of:
Being able to use anything with the screen off without losing performance. For example phone calls, listening to music, etc.
Time for a brave new world of thinking, folks. Get used to the idea that it's better for the governor to accomplish a task as quickly as possible, then clock back down.
The other switch in thinking, is this. It's time we stop trying to work around whatever bull**** problem that apps on the market introduce by being buggy, crap or poorly designed. If we find there's an app or a widget that runs your phone at top clock all night, well, start giving the developer ****. We're no longer going to try and work around issues introduced into the OS by bad applications. Developers need to start taking more responsibility or face people not using their apps anymore.
Screen off profiles are a nasty workaround for this problem and it's going to go away, at least in FroydVillain. Your phone's performance should not be at the mercy of whether the screen is on or not. Having many frequencies in the table is a false economy because, and especially with the

EXTRA
For any other details
IF ANY BODY NEED ACCESS TO THIS XDA ACCOUNT TO EDIT
i.e
pulser
ninpo
lenny
email for account details
[email protected]
[email protected]

neither links work....anyone got ANOTHER link we could use?
thanks

Mike, your links is borked:
Use this link instead: http://tinyurl.com/3a6r9u5

thanks for the links
hey jeremy
nice to see someone else from the Elf forums over here

Whoops.... hopefully one of team villain can log in and change top post
Sent from my HTC Desire using Tapatalk

Still down hopefully mcduck will get it sorted soon

anyone that haves the links of the kernels? i need a nice kernel, but can't find a link anywhere

Great work... I was doing fine until I tried one of the kernels... First boot should take longer... but how much longer? Mine's been on the VillainRom Loading screen for maybe 30 mins...
Cheers for the work...
Tom

tom3668 said:
Great work... I was doing fine until I tried one of the kernels... First boot should take longer... but how much longer? Mine's been on the VillainRom Loading screen for maybe 30 mins...
Cheers for the work...
Tom
Click to expand...
Click to collapse
30 mins is too long. Try reboot again, if still failed to boot up. Reflash again.
Sent from my HTC Hero using Tapatalk

Delete this thread

As per OP request, thead buried.

[NAND] Warbyte Donut for Kaiser - RLS04 Oct 21 - compcache and market! / General help

Sad news right before we end this year. Today (12-28-2010) I accidentally stepped on my Kaiser and though it endured like a champ it was too much to ask from the screen and it cracked. No more Kaiser for me so this project is coming to an abrupt end. If I find a Kaiser and it is flashable then I'll gladly continue and move on, hopefully on Froyo but until then I wanna thank all of those wonderful people who took part in this thread either by providing feedback, asking, helping or even just reading. It was a great experience. Happy new year to everybody!
What this is:
This is my personal attempt at a flexible, responsive, complete, and stable Donut release. My first release was based on Dzo's Odexed version and from there things have been evolving.
This thread has also been gathering some really interesting info so it might as well serve for helping anyone out there so feel free to look for any info you need or ask but please search before you do because the answer might have been given here or in another thread already. Feel free to contribute with any info or apps but please respect XDA's rules and respect other members. No keygens, serials, cracked apps, any request about it or any contribution containing them is allowed. If I miss any rule being broken (most likely due to my time constraints) then a moderator will catch you and ugly things will happen. You've been warned.
Thanks!
To thoughtlesskyle for his answers to many questions and help in the thread, Millence for his info about compache running as a service in VaniljEclair, elander, marcelotorres, albertorodast2007, and snake664 for his patience, interest, extensive testing, and much appreciated feedback. Thanks to anyone else involved and supporting this thread. If for any reason I forgot your name here I apologize, pm me and I shall make the necessary changes.
Why another Donut?
Edit: Even shorter version - One day things went very wrong for me when I flashed a stock ROM by accident that contained an original SPL 3.34. The process stopped halfways and rendered me unable to flash anything else on my phone. The last thing I was able to flash was an Eclair kernel that I edited to fit Donut.
I found out about Dzo's Odexed release and though it was great to say the list I soon realized that having an odexed version wasn't very helpful if you needed to change things. I went ahead and got all deodexed, changed, themed, updated, mixed, messed up, fixed again, zipaligned and all that good stuff.
Some work I would like to respect by encouraging you to visit, try, and support:
Incubus26Jc's Super FroYo
Zenity's Polymod 2.1D (Maintenance version)
Dzo's script for odexing and optimized build
Myn's Warm Donut (Support for Kaiser thread)
Jonasl's HTC_IME (HTC Keyboard)
Thoughtlesskyle's Not So Super Froyo (But looking Great!)
Last notes about the packages:
As of RLS04 there is an AE version (APKtor Edition) which does not contain preinstalled apps besides Helix Launcher and APKtor. It is configured to point to a repository I am currently hosting and that aims to contain this thread's favorite apps list.
The stock launcher is not included as I have never used it, you can however install it and use one of the custom and awesome looking updates from Incubus26jc's addons for Warm Donut.
There is no file manager included. That way everyone can use Market and install Astro or whatever suits their needs.
The included kernel was modified to fit a Kaiser, at 320x428, version is set to Donut, Panel Type 1, Key Map is normal, and Battery set to 1350. If you need something different please use Atools to edit it and match your needs.
There is no battery patch in sysinit.rc as I think it is unreliable based on the fact that several people get really different results. I prefer to go with editing the value in kernel set to the actual capacity of the battery.
The build is set to 143 DPI based on Zenity's research about 320x428 resolution.
Please be aware that there is some /data partition corruption depending on the kernel you use. I moved my /data to an EXT3 (EXT2 in the installer options) to help minimize this. Doing this might freeze your Kaiser when you slide the keyboard out depending on how fast your SD access is.
I generally don't have too much free time. I will try to be as helpful as time permits though I would like to rely on other people's knowledge to help each other as well.
Disclaimer:
I am not responsible for any damage to your phone you know very well we're all here to experiment and learn. If you need help with flashing ROM's, radios, and / or security unlocking please use the search feature of the forum. There is plenty of documentation that can guide you through the process.
Might be done / In progress / Included in release:
To do:
Resize images in some packages to fit a 120 DPI, QVGA resolution.
Change resources in apk's to match Froyo's look.
Experiment with a different wlan.ko hoping to fix wifi problems (reported by 1 user only).
Included in RLS04:
Compcache!
Custom script for loading compcache, values based on testing.
Custom services for persistent compcache, enable and disable.
Custom service for persistent 2G only networks.
Zipaligning diagnose script. Mainly for me as I am a zipaligning freak.
Included in RLS02 and RLS03:
More stability in Android core apps. Avoid force closes.
Fix Android Terminal Emulator force closing (Package does support a soft keyboard).
Include SMS Popup, enhances default Messaging app. Fix force closes.
Include HTC Keyboard (Mod by an XDA member). Fix force closes.
Switching between 2G and 3G. Can set "use only 2G networks".
Cell based location. Tested with OsmAnd, GPS off.
Working SIM lock.
Addons - Fat free blue Donut theme
Thoughtlesskyle gave us this amazing present: a ported theme from his Fat Free Froyo release. It brings a very refreshing (and black status bar) look. Tested on RLS04 and working great! Thank you!
Downloads:
Fat free blue Donut theme
Addons - Bugless Beast Sound Recorder
A recent discussion that started over at the Warm Donut thread. The stock Sound Recorder app does not have a GUI and it is just a group of functions that other programs can use. Bugless Beast's author modified the original app giving it a nice GUI. Get it here as an update for your build!
Downloads:
Sound Recorder Update
Release 04 - The Redeemer on Steroids
I consider RLS03 to be a very solid build so I am trying to get all those final touches we all wish for sometimes. This release addresses two issues: compcache and default 2G networks. Everything else is RLS03.
Compcache:
After some serious testing with my own device I came up with three different settings. There is a disk size of 16 MB, 24 MB, and 32 MB which to me are what work better in our Kaisers. RLS04 has compcache enabled with a size of 24 MB as a default setting. This is a balanced compromise between compressed caching and available RAM for everything else. After each restart the compcache settings will kick in automatically (if not disabled manually) after exactly 4 minutes, it will reserve the specified disk size or as much as it can if the total amount is not available. If you need to change some settings I included a modified script, by executing this you will be changing the persistent service settings, very simple and straightforward. If you need to change something, bring up the terminal, give yourself super user permissions (type su and press enter) and do any of the following. Please note that a what is after the # character on the same line is just a comment.
Code:
# Stop compcache immediately, toggles to enabled on reboot
compcache.sh stop
Code:
# Disable compcache, it will not load on subsequent restarts
compcache.sh disable
Code:
# Enable compcache with 16 MB disk, changes reflected after restart
compcache.sh enable16
Code:
# Enable compcache with 24 MB disk, changes reflected after restart
compcache.sh enable24
Code:
# Enable compcache with 32 MB disk, changes reflected after restart
compcache.sh enable32
Because compcache does promote data corruption I must emphasize: Create a /data backup. You'll be happier if corruption happens and you need to reinstall.
Default 2G Networks:
RLS04 sets 2G networks only as a default settings after restarts which is what works best for me and several people. After a restart you can change the setting in Wireless controls -> Mobile networks as always but 2G will persist on reboot. If you need to change this setting to have 3G as a default setting after a restart then bring up terminal emulator, give yourself super user permissions (type su and press enter) and do any of the following. Please note that a what is after the # character on the same line is just a comment.
Code:
# 3G networks as default
set2g.sh disable
Code:
# 2G networks only as default
set2g.sh enable
Warnings:
As with previous releases, be careful if you use QVGA, haven't tested it on that resolution, some important things might not fit well, like the numbers for unlocking your SIM
Known Issues / Notes:
None so far.
Additional apps included in the package:
Normal Edition:
Weather Wiget (Provides digital HTC like clock)
HelixLauncher 1.2 (Replaced ADW Launcher because current version drains battery faster)
HTC Keyboard (With working calibration. Long press on a text field to select as default or check "Locale & text" settings)
SMS Popup 1.0.9
Rogue Tools 1.1
Keep Screen 1.7
Android Terminal Emulator 1.0.17
Market Enabler 3.0.8
XScope GL Lite 5.34
APKtor Edition:
HelixLauncher 1.2
APKtor 1.0.8.7
Downloads:
Donut Deodexed RLS04
Donut Deodexed RLS04 APKtor Edition
Release 03 - The Redeemer
This release is what RLS02 should have been. More stability, working gps, wifi, bluetooth, camera, cell based location, and SIM lock. I ran it on NAND, works great, still with it I had some normal and expected /data corruption which reset my wallpaper. I've been running it with /data on EXT3, there is not a performance hit that I notice and I would advise the same as this helps with the partition corruption. Just in case keep a /data backup handy.
Warnings:
As with RLS02, be careful if you use QVGA, haven't tested it on that resolution, some important things might not fit well, like the numbers for unlocking your SIM
Known Issues / Notes:
Setting "Use only 2G networks" works now but it does not survive a reboot. It enables 3G as default. To solve this if you need to reboot your phone and you prefer to be in 2G you need to check the setting again.
Additional apps included in the package:
Weather Wiget (Provides digital HTC like clock)
HelixLauncher 1.2 (Replaced ADW Launcher because current version drains battery faster)
HTC Keyboard (With working calibration. Long press on a text field to select as default or check "Locale & text" settings)
SMS Popup 1.0.9
Rogue Tools 1.1
Keep Screen 1.7
Android Terminal Emulator 1.0.17
Market Enabler 3.0.8
XScope GL Lite 5.34
Downloads:
Donut Deodexed RLS03
Release 02
Known Issues / Notes:
Obsolete. I am no longer working on this particular package.
Additional apps included in the package:
HelixLauncher 1.2 (Replaced ADW Launcher because current version drains battery faster)
HTC Keyboard (With working calibration. Long press on a text field to select as default or check "Locale & text" settings)
SMS Popup 1.0.9
Rogue Tools 1.1
Keep Screen 1.7
Android Terminal Emulator 1.0.17
Market Enabler 3.0.8
XScope GL Lite 5.34
Downloads:
Donut Deodexed RLS02
Release 01
Known Issues:
Obsolete. I am no longer working on this particular package.
Additional apps included in the package:
ADW Launcher 1.1.5
Rogue Tools 1.1
Keep Screen 1.7
Android Terminal Emulator 1.0.17
Market Enabler 3.0.8
XScope GL Lite 5.34
Downloads:
Donut Deodexed RLS01
Release screen captures:
{
"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"
}
Thoughtlesskyle fat free blue Donut theme screen captures on RLS04:

wow, first time I get to post first post, what an honor, jejeje, anyways this is looking good I'll download and try it, the timing couldn't be better as I am using myn's warm donut and after messing around with njtr2 battery mods somebody told me that I'll have troubles because of the sysinit.rc had some codelines to set it at 2000mah so I had to change that, anyways since I messed both system and data so much I was going to reinstall everything, but now I'll try yours first. thanks

elander said:
wow, first time I get to post first post, what an honor, jejeje, anyways this is looking good I'll download and try it, the timing couldn't be better as I am using myn's warm donut and after messing around with njtr2 battery mods somebody told me that I'll have troubles because of the sysinit.rc had some codelines to set it at 2000mah so I had to change that, anyways since I messed both system and data so much I was going to reinstall everything, but now I'll try yours first. thanks
Click to expand...
Click to collapse
I am glad you feel honored, you must also know this is the first thread that I create and so I am even a little nervous about the reception. Oh I know what ya mean, I've been messing around with that famous sysinit.rc and trust me, it was a headache. Tried both a new battery that I got and my old messed up one, which drops to almost nothing in 5 mins. In both cases, the battery seems to indicate an accurate current charge and recharge. Good luck with everything, and please let me know what you think

weird, I'm trying to download this from the link (mediafire) but after I click on the "click to start download" it stays on your download is about to start....

elander said:
weird, I'm trying to download this from the link (mediafire) but after I click on the "click to start download" it stays on your download is about to start....
Click to expand...
Click to collapse
Hmmm weird, just tried the link here. Works okay and starts. I had a couple issues some weeks ago when downloading from media fire. The server would not be found, it was okay later. Could I ask you to wait a little and try again? if it doesn't work for you I will try to have a mirror link as well.

thanks for such a fast reply, I told you what happened so you know, but I was going to wait anyways, (as some say patience is the key, lol) on a side note (and a little off topic as well) could you please tell me how did you manage to get rid of the battery settings on sysinit.rc, cuz I'd love to try the new battery kernel in my current installation (as it is pretty much broken anyways) as I wait for mediafire to "like me". thanks!

elander said:
thanks for such a fast reply, I told you what happened so you know, but I was going to wait anyways, (as some say patience is the key, lol) on a side note (and a little off topic as well) could you please tell me how did you manage to get rid of the battery settings on sysinit.rc, cuz I'd love to try the new battery kernel in my current installation (as it is pretty much broken anyways) as I wait for mediafire to "like me". thanks!
Click to expand...
Click to collapse
Sure thing. well, I guess this is gonna be a feared answer but the method is by hand. Grab an editor that does not mess up your ends of line. I use pspad for this kind of thing. the .tar file is just a compressed file you can open with winrar or 7zip for a free alternative. Open your sysinit.rc, look for the lines sys/module/board_kaiser_battery/parameters/battery_capacity, that is where the value is set. The most common builds I have seen have a #battery patch comment so you can just delete that section. Save your file, dump it back in your .tar file and install.
I have also used androidupdate.tar if you wanna make it an update instead of a reinstall, just make sure it is in the correct path. Should be the same path you see in androidinstall.tar.
One thing I gotta warn you, I have always been tempted to realign tabs and delete unnecessary whitespace. The last time I did that it resulted in weird wifi and bluetooth behavior, so be careful and only change what you need. Save a copy of your original file so you can always "update" it with the old one in case you mess something up accidentally. Patience, that works. Take a deep breath, watch some tv, then try again

Nice....
I must say it is refreshing to see someone doing something new with the Kaiser!!! I just may give this a whirl tomorrow!!! I'll chime in if I do......

i wanna try it....
let me download it first

@cnigro1279 There aren't too many new things with this, just trying to save people some time and work I have great love for the Kaiser, it's like a good old faithful friend. It just goes through several battery packs. Please give us some feedback if you decide to try it.
@fahkin Appreciate the interest

I´ve been messing with this build for a couple of hours and I must say It is great so far, the only issues I have are: the terminal emulator force closes, but it is not a big deal I just uninstalled it and downloaded it again from the market, and the second one is not really an issue but raher a matter of taste, I installed this with the recommended resolution 320*428 with a 144 dpi setting, thinking that maybe this time I´d get it to look less blurry than last time I tried such resolution, but it´s still the same, so I´m gonna try this with 240*320 and a dpi value of 117 (as I recall being able to fit almost everything onscreen last time I did it) so, I feel tempted to ask, What are the chances of getting a fix for 240*320 resolution? (myn´s warm donut has it I think) anyways great work, oh by the way I love the look on this one, it makes me forget about froyo (although if I could them the widgets to look like the froyo´s it´d be a dream come true,lol), overall very fast and stable (so far) build, with great looks and the fact that it is deodexed leaves rom for theming it the way you like it. thanks.

Thank you !
Thank you WarByte !
I will give it a ride on mine Kaiser

About resolution confusion
@elander
you can take a look at:
forum.xda-developers.com/showthread.php?t=667581&page=4
forum.xda-developers.com/showpost.php?p=7767902&postcount=3

Thanks for reporting!
@elander Thank you for reporting back. Yeah the clearest screen you can get is using the native QVGA resolution of the Kaiser, I might suggest trying a DPI of 121, that one looks great with that resolution. I could attach another kernel and an androidupdate.tar with the DPI setting, though you could edit the kernel with Atools and the included Rogue Tools app in the rom lets you change the DPI setting to anything you might want to try. After the change you just need to reboot. I got some apps force closing if already included in the package as opposed to installing them after the rom. Apparently I missed Terminal. I also thought about using Better Terminal since most builds have it and the one I am using doesnt let you use a soft keyboard. I am glad you liked the build By the way if you use a QVGA resolution your dialer is gonna look messed up, buttons over each other. Please check out a modified dialer for Warm Donut at http://forum.xda-developers.com/showpost.php?p=6402522&postcount=4080. This should work well with it.
@kljoki Please do and let us know how it goes, if there's anything I can help with I'll be glad to try my best.

ok, don't forget I'm using HaRET
The things which does not work on my Kaiser or I didn't have a luck:
- camera force closing (FC)
- terminal (ok, you just explained why)
unstable:
- wifi signal, I had a lot of system confusions and retries, in general it working
- WiFi Static
I was trying with panel 3,2 and 1 in default.txt,
and was thinking to flash an old radio as you suggested
but from your sig I can see we are using same radio versions.
Thanks.

Downloading... will try it later `cause i am really tired but thanks for the build anyway

WarByte said:
@elander Thank you for reporting back. Yeah the clearest screen you can get is using the native QVGA resolution of the Kaiser, I might suggest trying a DPI of 121, that one looks great with that resolution. I could attach another kernel and an androidupdate.tar with the DPI setting, though you could edit the kernel with Atools and the included Rogue Tools app in the rom lets you change the DPI setting to anything you might want to try. After the change you just need to reboot. I got some apps force closing if already included in the package as opposed to installing them after the rom. Apparently I missed Terminal. I also thought about using Better Terminal since most builds have it and the one I am using doesnt let you use a soft keyboard. I am glad you liked the build By the way if you use a QVGA resolution your dialer is gonna look messed up, buttons over each other. Please check out a modified dialer for Warm Donut at http://forum.xda-developers.com/showpost.php?p=6402522&postcount=4080. This should work well with it.
@kljoki Please do and let us know how it goes, if there's anything I can help with I'll be glad to try my best.
Click to expand...
Click to collapse
THanks for the tips, but I already knew how to work with resolutions and rogue tools/atools/nbheditor, thats why I said that I was going to try this with a 117 dpi/240*320 resolution as I know that most things, (including the dialer) fits the screen and also looks better/less blurry, what I meant is that I wanted to know if there was a chance for this to get fixed to fit in a 240*320/120 dpi, that's why I mentioned warm donut, (cuz somebody got most things including dialer fixed for a 240*320/120dpi and put up an android install), so that way we wouldn't need to use 320*428/144 dpi, as (in my humble opinion) it looks a little blurry. anyways thanks for everything so far this is in my top 3 list and this is only the beggining (rls1). kaizen!!!!

I just recently got the Kaiser, and have been trying out Android.
After messing around with most the ROMs, I must say, this one is stable and already has wifi and bluetooth working for me.
Thanks!

@elander Sorry about forgetting haret, I just way too used to nand. I know what you mean now and actually a couple days ago i was trying a lockbot demo and it wouldnt fit so i found a dpi that gave me almost the same QVGA look though blurry. I thought of resizing the dialer. You got me interested so I'll work on it. Test on my quasi QVGA and I'll rely on you for some actual final testing since i cant flash another kernel. Maybe later on we can get some froyo looking widgets a reality
@randomgoon Glad it worked for you. Appreciate your feedback.
@All i can confirm working radios: Nikki, 1.70 and 1.71. I have never gone below 1.65 and noticed almost no difference. Most people recommend a 1.65 radio.
--
Sent from my HTC Kaiser using Tapatalk.

Rollride! Good to see you here. Get some rest then let us know what you think. Hope you like it
--
Sent from my HTC Kaiser using Tapatalk.

[ROM] CarbonROM Linaro GCC 4.7/-O3 JB 4.2.2 Unofficial 8.03.13

As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
What is CarbonROM?
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-PIE
-HALO
-Floating Application windows (long press app in recent apps list)
-Lock screen rotation is back
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
*not all features are available on the A100 tablet.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00​

Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
Download the ROM
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup device as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your device in settings.
Change Log
8.01.13-B1:
initial build for experimenting, didn't boot.
8.01.13-B2:
Next try, boots, SystemUI crash makes it unusable, no nav/status bars
8.02.13:
WiFi works, SystemUI persistent crashing still makes device unsable.
8.02.13-B2:
BT, WiFi, sound all work, persistent SystemUI crashes still occuring.
8.03.13:
All works, SystemUI crash fixed, PIE crashing, battery mods missing, Torch doesn't work.
8.03.13-B2:
All works, Torch works
8.03.13-B3:
Fixed PIE crashing, fixed missing battery mods. Rom is now fully operational.

FAQS
If you didn't read the bugs list below, go down and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to use this build(s) as a base for my ROM, or I want to host/re release it in another country/forum, can I?
A. You may, but only if you send me a PM about it first. I've had a bit of trouble with people taking credit for my work, and I'm getting sick of it. I don't mind sharing and whatnot, but taking my build, adding a build.prop tweak and releasing it on another forum with no mention of my name is not acceptable. As for re releasing on another forum, you may if you just shoot me a link to the post about it, I would rather you link directly to this thread if possible. For those posting in forums of other languages (I know some users might in Russia, for example, use my ROMs) feel free to post for your native languages, and please include a link here also.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, thats basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. I'm not going to write a guide, I did write one for CM9 which is 99.99% still a working guide aside from source urls for updated jellybean. Otherwise there are plenty of very well written guides on how to build ROMs, individual questions about build it can be asked here if you wish as this is a development thread.
Q. Can I use -insert kernel name here-?
A. You can probably use any kernel you want, but WiFi and such won't work. If you don't mind no WiFi feel free to use any kernel that will boot.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyo urass.zip"
Bugs:
MIC doesn't work
Camera crashes when you change resolutions
WiFi may not connect after being turned off, needing a reboot to come back up
Google Search doesn't work (no MIC)
Headset MIC also doesn't work
ROM may get stuck booting, powering off and on will have it boot again, not sure where this is coming from.
More, I'm sure.
Downloads:
Please visit http://pio-masaki.com for all my ROM builds
CARBON-JB-UNOFFICIAL-20130803-2330-a100.zip

WHOA BUNDY! This ROM is amazing! Finally some 4.2.2 action on the A100. Thanks!

This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.

MrCubbins said:
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
Click to expand...
Click to collapse
Actually, try a headset, or plug then unplug headphones, it works on the thrive for audio to get working properly, may work here too, they use the same audio system, drivers and libs.

Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!

MrCubbins said:
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
Click to expand...
Click to collapse
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol

pio_masaki said:
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
Click to expand...
Click to collapse
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?

MrCubbins said:
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
Click to expand...
Click to collapse
Well as I said unless it was reported (to me) I wouldn't have known. Hardslog wasn't reporting issues or fixes to me so I never knew it happened or how it was fixed.
The mic should be fixable, and yes it works on the thrive, so its likely a minor routing issue on the vangogh vs Antares or Picasso boards. Sound is my weakest point though, I always have troubles with it for some reason.
As for pie, there's options for all kinda shiz in there, just gotta go through them all and restart systemui to make them active in some cases. That bar is, I think, just decoration, though.

Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:

AngryManMLS said:
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
Click to expand...
Click to collapse
I'm just curious why anyone
A: uses the crappy camera on these things for anything but Skype
B: bothers changing the resolution of the already low resolution cameras
The kernel included is already modified just hasn't had the juice turned on yet. I'm not a fan of his kernel for my personal device, it never got along with it. If you venture into its settings you'll notice it has some extras in governors and io, no longer stock CM.

Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.

AngryManMLS said:
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
Click to expand...
Click to collapse
I think he used ezterrys kernel, why he chose to over the godmachine kernel you'll need to ask him about lol. It was a nice kernel for sure, but my a100 just didn't like it. My thrive kernels love mine but hate some others, such is electronics I guess.
I'm still testing the kernel for when the juice is turned on so its a pretty basic kernel otherwise, bit it should wake up real nice when its let loose.

Looking over the notes from several of hardslog's ROMs he's mentioned they have used godmachine kernels (or as I mistakenly called them "Linuxsociety"). No idea on the latest ROM that he's released since there's no mention. Let me know if you need to me to test any kernels here. My A100 is ready.

Well the kernel has some odd issues, for one lulzactive seems to just stay at top speed, it doesn't seem to scale at all. In the overclock enabled builds anychanges to min/max speeds will result in no deep sleep, the kernel stays awake at all times. Not sure whats causing either of those, lulzactive can be gone over but why the speed change locks the system awake I have no clue.
I really wish I knew what I was doing with kernels lol
Edit:
Vote, who thinks I should just update the linux society/god machine kernel to 4.2 and leave it at that? lol

I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?

AngryManMLS said:
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
Click to expand...
Click to collapse
The deep sleep issues are only on the overclock enabled kernel that I use, it shouldn't appear in the released build, it only shows up if min/max speeds are changed from stock. Scaling issues appear only in lulzactive, its defaulted to interactive so unless you change it, its scaling properly.
I'm not using the ezterry or god machine kernels, so its a problem unique to mine I think.
It uses cache or it wouldn't be booting at all, and you shouldn't back that up anyways I think twrp has some bugs no one ironed out and its causing oddness with older devices.

Oops. I thought you meant godmachine's kernel had those issues. My bad. I should read better next time. :laugh:
Also checking CYANOSAKI_FLEX_V2.0 the kernel it's using believe it or not is by ezterry. SetCPU defaults to interactive on this for me as well running at 1.5 ghz max speed, 312 mhz minimum. No idea if hardslog has done any mods/changes to the kernel however. Run perfectly fine on my A100. :good:
And you are right about cache let alone the TWRP bug. Just finished wiping and restoring my CarbonROM backup by the way. Successful swapping from 4.2.2 to 4.1.2 and back via TWRP backups.

Ugh I hate kernels, and I hate working IN them even more. But, it's coming along. It'll basically be the GM kernel all over again when I'm done lol.
So far vs the source I began with:
GPU/CPU/system speeds are tuned a little more, voltages tuned a little more
Adding in those missing governors, like Smartass and lagfree.
Converted/updated to BCMDHD from BCM4329
OC up to 1.5, UC to 216
I'm building this to include with my 4.2 builds, and I suppose I could just release a flashable version, it may even work on 4.1, who knows.

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

Turn the S4 into an Oppo Find 7

I wanted to let everyone know for the past day or so ive been testing out the Color OS 2.0 for the I9505, here are some of those results, screenshots, and how to install for yourself.
So, the reason im bringing this up to get started is that for the past year or so i was unable to install this rom on my S4 i assume from not having the correct version of TWRP required for the install (AND the install will fail a few times for random reasons if SU is not installed (rom or not)...I found this out after a full wipe and it not letting me install the rom until i rebooted back into TWRP and told it to root my phone because it found no root access.
So the initial install went like this
Wipe...
Install...
fail halfway...
wipe...
install...
fail haflway...
reboot to recovery from recovery...
tell twrp to root....​back in recovery....
wipe...
install...
success...
Now the rom does include its own gapps package so there isnt a need for that, It also includes its own kernel that because of how heavily modified Color OS is from stock cannot be changed (unless you can find one that will work, the AOSP Ktoonz kernel didnt work and that was the only test i really attempted as i had to re-install the rom (wouldn't boot)
So, once the rom is installed it asks you to pick a language and looks a lot like regular AOSP (dark) but as soon as you do it prompts for wifi and settings FC's, then you move on to accounts and accounts FC's
So to get through this just skip ALL setup processes and type in your name with the built in keyboard (it has to be changed back to full qwerty or your gonna come up wth some weird things)
Then you can go into settings and apply your accounts and things like that to get your contacts and everything back per the usual.
Now onto my impressions of the rom so far...
This is the fastest rom i have ever put on my phone and yes it does come at a cost but from what i could see it is the most overall fluid rom especially when it comes to animations.
It has a lot of cool features i am still learning to use (gesture panel pull up from bottom, lets you draw a shape to preform action and set your own custom...looks cool as hell) and none of them even when enabled slow the device down.
The cost however is battery life...you WANT to have an extra battery or a fast charger on hand because this thing loves to suck power. Im alright with it currently with how fast the thing moves i am going to use it as my daily driver but i went from 50 to 2 in about an hour and a half with screen on. Screen on time isnt that awesome on this phone but standby seems to be pretty good.
Its a nice break from AOSP and Touchwiz, thats all that needs to be said really. Its much faster than either AOSP or Touchwiz even with custom kernels you can take that from me being a crack flasher, ive gone through every kernel made for the device, learnt about them, customized them, and then moved on to test another kernel.
This rom has ceased development but will currently be remaining my daily driver until i can find something else unique, i would say give it a shot guys and see how much you like it
For my install i needed TWRP 2.7.1.0
It will fail, do some troubleshooting to find out why (such as change to RM -rf formatting in settings in twrp) and after you wipe reboot to recovery and let TWRP do the root thing even though there is no rom (i dont know why this mattered at all -_-;;;; but it did) do another wipe when you get it and you should be able to install the rom and it will boot. (THERE ARE NO SIGNAL BARS TO INDICATE SIGNAL STRENGTH when you get in) and once you are finally in make sure you run to your APN settings under Mobile network and then go down to the T-mobile LTE APN and modify it, remove the password and the server info thats in there (for some reason) and change the APN protocol to IPv4/IPV6 and the roaming protocol and then save it so you have good data speeds and such (just to make it set up the same as a standard T-mobile rom)
in this rom ive noticed you CANNOT have wifi on and send MMS so to send pictures ensure you are off of wifi.
There is also a problem being noted in the comments on the rom page with Whatsapp...i dont use it >.> i know what it is but whatever it doesnt bug me at all.
Alright SO TO CLEARLY LIST THE STEPS
1. Wipe phone
2. Attempt to install rom
3. (IF FAILS on install) wipe phone
4. (IF FAILS on install) reboot from recovery to recovery
5. (IF FAILS on install) tell it to root
6. repeat steps 1 and 2.
7. when successful, boot into rom
8. select english and FC your way to the end of setup
9. enter your name or a random name into phone owner
10. setup your account in settings (or just open play store and it will prompt you)
11. Match your APN to T-mobiles standard (Settings>mobilenetworks>APn> T-mobile Us LTe)
--------Remove Password, Server, Change APN protocol to IPv4/IPv6, same with roaming, save and use that apn-------------------
You will not be able to send MMS with WIFI on. (you can if its off)
You WILL have to change keyboards (the one that comes with the rom is absolute ****, use enter to keep what you type english...)
There is a FIX for Whatsapp inside of the roms official forums ( i dont use it though )
ALSO unsure if USB file transfer is working right >.> sure there is a fix for that but it doesnt but me either. (i use wifi file transfer anyways >.>)
YOU CANNOT INSTALL A CUSTOM KERNEL (unless your willing to find one that works)
So far i havnt found any problems for my use, this is one of, if not the, fastest and smoothest roms ive ever used so i am attempting to show others the awesome
link to rom forum below (MAKE SURE YOU DOWNLOAD THE NEWEST ONE, old one borked and buggy)
http://forum.xda-developers.com/showthread.php?t=2748022
NEWEST VERSION (Taken from OP) http://www.androidfilehost.com/?fid=23487008491964142
Just for those of you who didnt know this was out there, or were like me and gave up trying to install it at first.
SCREENSHOTS (CLICK FOR FULL RESOLUTION) (TAKEN DIRECTLY FROM PHONE) (VIA OPPO 3 FINGER SWIPE UP (customizable to change to anything i believe))
Now to get dual tap to wake download an app called Knokr <- from the playstore (its part of the Oppo screen so this is the only way to emulate)

igotlostintampa said:
I wanted to let everyone know for the past day or so ive been testing out the Color OS 2.0 for the I9505, here are some of those results, screenshots, and how to install for yourself.
So, the reason im bringing this up to get started is that for the past year or so i was unable to install this rom on my S4 i assume from not having the correct version of TWRP required for the install (AND the install will fail a few times for random reasons if SU is not installed (rom or not)...I found this out after a full wipe and it not letting me install the rom until i rebooted back into TWRP and told it to root my phone because it found no root access.
or were like me and gave up trying to install it at first.
SCREENSHOTS (CLICK FOR FULL RESOLUTION) (TAKEN DIRECTLY FROM PHONE) (VIA OPPO 3 FINGER SWIPE UP (customizable to change to anything i believe))
Now to get dual tap to wake download an app called Knokr <- from the playstore (its part of the Oppo screen so this is the only way to emulate)
Click to expand...
Click to collapse
o.o was i the only one excited feels bad being the only crack flasher here.

Is it stable? If yes, will like to give it a try

dunhillpanda said:
Is it stable? If yes, will like to give it a try
Click to expand...
Click to collapse
Yeah I really like it once its got a new keyboard. Havnt had a force close or random reboot. The thing is so much smoother than any other rom ive tried its crazy. And after about a day the battery drain has gone away. I honestly am thunkibg about keepimg the thing if it keeps going this well as a perm backup.
The onky issues ive seen i listed in the OP but they arent problems for me really

Looks interesting. Props on the info, I'll look into this soon
Sent from my SGH-M919 using XDA Free mobile app

All Functional
IT seems everything i use the phone for is functional on this rom. I have seen no issues at all with everything that i regularly do and with some added functionality from the android general section (acid audio (i prefer it >.>)) I dont see any reason to change off the rom o.o it has some of the best touch response i have seen on a rom (less lag on inital jerk from finger than touchwiz/aosp) the only thing its missing is the over the top customizations some roms have that will be kinda stock in android L o.o so i think im going to wait for either an L rom or color os 2.5 > 3
>.> <.<
unless another rom peaks my interest before then but im so tired of AOSP and Touchwiz xD and that seems to be the majority of this forum o.o like ive googled a lot of other roms... >.> MIUI and XUI both exist for this phone as does Color OS and many hybrid Touchwiz/AOSP roms exist over in international, as well as many roms that just never make it to our forum because they are being undercut by the popular roms for our device and immediately jump to the end of the forum..some of which are more stable than some of our most popular roms >.<
Sorry i ranted, just overal kind of curious what the Samsung user Obsession is with Touchwiz and AOSP when better than both exist for the devices we use >.> i mean i get liking the style of a rom but im not used to entering a forum here where other roms dont exist o.o i wonder what roms the nexus devices get.

Ooh! This looks fascinating! Im pretty new here but ive lurked forever and I have been looking for a new rom to try. It looks like we value the same things in a rom and the bugs wont be a problem for me either (almost never ever turn on wifi for instance) so im excited to try a rom that youve decided will be your DD.
Ill let ya know how it worked.

Oh man. This ROM is cool...
My phone played nice with it upon install for whatever reason. On my first wipe it took. Most of the setup crashed like you said, for some reason the google log in part didn't crash. After changing the APN settings everything seems to be working great. It really is fast and responsive ( there is a scroll slide effect kinda like iOS that makes lists feel slick)
My small qualm is that it shows that you have no service at all times. Even the weather app says "no service" in it so having that on the home screen and in the status bar is bothersome.
My large qualm is battery. This ROM is freaking gorgeous, I seriously want a phone beefy enough to run like this for a long time, I can't stress how pretty this is for anyone who hasn't tried Oppo's stuff. But I'm getting roughly what OP did on battery though, it feels like only a bit over 1/3 the longetivity of most other Roms I've tried... Reminds me of my old iPhone 4 after 3 years of use. So that really bites. But hell if it isn't pretty.
Another user said the battery problems go away after the ROM settles so imma give that a bit and if it does... I couldn't possibly change it. The weather effects on the home screen are addicting and I love how the rain/snow will fall on icons and splash or accumulate. It feels like a ROM in step with the future.
---------- Post added at 11:56 AM ---------- Previous post was at 11:44 AM ----------
Scrawlerism said:
Oh man. This ROM is cool...
My phone played nice with it upon install for whatever reason. On my first wipe it took. Most of the setup crashed like you said, for some reason the google log in part didn't crash. After changing the APN settings everything seems to be working great. It really is fast and responsive ( there is a scroll slide effect kinda like iOS that makes lists feel slick)
My small qualm is that it shows that you have no service at all times. Even the weather app says "no service" in it so having that on the home screen and in the status bar is bothersome.
My large qualm is battery. This ROM is freaking gorgeous, I seriously want a phone beefy enough to run like this for a long time, I can't stress how pretty this is for anyone who hasn't tried Oppo's stuff. But I'm getting roughly what OP did on battery though, it feels like only a bit over 1/3 the longetivity of most other Roms I've tried... Reminds me of my old iPhone 4 after 3 years of use. So that really bites. But hell if it isn't pretty.
Another user said the battery problems go away after the ROM settles so imma give that a bit and if it does... I couldn't possibly change it. The weather effects on the home screen are addicting and I love how the rain/snow will fall on icons and splash or accumulate. It feels like a ROM in step with the future.
Click to expand...
Click to collapse
Oh shoot I forgot to mention, sorry to spam this thread! Some apps return "package file invalid" and you flat out can't install those apps. This was fixed for me by wiping the caches in recovery but I've read this doesn't always work. In the end I personally got every app I wanted installed so idk if that will be a problem but yeah.

My issues with battery life so far have greatly dimmed, I am unsure if it was just the rom getting used to itself or the kernel setting itself up...but my battery issues have gone down greatly.
THOUGH I will mention that it is still worse than AOSP and Touchwiz, just not by nearly as much as previously thought. (EDIT: THE BATTERY LIFE, I actually don't think ill give this rom up
Also I did also have the problem with "Package File Invalid" and I also wiped the caches to get everything to install properly, but I also found that a full storage wipe of the phone (copy everything important off first) prevents that issue with most roms, I may try it with this one if I decide to ever uninstall it in the first place. The rom is kind of amazing...
Normally I would be experiencing some kind of stability issue with an app or something by now or maybe a keyboard...but not with this rom, not at all. It is still running as amazing as when I first turned it on.
OH I have to mention I guess that I did turn on some power saving settings so that may have been what effected the battery life so dramatically. In honesty I think now it lasts me quite a while...I may actually think I get better battery life in the last 15-20% than AOSP or Touchwiz, touchwiz being the only one with a decent power saver setting (with ROM)
but yeah I love this rom and wish there were more like it for our device....I know miui is available and I might look back into it for more of a full themeing effect, but I love the gesture panel and im gonna try to port it over to the miui rom >.> and see if it will load. Seems to be an app that's built into the phone but im unsure how deep rooted it is.
MIUI+ColorOS = Amazing combo.
Thanks though guys for looking into this! glad to see some other crack flashers around.
This rom does seem to be taking kind of a large leap, but at least its forward.

igotlostintampa said:
My issues with battery life so far have greatly dimmed, I am unsure if it was just the rom getting used to itself or the kernel setting itself up...but my battery issues have gone down greatly.
THOUGH I will mention that it is still worse than AOSP and Touchwiz, just not by nearly as much as previously thought. (EDIT: THE BATTERY LIFE, I actually don't think ill give this rom up
Also I did also have the problem with "Package File Invalid" and I also wiped the caches to get everything to install properly, but I also found that a full storage wipe of the phone (copy everything important off first) prevents that issue with most roms, I may try it with this one if I decide to ever uninstall it in the first place. The rom is kind of amazing...
Normally I would be experiencing some kind of stability issue with an app or something by now or maybe a keyboard...but not with this rom, not at all. It is still running as amazing as when I first turned it on.
OH I have to mention I guess that I did turn on some power saving settings so that may have been what effected the battery life so dramatically. In honesty I think now it lasts me quite a while...I may actually think I get better battery life in the last 15-20% than AOSP or Touchwiz, touchwiz being the only one with a decent power saver setting (with ROM)
but yeah I love this rom and wish there were more like it for our device....I know miui is available and I might look back into it for more of a full themeing effect, but I love the gesture panel and im gonna try to port it over to the miui rom >.> and see if it will load. Seems to be an app that's built into the phone but im unsure how deep rooted it is.
MIUI+ColorOS = Amazing combo.
Thanks though guys for looking into this! glad to see some other crack flashers around.
This rom does seem to be taking kind of a large leap, but at least its forward.
Click to expand...
Click to collapse
Honestly the battery did get better after a couple days. Aosp has probably spoiled me. I really really liked this ROM.
Edit: and I know what you mean by "forward thinking" this ROM feels like the future.
And yes, definitely a crack flasher here. Even now that I have a ROM that I always fall back on I'm still flashing at least a few times a week, and trying new Roms on weekends. >.<

Will try this soon

this is a really nice rom for the s4 , i didn't have to reflash at all, one wipe flashed the rom, it was succesful and booted right up on the first try. Thanks for this, i tried the newest 9/6 debloated version from the link in the OP but it seemed to be a lil glitchy, the one in OP works fine. Thanks again