7-7-10 [ROM] Froyo Kangerade 5.0.9 *source built, 9 themes, bug fixes, many features*

[Signum]

Is there anybody else here who just upgraded to this new 5.0.9 version who is running LauncherPro Beta and noticing a serious lag in the scrolling dock beginning to react after the phone has been on standby for a while? If so I'd just like to hear your experiences. If I leave the phone in standby for say a couple hours and then turn it on, the scrolling dock, and even sometimes all the icons on the home screen, and even the scrolling home screens may just sit there and act frozen or stutter really bad for around 10-20 seconds and then after it finishes doing something (indicated by when SetCPU shows speed drops back down to 125mHz), it starts working normally and really fast after that like it should. I have noticed this issue getting slightly worse with each new release of LauncherPro Beta for the last few releases, but I was still able to deal with it since it would only stutter for a few seconds, but after putting on this latest 5.0.6 ROM on it got really bad and I'm not sure how to deal with it 100% just yet. I really love the LauncherPro Beta because it has the option for the 3 docks side-by-side and they all scroll and are customizable so you can have a total of 15 shortcuts. It was working really nice back when I had Kangerade v1.0 and a LauncherPro Beta version several builds ago. Back then if I left the phone on standby for say an hour or 2, and then turned the screen on, the dock might just stutter for a couple of scroll attempts while scrolling it but then within about 6-7 seconds it would smooth out and work fine after that. And even if you shut the screen off for just a few minutes and turn it back on it will work fine. But a long soak on standby and it is bad. Then like I said, after a few builds later in LauncherPro Beta, it got a little more pronounced, but this new Kangerade 5.0.6 really kicks it off bad. When I turn the phone on, I'm best off not to even touch a single button or anything, and count to 20 and then when the CPU finally calms down, then everything works as normal, but if I try to do anything like hit a button, icon, scroll a home screen or keep trying to scroll the scrolling dock feature or anything, it just stalls, and hangs and if I keep trying to push buttons and scroll stuff when it is in this frozen state, it will pop up the dialogue asking me to 'Wait' for LauncherPro to respond or to 'Force Close' by hitting the other button. Since I don't have any understanding of how Froyo or Kangerade works under the hood, or even how a launcher works in Android, I really have no idea how to diagnose this problem. I can always restore back to my old Kangerade v1.0 image though and just never upgrade anything ever again, but I would rather keep moving forward with the train and not jump off yet since everything is still really in a beta state for the most part. Maybe JRummy or somebody else technical here might have some ideas on what got changed or what could have been changed that might cause or could cause issues like this. When it is hung in this state where it is really jittery and laggy for that 20 seconds, the SetCPU is reporting that it is at the highest speed slot (1000mHz) and it is like it doesn't have enough resources to do some big task that it is trying to do. And so if you just wait out the 10-20 seconds then it all comes back and works normally again. I've also heard that Froyo was supposed to handle wake-ups better than 2.1 but with this issue it almost feels like the opposite is occuring (like the wake-up process is bringing the system down to its knees). Fuz 1987 from the LauncherPro forum suggested I try a different launcher just to test with and see if I get this same or similar issue after that, so I am going to try that first, but I just thought I'd post this here to see what brews up.

paragraphs are your friend.

 

[FrostMan]

Are this just themes or are they roms? and if they are themes would it work on SS v4.4?

It is undermining to even call these just themes. These are themed roms over a source built froyo by JRummy.

 

[foxxy]

I had the same problem.. I used the root explorer method and the Kang scripts.. couldn't change it..

I too tried all of these methods to no avail -- needed to use terminal emulator as su to copy the zip from sdcard to /data/local directory --working fine now.

That did the trick, thanks!

what if you dont have a data/local directory ? Can you create one. All I have is a data folder and its empty

Decided to buy root explorer and was able to see the hidden files located in my data folder. Deleted the boot animation zip, turned off the phone and *bam* my boot is back and all is now well in the droid world!

Thanks Jrummy for another fine froyo version. So far that is the only problem I have had.

 

[samsonite801]

Post deleted

 

[comper]

Is there anybody else here who just upgraded to this new 5.0.9 version who is running LauncherPro Beta and noticing a serious lag in the scrolling dock beginning to react after the phone has been on standby for a while? If so I'd just like to hear your experiences. If I leave the phone in standby for say a couple hours and then turn it on, the scrolling dock, and even sometimes all the icons on the home screen, and even the scrolling home screens may just sit there and act frozen or stutter really bad for around 10-20 seconds and then after it finishes doing something (indicated by when SetCPU shows speed drops back down to 125mHz), it starts working normally and really fast after that like it should.

I have noticed this issue getting slightly worse with each new release of LauncherPro Beta for the last few releases, but I was still able to deal with it since it would only stutter for a few seconds, but after putting on this latest 5.0.6 ROM on it got really bad and I'm not sure how to deal with it 100% just yet. I really love the LauncherPro Beta because it has the option for the 3 docks side-by-side and they all scroll and are customizable so you can have a total of 15 shortcuts. It was working really nice back when I had Kangerade v1.0 and a LauncherPro Beta version several builds ago. Back then if I left the phone on standby for say an hour or 2, and then turned the screen on, the dock might just stutter for a couple of scroll attempts while scrolling it but then within about 6-7 seconds it would smooth out and work fine after that. And even if you shut the screen off for just a few minutes and turn it back on it will work fine. But a long soak on standby and it is bad.

Then like I said, after a few builds later in LauncherPro Beta, it got a little more pronounced, but this new Kangerade 5.0.6 really kicks it off bad. When I turn the phone on, I'm best off not to even touch a single button or anything, and count to 20 and then when the CPU finally calms down, then everything works as normal, but if I try to do anything like hit a button, icon, scroll a home screen or keep trying to scroll the scrolling dock feature or anything, it just stalls, and hangs and if I keep trying to push buttons and scroll stuff when it is in this frozen state, it will pop up the dialogue asking me to 'Wait' for LauncherPro to respond or to 'Force Close' by hitting the other button.

Since I don't have any understanding of how Froyo or Kangerade works under the hood, or even how a launcher works in Android, I really have no idea how to diagnose this problem. I can always restore back to my old Kangerade v1.0 image though and just never upgrade anything ever again, but I would rather keep moving forward with the train and not jump off yet since everything is still really in a beta state for the most part. Maybe JRummy or somebody else technical here might have some ideas on what got changed or what could have been changed that might cause or could cause issues like this. When it is hung in this state where it is really jittery and laggy for that 20 seconds, the SetCPU is reporting that it is at the highest speed slot (1000mHz) and it is like it doesn't have enough resources to do some big task that it is trying to do. And so if you just wait out the 10-20 seconds then it all comes back and works normally again. I've also heard that Froyo was supposed to handle wake-ups better than 2.1 but with this issue it almost feels like the opposite is occuring (like the wake-up process is bringing the system down to its knees). Fuz 1987 from the LauncherPro forum suggested I try a different launcher just to test with and see if I get this same or similar issue after that, so I am going to try that first, but I just thought I'd post this here to see what brews up.

paragraphs are your friend.

Oh? And where do YOU suggest I insert my paragraph breaks since the subject never changes and thus is only one paragraph? Why don't you show me since you seem to act superior in English composition?

Just split it up a bit like that

 

[devinhfox]

Anyone elses red theme portrait keyboard keys have lines through them when pressed?
The keys turn a nice red when pressed, except they have lines through them.

 

[devinhfox]

comper you cracking me up

 

[hellboar]

Anyone elses red theme portrait keyboard keys have lines through them when pressed?
The keys turn a nice red when pressed, except they have lines through them.

Yes, this has been happening on the cyan version for a few releases now as well.

 

[atticus]

paragraphs are your friend.

Oh? And where do YOU suggest I insert my paragraph breaks since the subject never changes and thus is only one paragraph? Why don't you show me since you seem to act superior in English composition?

Just split it up a bit like that

let's all relax. but yeah ..that is uber long to read. splitting it up wouldn't make people look at it and be like ....."oh, fxck that, that's way too long to read". but I did take the time to read it. and no, i'm sorry, I have had none of those issues with my LaucherPro on 5.0.9.

 

[dlwhtrose]

Okay just updated to the 5.0.9 and wondered if anyone had any issue with the battery not being recognized? I updated both mine and my husband's droid to the latest Kangerade and my droid stopped seeing the battery and thus said that I needed to connect to my charger and it would not see that I was plugged up. so the phone thought the battery was dead and kept rebooting. Same with my husbands. Just wondering if anyone else had this issue. I have since restored our backups until this problem can be resolved.

 

[devinhfox]

one more thing, when trying to switch to the stock font through kangerade scripts, it seems the clock on the lock screen (with pattern unlocking) does not restore to stock, it stays as the font that comes with the rom.
How can I have a completely stock font for the themes?

 

[myk.robinson]

Frequent lock ups?

Having a problem with this ROM and frequent lock ups that require a battery pull. Running the NexTheme version, no special kernel or other custom options. Not sure if I just got a botched download or what. Installing the Green theme tonight to see if I can duplicate it with another, but never had any issues with roms in the past.

Anyone else have any ideas as to what may be causing the instability? Its totally at random, cant narrow it down to any one event.

Thanks,
-myk

 

[FrostMan]

Having a problem with this ROM and frequent lock ups that require a battery pull. Running the NexTheme version, no special kernel or other custom options. Not sure if I just got a botched download or what. Installing the Green theme tonight to see if I can duplicate it with another, but never had any issues with roms in the past.

Anyone else have any ideas as to what may be causing the instability? Its totally at random, cant narrow it down to any one event.

Thanks,
-myk

You using launcherpro by any chance, me along with one other reported to have lock ups on it.

 

[samsonite801]

Post deleted

 

[myk.robinson]

Having a problem with this ROM and frequent lock ups that require a battery pull. Running the NexTheme version, no special kernel or other custom options. Not sure if I just got a botched download or what. Installing the Green theme tonight to see if I can duplicate it with another, but never had any issues with roms in the past.

Anyone else have any ideas as to what may be causing the instability? Its totally at random, cant narrow it down to any one event.

Thanks,
-myk

You using launcherpro by any chance, me along with one other reported to have lock ups on it.

No, but I am using ADW Launcher