Hi all,
So, I took the leap of rooting my HOX+ (international) about 2 months ago, and the ROM of choice was CM.
I loved it! Love everything about it. At the time, the "stable" channel hadn't been opened, so I was using the version in nightly - it's been moved to stable now - 10.1.
Since I was attached to the stable repo, Goo Manager notified me when 10.2 moved into nightly. After a couple of days of having it stick in my status bar, nagging for an update, I just clicked and let it do its thing.
Unfortunately, this broke my phone . I got an error something along the lines of "the process com.android.phone has stopped". When I tapped "okay" the notification would re-appear after <1 second. I've since found out via Google this is something to do with my kernel (why the auto-update didn't update the kernel too is beyond me =s ) - but at the time, I just wanted a functioning phone with minimal fuss, and thought it'd be best moving myself to stable anyway. This is what I did.
That was Tuesday of this week. Between then and now, the "signal"/reception on the phone (I use Vodafone, so coverage isn't spectacular anyway) has been awful - calls randomly dropping, and it just being unreliable and generally a pain. This is despite it being the supposedly "stable" channel, and the version being the same as the one I installed from nightly (previously). Maturing seemed to make the ROM more buggy, not less!
In the interests of having a working phone, I decided to leave CM. Atm, I'm going to try out an AOKP build - though officially unofficial, I'm hoping that minimalistic => less things to break. We'll see how it goes.
I've run various Google searches and the HOX+ finally seems to be getting (after nearly a year) a good developer community - with Lloir at the forefront of it, and Maxwen's blade kernel. Could anyone recommend a flexible, good looking, regularly updated ROM? I'm not a Sense fan (not long before rooting, Sense 5 came out, and it was "the straw that broke the camel's back" so to speak), but otherwise...I'm not really sure what I'm looking for. GPL would be good, and I'm a fan of minimalism (having as little clutter in the way of unused apps as possible). An active and engaged developer/dev community is a must - I don't want to install software that will become obsolete within a week, and have no prospect of a new release. Other than that, I'm more or less happy to try everything/anything!
Cheers,
AA.
PS - I should probably mention, although I'm in no way a dev, I am quite comfortable with tech, and don't mind spending a bit of time researching things to get stuff working. I'm a dedicated GNU/Linux user, and after a fair bit of distro-hopping I've come full circle to landing on Xubuntu. My view of my phone is basically a more awkward, more delicate version of my PC - the concept of "bricking" a computer is a joke, and I think until this possibility is 100% eliminated on phones, the developer community is always going to be slightly held back. I think the models used for developing Linux OSes could/should be applied to the ROM development process, too - as brilliant as the community is atm, it does have the "exclusive hacker culture" feel to it still.
The kernel didn't update because the device is s-on, also the call dropping bug, is you're problem no one else mentioned it. Just do research on the small amount of ROMs we got.
Sent from my Nexus 5 using Tapatalk
Lloir said:
The kernel didn't update because the device is s-on, also the call dropping bug, is you're problem no one else mentioned it. Just do research on the small amount of ROMs we got.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
How come you can be so sure of the cause? The 'symptom' must be relatively common, I suppose a bit like the technological equivalent of a headache and nausea.
The device is S-ON, you're right. I've read a little but I've not found anything specific to the UK about potential risks. You've got the same phone as me, and you're in the UK too, would you recommend going S-OFF? Does it cause problems with your carrier (I read somewhere that the manufacturer wasn't so bothered, but the carrier was - as it allowed the user to change certain things to do with the way the phone received carrier signal)?
Last bit on ROMs - I've read/seen quite a lot, but the information just isn't out there (unless you personally badger the devs, perhaps). The most official most ROMs get is a thread here. Compare that to (for instance) a Linux distro - you can more or less guarantee that if a distro is linked to on Distrowatch, it'll have it's own site, you can read up about source, included packages, what distinguishing features that OS has, what DE/package manager, etc. There's virtually no equivalent for phones - the best I've seen is xda's ROM listings under the device...if you're lucky one or two of the bigger ones (e.g. CM) will have it's own site. So, in lieu of that, I'm wanting to get a feel of what other users are doing, and what they'd recommend
ArminasAnarchy said:
Hi,
How come you can be so sure of the cause? The 'symptom' must be relatively common, I suppose a bit like the technological equivalent of a headache and nausea.
The device is S-ON, you're right. I've read a little but I've not found anything specific to the UK about potential risks. You've got the same phone as me, and you're in the UK too, would you recommend going S-OFF? Does it cause problems with your carrier (I read somewhere that the manufacturer wasn't so bothered, but the carrier was - as it allowed the user to change certain things to do with the way the phone received carrier signal)?
Last bit on ROMs - I've read/seen quite a lot, but the information just isn't out there (unless you personally badger the devs, perhaps). The most official most ROMs get is a thread here. Compare that to (for instance) a Linux distro - you can more or less guarantee that if a distro is linked to on Distrowatch, it'll have it's own site, you can read up about source, included packages, what distinguishing features that OS has, what DE/package manager, etc. There's virtually no equivalent for phones - the best I've seen is xda's ROM listings under the device...if you're lucky one or two of the bigger ones (e.g. CM) will have it's own site. So, in lieu of that, I'm wanting to get a feel of what other users are doing, and what they'd recommend
Click to expand...
Click to collapse
you cannot S-OFF the X+ currently, so i'm not going into that. Also you stated you flashed from CM10.1 > 10.2, which i assume was a dirty flash (no full wipe etc)
it's like installing the Arch + xubuntu on the same hard drive, which is bound to cause issues. So a full wipe was needed, as you should know "nightlies" are well nightlies, UNSTABLE
the closest we have to distrowatch are the rom reviews and so on. there's my PureAosp, AOSP+ both based on 4.3
CM as well you know what that is.
AOKP no longer supported but stable.
as "best rom" and so on are fround upon, due to the flame and chest beating and so on. which mean's you won't get a good answer tbh, and i'am quite impartial when it comes to rom's as i won't recommend anyone's rom's nor my own.
Lloir said:
you cannot S-OFF the X+ currently, so i'm not going into that. Also you stated you flashed from CM10.1 > 10.2, which i assume was a dirty flash (no full wipe etc)
it's like installing the Arch + xubuntu on the same hard drive, which is bound to cause issues. So a full wipe was needed, as you should know "nightlies" are well nightlies, UNSTABLE
the closest we have to distrowatch are the rom reviews and so on. there's my PureAosp, AOSP+ both based on 4.3
CM as well you know what that is.
AOKP no longer supported but stable.
as "best rom" and so on are fround upon, due to the flame and chest beating and so on. which mean's you won't get a good answer tbh, and i'am quite impartial when it comes to rom's as i won't recommend anyone's rom's nor my own.
Click to expand...
Click to collapse
First thing first, cheers for this man! It's good to be able to have a "conversation" with a dev - although Linux distros have got more infrastructure in place, there is a lack of 1:1 as a result (of having so many devs, etc).
It wasn't a dirty flash at all - every time I've written a new ROM I've wiped everything (or at least, ticked all the boxes in TWRP), then after reformatted - you can see the output of the 'make ext4fs' in front of your eyes. So unless it's that there's some partition which is write-protected (I assume the kernel is - since every time I've had to flash a new kernel - regardless of the wiping in TWRP, the phone just boot-loops without the kernel being flashed)...it's been clean.
I flashed 10.1 BEFORE it was in stable - so my phone was still pointing at the nightly repo (I guess?). GooManager pestered me into updating, and when I did, I ran into issues (presumably, the auto-update isn't intelligent enough to write a new kernel, and/or its in this write-protected partition which can't be accessed from the OS?)
It'd been a while since I'd put 10.1 on, and thought it'd be worth checking to see if it was in stable yet (it was). Did full wipe - as above - and then hit that annoying bug with call dropping. So I'd gone from being working on nightly to broken on stable. Time for a new ROM, methinks...looked around, and decide to post here.
As things stand I'm using AOKP (just because it was another popular ROM I knew, not really for any other reason). It's doing my head in though - either I'm being thick, or there's no option to edit settings in ANY app. I'm missing some of the gloss CM has too, things like it coming with a File Manager installed (why the hell would you not have one?!). From what you say, flashing 10.1 might be worth trying again...I'll go through from ground 0 and hopefully it won't break this time.
I get the thing with not wanting to advertise...so instead can I ask what you yourself use on your HOX+? Do you use it as a main phone, or is it just something you use for developing?
ArminasAnarchy said:
(presumably, the auto-update isn't intelligent enough to write a new kernel, and/or its in this write-protected partition which can't be accessed from the OS?)
I get the thing with not wanting to advertise...so instead can I ask what you yourself use on your HOX+? Do you use it as a main phone, or is it just something you use for developing?
Click to expand...
Click to collapse
you are right on point 1, it's in the write protected partition, and 2nd point, i tend to use my own rom's....i'am in the mindset, if i don't use my own rom's why should other people?
Lloir said:
you are right on point 1, it's in the write protected partition, and 2nd point, i tend to use my own rom's....i'am in the mindset, if i don't use my own rom's why should other people?
Click to expand...
Click to collapse
Haha, I see the logic!
Okay: so we've narrowed it down to a kernel issue. With my AOKP flash, what I did (blade wasn't for the right Android version I think) was extracted the .img file from the ROM.zip and flashed that.
With CM 10,1 (i.e. stable channel) - in your opinion would it be better to do the same, or use the blade kernel?
ArminasAnarchy said:
Haha, I see the logic!
Okay: so we've narrowed it down to a kernel issue. With my AOKP flash, what I did (blade wasn't for the right Android version I think) was extracted the .img file from the ROM.zip and flashed that.
With CM 10,1 (i.e. stable channel) - in your opinion would it be better to do the same, or use the blade kernel?
Click to expand...
Click to collapse
ALL my rom's are extract kernel from zip, i'am not sure what max did with his AOKP.....but 100% all mine you pull from zip and flash that
you can try the CM10.2 btw M1 not long ago released....just an idea..
Lloir said:
ALL my rom's are extract kernel from zip, i'am not sure what max did with his AOKP.....but 100% all mine you pull from zip and flash that
you can try the CM10.2 btw M1 not long ago released....just an idea..
Click to expand...
Click to collapse
Re-installed 10.1 (stable) again. Same issue, even though I've only had it running for 24 hours, it's dropped the call and didn't seem able to get 3G data (it was stuck at "E" for some reason, which makes doing anything impossible) despite being in the middle of the city and not near anything obvious that should block it like a huge block of flats etc.
I installed 10.2, we'll see how it goes.
Related
Hi guys,
I have one of the earliest retail models of the 10.1, 16GB Wifi. I'll be honest, I never got around to updating it from the original 3.0 release that it came with (before the TouchWiz stuff that Samsung added).
I'm not a heavy user of the tablet, but it rewarded me with stunning reliability -- it would run without needing a reboot for months at a time. However, it was needing a fresh start, so I figured I'd investigate the ICS ROMs available -- having a Galaxy Nexus as well, I really wanted to try ICS on a big screen.
Before we go further, I'm absolutely aware that none of the ICS are in any way official, that bugs are expected, and that there is no support. I'm absolutely not expecting a 100% reliable and functional build from any of these.
Anyway, I flashed the latest ClockworkMod recovery (5.5.0.4, from the dev forum), and proceeded to flash an ICS ROM. So far I have tried three different Kang CM9 ICS builds from various dates in March and February, as well as the 2nd March 'official' snapshot of CM9. In each case I did a data wipe, cache wipe, and dalvik wipe, followed by flashing the ROM, followed by flashing the GApps package.
Every version I've tried has booted up fine, been fully-functional bar the camera, and been a pleasure to use. Unfortunately, every version has been *incredibly* unstable. Typically the tablet will go to sleep and refuse to wake up with the power button, and feels warm on the back. Less often but still frequently, the tablet will simply freeze when interacting with it.
As I say, I'm aware that these things may happen, but to put this into perspective, I am unable to have the tablet booted up for more than 15-20 minutes before one of these situations will happen. In either case, the only way I've found to recover is to hold the power button down until it reboots. I have tried doing absolutely nothing other than completing initial setup (add Wifi details and Google account) and exactly the same thing happens -- this isn't due to any added applications.
Obviously, other people aren't seeing this extreme instability, so what have I done wrong? As said, the tablet was 100% reliable on 3.0, so I doubt this is a hardware issue. Does anyone have any other ideas?
Many thanks!
OK, after more testing, I've determined that it's not just ICS ROMs that are causing this. I tried CleanROM 1.3, an Android 3.2 ROM with the Samsung software removed, and experienced exactly the same problem -- inability to wake from sleep mode within a few minutes of booting, and the tablet getting warm.
However, I also tried the stock, but de-odexed/rooted 3.2 ROM from here, and this has been running for in excess of 12 hours without any issues whatsoever.
Both were flashed with the same version of CWM, so I think I can rule out a problem with flashing. So what else could be causing the tablet to freeze when using a non-stock ROM, but work when using a (largely) stock ROM? Any ideas?
Because both are based off AOKP ROM's, ICS builds , aka the nightly ones are based off these AOKP ROM's
ICS ROM's and Custom ROM's are built off AOKP rom's with what's been given by the source pack/drivers from Samsung to ensure that the cROM's are unique from one another, rather than the bulk of useless apps that the stock provides, developer's grab what they can from the source pack to improve and add what they want in their ROM. But grabbing files from the source package causes major instability only because Samsung won't be giving 100% of the original stable files, they give about 50% close to what seem's to be the original, but unstable when used, which is why they need to be worked on, this is just to avoid any GPL copyright or law's being broken or theft from other competetive companies.
Here's the best way to put it, when Google releases it, Android in general is open source, but Samsung's files aren't. Best way to put it is, me and you are in the same class, and we have been given a project by the class teach! I've already done mine, so best bet would be I fork it over to you so you can grab or copy as you may, but to avoid being caught or stating you copied, I try to give only what you can and hope you do the rest by yourself.
I hope this what your looking for
Same problem
I got the same problem.
Does anyone have a solution???
First, an explanation of my situation:
I bought a Galaxy Note at the beginning of the summer. All-in-all, I was pretty happy with it. It was a much improved experience over my Atrix, which was in poor condition by the time I switched over.
I wasn't able to root at first as I only had access to a Mac, and there were innumerable issues in doing so - Odin was PC only, WINE ports of it failed to recognize the phone, the Mac equivalent of Odin (I am spacing on its name right now) didn't work with the Note, etc.
When ICS was officially released, I tried to update to it via Kies. Kies on Mac is a ****storm. It's incredibly buggy, toolbars and menus don't display correctly, it has trouble recognizing the device, etc. I was unable to get it to make a backup, but I eventually managed to load the ROM onto it...
... and that's when the real problems started.
My battery life has turned to crap. Everything runs incredibly slow. Everything's super buggy. Apps force-close all the time. My MicroSD card ended up getting corrupted - half of my music disappeared, of what was left only 1/3rd actually worked. I just reformatted my MicroSD, backing everything important up, etc.
I've been dealing with this for around a month now, as whenever I come to the forum I have no idea where to even start to fix this. I'm up for wiping everything and starting over, and I do have access to a Windows XP machine now so that may be easier... but I don't even know where to go from there.
---------------------------------------------------
That's why I'm here - I need advice. I need advice as to how to clean up the current mess my phone has turned into and start over. I need advice as to what ROM to try and how to go about loading it. I need advice as to whether to root and how to do so. I need advice as to whether to install a CWM, which one to use and how to go about doing so.
Here is what I am looking for, ordered from most important to least:
Battery life is important to me. I loved how long the battery lasted before my attempted upgrade to ICS... now it lasts maybe 1/3 of the time.
I want something that will work - I want stability. No more constant force-quits of every freaking app.
A smooth, fast UI would be preferable.
Feature packed. I like the thought of cutting edge features of newer (or custom) versions of Android being incorporated - but this is far less important to me than battery life and stability.
My preferred method of installation would be using my Mac - but as I said, Windows XP is a very easy option for me as well. I could also install a newer version of Windows if need be, but would prefer not to go through that...
Thanks in advance for any help, advice and recommendations! ^_^
Get Odin and root your phone...
Download and flash TWRP... http://teamw.in/project/twrp
download a ROM of your choice
boot into the recovery ..wipe--->>cache/dalvik cache/ wipe ROM/factory reset..>then go to the install and flash your ROM...
These are very rudimentary instructions I hope they helped a bit...good luck
Do you have an idea for what ROM you like or want? Couple of great ROMs..for stockish check out flappjaxxx's for jellybean check out manelscout4life..stable and fast
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Techno is onto the correct answer, unless of course you are truly wanting the stock version back.
Kies and OTA updates are often flawed, and give the end user exactly the type of problems you are stating.
However, if you want a return to stock, the information can be found in the "note super everything thread" located as a sticky at the top of the general note section.
But I do agree with techno, that a root and flash of a quality custom rom is the way to go......g
Thanks a lot, both of you!
As to what ROM I want, honestly that's one of the reasons I have been procrastinating so much -- I have no idea whatsoever. There's such an overwhelming number of options out there, of basic flavors (ICS, JB, GB, CM7, etc.) and tens of derivatives of each one made by different people. I have no idea where to even start making such a decision.
I can tell you this much. On my Atrix, I started with the stock Motoblur-Froyo, flashed GingerBlur, disliked it's bugginess but dealt with it for almost a year, then flashed the CM7-based Neutrino. I wasn't very happy with how skimpy the ROM was but stuck with it until I got my Note. I was pretty satiated with the stock ROM, but decided to upgrade to ICS due to the promise of a better UI, increased functionality and especially a faster camera. While my experience with ICS was terrible, I could see myself enjoying a functional, non-buggy version...
Basically, I have no idea what ROM or even what base OS version I am looking for. That said, I do know the criteria that matter to me, as stated prior:
Battery Life
Stability
Smooth UI
Cutting-Edge Feature Packed
I can't really think of any features I am specifically looking for, other than under-the-radar tethering and top-notch camera speed & functionality .
As I have no attachment to any specific OS version, suppose that would mean that if battery life, stability and smoothness issues are equal amongst ROM variants, I would be looking for a Jellybean ROM - as it would be most packed with new features... right?
http://forum.xda-developers.com/showthread.php?t=1664980
That is the best stockish ICS experience you can get and keeps all the functionality of your phone including the spen. He also offers a jellybean ROM but honestly to find the best JB rom for you just read through the threads read and REREAD THE OP of those ROMs..jellybean is fun and cool but not 101% stable yet..people still getting random reboots and some are losing there APN settings..so maybe just flashing ics and playing with those ROMs is best for you for now..FYI the above rom is smooth as silk and great battery life
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Again , I agree with Techno, and the rom he posted is the one I'm using to type this.
Flappjaxxx is a fine developer, and he has packed this UCLF6 build with full functionality , and much more.
He is , and will continue to be my top pick for quality builds and performance ...g
This is all really wonderful advice - thanks again!
I guess I have a few last questions:
What is the best way to root at this point? If I recall, there are multiple ways to root via Odin... is there a specific one you would recommend for my current situation (read: current buggy ICS firmware)? A link would be very much appreciated, as the roadmap thread is a bit... overwhelming with all of the options.
Are there any MODs you recommend I install after I have my new flappjaxxx ROM in place? Will tethering work off the bat? Will all of the Gapps (Gmail, Navigation, etc.) be there for me to use? Will I need to install anything else, or is there any recommendations that you have?
Thanks again a ton - you've both been enormously helpful!
Also, I just noticed that the recovery you linked me to (http://teamw.in/project/twrp) has no option for the Galaxy Note...
EDIT: It turns out you linked me to the wrong page - to TWPR 1. Here's the link to TWRP 2.2, for anyone else who comes across this thread: http://teamw.in/project/twrp2
Just my 2 cents. After you get straightened out, you may want to take a look here.
http://forum.xda-developers.com/showthread.php?p=29376779
Another stable rom with great battery life, and a super Dev a well. I have been running it since testing and find it to be the perfect rom and team for me.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Okay ....
Please verify your carrier ....model ...and current software version ....then we can point you to the correct bits and pieces of the super thread.
I just want to make sure we are all on the same page ....g
Edit :
I'm away for a few hours ...
But I'm sure a few other helpful folks will chime in with the links ...g
phnord said:
Thanks a lot, both of you!
As to what ROM I want, honestly that's one of the reasons I have been procrastinating so much -- I have no idea whatsoever. There's such an overwhelming number of options out there, of basic flavors (ICS, JB, GB, CM7, etc.) and tens of derivatives of each one made by different people. I have no idea where to even start making such a decision.
I can tell you this much. On my Atrix, I started with the stock Motoblur-Froyo, flashed GingerBlur, disliked it's bugginess but dealt with it for almost a year, then flashed the CM7-based Neutrino. I wasn't very happy with how skimpy the ROM was but stuck with it until I got my Note. I was pretty satiated with the stock ROM, but decided to upgrade to ICS due to the promise of a better UI, increased functionality and especially a faster camera. While my experience with ICS was terrible, I could see myself enjoying a functional, non-buggy version...
Basically, I have no idea what ROM or even what base OS version I am looking for. That said, I do know the criteria that matter to me, as stated prior:
Battery Life
Stability
Smooth UI
Cutting-Edge Feature Packed
I can't really think of any features I am specifically looking for, other than under-the-radar tethering and top-notch camera speed & functionality .
As I have no attachment to any specific OS version, suppose that would mean that if battery life, stability and smoothness issues are equal amongst ROM variants, I would be looking for a Jellybean ROM - as it would be most packed with new features... right?
Click to expand...
Click to collapse
Im using black star v flawless in my eyes..
Sent from my SAMSUNG-SGH-I717 using xda premium
Wanted to get an idea from the group on options here:
Have seen quite a few postings on the issues with JB on the TF201 and how limited that makes things. Currently have a Gnexus phone running cyanogenmod 10 and really like it; started wondering what interesting features that rom might bring to the TF201.
So, first question is can any roms such as the CY10 even be installed given the JB limitations?
If so, are the benefits gained from custom roms worth whatever headaches are involved with the currently upgrade processes.
I am heading out on a deployment in about 6 days so access to pull down upgrade files will obviously be limited. Won't be returning to the US until the Sept timeframe, so definitely a needed decision on if anything can/should be done for improvements (to play with of course!) during the deployment.
I have the weekend to tinker but wanted to ask whether I'm better off just keeping the device as-is or putting in the time for possible upgrade steps.
Thanks!
militarymedic23 said:
Wanted to get an idea from the group on options here:
Have seen quite a few postings on the issues with JB on the TF201 and how limited that makes things. Currently have a Gnexus phone running cyanogenmod 10 and really like it; started wondering what interesting features that rom might bring to the TF201.
So, first question is can any roms such as the CY10 even be installed given the JB limitations?
If so, are the benefits gained from custom roms worth whatever headaches are involved with the currently upgrade processes.
I am heading out on a deployment in about 6 days so access to pull down upgrade files will obviously be limited. Won't be returning to the US until the Sept timeframe, so definitely a needed decision on if anything can/should be done for improvements (to play with of course!) during the deployment.
I have the weekend to tinker but wanted to ask whether I'm better off just keeping the device as-is or putting in the time for possible upgrade steps.
Thanks!
Click to expand...
Click to collapse
Hey militarymedic23,
There are definitely ROMs that can be installed currently, however most are unofficial ports from either a different device (TF700) or ported to the JellyBean bootloader (current OFFICIAL CM10 runs on ICS bootloader and will fail on updated JellyBean bootloader).
After experimenting with unofficial ports of CM10 (4.1), CM10.1 and JellyBeer (Android 4.2), I honestly recommend sticking to stock JellyBean as of right now. These ROMs, although offering a lot of customizations, are not "done" yet. There are many little bugs on each (ex: JellyBeer rom doesn't show dock battery, uses mobile mode aka. single pane, for play store, etc etc.) and although by itself doesn't take too much away from the experience, does tend to bother me over time.
It is these small bugs that I wouldn't recommend changing over from stock. A lot of the Asus features also missing (I really enjoy being able to change CPU modes from navigation menu-- which is a missing feature, for example). Also, assuming you already upgraded to the JellyBean bootloader, official CM10 ports DO NOT work, so you're getting unofficial ports.
Overall, I don't mind stock, and as long as you ROOT, you can go ahead and remove all the ASUS bloatware to get a pretty clean tablet experience. I also didn't find any performance enhancements after upgrading from stock (which I expected). I can include some pictures of stock vs unofficial CM10 benchmarks upon request.
My personal recommendation, due to the fact you will be deployed (so not sure if you'll have all the time to always flash the newest upgrades) is to continue with stock for now. The last thing you want is to be stuck with a buggy firmware without any way to update and restore. This way you can still receive OTA updates from Asus, which from my experience has been pretty timely (If you are out of the country, using an app like Hotspot Shield may help you get an OTA update if it isn't accessible from your current region).
Hope this helps.
Hi trophx, thanks for the input on this. I do agree that overall the stock software isn't actually that bad. In comparison to my phone, CM10 does give a nice assortment of features over the stock so I was thinking it might also do the same for the tablet. But for all of what I plan to be using the tablet for while deployed, keeping a stable release would eliminate one possible headache!
On a last note; I have seen other posts that mention some tablets have dropped by the wayside in terms of developers focusing on them vs the latest and greatest fresh meat hitting the market. Do you think the TF201 is among those tablets that probably won't be having things like CM written specifically for them?
Thanks again
militarymedic23 said:
Hi trophx, thanks for the input on this. I do agree that overall the stock software isn't actually that bad. In comparison to my phone, CM10 does give a nice assortment of features over the stock so I was thinking it might also do the same for the tablet. But for all of what I plan to be using the tablet for while deployed, keeping a stable release would eliminate one possible headache!
On a last note; I have seen other posts that mention some tablets have dropped by the wayside in terms of developers focusing on them vs the latest and greatest fresh meat hitting the market. Do you think the TF201 is among those tablets that probably won't be having things like CM written specifically for them?
Thanks again
Click to expand...
Click to collapse
The difference between the phone and THIS particular tablet is that the added dock functionality which is built into ASUS' stock firmware (which means support for a all dock keys-- screenshot, volume, brightness, lock, etc.--, USB, SDslot, etc.). This makes it different from almost all other tablets/phones in terms of how to get the best user experience. To address your point, the added functionality of CM10, for example, isn't THIS tablet specific, thus not as appealing in my opinion (just because of the instability of the build as of now). Although there definitely are a lot of added features-- very similar to all your phone features. But as I said before, I'd probably prefer stability over extra functionality at this time.
To your second point, I'm not sure. I certainly hope that development continues. On the plus side the similarity of this device to its siblings (tf300t and tf700) makes porting software across each device easier (One of the CM10 dev threads is a port from tf700). Currently CM does officially support the tf201, however, they haven't worked out the issues with the new JB bootloader, and doesn't seem to be too high on their priorities list. On another plus note, ASUS has been pretty quick about shipping out new firmware updates.
Hope this helps
I'd suggest Androwook 1.51. It's stock based so you get all the Asus compatibility with tweaks and performance out the @$$. It's definitely a lot better than stock and more stable/faster than AOSP based roms like CyanogenMod unofficial ports.
hmm, that androwook does look interesting. And you say that it pretty much adds to the base functionality without taking away any of the prime/keyboard specifics? I did a bit of searching on it and saw that many people like it and are awaiting 4.2 to be pushed out so the 1.51 -> 2.0 can go forward. Any rough timeline floating around on that?
Also, considering I will be overseas and on a limited connectivity basis, can anyone point out issues with 1.51 that would be a problem in this scenario?
Since my prime is completely untouched in the sense of no unlocking or rooting, is there a specific guide recommended, start to finish, for getting this loaded? Some of the articles I read seemed to expect a few steps to be done already. Messed around with my phone without too much problem but I get a bit edgy with wanting the exact process for the tf201. I bought it over a year ago now so the unlocking shouldn't be an issue with the one year warranty now expired, but I guess I'm more concerned on making sure I don't brick it!!! Currently use TWRP for my phone, and if that is installed on the tf201 would that allow a full restore back to the current image that is running right now (in case of whatever issue rendering it problematic)?
Thanks!
militarymedic23 said:
hmm, that androwook does look interesting. And you say that it pretty much adds to the base functionality without taking away any of the prime/keyboard specifics? I did a bit of searching on it and saw that many people like it and are awaiting 4.2 to be pushed out so the 1.51 -> 2.0 can go forward. Any rough timeline floating around on that?
Also, considering I will be overseas and on a limited connectivity basis, can anyone point out issues with 1.51 that would be a problem in this scenario?
Since my prime is completely untouched in the sense of no unlocking or rooting, is there a specific guide recommended, start to finish, for getting this loaded? Some of the articles I read seemed to expect a few steps to be done already. Messed around with my phone without too much problem but I get a bit edgy with wanting the exact process for the tf201. I bought it over a year ago now so the unlocking shouldn't be an issue with the one year warranty now expired, but I guess I'm more concerned on making sure I don't brick it!!! Currently use TWRP for my phone, and if that is installed on the tf201 would that allow a full restore back to the current image that is running right now (in case of whatever issue rendering it problematic)?
Thanks!
Click to expand...
Click to collapse
Yep-- for the most part. Since I don't believe you can use NVFlash (this can recover almost all bricks) on already Asus's OTA jelly bean bootloader, TWRP is next best option. I've been flashing and restoring and such for a few months now and no issues. Just be sure to READ very very carefully because the JB bootloader is very different from the ICS one, and (Cyanogenmod for example) some only support one-- installing the wrong one can brick your device permanently.
Ps. I don't want to seem like I'm recommending Stock over other roms in most scenarios, just in yours with limited connectivity, and I don't know how much time you'll have to mess around with a comp, and backing up your device and what not. I just think OTA updates from Asus is the easiest way to go.
**Androwook is extremely stable and super fast. It is exactly as McJesus15 said, based off Asus's rom-- I didn't know if you were asking about those too, because it doesn't offer the same tweaking and system settings CM10 or AOKP offer.
Hi guys, I'll throw in my 2 cents ... Mr medic u should unlock and flash Androwook. The McJesus poster above wrote a newbie guide that I followed and had success with, glitch free. I had been fully stock and read heaps before taking the plunge. You seem the type to read 1st act 2nd so ... no drawbacks. All Asus stock options remain available and Androwook uses an installer that gives you choices every step of the way.
Good luck.
Thanks for the additional feedback. Certainly am interested in the wooky version, but have a few questions on the process McJesus wrote.
An Unlocked Transformer Prime with a custom recovery and updated to the official JB bootloader..
NVflash installed if you want to go back to any other ROM not built on official JB. This is more a recommendation
Click to expand...
Click to collapse
The first would be an obvious download and run the unlocker (warranty buster) from Asus, and the second; that is more of an optional?
And per the instructions it seems once unlocked then doing the pwr_volume combo will allow the bootloader to see the SDcard contents of the wooky image?
Might be bordering on the paranoid level of doublechecking, but definitely can't afford to accidently brick this a day before shipping out!
Thanks!
militarymedic23 said:
Thanks for the additional feedback. Certainly am interested in the wooky version, but have a few questions on the process McJesus wrote.
The first would be an obvious download and run the unlocker (warranty buster) from Asus, and the second; that is more of an optional?
And per the instructions it seems once unlocked then doing the pwr_volume combo will allow the bootloader to see the SDcard contents of the wooky image?
Might be bordering on the paranoid level of doublechecking, but definitely can't afford to accidently brick this a day before shipping out!
Thanks!
Click to expand...
Click to collapse
Alright I'll take care of ya before you ship out. Good luck and God bless you.
NVflash is a utility that can only be used while you are on Ice Cream Sandwich. Since you are on Jelly Bean there is currently no way to do the process.
Unlocking your Prime is easy. Just use the app provided on the Asus website. Understand that your warranty is now void (not like Asus intended to do much for you anyways). Once you are unlocked use the automated utility in my guide to easily flash TWRP. It's not the latest version but I haven't had time to update my post. It's perfectly fine for your uses.
Once that's done just flash Androwook either by putting the .zip file on an external SD card or the internal storage of the Prime. Once you begin the process and start selecting options the rom is basically totally customizable for you. One suggestion I will make is when selecting the kernel go with Clemsyn's 1.7ghz custom kernel as it literally is the biggest performance boost you could possibly do for your Transformer Prime. If you need any help you can message me privately or ask in the Androwook thread. The guys there are genius's. Hope we helped you get your Prime in working order before you deploy.
Oh, also, when you first boot into recovery I suggest making a back up immediately. Always have a back up handy and I personally keep 2-3 rom zips on my Prime for the SHTF moment.
Thank you!
I actually started tinkering around with the unlocker just before you posted. Unlocked it fine, and put TWRP on it and did a full backup of stock. I did pull down the 1.51 wooky image and put it on. I guess after working with CM10 I was expecting all the fancy changes but so far I can't tell the difference between stock and androwook.
I did also try and put the Wooky Prime 2.1 image but the tablet would just sit on the asus logo and not go anywhere. Can you advise what major differences should be noticed between 1.51 and prime 2.1?
Thanks
militarymedic23 said:
Thank you!
I actually started tinkering around with the unlocker just before you posted. Unlocked it fine, and put TWRP on it and did a full backup of stock. I did pull down the 1.51 wooky image and put it on. I guess after working with CM10 I was expecting all the fancy changes but so far I can't tell the difference between stock and androwook.
I did also try and put the Wooky Prime 2.1 image but the tablet would just sit on the asus logo and not go anywhere. Can you advise what major differences should be noticed between 1.51 and prime 2.1?
Thanks
Click to expand...
Click to collapse
Wooky Prime 2.1???
oh I have to laugh at myself sometimes
Androwook Prime 2.1
militarymedic23 said:
oh I have to laugh at myself sometimes
Androwook Prime 2.1
Click to expand...
Click to collapse
I'm still not getting where you are seeing 2.1. Can you link me please.
it was buried fairly well, but here is the link:
http://www.teambamf.net/topic/3986-rom040712-androwook-prime-v21-complete-rom-customization/
militarymedic23 said:
it was buried fairly well, but here is the link:
http://www.teambamf.net/topic/3986-rom040712-androwook-prime-v21-complete-rom-customization/
Click to expand...
Click to collapse
Ahh, sorry mate but that is really old. That was when the rom was based on ICS. When it turned to jellybean it became hairybean and went back to version 1.
1.51 is the latest.
oh, no worries though. Since it was hanging at startup I went back to 1.51.
Is there a rough rumor when JB 4.2 might be coming out and HB goes up a version? It will of course be while I'm away but if I know a general date then I can try and watch for it.
militarymedic23 said:
oh, no worries though. Since it was hanging at startup I went back to 1.51.
Is there a rough rumor when JB 4.2 might be coming out and HB goes up a version? It will of course be while I'm away but if I know a general date then I can try and watch for it.
Click to expand...
Click to collapse
Someone correct me if I'm wrong but I believe the AndroWook rom is based of OTA releases from Asus, so it probably won't have JB 4.2 unless something along those lines comes out.
of course but I was just curious if anyone has heard if a major version change or new version of android scheduled to be released in the next 6 months.
militarymedic23 said:
of course but I was just curious if anyone has heard if a major version change or new version of android scheduled to be released in the next 6 months.
Click to expand...
Click to collapse
Oh no idea-- Asus said they would be supporting 4.2 back in November, but it'll probably take a bit. It isn't a Nexus after all. But so far I've been pretty satisfied with their software updates in terms of speed of release and quantity.
I'm considering putting a ROM on a friend's device that is not familiar with any sort of troubleshooting but is a reasonable upgrade over stock. If that's not possible I'm fine with that. No bugs preferred. Features aren't that important but the phone lags a lot stock so a speed boost would be nice.
Thanks!
Action B said:
I'm considering putting a ROM on a friend's device that is not familiar with any sort of troubleshooting but is a reasonable upgrade over stock. If that's not possible I'm fine with that. No bugs preferred. Features aren't that important but the phone lags a lot stock so a speed boost would be nice.
Thanks!
Click to expand...
Click to collapse
I typically refrain from "advertising" (even in my own thread - hah) since there are many many fine works to choose from out here crafted by a lot of very dedicated and amazing developers, but in this case I think I'll break my rule and see if my ROM would fit your needs:
http://forum.xda-developers.com/showthread.php?t=2088224
My ROM is pretty basic, it tries to mimick the AOSP/Galaxy Nexus as best as possible for the Fascinate, with only a few customizations. I can't say it's 100% bug free, that would be silly (lol), but the latest version (GeeWiz 4.4 + 2 patches) is very solid/stable in my opinion. I think it's a good fit here since it can be applied as a direct stock replacement using ODIN and doesn't change anything that would cause problems going back to stock again if it's not what your friend was expecting.
I'm not sure the "speed" will impress, but it does pretty well considering it's Jelly Bean 4.2 running on a device that came with Eclair :silly: There are some built-in optimizations you can enable like overclocking the CPU to 1.2GHz that help smooth it out, and I've done a lot of work on the kernel to ensure as little wasted CPU % as possible. Battery life will also be less impressive than your friend is used to on stock, but again I think it's pretty darn good given that we are well beyond what the Fascinate was designed for at this point!
If you want a mildly enhanced Gingerbread experience, you can also try my GeeWiz v2.9.2 here at XDA. It's retired and I no longer actively work on it, but it still gets THOUSANDS of downloads every month (admittedly mostly from China and parts of Africa, I've chosen to not try to understand why - lol).
I don't want to drone on, but I want to add something else ... ANY of the ROMs out here should blow your friend's mind! I only recommend my own because it sounds like a good fit for your needs and could be an easier sell for you since it strives for a stock-like experience. Every dev out here is friendly and will help you if you run into problems, so perhaps the best way to go is peruse the selection in the development thread and see what you think! There are really no "bad" choices to be made here.
I'm impressed how helpful you are. How much difference in battery life are we talking here? I put a jellybean rom on my galaxy tab 7 and it lasts for a month easy on standby, so I know it can vary greatly with custom ROMs.
djp952 said:
I typically refrain from "advertising" (even in my own thread - hah) since there are many many fine works to choose from out here crafted by a lot of very dedicated and amazing developers, but in this case I think I'll break my rule and see if my ROM would fit your needs:
http://forum.xda-developers.com/showthread.php?t=2088224
My ROM is pretty basic, it tries to mimick the AOSP/Galaxy Nexus as best as possible for the Fascinate, with only a few customizations. I can't say it's 100% bug free, that would be silly (lol), but the latest version (GeeWiz 4.4 + 2 patches) is very solid/stable in my opinion. I think it's a good fit here since it can be applied as a direct stock replacement using ODIN and doesn't change anything that would cause problems going back to stock again if it's not what your friend was expecting.
I'm not sure the "speed" will impress, but it does pretty well considering it's Jelly Bean 4.2 running on a device that came with Eclair :silly: There are some built-in optimizations you can enable like overclocking the CPU to 1.2GHz that help smooth it out, and I've done a lot of work on the kernel to ensure as little wasted CPU % as possible. Battery life will also be less impressive than your friend is used to on stock, but again I think it's pretty darn good given that we are well beyond what the Fascinate was designed for at this point!
If you want a mildly enhanced Gingerbread experience, you can also try my GeeWiz v2.9.2 here at XDA. It's retired and I no longer actively work on it, but it still gets THOUSANDS of downloads every month (admittedly mostly from China and parts of Africa, I've chosen to not try to understand why - lol).
I don't want to drone on, but I want to add something else ... ANY of the ROMs out here should blow your friend's mind! I only recommend my own because it sounds like a good fit for your needs and could be an easier sell for you since it strives for a stock-like experience. Every dev out here is friendly and will help you if you run into problems, so perhaps the best way to go is peruse the selection in the development thread and see what you think! There are really no "bad" choices to be made here.
Click to expand...
Click to collapse
Action B said:
I'm impressed how helpful you are. How much difference in battery life are we talking here? I put a jellybean rom on my galaxy tab 7 and it lasts for a month easy on standby, so I know it can vary greatly with custom ROMs.
Click to expand...
Click to collapse
Ugh, that's always a tough one to answer Maybe 10%-15%? It's really hard to say since it depends on how the device is used. Some stuff like active Bluetooth definitely takes more juice, whereas Wifi takes less. The screen takes more since JB requires the kernel to maintain a VSYNC (Vertical Sync) signal and it will enable the accelerometer device whenever the screen is on for auto-rotation support (if you turn off auto-rotate it's smart enough to disable the accelerometer). Pretty much anything you actively do with the device will require more battery than it did, there's lots more code in JB, fancier graphics to animate, etc.
There is also one application, Google Play Music, that I have listed as a "Known Issue" when it comes to battery life. For some reason/bug in it's album art downloader, it can get itself stuck in a loop and trash the battery in a matter of hours. I tracked it down to the mentioned album art service when an external SD card is installed, and told Google, but that's all I could do for that. I recommend disabling Google Play Music and replacing it with a better music player!
I wish I had a more concrete answer for this one, but "it depends" is about as good as I can do. If your friend is getting well more than a day out of the phone now, he should probably be OK if charging every night is acceptable. If he's already battery-challenged, I think it may be a frustrating experience for him.
For what it's worth, here are the most two recent battery life screenshots I have. Note: These are with a brand new battery ($14 - amazon) and really only show standby with Wifi ON times, which is what I was testing. Basically indicative of the absolute maximum battery life possible, not real world usage.
Hope this was enough to help with your decision!
Geewiz is probably the most stable by far great battery life and as you can see great developer
Sent from my SCH-I500 using Tapatalk 2
There are so many recommended ROMs now, it almost seems like too many choices. (It's a good "problem". I'm not complaining.) I tend to find one based on reviews and recommendations and stick with it, rather than flashing through a bunch. I've been using MIUI from GB to JB, but sadly development seems to have ceased.
I had been eyeing Stephen.k.spear's AOKP PUB as a replacement, but development seems to have ceased there as well. Looks like the torch was picked up by bbrad's AOKP, but browsing that thread opened the floodgates to other ROMs such as Liquidsmooth, Carbonrom, SuperNexus, etc, etc, etc, as well as Geewiz mentioned here. Can anyone provide an overview comparison (stability, features, other pros/cons...) between some of these ROMs? (What exactly is the difference in stability of "by far"?)
Also, at some point around ICS, there was a change in file system and/or structure that allowed MIUI to hold a lot more apps than previously. (I think it had to do with MTD, but not 100% sure.) Can I assume most ROM's have this expanded capability now? Does Geewiz have it? I noticed it uses a different file system. Thank you.
I am one of those people who really likes a stable rom and I would really recommend you try Helly Bean. It's been by far the most stable and feature packed rom I've ever used. I'm not trashing any of the other roms we have, but I've tried almost all of them and I always come back to Helly Bean.
Crawshayi said:
I am one of those people who really likes a stable rom and I would really recommend you try Helly Bean. It's been by far the most stable and feature packed rom I've ever used. I'm not trashing any of the other roms we have, but I've tried almost all of them and I always come back to Helly Bean.
Click to expand...
Click to collapse
Unfortunately I can't ask in the ROM thread, so I'll ask here... Which version of gapps do I flash for Helly Bean? The thread points to 20121130, but there seems to be a more recent version 20130301 at goo.im. Also, droidstyle's guide mentions inverted gapps. Does that work with Helly Bean? If so, are they flashed after the regular gapps, or instead of them? Thanks so much.
donkeyhaughty said:
Unfortunately I can't ask in the ROM thread, so I'll ask here... Which version of gapps do I flash for Helly Bean? The thread points to 20121130, but there seems to be a more recent version 20130301 at goo.im. Also, droidstyle's guide mentions inverted gapps. Does that work with Helly Bean? If so, are they flashed after the regular gapps, or instead of them? Thanks so much.
Click to expand...
Click to collapse
Flash the ones from goo.im and as for the inverted you just flash them like regular gapps
Sent from my SCH-I500 using Tapatalk 2
While cleaning the garage, I found my wife's old nook BNTV250. She said I could have it. So, I've been trying to get a custom rom on there.
I have experience with custom roms. I have a Samsung Galaxy Note 2 running Philz and Lollipop as well as a Note 10.1 running TWRP and Kitkat. So, I have experience with successfully installing recoveries and flashing custom roms to devices.
This one isn't as easy for some reason.
I can get a rooted stock rom by following the directions here...
https://www.youtube.com/watch?v=hZyfWpBJpiE
but no matter what I try, I can't get any further than that.
When I tried to sign in with the google play store, I am told my password is bad (which it isn't). Then I get an email from google in my gmail account telling me that someone (which was me) has tried to sign in to my account but was denied because the device they were using is way too old. So, getting anything on to my device via the play store that I need, such as a terminal emulator, TWRP install, etc, is apparently out of the questions.
gapps won't flash without errors, so that is out of the question, too.
the included es file explorer won't see the internal SD card for a reason I haven't been able to figure out (yes, it has root access), so copying apk files over and installing them from there is out.
When I boot off of ann sd card, and attempt to flash custom recoveries from the internal storage, I am also unsuccessful. With TWRP, I get errors. With CWM, it says it was successful, but it isn't.
So, every road I go down to get CM on this thing is blocked.
Am I missing something, or did I just miss my window by not doing this two years ago?
xflbret said:
While cleaning the garage, I found my wife's old nook BNTV250. She said I could have it. So, I've been trying to get a custom rom on there.
Am I missing something, or did I just miss my window by not doing this two years ago?
Click to expand...
Click to collapse
Try:
1. A factory reset
2. The instructions here---they worked for me as a noob.
That could leave you with CM 10.2. If you'd like something higher, this post might send you in the right direction after you succeed with CM 10.x, but it does become more complicated. Or you can just try to get there directly.
It can't be too late:fingers-crossed: There's life in that tablet yet!
Edit: I see that the CM 10.2 build is no longer posted over at Cyanogenmod. If you want to try it, let me know. I have the zip file.
Sorry, I haven't posted my update yet. I managed to find a solution to the problem with the included es file explorer. That allowed me to install some apk's like terminal emulator which allowed me to get TWRP on, and then the figurative flood gates were open from there.
I am disappointed. I flashed both liquid smooth kitkat, and a lollipop build. Neither are very responsive, and both seem to have great difficulties awakening from a sleeping state (the lollipop one was worse). I looked around, but couldn't find a kernel to flash. Is there a kernel we should be using to speed up these roms? If not, I think I will give up because I stand stand the slowness.
xflbret said:
Sorry, I haven't posted my update yet. I managed to find a solution to the problem with the included es file explorer. That allowed me to install some apk's like terminal emulator which allowed me to get TWRP on, and then the figurative flood gates were open from there.
I am disappointed. I flashed both liquid smooth kitkat, and a lollipop build. Neither are very responsive, and both seem to have great difficulties awakening from a sleeping state (the lollipop one was worse). I looked around, but couldn't find a kernel to flash. Is there a kernel we should be using to speed up these roms? If not, I think I will give up because I stand stand the slowness.
Click to expand...
Click to collapse
I read through some CM11 threads and was amazed at the different experiences people had, ranging from "works great" to "really sluggish". Speaking only from a logical perspective it seems to me that the more advanced OS you try to shoe-horn into an older device, the more likely you will exhaust (or at least severely task) its hardware resources. Like trying to install Windows 10 on a machine designed for XP with hardware that just barely meets the minimum requirements of Win 10.
All I can say is that CM 10.2 works "great" on my NT. I've yet to encounter an app that I wanted which would not run (of course, my wants may not match yours). I can read the newspaper, listen to music, Kodi runs great--I can even stream a video from the NT to my TV (which has an old laptop connected) using VLCDirect. So lots of life in the thing from my perspective. CM 10.2 does get cranky once in awhile, but a reboot sorts that out. I expect many newer tablets are the same in that respect.
Let me know if you change your mind and want to try CM10.2
nmyshkin said:
I read through some CM11 threads and was amazed at the different experiences people had, ranging from "works great" to "really sluggish". Speaking only from a logical perspective it seems to me that the more advanced OS you try to shoe-horn into an older device, the more likely you will exhaust (or at least severely task) its hardware resources. Like trying to install Windows 10 on a machine designed for XP with hardware that just barely meets the minimum requirements of Win 10.
All I can say is that CM 10.2 works "great" on my NT. I've yet to encounter an app that I wanted which would not run (of course, my wants may not match yours). I can read the newspaper, listen to music, Kodi runs great--I can even stream a video from the NT to my TV (which has an old laptop connected) using VLCDirect. So lots of life in the thing from my perspective. CM 10.2 does get cranky once in awhile, but a reboot sorts that out. I expect many newer tablets are the same in that respect.
Let me know if you change your mind and want to try CM10.2
Click to expand...
Click to collapse
You talked me into it. I'll give 10.2 a shot. I'm assuming that's based on Jellybean. I think every app I want to use will still work on Jellybean.
Any recommended builds? Any recommended gapps?
xflbret said:
You talked me into it. I'll give 10.2 a shot. I'm assuming that's based on Jellybean. I think every app I want to use will still work on Jellybean.
Any recommended builds? Any recommended gapps?
Click to expand...
Click to collapse
I finally located the 10.x downloads here. I'm using the last stable build, 10.2.1 (Android equivalent 4.3.1). You should use the gapps package that is listed for 10.2 build here.
Like I said in an earlier post, I followed the excellent directions from digixmax here and while the initial boot was kind of confusing, things did sort themselves out. But that method assumes you are starting from stock. If you can't get back to there you'll need to try something else.
Once in a blue moon some app in the PlayStore will be listed as incompatible, I guess because Google can't quite figure out what to make of these modded tablets, even though the Android version is well within reach of CM 10.2. That happened recently to me with my local newspaper app. I just used this site to download the app outside the PlayStore and then side-loaded it. It installed and works just fine.
Good luck! I hope this all works to your satisfaction
Well, I installed CM 10.2. Everything works, albiet VERY slowly. I'm going to go google for a kernel now so I can do some overclocking. If I can't find one, then I'm afraid I'll have to let this go. It is just too slow and unresponsive the way it is to be productive.
xflbret said:
Well, I installed CM 10.2. Everything works, albiet VERY slowly. I'm going to go google for a kernel now so I can do some overclocking. If I can't find one, then I'm afraid I'll have to let this go. It is just too slow and unresponsive the way it is to be productive.
Click to expand...
Click to collapse
Sorry it didn't work out well for you. It's obvious to say, but either there is a hardware issue or something did not go right in the flashing. Otherwise no one would bother with these things.
You've probably already looked at this, but just in case, under Settings/Performance/Processor I show a resting CPU freq. of 300 MHz, the governor set at "interactive, and a max. CPU freq. of 1008 MHz. Theoretically you could try playing with those if you have the same figures, but I'm not sure where that would take you.
The only custom kernel I could find for this was for KitKat, so I reflashed with that. I clocked both the minimum and the maximum to 1200 MHz. Even at that, my Antutu benchmarks score was just under 14k, or less than half of the score for my Samsung Galaxy Note 2. I never got "great" results with this device so far, but the KK with the custom kernel is the best I have got so far. I'm tempted to try this KK kernel with the lollipop build to see what happens. If I do that, I'll report my results.
This device is over four years old now. Add to this that, at the time, it wasn't exactly designed to break any speed records. All it was intended to do is read ebooks, and play a few other select apps. No GPS, no bluetooth. I guess asking it to run today's resource intense apps like Facebook may be asking too much of it. But, for some weird reason, I can't let this go now. It is kind of like an electronic pet to me. I keep it by my easy chair, and I pick it up and start doing something with it quite often.
Yeah, I was just getting ready to point you toward the kernal for CM 11 but you got there without my direction.
It's really puzzling to me that your system seems so slow. Maybe mine is too! I've never owned a tablet before (I don't count my much-modded NST e-ink reader!) and this one running CM 10.2 seems just fine to me, certainly no worse than laptops I often work with. I have an inexpensive LG smartphone I just bought to use as an mp3 player after my much-loved Insignia Pilot finally died. It runs KitKat and seems about as responsive as my Nook Tablet, maybe slightly better, so I guess a lot is what we are used to.