I wanted to report some feedback on installing RevolutionRom JVQ. I have been most lurking so didn't have posting privileges to post in the development forum under the release.
I have been experimenting with various ROMS since I acquired my Vibrant last July. I installed Revolution ROM Beta 2 and was blown away by both the speed of the system but by the great battery life, the best I have tested to date on any ROM.
I was very excited to install the final version released yesterday.
From RevolutionROM JVQ beta 2 I updated with CWM with the both wipe and non wipe versions. The end result was boot looping.
I returned to stock using ODIN and tried again with the same result (From stock -> rooted, installed ROM manager and flashed CWM to ROM, installed wipe ROM version).
I returned to stock and used ODIN to flash the Final version with GB bootloader. This booted properly but I received mail forced closed message.
From this I finally installed with CWM the final version without Wi-Fi calling. This seems to be working properly without any noted difficulties. I'm still restoring apps with titanium backup but so far everything is working without a hitch.
I noticed that other users have posted similar results. http://forum.xda-developers.com/showpost.php?p=16147594&postcount=92
ali1276, I wanted to thank you for this awesome release. You may however want to reevaluate the wi-fi calling versions of your ROM. I think there's something wrong that's causing the phone to boot loop.
So you flashed the wi-fi calling one. Ok, I will probably fix and repost it today.
Sent from my GT-I9000 using XDA Premium App
Problem with system rebooting
In comparison with the JVQ Beta 2 the final Revolutionrom update 2 is constantly crashing and rebooting. Happens either while phone is on standby, playing music but has also happened in the middle of a call. I don't think the BT issue has been completely resolved with update 2. Sometimes it requires a reboot to get it to work, sometimes event that doesn't work.
I flashed back to beta 2 which in my opinion seems to be working a bit better. BT works from initial bootup and I'm not experiencing any system crashes.
I think I have identified a bug on the dialer (in the JVQ beta 2).
when you use the dialer to call a number you have stored on speed dial, lets' say you press 3 and dial instead of dialing that number a window opens that says:
"USSD code running....."
then an error window appears:
"Connection problem or invalid MMI code. "
If you dial the same number using the contact or just dialing the numbers the call goes through normally.
Despite these glitches, I love this ROM. It's fast, great on battery life. Over 50% at the end of a busy day. Not sure I have seen that even on stock firmware. Hope these glitches get ironed out.
Related
I was running a stock ROM, rooted, with the original radios. All was operating properly.
Flashed the leaked radio update. Everything still okay.
Flashed Das BAMF 1.6. It boots up fine (and looks gorgeous, btw), but my SIM card is not recognized at all. Symptoms:
When making a call, I see text in the upper-right corner saying: "SIM Card not found. Please \n the phone."
Settings > Call > Voicemail Service... tapping on this dropdown results in "Voicemail number change unsuccessful. Please contact your carrier if this..."
I tried turning the phone off, booting it once without the SIM card, then rebooting with it back in place. That didn't help.
Out of frustration, I restored my tbolt to the backup I made before attempting das BAMF. Magically, my SIM card is recognized and everything back to normal. ...I tried das bamf one more time, only to have the same crappy results... FYI, I was sure to wipe data/cache/dalvik before flashing the rom in recovery.
HELP!
EDIT: I've also just noticed that despite this being das bamf 1.6 remix, I don't see the 4-in-1 restart menu, nor a 6-bar signal indicator. I'm absolutely positive that I downloaded 1.6 remix... Am I in the twilight zone?
did you wipe data before installing the ROM?
nevermind i missed it. i dont know then sorry.
try redownloading and check md5
I verified the md5 before flashing.
i actually received the same errors but it did not impede functions of the phone. My data has been dropping, but that is not because of the ROM, it has been doing it since the 4G outage.
EDIT: Actuallly my voicemail says:
"We have a problem
Your voicemail settings could not be loaded. Please try again."
Never seen that before.
The more I look into it, I'm missing things that are pictured in the 1.6 Remix screenshots... all of this has me very confused. I'm going back to the stock ROM until someone else finds and resolves the SIM card issue.
I am experiencing the same issues here. I see 'no Sim Card Detected' at the top, I have none of the Reboot Options, no 6 bar signal, etc.
Seems to be kind of a big issue and yet noone has really offered solutions. I have done the full wipe aswell.
Thank you for everyone's time involved with making such a Great ROM....Plus this Community of Users is awesome...Take that IPhone!
Did you happen to download 1.6.1 or 1.6.2 and install just those first? Those two are just patches that required 1.6 as a base.
So, you would have to flash 1.6, then 1.6.1 or 1.6.2 over it as a patch - you can't just flash 1.6.1 or 1.6.2 by themselves. With 1.6.3, I think they went back to a full rom release.
Install via cwr, not Rom manager.
Sent from my ADR6400L using XDA App
I had the same problem with the SD card running Bamf Remix. What solved it for me was formatting the SD card. Obviously backup the SD card on your computer first.
Download 1.6.3 and do a flash. It's a complete download too, id give that a go. I didn't run into any of those problems. Are you flashing through rom manager or cwm?
Sent from my ADR6400L using XDA App
Dont manually mount data. For some reason when i did that the same exact this happened to me. No 6 bar signal and no 4 in 1 reboot menu.
Sent from my ADR6400L using XDA App
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
I ended up wiping everything and installing 1.6.3 and that fixed everything. Thank You all Gentlemen for helping!
You guys are genius!
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Kodiax said:
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Click to expand...
Click to collapse
For the Call Recorder, it sounds like you're running a custom kernel. Most kernels don't support the things that Call Recorder needs. For the reboots, well, can't help you there.
mcore09 said:
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
Click to expand...
Click to collapse
Other than wiping twice (???), what you said you did should be standard procedure. Flashing via ROM Manager and Kernel Manager are no-no's unless you get lucky. In an ideal world, they work. And in many cases, they do work. However, in many cases, they cause nasty issues. For example, if you flash some kernels via Kernel Manager, the device drivers don't get flashed properly and you have some pretty nasty problems. And when you flash via ROM Manager, well, you learned what happens. From now on, only flash via CWM and CWM only.
Thank you for your responses. I am only using the 4.4.7 kernel. Which come s with dad band 1.6.3. I think that it is this new kernel (4.4.7). I never had these issues with 1.6.2.
Sent from my ADR6400L using XDA Premium App
Try down grading your kernel to a slightly older version.
Sent from my ADR6400L using XDA App
I reflashed my kernel to the same 4.4.7 but downloaded the kernel from his standalone post regarding kernels. My call rcorder is working now. Hasn't restarted since then either. Crossing my fingers ...
Sent from my ADR6400L using XDA Premium App
Well it restarted randomly while I had it connected to my Laptop and set to charge. I was in the middle of a Call with someone.
Very interesting why its Randomly rebooting. Could be the new radio. May be that why verizon held out on releasing it yet.
I found the solution to the problem described below. It was ROM Manager that was sabotaging me, for whatever reason. I went into CWM manually, wiped everything obsessively 3 times like I've seen other people describe, installed 1.6, and it worked perfectly. Too early to say how it actually runs for me but I least I've got it fully installed!
PROBLEM:
I started from stock rooted S-off ROM and installed Das BAMF 1.5, wiping everything as recommended. Under Settings/About Phone/Software information, the baseband, kernel, build number etc were all correct. Things ran OK, although battery life was pretty bad. But there were a number of anomalies. The Verizon bloatware still seems to be present. The location reticule is still present in the notification area. Etc.
Today I installed 1.6 over 1.5, again wiping everything even though it is said not to be essential. I did the install through ROM Manager. Everything proceeded as expected, the boot animation screen shows BAMF 1.6, all the About Phone information is correct for 1.6. But again, the location reticule is still present; signal strength indicator is 4 bars instead of 6, Verizon bloatware still present.
I know the real action is in the development thread but I still need a few more posts before reaching that exalted status. Anybody else seen/solved an issue like this? Any help is appreciated and if some kind moderator feels led to move this to the other thread, all the better!
[EDIT] A couple other anomalies are the extended Power Options and Reboot menu options shown in the 3rd and 4th screenshots at the beginning of the Das BAMF 1.6.1 development thread-- I don't have those. On the other hand, I do have BAMF Toolbox, Call Recorder, and other expected apps included with the ROM.
Thanks very much.
I'm having the exact same results. Frustrating!
Are you installing with ROM Manager, or directly from CWM?
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Here's the thing I don't get. What's the fricking point of wiping 3 times?
If wiping == formatting a partition, then what good does it do to do it 3 times? None that I can imagine.
If wiping == deleting everything in a directory tree, then again, what point is it to wipe 3 times? What is accomplished on the second and third time that isn't on the first?
Just my opinion. I've never had a problem with wiping just once.
johnkc1975 said:
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Click to expand...
Click to collapse
I would try hbooting the unsigned stock RUU. Then try flashing the rom of your choice through Cwm not rom manager. This should start you back at scratch with s off along with clearing up any bugs you can't seem to get rid of.
I had the same problem. Don't use Rom Manager for this Rom. Do it manually and everything will be like it should.
Ditto to that. All my unfruitful efforts were due to initiating the process via ROM Manager. Doing it all via CWR did the trick.
So I am thinking about isntalling the gingervitis 1.0 rom, I am currently on 1.12.605.6 radio and stock os w/root, I was wondering what radio i need to be on for this rom( he does have a link for a radio but dont know if it is ok to upgrade from the verison i am on) and after i do flash this radio and rom, and say i dont like the rom, if i restore back to stock os w/root am i able to keep the radio i upgraded to or am i going to have to downgrade to a different one, sorry about posting this in general i tried in the actual thread and got no answers.
You should be fine upgrading as long as you follow his steps.
As far as going back, I don't think that radio works on froyo roms. That's why when you flash the radio first and boot your phone back up, you don't have service. I could be wrong, but that's what I've gathered from everything.
I have GB right now and the only problem I've had so far is my text messages are out of order. Other than that, everything works great. I do know a lot of people are having trouble placing phone calls, and having random reboots though. It seems pretty hit or miss, but the developers are working hard trying to get everything as stable as possible.
Seems like every day since the leak a new version comes out with more bug fixes and different sense 3.0 additions. If you don't like the downfalls you see today, wait until tomorrow and see if they've fixed it yet.
I've been very impressed with the amount of bugs have been fixed so far and how fast they've fixed them.
I was having Force Close issue on beta 6 but beta 5 rocked
k i think i am going to do it, do you know if its easy enough to just flash the old radio back on it or am i going to run into problems if i decide to restore back, also when he comes out with updates i should just be able to flash the newest beta on top the other or should i do a wipe and then install again.
I'm having serious charging problems with this rom and the test 4 kernel. Talking like, 3% charged in 45 minutes off the wall.
I'm using the beta 6 Rom with the kernel that came with it and no problems so far not even reboots, have tried the newest kernel by imoysen?
Sent from my ADR6400L using Tapatalk
I recently unlocked my bootloader, and installed ken's 2.3.4 Beta #4. I love the look and happy that i'm finally on 2.3.4 but my data speeds are horrible. When i try to open the market, it would either take about 2 minutes to load up or i would have to hit retry a few times for it to start loading. Then once it loads, sometimes when i'm downloading multiple apps, it would disconnect then about a minute later reconnect and finish downloading. I'm not running an overclocked kernal(got kinda confused with moto-flashboot and where to put the files), i flashed a new radio(.30). Everything else seems to be fine though as far as text messaging and calls.
flash a different radio and see if that helps. theres is a few floating around in the Dev forum.
some people also reported that the radio works much better after a second flash.
i'ma try it again, i don't have to take out my sim and sdcard right? i flashed it the first time with rsd lite
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
[email protected] said:
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
Click to expand...
Click to collapse
1) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
2) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
3) No
Also I find if switching between 4.3 roms and 4.4 roms (which I do alot) it is good idea to backup internal sd card and to format it (not all the time just if phone becomes really slow or has random reboots)