CM11 degradation? - Nook HD, HD+ General

I really don't want to come across as if I don't appreciate the work that is going into the CM11 / KitKat builds for the Nook HD because I do and continually look forward to flashing the latest nightlies etc.
But does it seem as if each version from either variant available are less and less stable? initial releases seemed fine while each new version has more and more issues that seem to pop up. I just flashed the latest from the General forum here and lost Play store, once I reflashed my GAPPS and got it back I got odd green screen flashing and terrible performance requiring a reboot which black screened. I had to do a soft reset by holding the power button.
I don't know. Again, appreciate the work, saddened by the current crop, I guess.

And here I am wondering why I don't have any issues at all. Not one single reboot, no loss of functionality, nothing. I am running the latest nightly.
Sent from my BN NookHD+ using Tapatalk 4

asawi said:
And here I am wondering why I don't have any issues at all. Not one single reboot, no loss of functionality, nothing. I am running the latest nightly.
Sent from my BN NookHD+ using Tapatalk 4
Click to expand...
Click to collapse
02-03?
Did you swap kernels? Dirty flash? Etc.
Sent from my HTC One using Tapatalk

Did you try factory restore after your google app install?
If not i try doing the restore in settings and see if it resolves the problems. Seems like it usually works for me.

If you notice the launcher is now trebuchet. They just started replacing launcher 3 with theirs. So things will be broken or missing. Same with others areas.
I always have a very recent backup and so it doesn't matter. 10.2 went though pains too and so on so forth.
If you want more stable 10.2 is right there. Backup cm11 in recovery and restore it later on when its more mature.

So...am I the only one who....
Doesn't use Google anymore? Look, I mean I know the paid Koogle-aid dispensers will dog pile on me as a heretic, but CM on my nook is working great for me and in concert with other play stores all is well. I just don't see the need to put anymore money or information in Big GData's pocket.
Just one guys opinion, flame away

50bux said:
Doesn't use Google anymore? Look, I mean I know the paid Koogle-aid dispensers will dog pile on me as a heretic, but CM on my nook is working great for me and in concert with other play stores all is well. I just don't see the need to put anymore money or information in Big GData's pocket.
Just one guys opinion, flame away
Click to expand...
Click to collapse
This is rich. It used to be big M$ that folks dumped on, now Google?
Sent from my BN NookHD+ using XDA Premium HD app

Rich?
I respectfully disagree. LL you of all people know of the massive holes and security flaws that gapps add to what is mostly a great open source system. I think if people really were to examine just what adding gapps does to your phone as far as adding in avenues for exploitation they wouldn't use it.
Have I said something technically incorrect?

50bux said:
I respectfully disagree. LL you of all people know of the massive holes and security flaws that gapps add to what is mostly a great open source system. I think if people really were to examine just what adding gapps does to your phone as far as adding in avenues for exploitation they wouldn't use it.
Have I said something technically incorrect?
Click to expand...
Click to collapse
I'm not disagreeing with your point, I just think it is interesting that folks tend to see big companies as evil and jump on them.
Sent from my BN NookHD+ using XDA Premium HD app

All running smooth as a babys bottom
Sent from my HTC One using Tapatalk

felacio said:
02-03?
Did you swap kernels? Dirty flash? Etc.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes, 02-03. I don't swap any kernels. Clean initial install and then updated from settings menu. And as I said, no issues whatsoever! Working woonderfully, no reboots, no lag, nothing! Just working beautifully!
The only issues I've had with CM11 was in the initial unofficial release there was a screen flicker now and then. That dispappeard a coulpe of releases in. And then last week (?) there was an issue with the screen rotating when putting the device to sleep. That did't have any effect on the device while running, but either way it's fixed now.
And as I said, not one single unwanted reboot! Ever! I have a 16GB HD+ and a 16GB HD running unmodified nightlies. Both of then problem free! I'm (of course) not complaining, just wondering how come some have lots of problems and others don't. Hardware related? Dirty installs? Messed around with stuff best left alone?

asawi said:
Hardware related?
Click to expand...
Click to collapse
That's been my theory since I got my first Android device. More specifically, hardware revisions.

I have done it in the past just to see if android would still be useable if Google stopped supporting it. It is but it is easier with them. More security would be nice.
Sent from my PG86100 using xda app-developers app

felacio said:
I really don't want to come across as if I don't appreciate the work that is going into the CM11 / KitKat builds for the Nook HD because I do and continually look forward to flashing the latest nightlies etc.
But does it seem as if each version from either variant available are less and less stable? initial releases seemed fine while each new version has more and more issues that seem to pop up. I just flashed the latest from the General forum here and lost Play store, once I reflashed my GAPPS and got it back I got odd green screen flashing and terrible performance requiring a reboot which black screened. I had to do a soft reset by holding the power button.
I don't know. Again, appreciate the work, saddened by the current crop, I guess.
Click to expand...
Click to collapse
I understand what you mean. Seriously if I knew enough about caf and kernels, etc. I would find a way to build some form of 4.4.2 pure AOSP. Stock just seems so much better with my N5 and I would love to see it in action on my Nook HD+. But I don't know that much and am too busy to start learning complicated things like that (I own a business and root&mod as a limited hobby). I'm just grateful to @verygreen & helpful folks like @leapinlar to have some kind of 4.4 emmc on this mostly abandoned (by B&N) device. I think that CM in general has gone downhill from a stability perspective since CM10 (basing that on a few devices that got 'official' cm).

Well, did a full wipe and flashed the latest 02-04 build. So far so good. No horrible performance after an hour requiring a reset and it hasn't gone black on me, but that usually takes a couple days. I should have learned long ago to just do a full wipe and flash when things aren't going right.

felacio said:
Well, did a full wipe and flashed the latest 02-04 build. So far so good. No horrible performance after an hour requiring a reset and it hasn't gone black on me, but that usually takes a couple days. I should have learned long ago to just do a full wipe and flash when things aren't going right.
Click to expand...
Click to collapse
Just for my future reference , what is meant by full wipe? I did a wipe data and factory reset before and went through the setup screens again but there was clearly still some stuff left, like data folders from apps previously installed.
Thanks

barth2 said:
Just for my future reference , what is meant by full wipe? I did a wipe data and factory reset before and went through the setup screens again but there was clearly still some stuff left, like data folders from apps previously installed.
Thanks
Click to expand...
Click to collapse
To get rid of personal data you have to format data under mounts. Word of warning anything not backed up will be gone.
Sent from my PG86100 using xda app-developers app

barth2 said:
Just for my future reference , what is meant by full wipe? I did a wipe data and factory reset before and went through the setup screens again but there was clearly still some stuff left, like data folders from apps previously installed.
Thanks
Click to expand...
Click to collapse
A wipe data /factory reset with CWM is not really a full wipe. It leaves your media files intact. Even a format of /data in 'mounts and storage' leaves the media files. To do a full wipe you need to format 'data and datamedia'. That truly wipes all data, including media files.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
A wipe data /factory reset with CWM is not really a full wipe. It leaves your media files intact. Even a format of /data in 'mounts and storage' leaves the media files. To do a full wipe you need to format 'data and datamedia'. That truly wipes all data, including media files.
Click to expand...
Click to collapse
While we're at it, what's a dirty flash / re flash, and how does one change kernels in a nook device? I thought kernels were always included in a rom zip as boot.img files and you could not flash a different one

Nolfer said:
While we're at it, what's a dirty flash / re flash, and how does one change kernels in a nook device? I thought kernels were always included in a rom zip as boot.img files and you could not flash a different one
Click to expand...
Click to collapse
A dirty flash is just installing a new Rom without wiping anything first. Depends on what you are flashing whether a dirty flash is OK. Usually if you are going from one CM nightly to another say CM 10.2 from yesterday to CM 10.2 from today you can get away without wiping caches. If on the other hand you want to go from CM 10.2 to Cm 11 you really should wipe caches first, same going from say CM to Carbon it is recommended to wipe first.
There are a few kernels out there but they are specific to certain Roms. There were some touch kernels for CM 10.2 but they only work on early releases not the stable. Unless you have a specific need I would't worry about flashing a new kernel.

Related

[Q] Does your Kindle Fire become unresponsive much?

So I tend to answer more questions that I ask on here, but now it's my turn!!
So, I've noticed at times that my KF is totally unresponsive from sleep. No power light, nothing. I have to press the power button for 20 seconds, then again to power on. This used to happen every so often on the Stock ROM.
However, since I've been on CM7 w/ TWRP/FFF, it hangs up every single day. At first I thought it was due to low charge, but it's doing it whilst the battery is over 90% full. I've had a nose around the CM7 settings and tweaks, but can't see anything obvious.
Running services at startup are:
Settings (presumably because I'm looking at settings to see this info!)
Google Services
Amazon Video (Not sure why this is running. I may uninstall to see if this is the problem) - Uninstalled. Will see how it goes.
DSPManager
Swype
Anybody else seen this? Anybody else got any ideas on how to resolve this?
Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk
I've not experienced this problem. My kindle fire has been pretty much perfect and I've never had to force a reboot. I'm also using the Sywpe keyboard.
asb2164 said:
Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.
sl0ttedpig said:
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.
Click to expand...
Click to collapse
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk
asb2164 said:
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Wow, seriously?!
I *did* read about it, and concluded that it was a memory management app. Given my symptoms, I cannot find one example of where this app would help me, and I'm not about to install something that is possibly just going to add further variables to an already odd behavior.
Show me where you think it's going to help (specific examples), and I'll gladly accept your thanks/suggestions.
Until then, I would ask you keep your snark for sites like Slashdot.
You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk
asb2164 said:
You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Again, Wow Seriously?!
Your definition of me not reading is based on me calling it an app over a script!? Interesting logic there.
However, I'm still wondering how you deduce that this is going to help my problem, and hence why I asked for specifics. I'm quite capable of finding information, but it's like you saying to me "Dude, install Angry Birds, it will solve all your problems". My conclusion was that there was nothing in that post that specifies "This will also help your system if it sleeps permanently" (clearly I'm paraphrasing there, just in case that wasn't clear). If I'm missing something, I'm all ears, but blindly recommending apps for no reason is no help to anyone.
Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.
asb2164 said:
Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.
Click to expand...
Click to collapse
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.
You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.
asb2164 said:
You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.
Click to expand...
Click to collapse
I guess it's entirely possible. I'll do a Titanium Backup now, re-flash, and see what happens. But as mentioned in my OP, I had this happen on stock 6.2, just not as frequently, so I'll be hoping that it is a bad flash, and not something inherently worse.
See how much better this conversation is now!
Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly
Your problem is a bit unique so I don't mind throwing out a few ideas.
Mine is solid as a rock I am ready for a good overclocking kernel so I can stretch it's legs
Sent from my Kindle Fire using Tapatalk
altitude909 said:
Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly
Click to expand...
Click to collapse
Yep, I always clear everything when moving to a new ROM. It's a habit that was drilled into me during my first custom ROM exploits on my Droid. I've even told people on here to do it too, so I'm practicing what I'm preaching!
I think what I'm going to do is, reflash to stock 6.2.1, use the new root method, push TWRP/FFF again, and then CM7. A little drastic, but I think that having a clean run at this might prove/disprove the theory.
My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.
krelvinaz said:
My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.
Click to expand...
Click to collapse
Yeah, this is happening a little too frequently for my liking. Occasionally is fairly OK, every day is not. But it has got worse since going to CM7, but that could be purely coincidence at this point.
Trying some different things right now, but it will be a few days before I know for certain.
This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.
butterflygirl said:
This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.
Click to expand...
Click to collapse
Thanks, that hadn't crossed my mind, but I like my brightness at a pretty high level, and as the sensor is not working currently, it pretty much stays at that level.
Back at stock 6.2.1 now. Going to root it and leave it like this for a few days to see what happens.
sl0ttedpig said:
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.
Click to expand...
Click to collapse
Not sure if you have resloved this issue, but having read most of the Forum Dev Thread for the CM7 initial release and the newest reboot of the first ROM I think many others are having this issue as well. I remember reading many post people were referring to something similar to your problem as "the sleep of death." I however am not having that problem with mine, but thought it might be helpful to know that it might not be your device specific and may be something with CM7 itself with some devices.

[Q] Worth flashing to Paranoid Android?

Is it worth worth flashing to Paranoid Android or should i stay with my stock rom?
That is really up to you I personally use AOKP but each person has their own preference. Just back up your current ROM and settings and flash away try a bunch of different ones figure out which one works best for you
I tried PA as it's very popular but there were unfortunately a few turn offs for me. I tried it a few times hoping I might like it but I couldn't.
I am not a fan of any tablet UI on my N7 at all, I use it exclusively in portrait mode (games aside). The main settings page is hard coded to display dual view. The sub menus can be changed through DPI settings. Also on the home screens, there will be a blue box around the home pages as you scroll. No ability to change lock screen colors.
I'm just picky like that and it's all cosmetic. If there were more options, I would of given it more of a chance. I really wanted to use it but couldn't. I went back to XenonHD.
Sent from my Nexus 7 using xda app-developers app
PA just somehow didn't suit me and my nexus 7. The tablet ui feels way too cramped, and per app layout sure is neat but I never quit bothered to use it, stock works fine of not better. Of course, it's just my personal opinion, why don't you try it out yourself to see what's what.
Is it possible to flash it without full wipe?
mgsstar said:
Is it possible to flash it without full wipe?
Click to expand...
Click to collapse
It depends on what ROM you probably come from (if you're coming from AOSP, most likely you have to full wipe; if coming from CM10 or CM10-based ROM's, you "might" not have to full wipe).
mgsstar said:
Is it possible to flash it without full wipe?
Click to expand...
Click to collapse
Just make a backup and you can easily flash back to where you were if you don't like PA. Otherwise you will have to set everything up but you can use titanium backup to save your apps and restore them.
Sent from my Nexus 7 using xda app-developers app
A lot of people say that it is the most customizable rom for nexus 7, so if you like the 'personalize everything' idea check it out, you will love it.
For me, PA works slower than other roms and is focused on customization, i dont really prefer it. I use SmoothRom now and it is acting great so far.
I love it so far, the only rom I've ever used but I am noticing the slight speed decrease and as time goes on I'm liking phablet mode more and using less of its features so I might look for something "more pure" soon.
That's my 2 cents
Sent from my HTC PH39100 using Tapatalk 2
mgsstar said:
Is it possible to flash it without full wipe?
Click to expand...
Click to collapse
Do a factory reset when flashing different roms. Save yourself a headache
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm running Cookies&Cream (PA/CNA hybrid) and its definitely faster than the CM10 nightly builds that I was running.

[Q] Is Nexus 7 supposed to be this way? (laggy)

Nexus 7 32GB is my first android device. Before I bought it, most people were saying that android is finally smooth, project butter and so on. But that's not the case here. I'm on 4.2.2 stock, have currents sync disabled, my storage is only half full, and my Nexus is starting to get on my nerves.
- screen rotation takes exactly 4 seconds, no exception.
- apps sometimes freeze, forcing me to force close them or even reboot occasionally.
- even some simple games, like Dragonvale, run like stop motion in certain segments.
- when I install ANY app, it seems that android service responsible to put icon on my home screen takes 100% CPU time for 10-15 seconds or so.
- when there are app updates, my nexus is unusable. Takes 10+ seconds for any action.
Say what you want about windows phone, but that thing flies. Am I maybe spoiled by it's buttery smoothness so android by comparison irritates me, or is there really something wrong with my Nexus? I already did hard reset once, early on. It did not help. Should I try again? If so, what backup solution is the easiest?
I know I might be asking a lot and that there are threads about this already, but info is scattered, and there are numerous contradicting opinions and advices. Basically I am just not sure if this is how it's supposed to be, or should I try something.
The lag after installing app is there because of R/W being made to internal memory. App's icons on homescreen are being placed by Play. You can disable it in it's settings. But the rest sounds like a rouge app. Are you sure this lag is there even after fresh system installation?
Odoslané z Galaxy Nexus cez Tapatalk 2
Root, get Franco, disable fsync, enjoy.
Sent from my Nexus 7 using xda app-developers app
Terepin said:
The lag after installing app is there because of R/W being made to internal memory. App's icons on homescreen are being placed by Play. You can disable it in it's settings. But the rest sounds like a rouge app. Are you sure this lag is there even after fresh system installation?
Odoslané z Galaxy Nexus cez Tapatalk 2
Click to expand...
Click to collapse
How do I detect a rouge app? Task manager? Can you recommend one?
It was slow to start with. Disabling currents sync did not help. And I did do reset in the first few days. Did not help.
Now, it's just even more slower. Perhaps by as much as 50% in some actions, if I can put a number on a subjective impression.
Dr.Molestratus said:
Root, get Franco, disable fsync, enjoy.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Rooted, don't want to mess with kernels and ROMs, what's fsync?
While I'm at it, I rooted with wugfresh rootkit, worked flawlessly, but I can't install adaway. Any thoughts?
d.a.v.o.r said:
Rooted, don't want to mess with kernels and ROMs, what's fsync?
While I'm at it, I rooted with wugfresh rootkit, worked flawlessly, but I can't install adaway. Any thoughts?
Click to expand...
Click to collapse
Well if you want better performance... ROMs and kernels are the things to mess with.
Sent from my Nexus 7 using Tapatalk HD
You should probably flash a ROM/kernel for best performance. But if you still don't want to mess with ROMs, reflash the stock rom and reroot it. That's what helped me.
I've had some issues with my phone lagging during/after app update, and i've only recently nailed down the culprit. Turns out it was the Root Uninstaller app that was making backups of older versions of the apps during the update, it ceased after i turned off the option in it's settings (or just uninstall). My guesstimate would be that you have some app that is doing just that. Because my own n7 doesn't noticeably lag even if i try to update many (as much as 10) apps at the same, which usually kills my single-core SGSL into a reboot shortly after trying this.
I think 4.2 is just buggy. It flies for me sometimes and on some devices, and sometimes it crawls horribly. Maybe the next android version will fix this, maybe not
Sent from my Nexus 4 using Tapatalk 2
This helped me a little (If you don't use Currents then this could help)
1. Go to Settings > Apps > All (swipe right 2 times) > Currents
2. Click "Force Stop"
3. Click "Disable"
It should be now fixed for some of it. Like the earlier posts suggest, maybe reflashing stock ROM or installing a kernel (once you're comfortable) will help for sure.
It seems messing with kernels and roms is the best way to do it.
And even though I'm asking this on XDA, I'm not really comfortable with that, especially considering that I've come across the word "bricked" many a times. Especially since I have almost two years of warranty left.
I'll give it a thought and see if I'll go along. It depends how irritating the lag becomes. But by the looks of it, I'll end up with a windows 8/blue tablet next time around, when the next gen silicone from AMD and Intel is ready. I'm much more comfortable with windows environment.
AW: [Q] Is Nexus 7 supposed to be this way? (laggy)
If you're having a lot of apps installed you can get ram problems. Some apps are running in the background even if they don't need to. If you wanna know which apps those are simply go to apps and swipe to the second panel. There you can see which asps are running in the background .You should delete them. If you don't want to do that simply download the app Greenify
(You should have more than 200mb free)
Sent from my Nexus 7 using xda app-developers app
Entropy generator, I just use pimp my ROM, even on stock rooted.
Sent from my Nexus 7 using xda app-developers app
I'm on paranoid 2.54 which is 4.1 and it feels faster than cm10.1 I miss 4.2.2 fonts but I'll see If I get it.
BR.
d.a.v.o.r said:
It seems messing with kernels and roms is the best way to do it.
And even though I'm asking this on XDA, I'm not really comfortable with that, especially considering that I've come across the word "bricked" many a times. Especially since I have almost two years of warranty left.
I'll give it a thought and see if I'll go along. It depends how irritating the lag becomes. But by the looks of it, I'll end up with a windows 8/blue tablet next time around, when the next gen silicone from AMD and Intel is ready. I'm much more comfortable with windows environment.
Click to expand...
Click to collapse
Get rid of your Nexus and buy a bloody surface then?
In regards to your question, if you've Rooted but cannot install Adaway then it seems you haven't rooted correctly.
This may be the source of your issues.
As explained before, factory reset, re-root and then if you really wanna see it fly take our advice.
A good start is Paranoid Android and Faux123 Kernel (I've been using this combo since I bought my nexus, and yes I've tried other combo's I just can't stay away). Paranoid is an epic ROM, and IMO Faux cannot be beaten. He finds the absolute perfect point between performance and battery !!.
Unless you seriously can't follow directions you won't brick your device. People throw that term around when they are far from bricked. Just make sure you understand the steps of anything you are doing and use good sense. If things go sideways, don't just start doing things blindly. Research the problem you are having, and ask for help if you need it.
But you shouldn't have to run a custom rom to get smooth performance. Like has been suggested I'd go back to stock. Root, and add things back as you need them. See if it runs smooth with only a basic set of apps installed.
Your N7 will be fastest on a custom ROM/kernel. But it should be perfectly usable on a stock setup.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
Wilks3y said:
Get rid of your Nexus and buy a bloody surface then?
In regards to your question, if you've Rooted but cannot install Adaway then it seems you haven't rooted correctly.
This may be the source of your issues.
As explained before, factory reset, re-root and then if you really wanna see it fly take our advice.
A good start is Paranoid Android and Faux123 Kernel (I've been using this combo since I bought my nexus, and yes I've tried other combo's I just can't stay away). Paranoid is an epic ROM, and IMO Faux cannot be beaten. He finds the absolute perfect point between performance and battery !!.
Click to expand...
Click to collapse
RT is a joke, and PRO is too expensive and has awful battery life. I'll wait and see how temash and baytrail turn out to be. But that's besides the point, since I'll still keep nexus as an ultra-mobile device.
In any case, can I backup all the data, reset, and get EVERYTHING back, or will I need to do something manually? I'll definitely try to reset/re-root.
But I don't see what I did wrong. I mean, I can install every app on the market that requires root
ezas said:
Unless you seriously can't follow directions you won't brick your device. People throw that term around when they are far from bricked. Just make sure you understand the steps of anything you are doing and use good sense. If things go sideways, don't just start doing things blindly. Research the problem you are having, and ask for help if you need it.
But you shouldn't have to run a custom rom to get smooth performance. Like has been suggested I'd go back to stock. Root, and add things back as you need them. See if it runs smooth with only a basic set of apps installed.
Your N7 will be fastest on a custom ROM/kernel. But it should be perfectly usable on a stock setup.
Click to expand...
Click to collapse
Ok, I'll try it. First with reset.
But also, my nexus is usable, it's just not pleasant to use.
d.a.v.o.r said:
RT is a joke, and PRO is too expensive and has awful battery life. I'll wait and see how temash and baytrail turn out to be. But that's besides the point, since I'll still keep nexus as an ultra-mobile device.
In any case, can I backup all the data, reset, and get EVERYTHING back, or will I need to do something manually? I'll definitely try to reset/re-root.
But I don't see what I did wrong. I mean, I can install every app on the market that requires root
Ok, I'll try it. First with reset.
But also, my nexus is usable, it's just not pleasant to use.
Click to expand...
Click to collapse
It honestly shouldn't lag like that. Even bone stock.
One thing you can do right away is go into developer settings (click 7 times on Build Number in About Tablet to enable) and change all animation settings to.5 or to none.
DL Root Checker, or just try to use any root app to see if you actually do have root. Even with the wonderful toolkits (which will also save your bacon if you get into a bootloop) getting root to stick can be tricky...you may have to run it a couple of times.
But the best results will come if you flash a custom rom and kernel. if you like a tweaked stock experience, try CleanRom Inheritance. It uses the Aroma installer, so it's very easy and customizable. It can be found under Android Development.
d.a.v.o.r said:
RT is a joke, and PRO is too expensive and has awful battery life. I'll wait and see how temash and baytrail turn out to be. But that's besides the point, since I'll still keep nexus as an ultra-mobile device.
In any case, can I backup all the data, reset, and get EVERYTHING back, or will I need to do something manually? I'll definitely try to reset/re-root.
But I don't see what I did wrong. I mean, I can install every app on the market that requires root
Ok, I'll try it. First with reset.
But also, my nexus is usable, it's just not pleasant to use.
Click to expand...
Click to collapse
You can use titanium backup. It there others like carbon. But titanium has been around the longest and it's my preferred way. Requires root, and it should warn you at start up if you aren't rooted correctly.
I would do as others suggested and just restore basic apps after factory reboot and re root. Then slowly restore others to see if you notice other problems along the way.
Also, if you didn't know. You can install kernels without wiping tablet and changing the whole Rom. I would definitely try that eventually too.
One more thing to note. Don't judge android on chrome (not that you mentioned it, but I know a lot of newbies have). It's one of the slowest browsers. It has tons of great features which I love, but do slow compared to most others. I wish I wasn't so addicted to its syncing.
Thanks to everyone on advices.
1) root checker says I do not have proper root. Now that I think about it, I did update my Nexus 7 from 4.2.1 to 4.2.2. I guess that also removed root.
2) I will reset. I don't really have any messages or photos or app data that is not already in the cloud that I need to backup.
3) I'll try to gradually install everything app by app to see if it's a rouge app.
4) I'll than revive this thread with my results. Though I doubt I'll get to doing all that in the next few days.
Again, thanks everyone!

Nexus S 4G Rom that doesn't crash every hour and lock up at boot screen?

I recently had to go back to my Nexus S 4G and I've been frustrated because it seems like every ROM I've tried has had issues with crashing at least once an hour if not more and often getting stuck at the bootscreen (google logo) when it resets.
I'm at the point where I'm beginning to wonder if its a hardware problem not a software one.
Try the new jelly shot v3.3 for a 4.2.2 rom.I'm running that and it doesn't lag or crash so far. Or for 4.1.2 try rasbeanjelly or cm10 stable or the last cm10 nightly
Sent from my Nexus S 4G using Tapatalk 2
pandaman21 said:
Try the new jelly shot v3.3 for a 4.2.2 rom.I'm running that and it doesn't lag or crash so far. Or for 4.1.2 try rasbeanjelly or cm10 stable or the last cm10 nightly
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I did try rasbeanjelly and it had the same crashing. CM10 I never got very far because no matter how many times I wiped after I would boot it, the keyboard would just constantly force close.
I'll give the jelly shot one a try.
CM 9.1 is very stable and is a real sweet spot. Just keep the kernel that comes with it and you will be good to go. I use interactive governor and over clock to 1200.
For Cm 9.1 there are 2 different ones. One of them is bigger and then other smaller do you know which one I install?
Sent from my Nexus S 4G using Tapatalk 2
pandaman21 said:
For Cm 9.1 there are 2 different ones. One of them is bigger and then other smaller do you know which one I install?
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Yes ... the larger of the two is the correct one.
akijikan said:
I recently had to go back to my Nexus S 4G and I've been frustrated because it seems like every ROM I've tried has had issues with crashing at least once an hour if not more and often getting stuck at the bootscreen (google logo) when it resets.
I'm at the point where I'm beginning to wonder if its a hardware problem not a software one.
Click to expand...
Click to collapse
Looks like a hardware issue to me...
My 3G is like yours, but my i know it's broken and i will send to warranty soon, before the warranty ends...
akijikan said:
I recently had to go back to my Nexus S 4G and I've been frustrated because it seems like every ROM I've tried has had issues with crashing at least once an hour if not more and often getting stuck at the bootscreen (google logo) when it resets.
I'm at the point where I'm beginning to wonder if its a hardware problem not a software one.
Click to expand...
Click to collapse
Same exact thing is happening to me. Have tried cm10.1 and slim beam but both have the same issue. Very frustrating.
If you have tried multiple roms and are formatting boot, system, cache and data you may want to just backup the sdcard to a computer and format it too. Personally, my phone runs very stable on slimbean with marmite 8.5 bigmem. If you're hanging on the Google logo I would suspect an issue with one of the partitions though and format is about the only option for that. Just DON'T format wimax!
Sent from my Nexus S 4G using Tapatalk 2
dpeeps74 said:
If you have tried multiple roms and are formatting boot, system, cache and data you may want to just backup the sdcard to a computer and format it too. Personally, my phone runs very stable on slimbean with marmite 8.5 bigmem. If you're hanging on the Google logo I would suspect an issue with one of the partitions though and format is about the only option for that. Just DON'T format wimax!
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I'll give that a try. Trying to keep this phone up and running till the next nexus at the end of the year... thanks!
dpeeps74 said:
If you have tried multiple roms and are formatting boot, system, cache and data you may want to just backup the sdcard to a computer and format it too. Personally, my phone runs very stable on slimbean with marmite 8.5 bigmem. If you're hanging on the Google logo I would suspect an issue with one of the partitions though and format is about the only option for that. Just DON'T format wimax!
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Is there anything specific i should know about reformatting? Will i lose root or will it affect unlocking the bootloader? Also there are lots of items to format: sdcard, system, cache, data, boot and wimax. Should I format all of them except for wimax as you mentioned?
Thanks again... will try when i get back home today.
last night i reformatted everything... boot, system, cache, data, etc. loaded cm10.1 thru adb. at first i thought this solved the issue... but nope. still having rebooting/google splash screen problems.
i think the problem has to do w/ when the phone comes in and out of sleep... the reboots only happen when the phone sleeps... in addition I have set the phone so that it doesnt sleep when its charging, and lo and behold, no reboots.
anyone have any idea what might be happening?

Looking for testers for PAC-rom

As I don't have the device yet, I need some testers to test early builds of PAC-rom for honami.
Please let me know if you want to help....
Requirements:
- Unlocked bootloader
- A little experience on how to install ROMS via Recovery (CWM/TWRP)
- Preferably know how to get logs (logcat) from the device
Download it here:
http://d-h.st/Arq
Also, you need to flash these GAPPS after flashing the ROM:
http://goo.im/gapps/gapps-jb-20130813-signed.zip
More information on PAC-rom: http://www.pac-rom.com/
Thanks.
jeroenqui said:
As I don't have the device yet, I need some testers to test early builds of PAC-rom for honami.
Please let me know if you want to help....
Requirements:
- Unlocked bootloader
- A little experience on how to install ROMS via Recovery (CWM/TWRP)
- Preferably know how to get logs (logcat) from the device
Just reply here and I will send you the download link in PM.
More information on PAC-rom: http://www.pac-rom.com/
Thanks.
Click to expand...
Click to collapse
Contemplating unlocking the bootloader to test this, is the Sony backup app still in this rom?
Sent from my C6903 using XDA Premium 4 mobile app
ianford10 said:
Contemplating unlocking the bootloader to test this, is the Sony backup app still in this rom?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, it's not included.
jeroenqui said:
No, it's not included.
Click to expand...
Click to collapse
Can it be or is that Sony exclusive?
Sent from my C6903 using XDA Premium 4 mobile app
It's only for stock roms, yes
Sent from my C6603 using Tapatalk 4
jeroenqui said:
As I don't have the device yet, I need some testers to test early builds of PAC-rom for honami.
Please let me know if you want to help....
Requirements:
- Unlocked bootloader
- A little experience on how to install ROMS via Recovery (CWM/TWRP)
- Preferably know how to get logs (logcat) from the device
Just reply here and I will send you the download link in PM.
More information on PAC-rom: http://www.pac-rom.com/
Thanks.
Click to expand...
Click to collapse
I'll give it a try.
I might not make it my daily driver if a lot of stuff is broken, but I can certainly load it up, test it out, log any bugs, rinse, and repeat...
Download it here:
http://d-h.st/Arq
Also, you need to flash these GAPPS after flashing the ROM:
http://goo.im/gapps/gapps-jb-20130813-signed.zip
iconoclastnet said:
I'll give it a try.
I might not make it my daily driver if a lot of stuff is broken, but I can certainly load it up, test it out, log any bugs, rinse, and repeat...
Click to expand...
Click to collapse
Any results?
jeroenqui said:
Download it here:
http://d-h.st/Arq
Also, you need to flash these GAPPS after flashing the ROM:
http://goo.im/gapps/gapps-jb-20130813-signed.zip
Click to expand...
Click to collapse
Thanks! I'll give it a spin and let you know how it looks.
iconoclastnet said:
Thanks! I'll give it a spin and let you know how it looks.
Click to expand...
Click to collapse
Hey, any news?
jeroenqui said:
Hey, any news?
Click to expand...
Click to collapse
Sorry for the slow progress.
I got as far as the "insert coin" animation and then it just looped there. (Not a true bootloop, just stuck at that point with the animation still looping). However, I then tried to flash back to my previously working rom and saw roughly the same behavior, so I'm not completely convinced that the wipe/factory-reset option in the current recovery images is working entirely right.
So, I'm back on pure stock firmware and planning on doing a full sony/google style wipe everything including the internal "sdcard", and trying again from a known clean slate. If I can reproduce the same behavior, I'll call it a bug and send logs. If not, then hopefully I'll have better news.
iconoclastnet said:
Sorry for the slow progress.
I got as far as the "insert coin" animation and then it just looped there. (Not a true bootloop, just stuck at that point with the animation still looping). However, I then tried to flash back to my previously working rom and saw roughly the same behavior, so I'm not completely convinced that the wipe/factory-reset option in the current recovery images is working entirely right.
So, I'm back on pure stock firmware and planning on doing a full sony/google style wipe everything including the internal "sdcard", and trying again from a known clean slate. If I can reproduce the same behavior, I'll call it a bug and send logs. If not, then hopefully I'll have better news.
Click to expand...
Click to collapse
Ok, thanks man.. Did you flash GAPPS after the ROM though?
If factory reset is not working, you can just wipe the /data partition. That should be enough...
There is an issie with C6902 Models. Somehow they have issues booting AOSP based roms like CM etc.
I'll flash it today. Sorry for the delay Jeroen.. I'm making a web shop for my uncle so don't have a lot of time at the moment. But today I'll flash for sure
Sent from my Xperia Z1 using xda app-developers app
OK, I did another install and it seems to be working this time.
Camera is non-functional, I'm sure that's no surprise.
The logs show "LLC length mis-match" repeatedly, although other roms I've run on the Z1 do the same.
So far, everything else seem to be working, but there are quite a few options to run through. I'll try and test out as many features and see if anything else pops up.
For the record, this is on a c6903
I've been living with this rom for a couple of days now, and haven't found any serious issues.
Pie menu works great. Hybrid engine seems fine with various combinations of dpi and layout. The various navigation bar and status bar tweaks seem to do what you'd expect. Same with the power toggles. Haven't delved into halo or gesture settings yet.
I've found that the camera issue is a bit more annoying than I expected, even though I wasn't planning on taking any photos. I know we're all still waiting for a real camera fix, but the "partially working but still buggy" state of the camera in a few of the other roms has been good enough for things like face unlock, qr code scans, etc. I guess you don't realize how much you use that stuff until it's gone.
The hardware info section of the settings seems to be missing a few values, although that appears to be purely cosmetic as all the hardware seems to work fine apart from the cameras. Phone, bluetooth, wifi, gps, etc. all seem fine. I haven't yet tried out some of the more esoteric hardware features (mhl, miracast, etc.)
Fwiw, Antutu is showing lower scores than the last couple of roms I've tried, but that should of course be taken with a grain of salt. (Lies, damn lies and benchmarks.)
I'll report back if anything else pops up.
iconoclastnet said:
I've been living with this rom for a couple of days now, and haven't found any serious issues.
Pie menu works great. Hybrid engine seems fine with various combinations of dpi and layout. The various navigation bar and status bar tweaks seem to do what you'd expect. Same with the power toggles. Haven't delved into halo or gesture settings yet.
I've found that the camera issue is a bit more annoying than I expected, even though I wasn't planning on taking any photos. I know we're all still waiting for a real camera fix, but the "partially working but still buggy" state of the camera in a few of the other roms has been good enough for things like face unlock, qr code scans, etc. I guess you don't realize how much you use that stuff until it's gone.
The hardware info section of the settings seems to be missing a few values, although that appears to be purely cosmetic as all the hardware seems to work fine apart from the cameras. Phone, bluetooth, wifi, gps, etc. all seem fine. I haven't yet tried out some of the more esoteric hardware features (mhl, miracast, etc.)
Fwiw, Antutu is showing lower scores than the last couple of roms I've tried, but that should of course be taken with a grain of salt. (Lies, damn lies and benchmarks.)
I'll report back if anything else pops up.
Click to expand...
Click to collapse
Thank you for reporting!
Can you also post this here: http://forum.xda-developers.com/showthread.php?t=2478003
The ROM has been released officially and an update has been released yesterday!
Thanks for testing!!!

Resources