Related
Ok...I am a 'somewhat' noob. I do have my phone rooted and have watched many videos and read through the forums. I have not yet flashed to a custom rom, but am thinking of making the jump. Just have a few questions....
Firstly...Anyone have any negative experience with PARAGON's rom? Looking though the many different ones, this one seems to keep catching my eye...
Next...I have backed up all my necessary files including using Titanium pro backup. As I said the phone is rooted. I am running stock 2.1. I have also used one click lagfix. Do I need to remove the lagfix? Can I use Odin to just master clear or do I need to flash to odins stock first? I have rom manger dowloaded also!
Thanks for any input and help in advance!
paragon is an awesome rom
You must disable the lag fix prior to flash. You can odin back to stock as long as you have all your backups. You do not need to be rooted to flash a rom. Odin will get rid of lag fix, but app should do so as well. If you use odin there is an update.zip on your sd. Leave it there, when on stock boot recovery, reinstall packages twice, you well have clockwork recovery. Install zip from sd, choose zip, select paragon, confirm
If you do not disable the lag fix you will get stock in a boot loop
gandalf21502 said:
Firstly...Anyone have any negative experience with PARAGON's rom? Looking though the many different ones, this one seems to keep catching my eye...
Click to expand...
Click to collapse
Yeah...I got tired of waiting for at&t to release an update so took my froyo fate into my own hands...so to speak.
I ran Cognition 2.b3 - 3.02 and was pleased with the performance. I started watching this ROM at RC5 and just pulled the trigger today. The process went exactly as described. One thing I noticed is that this modem supports hsdpa, maybe cog3.0x did too...but never noticed. Went outside and turn GPS on and got 12 sat lock in seconds....sweet. locked in within 10'...very nice results.
Anyway, just get your feet wet, try it, don't like flash back to stock, or try another flavor. So far I'm very pleased with this ROM.
Paragon is great ROM. Been running it for about 6 weeks. I'm on RC5 now, waiting for RC6. I've had no issues. I'm running OC/UV (not required) with very conservative settings. Getting great performance, battery life and pretty good GPS.
Enjoy.
Paragon is a great ROM hands down!
Yeah, I'm running Paragon 5.1 and it's been running great. I haven't changed the OC/UV settings, just running default, with good battery and good speed.
Try it, you'll like it.
There's a reason he named it Paragon.
eSPyeL did his homework, paid attention to the details, and doesn't rush things.
If you like the ROM, throw him a bone. He's sticking with the Captivate for a good while and things will only get better.
THANKS for all the input!
I like my captivate! BUT the main reason I am looking to flash a custom rom is even with the lagfix, seems slow compared to my HTC flavors. I MUCH prefer this phone over them just want better responses. Also really want flash. I am an o/c'er by heart...ever since I have owned a PC I have o/c my CPU/GPU. Just like to get the most 'bang for buck' out of my parts...lol.
I think I shall give this a try...hopefully all goes well...
Take a look at Cezars Continuum v 2.1
After trying at least 10 different roms i am sticking with this one.
I am on paragon 5.1 with the 1.4Ghz 500hz kernel. I absolutely love it. Obviously I'm using the OC/UV to tweak it. I'm getting pretty fantastic battery life. Great GPS. I personally love the look and feel to it. I would reccomend this rom over and over again. I haven't found anything that I don't like about it so far. It's a solid working beast of a rom.
I have been running Paragon since RC3 and it has worked great. I have had a couple flashes that seemed to cause some issues with my phone, but when I had more issues than I could handle, I reflashed it and my phone worked great since. My first issues occurred when I flashed RC4 the first time, I was getting a lot if Force Closes of the system. I flashed RC4 again and didn't have any problems. The last time I had an issue was this past weekend with my flash of RC5.1. I was having some slow down issues where unlocking the phone or going back to the home screen would take more than 5 seconds. I just reflashed on Saturday and haven't experienced what I was before.
The flash issues I've had could be limited to my phone, so I won't be giving any grief to the ROM itself, and reflashing seems to fix it.
I like Paragon because it is fast, I like the theme and don't have to change it every time I flash, battery life is good enough for me to make it every day with only charging at night, and it has Bluetooth voice dialing. The Dev is also constantly updating the ROM to make it better and is doing a great job at it.
Seems over all everyone is VERY happy with the rom...Like I said before I have browsed many roms and Paragon seems to be the one.
Couple more questions. Reading through various posts in the forums, there seems to be quite a few different ways to flash. Is it necessary to remove the battery and external SD card to get into download mode then run ODIN to go to stock 2.1 and then master clear? Some say yes, some say not necessary to use ODIN if you are currently running stock 2.1. I have removed my lagfix btw.
Is it necessary to use ROM MANGER opposed to simply booting into revovery mode yourself to flash the rom?
Paragaon defaults when installed with a standard o/c of 1200 correct? Seems most find that very stable, where 1400 is possilbe but less likely to hit.
Thanks again!
So this was my setup when auto-rotate decided to cut itself out on me. I had been using this setup for over a week now at least.
Paragon RC 5.1, default kernel (1200MHz, 500Hz?)
Generation X 2.0 theme, blue version (from i9000 theme forums)
Now, out of nowhere, my phone's gyroscope stops working on me. Out of nowhere as in, phone hasn't been reset, nothing flashed recently, no new apps installed, nothing, just regular usage.
I tried using the methods in the other threads I found (deleting /data/system/ms3c_yamaha.cfg, then running /system/bin/sensorcalibutil_yamaha to manually recalibrate). Didn't work. Reflashed, wiped, all using CWM, nothing worked.
The sensor was stuck, and all the sensor readings would show that it was flat on a table (0,0,213 or something like that, the calibration utility in the Settings menu would show the ball dead center and not move).
Then I got stuck in bootloop and lost 3-button recovery mode after trying to flash 2.2 Rogers stock via CWM and forgetting to wipe data, and having to Odin flash to stock 2.1 AT&T in order to get 3-button recovery back, then flashed 2e, got CWM and clean installed Paragon from there, and then got rid of the AT&T splash screen.
However, I did notice that after flashing 2.1 AT&T (JH7) and booting to check if the update went through, the gyroscope sensor was working again.
Weird. But I guess that's why people say in the forums to flash to stock via Odin...
ANYWAYS. I literally just finished fixing it. What a painful work-around just because of auto-rotate, in order to get the gyroscope working again, and I don't even know why it stopped working. Definitely a huge negative experience. On the other hand, I'm sure it's an isolated incident not to do specifically with the rom.
On the plus side, battery life is reasonable, call quality and signal strength are great, JS3-based which means lots of themes from the i9000 forums, frequent updates, lots of features and oc/uv options. Did I mention it's fast?
Please PLEASE make sure you know how to restore your phone before flash ANY ROM!
I don't personally run this ROM (for the moment but I've heard good things overall about it.
Good thing about flashing custom ROM's - if you don't like it you have a doze others to choose from!
Well I took the plunge and installed Paragon 5.1...and SO FAR I LOVE IT. Blazing fast compaired to stock even with lagfix installed. Haven't had much time to test all things...but so far...SWEET!
I loved this rom. The best.
Senda from my Captivate with Paragon RC5.1 wait for rc6
Well been using it for a few days now, and I must say...IMPRESSIVE! Speed is great! So far I have found no bugs myself. The GPS is AMAZING! Locks in just a few seconds and I can now travel on an interstate at 65 and it keeps up with me, never thought I would see that on the captivate. Only issues really is my battery life is a bit less, but not much. just installed Juice Defender to see if that helps a bit. I am going to donate for this one! Can't wait to see what RC6 will be like...
gandalf21502 said:
Well been using it for a few days now, and I must say...IMPRESSIVE! Speed is great! So far I have found no bugs myself. The GPS is AMAZING! Locks in just a few seconds and I can now travel on an interstate at 65 and it keeps up with me, never thought I would see that on the captivate. Only issues really is my battery life is a bit less, but not much. just installed Juice Defender to see if that helps a bit. I am going to donate for this one! Can't wait to see what RC6 will be like...
Click to expand...
Click to collapse
Juice defender will actually shorten your time between charges....don't use it. Paragon for me has been awesome. I have been running it since rc3 and it has definitely stopped my urge to flash. Battery life has been amazing and average between 18 and 26 hours on my phone (usually around 20 hours). Play with some tweaks, try out the different paragon kernels and play with your uv settings. When you find the right settings you will be amazed!
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5.1 1200 mhz/100hz kernel
I love this rom is fast and nice look
Senda from my Captivate with Paragon RC5.1 and waiting for rc6
Issues with Juice Defender? I have heard good things about it....what problems have you had using it? I installed it yesterday, really haven't seen any 'real' difference myself, but I am just using the defualt settings for now.
I am using the default kernel that came with the rom 1200/500. I set via OC/UV all my settings to -75. Max core 1200. Min 100.
My nook is booting up fine, but once it gets to the android interface after a couple seconds or minutes, it just freezes and I can't do anything until I reboot. Has anyone else had any similar issues like this?
If this is a repost, I'm sorry just point me in the right direction as I could not find anything.
Edit: This may be linked to beautiful widgets? I have reflashed CM7 twice now, seems to be linked to that.
Yep, BW will do exactly that. Fancy Widgets is a decent alternative for a large clock widget
I've been having a similar problem after I rerooted and installed phiremod. I can rarely even boot up and have a functional tablet. It almost instantly freezes and must be reboot only to do it again.
reeeaaally pissing me off.
---------- Post added at 05:24 PM ---------- Previous post was at 05:10 PM ----------
after about 10 reboots I was able get it running long enough to uninstall beautiful widgets and after another reboot it seems to have solved the problem. Its a bummer though cause it a good app.
I had the same problems with Beautiful Widgets and the BeWeather widgets. I've read Fancy Widgets work and I'm currently using HD Widgets since it has a 4x4 widget and hasn't given me any problems.
Sent from my PG86100 using xda premium
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
mondegreen said:
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
Click to expand...
Click to collapse
Are you overclocked? And I assume since you mention SD card, you normally run from the internal storage? And is this a hard freeze while you're using it, or some time later while the screen is off?
1. Not overclocked. Completely pure, just-installed, CM7 with no changes to default settings. No GApps even.
2. I had the same problem when running from internal. Switched to the SD card to see if that would change anything--it didn't'.
3. Hard freeze occurs while using it.
Thanks!
I also had major freezing w/7.1. I flashed the last nightly (11/16/11) and gaaps.
http://download.cyanogenmod.com/?device=encore
Although freezing might happen once in awhile, it's rare now. I only use one widget (wifi signal). Everything else is pretty much default. No overclocking, live wallpaper, themes, etc.
I've downloaded about 20 apps so far.
Yep, it is caused by beautiful Widgets. I had the same thing happen and I posted on their development forums. I was able to get the startup logs and send them to the developer. Then the response was he could not figure out the bug. The logs clear showed a problem when trying to load the bw, but the bug may have been down deeper the operation system.
Not sure. But bummed none the less.....
Sent from my NookColor using Xparent Green Tapatalk
I was having a similar issue. However I didn't have Beautiful Widgets installed. I solved this by going to the Cyanogen CPU settings. I set minimum to 800mhz, max to 1200mhz and the profile to performance. I also checked the SET ON BOOT (can't recall the exact wording.) After a reboot, I haven't experienced any freezing. Hope this helps you guys.
Thanks.
I will give that a try with a beautiful widget on my home screen. then I will report back on my findings.
Update: nope that did not fix the problem for beautiful Widgets. I made your changes, rebooted, added a super clock widget to my home screen, rebooted, it froze. Thanks for the idea, though.
Sent from my DROID2 using Xparent Green Tapatalk
I've been following this thread as I have been experiencing the same thing, I ridded the nook of BW and it hasn't helped the freezing upon boot issue, even knocked up the min setting to 800. I've reflashed a million times. This came out of no where.
Edit: its getting really annoying. This thing isn't even useful. Never occurs with the ics preview. Only with any cm rom.
Sent from my PG06100 using xda premium
Sorry to hear that. The only time I have really experienced freezing, it was always because of some application. Is there some application that you always install that could be causing the issue. I know at one point it seemed like a certain version of flash would freeze mine, even if it was just installed not being used. Are you using the most recent stable build of cm7?
for now I have switched to ics on my nook, just for fun, I wanted to be able to make my own nightlies so I set that up . Will have to try a beautiful widget on there once I make a backup.
Sent from my DROID2 using Xparent Green Tapatalk
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
---------- Post added at 04:10 PM ---------- Previous post was at 03:30 PM ----------
carlosraf20 said:
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
Click to expand...
Click to collapse
reporting back still freezes , i will install cm-7.1.0-encore-signed.zip stable tonight and see what happens, what oc kernel to go with stable cm?
So for what it's worth currently beautiful Widgets seem to work on nook color ICS without freezing it up. But ICS is still in it's infancy.
By the way are you running off an sd card or Emmc? Running off an sd card is not nearly as good and that can cause a lot of freezing. Just throwing that out there.
Sent from my NookColor CM9 pre-alpha using Xparent Green Tapatalk
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
peanjr said:
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
how do u find out it was nook tweaks that was causing this?
Because it always ran just fine, until I installed nook tweaks checked "set on boot" for the cpu settings. I didn't change them, just ticked it. After that, anytime i rebooted, it was a fight to keep it on. So i removed the last thing i put on there, nook tweaks. Its not froze one time and I've rebooted it a whole since then. I reinstalled it but never opened the cpu settings, just edit the audio stuff, no freezes. Kinda wierd.
Sent from my PG06100 using xda premium
I just install cm 7.1 stable and change the kernel to daligrin 603011 and still having freezing issues . I don't want to do it ,but i guess i will have to do a complete wipe and then install cm 7.1 fresh.
Nook Color freezing issues
I too have having freezing issues.
Symptoms: I'll be using my Nook Color with no issues when it suddenly just locks up. No error of any sort on the screen. Screen does not black out. It just locks up. I think everytime it has happened has been after I've transferred several MB (over 5 at least) of data over Wi-Fi.
I'm running CM7.2.0 RC0 KANG build from 11/30/2011 from eMMC.
I'm overclocking to 1200 with the Min CPU set to 800 and the governor set to Performance. I also tried Max CPU at 1100 but that didn't make a difference. I'd had Min CPU at 300 but moved to 800 based on a suggestion found here. Setting the Governor to Ondemand didn't make a difference either.
I do have Nook Tweaks installed but have changed nothing from the defaults and nothing is set to start up at boot time. (I use it to get to USB Host Mode.)
With this build I haven't had any screens of death like I was getting on CM7.1. Just the freeze-ups.
Anyone else seeing a pattern with Wi-Fi?
I've never installed Beautiful Widgets.
Hi everyone
Recently, i've updated my i9000 from cm9 to cm10. But i found it a little bit laggy, there is too much data run in the background and my phone can't just handel it. Some app don't work anymore (i have some message after an unsuccefull update saying "out of memory").
Do i have to wait for further updates or should i go back to the latest CM9 ?
PS: Is there any tips to prevent the shuting down signal problem with the i9000 ?
Hey,
I've had the same feeling about CM10 being laggy on my I9000. Hopefully it's just another bug.
And it is a well known issue that some apps aren't still running yet.
I went back to CM9.1 which runs really smooth. I'm gonna wait for a CM10 stable version and check if it's still laggy.
Sent from my GT-I9000 using xda app-developers app
Yust move apps to SD, CM10 has a new partition layout.. That solve the problem of low space
Try elitemovil rc12.1 which is faster and smooter than stock sgs3
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
You should try the new nightlies, hardly any lag at all.
All jellybean roms get laggy no matter what you do, I tried most of the JB roms and I used HellyBean for a while with super launcher (a custom supercharge for galaxy s) and it kept working fine because somehow by flashing a new rom version often the phone would stay fine (wasn't just wipe cache and dalvik)
But I'm now back to ICS because even if most of the time the phone is doing fine, when you need it the most it starts failing even overclocked at 1.4 and with performance mode and swap, so I will wait 11 days and buy the nexus 4 !
Jelly bean runs fine on my phone to be honest. No lag or nothing. Only ROM that's ever lagged is hellybean.
Sent from my GT-I9000 using xda premium
On X-Bean 3.0 + Semaphore 2.5.0s here. LiveOc 120, ondemand ui, noop/sio, big mem 404mb, rasd 1024. Running smooth & stable here. No lag, reboots etc whatsoever
NIMBAH said:
Jelly bean runs fine on my phone to be honest. No lag or nothing. Only ROM that's ever lagged is hellybean.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
So u r all alone with that!
For me its totally different!
getapatalked
[email protected]@tz said:
So u r all alone with that!
For me its totally different!
getapatalked
Click to expand...
Click to collapse
Try elite v4 before speak
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
[email protected]@tz said:
So u r all alone with that!
For me its totally different!
getapatalked
Click to expand...
Click to collapse
My experience is the exact same as the one you quoted.
I believe the clue to having a stable jb is to avoid most of the non-vanilla settings. I.e people come in various jb threads claiming bugs and unstability, while having oced, deep idle, custom kernels with experimental settings, not having wiped, flashed the wrong package - lots of issues that are experimental and not stock and stable.
The question of what is stable is relative, but I'm convinced that the ability to read, knowledge, proper flashing and simple logic would help avoid 9 out of 10 "unstable" jellybean experiences.
I am aware this might come over as a bit condescending, and I guess that's partially true, but it's not directed at any particular person here.
Sent from horseback.
people, CM10 is the best. I've never had such a great rom, I mean, the SGS I is old, but with CM10, oh boy... I've never had such a good battery life, such a smooth rom, and non laggy ( helly bean was a disaster, it lagged a lot and very few updates).
Well, here is my settings:
-> CM10 latest nightly
-> JB hugemem patch (391mb ram and 720p recording still working)
-> Rom Slimmer
-> Semaphore kernel 2.5.0s:
.......- oc 1140 MHz
.......- SIO
.......- Smartassv2
.......- 512kb read ahead
-> SUPERLAUNCHER + SQLITE
Difusal said:
people, CM10 is the best. I've never had such a great rom, I mean, the SGS I is old, but with CM10, oh boy... I've never had such a good battery life, such a smooth rom, and non laggy ( helly bean was a disaster, it lagged a lot and very few updates).
Well, here is my settings:
-> CM10 latest nightly
-> JB hugemem patch (391mb ram and 720p recording still working)
-> Rom Slimmer
-> Semaphore kernel 2.5.0s:
.......- oc 1140 MHz
.......- SIO
.......- Smartassv2
.......- 512kb read ahead
-> SUPERLAUNCHER + SQLITE
Click to expand...
Click to collapse
i cant believe that so many ppl are busting HB.
laggy disaster?
first of all, HB is a CM10 too.
and beside this HB isnt laggy!
sometimes it depends on the phone, cos a SGS1 is not a SGS1. so many differences available...
best is, just try some JB ROMs and decide for urself!
I never had problems with CM10 . Run smooth .
I think is the best ROM i had experienced on my SGSI .
I installed slimbean (cm10 based) recently on my i9000m and its a tad laggy when I am pushing it but overall its better than the last stock GB rom that I had been on for a long time (got tired flashing this and that). And its stable too. Overall the switch has been nice, for the main reason that I have less of a desire for the SGS 3 (hey there's always the 4 one day right?)
My experience with cm10.1 has been roller coaster. To day it is fast and smooth but yesterday it is leggy and gets stuck. I frequently get popups of applications not responding etc. The i click wait and it gets done.
Before you throw me with rotten tomatoes let me give you the steps that i followed.
Got a brand new i9000 from from a warranty claim a month ago.
Flashed cm10.1 nightly using Cwm after having to work around a few bugs with the new heimdall program not being compatible. But with CWM on I no longer needed the pc.
Download a nightly (26 Feb)
So did a factory reset and wiped everything. Flashed cm10.1 nightly again just to make sure. Then loaded a modem that seems to work for my area. The modem is a XXJVR and is a ICS modem. then flashed Google app for jb 4. 2.2.
Rebooted and logged in. Restored all my sms using sms+ backup and restore
Installed all my preferred application from play Store.
It started nice but soon became slow and large.
So I updated to 10.1m2. Same problem.
At this moment it is workable. It takes about 6 counts to respond to changing from portrait to landscape. If i turn it one the home screen takes about 2 counts to get updated and responsive.
Holding the home button gives you the recent application list. It takes about 2 counts to respond with a vibration and then 2 to 3 more counts before the menu pops up and the list of recent applications have been populate. I don't know if this is normal but 5 counts feels forever when you decide to do something and need to wait for the system to be ready.
I am not over clocking and I am running no custom kernels.
The notification bar at first comes down in jumps. If i do it again it is smooth.
But the biggest frustration is typing. The lag between presses and haptic feedback seems to be random. It is always under a half a second but when you want to type you never know if it got the press or not. Just as you think you need go repress the letter updates.
Battery life is also erratic. Yesterday the phone was uncomfortable hot in my pocket all day. Battery did not make 14h. Today it is cool and it is at 73 % for 9h.
The main battery life is taken by android OS and screen. Not calls or any of the chat apps that I use. Yesterday Android OS took half my battery life.
Going to apps the zoom is jumpy and sliding jumps. If i do it again it is smooth.
And today is a good day.
Any suggestions what I can do to improve the performance? Except getting a new phone.
H
I don't think I can quite relate to that, my phone runs CM10.1 quite well...
Had to be said though that I can feel my phone struggles running it, pushing the limits pretty hard.
My phone has the slow RAM, unfortunately, I'm sure a lot of the people posting stories of glory are ones with the faster version.
That said, I could never in a million years go back to an earlier version, I know my phones limits and work around them without too much trouble, mainly browsing (using Chrome) is the one thing my phone struggles with.
But regarding your erratic phone behavior, have you installed a startup manager and better battery stats?
Android battery stats doesn't always do a very good job of reporting exactly what apps or background processes are draining over time...
Sent from my GT-I9000 using xda premium
jjziets said:
My experience with cm10.1 has been roller coaster. To day it is fast and smooth but yesterday it is leggy and gets stuck. I frequently get popups of applications not responding etc. The i click wait and it gets done. .....
Click to expand...
Click to collapse
It been quite some time now, but have you been able to fix your erratic behaviour? Cause I'm experiencing something similar.
I tried Slim JB & Fishears Rom so far. Right after flashing, without any apps, the roms seem to be running smooth but Slim JB soon became laggy so I tried out Fishears Rom which seemed to behave smoothly even after installing some apps.
But after several month of usage the system slowed down almost as much as it was with Slim JB.
As both of them are based on CM I guess it's a general problem that the SGS 1 just can't handle the new Rom + big amout of apps. Sometimes it runs relatively smooth if I cleared RAM etc and didn't start any apps, but as soon as I for example listen to music in the background everything just becomes laggy :-/
I guess after 3 years my SGS1 is just too old now^^
p-walker said:
It been quite some time now, but have you been able to fix your erratic behaviour? Cause I'm experiencing something similar.
I tried Slim JB & Fishears Rom so far. Right after flashing, without any apps, the roms seem to be running smooth but Slim JB soon became laggy so I tried out Fishears Rom which seemed to behave smoothly even after installing some apps.
But after several month of usage the system slowed down almost as much as it was with Slim JB.
As both of them are based on CM I guess it's a general problem that the SGS 1 just can't handle the new Rom + big amout of apps. Sometimes it runs relatively smooth if I cleared RAM etc and didn't start any apps, but as soon as I for example listen to music in the background everything just becomes laggy :-/
I guess after 3 years my SGS1 is just too old now^^
Click to expand...
Click to collapse
Hi. No I gave up. My first SGS1 was amazing and did not behave like this. I think it had faster ram. Due to some issue it was replaced under warranty. The replacement looks the same but it is very frustrating. I am running stock rom now 2.3.4 with almost nothing installed. But it find that it is a pain. Calling takes long to actuality start to dial. The screens are smooth but when you do things. Like flip between apps or go to dialler it is almost unusable.
I think Samsung release more expensive variations in the beginning and then keep the look the same but drop the cost of the handset to the end.
Hi.
I'm a noob in this custom business and i have a i9000 and i just flashed CM10.1.2 and everything is ok but i want to use igo and after install i get an error about the sd card. How can i use igo?
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work for me...
-Increased minimum clock speed
-Increased voltage of minimum clock speed
-Removed Titanium Backup
-Removed all third party apps
-Disabled deep idle
-Removed/didn't use task killers
-Tried various ICS & JB ROMs
-Tried various ICS and JB kernels, including baked-in versions
-Tried i9000 bootloaders
These are pretty much all the details I have so far on these SoDs, hopefully they add up to a possible cause or explanation...
-SoDs happen anywhere from 1-2 times an hour to 1-2 times a day and only when screen is locked/phone is idle
-Having GrooveIP or Skype running doesn't prevent SoDs, but Pandora Radio running seems to prevent it
-Sometimes on a fresh ROM install I can go about 24-36 hours before the first sleep death, but after that they occur normally
-If I unlock the screen every few minutes it seems to stay on. If I let it sit anywhere from 15-30 minutes or longer then it will usually shut off.
-The only time I can get this phone to not suffer an SoD is on stock software(GB KK4). Not sure what this means, but it is aggravating because I would like to have better software.
What remedies have you tried, and what worked/didn't work for you?
johnnyrichter said:
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work are...
-Increase minimum clock speed
-Increase voltage of minimum clock speed
-Remove Titanium Backup
-Remove all third party apps
-Oneclick back to stock with most recent GB bootloaders
-Disable deep idle
-Remove/don't use task killers
My sleep-deaths are random, almost always occur over night while I'm asleep, can sometimes happen within seconds or minutes after locking the screen. Leaving apps running also doesn't stop the problem(GrooveIP is always running, Skype is running most of the time).
The only thing that stops sleep deaths on my phone is leaving it plugged in.
What remedies have you tried, and what worked/didn't work for you?
Click to expand...
Click to collapse
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
BWolf56 said:
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
Click to expand...
Click to collapse
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
johnnyrichter said:
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
Click to expand...
Click to collapse
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
BWolf56 said:
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
Click to expand...
Click to collapse
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
johnnyrichter said:
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
Click to expand...
Click to collapse
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
BWolf56 said:
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
Click to expand...
Click to collapse
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.
johnnyrichter said:
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.
Click to expand...
Click to collapse
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.
BWolf56 said:
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.
Click to expand...
Click to collapse
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
johnnyrichter said:
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
Click to expand...
Click to collapse
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
BWolf56 said:
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
Click to expand...
Click to collapse
I'll check out that app right now and report back with any findings.
johnnyrichter said:
I'll check out that app right now and report back with any findings.
Click to expand...
Click to collapse
Booted phone up just now after an SoD and the only log available is the one it just started. So if it logged anything before it looks like it didn't save it. Crap.
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.
johnnyrichter said:
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.
Click to expand...
Click to collapse
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Still no SoD and that's with/without Skype running. GrooveIP boots with phone.
If it won't SoD on stock software then I wonder what the problem could be? It's SoD'd with every kernel and ROM I've ever tried.
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app
JoeCastellon said:
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
SoD means, while idle, that it randomly turns itself off. It was a defect in X amount of phones produced up to a certain IMEI number, and ATT/Samsung at one point offered an exchange program so people can turn theirs in for a model that didn't have the issue.
What you're suffering from is low memory. You probably have apps running in the background that are utilizing X amount of RAM, and your browsing/gaming is eating up the rest which slows down the phone. Some ways to fix this...
-Use a kernel that allows you to increase maximum memory. I think Devil kernel allows up to 396mb with no downsides, and 413mb at the cost of something that has to do with playing a certain video resolution IIRC.
-Use a task killer. This lets you kill running tasks except for those you choose to "lock." Some advise against using a task killer, but honestly I've yet to have a problem with any of them. My favorite is the one you can get for GOLauncherEX.
-Use Titanium Backup to delete(or freeze if you buy the pro version) apps that you don't use that you can safely remove, specifically items that constantly run in the background eating up your RAM.
-Use a different ROM. There's plenty of ROMs out there including slim/aosp/etc releases that are faster and arguably better-performing.
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.
BWolf56 said:
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.
Click to expand...
Click to collapse
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
ETA: If it matters any, when I got the phone I believe it was on GB KK4 and was never modded before. When I got it I used the easy-root to corn 7.0a method and first ran Legend5 ICS ROM. That was the first time I started suffering sleep deaths. Ever since then I have used the one-click back to stock w/ GB bootloaders before using any other kernel or rom.
I've used several different kernels/cwm versions to obtain root, at least 6 different ROMs, several different versions of gapps, and numerous other kernels after ROM installation. I've also used the baked-in kernel of each ROM for at least several days before upgrading to something like Devil or Sema. SoDs on everything, both ICS and JB.
I have also tried one-clicking back to stock with what I believe were "up-to-date" GB bootloaders. This was posted by another member that did it and fixed his SoD problem. It didn't produce any sort of a change for me.
I have not tried checking for SoDs on just a root(without ROM). I suppose if I did this I could figure out if it's the root or the ROM that is triggering the sleep deaths, but even if I did get any results from that I'm still not sure how to figure out exactly what's causing the problem since this event apparently can't be logged.
johnnyrichter said:
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
Click to expand...
Click to collapse
Mosaic is a ROM that was made by The Family; http://forum.xda-developers.com/showthread.php?t=1061203
It is I9000 based so I'm thinking you won't get any SoD on it. Thing is that it's not JB based. Devs aren't porting from I9000 anymore so you won't find a I9000 ported JB ROM. (Hoping I'm not wrong on this lol)
And yeah, many users reported that flashing the I9000 bootloaders with a JB ROM fixed their SoD problem. Back in GB, it wasn't suggested to have I9000 bootloaders and run a I897 ROM (music player wouldn't work and some other little things) but it seems fine now.
EDIT: I highly doubt root is the problem.
My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues！
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...