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...
Related
Hey this is mainly aimed at Dev's,
How long will it be before a workable 2.2 ROM is cooked up, I think its just come out for the G1 with cyanogen 6, so it shouldn't be too long here?
Thanks guys!!
Cyan's 6alpha is quite usable even now. Just few issues like no preview in camera (but camera is taking photos correctly), and trackball isn't blinking for notifications.
But seems to work stable, and is almost fully functional
zbaracki said:
Cyan's 6alpha is quite usable even now. Just few issues like no preview in camera (but camera is taking photos correctly), and trackball isn't blinking for notifications.
But seems to work stable, and is almost fully functional
Click to expand...
Click to collapse
yeah, and its only a matter of time before all these bugs are ironed out one by one, especially as all the good dev's will be working on a 2.2 rom, they will manage to get everything fixed between them.
I second that, Cyanogemod 6 is working on my phone for the last two days, it's super quick and usable. If you can manage without Sense, it's a real charm.
Datrio said:
I second that, Cyanogemod 6 is working on my phone for the last two days, it's super quick and usable. If you can manage without Sense, it's a real charm.
Click to expand...
Click to collapse
Did u put it on via one of the nightly builds? Because i cant get the graphics to render correctly,
stickyasglue said:
Did u put it on via one of the nightly builds? Because i cant get the graphics to render correctly,
Click to expand...
Click to collapse
Use the alpha0 from CM Forum or the latest nightly from teamdouche buildbot.
(Both are the same version)
rootbox00 said:
Use the alpha0 from CM Forum or the latest nightly from teamdouche buildbot.
(Both are the same version)
Click to expand...
Click to collapse
flashing again now
I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.
FunkTrooper said:
I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.
Click to expand...
Click to collapse
tried the new kernel? i think that will be fixed if you flash it
download
FunkTrooper said:
I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.
Click to expand...
Click to collapse
this one (07/12) works fine
Cyanogen 6 alpha for Hero http://forum.xda-developers.com/showthread.php?t=714923
worked for me
FunkTrooper said:
I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.
Click to expand...
Click to collapse
read the thread about nightly builds. widely discussed with well documented easy to flash fix.
or, do as posted above your post and just get the latest from the new nightly buildbot or the alpha.
The 10/07 build (currently the latest one on the Cyanogen website) works fine for me - just no camera preview and some issues with trackball lights as mentioned elsewhere in this thread.
Works good enough for me to keep it on as my regular rom...
i think at the latest when the legend become its 2.2 update. then we are afloat with legend ports
essbee1958 said:
The 10/07 build (currently the latest one on the Cyanogen website) works fine for me - just no camera preview and some issues with trackball lights as mentioned elsewhere in this thread.
Works good enough for me to keep it on as my regular rom...
Click to expand...
Click to collapse
second that!
Fraqq said:
i think at the latest when the legend become its 2.2 update. then we are afloat with legend ports
Click to expand...
Click to collapse
that would be nice, but it's clear we won't have to wait that long. the only major hickup is the camera and they're working away trying to solve issues with it. Remember this is an AOSP rom (with cyanogen additions and changes), not a sense rom, and hardware support from 2.1 roms is ripe which is I'm sure part of why froyo worked so well right off the bat on the hero (again, other than the obvious camera bug, some media/3d issues (which if I recall seemed to be specific to a couple of apps) and some minor led notification problems).
strange though that the latest alpha build isn't as fast (measurably so and by quite a bit) as the original pre-alpha build was.
Considering the original had a sort-of camera thanks to camera magic it's really a more fun rom to play with than the later builds which ahve working apps2sd etc.
I hope they can get the speed back up.
I have a better question:
How long til 2.2 with Sense?!
any idea?
Desire has it as I know.
liljom said:
I have a better question:
How long til 2.2 with Sense?!
any idea?
Desire has it as I know.
Click to expand...
Click to collapse
froyo with sense seems like htc trying to make the most of the "sense" brand name now. I'd prefer a froyo phone without sense after having used my hero with nonsense froyo for a few days.
does sense on desire 2.2 have anything the older sense versions don't have? if not then it would take features away from froyo (such as froyo's contact integration, froyo's multiple exchange account support with multiple exchange calendars, just to name a couple of great features which are already in the current alpha builds).
UPDATE: I should add that Sense was an incredible thing in 1.5 roms. it's still got sexier widgets than most other non-sense widgets offer, although exceptions exist. But it stomps all over the way android works by offering it's own set of features (like exchagne support with calendar integration for one account).
now with froyo we have almost everythign sense offers and in some cases we have quite a bit better tools than what sense offers.
the worst part about froyo adn all vanilla roms is the dialer, so just download "dialer one" from the market for free and set it as your default dialer. it's at least as good as the sense dialer and integrates well with froyo and with all vanilla roms.
I understand what you say : )
I like the way I can dial people/numbers, I can write sms, I can call the favorites, the calendar widget, the notes widget.
You are lucky that you can get "your" Froyo now : )
liljom said:
I understand what you say : )
I like the way I can dial people/numbers, I can write sms, I can call the favorites, the calendar widget, the notes widget.
You are lucky that you can get "your" Froyo now : )
Click to expand...
Click to collapse
I'm sure you're happy now. I was happy with sense. I didn't understand that vanilla's sms, contacts, and so on are better than those in sense.
if you think your favorites setup is good now, just wait until your froyo setup has finished it's first update (this can take an hour or more if you come from 2.1 with lots of apps installed previously... google will try to reinstall them for you on your froyo rom!). you find your person in the contacts list and have instant single screen click-to-contact with every form of contact that person has enabled. sms, each phone number, gmail, exchange mail, gtalk, facebook, and more. it's quite a bit nicer than sense.
I think you'll like it if you actually give it a chance. Sense's feature list is getting pretty old now by android standards. launcherpro and adw launcher are dramatically better than the sense launcher too, especially imho launcherpro which is the only alternative launcher that is actually faster than the sense launcher even with live wallpaper running and 5 to 7 screenfuls of widgets and shortcuts (as I'm doing now).
I'm just telling you this because I'd hate to see someone disable great features in the new operating system by having sense installed because they don't realize that sense is actually overwriting the superior newer android features with sense's older and less integrated contact and email features.
I wish HTC would release their mail widget as a product for non-sense phones, it's really sexy. but the sense contacts widgets are pretty terrible compared to what's built into vanilla roms with launcherpro (the home screen contact shortcuts are brilliant and very sexy in vanilla). and the calendars from free products like jorte or gemini are excellent, integrated products, and have a great style of their own if you like that kind of thing (but they can only integrate calendars in froyo, not in 2.1 vanilla from my experience... so I suspect those developers will see a big increase in use of their great products in coming months).
sorry, too much caffeine here LoL
cheers
UPDATE: by the way, I don't expect you to say "oh wow, I didn't know that, I'll take your word for it" LoL. I just am hoping you and others will keep an open mind that "vanilla" doesn't mean "missing features" necessarily. seems to be my goal today, I'll stop posting about it now
Everyone's aware of froyd, chronos etc since they're actively being developed by people here but I've been using CM6 nightlies since they started being released and they work great! Music controls for lockscreen and a nice configurable power control widget have appeared in the recent builds. I don't even mind the lack of a changelog, more fun working it out for yourself
So, does anyone else use them? Have a look here: http://mirror.kanged.net/cm/nightly/hero/
:O i didnt know there was still work going into CM6 for Hero. Ive been checking one Github Commits page, there were no updates for a while and assumed ppl had given up!
out of curiosity, whos developing those nightlies?
I'm not sure - it's possible i suppose that the new features are just CM6 bits which happen to work ok and no-one's really working towards making it work better on the hero but lox should be back on the case in a couple of weeks and it's no more broken than the other roms....
Do we need to wipe for these, or can we flash them over the current alpha?
Is the camera working in this ROM?..
sinding said:
Is the camera working in this ROM?..
Click to expand...
Click to collapse
no, trust me you'll know when froyo gets a rom with camera working
[edit] actually, it kinda does... the preview only seems to update when something else is moving though, so for example if you press menu, it will work while the menu animation is going on, also auto focus actually seemed to work. So you can get a half-useful camera if you spam menu constantly or rotate the phone like mad. [edit]
The camera doesn't work right but it doesn't work the same way every time I know i can take photos, I just can't see what I'm taking photos of....
I've flashed each nightly over the previous one all the way back and had no issues, just a dalvik wipe each re-flash.
kieranc said:
... but lox should be back on the case in a couple of weeks ...
Click to expand...
Click to collapse
Exciting news! I was beginning to lose hope that the CM6 Alpha build would ever make it out of Alpha.
For those that didn't see it, Lox tweeted this morning with that update.
https://twitter.com/LoxDev
where can I find google apps for this?
no market??
yeah, you miss things 'cause you need to install google apps
I just don't know where to download
on feeyo's website on froyo 2.2 is a link with google apps
http://www.cronosproject.org/forum/viewtopic.php?f=20&t=198
just not sure if you can flash them over this one..
don't know wich ones are included either, but it's worth a shot
grtz
this is the gaps for CM6 nightlis build:
http://www.multiupload.com/9LJMNBHOXF
and this is the link to the original thread of @maxisma:
http://forum.xda-developers.com/showthread.php?t=717824
maxniper said:
this is the gaps for CM6 nightlis build:
http://www.multiupload.com/9LJMNBHOXF
and this is the link to the original thread of @maxisma:
http://forum.xda-developers.com/showthread.php?t=717824
Click to expand...
Click to collapse
thank you : )
There's a newer version of the gapps for cm6 here:
http://www.multiupload.com/DPC7H4DDFO
kieranc said:
Everyone's aware of froyd, chronos etc since they're actively being developed by people here but I've been using CM6 nightlies since they started being released and they work great! Music controls for lockscreen and a nice configurable power control widget have appeared in the recent builds. I don't even mind the lack of a changelog, more fun working it out for yourself
So, does anyone else use them? Have a look here: http://mirror.kanged.net/cm/nightly/hero/
Click to expand...
Click to collapse
I stopped flashing them when I found zero differences in them between builds that were 3 or 4 days apart.
I'm happy they're adding little things still, but the changes I see in cronos and fusion (in particular) are far more dramatic and useful than what I saw in the nightlies from maxisma et al.
The nightlies were the first, and originally the best (and only) froyo. I loved the original test0 build, it was so solid and fast, but with lots of broken bits.
However with the new cronos from yesterday and fusion as an alternative, and froyd of course which hasn't changed in a while but is always solid, fairly quick and runs well... I'd trust those over nightlies any day.
Nightlies aren't meant for mass use or stability - any nightly could suddenly break things. I know they're pretty solid now but it's because thy're not doing significant things either, adding little widgets etc is nice but not really amazing or anything.
I'll stick with Cronos which I'll bet you performs faster in gpu results.
kieranc said:
The camera doesn't work right but it doesn't work the same way every time I know i can take photos, I just can't see what I'm taking photos of....
I've flashed each nightly over the previous one all the way back and had no issues, just a dalvik wipe each re-flash.
Click to expand...
Click to collapse
that is all exactly the same with all froyo roms on the hero.
so if anything is thinking "hey, well in that case I'll flash the nightly so I can at least get SOME previews and some camera operation", it's exactly as with froyd, fusion and cronos. occasional previews, autofocus that works then makes it out of focus again before taking the pic, some crashing of the phone, some gps getting stuck on with camera magic, zero video recording.
For people who think of changing...
Nightly Builds from 6/8/2010 !
Froyo 2.2
Advantages:
- JIT and Compcache on/off
- Overclockable ( to 710MHz )
- all 2.2 benefits otherwise
Bugs (as far as i know):
- Camera (like all 2.2 roms)
- Landscape in gallery 3D
- Battery life isn't that good (imo)
Scores:
- Linpack: 3,531 MFLOPS (JIT on) / 2.32 MFLOPS (JIT off)
- BenchmarkPI: 10863 ms
Screens in attachments
grtz
I've been using the nightly builds, and like it a lot. I've requested changelogs though, but sadly I still haven't got any response on that matter. I don't notice that much differences between the nightly builds, but a few things I noticed lately:
1) browser doesn't FC when closing the last tab anymore
2) music controls on the lockscreen (provided by koush for CM6)
Would be great if we could keep track on changes in this thread. I love changelogs ;-)
opera mini has stopped working for me over the last few days which has made me realise how slow the stock browser is... might have to do something about it.
edit: opera working again in latest nightly
Figured I'd make a new thread so Fuzz\Skankwitch ports and problems with them aren't mixed up in Quarx's CM9 thread. Helps keep relevant info and fixes for their respected rom easily available and findable. And to put Defy Porting in a centralized place (hopefully) All the relevant Defy Porting, especially CM9, is extremely scattered around here. I know, I wrote most of em. I'll post better porting guide eventually.
The latest build (0616) looks like its gonna be pretty awesome since it merges in even more of Linaro build environment. If you don't know, in a nutshell, Linaro is a new toolchain to compile CM9 with fixes and optimizations to the build environment that allows the compiler to use exotic flags, which in turn makes software run faster.
I'm off today and tomorrow, so I plan on starting that Aroma installed Kang in the next few hours. If you've never build a rock wall, they're a pita and will wear you out, especially when you're alone and the rocks are 200+ft away and you push them in about 260-300 pound loads (slightly) up hill to the wall -- damn I missed having the truck that day. Each rock weighs between 60-180 lbs, and I weigh 180 btw. For you metric guys, multiply by 2.2 to get the kilo version, provided my weed math is correct (~2.2 kilos a pound).
Once the initial framework is done, weekly updates won't be that hard to do since it will only be replacing the core rom and updating a few mods that affect system files (volume step, pdroid if it'll patch).
(reserved for later)
Updated:
here's a port I just made: http://www.sendspace.com/file/hh74un (June 28 FuZZ)
Looking forward to the port with the aroma installer. Hopefully linaro is gonna make our devices more smooth. Thanks skeevy!
corvx said:
Looking forward to the port with the aroma installer. Hopefully linaro is gonna make our devices more smooth. Thanks skeevy!
Click to expand...
Click to collapse
Not sure if its Linaro or the build.prop tweaks I did, but the roms feeling really smooth and hardly any lag -- even when opening the app drawer. Base rom and tweaks are done. Currently going over the scripting and changing it as needed, and it needs quite a few since it started as GB Miui, adapted and extended for V4, and now being used for CM9
Almost done with the scripting. I plan on doing a test install later this evening.
Also working on a deal to get a $40 Defy + shipping -- has a cracked screen, but my Bravo's cracked screen is worse Hopefully the deal is able to go through -- seller is in Australia and my online currency is Pre-Paid Visa.
Any Australian Bravoers able to help me out and pay for it for me and I'll hook ya up with an American Pre-Paid Visa #, with it comes full access to the American Market...It's only $40+ shipping. Seller doesn't know much about pre-paid cards, so I sent more info on them, hopefully I'm over worrying about it and the pre-paid card will work.
I plan on getting a Defy or Defy+ as the "upgrade" to my Bravo. Yes, I know that they're the same phones, but I want a damn torch flashlight, 720p recording, and a Gingerbread kernel with 4 Vsel's.
If this doesn't work out, I'll just get one off ebay in a few weeks.
What sucks is doing a GiS for Defy on shopping leads to a few scam sites selling them (Defy) for $120 -- you're lucky to find them on ebay for that price.
skeevy420 said:
Almost done with the scripting. I plan on doing a test install later this evening.
Also working on a deal to get a $40 Defy + shipping -- has a cracked screen, but my Bravo's cracked screen is worse Hopefully the deal is able to go through -- seller is in Australia and my online currency is Pre-Paid Visa.
Any Australian Bravoers able to help me out and pay for it for me and I'll hook ya up with an American Pre-Paid Visa #, with it comes full access to the American Market...It's only $40+ shipping. Seller doesn't know much about pre-paid cards, so I sent more info on them, hopefully I'm over worrying about it and the pre-paid card will work.
I plan on getting a Defy or Defy+ as the "upgrade" to my Bravo. Yes, I know that they're the same phones, but I want a damn torch flashlight, 720p recording, and a Gingerbread kernel with 4 Vsel's.
If this doesn't work out, I'll just get one off ebay in a few weeks.
What sucks is doing a GiS for Defy on shopping leads to a few scam sites selling them (Defy) for $120 -- you're lucky to find them on ebay for that price.
Click to expand...
Click to collapse
Glad to hear that you are upgrading, please dont stop developing for the Bravo. Looking forward to your realease. I tried syllogyking's release, and battery life is amazing, even wifi tethering is working. With all the scriptings you are adding and modifying I can only expect it to be smoother and better. Thanks.
On a side note: I'm not australian, but I use a local pre-paid visa, to buy online on the US, I use paypal though (ex. transfer from the visa to my paypal account).
corvx said:
Glad to hear that you are upgrading, please dont stop developing for the Bravo. Looking forward to your realease. I tried syllogyking's release, and battery life is amazing, even wifi tethering is working. With all the scriptings you are adding and modifying I can only expect it to be smoother and better. Thanks.
On a side note: I'm not australian, but I use a local pre-paid visa, to buy online on the US, I use paypal though (ex. transfer from the visa to my paypal account).
Click to expand...
Click to collapse
I'm not gonna stop, that's the whole reason I want to "upgrade" to a Defy.
I'll try and make it a point to finish the rom by tomorrow evening -- I have things to do tonight.
I did have an idea hit me yesterday -- an aroma installer that contains only the bootloader, our baseband, a few mods, and does basic Defy Rom Porting. It would be a Bravo repair, mod, and porting tool to make it easy for noobs to use Defy roms w\o the hassle of having to port it yourself and be able to tweak whatever rom you're installing. The hardest part would be the build.prop, but I could include generic props for cm7, cm9, miui 2.4.20. Anyone interested in something like that?
After going to the Defy forums, I find it kind of funny that a lot of the posters giving help are Bravo usres....but it makes since since we need to know a bit more about the phones because we have to do a lot more digging around in order to get the roms working.
very good idea to use Aroma with Defy Roms.
I'd like to test it when it will be done.
Also I'm interested will KANG team accept Bravo for rom develompent ?
Unfortunelly CM, MIUI currently stopped
PsyClip-R said:
very good idea to use Aroma with Defy Roms.
I'd like to test it when it will be done.
Also I'm interested will KANG team accept Bravo for rom develompent ?
Unfortunelly CM, MIUI currently stopped
Click to expand...
Click to collapse
I put doing the actual rom on the backburner for the moment -- I only have time to for the one project now since I have things going on everyday IRL now.
I decided to do the recovery tool since, other than volume step mod, everything else in the aroma rom was universal and a port tool means users can update, have mods and tweaks, and not have to either rewrite or remod the rom for updates -- which occur every few days with Defy Skank roms.
The recovery tool is about 1\4 - 1\3 done.
Planned features include
Defy CM9, CM7, MIUI (GB) Porting
Bravo Greenbread Mod (for MS2)
Reinstall the kernel\devtree\bootloader
Mods for ICS and GB roms
Basic Rom Backup and Restore in Aroma
/data/app backup\restore (for keeping apps in between flashes)
andriod secure backup\restore
system\data\andriod secure\cache\dalvik\sdext wiping (all separate)
Bootmenu Fixes for all roms
Apps only available on XDA or other forums (or banned by google; only legal apps, nothing pirate)
Add init.d support to stock roms
Multiple touch recovery options ??? (a new cwm touch is being worked on, need to use and test it first)
build.prop tweaks
Multiple gps, wifi drivers and settings
init scripts for performance
custom overclocks
add multiboot support to roms
Maybe more??? Will take requests
Still have much to do, as I only have the basic aroma layout done. I still need to finalize the aroma layout, add in a few of the mods, write the updater-script, write the language file, test, test, and test again....
A few of the features I have planned have never been done or attempted with Aroma as far as I know, and may not be in the release (full system backup and restore); but they technically should work. I'm going to try and make the backups CWM compatible, but don't quote me on that, as the md5 scripting may be a pita to do for first release and proof of concept.
I quite surprised Quarx hasn't released an updated 9 yet, with all the updates his git-hub page has had over the past few weeks. I was hoping that he'd stay with the every 2 weeks-ish that he was doing up until now -- not a big deal since we're Defy porting again. I suppose he's just more interested in the Novo7 tablet than the Defy\Bravo roms for the moment. I'd like to hear his review of it, since a dev's review holds more stock with me than a random website catered to end users.
Not sure if the Kang team will accept the Bravo, never asked or even heard it brought up until now. If someone here has a Linux Build Environment setup, go ahead and ask them if they'll help get it setup to start building Bravo Kangs. You'd get better results offering to build it yourself versus asking one of them to do it for you. I might ask when this is done, but might not since I'd be able to run the roms w\o even having to edit the zip once this is finished -- just flash Defy Kang, run Aroma Recovery, port and mod the rom, reboot and enjoy...easy enough I think.
Can we have MIUIV4?
glucky said:
Can we have MIUIV4?
Click to expand...
Click to collapse
Easier said than done....the Defy Miui v4's that we port from are based on Quarx CM9 from March 08. The newer CM9's don't like to be the base rom for v4 porting. Miui v4 is based on pure AOSP roms, not CM9; where GB Miui was based on CM7 and more compatible with CM7 porting.
Since it only takes 30-40 minutes to port and see if it works, I'll attempt porting v4 with the latest skank rom I ported last night. Maybe it'll work, maybe not.
In the meantime, I'm about to upload the yesterday's skank slightly tweaked with 30 step volume mod, Motoinspired CM9 Theme, HWA Selector --- I also have the srs mod installed with it, but frankly, the srs mod has washy treble that I don't like so I'm going to remove it first. I should begin that upload in 40 minutes, with it finishing 40 minutes after that. BTW, the lastest Skank (0628) is really stable and battery efficient (I fell asleep lisnening to music, woke up 8 hours later with 65% battery -- 45% loss with wifi on, radio on, 2 hours web surfing on wifi, 8 hours of music, 6 reboots, full brightness, and installing 20 apps from google sync is very acceptable to me -- means I can listen to music while driving for 12 hour, have about 4-8 talk hours, and have that last for at least 2 days on a single charge.
EDIT: Call of Duty being played in the other room, need to wait for the bandwidth to be freed up before I can upload.
As far as the Port Project is concerned, I have the Aroma layout almost finished (just need to add in an install rom feature), its completely translated for English and ready for multilingual. The rest of the Aroma part will only take 5 minutes or so to complete, then its on to the edify scripting and shell scripting; followed by actual testing of the tool. If I had to guess, 50%+ of what I'm trying to do has never been done in Aroma as far as I know; and if they work as expected, you'll soon start seeing Aroma Roms that install from Nandroid Backups as that's a feature I know Walter79 and espaciosalter20 both want. Expect something in the next 4-5 days as all I really have left is a ton of edify scripting and shell scripts (around 20-30 shell scripts I assume).
Skankport 0628 (NOW UP)
Port to Bravo of Skank CM9 0628
Does anyone here still need install instructions???
--If so, feel free to look in any other damn CM thread, they're all the same
Gapps not included, so flash it as well.
30 step volume mod
Motoinspired 1.4 Theme
HWA Selector 1.5 Beta
Bravia Engine
Vibhinna 1.01 Beta (Multiboot Manager Reloaded)
Defy Apps Removed (Torch, Rom Updater)
DOWNLOAD HERE
I don't think that Bravia Engine is working with ICS roms due to there being no Bravia being mentioned at all in logcat output; you can see it loading on GB Roms; also my first time trying Bravia on ICS. Everything else, however, is working perfectly*. Before enabling it in HWA, Chrome actually loaded and let me enter an address, but only showed a grey screen instead of fark.com which did load....Chrome's almost there.
*Except for camera....
camera isn't connecting for me...when I tried making my own skank port based on your instructions, it didn't connect either. any advice?
also, sio wasn't present (only noop and cfq) according to no frills, so I flashed the droidx zip to get it
syllogyking said:
camera isn't connecting for me...when I tried making my own skank port based on your instructions, it didn't connect either. any advice?
Click to expand...
Click to collapse
Not as of yet....I do know the problem -- its not loading the kernel module correctly. I've already tried the Defy modules, replacing camera.kobe.so with a renamed camera.jordan.so, using the Kobe CM9 camera app, swapping init scripts with Quarx CM9...I'm kind of stumped for the moment, but I've only been at it for about 10 minutes now. I never actually tested the camera, just ported over like usual, which usually works.
I'm just hoping that there isn't a new step in camera porting....
For sio, I didn't fully tweak the overclock.sh like I normally do as a test to see if the scripting would work like its supposed to. Apparently it doesn't....You can remove the 2 governors from the DX zip and also remove the 2 insmod lines for the Governors in the init script to save a bit of ram....and the boosted governor works as well as boostedass anyways. I'm not sure what Epsylon did, but he did do something to it.
Perhaps a better option would be to ask Fuzz for some help in starting up a Bravo build environment. I've built my own CM7's in the past. I'd already be doing the same for CM9, but I've been getting sync errors every time I try to sync with Quarx's Bravo repo since he's been releasing CM9 (usually due to MotoMagic, then I fixed that and couldn't sync with Quarx's personal repo).
The building and compiling isn't hard at all, its just a matter of syncing the repo (which I can't do) and knowing how to use git (which I don't). I'll send Fuzz a pm shortly and we'll see what happens from there.
EDIT: PM Sent; Hopefully he'll help me out in setting up a Kang build environment.
Yeah, I'm fearing there might be some further tinkering that now needs to be done to get the camera to work again. Since Fuzz basically adds cherry picks to epsylon's commits (he pushes mostly tpruvot commits in git), I'm thinking all of this is going to quickly change. The reason being because epsylon has already stated that jelly bean is going to be ported to defy in a few weeks, and that I can believe. But because the camera app is further "improved" in jb, it might still require some more steps to keep us on pace with the "bleeding edge".
anyways, I wish I had the time to read up on Android dev and get started on git, but unfortunately real life is taking priority atm
thanks for the pm initiative. hopefully, fuzz imparts some insight.
Oh the fun fun world of porting never ends when you own a Bravo.
From what I've understood, Jellybean isn't that big of an update so I'm not surprised that they're doin it (and doin it and doin it well). I actually expect them to keep coding until the platform just can't handle the new software any longer without updating the kernel...
I figured out my github sync problems -- the manifest.xml linked to the bravo repo was out dated, so I switched it to Quarx's manifest.xml on his github and have now fully synced it with no problems.
I was thinking that if I was going to ask for help, I might as well try to build it from the repo first (or at least have it all on hand).
If all goes well it should compile in while I'm sleeping.:fingers-crossed:
I'm referring to CM9 & not a Skank Kang, btw.
EDIT: NOW COMPILING, time to smoke a bowl and go to bed.
EDIT2: Didn't compile correctly...
EDIT3: Think I found that problem as well, been compiling for 3+ hours now. Problem was I followed the Bravo ICS instructions to the letter & and they're now wrong. Using Quarx's Defy+ Instructions, modified for the Bravo, are working.
EDIT4: Successfully compiled CM9, going to test it in the next hour or so -- took over 5 hours to build.
My First CM9 Compile
Here ya'll go -- my first compiled CM9 rom. This is basically Quarx 0526 with an updated CM app base. Haven't tested it much, but camera works, it synced with Google and installed all my apps, and it hasn't FC yet. It doesn't have the new hwui.allow feature yet, as I'm still learning git and want to do this all in the proper manner.
Once I learn how to properly sync the Defy repo to the Bravo repo and not screw up the camera is when I'll start to be able to make Bravo Kangs.
DOWNLOAD HERE
Install as usual, gapps not included.
While I don't want to start doing too much too fast, I'd like to add in Pdroid support, use Motoinspired as the default theme (I really like it), add in what ever the Skank roms do, and maybe add in Paranoidandriod to the mix.
I've actually wanted to do this since CM9 was released but I got caught up with v4 porting that went nowhere, v4 Patchrom that's being a pita but getting somewhere albeit slowly, found some work, and finally got COD Elite. I'd post my gamertag, but I'm currently using my Dad's since my PS3 is out of commission for the moment (it fell out of my truck door).
/Dammit, all this has done is set my other project back a few days, but I think we'd rather have Kangs from Bravo source rather than a tool to port them from the Defy.....Anyone disagree with that?
Great works skeevy420 ...congratulation..
Long time lurker, first time poster (which means I can't post in the actual ROM thread). If my thread is inappropriate, please feel free to revise/delete as necessary. If additional information is needed from me, please advise.
By way of background: I have experience with flashing on this phone dating back to Gingerbread with IncredibleHD and MikRunny from "another site". I came over from a Samsung Fascinate where I was also flashing ROMs. So while not an expert in the actual development of the device, I would like to think I am somewhat experienced with flashing ROMs at least.
Incredibly(^<Paranoid2.19.30Final Questions:
With my current flash of Incredibly(^<Paranoid2.19.30Final, I am not running any themes and installation should be basically standard (though I did have to flash the October GApps package over it because there was no way to set up a Google account).
1. Aroma: The Revised OP still talks about the Aroma installer (I know that there have been two versions of the ROM zip in the past). When I flashed 2.19.30, there was no Aroma installer. Bad download or mistake in OP? Answered in Post #4.
2. Camcorder: Regular camera and FFC are working correctly. The OP says that the camcorder has 720p enabled at this point. However, I do not see anywhere in the settings to change the quality of the camcorder, and the camcorder is currently recording at 480p. How do I change the camcorder to 720p? Answered by The Man himself in Post #14.
3. Bluetooth in Car: With the various AOSP ROMs, when connecting the phone to my car via Bluetooth (not A2DP, just a headset profile), I get sound but it is garbled beyond belief while ringing. For any music buffs, the sound is basically the first chord of "I Believe In a Thing Called Love" by The Darkness...as the sound of a phone ringing. Per Rushead's post #710, it appears that Bluetooth headsets and in-call voice are not functional, which is a known issue in AOSP ROMs under ICS and JB with no fix. Has this been resolved in this ROM since "everything" works but LED camera flash? Answered in Post #9 via OP for Incredibly(^<Paranoid Collection.
4. Status Bar Clock: I want to eliminate the clock in the status bar. I go in to the AOKP settings via Settings > ROM Control > Clock > Clock Style and select "No Clock". This removes the clock from the status bar. However, when the phone goes to sleep, and I come back through the lock screen, the clock is back. Going back in to the settings as referenced above, the "No Clock" option is still selected...and yet there is a clock there. If my memory serves me, in Aeroevan's CM10 the option would be under Settings > System > Status Bar, but there is no option for the clock there in Incredibly(^<Paranoid. Obviously not a huge deal, but just curious if anyone has a suggestion. Answered in Post #9; works fine in CM10 so who cares.
Any information or assistance would be greatly appreciated.
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 helpfully suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.
Re: ViperInc headphones
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.[/SIZE]
Click to expand...
Click to collapse
great questions. i am in the same situation...a little experience but not enough forum-cred to post in dev.
i'm currently running ViperInc 1.3.1, just plugged in my el-cheapo RCA headphones and they work fine. sorry bro :-/
i'd love to see some answers to your 2.19.30 questions.
johannvonperfect said:
Long time lurker, first time poster (which means I can't post in the actual ROM thread). If my thread is inappropriate, please feel free to revise/delete as necessary. If additional information is needed from me, please advise.
By way of background: I have experience with flashing on this phone dating back to Gingerbread with IncredibleHD and MikRunny from "another site". I came over from a Samsung Fascinate where I was also flashing ROMs. So while not an expert in the actual development of the device, I would like to think I am somewhat experienced with flashing ROMs at least.
VenomINC 1.3.1 Question:
While my primary questions are related to Incredibly(^<Paranoid as I am digging JB at the moment, as I am already running up my technical support bill I figure I will ask a VenomINC question as well.
I have tried the various Sense-based ROMs under ICS (but VenomINC in particular...same thing, standard install, no themes) and have a giant issue that does not seem to have popped up in that thread: everything works perfectly, with one exception: no audio comes out of the headphone jack. I have tried an aux cable in the car, regular headphones...nothing. This makes the Sense ROMs unusable for me personally, as I spend a good amount of time in the car for work and listen to podcasts/music.
As best I can tell, I believe that this only happens with Sense 4 based ROMs (UKB, ViperINC, EclipticSense over on "another site") but not with Sense 3.6 ROMs (Ascension, the Nitsuj ICS leak) or with CM based ROMs (including Aero's CM10). I will note that I have not tried changing the kernel - I understand that Viper is using the Chinese kernel, while some of the other ROMs have the leak kernel.
The issue was raised in the ViperINC thread by user artcotto in post #s 615, 634, 689, 691, and 693 with no resolution beyond Nitsua98 suggesting that maybe his headphones were broken (they were not). I have flashed the various updates to ViperINC since November and the issue has not gone away. Any information on this would be appreciated as well as I am a bit of a flashoholic and would likely go back and forth between Sense and AOSP (even though as noted above JB is pretty awesome).
Thank you for the great community and for any information and assistance you can provide. Thanks to all the developers for all the hard work you have done for our phone (which was apparently ancient and incapable of upgrade by HTC the second we bought it) allowing me to have a current phone without needing to buy a NEW phone.
Click to expand...
Click to collapse
Have you tried earlier versions of ViperInc? I am using 1.0.2 and have none of the issues I was having with 1.3.1 (which were not your issues - just lag). Another question would be - and I'm not sure this would really affect the jack - have you flashed the firmware?
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
Question number 1: that was a kind of op misunderstanding, a previous version included aroma, while the best one does not, your download was fine
Sent from my Incredible 2 using xda app-developers app
brymaster5000 said:
Have you tried earlier versions of ViperInc? I am using 1.0.2 and have none of the issues I was having with 1.3.1 (which were not your issues - just lag). Another question would be - and I'm not sure this would really affect the jack - have you flashed the firmware?
Click to expand...
Click to collapse
I have not tried going back to prior versions of ViperINC, though I believe I have used from 1.1 onward and had this issue. I didn't mention in my original post, but yes, I have flashed the ICS firmware with the 0320 radio. Maybe 1.0.2 would be worth a try (though I'm not sure there is a way to get old versions of the ROM).
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
This might sound odd. I've been on viper the longest. No lag. I installed super su n un installed their SU. Also got a busy box installer from the market n updated the phones busy box. I'm also running defensed but made sure I popped in rosie, but it's frozen n I'm running nova. Night n day I tell ya.
Sent from my forgotten by HTC Droid Incredible 2. Rooted and Rommed by great minds that haven't forgotten this phone.
johannvonperfect said:
I have not tried going back to prior versions of ViperINC, though I believe I have used from 1.1 onward and had this issue. I didn't mention in my original post, but yes, I have flashed the ICS firmware with the 0320 radio. Maybe 1.0.2 would be worth a try (though I'm not sure there is a way to get old versions of the ROM).
Click to expand...
Click to collapse
fwiw, i also have 0320 radio with headphones working fine. i was previously on ViperInc 1.2.0 and EclipticSense and it also worked fine.
Can you think of anything else you did with your phone around the time you first started experiencing the headphone issue?
vikrantislav said:
fwiw, i also have 0320 radio with headphones working fine. i was previously on ViperInc 1.2.0 and EclipticSense and it also worked fine.
Can you think of anything else you did with your phone around the time you first started experiencing the headphone issue?
Click to expand...
Click to collapse
Not that I'm aware of. As I mentioned above, I don't think it's a "hardware" issue, in the sense that even now I have no problems with CM 10, Incredibly(^<Paranoid2.19.30, etc. My best thought was that it may be something with the way the Sense 4 ROMs interact with the hardware, i.e. maybe the kernel on my particular phone? But I have no idea. At some point I will try flashing the "leak" kernel over the VenomINC install.
What I'm more interested in at this point is 720p recording on Incredibly(^<Paranoid2.19.30Final (And I am looking forward to Chilly throwing together a CM10 ROM).
If we keep going back and forth we can rack up enough posts to start posting at the grown-up table :good:
So the revised OP for what is now the Incredibly(^<Paranoid Collection answered a couple of the questions.
Bluetooth phone calls do not work in any of Chilly's ROMs.
I flashed his CM10, and the issue with the clock in the status bar is resolved. This leads me to believe it is an AOKP/PA issue; I am fine with CM10 anyway so no big deal there.
However, when I flashed CM10, the same issue exists with the camcorder. FFC and regular camera work great for photos; there is no option to change the camcorder to 720p.
Re: ViperINC issue: I flashed ViperINC 1.3.1 again, and this time I flashed the "leak" kernel over it. Still no audio through the headphones. I tried turning Beats Audio on/off, did not do anything.
Only issues I have with Viper is it will not connect to my media server via the native apps. I also have been experiencing lag but I think it's mainly due to lack of ram as a reboot usually clears it up. Also if you toggle gps off it doesn't work unless you reboot.
johannvonperfect said:
Re: ViperINC issue: I flashed ViperINC 1.3.1 again, and this time I flashed the "leak" kernel over it. Still no audio through the headphones. I tried turning Beats Audio on/off, did not do anything.
Click to expand...
Click to collapse
that reminds me, i also have the Sony XLoud disabled in ViperINC
vikrantislav said:
that reminds me, i also have the Sony XLoud disabled in ViperINC
Click to expand...
Click to collapse
I did not install XLoud in the Viper Installer, just went with Beats. As I said in the OP, I know that my issue was previously mentioned but it does not seem like anybody ever found out the cause.
Bluetooth phone calls are not a dealbreaker for me. At this point, if the 720p recording is actually working, I would be happy with CM10 as a daily driver (though I may check out Evervolv as well to see what 4.2 can do). I just can't find the setting...
So what I think I pieced together: the Chilly collection of ROMs does not have 720p recording. When he was talking about the camera being fixed 99.999% except for flash, he was talking about FFC only, and the ROMs do not have 720p recording. I am hoping I am wrong but confirmation would be appreciated.
It may be a situation like the DKStunna thread, where it was proudly proclaimed at the top that "EVERYTHING WORKS", except for the stuff that didn't that you were just supposed to know hadn't been fixed. When Chilly said in Post #875 that "Lol FFC can works ..led flash works but not with taking pictures...video etc works" that does not appear to mean that 720p recording works.
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
johannvonperfect said:
So what I think I pieced together: the Chilly collection of ROMs does not have 720p recording. When he was talking about the camera being fixed 99.999% except for flash, he was talking about FFC only, and the ROMs do not have 720p recording. I am hoping I am wrong but confirmation would be appreciated.
It may be a situation like the DKStunna thread, where it was proudly proclaimed at the top that "EVERYTHING WORKS", except for the stuff that didn't that you were just supposed to know hadn't been fixed. When Chilly said in Post #875 that "Lol FFC can works ..led flash works but not with taking pictures...video etc works" that does not appear to mean that 720p recording works.
Click to expand...
Click to collapse
I had got 720p working but it caused problems so I removed it u caught the thread before the revamp
Currently working on most my roms is
FFC with recording
Tethering with 3party app
I will be implementing fixes for led flash
Blue tooth works but has some bugs
Mostly everything works with fixes that I will be implementing
The pa I upped has fixes already baked in ..I'm yet to try BT yet
Once fixes have been baked the roms will be fully functional minus 720p
Sent from my Incredible 2 using xda app-developers app
chillybean said:
I had got 720p working but it caused problems so I removed it u caught the thread before the revamp
Currently working on most my roms is
FFC with recording
Tethering with 3party app
I will be implementing fixes for led flash
Blue tooth works but has some bugs
Mostly everything works with fixes that I will be implementing
The pa I upped has fixes already baked in ..I'm yet to try BT yet
Once fixes have been baked the roms will be fully functional minus 720p
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
That must have been what happened...I have kept up with the thread fairly regularly and thought I saw that 720p had been figured out, but as you said that must have been before it was pulled. I was confused why nobody was mentioning it in the thread considering it would have been big news.
Chilly, thanks for the response, and thanks for all the hard work you do to make the phone feel like new. We're lucky to have such talented devs keeping our device relevant. Keep doing what you do! :highfive:
To the Mods: that should wrap up this thread if you want to lock it. I do not believe there is an answer to my remaining question about ViperINC and audio through the headphone jack.
Re: [Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs
Hehe even the mods have moved on...
Once everyone leaves this device Verizon will update it like the thunderbolt.
Sent from my Nitsy CM7.
I don't think it was mentioned, but did you try a reflash / redownload?
Probably not going to do anything, but worth a shot.
brymaster5000 said:
Hehe even the mods have moved on...
Once everyone leaves this device Verizon will update it like the thunderbolt.
Sent from my Nitsy CM7.
Click to expand...
Click to collapse
Sweet. I'm locked in my phone till November so I'll be like 1 outta 12 people left with the phone rocking ICS. Sounds exciting
Can usb tethering be done in cm10. I saw the WiFi app thread but nothing on usb.
Not to bump an old thread, but since I still can't post in the actual development thread: Chilly said in Post #1369 of his ROM thread that "No such thing as 100% but yes everything should work other then rotating hard keys bust out the champagne!"
Therefore my question is, once again: how do you change video recording quality to 720p in the camcorder? There still doesn't seem to be an option for it. Any info would be appreciated.
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.