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.
Hello,
I own a 64GB P7510. It is rooted and currently it has a version of CM9 ICS installed. I have tried several versions of ICS and Stock Honeycomb as well as Tasks GalaxyTask 14.
I use Splashtop HD mostly on the tab and have noticed that it randomly freezes the tablet and crashes the device. The only way to recover it to hold the power button down and wait for the device to restart.
In Stock ROM and GalaxyTask 14 it seems to work fine. In ICS or when installing Pershoots kernel the crashes occur. The crashes are totally random and can happen when splashtop has been left along for a minute, ten minutes or not at all.
I assume this has something to do with the kernel as I experience the same problem with GalaxyTask 14 but only when I install the pershoots kernel. It also happens in all ICS versions I have tried.
Current config: Android 4.0.4, Kernel [email protected] #1 SMP PREEMPT Sat June 23 22:18:30 EDT 2012, Cyanogenmod version: 9-20120703-NIGHTLY-p4wifi, Build date: Mon Jul 2 22:00:33 PDT 2012, Build number: cm_p4wifi-userdebug 4.0.4 IMM76L eng.jenkins.20120702.220017 test-keys
Splashtop version: (Streamer) 2.0.0.4 (also tested in older streamer but same results), (Client) Splashtop 1.9.9.5 SW r21787
This make using Splashtop unusable as it randomly crashes. When I spoke to Splashtop support they said they had never heard of a problem like it.
I have looked all over the web and done extensive searches of XDA to try to find out what the problem could be, but to no avail. I also hope I have put this question in the correct forum.
The problem takes place in (and I have tested):
GalaxyTask 14 (only with pershoots kernel)
AOKP ICS
CM9 ICS
It works fine in:
GalaxyTask 14 without pershoots kernel
Stock HC ROM
Even if there is no solution, is there a way I could troubleshoot the problem.
Any help would be appreciated.
Many thanks,
Graham.
Just bumping. Has no one at all experienced this problem at all?
I reloaded Honeycomb this week and there were no problems at all, then reloaded ICS and it still crashes. I can't be on my own surely?
Graham.
on ICS (you can use 0710 experimental i posted this morning on droidbasement),
as soon as it crashes, head straight to recovery and pull /proc/last_kmsg and send it to me.
i'll see what i can do.
I will flash this now and let you know. My tab crashes quite a bit on the 07.04 CM9 nightly, and am thinking about going back to HC
Sent from my GT-P7510 using xda premium
it should not be crashing. you may have a bad app or an unstable OC doing harm. at any rate, load up 7/10 experimental, do not OC or install any other app but splashtop. if it crashes, pull the log.
pershoot said:
it should not be crashing. you may have a bad app or an unstable OC doing harm. at any rate, load up 7/10 experimental, do not OC or install any other app but splashtop. if it crashes, pull the log.
Click to expand...
Click to collapse
in fact, this is what you should do:
pull your data off /data/media, odin back to 3.2 (the whole tab will be wiped), odin CWM (found in the 7/10 experimental folder), boot CWM, wipe, flash 7/10 experimental, latest gapps, and boot in. dont restore any apps and dont OC. install only the splashtop app. observe and pull log if it crashes as i outlined above.
the added bonus from the above will ensure you don't have any more crashes from extraneous unknown factors.
When I said my Tab was crashing, I meant in general and not due to splashtop. I don't even use splashtop. I thought maybe your experimental build and giving you that one file could help troubleshoot crashing in general. Sorry about that.
Sent from my GT-P7510 using xda premium
Thanks Pershoots. I am not sure what is going on. I will have a look and send it to you. It may be next week before I get a chance.
Many thanks,
Graham.
pershoot said:
on ICS (you can use 0710 experimental i posted this morning on droidbasement),
as soon as it crashes, head straight to recovery and pull /proc/last_kmsg and send it to me.
i'll see what i can do.
Click to expand...
Click to collapse
hi pershots.
i rebooted into recovery after the last crash but i dont see where to pull that from. i am using cwm recovery. also when you talk of your 0710 experimental do you mean a newer version of the kernel?
many thanks,
graham.
medialinx said:
hi pershots.
i rebooted into recovery after the last crash but i dont see where to pull that from. i am using cwm recovery. also when you talk of your 0710 experimental do you mean a newer version of the kernel?
many thanks,
graham.
Click to expand...
Click to collapse
you need to be on 07/11 experimental rom (from droidbasement) or 07/12 nightly from get.cm.
please odin back to 3.2 (the whole tab will be wiped; make sure you back up any data you may have in /data/media), odin CWM (you can find this at droidbasement), boot it, wipe, flash either of those roms and flash latest gapps. enter in, do not restore any apps. install only splashtop and run it.
now observe.
if you get a crash, head straight to recovery and do this:
adb pull /proc/last_kmsg .
then send that to me.
I am experiencing the same problem. On stock HC 3.2 splashtop worked fine but my HDMI cable out didn't work so I flashed RS_Supremacy_AOKP v0.2 pershoots kernel 2.6.36.4-cynogenmod+, my HDMI cable worked great after that the rom is awesome I love it but only just recently noticed that splashtop now is almost useless it always freezes within 5-10mins of use and I then need to hold power button down to restart tablet. I'll be watching this thread with great interest as I don't really want to change my rom I really like this one.
Sent from my GT-P7100 using XDA Premium HD app
Ichigo66 said:
I am experiencing the same problem. On stock HC 3.2 splashtop worked fine but my HDMI cable out didn't work so I flashed RS_Supremacy_AOKP v0.2 pershoots kernel 2.6.36.4-cynogenmod+, my HDMI cable worked great after that the rom is awesome I love it but only just recently noticed that splashtop now is almost useless it always freezes within 5-10mins of use and I then need to hold power button down to restart tablet. I'll be watching this thread with great interest as I don't really want to change my rom I really like this one.
Sent from my GT-P7100 using XDA Premium HD app
Click to expand...
Click to collapse
it will not get fixed until i see logs.
Ok I'm still a bit of a noob when it comes to these things but i'll give it a try and see if I can get a log for u fingers crossed X
Sent from my GT-I9300T using xda app-developers app
pershoot said:
you need to be on 07/11 experimental rom (from droidbasement) or 07/12 nightly from get.cm.
please odin back to 3.2 (the whole tab will be wiped; make sure you back up any data you may have in /data/media), odin CWM (you can find this at droidbasement), boot it, wipe, flash either of those roms and flash latest gapps. enter in, do not restore any apps. install only splashtop and run it.
now observe.
if you get a crash, head straight to recovery and do this:
adb pull /proc/last_kmsg .
then send that to me.
Click to expand...
Click to collapse
Here you go Pershoots. I hope this is what you are looking for. I am not really up on using ADB. I could not get it to do a pull from CWM recovery or Odin recovery so I rebooted and ran USB Debug then finally got the computer to see the device. Anyhow, here is what I pulled. If I did this wrong if you could please explain or point me to somewhere to see the steps needed to ADB from recovery as I could not find anything on Google about ADB recovery galaxy tab 10.1.
Thank you for looking at this for me.
Here you go...
[ 12.526464] [DBG] upload cause : UPLOAD_CAUSE_INIT
[ 12.526479] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 12.526464] [DBG] upload cause : UPLOAD_CAUSE_INIT
[ 12.526479] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 13.162166] i2c i2c-11: sendbytes: NAK bailout.
[ 13.276914] mxt_config_settings
[ 13.852817] Failed to add route HPOUTL->Headset Jack
[ 13.886165] Tegra protected aperture disabled because nvmap is using system memory
[ 14.706771] init: cannot open '/initlogo.rle'
[ 14.712062] init: Unable to open persistent property directory /data/property errno: 2
[ 14.721883] android_usb: already disabled
[ 84.203676] SysRq : Emergency Remount R/O
[ 84.208259] Restarting Linux version 2.6.36.4-cyanogenmod+ ([email protected]) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-51) ) #1 SMP PREEMPT Sat Mar 17 18:04:36 EDT 2012
[ 84.208268]
[ 84.266040] VFS: Close: file count is 0
[ 84.884148] Restarting system.
No errors detected
You're running a really old kernel/build.
I'll be posting new test builds soon. U can retest against them.
pershoot said:
You're running a really old kernel/build.
I'll be posting new test builds soon. U can retest against them.
Click to expand...
Click to collapse
Thanks pershoots.
From looking at that output would you have any idea what is going wrong?
Graham.
medialinx said:
Thanks pershoots.
From looking at that output would you have any idea what is going wrong?
Graham.
Click to expand...
Click to collapse
not really. altho, there was a blurb about protected memory which ive since enabled in the video driver (been enabled for a while).
crash
The crash is happening in aDownloader and Splashtop... now in JB. It happens very randomly...
I have re-flashed it, re-odined it, re-stocked it many times(tried all sorts of different roms), but I get this issue always when I have pershoot kernel, and unfortunately there isn't much alternative choice on ICS / JB. It looks like this kernel issue is here since the beginning and basically I am unable to download torrents (or stream HD via splashtop) without restarting it a couple of times.
It's really strange that more people are not experiencing this issue...
Try the experimental I posted for cm9 or 10 (07/28).
Post logs if it crashes.
Hi pershoots.
I have been running jellybean with your kernel 26/7 for the last week and had only a couple of crashes. Maybe it is an ics issue as i have reflashed ics this week too and it crashed under it.
Graham.
Samsung Galaxy SIII GT-I9300
Hi, I just recently installed ARHD 11.2 with the Perseus Kernel onto my S3, and it generally runs very smoothly and the battery life is greatly improved.
However, after a while, the phone starts getting very laggy and unresponsive (it will take more than 5 seconds to recognize any input) and I have to restart the phone. It'll work fine again for a while before it starts getting laggy again. Because of this, I just had to go back to the stock ROM.
Anyone have a similar problem? Note that I haven't used any other performance tweaks, only just the Perseus Kernel.
rustingee said:
Samsung Galaxy SIII GT-I9300
Hi, I just recently installed ARHD 13.0 with the Perseus Kernel onto my S3, and it generally runs very smoothly and the battery life is greatly improved.
However, after a while, the phone starts getting very laggy and unresponsive (it will take more than 5 seconds to recognize any input) and I have to restart the phone. It'll work fine again for a while before it starts getting laggy again. Because of this, I just had to go back to the stock ROM.
Anyone have a similar problem? Note that I haven't used any other performance tweaks, only just the Perseus Kernel.
Click to expand...
Click to collapse
which version of Perseus are you running? because i have heard that the latest perseus kernel has a bug or something, hence, using the v24.x is recommended at the moment..
try this
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
Ok, I will try flashing ARHD again with an older version of Perseus. I'm not sure what version it is, but I downloaded the latest version of ARHD very recently, so I'm guessing it comes with the latest version of Perseus.
PS. Noob question, but where can I find older version of Perseus? I can only find 25.3 from the thread in the developers forums.
Oh v25.3 is out maybe he made some bug fixes already.. and it will work great with ARHD v13
Perseus kernel v24.x is already implented in ARHD's Aroma installation
Sent from my GT-I9300 using xda premium
So I'm getting right to the point. Upon every try of kernel installation I eather get kernel panic on boot, or it pops up at the finish of "optimazing android" screen. Tried every wipe, every installation sequence - nothing. I'm currently on Paranoid Android RC2 by adamz667, still no success installing kernel (but the rom works perfectly by itself). I've searched every message on that thread, but no one is having a problem like mine. So.. I ask your help
Model Number - P760
Android Version - 4.3.1
Baseband version - LGP760AT-00-V20h-EUR-XXX-JUL-12-2013
Kernel Version - 3.0.31-ASAP+
[email protected] #2
ParanoidAndroid version - 3.99-RC2
Without any logs we can't tell you what's wrong.
Here is the screen:
You have similar problem as some users of my experiencedkernel. I'm trying to fix it.
I pressume this is some hardware problem? Why is it that just some of us have this problem?
And yeah, I had the same window when I had MIUI installed and tried to install your experiencedkernel.
evalduuk said:
I pressume this is some hardware problem? Why is it that just some of us have this problem?
And yeah, I had the same window when I had MIUI installed and tried to install your experiencedkernel.
Click to expand...
Click to collapse
I've this problem with some kernel, I think should be a low or high voltage of some frequencies at boot.
Have S3 i9300 with cm11, latest nightly. Due to recommendations from this Website, I installed arter97 kernel a few days ago.
I'm not happy with that. The phone has extreme lags after wake up, sometimes it takes 20 seconds until something happen after tapping on an icon. And Google maps takes too long to load so that Andoid presents the "application not responding" dialog.
I like to revert to the default (previosly) installed kernel, but havn't found any information how to do that. Thank you in advance for any help.
Franz
franzschenk said:
Have S3 i9300 with cm11, latest nightly. Due to recommendations from this Website, I installed arter97 kernel a few days ago.
I'm not happy with that. The phone has extreme lags after wake up, sometimes it takes 20 seconds until something happen after tapping on an icon. And Google maps takes too long to load so that Andoid presents the "application not responding" dialog.
I like to revert to the default (previosly) installed kernel, but havn't found any information how to do that. Thank you in advance for any help.
Franz
Click to expand...
Click to collapse
in recovery format system. alternativeley you can also delete the kernel.sh (not sure about the exact name) in /system/addon.d
after that reflash your ROM. your data will not be lost.
check Boeflla kernel for CM 11 is best than arter kernel
Thank you for your feedback!
Because I'm not a developper, I'm too afraid to edit manually files in the Android system.
I decided to give Greenify a try. After the installation, I discovered that SU from Chainfire didn't work anymore (probably since the flash of arter97 kernel). I was unable to give root access to Greenify. I then reflashed SU from Chainfire. SU works again and I was able to configure Greenify in root mode.
Since that, my phone runs incredibely smooth (like never before), and also battery life has greately improved.