Database Users

Nexus S wont turn on after charging.

I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?

kalda01 said:
I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?
Click to expand...
Click to collapse
Thats what you called "SOD" screen of death. Just pull your batery when it happen. Also it might be kernel related try changing kernel
Sent from my Nexus S

I'm running CM7 since day one with whatever kernel it came with.
What other kernel might work with CM7 ?

There are still a couple though i don't think any are in development any more. Since it seems to have only happened once so no need to try out different kernels. I wouldn't worry about it at all unless it becomes a regular occurrence.

This seems to have happened to many others with the stable CM7 rom version.
In another post someone who had the issue reported that switching to Netarchy's kernel addressed the problem for him.
This happened already twice today so looks like I need to find a solution.
How difficult it is to replace just the kernel?

Get ahold of a GB compatible kernel, wipe dalvik cache and flash the kernel .zip file. Do a NANDROID backup beforehand (CWM -> backup) if you don't have a recent one already.

In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?

kalda01 said:
In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?
Click to expand...
Click to collapse
CFS is a fairer CPU allocation scheduler, and generally better for multitasking as well as overall performance. BFS is, in theory, better at doing only the "task at hand", but so far hasn't proven any better than CFS, and is additionally less stable most of the time. tl;dr, get CFS.
Kernel should work fine on 2.3.7, don't stress about it. In the event that something goes wrong, just make sure you have a backup anyway.

netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?

kalda01 said:
netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?
Click to expand...
Click to collapse
Yup, it's OK to use it anyway. Also kernel is flashed via recovery.
Sent from my Nexus S from Tapatalk

Any need to wipe or reset the phone before flashing a new Kernel ?

kalda01 said:
Any need to wipe or reset the phone before flashing a new Kernel ?
Click to expand...
Click to collapse
No need. Simply flash the kernel, via fastboot

flashed the kernel via recovery. I'll report back if the SOD problem is resolved.

5 days later and not even a single "SOD" freeze. looks like changing the stock kernel
did the trick.

3 weeks after flashing the Kernel and the SOD problem is back. 3 times in last 2 days.
Anything I can tweak to avoid these freezes ?

Do you have any problem caused by the [LPY] ICS ROM?

If YES, please state how did get into the Official [LPY] ICS ROM and the problem you are experiencing.
If NO, then just please tell us your success story.
The reason why this thread exists is to, once and for all, trace the HARDBRICK that plague (?) some (?) ITCHY SGN fanatics and to pacify the fear of some of the other kids.
Don't need your opinions on why blah blah, just the scenario, OK?
Thanks

no problems now, except maybe battery but that might because we are all using it more to test it out
gonna test the battery today when i go to work, if it drops 20% in my pocket then theres a problem but last night it only dropped 5%

Does anyone know anybody that bricked te note with LPY?
I have no problems at all. All working excellent. From miui, flashed back to gingerbread then update to LPY all with mobile odin. No Cwm only everRoot.
Sent from my GT-N7000 using xda premium

No problem coming from official LC1 GB with CF-Root kernel using Mobile Odin Pro with Everoot and injections. Had no problems before factory reset in CWM nor after. I let the system rest both after the initial flash, and after the factory reset/wipe cache/wipe dalvik for about 20 minutes without touching the device.
This is my best experience on the note yet.

Alejandrissimo said:
Does anyone know anybody that bricked te note with LPY?
I have no problems at all. All working excellent. From miui, flashed back to gingerbread then update to LPY all with mobile odin. No Cwm only everRoot.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
One person has, but it is VERY questionable as to the cause of the brick. Time will tell.

No problem occurred thusfar.
I kept my Note stock, didn't want to root to give Sammy a chance...especially with the premium suite and S apps.
So used Odin v1.85..downloaded the 600mb+ file from samfirmware.com..extracted, loaded .tar file In PDA..flash and succes so far.
Good battery life..using Apex launcher but graphics seem improved, Tweakers.net did some benchmarks and conforms my feeling about this.
No trouble downloading large files, playing them and deleting.
So far nothing but good feelings about this..got bit scared by the posible brick stories but keeping it all stock seems to do the trick.
Sent from my GT-N7000 using xda premium

All good here as well . I returned to my stock rooted GB nandroid when the problems with the leaked kernels started (from Stunner, using the Abyss method without any problems). Stayed on it and then upgraded today with mobile odin and everoot (with full wipe). With that I kept root and restored my apps & data with TB. As I read a lot about bricking even with stock ICS I hesitated a bit to also flash the CF kernel. In the end I even flashed that (also using mobile odin). Went into CWM an wiped cashes to flash lidroid's 15 toggle mod. That is working fine now as well. Been using it since some hours now and no problems whatsoever! The only thing I didn't do as yet is a nandroid backup of it.
Sent from my GT-N7000 using xda premium

I am having issues with screen sensitivity.
Battery life isn't very good...
Runs a little warm...
Otherwise, I'm very happy with ICS

zkyevolved said:
I am having issues with screen sensitivity.
Battery life isn't very good...
Runs a little warm...
Otherwise, I'm very happy with ICS
Click to expand...
Click to collapse
I noticed some wonky screen sensitivity issues too. Scrolling through lists on Tapatalk 2 is a pain in the arse. Going to try touch screen booster app
I froze a lot of apps in Titanium Backup, and my battery life/heat issue went away

Itchy SGN fanatics and other kids? Calling an opinion bla bla?
Here's my bla bla: don't patronize people if you want them to contribute to your cause.
Here's my success story: flashed LPY with PC Odin, hated it, reverted back to CM9, happy again.

smooth so far 2 days now and working great battery drains a bit faster but np.

No problems here. Flashed rom and CF-Kernel using Mobile Odin Pro. Have got now a rooted ICS which works very well.
Sent from my rooted Galaxy Note using XDA Premium App

[Success]
Flashed from CM9 build#7 via Mobile Odin with everroot, inject su, inject Mobile Odin and Wipe data and cache options. Worked fine for me.
Flashed CF's CWM injected LPY kernel via Mobile Odin and that worked too.
After the whole brick panic I reverted to the original Samsung LPY kernel via Mobile Odin, no problem.
I didn't use CWM at all though given the suggestions that there may be some imcompatibility between it and the lpy kernel.

bioweb said:
Itchy SGN fanatics and other kids? Calling an opinion bla bla?
Here's my bla bla: don't patronize people if you want them to contribute to your cause.
Here's my success story: flashed LPY with PC Odin, hated it, reverted back to CM9, happy again.
Click to expand...
Click to collapse
Nobody cares... Thread asks if you had problems, not if you hated it. So we will assume it was working just fine for you.

Ok. Here's the real deal. I upgraded through Kies. No root here. DONT UPGRADE NOW:
Problems:
1. Its just as jerky as Gingerbread. Its actually even worse at times in slowness. It has a fast homescreen scroll at first and then has random pauses (almost the same). What worst is in apps when scrolling up and down on text it randomly pauses sometimes for several seconds. Also, every once in a while it does this on and off screen flashing then (not very seldom though). When it does it sucks.
2. The "fast reboot" app now crashes apps if you use them within the first 5-10 seconds after doing a reboot.
3. I'm noticing lots of compatibility issues with apps that aren't fully ics ready.
4. Samsung's version of Ics is dumbed down to almost look like gingerbread. So it runs worse and almost looks the same. I'm historically the one that notices all of the bugs because of how frequently I use multiple apps and because of the amount of apps I have on my phone. Thats why I constantly help by emailing devs pointing out bugs that 98% dont see for some reason.
5. Please dont get mad at me because I'm not a follower to give all praises to samsung and google (I am the same way towards apple too, even know I prefer android).
6. I suspect one of the problems is that Ics takes a little more juice and that the 1.4 exynos is once again underpowered. I think the other problem is samsung tried to rush this update out to the people and that the current touchwiz overlay is buggy. I expect an updgrade on touchwiz shortly (if they are a ethical company).
7. A primary example of the problems: While I'm typing this post I get a phone call. After I reject the phone call it goes back to taptalk with a less lighter screen. It is totally unresponsive. I then have to hit the back key to get back to composing. I then try to move up and down. It won't let me. After 15 to 30 seconds in able to once again continue this post.
8. I am sorry also that I upgraded because it might be glitchy for whom ever buys my phone eventually when I sell it (sell my phone every 6 months) and they may think there is something wrong with the phone, even though I baby my phones for future resell.
9. Bottom line: If its not broke dont fix it. We all want ice cream sandwich. Unfortunately, samsung's touchwiz version of ics at least doesn't appear to be ready for prime time. If you like beta testing and dont mind even worst glitches, then go for it. I definitely wont be upgrading to another phone with ics unless it has the new tegra 3 or the latest exynos processor.
AC
Sent from my GT-N7000 using Tapatalk 2

Well said my man, if it is slower and chews my battery faster wtf is the point of upgrading. We don't gain any mind blowing feature. Fyi who gives a flying F^k about angry birds space or whatever they come out with next
Sent from my GT-N7000

I went from gb, to german release ics, worked fine no issues from pc odin, then chainfire produced rooted kernel for it flashed with pc odin. all worked fine, but now i had triangle and 1 on the counter, ahhh, ok so triangle away dont work, flashed chinese repack did triangle away worked, using mobile odin, then i flashed the repack of the release with chainfire kernel, had nothing but problems, so went back to mobile odin flashed stock ics, then lost root, ahhh so flashed chainfire kernel with pc odin all well but still have triangle and 1 on the counter, i did full factory reset each time. I find ics a bit laggy more than latest gingerbread, i am leaving mine as is for the moment.

Was on several Leaks, to CM9 Official, to Official ICS. 0 problems!
People panic to easily in this forum. 1 guy bricks his phone and the damn section blows up and a public service announcement is made. Really?
Follow the directions.. EXACTLY, don't do anything erroneous, and you will be perfectly fine! Just like the rest of us.

Nope, not yet. Flashed with Mobile Odin Pro with Everroot and not the CF kernel.

Folowed dr ketan method from the lc1 cf root kernel. No problem so far

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.

CM10 Nightlies for Fascinate!

Just noticed that fascinatemtd is finally being included on the CM10 nightlies! I've been following the Jelly Bro roms up to last week. Although I've been using it as my daily driver, I'm looking forward to even more stability.

Anything not working?

Hilbe said:
Anything not working?
Click to expand...
Click to collapse
I couldn't get the market to download any apps on 8/22. 7/26 gapps. Wiped all three coming from Jt's newest build. Tried twice.

rjkxb2 said:
I couldn't get the market to download any apps on 8/22. 7/26 gapps. Wiped all three coming from Jt's newest build. Tried twice.
Click to expand...
Click to collapse
JT's last build (19 August) had zero issues for me. Last night I dirty-flashed to the 8-23 nightly (after wiping caches) and all is well including app installs with market.
Sent from my SCH-I500 using xda premium

is anyone running the nightly on a alt carrier ?
if so can i get a link to the fix

The wifi reception on the 8/24 nightly with devil kernel 1.2.1 is not as strong as on ths ics build 15 with devil 1.1.3
Smoother than ics, but doesn't feel quite as fast.

What CWM are people using. I was running 7.2 and tried flashing while CWM 3 was installed, it rebooted in CWM 6 and it said it installed fine, but im stuck on the Cyanogenmod boot screen for like 10 minutes...
also is there a way to turn a ROM ZIP file into something I can use Odin to flash it with? I can get into recovery, but I dont ahve a mini USB reader to install a new ROM on.

I was running build 15 teamhacksung ICS, then went to 8/24 build CM10.. cleared all cache, etc, installed cleanly. Loved jelly bean, but it's still very half baked, not usable as an every day phone.
Just went back to CM9 nightly, into which teamhacksung ICS was rolled into today, and everything is nice and quick again. will go back to CM10 when the bugs are worked out.

audiphile said:
I was running build 15 teamhacksung ICS, then went to 8/24 build CM10.. cleared all cache, etc, installed cleanly. Loved jelly bean, but it's still very half baked, not usable as an every day phone.
Just went back to CM9 nightly, into which teamhacksung ICS was rolled into today, and everything is nice and quick again. will go back to CM10 when the bugs are worked out.
Click to expand...
Click to collapse
Really?? 8/24 nightly and all of Jt's builds before that worked great. Very snappy and I've had zero problems. I haven't been back to ICS since probably JT's second build. The nightlies or paranoid android are what I use now daily, and I haven't had a bug problem in quite some time.

I'm been on CM10 8/19 nightly since it dropped. Everything works. I use it heavily for work and personal.
I've put off updating my ROM to another nightly, because it takes me a hour or two to get everything restored back the way I want it. Seems you really do need to do both wipes and a cache flush, then flash ROM, then latest JB apps, to assure best results. I've tried cutting corners twice, and both times, it's bit me in the ass.
Kind of hoping they'll hit a "stable" point on the nightlies soon, and I'll catch up then. I ran CM9 happily for about a month, but I'm so pleased with the additional smoothness, stability and additional features of JB, I haven't looked back since I switched.

tbaddley said:
I'm been on CM10 8/19 nightly since it dropped. Everything works. I use it heavily for work and personal.
I've put off updating my ROM to another nightly, because it takes me a hour or two to get everything restored back the way I want it. Seems you really do need to do both wipes and a cache flush, then flash ROM, then latest JB apps, to assure best results. I've tried cutting corners twice, and both times, it's bit me in the ass.
Kind of hoping they'll hit a "stable" point on the nightlies soon, and I'll catch up then. I ran CM9 happily for about a month, but I'm so pleased with the additional smoothness, stability and additional features of JB, I haven't looked back since I switched.
Click to expand...
Click to collapse
Strange, I have the exact opposite experience. I install everything clean, never cut corners.. CM10 seems to have some memory leak.. it start out really beautiful and smooth.. within hours, it's not usable. CM9 remains stable for days in a row, so i'm back to that for a while.

I've been using the nightly CM-10 builds since 8/23. What's the consensus? If I want to flash to the latest build, do I need to wipe the data and cache?
Thanks!

gm2racer said:
I've been using the nightly CM-10 builds since 8/23. What's the consensus? If I want to flash to the latest build, do I need to wipe the data and cache?
Thanks!
Click to expand...
Click to collapse
That's been my experience, and the thing holding me back from upgrading right now. Definitely going to flash to the latest by this weekend, to see if there are any changes/improvements.
I'm just glad I haven't experienced any memory-leak type behavior. I will admit, though, that I've had it do the "sleep of death" thing twice in ~2 weeks. It may have come back to life on it's own, but I was impatient and pulled the battery in both instances.

is anybody else not able to send mms ?

tbaddley said:
That's been my experience, and the thing holding me back from upgrading right now. Definitely going to flash to the latest by this weekend, to see if there are any changes/improvements.
Click to expand...
Click to collapse
I've done a couple of flashes without wiping the data or cache with no ill effect.

Flashed the 9.1.12 CM10 nightly this morning. Only wiped Dalvik cache, nothing else. Kept all my apps/settings. Everything but Google Music was working great, so I flashed the GApps again, went into Play, uninstalled/reinstalled Music, and everything works now.
GPS locks in pretty quickly in GMaps and all of my GApp and 3rd party apps are working normally.
If this continues to be stable, I'll be more likely to flash more nightlies, with fewer days between upgrades.

phone call static
Has anyone experienced static when making phone calls. I was using the 8/26 build and everyone that I called complained that they couldn't understand me because there was a lot of static. I flashed the 9/1 build and I get the samething but a little worst. Other than the static everything is working great.

Bassmas5 said:
Has anyone experienced static when making phone calls. I was using the 8/26 build and everyone that I called complained that they couldn't understand me because there was a lot of static. I flashed the 9/1 build and I get the samething but a little worst. Other than the static everything is working great.
Click to expand...
Click to collapse
No static here... I've been running the cm10 nightlies (stock kernel) for about a week without any issues. I updated to the 09-04 build last night after just wiping cache and dalvik, along with a test kernel that JT posted yesterday that's designed to provide a bit more power to the radio in order to maybe fix the intermittent loss of data. So far so good.
One thing - I've had some issues after experimenting with using link2sd (a great tool) to move various apps to /system to save precious space on /data. It seems that after moving Google maps; voice; Gmail; and similar core apps to system, play store reports update after update for the apps I've moved.
Sent from my SCH-I500 using xda premium

i was running SC3 milestone 2 (gingerbread).
i odin'd to stock EH03 then rooted it.
tried flashing the CM10 ROM via CWM recovery 2.5.1.x (red), 3.0.0.5 (blue), and 3.0.0.8 (yellow). they all abort saying that there is an error on the .zip file.
any suggestions?
edit: followed this: http://forum.xda-developers.com/showthread.php?t=1238070; stock GB -> THS ICS -> JB. yay!

Anyone else notice that auto brightness isn't working, or maybe it's just me? Using the 9/10 nightly.
Edit: Seems to be working now, before I had all -1's in the light sensor levels but now I'm getting actual values.

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.