As the title says, snapshot 2 has been released. Anyone flashed yet?
running good here quick question dies exposed wrk on cm13
Sent from my Nexus 6P using Tapatalk
CM fix the sound bug where the first sound played after a reboot is distorted?
Anyone experiencing the phone app causing the device to reboot? I flashed the 2nd snapshot with the open Gapps stock Gapps and every time I click on the phone icon, the phone reboots.
MichaelDrakeMS said:
Anyone experiencing the phone app causing the device to reboot? I flashed the 2nd snapshot with the open Gapps stock Gapps and every time I click on the phone icon, the phone reboots.
Click to expand...
Click to collapse
I flashed the open aroma gapps, unselected the install of Google dialer and dialer framework and I can make phone calls normally without a reboot when trying to call
Any improvements for the crackling and stuttering Bluetooth audio?
Doughnut643 said:
I flashed the open aroma gapps, unselected the install of Google dialer and dialer framework and I can make phone calls normally without a reboot when trying to call
Click to expand...
Click to collapse
really? Awesome! I am going to try this once i get back home.
Related
Introduction:
This is a pure AOSP built ROM. Nothing has been added to it but for root, busybox, zipalign and kernel that is not secure for ADB . This is for the user who wants a pure vanilla Android experience. I will be back with my AOSP+ Neapolitan ROMs soon which add a few more options.
GApps are NOT included. You can download GApps below.
Info:
AOSP build
JZO54K - 4.1.2
Web Presence:
Twitter
Google+
Would be best to follow me on Google+ for latest updates and news. Sometimes I post stuff there more than I do here...
Change Log:
10/12/12
Updated to latest binaries.
Created add-on GApps package. GApps created from latest JB public images. Missing apps can be downloaded from Google Play.
Fixed Google Now crash.
Dev Tools and SpareParts now part of build.
Enabled Sound Recorder from Launcher.
10/10/12 - First release
Install Instructions:
Install Clockwork recovery if you have not done so
Download ROM
*Wipe cache
*Wipe Data/Factory Reset
Above steps are opitional but at the very least wipe dalvik cache
Install ROM
Reboot
Enjoy!
Downloads:
ROM
HERE
Filename - grouper_412_AU_101212.zip
MD5 - 0d2415836255a60452e32e805203849a
GApps
HERE
Filename - gapps-jb4.1.1-10112012.zip
MD5 - 1dc7ef9363615329545a744484c31112
Credits:
Google, AOSP, Sixstring, Codenamedroid, Braway, Romanbb, CM, peteralfonso, xplodwild and all others that I have gained knowledge and source from.
Einstein quote but modified a bit for this
I am often worried at the thought that my Android development is based to such a large extent on the work of my fellow developers and I am aware of my great indebtedness to them.
Reserved......
Will I get the new bootloader by flashing this ROM?
THX by the way! :thumbup:
Elting said:
Will I get the new bootloader by flashing this ROM?
THX by the way! :thumbup:
Click to expand...
Click to collapse
No...bootloader not included.
You're welcome!
Elting said:
Will I get the new bootloader by flashing this ROM?
THX by the way! :thumbup:
Click to expand...
Click to collapse
Only for a Google device will you see people actually asking for the new bootloader.
Thanks for your work OP.
Thanks a lot, giving this a go right now.
Loaded this without any problems. I've got 4.1.2 and build jz054k. I did have one issue of my own doing. The first time I loaded it I did not wipe data and on reboot I was stuck on the "android" screen. After about 10 minutes I did a complete wipe and then loaded it again and it booted right up.
Not sure if this was an improvement in the build but gps locked on immediately as soon as I loaded up google maps. I don't remember it being that fast before. I mean, it was fast before but it might have taken 5 seconds or so to get a lock. And landscape mode is pretty cool.
Thanks for this.
Hmm Pure Vanilla AOSP has Chrome instead of AOSP Browser now?
mmmmmmm，give you a hug.
Thanks, I needed that.
Downloading for an hour now.....is it really that slow or is it on my end?
Sent from my Nexus 7 using XDA Premium HD app
Anyone having issues with Google Now force closing?
Sent from my Nexus 7 using xda premium
Edit * uninstalled then reinstalled. Works fine.
chappy824 said:
Downloading for an hour now.....is it really that slow or is it on my end?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
It took 5 minutes on my home pc.
I have a CM based ROM on my Nexus 7, JB 4.1.1 .. if i wanna flash this one over, shall i simply follow your same steps ? or do i have to do anything special since i'm running a CM based ROM ?
Thanks
Google Now crashing for me too.
Edit: fixed by removing velvet.apk from /system/app/ and then reinstalling Google Search from the Play Store.
Sent from my Nexus 7 using xda premium
Maybe i am confused, but why did you put this rom in the original section?
So, I ran into a problem. And now I can't get my Nexus 7 to load past the black and whit Google screen when you first power it on.
I was running the stock out of the box 4.1.1 JB that was rooted. I updated my ROM Manager and did a backup, then rebooted, and wiped the Davlik Cache and flashed. After about 30 seconds into the flash ROM Manager received and error and wanted to know if i wanted to reboot. So I did and now i'm stuck. Any suggestions or how i can get it into the correct recovery?
I can get to fast boot, (power and down volume) but when I choose Boot recovery or any option other than power off I just get back to the White Google on black background.
Fixing the Google Now crashing problem too and will have updated ROM with the latest binaries up in a couple of hours.
Updated ROM has been posted.
GApps are no longer included and can be downloaded from first post.
Droid8492 said:
So, I ran into a problem. And now I can't get my Nexus 7 to load past the black and whit Google screen when you first power it on.
I was running the stock out of the box 4.1.1 JB that was rooted. I updated my ROM Manager and did a backup, then rebooted, and wiped the Davlik Cache and flashed. After about 30 seconds into the flash ROM Manager received and error and wanted to know if i wanted to reboot. So I did and now i'm stuck. Any suggestions or how i can get it into the correct recovery?
I can get to fast boot, (power and down volume) but when I choose Boot recovery or any option other than power off I just get back to the White Google on black background.
Click to expand...
Click to collapse
Flash the Google images and start over or find the recovery file and use fastboot to load it up.
Hello.
I have had Remix Res. 3.1.3 as a 2nd ROM for a few weeks now. Recently it became unusable.
When it boots, the start-up animation stutters. When finally boots I right away receive "System UI has stopped" & "android.phone" has stopped".
No buttons are usable. It will just give me one of those errors until I physically remove the battery.
My main ROM is JellyBAM 4.0.0 and is working great.
Kernel on both ROMs is Siyha 5.0.1.
I tried completely removing the 2nd ROM, and re-installing it. I tired a complete wipe/clear and also fix permissions.
Nothing solved this.. What can be causing such problem???
RadicalxMind said:
Hello.
I have had Remix Res. 3.1.3 as a 2nd ROM for a few weeks now. Recently it became unusable.
When it boots, the start-up animation stutters. When finally boots I right away receive "System UI has stopped" & "android.phone" has stopped".
No buttons are usable. It will just give me one of those errors until I physically remove the battery.
My main ROM is JellyBAM 4.0.0 and is working great.
Kernel on both ROMs is Siyha 5.0.1.
I tried completely removing the 2nd ROM, and re-installing it. I tired a complete wipe/clear and also fix permissions.
Nothing solved this.. What can be causing such problem???
Click to expand...
Click to collapse
anyone?
RadicalxMind said:
anyone?
Click to expand...
Click to collapse
I experience the exact same thing. Managed to install RR_JB_V3.1.3_AOKP_4.2.1_I9100 as 2nd rom, tried both kernels, and when it loads up, the boot animation goes frame by frame, and as soon as its done, i get "System UI has stopped" & "android.phone has stopped" until i force a reboot.
wipedcache and delvik before installation, didnt help.
Any directions? could i give any more information that would be useful to identify the problem?
I've three options in mind:
Maybe the free space is to small to that the kernel save this for primary System.
Did u try to update ur kernel?
U both said u wipe and clear all, but did u even do a full wipe? (format data/system/cache)
Sorry no more ideas atm.
CHEERS
Sent from my GT-I9100 running with RootBox
Did you tried other 4.2.1 ROM then RR?
Maybe its a bug with 4.2.1 version at siyah 5 (when its become 2nd rom)
Oh I didn't recognized that it's 4.2.1
I think that's a problem, too, because this need an actual kernel but they don't support dual boot atm.
So I would say no (correct) dual boot in connection with 4.2.1
CHEERS
Sent from my GT-I9100 running with RootBox
Hannibal226 said:
Oh I didn't recognized that it's 4.2.1
I think that's a problem, too, because this need an actual kernel but they don't support dual boot atm.
So I would say no (correct) dual boot in connection with 4.2.1
CHEERS
Sent from my GT-I9100 running with RootBox
Click to expand...
Click to collapse
thanks for your reply, i didnt try any other rom, but what you say makes sense.
good day
Hey guys, I am quite new to this flashing roms, kernals, etc.. I am not a novice when it comes to general programming, just to the mobile devices. Well, I installed Jellyverse 3.0, and at the OS startup (where you would normally enter google account information for sync) It had told me the UI had stopped working. I did this twice to test.. The pull down status bar wouldnt work, no animations, and no 3g on the first run. I decided {MAYBE} and I say that with an extreme giggly voice, I had done something wrong. So, I followed the process again and of course, same problem. The third time I installed, when I got the UI stopped working error (before I made the first selection after install even) I decided to just Reboot the device. Thus rebooted and continued on without any error. My question is what did I miss on the install leading to this problem? I notice I don't have anykind of themed screen transition, is this because of the error? Any response and feed back if aprriciated, Thanks!
Mate did u wipe phone before flash? Try to find romnuke by hawkerpul before flash any rom install that zip
Sent from my GT-I9100 using xda premium
stopro said:
Mate did u wipe phone before flash? Try to find romnuke by hawkerpul before flash any rom install that zip
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you, for your response. Yes, I did try wiping ALL data.. Still have the same error. The phone is up and running, flawless (after a reboot of said error..) I'm just wondering if I missed anything and reporting back for future bug fixes. Is there no screen transition animation to this rom?
That rom.is cm10.1 4.2.2?
Sent from my GT-I9100 using xda premium
This is the pre-alpha thread of OmniROM for the Samsung Galaxy Note 2 (i605). More information can be found here.
This build is very bare bones at the moment. Don't let flashing this now turn you down from trying it again in the future, a lot of changes are coming soon. I would still consider this much more of a tester than a daily driver unless bare bones is your style. The rom is very smooth and fast though probably for that very same reason.
Source:
https://github.com/omnirom
https://gerrit.omnirom.org/#/q/status:open,n,z
https://github.com/omnirom-slickrick
What doesn't work:
You tell me!
Installation method:
Wipe all if coming from another rom
Flash OmniROM
Flash GApps
Reboot
This rom does not come with root by default. Flash SuperSU in recovery if you want root!
Flash at your own risk! No one else is responsible if your device bursts into flames
To try out multiwindow, go to recents and long press an app. Click add to split view and repeat to add another app. Keep in mind its still buggy at the moment
Have fun and enjoy!
For "pre-alpha" this is a very solid stripped to the basics AOSP ROM. Obviously features like customizing and themes will get added in but for now this is pretty good. Basic stuff like wifi, bluetooth, phone, etc are working on my end here. Looking forward to seeing where this ROM goes. Will be keeping my eyes on this.
Excited to see this come together.
Sent from my SCH-I605 using xda app-developers app
Wish I could get this working on T-Mobile. Zip fails in recovery. Any ideas? TIA
Sent from my SGH-T889 using xda app-developers app
dagod80 said:
Wish I could get this working on T-Mobile. Zip fails in recovery. Any ideas? TIA
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I tried messing with the updater script to match that of a tmobile note2, but didnt work
I really want to try this :crying:
Boo so excited for 4.3... my socks are wet
ssmr2t said:
I tried messing with the updater script to match that of a tmobile note2, but didnt work
I really want to try this :crying:
Click to expand...
Click to collapse
There's a working art version on RootzWiki
Sent from my GT-N7105 using xda app-developers app
im definitely excited about seeing this rom come rogether in the future! thanks Rick!
I am not able to get data on this rom.
I have Baseband version Unknown.
As mentioned here, I made sure I am using the latest TWRP... Any ideas?
Taken from here...
Pilatus47 said:
Try to flash the last Rom with the working baseband. And then flash Omni.
Saludos
Click to expand...
Click to collapse
Dirty flash on top of an existing rom with working data? I will try over CM 10.2 to see if that works.
Update: That was a no go. Stuck at boot...
R-Rizzo said:
Are you flashing any LTE fix zip?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I am afraid I have not seen that zip. Is it the one found here?
Update: Tried this and the apns-conf.xml from slick_rick found here just to see if it would resolve the issue but still a no go...
Click to expand...
Click to collapse
PapaJohnMc said:
I am not able to get data on this rom.
I have Baseband version Unknown.
As mentioned here, I made sure I am using the latest TWRP... Any ideas?
Taken from here...
Click to expand...
Click to collapse
yeah i couldn't get data to show up, but I'm okay with that the rom was definitely smooth and I'll have to try it out again soon. thank you Rick! you kick ass like always
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
slick_rick said:
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Here is what I have. I haven't done a logcat in quite some time. Hope this helps!
Thanks
This is my daily driver so I am flashing back to CM 10.2 for now... Gotta be accessible.
slick_rick said:
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'll have to restore my nan and run a log.
EDIT: here's my logcat @slickrick
EDITdos: if that's not enough I'll run another logcat just let me know!
Any progress on the data issue? I tried again and still a no-go on data.
Thanks!
sorry to bring up a semi old thread, but i wonder if because i flashed omni using twrp 2.6.3.0 that's why i didn't have data... ima try with cwm and see if i have data then
EDIT: yup that didn't fix my radio issues..
Data working
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Bluetooth
dturneys said:
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Click to expand...
Click to collapse
I wiped cache and dalvik rebooted and reconnected bluetooth and everything is good.
dturneys said:
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Click to expand...
Click to collapse
This worked for me! Thanks!
Sorry
Sorry, I am going to be "that guy" who proves my ignorance. I would love having the OMNI rom on my i605, but I couldn't get data or voice working. I saw the whole thing about backing up and restoring but I could not get that to work either. Are you working on a 4.3 or 4.4 release?
Thanks
The play google is giving problem, it is closing alone, especially when I click search. I cleared the cache and nothing, do not know what else to do. I'm using the stable version CM10.2 and GAPPS 4.3.0.
And it happens after a while, it always works normal at first, but after a while it starts to close. I installed this rom yesterday. A few days ago I was with this rom and the same thing happened, and I ended up going back to stock. And yesterday I decided to use the CM again and the problem persists.
thank you
tcoteco said:
The play google is giving problem, it is closing alone, especially when I click search. I cleared the cache and nothing, do not know what else to do. I'm using the stable version CM10.2 and GAPPS 4.3.0.
And it happens after a while, it always works normal at first, but after a while it starts to close. I installed this rom yesterday. A few days ago I was with this rom and the same thing happened, and I ended up going back to stock. And yesterday I decided to use the CM again and the problem persists.
thank you
Click to expand...
Click to collapse
Use a different version of gapps Banks or PA or another that's compatible..
tallman43 said:
Use a different version of gapps Banks or PA or another that's compatible..
Click to expand...
Click to collapse
But what? I'm new in these things. I'm using the gapps-jb-20130813-signed
Where do I find to download? I can't find. Thanks
Did u try dirty flashing again rom and gapps? I solved this same issue by cleaning cache and dalvik and reflashing rom again.
sent from Neatrom'd i9300
Now it seems solved. I put the Cyanogenmod 11 and boeffla kernel. I'm 2 days and everything is normal, until the camera no longer crashes.
Thank you all for your help.