Related
I am still using Primordial 3.1 which is one of the first ROM's released for the Transformer.
I see now there are others, such as Revolver and PRIME!
However, upon reading some things in their threads, people seem to be having some random issues here and there. Like Google bookmark issues and FC's during Quadrant tests.
Primordial seems pretty stable, don't really have any FC's going on. What are you guys still running?
I know ROM's might have been improved since the first one, and can make my Transformer operate more powerfully, but I am just cautious of the issues going on with both ROM's out there kinda.
i use prime 1.5.. it works really well
quadrant is not worth even using, so dont install it. the scores dont matter so it doesnt matter if it FCs
Using Prime 1.6. It's pretty snappy and fast, and I haven't had any issues. I've also tried Clemys's rom (I totally spelled that wrong but..) and it keep rebooting my tab randomly, even when not in use. I watched it reboot 10 times on my desk without me even touching it. Never tried Magnus's roms, as I hate the font nor Revolver.
Oh, and Prime and Primordial are both made by Roach. He dropped Primordial though.
Using Revolver 1.0.1 right now and moderately pleased. Came from stock 3.1 rooted since it was so easy.
Minor problems: I'm seeing the freeze when the screen times out. ie. it won't wake back up. I may just have setcpu configured wrong, however. I'll figure that out tonight.
Still waiting for the real work with ICS, of course.
jazper65 said:
Minor problems: I'm seeing the freeze when the screen times out. ie. it won't wake back up. I may just have setcpu configured wrong, however. I'll figure that out tonight.
Click to expand...
Click to collapse
Yeah, didn't have the profile set right. That issue is now gone and I'm about to go to 1.1. Still recommended.
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Stock JB was very laggy on my NS for some reason. Even swipping pages in the home screen was laggy. Some apps would instantly crash, too.
I've been running custom JB roms on my Nexus S, and its been running really well. The only thing is im experiencing the same lag that you do with Google Now. It has caused me to open my browser to do a search, which is disappointing, because in GB and ICS, the Google Search bar was so quick and convenient.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
polobunny said:
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Click to expand...
Click to collapse
heh, that's a fair point. I'm not so upset with the cards taking a long time to load as I am that, while they are loading, the OS is very unstable. It's difficult for me to bring up the keyboard and search google while it's trying to load those cards. I can't believe it's not butter
Nothijngrad said:
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
Click to expand...
Click to collapse
My thoughts exactly . I was excited to get back on stock so I could have a functional phone without any added bells and whistles. New features are nice, but not at this price.
Try running a custom kernel.. Try the thalamus kernel its very stockish and it's SUPER smooth..
Sent from my Nexus S 4G using xda premium
I'm running stock on [email protected] with a matrix kernel everything smooth for me
Sent from my Nexus S using xda premium
I had problems with JB too. There were a few lags, especially with Google Now. Some apps would crash every time I tried to open them, and the launcher crashed every time I tried to change wall paper.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
Hmm I can say that AOSP JB is WAYYYY better than ICS. Soon I can port my ROM from the NS4G to the NS.
I have to agree with this. I've used stock JB when it was released, I was wowed by it's smoothness and cool animations. But everything felt a little slow and sluggish coming from ICS custom rom. After switching to Jellybro, JB feels both very fast and smooth. If you feel disappointed with JB, try using custom rom.
Sent from my Nexus S using Tapatalk 2
I don't know if you guys with problem tried that yet, but it might be a good idea to do a factory reset. You will lose all your data if not backed up but I'm getting a feeling it could help. JB has only been smoother than ICS for most.
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
got556 said:
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
Click to expand...
Click to collapse
I just got my GNex and the difference with JB on this phone is night and day. I didn't think it would be but I'm pleasantly surprised. But yeah. The RAM issue seems to be my biggest gripe with it on the NS. And for some reason, it just dominated my battery. I went through my first cycle on stock with Trinity and managed 3.5 hours of screen time over the course of almost 17 hours and still had a little under 50% remaining. My NS would've been dead long before that with the same usage pattern.....
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
ekerazha said:
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
Click to expand...
Click to collapse
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
I'm running Androxide 3.1 and used to run AdamG's custom ROM. Both ran great, no hiccups what so ever, Google now loads very fast, I guess it depends on your GPS and internet connection. My experience with JB is far better than the fastest ICS ROM out there, I believe given enough time, performance will become exceptional.
Logomotph said:
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
Click to expand...
Click to collapse
That can be tweaked a bit with different kernels.
I am running XenonHD 9 + marmite 4.2 kernel. It's stable and smooth. Worth a try.
Hey guys,
My phone has been acting weird lately. It starts by, lets say, lagging.
I reboot the phone and it gets stuck into a reboot cycle... Great. The only way to fix this is to restore a back up.
I tried reinstalling the rom a couple of times, which resulted into the same problem after a couple days of use.
I've also tried the bubba kernel which, again, resulted into the same problem.
Some specs:
S-OFF, Supercid, HBOOT 2.15, RADIO 1.11
Not sure which ones are actually relevant, but I mentioned it anyways
Any suggestions/questions are welcome. Anything. Thanks for reading.
Well, since you have SuperCID and S-Off you clearly have a basic knowledge of what you are doing. I can only think that it is the kernel or the ROM. I'd never mess around with a kernel, because that is probably the only thing I trust HTC on, that's why I've kept stock. Have you tried another ROM? You might be madly in love with the appearance and the functionality of the ROM, but if it is laggy and is causing you to have to repeatedly restore backups, then you are best off using a smooth one. I also use the CM10.1 nightlies, and I agree with that. If you are seeing screen tearing, then that is not your phone being a retard, that is a known bug that they are going to address. However, some suffer worse than others. My One S is at the grand age of one year and is suffering quite badly from it, yours may not. Also, if you're talking about the RAM dropping from around 350MB at boot to around 150MB in 24 hours, that's pretty normal too.
The screen tearing is rarely noticeable, its actually almost non existent.
Im running the cm10.1 kernel that came with the rom.
I did try ViperOneS but it wouldnt even go further past the splash screen throughout the first reboot after installation in Aroma. Did flash clear fastboot cache and flash boot.img but it didnt work so I gave up on that, lol.
This morning I decided to back up my current rom and restore it after wiping everything, something I only do when installing a new rom. So far my phone is behaving like it should.
I just opened the thread to get help when needed and to get idea's as to why it's behaving like that.
Thank you for your response
Sent from my One S using xda app-developers app
Somebody who has a greater knowledge on this subject than me, most likely usaff, will pop up within the next couple of days and give you some better help than I could. I've only known what I'm doing for a couple of weeks, so I'm new at it, but since I'm a bit of a noob I can give advice that noobs will understand. Since you're clearly not a noob, I didn't help that much.
Maybe some more info is/can be helpfull.
Wich nightly you running?
You say it runs for few days, then you get problems, So it runs correct after initial install.? If So, what programs do you install/use (wich might cause tot make it unstable)
Can you tell how you install the ROM in steps.
Verstuurd van mijn HTC One S met Tapatalk
I haven't experienced this problem in a while anymore. I think a full wipe/reset did the trick before restoring a back up. Thread may be closed
In the beginning of December '14 my tf700t had become so sluggish that I decided it was either ditch it and buy a new non-Asus device - or be adventurous and look into how to unlock, root and install Crombi-KK. Since I had nothing to lose and prefer using my old hardware, I decided to go for 'adventurous'. I did my homework and everything went well. My tf700t ran buttery smooth, and I was overjoyed. My first attempt at tinkering with anything android was a success.
Then after a week or so things started slowing down. Lags, crashes and freezes. Having to reboot the device every 5 - 10 minutes, which obviously I couldn't live with, so I factory wiped from TWRP, reflashed and once again my tablet-life was full of joy. This story has repeated itself so many times that I've stopped counting. On Jan. 6th I did yet another restore, and this time I did a nandroid to make life easier when once again I have to restore. This process is fast becoming tedious, though, and obviously it's not a permanent solution to my problem, so I hope someone will take a look at a couple of catlogs and please tell me what's going on, as interpreting these logs is way beyond my skills.
Not knowing much about flashing custom roms, I go with SBdags default settings when I flash. Freezes, crashes etc. seem to happen with all apps, but in particular with Dolphin Browser. Sometimes I notice that the back of the device tends to become warm.
I installed Autokiller Memory Optimizer - but the tablet crashed within minutes .
I'm sure you'll need further info to be able to point me in the right direction, but unsure exactly which, so please do ask.
Thanks a bunch
While I can't say I'm smart enough to give you a great answer like SDBags himself, I can offer whats worked for me. I've noticed this too as a general trend that seems to be specific to the TF700 itself, regardless of your ROM. For all of his wizardry SDBags can't change hardware and the TF700 is starting to get very long in the tooth. When I feel like mine is acting up I back up the app data and just reflash the ROM. That seems to set everything back to a good spot. As for heating up that might be from overclocking the CPU, I can't remember if thats a default option but I feel it always helps. Play around with Zombi-Cat if you haven't already tried it.
Cheers
Sent from my TF700T using XDA Free mobile app
R_McNeely said:
While I can't say I'm smart enough to give you a great answer like SDBags himself, I can offer whats worked for me. I've noticed this too as a general trend that seems to be specific to the TF700 itself, regardless of your ROM.
Click to expand...
Click to collapse
Actually, hearing from another tf700/custom ROM user with the same experience is a great answer in itself because now I know that flashing a custom ROM on a TF700 hasn't solved all problems for everybody but me. I'll stop worrying that there's something I did wrong and thank Asus for selling me a crappy product and make me learn about unlocking and flashing custom roms without being afraid of bricking it and/or turning it into a fantastic baby bob-sleigh.
Britta
I should add that my post wasn't meant as a criticism against SBdags and Crombi-kk at all. I'm very grateful that I can learn from him and other devs and users here.
My apologies. I made a Noob mistake and put my 1st post all in the title. I am having issues with a lot of the recent apps I download. Closing at random, flashing screen and freezes. Done many searches to no avail. Reinstalled and removed apps. Rebooted pad and reinstalled os with last available from Asus. Any help or advice would make an old man happy. Sent from my Transformer TF101 using XDA Free mobile app
I may of solved my problem. ICS uses flash. I had removed it months ago. When I installed Firefox it didn't need flash. Going back to the stock browser it wanted flash. After installation all glitches went away .
Sent from my Transformer TF101 using XDA Free mobile app
You should try Timduru's KatKiss ROM, KitKat or Lollipop - 100x better than ICS
Hi ,how is lollipop better than ICS ?.Im still using ICS and after a reset it works ok. But if there is something better i might try it. I just bought an unused TF101 after giving up on my nexus7.
zimtuff said:
Hi ,how is lollipop better than ICS ?.Im still using ICS and after a reset it works ok. But if there is something better i might try it. I just bought an unused TF101 after giving up on my nexus7.
Click to expand...
Click to collapse
Try KatKiss 4.4. I found the Lollipop version to be slower than the KitKat version.
ICS was the worst, buggiest PoS OS ever released for the TF101
It turned perfectly stable tablet, into a rebooting, Sleep of Death, battery draining paperweight
Honeycomb was the only stable stock ROM
KatKiss 4.4.4 is the best custom by far
*Detection* said:
ICS was the worst, buggiest PoS OS ever released for the TF101
It turned perfectly stable tablet, into a rebooting, Sleep of Death, battery draining paperweight
Honeycomb was the only stable stock ROM
KatKiss 4.4.4 is the best custom by far
Click to expand...
Click to collapse
Hahahahahaha....breathe....Hahahahahaha
I know you remember all the people that were clamoring for the ICS update and then once we got it (after 3 HC updates that were perfectly stable), they were all......crickets. That was a fun time and I do miss some of those guys that frequented this device section. I still look in from time to time to see what is new. My TF101 is running KatKiss #36 perfectly fine and stable to this day, albeit now regulated to basically a media player. I should really look at the uptime on that thing. I honestly can't remember the last time I rebooted, but I keep it charged all the time and use it at least once a week. I do run into @just lou here or there and a few others that whenever I see them, make a point to say hello.
Glad to see you still supporting. Keep up the good work. That goes for you too @PRBajista.
Woody said:
Hahahahahaha....breathe....Hahahahahaha
I know you remember all the people that were clamoring for the ICS update and then once we got it (after 3 HC updates that were perfectly stable), they were all......crickets. That was a fun time and I do miss some of those guys that frequented this device section. I still look in from time to time to see what is new. My TF101 is running KatKiss #36 perfectly fine and stable to this day, albeit now regulated to basically a media player. I should really look at the uptime on that thing. I honestly can't remember the last time I rebooted, but I keep it charged all the time and use it at least once a week. I do run into @just lou here or there and a few others that whenever I see them, make a point to say hello.
Glad to see you still supporting. Keep up the good work. That goes for you too @PRBajista.
Click to expand...
Click to collapse
Oh I remember it very well lol
Each time a new ICS update arrived, "This one" was the one that was going to end all the pain and misery, and fix everything
And each new update, it got worse, old bugs still there, new bugs added, until it got to the point where I couldn't even use the TF for more than a few minutes without it crashing
And god forbid you left it in sleep mode overnight with both batteries fully charged...because in the morning, the pixies had been playing, and drained both batteries, leaving the tab either off because of no power, or stuck on a black screen of SoD lol (And pretty warm iirc, if it was still powered up anyway)
Mine's running KK #36 too, still going strong, always makes me laugh that a huge company like ASUS got their a$$es handed to them by one guy on XDA