Database Users

Too slow

I have no idea what happened.
I'm using Cyanogen last update and the phone is so slow it is useless.
Specially when closing an app and going back to the home screen... it takes forever for the phone to be available and ready.
What is the problem ? Any hint?

nricci said:
I have no idea what happened.
I'm using Cyanogen last update and the phone is so slow it is useless.
Specially when closing an app and going back to the home screen... it takes forever for the phone to be available and ready.
What is the problem ? Any hint?
Click to expand...
Click to collapse
Im guessing you have alot of apps open in the background then, you should consider getting a task killer app from market.

Not really...
A wipe fixes everything.

Thank you guys.
The phone is slow 5 seconds after a reboot.
Home screen takes forever to appear and some time forces close.
I might try another room, I don't know.

Everything you need is right here:
http://forum.xda-developers.com/showthread.php?t=567610

I had the same issue. Here is what i did to fix it
Did a Nandroid backup, wipe ,flash with the 1.6 base rom first, then the latest CyanogenMod rom.

Thanks
Will try your suggestions and post the results

Mine was slowing to a crawl as well, turns out (I think) it didn't run as well with compcache enabled. Since disabling it again it is running much better.

nricci said:
I have no idea what happened.
I'm using Cyanogen last update and the phone is so slow it is useless.
Specially when closing an app and going back to the home screen... it takes forever for the phone to be available and ready.
What is the problem ? Any hint?
Click to expand...
Click to collapse
My hint would be ditch Cyan(buggy arse rom)mod and switch to something better and more reliable like either rom in my signiture.

shadowch31 said:
My hint would be ditch Cyan(buggy arse rom)mod and switch to something better and more reliable like either rom in my signiture.
Click to expand...
Click to collapse
Did you just call cyanogen buggy? Them's fightin' words *spits into spittoon*

JAguirre1231 said:
Did you just call cyanogen buggy? Them's fightin' words *spits into spittoon*
Click to expand...
Click to collapse
Erm I do believe I did! *spits into spittoon and listens for the 'ting' noise*
I'll even go as far to say any dev putting the word stable in the title of a rom (at his own admission when it is anything but and needs to be tested) yet still continues trying to fool himself by still saying its stable deserves to have it labelled buggy crap

shadowch31 said:
Erm I do believe I did! *spits into spittoon and listens for the 'ting' noise*
I'll even go as far to say any dev putting the word stable in the title of a rom (at his own admission when it is anything but and needs to be tested) yet still continues trying to fool himself by still saying its stable deserves to have it labelled buggy crap
Click to expand...
Click to collapse
Let's just remember, cyan is basically the base for many roms

JAguirre1231 said:
Let's just remember, cyan is basically the base for many roms
Click to expand...
Click to collapse
Oh I know that fella, I'm using Super D at the moment which is a mix of cyan and dwang and whilst they use the base they also inherite the annoying little bugs too
He has done one hell of a lot for the community, still doesn't detract from the facts though.

shadowch31 said:
Oh I know that fella, I'm using Super D at the moment which is a mix of cyan and dwang and whilst they use the base they also inherite the annoying little bugs too
He has done one hell of a lot for the community, still doesn't detract from the facts though.
Click to expand...
Click to collapse
I used cyan for a week then went back to hero.Now im back on hero(espresso).

On the concept of "stable" I think people have preconceived definitions without merit. Take for example the definition of a "stable stochastic process", which though it is nicer to deal with than many Levy processes, is still a pure jump process. If one can accept the idea of a pure jump stochastic process as being "stable" then it is no problem to see any Cyanogen ROM as stable.
As a side note, I have not had any issues with CM that could not be easily resolved. I love his ROMS, but have a lot of respect for the extremely stable work put out by Enom (I only used his ROM for awhile, but switched to CM for the ease in theming).

This has happened to me before with Cyanogen but I found it was more to do with the SD Card. It would happen anytime I removed the USB cable without "Ejecting" the phone first, amongst other things.
The solution was to format the SD Card and reflash but the downside is you lose everything including apps.

about the DK05 leak wasn't about monopoly

he is lying about the whole thing. i did not give it to people i liked...
i only gave it to people that developed for the epic and people that they trust weather i liked it or not.
I gave firon the leak of dj29 then whodaman & firon decided to leak it without my approval a week later... they have the power to leak froyo without me approving that .. it take time to test froyo.. i assure you that guy that leaked it is not a developer or a tester..
thanks the mods for closing the thread of the dk05 leak because flashing the leak is NOT SAFE!
i just don't want people bricking their phone and yes it has a signature. don't take word for it my source confirmed it..
the closed leak lasted for a week before it became out of control..

Good to know that bro!
Sent from my SPH-D700 using XDA App

noobnl said:
he is lying about the whole thing. i did not give it to people i liked...
i only gave it to people that developed for the epic and people that they trust weather i liked it or not.
I gave firon the leak of dj29 then whodaman & firon decided to leak it without my approval a week later... they have the power to leak froyo without me approving that .. it take time to test froyo.. i assure you that guy that leaked it is not a developer or a tester..
thanks the mods for closing the thread of the dk05 leak because flashing the leak is NOT SAFE!
i just don't want people bricking their phone and yes it has a signature. don't take word for it my source confirmed it..
the closed leak lasted for a week before it became out of control..
Click to expand...
Click to collapse
I agree it wasnt posted by many people who had it for a REASON as to prevent problems and people getting BRICKED or not flashing properly.
Sit back and think about how long the leak has been out do you all really think that if it was WORTHY of being let out to the masses it would have taken so long? No it would have been posted as a rom for mass consumption REALLY Fast....
BUYERS BEWARE

noobnl said:
the closed leak lasted for a week before it became out of control..
Click to expand...
Click to collapse
I think the epic forums are out of control. As someone stated, we should all be helping eachother.
I just see noob has done a lot of amazing work for the epic, people should be grateful & all they do talk garbage & complain. I should just get my evo back & leave all this behind.

rjmjr69 said:
I agree it wasnt posted by many people who had it for a REASON as to prevent problems and people getting BRICKED or not flashing properly.
Click to expand...
Click to collapse
That explains why the modem was not released. Now why wasn't the rom released?
I think the epic forums are out of control. As someone stated, we should all be helping eachother.
Click to expand...
Click to collapse
They absolutely are.

I tested DJ29 for about a week and found it was good enough for a release. DK05 bricked my modem, so I didn't consider it safe.
The ROM was -probably- okay to release, but the modem is not.
It was not held back for fame or any bull**** like that.

There are too many trolls on these forums who obviously don't understand the time and patience it takes to make things like this possible.
I appreciate all the hard work you've done noob, and firon.
I really wish I had the knowledge to participate, but my time will come

halfcourtshoes said:
I think the epic forums are out of control.
I should just get my evo back & leave all this behind.
Click to expand...
Click to collapse
You are dead right on this one. The Epic side of the house is unbelievably bad. Not only are things slow, at no fault to anyone here, but there is WAY too much bickering in these threads. I go to the threads concerning my EVO and love it. I come here and am continually caught off guard by the way folks are. Either way, I want my Epic to stay my main phone, so I keep coming back.

Any one know what the "phone,orange triangle and little computer" mean. I fear I bricked my phone. I can't even get into download mode now. WHen I press 1 and power up the charging battery comes on the screen. Thanks for trying to keep this from happening. This the first time I have bricked a phone in many years. Guess ut was bound to happen at some point.

Why not just release the rom + modem with a disclaimer that it may brick your phone and require an Odin flash? Also, the safety net Odin represents in itself, I think, nullifies any danger from bricking.
And another thing; don't send things to people over the internet and expect them to stay secret.

done12many2 said:
Either way, I want my Epic to stay my main phone, so I keep coming back.
Click to expand...
Click to collapse
Lol, that's my problem. I love my Epic, so I just skim through the bickering & hang around. No offense but a lot of it does seem about egos & fame, but I understand what goes into being a dev & it is nice to have recognition for your work. But at the same time it's not safe to release stuff not ready for the primetime because everyday average users looking for a better phone experience will just end up bricking their phones. & like I said, everything noob has put out has been quality work & I've never had a problem with any of it. just my two cents.

ptfdmedic said:
Any one know what the "phone,orange triangle and little computer" mean. I fear I bricked my phone. I can't even get into download mode now. WHen I press 1 and power up the charging battery comes on the screen. Thanks for trying to keep this from happening. This the first time I have bricked a phone in many years. Guess ut was bound to happen at some point.
Click to expand...
Click to collapse
Pull the battery and try again.

ptfdmedic said:
Any one know what the "phone,orange triangle and little computer" mean. I fear I bricked my phone. I can't even get into download mode now. WHen I press 1 and power up the charging battery comes on the screen. Thanks for trying to keep this from happening. This the first time I have bricked a phone in many years. Guess ut was bound to happen at some point.
Click to expand...
Click to collapse
Hm. What you're describing sounds like you have the phone plugged in while you're trying to enter Download mode, which isn't very effective. Try plugging it out first.

Anyway we can have you guys upload DK17 at least for us to flash or odin? I can wait for the final modem...jjst want an up to date rom.

vgambit said:
Why not just release the rom + modem with a disclaimer that it may brick your phone and require an Odin flash? Also, the safety net Odin represents in itself, I think, nullifies any danger from bricking.
And another thing; don't send things to people over the internet and expect them to stay secret.
Click to expand...
Click to collapse
Because despite all the warnings in the world people who should not touch things of this nature WILL and then a storm of accusations and mad people will hit the forums... What ever happened to being a MAN OF YOUR WORD? thats the beef
DONT SEND THINGS ON THE NET??? Guess you certainly would not be trust worthy

vgambit said:
Hm. What you're describing sounds like you have the phone plugged in while you're trying to enter Download mode, which isn't very effective. Try plugging it out first.
Click to expand...
Click to collapse
mattallica76 said:
Pull the battery and try again.
Click to expand...
Click to collapse
Thanks guys. I'm not sure what was happening but I finally got it to work. Back up and running. I pulled the battery walked away and tried again and it worked.
Defiantly waiting for the ok from the people in the "know" before trying this again. Thanks for trying to protect us from ourselves. LOL

rjmjr69 said:
Because despite all the warnings in the world people who should not touch things of this nature WILL and then a storm of accusations and mad people will hit the forums... What ever happened to being a MAN OF YOUR WORD? thats the beef
DONT SEND THINGS ON THE NET??? Guess you certainly would not be trust worthy
Click to expand...
Click to collapse
Very well put. I am ok waiting. I don't think it's some big conspiracy. I feel better knowing that the newer radios seem to fix the gps. Now we just need to make it safer to use. Until then I'll just pull up a chair, crack open a beer and roast some marshmallows courtesy of all the flames. Anyone care to join? lol

I'm not getting dragged into another fight on here, the **** with Hero was bad enough, but I will say a few things on this issue.
1. Odin gives a safety net, and it works well.
2. The modem is safe, so long as you're competent enough to flash it right. Thats not a shot at anyone who got a brick from it, but it works fine for me and many people who flashed it successfully.
3. This ROM is essentially **** anyway. I had one of the early leaks of it, and I went back to DJ29. The music player has issues, there are UI bugs in the launcher, the camera & flashlight APIs are broken for everything but the stock camera app, and there's still the lag issue on unlock. This is all straight off a wipe as well, so it isn't that.
4. Sometimes it isn't good to give everything to the public. I don't agree with keeping it in a secret little circle for devs, but sometimes things NEED to be tested and cleaned up before they can be given to the public.
5. As for the whole thing that it was a lie that there are tags from the source in the ROM, I'm not aware of everything, but I have found a few myself. All pointing to one Korean name, who built the ROM originally, and it's the same name as on the DJ29 leaks. I'm sure you're smart enough to find it. Does that mean he leaked it? No, but it is still a liability for him and his career because it was built on his machine & probably by him as well. Some people on here are just selfish and don't realize that their craving for the latest and greatest could cost someone their job.
There. I'm done.

This is exactly why the Epic community is not progessing as fast as the Evo community, the leaks don't get put into the right hands. And progress haults, I understand your concern about bricks but maybe you should post a thread with a request for people to Close beta test and perhaps create an application that can be filled out and submitted via PM to the person in control of the leak, this could help the rom fall into the correct hands that can test and verify a rom.
Thank you.

Well when you released dj29 he lost his job then

[Discussion] [WIP] ICS Port

This is discussion thread for PaulBurton's ICS 4.0.x Port.
This is a Discussion Thread About the DEV Thread:WIP ICS PORT
Before We start to discuss i will tell what's working in the latest release *20120201*
Even tough the build is still in Alpha/Beta stage the build is extremely fast, even if all HW/3D Acceleration isn't activated also the driver's for the Tegra2 Isn't fully working! but still the build answer's fast and do the most things you tell it to do!
*Working* (Updated 2012-02-11)
Touchscreen
Sound
Wifi
Bluetooth
Deep Sleep
Headset
GPS On Location
GAPP'S
SU *Fixed*
Battery Indicator*
HDMI Out
Dock Station*
*Doesn't Work*
Rotation*
Microphone*
Camera
Full 3D*
Full HW*
Video Playback
*Latest Build -Battery Indicator-* Partitionaly working*
There you go atleast this is what i know what works and what doesn't!
Even if THOOSE Stuffs Doesn't Work, What can you say about the work so far?
IS it good, Bad, Amazing, or what is your expression!?
Please Hit The Thank's Button On Hes Port Project, as he's mostly doing this Alone and he also do it with much more closed source's!

Earlier Releases
20120201 - NvFlash or CWM
Suspend improvements, now uses LP0, but still likes waking itself up
Backlight fixed
Storage settings no longer crashes
USB device improvements, MTP indicator etc
USB drives & micro SD cards mount, images visible in gallery etc.
CWM update zip now just writes everything as a blob, should avoid all previous zip-related problems
Graphics drivers updated to those from nVidia’s ventana devkit ICS release
Includes Google apps
Click to expand...
Click to collapse
20120121 - NvFlash or CWM
Suspend improvements (still needs work)
Headphones should work properly
Improve CWM update zip to cope with mounted /data
Click to expand...
Click to collapse
20120112 - NvFlash or CWM CWM, CWM mirror
Initial audio support (still needs work)
Bluetooth working
WiFi MAC address fixed
Rooted
USB fixes
Include a CWM update zip version (be careful, remember only use if you can flash back honeycomb)
Click to expand...
Click to collapse
20120110
Using a 2.6.39 kernel
Orientation defaulting to landscape
RAM size fixed
Hopefully fix suspend
Click to expand...
Click to collapse
20120106
Fixed WiFi
Click to expand...
Click to collapse
20120105
Initial build
Click to expand...
Click to collapse
___________________________________________________________________

I think the battery indicator has a glitch that *Detection* has a temporary fix for. However, even partly broken, the ROM is fantastic. I would like to use it as a daily. I'm just not going to jump the gun on it. I'd like to see a little more in the configurable option department, like a reboot to recovery option in the shutdown menu. Removing the Phone.apk and Telephony.apk also. No real need for them as we stand. That's my 2 pennies so far. But, Paul has really gotten far for such a short time, and I'm excited to see where he takes it.
sent from my ASUS Transformer running modded 8.6.5.21 using Tapatalk

Sharpe351 said:
I think the battery indicator has a glitch that *Detection* has a temporary fix for. However, even partly broken, the ROM is fantastic. I would like to use it as a daily. I'm just not going to jump the gun on it. I'd like to see a little more in the configurable option department, like a reboot to recovery option in the shutdown menu. Removing the Phone.apk and Telephony.apk also. No real need for them as we stand. That's my 2 pennies so far. But, Paul has really gotten far for such a short time, and I'm excited to see where he takes it.
sent from my ASUS Transformer running modded 8.6.5.21 using Tapatalk
Click to expand...
Click to collapse
i can sure do indeed , we can use it for daily use, but thats not the best to do atm, but he sure works fast for being alone
Sent from my Transformer TF101 using xda app

Do you think it would be safe for a late model B70 sbk2? I've seen the warnings but i really wanna try it. Caution vs curiosity. I know it's a stupid risk to take with the official ICS just around the corner. What do you guys think?

Dreamboxuser said:
Do you think it would be safe for a late model B70 sbk2? I've seen the warnings but i really wanna try it. Caution vs curiosity. I know it's a stupid risk to take with the official ICS just around the corner. What do you guys think?
Click to expand...
Click to collapse
well, if you got a backup you can try the ics , as it can be done for daily use, but its not recomened. if you want to try make sure you got a working backup, also if you restore honeycomb after tested ics, you need to flash a HC kernel
Sent From My Transformer TF101 Using XDA APP

Dreamboxuser said:
Do you think it would be safe for a late model B70 sbk2? I've seen the warnings but i really wanna try it. Caution vs curiosity. I know it's a stupid risk to take with the official ICS just around the corner. What do you guys think?
Click to expand...
Click to collapse
Risky considering you have no nvflash recovery should anything go wrong.
If you find you have no root / access to CWM you would be basically screwed.
I would listen to your sensible you this time and wait, yes it is bad having to wait, but worse if you brick your tablet.
ICS is nice, fast, but that soon fades with the current suspend / wifi bugs, I would advise waiting

Agreed. I've been in plenty of situations where CWM has saved me and always restored without a problem. It's just a shame i am not able to see the progress as it is happening and I can't be one of those people in the dev thread saying any updates?

Dreamboxuser said:
Agreed. I've been in plenty of situations where CWM has saved me and always restored without a problem. It's just a shame i am not able to see the progress as it is happening and I can't be one of those people in the dev thread saying any updates?
Click to expand...
Click to collapse
The main thing is the kernal. Paul uses a different kernal to get ICS to function more smoothly. In the realm of sbk2, my main concern would be that NVflash doesn't work... and if something goes wrong, you are left with a really expensive coaster. With the rate that Paul has put out updates, it should be no time until we see a daily out of this.
sent from my ASUS Transformer running modded 8.6.5.21 using Tapatalk

Oh well at least my concerns were justified. Although i would like to add
Any updates?????
i wanna play too.

Dreamboxuser said:
Oh well at least my concerns were justified. Although i would like to add
Any updates?????
i wanna play too.
Click to expand...
Click to collapse
Asking for updates is like asking for an eta..don't do that. These guys are doing this on their own time, it is disrespectful to be impatient.
And fyi guys, i have a B70 if it roots with razor claw and can install cwm, and as long as you don't flash over your recovery you should be able to rescue any bad rom/kernel flash. I guess if my recovery went screwy i would be SOL but so far I've not had a problem. Be patient, and check and double check every step.
Did you wipe dalvik? Factory reset? Better make sure before you flash that rom and do an md5 before you flash any recovery to be sure it didn't corrupt in the meantime..if you are really careful, patient, and read a lot, and i mean A LOT, before you flash you can get away with flashing an sbk2 safely. If on the other hand, you've never flashed anything before, and don't know EXACTLY what you are doing, then i wouldn't risk it.
Paul's ICS is great progress, but unfortunately far from being just a novelty due to the bugginess and loss of functions. I played with it for about 5 minutes before I decided it wasn't ready for prime time and went back to revolver
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
Sharpe351 said:
The main thing is the kernal. Paul uses a different kernal to get ICS to function more smoothly. In the realm of sbk2, my main concern would be that NVflash doesn't work... and if something goes wrong, you are left with a really expensive coaster. With the rate that Paul has put out updates, it should be no time until we see a daily out of this.
sent from my ASUS Transformer running modded 8.6.5.21 using Tapatalk
Click to expand...
Click to collapse
Btw it's kernel with an "e"

luna_c666 said:
Asking for updates is like asking for an eta..don't do that. These guys are doing this on their own time, it is disrespectful to be impatient.
And fyi guys, i have a B70 if it roots with razor claw and can install cwm, and as long as you don't flash over your recovery you should be able to rescue any bad rom/kernel flash. I guess if my recovery went screwy i would be SOL but so far I've not had a problem. Be patient, and check and double check every step.
Did you wipe dalvik? Factory reset? Better make sure before you flash that rom and do an md5 before you flash any recovery to be sure it didn't corrupt in the meantime..if you are really careful, patient, and read a lot, and i mean A LOT, before you flash you can get away with flashing an sbk2 safely. If on the other hand, you've never flashed anything before, and don't know EXACTLY what you are doing, then i wouldn't risk it.
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
Btw it's kernel with an "e"
Click to expand...
Click to collapse
Ok luna... with an "e". lol...
sent from my ASUS Transformer running modded 8.6.5.21 using Tapatalk

Dreamboxuser said:
Oh well at least my concerns were justified. Although i would like to add
Any updates?????
i wanna play too.
Click to expand...
Click to collapse
read second post or go to dev thread it should be no problem flash this for me (it's not for me) and i got a Sbkv2 and i can always restore to HC!

luna_c666 said:
Asking for updates is like asking for an eta..don't do that. These guys are doing this on their own time, it is disrespectful to be impatient.
And fyi guys, i have a B70 if it roots with razor claw and can install cwm, and as long as you don't flash over your recovery you should be able to rescue any bad rom/kernel flash. I guess if my recovery went screwy i would be SOL but so far I've not had a problem. Be patient, and check and double check every step.
Did you wipe dalvik? Factory reset? Better make sure before you flash that rom and do an md5 before you flash any recovery to be sure it didn't corrupt in the meantime..if you are really careful, patient, and read a lot, and i mean A LOT, before you flash you can get away with flashing an sbk2 safely. If on the other hand, you've never flashed anything before, and don't know EXACTLY what you are doing, then i wouldn't risk it.
Paul's ICS is great progress, but unfortunately far from being just a novelty due to the bugginess and loss of functions. I played with it for about 5 minutes before I decided it wasn't ready for prime time and went back to revolver
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
Btw it's kernel with an "e"
Click to expand...
Click to collapse
about asking for ETA doesn't meen your disrespectall ful, look at all the ICS questions that asus got, its not disrespectful, you ask's for something that is good to know when you can be able to prepare to leave Honeycomb and go to ICS. but in this case Paul is almost alone working on this. and i can see that asking ETA when he does this on freetime will make it much more harder to set a date! SO asking ETA Isn't Mean. you really show that something is wanted and can give the OP both glad and angry moment's......
Anyhow. The Work goes amazingly fast forward, i wish i had his schills

LastStandingDroid said:
about asking for ETA doesn't meen your disrespectall ful, look at all the ICS questions that asus got, its not disrespectful, you ask's for something that is good to know when you can be able to prepare to leave Honeycomb and go to ICS. but in this case Paul is almost alone working on this. and i can see that asking ETA when he does this on freetime will make it much more harder to set a date! SO asking ETA Isn't Mean. you really show that something is wanted and can give the OP both glad and angry moment's......
Anyhow. The Work goes amazingly fast forward, i wish i had his schills
Click to expand...
Click to collapse
You do realize asking Asus for an eta, when they are a company selling a product, and asking developers who are working for free in their own time, are not the same thing right?
Read the rules. It says pretty explicitly.. Do not ask for eta's.

Well the ETA thing was a joke simply because every third post in the dev thread is got an ETA. Don't let the lack of posts fool you I have been around the block a few times. Also if I hadn't been reading I wouldn't have known that it was not recommend to install on sbk2 devices.
Sent from my Infected Galaxy Y using Tapatalk

luna_c666 said:
You do realize asking Asus for an eta, when they are a company selling a product, and asking developers who are working for free in their own time, are not the same thing right?
Read the rules. It says pretty explicitly.. Do not ask for eta's.
Click to expand...
Click to collapse
Help me out..... where does it say no etas? Serious question.... thnx

I think what the last post referred to is when you pay for a service it's ok to ask them(ASUS) for an ETA but when devs here (Xda) do it for nothing more than street cred, fun, or cause they want to it is not cool to ask for an ETA.
Sent from my Infected Galaxy Y using Tapatalk

slopokdave said:
Help me out..... where does it say no etas? Serious question.... thnx
Click to expand...
Click to collapse
Ok, it isn't as explicit as I thought, but it has been pounded into my head because it's been repeated so many times over and over..
Here: http://forum.xda-developers.com/showthread.php?t=1376759
And Here; http://forum.xda-developers.com/showthread.php?t=1081035
OBKING77's video cites it here; http://www.youtube.com/watch?v=RzpixaIOwSg
This part IS in the guide (though not in the rules);
XDA-Devs is about developers & hackers helping each other and working together to get the most out of our devices by understanding them better than most.
XDA-Devs is not about helping everyone who wants a "Kewl bit of kit" make their phone better than the guy next to him.
Now do we go kicking users off who never contribute anything, NO. We tolerate it to an extent. Where the toleration ends is when these users start diluting the usefulness of the forum by repeating the same questions over and over again.
Click to expand...
Click to collapse
I've just read it so many times it's become a 'rule' in my head. Sorry I was not accurate when stating it was 'explicit in the rules'. But it is a matter of respect for the devs

I wonder if we could do a tally and see how many posts on xda are actually people asking for updates or etas? Probably be in the thousands if not more.
Anyways back on topic.... sorry about that i thought that the implication that it was a joke was pretty clear in the previous message.
So i do think i will try ICS out after i do my backups. I suppose as a trial it will be good.

plz vote ( are u with LPY ICS or going back to GB)

THERE IS ANOTHER POST AND POLL THIS IS REDUNDANT
~~~THREAD CLOSED~~~
plz vote ( are u with ICS or going back to GB)

There is already a post with this exact same question and a poll to answer.
Pointless waste of a thread.
On topic: LPY ICS !

Using stock ics latest update and ....hell no! No never gb for me. This rom is f!cking great. All i need now is a custom kernel(thats made with original sourses). No home made brick kernels with no wifi, black camera screen, buggy speaker.

updated to LPY two days ago... loving it so far...
wifi is good, battery life is good, no overheating problems...
The only 'complaint' i have is that it seems to be a bit of a memory hog... but i can wait for a strimmed down custom Rom based on this one to take care of that issue...
overall, pretty damn happy with it
M

Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now

just i want to know the no of bricked phones compared to all

ratcom said:
Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now
Click to expand...
Click to collapse
Considering what we've seen CM9, repacked i9220 kernel, or home made kernel has been the common denominator in every brick

Totally using official ics and loving it. ;-)
Sent from my GT-N7000 using XDA Premium HD app

Note_E said:
Considering what we've seen CM9 has been the common denominator in every brick
Click to expand...
Click to collapse
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?

If it ain' broken, DON'T FIX IT!!!
Zapped through server hops to XDA forums

sehooo said:
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?
Click to expand...
Click to collapse
Are you rooted with CWM?

Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?

Ueihtam said:
Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?
Click to expand...
Click to collapse
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to believe that source considering the amount of donations. I look at what's happening and the results of the numerous upgrades being flashed over the past few days to use that as an indicator. Until LPY kernel source is released and the experts can comb through it, there is no real answer. I don't use CM, it's just not my flavor...but I really mean no disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.

Note_E said:
Are you rooted with CWM?
Click to expand...
Click to collapse
just flashed LPY and not rooted till now

sehooo said:
just flashed LPY and not rooted till now
Click to expand...
Click to collapse
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged, but his home grown kernel is not, but all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering it's a source of donations.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
just i want to know no of bricked phones as there are alot of rumors and i read alot and didn't find the solution to get back to gb OR stay on LPY and go for root

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering the amount of donations. I don't use CM, it's just not my flavor...but I really mean not disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!

Note_E said:
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).
Click to expand...
Click to collapse
i got force close with some applications like youtube and applications which need root which i setuped before on rooted GB before upgrading

vetchems said:
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!
Click to expand...
Click to collapse
Correction: before "official" CM9 there was imilkas...which bricked many others. then there was xplod's donated device during kernel development which you can take that as you will.
My argument is valid...I'm using common denominators. But if you read my whole post, I said there is no real answer...so I'm not trying to be "right"...it's my opinion/observation

I moved back my sister phone to GB because of the brick issues in LPY ICS and high battery usage !
Sent from my GT-I9100 using Tapatalk

Soft/Hard brick on LPY - My theory of the cause

I am in no way an expert and what I am about to say could just make no sense. But after reading hundreds of posts on the subject I believe that ONE common pattern emerges. The brick is not really caused by a faulty wiping process of either CWM or Stock recovery. It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_

pakalrtb said:
I am in no way an expert and what I am about to say could just make no sense. But after reading hundreds of posts on the subject I believe that ONE common pattern emerges. The brick is not really caused by a faulty wiping process of either CWM or Stock recovery. It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_
Click to expand...
Click to collapse
like how? if its not a faulty wiping then why the faulty process combination? its the kernel source. samsung changed something to make it problematic with cwm. the rest of GB is fine. but since the leak of ICS and the latest official one, the problem persisted.

Ashren81 said:
like how? if its not a faulty wiping then why the faulty process combination? its the kernel source. samsung changed something to make it problematic with cwm. the rest of GB is fine. but since the leak of ICS and the latest official one, the problem persisted.
Click to expand...
Click to collapse
i think samsung changed kernel against cwm(as we know it is very popular) to brick phones thats how they would earn some extra money: from repairing, buying new phone. Just my opinion

EdgaBimbam said:
i think samsung changed kernel against cwm(as we know it is very popular) to brick phones thats how they would earn some extra money: from repairing, buying new phone. Just my opinion
Click to expand...
Click to collapse
i second that. just like how apple did to their baseband kernel every now and then to block jailbreaking.

Negative publicity would cost a lot more to samsung then the profit of selling/repairing less then 50 bricked phones worldwide, you guys should stop reading conspiracy novels

EdgaBimbam said:
i think samsung changed kernel against cwm(as we know it is very popular) to brick phones thats how they would earn some extra money: from repairing, buying new phone. Just my opinion
Click to expand...
Click to collapse
Except that stock recovery is also affected.
Nothing to do with the power button - just a broken MMC driver.

I believe this. Samsung will be generating more revenue this year.
There are thousands of users outside XDA who are waiting for OTA/Kies updates of their regions.
----
Probably my last samsung phone. Delayed and dangerous update.

friedje said:
Negative publicity would cost a lot more to samsung then the profit of selling/repairing less then 50 bricked phones worldwide, you guys should stop reading conspiracy novels
Click to expand...
Click to collapse
why dont u provide the community with a solution rather than publicising ur conspiracy theory.
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
Entropy512 said:
Except that stock recovery is also affected.
Nothing to do with the power button - just a broken MMC driver.
Click to expand...
Click to collapse
Stock recovery is also affected when u try to wipe a note with rooted/cwm kernel as far as I can tell. As long as it its stock virgin, no problem.

pakalrtb said:
I am in no way an expert and what I am about to say could just make no sense. But after reading hundreds of posts on the subject I believe that ONE common pattern emerges. The brick is not really caused by a faulty wiping process of either CWM or Stock recovery. It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_
Click to expand...
Click to collapse
150% FALSE
i dont touch the power button in recover ever, i use the menu-key/home-key/vol-keys
yet i still bricked my phone

Boy124 said:
I believe this. Samsung will be generating more revenue this year.
There are thousands of users outside XDA who are waiting for OTA/Kies updates of their regions.
----
Probably my last samsung phone. Delayed and dangerous update.
Click to expand...
Click to collapse
Most Notes are under some kind of warranty. If you believe that Samsung would brick phone intentionally to make $$ then I disagree with you in every way.

Intentionally or unintentionally... not everyone but hundreds of users will have pay for MoBos just because they flashed official ICS.
And 'you flashed it yourself' is NOT an excuse. It proves Samsung has poor quality control and testing, period.

pakalrtb said:
It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_
Click to expand...
Click to collapse
I never ever touched anything during cache wipe in CWMR, and I still got the black brick.
So much for your little theory.

chasmodo said:
I never ever touched anything during cache wipe in CWMR, and I still got the black brick.
So much for your little theory.
Click to expand...
Click to collapse
Did you (at any earlier date) flash CM9 or a variant of CM9 on your note?
My theory/hypothesis is that these bricks are occurring when LPY is flashed on a note that has, or has previously had, CM9 or a variant flashed on it.
I am not sure that the ICS kernels themselves are actually faulty.

It's the cwm. Period. A lot of people call it a bug, i would assume it is a feature designed by sammy devs to avoid tinkering with their software.
I am on stock LPY and i did a data wipe via stock recovery.
Zapped through server hops to XDA forums

Isn't Samsung known to be one of the most dev friendly manufacturers? So why would they try to keep people from tinkering with it? As far as I can tell, they just made a mistake. Besides, I know it's cliche, but we all know that when you tinker with stuff you do so at your own risk. Our experiences with the Note should serve as a reminder of that.
Sent from my GT-N7000 using Tapatalk 2

clandestino123 said:
My theory/hypothesis is that these bricks are occurring when LPY is flashed on a note that has, or has previously had, CM9 or a variant flashed on it.
Click to expand...
Click to collapse
Very interesting theory ideed. Tell me, how does your pet theory cover at least half-dozen hard-bricks happening after upgrading from stock GB, rooting and then doing a wipe?
clandestino123 said:
I am not sure that the ICS kernels themselves are actually faulty.
Click to expand...
Click to collapse
I see.
____________________________________________________________
Entropy512:
These kernels are fundamentally dangerous. Samsung introduced some sort of bug in the eMMC driver that can permanently damage the eMMC flash storage of the phone.
Kernels that have been confirmed affected are:
XXLPY official ICS release for the GT-N7000 - At least one user has fully hardbricked and at least 2-3 others have "blown" /system or /data partitions - one of those was after wiping with stock recovery
____________________________________________________________
Chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
____________________________________________________________
These two are top-notch kernel developers, and they don't know what they are talking about? Get out of here....

chasmodo said:
Very interesting theory ideed. Tell me, how does your pet theory cover at least half-dozen hard-bricks happening after upgrading from stock GB, rooting and then doing a wipe?
I see.
____________________________________________________________
Entropy512:
These kernels are fundamentally dangerous. Samsung introduced some sort of bug in the eMMC driver that can permanently damage the eMMC flash storage of the phone.
Kernels that have been confirmed affected are:
XXLPY official ICS release for the GT-N7000 - At least one user has fully hardbricked and at least 2-3 others have "blown" /system or /data partitions - one of those was after wiping with stock recovery
____________________________________________________________
Chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
____________________________________________________________
These two are top-notch kernel developers, and they don't know what they are talking about? Get out of here....
Click to expand...
Click to collapse
Great but either way you make it worse. Its already been said and resaid...and stickied. This **** is getting so lame now

freedomispopular said:
Isn't Samsung known to be one of the most dev friendly manufacturers? So why would they try to keep people from tinkering with it? As far as I can tell, they just made a mistake. Besides, I know it's cliche, but we all know that when you tinker with stuff you do so at your own risk. Our experiences with the Note should serve as a reminder of that.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
+1 for this
Sent from my GT-N7000

Note_E said:
Great but either way you make it worse. Its already been said and resaid...and stickied. This **** is getting so lame now
Click to expand...
Click to collapse
Yes you are right. This is lame - until you brick your device.
What i really don't understand in all this discussions is the mistrust in Chainfire.
We all are more or less using his great work. almost every custom rom has it's roots in CF-Kernel.
Now Chainfire give a warning and people try to argue it away. What's that?
Same to Entropy...
It's a bit like not using safety belt in a car. In the most cases nothing happens....
Though I'm eagerly waiting for ICS - I'll wait for a new update from Sammy or a new statement from CF.
And yes, the discussions should be stopped. but there are new roms released and the risk is growing....

trahzebuck said:
And yes, the discussions should be stopped. but there are new roms released and the risk is growing....
Click to expand...
Click to collapse
as well as profit .... samsung