yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
What happens when you combine mind-blowing speed and talent?

You get VANIR, b*itches.

I'm NOT the developer of this ROM.

.

Features:

-Halo 2.0

-Android 4.3 (JSS15Q)

-PIE

-AppBar

-Freaking insane speed

-Custom toolchains, -O3, OptiPNG, bionic, krait, and dalvik performance commits, -fstrict-aliasing, custom CFLAGS, and MORE!

-A Vanir performance on/off toggle

-UI mode switcher

-Tablet statusbar split

-etc (But seriously, this frickin' thing is PACKED with features).

Install:

1. Make sure you're on the latest 4.3 TWRP 2.6.1.0
2. Make a backup
3. Do a full wipe -- Cache, Dalvik Cache, Factory Reset, System --
4. Flash Rom
5. Flash 4.3 Gapps
6. Reboot
7. Let phone sit for 10mins
8. Reboot -- Have fun!!

Downloads:

ROM -- [url]http://d-h.st/yqk[/url] -- Sep 07 '13

Gapps -- [url]http://goo.im/gapps[/url]

Not Working:

Fails to Mount/Detect sdcard
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Source:

Vanir Rom Source Code -- https://github.com/VanirAOSP

CyanogenMod Kernel and Device Source -- https://github.com/CyanogenMod

Thanks/Credit:

I take no credit for this rom. I just compiled it for our device from Vanir Source using CyanogenMod kernel and device.

Team Vanir
CyanogenMod
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] stoopendis:
Twrp 2.7.0?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
http://xdaforums.com/show...postcount=4588

Yes, 2.7.0 is the one I use. The official 2.6.1.0 should work fine too. Just haven't used it. Added link to the OP
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
A new fix for my flashaholic tendencies. :eek:

Downloading now and will report back. :highfive:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
I had problems with twrp 2.7 restoring my old nandroids on my SD, it doesn't read it. Anyhoo, looking forward to this one. Your a machine bro!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
I actually haven't tried to restore anything yet. Was that from an old backup or one created in 2.7.0? I'll look into it and if I come across any issues I will revert back to 2.6.1.0. Thanks.

Edit: Just created a backup. Rebooted. Performed a full wipe. Restored the backup with no issues. This was to and from my sdcard.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] anomalya:
Mount USB Storage in TWRP v2.70

While on topic, are you guys able to mount USB storage in recovery? It's broken in v2.7.0 for me it seems.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
After I installed this and grabbed a file explorer it kept saying that my SD card wasn't mounted. I rewiped and reflashed with the same outcome
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Ok, results of my testing. Out of the box, extremely quick and snappy, extremely responsive, extremely stable (couldn't really break it or get it to crash). While CM10.2 and Carbon have handled my apps and games pretty well, this rom has that missing "umph" that makes them shine and enjoyable again (had kernel set to ondemand/row). Battery usage was slightly better than what I was expecting for the test period when compared to other roms that I have ran on a trial run (about 6% usage for the 90 minutes I was testing).

That being said, I ran into one issue that I could not resolve no matter what I tried to do to remedy the problem. The internal storage would not mount/could not be found (does show up in TWRP 2.6.1 and 2.7.0, just not in this rom). This unfortunately is a deal breaker atm for me because some of my apps that I use heavily require the internal storage.

Other than that, I dare say this may be the fastest of the feature loaded roms I've ever touched without running a custom kernel. I'd love to test this again with a fix when I have "play" time again and even make it my DD, because I honestly must say that I'm in LOVE with this rom. :good::good: :victory:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
You are both correct. I cannot see my sdcard either. Thanks for the feedback and will look into a fix.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Could the internal storage issue be tied to the problems with CM10.2 post 9/4? Just a thought...

:f5: :coffee:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jobankler:
Actually guys the problem is created by HALO notifications. Read more here http://xdaforums.com/showpost.php?p=44774253&postcount=635
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Mervingio:
Damn Halo
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] baddgoat:
For me, I had made a backup with 2.6.1.0 and when I tried to restore using 2.7 it failed. I'm gonna try re-backing with 2.7 and see if it restores.

On another note, flashed this and all seems to be good. Thanks for another great ROM Toyes :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
We should probably keep the forums on track about this ROM. There is a TWRP thread for that discussion
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Mervingio:
Did you see your SD card without issues
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] yogi-4:
I just have to say WOW!! Holy Crap fast!! Unfortunately I need to see my sd card which is a deal breaker. But as soon as a fix is available I'll be back for sure. Awesome job Toyes!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Mervingio:
Great i will wait too for the fix
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] soccerfan6789:
Hey man. I built a vanir ROM for hercules and had the same SD card issue. I took a break because I wasn't able to figure out what was wrong...if you ever do figure it out, tell me please.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jobankler:
Have you tried removing halo from the rom?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Can you explain how halo could cause storage detection issues?? I don't think that is what is causing the issues. I have a build on the go with a possible fix that has nothing to do with halo. I'll let you know what I did if works.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Kiltnar:
Mount issues usually have to do with the vold.fstab file.

EDIT: The file should be in /system/etc .... ONLY MESS WITH THIS IF YOU KNOW WHAT YOU'RE DOING... basically, if you don't know what the fstab is .. just don't even look...

I'm not sure if it's included in 4.2.2 anymore. Just throwing this out there. Standard disclaimer applies....

As always... defer to OP on this.. [MENTION=4779173]toyes[/MENTION]
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
When I tested this ROM, I actually looked for that file to see if I could edit it to get the sdcard to mount, but I was unable to locate it. I have some time after work tonight, I may take a crack at it again and see if I can do anything, but I'm sure I will be waiting for an update from Toyes (the awesome) as he has more knowledge on the matter.

Sent from my SAMSUNG-SGH-I727 running CM10.2

Smart Phone History: HTC Star Trek > LG Incite CT810 > Samsung Galaxy S I Captivate > Samsung Galaxy S II Skyrocket
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Did some poking around the forum and the lack of the vold.fstab file is correct as of Android 4.3.

I personally have not messed with the boot.img files yet and until I learn a bit more to understand them, I won't be playing with them so freely and advising on any changes. That's why we have the pros. :highfive:

If someone wants to take a look at this, go for it, but the best bet at the moment is to sit back and wait to smell what Toyes is cooking up. :cool:

Smart Phone History: HTC Star Trek > LG Incite CT810 > Samsung Galaxy S I Captivate > Samsung Galaxy S II Skyrocket
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Two things while I have a moment to report on some stuff I've been up to recently.

1. I'm working on trying to compile this ROM myself to see if I can get it running and troubleshoot the sdcard issue. I've been learning really quickly over the past week and a half and have been successfully building my own CM ROMs, so with a little more study and effort, I believe I will get this one going as well. : fingerscrossed:

2. (Use this info at your own risk! I do not advise this to be attempted unless you know what you are doing. You have been warned!)

I did a little experiment and extracted a copy of the Moretz kernel from the latest witmo beanstalk zip and merged it into the Vanir zip (and updated the installer script to handle removing the mpmdescision file as per instructions with that kernel) to see if the sdcard issue would still be present. The result of the experiment was that the sdcard did mount while the ROM booted (as the folder opened on my desktop since I had the cable plugged in) and the storage did show up in the storage screen in settings for about 2 seconds and then it reverted back to being undetectable. I thought it was an interesting find and may help with a solution. I only wish I captured a logcat. I will try to replicate things again this weekend and capture one to see if it can shed any light on a fix.

Sent from my SAMSUNG-SGH-I727 running CM10.2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] drago10029:
Can you post some screen shots? also a feature list? thanks.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
Send me your phone and I'll flash it for you too. Flash it and play with it for a minute! It's broken but still good looking
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
@toyes has posted the features and rom links in post #1, please look there first. :good:

With the sdcard bug, I doubt capturing screen shots will work presently as they save to the internal sdcard. This rom at the moment is functional and play-worthy, but not DD worthy, so it is a flash and explore rom. I can't think of anything a screen-shot is going to show you that you haven't seen already in a 4.3 based rom. IMHO, most of the time anymore screen-shots are only good for verification of the "About Phone" page and for cosmetic display of anything special that is base to the rom such as bootscreens. This rom isn't about what it looks like cosmetically, it is about what was done "under the hood" that makes it an unique gem. I haven't spoken to Toyes personally at this point, but seeing how much he does in our forums, I'm sure he has something cooking to fix the bug and get this ball rolling, and I personally am working at my own angle on this rom, so that if I do find anything I can report back what I did to help speed up the process. Toyes is a major rom maintainer, so I'm sure he appreciates any assist he can get from the community. ;):cool:

UPDATE #1: I have an experimental test build frying in the pan now. Will report back if it is nice and crispy or if I will be cutting a fresh slab off of the pig. :fingers-crossed:

UPDATE #2: Ok. Now for the fun to begin... I have a working JLS36C test build running, but with the same issue with the sdcard not working. :crying: I'll continue to research and work with the build I have to see if I can figure it out. :fingers-crossed::fingers-crossed::fingers-crossed:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] drago10029:
good ole' xda humor huh? lol and I can't do beta's too much. my phone ever goes bye bye im stuck

---------- Post added at 03:04 AM ---------- Previous post was at 03:03 AM ----------

and thanks, I guess i had something else in mind and thanks.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Droid>iOS:
I'm been reading this thread and people are experiencing issues with the external SD card not being recognized on Skyrocket devices.

I'm getting similar error. My phones says the external SD card does not have enough storage space when I try to transfer apps to my external SD card. I can't even mount it. Has anybody been able to find a solution?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
Dude you missed something in your "reading." Known issue with everyone that downloaded and ran this ROM three months ago!

Sent from my skyrocket running something better than yours! BOOM!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Droid>iOS:
You are right I failed to see this thread is a bit dated and people have been having issues with this rom. Still is there a fix?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
[MENTION=4779173]toyes[/MENTION] was close to having one, but with the Kitkat running wild it may not get updated until the build is updated to 4.4. This ROM will still have it's day on the SR. ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
You're right. I did have a fix but I deleted the zip before I uploaded it.. doh. I lost it as I updated my local source to 4.4. Next update will most likely be 4.4 but I am not sure when I will get to completing that build.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
This might be a reaching question, but is there still a copy of the zip on your SD card? Figured it couldn't hurt to ask. :cool: lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
It has a broken version of vanir on it...

[MENTION=4979831]gr8tech[/MENTION] Vanir 4.4 build on the go.... don't expect it to go without errors though. See if I can get something working today.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
That would be awesome dude, but no need to rush for me, lol. I'm perfectly happy waiting until 4.4 is running in DD mode first and it is also giving me time to learn more about the driver sources for ROM development and how it all works as I have been working on building and testing my own patches for CM (with some minor success and much fail, lol) in conjunction with the ones TeamChopsticks has been posting. I am curious though as to the vold fix you used for this rom. I still have the source for the 4.3.1 version of Vanir, but haven't been able to figure out the vold problem yet, so if I could apply your fix to have a working build, that would be a great deal of help for me alone. :cool:
[Verizon HTC One (M7)] m4rk0358:
Shows Android 4.1.2
[Verizon HTC One (M7)] Murrda:
It's generic I believe, because all the other HTC One devices launched with Android 4.1.2 and Sense 5, we were the only device that launched with Android 4.2.2 with Sense 5.

So they most likely were lazy and decided not to update the spec banner for us lol....

Make sense? I could be wrong but it makes sense to me!
[Samsung Galaxy S Relay 4G] esilence:
[SOLVED]

I can not get into the phone call (green phone button) to the dialer, this is the main problem; when I open it, it hangs for a few seconds then I get a message box centered in the middle of the screen: Contacts has stopped. - only OK button to press; and pressing returns to homescreen.

Everytime after sending an SMS I get: "messaging has stopped", although still I can send.

I can access the contacts normally and also everything else is fine. when I start calling someone from there, it works also fine, with the resemling dialer(?) look while talking. But then right after finishing call, again a message pops up: com.android.phone has stopped

- resulting that the calls are not being logged.

the app "GO Contacts Ex" would be ok as an alternative, but here again, after the call ends, the message comes up: com.android.phone has stopped. also other apps like contact+/dialer+ and exDialer&contacts seem like that all using somehow com.android.phone in the end and causing that error message box coming up.

if no fix, is there an alternative app totally replacing the usage of com.android.phone? so that I could use another app?

I have found and tried some suggestions from google to this problem, but none of them helped..

deleting cache in: apps -> all -> contacts memory and contacts and phone, & reboot; - several tries, also SIM card out, and reloads, re-sync;

uninstalled recent updated apps; reboots, sim out, re sync etc.

It seems like there is one small thing interrupting but I can be wrong.

I dont wish to do a factory reset first, and lose all my apps and settings. Before doing that desperately, I would like know if someone could help me out in here? It could be one small setting or stuff to do

I am using JB 4.1.2 rooted

it is possible that I disabled some important processes earlier which caused that, but I enabled them all again and restarted, still nothing changed. otherwise this problem started surely after recent app updates, which i also tried undone and checked

any help is appreciated!

SOLUTION

1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.

2. Reboot. Activate these apps. Reboot again.

Another reason for "com.android.phone has stopped" coming up is when you previously deactivated com.movial.ipprovider, or if it is damaged, which is needed to connect to the internet. The error starts coming permanently as soon the phone trys to connect to the internet.

Solution: just stop com.movial.ipprovider, delete its cache and reboot! (or reinstall it)
[Samsung Galaxy S Relay 4G] esilence:
I can avoid the first two problems (contacts and messaging has stopped) by simply using a different app which I at least like better (Dialer+ / Contacts+ including sms), and have deactivated the stock versions now (contact and messaging). - and I am happy with that!

the problem with com.android.phone still remains after each call, for both incoming and outgoing. the bothering thing is that error message box, and that the calls are not being logged at all, but sms messages are logged fine.

(I could not find any app that could be an alternative to this com.android.phone, similar to the contacts and messages app. all the 3rd party caller and dialer apps uses com.android.phone in the end when dialing. if i uninstall com.android.phone, there is only skype as an alternative to call. and uninstalling skype gives then no possible ways to call a number. so I need to fix this somehow.)

problems:

1. message "the process com.android.phone has stopped" after every calls.

2. no calls are logged

please find attached a logcat logs when that happens, maybe someone can understand what is causing this (look for com.android.phone).

what is for example E ActivityThread: Failed to find provider info for logs ?

and what can you suggest me?
[Samsung Galaxy S Relay 4G] esilence:
I got it !!!

I searched and located the file on where the calls logs are being saved: data/data/com.sec.android.provider.logsprovider/databases/logs.db

As I thought it could be damaged. I cleared the cache from LogsProvider and restarted it, and the error is now gone since then!

But clearing also deleted all the files in its folder including the logs.db. Unfortunately it doesnt recreate this files, even after a reboot. How can I get these structure and basic files again?

Can someone copy this for me? or can I use any logprovider files from internet?...

will check ...
[Samsung Galaxy S Relay 4G] esilence:
SOLVED !!!!

after reactivating Contacts & Phone, also a brand new folder structure with logs.db was recreated automatically !!!!!

Everything is running smoothly now!!! yay!!!
[Samsung Galaxy S Relay 4G] esilence:
Just FYI and to summarize, in case it happens to you. it was either logs.db file or something in logsprovider folder damaged.

SOLUTION: just stopped com.android.phone and logsprovider service, and deleted the cache from both. then reactivating them should be ok! then just reboot!

cheers
[Samsung Galaxy S Relay 4G] kenkamm:
You mention this "reactivating" step. Can you explain more about how to do this part?
[Samsung Galaxy S Relay 4G] esilence:
Hello Kenkamm,

1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.

2. Reboot. And activate these apps. Edit: reboot again.
[Samsung Galaxy S Relay 4G] kenkamm:
Thanks! Next time I feel brave and re install xposed I will give this try.
[Samsung Galaxy S Relay 4G] esilence:
I forgot to mention, also after the 2nd step you need to reboot.
[Samsung Galaxy S Relay 4G] aztrack:
THANK YOU!!!!

OMG, I've been dealing with that darn com.android.phone error for nearly a year now ==== and you solved it for me!!! I can't tell you how happy and thankful I am. After every call in/outbound I would get that pesky error! NOW I'M FREE AGAIN!!!!! WOOO HOOOO!!!
[Samsung Galaxy S Relay 4G] esilence:
I am glad that I could help! you obviously just joined and posted because of me to tell about this.. thank you :)
[Samsung Galaxy S Relay 4G] furboom1240:
Namecards cannot be shared

I was looking at this and hoping these drastic moves could fix the reason I cannot share my contacts using the share command. It force closes afterwards.

Sadly, I've tried all of this and my contacts still cannot share. So you have any idea what could be wrong with my Galaxy S Relay? I am rooted (but using stock 4.1.2) at this time, and have only removed bloatware such as Evernote, Slacker, etc.
[Samsung Galaxy S Relay 4G] DeViBos:
Thank you !!

Worked like a charm on Samsung S5 Mini. :) :)
[Samsung Galaxy S Relay 4G] esilence:
sorry [MENTION=5616810]furboom1240[/MENTION] i missed that topic here and didnt see your message earlier. but i have no idea what could have solved your issue either. it relates to something else i guess, hope u had luck in the meantime and solved

[MENTION=6029389]DeViBos[/MENTION] thanks :) another new user and first post, i appreciate! welcome to xda and have fun :)
[Samsung Galaxy S Relay 4G] prazetyo:
Is it possible to try this method to other brand like HTC example? Because Phone can't force stop and there's no logsprovider. Where it can be found?
[Samsung Galaxy S Relay 4G] barr1332:
Just as I will do now. Thank you sooooo much I thot my phone was a hacked mess. The world just became a better place!
[Samsung Galaxy S Relay 4G] ManSamVampire:
Same problem on my Redmi 1S

Sorry for waking an old thread. I am facing a similar problem.

My Device is -

Xiaomi Redmi 1SW (Rooted)

Android 4.4.4

MIUI 7.2.3.0 KHCMIDA

I have removed all bloatware as mentioned in this post (http://xdaforums.com/xiaomi-mi-3/general/tip-safe-to-remove-bloatware-list-miui-t2999283/page2) and also another app called 'Xiaomi Service Framework' if these are causing the problem.

I was earlier facing this problem when I was using MIUI 7.1.1.0 KHCMICH (Rooted and Xposed installed). It suddenly started occurring as soon as I connected my phone to the PC before even doing anything. The pop-ups (Unfortunately Phone has stopped) became irritating. Luckily, I had USB debugging enabled. I connected the phone to the computer and put the following in the CMD -

adb devices

adb shell

su

pm disable com.android.phone

exit

exit

exit

Then the window stopped appearing. So I (mark this) turned off Wi-Fi and disconnected phone from PC. I was using the phone normally for few hours. But I realized that outgoing calls on my phone were not possible (the system dialer (com.android.contacts) closed after pressing the call button) and no incoming calls were being recorded (I use the in-built call record feature in the system dialer app). So I connected my phone back to the computer and wrote

pm enable com.android.phone

in place of pm disable com.android.phone keeping all above mentioned commands same.

This time the window did not appear. I was able to make and record calls perfectly. But on the same day, when I again switched on Wi-Fi, the window started reappearing. So I used my device by keeping the com.android.phone disabled for few days.

After few days, I got an OTA update to MIUI 7.2.3.0 KHCMIDA. I thought it would solve the problem.

I also wanted to reset my device because it had lot of junk. So, I flashed the update, rooted the device, removed all bloatware apps again (which came after the update) and shut down my phone. The error window hadn't appeared yet though com.android.phone was enabled and Wi-Fi was connected.

Then I booted into recovery and erased the cache and data partitions (NOT the internal storage). Then after phone was booted and as soon as all setup was done, the error window started coming up again.

So, I don't think that data/data/com.sec.android.provider.logsprovider/databases/logs.db has any problem because it was erased completely after I wiped data.

I need HELP !!!