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???
I'm running MIUI ROM from Th3Bill and loving it (thanks Th3Bill!), the latest release (.29) has transformed my phone - again.
I just have a question though.
I notice the bill releases lots of JB roms (AOKP, Paranoid Android, CNA, MIUI)..
I'm uncertain as to the difference between all of these.
do any work better or worse on the atrix 4g?
Don't get me wrong i'm not doubting TheBill for one microsecond, but am just curious as to why so many roms would be released by one person unless they have some difference between them, or is it just a different look and feel?
I guess i'm just wanting the best JB experience i can get with the ROMS currently available, and short of 'just trying them all', well. i took the lazy route and posted here to ask what fundamental differences there are to an end user perspective.
i understand the underlying release may have features which do not work with the atrix (cam/fp-sensor/tether) and this will be comon accross all ROMS using this underlying release.
thanks.
Gavin.
Best thing to do is probably use each for a day and see which ones have the features you like/need.
I haven't tried cna or pa yet, so I can't comment on their stability. I think since they are all based off the same cm10 that their issues (beyond the common issues of all the roms) are upstream. For example, I don't think any of the roms have camcorder 100 percent working, or native wifi hot spot. The individual roms probably have some smaller bugs that are upstream of th3Bill's work, like I said.
Here's a rough breakdown: miui is very themed/themeable and has some custom features like a cool lock screen, sms pop ups,... You probably know miui already, since you are on it. It's the most different from the rest.
Paranoid android specializes in tabet/phone hybrid ui, tweaking dpi for individual apps without reboot (I think)
Cna is the only jb rom (I think) that has custom lock screen targets yet. I don't know much about it other than that.
I'm on aokp, and I really like it. I like the notification toggles with a brightness bar underneath, and I like the rest of the systemui tweaks.
People can add to this, or correct me if I'm wrong about any of it.
Unfortunately it's a bit time consuming to set up a new rom every day, but there is only 4, so I'm sure you can find the time.... At some point.
I hope that helps a tiny bit. I'm still exploring them myself =)
Sent from my MB860 using xda app-developers app
Thanks for the quick and detailed reply.
Trust me to chose the 'most different' ROM (MIUI)
This is good information to have thank you, and gives me some comfort that i'm not missing out on anything, also that just trying each rom for a day or two is the way to do it.
Cheers for your help, although as my phone is a daily runner, i'll probably stick with what i know now (MIUI).
I may find a cheep atrix to try loading other roms onto soon and perhaps be adventurous with trying other roms on that.
many thanks
Gavin
Miui is definitely my favorite but it feels a little heavy/less responsive compared to aokp/cm10.
I can't comment on cna, or pa because I've never used them.
Aokp/cm10 are great. Fast and smooth and a few of the paid themes lurking around the play store are absolutely stunning, Dream, Lucid, PopStyle all amazing. I use Aokp because of it advanced visual preferences like centered clock, weather under toggles, sliders, lock screen tweaks, on screen nav buttons, stuff like that
Sent from my MB860 using Tapatalk 2
I need my phone during the week too, so I usually try one out over the weekend. I definitely can't keep up with th3bill like that hah
Epinter
I´m using Epinter´s CM10 and I´m loving it. I find it very fast and my battery last all day.
I´ve tried MIUI and personally is the one I like the least. AOKP is good also, but not as good as Epinter.
I tried JB roms and my first ROM was CNA. But the provided build during my install had issues and Bill said he might take couple more days. Since it was more related to emails, i have to switch back to other ROM and switched to epinter.
I am on epinter CM10 and its i like it. But even in this ROM, i am having issues with apps like shopkicks not getting loaded.
And few times, when i launch four square app, i will see like slanting colored lines until i reboot.
Also rarely WiFi issues it wont connect and even not possible to disable Wifi until reboot.
But Battery wise i get nearly 1.5 to 2 days with regular use of browsing, 2 emails , texting and phonecalls.
I have tried all JB roms for the AT&T Samsung Note 1. Now I am currently running Collective. I have over the past 5 months read through all their Forums and troubleshooting and have followed all instructions to the T. I wont be bashed or called a noob because all phones are not alike and some users don't have certain issues from what I read. BUT others have most definitely had my issues lol. I get random reboots, also seems like phone does not update properly like updates for apps through play store. I reboot my phone and all of a sudden i get new emails and there's 5 updates where my phone while on told me nothing about them. The reboots are the bigger issue. Is there no Stable JB rom out there? I keep being told go back to ICS, which I am believing that after JB being out for so long nobody is able to make the roms stable. Never seen such a long period of no stable rom coming out for a phone. Appreciate any advice ty
Hmm, there is two that I know of now. Cyanogen mod 10, and paranoid android which has cm10 as a base
Sent from my SAMSUNG-SGH-I717 using xda premium
Korvan30 said:
I have tried all JB roms for the AT&T Samsung Note 1. Now I am currently running Collective. I have over the past 5 months read through all their Forums and troubleshooting and have followed all instructions to the T. I wont be bashed or called a noob because all phones are not alike and some users don't have certain issues from what I read. BUT others have most definitely had my issues lol. I get random reboots, also seems like phone does not update properly like updates for apps through play store. I reboot my phone and all of a sudden i get new emails and there's 5 updates where my phone while on told me nothing about them. The reboots are the bigger issue. Is there no Stable JB rom out there? I keep being told go back to ICS, which I am believing that after JB being out for so long nobody is able to make the roms stable. Never seen such a long period of no stable rom coming out for a phone. Appreciate any advice ty
Click to expand...
Click to collapse
My first experience with CM10 was that it was not stable, especially coming from CM9 which was rock solid but the last week or so of builds have performed very well for me. Within the last week my phone has rebooted 2x's on me. Both were just as I hung up a call the screen froze then the phone rebooted. Otherwise, I have not had any issues. My previous ROM was JellyBeer which as not quite as stable but still pretty good. I did clean wipes, loaded CM10 (latest) then JB GAPPS 20121011. After rebooting the phone I run "fix permissions" from CWM. I go to the play store and download my apps from there and not from a back up. Hope this helps, good luck.
Korvan30 said:
I have tried all JB roms for the AT&T Samsung Note 1. Now I am currently running Collective. I have over the past 5 months read through all their Forums and troubleshooting and have followed all instructions to the T. I wont be bashed or called a noob because all phones are not alike and some users don't have certain issues from what I read. BUT others have most definitely had my issues lol. I get random reboots, also seems like phone does not update properly like updates for apps through play store. I reboot my phone and all of a sudden i get new emails and there's 5 updates where my phone while on told me nothing about them. The reboots are the bigger issue. Is there no Stable JB rom out there? I keep being told go back to ICS, which I am believing that after JB being out for so long nobody is able to make the roms stable. Never seen such a long period of no stable rom coming out for a phone. Appreciate any advice ty
Click to expand...
Click to collapse
You must be ON CRACK? The PAC MAN rom is the most stable rom i have ever ran.... and i've tried them all. NO random reboots and no issues. give it a shot man
Isn't the cm10 Jellybean kernel for the note just a modified ICS Kernel with bits and pieces from other kernels put in one package in order to run Jellybean. There's the stability issue. There's no source for the GN Jb kernel yet so they'll be issues. In my experience reboots and lost data connection. That's why I went back to ICS. Everything works. But I would like to check out Paranoid Android 3.0 ,4.2 aospa builds coming out soon. Don't know if there using a cm kernel or in-house built.
Novena injected I717 Samsung Galaxy Note
Nov 8 PA and linero (pacman) kernel and only get a reboot one every 5-7 days . Were on all others was like 3-4 a day . Also I have found (I could be crazy) but when a reboot yellow screen of death occurs power off the phone then restart seems to stop the reboots for much longer ,not that I need to do it anymore.
darkchyldx101 said:
Isn't the cm10 Jellybean kernel for the note just a modified ICS Kernel with bits and pieces from other kernels put in one package in order to run Jellybean. There's the stability issue. There's no source for the GN Jb kernel yet so they'll be issues. In my experience reboots and lost data connection. That's why I went back to ICS. Everything works. But I would like to check out Paranoid Android 3.0 ,4.2 aospa builds coming out soon. Don't know if there using a cm kernel or in-house built.
Novena injected I717 Samsung Galaxy Note
Click to expand...
Click to collapse
DING DING DING!!!
No source, mo' problems!
We need source to drop for JB, especially the kernel source...
Until then, we can get "good" builds, but not "Great" builds...
Source is the key, and according to Samsung, the note will get the official upgrade in december...I dont know more than that.....g
so was there ever a great 4.04 aosp or aokp rom for the i717??
by great i mean everything working.. hdmi, usb otg, etc...
on the s2 it seemed that as soon as the source dropped everyone went to jellybean..
so there never was a near flawless build.. and there never were sources for the hdmi and some other drivers..
i dont see it being different on any samsung product..
See this is why I made this thread. Simply put I spend countless hours searching threads and topics and I jsut got 90% of my answers there. I have used cm Roms in the past and I liked them. I am not a expert at rooting but one gets there over time. I really do not think any question is a stupid one but where it posted can be wrong place to post. I do very much appreciate everything everyone has posted. If you have any other imput or great ideas please post. Again ty very much:good:
THE most important thing to remember is that no 2 phones will act the same on every ROM, so, anytime someone says a certain rom is great, or another one sucks, you can only take that with a grain of sand....the ONLY way to know how any rom will run for you is to install it on YOUR phone.
As others have said, until there is source from Samsung, NO JB rom will run perfectly 100% of the time for everyone, so, if you don't want to deal with the possibility of reboots or other weird issues, you are probably best sticking with an ICS rom...
Actually, I have found the JB's to be more stable than the ICS Roms. I have found AOKP Milestone 1 the most stable. No reboots and offers tabletUI if you want it.
Right now, I am running Dman's PACman and find it to be very smooth and stable.
Sent from my Nexus 7 using xda app-developers app
I have been using AOKP Milestone 1 and haven't had many issues. There are a few bugs but nothing show stopping. I run mine at 240DPI and it looks beautiful and have only had 1 reboot. I would give it a try.
On crack lol appropriate but ok. I tried pacman at one point I loved all roms but no phones are equal ever jb rom at some point gave me reboots. Sporting padawan at the moment loving it
Sent from my SAMSUNG-SGH-I717 using xda premium
Hey people... I myself own a 312 model and love the thing to pieces. The first thing i did was get my precious root.
Right now I am reading up on the ROM releases and just dont know if I want to continue modifying or to wait.
I own a galaxy note... so i know all about flashing different roms... but my experience is usually the same with every rom.
Day one... yay... it works flawless. Day two... runs ok... then by the time a week goes by the thing just reboots so often that i get pissed off and flash something else.
So my question is what rom/kernel are people using... how long have you been using it... and how stable has it been?
KanjiMan1977 said:
Hey people... I myself own a 312 model and love the thing to pieces. The first thing i did was get my precious root.
Right now I am reading up on the ROM releases and just dont know if I want to continue modifying or to wait.
I own a galaxy note... so i know all about flashing different roms... but my experience is usually the same with every rom.
Day one... yay... it works flawless. Day two... runs ok... then by the time a week goes by the thing just reboots so often that i get pissed off and flash something else.
So my question is what rom/kernel are people using... how long have you been using it... and how stable has it been?
Click to expand...
Click to collapse
Went from 4.1.2 to 4.2.2 and was shocked by the phablet UI and the loss of usefull screen. That's when i unlocked my bootloader.
Been using PACMAN nightlies and am currently testing AOKP. Both are working just fine but you lack stamina mode and some sony features like doubletap wakeup and the remote.
The Android 4.3 ROMs are both very usable for everyday usage though. PACMAN comes with more additional stuff but i don't need even half of it wich is why i test AOKP right now. All i want is the tablet UI and the fast 4.3 performance.
I flashed so many ROMS lately that it is probably due to that fact and i need to wipe it clean and start from scratch. :laugh:
My wish would be a modified Sony 4.2.2 ROM with tablet UI. I think the additions Sony implemented are useful without bloating the operating system. Sadly it is completely useless with the phablet UI.
KanjiMan1977 said:
Hey people... I myself own a 312 model and love the thing to pieces. The first thing i did was get my precious root.
Right now I am reading up on the ROM releases and just dont know if I want to continue modifying or to wait.
I own a galaxy note... so i know all about flashing different roms... but my experience is usually the same with every rom.
Day one... yay... it works flawless. Day two... runs ok... then by the time a week goes by the thing just reboots so often that i get pissed off and flash something else.
So my question is what rom/kernel are people using... how long have you been using it... and how stable has it been?
Click to expand...
Click to collapse
I'm using the PAC nightly builds and having no problems :good:
As Jequan mentions, you do loose some of the stock functionality. The only bit I miss is the double tap to wake - that was nice.
The main reason I use PAC is for Pie functionality. For me, permanent on-screen navigation buttons are a waste of screen space - so I use ROMs with Pie (PA on my phone, PAC on my tablet z).
Note : If you are going to unlock your bootloader, backup the TA partition first. (Google: 'Sony DRM TA partition backup' for more info)
At the moment, the Sony stock 4.1.2 is the best ROM. Full functionality, rock stable, no annoying phablet UI.
Only problem is WiFi connection is sometimes a bit unstable. You have to test whether that's a problem for you (for me it's not, with my router it works very good).
Well Im really just waiting to see if they screw up 4.3 cause its supposed to be out really soon. Ir remote... dont care about cause there are other apps on play... just wont be as pretty. What I really wanna hold on to lol... my gallery widget... I cant find one even close to it. but if I want it that bad theres an Advanced Xperia launcher I can install. I have all the files needed to get the ball rolling. Im just still kicking myself for upgrading to 4.2.2. Now I guess either downgrade or Rom either way next step for me is a recovery cause im not flashing nothing without one. PAC was a pretty good Rom ported to the Galaxy Note... But it crashed a lot on me.. But that was back awhile ago. I like my per app dpi and all the customization bells an whistles.
Another thing I was thinking was trying the Xposed framework on the stock Sony firmwares. With the right modules it just might do the trick. But I would still want to run a recovery before trying that aswell.
After benevolently testing new phablet-ui for some weeks, I found it most inappropriate for a 10.1" device on which I work in horizontal screen orientation. So I changed to latest PACMAN ROM nightly and now after a week I can conclude, this step has payed off. Although some things do not work (yet) in this ROM, it runs very smooth, not a single reboot from the start. It has tons of options to set and play with and it brought back the tablet-ui. I did no great feature testing, only daily work with Dolphin, Firefox, Chrome, K9, Jota, FileManager HD, QuickPic, c4Droid, AdobeReader, YouTube etc. Also battery live seems to be all right to me. The only thing is I had to change to Nova launcher, built-in Trebuchet did not handle wallpaper setting properly. On the downside I lost the unique features and apps of stock ROM, but I did not use them anyway ...
What i miss, is the stamina mode, MHL hdmi, USB Mass Storage.
I use CM10.2
USB mass storage also doesn't work??
You can't connect a USB stick to the tablet, even not with Stickmount or a similar helper app??
USB Storage seemed to work for me when i had PACMAN installed.
The complete lack of deepsleep resulting in battery drain when inactive is what made me go back to Sony 4.1.2.
Once they found a way to do something like staminamode i will switch back.
All it would take is to let the tablet enter deepsleep i think.
Pacman (or any other AOSP based ROM) doesn't have deep sleep? Can't believe that!
I'm sure you just had some app which held the tablet awake.
hasenbein1966 said:
Pacman (or any other AOSP based ROM) doesn't have deep sleep? Can't believe that!
I'm sure you just had some app which held the tablet awake.
Click to expand...
Click to collapse
I reinstalled it clean just for that. Also installed greenify and disabled everything possible. Then installed wakelock detector and nope it never went to deepsleep. Neither did the AOKP ROM for that matter.
I posted it in various threads but so far i got not a single confirmation that others get deepsleep.
OK, so no deepsleep -> worse battery life?
I'm on PAC for two weeks now, I'm using the device exactly the same way as with Sony stock and activated stamina-mode. And there seems to be not much difference, maybe few percent advantage for Sony stock.
PAC Wi-Fi settings 'Keep Wi-Fi on during sleep' I set to never, but sometimes incoming mails are received anyway.
qshoo said:
OK, so no deepsleep -> worse battery life?
I'm on PAC for two weeks now, I'm using the device exactly the same way as with Sony stock and activated stamina-mode. And there seems to be not much difference, maybe few percent advantage for Sony stock.
PAC Wi-Fi settings 'Keep Wi-Fi on during sleep' I set to never, but sometimes incoming mails are received anyway.
Click to expand...
Click to collapse
When i used AOKP or PACMAN i lost about 1% battery per hour when in standby. With the sony ROM i wont lost a single % over 12 hours. I also had massive battery usage shown for "Android system". I never could narrow down why or what causes it. With timescape the display is using most of the juice as it should be.
That is why i started looking into where the juice goes and it showed that it never goes into deepsleep and no app was active.
Maybe i did something wrong i dunno.
I'm on cm and loving it. I like the simplicity of cm while still having that AOSP feel.
I'm running AOKP nightlies, only because CM 10.2 doesn't seem to have a tablet UI - I'd love to be proven wrong on this though! AOKP is pretty solid, but it has some oddities to it that make me miss CM 10.2 or stock Sony. Mostly I miss Double Tap to Wake.
AOKP is not updated very frequently either, and there are some issues that I think should be fixed that just haven't been after weeks, so I'm somewhat disappointed for now.
joe.cole1 said:
I'm running AOKP nightlies, only because CM 10.2 doesn't seem to have a tablet UI - I'd love to be proven wrong on this though! AOKP is pretty solid, but it has some oddities to it that make me miss CM 10.2 or stock Sony. Mostly I miss Double Tap to Wake.
AOKP is not updated very frequently either, and there are some issues that I think should be fixed that just haven't been after weeks, so I'm somewhat disappointed for now.
Click to expand...
Click to collapse
See that's what i dont get... all these roms running off the same buggy cyanogen but know one fixes them... they just copy them over to such and such rom and its no better cause it has the same bugs. I guess its just the fact is whether or not all the fancy dancy features is worth loosing some functionality over a stock rom. I was thinking that modified xperia launcher was great to use on stock rom (but what happened to that... been months since update) along with a couple other customization apps. I don't see to much happening in the XTZ scene I cant even find a functional recovery that works like it should... correct me if Im wrong. Almost all the threads are full of out dated info ("that was soo last week" ) or empty promises, Or is it that there are people working on new great things and keeping it hush hush. Im no dev i would learn if i knew where to start (I know starting with XML would help) but how about an update on your projects once in a while like how things are going.
But to be honest I think im gonna downgrade cause Im sick of lookin at the stupid phablet UI with its grey bars (BAD SONY).
[ROM][10/11][CM10.2][Linaro][O3][MeowKernel][TWRP][Fidelity]CM10.2 - Fidelity Edition
http://forum.xda-developers.com/showthread.php?t=2383800
Works beautifully well. Was getting boot loops on pac rom on my wifi only 32g xperiabtablet z.
I also posted in thread how to get viper4android to work and have scipts Supercharger V6 supercharged 100% working along with crossbreader.
Unrelated, is anyone else concerned about the usb port breaking on the device? im reading reports that it eventually falls off. Anyone here have their tablet since May, no issues? im buying a charging cradle to mitigate damage.
Also I really like the GUI in this ROM. I have deleted stock along launcher using no bloat,;I use Nova, way better and I locked nova in portrait mode because looks way nicer. I also flashed a swipe asop black keyboard with swipe and installed exposed module with app settings. I use greenify to grrenify all and keep a greenify shortcut on my desktop. I deleted all email apps including gmail because I use aqua mail.
Running very smooth here. Really love the expanded desktop feature, I use it while I'm gaming.
This tablet is far more superior with boot loader unlocked. Glad I did it!
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.