Develop Bugs

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

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

I can just wait

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] App Lag, Choppy Scrolling, Slow Loading Apps... Anyone else?

Hi All,
I have had my GSM GNEX for almost a month now and have already suffered from the weird bug of loosing signal for no reason after flashing any 4.0.3+ AOSP ROM ( I have a thread dedicated to this here http://forum.xda-developers.com/showthread.php?t=1487239 ) and I have to say that after using it for a while now, the performance is NOT what I was expecting.
Apps take WAY longer to load on my GNEX then they do on my SGSII both on H Data and on WIFI. Apps include Facebook, XDA Premium, etc...
Scrolling within these same (or any other) apps is very laggy and choppy compared to my SGSII and just general response of the apps is quite laggy compared to the same apps on my SGSII and again this is using both H Data or WIFI.
Has anyone else noticed this at all? If you think it may be ROM based then please see my signature for info.
Does this / Could this have anything to do with the "Force 2G rendering" option in the settings menu? I have not had it turned on since I got my GNEX...
Thanks...

I think you're experiencing the same compare/contrast that I am vs the SGSII. I think it comes down to the gpu (potential cpu as well) influence. My first impressions are that I'll get lag + choppiness when multitasking +/- what those tasks might be.
Also, widgets in the app drawer, forget about it, various kernels and ROMs and drawer lag is typically there with widgets in the drawer for me, at least from a "cold start".
That said, I'm much happier with my GN that I am with my I9100 despite the apparent hw advantages of the I9100.

mudferret said:
I think you're experiencing the same compare/contrast that I am vs the SGSII. I think it comes down to the gpu (potential cpu as well) influence. My first impressions are that I'll get lag + choppiness when multitasking +/- what those tasks might be.
Also, widgets in the app drawer, forget about it, various kernels and ROMs and drawer lag is typically there with widgets in the drawer for me, at least from a "cold start".
That said, I'm much happier with my GN that I am with my I9100 despite the apparent hw advantages of the I9100.
Click to expand...
Click to collapse
Thanks for the reply... I don't have any widgets in my drawer nor do I really have many apps running simultaneously as I'm a bit OCD when it comes to closing apps that I am not using. I have turned on the "Force 2G rendering" option and it SEEMS to have made a SLIGHT difference (at least in my mind... lol).
Also... have you (or anyone) also noticed that the colours / screen on the GNEX just don't "POP" like they do on the SGSII? My colours (compared to my SGSII) just seem very "blah". Could this be due to the fact that the SGSII is SAMOLED + and the GNEX is only SAMOLED? Would it really make THAT much of a difference? Does the option on the SGSII for Standard, Dynamic and Movie really make that much of a difference?

I dont know could be causing this, but mine seems smooth like always. Maybe the SGS2 is just that much better? I dont use 2d rendering either as for me that makes thing laggy and choppy.

I'm using Leankernel 2.2 now and smoothness is great; it's posted in the CDMA dev forum, but is compatible with GSM as well.

mudferret said:
I'm using Leankernel 2.2 now and smoothness is great; it's posted in the CDMA dev forum, but is compatible with GSM as well.
Click to expand...
Click to collapse
That's the other thing about MY GNEX though. As I said... I had the weird bug with my device after flashing any AOSP 4.0.3+ ROM where I would randomly just lose signal ALL TOGETHER making the phone pretty much useless and the ONLY thing that I found that fixed the issue was using the FuGuMod Kernel so I am scared to try any other kernels.
Take a look at the link I posted in my first post for more info. Others have also experienced this bug(?).

Re: signal drop.
I haven't experienced it yet, although I only purchased the phone on Sunday, it was 4.0.3 20 minutes after buying however.

mudferret said:
Re: signal drop.
I haven't experienced it yet, although I only purchased the phone on Sunday, it was 4.0.3 20 minutes after buying however.
Click to expand...
Click to collapse
Mine was flashed to 4.0.3 too almost as quickly and the strange thing is that on Stock 4.0.1 AND on ARHD 4.0.2 ROMS the signal would not drop with the stock OR ROM included Kernels but as soon as I flashed to 4.0.3 the signal would drop like every 5 minutes and the only thing that fixed it was using the FuGuMod Kernel. I am using the UGKL1 radio as well since I am here in Canada and yes... I have tried like ALL the other radios and so far the UGKL1 seems to be the best.

yiannisthegreek said:
That's the other thing about MY GNEX though. As I said... I had the weird bug with my device after flashing any AOSP 4.0.3+ ROM where I would randomly just lose signal ALL TOGETHER making the phone pretty much useless and the ONLY thing that I found that fixed the issue was using the FuGuMod Kernel so I am scared to try any other kernels.
Take a look at the link I posted in my first post for more info. Others have also experienced this bug(?).
Click to expand...
Click to collapse
I have to say that kernel is not responsible for signal loss it is your modem . You should also understand that flashing a rom can't change your modem, only if u flash it manually . So I advice you to visit modem collection topic and try several , the efficiency depends on mobile network you use , so I can't name the best for you. As for me UGKK7 works better than others .
Sent from my Galaxy Nexus using Tapatalk

Speaking about choppiness and lag ... I tried almost all kernels and roms and my verdict for performance hungry : use MoDaCo + Franco kernel 13 .1 or AOKP with the kernel mentioned above . You will be very impressed . But pay attention 13.1 version of kernel not the latest cuz this one is rock stable and very very smooth like nothing else
Sent from my Galaxy Nexus using Tapatalk

beeboss said:
I have to say that kernel is not responsible for signal loss it is your modem . You should also understand that flashing a rom can't change your modem, only if u flash it manually . So I advice you to visit modem collection topic and try several , the efficiency depends on mobile network you use , so I can't name the best for you. As for me UGKK7 works better than others .
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I know it sounds silly that a kernel seemed to fix the signal drop issue as I thought it was weird as well but if you look at my thread (link is in my first post) you will see that it is not ONLY me who has fixed this issue by using the FuGuMod Kernel. There are about 10 others who have posted the same success and some who have posted that OTHER Kernel/Radio/ROM combos have fixed their issues as well when NOTHING ELSE had worked.

In your case, I would go to the Samsung website, and download the stock firmware, and stick with that, just root it, and flash recovery (if it get's erased)
Then check if your problem maintains, if it does, relock bootloader, and send it back to Samsung (warranty) if not, then it's the ROM and/or kernel you had installed with the AOKP ROM...

familyguy59 said:
In your case, I would go to the Samsung website, and download the stock firmware, and stick with that, just root it, and flash recovery (if it get's erased)
Then check if your problem maintains, if it does, relock bootloader, and send it back to Samsung (warranty) if not, then it's the ROM and/or kernel you had installed with the AOKP ROM...
Click to expand...
Click to collapse
I have a nandroid backup of my stock ROM rooted and with CWM and like I said... I do not lose connection while on stock ROM which for me is 4.0.1
I only started losing signal when I flashed ANY aosp 4.0.3+ ROMs until I flashed the FuGuMod Kernel which seems to have fixed the signal loss issue so unfortunately...
Sending it to Samsung for warranty wont do any good cause on stock there is no issue and if I send it back while on a custom ROM they will void my warranty so I'm kinda hooped either way...

[Q] Questions re: Incredibly(^<Paranoid2.19.30Final, Sense-based ROMs

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.

[Q] How stable and reliable are the Android 4.4 ROMs?

At the moment there is no stable and reliable Android 4.4 ROM yet, but I hope this will soon change.
Perhaps we can compare the different ROMs here. Please note that I am not asking for best performance or lowest RAM requirement. These are secondary issues. The most critical issue is reliability.
The Google ROMs have always been the most stable and reliable. They were never perfect, but at least we could expect them to run for a week or longer without any significant error and without rebooting. In my experience, other ROMs, like the admirable CyanogenMod, came close, but never quite reached that same level of reliability. Given that the CyanogenMod crew works for free and in their free time, the quality they delivered has been astounding and admirable.
Nonetheless, reliability remains the biggest issue among the third-party ROMs.
So, if you install any of the Android 4.4 ROMs on your Galaxy Nexus, please report what you find. Please try to judge whether that ROM can be recommended for general use or whether the newbies had better stand back and wait for the next version.
Another question is: How user-friendly is the install procedure? Can you keep your apps and app data?

It is very unfortunate that the gnex community is not supported anymore due to 'hardware issues' or the 18 month timeframe. It is true that the ROMs made these days are not so 'reliable' and they may be buggy and cause force closes on certain applications. The new roms may never support cleanly and as stable as stock factory images by Google but its all the Gnex community can rely on from now. Personally, I feel the slimkat 4.4 ROM is acceptable considering it is only about less than a week old. They have been fixing bugs such as GPS tracking and such. I will be using it as my daily driver from now and just hope that the developers can make it as stable as the stock android ROM.
Sent from my Galaxy Nexus using xda app-developers app

a taste of kitkat perfect aosp leaked rom
i''ve installed yesterday a taste of kitkat with mpokang 1080p kernel.. some glitches when rotate screen but only one reboot using google now (i don't use gnow so it's not a problem for me) and i've a crash only on fifa14... battery good performance, no lags, no problems, trickstermod overclock to 1.4ghz no problems, facebook, whatsapp, viber, tango, hangout, 3G, Wifi, Bluetooth, GPS alla working without problems.. and now i'm testing battery..

Toro Plus
For us sprint (or Ting) users the 4.4 ROMs are not even installable. There have been two threads started and each one was locked after it became apparent that the developers did not have booting builds. I appreciate all the work devs do, but this keeps getting my hopes up. Hopefully, someone will get one working soon and we won't have any more false starts.

They are just alpha builds, experimental builds. Most of them have some glitches. They are not for daily use.
If you do not have necessary knowledge and do not have time to report bug, then I suggest you should back out on those alpha builds.

They're not even a week old. Give time and reap miracles afterwards
Sent from Samsung Galaxy Nexus @ CM10.2

It's a Nexus device. Things will improve over time.

I've been running the most recent SlimKat alpha build and it's been pretty solid. Phone feels rejuvenated. It is my work phone and worked flawlessly all day. The only restarts were Hangouts last night and when I was fiddling around with wallpaper settings after work, and forgivable graphics glitch during screen rotation. Otherwise, it has has felt like a new-ish phone today.

Thanks for the good information!
I think, when the builds go from alpha to beta and there are no obvious glitches any more, then would be the time to do some more thorough testing, particularly:
GPS, including track recording with My Tracks, Locus, or a similar app
Cameras with all their functions
Compass, gravity, and other sensors
Tethering via USB, Wi-Fi, and Bluetooth
Radio functions, particularly LTE and the general behavior with a weak or frequently interrupted signal
OTG with USB mass storage device, keyboard, etc.
I would recommend to report all defects not only here, but also to the maker of the ROM.

For now, they are pretty unstable, but I would keep an eye out for linaro's builds as well:
http://www.cnx-software.com/2013/11/06/android-4-4-kitkat-on-galaxy-nexus-rom-linaro-and-petition/

idk what you're talking about OP. i've run these custom roms more tha n week and they've been good. only reason the counter will reset is because I flash a new rom or flash an update or a mod.
These ROMs are very stable.
4.4 ROMs. give it some time. it's amazing that in less than 24 hours after the release of 4.4, we got a semi daily usable ROM from people that don't even work for Google.

I've been on SlimKat for a couple hours now. Clearly a ton of the SlimRom features are missing but considering that its an Alpha its not that bad.

Other than some graphical glitches here and there, which are very rare actually, there arent any other instabilities that I can see. Everything works fine. I dont know who is starting this rumor about 4.4 being unstable. Some ROMs may work better than others but thats due to different developers working at different paces. Bottom line is, 4.4 is perfectly fine for a daily driver. It just needs some ironing out.

Yeah, I'm running the SlimKat ROM, and its beautiful
Sent from my Galaxy Nexus running the Forbidden Update using xda app-developers app

Running Shiny 4.4. Good taste of KitKat. Sounds crazy, but I'm using it to test stuff out before it goes on the N5.
Biggest glitch seems to be with graphics, in that overlays of menus and random black boxes over some text in gmail and Chrome, make things unreadable and useless. Not to mention the random reboots when you can tell something happened that the GNex doesn't like.
IMO, they are not ready for use on a primary device. As in, at the end of the day, when I'm home, I pop my simcard out of my MotoX and out it in my GNex/3.4 to tinker. No maps to crash at the wrong time, I have other devices at the low-ready to surf on and more time to tinker. My gf loves me for this routine I've made for myself

Definitely a good taste of KitKat. Considering today would mark 1 week since release, on an unsupported device - its actually pretty stable.

LCD Density
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?

xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
use rom toolbox, it worked for me
Inviato dal mio Nexus 7 con Tapatalk 4

xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:

Thanks - I was rooted already and made sure root explorer was on. Tried to change permissions in terminal, didn't work. Booted into recovery and mounted system, rebooted and hung at the google logo...so flashed FML and the DPI is 320 so I'm fixed
joytsay said:
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:
Click to expand...
Click to collapse

How are newer versions of the stock rom these days?

I'm currently on the summer 2021 release of the Verizon stock rom based on Android 11 and ONE UI 3.1, but have been hearing about newer versions based on Android 12. I'm fairly happy with the performance of the existing combination, (the speed and battery life are nothing short of epic) but have never found a solution for the longstanding bug where audio playback inside of Shazam is choppy.
My question to the community is if newer builds of the stock rom fix the choppy Shazam audio playback, and also, whether or not they break the Wichita version of the Google Camera app, which I rely on extensively (unless there's a less-broken distribution that I haven't heard about yet, in which case, lay it on me!).

Well, I finally bit the bullet and chomped down all the dirty/in-place updates for both the stock rom based on Android 11 and Android 12. After I inserted a T-Mobile-branded sim card, it set off a whirlwind of changes, including switching the stock rom from the Verizon rom to the T-Moible one all by itself somehow. Lots of nasty packages to disable, but it calms down well enough after doing so. Among other things, the T-Mobile stock rom is extremely aggressive about software updates. I let it push me around this time, but after getting through the batch, I did disable the obnoxious & pushy updater.
I can confirm that choppy Shazam audio was fixed by one of those (can't remember which one) and that the Google Camera app still works in the new rom, so that's a win. The sidecar widgets are degraded, and the little animation that appears when power is connected looks kind of weird, but everything else is alright, except for the horrible widget shaping on the newer stock Samsung launcher. Also, the friendlier band switching menu is stripped out, requiring use of the dialer code to prompt the more primitive one.
If anyone was on the fence about it, as long as you're okay with those minor caveats, I'd recommend going along for the upgrade.