CM10.2 Discussion, General Talk, Q/A Thread - Nexus 7 (2013) General

We can basicly use this thread for discussion, general talk, Q/A as long as its about CM.
Bugs:
Deadlocks (JSS15J bug)
Miracast & PTV3000
You tell me
F.A.Q
Enable root: Developer settings->Root Access->Apps and ADB. Also turn on USB-debugging.
Gapps: Photosphere is not included in standard gapps, use an alternative gapps package.
Links:
Download: http://get.cm/?device=flo (Wi-Fi)
GApps: http://goo.im/gapps
BBQLog: http://changelog.bbqdroid.org/#/flo/next

Whats a deadlock? Its obviously different from a wakelock? I have been on CM10.2 for a week now, surprising no noticable issues day to day. Good performance and battery life.

Just tested out Miracast last night using the Rocketfish receiver (RF-WFD301) from BB. Miracast worked for me although there were some pixelations and momentary screen freezes here and there. Of course, there's also the lag that you'd expect with Miracast at this stage.
Am on the latest CM10.2 nightly which was cm-10.2-20130819-NIGHTLY-flo.zip when I tested.
Planning to return the Miracast receiver though. Don't think the technology is quite ready for prime time yet and personally, was more of a urge to check it out but don't really have a need for it.

I mentioned this elsewhere, but I might as well bring it up here too since this will probably turn into a more official thread...
I've noticed here that my tablet isn't automounting USB drives (via OTG) on its own; I need an external app to do that, unlike my phone (d2att; both devices running 8/21 right now).
Is this intentional, a hiccup, or something else?

Deadlock is when it freezes, caused by a keyboard bug
Sent from my Nexus 7 using Tapatalk 4

I've only had one deadlock and I flash about 2 nightlies a week

CM Kanged rom is working great here. No more reboots and lots of options. Closest thing to the official AOKP rom there is until they start making AOKP 4.3 roms.
I did have one deadlock that recovered but I was updating some apps, which is expected from time to time.
I'm using a release from 8/8. Can't find a reason to update. I think there might be some issues with 8/20 because I tried many CM based nightly ROMs and all FC the AOSP keyboard on my Galaxy Nexus. Flashed a 8/18 nightly and it appears fine.
I'm happy with the CM Kanged rom until they mature enough to upgrade. Fast, smooth, no quirks, no random reboots like stock ROMs experience. Quite happy. It has the new HALO notification and SideBar built in. Probably has that weird navigation PA feature too that I don't use. HALO is weird but growing on me. Works good on a tab. Not sure about using it on my phone yet. I had to watch a video on how to use it before it really made sense.
Sent from my Nexus 7 using XDA Premium 4 mobile app

cowabunga said:
Just tested out Miracast last night using the Rocketfish receiver (RF-WFD301) from BB. Miracast worked for me although there were some pixelations and momentary screen freezes here and there. Of course, there's also the lag that you'd expect with Miracast at this stage.
Am on the latest CM10.2 nightly which was cm-10.2-20130819-NIGHTLY-flo.zip when I tested.
Planning to return the Miracast receiver though. Don't think the technology is quite ready for prime time yet and personally, was more of a urge to check it out but don't really have a need for it.
Click to expand...
Click to collapse
Might be ptv3000 issue then, removing it from bugs list.
smelenchuk said:
I mentioned this elsewhere, but I might as well bring it up here too since this will probably turn into a more official thread...
I've noticed here that my tablet isn't automounting USB drives (via OTG) on its own; I need an external app to do that, unlike my phone (d2att; both devices running 8/21 right now).
Is this intentional, a hiccup, or something else?
Click to expand...
Click to collapse
This is normal on nexus devices as far as I know.
Sent from my Nexus 7 using Tapatalk 4

Hey utacka ..lived your work on PA for the note !!
Planning to dev for the flo as well ??
Sent from my HTC One using Tapatalk 2

aamitabh28 said:
Hey utacka ..lived your work on PA for the note !!
Planning to dev for the flo as well ??
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Not planning going back to PA, maybe some gerrit patches to CM (mako, flo or whatever).
Sent from my Nexus 7 using Tapatalk 4

This is the first time I've ever run a CM rom. How long will it take them to incorporate JSS15Q now that its out?

Utacka said:
This is normal on nexus devices as far as I know.
Click to expand...
Click to collapse
Is this a hardware issue, then? That sounds implausible at best.

SalTNutz said:
This is the first time I've ever run a CM rom. How long will it take them to incorporate JSS15Q now that its out?
Click to expand...
Click to collapse
Yeah. How long will it take CM10.2 to pick the latest update changes up?

Should we expect overclocking options in the official CM in the future? I'm curious to see what my device can handle, but I prefer to stick with official CM builds where I can trust that code is the same as what's public.
Sent from my Nexus 7 using xda app-developers app

ragesoss said:
Should we expect overclocking options in the official CM in the future? I'm curious to see what my device can handle, but I prefer to stick with official CM builds where I can trust that code is the same as what's public.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You usually have to install one of the other developer kernels to get fancy with the kernel (ie. OC, UV, fancy governors, fancy schedulers, etc...).

cowabunga said:
Yeah. How long will it take CM10.2 to pick the latest update changes up?
Click to expand...
Click to collapse
I'm not seeing them yet. Give it some time.

8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.

cowabunga said:
8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.
Click to expand...
Click to collapse
I trust you mean 8/23
And no, the stock update fixes aren't in it.

I don't know if it's just me but, every time i launch the focal app the image that I get is always darker than with the stock camera app?
Sent from my Nexus 7 using xda app-developers app

cowabunga said:
8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.
Click to expand...
Click to collapse
They will be in the next build
Anyone successfully changed the CPU governor to Interactive? Mine reboots a few seconds after setting it to that

Related

[Q] Is CM10 for Nexus 7 Good For Daily Drive?

I've long been a fan of Cyanogenmod's builds and I've used since my OG Droid days. I have a nice, clean Google Nexus 7 now, and I'm asking you guys if it's ready for daily drive. I don't have the time or energy anymore to continuously load nightly builds and I'd like to keep it down to maybe a monthly thing.
So, what's the deal? How is CM10 different from Google's own N7 JellyBean build?
been using it as a daily driver since 9/15 came out and I haven't had any problems.
tebuddy said:
been using it as a daily driver since 9/15 came out and I haven't had any problems.
Click to expand...
Click to collapse
Update to a build on the 19th or newer if you haven't flashed my lag fix. Its now in the cm10 source code on builds from the 19th or newer. It makes a huge difference and fixes flickering in certain apps as well.
Cm10 includes the stock jellybean browser which in my opinion is vastly superior to chrome for android. Much smoother and it doesn't take forever to render when scrolling.
Sent from my Nexus 7 using xda premium

Nexus 4 - CM10.1 Pros Cons

Looking for feedback on CM10.1 vs. sticking with the stock ROM. I've used CM10.1 on my GS3 , but wondering what the advantages are of using it on the N4.
Being that you have used both stock build and cm10 you should be able to judge which works better for you.
Sent from my Optimus G using XDA premium
pros: added features, fixes bugs from the stock ROM
cons: none
Sent from my Nexus 4 using xda premium
The pros are the same as your galaxy. It's the same rom
Sent from my Transformer TF101 using Tapatalk HD
Does the Google voice integration work the same (ie when it takes over the phone and messaging functions completely)
Sorry to jump on this, but I'm considering the same largely for battery and some tweaking options.
Sent from my Nexus 4 using xda app-developers app
emailrob said:
Does the Google voice integration work the same (ie when it takes over the phone and messaging functions completely)
Sorry to jump on this, but I'm considering the same largely for battery and some tweaking options.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yes it works the same. you can set it to do that if you choose to, if not u can disable it.
The only con is a slightly slower Android upgrade path. Having said that, 2-3 weeks max (for a Nexus device) isn't that long to wait. Beats all the manufacturers.
Ajfink said:
The only con is a slightly slower Android upgrade path. Having said that, 2-3 weeks max (for a Nexus device) isn't that long to wait. Beats all the manufacturers.
Click to expand...
Click to collapse
Not really. When CM does get updated to the next version of Android, Nexus devices are the first to get it on CM whereas other devices will take longer (and things may not be working day one for other phones whereas Nexus it will be working from day one, just not all the CM goodies will be available right away as it'll take time to port them over)
Alternatively, people may flash non-CM roms and just a AOSP version of the new Android to try out new features etc etc
My biggest consideration is battery , I'm not impressed with my battery hardly making it through a 8 hours of the day.
ksujace said:
My biggest consideration is battery , I'm not impressed with my battery hardly making it through a 8 hours of the day.
Click to expand...
Click to collapse
CM10 will most definitely help you out with that. Some people have been getting weird Android OS or Mediaserver troubles that eat away at their battery with stock 4.2.1. How many hours of screen on time are you getting?
ksujace said:
My biggest consideration is battery , I'm not impressed with my battery hardly making it through a 8 hours of the day.
Click to expand...
Click to collapse
Kernel plays a bigger role in battery conservation more than a ROM. People always gets mixed between the two.
To fix battery problems,
1) Ensure Google Latitude is off (it's in Google Maps). Disable automatic reporting of location and all the other checks in that menu.
2) Flash a ROM that meets your requirements (there is no BEST ROM).
3) Flash a Kernel that meets your requirements based upon feedback and past experiences (there is no BEST KERNEL).
4) Install BetterBatteryStats @ http://forum.xda-developers.com/showthread.php?t=1179809
5) Use BetterBatteryStats to ensure there are no kernel and partial wakelocks. If there are debug them. Ensure that your phone is indeed deep sleeping (use BetterBatteryStats to look at CPUStates or download CPUSpy from Play Store).
I recommend CM10.1 Jellybro + Franco Kernel, but that's based on my own personal opinions. Look around the dev forums and decide what you like the most
Edit: Oh yeah, how could I forget... go into Google Now and disable the cards you don't need.
zephiK said:
Kernel plays a bigger role in battery conservation more than a ROM. People always gets mixed between the two.
To fix battery problems,
1) Ensure Google Latitude is off (it's in Google Maps). Disable automatic reporting of location and all the other checks in that menu.
2) Flash a ROM that meets your requirements (there is no BEST ROM).
3) Flash a Kernel that meets your requirements based upon feedback and past experiences (there is no BEST KERNEL).
4) Install BetterBatteryStats @ http://forum.xda-developers.com/showthread.php?t=1179809
5) Use BetterBatteryStats to ensure there are no kernel and partial wakelocks. If there are debug them. Ensure that your phone is indeed deep sleeping (use BetterBatteryStats to look at CPUStates or download CPUSpy from Play Store).
I recommend CM10.1 Jellybro + Franco Kernel, but that's based on my own personal opinions. Look around the dev forums and decide what you like the most
Edit: Oh yeah, how could I forget... go into Google Now and disable the cards you don't need.
Click to expand...
Click to collapse
+1 for CM10.1 Jellybro + Franco. I've also used MiNCO ROM which is pretty good, but not a ton of features yet so I'm sticking with CM10.1
Installed CM10.1 , seems there is more real estate (5 icons across vs 4?) ...
anyone else had the problem where you can't create app folders on the home screen?
Hey what is CM10.1 JellyBro?
Is it the nightly CM 10,1?
ksujace said:
Installed CM10.1 , seems there is more real estate (5 icons across vs 4?) ...
anyone else had the problem where you can't create app folders on the home screen?
Click to expand...
Click to collapse
I hear that's an issue on the latest nightly. I'm sure they'll address that in the upcoming nightly.
mediumsteak said:
Hey what is CM10.1 JellyBro?
Is it the nightly CM 10,1?
Click to expand...
Click to collapse
It's the same thing as CM10.1 but including cherry picks.
Cherry picks are unmerged features that are currently pending/awaiting approval from CM. They are implemented within Jellybro before official nightlies get them. It is a very stable ROM and uses the same sources as CM. So whatsever in CM10.1 is in Jellybro, just jellybro has extras (very minimal)
http://forum.xda-developers.com/showthread.php?t=2015081 is the thread.
mediumsteak said:
Hey what is CM10.1 JellyBro?
Is it the nightly CM 10,1?
Click to expand...
Click to collapse
Check it out ...
JellyBro link
It's basically CM 10.1 with some cherry picks (additions) that either get merged into CM or they are removed because they become obsolete
dmorand said:
I hear that's an issue on the latest nightly. I'm sure they'll address that in the upcoming nightly.
Click to expand...
Click to collapse
It's fixed in 12/27.
To elaborate on dmorand,
If cherry picks disappear, it's because they were merged, abandoned or conflict with the current source or other cherry picks.
Click to expand...
Click to collapse
not only because they are 'obsolete' (not really obsolete but abandoned)
I heard from my friend that CM isn't as stable as stock but does have the added features. Can anyone confirm about CM's stability as to stock?
mgkrp said:
I heard from my friend that CM isn't as stable as stock but does have the added features. Can anyone confirm about CM's stability as to stock?
Click to expand...
Click to collapse
that's only the case on devices that weren't made to run aosp android, such as HTC (sense), Samsung (touchwiz), motorolla (motoblur). on nexus devices that natively run stock android, cm works id say 99% perfectly. and usually if there is a "bug" its cosmetic and doesn't affect the functionality of the phone one bit, and once reported by a user it gets fixed pretty fast (within the next few nightlies) :beer:
Sent from my Nexus 4 using xda premium

Just ordered N4

Hey I just ordered my nexus 4. Just a quick question, which custom rom most resembles the stock one that the n4 comes with but with better tweaks and battery life?
Coming from an s3 and I've always used a touchwiz based custom rom.
So I would like to stay with the rom that most is similar to the one the n4 comes with. Ty
Sent from my SGH-T999 using xda app-developers app
Probably Primerunner under Nexus 4 Android Development. Seems pretty stock but with some enhancements.
Sent from my Nexus 4 using Tapatalk 2
MiNCO v6 ROM resembles the stock ROM. No customizations.
Sent from my Nexus 4 using Tapatalk 2
All of them resemble stock. They're all themed the same, it's just a matter of added features while maintaining the same look as stock.
I don't get what you're trying to get at op. It's not like s3 roms where everybody is trying to theme their rom. A lot of roms on n4 aren't themed, some are but most are left it's holo look.
Sent from my Nexus 4 using xda premium
zephiK said:
All of them resemble stock. They're all themed the same, it's just a matter of added features while maintaining the same look as stock.
I don't get what you're trying to get at op. It's not like s3 roms where everybody is trying to theme their rom. A lot of roms on n4 aren't themed, some are but most are left it's holo look.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I guess... From a stability point of view... To be as stable as the stock.
I've ran cm10.1 and cm10...Along with some other aokp roms on my s3 before and of course it's not as stable as the stock tw rom.
Sent from my SGH-T999 using xda app-developers app
Minco
Sent from my Nexus 4 using xda premium
All the ROMs should be very stable since they are all based on the same AOSP code. This is very different from a non-Nexus phone where custom ROMs might be less stable.
Sent from my Nexus 4 using xda premium
Don't want to create new thread so will ask here as I'm also coming from S3...
Are the any major bugs with CM rom? With the S3, Picassa sync and Bluetooth didn't work...I'm assuming with the N4 everything should be more or less 100%?
steviewevie said:
All the ROMs should be very stable since they are all based on the same AOSP code. This is very different from a non-Nexus phone where custom ROMs might be less stable.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yeah that makes sense... Thanks.
Sent from my SGH-T999 using xda app-developers app
Crisisx1 said:
I guess... From a stability point of view... To be as stable as the stock.
I've ran cm10.1 and cm10...Along with some other aokp roms on my s3 before and of course it's not as stable as the stock tw rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Well the difference is that this is NEXUS device and is AOSP supported. So 99.9% of the ROMs that come out for this phone are stable. They're not stable on the S3 for AOKP/CM right away because they have to actually do work to make it work; whereas, N4 is AOSP supported and its like.. BAM! it works out of the box. As for S3, the phone ships out with TouchWiz. Going from TouchWiz to AOSP requires work to make everything work.
I'd say CM/AOKP are pretty stable overall. All ROMs are stable. This is one of the many benefits of having a Nexus device and I don't believe in when people are wanting to upgrade and people say "oh just get a S3.. it doesnt have latest but just flash a custom rom and you'll be on latest android) no it doesn't work that way just because of like what you said... instablity. When Android 5.0 (Key Lime Pie) comes out, N4 will be one of the first devices to launch with it and we'll have the most stable ROM day one without having to rework code to make all the functionalities like calling, 3G/4G, WiFi, Bluetooth, Screen Rotation, Data, etc to work (I know on other phones, people release dirty ROMs and things like what I listed don't work as of yet until its fixed)
Shopping for a ROM/Kernel is like shopping for a car. Some tips to take,
1) Browse the original and android dev forums. Search around and look for whats interesting.
2) Find it interesting? Read OP post and the past 6-7 posts (dont even read it.. skim through it for feedback)
3) Like what you see? Check for screenshots or even a YouTube video
4) Still like it? Flash it and try it
and most of all, ENJOY.
zephiK said:
Well the difference is that this is NEXUS device and is AOSP supported. So 99.9% of the ROMs that come out for this phone are stable. They're not stable on the S3 for AOKP/CM right away because they have to actually do work to make it work; whereas, N4 is AOSP supported and its like.. BAM! it works out of the box. As for S3, the phone ships out with TouchWiz. Going from TouchWiz to AOSP requires work to make everything work.
I'd say CM/AOKP are pretty stable overall. All ROMs are stable. This is one of the many benefits of having a Nexus device and I don't believe in when people are wanting to upgrade and people say "oh just get a S3.. it doesnt have latest but just flash a custom rom and you'll be on latest android) no it doesn't work that way just because of like what you said... instablity. When Android 5.0 (Key Lime Pie) comes out, N4 will be one of the first devices to launch with it and we'll have the most stable ROM day one without having to rework code to make all the functionalities like calling, 3G/4G, WiFi, Bluetooth, Screen Rotation, Data, etc to work (I know on other phones, people release dirty ROMs and things like what I listed don't work as of yet until its fixed)
Shopping for a ROM/Kernel is like shopping for a car. Some tips to take,
1) Browse the original and android dev forums. Search around and look for whats interesting.
2) Find it interesting? Read OP post and the past 6-7 posts (dont even read it.. skim through it for feedback)
3) Like what you see? Check for screenshots or even a YouTube video
4) Still like it? Flash it and try it
and most of all, ENJOY.
Click to expand...
Click to collapse
Great reply... awesome, makes a lot more sense now. Thank you. I can't wait til my N4 arrives : )))
I've been reading at other threads about people complaining about quick battery drain and the screen not looking too good... I hope that isn't the case with me.. but I'm pretty sure a custom rom and kernel can fix all of that.
Crisisx1 said:
Great reply... awesome, makes a lot more sense now. Thank you. I can't wait til my N4 arrives : )))
I've been reading at other threads about people complaining about quick battery drain and the screen not looking too good... I hope that isn't the case with me.. but I'm pretty sure a custom rom and kernel can fix all of that.
Click to expand...
Click to collapse
Quick battery drain. Hmmmm, you will probably notice that battery won't be good until at least 2-3 charge cycles. Why?
1. You just got the phone, obviously you're going to be playing with the phone. Downloading apps, changing settings, setting up your home screen etc.
2. It takes time for the phone to get its charging cycle.
3. Stock kernel has the msm wakelock. Fixed in a future OTA.
Screen looks great. I don't have any problems. But yes you are right, custom kernel does fix #3 and you can alter your colors until it satisfy your eyes. Stock values are good enough for me. It looks A LOT better than Samsung's Super AMOLED, I came from a Galaxy Nexus.

[Q] Roms NOT affected by 4.2.* issues

Hi,
I got a Nexus 10 device and get random reboots, bluetooth- and Wifi-problems and wonder if those problems are solved in other ROMs.
I've looked at ParanoidAndroid, CM10.1, AOKP and so on and they seem(?) premature for now? They all seem lovely though and after some time when they had the chance to mature I'll test all of them anyway
Is Nexus 10 a too new device so no one had the time to release a stable(Released as Stable by group) version of any Original Rom Dev?
Sv: [Q] Roms NOT affected by 4.2.* issues
Anyone...?
Sent from my GT-I9100 using xda app-developers app
I'm running CleanROM 2.0 and no reboot issues. I strongly believe that Chrome Browser is a major culprit with the reboot issue. CR does not contain Chrome, uses AOSP browser by default.
http://forum.xda-developers.com/showthread.php?t=2113048
sfobrien said:
I'm running CleanROM 2.0 and no reboot issues. I strongly believe that Chrome Browser is a major culprit with the reboot issue. CR does not contain Chrome, uses AOSP browser by default.
http://forum.xda-developers.com/showthread.php?t=2113048
Click to expand...
Click to collapse
How about the bluetooth and wifi issues?
Depends what you mean. Some people have problems connecting to some hardware, others dont. It is somewhat of a 4.2 issue, but it also has to do with hardware compatibility and what version of hardware you have for your bluetooth. You might just be SOL.
random reboots seem to happen a little bit from 4.2 issues but also from software compatibility issues from things that dont work well with the new system. So it will just take time there as well.
Thank you very much!
zidz said:
How about the bluetooth and wifi issues?
Click to expand...
Click to collapse
I don't have any WiFi issues. Don't use Bluetooth
I had some major issues with 4.2 on my nexus 7, which I was able to solve by flashing cm10.1 - this is 2 months ago. When I got the nexus 10 a month ago, I kinda immediately flashed cm10.1 and have not had 1 issue with it so far.... just my 2c
I've had reboot problems with the stock ROM and the Official AOKP ROM with the kernel it comes with. I've never had issues with bluetooth and my only problem with wifi is that it is not nearly as strong as my Galaxy S2's wifi. I've had no problems with Paranoid or CM, but I used ktoonsez's kernel with those. Right now, I am using Task650's AOKP with ktoonsez's kernel and it's running flawless. I have a lot of love for them as I use their stuff on my phone too. As far as I can tell, the problems are in the kernel.
CM10.1, and Franco kernal here with absolutely no problems...
I'm stock rooted build JOD40F without freezes .
Sent from my Nexus 10 using XDA Premium HD app

[Q]Which ROM would you recommend?

Hey guys,
I just recently got my Nexus 10 and after making sure everything is fine with it I want to go ahead and root it.
Since I'm using a HTC Sensation as my phone I know how much a good ROM can improve the user experience and I'm looking for a nice ROM with good battery life.
Normally it's pretty easy to find a thread with a poll, or suggestions etc. but I'm out of luck when it comes to the N10 - haven't found anything yet.
Which ROM would you recommend as a good starting point to try out?
Rather than a poll or suggestions, it'll be better if you try it out different ROMs on your own since most ROMs here are fairly stable. Just remember to read their features and stuff..
Sent from my Nexus 10 using xda app-developers app
Personally I recommend starting with CM. They have the easiest to use custom interface and pretty much everything just works fantastic. PA has gobs of customization but it is far from the smoothest experience on the N10. I personally just don't like AOKP.
Sent from my Nexus 10 using Tapatalk HD
Try a few to see what you like. Personally, I'd go with the latest AOKP PUB build. TONS of customization options, extremely stable, and the PUB extras make it smoother and faster.
I have run most of the ROMs and I prefer TeamEOS followed by AOKP. They both have built in custom optional tweaks.
Sent from my Nexus 10 using xda premium
Rodeojones said:
Try a few to see what you like. Personally, I'd go with the latest AOKP PUB build. TONS of customization options, extremely stable, and the PUB extras make it smoother and faster.
Click to expand...
Click to collapse
This ! if you like the customizations that AOKP offers try Mr.Robinsons AOKP PUB (Project Unicorn Butter).
I have to say i was a little bit disappointment with CM 10.1 on the manta, using it on my I9100 since almost 1.5 years.
In My Opinion AOKP PUB works better on our Device
Thanks for the replys guys, it's a lot easier for me to know which threads to look for now, thank you!
addicted1900 said:
This ! if you like the customizations that AOKP offers try Mr.Robinsons AOKP PUB (Project Unicorn Butter).
Click to expand...
Click to collapse
I'm using that one too, and it's great. And if you pair it with KTManta kernel you get a pretty customizable set up.
I don't know why, but Mr Robinson's was a bit of a nightmare for me. I tried twice (clean install) but each time one of my favorite apps, FX Explorer, would lock up when trying to set up/access remote locations and then the N10 would just reboot. It happened repeatedly whether I used TiBU to restore data or installed fresh from the Store. This doesn't happen with the AOKP (mr1, build 6) I'm on now. The final straw, though, was rebooting from recovery (didn't do anything, went in and changed my mind) and couldn't get past the lock screen.
Anyone have an idea what the hell was going on?
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
I don't know why, but Mr Robinson's was a bit of a nightmare for me. I tried twice (clean install) but each time one of my favorite apps, FX Explorer, would lock up when trying to set up/access remote locations and then the N10 would just reboot. It happened repeatedly whether I used TiBU to restore data or installed fresh from the Store. This doesn't happen with the AOKP (mr1, build 6) I'm on now. The final straw, though, was rebooting from recovery (didn't do anything, went in and changed my mind) and couldn't get past the lock screen.
Anyone have an idea what the hell was going on?
Click to expand...
Click to collapse
¿Did you happen to select the KTManta kernel during the installation?.
Arcano said:
¿Did you happen to select the KTManta kernel during the installation?.
Click to expand...
Click to collapse
I didn't do Aroma, just flashed the ROM, so didn't touch the kernal. It's the one from the (official?) JB-mr1-build 6 ROM. Was that a mistake?
Sent from my Nexus 10 using Tapatalk HD
I like Paranoidandroid for nexus 10. Gives you full tablet ui
Sent from my Nexus 4 using XDA Premium HD app
My favorite ROM's (in no particular order) are EOS, Rasbeanjelly, and CyanogenMod
bruce7373 said:
I didn't do Aroma, just flashed the ROM, so didn't touch the kernal. It's the one from the (official?) JB-mr1-build 6 ROM. Was that a mistake?
Click to expand...
Click to collapse
No, I asked because I had instability problems with that kernel, until I found out they were caused by improper gpu voltages.
But wiith the stock kernel and Mr.Robinson's rom my Nexus was rock solid, so I can't help you there.
I prefer AOKP ROM, because he faster that stock, he has many settings and very customize. Also he has good performance at games and benchmarks.
I decided to try the AOKP Pub by mrRobinson and I'm very satisfied so far
Might try Paranoid next, or I'll just stick with this one for a while - we'll see. You just have so many options to play around with on an Android device... it's beautiful.
Current look

Categories

Resources