Develop Bugs

Android 2.3 (Gingerbread) Being Pushed To AOSP

http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )

These are very good news
I already see my Hero running CM 7
:happy face:

Excellent News Lets see who get's their GingerBread ROM out first

Sweet, if the hero really will be supported!

Cooooooooooooooool man very nice go go go go gooooooooooooooogle

Tchuup-tchuup! Hotness train is leaving the stations

ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.

dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...

Good news
Sent from my HTC Hero

C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress

I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor

I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero

l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.

Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?

That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project

Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero

I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...

Especially the repo syncing... that just takes ages ;

krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!

Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents

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

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

I can just wait

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Attempting development for Gingerbread. (Long post/discussion)

Hello everyone...I'm planning on trying to develop a gingerbread kernel for AOSP because we don't really have support anymore and everyone has moved onto developing for ICS (not that this is a bad thing). I figure in my spare time I might as well try to learn and develop for our phone. Let me start by saying I was never really into phones/smartphones/rooting, or software development, but I've always been fascinated by Linux in general. I've played around using a number of Linux distros, but I've never really done anything intensive with them (modified their kernels, etc.) but I am vaguely familiar with terminal usage.
Anyways that was just my introduction. I've been running an ICS kernel on my AOSP GB system (specs/stuff in my signature) and while most advised against it, I find it to run pretty well. I'm not sure why it seems to run so well on my phone, but it's basically solved most of my problems (or at least it appears to have done that), but I know the kernel isn't "optimized" for my phone. Some major things people have said are that the ramdisking operations/system is totally different when comparing ICS and GB. This kernel that I'm using is running pretty well, even knowing this fact. What I was wondering is if I could basically get the ICS kernel, then "merge it" with a GB kernel's parameters that pertain to the ramdisk/other major options of GB. That would probably make it better. Also, people stated that multitouch issues for the DINC2 occured on Aeroevan's 0.8 kernel, but not on the 0.7 kernel. This was the changelog stated by aeroevan:
v0.8: Upstream CyanogenMod changes + small touchscreen driver update from HTC. Only tested on my CM7.2 Kang build.
Click to expand...
Click to collapse
So maybe this "small touchscreen driver update" is the thing that caused it, but I'm assuming many other kernels applied this update too? Maybe there is a way to roll back to whatever was in 0.7 in this sense to get rid of the multitouch bug that plagues some people.
I have a pretty powerful laptop, so development shouldn't be too bad. I plan on running Ubuntu 11.10 (or whatever people find suitable these days) in a Virtual Machine and I plan on compiling stuff from there. I am not claiming I know everything or that these things are correct....I am simply just throwing out some brainstorming to get some ideas out there. I know GB is "old", but I (and some others as well) enjoy it's stability and that it generally functions perfectly. Maybe this thread will get a look from popular devs, or maybe it'll get a look from people who just know this stuff. Thanks for reading, and sorry for the length of the post.

Looking forward to your progress on this.
Sent from my ADR6350 using xda premium

It would be nice to have another kernal for AOSP other than aero.

Your help in developing AOSP kernels would be fantastic.
Thanks given. Because I am hard of hearing I cannot use any of the kernels (even Evan's) and have to stick to Sense

[PROJECT][KERNEL] Join your efforts for HOX kernel development

I already saw a lot of kernel developers here, each of them posting their own version.
I don't think that "download sources / fix them / apply patches" by every one of them is ok.
If all could focus on a single source-tree and fix / apply patches to that we would get to a stable/improved version a lot faster.
I can provide a linux machine for the developers interested by this project.
Hardware: 2 x Xeon X7550, 16GB RAM (can be extended to about 60GB), 300GB of storage (can be extended) - RAID6, FC dedicated storage.
Example:
$ time make ARCH=arm clean
[...]
real 0m2.479s
user 0m0.953s
sys 0m1.151s
$ time make -j32 ARCH=arm CROSS_COMPILE=arm-eabi-
[...]
real 1m4.720s
user 19m11.694s
sys 3m23.190s
Click to expand...
Click to collapse
Software:
Slackware 64bit 13.37, gcc 4.5.2, gcc-arm 4.6.1
OS can be changed if you have good enough arguments.
SSH access, no root.
If any developer is interested by an account, pm me with the desired username.
Have fun!

Ok, if no one is interested, I have to start this alone...
BETA
First release - ALiCE Kernel - with patches/tweaks from eternity/franco/bricked kernels and some of my own. Everything seems to work on my HOX.
- Sweep2wake included
- modules built in kernel, no need to flash anything else but boot.img
Attached:
zImage - for including into your own boot.img
boot.img - InsertCoin 5.3.0 boot.img with this kernel.
DELETED ATTACHMENTS - Kernel was virtually unusable.
You can use zImage injector ( http://forum.xda-developers.com/showthread.php?t=1647398 ) to update your own boot.img

I like the idea of this collaboration of kernels.
And I like how the modules are integrated into the kernel.
I'll be testing this out more tomorrow with a battery test for a work day
Keep up the good work
EDIT:
3G Does not work.
As in it shows 3G/H on the top, but no network connectivity.
WiFi does however work.

Great
I'm not a kernel dev, but this seems like a good idea.
Kernel devs working together to create a solid/stable base kernel.
If they want to add specifics they can always release one aside of this.
Also good to integrate modules into boot.img
Keep up the good work.

+1
Good idea, and go on
Good work.

Well I build kernel in 1 minute on i7 920 @4.2 ghz, no need for you machine ;-)
But common git would be nice.. I have zero time to maintain a kernel for HOX
Sent from my HTC One X

It will be nice if we can have a common github repository for the OneX sense kernel with all the patch applies by the devs.
AliceXES, do you have a git link of your repo ?
Because I currently compiling the franco's repo with some config tweek for my own need. And I would like to compiling yours just for testing.
Anyways, thanks for starting your project

Please send me your twitter account it's for helping you

The biggest problems ain't hosting or building times, just version-control. A common Git would be nice, although it seems most changes get picked by eachothers at github.

What about a GitHub organisation? You can have free ones where everyone is admin if you leave the source open. But then that requires a certain level of trust I suppose, heh.

The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.

AliceXES said:
The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.
Click to expand...
Click to collapse
Sad happenings. Hopefully it'll be fixed soon so you'll be back on track!

1: 3G problem indeed lies in the modules (linked to one of the binary baseband module)
2: getting collaborators won't be easy; many (apart from a select few) of today's "chefs" (dare not call them devs) prefer to act alone, get the credits, instead of working together, where the progress would've been much faster. This has been discussed too many a time on xda.
It is so much easier to rip someone's work & claim it as your own... Which is why many a dev resorted to "protecting" their roms (for example, from dumping).
Another reason why not many would like to join you, is that then it would come apparent that they don't have any real skills, since they won't be contributing any patches. ;]

Why compare ROMs with Kernels though? Maybe I'm unique at this, I don't know but, I never really cared about moving files around at ROM level or building AOSP ROMs. I prefer the kernel-space just a bit more
If people are afraid that their commits get stolen (which unintently happened just a few days ago, it seems) they should sign-off it properly.
Ányway I'm always interested in collaborating. Atm I'm just foring Franco's kernel and fixing a few compiling warnings.. I think what we really need is one main-maintainer which holds the master-branch, then the rest of our bunch just can push commits to him for reviewing. Who this lad is going to be, is also a tricky one.

I don't think I will have any success with this project
I started my own kernel thread (here: http://forum.xda-developers.com/showthread.php?t=1662781 ), sorry.
Anyway, the invitation is still open.

[ROM] Jellytime Sosei 4.3

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

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

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

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

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

Go for it.

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

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

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

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

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

unbelievable, I am bewildered by this topic! fantastic!

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

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

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

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

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

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

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

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