Develop Bugs

[ROM][29July2013] mROM v4.0 JSS15J - stock 4.3 + GAPPS, MOD(s), etc.

Here is a 4.3 ROM built from AOSP source designed to emulate what a Verizon 4.3 ROM would be like. The changes from AOSP include the addition of GAPPS, addition of Verizon apps, appropriate binaries so everything works, addition of busybox, correct eri.xml, home screen layout to mimic a stock ROM, and the removal of the tethering restriction. The ROM is not pre-rooted, so flash Chainfire's SuperSU if you want root.
As usual, flash at your own risk and post any successes or problems.
Download Link(s) for v4.0: MD5: be4377ab16432112f09d18ae37c91041
DOWNLOAD via Goo.im
Cubby.com MIRROR
SuperSU v1.51 - you may want to check for a more recent version if this link becomes outdated. Flash after you flash the ROM.
Bugs - text-to-speech may not work correctly. Please flash fix attached to this post after flashing the ROM. Thanks AndroJak!
MODS:
Extended Power Menu - CM style
- Ability to reboot, hot reboot, reboot recovery, & reboot bootloader.
- Replaces /system/framework/android.policy.jar
- Thanks to Cyanogenmod and xIC-MACIx
- DOWLOAD
- MIRROR
Thanks to mmuzzy for help building from aosp (fixing t-cdma64 in eri.xml and cell broadcasts menu, plus other stuff I'm probably forgetting), adrynalyne, and djp952 for help building from AOSP.

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
about 5 min or so....
Click to expand...
Click to collapse
first cant wait!!! ^.^

Here we go!!!!!

Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.

Download for 1 server is ready now. I'll get a mirror up as well.
BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
Yes, it's working. I asked it how long a bridge was and it read the answer back to me. I haven't done much more than that though yet.

Downloading. Looking forward to this. Thanks Mwalt for sharing!!!
Quick DL as well. 2 minutes has got to be a new record for a JB rom

BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
OP says Google Now is working. I'm downloading now.

excellent. you're a regular johnny on the spot!

downloading now, hope its all good! i'm looking for a "stock jb" style rom of the newest update. ill post my outcome shortly. going to test the basics that are supposed to work.

Is a flash to the JB bootloader recommended? Finally, a build that seems to have all/most components working! No issues with the 4G's or the LTE's?? Lol.
Galaxy Nexus - Slim ICS 4.2

Downloading now. Any thoughts on current JB kernel compatibility?

i wiped data, cache and dalvik cache 2x each, installed and installed trinity kernel on top and hit reboot. (i like trinity for the colors and such, and good battery life ).
first boot took a minute.
updating some apps and gonna test some things.
still getting t-cdma 64 as a carrier

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
DOWNLOAD from Dev-Host
MD5: 8383b87cc2f9e5b510807c3034052ffe
Click to expand...
Click to collapse
Any issues in this build? Also, what are the install instructions?

when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?

^System/media/ringtones maybe?
Galaxy Nexus - Slim ICS 4.2

works well so far. thanks!

xweaponx said:
Downloading now. Any thoughts on current JB kernel compatibility?
Click to expand...
Click to collapse
I've always used stock, so I can't really comment. Now that source is out, I'd expect the JB kernels to work better.
imablackhat said:
still getting t-cdma 64 as a carrier
Click to expand...
Click to collapse
No sure what causes this, but I've never seen it with this build or the previous developer preview build. Did it happen on first boot before you installed anything else?
tycoon177 said:
Any issues in this build? Also, what are the install instructions?
Click to expand...
Click to collapse
I'd recommend a full factory reset, but people can try what they feel comfortable with. Personally, I did a factory reset, wiped both caches, and then flashed the ROM (with TWRP).
imablackhat said:
when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?
Click to expand...
Click to collapse
Do you have any on your sdcard partition in the Ringtones folder? If not, I'd check \system\media\audio path (subfolders for ringtones, alarms, etc). Delete any duplicates you find in there. I don't have any duplicates and there aren't any in the rom.zip I uploaded.

just overwrote mms.apk in system/apps to get the custom pink mms, and got a quick reboot to my boot screen, this never happened on 4.1 roms that weren't source, don't know if this is normal because i replaced the app and it was a one time thing (i hope). as far as going to system/media/ringtones, i see them but there arent any doubles, however theres doubles when i go to select a ringtone from the menu, for everything system related, ringtones and notifications.

What issues have people had? Any boot issues?

I replaced the "stock" keypress ogg files from ics/jelly bean that sound better with this 4.1.1 release, the new key click sounds are horrible. works fine. i used to have t-cdma 64 with any build from 4.1.1 there is a fix that works that ill just apply. its a xml file or something.

No Thread for LiquidSmooth 4.2.2 RC1 Toro

I'm currently running the LiquidSmooth 4.2.2 RC1 ROM for my Vzw Samsung Galaxy Nexus (Toro). I see the threads created for other devices but not the Toro.
Running great so far but would love a place for discussions on what few bugs people are able to find to help with the next build.
Found bugs:
Crash when opening LiquidSmooth Settings for lockscreen
Goo Manager is appearing as pre-installed but can't be found on the phone outside of Manage Apps and can't be uninstalled or installed over.

joshwoods said:
I'm currently running the LiquidSmooth 4.2.2 RC1 ROM for my Vzw Samsung Galaxy Nexus (Toro). I see the threads created for other devices but not the Toro.
Running great so far but would love a place for discussions on what few bugs people are able to find to help with the next build.
Found bugs:
Crash when opening LiquidSmooth Settings for lockscreen
Goo Manager is appearing as pre-installed but can't be found on the phone outside of Manage Apps and can't be uninstalled or installed over.
Click to expand...
Click to collapse
Both of those issues confirmed for me. Also FC when trying to set up swiftkey
Workaround for this: restore swiftkey using TB, then go into the settings and set swiftkey as your input device.

Agreed - i noticed exactly the same with RC1. As well I noticed:
- about -> status -> phone number not showing
- about -> status -> bluetooth address not showing
I also tried RC2 and after rebooting I got a polish (i think that was the language) message, that would not go away (no matter how many times i pressed 'ok'). So i reverted back to RC1.

CM Version Updates

Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.

Invalid_GR said:
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Click to expand...
Click to collapse
CM will handle the CM version. Oppo will supply updates to their software, but CM will handle the actual ROM itself.
Right now there's only one build released. I have a new build that I'm checking out now, but it's still on 10.2. We should see CM11 very soon, and I predict that it will come with the official Google software built in, so there won't be a need to flash gapps. I might be wrong about that, but I think that's how it will work.
I'll post the link for the update very soon in the correct section.

Invalid_GR said:
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Click to expand...
Click to collapse
Software should be coming out tomorrow, can't wait.
Cyanogenmod does have their new CM Installer software for Windows and Android. If you're not familiar with fastboot, installing recoveries, and all that....it may be the easier way to go....in fact, I'm curious to try it myself.
http://www.tomshardware.com/news/oppo-n1-cyanogenmod,25495.html

I am more interested to see how this will work not only for the N1 but for future CM phones.
Imo if they want to go official they should provide the stable versions OTA to begin with.

Harfainx said:
CM will handle the CM version. Oppo will supply updates to their software, but CM will handle the actual ROM itself.
Right now there's only one build released. I have a new build that I'm checking out now, but it's still on 10.2. We should see CM11 very soon, and I predict that it will come with the official Google software built in, so there won't be a need to flash gapps. I might be wrong about that, but I think that's how it will work.
I'll post the link for the update very soon in the correct section.
Click to expand...
Click to collapse
I'm fairly certain that CM11 won't have included gapps until an official "stable" release occurs.
Only the released version of 10.2 has been approved by Google.

Entropy512 said:
I'm fairly certain that CM11 won't have included gapps until an official "stable" release occurs.
Click to expand...
Click to collapse
I'm talking about the official build of CM11. Steve Kondik has informed me that the build is almost ready to roll. They're just waiting on a few last details... Which I assume is the inclusion of gapps.
Sent from my HTCONE using Tapatalk

All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.

[Q] OTA Installer installs vanilla Android?

I used the OTA app on my Nexus 7 (flo) to update to 4.0 beta 3 and when the tablet rebooted vanilla Android was installed. The boot icon is still Paranoid Android, but halo, pie controls, and all the customization settings are gone. Am I doing something wrong? It seemed like a fairly straight forward process.

StormConjurer said:
I used the OTA app on my Nexus 7 (flo) to update to 4.0 beta 3 and when the tablet rebooted vanilla Android was installed. The boot icon is still Paranoid Android, but halo, pie controls, and all the customization settings are gone. Am I doing something wrong? It seemed like a fairly straight forward process.
Click to expand...
Click to collapse
Read the change logs...it's not vanilla. That's the intended look however

Anu6is said:
Read the change logs...it's not vanilla. That's the intended look however
Click to expand...
Click to collapse
So those features just haven't been introduced into the new version yet?
It would be nice if the update app didn't pester me to install a new version if it's not finished.

StormConjurer said:
So those features just haven't been introduced into the new version yet?
It would be nice if the update app didn't pester me to install a new version if it's not finished.
Click to expand...
Click to collapse
I don't see how it's pestering you. You can turn off notifications.
It's doing what it is supposed to do, which is inform you of an updated version.

OmniROM

** If you are interested in taking over the project, pm me **
Offical Site
XDA Forums
Google+
Twitter
Facebook
IRC(User)
JIRA
Disclaimer
Flash at your OWN Risk
How to Install
Install TWRP
Factory Reset
Format System
Install ROM
Install Google Apps
Install SuperSU
How to Update
Goto SuperSU -> Settings -> Install SuperSU backup script
Goto Settings -> About phone -> System Updates -> Check now
This will download and install latest OTA
DOWNLOAD
TWRP
ROM
Google Apps
SuperSU
Known Issues
Developer Stuff
COMPILE YOURSELF
Github
Gerrit
IRC(Dev)
Changelog​
XDA:DevDB Information
OmniROM, ROM for the Sprint Samsung Galaxy Note II
Contributors
UtkarshGupta, XpLoDWilD, Entropy512, OmniROM Team
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SPH-L900
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: Nightlies
Created 2014-04-10
Last Updated 2014-12-08

Nice

My name is Skripka and I approve of this. :good:

Excited to try this out. Read up on OmniRom, I am particularly interested in the multi-workspace piece.
I just started working with JIRA at my workplace, I was just thinking today that it would be great for Rom developers.
Sent from my SPH-L900 using Tapatalk

this rom is really awesome; esp with plasma. nice to see it in development thread finally:good:

cmart4 said:
this rom is really awesome; esp with plasma. nice to see it in development thread finally:good:
Click to expand...
Click to collapse
Definitely might have to try this rom. It's either this or Paranoid.. not sure what the difference are Really want to get Plasma going though!

slick_rick said:
...
Known bugs:
- Check sbrissen's CM11 thread...
Click to expand...
Click to collapse
Out of curiosity, I thought that Cyanogen and Omni were separate since CM went commercial..? I thought that some of the CM devs (like Chainfire, XplodedWild, and Dees_Troy) were upset with that and decided to start their own ROM (hence OmniRom)...
Regardless, I'm very excited to see OmniRom has its own page now in our Android Development. It will make it much easier to see how each nightly performs and if there are any bugs that need to be reported.
Additionally, there's a lot of info/support/feature requests/etc here.
Thanks slick_rick!!

altimuh said:
Out of curiosity, I thought that Cyanogen and Omni were separate since CM went commercial..? I thought that some of the CM devs (like Chainfire, XplodedWild, and Dees_Troy) were upset with that and decided to start their own ROM (hence OmniRom)...
Regardless, I'm very excited to see OmniRom has its own page now in our Android Development. It will make it much easier to see how each nightly performs and if there are any bugs that need to be reported.
Additionally, there's a lot of info/support/feature requests/etc here.
Thanks slick_rick!!
Click to expand...
Click to collapse
They are separate for the most part but I am using sbrissens cm11 device tree as a base for omni l900 tree so any bugs there will be here.
Sent from my Nexus 7 using Tapatalk

slick_rick said:
They are separate for the most part but I am using sbrissens cm11 device tree as a base for omni l900 tree so any bugs there will be here.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
On Omni's page they talk about mulitwindow being up to the individual dev who brings it to each device. Is it possible to get that added in the future, or is that going to be up to Omni?
Thanks for the info and thanks for your hard work!!

Thanks for all your hard work and not given up on us like people's. Just downloaded and look forward to trying it out. On a side note I've been spending all my free time in the XDA University forums trying to teach myself how to compile and build. I've got Ubuntu and all the tools but having a 14 month old son n being a single dad in the evenings haven't given me much free time to practice and read.
So i can appreciate all the time and effort you put in to doing this all.

Thank you slick-rick for this great ROM. For me, everything is running flawlessly so far but I have a question. I used Phil's Touch to install the ROM originally and as I mentioned it's running great. This morning I checked for an update and there is a new nightly available. When I went through the process to install the nightly it said that it was only compatible with TWRP. Is this correct, or is it OK to continue with the installation even though I have Phil's Touch? Thank you again for all your work.
Sent from my SPH-L900 using XDA Premium 4 mobile app

davesbest said:
Thank you slick-rick for this great ROM. For me, everything is running flawlessly so far but I have a question. I used Phil's Touch to install the ROM originally and as I mentioned it's running great. This morning I checked for an update and there is a new nightly available. When I went through the process to install the nightly it said that it was only compatible with TWRP. Is this correct, or is it OK to continue with the installation even though I have Phil's Touch? Thank you again for all your work.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which Nightly did you install? Any nightly build after 1/10 or so should be able to OpenDelta update script via PhilZ/CWM just fine.

Skripka said:
Which Nightly did you install? Any nightly build after 1/10 or so should be able to OpenDelta update script via PhilZ/CWM just fine.
Click to expand...
Click to collapse
I haven't installed a nightly yet. I was waiting to make sure i could do it with phils. Thank you so much for the help. Going to install it now.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Well, that didn't go so good. When I go to system update and do "flash now," it boots to philz recovery but I keep getting "installation aborted" messages. Any ideas?
Thanks. Dave.
Sent from my SPH-L900 using XDA Premium 4 mobile app

SuperSU won't allow me to update binary and tried to use root explorer stated that I didn't have root. ?
Sent from my Transformer TF101 using Tapatalk

Is anyone else getting high Google Services usage? It's the highest usage listed in the battery settings

EGOvoruhk said:
Is anyone else getting high Google Services usage? It's the highest usage listed in the battery settings
Click to expand...
Click to collapse
Check your wakelocks...I saw it and made it go away by changing location to "Device only".

'no service' issue
I had this rom running for a couple of days, then had an issue with an app (xbmc), and decided to go back to macksrom....didn't realize that once you install 4.4.2, you can't go back to 4.1.2...anyway after trying to restore to macksrom failed twice on the data restore, I went ahead and reloaded omnirom, and worked through the xbmc issue....didn't realize until my wife found me at the grocery store that after bringing it back via restore I had no service...and I couldn't find anyway to get service either....
Is this a known issue, or do you know if I did something wrong?
---------- Post added at 07:41 PM ---------- Previous post was at 07:20 PM ----------
hinesw said:
I had this rom running for a couple of days, then had an issue with an app (xbmc), and decided to go back to macksrom....didn't realize that once you install 4.4.2, you can't go back to 4.1.2...anyway after trying to restore to macksrom failed twice on the data restore, I went ahead and reloaded omnirom, and worked through the xbmc issue....didn't realize until my wife found me at the grocery store that after bringing it back via restore I had no service...and I couldn't find anyway to get service either....
Is this a known issue, or do you know if I did something wrong?
Click to expand...
Click to collapse
Just did a complete re-install of the omnirom zip file....seems to be back to normal. Of course, now I have to get all my apps back on and placed the way I like 'em....oh well.

Skripka said:
Check your wakelocks...I saw it and made it go away by changing location to "Device only".
Click to expand...
Click to collapse
Tried this for two days - one mostly on WiFi and one out and about. First day on WiFi I got waaaaaaay better battery, but the second day I got not so good results with Google maps - it took a while to "find my location"....also with location set to 'Device Only', I got high battery use from the weather channel app I have installed, and Dashclock widget can't find my geo location and report.... I think I'll take the slightly higher battery drain with a fully functioning GPS setting.
Thanks for the tip though - it could be super handy for someone mostly on WiFi.

altimuh said:
Tried this for two days - one mostly on WiFi and one out and about. First day on WiFi I got waaaaaaay better battery, but the second day I got not so good results with Google maps - it took a while to "find my location"....also with location set to 'Device Only', I got high battery use from the weather channel app I have installed, and Dashclock widget can't find my geo location and report.... I think I'll take the slightly higher battery drain with a fully functioning GPS setting.
Thanks for the tip though - it could be super handy for someone mostly on WiFi.
Click to expand...
Click to collapse
If you're not traveling, just set DashClock's location manually. Can't vouch for Weather Channel's app, but Weatherbug Elite plays fine with it and doesn't care.
The location pinging with Google Now is insane...and there's no way I know to stop the thousands of location wakelocks short of changing the location preference. Not even changing the app permissions for the location services does any good. And that isn't just an OmniROM issue, but for ever 4.4 ROM I know of.