Database Users

Stock or custom?

I am getting tired of waiting for the stock 3.1 rom now so I am starting to think about using one of the custom roms.
Have there been any performance and function comparisons between the stock rom and the custom roms?
Or do you have any good arguments either way?

The two most popular appear to be Virtuous Picasso and Virtuous Galaxy. I have been using the 1.08 version of the former for sometime and have had no issues. I thether, have gps, bluetooth, WiFi all w/out issue. If your rooted, get wild and flash them both; see which you Luke better.

I like virtuous galaxy for the the touchwiz, but there were too many broken things. Exchange didn't work, couldn't access files on my external sd card (although apps like google music seemed to be able to) and my usb keyboard didn't work. Virtuous galaxy seems to work without any issues.

I've tried them all so far, and they all have pro's and con's. They also all have bugs, which is only to be expected.
Currently, I'm running stock and, to be honest, kinda prefer it. Though I *have* rooted and added a few tweaks...

willyampz said:
I like virtuous galaxy for the the touchwiz, but there were too many broken things. Exchange didn't work, couldn't access files on my external sd card (although apps like google music seemed to be able to) and my usb keyboard didn't work. Virtuous galaxy seems to work without any issues.
Click to expand...
Click to collapse
You started off saying virtuous galaxy had too many broken things, then went on to say virtuous galaxy seems to work without issues? Maybe it's too early and I'm reading it wrong in my barely awake state, but could you clarify please? Lol

vanisleguy1976 said:
You started off saying virtuous galaxy had too many broken things, then went on to say virtuous galaxy seems to work without issues? Maybe it's too early and I'm reading it wrong in my barely awake state, but could you clarify please? Lol
Click to expand...
Click to collapse
I don't mean to speak for willy but I think what he was saying is that at first, Virtuous Galaxy was nice but had too many broken features but after the release this past weekend, most of the bugs are fixed.
I am using Primee which is the Asus Transformer ROM with some of the Acer items left intact. I have tried Virtuous Galaxy and UI is beautiful but I was getting a barely perceptible lag opening and closing the app drawer even after OC to 1500 and it was bugging me. I think the problem could have been one of the Samsung widgets.
I normally recommend loading a custom rom if you feel comfortable. I rooted my HTC Magic back in the early days of Android and have never looked back.

wahlis said:
I am getting tired of waiting for the stock 3.1 rom now so I am starting to think about using one of the custom roms.
Have there been any performance and function comparisons between the stock rom and the custom roms?
Or do you have any good arguments either way?
Click to expand...
Click to collapse
You should go for 3.1 stock (official acer update), works like butter and fixes problems that custom roms still have (like cell stanby) unless they are based on 3.1 stock (I'm still waiting )
Update to 3.1 stock Acer Official Update
No wipe needed or acer recovery/cwm, you don't lose your data, but it's highly recommended to backup and use recovery/cwm, through again not necesary.
Here is a change log (what's new/changed) to see if it's worth, if you do update please share with me in that thread what's new and changed so we can inform, share and encourage pleople to update to 3.1, plus if you do it now you get new OTA Acer_ A500_4.010.30_COM_GEN1 (I sound like a salesman ) who knows for how long they will keep the update

Justray said:
You should go for 3.1 stock (official acer update), works like butter and fixes problems that custom roms still have (like cell stanby) unless they are based on 3.1 stock (I'm still waiting )
Update to 3.1 stock Acer Official Update
No wipe needed or acer recovery/cwm, you don't lose your data, but it's highly recommended to backup and use recovery/cwm, through again not necesary.
Here is a change log (what's new/changed) to see if it's worth, if you do update please share with me in that thread what's new and changed so we can inform, share and encourage pleople to update to 3.1, plus if you do it now you get new OTA Acer_ A500_4.010.30_COM_GEN1 (I sound like a salesman ) who knows for how long they will keep the update
Click to expand...
Click to collapse
My question is,after read almost all pages of the threads about this;does this go for all devices?I have a emea_gen3..sorry if i'm being a Noob now.
Sent from my A500 using Tapatalk

Thanks for all the advice. I think I'll wait a while longer for the stock now. It doesn't sound like the custom roms are the kind of miracle upgrades I got to my Hero and Desire phones yet.
Sent from my A500 using Tapatalk

booze78 said:
My question is,after read almost all pages of the threads about this;does this go for all devices?I have a emea_gen3..sorry if i'm being a Noob now.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA.
wahlis said:
Thanks for all the advice. I think I'll wait a while longer for the stock now. It doesn't sound like the custom roms are the kind of miracle upgrades I got to my Hero and Desire phones yet.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Actually the update posted IS official, Acer one, right now those with that version are getting OTA .30 update, so as far as I know that's stock unless you mean out-of-the-box as stock.

i meant to say virtuous picasso seems to work without issues and tried to edit it after.

Justray said:
Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA.
Actually the update posted IS official, Acer one, right now those with that version are getting OTA .30 update, so as far as I know that's stock unless you mean out-of-the-box as stock.
Click to expand...
Click to collapse
Yessss,it worked.Lost root only..
Sent from my A500 using Tapatalk

booze78 said:
Yessss,it worked.Lost root only..
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
and you can re-root
Please post here anything new you find, new issues, fixed issues, software and experience related please

Just don't forget to back up!

@Justray, you say : "Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA."
How do you procede to go from EMEA_GEN3 to COM_GEN1?
My machine is COM_GEN1 so I'm happy. My sister who got hers in Denmark is EMEA_GEN3 and is still stuck with firmware 1.x (Android 3.0.1)... Is there a step-by-step instructions for going to COM_GEN1 for her machine?
I suspect I can then download the latest firmware manually from : code.google.com/p/acer-a500/downloads/list or use OTA like my machine?
Thanks,
Gilles.

ggravier said:
@Justray, you say : "Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA."
How do you procede to go from EMEA_GEN3 to COM_GEN1?
My machine is COM_GEN1 so I'm happy. My sister who got hers in Denmark is EMEA_GEN3 and is still stuck with firmware 1.x (Android 3.0.1)... Is there a step-by-step instructions for going to COM_GEN1 for her machine?
Click to expand...
Click to collapse
I too went from EMEA_GEN3 to COM_GEN1. Here is the basic low-down as to how I went about it:
* Install Acer Recovery from Market and use it to install clockworkmod.
* Download the COM_GEN1 ROM from http://forum.xda-developers.com/showthread.php?t=1176632 thread.
* Use Acer ROM Decrypter to decrypt the .zip file and extract the update.zip from there.
* Rename the update.zip to something like e.g. AcerROMcomgen1.zip and copy it on your SD card. It's important that it is on the SD, not internal storage.
* Turn off your tablet, then turn it on while keeping the volume button pressed down until you see white text appear on the tablet screen's top-left corner.
* Use clockwordmod to first make a full backup for just-in-case. I really mean it: do a full backup. You never know if you might need it later!
* Then format cache, format data/factory reset, then install zip from SD.
* Reboot.
As for navigating in clockwordmod: you use the volume button to go up or down in menus, and power button to select the menu item.

How doi I get to ICS?

In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)

Wait till Asus fix the problems.

Yea dont install ICS, it would be like pouring water over your PC
It might seem fun at the time, but its really not a good idea

I would say it is a very bad idea. Avoid it. I did it and literally my tablet is unusable now because of
Slow response
Random rebooted
Random no message crash of apps like gmail.
Dead slow,app response
white screen on app loading
It is now embarrassing infront of ipad users.
Sent from my Transformer TF101 using Tapatalk

spinaldex said:
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Click to expand...
Click to collapse
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.

horndroid said:
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
Click to expand...
Click to collapse
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk

*Detection* said:
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
Click to expand...
Click to collapse
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.

I would no say my TF is unusable under ICS.
It works fine, apart from not so random reboots, as it reboots mainly in the morning when I wake it up form the night...
maybe the Sleeping Beauty requires a kiss from the Prince ...
By the way, it used to be really better under HoneyComb, I wish i could have refused that damned firmware upgrade ...
If I were you I'd rather wait as an other poster said for a really proven Stable version from Asus
Nickola

horndroid said:
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
Click to expand...
Click to collapse
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**

*Detection* said:
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
Click to expand...
Click to collapse
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.

I've got issues on Stock and I did a full wipe using voldn+power method and this was before I rooted. I also lost sound randomly on Stock, and the custom kernels I still get reboots but my sound for the main part does work.
So, if the OP needs their tablet to work correctly then wait, if it's not that important to them and they don't need for day to day tasks then take a chance, you might get lucky or you might be causing yourself a headache, up to you.

horndroid said:
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
Click to expand...
Click to collapse
How is the problem me when I am doing everything the "ASUS way" ?
The problem is ASUS and their code.
If you read the OP's actual post, you will see this line
"Is it possible to upgrade to the stock ICS"
And if you want to go even further into it, your line "Probably because I do it correctly and do a full wipe including format /system before I flash anything"
I don't think you can get a cleaner flash than NVFLASH, which is how I always flash my ROMs

Do give latest Revolver a try for your ICS woes

Been pretty vocal about ICS troubles, to the point of downgrading to HC (using Revolver 3.11). Well, after .24 upgrade, decided to give ICS a try. Thankfully, there is a new Revolver with .24 integrated, pre-rooted and all.
Backed up my HC install, JIC and went for it. Been stable for a few days, no RR or SOD ... so if you're at the wits end, do give it a try. Sometimes, those SODs/RR have a pesky habit of rearing their ugly butts weeks after installs, but it is all good for now and I will deal with issues when/if they arise.
As usual, if you have apps with lotsa of settings that you want to retain, use Titanium to make the post-flash-app-reinstall-dash easier

Just curious.. beside the .24 integrated. What significant changes, features or feeling having Revolver running?
I've been running rooted stock ICS with CWM installed and pretty happy with it under guever's awesome kernel..
Sent from Transformer TF101 (B60) via XDA Premium HD

I dont see anything uber special in there. If u have something that is 100%, stick with it .. For me, it was an ez flash with everything included in there, so I won't have to root it etc.

Unlocked Bootloader v8 / ICS - SoDs

I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?

droidroidz said:
I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
Click to expand...
Click to collapse
Had sod on any rom (and stock) with changed bootloader (and other problems). Went back to ota stock without root. No problems

I have SoD since going from thors rom back to taboonay and then to V8 bootloader, still trying to solve the issue but no luck. I can't even connect to pc to root it again as I've lost that too

Any of you running a 501?
If so, it's an issue with the kernel.
MD

a500 here

Moscow Desire said:
Any of you running a 501?
If so, it's an issue with the kernel.
MD
Click to expand...
Click to collapse
Using A500
I see so many others with success which is why its killing me that this is not more common issue. There must be something we are doing slightly wrong or forgot to do causing this.

Ok, here is the real deal.
1. ICS Bootloader. Mandatory. Check it when you boot, it should say in the left corner.
2. Recovery version has no effect on SOD. However, you should have the correct one for ICS. Currently I use 1.7.3.
3. The kernel. Now, most of the ICS Roms in the forum for the 500 have a "tweaked kernel". These are the ones you want to use. MAKE SURE the rom you are using is for the patched ICS Bootloader. This includes EZTerry's and Civatos. You have to pay attention with Civ's as he may still have some designed for HC bootloader. YOU DO NOT WANT THESE. I believe Smaury's and Vache's are ok also, but check first.
4. This is probably where the problem is. Wipes and Formats. Sometimes, leftover code from a previous kernel or modules could still possibly be in the tab. This can cause strange issues.
Wipe
Data/factory reset
Cache
Dalvik Cache
(depending on recovery version)
Format System
Format Flexrom
Do this 2 or 3 times, then install the rom.
I use CWM 1.7.3 recovery (too lazy now to change but will in the future)
Also, if you have any doubt which bootloader you currently have, download AcerRecoveryInstaller and it should tell you. After OTA in the Dev forum will also tell you. You don't have to do anything with the app, just start it to get information.
This should get you going.
MD

I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?

riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011

riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD

Moscow Desire said:
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Click to expand...
Click to collapse
This is an interesting theory and makes sense. In my case with CM9 and Ezterry's rom I have tried the stock kernel for each and ezterry's OC kernel on both...and still SoDs although ezterrys rom/kernel seems to be far less frequest SoDs. We don't have much options for kernels around here.

Progress?
Has anyone made any progress with figuring this out?
My tablet was running fine on a stock, rooted ICS. Then I installed custom recovery, different kernel, and bootloader when I tried JellyBean (ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]) from the Developers forum on here. I started getting SoDs and some of my games weren't running, so I went back to the ICS rom, but the SoDs are still happening. At that point, I was pretty sure it was related to the kernel or the bootloader.
On the "ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]" thread in the developers section they are questioning if the SoD is related to CyanogenMod (which I don't believe it is). I wanted to post there about what this thread is hypothesizing, but am unable to post to that thread (too new to XDA).

Update
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...

Waleslie said:
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Click to expand...
Click to collapse
Venturing out to JB land is a choice.
Although CM does a pretty good job of doing things, I always have to remember, they lean toward mainstream devices.
We 50x owners, have some pretty good guys. But, we only have a few, compared to the mainstream devices, which have a whole lot more. Welcome to the tablet world.
If it were a samsung or Asus, would probably have a ton more.
But, my ICS on my 501 runs pretty darn good. And I'm thankful to each and every dev and cook who strive to make it better. It's a pity there are not more for our device.
SOD will always plague us it seems. A lot seems to depend on the revision hardware. Seems the earlier versions don't get it much.
MD

droidroidz said:
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
Click to expand...
Click to collapse
same problem as you and 8/10/2011 is when I got mine. I have had some version of hc to work with no sod, but tried everthing and every combination out there (with the mod bootloader) and still have sod, so just went back to stock.

LS8... another test rom?

I've read on this forum that some well-respected users* hypothesizing that LS8 may actually be just another test rom based on the following things:
- Only released in Spain (FOP) [not sure what the other 2 Chinese releases brought to the table)
- Bootloops/freezes seem to happen even while using the stock rom (this seems to happen to all users eventually)
In my experience, I had one freeze in which I couldn't wake the device. I turned it off, removed the battery,
and it got stuck on boot. Then I turned it off (by holding the power button) and turned it on again and it work. Hours later the same thing happened. I thought it was Jeboo Kernel 1.2's fault, but now that I read this I am uncertain.
So what do you guys think? Are we running a test rom? Did Samsung release it so that we would shut the hell up for a while? Or is it the real deal and it is the best we'll get?
*not mentioning them just to avoid them getting hatemail (actuallly hatePMs) if this proves not to be true

Dexter_prog said:
I've read on this forum that some well-respected users* hypothesizing that LS8 may actually be just another test rom based on the following things:
- Only released in Spain (FOP) [not sure what the other 2 Chinese releases brought to the table)
- Bootloops/freezes seem to happen even while using the stock rom (this seems to happen to all users eventually)
In my experience, I had one freeze in which I couldn't wake the device. I turned it off, removed the battery,
and it got stuck on boot. Then I turned it off (by holding the power button) and turned it on again and it work. Hours later the same thing happened. I thought it was Jeboo Kernel 1.2's fault, but now that I read this I am uncertain.
So what do you guys think? Are we running a test rom? Did Samsung release it so that we would shut the hell up for a while? Or is it the real deal and it is the best we'll get?
*not mentioning them just to avoid them getting hatemail (actuallly hatePMs) if this proves not to be true
Click to expand...
Click to collapse
I would say so, why would they only release it in one country? I has to be released only in Spain so they can iron out the rest of the bugs, including the annoying freezing/random turning off ones that kill your battery. Battery drain has to be sorted also, so some call it the final build, but I reckon it will another month or two before we see the true "final" build, hopefully with all the bugs ironed out.

Question. ...are people getting these bugs you talk about if they run the rom bone stock no root? I do believe this was rushed out but not that its another test rom. Staying on my rock solid neat rom 4.0 with siyah for now. Something better is coming....fingers crossed.
Sent from my GT-I9100 using xda app-developers app

themadba said:
I would say so, why would they only release it in one country? I has to be released only in Spain so they can iron out the rest of the bugs, including the annoying freezing/random turning off ones that kill your battery. Battery drain has to be sorted also, so some call it the final build, but I reckon it will another month or two before we see the true "final" build, hopefully with all the bugs ironed out.
Click to expand...
Click to collapse
Perhaps, but doesn't that make it a test rom by definition?
vanisleryan said:
Question. ...are people getting these bugs you talk about if they run the rom bone stock no root? I do believe this was rushed out but not that its another test rom. Staying on my rock solid neat rom 4.0 with siyah for now. Something better is coming....fingers crossed.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
This dev claims that the first time he installed it (straight from the sammobile odin file) it caused him bugs. I haven't tried the stock, untouched, unrooted version.

I've said before that LS8 feels unfinished.
Sent from my GT-I9100 using xda premium

I don't have any bug or freeze. I'm on LS8 with PhilZ kernel btw.

Until UK's XEU is out, I won't call anything "final".

I have the spanish rom, clean install. Without root, pure stock, odexed, not zipaligned... I had thoose problems using custom kernels and rooting my phone! going back to stock, everything is fine. I think that the problem is that some files are changed, I tried cooking my own rom and it didn't worked (ok a "first try").
I think that we must wait some weeks for good kernels, because the development of a kernel requires time. You can make one that boots in a short amount of time, but one without freezes... It should need some weeks.

No freezes, stucks nor bootloops for me. U'll get the best of it if u actually did total wiping rom & kernel by wiper scripts provided by hawkerpaul's especially if u ran custom rom & kernel before.
And u'll get worth battery savings if u wipe the bloatware by TiB & slimmin down ls8 at ur taste, those will grab out crappy ware from ur ram & kill the batt eater. Disable gnow, syncing at certains need & disabling fast dormancy if ur operator doesnt supported.
Just one so annoyed for me & does anyone has idea why : stock browser didn't run & got FC at custom dpi ??? and pls provide me a link a multi dpi playstore to install at stock recovery, the one I had got unsigned to install.
Please give me some respect for useful answer..
Sent from my GT-I9100 using xda app-developers app

It definitely is a test ROM... There are bugs.:banghead:
Sent from my GT-I9100 using xda premium

Never had this sort of issues with any ROM before. Sure I had buggy ROMs that crashed apps left and right, but never have I had to worry that forcing a reboot will corrupt the system.
So in my opinion there are two issues here. One being that the phone can freeze in pretty much any app. The other being that holding the volume and power buttons down to force a reboot will ruin the boot sequence somehow.
In some ways, the inevitable freezes bother me the most. On my old 4.0.4 RR AOKP ROM I just to have this issue where scrolling too fast in lists in certain 3rd party apps (like Amazon, Techpowerup, Ebay etc) would freeze the phone and I had to reboot. Well, at least it never broke the OS ...
I got the tip from the official Jelly Bean thread that backing up, wiping and restoring an installation with a boot freeze / loop will in fact bring the system back to life. As to why this works I have no idea.
I also noticed someone talking about possible issues with restoring apps via Titanium Backup, the Android ID and some mismatch. I have never seen the Android ID pop-up in TB though and I assume this is just another developer mantra, like wipe - reinstall - wipe - reinstall. In truth they seem to have no clue what is going on.
Good job Samsung, good job ...

Well. I too think that this is a test release. One for Europe and one for Asia (China releases). We'll have the proof when we will see the next releases in other countries (like UK XEU and/or Nordic NEE). I assume that there will be different PDA's with newer changelog.
But, from my experience, this release is very good. I flashed it from the first day it has been released via Kies and I kept it unrooted since (only disabling some apps). I haven't experienced any of the issues mentioned time and again in this forum and the battery is on par with ICS 4.0.4 LPY for me. 2d10h with 2h screen on.
Maybe I'm lucky or maybe this is the way to go for now (kies and all stock), until the dev and optimizing process matures itself.

Compared to CM10 and LSJ, this ROM have been the the most smoothest and most stable ROM. I haven't encountered any freezes or instability since I installed it last week. However I did loose service last saturday, presumably a RIL crash, but since restarting it have been running problem free for 69 hours.
I have kept it completely stock, but it is rooted through Mobile Odin.

LS8 is not a test rom, Its available via kies so its public final, The fact that its only been released via Spain so far is irrelevant.
All the people moaning about problems are also irrelevant since you will always have some people who have issues after updating to new rom whether its Sammy official or a custom.
LS8 is very stable and very smooth for me.

i never seen such an crappy rom, its unstable.( xwls8)
First, format my card,rom, etc, put xwls8, default kernel.
After 1-2 hours the bugs appears: when i click on almost anything( like any game, my file, es file explorer, stweak, etc), it freeze, then i was force to close and start again the phone, then bootloop.
Or after an force shutdown i stuck at samsung logo.
I tried siyah, dorimanx, etc, wipe cache, etc, etc
Then after 4-5 days of bugs an unlimited shutdown, freezes, etc, i wipe everyting an install 404 xwlq3, stuck at samsung logo, force to install the rom again, etc.
Now im on xwlq3 and dorimanx 5.92 till a new rom appear. This 4.1.2 is not usable.
Previous one, xxlsj, except lag on lock screen, i dont seen serious bugs.
Boy this xwlq3 rom it feel so nice and fast. And no bugs.
If any of you read on siyah , dorimanx, philz, rootbox, etc,etc thread you will see that a lot of us have this problem.

TheATHEiST said:
LS8 is not a test rom, Its available via kies so its public final, The fact that its only been released via Spain so far is irrelevant.
All the people moaning about problems are also irrelevant since you will always have some people who have issues after updating to new rom whether its Sammy official or a custom.
LS8 is very stable and very smooth for me.
Click to expand...
Click to collapse
Agreed.
Sent from my GT-I9100 using xda premium

TheATHEiST said:
LS8 is not a test rom, Its available via kies so its public final, The fact that its only been released via Spain so far is irrelevant.
All the people moaning about problems are also irrelevant since you will always have some people who have issues after updating to new rom whether its Sammy official or a custom.
LS8 is very stable and very smooth for me.
Click to expand...
Click to collapse
LS8 feels unfinished.
Yes, people may have issues after upgrading but those people are silly and invariably don't know what they're doing. I am however sure that I don't fall in to this category.
Yes, it may be an official release but even so it seems rushed out to appease the masses who were getting sick of waiting.
Yes, it is you lot who're at fault for rushing Sammy in to releasing sub-par, unpolished updates.
I hope you're all happy!
Sent from my GT-I9100 using xda premium

No issues experienced whatsoever
Sent from my Samsung GT-i9100M
ROM NeatRom Lite 4.2 XWLS8
Kernel Philz 4.00b30
Mods:
23 toggles blue w/rt clock
Automatic Call Recorder

Sorry if this is in the wrong place, but is it necessary to change the CSC after flashing this ROM?

I've been using LS8 + Siyah 6.0
Not getting great performance. No hangs/freezes but my battery drains pretty quickly.