Related
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.
so this is what i have been messing with for the past few days since i think not so super froyo has hit a point that im happy with for the moment
my goal with this build is to get rid of as much of the unneeded apps as possible and shrink the system down as small as it can.
things that are removed from the initial install that are in fresh froyo
-HTC_IME
-Gmail, google search, voice search and pretty much every other google app that can now be installed from the market
-as always live wallpapers and launcher 2 are gone
- the how to use android widget
- their are no other wallpapers or galleries installed on this build too their are plenty of the apps on the market for that
- THIS BUILD IS ENGLISH AND SPANISH ONLY!
things that are in it
- a new blue theme i have been working on (some of the .png's are from losteden, vellowax and some other various themes), its pretty close to perfect but their might be a few hiccups still
- ADW is still the launcher of choice and its still in /data for easy removal
- a different themed clock
- zip align on first boot
- astro and rogue tools are both installed in /data
known issues
- ADW still does the could not load widget error like in Not so super
I was going to odex this build but wasnt able to get the ADB driver to work correctly (if somebody does manage to get it Odex'd feel free to post it)
Also this was merely a test to see how light i could get it and it ended up being decently stable, i don't know how much updating i am going to do to it.
RLS2
-car home and car home launcher removed
-music player removed as their are tons of replacements in the market
- now odex'd
New in odex'd RLS3
-street.apk is now removed since maps is also gone
- voicedialer is also gone seeing at the newest version of voice search on the market can voice dial also it seems pointless
- lowered the volume on the camera shutter noise
RLS4
- newer version of fresh froyo (thanks scooter)
- Now using ADW standalone with a myn warm twopointtwo inspired look
- Flutey phone ringtone now include by default
- different wallpaper this time around
- bright blue themed desk clock
- more "sensible" notification drawer
RLS5
-fixed facebook sync
-fixed the graphical issue with the status bar highlights being green instead of blue
-added the blue keyboard from my Galaxy S theme/port (delete key is a little small but the keyboard file size is overall smaller.
-new boot animation that goes better with the theme
ALL-LANG ODEX
-all languages
-doesn't have 1% battery indicators
-sadly some of the theming elements had to take a backseat to space saving
-seems just as stable
screenies
{
"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"
}
DOWNLOAD RLS1 DEODEX
here is an odex'd version of the build, the music player is also removed seeing as there are a ton of free options for that on the market that do it better
also this is untested as far as data and sms, it should work fine ( i did check to make sure there was not a call hang issue)
ODEX DOWNLOAD RLS5
ALL LANG-ODEX
looks nice... gonna give it a shot!
Nice battery meter... what's it?
Is it available as update? (Running VaniljEclair... having trouble with Froyo )
Have a nice day
On our weak kaisers, we need more roms like this. Barebones and stripped to the maximum.
Please wait while I give it a go .
Thanks.
EPIC WIN Thoughtlesskyle! 100X times better than Not so Super Froyo and OVER 9000 times better than any other Android distro out there. My current droid, not changing it at all for a long time (only updates to this build and odexed build).
Fat Free Froyo
Seems to be a good build!
I'll test.
Nice job guy!
Really want to thank you for all the hard work on this and your other builds which I have been trying out.
I've had a lot of trouble with yours and others builds getting mass storage to work consistently - even using the Dual Mount Widget. Finally seem to have hit a good combo though with the latest 2.6.25 (+wifi fix) and your builds.
I'm loving the blue and black plus it's nice to know I'm not pushing the envelope installing some of my other fav apps .
so i just managed to get the build odex'd holy poop its fast is all i have to say
im a little low on bandwith from my free mediafire account so i kind of have to decide what i want to do as far as putting this build up
He's on fire..
Very nice work...
vellowax said:
He's on fire..
Very nice work...
Click to expand...
Click to collapse
thank you for all your help btw without you my theme would look very bland (used some of your png's) and also the battery indicator wouldnt be nearly as cool
thoughtlesskyle said:
thank you for all your help btw without you my theme would look very bland (used some of your png's) and also the battery indicator wouldnt be nearly as cool
Click to expand...
Click to collapse
You are a busy man now...
Well, as I said before, feel free to use it, I don't plan to make a new theme at least for now, you mix them better than mine.
I'm now get busy with those java lang and eclipse, I still attempt to fix the camcorder app though I might failed.
This is a very great community, I learn a lot from here.
vellowax said:
You are a busy man now...
Well, as I said before, feel free to use it, I don't plan to make a new theme at least for now, you mix them better than mine.
I'm now get busy with those java lang and eclipse, I still attempt to fix the camcorder app though I might failed.
This is a very great community, I learn a lot from here.
Click to expand...
Click to collapse
how sad is it that i just do this for fun, since my touch isn't active part of me actually enjoys having to do some basic problem solving and i must say i have learned alot about file structure and how android works from doing it, and im really happy i have been so well received by everyone since a few months ago i was the one using everyone else is builds, its nice to give back.
and i'm glad to see that this community is still active even though the faces have changed of people making the builds and doing the dev.
i am also thoroughly surprised at how many new people just show up on here.
odexed build now! HAVE TO DOWNLOAD ! You just managed to knock myn and incubus off my favourite android dev list! U are on top man, keep going! I'm just going to use 3, that nice music app replacement and it's perfect!
pl0ppy said:
odexed build now! HAVE TO DOWNLOAD ! You just managed to knock myn and incubus off my favourite android dev list! U are on top man, keep going! I'm just going to use 3, that nice music app replacement and it's perfect!
Click to expand...
Click to collapse
Could you explain (or reference) how you did the odexing.
sir i have a problem i try this version when i installed it then quit my phone is still in boot mode and it says mounting /data/sysfiles/ su on / system/xbin/sun faiel no such file or directory
need help sir here
in the below it says
ANDROID unable to open persistent directory /data/property error 2
what is the problem with this? thanks for the help
Blue
I love the blue theme in some of the icons - actually a bit easier to read for me than the green.
Nice and quick
Trouble is I don't use market so all the apps I want have to be installed using my alternative method - but it's nice to have the control ...
Very nice job, I like it, but how can I add french language ?
Kernel recommendations?
Which kernel is recommended for this build on Kaiser?
URL would be nice.
I've tried running some different builds with zImage-2.6.32-froyo-09-10-10_23 from (http://it029000.massey.ac.nz/vogue/files/) and the new haret-for-kernel-2-6-32, but that gives really crappy performance for me.
Takes ages for haret to switch from frozen state to android boot + long boot time and FCs.
pl0ppy said:
odexed build now! HAVE TO DOWNLOAD ! You just managed to knock myn and incubus off my favourite android dev list! U are on top man, keep going! I'm just going to use 3, that nice music app replacement and it's perfect!
Click to expand...
Click to collapse
thank you for the kind words but i still stand firm on my statement that i am not a dev i'm a guy who can use 7zip and read. also being patient helps too.
but yea it seems to be really stable so far i am happy i finally got it to odex
waterpolo said:
Could you explain (or reference) how you did the odexing.
Click to expand...
Click to collapse
alright here is the thread with the odexing info i used
http://forum.xda-developers.com/showthread.php?t=694597
my biggest problem (and still is) i could never get my vogue to read correctly with my windows 7 computer, so how i worked around it was
1. first i moved all of the apps into /system so /data was empty
2. then using 7zip i edited the tar so that the odex script was in the same place that the adb push would have located it (e.g. /data/odex/odex.sh)
3. then i added a terminal editor into the build (i just grabbed the one from CM6)
4. i booted up the phone then opened terminal emulator
5. in the emulator i typed the following
su (the superuser box will pop up i hit allow, this caused the program not to work right after the SU so i backed out and when back into it) then i typed
su
# sh /data/odex/odex.sh
6 once i did that the script started odexing the files
7 upon completion the phone needed to be restarted
8 then using astro i pressed up till i could get to the system folder
9 i then copy and pasted this to the sd card
10 i then put the sd card into my computer and used 7zip to replace the system i was using with the newly odex'd system
11 since not everything was in the system folder i copied i used 7zip to merge the missing files this was the ect folder and the media folder
12 i then deleted the files i moved into /system from data (adw,roguetools,and astro) and put the /data folder back into the .tar
13 then booted it up on my phone for a test run
i am pretty sure thats about everything i did to odex it
First I would like to give credit to everyone who has worked on GBX0* in any way. ACL, arrrghhh, detule, and Stinger22 to name a few important faces around here. I do not take credit for 99% of this. It is a modded version of the GBX already published on XDA.
Stinger22 is responsible for building the killer new kernel. I packaged the kernel into a boot.img and collected all the compatible updates into a single installable Zip with lots of tweaks.Stinger22 deserves big thanks for his work here.
There will be limited support for this build. Feel free to ask questions, and even better if you can help answer them. If you know how to fix something that is broken I would love to hear from you. I would be happy to include anything that you can contribute.
Due to the number of people unhappy with the RHOD100s phones and this rom, we do not recommend it for the RHOD100s (not that we ever did as we only have RHOD400s to test with).
New install guide.
Now what you came for:
GBX*
Includes:
GBX 5-8-12 lib update.
Slightly smoother boot animation used.
Build.prop tweaks.
Added a couple of ringtone/media sounds.
Superuser replaced with SuperSU .97
Modded audio.conf file to allow for the streaming of media metadata from apps like Pandora when the advanced menu / car bluetooth mode is enabled in the app. Also this change should allow for more Bluetooth devices to connect to the phone. Does only appear to support AVRCP 1.0, so no metadata without extra app support. However track forward/back/pause will work with some setups.
Added circle battery icons with %s for more precise gauging. Shows in 5% blocks. What you see is +/-3% of what the battery is really reporting. Based off the themes here. It is better than a half filled bar IMHO. It might take a full discharge or two before the battery gague/acl code becomes accurate. The battery also tends to drop quickly in the first 10% and then levels off.
RHOD300 keyboard fix. Credit to Detule
Changed RHOD100 from default keyboard to RHOD100_UK keyboard map.
Fix to ramdisk to resolve error reported during boot.
Fix to bluetooth main.conf to prevent bluetooth media devices from crashing OS. *only included in the 3.4.26.1 and newer full build*
-Still have issues where connecting/disconnecting the sink device can sometimes cause the phone to reboot. Seems sink device dependent. Mostly fixed in 3.4.26.13
Fixed bluetooth typo bug to 3.4.26.1 in 3.4.26.11
Boot animation in 3.4.26.13 credit.
3.4.17 Kernel update:
Including ACL's newer battery code.
More accurate readings from battery gague.
Maybe slightly better sleep battery usage.
Small Bluetooth fix (I find paring to be easier).
Kernel panic fix that may help prevent phone lockup if apps crash.
Many other small patches.
Fixed USB detection issue in 3.4 kernels.
Overclocking still supported. (SetCPU is free to XDA members)
Added a hack supplied by detule to prevent the sd card reader from suspending to prevent unexpected sd card removal errors.
Added a kernel splash screen to cover up some of the rolling text during boot time. Credit.
Sleep works with wifi turned on. - Battery life should improve where wifi prevented sleep before. Wifi tethering will prevent wifi sleep.
Zoom slider bar now works. Acts like a two finger touch moving from the center of the screen. If you tap on the zoom bar it will be just like tapping in the middle of your screen. Something to keep in mind if you get unexpected touches while holding the bottom of your phone. More benefit than a draw back IMHO. Added permission files. Link at bottom for those who just need this (based off of mankineko's work).
3.4.24 Kernel *minor update*
Includes updates from source.
Added code to cause system to reboot rather than hang from a system crash.
3.4.26 Kernel
Reboot function in shutdown menu has been fixed (power off is still broken)
Host file is no longer over written on boot up. This had been preventing ad blocker apps from working correctly.
ACL's panel code has been used. Hopefully this will resolve some issues for the RHOD100 users. We have no way to test, so it is as-is.
Auto brightness has been fixed. You may need to press the power button and force the lcd off, after it has been enabled, before it will take effect.
Device name is no longer reported as 00000000 by ADB. It should show as the serial number.
3.4.35 Kernel
Slight performance tweaks.
Added CrossBreeder mod. Basically helps tethering internet.
Added "Smartassv2" cpu governor. Can be set using apps like SetCPU. Should be slightly better performance, but may come at the cost of battery life.
Added "row" scheduler.
3.4.41 Experimental Rhod400 Kernel.
Shutdown working
Fps limit fixed, plus a slight gpu performance boost (previously was benching about 19fps for both 2d/3d, now I'm getting up to 60fps 2d, 26fps 3d)
Enabled more compiler optimizations. Kernel is slightly larger, but seems to perform a bit better
USB: No need to plug/unplug once before adb works, faster cable connection detection
Other miscellaneous tweaks that may or may not help battery life
Known bugs:
Many of these bugs are found in the 3.X kernels, and so they may be found here too.
MMS does not work out of the box. Add this APN info if you want it.
Google maps newer than 5.9 shows graphic distortions with street names, and other graphic issues sometimes. Waze is a good gps alternative if you want something with more features.
Shutdown and reboot options on the power button menu do not work.
Auto backlight does not work.
8-15-12 RIL update breaks radio (on CDMA for sure/no reports from GSM owners).
SD card unexpected removal errors when the phone wakes from sleep on *some* phones. -try a non SDHC sd card if all other standard troubleshooting fails. I have been able to use a 512mb and 1gb card micro sd card without issue. However all my 4,8,16, and 32gb micro SDHC cards have this issue. Hacked work around as of update 3.4.17.
May have to remove and reinsert USB cable a few times before the phone will recognize it has been plugged into a data port. Also you may need to turn features on/off to get the correct tethering/usb storage/usb debug to work correctly.
No front facing camera support for RHOD100.
Deleting bluetooth.apk may be necessary to get the phone to connect to some Bluetooth devices that have any advanced features.
If Bluetooth is left on and the phone is rebooted/crashes, the unit may bootloop. I have not found a fix other than reloading the Rom from recovery.
This bug seems to effect A2DP and other audio streaming devices the most v.s a bluetooth mono ear piece for calling with. This is a bug I have been able to repro on the GBX*+ 3.3.6 kernel as well. Make backups before using Bluetooth. If you are a CDMA user, you could try the original Ril from inside the GBX+3.x rom. It seemed to cause the reboot loop a little less. However GSM users must have the 5-8 Ril to use this Rom.
Found that this bug seems to be for devices that support multiple profiles. I have a Bluetooth receiver that will use phone and media profiles. If the phone profile is disabled the lock-ups do not happen. This work around will not let you use the phone features, but you can stream media. You need to pair the device. Then long touch it to get a to an options menu. Uncheck the phone profile option to stop the crashes when playing any media.
Sometimes if the phone locks up during the boot animation from this issue, then you reboot once or twice, and leave it alone for a long long time it will sometimes finally finish booting. It is worth a couple of reboots, and a lot of waiting vs reloading the rom. It also seems to help if you plug the phone into the usb on a computer after the boot process has passed the blue screen.
Pandora's internal/advanced bluetooth settings must be turned off, otherwise it may crash the phone on device disconnect.
Bluetooth is not 100% stable, and may crash the phone on connecting or disconnecting devices. During use it is stable.
If the phone crashes while bluetooth is turned on it may boot loop. If this happens connect the phone's usb port to a charger or usb port on a computer. This should cause it to boot correctly on the next time around.
Sprint phones must be activated on the Sprint network in WM before loading Android. Android can not activate everything correctly.
It has been reported that the keymap for the RHOD300 is not correct.
Not an Android bug, but Sprint DNS services are crap. I found good working links not working correctly due to bad dns info. Of course you can use any public dns server you like.
A suggestion for getting your own dns in more easily is this App.
If you tether on Sprint I suggest that you put your own DNS server in under the TCP/IP settings on client device as it will only use sprint's by default. I leaned this the hard way.
RHOD100 WIFI may not reconnect to access point automatically upon waking from sleep. Disable and reconnect to work around.
This Rom was only tested on the Sprint TP2 RHOD400. It will probably work on any that worked with the GBX0* + 3.3.x kernel, but we can't promise it.
Updated RIL from Skysoft here. Not included in any build. 4-16-2013
Full Downloads:
GBX0*+3.4.17 Full.
GBX0*+3.4.24 Full
GBX0*+3.4.26 Full
GBX0*+3.4.26.13 Full *feedback on if Bluetooth is still crashing the phone after a clean rom load would be interesting.*
GBX0*+3.4.35 Full
Kernels:
3.4.26 Kernel update.
3.4.24 Kernel update.
3.4.17 kernel update.
3.4.35 kernel update.
3.4.41 Experimental Rhod400 Kernel.
If you download please hit thanks at the bottom and/or post feedback. I'm curious as to how many people are downloading.
New install guide.
Old install directions for all other NAND roms.
It is assumed that you have unlocked your phone. If not read here and/or here, and/or here.
If you are running the 8-15 ril that was patched, and you are unable to get a cell signal, I would highly suggest that you install the older patch ril file.
If you want to add just the permission files for the zoom bar (and a few other things) rather than downloading the whole thing again here they are. When I did this it broke Zeam. I had to add another launcher, and then switch between the two. That fixed it for me.
As always BACKUP, BACKUP, BACKUP before doing anything. Please use at your own risk.
*Related goodies*
Gapps package.
For those of you who want an ICS facelift, check out the modded Zeam launcher.
Most recent recovery thread. - this recovery creates a md5 error on a backup's restore. Anyone know how to fix it?
ACL's known good recovery.
Good chance you will need to calibrate your touch screen. This thread covers that,and how to make it stick.
I may have found a launcher that is more lightweight than Zeam from what I can tell. I am running Lighting Launcher, and am quite happy. Seems to have an even smaller memory footprint, which is great for phones without much memory.
Swapper2 app. This is an interesting thing I found the other day. It allows you to use your SD card for swap (Virtual ram). I did verify that a 64mb swap file (did not test swap partition) can work on our phones. I would love to hear some feedback from people who might be interested in playing with it. I would suggest a Micro sd card with a high random read/write speed. Here is a guide that is already made if you want to use a swap partition rather than a swap file. It will probably wear out your sd card faster, but sd cards are cheap these days. Also note that SD storage vie USB may not work if you use this mod.
Update.
I got out my 32gb high random speed sd card today, and I whipped up a swap partition according to the guide above. I bumped the swappyness setting to 100. I was in a generous mood, so I lopped off 1gb of space for swap (256mg would have probably been a better choice). I did get a name error when I enabled it, but it seemed to work just fine. The swap space of 1gb showed up by the free command, and the swap space showed use after I ran a few apps. It is a subjective observation, but I think multitasking is a little smoother. I plan on leaving it setup like this for now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did manage to max out the cpu, and crash the system resulting in a reboot. I was running two gps apps, and two music apps, and two or three other apps all at the same time (abit poorly though). It might not have liked having multiple apps access the same resources.
Here is a handy app for rebooting the phone quickly, and entering into recovery.
Possible way to disable the proxmity sensor for people who have bad ones causing a non-waking screen here. Credit.
*Bonus for Sprint RHOD400 TP2 users*
If you are tired of the white HTC splash screen here are two nbh files you can flash just like a rom from the SD card. They should only touch the splash screen. Everything else is left alone. Flash one, or both in any order. These probably work on other Rhod phones, but I have no way to test them. So no screaming if something gets bricked. Based off the work in this thread. Reported not working on RHOD100 by this post. Reported working on RHOD300 here.
If you know of an image (480x800 res) that is even more amazing than these, and you feel it would be a good replacement drop me a link to it. If I love it, it will make it to the first post. Otherwise I might just whip one up special for you for contributing.
Primary
Secondary
As of 3-25-13 I have moved onto the EG4G/SII phone after reading about it and SERO legacy at Howardforums.
I will stop in from time to time, and if I am given a newer kernel I will post it. However I will no longer be using this phone.
So long, and thanks for all the fish.
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Slipdoozy said:
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Click to expand...
Click to collapse
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
wizardknight said:
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
Click to expand...
Click to collapse
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Slipdoozy said:
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Click to expand...
Click to collapse
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
wizardknight said:
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
Click to expand...
Click to collapse
im not happy with google selling my info so i refuse to give them any space on my phone lol
i tried the modded zeam all the ways i could think of, before flash, after flash, through adb didnt matter. maybe corrupt apk?
no worries. ill try to redownload it and try it your way with launcher2 first
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Slipdoozy said:
i tried the modded zeam all the ways i could maybe corrupt apk. before flash, after flash, through adb didnt matter.
no worries.
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Click to expand...
Click to collapse
Be ok with loosing the money. Some people have reported that they didn't get the unlock info, and the dev for that is next to impossible to get to respond.
You might check this thread. Not sure if they got it working.
Most of the credit goes to Stinger22. The man is kicking some serious code butt!
I would try re-downloading the apk. I was able to install it with a adb install. Not sure what else it could be. Did you hold your tongue just right while dancing madly during the install?
Slipdoozy said:
im not happy with google selling my info so i refuse to give them any space on my phone lol.
Click to expand...
Click to collapse
You do realize where Android is coming from... Right? lol
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it... Glad it did not get forgotten!
Zoombar!!
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Caldair said:
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Click to expand...
Click to collapse
HAHA. I didn't think the zoom bar would be the selling feature of this rom, but I am glad you are happy.
arrrghhh said:
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it.
Click to expand...
Click to collapse
Didn't know who did the base work. - Gave credit in the post.
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
CodaHighland said:
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
Click to expand...
Click to collapse
Wow. I had no idea that the zoom bar was so popular. Just doing what we can to keep the phone going.
Thank you so much for your hard work (especially fixing zoom bar!!!.)
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
Yes, overclocking is supported. This should be the same as 3.3.6. I believe the frequency range you can choose from is 122-825. Download your favorite overclocking app from the market, and have at it. I use quick cpu overclock lite.
*edit. I think we have some new governor options. Link for descriptions.
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Slipdoozy said:
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Click to expand...
Click to collapse
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
wizardknight said:
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
Click to expand...
Click to collapse
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Slipdoozy said:
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Click to expand...
Click to collapse
I am assuming that you mean OMGB by ACL's rom. To the best of my knowledge there is no way to port the feature without building your own kernel. It is my understanding that the 3.x kernels (what we use) are not compatible with that rom. OMGB userland is no longer receiving updates, so unless another dev adopts that rom it will never work.
I will take the 1% credit for this rom. I have done behind the scenes, packaging, some Bluetooth mods, and testing stuff. The other 99% goes to everyone (esp Stinger22) who has worked on it before me or with me.
On the phone that the zoom bar is not working, did you download that rom zip before or after 11-3? I didn't change the file names or links with the last update. You might try downloading the perms file at the end of the post, and installing that. Otherwise I would re-download, wipe, and reinstall.
If you are still having trouble let me know, and I will go check the zips to make sure that something didn't get busted in the last round of updates.
Ok so I've been using Jelly Bomb 13 for a while now.
I've been having issues with it, I'm not sure if its the ROM itself, or if its Just Jelly Bean, and some of the Apps I run.
I'd like to explore other ROMS, but don't want to waste my time, when I'm not clear what some of the roms are offering.
I will start with my observations.
First JBomb 13 issues.
I've had weird problems with the alarm clock, changing its settings, etc...
It does this annoying thing when the lock screen wakes up if I try to lock it again the screen turns of then back on again.
Desktop rotation freezes sometimes.
Lately the entire phone freezes and I have to remove the battery to reboot it.
I don't know if this is related to skype on my phone. Skype seems to be pretty damn unstable on this phone (or all phones).
Sometimes volume control won't change volume for current app being used (probably just Android??)
There is absolutely no way to get the water and ink effect to work on my lockscreen.
Also I had an issue where I powered off the phone, but it powered up as I was removing the battery, and caused all my system settings to reset, as well as screwed up a bunch of my installed programs where I had to manually delete the files, before It would allow me to reinstall the apps. I'm not quite sure that I've fully recovered from that issue a lot of settings I had to go and tweak.
Ok my confusion and Questions:
There are several devs:
Besides their list of things they've tweaked or changed, I'm not really clear on why these are compelling reasons to use their roms.
I've noticed that [Team Nocturnal], has several different roms being worked on, but their sites don't reflect what the various branches are,
or why one may be better for certain users than others.
So my question to the Devs especially ones like [Team Nocturnal] Why don't you make specific distinctions between the various roms. It seems like to many of these roms are obsessively focused on the aesthetic.
I am assuming its more of a ME TOO thing, than "Look what I can offer you" thing.
I really liked "The Blu Khuban" from Team Nocturnal on my EPIC4G touch, I would love something like that for my Galaxy note 2, the update feature was great.
Also I have paid for stuff like Sketch Book and Papyrus, Personally I like some of the general pencil, and ink tools better, on S-Note...
Is it impossible to implement touchwiz stuff in Cyanogen? I used Cyanogen9 on my Epic4G touch and loved it except for they couldn't get the damn Wimax Modem working stable.
At the moment I think I will just go back to a stock de-odexed ROM, and tweak my OS myself as much as I can. Aesthetics are nice, but I feel like some of the tweaks in Jelly Bomb overlap and interfere with each other. Not sure if this is the case, but its very difficult to sift through 800 pages on Jelly Bomb...
INB4 wrong thread moved to dev forum...
your whole post is tldr.
you should post yer jellybomb issues in the... jellybomb thread!
but: TW anything will never be in/work with CM#/AOSP. the end.
and: this will never be moved to dev forum, because you didn't' dev anything.
spodemaster said:
Ok so I've been using Jelly Bomb 13 for a while now.
I've been having issues with it, I'm not sure if its the ROM itself, or if its Just Jelly Bean, and some of the Apps I run.
I'd like to explore other ROMS, but don't want to waste my time, when I'm not clear what some of the roms are offering.
I will start with my observations.
First JBomb 13 issues.
I've had weird problems with the alarm clock, changing its settings, etc...
It does this annoying thing when the lock screen wakes up if I try to lock it again the screen turns of then back on again.
Desktop rotation freezes sometimes.
Lately the entire phone freezes and I have to remove the battery to reboot it.
I don't know if this is related to skype on my phone. Skype seems to be pretty damn unstable on this phone (or all phones).
Sometimes volume control won't change volume for current app being used (probably just Android??)
There is absolutely no way to get the water and ink effect to work on my lockscreen.
Also I had an issue where I powered off the phone, but it powered up as I was removing the battery, and caused all my system settings to reset, as well as screwed up a bunch of my installed programs where I had to manually delete the files, before It would allow me to reinstall the apps. I'm not quite sure that I've fully recovered from that issue a lot of settings I had to go and tweak.
Ok my confusion and Questions:
There are several devs:
Besides their list of things they've tweaked or changed, I'm not really clear on why these are compelling reasons to use their roms.
I've noticed that [Team Nocturnal], has several different roms being worked on, but their sites don't reflect what the various branches are,
or why one may be better for certain users than others.
So my question to the Devs especially ones like [Team Nocturnal] Why don't you make specific distinctions between the various roms. It seems like to many of these roms are obsessively focused on the aesthetic.
I am assuming its more of a ME TOO thing, than "Look what I can offer you" thing.
I really liked "The Blu Khuban" from Team Nocturnal on my EPIC4G touch, I would love something like that for my Galaxy note 2, the update feature was great.
Also I have paid for stuff like Sketch Book and Papyrus, Personally I like some of the general pencil, and ink tools better, on S-Note...
Is it impossible to implement touchwiz stuff in Cyanogen? I used Cyanogen9 on my Epic4G touch and loved it except for they couldn't get the damn Wimax Modem working stable.
At the moment I think I will just go back to a stock de-odexed ROM, and tweak my OS myself as much as I can. Aesthetics are nice, but I feel like some of the tweaks in Jelly Bomb overlap and interfere with each other. Not sure if this is the case, but its very difficult to sift through 800 pages on Jelly Bomb...
INB4 wrong thread moved to dev forum...
Click to expand...
Click to collapse
There is already a Jellybomb Bug Report Thread here:
http://forum.xda-developers.com/showthread.php?t=2006041
^ Post there.
Sent from my SPH-L900 using xda premium
devynbf said:
There is already a Jellybomb Bug Report Thread here:
http://forum.xda-developers.com/showthread.php?t=2006041
^ Post there.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I posted there.
I still think the question of why these dev's don't talk about the strengths, of their particular roms.
and I'm still confused why a group like Team Venum is working on so many different roms, but they again
they don't really try and up sell or distinguish the differences.
spodemaster said:
I posted there.
I still think the question of why these dev's don't talk about the strengths, of their particular roms.
and I'm still confused why a group like Team Venum is working on so many different roms, but they again
they don't really try and up sell or distinguish the differences.
Click to expand...
Click to collapse
I'm thinking because it's a matter of taste.. Not what's better.. I, prefer labrats.. It's awesome in my opinion whereas the next fellow xdaer might prefer aokp and so on...
Sent from my SPH-L900 using Tapatalk 2
sparytrainor said:
I'm thinking because it's a matter of taste.. Not what's better.. I, prefer labrats.. It's awesome in my opinion whereas the next fellow xdaer might prefer aokp and so on...
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Well of course thats part of it, but there are different levels of users, some of us want a cool theme, and some of us want to really tweak with our hardware, or have specific applications and tasks we want to optimize our devices to perform.
Since you know team nocturnal already and seem to like it, you should come check out the Lab Rats Rom. It is made by team nocturnal and includes the ever popular updater. There are multiple themes and mods, but there are very few apps and theming included on the base install, that way you choose what you want and it's not forced on you.
Feel free to ask any questions in our thread!
{
"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"
}
check out our rom website, http://updater.team-nocturnal.com/labrats/
This is just a pet peeve thing but guys, its CyanogenMod 9/10/10.1, not Cyanogen 9/10/10.1 lol. Not directed at you, just see this a lot in general
To answer some of your question, your apps will work still as the spen still functions as a stylus but some of the more integrated stuff in Touchwiz is not possible. I know on CM10.1, theres some stylus gesture features ive been testing on CM gerrit that bring some of this functionality back.
spodemaster said:
Ok so I've been using Jelly Bomb 13 for a while now.
I've been having issues with it, I'm not sure if its the ROM itself, or if its Just Jelly Bean, and some of the Apps I run.
I'd like to explore other ROMS, but don't want to waste my time, when I'm not clear what some of the roms are offering.
I will start with my observations.
First JBomb 13 issues.
I've had weird problems with the alarm clock, changing its settings, etc...
It does this annoying thing when the lock screen wakes up if I try to lock it again the screen turns of then back on again.
Desktop rotation freezes sometimes.
Lately the entire phone freezes and I have to remove the battery to reboot it.
I don't know if this is related to skype on my phone. Skype seems to be pretty damn unstable on this phone (or all phones).
Sometimes volume control won't change volume for current app being used (probably just Android??)
There is absolutely no way to get the water and ink effect to work on my lockscreen.
Also I had an issue where I powered off the phone, but it powered up as I was removing the battery, and caused all my system settings to reset, as well as screwed up a bunch of my installed programs where I had to manually delete the files, before It would allow me to reinstall the apps. I'm not quite sure that I've fully recovered from that issue a lot of settings I had to go and tweak.
Ok my confusion and Questions:
There are several devs:
Besides their list of things they've tweaked or changed, I'm not really clear on why these are compelling reasons to use their roms.
I've noticed that [Team Nocturnal], has several different roms being worked on, but their sites don't reflect what the various branches are,
or why one may be better for certain users than others.
So my question to the Devs especially ones like [Team Nocturnal] Why don't you make specific distinctions between the various roms. It seems like to many of these roms are obsessively focused on the aesthetic.
I am assuming its more of a ME TOO thing, than "Look what I can offer you" thing.
I really liked "The Blu Khuban" from Team Nocturnal on my EPIC4G touch, I would love something like that for my Galaxy note 2, the update feature was great.
Also I have paid for stuff like Sketch Book and Papyrus, Personally I like some of the general pencil, and ink tools better, on S-Note...
Is it impossible to implement touchwiz stuff in Cyanogen? I used Cyanogen9 on my Epic4G touch and loved it except for they couldn't get the damn Wimax Modem working stable.
At the moment I think I will just go back to a stock de-odexed ROM, and tweak my OS myself as much as I can. Aesthetics are nice, but I feel like some of the tweaks in Jelly Bomb overlap and interfere with each other. Not sure if this is the case, but its very difficult to sift through 800 pages on Jelly Bomb...
INB4 wrong thread moved to dev forum...
Click to expand...
Click to collapse
I would suggest you try Stock rooted Deodexed MA7. Then you can use Titanium to remove some of the bloat.
Then if you want to spruce it up a bit you can flash Morphology (Themes section) to change the status bar, dialer etc.
If you want a custom bootanimation Kevinrocksman (Themes section again) has a nice user friendly zip you flash in recovery and you can select a custom bootanimation.
You do what I suggested above and you will have a relatively bug free experience (unless you delete a system app you shouldn't of touched.)
spodemaster said:
Ok so I've been using Jelly Bomb 13 for a while now.
I've been having issues with it, I'm not sure if its the ROM itself, or if its Just Jelly Bean, and some of the Apps I run.
I'd like to explore other ROMS, but don't want to waste my time, when I'm not clear what some of the roms are offering.
I will start with my observations.
First JBomb 13 issues.
I've had weird problems with the alarm clock, changing its settings, etc...
It does this annoying thing when the lock screen wakes up if I try to lock it again the screen turns of then back on again.
Desktop rotation freezes sometimes.
Lately the entire phone freezes and I have to remove the battery to reboot it.
I don't know if this is related to skype on my phone. Skype seems to be pretty damn unstable on this phone (or all phones).
Sometimes volume control won't change volume for current app being used (probably just Android??)
There is absolutely no way to get the water and ink effect to work on my lockscreen.
Also I had an issue where I powered off the phone, but it powered up as I was removing the battery, and caused all my system settings to reset, as well as screwed up a bunch of my installed programs where I had to manually delete the files, before It would allow me to reinstall the apps. I'm not quite sure that I've fully recovered from that issue a lot of settings I had to go and tweak.
Ok my confusion and Questions:
There are several devs:
Besides their list of things they've tweaked or changed, I'm not really clear on why these are compelling reasons to use their roms.
I've noticed that [Team Nocturnal], has several different roms being worked on, but their sites don't reflect what the various branches are,
or why one may be better for certain users than others.
So my question to the Devs especially ones like [Team Nocturnal] Why don't you make specific distinctions between the various roms. It seems like to many of these roms are obsessively focused on the aesthetic.
I am assuming its more of a ME TOO thing, than "Look what I can offer you" thing.
I really liked "The Blu Khuban" from Team Nocturnal on my EPIC4G touch, I would love something like that for my Galaxy note 2, the update feature was great.
Also I have paid for stuff like Sketch Book and Papyrus, Personally I like some of the general pencil, and ink tools better, on S-Note...
Is it impossible to implement touchwiz stuff in Cyanogen? I used Cyanogen9 on my Epic4G touch and loved it except for they couldn't get the damn Wimax Modem working stable.
At the moment I think I will just go back to a stock de-odexed ROM, and tweak my OS myself as much as I can. Aesthetics are nice, but I feel like some of the tweaks in Jelly Bomb overlap and interfere with each other. Not sure if this is the case, but its very difficult to sift through 800 pages on Jelly Bomb...
INB4 wrong thread moved to dev forum...
Click to expand...
Click to collapse
I'm sure ull probably protest this statement but it sounds like you didn't follow instructions when flashing. I've been using Jellybomb since the inception and I never had one of those bugs on 13. We have to ask ourselves when we run into problems no one else has what did I do wrong? If no one is helping you figure out ur problems no one else is experiencing them. Sometimes jellybomb works better when u dirty flash on top of an older version sometimes a clean install is better. Every rom and every phone is different. There is somewhat of a luck factor when flashing that everyone expects should be universal to all roms and every phone should act the same. I've literally flashed and restored 20x in different ways and combinations to get some roms working perfect. Sometimes u just have to make sure u have all the files to fix ur phone then just play around. You only get more comfortable with the process each time u flash f it up fix it and reflash. It's not as easy as expecting others to figure it out for you but u get more out of it and u won't feel so helpless in the future. Just my $.02. Also pulling the battery in the middle of a boot cycle is never recommended for any computing device. I suspect u could be right in that ur still experiencing issues from that. U should probably Odin back to stock and try again. Also if ur firmware version isn't lk8 then that firmware is not compatible with Jellybomb 13. 13 is lk8 only. The newer 15.3 is a hybrid so u can use any firmware with the rom. And why are you still on 13 when 15.3 is out anyway?
Sent from my SPH-L900 using JellyBombed Tapatalk 2
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.