[Q] pros & cons - Nook Color General

what are the pros or cons of upgrading to the latest nighly from cm 7.1.0-rc1?

Look here.

Honestly, I'd say all pros and no cons. I forget when deep sleep was fixed, but there's that, USB host mode, integrated Dal's OC kernel, nightly 150 brought with it a fast bootup, and those are just the main things I can think of off the top of my head.

Do they have a set of instructions for install in one place or do I need to read through the thread for that? I remember there being things about uboot and stuff but I haven't read in a while.

do you lose all you settings/apps if you just delete devlick cache? im on nightly 87 now...
Sent from my NookColor using Tapatalk

I thought I would finish my upgrading of my Nook at cm 7.1.0-rc1. I was getting Sleep Of Death (SOD) and had read that some of the new nightlies had Dalingren's OC inbuilt so went the nightly option (now am on #150).
So if you have ROM Manager (Paid), then going to Nightlies is very easy and has all the new features. ROM Manager updates you on a new build and it is a quick download and install. Nightlies also do not reset your device. Dalvik and Cache do not lose your settings as well. So, if you have ROM Manager, I would go the nightlies (just make sure you backup everything).
I am not going to guarantee it will fix everything, hence keep upgrading but have some workarounds in place.
Pros:
- All the new features and fixes (you will see improved speed, smoothness, Dalingren's OC inbuilt). Am on #150.
- Easy to do (if on ROM Manager paid). Easy to do in general but ROM Manager simplifies in general.
Cons:
- Be prepared that you backup everything. Nightlies are beta and you could have to go back to previous rom or fresh install (everyone suggests a fresh install is optimum but have only done once).
- Difficult settling for one build. You end up upgrading quite frequently and a new one can potentially break things (only happened to me once where I had to go back to a previous build). You also end up checking the comments of the next build, thinking that the next one will be the perfect build.

nolook said:
do you lose all you settings/apps if you just delete devlick cache? im on nightly 87 now...
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
No, you do not.....

Related

[Q] Samuaz's ICS ROM vs texasice's ICS ROM?

Which ROM is better?
I don't know for sure, but it seems that samuaz's is texasice's build plus the CM goodies. So I would say samuaz's has more features.
bassmadrigal said:
I don't know for sure, but it seems that samuaz's is texasice's build plus the CM goodies. So I would say samuaz's has more features.
Click to expand...
Click to collapse
Ok. Hey, aren't you that Cyanogenmod moderator?
That'd be me
why ask--try them both--
Am using texasice's ROM since like day 1 and loving it. Its my daily driver
I tried thrice to use texacise ROM [Alpha 8, ev-1, and latest p3]. There are huge improvements and p3 is quite close to be used as daily rom. However, still there are issues with network dropping off , random soft reboots and many Apps FCing.
Nexy has good future with both these ROMs progressing so fast [it is less than 50 days since google released the code].
The samuaz ROM, looking at the feedback, I'll give it a try for couple of days next week.
Yes I do notice those soft reboots with p3. But no FCs and no network drops. However the progress for each build looks quite promising.
Would be nice if Samuaz too release a mini skirt version for stock Hboot
Yet another reason not to stay on stock Hboot: Camera is already working (not completely) on N1.
Also msm kernel 3.0 is ready. Just a few days before we get ICS beta
Where can we get the msm 3.0 kernel?
JoshX said:
Where can we get the msm 3.0 kernel?
Click to expand...
Click to collapse
Where? From a kernel dev, of course.
When? When it's ready. Further questions will not aid in getting it faster.
I heard the kernel dev over at the Desire forums is going to upload his msm-3.0 sources to guthub and will make it work on the HD2 and Nexus One, of course after it works on the Desire itself.
Just wait patiently and it will be here sooner or later.
Which rom work on 2g network?
Mohamad_j said:
Which rom work on 2g network?
Click to expand...
Click to collapse
I think texasice's ROM works with 2G network.
Theshawty said:
Where? From a kernel dev, of course.
When? When it's ready. Further questions will not aid in getting it faster.
I heard the kernel dev over at the Desire forums is going to upload his msm-3.0 sources to guthub and will make it work on the HD2 and Nexus One, of course after it works on the Desire itself.
Just wait patiently and it will be here sooner or later.
Click to expand...
Click to collapse
That's what I figured, but it seemed to be implied, by indiangeek, that one was already available.
I just upgraded from CM 7 to Texas ICS p4. The market didn't work (my apps didn't auto-sync and re-download - couldn't get it working after an hour of trying), the animations were a little jerky, camera didn't work, USB mass storage didn't work, CM mods weren't there. In it's current form, it could use a little polishing.
I tried Samuaz's MeDroid ICS 4.1 and it works way better. No market issues. Animations are much more fluid, camera works (panorama and video are broken). Gallery doesn't pull in picasa web albums (that'll be fixed today in 4.2). Also, you get CM features, which aren't present in TICS. I got a few force closes, but I think that was due to not rebooting after restoring from mybackup root, as I haven't had the FCs in a while. Oh, and USB mass storage is working, so I can restore apps and data from my backups. Sometimes the USB icon shows up or the app starts up (like at startup) when nothing is plugged in. Minor issue, though.
Upgrade method (some of these flash files aren't signed, so I needed to disable signature verification before they'd flash):
Upgrade bootloader (HBOOT) to 0.35.0017
Flash latest radio (5.12.00.08) - CHECK THE MD5 BEFORE FLASHING
Install Blackrose using the automatic method (It will not work without the HBOOT above)
Install custom blackrose from http://forum.xda-developers.com/showthread.php?t=1366897 - this increases the space available for ICS to install
Use recovery to do a full wipe three times (people had issues only wiping once)
Mount SD card via recovery and deleted/backed up everything.
Flash Evervolv-Perdo-2.1.0p4-passion.zip from http://forum.xda-developers.com/showthread.php?t=1366897
(Realize a bunch of things weren't working)
Use recovery to do a full wipe three times (people had issues only wiping once)
Flash MeDroid 4.1 from http://forum.xda-developers.com/showpost.php?p=21093710&postcount=188
To do yet:
Upgrade as soon as 4.2 comes out to fix gallery - I'll probably just use adb to replace the current gallery app - http://forum.xda-developers.com/showpost.php?p=21097768&postcount=191
Replace MeDroid's boot animation with this one http://forum.xda-developers.com/showthread.php?t=1429308
Am I the only one to be a little knee-shaking when it comes to flashing radios? I mean, ****ing up the system or boot seems easily restorable, but flashing a corrupted or unsigned radio may turn your device into a fully usable paperweight?
That's kinda the reason I've stayed with the 5.08.00.04 or what it's called. I mean, it works for me and hasn't bugged in any way, so why upgrade it?
I agree it's scary, but I saw so many people using the same file without issues, I was alright with it. Radios are the only file I check md5 on for this reason.
I think you're ok if fastbooting the img and like loki980 said, checking md5
I've done it a few times with no issues
Theshawty said:
That's kinda the reason I've stayed with the 5.08.00.04 or what it's called. I mean, it works for me and hasn't bugged in any way, so why upgrade it?
Click to expand...
Click to collapse
In all my time in the CyanogenMod forum (which is probably waaay too much time), it seems that the 5.08 is the best supported radio with the N1. I have never seen issues fixed from going from the 5.08 to the 5.12, but I have seen quite a few fixed doing the reverse. A lot of people get great results with 5.12, but it seems that more have better luck with 5.08.
Plus, I am sure that Google did a lot of testing before they sent out the Gingerbread update, and I'd bet there is a reason they included the 5.08 instead of the 5.12.

[Q] The Jelly Bean Upgrade Plan

Hey Guys,
Next Weekend (Friday December 20), I will finally make the jump to Jelly Bean from Gingerbread. I know that Kit Kat is also available, but it is much more buggy than Jelly Bean, and stability is my main goal, which is why I stayed on Gingerbread for so long. My plan for upgrading is this:
-Make a complete backup and snapshot of my device (Nandroid + Titanium Backup + Backup both Internal and External SD Cards to Computer) in case something goes wrong.
-Fully format both internal and external SD Cards (Including second Link2SD Partition in Ubuntu)
-Use AIO Toolkit to upgrade to New bootloader, and set up all new partitions, etc.
-Use AIO Toolkit to flash TWRP 2.6.0.0/ 2.6.3.0 For new bootloader (If it becomes available by the time I flash)
-Wipe Everything in Recovery
-Flash the latest TheROM 26 Stable (Most stable 4.3.1, with awesome extra features), + Kowalski Kernel M1 Stable, but I am keeping a close eye on the 3.1 developments (the 3.1 Hijuni port is too unstable for daily use currently, and Pengus mentions that Kowlaski features are being ported and code is being cleaned up for the Kowalski 3.1 release), so basically, I will make the kernel decision the day of the flashing operation.
-Flash Tonyp's full Non-Neon gapps from the development section
-Flash extra ROM Goodies, like feav's camera mod
-Reboot, let sit for a few minutes, and reboot again after first boot
-Begin setting up ROM/ Kernel and begin installing apps fresh from Google Play, and only restoring data from titanium backup for certain apps like games, etc.
Regarding the above, I have a few questions:
To begin, are the above steps proper? Is there anything that I should add or remove?
Secondly, when the 2.6.3.0 for New bootloader becomes available, it is as simple as flashing the new image through AIO Toolkit with no loss of data?
Lastly, does the Full non-neon gapps by Tonyp contain everything? Is there a better gapps to flash? I want the full Google apps experience, and the included mini-gapps does not contain everything I think.
I know this is a long post, but I really want to make sure I'm doing this right, and hopefully someone can use this thread in the future to do things proper also. Thanks in advance.
hi, I think the steps are correct. changing the bootloader will format the internal sd, but it doesn't matter if you format it before it. If tonyp makes a new twrp available you can flash it through the previous version of it, then you reboot recovery and it will be the updated version. not sure about the gapps question, but it surely contains play store, so you can install the latest version of the Google apps manually from it. good luck.
Sent from my LG-P990 using xda premium
Hello,
Thank you very much. I will continue to research and if I have any questions which I cannot find the answer to, I will ask here. Thanks again.
Sent from my Optimus 2X using xda app-developers app
Yeah. Your steps are fine.
The new 3.1 kernel is awesome. I am using it with TheROM build 25. You might wanna try it.
TonyP's GApps have most of the important Google Apps. It's sufficient, I think.
And, AFAIK, a new recovery doesn't need a data wipe of any kind.
Have fun Flashing and Upgrading!
Sent from my LG-P990 using Tapatalk
Thanks for your answer! I think I will stick with the KK M1 build, and maybe when the 3.1 kernel becomes a bit more stable I will flash it. It's not too big of a deal, because a kernel upgrade is just wiping dalvik and regular caches, installing, and setting up kernel settings, which is a lot less work than a ROM upgrade. I think I will stick with Tonyp's non-neon full gapps, and I'll upgrade the recovery to TWRP 2.6.3.0 newbl whenever it becomes available . Thanks again!
Sent from my Optimus 2X using xda app-developers app
Hello,
I have remebered a question I forgot to ask. Is Pdroid 2.0 supported in TheROM, and if it is, is it stable? Could I just use the auto patcher to add the functionality? Thanks again.
Sent from my Optimus 2X using xda app-developers app
Starting right now!
Hey Guys,
I'm starting the upgrade right now! I will post results after everything is done. I decided to use XPrivacy instead of the newer PDroids, because they contain bugs and are no longer developed. See you guys on the other side.
-lolcakes

[Q] Best stable ROM for HD+

Hi
Just received a Nook HD+ but after quickly browsing and playing for a while, I was not pleased with the stock rom, scrolls were not as smooth as I had seen on my nexus 4 for nexus 7 (maybe I am spoilt), I could notice some jitters and hope a custom ROM could fix this.
When I see in the Android development forum for this device, as usual the very many listing of the ROMs makes it difficult to identify which is the latest and the stable one (I suggest in future we should group the threads as - stable and non-stable which will help Noobs like me to jump into the act immediately).
Can somebody please advise me this bit of information as to which is the most latest custom rom that is stable, I am guessing it could the 10.1 build here [NookHD+] CM10.1 native emmc install Now part of CM Nightlies . Also to a step by step resource starting from rooting to the final flashing of the custom rom.
Also, is it possible to use 'Cyonogenmod installer' instead directly from their website!?
thanks
S
reply cm
Believe me I tried everything on nook.my initial thoughts were to run on SD card.but you have no official stable ROM for SD card .and the one available from bookbane was quite laggy .I tried both cm 11 and cm 10.2.then I installed on emmc again cm 11,cm 10.1 ,xperia ROM.but trust me the best experience I had so far was from cm10.2 on emmc .works beutiffully without any lag.
Just received a Nook HD+ but after quickly browsing and playing for a while, I was not pleased with the stock rom, scrolls were not as smooth as I had seen on my nexus 4 for nexus 7 (maybe I am spoilt), I could notice some jitters and hope a custom ROM could fix this.
When I see in the Android development forum for this device, as usual the very many listing of the ROMs makes it difficult to identify which is the latest and the stable one (I suggest in future we should group the threads as - stable and non-stable which will help Noobs like me to jump into the act immediately).
Can somebody please advise me this bit of information as to which is the most latest custom rom that is stable, I am guessing it could the 10.1 build here [NookHD+] CM10.1 native emmc install Now part of CM Nightlies . Also to a step by step resource starting from rooting to the final flashing of the custom rom.
Also, is it possible to use 'Cyonogenmod installer' instead directly from their website!?
thanks
S[/QUOTE]
dajmaa said:
Believe me I tried everything on nook.my initial thoughts were to run on SD card.but you have no official stable ROM for SD card .and the one available from bookbane was quite laggy .I tried both cm 11 and cm 10.2.then I installed on emmc again cm 11,cm 10.1 ,xperia ROM.but trust me the best experience I had so far was from cm10.2 on emmc .works beutiffully without any lag.
Just received a Nook HD+ but after quickly browsing and playing for a while, I was not pleased with the stock rom, scrolls were not as smooth as I had seen on my nexus 4 for nexus 7 (maybe I am spoilt), I could notice some jitters and hope a custom ROM could fix this.
When I see in the Android development forum for this device, as usual the very many listing of the ROMs makes it difficult to identify which is the latest and the stable one (I suggest in future we should group the threads as - stable and non-stable which will help Noobs like me to jump into the act immediately).
Can somebody please advise me this bit of information as to which is the most latest custom rom that is stable, I am guessing it could the 10.1 build here [NookHD+] CM10.1 native emmc install Now part of CM Nightlies . Also to a step by step resource starting from rooting to the final flashing of the custom rom.
Also, is it possible to use 'Cyonogenmod installer' instead directly from their website!?
thanks
S
Click to expand...
Click to collapse
[/QUOTE]
Could you please point me to the source please with instructions to the best experience ROM 10.2!? will this autoupdate to any other new updates from Cyanogenmod?
thanks
S
Could you please point me to the source please with instructions to the best experience ROM 10.2!? will this autoupdate to any other new updates from Cyanogenmod?
thanks
S[/QUOTE]Go to the dummies guide for installing CM10.1/CM10.2 linked in my signature.
Sent from my SCH-i705 using Tapatalk
CM11
Best choice for HD+ is CM11 EMMC from verygreen.
It's officially supported by Cyanogemod and gets nightly updates.
The ROM is smooth and efficient.
There may be tiny little bugs for the ROM, but they won't stop you from using your device as a daily driver.
3/27 is very stable btw.
CM 10.2.1. vs. CM 11
After reading some of the posts here, I decided to "downgrade" from CM 11 0327 to the last stable CM 10, 10.2.1. (Per dajmaa's suggestion.)
I'd never tried CM 10 before. When I got my HD+ a few weeks ago, I went from the Nook stock ROM direct to a CM11 SD install (0308) and then ended up at CD 11 0327 on emmc the other day.
While CM 11 was usable for me (except for one annoying problem, where I couldn't download mp3's), I see that CM 10 is much more finished. For example, it has zRam implemented. (But maybe KitKat doesn't need that, with it's ostensibly better memory management?) Trebuchet launcher works like it's supposed to in CM 10.2.1, although I liked the ability to enlarge the icons in CM 11. And the font in the status bar seemed bigger to my old eyes in CM 11 than CM 10.
Lagwise, they both seem the same. No lag, although I noticed that CM 10 gets "stuck" every now and then when I switch back and forth quickly between apps. And it keeps wanting to put "Extended Desktop" in the Power menu.
I haven't had it running long enough with my aviation moving maps to see if I get any random reboots like I did with CM 11.
As JimJ2Mz said, 0327 runs well. (Except that I couldn't download podcasts.)
But I'll plan to stay put now until there's some major announcement about CM 11, like a RC or something.
JimJ2Mz said:
Best choice for HD+ is CM11 EMMC from verygreen.
It's officially supported by Cyanogemod and gets nightly updates.
The ROM is smooth and efficient.
There may be tiny little bugs for the ROM, but they won't stop you from using your device as a daily driver.
3/27 is very stable btw.
Click to expand...
Click to collapse
Thanks Jim, I installed 10.2.x after trying out 10.1.3 for some time. I notice, GAPPS crashing randomly once in a while although not that too bad. Sometimes hangs for a while before it gets normal. So I guess there are still some bugs around. So was wondering 10.1.3 must be the one for me unless something stable comes up.
Now I see your post, and wondering why not I try it if there is going to be future updates. Do you feel it is smoother than the 10.1.x and 10.2.x as we all know KitKat is designed to run better on older hardware? If so I will proceed with CM11 and live minor bugs if that is not going to stand in the way of my daily usage like you mentioned.
sany said:
Thanks Jim, I installed 10.2.x after trying out 10.1.3 for some time. I notice, GAPPS crashing randomly once in a while although not that too bad. Sometimes hangs for a while before it gets normal. So I guess there are still some bugs around. So was wondering 10.1.3 must be the one for me unless something stable comes up.
Now I see your post, and wondering why not I try it if there is going to be future updates. Do you feel it is smoother than the 10.1.x and 10.2.x as we all know KitKat is designed to run better on older hardware? If so I will proceed with CM11 and live minor bugs if that is not going to stand in the way of my daily usage like you mentioned.
Click to expand...
Click to collapse
When you updated to CM10.2, did you also update to 20120813 gapps? That could be the reason for your gapps problems if you didn't.
And an HD+ is not 'older hardware'.
I recommend CM10.1.3 as the most stable.
Sent from my BN NookHD+ using XDA Premium HD app
sany said:
Thanks Jim, I installed 10.2.x after trying out 10.1.3 for some time. I notice, GAPPS crashing randomly once in a while although not that too bad. Sometimes hangs for a while before it gets normal. So I guess there are still some bugs around. So was wondering 10.1.3 must be the one for me unless something stable comes up.
Now I see your post, and wondering why not I try it if there is going to be future updates. Do you feel it is smoother than the 10.1.x and 10.2.x as we all know KitKat is designed to run better on older hardware? If so I will proceed with CM11 and live minor bugs if that is not going to stand in the way of my daily usage like you mentioned.
Click to expand...
Click to collapse
In my own experience, yes, CM11 feels much more fluid than the older versions.
4.4 RAM usage is optimized for older hardware, which actually benefits ALL devices, but that doesn't mean that the Nook HD/HD+ is old. It's modern and is still very powerful, just as leapinlar said. Well, not powerful, but not weak. Haha.
And as leapinlar also recommended, CM10.1.3 is indeed stable. Anyway. It's up to you. I've had my experiences with the ROMs and they can differ from others, so it's all up to you whether you want to try CM11 or stick to any other ROM.
JimJ2Mz said:
In my own experience, yes, CM11 feels much more fluid than the older versions.
4.4 RAM usage is optimized for older hardware, which actually benefits ALL devices, but that doesn't mean that the Nook HD/HD+ is old. It's modern and is still very powerful, just as leapinlar said. Well, not powerful, but not weak. Haha.
And as leapinlar also recommended, CM10.1.3 is indeed stable. Anyway. It's up to you. I've had my experiences with the ROMs and they can differ from others, so it's all up to you whether you want to try CM11 or stick to any other ROM.
Click to expand...
Click to collapse
I tried CM11 but it was throwing lots of google app erros on load, I was actually using the same GAPPS file that was on the 10.2.1, is there a used diferent GAPP file for CM11? maybe that caused the error. And also I struggled to go back to the CWM recovery for CM10.1 and 10.2 as it was just stuck at the recovery used for CM11 even after flashing the ver.3 recovery zip several times.
I have literally tried every single ROM out there and here are my recommendations:
1. Succulent's CM 11 (http://goo.im/devs/succulent/ovation/cyanogenmod/internal)
2. Official CM 10.2 Stable (I have been using it with drmarble's Kernel, which you can get here: https://app.box.com/s/ry03xsmhlxq2jomnwlaj)
Both ROMs are bug-free and run flawlessly. I get around 6 hours of screen-on time on both (which is an amazing battery life).
OH GEEZ
sany said:
I tried CM11 but it was throwing lots of google app erros on load, I was actually using the same GAPPS file that was on the 10.2.1, is there a used diferent GAPP file for CM11? maybe that caused the error. And also I struggled to go back to the CWM recovery for CM10.1 and 10.2 as it was just stuck at the recovery used for CM11 even after flashing the ver.3 recovery zip several times.
Click to expand...
Click to collapse
DUDE YOU HAVE TO USE GAPPS DEDICATED FOR CM11 (4.4)!
That's a given. You're having errors due to the fact that you're using 4.2 gapps on 4.4!
Follow this guide and FIX EVERYTHING. I followed it myself it everything works perfectly.
Please do ask if you need help on anything. I may be a noob, but I do know some stuff.
http://forum.xda-developers.com/showthread.php?t=2602796
Thanks Jim
JimJ2Mz said:
DUDE YOU HAVE TO USE GAPPS DEDICATED FOR CM11 (4.4)!
That's a given. You're having errors due to the fact that you're using 4.2 gapps on 4.4!
Follow this guide and FIX EVERYTHING. I followed it myself it everything works perfectly.
Please do ask if you need help on anything. I may be a noob, but I do know some stuff.
http://forum.xda-developers.com/showthread.php?t=2602796
Click to expand...
Click to collapse
Thanks Jim, I will do this. Why do you think I was unable to go back to CWN recovery for 10.1/10.2 - everytime after flashing the old recovery and go into the recovery mode, I still see the ver.6 (of CM11) in action.
S

[Q] Stock 2.3.6, ODIN, and Flashing CWM 6.0.5.0

Hello! First timer here to flashing and custom ROMing and have read as much as I possibly can but need some clarification before I proceed.
Background:
Let my family borrow my iPhone 4S while they travel so I'm using this SGH-T679. I have to stay in touch with them via Viber, Skype, and Hangouts (using GVPhone for Google Voice calls). After installing those apps the phone slowed down to a crawl and became a very frustrating experience;
the specs at this time were Android 2.3.5 and Baseband T679UVKJ1, stock and unrooted.
After reading that T-mobile released 2.3.6, I followed the upgrade instructions here;
now the specs are Android 2.3.6 and Baseband T679UVLK2, stock and unrooted.
For awhile I thought it was going well, but now I'm back to having frustrating experiences. It seems like memory management is terrible.
Desire:
I wonder if one of the KitKat roms will help alleviate some of the memory issues and better support the communication apps I need. Any advice? Or should I go with a custom Gingerbread or ICS ROM?
I'm leaning towards CyanogenMod 11 20140714-UNOFFICIAL by jfbs (however I also see a thread for CM11 by cars1189 but I can't figure out the difference, maybe question for a different thread).
[Q]:
I understand the first step is to install a Recovery. In the ROM thread the options are listed as:
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
So can I just transfer "Odin CWM 6.0.5.0" to root of device and install via powering on the phone and entering stock recovery by pressing & holding Power + Volume-Down?
When the phone was on 2.3.5, Power + Volume-Down and Power + Volume-Up (ODIN Download Mode from what I understand) yielded different modes. But now on 2.3.6, only Power + Volume-Down yields any kind of recovery option. That's why I'm wondering if installing CWM via stock recovery still holds for Android 2.3.6.
Appreciate you reading and thanks for your help!
ZHXS said:
Hello! First timer here to flashing and custom ROMing and have read as much as I possibly can but need some clarification before I proceed.
Background:
Let my family borrow my iPhone 4S while they travel so I'm using this SGH-T679. I have to stay in touch with them via Viber, Skype, and Hangouts (using GVPhone for Google Voice calls). After installing those apps the phone slowed down to a crawl and became a very frustrating experience;
the specs at this time were Android 2.3.5 and Baseband T679UVKJ1, stock and unrooted.
After reading that T-mobile released 2.3.6, I followed the upgrade instructions here;
now the specs are Android 2.3.6 and Baseband T679UVLK2, stock and unrooted.
For awhile I thought it was going well, but now I'm back to having frustrating experiences. It seems like memory management is terrible.
Desire:
I wonder if one of the KitKat roms will help alleviate some of the memory issues and better support the communication apps I need. Any advice? Or should I go with a custom Gingerbread or ICS ROM?
I'm leaning towards CyanogenMod 11 20140714-UNOFFICIAL by jfbs (however I also see a thread for CM11 by cars1189 but I can't figure out the difference, maybe question for a different thread).
[Q]:
I understand the first step is to install a Recovery. In the ROM thread the options are listed as:
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
So can I just transfer "Odin CWM 6.0.5.0" to root of device and install via powering on the phone and entering stock recovery by pressing & holding Power + Volume-Down?
When the phone was on 2.3.5, Power + Volume-Down and Power + Volume-Up (ODIN Download Mode from what I understand) yielded different modes. But now on 2.3.6, only Power + Volume-Down yields any kind of recovery option. That's why I'm wondering if installing CWM via stock recovery still holds for Android 2.3.6.
Appreciate you reading and thanks for your help!
Click to expand...
Click to collapse
install cwm via odin, Jfbs posted link for odin pc app that is needed to do it in one of his rom ops i believe in the same op as the rom your are pondering on upgrading to. either way you need the odin files and usb drivers. as far as a rom with better memory and faster performance well any kk rom will do that or for older roms cars1189 CM Mass OP as cm10 and 10.1. reason being the new hybrid ion/pmem. compared to the old stock pmem based. now if you want battery battery life and even faster performance use a oc kernel and use an app like performance control to change the voltage and cpu frequency settings to your liking you can check my op in gen section for our phones for more details and guide for it.
EDIT yes the files are in the that rom op you mentioned 3 post down xD
I'm not a dev but from my experience with Viber, I have learned that this app uses a lot of memory. I have stopped using it for awhile cuz it was using over 30mb of my ram. So the best advice I have for you is not to install apps that you won't use often. Just use the strict minimum. For the memory management I also use Greenify to put asleep any app I'm not using often. This app in my case doesn't use over 5mb of ram but saves me over 50mb of memory when needed. But just be wise when selecting which apps to put asleep. I also use NovaLauncher as it is faster then any other I've tried and it's not hard on memory cache. Also other adive like @TripFX said, any KitKat rom can help you with memory management and performance. Me i use the lastest build of CM11 by @cars1189 with the Christopher oc kernel.
---------- Post added at 10:59 PM ---------- Previous post was at 10:47 PM ----------
theking1st said:
I'm not a dev but from my experience with Viber, I have learned that this app uses a lot of memory. I have stopped using it for awhile cuz it was using over 30mb of my ram. So the best advice I have for you is not to install apps that you won't use often. Just use the strict minimum. For the memory management I also use Greenify to put asleep any app I'm not using often. This app in my case doesn't use over 5mb of ram but saves me over 50mb of memory when needed. But just be wise when selecting which apps to put asleep. I also use NovaLauncher as it is faster then any other I've tried and it's not hard on memory cache. Also other adive like @TripFX said, any KitKat rom can help you with memory management and performance. Me i use the lastest build of CM11 by @cars1189 with the Christopher oc kernel.
Click to expand...
Click to collapse
Another advice also is to avoid modding too much your user interface cause for a phone like this it will make it slower, from my experience. Hope I could help! . (All these suggestions are from experiences i had and that helped me better manage my phone performances.) ?
TripFX said:
install cwm via odin, Jfbs posted link for odin pc app that is needed to do it in one of his rom ops i believe in the same op as the rom your are pondering on upgrading to. either way you need the odin files and usb drivers. as far as a rom with better memory and faster performance well any kk rom will do that or for older roms cars1189 CM Mass OP as cm10 and 10.1. reason being the new hybrid ion/pmem. compared to the old stock pmem based. now if you want battery battery life and even faster performance use a oc kernel and use an app like performance control to change the voltage and cpu frequency settings to your liking you can check my op in gen section for our phones for more details and guide for it.
EDIT yes the files are in the that rom op you mentioned 3 post down xD
Click to expand...
Click to collapse
Hey! So I wanted to post an update about my experience...
After realizing the reference to Odin is actually a PC application, I decided to just install via Samsung Recovery.
Unfortunately from Power Off, pressing the Power + Volume Up buttons did not start recovery.
I had to use the method from the XDA Exhibit Wiki:
Pull the battery from your phone.
Connect phone to your pc via usb.
Press & hold Volume-up
Insert battery
Click to expand...
Click to collapse
It's weird because on stock 2.3.5 I was able to start recovery from Power Off, but after OTA 2.3.6 baseband T679UVLK2 it no longer works. I wonder if flashing baseband T679UVLG3 or flash2stock will get back that ability. Anyway, I might try that later, right now it's setup with what I need.
I flashed CM11 by jfbs and it's working quite smoothly. Even when free memory drops below 100MB it works well. Amazing what a ROM change can do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read your OC and UV to perfection safely and easy guide !!! and I'm definitely bookmarking it for future exploration. Sometimes the battery gets so warm that I'm more comfortable leaving it in stock settings for now.
theking1st said:
I'm not a dev but from my experience with Viber, I have learned that this app uses a lot of memory. I have stopped using it for awhile cuz it was using over 30mb of my ram. So the best advice I have for you is not to install apps that you won't use often. Just use the strict minimum. For the memory management I also use Greenify to put asleep any app I'm not using often. This app in my case doesn't use over 5mb of ram but saves me over 50mb of memory when needed. But just be wise when selecting which apps to put asleep. I also use NovaLauncher as it is faster then any other I've tried and it's not hard on memory cache. Also other adive like @TripFX said, any KitKat rom can help you with memory management and performance. Me i use the lastest build of CM11 by @cars1189 with the Christopher oc kernel.
---------- Post added at 10:59 PM ---------- Previous post was at 10:47 PM ----------
Another advice also is to avoid modding too much your user interface cause for a phone like this it will make it slower, from my experience. Hope I could help! . (All these suggestions are from experiences i had and that helped me better manage my phone performances.) ?
Click to expand...
Click to collapse
Appreciate your tips. You're right about Viber and communication apps, they're all using between 20-30MB each, but I need them so I'm leaving them on for now.
I'll definitely have to check out Greenify.
Also appreciate your tip about NovaLauncher, as I witnessed a few niggling issues with Trebuchet Launcher upon initial boot up after flashing the ROM.
I've limited my UI customization based upon your advice, I just have one page for apps and Google Now page to the left (I initially installed BaNkS GApps Minimal 4.4.4 but then flashed on top GApps Minimal GoogleSearch and AOSP Calendar Sync Addonas I was missing typing by voice and calendar events).
Do you know if there is a post/thread where I can find out the difference between kernels available for this phone?
I see for CM11 by cars1189 that there is ADC/Linaro Kernel and Christopher K^Kernel, but I can't find a comparison between the two.
Thinking of Future: Is it ok to dirty flash CM11 by cars1189 over CM11 by jfbs, or is formatting everything recommended?
Thanks for the replies fellas!
as far as basebands go that jfbs posted. either will work and there really isn't i a difference between the 2 and flashing either one should cause any harm to you phone that i'm aware of as i have personally tried both on same phone.
personally i never dirty flash but thats just my preference. however dirty flashing cross rom authors i would definitely do a clean install even devs would agree with that.
as far as warm battery you could undervolt it without overclocking to reduce the temp more so then how much temp increase you get from upping the frequency. So no matter what i would find my cpu's lowest stable voltage as it will give you longer battery life and lower temps. as long as your stable voltage is under 1.200mhv however i haven't heard anyone not be able to use 1.100mhv at stock frequency. how ever i would still start from stock voltage 1.2mhv and lower by 0.025mhv (1.175) test it out for a bit open and close and so forth. then lower it again by same about. and do so for each frequency below what set max frequency for.
TripFX said:
as far as basebands go that jfbs posted. either will work and there really isn't i a difference between the 2 and flashing either one should cause any harm to you phone that i'm aware of as i have personally tried both on same phone.
personally i never dirty flash but thats just my preference. however dirty flashing cross rom authors i would definitely do a clean install even devs would agree with that.
as far as warm battery you could undervolt it without overclocking to reduce the temp more so then how much temp increase you get from upping the frequency. So no matter what i would find my cpu's lowest stable voltage as it will give you longer battery life and lower temps. as long as your stable voltage is under 1.200mhv however i haven't heard anyone not be able to use 1.100mhv at stock frequency. how ever i would still start from stock voltage 1.2mhv and lower by 0.025mhv (1.175) test it out for a bit open and close and so forth. then lower it again by same about. and do so for each frequency below what set max frequency for.
Click to expand...
Click to collapse
Ok, Clean Install it is.
As far as App + App Data Backup & Restore is concerned when flashing a new ROM, I have read about a variety of methods.
Method 1:
eushaun99 said:
You have to wipe system, cache and dalvik first then reflash your ROM and gapps.
Click to expand...
Click to collapse
Meaning, no need to Wipe Data. So all of your Downloaded Apps + Data will still be on the phone after flashing new ROM.
Method 2:
Wipe Everything.
Flash New ROM and Gapps.
Advanced Restore of Data and Cache Partitions via Recovery.
Method 3:
Wipe Everything.
Flash New ROM and Gapps.
Restore Apps + Data via program like Titanium Backup, ES File Explorer, etc.
I like the idea of Method 1, but I think you recommend Method 3?
What is your current ROM + Kernel setup if you don't mind me asking?
I think I may undervolt using the same settings from your OC and UV Guide. I figure it's the same phone, processor, etc.
ZHXS said:
Ok, Clean Install it is.
As far as App + App Data Backup & Restore is concerned when flashing a new ROM, I have read about a variety of methods.
Method 1:
Meaning, no need to Wipe Data. So all of your Downloaded Apps + Data will still be on the phone after flashing new ROM.
Method 2:
Wipe Everything.
Flash New ROM and Gapps.
Advanced Restore of Data and Cache Partitions via Recovery.
Method 3:
Wipe Everything.
Flash New ROM and Gapps.
Restore Apps + Data via program like Titanium Backup, ES File Explorer, etc.
I like the idea of Method 1, but I think you recommend Method 3?
What is your current ROM + Kernel setup if you don't mind me asking?
I think I may undervolt using the same settings from your OC and UV Guide. I figure it's the same phone, processor, etc.
Click to expand...
Click to collapse
I've had an issue in the past (Being builds of cm11) doing that but not during aoip days and had gapp issues. regardless of the 3 methods. as far as backing and restoring user apps+data. use es file explorer to copy apks to either sdcard. then connect phone to pc and make a new folder on desktop then copy all the apks and data to that folder. then after doing complete clean install and setting up the phone the way like it ( mods, advance settings, oc, uv, etc. then copy back over to sdcard then move the apks back to the original directory you pulled it from. However im just super cautious as it could have just be a fluke bug in cm11 that may have already been fixed. but as far as back up it which ever works best for you.
private testing mahdi build with rom. still using the settings that are in oc/uc guide. as far as kernels my phone does much better with jfbs stock rom kernels as they already have oc/uc support by default and has a much high user ram space that is stable. jfbs roms i think are for the more advance users that like to tweak everything where cars1198 is better for the everyday user. Hence why i use jfbs roms and wife uses cars1198 roms.
TripFX said:
private testing mahdi build with rom. still using the settings that are in oc/uc guide. as far as kernels my phone does much better with jfbs stock rom kernels as they already have oc/uc support by default and has a much high user ram space that is stable. jfbs roms i think are for the more advance users that like to tweak everything where cars1198 is better for the everyday user. Hence why i use jfbs roms and wife uses cars1198 roms.
Click to expand...
Click to collapse
Thanks for all the great info you've been providing!
Which Kernel is she using with cars1198's CM11? ADC/Linaro Kernel, Christopher K^Kernel, jfbs?
Judging from the last few pages of jfbs' CM11 OP, it doesn't appear he will update any longer
ZHXS said:
Thanks for all the great info you've been providing!
Which Kernel is she using with cars1198's CM11? ADC/Linaro Kernel, Christopher K^Kernel, jfbs?
Judging from the last few pages of jfbs' CM11 OP, it doesn't appear he will update any longer
Click to expand...
Click to collapse
K^Kernel hm and as far as jfbs it's hit and miss as far as newer roms and so forth go. Im not in a rush as he has done more than enough for our device and for free along with helping lots of users including but not limited to rude users. So expect him to do what he think is best and if someone doesn't like it they can just deal with it. I'm happy with the phone even as is. I mean this phone is uberly outdated hardware wise and has been really stressed to it limits even beyond anything rom before kitkat roms came out. However that's not to mention it prolly wouldn't have been possible without arco86, adc team, and others. So when/if he does i'm grateful for what he gives us. same for cars1198 and other devs on this site. Not saying anything bad about you but just giving a short version of where things are at.
FYI most people here on xda just prefer you either clicking the thanks button if you the post was useful or if it a bug related then logcats and brief description of the problem and wait patiently for someone who knows to either A) if dev - fixes it or asks for more info. B) if other user- tries to help you out if possible. Also as always even it something isn't to your liking the it would be wiser and nicer to post something like "Hey I really don't like X if you don't mind can you do X. If you are to busy or like X the way it is, that is fine and thank you for helping the community and good luck on you project."
TripFX said:
K^Kernel hm and as far as jfbs it's hit and miss as far as newer roms and so forth go. Im not in a rush as he has done more than enough for our device and for free along with helping lots of users including but not limited to rude users. So expect him to do what he think is best and if someone doesn't like it they can just deal with it. I'm happy with the phone even as is. I mean this phone is uberly outdated hardware wise and has been really stressed to it limits even beyond anything rom before kitkat roms came out. However that's not to mention it prolly wouldn't have been possible without arco86, adc team, and others. So when/if he does i'm grateful for what he gives us. same for cars1198 and other devs on this site. Not saying anything bad about you but just giving a short version of where things are at.
Click to expand...
Click to collapse
Totally agree with you on all points. I'm very happy with the current state - I'm not planning to move to another ROM anytime soon. The way I see it, most of the monthly updates appear to be incremental changes, and not something that will radically alter the core functionality of the phone.
It's amazing development still happening for this 3 year old device.
Alright! Looks like @ZHXS you've found all the answers you needed.
I'm using the latest CM11 build by @cars1189. I don't remember what the difference between both kernels in cars' thread is, but I definitely know that the Christopher kernel is for OC and UV because it is the kernel i'm using right now. I will check it out again and come back at you when I find out.
For flashing one ROM over the other one I have done it many times (I don't know if it is fine or not but from the replies I think that it's not recommended) but i didn't encounter any trouble. Just but sure to nandroid before you flash on top. Also if it is an update of the same ROM you are running, it shouldn't cause any trouble in the future. The only thing is that if you had Xposed framework activated before the update, after the update you will have to reactivate it again because with an update of the ROM, Xposed framework gets deactivated. Also I would recommend a nandroid before the update just in case. :good:
Also for the launcher, I have just found out that the home launcher of the Z3 has been ported and I tried it out. And I got to say, it is definitely faster than NovaLauncher in my phone. It takes less more time to go back when I press the home button from anywhere I'm in the phone. It doesn't have too much tweaks and personalisation like NovaLauncher, but hey with this phone the simpler the faster. The only down side with this launcher is that there is an empty spot under the dock that creates a waste of screen space. Here is one of my screenshot:
Click to expand...
Click to collapse
The thread author said that he(she, I don't know) is working on it so we might see a fix for it. But if you want to check it out, here it is: http://forum.xda-developers.com/crossdevice-dev/sony/port-xperia-z3-home-7-0-0-14-t2868655
That's all I had to say, happy to help you if you have any other question that I can answer.
I tested both kernels and it turns out that the ADC kernel looks like just a regular kernel. I had to do the flashing of the kernels on the 7-7-14 build because the ADC kernel was not available for the 8-28-14 build, and for the replies in the thread, the kernels for the 7-7-14 build and previous builds are not compatible with the 8-28-14 build. But I flashed it on the 7-7-14 build it did not show me any OC or UV settings and options. But I think that there is something else about this kernel that I don't know the presence of. But the Christopher kernel showed me OC and UV options so this kernel is definitely for OC and UV. There are also different versions of the Christopher kernel so you can check them out if you want.
And also the Xperia Z3 launcher port has been updated! The empty space under the dock has been removed. Looks like this now.
Click to expand...
Click to collapse
If you want to check it out make sure to download the Home-superuser-nonav.apk . It's done by @Sahaab (just wanted to s/o him)
theking1st said:
I tested both kernels and it turns out that the ADC kernel looks like just a regular kernel. I had to do the flashing of the kernels on the 7-7-14 build because the ADC kernel was not available for the 8-28-14 build, and for the replies in the thread, the kernels for the 7-7-14 build and previous builds are not compatible with the 8-28-14 build. But I flashed it on the 7-7-14 build it did not show me any OC or UV settings and options. But I think that there is something else about this kernel that I don't know the presence of. But the Christopher kernel showed me OC and UV options so this kernel is definitely for OC and UV. There are also different versions of the Christopher kernel so you can check them out if you want.
Click to expand...
Click to collapse
Wow @theking1st, going above & beyond testing the kernels! Thanks for the info man.
I'm kind of eager to OC now since after adding Google Search it's a bit slower again. I think I'll do that tonight, start fresh.:good:
ZHXS said:
Wow @theking1st, going above & beyond testing the kernels! Thanks for the info man.
I'm kind of eager to OC now since after adding Google Search it's a bit slower again. I think I'll do that tonight, start fresh.:good:
Click to expand...
Click to collapse
besides the oc and uc there they both use different optimizations and default kernel tweaks. Personally i like having the oc and uv option. you can make it run faster then stock while having lower temps and longer battery life as well as faster charging wile the phone is actually on. Powered off its the same no matter what ya do as far as how fast it charges. also if your fine with the speed i;d still recommend undervolting as you can run at stable at lower mv then stock. How low you can goes varies from person to person but in general im sure you can run 1.2GHZ @ 1.150mv compared to stock 1ghz @ 1.200mv. if ya can go lower stable then kudos for getting a lucky kudos for getting a decent made chip. follow my oc/uv guide in the gen section if your new to it and you will be just fine and safely.

[Q] Need general advise for S5830

I kind of messed up a bit with my Galaxy Ace S5830, so I'm about to wipe it again. But after thinking about it, I was wondering if there's a bit more that can be done for this legacy device aside of installing CM.
I first had CM 7.2.0 stable installed and overall it went fairly well for daily use, except for just a couple of issues: default camera not having zooming function, and this other issue:
http://forum.xda-developers.com/showthread.php?t=2596926
On IRC (cyanogenmod channel) I was told this probably could be due to Ace's awfully limited amount of RAM, which caused the updating app to not be able to temporarily store in RAM and use some of internal sotrage (limited as well), resulting in more and more internal storage consumed each time an update was performed. Or so I understood...
Also I noticed there are a few nightlies after stable CM version 7.2.0
http://download.cyanogenmod.org/?device=cooper
So, questions would be:
1. If I'm to install CM7, which one should I pick, stable 7.2.0 again, or latest nightly? I think I once read comments that latest build fixed some minor bugs and was actualyl good, but I do care a lot about stability and the Wikia site says nightlies are unstable.
2. Is there something I could do for the updates/storage issue?
3. Is there default zoom for camera on CM7, or would I have to download another camera app?
4. I've seen there are now some CM 9, 10, 11, etc builds for S5830, but they are unofficial and in the IRC I was told unofficial was generally not that good (and potential malware). Should I better stick with CM7, or is there by chance an "official" CM 9, 10, 11 mod?
Thanks beforehand.
ctcx said:
I kind of messed up a bit with my Galaxy Ace S5830, so I'm about to wipe it again. But after thinking about it, I was wondering if there's a bit more that can be done for this legacy device aside of installing CM.
I first had CM 7.2.0 stable installed and overall it went fairly well for daily use, except for just a couple of issues: default camera not having zooming function, and this other issue:
http://forum.xda-developers.com/showthread.php?t=2596926
On IRC (cyanogenmod channel) I was told this probably could be due to Ace's awfully limited amount of RAM, which caused the updating app to not be able to temporarily store in RAM and use some of internal sotrage (limited as well), resulting in more and more internal storage consumed each time an update was performed. Or so I understood...
Also I noticed there are a few nightlies after stable CM version 7.2.0
http://download.cyanogenmod.org/?device=cooper
So, questions would be:
1. If I'm to install CM7, which one should I pick, stable 7.2.0 again, or latest nightly? I think I once read comments that latest build fixed some minor bugs and was actualyl good, but I do care a lot about stability and the Wikia site says nightlies are unstable.
2. Is there something I could do for the updates/storage issue?
3. Is there default zoom for camera on CM7, or would I have to download another camera app?
4. I've seen there are now some CM 9, 10, 11, etc builds for S5830, but they are unofficial and in the IRC I was told unofficial was generally not that good (and potential malware). Should I better stick with CM7, or is there by chance an "official" CM 9, 10, 11 mod?
Thanks beforehand.
Click to expand...
Click to collapse
1. Flash your desired version... there'is a lot of rom in Android Development section... Nightly doesn't mean unstable :silly:
2. Storage issue?... AFAiK CM7.x/9.x/10.x/11 haven't got any storage issue...
3. Our camera hasn't optical ZOOM... digital zoom is as if you enlarge a picture when you're seeing it in the gallery... anyway you can't do digital zoom using any CM camera.
4. Unofficial doesn't mean that the file contains potential malware...
Thanks mr Viper.
There's quite a lot of stuff in the Android Development section, maybe too much for me to process...
Although, from what I managed to see, @Mardon's roms -specially his CM11 rom- would rise my hopes high, if his roms weren't in alpha/beta stages and he could work on them more often.
However there's another rom that looks promising to flash right now, @Rhievaldo's CM9. From what I read in its thread, it looks functional enough for daily use. It's a shame that seemingly he's put its development on hiatus; would be great if those remaining issues could be fixed (compass, weather in lockscreen, etc).
@Viper The Ripper, in your experience, would you advise for 1 or 2 CM roms for S5830 in particular?
Also, do I need stock rom before flashing a CM rom, or can I just wipe data, cache, system? Do all CM roms come pre-rooted, or do I need to root beforehand?
Thanks again.
P.S.: regarding the "storage issue", I did leave a link to a previous thread started by me to explain what I meant, if you see it...
?????????????????
ctcx said:
I kind of messed up a bit with my Galaxy Ace S5830, so I'm about to wipe it again. But after thinking about it, I was wondering if there's a bit more that can be done for this legacy device aside of installing CM.
I first had CM 7.2.0 stable installed and overall it went fairly well for daily use, except for just a couple of issues: default camera not having zooming function, and this other issue:
http://forum.xda-developers.com/showthread.php?t=2596926
On IRC (cyanogenmod channel) I was told this probably could be due to Ace's awfully limited amount of RAM, which caused the updating app to not be able to temporarily store in RAM and use some of internal sotrage (limited as well), resulting in more and more internal storage consumed each time an update was performed. Or so I understood...
Also I noticed there are a few nightlies after stable CM version 7.2.0
http://download.cyanogenmod.org/?device=cooper
So, questions would be:
1. If I'm to install CM7, which one should I pick, stable 7.2.0 again, or latest nightly? I think I once read comments that latest build fixed some minor bugs and was actualyl good, but I do care a lot about stability and the Wikia site says nightlies are unstable.
2. Is there something I could do for the updates/storage issue?
3. Is there default zoom for camera on CM7, or would I have to download another camera app?
4. I've seen there are now some CM 9, 10, 11, etc builds for S5830, but they are unofficial and in the IRC I was told unofficial was generally not that good (and potential malware). Should I better stick with CM7, or is there by chance an "official" CM 9, 10, 11 mod?
Thanks beforehand.
Click to expand...
Click to collapse
Hi There,
Well Stable would be my preference for daily use.
Hit Thanks if Helped

Categories

Resources