Related
I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF
Hi..
I Have a nexus one. My question is regarding the CyanogenMod Nighty and stable. whats the difference? Which one should i use? Which is better?
Thanks.
Nightly build = Work-in-Progress version. You can try new features, but it can be buggy and less stable. Besides, there's no support provided officially.
Stable = The 'Official' version.
great
Thanks a bunch, helped me out
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
bassmadrigal said:
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
Click to expand...
Click to collapse
I just checked the website and for the nighty it has #81. I understand the part of updating at night. My question is like how u said that you are on #76, so do you have to manually change to #81(by flashing and making a backup) or it automatically updates? Am confused.
You manually update like you would a normal release of CyanogenMod. If you have the premium version of ROM Manager, it can notify you of new nightlies and you can download them through it. If you don't have it, you would manually have to download the files from http://mirror.teamdouche.net.
And I ALWAYS recommend making a backup. That way, if one of the nightlies you install is all screwed up, you just revert to the last one and wait until it is fixed bfore you flash the next verison.
You don't really have to wipe when going to the next nightly. Just flash and all your data is in tact, just like a regular upgrade.
I suggest going with the latest nightly.
Curious about experiences. Right now I'm on the M3 Experimental.
It's really stable.. By far the most stable cm10.1 build I've ever used. Only thing Is the instagram videos come out fuzzed out and you can't see anything. That Sux
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Only one bluescreen in 24 hours so far. Using its boot image in the newest Slimbean, hope it continues to hold up.
I was just coming to post this exact same question. I had to go back to M3 because there were too many bugs in the subsequent nightlies.
But I think i'll try RC-5 and see what it's about.
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
jdekoven said:
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
Click to expand...
Click to collapse
The bluetooth issue seems inherent in any of the 4.2.2 roms. I've done clean installs , wiped with Darkside, etc. It doesn't really seem to matter.
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Installed 10.1.0 using the updater and had lots of problems. Audio bad, Bluetooth not working. Installed clean with a factory reset and it is very stable. Only issue is still some camera apps (Google drive scan, latest evernote) require setting Disable HW Overlays. But other than that, seems good
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
Lots of random reboots followed by a blue screen, I have noticed that it happens a lot during or after viewing a video and certain games, it even has happened while texting. No where near stable, battery life is horrible and like I said the reboots are random but often.
I'm using the CM 10.1 stable release as the boot image for PAC-Man rom. So far, no blue screens, reboots or anything. I've messed around with it, adding the Google edition camera and other goodies I found in i717 forum. Flashed in the S-4 launcher and everything is still holding together. Battery life is okay, considering I'm using livewall paper and wifi also. 60% remaining after four hours.
I'll give it a few days to settle in.
10.1.0 (4.2.2), good so far
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
I've been running the 'stable' version for a couple days and only one b.s.o.d. Runs smooth and battery is about the same at RC5. Camera is good as well. Don't use Blu-tooth so can't testify for that. I reboot every morning and that seems to make a world of difference.
Wish stock JB would come to us.
Anyone know how to get stock screen resolution back?
20130804-Nightly stable
Hey all, just thought that since I complained about how buggy the nigthlies were, I should come back and say that I am now on the 20130804 and it is very stable. I have been using it since Monday and i've only have one reboot. I initially had some screen flickering when I had a solid green background (from an MIUI theme), but I switched to another wallpaper and don't have that problem anymore.
Just FYI.
The M10 build of CM11 just came out, I read the blog post and saw the new version in my OTA updates (I flashed CWM to internal so I can do that and have for a few versions). I know it will probably go smoothly, but the horror stories about boot loops, soft bricks, and Android system process crashes that I've read about in the comments make me really nervous. Nobody's yet posted about the HD+/Ovation, but the first 5 CM11 M updates were all bad, even with a complete wipe, so I don't want to take the risk.
I am aware, though, that there are many users here who literally keep their devices for development and ROM testing purposes and don't have (much) personal date to worry about losing. Not so for me. So, I was wondering, could anyone do a CWM backup to SD, perform the OTA upgrade from the settings panel, and write a review/say what happens? Note that I have the most recent gapps installed, so those should be tested because they may cause issues.
Preferably someone with gapps who was going to do an upgrade anyway, so I don't inconvenience anyone by having them upgrade where they otherwise wouldn't.
You hint, but do not really say, that you already have CM11 installed. If so what version?
Many have already tried M10 and said there are issues with media scanner if you dirty install. See the CM11 thread.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You hint, but do not really say, that you already have CM11 installed. If so what version?
Many have already tried M10 and said there are issues with media scanner if you dirty install. See the CM11 thread.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
M9, and it works perfectly, which is why I'm wary about updating. Also, the media scanner error can apparently be fixed by wiping the app's data/cache in settings and rebooting.
Seanthedroid said:
M9, and it works perfectly, which is why I'm wary about updating. Also, the media scanner error can apparently be fixed by wiping the app's data/cache in settings and rebooting.
Click to expand...
Click to collapse
I installed M10 over M9, and it went very smooth. The usually two reboots, followed by optimising apps, and everything is up and running again. If anything comes up, I will certainly mention it.
Seanthedroid said:
The M10 build of CM11 just came out, I read the blog post and saw the new version in my OTA updates (I flashed CWM to internal so I can do that and have for a few versions). I know it will probably go smoothly, but the horror stories about boot loops, soft bricks, and Android system process crashes that I've read about in the comments make me really nervous. Nobody's yet posted about the HD+/Ovation, but the first 5 CM11 M updates were all bad, even with a complete wipe, so I don't want to take the risk.
I am aware, though, that there are many users here who literally keep their devices for development and ROM testing purposes and don't have (much) personal date to worry about losing. Not so for me. So, I was wondering, could anyone do a CWM backup to SD, perform the OTA upgrade from the settings panel, and write a review/say what happens? Note that I have the most recent gapps installed, so those should be tested because they may cause issues.
Preferably someone with gapps who was going to do an upgrade anyway, so I don't inconvenience anyone by having them upgrade where they otherwise wouldn't.
Click to expand...
Click to collapse
I went from 10.2.1 to cm 11 nightlies just a few weeks ago and was pleased except for a few glitches like screen flashes between apps. When m10 came out I decided to go for what I understood as a generally more stable rom. Unfortunately I did not wipe first as I had upgraded from previous nghtlies without a problem. I had some issues as mentioned in another thread and realized you must wipe before install and I reinstalled. So far so good and I thank titanium for making restoration so easy. I still see screen flashes and a few random crashes but it seems good.
MrPuddington said:
I installed M10 over M9, and it went very smooth. The usually two reboots, followed by optimising apps, and everything is up and running again. If anything comes up, I will certainly mention it.
Click to expand...
Click to collapse
I've just upgraded to m10, it's smooth and stable
But my device is slow, maybe cpu of nook hd+ is weak
Sent from my C6916 using Tapatalk
USRobotics said:
I've just upgraded to m10, it's smooth and stable
But my device is slow, maybe cpu of nook hd+ is weak
Sent from my C6916 using Tapatalk
Click to expand...
Click to collapse
My HD+ also seems quite slow, especially as I load more apps on the 32GB internal card. My 7" HD has no issues with m10 nightlies, and is quite peppy.
danshane said:
My HD+ also seems quite slow, especially as I load more apps on the 32GB internal card. My 7" HD has no issues with m10 nightlies, and is quite peppy.
Click to expand...
Click to collapse
I had noticed an interesting sort of choppiness or hitching after first flashing M10 but it either has gone away or I'm now adjusted to it. It wasn't much to begin with but it was there. Otherwise, that was all.
My nook is ~138 apps during the cache configuration (art) upon first boot as the best number I can give for app load. Surely the more apps and the more background services running on the device the harder it will be for it to keep everything going as fast as possible. If your not on art, that might help (recovery backup first for safety + be aware of art's hunger for more internal storage).
Otherwise, its also possible to "out grow" the device and need something more powerful at the same screen size. If your needs change, the device may need to be changed. (Or similar). Too many apps and you could find yourself there.
sandsofmyst said:
If your not on art, that might help (recovery backup first for safety + be aware of art's hunger for more internal storage).
Otherwise, its also possible to "out grow" the device and need something more powerful at the same screen size. If your needs change, the device may need to be changed. (Or similar). Too many apps and you could find yourself there.
Click to expand...
Click to collapse
I tried ART with no improvement, so i am just going to experiment with a different build. My wife has an identical, fully loaded HD+ that zips right along on CM 10 with Jelly Bean, and my HD has no lag with KitKat, so I am not worried that the hardware will not handle the job. My son has an old Nook Tablet (pre-HD) that is really peppy on CM11 KitKat. I think all the Nook models are great for modding, and I am sure I will get this one performing as I like once I hit on the right combination.
** UPDATE ** I installed the latest Pac-Man ROM and I am now getting the performance I hoped for.
Installed M10. Did full wipe.
Was running a nightly from 03/2014 that was rock solid and fast (using ART).
All I can say to any one thinking of going to M10 is prepare to be disappointed. Its really laggy, even with other launchers, it looks terrible, the refresh rate/redraws/whatever are really obvious. Uncomfortably obvious. The screen sensitivity is really bad. Not responsive at all. I am looking forward to checking out the battery life over the next few days, because I have a sneaking suspicion it will deliver the trifecta of slower speeds, less responsive screen and worse battery life.
Trebuchet seems to be getting worse and worse. I wish Cyanogenmod would do a deal with one of the proper launchers and stop subjecting us to the substandard experience that is Trebuchet.
Oh yeah, and to top it all, the HD+ will no longer turn off. Selecting power off in the power menu just reboots the device. I now have to reboot into recovery and power off from there.
I am really disappointed. After all that effort backing up, wiping and reinstalling everything and actually took several (so many!) steps backwards.
gandalf_grey91 said:
Installed M10. Did full wipe.
Was running a nightly from 03/2014 that was rock solid and fast (using ART).
All I can say to any one thinking of going to M10 is prepare to be disappointed. Its really laggy, even with other launchers, it looks terrible, the refresh rate/redraws/whatever are really obvious. Uncomfortably obvious. The screen sensitivity is really bad. Not responsive at all. I am looking forward to checking out the battery life over the next few days, because I have a sneaking suspicion it will deliver the trifecta of slower speeds, less responsive screen and worse battery life.
Trebuchet seems to be getting worse and worse. I wish Cyanogenmod would do a deal with one of the proper launchers and stop subjecting us to the substandard experience that is Trebuchet.
Oh yeah, and to top it all, the HD+ will no longer turn off. Selecting power off in the power menu just reboots the device. I now have to reboot into recovery and power off from there.
...
Click to expand...
Click to collapse
I upgraded to M10 from M9 and so far had none of the issues you described. The only and somewhat minor problem is ~25% of Playstore app updates would abort on first try.
FWIW I use the Nova launcher and love it.
digixmax said:
I upgraded to M10 from M9 and so far had none of the issues you described. The only and somewhat minor problem is ~25% of Playstore app updates would abort on first try.
FWIW I use the Nova launcher and love it.
Click to expand...
Click to collapse
I can only report the facts, I was expecting a different experience from M10. Generally, I also choose to use Nova but on M10 it is suddenly jerky, jagged and uncomfortably laggy.
I believe the Play store issue is a google issue, which seems to come and go as they update Play store app. For me, it started in March of this year, was fixed later on and then came back a couple of months later, only to disappear a few weeks later..
Update: the Power Off = Reboot issue cleared up after 3 reboots/power offs. Its now working properly.
Okay so once again, another ROM has got bad after 2 weeks. FXP 349 build has got to be pretty much unsuable, the unlock button doesnt respond, and the UI crashes for a laugh now. Getting very frustrated with this phone. Its getting harder to not smash the hell out of it with a hammer.
I must be doing something wrong, but every ROM Ive used just degrades in performance to the point where I cant take how laggy it is, Ive missed phonecalls because the UI cant wake up and show the incall UI fast enough. There has to be something deep in this phone which causes bad performance.
Im moving to VanirAOSP, as it says in the title of the ROM that its fast and smooth. Lets see if it can outlast any other ROM I've tried.
Sorry for ranting, I just dont get it, is there some secret setting that everyones using and not telling about? Ive tried stock kernel with CM, williams kernel with CM, stock kernel with CrystalPA, same again with williams kernel. Art or dalvik, it seems to make no difference, no matter what, the UI will bug out. Im not moaning at the devs because I know the work they do is hard and is much appreciated. I just wish I knew why this phone cant last 2 weeks without needing to be wiped!
Every ROM gets laggy after a while. Just use some app to clear cache and thumbnails and you should be fine.
donk165 said:
Okay so once again, another ROM has got bad after 2 weeks. FXP 349 build has got to be pretty much unsuable, the unlock button doesnt respond, and the UI crashes for a laugh now. Getting very frustrated with this phone. Its getting harder to not smash the hell out of it with a hammer.
I must be doing something wrong, but every ROM Ive used just degrades in performance to the point where I cant take how laggy it is, Ive missed phonecalls because the UI cant wake up and show the incall UI fast enough. There has to be something deep in this phone which causes bad performance.
Im moving to VanirAOSP, as it says in the title of the ROM that its fast and smooth. Lets see if it can outlast any other ROM I've tried.
Sorry for ranting, I just dont get it, is there some secret setting that everyones using and not telling about? Ive tried stock kernel with CM, williams kernel with CM, stock kernel with CrystalPA, same again with williams kernel. Art or dalvik, it seems to make no difference, no matter what, the UI will bug out. Im not moaning at the devs because I know the work they do is hard and is much appreciated. I just wish I knew why this phone cant last 2 weeks without needing to be wiped!
Click to expand...
Click to collapse
I have a feeling you are installing too many apps running in background at once. My phone is super smooth, fast and responsive. I just either close apps after I am done with them (kill process) or don't install trash. Deleting some in-build rom apps which you never use could also help.
kwitu said:
I have a feeling you are installing too many apps running in background at once. My phone is super smooth, fast and responsive. I just either close apps after I am done with them (kill process) or don't install trash. Deleting some in-build rom apps which you never use could also help.
Click to expand...
Click to collapse
Well VanirAOSP has sorted out my issues for now it seems. I dont really install many apps to be honest, I use the Micro PA Gapps package and I then remove Google Now Launcher, freeze the preinstalled launcher3, install Nova launcher. I have only 17 installed apps, Facebook is the only real hog app I think, I install messenger and then freeze it to get around the Facebook app not letting me use chat within the app. I do also play Marvel Contest of Champions, and I make sure to clear all running apps before playing games. I just feel like now on this ROM, the ram is clearing properly, swiping away apps is freeing up the RAM now.
I think the difference is that this ROM is based on AOSP, whereas before, I was using CM ROM's or Crystal PA which is pretty feature rich. Ill stick with this and see if it will last. This ROM just feels noticeably faster and the UI hasnt crashed once yet, even with a theme on!
donk165 said:
Well VanirAOSP has sorted out my issues for now it seems. I dont really install many apps to be honest, I use the Micro PA Gapps package and I then remove Google Now Launcher, freeze the preinstalled launcher3, install Nova launcher. I have only 17 installed apps, Facebook is the only real hog app I think, I install messenger and then freeze it to get around the Facebook app not letting me use chat within the app. I do also play Marvel Contest of Champions, and I make sure to clear all running apps before playing games. I just feel like now on this ROM, the ram is clearing properly, swiping away apps is freeing up the RAM now.
I think the difference is that this ROM is based on AOSP, whereas before, I was using CM ROM's or Crystal PA which is pretty feature rich. Ill stick with this and see if it will last. This ROM just feels noticeably faster and the UI hasnt crashed once yet, even with a theme on!
Click to expand...
Click to collapse
I could give you a tip about Facebook app and Messenger. There is an app that lets you chat using Facebook app, meaning you can get rid of Messenger. Google it and you will find it, I can't recall the name now.
kwitu said:
I could give you a tip about Facebook app and Messenger. There is an app that lets you chat using Facebook app, meaning you can get rid of Messenger. Google it and you will find it, I can't recall the name now.
Click to expand...
Click to collapse
Well the way im doing it, i dont actually use messenger, its installed but frozen/disabled so it isnt used, this allows me to chat inside the facebook app but the only downside ive found is that the chat notification dont seem to be working. This was a fix I picked up while browsing the net. Ill try out this app if I can find it, the name would make it much easier to find
donk165 said:
Well VanirAOSP has sorted out my issues for now it seems. I dont really install many apps to be honest, I use the Micro PA Gapps package and I then remove Google Now Launcher, freeze the preinstalled launcher3, install Nova launcher. I have only 17 installed apps, Facebook is the only real hog app I think, I install messenger and then freeze it to get around the Facebook app not letting me use chat within the app. I do also play Marvel Contest of Champions, and I make sure to clear all running apps before playing games. I just feel like now on this ROM, the ram is clearing properly, swiping away apps is freeing up the RAM now.
I think the difference is that this ROM is based on AOSP, whereas before, I was using CM ROM's or Crystal PA which is pretty feature rich. Ill stick with this and see if it will last. This ROM just feels noticeably faster and the UI hasnt crashed once yet, even with a theme on!
Click to expand...
Click to collapse
And? Are you still satisfied with this rom after a while?
Well the 'ROM decay' creeped back in. I tried to counter it by cleaning things up but I had a few problems, nothing was working, I tried fix permissions from ROM toolbox and then my phone stopped booting, tried hard reset with the button on the back, couldn't get into recovery, pretty much died on me. I eventually got into recovery and caches wipes and that didn't work, I tried reinstalling the ROM and gapps without losing my data, it just got stuck on the boot logo, then recovery stopped working again, I eventually got in and had to wipe data, reinstall ROM and I finally got the phone booting again.
I'm not satisfied to be honest, its frustrating that I have to wipe the phone or reflash the roms so often, never has a phone been this bad for me. I'm selling it and moving to the OnePlus One in a few weeks, this phone has been nothing but headaches.
donk165 said:
Well the 'ROM decay' creeped back in. I tried to counter it by cleaning things up but I had a few problems, nothing was working, I tried fix permissions from ROM toolbox and then my phone stopped booting, tried hard reset with the button on the back, couldn't get into recovery, pretty much died on me. I eventually got into recovery and caches wipes and that didn't work, I tried reinstalling the ROM and gapps without losing my data, it just got stuck on the boot logo, then recovery stopped working again, I eventually got in and had to wipe data, reinstall ROM and I finally got the phone booting again.
I'm not satisfied to be honest, its frustrating that I have to wipe the phone or reflash the roms so often, never has a phone been this bad for me. I'm selling it and moving to the OnePlus One in a few weeks, this phone has been nothing but headaches.
Click to expand...
Click to collapse
IF you are going to stay or at least try for the last time, I suggest formatting /boot but please be careful as I dont really know what will happen if you reboot the device while /boot is empty.
As in PC, an empty boot partition will leave an inaccessible Operating System. If in phone they are the same then I guess it can be much repairable.
IF again it fails and you are still staying I suggest extreme formatting by using the PC Companion and start fresh.
These are still suggestions and I hope you will have a headache free adventures with One plus. Good luck
TechnoSparks said:
IF you are going to stay or at least try for the last time, I suggest formatting /boot but please be careful as I dont really know what will happen if you reboot the device while /boot is empty.
As in PC, an empty boot partition will leave an inaccessible Operating System. If in phone they are the same then I guess it can be much repairable.
IF again it fails and you are still staying I suggest extreme formatting by using the PC Companion and start fresh.
These are still suggestions and I hope you will have a headache free adventures with One plus. Good luck
Click to expand...
Click to collapse
Thanks for the advice, For me, its the lack of RAM on this phone which is my problem. After a reboot, i have about 300mb free ram, and as soon as I have more than one simple app running (or just one game), ill get a very slow UI, and I have to be very careful and patient with it or it will crash. To me, that is terrible, why would anyone think this is acceptable for a smartphone to just about be able to run an app and hold the interface together. When the System UI crashes, or the lockscreen, It frustrates me so much! The most important part of a touchscreen phone is the UI, without it, your just staring at a blank screen.
There has to be something deep in this phone (the kernel?) where its memory management is broken in someway, ive never experienced a phone be so unstable with 1GB of RAM. When I bought it, I was really hopeful it would be good, it was higher specced than my last phone, it had 4g, it had jelly bean updates coming out, and at the time, a future update to kitkat, and we had support from FXP and CM. What weve actually got is a half baked attempt at 4.3 by Sony, a cancelled 4.4 update, and weve been moved to legacy support by FXP when CM11 didnt even get to the stable point. We may have lollipop builds coming out which could be the savior for this phone, but im sick of waiting for something which might not happen. I just want to be able to rely on my phone and not spend half my screen on time waiting for something to crash and then restart.
Back on my Optimus L9, it has only 768MB ram and a lower clocked dual core CPU but that could run CM10 fine, I never ever had UI crashes, ever! I got lag from time to time, but nothing crashed. Thie SP has 100mb+ more RAM available and a higher clocked CPU but it feels so much more clunky and unstable compared to the L9, it should be the other way round. On my nexus 7 2012 which is similarly specced to the SP (apart from the tegra quad CPU) I again, had no UI crashes, I had lags, but at least things didnt crash. My friend has the Xperia L, which is lower specced than the SP and is only on 4.1, but again, he never gets UI crashes and generally, his phone can run games smoother than I can even though he has lower specs!
This phone, for me, just doesn't fit my needs. It cant really multi task how I would expect it to, and having the phone pretty much lock up if its writing to internal storage is a joke, installing an app from the play store, and not being able to bring down the notification bar to look at the progress without causing problems, to me just feels like something is seriously wrong. The lightbar was the only thing ive really liked on the phone to this day. At first, I was loving this phone, it was great, the only problem I had on 4.1 was that I couldn't play Injustice because it would close the game after a while. I thought, ill wait for software updates, hopefully Sony will fix it. Then the 4.3 updates came but they were buggy, but I held onto hope because at the time, 4.4 was in the pipeline. Then we got a few more 4.3 updates which did fix some bugs but this RAM problem was still there. So I gave up on Official software and tried out custom stuff. I've tried modified Stock ROM's where you get more features but the same inherent problems are there. Ive tried CM, but there hasnt been a stable release of 4.4 and the snapshot builds have also stopped. Vanir ROM is designed to be stable, its one of their highest priorities with their builds. And I definitely feel the difference, but this lack of RAM becomes more obvious with time, this week, I've seen my UI crash 4 times.
Ive done what you've said about fully starting fresh with PC companion Ive flashed stock FTF's and Ive done the PC companion method, Ive done that at least 5 times in the past. When I first do it, it seems like everything is okay. But without fail, after a month of use (usually less) the phone will bog down and the RAM issues return. Maybe my specific device has faulty RAM or something or maybe the storage is messed up. All I know is, this phone has not been enjoyable for me to use, lower specced phones are out performing it, and its value has plummeted in trade in stores like CEX, my old L9 that I traded into my local CEX is being sold for more money than an SP is.
Im sorry to rant but ive just had enough of this phone.
Ive got to flash the phone fully back to stock for when I sell it, so ill go back to full stock, and see if it will last.
donk165 said:
Thanks for the advice, For me, its the lack of RAM on this phone which is my problem. After a reboot, i have about 300mb free ram, and as soon as I have more than one simple app running (or just one game), ill get a very slow UI, and I have to be very careful and patient with it or it will crash. To me, that is terrible, why would anyone think this is acceptable for a smartphone to just about be able to run an app and hold the interface together. When the System UI crashes, or the lockscreen, It frustrates me so much! The most important part of a touchscreen phone is the UI, without it, your just staring at a blank screen.
There has to be something deep in this phone (the kernel?) where its memory management is broken in someway, ive never experienced a phone be so unstable with 1GB of RAM. When I bought it, I was really hopeful it would be good, it was higher specced than my last phone, it had 4g, it had jelly bean updates coming out, and at the time, a future update to kitkat, and we had support from FXP and CM. What weve actually got is a half baked attempt at 4.3 by Sony, a cancelled 4.4 update, and weve been moved to legacy support by FXP when CM11 didnt even get to the stable point. We may have lollipop builds coming out which could be the savior for this phone, but im sick of waiting for something which might not happen. I just want to be able to rely on my phone and not spend half my screen on time waiting for something to crash and then restart.
Back on my Optimus L9, it has only 768MB ram and a lower clocked dual core CPU but that could run CM10 fine, I never ever had UI crashes, ever! I got lag from time to time, but nothing crashed. Thie SP has 100mb+ more RAM available and a higher clocked CPU but it feels so much more clunky and unstable compared to the L9, it should be the other way round. On my nexus 7 2012 which is similarly specced to the SP (apart from the tegra quad CPU) I again, had no UI crashes, I had lags, but at least things didnt crash. My friend has the Xperia L, which is lower specced than the SP and is only on 4.1, but again, he never gets UI crashes and generally, his phone can run games smoother than I can even though he has lower specs!
This phone, for me, just doesn't fit my needs. It cant really multi task how I would expect it to, and having the phone pretty much lock up if its writing to internal storage is a joke, installing an app from the play store, and not being able to bring down the notification bar to look at the progress without causing problems, to me just feels like something is seriously wrong. The lightbar was the only thing ive really liked on the phone to this day. At first, I was loving this phone, it was great, the only problem I had on 4.1 was that I couldn't play Injustice because it would close the game after a while. I thought, ill wait for software updates, hopefully Sony will fix it. Then the 4.3 updates came but they were buggy, but I held onto hope because at the time, 4.4 was in the pipeline. Then we got a few more 4.3 updates which did fix some bugs but this RAM problem was still there. So I gave up on Official software and tried out custom stuff. I've tried modified Stock ROM's where you get more features but the same inherent problems are there. Ive tried CM, but there hasnt been a stable release of 4.4 and the snapshot builds have also stopped. Vanir ROM is designed to be stable, its one of their highest priorities with their builds. And I definitely feel the difference, but this lack of RAM becomes more obvious with time, this week, I've seen my UI crash 4 times.
Ive done what you've said about fully starting fresh with PC companion Ive flashed stock FTF's and Ive done the PC companion method, Ive done that at least 5 times in the past. When I first do it, it seems like everything is okay. But without fail, after a month of use (usually less) the phone will bog down and the RAM issues return. Maybe my specific device has faulty RAM or something or maybe the storage is messed up. All I know is, this phone has not been enjoyable for me to use, lower specced phones are out performing it, and its value has plummeted in trade in stores like CEX, my old L9 that I traded into my local CEX is being sold for more money than an SP is.
Im sorry to rant but ive just had enough of this phone.
Ive got to flash the phone fully back to stock for when I sell it, so ill go back to full stock, and see if it will last.
Click to expand...
Click to collapse
Its okay and I have read all of your post
It quite saddens me that some people isnt actually having fun with their SP. Shockingly enough, my SP does not face those mentioned problems (heck most of those that appears in the forum) but some exceptions goes to Stock Rom bugs and game problems.
This is my first android phone, I actually always wanted one but i am a teenager - i dont make money. But since my dad bought me this lovely sp, I have finally gained so much knowledge about android and it somehow further strengthens my Linux knowledge.
Maybe I was just lucky. Perhaps. But who knows if something is still wrong with my phone
I understand things will get older - people will buy new phones, developer will stop developing, people who got bored of customising etc. In fact I have seen so much decline of SP since the discontinued 4.4 update.
This is my first smartphone and I love it. It has an awesome community and awesome devs, but now it is getting old. Which quite sad to me.
I am saving for Ara phone (i hope it doesnt fail like smartwatches do). Since you are quite involved with many developments (i mean you customise your phone much like others), I hope your transition to a new device is a breeze. And above all, doesn't have the bugs that SP has.
LOL, I thought I was the only one with a "faulty SP".
My XSP has the exact same problems as yours. It is very annoying to change ROMS (or wipe data) every month.
The RAM is SO BAD on my SP, even though it only have 1GB of RAM, it should be a lot better. I didn't have such problems on my Motorola Defy + as I have with the XSP.
I thank so much that we have very nice developers, always trying to improve our user exp., but for some people like me it's difficult.
TechnoSparks said:
Its okay and I have read all of your post
It quite saddens me that some people isnt actually having fun with their SP. Shockingly enough, my SP does not face those mentioned problems (heck most of those that appears in the forum) but some exceptions goes to Stock Rom bugs and game problems.
This is my first android phone, I actually always wanted one but i am a teenager - i dont make money. But since my dad bought me this lovely sp, I have finally gained so much knowledge about android and it somehow further strengthens my Linux knowledge.
Maybe I was just lucky. Perhaps. But who knows if something is still wrong with my phone
I understand things will get older - people will buy new phones, developer will stop developing, people who got bored of customising etc. In fact I have seen so much decline of SP since the discontinued 4.4 update.
This is my first smartphone and I love it. It has an awesome community and awesome devs, but now it is getting old. Which quite sad to me.
I am saving for Ara phone (i hope it doesnt fail like smartwatches do). Since you are quite involved with many developments (i mean you customise your phone much like others), I hope your transition to a new device is a breeze. And above all, doesn't have the bugs that SP has.
Click to expand...
Click to collapse
Well atleast you have started on a better android device than my first one. My first was a ZTE Skate and this was back in the gingerbread days. 512MB RAM, Single core CPU, barely any internal storage. Im very used to using android in a minimalist way, but the SP just takes it to a whole different level for me, i cant take it! Im glad that you arnt having all the same problems Im having. The fact that not everyone is getting the problems is a frustration because unless its a widespread problem, people wont really be pulling together to fix it because they dont understand/experience the problems. It has to be some kind of manufacturing defect, maybe certain batches of RAM/Storage chips used in the SP are defective/bad performers.
I hope the XSP continues to work well for you!
Bruno_Puzoni said:
LOL, I thought I was the only one with a "faulty SP".
My XSP has the exact same problems as yours. It is very annoying to change ROMS (or wipe data) every month.
The RAM is SO BAD on my SP, even though it only have 1GB of RAM, it should be a lot better. I didn't have such problems on my Motorola Defy + as I have with the XSP.
I thank so much that we have very nice developers, always trying to improve our user exp., but for some people like me it's difficult.
Click to expand...
Click to collapse
Its a very weird problem, but its definitely RAM/Storage related.
I agree with you about the devs, I appreciate their hard work, it is great having all these ROM's to choose from when trying to solve the problems. It just seems it doesn't matter which ROM you are on, the problems will always be there. The problem must lie within the hardware or deep in the software side of things, beyond the ROM's like in the kernel or something. I dont know enough about those sides of a phone, but I can see just from using the phone, something isnt right.
It sucks that you are facing the same problems, but its nice to know im not alone in my experiences, its not just me.
If only we knew what the issue was, maybe there would be a chance to solve the issue.
I have the same problems with my phone exactly and am going to smash it with a hammer when I get a new phone. It is indeed so frustrating, I expect much more from sony!
i stopped to mess up with custom kernels, stock 207 is the best option.
Ondemand cpu governor + underclock to 1500mhz + greenify
Battery life + perfomance
My usage:
4 hours online gaming per day
+ some skype calls